commit f443e374ae131c168a065ea1748feac6b2e76613
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 20 13:14:17 2022 -0700

    Linux 5.17
    
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7445b2dcd77ae8385bd08bb6c2db20ea0cfa6230
Merge: 1e0e7a6a28f87 fe83f5eae432c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 20 09:46:52 2022 -0700

    Merge tag 'for-linus-5.17' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fix from Paolo Bonzini:
     "Fix for the SLS mitigation, which makes a 'SETcc/RET' pair grow
      to 'SETcc/RET/INT3'.
    
      This doesn't fit in 4 bytes any more, so the alignment has to
      change to 8 for this case"
    
    * tag 'for-linus-5.17' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      kvm/emulate: Fix SETcc emulation function offsets with SLS

commit 1e0e7a6a28f877312b93cd12a1448c8d53733b55
Merge: 14702b3b2438e 5600f6986628d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 20 09:27:52 2022 -0700

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
    
    Pull input fixes from Dmitry Torokhov:
     "Two driver fixes:
    
       - a fix for zinitix touchscreen to properly report contacts
    
       - a fix for aiptek tablet driver to be more resilient to devices with
         incorrect descriptors"
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
      Input: aiptek - properly check endpoint type
      Input: zinitix - do not report shadow fingers

commit fe83f5eae432ccc8e90082d6ed506d5233547473
Author: Borislav Petkov <bp@suse.de>
Date:   Wed Mar 16 22:05:52 2022 +0100

    kvm/emulate: Fix SETcc emulation function offsets with SLS
    
    The commit in Fixes started adding INT3 after RETs as a mitigation
    against straight-line speculation.
    
    The fastop SETcc implementation in kvm's insn emulator uses macro magic
    to generate all possible SETcc functions and to jump to them when
    emulating the respective instruction.
    
    However, it hardcodes the size and alignment of those functions to 4: a
    three-byte SETcc insn and a single-byte RET. BUT, with SLS, there's an
    INT3 that gets slapped after the RET, which brings the whole scheme out
    of alignment:
    
      15:   0f 90 c0                seto   %al
      18:   c3                      ret
      19:   cc                      int3
      1a:   0f 1f 00                nopl   (%rax)
      1d:   0f 91 c0                setno  %al
      20:   c3                      ret
      21:   cc                      int3
      22:   0f 1f 00                nopl   (%rax)
      25:   0f 92 c0                setb   %al
      28:   c3                      ret
      29:   cc                      int3
    
    and this explodes like this:
    
      int3: 0000 [#1] PREEMPT SMP PTI
      CPU: 0 PID: 2435 Comm: qemu-system-x86 Not tainted 5.17.0-rc8-sls #1
      Hardware name: Dell Inc. Precision WorkStation T3400  /0TP412, BIOS A14 04/30/2012
      RIP: 0010:setc+0x5/0x8 [kvm]
      Code: 00 00 0f 1f 00 0f b6 05 43 24 06 00 c3 cc 0f 1f 80 00 00 00 00 0f 90 c0 c3 cc 0f \
              1f 00 0f 91 c0 c3 cc 0f 1f 00 0f 92 c0 c3 cc <0f> 1f 00 0f 93 c0 c3 cc 0f 1f 00 \
              0f 94 c0 c3 cc 0f 1f 00 0f 95 c0
      Call Trace:
       <TASK>
       ? x86_emulate_insn [kvm]
       ? x86_emulate_instruction [kvm]
       ? vmx_handle_exit [kvm_intel]
       ? kvm_arch_vcpu_ioctl_run [kvm]
       ? kvm_vcpu_ioctl [kvm]
       ? __x64_sys_ioctl
       ? do_syscall_64
       ? entry_SYSCALL_64_after_hwframe
       </TASK>
    
    Raise the alignment value when SLS is enabled and use a macro for that
    instead of hard-coding naked numbers.
    
    Fixes: e463a09af2f0 ("x86: Add straight-line-speculation mitigation")
    Reported-by: Jamie Heilman <jamie@audible.transient.net>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Jamie Heilman <jamie@audible.transient.net>
    Link: https://lore.kernel.org/r/YjGzJwjrvxg5YZ0Z@audible.transient.net
    [Add a comment and a bit of safety checking, since this is going to be changed
     again for IBT support. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 14702b3b2438e2f2d07ae93b5d695c166e5c83d1
Merge: f76da4d5ad516 1447c635802fd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 19 16:36:32 2022 -0700

    Merge tag 'soc-fixes-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC fix from Arnd Bergmann:
     "Here is one last regression fix for 5.17, reverting a patch that went
      into 5.16 as a cleanup that ended up breaking external interrupts on
      Layerscape chips.
    
      The revert makes it work again, but also reintroduces a build time
      warning about the nonstandard DT binding that will have to be dealt
      with in the future"
    
    * tag 'soc-fixes-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
      Revert "arm64: dts: freescale: Fix 'interrupt-map' parent address cells"

commit f76da4d5ad5168de58f0f5be1a12c1052a614663
Merge: 97e9c8eb4bb1d 733ab7e1b5d10
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 19 15:56:43 2022 -0700

    Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Two small(ish) fixes, both in drivers"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: fnic: Finish scsi_cmnd before dropping the spinlock
      scsi: mpt3sas: Page fault in reply q processing

commit 97e9c8eb4bb1dc57859acb1338dfddbd967d7484
Merge: ba6354f61472c 7bd1da15d211d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 19 11:04:10 2022 -0700

    Merge tag 'perf-tools-fixes-for-v5.17-2022-03-19' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tools fixes from Arnaldo Carvalho de Melo:
    
     - Avoid iterating empty evlist, fixing a segfault with 'perf stat --null'
    
     - Ignore case in topdown.slots check, fixing issue with Intel Icelake
       JSON metrics.
    
     - Fix symbol size calculation condition for fixing up corner case
       symbol end address obtained from Kallsyms.
    
    * tag 'perf-tools-fixes-for-v5.17-2022-03-19' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf parse-events: Ignore case in topdown.slots check
      perf evlist: Avoid iteration for empty evlist.
      perf symbols: Fix symbol size calculation condition

commit ba6354f61472c5bc910c34ea1b368f62c3706692
Merge: 6aa61c12a43bb 01b44ef2bf6bc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 19 10:21:34 2022 -0700

    Merge tag 'char-misc-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
    
    Pull char/misc driver fix from Greg KH:
     "Here is a single driver fix for 5.17-final that has been submitted
      many times but I somehow missed it in my patch queue:
    
       - fix for counter sysfs code for reported problem
    
      This has been in linux-next all week with no reported issues"
    
    * tag 'char-misc-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
      counter: Stop using dev_get_drvdata() to get the counter device

commit 6aa61c12a43bb365296e72251e7346b661030b52
Merge: 34e047aa16c01 16b1941eac2bd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 19 10:16:33 2022 -0700

    Merge tag 'usb-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
    
    Pull USB fixes from Greg KH:
     "Here are some small remaining USB fixes for 5.17-final.
    
      They include:
    
       - two USB gadget driver fixes for reported problems
    
       - usbtmc driver fix for syzbot found issues
    
       - musb patch partial revert to resolve a reported regression.
    
      All of these have been in linux-next this week with no reported
      problems"
    
    * tag 'usb-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
      usb: gadget: Fix use-after-free bug by not setting udc->dev.driver
      usb: usbtmc: Fix bug in pipe direction for control transfers
      partially Revert "usb: musb: Set the DT node on the child device"
      usb: gadget: rndis: prevent integer overflow in rndis_set_response()

commit 7bd1da15d211d439d96eb7cc8a35ce694b71d120
Author: Ian Rogers <irogers@google.com>
Date:   Thu Mar 17 15:43:09 2022 -0700

    perf parse-events: Ignore case in topdown.slots check
    
    An issue with icelakex metrics:
    
      https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/tree/tools/perf/pmu-events/arch/x86/icelakex/icx-metrics.json?h=perf/core&id=65eab2bc7dab326ee892ec5a4c749470b368b51a#n48
    
    That causes the slots not to be first.
    
    Fixes: 94dbfd6781a0e87b ("perf parse-events: Architecture specific leader override")
    Reported-by: Caleb Biggers <caleb.biggers@intel.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Zhengjun Xing <zhengjun.xing@linux.intel.com>
    Link: https://lore.kernel.org/r/20220317224309.543736-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 8b464eac9765dfc84d0327fa3f3668faa439d1ce
Author: Ian Rogers <irogers@google.com>
Date:   Thu Mar 17 16:16:43 2022 -0700

    perf evlist: Avoid iteration for empty evlist.
    
    As seen with 'perf stat --null ..' and reported in:
    https://lore.kernel.org/lkml/YjCLcpcX2peeQVCH@kernel.org/
    
    v2. Avoids setting evsel in the empty list case as suggested by Jiri Olsa.
    
        Committer testing:
    
    Before:
    
      $  perf stat --null sleep 1
      Segmentation fault (core dumped)
      $
    
    After:
    
      $  perf stat --null sleep 1
    
       Performance counter stats for 'sleep 1':
    
             1.010340646 seconds time elapsed
    
             0.001420000 seconds user
             0.000000000 seconds sys
      $
    
    Fixes: 472832d2c000b961 ("perf evlist: Refactor evlist__for_each_cpu()")
    Reported-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Acked-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220317231643.550902-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3cf6a32f3f2a45944dd5be5c6ac4deb46bcd3bee
Author: Michael Petlan <mpetlan@redhat.com>
Date:   Thu Mar 17 14:55:36 2022 +0100

    perf symbols: Fix symbol size calculation condition
    
    Before this patch, the symbol end address fixup to be called, needed two
    conditions being met:
    
      if (prev->end == prev->start && prev->end != curr->start)
    
    Where
      "prev->end == prev->start" means that prev is zero-long
                                 (and thus needs a fixup)
    and
      "prev->end != curr->start" means that fixup hasn't been applied yet
    
    However, this logic is incorrect in the following situation:
    
    *curr  = {rb_node = {__rb_parent_color = 278218928,
      rb_right = 0x0, rb_left = 0x0},
      start = 0xc000000000062354,
      end = 0xc000000000062354, namelen = 40, type = 2 '\002',
      binding = 0 '\000', idle = 0 '\000', ignore = 0 '\000',
      inlined = 0 '\000', arch_sym = 0 '\000', annotate2 = false,
      name = 0x1159739e "kprobe_optinsn_page\t[__builtin__kprobes]"}
    
    *prev = {rb_node = {__rb_parent_color = 278219041,
      rb_right = 0x109548b0, rb_left = 0x109547c0},
      start = 0xc000000000062354,
      end = 0xc000000000062354, namelen = 12, type = 2 '\002',
      binding = 1 '\001', idle = 0 '\000', ignore = 0 '\000',
      inlined = 0 '\000', arch_sym = 0 '\000', annotate2 = false,
      name = 0x1095486e "optinsn_slot"}
    
    In this case, prev->start == prev->end == curr->start == curr->end,
    thus the condition above thinks that "we need a fixup due to zero
    length of prev symbol, but it has been probably done, since the
    prev->end == curr->start", which is wrong.
    
    After the patch, the execution path proceeds to arch__symbols__fixup_end
    function which fixes up the size of prev symbol by adding page_size to
    its end offset.
    
    Fixes: 3b01a413c196c910 ("perf symbols: Improve kallsyms symbol end addr calculation")
    Signed-off-by: Michael Petlan <mpetlan@redhat.com>
    Cc: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
    Link: http://lore.kernel.org/lkml/20220317135536.805-1-mpetlan@redhat.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 34e047aa16c0123bbae8e2f6df33e5ecc1f56601
Merge: 6e4069881a7f9 316e46f65a549
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 18 12:32:59 2022 -0700

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fixes from Catalin Marinas:
     "Fix two compiler warnings introduced by recent commits: pointer
      arithmetic and double initialisation of struct field"
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: errata: avoid duplicate field initializer
      arm64: fix clang warning about TRAMP_VALIAS

commit 6e4069881a7f9dceb6dfb97e436d55e3c7f43e81
Merge: 6c4bcd8140770 e3ee9fb22652f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 18 12:22:15 2022 -0700

    Merge tag '5.17-rc8-smb3-fix' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs fix from Steve French:
     "Small fix for regression in multiuser mounts.
    
      The additional improvements suggested by Ronnie to make the server and
      session status handling code easier to read can wait for the 5.18
      merge window."
    
    * tag '5.17-rc8-smb3-fix' of git://git.samba.org/sfrench/cifs-2.6:
      smb3: fix incorrect session setup check for multiuser mounts

commit 6c4bcd8140770f8190a8e691aff0e3550069edb1
Merge: cced5148a1303 f6189589fa7cc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 18 12:15:56 2022 -0700

    Merge tag 'block-5.17-2022-03-18' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - Revert of a nvme target feature (Hannes)
    
     - Fix a memory leak with rq-qos (Ming)
    
    * tag 'block-5.17-2022-03-18' of git://git.kernel.dk/linux-block:
      nvmet: revert "nvmet: make discovery NQN configurable"
      block: release rq qos structures for queue without disk

commit cced5148a1303a2ec57d04a7745a560821b45280
Merge: 551acdc3c3d2b ca5a5761ac542
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 18 12:01:19 2022 -0700

    Merge tag 'drm-fixes-2022-03-18' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "A few minor changes to finish things off, one mgag200 regression, imx
      fix and couple of panel changes.
    
      imx:
       - Don't test bus flags in atomic check
    
      mgag200:
       - Fix PLL setup on some models
    
      panel:
       - Fix bpp settings on Innolux G070Y2-L01
       - Fix DRM_PANEL_EDP Kconfig dependencies"
    
    * tag 'drm-fixes-2022-03-18' of git://anongit.freedesktop.org/drm/drm:
      drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS
      drm/panel: simple: Fix Innolux G070Y2-L01 BPP settings
      drm/imx: parallel-display: Remove bus flags check in imx_pd_bridge_atomic_check()
      drm/mgag200: Fix PLL setup for g200wb and g200ew

commit 316e46f65a5497839857db08b6fbf60f568b165a
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Wed Mar 16 19:37:45 2022 +0100

    arm64: errata: avoid duplicate field initializer
    
    The '.type' field is initialized both in place and in the macro
    as reported by this W=1 warning:
    
    arch/arm64/include/asm/cpufeature.h:281:9: error: initialized field overwritten [-Werror=override-init]
      281 |         (ARM64_CPUCAP_SCOPE_LOCAL_CPU | ARM64_CPUCAP_OPTIONAL_FOR_LATE_CPU)
          |         ^
    arch/arm64/kernel/cpu_errata.c:136:17: note: in expansion of macro 'ARM64_CPUCAP_LOCAL_CPU_ERRATUM'
      136 |         .type = ARM64_CPUCAP_LOCAL_CPU_ERRATUM,                         \
          |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    arch/arm64/kernel/cpu_errata.c:145:9: note: in expansion of macro 'ERRATA_MIDR_RANGE'
      145 |         ERRATA_MIDR_RANGE(m, var, r_min, var, r_max)
          |         ^~~~~~~~~~~~~~~~~
    arch/arm64/kernel/cpu_errata.c:613:17: note: in expansion of macro 'ERRATA_MIDR_REV_RANGE'
      613 |                 ERRATA_MIDR_REV_RANGE(MIDR_CORTEX_A510, 0, 0, 2),
          |                 ^~~~~~~~~~~~~~~~~~~~~
    arch/arm64/include/asm/cpufeature.h:281:9: note: (near initialization for 'arm64_errata[18].type')
      281 |         (ARM64_CPUCAP_SCOPE_LOCAL_CPU | ARM64_CPUCAP_OPTIONAL_FOR_LATE_CPU)
          |         ^
    
    Remove the extranous initializer.
    
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Fixes: 1dd498e5e26a ("KVM: arm64: Workaround Cortex-A510's single-step and PAC trap errata")
    Link: https://lore.kernel.org/r/20220316183800.1546731-1-arnd@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 7f34b43e07cb512b28543fdcb9f35d1fbfda9ebc
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Wed Mar 16 19:38:18 2022 +0100

    arm64: fix clang warning about TRAMP_VALIAS
    
    The newly introduced TRAMP_VALIAS definition causes a build warning
    with clang-14:
    
    arch/arm64/include/asm/vectors.h:66:31: error: arithmetic on a null pointer treated as a cast from integer to pointer is a GNU extension [-Werror,-Wnull-pointer-arithmetic]
                    return (char *)TRAMP_VALIAS + SZ_2K * slot;
    
    Change the addition to something clang does not complain about.
    
    Fixes: bd09128d16fa ("arm64: Add percpu vectors for EL1")
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Acked-by: James Morse <james.morse@arm.com>
    Link: https://lore.kernel.org/r/20220316183833.1563139-1-arnd@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit ca5a5761ac542691a6b3520b6c5c047cf63b4b8d
Merge: 09688c0166e76 3c3384050d685
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 18 13:30:30 2022 +1000

    Merge tag 'drm-misc-fixes-2022-03-17' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/imx: Don't test bus flags in atomic check
     * drm/mgag200: Fix PLL setup on some models
     * drm/panel: Fix bpp settings on Innolux G070Y2-L01; Fix DRM_PANEL_EDP
       Kconfig dependencies
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YjMNcqOuDFDoe+EN@linux-uq9g

commit 551acdc3c3d2b6bc97f11e31dcf960bc36343bfc
Merge: c81801eb7f247 b04683ff8f082
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 17 12:55:26 2022 -0700

    Merge tag 'net-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from netfilter, ipsec, and wireless.
    
      A few last minute revert / disable and fix patches came down from our
      sub-trees. We're not waiting for any fixes at this point.
    
      Current release - regressions:
    
       - Revert "netfilter: nat: force port remap to prevent shadowing
         well-known ports", restore working conntrack on asymmetric paths
    
       - Revert "ath10k: drop beacon and probe response which leak from
         other channel", restore working AP and mesh mode on QCA9984
    
       - eth: intel: fix hang during reboot/shutdown
    
      Current release - new code bugs:
    
       - netfilter: nf_tables: disable register tracking, it needs more work
         to cover all corner cases
    
      Previous releases - regressions:
    
       - ipv6: fix skb_over_panic in __ip6_append_data when (admin-only)
         extension headers get specified
    
       - esp6: fix ESP over TCP/UDP, interpret ipv6_skip_exthdr's return
         value more selectively
    
       - bnx2x: fix driver load failure when FW not present in initrd
    
      Previous releases - always broken:
    
       - vsock: stop destroying unrelated sockets in nested virtualization
    
       - packet: fix slab-out-of-bounds access in packet_recvmsg()
    
      Misc:
    
       - add Paolo Abeni to networking maintainers!"
    
    * tag 'net-5.17-final' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (26 commits)
      iavf: Fix hang during reboot/shutdown
      net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower offload
      net: bcmgenet: skip invalid partial checksums
      bnx2x: fix built-in kernel driver load failure
      net: phy: mscc: Add MODULE_FIRMWARE macros
      net: dsa: Add missing of_node_put() in dsa_port_parse_of
      net: handle ARPHRD_PIMREG in dev_is_mac_header_xmit()
      Revert "ath10k: drop beacon and probe response which leak from other channel"
      hv_netvsc: Add check for kvmalloc_array
      iavf: Fix double free in iavf_reset_task
      ice: destroy flow director filter mutex after releasing VSIs
      ice: fix NULL pointer dereference in ice_update_vsi_tx_ring_stats()
      Add Paolo Abeni to networking maintainers
      atm: eni: Add check for dma_map_single
      net/packet: fix slab-out-of-bounds access in packet_recvmsg()
      net: mdio: mscc-miim: fix duplicate debugfs entry
      net: phy: marvell: Fix invalid comparison in the resume and suspend functions
      esp6: fix check on ipv6_skip_exthdr's return value
      net: dsa: microchip: add spi_device_id tables
      netfilter: nf_tables: disable register tracking
      ...

commit c81801eb7f2476a25d8fb27449e01b0bef46908a
Merge: 2ab99e54584e0 462ccc35a750f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 17 12:40:59 2022 -0700

    Merge tag 'acpi-5.17-rc9' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull ACPI fix from Rafael Wysocki:
     "Revert recent commit that caused multiple systems to misbehave due to
      firmware issues"
    
    * tag 'acpi-5.17-rc9' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      Revert "ACPI: scan: Do not add device IDs from _CID if _HID is not valid"

commit 2ab99e54584e0048b9c0bea2d61053a61bae0bbc
Merge: a46310bfae94c 1c4debc443ef7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 17 12:36:47 2022 -0700

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "Four patches.
    
      Subsystems affected by this patch series: mm/swap, kconfig, ocfs2, and
      selftests"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      selftests: vm: fix clang build error multiple output files
      ocfs2: fix crash when initialize filecheck kobj fails
      configs/debug: restore DEBUG_INFO=y for overriding
      mm: swap: get rid of livelock in swapin readahead

commit 1c4debc443ef7037dcb7c4f08c33b9caebd21d2e
Author: Yosry Ahmed <yosryahmed@google.com>
Date:   Wed Mar 16 16:15:12 2022 -0700

    selftests: vm: fix clang build error multiple output files
    
    When building the vm selftests using clang, some errors are seen due to
    having headers in the compilation command:
    
      clang -Wall -I ../../../../usr/include  -no-pie    gup_test.c ../../../../mm/gup_test.h -lrt -lpthread -o .../tools/testing/selftests/vm/gup_test
      clang: error: cannot specify -o when generating multiple output files
      make[1]: *** [../lib.mk:146: .../tools/testing/selftests/vm/gup_test] Error 1
    
    Rework to add the header files to LOCAL_HDRS before including ../lib.mk,
    since the dependency is evaluated in '$(OUTPUT)/%:%.c $(LOCAL_HDRS)' in
    file lib.mk.
    
    Link: https://lkml.kernel.org/r/20220304000645.1888133-1-yosryahmed@google.com
    Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Nathan Chancellor <nathan@kernel.org>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7b0b1332cfdb94489836b67d088a779699f8e47e
Author: Joseph Qi <joseph.qi@linux.alibaba.com>
Date:   Wed Mar 16 16:15:09 2022 -0700

    ocfs2: fix crash when initialize filecheck kobj fails
    
    Once s_root is set, genric_shutdown_super() will be called if
    fill_super() fails.  That means, we will call ocfs2_dismount_volume()
    twice in such case, which can lead to kernel crash.
    
    Fix this issue by initializing filecheck kobj before setting s_root.
    
    Link: https://lkml.kernel.org/r/20220310081930.86305-1-joseph.qi@linux.alibaba.com
    Fixes: 5f483c4abb50 ("ocfs2: add kobject for online file check")
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8208257d2d04d4953a8cb9f1426d245a95c4fea2
Author: Qian Cai <quic_qiancai@quicinc.com>
Date:   Wed Mar 16 16:15:06 2022 -0700

    configs/debug: restore DEBUG_INFO=y for overriding
    
    Previously, I failed to realize that Kees' patch [1] has not been merged
    into the mainline yet, and dropped DEBUG_INFO=y too eagerly from the
    mainline.  As the results, "make debug.config" won't be able to flip
    DEBUG_INFO=n from the existing .config.  This should close the gaps of a
    few weeks before Kees' patch is there, and work regardless of their
    merging status anyway.
    
    Link: https://lore.kernel.org/all/20220125075126.891825-1-keescook@chromium.org/ [1]
    Link: https://lkml.kernel.org/r/20220308153524.8618-1-quic_qiancai@quicinc.com
    Signed-off-by: Qian Cai <quic_qiancai@quicinc.com>
    Reported-by: Daniel Thompson <daniel.thompson@linaro.org>
    Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
    Cc: Kees Cook <keescook@chromium.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 029c4628b2eb2ca969e9bf979b05dc18d8d5575e
Author: Guo Ziliang <guo.ziliang@zte.com.cn>
Date:   Wed Mar 16 16:15:03 2022 -0700

    mm: swap: get rid of livelock in swapin readahead
    
    In our testing, a livelock task was found.  Through sysrq printing, same
    stack was found every time, as follows:
    
      __swap_duplicate+0x58/0x1a0
      swapcache_prepare+0x24/0x30
      __read_swap_cache_async+0xac/0x220
      read_swap_cache_async+0x58/0xa0
      swapin_readahead+0x24c/0x628
      do_swap_page+0x374/0x8a0
      __handle_mm_fault+0x598/0xd60
      handle_mm_fault+0x114/0x200
      do_page_fault+0x148/0x4d0
      do_translation_fault+0xb0/0xd4
      do_mem_abort+0x50/0xb0
    
    The reason for the livelock is that swapcache_prepare() always returns
    EEXIST, indicating that SWAP_HAS_CACHE has not been cleared, so that it
    cannot jump out of the loop.  We suspect that the task that clears the
    SWAP_HAS_CACHE flag never gets a chance to run.  We try to lower the
    priority of the task stuck in a livelock so that the task that clears
    the SWAP_HAS_CACHE flag will run.  The results show that the system
    returns to normal after the priority is lowered.
    
    In our testing, multiple real-time tasks are bound to the same core, and
    the task in the livelock is the highest priority task of the core, so
    the livelocked task cannot be preempted.
    
    Although cond_resched() is used by __read_swap_cache_async, it is an
    empty function in the preemptive system and cannot achieve the purpose
    of releasing the CPU.  A high-priority task cannot release the CPU
    unless preempted by a higher-priority task.  But when this task is
    already the highest priority task on this core, other tasks will not be
    able to be scheduled.  So we think we should replace cond_resched() with
    schedule_timeout_uninterruptible(1), schedule_timeout_interruptible will
    call set_current_state first to set the task state, so the task will be
    removed from the running queue, so as to achieve the purpose of giving
    up the CPU and prevent it from running in kernel mode for too long.
    
    (akpm: ugly hack becomes uglier.  But it fixes the issue in a
    backportable-to-stable fashion while we hopefully work on something
    better)
    
    Link: https://lkml.kernel.org/r/20220221111749.1928222-1-cgel.zte@gmail.com
    Signed-off-by: Guo Ziliang <guo.ziliang@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Reviewed-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
    Reviewed-by: Jiang Xuexin <jiang.xuexin@zte.com.cn>
    Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
    Acked-by: Hugh Dickins <hughd@google.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Roger Quadros <rogerq@kernel.org>
    Cc: Ziliang Guo <guo.ziliang@zte.com.cn>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b04683ff8f0823b869c219c78ba0d974bddea0b5
Author: Ivan Vecera <ivecera@redhat.com>
Date:   Thu Mar 17 11:45:24 2022 +0100

    iavf: Fix hang during reboot/shutdown
    
    Recent commit 974578017fc1 ("iavf: Add waiting so the port is
    initialized in remove") adds a wait-loop at the beginning of
    iavf_remove() to ensure that port initialization is finished
    prior unregistering net device. This causes a regression
    in reboot/shutdown scenario because in this case callback
    iavf_shutdown() is called and this callback detaches the device,
    makes it down if it is running and sets its state to __IAVF_REMOVE.
    Later shutdown callback of associated PF driver (e.g. ice_shutdown)
    is called. That callback calls among other things sriov_disable()
    that calls indirectly iavf_remove() (see stack trace below).
    As the adapter state is already __IAVF_REMOVE then the mentioned
    loop is end-less and shutdown process hangs.
    
    The patch fixes this by checking adapter's state at the beginning
    of iavf_remove() and skips the rest of the function if the adapter
    is already in remove state (shutdown is in progress).
    
    Reproducer:
    1. Create VF on PF driven by ice or i40e driver
    2. Ensure that the VF is bound to iavf driver
    3. Reboot
    
    [52625.981294] sysrq: SysRq : Show Blocked State
    [52625.988377] task:reboot          state:D stack:    0 pid:17359 ppid:     1 f2
    [52625.996732] Call Trace:
    [52625.999187]  __schedule+0x2d1/0x830
    [52626.007400]  schedule+0x35/0xa0
    [52626.010545]  schedule_hrtimeout_range_clock+0x83/0x100
    [52626.020046]  usleep_range+0x5b/0x80
    [52626.023540]  iavf_remove+0x63/0x5b0 [iavf]
    [52626.027645]  pci_device_remove+0x3b/0xc0
    [52626.031572]  device_release_driver_internal+0x103/0x1f0
    [52626.036805]  pci_stop_bus_device+0x72/0xa0
    [52626.040904]  pci_stop_and_remove_bus_device+0xe/0x20
    [52626.045870]  pci_iov_remove_virtfn+0xba/0x120
    [52626.050232]  sriov_disable+0x2f/0xe0
    [52626.053813]  ice_free_vfs+0x7c/0x340 [ice]
    [52626.057946]  ice_remove+0x220/0x240 [ice]
    [52626.061967]  ice_shutdown+0x16/0x50 [ice]
    [52626.065987]  pci_device_shutdown+0x34/0x60
    [52626.070086]  device_shutdown+0x165/0x1c5
    [52626.074011]  kernel_restart+0xe/0x30
    [52626.077593]  __do_sys_reboot+0x1d2/0x210
    [52626.093815]  do_syscall_64+0x5b/0x1a0
    [52626.097483]  entry_SYSCALL_64_after_hwframe+0x65/0xca
    
    Fixes: 974578017fc1 ("iavf: Add waiting so the port is initialized in remove")
    Signed-off-by: Ivan Vecera <ivecera@redhat.com>
    Link: https://lore.kernel.org/r/20220317104524.2802848-1-ivecera@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8e0341aefcc9133f3f48683873284b169581315b
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Wed Mar 16 21:21:17 2022 +0200

    net: mscc: ocelot: fix backwards compatibility with single-chain tc-flower offload
    
    ACL rules can be offloaded to VCAP IS2 either through chain 0, or, since
    the blamed commit, through a chain index whose number encodes a specific
    PAG (Policy Action Group) and lookup number.
    
    The chain number is translated through ocelot_chain_to_pag() into a PAG,
    and through ocelot_chain_to_lookup() into a lookup number.
    
    The problem with the blamed commit is that the above 2 functions don't
    have special treatment for chain 0. So ocelot_chain_to_pag(0) returns
    filter->pag = 224, which is in fact -32, but the "pag" field is an u8.
    
    So we end up programming the hardware with VCAP IS2 entries having a PAG
    of 224. But the way in which the PAG works is that it defines a subset
    of VCAP IS2 filters which should match on a packet. The default PAG is
    0, and previous VCAP IS1 rules (which we offload using 'goto') can
    modify it. So basically, we are installing filters with a PAG on which
    no packet will ever match. This is the hardware equivalent of adding
    filters to a chain which has no 'goto' to it.
    
    Restore the previous functionality by making ACL filters offloaded to
    chain 0 go to PAG 0 and lookup number 0. The choice of PAG is clearly
    correct, but the choice of lookup number isn't "as before" (which was to
    leave the lookup a "don't care"). However, lookup 0 should be fine,
    since even though there are ACL actions (policers) which have a
    requirement to be used in a specific lookup, that lookup is 0.
    
    Fixes: 226e9cd82a96 ("net: mscc: ocelot: only install TCAM entries into a specific lookup and PAG")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220316192117.2568261-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0f643c88c8d240eba0ea25c2e095a46515ff46e9
Author: Doug Berger <opendmb@gmail.com>
Date:   Wed Mar 16 18:28:12 2022 -0700

    net: bcmgenet: skip invalid partial checksums
    
    The RXCHK block will return a partial checksum of 0 if it encounters
    a problem while receiving a packet. Since a 1's complement sum can
    only produce this result if no bits are set in the received data
    stream it is fair to treat it as an invalid partial checksum and
    not pass it up the stack.
    
    Fixes: 810155397890 ("net: bcmgenet: use CHECKSUM_COMPLETE for NETIF_F_RXCSUM")
    Signed-off-by: Doug Berger <opendmb@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220317012812.1313196-1-opendmb@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 424e7834e293936a54fcf05173f2884171adc5a3
Author: Manish Chopra <manishc@marvell.com>
Date:   Wed Mar 16 14:46:13 2022 -0700

    bnx2x: fix built-in kernel driver load failure
    
    Commit b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")
    added request_firmware() logic in probe() which caused
    load failure when firmware file is not present in initrd (below),
    as access to firmware file is not feasible during probe.
    
      Direct firmware load for bnx2x/bnx2x-e2-7.13.15.0.fw failed with error -2
      Direct firmware load for bnx2x/bnx2x-e2-7.13.21.0.fw failed with error -2
    
    This patch fixes this issue by -
    
    1. Removing request_firmware() logic from the probe()
       such that .ndo_open() handle it as it used to handle
       it earlier
    
    2. Given request_firmware() is removed from probe(), so
       driver has to relax FW version comparisons a bit against
       the already loaded FW version (by some other PFs of same
       adapter) to allow different compatible/close enough FWs with which
       multiple PFs may run with (in different environments), as the
       given PF who is in probe flow has no idea now with which firmware
       file version it is going to initialize the device in ndo_open()
    
    Link: https://lore.kernel.org/all/46f2d9d9-ae7f-b332-ddeb-b59802be2bab@molgen.mpg.de/
    Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Tested-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Fixes: b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")
    Signed-off-by: Manish Chopra <manishc@marvell.com>
    Signed-off-by: Ariel Elior <aelior@marvell.com>
    Link: https://lore.kernel.org/r/20220316214613.6884-1-manishc@marvell.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f1858c277ba40172005b76a31e6bb931bfc19d9c
Author: Juerg Haefliger <juerg.haefliger@canonical.com>
Date:   Wed Mar 16 16:18:35 2022 +0100

    net: phy: mscc: Add MODULE_FIRMWARE macros
    
    The driver requires firmware so define MODULE_FIRMWARE so that modinfo
    provides the details.
    
    Fixes: fa164e40c53b ("net: phy: mscc: split the driver into separate files")
    Signed-off-by: Juerg Haefliger <juergh@canonical.com>
    Link: https://lore.kernel.org/r/20220316151835.88765-1-juergh@canonical.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cb0b430b4e3acc88c85e0ad2e25f2a25a5765262
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Wed Mar 16 08:26:02 2022 +0000

    net: dsa: Add missing of_node_put() in dsa_port_parse_of
    
    The device_node pointer is returned by of_parse_phandle()  with refcount
    incremented. We should use of_node_put() on it when done.
    
    Fixes: 6d4e5c570c2d ("net: dsa: get port type at parse time")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20220316082602.10785-1-linmq006@gmail.com
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>

commit 3c3384050d68570f9de0fec9e58824decfefba7a
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Tue Mar 15 09:45:59 2022 +0100

    drm: Don't make DRM_PANEL_BRIDGE dependent on DRM_KMS_HELPERS
    
    Fix a number of undefined references to drm_kms_helper.ko in
    drm_dp_helper.ko:
    
      arm-suse-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in function `drm_dp_mst_duplicate_state':
      drm_dp_mst_topology.c:(.text+0x2df0): undefined reference to `__drm_atomic_helper_private_obj_duplicate_state'
      arm-suse-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in function `drm_dp_delayed_destroy_work':
      drm_dp_mst_topology.c:(.text+0x370c): undefined reference to `drm_kms_helper_hotplug_event'
      arm-suse-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in function `drm_dp_mst_up_req_work':
      drm_dp_mst_topology.c:(.text+0x7938): undefined reference to `drm_kms_helper_hotplug_event'
      arm-suse-linux-gnueabi-ld: drivers/gpu/drm/dp/drm_dp_mst_topology.o: in function `drm_dp_mst_link_probe_work':
      drm_dp_mst_topology.c:(.text+0x82e0): undefined reference to `drm_kms_helper_hotplug_event'
    
    This happens if panel-edp.ko has been configured with
    
      DRM_PANEL_EDP=y
      DRM_DP_HELPER=y
      DRM_KMS_HELPER=m
    
    which builds DP helpers into the kernel and KMS helpers sa a module.
    Making DRM_PANEL_EDP select DRM_KMS_HELPER resolves this problem.
    
    To avoid a resulting cyclic dependency with DRM_PANEL_BRIDGE, don't
    make the latter depend on DRM_KMS_HELPER and fix the one DRM bridge
    drivers that doesn't already select DRM_KMS_HELPER. As KMS helpers
    cannot be selected directly by the user, config symbols should avoid
    depending on it anyway.
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
    Fixes: 3755d35ee1d2 ("drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP")
    Acked-by: Sam Ravnborg <sam@ravnborg.org>
    Tested-by: Brian Masney <bmasney@redhat.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
    Cc: Linux Kernel Functional Testing <lkft@linaro.org>
    Cc: Lyude Paul <lyude@redhat.com>
    Cc: Sam Ravnborg <sam@ravnborg.org>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: dri-devel@lists.freedesktop.org
    Cc: Dave Airlie <airlied@redhat.com>
    Cc: Thierry Reding <thierry.reding@gmail.com>
    Link: https://patchwork.freedesktop.org/patch/478296/

commit a8253684eb4b30abd3faf055bc475c23da748dc6
Merge: fc1b6ef7bfb3d 09688c0166e76
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Thu Mar 17 11:03:28 2022 +0100

    Merge drm/drm-fixes into drm-misc-fixes
    
    Backmerging drm/drm-fixes for commit 3755d35ee1d2 ("drm/panel: Select
    DRM_DP_HELPER for DRM_PANEL_EDP").
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>

commit e3ee9fb22652f228225c352bd4fabec330cac5f0
Author: Steve French <stfrench@microsoft.com>
Date:   Wed Mar 16 22:08:43 2022 -0500

    smb3: fix incorrect session setup check for multiuser mounts
    
    A recent change to how the SMB3 server (socket) and session status
    is managed regressed multiuser mounts by changing the check
    for whether session setup is needed to the socket (TCP_Server_info)
    structure instead of the session struct (cifs_ses). Add additional
    check in cifs_setup_sesion to fix this.
    
    Fixes: 73f9bfbe3d81 ("cifs: maintain a state machine for tcp/smb/tcon sessions")
    Reported-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Acked-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 4ee06de7729d795773145692e246a06448b1eb7a
Author: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Date:   Tue Mar 15 10:20:08 2022 +0100

    net: handle ARPHRD_PIMREG in dev_is_mac_header_xmit()
    
    This kind of interface doesn't have a mac header. This patch fixes
    bpf_redirect() to a PIM interface.
    
    Fixes: 27b29f63058d ("bpf: add bpf_redirect() helper")
    Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
    Link: https://lore.kernel.org/r/20220315092008.31423-1-nicolas.dichtel@6wind.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a46310bfae94cfadf3d28a4d97b71e3e4dcc954c
Merge: d34c58247f73c 9feaf8b387ee0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 16 11:57:46 2022 -0700

    Merge tag 'efi-urgent-for-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi
    
    Pull EFI fix from Ard Biesheuvel:
     "Avoid spurious warnings about unknown boot parameters"
    
    * tag 'efi-urgent-for-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi:
      efi: fix return value of __setup handlers

commit d34c58247f73c5358ceae1ae648fb9daa408ef23
Merge: 56e337f2cf132 a680b1832ced3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 16 11:50:35 2022 -0700

    Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6
    
    Pull crypto fix from Herbert Xu:
     "This fixes a bug where qcom-rng can return a buffer that is not
      completely filled with random data"
    
    * 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6:
      crypto: qcom-rng - ensure buffer for generate is completely filled

commit 1447c635802fd0f5e213ad5277753108d56a4db3
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Tue Dec 14 15:58:52 2021 +0200

    Revert "arm64: dts: freescale: Fix 'interrupt-map' parent address cells"
    
    This reverts commit 869f0ec048dc8fd88c0b2003373bd985795179fb. That
    updated the expected device tree binding format for the ls-extirq
    driver, without also updating the parsing code (ls_extirq_parse_map)
    to the new format.
    
    The context is that the ls-extirq driver uses the standard
    "interrupt-map" OF property in a non-standard way, as suggested by
    Rob Herring during review:
    https://lore.kernel.org/lkml/20190927161118.GA19333@bogus/
    
    This has turned out to be problematic, as Marc Zyngier discovered
    through commit 041284181226 ("of/irq: Allow matching of an interrupt-map
    local to an interrupt controller"), later fixed through commit
    de4adddcbcc2 ("of/irq: Add a quirk for controllers with their own
    definition of interrupt-map"). Marc's position, expressed on multiple
    opportunities, is that:
    
    (a) [ making private use of the reserved "interrupt-map" name in a
        driver ] "is wrong, by the very letter of what an interrupt-map
        means. If the interrupt map points to an interrupt controller,
        that's the target for the interrupt."
    https://lore.kernel.org/lkml/87k0g8jlmg.wl-maz@kernel.org/
    
    (b) [ updating the driver's bindings to accept a non-reserved name for
        this property, as an alternative, is ] "is totally pointless. These
        machines have been in the wild for years, and existing DTs will be
        there *forever*."
    https://lore.kernel.org/lkml/87ilvrk1r0.wl-maz@kernel.org/
    
    Considering the above, the Linux kernel has quirks in place to deal with
    the ls-extirq's non-standard use of the "interrupt-map". These quirks
    may be needed in other operating systems that consume this device tree,
    yet this is seen as the only viable solution.
    
    Therefore, the premise of the patch being reverted here is invalid.
    It doesn't matter whether the driver, in its non-standard use of the
    property, complies to the standard format or not, since this property
    isn't expected to be used for interrupt translation by the core.
    
    This change restores LS1088A, LS2088A/LS2085A and LX2160A to their
    previous bindings, which allows these systems to continue to use
    external interrupt lines with the correct polarity.
    
    Fixes: 869f0ec048dc ("arm64: dts: freescale: Fix 'interrupt-map' parent address cells")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Acked-by: Marc Zyngier <maz@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 186abea8a80b7699a05bbe6cbd661d64f887e1a0
Merge: 1bbdcbaeda445 4db4075f92af2
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Mar 16 11:39:36 2022 -0700

    Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec
    
    Steffen Klassert says:
    
    ====================
    pull request (net): ipsec 2022-03-16
    
    1) Fix a kernel-info-leak in pfkey.
       From Haimin Zhang.
    
    2) Fix an incorrect check of the return value of ipv6_skip_exthdr.
       From Sabrina Dubroca.
    
    * 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec:
      esp6: fix check on ipv6_skip_exthdr's return value
      af_key: add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register
    ====================
    
    Link: https://lore.kernel.org/r/20220316121142.3142336-1-steffen.klassert@secunet.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 1bbdcbaeda445c76ca05f5d822c26fc7268c1ff5
Merge: dea2d93a8ba43 45b4eb7ee6aa1
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Mar 16 11:08:09 2022 -0700

    Merge tag 'wireless-2022-03-16' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless
    
    Kalle Valo says:
    
    ====================
    wireless fixes for v5.17
    
    Third set of fixes for v5.17. We have only one revert to fix an ath10k
    regression.
    
    * tag 'wireless-2022-03-16' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless:
      Revert "ath10k: drop beacon and probe response which leak from other channel"
    ====================
    
    Link: https://lore.kernel.org/r/20220316130249.B5225C340EC@smtp.kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit fc1b6ef7bfb3d1d4df868b1c3e0480cacda6cd81
Author: Marek Vasut <marex@denx.de>
Date:   Sun Feb 20 05:07:18 2022 +0100

    drm/panel: simple: Fix Innolux G070Y2-L01 BPP settings
    
    The Innolux G070Y2-L01 supports two modes of operation:
    1) FRC=Low/NC ... MEDIA_BUS_FMT_RGB666_1X7X3_SPWG ... BPP=6
    2) FRC=High ..... MEDIA_BUS_FMT_RGB888_1X7X4_SPWG ... BPP=8
    
    Currently the panel description mixes both, BPP from 1) and bus
    format from 2), which triggers a warning at panel-simple.c:615.
    
    Pick the later, set bpp=8, fix the warning.
    
    Fixes: a5d2ade627dca ("drm/panel: simple: Add support for Innolux G070Y2-L01")
    Signed-off-by: Marek Vasut <marex@denx.de>
    Cc: Christoph Fritz <chf.fritz@googlemail.com>
    Cc: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
    Cc: Maxime Ripard <maxime@cerno.tech>
    Cc: Sam Ravnborg <sam@ravnborg.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220220040718.532866-1-marex@denx.de
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

commit 6061806a863e8b65b109eb06a280041cc7525442
Author: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Date:   Tue Feb 1 12:36:43 2022 +0100

    drm/imx: parallel-display: Remove bus flags check in imx_pd_bridge_atomic_check()
    
    If display timings were read from the devicetree using
    of_get_display_timing() and pixelclk-active is defined
    there, the flag DISPLAY_FLAGS_SYNC_POSEDGE/NEGEDGE is
    automatically generated. Through the function
    drm_bus_flags_from_videomode() e.g. called in the
    panel-simple driver this flag got into the bus flags,
    but then in imx_pd_bridge_atomic_check() the bus flag
    check failed and will not initialize the display. The
    original commit fe141cedc433 does not explain why this
    check was introduced. So remove the bus flags check,
    because it stops the initialization of the display with
    valid bus flags.
    
    Fixes: fe141cedc433 ("drm/imx: pd: Use bus format/flags provided by the bridge when available")
    Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
    Cc: Marek Vasut <marex@denx.de>
    Cc: Boris Brezillon <boris.brezillon@collabora.com>
    Cc: Philipp Zabel <p.zabel@pengutronix.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Shawn Guo <shawnguo@kernel.org>
    Cc: Sascha Hauer <s.hauer@pengutronix.de>
    Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
    Cc: Fabio Estevam <festevam@gmail.com>
    Cc: NXP Linux Team <linux-imx@nxp.com>
    Cc: linux-arm-kernel@lists.infradead.org
    To: dri-devel@lists.freedesktop.org
    Tested-by: Max Krummenacher <max.krummenacher@toradex.com>
    Acked-by: Boris Brezillon <boris.brezillon@collabora.com>
    Signed-off-by: Marek Vasut <marex@denx.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220201113643.4638-1-cniedermaier@dh-electronics.com
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

commit f6189589fa7cc4fb6b53f2929f69f0505123202f
Merge: daaca3522a8e6 0c48645a7f398
Author: Jens Axboe <axboe@kernel.dk>
Date:   Wed Mar 16 05:43:25 2022 -0600

    Merge tag 'nvme-5.17-2022-03-16' of git://git.infradead.org/nvme into block-5.17
    
    Pull NVMe fix from Christoph:
    
    "nvme fix for Linux 5.17
    
     - last minute revert of a nvmet feature added in Linux 5.16
       (Hannes Reinecke)"
    
    * tag 'nvme-5.17-2022-03-16' of git://git.infradead.org/nvme:
      nvmet: revert "nvmet: make discovery NQN configurable"

commit 45b4eb7ee6aa1a55a50831b328aa5f46ac3a7187
Author: Kalle Valo <quic_kvalo@quicinc.com>
Date:   Tue Mar 15 17:54:55 2022 +0200

    Revert "ath10k: drop beacon and probe response which leak from other channel"
    
    This reverts commit 3bf2537ec2e33310b431b53fd84be8833736c256.
    
    I was reported privately that this commit breaks AP and mesh mode on QCA9984
    (firmware 10.4-3.9.0.2-00156). So revert the commit to fix the regression.
    
    There was a conflict due to cfg80211 API changes but that was easy to fix.
    
    Fixes: 3bf2537ec2e3 ("ath10k: drop beacon and probe response which leak from other channel")
    Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
    Link: https://lore.kernel.org/r/20220315155455.20446-1-kvalo@kernel.org

commit 462ccc35a750f335c8456cde9120b8b593fff60f
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Mar 16 11:23:05 2022 +0100

    Revert "ACPI: scan: Do not add device IDs from _CID if _HID is not valid"
    
    Revert commit e38f9ff63e6d ("ACPI: scan: Do not add device IDs from _CID
    if _HID is not valid"), because it has introduced regressions on
    multiple systems, even though it only has effect on clearly invalid
    firmware.
    
    Reported-by: Pierre-Louis Bossart <notifications@github.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit dea2d93a8ba437460c5f21bdfa4ada57fa1d2179
Merge: 886e44c9298a6 16b2dd8cdf6f4
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Mar 16 10:07:43 2022 +0000

    Merge branch '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    ====================
    Intel Wired LAN Driver Updates 2022-03-15
    
    This series contains updates to ice and iavf drivers.
    
    Maciej adjusts null check logic on Tx ring to prevent possible NULL
    pointer dereference for ice.
    
    Sudheer moves destruction of Flow Director lock as it was being accessed
    after destruction for ice.
    
    Przemyslaw removes an excess mutex unlock as it was being double
    unlocked for iavf.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 886e44c9298a6b428ae046e2fa092ca52e822e6a
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Mon Mar 14 10:01:25 2022 +0800

    hv_netvsc: Add check for kvmalloc_array
    
    As the potential failure of the kvmalloc_array(),
    it should be better to check and restore the 'data'
    if fails in order to avoid the dereference of the
    NULL pointer.
    
    Fixes: 6ae746711263 ("hv_netvsc: Add per-cpu ethtool stats for netvsc")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220314020125.2365084-1-jiasheng@iscas.ac.cn
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 16b2dd8cdf6f4e0597c34899de74b4d012b78188
Author: Przemyslaw Patynowski <przemyslawx.patynowski@intel.com>
Date:   Wed Mar 9 16:37:39 2022 +0100

    iavf: Fix double free in iavf_reset_task
    
    Fix double free possibility in iavf_disable_vf, as crit_lock is
    freed in caller, iavf_reset_task. Add kernel-doc for iavf_disable_vf.
    Remove mutex_unlock in iavf_disable_vf.
    Without this patch there is double free scenario, when calling
    iavf_reset_task.
    
    Fixes: e85ff9c631e1 ("iavf: Fix deadlock in iavf_reset_task")
    Signed-off-by: Przemyslaw Patynowski <przemyslawx.patynowski@intel.com>
    Suggested-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 1b4ae7d925c6569fff27313b4d84171b11510893
Author: Sudheer Mogilappagari <sudheer.mogilappagari@intel.com>
Date:   Thu Mar 10 10:46:52 2022 -0800

    ice: destroy flow director filter mutex after releasing VSIs
    
    Currently fdir_fltr_lock is accessed in ice_vsi_release_all() function
    after it is destroyed. Instead destroy mutex after ice_vsi_release_all.
    
    Fixes: 40319796b732 ("ice: Add flow director support for channel mode")
    Signed-off-by: Sudheer Mogilappagari <sudheer.mogilappagari@intel.com>
    Tested-by: Bharathi Sreenivas <bharathi.sreenivas@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit f153546913bada41a811722f2c6d17c3243a0333
Author: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Date:   Mon Mar 7 18:47:39 2022 +0100

    ice: fix NULL pointer dereference in ice_update_vsi_tx_ring_stats()
    
    It is possible to do NULL pointer dereference in routine that updates
    Tx ring stats. Currently only stats and bytes are updated when ring
    pointer is valid, but later on ring is accessed to propagate gathered Tx
    stats onto VSI stats.
    
    Change the existing logic to move to next ring when ring is NULL.
    
    Fixes: e72bba21355d ("ice: split ice_ring onto Tx/Rx separate structs")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
    Acked-by: Alexander Lobakin <alexandr.lobakin@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit e9c14b59ea2ec19afe22d60b07583b7e08c74290
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Mon Mar 14 15:28:19 2022 -0700

    Add Paolo Abeni to networking maintainers
    
    Growing the network maintainers team from 2 to 3.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Link: https://lore.kernel.org/r/20220314222819.958428-1-kuba@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 01b44ef2bf6bc83df8a4703029fd611fbfc31c60
Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date:   Thu Mar 10 19:18:09 2022 -0500

    counter: Stop using dev_get_drvdata() to get the counter device
    
    dev_get_drvdata() returns NULL since commit b56346ddbd82 ("counter: Use
    container_of instead of drvdata to track counter_device") which wrongly
    claimed there were no users of drvdata. Convert to container_of() to
    fix a null pointer dereference.
    
    Reported-by: Oleksij Rempel <o.rempel@pengutronix.de>
    Fixes: b56346ddbd82 ("counter: Use container_of instead of drvdata to track counter_device")
    Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
    Link: https://lore.kernel.org/all/20220204082556.370348-1-u.kleine-koenig@pengutronix.de/
    Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
    Link: https://lore.kernel.org/r/4a14311a3b935b62b33e665a97ecaaf2f078228a.1646957732.git.vilhelm.gray@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 733ab7e1b5d1041204c4ca7373f6e6f9d08e3283
Author: David Jeffery <djeffery@redhat.com>
Date:   Fri Mar 11 13:43:59 2022 -0500

    scsi: fnic: Finish scsi_cmnd before dropping the spinlock
    
    When aborting a SCSI command through fnic, there is a race with the fnic
    interrupt handler which can result in the SCSI command and its request
    being completed twice. If the interrupt handler claims the command by
    setting CMD_SP to NULL first, the abort handler assumes the interrupt
    handler has completed the command and returns SUCCESS, causing the request
    for the scsi_cmnd to be re-queued.
    
    But the interrupt handler may not have finished the command yet. After it
    drops the spinlock protecting CMD_SP, it does memory cleanup before finally
    calling scsi_done() to complete the scsi_cmnd. If the call to scsi_done
    occurs after the abort handler finishes and re-queues the request, the
    completion of the scsi_cmnd will advance and try to double complete a
    request already queued for retry.
    
    This patch fixes the issue by moving scsi_done() and any other use of
    scsi_cmnd to before the spinlock is released by the interrupt handler.
    
    Link: https://lore.kernel.org/r/20220311184359.2345319-1-djeffery@redhat.com
    Reviewed-by: Laurence Oberman <loberman@redhat.com>
    Reviewed-by: Ming Lei <ming.lei@redhat.com>
    Signed-off-by: David Jeffery <djeffery@redhat.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 16b1941eac2bd499f065a6739a40ce0011a3d740
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Sat Mar 5 21:47:22 2022 -0500

    usb: gadget: Fix use-after-free bug by not setting udc->dev.driver
    
    The syzbot fuzzer found a use-after-free bug:
    
    BUG: KASAN: use-after-free in dev_uevent+0x712/0x780 drivers/base/core.c:2320
    Read of size 8 at addr ffff88802b934098 by task udevd/3689
    
    CPU: 2 PID: 3689 Comm: udevd Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0
    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     print_address_description.constprop.0.cold+0x8d/0x303 mm/kasan/report.c:255
     __kasan_report mm/kasan/report.c:442 [inline]
     kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
     dev_uevent+0x712/0x780 drivers/base/core.c:2320
     uevent_show+0x1b8/0x380 drivers/base/core.c:2391
     dev_attr_show+0x4b/0x90 drivers/base/core.c:2094
    
    Although the bug manifested in the driver core, the real cause was a
    race with the gadget core.  dev_uevent() does:
    
            if (dev->driver)
                    add_uevent_var(env, "DRIVER=%s", dev->driver->name);
    
    and between the test and the dereference of dev->driver, the gadget
    core sets dev->driver to NULL.
    
    The race wouldn't occur if the gadget core registered its devices on
    a real bus, using the standard synchronization techniques of the
    driver core.  However, it's not necessary to make such a large change
    in order to fix this bug; all we need to do is make sure that
    udc->dev.driver is always NULL.
    
    In fact, there is no reason for udc->dev.driver ever to be set to
    anything, let alone to the value it currently gets: the address of the
    gadget's driver.  After all, a gadget driver only knows how to manage
    a gadget, not how to manage a UDC.
    
    This patch simply removes the statements in the gadget core that touch
    udc->dev.driver.
    
    Fixes: 2ccea03a8f7e ("usb: gadget: introduce UDC Class")
    CC: <stable@vger.kernel.org>
    Reported-and-tested-by: syzbot+348b571beb5eeb70a582@syzkaller.appspotmail.com
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Link: https://lore.kernel.org/r/YiQgukfFFbBnwJ/9@rowland.harvard.edu
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e9b667a82cdcfe21d590344447d65daed52b353b
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Thu Mar 3 16:00:17 2022 -0500

    usb: usbtmc: Fix bug in pipe direction for control transfers
    
    The syzbot fuzzer reported a minor bug in the usbtmc driver:
    
    usb 5-1: BOGUS control dir, pipe 80001e80 doesn't match bRequestType 0
    WARNING: CPU: 0 PID: 3813 at drivers/usb/core/urb.c:412
    usb_submit_urb+0x13a5/0x1970 drivers/usb/core/urb.c:410
    Modules linked in:
    CPU: 0 PID: 3813 Comm: syz-executor122 Not tainted
    5.17.0-rc5-syzkaller-00306-g2293be58d6a1 #0
    ...
    Call Trace:
     <TASK>
     usb_start_wait_urb+0x113/0x530 drivers/usb/core/message.c:58
     usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
     usb_control_msg+0x2a5/0x4b0 drivers/usb/core/message.c:153
     usbtmc_ioctl_request drivers/usb/class/usbtmc.c:1947 [inline]
    
    The problem is that usbtmc_ioctl_request() uses usb_rcvctrlpipe() for
    all of its transfers, whether they are in or out.  It's easy to fix.
    
    CC: <stable@vger.kernel.org>
    Reported-and-tested-by: syzbot+a48e3d1a875240cab5de@syzkaller.appspotmail.com
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Link: https://lore.kernel.org/r/YiEsYTPEE6lOCOA5@rowland.harvard.edu
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 56e337f2cf1326323844927a04e9dbce9a244835
Author: Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Tue Mar 15 17:52:05 2022 +0100

    Revert "gpio: Revert regression in sysfs-gpio (gpiolib.c)"
    
    This reverts commit fc328a7d1fcce263db0b046917a66f3aa6e68719.
    
    This commit - while attempting to fix a regression - has caused a number
    of other problems. As the fallout from it is more significant than the
    initial problem itself, revert it for now before we find a correct
    solution.
    
    Link: https://lore.kernel.org/all/20220314192522.GA3031157@roeck-us.net/
    Link: https://lore.kernel.org/stable/20220314155509.552218-1-michael@walle.cc/
    Link: https://lore.kernel.org/all/20211217153555.9413-1-marcelo.jimenez@gmail.com/
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
    Reported-and-bisected-by: Guenter Roeck <linux@roeck-us.net>
    Reported-by: Michael Walle <michael@walle.cc>
    Cc: Thorsten Leemhuis <linux@leemhuis.info>
    Cc: Marcelo Roberto Jimenez <marcelo.jimenez@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 239071064732bc4a30308cbba11014aa1aab550a
Author: H. Nikolaus Schaller <hns@goldelico.com>
Date:   Tue Mar 8 13:56:06 2022 +0100

    partially Revert "usb: musb: Set the DT node on the child device"
    
    This reverts the omap2430 changes of
    
    commit cf081d009c44 ("usb: musb: Set the DT node on the child device")
    
    Since v5.17-rc1, musb is broken on the gta04 and openpandora devices
    (omap3530/dm3730). BeagleBone Black (am335x) seems to work.
    
    Symptoms of this bug are
    
    a) main symptom
    
    [   21.336517] using random host ethernet address
    [   21.341430] using host ethernet address: 32:70:05:18:ff:78
    [   21.341461] using self ethernet address: 46:10:3a:b3:af:d9
    [   21.358184] usb0: HOST MAC 32:70:05:18:ff:78
    [   21.376678] usb0: MAC 46:10:3a:b3:af:d9
    [   21.388305] using random self ethernet address
    [   21.393371] using random host ethernet address
    [   21.398162] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
    [   21.421081] g_ether gadget: g_ether ready
    [   21.492156] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   21.691345] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   21.803192] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   21.819427] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   22.124450] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   22.168518] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   22.179382] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.213592] musb-hdrc musb-hdrc.1.auto: pm runtime get failed in musb_gadget_queue
    [   23.221832] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.227905] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.239440] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.401000] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.407073] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.426361] musb-hdrc musb-hdrc.1.auto: Could not enable: -22
    [   23.734466] musb-hdrc musb-hdrc.1.auto: pm runtime get failed in musb_gadget_queue
    [   23.742462] musb-hdrc musb-hdrc.1.auto: pm runtime get failed in musb_gadget_queue
    [   23.750396] musb-hdrc musb-hdrc.1.auto: pm runtime get failed in musb_gadget_queue
    ... (repeats with high frequency)
    
    This stops if the USB cable is unplugged and restarts if it is plugged in again.
    
    b) also found in the log
    
    [    6.498107] ------------[ cut here ]------------
    [    6.502960] WARNING: CPU: 0 PID: 868 at arch/arm/mach-omap2/omap_hwmod.c:1885 _enable+0x50/0x234
    [    6.512207] omap_hwmod: usb_otg_hs: enabled state can only be entered from initialized, idle, or disabled state
    [    6.522766] Modules linked in: omap2430(+) bmp280_i2c bmp280 itg3200 at24 tsc2007 leds_tca6507 bma180 hmc5843_i2c hmc5843_core industrialio_triggered_buffer lis3lv02d_i2c kfifo_buf lis3lv02d phy_twl4030_usb snd_soc_omap_mcbsp snd_soc_ti_sdma musb_hdrc snd_soc_twl4030 gnss_sirf twl4030_vibra twl4030_madc twl4030_charger twl4030_pwrbutton gnss industrialio ehci_omap omapdrm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm drm_panel_orientation_quirks cec
    [    6.566436] CPU: 0 PID: 868 Comm: udevd Not tainted 5.16.0-rc5-letux+ #8251
    [    6.573730] Hardware name: Generic OMAP36xx (Flattened Device Tree)
    [    6.580322] [<c010ed30>] (unwind_backtrace) from [<c010a1d0>] (show_stack+0x10/0x14)
    [    6.588470] [<c010a1d0>] (show_stack) from [<c0897c14>] (dump_stack_lvl+0x40/0x4c)
    [    6.596405] [<c0897c14>] (dump_stack_lvl) from [<c0130cc4>] (__warn+0xb4/0xdc)
    [    6.604003] [<c0130cc4>] (__warn) from [<c0130d5c>] (warn_slowpath_fmt+0x70/0x9c)
    [    6.611846] [<c0130d5c>] (warn_slowpath_fmt) from [<c011f4d4>] (_enable+0x50/0x234)
    [    6.619903] [<c011f4d4>] (_enable) from [<c012081c>] (omap_hwmod_enable+0x28/0x40)
    [    6.627838] [<c012081c>] (omap_hwmod_enable) from [<c0120ff4>] (omap_device_enable+0x4c/0x78)
    [    6.636779] [<c0120ff4>] (omap_device_enable) from [<c0121030>] (_od_runtime_resume+0x10/0x3c)
    [    6.645812] [<c0121030>] (_od_runtime_resume) from [<c05c688c>] (__rpm_callback+0x3c/0xf4)
    [    6.654510] [<c05c688c>] (__rpm_callback) from [<c05c6994>] (rpm_callback+0x50/0x54)
    [    6.662628] [<c05c6994>] (rpm_callback) from [<c05c66b0>] (rpm_resume+0x448/0x4e4)
    [    6.670593] [<c05c66b0>] (rpm_resume) from [<c05c6784>] (__pm_runtime_resume+0x38/0x50)
    [    6.678985] [<c05c6784>] (__pm_runtime_resume) from [<bf14ab20>] (musb_init_controller+0x350/0xa5c [musb_hdrc])
    [    6.689727] [<bf14ab20>] (musb_init_controller [musb_hdrc]) from [<c05bccb8>] (platform_probe+0x58/0xa8)
    [    6.699737] [<c05bccb8>] (platform_probe) from [<c05badf0>] (really_probe+0x170/0x2fc)
    [    6.708068] [<c05badf0>] (really_probe) from [<c05bb040>] (__driver_probe_device+0xc4/0xd8)
    [    6.716827] [<c05bb040>] (__driver_probe_device) from [<c05bb084>] (driver_probe_device+0x30/0xac)
    [    6.726226] [<c05bb084>] (driver_probe_device) from [<c05bb3d0>] (__device_attach_driver+0x94/0xb4)
    [    6.735717] [<c05bb3d0>] (__device_attach_driver) from [<c05b93f8>] (bus_for_each_drv+0xa0/0xb4)
    [    6.744934] [<c05b93f8>] (bus_for_each_drv) from [<c05bb248>] (__device_attach+0xc0/0x134)
    [    6.753631] [<c05bb248>] (__device_attach) from [<c05b9fcc>] (bus_probe_device+0x28/0x80)
    [    6.762207] [<c05b9fcc>] (bus_probe_device) from [<c05b7e40>] (device_add+0x5fc/0x788)
    [    6.770507] [<c05b7e40>] (device_add) from [<c05bd240>] (platform_device_add+0x70/0x1bc)
    [    6.779022] [<c05bd240>] (platform_device_add) from [<bf177830>] (omap2430_probe+0x260/0x2d4 [omap2430])
    [    6.789001] [<bf177830>] (omap2430_probe [omap2430]) from [<c05bccb8>] (platform_probe+0x58/0xa8)
    [    6.798309] [<c05bccb8>] (platform_probe) from [<c05badf0>] (really_probe+0x170/0x2fc)
    [    6.806610] [<c05badf0>] (really_probe) from [<c05bb040>] (__driver_probe_device+0xc4/0xd8)
    [    6.815399] [<c05bb040>] (__driver_probe_device) from [<c05bb084>] (driver_probe_device+0x30/0xac)
    [    6.824798] [<c05bb084>] (driver_probe_device) from [<c05bb4b4>] (__driver_attach+0xc4/0xd8)
    [    6.833648] [<c05bb4b4>] (__driver_attach) from [<c05b9308>] (bus_for_each_dev+0x64/0xa0)
    [    6.842224] [<c05b9308>] (bus_for_each_dev) from [<c05ba248>] (bus_add_driver+0x148/0x1a4)
    [    6.850891] [<c05ba248>] (bus_add_driver) from [<c05bbd1c>] (driver_register+0xb4/0xf8)
    [    6.859313] [<c05bbd1c>] (driver_register) from [<c0101f54>] (do_one_initcall+0x90/0x1c8)
    [    6.867889] [<c0101f54>] (do_one_initcall) from [<c0893968>] (do_init_module+0x4c/0x204)
    [    6.876373] [<c0893968>] (do_init_module) from [<c01b4c30>] (load_module+0x13f0/0x1928)
    [    6.884796] [<c01b4c30>] (load_module) from [<c01b53a0>] (sys_finit_module+0xa0/0xc0)
    [    6.893005] [<c01b53a0>] (sys_finit_module) from [<c0100080>] (ret_fast_syscall+0x0/0x54)
    [    6.901580] Exception stack(0xc2807fa8 to 0xc2807ff0)
    [    6.906890] 7fa0:                   b6e517d4 00052068 00000006 b6e509f8 00000000 b6e5131c
    [    6.915466] 7fc0: b6e517d4 00052068 cd718000 0000017b 00020000 00037f78 00050048 00063368
    [    6.924011] 7fe0: bed8fef0 bed8fee0 b6e4ac4b b6f55a42
    [    6.929321] ---[ end trace d715ff121b58763c ]---
    
    c) git bisect result on testing for "musb-hdrc" in the console log:
    
    cf081d009c447647c6b36aced535ca427dbebe72 is the first bad commit
    commit cf081d009c447647c6b36aced535ca427dbebe72
    Author: Rob Herring <robh@kernel.org>
    Date:   Wed Dec 15 17:07:57 2021 -0600
    
      usb: musb: Set the DT node on the child device
    
      The musb glue drivers just copy the glue resources to the musb child device.
      Instead, set the musb child device's DT node pointer to the parent device's
      node so that platform_get_irq_byname() can find the resources in the DT.
      This removes the need for statically populating the IRQ resources from the
      DT which has been deprecated for some time.
    
      Signed-off-by: Rob Herring <robh@kernel.org>
      Link: https://lore.kernel.org/r/20211215230756.2009115-3-robh@kernel.org
      Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    
    drivers/usb/musb/am35x.c    | 2 ++
    drivers/usb/musb/da8xx.c    | 2 ++
    drivers/usb/musb/jz4740.c   | 1 +
    drivers/usb/musb/mediatek.c | 2 ++
    drivers/usb/musb/omap2430.c | 1 +
    drivers/usb/musb/ux500.c    | 1 +
    6 files changed, 9 insertions(+)
    
    Reverting this patch makes musb work again as before.
    
    Fixes: cf081d009c44 ("usb: musb: Set the DT node on the child device")
    Cc: Rob Herring <robh@kernel.org>
    Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
    Link: https://lore.kernel.org/r/f62f5fc11f9ecae7e57f3fd66939e051bd3b11fc.1646744166.git.hns@goldelico.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 65f3324f4b6fed78b8761c3b74615ecf0ffa81fa
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Mar 1 11:04:24 2022 +0300

    usb: gadget: rndis: prevent integer overflow in rndis_set_response()
    
    If "BufOffset" is very large the "BufOffset + 8" operation can have an
    integer overflow.
    
    Cc: stable@kernel.org
    Fixes: 38ea1eac7d88 ("usb: gadget: rndis: check size of RNDIS_MSG_SET command")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220301080424.GA17208@kili
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 0f74b29a4f53627376cf5a5fb7b0b3fa748a0b2b
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Mon Mar 14 09:34:48 2022 +0800

    atm: eni: Add check for dma_map_single
    
    As the potential failure of the dma_map_single(),
    it should be better to check it and return error
    if fails.
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0c48645a7f3988a624767d025fa3275ae24b6ca1
Author: Hannes Reinecke <hare@suse.de>
Date:   Tue Mar 15 10:14:36 2022 +0100

    nvmet: revert "nvmet: make discovery NQN configurable"
    
    Revert commit 626851e9225d ("nvmet: make discovery NQN configurable");
    the interface was deemed incorrect and will be replaced with a different
    one.
    
    Fixes: 626851e9225d ("nvmet: make discovery NQN configurable")
    Signed-off-by: Hannes Reinecke <hare@suse.de>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit c700525fcc06b05adfea78039de02628af79e07a
Author: Eric Dumazet <edumazet@google.com>
Date:   Sat Mar 12 15:29:58 2022 -0800

    net/packet: fix slab-out-of-bounds access in packet_recvmsg()
    
    syzbot found that when an AF_PACKET socket is using PACKET_COPY_THRESH
    and mmap operations, tpacket_rcv() is queueing skbs with
    garbage in skb->cb[], triggering a too big copy [1]
    
    Presumably, users of af_packet using mmap() already gets correct
    metadata from the mapped buffer, we can simply make sure
    to clear 12 bytes that might be copied to user space later.
    
    BUG: KASAN: stack-out-of-bounds in memcpy include/linux/fortify-string.h:225 [inline]
    BUG: KASAN: stack-out-of-bounds in packet_recvmsg+0x56c/0x1150 net/packet/af_packet.c:3489
    Write of size 165 at addr ffffc9000385fb78 by task syz-executor233/3631
    
    CPU: 0 PID: 3631 Comm: syz-executor233 Not tainted 5.17.0-rc7-syzkaller-02396-g0b3660695e80 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     print_address_description.constprop.0.cold+0xf/0x336 mm/kasan/report.c:255
     __kasan_report mm/kasan/report.c:442 [inline]
     kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
     check_region_inline mm/kasan/generic.c:183 [inline]
     kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189
     memcpy+0x39/0x60 mm/kasan/shadow.c:66
     memcpy include/linux/fortify-string.h:225 [inline]
     packet_recvmsg+0x56c/0x1150 net/packet/af_packet.c:3489
     sock_recvmsg_nosec net/socket.c:948 [inline]
     sock_recvmsg net/socket.c:966 [inline]
     sock_recvmsg net/socket.c:962 [inline]
     ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632
     ___sys_recvmsg+0x127/0x200 net/socket.c:2674
     __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7fdfd5954c29
    Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007ffcf8e71e48 EFLAGS: 00000246 ORIG_RAX: 000000000000002f
    RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fdfd5954c29
    RDX: 0000000000000000 RSI: 0000000020000500 RDI: 0000000000000005
    RBP: 0000000000000000 R08: 000000000000000d R09: 000000000000000d
    R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffcf8e71e60
    R13: 00000000000f4240 R14: 000000000000c1ff R15: 00007ffcf8e71e54
     </TASK>
    
    addr ffffc9000385fb78 is located in stack of task syz-executor233/3631 at offset 32 in frame:
     ____sys_recvmsg+0x0/0x600 include/linux/uio.h:246
    
    this frame has 1 object:
     [32, 160) 'addr'
    
    Memory state around the buggy address:
     ffffc9000385fa80: 00 04 f3 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00
     ffffc9000385fb00: 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00
    >ffffc9000385fb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f3
                                                                    ^
     ffffc9000385fc00: f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 f1
     ffffc9000385fc80: f1 f1 f1 00 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00
    ==================================================================
    
    Fixes: 0fb375fb9b93 ("[AF_PACKET]: Allow for > 8 byte hardware addresses.")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220312232958.3535620-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0f8946ae704ac6880c590beb91bc3a732595a28a
Author: Michael Walle <michael@walle.cc>
Date:   Sat Mar 12 23:41:40 2022 +0100

    net: mdio: mscc-miim: fix duplicate debugfs entry
    
    This driver can have up to two regmaps. If the second one is registered
    its debugfs entry will have the same name as the first one and the
    following error will be printed:
    
    [    3.833521] debugfs: Directory 'e200413c.mdio' with parent 'regmap' already present!
    
    Give the second regmap a name to avoid this.
    
    Fixes: a27a76282837 ("net: mdio: mscc-miim: convert to a regmap implementation")
    Signed-off-by: Michael Walle <michael@walle.cc>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220312224140.4173930-1-michael@walle.cc
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 69ad4ef868c1fc7609daa235dfa46d28ba7a3ba3
Author: Matt Lupfer <mlupfer@ddn.com>
Date:   Tue Mar 8 15:27:02 2022 +0000

    scsi: mpt3sas: Page fault in reply q processing
    
    A page fault was encountered in mpt3sas on a LUN reset error path:
    
    [  145.763216] mpt3sas_cm1: Task abort tm failed: handle(0x0002),timeout(30) tr_method(0x0) smid(3) msix_index(0)
    [  145.778932] scsi 1:0:0:0: task abort: FAILED scmd(0x0000000024ba29a2)
    [  145.817307] scsi 1:0:0:0: attempting device reset! scmd(0x0000000024ba29a2)
    [  145.827253] scsi 1:0:0:0: [sg1] tag#2 CDB: Receive Diagnostic 1c 01 01 ff fc 00
    [  145.837617] scsi target1:0:0: handle(0x0002), sas_address(0x500605b0000272b9), phy(0)
    [  145.848598] scsi target1:0:0: enclosure logical id(0x500605b0000272b8), slot(0)
    [  149.858378] mpt3sas_cm1: Poll ReplyDescriptor queues for completion of smid(0), task_type(0x05), handle(0x0002)
    [  149.875202] BUG: unable to handle page fault for address: 00000007fffc445d
    [  149.885617] #PF: supervisor read access in kernel mode
    [  149.894346] #PF: error_code(0x0000) - not-present page
    [  149.903123] PGD 0 P4D 0
    [  149.909387] Oops: 0000 [#1] PREEMPT SMP NOPTI
    [  149.917417] CPU: 24 PID: 3512 Comm: scsi_eh_1 Kdump: loaded Tainted: G S         O      5.10.89-altav-1 #1
    [  149.934327] Hardware name: DDN           200NVX2             /200NVX2-MB          , BIOS ATHG2.2.02.01 09/10/2021
    [  149.951871] RIP: 0010:_base_process_reply_queue+0x4b/0x900 [mpt3sas]
    [  149.961889] Code: 0f 84 22 02 00 00 8d 48 01 49 89 fd 48 8d 57 38 f0 0f b1 4f 38 0f 85 d8 01 00 00 49 8b 45 10 45 31 e4 41 8b 55 0c 48 8d 1c d0 <0f> b6 03 83 e0 0f 3c 0f 0f 85 a2 00 00 00 e9 e6 01 00 00 0f b7 ee
    [  149.991952] RSP: 0018:ffffc9000f1ebcb8 EFLAGS: 00010246
    [  150.000937] RAX: 0000000000000055 RBX: 00000007fffc445d RCX: 000000002548f071
    [  150.011841] RDX: 00000000ffff8881 RSI: 0000000000000001 RDI: ffff888125ed50d8
    [  150.022670] RBP: 0000000000000000 R08: 0000000000000000 R09: c0000000ffff7fff
    [  150.033445] R10: ffffc9000f1ebb68 R11: ffffc9000f1ebb60 R12: 0000000000000000
    [  150.044204] R13: ffff888125ed50d8 R14: 0000000000000080 R15: 34cdc00034cdea80
    [  150.054963] FS:  0000000000000000(0000) GS:ffff88dfaf200000(0000) knlGS:0000000000000000
    [  150.066715] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  150.076078] CR2: 00000007fffc445d CR3: 000000012448a006 CR4: 0000000000770ee0
    [  150.086887] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [  150.097670] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [  150.108323] PKRU: 55555554
    [  150.114690] Call Trace:
    [  150.120497]  ? printk+0x48/0x4a
    [  150.127049]  mpt3sas_scsih_issue_tm.cold.114+0x2e/0x2b3 [mpt3sas]
    [  150.136453]  mpt3sas_scsih_issue_locked_tm+0x86/0xb0 [mpt3sas]
    [  150.145759]  scsih_dev_reset+0xea/0x300 [mpt3sas]
    [  150.153891]  scsi_eh_ready_devs+0x541/0x9e0 [scsi_mod]
    [  150.162206]  ? __scsi_host_match+0x20/0x20 [scsi_mod]
    [  150.170406]  ? scsi_try_target_reset+0x90/0x90 [scsi_mod]
    [  150.178925]  ? blk_mq_tagset_busy_iter+0x45/0x60
    [  150.186638]  ? scsi_try_target_reset+0x90/0x90 [scsi_mod]
    [  150.195087]  scsi_error_handler+0x3a5/0x4a0 [scsi_mod]
    [  150.203206]  ? __schedule+0x1e9/0x610
    [  150.209783]  ? scsi_eh_get_sense+0x210/0x210 [scsi_mod]
    [  150.217924]  kthread+0x12e/0x150
    [  150.224041]  ? kthread_worker_fn+0x130/0x130
    [  150.231206]  ret_from_fork+0x1f/0x30
    
    This is caused by mpt3sas_base_sync_reply_irqs() using an invalid reply_q
    pointer outside of the list_for_each_entry() loop. At the end of the full
    list traversal the pointer is invalid.
    
    Move the _base_process_reply_queue() call inside of the loop.
    
    Link: https://lore.kernel.org/r/d625deae-a958-0ace-2ba3-0888dd0a415b@ddn.com
    Fixes: 711a923c14d9 ("scsi: mpt3sas: Postprocessing of target and LUN reset")
    Cc: stable@vger.kernel.org
    Acked-by: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
    Signed-off-by: Matt Lupfer <mlupfer@ddn.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 5600f6986628dde8881734090588474f54a540a8
Author: Pavel Skripkin <paskripkin@gmail.com>
Date:   Sun Mar 13 22:56:32 2022 -0700

    Input: aiptek - properly check endpoint type
    
    Syzbot reported warning in usb_submit_urb() which is caused by wrong
    endpoint type. There was a check for the number of endpoints, but not
    for the type of endpoint.
    
    Fix it by replacing old desc.bNumEndpoints check with
    usb_find_common_endpoints() helper for finding endpoints
    
    Fail log:
    
    usb 5-1: BOGUS urb xfer, pipe 1 != type 3
    WARNING: CPU: 2 PID: 48 at drivers/usb/core/urb.c:502 usb_submit_urb+0xed2/0x18a0 drivers/usb/core/urb.c:502
    Modules linked in:
    CPU: 2 PID: 48 Comm: kworker/2:2 Not tainted 5.17.0-rc6-syzkaller-00226-g07ebd38a0da2 #0
    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
    Workqueue: usb_hub_wq hub_event
    ...
    Call Trace:
     <TASK>
     aiptek_open+0xd5/0x130 drivers/input/tablet/aiptek.c:830
     input_open_device+0x1bb/0x320 drivers/input/input.c:629
     kbd_connect+0xfe/0x160 drivers/tty/vt/keyboard.c:1593
    
    Fixes: 8e20cf2bce12 ("Input: aiptek - fix crash on detecting device without endpoints")
    Reported-and-tested-by: syzbot+75cccf2b7da87fb6f84b@syzkaller.appspotmail.com
    Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
    Link: https://lore.kernel.org/r/20220308194328.26220-1-paskripkin@gmail.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 15d703921f0618a212567d06bca767f3f1c25681
Merge: 837d9e49402ea ed5f85d422901
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Mon Mar 14 15:51:10 2022 -0700

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    The following patchset contains Netfilter fixes for net coming late
    in the 5.17-rc process:
    
    1) Revert port remap to mitigate shadowing service ports, this is causing
       problems in existing setups and this mitigation can be achieved with
       explicit ruleset, eg.
    
            ... tcp sport < 16386 tcp dport >= 32768 masquerade random
    
      This patches provided a built-in policy similar to the one described above.
    
    2) Disable register tracking infrastructure in nf_tables. Florian reported
       two issues:
    
       - Existing expressions with no implemented .reduce interface
         that causes data-store on register should cancel the tracking.
       - Register clobbering might be possible storing data on registers that
         are larger than 32-bits.
    
       This might lead to generating incorrect ruleset bytecode. These two
       issues are scheduled to be addressed in the next release cycle.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf:
      netfilter: nf_tables: disable register tracking
      Revert "netfilter: conntrack: tag conntracks picked up in local out hook"
      Revert "netfilter: nat: force port remap to prevent shadowing well-known ports"
    ====================
    
    Link: https://lore.kernel.org/r/20220312220315.64531-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 837d9e49402eaf030db55a49f96fc51d73b4b441
Author: Kurt Cancemi <kurt@x64architecture.com>
Date:   Sat Mar 12 15:15:13 2022 -0500

    net: phy: marvell: Fix invalid comparison in the resume and suspend functions
    
    This bug resulted in only the current mode being resumed and suspended when
    the PHY supported both fiber and copper modes and when the PHY only supported
    copper mode the fiber mode would incorrectly be attempted to be resumed and
    suspended.
    
    Fixes: 3758be3dc162 ("Marvell phy: add functions to suspend and resume both interfaces: fiber and copper links.")
    Signed-off-by: Kurt Cancemi <kurt@x64architecture.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220312201512.326047-1-kurt@x64architecture.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit daaca3522a8e67c46e39ef09c1d542e866f85f3b
Author: Ming Lei <ming.lei@redhat.com>
Date:   Mon Mar 14 12:30:18 2022 +0800

    block: release rq qos structures for queue without disk
    
    blkcg_init_queue() may add rq qos structures to request queue, previously
    blk_cleanup_queue() calls rq_qos_exit() to release them, but commit
    8e141f9eb803 ("block: drain file system I/O on del_gendisk")
    moves rq_qos_exit() into del_gendisk(), so memory leak is caused
    because queues may not have disk, such as un-present scsi luns, nvme
    admin queue, ...
    
    Fixes the issue by adding rq_qos_exit() to blk_cleanup_queue() back.
    
    BTW, v5.18 won't need this patch any more since we move
    blkcg_init_queue()/blkcg_exit_queue() into disk allocation/release
    handler, and patches have been in for-5.18/block.
    
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: stable@vger.kernel.org
    Fixes: 8e141f9eb803 ("block: drain file system I/O on del_gendisk")
    Reported-by: syzbot+b42749a851a47a0f581b@syzkaller.appspotmail.com
    Signed-off-by: Ming Lei <ming.lei@redhat.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220314043018.177141-1-ming.lei@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 6665ca15746dc34606b5d79fae278a101a368437
Merge: 09688c0166e76 95932ab2ea07b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Mar 14 11:21:52 2022 -0700

    Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
    
    Pull virtio fix from Michael Tsirkin:
     "A last minute regression fix.
    
      I thought we did a lot of testing, but a regression still managed to
      sneak in. The fix seems trivial"
    
    * tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost:
      vhost: allow batching hint without size

commit 4db4075f92af2b28f415fc979ab626e6b37d67b6
Author: Sabrina Dubroca <sd@queasysnail.net>
Date:   Thu Mar 10 11:49:00 2022 +0100

    esp6: fix check on ipv6_skip_exthdr's return value
    
    Commit 5f9c55c8066b ("ipv6: check return value of ipv6_skip_exthdr")
    introduced an incorrect check, which leads to all ESP packets over
    either TCPv6 or UDPv6 encapsulation being dropped. In this particular
    case, offset is negative, since skb->data points to the ESP header in
    the following chain of headers, while skb->network_header points to
    the IPv6 header:
    
        IPv6 | ext | ... | ext | UDP | ESP | ...
    
    That doesn't seem to be a problem, especially considering that if we
    reach esp6_input_done2, we're guaranteed to have a full set of headers
    available (otherwise the packet would have been dropped earlier in the
    stack). However, it means that the return value will (intentionally)
    be negative. We can make the test more specific, as the expected
    return value of ipv6_skip_exthdr will be the (negated) size of either
    a UDP header, or a TCP header with possible options.
    
    In the future, we should probably either make ipv6_skip_exthdr
    explicitly accept negative offsets (and adjust its return value for
    error cases), or make ipv6_skip_exthdr only take non-negative
    offsets (and audit all callers).
    
    Fixes: 5f9c55c8066b ("ipv6: check return value of ipv6_skip_exthdr")
    Reported-by: Xiumei Mu <xmu@redhat.com>
    Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit e981bc74aefc6a177b50c16cfa7023599799cf74
Author: Claudiu Beznea <claudiu.beznea@microchip.com>
Date:   Fri Mar 11 13:17:16 2022 +0200

    net: dsa: microchip: add spi_device_id tables
    
    Add spi_device_id tables to avoid logs like "SPI driver ksz9477-switch
    has no spi_device_id".
    
    Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a680b1832ced3b5fa7c93484248fd221ea0d614b
Author: Brian Masney <bmasney@redhat.com>
Date:   Thu Mar 10 18:24:59 2022 -0500

    crypto: qcom-rng - ensure buffer for generate is completely filled
    
    The generate function in struct rng_alg expects that the destination
    buffer is completely filled if the function returns 0. qcom_rng_read()
    can run into a situation where the buffer is partially filled with
    randomness and the remaining part of the buffer is zeroed since
    qcom_rng_generate() doesn't check the return value. This issue can
    be reproduced by running the following from libkcapi:
    
        kcapi-rng -b 9000000 > OUTFILE
    
    The generated OUTFILE will have three huge sections that contain all
    zeros, and this is caused by the code where the test
    'val & PRNG_STATUS_DATA_AVAIL' fails.
    
    Let's fix this issue by ensuring that qcom_rng_read() always returns
    with a full buffer if the function returns success. Let's also have
    qcom_rng_generate() return the correct value.
    
    Here's some statistics from the ent project
    (https://www.fourmilab.ch/random/) that shows information about the
    quality of the generated numbers:
    
        $ ent -c qcom-random-before
        Value Char Occurrences Fraction
          0           606748   0.067416
          1            33104   0.003678
          2            33001   0.003667
        ...
        253   �        32883   0.003654
        254   �        33035   0.003671
        255   �        33239   0.003693
    
        Total:       9000000   1.000000
    
        Entropy = 7.811590 bits per byte.
    
        Optimum compression would reduce the size
        of this 9000000 byte file by 2 percent.
    
        Chi square distribution for 9000000 samples is 9329962.81, and
        randomly would exceed this value less than 0.01 percent of the
        times.
    
        Arithmetic mean value of data bytes is 119.3731 (127.5 = random).
        Monte Carlo value for Pi is 3.197293333 (error 1.77 percent).
        Serial correlation coefficient is 0.159130 (totally uncorrelated =
        0.0).
    
    Without this patch, the results of the chi-square test is 0.01%, and
    the numbers are certainly not random according to ent's project page.
    The results improve with this patch:
    
        $ ent -c qcom-random-after
        Value Char Occurrences Fraction
          0            35432   0.003937
          1            35127   0.003903
          2            35424   0.003936
        ...
        253   �        35201   0.003911
        254   �        34835   0.003871
        255   �        35368   0.003930
    
        Total:       9000000   1.000000
    
        Entropy = 7.999979 bits per byte.
    
        Optimum compression would reduce the size
        of this 9000000 byte file by 0 percent.
    
        Chi square distribution for 9000000 samples is 258.77, and randomly
        would exceed this value 42.24 percent of the times.
    
        Arithmetic mean value of data bytes is 127.5006 (127.5 = random).
        Monte Carlo value for Pi is 3.141277333 (error 0.01 percent).
        Serial correlation coefficient is 0.000468 (totally uncorrelated =
        0.0).
    
    This change was tested on a Nexus 5 phone (msm8974 SoC).
    
    Signed-off-by: Brian Masney <bmasney@redhat.com>
    Fixes: ceec5f5b5988 ("crypto: qcom-rng - Add Qcom prng driver")
    Cc: stable@vger.kernel.org # 4.19+
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Reviewed-by: Andrew Halaney <ahalaney@redhat.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

commit 09688c0166e76ce2fb85e86b9d99be8b0084cdf9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 13 13:23:37 2022 -0700

    Linux 5.17-rc8

commit 40ce1121c1d76daf9048a86e36c83e469281b9fd
Author: Jocelyn Falempe <jfalempe@redhat.com>
Date:   Tue Mar 8 18:43:21 2022 +0100

    drm/mgag200: Fix PLL setup for g200wb and g200ew
    
    commit f86c3ed55920 ("drm/mgag200: Split PLL setup into compute and
     update functions") introduced a regression for g200wb and g200ew.
    The PLLs are not set up properly, and VGA screen stays
    black, or displays "out of range" message.
    
    MGA1064_WB_PIX_PLLC_N/M/P was mistakenly replaced with
    MGA1064_PIX_PLLC_N/M/P which have different addresses.
    
    Patch tested on a Dell T310 with g200wb
    
    Fixes: f86c3ed55920 ("drm/mgag200: Split PLL setup into compute and update functions")
    Cc: stable@vger.kernel.org
    Signed-off-by: Jocelyn Falempe <jfalempe@redhat.com>
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220308174321.225606-1-jfalempe@redhat.com

commit f0e18b03fcafd8344539101f564ae358950ae892
Merge: aad611a868d16 08999b2489b4c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 13 10:36:38 2022 -0700

    Merge tag 'x86_urgent_for_v5.17_rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 fixes from Borislav Petkov:
    
     - Free shmem backing storage for SGX enclave pages when those are
       swapped back into EPC memory
    
     - Prevent do_int3() from being kprobed, to avoid recursion
    
     - Remap setup_data and setup_indirect structures properly when
       accessing their members
    
     - Correct the alternatives patching order for modules too
    
    * tag 'x86_urgent_for_v5.17_rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/sgx: Free backing memory after faulting the enclave page
      x86/traps: Mark do_int3() NOKPROBE_SYMBOL
      x86/boot: Add setup_indirect support in early_memremap_is_setup_data()
      x86/boot: Fix memremap of setup_indirect structures
      x86/module: Fix the paravirt vs alternative order

commit aad611a868d16cdc16a7d4a764cef955293e47e3
Merge: 1518a4f636b39 91c9923a473a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 12 10:29:25 2022 -0800

    Merge tag 'perf-tools-fixes-for-v5.17-2022-03-12' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tools fixes from Arnaldo Carvalho de Melo:
    
     - Fix event parser error for hybrid systems
    
     - Fix NULL check against wrong variable in 'perf bench' and in the
       parsing code
    
     - Update arm64 KVM headers from the kernel sources
    
     - Sync cpufeatures header with the kernel sources
    
    * tag 'perf-tools-fixes-for-v5.17-2022-03-12' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf parse: Fix event parser error for hybrid systems
      perf bench: Fix NULL check against wrong variable
      perf parse-events: Fix NULL check against wrong variable
      tools headers cpufeatures: Sync with the kernel sources
      tools kvm headers arm64: Update KVM headers from the kernel sources

commit 1518a4f636b39718788c81154420d7abc62fd839
Merge: 68453767131a5 3755d35ee1d24
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 12 10:22:43 2022 -0800

    Merge tag 'drm-fixes-2022-03-12' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm kconfig fix from Dave Airlie:
     "Thorsten pointed out this had fallen down the cracks and was in -next
      only, I've picked it out, fixed up it's Fixes: line.
    
       - fix regression in Kconfig"
    
    * tag 'drm-fixes-2022-03-12' of git://anongit.freedesktop.org/drm/drm:
      drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP

commit ed5f85d4229010235eab1e3d9acf6970d9304963
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sat Mar 12 11:05:46 2022 +0100

    netfilter: nf_tables: disable register tracking
    
    The register tracking infrastructure is incomplete, it might lead to
    generating incorrect ruleset bytecode, disable it by now given we are
    late in the release process.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 91c9923a473a694eb1c5c01ab778a77114969707
Author: Zhengjun Xing <zhengjun.xing@linux.intel.com>
Date:   Mon Mar 7 23:16:27 2022 +0800

    perf parse: Fix event parser error for hybrid systems
    
    This bug happened on hybrid systems when both cpu_core and cpu_atom
    have the same event name such as "UOPS_RETIRED.MS" while their event
    terms are different, then during perf stat, the event for cpu_atom
    will parse fail and then no output for cpu_atom.
    
    UOPS_RETIRED.MS -> cpu_core/period=0x1e8483,umask=0x4,event=0xc2,frontend=0x8/
    UOPS_RETIRED.MS -> cpu_atom/period=0x1e8483,umask=0x1,event=0xc2/
    
    It is because event terms in the "head" of parse_events_multi_pmu_add
    will be changed to event terms for cpu_core after parsing UOPS_RETIRED.MS
    for cpu_core, then when parsing the same event for cpu_atom, it still
    uses the event terms for cpu_core, but event terms for cpu_atom are
    different with cpu_core, the event parses for cpu_atom will fail. This
    patch fixes it, the event terms should be parsed from the original
    event.
    
    This patch can work for the hybrid systems that have the same event
    in more than 2 PMUs. It also can work in non-hybrid systems.
    
    Before:
    
      # perf stat -v  -e  UOPS_RETIRED.MS  -a sleep 1
    
      Using CPUID GenuineIntel-6-97-1
      UOPS_RETIRED.MS -> cpu_core/period=0x1e8483,umask=0x4,event=0xc2,frontend=0x8/
      Control descriptor is not initialized
      UOPS_RETIRED.MS: 2737845 16068518485 16068518485
    
     Performance counter stats for 'system wide':
    
             2,737,845      cpu_core/UOPS_RETIRED.MS/
    
           1.002553850 seconds time elapsed
    
    After:
    
      # perf stat -v  -e  UOPS_RETIRED.MS  -a sleep 1
    
      Using CPUID GenuineIntel-6-97-1
      UOPS_RETIRED.MS -> cpu_core/period=0x1e8483,umask=0x4,event=0xc2,frontend=0x8/
      UOPS_RETIRED.MS -> cpu_atom/period=0x1e8483,umask=0x1,event=0xc2/
      Control descriptor is not initialized
      UOPS_RETIRED.MS: 1977555 16076950711 16076950711
      UOPS_RETIRED.MS: 568684 8038694234 8038694234
    
     Performance counter stats for 'system wide':
    
             1,977,555      cpu_core/UOPS_RETIRED.MS/
               568,684      cpu_atom/UOPS_RETIRED.MS/
    
           1.004758259 seconds time elapsed
    
    Fixes: fb0811535e92c6c1 ("perf parse-events: Allow config on kernel PMU events")
    Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Zhengjun Xing <zhengjun.xing@linux.intel.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Alexander Shishkin <alexander.shishkin@intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20220307151627.30049-1-zhengjun.xing@linux.intel.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 073a15c3512f6b8d36c0c05992cf31e845f4dfe0
Author: Weiguo Li <liwg06@foxmail.com>
Date:   Fri Mar 11 21:07:16 2022 +0800

    perf bench: Fix NULL check against wrong variable
    
    We did a NULL check after "epollfdp = calloc(...)", but we checked
    "epollfd" instead of "epollfdp".
    
    Signed-off-by: Weiguo Li <liwg06@foxmail.com>
    Acked-by: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Davidlohr Bueso <dbueso@suse.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/tencent_B5D64530EB9C7DBB8D2C88A0C790F1489D0A@qq.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit a7a72631f62445e3671b7cab5ad01f856c1aa90d
Author: Weiguo Li <liwg06@foxmail.com>
Date:   Fri Mar 11 21:06:57 2022 +0800

    perf parse-events: Fix NULL check against wrong variable
    
    We did a null check after "tmp->symbol = strdup(...)", but we checked
    "list->symbol" other than "tmp->symbol".
    
    Reviewed-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Weiguo Li <liwg06@foxmail.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/tencent_DF39269807EC9425E24787E6DB632441A405@qq.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit ec9d50ace39925f7fd0302bf0fad640e2c9826ea
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Thu Jul 1 13:39:15 2021 -0300

    tools headers cpufeatures: Sync with the kernel sources
    
    To pick the changes from:
    
      d45476d983240937 ("x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE")
    
    Its just a comment fixup.
    
    This only causes these perf files to be rebuilt:
    
      CC       /tmp/build/perf/bench/mem-memcpy-x86-64-asm.o
      CC       /tmp/build/perf/bench/mem-memset-x86-64-asm.o
    
    And addresses this perf build warning:
    
      Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h'
      diff -u tools/arch/x86/include/asm/cpufeatures.h arch/x86/include/asm/cpufeatures.h
    
    Cc: Borislav Petkov <bp@suse.de>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lore.kernel.org/lkml/YiyiHatGaJQM7l/Y@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3ec94eeaff9ad58a76be2232068b4a2546b2f6bb
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Dec 21 12:53:44 2020 -0300

    tools kvm headers arm64: Update KVM headers from the kernel sources
    
    To pick the changes from:
    
      a5905d6af492ee6a ("KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated")
    
    That don't causes any changes in tooling (when built on x86), only
    addresses this perf build warning:
    
      Warning: Kernel ABI header at 'tools/arch/arm64/include/uapi/asm/kvm.h' differs from latest version at 'arch/arm64/include/uapi/asm/kvm.h'
      diff -u tools/arch/arm64/include/uapi/asm/kvm.h arch/arm64/include/uapi/asm/kvm.h
    
    Cc: James Morse <james.morse@arm.com>
    Link: https://lore.kernel.org/lkml/YiyhAK6sVPc83FaI@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3755d35ee1d2454b20b8a1e20d790e56201678a4
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Thu Feb 3 10:39:22 2022 +0100

    drm/panel: Select DRM_DP_HELPER for DRM_PANEL_EDP
    
    As reported in [1], DRM_PANEL_EDP depends on DRM_DP_HELPER. Select
    the option to fix the build failure. The error message is shown
    below.
    
      arm-linux-gnueabihf-ld: drivers/gpu/drm/panel/panel-edp.o: in function
        `panel_edp_probe': panel-edp.c:(.text+0xb74): undefined reference to
        `drm_panel_dp_aux_backlight'
      make[1]: *** [/builds/linux/Makefile:1222: vmlinux] Error 1
    
    The issue has been reported before, when DisplayPort helpers were
    hidden behind the option CONFIG_DRM_KMS_HELPER. [2]
    
    v2:
            * fix and expand commit description (Arnd)
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
    Fixes: 9d6366e743f3 ("drm: fb_helper: improve CONFIG_FB dependency")
    Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
    Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Reviewed-by: Lyude Paul <lyude@redhat.com>
    Acked-by: Sam Ravnborg <sam@ravnborg.org>
    Link: https://lore.kernel.org/dri-devel/CA+G9fYvN0NyaVkRQmA1O6rX7H8PPaZrUAD7=RDy33QY9rUU-9g@mail.gmail.com/ # [1]
    Link: https://lore.kernel.org/all/20211117062704.14671-1-rdunlap@infradead.org/ # [2]
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: Lyude Paul <lyude@redhat.com>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: dri-devel@lists.freedesktop.org
    Link: https://patchwork.freedesktop.org/patch/msgid/20220203093922.20754-1-tzimmermann@suse.de
    Signed-off-by: Dave Airlie <airlied@redhat.com>

commit 8e6ed963763fe21429eabfc76c69ce2b0163a3dd
Author: Jiyong Park <jiyong@google.com>
Date:   Fri Mar 11 11:00:16 2022 +0900

    vsock: each transport cycles only on its own sockets
    
    When iterating over sockets using vsock_for_each_connected_socket, make
    sure that a transport filters out sockets that don't belong to the
    transport.
    
    There actually was an issue caused by this; in a nested VM
    configuration, destroying the nested VM (which often involves the
    closing of /dev/vhost-vsock if there was h2g connections to the nested
    VM) kills not only the h2g connections, but also all existing g2h
    connections to the (outmost) host which are totally unrelated.
    
    Tested: Executed the following steps on Cuttlefish (Android running on a
    VM) [1]: (1) Enter into an `adb shell` session - to have a g2h
    connection inside the VM, (2) open and then close /dev/vhost-vsock by
    `exec 3< /dev/vhost-vsock && exec 3<&-`, (3) observe that the adb
    session is not reset.
    
    [1] https://android.googlesource.com/device/google/cuttlefish/
    
    Fixes: c0cfa2d8a788 ("vsock: add multi-transports support")
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
    Acked-by: Michael S. Tsirkin <mst@redhat.com>
    Signed-off-by: Jiyong Park <jiyong@google.com>
    Link: https://lore.kernel.org/r/20220311020017.1509316-1-jiyong@google.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 46b348fd2d81a341b15fb3f3f986204b038f5c42
Author: Niels Dossche <dossche.niels@gmail.com>
Date:   Fri Mar 11 00:27:08 2022 +0100

    alx: acquire mutex for alx_reinit in alx_change_mtu
    
    alx_reinit has a lockdep assertion that the alx->mtx mutex must be held.
    alx_reinit is called from two places: alx_reset and alx_change_mtu.
    alx_reset does acquire alx->mtx before calling alx_reinit.
    alx_change_mtu does not acquire this mutex, nor do its callers or any
    path towards alx_change_mtu.
    Acquire the mutex in alx_change_mtu.
    
    The issue was introduced when the fine-grained locking was introduced
    to the code to replace the RTNL. The same commit also introduced the
    lockdep assertion.
    
    Fixes: 4a5fe57e7751 ("alx: use fine-grained locking instead of RTNL")
    Signed-off-by: Niels Dossche <dossche.niels@gmail.com>
    Link: https://lore.kernel.org/r/20220310232707.44251-1-dossche.niels@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5e34af4142ffe68f01c8a9acae83300f8911e20c
Author: Tadeusz Struk <tadeusz.struk@linaro.org>
Date:   Thu Mar 10 15:25:38 2022 -0800

    net: ipv6: fix skb_over_panic in __ip6_append_data
    
    Syzbot found a kernel bug in the ipv6 stack:
    LINK: https://syzkaller.appspot.com/bug?id=205d6f11d72329ab8d62a610c44c5e7e25415580
    The reproducer triggers it by sending a crafted message via sendmmsg()
    call, which triggers skb_over_panic, and crashes the kernel:
    
    skbuff: skb_over_panic: text:ffffffff84647fb4 len:65575 put:65575
    head:ffff888109ff0000 data:ffff888109ff0088 tail:0x100af end:0xfec0
    dev:<NULL>
    
    Update the check that prevents an invalid packet with MTU equal
    to the fregment header size to eat up all the space for payload.
    
    The reproducer can be found here:
    LINK: https://syzkaller.appspot.com/text?tag=ReproC&x=1648c83fb00000
    
    Reported-by: syzbot+e223cf47ec8ae183f2a0@syzkaller.appspotmail.com
    Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
    Acked-by: Willem de Bruijn <willemb@google.com>
    Link: https://lore.kernel.org/r/20220310232538.1044947-1-tadeusz.struk@linaro.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 68453767131a5deec1e8f9ac92a9042f929e585d
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Fri Mar 11 11:49:12 2022 -0800

    ARM: Spectre-BHB: provide empty stub for non-config
    
    When CONFIG_GENERIC_CPU_VULNERABILITIES is not set, references
    to spectre_v2_update_state() cause a build error, so provide an
    empty stub for that function when the Kconfig option is not set.
    
    Fixes this build error:
    
      arm-linux-gnueabi-ld: arch/arm/mm/proc-v7-bugs.o: in function `cpu_v7_bugs_init':
      proc-v7-bugs.c:(.text+0x52): undefined reference to `spectre_v2_update_state'
      arm-linux-gnueabi-ld: proc-v7-bugs.c:(.text+0x82): undefined reference to `spectre_v2_update_state'
    
    Fixes: b9baf5c8c5c3 ("ARM: Spectre-BHB workaround")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Russell King <rmk+kernel@armlinux.org.uk>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: patches@armlinux.org.uk
    Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 77fe1ba90241c2af6f14d53988bf0cd6b9586699
Merge: 878409ecde7c8 0966d385830de
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 11 12:28:21 2022 -0800

    Merge tag 'riscv-for-linus-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V fixes from Palmer Dabbelt:
    
     - prevent users from enabling the alternatives framework (and thus
       errata handling) on XIP kernels, where runtime code patching does not
       function correctly.
    
     - properly detect offset overflow for AUIPC-based relocations in
       modules. This may manifest as modules calling arbitrary invalid
       addresses, depending on the address allocated when a module is
       loaded.
    
    * tag 'riscv-for-linus-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
      riscv: Fix auipc+jalr relocation range checks
      riscv: alternative only works on !XIP_KERNEL

commit 878409ecde7c89c9f3db76ff1ef9486c6ceed02c
Merge: 6c7cb60bff7ae 48015b632f770
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 11 11:50:36 2022 -0800

    Merge tag 'powerpc-5.17-6' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc fix from Michael Ellerman:
     "Fix STACKTRACE=n build, in particular for skiroot_defconfig"
    
    * tag 'powerpc-5.17-6' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc: Fix STACKTRACE=n build

commit 6c7cb60bff7aec24b834343ff433125f469886a3
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Fri Mar 11 17:13:17 2022 +0000

    ARM: fix Thumb2 regression with Spectre BHB
    
    When building for Thumb2, the vectors make use of a local label. Sadly,
    the Spectre BHB code also uses a local label with the same number which
    results in the Thumb2 reference pointing at the wrong place. Fix this
    by changing the number used for the Spectre BHB local label.
    
    Fixes: b9baf5c8c5c3 ("ARM: Spectre-BHB workaround")
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3977a3fb67703273fb3d6f8647bbca43b3471d4e
Merge: 93ce93587d364 1760fdb6fe9f7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 11 11:24:58 2022 -0800

    Merge tag 'mmc-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
    
    Pull MMC fixes from Ulf Hansson:
     "MMC core:
       - Restore (mostly) the busy polling for MMC_SEND_OP_COND
    
      MMC host:
       - meson-gx: Fix DMA usage of meson_mmc_post_req()"
    
    * tag 'mmc-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc:
      mmc: core: Restore (almost) the busy polling for MMC_SEND_OP_COND
      mmc: meson: Fix usage of meson_mmc_post_req()

commit 08999b2489b4c9b939d7483dbd03702ee4576d96
Author: Jarkko Sakkinen <jarkko@kernel.org>
Date:   Fri Mar 4 00:38:58 2022 +0200

    x86/sgx: Free backing memory after faulting the enclave page
    
    There is a limited amount of SGX memory (EPC) on each system.  When that
    memory is used up, SGX has its own swapping mechanism which is similar
    in concept but totally separate from the core mm/* code.  Instead of
    swapping to disk, SGX swaps from EPC to normal RAM.  That normal RAM
    comes from a shared memory pseudo-file and can itself be swapped by the
    core mm code.  There is a hierarchy like this:
    
            EPC <-> shmem <-> disk
    
    After data is swapped back in from shmem to EPC, the shmem backing
    storage needs to be freed.  Currently, the backing shmem is not freed.
    This effectively wastes the shmem while the enclave is running.  The
    memory is recovered when the enclave is destroyed and the backing
    storage freed.
    
    Sort this out by freeing memory with shmem_truncate_range(), as soon as
    a page is faulted back to the EPC.  In addition, free the memory for
    PCMD pages as soon as all PCMD's in a page have been marked as unused
    by zeroing its contents.
    
    Cc: stable@vger.kernel.org
    Fixes: 1728ab54b4be ("x86/sgx: Add a page reclaimer")
    Reported-by: Dave Hansen <dave.hansen@linux.intel.com>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
    Link: https://lkml.kernel.org/r/20220303223859.273187-1-jarkko@kernel.org

commit 93ce93587d36493f2f86921fa79921b3cba63fbb
Merge: 79b00034e9dcd 413a4a6b0b555
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 11 10:28:32 2022 -0800

    Merge branch 'davidh' (fixes from David Howells)
    
    Merge misc fixes from David Howells:
     "A set of patches for watch_queue filter issues noted by Jann. I've
      added in a cleanup patch from Christophe Jaillet to convert to using
      formal bitmap specifiers for the note allocation bitmap.
    
      Also two filesystem fixes (afs and cachefiles)"
    
    * emailed patches from David Howells <dhowells@redhat.com>:
      cachefiles: Fix volume coherency attribute
      afs: Fix potential thrashing in afs writeback
      watch_queue: Make comment about setting ->defunct more accurate
      watch_queue: Fix lack of barrier/sync/lock between post and read
      watch_queue: Free the alloc bitmap when the watch_queue is torn down
      watch_queue: Fix the alloc bitmap size to reflect notes allocated
      watch_queue: Use the bitmap API when applicable
      watch_queue: Fix to always request a pow-of-2 pipe ring size
      watch_queue: Fix to release page in ->release()
      watch_queue, pipe: Free watchqueue state after clearing pipe ring
      watch_queue: Fix filter limit check

commit 413a4a6b0b5553f2423d210f65e98c211b99c3f8
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 16:02:18 2022 +0000

    cachefiles: Fix volume coherency attribute
    
    A network filesystem may set coherency data on a volume cookie, and if
    given, cachefiles will store this in an xattr on the directory in the
    cache corresponding to the volume.
    
    The function that sets the xattr just stores the contents of the volume
    coherency buffer directly into the xattr, with nothing added; the
    checking function, on the other hand, has a cut'n'paste error whereby it
    tries to interpret the xattr contents as would be the xattr on an
    ordinary file (using the cachefiles_xattr struct).  This results in a
    failure to match the coherency data because the buffer ends up being
    shifted by 18 bytes.
    
    Fix this by defining a structure specifically for the volume xattr and
    making both the setting and checking functions use it.
    
    Since the volume coherency doesn't work if used, take the opportunity to
    insert a reserved field for future use, set it to 0 and check that it is
    0.  Log mismatch through the appropriate tracepoint.
    
    Note that this only affects cifs; 9p, afs, ceph and nfs don't use the
    volume coherency data at the moment.
    
    Fixes: 32e150037dce ("fscache, cachefiles: Store the volume coherency data")
    Reported-by: Rohith Surabattula <rohiths.msft@gmail.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: Steve French <smfrench@gmail.com>
    cc: linux-cifs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 173ce1ca47c489135b2799f70f550e1319ba36d8
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 15:58:21 2022 +0000

    afs: Fix potential thrashing in afs writeback
    
    In afs_writepages_region(), if the dirty page we find is undergoing
    writeback or write to cache, but the sync_mode is WB_SYNC_NONE, we go
    round the loop trying the same page again and again with no pausing or
    waiting unless and until another thread manages to clear the writeback
    and fscache flags.
    
    Fix this with three measures:
    
     (1) Advance start to after the page we found.
    
     (2) Break out of the loop and return if rescheduling is requested.
    
     (3) Arbitrarily give up after a maximum of 5 skips.
    
    Fixes: 31143d5d515e ("AFS: implement basic file write support")
    Reported-by: Marc Dionne <marc.dionne@auristor.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: Marc Dionne <marc.dionne@auristor.com>
    Acked-by: Marc Dionne <marc.dionne@auristor.com>
    Link: https://lore.kernel.org/r/164692725757.2097000.2060513769492301854.stgit@warthog.procyon.org.uk/ # v1
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a365a65f9ca1ceb9cf1ac29db4a4f51df7c507ad
Author: Li Huafei <lihuafei1@huawei.com>
Date:   Thu Mar 10 20:09:15 2022 +0800

    x86/traps: Mark do_int3() NOKPROBE_SYMBOL
    
    Since kprobe_int3_handler() is called in do_int3(), probing do_int3()
    can cause a breakpoint recursion and crash the kernel. Therefore,
    do_int3() should be marked as NOKPROBE_SYMBOL.
    
    Fixes: 21e28290b317 ("x86/traps: Split int3 handler up")
    Signed-off-by: Li Huafei <lihuafei1@huawei.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220310120915.63349-1-lihuafei1@huawei.com

commit 4edc0760412b0c4ecefc7e02cb855b310b122825
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:24:47 2022 +0000

    watch_queue: Make comment about setting ->defunct more accurate
    
    watch_queue_clear() has a comment stating that setting ->defunct to true
    preventing new additions as well as preventing notifications.  Whilst
    the latter is true, the first bit is superfluous since at the time this
    function is called, the pipe cannot be accessed to add new event
    sources.
    
    Remove the "new additions" bit from the comment.
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2ed147f015af2b48f41c6f0b6746aa9ea85c19f3
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:24:36 2022 +0000

    watch_queue: Fix lack of barrier/sync/lock between post and read
    
    There's nothing to synchronise post_one_notification() versus
    pipe_read().  Whilst posting is done under pipe->rd_wait.lock, the
    reader only takes pipe->mutex which cannot bar notification posting as
    that may need to be made from contexts that cannot sleep.
    
    Fix this by setting pipe->head with a barrier in post_one_notification()
    and reading pipe->head with a barrier in pipe_read().
    
    If that's not sufficient, the rd_wait.lock will need to be taken,
    possibly in a ->confirm() op so that it only applies to notifications.
    The lock would, however, have to be dropped before copy_page_to_iter()
    is invoked.
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7ea1a0124b6da246b5bc8c66cddaafd36acf3ecb
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:24:29 2022 +0000

    watch_queue: Free the alloc bitmap when the watch_queue is torn down
    
    Free the watch_queue note allocation bitmap when the watch_queue is
    destroyed.
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3b4c0371928c17af03e8397ac842346624017ce6
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:24:22 2022 +0000

    watch_queue: Fix the alloc bitmap size to reflect notes allocated
    
    Currently, watch_queue_set_size() sets the number of notes available in
    wqueue->nr_notes according to the number of notes allocated, but sets
    the size of the bitmap to the unrounded number of notes originally asked
    for.
    
    Fix this by setting the bitmap size to the number of notes we're
    actually going to make available (ie. the number allocated).
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a66bd7575b5f449ee0ba20cfd21c3bc5b04ef361
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Fri Mar 11 13:24:15 2022 +0000

    watch_queue: Use the bitmap API when applicable
    
    Use bitmap_alloc() to simplify code, improve the semantic and reduce
    some open-coded arithmetic in allocator arguments.
    
    Also change a memset(0xff) into an equivalent bitmap_fill() to keep
    consistency.
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 96a4d8912b28451cd62825fd7caa0e66e091d938
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:24:08 2022 +0000

    watch_queue: Fix to always request a pow-of-2 pipe ring size
    
    The pipe ring size must always be a power of 2 as the head and tail
    pointers are masked off by AND'ing with the size of the ring - 1.
    watch_queue_set_size(), however, lets you specify any number of notes
    between 1 and 511.  This number is passed through to pipe_resize_ring()
    without checking/forcing its alignment.
    
    Fix this by rounding the number of slots required up to the nearest
    power of two.  The request is meant to guarantee that at least that many
    notifications can be generated before the queue is full, so rounding
    down isn't an option, but, alternatively, it may be better to give an
    error if we aren't allowed to allocate that much ring space.
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c1853fbadcba1497f4907971e7107888e0714c81
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:23:46 2022 +0000

    watch_queue: Fix to release page in ->release()
    
    When a pipe ring descriptor points to a notification message, the
    refcount on the backing page is incremented by the generic get function,
    but the release function, which marks the bitmap, doesn't drop the page
    ref.
    
    Fix this by calling generic_pipe_buf_release() at the end of
    watch_queue_pipe_buf_release().
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit db8facfc9fafacefe8a835416a6b77c838088f8b
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:23:38 2022 +0000

    watch_queue, pipe: Free watchqueue state after clearing pipe ring
    
    In free_pipe_info(), free the watchqueue state after clearing the pipe
    ring as each pipe ring descriptor has a release function, and in the
    case of a notification message, this is watch_queue_pipe_buf_release()
    which tries to mark the allocation bitmap that was previously released.
    
    Fix this by moving the put of the pipe's ref on the watch queue to after
    the ring has been cleared.  We still need to call watch_queue_clear()
    before doing that to make sure that the pipe is disconnected from any
    notification sources first.
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c993ee0f9f81caf5767a50d1faeba39a0dc82af2
Author: David Howells <dhowells@redhat.com>
Date:   Fri Mar 11 13:23:31 2022 +0000

    watch_queue: Fix filter limit check
    
    In watch_queue_set_filter(), there are a couple of places where we check
    that the filter type value does not exceed what the type_filter bitmap
    can hold.  One place calculates the number of bits by:
    
       if (tf[i].type >= sizeof(wfilter->type_filter) * 8)
    
    which is fine, but the second does:
    
       if (tf[i].type >= sizeof(wfilter->type_filter) * BITS_PER_LONG)
    
    which is not.  This can lead to a couple of out-of-bounds writes due to
    a too-large type:
    
     (1) __set_bit() on wfilter->type_filter
     (2) Writing more elements in wfilter->filters[] than we allocated.
    
    Fix this by just using the proper WATCH_TYPE__NR instead, which is the
    number of types we actually know about.
    
    The bug may cause an oops looking something like:
    
      BUG: KASAN: slab-out-of-bounds in watch_queue_set_filter+0x659/0x740
      Write of size 4 at addr ffff88800d2c66bc by task watch_queue_oob/611
      ...
      Call Trace:
       <TASK>
       dump_stack_lvl+0x45/0x59
       print_address_description.constprop.0+0x1f/0x150
       ...
       kasan_report.cold+0x7f/0x11b
       ...
       watch_queue_set_filter+0x659/0x740
       ...
       __x64_sys_ioctl+0x127/0x190
       do_syscall_64+0x43/0x90
       entry_SYSCALL_64_after_hwframe+0x44/0xae
    
      Allocated by task 611:
       kasan_save_stack+0x1e/0x40
       __kasan_kmalloc+0x81/0xa0
       watch_queue_set_filter+0x23a/0x740
       __x64_sys_ioctl+0x127/0x190
       do_syscall_64+0x43/0x90
       entry_SYSCALL_64_after_hwframe+0x44/0xae
    
      The buggy address belongs to the object at ffff88800d2c66a0
       which belongs to the cache kmalloc-32 of size 32
      The buggy address is located 28 bytes inside of
       32-byte region [ffff88800d2c66a0, ffff88800d2c66c0)
    
    Fixes: c73be61cede5 ("pipe: Add general notification queue support")
    Reported-by: Jann Horn <jannh@google.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 79b00034e9dcd2b065c1665c8b42f62b6b80a9be
Merge: dda64ead7e82c 30eb13a26014c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 21:15:42 2022 -0800

    Merge tag 'drm-fixes-2022-03-11' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "As expected at this stage its pretty quiet, one sun4i mixer fix and
      one i915 display flicker fix:
    
      i915:
       - fix psr screen flicker
    
      sun4i:
       - mixer format fix"
    
    * tag 'drm-fixes-2022-03-11' of git://anongit.freedesktop.org/drm/drm:
      drm/sun4i: mixer: Fix P010 and P210 format numbers
      drm/i915/psr: Set "SF Partial Frame Enable" also on full update

commit 0966d385830de3470b7131db8e86c0c5bc9c52dc
Author: Emil Renner Berthing <kernel@esmil.dk>
Date:   Wed Feb 23 20:12:57 2022 +0100

    riscv: Fix auipc+jalr relocation range checks
    
    RISC-V can do PC-relative jumps with a 32bit range using the following
    two instructions:
    
            auipc   t0, imm20       ; t0 = PC + imm20 * 2^12
            jalr    ra, t0, imm12   ; ra = PC + 4, PC = t0 + imm12
    
    Crucially both the 20bit immediate imm20 and the 12bit immediate imm12
    are treated as two's-complement signed values. For this reason the
    immediates are usually calculated like this:
    
            imm20 = (offset + 0x800) >> 12
            imm12 = offset & 0xfff
    
    ..where offset is the signed offset from the auipc instruction. When
    the 11th bit of offset is 0 the addition of 0x800 doesn't change the top
    20 bits and imm12 considered positive. When the 11th bit is 1 the carry
    of the addition by 0x800 means imm20 is one higher, but since imm12 is
    then considered negative the two's complement representation means it
    all cancels out nicely.
    
    However, this addition by 0x800 (2^11) means an offset greater than or
    equal to 2^31 - 2^11 would overflow so imm20 is considered negative and
    result in a backwards jump. Similarly the lower range of offset is also
    moved down by 2^11 and hence the true 32bit range is
    
            [-2^31 - 2^11, 2^31 - 2^11)
    
    Signed-off-by: Emil Renner Berthing <kernel@esmil.dk>
    Fixes: e2c0cdfba7f6 ("RISC-V: User-facing API")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 30eb13a26014ca640b5eb57b6d010114084d5c92
Merge: 1f37299bb4e10 804f468853179
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 11 13:26:18 2022 +1000

    Merge tag 'drm-intel-fixes-2022-03-10' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    - Fix PSR2 when selective fetch is enabled and cursor at (-1, -1) (Jouni Högander)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/YinTFSFg++HvuFpZ@tursulin-mobl2

commit 1f37299bb4e10223f689b49723bac74b5c05c1a9
Merge: ffb217a13a2ea 9470c29faa91c
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 11 10:37:16 2022 +1000

    Merge tag 'drm-misc-fixes-2022-03-10' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/sun4i: Fix P010 and P210 format numbers
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YipS65Iuu7RMMlAa@linux-uq9g

commit dda64ead7e82caa47fafe0edc36067ee64df2203
Merge: 186d32bbf0344 78cbc6513217b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 17:23:08 2022 -0800

    Merge tag 'trace-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing fixes from Steven Rostedt:
     "Minor tracing fixes:
    
       - Fix unregistering the same event twice. A user could disable the
         same event that osnoise will disable on unregistering.
    
       - Inform RCU of a quiescent state in the osnoise testing thread.
    
       - Fix some kerneldoc comments"
    
    * tag 'trace-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      ftrace: Fix some W=1 warnings in kernel doc comments
      tracing/osnoise: Force quiescent states while tracing
      tracing/osnoise: Do not unregister events twice

commit 186d32bbf034417b40e2b4e773eeb8ef106c16c1
Merge: 3bcb6451cc96c e0ae713023a9d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 16:47:58 2022 -0800

    Merge tag 'net-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from bluetooth, and ipsec.
    
      Current release - regressions:
    
       - Bluetooth: fix unbalanced unlock in set_device_flags()
    
       - Bluetooth: fix not processing all entries on cmd_sync_work, make
         connect with qualcomm and intel adapters reliable
    
       - Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0"
    
       - xdp: xdp_mem_allocator can be NULL in trace_mem_connect()
    
       - eth: ice: fix race condition and deadlock during interface enslave
    
      Current release - new code bugs:
    
       - tipc: fix incorrect order of state message data sanity check
    
      Previous releases - regressions:
    
       - esp: fix possible buffer overflow in ESP transformation
    
       - dsa: unlock the rtnl_mutex when dsa_master_setup() fails
    
       - phy: meson-gxl: fix interrupt handling in forced mode
    
       - smsc95xx: ignore -ENODEV errors when device is unplugged
    
      Previous releases - always broken:
    
       - xfrm: fix tunnel mode fragmentation behavior
    
       - esp: fix inter address family tunneling on GSO
    
       - tipc: fix null-deref due to race when enabling bearer
    
       - sctp: fix kernel-infoleak for SCTP sockets
    
       - eth: macb: fix lost RX packet wakeup race in NAPI receive
    
       - eth: intel stop disabling VFs due to PF error responses
    
       - eth: bcmgenet: don't claim WOL when its not available"
    
    * tag 'net-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (50 commits)
      xdp: xdp_mem_allocator can be NULL in trace_mem_connect().
      ice: Fix race condition during interface enslave
      net: phy: meson-gxl: improve link-up behavior
      net: bcmgenet: Don't claim WOL when its not available
      net: arc_emac: Fix use after free in arc_mdio_probe()
      sctp: fix kernel-infoleak for SCTP sockets
      net: phy: correct spelling error of media in documentation
      net: phy: DP83822: clear MISR2 register to disable interrupts
      gianfar: ethtool: Fix refcount leak in gfar_get_ts_info
      selftests: pmtu.sh: Kill nettest processes launched in subshell.
      selftests: pmtu.sh: Kill tcpdump processes launched by subshell.
      NFC: port100: fix use-after-free in port100_send_complete
      net/mlx5e: SHAMPO, reduce TIR indication
      net/mlx5e: Lag, Only handle events from highest priority multipath entry
      net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
      net/mlx5: Fix a race on command flush flow
      net/mlx5: Fix size field in bufferx_reg struct
      ax25: Fix NULL pointer dereference in ax25_kill_by_device
      net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr
      net: ethernet: lpc_eth: Handle error for clk_enable
      ...

commit e0ae713023a9d09d6e1b454bdc8e8c1dd32c586e
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Wed Mar 9 23:13:45 2022 +0100

    xdp: xdp_mem_allocator can be NULL in trace_mem_connect().
    
    Since the commit mentioned below __xdp_reg_mem_model() can return a NULL
    pointer. This pointer is dereferenced in trace_mem_connect() which leads
    to segfault.
    
    The trace points (mem_connect + mem_disconnect) were put in place to
    pair connect/disconnect using the IDs. The ID is only assigned if
    __xdp_reg_mem_model() does not return NULL. That connect trace point is
    of no use if there is no ID.
    
    Skip that connect trace point if xdp_alloc is NULL.
    
    [ Toke Høiland-Jørgensen delivered the reasoning for skipping the trace
      point ]
    
    Fixes: 4a48ef70b93b8 ("xdp: Allow registering memory model without rxq reference")
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Link: https://lore.kernel.org/r/YikmmXsffE+QajTB@linutronix.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5cb1ebdbc4342b1c2ce89516e19808d64417bdbc
Author: Ivan Vecera <ivecera@redhat.com>
Date:   Thu Mar 10 18:16:41 2022 +0100

    ice: Fix race condition during interface enslave
    
    Commit 5dbbbd01cbba83 ("ice: Avoid RTNL lock when re-creating
    auxiliary device") changes a process of re-creation of aux device
    so ice_plug_aux_dev() is called from ice_service_task() context.
    This unfortunately opens a race window that can result in dead-lock
    when interface has left LAG and immediately enters LAG again.
    
    Reproducer:
    ```
    #!/bin/sh
    
    ip link add lag0 type bond mode 1 miimon 100
    ip link set lag0
    
    for n in {1..10}; do
            echo Cycle: $n
            ip link set ens7f0 master lag0
            sleep 1
            ip link set ens7f0 nomaster
    done
    ```
    
    This results in:
    [20976.208697] Workqueue: ice ice_service_task [ice]
    [20976.213422] Call Trace:
    [20976.215871]  __schedule+0x2d1/0x830
    [20976.219364]  schedule+0x35/0xa0
    [20976.222510]  schedule_preempt_disabled+0xa/0x10
    [20976.227043]  __mutex_lock.isra.7+0x310/0x420
    [20976.235071]  enum_all_gids_of_dev_cb+0x1c/0x100 [ib_core]
    [20976.251215]  ib_enum_roce_netdev+0xa4/0xe0 [ib_core]
    [20976.256192]  ib_cache_setup_one+0x33/0xa0 [ib_core]
    [20976.261079]  ib_register_device+0x40d/0x580 [ib_core]
    [20976.266139]  irdma_ib_register_device+0x129/0x250 [irdma]
    [20976.281409]  irdma_probe+0x2c1/0x360 [irdma]
    [20976.285691]  auxiliary_bus_probe+0x45/0x70
    [20976.289790]  really_probe+0x1f2/0x480
    [20976.298509]  driver_probe_device+0x49/0xc0
    [20976.302609]  bus_for_each_drv+0x79/0xc0
    [20976.306448]  __device_attach+0xdc/0x160
    [20976.310286]  bus_probe_device+0x9d/0xb0
    [20976.314128]  device_add+0x43c/0x890
    [20976.321287]  __auxiliary_device_add+0x43/0x60
    [20976.325644]  ice_plug_aux_dev+0xb2/0x100 [ice]
    [20976.330109]  ice_service_task+0xd0c/0xed0 [ice]
    [20976.342591]  process_one_work+0x1a7/0x360
    [20976.350536]  worker_thread+0x30/0x390
    [20976.358128]  kthread+0x10a/0x120
    [20976.365547]  ret_from_fork+0x1f/0x40
    ...
    [20976.438030] task:ip              state:D stack:    0 pid:213658 ppid:213627 flags:0x00004084
    [20976.446469] Call Trace:
    [20976.448921]  __schedule+0x2d1/0x830
    [20976.452414]  schedule+0x35/0xa0
    [20976.455559]  schedule_preempt_disabled+0xa/0x10
    [20976.460090]  __mutex_lock.isra.7+0x310/0x420
    [20976.464364]  device_del+0x36/0x3c0
    [20976.467772]  ice_unplug_aux_dev+0x1a/0x40 [ice]
    [20976.472313]  ice_lag_event_handler+0x2a2/0x520 [ice]
    [20976.477288]  notifier_call_chain+0x47/0x70
    [20976.481386]  __netdev_upper_dev_link+0x18b/0x280
    [20976.489845]  bond_enslave+0xe05/0x1790 [bonding]
    [20976.494475]  do_setlink+0x336/0xf50
    [20976.502517]  __rtnl_newlink+0x529/0x8b0
    [20976.543441]  rtnl_newlink+0x43/0x60
    [20976.546934]  rtnetlink_rcv_msg+0x2b1/0x360
    [20976.559238]  netlink_rcv_skb+0x4c/0x120
    [20976.563079]  netlink_unicast+0x196/0x230
    [20976.567005]  netlink_sendmsg+0x204/0x3d0
    [20976.570930]  sock_sendmsg+0x4c/0x50
    [20976.574423]  ____sys_sendmsg+0x1eb/0x250
    [20976.586807]  ___sys_sendmsg+0x7c/0xc0
    [20976.606353]  __sys_sendmsg+0x57/0xa0
    [20976.609930]  do_syscall_64+0x5b/0x1a0
    [20976.613598]  entry_SYSCALL_64_after_hwframe+0x65/0xca
    
    1. Command 'ip link ... set nomaster' causes that ice_plug_aux_dev()
       is called from ice_service_task() context, aux device is created
       and associated device->lock is taken.
    2. Command 'ip link ... set master...' calls ice's notifier under
       RTNL lock and that notifier calls ice_unplug_aux_dev(). That
       function tries to take aux device->lock but this is already taken
       by ice_plug_aux_dev() in step 1
    3. Later ice_plug_aux_dev() tries to take RTNL lock but this is already
       taken in step 2
    4. Dead-lock
    
    The patch fixes this issue by following changes:
    - Bit ICE_FLAG_PLUG_AUX_DEV is kept to be set during ice_plug_aux_dev()
      call in ice_service_task()
    - The bit is checked in ice_clear_rdma_cap() and only if it is not set
      then ice_unplug_aux_dev() is called. If it is set (in other words
      plugging of aux device was requested and ice_plug_aux_dev() is
      potentially running) then the function only clears the bit
    - Once ice_plug_aux_dev() call (in ice_service_task) is finished
      the bit ICE_FLAG_PLUG_AUX_DEV is cleared but it is also checked
      whether it was already cleared by ice_clear_rdma_cap(). If so then
      aux device is unplugged.
    
    Signed-off-by: Ivan Vecera <ivecera@redhat.com>
    Co-developed-by: Petr Oros <poros@redhat.com>
    Signed-off-by: Petr Oros <poros@redhat.com>
    Reviewed-by: Dave Ertman <david.m.ertman@intel.com>
    Link: https://lore.kernel.org/r/20220310171641.3863659-1-ivecera@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2c87c6f9fbddc5b84d67b2fa3f432fcac6d99d93
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date:   Wed Mar 9 22:04:47 2022 +0100

    net: phy: meson-gxl: improve link-up behavior
    
    Sometimes the link comes up but no data flows. This patch fixes
    this behavior. It's not clear what's the root cause of the issue.
    
    According to the tests one other link-up issue remains.
    In very rare cases the link isn't even reported as up.
    
    Fixes: 84c8f773d2dc ("net: phy: meson-gxl: remove the use of .ack_callback()")
    Tested-by: Erico Nunes <nunes.erico@gmail.com>
    Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
    Link: https://lore.kernel.org/r/e3473452-a1f9-efcf-5fdd-02b6f44c3fcd@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 00b022f8f876a3a036b0df7f971001bef6398605
Author: Jeremy Linton <jeremy.linton@arm.com>
Date:   Wed Mar 9 22:55:35 2022 -0600

    net: bcmgenet: Don't claim WOL when its not available
    
    Some of the bcmgenet platforms don't correctly support WOL, yet
    ethtool returns:
    
    "Supports Wake-on: gsf"
    
    which is false.
    
    Ideally if there isn't a wol_irq, or there is something else that
    keeps the device from being able to wakeup it should display:
    
    "Supports Wake-on: d"
    
    This patch checks whether the device can wakup, before using the
    hard-coded supported flags. This corrects the ethtool reporting, as
    well as the WOL configuration because ethtool verifies that the mode
    is supported before attempting it.
    
    Fixes: c51de7f3976b ("net: bcmgenet: add Wake-on-LAN support code")
    Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
    Tested-by: Peter Robinson <pbrobinson@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220310045535.224450-1-jeremy.linton@arm.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bc0e610a6eb0d46e4123fafdbe5e6141d9fff3be
Author: Jianglei Nie <niejianglei2021@163.com>
Date:   Wed Mar 9 20:18:24 2022 +0800

    net: arc_emac: Fix use after free in arc_mdio_probe()
    
    If bus->state is equal to MDIOBUS_ALLOCATED, mdiobus_free(bus) will free
    the "bus". But bus->name is still used in the next line, which will lead
    to a use after free.
    
    We can fix it by putting the name in a local variable and make the
    bus->name point to the rodata section "name",then use the name in the
    error message without referring to bus to avoid the uaf.
    
    Fixes: 95b5fc03c189 ("net: arc_emac: Make use of the helper function dev_err_probe()")
    Signed-off-by: Jianglei Nie <niejianglei2021@163.com>
    Link: https://lore.kernel.org/r/20220309121824.36529-1-niejianglei2021@163.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 633593a808980f82d251d0ca89730d8bb8b0220c
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Mar 9 16:11:45 2022 -0800

    sctp: fix kernel-infoleak for SCTP sockets
    
    syzbot reported a kernel infoleak [1] of 4 bytes.
    
    After analysis, it turned out r->idiag_expires is not initialized
    if inet_sctp_diag_fill() calls inet_diag_msg_common_fill()
    
    Make sure to clear idiag_timer/idiag_retrans/idiag_expires
    and let inet_diag_msg_sctpasoc_fill() fill them again if needed.
    
    [1]
    
    BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline]
    BUG: KMSAN: kernel-infoleak in copyout lib/iov_iter.c:154 [inline]
    BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x6ef/0x25a0 lib/iov_iter.c:668
     instrument_copy_to_user include/linux/instrumented.h:121 [inline]
     copyout lib/iov_iter.c:154 [inline]
     _copy_to_iter+0x6ef/0x25a0 lib/iov_iter.c:668
     copy_to_iter include/linux/uio.h:162 [inline]
     simple_copy_to_iter+0xf3/0x140 net/core/datagram.c:519
     __skb_datagram_iter+0x2d5/0x11b0 net/core/datagram.c:425
     skb_copy_datagram_iter+0xdc/0x270 net/core/datagram.c:533
     skb_copy_datagram_msg include/linux/skbuff.h:3696 [inline]
     netlink_recvmsg+0x669/0x1c80 net/netlink/af_netlink.c:1977
     sock_recvmsg_nosec net/socket.c:948 [inline]
     sock_recvmsg net/socket.c:966 [inline]
     __sys_recvfrom+0x795/0xa10 net/socket.c:2097
     __do_sys_recvfrom net/socket.c:2115 [inline]
     __se_sys_recvfrom net/socket.c:2111 [inline]
     __x64_sys_recvfrom+0x19d/0x210 net/socket.c:2111
     do_syscall_x64 arch/x86/entry/common.c:51 [inline]
     do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Uninit was created at:
     slab_post_alloc_hook mm/slab.h:737 [inline]
     slab_alloc_node mm/slub.c:3247 [inline]
     __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4975
     kmalloc_reserve net/core/skbuff.c:354 [inline]
     __alloc_skb+0x545/0xf90 net/core/skbuff.c:426
     alloc_skb include/linux/skbuff.h:1158 [inline]
     netlink_dump+0x3e5/0x16c0 net/netlink/af_netlink.c:2248
     __netlink_dump_start+0xcf8/0xe90 net/netlink/af_netlink.c:2373
     netlink_dump_start include/linux/netlink.h:254 [inline]
     inet_diag_handler_cmd+0x2e7/0x400 net/ipv4/inet_diag.c:1341
     sock_diag_rcv_msg+0x24a/0x620
     netlink_rcv_skb+0x40c/0x7e0 net/netlink/af_netlink.c:2494
     sock_diag_rcv+0x63/0x80 net/core/sock_diag.c:277
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x1093/0x1360 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x14d9/0x1720 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     sock_write_iter+0x594/0x690 net/socket.c:1061
     do_iter_readv_writev+0xa7f/0xc70
     do_iter_write+0x52c/0x1500 fs/read_write.c:851
     vfs_writev fs/read_write.c:924 [inline]
     do_writev+0x645/0xe00 fs/read_write.c:967
     __do_sys_writev fs/read_write.c:1040 [inline]
     __se_sys_writev fs/read_write.c:1037 [inline]
     __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037
     do_syscall_x64 arch/x86/entry/common.c:51 [inline]
     do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Bytes 68-71 of 2508 are uninitialized
    Memory access of size 2508 starts at ffff888114f9b000
    Data copied to user address 00007f7fe09ff2e0
    
    CPU: 1 PID: 3478 Comm: syz-executor306 Not tainted 5.17.0-rc4-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 8f840e47f190 ("sctp: add the sctp_diag.c file")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Cc: Vlad Yasevich <vyasevich@gmail.com>
    Cc: Neil Horman <nhorman@tuxdriver.com>
    Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
    Reviewed-by: Xin Long <lucien.xin@gmail.com>
    Link: https://lore.kernel.org/r/20220310001145.297371-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 26183cfe478c1d1d5cd1e3920a4b2c5b1980849d
Author: Colin Foster <colin.foster@in-advantage.com>
Date:   Tue Mar 8 22:25:44 2022 -0800

    net: phy: correct spelling error of media in documentation
    
    The header file incorrectly referenced "median-independant interface"
    instead of media. Correct this typo.
    
    Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
    Fixes: 4069a572d423 ("net: phy: Document core PHY structures")
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Link: https://lore.kernel.org/r/20220309062544.3073-1-colin.foster@in-advantage.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 55c4bf4d93bec773eb373f048ed8c6c53b96d8eb
Merge: 37c9d66c95564 99a2b9be077ae
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Mar 10 14:32:32 2022 -0800

    Merge tag 'mlx5-fixes-2022-03-09' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
    
    Saeed Mahameed says:
    
    ====================
    mlx5 fixes 2022-03-09
    
    This series provides bug fixes to mlx5 driver.
    
    * tag 'mlx5-fixes-2022-03-09' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux:
      net/mlx5e: SHAMPO, reduce TIR indication
      net/mlx5e: Lag, Only handle events from highest priority multipath entry
      net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
      net/mlx5: Fix a race on command flush flow
      net/mlx5: Fix size field in bufferx_reg struct
    ====================
    
    Link: https://lore.kernel.org/r/20220309201517.589132-1-saeed@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3bcb6451cc96ca38e50120a4f333ecf157245544
Merge: c30b5b8cfb72c 0a5aa8d161d19
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 12:56:36 2022 -0800

    Merge tag 'block-5.17-2022-03-10' of git://git.kernel.dk/linux-block
    
    Pull block fix from Jens Axboe:
     "Just a single fix for a regression that occured in this merge window"
    
    * tag 'block-5.17-2022-03-10' of git://git.kernel.dk/linux-block:
      block: fix blk_mq_attempt_bio_merge and rq_qos_throttle protection

commit c30b5b8cfb72cc83c10793588ce94471a4769409
Merge: 55b4083b44361 342e7c6ea5820
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 12:43:06 2022 -0800

    Merge tag 'staging-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
    
    Pull staging driver fixes from Greg KH:
     "Here are three small fixes for staging drivers for 5.17-rc8 or -final,
      which ever comes next.
    
      They resolve some reported problems:
    
       - rtl8723bs wifi driver deadlock fix for reported problem that is a
         revert of a previous patch. Also a documentation fix is added so
         that the same problem hopefully can not come back again.
    
       - gdm724x driver use-after-free fix for a reported problem.
    
      All of these have been in linux-next for a while with no reported
      problems"
    
    * tag 'staging-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
      staging: rtl8723bs: Improve the comment explaining the locking rules
      staging: rtl8723bs: Fix access-point mode deadlock
      staging: gdm724x: fix use after free in gdm_lte_rx()

commit 37c9d66c95564c85a001d8a035354f0220a1e1c3
Author: Clément Léger <clement.leger@bootlin.com>
Date:   Wed Mar 9 15:22:28 2022 +0100

    net: phy: DP83822: clear MISR2 register to disable interrupts
    
    MISR1 was cleared twice but the original author intention was probably
    to clear MISR1 & MISR2 to completely disable interrupts. Fix it to
    clear MISR2.
    
    Fixes: 87461f7a58ab ("net: phy: DP83822 initial driver submission")
    Signed-off-by: Clément Léger <clement.leger@bootlin.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220309142228.761153-1-clement.leger@bootlin.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2ac5b58e645c66932438bb021cb5b52097ce70b0
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Mar 10 01:53:13 2022 +0000

    gianfar: ethtool: Fix refcount leak in gfar_get_ts_info
    
    The of_find_compatible_node() function returns a node pointer with
    refcount incremented, We should use of_node_put() on it when done
    Add the missing of_node_put() to release the refcount.
    
    Fixes: 7349a74ea75c ("net: ethernet: gianfar_ethtool: get phc index through drvdata")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
    Reviewed-by: Claudiu Manoil <claudiu.manoil@nxp.com>
    Link: https://lore.kernel.org/r/20220310015313.14938-1-linmq006@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 55b4083b44361d833c93216a619d3b4e6d03a0c9
Merge: fe673d3f5bf1f 7e606edaa0a2e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 11:43:01 2022 -0800

    Merge tag 'soc-fixes-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC fixes from Arnd Bergmann:
     "Here is a third set of fixes for the soc tree, well within the
      expected set of changes.
    
      Maintainer list changes:
       - Krzysztof Kozlowski and Jisheng Zhang both have new email addresses
       - Broadcom iProc has a new git tree
    
      Regressions:
       - Robert Foss sends a revert for a Mediatek DPI bridge patch that
         caused an inadvertent break in the DT binding
       - mstar timers need to be included in Kconfig
    
      Devicetree fixes for:
       - Aspeed ast2600 spi pinmux
       - Tegra eDP panels on Nyan FHD
       - Tegra display IOMMU
       - Qualcomm sm8350 UFS clocks
       - minor DT changes for Marvell Armada, Qualcomm sdx65, Qualcomm
         sm8450, and Broadcom BCM2711"
    
    * tag 'soc-fixes-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
      arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
      MAINTAINERS: Update Jisheng's email address
      Revert "arm64: dts: mt8183: jacuzzi: Fix bus properties in anx's DSI endpoint"
      dt-bindings: drm/bridge: anx7625: Revert DPI support
      ARM: dts: aspeed: Fix AST2600 quad spi group
      MAINTAINERS: update Krzysztof Kozlowski's email
      MAINTAINERS: Update git tree for Broadcom iProc SoCs
      ARM: tegra: Move Nyan FHD panels to AUX bus
      arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias
      ARM: mstar: Select HAVE_ARM_ARCH_TIMER
      soc: mediatek: mt8192-mmsys: Fix dither to dsi0 path's input sel
      arm64: dts: mt8183: jacuzzi: Fix bus properties in anx's DSI endpoint
      ARM: boot: dts: bcm2711: Fix HVS register range
      arm64: dts: qcom: c630: disable crypto due to serror
      arm64: dts: qcom: sm8450: fix apps_smmu interrupts
      arm64: dts: qcom: sm8450: enable GCC_USB3_0_CLKREF_EN for usb
      arm64: dts: qcom: sm8350: Correct UFS symbol clocks
      arm64: tegra: Disable ISO SMMU for Tegra194
      Revert "dt-bindings: arm: qcom: Document SDX65 platform and boards"

commit fe673d3f5bf1fc50cdc4b754831db91a2ec10126
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 8 11:55:48 2022 -0800

    mm: gup: make fault_in_safe_writeable() use fixup_user_fault()
    
    Instead of using GUP, make fault_in_safe_writeable() actually force a
    'handle_mm_fault()' using the same fixup_user_fault() machinery that
    futexes already use.
    
    Using the GUP machinery meant that fault_in_safe_writeable() did not do
    everything that a real fault would do, ranging from not auto-expanding
    the stack segment, to not updating accessed or dirty flags in the page
    tables (GUP sets those flags on the pages themselves).
    
    The latter causes problems on architectures (like s390) that do accessed
    bit handling in software, which meant that fault_in_safe_writeable()
    didn't actually do all the fault handling it needed to, and trying to
    access the user address afterwards would still cause faults.
    
    Reported-and-tested-by: Andreas Gruenbacher <agruenba@redhat.com>
    Fixes: cdd591fc86e3 ("iov_iter: Introduce fault_in_iov_iter_writeable")
    Link: https://lore.kernel.org/all/CAHc6FU5nP+nziNGG0JAF1FUx-GV7kKFvM7aZuU_XD2_1v4vnvg@mail.gmail.com/
    Acked-by: David Hildenbrand <david@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c80ee64a8020ef1a6a92109798080786829b8994
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Fri Feb 11 00:49:43 2022 +0800

    riscv: alternative only works on !XIP_KERNEL
    
    The alternative mechanism needs runtime code patching, it can't work
    on XIP_KERNEL. And the errata workarounds are implemented via the
    alternative mechanism. So add !XIP_KERNEL dependency for alternative
    and erratas.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Fixes: 44c922572952 ("RISC-V: enable XIP")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 7e606edaa0a2e443fba9ae324efc1ba7834a0e7d
Merge: d986afd5a7b75 a1cc1697bb56c
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Mar 10 15:25:45 2022 +0100

    Merge tag 'mvebu-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu into arm/fixes
    
    mvebu fixes for 5.17 (part 2)
    
    Allow using old PCIe card on Armada 37xx
    
    * tag 'mvebu-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu:
      arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
    
    Link: https://lore.kernel.org/r/87bkydj4fn.fsf@BL-laptop
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit a1cc1697bb56cdf880ad4d17b79a39ef2c294bc9
Author: Pali Rohár <pali@kernel.org>
Date:   Thu Mar 10 11:39:23 2022 +0100

    arm64: dts: marvell: armada-37xx: Remap IO space to bus address 0x0
    
    Legacy and old PCI I/O based cards do not support 32-bit I/O addressing.
    
    Since commit 64f160e19e92 ("PCI: aardvark: Configure PCIe resources from
    'ranges' DT property") kernel can set different PCIe address on CPU and
    different on the bus for the one A37xx address mapping without any firmware
    support in case the bus address does not conflict with other A37xx mapping.
    
    So remap I/O space to the bus address 0x0 to enable support for old legacy
    I/O port based cards which have hardcoded I/O ports in low address space.
    
    Note that DDR on A37xx is mapped to bus address 0x0. And mapping of I/O
    space can be set to address 0x0 too because MEM space and I/O space are
    separate and so do not conflict.
    
    Remapping IO space on Turris Mox to different address is not possible to
    due bootloader bug.
    
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Reported-by: Arnd Bergmann <arnd@arndb.de>
    Fixes: 76f6386b25cc ("arm64: dts: marvell: Add Aardvark PCIe support for Armada 3700")
    Cc: stable@vger.kernel.org # 64f160e19e92 ("PCI: aardvark: Configure PCIe resources from 'ranges' DT property")
    Cc: stable@vger.kernel.org # 514ef1e62d65 ("arm64: dts: marvell: armada-37xx: Extend PCIe MEM space")
    Reviewed-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>

commit 95932ab2ea07b79cdb33121e2f40ccda9e6a73b5
Author: Jason Wang <jasowang@redhat.com>
Date:   Thu Mar 10 15:52:11 2022 +0800

    vhost: allow batching hint without size
    
    Commit e2ae38cf3d91 ("vhost: fix hung thread due to erroneous iotlb
    entries") tries to reject the IOTLB message whose size is zero. But
    the size is not necessarily meaningful, one example is the batching
    hint, so the commit breaks that.
    
    Fixing this be reject zero size message only if the message is used to
    update/invalidate the IOTLB.
    
    Fixes: e2ae38cf3d91 ("vhost: fix hung thread due to erroneous iotlb entries")
    Reported-by: Eli Cohen <elic@nvidia.com>
    Cc: Anirudh Rayabharam <mail@anirudhrb.com>
    Signed-off-by: Jason Wang <jasowang@redhat.com>
    Link: https://lore.kernel.org/r/20220310075211.4801-1-jasowang@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Tested-by: Eli Cohen <elic@nvidia.com>

commit 1db333d9a51f3459fba1bcaa564d95befe79f0b3
Merge: b1a384d2cbccb 1a4e53d2fc4f6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 04:15:09 2022 -0800

    Merge tag 'spi-fix-v5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
    
    Pull spi fix from Mark Brown:
     "One fix for type conversion issues when working out maximum
      scatter/gather segment sizes.
    
      It caused problems for some systems where the limits overflow
      due to the type conversion"
    
    * tag 'spi-fix-v5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi:
      spi: Fix invalid sgs value

commit b1a384d2cbccb1eb3f84765020d25e2c1929706e
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Thu Mar 10 10:22:14 2022 +0000

    ARM: fix build warning in proc-v7-bugs.c
    
    The kernel test robot discovered that building without
    HARDEN_BRANCH_PREDICTOR issues a warning due to a missing
    argument to pr_info().
    
    Add the missing argument.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 9dd78194a372 ("ARM: report Spectre v2 status through sysfs")
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit cef06913a0af21e161a6179a17d3f5fa7132ba46
Merge: 9c674947f6112 55d01c98a88b3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 10 03:55:33 2022 -0800

    Merge tag 'gpio-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio fixes from Bartosz Golaszewski:
    
     - fix a probe failure for Tegra241 GPIO controller in gpio-tegra186
    
     - revert changes that caused a regression in the sysfs user-space
       interface
    
     - correct the debounce time conversion in GPIO ACPI
    
     - statify a struct in gpio-sim and fix a typo
    
     - update registers in correct order (hardware quirk) in gpio-ts4900
    
    * tag 'gpio-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:
      gpio: sim: fix a typo
      gpio: ts4900: Do not set DAT and OE together
      gpio: sim: Declare gpio_sim_hog_config_item_ops static
      gpiolib: acpi: Convert ACPI value of debounce to microseconds
      gpio: Revert regression in sysfs-gpio (gpiolib.c)
      gpio: tegra186: Add IRQ per bank for Tegra241

commit 55d01c98a88b346e217eaa931b32e7baea905c9a
Author: Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Tue Mar 8 09:44:54 2022 +0100

    gpio: sim: fix a typo
    
    Just noticed this when applying Andy's patch. s/childred/children/
    
    Fixes: cb8c474e79be ("gpio: sim: new testing module")
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
    Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

commit 03fe003547975680fdb9ff5ab0e41cb68276c4f2
Author: Mark Featherston <mark@embeddedTS.com>
Date:   Wed Mar 9 17:16:16 2022 -0800

    gpio: ts4900: Do not set DAT and OE together
    
    This works around an issue with the hardware where both OE and
    DAT are exposed in the same register. If both are updated
    simultaneously, the harware makes no guarantees that OE or DAT
    will actually change in any given order and may result in a
    glitch of a few ns on a GPIO pin when changing direction and value
    in a single write.
    
    Setting direction to input now only affects OE bit. Setting
    direction to output updates DAT first, then OE.
    
    Fixes: 9c6686322d74 ("gpio: add Technologic I2C-FPGA gpio support")
    Signed-off-by: Mark Featherston <mark@embeddedTS.com>
    Signed-off-by: Kris Bahnsen <kris@embeddedTS.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 9a564bccb78a76740ea9d75a259942df8143d02c
Author: Haimin Zhang <tcs_kernel@tencent.com>
Date:   Tue Mar 8 11:20:28 2022 +0800

    af_key: add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register
    
    Add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register
    to initialize the buffer of supp_skb to fix a kernel-info-leak issue.
    1) Function pfkey_register calls compose_sadb_supported to request
    a sk_buff. 2) compose_sadb_supported calls alloc_sbk to allocate
    a sk_buff, but it doesn't zero it. 3) If auth_len is greater 0, then
    compose_sadb_supported treats the memory as a struct sadb_supported and
    begins to initialize. But it just initializes the field sadb_supported_len
    and field sadb_supported_exttype without field sadb_supported_reserved.
    
    Reported-by: TCS Robot <tcs_robot@tencent.com>
    Signed-off-by: Haimin Zhang <tcs_kernel@tencent.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 9c674947f6112e4d68715e9f363c6698c2b0eead
Merge: b5521fe9a9336 aa091a6a91df3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 9 20:58:29 2022 -0800

    Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
    
    Pull clk fixes from Stephen Boyd:
     "One more small batch of clk driver fixes:
    
       - A fix for the Qualcomm GDSC power domain delays that avoids black
         screens at boot on some more recent SoCs that use a different delay
         than the hard-coded delays in the driver.
    
       - A build fix LAN966X clk driver that let it be built on
         architectures that didn't have IOMEM"
    
    * tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux:
      clk: lan966x: Fix linking error
      clk: qcom: dispcc: Update the transition delay for MDSS GDSC
      clk: qcom: gdsc: Add support to update GDSC transition delay

commit b5521fe9a9336caa1caa2db126f1d3ba1bc8303e
Merge: 3bf7edc84a9eb 66e3531b33ee5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 9 20:44:17 2022 -0800

    Merge tag 'xsa396-5.17-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
    
    Pull xen fixes from Juergen Gross:
     "Several Linux PV device frontends are using the grant table interfaces
      for removing access rights of the backends in ways being subject to
      race conditions, resulting in potential data leaks, data corruption by
      malicious backends, and denial of service triggered by malicious
      backends:
    
       - blkfront, netfront, scsifront and the gntalloc driver are testing
         whether a grant reference is still in use. If this is not the case,
         they assume that a following removal of the granted access will
         always succeed, which is not true in case the backend has mapped
         the granted page between those two operations.
    
         As a result the backend can keep access to the memory page of the
         guest no matter how the page will be used after the frontend I/O
         has finished. The xenbus driver has a similar problem, as it
         doesn't check the success of removing the granted access of a
         shared ring buffer.
    
       - blkfront, netfront, scsifront, usbfront, dmabuf, xenbus, 9p,
         kbdfront, and pvcalls are using a functionality to delay freeing a
         grant reference until it is no longer in use, but the freeing of
         the related data page is not synchronized with dropping the granted
         access.
    
         As a result the backend can keep access to the memory page even
         after it has been freed and then re-used for a different purpose.
    
       - netfront will fail a BUG_ON() assertion if it fails to revoke
         access in the rx path.
    
         This will result in a Denial of Service (DoS) situation of the
         guest which can be triggered by the backend"
    
    * tag 'xsa396-5.17-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
      xen/netfront: react properly to failing gnttab_end_foreign_access_ref()
      xen/gnttab: fix gnttab_end_foreign_access() without page specified
      xen/pvcalls: use alloc/free_pages_exact()
      xen/9p: use alloc/free_pages_exact()
      xen/usb: don't use gnttab_end_foreign_access() in xenhcd_gnttab_done()
      xen: remove gnttab_query_foreign_access()
      xen/gntalloc: don't use gnttab_query_foreign_access()
      xen/scsifront: don't use gnttab_query_foreign_access() for mapped status
      xen/netfront: don't use gnttab_query_foreign_access() for mapped status
      xen/blkfront: don't use gnttab_query_foreign_access() for mapped status
      xen/grant-table: add gnttab_try_end_foreign_access()
      xen/xenbus: don't let xenbus_grant_ring() remove grants in error case

commit 5f147476057832b8f87461ff6da35b5d2e1c2c29
Merge: f80cfe2f26581 94a4a4fe4c696
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Mar 9 20:23:37 2022 -0800

    Merge branch 'selftests-pmtu-sh-fix-cleanup-of-processes-launched-in-subshell'
    
    Guillaume Nault says:
    
    ====================
    selftests: pmtu.sh: Fix cleanup of processes launched in subshell.
    
    Depending on the options used, pmtu.sh may launch tcpdump and nettest
    processes in the background. However it fails to clean them up after
    the tests complete.
    
    Patch 1 allows the cleanup() function to read the list of PIDs launched
    by the tests.
    Patch 2 fixes the way the nettest PIDs are retrieved.
    ====================
    
    Link: https://lore.kernel.org/r/cover.1646776561.git.gnault@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 94a4a4fe4c696413932eed8bdec46574de9576b8
Author: Guillaume Nault <gnault@redhat.com>
Date:   Tue Mar 8 23:15:03 2022 +0100

    selftests: pmtu.sh: Kill nettest processes launched in subshell.
    
    When using "run_cmd <command> &", then "$!" refers to the PID of the
    subshell used to run <command>, not the command itself. Therefore
    nettest_pids actually doesn't contain the list of the nettest commands
    running in the background. So cleanup() can't kill them and the nettest
    processes run until completion (fortunately they have a 5s timeout).
    
    Fix this by defining a new command for running processes in the
    background, for which "$!" really refers to the PID of the command run.
    
    Also, double quote variables on the modified lines, to avoid shellcheck
    warnings.
    
    Fixes: ece1278a9b81 ("selftests: net: add ESP-in-UDP PMTU test")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 18dfc667550fe9c032a6dcc3402b50e691e18029
Author: Guillaume Nault <gnault@redhat.com>
Date:   Tue Mar 8 23:15:00 2022 +0100

    selftests: pmtu.sh: Kill tcpdump processes launched by subshell.
    
    The cleanup() function takes care of killing processes launched by the
    test functions. It relies on variables like ${tcpdump_pids} to get the
    relevant PIDs. But tests are run in their own subshell, so updated
    *_pids values are invisible to other shells. Therefore cleanup() never
    sees any process to kill:
    
    $ ./tools/testing/selftests/net/pmtu.sh -t pmtu_ipv4_exception
    TEST: ipv4: PMTU exceptions                                         [ OK ]
    TEST: ipv4: PMTU exceptions - nexthop objects                       [ OK ]
    
    $ pgrep -af tcpdump
    6084 tcpdump -s 0 -i veth_A-R1 -w pmtu_ipv4_exception_veth_A-R1.pcap
    6085 tcpdump -s 0 -i veth_R1-A -w pmtu_ipv4_exception_veth_R1-A.pcap
    6086 tcpdump -s 0 -i veth_R1-B -w pmtu_ipv4_exception_veth_R1-B.pcap
    6087 tcpdump -s 0 -i veth_B-R1 -w pmtu_ipv4_exception_veth_B-R1.pcap
    6088 tcpdump -s 0 -i veth_A-R2 -w pmtu_ipv4_exception_veth_A-R2.pcap
    6089 tcpdump -s 0 -i veth_R2-A -w pmtu_ipv4_exception_veth_R2-A.pcap
    6090 tcpdump -s 0 -i veth_R2-B -w pmtu_ipv4_exception_veth_R2-B.pcap
    6091 tcpdump -s 0 -i veth_B-R2 -w pmtu_ipv4_exception_veth_B-R2.pcap
    6228 tcpdump -s 0 -i veth_A-R1 -w pmtu_ipv4_exception_veth_A-R1.pcap
    6229 tcpdump -s 0 -i veth_R1-A -w pmtu_ipv4_exception_veth_R1-A.pcap
    6230 tcpdump -s 0 -i veth_R1-B -w pmtu_ipv4_exception_veth_R1-B.pcap
    6231 tcpdump -s 0 -i veth_B-R1 -w pmtu_ipv4_exception_veth_B-R1.pcap
    6232 tcpdump -s 0 -i veth_A-R2 -w pmtu_ipv4_exception_veth_A-R2.pcap
    6233 tcpdump -s 0 -i veth_R2-A -w pmtu_ipv4_exception_veth_R2-A.pcap
    6234 tcpdump -s 0 -i veth_R2-B -w pmtu_ipv4_exception_veth_R2-B.pcap
    6235 tcpdump -s 0 -i veth_B-R2 -w pmtu_ipv4_exception_veth_B-R2.pcap
    
    Fix this by running cleanup() in the context of the test subshell.
    Now that each test cleans the environment after completion, there's no
    need for calling cleanup() again when the next test starts. So let's
    drop it from the setup() function. This is okay because cleanup() is
    also called when pmtu.sh starts, so even the first test starts in a
    clean environment.
    
    Also, use tcpdump's immediate mode. Otherwise it might not have time to
    process buffered packets, resulting in missing packets or even empty
    pcap files for short tests.
    
    Note: PAUSE_ON_FAIL is still evaluated before cleanup(), so one can
    still inspect the test environment upon failure when using -p.
    
    Fixes: a92a0a7b8e7c ("selftests: pmtu: Simplify cleanup and namespace names")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f80cfe2f26581f188429c12bd937eb905ad3ac7b
Author: Pavel Skripkin <paskripkin@gmail.com>
Date:   Tue Mar 8 21:50:07 2022 +0300

    NFC: port100: fix use-after-free in port100_send_complete
    
    Syzbot reported UAF in port100_send_complete(). The root case is in
    missing usb_kill_urb() calls on error handling path of ->probe function.
    
    port100_send_complete() accesses devm allocated memory which will be
    freed on probe failure. We should kill this urbs before returning an
    error from probe function to prevent reported use-after-free
    
    Fail log:
    
    BUG: KASAN: use-after-free in port100_send_complete+0x16e/0x1a0 drivers/nfc/port100.c:935
    Read of size 1 at addr ffff88801bb59540 by task ksoftirqd/2/26
    ...
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     print_address_description.constprop.0.cold+0x8d/0x303 mm/kasan/report.c:255
     __kasan_report mm/kasan/report.c:442 [inline]
     kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
     port100_send_complete+0x16e/0x1a0 drivers/nfc/port100.c:935
     __usb_hcd_giveback_urb+0x2b0/0x5c0 drivers/usb/core/hcd.c:1670
    
    ...
    
    Allocated by task 1255:
     kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38
     kasan_set_track mm/kasan/common.c:45 [inline]
     set_alloc_info mm/kasan/common.c:436 [inline]
     ____kasan_kmalloc mm/kasan/common.c:515 [inline]
     ____kasan_kmalloc mm/kasan/common.c:474 [inline]
     __kasan_kmalloc+0xa6/0xd0 mm/kasan/common.c:524
     alloc_dr drivers/base/devres.c:116 [inline]
     devm_kmalloc+0x96/0x1d0 drivers/base/devres.c:823
     devm_kzalloc include/linux/device.h:209 [inline]
     port100_probe+0x8a/0x1320 drivers/nfc/port100.c:1502
    
    Freed by task 1255:
     kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38
     kasan_set_track+0x21/0x30 mm/kasan/common.c:45
     kasan_set_free_info+0x20/0x30 mm/kasan/generic.c:370
     ____kasan_slab_free mm/kasan/common.c:366 [inline]
     ____kasan_slab_free+0xff/0x140 mm/kasan/common.c:328
     kasan_slab_free include/linux/kasan.h:236 [inline]
     __cache_free mm/slab.c:3437 [inline]
     kfree+0xf8/0x2b0 mm/slab.c:3794
     release_nodes+0x112/0x1a0 drivers/base/devres.c:501
     devres_release_all+0x114/0x190 drivers/base/devres.c:530
     really_probe+0x626/0xcc0 drivers/base/dd.c:670
    
    Reported-and-tested-by: syzbot+16bcb127fb73baeecb14@syzkaller.appspotmail.com
    Fixes: 0347a6ab300a ("NFC: port100: Commands mechanism implementation")
    Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220308185007.6987-1-paskripkin@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3bf7edc84a9eb4007dd9a0cb8878a7e1d5ec6a3b
Merge: 36168e387fa7d 52c9f93a9c482
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 9 14:30:09 2022 -0800

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 build fix from Catalin Marinas:
     "Fix kernel build with clang LTO after the inclusion of the Spectre BHB
      arm64 mitigations"
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: Do not include __READ_ONCE() block in assembly files

commit 36168e387fa7d0f1fe0cd5cf76c8cea7aee714fa
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Mar 9 15:07:27 2022 -0700

    ARM: Do not use NOCROSSREFS directive with ld.lld
    
    ld.lld does not support the NOCROSSREFS directive at the moment, which
    breaks the build after commit b9baf5c8c5c3 ("ARM: Spectre-BHB
    workaround"):
    
      ld.lld: error: ./arch/arm/kernel/vmlinux.lds:34: AT expected, but got NOCROSSREFS
    
    Support for this directive will eventually be implemented, at which
    point a version check can be added. To avoid breaking the build in the
    meantime, just define NOCROSSREFS to nothing when using ld.lld, with a
    link to the issue for tracking.
    
    Cc: stable@vger.kernel.org
    Fixes: b9baf5c8c5c3 ("ARM: Spectre-BHB workaround")
    Link: https://github.com/ClangBuiltLinux/linux/issues/1609
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 52c9f93a9c482251cb0d224faa602ba26d462be8
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Mar 9 12:16:34 2022 -0700

    arm64: Do not include __READ_ONCE() block in assembly files
    
    When building arm64 defconfig + CONFIG_LTO_CLANG_{FULL,THIN}=y after
    commit 558c303c9734 ("arm64: Mitigate spectre style branch history side
    channels"), the following error occurs:
    
      <instantiation>:4:2: error: invalid fixup for movz/movk instruction
       mov w0, #ARM_SMCCC_ARCH_WORKAROUND_3
       ^
    
    Marc figured out that moving "#include <linux/init.h>" in
    include/linux/arm-smccc.h into a !__ASSEMBLY__ block resolves it. The
    full include chain with CONFIG_LTO=y from include/linux/arm-smccc.h:
    
    include/linux/init.h
    include/linux/compiler.h
    arch/arm64/include/asm/rwonce.h
    arch/arm64/include/asm/alternative-macros.h
    arch/arm64/include/asm/assembler.h
    
    The asm/alternative-macros.h include in asm/rwonce.h only happens when
    CONFIG_LTO is set, which ultimately casues asm/assembler.h to be
    included before the definition of ARM_SMCCC_ARCH_WORKAROUND_3. As a
    result, the preprocessor does not expand ARM_SMCCC_ARCH_WORKAROUND_3 in
    __mitigate_spectre_bhb_fw, which results in the error above.
    
    Avoid this problem by just avoiding the CONFIG_LTO=y __READ_ONCE() block
    in asm/rwonce.h with assembly files, as nothing in that block is useful
    to assembly files, which allows ARM_SMCCC_ARCH_WORKAROUND_3 to be
    properly expanded with CONFIG_LTO=y builds.
    
    Fixes: e35123d83ee3 ("arm64: lto: Strengthen READ_ONCE() to acquire when CONFIG_LTO=y")
    Cc: <stable@vger.kernel.org> # 5.11.x
    Link: https://lore.kernel.org/r/20220309155716.3988480-1-maz@kernel.org/
    Reported-by: Marc Zyngier <maz@kernel.org>
    Acked-by: James Morse <james.morse@arm.com>
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lore.kernel.org/r/20220309191633.2307110-1-nathan@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 37c333a5dea519973e8b6588ef7845b18ee1cb46
Merge: e7e19defa5758 fe23b6bbeac40
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 9 13:47:12 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid
    
    Pull HID fixes from Jiri Kosina:
    
     - sysfs attributes leak fix for Google Vivaldi driver (Dmitry Torokhov)
    
     - fix for potential out-of-bounds read in Thrustmaster driver (Pavel
       Skripkin)
    
     - error handling reference leak in Elo driver (Jiri Kosina)
    
     - a few new device IDs
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid:
      HID: nintendo: check the return value of alloc_workqueue()
      HID: vivaldi: fix sysfs attributes leak
      HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts
      HID: elo: Revert USB reference counting
      HID: Add support for open wheel and no attachment to T300
      HID: logitech-dj: add new lightspeed receiver id

commit e7e19defa57580d679bf0d03f8a34933008a7930
Merge: 33970b031dc46 b859ebedd1e73
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 9 12:59:21 2022 -0800

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fixes from Catalin Marinas:
    
     - Fix compilation of eBPF object files that indirectly include
       mte-kasan.h.
    
     - Fix test for execute-only permissions with EPAN (Enhanced Privileged
       Access Never, ARMv8.7 feature).
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: kasan: fix include error in MTE functions
      arm64: Ensure execute-only permissions are not allowed without EPAN

commit 33970b031dc4653cc9dc80f2886976706c4c8ef1
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Wed Mar 9 19:08:42 2022 +0000

    ARM: fix co-processor register typo
    
    In the recent Spectre BHB patches, there was a typo that is only
    exposed in certain configurations: mcr p15,0,XX,c7,r5,4 should have
    been mcr p15,0,XX,c7,c5,4
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: b9baf5c8c5c3 ("ARM: Spectre-BHB workaround")
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 99a2b9be077ae3a5d97fbf5f7782e0f2e9812978
Author: Ben Ben-Ishay <benishay@nvidia.com>
Date:   Wed Mar 2 17:07:08 2022 +0200

    net/mlx5e: SHAMPO, reduce TIR indication
    
    SHAMPO is an RQ / WQ feature, an indication was added to the TIR in the
    first place to enforce suitability between connected TIR and RQ, this
    enforcement does not exist in current the Firmware implementation and was
    redundant in the first place.
    
    Fixes: 83439f3c37aa ("net/mlx5e: Add HW-GRO offload")
    Signed-off-by: Ben Ben-Ishay <benishay@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit ad11c4f1d8fd1f03639460e425a36f7fd0ea83f5
Author: Roi Dayan <roid@nvidia.com>
Date:   Wed Feb 16 13:56:57 2022 +0200

    net/mlx5e: Lag, Only handle events from highest priority multipath entry
    
    There could be multiple multipath entries but changing the port affinity
    for each one doesn't make much sense and there should be a default one.
    So only track the entry with lowest priority value.
    The commit doesn't affect existing users with a single entry.
    
    Fixes: 544fe7c2e654 ("net/mlx5e: Activate HW multipath and handle port affinity based on FIB events")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 39bab83b119faac4bf7f07173a42ed35be95147e
Author: Dima Chumak <dchumak@nvidia.com>
Date:   Mon Jan 17 15:32:16 2022 +0200

    net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
    
    Only prio 1 is supported for nic mode when there is no ignore flow level
    support in firmware. But for switchdev mode, which supports fixed number
    of statically pre-allocated prios, this restriction is not relevant so
    it can be relaxed.
    
    Fixes: d671e109bd85 ("net/mlx5: Fix tc max supported prio for nic mode")
    Signed-off-by: Dima Chumak <dchumak@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 063bd355595428750803d8736a9bb7c8db67d42d
Author: Moshe Shemesh <moshe@nvidia.com>
Date:   Fri Feb 4 11:47:44 2022 +0200

    net/mlx5: Fix a race on command flush flow
    
    Fix a refcount use after free warning due to a race on command entry.
    Such race occurs when one of the commands releases its last refcount and
    frees its index and entry while another process running command flush
    flow takes refcount to this command entry. The process which handles
    commands flush may see this command as needed to be flushed if the other
    process released its refcount but didn't release the index yet. Fix it
    by adding the needed spin lock.
    
    It fixes the following warning trace:
    
    refcount_t: addition on 0; use-after-free.
    WARNING: CPU: 11 PID: 540311 at lib/refcount.c:25 refcount_warn_saturate+0x80/0xe0
    ...
    RIP: 0010:refcount_warn_saturate+0x80/0xe0
    ...
    Call Trace:
     <TASK>
     mlx5_cmd_trigger_completions+0x293/0x340 [mlx5_core]
     mlx5_cmd_flush+0x3a/0xf0 [mlx5_core]
     enter_error_state+0x44/0x80 [mlx5_core]
     mlx5_fw_fatal_reporter_err_work+0x37/0xe0 [mlx5_core]
     process_one_work+0x1be/0x390
     worker_thread+0x4d/0x3d0
     ? rescuer_thread+0x350/0x350
     kthread+0x141/0x160
     ? set_kthread_struct+0x40/0x40
     ret_from_fork+0x1f/0x30
     </TASK>
    
    Fixes: 50b2412b7e78 ("net/mlx5: Avoid possible free of command entry while timeout comp handler")
    Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
    Reviewed-by: Eran Ben Elisha <eranbe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit ac77998b7ac3044f0509b097da9637184598980d
Author: Mohammad Kabat <mohammadkab@nvidia.com>
Date:   Thu Mar 25 14:38:55 2021 +0200

    net/mlx5: Fix size field in bufferx_reg struct
    
    According to HW spec the field "size" should be 16 bits
    in bufferx register.
    
    Fixes: e281682bf294 ("net/mlx5_core: HW data structs/types definitions cleanup")
    Signed-off-by: Mohammad Kabat <mohammadkab@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 78cbc6513217b00be6a9904415ef7ff3619eb035
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Mon Mar 7 08:43:03 2022 +0800

    ftrace: Fix some W=1 warnings in kernel doc comments
    
    Clean up the following clang-w1 warning:
    
    kernel/trace/ftrace.c:7827: warning: Function parameter or member 'ops'
    not described in 'unregister_ftrace_function'.
    
    kernel/trace/ftrace.c:7805: warning: Function parameter or member 'ops'
    not described in 'register_ftrace_function'.
    
    Link: https://lkml.kernel.org/r/20220307004303.26399-1-jiapeng.chong@linux.alibaba.com
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit caf4c86bf136845982c5103b2661751b40c474c0
Author: Nicolas Saenz Julienne <nsaenzju@redhat.com>
Date:   Mon Mar 7 19:07:40 2022 +0100

    tracing/osnoise: Force quiescent states while tracing
    
    At the moment running osnoise on a nohz_full CPU or uncontested FIFO
    priority and a PREEMPT_RCU kernel might have the side effect of
    extending grace periods too much. This will entice RCU to force a
    context switch on the wayward CPU to end the grace period, all while
    introducing unwarranted noise into the tracer. This behaviour is
    unavoidable as overly extending grace periods might exhaust the system's
    memory.
    
    This same exact problem is what extended quiescent states (EQS) were
    created for, conversely, rcu_momentary_dyntick_idle() emulates them by
    performing a zero duration EQS. So let's make use of it.
    
    In the common case rcu_momentary_dyntick_idle() is fairly inexpensive:
    atomically incrementing a local per-CPU counter and doing a store. So it
    shouldn't affect osnoise's measurements (which has a 1us granularity),
    so we'll call it unanimously.
    
    The uncommon case involve calling rcu_momentary_dyntick_idle() after
    having the osnoise process:
    
     - Receive an expedited quiescent state IPI with preemption disabled or
       during an RCU critical section. (activates rdp->cpu_no_qs.b.exp
       code-path).
    
     - Being preempted within in an RCU critical section and having the
       subsequent outermost rcu_read_unlock() called with interrupts
       disabled. (t->rcu_read_unlock_special.b.blocked code-path).
    
    Neither of those are possible at the moment, and are unlikely to be in
    the future given the osnoise's loop design. On top of this, the noise
    generated by the situations described above is unavoidable, and if not
    exposed by rcu_momentary_dyntick_idle() will be eventually seen in
    subsequent rcu_read_unlock() calls or schedule operations.
    
    Link: https://lkml.kernel.org/r/20220307180740.577607-1-nsaenzju@redhat.com
    
    Cc: stable@vger.kernel.org
    Fixes: bce29ac9ce0b ("trace: Add osnoise tracer")
    Signed-off-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Acked-by: Paul E. McKenney <paulmck@kernel.org>
    Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit f0cfe17bcc1dd2f0872966b554a148e888833ee9
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Wed Mar 9 14:13:02 2022 +0100

    tracing/osnoise: Do not unregister events twice
    
    Nicolas reported that using:
    
     # trace-cmd record -e all -M 10 -p osnoise --poll
    
    Resulted in the following kernel warning:
    
     ------------[ cut here ]------------
     WARNING: CPU: 0 PID: 1217 at kernel/tracepoint.c:404 tracepoint_probe_unregister+0x280/0x370
     [...]
     CPU: 0 PID: 1217 Comm: trace-cmd Not tainted 5.17.0-rc6-next-20220307-nico+ #19
     RIP: 0010:tracepoint_probe_unregister+0x280/0x370
     [...]
     CR2: 00007ff919b29497 CR3: 0000000109da4005 CR4: 0000000000170ef0
     Call Trace:
      <TASK>
      osnoise_workload_stop+0x36/0x90
      tracing_set_tracer+0x108/0x260
      tracing_set_trace_write+0x94/0xd0
      ? __check_object_size.part.0+0x10a/0x150
      ? selinux_file_permission+0x104/0x150
      vfs_write+0xb5/0x290
      ksys_write+0x5f/0xe0
      do_syscall_64+0x3b/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
     RIP: 0033:0x7ff919a18127
     [...]
     ---[ end trace 0000000000000000 ]---
    
    The warning complains about an attempt to unregister an
    unregistered tracepoint.
    
    This happens on trace-cmd because it first stops tracing, and
    then switches the tracer to nop. Which is equivalent to:
    
      # cd /sys/kernel/tracing/
      # echo osnoise > current_tracer
      # echo 0 > tracing_on
      # echo nop > current_tracer
    
    The osnoise tracer stops the workload when no trace instance
    is actually collecting data. This can be caused both by
    disabling tracing or disabling the tracer itself.
    
    To avoid unregistering events twice, use the existing
    trace_osnoise_callback_enabled variable to check if the events
    (and the workload) are actually active before trying to
    deactivate them.
    
    Link: https://lore.kernel.org/all/c898d1911f7f9303b7e14726e7cc9678fbfb4a0e.camel@redhat.com/
    Link: https://lkml.kernel.org/r/938765e17d5a781c2df429a98f0b2e7cc317b022.1646823913.git.bristot@kernel.org
    
    Cc: stable@vger.kernel.org
    Cc: Marcelo Tosatti <mtosatti@redhat.com>
    Fixes: 2fac8d6486d5 ("tracing/osnoise: Allow multiple instances of the same tracer")
    Reported-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit b859ebedd1e730bbda69142fca87af4e712649a1
Author: Paul Semel <semelpaul@gmail.com>
Date:   Tue Mar 8 10:30:58 2022 +0100

    arm64: kasan: fix include error in MTE functions
    
    Fix `error: expected string literal in 'asm'`.
    This happens when compiling an ebpf object file that includes
    `net/net_namespace.h` from linux kernel headers.
    
    Include trace:
         include/net/net_namespace.h:10
         include/linux/workqueue.h:9
         include/linux/timer.h:8
         include/linux/debugobjects.h:6
         include/linux/spinlock.h:90
         include/linux/workqueue.h:9
         arch/arm64/include/asm/spinlock.h:9
         arch/arm64/include/generated/asm/qrwlock.h:1
         include/asm-generic/qrwlock.h:14
         arch/arm64/include/asm/processor.h:33
         arch/arm64/include/asm/kasan.h:9
         arch/arm64/include/asm/mte-kasan.h:45
         arch/arm64/include/asm/mte-def.h:14
    
    Signed-off-by: Paul Semel <paul.semel@datadoghq.com>
    Fixes: 2cb34276427a ("arm64: kasan: simplify and inline MTE functions")
    Cc: <stable@vger.kernel.org> # 5.12.x
    Link: https://lore.kernel.org/r/bacb5387-2992-97e4-0c48-1ed925905bee@gmail.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit cc7e2f596e64783ded1feebc55445199c9bd929e
Merge: 71171ac8eb34c 23c7f8d7989e1
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Mar 9 14:48:11 2022 +0000

    Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec
    
    Steffen Klassert says:
    
    ====================
    pull request (net): ipsec 2022-03-09
    
    1) Fix IPv6 PMTU discovery for xfrm interfaces.
       From Lina Wang.
    
    2) Revert failing for policies and states that are
       configured with XFRMA_IF_ID 0. It broke a
       user configuration. From Kai Lueke.
    
    3) Fix a possible buffer overflow in the ESP output path.
    
    4) Fix ESP GSO for tunnel and BEET mode on inter address
       family tunnels.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 71171ac8eb34ce7fe6b3267dce27c313ab3cb3ac
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Tue Mar 8 16:12:23 2022 +0800

    ax25: Fix NULL pointer dereference in ax25_kill_by_device
    
    When two ax25 devices attempted to establish connection, the requester use ax25_create(),
    ax25_bind() and ax25_connect() to initiate connection. The receiver use ax25_rcv() to
    accept connection and use ax25_create_cb() in ax25_rcv() to create ax25_cb, but the
    ax25_cb->sk is NULL. When the receiver is detaching, a NULL pointer dereference bug
    caused by sock_hold(sk) in ax25_kill_by_device() will happen. The corresponding
    fail log is shown below:
    
    ===============================================================
    BUG: KASAN: null-ptr-deref in ax25_device_event+0xfd/0x290
    Call Trace:
    ...
    ax25_device_event+0xfd/0x290
    raw_notifier_call_chain+0x5e/0x70
    dev_close_many+0x174/0x220
    unregister_netdevice_many+0x1f7/0xa60
    unregister_netdevice_queue+0x12f/0x170
    unregister_netdev+0x13/0x20
    mkiss_close+0xcd/0x140
    tty_ldisc_release+0xc0/0x220
    tty_release_struct+0x17/0xa0
    tty_release+0x62d/0x670
    ...
    
    This patch add condition check in ax25_kill_by_device(). If s->sk is
    NULL, it will goto if branch to kill device.
    
    Fixes: 4e0f718daf97 ("ax25: improve the incomplete fix to avoid UAF and NPD bugs")
    Reported-by: Thomas Osterried <thomas@osterried.de>
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c9ffa3e2bc451816ce0295e40063514fabf2bd36
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Tue Mar 8 07:42:47 2022 +0000

    net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr
    
    This node pointer is returned by of_find_compatible_node() with
    refcount incremented. Calling of_node_put() to aovid the refcount leak.
    
    Fixes: 501ef3066c89 ("net: marvell: prestera: Add driver for Prestera family ASIC devices")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2169b79258c8be803d2595d6456b1e77129fe154
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Mar 8 14:57:39 2022 +0800

    net: ethernet: lpc_eth: Handle error for clk_enable
    
    As the potential failure of the clk_enable(),
    it should be better to check it and return error
    if fails.
    
    Fixes: b7370112f519 ("lpc32xx: Added ethernet driver")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2a760554dcba450d3ad61b32375b50ed6d59a87c
Author: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn>
Date:   Tue Mar 8 06:43:09 2022 +0000

    net:mcf8390: Use platform_get_irq() to get the interrupt
    
    It is not recommened to use platform_get_resource(pdev, IORESOURCE_IRQ)
    for requesting IRQ's resources any more, as they can be not ready yet in
    case of DT-booting.
    
    platform_get_irq() instead is a recommended way for getting IRQ even if
    it was not retrieved earlier.
    
    It also makes code simpler because we're getting "int" value right away
    and no conversion from resource to int is required.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6babfc6e6fab068018c36e8f6605184b8c0b349d
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Mar 8 14:40:07 2022 +0800

    net: ethernet: ti: cpts: Handle error for clk_enable
    
    As the potential failure of the clk_enable(),
    it should be better to check it and return error
    if fails.
    
    Fixes: 8a2c9a5ab4b9 ("net: ethernet: ti: cpts: rework initialization/deinitialization")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 445c1470b6ef96440e7cfc42dfc160f5004fd149
Author: Ross Philipson <ross.philipson@oracle.com>
Date:   Wed Feb 23 21:07:36 2022 -0500

    x86/boot: Add setup_indirect support in early_memremap_is_setup_data()
    
    The x86 boot documentation describes the setup_indirect structures and
    how they are used. Only one of the two functions in ioremap.c that needed
    to be modified to be aware of the introduction of setup_indirect
    functionality was updated. Adds comparable support to the other function
    where it was missing.
    
    Fixes: b3c72fc9a78e ("x86/boot: Introduce setup_indirect")
    Signed-off-by: Ross Philipson <ross.philipson@oracle.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/1645668456-22036-3-git-send-email-ross.philipson@oracle.com

commit 7228918b34615ef6317edcd9a058a057bc54aa32
Author: Ross Philipson <ross.philipson@oracle.com>
Date:   Wed Feb 23 21:07:35 2022 -0500

    x86/boot: Fix memremap of setup_indirect structures
    
    As documented, the setup_indirect structure is nested inside
    the setup_data structures in the setup_data list. The code currently
    accesses the fields inside the setup_indirect structure but only
    the sizeof(struct setup_data) is being memremapped. No crash
    occurred but this is just due to how the area is remapped under the
    covers.
    
    Properly memremap both the setup_data and setup_indirect structures
    in these cases before accessing them.
    
    Fixes: b3c72fc9a78e ("x86/boot: Introduce setup_indirect")
    Signed-off-by: Ross Philipson <ross.philipson@oracle.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/1645668456-22036-2-git-send-email-ross.philipson@oracle.com

commit 030141b0fce1e823190b07b1a592b5ccdab3f5fd
Merge: c79fcc27be90b ad35ffa252af6
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Mar 9 10:42:14 2022 +0000

    Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-03-08
    
    This series contains updates to iavf, i40e, and ice drivers.
    
    Michal ensures netdev features are properly updated to reflect VLAN
    changes received from PF and adds an additional flag for MSI-X
    reinitialization as further differentiation of reinitialization
    operations is needed for iavf.
    
    Jake stops disabling of VFs due to failed virtchannel responses for
    i40e and ice driver.
    
    Dave moves MTU event notification to the service task to prevent issues
    with RTNL lock for ice.
    
    Christophe Jaillet corrects an allocation to GFP_ATOMIC instead of
    GFP_KERNEL for ice.
    
    Jedrzej fixes the value for link speed comparison which was preventing
    the requested value from being set for ice.
    ---
    Note: This will conflict when merging with net-next. Resolution:
    
    diff --cc drivers/net/ethernet/intel/ice/ice.h
    index dc42ff92dbad,3121f9b04f59..000000000000
    --- a/drivers/net/ethernet/intel/ice/ice.h
    +++ b/drivers/net/ethernet/intel/ice/ice.h
    @@@ -484,10 -481,9 +484,11 @@@ enum ice_pf_flags
            ICE_FLAG_LEGACY_RX,
            ICE_FLAG_VF_TRUE_PROMISC_ENA,
            ICE_FLAG_MDD_AUTO_RESET_VF,
     +      ICE_FLAG_VF_VLAN_PRUNING,
            ICE_FLAG_LINK_LENIENT_MODE_ENA,
            ICE_FLAG_PLUG_AUX_DEV,
    +       ICE_FLAG_MTU_CHANGED,
     +      ICE_FLAG_GNSS,                  /* GNSS successfully initialized */
            ICE_PF_FLAGS_NBITS              /* must be last */
      };
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c79fcc27be90b308b3fa90811aefafdd4078668c
Author: Tung Nguyen <tung.q.nguyen@dektech.com.au>
Date:   Tue Mar 8 02:11:59 2022 +0000

    tipc: fix incorrect order of state message data sanity check
    
    When receiving a state message, function tipc_link_validate_msg()
    is called to validate its header portion. Then, its data portion
    is validated before it can be accessed correctly. However, current
    data sanity  check is done after the message header is accessed to
    update some link variables.
    
    This commit fixes this issue by moving the data sanity check to
    the beginning of state message handling and right after the header
    sanity check.
    
    Fixes: 9aa422ad3266 ("tipc: improve size validations for received domain records")
    Acked-by: Jon Maloy <jmaloy@redhat.com>
    Signed-off-by: Tung Nguyen <tung.q.nguyen@dektech.com.au>
    Link: https://lore.kernel.org/r/20220308021200.9245-1-tung.q.nguyen@dektech.com.au
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit b19ab4b38b06aae12442b2de95ccf58b5dc53584
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Tue Mar 8 02:47:49 2022 +0000

    ethernet: Fix error handling in xemaclite_of_probe
    
    This node pointer is returned by of_parse_phandle() with refcount
    incremented in this function. Calling of_node_put() to avoid the
    refcount leak. As the remove function do.
    
    Fixes: 5cdaaa12866e ("net: emaclite: adding MDIO and phy lib support")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220308024751.2320-1-linmq006@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0a5aa8d161d19a1b12fd25b434b32f7c885c73bb
Author: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Date:   Tue Mar 8 17:09:15 2022 +0900

    block: fix blk_mq_attempt_bio_merge and rq_qos_throttle protection
    
    Commit 9d497e2941c3 ("block: don't protect submit_bio_checks by
    q_usage_counter") moved blk_mq_attempt_bio_merge and rq_qos_throttle
    calls out of q_usage_counter protection. However, these functions require
    q_usage_counter protection. The blk_mq_attempt_bio_merge call without
    the protection resulted in blktests block/005 failure with KASAN null-
    ptr-deref or use-after-free at bio merge. The rq_qos_throttle call
    without the protection caused kernel hang at qos throttle.
    
    To fix the failures, move the blk_mq_attempt_bio_merge and
    rq_qos_throttle calls back to q_usage_counter protection.
    
    Fixes: 9d497e2941c3 ("block: don't protect submit_bio_checks by q_usage_counter")
    Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
    Link: https://lore.kernel.org/r/20220308080915.3473689-1-shinichiro.kawasaki@wdc.com
    Reviewed-by: Ming Lei <ming.lei@redhat.com>
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit ad35ffa252af67d4cc7c744b9377a2b577748e3f
Author: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Date:   Tue Feb 22 11:43:04 2022 +0000

    ice: Fix curr_link_speed advertised speed
    
    Change curr_link_speed advertised speed, due to
    link_info.link_speed is not equal phy.curr_user_speed_req.
    Without this patch it is impossible to set advertised
    speed to same as link_speed.
    
    Testing Hints: Try to set advertised speed
    to 25G only with 25G default link (use ethtool -s 0x80000000)
    
    Fixes: 48cb27f2fd18 ("ice: Implement handlers for ethtool PHY/link operations")
    Signed-off-by: Grzegorz Siwik <grzegorz.siwik@intel.com>
    Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
    Tested-by: Gurucharan <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 3d97f1afd8d831e0c0dc1157418f94b8faa97b54
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 16 19:46:20 2022 +0100

    ice: Don't use GFP_KERNEL in atomic context
    
    ice_misc_intr() is an irq handler. It should not sleep.
    
    Use GFP_ATOMIC instead of GFP_KERNEL when allocating some memory.
    
    Fixes: 348048e724a0 ("ice: Implement iidc operations")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Tested-by: Leszek Kaliszczuk <leszek.kaliszczuk@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 97b0129146b1544bbb0773585327896da3bb4e0a
Author: Dave Ertman <david.m.ertman@intel.com>
Date:   Fri Feb 18 12:39:25 2022 -0800

    ice: Fix error with handling of bonding MTU
    
    When a bonded interface is destroyed, .ndo_change_mtu can be called
    during the tear-down process while the RTNL lock is held.  This is a
    problem since the auxiliary driver linked to the LAN driver needs to be
    notified of the MTU change, and this requires grabbing a device_lock on
    the auxiliary_device's dev.  Currently this is being attempted in the
    same execution context as the call to .ndo_change_mtu which is causing a
    dead-lock.
    
    Move the notification of the changed MTU to a separate execution context
    (watchdog service task) and eliminate the "before" notification.
    
    Fixes: 348048e724a0e ("ice: Implement iidc operations")
    Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
    Tested-by: Jonathan Toppins <jtoppins@redhat.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 79498d5af8e458102242d1667cf44df1f1564e63
Author: Jacob Keller <jacob.e.keller@intel.com>
Date:   Wed Feb 16 16:51:36 2022 -0800

    ice: stop disabling VFs due to PF error responses
    
    The ice_vc_send_msg_to_vf function has logic to detect "failure"
    responses being sent to a VF. If a VF is sent more than
    ICE_DFLT_NUM_INVAL_MSGS_ALLOWED then the VF is marked as disabled.
    Almost identical logic also existed in the i40e driver.
    
    This logic was added to the ice driver in commit 1071a8358a28 ("ice:
    Implement virtchnl commands for AVF support") which itself copied from
    the i40e implementation in commit 5c3c48ac6bf5 ("i40e: implement virtual
    device interface").
    
    Neither commit provides a proper explanation or justification of the
    check. In fact, later commits to i40e changed the logic to allow
    bypassing the check in some specific instances.
    
    The "logic" for this seems to be that error responses somehow indicate a
    malicious VF. This is not really true. The PF might be sending an error
    for any number of reasons such as lack of resources, etc.
    
    Additionally, this causes the PF to log an info message for every failed
    VF response which may confuse users, and can spam the kernel log.
    
    This behavior is not documented as part of any requirement for our
    products and other operating system drivers such as the FreeBSD
    implementation of our drivers do not include this type of check.
    
    In fact, the change from dev_err to dev_info in i40e commit 18b7af57d9c1
    ("i40e: Lower some message levels") explains that these messages
    typically don't actually indicate a real issue. It is quite likely that
    a user who hits this in practice will be very confused as the VF will be
    disabled without an obvious way to recover.
    
    We already have robust malicious driver detection logic using actual
    hardware detection mechanisms that detect and prevent invalid device
    usage. Remove the logic since its not a documented requirement and the
    behavior is not intuitive.
    
    Fixes: 1071a8358a28 ("ice: Implement virtchnl commands for AVF support")
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 5710ab79166504013f7c0ae6a57e7d2fd26e5c43
Author: Jacob Keller <jacob.e.keller@intel.com>
Date:   Wed Feb 16 16:51:35 2022 -0800

    i40e: stop disabling VFs due to PF error responses
    
    The i40e_vc_send_msg_to_vf_ex (and its wrapper i40e_vc_send_msg_to_vf)
    function has logic to detect "failure" responses sent to the VF. If a VF
    is sent more than I40E_DEFAULT_NUM_INVALID_MSGS_ALLOWED, then the VF is
    marked as disabled. In either case, a dev_info message is printed
    stating that a VF opcode failed.
    
    This logic originates from the early implementation of VF support in
    commit 5c3c48ac6bf5 ("i40e: implement virtual device interface").
    
    That commit did not go far enough. The "logic" for this behavior seems
    to be that error responses somehow indicate a malicious VF. This is not
    really true. The PF might be sending an error for any number of reasons
    such as lacking resources, an unsupported operation, etc. This does not
    indicate a malicious VF. We already have a separate robust malicious VF
    detection which relies on hardware logic to detect and prevent a variety
    of behaviors.
    
    There is no justification for this behavior in the original
    implementation. In fact, a later commit 18b7af57d9c1 ("i40e: Lower some
    message levels") reduced the opcode failure message from a dev_err to a
    dev_info. In addition, recent commit 01cbf50877e6 ("i40e: Fix to not
    show opcode msg on unsuccessful VF MAC change") changed the logic to
    allow quieting it for expected failures.
    
    That commit prevented this logic from kicking in for specific
    circumstances. This change did not go far enough. The behavior is not
    documented nor is it part of any requirement for our products. Other
    operating systems such as the FreeBSD implementation of our driver do
    not include this logic.
    
    It is clear this check does not make sense, and causes problems which
    led to ugly workarounds.
    
    Fix this by just removing the entire logic and the need for the
    i40e_vc_send_msg_to_vf_ex function.
    
    Fixes: 01cbf50877e6 ("i40e: Fix to not show opcode msg on unsuccessful VF MAC change")
    Fixes: 5c3c48ac6bf5 ("i40e: implement virtual device interface")
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 57d03f5608c34079f6f15031f4e8b1e2ae95dcb0
Author: Michal Maloszewski <michal.maloszewski@intel.com>
Date:   Wed Feb 2 12:44:54 2022 +0000

    iavf: Fix adopting new combined setting
    
    In some cases overloaded flag IAVF_FLAG_REINIT_ITR_NEEDED
    which should indicate that interrupts need to be completely
    reinitialized during reset leads to RTNL deadlocks using ethtool -C
    while a reset is in progress.
    To fix, it was added a new flag IAVF_FLAG_REINIT_MSIX_NEEDED
    used to trigger MSI-X reinit.
    New combined setting is fixed adopt after VF reset.
    This has been implemented by call reinit interrupt scheme
    during VF reset.
    Without this fix new combined setting has never been adopted.
    
    Fixes: 209f2f9c7181 ("iavf: Add support for VIRTCHNL_VF_OFFLOAD_VLAN_V2 negotiation")
    Signed-off-by: Grzegorz Szczurek <grzegorzx.szczurek@intel.com>
    Signed-off-by: Mitch Williams <mitch.a.williams@intel.com>
    Signed-off-by: Michal Maloszewski <michal.maloszewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 2cf29e55894886965722e6625f6a03630b4db31d
Author: Michal Maloszewski <michal.maloszewski@intel.com>
Date:   Mon Jan 24 13:35:43 2022 +0000

    iavf: Fix handling of vlan strip virtual channel messages
    
    Modify netdev->features for vlan stripping based on virtual
    channel messages received from the PF. Change is needed
    to synchronize vlan strip status between PF sysfs and iavf ethtool.
    
    Fixes: 5951a2b9812d ("iavf: Fix VLAN feature flags after VFR")
    Signed-off-by: Norbert Ciosek <norbertx.ciosek@intel.com>
    Signed-off-by: Michal Maloszewski <michal.maloszewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 330f4c53d3c2d8b11d86ec03a964b86dc81452f5
Author: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
Date:   Tue Mar 8 20:18:20 2022 +0100

    ARM: fix build error when BPF_SYSCALL is disabled
    
    It was missing a semicolon.
    
    Signed-off-by: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Fixes: 25875aa71dfe ("ARM: include unprivileged BPF status in Spectre V2 reporting").
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4f86a6b46e5377a300b1d49f51c687450f72fb6d
Merge: 92f90cc9fe0e7 f6eafa4022dd6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 8 11:52:45 2022 -0800

    Merge tag 'devicetree-fixes-for-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
    
    Pull devicetree fixes from Rob Herring:
    
     - Fix pinctrl node name warnings in examples
    
     - Add missing 'mux-states' property in ti,tcan104x-can binding
    
    * tag 'devicetree-fixes-for-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux:
      dt-bindings: phy: ti,tcan104x-can: Document mux-states property
      dt-bindings: mfd: Fix pinctrl node name warnings

commit 92f90cc9fe0e7a984ea3d4bf3d120e30ba8a2118
Merge: cd22a8bfcfe07 0c4bcfdecb1ac
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 8 09:41:18 2022 -0800

    Merge tag 'fuse-fixes-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse
    
    Pull fuse fixes from Miklos Szeredi:
    
     - Fix an issue with splice on the fuse device
    
     - Fix a regression in the fileattr API conversion
    
     - Add a small userspace API improvement
    
    * tag 'fuse-fixes-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse:
      fuse: fix pipe buffer lifetime for direct_io
      fuse: move FUSE_SUPER_MAGIC definition to magic.h
      fuse: fix fileattr op failure

commit cd22a8bfcfe07ef35b1b5d96dd468e92dc5e9d8a
Merge: fc55c23a736cc 58c9a5060cb7c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 8 09:27:25 2022 -0800

    Merge tag 'arm64-spectre-bhb-for-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 spectre fixes from James Morse:
     "ARM64 Spectre-BHB mitigations:
    
       - Make EL1 vectors per-cpu
    
       - Add mitigation sequences to the EL1 and EL2 vectors on vulnerble
         CPUs
    
       - Implement ARCH_WORKAROUND_3 for KVM guests
    
       - Report Vulnerable when unprivileged eBPF is enabled"
    
    * tag 'arm64-spectre-bhb-for-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: proton-pack: Include unprivileged eBPF status in Spectre v2 mitigation reporting
      arm64: Use the clearbhb instruction in mitigations
      KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
      arm64: Mitigate spectre style branch history side channels
      arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of Spectre-v2
      arm64: Add percpu vectors for EL1
      arm64: entry: Add macro for reading symbol addresses from the trampoline
      arm64: entry: Add vectors that have the bhb mitigation sequences
      arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
      arm64: entry: Allow the trampoline text to occupy multiple pages
      arm64: entry: Make the kpti trampoline's kpti sequence optional
      arm64: entry: Move trampoline macros out of ifdef'd section
      arm64: entry: Don't assume tramp_vectors is the start of the vectors
      arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
      arm64: entry: Move the trampoline data page before the text page
      arm64: entry: Free up another register on kpti's tramp_exit path
      arm64: entry: Make the trampoline cleanup optional
      KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
      arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
      arm64: entry.S: Add ventry overflow sanity checks

commit fc55c23a736cce88f5f975ab93326d25b49ef109
Merge: 4a01e748a51cd 25875aa71dfef
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 8 09:08:06 2022 -0800

    Merge tag 'for-linus-bhb' of git://git.armlinux.org.uk/~rmk/linux-arm
    
    Pull ARM spectre fixes from Russell King:
     "ARM Spectre BHB mitigations.
    
      These patches add Spectre BHB migitations for the following Arm CPUs
      to the 32-bit ARM kernels:
       - Cortex A15
       - Cortex A57
       - Cortex A72
       - Cortex A73
       - Cortex A75
       - Brahma B15
      for CVE-2022-23960"
    
    * tag 'for-linus-bhb' of git://git.armlinux.org.uk/~rmk/linux-arm:
      ARM: include unprivileged BPF status in Spectre V2 reporting
      ARM: Spectre-BHB workaround
      ARM: use LOADADDR() to get load address of sections
      ARM: early traps initialisation
      ARM: report Spectre v2 status through sysfs

commit f6eafa4022dd61e029205bea4d4147d26e69fef2
Author: Aswath Govindraju <a-govindraju@ti.com>
Date:   Thu Dec 16 09:40:11 2021 +0530

    dt-bindings: phy: ti,tcan104x-can: Document mux-states property
    
    On some boards, for routing CAN signals from controller to transceivers,
    muxes might need to be set. This can be implemented using mux-states
    property. Therefore, document the same in the respective bindings.
    
    Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20211216041012.16892-2-a-govindraju@ti.com

commit 7e807f4b081c5813df21da54e9a0491ea2ce16e7
Author: Rob Herring <robh@kernel.org>
Date:   Thu Mar 3 17:23:49 2022 -0600

    dt-bindings: mfd: Fix pinctrl node name warnings
    
    The recent addition pinctrl.yaml in commit c09acbc499e8 ("dt-bindings:
    pinctrl: use pinctrl.yaml") resulted in some node name warnings:
    
    Documentation/devicetree/bindings/mfd/cirrus,lochnagar.example.dt.yaml: \
     lochnagar-pinctrl: $nodename:0: 'lochnagar-pinctrl' does not match '^(pinctrl|pinmux)(@[0-9a-f]+)?$'
    Documentation/devicetree/bindings/mfd/cirrus,madera.example.dt.yaml: \
     codec@1a: $nodename:0: 'codec@1a' does not match '^(pinctrl|pinmux)(@[0-9a-f]+)?$'
    Documentation/devicetree/bindings/mfd/brcm,cru.example.dt.yaml: \
     pin-controller@1c0: $nodename:0: 'pin-controller@1c0' does not match '^(pinctrl|pinmux)(@[0-9a-f]+)?$'
    
    Fix the node names to the preferred 'pinctrl'. For cirrus,madera,
    nothing from pinctrl.yaml schema is used, so just drop the reference.
    
    Fixes: c09acbc499e8 ("dt-bindings: pinctrl: use pinctrl.yaml")
    Cc: Rafał Miłecki <rafal@milecki.pl>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Acked-by: Lee Jones <lee.jones@linaro.org>
    Link: https://lore.kernel.org/r/20220303232350.2591143-1-robh@kernel.org

commit d986afd5a7b75b477ac347b222354cecd97edc87
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Fri Mar 4 15:55:59 2022 +0800

    MAINTAINERS: Update Jisheng's email address
    
    I'm leaving synaptics. Update my email address to my korg mail
    address and add entries to .mailmap as well to map my work
    addresses to korg mail address.
    
    Signed-off-by: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
    Link: https://lore.kernel.org/r/ce7213bd-28ac-6580-466e-875e755fe0ae@synaptics.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit ee0a4dc9f317fb9a97f20037d219802ca8de939b
Author: Florian Westphal <fw@strlen.de>
Date:   Tue Mar 8 17:28:38 2022 +0100

    Revert "netfilter: conntrack: tag conntracks picked up in local out hook"
    
    This was a prerequisite for the ill-fated
    "netfilter: nat: force port remap to prevent shadowing well-known ports".
    
    As this has been reverted, this change can be backed out too.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit d25ca90833073f2b807e0e697dcf05ba75396de7
Merge: d3258737afc01 1860d30466366
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 8 17:25:23 2022 +0100

    Merge tag 'arm-soc/for-5.18/maintainers' of https://github.com/Broadcom/stblinux into arm/fixes
    
    This pull request updates the MAINTAINERS file for Broadcom SoCs, please
    pull the following for 5.18:
    
    - Kuldeep updates the Broadcom iProc entry to use the same up to date
    Linux tree as the other Broadcom SoCs.
    
    * tag 'arm-soc/for-5.18/maintainers' of https://github.com/Broadcom/stblinux:
      MAINTAINERS: Update git tree for Broadcom iProc SoCs
    
    Link: https://lore.kernel.org/r/20220307194817.3754107-4-f.fainelli@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 25875aa71dfefd1959f07e626c4d285b88b27ac2
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Mon Mar 7 19:28:32 2022 +0000

    ARM: include unprivileged BPF status in Spectre V2 reporting
    
    The mitigations for Spectre-BHB are only applied when an exception
    is taken, but when unprivileged BPF is enabled, userspace can
    load BPF programs that can be used to exploit the problem.
    
    When unprivileged BPF is enabled, report the vulnerable status via
    the spectre_v2 sysfs file.
    
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit d3258737afc0101f497745f83fc4038c963a6b81
Author: Robert Foss <robert.foss@linaro.org>
Date:   Tue Mar 8 10:49:11 2022 +0100

    Revert "arm64: dts: mt8183: jacuzzi: Fix bus properties in anx's DSI endpoint"
    
    This reverts commit 32568ae37596b529628ac09b875f4874e614f63f.
    
    Signed-off-by: Robert Foss <robert.foss@linaro.org>
    Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Acked-by: Matthias Brugger <matthias.bgg@gmail.com>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 979452fbc43028675b5a5da156f91928b739dea8
Author: Robert Foss <robert.foss@linaro.org>
Date:   Tue Mar 8 10:49:10 2022 +0100

    dt-bindings: drm/bridge: anx7625: Revert DPI support
    
    Revert DPI support from binding.
    
    DPI support relies on the bus-type enum which does not yet support
    Mipi DPI, since no v4l2_fwnode_bus_type has been defined for this
    bus type.
    
    When DPI for anx7625 was initially added, it assumed that
    V4L2_FWNODE_BUS_TYPE_PARALLEL was the correct bus type for
    representing DPI, which it is not.
    
    In order to prevent adding this mis-usage to the ABI, let's revert
    the support.
    
    Signed-off-by: Robert Foss <robert.foss@linaro.org>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 5adf349439d29f92467e864f728dfc23180f3ef9
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Thu Mar 3 12:23:23 2022 +0100

    x86/module: Fix the paravirt vs alternative order
    
    Ever since commit
    
      4e6292114c74 ("x86/paravirt: Add new features for paravirt patching")
    
    there is an ordering dependency between patching paravirt ops and
    patching alternatives, the module loader still violates this.
    
    Fixes: 4e6292114c74 ("x86/paravirt: Add new features for paravirt patching")
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Miroslav Benes <mbenes@suse.cz>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220303112825.068773913@infradead.org

commit a82c25c366b0963d33ddf699196e6cf57f6d89b1
Author: Florian Westphal <fw@strlen.de>
Date:   Tue Mar 8 13:52:11 2022 +0100

    Revert "netfilter: nat: force port remap to prevent shadowing well-known ports"
    
    This reverts commit 878aed8db324bec64f3c3f956e64d5ae7375a5de.
    
    This change breaks existing setups where conntrack is used with
    asymmetric paths.
    
    In these cases, the NAT transformation occurs on the syn-ack instead of
    the syn:
    
    1. SYN    x:12345 -> y -> 443 // sent by initiator, receiverd by responder
    2. SYNACK y:443 -> x:12345 // First packet seen by conntrack, as sent by responder
    3. tuple_force_port_remap() gets called, sees:
      'tcp from 443 to port 12345 NAT' -> pick a new source port, inititor receives
    4. SYNACK y:$RANDOM -> x:12345   // connection is never established
    
    While its possible to avoid the breakage with NOTRACK rules, a kernel
    update should not break working setups.
    
    An alternative to the revert is to augment conntrack to tag
    mid-stream connections plus more code in the nat core to skip NAT
    for such connections, however, this leads to more interaction/integration
    between conntrack and NAT.
    
    Therefore, revert, users will need to add explicit nat rules to avoid
    port shadowing.
    
    Link: https://lore.kernel.org/netfilter-devel/20220302105908.GA5852@breakpoint.cc/#R
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2051413
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit 2f6edb6bcb2f3f41d876e0eba2ba97f87a0296ea
Author: Joel Stanley <joel@jms.id.au>
Date:   Tue Mar 8 10:36:31 2022 +1030

    ARM: dts: aspeed: Fix AST2600 quad spi group
    
    Requesting quad mode for the FMC resulted in an error:
    
      &fmc {
             status = "okay";
     +       pinctrl-names = "default";
     +       pinctrl-0 = <&pinctrl_fwqspi_default>'
    
    [    0.742963] aspeed-g6-pinctrl 1e6e2000.syscon:pinctrl: invalid function FWQSPID in map table
    
    
    This is because the quad mode pins are a group of pins, not a function.
    
    After applying this patch we can request the pins and the QSPI data
    lines are muxed:
    
     # cat /sys/kernel/debug/pinctrl/1e6e2000.syscon\:pinctrl-aspeed-g6-pinctrl/pinmux-pins |grep 1e620000.spi
     pin 196 (AE12): device 1e620000.spi function FWSPID group FWQSPID
     pin 197 (AF12): device 1e620000.spi function FWSPID group FWQSPID
     pin 240 (Y1): device 1e620000.spi function FWSPID group FWQSPID
     pin 241 (Y2): device 1e620000.spi function FWSPID group FWQSPID
     pin 242 (Y3): device 1e620000.spi function FWSPID group FWQSPID
     pin 243 (Y4): device 1e620000.spi function FWSPID group FWQSPID
    
    Fixes: f510f04c8c83 ("ARM: dts: aspeed: Add AST2600 pinmux nodes")
    Signed-off-by: Joel Stanley <joel@jms.id.au>
    Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
    Link: https://lore.kernel.org/r/20220304011010.974863-1-joel@jms.id.au
    Link: https://lore.kernel.org/r/20220304011010.974863-1-joel@jms.id.au'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 60392db617b5ccd7ba3bfa03673a45085bcfe3ee
Merge: 5125091d757a2 7401b49c50c2b
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 8 13:43:41 2022 +0100

    Merge tag 'tegra-for-5.17-arm-dt-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into arm/fixes
    
    ARM: tegra: Device tree fixes for v5.17
    
    One more patch to fix up eDP panels on Nyan FHD models.
    
    * tag 'tegra-for-5.17-arm-dt-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux:
      ARM: tegra: Move Nyan FHD panels to AUX bus
      ARM: tegra: Move panels to AUX bus
    
    Link: https://lore.kernel.org/r/20220308084339.2199400-1-thierry.reding@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 1a4e53d2fc4f68aa654ad96d13ad042e1a8e8a7d
Author: Biju Das <biju.das.jz@bp.renesas.com>
Date:   Mon Mar 7 18:48:43 2022 +0000

    spi: Fix invalid sgs value
    
    max_seg_size is unsigned int and it can have a value up to 2^32
    (for eg:-RZ_DMAC driver sets dma_set_max_seg_size as U32_MAX)
    When this value is used in min_t() as an integer type, it becomes
    -1 and the value of sgs becomes 0.
    
    Fix this issue by replacing the 'int' data type with 'unsigned int'
    in min_t().
    
    Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
    Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Link: https://lore.kernel.org/r/20220307184843.9994-1-biju.das.jz@bp.renesas.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit e5417cbf7ab5df1632e68fe7d9e6331fc0e7dbd6
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Mon Mar 7 12:13:30 2022 +0000

    net: dsa: mt7530: fix incorrect test in mt753x_phylink_validate()
    
    Discussing one of the tests in mt753x_phylink_validate() with Landen
    Chao confirms that the "||" should be "&&". Fix this.
    
    Fixes: c288575f7810 ("net: dsa: mt7530: Add the support of MT7531 switch")
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Link: https://lore.kernel.org/r/E1nRCF0-00CiXD-7q@rmk-PC.armlinux.org.uk
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>

commit 9470c29faa91c804aa04de4c10634bf02462bfa5
Author: Jernej Skrabec <jernej.skrabec@gmail.com>
Date:   Mon Feb 28 19:14:36 2022 +0100

    drm/sun4i: mixer: Fix P010 and P210 format numbers
    
    It turns out that DE3 manual has inverted YUV and YVU format numbers for
    P010 and P210. Invert them.
    
    This was tested by playing video decoded to P010 and additionally
    confirmed by looking at BSP driver source.
    
    Fixes: 169ca4b38932 ("drm/sun4i: Add separate DE3 VI layer formats")
    Signed-off-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220228181436.1424550-1-jernej.skrabec@gmail.com

commit 6e2edd6371a497a6350bb735534c9bda2a31f43d
Author: Catalin Marinas <catalin.marinas@arm.com>
Date:   Thu Mar 3 18:00:44 2022 +0000

    arm64: Ensure execute-only permissions are not allowed without EPAN
    
    Commit 18107f8a2df6 ("arm64: Support execute-only permissions with
    Enhanced PAN") re-introduced execute-only permissions when EPAN is
    available. When EPAN is not available, arch_filter_pgprot() is supposed
    to change a PAGE_EXECONLY permission into PAGE_READONLY_EXEC. However,
    if BTI or MTE are present, such check does not detect the execute-only
    pgprot in the presence of PTE_GP (BTI) or MT_NORMAL_TAGGED (MTE),
    allowing the user to request PROT_EXEC with PROT_BTI or PROT_MTE.
    
    Remove the arch_filter_pgprot() function, change the default VM_EXEC
    permissions to PAGE_READONLY_EXEC and update the protection_map[] array
    at core_initcall() if EPAN is detected.
    
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
    Fixes: 18107f8a2df6 ("arm64: Support execute-only permissions with Enhanced PAN")
    Cc: <stable@vger.kernel.org> # 5.13.x
    Acked-by: Will Deacon <will@kernel.org>
    Reviewed-by: Vladimir Murzin <vladimir.murzin@arm.com>
    Tested-by: Vladimir Murzin <vladimir.murzin@arm.com>

commit a9a5b720dc8227243f433141ba1343aa53ef57e4
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Mon Mar 7 18:38:40 2022 +0200

    gpio: sim: Declare gpio_sim_hog_config_item_ops static
    
    Compiler is not happy:
    
      warning: symbol 'gpio_sim_hog_config_item_ops' was not declared. Should it be static?
    
    Fixes: cb8c474e79be ("gpio: sim: new testing module")
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 4a01e748a51cdc0527fdc913546dd46e822aa00d
Merge: ea4424be16887 0de05d056afdb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Mar 7 17:29:47 2022 -0800

    Merge tag 'x86_bugs_for_v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 spectre fixes from Borislav Petkov:
    
     - Mitigate Spectre v2-type Branch History Buffer attacks on machines
       which support eIBRS, i.e., the hardware-assisted speculation
       restriction after it has been shown that such machines are vulnerable
       even with the hardware mitigation.
    
     - Do not use the default LFENCE-based Spectre v2 mitigation on AMD as
       it is insufficient to mitigate such attacks. Instead, switch to
       retpolines on all AMD by default.
    
     - Update the docs and add some warnings for the obviously vulnerable
       cmdline configurations.
    
    * tag 'x86_bugs_for_v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
      x86/speculation: Warn about Spectre v2 LFENCE mitigation
      x86/speculation: Update link to AMD speculation whitepaper
      x86/speculation: Use generic retpoline by default on AMD
      x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation reporting
      Documentation/hw-vuln: Update spectre doc
      x86/speculation: Add eIBRS + Retpoline options
      x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE

commit 5125091d757a251a128ec38d2397c9d160394eac
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Mar 7 18:28:05 2022 +0100

    MAINTAINERS: update Krzysztof Kozlowski's email
    
    Use Krzysztof Kozlowski's @kernel.org account in maintainer entries.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220307172805.156760-1-krzysztof.kozlowski@canonical.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 537c3757b4e3116ad5ab039029b830224f9154d9
Merge: a0e897d1b3679 ebea268ea583b
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Mon Mar 7 23:23:56 2022 +0100

    Merge tag 'tegra-for-5.17-arm64-dt-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into arm/fixes
    
    arm64: tegra: Device tree fixes for v5.17
    
    This contains a single, last-minute fix to disable the display SMMU by
    default because under some circumstances leaving it enabled by default
    can cause SMMU faults on boot.
    
    * tag 'tegra-for-5.17-arm64-dt-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux:
      arm64: tegra: Disable ISO SMMU for Tegra194
    
    Link: https://lore.kernel.org/r/20220307182120.2169598-1-thierry.reding@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit e941dc13fd3717122207d74539ab95da07ef797f
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Fri Mar 4 13:17:33 2022 -0800

    Input: zinitix - do not report shadow fingers
    
    I observed the following problem with the BT404 touch pad
    running the Phosh UI:
    
    When e.g. typing on the virtual keyboard pressing "g" would
    produce "ggg".
    
    After some analysis it turns out the firmware reports that three
    fingers hit that coordinate at the same time, finger 0, 2 and
    4 (of the five available 0,1,2,3,4).
    
    DOWN
      Zinitix-TS 3-0020: finger 0 down (246, 395)
      Zinitix-TS 3-0020: finger 1 up (0, 0)
      Zinitix-TS 3-0020: finger 2 down (246, 395)
      Zinitix-TS 3-0020: finger 3 up (0, 0)
      Zinitix-TS 3-0020: finger 4 down (246, 395)
    UP
      Zinitix-TS 3-0020: finger 0 up (246, 395)
      Zinitix-TS 3-0020: finger 2 up (246, 395)
      Zinitix-TS 3-0020: finger 4 up (246, 395)
    
    This is one touch and release: i.e. this is all reported on
    touch (down) and release.
    
    There is a field in the struct touch_event called finger_cnt
    which is actually a bitmask of the fingers active in the
    event.
    
    Rename this field finger_mask as this matches the use contents
    better, then use for_each_set_bit() to iterate over just the
    fingers that are actally active.
    
    Factor out a finger reporting function zinitix_report_fingers()
    to handle all fingers.
    
    Also be more careful in reporting finger down/up: we were
    reporting every event with input_mt_report_slot_state(..., true);
    but this should only be reported on finger down or move,
    not on finger up, so also add code to check p->sub_status
    to see what is happening and report correctly.
    
    After this my Zinitix BT404 touchscreen report fingers
    flawlessly.
    
    The vendor drive I have notably does not use the "finger_cnt"
    and contains obviously incorrect code like this:
    
      if (touch_dev->touch_info.finger_cnt > MAX_SUPPORTED_FINGER_NUM)
          touch_dev->touch_info.finger_cnt = MAX_SUPPORTED_FINGER_NUM;
    
    As MAX_SUPPORTED_FINGER_NUM is an ordinal and the field is
    a bitmask this seems quite confused.
    
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/20220228233017.2270599-1-linus.walleij@linaro.org
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 1860d30466366774055d993f9b31094ede8af415
Author: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Date:   Mon Mar 7 23:50:59 2022 +0530

    MAINTAINERS: Update git tree for Broadcom iProc SoCs
    
    Current git tree for Broadcom iProc SoCs is pretty outdated as it has
    not updated for a long time. Fix the reference.
    
    Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>

commit ea4424be16887a37735d6550cfd0611528dbe5d9
Merge: 06be3029703fe 42da5a4ba1707
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Mar 7 11:43:22 2022 -0800

    Merge tag 'mtd/fixes-for-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux
    
    Pull MTD fix from Miquel Raynal:
     "As part of a previous changeset introducing support for the K3
      architecture, the OMAP_GPMC (a non visible symbol) got selected by the
      selection of MTD_NAND_OMAP2 instead of doing so from the architecture
      directly (like for the other users of these two drivers). Indeed, from
      a hardware perspective, the OMAP NAND controller needs the GPMC to
      work.
    
      This led to a robot error which got addressed in fix merge into -rc4.
      Unfortunately, the approach at this time still used "select" and lead
      to further build error reports (sparc64:allmodconfig).
    
      This time we switch to 'depends on' in order to prevent random
      misconfigurations. The different dependencies will however need a
      future cleanup"
    
    * tag 'mtd/fixes-for-5.17-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux:
      mtd: rawnand: omap2: Actually prevent invalid configuration and build error

commit 06be3029703fed2099b7247c527ab70d75255178
Merge: aa6f8dcbab473 3dd7d135e75cb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Mar 7 11:32:17 2022 -0800

    Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
    
    Pull virtio fixes from Michael Tsirkin:
     "Some last minute fixes that took a while to get ready. Not
      regressions, but they look safe and seem to be worth to have"
    
    * tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost:
      tools/virtio: handle fallout from folio work
      tools/virtio: fix virtio_test execution
      vhost: remove avail_event arg from vhost_update_avail_event()
      virtio: drop default for virtio-mem
      vdpa: fix use-after-free on vp_vdpa_remove
      virtio-blk: Remove BUG_ON() in virtio_queue_rq()
      virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero
      vhost: fix hung thread due to erroneous iotlb entries
      vduse: Fix returning wrong type in vduse_domain_alloc_iova()
      vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command
      vdpa/mlx5: should verify CTRL_VQ feature exists for MQ
      vdpa: factor out vdpa_set_features_unlocked for vdpa internal use
      virtio_console: break out of buf poll on remove
      virtio: document virtio_reset_device
      virtio: acknowledge all features before access
      virtio: unexport virtio_finalize_features

commit aa6f8dcbab473f3a3c7454b74caa46d36cdc5d13
Author: Halil Pasic <pasic@linux.ibm.com>
Date:   Sat Mar 5 18:07:14 2022 +0100

    swiotlb: rework "fix info leak with DMA_FROM_DEVICE"
    
    Unfortunately, we ended up merging an old version of the patch "fix info
    leak with DMA_FROM_DEVICE" instead of merging the latest one. Christoph
    (the swiotlb maintainer), he asked me to create an incremental fix
    (after I have pointed this out the mix up, and asked him for guidance).
    So here we go.
    
    The main differences between what we got and what was agreed are:
    * swiotlb_sync_single_for_device is also required to do an extra bounce
    * We decided not to introduce DMA_ATTR_OVERWRITE until we have exploiters
    * The implantation of DMA_ATTR_OVERWRITE is flawed: DMA_ATTR_OVERWRITE
      must take precedence over DMA_ATTR_SKIP_CPU_SYNC
    
    Thus this patch removes DMA_ATTR_OVERWRITE, and makes
    swiotlb_sync_single_for_device() bounce unconditionally (that is, also
    when dir == DMA_TO_DEVICE) in order do avoid synchronising back stale
    data from the swiotlb buffer.
    
    Let me note, that if the size used with dma_sync_* API is less than the
    size used with dma_[un]map_*, under certain circumstances we may still
    end up with swiotlb not being transparent. In that sense, this is no
    perfect fix either.
    
    To get this bullet proof, we would have to bounce the entire
    mapping/bounce buffer. For that we would have to figure out the starting
    address, and the size of the mapping in
    swiotlb_sync_single_for_device(). While this does seem possible, there
    seems to be no firm consensus on how things are supposed to work.
    
    Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
    Fixes: ddbd89deb7d3 ("swiotlb: fix info leak with DMA_FROM_DEVICE")
    Cc: stable@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7401b49c50c2b032223de408e28e37cbd63f4c97
Author: Thierry Reding <treding@nvidia.com>
Date:   Mon Mar 7 18:59:09 2022 +0100

    ARM: tegra: Move Nyan FHD panels to AUX bus
    
    Similarly to what was earlier done for other Nyan variants, move the eDP
    panel on the FHD models to the AUX bus as well.
    
    Suggested-by: Dmitry Osipenko <digetx@gmail.com>
    Fixes: ef6fb9875ce0 ("ARM: tegra: Add device-tree for 1080p version of Nyan Big")
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit 58c9a5060cb7cd529d49c93954cdafe81c1d642a
Author: James Morse <james.morse@arm.com>
Date:   Thu Mar 3 16:53:56 2022 +0000

    arm64: proton-pack: Include unprivileged eBPF status in Spectre v2 mitigation reporting
    
    The mitigations for Spectre-BHB are only applied when an exception is
    taken from user-space. The mitigation status is reported via the spectre_v2
    sysfs vulnerabilities file.
    
    When unprivileged eBPF is enabled the mitigation in the exception vectors
    can be avoided by an eBPF program.
    
    When unprivileged eBPF is enabled, print a warning and report vulnerable
    via the sysfs vulnerabilities file.
    
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 42da5a4ba17070e9d99abf375a5bd70e85d2a6b8
Author: Roger Quadros <rogerq@kernel.org>
Date:   Sat Feb 19 21:36:00 2022 +0200

    mtd: rawnand: omap2: Actually prevent invalid configuration and build error
    
    The root of the problem is that we are selecting symbols that have
    dependencies. This can cause random configurations that can fail.
    The cleanest solution is to avoid using select.
    
    This driver uses interfaces from the OMAP_GPMC driver so we have to
    depend on it instead.
    
    Fixes: 4cd335dae3cf ("mtd: rawnand: omap2: Prevent invalid configuration and build error")
    Signed-off-by: Roger Quadros <rogerq@kernel.org>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Tested-by: Randy Dunlap <rdunlap@infradead.org>
    Link: https://lore.kernel.org/linux-mtd/20220219193600.24892-1-rogerq@kernel.org

commit 0c4bcfdecb1ac0967619ee7ff44871d93c08c909
Author: Miklos Szeredi <mszeredi@redhat.com>
Date:   Mon Mar 7 16:30:44 2022 +0100

    fuse: fix pipe buffer lifetime for direct_io
    
    In FOPEN_DIRECT_IO mode, fuse_file_write_iter() calls
    fuse_direct_write_iter(), which normally calls fuse_direct_io(), which then
    imports the write buffer with fuse_get_user_pages(), which uses
    iov_iter_get_pages() to grab references to userspace pages instead of
    actually copying memory.
    
    On the filesystem device side, these pages can then either be read to
    userspace (via fuse_dev_read()), or splice()d over into a pipe using
    fuse_dev_splice_read() as pipe buffers with &nosteal_pipe_buf_ops.
    
    This is wrong because after fuse_dev_do_read() unlocks the FUSE request,
    the userspace filesystem can mark the request as completed, causing write()
    to return. At that point, the userspace filesystem should no longer have
    access to the pipe buffer.
    
    Fix by copying pages coming from the user address space to new pipe
    buffers.
    
    Reported-by: Jann Horn <jannh@google.com>
    Fixes: c3021629a0d8 ("fuse: support splice() reading from fuse device")
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

commit 804f468853179b9b58af05c153c411931aa5b310
Author: Jouni Högander <jouni.hogander@intel.com>
Date:   Fri Feb 25 09:02:28 2022 +0200

    drm/i915/psr: Set "SF Partial Frame Enable" also on full update
    
    Currently we are observing occasional screen flickering when
    PSR2 selective fetch is enabled. More specifically glitch seems
    to happen on full frame update when cursor moves to coords
    x = -1 or y = -1.
    
    According to Bspec SF Single full frame should not be set if
    SF Partial Frame Enable is not set. This happened to be true for
    ADLP as PSR2_MAN_TRK_CTL_ENABLE is always set and for ADL_P it's
    actually "SF Partial Frame Enable" (Bit 31).
    
    Setting "SF Partial Frame Enable" bit also on full update seems to
    fix screen flickering.
    
    Also make code more clear by setting PSR2_MAN_TRK_CTL_ENABLE
    only if not on ADL_P. Bit 31 has different meaning in ADL_P.
    
    Bspec: 49274
    
    v2: Fix Mihai Harpau email address
    v3: Modify commit message and remove unnecessary comment
    
    Tested-by: Lyude Paul <lyude@redhat.com>
    Fixes: 7f6002e58025 ("drm/i915/display: Enable PSR2 selective fetch by default")
    Reported-by: Lyude Paul <lyude@redhat.com>
    Cc: Mihai Harpau <mharpau@gmail.com>
    Cc: José Roberto de Souza <jose.souza@intel.com>
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Bugzilla: https://gitlab.freedesktop.org/drm/intel/-/issues/5077
    Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
    Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
    Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220225070228.855138-1-jouni.hogander@intel.com
    (cherry picked from commit 8d5516d18b323cf7274d1cf5fe76f4a691f879c6)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 660c619b9d7ccd28648ee3766cdbe94ec7b27402
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Mon Mar 7 13:56:23 2022 +0200

    gpiolib: acpi: Convert ACPI value of debounce to microseconds
    
    It appears that GPIO ACPI library uses ACPI debounce values directly.
    However, the GPIO library APIs expect the debounce timeout to be in
    microseconds.
    
    Convert ACPI value of debounce to microseconds.
    
    While at it, document this detail where it is appropriate.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215664
    Reported-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Fixes: 8dcb7a15a585 ("gpiolib: acpi: Take into account debounce settings")
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Tested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit fc328a7d1fcce263db0b046917a66f3aa6e68719
Author: Marcelo Roberto Jimenez <marcelo.jimenez@gmail.com>
Date:   Mon Mar 7 10:57:24 2022 +0100

    gpio: Revert regression in sysfs-gpio (gpiolib.c)
    
    Some GPIO lines have stopped working after the patch
    commit 2ab73c6d8323f ("gpio: Support GPIO controllers without pin-ranges")
    
    And this has supposedly been fixed in the following patches
    commit 89ad556b7f96a ("gpio: Avoid using pin ranges with !PINCTRL")
    commit 6dbbf84603961 ("gpiolib: Don't free if pin ranges are not defined")
    
    But an erratic behavior where some GPIO lines work while others do not work
    has been introduced.
    
    This patch reverts those changes so that the sysfs-gpio interface works
    properly again.
    
    Signed-off-by: Marcelo Roberto Jimenez <marcelo.jimenez@gmail.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 5f84e73f9a8f14b95115b0eb2080da6d9fa7a82e
Author: Akhil R <akhilrajeev@nvidia.com>
Date:   Mon Feb 28 21:04:05 2022 +0530

    gpio: tegra186: Add IRQ per bank for Tegra241
    
    Add the number of interrupts per bank for Tegra241 (Grace) to
    fix the probe failure.
    
    Fixes: d1056b771ddb ("gpio: tegra186: Add support for Tegra241")
    Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit c70c453abcbf3ecbaadd4c3236a5119b8da365cf
Author: Fabio Estevam <festevam@denx.de>
Date:   Sat Mar 5 17:47:20 2022 -0300

    smsc95xx: Ignore -ENODEV errors when device is unplugged
    
    According to Documentation/driver-api/usb/URB.rst when a device
    is unplugged usb_submit_urb() returns -ENODEV.
    
    This error code propagates all the way up to usbnet_read_cmd() and
    usbnet_write_cmd() calls inside the smsc95xx.c driver during
    Ethernet cable unplug, unbind or reboot.
    
    This causes the following errors to be shown on reboot, for example:
    
    ci_hdrc ci_hdrc.1: remove, state 1
    usb usb2: USB disconnect, device number 1
    usb 2-1: USB disconnect, device number 2
    usb 2-1.1: USB disconnect, device number 3
    smsc95xx 2-1.1:1.0 eth1: unregister 'smsc95xx' usb-ci_hdrc.1-1.1, smsc95xx USB 2.0 Ethernet
    smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
    smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
    smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
    smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
    smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
    smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
    smsc95xx 2-1.1:1.0 eth1: hardware isn't capable of remote wakeup
    usb 2-1.4: USB disconnect, device number 4
    ci_hdrc ci_hdrc.1: USB bus 2 deregistered
    ci_hdrc ci_hdrc.0: remove, state 4
    usb usb1: USB disconnect, device number 1
    ci_hdrc ci_hdrc.0: USB bus 1 deregistered
    imx2-wdt 30280000.watchdog: Device shutdown: Expect reboot!
    reboot: Restarting system
    
    Ignore the -ENODEV errors inside __smsc95xx_mdio_read() and
    __smsc95xx_phy_wait_not_busy() and do not print error messages
    when -ENODEV is returned.
    
    Fixes: a049a30fc27c ("net: usb: Correct PHY handling of smsc95xx")
    Signed-off-by: Fabio Estevam <festevam@denx.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d9dc0c84ad2d4cc911ba252c973d1bf18d5eb9cf
Author: Tom Rix <trix@redhat.com>
Date:   Sat Mar 5 07:06:42 2022 -0800

    qed: return status of qed_iov_get_link
    
    Clang static analysis reports this issue
    qed_sriov.c:4727:19: warning: Assigned value is
      garbage or undefined
      ivi->max_tx_rate = tx_rate ? tx_rate : link.speed;
                       ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    link is only sometimes set by the call to qed_iov_get_link()
    qed_iov_get_link fails without setting link or returning
    status.  So change the decl to return status.
    
    Fixes: 73390ac9d82b ("qed*: support ndo_get_vf_config")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 23c7f8d7989e1646aac82f75761b7648c355cb8a
Author: Steffen Klassert <steffen.klassert@secunet.com>
Date:   Mon Mar 7 13:11:41 2022 +0100

    net: Fix esp GSO on inter address family tunnels.
    
    The esp tunnel GSO handlers use skb_mac_gso_segment to
    push the inner packet to the segmentation handlers.
    However, skb_mac_gso_segment takes the Ethernet Protocol
    ID from 'skb->protocol' which is wrong for inter address
    family tunnels. We fix this by introducing a new
    skb_eth_gso_segment function.
    
    This function can be used if it is necessary to pass the
    Ethernet Protocol ID directly to the segmentation handler.
    First users of this function will be the esp4 and esp6
    tunnel segmentation handlers.
    
    Fixes: c35fe4106b92 ("xfrm: Add mode handlers for IPsec on layer 2")
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 053c8fdf2c930efdff5496960842bbb5c34ad43a
Author: Steffen Klassert <steffen.klassert@secunet.com>
Date:   Mon Mar 7 13:11:40 2022 +0100

    esp: Fix BEET mode inter address family tunneling on GSO
    
    The xfrm{4,6}_beet_gso_segment() functions did not correctly set the
    SKB_GSO_IPXIP4 and SKB_GSO_IPXIP6 gso types for the address family
    tunneling case. Fix this by setting these gso types.
    
    Fixes: 384a46ea7bdc7 ("esp4: add gso_segment for esp4 beet mode")
    Fixes: 7f9e40eb18a99 ("esp6: add gso_segment for esp6 beet mode")
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit ebe48d368e97d007bfeb76fcb065d6cfc4c96645
Author: Steffen Klassert <steffen.klassert@secunet.com>
Date:   Mon Mar 7 13:11:39 2022 +0100

    esp: Fix possible buffer overflow in ESP transformation
    
    The maximum message size that can be send is bigger than
    the  maximum site that skb_page_frag_refill can allocate.
    So it is possible to write beyond the allocated buffer.
    
    Fix this by doing a fallback to COW in that case.
    
    v2:
    
    Avoid get get_order() costs as suggested by Linus Torvalds.
    
    Fixes: cac2661c53f3 ("esp4: Avoid skb_cow_data whenever possible")
    Fixes: 03e2a30f6a27 ("esp6: Avoid skb_cow_data whenever possible")
    Reported-by: valis <sec@valis.email>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit bb77bd31c281f70ec77c9c4f584950a779e05cf8
Author: Zheyu Ma <zheyuma97@gmail.com>
Date:   Sat Mar 5 14:55:04 2022 +0000

    ethernet: sun: Free the coherent when failing in probing
    
    When the driver fails to register net device, it should free the DMA
    region first, and then do other cleanup.
    
    Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dd830aed23c6e07cd8e2a163742bf3d63c9add08
Author: Aleksander Jan Bajkowski <olek2@wp.pl>
Date:   Sat Mar 5 12:20:39 2022 +0100

    net: lantiq_xrx200: fix use after free bug
    
    The skb->len field is read after the packet is sent to the network
    stack. In the meantime, skb can be freed. This patch fixes this bug.
    
    Fixes: c3e6b2c35b34 ("net: lantiq_xrx200: add ingress SG DMA support")
    Reported-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
    Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e0058f0fa80f6e09c4d363779c241c45a3c56b94
Author: Jia-Ju Bai <baijiaju1990@gmail.com>
Date:   Sat Mar 5 01:14:11 2022 -0800

    net: qlogic: check the return value of dma_alloc_coherent() in qed_vf_hw_prepare()
    
    The function dma_alloc_coherent() in qed_vf_hw_prepare() can fail, so
    its return value should be checked.
    
    Fixes: 1408cc1fa48c ("qed: Introduce VFs")
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d0aeb0d4a3f7d2a0df7e9545892bbeede8f2ac7e
Author: Jia-Ju Bai <baijiaju1990@gmail.com>
Date:   Sat Mar 5 00:58:16 2022 -0800

    isdn: hfcpci: check the return value of dma_set_mask() in setup_hw()
    
    The function dma_set_mask() in setup_hw() can fail, so its return value
    should be checked.
    
    Fixes: 1700fe1a10dc ("Add mISDN HFC PCI driver")
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1760fdb6fe9f796fbdb9b4106b3e0bbacc16b55c
Author: Ulf Hansson <ulf.hansson@linaro.org>
Date:   Fri Mar 4 11:56:56 2022 +0100

    mmc: core: Restore (almost) the busy polling for MMC_SEND_OP_COND
    
    Commit 76bfc7ccc2fa ("mmc: core: adjust polling interval for CMD1"),
    significantly decreased the polling period from ~10-12ms into just a couple
    of us. The purpose was to decrease the total time spent in the busy polling
    loop, but unfortunate it has lead to problems, that causes eMMC cards to
    never gets out busy and thus fails to be initialized.
    
    To fix the problem, but also to try to keep some of the new improved
    behaviour, let's start by using a polling period of 1-2ms, which then
    increases for each loop, according to common polling loop in
    __mmc_poll_for_busy().
    
    Reported-by: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>
    Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
    Cc: Huijin Park <huijin.park@samsung.com>
    Fixes: 76bfc7ccc2fa ("mmc: core: adjust polling interval for CMD1")
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
    Tested-by: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>
    Tested-by: H. Nikolaus Schaller <hns@goldelico.com>
    Link: https://lore.kernel.org/r/20220304105656.149281-1-ulf.hansson@linaro.org

commit 66e3531b33ee51dad17c463b4d9c9f52e341503d
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:55 2022 +0100

    xen/netfront: react properly to failing gnttab_end_foreign_access_ref()
    
    When calling gnttab_end_foreign_access_ref() the returned value must
    be tested and the reaction to that value should be appropriate.
    
    In case of failure in xennet_get_responses() the reaction should not be
    to crash the system, but to disable the network device.
    
    The calls in setup_netfront() can be replaced by calls of
    gnttab_end_foreign_access(). While at it avoid double free of ring
    pages and grant references via xennet_disconnect_backend() in this case.
    
    This is CVE-2022-23042 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V2:
    - avoid double free
    V3:
    - remove pointless initializer (Jan Beulich)

commit 42baefac638f06314298087394b982ead9ec444b
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:55 2022 +0100

    xen/gnttab: fix gnttab_end_foreign_access() without page specified
    
    gnttab_end_foreign_access() is used to free a grant reference and
    optionally to free the associated page. In case the grant is still in
    use by the other side processing is being deferred. This leads to a
    problem in case no page to be freed is specified by the caller: the
    caller doesn't know that the page is still mapped by the other side
    and thus should not be used for other purposes.
    
    The correct way to handle this situation is to take an additional
    reference to the granted page in case handling is being deferred and
    to drop that reference when the grant reference could be freed
    finally.
    
    This requires that there are no users of gnttab_end_foreign_access()
    left directly repurposing the granted page after the call, as this
    might result in clobbered data or information leaks via the not yet
    freed grant reference.
    
    This is part of CVE-2022-23041 / XSA-396.
    
    Reported-by: Simon Gaiser <simon@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V4:
    - expand comment in header
    V5:
    - get page ref in case of kmalloc() failure, too

commit b0576cc9c6b843d99c6982888d59a56209341888
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:55 2022 +0100

    xen/pvcalls: use alloc/free_pages_exact()
    
    Instead of __get_free_pages() and free_pages() use alloc_pages_exact()
    and free_pages_exact(). This is in preparation of a change of
    gnttab_end_foreign_access() which will prohibit use of high-order
    pages.
    
    This is part of CVE-2022-23041 / XSA-396.
    
    Reported-by: Simon Gaiser <simon@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V4:
    - new patch

commit 5cadd4bb1d7fc9ab201ac14620d1a478357e4ebd
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:55 2022 +0100

    xen/9p: use alloc/free_pages_exact()
    
    Instead of __get_free_pages() and free_pages() use alloc_pages_exact()
    and free_pages_exact(). This is in preparation of a change of
    gnttab_end_foreign_access() which will prohibit use of high-order
    pages.
    
    By using the local variable "order" instead of ring->intf->ring_order
    in the error path of xen_9pfs_front_alloc_dataring() another bug is
    fixed, as the error path can be entered before ring->intf->ring_order
    is being set.
    
    By using alloc_pages_exact() the size in bytes is specified for the
    allocation, which fixes another bug for the case of
    order < (PAGE_SHIFT - XEN_PAGE_SHIFT).
    
    This is part of CVE-2022-23041 / XSA-396.
    
    Reported-by: Simon Gaiser <simon@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V4:
    - new patch

commit cd7bcfab4e73dcb3de92c2014c19f17af3864bfe
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:55 2022 +0100

    xen/usb: don't use gnttab_end_foreign_access() in xenhcd_gnttab_done()
    
    The usage of gnttab_end_foreign_access() in xenhcd_gnttab_done() is
    not safe against a malicious backend, as the backend could keep the
    I/O page mapped and modify it even after the granted memory page is
    being used for completely other purposes in the local system.
    
    So replace that use case with gnttab_try_end_foreign_access() and
    disable the PV host adapter in case the backend didn't stop using the
    granted page.
    
    In xenhcd_urb_request_done() immediately return in case of setting
    the device state to "error" instead of looking into further backend
    responses.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V2:
    - use gnttab_try_end_foreign_access()

commit 1dbd11ca75fe664d3e54607547771d021f531f59
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen: remove gnttab_query_foreign_access()
    
    Remove gnttab_query_foreign_access(), as it is unused and unsafe to
    use.
    
    All previous use cases assumed a grant would not be in use after
    gnttab_query_foreign_access() returned 0. This information is useless
    in best case, as it only refers to a situation in the past, which could
    have changed already.
    
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>

commit d3b6372c5881cb54925212abb62c521df8ba4809
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/gntalloc: don't use gnttab_query_foreign_access()
    
    Using gnttab_query_foreign_access() is unsafe, as it is racy by design.
    
    The use case in the gntalloc driver is not needed at all. While at it
    replace the call of gnttab_end_foreign_access_ref() with a call of
    gnttab_end_foreign_access(), which is what is really wanted there. In
    case the grant wasn't used due to an allocation failure, just free the
    grant via gnttab_free_grant_reference().
    
    This is CVE-2022-23039 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V3:
    - fix __del_gref() (Jan Beulich)

commit 33172ab50a53578a95691310f49567c9266968b0
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/scsifront: don't use gnttab_query_foreign_access() for mapped status
    
    It isn't enough to check whether a grant is still being in use by
    calling gnttab_query_foreign_access(), as a mapping could be realized
    by the other side just after having called that function.
    
    In case the call was done in preparation of revoking a grant it is
    better to do so via gnttab_try_end_foreign_access() and check the
    success of that operation instead.
    
    This is CVE-2022-23038 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V2:
    - use gnttab_try_end_foreign_access()

commit 31185df7e2b1d2fa1de4900247a12d7b9c7087eb
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/netfront: don't use gnttab_query_foreign_access() for mapped status
    
    It isn't enough to check whether a grant is still being in use by
    calling gnttab_query_foreign_access(), as a mapping could be realized
    by the other side just after having called that function.
    
    In case the call was done in preparation of revoking a grant it is
    better to do so via gnttab_end_foreign_access_ref() and check the
    success of that operation instead.
    
    This is CVE-2022-23037 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V2:
    - use gnttab_try_end_foreign_access()
    V3:
    - don't use gnttab_try_end_foreign_access()

commit abf1fd5919d6238ee3bc5eb4a9b6c3947caa6638
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/blkfront: don't use gnttab_query_foreign_access() for mapped status
    
    It isn't enough to check whether a grant is still being in use by
    calling gnttab_query_foreign_access(), as a mapping could be realized
    by the other side just after having called that function.
    
    In case the call was done in preparation of revoking a grant it is
    better to do so via gnttab_end_foreign_access_ref() and check the
    success of that operation instead.
    
    For the ring allocation use alloc_pages_exact() in order to avoid
    high order pages in case of a multi-page ring.
    
    If a grant wasn't unmapped by the backend without persistent grants
    being used, set the device state to "error".
    
    This is CVE-2022-23036 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
    ---
    V2:
    - use gnttab_try_end_foreign_access()
    V4:
    - use alloc_pages_exact() and free_pages_exact()
    - set state to error if backend didn't unmap (Roger Pau Monné)

commit 6b1775f26a2da2b05a6dc8ec2b5d14e9a4701a1a
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/grant-table: add gnttab_try_end_foreign_access()
    
    Add a new grant table function gnttab_try_end_foreign_access(), which
    will remove and free a grant if it is not in use.
    
    Its main use case is to either free a grant if it is no longer in use,
    or to take some other action if it is still in use. This other action
    can be an error exit, or (e.g. in the case of blkfront persistent grant
    feature) some special handling.
    
    This is CVE-2022-23036, CVE-2022-23038 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>
    ---
    V2:
    - new patch
    V4:
    - add comments to header (Jan Beulich)

commit 3777ea7bac3113005b7180e6b9dadf16d19a5827
Author: Juergen Gross <jgross@suse.com>
Date:   Mon Mar 7 09:48:54 2022 +0100

    xen/xenbus: don't let xenbus_grant_ring() remove grants in error case
    
    Letting xenbus_grant_ring() tear down grants in the error case is
    problematic, as the other side could already have used these grants.
    Calling gnttab_end_foreign_access_ref() without checking success is
    resulting in an unclear situation for any caller of xenbus_grant_ring()
    as in the error case the memory pages of the ring page might be
    partially mapped. Freeing them would risk unwanted foreign access to
    them, while not freeing them would leak memory.
    
    In order to remove the need to undo any gnttab_grant_foreign_access()
    calls, use gnttab_alloc_grant_references() to make sure no further
    error can occur in the loop granting access to the ring pages.
    
    It should be noted that this way of handling removes leaking of
    grant entries in the error case, too.
    
    This is CVE-2022-23040 / part of XSA-396.
    
    Reported-by: Demi Marie Obenour <demi@invisiblethingslab.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>

commit 48015b632f770c401f3816f144499a39f2884677
Author: Michael Ellerman <mpe@ellerman.id.au>
Date:   Fri Feb 11 17:32:37 2022 +1100

    powerpc: Fix STACKTRACE=n build
    
    Our skiroot_defconfig doesn't enable FTRACE, and so doesn't get
    STACKTRACE enabled either. That leads to a build failure since commit
    1614b2b11fab ("arch: Make ARCH_STACKWALK independent of STACKTRACE")
    made stacktrace.c build even when STACKTRACE=n.
    
      arch/powerpc/kernel/stacktrace.c: In function ‘handle_backtrace_ipi’:
      arch/powerpc/kernel/stacktrace.c:171:2: error: implicit declaration of function ‘nmi_cpu_backtrace’
        171 |  nmi_cpu_backtrace(regs);
            |  ^~~~~~~~~~~~~~~~~
      arch/powerpc/kernel/stacktrace.c: In function ‘arch_trigger_cpumask_backtrace’:
      arch/powerpc/kernel/stacktrace.c:226:2: error: implicit declaration of function ‘nmi_trigger_cpumask_backtrace’
        226 |  nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
            |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    This happens because our headers haven't defined
    arch_trigger_cpumask_backtrace, which causes lib/nmi_backtrace.c not to
    build nmi_cpu_backtrace().
    
    The code in question doesn't actually depend on STACKTRACE=y, that was
    just added because arch_trigger_cpumask_backtrace() lived in
    stacktrace.c for convenience. So drop the dependency on
    CONFIG_STACKTRACE, that causes lib/nmi_backtrace.c to build
    nmi_cpu_backtrace() etc. and fixes the build.
    
    Fixes: 1614b2b11fab ("arch: Make ARCH_STACKWALK independent of STACKTRACE")
    [mpe: Cherry pick of 5a72345e6a78 from next into fixes]
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220212111349.2806972-1-mpe@ellerman.id.au

commit ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 6 14:28:31 2022 -0800

    Linux 5.17-rc7

commit 3ee65c0f0778b8fa95381cd7676cde2c03e0f889
Merge: f81664f760046 ca93e44bfb5fd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 6 12:19:36 2022 -0800

    Merge tag 'for-5.17-rc6-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs fixes from David Sterba:
     "A few more fixes for various problems that have user visible effects
      or seem to be urgent:
    
       - fix corruption when combining DIO and non-blocking io_uring over
         multiple extents (seen on MariaDB)
    
       - fix relocation crash due to premature return from commit
    
       - fix quota deadlock between rescan and qgroup removal
    
       - fix item data bounds checks in tree-checker (found on a fuzzed
         image)
    
       - fix fsync of prealloc extents after EOF
    
       - add missing run of delayed items after unlink during log replay
    
       - don't start relocation until snapshot drop is finished
    
       - fix reversed condition for subpage writers locking
    
       - fix warning on page error"
    
    * tag 'for-5.17-rc6-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
      btrfs: fallback to blocking mode when doing async dio over multiple extents
      btrfs: add missing run of delayed items after unlink during log replay
      btrfs: qgroup: fix deadlock between rescan worker and remove qgroup
      btrfs: fix relocation crash due to premature return from btrfs_commit_transaction()
      btrfs: do not start relocation until in progress drops are done
      btrfs: tree-checker: use u64 for item data end to avoid overflow
      btrfs: do not WARN_ON() if we have PageError set
      btrfs: fix lost prealloc extents beyond eof after full fsync
      btrfs: subpage: fix a wrong check on subpage->writers

commit f81664f760046ac9b5731d9340f9e48e70ea7c8d
Merge: 9bdeaca18bf61 8d25b7beca7ed
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 6 12:08:42 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "x86 guest:
    
       - Tweaks to the paravirtualization code, to avoid using them when
         they're pointless or harmful
    
      x86 host:
    
       - Fix for SRCU lockdep splat
    
       - Brown paper bag fix for the propagation of errno"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      KVM: x86: pull kvm->srcu read-side to kvm_arch_vcpu_ioctl_run
      KVM: x86/mmu: Passing up the error state of mmu_alloc_shadow_roots()
      KVM: x86: Yield to IPI target vCPU only if it is busy
      x86/kvmclock: Fix Hyper-V Isolated VM's boot issue when vCPUs > 64
      x86/kvm: Don't waste memory if kvmclock is disabled
      x86/kvm: Don't use PV TLB/yield when mwait is advertised

commit 9bdeaca18bf61d55029277bb35f72c2002c88c4d
Merge: f40a33f5ea54c 58dbe9b373df2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 6 11:57:42 2022 -0800

    Merge tag 'powerpc-5.17-5' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc fix from Michael Ellerman:
     "Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set.
    
      Thanks to Murilo Opsfelder Araujo, and Erhard F"
    
    * tag 'powerpc-5.17-5' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set

commit f40a33f5ea54c01d640b150eb63e94defeb9b614
Merge: dcde98da99707 1d02b444b8d13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Mar 6 11:47:59 2022 -0800

    Merge tag 'trace-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing fixes from Steven Rostedt:
    
     - Fix sorting on old "cpu" value in histograms
    
     - Fix return value of __setup() boot parameter handlers
    
    * tag 'trace-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      tracing: Fix return value of __setup handlers
      tracing/histogram: Fix sorting on old "cpu" value

commit 3dd7d135e75cb37c8501ba02977332a2a487dd39
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Fri Mar 4 12:10:38 2022 -0500

    tools/virtio: handle fallout from folio work
    
    just add a stub
    
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 32f1b53fe8f03d962423ba81f8e92af5839814da
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Tue Jan 18 16:06:31 2022 +0100

    tools/virtio: fix virtio_test execution
    
    virtio_test hangs on __vring_new_virtqueue() because `vqs_list_lock`
    is not initialized.
    
    Let's initialize it in vdev_info_init().
    
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Link: https://lore.kernel.org/r/20220118150631.167015-1-sgarzare@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 4c8093637bc9f8cc2e41eed343c12f85d6ff9e25
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Thu Jan 13 15:11:34 2022 +0100

    vhost: remove avail_event arg from vhost_update_avail_event()
    
    In vhost_update_avail_event() we never used the `avail_event` argument,
    since its introduction in commit 2723feaa8ec6 ("vhost: set log when
    updating used flags or avail event").
    
    Let's remove it to clean up the code.
    
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Link: https://lore.kernel.org/r/20220113141134.186773-1-sgarzare@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit e7c552ec897894ec421867059e48474eb7f1ff6d
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Fri Feb 25 06:46:34 2022 -0500

    virtio: drop default for virtio-mem
    
    There's no special reason why virtio-mem needs a default that's
    different from what kconfig provides, any more than e.g. virtio blk.
    
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: David Hildenbrand <david@redhat.com>

commit eb057b44dbe35ae14527830236a92f51de8f9184
Author: Zhang Min <zhang.min9@zte.com.cn>
Date:   Tue Mar 1 17:10:59 2022 +0800

    vdpa: fix use-after-free on vp_vdpa_remove
    
    When vp_vdpa driver is unbind, vp_vdpa is freed in vdpa_unregister_device
    and then vp_vdpa->mdev.pci_dev is dereferenced in vp_modern_remove,
    triggering use-after-free.
    
    Call Trace of unbinding driver free vp_vdpa :
    do_syscall_64
      vfs_write
        kernfs_fop_write_iter
          device_release_driver_internal
            pci_device_remove
              vp_vdpa_remove
                vdpa_unregister_device
                  kobject_release
                    device_release
                      kfree
    
    Call Trace of dereference vp_vdpa->mdev.pci_dev:
    vp_modern_remove
      pci_release_selected_regions
        pci_release_region
          pci_resource_len
            pci_resource_end
              (dev)->resource[(bar)].end
    
    Signed-off-by: Zhang Min <zhang.min9@zte.com.cn>
    Signed-off-by: Yi Wang <wang.yi59@zte.com.cn>
    Link: https://lore.kernel.org/r/20220301091059.46869-1-wang.yi59@zte.com.cn
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Fixes: 64b9f64f80a6 ("vdpa: introduce virtio pci driver")
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

commit e030759a1ddcbf61d42b6e996bfeb675e0032d8b
Author: Xie Yongji <xieyongji@bytedance.com>
Date:   Fri Mar 4 18:00:58 2022 +0800

    virtio-blk: Remove BUG_ON() in virtio_queue_rq()
    
    Currently we have a BUG_ON() to make sure the number of sg
    list does not exceed queue_max_segments() in virtio_queue_rq().
    However, the block layer uses queue_max_discard_segments()
    instead of queue_max_segments() to limit the sg list for
    discard requests. So the BUG_ON() might be triggered if
    virtio-blk device reports a larger value for max discard
    segment than queue_max_segments(). To fix it, let's simply
    remove the BUG_ON() which has become unnecessary after commit
    02746e26c39e("virtio-blk: avoid preallocating big SGL for data").
    And the unused vblk->sg_elems can also be removed together.
    
    Fixes: 1f23816b8eb8 ("virtio_blk: add discard and write zeroes support")
    Suggested-by: Christoph Hellwig <hch@infradead.org>
    Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
    Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
    Link: https://lore.kernel.org/r/20220304100058.116-2-xieyongji@bytedance.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit dacc73ed0b88f1a787ec20385f42ca9dd9eddcd0
Author: Xie Yongji <xieyongji@bytedance.com>
Date:   Fri Mar 4 18:00:57 2022 +0800

    virtio-blk: Don't use MAX_DISCARD_SEGMENTS if max_discard_seg is zero
    
    Currently the value of max_discard_segment will be set to
    MAX_DISCARD_SEGMENTS (256) with no basis in hardware if device
    set 0 to max_discard_seg in configuration space. It's incorrect
    since the device might not be able to handle such large descriptors.
    To fix it, let's follow max_segments restrictions in this case.
    
    Fixes: 1f23816b8eb8 ("virtio_blk: add discard and write zeroes support")
    Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
    Link: https://lore.kernel.org/r/20220304100058.116-1-xieyongji@bytedance.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit e2ae38cf3d91837a493cb2093c87700ff3cbe667
Author: Anirudh Rayabharam <mail@anirudhrb.com>
Date:   Sat Mar 5 15:25:25 2022 +0530

    vhost: fix hung thread due to erroneous iotlb entries
    
    In vhost_iotlb_add_range_ctx(), range size can overflow to 0 when
    start is 0 and last is ULONG_MAX. One instance where it can happen
    is when userspace sends an IOTLB message with iova=size=uaddr=0
    (vhost_process_iotlb_msg). So, an entry with size = 0, start = 0,
    last = ULONG_MAX ends up in the iotlb. Next time a packet is sent,
    iotlb_access_ok() loops indefinitely due to that erroneous entry.
    
            Call Trace:
             <TASK>
             iotlb_access_ok+0x21b/0x3e0 drivers/vhost/vhost.c:1340
             vq_meta_prefetch+0xbc/0x280 drivers/vhost/vhost.c:1366
             vhost_transport_do_send_pkt+0xe0/0xfd0 drivers/vhost/vsock.c:104
             vhost_worker+0x23d/0x3d0 drivers/vhost/vhost.c:372
             kthread+0x2e9/0x3a0 kernel/kthread.c:377
             ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
             </TASK>
    
    Reported by syzbot at:
            https://syzkaller.appspot.com/bug?extid=0abd373e2e50d704db87
    
    To fix this, do two things:
    
    1. Return -EINVAL in vhost_chr_write_iter() when userspace asks to map
       a range with size 0.
    2. Fix vhost_iotlb_add_range_ctx() to handle the range [0, ULONG_MAX]
       by splitting it into two entries.
    
    Fixes: 0bbe30668d89e ("vhost: factor out IOTLB")
    Reported-by: syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com
    Tested-by: syzbot+0abd373e2e50d704db87@syzkaller.appspotmail.com
    Signed-off-by: Anirudh Rayabharam <mail@anirudhrb.com>
    Link: https://lore.kernel.org/r/20220305095525.5145-1-mail@anirudhrb.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit afb3cc1a397d77771f342691b7e6b032a234d7f2
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Mar 3 16:08:40 2022 +0200

    net: dsa: unlock the rtnl_mutex when dsa_master_setup() fails
    
    After the blamed commit, dsa_tree_setup_master() may exit without
    calling rtnl_unlock(), fix that.
    
    Fixes: c146f9bc195a ("net: dsa: hold rtnl_mutex when calling dsa_master_{setup,teardown}")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a3d9001b4e287fc043e5539d03d71a32ab114bcb
Author: Kai Lueke <kailueke@linux.microsoft.com>
Date:   Thu Mar 3 15:55:10 2022 +0100

    Revert "xfrm: state and policy should fail if XFRMA_IF_ID 0"
    
    This reverts commit 68ac0f3810e76a853b5f7b90601a05c3048b8b54 because ID
    0 was meant to be used for configuring the policy/state without
    matching for a specific interface (e.g., Cilium is affected, see
    https://github.com/cilium/cilium/pull/18789 and
    https://github.com/cilium/cilium/pull/19019).
    
    Signed-off-by: Kai Lueke <kailueke@linux.microsoft.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit dcde98da997075053041942ecf97d787855722ec
Merge: 0014404f9c18d 327b89f0acc4c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 5 15:49:45 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
    
    Pull input updates from Dmitry Torokhov:
    
     - a fixup for Goodix touchscreen driver allowing it to work on certain
       Cherry Trail devices
    
     - a fix for imbalanced enable/disable regulator in Elam touchpad driver
       that became apparent when used with Asus TF103C 2-in-1 dock
    
     - a couple new input keycodes used on newer keyboards
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
      HID: add mapping for KEY_ALL_APPLICATIONS
      HID: add mapping for KEY_DICTATE
      Input: elan_i2c - fix regulator enable count imbalance after suspend/resume
      Input: elan_i2c - move regulator_[en|dis]able() out of elan_[en|dis]able_power()
      Input: goodix - workaround Cherry Trail devices with a bogus ACPI Interrupt() resource
      Input: goodix - use the new soc_intel_is_byt() helper
      Input: samsung-keypad - properly state IOMEM dependency

commit 0014404f9c18dd360a1b8bb4243643c679ce99bf
Merge: f9026e19a44d9 d1eff16d727ff
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 5 12:03:14 2022 -0800

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "8 patches.
    
      Subsystems affected by this patch series: mm (hugetlb, pagemap, and
      userfaultfd), memfd, selftests, and kconfig"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      configs/debug: set CONFIG_DEBUG_INFO=y properly
      proc: fix documentation and description of pagemap
      kselftest/vm: fix tests build with old libc
      memfd: fix F_SEAL_WRITE after shmem huge page allocated
      mm: fix use-after-free when anon vma name is used after vma is freed
      mm: prevent vm_area_struct::anon_name refcount saturation
      mm: refactor vm_area_struct::anon_vma_name usage code
      selftests/vm: cleanup hugetlb file after mremap test

commit f9026e19a44d965793d25e7a02b0d6c1bcafd8f5
Merge: ac84e82f78cb5 c194dad21025d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Mar 5 11:25:26 2022 -0800

    Merge tag 's390-5.17-5' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
    
    Pull s390 fixes from Vasily Gorbik:
    
     - Fix HAVE_DYNAMIC_FTRACE_WITH_ARGS implementation by providing correct
       switching between ftrace_caller/ftrace_regs_caller and supplying
       pt_regs only when ftrace_regs_caller is activated.
    
     - Fix exception table sorting.
    
     - Fix breakage of kdump tooling by preserving metadata it cannot
       function without.
    
    * tag 's390-5.17-5' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
      s390/extable: fix exception table sorting
      s390/ftrace: fix arch_ftrace_get_regs implementation
      s390/ftrace: fix ftrace_caller/ftrace_regs_caller generation
      s390/setup: preserve memory at OLDMEM_BASE and OLDMEM_SIZE

commit d1eff16d727ff257b706d32114d3881f67cc9c75
Author: Qian Cai <quic_qiancai@quicinc.com>
Date:   Fri Mar 4 20:29:10 2022 -0800

    configs/debug: set CONFIG_DEBUG_INFO=y properly
    
    CONFIG_DEBUG_INFO can't be set by user directly, so set
    CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y instead.
    
    Otherwise, we end up with no debuginfo in vmlinux which is a big no-no
    for kernel debugging.
    
    Link: https://lkml.kernel.org/r/20220301202920.18488-1-quic_qiancai@quicinc.com
    Signed-off-by: Qian Cai <quic_qiancai@quicinc.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dd21bfa425c098b95ca86845f8e7d1ec1ddf6e4a
Author: Yun Zhou <yun.zhou@windriver.com>
Date:   Fri Mar 4 20:29:07 2022 -0800

    proc: fix documentation and description of pagemap
    
    Since bit 57 was exported for uffd-wp write-protected (commit
    fb8e37f35a2f: "mm/pagemap: export uffd-wp protection information"),
    fixing it can reduce some unnecessary confusion.
    
    Link: https://lkml.kernel.org/r/20220301044538.3042713-1-yun.zhou@windriver.com
    Fixes: fb8e37f35a2fe1 ("mm/pagemap: export uffd-wp protection information")
    Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
    Reviewed-by: Peter Xu <peterx@redhat.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Tiberiu A Georgescu <tiberiu.georgescu@nutanix.com>
    Cc: Florian Schmidt <florian.schmidt@nutanix.com>
    Cc: Ivan Teterevkov <ivan.teterevkov@nutanix.com>
    Cc: SeongJae Park <sj@kernel.org>
    Cc: Yang Shi <shy828301@gmail.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Axel Rasmussen <axelrasmussen@google.com>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Colin Cross <ccross@google.com>
    Cc: Alistair Popple <apopple@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b773827e361952b3f53ac6fa4c4e39ccd632102e
Author: Chengming Zhou <zhouchengming@bytedance.com>
Date:   Fri Mar 4 20:29:04 2022 -0800

    kselftest/vm: fix tests build with old libc
    
    The error message when I build vm tests on debian10 (GLIBC 2.28):
    
        userfaultfd.c: In function `userfaultfd_pagemap_test':
        userfaultfd.c:1393:37: error: `MADV_PAGEOUT' undeclared (first use
        in this function); did you mean `MADV_RANDOM'?
          if (madvise(area_dst, test_pgsize, MADV_PAGEOUT))
                                             ^~~~~~~~~~~~
                                             MADV_RANDOM
    
    This patch includes these newer definitions from UAPI linux/mman.h, is
    useful to fix tests build on systems without these definitions in glibc
    sys/mman.h.
    
    Link: https://lkml.kernel.org/r/20220227055330.43087-2-zhouchengming@bytedance.com
    Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f2b277c4d1c63a85127e8aa2588e9cc3bd21cb99
Author: Hugh Dickins <hughd@google.com>
Date:   Fri Mar 4 20:29:01 2022 -0800

    memfd: fix F_SEAL_WRITE after shmem huge page allocated
    
    Wangyong reports: after enabling tmpfs filesystem to support transparent
    hugepage with the following command:
    
      echo always > /sys/kernel/mm/transparent_hugepage/shmem_enabled
    
    the docker program tries to add F_SEAL_WRITE through the following
    command, but it fails unexpectedly with errno EBUSY:
    
      fcntl(5, F_ADD_SEALS, F_SEAL_WRITE) = -1.
    
    That is because memfd_tag_pins() and memfd_wait_for_pins() were never
    updated for shmem huge pages: checking page_mapcount() against
    page_count() is hopeless on THP subpages - they need to check
    total_mapcount() against page_count() on THP heads only.
    
    Make memfd_tag_pins() (compared > 1) as strict as memfd_wait_for_pins()
    (compared != 1): either can be justified, but given the non-atomic
    total_mapcount() calculation, it is better now to be strict.  Bear in
    mind that total_mapcount() itself scans all of the THP subpages, when
    choosing to take an XA_CHECK_SCHED latency break.
    
    Also fix the unlikely xa_is_value() case in memfd_wait_for_pins(): if a
    page has been swapped out since memfd_tag_pins(), then its refcount must
    have fallen, and so it can safely be untagged.
    
    Link: https://lkml.kernel.org/r/a4f79248-df75-2c8c-3df-ba3317ccb5da@google.com
    Signed-off-by: Hugh Dickins <hughd@google.com>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Reported-by: wangyong <wang.yong12@zte.com.cn>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: CGEL ZTE <cgel.zte@gmail.com>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Cc: Song Liu <songliubraving@fb.com>
    Cc: Yang Yang <yang.yang29@zte.com.cn>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 942341dcc5748d9c1fc7009a359fc1916bfe0ef0
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Mar 4 20:28:58 2022 -0800

    mm: fix use-after-free when anon vma name is used after vma is freed
    
    When adjacent vmas are being merged it can result in the vma that was
    originally passed to madvise_update_vma being destroyed.  In the current
    implementation, the name parameter passed to madvise_update_vma points
    directly to vma->anon_name and it is used after the call to vma_merge.
    In the cases when vma_merge merges the original vma and destroys it,
    this might result in UAF.  For that the original vma would have to hold
    the anon_vma_name with the last reference.  The following vma would need
    to contain a different anon_vma_name object with the same string.  Such
    scenario is shown below:
    
    madvise_vma_behavior(vma)
      madvise_update_vma(vma, ..., anon_name == vma->anon_name)
        vma_merge(vma)
          __vma_adjust(vma) <-- merges vma with adjacent one
            vm_area_free(vma) <-- frees the original vma
        replace_vma_anon_name(anon_name) <-- UAF of vma->anon_name
    
    Fix this by raising the name refcount and stabilizing it.
    
    Link: https://lkml.kernel.org/r/20220224231834.1481408-3-surenb@google.com
    Link: https://lkml.kernel.org/r/20220223153613.835563-3-surenb@google.com
    Fixes: 9a10064f5625 ("mm: add a field to store names for private anonymous memory")
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reported-by: syzbot+aa7b3d4b35f9dc46a366@syzkaller.appspotmail.com
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Alexey Gladkov <legion@kernel.org>
    Cc: Chris Hyser <chris.hyser@oracle.com>
    Cc: Christian Brauner <brauner@kernel.org>
    Cc: Colin Cross <ccross@google.com>
    Cc: Cyrill Gorcunov <gorcunov@gmail.com>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Peter Collingbourne <pcc@google.com>
    Cc: Sasha Levin <sashal@kernel.org>
    Cc: Sumit Semwal <sumit.semwal@linaro.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Xiaofeng Cao <caoxiaofeng@yulong.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 96403e11283def1d1c465c8279514c9a504d8630
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Mar 4 20:28:55 2022 -0800

    mm: prevent vm_area_struct::anon_name refcount saturation
    
    A deep process chain with many vmas could grow really high.  With
    default sysctl_max_map_count (64k) and default pid_max (32k) the max
    number of vmas in the system is 2147450880 and the refcounter has
    headroom of 1073774592 before it reaches REFCOUNT_SATURATED
    (3221225472).
    
    Therefore it's unlikely that an anonymous name refcounter will overflow
    with these defaults.  Currently the max for pid_max is PID_MAX_LIMIT
    (4194304) and for sysctl_max_map_count it's INT_MAX (2147483647).  In
    this configuration anon_vma_name refcount overflow becomes theoretically
    possible (that still require heavy sharing of that anon_vma_name between
    processes).
    
    kref refcounting interface used in anon_vma_name structure will detect a
    counter overflow when it reaches REFCOUNT_SATURATED value but will only
    generate a warning and freeze the ref counter.  This would lead to the
    refcounted object never being freed.  A determined attacker could leak
    memory like that but it would be rather expensive and inefficient way to
    do so.
    
    To ensure anon_vma_name refcount does not overflow, stop anon_vma_name
    sharing when the refcount reaches REFCOUNT_MAX (2147483647), which still
    leaves INT_MAX/2 (1073741823) values before the counter reaches
    REFCOUNT_SATURATED.  This should provide enough headroom for raising the
    refcounts temporarily.
    
    Link: https://lkml.kernel.org/r/20220223153613.835563-2-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Suggested-by: Michal Hocko <mhocko@suse.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Alexey Gladkov <legion@kernel.org>
    Cc: Chris Hyser <chris.hyser@oracle.com>
    Cc: Christian Brauner <brauner@kernel.org>
    Cc: Colin Cross <ccross@google.com>
    Cc: Cyrill Gorcunov <gorcunov@gmail.com>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Peter Collingbourne <pcc@google.com>
    Cc: Sasha Levin <sashal@kernel.org>
    Cc: Sumit Semwal <sumit.semwal@linaro.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Xiaofeng Cao <caoxiaofeng@yulong.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5c26f6ac9416b63d093e29c30e79b3297e425472
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Mar 4 20:28:51 2022 -0800

    mm: refactor vm_area_struct::anon_vma_name usage code
    
    Avoid mixing strings and their anon_vma_name referenced pointers by
    using struct anon_vma_name whenever possible.  This simplifies the code
    and allows easier sharing of anon_vma_name structures when they
    represent the same name.
    
    [surenb@google.com: fix comment]
    
    Link: https://lkml.kernel.org/r/20220223153613.835563-1-surenb@google.com
    Link: https://lkml.kernel.org/r/20220224231834.1481408-1-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Suggested-by: Matthew Wilcox <willy@infradead.org>
    Suggested-by: Michal Hocko <mhocko@suse.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Colin Cross <ccross@google.com>
    Cc: Sumit Semwal <sumit.semwal@linaro.org>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Christian Brauner <brauner@kernel.org>
    Cc: Alexey Gladkov <legion@kernel.org>
    Cc: Sasha Levin <sashal@kernel.org>
    Cc: Chris Hyser <chris.hyser@oracle.com>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Peter Collingbourne <pcc@google.com>
    Cc: Xiaofeng Cao <caoxiaofeng@yulong.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Cyrill Gorcunov <gorcunov@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ff712a627f7296a42ea5d7356704525e1e909e05
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date:   Fri Mar 4 20:28:48 2022 -0800

    selftests/vm: cleanup hugetlb file after mremap test
    
    The hugepage-mremap test will create a file in a hugetlb filesystem.  In
    a default 'run_vmtests' run, the file will contain all the hugetlb
    pages.  After the test, the file remains and there are no free hugetlb
    pages for subsequent tests.  This causes those hugetlb tests to fail.
    
    Change hugepage-mremap to take the name of the hugetlb file as an
    argument.  Unlink the file within the test, and just to be sure remove
    the file in the run_vmtests script.
    
    Link: https://lkml.kernel.org/r/20220201033459.156944-1-mike.kravetz@oracle.com
    Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Acked-by: Yosry Ahmed <yosryahmed@google.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Reviewed-by: Mina Almasry <almasrymina@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c6a502c2299941c8326d029cfc8a3bc8a4607ad5
Author: Alexey Khoroshilov <khoroshilov@ispras.ru>
Date:   Fri Mar 4 21:25:36 2022 +0300

    mISDN: Fix memory leak in dsp_pipeline_build()
    
    dsp_pipeline_build() allocates dup pointer by kstrdup(cfg),
    but then it updates dup variable by strsep(&dup, "|").
    As a result when it calls kfree(dup), the dup variable contains NULL.
    
    Found by Linux Driver Verification project (linuxtesting.org) with SVACE.
    
    Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
    Fixes: 960366cf8dbb ("Add mISDN DSP")
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b9baf5c8c5c356757f4f9d8180b5e9d234065bc3
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Thu Feb 10 16:05:45 2022 +0000

    ARM: Spectre-BHB workaround
    
    Workaround the Spectre BHB issues for Cortex-A15, Cortex-A57,
    Cortex-A72, Cortex-A73 and Cortex-A75. We also include Brahma B15 as
    well to be safe, which is affected by Spectre V2 in the same ways as
    Cortex-A15.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 8d9d651ff2270a632e9dc497b142db31e8911315
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Fri Feb 11 19:49:50 2022 +0000

    ARM: use LOADADDR() to get load address of sections
    
    Use the linker's LOADADDR() macro to get the load address of the
    sections, and provide a macro to set the start and end symbols.
    
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 04e91b7324760a377a725e218b5ee783826d30f5
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Fri Feb 11 19:46:15 2022 +0000

    ARM: early traps initialisation
    
    Provide a couple of helpers to copy the vectors and stubs, and also
    to flush the copied vectors and stubs.
    
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 9dd78194a3722fa6712192cdd4f7032d45112a9a
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Fri Feb 11 16:45:54 2022 +0000

    ARM: report Spectre v2 status through sysfs
    
    As per other architectures, add support for reporting the Spectre
    vulnerability status via sysfs CPU.
    
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 58dbe9b373df2828d873b1c0e5afc77485b2f376
Author: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
Date:   Tue Mar 1 17:47:43 2022 -0300

    powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set
    
    The following build failure occurs when CONFIG_PPC_64S_HASH_MMU is not
    set:
    
        arch/powerpc/kernel/setup_64.c: In function ‘setup_per_cpu_areas’:
        arch/powerpc/kernel/setup_64.c:811:21: error: ‘mmu_linear_psize’ undeclared (first use in this function); did you mean ‘mmu_virtual_psize’?
          811 |                 if (mmu_linear_psize == MMU_PAGE_4K)
              |                     ^~~~~~~~~~~~~~~~
              |                     mmu_virtual_psize
        arch/powerpc/kernel/setup_64.c:811:21: note: each undeclared identifier is reported only once for each function it appears in
    
    Move the declaration of mmu_linear_psize outside of
    CONFIG_PPC_64S_HASH_MMU ifdef.
    
    After the above is fixed, it fails later with the following error:
    
        ld: arch/powerpc/kexec/file_load_64.o: in function `.arch_kexec_kernel_image_probe':
        file_load_64.c:(.text+0x1c1c): undefined reference to `.add_htab_mem_range'
    
    Fix that, too, by conditioning add_htab_mem_range() symbol to
    CONFIG_PPC_64S_HASH_MMU.
    
    Fixes: 387e220a2e5e ("powerpc/64s: Move hash MMU support code under CONFIG_PPC_64S_HASH_MMU")
    Reported-by: Erhard F. <erhard_f@mailbox.org>
    Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215567
    Link: https://lore.kernel.org/r/20220301204743.45133-1-muriloo@linux.ibm.com

commit 0de05d056afdb00eca8c7bbb0c79a3438daf700c
Author: Josh Poimboeuf <jpoimboe@redhat.com>
Date:   Fri Feb 25 14:32:28 2022 -0800

    x86/speculation: Warn about eIBRS + LFENCE + Unprivileged eBPF + SMT
    
    The commit
    
       44a3918c8245 ("x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation reporting")
    
    added a warning for the "eIBRS + unprivileged eBPF" combination, which
    has been shown to be vulnerable against Spectre v2 BHB-based attacks.
    
    However, there's no warning about the "eIBRS + LFENCE retpoline +
    unprivileged eBPF" combo. The LFENCE adds more protection by shortening
    the speculation window after a mispredicted branch. That makes an attack
    significantly more difficult, even with unprivileged eBPF. So at least
    for now the logic doesn't warn about that combination.
    
    But if you then add SMT into the mix, the SMT attack angle weakens the
    effectiveness of the LFENCE considerably.
    
    So extend the "eIBRS + unprivileged eBPF" warning to also include the
    "eIBRS + LFENCE + unprivileged eBPF + SMT" case.
    
      [ bp: Massage commit message. ]
    
    Suggested-by: Alyssa Milburn <alyssa.milburn@linux.intel.com>
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>

commit eafd987d4a82c7bb5aa12f0e3b4f8f3dea93e678
Author: Josh Poimboeuf <jpoimboe@redhat.com>
Date:   Fri Feb 25 14:31:49 2022 -0800

    x86/speculation: Warn about Spectre v2 LFENCE mitigation
    
    With:
    
      f8a66d608a3e ("x86,bugs: Unconditionally allow spectre_v2=retpoline,amd")
    
    it became possible to enable the LFENCE "retpoline" on Intel. However,
    Intel doesn't recommend it, as it has some weaknesses compared to
    retpoline.
    
    Now AMD doesn't recommend it either.
    
    It can still be left available as a cmdline option. It's faster than
    retpoline but is weaker in certain scenarios -- particularly SMT, but
    even non-SMT may be vulnerable in some cases.
    
    So just unconditionally warn if the user requests it on the cmdline.
    
      [ bp: Massage commit message. ]
    
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>

commit a502a8f04097e038c3daa16c5202a9538116d563
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date:   Thu Mar 3 08:54:15 2022 +0100

    net: phy: meson-gxl: fix interrupt handling in forced mode
    
    This PHY doesn't support a link-up interrupt source. If aneg is enabled
    we use the "aneg complete" interrupt for this purpose, but if aneg is
    disabled link-up isn't signaled currently.
    According to a vendor driver there's an additional "energy detect"
    interrupt source that can be used to signal link-up if aneg is disabled.
    We can safely ignore this interrupt source if aneg is enabled.
    
    This patch was tested on a TX3 Mini TV box with S905W (even though
    boot message says it's a S905D).
    
    This issue has been existing longer, but due to changes in phylib and
    the driver the patch applies only from the commit marked as fixed.
    
    Fixes: 84c8f773d2dc ("net: phy: meson-gxl: remove the use of .ack_callback()")
    Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
    Link: https://lore.kernel.org/r/04cac530-ea1b-850e-6cfa-144a55c4d75d@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ac84e82f78cb55ce8e760e0b5887d56efd78d6bc
Merge: 07ebd38a0da24 30939293262eb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 16:03:46 2022 -0800

    Merge tag 'block-5.17-2022-03-04' of git://git.kernel.dk/linux-block
    
    Pull block fix from Jens Axboe:
     "Just a small UAF fix for blktrace"
    
    * tag 'block-5.17-2022-03-04' of git://git.kernel.dk/linux-block:
      blktrace: fix use after free for struct blk_trace

commit 07ebd38a0da24d2534da57b4841346379db9f354
Merge: 3f509f5971bca 74583f1b92cb3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 11:54:06 2022 -0800

    Merge tag 'riscv-for-linus-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V fixes from Palmer Dabbelt:
    
     - Fixes for a handful of KASAN-related crashes.
    
     - A fix to avoid a crash during boot for SPARSEMEM &&
       !SPARSEMEM_VMEMMAP configurations.
    
     - A fix to stop reporting some incorrect errors under DEBUG_VIRTUAL.
    
     - A fix for the K210's device tree to properly populate the interrupt
       map, so hart1 will get interrupts again.
    
    * tag 'riscv-for-linus-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
      riscv: dts: k210: fix broken IRQs on hart1
      riscv: Fix kasan pud population
      riscv: Move high_memory initialization to setup_bootmem
      riscv: Fix config KASAN && DEBUG_VIRTUAL
      riscv: Fix DEBUG_VIRTUAL false warnings
      riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP
      riscv: Fix is_linear_mapping with recent move of KASAN region

commit 3f509f5971bca38eeb543186131fb1b404262023
Merge: a4ffdb61035da 9826e393e4a8c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 11:30:57 2022 -0800

    Merge tag 'iommu-fixes-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
    
    Pull iommu fixes from Joerg Roedel:
    
     - Fix a double list_add() in Intel VT-d code
    
     - Add missing put_device() in Tegra SMMU driver
    
     - Two AMD IOMMU fixes:
         - Memory leak in IO page-table freeing code
         - Add missing recovery from event-log overflow
    
    * tag 'iommu-fixes-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
      iommu/tegra-smmu: Fix missing put_device() call in tegra_smmu_find
      iommu/vt-d: Fix double list_add when enabling VMD in scalable mode
      iommu/amd: Fix I/O page table memory leak
      iommu/amd: Recover from event log overflow

commit a4ffdb61035da6e1550c3cb141a6b25acd7ae3da
Merge: 8d670948f4d6d 5838a14832d44
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 11:19:14 2022 -0800

    Merge tag 'thermal-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull thermal control fix from Rafael Wysocki:
     "Fix NULL pointer dereference in the thermal netlink interface (Nicolas
      Cavallari)"
    
    * tag 'thermal-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      thermal: core: Fix TZ_GET_TRIP NULL pointer dereference

commit 8d670948f4d6d372935b7dcf9f7db14548859b67
Merge: c4fc118ae26f9 0aa6b294b312d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 11:15:00 2022 -0800

    Merge tag 'sound-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
    
    Pull sound fixes from Takashi Iwai:
     "Hopefully the last PR for 5.17, including just a few small changes:
      an additional fix for ASoC ops boundary check and other minor
      device-specific fixes"
    
    * tag 'sound-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound:
      ALSA: intel_hdmi: Fix reference to PCM buffer address
      ASoC: cs4265: Fix the duplicated control name
      ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min

commit c4fc118ae26f9d4e5885d151f9b0f96467a136da
Merge: 0b7344a658e66 8fdb19679722a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 11:01:22 2022 -0800

    Merge tag 'drm-fixes-2022-03-04' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Things are quieting down as expected, just a small set of fixes, i915,
      exynos, amdgpu, vrr, bridge and hdlcd. Nothing scary at all.
    
      i915:
       - Fix GuC SLPC unset command
       - Fix misidentification of some Apple MacBook Pro laptops as Jasper Lake
    
      amdgpu:
       - Suspend regression fix
    
      exynos:
       - irq handling fixes
       - Fix two regressions to TE-gpio handling
    
      arm/hdlcd:
       - Select DRM_GEM_CMEA_HELPER for HDLCD
    
      bridge:
       - ti-sn65dsi86: Properly undo autosuspend
    
      vrr:
       - Fix potential NULL-pointer deref"
    
    * tag 'drm-fixes-2022-03-04' of git://anongit.freedesktop.org/drm/drm:
      drm/amdgpu: fix suspend/resume hang regression
      drm/vrr: Set VRR capable prop only if it is attached to connector
      drm/arm: arm hdlcd select DRM_GEM_CMA_HELPER
      drm/bridge: ti-sn65dsi86: Properly undo autosuspend
      drm/i915: s/JSP2/ICP2/ PCH
      drm/i915/guc/slpc: Correct the param count for unset param
      drm/exynos: Search for TE-gpio in DSI panel's node
      drm/exynos: Don't fail if no TE-gpio is defined for DSI driver
      drm/exynos: gsc: Use platform_get_irq() to get the interrupt
      drm/exynos/fimc: Use platform_get_irq() to get the interrupt
      drm/exynos/exynos_drm_fimd: Use platform_get_irq_byname() to get the interrupt
      drm/exynos: mixer: Use platform_get_irq() to get the interrupt
      drm/exynos/exynos7_drm_decon: Use platform_get_irq_byname() to get the interrupt

commit 0b7344a658e66a6835ad96dbc5dd35f1e876078a
Merge: 0708a0afe291b bac129dbc6560
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Mar 4 10:56:00 2022 -0800

    Merge tag 'pinctrl-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
    
    Pull pin control fixes from Linus Walleij:
     "These two fixes should fix the issues seen on the OrangePi, first we
      needed the correct offset when calling pinctrl_gpio_direction(), and
      fixing that made a lockdep issue explode in our face. Both now fixed"
    
    * tag 'pinctrl-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
      pinctrl: sunxi: Use unique lockdep classes for IRQs
      pinctrl-sunxi: sunxi_pinctrl_gpio_direction_in/output: use correct offset

commit 1d02b444b8d1345ea4708db3bab4db89a7784b55
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Mar 2 19:17:44 2022 -0800

    tracing: Fix return value of __setup handlers
    
    __setup() handlers should generally return 1 to indicate that the
    boot options have been handled.
    
    Using invalid option values causes the entire kernel boot option
    string to be reported as Unknown and added to init's environment
    strings, polluting it.
    
      Unknown kernel command line parameters "BOOT_IMAGE=/boot/bzImage-517rc6
        kprobe_event=p,syscall_any,$arg1 trace_options=quiet
        trace_clock=jiffies", will be passed to user space.
    
     Run /sbin/init as init process
       with arguments:
         /sbin/init
       with environment:
         HOME=/
         TERM=linux
         BOOT_IMAGE=/boot/bzImage-517rc6
         kprobe_event=p,syscall_any,$arg1
         trace_options=quiet
         trace_clock=jiffies
    
    Return 1 from the __setup() handlers so that init's environment is not
    polluted with kernel boot options.
    
    Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
    Link: https://lkml.kernel.org/r/20220303031744.32356-1-rdunlap@infradead.org
    
    Cc: stable@vger.kernel.org
    Fixes: 7bcfaf54f591 ("tracing: Add trace_options kernel command line parameter")
    Fixes: e1e232ca6b8f ("tracing: Add trace_clock=<clock> kernel parameter")
    Fixes: 970988e19eb0 ("tracing/kprobe: Add kprobe_event= boot parameter")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 0708a0afe291bdfe1386d74d5ec1f0c27e8b9168
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Fri Mar 4 15:26:32 2022 +0100

    mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls
    
    syzkaller was recently triggering an oversized kvmalloc() warning via
    xdp_umem_create().
    
    The triggered warning was added back in 7661809d493b ("mm: don't allow
    oversized kvmalloc() calls"). The rationale for the warning for huge
    kvmalloc sizes was as a reaction to a security bug where the size was
    more than UINT_MAX but not everything was prepared to handle unsigned
    long sizes.
    
    Anyway, the AF_XDP related call trace from this syzkaller report was:
    
      kvmalloc include/linux/mm.h:806 [inline]
      kvmalloc_array include/linux/mm.h:824 [inline]
      kvcalloc include/linux/mm.h:829 [inline]
      xdp_umem_pin_pages net/xdp/xdp_umem.c:102 [inline]
      xdp_umem_reg net/xdp/xdp_umem.c:219 [inline]
      xdp_umem_create+0x6a5/0xf00 net/xdp/xdp_umem.c:252
      xsk_setsockopt+0x604/0x790 net/xdp/xsk.c:1068
      __sys_setsockopt+0x1fd/0x4e0 net/socket.c:2176
      __do_sys_setsockopt net/socket.c:2187 [inline]
      __se_sys_setsockopt net/socket.c:2184 [inline]
      __x64_sys_setsockopt+0xb5/0x150 net/socket.c:2184
      do_syscall_x64 arch/x86/entry/common.c:50 [inline]
      do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
      entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Björn mentioned that requests for >2GB allocation can still be valid:
    
      The structure that is being allocated is the page-pinning accounting.
      AF_XDP has an internal limit of U32_MAX pages, which is *a lot*, but
      still fewer than what memcg allows (PAGE_COUNTER_MAX is a LONG_MAX/
      PAGE_SIZE on 64 bit systems). [...]
    
      I could just change from U32_MAX to INT_MAX, but as I stated earlier
      that has a hacky feeling to it. [...] From my perspective, the code
      isn't broken, with the memcg limits in consideration. [...]
    
    Linus says:
    
      [...] Pretty much every time this has come up, the kernel warning has
      shown that yes, the code was broken and there really wasn't a reason
      for doing allocations that big.
    
      Of course, some people would be perfectly fine with the allocation
      failing, they just don't want the warning. I didn't want __GFP_NOWARN
      to shut it up originally because I wanted people to see all those
      cases, but these days I think we can just say "yeah, people can shut
      it up explicitly by saying 'go ahead and fail this allocation, don't
      warn about it'".
    
      So enough time has passed that by now I'd certainly be ok with [it].
    
    Thus allow call-sites to silence such userspace triggered splats if the
    allocation requests have __GFP_NOWARN. For xdp_umem_pin_pages()'s call
    to kvcalloc() this is already the case, so nothing else needed there.
    
    Fixes: 7661809d493b ("mm: don't allow oversized kvmalloc() calls")
    Reported-by: syzbot+11421fbbff99b989670e@syzkaller.appspotmail.com
    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Tested-by: syzbot+11421fbbff99b989670e@syzkaller.appspotmail.com
    Cc: Björn Töpel <bjorn@kernel.org>
    Cc: Magnus Karlsson <magnus.karlsson@intel.com>
    Cc: Willy Tarreau <w@1wt.eu>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Alexei Starovoitov <ast@kernel.org>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: David S. Miller <davem@davemloft.net>
    Link: https://lore.kernel.org/bpf/CAJ+HfNhyfsT5cS_U9EC213ducHs9k9zNxX9+abqC0kTrPbQ0gg@mail.gmail.com
    Link: https://lore.kernel.org/bpf/20211201202905.b9892171e3f5b9a60f9da251@linux-foundation.org
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Ackd-by: Michal Hocko <mhocko@suse.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b9d102dafec6af1c07b610faf0a6d4e8aee14ae0
Author: Xie Yongji <xieyongji@bytedance.com>
Date:   Fri Jan 21 16:39:39 2022 +0800

    vduse: Fix returning wrong type in vduse_domain_alloc_iova()
    
    This fixes the following smatch warnings:
    
    drivers/vdpa/vdpa_user/iova_domain.c:305 vduse_domain_alloc_iova() warn: should 'iova_pfn << shift' be a 64 bit type?
    
    Fixes: 8c773d53fb7b ("vduse: Implement an MMU-based software IOTLB")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
    Link: https://lore.kernel.org/r/20220121083940.102-1-xieyongji@bytedance.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit ed0f849fc3a63ed2ddf5e72cdb1de3bdbbb0f8eb
Author: Si-Wei Liu <si-wei.liu@oracle.com>
Date:   Fri Jan 14 19:28:01 2022 -0500

    vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command
    
    When control vq receives a VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command
    request from the driver, presently there is no validation against the
    number of queue pairs to configure, or even if multiqueue had been
    negotiated or not is unverified. This may lead to kernel panic due to
    uninitialized resource for the queues were there any bogus request
    sent down by untrusted driver. Tie up the loose ends there.
    
    Fixes: 52893733f2c5 ("vdpa/mlx5: Add multiqueue support")
    Signed-off-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Link: https://lore.kernel.org/r/1642206481-30721-4-git-send-email-si-wei.liu@oracle.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Eli Cohen <elic@nvidia.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 30c22f3816ffef8aa21a000e93c4ee1402a6ea65
Author: Si-Wei Liu <si-wei.liu@oracle.com>
Date:   Fri Jan 14 19:28:00 2022 -0500

    vdpa/mlx5: should verify CTRL_VQ feature exists for MQ
    
    Per VIRTIO v1.1 specification, section 5.1.3.1 Feature bit requirements:
    "VIRTIO_NET_F_MQ Requires VIRTIO_NET_F_CTRL_VQ".
    
    There's assumption in the mlx5_vdpa multiqueue code that MQ must come
    together with CTRL_VQ. However, there's nowhere in the upper layer to
    guarantee this assumption would hold. Were there an untrusted driver
    sending down MQ without CTRL_VQ, it would compromise various spots for
    e.g. is_index_valid() and is_ctrl_vq_idx(). Although this doesn't end
    up with immediate panic or security loophole as of today's code, the
    chance for this to be taken advantage of due to future code change is
    not zero.
    
    Harden the crispy assumption by failing the set_driver_features() call
    when seeing (MQ && !CTRL_VQ). For that end, verify_min_features() is
    renamed to verify_driver_features() to reflect the fact that it now does
    more than just validate the minimum features. verify_driver_features()
    is now used to accommodate various checks against the driver features
    for set_driver_features().
    
    Signed-off-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Link: https://lore.kernel.org/r/1642206481-30721-3-git-send-email-si-wei.liu@oracle.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Eli Cohen <elic@nvidia.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit e0077cc13b831f8fad5557442f73bf7728683713
Author: Si-Wei Liu <si-wei.liu@oracle.com>
Date:   Fri Jan 14 19:27:59 2022 -0500

    vdpa: factor out vdpa_set_features_unlocked for vdpa internal use
    
    No functional change introduced. vdpa bus driver such as virtio_vdpa
    or vhost_vdpa is not supposed to take care of the locking for core
    by its own. The locked API vdpa_set_features should suffice the
    bus driver's need.
    
    Signed-off-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Reviewed-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/1642206481-30721-2-git-send-email-si-wei.liu@oracle.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit ca93e44bfb5fd7996b76f0f544999171f647f93b
Author: Filipe Manana <fdmanana@suse.com>
Date:   Wed Mar 2 11:48:39 2022 +0000

    btrfs: fallback to blocking mode when doing async dio over multiple extents
    
    Some users recently reported that MariaDB was getting a read corruption
    when using io_uring on top of btrfs. This started to happen in 5.16,
    after commit 51bd9563b6783d ("btrfs: fix deadlock due to page faults
    during direct IO reads and writes"). That changed btrfs to use the new
    iomap flag IOMAP_DIO_PARTIAL and to disable page faults before calling
    iomap_dio_rw(). This was necessary to fix deadlocks when the iovector
    corresponds to a memory mapped file region. That type of scenario is
    exercised by test case generic/647 from fstests.
    
    For this MariaDB scenario, we attempt to read 16K from file offset X
    using IOCB_NOWAIT and io_uring. In that range we have 4 extents, each
    with a size of 4K, and what happens is the following:
    
    1) btrfs_direct_read() disables page faults and calls iomap_dio_rw();
    
    2) iomap creates a struct iomap_dio object, its reference count is
       initialized to 1 and its ->size field is initialized to 0;
    
    3) iomap calls btrfs_dio_iomap_begin() with file offset X, which finds
       the first 4K extent, and setups an iomap for this extent consisting
       of a single page;
    
    4) At iomap_dio_bio_iter(), we are able to access the first page of the
       buffer (struct iov_iter) with bio_iov_iter_get_pages() without
       triggering a page fault;
    
    5) iomap submits a bio for this 4K extent
       (iomap_dio_submit_bio() -> btrfs_submit_direct()) and increments
       the refcount on the struct iomap_dio object to 2; The ->size field
       of the struct iomap_dio object is incremented to 4K;
    
    6) iomap calls btrfs_iomap_begin() again, this time with a file
       offset of X + 4K. There we setup an iomap for the next extent
       that also has a size of 4K;
    
    7) Then at iomap_dio_bio_iter() we call bio_iov_iter_get_pages(),
       which tries to access the next page (2nd page) of the buffer.
       This triggers a page fault and returns -EFAULT;
    
    8) At __iomap_dio_rw() we see the -EFAULT, but we reset the error
       to 0 because we passed the flag IOMAP_DIO_PARTIAL to iomap and
       the struct iomap_dio object has a ->size value of 4K (we submitted
       a bio for an extent already). The 'wait_for_completion' variable
       is not set to true, because our iocb has IOCB_NOWAIT set;
    
    9) At the bottom of __iomap_dio_rw(), we decrement the reference count
       of the struct iomap_dio object from 2 to 1. Because we were not
       the only ones holding a reference on it and 'wait_for_completion' is
       set to false, -EIOCBQUEUED is returned to btrfs_direct_read(), which
       just returns it up the callchain, up to io_uring;
    
    10) The bio submitted for the first extent (step 5) completes and its
        bio endio function, iomap_dio_bio_end_io(), decrements the last
        reference on the struct iomap_dio object, resulting in calling
        iomap_dio_complete_work() -> iomap_dio_complete().
    
    11) At iomap_dio_complete() we adjust the iocb->ki_pos from X to X + 4K
        and return 4K (the amount of io done) to iomap_dio_complete_work();
    
    12) iomap_dio_complete_work() calls the iocb completion callback,
        iocb->ki_complete() with a second argument value of 4K (total io
        done) and the iocb with the adjust ki_pos of X + 4K. This results
        in completing the read request for io_uring, leaving it with a
        result of 4K bytes read, and only the first page of the buffer
        filled in, while the remaining 3 pages, corresponding to the other
        3 extents, were not filled;
    
    13) For the application, the result is unexpected because if we ask
        to read N bytes, it expects to get N bytes read as long as those
        N bytes don't cross the EOF (i_size).
    
    MariaDB reports this as an error, as it's not expecting a short read,
    since it knows it's asking for read operations fully within the i_size
    boundary. This is typical in many applications, but it may also be
    questionable if they should react to such short reads by issuing more
    read calls to get the remaining data. Nevertheless, the short read
    happened due to a change in btrfs regarding how it deals with page
    faults while in the middle of a read operation, and there's no reason
    why btrfs can't have the previous behaviour of returning the whole data
    that was requested by the application.
    
    The problem can also be triggered with the following simple program:
    
      /* Get O_DIRECT */
      #ifndef _GNU_SOURCE
      #define _GNU_SOURCE
      #endif
    
      #include <stdio.h>
      #include <stdlib.h>
      #include <unistd.h>
      #include <fcntl.h>
      #include <errno.h>
      #include <string.h>
      #include <liburing.h>
    
      int main(int argc, char *argv[])
      {
          char *foo_path;
          struct io_uring ring;
          struct io_uring_sqe *sqe;
          struct io_uring_cqe *cqe;
          struct iovec iovec;
          int fd;
          long pagesize;
          void *write_buf;
          void *read_buf;
          ssize_t ret;
          int i;
    
          if (argc != 2) {
              fprintf(stderr, "Use: %s <directory>\n", argv[0]);
              return 1;
          }
    
          foo_path = malloc(strlen(argv[1]) + 5);
          if (!foo_path) {
              fprintf(stderr, "Failed to allocate memory for file path\n");
              return 1;
          }
          strcpy(foo_path, argv[1]);
          strcat(foo_path, "/foo");
    
          /*
           * Create file foo with 2 extents, each with a size matching
           * the page size. Then allocate a buffer to read both extents
           * with io_uring, using O_DIRECT and IOCB_NOWAIT. Before doing
           * the read with io_uring, access the first page of the buffer
           * to fault it in, so that during the read we only trigger a
           * page fault when accessing the second page of the buffer.
           */
           fd = open(foo_path, O_CREAT | O_TRUNC | O_WRONLY |
                    O_DIRECT, 0666);
           if (fd == -1) {
               fprintf(stderr,
                       "Failed to create file 'foo': %s (errno %d)",
                       strerror(errno), errno);
               return 1;
           }
    
           pagesize = sysconf(_SC_PAGE_SIZE);
           ret = posix_memalign(&write_buf, pagesize, 2 * pagesize);
           if (ret) {
               fprintf(stderr, "Failed to allocate write buffer\n");
               return 1;
           }
    
           memset(write_buf, 0xab, pagesize);
           memset(write_buf + pagesize, 0xcd, pagesize);
    
           /* Create 2 extents, each with a size matching page size. */
           for (i = 0; i < 2; i++) {
               ret = pwrite(fd, write_buf + i * pagesize, pagesize,
                            i * pagesize);
               if (ret != pagesize) {
                   fprintf(stderr,
                         "Failed to write to file, ret = %ld errno %d (%s)\n",
                          ret, errno, strerror(errno));
                   return 1;
               }
               ret = fsync(fd);
               if (ret != 0) {
                   fprintf(stderr, "Failed to fsync file\n");
                   return 1;
               }
           }
    
           close(fd);
           fd = open(foo_path, O_RDONLY | O_DIRECT);
           if (fd == -1) {
               fprintf(stderr,
                       "Failed to open file 'foo': %s (errno %d)",
                       strerror(errno), errno);
               return 1;
           }
    
           ret = posix_memalign(&read_buf, pagesize, 2 * pagesize);
           if (ret) {
               fprintf(stderr, "Failed to allocate read buffer\n");
               return 1;
           }
    
           /*
            * Fault in only the first page of the read buffer.
            * We want to trigger a page fault for the 2nd page of the
            * read buffer during the read operation with io_uring
            * (O_DIRECT and IOCB_NOWAIT).
            */
           memset(read_buf, 0, 1);
    
           ret = io_uring_queue_init(1, &ring, 0);
           if (ret != 0) {
               fprintf(stderr, "Failed to create io_uring queue\n");
               return 1;
           }
    
           sqe = io_uring_get_sqe(&ring);
           if (!sqe) {
               fprintf(stderr, "Failed to get io_uring sqe\n");
               return 1;
           }
    
           iovec.iov_base = read_buf;
           iovec.iov_len = 2 * pagesize;
           io_uring_prep_readv(sqe, fd, &iovec, 1, 0);
    
           ret = io_uring_submit_and_wait(&ring, 1);
           if (ret != 1) {
               fprintf(stderr,
                       "Failed at io_uring_submit_and_wait()\n");
               return 1;
           }
    
           ret = io_uring_wait_cqe(&ring, &cqe);
           if (ret < 0) {
               fprintf(stderr, "Failed at io_uring_wait_cqe()\n");
               return 1;
           }
    
           printf("io_uring read result for file foo:\n\n");
           printf("  cqe->res == %d (expected %d)\n", cqe->res, 2 * pagesize);
           printf("  memcmp(read_buf, write_buf) == %d (expected 0)\n",
                  memcmp(read_buf, write_buf, 2 * pagesize));
    
           io_uring_cqe_seen(&ring, cqe);
           io_uring_queue_exit(&ring);
    
           return 0;
      }
    
    When running it on an unpatched kernel:
    
      $ gcc io_uring_test.c -luring
      $ mkfs.btrfs -f /dev/sda
      $ mount /dev/sda /mnt/sda
      $ ./a.out /mnt/sda
      io_uring read result for file foo:
    
        cqe->res == 4096 (expected 8192)
        memcmp(read_buf, write_buf) == -205 (expected 0)
    
    After this patch, the read always returns 8192 bytes, with the buffer
    filled with the correct data. Although that reproducer always triggers
    the bug in my test vms, it's possible that it will not be so reliable
    on other environments, as that can happen if the bio for the first
    extent completes and decrements the reference on the struct iomap_dio
    object before we do the atomic_dec_and_test() on the reference at
    __iomap_dio_rw().
    
    Fix this in btrfs by having btrfs_dio_iomap_begin() return -EAGAIN
    whenever we try to satisfy a non blocking IO request (IOMAP_NOWAIT flag
    set) over a range that spans multiple extents (or a mix of extents and
    holes). This avoids returning success to the caller when we only did
    partial IO, which is not optimal for writes and for reads it's actually
    incorrect, as the caller doesn't expect to get less bytes read than it has
    requested (unless EOF is crossed), as previously mentioned. This is also
    the type of behaviour that xfs follows (xfs_direct_write_iomap_begin()),
    even though it doesn't use IOMAP_DIO_PARTIAL.
    
    A test case for fstests will follow soon.
    
    Link: https://lore.kernel.org/linux-btrfs/CABVffEM0eEWho+206m470rtM0d9J8ue85TtR-A_oVTuGLWFicA@mail.gmail.com/
    Link: https://lore.kernel.org/linux-btrfs/CAHF2GV6U32gmqSjLe=XKgfcZAmLCiH26cJ2OnHGp5x=VAH4OHQ@mail.gmail.com/
    CC: stable@vger.kernel.org # 5.16+
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0e7174b9d5877130fec41fb4a16e0c2ee4958d44
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Tue Oct 5 03:04:10 2021 -0400

    virtio_console: break out of buf poll on remove
    
    A common pattern for device reset is currently:
    vdev->config->reset(vdev);
    .. cleanup ..
    
    reset prevents new interrupts from arriving and waits for interrupt
    handlers to finish.
    
    However if - as is common - the handler queues a work request which is
    flushed during the cleanup stage, we have code adding buffers / trying
    to get buffers while device is reset. Not good.
    
    This was reproduced by running
            modprobe virtio_console
            modprobe -r virtio_console
    in a loop.
    
    Fix this up by calling virtio_break_device + flush before reset.
    
    Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1786239
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit c46eccdaadabb7822080a04e633f81b2ad37f358
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Fri Jan 14 15:54:01 2022 -0500

    virtio: document virtio_reset_device
    
    Looks like most callers get driver/device removal wrong.
    Document what's expected of callers.
    
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 4fa59ede95195f267101a1b8916992cf3f245cdb
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Fri Jan 14 14:58:41 2022 -0500

    virtio: acknowledge all features before access
    
    The feature negotiation was designed in a way that
    makes it possible for devices to know which config
    fields will be accessed by drivers.
    
    This is broken since commit 404123c2db79 ("virtio: allow drivers to
    validate features") with fallout in at least block and net.  We have a
    partial work-around in commit 2f9a174f918e ("virtio: write back
    F_VERSION_1 before validate") which at least lets devices find out which
    format should config space have, but this is a partial fix: guests
    should not access config space without acknowledging features since
    otherwise we'll never be able to change the config space format.
    
    To fix, split finalize_features from virtio_finalize_features and
    call finalize_features with all feature bits before validation,
    and then - if validation changed any bits - once again after.
    
    Since virtio_finalize_features no longer writes out features
    rename it to virtio_features_ok - since that is what it does:
    checks that features are ok with the device.
    
    As a side effect, this also reduces the amount of hypervisor accesses -
    we now only acknowledge features once unless we are clearing any
    features when validating (which is uncommon).
    
    IRC I think that this was more or less always the intent in the spec but
    unfortunately the way the spec is worded does not say this explicitly, I
    plan to address this at the spec level, too.
    
    Acked-by: Jason Wang <jasowang@redhat.com>
    Cc: stable@vger.kernel.org
    Fixes: 404123c2db79 ("virtio: allow drivers to validate features")
    Fixes: 2f9a174f918e ("virtio: write back F_VERSION_1 before validate")
    Cc: "Halil Pasic" <pasic@linux.ibm.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 838d6d3461db0fdbf33fc5f8a69c27b50b4a46da
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Fri Jan 14 14:56:15 2022 -0500

    virtio: unexport virtio_finalize_features
    
    virtio_finalize_features is only used internally within virtio.
    No reason to export it.
    
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Cornelia Huck <cohuck@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit be4977b847f5d5cedb64d50eaaf2218c3a55a3a3
Author: Tung Nguyen <tung.q.nguyen@dektech.com.au>
Date:   Fri Mar 4 03:25:18 2022 +0000

    tipc: fix kernel panic when enabling bearer
    
    When enabling a bearer on a node, a kernel panic is observed:
    
    [    4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
    ...
    [    4.520030] Call Trace:
    [    4.520689]  <IRQ>
    [    4.521236]  tipc_link_build_proto_msg+0x375/0x750 [tipc]
    [    4.522654]  tipc_link_build_state_msg+0x48/0xc0 [tipc]
    [    4.524034]  __tipc_node_link_up+0xd7/0x290 [tipc]
    [    4.525292]  tipc_rcv+0x5da/0x730 [tipc]
    [    4.526346]  ? __netif_receive_skb_core+0xb7/0xfc0
    [    4.527601]  tipc_l2_rcv_msg+0x5e/0x90 [tipc]
    [    4.528737]  __netif_receive_skb_list_core+0x20b/0x260
    [    4.530068]  netif_receive_skb_list_internal+0x1bf/0x2e0
    [    4.531450]  ? dev_gro_receive+0x4c2/0x680
    [    4.532512]  napi_complete_done+0x6f/0x180
    [    4.533570]  virtnet_poll+0x29c/0x42e [virtio_net]
    ...
    
    The node in question is receiving activate messages in another
    thread after changing bearer status to allow message sending/
    receiving in current thread:
    
             thread 1           |              thread 2
             --------           |              --------
                                |
    tipc_enable_bearer()        |
      test_and_set_bit_lock()   |
        tipc_bearer_xmit_skb()  |
                                | tipc_l2_rcv_msg()
                                |   tipc_rcv()
                                |     __tipc_node_link_up()
                                |       tipc_link_build_state_msg()
                                |         tipc_link_build_proto_msg()
                                |           tipc_mon_prep()
                                |           {
                                |             ...
                                |             // null-pointer dereference
                                |             u16 gen = mon->dom_gen;
                                |             ...
                                |           }
      // Not being executed yet |
      tipc_mon_create()         |
      {                         |
        ...                     |
        // allocate             |
        mon = kzalloc();        |
        ...                     |
      }                         |
    
    Monitoring pointer in thread 2 is dereferenced before monitoring data
    is allocated in thread 1. This causes kernel panic.
    
    This commit fixes it by allocating the monitoring data before enabling
    the bearer to receive messages.
    
    Fixes: 35c55c9877f8 ("tipc: add neighbor monitoring framework")
    Reported-by: Shuang Li <shuali@redhat.com>
    Acked-by: Jon Maloy <jmaloy@redhat.com>
    Signed-off-by: Tung Nguyen <tung.q.nguyen@dektech.com.au>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0bf476fc3624e3a72af4ba7340d430a91c18cd67
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Thu Mar 3 12:10:27 2022 -0600

    net: macb: Fix lost RX packet wakeup race in NAPI receive
    
    There is an oddity in the way the RSR register flags propagate to the
    ISR register (and the actual interrupt output) on this hardware: it
    appears that RSR register bits only result in ISR being asserted if the
    interrupt was actually enabled at the time, so enabling interrupts with
    RSR bits already set doesn't trigger an interrupt to be raised. There
    was already a partial fix for this race in the macb_poll function where
    it checked for RSR bits being set and re-triggered NAPI receive.
    However, there was a still a race window between checking RSR and
    actually enabling interrupts, where a lost wakeup could happen. It's
    necessary to check again after enabling interrupts to see if RSR was set
    just prior to the interrupt being enabled, and re-trigger receive in that
    case.
    
    This issue was noticed in a point-to-point UDP request-response protocol
    which periodically saw timeouts or abnormally high response times due to
    received packets not being processed in a timely fashion. In many
    applications, more packets arriving, including TCP retransmissions, would
    cause the original packet to be processed, thus masking the issue.
    
    Fixes: 02f7a34f34e3 ("net: macb: Re-enable RX interrupt only when RX is done")
    Cc: stable@vger.kernel.org
    Co-developed-by: Scott McNutt <scott.mcnutt@siriusxm.com>
    Signed-off-by: Scott McNutt <scott.mcnutt@siriusxm.com>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Tested-by: Claudiu Beznea <claudiu.beznea@microchip.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9f3956d6595abcd1295f13d96132ff7f28e8ed64
Merge: b949c21fc23ec 008ee9eb8a11b
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Mar 3 20:31:02 2022 -0800

    Merge tag 'for-net-2022-03-03' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth
    
    Luiz Augusto von Dentz says:
    
    ====================
    bluetooth pull request for net:
    
     - Fix regression with processing of MGMT commands
     - Fix unbalanced unlock in Set Device Flags
    
    * tag 'for-net-2022-03-03' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth:
      Bluetooth: hci_sync: Fix not processing all entries on cmd_sync_work
      Bluetooth: hci_core: Fix unbalanced unlock in set_device_flags()
    ====================
    
    Link: https://lore.kernel.org/r/20220303210743.314679-1-luiz.dentz@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 74583f1b92cb3bbba1a3741cea237545c56f506c
Author: Niklas Cassel <niklas.cassel@wdc.com>
Date:   Tue Mar 1 00:44:18 2022 +0000

    riscv: dts: k210: fix broken IRQs on hart1
    
    Commit 67d96729a9e7 ("riscv: Update Canaan Kendryte K210 device tree")
    incorrectly removed two entries from the PLIC interrupt-controller node's
    interrupts-extended property.
    
    The PLIC driver cannot know the mapping between hart contexts and hart ids,
    so this information has to be provided by device tree, as specified by the
    PLIC device tree binding.
    
    The PLIC driver uses the interrupts-extended property, and initializes the
    hart context registers in the exact same order as provided by the
    interrupts-extended property.
    
    In other words, if we don't specify the S-mode interrupts, the PLIC driver
    will simply initialize the hart0 S-mode hart context with the hart1 M-mode
    configuration. It is therefore essential to specify the S-mode IRQs even
    though the system itself will only ever be running in M-mode.
    
    Re-add the S-mode interrupts, so that we get working IRQs on hart1 again.
    
    Cc: <stable@vger.kernel.org>
    Fixes: 67d96729a9e7 ("riscv: Update Canaan Kendryte K210 device tree")
    Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 8fdb19679722a02fe21642d39710c701d2ed567a
Merge: c9585249c245e 62929726ef0ec
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 4 13:04:06 2022 +1000

    Merge tag 'drm-misc-fixes-2022-03-03' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/arm: Select DRM_GEM_CMEA_HELPER for HDLCD
     * drm/bridge: ti-sn65dsi86: Properly undo autosuspend
     * drm/vrr: Fix potential NULL-pointer deref
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YiCTGZ8IVCw0ilKK@linux-uq9g

commit c9585249c245e23580a2c3edbc8f14d9d7173f12
Merge: 0d9f0ee17b3f5 f1ef17011c765
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 4 13:02:13 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-03-02' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-03-02:
    
    amdgpu:
    - Suspend regression fix
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220303045035.5650-1-alexander.deucher@amd.com

commit 0d9f0ee17b3f57012e6b8530d6b9e80f138a8e28
Merge: e7c470a4b5433 08783aa7693f5
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Mar 4 12:55:48 2022 +1000

    Merge tag 'drm-intel-fixes-2022-03-03' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    - Fix GuC SLPC unset command. (Vinay Belgaumkar)
    - Fix misidentification of some Apple MacBook Pro laptops as Jasper Lake. (Ville Syrjälä)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/YiCXHiTyCE7TbopG@tursulin-mobl2

commit 327b89f0acc4c20a06ed59e4d9af7f6d804dc2e2
Author: William Mahon <wmahon@chromium.org>
Date:   Thu Mar 3 18:26:22 2022 -0800

    HID: add mapping for KEY_ALL_APPLICATIONS
    
    This patch adds a new key definition for KEY_ALL_APPLICATIONS
    and aliases KEY_DASHBOARD to it.
    
    It also maps the 0x0c/0x2a2 usage code to KEY_ALL_APPLICATIONS.
    
    Signed-off-by: William Mahon <wmahon@chromium.org>
    Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
    Link: https://lore.kernel.org/r/20220303035618.1.I3a7746ad05d270161a18334ae06e3b6db1a1d339@changeid
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit bfa26ba343c727e055223be04e08f2ebdd43c293
Author: William Mahon <wmahon@chromium.org>
Date:   Thu Mar 3 18:23:42 2022 -0800

    HID: add mapping for KEY_DICTATE
    
    Numerous keyboards are adding dictate keys which allows for text
    messages to be dictated by a microphone.
    
    This patch adds a new key definition KEY_DICTATE and maps 0x0c/0x0d8
    usage code to this new keycode. Additionally hid-debug is adjusted to
    recognize this new usage code as well.
    
    Signed-off-by: William Mahon <wmahon@chromium.org>
    Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
    Link: https://lore.kernel.org/r/20220303021501.1.I5dbf50eb1a7a6734ee727bda4a8573358c6d3ec0@changeid
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit e4fcfe6eca6f32357f1b4408ff15b10527518eee
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:53 2022 +0100

    riscv: Fix kasan pud population
    
    In sv48, the kasan inner regions are not aligned on PGDIR_SIZE and then
    when we populate the kasan linear mapping region, we clear the kasan
    vmalloc region which is in the same PGD.
    
    Fix this by copying the content of the kasan early pud after allocating a
    new PGD for the first time.
    
    Fixes: e8a62cc26ddf ("riscv: Implement sv48 support")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 625e24a550e6a600e639b43cf7c15879b2a70840
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:52 2022 +0100

    riscv: Move high_memory initialization to setup_bootmem
    
    high_memory used to be initialized in mem_init, way after setup_bootmem.
    But a call to dma_contiguous_reserve in this function gives rise to the
    below warning because high_memory is equal to 0 and is used at the very
    beginning at cma_declare_contiguous_nid.
    
    It went unnoticed since the move of the kasan region redefined
    KERN_VIRT_SIZE so that it does not encompass -1 anymore.
    
    Fix this by initializing high_memory in setup_bootmem.
    
    ------------[ cut here ]------------
    virt_to_phys used for non-linear address: ffffffffffffffff (0xffffffffffffffff)
    WARNING: CPU: 0 PID: 0 at arch/riscv/mm/physaddr.c:14 __virt_to_phys+0xac/0x1b8
    Modules linked in:
    CPU: 0 PID: 0 Comm: swapper Not tainted 5.17.0-rc1-00007-ga68b89289e26 #27
    Hardware name: riscv-virtio,qemu (DT)
    epc : __virt_to_phys+0xac/0x1b8
     ra : __virt_to_phys+0xac/0x1b8
    epc : ffffffff80014922 ra : ffffffff80014922 sp : ffffffff84a03c30
     gp : ffffffff85866c80 tp : ffffffff84a3f180 t0 : ffffffff86bce657
     t1 : fffffffef09406e8 t2 : 0000000000000000 s0 : ffffffff84a03c70
     s1 : ffffffffffffffff a0 : 000000000000004f a1 : 00000000000f0000
     a2 : 0000000000000002 a3 : ffffffff8011f408 a4 : 0000000000000000
     a5 : 0000000000000000 a6 : 0000000000f00000 a7 : ffffffff84a03747
     s2 : ffffffd800000000 s3 : ffffffff86ef4000 s4 : ffffffff8467f828
     s5 : fffffff800000000 s6 : 8000000000006800 s7 : 0000000000000000
     s8 : 0000000480000000 s9 : 0000000080038ea0 s10: 0000000000000000
     s11: ffffffffffffffff t3 : ffffffff84a035c0 t4 : fffffffef09406e8
     t5 : fffffffef09406e9 t6 : ffffffff84a03758
    status: 0000000000000100 badaddr: 0000000000000000 cause: 0000000000000003
    [<ffffffff8322ef4c>] cma_declare_contiguous_nid+0xf2/0x64a
    [<ffffffff83212a58>] dma_contiguous_reserve_area+0x46/0xb4
    [<ffffffff83212c3a>] dma_contiguous_reserve+0x174/0x18e
    [<ffffffff83208fc2>] paging_init+0x12c/0x35e
    [<ffffffff83206bd2>] setup_arch+0x120/0x74e
    [<ffffffff83201416>] start_kernel+0xce/0x68c
    irq event stamp: 0
    hardirqs last  enabled at (0): [<0000000000000000>] 0x0
    hardirqs last disabled at (0): [<0000000000000000>] 0x0
    softirqs last  enabled at (0): [<0000000000000000>] 0x0
    softirqs last disabled at (0): [<0000000000000000>] 0x0
    ---[ end trace 0000000000000000 ]---
    
    Fixes: f7ae02333d13 ("riscv: Move KASAN mapping next to the kernel mapping")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit c648c4bb7d02ceb53ee40172fdc4433b37cee9c6
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:51 2022 +0100

    riscv: Fix config KASAN && DEBUG_VIRTUAL
    
    __virt_to_phys function is called very early in the boot process (ie
    kasan_early_init) so it should not be instrumented by KASAN otherwise it
    bugs.
    
    Fix this by declaring phys_addr.c as non-kasan instrumentable.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Fixes: 8ad8b72721d0 (riscv: Add KASAN support)
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 5f763b3b59602735993149330ffa7e348bc85bc0
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:50 2022 +0100

    riscv: Fix DEBUG_VIRTUAL false warnings
    
    KERN_VIRT_SIZE used to encompass the kernel mapping before it was
    redefined when moving the kasan mapping next to the kernel mapping to only
    match the maximum amount of physical memory.
    
    Then, kernel mapping addresses that go through __virt_to_phys are now
    declared as wrong which is not true, one can use __virt_to_phys on such
    addresses.
    
    Fix this by redefining the condition that matches wrong addresses.
    
    Fixes: f7ae02333d13 ("riscv: Move KASAN mapping next to the kernel mapping")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit a3d328037846d013bb4c7f3777241e190e4c75e1
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:49 2022 +0100

    riscv: Fix config KASAN && SPARSEMEM && !SPARSE_VMEMMAP
    
    In order to get the pfn of a struct page* when sparsemem is enabled
    without vmemmap, the mem_section structures need to be initialized which
    happens in sparse_init.
    
    But kasan_early_init calls pfn_to_page way before sparse_init is called,
    which then tries to dereference a null mem_section pointer.
    
    Fix this by removing the usage of this function in kasan_early_init.
    
    Fixes: 8ad8b72721d0 ("riscv: Add KASAN support")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 8b274f2238950c55570ff14fcc278a7fcbecc663
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Feb 25 13:39:48 2022 +0100

    riscv: Fix is_linear_mapping with recent move of KASAN region
    
    The KASAN region was recently moved between the linear mapping and the
    kernel mapping, is_linear_mapping used to check the validity of an
    address by using the start of the kernel mapping, which is now wrong.
    
    Fix this by using the maximum size of the physical memory.
    
    Fixes: f7ae02333d13 ("riscv: Move KASAN mapping next to the kernel mapping")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 38f80f42147ff658aff218edb0a88c37e58bf44f
Author: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Date:   Sat Feb 26 14:40:56 2022 +0700

    MAINTAINERS: Remove dead patchwork link
    
    The patchwork link is dead. It says:
    
      404: File not found
      The page URL requested (/project/LKML/list/) does not exist.
    
    Remove it.
    
    Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b08968f196d498b19e9d0841d76a03862258f2d8
Author: David Howells <dhowells@redhat.com>
Date:   Thu Mar 3 13:05:18 2022 +0000

    cachefiles: Fix incorrect length to fallocate()
    
    When cachefiles_shorten_object() calls fallocate() to shape the cache
    file to match the DIO size, it passes the total file size it wants to
    achieve, not the amount of zeros that should be inserted.  Since this is
    meant to preallocate that amount of storage for the file, it can cause
    the cache to fill up the disk and hit ENOSPC.
    
    Fix this by passing the length actually required to go from the current
    EOF to the desired EOF.
    
    Fixes: 7623ed6772de ("cachefiles: Implement cookie resize for truncate")
    Reported-by: Jeffle Xu <jefflexu@linux.alibaba.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164630854858.3665356.17419701804248490708.stgit@warthog.procyon.org.uk # v1
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b949c21fc23ecaccef89582f251e6281cad1f81e
Merge: e58bd49da6eb4 2d3916f318917
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 3 11:10:56 2022 -0800

    Merge tag 'net-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from can, xfrm, wifi, bluetooth, and netfilter.
    
      Lots of various size fixes, the length of the tag speaks for itself.
      Most of the 5.17-relevant stuff comes from xfrm, wifi and bt trees
      which had been lagging as you pointed out previously. But there's also
      a larger than we'd like portion of fixes for bugs from previous
      releases.
    
      Three more fixes still under discussion, including and xfrm revert for
      uAPI error.
    
      Current release - regressions:
    
       - iwlwifi: don't advertise TWT support, prevent FW crash
    
       - xfrm: fix the if_id check in changelink
    
       - xen/netfront: destroy queues before real_num_tx_queues is zeroed
    
       - bluetooth: fix not checking MGMT cmd pending queue, make scanning
         work again
    
      Current release - new code bugs:
    
       - mptcp: make SIOCOUTQ accurate for fallback socket
    
       - bluetooth: access skb->len after null check
    
       - bluetooth: hci_sync: fix not using conn_timeout
    
       - smc: fix cleanup when register ULP fails
    
       - dsa: restore error path of dsa_tree_change_tag_proto
    
       - iwlwifi: fix build error for IWLMEI
    
       - iwlwifi: mvm: propagate error from request_ownership to the user
    
      Previous releases - regressions:
    
       - xfrm: fix pMTU regression when reported pMTU is too small
    
       - xfrm: fix TCP MSS calculation when pMTU is close to 1280
    
       - bluetooth: fix bt_skb_sendmmsg not allocating partial chunks
    
       - ipv6: ensure we call ipv6_mc_down() at most once, prevent leaks
    
       - ipv6: prevent leaks in igmp6 when input queues get full
    
       - fix up skbs delta_truesize in UDP GRO frag_list
    
       - eth: e1000e: fix possible HW unit hang after an s0ix exit
    
       - eth: e1000e: correct NVM checksum verification flow
    
       - ptp: ocp: fix large time adjustments
    
      Previous releases - always broken:
    
       - tcp: make tcp_read_sock() more robust in presence of urgent data
    
       - xfrm: distinguishing SAs and SPs by if_id in xfrm_migrate
    
       - xfrm: fix xfrm_migrate issues when address family changes
    
       - dcb: flush lingering app table entries for unregistered devices
    
       - smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error
    
       - mac80211: fix EAPoL rekey fail in 802.3 rx path
    
       - mac80211: fix forwarded mesh frames AC & queue selection
    
       - netfilter: nf_queue: fix socket access races and bugs
    
       - batman-adv: fix ToCToU iflink problems and check the result belongs
         to the expected net namespace
    
       - can: gs_usb, etas_es58x: fix opened_channel_cnt's accounting
    
       - can: rcar_canfd: register the CAN device when fully ready
    
       - eth: igb, igc: phy: drop premature return leaking HW semaphore
    
       - eth: ixgbe: xsk: change !netif_carrier_ok() handling in
         ixgbe_xmit_zc(), prevent live lock when link goes down
    
       - eth: stmmac: only enable DMA interrupts when ready
    
       - eth: sparx5: move vlan checks before any changes are made
    
       - eth: iavf: fix races around init, removal, resets and vlan ops
    
       - ibmvnic: more reset flow fixes
    
      Misc:
    
       - eth: fix return value of __setup handlers"
    
    * tag 'net-5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (92 commits)
      ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
      net: dsa: make dsa_tree_change_tag_proto actually unwind the tag proto change
      ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc()
      selftests: mlxsw: resource_scale: Fix return value
      selftests: mlxsw: tc_police_scale: Make test more robust
      net: dcb: disable softirqs in dcbnl_flush_dev()
      bnx2: Fix an error message
      sfc: extend the locking on mcdi->seqno
      net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server
      net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client
      net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()
      tcp: make tcp_read_sock() more robust
      bpf, sockmap: Do not ignore orig_len parameter
      net: ipa: add an interconnect dependency
      net: fix up skbs delta_truesize in UDP GRO frag_list
      iwlwifi: mvm: return value for request_ownership
      nl80211: Update bss channel on channel switch for P2P_CLIENT
      iwlwifi: fix build error for IWLMEI
      ptp: ocp: Add ptp_ocp_adjtime_coarse for large adjustments
      batman-adv: Don't expect inter-netns unique iflink indices
      ...

commit e58bd49da6eb4ba80175f82025d6c0e084237abf
Merge: 4d5ae2340dd4f 5d8965704fe56
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 3 10:38:28 2022 -0800

    Merge tag 'mips-fixes-5.17_4' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
    
    Pull MIPS fixes from Thomas Bogendoerfer:
    
     - Fix memory detection for MT7621 devices
    
     - Fix setnocoherentio kernel option
    
     - Fix warning when CONFIG_SCHED_CORE is enabled
    
    * tag 'mips-fixes-5.17_4' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux:
      MIPS: ralink: mt7621: use bitwise NOT instead of logical
      mips: setup: fix setnocoherentio() boolean setting
      MIPS: smp: fill in sibling and core maps earlier
      MIPS: ralink: mt7621: do memory detection on KSEG1

commit 4d5ae2340dd4f0298e607e0792b0881693657279
Merge: 5859a2b199110 9ed331f8a0fb6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Mar 3 10:31:09 2022 -0800

    Merge tag 'auxdisplay-for-linus-v5.17-rc7' of git://github.com/ojeda/linux
    
    Pull auxdisplay fixes from Miguel Ojeda:
     "A few lcd2s fixes from Andy Shevchenko"
    
    * tag 'auxdisplay-for-linus-v5.17-rc7' of git://github.com/ojeda/linux:
      auxdisplay: lcd2s: Use proper API to free the instance of charlcd object
      auxdisplay: lcd2s: Fix memory leak in ->remove()
      auxdisplay: lcd2s: Fix lcd2s_redefine_char() feature

commit 2d3916f3189172d5c69d33065c3c21119fe539fc
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Mar 3 09:37:28 2022 -0800

    ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
    
    While investigating on why a synchronize_net() has been added recently
    in ipv6_mc_down(), I found that igmp6_event_query() and igmp6_event_report()
    might drop skbs in some cases.
    
    Discussion about removing synchronize_net() from ipv6_mc_down()
    will happen in a different thread.
    
    Fixes: f185de28d9ae ("mld: add new workqueues for process mld events")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Taehee Yoo <ap420073@gmail.com>
    Cc: Cong Wang <xiyou.wangcong@gmail.com>
    Cc: David Ahern <dsahern@kernel.org>
    Link: https://lore.kernel.org/r/20220303173728.937869-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e1bec7fa1cee311a6d3fb9161037c7675904134d
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Mar 3 17:42:49 2022 +0200

    net: dsa: make dsa_tree_change_tag_proto actually unwind the tag proto change
    
    The blamed commit said one thing but did another. It explains that we
    should restore the "return err" to the original "goto out_unwind_tagger",
    but instead it replaced it with "goto out_unlock".
    
    When DSA_NOTIFIER_TAG_PROTO fails after the first switch of a
    multi-switch tree, the switches would end up not using the same tagging
    protocol.
    
    Fixes: 0b0e2ff10356 ("net: dsa: restore error path of dsa_tree_change_tag_proto")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220303154249.1854436-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6c7273a266759d9d36f7c862149f248bcdeddc0f
Author: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Date:   Wed Mar 2 09:59:27 2022 -0800

    ixgbe: xsk: change !netif_carrier_ok() handling in ixgbe_xmit_zc()
    
    Commit c685c69fba71 ("ixgbe: don't do any AF_XDP zero-copy transmit if
    netif is not OK") addressed the ring transient state when
    MEM_TYPE_XSK_BUFF_POOL was being configured which in turn caused the
    interface to through down/up. Maurice reported that when carrier is not
    ok and xsk_pool is present on ring pair, ksoftirqd will consume 100% CPU
    cycles due to the constant NAPI rescheduling as ixgbe_poll() states that
    there is still some work to be done.
    
    To fix this, do not set work_done to false for a !netif_carrier_ok().
    
    Fixes: c685c69fba71 ("ixgbe: don't do any AF_XDP zero-copy transmit if netif is not OK")
    Reported-by: Maurice Baijens <maurice.baijens@ellips.com>
    Tested-by: Maurice Baijens <maurice.baijens@ellips.com>
    Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 312f2d500af55823b96cd33b6b9bf6c4c0bc6e78
Merge: 10b6bb62ae1a4 196f9bc050cbc
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Mar 3 08:14:04 2022 -0800

    Merge branch 'selftests-mlxsw-a-couple-of-fixes'
    
    Ido Schimmel says:
    
    ====================
    selftests: mlxsw: A couple of fixes
    
    Patch #1 fixes a breakage due to a change in iproute2 output. The real
    problem is not iproute2, but the fact that the check was not strict
    enough. Fixed by using JSON output instead. Targeting at net so that the
    test will pass as part of old and new kernels regardless of iproute2
    version.
    
    Patch #2 fixes an issue uncovered by the first one.
    ====================
    
    Link: https://lore.kernel.org/r/20220302161447.217447-1-idosch@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 196f9bc050cbc5085b4cbb61cce2efe380bc66d0
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Wed Mar 2 18:14:47 2022 +0200

    selftests: mlxsw: resource_scale: Fix return value
    
    The test runs several test cases and is supposed to return an error in
    case at least one of them failed.
    
    Currently, the check of the return value of each test case is in the
    wrong place, which can result in the wrong return value. For example:
    
     # TESTS='tc_police' ./resource_scale.sh
     TEST: 'tc_police' [default] 968                                     [FAIL]
             tc police offload count failed
     Error: mlxsw_spectrum: Failed to allocate policer index.
     We have an error talking to the kernel
     Command failed /tmp/tmp.i7Oc5HwmXY:969
     TEST: 'tc_police' [default] overflow 969                            [ OK ]
     ...
     TEST: 'tc_police' [ipv4_max] overflow 969                           [ OK ]
    
     $ echo $?
     0
    
    Fix this by moving the check to be done after each test case.
    
    Fixes: 059b18e21c63 ("selftests: mlxsw: Return correct error code in resource scale test")
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit dc9752075341e7beb653e37c6f4a3723074dc8bc
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Wed Mar 2 18:14:46 2022 +0200

    selftests: mlxsw: tc_police_scale: Make test more robust
    
    The test adds tc filters and checks how many of them were offloaded by
    grepping for 'in_hw'.
    
    iproute2 commit f4cd4f127047 ("tc: add skip_hw and skip_sw to control
    action offload") added offload indication to tc actions, producing the
    following output:
    
     $ tc filter show dev swp2 ingress
     ...
     filter protocol ipv6 pref 1000 flower chain 0 handle 0x7c0
       eth_type ipv6
       dst_ip 2001:db8:1::7bf
       skip_sw
       in_hw in_hw_count 1
             action order 1:  police 0x7c0 rate 10Mbit burst 100Kb mtu 2Kb action drop overhead 0b
             ref 1 bind 1
             not_in_hw
             used_hw_stats immediate
    
    The current grep expression matches on both 'in_hw' and 'not_in_hw',
    resulting in incorrect results.
    
    Fix that by using JSON output instead.
    
    Fixes: 5061e773264b ("selftests: mlxsw: Add scale test for tc-police")
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 10b6bb62ae1a49ee818fc479cf57b8900176773e
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Wed Mar 2 21:39:39 2022 +0200

    net: dcb: disable softirqs in dcbnl_flush_dev()
    
    Ido Schimmel points out that since commit 52cff74eef5d ("dcbnl : Disable
    software interrupts before taking dcb_lock"), the DCB API can be called
    by drivers from softirq context.
    
    One such in-tree example is the chelsio cxgb4 driver:
    dcb_rpl
    -> cxgb4_dcb_handle_fw_update
       -> dcb_ieee_setapp
    
    If the firmware for this driver happened to send an event which resulted
    in a call to dcb_ieee_setapp() at the exact same time as another
    DCB-enabled interface was unregistering on the same CPU, the softirq
    would deadlock, because the interrupted process was already holding the
    dcb_lock in dcbnl_flush_dev().
    
    Fix this unlikely event by using spin_lock_bh() in dcbnl_flush_dev() as
    in the rest of the dcbnl code.
    
    Fixes: 91b0383fef06 ("net: dcb: flush lingering app table entries for unregistered devices")
    Reported-by: Ido Schimmel <idosch@idosch.org>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220302193939.1368823-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8ccffe9ac3239e549beaa0a9d5e1a1eac94e866c
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Wed Mar 2 21:21:15 2022 +0100

    bnx2: Fix an error message
    
    Fix an error message and report the correct failing function.
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f1fb205efb0ccca55626fd4ef38570dd16b44719
Author: Niels Dossche <dossche.niels@gmail.com>
Date:   Tue Mar 1 23:28:22 2022 +0100

    sfc: extend the locking on mcdi->seqno
    
    seqno could be read as a stale value outside of the lock. The lock is
    already acquired to protect the modification of seqno against a possible
    race condition. Place the reading of this value also inside this locking
    to protect it against a possible race condition.
    
    Signed-off-by: Niels Dossche <dossche.niels@gmail.com>
    Acked-by: Martin Habets <habetsm.xilinx@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 008ee9eb8a11bcabf12c91771dd4f470b082bd44
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Wed Mar 2 13:02:45 2022 -0800

    Bluetooth: hci_sync: Fix not processing all entries on cmd_sync_work
    
    hci_cmd_sync_queue can be called multiple times, each adding a
    hci_cmd_sync_work_entry, before hci_cmd_sync_work is run so this makes
    sure they are all dequeued properly otherwise it creates a backlog of
    entries that are never run.
    
    Link: https://lore.kernel.org/all/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com/T/
    Fixes: 6a98e3836fa20 ("Bluetooth: Add helper for serialized HCI command execution")
    Tested-by: Chris Clayton <chris2553@googlemail.com>
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 815d5121927093017947fd76e627da03f0f70be7
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Mar 2 14:44:39 2022 +0100

    Bluetooth: hci_core: Fix unbalanced unlock in set_device_flags()
    
    There is only one "goto done;" in set_device_flags() and this happens
    *before* hci_dev_lock() is called, move the done label to after the
    hci_dev_unlock() to fix the following unlock balance:
    
    [   31.493567] =====================================
    [   31.493571] WARNING: bad unlock balance detected!
    [   31.493576] 5.17.0-rc2+ #13 Tainted: G         C  E
    [   31.493581] -------------------------------------
    [   31.493584] bluetoothd/685 is trying to release lock (&hdev->lock) at:
    [   31.493594] [<ffffffffc07603f5>] set_device_flags+0x65/0x1f0 [bluetooth]
    [   31.493684] but there are no more locks to release!
    
    Note this bug has been around for a couple of years, but before
    commit fe92ee6425a2 ("Bluetooth: hci_core: Rework hci_conn_params flags")
    supported_flags was hardcoded to "((1U << HCI_CONN_FLAG_MAX) - 1)" so
    the check for unsupported flags which does the "goto done;" never
    triggered.
    
    Fixes: fe92ee6425a2 ("Bluetooth: hci_core: Rework hci_conn_params flags")
    Cc: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit f8e9bd34cedd89b93b1167aa32ab8ecd6c2ccf4a
Merge: bd6f1fd5d33df 4940a1fdf31c3
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Mar 3 10:34:18 2022 +0000

    Merge branch 'smc-fix'
    
    D. Wythe says:
    
    ====================
    fix unexpected SMC_CLC_DECL_ERR_REGRMB error
    
    We can easily trigger the SMC_CLC_DECL_ERR_REGRMB exception within
    following script:
    
    server: smc_run nginx
    client: smc_run  ./wrk -c 2000 -t 8 -d 20 http://smc-server
    
    And we can clearly see that this error is also divided into two types:
    
    1. 0x09990003
    2. 0x05000000/0x09990003
    
    Which has the same root causes, but the immediate causes vary.
    
    The root cause of this issues is that remove connections from link group
    is not synchronous with add/delete rtoken entry,  which means that even
    the number of connections is less that SMC_RMBS_PER_LGR_MAX, it does not
    mean that the connection can register rtoken successfully later. In
    other words, the rtoken entry may released, This will cause an
    unexpected SMC_CLC_DECL_ERR_REGRMB to be reported, and then this SMC
    connections have to fallback to TCP.
    
    This patch set handles two types of SMC_CLC_DECL_ERR_REGRMB exceptions
    from different perspectives.
    
    Patch 1: fix the 0x05000000/0x09990003 error.
    Patch 2: fix the 0x09990003 error.
    
    After those patches, there is no SMC_CLC_DECL_ERR_REGRMB exceptions in
    my
    test case any more.
    
    v1 -> v2:
    - add bugfix patch for SMC_CLC_DECL_ERR_REGRMB cause by server side
    v2 -> v3:
    - fix incorrect mail thread
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4940a1fdf31c39f0806ac831cde333134862030b
Author: D. Wythe <alibuda@linux.alibaba.com>
Date:   Wed Mar 2 21:25:12 2022 +0800

    net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error cause by server
    
    The problem of SMC_CLC_DECL_ERR_REGRMB on the server is very clear.
    Based on the fact that whether a new SMC connection can be accepted or
    not depends on not only the limit of conn nums, but also the available
    entries of rtoken. Since the rtoken release is trigger by peer, while
    the conn nums is decrease by local, tons of thing can happen in this
    time difference.
    
    This only thing that needs to be mentioned is that now all connection
    creations are completely protected by smc_server_lgr_pending lock, it's
    enough to check only the available entries in rtokens_used_mask.
    
    Fixes: cd6851f30386 ("smc: remote memory buffers (RMBs)")
    Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0537f0a2151375dcf90c1bbfda6a0aaf57164e89
Author: D. Wythe <alibuda@linux.alibaba.com>
Date:   Wed Mar 2 21:25:11 2022 +0800

    net/smc: fix unexpected SMC_CLC_DECL_ERR_REGRMB error generated by client
    
    The main reason for this unexpected SMC_CLC_DECL_ERR_REGRMB in client
    dues to following execution sequence:
    
    Server Conn A:           Server Conn B:                 Client Conn B:
    
    smc_lgr_unregister_conn
                            smc_lgr_register_conn
                            smc_clc_send_accept     ->
                                                            smc_rtoken_add
    smcr_buf_unuse
                    ->              Client Conn A:
                                    smc_rtoken_delete
    
    smc_lgr_unregister_conn() makes current link available to assigned to new
    incoming connection, while smcr_buf_unuse() has not executed yet, which
    means that smc_rtoken_add may fail because of insufficient rtoken_entry,
    reversing their execution order will avoid this problem.
    
    Fixes: 3e034725c0d8 ("net/smc: common functions for RMBs and send buffers")
    Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit bd6f1fd5d33dfe5d1b4f2502d3694a7cc13f166d
Author: Zheyu Ma <zheyuma97@gmail.com>
Date:   Wed Mar 2 20:24:23 2022 +0800

    net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()
    
    During driver initialization, the pointer of card info, i.e. the
    variable 'ci' is required. However, the definition of
    'com20020pci_id_table' reveals that this field is empty for some
    devices, which will cause null pointer dereference when initializing
    these devices.
    
    The following log reveals it:
    
    [    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
    [    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]
    [    3.975181] Call Trace:
    [    3.976208]  local_pci_probe+0x13f/0x210
    [    3.977248]  pci_device_probe+0x34c/0x6d0
    [    3.977255]  ? pci_uevent+0x470/0x470
    [    3.978265]  really_probe+0x24c/0x8d0
    [    3.978273]  __driver_probe_device+0x1b3/0x280
    [    3.979288]  driver_probe_device+0x50/0x370
    
    Fix this by checking whether the 'ci' is a null pointer first.
    
    Fixes: 8c14f9c70327 ("ARCNET: add com20020 PCI IDs with metadata")
    Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e3d5ea2c011ecb16fb94c56a659364e6b30fac94
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Mar 2 08:17:23 2022 -0800

    tcp: make tcp_read_sock() more robust
    
    If recv_actor() returns an incorrect value, tcp_read_sock()
    might loop forever.
    
    Instead, issue a one time warning and make sure to make progress.
    
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Jakub Sitnicki <jakub@cloudflare.com>
    Acked-by: Daniel Borkmann <daniel@iogearbox.net>
    Link: https://lore.kernel.org/r/20220302161723.3910001-2-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 60ce37b03917e593d8e5d8bcc7ec820773daf81d
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Mar 2 08:17:22 2022 -0800

    bpf, sockmap: Do not ignore orig_len parameter
    
    Currently, sk_psock_verdict_recv() returns skb->len
    
    This is problematic because tcp_read_sock() might have
    passed orig_len < skb->len, due to the presence of TCP urgent data.
    
    This causes an infinite loop from tcp_read_sock()
    
    Followup patch will make tcp_read_sock() more robust vs bad actors.
    
    Fixes: ef5659280eb1 ("bpf, sockmap: Allow skipping sk_skb parser program")
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Jakub Sitnicki <jakub@cloudflare.com>
    Tested-by: Jakub Sitnicki <jakub@cloudflare.com>
    Acked-by: Daniel Borkmann <daniel@iogearbox.net>
    Link: https://lore.kernel.org/r/20220302161723.3910001-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 1dba41c9d2e2dc94b543394974f63d55aa195bfe
Author: Alex Elder <elder@linaro.org>
Date:   Tue Mar 1 05:34:40 2022 -0600

    net: ipa: add an interconnect dependency
    
    In order to function, the IPA driver very clearly requires the
    interconnect framework to be enabled in the kernel configuration.
    State that dependency in the Kconfig file.
    
    This became a problem when CONFIG_COMPILE_TEST support was added.
    Non-Qualcomm platforms won't necessarily enable CONFIG_INTERCONNECT.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 38a4066f593c5 ("net: ipa: support COMPILE_TEST")
    Signed-off-by: Alex Elder <elder@linaro.org>
    Link: https://lore.kernel.org/r/20220301113440.257916-1-elder@linaro.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 224102de2ff105a2c05695e66a08f4b5b6b2d19c
Author: lena wang <lena.wang@mediatek.com>
Date:   Tue Mar 1 19:17:09 2022 +0800

    net: fix up skbs delta_truesize in UDP GRO frag_list
    
    The truesize for a UDP GRO packet is added by main skb and skbs in main
    skb's frag_list:
    skb_gro_receive_list
            p->truesize += skb->truesize;
    
    The commit 53475c5dd856 ("net: fix use-after-free when UDP GRO with
    shared fraglist") introduced a truesize increase for frag_list skbs.
    When uncloning skb, it will call pskb_expand_head and trusesize for
    frag_list skbs may increase. This can occur when allocators uses
    __netdev_alloc_skb and not jump into __alloc_skb. This flow does not
    use ksize(len) to calculate truesize while pskb_expand_head uses.
    skb_segment_list
    err = skb_unclone(nskb, GFP_ATOMIC);
    pskb_expand_head
            if (!skb->sk || skb->destructor == sock_edemux)
                    skb->truesize += size - osize;
    
    If we uses increased truesize adding as delta_truesize, it will be
    larger than before and even larger than previous total truesize value
    if skbs in frag_list are abundant. The main skb truesize will become
    smaller and even a minus value or a huge value for an unsigned int
    parameter. Then the following memory check will drop this abnormal skb.
    
    To avoid this error we should use the original truesize to segment the
    main skb.
    
    Fixes: 53475c5dd856 ("net: fix use-after-free when UDP GRO with shared fraglist")
    Signed-off-by: lena wang <lena.wang@mediatek.com>
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Link: https://lore.kernel.org/r/1646133431-8948-1-git-send-email-lena.wang@mediatek.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ea97ab9889b0125d2256e5131d854c370aab8212
Merge: 95749c1033798 6c1f41afc1dbe
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Mar 2 21:53:34 2022 -0800

    Merge tag 'batadv-net-pullrequest-20220302' of git://git.open-mesh.org/linux-merge
    
    Simon Wunderlich says:
    
    ====================
    Here are some batman-adv bugfixes:
    
     - Remove redundant iflink requests, by Sven Eckelmann (2 patches)
    
     - Don't expect inter-netns unique iflink indices, by Sven Eckelmann
    
    * tag 'batadv-net-pullrequest-20220302' of git://git.open-mesh.org/linux-merge:
      batman-adv: Don't expect inter-netns unique iflink indices
      batman-adv: Request iflink once in batadv_get_real_netdevice
      batman-adv: Request iflink once in batadv-on-batadv check
    ====================
    
    Link: https://lore.kernel.org/r/20220302163049.101957-1-sw@simonwunderlich.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 95749c103379814780b5e2e8cbb168b744047841
Merge: 90f8f4c0e3ceb e6e91ec966db5
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Mar 2 21:49:57 2022 -0800

    Merge tag 'wireless-for-net-2022-03-02' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless
    
    Johannes Berg says:
    
    ====================
    Three more fixes:
     - fix build issue in iwlwifi, now that I understood
       what's going on there
     - propagate error in iwlwifi/mvm to userspace so it
       can figure out what's happening
     - fix channel switch related updates in P2P-client
       in cfg80211
    
    * tag 'wireless-for-net-2022-03-02' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless:
      iwlwifi: mvm: return value for request_ownership
      nl80211: Update bss channel on channel switch for P2P_CLIENT
      iwlwifi: fix build error for IWLMEI
    ====================
    
    Link: https://lore.kernel.org/r/20220302214444.100180-1-johannes@sipsolutions.net
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5859a2b1991101d6b978f3feb5325dad39421f29
Merge: 7e3d76139b5da 0ac983f512033
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 2 16:20:04 2022 -0800

    Merge branch 'ucount-rlimit-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
    
    Pull ucounts fix from Eric Biederman:
     "Etienne Dechamps recently found a regression caused by enforcing
      RLIMIT_NPROC for root where the rlimit was not previously enforced.
    
      Michal Koutný had previously pointed out the inconsistency in
      enforcing the RLIMIT_NPROC that had been on the root owned process
      after the root user creates a user namespace.
    
      Which makes the fix for the regression simply removing the
      inconsistency"
    
    * 'ucount-rlimit-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace:
      ucounts: Fix systemd LimitNPROC with private users regression

commit 7e3d76139b5da7f58bda13c485e8e208ffce5c9c
Merge: 92ebf5f91b4dd 7b83299e5b938
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 2 16:11:56 2022 -0800

    Merge tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm
    
    Pull ARM fixes from Russell King:
    
     - Fix kgdb breakpoint for Thumb2
    
     - Fix dependency for BITREVERSE kconfig
    
     - Fix nommu early_params and __setup returns
    
    * tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm:
      ARM: 9182/1: mmu: fix returns from early_param() and __setup() functions
      ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE
      ARM: Fix kgdb breakpoint for Thumb2

commit f1ef17011c765495c876fa75435e59eecfdc1ee4
Author: Qiang Yu <qiang.yu@amd.com>
Date:   Tue Mar 1 14:11:59 2022 +0800

    drm/amdgpu: fix suspend/resume hang regression
    
    Regression has been reported that suspend/resume may hang with
    the previous vm ready check commit.
    
    So bring back the evicted list check as a temp fix.
    
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1922
    Fixes: c1a66c3bc425 ("drm/amdgpu: check vm ready by amdgpu_vm->evicting flag")
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Qiang Yu <qiang.yu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 9ed331f8a0fb674f4f06edf05a1687bf755af27b
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Feb 23 17:47:18 2022 +0200

    auxdisplay: lcd2s: Use proper API to free the instance of charlcd object
    
    While it might work, the current approach is fragile in a few ways:
    - whenever members in the structure are shuffled, the pointer will be wrong
    - the resource freeing may include more than covered by kfree()
    
    Fix this by using charlcd_free() call instead of kfree().
    
    Fixes: 8c9108d014c5 ("auxdisplay: add a driver for lcd2s character display")
    Cc: Lars Poeschel <poeschel@lemonage.de>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

commit 898c0a15425a5bcaa8d44bd436eae5afd2483796
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Feb 23 17:47:17 2022 +0200

    auxdisplay: lcd2s: Fix memory leak in ->remove()
    
    Once allocated the struct lcd2s_data is never freed.
    Fix the memory leak by switching to devm_kzalloc().
    
    Fixes: 8c9108d014c5 ("auxdisplay: add a driver for lcd2s character display")
    Cc: Lars Poeschel <poeschel@lemonage.de>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

commit 4424c35ead667ba2e8de7ab8206da66453e6f728
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Feb 23 17:47:16 2022 +0200

    auxdisplay: lcd2s: Fix lcd2s_redefine_char() feature
    
    It seems that the lcd2s_redefine_char() has never been properly
    tested. The buffer is filled by DEF_CUSTOM_CHAR command followed
    by the character number (from 0 to 7), but immediately after that
    these bytes are rewritten by the decoded hex stream.
    
    Fix the index to fill the buffer after the command and number.
    
    Fixes: 8c9108d014c5 ("auxdisplay: add a driver for lcd2s character display")
    Cc: Lars Poeschel <poeschel@lemonage.de>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
    [fixed typo in commit message]
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

commit e6e91ec966db5af4f059cfbac1af06560404b317
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Wed Mar 2 09:27:15 2022 +0200

    iwlwifi: mvm: return value for request_ownership
    
    Propagate the value to the user space so it can understand
    if the operation failed or not.
    
    Fixes: bfcfdb59b669 ("iwlwifi: mvm: add vendor commands needed for iwlmei")
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Link: https://lore.kernel.org/r/20220302072715.4885-1-emmanuel.grumbach@intel.com
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit e50b88c4f076242358b66ddb67482b96947438f2
Author: Sreeramya Soratkal <quic_ssramya@quicinc.com>
Date:   Tue Mar 1 11:33:20 2022 +0530

    nl80211: Update bss channel on channel switch for P2P_CLIENT
    
    The wdev channel information is updated post channel switch only for
    the station mode and not for the other modes. Due to this, the P2P client
    still points to the old value though it moved to the new channel
    when the channel change is induced from the P2P GO.
    
    Update the bss channel after CSA channel switch completion for P2P client
    interface as well.
    
    Signed-off-by: Sreeramya Soratkal <quic_ssramya@quicinc.com>
    Link: https://lore.kernel.org/r/1646114600-31479-1-git-send-email-quic_ssramya@quicinc.com
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 875ad06015329314c594d3302ac2bbea37774543
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sun Feb 27 12:00:51 2022 -0800

    iwlwifi: fix build error for IWLMEI
    
    When CONFIG_IWLWIFI=m and CONFIG_IWLMEI=y, the kernel build system
    must be told to build the iwlwifi/ subdirectory for both IWLWIFI and
    IWLMEI so that builds for both =y and =m are done.
    
    This resolves an undefined reference build error:
    
    ERROR: modpost: "iwl_mei_is_connected" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!
    
    Fixes: 977df8bd5844 ("wlwifi: work around reverse dependency on MEI")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Luca Coelho <luciano.coelho@intel.com>
    Cc: linux-wireless@vger.kernel.org
    Link: https://lore.kernel.org/r/20220227200051.7176-1-rdunlap@infradead.org
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 92ebf5f91b4dd5156886d2509202be0fb4230dfd
Merge: ae5f531d1766a 22ba5e99b96f1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 2 12:08:36 2022 -0800

    Merge tag 'erofs-for-5.17-rc7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
    
    Pull erofs fix from Gao Xiang:
     "A one-line patch to fix the new ztailpacking feature on > 4GiB
      filesystems because z_idataoff can get trimmed improperly.
    
      ztailpacking is still a brand new EXPERIMENTAL feature, but it'd be
      better to fix the issue as soon as possible to avoid unnecessary
      backporting.
    
      Summary:
    
       - Fix ztailpacking z_idataoff getting trimmed on > 4GiB filesystems"
    
    * tag 'erofs-for-5.17-rc7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
      erofs: fix ztailpacking on > 4GiB filesystems

commit ae5f531d1766a2cc98857707671223ff1284236d
Merge: fb184c4af9b9f 9b818634f8e7e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Mar 2 11:58:27 2022 -0800

    Merge tag 'ntb-5.17-bugfixes' of git://github.com/jonmason/ntb
    
    Pull NTB fixes from Jon Mason:
     "Bug fixes for sparse warning, intel port config offset, and a new
      mailing list"
    
    * tag 'ntb-5.17-bugfixes' of git://github.com/jonmason/ntb:
      MAINTAINERS: update mailing list address for NTB subsystem
      ntb: intel: fix port config status offset for SPR
      NTB/msi: Use struct_size() helper in devm_kzalloc()

commit 90f8f4c0e3cebd541deaa45cf0e470bb9810dd4f
Author: Jonathan Lemon <jonathan.lemon@gmail.com>
Date:   Mon Feb 28 12:39:57 2022 -0800

    ptp: ocp: Add ptp_ocp_adjtime_coarse for large adjustments
    
    In ("ptp: ocp: Have FPGA fold in ns adjustment for adjtime."), the
    ns adjustment was written to the FPGA register, so the clock could
    accurately perform adjustments.
    
    However, the adjtime() call passes in a s64, while the clock adjustment
    registers use a s32.  When trying to perform adjustments with a large
    value (37 sec), things fail.
    
    Examine the incoming delta, and if larger than 1 sec, use the original
    (coarse) adjustment method.  If smaller than 1 sec, then allow the
    FPGA to fold in the changes over a 1 second window.
    
    Fixes: 6d59d4fa1789 ("ptp: ocp: Have FPGA fold in ns adjustment for adjtime.")
    Signed-off-by: Jonathan Lemon <jonathan.lemon@gmail.com>
    Acked-by: Richard Cochran <richardcochran@gmail.com>
    Link: https://lore.kernel.org/r/20220228203957.367371-1-jonathan.lemon@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8d25b7beca7ed6ca34f53f0f8abd009e2be15d94
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Sat Feb 19 04:28:20 2022 -0500

    KVM: x86: pull kvm->srcu read-side to kvm_arch_vcpu_ioctl_run
    
    kvm_arch_vcpu_ioctl_run is already doing srcu_read_lock/unlock in two
    places, namely vcpu_run and post_kvm_run_save, and a third is actually
    needed around the call to vcpu->arch.complete_userspace_io to avoid
    the following splat:
    
      WARNING: suspicious RCU usage
      arch/x86/kvm/pmu.c:190 suspicious rcu_dereference_check() usage!
      other info that might help us debug this:
      rcu_scheduler_active = 2, debug_locks = 1
      1 lock held by CPU 28/KVM/370841:
      #0: ff11004089f280b8 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x87/0x730 [kvm]
      Call Trace:
       <TASK>
       dump_stack_lvl+0x59/0x73
       reprogram_fixed_counter+0x15d/0x1a0 [kvm]
       kvm_pmu_trigger_event+0x1a3/0x260 [kvm]
       ? free_moved_vector+0x1b4/0x1e0
       complete_fast_pio_in+0x8a/0xd0 [kvm]
    
    This splat is not at all unexpected, since complete_userspace_io callbacks
    can execute similar code to vmexits.  For example, SVM with nrips=false
    will call into the emulator from svm_skip_emulated_instruction().
    
    While it's tempting to never acquire kvm->srcu for an uninitialized vCPU,
    practically speaking there's no penalty to acquiring kvm->srcu "early"
    as the KVM_MP_STATE_UNINITIALIZED path is a one-time thing per vCPU.  On
    the other hand, seemingly innocuous helpers like kvm_apic_accept_events()
    and sync_regs() can theoretically reach code that might access
    SRCU-protected data structures, e.g. sync_regs() can trigger forced
    existing of nested mode via kvm_vcpu_ioctl_x86_set_vcpu_events().
    
    Reported-by: Like Xu <likexu@tencent.com>
    Co-developed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c6c937d673aaa1d603f62f134e1ca9c173eeeed3
Author: Like Xu <likexu@tencent.com>
Date:   Tue Mar 1 20:49:41 2022 +0800

    KVM: x86/mmu: Passing up the error state of mmu_alloc_shadow_roots()
    
    Just like on the optional mmu_alloc_direct_roots() path, once shadow
    path reaches "r = -EIO" somewhere, the caller needs to know the actual
    state in order to enter error handling and avoid something worse.
    
    Fixes: 4a38162ee9f1 ("KVM: MMU: load PDPTRs outside mmu_lock")
    Signed-off-by: Like Xu <likexu@tencent.com>
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220301124941.48412-1-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4751dc99627e4d1465c5bfa8cb7ab31ed418eff5
Author: Filipe Manana <fdmanana@suse.com>
Date:   Mon Feb 28 16:29:28 2022 +0000

    btrfs: add missing run of delayed items after unlink during log replay
    
    During log replay, whenever we need to check if a name (dentry) exists in
    a directory we do searches on the subvolume tree for inode references or
    or directory entries (BTRFS_DIR_INDEX_KEY keys, and BTRFS_DIR_ITEM_KEY
    keys as well, before kernel 5.17). However when during log replay we
    unlink a name, through btrfs_unlink_inode(), we may not delete inode
    references and dir index keys from a subvolume tree and instead just add
    the deletions to the delayed inode's delayed items, which will only be
    run when we commit the transaction used for log replay. This means that
    after an unlink operation during log replay, if we attempt to search for
    the same name during log replay, we will not see that the name was already
    deleted, since the deletion is recorded only on the delayed items.
    
    We run delayed items after every unlink operation during log replay,
    except at unlink_old_inode_refs() and at add_inode_ref(). This was due
    to an overlook, as delayed items should be run after evert unlink, for
    the reasons stated above.
    
    So fix those two cases.
    
    Fixes: 0d836392cadd5 ("Btrfs: fix mount failure after fsync due to hard link recreation")
    Fixes: 1f250e929a9c9 ("Btrfs: fix log replay failure after unlink and link combination")
    CC: stable@vger.kernel.org # 4.19+
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d4aef1e122d8bbdc15ce3bd0bc813d6b44a7d63a
Author: Sidong Yang <realwakka@gmail.com>
Date:   Mon Feb 28 01:43:40 2022 +0000

    btrfs: qgroup: fix deadlock between rescan worker and remove qgroup
    
    The commit e804861bd4e6 ("btrfs: fix deadlock between quota disable and
    qgroup rescan worker") by Kawasaki resolves deadlock between quota
    disable and qgroup rescan worker. But also there is a deadlock case like
    it. It's about enabling or disabling quota and creating or removing
    qgroup. It can be reproduced in simple script below.
    
    for i in {1..100}
    do
        btrfs quota enable /mnt &
        btrfs qgroup create 1/0 /mnt &
        btrfs qgroup destroy 1/0 /mnt &
        btrfs quota disable /mnt &
    done
    
    Here's why the deadlock happens:
    
    1) The quota rescan task is running.
    
    2) Task A calls btrfs_quota_disable(), locks the qgroup_ioctl_lock
       mutex, and then calls btrfs_qgroup_wait_for_completion(), to wait for
       the quota rescan task to complete.
    
    3) Task B calls btrfs_remove_qgroup() and it blocks when trying to lock
       the qgroup_ioctl_lock mutex, because it's being held by task A. At that
       point task B is holding a transaction handle for the current transaction.
    
    4) The quota rescan task calls btrfs_commit_transaction(). This results
       in it waiting for all other tasks to release their handles on the
       transaction, but task B is blocked on the qgroup_ioctl_lock mutex
       while holding a handle on the transaction, and that mutex is being held
       by task A, which is waiting for the quota rescan task to complete,
       resulting in a deadlock between these 3 tasks.
    
    To resolve this issue, the thread disabling quota should unlock
    qgroup_ioctl_lock before waiting rescan completion. Move
    btrfs_qgroup_wait_for_completion() after unlock of qgroup_ioctl_lock.
    
    Fixes: e804861bd4e6 ("btrfs: fix deadlock between quota disable and qgroup rescan worker")
    CC: stable@vger.kernel.org # 5.4+
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
    Signed-off-by: Sidong Yang <realwakka@gmail.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 5fd76bf31ccfecc06e2e6b29f8c809e934085b99
Author: Omar Sandoval <osandov@fb.com>
Date:   Thu Feb 17 15:14:43 2022 -0800

    btrfs: fix relocation crash due to premature return from btrfs_commit_transaction()
    
    We are seeing crashes similar to the following trace:
    
    [38.969182] WARNING: CPU: 20 PID: 2105 at fs/btrfs/relocation.c:4070 btrfs_relocate_block_group+0x2dc/0x340 [btrfs]
    [38.973556] CPU: 20 PID: 2105 Comm: btrfs Not tainted 5.17.0-rc4 #54
    [38.974580] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
    [38.976539] RIP: 0010:btrfs_relocate_block_group+0x2dc/0x340 [btrfs]
    [38.980336] RSP: 0000:ffffb0dd42e03c20 EFLAGS: 00010206
    [38.981218] RAX: ffff96cfc4ede800 RBX: ffff96cfc3ce0000 RCX: 000000000002ca14
    [38.982560] RDX: 0000000000000000 RSI: 4cfd109a0bcb5d7f RDI: ffff96cfc3ce0360
    [38.983619] RBP: ffff96cfc309c000 R08: 0000000000000000 R09: 0000000000000000
    [38.984678] R10: ffff96cec0000001 R11: ffffe84c80000000 R12: ffff96cfc4ede800
    [38.985735] R13: 0000000000000000 R14: 0000000000000000 R15: ffff96cfc3ce0360
    [38.987146] FS:  00007f11c15218c0(0000) GS:ffff96d6dfb00000(0000) knlGS:0000000000000000
    [38.988662] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [38.989398] CR2: 00007ffc922c8e60 CR3: 00000001147a6001 CR4: 0000000000370ee0
    [38.990279] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [38.991219] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [38.992528] Call Trace:
    [38.992854]  <TASK>
    [38.993148]  btrfs_relocate_chunk+0x27/0xe0 [btrfs]
    [38.993941]  btrfs_balance+0x78e/0xea0 [btrfs]
    [38.994801]  ? vsnprintf+0x33c/0x520
    [38.995368]  ? __kmalloc_track_caller+0x351/0x440
    [38.996198]  btrfs_ioctl_balance+0x2b9/0x3a0 [btrfs]
    [38.997084]  btrfs_ioctl+0x11b0/0x2da0 [btrfs]
    [38.997867]  ? mod_objcg_state+0xee/0x340
    [38.998552]  ? seq_release+0x24/0x30
    [38.999184]  ? proc_nr_files+0x30/0x30
    [38.999654]  ? call_rcu+0xc8/0x2f0
    [39.000228]  ? __x64_sys_ioctl+0x84/0xc0
    [39.000872]  ? btrfs_ioctl_get_supported_features+0x30/0x30 [btrfs]
    [39.001973]  __x64_sys_ioctl+0x84/0xc0
    [39.002566]  do_syscall_64+0x3a/0x80
    [39.003011]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [39.003735] RIP: 0033:0x7f11c166959b
    [39.007324] RSP: 002b:00007fff2543e998 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
    [39.008521] RAX: ffffffffffffffda RBX: 00007f11c1521698 RCX: 00007f11c166959b
    [39.009833] RDX: 00007fff2543ea40 RSI: 00000000c4009420 RDI: 0000000000000003
    [39.011270] RBP: 0000000000000003 R08: 0000000000000013 R09: 00007f11c16f94e0
    [39.012581] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff25440df3
    [39.014046] R13: 0000000000000000 R14: 00007fff2543ea40 R15: 0000000000000001
    [39.015040]  </TASK>
    [39.015418] ---[ end trace 0000000000000000 ]---
    [43.131559] ------------[ cut here ]------------
    [43.132234] kernel BUG at fs/btrfs/extent-tree.c:2717!
    [43.133031] invalid opcode: 0000 [#1] PREEMPT SMP PTI
    [43.133702] CPU: 1 PID: 1839 Comm: btrfs Tainted: G        W         5.17.0-rc4 #54
    [43.134863] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014
    [43.136426] RIP: 0010:unpin_extent_range+0x37a/0x4f0 [btrfs]
    [43.139913] RSP: 0000:ffffb0dd4216bc70 EFLAGS: 00010246
    [43.140629] RAX: 0000000000000000 RBX: ffff96cfc34490f8 RCX: 0000000000000001
    [43.141604] RDX: 0000000080000001 RSI: 0000000051d00000 RDI: 00000000ffffffff
    [43.142645] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff96cfd07dca50
    [43.143669] R10: ffff96cfc46e8a00 R11: fffffffffffec000 R12: 0000000041d00000
    [43.144657] R13: ffff96cfc3ce0000 R14: ffffb0dd4216bd08 R15: 0000000000000000
    [43.145686] FS:  00007f7657dd68c0(0000) GS:ffff96d6df640000(0000) knlGS:0000000000000000
    [43.146808] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [43.147584] CR2: 00007f7fe81bf5b0 CR3: 00000001093ee004 CR4: 0000000000370ee0
    [43.148589] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [43.149581] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [43.150559] Call Trace:
    [43.150904]  <TASK>
    [43.151253]  btrfs_finish_extent_commit+0x88/0x290 [btrfs]
    [43.152127]  btrfs_commit_transaction+0x74f/0xaa0 [btrfs]
    [43.152932]  ? btrfs_attach_transaction_barrier+0x1e/0x50 [btrfs]
    [43.153786]  btrfs_ioctl+0x1edc/0x2da0 [btrfs]
    [43.154475]  ? __check_object_size+0x150/0x170
    [43.155170]  ? preempt_count_add+0x49/0xa0
    [43.155753]  ? __x64_sys_ioctl+0x84/0xc0
    [43.156437]  ? btrfs_ioctl_get_supported_features+0x30/0x30 [btrfs]
    [43.157456]  __x64_sys_ioctl+0x84/0xc0
    [43.157980]  do_syscall_64+0x3a/0x80
    [43.158543]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [43.159231] RIP: 0033:0x7f7657f1e59b
    [43.161819] RSP: 002b:00007ffda5cd1658 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
    [43.162702] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f7657f1e59b
    [43.163526] RDX: 0000000000000000 RSI: 0000000000009408 RDI: 0000000000000003
    [43.164358] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000
    [43.165208] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
    [43.166029] R13: 00005621b91c3232 R14: 00005621b91ba580 R15: 00007ffda5cd1800
    [43.166863]  </TASK>
    [43.167125] Modules linked in: btrfs blake2b_generic xor pata_acpi ata_piix libata raid6_pq scsi_mod libcrc32c virtio_net virtio_rng net_failover rng_core failover scsi_common
    [43.169552] ---[ end trace 0000000000000000 ]---
    [43.171226] RIP: 0010:unpin_extent_range+0x37a/0x4f0 [btrfs]
    [43.174767] RSP: 0000:ffffb0dd4216bc70 EFLAGS: 00010246
    [43.175600] RAX: 0000000000000000 RBX: ffff96cfc34490f8 RCX: 0000000000000001
    [43.176468] RDX: 0000000080000001 RSI: 0000000051d00000 RDI: 00000000ffffffff
    [43.177357] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff96cfd07dca50
    [43.178271] R10: ffff96cfc46e8a00 R11: fffffffffffec000 R12: 0000000041d00000
    [43.179178] R13: ffff96cfc3ce0000 R14: ffffb0dd4216bd08 R15: 0000000000000000
    [43.180071] FS:  00007f7657dd68c0(0000) GS:ffff96d6df800000(0000) knlGS:0000000000000000
    [43.181073] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [43.181808] CR2: 00007fe09905f010 CR3: 00000001093ee004 CR4: 0000000000370ee0
    [43.182706] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [43.183591] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    
    We first hit the WARN_ON(rc->block_group->pinned > 0) in
    btrfs_relocate_block_group() and then the BUG_ON(!cache) in
    unpin_extent_range(). This tells us that we are exiting relocation and
    removing the block group with bytes still pinned for that block group.
    This is supposed to be impossible: the last thing relocate_block_group()
    does is commit the transaction to get rid of pinned extents.
    
    Commit d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when
    waiting for a transaction commit") introduced an optimization so that
    commits from fsync don't have to wait for the previous commit to unpin
    extents. This was only intended to affect fsync, but it inadvertently
    made it possible for any commit to skip waiting for the previous commit
    to unpin. This is because if a call to btrfs_commit_transaction() finds
    that another thread is already committing the transaction, it waits for
    the other thread to complete the commit and then returns. If that other
    thread was in fsync, then it completes the commit without completing the
    previous commit. This makes the following sequence of events possible:
    
    Thread 1____________________|Thread 2 (fsync)_____________________|Thread 3 (balance)___________________
    btrfs_commit_transaction(N) |                                     |
      btrfs_run_delayed_refs    |                                     |
        pin extents             |                                     |
      ...                       |                                     |
      state = UNBLOCKED         |btrfs_sync_file                      |
                                |  btrfs_start_transaction(N + 1)     |relocate_block_group
                                |                                     |  btrfs_join_transaction(N + 1)
                                |  btrfs_commit_transaction(N + 1)    |
      ...                       |  trans->state = COMMIT_START        |
                                |                                     |  btrfs_commit_transaction(N + 1)
                                |                                     |    wait_for_commit(N + 1, COMPLETED)
                                |  wait_for_commit(N, SUPER_COMMITTED)|
      state = SUPER_COMMITTED   |  ...                                |
      btrfs_finish_extent_commit|                                     |
        unpin_extent_range()    |  trans->state = COMPLETED           |
                                |                                     |    return
                                |                                     |
        ...                     |                                     |Thread 1 isn't done, so pinned > 0
                                |                                     |and we WARN
                                |                                     |
                                |                                     |btrfs_remove_block_group
        unpin_extent_range()    |                                     |
          Thread 3 removed the  |                                     |
          block group, so we BUG|                                     |
    
    There are other sequences involving SUPER_COMMITTED transactions that
    can cause a similar outcome.
    
    We could fix this by making relocation explicitly wait for unpinning,
    but there may be other cases that need it. Josef mentioned ENOSPC
    flushing and the free space cache inode as other potential victims.
    Rather than playing whack-a-mole, this fix is conservative and makes all
    commits not in fsync wait for all previous transactions, which is what
    the optimization intended.
    
    Fixes: d0c2f4fa555e ("btrfs: make concurrent fsyncs wait less when waiting for a transaction commit")
    CC: stable@vger.kernel.org # 5.15+
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Omar Sandoval <osandov@fb.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit b4be6aefa73c9a6899ef3ba9c5faaa8a66e333ef
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Feb 18 14:56:10 2022 -0500

    btrfs: do not start relocation until in progress drops are done
    
    We hit a bug with a recovering relocation on mount for one of our file
    systems in production.  I reproduced this locally by injecting errors
    into snapshot delete with balance running at the same time.  This
    presented as an error while looking up an extent item
    
      WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680
      CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8
      RIP: 0010:lookup_inline_extent_backref+0x647/0x680
      RSP: 0018:ffffae0a023ab960 EFLAGS: 00010202
      RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000
      RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000
      RBP: ffff943fd2a39b60 R08: 0000000000000000 R09: 0000000000000001
      R10: 0001434088152de0 R11: 0000000000000000 R12: 0000000001d05000
      R13: ffff943fd2a39b60 R14: ffff943fdb96f2a0 R15: ffff9442fc923000
      FS:  0000000000000000(0000) GS:ffff944e9eb40000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 00007f1157b1fca8 CR3: 000000010f092000 CR4: 0000000000350ee0
      Call Trace:
       <TASK>
       insert_inline_extent_backref+0x46/0xd0
       __btrfs_inc_extent_ref.isra.0+0x5f/0x200
       ? btrfs_merge_delayed_refs+0x164/0x190
       __btrfs_run_delayed_refs+0x561/0xfa0
       ? btrfs_search_slot+0x7b4/0xb30
       ? btrfs_update_root+0x1a9/0x2c0
       btrfs_run_delayed_refs+0x73/0x1f0
       ? btrfs_update_root+0x1a9/0x2c0
       btrfs_commit_transaction+0x50/0xa50
       ? btrfs_update_reloc_root+0x122/0x220
       prepare_to_merge+0x29f/0x320
       relocate_block_group+0x2b8/0x550
       btrfs_relocate_block_group+0x1a6/0x350
       btrfs_relocate_chunk+0x27/0xe0
       btrfs_balance+0x777/0xe60
       balance_kthread+0x35/0x50
       ? btrfs_balance+0xe60/0xe60
       kthread+0x16b/0x190
       ? set_kthread_struct+0x40/0x40
       ret_from_fork+0x22/0x30
       </TASK>
    
    Normally snapshot deletion and relocation are excluded from running at
    the same time by the fs_info->cleaner_mutex.  However if we had a
    pending balance waiting to get the ->cleaner_mutex, and a snapshot
    deletion was running, and then the box crashed, we would come up in a
    state where we have a half deleted snapshot.
    
    Again, in the normal case the snapshot deletion needs to complete before
    relocation can start, but in this case relocation could very well start
    before the snapshot deletion completes, as we simply add the root to the
    dead roots list and wait for the next time the cleaner runs to clean up
    the snapshot.
    
    Fix this by setting a bit on the fs_info if we have any DEAD_ROOT's that
    had a pending drop_progress key.  If they do then we know we were in the
    middle of the drop operation and set a flag on the fs_info.  Then
    balance can wait until this flag is cleared to start up again.
    
    If there are DEAD_ROOT's that don't have a drop_progress set then we're
    safe to start balance right away as we'll be properly protected by the
    cleaner_mutex.
    
    CC: stable@vger.kernel.org # 5.10+
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a6ab66eb8541d61b0a11d70980f07b4c2dfeddc5
Author: Su Yue <l@damenly.su>
Date:   Tue Feb 22 16:42:07 2022 +0800

    btrfs: tree-checker: use u64 for item data end to avoid overflow
    
    User reported there is an array-index-out-of-bounds access while
    mounting the crafted image:
    
      [350.411942 ] loop0: detected capacity change from 0 to 262144
      [350.427058 ] BTRFS: device fsid a62e00e8-e94e-4200-8217-12444de93c2e devid 1 transid 8 /dev/loop0 scanned by systemd-udevd (1044)
      [350.428564 ] BTRFS info (device loop0): disk space caching is enabled
      [350.428568 ] BTRFS info (device loop0): has skinny extents
      [350.429589 ]
      [350.429619 ] UBSAN: array-index-out-of-bounds in fs/btrfs/struct-funcs.c:161:1
      [350.429636 ] index 1048096 is out of range for type 'page *[16]'
      [350.429650 ] CPU: 0 PID: 9 Comm: kworker/u8:1 Not tainted 5.16.0-rc4
      [350.429652 ] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
      [350.429653 ] Workqueue: btrfs-endio-meta btrfs_work_helper [btrfs]
      [350.429772 ] Call Trace:
      [350.429774 ]  <TASK>
      [350.429776 ]  dump_stack_lvl+0x47/0x5c
      [350.429780 ]  ubsan_epilogue+0x5/0x50
      [350.429786 ]  __ubsan_handle_out_of_bounds+0x66/0x70
      [350.429791 ]  btrfs_get_16+0xfd/0x120 [btrfs]
      [350.429832 ]  check_leaf+0x754/0x1a40 [btrfs]
      [350.429874 ]  ? filemap_read+0x34a/0x390
      [350.429878 ]  ? load_balance+0x175/0xfc0
      [350.429881 ]  validate_extent_buffer+0x244/0x310 [btrfs]
      [350.429911 ]  btrfs_validate_metadata_buffer+0xf8/0x100 [btrfs]
      [350.429935 ]  end_bio_extent_readpage+0x3af/0x850 [btrfs]
      [350.429969 ]  ? newidle_balance+0x259/0x480
      [350.429972 ]  end_workqueue_fn+0x29/0x40 [btrfs]
      [350.429995 ]  btrfs_work_helper+0x71/0x330 [btrfs]
      [350.430030 ]  ? __schedule+0x2fb/0xa40
      [350.430033 ]  process_one_work+0x1f6/0x400
      [350.430035 ]  ? process_one_work+0x400/0x400
      [350.430036 ]  worker_thread+0x2d/0x3d0
      [350.430037 ]  ? process_one_work+0x400/0x400
      [350.430038 ]  kthread+0x165/0x190
      [350.430041 ]  ? set_kthread_struct+0x40/0x40
      [350.430043 ]  ret_from_fork+0x1f/0x30
      [350.430047 ]  </TASK>
      [350.430047 ]
      [350.430077 ] BTRFS warning (device loop0): bad eb member start: ptr 0xffe20f4e start 20975616 member offset 4293005178 size 2
    
    btrfs check reports:
      corrupt leaf: root=3 block=20975616 physical=20975616 slot=1, unexpected
      item end, have 4294971193 expect 3897
    
    The first slot item offset is 4293005033 and the size is 1966160.
    In check_leaf, we use btrfs_item_end() to check item boundary versus
    extent_buffer data size. However, return type of btrfs_item_end() is u32.
    (u32)(4293005033 + 1966160) == 3897, overflow happens and the result 3897
    equals to leaf data size reasonably.
    
    Fix it by use u64 variable to store item data end in check_leaf() to
    avoid u32 overflow.
    
    This commit does solve the invalid memory access showed by the stack
    trace.  However, its metadata profile is DUP and another copy of the
    leaf is fine.  So the image can be mounted successfully. But when umount
    is called, the ASSERT btrfs_mark_buffer_dirty() will be triggered
    because the only node in extent tree has 0 item and invalid owner. It's
    solved by another commit
    "btrfs: check extent buffer owner against the owner rootid".
    
    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215299
    Reported-by: Wenqing Liu <wenqingliu0120@gmail.com>
    CC: stable@vger.kernel.org # 4.19+
    Signed-off-by: Su Yue <l@damenly.su>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a50e1fcbc9b85fd4e95b89a75c0884cb032a3e06
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Feb 18 10:17:39 2022 -0500

    btrfs: do not WARN_ON() if we have PageError set
    
    Whenever we do any extent buffer operations we call
    assert_eb_page_uptodate() to complain loudly if we're operating on an
    non-uptodate page.  Our overnight tests caught this warning earlier this
    week
    
      WARNING: CPU: 1 PID: 553508 at fs/btrfs/extent_io.c:6849 assert_eb_page_uptodate+0x3f/0x50
      CPU: 1 PID: 553508 Comm: kworker/u4:13 Tainted: G        W         5.17.0-rc3+ #564
      Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014
      Workqueue: btrfs-cache btrfs_work_helper
      RIP: 0010:assert_eb_page_uptodate+0x3f/0x50
      RSP: 0018:ffffa961440a7c68 EFLAGS: 00010246
      RAX: 0017ffffc0002112 RBX: ffffe6e74453f9c0 RCX: 0000000000001000
      RDX: ffffe6e74467c887 RSI: ffffe6e74453f9c0 RDI: ffff8d4c5efc2fc0
      RBP: 0000000000000d56 R08: ffff8d4d4a224000 R09: 0000000000000000
      R10: 00015817fa9d1ef0 R11: 000000000000000c R12: 00000000000007b1
      R13: ffff8d4c5efc2fc0 R14: 0000000001500000 R15: 0000000001cb1000
      FS:  0000000000000000(0000) GS:ffff8d4dbbd00000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 00007ff31d3448d8 CR3: 0000000118be8004 CR4: 0000000000370ee0
      Call Trace:
    
       extent_buffer_test_bit+0x3f/0x70
       free_space_test_bit+0xa6/0xc0
       load_free_space_tree+0x1f6/0x470
       caching_thread+0x454/0x630
       ? rcu_read_lock_sched_held+0x12/0x60
       ? rcu_read_lock_sched_held+0x12/0x60
       ? rcu_read_lock_sched_held+0x12/0x60
       ? lock_release+0x1f0/0x2d0
       btrfs_work_helper+0xf2/0x3e0
       ? lock_release+0x1f0/0x2d0
       ? finish_task_switch.isra.0+0xf9/0x3a0
       process_one_work+0x26d/0x580
       ? process_one_work+0x580/0x580
       worker_thread+0x55/0x3b0
       ? process_one_work+0x580/0x580
       kthread+0xf0/0x120
       ? kthread_complete_and_exit+0x20/0x20
       ret_from_fork+0x1f/0x30
    
    This was partially fixed by c2e39305299f01 ("btrfs: clear extent buffer
    uptodate when we fail to write it"), however all that fix did was keep
    us from finding extent buffers after a failed writeout.  It didn't keep
    us from continuing to use a buffer that we already had found.
    
    In this case we're searching the commit root to cache the block group,
    so we can start committing the transaction and switch the commit root
    and then start writing.  After the switch we can look up an extent
    buffer that hasn't been written yet and start processing that block
    group.  Then we fail to write that block out and clear Uptodate on the
    page, and then we start spewing these errors.
    
    Normally we're protected by the tree lock to a certain degree here.  If
    we read a block we have that block read locked, and we block the writer
    from locking the block before we submit it for the write.  However this
    isn't necessarily fool proof because the read could happen before we do
    the submit_bio and after we locked and unlocked the extent buffer.
    
    Also in this particular case we have path->skip_locking set, so that
    won't save us here.  We'll simply get a block that was valid when we
    read it, but became invalid while we were using it.
    
    What we really want is to catch the case where we've "read" a block but
    it's not marked Uptodate.  On read we ClearPageError(), so if we're
    !Uptodate and !Error we know we didn't do the right thing for reading
    the page.
    
    Fix this by checking !Uptodate && !Error, this way we will not complain
    if our buffer gets invalidated while we're using it, and we'll maintain
    the spirit of the check which is to make sure we have a fully in-cache
    block while we're messing with it.
    
    CC: stable@vger.kernel.org # 5.4+
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d99478874355d3a7b9d86dfb5d7590d5b1754b1f
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Feb 17 12:12:02 2022 +0000

    btrfs: fix lost prealloc extents beyond eof after full fsync
    
    When doing a full fsync, if we have prealloc extents beyond (or at) eof,
    and the leaves that contain them were not modified in the current
    transaction, we end up not logging them. This results in losing those
    extents when we replay the log after a power failure, since the inode is
    truncated to the current value of the logged i_size.
    
    Just like for the fast fsync path, we need to always log all prealloc
    extents starting at or beyond i_size. The fast fsync case was fixed in
    commit 471d557afed155 ("Btrfs: fix loss of prealloc extents past i_size
    after fsync log replay") but it missed the full fsync path. The problem
    exists since the very early days, when the log tree was added by
    commit e02119d5a7b439 ("Btrfs: Add a write ahead tree log to optimize
    synchronous operations").
    
    Example reproducer:
    
      $ mkfs.btrfs -f /dev/sdc
      $ mount /dev/sdc /mnt
    
      # Create our test file with many file extent items, so that they span
      # several leaves of metadata, even if the node/page size is 64K. Use
      # direct IO and not fsync/O_SYNC because it's both faster and it avoids
      # clearing the full sync flag from the inode - we want the fsync below
      # to trigger the slow full sync code path.
      $ xfs_io -f -d -c "pwrite -b 4K 0 16M" /mnt/foo
    
      # Now add two preallocated extents to our file without extending the
      # file's size. One right at i_size, and another further beyond, leaving
      # a gap between the two prealloc extents.
      $ xfs_io -c "falloc -k 16M 1M" /mnt/foo
      $ xfs_io -c "falloc -k 20M 1M" /mnt/foo
    
      # Make sure everything is durably persisted and the transaction is
      # committed. This makes all created extents to have a generation lower
      # than the generation of the transaction used by the next write and
      # fsync.
      sync
    
      # Now overwrite only the first extent, which will result in modifying
      # only the first leaf of metadata for our inode. Then fsync it. This
      # fsync will use the slow code path (inode full sync bit is set) because
      # it's the first fsync since the inode was created/loaded.
      $ xfs_io -c "pwrite 0 4K" -c "fsync" /mnt/foo
    
      # Extent list before power failure.
      $ xfs_io -c "fiemap -v" /mnt/foo
      /mnt/foo:
       EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
         0: [0..7]:          2178048..2178055     8   0x0
         1: [8..16383]:      26632..43007     16376   0x0
         2: [16384..32767]:  2156544..2172927 16384   0x0
         3: [32768..34815]:  2172928..2174975  2048 0x800
         4: [34816..40959]:  hole              6144
         5: [40960..43007]:  2174976..2177023  2048 0x801
    
      <power fail>
    
      # Mount fs again, trigger log replay.
      $ mount /dev/sdc /mnt
    
      # Extent list after power failure and log replay.
      $ xfs_io -c "fiemap -v" /mnt/foo
      /mnt/foo:
       EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
         0: [0..7]:          2178048..2178055     8   0x0
         1: [8..16383]:      26632..43007     16376   0x0
         2: [16384..32767]:  2156544..2172927 16384   0x1
    
      # The prealloc extents at file offsets 16M and 20M are missing.
    
    So fix this by calling btrfs_log_prealloc_extents() when we are doing a
    full fsync, so that we always log all prealloc extents beyond eof.
    
    A test case for fstests will follow soon.
    
    CC: stable@vger.kernel.org # 4.19+
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c992fa1fd52380d0c4ced7b07479e877311ae645
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Feb 18 10:13:00 2022 +0800

    btrfs: subpage: fix a wrong check on subpage->writers
    
    [BUG]
    When looping btrfs/074 with 64K page size and 4K sectorsize, there is a
    low chance (1/50~1/100) to crash with the following ASSERT() triggered
    in btrfs_subpage_start_writer():
    
            ret = atomic_add_return(nbits, &subpage->writers);
            ASSERT(ret == nbits); <<< This one <<<
    
    [CAUSE]
    With more debugging output on the parameters of
    btrfs_subpage_start_writer(), it shows a very concerning error:
    
      ret=29 nbits=13 start=393216 len=53248
    
    For @nbits it's correct, but @ret which is the returned value from
    atomic_add_return(), it's not only larger than nbits, but also larger
    than max sectors per page value (for 64K page size and 4K sector size,
    it's 16).
    
    This indicates that some call sites are not properly decreasing the value.
    
    And that's exactly the case, in btrfs_page_unlock_writer(), due to the
    fact that we can have page locked either by lock_page() or
    process_one_page(), we have to check if the subpage has any writer.
    
    If no writers, it's locked by lock_page() and we only need to unlock it.
    
    But unfortunately the check for the writers are completely opposite:
    
            if (atomic_read(&subpage->writers))
                    /* No writers, locked by plain lock_page() */
                    return unlock_page(page);
    
    We directly unlock the page if it has writers, which is the completely
    opposite what we want.
    
    Thankfully the affected call site is only limited to
    extent_write_locked_range(), so it's mostly affecting compressed write.
    
    [FIX]
    Just fix the wrong check condition to fix the bug.
    
    Fixes: e55a0de18572 ("btrfs: rework page locking in __extent_writepage()")
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 342e7c6ea58200e45bcaa9bdd8402a5531c4777e
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Mar 2 11:16:37 2022 +0100

    staging: rtl8723bs: Improve the comment explaining the locking rules
    
    rtw_mlme.h has a comment which briefly describes the locking rules for
    the rtl8723bs driver, improve this to also mention the locking order
    of xmit_priv.lock vs the lock(s) embedded in the various queues.
    
    Cc: Fabio Aiuto <fabioaiuto83@gmail.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220302101637.26542-2-hdegoede@redhat.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 8f4347081be32e67b0873827e0138ab0fdaaf450
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Mar 2 11:16:36 2022 +0100

    staging: rtl8723bs: Fix access-point mode deadlock
    
    Commit 54659ca026e5 ("staging: rtl8723bs: remove possible deadlock when
    disconnect (v2)") split the locking of pxmitpriv->lock vs sleep_q/lock
    into 2 locks in attempt to fix a lockdep reported issue with the locking
    order of the sta_hash_lock vs pxmitpriv->lock.
    
    But in the end this turned out to not fully solve the sta_hash_lock issue
    so commit a7ac783c338b ("staging: rtl8723bs: remove a second possible
    deadlock") was added to fix this in another way.
    
    The original fix was kept as it was still seen as a good thing to have,
    but now it turns out that it creates a deadlock in access-point mode:
    
    [Feb20 23:47] ======================================================
    [  +0.074085] WARNING: possible circular locking dependency detected
    [  +0.074077] 5.16.0-1-amd64 #1 Tainted: G         C  E
    [  +0.064710] ------------------------------------------------------
    [  +0.074075] ksoftirqd/3/29 is trying to acquire lock:
    [  +0.060542] ffffb8b30062ab00 (&pxmitpriv->lock){+.-.}-{2:2}, at: rtw_xmit_classifier+0x8a/0x140 [r8723bs]
    [  +0.114921]
                  but task is already holding lock:
    [  +0.069908] ffffb8b3007ab704 (&psta->sleep_q.lock){+.-.}-{2:2}, at: wakeup_sta_to_xmit+0x3b/0x300 [r8723bs]
    [  +0.116976]
                  which lock already depends on the new lock.
    
    [  +0.098037]
                  the existing dependency chain (in reverse order) is:
    [  +0.089704]
                  -> #1 (&psta->sleep_q.lock){+.-.}-{2:2}:
    [  +0.077232]        _raw_spin_lock_bh+0x34/0x40
    [  +0.053261]        xmitframe_enqueue_for_sleeping_sta+0xc1/0x2f0 [r8723bs]
    [  +0.082572]        rtw_xmit+0x58b/0x940 [r8723bs]
    [  +0.056528]        _rtw_xmit_entry+0xba/0x350 [r8723bs]
    [  +0.062755]        dev_hard_start_xmit+0xf1/0x320
    [  +0.056381]        sch_direct_xmit+0x9e/0x360
    [  +0.052212]        __dev_queue_xmit+0xce4/0x1080
    [  +0.055334]        ip6_finish_output2+0x18f/0x6e0
    [  +0.056378]        ndisc_send_skb+0x2c8/0x870
    [  +0.052209]        ndisc_send_ns+0xd3/0x210
    [  +0.050130]        addrconf_dad_work+0x3df/0x5a0
    [  +0.055338]        process_one_work+0x274/0x5a0
    [  +0.054296]        worker_thread+0x52/0x3b0
    [  +0.050124]        kthread+0x16c/0x1a0
    [  +0.044925]        ret_from_fork+0x1f/0x30
    [  +0.049092]
                  -> #0 (&pxmitpriv->lock){+.-.}-{2:2}:
    [  +0.074101]        __lock_acquire+0x10f5/0x1d80
    [  +0.054298]        lock_acquire+0xd7/0x300
    [  +0.049088]        _raw_spin_lock_bh+0x34/0x40
    [  +0.053248]        rtw_xmit_classifier+0x8a/0x140 [r8723bs]
    [  +0.066949]        rtw_xmitframe_enqueue+0xa/0x20 [r8723bs]
    [  +0.066946]        rtl8723bs_hal_xmitframe_enqueue+0x14/0x50 [r8723bs]
    [  +0.078386]        wakeup_sta_to_xmit+0xa6/0x300 [r8723bs]
    [  +0.065903]        rtw_recv_entry+0xe36/0x1160 [r8723bs]
    [  +0.063809]        rtl8723bs_recv_tasklet+0x349/0x6c0 [r8723bs]
    [  +0.071093]        tasklet_action_common.constprop.0+0xe5/0x110
    [  +0.070966]        __do_softirq+0x16f/0x50a
    [  +0.050134]        __irq_exit_rcu+0xeb/0x140
    [  +0.051172]        irq_exit_rcu+0xa/0x20
    [  +0.047006]        common_interrupt+0xb8/0xd0
    [  +0.052214]        asm_common_interrupt+0x1e/0x40
    [  +0.056381]        finish_task_switch.isra.0+0x100/0x3a0
    [  +0.063670]        __schedule+0x3ad/0xd20
    [  +0.048047]        schedule+0x4e/0xc0
    [  +0.043880]        smpboot_thread_fn+0xc4/0x220
    [  +0.054298]        kthread+0x16c/0x1a0
    [  +0.044922]        ret_from_fork+0x1f/0x30
    [  +0.049088]
                  other info that might help us debug this:
    
    [  +0.095950]  Possible unsafe locking scenario:
    
    [  +0.070952]        CPU0                    CPU1
    [  +0.054282]        ----                    ----
    [  +0.054285]   lock(&psta->sleep_q.lock);
    [  +0.047004]                                lock(&pxmitpriv->lock);
    [  +0.074082]                                lock(&psta->sleep_q.lock);
    [  +0.077209]   lock(&pxmitpriv->lock);
    [  +0.043873]
                   *** DEADLOCK ***
    
    [  +0.070950] 1 lock held by ksoftirqd/3/29:
    [  +0.049082]  #0: ffffb8b3007ab704 (&psta->sleep_q.lock){+.-.}-{2:2}, at: wakeup_sta_to_xmit+0x3b/0x300 [r8723bs]
    
    Analysis shows that in hindsight the splitting of the lock was not
    a good idea, so revert this to fix the access-point mode deadlock.
    
    Note this is a straight-forward revert done with git revert, the commented
    out "/* spin_lock_bh(&psta_bmc->sleep_q.lock); */" lines were part of the
    code before the reverted changes.
    
    Fixes: 54659ca026e5 ("staging: rtl8723bs: remove possible deadlock when disconnect (v2)")
    Cc: stable <stable@vger.kernel.org>
    Cc: Fabio Aiuto <fabioaiuto83@gmail.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215542
    Link: https://lore.kernel.org/r/20220302101637.26542-1-hdegoede@redhat.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 22ba5e99b96f1c0dbdfa4f4e1d9751b4c8348541
Author: Gao Xiang <hsiangkao@linux.alibaba.com>
Date:   Tue Feb 22 11:31:18 2022 +0800

    erofs: fix ztailpacking on > 4GiB filesystems
    
    z_idataoff here is an absolute physical offset, so it should use
    erofs_off_t (64 bits at least). Otherwise, it'll get trimmed and
    cause the decompresion failure.
    
    Link: https://lore.kernel.org/r/20220222033118.20540-1-hsiangkao@linux.alibaba.com
    Fixes: ab92184ff8f1 ("erofs: add on-disk compressed tail-packing inline support")
    Reviewed-by: Yue Hu <huyue2@yulong.com>
    Reviewed-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

commit 0aa6b294b312d9710804679abd2c0c8ca52cc2bc
Author: Zhen Ni <nizhen@uniontech.com>
Date:   Wed Mar 2 15:42:41 2022 +0800

    ALSA: intel_hdmi: Fix reference to PCM buffer address
    
    PCM buffers might be allocated dynamically when the buffer
    preallocation failed or a larger buffer is requested, and it's not
    guaranteed that substream->dma_buffer points to the actually used
    buffer.  The driver needs to refer to substream->runtime->dma_addr
    instead for the buffer address.
    
    Signed-off-by: Zhen Ni <nizhen@uniontech.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220302074241.30469-1-nizhen@uniontech.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 6c1f41afc1dbe59d9d3c8bb0d80b749c119aa334
Author: Sven Eckelmann <sven@narfation.org>
Date:   Sun Feb 27 23:23:49 2022 +0100

    batman-adv: Don't expect inter-netns unique iflink indices
    
    The ifindex doesn't have to be unique for multiple network namespaces on
    the same machine.
    
      $ ip netns add test1
      $ ip -net test1 link add dummy1 type dummy
      $ ip netns add test2
      $ ip -net test2 link add dummy2 type dummy
    
      $ ip -net test1 link show dev dummy1
      6: dummy1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
          link/ether 96:81:55:1e:dd:85 brd ff:ff:ff:ff:ff:ff
      $ ip -net test2 link show dev dummy2
      6: dummy2: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
          link/ether 5a:3c:af:35:07:c3 brd ff:ff:ff:ff:ff:ff
    
    But the batman-adv code to walk through the various layers of virtual
    interfaces uses this assumption because dev_get_iflink handles it
    internally and doesn't return the actual netns of the iflink. And
    dev_get_iflink only documents the situation where ifindex == iflink for
    physical devices.
    
    But only checking for dev->netdev_ops->ndo_get_iflink is also not an option
    because ipoib_get_iflink implements it even when it sometimes returns an
    iflink != ifindex and sometimes iflink == ifindex. The caller must
    therefore make sure itself to check both netns and iflink + ifindex for
    equality. Only when they are equal, a "physical" interface was detected
    which should stop the traversal. On the other hand, vxcan_get_iflink can
    also return 0 in case there was currently no valid peer. In this case, it
    is still necessary to stop.
    
    Fixes: b7eddd0b3950 ("batman-adv: prevent using any virtual device created on batman-adv as hard-interface")
    Fixes: 5ed4a460a1d3 ("batman-adv: additional checks for virtual interfaces on top of WiFi")
    Reported-by: Sabrina Dubroca <sd@queasysnail.net>
    Signed-off-by: Sven Eckelmann <sven@narfation.org>
    Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>

commit 6116ba09423f7d140f0460be6a1644dceaad00da
Author: Sven Eckelmann <sven@narfation.org>
Date:   Mon Feb 28 00:01:24 2022 +0100

    batman-adv: Request iflink once in batadv_get_real_netdevice
    
    There is no need to call dev_get_iflink multiple times for the same
    net_device in batadv_get_real_netdevice. And since some of the
    ndo_get_iflink callbacks are dynamic (for example via RCUs like in
    vxcan_get_iflink), it could easily happen that the returned values are not
    stable. The pre-checks before __dev_get_by_index are then of course bogus.
    
    Fixes: 5ed4a460a1d3 ("batman-adv: additional checks for virtual interfaces on top of WiFi")
    Signed-off-by: Sven Eckelmann <sven@narfation.org>
    Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>

commit 690bb6fb64f5dc7437317153902573ecad67593d
Author: Sven Eckelmann <sven@narfation.org>
Date:   Mon Feb 28 00:01:24 2022 +0100

    batman-adv: Request iflink once in batadv-on-batadv check
    
    There is no need to call dev_get_iflink multiple times for the same
    net_device in batadv_is_on_batman_iface. And since some of the
    .ndo_get_iflink callbacks are dynamic (for example via RCUs like in
    vxcan_get_iflink), it could easily happen that the returned values are not
    stable. The pre-checks before __dev_get_by_index are then of course bogus.
    
    Fixes: b7eddd0b3950 ("batman-adv: prevent using any virtual device created on batman-adv as hard-interface")
    Signed-off-by: Sven Eckelmann <sven@narfation.org>
    Signed-off-by: Simon Wunderlich <sw@simonwunderlich.de>

commit 04b7762e37c95d9b965d16bb0e18dbd1fa2e2861
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Feb 28 23:39:50 2022 -0800

    Input: elan_i2c - fix regulator enable count imbalance after suspend/resume
    
    Before these changes elan_suspend() would only disable the regulator
    when device_may_wakeup() returns false; whereas elan_resume() would
    unconditionally enable it, leading to an enable count imbalance when
    device_may_wakeup() returns true.
    
    This triggers the "WARN_ON(regulator->enable_count)" in regulator_put()
    when the elan_i2c driver gets unbound, this happens e.g. with the
    hot-plugable dock with Elan I2C touchpad for the Asus TF103C 2-in-1.
    
    Fix this by making the regulator_enable() call also be conditional
    on device_may_wakeup() returning false.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220131135436.29638-2-hdegoede@redhat.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 81a36d8ce554b82b0a08e2b95d0bd44fcbff339b
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Feb 28 23:39:38 2022 -0800

    Input: elan_i2c - move regulator_[en|dis]able() out of elan_[en|dis]able_power()
    
    elan_disable_power() is called conditionally on suspend, where as
    elan_enable_power() is always called on resume. This leads to
    an imbalance in the regulator's enable count.
    
    Move the regulator_[en|dis]able() calls out of elan_[en|dis]able_power()
    in preparation of fixing this.
    
    No functional changes intended.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220131135436.29638-1-hdegoede@redhat.com
    [dtor: consolidate elan_[en|dis]able() into elan_set_power()]
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 1d1898f65616c4601208963c3376c1d828cbf2c7
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Tue Mar 1 22:29:04 2022 -0500

    tracing/histogram: Fix sorting on old "cpu" value
    
    When trying to add a histogram against an event with the "cpu" field, it
    was impossible due to "cpu" being a keyword to key off of the running CPU.
    So to fix this, it was changed to "common_cpu" to match the other generic
    fields (like "common_pid"). But since some scripts used "cpu" for keying
    off of the CPU (for events that did not have "cpu" as a field, which is
    most of them), a backward compatibility trick was added such that if "cpu"
    was used as a key, and the event did not have "cpu" as a field name, then
    it would fallback and switch over to "common_cpu".
    
    This fix has a couple of subtle bugs. One was that when switching over to
    "common_cpu", it did not change the field name, it just set a flag. But
    the code still found a "cpu" field. The "cpu" field is used for filtering
    and is returned when the event does not have a "cpu" field.
    
    This was found by:
    
      # cd /sys/kernel/tracing
      # echo hist:key=cpu,pid:sort=cpu > events/sched/sched_wakeup/trigger
      # cat events/sched/sched_wakeup/hist
    
    Which showed the histogram unsorted:
    
    { cpu:         19, pid:       1175 } hitcount:          1
    { cpu:          6, pid:        239 } hitcount:          2
    { cpu:         23, pid:       1186 } hitcount:         14
    { cpu:         12, pid:        249 } hitcount:          2
    { cpu:          3, pid:        994 } hitcount:          5
    
    Instead of hard coding the "cpu" checks, take advantage of the fact that
    trace_event_field_field() returns a special field for "cpu" and "CPU" if
    the event does not have "cpu" as a field. This special field has the
    "filter_type" of "FILTER_CPU". Check that to test if the returned field is
    of the CPU type instead of doing the string compare.
    
    Also, fix the sorting bug by testing for the hist_field flag of
    HIST_FIELD_FL_CPU when setting up the sort routine. Otherwise it will use
    the special CPU field to know what compare routine to use, and since that
    special field does not have a size, it returns tracing_map_cmp_none.
    
    Cc: stable@vger.kernel.org
    Fixes: 1e3bac71c505 ("tracing/histogram: Rename "cpu" to "common_cpu"")
    Reported-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 0b0e2ff10356e7e2ffd66ecdd6eee69a2f03449b
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 28 16:17:15 2022 +0200

    net: dsa: restore error path of dsa_tree_change_tag_proto
    
    When the DSA_NOTIFIER_TAG_PROTO returns an error, the user space process
    which initiated the protocol change exits the kernel processing while
    still holding the rtnl_mutex. So any other process attempting to lock
    the rtnl_mutex would deadlock after such event.
    
    The error handling of DSA_NOTIFIER_TAG_PROTO was inadvertently changed
    by the blamed commit, introducing this regression. We must still call
    rtnl_unlock(), and we must still call DSA_NOTIFIER_TAG_PROTO for the old
    protocol. The latter is due to the limiting design of notifier chains
    for cross-chip operations, which don't have a built-in error recovery
    mechanism - we should look into using notifier_call_chain_robust for that.
    
    Fixes: dc452a471dba ("net: dsa: introduce tagger-owned storage for private and shared data")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220228141715.146485-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2e77551c61286bac56ebf337b1ac2dd419952c8d
Merge: 4761df52f1549 275f3f6487024
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Mar 1 17:16:46 2022 -0800

    Merge tag 'for-net-2022-03-01' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth
    
    Luiz Augusto von Dentz says:
    
    ====================
    bluetooth pull request for net:
    
     - Fix regression with scanning not working in some systems.
    
    * tag 'for-net-2022-03-01' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth:
      Bluetooth: Fix not checking MGMT cmd pending queue
    ====================
    
    Link: https://lore.kernel.org/r/20220302004330.125536-1-luiz.dentz@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 275f3f64870245b06188f24bdf917e55a813d294
Author: Brian Gix <brian.gix@intel.com>
Date:   Tue Mar 1 14:34:57 2022 -0800

    Bluetooth: Fix not checking MGMT cmd pending queue
    
    A number of places in the MGMT handlers we examine the command queue for
    other commands (in progress but not yet complete) that will interact
    with the process being performed. However, not all commands go into the
    queue if one of:
    
    1. There is no negative side effect of consecutive or redundent commands
    2. The command is entirely perform "inline".
    
    This change examines each "pending command" check, and if it is not
    needed, deletes the check. Of the remaining pending command checks, we
    make sure that the command is in the pending queue by using the
    mgmt_pending_add/mgmt_pending_remove pair rather than the
    mgmt_pending_new/mgmt_pending_free pair.
    
    Link: https://lore.kernel.org/linux-bluetooth/f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com/T/
    Tested-by: Maxim Levitsky <mlevitsk@redhat.com>
    Signed-off-by: Brian Gix <brian.gix@intel.com>
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

commit 4761df52f1549cc8c5ffcad0b2095fffe2c5435d
Merge: b8d06ce712e37 db6140e5e35a4
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Mar 1 15:13:46 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    1) Use kfree_rcu(ptr, rcu) variant, using kfree_rcu(ptr) was not
       intentional. From Eric Dumazet.
    
    2) Use-after-free in netfilter hook core, from Eric Dumazet.
    
    3) Missing rcu read lock side for netfilter egress hook,
       from Florian Westphal.
    
    4) nf_queue assume state->sk is full socket while it might not be.
       Invoke sock_gen_put(), from Florian Westphal.
    
    5) Add selftest to exercise the reported KASAN splat in 4)
    
    6) Fix possible use-after-free in nf_queue in case sk_refcnt is 0.
       Also from Florian.
    
    7) Use input interface index only for hardware offload, not for
       the software plane. This breaks tc ct action. Patch from Paul Blakey.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf:
      net/sched: act_ct: Fix flow table lookup failure with no originating ifindex
      netfilter: nf_queue: handle socket prefetch
      netfilter: nf_queue: fix possible use-after-free
      selftests: netfilter: add nfqueue TCP_NEW_SYN_RECV socket race test
      netfilter: nf_queue: don't assume sk is full socket
      netfilter: egress: silence egress hook lockdep splats
      netfilter: fix use-after-free in __nf_register_net_hook()
      netfilter: nf_tables: prefer kfree_rcu(ptr, rcu) variant
    ====================
    
    Link: https://lore.kernel.org/r/20220301215337.378405-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit fc7f750dc9d102c1ed7bbe4591f991e770c99033
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Mon Feb 28 10:43:31 2022 +0300

    staging: gdm724x: fix use after free in gdm_lte_rx()
    
    The netif_rx_ni() function frees the skb so we can't dereference it to
    save the skb->len.
    
    Fixes: 61e121047645 ("staging: gdm7240: adding LTE USB driver")
    Cc: stable <stable@vger.kernel.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220228074331.GA13685@kili
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a0e897d1b36793fe0ab899f2fe93dff25c82f418
Author: Pali Rohár <pali@kernel.org>
Date:   Mon Jan 17 19:20:06 2022 +0100

    arm64: dts: armada-3720-turris-mox: Add missing ethernet0 alias
    
    U-Boot uses ethernet* aliases for setting MAC addresses. Therefore define
    also alias for ethernet0.
    
    Fixes: 7109d817db2e ("arm64: dts: marvell: add DTS for Turris Mox")
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit db6140e5e35a48405e669353bd54042c1d4c3841
Author: Paul Blakey <paulb@nvidia.com>
Date:   Mon Feb 28 11:23:49 2022 +0200

    net/sched: act_ct: Fix flow table lookup failure with no originating ifindex
    
    After cited commit optimizted hw insertion, flow table entries are
    populated with ifindex information which was intended to only be used
    for HW offload. This tuple ifindex is hashed in the flow table key, so
    it must be filled for lookup to be successful. But tuple ifindex is only
    relevant for the netfilter flowtables (nft), so it's not filled in
    act_ct flow table lookup, resulting in lookup failure, and no SW
    offload and no offload teardown for TCP connection FIN/RST packets.
    
    To fix this, add new tc ifindex field to tuple, which will
    only be used for offloading, not for lookup, as it will not be
    part of the tuple hash.
    
    Fixes: 9795ded7f924 ("net/sched: act_ct: Fill offloading tuple iifidx")
    Signed-off-by: Paul Blakey <paulb@nvidia.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit fb184c4af9b9f4563e7a126219389986a71d5b5b
Merge: 575115360652e ece32a75f0034
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 1 12:01:18 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "The bigger part of the change is a revert for x86 hosts. Here the
      second patch was supposed to fix the first, but in reality it was just
      as broken, so both have to go.
    
      x86 host:
    
       - Revert incorrect assumption that cr3 changes come with preempt
         notifier callbacks (they don't when static branches are changed,
         for example)
    
      ARM host:
    
       - Correctly synchronise PMR and co on PSCI CPU_SUSPEND
    
       - Skip tests that depend on GICv3 when the HW isn't available"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      KVM: selftests: aarch64: Skip tests if we can't create a vgic-v3
      Revert "KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()"
      Revert "KVM: VMX: Save HOST_CR3 in vmx_set_host_fs_gs()"
      KVM: arm64: Don't miss pending interrupts for suspended vCPU

commit c194dad21025dfd043210912653baab823bdff67
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Thu Feb 24 22:03:29 2022 +0100

    s390/extable: fix exception table sorting
    
    s390 has a swap_ex_entry_fixup function, however it is not being used
    since common code expects a swap_ex_entry_fixup define. If it is not
    defined the default implementation will be used. So fix this by adding
    a proper define.
    However also the implementation of the function must be fixed, since a
    NULL value for handler has a special meaning and must not be adjusted.
    
    Luckily all of this doesn't fix a real bug currently: the main extable
    is correctly sorted during build time, and for runtime sorting there
    is currently no case where the handler field is not NULL.
    
    Fixes: 05a68e892e89 ("s390/kernel: expand exception table logic to allow new handling options")
    Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Reviewed-by: Alexander Gordeev <agordeev@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 1389f17937a03fe4ec71b094e1aa6530a901963e
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Tue Feb 22 14:53:47 2022 +0100

    s390/ftrace: fix arch_ftrace_get_regs implementation
    
    arch_ftrace_get_regs is supposed to return a struct pt_regs pointer
    only if the pt_regs structure contains all register contents, which
    means it must have been populated when created via ftrace_regs_caller.
    
    If it was populated via ftrace_caller the contents are not complete
    (the psw mask part is missing), and therefore a NULL pointer needs be
    returned.
    
    The current code incorrectly always returns a struct pt_regs pointer.
    
    Fix this by adding another pt_regs flag which indicates if the
    contents are complete, and fix arch_ftrace_get_regs accordingly.
    
    Fixes: 894979689d3a ("s390/ftrace: provide separate ftrace_caller/ftrace_regs_caller implementations")
    Reported-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Reported-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Reviewed-by: Sven Schnelle <svens@linux.ibm.com>
    Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 9fa881f7e3c74ce6626d166bca9397e5d925937f
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Wed Feb 23 13:02:59 2022 +0100

    s390/ftrace: fix ftrace_caller/ftrace_regs_caller generation
    
    ftrace_caller was used for both ftrace_caller and ftrace_regs_caller,
    which means that the target address of the hotpatch trampoline was
    never updated.
    
    With commit 894979689d3a ("s390/ftrace: provide separate
    ftrace_caller/ftrace_regs_caller implementations") a separate
    ftrace_regs_caller entry point was implemeted, however it was
    forgotten to implement the necessary changes for ftrace_modify_call
    and ftrace_make_call, where the branch target has to be modified
    accordingly.
    
    Therefore add the missing code now.
    
    Fixes: 894979689d3a ("s390/ftrace: provide separate ftrace_caller/ftrace_regs_caller implementations")
    Reviewed-by: Sven Schnelle <svens@linux.ibm.com>
    Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 6b4b54c7ca347bcb4aa7a3cc01aa16e84ac7fbe4
Author: Alexander Egorenkov <egorenar@linux.ibm.com>
Date:   Wed Feb 9 11:25:09 2022 +0100

    s390/setup: preserve memory at OLDMEM_BASE and OLDMEM_SIZE
    
    We need to preserve the values at OLDMEM_BASE and OLDMEM_SIZE which are
    used by zgetdump in case when kdump crashes. In that case zgetdump will
    attempt to read OLDMEM_BASE and OLDMEM_SIZE in order to find out where
    the memory range [0 - OLDMEM_SIZE] belonging to the production kernel is.
    
    Fixes: f1a546947431 ("s390/setup: don't reserve memory that occupied decompressor's head")
    Cc: stable@vger.kernel.org # 5.15+
    Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com>
    Acked-by: Vasily Gorbik <gor@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 62929726ef0ec72cbbe9440c5d125d4278b99894
Author: Manasi Navare <manasi.d.navare@intel.com>
Date:   Thu Feb 24 17:30:54 2022 -0800

    drm/vrr: Set VRR capable prop only if it is attached to connector
    
    VRR capable property is not attached by default to the connector
    It is attached only if VRR is supported.
    So if the driver tries to call drm core set prop function without
    it being attached that causes NULL dereference.
    
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Cc: dri-devel@lists.freedesktop.org
    Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220225013055.9282-1-manasi.d.navare@intel.com

commit 575115360652e9920cc56a028a286ebe9bf82694
Merge: 719fce7539cd3 439a8468242b3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Mar 1 11:31:37 2022 -0800

    Merge tag 'binfmt_elf-v5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
    
    Pull binfmt_elf fix from Kees Cook:
     "This addresses a regression[1] under ia64 where some ET_EXEC binaries
      were not loading"
    
    Link: https://linux-regtracking.leemhuis.info/regzbot/regression/a3edd529-c42d-3b09-135c-7e98a15b150f@leemhuis.info/ [1]
    
    - Fix ia64 ET_EXEC loading
    
    * tag 'binfmt_elf-v5.17-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
      binfmt_elf: Avoid total_mapping_size for ET_EXEC

commit 439a8468242b313486e69b8cc3b45ddcfa898fbf
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Feb 28 10:59:12 2022 -0800

    binfmt_elf: Avoid total_mapping_size for ET_EXEC
    
    Partially revert commit 5f501d555653 ("binfmt_elf: reintroduce using
    MAP_FIXED_NOREPLACE"), which applied the ET_DYN "total_mapping_size"
    logic also to ET_EXEC.
    
    At least ia64 has ET_EXEC PT_LOAD segments that are not virtual-address
    contiguous (but _are_ file-offset contiguous). This would result in a
    giant mapping attempting to cover the entire span, including the virtual
    address range hole, and well beyond the size of the ELF file itself,
    causing the kernel to refuse to load it. For example:
    
    $ readelf -lW /usr/bin/gcc
    ...
    Program Headers:
      Type Offset   VirtAddr           PhysAddr           FileSiz  MemSiz   ...
    ...
      LOAD 0x000000 0x4000000000000000 0x4000000000000000 0x00b5a0 0x00b5a0 ...
      LOAD 0x00b5a0 0x600000000000b5a0 0x600000000000b5a0 0x0005ac 0x000710 ...
    ...
           ^^^^^^^^ ^^^^^^^^^^^^^^^^^^                    ^^^^^^^^ ^^^^^^^^
    
    File offset range     : 0x000000-0x00bb4c
                            0x00bb4c bytes
    
    Virtual address range : 0x4000000000000000-0x600000000000bcb0
                            0x200000000000bcb0 bytes
    
    Remove the total_mapping_size logic for ET_EXEC, which reduces the
    ET_EXEC MAP_FIXED_NOREPLACE coverage to only the first PT_LOAD (better
    than nothing), and retains it for ET_DYN.
    
    Ironically, this is the reverse of the problem that originally caused
    problems with MAP_FIXED_NOREPLACE: overlapping PT_LOAD segments. Future
    work could restore full coverage if load_elf_binary() were to perform
    mappings in a separate phase from the loading (where it could resolve
    both overlaps and holes).
    
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Alexander Viro <viro@zeniv.linux.org.uk>
    Cc: linux-fsdevel@vger.kernel.org
    Cc: linux-mm@kvack.org
    Reported-by: matoro <matoro_bugzilla_kernel@matoro.tk>
    Fixes: 5f501d555653 ("binfmt_elf: reintroduce using MAP_FIXED_NOREPLACE")
    Link: https://lore.kernel.org/r/a3edd529-c42d-3b09-135c-7e98a15b150f@leemhuis.info
    Tested-by: matoro <matoro_mailinglist_kernel@matoro.tk>
    Link: https://lore.kernel.org/lkml/ce8af9c13bcea9230c7689f3c1e0e2cd@matoro.tk
    Tested-By: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
    Link: https://lore.kernel.org/lkml/49182d0d-708b-4029-da5f-bc18603440a6@physik.fu-berlin.de
    Cc: stable@vger.kernel.org
    Signed-off-by: Kees Cook <keescook@chromium.org>

commit 5838a14832d447990827d85e90afe17e6fb9c175
Author: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
Date:   Mon Feb 28 12:03:51 2022 +0100

    thermal: core: Fix TZ_GET_TRIP NULL pointer dereference
    
    Do not call get_trip_hyst() from thermal_genl_cmd_tz_get_trip() if
    the thermal zone does not define one.
    
    Fixes: 1ce50e7d408e ("thermal: core: genetlink support for events/cmd/sampling")
    Signed-off-by: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
    Cc: 5.10+ <stable@vger.kernel.org> # 5.10+
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit fe23b6bbeac40de957724b90a88d46fb336e29a9
Author: Jia-Ju Bai <baijiaju1990@gmail.com>
Date:   Thu Feb 24 19:41:10 2022 -0800

    HID: nintendo: check the return value of alloc_workqueue()
    
    The function alloc_workqueue() in nintendo_hid_probe() can fail, but
    there is no check of its return value. To fix this bug, its return value
    should be checked with new error handling code.
    
    Fixes: c4eae84feff3e ("HID: nintendo: add rumble support")
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Reviewed-by: Silvan Jegen <s.jegen@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit b8d06ce712e37c6a6e74bf1624a0f4a412cd6508
Merge: 7cf5aa32e392d a12f76345e026
Author: David S. Miller <davem@davemloft.net>
Date:   Tue Mar 1 14:45:55 2022 +0000

    Merge tag 'wireless-for-net-2022-03-01' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless
    
    johannes Berg says:
    
    ====================
    
    Some last-minute fixes:
     * rfkill
       - add missing rfill_soft_blocked() when disabled
    
     * cfg80211
       - handle a nla_memdup() failure correctly
       - fix CONFIG_CFG80211_EXTRA_REGDB_KEYDIR typo in
         Makefile
    
     * mac80211
       - fix EAPOL handling in 802.3 RX path
       - reject setting up aggregation sessions before
         connection is authorized to avoid timeouts or
         similar
       - handle some SAE authentication steps correctly
       - fix AC selection in mesh forwarding
    
     * iwlwifi
       - remove TWT support as it causes firmware crashes
         when the AP isn't behaving correctly
       - check debugfs pointer before dereferncing it
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit cc71d37fd1f11e0495b1cf580909ebea37eaa886
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Fri Feb 25 17:18:58 2022 -0800

    HID: vivaldi: fix sysfs attributes leak
    
    The driver creates the top row map sysfs attribute in input_configured()
    method; unfortunately we do not have a callback that is executed when HID
    interface is unbound, thus we are leaking these sysfs attributes, for
    example when device is disconnected.
    
    To fix it let's switch to managed version of adding sysfs attributes which
    will ensure that they are destroyed when the driver is unbound.
    
    Fixes: 14c9c014babe ("HID: add vivaldi HID driver")
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Tested-by: Stephen Boyd <swboyd@chromium.org>
    Reviewed-by: Stephen Boyd <swboyd@chromium.org>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit a12f76345e026f1b300a0d17c56f020b6949b093
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Mon Feb 21 15:55:12 2022 +0100

    cfg80211: fix CONFIG_CFG80211_EXTRA_REGDB_KEYDIR typo
    
    The kbuild change here accidentally removed not only the
    unquoting, but also the last character of the variable
    name. Fix that.
    
    Fixes: 129ab0d2d9f3 ("kbuild: do not quote string values in include/config/auto.conf")
    Reviewed-by: Masahiro Yamada <masahiroy@kernel.org>
    Link: https://lore.kernel.org/r/20220221155512.1d25895f7c5f.I50fa3d4189fcab90a2896fe8cae215035dae9508@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit ea49432d184a6a09f84461604b7711a4e9f5ec9c
Author: Daniel Palmer <daniel@0x0f.com>
Date:   Tue Mar 1 19:43:49 2022 +0900

    ARM: mstar: Select HAVE_ARM_ARCH_TIMER
    
    The mstar SoCs have an arch timer but HAVE_ARM_ARCH_TIMER wasn't
    selected. If MSC313E_TIMER isn't selected then the kernel gets
    stuck at boot because there are no timers available.
    
    Signed-off-by: Daniel Palmer <daniel@0x0f.com>
    Link: https://lore.kernel.org/r/20220301104349.3040422-1-daniel@0x0f.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 4ff2980b6bd2aa6b4ded3ce3b7c0ccfab29980af
Author: Lina Wang <lina.wang@mediatek.com>
Date:   Sat Feb 26 15:48:01 2022 +0800

    xfrm: fix tunnel model fragmentation behavior
    
    in tunnel mode, if outer interface(ipv4) is less, it is easily to let
    inner IPV6 mtu be less than 1280. If so, a Packet Too Big ICMPV6 message
    is received. When send again, packets are fragmentized with 1280, they
    are still rejected with ICMPV6(Packet Too Big) by xfrmi_xmit2().
    
    According to RFC4213 Section3.2.2:
    if (IPv4 path MTU - 20) is less than 1280
            if packet is larger than 1280 bytes
                    Send ICMPv6 "packet too big" with MTU=1280
                    Drop packet
            else
                    Encapsulate but do not set the Don't Fragment
                    flag in the IPv4 header.  The resulting IPv4
                    packet might be fragmented by the IPv4 layer
                    on the encapsulator or by some router along
                    the IPv4 path.
            endif
    else
            if packet is larger than (IPv4 path MTU - 20)
                    Send ICMPv6 "packet too big" with
                    MTU = (IPv4 path MTU - 20).
                    Drop packet.
            else
                    Encapsulate and set the Don't Fragment flag
                    in the IPv4 header.
            endif
    endif
    Packets should be fragmentized with ipv4 outer interface, so change it.
    
    After it is fragemtized with ipv4, there will be double fragmenation.
    No.48 & No.51 are ipv6 fragment packets, No.48 is double fragmentized,
    then tunneled with IPv4(No.49& No.50), which obey spec. And received peer
    cannot decrypt it rightly.
    
    48              2002::10        2002::11 1296(length) IPv6 fragment (off=0 more=y ident=0xa20da5bc nxt=50)
    49   0x0000 (0) 2002::10        2002::11 1304         IPv6 fragment (off=0 more=y ident=0x7448042c nxt=44)
    50   0x0000 (0) 2002::10        2002::11 200          ESP (SPI=0x00035000)
    51              2002::10        2002::11 180          Echo (ping) request
    52   0x56dc     2002::10        2002::11 248          IPv6 fragment (off=1232 more=n ident=0xa20da5bc nxt=50)
    
    xfrm6_noneed_fragment has fixed above issues. Finally, it acted like below:
    1   0x6206 192.168.1.138   192.168.1.1 1316 Fragmented IP protocol (proto=Encap Security Payload 50, off=0, ID=6206) [Reassembled in #2]
    2   0x6206 2002::10        2002::11    88   IPv6 fragment (off=0 more=y ident=0x1f440778 nxt=50)
    3   0x0000 2002::10        2002::11    248  ICMPv6    Echo (ping) request
    
    Signed-off-by: Lina Wang <lina.wang@mediatek.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 3b836da4081fa585cf6c392f62557496f2cb0efe
Author: Florian Westphal <fw@strlen.de>
Date:   Tue Mar 1 00:46:19 2022 +0100

    netfilter: nf_queue: handle socket prefetch
    
    In case someone combines bpf socket assign and nf_queue, then we will
    queue an skb who references a struct sock that did not have its
    reference count incremented.
    
    As we leave rcu protection, there is no guarantee that skb->sk is still
    valid.
    
    For refcount-less skb->sk case, try to increment the reference count
    and then override the destructor.
    
    In case of failure we have two choices: orphan the skb and 'delete'
    preselect or let nf_queue() drop the packet.
    
    Do the latter, it should not happen during normal operation.
    
    Fixes: cf7fbe660f2d ("bpf: Add socket assign support")
    Acked-by: Joe Stringer <joe@cilium.io>
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1
Author: Florian Westphal <fw@strlen.de>
Date:   Mon Feb 28 06:22:22 2022 +0100

    netfilter: nf_queue: fix possible use-after-free
    
    Eric Dumazet says:
      The sock_hold() side seems suspect, because there is no guarantee
      that sk_refcnt is not already 0.
    
    On failure, we cannot queue the packet and need to indicate an
    error.  The packet will be dropped by the caller.
    
    v2: split skb prefetch hunk into separate change
    
    Fixes: 271b72c7fa82c ("udp: RCU handling for Unicast packets.")
    Reported-by: Eric Dumazet <eric.dumazet@gmail.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit 2e78855d311c401083df9776aa450d32d716e83e
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Feb 25 12:01:23 2022 +0100

    selftests: netfilter: add nfqueue TCP_NEW_SYN_RECV socket race test
    
    causes:
    BUG: KASAN: slab-out-of-bounds in sk_free+0x25/0x80
    Write of size 4 at addr ffff888106df0284 by task nf-queue/1459
     sk_free+0x25/0x80
     nf_queue_entry_release_refs+0x143/0x1a0
     nf_reinject+0x233/0x770
    
    ... without 'netfilter: nf_queue: don't assume sk is full socket'.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit 747670fd9a2d1b7774030dba65ca022ba442ce71
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Feb 25 14:02:41 2022 +0100

    netfilter: nf_queue: don't assume sk is full socket
    
    There is no guarantee that state->sk refers to a full socket.
    
    If refcount transitions to 0, sock_put calls sk_free which then ends up
    with garbage fields.
    
    I'd like to thank Oleksandr Natalenko and Jiri Benc for considerable
    debug work and pointing out state->sk oddities.
    
    Fixes: ca6fb0651883 ("tcp: attach SYNACK messages to request sockets instead of listener")
    Tested-by: Oleksandr Natalenko <oleksandr@redhat.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>

commit 94d9864cc86f572f881db9b842a78e9d075493ae
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Thu Feb 24 10:39:34 2022 +0100

    mac80211: treat some SAE auth steps as final
    
    When we get anti-clogging token required (added by the commit
    mentioned below), or the other status codes added by the later
    commit 4e56cde15f7d ("mac80211: Handle special status codes in
    SAE commit") we currently just pretend (towards the internal
    state machine of authentication) that we didn't receive anything.
    
    This has the undesirable consequence of retransmitting the prior
    frame, which is not expected, because the timer is still armed.
    
    If we just disarm the timer at that point, it would result in
    the undesirable side effect of being in this state indefinitely
    if userspace crashes, or so.
    
    So to fix this, reset the timer and set a new auth_data->waiting
    in order to have no more retransmissions, but to have the data
    destroyed when the timer actually fires, which will only happen
    if userspace didn't continue (i.e. crashed or abandoned it.)
    
    Fixes: a4055e74a2ff ("mac80211: Don't destroy auth data in case of anti-clogging")
    Reported-by: Jouni Malinen <j@w1.fi>
    Link: https://lore.kernel.org/r/20220224103932.75964e1d7932.Ia487f91556f29daae734bf61f8181404642e1eec@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 6ad27f522cb3b210476daf63ce6ddb6568c0508b
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Mar 1 18:00:20 2022 +0800

    nl80211: Handle nla_memdup failures in handle_nan_filter
    
    As there's potential for failure of the nla_memdup(),
    check the return value.
    
    Fixes: a442b761b24b ("cfg80211: add add_nan_func / del_nan_func")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220301100020.3801187-1-jiasheng@iscas.ac.cn
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 5a6248c0a22352f09ea041665d3bd3e18f6f872c
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Tue Feb 22 19:06:30 2022 -0800

    iwlwifi: mvm: check debugfs_dir ptr before use
    
    When "debugfs=off" is used on the kernel command line, iwiwifi's
    mvm module uses an invalid/unchecked debugfs_dir pointer and causes
    a BUG:
    
     BUG: kernel NULL pointer dereference, address: 000000000000004f
     #PF: supervisor read access in kernel mode
     #PF: error_code(0x0000) - not-present page
     PGD 0 P4D 0
     Oops: 0000 [#1] PREEMPT SMP
     CPU: 1 PID: 503 Comm: modprobe Tainted: G        W         5.17.0-rc5 #7
     Hardware name: Dell Inc. Inspiron 15 5510/076F7Y, BIOS 2.4.1 11/05/2021
     RIP: 0010:iwl_mvm_dbgfs_register+0x692/0x700 [iwlmvm]
     Code: 69 a0 be 80 01 00 00 48 c7 c7 50 73 6a a0 e8 95 cf ee e0 48 8b 83 b0 1e 00 00 48 c7 c2 54 73 6a a0 be 64 00 00 00 48 8d 7d 8c <48> 8b 48 50 e8 15 22 07 e1 48 8b 43 28 48 8d 55 8c 48 c7 c7 5f 73
     RSP: 0018:ffffc90000a0ba68 EFLAGS: 00010246
     RAX: ffffffffffffffff RBX: ffff88817d6e3328 RCX: ffff88817d6e3328
     RDX: ffffffffa06a7354 RSI: 0000000000000064 RDI: ffffc90000a0ba6c
     RBP: ffffc90000a0bae0 R08: ffffffff824e4880 R09: ffffffffa069d620
     R10: ffffc90000a0ba00 R11: ffffffffffffffff R12: 0000000000000000
     R13: ffffc90000a0bb28 R14: ffff88817d6e3328 R15: ffff88817d6e3320
     FS:  00007f64dd92d740(0000) GS:ffff88847f640000(0000) knlGS:0000000000000000
     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
     CR2: 000000000000004f CR3: 000000016fc79001 CR4: 0000000000770ee0
     PKRU: 55555554
     Call Trace:
      <TASK>
      ? iwl_mvm_mac_setup_register+0xbdc/0xda0 [iwlmvm]
      iwl_mvm_start_post_nvm+0x71/0x100 [iwlmvm]
      iwl_op_mode_mvm_start+0xab8/0xb30 [iwlmvm]
      _iwl_op_mode_start+0x6f/0xd0 [iwlwifi]
      iwl_opmode_register+0x6a/0xe0 [iwlwifi]
      ? 0xffffffffa0231000
      iwl_mvm_init+0x35/0x1000 [iwlmvm]
      ? 0xffffffffa0231000
      do_one_initcall+0x5a/0x1b0
      ? kmem_cache_alloc+0x1e5/0x2f0
      ? do_init_module+0x1e/0x220
      do_init_module+0x48/0x220
      load_module+0x2602/0x2bc0
      ? __kernel_read+0x145/0x2e0
      ? kernel_read_file+0x229/0x290
      __do_sys_finit_module+0xc5/0x130
      ? __do_sys_finit_module+0xc5/0x130
      __x64_sys_finit_module+0x13/0x20
      do_syscall_64+0x38/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
     RIP: 0033:0x7f64dda564dd
     Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1b 29 0f 00 f7 d8 64 89 01 48
     RSP: 002b:00007ffdba393f88 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
     RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f64dda564dd
     RDX: 0000000000000000 RSI: 00005575399e2ab2 RDI: 0000000000000001
     RBP: 000055753a91c5e0 R08: 0000000000000000 R09: 0000000000000002
     R10: 0000000000000001 R11: 0000000000000246 R12: 00005575399e2ab2
     R13: 000055753a91ceb0 R14: 0000000000000000 R15: 000055753a923018
      </TASK>
     Modules linked in: btintel(+) btmtk bluetooth vfat snd_hda_codec_hdmi fat snd_hda_codec_realtek snd_hda_codec_generic iwlmvm(+) snd_sof_pci_intel_tgl mac80211 snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence soundwire_bus snd_sof_intel_hda snd_sof_pci snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core btrfs snd_compress snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec raid6_pq iwlwifi snd_hda_core snd_pcm snd_timer snd soundcore cfg80211 intel_ish_ipc(+) thunderbolt rfkill intel_ishtp ucsi_acpi wmi i2c_hid_acpi i2c_hid evdev
     CR2: 000000000000004f
     ---[ end trace 0000000000000000 ]---
    
    Check the debugfs_dir pointer for an error before using it.
    
    Fixes: 8c082a99edb9 ("iwlwifi: mvm: simplify iwl_mvm_dbgfs_register")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Luca Coelho <luciano.coelho@intel.com>
    Cc: linux-wireless@vger.kernel.org
    Cc: Kalle Valo <kvalo@kernel.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220223030630.23241-1-rdunlap@infradead.org
    [change to make both conditional]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 1db5fcbba2631277b78d7f8aff99c9607d29f6d8
Author: Golan Ben Ami <golan.ben.ami@intel.com>
Date:   Tue Mar 1 09:29:26 2022 +0200

    iwlwifi: don't advertise TWT support
    
    Some APs misbehave when TWT is used and cause our firmware to crash.
    We don't know a reasonable way to detect and work around this problem
    in the FW yet.  To prevent these crashes, disable TWT in the driver by
    stopping to advertise TWT support.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215523
    Signed-off-by: Golan Ben Ami <golan.ben.ami@intel.com>
    [reworded the commit message]
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Link: https://lore.kernel.org/r/20220301072926.153969-1-luca@coelho.fi
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 50bb467c9e76743fbc8441d29113cdad62dbc4fe
Author: Ben Dooks <ben.dooks@codethink.co.uk>
Date:   Fri Feb 18 09:38:58 2022 +0000

    rfkill: define rfill_soft_blocked() if !RFKILL
    
    If CONFIG_RFKILL is not set, the Intel WiFi driver will not build
    the iw_mvm driver part due to the missing rfill_soft_blocked()
    call. Adding a inline declaration of rfill_soft_blocked() if
    CONFIG_RFKILL=n fixes the following error:
    
    drivers/net/wireless/intel/iwlwifi/mvm/mvm.h: In function 'iwl_mvm_mei_set_sw_rfkill_state':
    drivers/net/wireless/intel/iwlwifi/mvm/mvm.h:2215:38: error: implicit declaration of function 'rfkill_soft_blocked'; did you mean 'rfkill_blocked'? [-Werror=implicit-function-declaration]
     2215 |                 mvm->hw_registered ? rfkill_soft_blocked(mvm->hw->wiphy->rfkill) : false;
          |                                      ^~~~~~~~~~~~~~~~~~~
          |                                      rfkill_blocked
    
    Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
    Reported-by: Neill Whillans <neill.whillans@codethink.co.uk>
    Fixes: 5bc9a9dd7535 ("rfkill: allow to get the software rfkill state")
    Link: https://lore.kernel.org/r/20220218093858.1245677-1-ben.dooks@codethink.co.uk
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 35e33a24f8fe0bacc55d62eb506d99c122f02012
Merge: cf90e2f1de977 c432cd598a185
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 1 10:46:04 2022 +0100

    Merge tag 'v5.17-fixes-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux into arm/fixes
    
    - Set display pipeline to DSI on mt8183 kukui jacuzzi
    - Fix display for mt8192 based boards by fixing the routing table
    
    * tag 'v5.17-fixes-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux:
      soc: mediatek: mt8192-mmsys: Fix dither to dsi0 path's input sel
      arm64: dts: mt8183: jacuzzi: Fix bus properties in anx's DSI endpoint
    
    Link: https://lore.kernel.org/r/8eb8510d-c597-4fee-e4b3-924b6d4bb3be@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit cf90e2f1de977fb79873b1eaf6df113e4e8b4469
Merge: e1d7eed180b63 fc5a40694ba68
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 1 10:45:55 2022 +0100

    Merge tag 'qcom-dts-fixes-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into arm/fixes
    
    Qualcomm DeviceTree fixes for v5.17
    
    The SDX65 platform and MTP device was added twice to the DT binding,
    this drops one of the occurances.
    
    * tag 'qcom-dts-fixes-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
      Revert "dt-bindings: arm: qcom: Document SDX65 platform and boards"
    
    Link: https://lore.kernel.org/r/20220301033838.1801689-1-bjorn.andersson@linaro.org
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit e1d7eed180b6355cedfbbd5c69ef7e0f145a5510
Merge: 9411ac255e535 382e3e0eb6a83
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 1 10:45:46 2022 +0100

    Merge tag 'qcom-arm64-fixes-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into arm/fixes
    
    Qualcomm ARM64 DeviceTree fixes for 5.17
    
    This starts off by fixing an issue introduced in a bug fix in the
    global clock controller, where the symbol clocks for UFS would
    end up picking the wrong parent clock which breaks UFS.
    
    It then makes sure that the reference clock for the USB blocks are
    enabled, even with booting without clk_ignore_unused.
    
    It corrects the apps SMMU interrupts defintion by adding a missing
    interrupt in the list.
    
    Lastly it disables the Qualcomm crypto hardware (for now) on the Lenovo
    Yoga C630, to prevent the cryptomanager tests during boot from crashing
    the device.
    
    * tag 'qcom-arm64-fixes-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
      arm64: dts: qcom: c630: disable crypto due to serror
      arm64: dts: qcom: sm8450: fix apps_smmu interrupts
      arm64: dts: qcom: sm8450: enable GCC_USB3_0_CLKREF_EN for usb
      arm64: dts: qcom: sm8350: Correct UFS symbol clocks
    
    Link: https://lore.kernel.org/r/20220301033526.1801295-1-bjorn.andersson@linaro.org
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 9411ac255e535059d06729acae34df0914e55502
Merge: 7e57714cd0ad2 515415d316168
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Mar 1 10:45:37 2022 +0100

    Merge tag 'arm-soc/for-5.17/devicetree-fixes' of https://github.com/Broadcom/stblinux into arm/fixes
    
    This pull request contains Broadcom ARM-based SoCs Device Tree fixes for
    5.17, please pull the following:
    
    - Maxime fixes the HVS (display) register range for the BCM2711
      (Raspberry Pi 4) SoC
    
    * tag 'arm-soc/for-5.17/devicetree-fixes' of https://github.com/Broadcom/stblinux:
      ARM: boot: dts: bcm2711: Fix HVS register range
    
    Link: https://lore.kernel.org/r/20220228165537.1950863-1-f.fainelli@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 5d8965704fe5662e2e4a7e4424a2cbe53e182670
Author: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
Date:   Mon Feb 28 17:15:07 2022 -0800

    MIPS: ralink: mt7621: use bitwise NOT instead of logical
    
    It was the intention to reverse the bits, not make them all zero by
    using logical NOT operator.
    
    Fixes: cc19db8b312a ("MIPS: ralink: mt7621: do memory detection on KSEG1")
    Suggested-by: Chuanhong Guo <gch981213@gmail.com>
    Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
    Reviewed-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 7cf5aa32e392dfa1e671ef2f704b729a7b39c7f9
Merge: caef14b7530c0 ffd24fa2fcc76
Author: David S. Miller <davem@davemloft.net>
Date:   Tue Mar 1 08:33:55 2022 +0000

    Merge branch '1GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-02-28
    
    This series contains updates to igc and e1000e drivers.
    
    Corinna Vinschen ensures release of hardware sempahore on failed
    register read in igc_read_phy_reg_gpy().
    
    Sasha does the same for the write variant, igc_write_phy_reg_gpy(). On
    e1000e, he resolves an issue with hardware unit hang on s0ix exit
    by disabling some bits and LAN connected device reset during power
    management flows. Lastly, he allows for TGP platforms to correct its
    NVM checksum.
    
    v2: Fix Fixes tag on patch 3
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9feaf8b387ee0ece9c1d7add308776b502a35d0c
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Mon Feb 28 20:18:51 2022 -0800

    efi: fix return value of __setup handlers
    
    When "dump_apple_properties" is used on the kernel boot command line,
    it causes an Unknown parameter message and the string is added to init's
    argument strings:
    
      Unknown kernel command line parameters "dump_apple_properties
        BOOT_IMAGE=/boot/bzImage-517rc6 efivar_ssdt=newcpu_ssdt", will be
        passed to user space.
    
     Run /sbin/init as init process
       with arguments:
         /sbin/init
         dump_apple_properties
       with environment:
         HOME=/
         TERM=linux
         BOOT_IMAGE=/boot/bzImage-517rc6
         efivar_ssdt=newcpu_ssdt
    
    Similarly when "efivar_ssdt=somestring" is used, it is added to the
    Unknown parameter message and to init's environment strings, polluting
    them (see examples above).
    
    Change the return value of the __setup functions to 1 to indicate
    that the __setup options have been handled.
    
    Fixes: 58c5475aba67 ("x86/efi: Retrieve and assign Apple device properties")
    Fixes: 475fb4e8b2f4 ("efi / ACPI: load SSTDs from EFI variables")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
    Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
    Cc: Ard Biesheuvel <ardb@kernel.org>
    Cc: linux-efi@vger.kernel.org
    Cc: Lukas Wunner <lukas@wunner.de>
    Cc: Octavian Purdila <octavian.purdila@intel.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Matt Fleming <matt@codeblueprint.co.uk>
    Link: https://lore.kernel.org/r/20220301041851.12459-1-rdunlap@infradead.org
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

commit c432cd598a185afefba1ac3b0ee226f222f71341
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Date:   Fri Jan 28 15:20:56 2022 +0100

    soc: mediatek: mt8192-mmsys: Fix dither to dsi0 path's input sel
    
    In commit d687e056a18f ("soc: mediatek: mmsys: Add mt8192 mmsys routing table"),
    the mmsys routing table for mt8192 was introduced but the input selector
    for DITHER->DSI0 has no value assigned to it.
    
    This means that we are clearing bit 0 instead of setting it, blocking
    communication between these two blocks; due to that, any display that
    is connected to DSI0 will not work, as no data will go through.
    The effect of that issue is that, during bootup, the DRM will block for
    some time, while atomically waiting for a vblank that never happens;
    later, the situation doesn't get better, leaving the display in a
    non-functional state.
    
    To fix this issue, fix the route entry in the table by assigning the
    dither input selector to MT8192_DISP_DSI0_SEL_IN.
    
    Fixes: d687e056a18f ("soc: mediatek: mmsys: Add mt8192 mmsys routing table")
    Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Tested-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
    Reviewed-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Link: https://lore.kernel.org/r/20220128142056.359900-1-angelogioacchino.delregno@collabora.com
    Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>

commit d982992669733dd75520000c6057d8ee0725a363
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Feb 28 22:53:12 2022 -0800

    Input: goodix - workaround Cherry Trail devices with a bogus ACPI Interrupt() resource
    
    ACPI/x86 devices with a Cherry Trail SoC should have a GpioInt + a regular
    GPIO ACPI resource in their ACPI tables.
    
    Some CHT devices have a bug, where the also is bogus interrupt resource
    (likely copied from a previous Bay Trail based generation of the device).
    
    The i2c-core-acpi code will assign the bogus, non-working, interrupt
    resource to client->irq. Add a workaround to fix this up.
    
    BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2043960
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220228111613.363336-1-hdegoede@redhat.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit d176708ffc20332d1c730098d2b111e0b77ece82
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Feb 28 22:52:31 2022 -0800

    Input: goodix - use the new soc_intel_is_byt() helper
    
    Use the new soc_intel_is_byt() helper from linux/platform_data/x86/soc.h.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220131143539.109142-5-hdegoede@redhat.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 1136fa0c07de570dc17858745af8be169d1440ba
Merge: ba115adf61b36 754e0b0e35608
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Mon Feb 28 23:12:55 2022 -0800

    Merge tag 'v5.17-rc4' into for-linus
    
    Merge with mainline to get the Intel ASoC generic helpers header and
    other changes.

commit bac129dbc6560dfeb634c03f0c08b78024e71915
Author: Samuel Holland <samuel@sholland.org>
Date:   Tue Feb 15 22:00:36 2022 -0600

    pinctrl: sunxi: Use unique lockdep classes for IRQs
    
    This driver, like several others, uses a chained IRQ for each GPIO bank,
    and forwards .irq_set_wake to the GPIO bank's upstream IRQ. As a result,
    a call to irq_set_irq_wake() needs to lock both the upstream and
    downstream irq_desc's. Lockdep considers this to be a possible deadlock
    when the irq_desc's share lockdep classes, which they do by default:
    
     ============================================
     WARNING: possible recursive locking detected
     5.17.0-rc3-00394-gc849047c2473 #1 Not tainted
     --------------------------------------------
     init/307 is trying to acquire lock:
     c2dfe27c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
    
     but task is already holding lock:
     c3c0ac7c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
    
     other info that might help us debug this:
      Possible unsafe locking scenario:
    
            CPU0
            ----
       lock(&irq_desc_lock_class);
       lock(&irq_desc_lock_class);
    
      *** DEADLOCK ***
    
      May be due to missing lock nesting notation
    
     4 locks held by init/307:
      #0: c1f29f18 (system_transition_mutex){+.+.}-{3:3}, at: __do_sys_reboot+0x90/0x23c
      #1: c20f7760 (&dev->mutex){....}-{3:3}, at: device_shutdown+0xf4/0x224
      #2: c2e804d8 (&dev->mutex){....}-{3:3}, at: device_shutdown+0x104/0x224
      #3: c3c0ac7c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
    
     stack backtrace:
     CPU: 0 PID: 307 Comm: init Not tainted 5.17.0-rc3-00394-gc849047c2473 #1
     Hardware name: Allwinner sun8i Family
      unwind_backtrace from show_stack+0x10/0x14
      show_stack from dump_stack_lvl+0x68/0x90
      dump_stack_lvl from __lock_acquire+0x1680/0x31a0
      __lock_acquire from lock_acquire+0x148/0x3dc
      lock_acquire from _raw_spin_lock_irqsave+0x50/0x6c
      _raw_spin_lock_irqsave from __irq_get_desc_lock+0x58/0xa0
      __irq_get_desc_lock from irq_set_irq_wake+0x2c/0x19c
      irq_set_irq_wake from irq_set_irq_wake+0x13c/0x19c
        [tail call from sunxi_pinctrl_irq_set_wake]
      irq_set_irq_wake from gpio_keys_suspend+0x80/0x1a4
      gpio_keys_suspend from gpio_keys_shutdown+0x10/0x2c
      gpio_keys_shutdown from device_shutdown+0x180/0x224
      device_shutdown from __do_sys_reboot+0x134/0x23c
      __do_sys_reboot from ret_fast_syscall+0x0/0x1c
    
    However, this can never deadlock because the upstream and downstream
    IRQs are never the same (nor do they even involve the same irqchip).
    
    Silence this erroneous lockdep splat by applying what appears to be the
    usual fix of moving the GPIO IRQs to separate lockdep classes.
    
    Fixes: a59c99d9eaf9 ("pinctrl: sunxi: Forward calls to irq_set_irq_wake")
    Reported-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Samuel Holland <samuel@sholland.org>
    Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Tested-by: Guenter Roeck <linux@roeck-us.net>
    Link: https://lore.kernel.org/r/20220216040037.22730-1-samuel@sholland.org
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 7795686d573de0438bba6b2b344e6b203223c889
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date:   Wed Jan 26 12:02:04 2022 +0100

    pinctrl-sunxi: sunxi_pinctrl_gpio_direction_in/output: use correct offset
    
    The commit that sets the direction directly without calling
    pinctrl_gpio_direction(), forgot to add chip->base to the offset when
    calling sunxi_pmx_gpio_set_direction().
    
    This caused failures for various Allwinner boards which have two
    GPIO blocks.
    
    Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
    Reported-by: 5kft <5kft@5kft.org>
    Suggested-by: 5kft <5kft@5kft.org>
    Reported-by: Corentin Labbe <clabbe.montjoie@gmail.com>
    Fixes: 8df89a7cbc63 (pinctrl-sunxi: don't call pinctrl_gpio_direction())
    Tested-by: Corentin Labbe <clabbe.montjoie@gmail.com>
    Tested-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Link: https://lore.kernel.org/r/0f536cd8-01db-5d16-2cec-ec6d19409a49@xs4all.nl
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    [Picked from linux-next to pinctrl fixes]
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit ffd24fa2fcc76ecb2e61e7a4ef8588177bcb42a6
Author: Sasha Neftin <sasha.neftin@intel.com>
Date:   Thu Feb 3 14:21:49 2022 +0200

    e1000e: Correct NVM checksum verification flow
    
    Update MAC type check e1000_pch_tgp because for e1000_pch_cnp,
    NVM checksum update is still possible.
    Emit a more detailed warning message.
    
    Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1191663
    Fixes: 4051f68318ca ("e1000e: Do not take care about recovery NVM checksum")
    Reported-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
    Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Naama Meir <naamax.meir@linux.intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 1866aa0d0d6492bc2f8d22d0df49abaccf50cddd
Author: Sasha Neftin <sasha.neftin@intel.com>
Date:   Tue Jan 25 19:31:23 2022 +0200

    e1000e: Fix possible HW unit hang after an s0ix exit
    
    Disable the OEM bit/Gig Disable/restart AN impact and disable the PHY
    LAN connected device (LCD) reset during power management flows. This
    fixes possible HW unit hangs on the s0ix exit on some corporate ADL
    platforms.
    
    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=214821
    Fixes: 3e55d231716e ("e1000e: Add handshake with the CSME to support S0ix")
    Suggested-by: Dima Ruinskiy <dima.ruinskiy@intel.com>
    Suggested-by: Nir Efrati <nir.efrati@intel.com>
    Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 17a8f31bba7bac8cce4bd12bab50697da96e7710
Author: Florian Westphal <fw@strlen.de>
Date:   Mon Feb 28 04:18:05 2022 +0100

    netfilter: egress: silence egress hook lockdep splats
    
    Netfilter assumes its called with rcu_read_lock held, but in egress
    hook case it may be called with BH readlock.
    
    This triggers lockdep splat.
    
    In order to avoid to change all rcu_dereference() to
    rcu_dereference_check(..., rcu_read_lock_bh_held()), wrap nf_hook_slow
    with read lock/unlock pair.
    
    Reported-by: Eric Dumazet <eric.dumazet@gmail.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 56763f12b0f02706576a088e85ef856deacc98a0
Author: Eric Dumazet <edumazet@google.com>
Date:   Sun Feb 27 10:01:41 2022 -0800

    netfilter: fix use-after-free in __nf_register_net_hook()
    
    We must not dereference @new_hooks after nf_hook_mutex has been released,
    because other threads might have freed our allocated hooks already.
    
    BUG: KASAN: use-after-free in nf_hook_entries_get_hook_ops include/linux/netfilter.h:130 [inline]
    BUG: KASAN: use-after-free in hooks_validate net/netfilter/core.c:171 [inline]
    BUG: KASAN: use-after-free in __nf_register_net_hook+0x77a/0x820 net/netfilter/core.c:438
    Read of size 2 at addr ffff88801c1a8000 by task syz-executor237/4430
    
    CPU: 1 PID: 4430 Comm: syz-executor237 Not tainted 5.17.0-rc5-syzkaller-00306-g2293be58d6a1 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     print_address_description.constprop.0.cold+0x8d/0x336 mm/kasan/report.c:255
     __kasan_report mm/kasan/report.c:442 [inline]
     kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
     nf_hook_entries_get_hook_ops include/linux/netfilter.h:130 [inline]
     hooks_validate net/netfilter/core.c:171 [inline]
     __nf_register_net_hook+0x77a/0x820 net/netfilter/core.c:438
     nf_register_net_hook+0x114/0x170 net/netfilter/core.c:571
     nf_register_net_hooks+0x59/0xc0 net/netfilter/core.c:587
     nf_synproxy_ipv6_init+0x85/0xe0 net/netfilter/nf_synproxy_core.c:1218
     synproxy_tg6_check+0x30d/0x560 net/ipv6/netfilter/ip6t_SYNPROXY.c:81
     xt_check_target+0x26c/0x9e0 net/netfilter/x_tables.c:1038
     check_target net/ipv6/netfilter/ip6_tables.c:530 [inline]
     find_check_entry.constprop.0+0x7f1/0x9e0 net/ipv6/netfilter/ip6_tables.c:573
     translate_table+0xc8b/0x1750 net/ipv6/netfilter/ip6_tables.c:735
     do_replace net/ipv6/netfilter/ip6_tables.c:1153 [inline]
     do_ip6t_set_ctl+0x56e/0xb90 net/ipv6/netfilter/ip6_tables.c:1639
     nf_setsockopt+0x83/0xe0 net/netfilter/nf_sockopt.c:101
     ipv6_setsockopt+0x122/0x180 net/ipv6/ipv6_sockglue.c:1024
     rawv6_setsockopt+0xd3/0x6a0 net/ipv6/raw.c:1084
     __sys_setsockopt+0x2db/0x610 net/socket.c:2180
     __do_sys_setsockopt net/socket.c:2191 [inline]
     __se_sys_setsockopt net/socket.c:2188 [inline]
     __x64_sys_setsockopt+0xba/0x150 net/socket.c:2188
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7f65a1ace7d9
    Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007f65a1a7f308 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
    RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 00007f65a1ace7d9
    RDX: 0000000000000040 RSI: 0000000000000029 RDI: 0000000000000003
    RBP: 00007f65a1b574c8 R08: 0000000000000001 R09: 0000000000000000
    R10: 0000000020000000 R11: 0000000000000246 R12: 00007f65a1b55130
    R13: 00007f65a1b574c0 R14: 00007f65a1b24090 R15: 0000000000022000
     </TASK>
    
    The buggy address belongs to the page:
    page:ffffea0000706a00 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1c1a8
    flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
    raw: 00fff00000000000 ffffea0001c1b108 ffffea000046dd08 0000000000000000
    raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
    page dumped because: kasan: bad access detected
    page_owner tracks the page as freed
    page last allocated via order 2, migratetype Unmovable, gfp_mask 0x52dc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_ZERO), pid 4430, ts 1061781545818, free_ts 1061791488993
     prep_new_page mm/page_alloc.c:2434 [inline]
     get_page_from_freelist+0xa72/0x2f50 mm/page_alloc.c:4165
     __alloc_pages+0x1b2/0x500 mm/page_alloc.c:5389
     __alloc_pages_node include/linux/gfp.h:572 [inline]
     alloc_pages_node include/linux/gfp.h:595 [inline]
     kmalloc_large_node+0x62/0x130 mm/slub.c:4438
     __kmalloc_node+0x35a/0x4a0 mm/slub.c:4454
     kmalloc_node include/linux/slab.h:604 [inline]
     kvmalloc_node+0x97/0x100 mm/util.c:580
     kvmalloc include/linux/slab.h:731 [inline]
     kvzalloc include/linux/slab.h:739 [inline]
     allocate_hook_entries_size net/netfilter/core.c:61 [inline]
     nf_hook_entries_grow+0x140/0x780 net/netfilter/core.c:128
     __nf_register_net_hook+0x144/0x820 net/netfilter/core.c:429
     nf_register_net_hook+0x114/0x170 net/netfilter/core.c:571
     nf_register_net_hooks+0x59/0xc0 net/netfilter/core.c:587
     nf_synproxy_ipv6_init+0x85/0xe0 net/netfilter/nf_synproxy_core.c:1218
     synproxy_tg6_check+0x30d/0x560 net/ipv6/netfilter/ip6t_SYNPROXY.c:81
     xt_check_target+0x26c/0x9e0 net/netfilter/x_tables.c:1038
     check_target net/ipv6/netfilter/ip6_tables.c:530 [inline]
     find_check_entry.constprop.0+0x7f1/0x9e0 net/ipv6/netfilter/ip6_tables.c:573
     translate_table+0xc8b/0x1750 net/ipv6/netfilter/ip6_tables.c:735
     do_replace net/ipv6/netfilter/ip6_tables.c:1153 [inline]
     do_ip6t_set_ctl+0x56e/0xb90 net/ipv6/netfilter/ip6_tables.c:1639
     nf_setsockopt+0x83/0xe0 net/netfilter/nf_sockopt.c:101
    page last free stack trace:
     reset_page_owner include/linux/page_owner.h:24 [inline]
     free_pages_prepare mm/page_alloc.c:1352 [inline]
     free_pcp_prepare+0x374/0x870 mm/page_alloc.c:1404
     free_unref_page_prepare mm/page_alloc.c:3325 [inline]
     free_unref_page+0x19/0x690 mm/page_alloc.c:3404
     kvfree+0x42/0x50 mm/util.c:613
     rcu_do_batch kernel/rcu/tree.c:2527 [inline]
     rcu_core+0x7b1/0x1820 kernel/rcu/tree.c:2778
     __do_softirq+0x29b/0x9c2 kernel/softirq.c:558
    
    Memory state around the buggy address:
     ffff88801c1a7f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
     ffff88801c1a7f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    >ffff88801c1a8000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                       ^
     ffff88801c1a8080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
     ffff88801c1a8100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
    
    Fixes: 2420b79f8c18 ("netfilter: debug: check for sorted array")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Acked-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 719fce7539cd3e186598e2aed36325fe892150cf
Merge: 201b5c016f165 c253bf70c657b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 28 12:51:14 2022 -0800

    Merge tag 'soc-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC fixes from Arnd Bergmann:
     "The code changes address mostly minor problems:
    
       - Several NXP/FSL SoC driver fixes, addressing issues with error
         handling and compilation
    
       - Fix a clock disabling imbalance in gpcv2 driver.
    
       - Arm Juno DMA coherency issue
    
       - Trivial firmware driver fixes for op-tee and scmi firmware
    
      The remaining changes address issues in the devicetree files:
    
       - A timer regression for the OMAP devkit8000, which has to use the
         alternative timer.
    
       - A hang in the i.MX8MM power domain configuration
    
       - Multiple fixes for the Rockchip RK3399 addressing issues with sound
         and eMMC
    
       - Cosmetic fixes for i.MX8ULP, RK3xxx, and Tegra124"
    
    * tag 'soc-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (32 commits)
      ARM: tegra: Move panels to AUX bus
      soc: imx: gpcv2: Fix clock disabling imbalance in error path
      soc: fsl: qe: Check of ioremap return value
      soc: fsl: qe: fix typo in a comment
      soc: fsl: guts: Add a missing memory allocation failure check
      soc: fsl: guts: Revert commit 3c0d64e867ed
      soc: fsl: Correct MAINTAINERS database (SOC)
      soc: fsl: Correct MAINTAINERS database (QUICC ENGINE LIBRARY)
      soc: fsl: Replace kernel.h with the necessary inclusions
      dt-bindings: fsl,layerscape-dcfg: add missing compatible for lx2160a
      dt-bindings: qoriq-clock: add missing compatible for lx2160a
      ARM: dts: Use 32KiHz oscillator on devkit8000
      ARM: dts: switch timer config to common devkit8000 devicetree
      tee: optee: fix error return code in probe function
      arm64: dts: imx8ulp: Set #thermal-sensor-cells to 1 as required
      arm64: dts: imx8mm: Fix VPU Hanging
      ARM: dts: rockchip: fix a typo on rk3288 crypto-controller
      ARM: dts: rockchip: reorder rk322x hmdi clocks
      firmware: arm_scmi: Remove space in MODULE_ALIAS name
      arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg"
      ...

commit 201b5c016f1655ead2ecc7e7e270841782cbbd0b
Merge: 7e57714cd0ad2 258dd902022cb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 28 12:44:33 2022 -0800

    Merge tag 'efi-urgent-for-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi
    
    Pull EFI fixes from Ard Biesheuvel:
    
     - don't treat valid hartid U32_MAX as a failure return code (RISC-V)
    
     - avoid blocking query_variable_info() call when blocking is not
       allowed
    
    * tag 'efi-urgent-for-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi:
      efivars: Respect "block" flag in efivar_entry_set_safe()
      riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value

commit cb1852783f790feae845006d062acb9e0a5d4304
Author: Carsten Haitzler <carsten.haitzler@arm.com>
Date:   Mon Jan 24 16:24:37 2022 +0000

    drm/arm: arm hdlcd select DRM_GEM_CMA_HELPER
    
    Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
    
    Fixes: 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER option")
    Reviewed-by: Steven Price <steven.price@arm.com>
    Signed-off-by: Carsten Haitzler <carsten.haitzler@arm.com>
    Acked-by: Liviu Dudau <liviu.dudau@arm.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220124162437.2470344-1-carsten.haitzler@foss.arm.com

commit 26d3474348293dc752c55fe6d41282199f73714c
Author: Douglas Anderson <dianders@chromium.org>
Date:   Tue Feb 22 14:18:43 2022 -0800

    drm/bridge: ti-sn65dsi86: Properly undo autosuspend
    
    The PM Runtime docs say:
      Drivers in ->remove() callback should undo the runtime PM changes done
      in ->probe(). Usually this means calling pm_runtime_disable(),
      pm_runtime_dont_use_autosuspend() etc.
    
    We weren't doing that for autosuspend. Let's do it.
    
    Fixes: 9bede63127c6 ("drm/bridge: ti-sn65dsi86: Use pm_runtime autosuspend")
    Signed-off-by: Douglas Anderson <dianders@chromium.org>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220222141838.1.If784ba19e875e8ded4ec4931601ce6d255845245@changeid

commit e9b6013a7ce31535b04b02ba99babefe8a8599fa
Author: Kim Phillips <kim.phillips@amd.com>
Date:   Mon Feb 28 11:23:16 2022 -0600

    x86/speculation: Update link to AMD speculation whitepaper
    
    Update the link to the "Software Techniques for Managing Speculation
    on AMD Processors" whitepaper.
    
    Signed-off-by: Kim Phillips <kim.phillips@amd.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>

commit 244d00b5dd4755f8df892c86cab35fb2cfd4f14b
Author: Kim Phillips <kim.phillips@amd.com>
Date:   Mon Feb 28 11:23:15 2022 -0600

    x86/speculation: Use generic retpoline by default on AMD
    
    AMD retpoline may be susceptible to speculation. The speculation
    execution window for an incorrect indirect branch prediction using
    LFENCE/JMP sequence may potentially be large enough to allow
    exploitation using Spectre V2.
    
    By default, don't use retpoline,lfence on AMD.  Instead, use the
    generic retpoline.
    
    Signed-off-by: Kim Phillips <kim.phillips@amd.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>

commit c4208653a327a09da1e9e7b10299709b6d9b17bf
Author: Sasha Neftin <sasha.neftin@intel.com>
Date:   Sun Feb 20 09:29:15 2022 +0200

    igc: igc_write_phy_reg_gpy: drop premature return
    
    Similar to "igc_read_phy_reg_gpy: drop premature return" patch.
    igc_write_phy_reg_gpy checks the return value from igc_write_phy_reg_mdic
    and if it's not 0, returns immediately. By doing this, it leaves the HW
    semaphore in the acquired state.
    
    Drop this premature return statement, the function returns after
    releasing the semaphore immediately anyway.
    
    Fixes: 5586838fe9ce ("igc: Add code for PHY support")
    Suggested-by: Dima Ruinskiy <dima.ruinskiy@intel.com>
    Reported-by: Corinna Vinschen <vinschen@redhat.com>
    Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Naama Meir <naamax.meir@linux.intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit fda2635466cd26ad237e1bc5d3f6a60f97ad09b6
Author: Corinna Vinschen <vinschen@redhat.com>
Date:   Wed Feb 16 14:31:35 2022 +0100

    igc: igc_read_phy_reg_gpy: drop premature return
    
    igc_read_phy_reg_gpy checks the return value from igc_read_phy_reg_mdic
    and if it's not 0, returns immediately. By doing this, it leaves the HW
    semaphore in the acquired state.
    
    Drop this premature return statement, the function returns after
    releasing the semaphore immediately anyway.
    
    Fixes: 5586838fe9ce ("igc: Add code for PHY support")
    Signed-off-by: Corinna Vinschen <vinschen@redhat.com>
    Acked-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Naama Meir <naamax.meir@linux.intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 7b83299e5b9385943a857d59e15cba270df20d7e
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Feb 23 20:46:35 2022 +0100

    ARM: 9182/1: mmu: fix returns from early_param() and __setup() functions
    
    early_param() handlers should return 0 on success.
    __setup() handlers should return 1 on success, i.e., the parameter
    has been handled. A return of 0 would cause the "option=value" string
    to be added to init's environment strings, polluting it.
    
    ../arch/arm/mm/mmu.c: In function 'test_early_cachepolicy':
    ../arch/arm/mm/mmu.c:215:1: error: no return statement in function returning non-void [-Werror=return-type]
    ../arch/arm/mm/mmu.c: In function 'test_noalign_setup':
    ../arch/arm/mm/mmu.c:221:1: error: no return statement in function returning non-void [-Werror=return-type]
    
    Fixes: b849a60e0903 ("ARM: make cr_alignment read-only #ifndef CONFIG_CPU_CP15")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
    Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: patches@armlinux.org.uk
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 30939293262eb433c960c4532a0d59c4073b2b84
Author: Yu Kuai <yukuai3@huawei.com>
Date:   Mon Feb 28 11:43:54 2022 +0800

    blktrace: fix use after free for struct blk_trace
    
    When tracing the whole disk, 'dropped' and 'msg' will be created
    under 'q->debugfs_dir' and 'bt->dir' is NULL, thus blk_trace_free()
    won't remove those files. What's worse, the following UAF can be
    triggered because of accessing stale 'dropped' and 'msg':
    
    ==================================================================
    BUG: KASAN: use-after-free in blk_dropped_read+0x89/0x100
    Read of size 4 at addr ffff88816912f3d8 by task blktrace/1188
    
    CPU: 27 PID: 1188 Comm: blktrace Not tainted 5.17.0-rc4-next-20220217+ #469
    Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-4
    Call Trace:
     <TASK>
     dump_stack_lvl+0x34/0x44
     print_address_description.constprop.0.cold+0xab/0x381
     ? blk_dropped_read+0x89/0x100
     ? blk_dropped_read+0x89/0x100
     kasan_report.cold+0x83/0xdf
     ? blk_dropped_read+0x89/0x100
     kasan_check_range+0x140/0x1b0
     blk_dropped_read+0x89/0x100
     ? blk_create_buf_file_callback+0x20/0x20
     ? kmem_cache_free+0xa1/0x500
     ? do_sys_openat2+0x258/0x460
     full_proxy_read+0x8f/0xc0
     vfs_read+0xc6/0x260
     ksys_read+0xb9/0x150
     ? vfs_write+0x3d0/0x3d0
     ? fpregs_assert_state_consistent+0x55/0x60
     ? exit_to_user_mode_prepare+0x39/0x1e0
     do_syscall_64+0x35/0x80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7fbc080d92fd
    Code: ce 20 00 00 75 10 b8 00 00 00 00 0f 05 48 3d 01 f0 ff ff 73 31 c3 48 83 1
    RSP: 002b:00007fbb95ff9cb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000000
    RAX: ffffffffffffffda RBX: 00007fbb95ff9dc0 RCX: 00007fbc080d92fd
    RDX: 0000000000000100 RSI: 00007fbb95ff9cc0 RDI: 0000000000000045
    RBP: 0000000000000045 R08: 0000000000406299 R09: 00000000fffffffd
    R10: 000000000153afa0 R11: 0000000000000293 R12: 00007fbb780008c0
    R13: 00007fbb78000938 R14: 0000000000608b30 R15: 00007fbb780029c8
     </TASK>
    
    Allocated by task 1050:
     kasan_save_stack+0x1e/0x40
     __kasan_kmalloc+0x81/0xa0
     do_blk_trace_setup+0xcb/0x410
     __blk_trace_setup+0xac/0x130
     blk_trace_ioctl+0xe9/0x1c0
     blkdev_ioctl+0xf1/0x390
     __x64_sys_ioctl+0xa5/0xe0
     do_syscall_64+0x35/0x80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Freed by task 1050:
     kasan_save_stack+0x1e/0x40
     kasan_set_track+0x21/0x30
     kasan_set_free_info+0x20/0x30
     __kasan_slab_free+0x103/0x180
     kfree+0x9a/0x4c0
     __blk_trace_remove+0x53/0x70
     blk_trace_ioctl+0x199/0x1c0
     blkdev_common_ioctl+0x5e9/0xb30
     blkdev_ioctl+0x1a5/0x390
     __x64_sys_ioctl+0xa5/0xe0
     do_syscall_64+0x35/0x80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    The buggy address belongs to the object at ffff88816912f380
     which belongs to the cache kmalloc-96 of size 96
    The buggy address is located 88 bytes inside of
     96-byte region [ffff88816912f380, ffff88816912f3e0)
    The buggy address belongs to the page:
    page:000000009a1b4e7c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0f
    flags: 0x17ffffc0000200(slab|node=0|zone=2|lastcpupid=0x1fffff)
    raw: 0017ffffc0000200 ffffea00044f1100 dead000000000002 ffff88810004c780
    raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000
    page dumped because: kasan: bad access detected
    
    Memory state around the buggy address:
     ffff88816912f280: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
     ffff88816912f300: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
    >ffff88816912f380: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
                                                        ^
     ffff88816912f400: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
     ffff88816912f480: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
    ==================================================================
    
    Fixes: c0ea57608b69 ("blktrace: remove debugfs file dentries from struct blk_trace")
    Signed-off-by: Yu Kuai <yukuai3@huawei.com>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220228034354.4047385-1-yukuai3@huawei.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 9826e393e4a8c3df474e7f9eacd3087266f74005
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 7 08:09:11 2022 +0000

    iommu/tegra-smmu: Fix missing put_device() call in tegra_smmu_find
    
    The reference taken by 'of_find_device_by_node()' must be released when
    not needed anymore.
    Add the corresponding 'put_device()' in the error handling path.
    
    Fixes: 765a9d1d02b2 ("iommu/tegra-smmu: Fix mc errors on tegra124-nyan")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Acked-by: Thierry Reding <treding@nvidia.com>
    Link: https://lore.kernel.org/r/20220107080915.12686-1-linmq006@gmail.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit b00833768e170a31af09268f7ab96aecfcca9623
Author: Adrian Huang <ahuang12@lenovo.com>
Date:   Mon Feb 21 13:33:48 2022 +0800

    iommu/vt-d: Fix double list_add when enabling VMD in scalable mode
    
    When enabling VMD and IOMMU scalable mode, the following kernel panic
    call trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids
    CPU) during booting:
    
    pci 0000:59:00.5: Adding to iommu group 42
    ...
    vmd 0000:59:00.5: PCI host bridge to bus 10000:80
    pci 10000:80:01.0: [8086:352a] type 01 class 0x060400
    pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]
    pci 10000:80:01.0: enabling Extended Tags
    pci 10000:80:01.0: PME# supported from D0 D3hot D3cold
    pci 10000:80:01.0: DMAR: Setup RID2PASID failed
    pci 10000:80:01.0: Failed to add to iommu group 42: -16
    pci 10000:80:03.0: [8086:352b] type 01 class 0x060400
    pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]
    pci 10000:80:03.0: enabling Extended Tags
    pci 10000:80:03.0: PME# supported from D0 D3hot D3cold
    ------------[ cut here ]------------
    kernel BUG at lib/list_debug.c:29!
    invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
    CPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7
    Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022
    Workqueue: events work_for_cpu_fn
    RIP: 0010:__list_add_valid.cold+0x26/0x3f
    Code: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f
          0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1
          fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9
          9e e8 8b b1 fe
    RSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246
    RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8
    RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20
    RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888
    R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0
    R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70
    FS:  0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
    PKRU: 55555554
    Call Trace:
     <TASK>
     intel_pasid_alloc_table+0x9c/0x1d0
     dmar_insert_one_dev_info+0x423/0x540
     ? device_to_iommu+0x12d/0x2f0
     intel_iommu_attach_device+0x116/0x290
     __iommu_attach_device+0x1a/0x90
     iommu_group_add_device+0x190/0x2c0
     __iommu_probe_device+0x13e/0x250
     iommu_probe_device+0x24/0x150
     iommu_bus_notifier+0x69/0x90
     blocking_notifier_call_chain+0x5a/0x80
     device_add+0x3db/0x7b0
     ? arch_memremap_can_ram_remap+0x19/0x50
     ? memremap+0x75/0x140
     pci_device_add+0x193/0x1d0
     pci_scan_single_device+0xb9/0xf0
     pci_scan_slot+0x4c/0x110
     pci_scan_child_bus_extend+0x3a/0x290
     vmd_enable_domain.constprop.0+0x63e/0x820
     vmd_probe+0x163/0x190
     local_pci_probe+0x42/0x80
     work_for_cpu_fn+0x13/0x20
     process_one_work+0x1e2/0x3b0
     worker_thread+0x1c4/0x3a0
     ? rescuer_thread+0x370/0x370
     kthread+0xc7/0xf0
     ? kthread_complete_and_exit+0x20/0x20
     ret_from_fork+0x1f/0x30
     </TASK>
    Modules linked in:
    ---[ end trace 0000000000000000 ]---
    ...
    Kernel panic - not syncing: Fatal exception
    Kernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
    ---[ end Kernel panic - not syncing: Fatal exception ]---
    
    The following 'lspci' output shows devices '10000:80:*' are subdevices of
    the VMD device 0000:59:00.5:
    
      $ lspci
      ...
      0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)
      ...
      10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)
      10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)
      10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)
      10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)
      10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]
      10000:82:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]
    
    The symptom 'list_add double add' is caused by the following failure
    message:
    
      pci 10000:80:01.0: DMAR: Setup RID2PASID failed
      pci 10000:80:01.0: Failed to add to iommu group 42: -16
      pci 10000:80:03.0: [8086:352b] type 01 class 0x060400
    
    Device 10000:80:01.0 is the subdevice of the VMD device 0000:59:00.5,
    so invoking intel_pasid_alloc_table() gets the pasid_table of the VMD
    device 0000:59:00.5. Here is call path:
    
      intel_pasid_alloc_table
        pci_for_each_dma_alias
         get_alias_pasid_table
           search_pasid_table
    
    pci_real_dma_dev() in pci_for_each_dma_alias() gets the real dma device
    which is the VMD device 0000:59:00.5. However, pte of the VMD device
    0000:59:00.5 has been configured during this message "pci 0000:59:00.5:
    Adding to iommu group 42". So, the status -EBUSY is returned when
    configuring pasid entry for device 10000:80:01.0.
    
    It then invokes dmar_remove_one_dev_info() to release
    'struct device_domain_info *' from iommu_devinfo_cache. But, the pasid
    table is not released because of the following statement in
    __dmar_remove_one_dev_info():
    
            if (info->dev && !dev_is_real_dma_subdevice(info->dev)) {
                    ...
                    intel_pasid_free_table(info->dev);
            }
    
    The subsequent dmar_insert_one_dev_info() operation of device
    10000:80:03.0 allocates 'struct device_domain_info *' from
    iommu_devinfo_cache. The allocated address is the same address that
    is released previously for device 10000:80:01.0. Finally, invoking
    device_attach_pasid_table() causes the issue.
    
    `git bisect` points to the offending commit 474dd1c65064 ("iommu/vt-d:
    Fix clearing real DMA device's scalable-mode context entries"), which
    releases the pasid table if the device is not the subdevice by
    checking the returned status of dev_is_real_dma_subdevice().
    Reverting the offending commit can work around the issue.
    
    The solution is to prevent from allocating pasid table if those
    devices are subdevices of the VMD device.
    
    Fixes: 474dd1c65064 ("iommu/vt-d: Fix clearing real DMA device's scalable-mode context entries")
    Cc: stable@vger.kernel.org # v5.14+
    Signed-off-by: Adrian Huang <ahuang12@lenovo.com>
    Link: https://lore.kernel.org/r/20220216091307.703-1-adrianhuang0701@gmail.com
    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Link: https://lore.kernel.org/r/20220221053348.262724-2-baolu.lu@linux.intel.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit f0d2f15362f02444c5d7ffd5a5eb03e4aa54b685
Author: Rong Chen <rong.chen@amlogic.com>
Date:   Wed Feb 16 20:42:39 2022 +0800

    mmc: meson: Fix usage of meson_mmc_post_req()
    
    Currently meson_mmc_post_req() is called in meson_mmc_request() right
    after meson_mmc_start_cmd(). This could lead to DMA unmapping before the request
    is actually finished.
    
    To fix, don't call meson_mmc_post_req() until meson_mmc_request_done().
    
    Signed-off-by: Rong Chen <rong.chen@amlogic.com>
    Reviewed-by: Kevin Hilman <khilman@baylibre.com>
    Fixes: 79ed05e329c3 ("mmc: meson-gx: add support for descriptor chain mode")
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220216124239.4007667-1-rong.chen@amlogic.com
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit 08783aa7693f55619859f4f63f384abf17cb58c5
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Thu Feb 24 15:21:42 2022 +0200

    drm/i915: s/JSP2/ICP2/ PCH
    
    This JSP2 PCH actually seems to be some special Apple
    specific ICP variant rather than a JSP. Make it so. Or at
    least all the references to it seem to be some Apple ICL
    machines. Didn't manage to find these PCI IDs in any
    public chipset docs unfortunately.
    
    The only thing we're losing here with this JSP->ICP change
    is Wa_14011294188, but based on the HSD that isn't actually
    needed on any ICP based design (including JSP), only TGP
    based stuff (including MCC) really need it. The documented
    w/a just never made that distinction because Windows didn't
    want to differentiate between JSP and MCC (not sure how
    they handle hpd/ddc/etc. then though...).
    
    Cc: stable@vger.kernel.org
    Cc: Matt Roper <matthew.d.roper@intel.com>
    Cc: Vivek Kasireddy <vivek.kasireddy@intel.com>
    Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4226
    Fixes: 943682e3bd19 ("drm/i915: Introduce Jasper Lake PCH")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220224132142.12927-1-ville.syrjala@linux.intel.com
    Acked-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
    Tested-by: Tomas Bzatek <bugs@bzatek.net>
    (cherry picked from commit 53581504a8e216d435f114a4f2596ad0dfd902fc)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 1b279f6ad467535c3b8a66b4edefaca2cdd5bdc3
Author: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Date:   Wed Feb 16 10:15:04 2022 -0800

    drm/i915/guc/slpc: Correct the param count for unset param
    
    SLPC unset param H2G only needs one parameter - the id of the
    param.
    
    Fixes: 025cb07bebfa ("drm/i915/guc/slpc: Cache platform frequency limits")
    
    Suggested-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
    Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
    Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
    Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220216181504.7155-1-vinay.belgaumkar@intel.com
    (cherry picked from commit 9648f1c3739505557d94ff749a4f32192ea81fe3)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit caef14b7530c065fb85d54492768fa48fdb5093e
Author: Alex Elder <elder@linaro.org>
Date:   Fri Feb 25 14:15:30 2022 -0600

    net: ipa: fix a build dependency
    
    An IPA build problem arose in the linux-next tree the other day.
    The problem is that a recent commit adds a new dependency on some
    code, and the Kconfig file for IPA doesn't reflect that dependency.
    As a result, some configurations can fail to build (particularly
    when COMPILE_TEST is enabled).
    
    The recent patch adds calls to qmp_get(), qmp_put(), and qmp_send(),
    and those are built based on the QCOM_AOSS_QMP config option.  If
    that symbol is not defined, stubs are defined, so we just need to
    ensure QCOM_AOSS_QMP is compatible with QCOM_IPA, or it's not
    defined.
    
    Reported-by: Randy Dunlap <rdunlap@infradead.org>
    Fixes: 34a081761e4e3 ("net: ipa: request IPA register values be retained")
    Signed-off-by: Alex Elder <elder@linaro.org>
    Tested-by: Randy Dunlap <rdunlap@infradead.org>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d4e26aaea7f82ba884dcb4acfe689406bc092dc3
Author: Jia-Ju Bai <baijiaju1990@gmail.com>
Date:   Fri Feb 25 04:52:30 2022 -0800

    atm: firestream: check the return value of ioremap() in fs_init()
    
    The function ioremap() in fs_init() can fail, so its return value should
    be checked.
    
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 90d4025285748448809701a44cf466a3f5443eaa
Author: Casper Andersson <casper.casan@gmail.com>
Date:   Fri Feb 25 13:43:27 2022 +0100

    net: sparx5: Add #include to remove warning
    
    main.h uses NUM_TARGETS from main_regs.h, but
    the missing include never causes any errors
    because everywhere main.h is (currently)
    included, main_regs.h is included before.
    But since it is dependent on main_regs.h
    it should always be included.
    
    Signed-off-by: Casper Andersson <casper.casan@gmail.com>
    Reviewed-by: Joacim Zetterling <joacim.zetterling@westermo.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4d08b7b57ece83a1c31c633a7e4e27f121157f9c
Author: Tony Lu <tonylu@linux.alibaba.com>
Date:   Fri Feb 25 14:56:57 2022 +0800

    net/smc: Fix cleanup when register ULP fails
    
    This patch calls smc_ib_unregister_client() when tcp_register_ulp()
    fails, and make sure to clean it up.
    
    Fixes: d7cd421da9da ("net/smc: Introduce TCP ULP support")
    Signed-off-by: Tony Lu <tonylu@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 32568ae37596b529628ac09b875f4874e614f63f
Author: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Date:   Mon Feb 14 15:05:07 2022 -0500

    arm64: dts: mt8183: jacuzzi: Fix bus properties in anx's DSI endpoint
    
    mt8183-kukui-jacuzzi has an anx7625 bridge connected to the output of
    its DSI host. However, after commit fd0310b6fe7d ("drm/bridge: anx7625:
    add MIPI DPI input feature"), a bus-type property started being required
    in the endpoint node by the driver to indicate whether it is DSI or DPI.
    
    Add the missing bus-type property and set it to 5
    (V4L2_FWNODE_BUS_TYPE_PARALLEL) so that the driver has its input
    configured to DSI and the display pipeline can probe correctly.
    
    While at it, also set the data-lanes property that was also introduced
    in that same commit, so that we don't rely on the default value.
    
    Fixes: fd0310b6fe7d ("drm/bridge: anx7625: add MIPI DPI input feature")
    Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Link: https://lore.kernel.org/r/20220214200507.2500693-1-nfraprado@collabora.com
    Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>

commit 9995b408f17ff8c7f11bc725c8aa225ba3a63b1c
Author: j.nixdorf@avm.de <j.nixdorf@avm.de>
Date:   Thu Feb 24 10:06:49 2022 +0100

    net: ipv6: ensure we call ipv6_mc_down() at most once
    
    There are two reasons for addrconf_notify() to be called with NETDEV_DOWN:
    either the network device is actually going down, or IPv6 was disabled
    on the interface.
    
    If either of them stays down while the other is toggled, we repeatedly
    call the code for NETDEV_DOWN, including ipv6_mc_down(), while never
    calling the corresponding ipv6_mc_up() in between. This will cause a
    new entry in idev->mc_tomb to be allocated for each multicast group
    the interface is subscribed to, which in turn leaks one struct ifmcaddr6
    per nontrivial multicast group the interface is subscribed to.
    
    The following reproducer will leak at least $n objects:
    
    ip addr add ff2e::4242/32 dev eth0 autojoin
    sysctl -w net.ipv6.conf.eth0.disable_ipv6=1
    for i in $(seq 1 $n); do
            ip link set up eth0; ip link set down eth0
    done
    
    Joining groups with IPV6_ADD_MEMBERSHIP (unprivileged) or setting the
    sysctl net.ipv6.conf.eth0.forwarding to 1 (=> subscribing to ff02::2)
    can also be used to create a nontrivial idev->mc_list, which will the
    leak objects with the right up-down-sequence.
    
    Based on both sources for NETDEV_DOWN events the interface IPv6 state
    should be considered:
    
     - not ready if the network interface is not ready OR IPv6 is disabled
       for it
     - ready if the network interface is ready AND IPv6 is enabled for it
    
    The functions ipv6_mc_up() and ipv6_down() should only be run when this
    state changes.
    
    Implement this by remembering when the IPv6 state is ready, and only
    run ipv6_mc_down() if it actually changed from ready to not ready.
    
    The other direction (not ready -> ready) already works correctly, as:
    
     - the interface notification triggered codepath for NETDEV_UP /
       NETDEV_CHANGE returns early if ipv6 is disabled, and
     - the disable_ipv6=0 triggered codepath skips fully initializing the
       interface as long as addrconf_link_ready(dev) returns false
     - calling ipv6_mc_up() repeatedly does not leak anything
    
    Fixes: 3ce62a84d53c ("ipv6: exit early in addrconf_notify() if IPv6 is disabled")
    Signed-off-by: Johannes Nixdorf <j.nixdorf@avm.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 258dd902022cb10c83671176688074879517fd21
Author: Jann Horn <jannh@google.com>
Date:   Fri Feb 18 19:05:59 2022 +0100

    efivars: Respect "block" flag in efivar_entry_set_safe()
    
    When the "block" flag is false, the old code would sometimes still call
    check_var_size(), which wrongly tells ->query_variable_store() that it can
    block.
    
    As far as I can tell, this can't really materialize as a bug at the moment,
    because ->query_variable_store only does something on X86 with generic EFI,
    and in that configuration we always take the efivar_entry_set_nonblocking()
    path.
    
    Fixes: ca0e30dcaa53 ("efi: Add nonblocking option to efi_query_variable_store()")
    Signed-off-by: Jann Horn <jannh@google.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Link: https://lore.kernel.org/r/20220218180559.1432559-1-jannh@google.com

commit dcf0c838854c86e1f41fb1934aea906845d69782
Author: Sunil V L <sunilvl@ventanamicro.com>
Date:   Fri Jan 28 10:20:04 2022 +0530

    riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value
    
    The get_boot_hartid_from_fdt() function currently returns U32_MAX
    for failure case which is not correct because U32_MAX is a valid
    hartid value. This patch fixes the issue by returning error code.
    
    Cc: <stable@vger.kernel.org>
    Fixes: d7071743db31 ("RISC-V: Add EFI stub support.")
    Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
    Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

commit ba115adf61b36b8c167126425a62b0efc23f72c0
Author: David Gow <davidgow@google.com>
Date:   Sun Feb 27 21:00:10 2022 -0800

    Input: samsung-keypad - properly state IOMEM dependency
    
    Make the samsung-keypad driver explicitly depend on CONFIG_HAS_IOMEM, as it
    calls devm_ioremap(). This prevents compile errors in some configs (e.g,
    allyesconfig/randconfig under UML):
    
    /usr/bin/ld: drivers/input/keyboard/samsung-keypad.o: in function `samsung_keypad_probe':
    samsung-keypad.c:(.text+0xc60): undefined reference to `devm_ioremap'
    
    Signed-off-by: David Gow <davidgow@google.com>
    Acked-by: anton ivanov <anton.ivanov@cambridgegreys.com>
    Link: https://lore.kernel.org/r/20220225041727.1902850-1-davidgow@google.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit e7c470a4b543375d50d88a4c5abd4b9e0f5adcea
Merge: 7e57714cd0ad2 4188db23285e2
Author: Dave Airlie <airlied@redhat.com>
Date:   Mon Feb 28 14:05:39 2022 +1000

    Merge tag 'exynos-drm-fixes-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-fixes
    
    Fixups
    - Make display controller drivers for Exynos series to use
      platform_get_irq and platform_get_irq_byname functions
      to get the interrupt, which prevents irq chaning from messed up
      when using hierarchical interrupt domains which use "interrupts"
      property in the node.
    - Fix two regressions to TE-gpio handling.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Inki Dae <inki.dae@samsung.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220225014042.17637-1-inki.dae@samsung.com

commit 7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 27 14:36:33 2022 -0800

    Linux 5.17-rc6

commit 52a02554673122486ecb36c36387d91cf9544986
Merge: 98f3e84f8df66 ba1366f3d039e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 27 13:07:40 2022 -0800

    Merge tag 'irq-urgent-2022-02-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq fix from Thomas Gleixner:
     "A single fix for a regression caused by the recent PCI/MSI rework
      which resulted in a recursive locking problem in the VMD driver.
    
      The cure is to cache the relevant information upfront instead of
      retrieving it at runtime"
    
    * tag 'irq-urgent-2022-02-27' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      PCI: vmd: Prevent recursive locking on interrupt allocation

commit 98f3e84f8df66f1ac9d04b6d8093993c9bfd69e6
Merge: 6676ba2a6df68 ddbd89deb7d32
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 27 12:42:37 2022 -0800

    Merge tag 'dma-mapping-5.17-1' of git://git.infradead.org/users/hch/dma-mapping
    
    Pull dma-mapping fix from Christoph Hellwig:
    
     - fix a swiotlb info leak (Halil Pasic)
    
    * tag 'dma-mapping-5.17-1' of git://git.infradead.org/users/hch/dma-mapping:
      swiotlb: fix info leak with DMA_FROM_DEVICE

commit 6676ba2a6df6864a6b7b11f20166026e2201b627
Merge: 2293be58d6a18 486c2d15aa812
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 27 12:30:54 2022 -0800

    Merge tag 'pinctrl-v5-17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
    
    Pull pin control fixes from Linus Walleij:
    
     - Fix some drive strength and pull-up code in the K210 driver.
    
     - Add the Alder Lake-M ACPI ID so it starts to work properly.
    
     - Use a static name for the StarFive GPIO irq_chip, forestalling an
       upcoming fixes series from Marc Zyngier.
    
     - Fix an ages old bug in the Tegra 186 driver where we were indexing at
       random into struct and being lucky getting the right member.
    
    * tag 'pinctrl-v5-17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
      gpio: tegra186: Fix chip_data type confusion
      pinctrl: starfive: Use a static name for the GPIO irq_chip
      pinctrl: tigerlake: Revert "Add Alder Lake-M ACPI ID"
      pinctrl: k210: Fix bias-pull-up
      pinctrl: fix loop in k210_pinconf_get_drive()

commit 2293be58d6a18cab800e25e42081bacb75c05752
Merge: e41898d2ba51e 90f59ee41abf5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 26 12:10:17 2022 -0800

    Merge tag 'trace-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing fixes from Steven Rostedt:
    
     - rtla (Real-Time Linux Analysis tool):
        - fix typo in man page
        - Update API -e to -E before it is released
        - Error message fix and memory leak fix
    
     - Partially uninline trace event soft disable to shrink text
    
     - Fix function graph start up test
    
     - Have triggers affect the trace instance they are in and not top level
    
     - Have osnoise sleep in the units it says it uses
    
     - Remove unused ftrace stub function
    
     - Remove event probe redundant info from event in the buffer
    
     - Fix group ownership setting in tracefs
    
     - Ensure trace buffer is minimum size to prevent crashes
    
    * tag 'trace-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      rtla/osnoise: Fix error message when failing to enable trace instance
      rtla/osnoise: Free params at the exit
      rtla/hist: Make -E the short version of --entries
      tracing: Fix selftest config check for function graph start up test
      tracefs: Set the group ownership in apply_options() not parse_options()
      tracing/osnoise: Make osnoise_main to sleep for microseconds
      ftrace: Remove unused ftrace_startup_enable() stub
      tracing: Ensure trace buffer is at least 4096 bytes large
      tracing: Uninline trace_trigger_soft_disabled() partly
      eprobes: Remove redundant event type information
      tracing: Have traceon and traceoff trigger honor the instance
      tracing: Dump stacktrace trigger to the corresponding instance
      rtla: Fix systme -> system typo on man page

commit e41898d2ba51ef2e8e81fb905c1eaa958aec830a
Merge: 086ee11b0384c c94afc46cae7a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 26 12:00:44 2022 -0800

    Merge tag 'fixes-2022-02-26' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
    
    Pull memblock fix from Mike Rapoport:
     "Use kfree() to release kmalloced memblock regions
    
      memblock.{reserved,memory}.regions may be allocated using kmalloc()
      in memblock_double_array(). Use kfree() to release these kmalloced
      regions"
    
    * tag 'fixes-2022-02-26' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock:
      memblock: use kfree() to release kmalloced memblock regions

commit 086ee11b0384c5ee837a46fac36e38189717960b
Merge: 2c8c230edab57 fda153c89af34
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 26 11:52:14 2022 -0800

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "12 patches.
    
      Subsystems affected by this patch series: MAINTAINERS, mailmap, memfd,
      and mm (hugetlb, kasan, hugetlbfs, pagemap, selftests, memcg, and
      slab)"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      selftests/memfd: clean up mapping in mfd_fail_write
      mailmap: update Roman Gushchin's email
      MAINTAINERS, SLAB: add Roman as reviewer, git tree
      MAINTAINERS: add Shakeel as a memcg co-maintainer
      MAINTAINERS: remove Vladimir from memcg maintainers
      MAINTAINERS: add Roman as a memcg co-maintainer
      selftest/vm: fix map_fixed_noreplace test failure
      mm: fix use-after-free bug when mm->mmap is reused after being freed
      hugetlbfs: fix a truncation issue in hugepages parameter
      kasan: test: prevent cache merging in kmem_cache_double_destroy
      mm/hugetlb: fix kernel crash with hugetlb mremap
      MAINTAINERS: add sysctl-next git tree

commit 2c8c230edab57eae6d2e8df7239ef121a45a1443
Merge: 3bd9dd813820a 22e2100b1b07d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 26 10:26:24 2022 -0800

    Merge tag 'riscv-for-linus-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V fixes from Palmer Dabbelt:
    
     - A fix for the K210 sdcard defconfig, to avoid using a
       fixed delay for the root FS
    
     - A fix to make sure there's a proper call frame for
       trace_hardirqs_{on,off}().
    
    * tag 'riscv-for-linus-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
      riscv: fix oops caused by irqsoff latency tracer
      riscv: fix nommu_k210_sdcard_defconfig

commit 3bd9dd813820a258fdd7df5444b550b2b1a71db6
Merge: 9137eda53752e b97cca3ba9098
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 26 09:53:19 2022 -0800

    Merge tag 'xfs-5.17-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs fixes from Darrick Wong:
     "Nothing exciting, just more fixes for not returning sync_filesystem
      error values (and eliding it when it's not necessary).
    
      Summary:
    
       - Only call sync_filesystem when we're remounting the filesystem
         readonly readonly, and actually check its return value"
    
    * tag 'xfs-5.17-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: only bother with sync_filesystem during readonly remount

commit fda153c89af344d21df281009a9d046cf587ea0f
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date:   Fri Feb 25 19:11:26 2022 -0800

    selftests/memfd: clean up mapping in mfd_fail_write
    
    Running the memfd script ./run_hugetlbfs_test.sh will often end in error
    as follows:
    
        memfd-hugetlb: CREATE
        memfd-hugetlb: BASIC
        memfd-hugetlb: SEAL-WRITE
        memfd-hugetlb: SEAL-FUTURE-WRITE
        memfd-hugetlb: SEAL-SHRINK
        fallocate(ALLOC) failed: No space left on device
        ./run_hugetlbfs_test.sh: line 60: 166855 Aborted                 (core dumped) ./memfd_test hugetlbfs
        opening: ./mnt/memfd
        fuse: DONE
    
    If no hugetlb pages have been preallocated, run_hugetlbfs_test.sh will
    allocate 'just enough' pages to run the test.  In the SEAL-FUTURE-WRITE
    test the mfd_fail_write routine maps the file, but does not unmap.  As a
    result, two hugetlb pages remain reserved for the mapping.  When the
    fallocate call in the SEAL-SHRINK test attempts allocate all hugetlb
    pages, it is short by the two reserved pages.
    
    Fix by making sure to unmap in mfd_fail_write.
    
    Link: https://lkml.kernel.org/r/20220219004340.56478-1-mike.kravetz@oracle.com
    Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Joel Fernandes <joel@joelfernandes.org>
    Cc: Shuah Khan <shuah@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9502bdbf34e4ffe865d144fe4218eb64602a75bd
Author: Roman Gushchin <roman.gushchin@linux.dev>
Date:   Fri Feb 25 19:11:23 2022 -0800

    mailmap: update Roman Gushchin's email
    
    I'm moving to a @linux.dev account. Map my old addresses.
    
    Link: https://lkml.kernel.org/r/20220221200006.416377-1-roman.gushchin@linux.dev
    Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7b0112f3432915fd6ac68ddd61bc4bcd1ac2505d
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Fri Feb 25 19:11:20 2022 -0800

    MAINTAINERS, SLAB: add Roman as reviewer, git tree
    
    The slab code has an overlap with kmem accounting, where Roman has done
    a lot of work recently and it would be useful to make sure he's CC'd on
    patches that potentially affect it.  Thus add him as a reviewer for the
    SLAB subsystem.
    
    Also while at it, add the link to slab git tree.
    
    Link: https://lkml.kernel.org/r/20220222103104.13241-1-vbabka@suse.cz
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: David Rientjes <rientjes@google.com>
    Acked-by: Roman Gushchin <roman.gushchin@linux.dev>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bb9d5454992322a0b793c655e1d860a54a38a3d3
Author: Shakeel Butt <shakeelb@google.com>
Date:   Fri Feb 25 19:11:17 2022 -0800

    MAINTAINERS: add Shakeel as a memcg co-maintainer
    
    I have been contributing and reviewing to the memcg codebase for last
    couple of years.  So, making it official.
    
    Link: https://lkml.kernel.org/r/20220224060148.4092228-1-shakeelb@google.com
    Signed-off-by: Shakeel Butt <shakeelb@google.com>
    Acked-by: Roman Gushchin <roman.gushchin@linux.dev>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0a972e72e2f9630b10bf6b7b5e08312e87eb6854
Author: Vladimir Davydov <vdavydov.dev@gmail.com>
Date:   Fri Feb 25 19:11:14 2022 -0800

    MAINTAINERS: remove Vladimir from memcg maintainers
    
    Link: https://lkml.kernel.org/r/4ad1f8da49d7b71c84a0c15bd5347f5ce704e730.1645608825.git.vdavydov.dev@gmail.com
    Signed-off-by: Vladimir Davydov <vdavydov.dev@gmail.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Roman Gushchin <roman.gushchin@linux.dev>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7d547dcf97f275e9f507c8099e168ed682fe1257
Author: Roman Gushchin <roman.gushchin@linux.dev>
Date:   Fri Feb 25 19:11:11 2022 -0800

    MAINTAINERS: add Roman as a memcg co-maintainer
    
    Add myself as a memcg co-maintainer.  My primary focus over last few
    years was the kernel memory accounting stack, but I do work on some
    other parts of the memory controller as well.
    
    Link: https://lkml.kernel.org/r/20220221233951.659048-1-roman.gushchin@linux.dev
    Signed-off-by: Roman Gushchin <roman.gushchin@linux.dev>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f39c58008dee7ab5fc94c3f1995a21e886801df0
Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Date:   Fri Feb 25 19:11:08 2022 -0800

    selftest/vm: fix map_fixed_noreplace test failure
    
    On the latest RHEL the test fails due to executable mapped at 256MB
    address
    
         # ./map_fixed_noreplace
        mmap() @ 0x10000000-0x10050000 p=0xffffffffffffffff result=File exists
        10000000-10010000 r-xp 00000000 fd:04 34905657                           /root/rpmbuild/BUILD/kernel-5.14.0-56.el9/linux-5.14.0-56.el9.ppc64le/tools/testing/selftests/vm/map_fixed_noreplace
        10010000-10020000 r--p 00000000 fd:04 34905657                           /root/rpmbuild/BUILD/kernel-5.14.0-56.el9/linux-5.14.0-56.el9.ppc64le/tools/testing/selftests/vm/map_fixed_noreplace
        10020000-10030000 rw-p 00010000 fd:04 34905657                           /root/rpmbuild/BUILD/kernel-5.14.0-56.el9/linux-5.14.0-56.el9.ppc64le/tools/testing/selftests/vm/map_fixed_noreplace
        10029b90000-10029bc0000 rw-p 00000000 00:00 0                            [heap]
        7fffbb510000-7fffbb750000 r-xp 00000000 fd:04 24534                      /usr/lib64/libc.so.6
        7fffbb750000-7fffbb760000 r--p 00230000 fd:04 24534                      /usr/lib64/libc.so.6
        7fffbb760000-7fffbb770000 rw-p 00240000 fd:04 24534                      /usr/lib64/libc.so.6
        7fffbb780000-7fffbb7a0000 r--p 00000000 00:00 0                          [vvar]
        7fffbb7a0000-7fffbb7b0000 r-xp 00000000 00:00 0                          [vdso]
        7fffbb7b0000-7fffbb800000 r-xp 00000000 fd:04 24514                      /usr/lib64/ld64.so.2
        7fffbb800000-7fffbb810000 r--p 00040000 fd:04 24514                      /usr/lib64/ld64.so.2
        7fffbb810000-7fffbb820000 rw-p 00050000 fd:04 24514                      /usr/lib64/ld64.so.2
        7fffd93f0000-7fffd9420000 rw-p 00000000 00:00 0                          [stack]
        Error: couldn't map the space we need for the test
    
    Fix this by finding a free address using mmap instead of hardcoding
    BASE_ADDRESS.
    
    Link: https://lkml.kernel.org/r/20220217083417.373823-1-aneesh.kumar@linux.ibm.com
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Jann Horn <jannh@google.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f798a1d4f94de9510e060d37b9b47721065a957c
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Feb 25 19:11:05 2022 -0800

    mm: fix use-after-free bug when mm->mmap is reused after being freed
    
    oom reaping (__oom_reap_task_mm) relies on a 2 way synchronization with
    exit_mmap.  First it relies on the mmap_lock to exclude from unlock
    path[1], page tables tear down (free_pgtables) and vma destruction.
    This alone is not sufficient because mm->mmap is never reset.
    
    For historical reasons[2] the lock is taken there is also MMF_OOM_SKIP
    set for oom victims before.
    
    The oom reaper only ever looks at oom victims so the whole scheme works
    properly but process_mrelease can opearate on any task (with fatal
    signals pending) which doesn't really imply oom victims.  That means
    that the MMF_OOM_SKIP part of the synchronization doesn't work and it
    can see a task after the whole address space has been demolished and
    traverse an already released mm->mmap list.  This leads to use after
    free as properly caught up by KASAN report.
    
    Fix the issue by reseting mm->mmap so that MMF_OOM_SKIP synchronization
    is not needed anymore.  The MMF_OOM_SKIP is not removed from exit_mmap
    yet but it acts mostly as an optimization now.
    
    [1] 27ae357fa82b ("mm, oom: fix concurrent munlock and oom reaper unmap, v3")
    [2] 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run concurrently")
    
    [mhocko@suse.com: changelog rewrite]
    
    Link: https://lore.kernel.org/all/00000000000072ef2c05d7f81950@google.com/
    Link: https://lkml.kernel.org/r/20220215201922.1908156-1-surenb@google.com
    Fixes: 64591e8605d6 ("mm: protect free_pgtables with mmap_lock write lock in exit_mmap")
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reported-by: syzbot+2ccf63a4bd07cf39cab0@syzkaller.appspotmail.com
    Suggested-by: Michal Hocko <mhocko@suse.com>
    Reviewed-by: Rik van Riel <riel@surriel.com>
    Reviewed-by: Yang Shi <shy828301@gmail.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Roman Gushchin <roman.gushchin@linux.dev>
    Cc: Rik van Riel <riel@surriel.com>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Christian Brauner <brauner@kernel.org>
    Cc: Christoph Hellwig <hch@infradead.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Jann Horn <jannh@google.com>
    Cc: Shakeel Butt <shakeelb@google.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Florian Weimer <fweimer@redhat.com>
    Cc: Jan Engelhardt <jengelh@inai.de>
    Cc: Tim Murray <timmurray@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e79ce9832316e09529b212a21278d68240ccbf1f
Author: Liu Yuntao <liuyuntao10@huawei.com>
Date:   Fri Feb 25 19:11:02 2022 -0800

    hugetlbfs: fix a truncation issue in hugepages parameter
    
    When we specify a large number for node in hugepages parameter, it may
    be parsed to another number due to truncation in this statement:
    
            node = tmp;
    
    For example, add following parameter in command line:
    
            hugepagesz=1G hugepages=4294967297:5
    
    and kernel will allocate 5 hugepages for node 1 instead of ignoring it.
    
    I move the validation check earlier to fix this issue, and slightly
    simplifies the condition here.
    
    Link: https://lkml.kernel.org/r/20220209134018.8242-1-liuyuntao10@huawei.com
    Fixes: b5389086ad7be0 ("hugetlbfs: extend the definition of hugepages parameter to support node allocation")
    Signed-off-by: Liu Yuntao <liuyuntao10@huawei.com>
    Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 70effdc3756c924f4a2b6af1ec4e2e92e18e1b45
Author: Andrey Konovalov <andreyknvl@gmail.com>
Date:   Fri Feb 25 19:10:59 2022 -0800

    kasan: test: prevent cache merging in kmem_cache_double_destroy
    
    With HW_TAGS KASAN and kasan.stacktrace=off, the cache created in the
    kmem_cache_double_destroy() test might get merged with an existing one.
    Thus, the first kmem_cache_destroy() call won't actually destroy it but
    will only decrease the refcount.  This causes the test to fail.
    
    Provide an empty constructor for the created cache to prevent the cache
    from getting merged.
    
    Link: https://lkml.kernel.org/r/b597bd434c49591d8af00ee3993a42c609dc9a59.1644346040.git.andreyknvl@google.com
    Fixes: f98f966cd750 ("kasan: test: add test case for double-kmem_cache_destroy()")
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
    Reviewed-by: Marco Elver <elver@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit db110a99d3367936058727ff4798e3a39c707969
Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Date:   Fri Feb 25 19:10:56 2022 -0800

    mm/hugetlb: fix kernel crash with hugetlb mremap
    
    This fixes the below crash:
    
      kernel BUG at include/linux/mm.h:2373!
      cpu 0x5d: Vector: 700 (Program Check) at [c00000003c6e76e0]
          pc: c000000000581a54: pmd_to_page+0x54/0x80
          lr: c00000000058d184: move_hugetlb_page_tables+0x4e4/0x5b0
          sp: c00000003c6e7980
         msr: 9000000000029033
        current = 0xc00000003bd8d980
        paca    = 0xc000200fff610100   irqmask: 0x03   irq_happened: 0x01
          pid   = 9349, comm = hugepage-mremap
      kernel BUG at include/linux/mm.h:2373!
        move_hugetlb_page_tables+0x4e4/0x5b0 (link register)
        move_hugetlb_page_tables+0x22c/0x5b0 (unreliable)
        move_page_tables+0xdbc/0x1010
        move_vma+0x254/0x5f0
        sys_mremap+0x7c0/0x900
        system_call_exception+0x160/0x2c0
    
    the kernel can't use huge_pte_offset before it set the pte entry because
    a page table lookup check for huge PTE bit in the page table to
    differentiate between a huge pte entry and a pointer to pte page.  A
    huge_pte_alloc won't mark the page table entry huge and hence kernel
    should not use huge_pte_offset after a huge_pte_alloc.
    
    Link: https://lkml.kernel.org/r/20220211063221.99293-1-aneesh.kumar@linux.ibm.com
    Fixes: 550a7d60bd5e ("mm, hugepages: add mremap() support for hugepage backed vma")
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
    Reviewed-by: Mina Almasry <almasrymina@google.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bbcf7b0e2e4b8376ef4b401777f2852302c745e3
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Feb 25 19:10:53 2022 -0800

    MAINTAINERS: add sysctl-next git tree
    
    Add a git tree for sysctls as there's been quite a bit of work lately to
    remove all the syctls out of kernel/sysctl.c and move to their respective
    places, so coordination has been needed to avoid conflicts.  This tree
    will also help soak these changes on linux-next prior to getting to Linus.
    
    Link: https://lkml.kernel.org/r/20220218182736.3694508-1-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 519ca6fa960587d02904a9f8f79d587ac874fb03
Merge: 328e765c03737 14756b2ae265d
Author: David S. Miller <davem@davemloft.net>
Date:   Sat Feb 26 12:50:20 2022 +0000

    Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-02-25
    
    This series contains updates to iavf driver only.
    
    Slawomir fixes stability issues that can be seen when stressing the
    driver using a large number of VFs with a multitude of operations.
    Among the fixes are reworking mutexes to provide more effective locking,
    ensuring initialization is complete before teardown, preventing
    operations which could race while removing the driver, stopping certain
    tasks from being queued when the device is down, and adding a missing
    mutex unlock.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 90f59ee41abf587ad4675a70434136c8707fdf4b
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 18 18:57:09 2022 +0100

    rtla/osnoise: Fix error message when failing to enable trace instance
    
    When a trace instance creation fails, tools are printing:
    
            Could not enable -> osnoiser <- tracer for tracing
    
    Print the actual (and correct) name of the tracer it fails to enable.
    
    Link: https://lkml.kernel.org/r/53ef0582605af91eca14b19dba9fc9febb95d4f9.1645206561.git.bristot@kernel.org
    
    Fixes: b1696371d865 ("rtla: Helper functions for rtla")
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 316f710172461c501f9b73f3b2fc7ce8aa5b84a5
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 18 18:57:08 2022 +0100

    rtla/osnoise: Free params at the exit
    
    The variable that stores the parsed command line arguments are not
    being free()d at the rtla osnoise top exit path.
    
    Free params variable before exiting.
    
    Link: https://lkml.kernel.org/r/0be31d8259c7c53b98a39769d60cfeecd8421785.1645206561.git.bristot@kernel.org
    
    Fixes: 1eceb2fc2ca5 ("rtla/osnoise: Add osnoise top mode")
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit dd48f316a1216fa10f9ba26852457794417d9bc6
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 18 18:57:07 2022 +0100

    rtla/hist: Make -E the short version of --entries
    
    Currently, --entries uses -e as the short version in the hist mode of
    timerlat and osnoise tools. But as -e is already used to enable events
    on trace sessions by other tools, thus let's keep it available for the
    same usage for all rtla tools.
    
    Make -E the short version of --entries for hist mode on all tools.
    
    Note: rtla was merged in this merge window, so rtla was not released yet.
    
    Link: https://lkml.kernel.org/r/5dbf0cbe7364d3a05e708926b41a097c59a02b1e.1645206561.git.bristot@kernel.org
    
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit c5229a0bd47814770c895e94fbc97ad21819abfe
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Mon Dec 20 16:38:06 2021 +0000

    tracing: Fix selftest config check for function graph start up test
    
    CONFIG_DYNAMIC_FTRACE_WITH_DIRECT_CALLS is required to test
    direct tramp.
    
    Link: https://lkml.kernel.org/r/bdc7e594e13b0891c1d61bc8d56c94b1890eaed7.1640017960.git.christophe.leroy@csgroup.eu
    
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 851e99ebeec3f4a672bb5010cf1ece095acee447
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Fri Feb 25 15:34:26 2022 -0500

    tracefs: Set the group ownership in apply_options() not parse_options()
    
    Al Viro brought it to my attention that the dentries may not be filled
    when the parse_options() is called, causing the call to set_gid() to
    possibly crash. It should only be called if parse_options() succeeds
    totally anyway.
    
    He suggested the logical place to do the update is in apply_options().
    
    Link: https://lore.kernel.org/all/20220225165219.737025658@goodmis.org/
    Link: https://lkml.kernel.org/r/20220225153426.1c4cab6b@gandalf.local.home
    
    Cc: stable@vger.kernel.org
    Acked-by: Al Viro <viro@zeniv.linux.org.uk>
    Reported-by: Al Viro <viro@zeniv.linux.org.uk>
    Fixes: 48b27b6b5191 ("tracefs: Set all files to the same group ownership as the mount option")
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 328e765c03737ec36d0cc9eabc445fc605070ef6
Merge: e01b042e580f1 c5048a7b2c23a
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Feb 25 14:53:58 2022 -0800

    Merge tag 'linux-can-fixes-for-5.17-20220225' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can
    
    Marc Kleine-Budde says:
    
    ====================
    pull-request: can 2022-02-25
    
    The first 2 patches are by Vincent Mailhol and fix the error handling
    of the ndo_open callbacks of the etas_es58x and the gs_usb CAN USB
    drivers.
    
    The last patch is by Lad Prabhakar and fixes a small race condition in
    the rcar_canfd's rcar_canfd_channel_probe() function.
    
    * tag 'linux-can-fixes-for-5.17-20220225' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can:
      can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready
      can: gs_usb: change active_channels's type from atomic_t to u8
      can: etas_es58x: change opened_channel_cnt's type from atomic_t to u8
    ====================
    
    Link: https://lore.kernel.org/r/20220225165622.3231809-1-mkl@pengutronix.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9137eda53752ef73148e42b0d7640a00f1bc96b1
Merge: c0419188b5c1a 84ec758fb2daa
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 14:12:36 2022 -0800

    Merge tag 'configfs-5.17-2022-02-25' of git://git.infradead.org/users/hch/configfs
    
    Pull configfs fix from Christoph Hellwig:
    
     - fix a race in configfs_{,un}register_subsystem (ChenXiaoSong)
    
    * tag 'configfs-5.17-2022-02-25' of git://git.infradead.org/users/hch/configfs:
      configfs: fix a race in configfs_{,un}register_subsystem()

commit c0419188b5c1a7735b12cf1405cafc3f8d722819
Merge: ca7457236d47d 558732df21220
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 14:08:03 2022 -0800

    Merge tag 'for-5.17-rc5-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs fixes from David Sterba:
     "This is a hopefully last batch of fixes for defrag that got broken in
      5.16, all stable material.
    
      The remaining reported problem is excessive IO with autodefrag due to
      various conditions in the defrag code not met or missing"
    
    * tag 'for-5.17-rc5-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
      btrfs: reduce extent threshold for autodefrag
      btrfs: autodefrag: only scan one inode once
      btrfs: defrag: don't use merged extent map for their generation check
      btrfs: defrag: bring back the old file extent search behavior
      btrfs: defrag: remove an ambiguous condition for rejection
      btrfs: defrag: don't defrag extents which are already at max capacity
      btrfs: defrag: don't try to merge regular extents with preallocated extents
      btrfs: defrag: allow defrag_one_cluster() to skip large extent which is not a target
      btrfs: prevent copying too big compressed lzo segment

commit ca7457236d47d8748bdb6b423d148726220ec3d8
Merge: 115ccd2278cca 22e9f71072fa6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 13:34:30 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
    
    Pull rdma fixes from Jason Gunthorpe:
    
     - Older "does not even boot" regression in qib from July
    
     - Bug fixes for error unwind in rtrs
    
     - Avoid a deadlock syzkaller found in srp
    
     - Fix another UAF syzkaller found in cma
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma:
      RDMA/cma: Do not change route.addr.src_addr outside state checks
      RDMA/ib_srp: Fix a deadlock
      RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
      RDMA/rtrs-clt: Fix possible double free in error case
      IB/qib: Fix duplicate sysfs directory name

commit 115ccd2278ccaa882000a20cb81a3649ef7dfe8b
Merge: 4b23c6ecefcc9 ae42f92888463
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:56:11 2022 -0800

    Merge tag 'gpio-fixes-for-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio fixes from Bartosz Golaszewski:
    
     - fix an bug generating spurious interrupts in gpio-rockchip
    
     - fix a race condition in gpiod_to_irq() called by GPIO consumers
    
    * tag 'gpio-fixes-for-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:
      gpio: Return EPROBE_DEFER if gc->to_irq is NULL
      gpio: rockchip: Reset int_bothedge when changing trigger

commit 22e9f71072fa605cbf033158db58e0790101928d
Author: Jason Gunthorpe <jgg@ziepe.ca>
Date:   Wed Feb 23 11:23:57 2022 -0400

    RDMA/cma: Do not change route.addr.src_addr outside state checks
    
    If the state is not idle then resolve_prepare_src() should immediately
    fail and no change to global state should happen. However, it
    unconditionally overwrites the src_addr trying to build a temporary any
    address.
    
    For instance if the state is already RDMA_CM_LISTEN then this will corrupt
    the src_addr and would cause the test in cma_cancel_operation():
    
               if (cma_any_addr(cma_src_addr(id_priv)) && !id_priv->cma_dev)
    
    Which would manifest as this trace from syzkaller:
    
      BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26
      Read of size 8 at addr ffff8881546491e0 by task syz-executor.1/32204
    
      CPU: 1 PID: 32204 Comm: syz-executor.1 Not tainted 5.12.0-rc8-syzkaller #0
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
      Call Trace:
       __dump_stack lib/dump_stack.c:79 [inline]
       dump_stack+0x141/0x1d7 lib/dump_stack.c:120
       print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:232
       __kasan_report mm/kasan/report.c:399 [inline]
       kasan_report.cold+0x7c/0xd8 mm/kasan/report.c:416
       __list_add_valid+0x93/0xa0 lib/list_debug.c:26
       __list_add include/linux/list.h:67 [inline]
       list_add_tail include/linux/list.h:100 [inline]
       cma_listen_on_all drivers/infiniband/core/cma.c:2557 [inline]
       rdma_listen+0x787/0xe00 drivers/infiniband/core/cma.c:3751
       ucma_listen+0x16a/0x210 drivers/infiniband/core/ucma.c:1102
       ucma_write+0x259/0x350 drivers/infiniband/core/ucma.c:1732
       vfs_write+0x28e/0xa30 fs/read_write.c:603
       ksys_write+0x1ee/0x250 fs/read_write.c:658
       do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
       entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    This is indicating that an rdma_id_private was destroyed without doing
    cma_cancel_listens().
    
    Instead of trying to re-use the src_addr memory to indirectly create an
    any address derived from the dst build one explicitly on the stack and
    bind to that as any other normal flow would do. rdma_bind_addr() will copy
    it over the src_addr once it knows the state is valid.
    
    This is similar to commit bc0bdc5afaa7 ("RDMA/cma: Do not change
    route.addr.src_addr.ss_family")
    
    Link: https://lore.kernel.org/r/0-v2-e975c8fd9ef2+11e-syz_cma_srcaddr_jgg@nvidia.com
    Cc: stable@vger.kernel.org
    Fixes: 732d41c545bb ("RDMA/cma: Make the locking for automatic state transition more clear")
    Reported-by: syzbot+c94a3675a626f6333d74@syzkaller.appspotmail.com
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 4b23c6ecefcc9c15ae3d2f09d529151ab214b97f
Merge: 64b5132b897ca 80808768e4132
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:37:41 2022 -0800

    Merge tag 'spi-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
    
    Pull spi fixes from Mark Brown:
     "A few small driver specific fixes"
    
    * tag 'spi-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi:
      spi: rockchip: terminate dma transmission when slave abort
      spi: rockchip: Fix error in getting num-cs property
      spi: spi-zynq-qspi: Fix a NULL pointer dereference in zynq_qspi_exec_mem_op()

commit 64b5132b897caeb4188fcbafd46fd73dc96be4a8
Merge: 0e9894e6aac2c 9c7cf33c53ce8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:33:51 2022 -0800

    Merge tag 'regulator-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
    
    Pull regulator fixes from Mark Brown:
     "A series of fixes for the da9121 driver"
    
    * tag 'regulator-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:
      regulator: da9121: Remove surplus DA9141 parameters
      regulator: da9121: Fix DA914x voltage value
      regulator: da9121: Fix DA914x current values

commit 0e9894e6aac2c591da00dae91c448c02d1ca6373
Merge: e48cb5c2c65db d04ad245d67a3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:30:01 2022 -0800

    Merge tag 'regmap-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap
    
    Pull regmap fix from Mark Brown:
     "A fix for interrupt controllers which require the explicit
      acknowledgement of interrupts using a different register to the one
      where interrupts are reported.
    
      Urgent for the few devices this affects"
    
    * tag 'regmap-fix-v5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap:
      regmap-irq: Update interrupt clear register for proper reset

commit e48cb5c2c65db87cf1269ca004e111764da6cc74
Merge: 2800b6d0fc390 3abea10e6a8f0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:25:44 2022 -0800

    Merge tag 'thermal-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull thermal control fix from Rafael Wysocki:
     "Fix a memory leak in the int340x thermal driver's ACPI notify handler
      (Chuansheng Liu)"
    
    * tag 'thermal-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      thermal: int340x: fix memory leak in int3400_notify()

commit 2800b6d0fc390d7c3f22109a408d5ed72746588c
Merge: c47658311d60b c5eb92f57de24
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:17:20 2022 -0800

    Merge tag 'pm-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull power management fixes from Rafael Wysocki:
     "Fix the throttle IRQ handling during cpufreq initialization on
      Qualcomm platforms (Bjorn Andersson)"
    
    * tag 'pm-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      cpufreq: qcom-hw: Delay enabling throttle_irq
      cpufreq: Reintroduce ready() callback

commit c47658311d60be064b839f329c0e4d34f5f0735b
Merge: d68ccfdbe5205 6c7621890995d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:12:06 2022 -0800

    Merge tag 'char-misc-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
    
    Pull char/misc driver fixes from Greg KH:
     "Here are a few small driver fixes for 5.17-rc6 for reported issues.
    
      The majority of these are IIO fixes for small things, and the other
      two are a mvmem and mtd core conflict fix.
    
      All of these have been in linux-next with no reported issues"
    
    * tag 'char-misc-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
      mtd: core: Fix a conflict between MTD and NVMEM on wp-gpios property
      nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property
      iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
      iio: Fix error handling for PM
      iio: addac: ad74413r: correct comparator gpio getters mask usage
      iio: addac: ad74413r: use ngpio size when iterating over mask
      iio: addac: ad74413r: Do not reference negative array offsets
      iio: adc: men_z188_adc: Fix a resource leak in an error handling path
      iio: frequency: admv1013: remove the always true condition
      iio: accel: fxls8962af: add padding to regmap for SPI
      iio:imu:adis16480: fix buffering for devices with no burst mode
      iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
      iio: adc: tsc2046: fix memory corruption by preventing array overflow

commit d68ccfdbe5205c746c6ad145c771a4db19fb8dc0
Merge: eae9350eb40aa d8f7a5484f218
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 12:05:40 2022 -0800

    Merge tag 'driver-core-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
    
    Pull driver core fix from Greg KH:
     "Here is a single driver core fix for 5.17-rc6. It resolves a reported
      problem when the DMA map of a device is not properly released.
    
      It has been in linux-next with no reported problems"
    
    * tag 'driver-core-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
      driver core: Free DMA range map when device is released

commit eae9350eb40aa0b07c280ab3a504bdc65c2211f1
Merge: d8fc3bb606d84 b6821b0d9b563
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 11:56:16 2022 -0800

    Merge tag 'staging-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
    
    Pull staging driver fix from Greg KH:
     "Here is a single staging driver fix for 5.17-rc6.
    
      It resolves a reported problem in the fbtft fb_st7789v.c driver that
      could cause the display to be flipped in cold weather.
    
      It has been in linux-next with no reported problems"
    
    * tag 'staging-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
      staging: fbtft: fb_st7789v: reset display before initialization

commit d8fc3bb606d84ddaf26e31231d848600ae0eccec
Merge: 548b1af45d1a1 eebb0f4e894f1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 11:45:29 2022 -0800

    Merge tag 'tty-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
    
    Pull tty/serial driver fixes from Greg KH:
     "Here are some small n_gsm and sc16is7xx serial driver fixes for
      5.17-rc6.
    
      The n_gsm fixes are from Siemens as it seems they are using the line
      discipline and fixing up a number of issues they found in their
      testing. The sc16is7xx serial driver fix is for a reported problem
      with that chip.
    
      All of these have been in linux-next with no reported problems"
    
    * tag 'tty-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
      sc16is7xx: Fix for incorrect data being transmitted
      tty: n_gsm: fix deadlock in gsmtty_open()
      tty: n_gsm: fix wrong modem processing in convergence layer type 2
      tty: n_gsm: fix wrong tty control line for flow control
      tty: n_gsm: fix NULL pointer access due to DLCI release
      tty: n_gsm: fix proper link termination after failed open
      tty: n_gsm: fix encoding of command/response bit
      tty: n_gsm: fix encoding of control signal octet bit DV

commit 14756b2ae265d526b8356e86729090b01778fdf6
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:38:55 2022 +0100

    iavf: Fix __IAVF_RESETTING state usage
    
    The setup of __IAVF_RESETTING state in watchdog task had no
    effect and could lead to slow resets in the driver as
    the task for __IAVF_RESETTING state only requeues watchdog.
    Till now the __IAVF_RESETTING was interpreted by reset task
    as running state which could lead to errors with allocating
    and resources disposal.
    
    Make watchdog_task queue the reset task when it's necessary.
    Do not update the state to __IAVF_RESETTING so the reset task
    knows exactly what is the current state of the adapter.
    
    Fixes: 898ef1cb1cb2 ("iavf: Combine init and watchdog state machines")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit d2c0f45fcceb0995f208c441d9c9a453623f9ccf
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:38:43 2022 +0100

    iavf: Fix missing check for running netdev
    
    The driver was queueing reset_task regardless of the netdev
    state.
    
    Do not queue the reset task in iavf_change_mtu if netdev
    is not running.
    
    Fixes: fdd4044ffdc8 ("iavf: Remove timer for work triggering, use delaying work instead")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit e85ff9c631e1bf109ce8428848dfc8e8b0041f48
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:38:31 2022 +0100

    iavf: Fix deadlock in iavf_reset_task
    
    There exists a missing mutex_unlock call on crit_lock in
    iavf_reset_task call path.
    
    Unlock the crit_lock before returning from reset task.
    
    Fixes: 5ac49f3c2702 ("iavf: use mutexes for locking of critical sections")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit a472eb5cbaebb5774672c565e024336c039e9128
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:38:01 2022 +0100

    iavf: Fix race in init state
    
    When iavf_init_version_check sends VIRTCHNL_OP_GET_VF_RESOURCES
    message, the driver will wait for the response after requeueing
    the watchdog task in iavf_init_get_resources call stack. The
    logic is implemented this way that iavf_init_get_resources has
    to be called in order to allocate adapter->vf_res. It is polling
    for the AQ response in iavf_get_vf_config function. Expect a
    call trace from kernel when adminq_task worker handles this
    message first. adapter->vf_res will be NULL in
    iavf_virtchnl_completion.
    
    Make the watchdog task not queue the adminq_task if the init
    process is not finished yet.
    
    Fixes: 898ef1cb1cb2 ("iavf: Combine init and watchdog state machines")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 0579fafd37fb7efe091f0e6c8ccf968864f40f3e
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:37:50 2022 +0100

    iavf: Fix locking for VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS
    
    iavf_virtchnl_completion is called under crit_lock but when
    the code for VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS is called,
    this lock is released in order to obtain rtnl_lock to avoid
    ABBA deadlock with unregister_netdev.
    
    Along with the new way iavf_remove behaves, there exist
    many risks related to the lock release and attmepts to regrab
    it. The driver faces crashes related to races between
    unregister_netdev and netdev_update_features. Yet another
    risk is that the driver could already obtain the crit_lock
    in order to destroy it and iavf_virtchnl_completion could
    crash or block forever.
    
    Make iavf_virtchnl_completion never relock crit_lock in it's
    call paths.
    
    Extract rtnl_lock locking logic to the driver for
    unregister_netdev in order to set the netdev_registered flag
    inside the lock.
    
    Introduce a new flag that will inform adminq_task to perform
    the code from VIRTCHNL_OP_GET_OFFLOAD_VLAN_V2_CAPS right after
    it finishes processing messages. Guard this code with remove
    flags so it's never called when the driver is in remove state.
    
    Fixes: 5951a2b9812d ("iavf: Fix VLAN feature flags after VFR")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 3ccd54ef44ebfa0792c5441b6d9c86618f3378d1
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:37:10 2022 +0100

    iavf: Fix init state closure on remove
    
    When init states of the adapter work, the errors like lack
    of communication with the PF might hop in. If such events
    occur the driver restores previous states in order to retry
    initialization in a proper way. When remove task kicks in,
    this situation could lead to races with unregistering the
    netdevice as well as resources cleanup. With the commit
    introducing the waiting in remove for init to complete,
    this problem turns into an endless waiting if init never
    recovers from errors.
    
    Introduce __IAVF_IN_REMOVE_TASK bit to indicate that the
    remove thread has started.
    
    Make __IAVF_COMM_FAILED adapter state respect the
    __IAVF_IN_REMOVE_TASK bit and set the __IAVF_INIT_FAILED
    state and return without any action instead of trying to
    recover.
    
    Make __IAVF_INIT_FAILED adapter state respect the
    __IAVF_IN_REMOVE_TASK bit and return without any further
    actions.
    
    Make the loop in the remove handler break when adapter has
    __IAVF_INIT_FAILED state set.
    
    Fixes: 898ef1cb1cb2 ("iavf: Combine init and watchdog state machines")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 974578017fc1fdd06cea8afb9dfa32602e8529ed
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:36:56 2022 +0100

    iavf: Add waiting so the port is initialized in remove
    
    There exist races when port is being configured and remove is
    triggered.
    
    unregister_netdev is not and can't be called under crit_lock
    mutex since it is calling ndo_stop -> iavf_close which requires
    this lock. Depending on init state the netdev could be still
    unregistered so unregister_netdev never cleans up, when shortly
    after that the device could become registered.
    
    Make iavf_remove wait until port finishes initialization.
    All critical state changes are atomic (under crit_lock).
    Crashes that come from iavf_reset_interrupt_capability and
    iavf_free_traffic_irqs should now be solved in a graceful
    manner.
    
    Fixes: 605ca7c5c6707 ("iavf: Fix kernel BUG in free_msi_irqs")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit fc2e6b3b132a907378f6af08356b105a4139c4fb
Author: Slawomir Laba <slawomirx.laba@intel.com>
Date:   Wed Feb 23 13:35:49 2022 +0100

    iavf: Rework mutexes for better synchronisation
    
    The driver used to crash in multiple spots when put to stress testing
    of the init, reset and remove paths.
    
    The user would experience call traces or hangs when creating,
    resetting, removing VFs. Depending on the machines, the call traces
    are happening in random spots, like reset restoring resources racing
    with driver remove.
    
    Make adapter->crit_lock mutex a mandatory lock for guarding the
    operations performed on all workqueues and functions dealing with
    resource allocation and disposal.
    
    Make __IAVF_REMOVE a final state of the driver respected by
    workqueues that shall not requeue, when they fail to obtain the
    crit_lock.
    
    Make the IRQ handler not to queue the new work for adminq_task
    when the __IAVF_REMOVE state is set.
    
    Fixes: 5ac49f3c2702 ("iavf: use mutexes for locking of critical sections")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Phani Burra <phani.r.burra@intel.com>
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 548b1af45d1a10a6e2a04255c29d06cc14c10870
Merge: 78081594971aa 19eae24b76c27
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 11:36:31 2022 -0800

    Merge tag 'usb-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
    
    Pull USB fixes from Greg KH:
     "Here are a number of small USB driver fixes for 5.17-rc6 to resolve
      reported problems and add new device ids. They include:
    
       - dwc3:
          - device mapping fix
          - new device ids
          - driver fixes
    
       - xhci driver fixes
    
       - gadget driver fixes
    
       - usb-serial driver device id updates
    
      All of these have been in linux-next with no reported problems"
    
    * tag 'usb-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
      usb: gadget: rndis: add spinlock for rndis response list
      usb: dwc3: gadget: Let the interrupt handler disable bottom halves.
      USB: gadget: validate endpoint index for xilinx udc
      USB: serial: option: add Telit LE910R1 compositions
      USB: serial: option: add support for DW5829e
      Revert "USB: serial: ch341: add new Product ID for CH341A"
      usb: dwc2: drd: fix soft connect when gadget is unconfigured
      usb: dwc3: pci: Fix Bay Trail phy GPIO mappings
      tps6598x: clear int mask on probe failure
      xhci: Prevent futile URB re-submissions due to incorrect return value.
      xhci: re-initialize the HC during resume if HCE was set
      usb: dwc3: pci: Add "snps,dis_u2_susphy_quirk" for Intel Bay Trail
      usb: dwc3: pci: add support for the Intel Raptor Lake-S

commit 78081594971aae94d743c1af73e63fb258c04616
Merge: 53ab78cd6d5ab 8d093e02e898b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 25 11:22:19 2022 -0800

    Merge tag 'ata-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ata fixes from Damien Le Moal:
     "Two fixes for the pata_hpt37x driver, both from Sergey:
    
       - Fix a PCI register access using an incorrect size (8bits instead of
         16bits)
    
       - Make sure to always disable the primary channel as it is unused"
    
    * tag 'ata-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: pata_hpt37x: disable primary channel on HPT371
      ata: pata_hpt37x: fix PCI clock detection

commit dd990352f01ee9a6c6eee152e5d11c021caccfe4
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 18 16:17:38 2022 +0100

    tracing/osnoise: Make osnoise_main to sleep for microseconds
    
    osnoise's runtime and period are in the microseconds scale, but it is
    currently sleeping in the millisecond's scale. This behavior roots in the
    usage of hwlat as the skeleton for osnoise.
    
    Make osnoise to sleep in the microseconds scale. Also, move the sleep to
    a specialized function.
    
    Link: https://lkml.kernel.org/r/302aa6c7bdf2d131719b22901905e9da122a11b2.1645197336.git.bristot@kernel.org
    
    Cc: Ingo Molnar <mingo@redhat.com>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit ab2f993c01f261aa3eeb8842842ff38bff7806b6
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Feb 14 12:28:47 2022 -0700

    ftrace: Remove unused ftrace_startup_enable() stub
    
    When building with clang + CONFIG_DYNAMIC_FTRACE=n + W=1, there is a
    warning:
    
      kernel/trace/ftrace.c:7194:20: error: unused function 'ftrace_startup_enable' [-Werror,-Wunused-function]
      static inline void ftrace_startup_enable(int command) { }
                         ^
      1 error generated.
    
    Clang warns on instances of static inline functions in .c files with W=1
    after commit 6863f5643dd7 ("kbuild: allow Clang to find unused static
    inline functions for W=1 build").
    
    The ftrace_startup_enable() stub has been unused since
    commit e1effa0144a1 ("ftrace: Annotate the ops operation on update"),
    where its use outside of the CONFIG_DYNAMIC_TRACE section was replaced
    by ftrace_startup_all().  Remove it to resolve the warning.
    
    Link: https://lkml.kernel.org/r/20220214192847.488166-1-nathan@kernel.org
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 7acf3a127bb7c65ff39099afd78960e77b2ca5de
Author: Sven Schnelle <svens@linux.ibm.com>
Date:   Mon Feb 14 14:44:56 2022 +0100

    tracing: Ensure trace buffer is at least 4096 bytes large
    
    Booting the kernel with 'trace_buf_size=1' give a warning at
    boot during the ftrace selftests:
    
    [    0.892809] Running postponed tracer tests:
    [    0.892893] Testing tracer function:
    [    0.901899] Callback from call_rcu_tasks_trace() invoked.
    [    0.983829] Callback from call_rcu_tasks_rude() invoked.
    [    1.072003] .. bad ring buffer .. corrupted trace buffer ..
    [    1.091944] Callback from call_rcu_tasks() invoked.
    [    1.097695] PASSED
    [    1.097701] Testing dynamic ftrace: .. filter failed count=0 ..FAILED!
    [    1.353474] ------------[ cut here ]------------
    [    1.353478] WARNING: CPU: 0 PID: 1 at kernel/trace/trace.c:1951 run_tracer_selftest+0x13c/0x1b0
    
    Therefore enforce a minimum of 4096 bytes to make the selftest pass.
    
    Link: https://lkml.kernel.org/r/20220214134456.1751749-1-svens@linux.ibm.com
    
    Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit bc82c38a6933aab308387d4aca47e0a05de7b553
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Fri Feb 11 08:10:18 2022 +0100

    tracing: Uninline trace_trigger_soft_disabled() partly
    
    On a powerpc32 build with CONFIG_CC_OPTIMISE_FOR_SIZE, the inline
    keyword is not honored and trace_trigger_soft_disabled() appears
    approx 50 times in vmlinux.
    
    Adding -Winline to the build, the following message appears:
    
            ./include/linux/trace_events.h:712:1: error: inlining failed in call to 'trace_trigger_soft_disabled': call is unlikely and code size would grow [-Werror=inline]
    
    That function is rather big for an inlined function:
    
            c003df60 <trace_trigger_soft_disabled>:
            c003df60:       94 21 ff f0     stwu    r1,-16(r1)
            c003df64:       7c 08 02 a6     mflr    r0
            c003df68:       90 01 00 14     stw     r0,20(r1)
            c003df6c:       bf c1 00 08     stmw    r30,8(r1)
            c003df70:       83 e3 00 24     lwz     r31,36(r3)
            c003df74:       73 e9 01 00     andi.   r9,r31,256
            c003df78:       41 82 00 10     beq     c003df88 <trace_trigger_soft_disabled+0x28>
            c003df7c:       38 60 00 00     li      r3,0
            c003df80:       39 61 00 10     addi    r11,r1,16
            c003df84:       4b fd 60 ac     b       c0014030 <_rest32gpr_30_x>
            c003df88:       73 e9 00 80     andi.   r9,r31,128
            c003df8c:       7c 7e 1b 78     mr      r30,r3
            c003df90:       41 a2 00 14     beq     c003dfa4 <trace_trigger_soft_disabled+0x44>
            c003df94:       38 c0 00 00     li      r6,0
            c003df98:       38 a0 00 00     li      r5,0
            c003df9c:       38 80 00 00     li      r4,0
            c003dfa0:       48 05 c5 f1     bl      c009a590 <event_triggers_call>
            c003dfa4:       73 e9 00 40     andi.   r9,r31,64
            c003dfa8:       40 82 00 28     bne     c003dfd0 <trace_trigger_soft_disabled+0x70>
            c003dfac:       73 ff 02 00     andi.   r31,r31,512
            c003dfb0:       41 82 ff cc     beq     c003df7c <trace_trigger_soft_disabled+0x1c>
            c003dfb4:       80 01 00 14     lwz     r0,20(r1)
            c003dfb8:       83 e1 00 0c     lwz     r31,12(r1)
            c003dfbc:       7f c3 f3 78     mr      r3,r30
            c003dfc0:       83 c1 00 08     lwz     r30,8(r1)
            c003dfc4:       7c 08 03 a6     mtlr    r0
            c003dfc8:       38 21 00 10     addi    r1,r1,16
            c003dfcc:       48 05 6f 6c     b       c0094f38 <trace_event_ignore_this_pid>
            c003dfd0:       38 60 00 01     li      r3,1
            c003dfd4:       4b ff ff ac     b       c003df80 <trace_trigger_soft_disabled+0x20>
    
    However it is located in a hot path so inlining it is important.
    But forcing inlining of the entire function by using __always_inline
    leads to increasing the text size by approx 20 kbytes.
    
    Instead, split the fonction in two parts, one part with the likely
    fast path, flagged __always_inline, and a second part out of line.
    
    With this change, on a powerpc32 with CONFIG_CC_OPTIMISE_FOR_SIZE
    vmlinux text increases by only 1,4 kbytes, which is partly
    compensated by a decrease of vmlinux data by 7 kbytes.
    
    On ppc64_defconfig which has CONFIG_CC_OPTIMISE_FOR_SPEED, this
    change reduces vmlinux text by more than 30 kbytes.
    
    Link: https://lkml.kernel.org/r/69ce0986a52d026d381d612801d978aa4f977460.1644563295.git.christophe.leroy@csgroup.eu
    
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit b61edd57740de5895f44f2ea417b164d9e1708bb
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Fri Feb 18 19:00:57 2022 -0500

    eprobes: Remove redundant event type information
    
    Currently, the event probes save the type of the event they are attached
    to when recording the event. For example:
    
      # echo 'e:switch sched/sched_switch prev_state=$prev_state prev_prio=$prev_prio next_pid=$next_pid next_prio=$next_prio' > dynamic_events
      # cat events/eprobes/switch/format
    
     name: switch
     ID: 1717
     format:
            field:unsigned short common_type;       offset:0;       size:2; signed:0;
            field:unsigned char common_flags;       offset:2;       size:1; signed:0;
            field:unsigned char common_preempt_count;       offset:3;       size:1; signed:0;
            field:int common_pid;   offset:4;       size:4; signed:1;
    
            field:unsigned int __probe_type;        offset:8;       size:4; signed:0;
            field:u64 prev_state;   offset:12;      size:8; signed:0;
            field:u64 prev_prio;    offset:20;      size:8; signed:0;
            field:u64 next_pid;     offset:28;      size:8; signed:0;
            field:u64 next_prio;    offset:36;      size:8; signed:0;
    
     print fmt: "(%u) prev_state=0x%Lx prev_prio=0x%Lx next_pid=0x%Lx next_prio=0x%Lx", REC->__probe_type, REC->prev_state, REC->prev_prio, REC->next_pid, REC->next_prio
    
    The __probe_type adds 4 bytes to every event.
    
    One of the reasons for creating eprobes is to limit what is traced in an
    event to be able to limit what is written into the ring buffer. Having
    this redundant 4 bytes to every event takes away from this.
    
    The event that is recorded can be retrieved from the event probe itself,
    that is available when the trace is happening. For user space tools, it
    could simply read the dynamic_event file to find the event they are for.
    So there is really no reason to write this information into the ring
    buffer for every event.
    
    Link: https://lkml.kernel.org/r/20220218190057.2f5a19a8@gandalf.local.home
    
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Reviewed-by: Joel Fernandes <joel@joelfernandes.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 302e9edd54985f584cfc180098f3554774126969
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Wed Feb 23 22:38:37 2022 -0500

    tracing: Have traceon and traceoff trigger honor the instance
    
    If a trigger is set on an event to disable or enable tracing within an
    instance, then tracing should be disabled or enabled in the instance and
    not at the top level, which is confusing to users.
    
    Link: https://lkml.kernel.org/r/20220223223837.14f94ec3@rorschach.local.home
    
    Cc: stable@vger.kernel.org
    Fixes: ae63b31e4d0e2 ("tracing: Separate out trace events from global variables")
    Tested-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Reviewed-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit e01b042e580f1fbf4fd8da467442451da00c7a90
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Feb 23 19:35:36 2022 -0800

    net: stmmac: fix return value of __setup handler
    
    __setup() handlers should return 1 on success, i.e., the parameter
    has been handled. A return of 0 causes the "option=value" string to be
    added to init's environment strings, polluting it.
    
    Fixes: 47dd7a540b8a ("net: add support for STMicroelectronics Ethernet controllers.")
    Fixes: f3240e2811f0 ("stmmac: remove warning when compile as built-in (V2)")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
    Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
    Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Jose Abreu <joabreu@synopsys.com>
    Link: https://lore.kernel.org/r/20220224033536.25056-1-rdunlap@infradead.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 50e06ddceeea263f57fe92baa677c638ecd65bb6
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Feb 23 19:35:28 2022 -0800

    net: sxgbe: fix return value of __setup handler
    
    __setup() handlers should return 1 on success, i.e., the parameter
    has been handled. A return of 0 causes the "option=value" string to be
    added to init's environment strings, polluting it.
    
    Fixes: acc18c147b22 ("net: sxgbe: add EEE(Energy Efficient Ethernet) for Samsung sxgbe")
    Fixes: 1edb9ca69e8a ("net: sxgbe: add basic framework for Samsung 10Gb ethernet driver")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Igor Zhbanov <i.zhbanov@omprussia.ru>
    Link: lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru
    Cc: Siva Reddy <siva.kallam@samsung.com>
    Cc: Girish K S <ks.giri@samsung.com>
    Cc: Byungho An <bh74.an@samsung.com>
    Link: https://lore.kernel.org/r/20220224033528.24640-1-rdunlap@infradead.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c5048a7b2c23ab589f3476a783bd586b663eda5b
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Mon Feb 21 22:59:35 2022 +0000

    can: rcar_canfd: rcar_canfd_channel_probe(): register the CAN device when fully ready
    
    Register the CAN device only when all the necessary initialization is
    completed. This patch makes sure all the data structures and locks are
    initialized before registering the CAN device.
    
    Link: https://lore.kernel.org/all/20220221225935.12300-1-prabhakar.mahadev-lad.rj@bp.renesas.com
    Reported-by: Pavel Machek <pavel@denx.de>
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Reviewed-by: Pavel Machek <pavel@denx.de>
    Reviewed-by: Ulrich Hecht <uli+renesas@fpond.eu>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 0ac983f512033cb7b5e210c9589768ad25b1e36b
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Thu Feb 24 08:32:28 2022 -0600

    ucounts: Fix systemd LimitNPROC with private users regression
    
    Long story short recursively enforcing RLIMIT_NPROC when it is not
    enforced on the process that creates a new user namespace, causes
    currently working code to fail.  There is no reason to enforce
    RLIMIT_NPROC recursively when we don't enforce it normally so update
    the code to detect this case.
    
    I would like to simply use capable(CAP_SYS_RESOURCE) to detect when
    RLIMIT_NPROC is not enforced upon the caller.  Unfortunately because
    RLIMIT_NPROC is charged and checked for enforcement based upon the
    real uid, using capable() which is euid based is inconsistent with reality.
    Come as close as possible to testing for capable(CAP_SYS_RESOURCE) by
    testing for when the real uid would match the conditions when
    CAP_SYS_RESOURCE would be present if the real uid was the effective
    uid.
    
    Reported-by: Etienne Dechamps <etienne@edechamps.fr>
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215596
    Link: https://lkml.kernel.org/r/e9589141-cfeb-90cd-2d0e-83a62787239a@edechamps.fr
    Link: https://lkml.kernel.org/r/87sfs8jmpz.fsf_-_@email.froward.int.ebiederm.org
    Cc: stable@vger.kernel.org
    Fixes: 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit c253bf70c657b407286a6139d85c42fb41f3fcfd
Merge: f03f10a9823ab a222fd8541394
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 25 16:41:17 2022 +0100

    Merge tag 'soc-fsl-fix-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux into arm/fixes
    
    NXP/FSL SoC driver fixes for v5.17
    
    - Add missing SoC compatible in existing binding
    - Replace kernel.h with the necessary inclusions
    - MAINTAINERS file fixes
    - Fix memory allocation failure check in guts driver
    - Various cleanups and minor fixes
    
    * tag 'soc-fsl-fix-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/leo/linux:
      soc: fsl: qe: Check of ioremap return value
      soc: fsl: qe: fix typo in a comment
      soc: fsl: guts: Add a missing memory allocation failure check
      soc: fsl: guts: Revert commit 3c0d64e867ed
      soc: fsl: Correct MAINTAINERS database (SOC)
      soc: fsl: Correct MAINTAINERS database (QUICC ENGINE LIBRARY)
      soc: fsl: Replace kernel.h with the necessary inclusions
      dt-bindings: fsl,layerscape-dcfg: add missing compatible for lx2160a
      dt-bindings: qoriq-clock: add missing compatible for lx2160a
    
    Link: https://lore.kernel.org/r/20220219012208.21835-1-leoyang.li@nxp.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 9ee83635d872812f3920209c606c6ea9e412ffcc
Author: Li RongQing <lirongqing@baidu.com>
Date:   Wed Feb 9 12:16:41 2022 +0800

    KVM: x86: Yield to IPI target vCPU only if it is busy
    
    When sending a call-function IPI-many to vCPUs, yield to the
    IPI target vCPU which is marked as preempted.
    
    but when emulating HLT, an idling vCPU will be voluntarily
    scheduled out and mark as preempted from the guest kernel
    perspective. yielding to idle vCPU is pointless and increase
    unnecessary vmexit, maybe miss the true preempted vCPU
    
    so yield to IPI target vCPU only if vCPU is busy and preempted
    
    Signed-off-by: Li RongQing <lirongqing@baidu.com>
    Message-Id: <1644380201-29423-1-git-send-email-lirongqing@baidu.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 92e68cc558774de01024c18e8b35cdce4731c910
Author: Dexuan Cui <decui@microsoft.com>
Date:   Fri Feb 25 00:46:00 2022 -0800

    x86/kvmclock: Fix Hyper-V Isolated VM's boot issue when vCPUs > 64
    
    When Linux runs as an Isolated VM on Hyper-V, it supports AMD SEV-SNP
    but it's partially enlightened, i.e. cc_platform_has(
    CC_ATTR_GUEST_MEM_ENCRYPT) is true but sev_active() is false.
    
    Commit 4d96f9109109 per se is good, but with it now
    kvm_setup_vsyscall_timeinfo() -> kvmclock_init_mem() calls
    set_memory_decrypted(), and later gets stuck when trying to zere out
    the pages pointed by 'hvclock_mem', if Linux runs as an Isolated VM on
    Hyper-V. The cause is that here now the Linux VM should no longer access
    the original guest physical addrss (GPA); instead the VM should do
    memremap() and access the original GPA + ms_hyperv.shared_gpa_boundary:
    see the example code in drivers/hv/connection.c: vmbus_connect() or
    drivers/hv/ring_buffer.c: hv_ringbuffer_init(). If the VM tries to
    access the original GPA, it keepts getting injected a fault by Hyper-V
    and gets stuck there.
    
    Here the issue happens only when the VM has >=65 vCPUs, because the
    global static array hv_clock_boot[] can hold 64 "struct
    pvclock_vsyscall_time_info" (the sizeof of the struct is 64 bytes), so
    kvmclock_init_mem() only allocates memory in the case of vCPUs > 64.
    
    Since the 'hvclock_mem' pages are only useful when the kvm clock is
    supported by the underlying hypervisor, fix the issue by returning
    early when Linux VM runs on Hyper-V, which doesn't support kvm clock.
    
    Fixes: 4d96f9109109 ("x86/sev: Replace occurrences of sev_active() with cc_platform_has()")
    Tested-by: Andrea Parri (Microsoft) <parri.andrea@gmail.com>
    Signed-off-by: Andrea Parri (Microsoft) <parri.andrea@gmail.com>
    Signed-off-by: Dexuan Cui <decui@microsoft.com>
    Message-Id: <20220225084600.17817-1-decui@microsoft.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 3c51d0a6c761c2025c6db1ed4d3a7273167bf899
Author: Wanpeng Li <wanpengli@tencent.com>
Date:   Tue Feb 22 01:02:03 2022 -0800

    x86/kvm: Don't waste memory if kvmclock is disabled
    
    Even if "no-kvmclock" is passed in cmdline parameter, the guest kernel
    still allocates hvclock_mem which is scaled by the number of vCPUs,
    let's check kvmclock enable in advance to avoid this memory waste.
    
    Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <1645520523-30814-1-git-send-email-wanpengli@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 40cd58dbf121e1d0c18f1bd4dd10335ae45a28fc
Author: Wanpeng Li <wanpengli@tencent.com>
Date:   Fri Feb 25 00:29:40 2022 -0800

    x86/kvm: Don't use PV TLB/yield when mwait is advertised
    
    MWAIT is advertised in host is not overcommitted scenario, however, PV
    TLB/sched yield should be enabled in host overcommitted scenario. Let's
    add the MWAIT checking when enabling PV TLB/sched yield.
    
    Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <1645777780-2581-1-git-send-email-wanpengli@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ece32a75f003464cad59c26305b4462305273d70
Merge: 1a71581012ddf 456f89e0928ab
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Feb 25 09:49:30 2022 -0500

    Merge tag 'kvmarm-fixes-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
    
    KVM/arm64 fixes for 5.17, take #4
    
    - Correctly synchronise PMR and co on PSCI CPU_SUSPEND
    
    - Skip tests that depend on GICv3 when the HW isn't available

commit 456f89e0928ab938122a40e9f094a6524cc158b4
Author: Mark Brown <broonie@kernel.org>
Date:   Wed Feb 23 13:16:24 2022 +0000

    KVM: selftests: aarch64: Skip tests if we can't create a vgic-v3
    
    The arch_timer and vgic_irq kselftests assume that they can create a
    vgic-v3, using the library function vgic_v3_setup() which aborts with a
    test failure if it is not possible to do so. Since vgic-v3 can only be
    instantiated on systems where the host has GICv3 this leads to false
    positives on older systems where that is not the case.
    
    Fix this by changing vgic_v3_setup() to return an error if the vgic can't
    be instantiated and have the callers skip if this happens. We could also
    exit flagging a skip in vgic_v3_setup() but this would prevent future test
    cases conditionally deciding which GIC to use or generally doing more
    complex output.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Reviewed-by: Andrew Jones <drjones@redhat.com>
    Tested-by: Ricardo Koller <ricarkol@google.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220223131624.1830351-1-broonie@kernel.org

commit b3a34dc362c03215031b268fcc0b988e69490231
Author: Casper Andersson <casper.casan@gmail.com>
Date:   Fri Feb 25 11:15:16 2022 +0100

    net: sparx5: Fix add vlan when invalid operation
    
    Check if operation is valid before changing any
    settings in hardware. Otherwise it results in
    changes being made despite it not being a valid
    operation.
    
    Fixes: 78eab33bb68b ("net: sparx5: add vlan support")
    
    Signed-off-by: Casper Andersson <casper.casan@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 767b9825ed1765894e569a3d698749d40d83762a
Author: Jia-Ju Bai <baijiaju1990@gmail.com>
Date:   Fri Feb 25 04:37:27 2022 -0800

    net: chelsio: cxgb3: check the return value of pci_find_capability()
    
    The function pci_find_capability() in t3_prep_adapter() can fail, so its
    return value should be checked.
    
    Fixes: 4d22de3e6cc4 ("Add support for the latest 1G/10G Chelsio adapter, T3")
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5a83dd14c63b80133c0075dfa089d0446cb1e4b3
Merge: 31372fe9668e5 fd98693cb0721
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Feb 25 10:57:47 2022 +0000

    Merge branch 'ibmvnic-fixes'
    
    Sukadev Bhattiprolu says:
    
    ====================
    ibmvnic: Fix a race in ibmvnic_probe()
    
    If we get a transport (reset) event right after a successful CRQ_INIT
    during ibmvnic_probe() but before we set the adapter state to VNIC_PROBED,
    we will throw away the reset assuming that the adapter is still in the
    probing state. But since the adapter has completed the CRQ_INIT any
    subsequent CRQs the we send will be ignored by the vnicserver until
    we release/init the CRQ again. This can leave the adapter unconfigured.
    
    While here fix a couple of other bugs that were observed (Patches 1,2,4).
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit fd98693cb0721317f27341951593712c580c36a1
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:58 2022 -0800

    ibmvnic: Allow queueing resets during probe
    
    We currently don't allow queuing resets when adapter is in VNIC_PROBING
    state - instead we throw away the reset and return EBUSY. The reasoning
    is probably that during ibmvnic_probe() the ibmvnic_adapter itself is
    being initialized so performing a reset during this time can lead us to
    accessing fields in the ibmvnic_adapter that are not fully initialized.
    A review of the code shows that all the adapter state neede to process a
    reset is initialized before registering the CRQ so that should no longer
    be a concern.
    
    Further the expectation is that if we do get a reset (transport event)
    during probe, the do..while() loop in ibmvnic_probe() will handle this
    by reinitializing the CRQ.
    
    While that is true to some extent, it is possible that the reset might
    occur _after_ the CRQ is registered and CRQ_INIT message was exchanged
    but _before_ the adapter state is set to VNIC_PROBED. As mentioned above,
    such a reset will be thrown away. While the client assumes that the
    adapter is functional, the vnic server will wait for the client to reinit
    the adapter. This disconnect between the two leaves the adapter down
    needing manual intervention.
    
    Because ibmvnic_probe() has other work to do after initializing the CRQ
    (such as registering the netdev at a minimum) and because the reset event
    can occur at any instant after the CRQ is initialized, there will always
    be a window between initializing the CRQ and considering the adapter
    ready for resets (ie state == PROBED).
    
    So rather than discarding resets during this window, allow queueing them
    - but only process them after the adapter is fully initialized.
    
    To do this, introduce a new completion state ->probe_done and have the
    reset worker thread wait on this before processing resets.
    
    This change brings up two new situations in or just after ibmvnic_probe().
    First after one or more resets were queued, we encounter an error and
    decide to retry the initialization.  At that point the queued resets are
    no longer relevant since we could be talking to a new vnic server. So we
    must purge/flush the queued resets before restarting the initialization.
    As a side note, since we are still in the probing stage and we have not
    registered the netdev, it will not be CHANGE_PARAM reset.
    
    Second this change opens up a potential race between the worker thread
    in __ibmvnic_reset(), the tasklet and the ibmvnic_open() due to the
    following sequence of events:
    
            1. Register CRQ
            2. Get transport event before CRQ_INIT completes.
            3. Tasklet schedules reset:
                    a) add rwi to list
                    b) schedule_work() to start worker thread which runs
                       and waits for ->probe_done.
            4. ibmvnic_probe() decides to retry, purges rwi_list
            5. Re-register crq and this time rest of probe succeeds - register
               netdev and complete(->probe_done).
            6. Worker thread resumes in __ibmvnic_reset() from 3b.
            7. Worker thread sets ->resetting bit
            8. ibmvnic_open() comes in, notices ->resetting bit, sets state
               to IBMVNIC_OPEN and returns early expecting worker thread to
               finish the open.
            9. Worker thread finds rwi_list empty and returns without
               opening the interface.
    
    If this happens, the ->ndo_open() call is effectively lost and the
    interface remains down. To address this, ensure that ->rwi_list is
    not empty before setting the ->resetting  bit. See also comments in
    __ibmvnic_reset().
    
    Fixes: 6a2fb0e99f9c ("ibmvnic: driver initialization for kdump/kexec")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f628ad531b4f34fdba0984255b4a2850dd369513
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:57 2022 -0800

    ibmvnic: clear fop when retrying probe
    
    Clear ->failover_pending flag that may have been set in the previous
    pass of registering CRQ. If we don't clear, a subsequent ibmvnic_open()
    call would be misled into thinking a failover is pending and assuming
    that the reset worker thread would open the adapter. If this pass of
    registering the CRQ succeeds (i.e there is no transport event), there
    wouldn't be a reset worker thread.
    
    This would leave the adapter unconfigured and require manual intervention
    to bring it up during boot.
    
    Fixes: 5a18e1e0c193 ("ibmvnic: Fix failover case for non-redundant configuration")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ae16bf15374d8b055e040ac6f3f1147ab1c9bb7d
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:56 2022 -0800

    ibmvnic: init init_done_rc earlier
    
    We currently initialize the ->init_done completion/return code fields
    before issuing a CRQ_INIT command. But if we get a transport event soon
    after registering the CRQ the taskslet may already have recorded the
    completion and error code. If we initialize here, we might overwrite/
    lose that and end up issuing the CRQ_INIT only to timeout later.
    
    If that timeout happens during probe, we will leave the adapter in the
    DOWN state rather than retrying to register/init the CRQ.
    
    Initialize the completion before registering the CRQ so we don't lose
    the notification.
    
    Fixes: 032c5e82847a ("Driver for IBM System i/p VNIC protocol")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 570425f8c7c18b14fa8a2a58a0adb431968ad118
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:55 2022 -0800

    ibmvnic: register netdev after init of adapter
    
    Finish initializing the adapter before registering netdev so state
    is consistent.
    
    Fixes: c26eba03e407 ("ibmvnic: Update reset infrastructure to support tunable parameters")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 36491f2df9ad2501e5a4ec25d3d95d72bafd2781
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:54 2022 -0800

    ibmvnic: complete init_done on transport events
    
    If we get a transport event, set the error and mark the init as
    complete so the attempt to send crq-init or login fail sooner
    rather than wait for the timeout.
    
    Fixes: bbd669a868bb ("ibmvnic: Fix completion structure initialization")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 83da53f7e4bd86dca4b2edc1e2bb324fb3c033a1
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:53 2022 -0800

    ibmvnic: define flush_reset_queue helper
    
    Define and use a helper to flush the reset queue.
    
    Fixes: 2770a7984db5 ("ibmvnic: Introduce hard reset recovery")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 765559b10ce514eb1576595834f23cdc92125fee
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:52 2022 -0800

    ibmvnic: initialize rc before completing wait
    
    We should initialize ->init_done_rc before calling complete(). Otherwise
    the waiting thread may see ->init_done_rc as 0 before we have updated it
    and may assume that the CRQ was successful.
    
    Fixes: 6b278c0cb378 ("ibmvnic delay complete()")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8d0657f39f487d904fca713e0bc39c2707382553
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Thu Feb 24 22:23:51 2022 -0800

    ibmvnic: free reset-work-item when flushing
    
    Fix a tiny memory leak when flushing the reset work queue.
    
    Fixes: 2770a7984db5 ("ibmvnic: Introduce hard reset recovery")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 31372fe9668e52c1f700c628c9fa716dd453f784
Merge: 91b0383fef06f 7c76ecd9c99b6
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Feb 25 10:44:15 2022 +0000

    Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec
    
    Steffen Klassert says:
    
    ====================
    1) Fix PMTU for IPv6 if the reported MTU minus the ESP overhead is
       smaller than 1280. From Jiri Bohac.
    
    2) Fix xfrm interface ID and inter address family tunneling when
       migrating xfrm states. From Yan Yan.
    
    3) Add missing xfrm intrerface ID initialization on xfrmi_changelink.
       From Antony Antony.
    
    4) Enforce validity of xfrm offload input flags so that userspace can't
       send undefined flags to the offload driver.
       From Leon Romanovsky.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 91b0383fef06f20b847fa9e4f0e3054ead0b1a1b
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Feb 24 18:01:54 2022 +0200

    net: dcb: flush lingering app table entries for unregistered devices
    
    If I'm not mistaken (and I don't think I am), the way in which the
    dcbnl_ops work is that drivers call dcb_ieee_setapp() and this populates
    the application table with dynamically allocated struct dcb_app_type
    entries that are kept in the module-global dcb_app_list.
    
    However, nobody keeps exact track of these entries, and although
    dcb_ieee_delapp() is supposed to remove them, nobody does so when the
    interface goes away (example: driver unbinds from device). So the
    dcb_app_list will contain lingering entries with an ifindex that no
    longer matches any device in dcb_app_lookup().
    
    Reclaim the lost memory by listening for the NETDEV_UNREGISTER event and
    flushing the app table entries of interfaces that are now gone.
    
    In fact something like this used to be done as part of the initial
    commit (blamed below), but it was done in dcbnl_exit() -> dcb_flushapp(),
    essentially at module_exit time. That became dead code after commit
    7a6b6f515f77 ("DCB: fix kconfig option") which essentially merged
    "tristate config DCB" and "bool config DCBNL" into a single "bool config
    DCB", so net/dcb/dcbnl.c could not be built as a module anymore.
    
    Commit 36b9ad8084bd ("net/dcb: make dcbnl.c explicitly non-modular")
    recognized this and deleted dcbnl_exit() and dcb_flushapp() altogether,
    leaving us with the version we have today.
    
    Since flushing application table entries can and should be done as soon
    as the netdevice disappears, fundamentally the commit that is to blame
    is the one that introduced the design of this API.
    
    Fixes: 9ab933ab2cc8 ("dcbnl: add appliction tlv handlers")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5
Author: D. Wythe <alibuda@linux.alibaba.com>
Date:   Thu Feb 24 23:26:19 2022 +0800

    net/smc: fix connection leak
    
    There's a potential leak issue under following execution sequence :
    
    smc_release                             smc_connect_work
    if (sk->sk_state == SMC_INIT)
                                            send_clc_confirim
            tcp_abort();
                                            ...
                                            sk.sk_state = SMC_ACTIVE
    smc_close_active
    switch(sk->sk_state) {
    ...
    case SMC_ACTIVE:
            smc_close_final()
            // then wait peer closed
    
    Unfortunately, tcp_abort() may discard CLC CONFIRM messages that are
    still in the tcp send buffer, in which case our connection token cannot
    be delivered to the server side, which means that we cannot get a
    passive close message at all. Therefore, it is impossible for the to be
    disconnected at all.
    
    This patch tries a very simple way to avoid this issue, once the state
    has changed to SMC_ACTIVE after tcp_abort(), we can actively abort the
    smc connection, considering that the state is SMC_INIT before
    tcp_abort(), abandoning the complete disconnection process should not
    cause too much problem.
    
    In fact, this problem may exist as long as the CLC CONFIRM message is
    not received by the server. Whether a timer should be added after
    smc_close_final() needs to be discussed in the future. But even so, this
    patch provides a faster release for connection in above case, it should
    also be valuable.
    
    Fixes: 39f41f367b08 ("net/smc: common release code for non-accepted sockets")
    Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
    Acked-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 087a7b944c5db409f7c1a68bf4896c56ba54eaff
Author: Vincent Whitchurch <vincent.whitchurch@axis.com>
Date:   Thu Feb 24 12:38:29 2022 +0100

    net: stmmac: only enable DMA interrupts when ready
    
    In this driver's ->ndo_open() callback, it enables DMA interrupts,
    starts the DMA channels, then requests interrupts with request_irq(),
    and then finally enables napi.
    
    If RX DMA interrupts are received before napi is enabled, no processing
    is done because napi_schedule_prep() will return false.  If the network
    has a lot of broadcast/multicast traffic, then the RX ring could fill up
    completely before napi is enabled.  When this happens, no further RX
    interrupts will be delivered, and the driver will fail to receive any
    packets.
    
    Fix this by only enabling DMA interrupts after all other initialization
    is complete.
    
    Fixes: 523f11b5d4fd72efb ("net: stmmac: move hardware setup for stmmac_open to new function")
    Reported-by: Lars Persson <larper@axis.com>
    Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dcf4ff7a48e7598e6b10126cc02177abb8ae4f3f
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Wed Feb 23 22:19:54 2022 +0100

    xen/netfront: destroy queues before real_num_tx_queues is zeroed
    
    xennet_destroy_queues() relies on info->netdev->real_num_tx_queues to
    delete queues. Since d7dac083414eb5bb99a6d2ed53dc2c1b405224e5
    ("net-sysfs: update the queue counts in the unregistration path"),
    unregister_netdev() indirectly sets real_num_tx_queues to 0. Those two
    facts together means, that xennet_destroy_queues() called from
    xennet_remove() cannot do its job, because it's called after
    unregister_netdev(). This results in kfree-ing queues that are still
    linked in napi, which ultimately crashes:
    
        BUG: kernel NULL pointer dereference, address: 0000000000000000
        #PF: supervisor read access in kernel mode
        #PF: error_code(0x0000) - not-present page
        PGD 0 P4D 0
        Oops: 0000 [#1] PREEMPT SMP PTI
        CPU: 1 PID: 52 Comm: xenwatch Tainted: G        W         5.16.10-1.32.fc32.qubes.x86_64+ #226
        RIP: 0010:free_netdev+0xa3/0x1a0
        Code: ff 48 89 df e8 2e e9 00 00 48 8b 43 50 48 8b 08 48 8d b8 a0 fe ff ff 48 8d a9 a0 fe ff ff 49 39 c4 75 26 eb 47 e8 ed c1 66 ff <48> 8b 85 60 01 00 00 48 8d 95 60 01 00 00 48 89 ef 48 2d 60 01 00
        RSP: 0000:ffffc90000bcfd00 EFLAGS: 00010286
        RAX: 0000000000000000 RBX: ffff88800edad000 RCX: 0000000000000000
        RDX: 0000000000000001 RSI: ffffc90000bcfc30 RDI: 00000000ffffffff
        RBP: fffffffffffffea0 R08: 0000000000000000 R09: 0000000000000000
        R10: 0000000000000000 R11: 0000000000000001 R12: ffff88800edad050
        R13: ffff8880065f8f88 R14: 0000000000000000 R15: ffff8880066c6680
        FS:  0000000000000000(0000) GS:ffff8880f3300000(0000) knlGS:0000000000000000
        CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
        CR2: 0000000000000000 CR3: 00000000e998c006 CR4: 00000000003706e0
        Call Trace:
         <TASK>
         xennet_remove+0x13d/0x300 [xen_netfront]
         xenbus_dev_remove+0x6d/0xf0
         __device_release_driver+0x17a/0x240
         device_release_driver+0x24/0x30
         bus_remove_device+0xd8/0x140
         device_del+0x18b/0x410
         ? _raw_spin_unlock+0x16/0x30
         ? klist_iter_exit+0x14/0x20
         ? xenbus_dev_request_and_reply+0x80/0x80
         device_unregister+0x13/0x60
         xenbus_dev_changed+0x18e/0x1f0
         xenwatch_thread+0xc0/0x1a0
         ? do_wait_intr_irq+0xa0/0xa0
         kthread+0x16b/0x190
         ? set_kthread_struct+0x40/0x40
         ret_from_fork+0x22/0x30
         </TASK>
    
    Fix this by calling xennet_destroy_queues() from xennet_uninit(),
    when real_num_tx_queues is still available. This ensures that queues are
    destroyed when real_num_tx_queues is set to 0, regardless of how
    unregister_netdev() was called.
    
    Originally reported at
    https://github.com/QubesOS/qubes-issues/issues/7257
    
    Fixes: d7dac083414eb5bb9 ("net-sysfs: update the queue counts in the unregistration path")
    Cc: stable@vger.kernel.org
    Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f03f10a9823ab8591afbc20ddaf9ce2aeb52ce59
Merge: 3f96885eb713c 8840f5460a237
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 25 11:14:22 2022 +0100

    Merge tag 'omap-for-v5.17/fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes
    
    Fixes for omaps
    
    Fixes for devkit8000 timer regression. Similar to the earlier beagleboard
    fixes, we must not configure the clocksource drivers to use an alternative
    timer configuration. It causes unnecessary issues with power management.
    Only some old designs based on early beagleboard revisions with a miswired
    timer need to use the alternative timer.
    
    * tag 'omap-for-v5.17/fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
      ARM: dts: Use 32KiHz oscillator on devkit8000
      ARM: dts: switch timer config to common devkit8000 devicetree
    
    Link: https://lore.kernel.org/r/pull-1645606483-876944@atomide.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 1a71581012ddf1f465040ef3d9f700341fa3cf04
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Feb 24 19:19:17 2022 +0000

    Revert "KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()"
    
    Revert back to refreshing vmcs.HOST_CR3 immediately prior to VM-Enter.
    The PCID (ASID) part of CR3 can be bumped without KVM being scheduled
    out, as the kernel will switch CR3 during __text_poke(), e.g. in response
    to a static key toggling.  If switch_mm_irqs_off() chooses a new ASID for
    the mm associate with KVM, KVM will do VM-Enter => VM-Exit with a stale
    vmcs.HOST_CR3.
    
    Add a comment to explain why KVM must wait until VM-Enter is imminent to
    refresh vmcs.HOST_CR3.
    
    The following splat was captured by stashing vmcs.HOST_CR3 in kvm_vcpu
    and adding a WARN in load_new_mm_cr3() to fire if a new ASID is being
    loaded for the KVM-associated mm while KVM has a "running" vCPU:
    
      static void load_new_mm_cr3(pgd_t *pgdir, u16 new_asid, bool need_flush)
      {
            struct kvm_vcpu *vcpu = kvm_get_running_vcpu();
    
            ...
    
            WARN(vcpu && (vcpu->cr3 & GENMASK(11, 0)) != (new_mm_cr3 & GENMASK(11, 0)) &&
                 (vcpu->cr3 & PHYSICAL_PAGE_MASK) == (new_mm_cr3 & PHYSICAL_PAGE_MASK),
                 "KVM is hosed, loading CR3 = %lx, vmcs.HOST_CR3 = %lx", new_mm_cr3, vcpu->cr3);
      }
    
      ------------[ cut here ]------------
      KVM is hosed, loading CR3 = 8000000105393004, vmcs.HOST_CR3 = 105393003
      WARNING: CPU: 4 PID: 20717 at arch/x86/mm/tlb.c:291 load_new_mm_cr3+0x82/0xe0
      Modules linked in: vhost_net vhost vhost_iotlb tap kvm_intel
      CPU: 4 PID: 20717 Comm: stable Tainted: G        W         5.17.0-rc3+ #747
      Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
      RIP: 0010:load_new_mm_cr3+0x82/0xe0
      RSP: 0018:ffffc9000489fa98 EFLAGS: 00010082
      RAX: 0000000000000000 RBX: 8000000105393004 RCX: 0000000000000027
      RDX: 0000000000000027 RSI: 00000000ffffdfff RDI: ffff888277d1b788
      RBP: 0000000000000004 R08: ffff888277d1b780 R09: ffffc9000489f8b8
      R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000
      R13: ffff88810678a800 R14: 0000000000000004 R15: 0000000000000c33
      FS:  00007fa9f0e72700(0000) GS:ffff888277d00000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 0000000000000000 CR3: 00000001001b5003 CR4: 0000000000172ea0
      Call Trace:
       <TASK>
       switch_mm_irqs_off+0x1cb/0x460
       __text_poke+0x308/0x3e0
       text_poke_bp_batch+0x168/0x220
       text_poke_finish+0x1b/0x30
       arch_jump_label_transform_apply+0x18/0x30
       static_key_slow_inc_cpuslocked+0x7c/0x90
       static_key_slow_inc+0x16/0x20
       kvm_lapic_set_base+0x116/0x190
       kvm_set_apic_base+0xa5/0xe0
       kvm_set_msr_common+0x2f4/0xf60
       vmx_set_msr+0x355/0xe70 [kvm_intel]
       kvm_set_msr_ignored_check+0x91/0x230
       kvm_emulate_wrmsr+0x36/0x120
       vmx_handle_exit+0x609/0x6c0 [kvm_intel]
       kvm_arch_vcpu_ioctl_run+0x146f/0x1b80
       kvm_vcpu_ioctl+0x279/0x690
       __x64_sys_ioctl+0x83/0xb0
       do_syscall_64+0x3b/0xc0
       entry_SYSCALL_64_after_hwframe+0x44/0xae
       </TASK>
      ---[ end trace 0000000000000000 ]---
    
    This reverts commit 15ad9762d69fd8e40a4a51828c1d6b0c1b8fbea0.
    
    Fixes: 15ad9762d69f ("KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()")
    Reported-by: Wanpeng Li <kernellwp@gmail.com>
    Cc: Lai Jiangshan <laijs@linux.alibaba.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Acked-by: Lai Jiangshan <jiangshanlai@gmail.com>
    Message-Id: <20220224191917.3508476-3-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit bca06b85fcaf866602e328b3bcd86f74180eca14
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Feb 24 19:19:16 2022 +0000

    Revert "KVM: VMX: Save HOST_CR3 in vmx_set_host_fs_gs()"
    
    Undo a nested VMX fix as a step toward reverting the commit it fixed,
    15ad9762d69f ("KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()"),
    as the underlying premise that "host CR3 in the vcpu thread can only be
    changed when scheduling" is wrong.
    
    This reverts commit a9f2705ec84449e3b8d70c804766f8e97e23080d.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220224191917.3508476-2-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 035b0fcf02707d3c9c2890dc1484b11aa5335eb1
Author: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Date:   Tue Feb 15 08:48:14 2022 +0900

    can: gs_usb: change active_channels's type from atomic_t to u8
    
    The driver uses an atomic_t variable: gs_usb:active_channels to keep
    track of the number of opened channels in order to only allocate
    memory for the URBs when this count changes from zero to one.
    
    However, the driver does not decrement the counter when an error
    occurs in gs_can_open(). This issue is fixed by changing the type from
    atomic_t to u8 and by simplifying the logic accordingly.
    
    It is safe to use an u8 here because the network stack big kernel lock
    (a.k.a. rtnl_mutex) is being hold. For details, please refer to [1].
    
    [1] https://lore.kernel.org/linux-can/CAMZ6Rq+sHpiw34ijPsmp7vbUpDtJwvVtdV7CvRZJsLixjAFfrg@mail.gmail.com/T/#t
    
    Fixes: d08e973a77d1 ("can: gs_usb: Added support for the GS_USB CAN devices")
    Link: https://lore.kernel.org/all/20220214234814.1321599-1-mailhol.vincent@wanadoo.fr
    Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit f4896248e9025ff744b4147e6758274a1cb8cbae
Author: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Date:   Sat Feb 12 20:27:13 2022 +0900

    can: etas_es58x: change opened_channel_cnt's type from atomic_t to u8
    
    The driver uses an atomic_t variable: struct
    es58x_device::opened_channel_cnt to keep track of the number of opened
    channels in order to only allocate memory for the URBs when this count
    changes from zero to one.
    
    While the intent was to prevent race conditions, the choice of an
    atomic_t turns out to be a bad idea for several reasons:
    
    - implementation is incorrect and fails to decrement
      opened_channel_cnt when the URB allocation fails as reported in
      [1].
    
    - even if opened_channel_cnt were to be correctly decremented,
      atomic_t is insufficient to cover edge cases: there can be a race
      condition in which 1/ a first process fails to allocate URBs
      memory 2/ a second process enters es58x_open() before the first
      process does its cleanup and decrements opened_channed_cnt. In
      which case, the second process would successfully return despite
      the URBs memory not being allocated.
    
    - actually, any kind of locking mechanism was useless here because
      it is redundant with the network stack big kernel lock
      (a.k.a. rtnl_lock) which is being hold by all the callers of
      net_device_ops:ndo_open() and net_device_ops:ndo_close(). c.f. the
      ASSERST_RTNL() calls in __dev_open() [2] and __dev_close_many()
      [3].
    
    The atmomic_t is thus replaced by a simple u8 type and the logic to
    increment and decrement es58x_device:opened_channel_cnt is simplified
    accordingly fixing the bug reported in [1]. We do not check again for
    ASSERST_RTNL() as this is already done by the callers.
    
    [1] https://lore.kernel.org/linux-can/20220201140351.GA2548@kili/T/#u
    [2] https://elixir.bootlin.com/linux/v5.16/source/net/core/dev.c#L1463
    [3] https://elixir.bootlin.com/linux/v5.16/source/net/core/dev.c#L1541
    
    Fixes: 8537257874e9 ("can: etas_es58x: add core support for ETAS ES58X CAN USB interfaces")
    Link: https://lore.kernel.org/all/20220212112713.577957-1-mailhol.vincent@wanadoo.fr
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit a6df953f0178c8a11fb2de95327643b622077018
Merge: 8a7271000b915 877d11f0332cd
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 24 21:54:56 2022 -0800

    Merge branch 'mptcp-fixes-for-5-17'
    
    Mat Martineau says:
    
    ====================
    mptcp: Fixes for 5.17
    
    Patch 1 fixes an issue with the SIOCOUTQ ioctl in MPTCP sockets that
    have performed a fallback to TCP.
    
    Patch 2 is a selftest fix to correctly remove temp files.
    
    Patch 3 fixes a shift-out-of-bounds issue found by syzkaller.
    ====================
    
    Link: https://lore.kernel.org/r/20220225005259.318898-1-mathew.j.martineau@linux.intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 877d11f0332cd2160e19e3313e262754c321fa36
Author: Mat Martineau <mathew.j.martineau@linux.intel.com>
Date:   Thu Feb 24 16:52:59 2022 -0800

    mptcp: Correctly set DATA_FIN timeout when number of retransmits is large
    
    Syzkaller with UBSAN uncovered a scenario where a large number of
    DATA_FIN retransmits caused a shift-out-of-bounds in the DATA_FIN
    timeout calculation:
    
    ================================================================================
    UBSAN: shift-out-of-bounds in net/mptcp/protocol.c:470:29
    shift exponent 32 is too large for 32-bit type 'unsigned int'
    CPU: 1 PID: 13059 Comm: kworker/1:0 Not tainted 5.17.0-rc2-00630-g5fbf21c90c60 #1
    Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
    Workqueue: events mptcp_worker
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     ubsan_epilogue+0xb/0x5a lib/ubsan.c:151
     __ubsan_handle_shift_out_of_bounds.cold+0xb2/0x20e lib/ubsan.c:330
     mptcp_set_datafin_timeout net/mptcp/protocol.c:470 [inline]
     __mptcp_retrans.cold+0x72/0x77 net/mptcp/protocol.c:2445
     mptcp_worker+0x58a/0xa70 net/mptcp/protocol.c:2528
     process_one_work+0x9df/0x16d0 kernel/workqueue.c:2307
     worker_thread+0x95/0xe10 kernel/workqueue.c:2454
     kthread+0x2f4/0x3b0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
     </TASK>
    ================================================================================
    
    This change limits the maximum timeout by limiting the size of the
    shift, which keeps all intermediate values in-bounds.
    
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/259
    Fixes: 6477dd39e62c ("mptcp: Retransmit DATA_FIN")
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 63bb8239d80571204c61d19c73f7bf5e3d9ef5fa
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Feb 24 16:52:58 2022 -0800

    selftests: mptcp: do complete cleanup at exit
    
    After commit 05be5e273c84 ("selftests: mptcp: add disconnect tests")
    the mptcp selftests leave behind a couple of tmp files after
    each run. run_tests_disconnect() misnames a few variables used to
    track them. Address the issue setting the appropriate global variables
    
    Fixes: 05be5e273c84 ("selftests: mptcp: add disconnect tests")
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 07c2c7a3b622e109ba4d2efd916da0477617ce81
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Feb 24 16:52:57 2022 -0800

    mptcp: accurate SIOCOUTQ for fallback socket
    
    The MPTCP SIOCOUTQ implementation is not very accurate in
    case of fallback: it only measures the data in the MPTCP-level
    write queue, but it does not take in account the subflow
    write queue utilization. In case of fallback the first can be
    empty, while the latter is not.
    
    The above produces sporadic self-tests issues and can foul
    legit user-space application.
    
    Fix the issue additionally querying the subflow in case of fallback.
    
    Fixes: 644807e3e462 ("mptcp: add SIOCINQ, OUTQ and OUTQNSD ioctls")
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/260
    Reported-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 22e2100b1b07d6f5acc71cc1acb53f680c677d77
Author: Changbin Du <changbin.du@intel.com>
Date:   Sun Feb 13 16:18:45 2022 +0800

    riscv: fix oops caused by irqsoff latency tracer
    
    The trace_hardirqs_{on,off}() require the caller to setup frame pointer
    properly. This because these two functions use macro 'CALLER_ADDR1' (aka.
    __builtin_return_address(1)) to acquire caller info. If the $fp is used
    for other purpose, the code generated this macro (as below) could trigger
    memory access fault.
    
       0xffffffff8011510e <+80>:    ld      a1,-16(s0)
       0xffffffff80115112 <+84>:    ld      s2,-8(a1)  # <-- paging fault here
    
    The oops message during booting if compiled with 'irqoff' tracer enabled:
    [    0.039615][    T0] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8
    [    0.041925][    T0] Oops [#1]
    [    0.042063][    T0] Modules linked in:
    [    0.042864][    T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.17.0-rc1-00233-g9a20c48d1ed2 #29
    [    0.043568][    T0] Hardware name: riscv-virtio,qemu (DT)
    [    0.044343][    T0] epc : trace_hardirqs_on+0x56/0xe2
    [    0.044601][    T0]  ra : restore_all+0x12/0x6e
    [    0.044721][    T0] epc : ffffffff80126a5c ra : ffffffff80003b94 sp : ffffffff81403db0
    [    0.044801][    T0]  gp : ffffffff8163acd8 tp : ffffffff81414880 t0 : 0000000000000020
    [    0.044882][    T0]  t1 : 0098968000000000 t2 : 0000000000000000 s0 : ffffffff81403de0
    [    0.044967][    T0]  s1 : 0000000000000000 a0 : 0000000000000001 a1 : 0000000000000100
    [    0.045046][    T0]  a2 : 0000000000000000 a3 : 0000000000000000 a4 : 0000000000000000
    [    0.045124][    T0]  a5 : 0000000000000000 a6 : 0000000000000000 a7 : 0000000054494d45
    [    0.045210][    T0]  s2 : ffffffff80003b94 s3 : ffffffff81a8f1b0 s4 : ffffffff80e27b50
    [    0.045289][    T0]  s5 : ffffffff81414880 s6 : ffffffff8160fa00 s7 : 00000000800120e8
    [    0.045389][    T0]  s8 : 0000000080013100 s9 : 000000000000007f s10: 0000000000000000
    [    0.045474][    T0]  s11: 0000000000000000 t3 : 7fffffffffffffff t4 : 0000000000000000
    [    0.045548][    T0]  t5 : 0000000000000000 t6 : ffffffff814aa368
    [    0.045620][    T0] status: 0000000200000100 badaddr: 00000000000000f8 cause: 000000000000000d
    [    0.046402][    T0] [<ffffffff80003b94>] restore_all+0x12/0x6e
    
    This because the $fp(aka. $s0) register is not used as frame pointer in the
    assembly entry code.
    
            resume_kernel:
                    REG_L s0, TASK_TI_PREEMPT_COUNT(tp)
                    bnez s0, restore_all
                    REG_L s0, TASK_TI_FLAGS(tp)
                    andi s0, s0, _TIF_NEED_RESCHED
                    beqz s0, restore_all
                    call preempt_schedule_irq
                    j restore_all
    
    To fix above issue, here we add one extra level wrapper for function
    trace_hardirqs_{on,off}() so they can be safely called by low level entry
    code.
    
    Signed-off-by: Changbin Du <changbin.du@gmail.com>
    Fixes: 3c4697982982 ("riscv: Enable LOCKDEP_SUPPORT & fixup TRACE_IRQFLAGS_SUPPORT")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 762e52f79c95ea20a7229674ffd13b94d7d8959c
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Wed Feb 9 12:56:23 2022 +0900

    riscv: fix nommu_k210_sdcard_defconfig
    
    Instead of an arbitrary delay, use the "rootwait" kernel option to wait
    for the mmc root device to be ready.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Fixes: 7e09fd3994c5 ("riscv: Add Canaan Kendryte K210 SD card defconfig")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit ce33c845b030c9cf768370c951bc699470b09fa7
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Sun Feb 20 23:49:57 2022 +0100

    tracing: Dump stacktrace trigger to the corresponding instance
    
    The stacktrace event trigger is not dumping the stacktrace to the instance
    where it was enabled, but to the global "instance."
    
    Use the private_data, pointing to the trigger file, to figure out the
    corresponding trace instance, and use it in the trigger action, like
    snapshot_trigger does.
    
    Link: https://lkml.kernel.org/r/afbb0b4f18ba92c276865bc97204d438473f4ebc.1645396236.git.bristot@kernel.org
    
    Cc: stable@vger.kernel.org
    Fixes: ae63b31e4d0e2 ("tracing: Separate out trace events from global variables")
    Reviewed-by: Tom Zanussi <zanussi@kernel.org>
    Tested-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 8a7271000b915bd6301866699c54c1e11885bc84
Merge: d8152cfe2f21d a56a1138cbd85
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 24 18:13:30 2022 -0800

    Merge tag 'for-net-2022-02-24' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth
    
    Luiz Augusto von Dentz says:
    
    ====================
    bluetooth pull request for net:
    
     - Fix regression with RFCOMM
     - Fix regression with LE devices using Privacy (RPA)
     - Fix regression with LE devices not waiting proper timeout to
       establish connections
     - Fix race in smp
    
    * tag 'for-net-2022-02-24' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth:
      Bluetooth: hci_sync: Fix not using conn_timeout
      Bluetooth: hci_sync: Fix hci_update_accept_list_sync
      Bluetooth: assign len after null check
      Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks
      Bluetooth: fix data races in smp_unregister(), smp_del_chan()
      Bluetooth: hci_core: Fix leaking sent_cmd skb
    ====================
    
    Link: https://lore.kernel.org/r/20220224210838.197787-1-luiz.dentz@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 53ab78cd6d5aba25575a7cfb95729336ba9497d8
Merge: 5ee3d0015a4ce 2f0754f27a230
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 17:35:22 2022 -0800

    Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
    
    Pull clk fixes from Stephen Boyd:
     "A couple driver fixes in the clk subsystem
    
       - Fix a hang due to bad clk parent in the Ingenic jz4725b driver
    
       - Fix SD controllers on Qualcomm MSM8994 SoCs by removing clks that
         shouldn't be touched"
    
    * tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux:
      clk: jz4725b: fix mmc0 clock gating
      clk: qcom: gcc-msm8994: Remove NoC clocks

commit 5ee3d0015a4cec798b44ceefc34245752104fc08
Merge: 7ee022567bf9e ecf8a99f4807c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 17:29:26 2022 -0800

    Merge tag 'drm-fixes-2022-02-25' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Regular drm fixes pull, i915, amdgpu and tegra mostly, all pretty
      small.
    
      core:
       - edid: Always set RGB444
    
      tegra:
       - tegra186 suspend/resume fixes
       - syncpoint wait fix
       - build warning fix
       - eDP on older devices fix
    
      amdgpu:
       - Display FP fix
       - PCO powergating fix
       - RDNA2 OEM SKU stability fixes
       - Display PSR fix
       - PCI ASPM fix
       - Display link encoder fix for TEST_COMMIT
       - Raven2 suspend/resume fix
       - Fix a regression in virtual display support
       - GPUVM eviction fix
    
      i915:
       - Fix QGV handling on ADL-P+
       - Fix bw atomic check when switching between SAGV vs. no SAGV
       - Disconnect PHYs left connected by BIOS on disabled ports
       - Fix SAVG to no SAGV transitions on TGL+
       - Print PHY name properly on calibration error (DG2)
    
      imx:
       - dcss: Select GEM CMA helpers
    
      radeon:
       - Fix some variables's type
    
      vc4:
       - Fix codec cleanup
       - Fix PM reference counting"
    
    * tag 'drm-fixes-2022-02-25' of git://anongit.freedesktop.org/drm/drm: (24 commits)
      drm/amdgpu: check vm ready by amdgpu_vm->evicting flag
      drm/amdgpu: bypass tiling flag check in virtual display case (v2)
      Revert "drm/amdgpu: add modifiers in amdgpu_vkms_plane_init()"
      drm/amdgpu: do not enable asic reset for raven2
      drm/amd/display: Fix stream->link_enc unassigned during stream removal
      drm/amd: Check if ASPM is enabled from PCIe subsystem
      drm/edid: Always set RGB444
      drm/tegra: dpaux: Populate AUX bus
      drm/radeon: fix variable type
      drm/amd/display: For vblank_disable_immediate, check PSR is really used
      drm/amd/pm: fix some OEM SKU specific stability issues
      drm/amdgpu: disable MMHUB PG for Picasso
      drm/amd/display: Protect update_bw_bounding_box FPU code.
      drm/i915/dg2: Print PHY name properly on calibration error
      drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV
      drm/i915: Correctly populate use_sagv_wm for all pipes
      drm/i915: Disconnect PHYs left connected by BIOS on disabled ports
      drm/i915: Widen the QGV point mask
      drm/imx/dcss: i.MX8MQ DCSS select DRM_GEM_CMA_HELPER
      drm/vc4: crtc: Fix runtime_pm reference counting
      ...

commit aa091a6a91df395a0fa00a808a543301ec99e734
Author: Horatiu Vultur <horatiu.vultur@microchip.com>
Date:   Sat Feb 19 15:15:36 2022 +0100

    clk: lan966x: Fix linking error
    
    If the config options HAS_IOMEM is not set then the driver fails to link
    with the following error:
    clk-lan966x.c:(.text+0x950): undefined reference to
    `devm_platform_ioremap_resource'
    
    Therefor add missing dependencies: HAS_IOMEM and OF.
    
    Fixes: 54104ee02333 ("clk: lan966x: Add lan966x SoC clock driver")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
    Link: https://lore.kernel.org/r/20220219141536.460812-1-horatiu.vultur@microchip.com
    Reviewed-by: Nicolas Ferre <nicolas.ferre@microchip.com>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 4188db23285e28d9e9b9096f856cdcd7868005ee
Author: Marek Szyprowski <m.szyprowski@samsung.com>
Date:   Mon Jan 24 14:52:46 2022 +0100

    drm/exynos: Search for TE-gpio in DSI panel's node
    
    TE-gpio, if defined, is placed in the panel's node, not the parent DSI
    node. Change the devm_gpiod_get_optional() to gpiod_get_optional() and
    pass proper device node to it. The code already has a proper cleanup
    path, so it looks that the devm_* variant has been applied accidentally
    during the conversion to gpiod API.
    
    Fixes: ee6c8b5afa62 ("drm/exynos: Replace legacy gpio interface for gpiod interface")
    Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Fixed a typo.
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit 0a6e8d0a6df67e0fff9c7d130b89769df4167c2b
Author: Marek Szyprowski <m.szyprowski@samsung.com>
Date:   Fri Jan 21 11:00:39 2022 +0100

    drm/exynos: Don't fail if no TE-gpio is defined for DSI driver
    
    TE-gpio is optional and if it is not found then gpiod_get_optional()
    returns NULL. In such case the code will continue and try to convert NULL
    gpiod to irq what in turn fails. The failure is then propagated and driver
    is not registered.
    
    Fix this by returning early from exynos_dsi_register_te_irq() if no
    TE-gpio is found.
    
    Fixes: ee6c8b5afa62 ("drm/exynos: Replace legacy gpio interface for gpiod interface")
    Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit 586d0902456ad965c9a456fd0a0f451518aed1c5
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Dec 22 19:01:34 2021 +0000

    drm/exynos: gsc: Use platform_get_irq() to get the interrupt
    
    platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypassed the hierarchical setup and messed up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq().
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit be0a3b7e2a97e3f73004a5b453cc2023d8c1317a
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Dec 22 19:01:33 2021 +0000

    drm/exynos/fimc: Use platform_get_irq() to get the interrupt
    
    platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypassed the hierarchical setup and messed up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq().
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit b342c1f335981ebc442127efe03524d2331a273c
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Dec 22 19:01:32 2021 +0000

    drm/exynos/exynos_drm_fimd: Use platform_get_irq_byname() to get the interrupt
    
    platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypassed the hierarchical setup and messed up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq_byname().
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit be52abd4d2b7ea343373cc116a99699a3e3c5573
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Dec 22 19:01:31 2021 +0000

    drm/exynos: mixer: Use platform_get_irq() to get the interrupt
    
    platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypassed the hierarchical setup and messed up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq().
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit 0d22b031662ad48d5835e470a90784f4b39adce9
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Dec 22 19:01:30 2021 +0000

    drm/exynos/exynos7_drm_decon: Use platform_get_irq_byname() to get the interrupt
    
    platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypassed the hierarchical setup and messed up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq_byname().
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>

commit 6e6fec3f961c00ca34ffb4bf2ad9febb4b499f8d
Author: Taniya Das <tdas@codeaurora.org>
Date:   Thu Feb 24 00:26:06 2022 +0530

    clk: qcom: dispcc: Update the transition delay for MDSS GDSC
    
    On SC7180 we observe black screens because the gdsc is being
    enabled/disabled very rapidly and the GDSC FSM state does not work as
    expected. This is due to the fact that the GDSC reset value is being
    updated from SW.
    
    The recommended transition delay for mdss core gdsc updated for
    SC7180/SC7280/SM8250.
    
    Fixes: dd3d06622138 ("clk: qcom: Add display clock controller driver for SC7180")
    Fixes: 1a00c962f9cd ("clk: qcom: Add display clock controller driver for SC7280")
    Fixes: 80a18f4a8567 ("clk: qcom: Add display clock controller driver for SM8150 and SM8250")
    Signed-off-by: Taniya Das <tdas@codeaurora.org>
    Link: https://lore.kernel.org/r/20220223185606.3941-2-tdas@codeaurora.org
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    [sboyd@kernel.org: lowercase hex]
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 4e7c4d3652f96f41179aab3ff53025c7a550d689
Author: Taniya Das <tdas@codeaurora.org>
Date:   Thu Feb 24 00:26:05 2022 +0530

    clk: qcom: gdsc: Add support to update GDSC transition delay
    
    GDSCs have multiple transition delays which are used for the GDSC FSM
    states. Older targets/designs required these values to be updated from
    gdsc code to certain default values for the FSM state to work as
    expected. But on the newer targets/designs the values updated from the
    GDSC driver can hamper the FSM state to not work as expected.
    
    On SC7180 we observe black screens because the gdsc is being
    enabled/disabled very rapidly and the GDSC FSM state does not work as
    expected. This is due to the fact that the GDSC reset value is being
    updated from SW.
    
    Thus add support to update the transition delay from the clock
    controller gdscs as required.
    
    Fixes: 45dd0e55317cc ("clk: qcom: Add support for GDSCs)
    Signed-off-by: Taniya Das <tdas@codeaurora.org>
    Link: https://lore.kernel.org/r/20220223185606.3941-1-tdas@codeaurora.org
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 7ee022567bf9e2e0b3cd92461a2f4986ecc99673
Merge: 1f840c0ef44b7 13e741b834538
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 14:36:38 2022 -0800

    Merge tag 'perf-tools-fixes-for-v5.17-2022-02-24' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tools fixes from Arnaldo Carvalho de Melo:
    
     - Fix double free in in the error path when opening perf.data from
       multiple files in a directory instead of from a single file
    
     - Sync the msr-index.h copy with the kernel sources
    
     - Fix error when printing 'weight' field in 'perf script'
    
     - Skip failing sigtrap test for arm+aarch64 in 'perf test'
    
     - Fix failure to use a cpu list for uncore events in hybrid systems,
       e.g. Intel Alder Lake
    
    * tag 'perf-tools-fixes-for-v5.17-2022-02-24' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf script: Fix error when printing 'weight' field
      tools arch x86: Sync the msr-index.h copy with the kernel sources
      perf data: Fix double free in perf_session__delete()
      perf evlist: Fix failed to use cpu list for uncore events
      perf test: Skip failing sigtrap test for arm+aarch64

commit 1f840c0ef44b7304d6a58499e0e5668084c0864d
Merge: d8152cfe2f21d e910a53fb4f20
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 14:05:49 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "x86 host:
    
       - Expose KVM_CAP_ENABLE_CAP since it is supported
    
       - Disable KVM_HC_CLOCK_PAIRING in TSC catchup mode
    
       - Ensure async page fault token is nonzero
    
       - Fix lockdep false negative
    
       - Fix FPU migration regression from the AMX changes
    
      x86 guest:
    
       - Don't use PV TLB/IPI/yield on uniprocessor guests
    
      PPC:
    
       - reserve capability id (topic branch for ppc/kvm)"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      KVM: x86: nSVM: disallow userspace setting of MSR_AMD64_TSC_RATIO to non default value when tsc scaling disabled
      KVM: x86/mmu: make apf token non-zero to fix bug
      KVM: PPC: reserve capability 210 for KVM_CAP_PPC_AIL_MODE_3
      x86/kvm: Don't use pv tlb/ipi/sched_yield if on 1 vCPU
      x86/kvm: Fix compilation warning in non-x86_64 builds
      x86/kvm/fpu: Remove kvm_vcpu_arch.guest_supported_xcr0
      x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0
      kvm: x86: Disable KVM_HC_CLOCK_PAIRING if tsc is in always catchup mode
      KVM: Fix lockdep false negative during host resume
      KVM: x86: Add KVM_CAP_ENABLE_CAP to x86

commit 3f96885eb713c45ca1c228a9a58b42e1a7726675
Merge: 31c50bf184a4f fa231bef3b34f
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Feb 24 22:50:17 2022 +0100

    Merge tag 'imx-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/fixes
    
    i.MX fixes for 5.17, round 2:
    
    - Drop reset signal from i.MX8MM vpumix power domain to fix a system
      hang.
    - Fix a dtbs_check warning caused by #thermal-sensor-cells in i.MX8ULP
      device tree.
    - Fix a clock disabling imbalance in gpcv2 driver.
    
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 31c50bf184a4f5c93394a48b5ba3bc281636360e
Merge: 795a2ab1da7bd 8d3b01e0d4bb5
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Feb 24 22:48:00 2022 +0100

    Merge tag 'tegra-for-5.17-arm-dt-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux into arm/fixes
    
    ARM: tegra: Device tree fixes for v5.17-rc6
    
    This contains fixes for the eDP panel found on the Venice 2 and Nyan
    boards.
    
    * tag 'tegra-for-5.17-arm-dt-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux:
      ARM: tegra: Move panels to AUX bus
    
    Link: https://lore.kernel.org/r/20220223162209.293722-1-thierry.reding@gmail.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 795a2ab1da7bd67eee4d6b8a3bc6daa862008774
Merge: 98e437f134b34 3916c3619599a
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Feb 24 22:46:59 2022 +0100

    Merge tag 'v5.17-rockchip-dtsfixes1' of git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip into arm/fixes
    
    Fix the display-port-sound on Gru devices, DDR voltage on the Quartz-A
    board, fix emmc signal-integrity and usb OTG mode on rk3399-puma as well
    as a number of dtschema fixes to make the reduce the number of errors.
    
    * tag 'v5.17-rockchip-dtsfixes1' of git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip:
      ARM: dts: rockchip: fix a typo on rk3288 crypto-controller
      ARM: dts: rockchip: reorder rk322x hmdi clocks
      arm64: dts: rockchip: reorder rk3399 hdmi clocks
      arm64: dts: rockchip: align pl330 node name with dtschema
      arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity
      arm64: dts: rockchip: fix Quartz64-A ddr regulator voltage
      arm64: dts: rockchip: Switch RK3399-Gru DP to SPDIF output
      arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode
      arm64: dts: rockchip: drop pclk_xpcs from gmac0 on rk3568
      arm64: dts: rockchip: fix dma-controller node names on rk356x
    
    Link: https://lore.kernel.org/r/1973741.CViHJPHrxy@phil
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit d8152cfe2f21d6930c680311b03b169899c8d2a0
Merge: f672ff91236b5 3f1271b54edcc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 13:19:57 2022 -0800

    Merge tag 'pci-v5.17-fixes-5' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci fixes from Bjorn Helgaas:
    
     - Fix a merge error that broke PCI device enumeration on mvebu
       platforms, including Turris Omnia (Armada 385) (Pali Rohár)
    
     - Avoid using ATS on all AMD Navi10 and Navi14 GPUs because some
       VBIOSes don't account for "harvested" (disabled) parts of the chip
       when initializing caches (Alex Deucher)
    
    * tag 'pci-v5.17-fixes-5' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
      PCI: Mark all AMD Navi10 and Navi14 GPU ATS as broken
      PCI: mvebu: Fix device enumeration regression

commit f672ff91236b556da338f477a23b1b4e87b40d23
Merge: 73878e5eb1bd3 42404d8f1c018
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 12:45:32 2022 -0800

    Merge tag 'net-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from bpf and netfilter.
    
      Current release - regressions:
    
       - bpf: fix crash due to out of bounds access into reg2btf_ids
    
       - mvpp2: always set port pcs ops, avoid null-deref
    
       - eth: marvell: fix driver load from initrd
    
       - eth: intel: revert "Fix reset bw limit when DCB enabled with 1 TC"
    
      Current release - new code bugs:
    
       - mptcp: fix race in overlapping signal events
    
      Previous releases - regressions:
    
       - xen-netback: revert hotplug-status changes causing devices to not
         be configured
    
       - dsa:
          - avoid call to __dev_set_promiscuity() while rtnl_mutex isn't
            held
          - fix panic when removing unoffloaded port from bridge
    
       - dsa: microchip: fix bridging with more than two member ports
    
      Previous releases - always broken:
    
       - bpf:
          - fix crash due to incorrect copy_map_value when both spin lock
            and timer are present in a single value
          - fix a bpf_timer initialization issue with clang
          - do not try bpf_msg_push_data with len 0
          - add schedule points in batch ops
    
       - nf_tables:
          - unregister flowtable hooks on netns exit
          - correct flow offload action array size
          - fix a couple of memory leaks
    
       - vsock: don't check owner in vhost_vsock_stop() while releasing
    
       - gso: do not skip outer ip header in case of ipip and net_failover
    
       - smc: use a mutex for locking "struct smc_pnettable"
    
       - openvswitch: fix setting ipv6 fields causing hw csum failure
    
       - mptcp: fix race in incoming ADD_ADDR option processing
    
       - sysfs: add check for netdevice being present to speed_show
    
       - sched: act_ct: fix flow table lookup after ct clear or switching
         zones
    
       - eth: intel: fixes for SR-IOV forwarding offloads
    
       - eth: broadcom: fixes for selftests and error recovery
    
       - eth: mellanox: flow steering and SR-IOV forwarding fixes
    
      Misc:
    
       - make __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor
         friends not report freed skbs as drops
    
       - force inlining of checksum functions in net/checksum.h"
    
    * tag 'net-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (85 commits)
      net: mv643xx_eth: process retval from of_get_mac_address
      ping: remove pr_err from ping_lookup
      Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC"
      openvswitch: Fix setting ipv6 fields causing hw csum failure
      ipv6: prevent a possible race condition with lifetimes
      net/smc: Use a mutex for locking "struct smc_pnettable"
      bnx2x: fix driver load from initrd
      Revert "xen-netback: Check for hotplug-status existence before watching"
      Revert "xen-netback: remove 'hotplug-status' once it has served its purpose"
      net/mlx5e: Fix VF min/max rate parameters interchange mistake
      net/mlx5e: Add missing increment of count
      net/mlx5e: MPLSoUDP decap, fix check for unsupported matches
      net/mlx5e: Fix MPLSoUDP encap to use MPLS action information
      net/mlx5e: Add feature check for set fec counters
      net/mlx5e: TC, Skip redundant ct clear actions
      net/mlx5e: TC, Reject rules with forward and drop actions
      net/mlx5e: TC, Reject rules with drop and modify hdr action
      net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
      net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
      net/mlx5: Fix possible deadlock on rule deletion
      ...

commit a56a1138cbd85e4d565356199d60e1cb94e5a77a
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Thu Feb 17 13:10:38 2022 -0800

    Bluetooth: hci_sync: Fix not using conn_timeout
    
    When using hci_le_create_conn_sync it shall wait for the conn_timeout
    since the connection complete may take longer than just 2 seconds.
    
    Also fix the masking of HCI_EV_LE_ENHANCED_CONN_COMPLETE and
    HCI_EV_LE_CONN_COMPLETE so they are never both set so we can predict
    which one the controller will use in case of HCI_OP_LE_CREATE_CONN.
    
    Fixes: 6cd29ec6ae5e3 ("Bluetooth: hci_sync: Wait for proper events when connecting LE")
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 80740ebb7e1ad15ab9c11425dcd26e073f86d74b
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Thu Feb 24 07:11:47 2022 -0800

    Bluetooth: hci_sync: Fix hci_update_accept_list_sync
    
    hci_update_accept_list_sync is returning the filter based on the error
    but that gets overwritten by hci_le_set_addr_resolution_enable_sync
    return instead of using the actual result of the likes of
    hci_le_add_accept_list_sync which was intended.
    
    Fixes: ad383c2c65a5b ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled")
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 2e8ecb4bbc13d4752d64a9f8f5512d59125cab25
Author: Wang Qing <wangqing@vivo.com>
Date:   Mon Feb 14 18:01:56 2022 -0800

    Bluetooth: assign len after null check
    
    len should be assigned after a null check
    
    Signed-off-by: Wang Qing <wangqing@vivo.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 29fb608396d6a62c1b85acc421ad7a4399085b9f
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Mon Feb 14 17:59:38 2022 -0800

    Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks
    
    Since bt_skb_sendmmsg can be used with the likes of SOCK_STREAM it
    shall return the partial chunks it could allocate instead of freeing
    everything as otherwise it can cause problems like bellow.
    
    Fixes: 81be03e026dc ("Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg")
    Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Link: https://lore.kernel.org/r/d7206e12-1b99-c3be-84f4-df22af427ef5@molgen.mpg.de
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215594
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Tested-by: Paul Menzel <pmenzel@molgen.mpg.de> (Nokia N9 (MeeGo/Harmattan)
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit fa78d2d1d64f147062e384a4a10a26a5f89944b5
Author: Lin Ma <linma@zju.edu.cn>
Date:   Wed Feb 16 12:37:14 2022 +0800

    Bluetooth: fix data races in smp_unregister(), smp_del_chan()
    
    Previous commit e04480920d1e ("Bluetooth: defer cleanup of resources
    in hci_unregister_dev()") defers all destructive actions to
    hci_release_dev() to prevent cocurrent problems like NPD, UAF.
    
    However, there are still some exceptions that are ignored.
    
    The smp_unregister() in hci_dev_close_sync() (previously in
    hci_dev_do_close) will release resources like the sensitive channel
    and the smp_dev objects. Consider the situations the device is detaching
    or power down while the kernel is still operating on it, the following
    data race could take place.
    
    thread-A  hci_dev_close_sync  | thread-B  read_local_oob_ext_data
                                  |
    hci_dev_unlock()              |
    ...                           | hci_dev_lock()
    if (hdev->smp_data)           |
      chan = hdev->smp_data       |
                                  | chan = hdev->smp_data (3)
                                  |
      hdev->smp_data = NULL (1)   | if (!chan || !chan->data) (4)
      ...                         |
      smp = chan->data            | smp = chan->data
      if (smp)                    |
        chan->data = NULL (2)     |
        ...                       |
        kfree_sensitive(smp)      |
                                  | // dereference smp trigger UFA
    
    That is, the objects hdev->smp_data and chan->data both suffer from the
    data races. In a preempt-enable kernel, the above schedule (when (3) is
    before (1) and (4) is before (2)) leads to UAF bugs. It can be
    reproduced in the latest kernel and below is part of the report:
    
    [   49.097146] ================================================================
    [   49.097611] BUG: KASAN: use-after-free in smp_generate_oob+0x2dd/0x570
    [   49.097611] Read of size 8 at addr ffff888006528360 by task generate_oob/155
    [   49.097611]
    [   49.097611] Call Trace:
    [   49.097611]  <TASK>
    [   49.097611]  dump_stack_lvl+0x34/0x44
    [   49.097611]  print_address_description.constprop.0+0x1f/0x150
    [   49.097611]  ? smp_generate_oob+0x2dd/0x570
    [   49.097611]  ? smp_generate_oob+0x2dd/0x570
    [   49.097611]  kasan_report.cold+0x7f/0x11b
    [   49.097611]  ? smp_generate_oob+0x2dd/0x570
    [   49.097611]  smp_generate_oob+0x2dd/0x570
    [   49.097611]  read_local_oob_ext_data+0x689/0xc30
    [   49.097611]  ? hci_event_packet+0xc80/0xc80
    [   49.097611]  ? sysvec_apic_timer_interrupt+0x9b/0xc0
    [   49.097611]  ? asm_sysvec_apic_timer_interrupt+0x12/0x20
    [   49.097611]  ? mgmt_init_hdev+0x1c/0x240
    [   49.097611]  ? mgmt_init_hdev+0x28/0x240
    [   49.097611]  hci_sock_sendmsg+0x1880/0x1e70
    [   49.097611]  ? create_monitor_event+0x890/0x890
    [   49.097611]  ? create_monitor_event+0x890/0x890
    [   49.097611]  sock_sendmsg+0xdf/0x110
    [   49.097611]  __sys_sendto+0x19e/0x270
    [   49.097611]  ? __ia32_sys_getpeername+0xa0/0xa0
    [   49.097611]  ? kernel_fpu_begin_mask+0x1c0/0x1c0
    [   49.097611]  __x64_sys_sendto+0xd8/0x1b0
    [   49.097611]  ? syscall_exit_to_user_mode+0x1d/0x40
    [   49.097611]  do_syscall_64+0x3b/0x90
    [   49.097611]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [   49.097611] RIP: 0033:0x7f5a59f51f64
    ...
    [   49.097611] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5a59f51f64
    [   49.097611] RDX: 0000000000000007 RSI: 00007f5a59d6ac70 RDI: 0000000000000006
    [   49.097611] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
    [   49.097611] R10: 0000000000000040 R11: 0000000000000246 R12: 00007ffec26916ee
    [   49.097611] R13: 00007ffec26916ef R14: 00007f5a59d6afc0 R15: 00007f5a59d6b700
    
    To solve these data races, this patch places the smp_unregister()
    function in the protected area by the hci_dev_lock(). That is, the
    smp_unregister() function can not be concurrently executed when
    operating functions (most of them are mgmt operations in mgmt.c) hold
    the device lock.
    
    This patch is tested with kernel LOCK DEBUGGING enabled. The price from
    the extended holding time of the device lock is supposed to be low as the
    smp_unregister() function is fairly short and efficient.
    
    Signed-off-by: Lin Ma <linma@zju.edu.cn>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit dd3b1dc3dd050f1f47cd13e300732852414270f8
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Fri Feb 4 13:12:35 2022 -0800

    Bluetooth: hci_core: Fix leaking sent_cmd skb
    
    sent_cmd memory is not freed before freeing hci_dev causing it to leak
    it contents.
    
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit ecf8a99f4807c17fa310a83067a95964cedd9ac1
Merge: 7c17b3d37f1fa 28adef861233c
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 25 05:51:04 2022 +1000

    Merge tag 'drm-intel-fixes-2022-02-24' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    - Fix QGV handling on ADL-P+ (Ville Syrjälä)
    - Fix bw atomic check when switching between SAGV vs. no SAGV (Ville Syrjälä)
    - Disconnect PHYs left connected by BIOS on disabled ports (Imre Deak)
    - Fix SAVG to no SAGV transitions on TGL+ (Ville Syrjälä)
    - Print PHY name properly on calibration error (DG2) (Matt Roper)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/YhdyHwRWkOTWwlqi@tursulin-mobl2

commit 73878e5eb1bd3c9656685ca60bc3a49d17311e0c
Merge: 3a5f59b17f9de b2750f14007f0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 11:15:10 2022 -0800

    Merge tag 'block-5.17-2022-02-24' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - NVMe pull request:
        - send H2CData PDUs based on MAXH2CDATA (Varun Prakash)
        - fix passthrough to namespaces with unsupported features (Christoph
          Hellwig)
    
     - Clear iocb->private at poll completion (Stefano)
    
    * tag 'block-5.17-2022-02-24' of git://git.kernel.dk/linux-block:
      nvme-tcp: send H2CData PDUs based on MAXH2CDATA
      nvme: also mark passthrough-only namespaces ready in nvme_update_ns_info
      nvme: don't return an error from nvme_configure_metadata
      block: clear iocb->private in blkdev_bio_end_io_async()

commit 3abea10e6a8f0e7804ed4c124bea2d15aca977c8
Author: Chuansheng Liu <chuansheng.liu@intel.com>
Date:   Wed Feb 23 08:20:24 2022 +0800

    thermal: int340x: fix memory leak in int3400_notify()
    
    It is easy to hit the below memory leaks in my TigerLake platform:
    
    unreferenced object 0xffff927c8b91dbc0 (size 32):
      comm "kworker/0:2", pid 112, jiffies 4294893323 (age 83.604s)
      hex dump (first 32 bytes):
        4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65  NAME=INT3400 The
        72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5  rmal.kkkkkkkkkk.
      backtrace:
        [<ffffffff9c502c3e>] __kmalloc_track_caller+0x2fe/0x4a0
        [<ffffffff9c7b7c15>] kvasprintf+0x65/0xd0
        [<ffffffff9c7b7d6e>] kasprintf+0x4e/0x70
        [<ffffffffc04cb662>] int3400_notify+0x82/0x120 [int3400_thermal]
        [<ffffffff9c8b7358>] acpi_ev_notify_dispatch+0x54/0x71
        [<ffffffff9c88f1a7>] acpi_os_execute_deferred+0x17/0x30
        [<ffffffff9c2c2c0a>] process_one_work+0x21a/0x3f0
        [<ffffffff9c2c2e2a>] worker_thread+0x4a/0x3b0
        [<ffffffff9c2cb4dd>] kthread+0xfd/0x130
        [<ffffffff9c201c1f>] ret_from_fork+0x1f/0x30
    
    Fix it by calling kfree() accordingly.
    
    Fixes: 38e44da59130 ("thermal: int3400_thermal: process "thermal table changed" event")
    Signed-off-by: Chuansheng Liu <chuansheng.liu@intel.com>
    Cc: 4.14+ <stable@vger.kernel.org> # 4.14+
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 3a5f59b17f9dec448976626663a73841460d7ab4
Merge: 6c528f34ca367 80912cef18f16
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 11:08:15 2022 -0800

    Merge tag 'io_uring-5.17-2022-02-23' of git://git.kernel.dk/linux-block
    
    Pull io_uring fixes from Jens Axboe:
    
     - Add a conditional schedule point in io_add_buffers() (Eric)
    
     - Fix for a quiesce speedup merged in this release (Dylan)
    
     - Don't convert to jiffies for event timeout waiting, it's way too
       coarse when we accept a timespec as input (me)
    
    * tag 'io_uring-5.17-2022-02-23' of git://git.kernel.dk/linux-block:
      io_uring: disallow modification of rsrc_data during quiesce
      io_uring: don't convert to jiffies for waiting on timeouts
      io_uring: add a schedule point in io_add_buffers()

commit c5eb92f57de2446e0071c3af70ea54f237eb05d5
Merge: cfb92440ee71a ef8ee1cb8fc89
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Thu Feb 24 19:54:59 2022 +0100

    Merge branch 'cpufreq/arm/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm
    
    Pull ARM cpufreq fixes for 5.18-rc6 from Viresh Kumar:
    
    "This fixes issues related to throttle IRQ for Qcom SoCs."
    
    * 'cpufreq/arm/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm:
      cpufreq: qcom-hw: Delay enabling throttle_irq
      cpufreq: Reintroduce ready() callback

commit 6c528f34ca367468a5be2f0263a7031c166ad558
Merge: 91318b29a81cf 21d90aaee8d5c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 24 10:42:20 2022 -0800

    Merge tag 'platform-drivers-x86-v5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
    
    Pull more x86 platform driver fixes from Hans de Goede:
     "Two more fixes:
    
       - Fix suspend/resume regression on AMD Cezanne APUs in >= 5.16
    
       - Fix Microsoft Surface 3 battery readings"
    
    * tag 'platform-drivers-x86-v5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:
      surface: surface3_power: Fix battery readings on batteries without a serial number
      platform/x86: amd-pmc: Set QOS during suspend on CZN w/ timer wakeup

commit 42404d8f1c01861b22ccfa1d70f950242720ae57
Author: Mauri Sandberg <maukka@ext.kapsi.fi>
Date:   Wed Feb 23 16:23:37 2022 +0200

    net: mv643xx_eth: process retval from of_get_mac_address
    
    Obtaining a MAC address may be deferred in cases when the MAC is stored
    in an NVMEM block, for example, and it may not be ready upon the first
    retrieval attempt and return EPROBE_DEFER.
    
    It is also possible that a port that does not rely on NVMEM has been
    already created when getting the defer request. Thus, also the resources
    allocated previously must be freed when doing a roll-back.
    
    Fixes: 76723bca2802 ("net: mv643xx_eth: add DT parsing support")
    Signed-off-by: Mauri Sandberg <maukka@ext.kapsi.fi>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220223142337.41757-1-maukka@ext.kapsi.fi
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e910a53fb4f20aa012e46371ffb4c32c8da259b4
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Wed Feb 23 13:56:49 2022 +0200

    KVM: x86: nSVM: disallow userspace setting of MSR_AMD64_TSC_RATIO to non default value when tsc scaling disabled
    
    If nested tsc scaling is disabled, MSR_AMD64_TSC_RATIO should
    never have non default value.
    
    Due to way nested tsc scaling support was implmented in qemu,
    it would set this msr to 0 when nested tsc scaling was disabled.
    Ignore that value for now, as it causes no harm.
    
    Fixes: 5228eb96a487 ("KVM: x86: nSVM: implement nested TSC scaling")
    Cc: stable@vger.kernel.org
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220223115649.319134-1-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6f3c1fc53d86d580d8d6d749c4af23705e4f6f79
Author: Liang Zhang <zhangliang5@huawei.com>
Date:   Tue Feb 22 11:12:39 2022 +0800

    KVM: x86/mmu: make apf token non-zero to fix bug
    
    In current async pagefault logic, when a page is ready, KVM relies on
    kvm_arch_can_dequeue_async_page_present() to determine whether to deliver
    a READY event to the Guest. This function test token value of struct
    kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a
    READY event is finished by Guest. If value is zero meaning that a READY
    event is done, so the KVM can deliver another.
    But the kvm_arch_setup_async_pf() may produce a valid token with zero
    value, which is confused with previous mention and may lead the loss of
    this READY event.
    
    This bug may cause task blocked forever in Guest:
     INFO: task stress:7532 blocked for more than 1254 seconds.
           Not tainted 5.10.0 #16
     "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
     task:stress          state:D stack:    0 pid: 7532 ppid:  1409
     flags:0x00000080
     Call Trace:
      __schedule+0x1e7/0x650
      schedule+0x46/0xb0
      kvm_async_pf_task_wait_schedule+0xad/0xe0
      ? exit_to_user_mode_prepare+0x60/0x70
      __kvm_handle_async_pf+0x4f/0xb0
      ? asm_exc_page_fault+0x8/0x30
      exc_page_fault+0x6f/0x110
      ? asm_exc_page_fault+0x8/0x30
      asm_exc_page_fault+0x1e/0x30
     RIP: 0033:0x402d00
     RSP: 002b:00007ffd31912500 EFLAGS: 00010206
     RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0
     RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0
     RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086
     R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000
     R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000
    
    Signed-off-by: Liang Zhang <zhangliang5@huawei.com>
    Message-Id: <20220222031239.1076682-1-zhangliang5@huawei.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit cd33bdcbead882c2e58fdb4a54a7bd75b610a452
Author: Xin Long <lucien.xin@gmail.com>
Date:   Wed Feb 23 22:41:08 2022 -0500

    ping: remove pr_err from ping_lookup
    
    As Jakub noticed, prints should be avoided on the datapath.
    Also, as packets would never come to the else branch in
    ping_lookup(), remove pr_err() from ping_lookup().
    
    Fixes: 35a79e64de29 ("ping: fix the dif and sdif check in ping_lookup")
    Reported-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Xin Long <lucien.xin@gmail.com>
    Link: https://lore.kernel.org/r/1ef3f2fcd31bd681a193b1fcf235eee1603819bd.1645674068.git.lucien.xin@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit fe20371578ef640069e6ae9fa8038f60e7908565
Author: Mateusz Palczewski <mateusz.palczewski@intel.com>
Date:   Wed Feb 23 09:53:47 2022 -0800

    Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC"
    
    Revert of a patch that instead of fixing a AQ error when trying
    to reset BW limit introduced several regressions related to
    creation and managing TC. Currently there are errors when creating
    a TC on both PF and VF.
    
    Error log:
    [17428.783095] i40e 0000:3b:00.1: AQ command Config VSI BW allocation per TC failed = 14
    [17428.783107] i40e 0000:3b:00.1: Failed configuring TC map 0 for VSI 391
    [17428.783254] i40e 0000:3b:00.1: AQ command Config VSI BW allocation per TC failed = 14
    [17428.783259] i40e 0000:3b:00.1: Unable to  configure TC map 0 for VSI 391
    
    This reverts commit 3d2504663c41104b4359a15f35670cfa82de1bbf.
    
    Fixes: 3d2504663c41 (i40e: Fix reset bw limit when DCB enabled with 1 TC)
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
    Link: https://lore.kernel.org/r/20220223175347.1690692-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d9b5ae5c1b241b91480aa30408be12fe91af834a
Author: Paul Blakey <paulb@nvidia.com>
Date:   Wed Feb 23 18:34:16 2022 +0200

    openvswitch: Fix setting ipv6 fields causing hw csum failure
    
    Ipv6 ttl, label and tos fields are modified without first
    pulling/pushing the ipv6 header, which would have updated
    the hw csum (if available). This might cause csum validation
    when sending the packet to the stack, as can be seen in
    the trace below.
    
    Fix this by updating skb->csum if available.
    
    Trace resulted by ipv6 ttl dec and then sending packet
    to conntrack [actions: set(ipv6(hlimit=63)),ct(zone=99)]:
    [295241.900063] s_pf0vf2: hw csum failure
    [295241.923191] Call Trace:
    [295241.925728]  <IRQ>
    [295241.927836]  dump_stack+0x5c/0x80
    [295241.931240]  __skb_checksum_complete+0xac/0xc0
    [295241.935778]  nf_conntrack_tcp_packet+0x398/0xba0 [nf_conntrack]
    [295241.953030]  nf_conntrack_in+0x498/0x5e0 [nf_conntrack]
    [295241.958344]  __ovs_ct_lookup+0xac/0x860 [openvswitch]
    [295241.968532]  ovs_ct_execute+0x4a7/0x7c0 [openvswitch]
    [295241.979167]  do_execute_actions+0x54a/0xaa0 [openvswitch]
    [295242.001482]  ovs_execute_actions+0x48/0x100 [openvswitch]
    [295242.006966]  ovs_dp_process_packet+0x96/0x1d0 [openvswitch]
    [295242.012626]  ovs_vport_receive+0x6c/0xc0 [openvswitch]
    [295242.028763]  netdev_frame_hook+0xc0/0x180 [openvswitch]
    [295242.034074]  __netif_receive_skb_core+0x2ca/0xcb0
    [295242.047498]  netif_receive_skb_internal+0x3e/0xc0
    [295242.052291]  napi_gro_receive+0xba/0xe0
    [295242.056231]  mlx5e_handle_rx_cqe_mpwrq_rep+0x12b/0x250 [mlx5_core]
    [295242.062513]  mlx5e_poll_rx_cq+0xa0f/0xa30 [mlx5_core]
    [295242.067669]  mlx5e_napi_poll+0xe1/0x6b0 [mlx5_core]
    [295242.077958]  net_rx_action+0x149/0x3b0
    [295242.086762]  __do_softirq+0xd7/0x2d6
    [295242.090427]  irq_exit+0xf7/0x100
    [295242.093748]  do_IRQ+0x7f/0xd0
    [295242.096806]  common_interrupt+0xf/0xf
    [295242.100559]  </IRQ>
    [295242.102750] RIP: 0033:0x7f9022e88cbd
    [295242.125246] RSP: 002b:00007f9022282b20 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffda
    [295242.132900] RAX: 0000000000000005 RBX: 0000000000000010 RCX: 0000000000000000
    [295242.140120] RDX: 00007f9022282ba8 RSI: 00007f9022282a30 RDI: 00007f9014005c30
    [295242.147337] RBP: 00007f9014014d60 R08: 0000000000000020 R09: 00007f90254a8340
    [295242.154557] R10: 00007f9022282a28 R11: 0000000000000246 R12: 0000000000000000
    [295242.161775] R13: 00007f902308c000 R14: 000000000000002b R15: 00007f9022b71f40
    
    Fixes: 3fdbd1ce11e5 ("openvswitch: add ipv6 'set' action")
    Signed-off-by: Paul Blakey <paulb@nvidia.com>
    Link: https://lore.kernel.org/r/20220223163416.24096-1-paulb@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6c0d8833a605e195ae219b5042577ce52bf71fff
Author: Niels Dossche <dossche.niels@gmail.com>
Date:   Wed Feb 23 14:19:56 2022 +0100

    ipv6: prevent a possible race condition with lifetimes
    
    valid_lft, prefered_lft and tstamp are always accessed under the lock
    "lock" in other places. Reading these without taking the lock may result
    in inconsistencies regarding the calculation of the valid and preferred
    variables since decisions are taken on these fields for those variables.
    
    Signed-off-by: Niels Dossche <dossche.niels@gmail.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Signed-off-by: Niels Dossche <niels.dossche@ugent.be>
    Link: https://lore.kernel.org/r/20220223131954.6570-1-niels.dossche@ugent.be
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7ff57e98fb78ad94edafbdc7435f2d745e9e6bb5
Author: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Date:   Wed Feb 23 11:02:52 2022 +0100

    net/smc: Use a mutex for locking "struct smc_pnettable"
    
    smc_pnetid_by_table_ib() uses read_lock() and then it calls smc_pnet_apply_ib()
    which, in turn, calls mutex_lock(&smc_ib_devices.mutex).
    
    read_lock() disables preemption. Therefore, the code acquires a mutex while in
    atomic context and it leads to a SAC bug.
    
    Fix this bug by replacing the rwlock with a mutex.
    
    Reported-and-tested-by: syzbot+4f322a6d84e991c38775@syzkaller.appspotmail.com
    Fixes: 64e28b52c7a6 ("net/smc: add pnet table namespace support")
    Confirmed-by: Tony Lu <tonylu@linux.alibaba.com>
    Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
    Acked-by: Karsten Graul <kgraul@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220223100252.22562-1-fmdefrancesco@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e13ad1443684f7afaff24cf207e85e97885256bd
Author: Manish Chopra <manishc@marvell.com>
Date:   Wed Feb 23 00:57:20 2022 -0800

    bnx2x: fix driver load from initrd
    
    Commit b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0") added
    new firmware support in the driver with maintaining older firmware
    compatibility. However, older firmware was not added in MODULE_FIRMWARE()
    which caused missing firmware files in initrd image leading to driver load
    failure from initrd. This patch adds MODULE_FIRMWARE() for older firmware
    version to have firmware files included in initrd.
    
    Fixes: b7a49f73059f ("bnx2x: Utilize firmware 7.13.21.0")
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215627
    Signed-off-by: Manish Chopra <manishc@marvell.com>
    Signed-off-by: Alok Prasad <palok@marvell.com>
    Signed-off-by: Ariel Elior <aelior@marvell.com>
    Link: https://lore.kernel.org/r/20220223085720.12021-1-manishc@marvell.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e8240addd0a3919e0fd7436416afe9aa6429c484
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Tue Feb 22 01:18:17 2022 +0100

    Revert "xen-netback: Check for hotplug-status existence before watching"
    
    This reverts commit 2afeec08ab5c86ae21952151f726bfe184f6b23d.
    
    The reasoning in the commit was wrong - the code expected to setup the
    watch even if 'hotplug-status' didn't exist. In fact, it relied on the
    watch being fired the first time - to check if maybe 'hotplug-status' is
    already set to 'connected'. Not registering a watch for non-existing
    path (which is the case if hotplug script hasn't been executed yet),
    made the backend not waiting for the hotplug script to execute. This in
    turns, made the netfront think the interface is fully operational, while
    in fact it was not (the vif interface on xen-netback side might not be
    configured yet).
    
    This was a workaround for 'hotplug-status' erroneously being removed.
    But since that is reverted now, the workaround is not necessary either.
    
    More discussion at
    https://lore.kernel.org/xen-devel/afedd7cb-a291-e773-8b0d-4db9b291fa98@ipxe.org/T/#u
    
    Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
    Reviewed-by: Paul Durrant <paul@xen.org>
    Reviewed-by: Michael Brown <mbrown@fensystems.co.uk>
    Link: https://lore.kernel.org/r/20220222001817.2264967-2-marmarek@invisiblethingslab.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0f4558ae91870692ce7f509c31c9d6ee721d8cdc
Author: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Date:   Tue Feb 22 01:18:16 2022 +0100

    Revert "xen-netback: remove 'hotplug-status' once it has served its purpose"
    
    This reverts commit 1f2565780e9b7218cf92c7630130e82dcc0fe9c2.
    
    The 'hotplug-status' node should not be removed as long as the vif
    device remains configured. Otherwise the xen-netback would wait for
    re-running the network script even if it was already called (in case of
    the frontent re-connecting). But also, it _should_ be removed when the
    vif device is destroyed (for example when unbinding the driver) -
    otherwise hotplug script would not configure the device whenever it
    re-appear.
    
    Moving removal of the 'hotplug-status' node was a workaround for nothing
    calling network script after xen-netback module is reloaded. But when
    vif interface is re-created (on xen-netback unbind/bind for example),
    the script should be called, regardless of who does that - currently
    this case is not handled by the toolstack, and requires manual
    script call. Keeping hotplug-status=connected to skip the call is wrong
    and leads to not configured interface.
    
    More discussion at
    https://lore.kernel.org/xen-devel/afedd7cb-a291-e773-8b0d-4db9b291fa98@ipxe.org/T/#u
    
    Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
    Reviewed-by: Paul Durrant <paul@xen.org>
    Link: https://lore.kernel.org/r/20220222001817.2264967-1-marmarek@invisiblethingslab.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 558732df2122092259ab4ef85594bee11dbb9104
Author: Qu Wenruo <wqu@suse.com>
Date:   Sun Feb 13 15:42:33 2022 +0800

    btrfs: reduce extent threshold for autodefrag
    
    There is a big gap between inode_should_defrag() and autodefrag extent
    size threshold.  For inode_should_defrag() it has a flexible
    @small_write value. For compressed extent is 16K, and for non-compressed
    extent it's 64K.
    
    However for autodefrag extent size threshold, it's always fixed to the
    default value (256K).
    
    This means, the following write sequence will trigger autodefrag to
    defrag ranges which didn't trigger autodefrag:
    
      pwrite 0 8k
      sync
      pwrite 8k 128K
      sync
    
    The latter 128K write will also be considered as a defrag target (if
    other conditions are met). While only that 8K write is really
    triggering autodefrag.
    
    Such behavior can cause extra IO for autodefrag.
    
    Close the gap, by copying the @small_write value into inode_defrag, so
    that later autodefrag can use the same @small_write value which
    triggered autodefrag.
    
    With the existing transid value, this allows autodefrag really to scan
    the ranges which triggered autodefrag.
    
    Although this behavior change is mostly reducing the extent_thresh value
    for autodefrag, I believe in the future we should allow users to specify
    the autodefrag extent threshold through mount options, but that's an
    other problem to consider in the future.
    
    CC: stable@vger.kernel.org # 5.16+
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 228a26b912287934789023b4132ba76065d9491c
Author: James Morse <james.morse@arm.com>
Date:   Fri Dec 10 14:32:56 2021 +0000

    arm64: Use the clearbhb instruction in mitigations
    
    Future CPUs may implement a clearbhb instruction that is sufficient
    to mitigate SpectreBHB. CPUs that implement this instruction, but
    not CSV2.3 must be affected by Spectre-BHB.
    
    Add support to use this instruction as the BHB mitigation on CPUs
    that support it. The instruction is in the hint space, so it will
    be treated by a NOP as older CPUs.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit b2750f14007f0e1b36caf51058c161d2c93e63b6
Merge: bb49c6fa8b845 c2700d2886a87
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Feb 24 07:02:15 2022 -0700

    Merge tag 'nvme-5.17-2022-02-24' of git://git.infradead.org/nvme into block-5.17
    
    Pull NVMe fixes from Christoph:
    
    "nvme fixes for Linux 5.17
    
     - send H2CData PDUs based on MAXH2CDATA (Varun Prakash)
     - fix passthrough to namespaces with unsupported features (me)"
    
    * tag 'nvme-5.17-2022-02-24' of git://git.infradead.org/nvme:
      nvme-tcp: send H2CData PDUs based on MAXH2CDATA
      nvme: also mark passthrough-only namespaces ready in nvme_update_ns_info
      nvme: don't return an error from nvme_configure_metadata

commit a5905d6af492ee6a4a2205f0d550b3f931b03d03
Author: James Morse <james.morse@arm.com>
Date:   Fri Dec 10 11:16:18 2021 +0000

    KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
    
    KVM allows the guest to discover whether the ARCH_WORKAROUND SMCCC are
    implemented, and to preserve that state during migration through its
    firmware register interface.
    
    Add the necessary boiler plate for SMCCC_ARCH_WORKAROUND_3.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 558c303c9734af5a813739cd284879227f7297d2
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 10 14:48:00 2021 +0000

    arm64: Mitigate spectre style branch history side channels
    
    Speculation attacks against some high-performance processors can
    make use of branch history to influence future speculation.
    When taking an exception from user-space, a sequence of branches
    or a firmware call overwrites or invalidates the branch history.
    
    The sequence of branches is added to the vectors, and should appear
    before the first indirect branch. For systems using KPTI the sequence
    is added to the kpti trampoline where it has a free register as the exit
    from the trampoline is via a 'ret'. For systems not using KPTI, the same
    register tricks are used to free up a register in the vectors.
    
    For the firmware call, arch-workaround-3 clobbers 4 registers, so
    there is no choice but to save them to the EL1 stack. This only happens
    for entry from EL0, so if we take an exception due to the stack access,
    it will not become re-entrant.
    
    For KVM, the existing branch-predictor-hardening vectors are used.
    When a spectre version of these vectors is in use, the firmware call
    is sufficient to mitigate against Spectre-BHB. For the non-spectre
    versions, the sequence of branches is added to the indirect vector.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 19eae24b76c27dedfb166dc06a8c48e052cbc814
Merge: aaaba1c86d04d cfc4442c642d5
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Feb 24 14:51:45 2022 +0100

    Merge tag 'usb-serial-5.17-rc6' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-linus
    
    Johan writes:
    
    USB-serial fixes for 5.17-rc6
    
    Here's a revert of a commit which erroneously added a device id used for
    the EPP/MEM mode of ch341 devices.
    
    Included are also some new modem device ids.
    
    All have been in linux-next with no reported issues.
    
    * tag 'usb-serial-5.17-rc6' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial:
      USB: serial: option: add Telit LE910R1 compositions
      USB: serial: option: add support for DW5829e
      Revert "USB: serial: ch341: add new Product ID for CH341A"

commit 21d90aaee8d5c2a097ef41f1430d97661233ecc6
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Feb 24 11:18:48 2022 +0100

    surface: surface3_power: Fix battery readings on batteries without a serial number
    
    The battery on the 2nd hand Surface 3 which I recently bought appears to
    not have a serial number programmed in. This results in any I2C reads from
    the registers containing the serial number failing with an I2C NACK.
    
    This was causing mshw0011_bix() to fail causing the battery readings to
    not work at all.
    
    Ignore EREMOTEIO (I2C NACK) errors when retrieving the serial number and
    continue with an empty serial number to fix this.
    
    Fixes: b1f81b496b0d ("platform/x86: surface3_power: MSHW0011 rev-eng implementation")
    BugLink: https://github.com/linux-surface/linux-surface/issues/608
    Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
    Reviewed-by: Maximilian Luz <luzmaximilian@gmail.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220224101848.7219-1-hdegoede@redhat.com

commit 68af28426b3ca1bf9ba21c7d8bdd0ff639e5134c
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Wed Feb 23 11:52:37 2022 -0600

    platform/x86: amd-pmc: Set QOS during suspend on CZN w/ timer wakeup
    
    commit 59348401ebed ("platform/x86: amd-pmc: Add special handling for
    timer based S0i3 wakeup") adds support for using another platform timer
    in lieu of the RTC which doesn't work properly on some systems. This path
    was validated and worked well before submission. During the 5.16-rc1 merge
    window other patches were merged that caused this to stop working properly.
    
    When this feature was used with 5.16-rc1 or later some OEM laptops with the
    matching firmware requirements from that commit would shutdown instead of
    program a timer based wakeup.
    
    This was bisected to commit 8d89835b0467 ("PM: suspend: Do not pause
    cpuidle in the suspend-to-idle path").  This wasn't supposed to cause any
    negative impacts and also tested well on both Intel and ARM platforms.
    However this changed the semantics of when CPUs are allowed to be in the
    deepest state. For the AMD systems in question it appears this causes a
    firmware crash for timer based wakeup.
    
    It's hypothesized to be caused by the `amd-pmc` driver sending `OS_HINT`
    and all the CPUs going into a deep state while the timer is still being
    programmed. It's likely a firmware bug, but to avoid it don't allow setting
    CPUs into the deepest state while using CZN timer wakeup path.
    
    If later it's discovered that this also occurs from "regular" suspends
    without a timer as well or on other silicon, this may be later expanded to
    run in the suspend path for more scenarios.
    
    Cc: stable@vger.kernel.org # 5.16+
    Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Link: https://lore.kernel.org/linux-acpi/BL1PR12MB51570F5BD05980A0DCA1F3F4E23A9@BL1PR12MB5157.namprd12.prod.outlook.com/T/#mee35f39c41a04b624700ab2621c795367f19c90e
    Fixes: 8d89835b0467 ("PM: suspend: Do not pause cpuidle in the suspend-to-idle path")
    Fixes: 23f62d7ab25b ("PM: sleep: Pause cpuidle later and resume it earlier during system transitions")
    Fixes: 59348401ebed ("platform/x86: amd-pmc: Add special handling for timer based S0i3 wakeup"
    Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Link: https://lore.kernel.org/r/20220223175237.6209-1-mario.limonciello@amd.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit aaaba1c86d04dac8e49bf508b492f81506257da3
Author: Daehwan Jung <dh10.jung@samsung.com>
Date:   Tue Feb 22 14:29:28 2022 +0900

    usb: gadget: rndis: add spinlock for rndis response list
    
    There's no lock for rndis response list. It could cause list corruption
    if there're two different list_add at the same time like below.
    It's better to add in rndis_add_response / rndis_free_response
    / rndis_get_next_response to prevent any race condition on response list.
    
    [  361.894299] [1:   irq/191-dwc3:16979] list_add corruption.
    next->prev should be prev (ffffff80651764d0),
    but was ffffff883dc36f80. (next=ffffff80651764d0).
    
    [  361.904380] [1:   irq/191-dwc3:16979] Call trace:
    [  361.904391] [1:   irq/191-dwc3:16979]  __list_add_valid+0x74/0x90
    [  361.904401] [1:   irq/191-dwc3:16979]  rndis_msg_parser+0x168/0x8c0
    [  361.904409] [1:   irq/191-dwc3:16979]  rndis_command_complete+0x24/0x84
    [  361.904417] [1:   irq/191-dwc3:16979]  usb_gadget_giveback_request+0x20/0xe4
    [  361.904426] [1:   irq/191-dwc3:16979]  dwc3_gadget_giveback+0x44/0x60
    [  361.904434] [1:   irq/191-dwc3:16979]  dwc3_ep0_complete_data+0x1e8/0x3a0
    [  361.904442] [1:   irq/191-dwc3:16979]  dwc3_ep0_interrupt+0x29c/0x3dc
    [  361.904450] [1:   irq/191-dwc3:16979]  dwc3_process_event_entry+0x78/0x6cc
    [  361.904457] [1:   irq/191-dwc3:16979]  dwc3_process_event_buf+0xa0/0x1ec
    [  361.904465] [1:   irq/191-dwc3:16979]  dwc3_thread_interrupt+0x34/0x5c
    
    Fixes: f6281af9d62e ("usb: gadget: rndis: use list_for_each_entry_safe")
    Cc: stable <stable@kernel.org>
    Signed-off-by: Daehwan Jung <dh10.jung@samsung.com>
    Link: https://lore.kernel.org/r/1645507768-77687-1-git-send-email-dh10.jung@samsung.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 84918a89d6efaff075de570b55642b6f4ceeac6d
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Fri Feb 18 18:32:45 2022 +0100

    usb: dwc3: gadget: Let the interrupt handler disable bottom halves.
    
    The interrupt service routine registered for the gadget is a primary
    handler which mask the interrupt source and a threaded handler which
    handles the source of the interrupt. Since the threaded handler is
    voluntary threaded, the IRQ-core does not disable bottom halves before
    invoke the handler like it does for the forced-threaded handler.
    
    Due to changes in networking it became visible that a network gadget's
    completions handler may schedule a softirq which remains unprocessed.
    The gadget's completion handler is usually invoked either in hard-IRQ or
    soft-IRQ context. In this context it is enough to just raise the softirq
    because the softirq itself will be handled once that context is left.
    In the case of the voluntary threaded handler, there is nothing that
    will process pending softirqs. Which means it remain queued until
    another random interrupt (on this CPU) fires and handles it on its exit
    path or another thread locks and unlocks a lock with the bh suffix.
    Worst case is that the CPU goes idle and the NOHZ complains about
    unhandled softirqs.
    
    Disable bottom halves before acquiring the lock (and disabling
    interrupts) and enable them after dropping the lock. This ensures that
    any pending softirqs will handled right away.
    
    Link: https://lkml.kernel.org/r/c2a64979-73d1-2c22-e048-c275c9f81558@samsung.com
    Fixes: e5f68b4a3e7b0 ("Revert "usb: dwc3: gadget: remove unnecessary _irqsave()"")
    Cc: stable <stable@kernel.org>
    Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Link: https://lore.kernel.org/r/Yg/YPejVQH3KkRVd@linutronix.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 7f14c7227f342d9932f9b918893c8814f86d2a0d
Author: Szymon Heidrich <szymon.heidrich@gmail.com>
Date:   Mon Feb 21 13:24:56 2022 +0100

    USB: gadget: validate endpoint index for xilinx udc
    
    Assure that host may not manipulate the index to point
    past endpoint array.
    
    Signed-off-by: Szymon Heidrich <szymon.heidrich@gmail.com>
    Cc: stable <stable@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5facf49702b6d994d3f1c72cffa0e83f3858ee19
Merge: 0228d37bd1a4f ca49df96f9f5e
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Feb 23 20:30:00 2022 -0800

    Merge tag 'mlx5-fixes-2022-02-23' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
    
    Saeed Mahameed says:
    
    ====================
    mlx5 fixes 2022-02-22
    
    This series provides bug fixes to mlx5 driver.
    Please pull and let me know if there is any problem.
    
    * tag 'mlx5-fixes-2022-02-23' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux:
      net/mlx5e: Fix VF min/max rate parameters interchange mistake
      net/mlx5e: Add missing increment of count
      net/mlx5e: MPLSoUDP decap, fix check for unsupported matches
      net/mlx5e: Fix MPLSoUDP encap to use MPLS action information
      net/mlx5e: Add feature check for set fec counters
      net/mlx5e: TC, Skip redundant ct clear actions
      net/mlx5e: TC, Reject rules with forward and drop actions
      net/mlx5e: TC, Reject rules with drop and modify hdr action
      net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
      net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
      net/mlx5: Fix possible deadlock on rule deletion
      net/mlx5: Fix tc max supported prio for nic mode
      net/mlx5: Fix wrong limitation of metadata match on ecpf
      net/mlx5: Update log_max_qp value to be 17 at most
      net/mlx5: DR, Fix the threshold that defines when pool sync is initiated
      net/mlx5: DR, Don't allow match on IP w/o matching on full ethertype/ip_version
      net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
      net/mlx5: DR, Cache STE shadow memory
      net/mlx5: Update the list of the PCI supported devices
    ====================
    
    Link: https://lore.kernel.org/r/20220224001123.365265-1-saeed@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7c17b3d37f1fa1eb0498cdf63d43ce37b23eaae5
Merge: 0c3127933cb5e c1a66c3bc425f
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 24 14:27:35 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-02-23' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-02-23:
    
    amdgpu:
    - Display FP fix
    - PCO powergating fix
    - RDNA2 OEM SKU stability fixes
    - Display PSR fix
    - PCI ASPM fix
    - Display link encoder fix for TEST_COMMIT
    - Raven2 suspend/resume fix
    - Fix a regression in virtual display support
    - GPUVM eviction fix
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220223214623.28823-1-alexander.deucher@amd.com

commit 0c3127933cb5ee73784bdf6881525d1efc1d4b34
Merge: 753a64c779903 8913e1aea4b32
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 24 14:21:57 2022 +1000

    Merge tag 'drm/tegra/for-5.17-rc6' of https://gitlab.freedesktop.org/drm/tegra into drm-fixes
    
    drm/tegra: Fixes for v5.17-rc6
    
    Contains a couple of fixes for Tegra186 suspend/resume, syncpoint
    waiting, a build warning and eDP on older Tegra devices.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thierry Reding <thierry.reding@gmail.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220223161903.293392-1-thierry.reding@gmail.com

commit 753a64c7799034a413083ad03b9fe51dfcad9fb2
Merge: cfb92440ee71a ecbd4912a693b
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 24 13:51:46 2022 +1000

    Merge tag 'drm-misc-fixes-2022-02-23' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * edid: Always set RGB444
     * imx/dcss: Select GEM CMA helpers
     * radeon: Fix some variables's type
     * vc4: Fix codec cleanup; Fix PM reference counting
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YhaKj4zWJ42YWRts@linux-uq9g.fritz.box

commit 7414db411919980bc4c9bab11d5d040b5dd7667c
Author: Arnaldo Carvalho de Melo <acme@kernel.org>
Date:   Wed Feb 23 14:18:31 2022 -0300

    rtla: Fix systme -> system typo on man page
    
    Link: https://lkml.kernel.org/r/YhZsZxqk+IaFxorj@kernel.org
    
    Fixes: 496082df01bb08a4 ("rtla: Add rtla osnoise man page")
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 91318b29a81cf51451ecf1c0054898f67dc26d87
Merge: 54134be658036 0c0822bcb73f1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 23 17:25:22 2022 -0800

    Merge tag 'devicetree-fixes-for-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
    
    Pull devicetree fixes from Rob Herring:
    
     - Update some maintainers email addresses
    
     - Fix handling of elfcorehdr reservation for crash dump kernel
    
     - Fix unittest expected warnings text
    
    * tag 'devicetree-fixes-for-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux:
      dt-bindings: update Roger Quadros email
      MAINTAINERS: sifive: drop Yash Shah
      of/fdt: move elfcorehdr reservation early for crash dump kernel
      of: unittest: update text of expected warnings

commit 54134be6580364ab98db09eb8070a09bb02e37ae
Merge: 23d04328444a8 ce2fc710c9d2b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 23 17:19:55 2022 -0800

    Merge tag 'selinux-pr-20220223' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux
    
    Pull selinux fix from Paul Moore:
     "A second small SELinux fix which addresses an incorrect
      mutex_is_locked() check"
    
    * tag 'selinux-pr-20220223' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux:
      selinux: fix misuse of mutex_is_locked()

commit ca49df96f9f5efd4f0f1e64f7c4c0c63a3329cb9
Author: Gal Pressman <gal@nvidia.com>
Date:   Mon Feb 21 17:54:34 2022 +0200

    net/mlx5e: Fix VF min/max rate parameters interchange mistake
    
    The VF min and max rate were passed incorrectly and resulted in wrongly
    interchanging them. Fix the order of parameters in
    mlx5_esw_qos_set_vport_rate().
    
    Fixes: d7df09f5e7b4 ("net/mlx5: E-switch, Enable vport QoS on demand")
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Aya Levin <ayal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5ee02b7a800654ff9549807bcf0b4c9fd5cf25f9
Author: Lama Kayal <lkayal@nvidia.com>
Date:   Mon Feb 21 12:26:11 2022 +0200

    net/mlx5e: Add missing increment of count
    
    Add mistakenly missing increment of count variable when looping over
    output buffer in mlx5e_self_test().
    
    This resolves the issue of garbage values output when querying with self
    test via ethtool.
    
    before:
    $ ethtool -t eth2
    The test result is PASS
    The test extra info:
    Link Test        0
    Speed Test       1768697188
    Health Test      758528120
    Loopback Test    3288687
    
    after:
    $ ethtool -t eth2
    The test result is PASS
    The test extra info:
    Link Test        0
    Speed Test       0
    Health Test      0
    Loopback Test    0
    
    Fixes: 7990b1b5e8bd ("net/mlx5e: loopback test is not supported in switchdev mode")
    Signed-off-by: Lama Kayal <lkayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit fdc18e4e4bded2a08638cdcd22dc087a64b9ddad
Author: Maor Dickman <maord@nvidia.com>
Date:   Thu Jan 6 14:46:24 2022 +0200

    net/mlx5e: MPLSoUDP decap, fix check for unsupported matches
    
    Currently offload of rule on bareudp device require tunnel key
    in order to match on mpls fields and without it the mpls fields
    are ignored, this is incorrect due to the fact udp tunnel doesn't
    have key to match on.
    
    Fix by returning error in case flow is matching on tunnel key.
    
    Fixes: 72046a91d134 ("net/mlx5e: Allow to match on mpls parameters")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit c63741b426e11062631b013c3396f5452bbc0034
Author: Maor Dickman <maord@nvidia.com>
Date:   Thu Jan 6 14:10:18 2022 +0200

    net/mlx5e: Fix MPLSoUDP encap to use MPLS action information
    
    Currently the MPLSoUDP encap builds the MPLS header using encap action
    information (tunnel id, ttl and tos) instead of the MPLS action
    information (label, ttl, tc and bos) which is wrong.
    
    Fix by storing the MPLS action information during the flow action
    parse and later using it to create the encap MPLS header.
    
    Fixes: f828ca6a2fb6 ("net/mlx5e: Add support for hw encapsulation of MPLS over UDP")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 7fac0529038021919ef56a9c3218d8012f187cbb
Author: Lama Kayal <lkayal@nvidia.com>
Date:   Tue Feb 1 11:24:41 2022 +0200

    net/mlx5e: Add feature check for set fec counters
    
    Fec counters support is checked via the PCAM feature_cap_mask,
    bit 0: PPCNT_counter_group_Phy_statistical_counter_group.
    Add feature check to avoid faulty behavior.
    
    Fixes: 0a1498ebfa55 ("net/mlx5e: Expose FEC counters via ethtool")
    Signed-off-by: Lama Kayal <lkayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit fb7e76ea3f3b6238dda2f19a4212052d2caf00aa
Author: Roi Dayan <roid@nvidia.com>
Date:   Thu Feb 3 09:42:19 2022 +0200

    net/mlx5e: TC, Skip redundant ct clear actions
    
    Offload of ct clear action is just resetting the reg_c register.
    It's done by allocating modify hdr resources which is limited.
    Doing it multiple times is redundant and wasting modify hdr resources
    and if resources depleted the driver will fail offloading the rule.
    Ignore redundant ct clear actions after the first one.
    
    Fixes: 806401c20a0f ("net/mlx5e: CT, Fix multiple allocations and memleak of mod acts")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Ariel Levkovich <lariel@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 3d65492a86d4e6675734646929759138a023d914
Author: Roi Dayan <roid@nvidia.com>
Date:   Mon Jan 17 15:00:30 2022 +0200

    net/mlx5e: TC, Reject rules with forward and drop actions
    
    Such rules are redundant but allowed and passed to the driver.
    The driver does not support offloading such rules so return an error.
    
    Fixes: 03a9d11e6eeb ("net/mlx5e: Add TC drop and mirred/redirect action parsing for SRIOV offloads")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Oz Shlomo <ozsh@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 23216d387c40b090b221ad457c95912fb47eb11e
Author: Roi Dayan <roid@nvidia.com>
Date:   Tue Jan 4 10:38:02 2022 +0200

    net/mlx5e: TC, Reject rules with drop and modify hdr action
    
    This kind of action is not supported by firmware and generates a
    syndrome.
    
    kernel: mlx5_core 0000:08:00.0: mlx5_cmd_check:777:(pid 102063): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x8708c3)
    
    Fixes: d7e75a325cb2 ("net/mlx5e: Add offloading of E-Switch TC pedit (header re-write) actions")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Oz Shlomo <ozsh@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 7eaf1f37b8817c608c4e959d69986ef459d345cd
Author: Tariq Toukan <tariqt@nvidia.com>
Date:   Mon Jan 31 10:26:19 2022 +0200

    net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
    
    For RX TLS device-offloaded packets, the HW spec guarantees checksum
    validation for the offloaded packets, but does not define whether the
    CQE.checksum field matches the original packet (ciphertext) or
    the decrypted one (plaintext). This latitude allows architetctural
    improvements between generations of chips, resulting in different decisions
    regarding the value type of CQE.checksum.
    
    Hence, for these packets, the device driver should not make use of this CQE
    field. Here we block CHECKSUM_COMPLETE usage for RX TLS device-offloaded
    packets, and use CHECKSUM_UNNECESSARY instead.
    
    Value of the packet's tcp_hdr.csum is not modified by the HW, and it always
    matches the original ciphertext.
    
    Fixes: 1182f3659357 ("net/mlx5e: kTLS, Add kTLS RX HW offload support")
    Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 0b89429722353d112f8b8b29ca397e95fa994d27
Author: Gal Pressman <gal@nvidia.com>
Date:   Wed Feb 2 16:07:21 2022 +0200

    net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
    
    The ioctl EEPROM query wrongly returns success on read failures, fix
    that by returning the appropriate error code.
    
    Fixes: bb64143eee8c ("net/mlx5e: Add ethtool support for dump module EEPROM")
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit b645e57debca846f51b3209907546ea857ddd3f5
Author: Maor Gottlieb <maorg@nvidia.com>
Date:   Mon Jan 24 21:25:04 2022 +0200

    net/mlx5: Fix possible deadlock on rule deletion
    
    Add missing call to up_write_ref_node() which releases the semaphore
    in case the FTE doesn't have destinations, such in drop rule case.
    
    Fixes: 465e7baab6d9 ("net/mlx5: Fix deletion of duplicate rules")
    Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
    Reviewed-by: Mark Bloch <mbloch@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit be7f4b0ab149afd19514929fad824b2117d238c9
Author: Chris Mi <cmi@nvidia.com>
Date:   Tue Dec 14 03:52:53 2021 +0200

    net/mlx5: Fix tc max supported prio for nic mode
    
    Only prio 1 is supported if firmware doesn't support ignore flow
    level for nic mode. The offending commit removed the check wrongly.
    Add it back.
    
    Fixes: 9a99c8f1253a ("net/mlx5e: E-Switch, Offload all chain 0 priorities when modify header and forward action is not supported")
    Signed-off-by: Chris Mi <cmi@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 07666c75ad17d7389b18ac0235c8cf41e1504ea8
Author: Ariel Levkovich <lariel@nvidia.com>
Date:   Sat Jan 29 01:39:24 2022 +0200

    net/mlx5: Fix wrong limitation of metadata match on ecpf
    
    Match metadata support check returns false for ecpf device.
    However, this support does exist for ecpf and therefore this
    limitation should be removed to allow feature such as stacked
    devices and internal port offloaded to be supported.
    
    Fixes: 92ab1eb392c6 ("net/mlx5: E-Switch, Enable vport metadata matching if firmware supports it")
    Signed-off-by: Ariel Levkovich <lariel@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 7f839965b2d77e1926ad08b23c51d60988f10a99
Author: Maher Sanalla <msanalla@nvidia.com>
Date:   Wed Feb 16 11:01:04 2022 +0200

    net/mlx5: Update log_max_qp value to be 17 at most
    
    Currently, log_max_qp value is dependent on what FW reports as its max capability.
    In reality, due to a bug, some FWs report a value greater than 17, even though they
    don't support log_max_qp > 17.
    
    This FW issue led the driver to exhaust memory on startup.
    Thus, log_max_qp value is set to be no more than 17 regardless
    of what FW reports, as it was before the cited commit.
    
    Fixes: f79a609ea6bf ("net/mlx5: Update log_max_qp value to FW max capability")
    Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
    Reviewed-by: Avihai Horon <avihaih@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit ecd9c5cd46e013659e2fad433057bad1ba66888e
Author: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date:   Wed Dec 29 22:22:05 2021 +0200

    net/mlx5: DR, Fix the threshold that defines when pool sync is initiated
    
    When deciding whether to start syncing and actually free all the "hot"
    ICM chunks, we need to consider the type of the ICM chunks that we're
    dealing with. For instance, the amount of available ICM for MODIFY_ACTION
    is significantly lower than the usual STE ICM, so the threshold should
    account for that - otherwise we can deplete MODIFY_ACTION memory just by
    creating and deleting the same modify header action in a continuous loop.
    
    This patch replaces the hard-coded threshold with a dynamic value.
    
    Fixes: 1c58651412bb ("net/mlx5: DR, ICM memory pools sync optimization")
    Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
    Reviewed-by: Alex Vesker <valex@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit ffb0753b954763d94f52c901adfe58ed0d4005e6
Author: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date:   Thu Jan 13 14:52:48 2022 +0200

    net/mlx5: DR, Don't allow match on IP w/o matching on full ethertype/ip_version
    
    Currently SMFS allows adding rule with matching on src/dst IP w/o matching
    on full ethertype or ip_version, which is not supported by HW.
    This patch fixes this issue and adds the check as it is done in DMFS.
    
    Fixes: 26d688e33f88 ("net/mlx5: DR, Add Steering entry (STE) utilities")
    Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
    Reviewed-by: Alex Vesker <valex@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 0aec12d97b2036af0946e3d582144739860ac07b
Author: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date:   Tue Jan 11 03:00:03 2022 +0200

    net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
    
    When adding a rule with 32 destinations, we hit the following out-of-band
    access issue:
    
      BUG: KASAN: slab-out-of-bounds in mlx5_cmd_dr_create_fte+0x18ee/0x1e70
    
    This patch fixes the issue by both increasing the allocated buffers to
    accommodate for the needed actions and by checking the number of actions
    to prevent this issue when a rule with too many actions is provided.
    
    Fixes: 1ffd498901c1 ("net/mlx5: DR, Increase supported num of actions to 32")
    Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
    Reviewed-by: Alex Vesker <valex@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit e5b2bc30c21139ae10f0e56989389d0bc7b7b1d6
Author: Yevgeny Kliteynik <kliteyn@nvidia.com>
Date:   Fri Dec 24 01:07:30 2021 +0200

    net/mlx5: DR, Cache STE shadow memory
    
    During rule insertion on each ICM memory chunk we also allocate shadow memory
    used for management. This includes the hw_ste, dr_ste and miss list per entry.
    Since the scale of these allocations is large we noticed a performance hiccup
    that happens once malloc and free are stressed.
    In extreme usecases when ~1M chunks are freed at once, it might take up to 40
    seconds to complete this, up to the point the kernel sees this as self-detected
    stall on CPU:
    
     rcu: INFO: rcu_sched self-detected stall on CPU
    
    To resolve this we will increase the reuse of shadow memory.
    Doing this we see that a time in the aforementioned usecase dropped from ~40
    seconds to ~8-10 seconds.
    
    Fixes: 29cf8febd185 ("net/mlx5: DR, ICM pool memory allocator")
    Signed-off-by: Alex Vesker <valex@nvidia.com>
    Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit f908a35b22180c4da64cf2647e4f5f0cd3054da7
Author: Meir Lichtinger <meirl@nvidia.com>
Date:   Mon Jan 10 10:14:41 2022 +0200

    net/mlx5: Update the list of the PCI supported devices
    
    Add the upcoming BlueField-4 and ConnectX-8 device IDs.
    
    Fixes: 2e9d3e83ab82 ("net/mlx5: Update the list of the PCI supported devices")
    Signed-off-by: Meir Lichtinger <meirl@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit c1a66c3bc425ff93774fb2f6eefa67b83170dd7e
Author: Qiang Yu <qiang.yu@amd.com>
Date:   Mon Feb 21 17:53:56 2022 +0800

    drm/amdgpu: check vm ready by amdgpu_vm->evicting flag
    
    Workstation application ANSA/META v21.1.4 get this error dmesg when
    running CI test suite provided by ANSA/META:
    [drm:amdgpu_gem_va_ioctl [amdgpu]] *ERROR* Couldn't update BO_VA (-16)
    
    This is caused by:
    1. create a 256MB buffer in invisible VRAM
    2. CPU map the buffer and access it causes vm_fault and try to move
       it to visible VRAM
    3. force visible VRAM space and traverse all VRAM bos to check if
       evicting this bo is valuable
    4. when checking a VM bo (in invisible VRAM), amdgpu_vm_evictable()
       will set amdgpu_vm->evicting, but latter due to not in visible
       VRAM, won't really evict it so not add it to amdgpu_vm->evicted
    5. before next CS to clear the amdgpu_vm->evicting, user VM ops
       ioctl will pass amdgpu_vm_ready() (check amdgpu_vm->evicted)
       but fail in amdgpu_vm_bo_update_mapping() (check
       amdgpu_vm->evicting) and get this error log
    
    This error won't affect functionality as next CS will finish the
    waiting VM ops. But we'd better clear the error log by checking
    the amdgpu_vm->evicting flag in amdgpu_vm_ready() to stop calling
    amdgpu_vm_bo_update_mapping() later.
    
    Another reason is amdgpu_vm->evicted list holds all BOs (both
    user buffer and page table), but only page table BOs' eviction
    prevent VM ops. amdgpu_vm->evicting flag is set only for page
    table BOs, so we should use evicting flag instead of evicted list
    in amdgpu_vm_ready().
    
    The side effect of this change is: previously blocked VM op (user
    buffer in "evicted" list but no page table in it) gets done
    immediately.
    
    v2: update commit comments.
    
    Acked-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Qiang Yu <qiang.yu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit e2b993302f40c4eb714ecf896dd9e1c5be7d4cd7
Author: Guchun Chen <guchun.chen@amd.com>
Date:   Fri Feb 18 13:05:26 2022 +0800

    drm/amdgpu: bypass tiling flag check in virtual display case (v2)
    
    vkms leverages common amdgpu framebuffer creation, and
    also as it does not support FB modifier, there is no need
    to check tiling flags when initing framebuffer when virtual
    display is enabled.
    
    This can fix below calltrace:
    
    amdgpu 0000:00:08.0: GFX9+ requires FB check based on format modifier
    WARNING: CPU: 0 PID: 1023 at drivers/gpu/drm/amd/amdgpu/amdgpu_display.c:1150 amdgpu_display_framebuffer_init+0x8e7/0xb40 [amdgpu]
    
    v2: check adev->enable_virtual_display instead as vkms can be
            enabled in bare metal as well.
    
    Signed-off-by: Leslie Shi <Yuliang.Shi@amd.com>
    Signed-off-by: Guchun Chen <guchun.chen@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 97c61e0b7c596cc5f683da30289f92c2e1b4b799
Author: Guchun Chen <guchun.chen@amd.com>
Date:   Fri Feb 18 12:57:52 2022 +0800

    Revert "drm/amdgpu: add modifiers in amdgpu_vkms_plane_init()"
    
    This reverts commit 4046afcebfc3c8c0dd5666c2671b2c192b344f78.
    
    No need to support modifier in virtual kms, otherwise, in SRIOV
    mode, when lanuching X server, set crtc will fail due to mismatch
    between primary plane modifier and framebuffer modifier.
    
    Signed-off-by: Guchun Chen <guchun.chen@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 1e2be869c8a7247a7253ef4f461f85e2f5931b95
Author: Chen Gong <curry.gong@amd.com>
Date:   Thu Feb 17 15:29:41 2022 +0800

    drm/amdgpu: do not enable asic reset for raven2
    
    The GPU reset function of raven2 is not maintained or tested, so it should be
    very unstable.
    
    Now the amdgpu_asic_reset function is added to amdgpu_pmops_suspend, which
    causes the S3 test of raven2 to fail, so the asic_reset of raven2 is ignored
    here.
    
    Fixes: daf8de0874ab5b ("drm/amdgpu: always reset the asic in suspend (v2)")
    Signed-off-by: Chen Gong <curry.gong@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 3743e7f6fcb938b7d8b7967e6a9442805e269b3d
Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Date:   Tue Jan 25 12:04:34 2022 -0500

    drm/amd/display: Fix stream->link_enc unassigned during stream removal
    
    [Why]
    Found when running igt@kms_atomic.
    
    Userspace attempts to do a TEST_COMMIT when 0 streams which calls
    dc_remove_stream_from_ctx. This in turn calls link_enc_unassign
    which ends up modifying stream->link = NULL directly, causing the
    global link_enc to be removed preventing further link activity
    and future link validation from passing.
    
    [How]
    We take care of link_enc unassignment at the start of
    link_enc_cfg_link_encs_assign so this call is no longer necessary.
    
    Fixes global state from being modified while unlocked.
    
    Reviewed-by: Jimmy Kizito <Jimmy.Kizito@amd.com>
    Acked-by: Jasdeep Dhillon <jdhillon@amd.com>
    Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 7294863a6f01248d72b61d38478978d638641bee
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Feb 1 10:26:33 2022 -0600

    drm/amd: Check if ASPM is enabled from PCIe subsystem
    
    commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
    by default but a variety of hardware configurations it turns out that this
    caused a regression.
    
    * PPC64LE hardware does not support ASPM at a hardware level.
      CONFIG_PCIEASPM is often disabled on these architectures.
    * Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe subsystem
      disables it
    
    Check with the PCIe subsystem to see that ASPM has been enabled
    or not.
    
    Fixes: 0064b0ce85bb ("drm/amd/pm: enable ASPM by default")
    Link: https://wiki.raptorcs.com/w/images/a/ad/P9_PHB_version1.0_27July2018_pub.pdf
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1723
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1739
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1885
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1907
    Tested-by: koba.ko@canonical.com
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit ae42f9288846353982e2eab181fb41e7fd8bf60f
Author: Shreeya Patel <shreeya.patel@collabora.com>
Date:   Thu Feb 17 01:56:55 2022 +0530

    gpio: Return EPROBE_DEFER if gc->to_irq is NULL
    
    We are racing the registering of .to_irq when probing the
    i2c driver. This results in random failure of touchscreen
    devices.
    
    Following explains the race condition better.
    
    [gpio driver] gpio driver registers gpio chip
    [gpio consumer] gpio is acquired
    [gpio consumer] gpiod_to_irq() fails with -ENXIO
    [gpio driver] gpio driver registers irqchip
    gpiod_to_irq works at this point, but -ENXIO is fatal
    
    We could see the following errors in dmesg logs when gc->to_irq is NULL
    
    [2.101857] i2c_hid i2c-FTS3528:00: HID over i2c has not been provided an Int IRQ
    [2.101953] i2c_hid: probe of i2c-FTS3528:00 failed with error -22
    
    To avoid this situation, defer probing until to_irq is registered.
    Returning -EPROBE_DEFER would be the first step towards avoiding
    the failure of devices due to the race in registration of .to_irq.
    Final solution to this issue would be to avoid using gc irq members
    until they are fully initialized.
    
    This issue has been reported many times in past and people have been
    using workarounds like changing the pinctrl_amd to built-in instead
    of loading it as a module or by adding a softdep for pinctrl_amd into
    the config file.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=209413
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 23d04328444a8fa0ca060c5e532220dac8e8bc26
Merge: 6f5738db96ddc a97279836867b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 23 12:06:23 2022 -0800

    Merge tag 'for-5.17/parisc-4' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
    
    Pull parisc unaligned handler fixes from Helge Deller:
     "Two patches which fix a few bugs in the unalignment handlers.
    
      The fldd and fstd instructions weren't handled at all on 32-bit
      kernels, the stw instruction didn't check for fault errors and the
      fldw_l and ldw_m were handled wrongly as integer vs floating point
      instructions.
    
      Both patches are tagged for stable series"
    
    * tag 'for-5.17/parisc-4' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
      parisc/unaligned: Fix ldw() and stw() unalignment handlers
      parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel

commit 6f5738db96ddc3525de21990ed569ef43e05f42d
Merge: 4eb0a7c8e195d 35f165f08950a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 23 11:51:35 2022 -0800

    Merge tag 'hwmon-for-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
    
    Pull hwmon fixes from Guenter Roeck:
     "Fix two old bugs and one new bug in the hwmon subsystem:
    
       - In pmbus core, clear pmbus fault/warning status bits after read to
         follow PMBus standard
    
       - In hwmon core, handle failure to register sensor with thermal zone
         correctly
    
       - In ntc_thermal driver, use valid thermistor names for Samsung
         thermistors"
    
    * tag 'hwmon-for-v5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
      hwmon: (pmbus) Clear pmbus fault/warning bits after read
      hwmon: Handle failure to register sensor with thermal zone correctly
      hwmon: (ntc_thermistor) Underscore Samsung thermistor

commit 4eb0a7c8e195d4549221f9df3a0313254c493949
Merge: 5c1ee569660d4 221944736f66f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 23 11:33:12 2022 -0800

    Merge tag 'slab-for-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab
    
    Pull slab fixes from Vlastimil Babka:
    
     - Build fix (workaround) for clang.
    
     - Fix a /proc/kcore based slabinfo script broken by struct slab changes
       in 5.17-rc1.
    
    * tag 'slab-for-5.17-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab:
      tools/cgroup/slabinfo: update to work with struct slab
      slab: remove __alloc_size attribute from __kmalloc_track_caller

commit 081bdc9fe05bb23248f5effb6f811da3da4b8252
Author: Bart Van Assche <bvanassche@acm.org>
Date:   Tue Feb 15 13:05:11 2022 -0800

    RDMA/ib_srp: Fix a deadlock
    
    Remove the flush_workqueue(system_long_wq) call since flushing
    system_long_wq is deadlock-prone and since that call is redundant with a
    preceding cancel_work_sync()
    
    Link: https://lore.kernel.org/r/20220215210511.28303-3-bvanassche@acm.org
    Fixes: ef6c49d87c34 ("IB/srp: Eliminate state SRP_TARGET_DEAD")
    Reported-by: syzbot+831661966588c802aae9@syzkaller.appspotmail.com
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 515415d316168c6521d74ea8280287e28d7303e6
Author: Maxime Ripard <maxime@cerno.tech>
Date:   Sat Feb 19 13:07:55 2022 +0100

    ARM: boot: dts: bcm2711: Fix HVS register range
    
    While the HVS has the same context memory size in the BCM2711 than in
    the previous SoCs, the range allocated to the registers doubled and it
    now takes 16k + 16k, compared to 8k + 16k before.
    
    The KMS driver will use the whole context RAM though, eventually
    resulting in a pointer dereference error when we access the higher half
    of the context memory since it hasn't been mapped.
    
    Fixes: 4564363351e2 ("ARM: dts: bcm2711: Enable the display pipeline")
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

commit 3f1271b54edcc692da5a3663f2aa2a64781f9bc3
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Tue Feb 22 11:08:01 2022 -0500

    PCI: Mark all AMD Navi10 and Navi14 GPU ATS as broken
    
    There are enough VBIOS escapes without the proper workaround that some
    users still hit this.  Microsoft never productized ATS on Windows so OEM
    platforms that were Windows-only didn't always validate ATS.
    
    The advantages of ATS are not worth it compared to the potential
    instabilities on harvested boards.  Disable ATS on all Navi10 and Navi14
    boards.
    
    Symptoms include:
    
      amdgpu 0000:07:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0007 address=0xffffc02000 flags=0x0000]
      AMD-Vi: Event logged [IO_PAGE_FAULT device=07:00.0 domain=0x0007 address=0xffffc02000 flags=0x0000]
      [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=6047, emitted seq=6049
      amdgpu 0000:07:00.0: amdgpu: GPU reset begin!
      amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
      amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
      [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v4_0> failed -110
      amdgpu 0000:07:00.0: amdgpu: GPU reset(1) failed
    
    Related commits:
    
      e8946a53e2a6 ("PCI: Mark AMD Navi14 GPU ATS as broken")
      a2da5d8cc0b0 ("PCI: Mark AMD Raven iGPU ATS as broken in some platforms")
      45beb31d3afb ("PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken")
      5e89cd303e3a ("PCI: Mark AMD Navi14 GPU rev 0xc5 ATS as broken")
      d28ca864c493 ("PCI: Mark AMD Stoney Radeon R7 GPU ATS as broken")
      9b44b0b09dec ("PCI: Mark AMD Stoney GPU ATS as broken")
    
    [bhelgaas: add symptoms and related commits]
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1760
    Link: https://lore.kernel.org/r/20220222160801.841643-1-alexander.deucher@amd.com
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Acked-by: Guchun Chen <guchun.chen@amd.com>

commit a97279836867b1cb50a3d4f0b1bf60e0abe6d46c
Author: Helge Deller <deller@gmx.de>
Date:   Fri Feb 18 23:40:14 2022 +0100

    parisc/unaligned: Fix ldw() and stw() unalignment handlers
    
    Fix 3 bugs:
    
    a) emulate_stw() doesn't return the error code value, so faulting
    instructions are not reported and aborted.
    
    b) Tell emulate_ldw() to handle fldw_l as floating point instruction
    
    c) Tell emulate_ldw() to handle ldw_m as integer instruction
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org

commit dd2288f4a020d693360e3e8d72f8b9d9c25f5ef6
Author: Helge Deller <deller@gmx.de>
Date:   Fri Feb 18 09:25:20 2022 +0100

    parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel
    
    Usually the kernel provides fixup routines to emulate the fldd and fstd
    floating-point instructions if they load or store 8-byte from/to a not
    natuarally aligned memory location.
    
    On a 32-bit kernel I noticed that those unaligned handlers didn't worked and
    instead the application got a SEGV.
    While checking the code I found two problems:
    
    First, the OPCODE_FLDD_L and OPCODE_FSTD_L cases were ifdef'ed out by the
    CONFIG_PA20 option, and as such those weren't built on a pure 32-bit kernel.
    This is now fixed by moving the CONFIG_PA20 #ifdef to prevent the compilation
    of OPCODE_LDD_L and OPCODE_FSTD_L only, and handling the fldd and fstd
    instructions.
    
    The second problem are two bugs in the 32-bit inline assembly code, where the
    wrong registers where used. The calculation of the natural alignment used %2
    (vall) instead of %3 (ior), and the first word was stored back to address %1
    (valh) instead of %3 (ior).
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org

commit 26fbac2517fcad34fa3f950151fd4c0240fb2935
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Feb 22 18:20:59 2022 +0100

    btrfs: autodefrag: only scan one inode once
    
    Although we have btrfs_requeue_inode_defrag(), for autodefrag we are
    still just exhausting all inode_defrag items in the tree.
    
    This means, it doesn't make much difference to requeue an inode_defrag,
    other than scan the inode from the beginning till its end.
    
    Change the behaviour to always scan from offset 0 of an inode, and till
    the end.
    
    By this we get the following benefit:
    
    - Straight-forward code
    
    - No more re-queue related check
    
    - Fewer members in inode_defrag
    
    We still keep the same btrfs_get_fs_root() and btrfs_iget() check for
    each loop, and added extra should_auto_defrag() check per-loop.
    
    Note: the patch needs to be backported and is intentionally written
    to minimize the diff size, code will be cleaned up later.
    
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 199257a78bb01341c3ba6e85bdcf3a2e6e452c6d
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Feb 11 14:46:13 2022 +0800

    btrfs: defrag: don't use merged extent map for their generation check
    
    For extent maps, if they are not compressed extents and are adjacent by
    logical addresses and file offsets, they can be merged into one larger
    extent map.
    
    Such merged extent map will have the higher generation of all the
    original ones.
    
    But this brings a problem for autodefrag, as it relies on accurate
    extent_map::generation to determine if one extent should be defragged.
    
    For merged extent maps, their higher generation can mark some older
    extents to be defragged while the original extent map doesn't meet the
    minimal generation threshold.
    
    Thus this will cause extra IO.
    
    So solve the problem, here we introduce a new flag, EXTENT_FLAG_MERGED,
    to indicate if the extent map is merged from one or more ems.
    
    And for autodefrag, if we find a merged extent map, and its generation
    meets the generation requirement, we just don't use this one, and go
    back to defrag_get_extent() to read extent maps from subvolume trees.
    
    This could cause more read IO, but should result less defrag data write,
    so in the long run it should be a win for autodefrag.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d5633b0dee02d7d25e93463a03709f11c71500e2
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Feb 11 14:46:12 2022 +0800

    btrfs: defrag: bring back the old file extent search behavior
    
    For defrag, we don't really want to use btrfs_get_extent() to iterate
    all extent maps of an inode.
    
    The reasons are:
    
    - btrfs_get_extent() can merge extent maps
      And the result em has the higher generation of the two, causing defrag
      to mark unnecessary part of such merged large extent map.
    
      This in fact can result extra IO for autodefrag in v5.16+ kernels.
    
      However this patch is not going to completely solve the problem, as
      one can still using read() to trigger extent map reading, and got
      them merged.
    
      The completely solution for the extent map merging generation problem
      will come as an standalone fix.
    
    - btrfs_get_extent() caches the extent map result
      Normally it's fine, but for defrag the target range may not get
      another read/write for a long long time.
      Such cache would only increase the memory usage.
    
    - btrfs_get_extent() doesn't skip older extent map
      Unlike the old find_new_extent() which uses btrfs_search_forward() to
      skip the older subtree, thus it will pick up unnecessary extent maps.
    
    This patch will fix the regression by introducing defrag_get_extent() to
    replace the btrfs_get_extent() call.
    
    This helper will:
    
    - Not cache the file extent we found
      It will search the file extent and manually convert it to em.
    
    - Use btrfs_search_forward() to skip entire ranges which is modified in
      the past
    
    This should reduce the IO for autodefrag.
    
    Reported-by: Filipe Manana <fdmanana@suse.com>
    Fixes: 7b508037d4ca ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 550f133f6959db927127111b50e483da3a7ce662
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Jan 28 15:21:22 2022 +0800

    btrfs: defrag: remove an ambiguous condition for rejection
    
    From the very beginning of btrfs defrag, there is a check to reject
    extents which meet both conditions:
    
    - Physically adjacent
    
      We may want to defrag physically adjacent extents to reduce the number
      of extents or the size of subvolume tree.
    
    - Larger than 128K
    
      This may be there for compressed extents, but unfortunately 128K is
      exactly the max capacity for compressed extents.
      And the check is > 128K, thus it never rejects compressed extents.
    
      Furthermore, the compressed extent capacity bug is fixed by previous
      patch, there is no reason for that check anymore.
    
    The original check has a very small ranges to reject (the target extent
    size is > 128K, and default extent threshold is 256K), and for
    compressed extent it doesn't work at all.
    
    So it's better just to remove the rejection, and allow us to defrag
    physically adjacent extents.
    
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 979b25c300dbcbcb750e88715018e04e854de6c6
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Jan 28 15:21:21 2022 +0800

    btrfs: defrag: don't defrag extents which are already at max capacity
    
    [BUG]
    For compressed extents, defrag ioctl will always try to defrag any
    compressed extents, wasting not only IO but also CPU time to
    compress/decompress:
    
       mkfs.btrfs -f $DEV
       mount -o compress $DEV $MNT
       xfs_io -f -c "pwrite -S 0xab 0 128K" $MNT/foobar
       sync
       xfs_io -f -c "pwrite -S 0xcd 128K 128K" $MNT/foobar
       sync
       echo "=== before ==="
       xfs_io -c "fiemap -v" $MNT/foobar
       btrfs filesystem defrag $MNT/foobar
       sync
       echo "=== after ==="
       xfs_io -c "fiemap -v" $MNT/foobar
    
    Then it shows the 2 128K extents just get COW for no extra benefit, with
    extra IO/CPU spent:
    
        === before ===
        /mnt/btrfs/file1:
         EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
           0: [0..255]:        26624..26879       256   0x8
           1: [256..511]:      26632..26887       256   0x9
        === after ===
        /mnt/btrfs/file1:
         EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
           0: [0..255]:        26640..26895       256   0x8
           1: [256..511]:      26648..26903       256   0x9
    
    This affects not only v5.16 (after the defrag rework), but also v5.15
    (before the defrag rework).
    
    [CAUSE]
    From the very beginning, btrfs defrag never checks if one extent is
    already at its max capacity (128K for compressed extents, 128M
    otherwise).
    
    And the default extent size threshold is 256K, which is already beyond
    the compressed extent max size.
    
    This means, by default btrfs defrag ioctl will mark all compressed
    extent which is not adjacent to a hole/preallocated range for defrag.
    
    [FIX]
    Introduce a helper to grab the maximum extent size, and then in
    defrag_collect_targets() and defrag_check_next_extent(), reject extents
    which are already at their max capacity.
    
    Reported-by: Filipe Manana <fdmanana@suse.com>
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 7093f15291e95f16dfb5a93307eda3272bfe1108
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Jan 28 15:21:20 2022 +0800

    btrfs: defrag: don't try to merge regular extents with preallocated extents
    
    [BUG]
    With older kernels (before v5.16), btrfs will defrag preallocated extents.
    While with newer kernels (v5.16 and newer) btrfs will not defrag
    preallocated extents, but it will defrag the extent just before the
    preallocated extent, even it's just a single sector.
    
    This can be exposed by the following small script:
    
            mkfs.btrfs -f $dev > /dev/null
    
            mount $dev $mnt
            xfs_io -f -c "pwrite 0 4k" -c sync -c "falloc 4k 16K" $mnt/file
            xfs_io -c "fiemap -v" $mnt/file
            btrfs fi defrag $mnt/file
            sync
            xfs_io -c "fiemap -v" $mnt/file
    
    The output looks like this on older kernels:
    
    /mnt/btrfs/file:
     EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
       0: [0..7]:          26624..26631         8   0x0
       1: [8..39]:         26632..26663        32 0x801
    /mnt/btrfs/file:
     EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
       0: [0..39]:         26664..26703        40   0x1
    
    Which defrags the single sector along with the preallocated extent, and
    replace them with an regular extent into a new location (caused by data
    COW).
    This wastes most of the data IO just for the preallocated range.
    
    On the other hand, v5.16 is slightly better:
    
    /mnt/btrfs/file:
     EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
       0: [0..7]:          26624..26631         8   0x0
       1: [8..39]:         26632..26663        32 0x801
    /mnt/btrfs/file:
     EXT: FILE-OFFSET      BLOCK-RANGE      TOTAL FLAGS
       0: [0..7]:          26664..26671         8   0x0
       1: [8..39]:         26632..26663        32 0x801
    
    The preallocated range is not defragged, but the sector before it still
    gets defragged, which has no need for it.
    
    [CAUSE]
    One of the function reused by the old and new behavior is
    defrag_check_next_extent(), it will determine if we should defrag
    current extent by checking the next one.
    
    It only checks if the next extent is a hole or inlined, but it doesn't
    check if it's preallocated.
    
    On the other hand, out of the function, both old and new kernel will
    reject preallocated extents.
    
    Such inconsistent behavior causes above behavior.
    
    [FIX]
    - Also check if next extent is preallocated
      If so, don't defrag current extent.
    
    - Add comments for each branch why we reject the extent
    
    This will reduce the IO caused by defrag ioctl and autodefrag.
    
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit ce345f1e48458837a5b064cac94382c095e00e79
Merge: c22a8086b3840 c5487b9cdea5c
Author: Takashi Iwai <tiwai@suse.de>
Date:   Wed Feb 23 15:06:48 2022 +0100

    Merge tag 'asoc-fix-v5.17-rc5' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus
    
    ASoC: Fixes for v5.17
    
    A few more fixes for v5.17, one followup to the bounds checking fixes
    handling controls which support negative values internally and a driver
    specific one.

commit c2700d2886a87f83f31e0a301de1d2350b52c79b
Author: Varun Prakash <varun@chelsio.com>
Date:   Sat Jan 22 22:27:44 2022 +0530

    nvme-tcp: send H2CData PDUs based on MAXH2CDATA
    
    As per NVMe/TCP specification (revision 1.0a, section 3.6.2.3)
    Maximum Host to Controller Data length (MAXH2CDATA): Specifies the
    maximum number of PDU-Data bytes per H2CData PDU in bytes. This value
    is a multiple of dwords and should be no less than 4,096.
    
    Current code sets H2CData PDU data_length to r2t_length,
    it does not check MAXH2CDATA value. Fix this by setting H2CData PDU
    data_length to min(req->h2cdata_left, queue->maxh2cdata).
    
    Also validate MAXH2CDATA value returned by target in ICResp PDU,
    if it is not a multiple of dword or if it is less than 4096 return
    -EINVAL from nvme_tcp_init_connection().
    
    Signed-off-by: Varun Prakash <varun@chelsio.com>
    Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 602e57c9799c19f27e440639deed3ec45cfe1651
Author: Christoph Hellwig <hch@lst.de>
Date:   Wed Feb 16 14:14:58 2022 +0100

    nvme: also mark passthrough-only namespaces ready in nvme_update_ns_info
    
    Commit e7d65803e2bb ("nvme-multipath: revalidate paths during rescan")
    introduced the NVME_NS_READY flag, which nvme_path_is_disabled() uses
    to check if a path can be used or not.  We also need to set this flag
    for devices that fail the ZNS feature validation and which are available
    through passthrough devices only to that they can be used in multipathing
    setups.
    
    Fixes: e7d65803e2bb ("nvme-multipath: revalidate paths during rescan")
    Reported-by: Kanchan Joshi <joshi.k@samsung.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
    Reviewed-by: Daniel Wagner <dwagner@suse.de>
    Tested-by: Kanchan Joshi <joshi.k@samsung.com>

commit 363f6368603743072e5f318c668c632bccb097a3
Author: Christoph Hellwig <hch@lst.de>
Date:   Wed Feb 16 15:07:15 2022 +0100

    nvme: don't return an error from nvme_configure_metadata
    
    When a fabrics controller claims to support an invalidate metadata
    configuration we already warn and disable metadata support.  No need to
    also return an error during revalidation.
    
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
    Reviewed-by: Daniel Wagner <dwagner@suse.de>
    Tested-by: Kanchan Joshi <joshi.k@samsung.com>

commit ecbd4912a693b862e25cba0a6990a8c95b00721e
Author: Maxime Ripard <maxime@cerno.tech>
Date:   Thu Feb 3 12:54:16 2022 +0100

    drm/edid: Always set RGB444
    
    In order to fill the drm_display_info structure each time an EDID is
    read, the code currently will call drm_add_display_info with the parsed
    EDID.
    
    drm_add_display_info will then call drm_reset_display_info to reset all
    the fields to 0, and then set them to the proper value depending on the
    EDID.
    
    In the color_formats case, we will thus report that we don't support any
    color format, and then fill it back with RGB444 plus the additional
    formats described in the EDID Feature Support byte.
    
    However, since that byte only contains format-related bits since the 1.4
    specification, this doesn't happen if the EDID is following an earlier
    specification. In turn, it means that for one of these EDID, we end up
    with color_formats set to 0.
    
    The EDID 1.3 specification never really specifies what it means by RGB
    exactly, but since both HDMI and DVI will use RGB444, it's fairly safe
    to assume it's supposed to be RGB444.
    
    Let's move the addition of RGB444 to color_formats earlier in
    drm_add_display_info() so that it's always set for a digital display.
    
    Fixes: da05a5a71ad8 ("drm: parse color format support for digital displays")
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Reported-by: Matthias Reichl <hias@horus.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220203115416.1137308-1-maxime@cerno.tech

commit 0228d37bd1a4fa552916e696f70490225272d58a
Merge: ecf4a24cf9783 1baf2e50e48f1
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Feb 23 12:50:19 2022 +0000

    Merge branch 'ftgmac100-fixes'
    
    Heyi Guo says:
    
    ====================
    drivers/net/ftgmac100: fix occasional DHCP failure
    
    This patch set is to fix the issues discussed in the mail thread:
    https://lore.kernel.org/netdev/51f5b7a7-330f-6b3c-253d-10e45cdb6805@linux.alibaba.com/
    and follows the advice from Andrew Lunn.
    
    The first 2 patches refactors the code to enable adjust_link calling reset
    function directly.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1baf2e50e48f10f0ea07d53e13381fd0da1546d2
Author: Heyi Guo <guoheyi@linux.alibaba.com>
Date:   Wed Feb 23 11:14:36 2022 +0800

    drivers/net/ftgmac100: fix DHCP potential failure with systemd
    
    DHCP failures were observed with systemd 247.6. The issue could be
    reproduced by rebooting Aspeed 2600 and then running ifconfig ethX
    down/up.
    
    It is caused by below procedures in the driver:
    
    1. ftgmac100_open() enables net interface and call phy_start()
    2. When PHY is link up, it calls netif_carrier_on() and then
    adjust_link callback
    3. ftgmac100_adjust_link() will schedule the reset task
    4. ftgmac100_reset_task() will then reset the MAC in another schedule
    
    After step 2, systemd will be notified to send DHCP discover packet,
    while the packet might be corrupted by MAC reset operation in step 4.
    
    Call ftgmac100_reset() directly instead of scheduling task to fix the
    issue.
    
    Signed-off-by: Heyi Guo <guoheyi@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3c773dba8182cdfea7b32caafe9290240ab8de5f
Author: Heyi Guo <guoheyi@linux.alibaba.com>
Date:   Wed Feb 23 11:14:35 2022 +0800

    drivers/net/ftgmac100: adjust code place for function call dependency
    
    This is to prepare for ftgmac100_adjust_link() to call
    ftgmac100_reset() directly. Only code places are changed.
    
    Signed-off-by: Heyi Guo <guoheyi@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4f1e72850d452e5c3302faa82a01f179ff5f9482
Author: Heyi Guo <guoheyi@linux.alibaba.com>
Date:   Wed Feb 23 11:14:34 2022 +0800

    drivers/net/ftgmac100: refactor ftgmac100_reset_task to enable direct function call
    
    This is to prepare for ftgmac100_adjust_link() to call reset function
    directly, instead of task schedule.
    
    Signed-off-by: Heyi Guo <guoheyi@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ecf4a24cf97838fb0b78d4ede0f91d80b058289c
Author: Wan Jiabing <wanjiabing@vivo.com>
Date:   Wed Feb 23 10:34:19 2022 +0800

    net: sched: avoid newline at end of message in NL_SET_ERR_MSG_MOD
    
    Fix following coccicheck warning:
    ./net/sched/act_api.c:277:7-49: WARNING avoid newline at end of message
    in NL_SET_ERR_MSG_MOD
    
    Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 404ba13a6588d72b3fb9e5c17b73e4725f18c047
Author: Alvin Šipraga <alsi@bang-olufsen.dk>
Date:   Tue Feb 22 17:14:08 2022 +0100

    MAINTAINERS: add myself as co-maintainer for Realtek DSA switch drivers
    
    Adding myself (Alvin Šipraga) as another maintainer for the Realtek DSA
    switch drivers. I intend to help Linus out with reviewing and testing
    changes to these drivers, particularly the rtl8365mb driver which I
    authored and have hardware access to.
    
    Cc: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Alvin Šipraga <alsi@bang-olufsen.dk>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a1f8fec4dac8bc7b172b2bdbd881e015261a6322
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Feb 22 16:43:12 2022 +0300

    tipc: Fix end of loop tests for list_for_each_entry()
    
    These tests are supposed to check if the loop exited via a break or not.
    However the tests are wrong because if we did not exit via a break then
    "p" is not a valid pointer.  In that case, it's the equivalent of
    "if (*(u32 *)sr == *last_key) {".  That's going to work most of the time,
    but there is a potential for those to be equal.
    
    Fixes: 1593123a6a49 ("tipc: add name table dump to new netlink api")
    Fixes: 1a1a143daf84 ("tipc: add publication dump to new netlink api")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit de7b2efacf4e83954aed3f029d347dfc0b7a4f49
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Feb 22 16:42:51 2022 +0300

    udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()
    
    This test is checking if we exited the list via break or not.  However
    if it did not exit via a break then "node" does not point to a valid
    udp_tunnel_nic_shared_node struct.  It will work because of the way
    the structs are laid out it's the equivalent of
    "if (info->shared->udp_tunnel_nic_info != dev)" which will always be
    true, but it's not the right way to test.
    
    Fixes: 74cc6d182d03 ("udp_tunnel: add the ability to share port tables")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a58da53ffd70294ebea8ecd0eb45fd0d74add9f9
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Tue Feb 22 10:47:42 2022 +0100

    vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
    
    vhost_vsock_stop() calls vhost_dev_check_owner() to check the device
    ownership. It expects current->mm to be valid.
    
    vhost_vsock_stop() is also called by vhost_vsock_dev_release() when
    the user has not done close(), so when we are in do_exit(). In this
    case current->mm is invalid and we're releasing the device, so we
    should clean it anyway.
    
    Let's check the owner only when vhost_vsock_stop() is called
    by an ioctl.
    
    When invoked from release we can not fail so we don't check return
    code of vhost_vsock_stop(). We need to stop vsock even if it's not
    the owner.
    
    Fixes: 433fc58e6bf2 ("VSOCK: Introduce vhost_vsock.ko")
    Cc: stable@vger.kernel.org
    Reported-by: syzbot+1e3ea63db39f2b4440e0@syzkaller.appspotmail.com
    Reported-and-tested-by: syzbot+3140b17cb44a7b174008@syzkaller.appspotmail.com
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8d3b01e0d4bb54368d73d0984466d72c2eeeac74
Author: Thierry Reding <treding@nvidia.com>
Date:   Mon Dec 20 11:32:39 2021 +0100

    ARM: tegra: Move panels to AUX bus
    
    Move the eDP panel on Venice 2 and Nyan boards into the corresponding
    AUX bus device tree node. This allows us to avoid a nasty circular
    dependency that would otherwise be created between the DPAUX and panel
    nodes via the DDC/I2C phandle.
    
    Fixes: eb481f9ac95c ("ARM: tegra: add Acer Chromebook 13 device tree")
    Fixes: 59fe02cb079f ("ARM: tegra: Add DTS for the nyan-blaze board")
    Fixes: 40e231c770a4 ("ARM: tegra: Enable eDP for Venice2")
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit 8913e1aea4b32a866343b14e565c62cec54f3f78
Author: Thierry Reding <treding@nvidia.com>
Date:   Mon Dec 20 11:28:22 2021 +0100

    drm/tegra: dpaux: Populate AUX bus
    
    The DPAUX hardware block exposes an DP AUX interface that provides
    access to an AUX bus and the devices on that bus. Use the DP AUX bus
    infrastructure that was recently introduced to probe devices on this
    bus from DT.
    
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit f762ce78897d734a08f52e39a353359b7d417578
Author: Christian König <christian.koenig@amd.com>
Date:   Mon Feb 21 09:31:28 2022 +0100

    drm/radeon: fix variable type
    
    When we switch to dma_resv_wait_timeout() the returned type changes as
    well.
    
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Fixes: 89aae41d740f ("drm/radeon: use dma_resv_wait_timeout() instead of manually waiting")
    Bug: https://bugzilla.kernel.org/show_bug.cgi?id=215600
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220221110503.2803-1-christian.koenig@amd.com

commit ae089831ff28a115908b8d796f667c2dadef1637
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Feb 22 10:13:31 2022 -0800

    netfilter: nf_tables: prefer kfree_rcu(ptr, rcu) variant
    
    While kfree_rcu(ptr) _is_ supported, it has some limitations.
    
    Given that 99.99% of kfree_rcu() users [1] use the legacy
    two parameters variant, and @catchall objects do have an rcu head,
    simply use it.
    
    Choice of kfree_rcu(ptr) variant was probably not intentional.
    
    [1] including calls from net/netfilter/nf_tables_api.c
    
    Fixes: aaa31047a6d2 ("netfilter: nftables: add catch-all set element support")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 277f2bb14361790a70e4b3c649e794b75a91a597
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Mon Feb 21 15:05:45 2022 -0600

    ibmvnic: schedule failover only if vioctl fails
    
    If client is unable to initiate a failover reset via H_VIOCTL hcall, then
    it should schedule a failover reset as a last resort. Otherwise, there is
    no need to do a last resort.
    
    Fixes: 334c42414729 ("ibmvnic: improve failover sysfs entry")
    Reported-by: Cris Forno <cforno12@outlook.com>
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Signed-off-by: Dany Madden <drt@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220221210545.115283-1-drt@linux.ibm.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 342b6419193c6f697fd47d9c72fcff9cafc70687
Author: Alvin Šipraga <alsi@bang-olufsen.dk>
Date:   Mon Feb 21 21:35:38 2022 +0100

    net: dsa: fix panic when removing unoffloaded port from bridge
    
    If a bridged port is not offloaded to the hardware - either because the
    underlying driver does not implement the port_bridge_{join,leave} ops,
    or because the operation failed - then its dp->bridge pointer will be
    NULL when dsa_port_bridge_leave() is called. Avoid dereferncing NULL.
    
    This fixes the following splat when removing a port from a bridge:
    
     Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000000
     Internal error: Oops: 96000004 [#1] PREEMPT_RT SMP
     CPU: 3 PID: 1119 Comm: brctl Tainted: G           O      5.17.0-rc4-rt4 #1
     Call trace:
      dsa_port_bridge_leave+0x8c/0x1e4
      dsa_slave_changeupper+0x40/0x170
      dsa_slave_netdevice_event+0x494/0x4d4
      notifier_call_chain+0x80/0xe0
      raw_notifier_call_chain+0x1c/0x24
      call_netdevice_notifiers_info+0x5c/0xac
      __netdev_upper_dev_unlink+0xa4/0x200
      netdev_upper_dev_unlink+0x38/0x60
      del_nbp+0x1b0/0x300
      br_del_if+0x38/0x114
      add_del_if+0x60/0xa0
      br_ioctl_stub+0x128/0x2dc
      br_ioctl_call+0x68/0xb0
      dev_ifsioc+0x390/0x554
      dev_ioctl+0x128/0x400
      sock_do_ioctl+0xb4/0xf4
      sock_ioctl+0x12c/0x4e0
      __arm64_sys_ioctl+0xa8/0xf0
      invoke_syscall+0x4c/0x110
      el0_svc_common.constprop.0+0x48/0xf0
      do_el0_svc+0x28/0x84
      el0_svc+0x1c/0x50
      el0t_64_sync_handler+0xa8/0xb0
      el0t_64_sync+0x17c/0x180
     Code: f9402f00 f0002261 f9401302 913cc021 (a9401404)
     ---[ end trace 0000000000000000 ]---
    
    Fixes: d3eed0e57d5d ("net: dsa: keep the bridge_dev and bridge_num as part of the same structure")
    Signed-off-by: Alvin Šipraga <alsi@bang-olufsen.dk>
    Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220221203539.310690-1-alvin@pqrs.dk
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8d093e02e898b24c58788b0289e3202317a96d2a
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Sat Feb 19 20:44:43 2022 +0300

    ata: pata_hpt37x: disable primary channel on HPT371
    
    The HPT371 chip physically has only one channel, the secondary one,
    however the primary channel registers do exist! Thus we have to
    manually disable the non-existing channel if the BIOS hasn't done this
    already. Similarly to the pata_hpt3x2n driver, always disable the
    primary channel.
    
    Fixes: 669a5db411d8 ("[libata] Add a bunch of PATA drivers.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit ef527f968ae05c6717c39f49c8709a7e2c19183a
Author: Eric Dumazet <edumazet@google.com>
Date:   Sun Feb 20 07:40:52 2022 -0800

    net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends
    
    Whenever one of these functions pull all data from an skb in a frag_list,
    use consume_skb() instead of kfree_skb() to avoid polluting drop
    monitoring.
    
    Fixes: 6fa01ccd8830 ("skbuff: Add pskb_extract() helper function")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Link: https://lore.kernel.org/r/20220220154052.1308469-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 13e741b834538a225512912608f0182079fc64e2
Author: German Gomez <german.gomez@arm.com>
Date:   Mon Feb 21 17:17:06 2022 +0000

    perf script: Fix error when printing 'weight' field
    
    In SPE traces the 'weight' field can't be printed in 'perf script'
    because the 'dummy:u' event doesn't have the WEIGHT attribute set.
    
    Use evsel__do_check_stype(..) to check this field, as it's done with
    other fields such as "phys_addr".
    
    Before:
    
      $ perf record -e arm_spe_0// -- sleep 1
      $ perf script -F event,ip,weight
      Samples for 'dummy:u' event do not have WEIGHT attribute set. Cannot print 'weight' field.
    
    After:
    
      $ perf script -F event,ip,weight
         l1d-access:               12 ffffaf629d4cb320
         tlb-access:               12 ffffaf629d4cb320
             memory:               12 ffffaf629d4cb320
    
    Fixes: b0fde9c6e291e528 ("perf arm-spe: Add SPE total latency as PERF_SAMPLE_WEIGHT")
    Signed-off-by: German Gomez <german.gomez@arm.com>
    Acked-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220221171707.62960-1-german.gomez@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 5c1ee569660d4a205dced9cb4d0306b907fb7599
Merge: 917bbdb107f87 c70cd039f1d77
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 22 16:14:35 2022 -0800

    Merge branch 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
    
    Pull cgroup fixes from Tejun Heo:
    
     - Fix for a subtle bug in the recent release_agent permission check
       update
    
     - Fix for a long-standing race condition between cpuset and cpu hotplug
    
     - Comment updates
    
    * 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
      cpuset: Fix kernel-doc
      cgroup-v1: Correct privileges check in release_agent writes
      cgroup: clarify cgroup_css_set_fork()
      cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug

commit ce2fc710c9d2b25afc710f49bb2065b4439a62bc
Author: Ondrej Mosnacek <omosnace@redhat.com>
Date:   Mon Feb 21 15:06:49 2022 +0100

    selinux: fix misuse of mutex_is_locked()
    
    mutex_is_locked() tests whether the mutex is locked *by any task*, while
    here we want to test if it is held *by the current task*. To avoid
    false/missed WARNINGs, use lockdep_assert_is_held() and
    lockdep_assert_is_not_held() instead, which do the right thing (though
    they are a no-op if CONFIG_LOCKDEP=n).
    
    Cc: stable@vger.kernel.org
    Fixes: 2554a48f4437 ("selinux: measure state and policy capabilities")
    Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
    Signed-off-by: Paul Moore <paul@paul-moore.com>

commit 0c0822bcb73f154d96ee648644ec5a8628e3b864
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 21 11:07:01 2022 +0100

    dt-bindings: update Roger Quadros email
    
    Emails to Roger Quadros TI account bounce with:
      550 Invalid recipient <rogerq@ti.com> (#5.1.1)
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Roger Quadros <rogerq@kernel.org>
    Acked-By: Vinod Koul <vkoul@kernel.org>
    Acked-by: Lee Jones <lee.jones@linaro.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220221100701.48593-1-krzysztof.kozlowski@canonical.com

commit 34f3eda8c8ffd4d0b2145ac11c91cc365cd1ada3
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 14 09:23:49 2022 +0100

    MAINTAINERS: sifive: drop Yash Shah
    
    Emails to Yash Shah bounce with "The email account that you tried to
    reach does not exist.", so drop him from all maintainer entries.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220214082349.162973-1-krzysztof.kozlowski@canonical.com

commit 5b061a322b05a5e023d9a0df1ae1f8bb562ed87b
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Fri Aug 7 08:45:47 2020 -0300

    tools arch x86: Sync the msr-index.h copy with the kernel sources
    
    To pick up the changes in:
    
      3915035282573c5e ("KVM: x86: SVM: move avic definitions from AMD's spec to svm.h")
    
    Addressing these tools/perf build warnings:
    
        diff -u tools/arch/x86/include/asm/msr-index.h arch/x86/include/asm/msr-index.h
        Warning: Kernel ABI header at 'tools/arch/x86/include/asm/msr-index.h' differs from latest version at 'arch/x86/include/asm/msr-index.h'
    
    That makes the beautification scripts to pick some new entries:
    
      $ tools/perf/trace/beauty/tracepoints/x86_msr.sh > before
      $ cp arch/x86/include/asm/msr-index.h tools/arch/x86/include/asm/msr-index.h
      $ tools/perf/trace/beauty/tracepoints/x86_msr.sh > after
      $ diff -u before after
      --- before    2022-02-22 17:35:36.996271430 -0300
      +++ after     2022-02-22 17:35:46.258503347 -0300
      @@ -287,6 +287,7 @@
            [0xc0010114 - x86_AMD_V_KVM_MSRs_offset] = "VM_CR",
            [0xc0010115 - x86_AMD_V_KVM_MSRs_offset] = "VM_IGNNE",
            [0xc0010117 - x86_AMD_V_KVM_MSRs_offset] = "VM_HSAVE_PA",
      +     [0xc001011b - x86_AMD_V_KVM_MSRs_offset] = "AMD64_SVM_AVIC_DOORBELL",
            [0xc001011e - x86_AMD_V_KVM_MSRs_offset] = "AMD64_VM_PAGE_FLUSH",
            [0xc001011f - x86_AMD_V_KVM_MSRs_offset] = "AMD64_VIRT_SPEC_CTRL",
            [0xc0010130 - x86_AMD_V_KVM_MSRs_offset] = "AMD64_SEV_ES_GHCB",
      $
    
    And this gets rebuilt:
    
      CC      /tmp/build/perf/trace/beauty/tracepoints/x86_msr.o
      LD      /tmp/build/perf/trace/beauty/tracepoints/perf-in.o
      LD      /tmp/build/perf/trace/beauty/perf-in.o
      CC      /tmp/build/perf/util/amd-sample-raw.o
      LD      /tmp/build/perf/util/perf-in.o
      LD      /tmp/build/perf/perf-in.o
      LINK    /tmp/build/perf/perf
    
    Now one can trace systemwide asking to see backtraces to where those
    MSRs are being read/written with:
    
      # perf trace -e msr:*_msr/max-stack=32/ --filter="msr>=AMD64_SVM_AVIC_DOORBELL && msr<=AMD64_SEV_ES_GHCB"
      ^C#
    
    If we use -v (verbose mode) we can see what it does behind the scenes:
    
      # perf trace -v -e msr:*_msr/max-stack=32/ --filter="msr>=AMD64_SVM_AVIC_DOORBELL && msr<=AMD64_SEV_ES_GHCB"
      Using CPUID AuthenticAMD-25-21-0
      0xc001011b
      0xc0010130
      New filter for msr:read_msr: (msr>=0xc001011b && msr<=0xc0010130) && (common_pid != 1019953 && common_pid != 3629)
      0xc001011b
      0xc0010130
      New filter for msr:write_msr: (msr>=0xc001011b && msr<=0xc0010130) && (common_pid != 1019953 && common_pid != 3629)
      mmap size 528384B
      ^C#
    
      Example with a frequent msr:
    
        # perf trace -v -e msr:*_msr/max-stack=32/ --filter="msr==IA32_SPEC_CTRL" --max-events 2
        Using CPUID AuthenticAMD-25-21-0
        0x48
        New filter for msr:read_msr: (msr==0x48) && (common_pid != 2612129 && common_pid != 3841)
        0x48
        New filter for msr:write_msr: (msr==0x48) && (common_pid != 2612129 && common_pid != 3841)
        mmap size 528384B
        Looking at the vmlinux_path (8 entries long)
        symsrc__init: build id mismatch for vmlinux.
        Using /proc/kcore for kernel data
        Using /proc/kallsyms for symbols
           0.000 Timer/2525383 msr:write_msr(msr: IA32_SPEC_CTRL, val: 6)
                                             do_trace_write_msr ([kernel.kallsyms])
                                             do_trace_write_msr ([kernel.kallsyms])
                                             __switch_to_xtra ([kernel.kallsyms])
                                             __switch_to ([kernel.kallsyms])
                                             __schedule ([kernel.kallsyms])
                                             schedule ([kernel.kallsyms])
                                             futex_wait_queue_me ([kernel.kallsyms])
                                             futex_wait ([kernel.kallsyms])
                                             do_futex ([kernel.kallsyms])
                                             __x64_sys_futex ([kernel.kallsyms])
                                             do_syscall_64 ([kernel.kallsyms])
                                             entry_SYSCALL_64_after_hwframe ([kernel.kallsyms])
                                             __futex_abstimed_wait_common64 (/usr/lib64/libpthread-2.33.so)
           0.030 :0/0 msr:write_msr(msr: IA32_SPEC_CTRL, val: 2)
                                             do_trace_write_msr ([kernel.kallsyms])
                                             do_trace_write_msr ([kernel.kallsyms])
                                             __switch_to_xtra ([kernel.kallsyms])
                                             __switch_to ([kernel.kallsyms])
                                             __schedule ([kernel.kallsyms])
                                             schedule_idle ([kernel.kallsyms])
                                             do_idle ([kernel.kallsyms])
                                             cpu_startup_entry ([kernel.kallsyms])
                                             secondary_startup_64_no_verify ([kernel.kallsyms])
      #
    
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Maxim Levitsky <mlevitsk@redhat.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Link: http://lore.kernel.org/lkml/YhVKxaft+z8rpOfy@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 69560e366fc4d5fca7bebb0e44edbfafc8bcaf05
Author: Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
Date:   Fri Feb 18 18:23:41 2022 +0300

    perf data: Fix double free in perf_session__delete()
    
    When perf_data__create_dir() fails, it calls close_dir(), but
    perf_session__delete() also calls close_dir() and since dir.version and
    dir.nr were initialized by perf_data__create_dir(), a double free occurs.
    
    This patch moves the initialization of dir.version and dir.nr after
    successful initialization of dir.files, that prevents double freeing.
    This behavior is already implemented in perf_data__open_dir().
    
    Fixes: 145520631130bd64 ("perf data: Add perf_data__(create_dir|close_dir) functions")
    Signed-off-by: Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
    Acked-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Alexander Antonov <alexander.antonov@linux.intel.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexei Budankov <abudankov@huawei.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20220218152341.5197-2-alexey.v.bayduraev@linux.intel.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit c70cd039f1d779126347a896a58876782dcc5284
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Wed Feb 16 11:17:53 2022 +0800

    cpuset: Fix kernel-doc
    
    Fix the following W=1 kernel warnings:
    
    kernel/cgroup/cpuset.c:3718: warning: expecting prototype for
    cpuset_memory_pressure_bump(). Prototype was for
    __cpuset_memory_pressure_bump() instead.
    
    kernel/cgroup/cpuset.c:3568: warning: expecting prototype for
    cpuset_node_allowed(). Prototype was for __cpuset_node_allowed()
    instead.
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 917bbdb107f8767cb78f24e7d6725a2f93b9effe
Merge: 038101e6b2cd5 9d2231c5d74e1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 22 10:31:53 2022 -0800

    Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
    
    Pull ITER_PIPE fix from Al Viro:
     "Fix for old sloppiness in pipe_buffer reuse"
    
    * 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
      lib/iov_iter: initialize "flags" in new pipe_buffer

commit 467a726b754f474936980da793b4ff2ec3e382a7
Author: Michal Koutný <mkoutny@suse.com>
Date:   Thu Feb 17 17:11:28 2022 +0100

    cgroup-v1: Correct privileges check in release_agent writes
    
    The idea is to check: a) the owning user_ns of cgroup_ns, b)
    capabilities in init_user_ns.
    
    The commit 24f600856418 ("cgroup-v1: Require capabilities to set
    release_agent") got this wrong in the write handler of release_agent
    since it checked user_ns of the opener (may be different from the owning
    user_ns of cgroup_ns).
    Secondly, to avoid possibly confused deputy, the capability of the
    opener must be checked.
    
    Fixes: 24f600856418 ("cgroup-v1: Require capabilities to set release_agent")
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/stable/20220216121142.GB30035@blackbody.suse.cz/
    Signed-off-by: Michal Koutný <mkoutny@suse.com>
    Reviewed-by: Masami Ichikawa(CIP) <masami.ichikawa@cybertrust.co.jp>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 6d3971dab239e7db1691690a02ce6becf30689cb
Author: Christian Brauner <brauner@kernel.org>
Date:   Mon Feb 21 16:16:39 2022 +0100

    cgroup: clarify cgroup_css_set_fork()
    
    With recent fixes for the permission checking when moving a task into a cgroup
    using a file descriptor to a cgroup's cgroup.procs file and calling write() it
    seems a good idea to clarify CLONE_INTO_CGROUP permission checking with a
    comment.
    
    Cc: Tejun Heo <tj@kernel.org>
    Cc: <cgroups@vger.kernel.org>
    Signed-off-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 84ec758fb2daa236026506868c8796b0500c047d
Author: ChenXiaoSong <chenxiaosong2@huawei.com>
Date:   Tue Feb 15 15:10:30 2022 +0800

    configfs: fix a race in configfs_{,un}register_subsystem()
    
    When configfs_register_subsystem() or configfs_unregister_subsystem()
    is executing link_group() or unlink_group(),
    it is possible that two processes add or delete list concurrently.
    Some unfortunate interleavings of them can cause kernel panic.
    
    One of cases is:
    A --> B --> C --> D
    A <-- B <-- C <-- D
    
         delete list_head *B        |      delete list_head *C
    --------------------------------|-----------------------------------
    configfs_unregister_subsystem   |   configfs_unregister_subsystem
      unlink_group                  |     unlink_group
        unlink_obj                  |       unlink_obj
          list_del_init             |         list_del_init
            __list_del_entry        |           __list_del_entry
              __list_del            |             __list_del
                // next == C        |
                next->prev = prev   |
                                    |               next->prev = prev
                prev->next = next   |
                                    |                 // prev == B
                                    |                 prev->next = next
    
    Fix this by adding mutex when calling link_group() or unlink_group(),
    but parent configfs_subsystem is NULL when config_item is root.
    So I create a mutex configfs_subsystem_mutex.
    
    Fixes: 7063fbf22611 ("[PATCH] configfs: User-driven configuration filesystem")
    Signed-off-by: ChenXiaoSong <chenxiaosong2@huawei.com>
    Signed-off-by: Laibin Qiu <qiulaibin@huawei.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 80912cef18f16f8fe59d1fb9548d4364342be360
Author: Dylan Yudaken <dylany@fb.com>
Date:   Tue Feb 22 08:17:51 2022 -0800

    io_uring: disallow modification of rsrc_data during quiesce
    
    io_rsrc_ref_quiesce will unlock the uring while it waits for references to
    the io_rsrc_data to be killed.
    There are other places to the data that might add references to data via
    calls to io_rsrc_node_switch.
    There is a race condition where this reference can be added after the
    completion has been signalled. At this point the io_rsrc_ref_quiesce call
    will wake up and relock the uring, assuming the data is unused and can be
    freed - although it is actually being used.
    
    To fix this check in io_rsrc_ref_quiesce if a resource has been revived.
    
    Reported-by: syzbot+ca8bf833622a1662745b@syzkaller.appspotmail.com
    Cc: stable@vger.kernel.org
    Signed-off-by: Dylan Yudaken <dylany@fb.com>
    Link: https://lore.kernel.org/r/20220222161751.995746-1-dylany@fb.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 35f165f08950a876f1b95a61d79c93678fba2fd6
Author: Vikash Chandola <vikash.chandola@linux.intel.com>
Date:   Tue Feb 22 13:12:53 2022 +0000

    hwmon: (pmbus) Clear pmbus fault/warning bits after read
    
    Almost all fault/warning bits in pmbus status registers remain set even
    after fault/warning condition are removed. As per pmbus specification
    these faults must be cleared by user.
    Modify hwmon behavior to clear fault/warning bit after fetching data if
    fault/warning bit was set. This allows to get fresh data in next read.
    
    Signed-off-by: Vikash Chandola <vikash.chandola@linux.intel.com>
    Link: https://lore.kernel.org/r/20220222131253.2426834-1-vikash.chandola@linux.intel.com
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit 1b5f517cca36292076d9e38fa6e33a257703e62e
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Mon Feb 21 08:32:14 2022 -0800

    hwmon: Handle failure to register sensor with thermal zone correctly
    
    If an attempt is made to a sensor with a thermal zone and it fails,
    the call to devm_thermal_zone_of_sensor_register() may return -ENODEV.
    This may result in crashes similar to the following.
    
    Unable to handle kernel NULL pointer dereference at virtual address 00000000000003cd
    ...
    Internal error: Oops: 96000021 [#1] PREEMPT SMP
    ...
    pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    pc : mutex_lock+0x18/0x60
    lr : thermal_zone_device_update+0x40/0x2e0
    sp : ffff800014c4fc60
    x29: ffff800014c4fc60 x28: ffff365ee3f6e000 x27: ffffdde218426790
    x26: ffff365ee3f6e000 x25: 0000000000000000 x24: ffff365ee3f6e000
    x23: ffffdde218426870 x22: ffff365ee3f6e000 x21: 00000000000003cd
    x20: ffff365ee8bf3308 x19: ffffffffffffffed x18: 0000000000000000
    x17: ffffdde21842689c x16: ffffdde1cb7a0b7c x15: 0000000000000040
    x14: ffffdde21a4889a0 x13: 0000000000000228 x12: 0000000000000000
    x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
    x8 : 0000000001120000 x7 : 0000000000000001 x6 : 0000000000000000
    x5 : 0068000878e20f07 x4 : 0000000000000000 x3 : 00000000000003cd
    x2 : ffff365ee3f6e000 x1 : 0000000000000000 x0 : 00000000000003cd
    Call trace:
     mutex_lock+0x18/0x60
     hwmon_notify_event+0xfc/0x110
     0xffffdde1cb7a0a90
     0xffffdde1cb7a0b7c
     irq_thread_fn+0x2c/0xa0
     irq_thread+0x134/0x240
     kthread+0x178/0x190
     ret_from_fork+0x10/0x20
    Code: d503201f d503201f d2800001 aa0103e4 (c8e47c02)
    
    Jon Hunter reports that the exact call sequence is:
    
    hwmon_notify_event()
      --> hwmon_thermal_notify()
        --> thermal_zone_device_update()
          --> update_temperature()
            --> mutex_lock()
    
    The hwmon core needs to handle all errors returned from calls
    to devm_thermal_zone_of_sensor_register(). If the call fails
    with -ENODEV, report that the sensor was not attached to a
    thermal zone  but continue to register the hwmon device.
    
    Reported-by: Jon Hunter <jonathanh@nvidia.com>
    Cc: Dmitry Osipenko <digetx@gmail.com>
    Fixes: 1597b374af222 ("hwmon: Add notification support")
    Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
    Tested-by: Jon Hunter <jonathanh@nvidia.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit 1e2277ed709585672565ecf0ff9215af148b7800
Merge: ec756e40e2718 93b71801a8274
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Tue Feb 22 09:07:16 2022 -0500

    Merge branch 'kvm-ppc-cap-210' into kvm-master
    
    By request of Nick Piggin:
    
    > Patch 3 requires a KVM_CAP_PPC number allocated. QEMU maintainers are
    > happy with it (link in changelog) just waiting on KVM upstreaming. Do
    > you have objections to the series going to ppc/kvm tree first, or
    > another option is you could take patch 3 alone first (it's relatively
    > independent of the other 2) and ppc/kvm gets it from you?

commit 93b71801a8274cd9511557faf04365a5de487197
Author: Nicholas Piggin <npiggin@gmail.com>
Date:   Tue Feb 22 09:06:54 2022 -0500

    KVM: PPC: reserve capability 210 for KVM_CAP_PPC_AIL_MODE_3
    
    Add KVM_CAP_PPC_AIL_MODE_3 to advertise the capability to set the AIL
    resource mode to 3 with the H_SET_MODE hypercall. This capability
    differs between processor types and KVM types (PR, HV, Nested HV), and
    affects guest-visible behaviour.
    
    QEMU will implement a cap-ail-mode-3 to control this behaviour[1], and
    use the KVM CAP if available to determine KVM support[2].
    
    Reviewed-by: Fabiano Rosas <farosas@linux.ibm.com>
    Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit bb49c6fa8b845591b317b0d7afea4ae60ec7f3aa
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Fri Feb 11 10:01:36 2022 +0100

    block: clear iocb->private in blkdev_bio_end_io_async()
    
    iocb_bio_iopoll() expects iocb->private to be cleared before
    releasing the bio.
    
    We already do this in blkdev_bio_end_io(), but we forgot in the
    recently added blkdev_bio_end_io_async().
    
    Fixes: 54a88eb838d3 ("block: add single bio async direct IO helper")
    Cc: asml.silence@gmail.com
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Reviewed-by: Ming Lei <ming.lei@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220211090136.44471-1-sgarzare@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 9c7cf33c53ce833b58de9e5c192b4736dbd09cb1
Author: Adam Ward <Adam.Ward.opensource@diasemi.com>
Date:   Tue Feb 22 00:27:44 2022 +0000

    regulator: da9121: Remove surplus DA9141 parameters
    
    Remove ramp_delay/enable_time values - subject to OTP, incorrect
    
    Signed-off-by: Adam Ward <Adam.Ward.opensource@diasemi.com>
    Link: https://lore.kernel.org/r/a175201b4a7ea323c6a70d77f7f6d2124bfc0bed.1645489455.git.Adam.Ward.opensource@diasemi.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit c8c57fbc1c5067b913077e948c7d957af6834ba3
Author: Adam Ward <Adam.Ward.opensource@diasemi.com>
Date:   Tue Feb 22 00:27:43 2022 +0000

    regulator: da9121: Fix DA914x voltage value
    
    Update DA9141/2 max voltage to match spec change
    
    Signed-off-by: Adam Ward <Adam.Ward.opensource@diasemi.com>
    Link: https://lore.kernel.org/r/9d1ec5b6db70d27f56d05b8a0139fc0840f03e20.1645489455.git.Adam.Ward.opensource@diasemi.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit f0fdfc04fd974cea23351b830fcac0822ea19a51
Author: Adam Ward <Adam.Ward.opensource@diasemi.com>
Date:   Tue Feb 22 00:27:42 2022 +0000

    regulator: da9121: Fix DA914x current values
    
    Update DA9141/2 ranges to correct errors
    
    Signed-off-by: Adam Ward <Adam.Ward.opensource@diasemi.com>
    Link: https://lore.kernel.org/r/cd5732c5061ce49dcfbcebb306d12ba1664b4ea6.1645489455.git.Adam.Ward.opensource@diasemi.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 5663b85462a66821fc314c5bf9ffd427d1ad71cc
Merge: b6ad6261d2770 dad3bdeef45f8
Author: David S. Miller <davem@davemloft.net>
Date:   Tue Feb 22 11:00:51 2022 +0000

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    This is fixing up the use without proper initialization in patch 5/5
    
    -o-
    
    Hi,
    
    The following patchset contains Netfilter fixes for net:
    
    1) Missing #ifdef CONFIG_IP6_NF_IPTABLES in recent xt_socket fix.
    
    2) Fix incorrect flow action array size in nf_tables.
    
    3) Unregister flowtable hooks from netns exit path.
    
    4) Fix missing limit object release, from Florian Westphal.
    
    5) Memleak in nf_tables object update path, also from Florian.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1e6ae0e46e32749b130f1823da30cea9aa2a59a0
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Mon Feb 21 09:50:29 2022 -0800

    mips: setup: fix setnocoherentio() boolean setting
    
    Correct a typo/pasto: setnocoherentio() should set
    dma_default_coherent to false, not true.
    
    Fixes: 14ac09a65e19 ("MIPS: refactor the runtime coherent vs noncoherent DMA indicators")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: linux-mips@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit d8f7a5484f2188e9af2d9e4e587587d724501b12
Author: Mårten Lindahl <marten.lindahl@axis.com>
Date:   Wed Feb 16 10:41:28 2022 +0100

    driver core: Free DMA range map when device is released
    
    When unbinding/binding a driver with DMA mapped memory, the DMA map is
    not freed before the driver is reloaded. This leads to a memory leak
    when the DMA map is overwritten when reprobing the driver.
    
    This can be reproduced with a platform driver having a dma-range:
    
    dummy {
            ...
            #address-cells = <0x2>;
            #size-cells = <0x2>;
            ranges;
            dma-ranges = <...>;
            ...
    };
    
    and then unbinding/binding it:
    
    ~# echo soc:dummy >/sys/bus/platform/drivers/<driver>/unbind
    
    DMA map object 0xffffff800b0ae540 still being held by &pdev->dev
    
    ~# echo soc:dummy >/sys/bus/platform/drivers/<driver>/bind
    ~# echo scan > /sys/kernel/debug/kmemleak
    ~# cat /sys/kernel/debug/kmemleak
    unreferenced object 0xffffff800b0ae540 (size 64):
      comm "sh", pid 833, jiffies 4295174550 (age 2535.352s)
      hex dump (first 32 bytes):
        00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00  ................
        00 00 00 80 00 00 00 00 00 00 00 80 00 00 00 00  ................
      backtrace:
        [<ffffffefd1694708>] create_object.isra.0+0x108/0x344
        [<ffffffefd1d1a850>] kmemleak_alloc+0x8c/0xd0
        [<ffffffefd167e2d0>] __kmalloc+0x440/0x6f0
        [<ffffffefd1a960a4>] of_dma_get_range+0x124/0x220
        [<ffffffefd1a8ce90>] of_dma_configure_id+0x40/0x2d0
        [<ffffffefd198b68c>] platform_dma_configure+0x5c/0xa4
        [<ffffffefd198846c>] really_probe+0x8c/0x514
        [<ffffffefd1988990>] __driver_probe_device+0x9c/0x19c
        [<ffffffefd1988cd8>] device_driver_attach+0x54/0xbc
        [<ffffffefd1986634>] bind_store+0xc4/0x120
        [<ffffffefd19856e0>] drv_attr_store+0x30/0x44
        [<ffffffefd173c9b0>] sysfs_kf_write+0x50/0x60
        [<ffffffefd173c1c4>] kernfs_fop_write_iter+0x124/0x1b4
        [<ffffffefd16a013c>] new_sync_write+0xdc/0x160
        [<ffffffefd16a256c>] vfs_write+0x23c/0x2a0
        [<ffffffefd16a2758>] ksys_write+0x64/0xec
    
    To prevent this we should free the dma_range_map when the device is
    released.
    
    Fixes: e0d072782c73 ("dma-mapping: introduce DMA range map, supplanting dma_pfn_offset")
    Cc: stable <stable@vger.kernel.org>
    Suggested-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
    Link: https://lore.kernel.org/r/20220216094128.4025861-1-marten.lindahl@axis.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit dad3bdeef45f81a6e90204bcc85360bb76eccec7
Author: Florian Westphal <fw@strlen.de>
Date:   Mon Feb 21 13:31:49 2022 +0100

    netfilter: nf_tables: fix memory leak during stateful obj update
    
    stateful objects can be updated from the control plane.
    The transaction logic allocates a temporary object for this purpose.
    
    The ->init function was called for this object, so plain kfree() leaks
    resources. We must call ->destroy function of the object.
    
    nft_obj_destroy does this, but it also decrements the module refcount,
    but the update path doesn't increment it.
    
    To avoid special-casing the update object release, do module_get for
    the update case too and release it via nft_obj_destroy().
    
    Fixes: d62d0ba97b58 ("netfilter: nf_tables: Introduce stateful object update operation")
    Cc: Fernando Fernandez Mancera <ffmancera@riseup.net>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 5f6b0f2d037c8864f20ff15311c695f65eb09db5
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Sat Feb 19 23:04:29 2022 +0300

    ata: pata_hpt37x: fix PCI clock detection
    
    The f_CNT register (at the PCI config. address 0x78) is 16-bit, not
    8-bit! The bug was there from the very start... :-(
    
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Fixes: 669a5db411d8 ("[libata] Add a bunch of PATA drivers.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 4d22336f903930eb94588b939c310743a3640276
Author: Michel Dänzer <mdaenzer@redhat.com>
Date:   Tue Feb 15 19:53:37 2022 +0100

    drm/amd/display: For vblank_disable_immediate, check PSR is really used
    
    Even if PSR is allowed for a present GPU, there might be no eDP link
    which supports PSR.
    
    Fixes: 708978487304 ("drm/amdgpu/display: Only set vblank_disable_immediate when PSR is not enabled")
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Michel Dänzer <mdaenzer@redhat.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit e3f3824874da78db5775a5cb9c0970cd1c6978bc
Author: Evan Quan <evan.quan@amd.com>
Date:   Thu Jan 20 19:16:19 2022 +0800

    drm/amd/pm: fix some OEM SKU specific stability issues
    
    Add a quirk in sienna_cichlid_ppt.c to fix some OEM SKU
    specific stability issues.
    
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit f626dd0ff05043e5a7154770cc7cda66acee33a3
Author: Evan Quan <evan.quan@amd.com>
Date:   Thu Jan 20 16:15:52 2022 +0800

    drm/amdgpu: disable MMHUB PG for Picasso
    
    MMHUB PG needs to be disabled for Picasso for stability reasons.
    
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 1432108d00e42ffa383240bcac8d58f89ae19104
Author: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Date:   Sat Feb 12 16:40:00 2022 +0100

    drm/amd/display: Protect update_bw_bounding_box FPU code.
    
    For DCN3/3.01/3.02 at least these use the fpu.
    
    v2: squash in build fix for when DCN is not enabled (Leo)
    
    Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit eebb0f4e894f1e9577a56b337693d1051dd6ebfd
Author: Phil Elwell <phil@raspberrypi.com>
Date:   Wed Feb 16 16:08:02 2022 +0000

    sc16is7xx: Fix for incorrect data being transmitted
    
    UART drivers are meant to use the port spinlock within certain
    methods, to protect against reentrancy. The sc16is7xx driver does
    very little locking, presumably because when added it triggers
    "scheduling while atomic" errors. This is due to the use of mutexes
    within the regmap abstraction layer, and the mutex implementation's
    habit of sleeping the current thread while waiting for access.
    Unfortunately this lack of interlocking can lead to corruption of
    outbound data, which occurs when the buffer used for I2C transmission
    is used simultaneously by two threads - a work queue thread running
    sc16is7xx_tx_proc, and an IRQ thread in sc16is7xx_port_irq, both
    of which can call sc16is7xx_handle_tx.
    
    An earlier patch added efr_lock, a mutex that controls access to the
    EFR register. This mutex is already claimed in the IRQ handler, and
    all that is required is to claim the same mutex in sc16is7xx_tx_proc.
    
    See: https://github.com/raspberrypi/linux/issues/4885
    
    Fixes: 6393ff1c4435 ("sc16is7xx: Use threaded IRQ")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Phil Elwell <phil@raspberrypi.com>
    Link: https://lore.kernel.org/r/20220216160802.1026013-1-phil@raspberrypi.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a2ab75b8e76e455af7867e3835fd9cdf386b508f
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:23 2022 -0800

    tty: n_gsm: fix deadlock in gsmtty_open()
    
    In the current implementation the user may open a virtual tty which then
    could fail to establish the underlying DLCI. The function gsmtty_open()
    gets stuck in tty_port_block_til_ready() while waiting for a carrier rise.
    This happens if the remote side fails to acknowledge the link establishment
    request in time or completely. At some point gsm_dlci_close() is called
    to abort the link establishment attempt. The function tries to inform the
    associated virtual tty by performing a hangup. But the blocking loop within
    tty_port_block_til_ready() is not informed about this event.
    The patch proposed here fixes this by resetting the initialization state of
    the virtual tty to ensure the loop exits and triggering it to make
    tty_port_block_til_ready() return.
    
    Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-7-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 687f9ad43c52501f46164758e908a5dd181a87fc
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:22 2022 -0800

    tty: n_gsm: fix wrong modem processing in convergence layer type 2
    
    The function gsm_process_modem() exists to handle modem status bits of
    incoming frames. This includes incoming MSC (modem status command) frames
    and convergence layer type 2 data frames. The function, however, was only
    designed to handle MSC frames as it expects the command length. Within
    gsm_dlci_data() it is wrongly assumed that this is the same as the data
    frame length. This is only true if the data frame contains only 1 byte of
    payload.
    
    This patch names the length parameter of gsm_process_modem() in a generic
    manner to reflect its association. It also corrects all calls to the
    function to handle the variable number of modem status octets correctly in
    both cases.
    
    Fixes: 7263287af93d ("tty: n_gsm: Fixed logic to decode break signal from modem status")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-6-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit c19d93542a6081577e6da9bf5e887979c72e80c1
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:21 2022 -0800

    tty: n_gsm: fix wrong tty control line for flow control
    
    tty flow control is handled via gsmtty_throttle() and gsmtty_unthrottle().
    Both functions propagate the outgoing hardware flow control state to the
    remote side via MSC (modem status command) frames. The local state is taken
    from the RTS (ready to send) flag of the tty. However, RTS gets mapped to
    DTR (data terminal ready), which is wrong.
    This patch corrects this by mapping RTS to RTS.
    
    Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-5-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 96b169f05cdcc844b400695184d77e42071d14f2
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:20 2022 -0800

    tty: n_gsm: fix NULL pointer access due to DLCI release
    
    The here fixed commit made the tty hangup asynchronous to avoid a circular
    locking warning. I could not reproduce this warning. Furthermore, due to
    the asynchronous hangup the function call now gets queued up while the
    underlying tty is being freed. Depending on the timing this results in a
    NULL pointer access in the global work queue scheduler. To be precise in
    process_one_work(). Therefore, the previous commit made the issue worse
    which it tried to fix.
    
    This patch fixes this by falling back to the old behavior which uses a
    blocking tty hangup call before freeing up the associated tty.
    
    Fixes: 7030082a7415 ("tty: n_gsm: avoid recursive locking with async port hangup")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-4-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e3b7468f082d106459e86e8dc6fb9bdd65553433
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:19 2022 -0800

    tty: n_gsm: fix proper link termination after failed open
    
    Trying to open a DLCI by sending a SABM frame may fail with a timeout.
    The link is closed on the initiator side without informing the responder
    about this event. The responder assumes the link is open after sending a
    UA frame to answer the SABM frame. The link gets stuck in a half open
    state.
    
    This patch fixes this by initiating the proper link termination procedure
    after link setup timeout instead of silently closing it down.
    
    Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-3-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 57435c42400ec147a527b2313188b649e81e449e
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:18 2022 -0800

    tty: n_gsm: fix encoding of command/response bit
    
    n_gsm is based on the 3GPP 07.010 and its newer version is the 3GPP 27.010.
    See https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1516
    The changes from 07.010 to 27.010 are non-functional. Therefore, I refer to
    the newer 27.010 here. Chapter 5.2.1.2 describes the encoding of the
    C/R (command/response) bit. Table 1 shows that the actual encoding of the
    C/R bit is inverted if the associated frame is sent by the responder.
    
    The referenced commit fixed here further broke the internal meaning of this
    bit in the outgoing path by always setting the C/R bit regardless of the
    frame type.
    
    This patch fixes both by setting the C/R bit always consistently for
    command (1) and response (0) frames and inverting it later for the
    responder where necessary. The meaning of this bit in the debug output
    is being preserved and shows the bit as if it was encoded by the initiator.
    This reflects only the frame type rather than the encoded combination of
    communication side and frame type.
    
    Fixes: cc0f42122a7e ("tty: n_gsm: Modify CR,PF bit when config requester")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-2-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 737b0ef3be6b319d6c1fd64193d1603311969326
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Feb 17 23:31:17 2022 -0800

    tty: n_gsm: fix encoding of control signal octet bit DV
    
    n_gsm is based on the 3GPP 07.010 and its newer version is the 3GPP 27.010.
    See https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1516
    The changes from 07.010 to 27.010 are non-functional. Therefore, I refer to
    the newer 27.010 here. Chapter 5.4.6.3.7 describes the encoding of the
    control signal octet used by the MSC (modem status command). The same
    encoding is also used in convergence layer type 2 as described in chapter
    5.5.2. Table 7 and 24 both require the DV (data valid) bit to be set 1 for
    outgoing control signal octets sent by the DTE (data terminal equipment),
    i.e. for the initiator side.
    Currently, the DV bit is only set if CD (carrier detect) is on, regardless
    of the side.
    
    This patch fixes this behavior by setting the DV bit on the initiator side
    unconditionally.
    
    Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220218073123.2121-1-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 038101e6b2cd5c55f888f85db42ea2ad3aecb4b6
Merge: cfb92440ee71a ae09639e3b2a0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 21 09:10:53 2022 -0800

    Merge tag 'platform-drivers-x86-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
    
    Pull x86 platform driver fixes from Hans de Goede:
     "Two small fixes and one hardware-id addition"
    
    * tag 'platform-drivers-x86-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:
      platform/x86: int3472: Add terminator to gpiod_lookup_table
      platform/x86: asus-wmi: Fix regression when probing for fan curve control
      platform/x86: thinkpad_acpi: Add dual-fan quirk for T15g (2nd gen)

commit 6c7621890995d089a56a06d11580d185ede7c2f8
Author: Christophe Kerello <christophe.kerello@foss.st.com>
Date:   Sun Feb 20 15:14:32 2022 +0000

    mtd: core: Fix a conflict between MTD and NVMEM on wp-gpios property
    
    Wp-gpios property can be used on NVMEM nodes and the same property can
    be also used on MTD NAND nodes. In case of the wp-gpios property is
    defined at NAND level node, the GPIO management is done at NAND driver
    level. Write protect is disabled when the driver is probed or resumed
    and is enabled when the driver is released or suspended.
    
    When no partitions are defined in the NAND DT node, then the NAND DT node
    will be passed to NVMEM framework. If wp-gpios property is defined in
    this node, the GPIO resource is taken twice and the NAND controller
    driver fails to probe.
    
    A new Boolean flag named ignore_wp has been added in nvmem_config.
    In case ignore_wp is set, it means that the GPIO is handled by the
    provider. Lets set this flag in MTD layer to avoid the conflict on
    wp_gpios property.
    
    Fixes: 2a127da461a9 ("nvmem: add support for the write-protect pin")
    Cc: stable@vger.kernel.org
    Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220220151432.16605-3-srinivas.kandagatla@linaro.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit f6c052afe6f802d87c74153b7a57c43b2e9faf07
Author: Christophe Kerello <christophe.kerello@foss.st.com>
Date:   Sun Feb 20 15:14:31 2022 +0000

    nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property
    
    Wp-gpios property can be used on NVMEM nodes and the same property can
    be also used on MTD NAND nodes. In case of the wp-gpios property is
    defined at NAND level node, the GPIO management is done at NAND driver
    level. Write protect is disabled when the driver is probed or resumed
    and is enabled when the driver is released or suspended.
    
    When no partitions are defined in the NAND DT node, then the NAND DT node
    will be passed to NVMEM framework. If wp-gpios property is defined in
    this node, the GPIO resource is taken twice and the NAND controller
    driver fails to probe.
    
    It would be possible to set config->wp_gpio at MTD level before calling
    nvmem_register function but NVMEM framework will toggle this GPIO on
    each write when this GPIO should only be controlled at NAND level driver
    to ensure that the Write Protect has not been enabled.
    
    A way to fix this conflict is to add a new boolean flag in nvmem_config
    named ignore_wp. In case ignore_wp is set, the GPIO resource will
    be managed by the provider.
    
    Fixes: 2a127da461a9 ("nvmem: add support for the write-protect pin")
    Cc: stable@vger.kernel.org
    Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220220151432.16605-2-srinivas.kandagatla@linaro.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit efe8a1e7cad456075247488f92a05f9cc2ddb394
Merge: 754e0b0e35608 ea85bf9064661
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Mon Feb 21 17:58:09 2022 +0100

    Merge tag 'iio-fixes-for-5.17a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into char-misc-linus
    
    Jonathan writes:
    
    1st set of IIO fixes for the 5.17 cycle.
    
    Several drivers:
     - Fix a failure to disable runtime in probe error paths. All cases
       were introduced in the same rework patch.
    
    adi,ad7124
     - Fix incorrect register masking.
    adi,ad74413r
     - Avoid referencing negative array offsets.
     - Use ngpio size when iterating over mask not numebr of channels.
     - Fix issue with wrong mask uage getting GPIOs.
    adi,admv1014
     - Drop check on unsigned less than 0.
    adi,ads16480
     - Correctly handle devices that don't have burst mode support.
    fsl,fxls8962af
     - Add missing padding needed between address and data for SPI transfers.
    men_z188
     - Fix iomap leak in error path.
    st,lsm6dsx
     - Wait for setting time in oneshot reads to get a stable result.
    ti,tsc2046
     - Prevent an array overflow.
    
    * tag 'iio-fixes-for-5.17a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio:
      iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
      iio: Fix error handling for PM
      iio: addac: ad74413r: correct comparator gpio getters mask usage
      iio: addac: ad74413r: use ngpio size when iterating over mask
      iio: addac: ad74413r: Do not reference negative array offsets
      iio: adc: men_z188_adc: Fix a resource leak in an error handling path
      iio: frequency: admv1013: remove the always true condition
      iio: accel: fxls8962af: add padding to regmap for SPI
      iio:imu:adis16480: fix buffering for devices with no burst mode
      iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
      iio: adc: tsc2046: fix memory corruption by preventing array overflow

commit 9d2231c5d74e13b2a0546fee6737ee4446017903
Author: Max Kellermann <max.kellermann@ionos.com>
Date:   Mon Feb 21 11:03:13 2022 +0100

    lib/iov_iter: initialize "flags" in new pipe_buffer
    
    The functions copy_page_to_iter_pipe() and push_pipe() can both
    allocate a new pipe_buffer, but the "flags" member initializer is
    missing.
    
    Fixes: 241699cd72a8 ("new iov_iter flavour: pipe-backed")
    To: Alexander Viro <viro@zeniv.linux.org.uk>
    To: linux-fsdevel@vger.kernel.org
    To: linux-kernel@vger.kernel.org
    Cc: stable@vger.kernel.org
    Signed-off-by: Max Kellermann <max.kellermann@ionos.com>
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

commit 11c57c3ba94da74c3446924260e34e0b1950b5d7
Author: Julian Braha <julianbraha@gmail.com>
Date:   Mon Jan 17 05:09:40 2022 +0100

    ARM: 9178/1: fix unmet dependency on BITREVERSE for HAVE_ARCH_BITREVERSE
    
    Resending this to properly add it to the patch tracker - thanks for letting
    me know, Arnd :)
    
    When ARM is enabled, and BITREVERSE is disabled,
    Kbuild gives the following warning:
    
    WARNING: unmet direct dependencies detected for HAVE_ARCH_BITREVERSE
      Depends on [n]: BITREVERSE [=n]
      Selected by [y]:
      - ARM [=y] && (CPU_32v7M [=n] || CPU_32v7 [=y]) && !CPU_32v6 [=n]
    
    This is because ARM selects HAVE_ARCH_BITREVERSE
    without selecting BITREVERSE, despite
    HAVE_ARCH_BITREVERSE depending on BITREVERSE.
    
    This unmet dependency bug was found by Kismet,
    a static analysis tool for Kconfig. Please advise if this
    is not the appropriate solution.
    
    Signed-off-by: Julian Braha <julianbraha@gmail.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit d920eaa4c4559f59be7b4c2d26fa0a2e1aaa3da9
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Wed Feb 16 15:37:38 2022 +0000

    ARM: Fix kgdb breakpoint for Thumb2
    
    The kgdb code needs to register an undef hook for the Thumb UDF
    instruction that will fault in order to be functional on Thumb2
    platforms.
    
    Reported-by: Johannes Stezenbach <js@sig21.net>
    Tested-by: Johannes Stezenbach <js@sig21.net>
    Fixes: 5cbad0ebf45c ("kgdb: support for ARCH=arm")
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 1a58f84ea5df7f026bf92a0009f931bf547fe965
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Feb 18 13:17:05 2022 +0100

    netfilter: nft_limit: fix stateful object memory leak
    
    We need to provide a destroy callback to release the extra fields.
    
    Fixes: 3b9e2ea6c11b ("netfilter: nft_limit: move stateful fields out of expression data")
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 6069da443bf65f513bb507bb21e2f87cfb1ad0b6
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Fri Feb 18 12:45:32 2022 +0100

    netfilter: nf_tables: unregister flowtable hooks on netns exit
    
    Unregister flowtable hooks before they are releases via
    nf_tables_flowtable_destroy() otherwise hook core reports UAF.
    
    BUG: KASAN: use-after-free in nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142
    Read of size 4 at addr ffff8880736f7438 by task syz-executor579/3666
    
    CPU: 0 PID: 3666 Comm: syz-executor579 Not tainted 5.16.0-rc5-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106
     dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 lib/dump_stack.c:106
     print_address_description+0x65/0x380 mm/kasan/report.c:247 mm/kasan/report.c:247
     __kasan_report mm/kasan/report.c:433 [inline]
     __kasan_report mm/kasan/report.c:433 [inline] mm/kasan/report.c:450
     kasan_report+0x19a/0x1f0 mm/kasan/report.c:450 mm/kasan/report.c:450
     nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142
     __nf_register_net_hook+0x27e/0x8d0 net/netfilter/core.c:429 net/netfilter/core.c:429
     nf_register_net_hook+0xaa/0x180 net/netfilter/core.c:571 net/netfilter/core.c:571
     nft_register_flowtable_net_hooks+0x3c5/0x730 net/netfilter/nf_tables_api.c:7232 net/netfilter/nf_tables_api.c:7232
     nf_tables_newflowtable+0x2022/0x2cf0 net/netfilter/nf_tables_api.c:7430 net/netfilter/nf_tables_api.c:7430
     nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline]
     nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline]
     nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] net/netfilter/nfnetlink.c:652
     nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] net/netfilter/nfnetlink.c:652
     nfnetlink_rcv+0x10e6/0x2550 net/netfilter/nfnetlink.c:652 net/netfilter/nfnetlink.c:652
    
    __nft_release_hook() calls nft_unregister_flowtable_net_hooks() which
    only unregisters the hooks, then after RCU grace period, it is
    guaranteed that no packets add new entries to the flowtable (no flow
    offload rules and flowtable hooks are reachable from packet path), so it
    is safe to call nf_flow_table_free() which cleans up the remaining
    entries from the flowtable (both software and hardware) and it unbinds
    the flow_block.
    
    Fixes: ff4bf2f42a40 ("netfilter: nf_tables: add nft_unregister_flowtable_hook()")
    Reported-by: syzbot+e918523f77e62790d6d9@syzkaller.appspotmail.com
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit c086df4902573e2f06c6a2a83452c13a8bc603f5
Author: Jeff Layton <jlayton@kernel.org>
Date:   Mon Jan 10 18:52:52 2022 -0500

    fuse: move FUSE_SUPER_MAGIC definition to magic.h
    
    ...to help userland apps that need to identify FUSE mounts.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

commit ae09639e3b2a0291b37b122c94dd4f773cd4e513
Author: Daniel Scally <djrscally@gmail.com>
Date:   Wed Feb 16 22:53:02 2022 +0000

    platform/x86: int3472: Add terminator to gpiod_lookup_table
    
    Without the terminator, if a con_id is passed to gpio_find() that
    does not exist in the lookup table the function will not stop looping
    correctly, and eventually cause an oops.
    
    Fixes: 19d8d6e36b4b ("platform/x86: int3472: Pass tps68470_regulator_platform_data to the tps68470-regulator MFD-cell")
    Signed-off-by: Daniel Scally <djrscally@gmail.com>
    Link: https://lore.kernel.org/r/20220216225304.53911-5-djrscally@gmail.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit b6ad6261d27708567b309fdb3102b12c42a070cc
Author: Baruch Siach <baruch.siach@siklu.com>
Date:   Mon Feb 21 13:45:57 2022 +0200

    net: mdio-ipq4019: add delay after clock enable
    
    Experimentation shows that PHY detect might fail when the code attempts
    MDIO bus read immediately after clock enable. Add delay to stabilize the
    clock before bus access.
    
    PHY detect failure started to show after commit 7590fc6f80ac ("net:
    mdio: Demote probed message to debug print") that removed coincidental
    delay between clock enable and bus access.
    
    10ms is meant to match the time it take to send the probed message over
    UART at 115200 bps. This might be a far overshoot.
    
    Fixes: 23a890d493e3 ("net: mdio: Add the reset function for IPQ MDIO driver")
    Signed-off-by: Baruch Siach <baruch.siach@siklu.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 228339662b398a59b3560cd571deb8b25b253c7e
Author: Jens Axboe <axboe@kernel.dk>
Date:   Mon Feb 21 05:49:30 2022 -0700

    io_uring: don't convert to jiffies for waiting on timeouts
    
    If an application calls io_uring_enter(2) with a timespec passed in,
    convert that timespec to ktime_t rather than jiffies. The latter does
    not provide the granularity the application may expect, and may in
    fact provided different granularity on different systems, depending
    on what the HZ value is configured at.
    
    Turn the timespec into an absolute ktime_t, and use that with
    schedule_hrtimeout() instead.
    
    Link: https://github.com/axboe/liburing/issues/531
    Cc: stable@vger.kernel.org
    Reported-by: Bob Chen <chenbo.chen@alibaba-inc.com>
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit cc20cced0598d9a5ff91ae4ab147b3b5e99ee819
Author: Tao Liu <thomas.liu@ucloud.cn>
Date:   Fri Feb 18 22:35:24 2022 +0800

    gso: do not skip outer ip header in case of ipip and net_failover
    
    We encounter a tcp drop issue in our cloud environment. Packet GROed in
    host forwards to a VM virtio_net nic with net_failover enabled. VM acts
    as a IPVS LB with ipip encapsulation. The full path like:
    host gro -> vm virtio_net rx -> net_failover rx -> ipvs fullnat
     -> ipip encap -> net_failover tx -> virtio_net tx
    
    When net_failover transmits a ipip pkt (gso_type = 0x0103, which means
    SKB_GSO_TCPV4, SKB_GSO_DODGY and SKB_GSO_IPXIP4), there is no gso
    did because it supports TSO and GSO_IPXIP4. But network_header points to
    inner ip header.
    
    Call Trace:
     tcp4_gso_segment        ------> return NULL
     inet_gso_segment        ------> inner iph, network_header points to
     ipip_gso_segment
     inet_gso_segment        ------> outer iph
     skb_mac_gso_segment
    
    Afterwards virtio_net transmits the pkt, only inner ip header is modified.
    And the outer one just keeps unchanged. The pkt will be dropped in remote
    host.
    
    Call Trace:
     inet_gso_segment        ------> inner iph, outer iph is skipped
     skb_mac_gso_segment
     __skb_gso_segment
     validate_xmit_skb
     validate_xmit_skb_list
     sch_direct_xmit
     __qdisc_run
     __dev_queue_xmit        ------> virtio_net
     dev_hard_start_xmit
     __dev_queue_xmit        ------> net_failover
     ip_finish_output2
     ip_output
     iptunnel_xmit
     ip_tunnel_xmit
     ipip_tunnel_xmit        ------> ipip
     dev_hard_start_xmit
     __dev_queue_xmit
     ip_finish_output2
     ip_output
     ip_forward
     ip_rcv
     __netif_receive_skb_one_core
     netif_receive_skb_internal
     napi_gro_receive
     receive_buf
     virtnet_poll
     net_rx_action
    
    The root cause of this issue is specific with the rare combination of
    SKB_GSO_DODGY and a tunnel device that adds an SKB_GSO_ tunnel option.
    SKB_GSO_DODGY is set from external virtio_net. We need to reset network
    header when callbacks.gso_segment() returns NULL.
    
    This patch also includes ipv6_gso_segment(), considering SIT, etc.
    
    Fixes: cb32f511a70b ("ipip: add GSO/TSO support")
    Signed-off-by: Tao Liu <thomas.liu@ucloud.cn>
    Reviewed-by: Willem de Bruijn <willemb@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 221944736f66f38e9bdbce52c616d10df7f15c54
Author: Roman Gushchin <roman.gushchin@linux.dev>
Date:   Wed Feb 16 12:43:30 2022 -0800

    tools/cgroup/slabinfo: update to work with struct slab
    
    After the introduction of the dedicated struct slab to describe slab
    pages by commit d122019bf061 ("mm: Split slab into its own type") and
    the following removal of the corresponding struct page's fields by
    commit 07f910f9b729 ("mm: Remove slab from struct page") the
    memcg_slabinfo tool broke. An attempt to run it produces a trace like
    this:
    Traceback (most recent call last):
      File "/usr/bin/drgn", line 33, in <module>
        sys.exit(load_entry_point('drgn==0.0.16', 'console_scripts', 'drgn')())
      File "/usr/lib64/python3.9/site-packages/drgn/internal/cli.py", line 133, in main
        runpy.run_path(args.script[0], init_globals=init_globals, run_name="__main__")
      File "/usr/lib64/python3.9/runpy.py", line 268, in run_path
        return _run_module_code(code, init_globals, run_name,
      File "/usr/lib64/python3.9/runpy.py", line 97, in _run_module_code
        _run_code(code, mod_globals, init_globals,
      File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code
        exec(code, run_globals)
      File "memcg_slabinfo.py", line 226, in <module>
        main()
      File "memcg_slabinfo.py", line 199, in main
        cache = page.slab_cache
    AttributeError: 'struct page' has no member 'slab_cache'
    
    The problem can be fixed by explicitly casting struct page * to struct
    slab * for slab pages. The tools works as expected with this fix, e.g.:
    
    cred_jar             776    776    192   21    1 : tunables    0    0    0 : slabdata    547    547      0
    kmalloc-cg-32          6      6     32  128    1 : tunables    0    0    0 : slabdata      9      9      0
    files_cache            3      3    832   39    8 : tunables    0    0    0 : slabdata      8      8      0
    kmalloc-cg-512         1      1    512   32    4 : tunables    0    0    0 : slabdata     10     10      0
    task_struct           10     10   6720    4    8 : tunables    0    0    0 : slabdata     63     63      0
    mm_struct              3      3   1664   19    8 : tunables    0    0    0 : slabdata      9      9      0
    kmalloc-cg-16          1      1     16  256    1 : tunables    0    0    0 : slabdata      8      8      0
    pde_opener             1      1     40  102    1 : tunables    0    0    0 : slabdata      8      8      0
    anon_vma_chain       375    375     64   64    1 : tunables    0    0    0 : slabdata     81     81      0
    radix_tree_node        3      3    584   28    4 : tunables    0    0    0 : slabdata    419    419      0
    dentry                98     98    312   26    2 : tunables    0    0    0 : slabdata   1420   1420      0
    btrfs_inode            3      3   2368   13    8 : tunables    0    0    0 : slabdata    730    730      0
    signal_cache           3      3   1600   20    8 : tunables    0    0    0 : slabdata     17     17      0
    sighand_cache          3      3   2240   14    8 : tunables    0    0    0 : slabdata     20     20      0
    filp                  90     90    512   32    4 : tunables    0    0    0 : slabdata     95     95      0
    anon_vma             214    214    200   20    1 : tunables    0    0    0 : slabdata    162    162      0
    kmalloc-cg-1k          1      1   1024   32    8 : tunables    0    0    0 : slabdata     22     22      0
    pid                   10     10    256   32    2 : tunables    0    0    0 : slabdata     14     14      0
    kmalloc-cg-64          2      2     64   64    1 : tunables    0    0    0 : slabdata      8      8      0
    kmalloc-cg-96          3      3     96   42    1 : tunables    0    0    0 : slabdata      8      8      0
    sock_inode_cache       5      5   1408   23    8 : tunables    0    0    0 : slabdata     29     29      0
    UNIX                   7      7   1920   17    8 : tunables    0    0    0 : slabdata     21     21      0
    inode_cache           36     36   1152   28    8 : tunables    0    0    0 : slabdata    680    680      0
    proc_inode_cache      26     26   1224   26    8 : tunables    0    0    0 : slabdata     64     64      0
    kmalloc-cg-2k          2      2   2048   16    8 : tunables    0    0    0 : slabdata      9      9      0
    
    v2: change naming and count_partial()/count_free()/for_each_slab()
        signatures to work with slabs, suggested by Matthew Wilcox
    
    Fixes: 07f910f9b729 ("mm: Remove slab from struct page")
    Reported-by: Vasily Averin <vvs@virtuozzo.com>
    Signed-off-by: Roman Gushchin <guro@fb.com>
    Tested-by: Vasily Averin <vvs@virtuozzo.com>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Link: https://lore.kernel.org/linux-patches/Yg2cKKnIboNu7j+p@carbon.DHCP.thefacebook.com/

commit 93dd04ab0b2b32ae6e70284afc764c577156658e
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri Feb 18 14:13:58 2022 +0100

    slab: remove __alloc_size attribute from __kmalloc_track_caller
    
    Commit c37495d6254c ("slab: add __alloc_size attributes for better
    bounds checking") added __alloc_size attributes to a bunch of kmalloc
    function prototypes.  Unfortunately the change to __kmalloc_track_caller
    seems to cause clang to generate broken code and the first time this is
    called when booting, the box will crash.
    
    While the compiler problems are being reworked and attempted to be
    solved [1], let's just drop the attribute to solve the issue now.  Once
    it is resolved it can be added back.
    
    [1] https://github.com/ClangBuiltLinux/linux/issues/1599
    
    Fixes: c37495d6254c ("slab: add __alloc_size attributes for better bounds checking")
    Cc: stable <stable@vger.kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Daniel Micay <danielmicay@gmail.com>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Nathan Chancellor <nathan@kernel.org>
    Cc: linux-mm@kvack.org
    Cc: linux-kernel@vger.kernel.org
    Cc: llvm@lists.linux.dev
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Acked-by: Nick Desaulniers <ndesaulniers@google.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Acked-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Link: https://lore.kernel.org/r/20220218131358.3032912-1-gregkh@linuxfoundation.org

commit 28adef861233c6fce47372ebd2070b55eaa8e899
Author: Matt Roper <matthew.d.roper@intel.com>
Date:   Tue Feb 15 08:35:45 2022 -0800

    drm/i915/dg2: Print PHY name properly on calibration error
    
    We need to use phy_name() to convert the PHY value into a human-readable
    character in the error message.
    
    Fixes: a6a128116e55 ("drm/i915/dg2: Wait for SNPS PHY calibration during display init")
    Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
    Reviewed-by: Swathi Dhanavanthri <swathi.dhanavanthri@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220215163545.2175730-1-matthew.d.roper@intel.com
    (cherry picked from commit 84073e568eec7b586b2f6fd5fb2fb08f59edec54)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit ec663bca9128f13eada25cd0446e7fcb5fcdc088
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Feb 18 08:40:35 2022 +0200

    drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV
    
    If the only thing that is changing is SAGV vs. no SAGV but
    the number of active planes and the total data rates end up
    unchanged we currently bail out of intel_bw_atomic_check()
    early and forget to actually compute the new WGV point
    mask and thus won't actually enable/disable SAGV as requested.
    This ends up poorly if we end up running with SAGV enabled
    when we shouldn't. Usually ends up in underruns.
    
    To fix this let's go through the QGV point mask computation
    if either the data rates/number of planes, or the state
    of SAGV is changing.
    
    v2: Check more carefully if things are changing to avoid
        the extra calculations/debugs from introducing unwanted
        overhead
    
    Cc: stable@vger.kernel.org
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com> #v1
    Fixes: 20f505f22531 ("drm/i915: Restrict qgv points which don't have enough bandwidth.")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220218064039.12834-3-ville.syrjala@linux.intel.com
    (cherry picked from commit 6b728595ffa51c087343c716bccbfc260f120e72)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit afc189df6bcc6be65961deb54e15ec60e7f85337
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Feb 18 08:40:34 2022 +0200

    drm/i915: Correctly populate use_sagv_wm for all pipes
    
    When changing between SAGV vs. no SAGV on tgl+ we have to
    update the use_sagv_wm flag for all the crtcs or else
    an active pipe not already in the state will end up using
    the wrong watermarks. That is especially bad when we end up
    with the tighter non-SAGV watermarks with SAGV enabled.
    Usually ends up in underruns.
    
    Cc: stable@vger.kernel.org
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    Fixes: 7241c57d3140 ("drm/i915: Add TGL+ SAGV support")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220218064039.12834-2-ville.syrjala@linux.intel.com
    (cherry picked from commit 8dd8ffb824ca7b897ce9f2082ffa7e64831c22dc)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit a40ee54e9a0958406469d46def03eec62aea0b69
Author: Imre Deak <imre.deak@intel.com>
Date:   Thu Feb 17 17:22:37 2022 +0200

    drm/i915: Disconnect PHYs left connected by BIOS on disabled ports
    
    BIOS may leave a TypeC PHY in a connected state even though the
    corresponding port is disabled. This will prevent any hotplug events
    from being signalled (after the monitor deasserts and then reasserts its
    HPD) until the PHY is disconnected and so the driver will not detect a
    connected sink. Rebooting with the PHY in the connected state also
    results in a system hang.
    
    Fix the above by disconnecting TypeC PHYs on disabled ports.
    
    Before commit 64851a32c463e5 the PHY connected state was read out even
    for disabled ports and later the PHY got disconnected as a side effect
    of a tc_port_lock/unlock() sequence (during connector probing), hence
    recovering the port's hotplug functionality.
    
    Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5014
    Fixes: 64851a32c463 ("drm/i915/tc: Add a mode for the TypeC PHY's disconnected state")
    Cc: <stable@vger.kernel.org> # v5.16+
    Cc: José Roberto de Souza <jose.souza@intel.com>
    Signed-off-by: Imre Deak <imre.deak@intel.com>
    Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220217152237.670220-1-imre.deak@intel.com
    (cherry picked from commit ed0ccf349ffd9c80e7376d4d8c608643de990e86)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 3f33364836aacc28cd430d22cf22379e3b5ecd77
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Mon Feb 14 11:18:08 2022 +0200

    drm/i915: Widen the QGV point mask
    
    adlp+ adds some extra bits to the QGV point mask. The code attempts
    to handle that but forgot to actually make sure we can store those
    bits in the bw state. Fix it.
    
    Cc: stable@vger.kernel.org
    Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    Fixes: 192fbfb76744 ("drm/i915: Implement PSF GV point support")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220214091811.13725-4-ville.syrjala@linux.intel.com
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    (cherry picked from commit c0299cc9840b3805205173cc77782f317b78ea0e)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 44a3918c8245ab10c6c9719dd12e7a8d291980d8
Author: Josh Poimboeuf <jpoimboe@redhat.com>
Date:   Fri Feb 18 11:49:08 2022 -0800

    x86/speculation: Include unprivileged eBPF status in Spectre v2 mitigation reporting
    
    With unprivileged eBPF enabled, eIBRS (without retpoline) is vulnerable
    to Spectre v2 BHB-based attacks.
    
    When both are enabled, print a warning message and report it in the
    'spectre_v2' sysfs vulnerabilities file.
    
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

commit 5ad3eb1132453b9795ce5fd4572b1c18b292cca9
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Wed Feb 16 20:57:02 2022 +0100

    Documentation/hw-vuln: Update spectre doc
    
    Update the doc with the new fun.
    
      [ bp: Massage commit message. ]
    
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

commit 1e19da8522c81bf46b335f84137165741e0d82b7
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Wed Feb 16 20:57:01 2022 +0100

    x86/speculation: Add eIBRS + Retpoline options
    
    Thanks to the chaps at VUsec it is now clear that eIBRS is not
    sufficient, therefore allow enabling of retpolines along with eIBRS.
    
    Add spectre_v2=eibrs, spectre_v2=eibrs,lfence and
    spectre_v2=eibrs,retpoline options to explicitly pick your preferred
    means of mitigation.
    
    Since there's new mitigations there's also user visible changes in
    /sys/devices/system/cpu/vulnerabilities/spectre_v2 to reflect these
    new mitigations.
    
      [ bp: Massage commit message, trim error messages,
        do more precise eIBRS mode checking. ]
    
    Co-developed-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Patrick Colp <patrick.colp@oracle.com>
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

commit d45476d9832409371537013ebdd8dc1a7781f97a
Author: Peter Zijlstra (Intel) <peterz@infradead.org>
Date:   Wed Feb 16 20:57:00 2022 +0100

    x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
    
    The RETPOLINE_AMD name is unfortunate since it isn't necessarily
    AMD only, in fact Hygon also uses it. Furthermore it will likely be
    sufficient for some Intel processors. Therefore rename the thing to
    RETPOLINE_LFENCE to better describe what it is.
    
    Add the spectre_v2=retpoline,lfence option as an alias to
    spectre_v2=retpoline,amd to preserve existing setups. However, the output
    of /sys/devices/system/cpu/vulnerabilities/spectre_v2 will be changed.
    
      [ bp: Fix typos, massage. ]
    
    Co-developed-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

commit cfc4442c642d568014474b6718ccf65dc7ca6099
Author: Daniele Palmas <dnlplm@gmail.com>
Date:   Fri Feb 18 14:45:52 2022 +0100

    USB: serial: option: add Telit LE910R1 compositions
    
    Add support for the following Telit LE910R1 compositions:
    
    0x701a: rndis, tty, tty, tty
    0x701b: ecm, tty, tty, tty
    0x9201: tty
    
    Signed-off-by: Daniele Palmas <dnlplm@gmail.com>
    Link: https://lore.kernel.org/r/20220218134552.4051-1-dnlplm@gmail.com
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit 6ecb3f0b18b320320460a42e40d6fb603f6ded96
Author: Slark Xiao <slark_xiao@163.com>
Date:   Mon Feb 14 10:14:01 2022 +0800

    USB: serial: option: add support for DW5829e
    
    Dell DW5829e same as DW5821e except CAT level.
    DW5821e supports CAT16 but DW5829e supports CAT9.
    There are 2 types product of DW5829e: normal and eSIM.
    So we will add 2 PID for DW5829e.
    And for each PID, it support MBIM or RMNET.
    Let's see test evidence as below:
    
    DW5829e MBIM mode:
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  2
    P:  Vendor=413c ProdID=81e6 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 7 Cfg#= 2 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
    I:  If#=0x1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    I:  If#=0x6 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    
    DW5829e RMNET mode:
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  5 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  1
    P:  Vendor=413c ProdID=81e6 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    
    DW5829e-eSIM MBIM mode:
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  2
    P:  Vendor=413c ProdID=81e4 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e-eSIM Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 7 Cfg#= 2 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
    I:  If#=0x1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    I:  If#=0x6 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    
    DW5829e-eSIM RMNET mode:
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  7 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  1
    P:  Vendor=413c ProdID=81e4 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e-eSIM Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    
    BTW, the interface 0x6 of MBIM mode is GNSS port, which not same as NMEA
    port. So it's banned from serial option driver.
    The remaining interfaces 0x2-0x5 are: MODEM, MODEM, NMEA, DIAG.
    
    Signed-off-by: Slark Xiao <slark_xiao@163.com>
    Link: https://lore.kernel.org/r/20220214021401.6264-1-slark_xiao@163.com
    [ johan: drop unnecessary reservation of interface 1 ]
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit 198a7ebd5fa17b4d0be8cb70240ee1be885175c0
Author: Dmytro Bagrii <dimich.dmb@gmail.com>
Date:   Thu Feb 10 18:41:37 2022 +0200

    Revert "USB: serial: ch341: add new Product ID for CH341A"
    
    This reverts commit 46ee4abb10a07bd8f8ce910ee6b4ae6a947d7f63.
    
    CH341 has Product ID 0x5512 in EPP/MEM mode which is used for
    I2C/SPI/GPIO interfaces. In asynchronous serial interface mode
    CH341 has PID 0x5523 which is already in the table.
    
    Mode is selected by corresponding jumper setting.
    
    Signed-off-by: Dmytro Bagrii <dimich.dmb@gmail.com>
    Link: https://lore.kernel.org/r/20220210164137.4376-1-dimich.dmb@gmail.com
    Link: https://lore.kernel.org/r/YJ0OCS/sh+1ifD/q@hovoldconsulting.com
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit fc3ef2e3297b3c0e2006b5d7b3d66965e3392036
Author: Pavel Skripkin <paskripkin@gmail.com>
Date:   Sun Feb 20 19:01:14 2022 +0300

    HID: hid-thrustmaster: fix OOB read in thrustmaster_interrupts
    
    Syzbot reported an slab-out-of-bounds Read in thrustmaster_probe() bug.
    The root case is in missing validation check of actual number of endpoints.
    
    Code should not blindly access usb_host_interface::endpoint array, since
    it may contain less endpoints than code expects.
    
    Fix it by adding missing validaion check and print an error if
    number of endpoints do not match expected number
    
    Fixes: c49c33637802 ("HID: support for initialization of some Thrustmaster wheels")
    Reported-and-tested-by: syzbot+35eebd505e97d315d01c@syzkaller.appspotmail.com
    Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit fa231bef3b34f1670b240409c11e59a3ce095e6d
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Date:   Fri Feb 18 23:57:20 2022 +0200

    soc: imx: gpcv2: Fix clock disabling imbalance in error path
    
    The imx_pgc_power_down() starts by enabling the domain clocks, and thus
    disables them in the error path. Commit 18c98573a4cf ("soc: imx: gpcv2:
    add domain option to keep domain clocks enabled") made the clock enable
    conditional, but forgot to add the same condition to the error path.
    This can result in a clock enable/disable imbalance. Fix it.
    
    Fixes: 18c98573a4cf ("soc: imx: gpcv2: add domain option to keep domain clocks enabled")
    Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit ba1366f3d039e7c3ca1fc29ed00ce3ed2b8fd32f
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Sun Feb 13 14:54:05 2022 +0100

    PCI: vmd: Prevent recursive locking on interrupt allocation
    
    Tejas reported the following recursive locking issue:
    
     swapper/0/1 is trying to acquire lock:
     ffff8881074fd0a0 (&md->mutex){+.+.}-{3:3}, at: msi_get_virq+0x30/0xc0
    
     but task is already holding lock:
     ffff8881017cd6a0 (&md->mutex){+.+.}-{3:3}, at: __pci_enable_msi_range+0xf2/0x290
    
     stack backtrace:
      __mutex_lock+0x9d/0x920
      msi_get_virq+0x30/0xc0
      pci_irq_vector+0x26/0x30
      vmd_msi_init+0xcc/0x210
      msi_domain_alloc+0xbf/0x150
      msi_domain_alloc_irqs_descs_locked+0x3e/0xb0
      __pci_enable_msi_range+0x155/0x290
      pci_alloc_irq_vectors_affinity+0xba/0x100
      pcie_port_device_register+0x307/0x550
      pcie_portdrv_probe+0x3c/0xd0
      pci_device_probe+0x95/0x110
    
    This is caused by the VMD MSI code which does a lookup of the Linux
    interrupt number for an VMD managed MSI[X] vector. The lookup function
    tries to acquire the already held mutex.
    
    Avoid that by caching the Linux interrupt number at initialization time
    instead of looking it up over and over.
    
    Fixes: 82ff8e6b78fc ("PCI/MSI: Use msi_get_virq() in pci_get_vector()")
    Reported-by: "Surendrakumar Upadhyay, TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Tested-by: "Surendrakumar Upadhyay, TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
    Cc: linux-pci@vger.kernel.org
    Link: https://lore.kernel.org/r/87a6euub2a.ffs@tglx

commit cfb92440ee71adcc2105b0890bb01ac3cddb8507
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 13:07:20 2022 -0800

    Linux 5.17-rc5

commit 3324e6e803156b4296975555f566892e4e3f4fcf
Merge: 222177397aabd 28df029d53a2f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 12:50:50 2022 -0800

    Merge tag 'locking_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull locking fix from Borislav Petkov:
     "Fix a NULL ptr dereference when dumping lockdep chains through
      /proc/lockdep_chains"
    
    * tag 'locking_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      lockdep: Correct lock_classes index mapping

commit 222177397aabda681ca9a16ab498bba5c597cda0
Merge: 0b0894ff78cc4 44cad52cc14ae
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 12:46:21 2022 -0800

    Merge tag 'x86_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 fixes from Borislav Petkov:
    
     - Fix the ptrace regset xfpregs_set() callback to behave according to
       the ABI
    
     - Handle poisoned pages properly in the SGX reclaimer code
    
    * tag 'x86_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing
      x86/sgx: Fix missing poison handling in reclaimer

commit 0b0894ff78cc47bc72d53ec340e4898782189868
Merge: 6e8e752f705c2 b1e8206582f9d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 12:40:20 2022 -0800

    Merge tag 'sched_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull scheduler fix from Borislav Petkov:
     "Fix task exposure order when forking tasks"
    
    * tag 'sched_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      sched: Fix yet more sched_fork() races

commit 6e8e752f705c2713005a3182c8444ef7b54f10aa
Merge: e268d7084a90c f8efca92ae509
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 12:04:14 2022 -0800

    Merge tag 'edac_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras
    
    Pull EDAC fix from Borislav Petkov:
     "Fix a long-standing struct alignment bug in the EDAC struct allocation
      code"
    
    * tag 'edac_urgent_for_v5.17_rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras:
      EDAC: Fix calculation of returned address and next offset in edac_align_ptr()

commit e268d7084a90c740198579abc069813f903120aa
Merge: 77478077349f1 10af115646171
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:51:49 2022 -0800

    Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Three fixes, all in drivers.
    
      The ufs and qedi fixes are minor; the lpfc one is a bit bigger because
      it involves adding a heuristic to detect and deal with common but not
      standards compliant behaviour"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: ufs: core: Fix divide by zero in ufshcd_map_queues()
      scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop
      scsi: qedi: Fix ABBA deadlock in qedi_process_tmf_resp() and qedi_process_cmd_cleanup_resp()

commit 77478077349f14c78e30faeac358cf1187c0f0c1
Merge: dacec3e7b9bc5 455896c53d5b8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:30:18 2022 -0800

    Merge tag 'dmaengine-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine
    
    Pull dmaengine fixes from Vinod Koul:
     "A bunch of driver fixes for:
    
       - ptdma error handling in init
    
       - lock fix in at_hdmac
    
       - error path and error num fix for sh dma
    
       - pm balance fix for stm32"
    
    * tag 'dmaengine-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine:
      dmaengine: shdma: Fix runtime PM imbalance on error
      dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size
      dmaengine: stm32-dmamux: Fix PM disable depth imbalance in stm32_dmamux_probe
      dmaengine: sh: rcar-dmac: Check for error num after setting mask
      dmaengine: at_xdmac: Fix missing unlock in at_xdmac_tasklet()
      dmaengine: ptdma: Fix the error handling path in pt_core_init()

commit dacec3e7b9bc59275b4c41319a9a52b0a1cacfa9
Merge: 961af9dbe5d0d 2428766e20156
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:23:48 2022 -0800

    Merge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux
    
    Pull i2c fixes from Wolfram Sang:
     "Some driver updates, a MAINTAINERS fix, and additions to COMPILE_TEST
      (so we won't miss build problems again)"
    
    * 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
      MAINTAINERS: remove duplicate entry for i2c-qcom-geni
      i2c: brcmstb: fix support for DSL and CM variants
      i2c: qup: allow COMPILE_TEST
      i2c: imx: allow COMPILE_TEST
      i2c: cadence: allow COMPILE_TEST
      i2c: qcom-cci: don't put a device tree node before i2c_add_adapter()
      i2c: qcom-cci: don't delete an unregistered adapter
      i2c: bcm2835: Avoid clock stretching timeouts

commit 961af9dbe5d0d0f58aac989bac17279c17a43663
Merge: 70d2bec7c545e 7b1f781f2d246
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:15:46 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
    
    Pull input fixes from Dmitry Torokhov:
    
     - a fix for Synaptics touchpads in RMI4 mode failing to suspend/resume
       properly because I2C client devices are now being suspended and
       resumed asynchronously which changed the ordering
    
     - a change to make sure we do not set right and middle buttons
       capabilities on touchpads that are "buttonpads" (i.e. do not have
       separate physical buttons)
    
     - a change to zinitix touchscreen driver adding more compatible
       strings/IDs
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
      Input: psmouse - set up dependency between PS/2 and SMBus companions
      Input: zinitix - add new compatible strings
      Input: clear BTN_RIGHT/MIDDLE on buttonpads

commit 70d2bec7c545e06057c5d963b8623e6e234901e8
Merge: 7f25f0412c9e2 f444578d727a0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:07:46 2022 -0800

    Merge tag 'for-v5.17-rc' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply
    
    Pull power supply fixes from Sebastian Reichel:
     "Three regression fixes for the 5.17 cycle:
    
       - build warning fix for power-supply documentation
    
       - pointer size fix in cw2015 battery driver
    
       - OOM handling in bq256xx charger driver"
    
    * tag 'for-v5.17-rc' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply:
      power: supply: bq256xx: Handle OOM correctly
      power: supply: core: fix application of sizeof to pointer
      power: supply: fix table problem in sysfs-class-power

commit 7f25f0412c9e2be6811e8aedbd10ef795fff85f2
Merge: c1034d249d145 538f4f022a461
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 11:01:47 2022 -0800

    Merge tag 'fs.mount_setattr.v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux
    
    Pull mount_setattr test/doc fixes from Christian Brauner:
     "This contains a fix for one of the selftests for the mount_setattr
      syscall to create idmapped mounts, an entry for idmapped mounts for
      maintainers, and missing kernel documentation for the helper we split
      out some time ago to get and yield write access to a mount when
      changing mount properties"
    
    * tag 'fs.mount_setattr.v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux:
      fs: add kernel doc for mnt_{hold,unhold}_writers()
      MAINTAINERS: add entry for idmapped mounts
      tests: fix idmapped mount_setattr test

commit c1034d249d1453b0f4c11582515a418a5d45b570
Merge: 2d3409ebc87f4 ddc204b517e60
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 10:55:05 2022 -0800

    Merge tag 'pidfd.v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux
    
    Pull pidfd fix from Christian Brauner:
     "This fixes a problem reported by lockdep when installing a pidfd via
      fd_install() with siglock and the tasklisk write lock held in
      copy_process() when calling clone()/clone3() with CLONE_PIDFD.
    
      Originally a pidfd was created prior to holding any of these locks but
      this required a call to ksys_close(). So quite some time ago in
      6fd2fe494b17 ("copy_process(): don't use ksys_close() on cleanups") we
      switched to a get_unused_fd_flags() + fd_install() model.
    
      As part of that we moved fd_install() as late as possible. This was
      done for two main reasons. First, because we needed to ensure that we
      call fd_install() past the point of no return as once that's called
      the fd is live in the task's file table. Second, because we tried to
      ensure that the fd is visible in /proc/<pid>/fd/<pidfd> right when the
      task is visible.
    
      This fix moves the fd_install() to an even later point which means
      that a task will be visible in proc while the pidfd isn't yet under
      /proc/<pid>/fd/<pidfd>.
    
      While this is a user visible change it's very unlikely that this will
      have any impact. Nobody should be relying on that and if they do we
      need to come up with something better but again, it's doubtful this is
      relevant"
    
    * tag 'pidfd.v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux:
      copy_process(): Move fd_install() out of sighand->siglock critical section

commit 2d3409ebc87f4bc4ed23bd39e78db9ffc29eec44
Merge: 4f12b742eb2b3 0cbae9e24fa7d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 20 10:44:11 2022 -0800

    Merge branch 'ucount-rlimit-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
    
    Pull ucounts fixes from Eric Biederman:
     "Michal Koutný recently found some bugs in the enforcement of
      RLIMIT_NPROC in the recent ucount rlimit implementation.
    
      In this set of patches I have developed a very conservative approach
      changing only what is necessary to fix the bugs that I can see
      clearly. Cleanups and anything that is making the code more consistent
      can follow after we have the code working as it has historically.
    
      The problem is not so much inconsistencies (although those exist) but
      that it is very difficult to figure out what the code should be doing
      in the case of RLIMIT_NPROC.
    
      All other rlimits are only enforced where the resource is acquired
      (allocated). RLIMIT_NPROC by necessity needs to be enforced in an
      additional location, and our current implementation stumbled it's way
      into that implementation"
    
    * 'ucount-rlimit-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace:
      ucounts: Handle wrapping in is_ucounts_overlimit
      ucounts: Move RLIMIT_NPROC handling after set_user
      ucounts: Base set_cred_ucounts changes on the real user
      ucounts: Enforce RLIMIT_NPROC not RLIMIT_NPROC+1
      rlimit: Fix RLIMIT_NPROC enforcement failure caused by capability calls in set_user

commit 5a3449734bcbaac7a2cc25a4773a89913ef10e66
Merge: 8940e6b669ca1 1278d17a1fb86
Author: David S. Miller <davem@davemloft.net>
Date:   Sun Feb 20 13:47:15 2022 +0000

    Merge branch 'bnxt_en-fixes'
    
    Michael Chan says:
    
    ====================
    bnxt_en: Bug fixes
    
    This series contains bug fixes for FEC reporting, ethtool self test,
    multicast setup, devlink health reporting and live patching, and
    a firmware response timeout.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1278d17a1fb860e7eab4bc3ff4b026a87cbf5105
Author: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Date:   Sun Feb 20 04:05:53 2022 -0500

    bnxt_en: Fix devlink fw_activate
    
    To install a livepatch, first flash the package to NVM, and then
    activate the patch through the "HWRM_FW_LIVEPATCH" fw command.
    To uninstall a patch from NVM, flash the removal package and then
    activate it through the "HWRM_FW_LIVEPATCH" fw command.
    
    The "HWRM_FW_LIVEPATCH" fw command has to consider following scenarios:
    
    1. no patch in NVM and no patch active. Do nothing.
    2. patch in NVM, but not active. Activate the patch currently in NVM.
    3. patch is not in NVM, but active. Deactivate the patch.
    4. patch in NVM and the patch active. Do nothing.
    
    Fix the code to handle these scenarios during devlink "fw_activate".
    
    To install and activate a live patch:
    devlink dev flash pci/0000:c1:00.0 file thor_patch.pkg
    devlink -f dev reload pci/0000:c1:00.0 action fw_activate limit no_reset
    
    To remove and deactivate a live patch:
    devlink dev flash pci/0000:c1:00.0 file thor_patch_rem.pkg
    devlink -f dev reload pci/0000:c1:00.0 action fw_activate limit no_reset
    
    Fixes: 3c4153394e2c ("bnxt_en: implement firmware live patching")
    Reviewed-by: Vikas Gupta <vikas.gupta@broadcom.com>
    Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
    Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b891106da52b2c12dbaf73400f6d225b06a38d80
Author: Michael Chan <michael.chan@broadcom.com>
Date:   Sun Feb 20 04:05:52 2022 -0500

    bnxt_en: Increase firmware message response DMA wait time
    
    When polling for the firmware message response, we first poll for the
    response message header.  Once the valid length is detected in the
    header, we poll for the valid bit at the end of the message which
    signals DMA completion.  Normally, this poll time for DMA completion
    is extremely short (0 to a few usec).  But on some devices under some
    rare conditions, it can be up to about 20 msec.
    
    Increase this delay to 50 msec and use udelay() for the first 10 usec
    for the common case, and usleep_range() beyond that.
    
    Also, change the error message to include the above delay time when
    printing the timeout value.
    
    Fixes: 3c8c20db769c ("bnxt_en: move HWRM API implementation into separate file")
    Reviewed-by: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0e0e3c5358470cbad10bd7ca29f84a44d179d286
Author: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Date:   Sun Feb 20 04:05:51 2022 -0500

    bnxt_en: Restore the resets_reliable flag in bnxt_open()
    
    During ifdown, we call bnxt_inv_fw_health_reg() which will clear
    both the status_reliable and resets_reliable flags if these
    registers are mapped.  This is correct because a FW reset during
    ifdown will clear these register mappings.  If we detect that FW
    has gone through reset during the next ifup, we will remap these
    registers.
    
    But during normal ifup with no FW reset, we need to restore the
    resets_reliable flag otherwise we will not show the reset counter
    during devlink diagnose.
    
    Fixes: 8cc95ceb7087 ("bnxt_en: improve fw diagnose devlink health messages")
    Reviewed-by: Vikas Gupta <vikas.gupta@broadcom.com>
    Reviewed-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
    Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
    Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8cdb15924252e27af16c4a8fe0fc606ce5fd04dc
Author: Pavan Chebbi <pavan.chebbi@broadcom.com>
Date:   Sun Feb 20 04:05:50 2022 -0500

    bnxt_en: Fix incorrect multicast rx mask setting when not requested
    
    We should setup multicast only when net_device flags explicitly
    has IFF_MULTICAST set. Otherwise we will incorrectly turn it on
    even when not asked.  Fix it by only passing the multicast table
    to the firmware if IFF_MULTICAST is set.
    
    Fixes: 7d2837dd7a32 ("bnxt_en: Setup multicast properly after resetting device.")
    Signed-off-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit cfcab3b3b61584a02bb523ffa99564eafa761dfe
Author: Michael Chan <michael.chan@broadcom.com>
Date:   Sun Feb 20 04:05:49 2022 -0500

    bnxt_en: Fix occasional ethtool -t loopback test failures
    
    In the current code, we setup the port to PHY or MAC loopback mode
    and then transmit a test broadcast packet for the loopback test.  This
    scheme fails sometime if the port is shared with management firmware
    that can also send packets.  The driver may receive the management
    firmware's packet and the test will fail when the contents don't
    match the test packet.
    
    Change the test packet to use it's own MAC address as the destination
    and setup the port to only receive it's own MAC address.  This should
    filter out other packets sent by management firmware.
    
    Fixes: 91725d89b97a ("bnxt_en: Add PHY loopback to ethtool self-test.")
    Reviewed-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
    Reviewed-by: Edwin Peer <edwin.peer@broadcom.com>
    Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6758f937669dba14c6aac7ca004edda42ec1b18d
Author: Michael Chan <michael.chan@broadcom.com>
Date:   Sun Feb 20 04:05:48 2022 -0500

    bnxt_en: Fix offline ethtool selftest with RDMA enabled
    
    For offline (destructive) self tests, we need to stop the RDMA driver
    first.  Otherwise, the RDMA driver will run into unrecoverable errors
    when destructive firmware tests are being performed.
    
    The irq_re_init parameter used in the half close and half open
    sequence when preparing the NIC for offline tests should be set to
    true because the RDMA driver will free all IRQs before the offline
    tests begin.
    
    Fixes: 55fd0cf320c3 ("bnxt_en: Add external loopback test to ethtool selftest.")
    Reviewed-by: Edwin Peer <edwin.peer@broadcom.com>
    Reviewed-by: Ben Li <ben.li@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 84d3c83e6ea7d46cf3de3a54578af73eb24a64f2
Author: Somnath Kotur <somnath.kotur@broadcom.com>
Date:   Sun Feb 20 04:05:47 2022 -0500

    bnxt_en: Fix active FEC reporting to ethtool
    
    ethtool --show-fec <interface> does not show anything when the Active
    FEC setting in the chip is set to None.  Fix it to properly return
    ETHTOOL_FEC_OFF in that case.
    
    Fixes: 8b2775890ad8 ("bnxt_en: Report FEC settings to ethtool.")
    Signed-off-by: Somnath Kotur <somnath.kotur@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c94afc46cae7ad41b2ad6a99368147879f4b0e56
Author: Miaohe Lin <linmiaohe@huawei.com>
Date:   Thu Feb 17 22:53:27 2022 +0800

    memblock: use kfree() to release kmalloced memblock regions
    
    memblock.{reserved,memory}.regions may be allocated using kmalloc() in
    memblock_double_array(). Use kfree() to release these kmalloced regions
    indicated by memblock_{reserved,memory}_in_slab.
    
    Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
    Fixes: 3010f876500f ("mm: discard memblock data later")
    Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>

commit e23e40fd6de5c1c94793bc4147e8f34387d58576
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sat Feb 5 01:58:04 2022 +0100

    hwmon: (ntc_thermistor) Underscore Samsung thermistor
    
    The sysfs does not like that we name the thermistor something
    that contains a dash:
    
    ntc-thermistor thermistor: hwmon: 'ssg1404-001221' is not a valid
    name attribute, please fix
    
    Fix it up by switching to an underscore.
    
    Fixes: e13e979b2b3d ("hwmon: (ntc_thermistor) Add Samsung 1404-001221 NTC")
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/20220205005804.123245-1-linus.walleij@linaro.org
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit b1a5983f56e371046dcf164f90bfaf704d2b89f6
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Thu Feb 17 23:41:20 2022 +0100

    netfilter: nf_tables_offload: incorrect flow offload action array size
    
    immediate verdict expression needs to allocate one slot in the flow offload
    action array, however, immediate data expression does not need to do so.
    
    fwd and dup expression need to allocate one slot, this is missing.
    
    Add a new offload_action interface to report if this expression needs to
    allocate one slot in the flow offload action array.
    
    Fixes: be2861dc36d7 ("netfilter: nft_{fwd,dup}_netdev: add offload support")
    Reported-and-tested-by: Nick Gregory <Nick.Gregory@Sophos.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 8940e6b669ca1196ce0a0549c819078096390f76
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Fri Feb 18 14:13:02 2022 +0200

    net: dsa: avoid call to __dev_set_promiscuity() while rtnl_mutex isn't held
    
    If the DSA master doesn't support IFF_UNICAST_FLT, then the following
    call path is possible:
    
    dsa_slave_switchdev_event_work
    -> dsa_port_host_fdb_add
       -> dev_uc_add
          -> __dev_set_rx_mode
             -> __dev_set_promiscuity
    
    Since the blamed commit, dsa_slave_switchdev_event_work() no longer
    holds rtnl_lock(), which triggers the ASSERT_RTNL() from
    __dev_set_promiscuity().
    
    Taking rtnl_lock() around dev_uc_add() is impossible, because all the
    code paths that call dsa_flush_workqueue() do so from contexts where the
    rtnl_mutex is already held - so this would lead to an instant deadlock.
    
    dev_uc_add() in itself doesn't require the rtnl_mutex for protection.
    There is this comment in __dev_set_rx_mode() which assumes so:
    
                    /* Unicast addresses changes may only happen under the rtnl,
                     * therefore calling __dev_set_promiscuity here is safe.
                     */
    
    but it is from commit 4417da668c00 ("[NET]: dev: secondary unicast
    address support") dated June 2007, and in the meantime, commit
    f1f28aa3510d ("netdev: Add addr_list_lock to struct net_device."), dated
    July 2008, has added &dev->addr_list_lock to protect this instead of the
    global rtnl_mutex.
    
    Nonetheless, __dev_set_promiscuity() does assume rtnl_mutex protection,
    but it is the uncommon path of what we typically expect dev_uc_add()
    to do. So since only the uncommon path requires rtnl_lock(), just check
    ahead of time whether dev_uc_add() would result into a call to
    __dev_set_promiscuity(), and handle that condition separately.
    
    DSA already configures the master interface to be promiscuous if the
    tagger requires this. We can extend this to also cover the case where
    the master doesn't handle dev_uc_add() (doesn't support IFF_UNICAST_FLT),
    and on the premise that we'd end up making it promiscuous during
    operation anyway, either if a DSA slave has a non-inherited MAC address,
    or if the bridge notifies local FDB entries for its own MAC address, the
    address of a station learned on a foreign port, etc.
    
    Fixes: 0faf890fc519 ("net: dsa: drop rtnl_lock from dsa_slave_switchdev_event_work")
    Reported-by: Oleksij Rempel <o.rempel@pengutronix.de>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3d00827a90db6f79abc7cdc553887f89a2e0a184
Author: Svenning Sørensen <sss@secomea.com>
Date:   Fri Feb 18 11:27:01 2022 +0000

    net: dsa: microchip: fix bridging with more than two member ports
    
    Commit b3612ccdf284 ("net: dsa: microchip: implement multi-bridge support")
    plugged a packet leak between ports that were members of different bridges.
    Unfortunately, this broke another use case, namely that of more than two
    ports that are members of the same bridge.
    
    After that commit, when a port is added to a bridge, hardware bridging
    between other member ports of that bridge will be cleared, preventing
    packet exchange between them.
    
    Fix by ensuring that the Port VLAN Membership bitmap includes any existing
    ports in the bridge, not just the port being added.
    
    Fixes: b3612ccdf284 ("net: dsa: microchip: implement multi-bridge support")
    Signed-off-by: Svenning Sørensen <sss@secomea.com>
    Tested-by: Oleksij Rempel <o.rempel@pengutronix.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5486f5bf790b5c664913076c3194b8f916a5c7ad
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Thu Feb 17 14:35:49 2022 +0100

    net: Force inlining of checksum functions in net/checksum.h
    
    All functions defined as static inline in net/checksum.h are
    meant to be inlined for performance reason.
    
    But since commit ac7c3e4ff401 ("compiler: enable
    CONFIG_OPTIMIZE_INLINING forcibly") the compiler is allowed to
    uninline functions when it wants.
    
    Fair enough in the general case, but for tiny performance critical
    checksum helpers that's counter-productive.
    
    The problem mainly arises when selecting CONFIG_CC_OPTIMISE_FOR_SIZE,
    Those helpers being 'static inline' in header files you suddenly find
    them duplicated many times in the resulting vmlinux.
    
    Here is a typical exemple when building powerpc pmac32_defconfig
    with CONFIG_CC_OPTIMISE_FOR_SIZE. csum_sub() appears 4 times:
    
            c04a23cc <csum_sub>:
            c04a23cc:       7c 84 20 f8     not     r4,r4
            c04a23d0:       7c 63 20 14     addc    r3,r3,r4
            c04a23d4:       7c 63 01 94     addze   r3,r3
            c04a23d8:       4e 80 00 20     blr
                    ...
            c04a2ce8:       4b ff f6 e5     bl      c04a23cc <csum_sub>
                    ...
            c04a2d2c:       4b ff f6 a1     bl      c04a23cc <csum_sub>
                    ...
            c04a2d54:       4b ff f6 79     bl      c04a23cc <csum_sub>
                    ...
            c04a754c <csum_sub>:
            c04a754c:       7c 84 20 f8     not     r4,r4
            c04a7550:       7c 63 20 14     addc    r3,r3,r4
            c04a7554:       7c 63 01 94     addze   r3,r3
            c04a7558:       4e 80 00 20     blr
                    ...
            c04ac930:       4b ff ac 1d     bl      c04a754c <csum_sub>
                    ...
            c04ad264:       4b ff a2 e9     bl      c04a754c <csum_sub>
                    ...
            c04e3b08 <csum_sub>:
            c04e3b08:       7c 84 20 f8     not     r4,r4
            c04e3b0c:       7c 63 20 14     addc    r3,r3,r4
            c04e3b10:       7c 63 01 94     addze   r3,r3
            c04e3b14:       4e 80 00 20     blr
                    ...
            c04e5788:       4b ff e3 81     bl      c04e3b08 <csum_sub>
                    ...
            c04e65c8:       4b ff d5 41     bl      c04e3b08 <csum_sub>
                    ...
            c0512d34 <csum_sub>:
            c0512d34:       7c 84 20 f8     not     r4,r4
            c0512d38:       7c 63 20 14     addc    r3,r3,r4
            c0512d3c:       7c 63 01 94     addze   r3,r3
            c0512d40:       4e 80 00 20     blr
                    ...
            c0512dfc:       4b ff ff 39     bl      c0512d34 <csum_sub>
                    ...
            c05138bc:       4b ff f4 79     bl      c0512d34 <csum_sub>
                    ...
    
    Restore the expected behaviour by using __always_inline for all
    functions defined in net/checksum.h
    
    vmlinux size is even reduced by 256 bytes with this patch:
    
               text    data     bss     dec     hex filename
            6980022 2515362  194384 9689768  93daa8 vmlinux.before
            6979862 2515266  194384 9689512  93d9a8 vmlinux.now
    
    Fixes: ac7c3e4ff401 ("compiler: enable CONFIG_OPTIMIZE_INLINING forcibly")
    Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0033fced48d281d59f35565106e6d78b25a2f6e6
Merge: 90141edcd53d1 5950bdc88dd1d
Author: David S. Miller <davem@davemloft.net>
Date:   Sat Feb 19 12:35:20 2022 +0000

    Merge branch '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-02-18
    
    This series contains updates to ice driver only.
    
    Wojciech fixes protocol matching for slow-path switchdev so that all
    packets are correctly redirected.
    
    Michal removes accidental unconditional setting of l4 port filtering
    flag.
    
    Jake adds locking to protect VF reset and removal to fix various issues
    that can be encountered when they race with each other.
    
    Tom Rix propagates an error and initializes a struct to resolve reported
    Clang issues.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 90141edcd53d145e870bca24d0ce0daaa7157e02
Merge: 3a14d0888eb4b e35f885b357d4
Author: David S. Miller <davem@davemloft.net>
Date:   Sat Feb 19 12:28:01 2022 +0000

    Merge branch 'mptcp-fixes'
    
    Mat Martineau says:
    
    ====================
    mptcp: Fix address advertisement races and stabilize tests
    
    Patches 1, 2, and 7 modify two self tests to give consistent, accurate
    results by fixing timing issues and accounting for syncookie behavior.
    
    Paches 3-6 fix two races in overlapping address advertisement send and
    receive. Associated self tests are updated, including addition of two
    MIBs to enable testing and tracking dropped address events.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e35f885b357d47e04380a2056d1b2cc3e6f4f24b
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:44 2022 -0800

    selftests: mptcp: be more conservative with cookie MPJ limits
    
    Since commit 2843ff6f36db ("mptcp: remote addresses fullmesh"), an
    MPTCP client can attempt creating multiple MPJ subflow simultaneusly.
    
    In such scenario the server, when syncookies are enabled, could end-up
    accepting incoming MPJ syn even above the configured subflow limit, as
    the such limit can be enforced in a reliable way only after the subflow
    creation. In case of syncookie, only after the 3rd ack reception.
    
    As a consequence the related self-tests case sporadically fails, as it
    verify that the server always accept the expected number of MPJ syn.
    
    Address the issues relaxing the MPJ syn number constrain. Note that the
    check on the accepted number of MPJ 3rd ack still remains intact.
    
    Fixes: 2843ff6f36db ("mptcp: remote addresses fullmesh")
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6ef84b1517e08f6c2fc105b798a9d21bf4caa6cb
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:43 2022 -0800

    selftests: mptcp: more robust signal race test
    
    The in kernel MPTCP PM implementation can process a single
    incoming add address option at any given time. In the
    mentioned test the server can surpass such limit. Let the
    setup cope with that allowing a faster add_addr retransmission.
    
    Fixes: a88c9e496937 ("mptcp: do not block subflows creation on errors")
    Fixes: f7efc7771eac ("mptcp: drop argument port from mptcp_pm_announce_addr")
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/254
    Reported-and-tested-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f73c1194634506ab60af0debef04671fc431a435
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:42 2022 -0800

    mptcp: add mibs counter for ignored incoming options
    
    The MPTCP in kernel path manager has some constraints on incoming
    addresses announce processing, so that in edge scenarios it can
    end-up dropping (ignoring) some of such announces.
    
    The above is not very limiting in practice since such scenarios are
    very uncommon and MPTCP will recover due to ADD_ADDR retransmissions.
    
    This patch adds a few MIB counters to account for such drop events
    to allow easier introspection of the critical scenarios.
    
    Fixes: f7efc7771eac ("mptcp: drop argument port from mptcp_pm_announce_addr")
    Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 837cf45df163a3780bc04b555700231e95b31dc9
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:41 2022 -0800

    mptcp: fix race in incoming ADD_ADDR option processing
    
    If an MPTCP endpoint received multiple consecutive incoming
    ADD_ADDR options, mptcp_pm_add_addr_received() can overwrite
    the current remote address value after the PM lock is released
    in mptcp_pm_nl_add_addr_received() and before such address
    is echoed.
    
    Fix the issue caching the remote address value a little earlier
    and always using the cached value after releasing the PM lock.
    
    Fixes: f7efc7771eac ("mptcp: drop argument port from mptcp_pm_announce_addr")
    Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 98247bc16a27cf8ead4c47ce9f15888be85841fc
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:40 2022 -0800

    mptcp: fix race in overlapping signal events
    
    After commit a88c9e496937 ("mptcp: do not block subflows
    creation on errors"), if a signal address races with a failing
    subflow creation, the subflow creation failure control path
    can trigger the selection of the next address to be announced
    while the current announced is still pending.
    
    The above will cause the unintended suppression of the ADD_ADDR
    announce.
    
    Fix the issue skipping the to-be-suppressed announce before it
    will mark an endpoint as already used. The relevant announce
    will be triggered again when the current one will complete.
    
    Fixes: a88c9e496937 ("mptcp: do not block subflows creation on errors")
    Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5b31dda736e31c58d1941c7349569c7452eafb6b
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:39 2022 -0800

    selftests: mptcp: improve 'fair usage on close' stability
    
    The mentioned test has to wait for a subflow creation failure.
    The current code looks for TCP sockets in TW state and sometimes
    misses the relevant event. Switch to a more stable check, looking
    for the associated mib counter.
    
    Fixes: 46e967d187ed ("selftests: mptcp: add tests for subflow creation failure")
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/257
    Reported-and-tested-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0cd33c5ffec12bd77a1c02db2469fac08f840939
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Feb 18 13:35:38 2022 -0800

    selftests: mptcp: fix diag instability
    
    Instead of waiting for an arbitrary amount of time for the MPTCP
    MP_CAPABLE handshake to complete, explicitly wait for the relevant
    socket to enter into the established status.
    
    Additionally let the data transfer application use the slowest
    transfer mode available (-r), to cope with very slow host, or
    high jitter caused by hosting VMs.
    
    Fixes: df62f2ec3df6 ("selftests/mptcp: add diag interface tests")
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/258
    Reported-and-tested-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2428766e201565a5fa964d7461d9f6608eb04d7d
Author: Wolfram Sang <wsa@kernel.org>
Date:   Fri Feb 18 11:49:04 2022 +0100

    MAINTAINERS: remove duplicate entry for i2c-qcom-geni
    
    The driver is already covered in the ARM/QUALCOMM section. Also, Akash
    Asthana's email bounces meanwhile and Mukesh Savaliya has never
    responded to mails regarding this driver.
    
    Signed-off-by: Wolfram Sang <wsa@kernel.org>
    Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit b1e8206582f9d680cff7d04828708c8b6ab32957
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Mon Feb 14 10:16:57 2022 +0100

    sched: Fix yet more sched_fork() races
    
    Where commit 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an
    invalid sched_task_group") fixed a fork race vs cgroup, it opened up a
    race vs syscalls by not placing the task on the runqueue before it
    gets exposed through the pidhash.
    
    Commit 13765de8148f ("sched/fair: Fix fault in reweight_entity") is
    trying to fix a single instance of this, instead fix the whole class
    of issues, effectively reverting this commit.
    
    Fixes: 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an invalid sched_task_group")
    Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Tadeusz Struk <tadeusz.struk@linaro.org>
    Tested-by: Zhang Qiao <zhangqiao22@huawei.com>
    Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Link: https://lkml.kernel.org/r/YgoeCbwj5mbCR0qA@hirez.programming.kicks-ass.net

commit 3a14d0888eb4b0045884126acc69abfb7b87814d
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Fri Feb 18 14:15:35 2022 +0100

    nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()
    
    ida_simple_get() returns an id between min (0) and max (NFP_MAX_MAC_INDEX)
    inclusive.
    So NFP_MAX_MAC_INDEX (0xff) is a valid id.
    
    In order for the error handling path to work correctly, the 'invalid'
    value for 'ida_idx' should not be in the 0..NFP_MAX_MAC_INDEX range,
    inclusive.
    
    So set it to -1.
    
    Fixes: 20cce8865098 ("nfp: flower: enable MAC address sharing for offloadable devs")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Simon Horman <simon.horman@corigine.com>
    Link: https://lore.kernel.org/r/20220218131535.100258-1-simon.horman@corigine.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ba88b5533728c54bdea68431988eff2d9a7a1237
Author: Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>
Date:   Fri Feb 18 01:50:18 2022 -0700

    MAINTAINERS: rmnet: Update email addresses
    
    Switch to the quicinc.com ids.
    
    Signed-off-by: Sean Tranchetti <quic_stranche@quicinc.com>
    Signed-off-by: Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>
    Link: https://lore.kernel.org/r/1645174218-32632-1-git-send-email-quic_subashab@quicinc.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5a2aba71cd2610d3ed08867a1b1bf617cd8f89b8
Author: Jeremy Linton <jeremy.linton@arm.com>
Date:   Mon Feb 14 17:18:52 2022 -0600

    net: mvpp2: always set port pcs ops
    
    Booting a MACCHIATObin with 5.17, the system OOPs with
    a null pointer deref when the network is started. This
    is caused by the pcs->ops structure being null in
    mcpp2_acpi_start() when it tries to call pcs_config().
    
    Hoisting the code which sets pcs_gmac.ops and pcs_xlg.ops,
    assuring they are always set, fixes the problem.
    
    The OOPs looks like:
    [   18.687760] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000010
    [   18.698561] Mem abort info:
    [   18.698564]   ESR = 0x96000004
    [   18.698567]   EC = 0x25: DABT (current EL), IL = 32 bits
    [   18.709821]   SET = 0, FnV = 0
    [   18.714292]   EA = 0, S1PTW = 0
    [   18.718833]   FSC = 0x04: level 0 translation fault
    [   18.725126] Data abort info:
    [   18.729408]   ISV = 0, ISS = 0x00000004
    [   18.734655]   CM = 0, WnR = 0
    [   18.738933] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000111bbf000
    [   18.745409] [0000000000000010] pgd=0000000000000000, p4d=0000000000000000
    [   18.752235] Internal error: Oops: 96000004 [#1] SMP
    [   18.757134] Modules linked in: rfkill ip_set nf_tables nfnetlink qrtr sunrpc vfat fat omap_rng fuse zram xfs crct10dif_ce mvpp2 ghash_ce sbsa_gwdt phylink xhci_plat_hcd ahci_plam
    [   18.773481] CPU: 0 PID: 681 Comm: NetworkManager Not tainted 5.17.0-0.rc3.89.fc36.aarch64 #1
    [   18.781954] Hardware name: Marvell                         Armada 7k/8k Family Board      /Armada 7k/8k Family Board      , BIOS EDK II Jun  4 2019
    [   18.795222] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [   18.802213] pc : mvpp2_start_dev+0x2b0/0x300 [mvpp2]
    [   18.807208] lr : mvpp2_start_dev+0x298/0x300 [mvpp2]
    [   18.812197] sp : ffff80000b4732c0
    [   18.815522] x29: ffff80000b4732c0 x28: 0000000000000000 x27: ffffccab38ae57f8
    [   18.822689] x26: ffff6eeb03065a10 x25: ffff80000b473a30 x24: ffff80000b4735b8
    [   18.829855] x23: 0000000000000000 x22: 00000000000001e0 x21: ffff6eeb07b6ab68
    [   18.837021] x20: ffff6eeb07b6ab30 x19: ffff6eeb07b6a9c0 x18: 0000000000000014
    [   18.844187] x17: 00000000f6232bfe x16: ffffccab899b1dc0 x15: 000000006a30f9fa
    [   18.851353] x14: 000000003b77bd50 x13: 000006dc896f0e8e x12: 001bbbfccfd0d3a2
    [   18.858519] x11: 0000000000001528 x10: 0000000000001548 x9 : ffffccab38ad0fb0
    [   18.865685] x8 : ffff80000b473330 x7 : 0000000000000000 x6 : 0000000000000000
    [   18.872851] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff80000b4732f8
    [   18.880017] x2 : 000000000000001a x1 : 0000000000000002 x0 : ffff6eeb07b6ab68
    [   18.887183] Call trace:
    [   18.889637]  mvpp2_start_dev+0x2b0/0x300 [mvpp2]
    [   18.894279]  mvpp2_open+0x134/0x2b4 [mvpp2]
    [   18.898483]  __dev_open+0x128/0x1e4
    [   18.901988]  __dev_change_flags+0x17c/0x1d0
    [   18.906187]  dev_change_flags+0x30/0x70
    [   18.910038]  do_setlink+0x278/0xa7c
    [   18.913540]  __rtnl_newlink+0x44c/0x7d0
    [   18.917391]  rtnl_newlink+0x5c/0x8c
    [   18.920892]  rtnetlink_rcv_msg+0x254/0x314
    [   18.925006]  netlink_rcv_skb+0x48/0x10c
    [   18.928858]  rtnetlink_rcv+0x24/0x30
    [   18.932449]  netlink_unicast+0x290/0x2f4
    [   18.936386]  netlink_sendmsg+0x1d0/0x41c
    [   18.940323]  sock_sendmsg+0x60/0x70
    [   18.943825]  ____sys_sendmsg+0x248/0x260
    [   18.947762]  ___sys_sendmsg+0x74/0xa0
    [   18.951438]  __sys_sendmsg+0x64/0xcc
    [   18.955027]  __arm64_sys_sendmsg+0x30/0x40
    [   18.959140]  invoke_syscall+0x50/0x120
    [   18.962906]  el0_svc_common.constprop.0+0x4c/0xf4
    [   18.967629]  do_el0_svc+0x30/0x9c
    [   18.970958]  el0_svc+0x28/0xb0
    [   18.974025]  el0t_64_sync_handler+0x10c/0x140
    [   18.978400]  el0t_64_sync+0x1a4/0x1a8
    [   18.982078] Code: 52800004 b9416262 aa1503e0 52800041 (f94008a5)
    [   18.988196] ---[ end trace 0000000000000000 ]---
    
    Fixes: cff056322372 ("net: mvpp2: use .mac_select_pcs() interface")
    Suggested-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
    Reviewed-by: Marcin Wojtas <mw@semihalf.com>
    Link: https://lore.kernel.org/r/20220214231852.3331430-1-jeremy.linton@arm.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 486c2d15aa812d669bb27f8241aa5d5dafbac5b9
Merge: d1e972ace4239 6f66db29e2415
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sat Feb 19 02:03:58 2022 +0100

    Merge tag 'intel-pinctrl-v5.17-5' of gitolite.kernel.org:pub/scm/linux/kernel/git/pinctrl/intel into fixes
    
    intel-pinctrl for v5.17-5
    
    * Revert misplaced ID
    
    The following is an automated git shortlog grouped by driver:
    
    tigerlake:
     -  Revert "Add Alder Lake-M ACPI ID"

commit d1e972ace42390de739cde87d96043dcbe502286
Author: Marc Zyngier <maz@kernel.org>
Date:   Fri Feb 11 09:39:04 2022 +0000

    gpio: tegra186: Fix chip_data type confusion
    
    The tegra186 GPIO driver makes the assumption that the pointer
    returned by irq_data_get_irq_chip_data() is a pointer to a
    tegra_gpio structure. Unfortunately, it is actually a pointer
    to the inner gpio_chip structure, as mandated by the gpiolib
    infrastructure. Nice try.
    
    The saving grace is that the gpio_chip is the first member of
    tegra_gpio, so the bug has gone undetected since... forever.
    
    Fix it by performing a container_of() on the pointer. This results
    in no additional code, and makes it possible to understand how
    the whole thing works.
    
    Fixes: 5b2b135a87fc ("gpio: Add Tegra186 support")
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Cc: Thierry Reding <treding@nvidia.com>
    Cc: Linus Walleij <linus.walleij@linaro.org>
    Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
    Link: https://lore.kernel.org/r/20220211093904.1112679-1-maz@kernel.org
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 64fd52a4d3ce63a327948cefc8e4e5c7ef35e813
Author: Marc Zyngier <maz@kernel.org>
Date:   Fri Feb 11 09:23:45 2022 +0000

    pinctrl: starfive: Use a static name for the GPIO irq_chip
    
    Drop the device name used for the GPIO irq_chip and replace it
    with something static. The information is still available from
    debugfs and carried as part of the irqdomain.
    
    Suggested-by: Emil Renner Berthing <kernel@esmil.dk>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Cc: Linus Walleij <linus.walleij@linaro.org>
    Cc: Bartosz Golaszewski <brgl@bgdev.pl>
    Link: https://lore.kernel.org/r/20220211092345.1093332-1-maz@kernel.org
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 4f12b742eb2b3a850ac8be7dc4ed52976fc6cb0b
Merge: 1c2a33d0ac696 d19e0183a8830
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 16:24:44 2022 -0800

    Merge tag 'nfs-for-5.17-3' of git://git.linux-nfs.org/projects/anna/linux-nfs
    
    Pull NFS client bugfixes from Anna Schumaker:
    
     - Fix unnecessary changeattr revalidations
    
     - Fix resolving symlinks during directory lookups
    
     - Don't report writeback errors in nfs_getattr()
    
    * tag 'nfs-for-5.17-3' of git://git.linux-nfs.org/projects/anna/linux-nfs:
      NFS: Do not report writeback errors in nfs_getattr()
      NFS: LOOKUP_DIRECTORY is also ok with symlinks
      NFS: Remove an incorrect revalidation in nfs4_update_changeattr_locked()

commit 1c2a33d0ac6961d36cd653638c7841b179969906
Merge: 241c32d853a84 8292656464e5f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 16:19:14 2022 -0800

    Merge tag 'acpi-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull ACPI fixes from Rafael Wysocki:
     "These make an excess warning message go away and fix a recently
      introduced boot failure on a vintage machine.
    
      Specifics:
    
       - Change the log level of the "table not found" message in
         acpi_table_parse_entries_array() to debug to prevent it from
         showing up in the logs unnecessarily (Dan Williams)
    
       - Add a C-state limit quirk for 32-bit ThinkPad T40 to prevent it
         from crashing on boot after recent changes in the ACPI processor
         driver (Woody Suwalski)"
    
    * tag 'acpi-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
      ACPI: tables: Quiet ACPI table not found warning

commit 241c32d853a84b9d775f9fd58f1ba91a0a5c9117
Merge: 7993e65fdd0fe 5feef64f4c670
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 16:14:13 2022 -0800

    Merge tag 'riscv-for-linus-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V fixes from Palmer Dabbelt:
     "A set of three fixes, all aimed at fixing some fallout from the recent
      sparse hart ID support"
    
    * tag 'riscv-for-linus-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
      RISC-V: Fix IPI/RFENCE hmask on non-monotonic hartid ordering
      RISC-V: Fix handling of empty cpu masks
      RISC-V: Fix hartid mask handling for hartid 31 and up

commit a222fd8541394b36b13c89d1698d9530afd59a9c
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Thu Dec 30 09:45:43 2021 +0800

    soc: fsl: qe: Check of ioremap return value
    
    As the possible failure of the ioremap(), the par_io could be NULL.
    Therefore it should be better to check it and return error in order to
    guarantee the success of the initiation.
    But, I also notice that all the caller like mpc85xx_qe_par_io_init() in
    `arch/powerpc/platforms/85xx/common.c` don't check the return value of
    the par_io_init().
    Actually, par_io_init() needs to check to handle the potential error.
    I will submit another patch to fix that.
    Anyway, par_io_init() itsely should be fixed.
    
    Fixes: 7aa1aa6ecec2 ("QE: Move QE from arch/powerpc to drivers/soc")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit 6385960501d9e0248a8745714674e86bd077e198
Author: Jason Wang <wangborong@cdjrlc.com>
Date:   Sat Dec 11 17:08:45 2021 +0800

    soc: fsl: qe: fix typo in a comment
    
    The double `is' in the comment in line 150 is repeated. Remove one
    of them from the comment.  Also removes a redundant tab in a new line.
    
    Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit b9abe942cda43a1d46a0fd96efb54f1aa909f757
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Wed Nov 3 21:00:33 2021 +0100

    soc: fsl: guts: Add a missing memory allocation failure check
    
    If 'devm_kstrdup()' fails, we should return -ENOMEM.
    
    While at it, move the 'of_node_put()' call in the error handling path and
    after the 'machine' has been copied.
    Better safe than sorry.
    
    Fixes: a6fc3b698130 ("soc: fsl: add GUTS driver for QorIQ platforms")
    Depends-on: fddacc7ff4dd ("soc: fsl: guts: Revert commit 3c0d64e867ed")
    Suggested-by: Tyrel Datwyler <tyreld@linux.ibm.com>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit b113737cf12964a20cc3ba1ddabe6229099661c6
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Wed Nov 3 21:00:17 2021 +0100

    soc: fsl: guts: Revert commit 3c0d64e867ed
    
    This reverts commit 3c0d64e867ed
    ("soc: fsl: guts: reuse machine name from device tree").
    
    A following patch will fix the missing memory allocation failure check
    instead.
    
    Suggested-by: Tyrel Datwyler <tyreld@linux.ibm.com>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit b80af7564446c8ab96438cac00e0575eb86154ad
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Nov 10 12:59:51 2021 +0200

    soc: fsl: Correct MAINTAINERS database (SOC)
    
    MAINTAINERS lacks of proper coverage for FSL headers. Fix it accordingly.
    
    Fixes: 1b48706f027c ("MAINTAINERS: add entry for Freescale SoC drivers")
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit f2b70418ec6f104981b54709a4cfe3a3c46b7d8f
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Nov 10 12:59:50 2021 +0200

    soc: fsl: Correct MAINTAINERS database (QUICC ENGINE LIBRARY)
    
    MAINTAINERS lacks of proper coverage for FSL headers. Fix it accordingly.
    
    Fixes: 7aa1aa6ecec2 ("QE: Move QE from arch/powerpc to drivers/soc")
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit 988f0a9045b0058a43ccee764a671dfab81e6d15
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Nov 10 12:59:52 2021 +0200

    soc: fsl: Replace kernel.h with the necessary inclusions
    
    When kernel.h is used in the headers it adds a lot into dependency hell,
    especially when there are circular dependencies are involved.
    
    Replace kernel.h inclusion with the list of what is really being used.
    
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Li Yang <leoyang.li@nxp.com>

commit 6b4266b8deb857ce2dc2a9b769b242865b9a0bce
Author: Li Yang <leoyang.li@nxp.com>
Date:   Mon Nov 8 18:10:18 2021 -0600

    dt-bindings: fsl,layerscape-dcfg: add missing compatible for lx2160a
    
    The compatible string is already in use, fix the chip list in binding to
    include it.
    
    Signed-off-by: Li Yang <leoyang.li@nxp.com>
    Acked-by: Rob Herring <robh@kernel.org>

commit efd12405f1801ef0458d908a844317fb1388c3bf
Author: Li Yang <leoyang.li@nxp.com>
Date:   Mon Nov 8 18:07:51 2021 -0600

    dt-bindings: qoriq-clock: add missing compatible for lx2160a
    
    The compatible string is already in use, fix the binding to include it.
    
    Signed-off-by: Li Yang <leoyang.li@nxp.com>
    Acked-by: Rob Herring <robh@kernel.org>

commit 7b1f781f2d2460693f43d5f764198df558e3494b
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Tue Feb 15 13:32:26 2022 -0800

    Input: psmouse - set up dependency between PS/2 and SMBus companions
    
    When we switch from emulated PS/2 to native (RMI4 or Elan) protocols, we
    create SMBus companion devices that are attached to I2C/SMBus controllers.
    However, when suspending and resuming, we also need to make sure that we
    take into account the PS/2 device they are associated with, so that PS/2
    device is suspended after the companion and resumed before it, otherwise
    companions will not work properly. Before I2C devices were marked for
    asynchronous suspend/resume, this ordering happened naturally, but now we
    need to enforce it by establishing device links, with PS/2 devices being
    suppliers and SMBus companions being consumers.
    
    Fixes: 172d931910e1 ("i2c: enable async suspend/resume on i2c client devices")
    Reported-and-tested-by: Hugh Dickins <hughd@google.com>
    Tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
    Link: https://lore.kernel.org/r/89456fcd-a113-4c82-4b10-a9bcaefac68f@google.com
    Link: https://lore.kernel.org/r/YgwQN8ynO88CPMju@google.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 5950bdc88dd1d158f2845fdff8fb1de86476806c
Author: Tom Rix <trix@redhat.com>
Date:   Mon Feb 14 07:40:43 2022 -0800

    ice: initialize local variable 'tlv'
    
    Clang static analysis reports this issues
    ice_common.c:5008:21: warning: The left expression of the compound
      assignment is an uninitialized value. The computed value will
      also be garbage
      ldo->phy_type_low |= ((u64)buf << (i * 16));
      ~~~~~~~~~~~~~~~~~ ^
    
    When called from ice_cfg_phy_fec() ldo is the uninitialized local
    variable tlv.  So initialize.
    
    Fixes: ea78ce4dab05 ("ice: add link lenient and default override support")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit ed22d9c8d128293fc7b0b086c7d3654bcb99a8dd
Author: Tom Rix <trix@redhat.com>
Date:   Mon Feb 14 06:33:27 2022 -0800

    ice: check the return of ice_ptp_gettimex64
    
    Clang static analysis reports this issue
    time64.h:69:50: warning: The left operand of '+'
      is a garbage value
      set_normalized_timespec64(&ts_delta, lhs.tv_sec + rhs.tv_sec,
                                           ~~~~~~~~~~ ^
    In ice_ptp_adjtime_nonatomic(), the timespec64 variable 'now'
    is set by ice_ptp_gettimex64().  This function can fail
    with -EBUSY, so 'now' can have a gargbage value.
    So check the return.
    
    Fixes: 06c16d89d2cb ("ice: register 1588 PTP clock device object for E810 devices")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit fadead80fe4c033b5e514fcbadd20b55c4494112
Author: Jacob Keller <jacob.e.keller@intel.com>
Date:   Mon Feb 7 10:23:29 2022 -0800

    ice: fix concurrent reset and removal of VFs
    
    Commit c503e63200c6 ("ice: Stop processing VF messages during teardown")
    introduced a driver state flag, ICE_VF_DEINIT_IN_PROGRESS, which is
    intended to prevent some issues with concurrently handling messages from
    VFs while tearing down the VFs.
    
    This change was motivated by crashes caused while tearing down and
    bringing up VFs in rapid succession.
    
    It turns out that the fix actually introduces issues with the VF driver
    caused because the PF no longer responds to any messages sent by the VF
    during its .remove routine. This results in the VF potentially removing
    its DMA memory before the PF has shut down the device queues.
    
    Additionally, the fix doesn't actually resolve concurrency issues within
    the ice driver. It is possible for a VF to initiate a reset just prior
    to the ice driver removing VFs. This can result in the remove task
    concurrently operating while the VF is being reset. This results in
    similar memory corruption and panics purportedly fixed by that commit.
    
    Fix this concurrency at its root by protecting both the reset and
    removal flows using the existing VF cfg_lock. This ensures that we
    cannot remove the VF while any outstanding critical tasks such as a
    virtchnl message or a reset are occurring.
    
    This locking change also fixes the root cause originally fixed by commit
    c503e63200c6 ("ice: Stop processing VF messages during teardown"), so we
    can simply revert it.
    
    Note that I kept these two changes together because simply reverting the
    original commit alone would leave the driver vulnerable to worse race
    conditions.
    
    Fixes: c503e63200c6 ("ice: Stop processing VF messages during teardown")
    Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 932645c298c41aad64ef13016ff4c2034eef5aed
Author: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Date:   Mon Jan 3 07:41:21 2022 +0100

    ice: fix setting l4 port flag when adding filter
    
    Accidentally filter flag for none encapsulated l4 port field is always
    set. Even if user wants to add encapsulated l4 port field.
    
    Remove this unnecessary flag setting.
    
    Fixes: 9e300987d4a81 ("ice: VXLAN and Geneve TC support")
    Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit b70bc066d77b460a63a8c3fb2ea0d811ce862a83
Author: Wojciech Drewek <wojciech.drewek@intel.com>
Date:   Fri Dec 17 12:36:25 2021 +0100

    ice: Match on all profiles in slow-path
    
    In switchdev mode, slow-path rules need to match all protocols, in order
    to correctly redirect unfiltered or missed packets to the uplink. To set
    this up for the virtual function to uplink flow, the rule that redirects
    packets to the control VSI must have the tunnel type set to
    ICE_SW_TUN_AND_NON_TUN. As a result of that new tunnel type being set,
    ice_get_compat_fv_bitmap will select ICE_PROF_ALL. At that point all
    profiles would be selected for this rule, resulting in the desired
    behavior. Without this change slow-path would not work with
    tunnel protocols.
    
    Fixes: 8b032a55c1bd ("ice: low level support for tunnels")
    Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 8292656464e5f066d46cb73da957930613a2c597
Merge: f98da1d662988 bfe55a1f7fd6b
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Fri Feb 18 19:36:36 2022 +0100

    Merge branch 'acpi-processor'
    
    Merge fix for a recent boot lockup regression on 32-bit ThinkPad T40.
    
    * acpi-processor:
      ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40

commit 7993e65fdd0fe07beb9f36f998f9bbef2c0ee391
Merge: b9889768bda1a 36415a7964711
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:33:23 2022 -0800

    Merge tag 'mtd/fixes-for-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux
    
    Pull MTD fixes from Miquel Raynal:
     "MTD changes:
    
       - Qcom:
          - Don't print error message on -EPROBE_DEFER
          - Fix kernel panic on skipped partition
          - Fix missing free for pparts in cleanup
    
       - phram: Prevent divide by zero bug in phram_setup()
    
      Raw NAND controller changes:
    
       - ingenic: Fix missing put_device in ingenic_ecc_get
    
       - qcom: Fix clock sequencing in qcom_nandc_probe()
    
       - omap2: Prevent invalid configuration and build error
    
       - gpmi: Don't leak PM reference in error path
    
       - brcmnand: Fix incorrect sub-page ECC status"
    
    * tag 'mtd/fixes-for-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux:
      mtd: rawnand: brcmnand: Fixed incorrect sub-page ECC status
      mtd: rawnand: gpmi: don't leak PM reference in error path
      mtd: phram: Prevent divide by zero bug in phram_setup()
      mtd: rawnand: omap2: Prevent invalid configuration and build error
      mtd: parsers: qcom: Fix missing free for pparts in cleanup
      mtd: parsers: qcom: Fix kernel panic on skipped partition
      mtd: parsers: qcom: Don't print error message on -EPROBE_DEFER
      mtd: rawnand: qcom: Fix clock sequencing in qcom_nandc_probe()
      mtd: rawnand: ingenic: Fix missing put_device in ingenic_ecc_get

commit b9889768bda1a326238990b7d75ea179321d9693
Merge: 2848551bc6590 e92bc4cd34de2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:27:10 2022 -0800

    Merge tag 'block-5.17-2022-02-17' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - Surprise removal fix (Christoph)
    
     - Ensure that pages are zeroed before submitted for userspace IO
       (Haimin)
    
     - Fix blk-wbt accounting issue with BFQ (Laibin)
    
     - Use bsize for discard granularity in loop (Ming)
    
     - Fix missing zone handling in blk_complete_request() (Pankaj)
    
    * tag 'block-5.17-2022-02-17' of git://git.kernel.dk/linux-block:
      block/wbt: fix negative inflight counter when remove scsi device
      block: fix surprise removal for drivers calling blk_set_queue_dying
      block-map: add __GFP_ZERO flag for alloc_page in function bio_copy_kern
      block: loop:use kstatfs.f_bsize of backing file to set discard granularity
      block: Add handling for zone append command in blk_complete_request

commit 2848551bc6590a0f4eaaae71d60a4aaa0e99b8cf
Merge: 45a98a71d2daa c22a8086b3840
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:20:52 2022 -0800

    Merge tag 'sound-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
    
    Pull sound fixes from Takashi Iwai:
     "A collection of small patches, mostly for old and new regressions and
      device-specific fixes.
    
       - Regression fixes regarding ALSA core SG-buffer helpers
    
       - Regression fix for Realtek HD-audio mutex deadlock
    
       - Regression fix for USB-audio PM resume error
    
       - More coverage of ASoC core control API notification fixes
    
       - Old regression fixes for HD-audio probe mask
    
       - Fixes for ASoC Realtek codec work handling
    
       - Other device-specific quirks / fixes"
    
    * tag 'sound-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (24 commits)
      ASoC: intel: skylake: Set max DMA segment size
      ASoC: SOF: hda: Set max DMA segment size
      ALSA: hda: Set max DMA segment size
      ALSA: hda/realtek: Fix deadlock by COEF mutex
      ALSA: usb-audio: Don't abort resume upon errors
      ALSA: hda: Fix missing codec probe on Shenker Dock 15
      ALSA: hda: Fix regression on forced probe mask option
      ALSA: hda/realtek: Add quirk for Legion Y9000X 2019
      ALSA: usb-audio: revert to IMPLICIT_FB_FIXED_DEV for M-Audio FastTrack Ultra
      ASoC: wm_adsp: Correct control read size when parsing compressed buffer
      ASoC: qcom: Actually clear DMA interrupt register for HDMI
      ALSA: memalloc: invalidate SG pages before sync
      ALSA: memalloc: Fix dma_need_sync() checks
      MAINTAINERS: update cros_ec_codec maintainers
      ASoC: rt5682: do not block workqueue if card is unbound
      ASoC: rt5668: do not block workqueue if card is unbound
      ASoC: rt5682s: do not block workqueue if card is unbound
      ASoC: tas2770: Insert post reset delay
      ASoC: Revert "ASoC: mediatek: Check for error clk pointer"
      ASoC: amd: acp: Set gpio_spkr_en to None for max speaker amplifer in machine driver
      ...

commit 45a98a71d2daa8c58a99c17343a5d118b085a9be
Merge: ea4b3d299fe6b 4f6de676d94ee
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:14:19 2022 -0800

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fix from Catalin Marinas:
     "Fix wrong branch label in the EL2 GICv3 initialisation code"
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: Correct wrong label in macro __init_el2_gicv3

commit ea4b3d299fe6b6c9afa4a91dc2cf5479d0089eeb
Merge: 7476b043b1914 fe663df782581
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:10:14 2022 -0800

    Merge tag 'powerpc-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc fixes from Michael Ellerman:
    
     - Fix boot failure on 603 with DEBUG_PAGEALLOC and KFENCE
    
     - Fix 32-build with newer binutils that rejects 'ptesync' etc
    
    Thanks to Anders Roxell, Christophe Leroy, and Maxime Bizon.
    
    * tag 'powerpc-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc/lib/sstep: fix 'ptesync' build error
      powerpc/603: Fix boot failure with DEBUG_PAGEALLOC and KFENCE

commit 7476b043b1914413f75b7e99040969734ae1fab6
Merge: 9195e5e0adbb8 53923e0fe2098
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 18 09:04:27 2022 -0800

    Merge tag '5.17-rc5-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs fixes from Steve French:
     "Six small smb3 client fixes, three for stable:
    
       - fix for snapshot mount option
    
       - two ACL related fixes
    
       - use after free race fix
    
       - fix for confusing warning message logged with older dialects"
    
    * tag '5.17-rc5-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6:
      cifs: fix confusing unneeded warning message on smb2.1 and earlier
      cifs: modefromsids must add an ACE for authenticated users
      cifs: fix double free race when mount fails in cifs_get_root()
      cifs: do not use uninitialized data in the owner/group sid
      cifs: fix set of group SID via NTSD xattrs
      smb3: fix snapshot mount option

commit 98e437f134b3447e22af78e6c71837cd9b404990
Merge: f159f2941db99 1ba603f56568c
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 18 17:31:55 2022 +0100

    Merge tag 'scmi-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into arm/fixes
    
    Arm SCMI fix for v5.17
    
    A simple fix to remove space in the MODULE_ALIAS name used in the
    SCMI driver as userspace expect no spaces in these names.
    
    * tag 'scmi-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux:
      firmware: arm_scmi: Remove space in MODULE_ALIAS name
    
    Link: https://lore.kernel.org/r/20220214144245.2376150-1-sudeep.holla@arm.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit f159f2941db993d4356fbec5e5601c6c3fb470b3
Merge: 4f6668f05206d 31eeb6b09f405
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 18 17:30:32 2022 +0100

    Merge tag 'juno-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into arm/fixes
    
    Arm Juno fix for v5.17
    
    Just a single fix to address coherency issue reported[1] by removing the
    GICv2m address from the DMA ranges as it loose coherency if mapped as
    cacheable at the SMMU due to the attribute combining rules. The GICv2m
    range is normally programmed for Device memory attributes.
    
    [1] https://lore.kernel.org/stable/0a1d437d-9ea0-de83-3c19-e07f560ad37c@arm.com/
    
    * tag 'juno-fix-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux:
      arm64: dts: juno: Remove GICv2m dma-range
    
    Link: https://lore.kernel.org/r/20220214142615.2375269-1-sudeep.holla@arm.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 4f6668f05206d8b69cb0f52a635116b119dd6a27
Merge: 35f5417911753 40eb0dcf4114c
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 18 17:30:00 2022 +0100

    Merge tag 'optee-fix2-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee into arm/fixes
    
    OP-TEE fix error return code in probe functions
    
    * tag 'optee-fix2-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee:
      tee: optee: fix error return code in probe function
    
    Link: https://lore.kernel.org/r/20220214125931.GA1332792@jade
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 35f5417911753c7e815a5a2fbfc7c79648ecd8b6
Merge: a8cd28553f0f7 268a491aebc25
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 18 17:28:43 2022 +0100

    Merge tag 'socfpga_dts_update_for_v5.18_part2' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into arm/fixes
    
    SoCFPGA dts updates for v5.18, part 2
    - Add the "intel,socfpga-agilex-hsotg" compatible for Agilex platform
    
    * tag 'socfpga_dts_update_for_v5.18_part2' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux:
      arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg"
      dt-bindings: usb: dwc2: add compatible "intel,socfpga-agilex-hsotg"
    
    Link: https://lore.kernel.org/r/20220211112556.98940-2-dinguyen@kernel.org
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit c46fa8911b17e3f808679061a8af8bee219f4602
Author: Md Haris Iqbal <haris.iqbal@ionos.com>
Date:   Thu Feb 17 04:09:29 2022 +0100

    RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
    
    Error path of rtrs_clt_open() calls free_clt(), where free_permit is
    called.  This is wrong since error path of rtrs_clt_open() does not need
    to call free_permit().
    
    Also, moving free_permits() call to rtrs_clt_close(), makes it more
    aligned with the call to alloc_permit() in rtrs_clt_open().
    
    Fixes: 6a98d71daea1 ("RDMA/rtrs: client: main functionality")
    Link: https://lore.kernel.org/r/20220217030929.323849-2-haris.iqbal@ionos.com
    Signed-off-by: Md Haris Iqbal <haris.iqbal@ionos.com>
    Reviewed-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 8700af2cc18c919b2a83e74e0479038fd113c15d
Author: Md Haris Iqbal <haris.iqbal@ionos.com>
Date:   Thu Feb 17 04:09:28 2022 +0100

    RDMA/rtrs-clt: Fix possible double free in error case
    
    Callback function rtrs_clt_dev_release() for put_device() calls kfree(clt)
    to free memory. We shouldn't call kfree(clt) again, and we can't use the
    clt after kfree too.
    
    Replace device_register() with device_initialize() and device_add() so that
    dev_set_name can() be used appropriately.
    
    Move mutex_destroy() to the release function so it can be called in
    the alloc_clt err path.
    
    Fixes: eab098246625 ("RDMA/rtrs-clt: Refactor the failure cases in alloc_clt")
    Link: https://lore.kernel.org/r/20220217030929.323849-1-haris.iqbal@ionos.com
    Reported-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: Md Haris Iqbal <haris.iqbal@ionos.com>
    Reviewed-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 8a3d2ee0de3828e0d01f9682d35ee53704659bd0
Author: Zhengjun Xing <zhengjun.xing@linux.intel.com>
Date:   Fri Feb 18 17:31:27 2022 +0800

    perf evlist: Fix failed to use cpu list for uncore events
    
    The 'perf record' and 'perf stat' commands have supported the option
    '-C/--cpus' to count or collect only on the list of CPUs provided.
    
    Commit 1d3351e631fc34d7 ("perf tools: Enable on a list of CPUs for
    hybrid") add it to be supported for hybrid. For hybrid support, it
    checks the cpu list are available on hybrid PMU. But when we test only
    uncore events(or events not in cpu_core and cpu_atom), there is a bug:
    
    Before:
    
     # perf stat -C0  -e uncore_clock/clockticks/ sleep 1
       failed to use cpu list 0
    
    In this case, for uncore event, its pmu_name is not cpu_core or
    cpu_atom, so in evlist__fix_hybrid_cpus, perf_pmu__find_hybrid_pmu
    should return NULL,both events_nr and unmatched_count should be 0 ,then
    the cpu list check function evlist__fix_hybrid_cpus return -1 and the
    error "failed to use cpu list 0" will happen. Bypass "events_nr=0" case
    then the issue is fixed.
    
    After:
    
     # perf stat -C0  -e uncore_clock/clockticks/ sleep 1
    
     Performance counter stats for 'CPU(s) 0':
    
           195,476,873      uncore_clock/clockticks/
    
           1.004518677 seconds time elapsed
    
    When testing with at least one core event and uncore events, it has no
    issue.
    
     # perf stat -C0  -e cpu_core/cpu-cycles/,uncore_clock/clockticks/ sleep 1
    
     Performance counter stats for 'CPU(s) 0':
    
             5,993,774      cpu_core/cpu-cycles/
           301,025,912      uncore_clock/clockticks/
    
           1.003964934 seconds time elapsed
    
    Fixes: 1d3351e631fc34d7 ("perf tools: Enable on a list of CPUs for hybrid")
    Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Zhengjun Xing <zhengjun.xing@linux.intel.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: alexander.shishkin@intel.com
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jin Yao <yao.jin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20220218093127.1844241-1-zhengjun.xing@linux.intel.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f268088f65af69aa6ae1fb65e696cbb6478bcc9a
Author: John Garry <john.garry@huawei.com>
Date:   Fri Feb 18 17:33:33 2022 +0800

    perf test: Skip failing sigtrap test for arm+aarch64
    
    Skip the Sigtrap test for arm + arm64, same as was done for s390 in
    commit a840974e96fd ("perf test: Test 73 Sig_trap fails on s390"). For
    this, reuse BP_SIGNAL_IS_SUPPORTED - meaning that the arch can use BP to
    generate signals - instead of BP_ACCOUNT_IS_SUPPORTED, which is
    appropriate.
    
    As described by Will at [0], in the test we get stuck in a loop of
    handling the HW breakpoint exception and never making progress. GDB
    handles this by stepping over the faulting instruction, but with perf
    the kernel is expected to handle the step (which it doesn't for arm).
    
    Dmitry made an attempt to get this work, also mentioned in the same
    thread as [0], which was appreciated. But the best thing to do is skip
    the test for now.
    
    [0] https://lore.kernel.org/linux-perf-users/20220118124343.GC98966@leoy-ThinkPad-X240s/T/#m13b06c39d2a5100d340f009435df6f4d8ee57b5a
    
    Fixes: 5504f67944484495 ("perf test sigtrap: Add basic stress test for sigtrap handling")
    Signed-off-by: John Garry <john.garry@huawei.com>
    Tested-by: Leo Yan <leo.yan@linaro.org>
    Acked-by: Marco Elver <elver@google.com>
    Cc: Dmitriy Vyukov <dvyukov@google.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Marco Elver <elver@google.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Richter <tmricht@linux.ibm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux@armlinux.org.uk
    Link: https://lore.kernel.org/r/1645176813-202756-1-git-send-email-john.garry@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b352c3465bb808ab700d03f5bac2f7a6f37c5350
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Fri Feb 18 10:19:39 2022 +0800

    net: ll_temac: check the return value of devm_kmalloc()
    
    devm_kmalloc() returns a pointer to allocated memory on success, NULL
    on failure. While lp->indirect_lock is allocated by devm_kmalloc()
    without proper check. It is better to check the value of it to
    prevent potential wrong memory access.
    
    Fixes: f14f5c11f051 ("net: ll_temac: Support indirect_mutex share within TEMAC IP")
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a1cdec57e03a1352e92fbbe7974039dda4efcec0
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Feb 17 09:05:02 2022 -0800

    net-timestamp: convert sk->sk_tskey to atomic_t
    
    UDP sendmsg() can be lockless, this is causing all kinds
    of data races.
    
    This patch converts sk->sk_tskey to remove one of these races.
    
    BUG: KCSAN: data-race in __ip_append_data / __ip_append_data
    
    read to 0xffff8881035d4b6c of 4 bytes by task 8877 on cpu 1:
     __ip_append_data+0x1c1/0x1de0 net/ipv4/ip_output.c:994
     ip_make_skb+0x13f/0x2d0 net/ipv4/ip_output.c:1636
     udp_sendmsg+0x12bd/0x14c0 net/ipv4/udp.c:1249
     inet_sendmsg+0x5f/0x80 net/ipv4/af_inet.c:819
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    write to 0xffff8881035d4b6c of 4 bytes by task 8880 on cpu 0:
     __ip_append_data+0x1d8/0x1de0 net/ipv4/ip_output.c:994
     ip_make_skb+0x13f/0x2d0 net/ipv4/ip_output.c:1636
     udp_sendmsg+0x12bd/0x14c0 net/ipv4/udp.c:1249
     inet_sendmsg+0x5f/0x80 net/ipv4/af_inet.c:819
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x0000054d -> 0x0000054e
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 8880 Comm: syz-executor.5 Not tainted 5.17.0-rc2-syzkaller-00167-gdcb85f85fa6f-dirty #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 09c2d251b707 ("net-timestamp: add key to disambiguate concurrent datagrams")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e9da0b56fe27206b49f39805f7dcda8a89379062
Author: Oliver Neukum <oneukum@suse.com>
Date:   Thu Feb 17 14:10:44 2022 +0100

    sr9700: sanity check for packet length
    
    A malicious device can leak heap data to user space
    providing bogus frame lengths. Introduce a sanity check.
    
    Signed-off-by: Oliver Neukum <oneukum@suse.com>
    Reviewed-by: Grant Grundler <grundler@chromium.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2f131de361f6d0eaff17db26efdb844c178432f8
Author: Paul Blakey <paulb@nvidia.com>
Date:   Thu Feb 17 11:30:48 2022 +0200

    net/sched: act_ct: Fix flow table lookup after ct clear or switching zones
    
    Flow table lookup is skipped if packet either went through ct clear
    action (which set the IP_CT_UNTRACKED flag on the packet), or while
    switching zones and there is already a connection associated with
    the packet. This will result in no SW offload of the connection,
    and the and connection not being removed from flow table with
    TCP teardown (fin/rst packet).
    
    To fix the above, remove these unneccary checks in flow
    table lookup.
    
    Fixes: 46475bb20f4b ("net/sched: act_ct: Software offload of established flows")
    Signed-off-by: Paul Blakey <paulb@nvidia.com>
    Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4224cfd7fb6523f7a9d1c8bb91bb5df1e38eb624
Author: suresh kumar <suresh2514@gmail.com>
Date:   Thu Feb 17 07:25:18 2022 +0530

    net-sysfs: add check for netdevice being present to speed_show
    
    When bringing down the netdevice or system shutdown, a panic can be
    triggered while accessing the sysfs path because the device is already
    removed.
    
        [  755.549084] mlx5_core 0000:12:00.1: Shutdown was called
        [  756.404455] mlx5_core 0000:12:00.0: Shutdown was called
        ...
        [  757.937260] BUG: unable to handle kernel NULL pointer dereference at           (null)
        [  758.031397] IP: [<ffffffff8ee11acb>] dma_pool_alloc+0x1ab/0x280
    
        crash> bt
        ...
        PID: 12649  TASK: ffff8924108f2100  CPU: 1   COMMAND: "amsd"
        ...
         #9 [ffff89240e1a38b0] page_fault at ffffffff8f38c778
            [exception RIP: dma_pool_alloc+0x1ab]
            RIP: ffffffff8ee11acb  RSP: ffff89240e1a3968  RFLAGS: 00010046
            RAX: 0000000000000246  RBX: ffff89243d874100  RCX: 0000000000001000
            RDX: 0000000000000000  RSI: 0000000000000246  RDI: ffff89243d874090
            RBP: ffff89240e1a39c0   R8: 000000000001f080   R9: ffff8905ffc03c00
            R10: ffffffffc04680d4  R11: ffffffff8edde9fd  R12: 00000000000080d0
            R13: ffff89243d874090  R14: ffff89243d874080  R15: 0000000000000000
            ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
        #10 [ffff89240e1a39c8] mlx5_alloc_cmd_msg at ffffffffc04680f3 [mlx5_core]
        #11 [ffff89240e1a3a18] cmd_exec at ffffffffc046ad62 [mlx5_core]
        #12 [ffff89240e1a3ab8] mlx5_cmd_exec at ffffffffc046b4fb [mlx5_core]
        #13 [ffff89240e1a3ae8] mlx5_core_access_reg at ffffffffc0475434 [mlx5_core]
        #14 [ffff89240e1a3b40] mlx5e_get_fec_caps at ffffffffc04a7348 [mlx5_core]
        #15 [ffff89240e1a3bb0] get_fec_supported_advertised at ffffffffc04992bf [mlx5_core]
        #16 [ffff89240e1a3c08] mlx5e_get_link_ksettings at ffffffffc049ab36 [mlx5_core]
        #17 [ffff89240e1a3ce8] __ethtool_get_link_ksettings at ffffffff8f25db46
        #18 [ffff89240e1a3d48] speed_show at ffffffff8f277208
        #19 [ffff89240e1a3dd8] dev_attr_show at ffffffff8f0b70e3
        #20 [ffff89240e1a3df8] sysfs_kf_seq_show at ffffffff8eedbedf
        #21 [ffff89240e1a3e18] kernfs_seq_show at ffffffff8eeda596
        #22 [ffff89240e1a3e28] seq_read at ffffffff8ee76d10
        #23 [ffff89240e1a3e98] kernfs_fop_read at ffffffff8eedaef5
        #24 [ffff89240e1a3ed8] vfs_read at ffffffff8ee4e3ff
        #25 [ffff89240e1a3f08] sys_read at ffffffff8ee4f27f
        #26 [ffff89240e1a3f50] system_call_fastpath at ffffffff8f395f92
    
        crash> net_device.state ffff89443b0c0000
          state = 0x5  (__LINK_STATE_START| __LINK_STATE_NOCARRIER)
    
    To prevent this scenario, we also make sure that the netdevice is present.
    
    Signed-off-by: suresh kumar <suresh2514@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit efe4186e6a1b54bf38b9e05450d43b0da1fd7739
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Thu Feb 17 09:43:03 2022 +0800

    drivers: hamradio: 6pack: fix UAF bug caused by mod_timer()
    
    When a 6pack device is detaching, the sixpack_close() will act to cleanup
    necessary resources. Although del_timer_sync() in sixpack_close()
    won't return if there is an active timer, one could use mod_timer() in
    sp_xmit_on_air() to wake up timer again by calling userspace syscall such
    as ax25_sendmsg(), ax25_connect() and ax25_ioctl().
    
    This unexpected waked handler, sp_xmit_on_air(), realizes nothing about
    the undergoing cleanup and may still call pty_write() to use driver layer
    resources that have already been released.
    
    One of the possible race conditions is shown below:
    
          (USE)                      |      (FREE)
    ax25_sendmsg()                   |
     ax25_queue_xmit()               |
      ...                            |
      sp_xmit()                      |
       sp_encaps()                   | sixpack_close()
        sp_xmit_on_air()             |  del_timer_sync(&sp->tx_t)
         mod_timer(&sp->tx_t,...)    |  ...
                                     |  unregister_netdev()
                                     |  ...
         (wait a while)              | tty_release()
                                     |  tty_release_struct()
                                     |   release_tty()
        sp_xmit_on_air()             |    tty_kref_put(tty_struct) //FREE
         pty_write(tty_struct) //USE |    ...
    
    The corresponding fail log is shown below:
    ===============================================================
    BUG: KASAN: use-after-free in __run_timers.part.0+0x170/0x470
    Write of size 8 at addr ffff88800a652ab8 by task swapper/2/0
    ...
    Call Trace:
      ...
      queue_work_on+0x3f/0x50
      pty_write+0xcd/0xe0pty_write+0xcd/0xe0
      sp_xmit_on_air+0xb2/0x1f0
      call_timer_fn+0x28/0x150
      __run_timers.part.0+0x3c2/0x470
      run_timer_softirq+0x3b/0x80
      __do_softirq+0xf1/0x380
      ...
    
    This patch reorders the del_timer_sync() after the unregister_netdev()
    to avoid UAF bugs. Because the unregister_netdev() is well synchronized,
    it flushs out any pending queues, waits the refcount of net_device
    decreases to zero and removes net_device from kernel. There is not any
    running routines after executing unregister_netdev(). Therefore, we could
    not arouse timer from userspace again.
    
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Reviewed-by: Lin Ma <linma@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a679a61520d8a7b0211a1da990404daf5cc80b72
Author: Miklos Szeredi <mszeredi@redhat.com>
Date:   Fri Feb 18 11:47:51 2022 +0100

    fuse: fix fileattr op failure
    
    The fileattr API conversion broke lsattr on ntfs3g.
    
    Previously the ioctl(... FS_IOC_GETFLAGS) returned an EINVAL error, but
    after the conversion the error returned by the fuse filesystem was not
    propagated back to the ioctl() system call, resulting in success being
    returned with bogus values.
    
    Fix by checking for outarg.result in fuse_priv_ioctl(), just as generic
    ioctl code does.
    
    Reported-by: Jean-Pierre André <jean-pierre.andre@wanadoo.fr>
    Fixes: 72227eac177d ("fuse: convert to fileattr")
    Cc: <stable@vger.kernel.org> # v5.13
    Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

commit 44cad52cc14ae10062f142ec16ede489bccf4469
Author: Andy Lutomirski <luto@kernel.org>
Date:   Mon Feb 14 13:05:49 2022 +0100

    x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing
    
    xfpregs_set() handles 32-bit REGSET_XFP and 64-bit REGSET_FP. The actual
    code treats these regsets as modern FX state (i.e. the beginning part of
    XSTATE). The declarations of the regsets thought they were the legacy
    i387 format. The code thought they were the 32-bit (no xmm8..15) variant
    of XSTATE and, for good measure, made the high bits disappear by zeroing
    the wrong part of the buffer. The latter broke ptrace, and everything
    else confused anyone trying to understand the code. In particular, the
    nonsense definitions of the regsets confused me when I wrote this code.
    
    Clean this all up. Change the declarations to match reality (which
    shouldn't change the generated code, let alone the ABI) and fix
    xfpregs_set() to clear the correct bits and to only do so for 32-bit
    callers.
    
    Fixes: 6164331d15f7 ("x86/fpu: Rewrite xfpregs_set()")
    Reported-by: Luís Ferreira <contact@lsferreira.net>
    Signed-off-by: Andy Lutomirski <luto@kernel.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Cc: <stable@vger.kernel.org>
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215524
    Link: https://lore.kernel.org/r/YgpFnZpF01WwR8wU@zn.tnic

commit 834cea3a252ed4847db076a769ad9efe06afe2d5
Author: Rafał Miłecki <rafal@milecki.pl>
Date:   Tue Feb 15 08:27:35 2022 +0100

    i2c: brcmstb: fix support for DSL and CM variants
    
    DSL and CM (Cable Modem) support 8 B max transfer size and have a custom
    DT binding for that reason. This driver was checking for a wrong
    "compatible" however which resulted in an incorrect setup.
    
    Fixes: e2e5a2c61837 ("i2c: brcmstb: Adding support for CM and DSL SoCs")
    Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit 1aae05754fca861ce17f1f17fddcfbf8c0fc25b6
Author: Rudi Heitbaum <rudi@heitbaum.com>
Date:   Wed Feb 16 21:22:28 2022 +0000

    drm/imx/dcss: i.MX8MQ DCSS select DRM_GEM_CMA_HELPER
    
    Without DRM_GEM_CMA_HELPER i.MX8MQ DCSS won't build. This needs to be
    there.
    
    Signed-off-by: Rudi Heitbaum <rudi@heitbaum.com>
    Reviewed-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
    Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220216212228.1217831-1-rudi@heitbaum.com

commit ec756e40e271866f951d77c5e923d8deb6002b15
Author: Wanpeng Li <wanpengli@tencent.com>
Date:   Fri Feb 18 00:10:38 2022 -0800

    x86/kvm: Don't use pv tlb/ipi/sched_yield if on 1 vCPU
    
    Inspired by commit 3553ae5690a (x86/kvm: Don't use pvqspinlock code if
    only 1 vCPU), on a VM with only 1 vCPU, there is no need to enable
    pv tlb/ipi/sched_yield and we can save the memory for __pv_cpu_mask.
    
    Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <1645171838-2855-1-git-send-email-wanpengli@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ba1f77c546966c12d86220d078e5838dcaeab348
Author: Leonardo Bras <leobras@redhat.com>
Date:   Fri Feb 18 00:41:00 2022 -0300

    x86/kvm: Fix compilation warning in non-x86_64 builds
    
    On non-x86_64 builds, helpers gtod_is_based_on_tsc() and
    kvm_guest_supported_xfd() are defined but never used.  Because these are
    static inline but are in a .c file, some compilers do warn for them with
    -Wunused-function, which becomes an error if -Werror is present.
    
    Add #ifdef so they are only defined in x86_64 builds.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Leonardo Bras <leobras@redhat.com>
    Message-Id: <20220218034100.115702-1-leobras@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 8840f5460a23759403f1f2860429dcbcc2f04a65
Author: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>
Date:   Tue Jan 25 20:11:39 2022 +0100

    ARM: dts: Use 32KiHz oscillator on devkit8000
    
    Devkit8000 board seems to always used 32k_counter as clocksource.
    Restore this behavior.
    
    If clocksource is back to 32k_counter, timer12 is now the clockevent
    source (as before) and timer2 is not longer needed here.
    
    This commit fixes the same issue observed with commit 23885389dbbb
    ("ARM: dts: Fix timer regression for beagleboard revision c") when sleep
    is blocked until hitting keys over serial console.
    
    Fixes: aba1ad05da08 ("clocksource/drivers/timer-ti-dm: Add clockevent and clocksource support")
    Fixes: e428e250fde6 ("ARM: dts: Configure system timers for omap3")
    Signed-off-by: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>

commit 64324ef337d0caa5798fa8fa3f6bbfbd3245868a
Author: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>
Date:   Tue Jan 25 20:11:38 2022 +0100

    ARM: dts: switch timer config to common devkit8000 devicetree
    
    This patch allow lcd43 and lcd70 flavors to benefit from timer
    evolution.
    
    Fixes: e428e250fde6 ("ARM: dts: Configure system timers for omap3")
    Signed-off-by: Anthoine Bourgeois <anthoine.bourgeois@gmail.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>

commit 2f0754f27a230fee6e6d753f07585cee03bedfe3
Author: Siarhei Volkau <lis8215@gmail.com>
Date:   Sat Feb 5 20:18:49 2022 +0300

    clk: jz4725b: fix mmc0 clock gating
    
    The mmc0 clock gate bit was mistakenly assigned to "i2s" clock.
    You can find that the same bit is assigned to "mmc0" too.
    It leads to mmc0 hang for a long time after any sound activity
    also it  prevented PM_SLEEP to work properly.
    I guess it was introduced by copy-paste from jz4740 driver
    where it is really controls I2S clock gate.
    
    Fixes: 226dfa4726eb ("clk: Add Ingenic jz4725b CGU driver")
    Signed-off-by: Siarhei Volkau <lis8215@gmail.com>
    Tested-by: Siarhei Volkau <lis8215@gmail.com>
    Reviewed-by: Paul Cercueil <paul@crapouillou.net>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220205171849.687805-2-lis8215@gmail.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 3494894afff4ad11f25d8342cc99699be496d082
Author: Konrad Dybcio <konrad.dybcio@somainline.org>
Date:   Fri Feb 18 00:24:08 2022 +0100

    clk: qcom: gcc-msm8994: Remove NoC clocks
    
    Just like in commit 05cf3ec00d46 ("clk: qcom: gcc-msm8996: Drop (again)
    gcc_aggre1_pnoc_ahb_clk") adding NoC clocks turned out to be a huge
    mistake, as they cause a lot of issues at little benefit (basically
    letting Linux know about their children's frequencies), especially when
    mishandled or misconfigured.
    
    Adding these ones broke SDCC approx 99 out of 100 times, but that somehow
    went unnoticed. To prevent further issues like this one, remove them.
    
    This commit is effectively a revert of 74a33fac3aab ("clk: qcom:
    gcc-msm8994: Add missing NoC clocks") with ABI preservation.
    
    Fixes: 74a33fac3aab ("clk: qcom: gcc-msm8994: Add missing NoC clocks")
    Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
    Link: https://lore.kernel.org/r/20220217232408.78932-1-konrad.dybcio@somainline.org
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 9195e5e0adbb8a9a5ee9ef0f9dedf6340d827405
Merge: b3d971ec25346 6fec1ab67f8d6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 15:21:42 2022 -0800

    Merge tag 'linux-kselftest-fixes-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull Kselftest fixes from Shuah Khan:
     "Fixes to ftrace, exec, and seccomp tests build, run-time and install
      bugs. These bugs are in the way of running the tests"
    
    * tag 'linux-kselftest-fixes-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      selftests/ftrace: Do not trace do_softirq because of PREEMPT_RT
      selftests/seccomp: Fix seccomp failure by adding missing headers
      selftests/exec: Add non-regular to TEST_GEN_PROGS

commit 132507ed04ce0c5559be04dd378fec4f3bbc00e8
Author: Nikhil Gupta <nikhil.gupta@nxp.com>
Date:   Fri Jan 28 09:53:21 2022 +0530

    of/fdt: move elfcorehdr reservation early for crash dump kernel
    
    elfcorehdr_addr is fixed address passed to Second kernel which may be conflicted
    with potential reserved memory in Second kernel,so fdt_reserve_elfcorehdr() ahead
    of fdt_init_reserved_mem() can relieve this situation.
    
    Signed-off-by: Nikhil Gupta <nikhil.gupta@nxp.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220128042321.15228-1-nikhil.gupta@nxp.com

commit b3d971ec25346d6890e9e8f05b63f758cfcef8c5
Merge: 8b97cae315caf 5666b61019470
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 13:11:46 2022 -0800

    Merge tag 'drm-fixes-2022-02-18' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Regular fixes for rc5, nothing really stands out, mostly some amdgpu
      and i915 fixes with mediatek, radeon and some misc fixes.
    
      cma-helper:
       - set VM_DONTEXPAND
    
      atomic:
       - error handling fix
    
      mediatek:
       - fix probe defer loop with external bridge
    
      amdgpu:
       - Stable pstate clock fixes for Dimgrey Cavefish and Beige Goby
       - S0ix SDMA fix
       - Yellow Carp GPU reset fix
    
      radeon:
       - Backlight fix for iMac 12,1
    
      i915:
       - GVT kerneldoc cleanup.
       - GVT Kconfig should depend on X86
       - Prevent out of range access in SWSCI display code
       - Fix mbus join and dbuf slice config lookup
       - Fix inverted priority selection in the TTM backend
       - Fix FBC plane end Y offset check"
    
    * tag 'drm-fixes-2022-02-18' of git://anongit.freedesktop.org/drm/drm:
      drm/atomic: Don't pollute crtc_state->mode_blob with error pointers
      drm/radeon: Fix backlight control on iMac 12,1
      drm/amd/pm: correct the sequence of sending gpu reset msg
      drm/amdgpu: skipping SDMA hw_init and hw_fini for S0ix.
      drm/amd/pm: correct UMD pstate clocks for Dimgrey Cavefish and Beige Goby
      drm/i915/fbc: Fix the plane end Y offset check
      drm/i915/opregion: check port number bounds for SWSCI display power state
      drm/i915/ttm: tweak priority hint selection
      drm/i915: Fix mbus join config lookup
      drm/i915: Fix dbuf slice config lookup
      drm/cma-helper: Set VM_DONTEXPAND for mmap
      drm/mediatek: mtk_dsi: Avoid EPROBE_DEFER loop with external bridge
      drm/i915/gvt: Make DRM_I915_GVT depend on X86
      drm/i915/gvt: clean up kernel-doc in gtt.c

commit 7a2fb91285151e843d6f30c0689536a4747712cb
Merge: 8b97cae315caf 75134f16e7dd0
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 17 12:01:54 2022 -0800

    Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf
    
    Alexei Starovoitov says:
    
    ====================
    pull-request: bpf 2022-02-17
    
    We've added 8 non-merge commits during the last 7 day(s) which contain
    a total of 8 files changed, 119 insertions(+), 15 deletions(-).
    
    The main changes are:
    
    1) Add schedule points in map batch ops, from Eric.
    
    2) Fix bpf_msg_push_data with len 0, from Felix.
    
    3) Fix crash due to incorrect copy_map_value, from Kumar.
    
    4) Fix crash due to out of bounds access into reg2btf_ids, from Kumar.
    
    5) Fix a bpf_timer initialization issue with clang, from Yonghong.
    
    * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf:
      bpf: Add schedule points in batch ops
      bpf: Fix crash due to out of bounds access into reg2btf_ids.
      selftests: bpf: Check bpf_msg_push_data return value
      bpf: Fix a bpf_timer initialization issue
      bpf: Emit bpf_timer in vmlinux BTF
      selftests/bpf: Add test for bpf_timer overwriting crash
      bpf: Fix crash due to incorrect copy_map_value
      bpf: Do not try bpf_msg_push_data with len 0
    ====================
    
    Link: https://lore.kernel.org/r/20220217190000.37925-1-alexei.starovoitov@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5666b610194705587807a1078753eadc007b9d79
Merge: babb1fc323432 26ace8793aaef
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 18 05:44:44 2022 +1000

    Merge tag 'drm-intel-fixes-2022-02-17' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    - GVT kerneldoc cleanup. (Randy Dunlap)
    - GVT Kconfig should depend on X86. (Siva Mullati)
    - Prevent out of range access in SWSCI display code. (Jani Nikula)
    - Fix mbus join and dbuf slice config lookup. (Ville Syrjälä)
    - Fix inverted priority selection in the TTM backend. (Matthew Auld)
    - Fix FBC plane end Y offset check. (Ville Syrjälä)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yg4lA6k8+xp8u3aB@tursulin-mobl2

commit babb1fc3234320bd17930e02bad9d1a83f5e6859
Merge: 6379bd44ddbc4 439cf34c8e0a8
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 18 05:39:53 2022 +1000

    Merge tag 'drm-misc-fixes-2022-02-17' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/cma-helper: Set VM_DONTEXPAND
     * drm/atomic: Fix error handling in drm_atomic_set_mode_for_crtc()
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yg4mzQALMX69UmA3@linux-uq9g

commit 8b97cae315cafd7debf3601f88621e2aa8956ef3
Merge: a3580ac9b7a39 a6ab75cec1e46
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 11:33:59 2022 -0800

    Merge tag 'net-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from wireless and netfilter.
    
      Current release - regressions:
    
       - dsa: lantiq_gswip: fix use after free in gswip_remove()
    
       - smc: avoid overwriting the copies of clcsock callback functions
    
      Current release - new code bugs:
    
       - iwlwifi:
          - fix use-after-free when no FW is present
          - mei: fix the pskb_may_pull check in ipv4
          - mei: retry mapping the shared area
          - mvm: don't feed the hardware RFKILL into iwlmei
    
      Previous releases - regressions:
    
       - ipv6: mcast: use rcu-safe version of ipv6_get_lladdr()
    
       - tipc: fix wrong publisher node address in link publications
    
       - iwlwifi: mvm: don't send SAR GEO command for 3160 devices, avoid FW
         assertion
    
       - bgmac: make idm and nicpm resource optional again
    
       - atl1c: fix tx timeout after link flap
    
      Previous releases - always broken:
    
       - vsock: remove vsock from connected table when connect is
         interrupted by a signal
    
       - ping: change destination interface checks to match raw sockets
    
       - crypto: af_alg - get rid of alg_memory_allocated to avoid confusing
         semantics (and null-deref) after SO_RESERVE_MEM was added
    
       - ipv6: make exclusive flowlabel checks per-netns
    
       - bonding: force carrier update when releasing slave
    
       - sched: limit TC_ACT_REPEAT loops
    
       - bridge: multicast: notify switchdev driver whenever MC processing
         gets disabled because of max entries reached
    
       - wifi: brcmfmac: fix crash in brcm_alt_fw_path when WLAN not found
    
       - iwlwifi: fix locking when "HW not ready"
    
       - phy: mediatek: remove PHY mode check on MT7531
    
       - dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN
    
       - dsa: lan9303:
          - fix polarity of reset during probe
          - fix accelerated VLAN handling"
    
    * tag 'net-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (65 commits)
      bonding: force carrier update when releasing slave
      nfp: flower: netdev offload check for ip6gretap
      ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt
      ipv4: fix data races in fib_alias_hw_flags_set
      net: dsa: lan9303: add VLAN IDs to master device
      net: dsa: lan9303: handle hwaccel VLAN tags
      vsock: remove vsock from connected table when connect is interrupted by a signal
      Revert "net: ethernet: bgmac: Use devm_platform_ioremap_resource_byname"
      ping: fix the dif and sdif check in ping_lookup
      net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990
      net: sched: limit TC_ACT_REPEAT loops
      tipc: fix wrong notification node addresses
      net: dsa: lantiq_gswip: fix use after free in gswip_remove()
      ipv6: per-netns exclusive flowlabel checks
      net: bridge: multicast: notify switchdev driver whenever MC processing gets disabled
      CDC-NCM: avoid overflow in sanity checking
      mctp: fix use after free
      net: mscc: ocelot: fix use-after-free in ocelot_vlan_del()
      bonding: fix data-races around agg_select_timer
      dpaa2-eth: Initialize mutex used in one step timestamping path
      ...

commit a6ab75cec1e461f8a35559054c146c21428430b8
Author: Zhang Changzhong <zhangchangzhong@huawei.com>
Date:   Wed Feb 16 22:18:08 2022 +0800

    bonding: force carrier update when releasing slave
    
    In __bond_release_one(), bond_set_carrier() is only called when bond
    device has no slave. Therefore, if we remove the up slave from a master
    with two slaves and keep the down slave, the master will remain up.
    
    Fix this by moving bond_set_carrier() out of if (!bond_has_slaves(bond))
    statement.
    
    Reproducer:
    $ insmod bonding.ko mode=0 miimon=100 max_bonds=2
    $ ifconfig bond0 up
    $ ifenslave bond0 eth0 eth1
    $ ifconfig eth0 down
    $ ifenslave -d bond0 eth1
    $ cat /proc/net/bonding/bond0
    
    Fixes: ff59c4563a8d ("[PATCH] bonding: support carrier state for master")
    Signed-off-by: Zhang Changzhong <zhangchangzhong@huawei.com>
    Acked-by: Jay Vosburgh <jay.vosburgh@canonical.com>
    Link: https://lore.kernel.org/r/1645021088-38370-1-git-send-email-zhangchangzhong@huawei.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 75134f16e7dd0007aa474b281935c5f42e79f2c8
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Feb 17 10:19:02 2022 -0800

    bpf: Add schedule points in batch ops
    
    syzbot reported various soft lockups caused by bpf batch operations.
    
     INFO: task kworker/1:1:27 blocked for more than 140 seconds.
     INFO: task hung in rcu_barrier
    
    Nothing prevents batch ops to process huge amount of data,
    we need to add schedule points in them.
    
    Note that maybe_wait_bpf_programs(map) calls from
    generic_map_delete_batch() can be factorized by moving
    the call after the loop.
    
    This will be done later in -next tree once we get this fix merged,
    unless there is strong opinion doing this optimization sooner.
    
    Fixes: aa2e93b8e58e ("bpf: Add generic support for update and delete batch ops")
    Fixes: cb4d03ab499d ("bpf: Add generic support for lookup batch op")
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Reviewed-by: Stanislav Fomichev <sdf@google.com>
    Acked-by: Brian Vazquez <brianvv@google.com>
    Link: https://lore.kernel.org/bpf/20220217181902.808742-1-eric.dumazet@gmail.com

commit e5733d8c89c3b57c8fcd40b8acf508388fabaa42
Author: Reinette Chatre <reinette.chatre@intel.com>
Date:   Wed Feb 2 11:41:12 2022 -0800

    x86/sgx: Fix missing poison handling in reclaimer
    
    The SGX reclaimer code lacks page poison handling in its main
    free path. This can lead to avoidable machine checks if a
    poisoned page is freed and reallocated instead of being
    isolated.
    
    A troublesome scenario is:
     1. Machine check (#MC) occurs (asynchronous, !MF_ACTION_REQUIRED)
     2. arch_memory_failure() is eventually called
     3. (SGX) page->poison set to 1
     4. Page is reclaimed
     5. Page added to normal free lists by sgx_reclaim_pages()
        ^ This is the bug (poison pages should be isolated on the
        sgx_poison_page_list instead)
     6. Page is reallocated by some innocent enclave, a second (synchronous)
        in-kernel #MC is induced, probably during EADD instruction.
        ^ This is the fallout from the bug
    
    (6) is unfortunate and can be avoided by replacing the open coded
    enclave page freeing code in the reclaimer with sgx_free_epc_page()
    to obtain support for poison page handling that includes placing the
    poisoned page on the correct list.
    
    Fixes: d6d261bded8a ("x86/sgx: Add new sgx_epc_page flag bit to mark free pages")
    Fixes: 992801ae9243 ("x86/sgx: Initial poison handling for dirty and free pages")
    Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
    Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Link: https://lkml.kernel.org/r/dcc95eb2aaefb042527ac50d0a50738c7c160dac.1643830353.git.reinette.chatre@intel.com

commit a3580ac9b7a394a7d780448ba75cc5348d8a9e04
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Mon Feb 14 18:08:28 2022 -0800

    fs/file_table: fix adding missing kmemleak_not_leak()
    
    Commit b42bc9a3c511 ("Fix regression due to "fs: move binfmt_misc sysctl
    to its own file") fixed a regression, however it failed to add a
    kmemleak_not_leak().
    
    Fixes: b42bc9a3c511 ("Fix regression due to "fs: move binfmt_misc sysctl to its own file")
    Reported-by: Tong Zhang <ztong0001@gmail.com>
    Cc: Tong Zhang <ztong0001@gmail.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2dd3a8a139082679b7a73fc32596aa667b0841d1
Merge: edbd6c628ef19 31ded1535e318
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 10:06:09 2022 -0800

    Merge tag 'perf-tools-fixes-for-v5.17-2022-02-17' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tools fixes from Arnaldo Carvalho de Melo:
    
     - Fix corrupt inject files when only last branch option is enabled with
       ARM CoreSight ETM
    
     - Fix use-after-free for realloc(..., 0) in libsubcmd, found by gcc 12
    
     - Defer freeing string after possible strlen() on it in the BPF loader,
       found by gcc 12
    
     - Avoid early exit in 'perf trace' due SIGCHLD from non-workload
       processes
    
     - Fix arm64 perf_event_attr 'perf test's wrt --call-graph
       initialization
    
     - Fix libperf 32-bit build for 'perf test' wrt uint64_t printf
    
     - Fix perf_cpu_map__for_each_cpu macro in libperf, providing access to
       the CPU iterator
    
     - Sync linux/perf_event.h UAPI with the kernel sources
    
     - Update Jiri Olsa's email address in MAINTAINERS
    
    * tag 'perf-tools-fixes-for-v5.17-2022-02-17' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf bpf: Defer freeing string after possible strlen() on it
      perf test: Fix arm64 perf_event_attr tests wrt --call-graph initialization
      libsubcmd: Fix use-after-free for realloc(..., 0)
      libperf: Fix perf_cpu_map__for_each_cpu macro
      perf cs-etm: Fix corrupt inject files when only last branch option is enabled
      perf cs-etm: No-op refactor of synth opt usage
      libperf: Fix 32-bit build for tests uint64_t printf
      tools headers UAPI: Sync linux/perf_event.h with the kernel sources
      perf trace: Avoid early exit due SIGCHLD from non-workload processes
      MAINTAINERS: Update Jiri's email address

commit edbd6c628ef194ebef6e7b82ec9e396f57695d06
Merge: 80d47f5de5e31 a8e8f851e8299
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 09:54:00 2022 -0800

    Merge tag 'modules-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux
    
    Pull module fix from Luis Chamberlain:
     "Fixes module decompression when CONFIG_SYSFS=n
    
      The only fix trickled down for v5.17-rc cycle so far is the fix for
      module decompression when CONFIG_SYSFS=n. This was reported through
      0-day"
    
    * tag 'modules-5.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux:
      module: fix building with sysfs disabled

commit 7dbcda584eaa5bdb4a281c379207dacc1a5e6081
Author: Danie du Toit <danie.dutoit@corigine.com>
Date:   Thu Feb 17 14:48:20 2022 +0200

    nfp: flower: netdev offload check for ip6gretap
    
    IPv6 GRE tunnels are not being offloaded, this is caused by a missing
    netdev offload check. The functionality of IPv6 GRE tunnel offloading
    was previously added but this check was not included. Adding the
    ip6gretap check allows IPv6 GRE tunnels to be offloaded correctly.
    
    Fixes: f7536ffb0986 ("nfp: flower: Allow ipv6gretap interface for offloading")
    Signed-off-by: Danie du Toit <danie.dutoit@corigine.com>
    Signed-off-by: Louis Peens <louis.peens@corigine.com>
    Signed-off-by: Simon Horman <simon.horman@corigine.com>
    Link: https://lore.kernel.org/r/20220217124820.40436-1-louis.peens@corigine.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d95d6320ba7a51d61c097ffc3bcafcf70283414e
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Feb 16 09:32:17 2022 -0800

    ipv6: fix data-race in fib6_info_hw_flags_set / fib6_purge_rt
    
    Because fib6_info_hw_flags_set() is called without any synchronization,
    all accesses to gi6->offload, fi->trap and fi->offload_failed
    need some basic protection like READ_ONCE()/WRITE_ONCE().
    
    BUG: KCSAN: data-race in fib6_info_hw_flags_set / fib6_purge_rt
    
    read to 0xffff8881087d5886 of 1 bytes by task 13953 on cpu 0:
     fib6_drop_pcpu_from net/ipv6/ip6_fib.c:1007 [inline]
     fib6_purge_rt+0x4f/0x580 net/ipv6/ip6_fib.c:1033
     fib6_del_route net/ipv6/ip6_fib.c:1983 [inline]
     fib6_del+0x696/0x890 net/ipv6/ip6_fib.c:2028
     __ip6_del_rt net/ipv6/route.c:3876 [inline]
     ip6_del_rt+0x83/0x140 net/ipv6/route.c:3891
     __ipv6_dev_ac_dec+0x2b5/0x370 net/ipv6/anycast.c:374
     ipv6_dev_ac_dec net/ipv6/anycast.c:387 [inline]
     __ipv6_sock_ac_close+0x141/0x200 net/ipv6/anycast.c:207
     ipv6_sock_ac_close+0x79/0x90 net/ipv6/anycast.c:220
     inet6_release+0x32/0x50 net/ipv6/af_inet6.c:476
     __sock_release net/socket.c:650 [inline]
     sock_close+0x6c/0x150 net/socket.c:1318
     __fput+0x295/0x520 fs/file_table.c:280
     ____fput+0x11/0x20 fs/file_table.c:313
     task_work_run+0x8e/0x110 kernel/task_work.c:164
     tracehook_notify_resume include/linux/tracehook.h:189 [inline]
     exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
     exit_to_user_mode_prepare+0x160/0x190 kernel/entry/common.c:207
     __syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
     syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:300
     do_syscall_64+0x50/0xd0 arch/x86/entry/common.c:86
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    write to 0xffff8881087d5886 of 1 bytes by task 1912 on cpu 1:
     fib6_info_hw_flags_set+0x155/0x3b0 net/ipv6/route.c:6230
     nsim_fib6_rt_hw_flags_set drivers/net/netdevsim/fib.c:668 [inline]
     nsim_fib6_rt_add drivers/net/netdevsim/fib.c:691 [inline]
     nsim_fib6_rt_insert drivers/net/netdevsim/fib.c:756 [inline]
     nsim_fib6_event drivers/net/netdevsim/fib.c:853 [inline]
     nsim_fib_event drivers/net/netdevsim/fib.c:886 [inline]
     nsim_fib_event_work+0x284f/0x2cf0 drivers/net/netdevsim/fib.c:1477
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     worker_thread+0x616/0xa70 kernel/workqueue.c:2454
     kthread+0x2c7/0x2e0 kernel/kthread.c:327
     ret_from_fork+0x1f/0x30
    
    value changed: 0x22 -> 0x2a
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 1912 Comm: kworker/1:3 Not tainted 5.16.0-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Workqueue: events nsim_fib_event_work
    
    Fixes: 0c5fcf9e249e ("IPv6: Add "offload failed" indication to routes")
    Fixes: bb3c4ab93e44 ("ipv6: Add "offload" and "trap" indications to routes")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Amit Cohen <amcohen@nvidia.com>
    Cc: Ido Schimmel <idosch@nvidia.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220216173217.3792411-2-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9fcf986cc4bc6a3a39f23fbcbbc3a9e52d3c24fd
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Feb 16 09:32:16 2022 -0800

    ipv4: fix data races in fib_alias_hw_flags_set
    
    fib_alias_hw_flags_set() can be used by concurrent threads,
    and is only RCU protected.
    
    We need to annotate accesses to following fields of struct fib_alias:
    
        offload, trap, offload_failed
    
    Because of READ_ONCE()WRITE_ONCE() limitations, make these
    field u8.
    
    BUG: KCSAN: data-race in fib_alias_hw_flags_set / fib_alias_hw_flags_set
    
    read to 0xffff888134224a6a of 1 bytes by task 2013 on cpu 1:
     fib_alias_hw_flags_set+0x28a/0x470 net/ipv4/fib_trie.c:1050
     nsim_fib4_rt_hw_flags_set drivers/net/netdevsim/fib.c:350 [inline]
     nsim_fib4_rt_add drivers/net/netdevsim/fib.c:367 [inline]
     nsim_fib4_rt_insert drivers/net/netdevsim/fib.c:429 [inline]
     nsim_fib4_event drivers/net/netdevsim/fib.c:461 [inline]
     nsim_fib_event drivers/net/netdevsim/fib.c:881 [inline]
     nsim_fib_event_work+0x1852/0x2cf0 drivers/net/netdevsim/fib.c:1477
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     process_scheduled_works kernel/workqueue.c:2370 [inline]
     worker_thread+0x7df/0xa70 kernel/workqueue.c:2456
     kthread+0x1bf/0x1e0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30
    
    write to 0xffff888134224a6a of 1 bytes by task 4872 on cpu 0:
     fib_alias_hw_flags_set+0x2d5/0x470 net/ipv4/fib_trie.c:1054
     nsim_fib4_rt_hw_flags_set drivers/net/netdevsim/fib.c:350 [inline]
     nsim_fib4_rt_add drivers/net/netdevsim/fib.c:367 [inline]
     nsim_fib4_rt_insert drivers/net/netdevsim/fib.c:429 [inline]
     nsim_fib4_event drivers/net/netdevsim/fib.c:461 [inline]
     nsim_fib_event drivers/net/netdevsim/fib.c:881 [inline]
     nsim_fib_event_work+0x1852/0x2cf0 drivers/net/netdevsim/fib.c:1477
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     process_scheduled_works kernel/workqueue.c:2370 [inline]
     worker_thread+0x7df/0xa70 kernel/workqueue.c:2456
     kthread+0x1bf/0x1e0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30
    
    value changed: 0x00 -> 0x02
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 4872 Comm: kworker/0:0 Not tainted 5.17.0-rc3-syzkaller-00188-g1d41d2e82623-dirty #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Workqueue: events nsim_fib_event_work
    
    Fixes: 90b93f1b31f8 ("ipv4: Add "offload" and "trap" indications to routes")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Reviewed-by: Ido Schimmel <idosch@nvidia.com>
    Link: https://lore.kernel.org/r/20220216173217.3792411-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 430065e2671905ac675f97b7af240cc255964e93
Author: Mans Rullgard <mans@mansr.com>
Date:   Wed Feb 16 20:48:18 2022 +0000

    net: dsa: lan9303: add VLAN IDs to master device
    
    If the master device does VLAN filtering, the IDs used by the switch
    must be added for any frames to be received.  Do this in the
    port_enable() function, and remove them in port_disable().
    
    Fixes: a1292595e006 ("net: dsa: add new DSA switch driver for the SMSC-LAN9303")
    Signed-off-by: Mans Rullgard <mans@mansr.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
    Link: https://lore.kernel.org/r/20220216204818.28746-1-mans@mansr.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 017b355bbdc6620fd8fe05fe297f553ce9d855ee
Author: Mans Rullgard <mans@mansr.com>
Date:   Wed Feb 16 12:46:34 2022 +0000

    net: dsa: lan9303: handle hwaccel VLAN tags
    
    Check for a hwaccel VLAN tag on rx and use it if present.  Otherwise,
    use __skb_vlan_pop() like the other tag parsers do.  This fixes the case
    where the VLAN tag has already been consumed by the master.
    
    Fixes: a1292595e006 ("net: dsa: add new DSA switch driver for the SMSC-LAN9303")
    Signed-off-by: Mans Rullgard <mans@mansr.com>
    Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
    Link: https://lore.kernel.org/r/20220216124634.23123-1-mans@mansr.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 17 08:57:47 2022 -0800

    mm: don't try to NUMA-migrate COW pages that have other uses
    
    Oded Gabbay reports that enabling NUMA balancing causes corruption with
    his Gaudi accelerator test load:
    
     "All the details are in the bug, but the bottom line is that somehow,
      this patch causes corruption when the numa balancing feature is
      enabled AND we don't use process affinity AND we use GUP to pin pages
      so our accelerator can DMA to/from system memory.
    
      Either disabling numa balancing, using process affinity to bind to
      specific numa-node or reverting this patch causes the bug to
      disappear"
    
    and Oded bisected the issue to commit 09854ba94c6a ("mm: do_wp_page()
    simplification").
    
    Now, the NUMA balancing shouldn't actually be changing the writability
    of a page, and as such shouldn't matter for COW.  But it appears it
    does.  Suspicious.
    
    However, regardless of that, the condition for enabling NUMA faults in
    change_pte_range() is nonsensical.  It uses "page_mapcount(page)" to
    decide if a COW page should be NUMA-protected or not, and that makes
    absolutely no sense.
    
    The number of mappings a page has is irrelevant: not only does GUP get a
    reference to a page as in Oded's case, but the other mappings migth be
    paged out and the only reference to them would be in the page count.
    
    Since we should never try to NUMA-balance a page that we can't move
    anyway due to other references, just fix the code to use 'page_count()'.
    Oded confirms that that fixes his issue.
    
    Now, this does imply that something in NUMA balancing ends up changing
    page protections (other than the obvious one of making the page
    inaccessible to get the NUMA faulting information).  Otherwise the COW
    simplification wouldn't matter - since doing the GUP on the page would
    make sure it's writable.
    
    The cause of that permission change would be good to figure out too,
    since it clearly results in spurious COW events - but fixing the
    nonsensical test that just happened to work before is obviously the
    CorrectThing(tm) to do regardless.
    
    Fixes: 09854ba94c6a ("mm: do_wp_page() simplification")
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215616
    Link: https://lore.kernel.org/all/CAFCwf10eNmwq2wD71xjUhqkvv5+_pJMR1nPug2RqNDcFT4H86Q@mail.gmail.com/
    Reported-and-tested-by: Oded Gabbay <oded.gabbay@gmail.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Peter Xu <peterx@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b9208492fcaecff8f43915529ae34b3bcb03877c
Author: Seth Forshee <sforshee@digitalocean.com>
Date:   Thu Feb 17 08:13:12 2022 -0600

    vsock: remove vsock from connected table when connect is interrupted by a signal
    
    vsock_connect() expects that the socket could already be in the
    TCP_ESTABLISHED state when the connecting task wakes up with a signal
    pending. If this happens the socket will be in the connected table, and
    it is not removed when the socket state is reset. In this situation it's
    common for the process to retry connect(), and if the connection is
    successful the socket will be added to the connected table a second
    time, corrupting the list.
    
    Prevent this by calling vsock_remove_connected() if a signal is received
    while waiting for a connection. This is harmless if the socket is not in
    the connected table, and if it is in the table then removing it will
    prevent list corruption from a double add.
    
    Note for backporting: this patch requires d5afa82c977e ("vsock: correct
    removal of socket from the list"), which is in all current stable trees
    except 4.9.y.
    
    Fixes: d021c344051a ("VSOCK: Introduce VM Sockets")
    Signed-off-by: Seth Forshee <sforshee@digitalocean.com>
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
    Link: https://lore.kernel.org/r/20220217141312.2297547-1-sforshee@digitalocean.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6aba04ee3263669b335458c4cf4c7d97d6940229
Author: Jonas Gorski <jonas.gorski@gmail.com>
Date:   Wed Feb 16 10:46:34 2022 -0800

    Revert "net: ethernet: bgmac: Use devm_platform_ioremap_resource_byname"
    
    This reverts commit 3710e80952cf2dc48257ac9f145b117b5f74e0a5.
    
    Since idm_base and nicpm_base are still optional resources not present
    on all platforms, this breaks the driver for everything except Northstar
    2 (which has both).
    
    The same change was already reverted once with 755f5738ff98 ("net:
    broadcom: fix a mistake about ioremap resource").
    
    So let's do it again.
    
    Fixes: 3710e80952cf ("net: ethernet: bgmac: Use devm_platform_ioremap_resource_byname")
    Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
    [florian: Added comments to explain the resources are optional]
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220216184634.2032460-1-f.fainelli@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6764eb690e77ecded48587d6d4e346ba2e196546
Author: Maxime Ripard <maxime@cerno.tech>
Date:   Thu Feb 3 11:20:03 2022 +0100

    drm/vc4: crtc: Fix runtime_pm reference counting
    
    At boot on the BCM2711, if the HDMI controllers are running, the CRTC
    driver will disable itself and its associated HDMI controller to work
    around a hardware bug that would leave some pixels stuck in a FIFO.
    
    In order to avoid that issue, we need to run some operations in lockstep
    between the CRTC and HDMI controller, and we need to make sure the HDMI
    controller will be powered properly.
    
    However, since we haven't enabled it through KMS, the runtime_pm state
    is off at this point so we need to make sure the device is powered
    through pm_runtime_resume_and_get, and once the operations are complete,
    we call pm_runtime_put.
    
    However, the HDMI controller will do that itself in its
    post_crtc_powerdown, which means we'll end up calling pm_runtime_put for
    a single pm_runtime_get, throwing the reference counting off. Let's
    remove the pm_runtime_put call in the CRTC code in order to have the
    proper counting.
    
    Fixes: bca10db67bda ("drm/vc4: crtc: Make sure the HDMI controller is powered when disabling")
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220203102003.1114673-1-maxime@cerno.tech

commit e40945ab7c7f966d0c37b7bd7b0596497dfe228d
Author: Maxime Ripard <maxime@cerno.tech>
Date:   Thu Jan 27 12:14:52 2022 +0100

    drm/vc4: hdmi: Unregister codec device on unbind
    
    On bind we will register the HDMI codec device but we don't unregister
    it on unbind, leading to a device leakage. Unregister our device at
    unbind.
    
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127111452.222002-1-maxime@cerno.tech

commit 32f57cb1b2c8d6f20aefec7052b1bfeb7e3b69d4
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Thu Feb 17 08:59:32 2022 -0500

    IB/qib: Fix duplicate sysfs directory name
    
    The qib driver load has been failing with the following message:
    
      sysfs: cannot create duplicate filename '/devices/pci0000:80/0000:80:02.0/0000:81:00.0/infiniband/qib0/ports/1/linkcontrol'
    
    The patch below has two "linkcontrol" names causing the duplication.
    
    Fix by using the correct "diag_counters" name on the second instance.
    
    Fixes: 4a7aaf88c89f ("RDMA/qib: Use attributes for the port sysfs")
    Link: https://lore.kernel.org/r/1645106372-23004-1-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Cc: <stable@vger.kernel.org>
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 80808768e41324d2e23de89972b5406c1020e6e4
Author: Jon Lin <jon.lin@rock-chips.com>
Date:   Wed Feb 16 09:40:24 2022 +0800

    spi: rockchip: terminate dma transmission when slave abort
    
    After slave abort, all DMA should be stopped, or it will affect the
    next transmission and maybe abort again.
    
    Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
    Link: https://lore.kernel.org/r/20220216014028.8123-3-jon.lin@rock-chips.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 9382df0a98aad5bbcd4d634790305a1d786ad224
Author: Jon Lin <jon.lin@rock-chips.com>
Date:   Wed Feb 16 09:40:23 2022 +0800

    spi: rockchip: Fix error in getting num-cs property
    
    Get num-cs u32 from dts of_node property rather than u16.
    
    Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
    Link: https://lore.kernel.org/r/20220216014028.8123-2-jon.lin@rock-chips.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit d04ad245d67a3991dfea5e108e4c452c2ab39bac
Author: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
Date:   Thu Feb 17 14:20:07 2022 +0530

    regmap-irq: Update interrupt clear register for proper reset
    
    With the existing logic where clear_ack is true (HW doesn’t support
    auto clear for ICR), interrupt clear register reset is not handled
    properly. Due to this only the first interrupts get processed properly
    and further interrupts are blocked due to not resetting interrupt
    clear register.
    
    Example for issue case where Invert_ack is false and clear_ack is true:
    
        Say Default ISR=0x00 & ICR=0x00 and ISR is triggered with 2
        interrupts making ISR = 0x11.
    
        Step 1: Say ISR is set 0x11 (store status_buff = ISR). ISR needs to
                be cleared with the help of ICR once the Interrupt is processed.
    
        Step 2: Write ICR = 0x11 (status_buff), this will clear the ISR to 0x00.
    
        Step 3: Issue - In the existing code, ICR is written with ICR =
                ~(status_buff) i.e ICR = 0xEE -> This will block all the interrupts
                from raising except for interrupts 0 and 4. So expectation here is to
                reset ICR, which will unblock all the interrupts.
    
                if (chip->clear_ack) {
                     if (chip->ack_invert && !ret)
                      ........
                     else if (!ret)
                         ret = regmap_write(map, reg,
                                ~data->status_buf[i]);
    
    So writing 0 and 0xff (when ack_invert is true) should have no effect, other
    than clearing the ACKs just set.
    
    Fixes: 3a6f0fb7b8eb ("regmap: irq: Add support to clear ack registers")
    Signed-off-by: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
    Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Link: https://lore.kernel.org/r/20220217085007.30218-1-quic_pkumpatl@quicinc.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 0cbae9e24fa7d6c6e9f828562f084da82217a0c5
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Feb 9 18:09:41 2022 -0600

    ucounts: Handle wrapping in is_ucounts_overlimit
    
    While examining is_ucounts_overlimit and reading the various messages
    I realized that is_ucounts_overlimit fails to deal with counts that
    may have wrapped.
    
    Being wrapped should be a transitory state for counts and they should
    never be wrapped for long, but it can happen so handle it.
    
    Cc: stable@vger.kernel.org
    Fixes: 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    Link: https://lkml.kernel.org/r/20220216155832.680775-5-ebiederm@xmission.com
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit c923a8e7edb010da67424077cbf1a6f1396ebd2e
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Feb 14 09:40:25 2022 -0600

    ucounts: Move RLIMIT_NPROC handling after set_user
    
    During set*id() which cred->ucounts to charge the the current process
    to is not known until after set_cred_ucounts.  So move the
    RLIMIT_NPROC checking into a new helper flag_nproc_exceeded and call
    flag_nproc_exceeded after set_cred_ucounts.
    
    This is very much an arbitrary subset of the places where we currently
    change the RLIMIT_NPROC accounting, designed to preserve the existing
    logic.
    
    Fixing the existing logic will be the subject of another series of
    changes.
    
    Cc: stable@vger.kernel.org
    Link: https://lkml.kernel.org/r/20220216155832.680775-4-ebiederm@xmission.com
    Fixes: 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit a55d07294f1e9b576093bdfa95422f8119941e83
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Feb 9 16:22:20 2022 -0600

    ucounts: Base set_cred_ucounts changes on the real user
    
    Michal Koutný <mkoutny@suse.com> wrote:
    > Tasks are associated to multiple users at once. Historically and as per
    > setrlimit(2) RLIMIT_NPROC is enforce based on real user ID.
    >
    > The commit 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    > made the accounting structure "indexed" by euid and hence potentially
    > account tasks differently.
    >
    > The effective user ID may be different e.g. for setuid programs but
    > those are exec'd into already existing task (i.e. below limit), so
    > different accounting is moot.
    >
    > Some special setresuid(2) users may notice the difference, justifying
    > this fix.
    
    I looked at cred->ucount and it is only used for rlimit operations
    that were previously stored in cred->user.  Making the fact
    cred->ucount can refer to a different user from cred->user a bug,
    affecting all uses of cred->ulimit not just RLIMIT_NPROC.
    
    Fix set_cred_ucounts to always use the real uid not the effective uid.
    
    Further simplify set_cred_ucounts by noticing that set_cred_ucounts
    somehow retained a draft version of the check to see if alloc_ucounts
    was needed that checks the new->user and new->user_ns against the
    current_real_cred().  Remove that draft version of the check.
    
    All that matters for setting the cred->ucounts are the user_ns and uid
    fields in the cred.
    
    Cc: stable@vger.kernel.org
    Link: https://lkml.kernel.org/r/20220207121800.5079-4-mkoutny@suse.com
    Link: https://lkml.kernel.org/r/20220216155832.680775-3-ebiederm@xmission.com
    Reported-by: Michal Koutný <mkoutny@suse.com>
    Reviewed-by: Michal Koutný <mkoutny@suse.com>
    Fixes: 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 8f2f9c4d82f24f172ae439e5035fc1e0e4c229dd
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Feb 9 20:03:19 2022 -0600

    ucounts: Enforce RLIMIT_NPROC not RLIMIT_NPROC+1
    
    Michal Koutný <mkoutny@suse.com> wrote:
    
    > It was reported that v5.14 behaves differently when enforcing
    > RLIMIT_NPROC limit, namely, it allows one more task than previously.
    > This is consequence of the commit 21d1c5e386bc ("Reimplement
    > RLIMIT_NPROC on top of ucounts") that missed the sharpness of
    > equality in the forking path.
    
    This can be fixed either by fixing the test or by moving the increment
    to be before the test.  Fix it my moving copy_creds which contains
    the increment before is_ucounts_overlimit.
    
    In the case of CLONE_NEWUSER the ucounts in the task_cred changes.
    The function is_ucounts_overlimit needs to use the final version of
    the ucounts for the new process.  Which means moving the
    is_ucounts_overlimit test after copy_creds is necessary.
    
    Both the test in fork and the test in set_user were semantically
    changed when the code moved to ucounts.  The change of the test in
    fork was bad because it was before the increment.  The test in
    set_user was wrong and the change to ucounts fixed it.  So this
    fix only restores the old behavior in one lcation not two.
    
    Link: https://lkml.kernel.org/r/20220204181144.24462-1-mkoutny@suse.com
    Link: https://lkml.kernel.org/r/20220216155832.680775-2-ebiederm@xmission.com
    Cc: stable@vger.kernel.org
    Reported-by: Michal Koutný <mkoutny@suse.com>
    Reviewed-by: Michal Koutný <mkoutny@suse.com>
    Fixes: 21d1c5e386bc ("Reimplement RLIMIT_NPROC on top of ucounts")
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 32fde84362c40961726a5c91f35ad37355ccc0c6
Author: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Date:   Wed Feb 16 09:12:15 2022 +0100

    usb: dwc2: drd: fix soft connect when gadget is unconfigured
    
    When the gadget driver hasn't been (yet) configured, and the cable is
    connected to a HOST, the SFTDISCON gets cleared unconditionally, so the
    HOST tries to enumerate it.
    At the host side, this can result in a stuck USB port or worse. When
    getting lucky, some dmesg can be observed at the host side:
     new high-speed USB device number ...
     device descriptor read/64, error -110
    
    Fix it in drd, by checking the enabled flag before calling
    dwc2_hsotg_core_connect(). It will be called later, once configured,
    by the normal flow:
    - udc_bind_to_driver
     - usb_gadget_connect
       - dwc2_hsotg_pullup
         - dwc2_hsotg_core_connect
    
    Fixes: 17f934024e84 ("usb: dwc2: override PHY input signals with usb role switch support")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
    Link: https://lore.kernel.org/r/1644999135-13478-1-git-send-email-fabrice.gasnier@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 62e3f0afe246720f7646eb1b034a6897dac34405
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sun Feb 13 14:05:17 2022 +0100

    usb: dwc3: pci: Fix Bay Trail phy GPIO mappings
    
    When the Bay Trail phy GPIO mappings where added cs and reset were swapped,
    this did not cause any issues sofar, because sofar they were always driven
    high/low at the same time.
    
    Note the new mapping has been verified both in /sys/kernel/debug/gpio
    output on Android factory images on multiple devices, as well as in
    the schematics for some devices.
    
    Fixes: 5741022cbdf3 ("usb: dwc3: pci: Add GPIO lookup table on platforms without ACPI GPIO resources")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220213130524.18748-3-hdegoede@redhat.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit c16bdeb5a39ffa3f32b32f812831a2092d2a3061
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Fri Feb 11 13:57:44 2022 -0600

    rlimit: Fix RLIMIT_NPROC enforcement failure caused by capability calls in set_user
    
    Solar Designer <solar@openwall.com> wrote:
    > I'm not aware of anyone actually running into this issue and reporting
    > it.  The systems that I personally know use suexec along with rlimits
    > still run older/distro kernels, so would not yet be affected.
    >
    > So my mention was based on my understanding of how suexec works, and
    > code review.  Specifically, Apache httpd has the setting RLimitNPROC,
    > which makes it set RLIMIT_NPROC:
    >
    > https://httpd.apache.org/docs/2.4/mod/core.html#rlimitnproc
    >
    > The above documentation for it includes:
    >
    > "This applies to processes forked from Apache httpd children servicing
    > requests, not the Apache httpd children themselves. This includes CGI
    > scripts and SSI exec commands, but not any processes forked from the
    > Apache httpd parent, such as piped logs."
    >
    > In code, there are:
    >
    > ./modules/generators/mod_cgid.c:        ( (cgid_req.limits.limit_nproc_set) && ((rc = apr_procattr_limit_set(procattr, APR_LIMIT_NPROC,
    > ./modules/generators/mod_cgi.c:        ((rc = apr_procattr_limit_set(procattr, APR_LIMIT_NPROC,
    > ./modules/filters/mod_ext_filter.c:    rv = apr_procattr_limit_set(procattr, APR_LIMIT_NPROC, conf->limit_nproc);
    >
    > For example, in mod_cgi.c this is in run_cgi_child().
    >
    > I think this means an httpd child sets RLIMIT_NPROC shortly before it
    > execs suexec, which is a SUID root program.  suexec then switches to the
    > target user and execs the CGI script.
    >
    > Before 2863643fb8b9, the setuid() in suexec would set the flag, and the
    > target user's process count would be checked against RLIMIT_NPROC on
    > execve().  After 2863643fb8b9, the setuid() in suexec wouldn't set the
    > flag because setuid() is (naturally) called when the process is still
    > running as root (thus, has those limits bypass capabilities), and
    > accordingly execve() would not check the target user's process count
    > against RLIMIT_NPROC.
    
    In commit 2863643fb8b9 ("set_user: add capability check when
    rlimit(RLIMIT_NPROC) exceeds") capable calls were added to set_user to
    make it more consistent with fork.  Unfortunately because of call site
    differences those capable calls were checking the credentials of the
    user before set*id() instead of after set*id().
    
    This breaks enforcement of RLIMIT_NPROC for applications that set the
    rlimit and then call set*id() while holding a full set of
    capabilities.  The capabilities are only changed in the new credential
    in security_task_fix_setuid().
    
    The code in apache suexec appears to follow this pattern.
    
    Commit 909cc4ae86f3 ("[PATCH] Fix two bugs with process limits
    (RLIMIT_NPROC)") where this check was added describes the targes of this
    capability check as:
    
      2/ When a root-owned process (e.g. cgiwrap) sets up process limits and then
          calls setuid, the setuid should fail if the user would then be running
          more than rlim_cur[RLIMIT_NPROC] processes, but it doesn't.  This patch
          adds an appropriate test.  With this patch, and per-user process limit
          imposed in cgiwrap really works.
    
    So the original use case of this check also appears to match the broken
    pattern.
    
    Restore the enforcement of RLIMIT_NPROC by removing the bad capable
    checks added in set_user.  This unfortunately restores the
    inconsistent state the code has been in for the last 11 years, but
    dealing with the inconsistencies looks like a larger problem.
    
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/all/20210907213042.GA22626@openwall.com/
    Link: https://lkml.kernel.org/r/20220212221412.GA29214@openwall.com
    Link: https://lkml.kernel.org/r/20220216155832.680775-1-ebiederm@xmission.com
    Fixes: 2863643fb8b9 ("set_user: add capability check when rlimit(RLIMIT_NPROC) exceeds")
    History-Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
    Reviewed-by: Solar Designer <solar@openwall.com>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 988896bb61827345c6d074dd5f2af1b7b008193f
Author: Leonardo Bras <leobras@redhat.com>
Date:   Thu Feb 17 02:30:30 2022 -0300

    x86/kvm/fpu: Remove kvm_vcpu_arch.guest_supported_xcr0
    
    kvm_vcpu_arch currently contains the guest supported features in both
    guest_supported_xcr0 and guest_fpu.fpstate->user_xfeatures field.
    
    Currently both fields are set to the same value in
    kvm_vcpu_after_set_cpuid() and are not changed anywhere else after that.
    
    Since it's not good to keep duplicated data, remove guest_supported_xcr0.
    
    To keep the code more readable, introduce kvm_guest_supported_xcr()
    and kvm_guest_supported_xfd() to replace the previous usages of
    guest_supported_xcr0.
    
    Signed-off-by: Leonardo Bras <leobras@redhat.com>
    Message-Id: <20220217053028.96432-3-leobras@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ad856280ddea3401e1f5060ef20e6de9f6122c76
Author: Leonardo Bras <leobras@redhat.com>
Date:   Thu Feb 17 02:30:29 2022 -0300

    x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0
    
    During host/guest switch (like in kvm_arch_vcpu_ioctl_run()), the kernel
    swaps the fpu between host/guest contexts, by using fpu_swap_kvm_fpstate().
    
    When xsave feature is available, the fpu swap is done by:
    - xsave(s) instruction, with guest's fpstate->xfeatures as mask, is used
      to store the current state of the fpu registers to a buffer.
    - xrstor(s) instruction, with (fpu_kernel_cfg.max_features &
      XFEATURE_MASK_FPSTATE) as mask, is used to put the buffer into fpu regs.
    
    For xsave(s) the mask is used to limit what parts of the fpu regs will
    be copied to the buffer. Likewise on xrstor(s), the mask is used to
    limit what parts of the fpu regs will be changed.
    
    The mask for xsave(s), the guest's fpstate->xfeatures, is defined on
    kvm_arch_vcpu_create(), which (in summary) sets it to all features
    supported by the cpu which are enabled on kernel config.
    
    This means that xsave(s) will save to guest buffer all the fpu regs
    contents the cpu has enabled when the guest is paused, even if they
    are not used.
    
    This would not be an issue, if xrstor(s) would also do that.
    
    xrstor(s)'s mask for host/guest swap is basically every valid feature
    contained in kernel config, except XFEATURE_MASK_PKRU.
    Accordingto kernel src, it is instead switched in switch_to() and
    flush_thread().
    
    Then, the following happens with a host supporting PKRU starts a
    guest that does not support it:
    1 - Host has XFEATURE_MASK_PKRU set. 1st switch to guest,
    2 - xsave(s) fpu regs to host fpustate (buffer has XFEATURE_MASK_PKRU)
    3 - xrstor(s) guest fpustate to fpu regs (fpu regs have XFEATURE_MASK_PKRU)
    4 - guest runs, then switch back to host,
    5 - xsave(s) fpu regs to guest fpstate (buffer now have XFEATURE_MASK_PKRU)
    6 - xrstor(s) host fpstate to fpu regs.
    7 - kvm_vcpu_ioctl_x86_get_xsave() copy guest fpstate to userspace (with
        XFEATURE_MASK_PKRU, which should not be supported by guest vcpu)
    
    On 5, even though the guest does not support PKRU, it does have the flag
    set on guest fpstate, which is transferred to userspace via vcpu ioctl
    KVM_GET_XSAVE.
    
    This becomes a problem when the user decides on migrating the above guest
    to another machine that does not support PKRU: the new host restores
    guest's fpu regs to as they were before (xrstor(s)), but since the new
    host don't support PKRU, a general-protection exception ocurs in xrstor(s)
    and that crashes the guest.
    
    This can be solved by making the guest's fpstate->user_xfeatures hold
    a copy of guest_supported_xcr0. This way, on 7 the only flags copied to
    userspace will be the ones compatible to guest requirements, and thus
    there will be no issue during migration.
    
    As a bonus, it will also fail if userspace tries to set fpu features
    (with the KVM_SET_XSAVE ioctl) that are not compatible to the guest
    configuration.  Such features will never be returned by KVM_GET_XSAVE
    or KVM_GET_XSAVE2.
    
    Also, since kvm_vcpu_after_set_cpuid() now sets fpstate->user_xfeatures,
    there is not need to set it in kvm_check_cpuid(). So, change
    fpstate_realloc() so it does not touch fpstate->user_xfeatures if a
    non-NULL guest_fpu is passed, which is the case when kvm_check_cpuid()
    calls it.
    
    Signed-off-by: Leonardo Bras <leobras@redhat.com>
    Message-Id: <20220217053028.96432-2-leobras@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit aba2081e0a9c977396124aa6df93b55ed5912b19
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Feb 15 11:22:04 2022 -0700

    tps6598x: clear int mask on probe failure
    
    The interrupt mask is enabled before any potential failure points in
    the driver, which can leave a failure path where we exit with
    interrupts enabled but the device not live. This causes an infinite
    stream of interrupts on an Apple M1 Pro laptop on USB-C.
    
    Add a failure label that's used post enabling interrupts, where we
    mask them again before returning an error.
    
    Suggested-by: Sven Peter <sven@svenpeter.dev>
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Jens Axboe <axboe@kernel.dk>
    Link: https://lore.kernel.org/r/e6b80669-20f3-06e7-9ed5-8951a9c6db6f@kernel.dk
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 35a79e64de29e8d57a5989aac57611c0cd29e13e
Author: Xin Long <lucien.xin@gmail.com>
Date:   Wed Feb 16 00:20:52 2022 -0500

    ping: fix the dif and sdif check in ping_lookup
    
    When 'ping' changes to use PING socket instead of RAW socket by:
    
       # sysctl -w net.ipv4.ping_group_range="0 100"
    
    There is another regression caused when matching sk_bound_dev_if
    and dif, RAW socket is using inet_iif() while PING socket lookup
    is using skb->dev->ifindex, the cmd below fails due to this:
    
      # ip link add dummy0 type dummy
      # ip link set dummy0 up
      # ip addr add 192.168.111.1/24 dev dummy0
      # ping -I dummy0 192.168.111.1 -c1
    
    The issue was also reported on:
    
      https://github.com/iputils/iputils/issues/104
    
    But fixed in iputils in a wrong way by not binding to device when
    destination IP is on device, and it will cause some of kselftests
    to fail, as Jianlin noticed.
    
    This patch is to use inet(6)_iif and inet(6)_sdif to get dif and
    sdif for PING socket, and keep consistent with RAW socket.
    
    Fixes: c319b4d76b9e ("net: ipv4: add IPPROTO_ICMP socket kind")
    Reported-by: Jianlin Shi <jishi@redhat.com>
    Signed-off-by: Xin Long <lucien.xin@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e92bc4cd34de2ce454bdea8cd198b8067ee4e123
Author: Laibin Qiu <qiulaibin@huawei.com>
Date:   Sat Jan 22 19:10:45 2022 +0800

    block/wbt: fix negative inflight counter when remove scsi device
    
    Now that we disable wbt by set WBT_STATE_OFF_DEFAULT in
    wbt_disable_default() when switch elevator to bfq. And when
    we remove scsi device, wbt will be enabled by wbt_enable_default.
    If it become false positive between wbt_wait() and wbt_track()
    when submit write request.
    
    The following is the scenario that triggered the problem.
    
    T1                          T2                           T3
                                elevator_switch_mq
                                bfq_init_queue
                                wbt_disable_default <= Set
                                rwb->enable_state (OFF)
    Submit_bio
    blk_mq_make_request
    rq_qos_throttle
    <= rwb->enable_state (OFF)
                                                             scsi_remove_device
                                                             sd_remove
                                                             del_gendisk
                                                             blk_unregister_queue
                                                             elv_unregister_queue
                                                             wbt_enable_default
                                                             <= Set rwb->enable_state (ON)
    q_qos_track
    <= rwb->enable_state (ON)
    ^^^^^^ this request will mark WBT_TRACKED without inflight add and will
    lead to drop rqw->inflight to -1 in wbt_done() which will trigger IO hung.
    
    Fix this by move wbt_enable_default() from elv_unregister to
    bfq_exit_queue(). Only re-enable wbt when bfq exit.
    
    Fixes: 76a8040817b4b ("blk-wbt: make sure throttle is enabled properly")
    
    Remove oneline stale comment, and kill one oneshot local variable.
    
    Signed-off-by: Ming Lei <ming.lei@rehdat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/linux-block/20211214133103.551813-1-qiulaibin@huawei.com/
    Signed-off-by: Laibin Qiu <qiulaibin@huawei.com>
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 7a5428dcb7902700b830e912feee4e845df7c019
Author: Christoph Hellwig <hch@lst.de>
Date:   Thu Feb 17 08:52:31 2022 +0100

    block: fix surprise removal for drivers calling blk_set_queue_dying
    
    Various block drivers call blk_set_queue_dying to mark a disk as dead due
    to surprise removal events, but since commit 8e141f9eb803 that doesn't
    work given that the GD_DEAD flag needs to be set to stop I/O.
    
    Replace the driver calls to blk_set_queue_dying with a new (and properly
    documented) blk_mark_disk_dead API, and fold blk_set_queue_dying into the
    only remaining caller.
    
    Fixes: 8e141f9eb803 ("block: drain file system I/O on del_gendisk")
    Reported-by: Markus Blöchl <markus.bloechl@ipetronik.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
    Link: https://lore.kernel.org/r/20220217075231.1140-1-hch@lst.de
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit cc8f7fe1f5eab010191aa4570f27641876fa1267
Author: Haimin Zhang <tcs.kernel@gmail.com>
Date:   Wed Feb 16 16:40:38 2022 +0800

    block-map: add __GFP_ZERO flag for alloc_page in function bio_copy_kern
    
    Add __GFP_ZERO flag for alloc_page in function bio_copy_kern to initialize
    the buffer of a bio.
    
    Signed-off-by: Haimin Zhang <tcs.kernel@gmail.com>
    Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220216084038.15635-1-tcs.kernel@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 3a55f729240a686aa8af00af436306c0cd532522
Author: Anton Romanov <romanton@google.com>
Date:   Wed Feb 16 18:26:54 2022 +0000

    kvm: x86: Disable KVM_HC_CLOCK_PAIRING if tsc is in always catchup mode
    
    If vcpu has tsc_always_catchup set each request updates pvclock data.
    KVM_HC_CLOCK_PAIRING consumers such as ptp_kvm_x86 rely on tsc read on
    host's side and do hypercall inside pvclock_read_retry loop leading to
    infinite loop in such situation.
    
    v3:
        Removed warn
        Changed return code to KVM_EFAULT
    v2:
        Added warn
    
    Signed-off-by: Anton Romanov <romanton@google.com>
    Message-Id: <20220216182653.506850-1-romanton@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4cb9a998b1ce25fad74a82f5a5c45a4ef40de337
Author: Wanpeng Li <wanpengli@tencent.com>
Date:   Tue Feb 15 02:15:42 2022 -0800

    KVM: Fix lockdep false negative during host resume
    
    I saw the below splatting after the host suspended and resumed.
    
       WARNING: CPU: 0 PID: 2943 at kvm/arch/x86/kvm/../../../virt/kvm/kvm_main.c:5531 kvm_resume+0x2c/0x30 [kvm]
       CPU: 0 PID: 2943 Comm: step_after_susp Tainted: G        W IOE     5.17.0-rc3+ #4
       RIP: 0010:kvm_resume+0x2c/0x30 [kvm]
       Call Trace:
        <TASK>
        syscore_resume+0x90/0x340
        suspend_devices_and_enter+0xaee/0xe90
        pm_suspend.cold+0x36b/0x3c2
        state_store+0x82/0xf0
        kernfs_fop_write_iter+0x1b6/0x260
        new_sync_write+0x258/0x370
        vfs_write+0x33f/0x510
        ksys_write+0xc9/0x160
        do_syscall_64+0x3b/0xc0
        entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    lockdep_is_held() can return -1 when lockdep is disabled which triggers
    this warning. Let's use lockdep_assert_not_held() which can detect
    incorrect calls while holding a lock and it also avoids false negatives
    when lockdep is disabled.
    
    Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <1644920142-81249-1-git-send-email-wanpengli@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 127770ac0d043435375ab86434f31a93efa88215
Author: Aaron Lewis <aaronlewis@google.com>
Date:   Mon Feb 14 21:29:51 2022 +0000

    KVM: x86: Add KVM_CAP_ENABLE_CAP to x86
    
    Follow the precedent set by other architectures that support the VCPU
    ioctl, KVM_ENABLE_CAP, and advertise the VM extension, KVM_CAP_ENABLE_CAP.
    This way, userspace can ensure that KVM_ENABLE_CAP is available on a
    vcpu before using it.
    
    Fixes: 5c919412fe61 ("kvm/x86: Hyper-V synthetic interrupt controller")
    Signed-off-by: Aaron Lewis <aaronlewis@google.com>
    Message-Id: <20220214212950.1776943-1-aaronlewis@google.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 21e8a96377e6b6debae42164605bf9dcbe5720c5
Author: Daniele Palmas <dnlplm@gmail.com>
Date:   Tue Feb 15 12:13:35 2022 +0100

    net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990
    
    Add quirk CDC_MBIM_FLAG_AVOID_ALTSETTING_TOGGLE for Telit FN990
    0x1071 composition in order to avoid bind error.
    
    Signed-off-by: Daniele Palmas <dnlplm@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a867e9d0cc15039a6ef72e17e2603303dcd1783f
Author: Oliver Upton <oupton@google.com>
Date:   Thu Feb 17 10:12:42 2022 +0000

    KVM: arm64: Don't miss pending interrupts for suspended vCPU
    
    In order to properly emulate the WFI instruction, KVM reads back
    ICH_VMCR_EL2 and enables doorbells for GICv4. These preparations are
    necessary in order to recognize pending interrupts in
    kvm_arch_vcpu_runnable() and return to the guest. Until recently, this
    work was done by kvm_arch_vcpu_{blocking,unblocking}(). Since commit
    6109c5a6ab7f ("KVM: arm64: Move vGIC v4 handling for WFI out arch
    callback hook"), these callbacks were gutted and superseded by
    kvm_vcpu_wfi().
    
    It is important to note that KVM implements PSCI CPU_SUSPEND calls as
    a WFI within the guest. However, the implementation calls directly into
    kvm_vcpu_halt(), which skips the needed work done in kvm_vcpu_wfi()
    to detect pending interrupts. Fix the issue by calling the WFI helper.
    
    Fixes: 6109c5a6ab7f ("KVM: arm64: Move vGIC v4 handling for WFI out arch callback hook")
    Signed-off-by: Oliver Upton <oupton@google.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220217101242.3013716-1-oupton@google.com

commit ac89895213d8950dba6ab342863a0959f73142a7
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Thu Feb 17 14:13:49 2022 +0100

    HID: elo: Revert USB reference counting
    
    Commit 817b8b9c539 ("HID: elo: fix memory leak in elo_probe") introduced
    memory leak on error path, but more importantly the whole USB reference
    counting is not needed at all in the first place, as the driver itself
    doesn't change the reference counting in any way, and the associated
    usb_device is guaranteed to be kept around by USB core as long as the
    driver binding exists.
    
    Reported-by: Alan Stern <stern@rowland.harvard.edu>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Fixes: fbf42729d0e ("HID: elo: update the reference count of the usb device structure")
    Fixes: 817b8b9c539 ("HID: elo: fix memory leak in elo_probe")
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 31ded1535e3182778a1d0e5c32711f55da3bc512
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Feb 16 16:01:00 2022 -0300

    perf bpf: Defer freeing string after possible strlen() on it
    
    This was detected by the gcc in Fedora Rawhide's gcc:
    
      50    11.01 fedora:rawhide                : FAIL gcc version 12.0.1 20220205 (Red Hat 12.0.1-0) (GCC)
            inlined from 'bpf__config_obj' at util/bpf-loader.c:1242:9:
        util/bpf-loader.c:1225:34: error: pointer 'map_opt' may be used after 'free' [-Werror=use-after-free]
         1225 |                 *key_scan_pos += strlen(map_opt);
              |                                  ^~~~~~~~~~~~~~~
        util/bpf-loader.c:1223:9: note: call to 'free' here
         1223 |         free(map_name);
              |         ^~~~~~~~~~~~~~
        cc1: all warnings being treated as errors
    
    So do the calculations on the pointer before freeing it.
    
    Fixes: 04f9bf2bac72480c ("perf bpf-loader: Add missing '*' for key_scan_pos")
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Wang ShaoBo <bobo.shaobowang@huawei.com>
    Link: https://lore.kernel.org/lkml/Yg1VtQxKrPpS3uNA@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 6379bd44ddbc45cf5c7c46f74ad00de4ed72e7ce
Merge: fb9c96714f10d 364438fd629f7
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 17 19:06:07 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-02-16' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-02-16:
    
    amdgpu:
    - Stable pstate clock fixes for Dimgrey Cavefish and Beige Goby
    - S0ix SDMA fix
    - Yellow Carp GPU reset fix
    
    radeon:
    - Backlight fix for iMac 12,1
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220217035242.8084-1-alexander.deucher@amd.com

commit c22a8086b384025ab97ce07465420a219697d3f2
Author: Takashi Iwai <tiwai@suse.de>
Date:   Tue Feb 15 14:27:56 2022 +0100

    ASoC: intel: skylake: Set max DMA segment size
    
    The recent code refactoring to use the standard DMA helper requires
    the max DMA segment size setup for SG list management.  Without it,
    the kernel may spew warnings when a large buffer is allocated.
    
    This patch sets up dma_set_max_seg_size() for avoiding spurious
    warnings.
    
    Fixes: 2c95b92ecd92 ("ALSA: memalloc: Unify x86 SG-buffer handling (take#3)")
    Acked-by: Cezary Rojewski <cezary.rojewski@intel.com>
    Acked-by: Mark Brown <broonie@kernel.org>
    Cc: <stable@vger.kernel.org>
    BugLink: https://github.com/thesofproject/linux/issues/3430
    Link: https://lore.kernel.org/r/20220215132756.31236-4-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 8872fc0d04592925b74ad9ab1b5686f4e016befe
Author: Takashi Iwai <tiwai@suse.de>
Date:   Tue Feb 15 14:27:55 2022 +0100

    ASoC: SOF: hda: Set max DMA segment size
    
    The recent code refactoring to use the standard DMA helper requires
    the max DMA segment size setup for SG list management.  Without it,
    the kernel may spew warnings when a large buffer is allocated.
    
    This patch sets up dma_set_max_seg_size() for avoiding spurious
    warnings.
    
    Fixes: 2c95b92ecd92 ("ALSA: memalloc: Unify x86 SG-buffer handling (take#3)")
    Acked-by: Mark Brown <broonie@kernel.org>
    Cc: <stable@vger.kernel.org>
    BugLink: https://github.com/thesofproject/linux/issues/3430
    Link: https://lore.kernel.org/r/20220215132756.31236-3-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit acd289e04a0a1f52bea7ff1129b365626059e3c2
Author: Takashi Iwai <tiwai@suse.de>
Date:   Tue Feb 15 14:27:54 2022 +0100

    ALSA: hda: Set max DMA segment size
    
    The recent code refactoring to use the standard DMA helper requires
    the max DMA segment size setup for SG list management.  Without it,
    the kernel may spew warnings when a large buffer is allocated.
    
    This patch sets up dma_set_max_seg_size() for avoiding spurious
    warnings.
    
    Fixes: 2c95b92ecd92 ("ALSA: memalloc: Unify x86 SG-buffer handling (take#3)")
    Cc: <stable@vger.kernel.org>
    BugLink: https://github.com/thesofproject/linux/issues/3430
    Link: https://lore.kernel.org/r/20220215132756.31236-2-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 16693c1b2d98cebc8dedf03b49d1053cf1826c86
Author: Jon Hunter <jonathanh@nvidia.com>
Date:   Wed Feb 16 09:17:43 2022 +0000

    drm/tegra: Fix cast to restricted __le32
    
    Sparse warns about the following cast in the function
    falcon_copy_firmware_image() ...
    
     drivers/gpu/drm/tegra/falcon.c:66:27: warning: cast to restricted __le32
    
    Fix this by casting the firmware data array to __le32 instead of u32.
    
    Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit fb9c96714f10d99b8125d6f9dfbd36b0005cf5c3
Merge: 754e0b0e35608 647474b8d9802
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Feb 17 15:00:47 2022 +1000

    Merge tag 'mediatek-drm-fixes-5.17' of https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux into drm-fixes
    
    Mediatek DRM Fixes for Linux 5.17
    
    1. Avoid EPROBE_DEFER loop with external bridge
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Chun-Kuang Hu <chunkuang.hu@kernel.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/1645027727-19554-1-git-send-email-chunkuang.hu@kernel.org

commit 5740d068909676d4bdb5c9c00c37a83df7728909
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Feb 15 15:53:05 2022 -0800

    net: sched: limit TC_ACT_REPEAT loops
    
    We have been living dangerously, at the mercy of malicious users,
    abusing TC_ACT_REPEAT, as shown by this syzpot report [1].
    
    Add an arbitrary limit (32) to the number of times an action can
    return TC_ACT_REPEAT.
    
    v2: switch the limit to 32 instead of 10.
        Use net_warn_ratelimited() instead of pr_err_once().
    
    [1] (C repro available on demand)
    
    rcu: INFO: rcu_preempt self-detected stall on CPU
    rcu:    1-...!: (10500 ticks this GP) idle=021/1/0x4000000000000000 softirq=5592/5592 fqs=0
            (t=10502 jiffies g=5305 q=190)
    rcu: rcu_preempt kthread timer wakeup didn't happen for 10502 jiffies! g5305 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
    rcu:    Possible timer handling issue on cpu=0 timer-softirq=3527
    rcu: rcu_preempt kthread starved for 10505 jiffies! g5305 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
    rcu:    Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
    rcu: RCU grace-period kthread stack dump:
    task:rcu_preempt     state:I stack:29344 pid:   14 ppid:     2 flags:0x00004000
    Call Trace:
     <TASK>
     context_switch kernel/sched/core.c:4986 [inline]
     __schedule+0xab2/0x4db0 kernel/sched/core.c:6295
     schedule+0xd2/0x260 kernel/sched/core.c:6368
     schedule_timeout+0x14a/0x2a0 kernel/time/timer.c:1881
     rcu_gp_fqs_loop+0x186/0x810 kernel/rcu/tree.c:1963
     rcu_gp_kthread+0x1de/0x320 kernel/rcu/tree.c:2136
     kthread+0x2e9/0x3a0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
     </TASK>
    rcu: Stack dump where RCU GP kthread last ran:
    Sending NMI from CPU 1 to CPUs 0:
    NMI backtrace for cpu 0
    CPU: 0 PID: 3646 Comm: syz-executor358 Not tainted 5.17.0-rc3-syzkaller-00149-gbf8e59fd315f #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:rep_nop arch/x86/include/asm/vdso/processor.h:13 [inline]
    RIP: 0010:cpu_relax arch/x86/include/asm/vdso/processor.h:18 [inline]
    RIP: 0010:pv_wait_head_or_lock kernel/locking/qspinlock_paravirt.h:437 [inline]
    RIP: 0010:__pv_queued_spin_lock_slowpath+0x3b8/0xb40 kernel/locking/qspinlock.c:508
    Code: 48 89 eb c6 45 01 01 41 bc 00 80 00 00 48 c1 e9 03 83 e3 07 41 be 01 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8d 2c 01 eb 0c <f3> 90 41 83 ec 01 0f 84 72 04 00 00 41 0f b6 45 00 38 d8 7f 08 84
    RSP: 0018:ffffc9000283f1b0 EFLAGS: 00000206
    RAX: 0000000000000003 RBX: 0000000000000000 RCX: 1ffff1100fc0071e
    RDX: 0000000000000001 RSI: 0000000000000201 RDI: 0000000000000000
    RBP: ffff88807e0038f0 R08: 0000000000000001 R09: ffffffff8ffbf9ff
    R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000004c1e
    R13: ffffed100fc0071e R14: 0000000000000001 R15: ffff8880b9c3aa80
    FS:  00005555562bf300(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007ffdbfef12b8 CR3: 00000000723c2000 CR4: 00000000003506f0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     pv_queued_spin_lock_slowpath arch/x86/include/asm/paravirt.h:591 [inline]
     queued_spin_lock_slowpath arch/x86/include/asm/qspinlock.h:51 [inline]
     queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
     do_raw_spin_lock+0x200/0x2b0 kernel/locking/spinlock_debug.c:115
     spin_lock_bh include/linux/spinlock.h:354 [inline]
     sch_tree_lock include/net/sch_generic.h:610 [inline]
     sch_tree_lock include/net/sch_generic.h:605 [inline]
     prio_tune+0x3b9/0xb50 net/sched/sch_prio.c:211
     prio_init+0x5c/0x80 net/sched/sch_prio.c:244
     qdisc_create.constprop.0+0x44a/0x10f0 net/sched/sch_api.c:1253
     tc_modify_qdisc+0x4c5/0x1980 net/sched/sch_api.c:1660
     rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5594
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x6e8/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmsg+0xe5/0x1b0 net/socket.c:2496
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7f7ee98aae99
    Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007ffdbfef12d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
    RAX: ffffffffffffffda RBX: 00007ffdbfef1300 RCX: 00007f7ee98aae99
    RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000003
    RBP: 0000000000000000 R08: 000000000000000d R09: 000000000000000d
    R10: 000000000000000d R11: 0000000000000246 R12: 00007ffdbfef12f0
    R13: 00000000000f4240 R14: 000000000004ca47 R15: 00007ffdbfef12e4
     </TASK>
    INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 2.293 msecs
    NMI backtrace for cpu 1
    CPU: 1 PID: 3260 Comm: kworker/1:3 Not tainted 5.17.0-rc3-syzkaller-00149-gbf8e59fd315f #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Workqueue: mld mld_ifc_work
    Call Trace:
     <IRQ>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     nmi_cpu_backtrace.cold+0x47/0x144 lib/nmi_backtrace.c:111
     nmi_trigger_cpumask_backtrace+0x1b3/0x230 lib/nmi_backtrace.c:62
     trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline]
     rcu_dump_cpu_stacks+0x25e/0x3f0 kernel/rcu/tree_stall.h:343
     print_cpu_stall kernel/rcu/tree_stall.h:604 [inline]
     check_cpu_stall kernel/rcu/tree_stall.h:688 [inline]
     rcu_pending kernel/rcu/tree.c:3919 [inline]
     rcu_sched_clock_irq.cold+0x5c/0x759 kernel/rcu/tree.c:2617
     update_process_times+0x16d/0x200 kernel/time/timer.c:1785
     tick_sched_handle+0x9b/0x180 kernel/time/tick-sched.c:226
     tick_sched_timer+0x1b0/0x2d0 kernel/time/tick-sched.c:1428
     __run_hrtimer kernel/time/hrtimer.c:1685 [inline]
     __hrtimer_run_queues+0x1c0/0xe50 kernel/time/hrtimer.c:1749
     hrtimer_interrupt+0x31c/0x790 kernel/time/hrtimer.c:1811
     local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1086 [inline]
     __sysvec_apic_timer_interrupt+0x146/0x530 arch/x86/kernel/apic/apic.c:1103
     sysvec_apic_timer_interrupt+0x8e/0xc0 arch/x86/kernel/apic/apic.c:1097
     </IRQ>
     <TASK>
     asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:638
    RIP: 0010:__sanitizer_cov_trace_const_cmp4+0xc/0x70 kernel/kcov.c:286
    Code: 00 00 00 48 89 7c 30 e8 48 89 4c 30 f0 4c 89 54 d8 20 48 89 10 5b c3 0f 1f 80 00 00 00 00 41 89 f8 bf 03 00 00 00 4c 8b 14 24 <89> f1 65 48 8b 34 25 00 70 02 00 e8 14 f9 ff ff 84 c0 74 4b 48 8b
    RSP: 0018:ffffc90002c5eea8 EFLAGS: 00000246
    RAX: 0000000000000007 RBX: ffff88801c625800 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
    RBP: ffff8880137d3100 R08: 0000000000000000 R09: 0000000000000000
    R10: ffffffff874fcd88 R11: 0000000000000000 R12: ffff88801d692dc0
    R13: ffff8880137d3104 R14: 0000000000000000 R15: ffff88801d692de8
     tcf_police_act+0x358/0x11d0 net/sched/act_police.c:256
     tcf_action_exec net/sched/act_api.c:1049 [inline]
     tcf_action_exec+0x1a6/0x530 net/sched/act_api.c:1026
     tcf_exts_exec include/net/pkt_cls.h:326 [inline]
     route4_classify+0xef0/0x1400 net/sched/cls_route.c:179
     __tcf_classify net/sched/cls_api.c:1549 [inline]
     tcf_classify+0x3e8/0x9d0 net/sched/cls_api.c:1615
     prio_classify net/sched/sch_prio.c:42 [inline]
     prio_enqueue+0x3a7/0x790 net/sched/sch_prio.c:75
     dev_qdisc_enqueue+0x40/0x300 net/core/dev.c:3668
     __dev_xmit_skb net/core/dev.c:3756 [inline]
     __dev_queue_xmit+0x1f61/0x3660 net/core/dev.c:4081
     neigh_hh_output include/net/neighbour.h:533 [inline]
     neigh_output include/net/neighbour.h:547 [inline]
     ip_finish_output2+0x14dc/0x2170 net/ipv4/ip_output.c:228
     __ip_finish_output net/ipv4/ip_output.c:306 [inline]
     __ip_finish_output+0x396/0x650 net/ipv4/ip_output.c:288
     ip_finish_output+0x32/0x200 net/ipv4/ip_output.c:316
     NF_HOOK_COND include/linux/netfilter.h:296 [inline]
     ip_output+0x196/0x310 net/ipv4/ip_output.c:430
     dst_output include/net/dst.h:451 [inline]
     ip_local_out+0xaf/0x1a0 net/ipv4/ip_output.c:126
     iptunnel_xmit+0x628/0xa50 net/ipv4/ip_tunnel_core.c:82
     geneve_xmit_skb drivers/net/geneve.c:966 [inline]
     geneve_xmit+0x10c8/0x3530 drivers/net/geneve.c:1077
     __netdev_start_xmit include/linux/netdevice.h:4683 [inline]
     netdev_start_xmit include/linux/netdevice.h:4697 [inline]
     xmit_one net/core/dev.c:3473 [inline]
     dev_hard_start_xmit+0x1eb/0x920 net/core/dev.c:3489
     __dev_queue_xmit+0x2985/0x3660 net/core/dev.c:4116
     neigh_hh_output include/net/neighbour.h:533 [inline]
     neigh_output include/net/neighbour.h:547 [inline]
     ip6_finish_output2+0xf7a/0x14f0 net/ipv6/ip6_output.c:126
     __ip6_finish_output net/ipv6/ip6_output.c:191 [inline]
     __ip6_finish_output+0x61e/0xe90 net/ipv6/ip6_output.c:170
     ip6_finish_output+0x32/0x200 net/ipv6/ip6_output.c:201
     NF_HOOK_COND include/linux/netfilter.h:296 [inline]
     ip6_output+0x1e4/0x530 net/ipv6/ip6_output.c:224
     dst_output include/net/dst.h:451 [inline]
     NF_HOOK include/linux/netfilter.h:307 [inline]
     NF_HOOK include/linux/netfilter.h:301 [inline]
     mld_sendpack+0x9a3/0xe40 net/ipv6/mcast.c:1826
     mld_send_cr net/ipv6/mcast.c:2127 [inline]
     mld_ifc_work+0x71c/0xdc0 net/ipv6/mcast.c:2659
     process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307
     worker_thread+0x657/0x1110 kernel/workqueue.c:2454
     kthread+0x2e9/0x3a0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
     </TASK>
    ----------------
    Code disassembly (best guess):
       0:   48 89 eb                mov    %rbp,%rbx
       3:   c6 45 01 01             movb   $0x1,0x1(%rbp)
       7:   41 bc 00 80 00 00       mov    $0x8000,%r12d
       d:   48 c1 e9 03             shr    $0x3,%rcx
      11:   83 e3 07                and    $0x7,%ebx
      14:   41 be 01 00 00 00       mov    $0x1,%r14d
      1a:   48 b8 00 00 00 00 00    movabs $0xdffffc0000000000,%rax
      21:   fc ff df
      24:   4c 8d 2c 01             lea    (%rcx,%rax,1),%r13
      28:   eb 0c                   jmp    0x36
    * 2a:   f3 90                   pause <-- trapping instruction
      2c:   41 83 ec 01             sub    $0x1,%r12d
      30:   0f 84 72 04 00 00       je     0x4a8
      36:   41 0f b6 45 00          movzbl 0x0(%r13),%eax
      3b:   38 d8                   cmp    %bl,%al
      3d:   7f 08                   jg     0x47
      3f:   84                      .byte 0x84
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
    Cc: Cong Wang <xiyou.wangcong@gmail.com>
    Cc: Jiri Pirko <jiri@resnulli.us>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220215235305.3272331-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c08e58438d4a709fb451b6d7d33432cc9907a2a8
Author: Jon Maloy <jmaloy@redhat.com>
Date:   Tue Feb 15 21:00:09 2022 -0500

    tipc: fix wrong notification node addresses
    
    The previous bug fix had an unfortunate side effect that broke
    distribution of binding table entries between nodes. The updated
    tipc_sock_addr struct is also used further down in the same
    function, and there the old value is still the correct one.
    
    Fixes: 032062f363b4 ("tipc: fix wrong publisher node address in link publications")
    Signed-off-by: Jon Maloy <jmaloy@redhat.com>
    Link: https://lore.kernel.org/r/20220216020009.3404578-1-jmaloy@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8c6ae46150a453f8ae9a6cd49b45f354f478587d
Author: Alexey Khoroshilov <khoroshilov@ispras.ru>
Date:   Tue Feb 15 13:42:48 2022 +0300

    net: dsa: lantiq_gswip: fix use after free in gswip_remove()
    
    of_node_put(priv->ds->slave_mii_bus->dev.of_node) should be
    done before mdiobus_free(priv->ds->slave_mii_bus).
    
    Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
    Fixes: 0d120dfb5d67 ("net: dsa: lantiq_gswip: don't use devres for mdiobus")
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/1644921768-26477-1-git-send-email-khoroshilov@ispras.ru
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0b0dff5b3b98c5c7ce848151df9da0b3cdf0cc8b
Author: Willem de Bruijn <willemb@google.com>
Date:   Tue Feb 15 11:00:37 2022 -0500

    ipv6: per-netns exclusive flowlabel checks
    
    Ipv6 flowlabels historically require a reservation before use.
    Optionally in exclusive mode (e.g., user-private).
    
    Commit 59c820b2317f ("ipv6: elide flowlabel check if no exclusive
    leases exist") introduced a fastpath that avoids this check when no
    exclusive leases exist in the system, and thus any flowlabel use
    will be granted.
    
    That allows skipping the control operation to reserve a flowlabel
    entirely. Though with a warning if the fast path fails:
    
      This is an optimization. Robust applications still have to revert to
      requesting leases if the fast path fails due to an exclusive lease.
    
    Still, this is subtle. Better isolate network namespaces from each
    other. Flowlabels are per-netns. Also record per-netns whether
    exclusive leases are in use. Then behavior does not change based on
    activity in other netns.
    
    Changes
      v2
        - wrap in IS_ENABLED(CONFIG_IPV6) to avoid breakage if disabled
    
    Fixes: 59c820b2317f ("ipv6: elide flowlabel check if no exclusive leases exist")
    Link: https://lore.kernel.org/netdev/MWHPR2201MB1072BCCCFCE779E4094837ACD0329@MWHPR2201MB1072.namprd22.prod.outlook.com/
    Reported-by: Congyu Liu <liu3101@purdue.edu>
    Signed-off-by: Willem de Bruijn <willemb@google.com>
    Tested-by: Congyu Liu <liu3101@purdue.edu>
    Link: https://lore.kernel.org/r/20220215160037.1976072-1-willemdebruijn.kernel@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c832962ac972082b3a1f89775c9d4274c8cb5670
Author: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
Date:   Tue Feb 15 18:53:03 2022 +0200

    net: bridge: multicast: notify switchdev driver whenever MC processing gets disabled
    
    Whenever bridge driver hits the max capacity of MDBs, it disables
    the MC processing (by setting corresponding bridge option), but never
    notifies switchdev about such change (the notifiers are called only upon
    explicit setting of this option, through the registered netlink interface).
    
    This could lead to situation when Software MDB processing gets disabled,
    but this event never gets offloaded to the underlying Hardware.
    
    Fix this by adding a notify message in such case.
    
    Fixes: 147c1e9b902c ("switchdev: bridge: Offload multicast disabled")
    Signed-off-by: Oleksandr Mazur <oleksandr.mazur@plvision.eu>
    Acked-by: Nikolay Aleksandrov <nikolay@nvidia.com>
    Link: https://lore.kernel.org/r/20220215165303.31908-1-oleksandr.mazur@plvision.eu
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 53923e0fe2098f90f339510aeaa0e1413ae99a16
Author: Steve French <stfrench@microsoft.com>
Date:   Wed Feb 16 13:23:53 2022 -0600

    cifs: fix confusing unneeded warning message on smb2.1 and earlier
    
    When mounting with SMB2.1 or earlier, even with nomultichannel, we
    log the confusing warning message:
      "CIFS: VFS: multichannel is not supported on this protocol version, use 3.0 or above"
    
    Fix this so that we don't log this unless they really are trying
    to mount with multichannel.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215608
    Reported-by: Kim Scarborough <kim@scarborough.kim>
    Cc: stable@vger.kernel.org # 5.11+
    Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit a8e8f851e8299703a005cf23dfb9ec854a2611e5
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Tue Feb 15 13:11:42 2022 -0800

    module: fix building with sysfs disabled
    
    Sysfs support might be disabled so we need to guard the code that
    instantiates "compression" attribute with an #ifdef.
    
    Fixes: b1ae6dc41eaa ("module: add in-kernel support for decompressing")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit 45ce4b4f9009102cd9f581196d480a59208690c1
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date:   Thu Feb 17 01:49:43 2022 +0530

    bpf: Fix crash due to out of bounds access into reg2btf_ids.
    
    When commit e6ac2450d6de ("bpf: Support bpf program calling kernel function") added
    kfunc support, it defined reg2btf_ids as a cheap way to translate the verifier
    reg type to the appropriate btf_vmlinux BTF ID, however
    commit c25b2ae13603 ("bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL")
    moved the __BPF_REG_TYPE_MAX from the last member of bpf_reg_type enum to after
    the base register types, and defined other variants using type flag
    composition. However, now, the direct usage of reg->type to index into
    reg2btf_ids may no longer fall into __BPF_REG_TYPE_MAX range, and hence lead to
    out of bounds access and kernel crash on dereference of bad pointer.
    
    Fixes: c25b2ae13603 ("bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL")
    Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220216201943.624869-1-memxor@gmail.com

commit d19e0183a88306acda07f4a01fedeeffe2a2a06b
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Tue Feb 15 18:05:18 2022 -0500

    NFS: Do not report writeback errors in nfs_getattr()
    
    The result of the writeback, whether it is an ENOSPC or an EIO, or
    anything else, does not inhibit the NFS client from reporting the
    correct file timestamps.
    
    Fixes: 79566ef018f5 ("NFS: Getattr doesn't require data sync semantics")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit f71077a4d84bbe8c7b91b7db7c4ef815755ac5e3
Merge: 3593030761630 54309fde1a352
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 16 12:09:22 2022 -0800

    Merge tag 'mmc-v5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
    
    Pull MMC fix from Ulf Hansson:
     "Fix recovery logic for multi block I/O reads (MMC_READ_MULTIPLE_BLOCK)"
    
    * tag 'mmc-v5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc:
      mmc: block: fix read single on recovery logic

commit f2703def339c793674010cc9f01bfe4980231808
Author: Alexander Lobakin <alobakin@pm.me>
Date:   Sat Feb 12 22:21:11 2022 +0000

    MIPS: smp: fill in sibling and core maps earlier
    
    After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle),
    2-core 2-thread-per-core interAptiv (CPS-driven) started emitting
    the following:
    
    [    0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi))
    [    0.048183] ------------[ cut here ]------------
    [    0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240
    [    0.048220] Modules linked in:
    [    0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f
    [    0.048247] Stack : 817f0000 00000004 327804c8 810eb050 00000000 00000004 00000000 c314fdd1
    [    0.048278]         830cbd64 819c0000 81800000 817f0000 83070bf4 00000001 830cbd08 00000000
    [    0.048307]         00000000 00000000 815fcbc4 00000000 00000000 00000000 00000000 00000000
    [    0.048334]         00000000 00000000 00000000 00000000 817f0000 00000000 00000000 817f6f34
    [    0.048361]         817f0000 818a3c00 817f0000 00000004 00000000 00000000 4dc33260 0018c933
    [    0.048389]         ...
    [    0.048396] Call Trace:
    [    0.048399] [<8105a7bc>] show_stack+0x3c/0x140
    [    0.048424] [<8131c2a0>] dump_stack_lvl+0x60/0x80
    [    0.048440] [<8108b5c0>] __warn+0xc0/0xf4
    [    0.048454] [<8108b658>] warn_slowpath_fmt+0x64/0x10c
    [    0.048467] [<810bd418>] sched_core_cpu_starting+0x198/0x240
    [    0.048483] [<810c6514>] sched_cpu_starting+0x14/0x80
    [    0.048497] [<8108c0f8>] cpuhp_invoke_callback_range+0x78/0x140
    [    0.048510] [<8108d914>] notify_cpu_starting+0x94/0x140
    [    0.048523] [<8106593c>] start_secondary+0xbc/0x280
    [    0.048539]
    [    0.048543] ---[ end trace 0000000000000000 ]---
    [    0.048636] Synchronize counters for CPU 1: done.
    
    ...for each but CPU 0/boot.
    Basic debug printks right before the mentioned line say:
    
    [    0.048170] CPU: 1, smt_mask:
    
    So smt_mask, which is sibling mask obviously, is empty when entering
    the function.
    This is critical, as sched_core_cpu_starting() calculates
    core-scheduling parameters only once per CPU start, and it's crucial
    to have all the parameters filled in at that moment (at least it
    uses cpu_smt_mask() which in fact is `&cpu_sibling_map[cpu]` on
    MIPS).
    
    A bit of debugging led me to that set_cpu_sibling_map() performing
    the actual map calculation, was being invocated after
    notify_cpu_start(), and exactly the latter function starts CPU HP
    callback round (sched_core_cpu_starting() is basically a CPU HP
    callback).
    While the flow is same on ARM64 (maps after the notifier, although
    before calling set_cpu_online()), x86 started calculating sibling
    maps earlier than starting the CPU HP callbacks in Linux 4.14 (see
    [0] for the reference). Neither me nor my brief tests couldn't find
    any potential caveats in calculating the maps right after performing
    delay calibration, but the WARN splat is now gone.
    The very same debug prints now yield exactly what I expected from
    them:
    
    [    0.048433] CPU: 1, smt_mask: 0-1
    
    [0] https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=76ce7cfe35ef
    
    Signed-off-by: Alexander Lobakin <alobakin@pm.me>
    Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit cc19db8b312a6c75645645f5cc1b45166b109006
Author: Chuanhong Guo <gch981213@gmail.com>
Date:   Fri Feb 11 08:13:44 2022 +0800

    MIPS: ralink: mt7621: do memory detection on KSEG1
    
    It's reported that current memory detection code occasionally detects
    larger memory under some bootloaders.
    Current memory detection code tests whether address space wraps around
    on KSEG0, which is unreliable because it's cached.
    
    Rewrite memory size detection to perform the same test on KSEG1 instead.
    While at it, this patch also does the following two things:
    1. use a fixed pattern instead of a random function pointer as the magic
       value.
    2. add an additional memory write and a second comparison as part of the
       test to prevent possible smaller memory detection result due to
       leftover values in memory.
    
    Fixes: 139c949f7f0a MIPS: ("ralink: mt7621: add memory detection support")
    Reported-by: Rui Salvaterra <rsalvaterra@gmail.com>
    Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
    Tested-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Tested-by: Rui Salvaterra <rsalvaterra@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 3593030761630e09200072a4bd06468892c27be3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 15:28:00 2022 -0800

    tty: n_tty: do not look ahead for EOL character past the end of the buffer
    
    Daniel Gibson reports that the n_tty code gets line termination wrong in
    very specific cases:
    
     "If you feed a line with exactly 64 chars + terminating newline, and
      directly afterwards (without reading) another line into a pseudo
      terminal, the the first read() on the other side will return the 64
      char line *without* terminating newline, and the next read() will
      return the missing terminating newline AND the complete next line (if
      it fits in the buffer)"
    
    and bisected the behavior to commit 3b830a9c34d5 ("tty: convert
    tty_ldisc_ops 'read()' function to take a kernel pointer").
    
    Now, digging deeper, it turns out that the behavior isn't exactly new:
    what changed in commit 3b830a9c34d5 was that the tty line discipline
    .read() function is now passed an intermediate kernel buffer rather than
    the final user space buffer.
    
    And that intermediate kernel buffer is 64 bytes in size - thus that
    special case with exactly 64 bytes plus terminating newline.
    
    The same problem did exist before, but historically the boundary was not
    the 64-byte chunk, but the user-supplied buffer size, which is obviously
    generally bigger (and potentially bigger than N_TTY_BUF_SIZE, which
    would hide the issue entirely).
    
    The reason is that the n_tty canon_copy_from_read_buf() code would look
    ahead for the EOL character one byte further than it would actually
    copy.  It would then decide that it had found the terminator, and unmark
    it as an EOL character - which in turn explains why the next read
    wouldn't then be terminated by it.
    
    Now, the reason it did all this in the first place is related to some
    historical and pretty obscure EOF behavior, see commit ac8f3bf8832a
    ("n_tty: Fix poll() after buffer-limited eof push read") and commit
    40d5e0905a03 ("n_tty: Fix EOF push handling").
    
    And the reason for the EOL confusion is that we treat EOF as a special
    EOL condition, with the EOL character being NUL (aka "__DISABLED_CHAR"
    in the kernel sources).
    
    So that EOF look-ahead also affects the normal EOL handling.
    
    This patch just removes the look-ahead that causes problems, because EOL
    is much more critical than the historical "EOF in the middle of a line
    that coincides with the end of the buffer" handling ever was.
    
    Now, it is possible that we should indeed re-introduce the "look at next
    character to see if it's a EOF" behavior, but if so, that should be done
    not at the kernel buffer chunk boundary in canon_copy_from_read_buf(),
    but at a higher level, when we run out of the user buffer.
    
    In particular, the place to do that would be at the top of
    'n_tty_read()', where we check if it's a continuation of a previously
    started read, and there is no more buffer space left, we could decide to
    just eat the __DISABLED_CHAR at that point.
    
    But that would be a separate patch, because I suspect nobody actually
    cares, and I'd like to get a report about it before bothering.
    
    Fixes: 3b830a9c34d5 ("tty: convert tty_ldisc_ops 'read()' function to take a kernel pointer")
    Fixes: ac8f3bf8832a ("n_tty: Fix  poll() after buffer-limited eof push read")
    Fixes: 40d5e0905a03 ("n_tty: Fix EOF push handling")
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215611
    Reported-and-tested-by: Daniel Gibson <metalcaedes@gmail.com>
    Cc: Peter Hurley <peter@hurleysoftware.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bfe55a1f7fd6bfede16078bf04c6250fbca11588
Author: Woody Suwalski <wsuwalski@gmail.com>
Date:   Wed Feb 9 16:05:09 2022 -0500

    ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
    
    Add and ACPI idle power level limit for 32-bit ThinkPad T40.
    
    There is a regression on T40 introduced by commit d6b88ce2, starting
    with kernel 5.16:
    
    commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
    Author: Richard Gong <richard.gong@amd.com>
    Date:   Wed Sep 22 08:31:16 2021 -0500
    
      ACPI: processor idle: Allow playing dead in C3 state
    
    The above patch is trying to enter C3 state during init, what is causing
    a T40 system freeze. I have not found a similar issue on any other of my
    32-bit machines.
    
    The fix is to add another exception to the processor_power_dmi_table[] list.
    As a result the dmesg shows as expected:
    
    [2.155398] ACPI: IBM ThinkPad T40 detected - limiting to C2 max_cstate. Override with "processor.max_cstate=9"
    [2.155404] ACPI: processor limited to max C-state 2
    
    The fix is trivial and affects only vintage T40 systems.
    
    Fixes: d6b88ce2eb9d ("CPI: processor idle: Allow playing dead in C3 state")
    Signed-off-by: Woody Suwalski <wsuwalski@gmail.com>
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Cc: 5.16+ <stable@vger.kernel.org> # 5.16+
    [ rjw: New subject ]
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 047e6032c4f054372311eb20c759cfe0b3ca7ffe
Author: German Gomez <german.gomez@arm.com>
Date:   Tue Jan 25 10:44:34 2022 +0000

    perf test: Fix arm64 perf_event_attr tests wrt --call-graph initialization
    
    The struct perf_event_attr is initialised differently in Arm64 when
    recording in call-graph fp mode, so update the relevant tests, and add
    two extra arm64-only tests.
    
    Before:
    
      $ perf test 17 -v
      17: Setup struct perf_event_attr
      [...]
      running './tests/attr/test-record-graph-default'
      expected sample_type=295, got 4391
      expected sample_regs_user=0, got 1073741824
      FAILED './tests/attr/test-record-graph-default' - match failure
      test child finished with -1
      ---- end ----
    
    After:
    
    [...]
      running './tests/attr/test-record-graph-default-aarch64'
      test limitation 'aarch64'
      running './tests/attr/test-record-graph-fp-aarch64'
      test limitation 'aarch64'
      running './tests/attr/test-record-graph-default'
      test limitation '!aarch64'
      excluded architecture list ['aarch64']
      skipped [aarch64] './tests/attr/test-record-graph-default'
      running './tests/attr/test-record-graph-fp'
      test limitation '!aarch64'
      excluded architecture list ['aarch64']
      skipped [aarch64] './tests/attr/test-record-graph-fp'
    [...]
    
    Fixes: 7248e308a5758761 ("perf tools: Record ARM64 LR register automatically")
    Signed-off-by: German Gomez <german.gomez@arm.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexandre Truong <alexandre.truong@arm.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Fastabend <john.fastabend@gmail.com>
    Cc: KP Singh <kpsingh@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Martin KaFai Lau <kafai@fb.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Song Liu <songliubraving@fb.com>
    Cc: Yonghong Song <yhs@fb.com>
    Link: http://lore.kernel.org/lkml/20220125104435.2737-1-german.gomez@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 52a9dab6d892763b2a8334a568bd4e2c1a6fde66
Author: Kees Cook <keescook@chromium.org>
Date:   Sun Feb 13 10:24:43 2022 -0800

    libsubcmd: Fix use-after-free for realloc(..., 0)
    
    GCC 12 correctly reports a potential use-after-free condition in the
    xrealloc helper. Fix the warning by avoiding an implicit "free(ptr)"
    when size == 0:
    
    In file included from help.c:12:
    In function 'xrealloc',
        inlined from 'add_cmdname' at help.c:24:2: subcmd-util.h:56:23: error: pointer may be used after 'realloc' [-Werror=use-after-free]
       56 |                 ret = realloc(ptr, size);
          |                       ^~~~~~~~~~~~~~~~~~
    subcmd-util.h:52:21: note: call to 'realloc' here
       52 |         void *ret = realloc(ptr, size);
          |                     ^~~~~~~~~~~~~~~~~~
    subcmd-util.h:58:31: error: pointer may be used after 'realloc' [-Werror=use-after-free]
       58 |                         ret = realloc(ptr, 1);
          |                               ^~~~~~~~~~~~~~~
    subcmd-util.h:52:21: note: call to 'realloc' here
       52 |         void *ret = realloc(ptr, size);
          |                     ^~~~~~~~~~~~~~~~~~
    
    Fixes: 2f4ce5ec1d447beb ("perf tools: Finalize subcmd independence")
    Reported-by: Valdis Klētnieks <valdis.kletnieks@vt.edu>
    Signed-off-by: Kees Kook <keescook@chromium.org>
    Tested-by: Valdis Klētnieks <valdis.kletnieks@vt.edu>
    Tested-by: Justin M. Forbes <jforbes@fedoraproject.org>
    Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Cc: linux-hardening@vger.kernel.org
    Cc: Valdis Klētnieks <valdis.kletnieks@vt.edu>
    Link: http://lore.kernel.org/lkml/20220213182443.4037039-1-keescook@chromium.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 30d1c4d947983f3cfbff9cbb7a4d69b05b699678
Author: Jiri Olsa <jolsa@kernel.org>
Date:   Tue Feb 15 16:37:13 2022 +0100

    libperf: Fix perf_cpu_map__for_each_cpu macro
    
    Tzvetomir Stoyanov reported an issue with using macro
    perf_cpu_map__for_each_cpu using private perf_cpu object.
    
    The issue is caused by recent change that wrapped cpu in struct perf_cpu
    to distinguish it from cpu indexes. We need to make struct perf_cpu
    public.
    
    Add a simple test for using the perf_cpu_map__for_each_cpu macro.
    
    Fixes: 6d18804b963b78dc ("perf cpumap: Give CPUs their own type")
    Reported-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
    Signed-off-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20220215153713.31395-1-jolsa@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 9de0736973dd7f0f710d0f5e0a3dfd9fa9ffeb3f
Author: James Clark <james.clark@arm.com>
Date:   Thu Feb 10 20:06:20 2022 +0000

    perf cs-etm: Fix corrupt inject files when only last branch option is enabled
    
    'perf inject' with Coresight data generates files that cannot be opened
    when only the last branch option is specified:
    
      perf inject -i perf.data --itrace=l -o inject.data
      perf script -i inject.data
      0x33faa8 [0x8]: failed to process type: 9 [Bad address]
    
    This is because cs_etm__synth_instruction_sample() is called even when
    the sample type for instructions hasn't been setup. Last branch records
    are attached to instruction samples so it doesn't make sense to generate
    them when --itrace=i isn't specified anyway.
    
    This change disables all calls of cs_etm__synth_instruction_sample()
    unless --itrace=i is specified, resulting in a file with no samples if
    only --itrace=l is provided, rather than a bad file.
    
    Reviewed-by: Leo Yan <leo.yan@linaro.org>
    Signed-off-by: James Clark <james.clark@arm.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Will Deacon <will@kernel.org>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Link: https://lore.kernel.org/r/20220210200620.1227232-2-james.clark@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 0b31ea6613ad1e6b9b84d877c1be18e39934e90a
Author: James Clark <james.clark@arm.com>
Date:   Thu Feb 10 20:06:19 2022 +0000

    perf cs-etm: No-op refactor of synth opt usage
    
    sample_branches and sample_instructions are already saved in the
    synth_opts struct. Other usages like synth_opts.last_branch don't save a
    value, so make this more consistent by always going through synth_opts
    and not saving duplicate values.
    
    Reviewed-by: Leo Yan <leo.yan@linaro.org>
    Signed-off-by: James Clark <james.clark@arm.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Will Deacon <will@kernel.org>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Link: https://lore.kernel.org/r/20220210200620.1227232-1-james.clark@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 096972f5588dbac741f7f0cc057c84d895d4d80f
Author: Rob Herring <robh@kernel.org>
Date:   Tue Feb 1 15:39:03 2022 -0600

    libperf: Fix 32-bit build for tests uint64_t printf
    
    Commit a7f3713f6bf207e6 ("libperf tests: Add test_stat_multiplexing test")
    added printf's of 64-bit ints using %lu which doesn't work on 32-bit
    builds:
    
      tests/test-evlist.c:529:29: error: format ‘%lu’ expects argument of type \
        ‘long unsigned int’, but argument 4 has type ‘uint64_t’ {aka ‘long long unsigned int’} [-Werror=format=]
    
    Use PRIu64 instead which works on both 32-bit and 64-bit systems.
    
    Fixes: a7f3713f6bf207e6 ("libperf tests: Add test_stat_multiplexing test")
    Signed-off-by: Rob Herring <robh@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
    Link: https://lore.kernel.org/r/20220201213903.699656-1-robh@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 714b8b7131f9287b1ff6c0528accd5df585b30d3
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Fri May 21 16:00:31 2021 -0300

    tools headers UAPI: Sync linux/perf_event.h with the kernel sources
    
    To pick the trivial change in:
    
      ddecd22878601a60 ("perf: uapi: Document perf_event_attr::sig_data truncation on 32 bit architectures")
    
    Just adds a comment.
    
    This silences this perf build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/linux/perf_event.h' differs from latest version at 'include/uapi/linux/perf_event.h'
      diff -u tools/include/uapi/linux/perf_event.h include/uapi/linux/perf_event.h
    
    Cc: Marco Elver <elver@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/lkml/
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit de9f498d2b381de1abf654ca3459c4f01227b5cd
Author: Changbin Du <changbin.du@intel.com>
Date:   Tue Feb 8 22:07:25 2022 +0800

    perf trace: Avoid early exit due SIGCHLD from non-workload processes
    
    The function trace__symbols_init() runs "perf-read-vdso32" and that ends up
    with a SIGCHLD delivered to 'perf'. And this SIGCHLD make perf exit early.
    
    'perf trace' should exit only if the SIGCHLD is from our workload process.
    So let's use sigaction() instead of signal() to match such condition.
    
    Committer notes:
    
    Use memset to zero the 'struct sigaction' variable as the '= { 0 }'
    method isn't accepted in many compiler versions, e.g.:
    
       4    34.02 alpine:3.6                    : FAIL clang version 4.0.0 (tags/RELEASE_400/final)
        builtin-trace.c:4897:35: error: suggest braces around initialization of subobject [-Werror,-Wmissing-braces]
                struct sigaction sigchld_act = { 0 };
                                                 ^
                                                 {}
        builtin-trace.c:4897:37: error: missing field 'sa_mask' initializer [-Werror,-Wmissing-field-initializers]
                struct sigaction sigchld_act = { 0 };
                                                   ^
        2 errors generated.
       6    32.60 alpine:3.8                    : FAIL gcc version 6.4.0 (Alpine 6.4.0)
        builtin-trace.c:4897:35: error: suggest braces around initialization of subobject [-Werror,-Wmissing-braces]
                struct sigaction sigchld_act = { 0 };
                                                 ^
                                                 {}
        builtin-trace.c:4897:37: error: missing field 'sa_mask' initializer [-Werror,-Wmissing-field-initializers]
                struct sigaction sigchld_act = { 0 };
                                                   ^
        2 errors generated.
       7    34.82 alpine:3.9                    : FAIL gcc version 8.3.0 (Alpine 8.3.0)
        builtin-trace.c:4897:35: error: suggest braces around initialization of subobject [-Werror,-Wmissing-braces]
                struct sigaction sigchld_act = { 0 };
                                                 ^
                                                 {}
        builtin-trace.c:4897:37: error: missing field 'sa_mask' initializer [-Werror,-Wmissing-field-initializers]
                struct sigaction sigchld_act = { 0 };
                                                   ^
        2 errors generated.
    
    Signed-off-by: Changbin Du <changbin.du@gmail.com>
    Acked-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20220208140725.3947-1-changbin.du@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit c5487b9cdea5c1ede38a7ec94db0fc59963c8e86
Author: Fabio Estevam <festevam@denx.de>
Date:   Tue Feb 15 09:05:14 2022 -0300

    ASoC: cs4265: Fix the duplicated control name
    
    Currently, the following error messages are seen during boot:
    
    asoc-simple-card sound: control 2:0:0:SPDIF Switch:0 is already present
    cs4265 1-004f: ASoC: failed to add widget SPDIF dapm kcontrol SPDIF Switch: -16
    
    Quoting Mark Brown:
    
    "The driver is just plain buggy, it defines both a regular SPIDF Switch
    control and a SND_SOC_DAPM_SWITCH() called SPDIF both of which will
    create an identically named control, it can never have loaded without
    error.  One or both of those has to be renamed or they need to be
    merged into one thing."
    
    Fix the duplicated control name by combining the two SPDIF controls here
    and move the register bits onto the DAPM widget and have DAPM control them.
    
    Fixes: f853d6b3ba34 ("ASoC: cs4265: Add a S/PDIF enable switch")
    Signed-off-by: Fabio Estevam <festevam@denx.de>
    Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220215120514.1760628-1-festevam@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 9bdd10d57a8807dba0003af0325191f3cec0f11c
Author: Marek Vasut <marex@denx.de>
Date:   Tue Feb 15 14:06:45 2022 +0100

    ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min
    
    While the $val/$val2 values passed in from userspace are always >= 0
    integers, the limits of the control can be signed integers and the $min
    can be non-zero and less than zero. To correctly validate $val/$val2
    against platform_max, add the $min offset to val first.
    
    Fixes: 817f7c9335ec0 ("ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()")
    Signed-off-by: Marek Vasut <marex@denx.de>
    Cc: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220215130645.164025-1-marex@denx.de
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 184b58fa816fb5ee1854daf0d430766422bf2a77
Author: Mikko Perttunen <mperttunen@nvidia.com>
Date:   Mon Feb 7 15:19:31 2022 +0200

    gpu: host1x: Always return syncpoint value when waiting
    
    The new TegraDRM UAPI uses syncpoint waiting with timeout set to
    zero to indicate reading the syncpoint value. To support that we
    need to return the syncpoint value always when waiting.
    
    Fixes: 44e961381354 ("drm/tegra: Implement syncpoint wait UAPI")
    Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit 0a5a587501b54e8c6d86960b047d4491fd40dcf2
Author: Michael Hübner <michaelh.95@t-online.de>
Date:   Thu Jan 20 08:40:48 2022 +0100

    HID: Add support for open wheel and no attachment to T300
    
    Different add ons to the wheel base report different models. Having
    no wheel mounted to the base and using the open wheel attachment is
    added here.
    
    Signed-off-by: Michael Hübner <michaelh.95@t-online.de>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 25666e8ccd952627899b09b68f7c9b68cfeaf028
Author: Lucas Zampieri <lzampier@redhat.com>
Date:   Wed Jan 26 11:44:00 2022 -0300

    HID: logitech-dj: add new lightspeed receiver id
    
    As of logitech lightspeed receiver fw version 04.02.B0009,
    HIDPP_PARAM_DEVICE_INFO is being reported as 0x11.
    
    With patch "HID: logitech-dj: add support for the new lightspeed receiver
    iteration", the mouse starts to error out with:
      logitech-djreceiver: unusable device of type UNKNOWN (0x011) connected on
      slot 1
    and becomes unusable.
    
    This has been noticed on a Logitech G Pro X Superlight fw MPM 25.01.B0018.
    
    Signed-off-by: Lucas Zampieri <lzampier@redhat.com>
    Acked-by: Nestor Lopez Casado <nlopezcasad@logitech.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 7920af5c826cb4a7ada1ae26fdd317642805adc2
Author: Samuel Holland <samuel@sholland.org>
Date:   Sat Feb 12 14:50:48 2022 -0600

    gpio: rockchip: Reset int_bothedge when changing trigger
    
    With v2 hardware, an IRQ can be configured to trigger on both edges via
    a bit in the int_bothedge register. Currently, the driver sets this bit
    when changing the trigger type to IRQ_TYPE_EDGE_BOTH, but fails to reset
    this bit if the trigger type is later changed to something else. This
    causes spurious IRQs, and when using gpio-keys with wakeup-event-action
    set to EV_ACT_(DE)ASSERTED, those IRQs translate into spurious wakeups.
    
    Fixes: 3bcbd1a85b68 ("gpio/rockchip: support next version gpio controller")
    Reported-by: Guillaume Savaton <guillaume@baierouge.fr>
    Tested-by: Guillaume Savaton <guillaume@baierouge.fr>
    Signed-off-by: Samuel Holland <samuel@sholland.org>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 859ae7018316daa4adbc496012dcbbb458d7e510
Author: Nicolas Escande <nico.escande@gmail.com>
Date:   Mon Feb 14 18:32:14 2022 +0100

    mac80211: fix forwarded mesh frames AC & queue selection
    
    There are two problems with the current code that have been highlighted
    with the AQL feature that is now enbaled by default.
    
    First problem is in ieee80211_rx_h_mesh_fwding(),
    ieee80211_select_queue_80211() is used on received packets to choose
    the sending AC queue of the forwarding packet although this function
    should only be called on TX packet (it uses ieee80211_tx_info).
    This ends with forwarded mesh packets been sent on unrelated random AC
    queue. To fix that, AC queue can directly be infered from skb->priority
    which has been extracted from QOS info (see ieee80211_parse_qos()).
    
    Second problem is the value of queue_mapping set on forwarded mesh
    frames via skb_set_queue_mapping() is not the AC of the packet but a
    hardware queue index. This may or may not work depending on AC to HW
    queue mapping which is driver specific.
    
    Both of these issues lead to improper AC selection while forwarding
    mesh packets but more importantly due to improper airtime accounting
    (which is done on a per STA, per AC basis) caused traffic stall with
    the introduction of AQL.
    
    Fixes: cf44012810cc ("mac80211: fix unnecessary frame drops in mesh fwding")
    Fixes: d3c1597b8d1b ("mac80211: fix forwarded mesh frame queue mapping")
    Co-developed-by: Remi Pommarel <repk@triplefau.lt>
    Signed-off-by: Remi Pommarel <repk@triplefau.lt>
    Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
    Link: https://lore.kernel.org/r/20220214173214.368862-1-nico.escande@gmail.com
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit a6bce78262f5dd4b50510f0aa47f3995f7b185f3
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Thu Feb 3 20:15:29 2022 +0100

    mac80211: refuse aggregations sessions before authorized
    
    If an MFP station isn't authorized, the receiver will (or
    at least should) drop the action frame since it's a robust
    management frame, but if we're not authorized we haven't
    installed keys yet. Refuse attempts to start a session as
    they'd just time out.
    
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Link: https://lore.kernel.org/r/20220203201528.ff4d5679dce9.I34bb1f2bc341e161af2d6faf74f91b332ba11285@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 610d086d6df0b15c3732a7b4a5b0f1c3e1b84d4c
Author: Deren Wu <deren.wu@mediatek.com>
Date:   Sun Feb 13 00:20:15 2022 +0800

    mac80211: fix EAPoL rekey fail in 802.3 rx path
    
    mac80211 set capability NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211
    to upper layer by default. That means we should pass EAPoL packets through
    nl80211 path only, and should not send the EAPoL skb to netdevice diretly.
    At the meanwhile, wpa_supplicant would not register sock to listen EAPoL
    skb on the netdevice.
    
    However, there is no control_port_protocol handler in mac80211 for 802.3 RX
    packets, mac80211 driver would pass up the EAPoL rekey frame to netdevice
    and wpa_supplicant would be never interactive with this kind of packets,
    if SUPPORTS_RX_DECAP_OFFLOAD is enabled. This causes STA always rekey fail
    if EAPoL frame go through 802.3 path.
    
    To avoid this problem, align the same process as 802.11 type to handle
    this frame before put it into network stack.
    
    This also addresses a potential security issue in 802.3 RX mode that was
    previously fixed in commit a8c4d76a8dd4 ("mac80211: do not accept/forward
    invalid EAPOL frames").
    
    Cc: stable@vger.kernel.org # 5.12+
    Fixes: 80a915ec4427 ("mac80211: add rx decapsulation offload support")
    Signed-off-by: Deren Wu <deren.wu@mediatek.com>
    Link: https://lore.kernel.org/r/6889c9fced5859ebb088564035f84fd0fa792a49.1644680751.git.deren.wu@mediatek.com
    [fix typos, update comment and add note about security issue]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit dee435be76f4117410bbd90573a881fd33488f37
Author: James Morse <james.morse@arm.com>
Date:   Tue Feb 8 16:08:13 2022 +0000

    arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of Spectre-v2
    
    Speculation attacks against some high-performance processors can
    make use of branch history to influence future speculation as part of
    a spectre-v2 attack. This is not mitigated by CSV2, meaning CPUs that
    previously reported 'Not affected' are now moderately mitigated by CSV2.
    
    Update the value in /sys/devices/system/cpu/vulnerabilities/spectre_v2
    to also show the state of the BHB mitigation.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit bd09128d16fac3c34b80bd6a29088ac632e8ce09
Author: James Morse <james.morse@arm.com>
Date:   Tue Nov 23 18:29:25 2021 +0000

    arm64: Add percpu vectors for EL1
    
    The Spectre-BHB workaround adds a firmware call to the vectors. This
    is needed on some CPUs, but not others. To avoid the unaffected CPU in
    a big/little pair from making the firmware call, create per cpu vectors.
    
    The per-cpu vectors only apply when returning from EL0.
    
    Systems using KPTI can use the canonical 'full-fat' vectors directly at
    EL1, the trampoline exit code will switch to this_cpu_vector on exit to
    EL0. Systems not using KPTI should always use this_cpu_vector.
    
    this_cpu_vector will point at a vector in tramp_vecs or
    __bp_harden_el1_vectors, depending on whether KPTI is in use.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit b28a8eebe81c186fdb1a0078263b30576c8e1f42
Author: James Morse <james.morse@arm.com>
Date:   Thu Nov 25 14:25:34 2021 +0000

    arm64: entry: Add macro for reading symbol addresses from the trampoline
    
    The trampoline code needs to use the address of symbols in the wider
    kernel, e.g. vectors. PC-relative addressing wouldn't work as the
    trampoline code doesn't run at the address the linker expected.
    
    tramp_ventry uses a literal pool, unless CONFIG_RANDOMIZE_BASE is
    set, in which case it uses the data page as a literal pool because
    the data page can be unmapped when running in user-space, which is
    required for CPUs vulnerable to meltdown.
    
    Pull this logic out as a macro, instead of adding a third copy
    of it.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit ba2689234be92024e5635d30fe744f4853ad97db
Author: James Morse <james.morse@arm.com>
Date:   Thu Nov 18 13:59:46 2021 +0000

    arm64: entry: Add vectors that have the bhb mitigation sequences
    
    Some CPUs affected by Spectre-BHB need a sequence of branches, or a
    firmware call to be run before any indirect branch. This needs to go
    in the vectors. No CPU needs both.
    
    While this can be patched in, it would run on all CPUs as there is a
    single set of vectors. If only one part of a big/little combination is
    affected, the unaffected CPUs have to run the mitigation too.
    
    Create extra vectors that include the sequence. Subsequent patches will
    allow affected CPUs to select this set of vectors. Later patches will
    modify the loop count to match what the CPU requires.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 439cf34c8e0a8a33d8c15a31be1b7423426bc765
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Wed Feb 9 11:19:27 2022 +0200

    drm/atomic: Don't pollute crtc_state->mode_blob with error pointers
    
    Make sure we don't assign an error pointer to crtc_state->mode_blob
    as that will break all kinds of places that assume either NULL or a
    valid pointer (eg. drm_property_blob_put()).
    
    Cc: stable@vger.kernel.org
    Reported-by: fuyufan <fuyufan@huawei.com>
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220209091928.14766-1-ville.syrjala@linux.intel.com
    Acked-by: Maxime Ripard <maxime@cerno.tech>

commit de8aa31ac7c23af98fe24d1c1b43b065027d6af5
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Tue Feb 15 16:29:08 2022 -0800

    Input: zinitix - add new compatible strings
    
    This driver works just fine with the BT404 version of the touchscreen
    as well. Tested on the Samsung GT-I8160 (Codina) mobile phone.
    
    Add all the new variants from the binding document so people can
    easily test them, we believe most of them work more or less.
    
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/20220214234033.1052681-1-linus.walleij@linaro.org
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit c5d9ae265b105d9a67575fb67bd4650a6fc08e25
Merge: a254a9da455c1 710c476514313
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 11:07:59 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "ARM:
    
       - Read HW interrupt pending state from the HW
    
      x86:
    
       - Don't truncate the performance event mask on AMD
    
       - Fix Xen runstate updates to be atomic when preempting vCPU
    
       - Fix for AMD AVIC interrupt injection race
    
       - Several other AMD fixes"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      KVM: x86/pmu: Use AMD64_RAW_EVENT_MASK for PERF_TYPE_RAW
      KVM: x86/pmu: Don't truncate the PerfEvtSeln MSR when creating a perf event
      KVM: SVM: fix race between interrupt delivery and AVIC inhibition
      KVM: SVM: set IRR in svm_deliver_interrupt
      KVM: SVM: extract avic_ring_doorbell
      selftests: kvm: Remove absent target file
      KVM: arm64: vgic: Read HW interrupt pending state from the HW
      KVM: x86/xen: Fix runstate updates to be atomic when preempting vCPU
      KVM: x86: SVM: move avic definitions from AMD's spec to svm.h
      KVM: x86: lapic: don't touch irr_pending in kvm_apic_update_apicv when inhibiting it
      KVM: x86: nSVM: deal with L1 hypervisor that intercepts interrupts but lets L2 control them
      KVM: x86: nSVM: expose clean bit support to the guest
      KVM: x86: nSVM/nVMX: set nested_run_pending on VM entry which is a result of RSM
      KVM: x86: nSVM: mark vmcb01 as dirty when restoring SMM saved state
      KVM: x86: nSVM: fix potential NULL derefernce on nested migration
      KVM: x86: SVM: don't passthrough SMAP/SMEP/PKE bits in !NPT && !gCR0.PG case
      Revert "svm: Add warning message for AVIC IPI invalid target"

commit f98da1d66298882b1d2061051ea14ddc15c58884
Author: Dan Williams <dan.j.williams@intel.com>
Date:   Tue Feb 15 10:54:23 2022 -0800

    ACPI: tables: Quiet ACPI table not found warning
    
    Paul reports that the ACPI core complains on every boot about a missing
    CEDT table. Unlike the standard NUMA tables (SRAT, MADT, and SLIT) that
    are critical to NUMA init, CEDT is only expected on CXL platforms. Given
    the notice is not actionable lower its severity to debug.
    
    Link: https://lore.kernel.org/r/55f5c077-061c-7e53-b02d-53dde1dd654f@molgen.mpg.de
    Fixes: fd49f99c1809 ("ACPI: NUMA: Add a node and memblk for each CFMWS not in SRAT")
    Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Signed-off-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 966d879bafaaf020c11a7cee9526f6dd823a4126
Author: Qu Wenruo <wqu@suse.com>
Date:   Fri Feb 11 14:41:39 2022 +0800

    btrfs: defrag: allow defrag_one_cluster() to skip large extent which is not a target
    
    In the rework of btrfs_defrag_file(), we always call
    defrag_one_cluster() and increase the offset by cluster size, which is
    only 256K.
    
    But there are cases where we have a large extent (e.g. 128M) which
    doesn't need to be defragged at all.
    
    Before the refactor, we can directly skip the range, but now we have to
    scan that extent map again and again until the cluster moves after the
    non-target extent.
    
    Fix the problem by allow defrag_one_cluster() to increase
    btrfs_defrag_ctrl::last_scanned to the end of an extent, if and only if
    the last extent of the cluster is not a target.
    
    The test script looks like this:
    
            mkfs.btrfs -f $dev > /dev/null
    
            mount $dev $mnt
    
            # As btrfs ioctl uses 32M as extent_threshold
            xfs_io -f -c "pwrite 0 64M" $mnt/file1
            sync
            # Some fragemented range to defrag
            xfs_io -s -c "pwrite 65548k 4k" \
                      -c "pwrite 65544k 4k" \
                      -c "pwrite 65540k 4k" \
                      -c "pwrite 65536k 4k" \
                      $mnt/file1
            sync
    
            echo "=== before ==="
            xfs_io -c "fiemap -v" $mnt/file1
            echo "=== after ==="
            btrfs fi defrag $mnt/file1
            sync
            xfs_io -c "fiemap -v" $mnt/file1
            umount $mnt
    
    With extra ftrace put into defrag_one_cluster(), before the patch it
    would result tons of loops:
    
    (As defrag_one_cluster() is inlined, the function name is its caller)
    
      btrfs-126062  [005] .....  4682.816026: btrfs_defrag_file: r/i=5/257 start=0 len=262144
      btrfs-126062  [005] .....  4682.816027: btrfs_defrag_file: r/i=5/257 start=262144 len=262144
      btrfs-126062  [005] .....  4682.816028: btrfs_defrag_file: r/i=5/257 start=524288 len=262144
      btrfs-126062  [005] .....  4682.816028: btrfs_defrag_file: r/i=5/257 start=786432 len=262144
      btrfs-126062  [005] .....  4682.816028: btrfs_defrag_file: r/i=5/257 start=1048576 len=262144
      ...
      btrfs-126062  [005] .....  4682.816043: btrfs_defrag_file: r/i=5/257 start=67108864 len=262144
    
    But with this patch there will be just one loop, then directly to the
    end of the extent:
    
      btrfs-130471  [014] .....  5434.029558: defrag_one_cluster: r/i=5/257 start=0 len=262144
      btrfs-130471  [014] .....  5434.029559: defrag_one_cluster: r/i=5/257 start=67108864 len=16384
    
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 741b23a970a79d5d3a1db2d64fa2c7b375a4febb
Author: Dāvis Mosāns <davispuh@gmail.com>
Date:   Wed Feb 2 23:44:55 2022 +0200

    btrfs: prevent copying too big compressed lzo segment
    
    Compressed length can be corrupted to be a lot larger than memory
    we have allocated for buffer.
    This will cause memcpy in copy_compressed_segment to write outside
    of allocated memory.
    
    This mostly results in stuck read syscall but sometimes when using
    btrfs send can get #GP
    
      kernel: general protection fault, probably for non-canonical address 0x841551d5c1000: 0000 [#1] PREEMPT SMP NOPTI
      kernel: CPU: 17 PID: 264 Comm: kworker/u256:7 Tainted: P           OE     5.17.0-rc2-1 #12
      kernel: Workqueue: btrfs-endio btrfs_work_helper [btrfs]
      kernel: RIP: 0010:lzo_decompress_bio (./include/linux/fortify-string.h:225 fs/btrfs/lzo.c:322 fs/btrfs/lzo.c:394) btrfs
      Code starting with the faulting instruction
      ===========================================
         0:*  48 8b 06                mov    (%rsi),%rax              <-- trapping instruction
         3:   48 8d 79 08             lea    0x8(%rcx),%rdi
         7:   48 83 e7 f8             and    $0xfffffffffffffff8,%rdi
         b:   48 89 01                mov    %rax,(%rcx)
         e:   44 89 f0                mov    %r14d,%eax
        11:   48 8b 54 06 f8          mov    -0x8(%rsi,%rax,1),%rdx
      kernel: RSP: 0018:ffffb110812efd50 EFLAGS: 00010212
      kernel: RAX: 0000000000001000 RBX: 000000009ca264c8 RCX: ffff98996e6d8ff8
      kernel: RDX: 0000000000000064 RSI: 000841551d5c1000 RDI: ffffffff9500435d
      kernel: RBP: ffff989a3be856c0 R08: 0000000000000000 R09: 0000000000000000
      kernel: R10: 0000000000000000 R11: 0000000000001000 R12: ffff98996e6d8000
      kernel: R13: 0000000000000008 R14: 0000000000001000 R15: 000841551d5c1000
      kernel: FS:  0000000000000000(0000) GS:ffff98a09d640000(0000) knlGS:0000000000000000
      kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      kernel: CR2: 00001e9f984d9ea8 CR3: 000000014971a000 CR4: 00000000003506e0
      kernel: Call Trace:
      kernel:  <TASK>
      kernel: end_compressed_bio_read (fs/btrfs/compression.c:104 fs/btrfs/compression.c:1363 fs/btrfs/compression.c:323) btrfs
      kernel: end_workqueue_fn (fs/btrfs/disk-io.c:1923) btrfs
      kernel: btrfs_work_helper (fs/btrfs/async-thread.c:326) btrfs
      kernel: process_one_work (./arch/x86/include/asm/jump_label.h:27 ./include/linux/jump_label.h:212 ./include/trace/events/workqueue.h:108 kernel/workqueue.c:2312)
      kernel: worker_thread (./include/linux/list.h:292 kernel/workqueue.c:2455)
      kernel: ? process_one_work (kernel/workqueue.c:2397)
      kernel: kthread (kernel/kthread.c:377)
      kernel: ? kthread_complete_and_exit (kernel/kthread.c:332)
      kernel: ret_from_fork (arch/x86/entry/entry_64.S:301)
      kernel:  </TASK>
    
    CC: stable@vger.kernel.org # 4.9+
    Signed-off-by: Dāvis Mosāns <davispuh@gmail.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a254a9da455c171441ab3a76ed8f5d1e9412e15f
Merge: 705d84a366cfc 7f016b35ca762
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 10:52:05 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid
    
    Pull HID fixes from Jiri Kosina:
    
     - memory leak fix for hid-elo driver (Dongliang Mu)
    
     - fix for hangs on newer AMD platforms with amd_sfh-driven hardware
       (Basavaraj Natikar )
    
     - locking fix in i2c-hid (Daniel Thompson)
    
     - a few device-ID specific quirks
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid:
      HID: amd_sfh: Add interrupt handler to process interrupts
      HID: amd_sfh: Add functionality to clear interrupts
      HID: amd_sfh: Disable the interrupt for all command
      HID: amd_sfh: Correct the structure field name
      HID: amd_sfh: Handle amd_sfh work buffer in PM ops
      HID:Add support for UGTABLET WP5540
      HID: amd_sfh: Add illuminance mask to limit ALS max value
      HID: amd_sfh: Increase sensor command timeout
      HID: i2c-hid: goodix: Fix a lockdep splat
      HID: elo: fix memory leak in elo_probe
      HID: apple: Set the tilde quirk flag on the Wellspring 5 and later

commit 61d06f01f9710b327a53492e5add9f972eb909b3
Author: Felix Maurer <fmaurer@redhat.com>
Date:   Fri Feb 11 18:43:36 2022 +0100

    selftests: bpf: Check bpf_msg_push_data return value
    
    bpf_msg_push_data may return a non-zero value to indicate an error. The
    return value should be checked to prevent undetected errors.
    
    To indicate an error, the BPF programs now perform a different action
    than their intended one to make the userspace test program notice the
    error, i.e., the programs supposed to pass/redirect drop, the program
    supposed to drop passes.
    
    Fixes: 84fbfe026acaa ("bpf: test_sockmap add options to use msg_push_data")
    Signed-off-by: Felix Maurer <fmaurer@redhat.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Link: https://lore.kernel.org/bpf/89f767bb44005d6b4dd1f42038c438f76b3ebfad.1644601294.git.fmaurer@redhat.com

commit aff65393fa1401e034656e349abd655cfe272de0
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 24 15:03:15 2021 +0000

    arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
    
    kpti is an optional feature, for systems not using kpti a set of
    vectors for the spectre-bhb mitigations is needed.
    
    Add another set of vectors, __bp_harden_el1_vectors, that will be
    used if a mitigation is needed and kpti is not in use.
    
    The EL1 ventries are repeated verbatim as there is no additional
    work needed for entry from EL1.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit a9c406e6462ff14956d690de7bbe5131a5677dc9
Author: James Morse <james.morse@arm.com>
Date:   Thu Nov 18 15:04:32 2021 +0000

    arm64: entry: Allow the trampoline text to occupy multiple pages
    
    Adding a second set of vectors to .entry.tramp.text will make it
    larger than a single 4K page.
    
    Allow the trampoline text to occupy up to three pages by adding two
    more fixmap slots. Previous changes to tramp_valias allowed it to reach
    beyond a single page.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit c47e4d04ba0f1ea17353d85d45f611277507e07a
Author: James Morse <james.morse@arm.com>
Date:   Thu Nov 18 13:16:23 2021 +0000

    arm64: entry: Make the kpti trampoline's kpti sequence optional
    
    Spectre-BHB needs to add sequences to the vectors. Having one global
    set of vectors is a problem for big/little systems where the sequence
    is costly on cpus that are not vulnerable.
    
    Making the vectors per-cpu in the style of KVM's bh_harden_hyp_vecs
    requires the vectors to be generated by macros.
    
    Make the kpti re-mapping of the kernel optional, so the macros can be
    used without kpti.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 13d7a08352a83ef2252aeb464a5e08dfc06b5dfd
Author: James Morse <james.morse@arm.com>
Date:   Thu Nov 18 14:02:30 2021 +0000

    arm64: entry: Move trampoline macros out of ifdef'd section
    
    The macros for building the kpti trampoline are all behind
    CONFIG_UNMAP_KERNEL_AT_EL0, and in a region that outputs to the
    .entry.tramp.text section.
    
    Move the macros out so they can be used to generate other kinds of
    trampoline. Only the symbols need to be guarded by
    CONFIG_UNMAP_KERNEL_AT_EL0 and appear in the .entry.tramp.text section.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit ed50da7764535f1e24432ded289974f2bf2b0c5a
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 24 13:40:09 2021 +0000

    arm64: entry: Don't assume tramp_vectors is the start of the vectors
    
    The tramp_ventry macro uses tramp_vectors as the address of the vectors
    when calculating which ventry in the 'full fat' vectors to branch to.
    
    While there is one set of tramp_vectors, this will be true.
    Adding multiple sets of vectors will break this assumption.
    
    Move the generation of the vectors to a macro, and pass the start
    of the vectors as an argument to tramp_ventry.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 6c5bf79b69f911560fbf82214c0971af6e58e682
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 24 11:40:18 2021 +0000

    arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
    
    Systems using kpti enter and exit the kernel through a trampoline mapping
    that is always mapped, even when the kernel is not. tramp_valias is a macro
    to find the address of a symbol in the trampoline mapping.
    
    Adding extra sets of vectors will expand the size of the entry.tramp.text
    section to beyond 4K. tramp_valias will be unable to generate addresses
    for symbols beyond 4K as it uses the 12 bit immediate of the add
    instruction.
    
    As there are now two registers available when tramp_alias is called,
    use the extra register to avoid the 4K limit of the 12 bit immediate.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit c091fb6ae059cda563b2a4d93fdbc548ef34e1d6
Author: James Morse <james.morse@arm.com>
Date:   Tue Nov 23 15:43:31 2021 +0000

    arm64: entry: Move the trampoline data page before the text page
    
    The trampoline code has a data page that holds the address of the vectors,
    which is unmapped when running in user-space. This ensures that with
    CONFIG_RANDOMIZE_BASE, the randomised address of the kernel can't be
    discovered until after the kernel has been mapped.
    
    If the trampoline text page is extended to include multiple sets of
    vectors, it will be larger than a single page, making it tricky to
    find the data page without knowing the size of the trampoline text
    pages, which will vary with PAGE_SIZE.
    
    Move the data page to appear before the text page. This allows the
    data page to be found without knowing the size of the trampoline text
    pages. 'tramp_vectors' is used to refer to the beginning of the
    .entry.tramp.text section, do that explicitly.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 03aff3a77a58b5b52a77e00537a42090ad57b80b
Author: James Morse <james.morse@arm.com>
Date:   Tue Nov 23 18:41:43 2021 +0000

    arm64: entry: Free up another register on kpti's tramp_exit path
    
    Kpti stashes x30 in far_el1 while it uses x30 for all its work.
    
    Making the vectors a per-cpu data structure will require a second
    register.
    
    Allow tramp_exit two registers before it unmaps the kernel, by
    leaving x30 on the stack, and stashing x29 in far_el1.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit d739da1694a0eaef0358a42b76904b611539b77b
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 24 15:36:12 2021 +0000

    arm64: entry: Make the trampoline cleanup optional
    
    Subsequent patches will add additional sets of vectors that use
    the same tricks as the kpti vectors to reach the full-fat vectors.
    The full-fat vectors contain some cleanup for kpti that is patched
    in by alternatives when kpti is in use. Once there are additional
    vectors, the cleanup will be needed in more cases.
    
    But on big/little systems, the cleanup would be harmful if no
    trampoline vector were in use. Instead of forcing CPUs that don't
    need a trampoline vector to use one, make the trampoline cleanup
    optional.
    
    Entry at the top of the vectors will skip the cleanup. The trampoline
    vectors can then skip the first instruction, triggering the cleanup
    to run.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 5bdf3437603d4af87f9c7f424b0c8aeed2420745
Author: James Morse <james.morse@arm.com>
Date:   Tue Nov 16 15:06:19 2021 +0000

    KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
    
    CPUs vulnerable to Spectre-BHB either need to make an SMC-CC firmware
    call from the vectors, or run a sequence of branches. This gets added
    to the hyp vectors. If there is no support for arch-workaround-1 in
    firmware, the indirect vector will be used.
    
    kvm_init_vector_slots() only initialises the two indirect slots if
    the platform is vulnerable to Spectre-v3a. pKVM's hyp_map_vectors()
    only initialises __hyp_bp_vect_base if the platform is vulnerable to
    Spectre-v3a.
    
    As there are about to more users of the indirect vectors, ensure
    their entries in hyp_spectre_vector_selector[] are always initialised,
    and __hyp_bp_vect_base defaults to the regular VA mapping.
    
    The Spectre-v3a check is moved to a helper
    kvm_system_needs_idmapped_vectors(), and merged with the code
    that creates the hyp mappings.
    
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 1b33d4860deaecf1d8eec3061b7e7ed7ab0bae8d
Author: James Morse <james.morse@arm.com>
Date:   Tue Nov 16 15:00:51 2021 +0000

    arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
    
    The spectre-v4 sequence includes an SMC from the assembly entry code.
    spectre_v4_patch_fw_mitigation_conduit is the patching callback that
    generates an HVC or SMC depending on the SMCCC conduit type.
    
    As this isn't specific to spectre-v4, rename it
    smccc_patch_fw_mitigation_conduit so it can be re-used.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 4330e2c5c04c27bebf89d34e0bc14e6943413067
Author: James Morse <james.morse@arm.com>
Date:   Wed Nov 17 15:15:26 2021 +0000

    arm64: entry.S: Add ventry overflow sanity checks
    
    Subsequent patches add even more code to the ventry slots.
    Ensure kernels that overflow a ventry slot don't get built.
    
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>

commit 705d84a366cfccda1e7aec1113a5399cd2ffee7d
Merge: 2572da44a5119 2e7be9db125a0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 09:14:05 2022 -0800

    Merge tag 'for-5.17-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs fixes from David Sterba:
    
     - yield CPU more often when defragmenting a large file
    
     - skip defragmenting extents already under writeback
    
     - improve error message when send fails to write file data
    
     - get rid of warning when mounted with 'flushoncommit'
    
    * tag 'for-5.17-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
      btrfs: send: in case of IO error log it
      btrfs: get rid of warning on transaction commit when using flushoncommit
      btrfs: defrag: don't try to defrag extents which are under writeback
      btrfs: don't hold CPU for too long when defragging a file

commit 2572da44a51192ad181482c1989e66e5eb47dcbe
Merge: c24449b321095 6e8793674bb0d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 09:10:09 2022 -0800

    Merge tag 'for-5.17/parisc-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
    
    Pull parisc architecture fixes from Helge Deller:
    
     - Fix miscompilations when function calls are made from inside a
       put_user() call
    
     - Drop __init from map_pages() declaration to avoid random boot crashes
    
     - Added #error messages if a 64-bit compiler was used to build a 32-bit
       kernel (and vice versa)
    
     - Fix out-of-bound data TLB miss faults in sba_iommu and ccio-dma
       drivers
    
     - Add ioread64_lo_hi() and iowrite64_lo_hi() functions to avoid kernel
       test robot errors
    
     - Fix link failure when 8250_gsc driver is built without CONFIG_IOSAPIC
    
    * tag 'for-5.17/parisc-3' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
      serial: parisc: GSC: fix build when IOSAPIC is not set
      parisc: Fix some apparent put_user() failures
      parisc: Show error if wrong 32/64-bit compiler is being used
      parisc: Add ioread64_lo_hi() and iowrite64_lo_hi()
      parisc: Fix sglist access in ccio-dma.c
      parisc: Fix data TLB miss in sba_unmap_sg
      parisc: Drop __init from map_pages declaration

commit c24449b321095d8c80cdda3d68107269c1d5569f
Merge: d567f5db412ed ffc58bc4af936
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 15 09:05:01 2022 -0800

    Merge tag 'hyperv-fixes-signed-20220215' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux
    
    Pull hyperv fixes from Wei Liu:
    
     - Rework use of DMA_BIT_MASK in vmbus to work around a clang bug
       (Michael Kelley)
    
     - Fix NUMA topology (Long Li)
    
     - Fix a memory leak in vmbus (Miaoqian Lin)
    
     - One minor clean-up patch (Cai Huoqing)
    
    * tag 'hyperv-fixes-signed-20220215' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux:
      Drivers: hv: utils: Make use of the helper macro LIST_HEAD()
      Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64)
      Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj
      PCI: hv: Fix NUMA node assignment when kernel boots with custom NUMA topology

commit 6f66db29e2415cbe8759c48584f9cae19b3c2651
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Tue Dec 14 19:49:13 2021 +0200

    pinctrl: tigerlake: Revert "Add Alder Lake-M ACPI ID"
    
    It appears that last minute change moved ACPI ID of Alder Lake-M
    to the INTC1055, which is already in the driver.
    
    This ID on the other hand will be used elsewhere.
    
    This reverts commit 258435a1c8187f559549e515d2f77fa0b57bcd27.
    
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

commit b6821b0d9b56386d2bf14806f90ec401468c799f
Author: Oliver Graute <oliver.graute@kococonnector.com>
Date:   Thu Feb 10 09:53:22 2022 +0100

    staging: fbtft: fb_st7789v: reset display before initialization
    
    In rare cases the display is flipped or mirrored. This was observed more
    often in a low temperature environment. A clean reset on init_display()
    should help to get registers in a sane state.
    
    Fixes: ef8f317795da (staging: fbtft: use init function instead of init sequence)
    Cc: stable@vger.kernel.org
    Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
    Link: https://lore.kernel.org/r/20220210085322.15676-1-oliver.graute@kococonnector.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 8d2b1a1ec9f559d30b724877da4ce592edc41fdc
Author: Oliver Neukum <oneukum@suse.com>
Date:   Tue Feb 15 11:35:47 2022 +0100

    CDC-NCM: avoid overflow in sanity checking
    
    A broken device may give an extreme offset like 0xFFF0
    and a reasonable length for a fragment. In the sanity
    check as formulated now, this will create an integer
    overflow, defeating the sanity check. Both offset
    and offset + len need to be checked in such a manner
    that no overflow can occur.
    And those quantities should be unsigned.
    
    Signed-off-by: Oliver Neukum <oneukum@suse.com>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f8efca92ae509c25e0a4bd5d0a86decea4f0c41e
Author: Eliav Farber <farbere@amazon.com>
Date:   Thu Jan 13 10:06:19 2022 +0000

    EDAC: Fix calculation of returned address and next offset in edac_align_ptr()
    
    Do alignment logic properly and use the "ptr" local variable for
    calculating the remainder of the alignment.
    
    This became an issue because struct edac_mc_layer has a size that is not
    zero modulo eight, and the next offset that was prepared for the private
    data was unaligned, causing an alignment exception.
    
    The patch in Fixes: which broke this actually wanted to "what we
    actually care about is the alignment of the actual pointer that's about
    to be returned." But it didn't check that alignment.
    
    Use the correct variable "ptr" for that.
    
      [ bp: Massage commit message. ]
    
    Fixes: 8447c4d15e35 ("edac: Do alignment logic properly in edac_align_ptr()")
    Signed-off-by: Eliav Farber <farbere@amazon.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220113100622.12783-2-farbere@amazon.com

commit 7e5b6a5c8c44310784c88c1c198dde79f6402f7b
Author: Tom Rix <trix@redhat.com>
Date:   Mon Feb 14 18:05:41 2022 -0800

    mctp: fix use after free
    
    Clang static analysis reports this problem
    route.c:425:4: warning: Use of memory after it is freed
      trace_mctp_key_acquire(key);
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
    When mctp_key_add() fails, key is freed but then is later
    used in trace_mctp_key_acquire().  Add an else statement
    to use the key only when mctp_key_add() is successful.
    
    Fixes: 4f9e1ba6de45 ("mctp: Add tracepoints for tag/key handling")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f240762f88b4b1b58561939ffd44837759756477
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Feb 14 20:10:03 2022 -0800

    io_uring: add a schedule point in io_add_buffers()
    
    Looping ~65535 times doing kmalloc() calls can trigger soft lockups,
    especially with DEBUG features (like KASAN).
    
    [  253.536212] watchdog: BUG: soft lockup - CPU#64 stuck for 26s! [b219417889:12575]
    [  253.544433] Modules linked in: vfat fat i2c_mux_pca954x i2c_mux spidev cdc_acm xhci_pci xhci_hcd sha3_generic gq(O)
    [  253.544451] CPU: 64 PID: 12575 Comm: b219417889 Tainted: G S         O      5.17.0-smp-DEV #801
    [  253.544457] RIP: 0010:kernel_text_address (./include/asm-generic/sections.h:192 ./include/linux/kallsyms.h:29 kernel/extable.c:67 kernel/extable.c:98)
    [  253.544464] Code: 0f 93 c0 48 c7 c1 e0 63 d7 a4 48 39 cb 0f 92 c1 20 c1 0f b6 c1 5b 5d c3 90 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 53 48 89 fb <48> c7 c0 00 00 80 a0 41 be 01 00 00 00 48 39 c7 72 0c 48 c7 c0 40
    [  253.544468] RSP: 0018:ffff8882d8baf4c0 EFLAGS: 00000246
    [  253.544471] RAX: 1ffff1105b175e00 RBX: ffffffffa13ef09a RCX: 00000000a13ef001
    [  253.544474] RDX: ffffffffa13ef09a RSI: ffff8882d8baf558 RDI: ffffffffa13ef09a
    [  253.544476] RBP: ffff8882d8baf4d8 R08: ffff8882d8baf5e0 R09: 0000000000000004
    [  253.544479] R10: ffff8882d8baf5e8 R11: ffffffffa0d59a50 R12: ffff8882eab20380
    [  253.544481] R13: ffffffffa0d59a50 R14: dffffc0000000000 R15: 1ffff1105b175eb0
    [  253.544483] FS:  00000000016d3380(0000) GS:ffff88af48c00000(0000) knlGS:0000000000000000
    [  253.544486] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  253.544488] CR2: 00000000004af0f0 CR3: 00000002eabfa004 CR4: 00000000003706e0
    [  253.544491] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [  253.544492] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [  253.544494] Call Trace:
    [  253.544496]  <TASK>
    [  253.544498] ? io_queue_sqe (fs/io_uring.c:7143)
    [  253.544505] __kernel_text_address (kernel/extable.c:78)
    [  253.544508] unwind_get_return_address (arch/x86/kernel/unwind_frame.c:19)
    [  253.544514] arch_stack_walk (arch/x86/kernel/stacktrace.c:27)
    [  253.544517] ? io_queue_sqe (fs/io_uring.c:7143)
    [  253.544521] stack_trace_save (kernel/stacktrace.c:123)
    [  253.544527] ____kasan_kmalloc (mm/kasan/common.c:39 mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:515)
    [  253.544531] ? ____kasan_kmalloc (mm/kasan/common.c:39 mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:515)
    [  253.544533] ? __kasan_kmalloc (mm/kasan/common.c:524)
    [  253.544535] ? kmem_cache_alloc_trace (./include/linux/kasan.h:270 mm/slab.c:3567)
    [  253.544541] ? io_issue_sqe (fs/io_uring.c:4556 fs/io_uring.c:4589 fs/io_uring.c:6828)
    [  253.544544] ? __io_queue_sqe (fs/io_uring.c:?)
    [  253.544551] __kasan_kmalloc (mm/kasan/common.c:524)
    [  253.544553] kmem_cache_alloc_trace (./include/linux/kasan.h:270 mm/slab.c:3567)
    [  253.544556] ? io_issue_sqe (fs/io_uring.c:4556 fs/io_uring.c:4589 fs/io_uring.c:6828)
    [  253.544560] io_issue_sqe (fs/io_uring.c:4556 fs/io_uring.c:4589 fs/io_uring.c:6828)
    [  253.544564] ? __kasan_slab_alloc (mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469)
    [  253.544567] ? __kasan_slab_alloc (mm/kasan/common.c:39 mm/kasan/common.c:45 mm/kasan/common.c:436 mm/kasan/common.c:469)
    [  253.544569] ? kmem_cache_alloc_bulk (mm/slab.h:732 mm/slab.c:3546)
    [  253.544573] ? __io_alloc_req_refill (fs/io_uring.c:2078)
    [  253.544578] ? io_submit_sqes (fs/io_uring.c:7441)
    [  253.544581] ? __se_sys_io_uring_enter (fs/io_uring.c:10154 fs/io_uring.c:10096)
    [  253.544584] ? __x64_sys_io_uring_enter (fs/io_uring.c:10096)
    [  253.544587] ? do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)
    [  253.544590] ? entry_SYSCALL_64_after_hwframe (??:?)
    [  253.544596] __io_queue_sqe (fs/io_uring.c:?)
    [  253.544600] io_queue_sqe (fs/io_uring.c:7143)
    [  253.544603] io_submit_sqe (fs/io_uring.c:?)
    [  253.544608] io_submit_sqes (fs/io_uring.c:?)
    [  253.544612] __se_sys_io_uring_enter (fs/io_uring.c:10154 fs/io_uring.c:10096)
    [  253.544616] __x64_sys_io_uring_enter (fs/io_uring.c:10096)
    [  253.544619] do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80)
    [  253.544623] entry_SYSCALL_64_after_hwframe (??:?)
    
    Fixes: ddf0322db79c ("io_uring: add IORING_OP_PROVIDE_BUFFERS")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Jens Axboe <axboe@kernel.dk>
    Cc: Pavel Begunkov <asml.silence@gmail.com>
    Cc: io-uring <io-uring@vger.kernel.org>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220215041003.2394784-1-eric.dumazet@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit ef57640575406f57f5b3393cf57f457b0ace837e
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Tue Feb 15 01:42:00 2022 +0200

    net: mscc: ocelot: fix use-after-free in ocelot_vlan_del()
    
    ocelot_vlan_member_del() will free the struct ocelot_bridge_vlan, so if
    this is the same as the port's pvid_vlan which we access afterwards,
    what we're accessing is freed memory.
    
    Fix the bug by determining whether to clear ocelot_port->pvid_vlan prior
    to calling ocelot_vlan_member_del().
    
    Fixes: d4004422f6f9 ("net: mscc: ocelot: track the port pvid using a pointer")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9ceaf6f76b203682bb6100e14b3d7da4c0bedde8
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Feb 14 11:15:53 2022 -0800

    bonding: fix data-races around agg_select_timer
    
    syzbot reported that two threads might write over agg_select_timer
    at the same time. Make agg_select_timer atomic to fix the races.
    
    BUG: KCSAN: data-race in bond_3ad_initiate_agg_selection / bond_3ad_state_machine_handler
    
    read to 0xffff8881242aea90 of 4 bytes by task 1846 on cpu 1:
     bond_3ad_state_machine_handler+0x99/0x2810 drivers/net/bonding/bond_3ad.c:2317
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     worker_thread+0x616/0xa70 kernel/workqueue.c:2454
     kthread+0x1bf/0x1e0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30
    
    write to 0xffff8881242aea90 of 4 bytes by task 25910 on cpu 0:
     bond_3ad_initiate_agg_selection+0x18/0x30 drivers/net/bonding/bond_3ad.c:1998
     bond_open+0x658/0x6f0 drivers/net/bonding/bond_main.c:3967
     __dev_open+0x274/0x3a0 net/core/dev.c:1407
     dev_open+0x54/0x190 net/core/dev.c:1443
     bond_enslave+0xcef/0x3000 drivers/net/bonding/bond_main.c:1937
     do_set_master net/core/rtnetlink.c:2532 [inline]
     do_setlink+0x94f/0x2500 net/core/rtnetlink.c:2736
     __rtnl_newlink net/core/rtnetlink.c:3414 [inline]
     rtnl_newlink+0xfeb/0x13e0 net/core/rtnetlink.c:3529
     rtnetlink_rcv_msg+0x745/0x7e0 net/core/rtnetlink.c:5594
     netlink_rcv_skb+0x14e/0x250 net/netlink/af_netlink.c:2494
     rtnetlink_rcv+0x18/0x20 net/core/rtnetlink.c:5612
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x602/0x6d0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x728/0x850 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmsg+0x195/0x230 net/socket.c:2496
     __do_sys_sendmsg net/socket.c:2505 [inline]
     __se_sys_sendmsg net/socket.c:2503 [inline]
     __x64_sys_sendmsg+0x42/0x50 net/socket.c:2503
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x00000050 -> 0x0000004f
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 25910 Comm: syz-executor.1 Tainted: G        W         5.17.0-rc4-syzkaller-dirty #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Cc: Jay Vosburgh <j.vosburgh@gmail.com>
    Cc: Veaceslav Falico <vfalico@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 07dd44852be89386ab12210df90a2d78779f3bff
Author: Radu Bulie <radu-andrei.bulie@nxp.com>
Date:   Mon Feb 14 19:45:34 2022 +0200

    dpaa2-eth: Initialize mutex used in one step timestamping path
    
    1588 Single Step Timestamping code path uses a mutex to
    enforce atomicity for two events:
    - update of ptp single step register
    - transmit ptp event packet
    
    Before this patch the mutex was not initialized. This
    caused unexpected crashes in the Tx function.
    
    Fixes: c55211892f463 ("dpaa2-eth: support PTP Sync packet one-step timestamping")
    Signed-off-by: Radu Bulie <radu-andrei.bulie@nxp.com>
    Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2a36ed7c1cd55742503bed81d2cc0ea83bd0ad0c
Author: Tom Rix <trix@redhat.com>
Date:   Mon Feb 14 07:41:39 2022 -0800

    dpaa2-switch: fix default return of dpaa2_switch_flower_parse_mirror_key
    
    Clang static analysis reports this representative problem
    dpaa2-switch-flower.c:616:24: warning: The right operand of '=='
      is a garbage value
      tmp->cfg.vlan_id == vlan) {
                       ^  ~~~~
    vlan is set in dpaa2_switch_flower_parse_mirror_key(). However
    this function can return success without setting vlan.  So
    change the default return to -EOPNOTSUPP.
    
    Fixes: 0f3faece5808 ("dpaa2-switch: add VLAN based mirroring")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9d2d38c35e7a3de96340c446f3b0fde7b2e7348e
Author: Zhang Yunkai <zhang.yunkai@zte.com.cn>
Date:   Mon Feb 14 03:27:21 2022 +0000

    ipv4: add description about martian source
    
    When multiple containers are running in the environment and multiple
    macvlan network port are configured in each container, a lot of martian
    source prints will appear after martian_log is enabled. they are almost
    the same, and printed by net_warn_ratelimited. Each arp message will
    trigger this print on each network port.
    
    Such as:
    IPv4: martian source 173.254.95.16 from 173.254.100.109,
    on dev eth0
    ll header: 00000000: ff ff ff ff ff ff 40 00 ad fe 64 6d
    08 06        ......@...dm..
    IPv4: martian source 173.254.95.16 from 173.254.100.109,
    on dev eth1
    ll header: 00000000: ff ff ff ff ff ff 40 00 ad fe 64 6d
    08 06        ......@...dm..
    
    There is no description of this kind of source in the RFC1812.
    
    Signed-off-by: Zhang Yunkai <zhang.yunkai@zte.com.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 25206111512de994dfc914f5b2972a22aa904ef3
Author: Eric Dumazet <edumazet@google.com>
Date:   Sun Feb 13 11:06:07 2022 -0800

    crypto: af_alg - get rid of alg_memory_allocated
    
    alg_memory_allocated does not seem to be really used.
    
    alg_proto does have a .memory_allocated field, but no
    corresponding .sysctl_mem.
    
    This means sk_has_account() returns true, but all sk_prot_mem_limits()
    users will trigger a NULL dereference [1].
    
    THis was not a problem until SO_RESERVE_MEM addition.
    
    general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
    KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
    CPU: 1 PID: 3591 Comm: syz-executor153 Not tainted 5.17.0-rc3-syzkaller-00316-gb81b1829e7e3 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:sk_prot_mem_limits include/net/sock.h:1523 [inline]
    RIP: 0010:sock_reserve_memory+0x1d7/0x330 net/core/sock.c:1000
    Code: 08 00 74 08 48 89 ef e8 27 20 bb f9 4c 03 7c 24 10 48 8b 6d 00 48 83 c5 08 48 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 ef e8 fb 1f bb f9 48 8b 6d 00 4c 89 ff 48
    RSP: 0018:ffffc90001f1fb68 EFLAGS: 00010202
    RAX: 0000000000000001 RBX: ffff88814aabc000 RCX: dffffc0000000000
    RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff90e18120
    RBP: 0000000000000008 R08: dffffc0000000000 R09: fffffbfff21c3025
    R10: fffffbfff21c3025 R11: 0000000000000000 R12: ffffffff8d109840
    R13: 0000000000001002 R14: 0000000000000001 R15: 0000000000000001
    FS:  0000555556e08300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007fc74416f130 CR3: 0000000073d9e000 CR4: 00000000003506e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     sock_setsockopt+0x14a9/0x3a30 net/core/sock.c:1446
     __sys_setsockopt+0x5af/0x980 net/socket.c:2176
     __do_sys_setsockopt net/socket.c:2191 [inline]
     __se_sys_setsockopt net/socket.c:2188 [inline]
     __x64_sys_setsockopt+0xb1/0xc0 net/socket.c:2188
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7fc7440fddc9
    Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007ffe98f07968 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
    RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fc7440fddc9
    RDX: 0000000000000049 RSI: 0000000000000001 RDI: 0000000000000004
    RBP: 0000000000000000 R08: 0000000000000004 R09: 00007ffe98f07990
    R10: 0000000020000000 R11: 0000000000000246 R12: 00007ffe98f0798c
    R13: 00007ffe98f079a0 R14: 00007ffe98f079e0 R15: 0000000000000000
     </TASK>
    Modules linked in:
    ---[ end trace 0000000000000000 ]---
    RIP: 0010:sk_prot_mem_limits include/net/sock.h:1523 [inline]
    RIP: 0010:sock_reserve_memory+0x1d7/0x330 net/core/sock.c:1000
    Code: 08 00 74 08 48 89 ef e8 27 20 bb f9 4c 03 7c 24 10 48 8b 6d 00 48 83 c5 08 48 89 e8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 ef e8 fb 1f bb f9 48 8b 6d 00 4c 89 ff 48
    RSP: 0018:ffffc90001f1fb68 EFLAGS: 00010202
    RAX: 0000000000000001 RBX: ffff88814aabc000 RCX: dffffc0000000000
    RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff90e18120
    RBP: 0000000000000008 R08: dffffc0000000000 R09: fffffbfff21c3025
    R10: fffffbfff21c3025 R11: 0000000000000000 R12: ffffffff8d109840
    R13: 0000000000001002 R14: 0000000000000001 R15: 0000000000000001
    FS:  0000555556e08300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007fc74416f130 CR3: 0000000073d9e000 CR4: 00000000003506e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    
    Fixes: 2bb2f5fb21b0 ("net: add new socket option SO_RESERVE_MEM")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Wei Wang <weiwan@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b465c0dc83be93428eddff82b7bd4479759a0163
Merge: 525b108e6d95b bdc120a2bcd83
Author: David S. Miller <davem@davemloft.net>
Date:   Tue Feb 15 14:22:05 2022 +0000

    Merge tag 'ieee802154-for-net-2022-02-15' of git://git.kernel.org/pub/scm/linux/kernel/git/sschmidt/wpan
    
    Stefan Schmidt says:
    
    ====================
    Only a single fix this time.
    Miquel Raynal fixed the lifs/sifs periods in the ca82010 to take the actual
    symbol duration time into account.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 525b108e6d95b643eccbd84fb10aa9aa101b18dd
Author: DENG Qingfang <dqfext@gmail.com>
Date:   Wed Feb 9 22:39:47 2022 +0800

    net: phy: mediatek: remove PHY mode check on MT7531
    
    The function mt7531_phy_mode_supported in the DSA driver set supported
    mode to PHY_INTERFACE_MODE_GMII instead of PHY_INTERFACE_MODE_INTERNAL
    for the internal PHY, so this check breaks the PHY initialization:
    
    mt7530 mdio-bus:00 wan (uninitialized): failed to connect to PHY: -EINVAL
    
    Remove the check to make it work again.
    
    Reported-by: Hauke Mehrtens <hauke@hauke-m.de>
    Fixes: e40d2cca0189 ("net: phy: add MediaTek Gigabit Ethernet PHY driver")
    Signed-off-by: DENG Qingfang <dqfext@gmail.com>
    Acked-by: Arınç ÜNAL <arinc.unal@arinc9.com>
    Tested-by: Hauke Mehrtens <hauke@hauke-m.de>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 243a1dd7ba48c120986dd9e66fee74bcb7751034
Author: Hongyu Xie <xiehongyu1@kylinos.cn>
Date:   Tue Feb 15 14:33:20 2022 +0200

    xhci: Prevent futile URB re-submissions due to incorrect return value.
    
    The -ENODEV return value from xhci_check_args() is incorrectly changed
    to -EINVAL in a couple places before propagated further.
    
    xhci_check_args() returns 4 types of value, -ENODEV, -EINVAL, 1 and 0.
    xhci_urb_enqueue and xhci_check_streams_endpoint return -EINVAL if
    the return value of xhci_check_args <= 0.
    This causes problems for example r8152_submit_rx, calling usb_submit_urb
    in drivers/net/usb/r8152.c.
    r8152_submit_rx will never get -ENODEV after submiting an urb when xHC
    is halted because xhci_urb_enqueue returns -EINVAL in the very beginning.
    
    [commit message and header edit -Mathias]
    
    Fixes: 203a86613fb3 ("xhci: Avoid NULL pointer deref when host dies.")
    Cc: stable@vger.kernel.org
    Signed-off-by: Hongyu Xie <xiehongyu1@kylinos.cn>
    Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
    Link: https://lore.kernel.org/r/20220215123320.1253947-3-mathias.nyman@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 8b328f8002bcf29ef517ee4bf234e09aabec4d2e
Author: Puma Hsu <pumahsu@google.com>
Date:   Tue Feb 15 14:33:19 2022 +0200

    xhci: re-initialize the HC during resume if HCE was set
    
    When HCE(Host Controller Error) is set, it means an internal
    error condition has been detected. Software needs to re-initialize
    the HC, so add this check in xhci resume.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Puma Hsu <pumahsu@google.com>
    Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
    Link: https://lore.kernel.org/r/20220215123320.1253947-2-mathias.nyman@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d7c93a903f33ff35aa0e6b5a8032eb9755b00826
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sun Feb 13 14:05:16 2022 +0100

    usb: dwc3: pci: Add "snps,dis_u2_susphy_quirk" for Intel Bay Trail
    
    Commit e0082698b689 ("usb: dwc3: ulpi: conditionally resume ULPI PHY")
    fixed an issue where ULPI transfers would timeout if any requests where
    send to the phy sometime after init, giving it enough time to auto-suspend.
    
    Commit e5f4ca3fce90 ("usb: dwc3: ulpi: Fix USB2.0 HS/FS/LS PHY suspend
    regression") changed the behavior to instead of clearing the
    DWC3_GUSB2PHYCFG_SUSPHY bit, add an extra sleep when it is set.
    
    But on Bay Trail devices, when phy_set_mode() gets called during init,
    this leads to errors like these:
    [   28.451522] tusb1210 dwc3.ulpi: error -110 writing val 0x01 to reg 0x0a
    [   28.464089] tusb1210 dwc3.ulpi: error -110 writing val 0x01 to reg 0x0a
    
    Add "snps,dis_u2_susphy_quirk" to the settings for Bay Trail devices to
    fix this. This restores the old behavior for Bay Trail devices, since
    previously the DWC3_GUSB2PHYCFG_SUSPHY bit would get cleared on the first
    ulpi_read/_write() and then was never set again.
    
    Fixes: e5f4ca3fce90 ("usb: dwc3: ulpi: Fix USB2.0 HS/FS/LS PHY suspend regression")
    Cc: stable@kernel.org
    Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220213130524.18748-2-hdegoede@redhat.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 038438a25c45d5ac996e95a22fa9e76ff3d1f8c7
Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Date:   Mon Feb 14 17:19:48 2022 +0300

    usb: dwc3: pci: add support for the Intel Raptor Lake-S
    
    This patch adds the necessary PCI ID for Intel Raptor Lake-S
    devices.
    
    Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Link: https://lore.kernel.org/r/20220214141948.18637-1-heikki.krogerus@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit fe663df7825811358531dc2e8a52d9eaa5e3515e
Author: Anders Roxell <anders.roxell@linaro.org>
Date:   Fri Feb 11 01:51:13 2022 +0100

    powerpc/lib/sstep: fix 'ptesync' build error
    
    Building tinyconfig with gcc (Debian 11.2.0-16) and assembler (Debian
    2.37.90.20220207) the following build error shows up:
    
      {standard input}: Assembler messages:
      {standard input}:2088: Error: unrecognized opcode: `ptesync'
      make[3]: *** [/builds/linux/scripts/Makefile.build:287: arch/powerpc/lib/sstep.o] Error 1
    
    Add the 'ifdef CONFIG_PPC64' around the 'ptesync' in function
    'emulate_update_regs()' to like it is in 'analyse_instr()'. Since it looks like
    it got dropped inadvertently by commit 3cdfcbfd32b9 ("powerpc: Change
    analyse_instr so it doesn't modify *regs").
    
    A key detail is that analyse_instr() will never recognise lwsync or
    ptesync on 32-bit (because of the existing ifdef), and as a result
    emulate_update_regs() should never be called with an op specifying
    either of those on 32-bit. So removing them from emulate_update_regs()
    should be a nop in terms of runtime behaviour.
    
    Fixes: 3cdfcbfd32b9 ("powerpc: Change analyse_instr so it doesn't modify *regs")
    Cc: stable@vger.kernel.org # v4.14+
    Suggested-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
    [mpe: Add last paragraph of change log mentioning analyse_instr() details]
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220211005113.1361436-1-anders.roxell@linaro.org

commit 5de717974005fcad2502281e9f82e139ca91f4bb
Author: Wolfram Sang <wsa@kernel.org>
Date:   Sat Feb 12 20:47:07 2022 +0100

    i2c: qup: allow COMPILE_TEST
    
    Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
    and easier maintenance.
    
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit 2ce4462f2724d1b3cedccea441c6d18bb360629a
Author: Wolfram Sang <wsa@kernel.org>
Date:   Sat Feb 12 20:46:57 2022 +0100

    i2c: imx: allow COMPILE_TEST
    
    Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
    and easier maintenance.
    
    Signed-off-by: Wolfram Sang <wsa@kernel.org>
    Acked-by: Oleksij Rempel <o.rempel@pengutronix.de>

commit 0b0dcb3882c8f08bdeafa03adb4487e104d26050
Author: Wolfram Sang <wsa@kernel.org>
Date:   Sat Feb 12 20:45:48 2022 +0100

    i2c: cadence: allow COMPILE_TEST
    
    Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
    and easier maintenance.
    
    Signed-off-by: Wolfram Sang <wsa@kernel.org>
    Acked-by: Michal Simek <michal.simek@xilinx.com>

commit 455896c53d5b803733ddd84e1bf8a430644439b6
Author: Yongzhi Liu <lyz_cs@pku.edu.cn>
Date:   Sat Jan 15 21:34:56 2022 -0800

    dmaengine: shdma: Fix runtime PM imbalance on error
    
    pm_runtime_get_() increments the runtime PM usage counter even
    when it returns an error code, thus a matching decrement is needed on
    the error handling path to keep the counter balanced.
    
    Signed-off-by: Yongzhi Liu <lyz_cs@pku.edu.cn>
    Link: https://lore.kernel.org/r/1642311296-87020-1-git-send-email-lyz_cs@pku.edu.cn
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit da2ad87fba0891576aadda9161b8505fde81a84d
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Jan 11 09:12:39 2022 +0800

    dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size
    
    As the possible failure of the dma_set_max_seg_size(), it should be
    better to check the return value of the dma_set_max_seg_size().
    
    Fixes: 97d49c59e219 ("dmaengine: rcar-dmac: set scatter/gather max segment size")
    Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Link: https://lore.kernel.org/r/20220111011239.452837-1-jiasheng@iscas.ac.cn
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit e831c7aba950f3ae94002b10321279654525e5ec
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Sat Jan 8 08:53:36 2022 +0000

    dmaengine: stm32-dmamux: Fix PM disable depth imbalance in stm32_dmamux_probe
    
    The pm_runtime_enable will increase power disable depth.
    If the probe fails, we should use pm_runtime_disable() to balance
    pm_runtime_enable().
    
    Fixes: 4f3ceca254e0 ("dmaengine: stm32-dmamux: Add PM Runtime support")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
    Link: https://lore.kernel.org/r/20220108085336.11992-1-linmq006@gmail.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 2d21543efe332cd8c8f212fb7d365bc8b0690bfa
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Thu Jan 6 11:09:39 2022 +0800

    dmaengine: sh: rcar-dmac: Check for error num after setting mask
    
    Because of the possible failure of the dma_supported(), the
    dma_set_mask_and_coherent() may return error num.
    Therefore, it should be better to check it and return the error if
    fails.
    
    Fixes: dc312349e875 ("dmaengine: rcar-dmac: Widen DMA mask to 40 bits")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Link: https://lore.kernel.org/r/20220106030939.2644320-1-jiasheng@iscas.ac.cn
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit aa7accb7f91c4c2c98bfdde62446d96ecc1ef2c6
Author: Yang Yingliang <yangyingliang@huawei.com>
Date:   Fri Jan 7 10:40:47 2022 +0800

    dmaengine: at_xdmac: Fix missing unlock in at_xdmac_tasklet()
    
    Add the missing unlock before return from at_xdmac_tasklet().
    
    Fixes: e77e561925df ("dmaengine: at_xdmac: Fix race over irq_status")
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
    Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
    Link: https://lore.kernel.org/r/20220107024047.1051915-1-yangyingliang@huawei.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 032062f363b4bf02b1d547f329aa5d97b6a17410
Author: Jon Maloy <jmaloy@redhat.com>
Date:   Sun Feb 13 20:38:52 2022 -0500

    tipc: fix wrong publisher node address in link publications
    
    When a link comes up we add its presence to the name table to make it
    possible for users to subscribe for link up/down events. However, after
    a previous call signature change the binding is wrongly published with
    the peer node as publishing node, instead of the own node as it should
    be. This has the effect that the command 'tipc name table show' will
    list the link binding (service type 2) with node scope and a peer node
    as originator, something that obviously is impossible.
    
    We correct this bug here.
    
    Fixes: 50a3499ab853 ("tipc: simplify signature of tipc_namtbl_publish()")
    Signed-off-by: Jon Maloy <jmaloy@redhat.com>
    Link: https://lore.kernel.org/r/20220214013852.2803940-1-jmaloy@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3c62fd3406e0b2277c76a6984d3979c7f3f1d129
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Feb 5 07:58:44 2022 +0100

    dmaengine: ptdma: Fix the error handling path in pt_core_init()
    
    In order to free resources correctly in the error handling path of
    pt_core_init(), 2 goto's have to be switched. Otherwise, some resources
    will leak and we will try to release things that have not been allocated
    yet.
    
    Also move a dev_err() to a place where it is more meaningful.
    
    Fixes: fa5d823b16a9 ("dmaengine: ptdma: Initial driver for the AMD PTDMA")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Acked-by: Sanjay R Mehta <sanju.mehta@amd.com>
    Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/41a963a35173f89c874f5c44df5530dc09fea8da.1644044244.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 382e3e0eb6a83f1cf73d4dfa3448ade1ed721f22
Author: Steev Klimaszewski <steev@kali.org>
Date:   Thu Nov 4 22:52:32 2021 -0500

    arm64: dts: qcom: c630: disable crypto due to serror
    
    Disable the crypto block due to it causing an SError in qce_start() on
    the C630, which happens upon every boot when cryptomanager tests are
    enabled.
    
    Signed-off-by: Steev Klimaszewski <steev@kali.org>
    [bjorn: Reworked commit message]
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20211105035235.2392-1-steev@kali.org

commit 10af115646171afc0217177d6eae92917b785897
Author: Jinyoung Choi <j-young.choi@samsung.com>
Date:   Mon Feb 14 19:33:52 2022 +0900

    scsi: ufs: core: Fix divide by zero in ufshcd_map_queues()
    
    Before calling blk_mq_map_queues(), the mq_map and nr_queues belonging to
    struct blk_mq_queue_map must have a valid value.
    
    If nr_queues is set to 0, the system may encounter a divide by zero
    depending on the type of architecture.
    
        blk_mq_map_queues() -> queue_index()
    
    Link: https://lore.kernel.org/r/1891546521.01644873481638.JavaMail.epsvc@epcpadp4
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Jinyoung Choi <j-young.choi@samsung.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 7f4c5a26f735dea4bbc0eb8eb9da99cda95a8563
Author: James Smart <jsmart2021@gmail.com>
Date:   Sat Feb 12 08:31:20 2022 -0800

    scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop
    
    When connected point to point, the driver does not know the FC4's supported
    by the other end. In Fabrics, it can query the nameserver.  Thus the driver
    must send PRLIs for the FC4s it supports and enable support based on the
    acc(ept) or rej(ect) of the respective FC4 PRLI.  Currently the driver
    supports SCSI and NVMe PRLIs.
    
    Unfortunately, although the behavior is per standard, many devices have
    come to expect only SCSI PRLIs. In this particular example, the NVMe PRLI
    is properly RJT'd but the target decided that it must LOGO after seeing the
    unexpected NVMe PRLI. The LOGO causes the sequence to restart and login is
    now in an infinite failure loop.
    
    Fix the problem by having the driver, on a pt2pt link, remember NVMe PRLI
    accept or reject status across logout as long as the link stays "up".  When
    retrying login, if the prior NVMe PRLI was rejected, it will not be sent on
    the next login.
    
    Link: https://lore.kernel.org/r/20220212163120.15385-1-jsmart2021@gmail.com
    Cc: <stable@vger.kernel.org> # v5.4+
    Reviewed-by: Ewan D. Milne <emilne@redhat.com>
    Signed-off-by: James Smart <jsmart2021@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 6fec1ab67f8d60704cc7de64abcfd389ab131542
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 14 09:36:57 2022 +0100

    selftests/ftrace: Do not trace do_softirq because of PREEMPT_RT
    
    The PREEMPT_RT patchset does not use do_softirq() function thus trying
    to filter for do_softirq fails for such kernel:
    
      echo do_softirq
      ftracetest: 81: echo: echo: I/O error
    
    Choose some other visible function for the test.  The function does not
    have to be actually executed during the test, because it is only testing
    filter API interface.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 5feef64f4c67068c49f5409d43c67cabf2327f66
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon Jan 31 14:26:22 2022 +0100

    RISC-V: Fix IPI/RFENCE hmask on non-monotonic hartid ordering
    
    If the boot CPU does not have the lowest hartid, "hartid - hbase" can
    become negative, leading to an incorrect hmask, causing userspace to
    crash with SEGV.  This is observed on e.g. Starlight Beta, where cpuid 1
    maps to hartid 0, and cpuid 0 maps to hartid 1.
    
    Fix this by detecting this case, and shifting the accumulated mask and
    updating hbase, if possible.
    
    Fixes: 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for hartid bitmap")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Atish Patra <atishp@rivosinc.com>
    Tested-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 2b35d5b7d13062b805aa82dc53812a5f56249287
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon Jan 31 14:26:21 2022 +0100

    RISC-V: Fix handling of empty cpu masks
    
    The cpumask rework slightly changed the behavior of the code.  Fix this
    by treating an empty cpumask as meaning all online CPUs.
    
    Extracted from a patch by Atish Patra <atishp@rivosinc.com>.
    
    Reported-by: Jessica Clarke <jrtc27@jrtc27.com>
    Fixes: 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for hartid bitmap")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 12f4a665cc3568328728e46c3162873b5b69cd27
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon Jan 31 14:26:20 2022 +0100

    RISC-V: Fix hartid mask handling for hartid 31 and up
    
    Jessica reports that using "1 << hartid" causes undefined behavior for
    hartid 31 and up.
    
    Fix this by using the BIT() helper instead of an explicit shift.
    
    Reported-by: Jessica Clarke <jrtc27@jrtc27.com>
    Fixes: 26fb751ca37846c9 ("RISC-V: Do not use cpumask data structure for hartid bitmap")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 364438fd629f7611a84c8e6d7de91659300f1502
Author: Nicholas Bishop <nicholasbishop@google.com>
Date:   Fri Feb 11 14:57:39 2022 -0500

    drm/radeon: Fix backlight control on iMac 12,1
    
    The iMac 12,1 does not use the gmux driver for backlight, so the radeon
    backlight device is needed to set the brightness.
    
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1838
    Signed-off-by: Nicholas Bishop <nicholasbishop@google.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 9c4f59ea3f865693150edf0c91d1cc6b451360dd
Author: Yifan Zhang <yifan1.zhang@amd.com>
Date:   Fri Feb 11 17:58:08 2022 +0800

    drm/amd/pm: correct the sequence of sending gpu reset msg
    
    the 2nd parameter should be smu msg type rather than asic msg index.
    
    Fixes: 7d38d9dc4ecc ("drm/amdgpu: add mode2 reset support for yellow carp")
    Signed-off-by: Yifan Zhang <yifan1.zhang@amd.com>
    Acked-by: Aaron Liu <aaron.liu@amd.com>
    Reviewed-by: Huang Rui <ray.huang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit f8f4e2a518347063179def4e64580b2d28233d03
Author: Rajib Mahapatra <rajib.mahapatra@amd.com>
Date:   Thu Feb 10 18:46:40 2022 +0530

    drm/amdgpu: skipping SDMA hw_init and hw_fini for S0ix.
    
    [Why]
    SDMA ring buffer test failed if suspend is aborted during
    S0i3 resume.
    
    [How]
    If suspend is aborted for some reason during S0i3 resume
    cycle, it follows SDMA ring test failing and errors in amdgpu
    resume. For RN/CZN/Picasso, SMU saves and restores SDMA
    registers during S0ix cycle. So, skipping SDMA suspend and
    resume from driver solves the issue. This time, the system
    is able to resume gracefully even the suspend is aborted.
    
    Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Rajib Mahapatra <rajib.mahapatra@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 0136f5844b006e2286f873457c3fcba8c45a3735
Author: Evan Quan <evan.quan@amd.com>
Date:   Tue Jan 18 14:07:51 2022 +0800

    drm/amd/pm: correct UMD pstate clocks for Dimgrey Cavefish and Beige Goby
    
    Correct the UMD pstate profiling clocks for Dimgrey Cavefish and Beige
    Goby.
    
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit e0caaf75d443e02e55e146fd75fe2efc8aed5540
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Tue Feb 8 13:38:23 2022 -0500

    NFS: LOOKUP_DIRECTORY is also ok with symlinks
    
    Commit ac795161c936 (NFSv4: Handle case where the lookup of a directory
    fails) [1], part of Linux since 5.17-rc2, introduced a regression, where
    a symbolic link on an NFS mount to a directory on another NFS does not
    resolve(?) the first time it is accessed:
    
    Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Fixes: ac795161c936 ("NFSv4: Handle case where the lookup of a directory fails")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Tested-by: Donald Buczek <buczek@molgen.mpg.de>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 9d047bf68fe8cdb4086deaf4edd119731a9481ed
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Tue Feb 8 12:14:44 2022 -0500

    NFS: Remove an incorrect revalidation in nfs4_update_changeattr_locked()
    
    In nfs4_update_changeattr_locked(), we don't need to set the
    NFS_INO_REVAL_PAGECACHE flag, because we already know the value of the
    change attribute, and we're already flagging the size. In fact, this
    forces us to revalidate the change attribute a second time for no good
    reason.
    This extra flag appears to have been introduced as part of the xattr
    feature, when update_changeattr_locked() was converted for use by the
    xattr code.
    
    Fixes: 1b523ca972ed ("nfs: modify update_changeattr to deal with regular files")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 05c7b7a92cc87ff8d7fde189d0fade250697573c
Author: Zhang Qiao <zhangqiao22@huawei.com>
Date:   Fri Jan 21 18:12:10 2022 +0800

    cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug
    
    As previously discussed(https://lkml.org/lkml/2022/1/20/51),
    cpuset_attach() is affected with similar cpu hotplug race,
    as follow scenario:
    
         cpuset_attach()                            cpu hotplug
        ---------------------------            ----------------------
        down_write(cpuset_rwsem)
        guarantee_online_cpus() // (load cpus_attach)
                                            sched_cpu_deactivate
                                              set_cpu_active()
                                              // will change cpu_active_mask
        set_cpus_allowed_ptr(cpus_attach)
          __set_cpus_allowed_ptr_locked()
           // (if the intersection of cpus_attach and
             cpu_active_mask is empty, will return -EINVAL)
        up_write(cpuset_rwsem)
    
    To avoid races such as described above, protect cpuset_attach() call
    with cpu_hotplug_lock.
    
    Fixes: be367d099270 ("cgroups: let ss->can_attach and ss->attach do whole threadgroups at a time")
    Cc: stable@vger.kernel.org # v2.6.32+
    Reported-by: Zhao Gongyi <zhaogongyi@huawei.com>
    Signed-off-by: Zhang Qiao <zhangqiao22@huawei.com>
    Acked-by: Waiman Long <longman@redhat.com>
    Reviewed-by: Michal Koutný <mkoutny@suse.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 0bc2ba49101f4ca35e0c878968adb5660ffa2517
Author: Jiri Olsa <jolsa@kernel.org>
Date:   Tue Feb 8 23:11:17 2022 +0100

    MAINTAINERS: Update Jiri's email address
    
    Using my kernel.org email.
    
    Signed-off-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20220208221117.710405-1-jolsa@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 4f6de676d94ee8ddfc2e7e7cd935fc7cb2feff3a
Author: Joakim Tjernlund <joakim.tjernlund@infinera.com>
Date:   Mon Feb 14 18:56:43 2022 +0100

    arm64: Correct wrong label in macro __init_el2_gicv3
    
    In commit:
    
      114945d84a30a5fe ("arm64: Fix labels in el2_setup macros")
    
    We renamed a label from '1' to '.Lskip_gicv3_\@', but failed to update
    a branch to it, which now targets a later label also called '1'.
    
    The branch is taken rarely, when GICv3 is present but SRE is disabled
    at EL3, causing a boot-time crash.
    
    Update the caller to the new label name.
    
    Fixes: 114945d84a30 ("arm64: Fix labels in el2_setup macros")
    Cc: <stable@vger.kernel.org> # 5.12.x
    Signed-off-by: Joakim Tjernlund <joakim.tjernlund@infinera.com>
    Link: https://lore.kernel.org/r/20220214175643.21931-1-joakim.tjernlund@infinera.com
    Reviewed-by: Mark Rutland <mark.rutland@arm.com>
    Reviewed-by: Marc Zyngier <maz@kernel.org>
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 6e8793674bb0d1135ca0e5c9f7e16fecbf815926
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Mon Feb 14 10:00:19 2022 -0800

    serial: parisc: GSC: fix build when IOSAPIC is not set
    
    There is a build error when using a kernel .config file from
    'kernel test robot' for a different build problem:
    
    hppa64-linux-ld: drivers/tty/serial/8250/8250_gsc.o: in function `.LC3':
    (.data.rel.ro+0x18): undefined reference to `iosapic_serial_irq'
    
    when:
      CONFIG_GSC=y
      CONFIG_SERIO_GSCPS2=y
      CONFIG_SERIAL_8250_GSC=y
      CONFIG_PCI is not set
        and hence PCI_LBA is not set.
      IOSAPIC depends on PCI_LBA, so IOSAPIC is not set/enabled.
    
    Make the use of iosapic_serial_irq() conditional to fix the build error.
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
    Cc: Helge Deller <deller@gmx.de>
    Cc: linux-parisc@vger.kernel.org
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: linux-serial@vger.kernel.org
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Johan Hovold <johan@kernel.org>
    Suggested-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 21bffcb76ee2fbafc7d5946cef10abc9df5cfff7
Author: Sherry Yang <sherry.yang@oracle.com>
Date:   Thu Feb 10 12:30:49 2022 -0800

    selftests/seccomp: Fix seccomp failure by adding missing headers
    
    seccomp_bpf failed on tests 47 global.user_notification_filter_empty
    and 48 global.user_notification_filter_empty_threaded when it's
    tested on updated kernel but with old kernel headers. Because old
    kernel headers don't have definition of macro __NR_clone3 which is
    required for these two tests. Since under selftests/, we can install
    headers once for all tests (the default INSTALL_HDR_PATH is
    usr/include), fix it by adding usr/include to the list of directories
    to be searched. Use "-isystem" to indicate it's a system directory as
    the real kernel headers directories are.
    
    Signed-off-by: Sherry Yang <sherry.yang@oracle.com>
    Tested-by: Sherry Yang <sherry.yang@oracle.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit d567f5db412ed52de0b3b3efca4a451263de6108
Merge: 754e0b0e35608 4e2a354e37758
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 14 09:51:26 2022 -0800

    Merge tag 'regulator-fix-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
    
    Pull regulator fix from Mark Brown:
     "One fix here, for initialisation of regulators that don't have an
      in_enabled() operation which would mainly impact cases where they
      aren't otherwise used during early setup for some reason"
    
    * tag 'regulator-fix-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:
      regulator: core: fix false positive in regulator_late_cleanup()

commit 5948342a526f43ffbd02ebac64670e55475b7e09
Merge: 2a845837e3d0d a887f9c7a4d37
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Feb 14 17:55:39 2022 +0100

    Merge tag 'asoc-fix-v5.17-rc4' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus
    
    ASoC: Fixes for v5.18
    
    More fixes that have arrived in the past few -rcs, plus a MAINTAINERS
    update.  The biggest update here is the fix for control change
    notifications in ASoC generic controls found by mixer-test.

commit 0c6f4ebf8835d01866eb686d47578cde80097981
Author: Ronnie Sahlberg <lsahlber@redhat.com>
Date:   Mon Feb 14 08:40:52 2022 +1000

    cifs: modefromsids must add an ACE for authenticated users
    
    When we create a file with modefromsids we set an ACL that
    has one ACE for the magic modefromsid as well as a second ACE that
    grants full access to all authenticated users.
    
    When later we chante the mode on the file we strip away this, and other,
    ACE for authenticated users in set_chmod_dacl() and then just add back/update
    the modefromsid ACE.
    Thus leaving the file with a single ACE that is for the mode and no ACE
    to grant any user any rights to access the file.
    Fix this by always adding back also the modefromsid ACE so that we do not
    drop the rights to access the file.
    
    Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit c49ae619905eebd3f54598a84e4cd2bd58ba8fe9
Author: Pali Rohár <pali@kernel.org>
Date:   Mon Feb 14 12:02:28 2022 +0100

    PCI: mvebu: Fix device enumeration regression
    
    Jan reported that on Turris Omnia (Armada 385), no PCIe devices were
    detected after upgrading from v5.16.1 to v5.16.3 and identified the cause
    as the backport of 91a8d79fc797 ("PCI: mvebu: Fix configuring secondary bus
    of PCIe Root Port via emulated bridge"), which appeared in v5.17-rc1.
    
    91a8d79fc797 was incorrectly applied from mailing list patch [1] to the
    linux git repository [2] probably due to resolving merge conflicts
    incorrectly. Fix it now.
    
    [1] https://lore.kernel.org/r/20211125124605.25915-12-pali@kernel.org
    [2] https://git.kernel.org/linus/91a8d79fc797
    
    [bhelgaas: commit log]
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215540
    Fixes: 91a8d79fc797 ("PCI: mvebu: Fix configuring secondary bus of PCIe Root Port via emulated bridge")
    Link: https://lore.kernel.org/r/20220214110228.25825-1-pali@kernel.org
    Link: https://lore.kernel.org/r/20220127234917.GA150851@bhelgaas
    Reported-by: Jan Palus <jpalus@fastmail.com>
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 7f016b35ca7623c71b31facdde080e8ce171a697
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Tue Feb 8 17:51:12 2022 +0530

    HID: amd_sfh: Add interrupt handler to process interrupts
    
    On newer AMD platforms with SFH, it is observed that random interrupts
    get generated on the SFH hardware and until this is cleared the firmware
    sensor processing is stalled, resulting in no data been received to
    driver side.
    
    Add routines to handle these interrupts, so that firmware operations are
    not stalled.
    
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit fb75a3791a8032848c987db29b622878d8fe2b1c
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Tue Feb 8 17:51:11 2022 +0530

    HID: amd_sfh: Add functionality to clear interrupts
    
    Newer AMD platforms with SFH may generate interrupts on some events
    which are unwarranted. Until this is cleared the actual MP2 data
    processing maybe stalled in some cases.
    
    Add a mechanism to clear the pending interrupts (if any) during the
    driver initialization and sensor command operations.
    
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit b300667b33b2b5a2c8e5f8f22826befb3d7f4f2b
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Tue Feb 8 17:51:10 2022 +0530

    HID: amd_sfh: Disable the interrupt for all command
    
    Sensor data is processed in polling mode. Hence disable the interrupt
    for all sensor command.
    
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit aa0b724a2bf041036e56cbb3b4b3afde7c5e7c9e
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Tue Feb 8 17:51:09 2022 +0530

    HID: amd_sfh: Correct the structure field name
    
    Misinterpreted intr_enable field name. Hence correct the structure
    field name accordingly to reflect the functionality.
    
    Fixes: f264481ad614 ("HID: amd_sfh: Extend driver capabilities for multi-generation support")
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 0cf74235f4403b760a37f77271d2ca3424001ff9
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Tue Feb 8 17:51:08 2022 +0530

    HID: amd_sfh: Handle amd_sfh work buffer in PM ops
    
    Since in the current amd_sfh design the sensor data is periodically
    obtained in the form of poll data, during the suspend/resume cycle,
    scheduling a delayed work adds no value.
    
    So, cancel the work and restart back during the suspend/resume cycle
    respectively.
    
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 6605cc67ca18b9d583eb96e18a20f5f4e726103c
Author: Oliver Neukum <oneukum@suse.com>
Date:   Mon Feb 14 15:08:18 2022 +0100

    USB: zaurus: support another broken Zaurus
    
    This SL-6000 says Direct Line, not Ethernet
    
    v2: added Reporter and Link
    
    Signed-off-by: Oliver Neukum <oneukum@suse.com>
    Reported-by: Ross Maynard <bids.7405@bigpond.com>
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215361
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 603c692d574185a1fffc9549e8e30f27bd7dba6c
Author: Nikolay Aleksandrov <nikolay@nvidia.com>
Date:   Mon Feb 14 13:23:32 2022 +0200

    MAINTAINERS: bridge: update my email
    
    I'm leaving NVIDIA and my email account will stop working in a week, update
    it with my personal account.
    
    Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0fc95dec096c2133942c382396172ae4487b4d57
Author: Alex Maydanik <alexander.maydanik@gmail.com>
Date:   Sat Feb 12 12:29:27 2022 +0200

    net: fix documentation for kernel_getsockname
    
    Fixes return value documentation of kernel_getsockname()
    and kernel_getpeername() functions.
    
    The previous documentation wrongly specified that the return
    value is 0 in case of success, however sock->ops->getname returns
    the length of the address in bytes in case of success.
    
    Signed-off-by: Alex Maydanik <alexander.maydanik@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5891cd5ec46c2c2eb6427cb54d214b149635dd0e
Author: Eric Dumazet <edumazet@google.com>
Date:   Fri Feb 11 12:06:23 2022 -0800

    net_sched: add __rcu annotation to netdev->qdisc
    
    syzbot found a data-race [1] which lead me to add __rcu
    annotations to netdev->qdisc, and proper accessors
    to get LOCKDEP support.
    
    [1]
    BUG: KCSAN: data-race in dev_activate / qdisc_lookup_rcu
    
    write to 0xffff888168ad6410 of 8 bytes by task 13559 on cpu 1:
     attach_default_qdiscs net/sched/sch_generic.c:1167 [inline]
     dev_activate+0x2ed/0x8f0 net/sched/sch_generic.c:1221
     __dev_open+0x2e9/0x3a0 net/core/dev.c:1416
     __dev_change_flags+0x167/0x3f0 net/core/dev.c:8139
     rtnl_configure_link+0xc2/0x150 net/core/rtnetlink.c:3150
     __rtnl_newlink net/core/rtnetlink.c:3489 [inline]
     rtnl_newlink+0xf4d/0x13e0 net/core/rtnetlink.c:3529
     rtnetlink_rcv_msg+0x745/0x7e0 net/core/rtnetlink.c:5594
     netlink_rcv_skb+0x14e/0x250 net/netlink/af_netlink.c:2494
     rtnetlink_rcv+0x18/0x20 net/core/rtnetlink.c:5612
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x602/0x6d0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x728/0x850 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmsg+0x195/0x230 net/socket.c:2496
     __do_sys_sendmsg net/socket.c:2505 [inline]
     __se_sys_sendmsg net/socket.c:2503 [inline]
     __x64_sys_sendmsg+0x42/0x50 net/socket.c:2503
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffff888168ad6410 of 8 bytes by task 13560 on cpu 0:
     qdisc_lookup_rcu+0x30/0x2e0 net/sched/sch_api.c:323
     __tcf_qdisc_find+0x74/0x3a0 net/sched/cls_api.c:1050
     tc_del_tfilter+0x1c7/0x1350 net/sched/cls_api.c:2211
     rtnetlink_rcv_msg+0x5ba/0x7e0 net/core/rtnetlink.c:5585
     netlink_rcv_skb+0x14e/0x250 net/netlink/af_netlink.c:2494
     rtnetlink_rcv+0x18/0x20 net/core/rtnetlink.c:5612
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x602/0x6d0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x728/0x850 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmsg+0x195/0x230 net/socket.c:2496
     __do_sys_sendmsg net/socket.c:2505 [inline]
     __se_sys_sendmsg net/socket.c:2503 [inline]
     __x64_sys_sendmsg+0x42/0x50 net/socket.c:2503
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0xffffffff85dee080 -> 0xffff88815d96ec00
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 13560 Comm: syz-executor.2 Not tainted 5.17.0-rc3-syzkaller-00116-gf1baf68e1383-dirty #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 470502de5bdb ("net: sched: unlock rules update API")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Vlad Buslov <vladbu@mellanox.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Cc: Jamal Hadi Salim <jhs@mojatatu.com>
    Cc: Cong Wang <xiyou.wangcong@gmail.com>
    Cc: Jiri Pirko <jiri@resnulli.us>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a2614140dc0f467a83aa3bb4b6ee2d6480a76202
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Fri Feb 11 19:45:06 2022 +0200

    net: dsa: mv88e6xxx: flush switchdev FDB workqueue before removing VLAN
    
    mv88e6xxx is special among DSA drivers in that it requires the VTU to
    contain the VID of the FDB entry it modifies in
    mv88e6xxx_port_db_load_purge(), otherwise it will return -EOPNOTSUPP.
    
    Sometimes due to races this is not always satisfied even if external
    code does everything right (first deletes the FDB entries, then the
    VLAN), because DSA commits to hardware FDB entries asynchronously since
    commit c9eb3e0f8701 ("net: dsa: Add support for learning FDB through
    notification").
    
    Therefore, the mv88e6xxx driver must close this race condition by
    itself, by asking DSA to flush the switchdev workqueue of any FDB
    deletions in progress, prior to exiting a VLAN.
    
    Fixes: c9eb3e0f8701 ("net: dsa: Add support for learning FDB through notification")
    Reported-by: Rafael Richter <rafael.richter@gin.de>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 26394fc118d6115390bd5b3a0fb17096271da227
Author: Ignat Korchagin <ignat@cloudflare.com>
Date:   Fri Feb 11 17:30:42 2022 +0000

    ipv6: mcast: use rcu-safe version of ipv6_get_lladdr()
    
    Some time ago 8965779d2c0e ("ipv6,mcast: always hold idev->lock before mca_lock")
    switched ipv6_get_lladdr() to __ipv6_get_lladdr(), which is rcu-unsafe
    version. That was OK, because idev->lock was held for these codepaths.
    
    In 88e2ca308094 ("mld: convert ifmcaddr6 to RCU") these external locks were
    removed, so we probably need to restore the original rcu-safe call.
    
    Otherwise, we occasionally get a machine crashed/stalled with the following
    in dmesg:
    
    [ 3405.966610][T230589] general protection fault, probably for non-canonical address 0xdead00000000008c: 0000 [#1] SMP NOPTI
    [ 3405.982083][T230589] CPU: 44 PID: 230589 Comm: kworker/44:3 Tainted: G           O      5.15.19-cloudflare-2022.2.1 #1
    [ 3405.998061][T230589] Hardware name: SUPA-COOL-SERV
    [ 3406.009552][T230589] Workqueue: mld mld_ifc_work
    [ 3406.017224][T230589] RIP: 0010:__ipv6_get_lladdr+0x34/0x60
    [ 3406.025780][T230589] Code: 57 10 48 83 c7 08 48 89 e5 48 39 d7 74 3e 48 8d 82 38 ff ff ff eb 13 48 8b 90 d0 00 00 00 48 8d 82 38 ff ff ff 48 39 d7 74 22 <66> 83 78 32 20 77 1b 75 e4 89 ca 23 50 2c 75 dd 48 8b 50 08 48 8b
    [ 3406.055748][T230589] RSP: 0018:ffff94e4b3fc3d10 EFLAGS: 00010202
    [ 3406.065617][T230589] RAX: dead00000000005a RBX: ffff94e4b3fc3d30 RCX: 0000000000000040
    [ 3406.077477][T230589] RDX: dead000000000122 RSI: ffff94e4b3fc3d30 RDI: ffff8c3a31431008
    [ 3406.089389][T230589] RBP: ffff94e4b3fc3d10 R08: 0000000000000000 R09: 0000000000000000
    [ 3406.101445][T230589] R10: ffff8c3a31430000 R11: 000000000000000b R12: ffff8c2c37887100
    [ 3406.113553][T230589] R13: ffff8c3a39537000 R14: 00000000000005dc R15: ffff8c3a31431000
    [ 3406.125730][T230589] FS:  0000000000000000(0000) GS:ffff8c3b9fc80000(0000) knlGS:0000000000000000
    [ 3406.138992][T230589] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 3406.149895][T230589] CR2: 00007f0dfea1db60 CR3: 000000387b5f2000 CR4: 0000000000350ee0
    [ 3406.162421][T230589] Call Trace:
    [ 3406.170235][T230589]  <TASK>
    [ 3406.177736][T230589]  mld_newpack+0xfe/0x1a0
    [ 3406.186686][T230589]  add_grhead+0x87/0xa0
    [ 3406.195498][T230589]  add_grec+0x485/0x4e0
    [ 3406.204310][T230589]  ? newidle_balance+0x126/0x3f0
    [ 3406.214024][T230589]  mld_ifc_work+0x15d/0x450
    [ 3406.223279][T230589]  process_one_work+0x1e6/0x380
    [ 3406.232982][T230589]  worker_thread+0x50/0x3a0
    [ 3406.242371][T230589]  ? rescuer_thread+0x360/0x360
    [ 3406.252175][T230589]  kthread+0x127/0x150
    [ 3406.261197][T230589]  ? set_kthread_struct+0x40/0x40
    [ 3406.271287][T230589]  ret_from_fork+0x22/0x30
    [ 3406.280812][T230589]  </TASK>
    [ 3406.288937][T230589] Modules linked in: ... [last unloaded: kheaders]
    [ 3406.476714][T230589] ---[ end trace 3525a7655f2f3b9e ]---
    
    Fixes: 88e2ca308094 ("mld: convert ifmcaddr6 to RCU")
    Reported-by: David Pinilla Caparros <dpini@cloudflare.com>
    Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2a845837e3d0ddaed493b4c5c4643d7f0542804d
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Feb 14 14:04:10 2022 +0100

    ALSA: hda/realtek: Fix deadlock by COEF mutex
    
    The recently introduced coef_mutex for Realtek codec seems causing a
    deadlock when the relevant code is invoked from the power-off state;
    then the HD-audio core tries to power-up internally, and this kicks
    off the codec runtime PM code that tries to take the same coef_mutex.
    
    In order to avoid the deadlock, do the temporary power up/down around
    the coef_mutex acquisition and release.  This assures that the
    power-up sequence runs before the mutex, hence no re-entrance will
    happen.
    
    Fixes: b837a9f5ab3b ("ALSA: hda: realtek: Fix race at concurrent COEF updates")
    Reported-and-tested-by: Julian Wollrath <jwollrath@web.de>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220214132838.4db10fca@schienar
    Link: https://lore.kernel.org/r/20220214130410.21230-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 9a5adeb28b77416446658e75bdef3bbe5fb92a83
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Feb 14 13:57:11 2022 +0100

    ALSA: usb-audio: Don't abort resume upon errors
    
    The default mixer resume code treats the errors at restoring the
    modified mixer items as a fatal error, and it returns back to the
    caller.  This ends up in the resume failure, and the device will be
    come unavailable, although basically those errors are intermittent and
    can be safely ignored.
    
    The problem itself has been present from the beginning, but it didn't
    hit usually because the code tries to resume only the modified items.
    But now with the recent commit to forcibly initialize each item at the
    probe time, the problem surfaced more often, hence it appears as a
    regression.
    
    This patch fixes the regression simply by ignoring the errors at
    resume.
    
    Fixes: b96681bd5827 ("ALSA: usb-audio: Initialize every feature unit once at probe time")
    Cc: <stable@vger.kernel.org>
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215561
    Link: https://lore.kernel.org/r/20220214125711.20531-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 710c476514313c74045c41c0571bb5178fd16e3d
Author: Jim Mattson <jmattson@google.com>
Date:   Wed Feb 2 17:48:13 2022 -0800

    KVM: x86/pmu: Use AMD64_RAW_EVENT_MASK for PERF_TYPE_RAW
    
    AMD's event select is 3 nybbles, with the high nybble in bits 35:32 of
    a PerfEvtSeln MSR. Don't mask off the high nybble when configuring a
    RAW perf event.
    
    Fixes: ca724305a2b0 ("KVM: x86/vPMU: Implement AMD vPMU code for KVM")
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Message-Id: <20220203014813.2130559-2-jmattson@google.com>
    Reviewed-by: David Dunn <daviddunn@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b8bfee85f1307426e0242d654f3a14c06ef639c5
Author: Jim Mattson <jmattson@google.com>
Date:   Wed Feb 2 17:48:12 2022 -0800

    KVM: x86/pmu: Don't truncate the PerfEvtSeln MSR when creating a perf event
    
    AMD's event select is 3 nybbles, with the high nybble in bits 35:32 of
    a PerfEvtSeln MSR. Don't drop the high nybble when setting up the
    config field of a perf_event_attr structure for a call to
    perf_event_create_kernel_counter().
    
    Fixes: ca724305a2b0 ("KVM: x86/vPMU: Implement AMD vPMU code for KVM")
    Reported-by: Stephane Eranian <eranian@google.com>
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Message-Id: <20220203014813.2130559-1-jmattson@google.com>
    Reviewed-by: David Dunn <daviddunn@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6b0b2d9a6a308bcd9300c2d83000a82812c56cea
Author: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Date:   Thu Feb 10 09:47:45 2022 -0600

    iommu/amd: Fix I/O page table memory leak
    
    The current logic updates the I/O page table mode for the domain
    before calling the logic to free memory used for the page table.
    This results in IOMMU page table memory leak, and can be observed
    when launching VM w/ pass-through devices.
    
    Fix by freeing the memory used for page table before updating the mode.
    
    Cc: Joerg Roedel <joro@8bytes.org>
    Reported-by: Daniel Jordan <daniel.m.jordan@oracle.com>
    Tested-by: Daniel Jordan <daniel.m.jordan@oracle.com>
    Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
    Fixes: e42ba0633064 ("iommu/amd: Restructure code for freeing page table")
    Link: https://lore.kernel.org/all/20220118194720.urjgi73b7c3tq2o6@oracle.com/
    Link: https://lore.kernel.org/r/20220210154745.11524-1-suravee.suthikulpanit@amd.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit 40eb0dcf4114cbfff4d207890fa5a19e82da9fdc
Author: Yang Yingliang <yangyingliang@huawei.com>
Date:   Thu Feb 10 17:10:53 2022 +0800

    tee: optee: fix error return code in probe function
    
    If teedev_open() fails, probe function need return
    error code.
    
    Fixes: aceeafefff73 ("optee: use driver internal tee_context for some rpc")
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
    Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>

commit dbd0b42350d5717786cb8257fbe5b528f3af9772
Author: Helge Deller <deller@gmx.de>
Date:   Sun Feb 13 22:52:11 2022 +0100

    parisc: Fix some apparent put_user() failures
    
    After commit 4b9d2a731c3d ("parisc: Switch user access functions
    to signal errors in r29 instead of r8") bash suddenly started
    to report those warnings after login:
    
    -bash: cannot set terminal process group (-1): Bad file descriptor
    -bash: no job control in this shell
    
    It turned out, that a function call inside a put_user(), e.g.:
    put_user(vt_do_kdgkbmode(console), (int __user *)arg);
    clobbered the error register (r29) and thus the put_user() call itself
    seem to have failed.
    
    Rearrange the C-code to pre-calculate the intermediate value
    and then do the put_user().
    Additionally prefer the "+" constraint on pu_err and gu_err registers
    to tell the compiler that those operands are both read and written by
    the assembly instruction.
    
    Reported-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Fixes: 4b9d2a731c3d ("parisc: Switch user access functions to signal errors in r29 instead of r8")
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 86006f996346e8a5a1ea80637ec949ceeea4ecbc
Author: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date:   Fri Feb 11 09:14:18 2022 -0800

    ice: enable parsing IPSEC SPI headers for RSS
    
    The COMMS package can enable the hardware parser to recognize IPSEC
    frames with ESP header and SPI identifier.  If this package is available
    and configured for loading in /lib/firmware, then the driver will
    succeed in enabling this protocol type for RSS.
    
    This in turn allows the hardware to hash over the SPI and use it to pick
    a consistent receive queue for the same secure flow. Without this all
    traffic is steered to the same queue for multiple traffic threads from
    the same IP address. For that reason this is marked as a fix, as the
    driver supports the model, but it wasn't enabled.
    
    If the package is not available, adding this type will fail, but the
    failure is ignored on purpose as it has no negative affect.
    
    Fixes: c90ed40cefe1 ("ice: Enable writing hardware filtering tables")
    Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com> (A Contingent worker at Intel)
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5ce97f4ec5e0f8726a5dda1710727b1ee9badcac
Author: Lennert Buytenhek <buytenh@wantstofly.org>
Date:   Mon Oct 4 13:07:24 2021 +0300

    iommu/amd: Recover from event log overflow
    
    The AMD IOMMU logs I/O page faults and such to a ring buffer in
    system memory, and this ring buffer can overflow.  The AMD IOMMU
    spec has the following to say about the interrupt status bit that
    signals this overflow condition:
    
            EventOverflow: Event log overflow. RW1C. Reset 0b. 1 = IOMMU
            event log overflow has occurred. This bit is set when a new
            event is to be written to the event log and there is no usable
            entry in the event log, causing the new event information to
            be discarded. An interrupt is generated when EventOverflow = 1b
            and MMIO Offset 0018h[EventIntEn] = 1b. No new event log
            entries are written while this bit is set. Software Note: To
            resume logging, clear EventOverflow (W1C), and write a 1 to
            MMIO Offset 0018h[EventLogEn].
    
    The AMD IOMMU driver doesn't currently implement this recovery
    sequence, meaning that if a ring buffer overflow occurs, logging
    of EVT/PPR/GA events will cease entirely.
    
    This patch implements the spec-mandated reset sequence, with the
    minor tweak that the hardware seems to want to have a 0 written to
    MMIO Offset 0018h[EventLogEn] first, before writing an 1 into this
    field, or the IOMMU won't actually resume logging events.
    
    Signed-off-by: Lennert Buytenhek <buytenh@arista.com>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/YVrSXEdW2rzEfOvk@wantstofly.org
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit dd8e5b161d7fb9cefa1f1d6e35a39b9e1563c8d3
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Feb 14 11:00:20 2022 +0100

    ALSA: hda: Fix missing codec probe on Shenker Dock 15
    
    By some unknown reason, BIOS on Shenker Dock 15 doesn't set up the
    codec mask properly for the onboard audio.  Let's set the forced codec
    mask to enable the codec discovery.
    
    Reported-by: dmummenschanz@web.de
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/trinity-f018660b-95c9-442b-a2a8-c92a56eb07ed-1644345967148@3c-app-webde-bap22
    Link: https://lore.kernel.org/r/20220214100020.8870-2-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 6317f7449348a897483a2b4841f7a9190745c81b
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Feb 14 11:00:19 2022 +0100

    ALSA: hda: Fix regression on forced probe mask option
    
    The forced probe mask via probe_mask 0x100 bit doesn't work any longer
    as expected since the bus init code was moved and it's clearing the
    codec_mask value that was set beforehand.  This patch fixes the
    long-time regression by moving the check_probe_mask() call.
    
    Fixes: a41d122449be ("ALSA: hda - Embed bus into controller object")
    Reported-by: dmummenschanz@web.de
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/trinity-f018660b-95c9-442b-a2a8-c92a56eb07ed-1644345967148@3c-app-webde-bap22
    Link: https://lore.kernel.org/r/20220214100020.8870-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 26ace8793aaefbcd0d6bb664573ded35c69cd6ef
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Thu Feb 10 12:31:07 2022 +0200

    drm/i915/fbc: Fix the plane end Y offset check
    
    We lost the required >>16 when I refactored the FBC plane state
    checks. Bring it back so the check does what it's supposed to.
    
    Cc: Mika Kahola <mika.kahola@intel.com>
    Fixes: 2e6c99f88679 ("drm/i915/fbc: Nuke lots of crap from intel_fbc_state_cache")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220210103107.24492-1-ville.syrjala@linux.intel.com
    Reviewed-by: Mika Kahola <mika.kahola@intel.com>
    (cherry picked from commit f7bc440bc79ae5dcf648b90209910ea8dba6ef0c)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit ea958422291de248b9e2eaaeea36004e84b64043
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Thu Feb 10 12:36:42 2022 +0200

    drm/i915/opregion: check port number bounds for SWSCI display power state
    
    The mapping from enum port to whatever port numbering scheme is used by
    the SWSCI Display Power State Notification is odd, and the memory of it
    has faded. In any case, the parameter only has space for ports numbered
    [0..4], and UBSAN reports bit shift beyond it when the platform has port
    F or more.
    
    Since the SWSCI functionality is supposed to be obsolete for new
    platforms (i.e. ones that might have port F or more), just bail out
    early if the mapped and mangled port number is beyond what the Display
    Power State Notification can support.
    
    Fixes: 9c4b0a683193 ("drm/i915: add opregion function to notify bios of encoder enable/disable")
    Cc: <stable@vger.kernel.org> # v3.13+
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Cc: Lucas De Marchi <lucas.demarchi@intel.com>
    Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4800
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/cc363f42d6b5a5932b6d218fefcc8bdfb15dbbe5.1644489329.git.jani.nikula@intel.com
    (cherry picked from commit 24a644ebbfd3b13cda702f98907f9dd123e34bf9)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 0bdc0a0699929c814a8aecd55d2accb8c11beae2
Author: Matthew Auld <matthew.auld@intel.com>
Date:   Wed Feb 9 11:16:52 2022 +0000

    drm/i915/ttm: tweak priority hint selection
    
    For some reason we are selecting PRIO_HAS_PAGES when we don't have
    mm.pages, and vice versa.
    
    v2(Thomas):
      - Add missing fixes tag
    
    Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220209111652.468762-1-matthew.auld@intel.com
    (cherry picked from commit ba2c5d15022a565da187d90e2fe44768e33e5034)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 8d9d2a723d64b650f2e6423024ccb4a33f0cdc40
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Mon Feb 7 15:27:00 2022 +0200

    drm/i915: Fix mbus join config lookup
    
    The bogus loop from compute_dbuf_slices() was copied into
    check_mbus_joined() as well. So this lookup is wrong as well.
    Fix it.
    
    Cc: stable@vger.kernel.org
    Fixes: f4dc00863226 ("drm/i915/adl_p: MBUS programming")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220207132700.481-2-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula <jani.nikula@intel.com>
    (cherry picked from commit 053f2b85631316a9226f6340c1c0fd95634f7a5b)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 698bef8ff5d2edea5d1c9d6e5adf1bfed1e8a106
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Mon Feb 7 15:26:59 2022 +0200

    drm/i915: Fix dbuf slice config lookup
    
    Apparently I totally fumbled the loop condition when I
    removed the ARRAY_SIZE() stuff from the dbuf slice config
    lookup. Comparing the loop index with the active_pipes bitmask
    is utter nonsense, what we want to do is check to see if the
    mask is zero or not.
    
    Note that the code actually ended up working correctly despite
    the fumble, up until commit eef173954432 ("drm/i915: Allow
    !join_mbus cases for adlp+ dbuf configuration") when things
    broke for real.
    
    Cc: stable@vger.kernel.org
    Fixes: 05e8155afe35 ("drm/i915: Use a sentinel to terminate the dbuf slice arrays")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220207132700.481-1-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula <jani.nikula@intel.com>
    (cherry picked from commit a28fde308c3c1c174249ff9559b57f24e6850086)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit aa4d01a4734bcb1cc9190807cdbcd5af1495910b
Merge: 754e0b0e35608 d72d69abfdb6e
Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Date:   Mon Feb 14 09:50:23 2022 +0000

    Merge tag 'gvt-fixes-2022-01-13' of https://github.com/intel/gvt-linux into drm-intel-fixes
    
    gvt-fixes-2022-01-13
    
    - Make DRM_I915_GVT depend on X86 (Siva Mullati)
    - Clean kernel doc in gtt.c (Randy Dunlap)
    
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    From: Zhi Wang <zhi.wang.linux@gmail.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/1f619581-e3da-3899-09ac-f714d954a580@gmail.com

commit ddbd89deb7d32b1fbb879f48d68fda1a8ac58e8e
Author: Halil Pasic <pasic@linux.ibm.com>
Date:   Fri Feb 11 02:12:52 2022 +0100

    swiotlb: fix info leak with DMA_FROM_DEVICE
    
    The problem I'm addressing was discovered by the LTP test covering
    cve-2018-1000204.
    
    A short description of what happens follows:
    1) The test case issues a command code 00 (TEST UNIT READY) via the SG_IO
       interface with: dxfer_len == 524288, dxdfer_dir == SG_DXFER_FROM_DEV
       and a corresponding dxferp. The peculiar thing about this is that TUR
       is not reading from the device.
    2) In sg_start_req() the invocation of blk_rq_map_user() effectively
       bounces the user-space buffer. As if the device was to transfer into
       it. Since commit a45b599ad808 ("scsi: sg: allocate with __GFP_ZERO in
       sg_build_indirect()") we make sure this first bounce buffer is
       allocated with GFP_ZERO.
    3) For the rest of the story we keep ignoring that we have a TUR, so the
       device won't touch the buffer we prepare as if the we had a
       DMA_FROM_DEVICE type of situation. My setup uses a virtio-scsi device
       and the  buffer allocated by SG is mapped by the function
       virtqueue_add_split() which uses DMA_FROM_DEVICE for the "in" sgs (here
       scatter-gather and not scsi generics). This mapping involves bouncing
       via the swiotlb (we need swiotlb to do virtio in protected guest like
       s390 Secure Execution, or AMD SEV).
    4) When the SCSI TUR is done, we first copy back the content of the second
       (that is swiotlb) bounce buffer (which most likely contains some
       previous IO data), to the first bounce buffer, which contains all
       zeros.  Then we copy back the content of the first bounce buffer to
       the user-space buffer.
    5) The test case detects that the buffer, which it zero-initialized,
      ain't all zeros and fails.
    
    One can argue that this is an swiotlb problem, because without swiotlb
    we leak all zeros, and the swiotlb should be transparent in a sense that
    it does not affect the outcome (if all other participants are well
    behaved).
    
    Copying the content of the original buffer into the swiotlb buffer is
    the only way I can think of to make swiotlb transparent in such
    scenarios. So let's do just that if in doubt, but allow the driver
    to tell us that the whole mapped buffer is going to be overwritten,
    in which case we can preserve the old behavior and avoid the performance
    impact of the extra bounce.
    
    Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit c07f2c7b45413a9e50ba78630fda04ecfa17b4f2
Author: Yu Huang <diwang90@gmail.com>
Date:   Sun Feb 13 00:08:33 2022 +0800

    ALSA: hda/realtek: Add quirk for Legion Y9000X 2019
    
    Legion Y9000X 2019 has the same speaker with Y9000X 2020,
    but with a different quirk address. Add one quirk entry
    to make the speaker work on Y9000X 2019 too.
    
    Signed-off-by: Yu Huang <diwang90@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220212160835.165065-1-diwang90@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 19d20c7a29bf2e46ff1ab8e8c4fcd2da8a4f38e2
Author: Matteo Martelli <matteomartelli3@gmail.com>
Date:   Fri Feb 11 23:49:13 2022 +0100

    ALSA: usb-audio: revert to IMPLICIT_FB_FIXED_DEV for M-Audio FastTrack Ultra
    
    Commit 83b7dcbc51c930fc2079ab6c6fc9d719768321f1 introduced a generic
    implicit feedback parser, which fails to execute for M-Audio FastTrack
    Ultra sound cards. The issue is with the ENDPOINT_SYNCTYPE check in
    add_generic_implicit_fb() where the SYNCTYPE is ADAPTIVE instead of ASYNC.
    The reason is that the sync type of the FastTrack output endpoints are
    set to adaptive in the quirks table since commit
    65f04443c96dbda11b8fff21d6390e082846aa3c.
    
    Fixes: 83b7dcbc51c9 ("ALSA: usb-audio: Add generic implicit fb parsing")
    Signed-off-by: Matteo Martelli <matteomartelli3@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220211224913.20683-2-matteomartelli3@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 538f4f022a4612f969d5324ee227403c9f8b1d72
Author: Christian Brauner <brauner@kernel.org>
Date:   Thu Feb 3 14:14:07 2022 +0100

    fs: add kernel doc for mnt_{hold,unhold}_writers()
    
    When I introduced mnt_{hold,unhold}_writers() in commit fbdc2f6c40f6
    ("fs: split out functions to hold writers") I did not add kernel doc for
    them. Fix this and introduce proper documentation.
    
    Link: https://lore.kernel.org/r/20220203131411.3093040-4-brauner@kernel.org
    Fixes: fbdc2f6c40f6 ("fs: split out functions to hold writers")
    Cc: Seth Forshee <seth.forshee@digitalocean.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: linux-fsdevel@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christian Brauner <brauner@kernel.org>

commit 45d941f67b000b6d79159522a0bbfc37cfd584d6
Author: Sudeep Holla <sudeep.holla@arm.com>
Date:   Fri Feb 11 11:02:04 2022 +0000

    arm64: dts: imx8ulp: Set #thermal-sensor-cells to 1 as required
    
    The SCMI binding clearly states the value of #thermal-sensor-cells must
    be 1. However arch/arm64/boot/dts/freescale/imx8ulp.dtsi sets it 0 which
    results in the following warning with dtbs_check:
    
      |  arch/arm64/boot/dts/freescale/imx8ulp-evk.dt.yaml: scmi:
      |             protocol@15:#thermal-sensor-cells:0:0: 1 was expected
      |     From schema: Documentation/devicetree/bindings/firmware/arm,scmi.yaml
    
    Fix it by setting it to 1 as required.
    
    Cc:Shawn Guo <shawnguo@kernel.org>
    Cc: Sascha Hauer <s.hauer@pengutronix.de>
    Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
    Reviewed-by: Fabio Estevam <festevam@gmail.com>
    Acked-by: Peng Fan <peng.fan@nxp.com>
    Fixes: a38771d7a49b ("arm64: dts: imx8ulp: add scmi firmware node")
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit ef3075d6638d3d5353a97fcc7bb0338fc85675f5
Author: Adam Ford <aford173@gmail.com>
Date:   Tue Jan 25 11:11:25 2022 -0600

    arm64: dts: imx8mm: Fix VPU Hanging
    
    The vpumix power domain has a reset assigned to it, however
    when used, it causes a system hang.  Testing has shown that
    it does not appear to be needed anywhere.
    
    Fixes: d39d4bb15310 ("arm64: dts: imx8mm: add GPC node")
    Signed-off-by: Adam Ford <aford173@gmail.com>
    Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 2874b7911132f6975e668f6849c8ac93bc4e1f35
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sat Feb 12 00:44:11 2022 +0100

    netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency
    
    nf_defrag_ipv6_disable() requires CONFIG_IP6_NF_IPTABLES.
    
    Fixes: 75063c9294fb ("netfilter: xt_socket: fix a typo in socket_mt_destroy()")
    Reported-by: kernel test robot <lkp@intel.com>
    Reviewed-by: Eric Dumazet<edumazet@google.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit b160628e9ebcdc85d0db9d7f423c26b3c7c179d0
Author: Helge Deller <deller@gmx.de>
Date:   Sun Feb 13 22:29:25 2022 +0100

    parisc: Show error if wrong 32/64-bit compiler is being used
    
    It happens quite often that people use the wrong compiler to build the
    kernel:
    
    make ARCH=parisc   -> builds the 32-bit kernel
    make ARCH=parisc64 -> builds the 64-bit kernel
    
    This patch adds a sanity check which errors out with an instruction how
    use the correct ARCH= option.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org # v5.15+

commit 3d6cc9898efdfb062efb74dc18cfc700e082f5d5
Author: Ronnie Sahlberg <lsahlber@redhat.com>
Date:   Fri Feb 11 02:59:15 2022 +1000

    cifs: fix double free race when mount fails in cifs_get_root()
    
    When cifs_get_root() fails during cifs_smb3_do_mount() we call
    deactivate_locked_super() which eventually will call delayed_free() which
    will free the context.
    In this situation we should not proceed to enter the out: section in
    cifs_smb3_do_mount() and free the same resources a second time.
    
    [Thu Feb 10 12:59:06 2022] BUG: KASAN: use-after-free in rcu_cblist_dequeue+0x32/0x60
    [Thu Feb 10 12:59:06 2022] Read of size 8 at addr ffff888364f4d110 by task swapper/1/0
    
    [Thu Feb 10 12:59:06 2022] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           OE     5.17.0-rc3+ #4
    [Thu Feb 10 12:59:06 2022] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.0 12/17/2019
    [Thu Feb 10 12:59:06 2022] Call Trace:
    [Thu Feb 10 12:59:06 2022]  <IRQ>
    [Thu Feb 10 12:59:06 2022]  dump_stack_lvl+0x5d/0x78
    [Thu Feb 10 12:59:06 2022]  print_address_description.constprop.0+0x24/0x150
    [Thu Feb 10 12:59:06 2022]  ? rcu_cblist_dequeue+0x32/0x60
    [Thu Feb 10 12:59:06 2022]  kasan_report.cold+0x7d/0x117
    [Thu Feb 10 12:59:06 2022]  ? rcu_cblist_dequeue+0x32/0x60
    [Thu Feb 10 12:59:06 2022]  __asan_load8+0x86/0xa0
    [Thu Feb 10 12:59:06 2022]  rcu_cblist_dequeue+0x32/0x60
    [Thu Feb 10 12:59:06 2022]  rcu_core+0x547/0xca0
    [Thu Feb 10 12:59:06 2022]  ? call_rcu+0x3c0/0x3c0
    [Thu Feb 10 12:59:06 2022]  ? __this_cpu_preempt_check+0x13/0x20
    [Thu Feb 10 12:59:06 2022]  ? lock_is_held_type+0xea/0x140
    [Thu Feb 10 12:59:06 2022]  rcu_core_si+0xe/0x10
    [Thu Feb 10 12:59:06 2022]  __do_softirq+0x1d4/0x67b
    [Thu Feb 10 12:59:06 2022]  __irq_exit_rcu+0x100/0x150
    [Thu Feb 10 12:59:06 2022]  irq_exit_rcu+0xe/0x30
    [Thu Feb 10 12:59:06 2022]  sysvec_hyperv_stimer0+0x9d/0xc0
    ...
    [Thu Feb 10 12:59:07 2022] Freed by task 58179:
    [Thu Feb 10 12:59:07 2022]  kasan_save_stack+0x26/0x50
    [Thu Feb 10 12:59:07 2022]  kasan_set_track+0x25/0x30
    [Thu Feb 10 12:59:07 2022]  kasan_set_free_info+0x24/0x40
    [Thu Feb 10 12:59:07 2022]  ____kasan_slab_free+0x137/0x170
    [Thu Feb 10 12:59:07 2022]  __kasan_slab_free+0x12/0x20
    [Thu Feb 10 12:59:07 2022]  slab_free_freelist_hook+0xb3/0x1d0
    [Thu Feb 10 12:59:07 2022]  kfree+0xcd/0x520
    [Thu Feb 10 12:59:07 2022]  cifs_smb3_do_mount+0x149/0xbe0 [cifs]
    [Thu Feb 10 12:59:07 2022]  smb3_get_tree+0x1a0/0x2e0 [cifs]
    [Thu Feb 10 12:59:07 2022]  vfs_get_tree+0x52/0x140
    [Thu Feb 10 12:59:07 2022]  path_mount+0x635/0x10c0
    [Thu Feb 10 12:59:07 2022]  __x64_sys_mount+0x1bf/0x210
    [Thu Feb 10 12:59:07 2022]  do_syscall_64+0x5c/0xc0
    [Thu Feb 10 12:59:07 2022]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    [Thu Feb 10 12:59:07 2022] Last potentially related work creation:
    [Thu Feb 10 12:59:07 2022]  kasan_save_stack+0x26/0x50
    [Thu Feb 10 12:59:07 2022]  __kasan_record_aux_stack+0xb6/0xc0
    [Thu Feb 10 12:59:07 2022]  kasan_record_aux_stack_noalloc+0xb/0x10
    [Thu Feb 10 12:59:07 2022]  call_rcu+0x76/0x3c0
    [Thu Feb 10 12:59:07 2022]  cifs_umount+0xce/0xe0 [cifs]
    [Thu Feb 10 12:59:07 2022]  cifs_kill_sb+0xc8/0xe0 [cifs]
    [Thu Feb 10 12:59:07 2022]  deactivate_locked_super+0x5d/0xd0
    [Thu Feb 10 12:59:07 2022]  cifs_smb3_do_mount+0xab9/0xbe0 [cifs]
    [Thu Feb 10 12:59:07 2022]  smb3_get_tree+0x1a0/0x2e0 [cifs]
    [Thu Feb 10 12:59:07 2022]  vfs_get_tree+0x52/0x140
    [Thu Feb 10 12:59:07 2022]  path_mount+0x635/0x10c0
    [Thu Feb 10 12:59:07 2022]  __x64_sys_mount+0x1bf/0x210
    [Thu Feb 10 12:59:07 2022]  do_syscall_64+0x5c/0xc0
    [Thu Feb 10 12:59:07 2022]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Reported-by: Shyam Prasad N <sprasad@microsoft.com>
    Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 26d3dadebbcbddfaf1d9caad42527a28a0ed28d8
Author: Ronnie Sahlberg <lsahlber@redhat.com>
Date:   Sat Feb 12 08:16:20 2022 +1000

    cifs: do not use uninitialized data in the owner/group sid
    
    When idsfromsid is used we create a special SID for owner/group.
    This structure must be initialized or else the first 5 bytes
    of the Authority field of the SID will contain uninitialized data
    and thus not be a valid SID.
    
    Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit dd5a927e411836eaef44eb9b00fece615e82e242
Author: Amir Goldstein <amir73il@gmail.com>
Date:   Mon Jan 3 16:50:25 2022 +0200

    cifs: fix set of group SID via NTSD xattrs
    
    'setcifsacl -g <SID>' silently fails to set the group SID on server.
    
    Actually, the bug existed since commit 438471b67963 ("CIFS: Add support
    for setting owner info, dos attributes, and create time"), but this fix
    will not apply cleanly to kernel versions <= v5.10.
    
    Fixes: 3970acf7ddb9 ("SMB3: Add support for getting and setting SACLs")
    Cc: stable@vger.kernel.org # 5.11+
    Signed-off-by: Amir Goldstein <amir73il@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 9405b5f8b20c2bfa6523a555279a0379640dc136
Author: Steve French <stfrench@microsoft.com>
Date:   Sat Feb 12 01:54:14 2022 -0600

    smb3: fix snapshot mount option
    
    The conversion to the new API broke the snapshot mount option
    due to 32 vs. 64 bit type mismatch
    
    Fixes: 24e0a1eff9e2 ("cifs: switch to new mount api")
    Cc: stable@vger.kernel.org # 5.11+
    Reported-by: <ruckajan10@gmail.com>
    Acked-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 754e0b0e35608ed5206d6a67a791563c631cec07
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 12:13:30 2022 -0800

    Linux 5.17-rc4

commit e89d3a46710908c3973397849e758f6ca42db77d
Merge: c5d714aa6dce2 1b9e740a81f91
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 11:58:11 2022 -0800

    Merge tag 'kbuild-fixes-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
    
    Pull Kbuild fixes from Masahiro Yamada:
    
     - Fix the truncated path issue for HAVE_GCC_PLUGINS test in Kconfig
    
     - Move -Wunsligned-access to W=1 builds to avoid sprinkling warnings
       for the latest Clang
    
     - Fix missing fclose() in Kconfig
    
     - Fix Kconfig to touch dep headers correctly when KCONFIG_AUTOCONFIG is
       overridden.
    
    * tag 'kbuild-fixes-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild:
      kconfig: fix failing to generate auto.conf
      kconfig: fix missing fclose() on error paths
      Makefile.extrawarn: Move -Wunaligned-access to W=1
      kconfig: let 'shell' return enough output for deep path names

commit c5d714aa6dce262482992cccc0ab01383294f7ac
Merge: 42964a18f81c9 1e34064b60552
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 10:06:40 2022 -0800

    Merge tag 'irq-urgent-2022-02-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq fixes from Thomas Gleixner:
     "Interrupt chip driver fixes:
    
       - Don't install an hotplug notifier for GICV3-ITS on systems which do
         not need it to prevent a warning in the notifier about inconsistent
         state
    
       - Add the missing device tree matching for the T-HEAD PLIC variant so
         the related SoC is properly supported"
    
    * tag 'irq-urgent-2022-02-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      irqchip/sifive-plic: Add missing thead,c900-plic match string
      dt-bindings: update riscv plic compatible string
      irqchip/gic-v3-its: Skip HP notifier when no ITS is registered

commit 42964a18f81c9e514dce2d11277b7cc546146723
Merge: 6f3573672324b bfb1a7c91fb77
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 09:43:34 2022 -0800

    Merge tag 'objtool_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull objtool fix from Borislav Petkov:
     "Fix a case where objtool would mistakenly warn about instructions
      being unreachable"
    
    * tag 'objtool_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/bug: Merge annotate_reachable() into _BUG_FLAGS() asm

commit 6f3573672324b6391014680dd6e2cf7298aaea22
Merge: f5e02656b19fa 13765de8148f7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 09:27:26 2022 -0800

    Merge tag 'sched_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull scheduler fix from Borislav Petkov:
     "Fix a NULL-ptr dereference when recalculating a sched entity's weight"
    
    * tag 'sched_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      sched/fair: Fix fault in reweight_entity

commit f5e02656b19fa4e38180a08faadd631858a02877
Merge: 808f0ab22106d 5f4e5ce638e6a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 09:25:26 2022 -0800

    Merge tag 'perf_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull perf fix from Borislav Petkov:
     "Prevent cgroup event list corruption when switching events"
    
    * tag 'perf_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      perf: Fix list corruption in perf_cgroup_switch()

commit 808f0ab22106d2305b33a2b3e4df559a92679615
Merge: e9c25787db080 8795359e35bc3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 09:22:52 2022 -0800

    Merge tag 'x86_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 fix from Borislav Petkov:
     "Prevent softlockups when tearing down large SGX enclaves"
    
    * tag 'x86_urgent_for_v5.17_rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/sgx: Silence softlockup detection when releasing large enclaves

commit e9c25787db080cb28601ce182088ce77659f684b
Merge: b81b1829e7e39 2a05137a0575b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 13 09:16:45 2022 -0800

    Merge tag '5.17-rc4-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs fixes from Steve French:
     "Three small smb3 reconnect fixes and an error log clarification"
    
    * tag '5.17-rc4-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6:
      cifs: mark sessions for reconnection in helper function
      cifs: call helper functions for marking channels for reconnect
      cifs: call cifs_reconnect when a connection is marked
      [smb3] improve error message when mount options conflict with posix

commit 1e34064b60552616b2767d22f2e6f440ced09acb
Merge: dd7f5a11ac5a6 1d4df649cbb4b
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Sun Feb 13 14:16:23 2022 +0100

    Merge tag 'irqchip-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent
    
    Pull irqchip fixes from Marc Zyngier:
    
     - Don't register a hotplug notifier on GICv3 systems that advertise
       LPI support, but have no ITS to make use of it
    
     - Add missing DT matching for the thead,c900-plic variant of the
       SiFive PLIC
    
    Link: https://lore.kernel.org/r/20220211110038.1179155-1-maz@kernel.org

commit 143de8d97d79316590475dc2a84513c63c863ddf
Author: Hangyu Hua <hbh25y@gmail.com>
Date:   Fri Feb 11 12:55:10 2022 +0800

    tipc: fix a bit overflow in tipc_crypto_key_rcv()
    
    msg_data_sz return a 32bit value, but size is 16bit. This may lead to a
    bit overflow.
    
    Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b81b1829e7e39f6cebdf6e4d5484eacbceda8554
Merge: 080eba785fe10 5852ed2a6a39c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 10:29:02 2022 -0800

    Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Two minor fixes in the lpfc driver. One changing the classification of
      trace messages and the other fixing a build issue when NVME_FC is
      disabled"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: lpfc: Reduce log messages seen after firmware download
      scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled

commit 080eba785fe10ba21c40bbdd80f2bd5331a28be6
Merge: dcd72f5466571 c72ea20503610
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 10:16:32 2022 -0800

    Merge tag 'char-misc-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
    
    Pull char/misc driver fixes from Greg KH:
     "Here are a small number of char/misc driver fixes for 5.17-rc4 for
      reported issues. They contain:
    
       - phy driver fixes
    
       - iio driver fix
    
       - eeprom driver fix
    
       - speakup regression fix
    
       - fastrpc fix
    
      All of these have been in linux-next with no reported issues"
    
    * tag 'char-misc-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
      iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL
      speakup-dectlk: Restore pitch setting
      bus: mhi: pci_generic: Add mru_default for Cinterion MV31-W
      bus: mhi: pci_generic: Add mru_default for Foxconn SDX55
      eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
      misc: fastrpc: avoid double fput() on failed usercopy
      phy: dphy: Correct clk_pre parameter
      phy: phy-mtk-tphy: Fix duplicated argument in phy-mtk-tphy
      phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable()
      phy: xilinx: zynqmp: Fix bus width setting for SGMII
      phy: cadence: Sierra: fix error handling bugs in probe()
      phy: ti: Fix missing sentinel for clk_div_table
      phy: broadcom: Kconfig: Fix PHY_BRCM_USB config option
      phy: usb: Leave some clocks running during suspend

commit dcd72f54665717f9d610ea101336d42b7a80704b
Merge: 522e7d03f7d28 426aca16e903b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 10:10:35 2022 -0800

    Merge tag 'staging-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
    
    Pullstaging driver fixes from Greg KH:
     "Here are two staging driver fixes for 5.17-rc4.  These are:
    
       - fbtft error path fix
    
       - vc04_services rcu dereference fix
    
      Both of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'staging-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
      staging: fbtft: Fix error path in fbtft_driver_module_init()
      staging: vc04_services: Fix RCU dereference check

commit 522e7d03f7d286cde06bee51982121f63bb03097
Merge: 85187378990eb 28cb138f559f8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 10:01:55 2022 -0800

    Merge tag 'tty-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
    
    Pull tty/serial fixes from Greg KH:
     "Here are four small tty/serial fixes for 5.17-rc4.  They are:
    
       - 8250_pericom change revert to fix a reported regression
    
       - two speculation fixes for vt_ioctl
    
       - n_tty regression fix for polling
    
      All of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'tty-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
      vt_ioctl: add array_index_nospec to VT_ACTIVATE
      vt_ioctl: fix array_index_nospec in vt_setactivate
      serial: 8250_pericom: Revert "Re-enable higher baud rates"
      n_tty: wake up poll(POLLRDNORM) on receiving data

commit 85187378990eb25012b4a506114ad41a478b00a5
Merge: a4fd49cdb5495 736e8d89044c1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 09:56:18 2022 -0800

    Merge tag 'usb-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
    
    Pull USB fixes from Greg KH:
     "Here are some small USB driver fixes for 5.17-rc4 that resolve some
      reported issues and add new device ids:
    
       - usb-serial new device ids
    
       - ulpi cleanup fixes
    
       - f_fs use-after-free fix
    
       - dwc3 driver fixes
    
       - ax88179_178a usb network driver fix
    
       - usb gadget fixes
    
      There is a revert at the end of this series to resolve a build problem
      that 0-day found yesterday. Most of these have been in linux-next,
      except for the last few, and all have now passed 0-day tests"
    
    * tag 'usb-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
      Revert "usb: dwc2: drd: fix soft connect when gadget is unconfigured"
      usb: dwc2: drd: fix soft connect when gadget is unconfigured
      usb: gadget: rndis: check size of RNDIS_MSG_SET command
      USB: gadget: validate interface OS descriptor requests
      usb: core: Unregister device on component_add() failure
      net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
      usb: dwc3: gadget: Prevent core from processing stale TRBs
      USB: serial: cp210x: add CPI Bulk Coin Recycler id
      USB: serial: cp210x: add NCR Retail IO box id
      USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
      usb: gadget: f_uac2: Define specific wTerminalType
      usb: gadget: udc: renesas_usb3: Fix host to USB_ROLE_NONE transition
      usb: raw-gadget: fix handling of dual-direction-capable endpoints
      usb: usb251xb: add boost-up property support
      usb: ulpi: Call of_node_put correctly
      usb: ulpi: Move of_node_put to ulpi_dev_release
      USB: serial: option: add ZTE MF286D modem
      USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
      usb: f_fs: Fix use-after-free for epfile
      usb: dwc3: xilinx: fix uninitialized return value

commit a4fd49cdb5495f36a35bd27b69b3806e383c719b
Merge: 4a387c98b3abc dd9cb842fa9d9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 09:12:44 2022 -0800

    Merge tag 's390-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
    
    Pull s390 updates from Vasily Gorbik:
     "Maintainers and reviewers changes:
    
        - Add Alexander Gordeev as maintainer for s390.
    
        - Christian Borntraeger will focus on s390 KVM maintainership and
          stays as s390 reviewer.
    
      Fixes:
    
       - Fix clang build of modules loader KUnit test.
    
       - Fix kernel panic in CIO code on FCES path-event when no driver is
         attached to a device or the driver does not provide the path_event
         function"
    
    * tag 's390-5.17-4' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
      s390/cio: verify the driver availability for path_event call
      s390/module: fix building test_modules_helpers.o with clang
      MAINTAINERS: downgrade myself to Reviewer for s390
      MAINTAINERS: add Alexander Gordeev as maintainer for s390

commit 4a387c98b3abc7cf9a2281f01f9b4dd7dbc48f65
Merge: eef8cffcaba8f f66edf684edcb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 09:08:57 2022 -0800

    Merge tag 'for-linus-5.17a-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
    
    Pull xen fixes from Juergen Gross:
    
     - Two small cleanups
    
     - Another fix for addressing the EFI framebuffer above 4GB when running
       as Xen dom0
    
     - A patch to let Xen guests use reserved bits in MSI- and IO-APIC-
       registers for extended APIC-IDs the same way KVM guests are doing it
       already
    
    * tag 'for-linus-5.17a-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
      xen/pci: Make use of the helper macro LIST_HEAD()
      xen/x2apic: Fix inconsistent indenting
      xen/x86: detect support for extended destination ID
      xen/x86: obtain full video frame buffer address for Dom0 also under EFI

commit eef8cffcaba8f1498ec32f55c859b883315232ad
Merge: 9917ff5f31978 eed09ad261822
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 09:04:05 2022 -0800

    Merge tag 'seccomp-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
    
    Pull seccomp fixes from Kees Cook:
     "This fixes a corner case of fatal SIGSYS being ignored since v5.15.
      Along with the signal fix is a change to seccomp so that seeing
      another syscall after a fatal filter result will cause seccomp to kill
      the process harder.
    
      Summary:
    
       - Force HANDLER_EXIT even for SIGNAL_UNKILLABLE
    
       - Make seccomp self-destruct after fatal filter results
    
       - Update seccomp samples for easier behavioral demonstration"
    
    * tag 'seccomp-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
      samples/seccomp: Adjust sample to also provide kill option
      seccomp: Invalidate seccomp mode to catch death failures
      signal: HANDLER_EXIT should clear SIGNAL_UNKILLABLE

commit 9917ff5f319788a195c691fa19cf3e90cee59f40
Merge: 83e3966411106 8913c61001482
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 12 08:57:37 2022 -0800

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "5 patches.
    
      Subsystems affected by this patch series: binfmt, procfs, and mm
      (vmscan, memcg, and kfence)"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      kfence: make test case compatible with run time set sample interval
      mm: memcg: synchronize objcg lists with a dedicated spinlock
      mm: vmscan: remove deadlock due to throttling failing to make progress
      fs/proc: task_mmu.c: don't read mapcount for migration entry
      fs/binfmt_elf: fix PT_LOAD p_align values for loaders

commit 1b9e740a81f91ae338b29ed70455719804957b80
Author: Jing Leng <jleng@ambarella.com>
Date:   Fri Feb 11 17:27:36 2022 +0800

    kconfig: fix failing to generate auto.conf
    
    When the KCONFIG_AUTOCONFIG is specified (e.g. export \
    KCONFIG_AUTOCONFIG=output/config/auto.conf), the directory of
    include/config/ will not be created, so kconfig can't create deps
    files in it and auto.conf can't be generated.
    
    Signed-off-by: Jing Leng <jleng@ambarella.com>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 736e8d89044c1c330967fb938fa766cd9e0d8af0
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Sat Feb 12 10:08:54 2022 +0100

    Revert "usb: dwc2: drd: fix soft connect when gadget is unconfigured"
    
    This reverts commit 269cbcf7b72de6f0016806d4a0cec1d689b55a87.
    
    It causes build errors as reported by the kernel test robot.
    
    Link: https://lore.kernel.org/r/202202112236.AwoOTtHO-lkp@intel.com
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 269cbcf7b72d ("usb: dwc2: drd: fix soft connect when gadget is unconfigured")
    Cc: stable@kernel.org
    Cc: Amelie Delaunay <amelie.delaunay@foss.st.com>
    Cc: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
    Cc: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 8913c61001482378d4ed8cc577b17c1ba3e847e4
Author: Peng Liu <liupeng256@huawei.com>
Date:   Fri Feb 11 16:32:35 2022 -0800

    kfence: make test case compatible with run time set sample interval
    
    The parameter kfence_sample_interval can be set via boot parameter and
    late shell command, which is convenient for automated tests and KFENCE
    parameter optimization.  However, KFENCE test case just uses
    compile-time CONFIG_KFENCE_SAMPLE_INTERVAL, which will make KFENCE test
    case not run as users desired.  Export kfence_sample_interval, so that
    KFENCE test case can use run-time-set sample interval.
    
    Link: https://lkml.kernel.org/r/20220207034432.185532-1-liupeng256@huawei.com
    Signed-off-by: Peng Liu <liupeng256@huawei.com>
    Reviewed-by: Marco Elver <elver@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Sumit Semwal <sumit.semwal@linaro.org>
    Cc: Christian Knig <christian.koenig@amd.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0764db9b49c932b89ee4d9e3236dff4bb07b4a66
Author: Roman Gushchin <roman.gushchin@linux.dev>
Date:   Fri Feb 11 16:32:32 2022 -0800

    mm: memcg: synchronize objcg lists with a dedicated spinlock
    
    Alexander reported a circular lock dependency revealed by the mmap1 ltp
    test:
    
      LOCKDEP_CIRCULAR (suite: ltp, case: mtest06 (mmap1))
              WARNING: possible circular locking dependency detected
              5.17.0-20220113.rc0.git0.f2211f194038.300.fc35.s390x+debug #1 Not tainted
              ------------------------------------------------------
              mmap1/202299 is trying to acquire lock:
              00000001892c0188 (css_set_lock){..-.}-{2:2}, at: obj_cgroup_release+0x4a/0xe0
              but task is already holding lock:
              00000000ca3b3818 (&sighand->siglock){-.-.}-{2:2}, at: force_sig_info_to_task+0x38/0x180
              which lock already depends on the new lock.
              the existing dependency chain (in reverse order) is:
              -> #1 (&sighand->siglock){-.-.}-{2:2}:
                     __lock_acquire+0x604/0xbd8
                     lock_acquire.part.0+0xe2/0x238
                     lock_acquire+0xb0/0x200
                     _raw_spin_lock_irqsave+0x6a/0xd8
                     __lock_task_sighand+0x90/0x190
                     cgroup_freeze_task+0x2e/0x90
                     cgroup_migrate_execute+0x11c/0x608
                     cgroup_update_dfl_csses+0x246/0x270
                     cgroup_subtree_control_write+0x238/0x518
                     kernfs_fop_write_iter+0x13e/0x1e0
                     new_sync_write+0x100/0x190
                     vfs_write+0x22c/0x2d8
                     ksys_write+0x6c/0xf8
                     __do_syscall+0x1da/0x208
                     system_call+0x82/0xb0
              -> #0 (css_set_lock){..-.}-{2:2}:
                     check_prev_add+0xe0/0xed8
                     validate_chain+0x736/0xb20
                     __lock_acquire+0x604/0xbd8
                     lock_acquire.part.0+0xe2/0x238
                     lock_acquire+0xb0/0x200
                     _raw_spin_lock_irqsave+0x6a/0xd8
                     obj_cgroup_release+0x4a/0xe0
                     percpu_ref_put_many.constprop.0+0x150/0x168
                     drain_obj_stock+0x94/0xe8
                     refill_obj_stock+0x94/0x278
                     obj_cgroup_charge+0x164/0x1d8
                     kmem_cache_alloc+0xac/0x528
                     __sigqueue_alloc+0x150/0x308
                     __send_signal+0x260/0x550
                     send_signal+0x7e/0x348
                     force_sig_info_to_task+0x104/0x180
                     force_sig_fault+0x48/0x58
                     __do_pgm_check+0x120/0x1f0
                     pgm_check_handler+0x11e/0x180
              other info that might help us debug this:
               Possible unsafe locking scenario:
                     CPU0                    CPU1
                     ----                    ----
                lock(&sighand->siglock);
                                             lock(css_set_lock);
                                             lock(&sighand->siglock);
                lock(css_set_lock);
               *** DEADLOCK ***
              2 locks held by mmap1/202299:
               #0: 00000000ca3b3818 (&sighand->siglock){-.-.}-{2:2}, at: force_sig_info_to_task+0x38/0x180
               #1: 00000001892ad560 (rcu_read_lock){....}-{1:2}, at: percpu_ref_put_many.constprop.0+0x0/0x168
              stack backtrace:
              CPU: 15 PID: 202299 Comm: mmap1 Not tainted 5.17.0-20220113.rc0.git0.f2211f194038.300.fc35.s390x+debug #1
              Hardware name: IBM 3906 M04 704 (LPAR)
              Call Trace:
                dump_stack_lvl+0x76/0x98
                check_noncircular+0x136/0x158
                check_prev_add+0xe0/0xed8
                validate_chain+0x736/0xb20
                __lock_acquire+0x604/0xbd8
                lock_acquire.part.0+0xe2/0x238
                lock_acquire+0xb0/0x200
                _raw_spin_lock_irqsave+0x6a/0xd8
                obj_cgroup_release+0x4a/0xe0
                percpu_ref_put_many.constprop.0+0x150/0x168
                drain_obj_stock+0x94/0xe8
                refill_obj_stock+0x94/0x278
                obj_cgroup_charge+0x164/0x1d8
                kmem_cache_alloc+0xac/0x528
                __sigqueue_alloc+0x150/0x308
                __send_signal+0x260/0x550
                send_signal+0x7e/0x348
                force_sig_info_to_task+0x104/0x180
                force_sig_fault+0x48/0x58
                __do_pgm_check+0x120/0x1f0
                pgm_check_handler+0x11e/0x180
              INFO: lockdep is turned off.
    
    In this example a slab allocation from __send_signal() caused a
    refilling and draining of a percpu objcg stock, resulted in a releasing
    of another non-related objcg.  Objcg release path requires taking the
    css_set_lock, which is used to synchronize objcg lists.
    
    This can create a circular dependency with the sighandler lock, which is
    taken with the locked css_set_lock by the freezer code (to freeze a
    task).
    
    In general it seems that using css_set_lock to synchronize objcg lists
    makes any slab allocations and deallocation with the locked css_set_lock
    and any intervened locks risky.
    
    To fix the problem and make the code more robust let's stop using
    css_set_lock to synchronize objcg lists and use a new dedicated spinlock
    instead.
    
    Link: https://lkml.kernel.org/r/Yfm1IHmoGdyUR81T@carbon.dhcp.thefacebook.com
    Fixes: bf4f059954dc ("mm: memcg/slab: obj_cgroup API")
    Signed-off-by: Roman Gushchin <guro@fb.com>
    Reported-by: Alexander Egorenkov <egorenar@linux.ibm.com>
    Tested-by: Alexander Egorenkov <egorenar@linux.ibm.com>
    Reviewed-by: Waiman Long <longman@redhat.com>
    Acked-by: Tejun Heo <tj@kernel.org>
    Reviewed-by: Shakeel Butt <shakeelb@google.com>
    Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>
    Tested-by: Jeremy Linton <jeremy.linton@arm.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b485c6f1f9f54b81443efda5f3d8a5036ba2cd91
Author: Mel Gorman <mgorman@suse.de>
Date:   Fri Feb 11 16:32:29 2022 -0800

    mm: vmscan: remove deadlock due to throttling failing to make progress
    
    A soft lockup bug in kcompactd was reported in a private bugzilla with
    the following visible in dmesg;
    
      watchdog: BUG: soft lockup - CPU#33 stuck for 26s! [kcompactd0:479]
      watchdog: BUG: soft lockup - CPU#33 stuck for 52s! [kcompactd0:479]
      watchdog: BUG: soft lockup - CPU#33 stuck for 78s! [kcompactd0:479]
      watchdog: BUG: soft lockup - CPU#33 stuck for 104s! [kcompactd0:479]
    
    The machine had 256G of RAM with no swap and an earlier failed
    allocation indicated that node 0 where kcompactd was run was potentially
    unreclaimable;
    
      Node 0 active_anon:29355112kB inactive_anon:2913528kB active_file:0kB
        inactive_file:0kB unevictable:64kB isolated(anon):0kB isolated(file):0kB
        mapped:8kB dirty:0kB writeback:0kB shmem:26780kB shmem_thp:
        0kB shmem_pmdmapped: 0kB anon_thp: 23480320kB writeback_tmp:0kB
        kernel_stack:2272kB pagetables:24500kB all_unreclaimable? yes
    
    Vlastimil Babka investigated a crash dump and found that a task
    migrating pages was trying to drain PCP lists;
    
      PID: 52922  TASK: ffff969f820e5000  CPU: 19  COMMAND: "kworker/u128:3"
      Call Trace:
         __schedule
         schedule
         schedule_timeout
         wait_for_completion
         __flush_work
         __drain_all_pages
         __alloc_pages_slowpath.constprop.114
         __alloc_pages
         alloc_migration_target
         migrate_pages
         migrate_to_node
         do_migrate_pages
         cpuset_migrate_mm_workfn
         process_one_work
         worker_thread
         kthread
         ret_from_fork
    
    This failure is specific to CONFIG_PREEMPT=n builds.  The root of the
    problem is that kcompact0 is not rescheduling on a CPU while a task that
    has isolated a large number of the pages from the LRU is waiting on
    kcompact0 to reschedule so the pages can be released.  While
    shrink_inactive_list() only loops once around too_many_isolated, reclaim
    can continue without rescheduling if sc->skipped_deactivate == 1 which
    could happen if there was no file LRU and the inactive anon list was not
    low.
    
    Link: https://lkml.kernel.org/r/20220203100326.GD3301@suse.de
    Fixes: d818fca1cac3 ("mm/vmscan: throttle reclaim and compaction when too may pages are isolated")
    Signed-off-by: Mel Gorman <mgorman@suse.de>
    Debugged-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Rik van Riel <riel@surriel.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 24d7275ce2791829953ed4e72f68277ceb2571c6
Author: Yang Shi <shy828301@gmail.com>
Date:   Fri Feb 11 16:32:26 2022 -0800

    fs/proc: task_mmu.c: don't read mapcount for migration entry
    
    The syzbot reported the below BUG:
    
      kernel BUG at include/linux/page-flags.h:785!
      invalid opcode: 0000 [#1] PREEMPT SMP KASAN
      CPU: 1 PID: 4392 Comm: syz-executor560 Not tainted 5.16.0-rc6-syzkaller #0
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
      RIP: 0010:PageDoubleMap include/linux/page-flags.h:785 [inline]
      RIP: 0010:__page_mapcount+0x2d2/0x350 mm/util.c:744
      Call Trace:
        page_mapcount include/linux/mm.h:837 [inline]
        smaps_account+0x470/0xb10 fs/proc/task_mmu.c:466
        smaps_pte_entry fs/proc/task_mmu.c:538 [inline]
        smaps_pte_range+0x611/0x1250 fs/proc/task_mmu.c:601
        walk_pmd_range mm/pagewalk.c:128 [inline]
        walk_pud_range mm/pagewalk.c:205 [inline]
        walk_p4d_range mm/pagewalk.c:240 [inline]
        walk_pgd_range mm/pagewalk.c:277 [inline]
        __walk_page_range+0xe23/0x1ea0 mm/pagewalk.c:379
        walk_page_vma+0x277/0x350 mm/pagewalk.c:530
        smap_gather_stats.part.0+0x148/0x260 fs/proc/task_mmu.c:768
        smap_gather_stats fs/proc/task_mmu.c:741 [inline]
        show_smap+0xc6/0x440 fs/proc/task_mmu.c:822
        seq_read_iter+0xbb0/0x1240 fs/seq_file.c:272
        seq_read+0x3e0/0x5b0 fs/seq_file.c:162
        vfs_read+0x1b5/0x600 fs/read_write.c:479
        ksys_read+0x12d/0x250 fs/read_write.c:619
        do_syscall_x64 arch/x86/entry/common.c:50 [inline]
        do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
        entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    The reproducer was trying to read /proc/$PID/smaps when calling
    MADV_FREE at the mean time.  MADV_FREE may split THPs if it is called
    for partial THP.  It may trigger the below race:
    
               CPU A                         CPU B
               -----                         -----
      smaps walk:                      MADV_FREE:
      page_mapcount()
        PageCompound()
                                       split_huge_page()
        page = compound_head(page)
        PageDoubleMap(page)
    
    When calling PageDoubleMap() this page is not a tail page of THP anymore
    so the BUG is triggered.
    
    This could be fixed by elevated refcount of the page before calling
    mapcount, but that would prevent it from counting migration entries, and
    it seems overkilling because the race just could happen when PMD is
    split so all PTE entries of tail pages are actually migration entries,
    and smaps_account() does treat migration entries as mapcount == 1 as
    Kirill pointed out.
    
    Add a new parameter for smaps_account() to tell this entry is migration
    entry then skip calling page_mapcount().  Don't skip getting mapcount
    for device private entries since they do track references with mapcount.
    
    Pagemap also has the similar issue although it was not reported.  Fixed
    it as well.
    
    [shy828301@gmail.com: v4]
      Link: https://lkml.kernel.org/r/20220203182641.824731-1-shy828301@gmail.com
    [nathan@kernel.org: avoid unused variable warning in pagemap_pmd_range()]
      Link: https://lkml.kernel.org/r/20220207171049.1102239-1-nathan@kernel.org
    Link: https://lkml.kernel.org/r/20220120202805.3369-1-shy828301@gmail.com
    Fixes: e9b61f19858a ("thp: reintroduce split_huge_page()")
    Signed-off-by: Yang Shi <shy828301@gmail.com>
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Reported-by: syzbot+1f52b3a18d5633fa7f82@syzkaller.appspotmail.com
    Acked-by: David Hildenbrand <david@redhat.com>
    Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
    Cc: Jann Horn <jannh@google.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Alexey Dobriyan <adobriyan@gmail.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 925346c129da1171222a9cdb11fa2b734d9955da
Author: Mike Rapoport <rppt@kernel.org>
Date:   Fri Feb 11 16:32:22 2022 -0800

    fs/binfmt_elf: fix PT_LOAD p_align values for loaders
    
    Rui Salvaterra reported that Aisleroit solitaire crashes with "Wrong
    __data_start/_end pair" assertion from libgc after update to v5.17-rc1.
    
    Bisection pointed to commit 9630f0d60fec ("fs/binfmt_elf: use PT_LOAD
    p_align values for static PIE") that fixed handling of static PIEs, but
    made the condition that guards load_bias calculation to exclude loader
    binaries.
    
    Restoring the check for presence of interpreter fixes the problem.
    
    Link: https://lkml.kernel.org/r/20220202121433.3697146-1-rppt@kernel.org
    Fixes: 9630f0d60fec ("fs/binfmt_elf: use PT_LOAD p_align values for static PIE")
    Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
    Reported-by: Rui Salvaterra <rsalvaterra@gmail.com>
    Tested-by: Rui Salvaterra <rsalvaterra@gmail.com>
    Cc: Alexander Viro <viro@zeniv.linux.org.uk>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: "H.J. Lu" <hjl.tools@gmail.com>
    Cc: Kees Cook <keescook@chromium.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3916c3619599a3970d3e6f98fb430b7c46266ada
Author: Corentin Labbe <clabbe@baylibre.com>
Date:   Wed Feb 9 12:03:55 2022 +0000

    ARM: dts: rockchip: fix a typo on rk3288 crypto-controller
    
    crypto-controller had a typo, fix it.
    In the same time, rename it to just crypto
    
    Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
    Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220209120355.1985707-1-clabbe@baylibre.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit be4e65bdffab5f588044325117df77dad7e9c45a
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Thu Feb 10 15:23:53 2022 +0100

    ARM: dts: rockchip: reorder rk322x hmdi clocks
    
    The binding specifies the clock order to "iahb", "isfr", "cec". Reorder
    the clocks accordingly.
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
    Link: https://lore.kernel.org/r/20220210142353.3420859-1-s.hauer@pengutronix.de
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit bf8e59fd315f304eb538546e35de6dc603e4709f
Author: Gatis Peisenieks <gatis@mikrotik.com>
Date:   Fri Feb 11 08:51:23 2022 +0200

    atl1c: fix tx timeout after link flap on Mikrotik 10/25G NIC
    
    If NIC had packets in tx queue at the moment link down event
    happened, it could result in tx timeout when link got back up.
    
    Since device has more than one tx queue we need to reset them
    accordingly.
    
    Fixes: 057f4af2b171 ("atl1c: add 4 RX/TX queue support for Mikrotik 10/25G NIC")
    Signed-off-by: Gatis Peisenieks <gatis@mikrotik.com>
    Link: https://lore.kernel.org/r/20220211065123.4187615-1-gatis@mikrotik.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6c342ce2239c182c2428ce5a44cb32330434ae6e
Author: Jeremy Kerr <jk@codeconstruct.com.au>
Date:   Fri Feb 11 09:15:52 2022 +0800

    mctp: serial: Cancel pending work from ndo_uninit handler
    
    We cannot do the cancel_work_sync from after the unregister_netdev, as
    the dev pointer is no longer valid, causing a uaf on ldisc unregister
    (or device close).
    
    Instead, do the cancel_work_sync from the ndo_uninit op, where the dev
    still exists, but the queue has stopped.
    
    Fixes: 7bd9890f3d74 ("mctp: serial: cancel tx work on ldisc close")
    Reported-by: Luo Likang <luolikang@nsfocus.com>
    Tested-by: Luo Likang <luolikang@nsfocus.com>
    Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
    Link: https://lore.kernel.org/r/20220211011552.1861886-1-jk@codeconstruct.com.au
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 28df029d53a2fd80c1b8674d47895648ad26dcfb
Author: Cheng Jui Wang <cheng-jui.wang@mediatek.com>
Date:   Thu Feb 10 18:50:11 2022 +0800

    lockdep: Correct lock_classes index mapping
    
    A kernel exception was hit when trying to dump /proc/lockdep_chains after
    lockdep report "BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!":
    
    Unable to handle kernel paging request at virtual address 00054005450e05c3
    ...
    00054005450e05c3] address between user and kernel address ranges
    ...
    pc : [0xffffffece769b3a8] string+0x50/0x10c
    lr : [0xffffffece769ac88] vsnprintf+0x468/0x69c
    ...
     Call trace:
      string+0x50/0x10c
      vsnprintf+0x468/0x69c
      seq_printf+0x8c/0xd8
      print_name+0x64/0xf4
      lc_show+0xb8/0x128
      seq_read_iter+0x3cc/0x5fc
      proc_reg_read_iter+0xdc/0x1d4
    
    The cause of the problem is the function lock_chain_get_class() will
    shift lock_classes index by 1, but the index don't need to be shifted
    anymore since commit 01bb6f0af992 ("locking/lockdep: Change the range
    of class_idx in held_lock struct") already change the index to start
    from 0.
    
    The lock_classes[-1] located at chain_hlocks array. When printing
    lock_classes[-1] after the chain_hlocks entries are modified, the
    exception happened.
    
    The output of lockdep_chains are incorrect due to this problem too.
    
    Fixes: f611e8cf98ec ("lockdep: Take read/write status in consideration when generate chainkey")
    Signed-off-by: Cheng Jui Wang <cheng-jui.wang@mediatek.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
    Link: https://lore.kernel.org/r/20220210105011.21712-1-cheng-jui.wang@mediatek.com

commit 6bb9681a43f34f2cab4aad6e2a02da4ce54d13c5
Author: Mans Rullgard <mans@mansr.com>
Date:   Wed Feb 9 14:54:54 2022 +0000

    net: dsa: lan9303: fix reset on probe
    
    The reset input to the LAN9303 chip is active low, and devicetree
    gpio handles reflect this.  Therefore, the gpio should be requested
    with an initial state of high in order for the reset signal to be
    asserted.  Other uses of the gpio already use the correct polarity.
    
    Fixes: a1292595e006 ("net: dsa: add new DSA switch driver for the SMSC-LAN9303")
    Signed-off-by: Mans Rullgard <mans@mansr.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Reviewed-by: Florian Fianelil <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220209145454.19749-1-mans@mansr.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 06582bc86d7f48d35cd044098ca1e246e8c7c52e
Author: Ming Lei <ming.lei@redhat.com>
Date:   Wed Jan 26 11:58:30 2022 +0800

    block: loop:use kstatfs.f_bsize of backing file to set discard granularity
    
    If backing file's filesystem has implemented ->fallocate(), we think the
    loop device can support discard, then pass sb->s_blocksize as
    discard_granularity. However, some underlying FS, such as overlayfs,
    doesn't set sb->s_blocksize, and causes discard_granularity to be set as
    zero, then the warning in __blkdev_issue_discard() is triggered.
    
    Christoph suggested to pass kstatfs.f_bsize as discard granularity, and
    this way is fine because kstatfs.f_bsize means 'Optimal transfer block
    size', which still matches with definition of discard granularity.
    
    So fix the issue by setting discard_granularity as kstatfs.f_bsize if it
    is available, otherwise claims discard isn't supported.
    
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Vivek Goyal <vgoyal@redhat.com>
    Reported-by: Pei Zhang <pezhang@redhat.com>
    Signed-off-by: Ming Lei <ming.lei@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220126035830.296465-1-ming.lei@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit f10f582d28220f50099d3f561116256267821429
Author: Mike Christie <michael.christie@oracle.com>
Date:   Tue Feb 8 12:54:48 2022 -0600

    scsi: qedi: Fix ABBA deadlock in qedi_process_tmf_resp() and qedi_process_cmd_cleanup_resp()
    
    This fixes a deadlock added with commit b40f3894e39e ("scsi: qedi: Complete
    TMF works before disconnect")
    
    Bug description from Jia-Ju Bai:
    
    qedi_process_tmf_resp()
      spin_lock(&session->back_lock); --> Line 201 (Lock A)
      spin_lock(&qedi_conn->tmf_work_lock); --> Line 230 (Lock B)
    
    qedi_process_cmd_cleanup_resp()
      spin_lock_bh(&qedi_conn->tmf_work_lock); --> Line 752 (Lock B)
      spin_lock_bh(&conn->session->back_lock); --> Line 784 (Lock A)
    
    When qedi_process_tmf_resp() and qedi_process_cmd_cleanup_resp() are
    concurrently executed, the deadlock can occur.
    
    This patch fixes the deadlock by not holding the tmf_work_lock in
    qedi_process_cmd_cleanup_resp while holding the back_lock. The
    tmf_work_lock is only needed while we remove the tmf_work from the
    work_list.
    
    Link: https://lore.kernel.org/r/20220208185448.6206-1-michael.christie@oracle.com
    Fixes: b40f3894e39e ("scsi: qedi: Complete TMF works before disconnect")
    Cc: Manish Rangankar <mrangankar@marvell.com>
    Cc: Nilesh Javali <njavali@marvell.com>
    Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
    Reported-by: Jia-Ju Bai <baijiaju1990@gmail.com>
    Signed-off-by: Mike Christie <michael.christie@oracle.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 83e396641110663d3c7bb25b9bc0c6a750359ecf
Merge: adccc16ea3c5f 5e5eddd94c890
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 13:40:03 2022 -0800

    Merge tag 'soc-fixes-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC fixes from Arnd Bergmann:
     "This is a fairly large set of bugfixes, most of which had been sent a
      while ago but only now made it into the soc tree:
    
      Maintainer file updates:
    
       - Claudiu Beznea now co-maintains the at91 soc family, replacing
         Ludovic Desroches.
    
       - Michael Walle maintains the sl28cpld drivers
    
       - Alain Volmat and Raphael Gallais-Pou take over some drivers for ST
         platforms
    
       - Alim Akhtar is an additional reviewer for Samsung platforms
    
      Code fixes:
    
       - Op-tee had a problem with object lifetime that needs a slightly
         complex fix, as well as another bug with error handling.
    
       - Several minor issues for the OMAP platform, including a regression
         with the timer
    
       - A Kconfig change to fix a build-time issue on Intel SoCFPGA
    
      Device tree fixes:
    
       - The Amlogic Meson platform fixes a boot regression on am1-odroid, a
         spurious interrupt, and a problem with reserved memory regions
    
       - In the i.MX platform, several bug fixes are needed to make devices
         work correctly: SD card detection, alarmtimer, and sound card on
         some board. One patch for the GPU got in there by accident and gets
         reverted again.
    
       - TI K3 needs a fix for J721S2 serial port numbers
    
       - ux500 needs a fix to mount the SD card as root on the Skomer phone"
    
    * tag 'soc-fixes-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (46 commits)
      Revert "arm64: dts: imx8mn-venice-gw7902: disable gpu"
      arm64: Remove ARCH_VULCAN
      MAINTAINERS: add myself as a maintainer for the sl28cpld
      MAINTAINERS: add IRC to ARM sub-architectures and Devicetree
      MAINTAINERS: arm: samsung: add Git tree and IRC
      ARM: dts: Fix boot regression on Skomer
      ARM: dts: spear320: Drop unused and undocumented 'irq-over-gpio' property
      soc: aspeed: lpc-ctrl: Block error printing on probe defer cases
      docs/ABI: testing: aspeed-uart-routing: Escape asterisk
      MAINTAINERS: update drm/stm drm/sti and cec/sti maintainers
      MAINTAINERS: Update Benjamin Gaignard maintainer status
      ARM: socfpga: fix missing RESET_CONTROLLER
      arm64: dts: meson-sm1-odroid: fix boot loop after reboot
      arm64: dts: meson-g12: drop BL32 region from SEI510/SEI610
      arm64: dts: meson-g12: add ATF BL32 reserved-memory region
      arm64: dts: meson-gx: add ATF BL32 reserved-memory region
      arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO domain for GPIOE_2
      arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator
      arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133'
      optee: use driver internal tee_context for some rpc
      ...

commit 3df9d803163e1616c2e742be8a7bfc00ac444ea8
Merge: acc3c47394a17 5eaed6eedbe96
Author: Alexei Starovoitov <ast@kernel.org>
Date:   Fri Feb 11 13:21:47 2022 -0800

    Merge branch 'bpf: fix a bpf_timer initialization issue'
    
    Yonghong Song says:
    
    ====================
    
    The patch [1] exposed a bpf_timer initialization bug in function
    check_and_init_map_value(). With bug fix here, the patch [1]
    can be applied with all selftests passed. Please see individual
    patches for fix details.
    
      [1] https://lore.kernel.org/bpf/20220209070324.1093182-2-memxor@gmail.com/
    
    Changelog:
      v3 -> v4:
        . move header file in patch #1 to avoid bpf-next merge conflict
      v2 -> v3:
        . switch patch #1 and patch #2 for better bisecting
      v1 -> v2:
        . add Fixes tag for patch #1
        . rebase against bpf tree
    ====================
    
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 5eaed6eedbe9612f642ad2b880f961d1c6c8ec2b
Author: Yonghong Song <yhs@fb.com>
Date:   Fri Feb 11 11:49:53 2022 -0800

    bpf: Fix a bpf_timer initialization issue
    
    The patch in [1] intends to fix a bpf_timer related issue,
    but the fix caused existing 'timer' selftest to fail with
    hang or some random errors. After some debug, I found
    an issue with check_and_init_map_value() in the hashtab.c.
    More specifically, in hashtab.c, we have code
      l_new = bpf_map_kmalloc_node(&htab->map, ...)
      check_and_init_map_value(&htab->map, l_new...)
    Note that bpf_map_kmalloc_node() does not do initialization
    so l_new contains random value.
    
    The function check_and_init_map_value() intends to zero the
    bpf_spin_lock and bpf_timer if they exist in the map.
    But I found bpf_spin_lock is zero'ed but bpf_timer is not zero'ed.
    With [1], later copy_map_value() skips copying of
    bpf_spin_lock and bpf_timer. The non-zero bpf_timer caused
    random failures for 'timer' selftest.
    Without [1], for both bpf_spin_lock and bpf_timer case,
    bpf_timer will be zero'ed, so 'timer' self test is okay.
    
    For check_and_init_map_value(), why bpf_spin_lock is zero'ed
    properly while bpf_timer not. In bpf uapi header, we have
      struct bpf_spin_lock {
            __u32   val;
      };
      struct bpf_timer {
            __u64 :64;
            __u64 :64;
      } __attribute__((aligned(8)));
    
    The initialization code:
      *(struct bpf_spin_lock *)(dst + map->spin_lock_off) =
          (struct bpf_spin_lock){};
      *(struct bpf_timer *)(dst + map->timer_off) =
          (struct bpf_timer){};
    It appears the compiler has no obligation to initialize anonymous fields.
    For example, let us use clang with bpf target as below:
      $ cat t.c
      struct bpf_timer {
            unsigned long long :64;
      };
      struct bpf_timer2 {
            unsigned long long a;
      };
    
      void test(struct bpf_timer *t) {
        *t = (struct bpf_timer){};
      }
      void test2(struct bpf_timer2 *t) {
        *t = (struct bpf_timer2){};
      }
      $ clang -target bpf -O2 -c -g t.c
      $ llvm-objdump -d t.o
       ...
       0000000000000000 <test>:
           0:       95 00 00 00 00 00 00 00 exit
       0000000000000008 <test2>:
           1:       b7 02 00 00 00 00 00 00 r2 = 0
           2:       7b 21 00 00 00 00 00 00 *(u64 *)(r1 + 0) = r2
           3:       95 00 00 00 00 00 00 00 exit
    
    gcc11.2 does not have the above issue. But from
      INTERNATIONAL STANDARD ©ISO/IEC ISO/IEC 9899:201x
      Programming languages — C
      http://www.open-std.org/Jtc1/sc22/wg14/www/docs/n1547.pdf
      page 157:
      Except where explicitly stated otherwise, for the purposes of
      this subclause unnamed members of objects of structure and union
      type do not participate in initialization. Unnamed members of
      structure objects have indeterminate value even after initialization.
    
    To fix the problem, let use memset for bpf_timer case in
    check_and_init_map_value(). For consistency, memset is also
    used for bpf_spin_lock case.
    
      [1] https://lore.kernel.org/bpf/20220209070324.1093182-2-memxor@gmail.com/
    
    Fixes: 68134668c17f3 ("bpf: Add map side support for bpf timers.")
    Signed-off-by: Yonghong Song <yhs@fb.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220211194953.3142152-1-yhs@fb.com

commit 3bd916ee0ecbbdd902fc24845f2fef332b2a310c
Author: Yonghong Song <yhs@fb.com>
Date:   Fri Feb 11 11:49:48 2022 -0800

    bpf: Emit bpf_timer in vmlinux BTF
    
    Currently the following code in check_and_init_map_value()
      *(struct bpf_timer *)(dst + map->timer_off) =
          (struct bpf_timer){};
    can help generate bpf_timer definition in vmlinuxBTF.
    But the code above may not zero the whole structure
    due to anonymour members and that code will be replaced
    by memset in the subsequent patch and
    bpf_timer definition will disappear from vmlinuxBTF.
    Let us emit the type explicitly so bpf program can continue
    to use it from vmlinux.h.
    
    Signed-off-by: Yonghong Song <yhs@fb.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220211194948.3141529-1-yhs@fb.com

commit a8cd28553f0f7979668473b0b4675e5dd7587a48
Merge: 5e5eddd94c890 26077968f8389
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Feb 11 22:13:16 2022 +0100

    Merge tag 'at91-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux into arm/fixes
    
    AT91 fixes #1 for 5.17:
    
    - MAINTAINERS file update.
    
    * tag 'at91-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux:
      dt-bindings: ARM: at91: update maintainers entry
      MAINTAINERS: replace a Microchip AT91 maintainer
    
    Link: https://lore.kernel.org/r/20220211133515.15314-1-nicolas.ferre@microchip.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit acc3c47394a1790b4023ca316ac46e798338dd1a
Merge: 4a11678f68381 a7e75016a0753
Author: Alexei Starovoitov <ast@kernel.org>
Date:   Fri Feb 11 13:13:04 2022 -0800

    Merge branch 'Fix for crash due to overwrite in copy_map_value'
    
    Kumar Kartikeya says:
    
    ====================
    
    A fix for an oversight in copy_map_value that leads to kernel crash.
    
    Also, a question for BPF developers:
    It seems in arraymap.c, we always do check_and_free_timer_in_array after we do
    copy_map_value in map_update_elem callback, but the same is not done for
    hashtab.c. Is there a specific reason for this difference in behavior, or did I
    miss that it happens for hashtab.c as well?
    
    Changlog:
    ---------
    v1 -> v2:
    v1: https://lore.kernel.org/bpf/20220209051113.870717-1-memxor@gmail.com
    
     * Fix build error for selftests patch due to missing SYS_PREFIX in bpf tree
    ====================
    
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit a7e75016a0753c24d6c995bc02501ae35368e333
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date:   Wed Feb 9 12:33:24 2022 +0530

    selftests/bpf: Add test for bpf_timer overwriting crash
    
    Add a test that validates that timer value is not overwritten when doing
    a copy_map_value call in the kernel. Without the prior fix, this test
    triggers a crash.
    
    Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220209070324.1093182-3-memxor@gmail.com

commit a8abb0c3dc1e28454851a00f8b7333d9695d566c
Author: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Date:   Wed Feb 9 12:33:23 2022 +0530

    bpf: Fix crash due to incorrect copy_map_value
    
    When both bpf_spin_lock and bpf_timer are present in a BPF map value,
    copy_map_value needs to skirt both objects when copying a value into and
    out of the map. However, the current code does not set both s_off and
    t_off in copy_map_value, which leads to a crash when e.g. bpf_spin_lock
    is placed in map value with bpf_timer, as bpf_map_update_elem call will
    be able to overwrite the other timer object.
    
    When the issue is not fixed, an overwriting can produce the following
    splat:
    
    [root@(none) bpf]# ./test_progs -t timer_crash
    [   15.930339] bpf_testmod: loading out-of-tree module taints kernel.
    [   16.037849] ==================================================================
    [   16.038458] BUG: KASAN: user-memory-access in __pv_queued_spin_lock_slowpath+0x32b/0x520
    [   16.038944] Write of size 8 at addr 0000000000043ec0 by task test_progs/325
    [   16.039399]
    [   16.039514] CPU: 0 PID: 325 Comm: test_progs Tainted: G           OE     5.16.0+ #278
    [   16.039983] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ArchLinux 1.15.0-1 04/01/2014
    [   16.040485] Call Trace:
    [   16.040645]  <TASK>
    [   16.040805]  dump_stack_lvl+0x59/0x73
    [   16.041069]  ? __pv_queued_spin_lock_slowpath+0x32b/0x520
    [   16.041427]  kasan_report.cold+0x116/0x11b
    [   16.041673]  ? __pv_queued_spin_lock_slowpath+0x32b/0x520
    [   16.042040]  __pv_queued_spin_lock_slowpath+0x32b/0x520
    [   16.042328]  ? memcpy+0x39/0x60
    [   16.042552]  ? pv_hash+0xd0/0xd0
    [   16.042785]  ? lockdep_hardirqs_off+0x95/0xd0
    [   16.043079]  __bpf_spin_lock_irqsave+0xdf/0xf0
    [   16.043366]  ? bpf_get_current_comm+0x50/0x50
    [   16.043608]  ? jhash+0x11a/0x270
    [   16.043848]  bpf_timer_cancel+0x34/0xe0
    [   16.044119]  bpf_prog_c4ea1c0f7449940d_sys_enter+0x7c/0x81
    [   16.044500]  bpf_trampoline_6442477838_0+0x36/0x1000
    [   16.044836]  __x64_sys_nanosleep+0x5/0x140
    [   16.045119]  do_syscall_64+0x59/0x80
    [   16.045377]  ? lock_is_held_type+0xe4/0x140
    [   16.045670]  ? irqentry_exit_to_user_mode+0xa/0x40
    [   16.046001]  ? mark_held_locks+0x24/0x90
    [   16.046287]  ? asm_exc_page_fault+0x1e/0x30
    [   16.046569]  ? asm_exc_page_fault+0x8/0x30
    [   16.046851]  ? lockdep_hardirqs_on+0x7e/0x100
    [   16.047137]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [   16.047405] RIP: 0033:0x7f9e4831718d
    [   16.047602] Code: b4 0c 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 6c 0c 00 f7 d8 64 89 01 48
    [   16.048764] RSP: 002b:00007fff488086b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000023
    [   16.049275] RAX: ffffffffffffffda RBX: 00007f9e48683740 RCX: 00007f9e4831718d
    [   16.049747] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00007fff488086d0
    [   16.050225] RBP: 00007fff488086f0 R08: 00007fff488085d7 R09: 00007f9e4cb594a0
    [   16.050648] R10: 0000000000000000 R11: 0000000000000206 R12: 00007f9e484cde30
    [   16.051124] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    [   16.051608]  </TASK>
    [   16.051762] ==================================================================
    
    Fixes: 68134668c17f ("bpf: Add map side support for bpf timers.")
    Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220209070324.1093182-2-memxor@gmail.com

commit adccc16ea3c5fb205bdec0133d08e799aa6cc9ea
Merge: 1d41d2e82623b 075b7d363c675
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 12:55:17 2022 -0800

    Merge tag 'pci-v5.17-fixes-4' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci fix from Bjorn Helgaas:
     "Revert a commit that reduced the number of IRQs used but resulted in
      interrupt storms (Bjorn Helgaas)"
    
    * tag 'pci-v5.17-fixes-4' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
      Revert "PCI/portdrv: Do not setup up IRQs if there are no users"

commit f444578d727a0ca4a72b19cd4a1d7da9f1fb99fe
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Mon Jan 10 16:50:07 2022 +0100

    power: supply: bq256xx: Handle OOM correctly
    
    Since we now return a pointer to an allocated object we need
    to account for memory allocation failure in a separate
    error path.
    
    Fixes: 25fd330370ac ("power: supply_core: Pass pointer to battery info")
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

commit 075b7d363c675ef7fa03918881caeca3458e2a96
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Mon Feb 7 16:33:30 2022 -0600

    Revert "PCI/portdrv: Do not setup up IRQs if there are no users"
    
    This reverts commit 0e8ae5a6ff5952253cd7cc0260df838ab4c21009.
    
    0e8ae5a6ff59 ("PCI/portdrv: Do not setup up IRQs if there are no users")
    reduced usage of IRQs when we don't think we need them.  But Joey, Sergiu,
    and David reported choppy GUI rendering, systems that became unresponsive
    every few seconds, incorrect values reported by cpufreq, and high IRQ 16
    CPU usage.
    
    Joey bisected the issues to 0e8ae5a6ff59, so revert it until we figure out
    a better solution.
    
    Link: https://lore.kernel.org/r/20220210222717.GA658201@bhelgaas
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215533
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215546
    Reported-by: Joey Corleone <joey.corleone@mail.ru>
    Reported-by: Sergiu Deitsch <sergiu.deitsch@gmail.com>
    Reported-by: David Spencer <dspencer577@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Cc: stable@vger.kernel.org      # v5.16+
    Cc: Jan Kiszka <jan.kiszka@siemens.com>

commit 1d41d2e82623b40ee27811fe9ea38bafe2e722e9
Merge: e47ca40326268 6df2a016c0c8a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 12:02:09 2022 -0800

    Merge tag 'riscv-for-linus-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V fixes from Palmer Dabbelt:
    
     - A fix to avoid undefined behavior when stack backtracing, which
       manifests in GCC as incorrect stack addresses
    
     - A few fixes for the XIP kernels
    
     - A fix to tracking NUMA state on CPU hotplug
    
     - Support for the recently relesaed binutils-2.38, which changed the
       default ISA version to one without CSRs or fence.i in 'I' extension
    
    * tag 'riscv-for-linus-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
      riscv: fix build with binutils 2.38
      riscv: cpu-hotplug: clear cpu from numa map when teardown
      riscv: extable: fix err reg writing in dedicated uaccess handler
      riscv/mm: Add XIP_FIXUP for riscv_pfn_base
      riscv/mm: Add XIP_FIXUP for phys_ram_base
      riscv: Fix XIP_FIXUP_FLASH_OFFSET
      riscv: eliminate unreliable __builtin_frame_address(1)

commit e47ca403262680db81dbd8bbfd40e7f522c7f147
Merge: 883fd0aba1ae5 da5fb9e1ad3fb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:55:26 2022 -0800

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fixes from Catalin Marinas:
    
     - Enable Cortex-A510 erratum 2051678 by default as we do with other
       errata.
    
     - arm64 IORT: Check the node revision for PMCG resources to cope with
       old firmware based on a broken revision of the spec that had no way
       to describe the second register page (when an implementation is using
       the recommended RELOC_CTRS feature).
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      ACPI/IORT: Check node revision for PMCG resources
      arm64: Enable Cortex-A510 erratum 2051678 by default

commit 883fd0aba1ae52b800081b9aa9ba9edfc88f36b0
Merge: 8ce964b520ad0 27a98fe60b033
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:48:13 2022 -0800

    Merge tag 'acpi-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull ACPI fixes from Rafael Wysocki:
     "These revert two commits that turned out to be problematic and fix two
      issues related to wakeup from suspend-to-idle on x86.
    
      Specifics:
    
       - Revert a recent change that attempted to avoid issues with
         conflicting address ranges during PCI initialization, because it
         turned out to introduce a regression (Hans de Goede).
    
       - Revert a change that limited EC GPE wakeups from suspend-to-idle to
         systems based on Intel hardware, because it turned out that systems
         based on hardware from other vendors depended on that functionality
         too (Mario Limonciello).
    
       - Fix two issues related to the handling of wakeup interrupts and
         wakeup events signaled through the EC GPE during suspend-to-idle on
         x86 (Rafael Wysocki)"
    
    * tag 'acpi-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      x86/PCI: revert "Ignore E820 reservations for bridge windows on newer systems"
      PM: s2idle: ACPI: Fix wakeup interrupts handling
      ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE
      ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

commit 8ce964b520ad0ad626cb1ee93a444aedceed5425
Merge: cf26a2360a6e1 d3add1a9519dc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:36:32 2022 -0800

    Merge tag 'gfs2-v5.16-rc3-fixes2' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2
    
    Pull gfs2 fixes from Andreas Gruenbacher:
    
     - Revert debug commit that causes unexpected data corruption
    
     - Fix muti-block reservation regression
    
    * tag 'gfs2-v5.16-rc3-fixes2' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2:
      gfs2: Fix gfs2_release for non-writers regression
      Revert "gfs2: check context in gfs2_glock_put"

commit cf26a2360a6e1352a9e0bebabbbcad2b92dd8c6c
Merge: 199b7f84c428d bf23747ee0532
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:26:07 2022 -0800

    Merge tag 'block-5.17-2022-02-11' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - NVMe pull request
          - nvme-tcp: fix bogus request completion when failing to send AER
            (Sagi Grimberg)
          - add the missing nvme_complete_req tracepoint for batched
            completion (Bean Huo)
    
     - Revert of the loop async autoclear issue that has continued to plague
       us this release. A few patchsets exists to improve this, but they are
       too invasive to be considered at this point (Tetsuo)
    
    * tag 'block-5.17-2022-02-11' of git://git.kernel.dk/linux-block:
      loop: revert "make autoclear operation asynchronous"
      nvme-tcp: fix bogus request completion when failing to send AER
      nvme: add nvme_complete_req tracepoint for batched completion

commit 199b7f84c428d90e1858dafa583f7b1d587cbeb8
Merge: 0b9df436192aa 0a3f1e0beacf6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:18:42 2022 -0800

    Merge tag 'io_uring-5.17-2022-02-11' of git://git.kernel.dk/linux-block
    
    Pull io_uring fixes from Jens Axboe:
    
     - Fix a false-positive warning from an older gcc (Alviro)
    
     - Allow oom killer invocations from io_uring_setup (Shakeel)
    
    * tag 'io_uring-5.17-2022-02-11' of git://git.kernel.dk/linux-block:
      mm: io_uring: allow oom-killer from io_uring_setup
      io_uring: Clean up a false-positive warning from GCC 9.3.0

commit 0b9df436192aae9f9705bfe42f6e618dd4773792
Merge: 284fce0443329 c162ca0bcbfb3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 11:05:49 2022 -0800

    Merge tag 'gpio-fixes-for-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio fixes from Bartosz Golaszewski:
    
     - use sleeping variants of GPIO accessors where needed
       in gpio-aggregator
    
     - never return kernel's internal error codes to user-space
       in gpiolib core
    
     - use the correct register for reading output values in
       gpio-sifive
    
     - fix line hogging in gpio-sim
    
    * tag 'gpio-fixes-for-v5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:
      gpio: sim: fix hogs with custom chip labels
      gpio: sifive: use the correct register to read output values
      gpiolib: Never return internal error codes to user space
      gpio: aggregator: Fix calling into sleeping GPIO controllers

commit 284fce0443329b641694894bd1757e4cda626c1f
Merge: c3ee3a9e4fa6b c8ea23d5fa59f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 10:42:31 2022 -0800

    Merge tag 'ata-5.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ata fixes from Damien Le Moal:
     "A couple of additional fixes for 5.17-rc4:
    
       - Fix compilation warnings in the sata_fsl driver (powerpc) (me)
    
       - Disable TRIM commands on M88V29 devices as these commands are
         failing despite the device reporting it supports TRIM (Zoltan)"
    
    * tag 'ata-5.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: libata-core: Disable TRIM on M88V29
      ata: sata_fsl: fix sscanf() and sysfs_emit() format strings

commit c3ee3a9e4fa6b1d249b5abff2d4c7dab5a47d522
Merge: 32f6c5d037740 95e875bdb1862
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 10:35:12 2022 -0800

    Merge tag 'drm-fixes-2022-02-11' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Regular fixes pull, mostly i915 and amd fixes, along with a
      maintainers update for fbdev core.
    
      Otherwise just some build fixes and vc4 HDMI fixes.
    
      fbdev:
       - MAINTAINERS: add Daniel as fbdev core module maintainer
       - build warning fix
       - implicit type cast fix
    
      panel:
       - simple: Fix assignments from panel_dpi_probe()
    
      privacy-screen:
       - fix docs warning
    
      i915:
       - non-x86 build fix
       - ttm error propogation fix
       - drrs on hsw/ivb disabled
       - BIOS readout fixes
       - missing stackdepot oops fix
    
      amd:
       - DCN 3.1 display fixes
       - GC 10.3.1 harvest fix
       - Page flip irq fix
       - hwmon label fix
       - DCN 2.0 display fix
    
      rockchip:
       - fix HDMI error cleanup
       - fix RK3399 VOP register fields
    
      vc4:
       - HDMI fixes
       - remove redundant code"
    
    * tag 'drm-fixes-2022-02-11' of git://anongit.freedesktop.org/drm/drm: (25 commits)
      drm/amdgpu/display: change pipe policy for DCN 2.0
      drm/amd/pm: fix hwmon node of power1_label create issue
      drm/amd/display: keep eDP Vdd on when eDP stream is already enabled
      drm/amd/display: fix yellow carp wm clamping
      drm/amd/display: Cap pflip irqs per max otg number
      drm/amdgpu: add utcl2_harvest to gc 10.3.1
      display/amd: decrease message verbosity about watermarks table failure
      drm/rockchip: vop: Correct RK3399 VOP register fields
      drm/rockchip: dw_hdmi: Do not leave clock enabled in error case
      MAINTAINERS: Add entry for fbdev core
      fbcon: Avoid 'cap' set but not used warning
      drm/privacy-screen: Fix sphinx warning
      drm/i915: Workaround broken BIOS DBUF configuration on TGL/RKL
      drm/i915: Populate pipe dbuf slices more accurately during readout
      drm/i915: Allow !join_mbus cases for adlp+ dbuf configuration
      drm/i915: Fix header test for !CONFIG_X86
      drm/i915/ttm: Return some errors instead of trying memcpy move
      drm/i915: Disable DRRS on IVB/HSW port != A
      drm/i915: Fix oops due to missing stack depot
      drm/vc4: crtc: Fix redundant variable assignment
      ...

commit 32f6c5d037740835043f58f5c59b29841dbe39ff
Merge: f1baf68e1383f 3203ce39ac0b2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 11 10:22:48 2022 -0800

    Merge tag 'trace-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing fixes from Steven Rostedt:
    
     - Fixes to the RTLA tooling
    
     - A fix to a tp_printk overriding tp_printk_stop_on_boot on the
       command line
    
    * tag 'trace-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      tracing: Fix tp_printk option related with tp_printk_stop_on_boot
      MAINTAINERS: Add RTLA entry
      rtla: Fix segmentation fault when failing to enable -t
      rtla/trace: Error message fixup
      rtla/utils: Fix session duration parsing
      rtla: Follow kernel version

commit 66fa226c131fb89287f8f7d004a46e39a859fbf6
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Tue Feb 8 06:48:42 2022 -0500

    KVM: SVM: fix race between interrupt delivery and AVIC inhibition
    
    If svm_deliver_avic_intr is called just after the target vcpu's AVIC got
    inhibited, it might read a stale value of vcpu->arch.apicv_active
    which can lead to the target vCPU not noticing the interrupt.
    
    To fix this use load-acquire/store-release so that, if the target vCPU
    is IN_GUEST_MODE, we're guaranteed to see a previous disabling of the
    AVIC.  If AVIC has been disabled in the meanwhile, proceed with the
    KVM_REQ_EVENT-based delivery.
    
    Incomplete IPI vmexit has the same races as svm_deliver_avic_intr, and
    in fact it can be handled in exactly the same way; the only difference
    lies in who has set IRR, whether svm_deliver_interrupt or the processor.
    Therefore, svm_complete_interrupt_delivery can be used to fix incomplete
    IPI vmexits as well.
    
    Co-developed-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 30811174f0dbe17fd58eba5c22c50292c083c75b
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Tue Feb 8 06:57:07 2022 -0500

    KVM: SVM: set IRR in svm_deliver_interrupt
    
    SVM has to set IRR for both the AVIC and the software-LAPIC case,
    so pull it up to the common function that handles both configurations.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 0a5f784273aad41a22963fc8b818ead3c892c97a
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Tue Feb 8 06:45:16 2022 -0500

    KVM: SVM: extract avic_ring_doorbell
    
    The check on the current CPU adds an extra level of indentation to
    svm_deliver_avic_intr and conflates documentation on what happens
    if the vCPU exits (of interest to svm_deliver_avic_intr) and migrates
    (only of interest to avic_ring_doorbell, which calls get/put_cpu()).
    Extract the wrmsr to a separate function and rewrite the
    comment in svm_deliver_avic_intr().
    
    Co-developed-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 0316dbb9a017d3231f86e0188376f067ec26a59c
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Thu Feb 10 22:23:51 2022 +0500

    selftests: kvm: Remove absent target file
    
    There is no vmx_pi_mmio_test file. Remove it to get rid of error while
    creation of selftest archive:
    
    rsync: [sender] link_stat "/kselftest/kvm/x86_64/vmx_pi_mmio_test" failed: No such file or directory (2)
    rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]
    
    Fixes: 6a58150859fd ("selftest: KVM: Add intra host migration tests")
    Reported-by: "kernelci.org bot" <bot@kernelci.org>
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Message-Id: <20220210172352.1317554-1-usama.anjum@collabora.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 02a4a69667a2ad32f3b52ca906f19628fbdd8a01
Author: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Date:   Thu Feb 3 18:47:03 2022 +0200

    i2c: qcom-cci: don't put a device tree node before i2c_add_adapter()
    
    There is a minor chance for a race, if a pointer to an i2c-bus subnode
    is stored and then reused after releasing its reference, and it would
    be sufficient to get one more reference under a loop over children
    subnodes.
    
    Fixes: e517526195de ("i2c: Add Qualcomm CCI I2C driver")
    Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
    Reviewed-by: Robert Foss <robert.foss@linaro.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit a0d48505a1d68e27220369e2dd1e3573a2f362d2
Author: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Date:   Thu Feb 3 18:47:00 2022 +0200

    i2c: qcom-cci: don't delete an unregistered adapter
    
    If i2c_add_adapter() fails to add an I2C adapter found on QCOM CCI
    controller, on error path i2c_del_adapter() is still called.
    
    Fortunately there is a sanity check in the I2C core, so the only
    visible implication is a printed debug level message:
    
        i2c-core: attempting to delete unregistered adapter [Qualcomm-CCI]
    
    Nevertheless it would be reasonable to correct the probe error path.
    
    Fixes: e517526195de ("i2c: Add Qualcomm CCI I2C driver")
    Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
    Reviewed-by: Robert Foss <robert.foss@linaro.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit a7e793a867ae312cecdeb6f06cceff98263e75dd
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Thu Feb 10 22:13:23 2022 +0500

    selftests/exec: Add non-regular to TEST_GEN_PROGS
    
    non-regular file needs to be compiled and then copied to the output
    directory. Remove it from TEST_PROGS and add it to TEST_GEN_PROGS. This
    removes error thrown by rsync when non-regular object isn't found:
    
    rsync: [sender] link_stat "/linux/tools/testing/selftests/exec/non-regular" failed: No such file or directory (2)
    rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]
    
    Fixes: 0f71241a8e32 ("selftests/exec: add file type errno tests")
    Reported-by: "kernelci.org bot" <bot@kernelci.org>
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 59f39bfa6553d598cb22f694d45e89547f420d85
Author: Robin Murphy <robin.murphy@arm.com>
Date:   Wed Oct 13 10:36:54 2021 -0400

    drm/cma-helper: Set VM_DONTEXPAND for mmap
    
    drm_gem_cma_mmap() cannot assume every implementation of dma_mmap_wc()
    will end up calling remap_pfn_range() (which happens to set the relevant
    vma flag, among others), so in order to make sure expectations around
    VM_DONTEXPAND are met, let it explicitly set the flag like most other
    GEM mmap implementations do.
    
    This avoids repeated warnings on a small minority of systems where the
    display is behind an IOMMU, and has a simple driver which does not
    override drm_gem_cma_default_funcs. Arm hdlcd is an in-tree affected
    driver. Out-of-tree, the Apple DCP driver is affected; this fix is
    required for DCP to be mainlined.
    
    [Alyssa: Update commit message.]
    
    Fixes: c40069cb7bd6 ("drm: add mmap() to drm_gem_object_funcs")
    Acked-by: Daniel Vetter <daniel@ffwll.ch>
    Signed-off-by: Robin Murphy <robin.murphy@arm.com>
    Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20211013143654.39031-1-alyssa@rosenzweig.io

commit ed343aa85718f039f5c3121aff099085902c97f0
Merge: fcb732d8f8cf6 5bfa685e62e9b
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Feb 11 12:10:57 2022 -0500

    Merge tag 'kvmarm-fixes-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
    
    KVM/arm64 fixes for 5.17, take #3
    
    - Fix pending state read of a HW interrupt

commit a12821d5e012a42673f6fe521971f193441d8aa4
Author: Pankaj Raghav <p.raghav@samsung.com>
Date:   Fri Feb 11 10:34:25 2022 +0100

    block: Add handling for zone append command in blk_complete_request
    
    Zone append command needs special handling to update the bi_sector
    field in the bio struct with the actual position of the data in the
    device. It is stored in __sector field of the request struct.
    
    Fixes: 5581a5ddfe8d ("block: add completion handler for fast path")
    Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Tested-by: Adam Manzanares <a.manzanares@samsung.com>
    Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
    Link: https://lore.kernel.org/r/20220211093425.43262-2-p.raghav@samsung.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit d3add1a9519dcacd6e644ecac741c56cf18b67f5
Author: Bob Peterson <rpeterso@redhat.com>
Date:   Tue Jan 18 09:30:18 2022 -0500

    gfs2: Fix gfs2_release for non-writers regression
    
    When a file is opened for writing, the vfs code (do_dentry_open)
    calls get_write_access for the inode, thus incrementing the inode's write
    count. That writer normally then creates a multi-block reservation for
    the inode (i_res) that can be re-used by other writers, which speeds up
    writes for applications that stupidly loop on open/write/close.
    When the writes are all done, the multi-block reservation should be
    deleted when the file is closed by the last "writer."
    
    Commit 0ec9b9ea4f83 broke that concept when it moved the call to
    gfs2_rs_delete before the check for FMODE_WRITE.  Non-writers have no
    business removing the multi-block reservations of writers. In fact, if
    someone opens and closes the file for RO while a writer has a
    multi-block reservation, the RO closer will delete the reservation
    midway through the write, and this results in:
    
    kernel BUG at fs/gfs2/rgrp.c:677! (or thereabouts) which is:
    BUG_ON(rs->rs_requested); from function gfs2_rs_deltree.
    
    This patch moves the check back inside the check for FMODE_WRITE.
    
    Fixes: 0ec9b9ea4f83 ("gfs2: Check for active reservation in gfs2_release")
    Cc: stable@vger.kernel.org # v5.12+
    Signed-off-by: Bob Peterson <rpeterso@redhat.com>
    Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

commit 356b8103d4c495d5440e3e687db9026ec2b76043
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date:   Thu Feb 3 14:06:56 2022 +0100

    Revert "gfs2: check context in gfs2_glock_put"
    
    It turns out that the might_sleep() call that commit 660a6126f8c3 adds
    is triggering occasional data corruption in testing.  We're not sure
    about the root cause yet, but since this commit was added as a debugging
    aid only, revert it for now.
    
    This reverts commit 660a6126f8c3208f6df8d552039cda078a8426d1.
    
    Fixes: 660a6126f8c3 ("gfs2: check context in gfs2_glock_put")
    Cc: stable@vger.kernel.org # v5.16+
    Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

commit 27a98fe60b033dfce95361abe368750994b8a78e
Merge: cb1f65c1e1424 3eb616b26408a
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Fri Feb 11 17:32:20 2022 +0100

    Merge branch 'acpi-x86'
    
    Merge a revert of a problematic commit for 5.17-rc4.
    
    * acpi-x86:
      x86/PCI: revert "Ignore E820 reservations for bridge windows on newer systems"

commit c1dd10c681cd661aae7926630b3f3b0f26fc1cd5
Merge: 269cbcf7b72de 6ca0c6283340d
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri Feb 11 16:44:20 2022 +0100

    Merge tag 'usb-serial-5.17-rc4' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into usb-linus
    
    Johan writes:
    
    USB-serial fixes for 5.17-rc4
    
    Here are some new device ids for 5.17-rc4.
    
    All have been in linux-next with no reported issues.
    
    * tag 'usb-serial-5.17-rc4' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial:
      USB: serial: cp210x: add CPI Bulk Coin Recycler id
      USB: serial: cp210x: add NCR Retail IO box id
      USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
      USB: serial: option: add ZTE MF286D modem
      USB: serial: ch341: add support for GW Instek USB2.0-Serial devices

commit 85d24ad38bc4658ce9a16b85b9c8dc0577d66c71
Merge: 525de9a79349b bea2662e7818e
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Feb 11 14:18:39 2022 +0000

    Merge tag 'wireless-2022-02-11' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless
    
    wireless fixes for v5.17
    
    Second set of fixes for v5.17. This is the first pull request with
    both driver and stack patches.
    
    Most important here are a regression fix for brcmfmac USB devices and
    an iwlwifi fix for use after free when the firmware was missing. We
    have new maintainers for ath9k and wcn36xx as well as ath6kl is now
    orphaned. Also smaller fixes to iwlwifi and stack.

commit bf23747ee05320903177809648002601cd140cdd
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date:   Fri Feb 11 16:15:54 2022 +0900

    loop: revert "make autoclear operation asynchronous"
    
    The kernel test robot is reporting that xfstest which does
    
      umount ext2 on xfs
      umount xfs
    
    sequence started failing, for commit 322c4293ecc58110 ("loop: make
    autoclear operation asynchronous") removed a guarantee that fput() of
    backing file is processed before lo_release() from close() returns to
    user mode.
    
    And syzbot is reporting that deferring destroy_workqueue() from
    __loop_clr_fd() to a WQ context did not help [1]. Revert that commit.
    
    Link: https://syzkaller.appspot.com/bug?extid=831661966588c802aae9 [1]
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Acked-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reported-by: syzbot <syzbot+831661966588c802aae9@syzkaller.appspotmail.com>
    Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Link: https://lore.kernel.org/r/20220211071554.3424-1-penguin-kernel@I-love.SAKURA.ne.jp
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 4a11678f683814df82fca9018d964771e02d7e6d
Author: Felix Maurer <fmaurer@redhat.com>
Date:   Wed Feb 9 16:55:26 2022 +0100

    bpf: Do not try bpf_msg_push_data with len 0
    
    If bpf_msg_push_data() is called with len 0 (as it happens during
    selftests/bpf/test_sockmap), we do not need to do anything and can
    return early.
    
    Calling bpf_msg_push_data() with len 0 previously lead to a wrong ENOMEM
    error: we later called get_order(copy + len); if len was 0, copy + len
    was also often 0 and get_order() returned some undefined value (at the
    moment 52). alloc_pages() caught that and failed, but then bpf_msg_push_data()
    returned ENOMEM. This was wrong because we are most probably not out of
    memory and actually do not need any additional memory.
    
    Fixes: 6fff607e2f14b ("bpf: sk_msg program helper bpf_msg_push_data")
    Signed-off-by: Felix Maurer <fmaurer@redhat.com>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: Yonghong Song <yhs@fb.com>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Link: https://lore.kernel.org/bpf/df69012695c7094ccb1943ca02b4920db3537466.1644421921.git.fmaurer@redhat.com

commit 525de9a79349bd83fe5276d7672f91887f9ee721
Merge: dcd54265c8bc1 bbe4c0896d250
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Feb 11 11:55:08 2022 +0000

    Merge ra.kernel.org:/pub/scm/linux/kernel/git/netfilter/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    The following patchset contains Netfilter fixes for net:
    
    1) Add selftest for nft_synproxy, from Florian Westphal.
    
    2) xt_socket destroy path incorrectly disables IPv4 defrag for
       IPv6 traffic (typo), from Eric Dumazet.
    
    3) Fix exit value selftest nft_concat_range.sh, from Hangbin Liu.
    
    4) nft_synproxy disables the IPv4 hooks if the IPv6 hooks fail
       to be registered.
    
    5) disable rp_filter on router in selftest nft_fib.sh, also
       from Hangbin Liu.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dcd54265c8bc14bd023815e36e2d5f9d66ee1fee
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Feb 10 09:13:31 2022 -0800

    drop_monitor: fix data-race in dropmon_net_event / trace_napi_poll_hit
    
    trace_napi_poll_hit() is reading stat->dev while another thread can write
    on it from dropmon_net_event()
    
    Use READ_ONCE()/WRITE_ONCE() here, RCU rules are properly enforced already,
    we only have to take care of load/store tearing.
    
    BUG: KCSAN: data-race in dropmon_net_event / trace_napi_poll_hit
    
    write to 0xffff88816f3ab9c0 of 8 bytes by task 20260 on cpu 1:
     dropmon_net_event+0xb8/0x2b0 net/core/drop_monitor.c:1579
     notifier_call_chain kernel/notifier.c:84 [inline]
     raw_notifier_call_chain+0x53/0xb0 kernel/notifier.c:392
     call_netdevice_notifiers_info net/core/dev.c:1919 [inline]
     call_netdevice_notifiers_extack net/core/dev.c:1931 [inline]
     call_netdevice_notifiers net/core/dev.c:1945 [inline]
     unregister_netdevice_many+0x867/0xfb0 net/core/dev.c:10415
     ip_tunnel_delete_nets+0x24a/0x280 net/ipv4/ip_tunnel.c:1123
     vti_exit_batch_net+0x2a/0x30 net/ipv4/ip_vti.c:515
     ops_exit_list net/core/net_namespace.c:173 [inline]
     cleanup_net+0x4dc/0x8d0 net/core/net_namespace.c:597
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     worker_thread+0x616/0xa70 kernel/workqueue.c:2454
     kthread+0x1bf/0x1e0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30
    
    read to 0xffff88816f3ab9c0 of 8 bytes by interrupt on cpu 0:
     trace_napi_poll_hit+0x89/0x1c0 net/core/drop_monitor.c:292
     trace_napi_poll include/trace/events/napi.h:14 [inline]
     __napi_poll+0x36b/0x3f0 net/core/dev.c:6366
     napi_poll net/core/dev.c:6432 [inline]
     net_rx_action+0x29e/0x650 net/core/dev.c:6519
     __do_softirq+0x158/0x2de kernel/softirq.c:558
     do_softirq+0xb1/0xf0 kernel/softirq.c:459
     __local_bh_enable_ip+0x68/0x70 kernel/softirq.c:383
     __raw_spin_unlock_bh include/linux/spinlock_api_smp.h:167 [inline]
     _raw_spin_unlock_bh+0x33/0x40 kernel/locking/spinlock.c:210
     spin_unlock_bh include/linux/spinlock.h:394 [inline]
     ptr_ring_consume_bh include/linux/ptr_ring.h:367 [inline]
     wg_packet_decrypt_worker+0x73c/0x780 drivers/net/wireguard/receive.c:506
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     worker_thread+0x616/0xa70 kernel/workqueue.c:2454
     kthread+0x1bf/0x1e0 kernel/kthread.c:377
     ret_from_fork+0x1f/0x30
    
    value changed: 0xffff88815883e000 -> 0x0000000000000000
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 26435 Comm: kworker/0:1 Not tainted 5.17.0-rc1-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Workqueue: wg-crypt-wg2 wg_packet_decrypt_worker
    
    Fixes: 4ea7e38696c7 ("dropmon: add ability to detect when hardware dropsrxpackets")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Neil Horman <nhorman@tuxdriver.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c72ea20503610a4a7ba26c769357d31602769c01
Author: Mathias Krause <minipli@grsecurity.net>
Date:   Mon Feb 7 16:01:19 2022 +0100

    iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL
    
    If we fail to copy the just created file descriptor to userland, we
    try to clean up by putting back 'fd' and freeing 'ib'. The code uses
    put_unused_fd() for the former which is wrong, as the file descriptor
    was already published by fd_install() which gets called internally by
    anon_inode_getfd().
    
    This makes the error handling code leaving a half cleaned up file
    descriptor table around and a partially destructed 'file' object,
    allowing userland to play use-after-free tricks on us, by abusing
    the still usable fd and making the code operate on a dangling
    'file->private_data' pointer.
    
    Instead of leaving the kernel in a partially corrupted state, don't
    attempt to explicitly clean up and leave this to the process exit
    path that'll release any still valid fds, including the one created
    by the previous call to anon_inode_getfd(). Simply return -EFAULT to
    indicate the error.
    
    Fixes: f73f7f4da581 ("iio: buffer: add ioctl() to support opening extra buffers for IIO device")
    Cc: stable@kernel.org
    Cc: Jonathan Cameron <jic23@kernel.org>
    Cc: Alexandru Ardelean <ardeleanalex@gmail.com>
    Cc: Lars-Peter Clausen <lars@metafoo.de>
    Cc: Nuno Sa <Nuno.Sa@analog.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Mathias Krause <minipli@grsecurity.net>
    Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 1de9770d121ee9294794cca0e0be8fbfa0134ee8
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Wed Feb 9 22:10:53 2022 +0800

    net/smc: Avoid overwriting the copies of clcsock callback functions
    
    The callback functions of clcsock will be saved and replaced during
    the fallback. But if the fallback happens more than once, then the
    copies of these callback functions will be overwritten incorrectly,
    resulting in a loop call issue:
    
    clcsk->sk_error_report
     |- smc_fback_error_report() <------------------------------|
         |- smc_fback_forward_wakeup()                          | (loop)
             |- clcsock_callback()  (incorrectly overwritten)   |
                 |- smc->clcsk_error_report() ------------------|
    
    So this patch fixes the issue by saving these function pointers only
    once in the fallback and avoiding overwriting.
    
    Reported-by: syzbot+4de3c0e8a263e1e499bc@syzkaller.appspotmail.com
    Fixes: 341adeec9ada ("net/smc: Forward wakeup to smc socket waitqueue after fallback")
    Link: https://lore.kernel.org/r/0000000000006d045e05d78776f6@google.com
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5bfa685e62e9ba93c303a9a8db646c7228b9b570
Author: Marc Zyngier <maz@kernel.org>
Date:   Thu Feb 3 09:24:45 2022 +0000

    KVM: arm64: vgic: Read HW interrupt pending state from the HW
    
    It appears that a read access to GIC[DR]_I[CS]PENDRn doesn't always
    result in the pending interrupts being accurately reported if they are
    mapped to a HW interrupt. This is particularily visible when acking
    the timer interrupt and reading the GICR_ISPENDR1 register immediately
    after, for example (the interrupt appears as not-pending while it really
    is...).
    
    This is because a HW interrupt has its 'active and pending state' kept
    in the *physical* distributor, and not in the virtual one, as mandated
    by the spec (this is what allows the direct deactivation). The virtual
    distributor only caries the pending and active *states* (note the
    plural, as these are two independent and non-overlapping states).
    
    Fix it by reading the HW state back, either from the timer itself or
    from the distributor if necessary.
    
    Reported-by: Ricardo Koller <ricarkol@google.com>
    Tested-by: Ricardo Koller <ricarkol@google.com>
    Reviewed-by: Ricardo Koller <ricarkol@google.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220208123726.3604198-1-maz@kernel.org

commit 1ba603f56568c3b4c2542dfba07afa25f21dcff3
Author: Alyssa Ross <hi@alyssa.is>
Date:   Fri Feb 11 10:27:04 2022 +0000

    firmware: arm_scmi: Remove space in MODULE_ALIAS name
    
    modprobe can't handle spaces in aliases. Get rid of it to fix the issue.
    
    Link: https://lore.kernel.org/r/20220211102704.128354-1-sudeep.holla@arm.com
    Fixes: aa4f886f3893 ("firmware: arm_scmi: add basic driver infrastructure for SCMI")
    Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Alyssa Ross <hi@alyssa.is>
    Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>

commit 269cbcf7b72de6f0016806d4a0cec1d689b55a87
Author: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Date:   Wed Feb 9 17:15:53 2022 +0100

    usb: dwc2: drd: fix soft connect when gadget is unconfigured
    
    When the gadget driver hasn't been (yet) configured, and the cable is
    connected to a HOST, the SFTDISCON gets cleared unconditionally, so the
    HOST tries to enumerate it.
    At the host side, this can result in a stuck USB port or worse. When
    getting lucky, some dmesg can be observed at the host side:
     new high-speed USB device number ...
     device descriptor read/64, error -110
    
    Fix it in drd, by checking the enabled flag before calling
    dwc2_hsotg_core_connect(). It will be called later, once configured,
    by the normal flow:
    - udc_bind_to_driver
     - usb_gadget_connect
       - dwc2_hsotg_pullup
         - dwc2_hsotg_core_connect
    
    Fixes: 17f934024e84 ("usb: dwc2: override PHY input signals with usb role switch support")
    Cc: stable@kernel.org
    Reviewed-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
    Acked-by: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
    Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
    Link: https://lore.kernel.org/r/1644423353-17859-1-git-send-email-fabrice.gasnier@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 38ea1eac7d88072bbffb630e2b3db83ca649b826
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Feb 9 16:37:53 2022 +0100

    usb: gadget: rndis: check size of RNDIS_MSG_SET command
    
    Check the size of the RNDIS_MSG_SET command given to us before
    attempting to respond to an invalid message size.
    
    Reported-by: Szymon Heidrich <szymon.heidrich@gmail.com>
    Cc: stable@kernel.org
    Tested-by: Szymon Heidrich <szymon.heidrich@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 75e5b4849b81e19e9efe1654b30d7f3151c33c2c
Author: Szymon Heidrich <szymon.heidrich@gmail.com>
Date:   Mon Jan 24 12:14:00 2022 +0100

    USB: gadget: validate interface OS descriptor requests
    
    Stall the control endpoint in case provided index exceeds array size of
    MAX_CONFIG_INTERFACES or when the retrieved function pointer is null.
    
    Signed-off-by: Szymon Heidrich <szymon.heidrich@gmail.com>
    Cc: stable@kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit c853685d11c09da35cb49bbf8f0c001abdc0d0a9
Author: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Date:   Wed Feb 9 17:45:00 2022 +0100

    usb: core: Unregister device on component_add() failure
    
    Commit 8c67d06f3fd9 ("usb: Link the ports to the connectors they are
    attached to") creates a link to the USB Type-C connector for every new
    port that is added when possible. If component_add() fails,
    usb_hub_create_port_device() prints a warning but does not unregister
    the device and does not return errors to the callers.
    
    Syzbot reported a "WARNING in component_del()".
    
    Fix this issue in usb_hub_create_port_device by calling device_unregister()
    and returning the errors from component_add().
    
    Fixes: 8c67d06f3fd9 ("usb: Link the ports to the connectors they are attached to")
    Reported-and-tested-by: syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com
    Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
    Link: https://lore.kernel.org/r/20220209164500.8769-1-fmdefrancesco@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581
Author: Jann Horn <jannh@google.com>
Date:   Wed Jan 26 14:14:52 2022 +0100

    net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
    
    ax88179_rx_fixup() contains several out-of-bounds accesses that can be
    triggered by a malicious (or defective) USB device, in particular:
    
     - The metadata array (hdr_off..hdr_off+2*pkt_cnt) can be out of bounds,
       causing OOB reads and (on big-endian systems) OOB endianness flips.
     - A packet can overlap the metadata array, causing a later OOB
       endianness flip to corrupt data used by a cloned SKB that has already
       been handed off into the network stack.
     - A packet SKB can be constructed whose tail is far beyond its end,
       causing out-of-bounds heap data to be considered part of the SKB's
       data.
    
    I have tested that this can be used by a malicious USB device to send a
    bogus ICMPv6 Echo Request and receive an ICMPv6 Echo Reply in response
    that contains random kernel heap data.
    It's probably also possible to get OOB writes from this on a
    little-endian system somehow - maybe by triggering skb_cow() via IP
    options processing -, but I haven't tested that.
    
    Fixes: e2ca90c276e1 ("ax88179_178a: ASIX AX88179_178A USB 3.0/2.0 to gigabit ethernet adapter driver")
    Cc: stable@kernel.org
    Signed-off-by: Jann Horn <jannh@google.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit ddc204b517e60ae64db34f9832dc41dafa77c751
Author: Waiman Long <longman@redhat.com>
Date:   Tue Feb 8 11:39:12 2022 -0500

    copy_process(): Move fd_install() out of sighand->siglock critical section
    
    I was made aware of the following lockdep splat:
    
    [ 2516.308763] =====================================================
    [ 2516.309085] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
    [ 2516.309433] 5.14.0-51.el9.aarch64+debug #1 Not tainted
    [ 2516.309703] -----------------------------------------------------
    [ 2516.310149] stress-ng/153663 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
    [ 2516.310512] ffff0000e422b198 (&newf->file_lock){+.+.}-{2:2}, at: fd_install+0x368/0x4f0
    [ 2516.310944]
                   and this task is already holding:
    [ 2516.311248] ffff0000c08140d8 (&sighand->siglock){-.-.}-{2:2}, at: copy_process+0x1e2c/0x3e80
    [ 2516.311804] which would create a new lock dependency:
    [ 2516.312066]  (&sighand->siglock){-.-.}-{2:2} -> (&newf->file_lock){+.+.}-{2:2}
    [ 2516.312446]
                   but this new dependency connects a HARDIRQ-irq-safe lock:
    [ 2516.312983]  (&sighand->siglock){-.-.}-{2:2}
       :
    [ 2516.330700]  Possible interrupt unsafe locking scenario:
    
    [ 2516.331075]        CPU0                    CPU1
    [ 2516.331328]        ----                    ----
    [ 2516.331580]   lock(&newf->file_lock);
    [ 2516.331790]                                local_irq_disable();
    [ 2516.332231]                                lock(&sighand->siglock);
    [ 2516.332579]                                lock(&newf->file_lock);
    [ 2516.332922]   <Interrupt>
    [ 2516.333069]     lock(&sighand->siglock);
    [ 2516.333291]
                    *** DEADLOCK ***
    [ 2516.389845]
                   stack backtrace:
    [ 2516.390101] CPU: 3 PID: 153663 Comm: stress-ng Kdump: loaded Not tainted 5.14.0-51.el9.aarch64+debug #1
    [ 2516.390756] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
    [ 2516.391155] Call trace:
    [ 2516.391302]  dump_backtrace+0x0/0x3e0
    [ 2516.391518]  show_stack+0x24/0x30
    [ 2516.391717]  dump_stack_lvl+0x9c/0xd8
    [ 2516.391938]  dump_stack+0x1c/0x38
    [ 2516.392247]  print_bad_irq_dependency+0x620/0x710
    [ 2516.392525]  check_irq_usage+0x4fc/0x86c
    [ 2516.392756]  check_prev_add+0x180/0x1d90
    [ 2516.392988]  validate_chain+0x8e0/0xee0
    [ 2516.393215]  __lock_acquire+0x97c/0x1e40
    [ 2516.393449]  lock_acquire.part.0+0x240/0x570
    [ 2516.393814]  lock_acquire+0x90/0xb4
    [ 2516.394021]  _raw_spin_lock+0xe8/0x154
    [ 2516.394244]  fd_install+0x368/0x4f0
    [ 2516.394451]  copy_process+0x1f5c/0x3e80
    [ 2516.394678]  kernel_clone+0x134/0x660
    [ 2516.394895]  __do_sys_clone3+0x130/0x1f4
    [ 2516.395128]  __arm64_sys_clone3+0x5c/0x7c
    [ 2516.395478]  invoke_syscall.constprop.0+0x78/0x1f0
    [ 2516.395762]  el0_svc_common.constprop.0+0x22c/0x2c4
    [ 2516.396050]  do_el0_svc+0xb0/0x10c
    [ 2516.396252]  el0_svc+0x24/0x34
    [ 2516.396436]  el0t_64_sync_handler+0xa4/0x12c
    [ 2516.396688]  el0t_64_sync+0x198/0x19c
    [ 2517.491197] NET: Registered PF_ATMPVC protocol family
    [ 2517.491524] NET: Registered PF_ATMSVC protocol family
    [ 2591.991877] sched: RT throttling activated
    
    One way to solve this problem is to move the fd_install() call out of
    the sighand->siglock critical section.
    
    Before commit 6fd2fe494b17 ("copy_process(): don't use ksys_close()
    on cleanups"), the pidfd installation was done without holding both
    the task_list lock and the sighand->siglock. Obviously, holding these
    two locks are not really needed to protect the fd_install() call.
    So move the fd_install() call down to after the releases of both locks.
    
    Link: https://lore.kernel.org/r/20220208163912.1084752-1-longman@redhat.com
    Fixes: 6fd2fe494b17 ("copy_process(): don't use ksys_close() on cleanups")
    Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Signed-off-by: Waiman Long <longman@redhat.com>
    Signed-off-by: Christian Brauner <brauner@kernel.org>

commit 97acd701185b13825f8ec7882345040415d46762
Author: Christian Brauner <brauner@kernel.org>
Date:   Thu Feb 3 14:14:06 2022 +0100

    MAINTAINERS: add entry for idmapped mounts
    
    I'd like to continue maintaining the work that was done around idmapped,
    make sure that I'm Cced on new patches and work that impacts the
    infrastructure.
    
    Link: https://lore.kernel.org/r/20220203131411.3093040-3-brauner@kernel.org
    Cc: Seth Forshee <seth.forshee@digitalocean.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: linux-fsdevel@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christian Brauner <brauner@kernel.org>

commit d1c56bfdaca465bd1d0e913053a9c5cafe8b6a6c
Author: Christian Brauner <brauner@kernel.org>
Date:   Thu Feb 3 14:14:05 2022 +0100

    tests: fix idmapped mount_setattr test
    
    The test treated zero as a successful run when it really should treat
    non-zero as a successful run. A mount's idmapping can't change once it
    has been attached to the filesystem.
    
    Link: https://lore.kernel.org/r/20220203131411.3093040-2-brauner@kernel.org
    Fixes: 01eadc8dd96d ("tests: add mount_setattr() selftests")
    Cc: Seth Forshee <seth.forshee@digitalocean.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: linux-fsdevel@vger.kernel.org
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christian Brauner <brauner@kernel.org>

commit eed09ad261822a7bdc441ed192c6f444375e5527
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Feb 7 20:53:34 2022 -0800

    samples/seccomp: Adjust sample to also provide kill option
    
    As a quick way to test SECCOMP_RET_KILL, have a negative errno mean to
    kill the process.
    
    While we're in here, also swap the arch and syscall arguments so they're
    ordered more like how seccomp filters order them.
    
    Signed-off-by: Kees Cook <keescook@chromium.org>

commit 495ac3069a6235bfdf516812a2a9b256671bbdf9
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Feb 7 20:21:13 2022 -0800

    seccomp: Invalidate seccomp mode to catch death failures
    
    If seccomp tries to kill a process, it should never see that process
    again. To enforce this proactively, switch the mode to something
    impossible. If encountered: WARN, reject all syscalls, and attempt to
    kill the process again even harder.
    
    Cc: Andy Lutomirski <luto@amacapital.net>
    Cc: Will Drewry <wad@chromium.org>
    Fixes: 8112c4f140fa ("seccomp: remove 2-phase API")
    Cc: stable@vger.kernel.org
    Signed-off-by: Kees Cook <keescook@chromium.org>

commit 5c72263ef2fbe99596848f03758ae2dc593adf2c
Author: Kees Cook <keescook@chromium.org>
Date:   Tue Feb 8 00:57:17 2022 -0800

    signal: HANDLER_EXIT should clear SIGNAL_UNKILLABLE
    
    Fatal SIGSYS signals (i.e. seccomp RET_KILL_* syscall filter actions)
    were not being delivered to ptraced pid namespace init processes. Make
    sure the SIGNAL_UNKILLABLE doesn't get set for these cases.
    
    Reported-by: Robert Święcki <robert@swiecki.net>
    Suggested-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Fixes: 00b06da29cf9 ("signal: Add SA_IMMUTABLE to ensure forced siganls do not get changed")
    Cc: stable@vger.kernel.org
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Link: https://lore.kernel.org/lkml/878rui8u4a.fsf@email.froward.int.ebiederm.org

commit 95e875bdb1862db178bf24fb703387ec3aa3a34a
Merge: 7830643835535 6e7545ddb1341
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 11 12:44:01 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-02-09' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-02-09:
    
    amdgpu:
    - DCN 3.1 display fixes
    - GC 10.3.1 harvest fix
    - Page flip irq fix
    - hwmon label fix
    - DCN 2.0 display fix
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220210041137.5926-1-alexander.deucher@amd.com

commit 78306438355353e677a5ffcf5e9351604b694159
Merge: df2bb4dc285e6 4e6f55120c7ec
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 11 12:32:45 2022 +1000

    Merge tag 'drm-intel-fixes-2022-02-10' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    - Build fix for non-x86 platforms after remap_io_mmapping changes. (Lucas De Marchi)
    - Correctly propagate errors during object migration blits. (Thomas Hellström)
    - Disable DRRS support on HSW/IVB where it is not implemented yet. (Ville Syrjälä)
    - Correct pipe dbuf BIOS configuration during readout. (Ville Syrjälä)
    - Properly sanitise BIOS buf configuration on ADL-P+ for !join_mbus cases. (Ville Syrjälä)
    - Fix oops due to missing stack depot. (Ville Syrjälä)
    - Workaround broken BIOS DBUF configuration on TGL/RKL. (Ville Syrjälä)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/YgTuYAtpaV3XAGmx@tursulin-mobl2

commit df2bb4dc285e60665930889e6f8c5bb38b90249a
Merge: dfd42facf1e4a 9da1e9ab82c92
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 11 12:05:04 2022 +1000

    Merge tag 'drm-misc-fixes-2022-02-10' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/panel: simple: Fix assignments from panel_dpi_probe()
     * drm/privacy-screen: Cleanups
     * drm/rockchip: Fix HDMI error cleanup; Fix RK3399 VOP register fields
     * drm/vc4: HDMI fixes; Cleanups
     * fbdev: Add fbdev core module with Daniel as maintainer; Cleanups
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YgTf1Zsflzq3JSFo@linux-uq9g

commit e9f7b9228a94778edb7a63fde3c0a3c5bb793064
Author: Sean Anderson <seanga2@gmail.com>
Date:   Wed Feb 9 13:28:22 2022 -0500

    pinctrl: k210: Fix bias-pull-up
    
    Using bias-pull-up would actually cause the pin to have its pull-down
    enabled. Fix this.
    
    Signed-off-by: Sean Anderson <seanga2@gmail.com>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Fixes: d4c34d09ab03 ("pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver")
    Link: https://lore.kernel.org/r/20220209182822.640905-1-seanga2@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit ba2ab85951c91a140a8fa51d8347d54e59ec009d
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Wed Feb 9 21:08:06 2022 +0300

    pinctrl: fix loop in k210_pinconf_get_drive()
    
    The loop exited too early so the k210_pinconf_drive_strength[0] array
    element was never used.
    
    Fixes: d4c34d09ab03 ("pinctrl: Add RISC-V Canaan Kendryte K210 FPIOA driver")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Sean Anderson <seanga2@gmail.com>
    Link: https://lore.kernel.org/r/20220209180804.GA18385@kili
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit f1baf68e1383f6ed93eb9cff2866d46562607a43
Merge: 16f7432c884bb 51a04ebf21122
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 10 16:01:22 2022 -0800

    Merge tag 'net-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from netfilter and can.
    
    Current release - new code bugs:
    
       - sparx5: fix get_stat64 out-of-bound access and crash
    
       - smc: fix netdev ref tracker misuse
    
      Previous releases - regressions:
    
       - eth: ixgbevf: require large buffers for build_skb on 82599VF, avoid
         overflows
    
       - eth: ocelot: fix all IP traffic getting trapped to CPU with PTP
         over IP
    
       - bonding: fix rare link activation misses in 802.3ad mode
    
      Previous releases - always broken:
    
       - tcp: fix tcp sock mem accounting in zero-copy corner cases
    
       - remove the cached dst when uncloning an skb dst and its metadata,
         since we only have one ref it'd lead to an UaF
    
       - netfilter:
          - conntrack: don't refresh sctp entries in closed state
          - conntrack: re-init state for retransmitted syn-ack, avoid
            connection establishment getting stuck with strange stacks
          - ctnetlink: disable helper autoassign, avoid it getting lost
          - nft_payload: don't allow transport header access for fragments
    
       - dsa: fix use of devres for mdio throughout drivers
    
       - eth: amd-xgbe: disable interrupts during pci removal
    
       - eth: dpaa2-eth: unregister netdev before disconnecting the PHY
    
       - eth: ice: fix IPIP and SIT TSO offload"
    
    * tag 'net-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (53 commits)
      net: dsa: mv88e6xxx: fix use-after-free in mv88e6xxx_mdios_unregister
      net: mscc: ocelot: fix mutex lock error during ethtool stats read
      ice: Avoid RTNL lock when re-creating auxiliary device
      ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler
      ice: fix IPIP and SIT TSO offload
      ice: fix an error code in ice_cfg_phy_fec()
      net: mpls: Fix GCC 12 warning
      dpaa2-eth: unregister the netdev before disconnecting from the PHY
      skbuff: cleanup double word in comment
      net: macb: Align the dma and coherent dma masks
      mptcp: netlink: process IPv6 addrs in creating listening sockets
      selftests: mptcp: add missing join check
      net: usb: qmi_wwan: Add support for Dell DW5829e
      vlan: move dev_put into vlan_dev_uninit
      vlan: introduce vlan_dev_free_egress_priority
      ax25: fix UAF bugs of net_device caused by rebinding operation
      net: dsa: fix panic when DSA master device unbinds on shutdown
      net: amd-xgbe: disable interrupts during pci removal
      tipc: rate limit warning for received illegal binding update
      net: mdio: aspeed: Add missing MODULE_DEVICE_TABLE
      ...

commit 8795359e35bc33bf86b6d0765aa7f37431db3b9c
Author: Reinette Chatre <reinette.chatre@intel.com>
Date:   Tue Feb 8 10:48:07 2022 -0800

    x86/sgx: Silence softlockup detection when releasing large enclaves
    
    Vijay reported that the "unclobbered_vdso_oversubscribed" selftest
    triggers the softlockup detector.
    
    Actual SGX systems have 128GB of enclave memory or more.  The
    "unclobbered_vdso_oversubscribed" selftest creates one enclave which
    consumes all of the enclave memory on the system. Tearing down such a
    large enclave takes around a minute, most of it in the loop where
    the EREMOVE instruction is applied to each individual 4k enclave page.
    
    Spending one minute in a loop triggers the softlockup detector.
    
    Add a cond_resched() to give other tasks a chance to run and placate
    the softlockup detector.
    
    Cc: stable@vger.kernel.org
    Fixes: 1728ab54b4be ("x86/sgx: Add a page reclaimer")
    Reported-by: Vijay Dhanraj <vijay.dhanraj@intel.com>
    Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
    Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
    Tested-by: Jarkko Sakkinen <jarkko@kernel.org>  (kselftest as sanity check)
    Link: https://lkml.kernel.org/r/ced01cac1e75f900251b0a4ae1150aa8ebd295ec.1644345232.git.reinette.chatre@intel.com

commit 16f7432c884bb7882f0534cb8b9c38cdbccc37bc
Merge: ff00854812b21 183f80fd72db4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 10 15:42:48 2022 -0800

    Merge tag 'linux-kselftest-fixes-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull Kselftest fixes from Shuah Khan:
     "Build and run-time fixes to pidfd, clone3, and ir tests"
    
    * tag 'linux-kselftest-fixes-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      selftests/ir: fix build with ancient kernel headers
      selftests: fixup build warnings in pidfd / clone3 tests
      pidfd: fix test failure due to stack overflow on some arches

commit ff00854812b216e06e92191f036eb0bd1596b2d4
Merge: e3c85076d7a6f 92a68053c3468
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 10 15:39:59 2022 -0800

    Merge tag 'linux-kselftest-kunit-fixes-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull KUnit fixes from Shuah Khan:
     "Fixes to the test and usage documentation"
    
    * tag 'linux-kselftest-kunit-fixes-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      Documentation: KUnit: Fix usage bug
      kunit: fix missing f in f-string in run_checks.py

commit bbe4c0896d25009a7c86285d2ab024eed4374eea
Author: Hangbin Liu <liuhangbin@gmail.com>
Date:   Thu Feb 10 17:50:56 2022 +0800

    selftests: netfilter: disable rp_filter on router
    
    Some distros may enable rp_filter by default. After ns1 change addr to
    10.0.2.99 and set default router to 10.0.2.1, while the connected router
    address is still 10.0.1.1. The router will not reply the arp request
    from ns1. Fix it by setting the router's veth0 rp_filter to 0.
    
    Before the fix:
      # ./nft_fib.sh
      PASS: fib expression did not cause unwanted packet drops
      Netns nsrouter-HQkDORO2 fib counter doesn't match expected packet count of 1 for 1.1.1.1
      table inet filter {
              chain prerouting {
                      type filter hook prerouting priority filter; policy accept;
                      ip daddr 1.1.1.1 fib saddr . iif oif missing counter packets 0 bytes 0 drop
                      ip6 daddr 1c3::c01d fib saddr . iif oif missing counter packets 0 bytes 0 drop
              }
      }
    
    After the fix:
      # ./nft_fib.sh
      PASS: fib expression did not cause unwanted packet drops
      PASS: fib expression did drop packets for 1.1.1.1
      PASS: fib expression did drop packets for 1c3::c01d
    
    Fixes: 82944421243e ("selftests: netfilter: add fib test case")
    Signed-off-by: Yi Chen <yiche@redhat.com>
    Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 51a04ebf21122d5c76a716ecd9bfc33ea44b2b39
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Feb 10 19:40:17 2022 +0200

    net: dsa: mv88e6xxx: fix use-after-free in mv88e6xxx_mdios_unregister
    
    Since struct mv88e6xxx_mdio_bus *mdio_bus is the bus->priv of something
    allocated with mdiobus_alloc_size(), this means that mdiobus_free(bus)
    will free the memory backing the mdio_bus as well. Therefore, the
    mdio_bus->list element is freed memory, but we continue to iterate
    through the list of MDIO buses using that list element.
    
    To fix this, use the proper list iterator that handles element deletion
    by keeping a copy of the list element next pointer.
    
    Fixes: f53a2ce893b2 ("net: dsa: mv88e6xxx: don't use devres for mdiobus")
    Reported-by: Rafael Richter <rafael.richter@gin.de>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220210174017.3271099-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a19f7d7da9b3ffe8fcc43203a2d49c096d0754f6
Merge: 7fbf6795d127a 5dbbbd01cbba8
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 10 11:45:35 2022 -0800

    Merge branch '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-02-10
    
    Dan Carpenter propagates an error in FEC configuration.
    
    Jesse fixes TSO offloads of IPIP and SIT frames.
    
    Dave adds a dedicated LAG unregister function to resolve a KASAN error
    and moves auxiliary device re-creation after LAG removal to the service
    task to avoid issues with RTNL lock.
    
    * '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue:
      ice: Avoid RTNL lock when re-creating auxiliary device
      ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler
      ice: fix IPIP and SIT TSO offload
      ice: fix an error code in ice_cfg_phy_fec()
    ====================
    
    Link: https://lore.kernel.org/r/20220210170515.2609656-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7fbf6795d127a3b1bb39b0e42579904cf6db1624
Author: Colin Foster <colin.foster@in-advantage.com>
Date:   Thu Feb 10 07:04:51 2022 -0800

    net: mscc: ocelot: fix mutex lock error during ethtool stats read
    
    An ongoing workqueue populates the stats buffer. At the same time, a user
    might query the statistics. While writing to the buffer is mutex-locked,
    reading from the buffer wasn't. This could lead to buggy reads by ethtool.
    
    This patch fixes the former blamed commit, but the bug was introduced in
    the latter.
    
    Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
    Fixes: 1e1caa9735f90 ("ocelot: Clean up stats update deferred work")
    Fixes: a556c76adc052 ("net: mscc: Add initial Ocelot switch support")
    Reported-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/all/20220210150451.416845-2-colin.foster@in-advantage.com/
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit fcb732d8f8cf6084f8480015ad41d25fb023a4dd
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Mon Oct 25 14:29:01 2021 +0100

    KVM: x86/xen: Fix runstate updates to be atomic when preempting vCPU
    
    There are circumstances whem kvm_xen_update_runstate_guest() should not
    sleep because it ends up being called from __schedule() when the vCPU
    is preempted:
    
    [  222.830825]  kvm_xen_update_runstate_guest+0x24/0x100
    [  222.830878]  kvm_arch_vcpu_put+0x14c/0x200
    [  222.830920]  kvm_sched_out+0x30/0x40
    [  222.830960]  __schedule+0x55c/0x9f0
    
    To handle this, make it use the same trick as __kvm_xen_has_interrupt(),
    of using the hva from the gfn_to_hva_cache directly. Then it can use
    pagefault_disable() around the accesses and just bail out if the page
    is absent (which is unlikely).
    
    I almost switched to using a gfn_to_pfn_cache here and bailing out if
    kvm_map_gfn() fails, like kvm_steal_time_set_preempted() does — but on
    closer inspection it looks like kvm_map_gfn() will *always* fail in
    atomic context for a page in IOMEM, which means it will silently fail
    to make the update every single time for such guests, AFAICT. So I
    didn't do it that way after all. And will probably fix that one too.
    
    Cc: stable@vger.kernel.org
    Fixes: 30b5c851af79 ("KVM: x86/xen: Add support for vCPU runstate information")
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <b17a93e5ff4561e57b1238e3e7ccd0b613eb827e.camel@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a887f9c7a4d37a8e874ba8415a42a92a1b5139fc
Author: Charles Keepax <ckeepax@opensource.cirrus.com>
Date:   Thu Feb 10 17:20:51 2022 +0000

    ASoC: wm_adsp: Correct control read size when parsing compressed buffer
    
    When parsing the compressed stream the whole buffer descriptor is
    now read in a single cs_dsp_coeff_read_ctrl; on older firmwares
    this descriptor is just 4 bytes but on more modern firmwares it is
    24 bytes. The current code reads the full 24 bytes regardless, this
    was working but reading junk for the last 20 bytes. However commit
    f444da38ac92 ("firmware: cs_dsp: Add offset to cs_dsp read/write")
    added a size check into cs_dsp_coeff_read_ctrl, causing the older
    firmwares to now return an error.
    
    Update the code to only read the amount of data appropriate for
    the firmware loaded.
    
    Fixes: 04ae08596737 ("ASoC: wm_adsp: Switch to using wm_coeff_read_ctrl for compressed buffers")
    Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220210172053.22782-1-ckeepax@opensource.cirrus.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 6df2a016c0c8a3d0933ef33dd192ea6606b115e3
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Wed Jan 26 18:14:42 2022 +0100

    riscv: fix build with binutils 2.38
    
    From version 2.38, binutils default to ISA spec version 20191213. This
    means that the csr read/write (csrr*/csrw*) instructions and fence.i
    instruction has separated from the `I` extension, become two standalone
    extensions: Zicsr and Zifencei. As the kernel uses those instruction,
    this causes the following build failure:
    
      CC      arch/riscv/kernel/vdso/vgettimeofday.o
      <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h: Assembler messages:
      <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:71: Error: unrecognized opcode `csrr a5,0xc01'
      <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:71: Error: unrecognized opcode `csrr a5,0xc01'
      <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:71: Error: unrecognized opcode `csrr a5,0xc01'
      <<BUILDDIR>>/arch/riscv/include/asm/vdso/gettimeofday.h:71: Error: unrecognized opcode `csrr a5,0xc01'
    
    The fix is to specify those extensions explicitely in -march. However as
    older binutils version do not support this, we first need to detect
    that.
    
    Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
    Tested-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit f40fe31c01445f31253b15bef2412b33ae31093b
Author: Pingfan Liu <kernelfans@gmail.com>
Date:   Sun Jan 23 20:13:52 2022 +0800

    riscv: cpu-hotplug: clear cpu from numa map when teardown
    
    There is numa_add_cpu() when cpus online, accordingly, there should be
    numa_remove_cpu() when cpus offline.
    
    Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
    Fixes: 4f0e8eef772e ("riscv: Add numa support for riscv64 platform")
    Cc: stable@vger.kernel.org
    [Palmer: Add missing NUMA include]
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 5dbbbd01cbba831233c6ea9a3e6bfa133606d3c0
Author: Dave Ertman <david.m.ertman@intel.com>
Date:   Thu Jan 20 16:27:56 2022 -0800

    ice: Avoid RTNL lock when re-creating auxiliary device
    
    If a call to re-create the auxiliary device happens in a context that has
    already taken the RTNL lock, then the call flow that recreates auxiliary
    device can hang if there is another attempt to claim the RTNL lock by the
    auxiliary driver.
    
    To avoid this, any call to re-create auxiliary devices that comes from
    an source that is holding the RTNL lock (e.g. netdev notifier when
    interface exits a bond) should execute in a separate thread.  To
    accomplish this, add a flag to the PF that will be evaluated in the
    service task and dealt with there.
    
    Fixes: f9f5301e7e2d ("ice: Register auxiliary device to provide RDMA")
    Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
    Reviewed-by: Jonathan Toppins <jtoppins@redhat.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit bea1898f65b9b7096cb4e73e97c83b94718f1fa1
Author: Dave Ertman <david.m.ertman@intel.com>
Date:   Tue Jan 18 13:08:20 2022 -0800

    ice: Fix KASAN error in LAG NETDEV_UNREGISTER handler
    
    Currently, the same handler is called for both a NETDEV_BONDING_INFO
    LAG unlink notification as for a NETDEV_UNREGISTER call.  This is
    causing a problem though, since the netdev_notifier_info passed has
    a different structure depending on which event is passed.  The problem
    manifests as a call trace from a BUG: KASAN stack-out-of-bounds error.
    
    Fix this by creating a handler specific to NETDEV_UNREGISTER that only
    is passed valid elements in the netdev_notifier_info struct for the
    NETDEV_UNREGISTER event.
    
    Also included is the removal of an unbalanced dev_put on the peer_netdev
    and related braces.
    
    Fixes: 6a8b357278f5 ("ice: Respond to a NETDEV_UNREGISTER event for LAG")
    Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
    Acked-by: Jonathan Toppins <jtoppins@redhat.com>
    Tested-by: Sunitha Mekala <sunithax.d.mekala@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 46b699c50c0304cdbd725d7740073a7f9d5edb10
Author: Jesse Brandeburg <jesse.brandeburg@intel.com>
Date:   Fri Jan 14 15:38:39 2022 -0800

    ice: fix IPIP and SIT TSO offload
    
    The driver was avoiding offload for IPIP (at least) frames due to
    parsing the inner header offsets incorrectly when trying to check
    lengths.
    
    This length check works for VXLAN frames but fails on IPIP frames
    because skb_transport_offset points to the inner header in IPIP
    frames, which meant the subtraction of transport_header from
    inner_network_header returns a negative value (-20).
    
    With the code before this patch, everything continued to work, but GSO
    was being used to segment, causing throughputs of 1.5Gb/s per thread.
    After this patch, throughput is more like 10Gb/s per thread for IPIP
    traffic.
    
    Fixes: e94d44786693 ("ice: Implement filter sync, NDO operations and bump version")
    Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
    Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 21338d58736ef70eaae5fd75d567a358ff7902f9
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 11:02:06 2022 +0300

    ice: fix an error code in ice_cfg_phy_fec()
    
    Propagate the error code from ice_get_link_default_override() instead
    of returning success.
    
    Fixes: ea78ce4dab05 ("ice: add link lenient and default override support")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 249749c88906a00dc937a750406a36dfd11b5701
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Thu Feb 10 10:11:52 2022 +0100

    selftests: netfilter: synproxy test requires nf_conntrack
    
    Otherwise, this test does not find the sysctl entry in place:
    
     sysctl: cannot stat /proc/sys/net/netfilter/nf_conntrack_tcp_loose: No such file or directory
     iperf3: error - unable to send control message: Bad file descriptor
     FAIL: iperf3 returned an error
    
    Fixes: 7152303cbec4 ("selftests: netfilter: add synproxy test")
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 2b4e5fb4d3776c391e40fb33673ba946dd96012d
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Thu Feb 10 10:06:42 2022 +0100

    netfilter: nft_synproxy: unregister hooks on init error path
    
    Disable the IPv4 hooks if the IPv6 hooks fail to be registered.
    
    Fixes: ad49d86e07a4 ("netfilter: nf_tables: Add synproxy support")
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit c4416f5c2eb3ed48dfba265e628a6e52da962f03
Author: Victor Erminpour <victor.erminpour@oracle.com>
Date:   Wed Feb 9 16:28:38 2022 -0800

    net: mpls: Fix GCC 12 warning
    
    When building with automatic stack variable initialization, GCC 12
    complains about variables defined outside of switch case statements.
    Move the variable outside the switch, which silences the warning:
    
    ./net/mpls/af_mpls.c:1624:21: error: statement will never be executed [-Werror=switch-unreachable]
      1624 |                 int err;
           |                     ^~~
    
    Signed-off-by: Victor Erminpour <victor.erminpour@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9ccc6e0c8959a019bb40f6b18704b142c04b19a8
Author: Robert-Ionut Alexa <robert-ionut.alexa@nxp.com>
Date:   Wed Feb 9 17:57:43 2022 +0200

    dpaa2-eth: unregister the netdev before disconnecting from the PHY
    
    The netdev should be unregistered before we are disconnecting from the
    MAC/PHY so that the dev_close callback is called and the PHY and the
    phylink workqueues are actually stopped before we are disconnecting and
    destroying the phylink instance.
    
    Fixes: 719479230893 ("dpaa2-eth: add MAC/PHY support through phylink")
    Signed-off-by: Robert-Ionut Alexa <robert-ionut.alexa@nxp.com>
    Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 58e61e416b5abedcacd32032144b333bca30cf1e
Author: Tom Rix <trix@redhat.com>
Date:   Wed Feb 9 07:02:42 2022 -0800

    skbuff: cleanup double word in comment
    
    Remove the second 'to'.
    
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 37f7860602b5b2d99fc7465f6407f403f5941988
Author: Marc St-Amand <mstamand@ciena.com>
Date:   Wed Feb 9 15:13:25 2022 +0530

    net: macb: Align the dma and coherent dma masks
    
    Single page and coherent memory blocks can use different DMA masks
    when the macb accesses physical memory directly. The kernel is clever
    enough to allocate pages that fit into the requested address width.
    
    When using the ARM SMMU, the DMA mask must be the same for single
    pages and big coherent memory blocks. Otherwise the translation
    tables turn into one big mess.
    
      [   74.959909] macb ff0e0000.ethernet eth0: DMA bus error: HRESP not OK
      [   74.959989] arm-smmu fd800000.smmu: Unhandled context fault: fsr=0x402, iova=0x3165687460, fsynr=0x20001, cbfrsynra=0x877, cb=1
      [   75.173939] macb ff0e0000.ethernet eth0: DMA bus error: HRESP not OK
      [   75.173955] arm-smmu fd800000.smmu: Unhandled context fault: fsr=0x402, iova=0x3165687460, fsynr=0x20001, cbfrsynra=0x877, cb=1
    
    Since using the same DMA mask does not hurt direct 1:1 physical
    memory mappings, this commit always aligns DMA and coherent masks.
    
    Signed-off-by: Marc St-Amand <mstamand@ciena.com>
    Signed-off-by: Harini Katakam <harini.katakam@xilinx.com>
    Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 93e2c52d71a6067d08ee927e2682e9781cb911ef
Merge: b13e0c7185681 63573807b27e0
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Feb 10 06:56:43 2022 -0700

    Merge tag 'nvme-5.17-2022-02-10' of git://git.infradead.org/nvme into block-5.17
    
    Pull NVMe fixes from Christoph:
    
    "nvme fixes for Linux 5.17
    
     - nvme-tcp: fix bogus request completion when failing to send AER
       (Sagi Grimberg)
     - add the missing nvme_complete_req tracepoint for batched completion
       (Bean Huo)"
    
    * tag 'nvme-5.17-2022-02-10' of git://git.infradead.org/nvme:
      nvme-tcp: fix bogus request completion when failing to send AER
      nvme: add nvme_complete_req tracepoint for batched completion

commit e3c85076d7a6f986445b9008be7e7f83d1b0780a
Merge: 252787201edfd d9565bf40da22
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 10 05:52:00 2022 -0800

    Merge tag 'mips-fixes-5.17_3' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
    
    Pull MIPS fix from Thomas Bogendoerfer:
     "Device tree fix for Ingenic CI20"
    
    * tag 'mips-fixes-5.17_3' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux:
      MIPS: DTS: CI20: fix how ddc power is enabled

commit 252787201edfdf563ddf6b6006aa534ddc504031
Merge: 9aa422ad32663 7a82f89de92aa
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 10 05:43:43 2022 -0800

    Merge tag 'audit-pr-20220209' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit
    
    Pull audit fix from Paul Moore:
     "Another audit fix, this time a single rather small but important fix
      for an oops/page-fault caused by improperly accessing userspace
      memory"
    
    * tag 'audit-pr-20220209' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit:
      audit: don't deref the syscall args when checking the openat2 open_how::flags

commit 9aa422ad326634b76309e8ff342c246800621216
Author: Jon Maloy <jmaloy@redhat.com>
Date:   Sat Feb 5 14:11:18 2022 -0500

    tipc: improve size validations for received domain records
    
    The function tipc_mon_rcv() allows a node to receive and process
    domain_record structs from peer nodes to track their views of the
    network topology.
    
    This patch verifies that the number of members in a received domain
    record does not exceed the limit defined by MAX_MON_DOMAIN, something
    that may otherwise lead to a stack overflow.
    
    tipc_mon_rcv() is called from the function tipc_link_proto_rcv(), where
    we are reading a 32 bit message data length field into a uint16.  To
    avert any risk of bit overflow, we add an extra sanity check for this in
    that function.  We cannot see that happen with the current code, but
    future designers being unaware of this risk, may introduce it by
    allowing delivery of very large (> 64k) sk buffers from the bearer
    layer.  This potential problem was identified by Eric Dumazet.
    
    This fixes CVE-2022-0435
    
    Reported-by: Samuel Page <samuel.page@appgate.com>
    Reported-by: Eric Dumazet <edumazet@google.com>
    Fixes: 35c55c9877f8 ("tipc: add neighbor monitoring framework")
    Signed-off-by: Jon Maloy <jmaloy@redhat.com>
    Reviewed-by: Xin Long <lucien.xin@gmail.com>
    Reviewed-by: Samuel Page <samuel.page@appgate.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c8d251f51ee61df06ee0e419348d8c9160bbfb86
Author: Stephen Boyd <swboyd@chromium.org>
Date:   Wed Feb 9 15:25:20 2022 -0800

    ASoC: qcom: Actually clear DMA interrupt register for HDMI
    
    In commit da0363f7bfd3 ("ASoC: qcom: Fix for DMA interrupt clear reg
    overwriting") we changed regmap_write() to regmap_update_bits() so that
    we can avoid overwriting bits that we didn't intend to modify.
    Unfortunately this change breaks the case where a register is writable
    but not readable, which is exactly how the HDMI irq clear register is
    designed (grep around LPASS_HDMITX_APP_IRQCLEAR_REG to see how it's
    write only). That's because regmap_update_bits() tries to read the
    register from the hardware and if it isn't readable it looks in the
    regmap cache to see what was written there last time to compare against
    what we want to write there. Eventually, we're unable to modify this
    register at all because the bits that we're trying to set are already
    set in the cache.
    
    This is doubly bad for the irq clear register because you have to write
    the bit to clear an interrupt. Given the irq is level triggered, we see
    an interrupt storm upon plugging in an HDMI cable and starting audio
    playback. The irq storm is so great that performance degrades
    significantly, leading to CPU soft lockups.
    
    Fix it by using regmap_write_bits() so that we really do write the bits
    in the clear register that we want to. This brings the number of irqs
    handled by lpass_dma_interrupt_handler() down from ~150k/sec to ~10/sec.
    
    Fixes: da0363f7bfd3 ("ASoC: qcom: Fix for DMA interrupt clear reg overwriting")
    Cc: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
    Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Signed-off-by: Stephen Boyd <swboyd@chromium.org>
    Link: https://lore.kernel.org/r/20220209232520.4017634-1-swboyd@chromium.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3e16dc50d77dc3494275a241fac250c94bf45206
Author: Takashi Iwai <tiwai@suse.de>
Date:   Thu Feb 10 13:33:44 2022 +0100

    ALSA: memalloc: invalidate SG pages before sync
    
    It seems that calling invalidate_kernel_vmap_range() is more correct
    to be called before dma_sync_*(), judging from the other thread:
      https://lore.kernel.org/all/20220111085958.GA22795@lst.de/
    Although this won't matter much in practice, let's fix the call order
    for consistency.
    
    Fixes: a25684a95646 ("ALSA: memalloc: Support for non-contiguous page allocation")
    Reported-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220210123344.8756-3-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 8e1741c658996a16bd096e077dae0da2460a997f
Author: Takashi Iwai <tiwai@suse.de>
Date:   Thu Feb 10 13:33:43 2022 +0100

    ALSA: memalloc: Fix dma_need_sync() checks
    
    dma_need_sync() checks each DMA address.  Fix the incorrect usages
    for non-contiguous and non-coherent page allocations.
    Fortunately, there are no actual call sites that need manual syncs
    yet.
    
    Fixes: a25684a95646 ("ALSA: memalloc: Support for non-contiguous page allocation")
    Fixes: 73325f60e2ed ("ALSA: memalloc: Support for non-coherent page allocation")
    Cc: <stable@vger.kernel.org>
    Reported-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
    Link: https://lore.kernel.org/r/20220210123344.8756-2-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit f66edf684edcb85c1db0b0aa8cf1a9392ba68a9d
Author: Cai Huoqing <cai.huoqing@linux.dev>
Date:   Wed Feb 9 11:28:41 2022 +0800

    xen/pci: Make use of the helper macro LIST_HEAD()
    
    Replace "struct list_head head = LIST_HEAD_INIT(head)" with
    "LIST_HEAD(head)" to simplify the code.
    
    Signed-off-by: Cai Huoqing <cai.huoqing@linux.dev>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Link: https://lore.kernel.org/r/20220209032842.38818-1-cai.huoqing@linux.dev
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit afea27dc3105004080c3127c6570dc3dff8563b2
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Mon Feb 7 18:35:06 2022 +0800

    xen/x2apic: Fix inconsistent indenting
    
    Eliminate the follow smatch warning:
    
    arch/x86/xen/enlighten_hvm.c:189 xen_cpu_dead_hvm() warn: inconsistent
    indenting.
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Link: https://lore.kernel.org/r/20220207103506.102008-1-jiapeng.chong@linux.alibaba.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit e07e98da924e61e814bdaaa3ebc6e72b60dbf9ed
Author: Roger Pau Monne <roger.pau@citrix.com>
Date:   Thu Jan 20 16:25:27 2022 +0100

    xen/x86: detect support for extended destination ID
    
    Xen allows the usage of some previously reserved bits in the IO-APIC
    RTE and the MSI address fields in order to store high bits for the
    target APIC ID. Such feature is already implemented by QEMU/KVM and
    HyperV, so in order to enable it just add the handler that checks for
    it's presence.
    
    Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Link: https://lore.kernel.org/r/20220120152527.7524-3-roger.pau@citrix.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit f34c4f2dd2445ab89e5373fff2990fab36578bd3
Author: Jan Beulich <jbeulich@suse.com>
Date:   Mon Feb 7 08:41:03 2022 +0100

    xen/x86: obtain full video frame buffer address for Dom0 also under EFI
    
    The initial change would not work when Xen was booted from EFI: There is
    an early exit from the case block in that case. Move the necessary code
    ahead of that.
    
    Fixes: 335e4dd67b48 ("xen/x86: obtain upper 32 bits of video frame buffer address for Dom0")
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    
    Link: https://lore.kernel.org/r/2501ce9d-40e5-b49d-b0e5-435544d17d4a@suse.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit 5e5eddd94c8906472e3904cb11b4e3ccbb99d0d4
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Feb 10 09:57:48 2022 +0100

    Revert "arm64: dts: imx8mn-venice-gw7902: disable gpu"
    
    This reverts commit 0c566618e27f17b5807086dba8c222ca8ca3dc1e,
    this one was meant for v5.18, not as a bugfix, though the
    patch itself was correct.
    
    Reported-by: Shawn Guo <shawnguo@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit bea2662e7818e15d7607d17d57912ac984275d94
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Tue Feb 8 11:47:30 2022 +0100

    iwlwifi: fix use-after-free
    
    If no firmware was present at all (or, presumably, all of the
    firmware files failed to parse), we end up unbinding by calling
    device_release_driver(), which calls remove(), which then in
    iwlwifi calls iwl_drv_stop(), freeing the 'drv' struct. However
    the new code I added will still erroneously access it after it
    was freed.
    
    Set 'failure=false' in this case to avoid the access, all data
    was already freed anyway.
    
    Cc: stable@vger.kernel.org
    Reported-by: Stefan Agner <stefan@agner.ch>
    Reported-by: Wolfgang Walter <linux@stwm.de>
    Reported-by: Jason Self <jason@bluehome.net>
    Reported-by: Dominik Behr <dominik@dominikbehr.com>
    Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
    Fixes: ab07506b0454 ("iwlwifi: fix leaks/bad data after failed firmware load")
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220208114728.e6b514cf4c85.Iffb575ca2a623d7859b542c33b2a507d01554251@changeid

commit 4e9120cbaca118f35a31a5e9986063e722614378
Merge: 8ecbb179286cb 029744cd4bc6e
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Feb 9 21:44:37 2022 -0800

    Merge branch 'mptcp-fixes-for-5-17'
    
    Mat Martineau says:
    
    ====================
    mptcp: Fixes for 5.17
    
    Patch 1 fixes a MPTCP selftest bug that combined the results of two
    separate tests in the test output.
    
    Patch 2 fixes a problem where advertised IPv6 addresses were not actually
    available for incoming MP_JOIN requests.
    ====================
    
    Link: https://lore.kernel.org/r/20220210012508.226880-1-mathew.j.martineau@linux.intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 029744cd4bc6e9eb3bd833b4a033348296d34645
Author: Kishen Maloor <kishen.maloor@intel.com>
Date:   Wed Feb 9 17:25:08 2022 -0800

    mptcp: netlink: process IPv6 addrs in creating listening sockets
    
    This change updates mptcp_pm_nl_create_listen_socket() to create
    listening sockets bound to IPv6 addresses (where IPv6 is supported).
    
    Fixes: 1729cf186d8a ("mptcp: create the listening socket for new port")
    Acked-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 857898eb4b28daf3faca3ae334c78b2bb141475e
Author: Matthieu Baerts <matthieu.baerts@tessares.net>
Date:   Wed Feb 9 17:25:07 2022 -0800

    selftests: mptcp: add missing join check
    
    This function also writes the name of the test with its ID, making clear
    a new test has been executed.
    
    Without that, the ADD_ADDR results from this test was appended at the
    end of the previous test causing confusions. Especially when the second
    test was failing, we had:
    
      17 signal invalid addresses     syn[ ok ] - synack[ ok ] - ack[ ok ]
                                      add[ ok ] - echo  [ ok ]
                                      add[fail] got 2 ADD_ADDR[s] expected 3
    
    In fact, this 17th test was OK but not the 18th one.
    
    Now we have:
    
      17 signal invalid addresses     syn[ ok ] - synack[ ok ] - ack[ ok ]
                                      add[ ok ] - echo  [ ok ]
      18 signal addresses race test   syn[fail] got 2 JOIN[s] syn expected 3
       - synack[fail] got 2 JOIN[s] synack expected
       - ack[fail] got 2 JOIN[s] ack expected 3
                                      add[fail] got 2 ADD_ADDR[s] expected 3
    
    Fixes: 33c563ad28e3 ("selftests: mptcp: add_addr and echo race test")
    Reported-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit b97cca3ba9098522e5a1c3388764ead42640c1a5
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Thu Feb 3 08:29:21 2022 -0800

    xfs: only bother with sync_filesystem during readonly remount
    
    In commit 02b9984d6408, we pushed a sync_filesystem() call from the VFS
    into xfs_fs_remount.  The only time that we ever need to push dirty file
    data or metadata to disk for a remount is if we're remounting the
    filesystem read only, so this really could be moved to xfs_remount_ro.
    
    Once we've moved the call site, actually check the return value from
    sync_filesystem.
    
    Fixes: 02b9984d6408 ("fs: push sync_filesystem() down to the file system's remount_fs()")
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit 8ecbb179286cbc91810c16caeb3396e06305cd0c
Author: Slark Xiao <slark_xiao@163.com>
Date:   Wed Feb 9 10:47:17 2022 +0800

    net: usb: qmi_wwan: Add support for Dell DW5829e
    
    Dell DW5829e same as DW5821e except the CAT level.
    DW5821e supports CAT16 but DW5829e supports CAT9.
    Also, DW5829e includes normal and eSIM type.
    Please see below test evidence:
    
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  5 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  1
    P:  Vendor=413c ProdID=81e6 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    
    T:  Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  7 Spd=5000 MxCh= 0
    D:  Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs=  1
    P:  Vendor=413c ProdID=81e4 Rev=03.18
    S:  Manufacturer=Dell Inc.
    S:  Product=DW5829e-eSIM Snapdragon X20 LTE
    S:  SerialNumber=0123456789ABCDEF
    C:  #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=896mA
    I:  If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    I:  If#=0x1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
    I:  If#=0x2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
    I:  If#=0x5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    
    Signed-off-by: Slark Xiao <slark_xiao@163.com>
    Acked-by: Bjørn Mork <bjorn@mork.no>
    Link: https://lore.kernel.org/r/20220209024717.8564-1-slark_xiao@163.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d23a0c3718222a42430fd56359478a6fc7675070
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Feb 8 15:26:18 2022 +0900

    kconfig: fix missing fclose() on error paths
    
    The file is not closed when ferror() fails.
    
    Fixes: 00d674cb3536 ("kconfig: refactor conf_write_dep()")
    Fixes: 57ddd07c4560 ("kconfig: refactor conf_write_autoconf()")
    Reported-by: Ryan Cai <ycaibb@gmail.com>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 6e7545ddb13416fd200e0b91c0acfd0404e2e27b
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Feb 3 10:04:58 2022 -0500

    drm/amdgpu/display: change pipe policy for DCN 2.0
    
    Fixes hangs on driver load with multiple displays on
    DCN 2.0 parts.
    
    Bug: https://bugzilla.kernel.org/show_bug.cgi?id=215511
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1877
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1886
    Fixes: ee2698cf79cc ("drm/amd/display: Changed pipe split policy to allow for multi-display pipe split")
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit dd9cb842fa9d90653a9b48aba52f89c069f3bc50
Author: Vineeth Vijayan <vneethv@linux.ibm.com>
Date:   Wed Feb 2 21:45:56 2022 +0100

    s390/cio: verify the driver availability for path_event call
    
    If no driver is attached to a device or the driver does not provide the
    path_event function, an FCES path-event on this device could end up in a
    kernel-panic. Verify the driver availability before the path_event
    function call.
    
    Fixes: 32ef938815c1 ("s390/cio: Add support for FCES status notification")
    Cc: stable@vger.kernel.org
    Signed-off-by: Vineeth Vijayan <vneethv@linux.ibm.com>
    Suggested-by: Peter Oberparleiter <oberpar@linux.ibm.com>
    Reviewed-by: Jan Hoeppner <hoeppner@linux.ibm.com>
    Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 7a82f89de92aac5a244d3735b2bd162c1147620c
Author: Paul Moore <paul@paul-moore.com>
Date:   Wed Feb 9 14:49:38 2022 -0500

    audit: don't deref the syscall args when checking the openat2 open_how::flags
    
    As reported by Jeff, dereferencing the openat2 syscall argument in
    audit_match_perm() to obtain the open_how::flags can result in an
    oops/page-fault.  This patch fixes this by using the open_how struct
    that we store in the audit_context with audit_openat2_how().
    
    Independent of this patch, Richard Guy Briggs posted a similar patch
    to the audit mailing list roughly 40 minutes after this patch was
    posted.
    
    Cc: stable@vger.kernel.org
    Fixes: 1c30e3af8a79 ("audit: add support for the openat2 syscall")
    Reported-by: Jeff Mahoney <jeffm@suse.com>
    Signed-off-by: Paul Moore <paul@paul-moore.com>

commit a8b1e8636a3252daa729762b2e3cc9015cc91a5c
Author: Yang Wang <KevinYang.Wang@amd.com>
Date:   Tue Feb 8 14:23:55 2022 +0800

    drm/amd/pm: fix hwmon node of power1_label create issue
    
    it will cause hwmon node of power1_label is not created.
    
    v2:
    the hwmon node of "power1_label" is always needed for all ASICs.
    and the patch will remove ASIC type check for "power1_label".
    
    Fixes: ae07970a0621d6 ("drm/amd/pm: add support for hwmon control of slow and fast PPT limit on vangogh")
    
    Signed-off-by: Yang Wang <KevinYang.Wang@amd.com>
    Reviewed-by: Kenneth Feng <kenneth.feng@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ad787771b43602d64e02b5963f4192232b46366b
Author: Zhan Liu <Zhan.Liu@amd.com>
Date:   Thu Jan 27 22:08:53 2022 -0500

    drm/amd/display: keep eDP Vdd on when eDP stream is already enabled
    
    [Why]
    Even if can_apply_edp_fast_boot is set to 1 at boot, this flag will
    be cleared to 0 at S3 resume.
    
    [How]
    Keep eDP Vdd on when eDP stream is already enabled.
    
    Reviewed-by: Charlene Liu <Charlene.Liu@amd.com>
    Acked-by: Jasdeep Dhillon <jdhillon@amd.com>
    Signed-off-by: Zhan Liu <Zhan.Liu@amd.com>
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 60fdf98a774eee244a4e00c34a9e7729b61d0f44
Author: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
Date:   Thu Jan 27 11:55:49 2022 -0500

    drm/amd/display: fix yellow carp wm clamping
    
    Fix clamping to match register field size
    
    Reviewed-by: Charlene Liu <Charlene.Liu@amd.com>
    Acked-by: Jasdeep Dhillon <jdhillon@amd.com>
    Signed-off-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 328e34a5ad227399391891d454043e5d73e598d2
Author: Roman Li <Roman.Li@amd.com>
Date:   Wed Feb 2 14:30:09 2022 -0500

    drm/amd/display: Cap pflip irqs per max otg number
    
    [Why]
    pflip interrupt order are mapped 1 to 1 to otg id.
    e.g. if irq_src=26 corresponds to otg0 then 27->otg1, 28->otg2...
    
    Linux DM registers pflip interrupts per number of crtcs.
    In fused pipe case crtc numbers can be less than otg id.
    
    e.g. if one pipe out of 3(otg#0-2) is fused adev->mode_info.num_crtc=2
    so DM only registers irq_src 26,27.
    This is a bug since if pipe#2 remains unfused DM never gets
    otg2 pflip interrupt (irq_src=28)
    That may results in gfx failure due to pflip timeout.
    
    [How]
    Register pflip interrupts per max num of otg instead of num_crtc
    
    Signed-off-by: Roman Li <Roman.Li@amd.com>
    Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit a072312f43c33ea02ad88bff3375f650684a6f24
Author: Aaron Liu <aaron.liu@amd.com>
Date:   Sat Jan 29 09:21:31 2022 +0800

    drm/amdgpu: add utcl2_harvest to gc 10.3.1
    
    Confirmed with hardware team, there is harvesting for gc 10.3.1.
    
    Signed-off-by: Aaron Liu <aaron.liu@amd.com>
    Reviewed-by: Huang Rui <ray.huang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 03ad3093c7c069d6ab4403730009ebafeea9ee37
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Jan 25 15:49:47 2022 -0600

    display/amd: decrease message verbosity about watermarks table failure
    
    A number of BIOS versions have a problem with the watermarks table not
    being configured properly.  This manifests as a very scary looking warning
    during resume from s0i3.  This should be harmless in most cases and is well
    understood, so decrease the assertion to a clearer warning about the problem.
    
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 268a491aebc25e6dc7c618903b09ac3a2e8af530
Author: Dinh Nguyen <dinguyen@kernel.org>
Date:   Thu Jan 6 17:53:31 2022 -0600

    arm64: dts: agilex: use the compatible "intel,socfpga-agilex-hsotg"
    
    The DWC2 USB controller on the Agilex platform does not support clock
    gating, so use the chip specific "intel,socfpga-agilex-hsotg"
    compatible.
    
    Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>

commit 728390fce4fc4d033a898fb6f5088697d03254b8
Author: Dinh Nguyen <dinguyen@kernel.org>
Date:   Thu Jan 6 17:37:03 2022 -0600

    dt-bindings: usb: dwc2: add compatible "intel,socfpga-agilex-hsotg"
    
    Add the compatible "intel,socfpga-agilex-hsotg" to the DWC2
    implementation, because the Agilex DWC2 implementation does not support
    clock gating.
    
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>

commit 3eb616b26408ac813c67280cf883f36d98b8441d
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Feb 9 17:13:42 2022 +0100

    x86/PCI: revert "Ignore E820 reservations for bridge windows on newer systems"
    
    Commit 7f7b4236f204 ("x86/PCI: Ignore E820 reservations for bridge windows
    on newer systems") fixes the touchpad not working on laptops like
    the Lenovo IdeaPad 3 15IIL05 and the Lenovo IdeaPad 5 14IIL05, as well as
    fixing thunderbolt hotplug issues on the Lenovo Yoga C940.
    
    Unfortunately it turns out that this is causing issues with suspend/resume
    on Lenovo ThinkPad X1 Carbon Gen 2 laptops. So, per the no regressions
    policy, rever this. Note I'm looking into another fix for the issues this
    fixed.
    
    Fixes: 7f7b4236f204 ("x86/PCI: Ignore E820 reservations for bridge windows on newer systems")
    BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2029207
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit da5fb9e1ad3fbf632dce735f1bdad257ca528499
Author: Robin Murphy <robin.murphy@arm.com>
Date:   Thu Feb 3 19:31:24 2022 +0000

    ACPI/IORT: Check node revision for PMCG resources
    
    The original version of the IORT PMCG definition had an oversight
    wherein there was no way to describe the second register page for an
    implementation using the recommended RELOC_CTRS feature. Although the
    spec was fixed, and the final patches merged to ACPICA and Linux written
    against the new version, it seems that some old firmware based on the
    original revision has survived and turned up in the wild.
    
    Add a check for the original PMCG definition, and avoid filling in the
    second memory resource with nonsense if so. Otherwise it is likely that
    something horrible will happen when the PMCG driver attempts to probe.
    
    Reported-by: Michael Petlan <mpetlan@redhat.com>
    Fixes: 24e516049360 ("ACPI/IORT: Add support for PMCG")
    Cc: <stable@vger.kernel.org> # 5.2.x
    Signed-off-by: Robin Murphy <robin.murphy@arm.com>
    Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Link: https://lore.kernel.org/r/75628ae41c257fb73588f7bf1c4459160e04be2b.1643916258.git.robin.murphy@arm.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit f4bc5bbb5fef3cf421ba3485d6d383c27ec473ed
Merge: f9f94c9d2c070 c306d737691ef
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 9 09:56:57 2022 -0800

    Merge tag 'nfsd-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
    
    Pull more nfsd fixes from Chuck Lever:
     "Ensure that NFS clients cannot send file size or offset values that
      can cause the NFS server to crash or to return incorrect or surprising
      results.
    
      In particular, fix how the NFS server handles values larger than
      OFFSET_MAX"
    
    * tag 'nfsd-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux:
      NFSD: Deprecate NFS_OFFSET_MAX
      NFSD: Fix offset type in I/O trace points
      NFSD: COMMIT operations must not return NFS?ERR_INVAL
      NFSD: Clamp WRITE offsets
      NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
      NFSD: Fix ia_size underflow
      NFSD: Fix the behavior of READ near OFFSET_MAX

commit f9f94c9d2c070941a5688f0f751a489c7d0e5039
Merge: b42bc9a3c5115 c6ce9c5831cae
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 9 09:53:56 2022 -0800

    Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6
    
    Pull crypto fixes from Herbert Xu:
     "Fix two regressions:
    
       - Potential boot failure due to missing cryptomgr on initramfs
    
       - Stack overflow in octeontx2"
    
    * 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6:
      crypto: api - Move cryptomgr soft dependency into algapi
      crypto: octeontx2 - Avoid stack variable overflow

commit 2e7be9db125a0bf940c5d65eb5c40d8700f738b5
Author: Dāvis Mosāns <davispuh@gmail.com>
Date:   Sat Feb 5 20:48:23 2022 +0200

    btrfs: send: in case of IO error log it
    
    Currently if we get IO error while doing send then we abort without
    logging information about which file caused issue.  So log it to help
    with debugging.
    
    CC: stable@vger.kernel.org # 4.9+
    Signed-off-by: Dāvis Mosāns <davispuh@gmail.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a0f0cf8341e34e5d2265bfd3a7ad68342da1e2aa
Author: Filipe Manana <fdmanana@suse.com>
Date:   Wed Feb 2 15:26:09 2022 +0000

    btrfs: get rid of warning on transaction commit when using flushoncommit
    
    When using the flushoncommit mount option, during almost every transaction
    commit we trigger a warning from __writeback_inodes_sb_nr():
    
      $ cat fs/fs-writeback.c:
      (...)
      static void __writeback_inodes_sb_nr(struct super_block *sb, ...
      {
            (...)
            WARN_ON(!rwsem_is_locked(&sb->s_umount));
            (...)
      }
      (...)
    
    The trace produced in dmesg looks like the following:
    
      [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3
      [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif
      [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186
      [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3
      [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...)
      [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246
      [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000
      [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50
      [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000
      [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488
      [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460
      [947.553621] FS:  0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000
      [947.560537] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0
      [947.571072] Call Trace:
      [947.572354]  <TASK>
      [947.573266]  btrfs_commit_transaction+0x1f1/0x998
      [947.576785]  ? start_transaction+0x3ab/0x44e
      [947.579867]  ? schedule_timeout+0x8a/0xdd
      [947.582716]  transaction_kthread+0xe9/0x156
      [947.585721]  ? btrfs_cleanup_transaction.isra.0+0x407/0x407
      [947.590104]  kthread+0x131/0x139
      [947.592168]  ? set_kthread_struct+0x32/0x32
      [947.595174]  ret_from_fork+0x22/0x30
      [947.597561]  </TASK>
      [947.598553] ---[ end trace 644721052755541c ]---
    
    This is because we started using writeback_inodes_sb() to flush delalloc
    when committing a transaction (when using -o flushoncommit), in order to
    avoid deadlocks with filesystem freeze operations. This change was made
    by commit ce8ea7cc6eb313 ("btrfs: don't call btrfs_start_delalloc_roots
    in flushoncommit"). After that change we started producing that warning,
    and every now and then a user reports this since the warning happens too
    often, it spams dmesg/syslog, and a user is unsure if this reflects any
    problem that might compromise the filesystem's reliability.
    
    We can not just lock the sb->s_umount semaphore before calling
    writeback_inodes_sb(), because that would at least deadlock with
    filesystem freezing, since at fs/super.c:freeze_super() sync_filesystem()
    is called while we are holding that semaphore in write mode, and that can
    trigger a transaction commit, resulting in a deadlock. It would also
    trigger the same type of deadlock in the unmount path. Possibly, it could
    also introduce some other locking dependencies that lockdep would report.
    
    To fix this call try_to_writeback_inodes_sb() instead of
    writeback_inodes_sb(), because that will try to read lock sb->s_umount
    and then will only call writeback_inodes_sb() if it was able to lock it.
    This is fine because the cases where it can't read lock sb->s_umount
    are during a filesystem unmount or during a filesystem freeze - in those
    cases sb->s_umount is write locked and sync_filesystem() is called, which
    calls writeback_inodes_sb(). In other words, in all cases where we can't
    take a read lock on sb->s_umount, writeback is already being triggered
    elsewhere.
    
    An alternative would be to call btrfs_start_delalloc_roots() with a
    number of pages different from LONG_MAX, for example matching the number
    of delalloc bytes we currently have, in which case we would end up
    starting all delalloc with filemap_fdatawrite_wbc() and not with an
    async flush via filemap_flush() - that is only possible after the rather
    recent commit e076ab2a2ca70a ("btrfs: shrink delalloc pages instead of
    full inodes"). However that creates a whole new can of worms due to new
    lock dependencies, which lockdep complains, like for example:
    
    [ 8948.247280] ======================================================
    [ 8948.247823] WARNING: possible circular locking dependency detected
    [ 8948.248353] 5.17.0-rc1-btrfs-next-111 #1 Not tainted
    [ 8948.248786] ------------------------------------------------------
    [ 8948.249320] kworker/u16:18/933570 is trying to acquire lock:
    [ 8948.249812] ffff9b3de1591690 (sb_internal#2){.+.+}-{0:0}, at: find_free_extent+0x141e/0x1590 [btrfs]
    [ 8948.250638]
                   but task is already holding lock:
    [ 8948.251140] ffff9b3e09c717d8 (&root->delalloc_mutex){+.+.}-{3:3}, at: start_delalloc_inodes+0x78/0x400 [btrfs]
    [ 8948.252018]
                   which lock already depends on the new lock.
    
    [ 8948.252710]
                   the existing dependency chain (in reverse order) is:
    [ 8948.253343]
                   -> #2 (&root->delalloc_mutex){+.+.}-{3:3}:
    [ 8948.253950]        __mutex_lock+0x90/0x900
    [ 8948.254354]        start_delalloc_inodes+0x78/0x400 [btrfs]
    [ 8948.254859]        btrfs_start_delalloc_roots+0x194/0x2a0 [btrfs]
    [ 8948.255408]        btrfs_commit_transaction+0x32f/0xc00 [btrfs]
    [ 8948.255942]        btrfs_mksubvol+0x380/0x570 [btrfs]
    [ 8948.256406]        btrfs_mksnapshot+0x81/0xb0 [btrfs]
    [ 8948.256870]        __btrfs_ioctl_snap_create+0x17f/0x190 [btrfs]
    [ 8948.257413]        btrfs_ioctl_snap_create_v2+0xbb/0x140 [btrfs]
    [ 8948.257961]        btrfs_ioctl+0x1196/0x3630 [btrfs]
    [ 8948.258418]        __x64_sys_ioctl+0x83/0xb0
    [ 8948.258793]        do_syscall_64+0x3b/0xc0
    [ 8948.259146]        entry_SYSCALL_64_after_hwframe+0x44/0xae
    [ 8948.259709]
                   -> #1 (&fs_info->delalloc_root_mutex){+.+.}-{3:3}:
    [ 8948.260330]        __mutex_lock+0x90/0x900
    [ 8948.260692]        btrfs_start_delalloc_roots+0x97/0x2a0 [btrfs]
    [ 8948.261234]        btrfs_commit_transaction+0x32f/0xc00 [btrfs]
    [ 8948.261766]        btrfs_set_free_space_cache_v1_active+0x38/0x60 [btrfs]
    [ 8948.262379]        btrfs_start_pre_rw_mount+0x119/0x180 [btrfs]
    [ 8948.262909]        open_ctree+0x1511/0x171e [btrfs]
    [ 8948.263359]        btrfs_mount_root.cold+0x12/0xde [btrfs]
    [ 8948.263863]        legacy_get_tree+0x30/0x50
    [ 8948.264242]        vfs_get_tree+0x28/0xc0
    [ 8948.264594]        vfs_kern_mount.part.0+0x71/0xb0
    [ 8948.265017]        btrfs_mount+0x11d/0x3a0 [btrfs]
    [ 8948.265462]        legacy_get_tree+0x30/0x50
    [ 8948.265851]        vfs_get_tree+0x28/0xc0
    [ 8948.266203]        path_mount+0x2d4/0xbe0
    [ 8948.266554]        __x64_sys_mount+0x103/0x140
    [ 8948.266940]        do_syscall_64+0x3b/0xc0
    [ 8948.267300]        entry_SYSCALL_64_after_hwframe+0x44/0xae
    [ 8948.267790]
                   -> #0 (sb_internal#2){.+.+}-{0:0}:
    [ 8948.268322]        __lock_acquire+0x12e8/0x2260
    [ 8948.268733]        lock_acquire+0xd7/0x310
    [ 8948.269092]        start_transaction+0x44c/0x6e0 [btrfs]
    [ 8948.269591]        find_free_extent+0x141e/0x1590 [btrfs]
    [ 8948.270087]        btrfs_reserve_extent+0x14b/0x280 [btrfs]
    [ 8948.270588]        cow_file_range+0x17e/0x490 [btrfs]
    [ 8948.271051]        btrfs_run_delalloc_range+0x345/0x7a0 [btrfs]
    [ 8948.271586]        writepage_delalloc+0xb5/0x170 [btrfs]
    [ 8948.272071]        __extent_writepage+0x156/0x3c0 [btrfs]
    [ 8948.272579]        extent_write_cache_pages+0x263/0x460 [btrfs]
    [ 8948.273113]        extent_writepages+0x76/0x130 [btrfs]
    [ 8948.273573]        do_writepages+0xd2/0x1c0
    [ 8948.273942]        filemap_fdatawrite_wbc+0x68/0x90
    [ 8948.274371]        start_delalloc_inodes+0x17f/0x400 [btrfs]
    [ 8948.274876]        btrfs_start_delalloc_roots+0x194/0x2a0 [btrfs]
    [ 8948.275417]        flush_space+0x1f2/0x630 [btrfs]
    [ 8948.275863]        btrfs_async_reclaim_data_space+0x108/0x1b0 [btrfs]
    [ 8948.276438]        process_one_work+0x252/0x5a0
    [ 8948.276829]        worker_thread+0x55/0x3b0
    [ 8948.277189]        kthread+0xf2/0x120
    [ 8948.277506]        ret_from_fork+0x22/0x30
    [ 8948.277868]
                   other info that might help us debug this:
    
    [ 8948.278548] Chain exists of:
                     sb_internal#2 --> &fs_info->delalloc_root_mutex --> &root->delalloc_mutex
    
    [ 8948.279601]  Possible unsafe locking scenario:
    
    [ 8948.280102]        CPU0                    CPU1
    [ 8948.280508]        ----                    ----
    [ 8948.280915]   lock(&root->delalloc_mutex);
    [ 8948.281271]                                lock(&fs_info->delalloc_root_mutex);
    [ 8948.281915]                                lock(&root->delalloc_mutex);
    [ 8948.282487]   lock(sb_internal#2);
    [ 8948.282800]
                    *** DEADLOCK ***
    
    [ 8948.283333] 4 locks held by kworker/u16:18/933570:
    [ 8948.283750]  #0: ffff9b3dc00a9d48 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x1d2/0x5a0
    [ 8948.284609]  #1: ffffa90349dafe70 ((work_completion)(&fs_info->async_data_reclaim_work)){+.+.}-{0:0}, at: process_one_work+0x1d2/0x5a0
    [ 8948.285637]  #2: ffff9b3e14db5040 (&fs_info->delalloc_root_mutex){+.+.}-{3:3}, at: btrfs_start_delalloc_roots+0x97/0x2a0 [btrfs]
    [ 8948.286674]  #3: ffff9b3e09c717d8 (&root->delalloc_mutex){+.+.}-{3:3}, at: start_delalloc_inodes+0x78/0x400 [btrfs]
    [ 8948.287596]
                  stack backtrace:
    [ 8948.287975] CPU: 3 PID: 933570 Comm: kworker/u16:18 Not tainted 5.17.0-rc1-btrfs-next-111 #1
    [ 8948.288677] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
    [ 8948.289649] Workqueue: events_unbound btrfs_async_reclaim_data_space [btrfs]
    [ 8948.290298] Call Trace:
    [ 8948.290517]  <TASK>
    [ 8948.290700]  dump_stack_lvl+0x59/0x73
    [ 8948.291026]  check_noncircular+0xf3/0x110
    [ 8948.291375]  ? start_transaction+0x228/0x6e0 [btrfs]
    [ 8948.291826]  __lock_acquire+0x12e8/0x2260
    [ 8948.292241]  lock_acquire+0xd7/0x310
    [ 8948.292714]  ? find_free_extent+0x141e/0x1590 [btrfs]
    [ 8948.293241]  ? lock_is_held_type+0xea/0x140
    [ 8948.293601]  start_transaction+0x44c/0x6e0 [btrfs]
    [ 8948.294055]  ? find_free_extent+0x141e/0x1590 [btrfs]
    [ 8948.294518]  find_free_extent+0x141e/0x1590 [btrfs]
    [ 8948.294957]  ? _raw_spin_unlock+0x29/0x40
    [ 8948.295312]  ? btrfs_get_alloc_profile+0x124/0x290 [btrfs]
    [ 8948.295813]  btrfs_reserve_extent+0x14b/0x280 [btrfs]
    [ 8948.296270]  cow_file_range+0x17e/0x490 [btrfs]
    [ 8948.296691]  btrfs_run_delalloc_range+0x345/0x7a0 [btrfs]
    [ 8948.297175]  ? find_lock_delalloc_range+0x247/0x270 [btrfs]
    [ 8948.297678]  writepage_delalloc+0xb5/0x170 [btrfs]
    [ 8948.298123]  __extent_writepage+0x156/0x3c0 [btrfs]
    [ 8948.298570]  extent_write_cache_pages+0x263/0x460 [btrfs]
    [ 8948.299061]  extent_writepages+0x76/0x130 [btrfs]
    [ 8948.299495]  do_writepages+0xd2/0x1c0
    [ 8948.299817]  ? sched_clock_cpu+0xd/0x110
    [ 8948.300160]  ? lock_release+0x155/0x4a0
    [ 8948.300494]  filemap_fdatawrite_wbc+0x68/0x90
    [ 8948.300874]  ? do_raw_spin_unlock+0x4b/0xa0
    [ 8948.301243]  start_delalloc_inodes+0x17f/0x400 [btrfs]
    [ 8948.301706]  ? lock_release+0x155/0x4a0
    [ 8948.302055]  btrfs_start_delalloc_roots+0x194/0x2a0 [btrfs]
    [ 8948.302564]  flush_space+0x1f2/0x630 [btrfs]
    [ 8948.302970]  btrfs_async_reclaim_data_space+0x108/0x1b0 [btrfs]
    [ 8948.303510]  process_one_work+0x252/0x5a0
    [ 8948.303860]  ? process_one_work+0x5a0/0x5a0
    [ 8948.304221]  worker_thread+0x55/0x3b0
    [ 8948.304543]  ? process_one_work+0x5a0/0x5a0
    [ 8948.304904]  kthread+0xf2/0x120
    [ 8948.305184]  ? kthread_complete_and_exit+0x20/0x20
    [ 8948.305598]  ret_from_fork+0x22/0x30
    [ 8948.305921]  </TASK>
    
    It all comes from the fact that btrfs_start_delalloc_roots() takes the
    delalloc_root_mutex, in the transaction commit path we are holding a
    read lock on one of the superblock's freeze semaphores (via
    sb_start_intwrite()), the async reclaim task can also do a call to
    btrfs_start_delalloc_roots(), which ends up triggering writeback with
    calls to filemap_fdatawrite_wbc(), resulting in extent allocation which
    in turn can call btrfs_start_transaction(), which will result in taking
    the freeze semaphore via sb_start_intwrite(), forming a nasty dependency
    on all those locks which can be taken in different orders by different
    code paths.
    
    So just adopt the simple approach of calling try_to_writeback_inodes_sb()
    at btrfs_start_delalloc_flush().
    
    Link: https://lore.kernel.org/linux-btrfs/20220130005258.GA7465@cuci.nl/
    Link: https://lore.kernel.org/linux-btrfs/43acc426-d683-d1b6-729d-c6bc4a2fff4d@gmail.com/
    Link: https://lore.kernel.org/linux-btrfs/6833930a-08d7-6fbc-0141-eb9cdfd6bb4d@gmail.com/
    Link: https://lore.kernel.org/linux-btrfs/20190322041731.GF16651@hungrycats.org/
    Reviewed-by: Omar Sandoval <osandov@fb.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    [ add more link reports ]
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0d1ffa2228cb34f485f8fe927f134b82a0ea62ae
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Feb 8 14:54:05 2022 +0800

    btrfs: defrag: don't try to defrag extents which are under writeback
    
    Once we start writeback (have called btrfs_run_delalloc_range()), we
    allocate an extent, create an extent map point to that extent, with a
    generation of (u64)-1, created the ordered extent and then clear the
    DELALLOC bit from the range in the inode's io tree.
    
    Such extent map can pass the first call of defrag_collect_targets(), as
    its generation is (u64)-1, meets any possible minimal generation check.
    And the range will not have DELALLOC bit, also passing the DELALLOC bit
    check.
    
    It will only be re-checked in the second call of
    defrag_collect_targets(), which will wait for writeback.
    
    But at that stage we have already spent our time waiting for some IO we
    may or may not want to defrag.
    
    Let's reject such extents early so we won't waste our time.
    
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit ea0eba69a2a8125229b1b6011644598039bc53aa
Author: Qu Wenruo <wqu@suse.com>
Date:   Sun Jan 30 20:53:15 2022 +0800

    btrfs: don't hold CPU for too long when defragging a file
    
    There is a user report about "btrfs filesystem defrag" causing 120s
    timeout problem.
    
    For btrfs_defrag_file() it will iterate all file extents if called from
    defrag ioctl, thus it can take a long time.
    
    There is no reason not to release the CPU during such a long operation.
    
    Add cond_resched() after defragged one cluster.
    
    CC: stable@vger.kernel.org # 5.16
    Link: https://lore.kernel.org/linux-btrfs/10e51417-2203-f0a4-2021-86c8511cc367@gmx.com
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit b42bc9a3c5115c3102a4923776bbeed3b191f2db
Author: Domenico Andreoli <domenico.andreoli@linux.com>
Date:   Wed Feb 9 08:49:20 2022 +0100

    Fix regression due to "fs: move binfmt_misc sysctl to its own file"
    
    Commit 3ba442d5331f ("fs: move binfmt_misc sysctl to its own file") did
    not go unnoticed, binfmt-support stopped to work on my Debian system
    since v5.17-rc2 (did not check with -rc1).
    
    The existance of the /proc/sys/fs/binfmt_misc is a precondition for
    attempting to mount the binfmt_misc fs, which in turn triggers the
    autoload of the binfmt_misc module.  Without it, no module is loaded and
    no binfmt is available at boot.
    
    Building as built-in or manually loading the module and mounting the fs
    works fine, it's therefore only a matter of interaction with user-space.
    I could try to improve the Debian systemd configuration but I can't say
    anything about the other distributions.
    
    This patch restores a working system right after boot.
    
    Fixes: 3ba442d5331f ("fs: move binfmt_misc sysctl to its own file")
    Signed-off-by: Domenico Andreoli <domenico.andreoli@linux.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Tong Zhang <ztong0001@gmail.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 09a93c1df3eafa43bcdfd7bf837c574911f12f55
Merge: e6251ab4551f5 2c212e1baedcd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 9 09:14:22 2022 -0800

    Merge tag 'kvm-s390-kernel-access' from emailed bundle
    
    Pull s390 kvm fix from Christian Borntraeger:
     "Add missing check for the MEMOP ioctl
    
      The SIDA MEMOPs must only be used for secure guests, otherwise
      userspace can do unwanted memory accesses"
    
    * tag 'kvm-s390-kernel-access' from emailed bundle:
      KVM: s390: Return error on SIDA memop on normal guest

commit 647474b8d980256b26b1cd112d7333a4dbd4260a
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Date:   Mon Jan 31 09:55:20 2022 +0100

    drm/mediatek: mtk_dsi: Avoid EPROBE_DEFER loop with external bridge
    
    DRM bridge drivers are now attaching their DSI device at probe time,
    which requires us to register our DSI host in order to let the bridge
    to probe: this recently started producing an endless -EPROBE_DEFER
    loop on some machines that are using external bridges, like the
    parade-ps8640, found on the ACER Chromebook R13.
    
    Now that the DSI hosts/devices probe sequence is documented, we can
    do adjustments to the mtk_dsi driver as to both fix now and make sure
    to avoid this situation in the future: for this, following what is
    documented in drm_bridge.c, move the mtk_dsi component_add() to the
    mtk_dsi_ops.attach callback and delete it in the detach callback;
    keeping in mind that we are registering a drm_bridge for our DSI,
    which is only used/attached if the DSI Host is bound, it wouldn't
    make sense to keep adding our bridge at probe time (as it would
    be useless to have it if mtk_dsi_ops.attach() fails!), so also move
    that one to the dsi host attach function (and remove it in detach).
    
    Cc: <stable@vger.kernel.org> # 5.15.x
    Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
    Reviewed-by: Jagan Teki <jagan@amarulasolutions.com>
    Tested-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Signed-off-by: Chun-Kuang Hu <chunkuang.hu@kernel.org>

commit e4e3a93c6e267572ca2345d8d86053e166843a8c
Author: Tzung-Bi Shih <tzungbi@google.com>
Date:   Tue Feb 8 11:12:42 2022 +0800

    MAINTAINERS: update cros_ec_codec maintainers
    
    Updates cros_ec_codec maintainers.
    
    Signed-off-by: Tzung-Bi Shih <tzungbi@google.com>
    Acked-By: Cheng-Yi Chiang <cychiang@chromium.org>
    Acked-By: Benson Leung <bleung@chromium.org>
    Link: https://lore.kernel.org/r/20220208031242.227563-1-tzungbi@google.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit ffc58bc4af9365d4eea72526bb3cf6a83615c673
Author: Cai Huoqing <cai.huoqing@linux.dev>
Date:   Wed Feb 9 11:22:51 2022 +0800

    Drivers: hv: utils: Make use of the helper macro LIST_HEAD()
    
    Replace "struct list_head head = LIST_HEAD_INIT(head)" with
    "LIST_HEAD(head)" to simplify the code.
    
    Signed-off-by: Cai Huoqing <cai.huoqing@linux.dev>
    Link: https://lore.kernel.org/r/20220209032251.37362-1-cai.huoqing@linux.dev
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit c306d737691ef84305d4ed0d302c63db2932f0bb
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Jan 25 15:57:45 2022 -0500

    NFSD: Deprecate NFS_OFFSET_MAX
    
    NFS_OFFSET_MAX was introduced way back in Linux v2.3.y before there
    was a kernel-wide OFFSET_MAX value. As a clean up, replace the last
    few uses of it with its generic equivalent, and get rid of it.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 6a4d333d540041d244b2fca29b8417bfde20af81
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Fri Feb 4 17:05:24 2022 -0500

    NFSD: Fix offset type in I/O trace points
    
    NFSv3 and NFSv4 use u64 offset values on the wire. Record these values
    verbatim without the implicit type case to loff_t.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 3f965021c8bc38965ecb1924f570c4842b33d408
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Jan 24 15:50:31 2022 -0500

    NFSD: COMMIT operations must not return NFS?ERR_INVAL
    
    Since, well, forever, the Linux NFS server's nfsd_commit() function
    has returned nfserr_inval when the passed-in byte range arguments
    were non-sensical.
    
    However, according to RFC 1813 section 3.3.21, NFSv3 COMMIT requests
    are permitted to return only the following non-zero status codes:
    
          NFS3ERR_IO
          NFS3ERR_STALE
          NFS3ERR_BADHANDLE
          NFS3ERR_SERVERFAULT
    
    NFS3ERR_INVAL is not included in that list. Likewise, NFS4ERR_INVAL
    is not listed in the COMMIT row of Table 6 in RFC 8881.
    
    RFC 7530 does permit COMMIT to return NFS4ERR_INVAL, but does not
    specify when it can or should be used.
    
    Instead of dropping or failing a COMMIT request in a byte range that
    is not supported, turn it into a valid request by treating one or
    both arguments as zero. Offset zero means start-of-file, count zero
    means until-end-of-file, so we only ever extend the commit range.
    NFS servers are always allowed to commit more and sooner than
    requested.
    
    The range check is no longer bounded by NFS_OFFSET_MAX, but rather
    by the value that is returned in the maxfilesize field of the NFSv3
    FSINFO procedure or the NFSv4 maxfilesize file attribute.
    
    Note that this change results in a new pynfs failure:
    
    CMT4     st_commit.testCommitOverflow                             : RUNNING
    CMT4     st_commit.testCommitOverflow                             : FAILURE
               COMMIT with offset + count overflow should return
               NFS4ERR_INVAL, instead got NFS4_OK
    
    IMO the test is not correct as written: RFC 8881 does not allow the
    COMMIT operation to return NFS4ERR_INVAL.
    
    Reported-by: Dan Aloni <dan.aloni@vastdata.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Reviewed-by: Bruce Fields <bfields@fieldses.org>

commit 6260d9a56ab352b54891ec66ab0eced57d55abc6
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Jan 25 16:36:22 2022 -0500

    NFSD: Clamp WRITE offsets
    
    Ensure that a client cannot specify a WRITE range that falls in a
    byte range outside what the kernel's internal types (such as loff_t,
    which is signed) can represent. The kiocb iterators, invoked in
    nfsd_vfs_write(), should properly limit write operations to within
    the underlying file system's s_maxbytes.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit a648fdeb7c0e17177a2280344d015dba3fbe3314
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Jan 25 15:59:57 2022 -0500

    NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
    
    iattr::ia_size is a loff_t, so these NFSv3 procedures must be
    careful to deal with incoming client size values that are larger
    than s64_max without corrupting the value.
    
    Silently capping the value results in storing a different value
    than the client passed in which is unexpected behavior, so remove
    the min_t() check in decode_sattr3().
    
    Note that RFC 1813 permits only the WRITE procedure to return
    NFS3ERR_FBIG. We believe that NFSv3 reference implementations
    also return NFS3ERR_FBIG when ia_size is too large.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit e6faac3f58c7c4176b66f63def17a34232a17b0e
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Jan 31 13:01:53 2022 -0500

    NFSD: Fix ia_size underflow
    
    iattr::ia_size is a loff_t, which is a signed 64-bit type. NFSv3 and
    NFSv4 both define file size as an unsigned 64-bit type. Thus there
    is a range of valid file size values an NFS client can send that is
    already larger than Linux can handle.
    
    Currently decode_fattr4() dumps a full u64 value into ia_size. If
    that value happens to be larger than S64_MAX, then ia_size
    underflows. I'm about to fix up the NFSv3 behavior as well, so let's
    catch the underflow in the common code path: nfsd_setattr().
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 0cb4d23ae08c48f6bf3c29a8e5c4a74b8388b960
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Fri Feb 4 15:19:34 2022 -0500

    NFSD: Fix the behavior of READ near OFFSET_MAX
    
    Dan Aloni reports:
    > Due to commit 8cfb9015280d ("NFS: Always provide aligned buffers to
    > the RPC read layers") on the client, a read of 0xfff is aligned up
    > to server rsize of 0x1000.
    >
    > As a result, in a test where the server has a file of size
    > 0x7fffffffffffffff, and the client tries to read from the offset
    > 0x7ffffffffffff000, the read causes loff_t overflow in the server
    > and it returns an NFS code of EINVAL to the client. The client as
    > a result indefinitely retries the request.
    
    The Linux NFS client does not handle NFS?ERR_INVAL, even though all
    NFS specifications permit servers to return that status code for a
    READ.
    
    Instead of NFS?ERR_INVAL, have out-of-range READ requests succeed
    and return a short result. Set the EOF flag in the result to prevent
    the client from retrying the READ request. This behavior appears to
    be consistent with Solaris NFS servers.
    
    Note that NFSv3 and NFSv4 use u64 offset values on the wire. These
    must be converted to loff_t internally before use -- an implicit
    type cast is not adequate for this purpose. Otherwise VFS checks
    against sb->s_maxbytes do not work properly.
    
    Reported-by: Dan Aloni <dan.aloni@vastdata.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 63573807b27e0faf8065a28b1bbe1cbfb23c0130
Author: Sagi Grimberg <sagi@grimberg.me>
Date:   Mon Feb 7 00:40:13 2022 +0200

    nvme-tcp: fix bogus request completion when failing to send AER
    
    AER is not backed by a real request, hence we should not incorrectly
    assume that when failing to send a nvme command, it is a normal request
    but rather check if this is an aer and if so complete the aer (similar
    to the normal completion path).
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 00e757b648c0935d703a9b8042312f4a76ee793b
Author: Bean Huo <beanhuo@micron.com>
Date:   Tue Feb 8 00:28:06 2022 +0100

    nvme: add nvme_complete_req tracepoint for batched completion
    
    Add NVMe request completion trace in nvme_complete_batch_req() because
    nvme:nvme_complete_req tracepoint is missing in case of request batched
    completion.
    
    Signed-off-by: Bean Huo <beanhuo@micron.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 3bed06e36994661a75bae6a289926e566b9b3c1a
Merge: feef318c855a3 d6ff94afd90b0
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Feb 9 13:33:39 2022 +0000

    Merge branch 'vlan-QinQ-leak-fix'
    
    Xin Long says:
    
    ====================
    vlan: fix a netdev refcnt leak for QinQ
    
    This issue can be simply reproduced by:
    
      # ip link add dummy0 type dummy
      # ip link add link dummy0 name dummy0.1 type vlan id 1
      # ip link add link dummy0.1 name dummy0.1.2 type vlan id 2
      # rmmod 8021q
    
     unregister_netdevice: waiting for dummy0.1 to become free. Usage count = 1
    
    So as to fix it, adjust vlan_dev_uninit() in Patch 1/1 so that it won't
    be called twice for the same device, then do the fix in vlan_dev_uninit()
    in Patch 2/2.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d6ff94afd90b0ce8d1715f8ef77d4347d7a7f2c0
Author: Xin Long <lucien.xin@gmail.com>
Date:   Wed Feb 9 03:19:56 2022 -0500

    vlan: move dev_put into vlan_dev_uninit
    
    Shuang Li reported an QinQ issue by simply doing:
    
      # ip link add dummy0 type dummy
      # ip link add link dummy0 name dummy0.1 type vlan id 1
      # ip link add link dummy0.1 name dummy0.1.2 type vlan id 2
      # rmmod 8021q
    
     unregister_netdevice: waiting for dummy0.1 to become free. Usage count = 1
    
    When rmmods 8021q, all vlan devs are deleted from their real_dev's vlan grp
    and added into list_kill by unregister_vlan_dev(). dummy0.1 is unregistered
    before dummy0.1.2, as it's using for_each_netdev() in __rtnl_kill_links().
    
    When unregisters dummy0.1, dummy0.1.2 is not unregistered in the event of
    NETDEV_UNREGISTER, as it's been deleted from dummy0.1's vlan grp. However,
    due to dummy0.1.2 still holding dummy0.1, dummy0.1 will keep waiting in
    netdev_wait_allrefs(), while dummy0.1.2 will never get unregistered and
    release dummy0.1, as it delays dev_put until calling dev->priv_destructor,
    vlan_dev_free().
    
    This issue was introduced by Commit 563bcbae3ba2 ("net: vlan: fix a UAF in
    vlan_dev_real_dev()"), and this patch is to fix it by moving dev_put() into
    vlan_dev_uninit(), which is called after NETDEV_UNREGISTER event but before
    netdev_wait_allrefs().
    
    Fixes: 563bcbae3ba2 ("net: vlan: fix a UAF in vlan_dev_real_dev()")
    Reported-by: Shuang Li <shuali@redhat.com>
    Signed-off-by: Xin Long <lucien.xin@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 37aa50c539bcbcc01767e515bd170787fcfc0f33
Author: Xin Long <lucien.xin@gmail.com>
Date:   Wed Feb 9 03:19:55 2022 -0500

    vlan: introduce vlan_dev_free_egress_priority
    
    This patch is to introduce vlan_dev_free_egress_priority() to
    free egress priority for vlan dev, and keep vlan_dev_uninit()
    static as .ndo_uninit. It makes the code more clear and safer
    when adding new code in vlan_dev_uninit() in the future.
    
    Signed-off-by: Xin Long <lucien.xin@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit feef318c855a361a1eccd880f33e88c460eb63b4
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Wed Feb 9 20:53:45 2022 +0800

    ax25: fix UAF bugs of net_device caused by rebinding operation
    
    The ax25_kill_by_device() will set s->ax25_dev = NULL and
    call ax25_disconnect() to change states of ax25_cb and
    sock, if we call ax25_bind() before ax25_kill_by_device().
    
    However, if we call ax25_bind() again between the window of
    ax25_kill_by_device() and ax25_dev_device_down(), the values
    and states changed by ax25_kill_by_device() will be reassigned.
    
    Finally, ax25_dev_device_down() will deallocate net_device.
    If we dereference net_device in syscall functions such as
    ax25_release(), ax25_sendmsg(), ax25_getsockopt(), ax25_getname()
    and ax25_info_show(), a UAF bug will occur.
    
    One of the possible race conditions is shown below:
    
          (USE)                   |      (FREE)
    ax25_bind()                   |
                                  |  ax25_kill_by_device()
    ax25_bind()                   |
    ax25_connect()                |    ...
                                  |  ax25_dev_device_down()
                                  |    ...
                                  |    dev_put_track(dev, ...) //FREE
    ax25_release()                |    ...
      ax25_send_control()         |
        alloc_skb()      //USE    |
    
    the corresponding fail log is shown below:
    ===============================================================
    BUG: KASAN: use-after-free in ax25_send_control+0x43/0x210
    ...
    Call Trace:
      ...
      ax25_send_control+0x43/0x210
      ax25_release+0x2db/0x3b0
      __sock_release+0x6d/0x120
      sock_close+0xf/0x20
      __fput+0x11f/0x420
      ...
    Allocated by task 1283:
      ...
      __kasan_kmalloc+0x81/0xa0
      alloc_netdev_mqs+0x5a/0x680
      mkiss_open+0x6c/0x380
      tty_ldisc_open+0x55/0x90
      ...
    Freed by task 1969:
      ...
      kfree+0xa3/0x2c0
      device_release+0x54/0xe0
      kobject_put+0xa5/0x120
      tty_ldisc_kill+0x3e/0x80
      ...
    
    In order to fix these UAF bugs caused by rebinding operation,
    this patch adds dev_hold_track() into ax25_bind() and
    corresponding dev_put_track() into ax25_kill_by_device().
    
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ee534378f00561207656663d93907583958339ae
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Wed Feb 9 14:04:33 2022 +0200

    net: dsa: fix panic when DSA master device unbinds on shutdown
    
    Rafael reports that on a system with LX2160A and Marvell DSA switches,
    if a reboot occurs while the DSA master (dpaa2-eth) is up, the following
    panic can be seen:
    
    systemd-shutdown[1]: Rebooting.
    Unable to handle kernel paging request at virtual address 00a0000800000041
    [00a0000800000041] address between user and kernel address ranges
    Internal error: Oops: 96000004 [#1] PREEMPT SMP
    CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32
    pc : dsa_slave_netdevice_event+0x130/0x3e4
    lr : raw_notifier_call_chain+0x50/0x6c
    Call trace:
     dsa_slave_netdevice_event+0x130/0x3e4
     raw_notifier_call_chain+0x50/0x6c
     call_netdevice_notifiers_info+0x54/0xa0
     __dev_close_many+0x50/0x130
     dev_close_many+0x84/0x120
     unregister_netdevice_many+0x130/0x710
     unregister_netdevice_queue+0x8c/0xd0
     unregister_netdev+0x20/0x30
     dpaa2_eth_remove+0x68/0x190
     fsl_mc_driver_remove+0x20/0x5c
     __device_release_driver+0x21c/0x220
     device_release_driver_internal+0xac/0xb0
     device_links_unbind_consumers+0xd4/0x100
     __device_release_driver+0x94/0x220
     device_release_driver+0x28/0x40
     bus_remove_device+0x118/0x124
     device_del+0x174/0x420
     fsl_mc_device_remove+0x24/0x40
     __fsl_mc_device_remove+0xc/0x20
     device_for_each_child+0x58/0xa0
     dprc_remove+0x90/0xb0
     fsl_mc_driver_remove+0x20/0x5c
     __device_release_driver+0x21c/0x220
     device_release_driver+0x28/0x40
     bus_remove_device+0x118/0x124
     device_del+0x174/0x420
     fsl_mc_bus_remove+0x80/0x100
     fsl_mc_bus_shutdown+0xc/0x1c
     platform_shutdown+0x20/0x30
     device_shutdown+0x154/0x330
     __do_sys_reboot+0x1cc/0x250
     __arm64_sys_reboot+0x20/0x30
     invoke_syscall.constprop.0+0x4c/0xe0
     do_el0_svc+0x4c/0x150
     el0_svc+0x24/0xb0
     el0t_64_sync_handler+0xa8/0xb0
     el0t_64_sync+0x178/0x17c
    
    It can be seen from the stack trace that the problem is that the
    deregistration of the master causes a dev_close(), which gets notified
    as NETDEV_GOING_DOWN to dsa_slave_netdevice_event().
    But dsa_switch_shutdown() has already run, and this has unregistered the
    DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to
    call dev_close_many() on those slave interfaces, leading to the problem.
    
    The previous attempt to avoid the NETDEV_GOING_DOWN on the master after
    dsa_switch_shutdown() was called seems improper. Unregistering the slave
    interfaces is unnecessary and unhelpful. Instead, after the slaves have
    stopped being uppers of the DSA master, we can now reset to NULL the
    master->dsa_ptr pointer, which will make DSA start ignoring all future
    notifier events on the master.
    
    Fixes: 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown")
    Reported-by: Rafael Richter <rafael.richter@gin.de>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d9565bf40da22426d2f660cb31700b6858d1911d
Author: H. Nikolaus Schaller <hns@goldelico.com>
Date:   Wed Feb 2 17:31:22 2022 +0100

    MIPS: DTS: CI20: fix how ddc power is enabled
    
    Originally we proposed a new hdmi-5v-supply regulator reference
    for CI20 device tree but that was superseded by a better idea to use
    the already defined "ddc-en-gpios" property of the "hdmi-connector".
    
    Since "MIPS: DTS: CI20: Add DT nodes for HDMI setup" has already
    been applied to v5.17-rc1, we add this on top.
    
    Fixes: ae1b8d2c2de9 ("MIPS: DTS: CI20: Add DT nodes for HDMI setup")
    Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
    Reviewed-by: Paul Cercueil <paul@crapouillou.net>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 68c2d6af1f1e469544d6cbe9a601d96fb9c00e7f
Author: Raju Rangoju <Raju.Rangoju@amd.com>
Date:   Wed Feb 9 10:02:01 2022 +0530

    net: amd-xgbe: disable interrupts during pci removal
    
    Hardware interrupts are enabled during the pci probe, however,
    they are not disabled during pci removal.
    
    Disable all hardware interrupts during pci removal to avoid any
    issues.
    
    Fixes: e75377404726 ("amd-xgbe: Update PCI support to use new IRQ functions")
    Suggested-by: Selwin Sebastian <Selwin.Sebastian@amd.com>
    Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c7223d687758462826a20e9735305d55bb874c70
Author: Jon Maloy <jmaloy@redhat.com>
Date:   Tue Feb 8 22:22:37 2022 -0500

    tipc: rate limit warning for received illegal binding update
    
    It would be easy to craft a message containing an illegal binding table
    update operation. This is handled correctly by the code, but the
    corresponding warning printout is not rate limited as is should be.
    We fix this now.
    
    Fixes: b97bf3fd8f6a ("[TIPC] Initial merge")
    Signed-off-by: Jon Maloy <jmaloy@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit bc1c3c3b10db4f37c41e6107751a8d450d9c431c
Author: Joel Stanley <joel@jms.id.au>
Date:   Wed Feb 9 10:33:59 2022 +1030

    net: mdio: aspeed: Add missing MODULE_DEVICE_TABLE
    
    Fix loading of the driver when built as a module.
    
    Fixes: f160e99462c6 ("net: phy: Add mdio-aspeed")
    Signed-off-by: Joel Stanley <joel@jms.id.au>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Acked-by: Andrew Jeffery <andrew@aj.id.au>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 68468d8c4cd4222a4ca1f185ab5a1c14480d078c
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Feb 8 15:28:22 2022 -0800

    veth: fix races around rq->rx_notify_masked
    
    veth being NETIF_F_LLTX enabled, we need to be more careful
    whenever we read/write rq->rx_notify_masked.
    
    BUG: KCSAN: data-race in veth_xmit / veth_xmit
    
    write to 0xffff888133d9a9f8 of 1 bytes by task 23552 on cpu 0:
     __veth_xdp_flush drivers/net/veth.c:269 [inline]
     veth_xmit+0x307/0x470 drivers/net/veth.c:350
     __netdev_start_xmit include/linux/netdevice.h:4683 [inline]
     netdev_start_xmit include/linux/netdevice.h:4697 [inline]
     xmit_one+0x105/0x2f0 net/core/dev.c:3473
     dev_hard_start_xmit net/core/dev.c:3489 [inline]
     __dev_queue_xmit+0x86d/0xf90 net/core/dev.c:4116
     dev_queue_xmit+0x13/0x20 net/core/dev.c:4149
     br_dev_queue_push_xmit+0x3ce/0x430 net/bridge/br_forward.c:53
     NF_HOOK include/linux/netfilter.h:307 [inline]
     br_forward_finish net/bridge/br_forward.c:66 [inline]
     NF_HOOK include/linux/netfilter.h:307 [inline]
     __br_forward+0x2e4/0x400 net/bridge/br_forward.c:115
     br_flood+0x521/0x5c0 net/bridge/br_forward.c:242
     br_dev_xmit+0x8b6/0x960
     __netdev_start_xmit include/linux/netdevice.h:4683 [inline]
     netdev_start_xmit include/linux/netdevice.h:4697 [inline]
     xmit_one+0x105/0x2f0 net/core/dev.c:3473
     dev_hard_start_xmit net/core/dev.c:3489 [inline]
     __dev_queue_xmit+0x86d/0xf90 net/core/dev.c:4116
     dev_queue_xmit+0x13/0x20 net/core/dev.c:4149
     neigh_hh_output include/net/neighbour.h:525 [inline]
     neigh_output include/net/neighbour.h:539 [inline]
     ip_finish_output2+0x6f8/0xb70 net/ipv4/ip_output.c:228
     ip_finish_output+0xfb/0x240 net/ipv4/ip_output.c:316
     NF_HOOK_COND include/linux/netfilter.h:296 [inline]
     ip_output+0xf3/0x1a0 net/ipv4/ip_output.c:430
     dst_output include/net/dst.h:451 [inline]
     ip_local_out net/ipv4/ip_output.c:126 [inline]
     ip_send_skb+0x6e/0xe0 net/ipv4/ip_output.c:1570
     udp_send_skb+0x641/0x880 net/ipv4/udp.c:967
     udp_sendmsg+0x12ea/0x14c0 net/ipv4/udp.c:1254
     inet_sendmsg+0x5f/0x80 net/ipv4/af_inet.c:819
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffff888133d9a9f8 of 1 bytes by task 23563 on cpu 1:
     __veth_xdp_flush drivers/net/veth.c:268 [inline]
     veth_xmit+0x2d6/0x470 drivers/net/veth.c:350
     __netdev_start_xmit include/linux/netdevice.h:4683 [inline]
     netdev_start_xmit include/linux/netdevice.h:4697 [inline]
     xmit_one+0x105/0x2f0 net/core/dev.c:3473
     dev_hard_start_xmit net/core/dev.c:3489 [inline]
     __dev_queue_xmit+0x86d/0xf90 net/core/dev.c:4116
     dev_queue_xmit+0x13/0x20 net/core/dev.c:4149
     br_dev_queue_push_xmit+0x3ce/0x430 net/bridge/br_forward.c:53
     NF_HOOK include/linux/netfilter.h:307 [inline]
     br_forward_finish net/bridge/br_forward.c:66 [inline]
     NF_HOOK include/linux/netfilter.h:307 [inline]
     __br_forward+0x2e4/0x400 net/bridge/br_forward.c:115
     br_flood+0x521/0x5c0 net/bridge/br_forward.c:242
     br_dev_xmit+0x8b6/0x960
     __netdev_start_xmit include/linux/netdevice.h:4683 [inline]
     netdev_start_xmit include/linux/netdevice.h:4697 [inline]
     xmit_one+0x105/0x2f0 net/core/dev.c:3473
     dev_hard_start_xmit net/core/dev.c:3489 [inline]
     __dev_queue_xmit+0x86d/0xf90 net/core/dev.c:4116
     dev_queue_xmit+0x13/0x20 net/core/dev.c:4149
     neigh_hh_output include/net/neighbour.h:525 [inline]
     neigh_output include/net/neighbour.h:539 [inline]
     ip_finish_output2+0x6f8/0xb70 net/ipv4/ip_output.c:228
     ip_finish_output+0xfb/0x240 net/ipv4/ip_output.c:316
     NF_HOOK_COND include/linux/netfilter.h:296 [inline]
     ip_output+0xf3/0x1a0 net/ipv4/ip_output.c:430
     dst_output include/net/dst.h:451 [inline]
     ip_local_out net/ipv4/ip_output.c:126 [inline]
     ip_send_skb+0x6e/0xe0 net/ipv4/ip_output.c:1570
     udp_send_skb+0x641/0x880 net/ipv4/udp.c:967
     udp_sendmsg+0x12ea/0x14c0 net/ipv4/udp.c:1254
     inet_sendmsg+0x5f/0x80 net/ipv4/af_inet.c:819
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2413
     ___sys_sendmsg net/socket.c:2467 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x00 -> 0x01
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 23563 Comm: syz-executor.5 Not tainted 5.17.0-rc2-syzkaller-00064-gc36c04c2e132 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 948d4f214fde ("veth: Add driver XDP")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6d072066aba72243253a29acb2a58244355ece40
Merge: 7ec02f5ac8a5b 8375dfac4f683
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Feb 9 12:02:28 2022 +0000

    Merge tag 'linux-can-fixes-for-5.17-20220209' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can
    
    Marc Kleine-Budde says:
    
    ====================
    pull-request: can 2022-02-09
    
    this is a pull request of 2 patches for net/master.
    
    Oliver Hartkopp contributes 2 fixes for the CAN ISOTP protocol.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 7ec02f5ac8a5be5a3f20611731243dc5e1d9ba10
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Tue Feb 8 23:40:00 2022 +0800

    ax25: fix NPD bug in ax25_disconnect
    
    The ax25_disconnect() in ax25_kill_by_device() is not
    protected by any locks, thus there is a race condition
    between ax25_disconnect() and ax25_destroy_socket().
    when ax25->sk is assigned as NULL by ax25_destroy_socket(),
    a NULL pointer dereference bug will occur if site (1) or (2)
    dereferences ax25->sk.
    
    ax25_kill_by_device()                | ax25_release()
      ax25_disconnect()                  |   ax25_destroy_socket()
        ...                              |
        if(ax25->sk != NULL)             |     ...
          ...                            |     ax25->sk = NULL;
          bh_lock_sock(ax25->sk); //(1)  |     ...
          ...                            |
          bh_unlock_sock(ax25->sk); //(2)|
    
    This patch moves ax25_disconnect() into lock_sock(), which can
    synchronize with ax25_destroy_socket() in ax25_release().
    
    Fail log:
    ===============================================================
    BUG: kernel NULL pointer dereference, address: 0000000000000088
    ...
    RIP: 0010:_raw_spin_lock+0x7e/0xd0
    ...
    Call Trace:
    ax25_disconnect+0xf6/0x220
    ax25_device_event+0x187/0x250
    raw_notifier_call_chain+0x5e/0x70
    dev_close_many+0x17d/0x230
    rollback_registered_many+0x1f1/0x950
    unregister_netdevice_queue+0x133/0x200
    unregister_netdev+0x13/0x20
    ...
    
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 676b49366a70ea91997585ba8e4577290f5172a5
Merge: 7db788ad627aa 9eeabdf17fa0a
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Feb 9 11:41:48 2022 +0000

    Merge branch 'net-fix-skb-unclone-issues'
    
    Antoine Tenart says:
    
    ====================
    net: fix issues when uncloning an skb dst+metadata
    
    This fixes two issues when uncloning an skb dst+metadata in
    tun_dst_unclone; this was initially reported by Vlad Buslov[1]. Because
    of the memory leak fixed by patch 2, the issue in patch 1 never happened
    in practice.
    
    tun_dst_unclone is called from two different places, one in geneve/vxlan
    to handle PMTU and one in net/openvswitch/actions.c where it is used to
    retrieve tunnel information. While both Vlad and I tested the former, we
    could not for the latter. I did spend quite some time trying to, but
    that code path is not easy to trigger. Code inspection shows this should
    be fine, the tunnel information (dst+metadata) is uncloned and the skb
    it is referenced from is only consumed after all accesses to the tunnel
    information are done:
    
      do_execute_actions
        output_userspace
          dev_fill_metadata_dst         <- dst+metadata is uncloned
          ovs_dp_upcall
            queue_userspace_packet
              ovs_nla_put_tunnel_info   <- metadata (tunnel info) is accessed
        consume_skb                     <- dst+metadata is freed
    
    Thanks!
    Antoine
    
    [1] https://lore.kernel.org/all/ygnhh79yluw2.fsf@nvidia.com/T/#m2f814614a4f5424cea66bbff7297f692b59b69a0
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9eeabdf17fa0ab75381045c867c370f4cc75a613
Author: Antoine Tenart <atenart@kernel.org>
Date:   Mon Feb 7 18:13:19 2022 +0100

    net: fix a memleak when uncloning an skb dst and its metadata
    
    When uncloning an skb dst and its associated metadata, a new
    dst+metadata is allocated and later replaces the old one in the skb.
    This is helpful to have a non-shared dst+metadata attached to a specific
    skb.
    
    The issue is the uncloned dst+metadata is initialized with a refcount of
    1, which is increased to 2 before attaching it to the skb. When
    tun_dst_unclone returns, the dst+metadata is only referenced from a
    single place (the skb) while its refcount is 2. Its refcount will never
    drop to 0 (when the skb is consumed), leading to a memory leak.
    
    Fix this by removing the call to dst_hold in tun_dst_unclone, as the
    dst+metadata refcount is already 1.
    
    Fixes: fc4099f17240 ("openvswitch: Fix egress tunnel info.")
    Cc: Pravin B Shelar <pshelar@ovn.org>
    Reported-by: Vlad Buslov <vladbu@nvidia.com>
    Tested-by: Vlad Buslov <vladbu@nvidia.com>
    Signed-off-by: Antoine Tenart <atenart@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit cfc56f85e72f5b9c5c5be26dc2b16518d36a7868
Author: Antoine Tenart <atenart@kernel.org>
Date:   Mon Feb 7 18:13:18 2022 +0100

    net: do not keep the dst cache when uncloning an skb dst and its metadata
    
    When uncloning an skb dst and its associated metadata a new dst+metadata
    is allocated and the tunnel information from the old metadata is copied
    over there.
    
    The issue is the tunnel metadata has references to cached dst, which are
    copied along the way. When a dst+metadata refcount drops to 0 the
    metadata is freed including the cached dst entries. As they are also
    referenced in the initial dst+metadata, this ends up in UaFs.
    
    In practice the above did not happen because of another issue, the
    dst+metadata was never freed because its refcount never dropped to 0
    (this will be fixed in a subsequent patch).
    
    Fix this by initializing the dst cache after copying the tunnel
    information from the old metadata to also unshare the dst cache.
    
    Fixes: d71785ffc7e7 ("net: add dst_cache to ovs vxlan lwtunnel")
    Cc: Paolo Abeni <pabeni@redhat.com>
    Reported-by: Vlad Buslov <vladbu@nvidia.com>
    Tested-by: Vlad Buslov <vladbu@nvidia.com>
    Signed-off-by: Antoine Tenart <atenart@kernel.org>
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c162ca0bcbfb39308c4dff4157e27c751af7032a
Author: Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Tue Feb 8 11:37:56 2022 +0100

    gpio: sim: fix hogs with custom chip labels
    
    We always assign the default device name as the chip_label in hog
    structures which makes it impossible to assign hogs to chips. Let's
    first check if a custom label was set and then copy it instead of the
    default device name.
    
    Fixes: cb8c474e79be ("gpio: sim: new testing module")
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>

commit 26077968f8389a68fdb38af3f2c2289ddc95e8ca
Author: Nicolas Ferre <nicolas.ferre@microchip.com>
Date:   Sun Jan 30 15:39:36 2022 +0100

    dt-bindings: ARM: at91: update maintainers entry
    
    Align the binding documentation with the newly updated MAINTAINERS
    entry.
    
    Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
    Acked-by: Claudiu Beznea <claudiu.beznea@microchip.com>
    Acked-by: Ludovic Desroches <ludovic.desroches@microchip.com>
    Link: https://lore.kernel.org/r/5bf9873eeee3cd49c52a8952a7cd4cb60b61d50a.1643553501.git.nicolas.ferre@microchip.com

commit 6620e311ae76c502b685247b8f7232e81a321a5b
Author: Nicolas Ferre <nicolas.ferre@microchip.com>
Date:   Sun Jan 30 15:39:35 2022 +0100

    MAINTAINERS: replace a Microchip AT91 maintainer
    
    As Ludovic is more focusing on other aspects of the Microchip
    Linux-based development, replace him with Claudiu.
    Entry is added to the CREDITS file.
    
    Thanks Ludovic for these great contributions in the kernel space!
    
    Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
    Acked-by: Claudiu Beznea <claudiu.beznea@microchip.com>
    Acked-by: Ludovic Desroches <ludovic.desroches@microchip.com>
    Link: https://lore.kernel.org/r/23819d8baa635815d0893955197561fe4f044d5e.1643553501.git.nicolas.ferre@microchip.com

commit 2e71ec1a725a794a16e3862791ed43fe5ba6a06b
Author: Hangbin Liu <liuhangbin@gmail.com>
Date:   Wed Feb 9 16:25:51 2022 +0800

    selftests: netfilter: fix exit value for nft_concat_range
    
    When the nft_concat_range test failed, it exit 1 in the code
    specifically.
    
    But when part of, or all of the test passed, it will failed the
    [ ${passed} -eq 0 ] check and thus exit with 1, which is the same
    exit value with failure result. Fix it by exit 0 when passed is not 0.
    
    Fixes: 611973c1e06f ("selftests: netfilter: Introduce tests for sets with range concatenation")
    Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
    Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 75063c9294fb239bbe64eb72141b6871fe526d29
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Feb 8 18:30:43 2022 -0800

    netfilter: xt_socket: fix a typo in socket_mt_destroy()
    
    Calling nf_defrag_ipv4_disable() instead of nf_defrag_ipv6_disable()
    was probably not the intent.
    
    I found this by code inspection, while chasing a possible issue in TPROXY.
    
    Fixes: de8c12110a13 ("netfilter: disable defrag once its no longer needed")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 7152303cbec4f7c2c4db1fb646b549ffd4069b7c
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Feb 4 14:02:33 2022 +0100

    selftests: netfilter: add synproxy test
    
    Simple test for synproxy feature, iperf3 should be intercepted
    by synproxy netns, but connection should still succeed.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 7c76ecd9c99b6e9a771d813ab1aa7fa428b3ade1
Author: Leon Romanovsky <leon@kernel.org>
Date:   Tue Feb 8 16:14:32 2022 +0200

    xfrm: enforce validity of offload input flags
    
    struct xfrm_user_offload has flags variable that received user input,
    but kernel didn't check if valid bits were provided. It caused a situation
    where not sanitized input was forwarded directly to the drivers.
    
    For example, XFRM_OFFLOAD_IPV6 define that was exposed, was used by
    strongswan, but not implemented in the kernel at all.
    
    As a solution, check and sanitize input flags to forward
    XFRM_OFFLOAD_INBOUND to the drivers.
    
    Fixes: d77e38e612a0 ("xfrm: Add an IPsec hardware offloading API")
    Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit ef8ee1cb8fc8976a68f5e89cd5f7b6f7de80c66f
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date:   Thu Jan 27 19:25:54 2022 -0800

    cpufreq: qcom-hw: Delay enabling throttle_irq
    
    In the event that the SoC is under thermal pressure while booting it's
    possible for the dcvs notification to happen inbetween the cpufreq
    framework calling init and it actually updating the policy's
    related_cpus cpumask.
    
    Prior to the introduction of the thermal pressure update helper an empty
    cpumask would simply result in the thermal pressure of no cpus being
    updated, but the new code will attempt to dereference an invalid per_cpu
    variable.
    
    Avoid this problem by using the newly reintroduced "ready" callback, to
    postpone enabling the IRQ until the related_cpus cpumask is filled in.
    
    Fixes: 0258cb19c77d ("cpufreq: qcom-cpufreq-hw: Use new thermal pressure update function")
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

commit 4f774c4a65bf3987d1a95c966e884f38c8a942af
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date:   Thu Jan 27 19:25:53 2022 -0800

    cpufreq: Reintroduce ready() callback
    
    This effectively revert '4bf8e582119e ("cpufreq: Remove ready()
    callback")', in order to reintroduce the ready callback.
    
    This is needed in order to be able to leave the thermal pressure
    interrupts in the Qualcomm CPUfreq driver disabled during
    initialization, so that it doesn't fire while related_cpus are still 0.
    
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    [ Viresh: Added the Chinese translation as well and updated commit msg ]
    Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

commit 8375dfac4f683e1b2c5956d919d36aeedad46699
Author: Oliver Hartkopp <socketcan@hartkopp.net>
Date:   Wed Feb 9 08:36:01 2022 +0100

    can: isotp: fix error path in isotp_sendmsg() to unlock wait queue
    
    Commit 43a08c3bdac4 ("can: isotp: isotp_sendmsg(): fix TX buffer concurrent
    access in isotp_sendmsg()") introduced a new locking scheme that may render
    the userspace application in a locking state when an error is detected.
    This issue shows up under high load on simultaneously running isotp channels
    with identical configuration which is against the ISO specification and
    therefore breaks any reasonable PDU communication anyway.
    
    Fixes: 43a08c3bdac4 ("can: isotp: isotp_sendmsg(): fix TX buffer concurrent access in isotp_sendmsg()")
    Link: https://lore.kernel.org/all/20220209073601.25728-1-socketcan@hartkopp.net
    Cc: stable@vger.kernel.org
    Cc: Ziyang Xuan <william.xuanziyang@huawei.com>
    Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 7c759040c1dd03954f650f147ae7175476d51314
Author: Oliver Hartkopp <socketcan@hartkopp.net>
Date:   Tue Feb 8 21:00:26 2022 +0100

    can: isotp: fix potential CAN frame reception race in isotp_rcv()
    
    When receiving a CAN frame the current code logic does not consider
    concurrently receiving processes which do not show up in real world
    usage.
    
    Ziyang Xuan writes:
    
    The following syz problem is one of the scenarios. so->rx.len is
    changed by isotp_rcv_ff() during isotp_rcv_cf(), so->rx.len equals
    0 before alloc_skb() and equals 4096 after alloc_skb(). That will
    trigger skb_over_panic() in skb_put().
    
    =======================================================
    CPU: 1 PID: 19 Comm: ksoftirqd/1 Not tainted 5.16.0-rc8-syzkaller #0
    RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:113
    Call Trace:
     <TASK>
     skb_over_panic net/core/skbuff.c:118 [inline]
     skb_put.cold+0x24/0x24 net/core/skbuff.c:1990
     isotp_rcv_cf net/can/isotp.c:570 [inline]
     isotp_rcv+0xa38/0x1e30 net/can/isotp.c:668
     deliver net/can/af_can.c:574 [inline]
     can_rcv_filter+0x445/0x8d0 net/can/af_can.c:635
     can_receive+0x31d/0x580 net/can/af_can.c:665
     can_rcv+0x120/0x1c0 net/can/af_can.c:696
     __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5465
     __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5579
    
    Therefore we make sure the state changes and data structures stay
    consistent at CAN frame reception time by adding a spin_lock in
    isotp_rcv(). This fixes the issue reported by syzkaller but does not
    affect real world operation.
    
    Fixes: e057dd3fc20f ("can: add ISO 15765-2:2016 transport protocol")
    Link: https://lore.kernel.org/linux-can/d7e69278-d741-c706-65e1-e87623d9a8e8@huawei.com/T/
    Link: https://lore.kernel.org/all/20220208200026.13783-1-socketcan@hartkopp.net
    Cc: stable@vger.kernel.org
    Reported-by: syzbot+4c63f36709a642f801c5@syzkaller.appspotmail.com
    Reported-by: Ziyang Xuan <william.xuanziyang@huawei.com>
    Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 7db788ad627aabff2b74d4f1a3b68516d0fee0d7
Author: Louis Peens <louis.peens@corigine.com>
Date:   Tue Feb 8 11:14:53 2022 +0100

    nfp: flower: fix ida_idx not being released
    
    When looking for a global mac index the extra NFP_TUN_PRE_TUN_IDX_BIT
    that gets set if nfp_flower_is_supported_bridge is true is not taken
    into account. Consequently the path that should release the ida_index
    in cleanup is never triggered, causing messages like:
    
        nfp 0000:02:00.0: nfp: Failed to offload MAC on br-ex.
        nfp 0000:02:00.0: nfp: Failed to offload MAC on br-ex.
        nfp 0000:02:00.0: nfp: Failed to offload MAC on br-ex.
    
    after NFP_MAX_MAC_INDEX number of reconfigs. Ultimately this lead to
    new tunnel flows not being offloaded.
    
    Fix this by unsetting the NFP_TUN_PRE_TUN_IDX_BIT before checking if
    the port is of type OTHER.
    
    Fixes: 2e0bc7f3cb55 ("nfp: flower: encode mac indexes with pre-tunnel rule check")
    Signed-off-by: Louis Peens <louis.peens@corigine.com>
    Signed-off-by: Simon Horman <simon.horman@corigine.com>
    Link: https://lore.kernel.org/r/20220208101453.321949-1-simon.horman@corigine.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5611a00697c8ecc5aad04392bea629e9d6a20463
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Feb 7 21:34:51 2022 -0800

    ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
    
    ip[6]mr_free_table() can only be called under RTNL lock.
    
    RTNL: assertion failed at net/core/dev.c (10367)
    WARNING: CPU: 1 PID: 5890 at net/core/dev.c:10367 unregister_netdevice_many+0x1246/0x1850 net/core/dev.c:10367
    Modules linked in:
    CPU: 1 PID: 5890 Comm: syz-executor.2 Not tainted 5.16.0-syzkaller-11627-g422ee58dc0ef #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:unregister_netdevice_many+0x1246/0x1850 net/core/dev.c:10367
    Code: 0f 85 9b ee ff ff e8 69 07 4b fa ba 7f 28 00 00 48 c7 c6 00 90 ae 8a 48 c7 c7 40 90 ae 8a c6 05 6d b1 51 06 01 e8 8c 90 d8 01 <0f> 0b e9 70 ee ff ff e8 3e 07 4b fa 4c 89 e7 e8 86 2a 59 fa e9 ee
    RSP: 0018:ffffc900046ff6e0 EFLAGS: 00010286
    RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
    RDX: ffff888050f51d00 RSI: ffffffff815fa008 RDI: fffff520008dfece
    RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
    R10: ffffffff815f3d6e R11: 0000000000000000 R12: 00000000fffffff4
    R13: dffffc0000000000 R14: ffffc900046ff750 R15: ffff88807b7dc000
    FS:  00007f4ab736e700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007fee0b4f8990 CR3: 000000001e7d2000 CR4: 00000000003506e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     mroute_clean_tables+0x244/0xb40 net/ipv6/ip6mr.c:1509
     ip6mr_free_table net/ipv6/ip6mr.c:389 [inline]
     ip6mr_rules_init net/ipv6/ip6mr.c:246 [inline]
     ip6mr_net_init net/ipv6/ip6mr.c:1306 [inline]
     ip6mr_net_init+0x3f0/0x4e0 net/ipv6/ip6mr.c:1298
     ops_init+0xaf/0x470 net/core/net_namespace.c:140
     setup_net+0x54f/0xbb0 net/core/net_namespace.c:331
     copy_net_ns+0x318/0x760 net/core/net_namespace.c:475
     create_new_namespaces+0x3f6/0xb20 kernel/nsproxy.c:110
     copy_namespaces+0x391/0x450 kernel/nsproxy.c:178
     copy_process+0x2e0c/0x7300 kernel/fork.c:2167
     kernel_clone+0xe7/0xab0 kernel/fork.c:2555
     __do_sys_clone+0xc8/0x110 kernel/fork.c:2672
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7f4ab89f9059
    Code: Unable to access opcode bytes at RIP 0x7f4ab89f902f.
    RSP: 002b:00007f4ab736e118 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
    RAX: ffffffffffffffda RBX: 00007f4ab8b0bf60 RCX: 00007f4ab89f9059
    RDX: 0000000020000280 RSI: 0000000020000270 RDI: 0000000040200000
    RBP: 00007f4ab8a5308d R08: 0000000020000300 R09: 0000000020000300
    R10: 00000000200002c0 R11: 0000000000000206 R12: 0000000000000000
    R13: 00007ffc3977cc1f R14: 00007f4ab736e300 R15: 0000000000022000
     </TASK>
    
    Fixes: f243e5a7859a ("ipmr,ip6mr: call ip6mr_free_table() on failure path")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Cong Wang <cong.wang@bytedance.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220208053451.2885398-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2427f03fb42f9dc14c53108f2c9b5563eb37e770
Author: Cai Huoqing <cai.huoqing@linux.dev>
Date:   Tue Feb 8 09:33:08 2022 +0800

    net: ethernet: litex: Add the dependency on HAS_IOMEM
    
    The LiteX driver uses devm io function API which
    needs HAS_IOMEM enabled, so add the dependency on HAS_IOMEM.
    
    Fixes: ee7da21ac4c3 ("net: Add driver for LiteX's LiteETH network interface")
    Signed-off-by: Cai Huoqing <cai.huoqing@linux.dev>
    Link: https://lore.kernel.org/r/20220208013308.6563-1-cai.huoqing@linux.dev
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 61772b0908c640d0309c40f7d41d062ca4e979fa
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Mon Feb 7 16:19:18 2022 -0800

    ibmvnic: don't release napi in __ibmvnic_open()
    
    If __ibmvnic_open() encounters an error such as when setting link state,
    it calls release_resources() which frees the napi structures needlessly.
    Instead, have __ibmvnic_open() only clean up the work it did so far (i.e.
    disable napi and irqs) and leave the rest to the callers.
    
    If caller of __ibmvnic_open() is ibmvnic_open(), it should release the
    resources immediately. If the caller is do_reset() or do_hard_reset(),
    they will release the resources on the next reset.
    
    This fixes following crash that occurred when running the drmgr command
    several times to add/remove a vnic interface:
    
            [102056] ibmvnic 30000003 env3: Disabling rx_scrq[6] irq
            [102056] ibmvnic 30000003 env3: Disabling rx_scrq[7] irq
            [102056] ibmvnic 30000003 env3: Replenished 8 pools
            Kernel attempted to read user page (10) - exploit attempt? (uid: 0)
            BUG: Kernel NULL pointer dereference on read at 0x00000010
            Faulting instruction address: 0xc000000000a3c840
            Oops: Kernel access of bad area, sig: 11 [#1]
            LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries
            ...
            CPU: 9 PID: 102056 Comm: kworker/9:2 Kdump: loaded Not tainted 5.16.0-rc5-autotest-g6441998e2e37 #1
            Workqueue: events_long __ibmvnic_reset [ibmvnic]
            NIP:  c000000000a3c840 LR: c0080000029b5378 CTR: c000000000a3c820
            REGS: c0000000548e37e0 TRAP: 0300   Not tainted  (5.16.0-rc5-autotest-g6441998e2e37)
            MSR:  8000000000009033 <SF,EE,ME,IR,DR,RI,LE>  CR: 28248484  XER: 00000004
            CFAR: c0080000029bdd24 DAR: 0000000000000010 DSISR: 40000000 IRQMASK: 0
            GPR00: c0080000029b55d0 c0000000548e3a80 c0000000028f0200 0000000000000000
            ...
            NIP [c000000000a3c840] napi_enable+0x20/0xc0
            LR [c0080000029b5378] __ibmvnic_open+0xf0/0x430 [ibmvnic]
            Call Trace:
            [c0000000548e3a80] [0000000000000006] 0x6 (unreliable)
            [c0000000548e3ab0] [c0080000029b55d0] __ibmvnic_open+0x348/0x430 [ibmvnic]
            [c0000000548e3b40] [c0080000029bcc28] __ibmvnic_reset+0x500/0xdf0 [ibmvnic]
            [c0000000548e3c60] [c000000000176228] process_one_work+0x288/0x570
            [c0000000548e3d00] [c000000000176588] worker_thread+0x78/0x660
            [c0000000548e3da0] [c0000000001822f0] kthread+0x1c0/0x1d0
            [c0000000548e3e10] [c00000000000cf64] ret_from_kernel_thread+0x5c/0x64
            Instruction dump:
            7d2948f8 792307e0 4e800020 60000000 3c4c01eb 384239e0 f821ffd1 39430010
            38a0fff6 e92d1100 f9210028 39200000 <e9030010> f9010020 60420000 e9210020
            ---[ end trace 5f8033b08fd27706 ]---
    
    Fixes: ed651a10875f ("ibmvnic: Updated reset handling")
    Reported-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Reviewed-by: Dany Madden <drt@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220208001918.900602-1-sukadev@linux.ibm.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 1335648f0b6f9e2f643ae0c1501e995752b5c79e
Merge: 23de0d7b6f0e3 0d120dfb5d67e
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Feb 8 20:30:38 2022 -0800

    Merge branch 'more-dsa-fixes-for-devres-mdiobus_-alloc-register'
    
    Vladimir Oltean says:
    
    ====================
    More DSA fixes for devres + mdiobus_{alloc,register}
    
    The initial patch series "[net,0/2] Fix mdiobus users with devres"
    https://patchwork.kernel.org/project/netdevbpf/cover/20210920214209.1733768-1-vladimir.oltean@nxp.com/
    fixed some instances where DSA drivers on slow buses (SPI, I2C) trigger
    a panic (changed since then to a warn) in mdiobus_free. That was due to
    devres calling mdiobus_free() with no prior mdiobus_unregister(), which
    again was due to commit ac3a68d56651 ("net: phy: don't abuse devres in
    devm_mdiobus_register()") by Bartosz Golaszewski.
    
    Rafael Richter and Daniel Klauer report yet another variation on that
    theme, but this time it applies to any DSA switch driver, not just those
    on buses which have a "->shutdown() calls ->remove() which unregisters
    children" sequence.
    
    Their setup is that of an LX2160A DPAA2 SoC driving a Marvell DSA switch
    (MDIO). DPAA2 Ethernet drivers probe on the "fsl-mc" bus
    (drivers/bus/fsl-mc/fsl-mc-bus.c). This bus is meant to be the
    kernel-side representation of the networking objects kept by the
    Management Complex (MC) firmware.
    
    The fsl-mc bus driver has this pattern:
    
    static void fsl_mc_bus_shutdown(struct platform_device *pdev)
    {
            fsl_mc_bus_remove(pdev);
    }
    
    which proceeds to remove the children on the bus. Among those children,
    the dpaa2-eth network driver.
    
    When dpaa2-eth is a DSA master, this removal of the master on shutdown
    trips up the device link created by dsa_master_setup(), and as such, the
    Marvell switch is also removed.
    
    From this point on, readers can revisit the description of commits
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    since the prerequisites for the BUG_ON in mdiobus_free() have been
    accomplished if there is a devres mismatch between mdiobus_alloc() and
    mdiobus_register().
    
    Most DSA drivers have this kind of mismatch, and upon my initial
    assessment I had not realized the possibility described above, so I
    didn't fix it. This patch series walks through all drivers and makes
    them use either fully devres, or no devres.
    
    I am aware that there are DSA drivers that are only known to be tested
    with a single DSA master, so some patches are probably overkill for
    them. But code is copy-pasted from so many sources without fully
    understanding the differences, that I think it's better to not leave an
    in-tree source of inspiration that may lead to subtle breakage if not
    adapted properly.
    ====================
    
    Link: https://lore.kernel.org/r/20220207161553.579933-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0d120dfb5d67edc5bcd1804e167dba2b30809afd
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:53 2022 +0200

    net: dsa: lantiq_gswip: don't use devres for mdiobus
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The GSWIP switch is a platform device, so the initial set of constraints
    that I thought would cause this (I2C or SPI buses which call ->remove on
    ->shutdown) do not apply. But there is one more which applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the GSWIP switch driver on shutdown.
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The gswip driver has the code structure in place for orderly mdiobus
    removal, so just replace devm_mdiobus_alloc() with the non-devres
    variant, and add manual free where necessary, to ensure that we don't
    let devres free a still-registered bus.
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9ffe3d09e32da45bb5a29cf2e80ec8d7534010c5
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:52 2022 +0200

    net: dsa: mt7530: fix kernel bug in mdiobus_free() when unbinding
    
    Nobody in this driver calls mdiobus_unregister(), which is necessary if
    mdiobus_register() completes successfully. So if the devres callbacks
    that free the mdiobus get invoked (this is the case when unbinding the
    driver), mdiobus_free() will BUG if the mdiobus is still registered,
    which it is.
    
    My speculation is that this is due to the fact that prior to commit
    ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    from June 2020, _devm_mdiobus_free() used to call mdiobus_unregister().
    But at the time that the mt7530 support was introduced in May 2021, the
    API was already changed. It's therefore likely that the blamed patch was
    developed on an older tree, and incorrectly adapted to net-next. This
    makes the Fixes: tag correct.
    
    Fix the problem by using the devres variant of mdiobus_register.
    
    Fixes: ba751e28d442 ("net: dsa: mt7530: add interrupt support")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bd488afc3b39e045ba71aab472233f2a78726e7b
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:51 2022 +0200

    net: dsa: seville: register the mdiobus under devres
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The Seville VSC9959 switch is a platform device, so the initial set of
    constraints that I thought would cause this (I2C or SPI buses which call
    ->remove on ->shutdown) do not apply. But there is one more which
    applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the seville switch driver on shutdown.
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The seville driver has a code structure that could accommodate both the
    mdiobus_unregister and mdiobus_free calls, but it has an external
    dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls
    devm_mdiobus_alloc_size() on its behalf. So rather than restructuring
    that, and exporting yet one more symbol mscc_miim_teardown(), let's work
    with devres and replace of_mdiobus_register with the devres variant.
    When we use all-devres, we can ensure that devres doesn't free a
    still-registered bus (it either runs both callbacks, or none).
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 209bdb7ec6a28c7cdf580a0a98afbc9fc3b98932
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:50 2022 +0200

    net: dsa: felix: don't use devres for mdiobus
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The Felix VSC9959 switch is a PCI device, so the initial set of
    constraints that I thought would cause this (I2C or SPI buses which call
    ->remove on ->shutdown) do not apply. But there is one more which
    applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the felix switch driver on shutdown.
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The felix driver has the code structure in place for orderly mdiobus
    removal, so just replace devm_mdiobus_alloc_size() with the non-devres
    variant, and add manual free where necessary, to ensure that we don't
    let devres free a still-registered bus.
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 08f1a20822349004bb9cc1b153ecb516e9f2889d
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:49 2022 +0200

    net: dsa: bcm_sf2: don't use devres for mdiobus
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The Starfighter 2 is a platform device, so the initial set of
    constraints that I thought would cause this (I2C or SPI buses which call
    ->remove on ->shutdown) do not apply. But there is one more which
    applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the bcm_sf2 switch driver on shutdown.
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The bcm_sf2 driver has the code structure in place for orderly mdiobus
    removal, so just replace devm_mdiobus_alloc() with the non-devres
    variant, and add manual free where necessary, to ensure that we don't
    let devres free a still-registered bus.
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 50facd86e9fbc4b93fe02e5fe05776047f45dbfb
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:48 2022 +0200

    net: dsa: ar9331: register the mdiobus under devres
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The ar9331 is an MDIO device, so the initial set of constraints that I
    thought would cause this (I2C or SPI buses which call ->remove on
    ->shutdown) do not apply. But there is one more which applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the ar9331 switch driver on shutdown.
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The ar9331 driver doesn't have a complex code structure for mdiobus
    removal, so just replace of_mdiobus_register with the devres variant in
    order to be all-devres and ensure that we don't free a still-registered
    bus.
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Tested-by: Oleksij Rempel <o.rempel@pengutronix.de>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f53a2ce893b2c7884ef94471f170839170a4eba0
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Mon Feb 7 18:15:47 2022 +0200

    net: dsa: mv88e6xxx: don't use devres for mdiobus
    
    As explained in commits:
    74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres")
    5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres")
    
    mdiobus_free() will panic when called from devm_mdiobus_free() <-
    devres_release_all() <- __device_release_driver(), and that mdiobus was
    not previously unregistered.
    
    The mv88e6xxx is an MDIO device, so the initial set of constraints that
    I thought would cause this (I2C or SPI buses which call ->remove on
    ->shutdown) do not apply. But there is one more which applies here.
    
    If the DSA master itself is on a bus that calls ->remove from ->shutdown
    (like dpaa2-eth, which is on the fsl-mc bus), there is a device link
    between the switch and the DSA master, and device_links_unbind_consumers()
    will unbind the Marvell switch driver on shutdown.
    
    systemd-shutdown[1]: Powering off.
    mv88e6085 0x0000000008b96000:00 sw_gl0: Link is Down
    fsl-mc dpbp.9: Removing from iommu group 7
    fsl-mc dpbp.8: Removing from iommu group 7
    ------------[ cut here ]------------
    kernel BUG at drivers/net/phy/mdio_bus.c:677!
    Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
    Modules linked in:
    CPU: 0 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00040-gdc05f73788e5 #15
    pc : mdiobus_free+0x44/0x50
    lr : devm_mdiobus_free+0x10/0x20
    Call trace:
     mdiobus_free+0x44/0x50
     devm_mdiobus_free+0x10/0x20
     devres_release_all+0xa0/0x100
     __device_release_driver+0x190/0x220
     device_release_driver_internal+0xac/0xb0
     device_links_unbind_consumers+0xd4/0x100
     __device_release_driver+0x4c/0x220
     device_release_driver_internal+0xac/0xb0
     device_links_unbind_consumers+0xd4/0x100
     __device_release_driver+0x94/0x220
     device_release_driver+0x28/0x40
     bus_remove_device+0x118/0x124
     device_del+0x174/0x420
     fsl_mc_device_remove+0x24/0x40
     __fsl_mc_device_remove+0xc/0x20
     device_for_each_child+0x58/0xa0
     dprc_remove+0x90/0xb0
     fsl_mc_driver_remove+0x20/0x5c
     __device_release_driver+0x21c/0x220
     device_release_driver+0x28/0x40
     bus_remove_device+0x118/0x124
     device_del+0x174/0x420
     fsl_mc_bus_remove+0x80/0x100
     fsl_mc_bus_shutdown+0xc/0x1c
     platform_shutdown+0x20/0x30
     device_shutdown+0x154/0x330
     kernel_power_off+0x34/0x6c
     __do_sys_reboot+0x15c/0x250
     __arm64_sys_reboot+0x20/0x30
     invoke_syscall.constprop.0+0x4c/0xe0
     do_el0_svc+0x4c/0x150
     el0_svc+0x24/0xb0
     el0t_64_sync_handler+0xa8/0xb0
     el0t_64_sync+0x178/0x17c
    
    So the same treatment must be applied to all DSA switch drivers, which
    is: either use devres for both the mdiobus allocation and registration,
    or don't use devres at all.
    
    The Marvell driver already has a good structure for mdiobus removal, so
    just plug in mdiobus_free and get rid of devres.
    
    Fixes: ac3a68d56651 ("net: phy: don't abuse devres in devm_mdiobus_register()")
    Reported-by: Rafael Richter <Rafael.Richter@gin.de>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Tested-by: Daniel Klauer <daniel.klauer@gin.de>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2a05137a0575b7d1006bdf4c1beeee9e391e22a0
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Tue Feb 8 17:10:02 2022 +0000

    cifs: mark sessions for reconnection in helper function
    
    Today we have the code to mark connections and sessions
    (and tcons) for reconnect clubbed with the code to close
    the socket and abort all mids in the same function.
    
    Sometimes, we need to mark connections and sessions
    outside cifsd thread. So as a part of this change, I'm
    splitting this function into two different functions and
    calling them one after the other in cifs_reconnect.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 52492ff5c583036306bc422a83e246c971af387a
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Tue Feb 8 19:15:17 2022 +0000

    cifs: call helper functions for marking channels for reconnect
    
    cifs_mark_tcp_ses_conns_for_reconnect helper function is now
    meant to be used by any of the threads to mark a channel
    (or all the channels) for reconnect.
    
    Replace all such manual changes to tcpStatus to use this
    helper function, which takes care that the right channels,
    smb sessions and tcons are marked for reconnect.
    
    Also includes one line minor change
    Reported-by: kernel test robot <lkp@intel.com>
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 23de0d7b6f0e3f9a6283a882594c479949da1120
Author: Mahesh Bandewar <maheshb@google.com>
Date:   Mon Feb 7 14:29:01 2022 -0800

    bonding: pair enable_port with slave_arr_updates
    
    When 803.2ad mode enables a participating port, it should update
    the slave-array. I have observed that the member links are participating
    and are part of the active aggregator while the traffic is egressing via
    only one member link (in a case where two links are participating). Via
    kprobes I discovered that slave-arr has only one link added while
    the other participating link wasn't part of the slave-arr.
    
    I couldn't see what caused that situation but the simple code-walk
    through provided me hints that the enable_port wasn't always associated
    with the slave-array update.
    
    Fixes: ee6377147409 ("bonding: Simplify the xmit function for modes that use xmit_hash")
    Signed-off-by: Mahesh Bandewar <maheshb@google.com>
    Acked-by: Jay Vosburgh <jay.vosburgh@canonical.com>
    Link: https://lore.kernel.org/r/20220207222901.1795287-1-maheshb@google.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f81393a5b252df772b934cde81b7e16273afbd43
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Sun Jan 23 17:04:17 2022 +0800

    riscv: extable: fix err reg writing in dedicated uaccess handler
    
    Mayuresh reported commit 20802d8d477d ("riscv: extable: add a dedicated
    uaccess handler") breaks the writev02 test case in LTP. This is due to
    the err reg isn't correctly set with the errno(-EFAULT in writev02
    case). First of all, the err and zero regs are reg numbers rather than
    reg offsets in struct pt_regs; Secondly, regs_set_gpr() should write
    the regs when offset isn't zero(zero means epc)
    
    Fix it by correcting regs_set_gpr() logic and passing the correct reg
    offset to it.
    
    Reported-by: Mayuresh Chitale <mchitale@ventanamicro.com>
    Fixes: 20802d8d477d ("riscv: extable: add a dedicated uaccess handler")
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 084cbb2ec3af2d23be9de65fcc9493e21e265859
Author: Tao Liu <xliutaox@google.com>
Date:   Mon Feb 7 09:59:01 2022 -0800

    gve: Recording rx queue before sending to napi
    
    This caused a significant performance degredation when using generic XDP
    with multiple queues.
    
    Fixes: f5cedc84a30d2 ("gve: Add transmit and receive support")
    Signed-off-by: Tao Liu <xliutaox@google.com>
    Link: https://lore.kernel.org/r/20220207175901.2486596-1-jeroendb@google.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 37ef4c19b4c659926ce65a7ac709ceaefb211c40
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Tue Feb 8 09:59:16 2022 -0800

    Input: clear BTN_RIGHT/MIDDLE on buttonpads
    
    Buttonpads are expected to map the INPUT_PROP_BUTTONPAD property bit
    and the BTN_LEFT key bit.
    
    As explained in the specification, where a device has a button type
    value of 0 (click-pad) or 1 (pressure-pad) there should not be
    discrete buttons:
    https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchpad-windows-precision-touchpad-collection#device-capabilities-feature-report
    
    However, some drivers map the BTN_RIGHT and/or BTN_MIDDLE key bits even
    though the device is a buttonpad and therefore does not have those
    buttons.
    
    This behavior has forced userspace applications like libinput to
    implement different workarounds and quirks to detect buttonpads and
    offer to the user the right set of features and configuration options.
    For more information:
    https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/726
    
    In order to avoid this issue clear the BTN_RIGHT and BTN_MIDDLE key
    bits when the input device is register if the INPUT_PROP_BUTTONPAD
    property bit is set.
    
    Notice that this change will not affect udev because it does not check
    for buttons. See systemd/src/udev/udev-builtin-input_id.c.
    
    List of known affected hardware:
    
     - Chuwi AeroBook Plus
     - Chuwi Gemibook
     - Framework Laptop
     - GPD Win Max
     - Huawei MateBook 2020
     - Prestigio Smartbook 141 C2
     - Purism Librem 14v1
     - StarLite Mk II   - AMI firmware
     - StarLite Mk II   - Coreboot firmware
     - StarLite Mk III  - AMI firmware
     - StarLite Mk III  - Coreboot firmware
     - StarLabTop Mk IV - AMI firmware
     - StarLabTop Mk IV - Coreboot firmware
     - StarBook Mk V
    
    Acked-by: Peter Hutterer <peter.hutterer@who-t.net>
    Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
    Acked-by: Jiri Kosina <jkosina@suse.cz>
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Link: https://lore.kernel.org/r/20220208174806.17183-1-jose.exposito89@gmail.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 3203ce39ac0b2a57a84382ec184c7d4a0bede175
Author: JaeSang Yoo <js.yoo.5b@gmail.com>
Date:   Wed Feb 9 04:54:22 2022 +0900

    tracing: Fix tp_printk option related with tp_printk_stop_on_boot
    
    The kernel parameter "tp_printk_stop_on_boot" starts with "tp_printk" which is
    the same as another kernel parameter "tp_printk". If "tp_printk" setup is
    called before the "tp_printk_stop_on_boot", it will override the latter
    and keep it from being set.
    
    This is similar to other kernel parameter issues, such as:
      Commit 745a600cf1a6 ("um: console: Ignore console= option")
    or init/do_mounts.c:45 (setup function of "ro" kernel param)
    
    Fix it by checking for a "_" right after the "tp_printk" and if that
    exists do not process the parameter.
    
    Link: https://lkml.kernel.org/r/20220208195421.969326-1-jsyoo5b@gmail.com
    
    Signed-off-by: JaeSang Yoo <jsyoo5b@gmail.com>
    [ Fixed up change log and added space after if condition ]
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 3a92e6de780c7afaa826b80058abd952bb2904d8
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Tue Feb 8 15:47:10 2022 +0100

    MAINTAINERS: Add RTLA entry
    
    Add an RTLA entry in the MAINTAINERS file with Steven Rostedt and
    myself as maintainers.
    
    Link: https://lkml.kernel.org/r/50d8870522580905a1c7f3e6fb611a700f632af1.1643994005.git.bristot@kernel.org
    
    Cc: Joe Perches <joe@perches.com>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 92a68053c3468705e2c7c752c9a3f256304a35a6
Author: Akira Kawata <akirakawata1@gmail.com>
Date:   Mon Feb 7 20:20:44 2022 +0900

    Documentation: KUnit: Fix usage bug
    
    Fix a bug of kunit documentation.
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=205773
    
    : Quoting Steve Pfetsch:
    :
    : kunit documentation is incorrect:
    : https://kunit.dev/third_party/stable_kernel/docs/usage.html
    : struct rectangle *self = container_of(this, struct shape, parent);
    :
    :
    : Shouldn't it be:
    : struct rectangle *self = container_of(this, struct rectangle, parent);
    : ?
    
    Signed-off-by: Akira Kawata <akirakawata1@gmail.com>
    Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit e6251ab4551f51fa4cee03523e08051898c3ce82
Merge: 555f3d7be91a8 b49ea673e119f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 8 12:03:07 2022 -0800

    Merge tag 'nfs-for-5.17-2' of git://git.linux-nfs.org/projects/anna/linux-nfs
    
    Pull NFS client fixes from Anna Schumaker:
     "Stable Fixes:
    
       - Fix initialization of nfs_client cl_flags
    
      Other Fixes:
    
       - Fix performance issues with uncached readdir calls
    
       - Fix potential pointer dereferences in rpcrdma_ep_create
    
       - Fix nfs4_proc_get_locations() kernel-doc comment
    
       - Fix locking during sunrpc sysfs reads
    
       - Update my email address in the MAINTAINERS file to my new
         kernel.org email"
    
    * tag 'nfs-for-5.17-2' of git://git.linux-nfs.org/projects/anna/linux-nfs:
      SUNRPC: lock against ->sock changing during sysfs read
      MAINTAINERS: Update my email address
      NFS: Fix nfs4_proc_get_locations() kernel-doc comment
      xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create
      NFS: Fix initialisation of nfs_client cl_flags field
      NFS: Avoid duplicate uncached readdir calls on eof
      NFS: Don't skip directory entries when doing uncached readdir
      NFS: Don't overfill uncached readdir pages

commit a81da65fbae6436e1e2f415532b8aacc3274d840
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Tue Feb 8 19:28:28 2022 +0000

    cifs: call cifs_reconnect when a connection is marked
    
    In cifsd thread, we should continue to call cifs_reconnect
    whenever server->tcpStatus is marked as CifsNeedReconnect.
    This was inexplicably removed by one of my recent commits.
    Fixing that here.
    
    Fixes: a05885ce13bd ("cifs: fix the connection state transitions with multichannel")
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 3915035282573c5e29996ce3173171f5f05234d1
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:26 2022 +0200

    KVM: x86: SVM: move avic definitions from AMD's spec to svm.h
    
    asm/svm.h is the correct place for all values that are defined in
    the SVM spec, and that includes AVIC.
    
    Also add some values from the spec that were not defined before
    and will be soon useful.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220207155447.840194-10-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 755c2bf878607dbddb1423df9abf16b82205896f
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:25 2022 +0200

    KVM: x86: lapic: don't touch irr_pending in kvm_apic_update_apicv when inhibiting it
    
    kvm_apic_update_apicv is called when AVIC is still active, thus IRR bits
    can be set by the CPU after it is called, and don't cause the irr_pending
    to be set to true.
    
    Also logic in avic_kick_target_vcpu doesn't expect a race with this
    function so to make it simple, just keep irr_pending set to true and
    let the next interrupt injection to the guest clear it.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220207155447.840194-9-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2b0ecccb55310a4b8ad5d59c703cf8c821be6260
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:24 2022 +0200

    KVM: x86: nSVM: deal with L1 hypervisor that intercepts interrupts but lets L2 control them
    
    Fix a corner case in which the L1 hypervisor intercepts
    interrupts (INTERCEPT_INTR) and either doesn't set
    virtual interrupt masking (V_INTR_MASKING) or enters a
    nested guest with EFLAGS.IF disabled prior to the entry.
    
    In this case, despite the fact that L1 intercepts the interrupts,
    KVM still needs to set up an interrupt window to wait before
    injecting the INTR vmexit.
    
    Currently the KVM instead enters an endless loop of 'req_immediate_exit'.
    
    Exactly the same issue also happens for SMIs and NMI.
    Fix this as well.
    
    Note that on VMX, this case is impossible as there is only
    'vmexit on external interrupts' execution control which either set,
    in which case both host and guest's EFLAGS.IF
    are ignored, or not set, in which case no VMexits are delivered.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220207155447.840194-8-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 91f673b3e1bd99faf46472b5244cb40fdcd01078
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:22 2022 +0200

    KVM: x86: nSVM: expose clean bit support to the guest
    
    KVM already honours few clean bits thus it makes sense
    to let the nested guest know about it.
    
    Note that KVM also doesn't check if the hardware supports
    clean bits, and therefore nested KVM was
    already setting clean bits and L0 KVM
    was already honouring them.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220207155447.840194-6-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 759cbd59674a6c0aec616a3f4f0740ebd3f5fbef
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:21 2022 +0200

    KVM: x86: nSVM/nVMX: set nested_run_pending on VM entry which is a result of RSM
    
    While RSM induced VM entries are not full VM entries,
    they still need to be followed by actual VM entry to complete it,
    unlike setting the nested state.
    
    This patch fixes boot of hyperv and SMM enabled
    windows VM running nested on KVM, which fail due
    to this issue combined with lack of dirty bit setting.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Cc: stable@vger.kernel.org
    Message-Id: <20220207155447.840194-5-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e8efa4ff00374d2e6f47f6e4628ca3b541c001af
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:20 2022 +0200

    KVM: x86: nSVM: mark vmcb01 as dirty when restoring SMM saved state
    
    While usually, restoring the smm state makes the KVM enter
    the nested guest thus a different vmcb (vmcb02 vs vmcb01),
    KVM should still mark it as dirty, since hardware
    can in theory cache multiple vmcbs.
    
    Failure to do so, combined with lack of setting the
    nested_run_pending (which is fixed in the next patch),
    might make KVM re-enter vmcb01, which was just exited from,
    with completely different set of guest state registers
    (SMM vs non SMM) and without proper dirty bits set,
    which results in the CPU reusing stale IDTR pointer
    which leads to a guest shutdown on any interrupt.
    
    On the real hardware this usually doesn't happen,
    but when running nested, L0's KVM does check and
    honour few dirty bits, causing this issue to happen.
    
    This patch fixes boot of hyperv and SMM enabled
    windows VM running nested on KVM.
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Cc: stable@vger.kernel.org
    Message-Id: <20220207155447.840194-4-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e1779c2714c3023e4629825762bcbc43a3b943df
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:19 2022 +0200

    KVM: x86: nSVM: fix potential NULL derefernce on nested migration
    
    Turns out that due to review feedback and/or rebases
    I accidentally moved the call to nested_svm_load_cr3 to be too early,
    before the NPT is enabled, which is very wrong to do.
    
    KVM can't even access guest memory at that point as nested NPT
    is needed for that, and of course it won't initialize the walk_mmu,
    which is main issue the patch was addressing.
    
    Fix this for real.
    
    Fixes: 232f75d3b4b5 ("KVM: nSVM: call nested_svm_load_cr3 on nested state load")
    Cc: stable@vger.kernel.org
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20220207155447.840194-3-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c53bbe2145f51d3bc0438c2db02e737b9b598bf3
Author: Maxim Levitsky <mlevitsk@redhat.com>
Date:   Mon Feb 7 17:54:18 2022 +0200

    KVM: x86: SVM: don't passthrough SMAP/SMEP/PKE bits in !NPT && !gCR0.PG case
    
    When the guest doesn't enable paging, and NPT/EPT is disabled, we
    use guest't paging CR3's as KVM's shadow paging pointer and
    we are technically in direct mode as if we were to use NPT/EPT.
    
    In direct mode we create SPTEs with user mode permissions
    because usually in the direct mode the NPT/EPT doesn't
    need to restrict access based on guest CPL
    (there are MBE/GMET extenstions for that but KVM doesn't use them).
    
    In this special "use guest paging as direct" mode however,
    and if CR4.SMAP/CR4.SMEP are enabled, that will make the CPU
    fault on each access and KVM will enter endless loop of page faults.
    
    Since page protection doesn't have any meaning in !PG case,
    just don't passthrough these bits.
    
    The fix is the same as was done for VMX in commit:
    commit 656ec4a4928a ("KVM: VMX: fix SMEP and SMAP without EPT")
    
    This fixes the boot of windows 10 without NPT for good.
    (Without this patch, BSP boots, but APs were stuck in endless
    loop of page faults, causing the VM boot with 1 CPU)
    
    Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
    Cc: stable@vger.kernel.org
    Message-Id: <20220207155447.840194-2-mlevitsk@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit dd4589eee99db8f61f7b8f7df1531cad3f74a64d
Author: Sean Christopherson <seanjc@google.com>
Date:   Fri Feb 4 21:41:55 2022 +0000

    Revert "svm: Add warning message for AVIC IPI invalid target"
    
    Remove a WARN on an "AVIC IPI invalid target" exit, the WARN is trivial
    to trigger from guest as it will fail on any destination APIC ID that
    doesn't exist from the guest's perspective.
    
    Don't bother recording anything in the kernel log, the common tracepoint
    for kvm_avic_incomplete_ipi() is sufficient for debugging.
    
    This reverts commit 37ef0c4414c9743ba7f1af4392f0a27a99649f2a.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220204214205.3306634-2-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 9da1e9ab82c92d0e89fe44cad2cd7c2d18d64070
Author: Brian Norris <briannorris@chromium.org>
Date:   Wed Jan 19 16:11:22 2022 -0800

    drm/rockchip: vop: Correct RK3399 VOP register fields
    
    Commit 7707f7227f09 ("drm/rockchip: Add support for afbc") switched up
    the rk3399_vop_big[] register windows, but it did so incorrectly.
    
    The biggest problem is in rk3288_win23_data[] vs.
    rk3368_win23_data[] .format field:
    
      RK3288's format: VOP_REG(RK3288_WIN2_CTRL0, 0x7, 1)
      RK3368's format: VOP_REG(RK3368_WIN2_CTRL0, 0x3, 5)
    
    Bits 5:6 (i.e., shift 5, mask 0x3) are correct for RK3399, according to
    the TRM.
    
    There are a few other small differences between the 3288 and 3368
    definitions that were swapped in commit 7707f7227f09. I reviewed them to
    the best of my ability according to the RK3399 TRM and fixed them up.
    
    This fixes IOMMU issues (and display errors) when testing with BG24
    color formats.
    
    Fixes: 7707f7227f09 ("drm/rockchip: Add support for afbc")
    Cc: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Brian Norris <briannorris@chromium.org>
    Tested-by: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220119161104.1.I1d01436bef35165a8cdfe9308789c0badb5ff46a@changeid

commit c0cfbb122275da1b726481de5a8cffeb24e6322b
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Wed Jan 26 15:55:24 2022 +0100

    drm/rockchip: dw_hdmi: Do not leave clock enabled in error case
    
    The driver returns an error when devm_phy_optional_get() fails leaving
    the previously enabled clock turned on. Change order and enable the
    clock only after the phy has been acquired.
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220126145549.617165-3-s.hauer@pengutronix.de

commit 4bbf59a9db44c78dd3e5c72057548f7c1eb8d2ba
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Tue Feb 8 15:36:21 2022 +0100

    rtla: Fix segmentation fault when failing to enable -t
    
    rtla osnoise and timerlat are causing a segmentation fault when running
    with the --trace option on a kernel that does not support multiple
    instances. For example:
    
        [root@f34 rtla]# rtla osnoise top -t
        failed to enable the tracer osnoise
        Could not enable osnoiser tracer for tracing
        Failed to enable the trace instance
        Segmentation fault (core dumped)
    
    This error happens because the exit code of the tools is trying
    to destroy the trace instance that failed to be created.
    
    Make osnoise_destroy_tool() aware of possible NULL osnoise_tool *,
    and do not attempt to destroy it. This also simplifies the exit code.
    
    Link: https://lkml.kernel.org/r/5660a2b6bf66c2655842360f2d7f6b48db5dba23.1644327249.git.bristot@kernel.org
    
    Suggested-by: Steven Rostedt <rostedt@goodmis.org>
    Fixes: 1eceb2fc2ca5 ("rtla/osnoise: Add osnoise top mode")
    Fixes: 829a6c0b5698 ("rtla/osnoise: Add the hist mode")
    Fixes: a828cd18bc4a ("rtla: Add timerlat tool and timelart top mode")
    Fixes: 1eeb6328e8b3 ("rtla/timerlat: Add timerlat hist mode")
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 54309fde1a352ad2674ebba004a79f7d20b9f037
Author: Christian Löhle <CLoehle@hyperstone.com>
Date:   Fri Feb 4 15:11:37 2022 +0000

    mmc: block: fix read single on recovery logic
    
    On reads with MMC_READ_MULTIPLE_BLOCK that fail,
    the recovery handler will use MMC_READ_SINGLE_BLOCK for
    each of the blocks, up to MMC_READ_SINGLE_RETRIES times each.
    The logic for this is fixed to never report unsuccessful reads
    as success to the block layer.
    
    On command error with retries remaining, blk_update_request was
    called with whatever value error was set last to.
    In case it was last set to BLK_STS_OK (default), the read will be
    reported as success, even though there was no data read from the device.
    This could happen on a CRC mismatch for the response,
    a card rejecting the command (e.g. again due to a CRC mismatch).
    In case it was last set to BLK_STS_IOERR, the error is reported correctly,
    but no retries will be attempted.
    
    Fixes: 81196976ed946c ("mmc: block: Add blk-mq support")
    Cc: stable@vger.kernel.org
    Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
    Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
    Link: https://lore.kernel.org/r/bc706a6ab08c4fe2834ba0c05a804672@hyperstone.com
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit 1830947ee4e8ed3e7083e8d41d2b8486568ebea7
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Wed Jan 12 15:07:37 2022 +0100

    arm64: Remove ARCH_VULCAN
    
    Commit a314520d82317650 ("arm64: disable Broadcom Vulcan platform")
    did not remove the ARCH_VULCAN configuration symbol, as there were still
    references to this symbol.
    
    As of commits 240d3d5b2a7a3263 ("gpio: xlp: update GPIO_XLP dependency") and
    f85a543e5373eeba ("arm64: defconfig: drop ARCH_VULCAN"), the last users
    of ARCH_VULCAN have been removed.
    
    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Link: https://lore.kernel.org/r/9e8fef2cf4f2d5648e87076bc96601cff945ce40.1641996361.git.geert+renesas@glider.be'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit b49ea673e119f59c71645e2f65b3ccad857c90ee
Author: NeilBrown <neilb@suse.de>
Date:   Mon Jan 17 16:36:53 2022 +1100

    SUNRPC: lock against ->sock changing during sysfs read
    
    ->sock can be set to NULL asynchronously unless ->recv_mutex is held.
    So it is important to hold that mutex.  Otherwise a sysfs read can
    trigger an oops.
    Commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before
    handling sysfs reads") appears to attempt to fix this problem, but it
    only narrows the race window.
    
    Fixes: 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads")
    Fixes: a8482488a7d6 ("SUNRPC query transport's source port")
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 63db37e99ac17f575766c9317f927c8d4c6e8cdf
Author: Anna Schumaker <Anna.Schumaker@Netapp.com>
Date:   Mon Feb 7 11:14:47 2022 -0500

    MAINTAINERS: Update my email address
    
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 3d4a39404ba323b08fb42bcdca9a015144e213dd
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Thu Jan 13 10:26:04 2022 +0800

    NFS: Fix nfs4_proc_get_locations() kernel-doc comment
    
    Add the description of @server and @fhandle, and remove the excess
    @inode in nfs4_proc_get_locations() kernel-doc comment to remove
    warnings found by running scripts/kernel-doc, which is caused by
    using 'make W=1'.
    
    fs/nfs/nfs4proc.c:8219: warning: Function parameter or member 'server'
    not described in 'nfs4_proc_get_locations'
    fs/nfs/nfs4proc.c:8219: warning: Function parameter or member 'fhandle'
    not described in 'nfs4_proc_get_locations'
    fs/nfs/nfs4proc.c:8219: warning: Excess function parameter 'inode'
    description in 'nfs4_proc_get_locations'
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit a9c10b5b3b67b3750a10c8b089b2e05f5e176e33
Author: Dan Aloni <dan.aloni@vastdata.com>
Date:   Tue Jan 25 22:06:46 2022 +0200

    xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create
    
    If there are failures then we must not leave the non-NULL pointers with
    the error value, otherwise `rpcrdma_ep_destroy` gets confused and tries
    free them, resulting in an Oops.
    
    Signed-off-by: Dan Aloni <dan.aloni@vastdata.com>
    Acked-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 468d126dab45718feeb728319be20bd869a5eaa7
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Wed Feb 2 18:52:01 2022 -0500

    NFS: Fix initialisation of nfs_client cl_flags field
    
    For some long forgotten reason, the nfs_client cl_flags field is
    initialised in nfs_get_client() instead of being initialised at
    allocation time. This quirk was harmless until we moved the call to
    nfs_create_rpc_client().
    
    Fixes: dd99e9f98fbf ("NFSv4: Initialise connection to the server in nfs4_alloc_client()")
    Cc: stable@vger.kernel.org # 4.8.x
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit db405774f6a80c5607dcf43ec810f078bb5c660d
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon Jan 31 22:05:32 2022 +0100

    MAINTAINERS: Add entry for fbdev core
    
    Ever since Tomi extracted the core code in 2014 it's been defacto me
    maintaining this, with help from others from dri-devel and sometimes
    Linus (but those are mostly merge conflicts):
    
    $ git shortlog -ns  drivers/video/fbdev/core/ | head -n5
        35  Daniel Vetter
        23  Linus Torvalds
        10  Hans de Goede
         9  Dave Airlie
         6  Peter Rosin
    
    I think ideally we'd also record that the various firmware fb drivers
    (efifb, vesafb, ...) are also maintained in drm-misc because for the
    past few years the patches have either been to fix handover issues
    with drm drivers, or caused handover issues with drm drivers. So any
    other tree just doesn't make sense. But also, there's plenty of
    outdated MAINTAINER entries for these with people and git trees that
    haven't been active in years, so maybe let's just leave them alone.
    And furthermore distros are now adopting simpledrm as the firmware fb
    driver, so hopefully the need to care about the fbdev firmware drivers
    will go down going forward.
    
    Note that drm-misc is group maintained, I expect that to continue like
    we've done before, so no new expectations that patches all go through
    my hands. That would be silly. This also means I'm happy to put any
    other volunteer's name in the M: line, but otherwise git log says I'm
    the one who's stuck with this.
    
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Acked-by: Daniel Stone <daniels@collabora.com>
    Acked-by: Dave Airlie <airlied@redhat.com>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>Cc: Dave Airlie <airlied@gmail.com>
    Acked-by: Helge Deller <deller@gmx.de>
    Acked-by: Jani Nikula <jani.nikula@intel.com>
    Acked-by: Maxime Ripard <maxime@cerno.tech>
    Acked-by: Sam Ravnborg <sam@ravnborg.org>
    Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
    Acked-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
    Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Linux Fbdev development list <linux-fbdev@vger.kernel.org>
    Cc: Pavel Machek <pavel@ucw.cz>
    Cc: Sam Ravnborg <sam@ravnborg.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Javier Martinez Canillas <javierm@redhat.com>
    Cc: DRI Development <dri-devel@lists.freedesktop.org>
    Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
    Cc: Claudio Suarez <cssk@net-c.es>
    Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: Daniel Vetter <daniel.vetter@intel.com>
    Cc: Sven Schnelle <svens@stackframe.org>
    Cc: Gerd Hoffmann <kraxel@redhat.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220131210552.482606-2-daniel.vetter@ffwll.ch

commit 50b10528aad568c95f772039d4b3093b4aea7439
Author: Helge Deller <deller@gmx.de>
Date:   Mon Feb 7 16:59:31 2022 +0100

    fbcon: Avoid 'cap' set but not used warning
    
    Fix this kernel test robot warning:
    
      drivers/video/fbdev/core/fbcon.c: In function 'fbcon_init':
      drivers/video/fbdev/core/fbcon.c:1028:6: warning: variable 'cap' set but not used [-Wunused-but-set-variable]
    
    The cap variable is only used when CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION
    is enabled. Drop the temporary variable and use info->flags instead.
    
    Fixes: 87ab9f6b7417 ("Revert "fbcon: Disable accelerated scrolling")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/YgFB4xqI+As196FR@p100

commit ab3824427b848da10e9fe2727f035bbeecae6ff4
Author: Zhou Qingyang <zhou1615@umn.edu>
Date:   Wed Dec 1 01:22:53 2021 +0800

    spi: spi-zynq-qspi: Fix a NULL pointer dereference in zynq_qspi_exec_mem_op()
    
    In zynq_qspi_exec_mem_op(), kzalloc() is directly used in memset(),
    which could lead to a NULL pointer dereference on failure of
    kzalloc().
    
    Fix this bug by adding a check of tmpbuf.
    
    This bug was found by a static analyzer. The analysis employs
    differential checking to identify inconsistent security operations
    (e.g., checks or kfrees) between two code paths and confirms that the
    inconsistent operations are not recovered in the current function or
    the callers, so they constitute bugs.
    
    Note that, as a bug found by static analysis, it can be a false
    positive or hard to trigger. Multiple researchers have cross-reviewed
    the bug.
    
    Builds with CONFIG_SPI_ZYNQ_QSPI=m show no new warnings,
    and our static analyzer no longer warns about this code.
    
    Fixes: 67dca5e580f1 ("spi: spi-mem: Add support for Zynq QSPI controller")
    Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
    Link: https://lore.kernel.org/r/20211130172253.203700-1-zhou1615@umn.edu
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4e2a354e3775870ca823f1fb29bbbffbe11059a6
Author: Oliver Barta <oliver.barta@aptiv.com>
Date:   Tue Feb 8 09:46:45 2022 +0100

    regulator: core: fix false positive in regulator_late_cleanup()
    
    The check done by regulator_late_cleanup() to detect whether a regulator
    is on was inconsistent with the check done by _regulator_is_enabled().
    While _regulator_is_enabled() takes the enable GPIO into account,
    regulator_late_cleanup() was not doing that.
    
    This resulted in a false positive, e.g. when a GPIO-controlled fixed
    regulator was used, which was not enabled at boot time, e.g.
    
    reg_disp_1v2: reg_disp_1v2 {
            compatible = "regulator-fixed";
            regulator-name = "display_1v2";
            regulator-min-microvolt = <1200000>;
            regulator-max-microvolt = <1200000>;
            gpio = <&tlmm 148 0>;
            enable-active-high;
    };
    
    Such regulator doesn't have an is_enabled() operation. Nevertheless
    it's state can be determined based on the enable GPIO. The check in
    regulator_late_cleanup() wrongly assumed that the regulator is on and
    tried to disable it.
    
    Signed-off-by: Oliver Barta <oliver.barta@aptiv.com>
    Link: https://lore.kernel.org/r/20220208084645.8686-1-oliver.barta@aptiv.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4c33de0673ced9c7c37b3bbd9bfe0fda72340b2a
Author: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Date:   Mon Feb 7 17:30:00 2022 +0200

    ASoC: rt5682: do not block workqueue if card is unbound
    
    The current rt5682_jack_detect_handler() assumes the component
    and card will always show up and implements an infinite usleep
    loop waiting for them to show up.
    
    This does not hold true if a codec interrupt (or other
    event) occurs when the card is unbound. The codec driver's
    remove  or shutdown functions cannot cancel the workqueue due
    to the wait loop. As a result, code can either end up blocking
    the workqueue, or hit a kernel oops when the card is freed.
    
    Fix the issue by rescheduling the jack detect handler in
    case the card is not ready. In case card never shows up,
    the shutdown/remove/suspend calls can now cancel the detect
    task.
    
    Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
    Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
    Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Reviewed-by: Shuming Fan <shumingf@realtek.com>
    Link: https://lore.kernel.org/r/20220207153000.3452802-3-kai.vehmanen@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit a6d78661dc903d90a327892bbc34268f3a5f4b9c
Author: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Date:   Mon Feb 7 17:29:59 2022 +0200

    ASoC: rt5668: do not block workqueue if card is unbound
    
    The current rt5668_jack_detect_handler() assumes the component
    and card will always show up and implements an infinite usleep
    loop waiting for them to show up.
    
    This does not hold true if a codec interrupt (or other
    event) occurs when the card is unbound. The codec driver's
    remove  or shutdown functions cannot cancel the workqueue due
    to the wait loop. As a result, code can either end up blocking
    the workqueue, or hit a kernel oops when the card is freed.
    
    Fix the issue by rescheduling the jack detect handler in
    case the card is not ready. In case card never shows up,
    the shutdown/remove/suspend calls can now cancel the detect
    task.
    
    Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
    Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
    Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Reviewed-by: Shuming Fan <shumingf@realtek.com>
    Link: https://lore.kernel.org/r/20220207153000.3452802-2-kai.vehmanen@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit d7b530fdc45e75a54914a194c4becd9672a4e24f
Author: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Date:   Mon Feb 7 17:29:58 2022 +0200

    ASoC: rt5682s: do not block workqueue if card is unbound
    
    The current rt5682s_jack_detect_handler() assumes the component
    and card will always show up and implements an infinite usleep
    loop waiting for them to show up.
    
    This does not hold true if a codec interrupt (or other
    event) occurs when the card is unbound. The codec driver's
    remove  or shutdown functions cannot cancel the workqueue due
    to the wait loop. As a result, code can either end up blocking
    the workqueue, or hit a kernel oops when the card is freed.
    
    Fix the issue by rescheduling the jack detect handler in
    case the card is not ready. In case card never shows up,
    the shutdown/remove/suspend calls can now cancel the detect
    task.
    
    Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
    Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
    Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
    Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Reviewed-by: Shuming Fan <shumingf@realtek.com>
    Link: https://lore.kernel.org/r/20220207153000.3452802-1-kai.vehmanen@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 307f31452078792aab94a729fce33200c6e42dc4
Author: Martin Povišer <povik+lin@cutebit.org>
Date:   Fri Feb 4 10:53:01 2022 +0100

    ASoC: tas2770: Insert post reset delay
    
    Per TAS2770 datasheet there must be a 1 ms delay from reset to first
    command. So insert delays into the driver where appropriate.
    
    Fixes: 1a476abc723e ("tas2770: add tas2770 smart PA kernel driver")
    Signed-off-by: Martin Povišer <povik+lin@cutebit.org>
    Link: https://lore.kernel.org/r/20220204095301.5554-1-povik+lin@cutebit.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 946eb87114af37c9c13c618a7c1cdaca936905fa
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Mon Feb 7 08:09:23 2022 -0800

    ASoC: Revert "ASoC: mediatek: Check for error clk pointer"
    
    This reverts commit 9de2b9286a6d ("ASoC: mediatek: Check for error clk
    pointer").
    
    With this patch in the tree, Chromebooks running the affected hardware
    no longer boot. Bisect points to this patch, and reverting it fixes
    the problem.
    
    An analysis of the code with this patch applied shows:
    
            ret = init_clks(pdev, clk);
            if (ret)
                    return ERR_PTR(ret);
    ...
                    for (j = 0; j < MAX_CLKS && data->clk_id[j]; j++) {
                            struct clk *c = clk[data->clk_id[j]];
    
                            if (IS_ERR(c)) {
                                    dev_err(&pdev->dev, "%s: clk unavailable\n",
                                            data->name);
                                    return ERR_CAST(c);
                            }
    
                            scpd->clk[j] = c;
                    }
    
    Not all clocks in the clk_names array have to be present. Only the clocks
    in the data->clk_id array are actually needed. The code already checks if
    the required clocks are available and bails out if not. The assumption that
    all clocks have to be present is wrong, and commit 9de2b9286a6d ("ASoC:
    mediatek: Check for error clk pointer") needs to be reverted.
    
    Cc: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Cc: Mark Brown <broonie@kernel.org>
    Cc: James Liao <jamesjj.liao@mediatek.com>
    Cc: Kevin Hilman <khilman@baylibre.com>
    Cc: Matthias Brugger <matthias.bgg@gmail.com>
    Reported-by: Frank Wunderlich <frank-w@public-files.de>
    Reported-by: Daniel Golle <daniel@makrotopia.org>
    Fixes: 9de2b9286a6d ("ASoC: mediatek: Check for error clk pointer")
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>
    Link: https://lore.kernel.org/r/20220207160923.3911501-1-linux@roeck-us.net
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 2e8a8b5955a000cc655f7e368670518cbb77fe58
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Wed Jan 26 15:55:40 2022 +0100

    arm64: dts: rockchip: reorder rk3399 hdmi clocks
    
    The binding specifies the clock order to "cec", "grf", "vpll". Reorder
    the clocks accordingly.
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
    Link: https://lore.kernel.org/r/20220126145549.617165-19-s.hauer@pengutronix.de
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit 117b4e96c7f362eb6459543883fc07f77662472c
Author: Udipto Goswami <quic_ugoswami@quicinc.com>
Date:   Mon Feb 7 09:55:58 2022 +0530

    usb: dwc3: gadget: Prevent core from processing stale TRBs
    
    With CPU re-ordering on write instructions, there might
    be a chance that the HWO is set before the TRB is updated
    with the new mapped buffer address.
    And in the case where core is processing a list of TRBs
    it is possible that it fetched the TRBs when the HWO is set
    but before the buffer address is updated.
    Prevent this by adding a memory barrier before the HWO
    is updated to ensure that the core always process the
    updated TRBs.
    
    Fixes: f6bafc6a1c9d ("usb: dwc3: convert TRBs into bitshifts")
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
    Signed-off-by: Udipto Goswami <quic_ugoswami@quicinc.com>
    Link: https://lore.kernel.org/r/1644207958-18287-1-git-send-email-quic_ugoswami@quicinc.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit bca828ccdd6548d24613d0cede04ada4dfb2f89c
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Sun Feb 6 02:56:26 2022 +0100

    speakup-dectlk: Restore pitch setting
    
    d97a9d7aea04 ("staging/speakup: Add inflection synth parameter")
    introduced the inflection parameter, but happened to drop the pitch
    parameter from the dectlk driver. This restores it.
    
    Cc: stable@vger.kernel.org
    Fixes: d97a9d7aea04 ("staging/speakup: Add inflection synth parameter")
    Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
    Link: https://lore.kernel.org/r/20220206015626.aesbhvvdkmqsrbaw@begin
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 7896020612039fcbff11b8a903b28b0f157d2e5f
Merge: 4a64f2d3527a0 3375aa77135f6
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 10:51:03 2022 +0100

    Merge tag 'amlogic-fixes-v5.17-rc-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux into arm/fixes
    
    Amlogic fixes for v5.17-rc
    - meson6/meson8/meson8b UART compatible fixup to notably fix earlycon
    
    * tag 'amlogic-fixes-v5.17-rc-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux:
      ARM: dts: meson8b: Fix the UART device-tree schema validation
      ARM: dts: meson8: Fix the UART device-tree schema validation
      ARM: dts: meson: Fix the UART compatible strings
    
    Link: https://lore.kernel.org/r/746a7f25-1c96-9d27-3a08-e86b2af608ef@baylibre.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit cc38ef936840ac29204d806deb4d1836ec509594
Author: Niklas Cassel <niklas.cassel@wdc.com>
Date:   Fri Feb 4 13:02:25 2022 +0000

    gpio: sifive: use the correct register to read output values
    
    Setting the output of a GPIO to 1 using gpiod_set_value(), followed by
    reading the same GPIO using gpiod_get_value(), will currently yield an
    incorrect result.
    
    This is because the SiFive GPIO device stores the output values in reg_set,
    not reg_dat.
    
    Supply the flag BGPIOF_READ_OUTPUT_REG_SET to bgpio_init() so that the
    generic driver reads the correct register.
    
    Fixes: 96868dce644d ("gpio/sifive: Add GPIO driver for SiFive SoCs")
    Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    [Bartosz: added the Fixes tag]
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 95a4eed7dd5b7c1c3664a626174290686ddbee9f
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Tue Feb 1 17:27:55 2022 +0200

    gpiolib: Never return internal error codes to user space
    
    Currently it's possible that character device interface may return
    the error codes which are not supposed to be seen by user space.
    In this case it's EPROBE_DEFER.
    
    Wrap it to return -ENODEV instead as sysfs does.
    
    Fixes: d7c51b47ac11 ("gpio: userspace ABI for reading/writing GPIO lines")
    Fixes: 61f922db7221 ("gpio: userspace ABI for reading GPIO line events")
    Fixes: 3c0d9c635ae2 ("gpiolib: cdev: support GPIO_V2_GET_LINE_IOCTL and GPIO_V2_LINE_GET_VALUES_IOCTL")
    Reported-by: Suresh Balakrishnan <suresh.balakrishnan@intel.com>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 4a64f2d3527a0ae400bcea353898a8f47209b446
Author: Michael Walle <michael@walle.cc>
Date:   Mon Feb 7 19:46:52 2022 +0100

    MAINTAINERS: add myself as a maintainer for the sl28cpld
    
    The sl28cpld is a management controller found on the Kontron SMARC-sAL28
    board for now. Support for it was added by me quite a while ago, but I
    didn't add a MAINTAINERS entry. Add it now.
    
    Signed-off-by: Michael Walle <michael@walle.cc>
    Link: https://lore.kernel.org/r/20220207184652.1218447-1-michael@walle.cc'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 5b52ada7141f7adb53bed6d104df2690f4304f4c
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 7 18:55:03 2022 +0100

    MAINTAINERS: add IRC to ARM sub-architectures and Devicetree
    
    Mention the IRC channels used for discussions about ARM/ARM64
    sub-architectures and Devicetree.  This documents purely existing state.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220207175503.425200-2-krzysztof.kozlowski@canonical.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit d9bc0de02aa0afa7ff96682428b2bb792bf00d9c
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 7 18:55:02 2022 +0100

    MAINTAINERS: arm: samsung: add Git tree and IRC
    
    Add already used Krzysztof Kozlowski's Git tree for Samsung
    S3C/S5P/Exynos ARM sub-architecture and IRC channel (#linux-exynos at
    Libera).  This documents purely existing state.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220207175503.425200-1-krzysztof.kozlowski@canonical.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 6efb9f739d41b867cb7e865ba4213003ab1b9c91
Merge: d9058d6a0e92d 3037b174b1876
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:57:07 2022 +0100

    Merge tag 'socfpga_fix_for_v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux into arm/fixes
    
    SoCFPGA fix for v5.17, part 1
    - Fix a build error for socfpga_defconfig
    
    * tag 'socfpga_fix_for_v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux:
      ARM: socfpga: fix missing RESET_CONTROLLER
    
    Link: https://lore.kernel.org/r/20220207101002.7566-1-dinguyen@kernel.org
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit d9058d6a0e92d8e4a00855f8fe204792f42794db
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sun Feb 6 00:53:12 2022 +0100

    ARM: dts: Fix boot regression on Skomer
    
    The signal routing on the Skomer board was incorrect making
    it impossible to mount root from the SD card. Fix this up.
    
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Cc: stable@vger.kernel.org
    Cc: Stefan Hansson <newbyte@disroot.org>
    Link: https://lore.kernel.org/r/20220205235312.446730-1-linus.walleij@linaro.org'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 99c410e89ed0f9aef3c652279813611576d9ea5e
Merge: 724004a11a84e aee744a37aaf2
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:55:52 2022 +0100

    Merge tag 'ti-k3-dt-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux into arm/fixes
    
    Device Tree fixes for TI K3 platform for v5.17 merge window
    
    * Update J721S2 platform to switch serial aliases to ttyS2.
    
    * tag 'ti-k3-dt-fixes-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux:
      arm64: dts: ti: k3-j721s2-common-proc-board: Alias console uart to serial2
      arm64: dts: ti: k3-j721s2: Move aliases to board dts
    
    Link: https://lore.kernel.org/r/20220204130716.fjlm4vvcbtzcwlwx@chalice
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 724004a11a84ea762b03bc1822c40d977ae53f1c
Author: Rob Herring <robh@kernel.org>
Date:   Thu Feb 3 18:41:17 2022 -0600

    ARM: dts: spear320: Drop unused and undocumented 'irq-over-gpio' property
    
    The property 'irq-over-gpio' is both unused and undocumented. It also
    happens to collide with standard *-gpio properties. As it is not needed,
    drop it.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220204004117.1232902-1-robh@kernel.org'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 301a5d3ad2432d7829f59432ca0a93a6defbb9a1
Author: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Date:   Tue Feb 1 17:31:18 2022 +1030

    soc: aspeed: lpc-ctrl: Block error printing on probe defer cases
    
    Add a checking code when it gets -EPROBE_DEFER while getting a clock
    resource. In this case, it doesn't need to print out an error message
    because the probing will be re-visited.
    
    Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
    Signed-off-by: Joel Stanley <joel@jms.id.au>
    Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
    Reviewed-by: Iwona Winiarska <iwona.winiarska@intel.com>
    Link: https://lore.kernel.org/r/20211104173709.222912-1-jae.hyun.yoo@intel.com
    Link: https://lore.kernel.org/r/20220201070118.196372-1-joel@jms.id.au'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 088400521e421a1df7d0128dc0f9246db4ef1c7c
Author: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
Date:   Tue Feb 1 17:30:27 2022 +1030

    docs/ABI: testing: aspeed-uart-routing: Escape asterisk
    
    Escape asterisk symbols to fix the following warning:
    
    "WARNING: Inline emphasis start-string without end-string"
    
    Fixes: c6807970c3bc ("soc: aspeed: Add UART routing support")
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
    Signed-off-by: Joel Stanley <joel@jms.id.au>
    Link: https://lore.kernel.org/r/20220124014351.9121-1-chiawei_wang@aspeedtech.com
    Link: https://lore.kernel.org/r/20220201070027.196314-1-joel@jms.id.au'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit ebdd054ffa14ece5764365846f90fea3703c935f
Merge: f8d1fc05e2881 442b0c08db7e3
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:52:04 2022 +0100

    Merge tag 'samsung-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into arm/fixes
    
    Samsung fixes for v5.17
    
    1. Typo in CONFIG_EXYNOS_USI description.
    2. Add Alim Akhtar as a reviewer for Samsung Exynos platform.
    
    * tag 'samsung-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux:
      soc: samsung: Fix typo in CONFIG_EXYNOS_USI description
      MAINTAINERS: add reviewer entry for Samsung/Exynos platform
    
    Link: https://lore.kernel.org/r/20220129115442.13474-1-krzysztof.kozlowski@canonical.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit f8d1fc05e2881fe3e466b212af7a2b67c2d88f8d
Merge: cc0def5b4ed61 91f6d5f181f66
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:51:29 2022 +0100

    Merge tag 'imx-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/fixes
    
    i.MX fixes for 5.17:
    
    - Fix sound card model for MBa8Mx board.
    - Drop i.MX8MQ LCDIF port node unit-address to fix DTC warning.
    - Add missing SD card detect line for imx6qdl-udoo board.
    - Remove MX23_PAD_SSP1_DETECT from imx23-evk hog group. It fixes the
      broken SD ard support on the board.
    - A couple of fixes from Martin Kepplinger to fix the MIPI_CSI port
      number on i.MX8MQ.
    - Re-enable ftm_alarm0 device on ls1028a-kontron-sl28 board which was
      disabled accidentally.
    - Fix 'assigned-clocks-parents' typo in i.MX7ULP watchdog device node.
    - Disable GPU device on imx8mn-venice-gw7902 board, as it uses
      MIMX8MN5CVTI SoC which does not integrate a GPU.
    
    * tag 'imx-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:
      arm64: dts: imx8mq: fix lcdif port node
      arm64: dts: imx8mq-librem5: fix mipi_csi1 port number to sensor
      arm64: dts: imx8mq: fix mipi_csi bidirectional port numbers
      ARM: dts: imx7ulp: Fix 'assigned-clocks-parents' typo
      arm64: dts: ls1028a: sl28: re-enable ftm_alarm0
      arm64: dts: freescale: Fix sound card model for MBa8Mx
      ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
      ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
      arm64: dts: imx8mn-venice-gw7902: disable gpu
    
    Link: https://lore.kernel.org/r/20220129073150.GZ4686@dragon
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit cc0def5b4ed61a262b88c67e6f8ed1a70c52c568
Merge: 78b390bd5657e 4064c461148ab
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:48:43 2022 +0100

    Merge tag 'optee-fixes-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee into arm/fixes
    
    OP-TE fixes for v5.17
    
    - Adds error checking in optee_ffa_do_call_with_arg()
    - Reintroduces an accidentally lost fix for a memref size check
    - Uses bitmap_free() to free memory obtained with bitmap_zalloc()
    
    * tag 'optee-fixes-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee:
      optee: add error checks in optee_ffa_do_call_with_arg()
      tee: optee: do not check memref size on return from Secure World
      optee: Use bitmap_free() to free bitmap
    
    Link: https://lore.kernel.org/r/20220126102609.GA1516258@jade
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 78b390bd5657e79f8e60b736f81ac1a3203777ea
Merge: 7eabedfb29034 6dc701ee9fabf
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Feb 8 09:47:05 2022 +0100

    Merge tag 'asahi-soc-maintainers-5.17' of https://github.com/AsahiLinux/linux into arm/fixes
    
    Apple SoC MAINTAINERS updates for 5.17.
    
    Adds the watchdog driver MAINTAINERS changes. The driver itself is
    already merged.
    
    This branch is based on asahi-soc-dt-5.17-v2 to avoid a merge conflict.
    
    * tag 'asahi-soc-maintainers-5.17' of https://github.com/AsahiLinux/linux:
      MAINTAINERS: Add Apple watchdog to ARM/APPLE MACHINE SUPPORT
    
    Link: https://lore.kernel.org/r/24ae6871-3e67-5c7f-2060-28048db439a2@marcan.st
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit c8ea23d5fa59f28302d4e3370c75d9c308e64410
Author: Zoltán Böszörményi <zboszor@gmail.com>
Date:   Fri Feb 4 13:57:50 2022 +0100

    ata: libata-core: Disable TRIM on M88V29
    
    This device is a CF card, or possibly an SSD in CF form factor.
    It supports NCQ and high speed DMA.
    
    While it also advertises TRIM support, I/O errors are reported
    when the discard mount option fstrim is used. TRIM also fails
    when disabling NCQ and not just as an NCQ command.
    
    TRIM must be disabled for this device.
    
    Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 921d2eb09673af8e74aa11369a4de700e676a9c1
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Feb 8 15:16:09 2022 +0900

    ata: sata_fsl: fix sscanf() and sysfs_emit() format strings
    
    Use the %u format for unsigned int parameters handling with sscanf() and
    sysfs_emit() to avoid compilation warnings. In
    fsl_sata_rx_watermark_store(), the call to sscanf() to parse a single
    argument is replaced with a call to kstrtouint().
    
    While at it, also replace the printk(KERN_ERR) calls with dev_err()
    calls and fix blank lines in fsl_sata_rx_watermark_store().
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 5852ed2a6a39c862c8a3fdf646e1f4e01b91d710
Author: James Smart <jsmart2021@gmail.com>
Date:   Mon Feb 7 10:04:42 2022 -0800

    scsi: lpfc: Reduce log messages seen after firmware download
    
    Messages around firmware download were incorrectly tagged as being related
    to discovery trace events. Thus, firmware download status ended up dumping
    the trace log as well as the firmware update message. As there were a
    couple of log messages in this state, the trace log was dumped multiple
    times.
    
    Resolve this by converting from trace events to SLI events.
    
    Link: https://lore.kernel.org/r/20220207180442.72836-1-jsmart2021@gmail.com
    Reviewed-by: Ewan D. Milne <emilne@redhat.com>
    Signed-off-by: James Smart <jsmart2021@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit c80b27cfd93ba9f5161383f798414609e84729f3
Author: James Smart <jsmart2021@gmail.com>
Date:   Mon Feb 7 10:05:16 2022 -0800

    scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled
    
    The driver is initiating NVMe PRLIs to determine device NVMe support.  This
    should not be occurring if CONFIG_NVME_FC support is disabled.
    
    Correct this by changing the default value for FC4 support. Currently it
    defaults to FCP and NVMe. With change, when NVME_FC support is not enabled
    in the kernel, the default value is just FCP.
    
    Link: https://lore.kernel.org/r/20220207180516.73052-1-jsmart2021@gmail.com
    Reviewed-by: Ewan D. Milne <emilne@redhat.com>
    Signed-off-by: James Smart <jsmart2021@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 1cf5f151d25fcca94689efd91afa0253621fb33a
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Feb 2 16:05:16 2022 -0700

    Makefile.extrawarn: Move -Wunaligned-access to W=1
    
    -Wunaligned-access is a new warning in clang that is default enabled for
    arm and arm64 under certain circumstances within the clang frontend (see
    LLVM commit below). On v5.17-rc2, an ARCH=arm allmodconfig build shows
    1284 total/70 unique instances of this warning (most of the instances
    are in header files), which is quite noisy.
    
    To keep a normal build green through CONFIG_WERROR, only show this
    warning with W=1, which will allow automated build systems to catch new
    instances of the warning so that the total number can be driven down to
    zero eventually since catching unaligned accesses at compile time would
    be generally useful.
    
    Cc: stable@vger.kernel.org
    Link: https://github.com/llvm/llvm-project/commit/35737df4dcd28534bd3090157c224c19b501278a
    Link: https://github.com/ClangBuiltLinux/linux/issues/1569
    Link: https://github.com/ClangBuiltLinux/linux/issues/1576
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 8a4c5b2a6d8ea079fa36034e8167de87ab6f8880
Author: Brenda Streiff <brenda.streiff@ni.com>
Date:   Fri Jan 28 16:01:28 2022 -0600

    kconfig: let 'shell' return enough output for deep path names
    
    The 'shell' built-in only returns the first 256 bytes of the command's
    output. In some cases, 'shell' is used to return a path; by bumping up
    the buffer size to 4096 this lets us capture up to PATH_MAX.
    
    The specific case where I ran into this was due to commit 1e860048c53e
    ("gcc-plugins: simplify GCC plugin-dev capability test"). After this
    change, we now use `$(shell,$(CC) -print-file-name=plugin)` to return
    a path; if the gcc path is particularly long, then the path ends up
    truncated at the 256 byte mark, which makes the HAVE_GCC_PLUGINS
    depends test always fail.
    
    Signed-off-by: Brenda Streiff <brenda.streiff@ni.com>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit fe4f57bf7b585dca58f1496c4e2481ecbae18126
Author: Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>
Date:   Sat Feb 5 23:39:32 2022 +0300

    net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs
    
    It is mandatory for a software to issue a reset upon modifying RGMII
    Receive Timing Control and RGMII Transmit Timing Control bit fields of MAC
    Specific Control register 2 (page 2, register 21) otherwise the changes
    won't be perceived by the PHY (the same is applicable for a lot of other
    registers). Not setting the RGMII delays on the platforms that imply it'
    being done on the PHY side will consequently cause the traffic loss. We
    discovered that the denoted soft-reset is missing in the
    m88e1121_config_aneg() method for the case if the RGMII delays are
    modified but the MDIx polarity isn't changed or the auto-negotiation is
    left enabled, thus causing the traffic loss on our platform with Marvell
    Alaska 88E1510 installed. Let's fix that by issuing the soft-reset if the
    delays have been actually set in the m88e1121_config_aneg_rgmii_delays()
    method.
    
    Cc: stable@vger.kernel.org
    Fixes: d6ab93364734 ("net: phy: marvell: Avoid unnecessary soft reset")
    Signed-off-by: Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Reviewed-by: Serge Semin <fancer.lancer@gmail.com>
    Link: https://lore.kernel.org/r/20220205203932.26899-1-Pavel.Parkhomenko@baikalelectronics.ru
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 555f3d7be91a873114c9656069f1a9fa476ec41a
Merge: 2ade8eef993c3 f9929ef6a2a55
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 7 15:25:50 2022 -0800

    Merge tag '5.17-rc3-ksmbd-server-fixes' of git://git.samba.org/ksmbd
    
    Pull ksmbd server fixes from Steve French:
    
     - NTLMSSP authentication improvement
    
     - RDMA (smbdirect) fix allowing broader set of NICs to be supported
    
     - improved buffer validation
    
     - additional small fixes, including a posix extensions fix for stable
    
    * tag '5.17-rc3-ksmbd-server-fixes' of git://git.samba.org/ksmbd:
      ksmbd: add support for key exchange
      ksmbd: reduce smb direct max read/write size
      ksmbd: don't align last entry offset in smb2 query directory
      ksmbd: fix same UniqueId for dot and dotdot entries
      ksmbd: smbd: validate buffer descriptor structures
      ksmbd: fix SMB 3.11 posix extension mount failure

commit ea85bf906466191b58532bb19f4fbb4591f0a77e
Author: Lorenzo Bianconi <lorenzo@kernel.org>
Date:   Sat Feb 5 22:57:42 2022 +0100

    iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
    
    We need to wait for sensor settling time (~ 3/ODR) before reading data
    in st_lsm6dsx_read_oneshot routine in order to avoid corrupted samples.
    
    Fixes: 290a6ce11d93 ("iio: imu: add support to lsm6dsx driver")
    Reported-by: Mario Tesi <mario.tesi@st.com>
    Tested-by: Mario Tesi <mario.tesi@st.com>
    Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
    Link: https://lore.kernel.org/r/b41ebda5535895298716c76d939f9f165fcd2d13.1644098120.git.lorenzo@kernel.org
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 2ade8eef993c37a2a43e51a9b1f6c25509a2acce
Merge: 51f7ea914d79a fda17afc6166e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 7 12:10:35 2022 -0800

    Merge tag 'ata-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ata fix from Damien Le Moal:
     "A single patch from me, to fix a bug that is causing boot issues in
      the field (reports of problems with Fedora 35).
    
      The bug affects mostly old-ish drives that have issues with read log
      page command handling"
    
    * tag 'ata-5.17-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: libata-core: Fix ata_dev_config_cpr()

commit cb1f65c1e1424a4b5e4a86da8aa3b8fd8459c8ec
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Fri Feb 4 18:35:22 2022 +0100

    PM: s2idle: ACPI: Fix wakeup interrupts handling
    
    After commit e3728b50cd9b ("ACPI: PM: s2idle: Avoid possible race
    related to the EC GPE") wakeup interrupts occurring immediately after
    the one discarded by acpi_s2idle_wake() may be missed.  Moreover, if
    the SCI triggers again immediately after the rearming in
    acpi_s2idle_wake(), that wakeup may be missed too.
    
    The problem is that pm_system_irq_wakeup() only calls pm_system_wakeup()
    when pm_wakeup_irq is 0, but that's not the case any more after the
    interrupt causing acpi_s2idle_wake() to run until pm_wakeup_irq is
    cleared by the pm_wakeup_clear() call in s2idle_loop().  However,
    there may be wakeup interrupts occurring in that time frame and if
    that happens, they will be missed.
    
    To address that issue first move the clearing of pm_wakeup_irq to
    the point at which it is known that the interrupt causing
    acpi_s2idle_wake() to tun will be discarded, before rearming the SCI
    for wakeup.  Moreover, because that only reduces the size of the
    time window in which the issue may manifest itself, allow
    pm_system_irq_wakeup() to register two second wakeup interrupts in
    a row and, when discarding the first one, replace it with the second
    one.  [Of course, this assumes that only one wakeup interrupt can be
    discarded in one go, but currently that is the case and I am not
    aware of any plans to change that.]
    
    Fixes: e3728b50cd9b ("ACPI: PM: s2idle: Avoid possible race related to the EC GPE")
    Cc: 5.4+ <stable@vger.kernel.org> # 5.4+
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit dc0075ba7f387fe4c48a8c674b11ab6f374a6acc
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Fri Feb 4 18:31:02 2022 +0100

    ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE
    
    Commit 4a9af6cac050 ("ACPI: EC: Rework flushing of EC work while
    suspended to idle") made acpi_ec_dispatch_gpe() check
    pm_wakeup_pending(), but that is before canceling the SCI wakeup,
    so pm_wakeup_pending() is always true.  This causes the loop in
    acpi_ec_dispatch_gpe() to always terminate after one iteration which
    may not be correct.
    
    Address this issue by canceling the SCI wakeup earlier, from
    acpi_ec_dispatch_gpe() itself.
    
    Fixes: 4a9af6cac050 ("ACPI: EC: Rework flushing of EC work while suspended to idle")
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit d6ebb17ccc7b37872a32bc25b4a21f1e5af8c7e3
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Fri Jan 28 14:35:03 2022 -0600

    ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"
    
    Testing on various upcoming OEM systems shows commit 7b167c4cb48e ("ACPI:
    PM: Only mark EC GPE for wakeup on Intel systems") was short
    sighted and the symptoms were indicative of other problems. Some OEMs
    do have the dedicated GPIOs for the power button but also rely upon
    an interrupt to the EC SCI to let the lid work.
    
    The original commit showed spurious activity on Lenovo systems:
         * On both Lenovo T14 and P14s the keyboard wakeup doesn't work, and
           sometimes the power button event doesn't work.
    
    This was confirmed on my end at that time.
    
    However further development in the kernel showed that the issue was
    actually the IRQ for the GPIO controller was also shared with the EC SCI.
    This was actually fixed by commit 2d54067fcd23 ("pinctrl: amd: Fix
    wakeups when IRQ is shared with SCI").
    
    The original commit also showed problems with AC adapter:
         * On HP 635 G7 detaching or attaching AC during suspend will cause
           the system not to wakeup
         * On Asus vivobook to prevent detaching AC causing resume problems
         * On Lenovo 14ARE05 to prevent detaching AC causing resume problems
         * On HP ENVY x360  to prevent detaching AC causing resume problems
    
    Detaching AC adapter causing problems appears to have been a problem
    because the EC SCI went off to notify the OS of the power adapter change
    but the SCI was ignored and there was no other way to wake up this system
    since GPIO controller wasn't properly enabled.  The wakeups were fixed by
    enabling the GPIO controller in commit acd47b9f28e5 ("pinctrl: amd: Handle
    wake-up interrupt").
    
    I've confirmed on a variety of OEM notebooks with the following test
    
     1) echo 1 | sudo tee /sys/power/pm_debug_messages
     2) sudo systemctl suspend
     3) unplug AC adapter, make sure system is still asleep
     4) wake system from lid (which is provided by ACPI SCI on some of them)
     5) dmesg
        a) see the EC GPE dispatched, timekeeping for X seconds (matching ~time
           until AC adapter plug out)
        b) see timekeeping for Y seconds until woke (matching ~time from AC
           adapter until lid event)
     6) Look at /sys/kernel/debug/amd_pmc/s0ix_stats
        "Time (in us) in S0i3" = X + Y - firmware processing time
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Tested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 51f7ea914d79aa44156dd63fe9e1cc75708d781d
Merge: c8ba56b7e8f3c bd2db32e7c3e3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 7 11:51:14 2022 -0800

    Merge tag 'mmc-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
    
    Pull MMC fixes from Ulf Hansson:
     "MMC core:
       - Fix support for SD Power off notification
    
      MMC host:
       - moxart: Fix potential use-after-free on remove path
       - sdhci-of-esdhc: Fix error path when setting dma mask
       - sh_mmcif: Fix potential NULL pointer dereference"
    
    * tag 'mmc-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc:
      moxart: fix potential use-after-free on remove path
      mmc: core: Wait for command setting 'Power Off Notification' bit to complete
      mmc: sh_mmcif: Check for null res pointer
      mmc: sdhci-of-esdhc: Check for error num after setting mask

commit 6bf625a4140f24b490766043b307f8252519578b
Author: Michael Kelley <mikelley@microsoft.com>
Date:   Sun Feb 6 11:36:56 2022 -0800

    Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64)
    
    Using DMA_BIT_MASK(64) as an initializer for a global variable
    causes problems with Clang 12.0.1. The compiler doesn't understand
    that value 64 is excluded from the shift at compile time, resulting
    in a build error.
    
    While this is a compiler problem, avoid the issue by setting up
    the dma_mask memory as part of struct hv_device, and initialize
    it using dma_set_mask().
    
    Reported-by: Nathan Chancellor <nathan@kernel.org>
    Reported-by: Vitaly Chikunov <vt@altlinux.org>
    Reported-by: Jakub Kicinski <kuba@kernel.org>
    Fixes: 743b237c3a7b ("scsi: storvsc: Add Isolation VM support for storvsc driver")
    Signed-off-by: Michael Kelley <mikelley@microsoft.com>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lore.kernel.org/r/1644176216-12531-1-git-send-email-mikelley@microsoft.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit c8ba56b7e8f3ca4d86c556f5498e4faeb6d139ec
Merge: dfd42facf1e4a 89677197ae709
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Feb 7 09:55:14 2022 -0800

    Merge tag 'integrity-v5.17-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
    
    Pull integrity fixes from Mimi Zohar:
     "Fixes for recently found bugs.
    
      One was found/noticed while reviewing IMA support for fsverity digests
      and signatures. Two of them were found/noticed while working on IMA
      namespacing. Plus two other bugs.
    
      All of them are for previous kernel releases"
    
    * tag 'integrity-v5.17-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity:
      ima: Do not print policy rule with inactive LSM labels
      ima: Allow template selection with ima_template[_fmt]= after ima_hash=
      ima: Remove ima_policy file before directory
      integrity: check the return value of audit_log_start()
      ima: fix reference leak in asymmetric_verify()

commit 8bc69f86328e87a0ffa79438430cc82f3aa6a194
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Feb 4 01:30:08 2022 +0800

    Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj
    
    kobject_init_and_add() takes reference even when it fails.
    According to the doc of kobject_init_and_add()：
    
       If this function returns an error, kobject_put() must be called to
       properly clean up the memory associated with the object.
    
    Fix memory leak by calling kobject_put().
    
    Fixes: c2e5df616e1a ("vmbus: add per-channel sysfs info")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Juan Vazquez <juvazq@linux.microsoft.com>
    Link: https://lore.kernel.org/r/20220203173008.43480-1-linmq006@gmail.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit 7eabedfb2903493d2601fd224f1e027cd1860fa0
Merge: 486343d3728be e6b03375132fe
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Mon Feb 7 17:45:06 2022 +0100

    Merge branch 'v5.17/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux into arm/fixes
    
    * 'v5.17/fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux:
      arm64: dts: meson-sm1-odroid: fix boot loop after reboot
      arm64: dts: meson-g12: drop BL32 region from SEI510/SEI610
      arm64: dts: meson-g12: add ATF BL32 reserved-memory region
      arm64: dts: meson-gx: add ATF BL32 reserved-memory region
      arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO domain for GPIOE_2
      arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator
      arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133'
    
    Link: https://lore.kernel.org/r/67888f6a-f4ff-9569-131a-0c7baba6ddaf@baylibre.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 486343d3728be741db13854dc7e983c20cdd7c07
Merge: 63a8728579a8d 31aa7056bbec0
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Mon Feb 7 17:42:43 2022 +0100

    Merge tag 'omap-for-v5.17/fixes-for-merge-window-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes
    
    Fixes for omaps
    
    A series of fixes for omap variants for minor issues, and a fix for a timer
    regression for some omap3 beagleboard versions.
    
    The timer fix needs to patch both the dts and the timer code because
    otherwise the timer quirk handling for old dtbs will prevent the dts fix
    from working.
    
    The other changes are for issues found by automated analysis, a macasp
    typo fix, and two cosmetic fixes for clocks.
    
    * tag 'omap-for-v5.17/fixes-for-merge-window-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
      ARM: dts: Don't use legacy clock defines for dra7 clkctrl
      clk: ti: Move dra7 clock devices out of the legacy section
      ARM: dts: Fix timer regression for beagleboard revision c
      ARM: dts: am335x-wega: Fix typo in mcasp property rx-num-evt
      ARM: OMAP2+: adjust the location of put_device() call in omapdss_init_of
      ARM: OMAP2+: hwmod: Add of_node_put() before break
    
    Link: https://lore.kernel.org/r/pull-1641801310-149268@atomide.com
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 0a3f1e0beacf6cc8ae5f846b0641c1df476e83d6
Author: Shakeel Butt <shakeelb@google.com>
Date:   Mon Jan 24 21:17:36 2022 -0800

    mm: io_uring: allow oom-killer from io_uring_setup
    
    On an overcommitted system which is running multiple workloads of
    varying priorities, it is preferred to trigger an oom-killer to kill a
    low priority workload than to let the high priority workload receiving
    ENOMEMs. On our memory overcommitted systems, we are seeing a lot of
    ENOMEMs instead of oom-kills because io_uring_setup callchain is using
    __GFP_NORETRY gfp flag which avoids the oom-killer. Let's remove it and
    allow the oom-killer to kill a lower priority job.
    
    Signed-off-by: Shakeel Butt <shakeelb@google.com>
    Link: https://lore.kernel.org/r/20220125051736.2981459-1-shakeelb@google.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 0d7c1153d9291197c1dc473cfaade77acb874b4b
Author: Alviro Iskandar Setiawan <alviro.iskandar@gmail.com>
Date:   Mon Feb 7 21:05:33 2022 +0700

    io_uring: Clean up a false-positive warning from GCC 9.3.0
    
    In io_recv(), if import_single_range() fails, the @flags variable is
    uninitialized, then it will goto out_free.
    
    After the goto, the compiler doesn't know that (ret < min_ret) is
    always true, so it thinks the "if ((flags & MSG_WAITALL) ..."  path
    could be taken.
    
    The complaint comes from gcc-9 (Debian 9.3.0-22) 9.3.0:
    ```
      fs/io_uring.c:5238 io_recvfrom() error: uninitialized symbol 'flags'
    ```
    Fix this by bypassing the @ret and @flags check when
    import_single_range() fails.
    
    Reasons:
     1. import_single_range() only returns -EFAULT when it fails.
     2. At that point, @flags is uninitialized and shouldn't be read.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reported-by: "Chen, Rong A" <rong.a.chen@intel.com>
    Link: https://lore.gnuweeb.org/timl/d33bb5a9-8173-f65b-f653-51fc0681c6d6@intel.com/
    Cc: Pavel Begunkov <asml.silence@gmail.com>
    Suggested-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
    Fixes: 7297ce3d59449de49d3c9e1f64ae25488750a1fc ("io_uring: improve send/recv error handling")
    Signed-off-by: Alviro Iskandar Setiawan <alviro.iskandar@gmail.com>
    Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
    Link: https://lore.kernel.org/r/20220207140533.565411-1-ammarfaizi2@gnuweeb.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 18a1d5e1945385d9b5adc3fe11427ce4a9d2826e
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Mon Feb 7 17:16:39 2022 +0200

    parisc: Add ioread64_lo_hi() and iowrite64_lo_hi()
    
    It's a followup to the previous commit f15309d7ad5d ("parisc: Add
    ioread64_hi_lo() and iowrite64_hi_lo()") which does only half of
    the job. Add the rest, so we won't get a new kernel test robot
    reports.
    
    Fixes: f15309d7ad5d ("parisc: Add ioread64_hi_lo() and iowrite64_hi_lo()")
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 63a8728579a8dc2cf3af6a56689eb1078a9946a5
Merge: 60f40305529b3 aceeafefff736
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Mon Feb 7 16:10:59 2022 +0100

    Merge tag 'optee-fix-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee into arm/fixes
    
    OP-TEE fix shutdown problems
    
    * tag 'optee-fix-for-v5.17' of git://git.linaro.org/people/jens.wiklander/linux-tee:
      optee: use driver internal tee_context for some rpc
    
    Link: https://lore.kernel.org/r/20220203132323.GA4132001@jade
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit 9495b9b31abe525ebd93da58de2c88b9f66d3a0e
Author: Eric Anholt <eric@anholt.net>
Date:   Fri Feb 23 22:42:31 2018 +0100

    i2c: bcm2835: Avoid clock stretching timeouts
    
    The CLKT register contains at poweron 0x40, which at our typical 100kHz
    bus rate means .64ms. But there is no specified limit to how long devices
    should be able to stretch the clocks, so just disable the timeout. We
    still have a timeout wrapping the entire transfer.
    
    Signed-off-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
    BugLink: https://github.com/raspberrypi/linux/issues/3064
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit 60f40305529b38d6c3903bd833dc25e39b94e5b6
Author: Philippe Cornu <philippe.cornu@foss.st.com>
Date:   Thu Jan 13 18:19:21 2022 +0100

    MAINTAINERS: update drm/stm drm/sti and cec/sti maintainers
    
    Add Alain as sti maintainer for both drm/sti & cec/sti.
    Add Raphaël as stm maintainer for drm/stm.
    
    Signed-off-by: Philippe Cornu <philippe.cornu@foss.st.com>
    Reviewed-by: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
    Reviewed-by: Alain Volmat <alain.volmat@foss.st.com>
    Link: https://lore.kernel.org/r/20220113171921.17466-3-philippe.cornu@foss.st.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit bf5bdcc9f262b5afd3c0f06c39b34b4f2fcff661
Author: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Date:   Thu Jan 13 18:19:20 2022 +0100

    MAINTAINERS: Update Benjamin Gaignard maintainer status
    
    Update Benjamin Gaignard address and remove it from no more maintained
    drivers.
    
    Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
    Reviewed-by: Philippe Cornu <philippe.cornu@foss.st.com>
    Link: https://lore.kernel.org/r/20220113171921.17466-2-philippe.cornu@foss.st.com'
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

commit fda17afc6166e975bec1197bd94cd2a3317bce3f
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Mon Feb 7 11:27:53 2022 +0900

    ata: libata-core: Fix ata_dev_config_cpr()
    
    The concurrent positioning ranges log page 47h is a general purpose log
    page and not a subpage of the indentify device log. Using
    ata_identify_page_supported() to test for concurrent positioning ranges
    support is thus wrong. ata_log_supported() must be used.
    
    Furthermore, unlike other advanced ATA features (e.g. NCQ priority),
    accesses to the concurrent positioning ranges log page are not gated by
    a feature bit from the device IDENTIFY data. Since many older drives
    react badly to the READ LOG EXT and/or READ LOG DMA EXT commands isued
    to read device log pages, avoid problems with older drives by limiting
    the concurrent positioning ranges support detection to drives
    implementing at least the ACS-4 ATA standard (major version 11). This
    additional condition effectively turns ata_dev_config_cpr() into a nop
    for older drives, avoiding problems in the field.
    
    Fixes: fe22e1c2f705 ("libata: support concurrent positioning ranges log")
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215519
    Cc: stable@vger.kernel.org
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Tested-by: Abderraouf Adjal <adjal.arf@gmail.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 200e8e3e43c4da4bd5ca83722523754ddb14ca02
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Feb 7 14:04:07 2022 +0100

    drm/privacy-screen: Fix sphinx warning
    
    Fix the following warning from "make htmldocs":
    
    drivers/gpu/drm/drm_privacy_screen.c:270:
     WARNING: Inline emphasis start-string without end-string.
    
    Fixes: 8a12b170558a ("drm/privacy-screen: Add notifier support (v2)")
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reviewed-by: Simon Ser <contact@emersion.fr>
    Link: https://lore.kernel.org/r/20220207130407.389585-1-hdegoede@redhat.com
    Link: https://patchwork.freedesktop.org/patch/msgid/20220207130407.389585-1-hdegoede@redhat.com

commit 4e6f55120c7eccf6f9323bb681632e23cbcb3f3c
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Feb 4 16:18:18 2022 +0200

    drm/i915: Workaround broken BIOS DBUF configuration on TGL/RKL
    
    On TGL/RKL the BIOS likes to use some kind of bogus DBUF layout
    that doesn't match what the spec recommends. With a single active
    pipe that is not going to be a problem, but with multiple pipes
    active skl_commit_modeset_enables() goes into an infinite loop
    since it can't figure out any order in which it can commit the
    pipes without causing DBUF overlaps between the planes.
    
    We'd need some kind of extra DBUF defrag stage in between to
    make the transition possible. But that is clearly way too complex
    a solution, so in the name of simplicity let's just sanitize the
    DBUF state by simply turning off all planes when we detect a
    pipe encroaching on its neighbours' DBUF slices. We only have
    to disable the primary planes as all other planes should have
    already been disabled (if they somehow were enabled) by
    earlier sanitization steps.
    
    And for good measure let's also sanitize in case the DBUF
    allocations of the pipes already seem to overlap each other.
    
    Cc: <stable@vger.kernel.org> # v5.14+
    Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4762
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220204141818.1900-3-ville.syrjala@linux.intel.com
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    (cherry picked from commit 15512021eb3975a8c2366e3883337e252bb0eee5)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 85bb289215cf37e05e9581b39b114db1293f9ecd
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Feb 4 16:18:17 2022 +0200

    drm/i915: Populate pipe dbuf slices more accurately during readout
    
    During readout we cannot assume the planes are actually using the
    slices they are supposed to use. The BIOS may have misprogrammed
    things and put the planes onto the wrong dbuf slices. So let's
    do the readout more carefully to make sure we really know which
    dbuf slices are actually in use by the pipe at the time.
    
    Cc: <stable@vger.kernel.org> # v5.14+
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220204141818.1900-2-ville.syrjala@linux.intel.com
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    (cherry picked from commit b3dcc6dc0f32612d04839c2fb32e94d0ebf92c98)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 8fd5a26e43859547790a7995494c952b708ab3b5
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Feb 4 16:18:16 2022 +0200

    drm/i915: Allow !join_mbus cases for adlp+ dbuf configuration
    
    Reintroduce the !join_mbus single pipe cases for adlp+.
    
    Due to the mbus relative dbuf offsets in PLANE_BUF_CFG we
    need to know the actual slices used by the pipe when doing
    readout, even when mbus joining isn't enabled. Accurate
    readout will be needed to properly sanitize invalid BIOS
    dbuf configurations.
    
    This will also make it much easier to play around with the
    !join_mbus configs for testin/workaround purposes.
    
    Cc: <stable@vger.kernel.org> # v5.14+
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220204141818.1900-1-ville.syrjala@linux.intel.com
    Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
    (cherry picked from commit eef173954432fe0612acb63421a95deb41155cdc)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 9d7516b16f2a7ecbddd7940e582c78fcdc9136ef
Author: Lucas De Marchi <lucas.demarchi@intel.com>
Date:   Mon Jan 31 08:59:25 2022 -0800

    drm/i915: Fix header test for !CONFIG_X86
    
    Architectures others than x86 have a stub implementation calling
    WARN_ON_ONCE(). The appropriate headers need to be included, otherwise
    the header-test target will fail with:
    
      HDRTEST drivers/gpu/drm/i915/i915_mm.h
    In file included from <command-line>:
    ./drivers/gpu/drm/i915/i915_mm.h: In function ‘remap_io_mapping’:
    ./drivers/gpu/drm/i915/i915_mm.h:26:2: error: implicit declaration of function ‘WARN_ON_ONCE’ [-Werror=implicit-function-declaration]
       26 |  WARN_ON_ONCE(1);
          |  ^~~~~~~~~~~~
    
    v2: Do not include <linux/printk.h> since call to pr_err() has been
    removed
    
    Fixes: 67c430bbaae1 ("drm/i915: Skip remap_io_mapping() for non-x86 platforms")
    Cc: Siva Mullati <siva.mullati@intel.com>
    Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
    Reviewed-by: Siva Mullati <siva.mullati@intel.com>
    Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220131165926.3230642-3-lucas.demarchi@intel.com
    (cherry picked from commit 377c675f3c17ffaefd023ee283bb366bbd6bbcea)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 3526b607b02397cdb6d459594e4f1d63133d6655
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Date:   Tue Feb 1 08:03:40 2022 +0100

    drm/i915/ttm: Return some errors instead of trying memcpy move
    
    The i915_ttm_accel_move() function may return error codes that should
    be propagated further up the stack rather than consumed assuming that
    the accel move failed and could be replaced with a memcpy move.
    
    For -EINTR, -ERESTARTSYS and -EAGAIN, just propagate those codes, rather
    than retrying with a memcpy move.
    
    Fixes: 2b0a750caf33 ("drm/i915/ttm: Failsafe migration blits")
    Cc: Matthew Auld <matthew.auld@intel.com>
    Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Matthew Auld <matthew.auld@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220201070340.16457-1-thomas.hellstrom@linux.intel.com
    (cherry picked from commit 29b9702ffe70d83b9970abbccaeb287dfda4409f)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit ee59792c97176f12c1da31f29fc4c2aab187f06e
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Jan 28 12:37:50 2022 +0200

    drm/i915: Disable DRRS on IVB/HSW port != A
    
    Currently we allow DRRS on IVB PCH ports, but we're missing a
    few programming steps meaning it is guaranteed to not work.
    And on HSW DRRS is not supported on anything but port A ever
    as only transcoder EDP has the M2/N2 registers (though I'm
    not sure if HSW ever has eDP on any other port).
    
    Starting from BDW all transcoders have the dynamically
    reprogrammable M/N registers so DRRS could work on any
    port.
    
    Stop initializing DRRS on ports where it cannot possibly work.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220128103757.22461-11-ville.syrjala@linux.intel.com
    Reviewed-by: Jani Nikula <jani.nikula@intel.com>
    (cherry picked from commit f0d4ce59f4d48622044933054a0e0cefa91ba15e)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit eb48d42198792f1330bbb3e82ac725d43c13fe02
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Wed Jan 26 10:15:38 2022 +0200

    drm/i915: Fix oops due to missing stack depot
    
    We call __save_depot_stack() unconditionally so the stack depot
    must always be initialized or else we'll oops on platforms without
    runtime pm support.
    
    Presumably we've not seen this in CI due to stack_depot_init()
    already getting called via drm_mm_init()+CONFIG_DRM_DEBUG_MM.
    
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Marco Elver <elver@google.com> # stackdepot
    Cc: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Imre Deak <imre.deak@intel.com>
    Fixes: 2dba5eb1c73b ("lib/stackdepot: allow optional init and stack_table allocation by kvmalloc()")
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220126081539.23227-1-ville.syrjala@linux.intel.com
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Imre Deak <imre.deak@intel.com>
    (cherry picked from commit 751a9d69b19702af35b0fedfb8ff362027c1cf0c)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 94fdd7c02a56d0316d20e417a1141b71a8dcee82
Author: Eric Dumazet <edumazet@google.com>
Date:   Sun Feb 6 06:33:48 2022 -0800

    net/smc: use GFP_ATOMIC allocation in smc_pnet_add_eth()
    
    My last patch moved the netdev_tracker_alloc() call to a section
    protected by a write_lock().
    
    I should have replaced GFP_KERNEL with GFP_ATOMIC to avoid the infamous:
    
    BUG: sleeping function called from invalid context at include/linux/sched/mm.h:256
    
    Fixes: 28f922213886 ("net/smc: fix ref_tracker issue in smc_pnet_add()")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit fc764b103b81ebe88f69f9ae4f116551ab8cfc5d
Author: Maxime Ripard <maxime@cerno.tech>
Date:   Thu Feb 3 16:11:51 2022 +0100

    drm/vc4: crtc: Fix redundant variable assignment
    
    The variable is assigned twice to the same value. Let's drop one.
    
    Reported-by: kernel test robot <yujie.liu@intel.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220203151151.1270461-1-maxime@cerno.tech

commit 3037b174b1876aae6b2d1a27a878c681c78ccadc
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Mon Feb 7 09:44:04 2022 +0100

    ARM: socfpga: fix missing RESET_CONTROLLER
    
    The SocFPGA machine since commit b3ca9888f35f ("reset: socfpga: add an
    early reset driver for SoCFPGA") uses reset controller, so it should
    select RESET_CONTROLLER explicitly.  Selecting ARCH_HAS_RESET_CONTROLLER
    is not enough because it affects only default choice still allowing a
    non-buildable configuration:
    
      /usr/bin/arm-linux-gnueabi-ld: arch/arm/mach-socfpga/socfpga.o: in function `socfpga_init_irq':
      arch/arm/mach-socfpga/socfpga.c:56: undefined reference to `socfpga_reset_init'
    
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: <stable@vger.kernel.org>
    Fixes: b3ca9888f35f ("reset: socfpga: add an early reset driver for SoCFPGA")
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>

commit 9bb162fa26ed76031ed0e7dbc77ccea0bf977758
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Tue Dec 7 06:10:05 2021 +0000

    powerpc/603: Fix boot failure with DEBUG_PAGEALLOC and KFENCE
    
    Allthough kernel text is always mapped with BATs, we still have
    inittext mapped with pages, so TLB miss handling is required
    when CONFIG_DEBUG_PAGEALLOC or CONFIG_KFENCE is set.
    
    The final solution should be to set a BAT that also maps inittext
    but that BAT then needs to be cleared at end of init, and it will
    require more changes to be able to do it properly.
    
    As DEBUG_PAGEALLOC or KFENCE are debugging, performance is not a big
    deal so let's fix it simply for now to enable easy stable application.
    
    Fixes: 035b19a15a98 ("powerpc/32s: Always map kernel text and rodata with BATs")
    Cc: stable@vger.kernel.org # v5.11+
    Reported-by: Maxime Bizon <mbizon@freebox.fr>
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/aea33b4813a26bdb9378b5f273f00bd5d4abe240.1638857364.git.christophe.leroy@csgroup.eu

commit d0cbe56a7d5ac170f6cf3757ef5a14dd854e7da9
Author: Steve French <stfrench@microsoft.com>
Date:   Sun Feb 6 18:59:57 2022 -0600

    [smb3] improve error message when mount options conflict with posix
    
    POSIX extensions require SMB3.1.1 (so improve the error
    message when vers=3.0, 2.1 or 2.0 is specified on mount)
    
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e286f231eab410793f3e91c924e6dbd23edee05a
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date:   Mon Jan 31 14:17:11 2022 +0100

    s390/module: fix building test_modules_helpers.o with clang
    
    Move test_modules_return_* prototypes into a header file in order to
    placate -Wmissing-prototypes.
    
    Fixes: 90c5318795ee ("s390/module: test loading modules with a lot of relocations")
    Reported-by: kernel test robot <lkp@intel.com>
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 72fc40931d7a488e1646d04f988f4d5a97b02100
Author: Christian Borntraeger <borntraeger@linux.ibm.com>
Date:   Thu Jan 27 15:24:49 2022 +0100

    MAINTAINERS: downgrade myself to Reviewer for s390
    
    Now that Alexander Gordeev has volunteered to be a co-maintainer for
    s390, I can act as a reviewer instead of being a maintainer for s390.
    With Alexander, Heiko, and Vasily we are in really good shape.
    I will continue to act as the maintainer for KVM on s390 together with
    Janosch.
    
    Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
    Acked-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 4f9e67f5e03ab92ecbe51399a8cc55968106e8f9
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Thu Jan 27 15:06:31 2022 +0100

    MAINTAINERS: add Alexander Gordeev as maintainer for s390
    
    Change Alexander Gordeev's status so he is maintainer
    instead of reviewer for s390.
    
    Acked-by: Alexander Gordeev <agordeev@linux.ibm.com>
    Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
    Acked-by: Sven Schnelle <svens@linux.ibm.com>
    Acked-by: Vasily Gorbik <gor@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 5f4e5ce638e6a490b976ade4a40017b40abb2da0
Author: Song Liu <song@kernel.org>
Date:   Thu Feb 3 16:40:57 2022 -0800

    perf: Fix list corruption in perf_cgroup_switch()
    
    There's list corruption on cgrp_cpuctx_list. This happens on the
    following path:
    
      perf_cgroup_switch: list_for_each_entry(cgrp_cpuctx_list)
          cpu_ctx_sched_in
             ctx_sched_in
                ctx_pinned_sched_in
                  merge_sched_in
                      perf_cgroup_event_disable: remove the event from the list
    
    Use list_for_each_entry_safe() to allow removing an entry during
    iteration.
    
    Fixes: 058fe1c0440e ("perf/core: Make cgroup switch visit only cpuctxs with cgroup events")
    Signed-off-by: Song Liu <song@kernel.org>
    Reviewed-by: Rik van Riel <riel@surriel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/20220204004057.2961252-1-song@kernel.org

commit 13765de8148f71fa795e0a6607de37c49ea5915a
Author: Tadeusz Struk <tadeusz.struk@linaro.org>
Date:   Thu Feb 3 08:18:46 2022 -0800

    sched/fair: Fix fault in reweight_entity
    
    Syzbot found a GPF in reweight_entity. This has been bisected to
    commit 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an invalid
    sched_task_group")
    
    There is a race between sched_post_fork() and setpriority(PRIO_PGRP)
    within a thread group that causes a null-ptr-deref in
    reweight_entity() in CFS. The scenario is that the main process spawns
    number of new threads, which then call setpriority(PRIO_PGRP, 0, -20),
    wait, and exit.  For each of the new threads the copy_process() gets
    invoked, which adds the new task_struct and calls sched_post_fork()
    for it.
    
    In the above scenario there is a possibility that
    setpriority(PRIO_PGRP) and set_one_prio() will be called for a thread
    in the group that is just being created by copy_process(), and for
    which the sched_post_fork() has not been executed yet. This will
    trigger a null pointer dereference in reweight_entity(), as it will
    try to access the run queue pointer, which hasn't been set.
    
    Before the mentioned change the cfs_rq pointer for the task  has been
    set in sched_fork(), which is called much earlier in copy_process(),
    before the new task is added to the thread_group.  Now it is done in
    the sched_post_fork(), which is called after that.  To fix the issue
    the remove the update_load param from the update_load param() function
    and call reweight_task() only if the task flag doesn't have the
    TASK_NEW flag set.
    
    Fixes: 4ef0c5c6b5ba ("kernel/sched: Fix sched_fork() access an invalid sched_task_group")
    Reported-by: syzbot+af7a719bc92395ee41b3@syzkaller.appspotmail.com
    Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Cc: stable@vger.kernel.org
    Link: https://lkml.kernel.org/r/20220203161846.1160750-1-tadeusz.struk@linaro.org

commit dfd42facf1e4ada021b939b4e19c935dcdd55566
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 12:20:50 2022 -0800

    Linux 5.17-rc3

commit d8ad2ce873abab1cfd38779c626b79cef6307aac
Merge: 18118a4298fd7 f340b3d902748
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 10:34:45 2022 -0800

    Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
    
    Pull ext4 fixes from Ted Ts'o:
     "Various bug fixes for ext4 fast commit and inline data handling.
    
      Also fix regression introduced as part of moving to the new mount API"
    
    * tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
      fs/ext4: fix comments mentioning i_mutex
      ext4: fix incorrect type issue during replay_del_range
      jbd2: fix kernel-doc descriptions for jbd2_journal_shrink_{scan,count}()
      ext4: fix potential NULL pointer dereference in ext4_fill_super()
      jbd2: refactor wait logic for transaction updates into a common function
      jbd2: cleanup unused functions declarations from jbd2.h
      ext4: fix error handling in ext4_fc_record_modified_inode()
      ext4: remove redundant max inline_size check in ext4_da_write_inline_data_begin()
      ext4: fix error handling in ext4_restore_inline_data()
      ext4: fast commit may miss file actions
      ext4: fast commit may not fallback for ineligible commit
      ext4: modify the logic of ext4_mb_new_blocks_simple
      ext4: prevent used blocks from being allocated during fast commit replay

commit 18118a4298fd7b0d686ef61be6f2622a77f51b96
Merge: c3bf8a14408ad fceb62124d8fe
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 10:18:23 2022 -0800

    Merge tag 'perf-tools-fixes-for-v5.17-2022-02-06' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tools fixes from Arnaldo Carvalho de Melo:
    
     - Fix display of grouped aliased events in 'perf stat'.
    
     - Add missing branch_sample_type to perf_event_attr__fprintf().
    
     - Apply correct label to user/kernel symbols in branch mode.
    
     - Fix 'perf ftrace' system_wide tracing, it has to be set before
       creating the maps.
    
     - Return error if procfs isn't mounted for PID namespaces when
       synthesizing records for pre-existing processes.
    
     - Set error stream of objdump process for 'perf annotate' TUI, to avoid
       garbling the screen.
    
     - Add missing arm64 support to perf_mmap__read_self(), the kernel part
       got into 5.17.
    
     - Check for NULL pointer before dereference writing debug info about a
       sample.
    
     - Update UAPI copies for asound, perf_event, prctl and kvm headers.
    
     - Fix a typo in bpf_counter_cgroup.c.
    
    * tag 'perf-tools-fixes-for-v5.17-2022-02-06' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf ftrace: system_wide collection is not effective by default
      libperf: Add arm64 support to perf_mmap__read_self()
      tools include UAPI: Sync sound/asound.h copy with the kernel sources
      perf stat: Fix display of grouped aliased events
      perf tools: Apply correct label to user/kernel symbols in branch mode
      perf bpf: Fix a typo in bpf_counter_cgroup.c
      perf synthetic-events: Return error if procfs isn't mounted for PID namespaces
      perf session: Check for NULL pointer before dereference
      perf annotate: Set error stream of objdump process for TUI
      perf tools: Add missing branch_sample_type to perf_event_attr__fprintf()
      tools headers UAPI: Sync linux/kvm.h with the kernel sources
      tools headers UAPI: Sync linux/prctl.h with the kernel sources
      perf beauty: Make the prctl arg regexp more strict to cope with PR_SET_VMA
      tools headers cpufeatures: Sync with the kernel sources
      tools headers UAPI: Sync linux/perf_event.h with the kernel sources
      tools include UAPI: Sync sound/asound.h copy with the kernel sources

commit c3bf8a14408ad2b84fe48246fa66d1459480ee6b
Merge: aeabe1e0744d1 1d9093457b243
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 10:11:14 2022 -0800

    Merge tag 'perf_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull perf fixes from Borislav Petkov:
    
     - Intel/PT: filters could crash the kernel
    
     - Intel: default disable the PMU for SMM, some new-ish EFI firmware has
       started using CPL3 and the PMU CPL filters don't discriminate against
       SMM, meaning that CPL3 (userspace only) events now also count EFI/SMM
       cycles.
    
     - Fixup for perf_event_attr::sig_data
    
    * tag 'perf_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      perf/x86/intel/pt: Fix crash with stop filters in single-range mode
      perf: uapi: Document perf_event_attr::sig_data truncation on 32 bit architectures
      selftests/perf_events: Test modification of perf_event_attr::sig_data
      perf: Copy perf_event_attr::sig_data on modification
      x86/perf: Default set FREEZE_ON_SMI for all

commit aeabe1e0744d1794246a909d2c042e9129fe22bd
Merge: b72e40b192f21 82880283d7fcd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 10:04:43 2022 -0800

    Merge tag 'objtool_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull objtool fix from Borislav Petkov:
     "Fix a potential truncated string warning triggered by gcc12"
    
    * tag 'objtool_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      objtool: Fix truncated string warning

commit b72e40b192f21f172a152ecb5905d22928bea2a3
Merge: 898b5841ae37c dd7f5a11ac5a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 10:00:40 2022 -0800

    Merge tag 'irq_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq fix from Borislav Petkov:
     "Remove a bogus warning introduced by the recent PCI MSI irq affinity
      overhaul"
    
    * tag 'irq_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      PCI/MSI: Remove bogus warning in pci_irq_get_affinity()

commit 898b5841ae37c8a7297214b7fd001d4c0f6fd89d
Merge: 90c9e950c0def dfd0dfb9a7cc0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Feb 6 09:57:39 2022 -0800

    Merge tag 'edac_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras
    
    Pull EDAC fixes from Borislav Petkov:
     "Fix altera and xgene EDAC drivers to propagate the correct error code
      from platform_get_irq() so that deferred probing still works"
    
    * tag 'edac_urgent_for_v5.17_rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras:
      EDAC/xgene: Fix deferred probing
      EDAC/altera: Fix deferred probing

commit fceb62124d8fe1f6fb4b64e8f11c095dca8e7ea7
Author: Changbin Du <changbin.du@intel.com>
Date:   Thu Jan 27 21:20:10 2022 +0800

    perf ftrace: system_wide collection is not effective by default
    
    The ftrace.target.system_wide must be set before invoking
    evlist__create_maps(), otherwise it has no effect.
    
    Fixes: 53be50282269b46c ("perf ftrace: Add 'latency' subcommand")
    Signed-off-by: Changbin Du <changbin.du@gmail.com>
    Acked-by: Namhyung Kim <namhyung@gmail.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20220127132010.4836-1-changbin.du@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 05daa805a86c831ad9692f6f15e1b877c8f10638
Author: Slark Xiao <slark_xiao@163.com>
Date:   Sat Feb 5 19:27:31 2022 +0530

    bus: mhi: pci_generic: Add mru_default for Cinterion MV31-W
    
    For default mechanism, product would use default MRU 3500 if
    they didn't define it. But for Cinterion MV31-W, there is a known
    issue which MRU 3500 would lead to data connection lost.
    So we align it with Qualcomm default MRU settings.
    
    Link: https://lore.kernel.org/r/20220119102519.5342-1-slark_xiao@163.com
    [mani: Modified the commit message to reflect Cinterion MV31-W and CCed stable]
    Fixes: 87693e092bd0 ("bus: mhi: pci_generic: Add Cinterion MV31-W PCIe to MHI")
    Cc: stable@vger.kernel.org # v5.14 +
    Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
    Signed-off-by: Slark Xiao <slark_xiao@163.com>
    Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
    Link: https://lore.kernel.org/r/20220205135731.157871-3-manivannan.sadhasivam@linaro.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a0572cea8866230ac13da6358c88075f89e99b20
Author: Slark Xiao <slark_xiao@163.com>
Date:   Sat Feb 5 19:27:30 2022 +0530

    bus: mhi: pci_generic: Add mru_default for Foxconn SDX55
    
    For default mechanism, product would use default MRU 3500 if
    they didn't define it. But for Foxconn SDX55, there is a known
    issue which MRU 3500 would lead to data connection lost.
    So we align it with Qualcomm default MRU settings.
    
    Link: https://lore.kernel.org/r/20220119101213.5008-1-slark_xiao@163.com
    [mani: Added pci_generic prefix to subject and CCed stable]
    Fixes: aac426562f56 ("bus: mhi: pci_generic: Introduce Foxconn T99W175 support")
    Cc: stable@vger.kernel.org # v5.12+
    Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
    Signed-off-by: Slark Xiao <slark_xiao@163.com>
    Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
    Link: https://lore.kernel.org/r/20220205135731.157871-2-manivannan.sadhasivam@linaro.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 407eb43ae87c969d98746c3274ae5d0f977b102e
Author: Rob Herring <robh@kernel.org>
Date:   Tue Feb 1 15:40:56 2022 -0600

    libperf: Add arm64 support to perf_mmap__read_self()
    
    Add the arm64 variants for read_perf_counter() and read_timestamp().
    Unfortunately the counter number is encoded into the instruction, so the
    code is a bit verbose to enumerate all possible counters.
    
    Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Jiri Olsa <jolsa@redhat.com>
    Tested-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Link: https://lore.kernel.org/r/20220201214056.702854-1-robh@kernel.org
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Will Deacon <will@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-perf-users@vger.kernel.org

commit 4f2492731ada9d702ffdfaa6ec1ff64820a1664c
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Feb 12 11:04:23 2020 -0300

    tools include UAPI: Sync sound/asound.h copy with the kernel sources
    
    Picking the changes from:
    
      06feec6005c9d950 ("ASoC: hdmi-codec: Fix OOB memory accesses")
    
    Which entails no changes in the tooling side as it doesn't introduce new
    SNDRV_PCM_IOCTL_ ioctls.
    
    To silence this perf tools build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/sound/asound.h' differs from latest version at 'include/uapi/sound/asound.h'
      diff -u tools/include/uapi/sound/asound.h include/uapi/sound/asound.h
    
    Cc: Dmitry Osipenko <digetx@gmail.com>
    Cc: Mark Brown <broonie@kernel.org>
    Cc: Takashi Iwai <tiwai@suse.de>
    Link: https://lore.kernel.org/lkml/Yf+6OT+2eMrYDEeX@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b2b1aa73ade982c175ac926a1fd34e76ad628b94
Author: Ian Rogers <irogers@google.com>
Date:   Fri Feb 4 17:09:41 2022 -0800

    perf stat: Fix display of grouped aliased events
    
    An event may have a number of uncore aliases that when added to the
    evlist are consecutive.
    
    If there are multiple uncore events in a group then
    parse_events__set_leader_for_uncore_aliase will reorder the evlist so
    that events on the same PMU are adjacent.
    
    The collect_all_aliases function assumes that aliases are in blocks so
    that only the first counter is printed and all others are marked merged.
    
    The reordering for groups breaks the assumption and so all counts are
    printed.
    
    This change removes the assumption from collect_all_aliases
    that the events are in blocks and instead processes the entire evlist.
    
    Before:
    
      ```
      $ perf stat -e '{UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE,UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE},duration_time' -a -A -- sleep 1
    
       Performance counter stats for 'system wide':
    
      CPU0                  256,866      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 494,413      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      967      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,738      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  285,161      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 429,920      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      955      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,443      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  310,753      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 416,657      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,231      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,573      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  416,067      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 405,966      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,481      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,447      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  312,911      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 408,154      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,086      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,380      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  333,994      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 370,349      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,287      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,335      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  188,107      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 302,423      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      701      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,070      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  307,221      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 383,642      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,036      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,158      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  318,479      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 821,545      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,028      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   2,550      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  227,618      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 372,272      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      903      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,456      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  376,783      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 419,827      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,406      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,453      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  286,583      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 429,956      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      999      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,436      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  313,867      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 370,159      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,114      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,291      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  342,083      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 409,111      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,399      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,684      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  365,828      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 376,037      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,378      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,411      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  382,456      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 621,743      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,232      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,955      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  342,316      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 385,067      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,176      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,268      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  373,588      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 386,163      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,394      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,464      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  381,206      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 546,891      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,266      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,712      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  221,176      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 392,069      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      831      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,456      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  355,401      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 705,595      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,235      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   2,216      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  371,436      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 428,103      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,306      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,442      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  384,352      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 504,200      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,468      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,860      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  228,856      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 287,976      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      832      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,060      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  215,121      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 334,162      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      681      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,026      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  296,179      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 436,083      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,084      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,525      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  262,296      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 416,573      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      986      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,533      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  285,852      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 359,842      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,073      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,326      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  303,379      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 367,222      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,008      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,156      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  273,487      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 425,449      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                      932      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,367      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  297,596      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 414,793      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,140      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,601      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  342,365      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 360,422      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,291      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,342      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  327,196      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 580,858      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,122      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   2,014      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  296,564      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 452,817      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,087      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,694      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  375,002      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 389,393      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,478      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   1,540      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0                  365,213      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36                 594,685      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                    1,401      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                   2,222      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0            1,000,749,060 ns   duration_time
    
             1.000749060 seconds time elapsed
      ```
    
    After:
    
      ```
       Performance counter stats for 'system wide':
    
      CPU0               20,547,434      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU36              45,202,862      UNC_CHA_TOR_OCCUPANCY.IA_MISS_DRD_REMOTE
      CPU0                   82,001      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU36                 159,688      UNC_CHA_TOR_INSERTS.IA_MISS_DRD_REMOTE
      CPU0            1,000,464,828 ns   duration_time
    
             1.000464828 seconds time elapsed
      ```
    
    Fixes: 3cdc5c2cb924acb4 ("perf parse-events: Handle uncore event aliases in small groups properly")
    Reviewed-by: Andi Kleen <ak@linux.intel.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Asaf Yaffe <asaf.yaffe@intel.com>
    Cc: Caleb Biggers <caleb.biggers@intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Kshipra Bopardikar <kshipra.bopardikar@intel.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Perry Taylor <perry.taylor@intel.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: Zhengjun Xing <zhengjun.xing@linux.intel.com>
    Link: https://lore.kernel.org/r/20220205010941.1065469-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 05b5a9d6285412d97fc61b8ec113d1d4f6b950c2
Author: German Gomez <german.gomez@arm.com>
Date:   Wed Jan 26 10:59:26 2022 +0000

    perf tools: Apply correct label to user/kernel symbols in branch mode
    
    In branch mode, the branch symbols were being displayed with incorrect
    cpumode labels. So fix this.
    
    For example, before:
      # perf record -b -a -- sleep 1
      # perf report -b
    
      Overhead  Command  Source Shared Object  Source Symbol               Target Symbol
         0.08%  swapper  [kernel.kallsyms]     [k] rcu_idle_enter          [k] cpuidle_enter_state
     ==> 0.08%  cmd0     [kernel.kallsyms]     [.] psi_group_change        [.] psi_group_change
         0.08%  cmd1     [kernel.kallsyms]     [k] psi_group_change        [k] psi_group_change
    
    After:
      # perf report -b
    
      Overhead  Command  Source Shared Object  Source Symbol               Target Symbol
         0.08%  swapper  [kernel.kallsyms]     [k] rcu_idle_enter          [k] cpuidle_enter_state
         0.08%  cmd0     [kernel.kallsyms]     [k] psi_group_change        [k] pei_group_change
         0.08%  cmd1     [kernel.kallsyms]     [k] psi_group_change        [k] psi_group_change
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: German Gomez <german.gomez@arm.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220126105927.3411216-1-german.gomez@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit a2887b9b8d1db7be971e5951e08ffe8563ea412f
Author: Masanari Iida <standby24x7@gmail.com>
Date:   Sat Dec 25 09:55:58 2021 +0900

    perf bpf: Fix a typo in bpf_counter_cgroup.c
    
    This patch fixes a spelling typo in error message.
    
    Signed-off-by: Masanari Iida <standby24x7@gmail.com>
    Acked-by: Namhyung Kim <namhyung@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20211225005558.503935-1-standby24x7@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit bc9c806e524429a4b98de257179af5e3fc2cb57d
Author: Leo Yan <leo.yan@linaro.org>
Date:   Fri Dec 24 20:40:13 2021 +0800

    perf synthetic-events: Return error if procfs isn't mounted for PID namespaces
    
    For perf recording, it retrieves process info by iterating nodes in proc
    fs.  If we run perf in a non-root PID namespace with command:
    
      # unshare --fork --pid perf record -e cycles -a -- test_program
    
    ... in this case, unshare command creates a child PID namespace and
    launches perf tool in it, but the issue is the proc fs is not mounted
    for the non-root PID namespace, this leads to the perf tool gathering
    process info from its parent PID namespace.
    
    We can use below command to observe the process nodes under proc fs:
    
      # unshare --pid --fork ls /proc
    1    137   1968  2128  3    342  48  62   78         crypto       kcore        net            uptime
    10   138   2     2142  30   35   49  63   8          devices      keys         pagetypeinfo   version
    11   139   20    2143  304  36   50  64   82         device-tree  key-users    partitions     vmallocinfo
    12   14    2011  22    305  37   51  65   83         diskstats    kmsg         self           vmstat
    128  140   2038  23    307  39   52  656  84         driver       kpagecgroup  slabinfo       zoneinfo
    129  15    2074  24    309  4    53  67   9          execdomains  kpagecount   softirqs
    13   16    2094  241   31   40   54  68   asound     fb           kpageflags   stat
    130  164   2096  242   310  41   55  69   buddyinfo  filesystems  loadavg      swaps
    131  17    2098  25    317  42   56  70   bus        fs           locks        sys
    132  175   21    26    32   43   57  71   cgroups    interrupts   meminfo      sysrq-trigger
    133  179   2102  263   329  44   58  75   cmdline    iomem        misc         sysvipc
    134  1875  2103  27    330  45   59  76   config.gz  ioports      modules      thread-self
    135  19    2117  29    333  46   6   77   consoles   irq          mounts       timer_list
    136  1941  2121  298   34   47   60  773  cpuinfo    kallsyms     mtd          tty
    
    So it shows many existed tasks, since unshared command has not mounted
    the proc fs for the new created PID namespace, it still accesses the
    proc fs of the root PID namespace.  This leads to two prominent issues:
    
    - Firstly, PID values are mismatched between thread info and samples.
      The gathered thread info are coming from the proc fs of the root PID
      namespace, but samples record its PID from the child PID namespace.
    
    - The second issue is profiled program 'test_program' returns its forked
      PID number from the child PID namespace, perf tool wrongly uses this
      PID number to retrieve the process info via the proc fs of the root
      PID namespace.
    
    To avoid issues, we need to mount proc fs for the child PID namespace
    with the option '--mount-proc' when use unshare command:
    
      # unshare --fork --pid --mount-proc perf record -e cycles -a -- test_program
    
    Conversely, when the proc fs of the root PID namespace is used by child
    namespace, perf tool can detect the multiple PID levels and
    nsinfo__is_in_root_namespace() returns false, this patch reports error
    for this case:
    
      # unshare --fork --pid perf record -e cycles -a -- test_program
      Couldn't synthesize bpf events.
      Perf runs in non-root PID namespace but it tries to gather process info from its parent PID namespace.
      Please mount the proc file system properly, e.g. add the option '--mount-proc' for unshare command.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Leo Yan <leo.yan@linaro.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexei Starovoitov <ast@kernel.org>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Cc: Daniel Borkmann <daniel@iogearbox.net>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Fastabend <john.fastabend@gmail.com>
    Cc: KP Singh <kpsingh@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Martin KaFai Lau <kafai@fb.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Song Liu <songliubraving@fb.com>
    Cc: Yonghong Song <yhs@fb.com>
    Link: https://lore.kernel.org/r/20211224124014.2492751-1-leo.yan@linaro.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit d792a7a94c2c3ba045247266bee2e2bced7b495a
Author: Ameer Hamza <amhamza.mgc@gmail.com>
Date:   Tue Jan 25 17:11:41 2022 +0500

    perf session: Check for NULL pointer before dereference
    
    Move NULL pointer check before dereferencing the variable.
    
    Addresses-Coverity: 1497622 ("Derereference before null check")
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ameer Hamza <amhamza.mgc@gmail.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
    Cc: German Gomez <german.gomez@arm.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Link: https://lore.kernel.org/r/20220125121141.18347-1-amhamza.mgc@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit a663520fcc4bce2814032e3de6c4e2665b9555e5
Author: Namhyung Kim <namhyung@kernel.org>
Date:   Tue Feb 1 23:08:25 2022 -0800

    perf annotate: Set error stream of objdump process for TUI
    
    The stderr should be set to a pipe when using TUI.  Otherwise it'd
    print to stdout and break TUI windows with an error message.
    
    Signed-off-by: Namhyung Kim <namhyung@kernel.org>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20220202070828.143303-2-namhyung@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit ae65b443f03fca3620cb37c5e019ddca3f89a1ce
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Wed Feb 2 16:27:23 2022 +0530

    perf tools: Add missing branch_sample_type to perf_event_attr__fprintf()
    
    This updates branch sample type with missing PERF_SAMPLE_BRANCH_TYPE_SAVE.
    
    Suggested-by: James Clark <james.clark@arm.com>
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Acked-by: Jiri Olsa <jolsa@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: linux-arm-kernel@lists.infradead.org
    Link: http://lore.kernel.org/lkml/1643799443-15109-1-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b7b9825fbee708e17ab7ea8b583561587c8ff7df
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sun May 9 09:39:02 2021 -0300

    tools headers UAPI: Sync linux/kvm.h with the kernel sources
    
    To pick the changes in:
    
      f6c6804c43fa18d3 ("kvm: Move KVM_GET_XSAVE2 IOCTL definition at the end of kvm.h")
    
    That just rebuilds perf, as these patches don't add any new KVM ioctl to
    be harvested for the the 'perf trace' ioctl syscall argument
    beautifiers.
    
    This is also by now used by tools/testing/selftests/kvm/, a simple test
    build succeeded.
    
    This silences this perf build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from latest version at 'include/uapi/linux/kvm.h'
      diff -u tools/include/uapi/linux/kvm.h include/uapi/linux/kvm.h
    
    Cc: Janosch Frank <frankja@linux.ibm.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Link: http://lore.kernel.org/lkml/Yf+4k5Fs5Q3HdSG9@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 9334030c3b94ca32af2e5afd02cb1c63307a2bea
Merge: fc45e6588d57b 90c9e950c0def
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sun Feb 6 08:28:34 2022 -0300

    Merge remote-tracking branch 'torvalds/master' into perf/urgent
    
    To check if more kernel API sync is needed and also to see if the perf
    build tests continue to pass.
    
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 28f9222138868899c53e00bc1f910faa55f88546
Author: Eric Dumazet <edumazet@google.com>
Date:   Sat Feb 5 21:05:16 2022 -0800

    net/smc: fix ref_tracker issue in smc_pnet_add()
    
    I added the netdev_tracker_alloc() right after ndev was
    stored into the newly allocated object:
    
      new_pe->ndev = ndev;
      if (ndev)
          netdev_tracker_alloc(ndev, &new_pe->dev_tracker, GFP_KERNEL);
    
    But I missed that later, we could end up freeing new_pe,
    then calling dev_put(ndev) to release the reference on ndev.
    
    The new_pe->dev_tracker would not be freed.
    
    To solve this issue, move the netdev_tracker_alloc() call to
    the point we know for sure new_pe will be kept.
    
    syzbot report (on net-next tree, but the bug is present in net tree)
    WARNING: CPU: 0 PID: 6019 at lib/refcount.c:31 refcount_warn_saturate+0xbf/0x1e0 lib/refcount.c:31
    Modules linked in:
    CPU: 0 PID: 6019 Comm: syz-executor.3 Not tainted 5.17.0-rc2-syzkaller-00650-g5a8fb33e5305 #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:refcount_warn_saturate+0xbf/0x1e0 lib/refcount.c:31
    Code: 1d f4 70 a0 09 31 ff 89 de e8 4d bc 99 fd 84 db 75 e0 e8 64 b8 99 fd 48 c7 c7 20 0c 06 8a c6 05 d4 70 a0 09 01 e8 9e 4e 28 05 <0f> 0b eb c4 e8 48 b8 99 fd 0f b6 1d c3 70 a0 09 31 ff 89 de e8 18
    RSP: 0018:ffffc900043b7400 EFLAGS: 00010282
    RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
    RDX: 0000000000040000 RSI: ffffffff815fb318 RDI: fffff52000876e72
    RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
    R10: ffffffff815f507e R11: 0000000000000000 R12: 1ffff92000876e85
    R13: 0000000000000000 R14: ffff88805c1c6600 R15: 0000000000000000
    FS:  00007f1ef6feb700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000001b2d02b000 CR3: 00000000223f4000 CR4: 00000000003506f0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     __refcount_dec include/linux/refcount.h:344 [inline]
     refcount_dec include/linux/refcount.h:359 [inline]
     ref_tracker_free+0x53f/0x6c0 lib/ref_tracker.c:119
     netdev_tracker_free include/linux/netdevice.h:3867 [inline]
     dev_put_track include/linux/netdevice.h:3884 [inline]
     dev_put_track include/linux/netdevice.h:3880 [inline]
     dev_put include/linux/netdevice.h:3910 [inline]
     smc_pnet_add_eth net/smc/smc_pnet.c:399 [inline]
     smc_pnet_enter net/smc/smc_pnet.c:493 [inline]
     smc_pnet_add+0x5fc/0x15f0 net/smc/smc_pnet.c:556
     genl_family_rcv_msg_doit+0x228/0x320 net/netlink/genetlink.c:731
     genl_family_rcv_msg net/netlink/genetlink.c:775 [inline]
     genl_rcv_msg+0x328/0x580 net/netlink/genetlink.c:792
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     genl_rcv+0x24/0x40 net/netlink/genetlink.c:803
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x6e8/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmsg+0xe5/0x1b0 net/socket.c:2496
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Fixes: b60645248af3 ("net/smc: add net device tracker to struct smc_pnetentry")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit aec12836e7196e4d360b2cbf20cf7aa5139ad2ec
Author: Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>
Date:   Sun Feb 6 00:49:51 2022 +0300

    net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
    
    When setting up autonegotiation for 88E1118R and compatible PHYs,
    a software reset of PHY is issued before setting up polarity.
    This is incorrect as changes of MDI Crossover Mode bits are
    disruptive to the normal operation and must be followed by a
    software reset to take effect. Let's patch m88e1118_config_aneg()
    to fix the issue mentioned before by invoking software reset
    of the PHY just after setting up MDI-x polarity.
    
    Fixes: 605f196efbf8 ("phy: Add support for Marvell 88E1118 PHY")
    Signed-off-by: Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>
    Reviewed-by: Serge Semin <fancer.lancer@gmail.com>
    Suggested-by: Andrew Lunn <andrew@lunn.ch>
    Cc: stable@vger.kernel.org
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6df4432a5eca101b5fd80fbee41d309f3d67928d
Author: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Date:   Tue Feb 1 12:01:53 2022 +0100

    drm/panel: simple: Assign data from panel_dpi_probe() correctly
    
    In the function panel_simple_probe() the pointer panel->desc is
    assigned to the passed pointer desc. If function panel_dpi_probe()
    is called panel->desc will be updated, but further on only desc
    will be evaluated. So update the desc pointer to be able to use
    the data from the function panel_dpi_probe().
    
    Fixes: 4a1d0dbc8332 ("drm/panel: simple: add panel-dpi support")
    
    Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
    Cc: Marek Vasut <marex@denx.de>
    Cc: Thierry Reding <thierry.reding@gmail.com>
    Cc: Sam Ravnborg <sam@ravnborg.org>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    To: dri-devel@lists.freedesktop.org
    Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
    Signed-off-by: Marek Vasut <marex@denx.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220201110153.3479-1-cniedermaier@dh-electronics.com

commit 90c9e950c0def5c354b4a6154a2ddda3e5f214ac
Merge: 5fdb26213fcb9 e25a8d959992f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 5 10:40:17 2022 -0800

    Merge tag 'for-linus-5.17a-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
    
    Pull xen fixes from Juergen Gross:
    
     - documentation fixes related to Xen
    
     - enable x2apic mode when available when running as hardware
       virtualized guest under Xen
    
     - cleanup and fix a corner case of vcpu enumeration when running a
       paravirtualized Xen guest
    
    * tag 'for-linus-5.17a-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
      x86/Xen: streamline (and fix) PV CPU enumeration
      xen: update missing ioctl magic numers documentation
      Improve docs for IOCTL_GNTDEV_MAP_GRANT_REF
      xen: xenbus_dev.h: delete incorrect file name
      xen/x2apic: enable x2apic mode when supported for HVM

commit 5fdb26213fcb912955e0c9eacbe2b8961628682f
Merge: fbc04bf01a8d5 7e6a6b400db80
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 5 09:55:59 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "ARM:
    
       - A couple of fixes when handling an exception while a SError has
         been delivered
    
       - Workaround for Cortex-A510's single-step erratum
    
      RISC-V:
    
       - Make CY, TM, and IR counters accessible in VU mode
    
       - Fix SBI implementation version
    
      x86:
    
       - Report deprecation of x87 features in supported CPUID
    
       - Preparation for fixing an interrupt delivery race on AMD hardware
    
       - Sparse fix
    
      All except POWER and s390:
    
       - Rework guest entry code to correctly mark noinstr areas and fix
         vtime' accounting (for x86, this was already mostly correct but not
         entirely; for ARM, MIPS and RISC-V it wasn't)"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
      KVM: x86: Use ERR_PTR_USR() to return -EFAULT as a __user pointer
      KVM: x86: Report deprecated x87 features in supported CPUID
      KVM: arm64: Workaround Cortex-A510's single-step and PAC trap errata
      KVM: arm64: Stop handle_exit() from handling HVC twice when an SError occurs
      KVM: arm64: Avoid consuming a stale esr value when SError occur
      RISC-V: KVM: Fix SBI implementation version
      RISC-V: KVM: make CY, TM, and IR counters accessible in VU mode
      kvm/riscv: rework guest entry logic
      kvm/arm64: rework guest entry logic
      kvm/x86: rework guest entry logic
      kvm/mips: rework guest entry logic
      kvm: add guest_state_{enter,exit}_irqoff()
      KVM: x86: Move delivery of non-APICv interrupt into vendor code
      kvm: Move KVM_GET_XSAVE2 IOCTL definition at the end of kvm.h

commit fbc04bf01a8d5a639c2e90fea9402f715cf10ff2
Merge: ea7b3e6d42d7a cea267c235e1b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 5 09:21:55 2022 -0800

    Merge tag 'xfs-5.17-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs fixes from Darrick Wong:
     "I was auditing operations in XFS that clear file privileges, and
      realized that XFS' fallocate implementation drops suid/sgid but
      doesn't clear file capabilities the same way that file writes and
      reflink do.
    
      There are VFS helpers that do it correctly, so refactor XFS to use
      them. I also noticed that we weren't flushing the log at the correct
      point in the fallocate operation, so that's fixed too.
    
      Summary:
    
       - Fix fallocate so that it drops all file privileges when files are
         modified instead of open-coding that incompletely.
    
       - Fix fallocate to flush the log if the caller wanted synchronous
         file updates"
    
    * tag 'xfs-5.17-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: ensure log flush at the end of a synchronous fallocate call
      xfs: move xfs_update_prealloc_flags() to xfs_pnfs.c
      xfs: set prealloc flag in xfs_alloc_file_space()
      xfs: fallocate() should call file_modified()
      xfs: remove XFS_PREALLOC_SYNC
      xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP*

commit ea7b3e6d42d7afa141ff765099d6b4ea406001bc
Merge: 524446e217985 2d86293c70750
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 5 09:13:51 2022 -0800

    Merge tag 'vfs-5.17-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull vfs fixes from Darrick Wong:
     "I was auditing the sync_fs code paths recently and noticed that most
      callers of ->sync_fs ignore its return value (and many implementations
      never return nonzero even if the fs is broken!), which means that
      internal fs errors and corruption are not passed up to userspace
      callers of syncfs(2) or FIFREEZE. Hence fixing the common code and
      XFS, and I'll start working on the ext4/btrfs folks if this is merged.
    
      Summary:
    
       - Fix a bug where callers of ->sync_fs (e.g. sync_filesystem and
         syncfs(2)) ignore the return value.
    
       - Fix a bug where callers of sync_filesystem (e.g. fs freeze) ignore
         the return value.
    
       - Fix a bug in XFS where xfs_fs_sync_fs never passed back error
         returns"
    
    * tag 'vfs-5.17-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: return errors in xfs_fs_sync_fs
      quota: make dquot_quota_sync return errors from ->sync_fs
      vfs: make sync_filesystem return errors from ->sync_fs
      vfs: make freeze_super abort when sync_filesystem returns error

commit 524446e2179855534b425647dfc250757905aad8
Merge: 0457e5153e0e8 ebb7fb1557b1d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Feb 5 09:04:43 2022 -0800

    Merge tag 'iomap-5.17-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull iomap fix from Darrick Wong:
     "A single bugfix for iomap.
    
      The fix should eliminate occasional complaints about stall warnings
      when a lot of writeback IO completes all at once and we have to then
      go clearing status on a large number of folios.
    
      Summary:
    
       - Limit the length of ioend chains in writeback so that we don't trip
         the softlockup watchdog and to limit long tail latency on clearing
         PageWriteback"
    
    * tag 'iomap-5.17-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs, iomap: limit individual ioend chain lengths in writeback

commit 59085208e4a2183998964844f8684fea0378128d
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Sat Feb 5 01:03:21 2022 +0200

    net: mscc: ocelot: fix all IP traffic getting trapped to CPU with PTP over IP
    
    The filters for the PTP trap keys are incorrectly configured, in the
    sense that is2_entry_set() only looks at trap->key.ipv4.dport or
    trap->key.ipv6.dport if trap->key.ipv4.proto or trap->key.ipv6.proto is
    set to IPPROTO_TCP or IPPROTO_UDP.
    
    But we don't do that, so is2_entry_set() goes through the "else" branch
    of the IP protocol check, and ends up installing a rule for "Any IP
    protocol match" (because msk is also 0). The UDP port is ignored.
    
    This means that when we run "ptp4l -i swp0 -4", all IP traffic is
    trapped to the CPU, which hinders bridging.
    
    Fix this by specifying the IP protocol in the VCAP IS2 filters for PTP
    over UDP.
    
    Fixes: 96ca08c05838 ("net: mscc: ocelot: set up traps for PTP packets")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e3d13da7f77d73c64981b62591c21614a6cf688f
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sat Feb 5 12:28:40 2022 +0100

    platform/x86: asus-wmi: Fix regression when probing for fan curve control
    
    The fan curve control patches introduced a regression for at least the
    TUF FX506 and possibly other TUF series laptops that do not have support
    for fan curve control.
    
    As part of the probing process, asus_wmi_evaluate_method_buf is called
    to get the factory default fan curve . The WMI management function
    returns 0 on certain laptops to indicate lack of fan curve control
    instead of ASUS_WMI_UNSUPPORTED_METHOD. This 0 is transformed to
    -ENODATA which results in failure when probing.
    
    Fixes: 0f0ac158d28f ("platform/x86: asus-wmi: Add support for custom fan curves")
    Reported-and-tested-by: Abhijeet V <abhijeetviswa@gmail.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220205112840.33095-1-hdegoede@redhat.com

commit fd5dd6acd8f823ea804f76d3af64fa1be9d5fb78
Author: Sergio Costas <rastersoft@gmail.com>
Date:   Fri Feb 4 10:01:17 2022 +0100

    HID:Add support for UGTABLET WP5540
    
    This patch adds support for the UGTABLET WP5540 digitizer tablet
    devices. Without it, the pen moves the cursor, but neither the
    buttons nor the tap sensor in the tip do work.
    
    Signed-off-by: Sergio Costas <rastersoft@gmail.com>
    Link: https://lore.kernel.org/r/63dece1d-91ca-1b1b-d90d-335be66896be@gmail.com
    Cc: stable@vger.kernel.org
    Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>

commit 9ccdcc73d37cf0f1d4f97712f6b38af8806ac064
Merge: c0689e46be231 9a8406ba1a9a2
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Sat Feb 5 11:52:53 2022 +0100

    Merge tag 'phy-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy into char-misc-next
    
    Vinod writes:
    
    phy: fixes for 5.17
    
    Fixes for bunch of drivers:
     - clk params for dphy
     - arg fix for mtk-tphy
     - refcount leak fix for stm32
     - bus width fix for zynqmp
     - sentinel fix ti
     - PHY_BRCM_USB Kconfig fix
     - clk fix for usb phy
    
    * tag 'phy-fixes-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy:
      phy: dphy: Correct clk_pre parameter
      phy: phy-mtk-tphy: Fix duplicated argument in phy-mtk-tphy
      phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable()
      phy: xilinx: zynqmp: Fix bus width setting for SGMII
      phy: cadence: Sierra: fix error handling bugs in probe()
      phy: ti: Fix missing sentinel for clk_div_table
      phy: broadcom: Kconfig: Fix PHY_BRCM_USB config option
      phy: usb: Leave some clocks running during suspend

commit 7e6a6b400db8048bd1c06e497e338388413cf5bc
Merge: 6e37ec8825a11 1dd498e5e26ad
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Sat Feb 5 00:58:25 2022 -0500

    Merge tag 'kvmarm-fixes-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
    
    KVM/arm64 fixes for 5.17, take #2
    
    - A couple of fixes when handling an exception while a SError has been
      delivered
    
    - Workaround for Cortex-A510's single-step[ erratum

commit c6ce9c5831cae515d375a01b97ae1778689acf19
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date:   Wed Feb 2 17:46:48 2022 +1100

    crypto: api - Move cryptomgr soft dependency into algapi
    
    The soft dependency on cryptomgr is only needed in algapi because
    if algapi isn't present then no algorithms can be loaded.  This
    also fixes the case where api is built-in but algapi is built as
    a module as the soft dependency would otherwise get lost.
    
    Fixes: 8ab23d547f65 ("crypto: api - Add softdep on cryptomgr")
    Reported-by: Jan Beulich <jbeulich@suse.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
    Tested-by: Jan Beulich <jbeulich@suse.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

commit f8d9d938514f46c4892aff6bfe32f425e84d81cc
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Feb 3 14:55:47 2022 -0800

    tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case
    
    syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY)
    calls over the same TCP socket would again trigger the
    infamous warning in inet_sock_destruct()
    
            WARN_ON(sk_forward_alloc_get(sk));
    
    While Talal took into account a mix of regular copied data
    and MSG_ZEROCOPY one in the same skb, the sendpage() path
    has been forgotten.
    
    We want the charging to happen for sendpage(), because
    pages could be coming from a pipe. What is missing is the
    downgrading of pure zerocopy status to make sure
    sk_forward_alloc will stay synced.
    
    Add tcp_downgrade_zcopy_pure() helper so that we can
    use it from the two callers.
    
    Fixes: 9b65b17db723 ("net: avoid double accounting for pure zerocopy skbs")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Cc: Talal Ahmad <talalahmad@google.com>
    Cc: Arjun Roy <arjunroy@google.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
    Link: https://lore.kernel.org/r/20220203225547.665114-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0457e5153e0e8420134f60921349099e907264ca
Merge: fc93310c67ff1 f3136c4ce7acf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 16:28:11 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
    
    Pull rdma fixes from Jason Gunthorpe:
     "Some medium sized bugs in the various drivers. A couple are more
      recent regressions:
    
       - Fix two panics in hfi1 and two allocation problems
    
       - Send the IGMP to the correct address in cma
    
       - Squash a syzkaller bug related to races reading the multicast list
    
       - Memory leak in siw and cm
    
       - Fix a corner case spec compliance for HFI/QIB
    
       - Correct the implementation of fences in siw
    
       - Error unwind bug in mlx4"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma:
      RDMA/mlx4: Don't continue event handler after memory allocation failure
      RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
      IB/rdmavt: Validate remote_addr during loopback atomic tests
      IB/cm: Release previously acquired reference counter in the cm_id_priv
      RDMA/siw: Fix refcounting leak in siw_create_qp()
      RDMA/ucma: Protect mc during concurrent multicast leaves
      RDMA/cma: Use correct address when leaving multicast group
      IB/hfi1: Fix tstats alloc and dealloc
      IB/hfi1: Fix AIP early init panic
      IB/hfi1: Fix alloc failure with larger txqueuelen
      IB/hfi1: Fix panic with larger ipoib send_queue_size

commit fc93310c67ff1c0dc38e3df7814973b55eea5559
Merge: e09e1a40639ba c763ec4c10f78
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 15:27:45 2022 -0800

    Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Seven fixes, six of which are fairly obvious driver fixes.
    
      The one core change to the device budget depth is to try to ensure
      that if the default depth is large (which can produce quite a sizeable
      bitmap allocation per device), we give back the memory we don't need
      if there's a queue size reduction in slave_configure (which happens to
      a lot of devices)"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: hisi_sas: Fix setting of hisi_sas_slot.is_internal
      scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
      scsi: pm8001: Fix use-after-free for aborted TMF sas_task
      scsi: pm8001: Fix warning for undescribed param in process_one_iomb()
      scsi: core: Reallocate device's budget map on queue depth change
      scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
      scsi: pm80xx: Fix double completion for SATA devices

commit e09e1a40639ba10eff22984003c201db57fe033a
Merge: 86286e486cbdd 7dd3876205df9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 15:22:35 2022 -0800

    Merge tag 'pci-v5.17-fixes-3' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci fixes from Bjorn Helgaas:
    
     - Restructure j721e_pcie_probe() so we don't dereference a NULL pointer
       (Bjorn Helgaas)
    
     - Add a kirin_pcie_data struct to identify different Kirin variants to
       fix probe failure for controllers with an internal PHY (Bjorn
       Helgaas)
    
    * tag 'pci-v5.17-fixes-3' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
      PCI: kirin: Add dev struct for of_device_get_match_data()
      PCI: j721e: Initialize pcie->cdns_pcie before using it

commit ca0cb9a60f6d86d4b2139c6f393a78f39edcd7cb
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Fri Feb 4 13:14:08 2022 -0800

    riscv/mm: Add XIP_FIXUP for riscv_pfn_base
    
    This manifests as a crash early in boot on VexRiscv.
    
    Signed-off-by: Myrtle Shah <gatecat@ds0.me>
    [Palmer: split commit]
    Fixes: 44c922572952 ("RISC-V: enable XIP")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 4b1c70aa8ed8249608bb991380cb8ff423edf49e
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Fri Feb 4 13:13:37 2022 -0800

    riscv/mm: Add XIP_FIXUP for phys_ram_base
    
    This manifests as a crash early in boot on VexRiscv.
    
    Signed-off-by: Myrtle Shah <gatecat@ds0.me>
    [Palmer: split commit]
    Fixes: 6d7f91d914bc ("riscv: Get rid of CONFIG_PHYS_RAM_BASE in kernel physical address conversion")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 7dd3876205df92e07d824fe2264b38e0b8a9eec1
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Wed Feb 2 09:52:41 2022 -0600

    PCI: kirin: Add dev struct for of_device_get_match_data()
    
    Bean reported that a622435fbe1a ("PCI: kirin: Prefer
    of_device_get_match_data()") broke kirin_pcie_probe() because it assumed
    match data of 0 was a failure when in fact, it meant the match data was
    "(void *)PCIE_KIRIN_INTERNAL_PHY".
    
    Therefore, probing of "hisilicon,kirin960-pcie" devices failed with -EINVAL
    and an "OF data missing" message.
    
    Add a struct kirin_pcie_data to encode the PHY type.  Then the result of
    of_device_get_match_data() should always be a non-NULL pointer to a struct
    kirin_pcie_data that contains the PHY type.
    
    Fixes: a622435fbe1a ("PCI: kirin: Prefer of_device_get_match_data()")
    Link: https://lore.kernel.org/r/20220202162659.GA12603@bhelgaas
    Link: https://lore.kernel.org/r/20220201215941.1203155-1-huobean@gmail.com
    Reported-by: Bean Huo <beanhuo@micron.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 86286e486cbdd68f01d330409307f6a6efcd4298
Merge: b0bc0cb8157d5 40cdc509877ba
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 12:14:58 2022 -0800

    Merge tag 'for-5.17-rc2-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs fixes from David Sterba:
     "A few fixes and error handling improvements:
    
       - fix deadlock between quota disable and qgroup rescan worker
    
       - fix use-after-free after failure to create a snapshot
    
       - skip warning on unmount after log cleanup failure
    
       - don't start transaction for scrub if the fs is mounted read-only
    
       - tree checker verifies item sizes"
    
    * tag 'for-5.17-rc2-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
      btrfs: skip reserved bytes warning on unmount after log cleanup failure
      btrfs: fix use of uninitialized variable at rm device ioctl
      btrfs: fix use-after-free after failure to create a snapshot
      btrfs: tree-checker: check item_size for dev_item
      btrfs: tree-checker: check item_size for inode_item
      btrfs: fix deadlock between quota disable and qgroup rescan worker
      btrfs: don't start transaction for scrub if the fs is mounted read-only

commit 183f80fd72db42c9cc483aa7a5e8e881355d0b03
Author: Sean Young <sean@mess.org>
Date:   Tue Feb 1 18:38:36 2022 +0000

    selftests/ir: fix build with ancient kernel headers
    
    Since commit e2bcbd7769ee ("tools headers UAPI: remove stale lirc.h"),
    the build of the selftests fails on rhel 8 since its version of
    /usr/include/linux/lirc.h has no definition of RC_PROTO_RCMM32, etc [1].
    
    [1] https://lkml.org/lkml/2022/1/28/275
    
    Fixes: e2bcbd7769ee ("tools headers UAPI: remove stale lirc.h")
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Signed-off-by: Sean Young <sean@mess.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit b0bc0cb8157d5f09493a235e1ee73e84dd182ff9
Merge: 7c4a94590e4dc 24331050a3e6a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 12:08:49 2022 -0800

    Merge tag 'erofs-for-5.17-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
    
    Pull erofs fixes from Gao Xiang:
     "Two fixes related to fsdax cleanup in this cycle and ztailpacking to
      fix small compressed data inlining. There is also a trivial cleanup to
      rearrange code for better reading.
    
      Summary:
    
       - fix fsdax partition offset misbehavior
    
       - clean up z_erofs_decompressqueue_work() declaration
    
       - fix up EOF lcluster inlining, especially for small compressed data"
    
    * tag 'erofs-for-5.17-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
      erofs: fix small compressed files inlining
      erofs: avoid unnecessary z_erofs_decompressqueue_work() declaration
      erofs: fix fsdax partition offset handling

commit e2aa5e650b07693477dff554053605976789fd68
Author: Axel Rasmussen <axelrasmussen@google.com>
Date:   Thu Jan 27 14:11:15 2022 -0800

    selftests: fixup build warnings in pidfd / clone3 tests
    
    These are some trivial fixups, which were needed to build the tests with
    clang and -Werror. The following issues are fixed:
    
    - Remove various unused variables.
    - In child_poll_leader_exit_test, clang isn't smart enough to realize
      syscall(SYS_exit, 0) won't return, so it complains we never return
      from a non-void function. Add an extra exit(0) to appease it.
    - In test_pidfd_poll_leader_exit, ret may be branched on despite being
      uninitialized, if we have !use_waitpid. Initialize it to zero to get
      the right behavior in that case.
    
    Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
    Acked-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 4cbd93c3c110447adc66cb67c08af21f939ae2d7
Author: Axel Rasmussen <axelrasmussen@google.com>
Date:   Thu Jan 27 13:29:51 2022 -0800

    pidfd: fix test failure due to stack overflow on some arches
    
    When running the pidfd_fdinfo_test on arm64, it fails for me. After some
    digging, the reason is that the child exits due to SIGBUS, because it
    overflows the 1024 byte stack we've reserved for it.
    
    To fix the issue, increase the stack size to 8192 bytes (this number is
    somewhat arbitrary, and was arrived at through experimentation -- I kept
    doubling until the failure no longer occurred).
    
    Also, let's make the issue easier to debug. wait_for_pid() returns an
    ambiguous value: it may return -1 in all of these cases:
    
    1. waitpid() itself returned -1
    2. waitpid() returned success, but we found !WIFEXITED(status).
    3. The child process exited, but it did so with a -1 exit code.
    
    There's no way for the caller to tell the difference. So, at least log
    which occurred, so the test runner can debug things.
    
    While debugging this, I found that we had !WIFEXITED(), because the
    child exited due to a signal. This seems like a reasonably common case,
    so also print out whether or not we have WIFSIGNALED(), and the
    associated WTERMSIG() (if any). This lets us see the SIGBUS I'm fixing
    clearly when it occurs.
    
    Finally, I'm suspicious of allocating the child's stack on our stack.
    man clone(2) suggests that the correct way to do this is with mmap(),
    and in particular by setting MAP_STACK. So, switch to doing it that way
    instead.
    
    Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
    Acked-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 7c4a94590e4dc134b36b0edeb5ddcf6e8b3da498
Merge: 494a2c2b27c5d b13e0c7185681
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 12:01:57 2022 -0800

    Merge tag 'block-5.17-2022-02-04' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - NVMe pull request
        - fix use-after-free in rdma and tcp controller reset (Sagi Grimberg)
        - fix the state check in nvmf_ctlr_matches_baseopts (Uday Shankar)
    
     - MD nowait null pointer fix (Song)
    
     - blk-integrity seed advance fix (Martin)
    
     - Fix a dio regression in this merge window (Ilya)
    
    * tag 'block-5.17-2022-02-04' of git://git.kernel.dk/linux-block:
      block: bio-integrity: Advance seed correctly for larger interval sizes
      nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
      md: fix NULL pointer deref with nowait but no mddev->queue
      block: fix DIO handling regressions in blkdev_read_iter()
      nvme-rdma: fix possible use-after-free in transport error_recovery work
      nvme-tcp: fix possible use-after-free in transport error_recovery work
      nvme: fix a possible use-after-free in controller reset during load

commit 494a2c2b27c5d2a3c4f65a325fe5a0087013c1a4
Merge: 07cd9ac4c5403 ac9f0c810684a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:52:37 2022 -0800

    Merge tag 'ata-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ATA fixes from Damien Le Moal:
    
     - Sergey volunteered to be a reviewer for the Renesas R-Car SATA driver
       and PATA drivers. Update the MAINTAINERS file accordingly.
    
     - Regression fix: add a horkage flag to prevent accessing the log
       directory log page with SATADOM-ML 3ME SATA devices as they react
       badly to reading that log page (from Anton).
    
    * tag 'ata-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: libata-core: Introduce ATA_HORKAGE_NO_LOG_DIR horkage
      MAINTAINERS: add myself as Renesas R-Car SATA driver reviewer
      MAINTAINERS: add myself as PATA drivers reviewer

commit 07cd9ac4c54039c99f98d30e83e23040e330fad5
Merge: ba6ef8af0f3be 9b45a7738eec5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:45:16 2022 -0800

    Merge tag 'iommu-fixes-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
    
    Pull iommu fixes from Joerg Roedel:
    
     - Warning fixes and a fix for a potential use-after-free in IOMMU core
       code
    
     - Another potential memory leak fix for the Intel VT-d driver
    
     - Fix for an IO polling loop timeout issue in the AMD IOMMU driver
    
    * tag 'iommu-fixes-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
      iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
      iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
      iommu: Fix some W=1 warnings
      iommu: Fix potential use-after-free during probe

commit ba6ef8af0f3be2e0318aac7e6e43d3a04a069a6a
Merge: ddb16b08316bc 9d5505f1eebec
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:38:01 2022 -0800

    Merge tag 'random-5.17-rc3-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random
    
    Pull random number generator fixes from Jason Donenfeld:
     "For this week, we have:
    
       - A fix to make more frequent use of hwgenerator randomness, from
         Dominik.
    
       - More cleanups to the boot initialization sequence, from Dominik.
    
       - A fix for an old shortcoming with the ZAP ioctl, from me.
    
       - A workaround for a still unfixed Clang CFI/FullLTO compiler bug,
         from me. On one hand, it's a bummer to commit workarounds for
         experimental compiler features that have bugs. But on the other, I
         think this actually improves the code somewhat, independent of the
         bug. So a win-win"
    
    * tag 'random-5.17-rc3-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random:
      random: only call crng_finalize_init() for primary_crng
      random: access primary_pool directly rather than through pointer
      random: wake up /dev/random writers after zap
      random: continually use hwgenerator randomness
      lib/crypto: blake2s: avoid indirect calls to compression function for Clang CFI

commit ddb16b08316bc4d57b9a46f4a470fd331815fb4a
Merge: 0a566d43c8cde 04662bac0067e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:32:46 2022 -0800

    Merge tag 'acpi-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull ACPI fix from Rafael Wysocki:
     "Fix compilation in the case when ACPI is selected and CRC32, depended
      on by ACPI after recent changes, is not (Randy Dunlap)"
    
    * tag 'acpi-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      ACPI: require CRC32 to build

commit 0a566d43c8cdefb30a225f0dbde40e4f487e0fc9
Merge: 31462d9e47cf6 52517d9c0c011
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:24:28 2022 -0800

    Merge tag 'sound-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
    
    Pull sound fixes from Takashi Iwai:
     "A collection of small fixes.
    
      The major changes are ASoC core fixes, addressing the DPCM locking
      issue after the recent code changes and the potentially invalid
      register accesses via control API. Also, HD-audio got a core fix for
      Oops at dynamic unbinding.
    
      The rest are device-specific small fixes, including the usual stuff
      like HD-audio and USB-audio quirks"
    
    * tag 'sound-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (31 commits)
      ALSA: hda: Skip codec shutdown in case the codec is not registered
      ALSA: usb-audio: Correct quirk for VF0770
      ALSA: Replace acpi_bus_get_device()
      Input: wm97xx: Simplify resource management
      ALSA: hda/realtek: Add quirk for ASUS GU603
      ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after reboot from Windows
      ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer chipset)
      ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 quirks
      ALSA: hda: realtek: Fix race at concurrent COEF updates
      ASoC: ops: Check for negative values before reading them
      ASoC: rt5682: Fix deadlock on resume
      ASoC: hdmi-codec: Fix OOB memory accesses
      ASoC: soc-pcm: Move debugfs removal out of spinlock
      ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks
      ASoC: fsl: Add missing error handling in pcm030_fabric_probe
      ALSA: hda: Fix signedness of sscanf() arguments
      ALSA: usb-audio: initialize variables that could ignore errors
      ALSA: hda: Fix UAF of leds class devs at unbinding
      ASoC: qdsp6: q6apm-dai: only stop graphs that are started
      ASoC: codecs: wcd938x: fix return value of mixer put function
      ...

commit 31462d9e47cf6e2cb10a69c833b5e081fff7086d
Merge: f9aaa5b05ea37 9ca3d3cd08575
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 11:13:54 2022 -0800

    Merge tag 'drm-fixes-2022-02-04' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Regular fixes for the week. Daniel has agreed to bring back the fbcon
      hw acceleration under a CONFIG option for the non-drm fbdev users, we
      don't advise turning this on unless you are in the niche that is old
      fbdev drivers, Since it's essentially a revert and shouldn't be high
      impact seemed like a good time to do it now.
    
      Otherwise, i915 and amdgpu fixes are most of it, along with some minor
      fixes elsewhere.
    
      fbdev:
       - readd fbcon acceleration
    
      i915:
       - fix DP monitor via type-c dock
       - fix for engine busyness and read timeout with GuC
       - use ALLOW_FAIL for error capture buffer allocs
       - don't use interruptible lock on error paths
       - smatch fix to reject zero sized overlays.
    
      amdgpu:
       - mGPU fan boost fix for beige goby
       - S0ix fixes
       - Cyan skillfish hang fix
       - DCN fixes for DCN 3.1
       - DCN fixes for DCN 3.01
       - Apple retina panel fix
       - ttm logic inversion fix
    
      dma-buf:
       - heaps: fix potential spectre v1 gadget
    
      kmb:
       - fix potential oob access
    
      mxsfb:
       - fix NULL ptr deref
    
      nouveau:
       - fix potential oob access during BIOS decode"
    
    * tag 'drm-fixes-2022-02-04' of git://anongit.freedesktop.org/drm/drm: (24 commits)
      drm: mxsfb: Fix NULL pointer dereference
      drm/amdgpu: fix logic inversion in check
      drm/amd: avoid suspend on dGPUs w/ s2idle support when runtime PM enabled
      drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels
      drm/amd/display: revert "Reset fifo after enable otg"
      drm/amd/display: watermark latencies is not enough on DCN31
      drm/amd/display: Update watermark values for DCN301
      drm/amdgpu: fix a potential GPU hang on cyan skillfish
      drm/amd: Only run s3 or s0ix if system is configured properly
      drm/amd: add support to check whether the system is set to s3
      fbcon: Add option to enable legacy hardware acceleration
      Revert "fbcon: Disable accelerated scrolling"
      Revert "fbdev: Garbage collect fbdev scrolling acceleration, part 1 (from TODO list)"
      drm/i915/pmu: Fix KMD and GuC race on accessing busyness
      dma-buf: heaps: Fix potential spectre v1 gadget
      drm/amd: Warn users about potential s0ix problems
      drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
      drm/nouveau: fix off by one in BIOS boundary checking
      drm/i915/adlp: Fix TypeC PHY-ready status readout
      drm/i915/pmu: Use PM timestamp instead of RING TIMESTAMP for reference
      ...

commit 3c04d84508b54fcf524093b0d4a718680ed67f0f
Author: Myrtle Shah <gatecat@ds0.me>
Date:   Thu Jan 20 15:33:37 2022 +0000

    riscv: Fix XIP_FIXUP_FLASH_OFFSET
    
    There were several problems with the calculation. Not only was an 'and'
    being computed into t1 but thrown away; but the 'and' itself would
    cause problems if the granularity of the XIP physical address was less
    than XIP_OFFSET - in my case I had the kernel image at 2MB in SPI flash.
    
    Fixes: f9ace4ede49b ("riscv: remove .text section size limitation for XIP")
    Cc: stable@vger.kernel.org
    Signed-off-by: Myrtle Shah <gatecat@ds0.me>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit f9aaa5b05ea376f4917ff2c838c4641a100fd1e2
Merge: cff7f2237c2b4 07d2505b963b2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 10:34:19 2022 -0800

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "10 patches.
    
      Subsystems affected by this patch series: ipc, MAINTAINERS, and mm
      (vmscan, debug, pagemap, kmemleak, and selftests)"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      kselftest/vm: revert "tools/testing/selftests/vm/userfaultfd.c: use swap() to make code cleaner"
      MAINTAINERS: update rppt's email
      mm/kmemleak: avoid scanning potential huge holes
      ipc/sem: do not sleep with a spin lock held
      mm/pgtable: define pte_index so that preprocessor could recognize it
      mm/page_table_check: check entries at pmd levels
      mm/khugepaged: unify collapse pmd clear, flush and free
      mm/page_table_check: use unsigned long for page counters and cleanup
      mm/debug_vm_pgtable: remove pte entry from the page table
      Revert "mm/page_isolation: unset migratetype directly for non Buddy page"

commit 9d5505f1eebeca778074a0260ed077fd85f8792c
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Sun Jan 30 22:03:20 2022 +0100

    random: only call crng_finalize_init() for primary_crng
    
    crng_finalize_init() returns instantly if it is called for another pool
    than primary_crng. The test whether crng_finalize_init() is still required
    can be moved to the relevant caller in crng_reseed(), and
    crng_need_final_init can be reset to false if crng_finalize_init() is
    called with workqueues ready. Then, no previous callsite will call
    crng_finalize_init() unless it is needed, and we can get rid of the
    superfluous function parameter.
    
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit ebf7606388732ecf2821ca21087e9446cb4a5b57
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Sun Jan 30 22:03:19 2022 +0100

    random: access primary_pool directly rather than through pointer
    
    Both crng_initialize_primary() and crng_init_try_arch_early() are
    only called for the primary_pool. Accessing it directly instead of
    through a function parameter simplifies the code.
    
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 042e293e16e3aa9794ce60c29f5b7b0c8170f933
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Fri Jan 28 23:44:03 2022 +0100

    random: wake up /dev/random writers after zap
    
    When account() is called, and the amount of entropy dips below
    random_write_wakeup_bits, we wake up the random writers, so that they
    can write some more in. However, the RNDZAPENTCNT/RNDCLEARPOOL ioctl
    sets the entropy count to zero -- a potential reduction just like
    account() -- but does not unblock writers. This commit adds the missing
    logic to that ioctl to unblock waiting writers.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit c321e907aa4803d562d6e70ebed9444ad082f953
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Tue Jan 25 21:14:57 2022 +0100

    random: continually use hwgenerator randomness
    
    The rngd kernel thread may sleep indefinitely if the entropy count is
    kept above random_write_wakeup_bits by other entropy sources. To make
    best use of multiple sources of randomness, mix entropy from hardware
    RNGs into the pool at least once within CRNG_RESEED_INTERVAL.
    
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: Jason A. Donenfeld <Jason@zx2c4.com>
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit d2a02e3c8bb6b347818518edff5a4b40ff52d6d8
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Jan 19 14:35:06 2022 +0100

    lib/crypto: blake2s: avoid indirect calls to compression function for Clang CFI
    
    blake2s_compress_generic is weakly aliased by blake2s_compress. The
    current harness for function selection uses a function pointer, which is
    ordinarily inlined and resolved at compile time. But when Clang's CFI is
    enabled, CFI still triggers when making an indirect call via a weak
    symbol. This seems like a bug in Clang's CFI, as though it's bucketing
    weak symbols and strong symbols differently. It also only seems to
    trigger when "full LTO" mode is used, rather than "thin LTO".
    
    [    0.000000][    T0] Kernel panic - not syncing: CFI failure (target: blake2s_compress_generic+0x0/0x1444)
    [    0.000000][    T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.16.0-mainline-06981-g076c855b846e #1
    [    0.000000][    T0] Hardware name: MT6873 (DT)
    [    0.000000][    T0] Call trace:
    [    0.000000][    T0]  dump_backtrace+0xfc/0x1dc
    [    0.000000][    T0]  dump_stack_lvl+0xa8/0x11c
    [    0.000000][    T0]  panic+0x194/0x464
    [    0.000000][    T0]  __cfi_check_fail+0x54/0x58
    [    0.000000][    T0]  __cfi_slowpath_diag+0x354/0x4b0
    [    0.000000][    T0]  blake2s_update+0x14c/0x178
    [    0.000000][    T0]  _extract_entropy+0xf4/0x29c
    [    0.000000][    T0]  crng_initialize_primary+0x24/0x94
    [    0.000000][    T0]  rand_initialize+0x2c/0x6c
    [    0.000000][    T0]  start_kernel+0x2f8/0x65c
    [    0.000000][    T0]  __primary_switched+0xc4/0x7be4
    [    0.000000][    T0] Rebooting in 5 seconds..
    
    Nonetheless, the function pointer method isn't so terrific anyway, so
    this patch replaces it with a simple boolean, which also gets inlined
    away. This successfully works around the Clang bug.
    
    In general, I'm not too keen on all of the indirection involved here; it
    clearly does more harm than good. Hopefully the whole thing can get
    cleaned up down the road when lib/crypto is overhauled more
    comprehensively. But for now, we go with a simple bandaid.
    
    Fixes: 6048fdcc5f26 ("lib/crypto: blake2s: include as built-in")
    Link: https://github.com/ClangBuiltLinux/linux/issues/1567
    Reported-by: Miles Chen <miles.chen@mediatek.com>
    Tested-by: Miles Chen <miles.chen@mediatek.com>
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Tested-by: John Stultz <john.stultz@linaro.org>
    Acked-by: Nick Desaulniers <ndesaulniers@google.com>
    Reviewed-by: Eric Biggers <ebiggers@google.com>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 6a00ef4493706a23120057fafbc62379bcde11ec
Author: Changbin Du <changbin.du@intel.com>
Date:   Mon Jan 17 23:44:33 2022 +0800

    riscv: eliminate unreliable __builtin_frame_address(1)
    
    I tried different pieces of code which uses __builtin_frame_address(1)
    (with both gcc version 7.5.0 and 10.3.0) to verify whether it works as
    expected on riscv64. The result is negative.
    
    What the compiler had generated is as below:
    31                      fp = (unsigned long)__builtin_frame_address(1);
       0xffffffff80006024 <+200>:   ld      s1,0(s0)
    
    It takes '0(s0)' as the address of frame 1 (caller), but the actual address
    should be '-16(s0)'.
    
              |       ...       | <-+
              +-----------------+   |
              | return address  |   |
              | previous fp     |   |
              | saved registers |   |
              | local variables |   |
      $fp --> |       ...       |   |
              +-----------------+   |
              | return address  |   |
              | previous fp --------+
              | saved registers |
      $sp --> | local variables |
              +-----------------+
    
    This leads the kernel can not dump the full stack trace on riscv.
    
    [    7.222126][    T1] Call Trace:
    [    7.222804][    T1] [<ffffffff80006058>] dump_backtrace+0x2c/0x3a
    
    This problem is not exposed on most riscv builds just because the '0(s0)'
    occasionally is the address frame 2 (caller's caller), if only ra and fp
    are stored in frame 1 (caller).
    
              |       ...       | <-+
              +-----------------+   |
              | return address  |   |
      $fp --> | previous fp     |   |
              +-----------------+   |
              | return address  |   |
              | previous fp --------+
              | saved registers |
      $sp --> | local variables |
              +-----------------+
    
    This could be a *bug* of gcc that should be fixed. But as noted in gcc
    manual "Calling this function with a nonzero argument can have
    unpredictable effects, including crashing the calling program.", let's
    remove the '__builtin_frame_address(1)' in backtrace code.
    
    With this fix now it can show full stack trace:
    [   10.444838][    T1] Call Trace:
    [   10.446199][    T1] [<ffffffff8000606c>] dump_backtrace+0x2c/0x3a
    [   10.447711][    T1] [<ffffffff800060ac>] show_stack+0x32/0x3e
    [   10.448710][    T1] [<ffffffff80a005c0>] dump_stack_lvl+0x58/0x7a
    [   10.449941][    T1] [<ffffffff80a005f6>] dump_stack+0x14/0x1c
    [   10.450929][    T1] [<ffffffff804c04ee>] ubsan_epilogue+0x10/0x5a
    [   10.451869][    T1] [<ffffffff804c092e>] __ubsan_handle_load_invalid_value+0x6c/0x78
    [   10.453049][    T1] [<ffffffff8018f834>] __pagevec_release+0x62/0x64
    [   10.455476][    T1] [<ffffffff80190830>] truncate_inode_pages_range+0x132/0x5be
    [   10.456798][    T1] [<ffffffff80190ce0>] truncate_inode_pages+0x24/0x30
    [   10.457853][    T1] [<ffffffff8045bb04>] kill_bdev+0x32/0x3c
    ...
    
    Signed-off-by: Changbin Du <changbin.du@gmail.com>
    Fixes: eac2f3059e02 ("riscv: stacktrace: fix the riscv stacktrace when CONFIG_FRAME_POINTER enabled")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit cff7f2237c2b494a07c90f70291588d218b77e14
Merge: 1eb7de177d407 038b8d1d1ab1c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 09:54:02 2022 -0800

    Merge tag 'ceph-for-5.17-rc3' of git://github.com/ceph/ceph-client
    
    Pull ceph fixes from Ilya Dryomov:
     "A patch to make it possible to disable zero copy path in the messenger
      to avoid checksum or authentication tag mismatches and ensuing session
      resets in case the destination buffer isn't guaranteed to be stable"
    
    * tag 'ceph-for-5.17-rc3' of git://github.com/ceph/ceph-client:
      libceph: optionally use bounce buffer on recv path in crc mode
      libceph: make recv path in secure mode work the same as send path

commit 1eb7de177d4073085e3a1cebf19d5d538d171f10
Merge: 633a8e8986eac 22e424feb6658
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 09:44:42 2022 -0800

    Merge tag '9p-for-5.17-rc3' of git://github.com/martinetd/linux
    
    Pull 9p fix from Dominique Martinet:
     "Fix 'cannot walk open fid' rule
    
      The 9p 'walk' operation requires fid arguments to not originate from
      an open or create call and we've missed that for a while as the
      servers regularly running tests with don't enforce the check and no
      active reviewer knew about the rule.
    
      Both reporters confirmed reverting this patch fixes things for them
      and looking at it further wasn't actually required... Will take more
      time for follow up and enforcing the rule more thoroughly later"
    
    * tag '9p-for-5.17-rc3' of git://github.com/martinetd/linux:
      Revert "fs/9p: search open fids first"

commit 1a6229096bb501495442ab47761d746c1ae791e1
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 4 17:24:04 2022 +0100

    rtla/trace: Error message fixup
    
    Use capital and change "tracer %s" to "%s tracer".
    
    No functional change.
    
    Link: https://lkml.kernel.org/r/361697d27431afefa64c67c323564205385c418d.1643990447.git.bristot@kernel.org
    
    Fixes: b1696371d865 ("rtla: Helper functions for rtla")
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit f35491b861290a2c8258b5f70f9bb5d5ed2a1c6f
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 4 17:24:03 2022 +0100

    rtla/utils: Fix session duration parsing
    
    Use gmtime to format the duration time. This avoids problems when the
    system uses local time different of Pisa's Local Time.
    
    Link: https://lkml.kernel.org/r/a2f0a37bc006c2561bb8ecd871cd70532b4a9f2d.1643990447.git.bristot@kernel.org
    
    Fixes: b1696371d865 ("rtla: Helper functions for rtla")
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 8619e32825fd0af82d243e585b9aa6917b99a975
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Feb 4 17:24:02 2022 +0100

    rtla: Follow kernel version
    
    To avoid having commits with new version, it is just easier to follow
    kernel version.
    
    Link: https://lkml.kernel.org/r/9c2df0d1de65cea96c7d731fe64781a2bb90c5b3.1643990447.git.bristot@kernel.org
    
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 633a8e8986eac2c9e32c76ccb9cfe0e5a898b314
Merge: dcb85f85fa6f1 d3b331fb51f32
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Feb 4 09:34:37 2022 -0800

    Merge tag '5.17-rc3-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs fixes from Steve French:
     "SMB3 client fixes including:
    
       - multiple fscache related fixes, reenabling ability to read/write to
         cached files for cifs.ko (that was temporarily disabled for cifs.ko
         a few weeks ago due to the recent fscache changes)
    
       - also includes a new fscache helper function ("query_occupancy")
         used by above
    
       - fix for multiuser mounts and NTLMSSP auth (workstation name) for
         stable
    
       - fix locking ordering problem in multichannel code
    
       - trivial malformed comment fix"
    
    * tag '5.17-rc3-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6:
      cifs: fix workstation_name for multiuser mounts
      Invalidate fscache cookie only when inode attributes are changed.
      cifs: Fix the readahead conversion to manage the batch when reading from cache
      cifs: Implement cache I/O by accessing the cache directly
      netfs, cachefiles: Add a method to query presence of data in the cache
      cifs: Transition from ->readpages() to ->readahead()
      cifs: unlock chan_lock before calling cifs_put_tcp_session
      Fix a warning about a malformed kernel doc comment in cifs

commit 07d2505b963b2d30f747dce338211f51068b8765
Author: Shuah Khan <skhan@linuxfoundation.org>
Date:   Thu Feb 3 20:49:45 2022 -0800

    kselftest/vm: revert "tools/testing/selftests/vm/userfaultfd.c: use swap() to make code cleaner"
    
    With this change, userfaultfd fails to build with undefined reference
    swap() error:
    
      userfaultfd.c: In function `userfaultfd_stress':
      userfaultfd.c:1530:17: warning: implicit declaration of function `swap'; did you mean `swab'? [-Wimplicit-function-declaration]
       1530 |                 swap(area_src, area_dst);
            |                 ^~~~
            |                 swab
      /usr/bin/ld: /tmp/ccDGOAdV.o: in function `userfaultfd_stress':
      userfaultfd.c:(.text+0x549e): undefined reference to `swap'
      /usr/bin/ld: userfaultfd.c:(.text+0x54bc): undefined reference to `swap'
      collect2: error: ld returned 1 exit status
    
    Revert the commit to fix the problem.
    
    Link: https://lkml.kernel.org/r/20220202003340.87195-1-skhan@linuxfoundation.org
    Fixes: 2c769ed7137a ("tools/testing/selftests/vm/userfaultfd.c: use swap() to make code cleaner")
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Minghao Chi <chi.minghao@zte.com.cn>
    
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6a0fb704b05cd143dfe2c6a4969c41c59a04b330
Author: Mike Rapoport <rppt@kernel.org>
Date:   Thu Feb 3 20:49:41 2022 -0800

    MAINTAINERS: update rppt's email
    
    Use my @kernel.org address
    
    Link: https://lkml.kernel.org/r/20220203090324.3701774-1-rppt@kernel.org
    Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c10a0f877fe007021d70f9cada240f42adc2b5db
Author: Lang Yu <lang.yu@amd.com>
Date:   Thu Feb 3 20:49:37 2022 -0800

    mm/kmemleak: avoid scanning potential huge holes
    
    When using devm_request_free_mem_region() and devm_memremap_pages() to
    add ZONE_DEVICE memory, if requested free mem region's end pfn were
    huge(e.g., 0x400000000), the node_end_pfn() will be also huge (see
    move_pfn_range_to_zone()).  Thus it creates a huge hole between
    node_start_pfn() and node_end_pfn().
    
    We found on some AMD APUs, amdkfd requested such a free mem region and
    created a huge hole.  In such a case, following code snippet was just
    doing busy test_bit() looping on the huge hole.
    
      for (pfn = start_pfn; pfn < end_pfn; pfn++) {
            struct page *page = pfn_to_online_page(pfn);
                    if (!page)
                            continue;
            ...
      }
    
    So we got a soft lockup:
    
      watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [bash:1221]
      CPU: 6 PID: 1221 Comm: bash Not tainted 5.15.0-custom #1
      RIP: 0010:pfn_to_online_page+0x5/0xd0
      Call Trace:
        ? kmemleak_scan+0x16a/0x440
        kmemleak_write+0x306/0x3a0
        ? common_file_perm+0x72/0x170
        full_proxy_write+0x5c/0x90
        vfs_write+0xb9/0x260
        ksys_write+0x67/0xe0
        __x64_sys_write+0x1a/0x20
        do_syscall_64+0x3b/0xc0
        entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    I did some tests with the patch.
    
    (1) amdgpu module unloaded
    
    before the patch:
    
      real    0m0.976s
      user    0m0.000s
      sys     0m0.968s
    
    after the patch:
    
      real    0m0.981s
      user    0m0.000s
      sys     0m0.973s
    
    (2) amdgpu module loaded
    
    before the patch:
    
      real    0m35.365s
      user    0m0.000s
      sys     0m35.354s
    
    after the patch:
    
      real    0m1.049s
      user    0m0.000s
      sys     0m1.042s
    
    Link: https://lkml.kernel.org/r/20211108140029.721144-1-lang.yu@amd.com
    Signed-off-by: Lang Yu <lang.yu@amd.com>
    Acked-by: David Hildenbrand <david@redhat.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 520ba724061cef59763e2b6f5b26e8387c2e5822
Author: Minghao Chi <chi.minghao@zte.com.cn>
Date:   Thu Feb 3 20:49:33 2022 -0800

    ipc/sem: do not sleep with a spin lock held
    
    We can't call kvfree() with a spin lock held, so defer it.
    
    Link: https://lkml.kernel.org/r/20211223031207.556189-1-chi.minghao@zte.com.cn
    Fixes: fc37a3b8b438 ("[PATCH] ipc sem: use kvmalloc for sem_undo allocation")
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
    Reviewed-by: Shakeel Butt <shakeelb@google.com>
    Reviewed-by: Manfred Spraul <manfred@colorfullife.com>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Yang Guang <cgel.zte@gmail.com>
    Cc: Davidlohr Bueso <dbueso@suse.de>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>
    Cc: Vasily Averin <vvs@virtuozzo.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 314c459a6fe0957b5885fbc65c53d51444092880
Author: Mike Rapoport <rppt@kernel.org>
Date:   Thu Feb 3 20:49:29 2022 -0800

    mm/pgtable: define pte_index so that preprocessor could recognize it
    
    Since commit 974b9b2c68f3 ("mm: consolidate pte_index() and
    pte_offset_*() definitions") pte_index is a static inline and there is
    no define for it that can be recognized by the preprocessor.  As a
    result, vm_insert_pages() uses slower loop over vm_insert_page() instead
    of insert_pages() that amortizes the cost of spinlock operations when
    inserting multiple pages.
    
    Link: https://lkml.kernel.org/r/20220111145457.20748-1-rppt@kernel.org
    Fixes: 974b9b2c68f3 ("mm: consolidate pte_index() and pte_offset_*() definitions")
    Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
    Reported-by: Christian Dietrich <stettberger@dokucode.de>
    Reviewed-by: Khalid Aziz <khalid.aziz@oracle.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 80110bbfbba6f0078d5a1cbc8df004506db8ffe5
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Thu Feb 3 20:49:24 2022 -0800

    mm/page_table_check: check entries at pmd levels
    
    syzbot detected a case where the page table counters were not properly
    updated.
    
      syzkaller login:  ------------[ cut here ]------------
      kernel BUG at mm/page_table_check.c:162!
      invalid opcode: 0000 [#1] PREEMPT SMP KASAN
      CPU: 0 PID: 3099 Comm: pasha Not tainted 5.16.0+ #48
      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIO4
      RIP: 0010:__page_table_check_zero+0x159/0x1a0
      Call Trace:
       free_pcp_prepare+0x3be/0xaa0
       free_unref_page+0x1c/0x650
       free_compound_page+0xec/0x130
       free_transhuge_page+0x1be/0x260
       __put_compound_page+0x90/0xd0
       release_pages+0x54c/0x1060
       __pagevec_release+0x7c/0x110
       shmem_undo_range+0x85e/0x1250
      ...
    
    The repro involved having a huge page that is split due to uprobe event
    temporarily replacing one of the pages in the huge page.  Later the huge
    page was combined again, but the counters were off, as the PTE level was
    not properly updated.
    
    Make sure that when PMD is cleared and prior to freeing the level the
    PTEs are updated.
    
    Link: https://lkml.kernel.org/r/20220131203249.2832273-5-pasha.tatashin@soleen.com
    Fixes: df4e817b7108 ("mm: page table check")
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Zi Yan <ziy@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e59a47b8a45353d9ee234aab2d229474e09885df
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Thu Feb 3 20:49:20 2022 -0800

    mm/khugepaged: unify collapse pmd clear, flush and free
    
    Unify the code that flushes, clears pmd entry, and frees the PTE table
    level into a new function collapse_and_free_pmd().
    
    This cleanup is useful as in the next patch we will add another call to
    this function to iterate through PTE prior to freeing the level for page
    table check.
    
    Link: https://lkml.kernel.org/r/20220131203249.2832273-4-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Zi Yan <ziy@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 64d8b9e14512ceb7bf11b235faeb8531aeb4d9d3
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Thu Feb 3 20:49:15 2022 -0800

    mm/page_table_check: use unsigned long for page counters and cleanup
    
    For consistency, use "unsigned long" for all page counters.
    
    Also, reduce code duplication by calling __page_table_check_*_clear()
    from __page_table_check_*_set() functions.
    
    Link: https://lkml.kernel.org/r/20220131203249.2832273-3-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Reviewed-by: Wei Xu <weixugc@google.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Zi Yan <ziy@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit fb5222aae64fe25e5f3ebefde8214dcf3ba33ca5
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Thu Feb 3 20:49:10 2022 -0800

    mm/debug_vm_pgtable: remove pte entry from the page table
    
    Patch series "page table check fixes and cleanups", v5.
    
    This patch (of 4):
    
    The pte entry that is used in pte_advanced_tests() is never removed from
    the page table at the end of the test.
    
    The issue is detected by page_table_check, to repro compile kernel with
    the following configs:
    
    CONFIG_DEBUG_VM_PGTABLE=y
    CONFIG_PAGE_TABLE_CHECK=y
    CONFIG_PAGE_TABLE_CHECK_ENFORCED=y
    
    During the boot the following BUG is printed:
    
      debug_vm_pgtable: [debug_vm_pgtable         ]: Validating architecture page table helpers
      ------------[ cut here ]------------
      kernel BUG at mm/page_table_check.c:162!
      invalid opcode: 0000 [#1] PREEMPT SMP PTI
      CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.16.0-11413-g2c271fe77d52 #3
      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
      ...
    
    The entry should be properly removed from the page table before the page
    is released to the free list.
    
    Link: https://lkml.kernel.org/r/20220131203249.2832273-1-pasha.tatashin@soleen.com
    Link: https://lkml.kernel.org/r/20220131203249.2832273-2-pasha.tatashin@soleen.com
    Fixes: a5c3b9ffb0f4 ("mm/debug_vm_pgtable: add tests validating advanced arch page table helpers")
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Reviewed-by: Zi Yan <ziy@nvidia.com>
    Tested-by: Zi Yan <ziy@nvidia.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: <stable@vger.kernel.org>    [5.9+]
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a85468b766d3bc17c8b17ed23a36ef6469340bb2
Author: Chen Wandun <chenwandun@huawei.com>
Date:   Thu Feb 3 20:49:06 2022 -0800

    Revert "mm/page_isolation: unset migratetype directly for non Buddy page"
    
    This reverts commit 721fb891ad0b3956d5c168b2931e3e5e4fb7ca40.
    
    Commit 721fb891ad0b ("mm/page_isolation: unset migratetype directly for
    non Buddy page") will result memory that should in buddy disappear by
    mistake.  move_freepages_block moves all pages in pageblock instead of
    pages indicated by input parameter, so if input pages is not in buddy
    but other pages in pageblock is in buddy, it will result in page out of
    control.
    
    Link: https://lkml.kernel.org/r/20220126024436.13921-1-chenwandun@huawei.com
    Fixes: 721fb891ad0b ("mm/page_isolation: unset migratetype directly for non Buddy page")
    Signed-off-by: Chen Wandun <chenwandun@huawei.com>
    Reported-by: "kernelci.org bot" <bot@kernelci.org>
    Acked-by: David Hildenbrand <david@redhat.com>
    Tested-by: Dong Aisheng <aisheng.dong@nxp.com>
    Tested-by: Francesco Dolcini <francesco.dolcini@toradex.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Tested-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 40106e005bd9764f84ef9e6c0979fe1126d7ff02
Merge: fe68195daf34d d1ca60efc53d6
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Feb 4 08:47:41 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    1) Don't refresh timeout for SCTP flows in CLOSED state.
    
    2) Don't allow access to transport header if fragment offset is set on.
    
    3) Reinitialize internal conntrack state for retransmitted TCP
       syn-ack packet.
    
    4) Update MAINTAINER file to add the Netfilter group tree. Moving
       forward, Florian Westphal has access to this tree so he can also
       send pull requests.
    
    5) Set on IPS_HELPER for entries created via ctnetlink, otherwise NAT
       might zap it.
    
    All patches from Florian Westphal.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf:
      netfilter: ctnetlink: disable helper autoassign
      MAINTAINERS: netfilter: update git links
      netfilter: conntrack: re-init state for retransmitted syn-ack
      netfilter: conntrack: move synack init code to helper
      netfilter: nft_payload: don't allow th access for fragments
      netfilter: conntrack: don't refresh sctp entries in closed state
    ====================
    
    Link: https://lore.kernel.org/r/20220204151903.320786-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f0a6fd1527067da537e9c48390237488719948ed
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Tue Feb 1 14:09:51 2022 +0100

    cfg80211: fix race in netlink owner interface destruction
    
    My previous fix here to fix the deadlock left a race where
    the exact same deadlock (see the original commit referenced
    below) can still happen if cfg80211_destroy_ifaces() already
    runs while nl80211_netlink_notify() is still marking some
    interfaces as nl_owner_dead.
    
    The race happens because we have two loops here - first we
    dev_close() all the netdevs, and then we destroy them. If we
    also have two netdevs (first one need only be a wdev though)
    then we can find one during the first iteration, close it,
    and go to the second iteration -- but then find two, and try
    to destroy also the one we didn't close yet.
    
    Fix this by only iterating once.
    
    Reported-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Fixes: ea6b2098dd02 ("cfg80211: fix locking in netlink owner interface destruction")
    Tested-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Link: https://lore.kernel.org/r/20220201130951.22093-1-johannes@sipsolutions.net
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit c0689e46be23160d925dca95dfc411f1a0462708
Author: Jonas Malaco <jonas@protocubo.io>
Date:   Thu Feb 3 13:49:52 2022 -0300

    eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
    
    Commit effa453168a7 ("i2c: i801: Don't silently correct invalid transfer
    size") revealed that ee1004_eeprom_read() did not properly limit how
    many bytes to read at once.
    
    In particular, i2c_smbus_read_i2c_block_data_or_emulated() takes the
    length to read as an u8.  If count == 256 after taking into account the
    offset and page boundary, the cast to u8 overflows.  And this is common
    when user space tries to read the entire EEPROM at once.
    
    To fix it, limit each read to I2C_SMBUS_BLOCK_MAX (32) bytes, already
    the maximum length i2c_smbus_read_i2c_block_data_or_emulated() allows.
    
    Fixes: effa453168a7 ("i2c: i801: Don't silently correct invalid transfer size")
    Cc: stable@vger.kernel.org
    Reviewed-by: Heiner Kallweit <hkallweit1@gmail.com>
    Signed-off-by: Jonas Malaco <jonas@protocubo.io>
    Link: https://lore.kernel.org/r/20220203165024.47767-1-jonas@protocubo.io
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 28cb138f559f8c1a1395f5564f86b8bbee83631b
Author: Jakob Koschel <jakobkoschel@gmail.com>
Date:   Thu Jan 27 15:44:05 2022 +0100

    vt_ioctl: add array_index_nospec to VT_ACTIVATE
    
    in vt_setactivate an almost identical code path has been patched
    with array_index_nospec. In the VT_ACTIVATE path the user input
    is from a system call argument instead of a usercopy.
    For consistency both code paths should have the same mitigations
    applied.
    
    Kasper Acknowledgements: Jakob Koschel, Brian Johannesmeyer, Kaveh
    Razavi, Herbert Bos, Cristiano Giuffrida from the VUSec group at VU
    Amsterdam.
    
    Co-developed-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com>
    Signed-off-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com>
    Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
    Link: https://lore.kernel.org/r/20220127144406.3589293-2-jakobkoschel@gmail.com
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 61cc70d9e8ef5b042d4ed87994d20100ec8896d9
Author: Jakob Koschel <jakobkoschel@gmail.com>
Date:   Thu Jan 27 15:44:04 2022 +0100

    vt_ioctl: fix array_index_nospec in vt_setactivate
    
    array_index_nospec ensures that an out-of-bounds value is set to zero
    on the transient path. Decreasing the value by one afterwards causes
    a transient integer underflow. vsa.console should be decreased first
    and then sanitized with array_index_nospec.
    
    Kasper Acknowledgements: Jakob Koschel, Brian Johannesmeyer, Kaveh
    Razavi, Herbert Bos, Cristiano Giuffrida from the VUSec group at VU
    Amsterdam.
    
    Co-developed-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com>
    Signed-off-by: Brian Johannesmeyer <bjohannesmeyer@gmail.com>
    Signed-off-by: Jakob Koschel <jakobkoschel@gmail.com>
    Link: https://lore.kernel.org/r/20220127144406.3589293-1-jakobkoschel@gmail.com
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5d5ead5e1cafa6a6076e8c3b55f707eafc76bfbd
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Thu Feb 3 17:00:26 2022 +0200

    serial: 8250_pericom: Revert "Re-enable higher baud rates"
    
    UPF_MAGIC_MULTIPLIER is userspace available bit and can be changed
    at any time. There is no sense to rely on it to be always present.
    
    This reverts commit b4ccaf5aa2d795ee7f47a6eeb209f3de981e1929.
    
    Note, that code was not reliably worked before, hence it implies
    no functional change.
    
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Fixes: b4ccaf5aa2d7 ("serial: 8250_pericom: Re-enable higher baud rates")
    Link: https://lore.kernel.org/r/20220203150026.19087-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 9b45a7738eec52bf0f5d8d3d54e822962781c5f2
Author: Joerg Roedel <jroedel@suse.de>
Date:   Fri Feb 4 12:55:37 2022 +0100

    iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
    
    The polling loop for the register change in iommu_ga_log_enable() needs
    to have a udelay() in it.  Otherwise the CPU might be faster than the
    IOMMU hardware and wrongly trigger the WARN_ON() further down the code
    stream. Use a 10us for udelay(), has there is some hardware where
    activation of the GA log can take more than a 100ms.
    
    A future optimization should move the activation check of the GA log
    to the point where it gets used for the first time. But that is a
    bigger change and not suitable for a fix.
    
    Fixes: 8bda0cfbdc1a ("iommu/amd: Detect and initialize guest vAPIC log")
    Signed-off-by: Joerg Roedel <jroedel@suse.de>
    Link: https://lore.kernel.org/r/20220204115537.3894-1-joro@8bytes.org

commit fe68195daf34d5dddacd3f93dd3eafc4beca3a0e
Author: Samuel Mendoza-Jonas <samjonas@amazon.com>
Date:   Thu Feb 3 14:49:16 2022 -0800

    ixgbevf: Require large buffers for build_skb on 82599VF
    
    From 4.17 onwards the ixgbevf driver uses build_skb() to build an skb
    around new data in the page buffer shared with the ixgbe PF.
    This uses either a 2K or 3K buffer, and offsets the DMA mapping by
    NET_SKB_PAD + NET_IP_ALIGN. When using a smaller buffer RXDCTL is set to
    ensure the PF does not write a full 2K bytes into the buffer, which is
    actually 2K minus the offset.
    
    However on the 82599 virtual function, the RXDCTL mechanism is not
    available. The driver attempts to work around this by using the SET_LPE
    mailbox method to lower the maximm frame size, but the ixgbe PF driver
    ignores this in order to keep the PF and all VFs in sync[0].
    
    This means the PF will write up to the full 2K set in SRRCTL, causing it
    to write NET_SKB_PAD + NET_IP_ALIGN bytes past the end of the buffer.
    With 4K pages split into two buffers, this means it either writes
    NET_SKB_PAD + NET_IP_ALIGN bytes past the first buffer (and into the
    second), or NET_SKB_PAD + NET_IP_ALIGN bytes past the end of the DMA
    mapping.
    
    Avoid this by only enabling build_skb when using "large" buffers (3K).
    These are placed in each half of an order-1 page, preventing the PF from
    writing past the end of the mapping.
    
    [0]: Technically it only ever raises the max frame size, see
    ixgbe_set_vf_lpe() in ixgbe_sriov.c
    
    Fixes: f15c5ba5b6cd ("ixgbevf: add support for using order 1 pages to receive large frames")
    Signed-off-by: Samuel Mendoza-Jonas <samjonas@amazon.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dd7f5a11ac5a6f733f422dc22b4d145d3260304e
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Jan 31 22:02:46 2022 +0100

    PCI/MSI: Remove bogus warning in pci_irq_get_affinity()
    
    The recent overhaul of pci_irq_get_affinity() introduced a regression when
    pci_irq_get_affinity() is called for an MSI-X interrupt which was not
    allocated with affinity descriptor information.
    
    The original code just returned a NULL pointer in that case, but the rework
    added a WARN_ON() under the assumption that the corresponding WARN_ON() in
    the MSI case can be applied to MSI-X as well.
    
    In fact the MSI warning in the original code does not make sense either
    because it's legitimate to invoke pci_irq_get_affinity() for a MSI
    interrupt which was not allocated with affinity descriptor information.
    
    Remove it and just return NULL as the original code did.
    
    Fixes: f48235900182 ("PCI/MSI: Simplify pci_irq_get_affinity()")
    Reported-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Link: https://lore.kernel.org/r/87ee4n38sm.ffs@tglx

commit 6e37ec8825a113bc2dd1b280be10e5ac6eb4f6b1
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Feb 2 00:51:57 2022 +0000

    KVM: x86: Use ERR_PTR_USR() to return -EFAULT as a __user pointer
    
    Use ERR_PTR_USR() when returning -EFAULT from kvm_get_attr_addr(), sparse
    complains about implicitly casting the kernel pointer from ERR_PTR() into
    a __user pointer.
    
    >> arch/x86/kvm/x86.c:4342:31: sparse: sparse: incorrect type in return expression
       (different address spaces) @@     expected void [noderef] __user * @@     got void * @@
       arch/x86/kvm/x86.c:4342:31: sparse:     expected void [noderef] __user *
       arch/x86/kvm/x86.c:4342:31: sparse:     got void *
    >> arch/x86/kvm/x86.c:4342:31: sparse: sparse: incorrect type in return expression
       (different address spaces) @@     expected void [noderef] __user * @@     got void * @@
       arch/x86/kvm/x86.c:4342:31: sparse:     expected void [noderef] __user *
       arch/x86/kvm/x86.c:4342:31: sparse:     got void *
    
    No functional change intended.
    
    Fixes: 56f289a8d23a ("KVM: x86: Add a helper to retrieve userspace address from kvm_device_attr")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220202005157.2545816-1-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e6b03375132fefddc55cf700418cf794b3884e0c
Author: Lutz Koschorreck <theleks@ko-hh.de>
Date:   Fri Jan 28 20:31:50 2022 +0100

    arm64: dts: meson-sm1-odroid: fix boot loop after reboot
    
    Since the correct gpio pin is used for enabling tf-io regulator the
    system did not boot correctly after calling reboot.
    
    [   36.862443] reboot: Restarting system
    bl31 reboot reason: 0xd
    bl31 reboot reason: 0x0
    system cmd  1.
    SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:B;RCY:0;SPINOR:0;CHK:1F;EMMC:800;NAND:81;SD?:0;SD:0;READ:0;0.0;CHK:0;
    bl2_stage_init 0x01
    bl2_stage_init 0x81
    hw id:
    SM1:BL:511f6b:81ca2f;FEAT:A0F83180:20282000;POC:B;RCY:0;SPINOR:0;CHK:1F;EMMC:800;NAND:81;SD?:0;SD:400;USB:8;LOOP:1;...
    
    Setting the gpio to open drain solves the issue.
    
    Fixes: 1f80a5cf74a6 ("arm64: dts: meson-sm1-odroid: add missing enable gpio and supply for tf_io regulator")
    Signed-off-by: Lutz Koschorreck <theleks@ko-hh.de>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    [narmstrong: reduced serial log & removed invalid character in commit message]
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20220128193150.GA1304381@odroid-VirtualBox

commit f26573e2bc9dfd551a0d5c6971f18cc546543312
Author: Christian Hewitt <christianshewitt@gmail.com>
Date:   Wed Jan 26 04:49:54 2022 +0000

    arm64: dts: meson-g12: drop BL32 region from SEI510/SEI610
    
    The BL32/TEE reserved-memory region is now inherited from the common
    family dtsi (meson-g12-common) so we can drop it from board files.
    
    Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Reviewed-by: Kevin Hilman <khilman@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20220126044954.19069-4-christianshewitt@gmail.com

commit 08982a1b3aa2611c9c711d24825c9002d28536f4
Author: Christian Hewitt <christianshewitt@gmail.com>
Date:   Wed Jan 26 04:49:53 2022 +0000

    arm64: dts: meson-g12: add ATF BL32 reserved-memory region
    
    Add an additional reserved memory region for the BL32 trusted firmware
    present in many devices that boot from Amlogic vendor u-boot.
    
    Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Reviewed-by: Kevin Hilman <khilman@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20220126044954.19069-3-christianshewitt@gmail.com

commit 76577c9137456febb05b0e17d244113196a98968
Author: Christian Hewitt <christianshewitt@gmail.com>
Date:   Wed Jan 26 04:49:52 2022 +0000

    arm64: dts: meson-gx: add ATF BL32 reserved-memory region
    
    Add an additional reserved memory region for the BL32 trusted firmware
    present in many devices that boot from Amlogic vendor u-boot.
    
    Suggested-by: Mateusz Krzak <kszaquitto@gmail.com>
    Signed-off-by: Christian Hewitt <christianshewitt@gmail.com>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Reviewed-by: Kevin Hilman <khilman@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20220126044954.19069-2-christianshewitt@gmail.com

commit a5be3e5d46f373fe1d2ee835c7ede31769c241cd
Author: Dongjin Kim <tobetter@gmail.com>
Date:   Fri Jan 28 00:16:56 2022 +0900

    arm64: dts: meson-sm1-bananapi-m5: fix wrong GPIO domain for GPIOE_2
    
    GPIOE_2 is in AO domain and "<&gpio GPIOE_2 ...>" changes the state of
    TF_PWR_EN of 'FC8731' on BPI-M5
    
    Fixes: 976e920183e4 ("arm64: dts: meson-sm1: add Banana PI BPI-M5 board dts")
    
    Signed-off-by: Dongjin Kim <tobetter@gmail.com>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20220127151656.GA2419733@paju

commit 323ca765bfe9d637fa774373baec0bc41e51fcfa
Author: Lutz Koschorreck <theleks@ko-hh.de>
Date:   Thu Jan 27 14:05:37 2022 +0100

    arm64: dts: meson-sm1-odroid: use correct enable-gpio pin for tf-io regulator
    
    The interrupt pin of the external ethernet phy is used, instead of the
    enable-gpio pin of the tf-io regulator. The GPIOE_2 pin is located in
    the gpio_ao bank.
    
    This causes phy interrupt problems at system startup.
    [   76.645190] irq 36: nobody cared (try booting with the "irqpoll" option)
    [   76.649617] CPU: 0 PID: 1416 Comm: irq/36-0.0:00 Not tainted 5.16.0 #2
    [   76.649629] Hardware name: Hardkernel ODROID-HC4 (DT)
    [   76.649635] Call trace:
    [   76.649638]  dump_backtrace+0x0/0x1c8
    [   76.649658]  show_stack+0x14/0x60
    [   76.649667]  dump_stack_lvl+0x64/0x7c
    [   76.649676]  dump_stack+0x14/0x2c
    [   76.649683]  __report_bad_irq+0x38/0xe8
    [   76.649695]  note_interrupt+0x220/0x3a0
    [   76.649704]  handle_irq_event_percpu+0x58/0x88
    [   76.649713]  handle_irq_event+0x44/0xd8
    [   76.649721]  handle_fasteoi_irq+0xa8/0x130
    [   76.649730]  generic_handle_domain_irq+0x38/0x58
    [   76.649738]  gic_handle_irq+0x9c/0xb8
    [   76.649747]  call_on_irq_stack+0x28/0x38
    [   76.649755]  do_interrupt_handler+0x7c/0x80
    [   76.649763]  el1_interrupt+0x34/0x80
    [   76.649772]  el1h_64_irq_handler+0x14/0x20
    [   76.649781]  el1h_64_irq+0x74/0x78
    [   76.649788]  irq_finalize_oneshot.part.56+0x68/0xf8
    [   76.649796]  irq_thread_fn+0x5c/0x98
    [   76.649804]  irq_thread+0x13c/0x260
    [   76.649812]  kthread+0x144/0x178
    [   76.649822]  ret_from_fork+0x10/0x20
    [   76.649830] handlers:
    [   76.653170] [<0000000025a6cd31>] irq_default_primary_handler threaded [<0000000093580eb7>] phy_interrupt
    [   76.661256] Disabling IRQ #36
    
    Fixes: 1f80a5cf74a6 ("arm64: dts: meson-sm1-odroid: add missing enable gpio and supply for tf_io regulator")
    Signed-off-by: Lutz Koschorreck <theleks@ko-hh.de>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    [narmstrong: removed spurious invalid & blank lines from commit message]
    Link: https://lore.kernel.org/r/20220127130537.GA187347@odroid-VirtualBox

commit bc41099f060ea74ac8d02c51bd0f5f46d969bedf
Author: Dongjin Kim <tobetter@gmail.com>
Date:   Thu Jan 27 21:29:25 2022 +0900

    arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133'
    
    Typo in audio amplifier node, dioo2133 -> dio2133
    
    Signed-off-by: Dongjin Kim <tobetter@gmail.com>
    Fixes: ef599f5f3e10 ("arm64: dts: meson: convert ODROID-N2 to dtsi")
    Fixes: 67d141c1f8e6 ("arm64: dts: meson: odroid-n2: add jack audio output support")
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/YfKQJejh0bfGYvof@anyang

commit e3bcfda012edd3564e12551b212afbd2521a1f68
Author: Jim Mattson <jmattson@google.com>
Date:   Thu Feb 3 16:13:48 2022 -0800

    KVM: x86: Report deprecated x87 features in supported CPUID
    
    CPUID.(EAX=7,ECX=0):EBX.FDP_EXCPTN_ONLY[bit 6] and
    CPUID.(EAX=7,ECX=0):EBX.ZERO_FCS_FDS[bit 13] are "defeature"
    bits. Unlike most of the other CPUID feature bits, these bits are
    clear if the features are present and set if the features are not
    present. These bits should be reported in KVM_GET_SUPPORTED_CPUID,
    because if these bits are set on hardware, they cannot be cleared in
    the guest CPUID. Doing so would claim guest support for a feature that
    the hardware doesn't support and that can't be efficiently emulated.
    
    Of course, any software (e.g WIN87EM.DLL) expecting these features to
    be present likely predates these CPUID feature bits and therefore
    doesn't know to check for them anyway.
    
    Aaron Lewis added the corresponding X86_FEATURE macros in
    commit cbb99c0f5887 ("x86/cpufeatures: Add FDP_EXCPTN_ONLY and
    ZERO_FCS_FDS"), with the intention of reporting these bits in
    KVM_GET_SUPPORTED_CPUID, but I was unable to find a proposed patch on
    the kvm list.
    
    Opportunistically reordered the CPUID_7_0_EBX capability bits from
    least to most significant.
    
    Cc: Aaron Lewis <aaronlewis@google.com>
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Message-Id: <20220204001348.2844660-1-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ac9f0c810684a1b161c18eb4b91ce84cbc13c91d
Author: Anton Lundin <glance@acc.umu.se>
Date:   Thu Feb 3 10:41:35 2022 +0100

    ata: libata-core: Introduce ATA_HORKAGE_NO_LOG_DIR horkage
    
    06f6c4c6c3e8 ("ata: libata: add missing ata_identify_page_supported() calls")
    introduced additional calls to ata_identify_page_supported(), thus also
    adding indirectly accesses to the device log directory log page through
    ata_log_supported(). Reading this log page causes SATADOM-ML 3ME devices
    to lock up.
    
    Introduce the horkage flag ATA_HORKAGE_NO_LOG_DIR to prevent accesses to
    the log directory in ata_log_supported() and add a blacklist entry
    with this flag for "SATADOM-ML 3ME" devices.
    
    Fixes: 636f6e2af4fb ("libata: add horkage for missing Identify Device log")
    Cc: stable@vger.kernel.org # v5.10+
    Signed-off-by: Anton Lundin <glance@acc.umu.se>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit d052c5d3a35fcea2d9089d76e295d7af713e8865
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Thu Feb 3 22:47:09 2022 +0300

    MAINTAINERS: add myself as Renesas R-Car SATA driver reviewer
    
    Add myself as a reviewer for the Renesas R-Car SATA driver -- I don't have
    the hardware anymore (Geert Uytterhoeven does have a lot of hardware!) but
    I do have the manuals still! :-)
    
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit f9929ef6a2a55f03aac61248c6a3a987b8546f2a
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Tue Feb 1 18:20:34 2022 +0900

    ksmbd: add support for key exchange
    
    When mounting cifs client, can see the following warning message.
    
    CIFS: decode_ntlmssp_challenge: authentication has been weakened as server
    does not support key exchange
    
    To remove this warning message, Add support for key exchange feature to
    ksmbd. This patch decrypts 16-byte ciphertext value sent by the client
    using RC4 with session key. The decrypted value is the recovered secondary
    key that will use instead of the session key for signing and sealing.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit deae24b0b13ff5f46022124fbfc2c72fc534bc6a
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Sun Jan 30 18:28:11 2022 +0900

    ksmbd: reduce smb direct max read/write size
    
    ksmbd does not support more than one Buffer Descriptor V1 element in
    an smbdirect protocol request. Reducing the maximum read/write size to
    about 512KB allows interoperability with Windows over a wider variety
    of RDMA NICs, as an interim workaround.
    
    Reviewed-by: Tom Talpey <tom@talpey.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 04e260948a160d3b7d622bf4c8a96fa4577c09bd
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Sun Jan 30 18:31:01 2022 +0900

    ksmbd: don't align last entry offset in smb2 query directory
    
    When checking smb2 query directory packets from other servers,
    OutputBufferLength is different with ksmbd. Other servers add an unaligned
    next offset to OutputBufferLength for the last entry.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 97550c7478a2da93e348d8c3075d92cddd473a78
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Sun Jan 30 18:28:56 2022 +0900

    ksmbd: fix same UniqueId for dot and dotdot entries
    
    ksmbd sets the inode number to UniqueId. However, the same UniqueId for
    dot and dotdot entry is set to the inode number of the parent inode.
    This patch set them using the current inode and parent inode.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 6d896d3b44cf64ab9b2483697e222098e7b72f70
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Thu Jan 20 21:10:11 2022 +0900

    ksmbd: smbd: validate buffer descriptor structures
    
    Check ChannelInfoOffset and ChannelInfoLength
    to validate buffer descriptor structures.
    And add a debug log to print the structures'
    content.
    
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 9ca3d3cd0857523c95ab8cdbb6cfe47b8f90e309
Merge: 8ea2c5187d7b4 7d73c602154df
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 4 15:48:26 2022 +1000

    Merge tag 'drm-intel-fixes-2022-02-03' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
    
    Fix GitLab issue #4698: DP monitor through Type-C dock(Dell DA310) doesn't work.
    Fixes for inconsistent engine busyness value and read timeout with GuC.
    Fix to use ALLOW_FAIL for error capture buffer allocation. Don't use
    interruptible lock on error path. Smatch fix to reject zero sized overlays.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/YfuiG8SKMKP5V/Dm@jlahtine-mobl.ger.corp.intel.com

commit 8ea2c5187d7b4901a70374415e772f1db422fb74
Merge: 7eb3848cc8c17 622c9a3a7868e
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 4 14:43:28 2022 +1000

    Merge tag 'drm-misc-fixes-2022-02-03' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * dma-buf/heaps: Fix potential spectre v1 gadget
     * drm/kmb: Fix potential out-of-bounds access
     * drm/mxsfb: Fix NULL-pointer dereference
     * drm/nouveau: Fix potential out-of-bounds access in BIOS decoding
     * fbdev: Re-add support for fbcon hardware acceleration
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yfu8mTZQUNt1RwZd@linux-uq9g

commit d1ca60efc53d665cf89ed847a14a510a81770b81
Author: Florian Westphal <fw@strlen.de>
Date:   Wed Feb 2 12:00:56 2022 +0100

    netfilter: ctnetlink: disable helper autoassign
    
    When userspace, e.g. conntrackd, inserts an entry with a specified helper,
    its possible that the helper is lost immediately after its added:
    
    ctnetlink_create_conntrack
      -> nf_ct_helper_ext_add + assign helper
        -> ctnetlink_setup_nat
          -> ctnetlink_parse_nat_setup
             -> parse_nat_setup -> nfnetlink_parse_nat_setup
                                   -> nf_nat_setup_info
                                     -> nf_conntrack_alter_reply
                                       -> __nf_ct_try_assign_helper
    
    ... and __nf_ct_try_assign_helper will zero the helper again.
    
    Set IPS_HELPER bit to bypass auto-assign logic, its unwanted, just like
    when helper is assigned via ruleset.
    
    Dropped old 'not strictly necessary' comment, it referred to use of
    rcu_assign_pointer() before it got replaced by RCU_INIT_POINTER().
    
    NB: Fixes tag intentionally incorrect, this extends the referenced commit,
    but this change won't build without IPS_HELPER introduced there.
    
    Fixes: 6714cf5465d280 ("netfilter: nf_conntrack: fix explicit helper attachment and NAT")
    Reported-by: Pham Thanh Tuyen <phamtyn@gmail.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 1f6339e034d5780ad7097c8d8c11b26e0762afba
Author: Florian Westphal <fw@strlen.de>
Date:   Sat Jan 29 18:30:18 2022 +0100

    MAINTAINERS: netfilter: update git links
    
    nf and nf-next have a new location.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 82b72cb94666b3dbd7152bb9f441b068af7a921b
Author: Florian Westphal <fw@strlen.de>
Date:   Sat Jan 29 17:47:01 2022 +0100

    netfilter: conntrack: re-init state for retransmitted syn-ack
    
    TCP conntrack assumes that a syn-ack retransmit is identical to the
    previous syn-ack.  This isn't correct and causes stuck 3whs in some more
    esoteric scenarios.  tcpdump to illustrate the problem:
    
     client > server: Flags [S] seq 1365731894, win 29200, [mss 1460,sackOK,TS val 2083035583 ecr 0,wscale 7]
     server > client: Flags [S.] seq 145824453, ack 643160523, win 65535, [mss 8952,wscale 5,TS val 3215367629 ecr 2082921663]
    
    Note the invalid/outdated synack ack number.
    Conntrack marks this syn-ack as out-of-window/invalid, but it did
    initialize the reply direction parameters based on this packets content.
    
     client > server: Flags [S] seq 1365731894, win 29200, [mss 1460,sackOK,TS val 2083036623 ecr 0,wscale 7]
    
    ... retransmit...
    
     server > client: Flags [S.], seq 145824453, ack 643160523, win 65535, [mss 8952,wscale 5,TS val 3215368644 ecr 2082921663]
    
    and another bogus synack. This repeats, then client re-uses for a new
    attempt:
    
    client > server: Flags [S], seq 2375731741, win 29200, [mss 1460,sackOK,TS val 2083100223 ecr 0,wscale 7]
    server > client: Flags [S.], seq 145824453, ack 643160523, win 65535, [mss 8952,wscale 5,TS val 3215430754 ecr 2082921663]
    
    ... but still gets a invalid syn-ack.
    
    This repeats until:
    
     server > client: Flags [S.], seq 145824453, ack 643160523, win 65535, [mss 8952,wscale 5,TS val 3215437785 ecr 2082921663]
     server > client: Flags [R.], seq 145824454, ack 643160523, win 65535, [mss 8952,wscale 5,TS val 3215443451 ecr 2082921663]
     client > server: Flags [S], seq 2375731741, win 29200, [mss 1460,sackOK,TS val 2083115583 ecr 0,wscale 7]
     server > client: Flags [S.], seq 162602410, ack 2375731742, win 65535, [mss 8952,wscale 5,TS val 3215445754 ecr 2083115583]
    
    This syn-ack has the correct ack number, but conntrack flags it as
    invalid: The internal state was created from the first syn-ack seen
    so the sequence number of the syn-ack is treated as being outside of
    the announced window.
    
    Don't assume that retransmitted syn-ack is identical to previous one.
    Treat it like the first syn-ack and reinit state.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Acked-by: Jozsef Kadlecsik <kadlec@netfilter.org>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit cc4f9d62037ebcb811f4908bba2986c01df1bd50
Author: Florian Westphal <fw@strlen.de>
Date:   Sat Jan 29 17:47:00 2022 +0100

    netfilter: conntrack: move synack init code to helper
    
    It seems more readable to use a common helper in the followup fix rather
    than copypaste or goto.
    
    No functional change intended.  The function is only called for syn-ack
    or syn in repy direction in case of simultaneous open.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Acked-by: Jozsef Kadlecsik <kadlec@netfilter.org>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit a9e8503def0fd4ed89ade1f61c315f904581d439
Author: Florian Westphal <fw@strlen.de>
Date:   Sat Jan 29 17:13:23 2022 +0100

    netfilter: nft_payload: don't allow th access for fragments
    
    Loads relative to ->thoff naturally expect that this points to the
    transport header, but this is only true if pkt->fragoff == 0.
    
    This has little effect for rulesets with connection tracking/nat because
    these enable ip defra. For other rulesets this prevents false matches.
    
    Fixes: 96518518cc41 ("netfilter: add nftables")
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 77b337196a9d87f3d6bb9b07c0436ecafbffda1e
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 28 13:13:32 2022 +0100

    netfilter: conntrack: don't refresh sctp entries in closed state
    
    Vivek Thrivikraman reported:
     An SCTP server application which is accessed continuously by client
     application.
     When the session disconnects the client retries to establish a connection.
     After restart of SCTP server application the session is not established
     because of stale conntrack entry with connection state CLOSED as below.
    
     (removing this entry manually established new connection):
    
     sctp 9 CLOSED src=10.141.189.233 [..]  [ASSURED]
    
    Just skip timeout update of closed entries, we don't want them to
    stay around forever.
    
    Reported-and-tested-by: Vivek Thrivikraman <vivek.thrivikraman@est.tech>
    Closes: https://bugzilla.netfilter.org/show_bug.cgi?id=1579
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 24331050a3e6afcd4451409831dd9ae8085a42f6
Author: Gao Xiang <hsiangkao@linux.alibaba.com>
Date:   Fri Feb 4 03:02:03 2022 +0800

    erofs: fix small compressed files inlining
    
    Prior to ztailpacking feature, it's enough that each lcluster has
    two pclusters at most, and the last pcluster should be turned into
    an uncompressed pcluster when necessary. For example,
      _________________________________________________
     |_ pcluster n-2 _|_ pcluster n-1 _|____ EOFed ____|
    
    which should be converted into:
      _________________________________________________
     |_ pcluster n-2 _|_ pcluster n-1 (uncompressed)' _|
    
    That is fine since either pcluster n-1 or (uncompressed)' takes one
    physical block.
    
    However, after ztailpacking was supported, the game is changed since
    the last pcluster can be inlined now. And such case above is quite
    common for inlining small files. Therefore, in order to inline more
    effectively, special EOF lclusters are now supported which can have
    three parts at most, as illustrated below:
      _________________________________________________
     |_ pcluster n-2 _|_ pcluster n-1 _|____ EOFed ____|
                                       ^ i_size
    
    Actually similar code exists in Yue Hu's original patchset [1], but I
    removed this part on purpose. After evaluating more real cases with
    small files, I've changed my mind.
    
    [1] https://lore.kernel.org/r/20211215094449.15162-1-huyue2@yulong.com
    
    Link: https://lore.kernel.org/r/20220203190203.30794-1-xiang@kernel.org
    Fixes: ab92184ff8f1 ("erofs: add on-disk compressed tail-packing inline support")
    Reviewed-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

commit b13e0c71856817fca67159b11abac350e41289f5
Author: Martin K. Petersen <martin.petersen@oracle.com>
Date:   Thu Feb 3 22:42:09 2022 -0500

    block: bio-integrity: Advance seed correctly for larger interval sizes
    
    Commit 309a62fa3a9e ("bio-integrity: bio_integrity_advance must update
    integrity seed") added code to update the integrity seed value when
    advancing a bio. However, it failed to take into account that the
    integrity interval might be larger than the 512-byte block layer
    sector size. This broke bio splitting on PI devices with 4KB logical
    blocks.
    
    The seed value should be advanced by bio_integrity_intervals() and not
    the number of sectors.
    
    Cc: Dmitry Monakhov <dmonakhov@openvz.org>
    Cc: stable@vger.kernel.org
    Fixes: 309a62fa3a9e ("bio-integrity: bio_integrity_advance must update integrity seed")
    Tested-by: Dmitry Ivanov <dmitry.ivanov2@hpe.com>
    Reported-by: Alexey Lyashkov <alexey.lyashkov@hpe.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
    Link: https://lore.kernel.org/r/20220204034209.4193-1-martin.petersen@oracle.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 7eb3848cc8c17a822f4cced5da0aa437e0063097
Merge: 26291c54e111f e8ae38720e1a6
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Feb 4 13:18:55 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-02-02' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-02-02:
    
    amdgpu:
    - mGPU fan boost fix for beige goby
    - S0ix fixes
    - Cyan skillfish hang fix
    - DCN fixes for DCN 3.1
    - DCN fixes for DCN 3.01
    - Apple retina panel fix
    - ttm logic inversion fix
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220203035224.5801-1-alexander.deucher@amd.com

commit ed14fc7a79ab43e9f2cb1fa9c1733fdc133bba30
Author: Steen Hegelund <steen.hegelund@microchip.com>
Date:   Thu Feb 3 11:29:00 2022 +0100

    net: sparx5: Fix get_stat64 crash in tcpdump
    
    This problem was found with Sparx5 when the tcpdump tool requests the
    do_get_stats64 (sparx5_get_stats64) statistic.
    
    The portstats pointer was incorrectly incremented when fetching priority
    based statistics.
    
    Fixes: af4b11022e2d (net: sparx5: add ethtool configuration and statistics support)
    Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
    Link: https://lore.kernel.org/r/20220203102900.528987-1-steen.hegelund@microchip.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit dcb85f85fa6f142aae1fe86f399d4503d49f2b60
Author: Kees Cook <keescook@chromium.org>
Date:   Thu Feb 3 12:17:54 2022 -0800

    gcc-plugins/stackleak: Use noinstr in favor of notrace
    
    While the stackleak plugin was already using notrace, objtool is now a
    bit more picky.  Update the notrace uses to noinstr.  Silences the
    following objtool warnings when building with:
    
    CONFIG_DEBUG_ENTRY=y
    CONFIG_STACK_VALIDATION=y
    CONFIG_VMLINUX_VALIDATION=y
    CONFIG_GCC_PLUGIN_STACKLEAK=y
    
      vmlinux.o: warning: objtool: do_syscall_64()+0x9: call to stackleak_track_stack() leaves .noinstr.text section
      vmlinux.o: warning: objtool: do_int80_syscall_32()+0x9: call to stackleak_track_stack() leaves .noinstr.text section
      vmlinux.o: warning: objtool: exc_general_protection()+0x22: call to stackleak_track_stack() leaves .noinstr.text section
      vmlinux.o: warning: objtool: fixup_bad_iret()+0x20: call to stackleak_track_stack() leaves .noinstr.text section
      vmlinux.o: warning: objtool: do_machine_check()+0x27: call to stackleak_track_stack() leaves .noinstr.text section
      vmlinux.o: warning: objtool: .text+0x5346e: call to stackleak_erase() leaves .noinstr.text section
      vmlinux.o: warning: objtool: .entry.text+0x143: call to stackleak_erase() leaves .noinstr.text section
      vmlinux.o: warning: objtool: .entry.text+0x10eb: call to stackleak_erase() leaves .noinstr.text section
      vmlinux.o: warning: objtool: .entry.text+0x17f9: call to stackleak_erase() leaves .noinstr.text section
    
    Note that the plugin's addition of calls to stackleak_track_stack() from
    noinstr functions is expected to be safe, as it isn't runtime
    instrumentation and is self-contained.
    
    Cc: Alexander Popov <alex.popov@linux.com>
    Suggested-by: Peter Zijlstra <peterz@infradead.org>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit eb2eb5161cdbd4f0acc574ef1c3ce799b980544b
Merge: 551007a8f10af 87563a043cef0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 3 16:54:18 2022 -0800

    Merge tag 'net-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from bpf, netfilter, and ieee802154.
    
      Current release - regressions:
    
       - Partially revert "net/smc: Add netlink net namespace support", fix
         uABI breakage
    
       - netfilter:
          - nft_ct: fix use after free when attaching zone template
          - nft_byteorder: track register operations
    
      Previous releases - regressions:
    
       - ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
    
       - phy: qca8081: fix speeds lower than 2.5Gb/s
    
       - sched: fix use-after-free in tc_new_tfilter()
    
      Previous releases - always broken:
    
       - tcp: fix mem under-charging with zerocopy sendmsg()
    
       - tcp: add missing tcp_skb_can_collapse() test in
         tcp_shift_skb_data()
    
       - neigh: do not trigger immediate probes on NUD_FAILED from
         neigh_managed_work, avoid a deadlock
    
       - bpf: use VM_MAP instead of VM_ALLOC for ringbuf, avoid KASAN
         false-positives
    
       - netfilter: nft_reject_bridge: fix for missing reply from prerouting
    
       - smc: forward wakeup to smc socket waitqueue after fallback
    
       - ieee802154:
          - return meaningful error codes from the netlink helpers
          - mcr20a: fix lifs/sifs periods
          - at86rf230, ca8210: stop leaking skbs on error paths
    
       - macsec: add missing un-offload call for NETDEV_UNREGISTER of parent
    
       - ax25: add refcount in ax25_dev to avoid UAF bugs
    
       - eth: mlx5e:
          - fix SFP module EEPROM query
          - fix broken SKB allocation in HW-GRO
          - IPsec offload: fix tunnel mode crypto for non-TCP/UDP flows
    
       - eth: amd-xgbe:
          - fix skb data length underflow
          - ensure reset of the tx_timer_active flag, avoid Tx timeouts
    
       - eth: stmmac: fix runtime pm use in stmmac_dvr_remove()
    
       - eth: e1000e: handshake with CSME starts from Alder Lake platforms"
    
    * tag 'net-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (69 commits)
      ax25: fix reference count leaks of ax25_dev
      net: stmmac: ensure PTP time register reads are consistent
      net: ipa: request IPA register values be retained
      dt-bindings: net: qcom,ipa: add optional qcom,qmp property
      tools/resolve_btfids: Do not print any commands when building silently
      bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
      net, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work
      tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
      net: sparx5: do not refer to skb after passing it on
      Partially revert "net/smc: Add netlink net namespace support"
      net/mlx5e: Avoid field-overflowing memcpy()
      net/mlx5e: Use struct_group() for memcpy() region
      net/mlx5e: Avoid implicit modify hdr for decap drop rule
      net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
      net/mlx5e: IPsec: Fix crypto offload for non TCP/UDP encapsulated traffic
      net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
      net/mlx5: E-Switch, Fix uninitialized variable modact
      net/mlx5e: Fix handling of wrong devices during bond netevent
      net/mlx5e: Fix broken SKB allocation in HW-GRO
      net/mlx5e: Fix wrong calculation of header index in HW_GRO
      ...

commit 551007a8f10afdc45959ad637d6bee816716769f
Merge: 25b20ae8151b3 186edf7e368c4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 3 16:44:12 2022 -0800

    Merge tag 'selinux-pr-20220203' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux
    
    Pull selinux fix from Paul Moore:
     "One small SELinux patch to ensure that a policy structure field is
      properly reset after freeing so that we don't inadvertently do a
      double-free on certain error conditions"
    
    * tag 'selinux-pr-20220203' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux:
      selinux: fix double free of cond_list on error paths

commit 25b20ae8151b3d5289896f4f200ff790d2cdf4bf
Merge: 1f2cfdd349b76 ec049891b2dc1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 3 16:36:26 2022 -0800

    Merge tag 'linux-kselftest-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull Kselftest fixes from Shuah Khan:
     "Important fixes to several tests and documentation clarification on
      running mainline kselftest on stable releases. A few notable fixes:
    
       - fix kselftest run hang due to child processes that haven't been
         terminated. Fix signals all child processes
    
       - fix false pass/fail results from vdso_test_abi, openat2, mincore
    
       - build failures when using -j (multiple jobs) option
    
       - exec test build failure due to incorrect build rule for a run-time
         created "pipe"
    
       - zram test fixes related to interaction with zram-generator to make
         sure zram test to coordinate deleted with zram-generator
    
       - zram test compression ratio calculation fix and skipping
         max_comp_streams.
    
       - increasing rtc test timeout
    
       - cpufreq test to write test results to stdout which will necessary
         on automated test systems"
    
    * tag 'linux-kselftest-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      kselftest: Fix vdso_test_abi return status
      selftests: skip mincore.check_file_mmap when fs lacks needed support
      selftests: openat2: Skip testcases that fail with EOPNOTSUPP
      selftests: openat2: Add missing dependency in Makefile
      selftests: openat2: Print also errno in failure messages
      selftests: futex: Use variable MAKE instead of make
      selftests/exec: Remove pipe from TEST_GEN_FILES
      selftests/zram: Adapt the situation that /dev/zram0 is being used
      selftests/zram01.sh: Fix compression ratio calculation
      selftests/zram: Skip max_comp_streams interface on newer kernel
      docs/kselftest: clarify running mainline tests on stables
      kselftest: signal all child processes
      selftests: cpufreq: Write test output to stdout as well
      selftests: rtc: Increase test timeout so that all tests run

commit 87563a043cef044fed5db7967a75741cc16ad2b1
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Thu Feb 3 23:08:11 2022 +0800

    ax25: fix reference count leaks of ax25_dev
    
    The previous commit d01ffb9eee4a ("ax25: add refcount in ax25_dev
    to avoid UAF bugs") introduces refcount into ax25_dev, but there
    are reference leak paths in ax25_ctl_ioctl(), ax25_fwd_ioctl(),
    ax25_rt_add(), ax25_rt_del() and ax25_rt_opt().
    
    This patch uses ax25_dev_put() and adjusts the position of
    ax25_addr_ax25dev() to fix reference cout leaks of ax25_dev.
    
    Fixes: d01ffb9eee4a ("ax25: add refcount in ax25_dev to avoid UAF bugs")
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220203150811.42256-1-duoming@zju.edu.cn
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 80d4609008e6d696a279e39ae7458c916fcd44c1
Author: Yannick Vignon <yannick.vignon@nxp.com>
Date:   Thu Feb 3 17:00:25 2022 +0100

    net: stmmac: ensure PTP time register reads are consistent
    
    Even if protected from preemption and interrupts, a small time window
    remains when the 2 register reads could return inconsistent values,
    each time the "seconds" register changes. This could lead to an about
    1-second error in the reported time.
    
    Add logic to ensure the "seconds" and "nanoseconds" values are consistent.
    
    Fixes: 92ba6888510c ("stmmac: add the support for PTP hw clock driver")
    Signed-off-by: Yannick Vignon <yannick.vignon@nxp.com>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Link: https://lore.kernel.org/r/20220203160025.750632-1-yannick.vignon@oss.nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 77b1b8b43ec3c060ecf7e926a92b0f8772171046
Merge: 0166556a12664 7f3bdbc3f1314
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 3 13:42:38 2022 -0800

    Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf
    
    Daniel Borkmann says:
    
    ====================
    pull-request: bpf 2022-02-03
    
    We've added 6 non-merge commits during the last 10 day(s) which contain
    a total of 7 files changed, 11 insertions(+), 236 deletions(-).
    
    The main changes are:
    
    1) Fix BPF ringbuf to allocate its area with VM_MAP instead of VM_ALLOC
       flag which otherwise trips over KASAN, from Hou Tao.
    
    2) Fix unresolved symbol warning in resolve_btfids due to LSM callback
       rename, from Alexei Starovoitov.
    
    3) Fix a possible race in inc_misses_counter() when IRQ would trigger
       during counter update, from He Fengqing.
    
    4) Fix tooling infra for cross-building with clang upon probing whether
       gcc provides the standard libraries, from Jean-Philippe Brucker.
    
    5) Fix silent mode build for resolve_btfids, from Nathan Chancellor.
    
    6) Drop unneeded and outdated lirc.h header copy from tooling infra as
       BPF does not require it anymore, from Sean Young.
    
    * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf:
      tools/resolve_btfids: Do not print any commands when building silently
      bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
      tools: Ignore errors from `which' when searching a GCC toolchain
      tools headers UAPI: remove stale lirc.h
      bpf: Fix possible race in inc_misses_counter
      bpf: Fix renaming task_getsecid_subj->current_getsecid_subj.
    ====================
    
    Link: https://lore.kernel.org/r/20220203155815.25689-1-daniel@iogearbox.net
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e8db8c9cadacab5694b0d1bd5f6b3ba6a234a34c
Merge: aace2b7a93ca4 6a51abdeb259a
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Feb 3 12:37:02 2022 -0700

    Merge tag 'nvme-5.17-2022-02-03' of git://git.infradead.org/nvme into block-5.17
    
    Pull NVMe fixes from Christoph:
    
    "nvme fixes for Linux 5.17
    
     - fix a use-after-free in rdm and tcp controller reset (Sagi Grimberg)
     - fix the state check in nvmf_ctlr_matches_baseopts (Uday Shankar)"
    
    * tag 'nvme-5.17-2022-02-03' of git://git.infradead.org/nvme:
      nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
      nvme-rdma: fix possible use-after-free in transport error_recovery work
      nvme-tcp: fix possible use-after-free in transport error_recovery work
      nvme: fix a possible use-after-free in controller reset during load

commit 1f2cfdd349b7647f438c1e552dc1b983da86d830
Author: Mickaël Salaün <mic@linux.microsoft.com>
Date:   Thu Feb 3 15:50:29 2022 +0100

    printk: Fix incorrect __user type in proc_dointvec_minmax_sysadmin()
    
    The move of proc_dointvec_minmax_sysadmin() from kernel/sysctl.c to
    kernel/printk/sysctl.c introduced an incorrect __user attribute to the
    buffer argument.  I spotted this change in [1] as well as the kernel
    test robot.  Revert this change to please sparse:
    
      kernel/printk/sysctl.c:20:51: warning: incorrect type in argument 3 (different address spaces)
      kernel/printk/sysctl.c:20:51:    expected void *
      kernel/printk/sysctl.c:20:51:    got void [noderef] __user *buffer
    
    Fixes: faaa357a55e0 ("printk: move printk sysctl to printk/sysctl.c")
    Link: https://lore.kernel.org/r/20220104155024.48023-2-mic@digikod.net [1]
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Mickaël Salaün <mic@linux.microsoft.com>
    Link: https://lore.kernel.org/r/20220203145029.272640-1-mic@digikod.net
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 67d6212afda218d564890d1674bab28e8612170f
Author: Igor Pylypiv <ipylypiv@google.com>
Date:   Thu Jan 27 15:39:53 2022 -0800

    Revert "module, async: async_synchronize_full() on module init iff async is used"
    
    This reverts commit 774a1221e862b343388347bac9b318767336b20b.
    
    We need to finish all async code before the module init sequence is
    done.  In the reverted commit the PF_USED_ASYNC flag was added to mark a
    thread that called async_schedule().  Then the PF_USED_ASYNC flag was
    used to determine whether or not async_synchronize_full() needs to be
    invoked.  This works when modprobe thread is calling async_schedule(),
    but it does not work if module dispatches init code to a worker thread
    which then calls async_schedule().
    
    For example, PCI driver probing is invoked from a worker thread based on
    a node where device is attached:
    
            if (cpu < nr_cpu_ids)
                    error = work_on_cpu(cpu, local_pci_probe, &ddi);
            else
                    error = local_pci_probe(&ddi);
    
    We end up in a situation where a worker thread gets the PF_USED_ASYNC
    flag set instead of the modprobe thread.  As a result,
    async_synchronize_full() is not invoked and modprobe completes without
    waiting for the async code to finish.
    
    The issue was discovered while loading the pm80xx driver:
    (scsi_mod.scan=async)
    
    modprobe pm80xx                      worker
    ...
      do_init_module()
      ...
        pci_call_probe()
          work_on_cpu(local_pci_probe)
                                         local_pci_probe()
                                           pm8001_pci_probe()
                                             scsi_scan_host()
                                               async_schedule()
                                               worker->flags |= PF_USED_ASYNC;
                                         ...
          < return from worker >
      ...
      if (current->flags & PF_USED_ASYNC) <--- false
            async_synchronize_full();
    
    Commit 21c3c5d28007 ("block: don't request module during elevator init")
    fixed the deadlock issue which the reverted commit 774a1221e862
    ("module, async: async_synchronize_full() on module init iff async is
    used") tried to fix.
    
    Since commit 0fdff3ec6d87 ("async, kmod: warn on synchronous
    request_module() from async workers") synchronous module loading from
    async is not allowed.
    
    Given that the original deadlock issue is fixed and it is no longer
    allowed to call synchronous request_module() from async we can remove
    PF_USED_ASYNC flag to make module init consistently invoke
    async_synchronize_full() unless async module probe is requested.
    
    Signed-off-by: Igor Pylypiv <ipylypiv@google.com>
    Reviewed-by: Changyuan Lyu <changyuanl@google.com>
    Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
    Acked-by: Tejun Heo <tj@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit aace2b7a93ca48dc075af8526394bc5d43b5b148
Merge: 3e1f941dd9f33 0f9650bd838ef
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Feb 3 11:54:53 2022 -0700

    Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-5.17
    
    Pull MD fix from Song:
    
    "Please consider pulling the following fix on top of your block-5.17
     branch. It fixes a NULL ptr deref case with nowait."
    
    * 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md:
      md: fix NULL pointer deref with nowait but no mddev->queue

commit 305e6c42e8de565864431510230a8ad75c85f4d4
Merge: c36c04c2e132f 2bdfd2825c966
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 3 08:15:13 2022 -0800

    Merge branch 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
    
    Pull cgroup fixes from Tejun Heo:
    
     - Eric's fix for a long standing cgroup1 permission issue where it only
       checks for uid 0 instead of CAP which inadvertently allows
       unprivileged userns roots to modify release_agent userhelper
    
     - Fixes for the fallout from Waiman's recent cpuset work
    
    * 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
      cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
      cgroup-v1: Require capabilities to set release_agent
      cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
      cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy

commit 0166556a12664ed3d91b58b0d3a4a78404c0e7c3
Merge: 4a81f6da9cb2d 34a081761e4e3
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Feb 3 08:04:15 2022 -0800

    Merge branch 'net-ipa-enable-register-retention'
    
    Alex Elder says:
    
    ====================
    net: ipa: enable register retention
    
    With runtime power management in place, we sometimes need to issue
    a command to enable retention of IPA register values before power
    collapse.  This requires a new Device Tree property, whose presence
    will also be used to signal that the command is required.
    ====================
    
    Link: https://lore.kernel.org/r/20220201150205.468403-1-elder@linaro.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 34a081761e4e3c35381cbfad609ebae2962fe2f8
Author: Alex Elder <elder@linaro.org>
Date:   Tue Feb 1 09:02:05 2022 -0600

    net: ipa: request IPA register values be retained
    
    In some cases, the IPA hardware needs to request the always-on
    subsystem (AOSS) to coordinate with the IPA microcontroller to
    retain IPA register values at power collapse.  This is done by
    issuing a QMP request to the AOSS microcontroller.  A similar
    request ondoes that request.
    
    We must get and hold the "QMP" handle early, because we might get
    back EPROBE_DEFER for that.  But the actual request should be sent
    while we know the IPA clock is active, and when we know the
    microcontroller is operational.
    
    Fixes: 1aac309d3207 ("net: ipa: use autosuspend")
    Signed-off-by: Alex Elder <elder@linaro.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ac62a0174d62ae0f4447c0c8cf35a8e5d793df56
Author: Alex Elder <elder@linaro.org>
Date:   Tue Feb 1 09:02:04 2022 -0600

    dt-bindings: net: qcom,ipa: add optional qcom,qmp property
    
    For some systems, the IPA driver must make a request to ensure that
    its registers are retained across power collapse of the IPA hardware.
    On such systems, we'll use the existence of the "qcom,qmp" property
    as a signal that this request is required.
    
    Signed-off-by: Alex Elder <elder@linaro.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2bdfd2825c9662463371e6691b1a794e97fa36b4
Author: Waiman Long <longman@redhat.com>
Date:   Wed Feb 2 22:31:03 2022 -0500

    cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
    
    It was found that a "suspicious RCU usage" lockdep warning was issued
    with the rcu_read_lock() call in update_sibling_cpumasks().  It is
    because the update_cpumasks_hier() function may sleep. So we have
    to release the RCU lock, call update_cpumasks_hier() and reacquire
    it afterward.
    
    Also add a percpu_rwsem_assert_held() in update_sibling_cpumasks()
    instead of stating that in the comment.
    
    Fixes: 4716909cc5c5 ("cpuset: Track cpusets that use parent's effective_cpus")
    Signed-off-by: Waiman Long <longman@redhat.com>
    Tested-by: Phil Auld <pauld@redhat.com>
    Reviewed-by: Phil Auld <pauld@redhat.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit f340b3d9027485945d59f9c04f1e33070b02cae2
Author: hongnanli <hongnan.li@linux.alibaba.com>
Date:   Fri Jan 21 15:06:11 2022 +0800

    fs/ext4: fix comments mentioning i_mutex
    
    inode->i_mutex has been replaced with inode->i_rwsem long ago. Fix
    comments still mentioning i_mutex.
    
    Signed-off-by: hongnanli <hongnan.li@linux.alibaba.com>
    Link: https://lore.kernel.org/r/20220121070611.21618-1-hongnan.li@linux.alibaba.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 8fca8a2b0a822f7936130af7299d2fd7f0a66714
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Wed Jan 26 14:31:46 2022 +0800

    ext4: fix incorrect type issue during replay_del_range
    
    should not use fast commit log data directly, add le32_to_cpu().
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 0b5b5a62b945 ("ext4: use ext4_ext_remove_space() for fast commit replay delete range")
    Cc: stable@kernel.org
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Reviewed-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220126063146.2302-1-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 715a67f11d6755e0cc853ff4ef539f362b566096
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Mon Jan 10 21:28:41 2022 +0800

    jbd2: fix kernel-doc descriptions for jbd2_journal_shrink_{scan,count}()
    
    Add the description of @shrink and @sc in jbd2_journal_shrink_scan() and
    jbd2_journal_shrink_count() kernel-doc comment to remove warnings found
    by running scripts/kernel-doc, which is caused by using 'make W=1'.
    fs/jbd2/journal.c:1296: warning: Function parameter or member 'shrink'
    not described in 'jbd2_journal_shrink_scan'
    fs/jbd2/journal.c:1296: warning: Function parameter or member 'sc' not
    described in 'jbd2_journal_shrink_scan'
    fs/jbd2/journal.c:1320: warning: Function parameter or member 'shrink'
    not described in 'jbd2_journal_shrink_count'
    fs/jbd2/journal.c:1320: warning: Function parameter or member 'sc' not
    described in 'jbd2_journal_shrink_count'
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/20220110132841.34531-1-yang.lee@linux.alibaba.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 7c268d4ce2d3761f666a9950b029c8902bfab710
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Wed Jan 19 14:02:09 2022 +0100

    ext4: fix potential NULL pointer dereference in ext4_fill_super()
    
    By mistake we fail to return an error from ext4_fill_super() in case
    that ext4_alloc_sbi() fails to allocate a new sbi. Instead we just set
    the ret variable and allow the function to continue which will later
    lead to a NULL pointer dereference. Fix it by returning -ENOMEM in the
    case ext4_alloc_sbi() fails.
    
    Fixes: cebe85d570cf ("ext4: switch to the new mount api")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Link: https://lore.kernel.org/r/20220119130209.40112-1-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 4f98186848707f530669238d90e0562d92a78aab
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date:   Mon Jan 17 17:41:51 2022 +0530

    jbd2: refactor wait logic for transaction updates into a common function
    
    No functionality change as such in this patch. This only refactors the
    common piece of code which waits for t_updates to finish into a common
    function named as jbd2_journal_wait_updates(journal_t *)
    
    Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/8c564f70f4b2591171677a2a74fccb22a7b6c3a4.1642416995.git.riteshh@linux.ibm.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 3ca40c0d329113a9f76f6aa01abe73d9f16ace9d
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date:   Mon Jan 17 17:41:50 2022 +0530

    jbd2: cleanup unused functions declarations from jbd2.h
    
    During code review found no references of few of these below function
    declarations. This patch cleans those up from jbd2.h
    
    Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/30d1fc327becda197a4136cf9cdc73d9baa3b7b9.1642416995.git.riteshh@linux.ibm.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit cdce59a1549190b66f8e3fe465c2b2f714b98a94
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date:   Mon Jan 17 17:41:49 2022 +0530

    ext4: fix error handling in ext4_fc_record_modified_inode()
    
    Current code does not fully takes care of krealloc() error case, which
    could lead to silent memory corruption or a kernel bug.  This patch
    fixes that.
    
    Also it cleans up some duplicated error handling logic from various
    functions in fast_commit.c file.
    
    Reported-by: luo penghao <luo.penghao@zte.com.cn>
    Suggested-by: Lukas Czerner <lczerner@redhat.com>
    Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/62e8b6a1cce9359682051deb736a3c0953c9d1e9.1642416995.git.riteshh@linux.ibm.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 09355d9d038a1590ee055831a4ad3a79952cfa8b
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date:   Mon Jan 17 17:41:48 2022 +0530

    ext4: remove redundant max inline_size check in ext4_da_write_inline_data_begin()
    
    ext4_prepare_inline_data() already checks for ext4_get_max_inline_size()
    and returns -ENOSPC. So there is no need to check it twice within
    ext4_da_write_inline_data_begin(). This patch removes the extra check.
    
    It also makes it more clean.
    
    No functionality change in this patch.
    
    Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/cdd1654128d5105550c65fd13ca5da53b2162cc4.1642416995.git.riteshh@linux.ibm.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 897026aaa73eb2517dfea8d147f20ddb0b813044
Author: Ritesh Harjani <riteshh@linux.ibm.com>
Date:   Mon Jan 17 17:41:47 2022 +0530

    ext4: fix error handling in ext4_restore_inline_data()
    
    While running "./check -I 200 generic/475" it sometimes gives below
    kernel BUG(). Ideally we should not call ext4_write_inline_data() if
    ext4_create_inline_data() has failed.
    
    <log snip>
    [73131.453234] kernel BUG at fs/ext4/inline.c:223!
    
    <code snip>
     212 static void ext4_write_inline_data(struct inode *inode, struct ext4_iloc *iloc,
     213                                    void *buffer, loff_t pos, unsigned int len)
     214 {
    <...>
     223         BUG_ON(!EXT4_I(inode)->i_inline_off);
     224         BUG_ON(pos + len > EXT4_I(inode)->i_inline_size);
    
    This patch handles the error and prints out a emergency msg saying potential
    data loss for the given inode (since we couldn't restore the original
    inline_data due to some previous error).
    
    [ 9571.070313] EXT4-fs (dm-0): error restoring inline_data for inode -- potential data loss! (inode 1703982, error -30)
    
    Reported-by: Eric Whitney <enwlinux@gmail.com>
    Signed-off-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/9f4cd7dfd54fa58ff27270881823d94ddf78dd07.1642416995.git.riteshh@linux.ibm.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit bdc8a53a6f2f0b1cb5f991440f2100732299eb93
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Mon Jan 17 17:36:55 2022 +0800

    ext4: fast commit may miss file actions
    
    in the follow scenario:
    1. jbd start transaction n
    2. task A get new handle for transaction n+1
    3. task A do some actions and add inode to FC_Q_MAIN fc_q
    4. jbd complete transaction n and clear FC_Q_MAIN fc_q
    5. task A call fsync
    
    Fast commit will lost the file actions during a full commit.
    
    we should also add updates to staging queue during a full commit.
    and in ext4_fc_cleanup(), when reset a inode's fc track range, check
    it's i_sync_tid, if it bigger than current transaction tid, do not
    rest it, or we will lost the track range.
    
    And EXT4_MF_FC_COMMITTING is not needed anymore, so drop it.
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Link: https://lore.kernel.org/r/20220117093655.35160-3-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit e85c81ba8859a4c839bcd69c5d83b32954133a5b
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Mon Jan 17 17:36:54 2022 +0800

    ext4: fast commit may not fallback for ineligible commit
    
    For the follow scenario:
    1. jbd start commit transaction n
    2. task A get new handle for transaction n+1
    3. task A do some ineligible actions and mark FC_INELIGIBLE
    4. jbd complete transaction n and clean FC_INELIGIBLE
    5. task A call fsync
    
    In this case fast commit will not fallback to full commit and
    transaction n+1 also not handled by jbd.
    
    Make ext4_fc_mark_ineligible() also record transaction tid for
    latest ineligible case, when call ext4_fc_cleanup() check
    current transaction tid, if small than latest ineligible tid
    do not clear the EXT4_MF_FC_INELIGIBLE.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reported-by: Ritesh Harjani <riteshh@linux.ibm.com>
    Suggested-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Link: https://lore.kernel.org/r/20220117093655.35160-2-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 31a074a0c62dc0d2bfb9b543142db4fe27f9e5eb
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Mon Jan 10 11:51:41 2022 +0800

    ext4: modify the logic of ext4_mb_new_blocks_simple
    
    For now in ext4_mb_new_blocks_simple, if we found a block which
    should be excluded then will switch to next group, this may
    probably cause 'group' run out of range.
    
    Change to check next block in the same group when get a block should
    be excluded. Also change the search range to EXT4_CLUSTERS_PER_GROUP
    and add error checking.
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20220110035141.1980-3-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 599ea31d13617c5484c40cdf50d88301dc351cfc
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Mon Jan 10 11:51:40 2022 +0800

    ext4: prevent used blocks from being allocated during fast commit replay
    
    During fast commit replay procedure, we clear inode blocks bitmap in
    ext4_ext_clear_bb(), this may cause ext4_mb_new_blocks_simple() allocate
    blocks still in use.
    
    Make ext4_fc_record_regions() also record physical disk regions used by
    inodes during replay procedure. Then ext4_mb_new_blocks_simple() can
    excludes these blocks in use.
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Link: https://lore.kernel.org/r/20220110035141.1980-2-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 46963e2e0629cb31c96b1d47ddd89dc3d8990b34
Author: Mathias Krause <minipli@grsecurity.net>
Date:   Thu Jan 27 14:02:18 2022 +0100

    misc: fastrpc: avoid double fput() on failed usercopy
    
    If the copy back to userland fails for the FASTRPC_IOCTL_ALLOC_DMA_BUFF
    ioctl(), we shouldn't assume that 'buf->dmabuf' is still valid. In fact,
    dma_buf_fd() called fd_install() before, i.e. "consumed" one reference,
    leaving us with none.
    
    Calling dma_buf_put() will therefore put a reference we no longer own,
    leading to a valid file descritor table entry for an already released
    'file' object which is a straight use-after-free.
    
    Simply avoid calling dma_buf_put() and rely on the process exit code to
    do the necessary cleanup, if needed, i.e. if the file descriptor is
    still valid.
    
    Fixes: 6cffd79504ce ("misc: fastrpc: Add support for dmabuf exporter")
    Acked-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Mathias Krause <minipli@grsecurity.net>
    Link: https://lore.kernel.org/r/20220127130218.809261-1-minipli@grsecurity.net
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 7f3bdbc3f13146eb9d07de81ea71f551587a384b
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Tue Feb 1 14:25:04 2022 -0700

    tools/resolve_btfids: Do not print any commands when building silently
    
    When building with 'make -s', there is some output from resolve_btfids:
    
    $ make -sj"$(nproc)" oldconfig prepare
      MKDIR     .../tools/bpf/resolve_btfids/libbpf/
      MKDIR     .../tools/bpf/resolve_btfids//libsubcmd
      LINK     resolve_btfids
    
    Silent mode means that no information should be emitted about what is
    currently being done. Use the $(silent) variable from Makefile.include
    to avoid defining the msg macro so that there is no information printed.
    
    Fixes: fbbb68de80a4 ("bpf: Add resolve_btfids tool to resolve BTF IDs in ELF object")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Link: https://lore.kernel.org/bpf/20220201212503.731732-1-nathan@kernel.org

commit 1d118965965f89948236ebe23072bb1fca5e7832
Author: Dave Stevenson <dave.stevenson@raspberrypi.com>
Date:   Thu Jan 27 14:51:16 2022 +0100

    drm/vc4: hdmi: Allow DBLCLK modes even if horz timing is odd.
    
    The 2711 pixel valve can't produce odd horizontal timings, and
    checks were added to vc4_hdmi_encoder_atomic_check and
    vc4_hdmi_encoder_mode_valid to filter out/block selection of
    such modes.
    
    Modes with DRM_MODE_FLAG_DBLCLK double all the horizontal timing
    values before programming them into the PV. The PV values,
    therefore, can not be odd, and so the modes can be supported.
    
    Amend the filtering appropriately.
    
    Fixes: 57fb32e632be ("drm/vc4: hdmi: Block odd horizontal timings")
    Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127135116.298278-1-maxime@cerno.tech

commit 71702c495b78dfbc22eeac32ea9cda452862750d
Author: Dave Stevenson <dave.stevenson@raspberrypi.com>
Date:   Thu Jan 27 14:45:59 2022 +0100

    drm/vc4: hdmi: Don't try disabling SCDC on Pi0-3.
    
    The code that set the scdc_enabled flag to ensure it was
    disabled at boot time also ran on Pi0-3 where there is no
    SCDC support. This lead to a warning in vc4_hdmi_encoder_post_crtc_disable
    due to vc4_hdmi_disable_scrambling being called and trying to
    read (and write) register HDMI_SCRAMBLER_CTL which doesn't
    exist on those platforms.
    
    Only set the flag should the interface be configured to support
    more than HDMI 1.4.
    
    Fixes: 1998646129fa ("drm/vc4: hdmi: Introduce a scdc_enabled flag")
    Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127134559.292778-1-maxime@cerno.tech

commit 3404b39919c3c87677cdba45405d24033b3276f3
Author: Dave Stevenson <dave.stevenson@raspberrypi.com>
Date:   Thu Jan 27 14:17:54 2022 +0100

    drm/vc4: hdmi: Ensure we don't use 2711 HPD registers on Pi0-3
    
    The existing logic was flawed in that it could try reading the
    2711 specific registers for HPD on a CM1/3 where the HPD GPIO
    hadn't been defined in DT.
    
    Ensure we don't do the 2711 register read on invalid hardware,
    and then
    
    Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127131754.236074-1-maxime@cerno.tech

commit c36c04c2e132fc39f6b658bf607aed4425427fd7
Author: John Hubbard <jhubbard@nvidia.com>
Date:   Tue Feb 1 19:23:17 2022 -0800

    Revert "mm/gup: small refactoring: simplify try_grab_page()"
    
    This reverts commit 54d516b1d62ff8f17cee2da06e5e4706a0d00b8a
    
    That commit did a refactoring that effectively combined fast and slow
    gup paths (again).  And that was again incorrect, for two reasons:
    
     a) Fast gup and slow gup get reference counts on pages in different
        ways and with different goals: see Linus' writeup in commit
        cd1adf1b63a1 ("Revert "mm/gup: remove try_get_page(), call
        try_get_compound_head() directly""), and
    
     b) try_grab_compound_head() also has a specific check for
        "FOLL_LONGTERM && !is_pinned(page)", that assumes that the caller
        can fall back to slow gup. This resulted in new failures, as
        recently report by Will McVicker [1].
    
    But (a) has problems too, even though they may not have been reported
    yet.  So just revert this.
    
    Link: https://lore.kernel.org/r/20220131203504.3458775-1-willmcvicker@google.com [1]
    Fixes: 54d516b1d62f ("mm/gup: small refactoring: simplify try_grab_page()")
    Reported-and-tested-by: Will McVicker <willmcvicker@google.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Minchan Kim <minchan@google.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Christian Borntraeger <borntraeger@de.ibm.com>
    Cc: Heiko Carstens <hca@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: stable@vger.kernel.org # 5.15
    Signed-off-by: John Hubbard <jhubbard@nvidia.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d394bb77dd0bd20b125459da25fdac00a853be28
Merge: 88808fbbead48 2161ba070999a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Feb 3 06:45:34 2022 -0800

    Merge tag 'mips-fixes-5.17_2' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
    
    Pull MIPS fixes from Thomas Bogendoerfer:
    
     - fix missed change for PTR->PTR_WD conversion
    
     - kernel-doc fixes
    
    * tag 'mips-fixes-5.17_2' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux:
      MIPS: KVM: fix vz.c kernel-doc notation
      MIPS: octeon: Fix missed PTR->PTR_WD conversion

commit 3149efcdf2c6314420c418dfc94de53bfd076b1f
Author: Long Li <longli@microsoft.com>
Date:   Wed Jan 26 17:43:34 2022 -0800

    PCI: hv: Fix NUMA node assignment when kernel boots with custom NUMA topology
    
    When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
    driver should only set an online NUMA node on the device. This can happen
    during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
    
    This patch also fixes the case where kernel is booting with "numa=off".
    
    Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support PCI_BUS_RELATIONS2")
    Signed-off-by: Long Li <longli@microsoft.com>
    Reviewed-by: Michael Kelley <mikelley@microsoft.com>
    Tested-by: Purna Pavan Chandra Aekkaladevi <paekkaladevi@microsoft.com>
    Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Link: https://lore.kernel.org/r/1643247814-15184-1-git-send-email-longli@linuxonhyperv.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit 68e8cc2a23b61862bf20ffc9b782a3fb49c65568
Author: Yizhuo Zhai <yzhai003@ucr.edu>
Date:   Wed Feb 2 15:58:08 2022 -0800

    fbdev: fbmem: Fix the implicit type casting
    
    In function do_fb_ioctl(), the "arg" is the type of unsigned long,
    and in "case FBIOBLANK:" this argument is casted into an int before
    passig to fb_blank(). In fb_blank(), the comparision
    if (blank > FB_BLANK_POWERDOWN) would be bypass if the original
    "arg" is a large number, which is possible because it comes from
    the user input. Fix this by adding the check before the function
    call.
    
    Reviewed-by: Guenter Roeck <linux@roeck-us.net>
    Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
    Acked-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Yizhuo Zhai <yzhai003@ucr.edu>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220202235811.1621017-1-yzhai003@ucr.edu

commit aceeafefff736057e8f93f19bbfbef26abd94604
Author: Jens Wiklander <jens.wiklander@linaro.org>
Date:   Thu Jan 27 15:29:39 2022 +0100

    optee: use driver internal tee_context for some rpc
    
    Adds a driver private tee_context by moving the tee_context in struct
    optee_notif to struct optee. This tee_context was previously used when
    doing internal calls to secure world to deliver notification.
    
    The new driver internal tee_context is now also when allocating driver
    private shared memory. This decouples the shared memory object from its
    original tee_context. This is needed when the life time of such a memory
    allocation outlives the client tee_context.
    
    This patch fixes the problem described below:
    
    The addition of a shutdown hook by commit f25889f93184 ("optee: fix tee out
    of memory failure seen during kexec reboot") introduced a kernel shutdown
    regression that can be triggered after running the OP-TEE xtest suites.
    
    Once the shutdown hook is called it is not possible to communicate any more
    with the supplicant process because the system is not scheduling task any
    longer. Thus if the optee driver shutdown path receives a supplicant RPC
    request from the OP-TEE we will deadlock the kernel's shutdown.
    
    Fixes: f25889f93184 ("optee: fix tee out of memory failure seen during kexec reboot")
    Fixes: 217e0250cccb ("tee: use reference counting for tee_context")
    Reported-by: Lars Persson <larper@axis.com>
    Cc: stable@vger.kernel.org
    Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
    Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>

commit 868d7618d75f2cac23c2be6ca8d55ae1380c36d1
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Feb 3 11:33:02 2022 +0100

    platform/x86: thinkpad_acpi: Add dual-fan quirk for T15g (2nd gen)
    
    The ThinkPad T15g Gen 2 has 2 fan, add a TPACPI_FAN_2CTL quirk entry for
    it to the fan_quirk_table[] so that both fans can be controllerd.
    
    Reported-and-tested-by: David Dreschner <david@dreschner.net>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220203103302.49401-1-hdegoede@redhat.com

commit 1dd498e5e26ad71e3e9130daf72cfb6a693fee03
Author: James Morse <james.morse@arm.com>
Date:   Thu Jan 27 12:20:52 2022 +0000

    KVM: arm64: Workaround Cortex-A510's single-step and PAC trap errata
    
    Cortex-A510's erratum #2077057 causes SPSR_EL2 to be corrupted when
    single-stepping authenticated ERET instructions. A single step is
    expected, but a pointer authentication trap is taken instead. The
    erratum causes SPSR_EL1 to be copied to SPSR_EL2, which could allow
    EL1 to cause a return to EL2 with a guest controlled ELR_EL2.
    
    Because the conditions require an ERET into active-not-pending state,
    this is only a problem for the EL2 when EL2 is stepping EL1. In this case
    the previous SPSR_EL2 value is preserved in struct kvm_vcpu, and can be
    restored.
    
    Cc: stable@vger.kernel.org # 53960faf2b73: arm64: Add Cortex-A510 CPU part definition
    Cc: stable@vger.kernel.org
    Signed-off-by: James Morse <james.morse@arm.com>
    [maz: fixup cpucaps ordering]
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220127122052.1584324-5-james.morse@arm.com

commit 1229630af88620f6e3a621a1ebd1ca14d9340df7
Author: James Morse <james.morse@arm.com>
Date:   Thu Jan 27 12:20:51 2022 +0000

    KVM: arm64: Stop handle_exit() from handling HVC twice when an SError occurs
    
    Prior to commit defe21f49bc9 ("KVM: arm64: Move PC rollback on SError to
    HYP"), when an SError is synchronised due to another exception, KVM
    handles the SError first. If the guest survives, the instruction that
    triggered the original exception is re-exectued to handle the first
    exception. HVC is treated as a special case as the instruction wouldn't
    normally be re-exectued, as its not a trap.
    
    Commit defe21f49bc9 didn't preserve the behaviour of the 'return 1'
    that skips the rest of handle_exit().
    
    Since commit defe21f49bc9, KVM will try to handle the SError and the
    original exception at the same time. When the exception was an HVC,
    fixup_guest_exit() has already rolled back ELR_EL2, meaning if the
    guest has virtual SError masked, it will execute and handle the HVC
    twice.
    
    Restore the original behaviour.
    
    Fixes: defe21f49bc9 ("KVM: arm64: Move PC rollback on SError to HYP")
    Cc: stable@vger.kernel.org
    Signed-off-by: James Morse <james.morse@arm.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220127122052.1584324-4-james.morse@arm.com

commit 1c71dbc8a179d99dd9bb7e7fc1888db613cf85de
Author: James Morse <james.morse@arm.com>
Date:   Thu Jan 27 12:20:50 2022 +0000

    KVM: arm64: Avoid consuming a stale esr value when SError occur
    
    When any exception other than an IRQ occurs, the CPU updates the ESR_EL2
    register with the exception syndrome. An SError may also become pending,
    and will be synchronised by KVM. KVM notes the exception type, and whether
    an SError was synchronised in exit_code.
    
    When an exception other than an IRQ occurs, fixup_guest_exit() updates
    vcpu->arch.fault.esr_el2 from the hardware register. When an SError was
    synchronised, the vcpu esr value is used to determine if the exception
    was due to an HVC. If so, ELR_EL2 is moved back one instruction. This
    is so that KVM can process the SError first, and re-execute the HVC if
    the guest survives the SError.
    
    But if an IRQ synchronises an SError, the vcpu's esr value is stale.
    If the previous non-IRQ exception was an HVC, KVM will corrupt ELR_EL2,
    causing an unrelated guest instruction to be executed twice.
    
    Check ARM_EXCEPTION_CODE() before messing with ELR_EL2, IRQs don't
    update this register so don't need to check.
    
    Fixes: defe21f49bc9 ("KVM: arm64: Move PC rollback on SError to HYP")
    Cc: stable@vger.kernel.org
    Reported-by: Steven Price <steven.price@arm.com>
    Signed-off-by: James Morse <james.morse@arm.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220127122052.1584324-3-james.morse@arm.com

commit 622c9a3a7868e1eeca39c55305ca3ebec4742b64
Author: Alexander Stein <alexander.stein@ew.tq-group.com>
Date:   Wed Feb 2 09:17:55 2022 +0100

    drm: mxsfb: Fix NULL pointer dereference
    
    mxsfb should not ever dereference the NULL pointer which
    drm_atomic_get_new_bridge_state is allowed to return.
    Assume a fixed format instead.
    
    Fixes: b776b0f00f24 ("drm: mxsfb: Use bus_format from the nearest bridge if present")
    Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
    Signed-off-by: Marek Vasut <marex@denx.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220202081755.145716-3-alexander.stein@ew.tq-group.com

commit 5f06f6bf8d816578c390a2b8a485d40adcca4749
Author: Luca Coelho <luciano.coelho@intel.com>
Date:   Fri Jan 28 14:48:51 2022 +0200

    iwlwifi: mvm: don't send SAR GEO command for 3160 devices
    
    SAR GEO offsets are not supported on 3160 devices.  The code was
    refactored and caused us to start sending the command anyway, which
    causes a FW assertion failure.  Fix that only considering this feature
    supported on FW API with major version is 17 if the device is not
    3160.
    
    Additionally, fix the caller of iwl_mvm_sar_geo_init() so that it
    checks for the return value, which it was ignoring.
    
    Reported-by: Len Brown <lenb@kernel.org>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Fixes: 78a19d5285d9 ("iwlwifi: mvm: Read the PPAG and SAR tables at INIT stage")
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128144623.96f683a89b42.I14e2985bfd7ddd8a8d83eb1869b800c0e7f30db4@changeid

commit 92883a524ae918736a7b8acef98698075507b8c1
Author: Luca Coelho <luciano.coelho@intel.com>
Date:   Fri Jan 28 14:48:50 2022 +0200

    iwlwifi: remove deprecated broadcast filtering feature
    
    This feature has been deprecated and should not be used anymore.  With
    newer firmwares, namely *-67.ucode and above, trying to use it causes an
    assertion failure in the FW, similar to this:
    
    [Tue Jan 11 20:05:24 2022] iwlwifi 0000:04:00.0: 0x00001062 | ADVANCED_SYSASSERT
    
    In order to prevent this feature from being used, remove it entirely
    and get rid of the Kconfig option that
    enables it (IWLWIFI_BCAST_FILTERING).
    
    Fixes: cbaa6aeedee5 ("iwlwifi: bump FW API to 67 for AX devices")
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215488
    Cc: stable@vger.kernel.org # 5.16.x
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128144623.9241e049f13e.Ia4f282813ca2ddd24c13427823519113f2bbebf2@changeid

commit 30de48b436a08a8df651011e2d3614e26a2c592a
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Fri Jan 28 14:30:57 2022 +0200

    iwlwifi: mei: report RFKILL upon register when needed
    
    When we register and we are in link protection passive, meaning
    that the host can't touch the device, report RFKILL immediately
    upon register() and don't wait for the CSME firmware to let us
    know again about the link protection state.
    
    What happens if we wait is that the host will not see RFKILL soon
    enough and we'll have a window of time during which it can bring
    up the device which will request ownership.
    
    Fixes: 2da4366f9e2c ("iwlwifi: mei: add the driver to allow cooperation with CSME")
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.a136f9f46336.Ief7506dc3b1813a1943a5a639aa45d8e5f284f31@changeid

commit 7cf800f46e07e6b75a43036c4389d6ca717fd017
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Fri Jan 28 14:30:56 2022 +0200

    iwlwifi: mvm: don't feed the hardware RFKILL into iwlmei
    
    iwlmei can trigger a hardware RFKILL when the CSME firmware
    does not want the host to touch the device.
    But then, iwlmvm reports RFKILL which makes cfg80211 update
    iwlmvm about RFKILL. iwlmvm then thinks there is a change in
    the _software_ rfkill and it calls rfkill_blocked() to fetch
    the RFKILL state. This returns that RFKILL is blocked (because
    of iwlmei) and iwlmvm tells iwlmei that _software_ RFKILL is
    asserted.
    
    This is a bug of course.
    Fix this by checking explicitly the software RFKILL state and
    not the overall RFKILL state.
    
    Fixes: 7ce1f2157e14 ("iwlwifi: mvm: read the rfkill state and feed it to iwlmei")
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Fixes: 7ce1f2157e14 ("iwlwifi: mvm: read the rfkill state and feed it to iwlmei")
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.f293861a3f92.I9553d27df1de6fd5756a43ea5f8b89d06fa1a6f2@changeid

commit 44bf7c4667efe10390aa59eda39833a9a0439b5b
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Fri Jan 28 14:30:55 2022 +0200

    iwlwifi: mei: retry mapping the shared area
    
    The shared area is a DMA memory allocated in the host and
    mapped so that the host and the CSME firmware can
    exchange data. It is mapped through a dedicated PCI device
    that is driven by the mei bus driver.
    
    The bus driver is in charge of allocating and mapping this
    memory. It also needs to configure the CSME firmware with
    a specific set of commands, so that the CSME firmware will
    know that this memory is meant to be used by its internal
    WLAN module.
    
    For this, the CSME firmware first needs to completely
    initialize its WLAN module and only then get the mapping
    request.
    
    The problem is that the mei bus enumeration completes
    before the WLAN is completely ready. This means that
    the WLAN module's initialization is racing with iwlmei's
    allocation and mapping flow.
    
    Testing showed a problem in resume flows where iwlmei
    was too fast and the DMA mapping failed.
    
    Add a retry mechanism to make sure that we will succeed
    to map the memory.
    
    Fixes: 2da4366f9e2c ("iwlwifi: mei: add the driver to allow cooperation with CSME")
    Fixes: bcbddc4f9d02 ("iwlwifi: mei: wait before mapping the shared area")
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.cc51e6a6d635.I4b74a082eb8d89f9e4f556a27c4339c15444dc6c@changeid

commit e1849784de9b75519f972abd22fb7e9e7bd7f992
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Fri Jan 28 14:30:54 2022 +0200

    iwlwifi: mei: fix the pskb_may_pull check in ipv4
    
    The check makes sure that we can look at the ip header.
    We first need to check that the basic ip header (20 bytes)
    can be pulled before we look at the field that will teach
    us how long is the ip header. This is why there are two
    checks.
    
    The second check was wrong and smatch pointed that
    sizeof(ip_hdrlen(skb) - sizeof(*iphdr)) can't be right.
    
    Looking at the code again made me think that we really
    need ip_hdrlen(skb) since we want to make sure all the
    IP header is in the buffer header. This will allow us
    to set the transport offset and from there to look
    at the transport header (TCP / UDP).
    
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Fixes: 2da4366f9e2c ("iwlwifi: mei: add the driver to allow cooperation with CSME")
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.6d9fcf82691e.I449b1e21c5b5478f2ac218522570479918f49f9d@changeid

commit 4c29c1e27a1e178a219b3877d055e6dd643bdfda
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Fri Jan 28 14:30:53 2022 +0200

    iwlwifi: pcie: gen2: fix locking when "HW not ready"
    
    If we run into this error path, we shouldn't unlock the mutex
    since it's not locked since. Fix this in the gen2 code as well.
    
    Fixes: eda50cde58de ("iwlwifi: pcie: add context information support")
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.b8b0dfce16ef.Ie20f0f7b23e5911350a2766524300d2915e7b677@changeid

commit e9848aed147708a06193b40d78493b0ef6abccf2
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Fri Jan 28 14:30:52 2022 +0200

    iwlwifi: pcie: fix locking when "HW not ready"
    
    If we run into this error path, we shouldn't unlock the mutex
    since it's not locked since. Fix this.
    
    Fixes: a6bd005fe92d ("iwlwifi: pcie: fix RF-Kill vs. firmware load race")
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.5d16821d1433.Id259699ddf9806459856d6aefbdbe54477aecffd@changeid

commit 973f02c932b0be41a26bb9bdf38b7b92721611d2
Author: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Date:   Fri Jan 28 14:30:51 2022 +0200

    iwlwifi: fix iwl_legacy_rate_to_fw_idx
    
    There are a couple of bugs in this function:
    
    1. It is declared as a non-static function, even though
       it's only used in one file.
    2. Its return value should be of type u32 but it returns
       (in some cases) -1.
    
    Fix them by making this function static and returning an
    error value of type unsigned.
    
    In addition, we're assigning the return value of this function
    as the legacy rate even if the function returned an error value.
    Fix this by assigning the lowest rate in this case.
    
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Reported-by: Ye Guojin <ye.guojin@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Fixes: 9998f81e4ba5 ("iwlwifi: mvm: convert old rate & flags to the new format.")
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.5612eeb9d6d0.I992e10d93fc22919b2bc42daad087ee1b5d6f014@changeid

commit be8287c9b8326d767429c8371bbc78b33f6efe13
Author: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Date:   Fri Jan 28 14:30:50 2022 +0200

    iwlwifi: mvm: fix condition which checks the version of rate_n_flags
    
    We're checking the FW version of TX_CMD in order to decide whether to
    convert rate_n_flags from the old format to the new one.  If the API
    is smaller or equal to 6 we should convert it.  Currently we're
    converting if the API version is greater than 6. Fix it.
    
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Fixes: dc52fac37c87 ("iwlwifi: mvm: Support new TX_RSP and COMPRESSED_BA_RES versions")
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/iwlwifi.20220128142706.a264ac51d106.I228ba1317cdcbfef931c09d280d701fcad9048d2@changeid

commit e25a8d959992f61b64a58fc62fb7951dc6f31d1f
Author: Jan Beulich <jbeulich@suse.com>
Date:   Tue Feb 1 11:57:16 2022 +0100

    x86/Xen: streamline (and fix) PV CPU enumeration
    
    This started out with me noticing that "dom0_max_vcpus=<N>" with <N>
    larger than the number of physical CPUs reported through ACPI tables
    would not bring up the "excess" vCPU-s. Addressing this is the primary
    purpose of the change; CPU maps handling is being tidied only as far as
    is necessary for the change here (with the effect of also avoiding the
    setting up of too much per-CPU infrastructure, i.e. for CPUs which can
    never come online).
    
    Noticing that xen_fill_possible_map() is called way too early, whereas
    xen_filter_cpu_maps() is called too late (after per-CPU areas were
    already set up), and further observing that each of the functions serves
    only one of Dom0 or DomU, it looked like it was better to simplify this.
    Use the .get_smp_config hook instead, uniformly for Dom0 and DomU.
    xen_fill_possible_map() can be dropped altogether, while
    xen_filter_cpu_maps() is re-purposed but not otherwise changed.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Link: https://lore.kernel.org/r/2dbd5f0a-9859-ca2d-085e-a02f7166c610@suse.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit 3ccb3128e50380b86e01c2f9b6f4ac9c11dc05eb
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Mon Jan 31 08:19:59 2022 -0800

    xen: update missing ioctl magic numers documentation
    
    Add missing ioctl "magic numbers" for various Xen interfaces
    (xenbus_dev.h, gntalloc.h, gntdev.h, and privcmd.h).
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Cc: Juergen Gross <jgross@suse.com>
    Cc: Stefano Stabellini <sstabellini@kernel.org>
    Cc: xen-devel@lists.xenproject.org
    Link: https://lore.kernel.org/r/20220131161959.16509-1-rdunlap@infradead.org
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit 164666fa66669d437bdcc8d5f1744a2aee73be41
Author: Demi Marie Obenour <demiobenour@gmail.com>
Date:   Mon Jan 31 12:23:07 2022 -0500

    Improve docs for IOCTL_GNTDEV_MAP_GRANT_REF
    
    --------------cKY3Ggs6VDUCSn4I6iN78sHA
    Content-Type: multipart/mixed; boundary="------------g0T69ASidFiPhh4eOY4XzIg1"
    
    --------------g0T69ASidFiPhh4eOY4XzIg1
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable
    
    The current implementation of gntdev guarantees that the first call to
    IOCTL_GNTDEV_MAP_GRANT_REF will set @index to 0.  This is required to
    use gntdev for Wayland, which is a future desire of Qubes OS.
    Additionally, requesting zero grants results in an error, but this was
    not documented either.  Document both of these.
    
    Signed-off-by: Demi Marie Obenour <demiobenour@gmail.com>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Link: https://lore.kernel.org/r/f66c5a4e-2034-00b5-a635-6983bd999c07@gmail.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit 4564661af6ee321942ec1ab012191d7adedd3e00
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sun Jan 30 11:17:05 2022 -0800

    xen: xenbus_dev.h: delete incorrect file name
    
    It is better/preferred not to include file names in source files
    because (a) they are not needed and (b) they can be incorrect,
    so just delete this incorrect file name.
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Cc: Juergen Gross <jgross@suse.com>
    Cc: Stefano Stabellini <sstabellini@kernel.org>
    Cc: xen-devel@lists.xenproject.org
    Link: https://lore.kernel.org/r/20220130191705.24971-1-rdunlap@infradead.org
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit b293dcc473d22a62dc6d78de2b15e4f49515db56
Author: Hou Tao <hotforest@gmail.com>
Date:   Wed Feb 2 14:01:58 2022 +0800

    bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
    
    After commit 2fd3fb0be1d1 ("kasan, vmalloc: unpoison VM_ALLOC pages
    after mapping"), non-VM_ALLOC mappings will be marked as accessible
    in __get_vm_area_node() when KASAN is enabled. But now the flag for
    ringbuf area is VM_ALLOC, so KASAN will complain out-of-bound access
    after vmap() returns. Because the ringbuf area is created by mapping
    allocated pages, so use VM_MAP instead.
    
    After the change, info in /proc/vmallocinfo also changes from
      [start]-[end]   24576 ringbuf_map_alloc+0x171/0x290 vmalloc user
    to
      [start]-[end]   24576 ringbuf_map_alloc+0x171/0x290 vmap user
    
    Fixes: 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support for it")
    Reported-by: syzbot+5ad567a418794b9b5983@syzkaller.appspotmail.com
    Signed-off-by: Hou Tao <houtao1@huawei.com>
    Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
    Link: https://lore.kernel.org/bpf/20220202060158.6260-1-houtao1@huawei.com

commit 6d0d95a1c2b07270870e7be16575c513c29af3f1
Author: Antony Antony <antony.antony@secunet.com>
Date:   Tue Feb 1 07:51:57 2022 +0100

    xfrm: fix the if_id check in changelink
    
    if_id will be always 0, because it was not yet initialized.
    
    Fixes: 8dce43919566 ("xfrm: interface with if_id 0 should return error")
    Reported-by: Pavel Machek <pavel@denx.de>
    Signed-off-by: Antony Antony <antony.antony@secunet.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 6a51abdeb259a56d95f13cc67e3a0838bcda0377
Author: Uday Shankar <ushankar@purestorage.com>
Date:   Thu Jan 20 12:17:37 2022 -0800

    nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
    
    Controller deletion/reset, immediately followed by or concurrent with
    a reconnect, is hard failing the connect attempt resulting in a
    complete loss of connectivity to the controller.
    
    In the connect request, fabrics looks for an existing controller with
    the same address components and aborts the connect if a controller
    already exists and the duplicate connect option isn't set. The match
    routine filters out controllers that are dead or dying, so they don't
    interfere with the new connect request.
    
    When NVME_CTRL_DELETING_NOIO was added, it missed updating the state
    filters in the nvmf_ctlr_matches_baseopts() routine. Thus, when in this
    new state, it's seen as a live controller and fails the connect request.
    
    Correct by adding the DELETING_NIO state to the match checks.
    
    Fixes: ecca390e8056 ("nvme: fix deadlock in disconnect during scan_work and/or ana_work")
    Cc: <stable@vger.kernel.org> # v5.7+
    Signed-off-by: Uday Shankar <ushankar@purestorage.com>
    Reviewed-by: James Smart <jsmart2021@gmail.com>
    Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit d3b331fb51f326d5b5326010bf2b5841bb86cdc6
Author: Ryan Bair <ryandbair@gmail.com>
Date:   Wed Dec 22 11:04:05 2021 -0500

    cifs: fix workstation_name for multiuser mounts
    
    Set workstation_name from the master_tcon for multiuser mounts.
    
    Just in case, protect size_of_ntlmssp_blob against a NULL workstation_name.
    
    Fixes: 49bd49f983b5 ("cifs: send workstation name during ntlmssp session setup")
    Cc: stable@vger.kernel.org # 5.16
    Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
    Signed-off-by: Ryan Bair <ryandbair@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 40c845c176953311c8fc232e977516f7733c64cd
Author: Rohith Surabattula <rohiths@microsoft.com>
Date:   Tue Feb 1 07:22:02 2022 +0000

    Invalidate fscache cookie only when inode attributes are changed.
    
    For example if mtime or size has changed.
    
    Signed-off-by: Rohith Surabattula <rohiths@microsoft.com>
    Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 4a81f6da9cb2d1ef911131a6fd8bd15cb61fc772
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Tue Feb 1 20:39:42 2022 +0100

    net, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work
    
    syzkaller was able to trigger a deadlock for NTF_MANAGED entries [0]:
    
      kworker/0:16/14617 is trying to acquire lock:
      ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652
      [...]
      but task is already holding lock:
      ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: neigh_managed_work+0x35/0x250 net/core/neighbour.c:1572
    
    The neighbor entry turned to NUD_FAILED state, where __neigh_event_send()
    triggered an immediate probe as per commit cd28ca0a3dd1 ("neigh: reduce
    arp latency") via neigh_probe() given table lock was held.
    
    One option to fix this situation is to defer the neigh_probe() back to
    the neigh_timer_handler() similarly as pre cd28ca0a3dd1. For the case
    of NTF_MANAGED, this deferral is acceptable given this only happens on
    actual failure state and regular / expected state is NUD_VALID with the
    entry already present.
    
    The fix adds a parameter to __neigh_event_send() in order to communicate
    whether immediate probe is allowed or disallowed. Existing call-sites
    of neigh_event_send() default as-is to immediate probe. However, the
    neigh_managed_work() disables it via use of neigh_event_send_probe().
    
    [0] <TASK>
      __dump_stack lib/dump_stack.c:88 [inline]
      dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
      print_deadlock_bug kernel/locking/lockdep.c:2956 [inline]
      check_deadlock kernel/locking/lockdep.c:2999 [inline]
      validate_chain kernel/locking/lockdep.c:3788 [inline]
      __lock_acquire.cold+0x149/0x3ab kernel/locking/lockdep.c:5027
      lock_acquire kernel/locking/lockdep.c:5639 [inline]
      lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5604
      __raw_write_lock_bh include/linux/rwlock_api_smp.h:202 [inline]
      _raw_write_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:334
      ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652
      ip6_finish_output2+0x1070/0x14f0 net/ipv6/ip6_output.c:123
      __ip6_finish_output net/ipv6/ip6_output.c:191 [inline]
      __ip6_finish_output+0x61e/0xe90 net/ipv6/ip6_output.c:170
      ip6_finish_output+0x32/0x200 net/ipv6/ip6_output.c:201
      NF_HOOK_COND include/linux/netfilter.h:296 [inline]
      ip6_output+0x1e4/0x530 net/ipv6/ip6_output.c:224
      dst_output include/net/dst.h:451 [inline]
      NF_HOOK include/linux/netfilter.h:307 [inline]
      ndisc_send_skb+0xa99/0x17f0 net/ipv6/ndisc.c:508
      ndisc_send_ns+0x3a9/0x840 net/ipv6/ndisc.c:650
      ndisc_solicit+0x2cd/0x4f0 net/ipv6/ndisc.c:742
      neigh_probe+0xc2/0x110 net/core/neighbour.c:1040
      __neigh_event_send+0x37d/0x1570 net/core/neighbour.c:1201
      neigh_event_send include/net/neighbour.h:470 [inline]
      neigh_managed_work+0x162/0x250 net/core/neighbour.c:1574
      process_one_work+0x9ac/0x1650 kernel/workqueue.c:2307
      worker_thread+0x657/0x1110 kernel/workqueue.c:2454
      kthread+0x2e9/0x3a0 kernel/kthread.c:377
      ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
      </TASK>
    
    Fixes: 7482e3841d52 ("net, neigh: Add NTF_MANAGED flag for managed neighbor entries")
    Reported-by: syzbot+5239d0e1778a500d477a@syzkaller.appspotmail.com
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Cc: Eric Dumazet <edumazet@google.com>
    Cc: Roopa Prabhu <roopa@nvidia.com>
    Tested-by: syzbot+5239d0e1778a500d477a@syzkaller.appspotmail.com
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Link: https://lore.kernel.org/r/20220201193942.5055-1-daniel@iogearbox.net
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit b67985be400969578d4d4b17299714c0e5d2c07b
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Feb 1 10:46:40 2022 -0800

    tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
    
    tcp_shift_skb_data() might collapse three packets into a larger one.
    
    P_A, P_B, P_C  -> P_ABC
    
    Historically, it used a single tcp_skb_can_collapse_to(P_A) call,
    because it was enough.
    
    In commit 85712484110d ("tcp: coalesce/collapse must respect MPTCP extensions"),
    this call was replaced by a call to tcp_skb_can_collapse(P_A, P_B)
    
    But the now needed test over P_C has been missed.
    
    This probably broke MPTCP.
    
    Then later, commit 9b65b17db723 ("net: avoid double accounting for pure zerocopy skbs")
    added an extra condition to tcp_skb_can_collapse(), but the missing call
    from tcp_shift_skb_data() is also breaking TCP zerocopy, because P_A and P_C
    might have different skb_zcopy_pure() status.
    
    Fixes: 85712484110d ("tcp: coalesce/collapse must respect MPTCP extensions")
    Fixes: 9b65b17db723 ("net: avoid double accounting for pure zerocopy skbs")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Cc: Talal Ahmad <talalahmad@google.com>
    Cc: Arjun Roy <arjunroy@google.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Link: https://lore.kernel.org/r/20220201184640.756716-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c4f9c8bbcc24f00002827f73957053a59aba5646
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Thu Feb 3 00:30:38 2022 +0300

    MAINTAINERS: add myself as PATA drivers reviewer
    
    Add myself as a reviewer for the libata PATA drivers -- there is
    activity in this area still... 8-)
    Having been hacking on ATA from the early 90s, I think I deserved this
    highly responsible position, at last! :-)
    
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit e8ae38720e1a685fd98cfa5ae118c9d07b45ca79
Author: Christian König <christian.koenig@amd.com>
Date:   Fri Jan 28 13:21:10 2022 +0100

    drm/amdgpu: fix logic inversion in check
    
    We probably never trigger this, but the logic inside the check is
    inverted.
    
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit e55a3aea418269266d84f426b3bd70794d3389c8
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Jan 25 21:46:58 2022 -0600

    drm/amd: avoid suspend on dGPUs w/ s2idle support when runtime PM enabled
    
    dGPUs connected to Intel systems configured for suspend to idle
    will not have the power rails cut at suspend and resetting the GPU
    may lead to problematic behaviors.
    
    Fixes: e25443d2765f4 ("drm/amdgpu: add a dev_pm_ops prepare callback (v2)")
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1879
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 30fbce374745a9c6af93c775a5ac49a97f822fda
Author: Aun-Ali Zaidi <admin@kodeit.net>
Date:   Sat Jan 29 05:49:55 2022 +0000

    drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels
    
    The eDP link rate reported by the DP_MAX_LINK_RATE dpcd register (0xa) is
    contradictory to the highest rate supported reported by
    EDID (0xc = LINK_RATE_RBR2). The effects of this compounded with commit
    '4a8ca46bae8a ("drm/amd/display: Default max bpc to 16 for eDP")' results
    in no display modes being found and a dark panel.
    
    For now, simply force the maximum supported link rate for the eDP attached
    2018 15" Apple Retina panels.
    
    Additionally, we must also check the firmware revision since the device ID
    reported by the DPCD is identical to that of the more capable 16,1,
    incorrectly quirking it. We also use said firmware check to quirk the
    refreshed 15,1 models with Vega graphics as they use a slightly newer
    firmware version.
    
    Tested-by: Aun-Ali Zaidi <admin@kodeit.net>
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Aun-Ali Zaidi <admin@kodeit.net>
    Signed-off-by: Aditya Garg <gargaditya08@live.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 49a6ebb95d04bdaa5d57313a380c44249cf02100
Author: Zhan Liu <Zhan.Liu@amd.com>
Date:   Fri Jan 28 22:03:59 2022 +0800

    drm/amd/display: revert "Reset fifo after enable otg"
    
    [Why]
    This change causes regression, that prevents some systems
    from lighting up internal displays.
    
    [How]
    Revert this patch until a new solution is ready.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Charlene Liu <Charlene.Liu@amd.com>
    Acked-by: Stylon Wang <stylon.wang@amd.com>
    Signed-off-by: Zhan Liu <Zhan.Liu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit f5fa54f45ab41cbb1f99b1208f49554132ffb207
Author: Paul Hsieh <paul.hsieh@amd.com>
Date:   Fri Jan 28 22:03:57 2022 +0800

    drm/amd/display: watermark latencies is not enough on DCN31
    
    [Why]
    The original latencies were causing underflow in some modes.
    Resolution: 2880x1620@60p when HDR enable
    
    [How]
    1. Replace with the up-to-date watermark values based on new measurments
    2. Correct the ddr_wm_table name to DDR5 on DCN31
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Aric Cyr <Aric.Cyr@amd.com>
    Acked-by: Stylon Wang <stylon.wang@amd.com>
    Signed-off-by: Paul Hsieh <paul.hsieh@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 2d8ae25d233767171942a9fba5fd8f4a620996be
Author: Agustin Gutierrez <agustin.gutierrez@amd.com>
Date:   Fri Jan 28 17:51:53 2022 -0500

    drm/amd/display: Update watermark values for DCN301
    
    [Why]
    There is underflow / visual corruption DCN301, for high
    bandwidth MST DSC configurations such as 2x1440p144 or 2x4k60.
    
    [How]
    Use up-to-date watermark values for DCN301.
    
    Reviewed-by: Zhan Liu <zhan.liu@amd.com>
    Signed-off-by: Agustin Gutierrez <agustin.gutierrez@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit bca52455a3c07922ee976714b00563a13a29ab15
Author: Lang Yu <Lang.Yu@amd.com>
Date:   Fri Jan 28 18:24:53 2022 +0800

    drm/amdgpu: fix a potential GPU hang on cyan skillfish
    
    We observed a GPU hang when querying GMC CG state(i.e.,
    cat amdgpu_pm_info) on cyan skillfish. Acctually, cyan
    skillfish doesn't support any CG features.
    
    Just prevent it from accessing GMC CG registers.
    
    Signed-off-by: Lang Yu <Lang.Yu@amd.com>
    Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 04ef860469fda6a646dc841190d05b31fae68e8c
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Jan 25 21:37:57 2022 -0600

    drm/amd: Only run s3 or s0ix if system is configured properly
    
    This will cause misconfigured systems to not run the GPU suspend
    routines.
    
    * In APUs that are properly configured system will go into s2idle.
    * In APUs that are intended to be S3 but user selects
      s2idle the GPU will stay fully powered for the suspend.
    * In APUs that are intended to be s2idle and system misconfigured
      the GPU will stay fully powered for the suspend.
    * In systems that are intended to be s2idle, but AMD dGPU is also
      present, the dGPU will go through S3
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit f52a2b8badbd24faf73a13c9c07fdb9d07352944
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Jan 25 21:35:09 2022 -0600

    drm/amd: add support to check whether the system is set to s3
    
    This will be used to help make decisions on what to do in
    misconfigured systems.
    
    v2: squash in semicolon fix from Stephen Rothwell
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit bfb1a7c91fb7758273b4a8d735313d9cc388b502
Author: Nick Desaulniers <ndesaulniers@google.com>
Date:   Wed Feb 2 12:55:53 2022 -0800

    x86/bug: Merge annotate_reachable() into _BUG_FLAGS() asm
    
    In __WARN_FLAGS(), we had two asm statements (abbreviated):
    
      asm volatile("ud2");
      asm volatile(".pushsection .discard.reachable");
    
    These pair of statements are used to trigger an exception, but then help
    objtool understand that for warnings, control flow will be restored
    immediately afterwards.
    
    The problem is that volatile is not a compiler barrier. GCC explicitly
    documents this:
    
    > Note that the compiler can move even volatile asm instructions
    > relative to other code, including across jump instructions.
    
    Also, no clobbers are specified to prevent instructions from subsequent
    statements from being scheduled by compiler before the second asm
    statement. This can lead to instructions from subsequent statements
    being emitted by the compiler before the second asm statement.
    
    Providing a scheduling model such as via -march= options enables the
    compiler to better schedule instructions with known latencies to hide
    latencies from data hazards compared to inline asm statements in which
    latencies are not estimated.
    
    If an instruction gets scheduled by the compiler between the two asm
    statements, then objtool will think that it is not reachable, producing
    a warning.
    
    To prevent instructions from being scheduled in between the two asm
    statements, merge them.
    
    Also remove an unnecessary unreachable() asm annotation from BUG() in
    favor of __builtin_unreachable(). objtool is able to track that the ud2
    from BUG() terminates control flow within the function.
    
    Link: https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Volatile
    Link: https://github.com/ClangBuiltLinux/linux/issues/1483
    Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Link: https://lore.kernel.org/r/20220202205557.2260694-1-ndesaulniers@google.com

commit 9b818634f8e7e0bca3386a50b1fada7a49036408
Author: Dave Jiang <dave.jiang@intel.com>
Date:   Wed Feb 2 14:19:25 2022 -0700

    MAINTAINERS: update mailing list address for NTB subsystem
    
    NTB mailing list is moving from linux-ntb@googlegroups.com to
    ntb@lists.linux.dev in order to get better archive and lore support.
    Update all entries in MAINTAINERS.
    
    Signed-off-by: Dave Jiang <dave.jiang@intel.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 618c2dc667c87995cdc7de339224bd96bb049a1f
Merge: 7fa5c33d04316 2b7c46369f09c
Author: Mark Brown <broonie@kernel.org>
Date:   Wed Feb 2 18:15:20 2022 +0000

    ASoC: ops: Fix stereo change notifications
    
    Merge series from Mark Brown <broonie@kernel.org>:
    
    The event generation coverage I just wrote shows that the generic ASoC
    ops fail to generate events for stereo controls when only the first
    channel is changed, we just return the status for the second channel and
    discard that for the first.

commit 88808fbbead481aedb46640a5ace69c58287f56a
Merge: d5084ffbc50c7 ab451ea952fe9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 2 10:14:31 2022 -0800

    Merge tag 'nfsd-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
    
    Pull nfsd fixes from Chuck Lever:
     "Notable bug fixes:
    
       - Ensure SM_NOTIFY doesn't crash the NFS server host
    
       - Ensure NLM locks are cleaned up after client reboot
    
       - Fix a leak of internal NFSv4 lease information"
    
    * tag 'nfsd-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux:
      nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client.
      lockd: fix failure to cleanup client locks
      lockd: fix server crash on reboot of client holding lock

commit 0f9650bd838efe5c52f7e5f40c3204ad59f1964d
Author: Song Liu <song@kernel.org>
Date:   Wed Feb 2 09:24:10 2022 -0800

    md: fix NULL pointer deref with nowait but no mddev->queue
    
    Leon reported NULL pointer deref with nowait support:
    
    [   15.123761] device-mapper: raid: Loading target version 1.15.1
    [   15.124185] device-mapper: raid: Ignoring chunk size parameter for RAID 1
    [   15.124192] device-mapper: raid: Choosing default region size of 4MiB
    [   15.129524] BUG: kernel NULL pointer dereference, address: 0000000000000060
    [   15.129530] #PF: supervisor write access in kernel mode
    [   15.129533] #PF: error_code(0x0002) - not-present page
    [   15.129535] PGD 0 P4D 0
    [   15.129538] Oops: 0002 [#1] PREEMPT SMP NOPTI
    [   15.129541] CPU: 5 PID: 494 Comm: ldmtool Not tainted 5.17.0-rc2-1-mainline #1 9fe89d43dfcb215d2731e6f8851740520778615e
    [   15.129546] Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F36e 10/14/2021
    [   15.129549] RIP: 0010:blk_queue_flag_set+0x7/0x20
    [   15.129555] Code: 00 00 00 0f 1f 44 00 00 48 8b 35 e4 e0 04 02 48 8d 57 28 bf 40 01 \
           00 00 e9 16 c1 be ff 66 0f 1f 44 00 00 0f 1f 44 00 00 89 ff <f0> 48 0f ab 7e 60 \
           31 f6 89 f7 c3 66 66 2e 0f 1f 84 00 00 00 00 00
    [   15.129559] RSP: 0018:ffff966b81987a88 EFLAGS: 00010202
    [   15.129562] RAX: ffff8b11c363a0d0 RBX: ffff8b11e294b070 RCX: 0000000000000000
    [   15.129564] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000001d
    [   15.129566] RBP: ffff8b11e294b058 R08: 0000000000000000 R09: 0000000000000000
    [   15.129568] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8b11e294b070
    [   15.129570] R13: 0000000000000000 R14: ffff8b11e294b000 R15: 0000000000000001
    [   15.129572] FS:  00007fa96e826780(0000) GS:ffff8b18deb40000(0000) knlGS:0000000000000000
    [   15.129575] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [   15.129577] CR2: 0000000000000060 CR3: 000000010b8ce000 CR4: 00000000003506e0
    [   15.129580] Call Trace:
    [   15.129582]  <TASK>
    [   15.129584]  md_run+0x67c/0xc70 [md_mod 1e470c1b6bcf1114198109f42682f5a2740e9531]
    [   15.129597]  raid_ctr+0x134a/0x28ea [dm_raid 6a645dd7519e72834bd7e98c23497eeade14cd63]
    [   15.129604]  ? dm_split_args+0x63/0x150 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129615]  dm_table_add_target+0x188/0x380 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129625]  table_load+0x13b/0x370 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129635]  ? dev_suspend+0x2d0/0x2d0 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129644]  ctl_ioctl+0x1bd/0x460 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129655]  dm_ctl_ioctl+0xa/0x20 [dm_mod 0d7b0bc3414340a79c4553bae5ca97294b78336e]
    [   15.129663]  __x64_sys_ioctl+0x8e/0xd0
    [   15.129667]  do_syscall_64+0x5c/0x90
    [   15.129672]  ? syscall_exit_to_user_mode+0x23/0x50
    [   15.129675]  ? do_syscall_64+0x69/0x90
    [   15.129677]  ? do_syscall_64+0x69/0x90
    [   15.129679]  ? syscall_exit_to_user_mode+0x23/0x50
    [   15.129682]  ? do_syscall_64+0x69/0x90
    [   15.129684]  ? do_syscall_64+0x69/0x90
    [   15.129686]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [   15.129689] RIP: 0033:0x7fa96ecd559b
    [   15.129692] Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c \
        c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff \
        ff 73 01 c3 48 8b 0d a5 a8 0c 00 f7 d8 64 89 01 48
    [   15.129696] RSP: 002b:00007ffcaf85c258 EFLAGS: 00000206 ORIG_RAX: 0000000000000010
    [   15.129699] RAX: ffffffffffffffda RBX: 00007fa96f1b48f0 RCX: 00007fa96ecd559b
    [   15.129701] RDX: 00007fa97017e610 RSI: 00000000c138fd09 RDI: 0000000000000003
    [   15.129702] RBP: 00007fa96ebab583 R08: 00007fa97017c9e0 R09: 00007ffcaf85bf27
    [   15.129704] R10: 0000000000000001 R11: 0000000000000206 R12: 00007fa97017e610
    [   15.129706] R13: 00007fa97017e640 R14: 00007fa97017e6c0 R15: 00007fa97017e530
    [   15.129709]  </TASK>
    
    This is caused by missing mddev->queue check for setting QUEUE_FLAG_NOWAIT
    Fix this by moving the QUEUE_FLAG_NOWAIT logic to under mddev->queue check.
    
    Fixes: f51d46d0e7cb ("md: add support for REQ_NOWAIT")
    Reported-by: Leon Möller <jkhsjdhjs@totally.rip>
    Tested-by: Leon Möller <jkhsjdhjs@totally.rip>
    Cc: Vishal Verma <vverma@digitalocean.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit de4d73b16d5d9c3e5d03a66046e5410e1e74f903
Author: Daniel Latypov <dlatypov@google.com>
Date:   Thu Jan 27 14:17:10 2022 -0800

    kunit: fix missing f in f-string in run_checks.py
    
    We're missing the `f` prefix to have python do string interpolation, so
    we'd never end up printing what the actual "unexpected" error is.
    
    Fixes: ee92ed38364e ("kunit: add run_checks.py script to validate kunit changes")
    Signed-off-by: Daniel Latypov <dlatypov@google.com>
    Reviewed-by: David Gow <davidgow@google.com>
    Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit d5084ffbc50c76e4a237d87e022e88f6b15b3cb9
Merge: 27bb0b18c208e ee12595147ac1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 2 10:08:52 2022 -0800

    Merge tag 'fsnotify_for_v5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
    
    Pull fanotify fix from Jan Kara:
     "Fix stale file descriptor in copy_event_to_user"
    
    * tag 'fsnotify_for_v5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
      fanotify: Fix stale file descriptor in copy_event_to_user()

commit 27bb0b18c208ecd4c0deda6aad28616d73e4133d
Merge: 3e5832e923a9c 235528072f28b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 2 10:00:08 2022 -0800

    Merge tag 'linux-kselftest-kunit-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull KUnit fixes from Shuah Khan:
     "A single fix to an error seen on qemu due to a missing import"
    
    * tag 'linux-kselftest-kunit-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      kunit: tool: Import missing importlib.abc

commit 038b8d1d1ab1cce11a158d30bf080ff41a2cfd15
Author: Ilya Dryomov <idryomov@gmail.com>
Date:   Thu Dec 30 15:13:32 2021 +0100

    libceph: optionally use bounce buffer on recv path in crc mode
    
    Both msgr1 and msgr2 in crc mode are zero copy in the sense that
    message data is read from the socket directly into the destination
    buffer.  We assume that the destination buffer is stable (i.e. remains
    unchanged while it is being read to) though.  Otherwise, CRC errors
    ensue:
    
      libceph: read_partial_message 0000000048edf8ad data crc 1063286393 != exp. 228122706
      libceph: osd1 (1)192.168.122.1:6843 bad crc/signature
    
      libceph: bad data crc, calculated 57958023, expected 1805382778
      libceph: osd2 (2)192.168.122.1:6876 integrity error, bad crc
    
    Introduce rxbounce option to enable use of a bounce buffer when
    receiving message data.  In particular this is needed if a mapped
    image is a Windows VM disk, passed to QEMU.  Windows has a system-wide
    "dummy" page that may be mapped into the destination buffer (potentially
    more than once into the same buffer) by the Windows Memory Manager in
    an effort to generate a single large I/O [1][2].  QEMU makes a point of
    preserving overlap relationships when cloning I/O vectors, so krbd gets
    exposed to this behaviour.
    
    [1] "What Is Really in That MDL?"
        https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn614012(v=vs.85)
    [2] https://blogs.msmvps.com/kernelmustard/2005/05/04/dummy-pages/
    
    URL: https://bugzilla.redhat.com/show_bug.cgi?id=1973317
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>

commit 2ea88716369ac9a7486a8cb309d6bf1239ea156c
Author: Ilya Dryomov <idryomov@gmail.com>
Date:   Sun Jan 23 17:27:47 2022 +0100

    libceph: make recv path in secure mode work the same as send path
    
    The recv path of secure mode is intertwined with that of crc mode.
    While it's slightly more efficient that way (the ciphertext is read
    into the destination buffer and decrypted in place, thus avoiding
    two potentially heavy memory allocations for the bounce buffer and
    the corresponding sg array), it isn't really amenable to changes.
    Sacrifice that edge and align with the send path which always uses
    a full-sized bounce buffer (currently there is no other way -- if
    the kernel crypto API ever grows support for streaming (piecewise)
    en/decryption for GCM [1], we would be able to easily take advantage
    of that on both sides).
    
    [1] https://lore.kernel.org/all/20141225202830.GA18794@gondor.apana.org.au/
    
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>

commit 3e5832e923a9c3a12c76980f68853668d4675ecf
Merge: 9f7fb8de5d9ba baf927a833ca2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Feb 2 09:50:17 2022 -0800

    Merge tag 'pinctrl-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
    
    Pull pin control fixes from Linus Walleij:
     "Most interesting and urgent is the Intel stuff affecting Chromebooks
      and laptops.
    
       - Fix up group name building on the Intel Thunderbay
    
       - Fix interrupt problems on the Intel Cherryview
    
       - Fix some pin data on the Sunxi H616
    
       - Fix up the CONFIG_PINCTRL_ST Kconfig sort order as noted during the
         merge window
    
       - Fix an unexpected interrupt problem on the Intel Sunrisepoint
    
       - Fix a glitch when updating IRQ flags on all Intel pin controllers
    
       - Revert a Zynqmp patch to unify the pin naming, let's find some
         better solution
    
       - Fix some error paths in the Broadcom BCM2835 driver
    
       - Fix a Kconfig problem pertaining to the BCM63XX drivers
    
       - Fix the regmap support in the Microchip SGPIO driver"
    
    * tag 'pinctrl-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
      pinctrl: microchip-sgpio: Fix support for regmap
      pinctrl: bcm63xx: fix unmet dependency on REGMAP for GPIO_REGMAP
      pinctrl: bcm2835: Fix a few error paths
      pinctrl: zynqmp: Revert "Unify pin naming"
      pinctrl: intel: Fix a glitch when updating IRQ flags on a preconfigured line
      pinctrl: intel: fix unexpected interrupt
      pinctrl: Place correctly CONFIG_PINCTRL_ST in the Makefile
      pinctrl: sunxi: Fix H616 I2S3 pin data
      pinctrl: cherryview: Trigger hwirq0 for interrupt-lines without a mapping
      pinctrl: thunderbay: rework loops looking for groups names
      pinctrl: thunderbay: comment process of building functions a bit

commit 81eb8b0b18789e647e65579303529fd52d861cc2
Author: Steen Hegelund <steen.hegelund@microchip.com>
Date:   Wed Feb 2 09:30:39 2022 +0100

    net: sparx5: do not refer to skb after passing it on
    
    Do not try to use any SKB fields after the packet has been passed up in the
    receive stack.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
    Link: https://lore.kernel.org/r/20220202083039.3774851-1-steen.hegelund@microchip.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bdc120a2bcd834e571ce4115aaddf71ab34495de
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Feb 1 19:06:26 2022 +0100

    net: ieee802154: ca8210: Fix lifs/sifs periods
    
    These periods are expressed in time units (microseconds) while 40 and 12
    are the number of symbol durations these periods will last. We need to
    multiply them both with the symbol_duration in order to get these
    values in microseconds.
    
    Fixes: ded845a781a5 ("ieee802154: Add CA8210 IEEE 802.15.4 device driver")
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/r/20220201180629.93410-2-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit 89677197ae709eb1ab3646952c44f6a171c9e74c
Author: Stefan Berger <stefanb@linux.ibm.com>
Date:   Tue Feb 1 15:37:10 2022 -0500

    ima: Do not print policy rule with inactive LSM labels
    
    Before printing a policy rule scan for inactive LSM labels in the policy
    rule. Inactive LSM labels are identified by args_p != NULL and
    rule == NULL.
    
    Fixes: 483ec26eed42 ("ima: ima/lsm policy rule loading logic bug fixes")
    Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
    Cc: <stable@vger.kernel.org> # v5.6+
    Acked-by: Christian Brauner <brauner@kernel.org>
    [zohar@linux.ibm.com: Updated "Fixes" tag]
    Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>

commit bb8e52e4906f148c2faf6656b5106cf7233e9301
Author: Roberto Sassu <roberto.sassu@huawei.com>
Date:   Mon Jan 31 18:11:39 2022 +0100

    ima: Allow template selection with ima_template[_fmt]= after ima_hash=
    
    Commit c2426d2ad5027 ("ima: added support for new kernel cmdline parameter
    ima_template_fmt") introduced an additional check on the ima_template
    variable to avoid multiple template selection.
    
    Unfortunately, ima_template could be also set by the setup function of the
    ima_hash= parameter, when it calls ima_template_desc_current(). This causes
    attempts to choose a new template with ima_template= or with
    ima_template_fmt=, after ima_hash=, to be ignored.
    
    Achieve the goal of the commit mentioned with the new static variable
    template_setup_done, so that template selection requests after ima_hash=
    are not ignored.
    
    Finally, call ima_init_template_list(), if not already done, to initialize
    the list of templates before lookup_template_desc() is called.
    
    Reported-by: Guo Zihua <guozihua@huawei.com>
    Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
    Cc: stable@vger.kernel.org
    Fixes: c2426d2ad5027 ("ima: added support for new kernel cmdline parameter ima_template_fmt")
    Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>

commit f7333b9572d0559e00352a926c92f29f061b4569
Author: Stefan Berger <stefanb@linux.ibm.com>
Date:   Tue Jan 25 17:46:23 2022 -0500

    ima: Remove ima_policy file before directory
    
    The removal of ima_dir currently fails since ima_policy still exists, so
    remove the ima_policy file before removing the directory.
    
    Fixes: 4af4662fa4a9 ("integrity: IMA policy")
    Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
    Cc: <stable@vger.kernel.org>
    Acked-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>

commit 83230351c523b04ff8a029a4bdf97d881ecb96fc
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Sat Jan 15 09:11:11 2022 +0800

    integrity: check the return value of audit_log_start()
    
    audit_log_start() returns audit_buffer pointer on success or NULL on
    error, so it is better to check the return value of it.
    
    Fixes: 3323eec921ef ("integrity: IMA as an integrity service provider")
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Cc: <stable@vger.kernel.org>
    Reviewed-by: Paul Moore <paul@paul-moore.com>
    Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>

commit 7fa5c33d043160eba3be9fb8e21588dff2a467c7
Author: V sujith kumar Reddy <vsujithkumar.reddy@amd.com>
Date:   Tue Feb 1 02:02:15 2022 +0530

    ASoC: amd: acp: Set gpio_spkr_en to None for max speaker amplifer in machine driver
    
    Maxim codec driver already enabling/disabling spk_en_gpio in form of sd_mode gpio
    hence remove such gpio access control from machine driver to avoid conflict
    
    Signed-off-by: V sujith kumar Reddy <vsujithkumar.reddy@amd.com>
    Link: https://lore.kernel.org/r/20220131203225.1418648-1-vsujithkumar.reddy@amd.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 2b7c46369f09c358164d31d17e5695185403185e
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Feb 1 15:56:29 2022 +0000

    ASoC: ops: Fix stereo change notifications in snd_soc_put_xr_sx()
    
    When writing out a stereo control we discard the change notification from
    the first channel, meaning that events are only generated based on changes
    to the second channel. Ensure that we report a change if either channel
    has changed.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220201155629.120510-5-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 650204ded3703b5817bd4b6a77fa47d333c4f902
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Feb 1 15:56:28 2022 +0000

    ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_range()
    
    When writing out a stereo control we discard the change notification from
    the first channel, meaning that events are only generated based on changes
    to the second channel. Ensure that we report a change if either channel
    has changed.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220201155629.120510-4-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 7f3d90a3519680dfa23e750f80bfdefc0f5eda4a
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Feb 1 15:56:27 2022 +0000

    ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_sx()
    
    When writing out a stereo control we discard the change notification from
    the first channel, meaning that events are only generated based on changes
    to the second channel. Ensure that we report a change if either channel
    has changed.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220201155629.120510-3-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 564778d7b1ea465f9487eedeece7527a033549c5
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Feb 1 15:56:26 2022 +0000

    ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw()
    
    When writing out a stereo control we discard the change notification from
    the first channel, meaning that events are only generated based on changes
    to the second channel. Ensure that we report a change if either channel
    has changed.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220201155629.120510-2-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 186edf7e368c40d06cf727a1ad14698ea67b74ad
Author: Vratislav Bendel <vbendel@redhat.com>
Date:   Wed Feb 2 12:25:11 2022 +0100

    selinux: fix double free of cond_list on error paths
    
    On error path from cond_read_list() and duplicate_policydb_cond_list()
    the cond_list_destroy() gets called a second time in caller functions,
    resulting in NULL pointer deref.  Fix this by resetting the
    cond_list_len to 0 in cond_list_destroy(), making subsequent calls a
    noop.
    
    Also consistently reset the cond_list pointer to NULL after freeing.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Vratislav Bendel <vbendel@redhat.com>
    [PM: fix line lengths in the description]
    Signed-off-by: Paul Moore <paul@paul-moore.com>

commit e1d2699b96793d19388e302fa095e0da2c145701
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Tue Jan 18 22:10:52 2022 -0500

    NFS: Avoid duplicate uncached readdir calls on eof
    
    If we've reached the end of the directory, then cache that information
    in the context so that we don't need to do an uncached readdir in order
    to rediscover that fact.
    
    Fixes: 794092c57f89 ("NFS: Do uncached readdir when we're seeking a cookie in an empty page cache")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit ce292d8faf41f62e0fb0c78476c6fce5d629235a
Author: trondmy@kernel.org <trondmy@kernel.org>
Date:   Tue Jan 18 19:52:16 2022 -0500

    NFS: Don't skip directory entries when doing uncached readdir
    
    Ensure that we initialise desc->cache_entry_index correctly in
    uncached_readdir().
    
    Fixes: d1bacf9eb2fd ("NFS: add readdir cache array")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit d9c4e39c1f8f8a8ebaccf00b8f22c14364b2d27e
Author: trondmy@kernel.org <trondmy@kernel.org>
Date:   Tue Jan 18 19:25:42 2022 -0500

    NFS: Don't overfill uncached readdir pages
    
    If we're doing an uncached read of the directory, then we ideally want
    to read only the exact set of entries that will fit in the buffer
    supplied by the getdents() system call. So unlike the case where we're
    reading into the page cache, let's send only one READDIR call, before
    trying to fill up the buffer.
    
    Fixes: 35df59d3ef69 ("NFS: Reduce number of RPC calls when doing uncached readdir")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit c86d86131ab75696fc52d98571148842e067d620
Author: Dmitry V. Levin <ldv@altlinux.org>
Date:   Wed Feb 2 06:09:04 2022 +0300

    Partially revert "net/smc: Add netlink net namespace support"
    
    The change of sizeof(struct smc_diag_linkinfo) by commit 79d39fc503b4
    ("net/smc: Add netlink net namespace support") introduced an ABI
    regression: since struct smc_diag_lgrinfo contains an object of
    type "struct smc_diag_linkinfo", offset of all subsequent members
    of struct smc_diag_lgrinfo was changed by that change.
    
    As result, applications compiled with the old version
    of struct smc_diag_linkinfo will receive garbage in
    struct smc_diag_lgrinfo.role if the kernel implements
    this new version of struct smc_diag_linkinfo.
    
    Fix this regression by reverting the part of commit 79d39fc503b4 that
    changes struct smc_diag_linkinfo.  After all, there is SMC_GEN_NETLINK
    interface which is good enough, so there is probably no need to touch
    the smc_diag ABI in the first place.
    
    Fixes: 79d39fc503b4 ("net/smc: Add netlink net namespace support")
    Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
    Reviewed-by: Karsten Graul <kgraul@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220202030904.GA9742@altlinux.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cb4f0843429e38431023c26ca7cdaee447953cbd
Merge: 8cfe148a7136b 403271548a840
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Feb 2 09:58:10 2022 -0500

    Merge tag 'kvm-riscv-fixes-5.17-1' of https://github.com/kvm-riscv/linux into HEAD
    
    KVM/riscv fixes for 5.17, take #1
    
    - Rework guest entry logic
    
    - Make CY, TM, and IR counters accessible in VU mode
    
    - Fix SBI implementation version

commit 3e1f941dd9f33776b3df4e30f741fe445ff773f3
Author: Ilya Dryomov <idryomov@gmail.com>
Date:   Tue Feb 1 11:04:20 2022 +0100

    block: fix DIO handling regressions in blkdev_read_iter()
    
    Commit ceaa762527f4 ("block: move direct_IO into our own read_iter
    handler") introduced several regressions for bdev DIO:
    
    1. read spanning EOF always returns 0 instead of the number of bytes
       read.  This is because "count" is assigned early and isn't updated
       when the iterator is truncated:
    
         $ lsblk -o name,size /dev/vdb
         NAME SIZE
         vdb    1G
         $ xfs_io -d -c 'pread -b 4M 1021M 4M' /dev/vdb
         read 0/4194304 bytes at offset 1070596096
         0.000000 bytes, 0 ops; 0.0007 sec (0.000000 bytes/sec and 0.0000 ops/sec)
    
         instead of
    
         $ xfs_io -d -c 'pread -b 4M 1021M 4M' /dev/vdb
         read 3145728/4194304 bytes at offset 1070596096
         3 MiB, 1 ops; 0.0007 sec (3.865 GiB/sec and 1319.2612 ops/sec)
    
    2. truncated iterator isn't reexpanded
    3. iterator isn't reverted on blkdev_direct_IO() error
    4. zero size read no longer skips atime update
    
    Fixes: ceaa762527f4 ("block: move direct_IO into our own read_iter handler")
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220201100420.25875-1-idryomov@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit c8ff576e4e553a059e0790afd15385f418b1a854
Merge: 3aa430d33b8dd ad5185735f7da
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Feb 2 14:19:38 2022 +0000

    Merge tag 'mlx5-fixes-2022-02-01' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
    
    Saeed Mahameed says:
    
    ====================
    mlx5 fixes 2022-02-01
    
    This series provides bug fixes to mlx5 driver.
    Please pull and let me know if there is any problem.
    
    Sorry about the long series, but I had to move the top two patches from
    net-next to net to help avoiding a build break when kspp branch is merged
    into linus-next on next merge window.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a3f781a9d6114c1d1e01defb7aa234dec45d2a5f
Author: Helge Deller <deller@gmx.de>
Date:   Wed Feb 2 14:55:31 2022 +0100

    fbcon: Add option to enable legacy hardware acceleration
    
    Add a config option CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION to
    enable bitblt and fillrect hardware acceleration in the framebuffer
    console. If disabled, such acceleration will not be used, even if it is
    supported by the graphics hardware driver.
    
    If you plan to use DRM as your main graphics output system, you should
    disable this option since it will prevent compiling in code which isn't
    used later on when DRM takes over.
    
    For all other configurations, e.g. if none of your graphic cards support
    DRM (yet), DRM isn't available for your architecture, or you can't be
    sure that the graphic card in the target system will support DRM, you
    most likely want to enable this option.
    
    In the non-accelerated case (e.g. when DRM is used), the inlined
    fb_scrollmode() function is hardcoded to return SCROLL_REDRAW and as such the
    compiler is able to optimize much unneccesary code away.
    
    In this v3 patch version I additionally changed the GETVYRES() and GETVXRES()
    macros to take a pointer to the fbcon_display struct. This fixes the build when
    console rotation is enabled and helps the compiler again to optimize out code.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org # v5.10+
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220202135531.92183-4-deller@gmx.de

commit 87ab9f6b7417349aa197a6c7098d4fdd4beebb74
Author: Helge Deller <deller@gmx.de>
Date:   Wed Feb 2 14:55:30 2022 +0100

    Revert "fbcon: Disable accelerated scrolling"
    
    This reverts commit 39aead8373b3c20bb5965c024dfb51a94e526151.
    
    Revert the first (of 2) commits which disabled scrolling acceleration in
    fbcon/fbdev.  It introduced a regression for fbdev-supported graphic cards
    because of the performance penalty by doing screen scrolling by software
    instead of using the existing graphic card 2D hardware acceleration.
    
    Console scrolling acceleration was disabled by dropping code which
    checked at runtime the driver hardware capabilities for the
    BINFO_HWACCEL_COPYAREA or FBINFO_HWACCEL_FILLRECT flags and if set, it
    enabled scrollmode SCROLL_MOVE which uses hardware acceleration to move
    screen contents.  After dropping those checks scrollmode was hard-wired
    to SCROLL_REDRAW instead, which forces all graphic cards to redraw every
    character at the new screen position when scrolling.
    
    This change effectively disabled all hardware-based scrolling acceleration for
    ALL drivers, because now all kind of 2D hardware acceleration (bitblt,
    fillrect) in the drivers isn't used any longer.
    
    The original commit message mentions that only 3 DRM drivers (nouveau, omapdrm
    and gma500) used hardware acceleration in the past and thus code for checking
    and using scrolling acceleration is obsolete.
    
    This statement is NOT TRUE, because beside the DRM drivers there are around 35
    other fbdev drivers which depend on fbdev/fbcon and still provide hardware
    acceleration for fbdev/fbcon.
    
    The original commit message also states that syzbot found lots of bugs in fbcon
    and thus it's "often the solution to just delete code and remove features".
    This is true, and the bugs - which actually affected all users of fbcon,
    including DRM - were fixed, or code was dropped like e.g. the support for
    software scrollback in vgacon (commit 973c096f6a85).
    
    So to further analyze which bugs were found by syzbot, I've looked through all
    patches in drivers/video which were tagged with syzbot or syzkaller back to
    year 2005. The vast majority fixed the reported issues on a higher level, e.g.
    when screen is to be resized, or when font size is to be changed. The few ones
    which touched driver code fixed a real driver bug, e.g. by adding a check.
    
    But NONE of those patches touched code of either the SCROLL_MOVE or the
    SCROLL_REDRAW case.
    
    That means, there was no real reason why SCROLL_MOVE had to be ripped-out and
    just SCROLL_REDRAW had to be used instead. The only reason I can imagine so far
    was that SCROLL_MOVE wasn't used by DRM and as such it was assumed that it
    could go away. That argument completely missed the fact that SCROLL_MOVE is
    still heavily used by fbdev (non-DRM) drivers.
    
    Some people mention that using memcpy() instead of the hardware acceleration is
    pretty much the same speed. But that's not true, at least not for older graphic
    cards and machines where we see speed decreases by factor 10 and more and thus
    this change leads to console responsiveness way worse than before.
    
    That's why the original commit is to be reverted. By reverting we
    reintroduce hardware-based scrolling acceleration and fix the
    performance regression for fbdev drivers.
    
    There isn't any impact on DRM when reverting those patches.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Sven Schnelle <svens@stackframe.org>
    Cc: stable@vger.kernel.org # v5.10+
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220202135531.92183-3-deller@gmx.de

commit 1148836fd3226c20de841084aba24184d4fbbe77
Author: Helge Deller <deller@gmx.de>
Date:   Wed Feb 2 14:55:29 2022 +0100

    Revert "fbdev: Garbage collect fbdev scrolling acceleration, part 1 (from TODO list)"
    
    This reverts commit b3ec8cdf457e5e63d396fe1346cc788cf7c1b578.
    
    Revert the second (of 2) commits which disabled scrolling acceleration
    in fbcon/fbdev.  It introduced a regression for fbdev-supported graphic
    cards because of the performance penalty by doing screen scrolling by
    software instead of using the existing graphic card 2D hardware
    acceleration.
    
    Console scrolling acceleration was disabled by dropping code which
    checked at runtime the driver hardware capabilities for the
    BINFO_HWACCEL_COPYAREA or FBINFO_HWACCEL_FILLRECT flags and if set, it
    enabled scrollmode SCROLL_MOVE which uses hardware acceleration to move
    screen contents.  After dropping those checks scrollmode was hard-wired
    to SCROLL_REDRAW instead, which forces all graphic cards to redraw every
    character at the new screen position when scrolling.
    
    This change effectively disabled all hardware-based scrolling acceleration for
    ALL drivers, because now all kind of 2D hardware acceleration (bitblt,
    fillrect) in the drivers isn't used any longer.
    
    The original commit message mentions that only 3 DRM drivers (nouveau, omapdrm
    and gma500) used hardware acceleration in the past and thus code for checking
    and using scrolling acceleration is obsolete.
    
    This statement is NOT TRUE, because beside the DRM drivers there are around 35
    other fbdev drivers which depend on fbdev/fbcon and still provide hardware
    acceleration for fbdev/fbcon.
    
    The original commit message also states that syzbot found lots of bugs in fbcon
    and thus it's "often the solution to just delete code and remove features".
    This is true, and the bugs - which actually affected all users of fbcon,
    including DRM - were fixed, or code was dropped like e.g. the support for
    software scrollback in vgacon (commit 973c096f6a85).
    
    So to further analyze which bugs were found by syzbot, I've looked through all
    patches in drivers/video which were tagged with syzbot or syzkaller back to
    year 2005. The vast majority fixed the reported issues on a higher level, e.g.
    when screen is to be resized, or when font size is to be changed. The few ones
    which touched driver code fixed a real driver bug, e.g. by adding a check.
    
    But NONE of those patches touched code of either the SCROLL_MOVE or the
    SCROLL_REDRAW case.
    
    That means, there was no real reason why SCROLL_MOVE had to be ripped-out and
    just SCROLL_REDRAW had to be used instead. The only reason I can imagine so far
    was that SCROLL_MOVE wasn't used by DRM and as such it was assumed that it
    could go away. That argument completely missed the fact that SCROLL_MOVE is
    still heavily used by fbdev (non-DRM) drivers.
    
    Some people mention that using memcpy() instead of the hardware acceleration is
    pretty much the same speed. But that's not true, at least not for older graphic
    cards and machines where we see speed decreases by factor 10 and more and thus
    this change leads to console responsiveness way worse than before.
    
    That's why the original commit is to be reverted. By reverting we
    reintroduce hardware-based scrolling acceleration and fix the
    performance regression for fbdev drivers.
    
    There isn't any impact on DRM when reverting those patches.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Sven Schnelle <svens@stackframe.org>
    Cc: stable@vger.kernel.org # v5.16+
    Signed-off-by: Helge Deller <deller@gmx.de>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220202135531.92183-2-deller@gmx.de

commit 91aaea527bc3b707c5d3208cde035421ed54f79c
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Mon Jan 31 22:48:33 2022 +0530

    HID: amd_sfh: Add illuminance mask to limit ALS max value
    
    ALS illuminance value present only in first 15 bits from SFH firmware
    for V2 platforms. Hence added a mask of 15 bit to limit ALS max
    illuminance values to get correct illuminance value.
    
    Fixes: 0aad9c95eb9a ("HID: amd_sfh: Extend ALS support for newer AMD platform")
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit a7072c01c3ac3ae6ecd08fa7b43431cfc8ed331f
Author: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Date:   Mon Jan 31 22:48:32 2022 +0530

    HID: amd_sfh: Increase sensor command timeout
    
    HPD sensors take more time to initialize. Hence increasing sensor
    command timeout to get response with status within a max timeout.
    
    Fixes: 173709f50e98 ("HID: amd_sfh: Add command response to check command status")
    Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 2787710f73fcce4a9bdab540aaf1aef778a27462
Author: Daniel Thompson <daniel.thompson@linaro.org>
Date:   Fri Jan 28 17:46:25 2022 +0000

    HID: i2c-hid: goodix: Fix a lockdep splat
    
    I'm was on the receiving end of a lockdep splat from this driver and after
    scratching my head I couldn't be entirely sure it was a false positive
    given we would also have to think about whether the regulator locking is
    safe (since the notifier is called whilst holding regulator locks which
    are also needed for regulator_is_enabled() ).
    
    Regardless of whether it is a real bug or not, the mutex isn't needed.
    We can use reference counting tricks instead to avoid races with the
    notifier calls.
    
    The observed splat follows:
    
    ------------------------------------------------------
    kworker/u16:3/127 is trying to acquire lock:
    ffff00008021fb20 (&ihid_goodix->regulator_mutex){+.+.}-{4:4}, at: ihid_goodix_vdd_notify+0x30/0x94
    
    but task is already holding lock:
    ffff0000835c60c0 (&(&rdev->notifier)->rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x30/0x70
    
    which lock already depends on the new lock.
    
    the existing dependency chain (in reverse order) is:
    
    -> #1 (&(&rdev->notifier)->rwsem){++++}-{4:4}:
           down_write+0x68/0x8c
           blocking_notifier_chain_register+0x54/0x70
           regulator_register_notifier+0x1c/0x24
           devm_regulator_register_notifier+0x58/0x98
           i2c_hid_of_goodix_probe+0xdc/0x158
           i2c_device_probe+0x25d/0x270
           really_probe+0x174/0x2cc
           __driver_probe_device+0xc0/0xd8
           driver_probe_device+0x50/0xe4
           __device_attach_driver+0xa8/0xc0
           bus_for_each_drv+0x9c/0xc0
           __device_attach_async_helper+0x6c/0xbc
           async_run_entry_fn+0x38/0x100
           process_one_work+0x294/0x438
           worker_thread+0x180/0x258
           kthread+0x120/0x130
           ret_from_fork+0x10/0x20
    
    -> #0 (&ihid_goodix->regulator_mutex){+.+.}-{4:4}:
           __lock_acquire+0xd24/0xfe8
           lock_acquire+0x288/0x2f4
           __mutex_lock+0xa0/0x338
           mutex_lock_nested+0x3c/0x5c
           ihid_goodix_vdd_notify+0x30/0x94
           notifier_call_chain+0x6c/0x8c
           blocking_notifier_call_chain+0x48/0x70
           _notifier_call_chain.isra.0+0x18/0x20
           _regulator_enable+0xc0/0x178
           regulator_enable+0x40/0x7c
           goodix_i2c_hid_power_up+0x18/0x20
           i2c_hid_core_power_up.isra.0+0x1c/0x2c
           i2c_hid_core_probe+0xd8/0x3d4
           i2c_hid_of_goodix_probe+0x14c/0x158
           i2c_device_probe+0x25c/0x270
           really_probe+0x174/0x2cc
           __driver_probe_device+0xc0/0xd8
           driver_probe_device+0x50/0xe4
           __device_attach_driver+0xa8/0xc0
           bus_for_each_drv+0x9c/0xc0
           __device_attach_async_helper+0x6c/0xbc
           async_run_entry_fn+0x38/0x100
           process_one_work+0x294/0x438
           worker_thread+0x180/0x258
           kthread+0x120/0x130
           ret_from_fork+0x10/0x20
    
    other info that might help us debug this:
    
     Possible unsafe locking scenario:
    
           CPU0                    CPU1
           ----                    ----
      lock(&(&rdev->notifier)->rwsem);
                                   lock(&ihid_goodix->regulator_mutex);
                                   lock(&(&rdev->notifier)->rwsem);
      lock(&ihid_goodix->regulator_mutex);
    
     *** DEADLOCK ***
    
    Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
    Fixes: 18eeef46d359 ("HID: i2c-hid: goodix: Tie the reset line to true state of the regulator")
    Reviewed-by: Douglas Anderson <dianders@chromium.org>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 403271548a840dd4f884088d6333e09f899be5ff
Author: Anup Patel <apatel@ventanamicro.com>
Date:   Mon Jan 31 22:12:32 2022 +0530

    RISC-V: KVM: Fix SBI implementation version
    
    The SBI implementation version returned by KVM RISC-V should be the
    Host Linux version code.
    
    Fixes: c62a76859723 ("RISC-V: KVM: Add SBI v0.2 base extension")
    Signed-off-by: Anup Patel <apatel@ventanamicro.com>
    Reviewed-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Anup Patel <anup@brainfault.org>

commit de1d7b6a51dab546160d252e47baa54adf104d4a
Author: Mayuresh Chitale <mchitale@ventanamicro.com>
Date:   Mon Jan 31 16:33:07 2022 +0530

    RISC-V: KVM: make CY, TM, and IR counters accessible in VU mode
    
    Those applications that run in VU mode and access the time CSR cause
    a virtual instruction trap as Guest kernel currently does not
    initialize the scounteren CSR.
    
    To fix this, we should make CY, TM, and IR counters accessibile
    by default in VU mode (similar to OpenSBI).
    
    Fixes: a33c72faf2d73 ("RISC-V: KVM: Implement VCPU create, init and
    destroy functions")
    Cc: stable@vger.kernel.org
    Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
    Signed-off-by: Anup Patel <anup@brainfault.org>

commit 6455317e4d0d8395e8e4a2fd1ec8d6502267dd02
Author: Mark Rutland <mark.rutland@arm.com>
Date:   Tue Feb 1 13:29:25 2022 +0000

    kvm/riscv: rework guest entry logic
    
    In kvm_arch_vcpu_ioctl_run() we enter an RCU extended quiescent state
    (EQS) by calling guest_enter_irqoff(), and unmask IRQs prior to exiting
    the EQS by calling guest_exit(). As the IRQ entry code will not wake RCU
    in this case, we may run the core IRQ code and IRQ handler without RCU
    watching, leading to various potential problems.
    
    Additionally, we do not inform lockdep or tracing that interrupts will
    be enabled during guest execution, which caan lead to misleading traces
    and warnings that interrupts have been enabled for overly-long periods.
    
    This patch fixes these issues by using the new timing and context
    entry/exit helpers to ensure that interrupts are handled during guest
    vtime but with RCU watching, with a sequence:
    
            guest_timing_enter_irqoff();
    
            guest_state_enter_irqoff();
            < run the vcpu >
            guest_state_exit_irqoff();
    
            < take any pending IRQs >
    
            guest_timing_exit_irqoff();
    
    Since instrumentation may make use of RCU, we must also ensure that no
    instrumented code is run during the EQS. I've split out the critical
    section into a new kvm_riscv_enter_exit_vcpu() helper which is marked
    noinstr.
    
    Fixes: 99cdc6c18c2d815e ("RISC-V: Add initial skeletal KVM support")
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Cc: Albert Ou <aou@eecs.berkeley.edu>
    Cc: Anup Patel <anup@brainfault.org>
    Cc: Atish Patra <atishp@atishpatra.org>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Paul E. McKenney <paulmck@kernel.org>
    Cc: Paul Walmsley <paul.walmsley@sifive.com>
    Tested-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Anup Patel <anup@brainfault.org>

commit 1d9093457b243061a9bba23543c38726e864a643
Author: Tristan Hume <tristan@thume.ca>
Date:   Thu Jan 27 17:08:06 2022 -0500

    perf/x86/intel/pt: Fix crash with stop filters in single-range mode
    
    Add a check for !buf->single before calling pt_buffer_region_size in a
    place where a missing check can cause a kernel crash.
    
    Fixes a bug introduced by commit 670638477aed ("perf/x86/intel/pt:
    Opportunistically use single range output mode"), which added a
    support for PT single-range output mode. Since that commit if a PT
    stop filter range is hit while tracing, the kernel will crash because
    of a null pointer dereference in pt_handle_status due to calling
    pt_buffer_region_size without a ToPA configured.
    
    The commit which introduced single-range mode guarded almost all uses of
    the ToPA buffer variables with checks of the buf->single variable, but
    missed the case where tracing was stopped by the PT hardware, which
    happens when execution hits a configured stop filter.
    
    Tested that hitting a stop filter while PT recording successfully
    records a trace with this patch but crashes without this patch.
    
    Fixes: 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode")
    Signed-off-by: Tristan Hume <tristan@thume.ca>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
    Cc: stable@kernel.org
    Link: https://lkml.kernel.org/r/20220127220806.73664-1-tristan@thume.ca

commit ddecd22878601a606d160680fa85802b75d92eb6
Author: Marco Elver <elver@google.com>
Date:   Mon Jan 31 11:34:07 2022 +0100

    perf: uapi: Document perf_event_attr::sig_data truncation on 32 bit architectures
    
    Due to the alignment requirements of siginfo_t, as described in
    3ddb3fd8cdb0 ("signal, perf: Fix siginfo_t by avoiding u64 on 32-bit
    architectures"), siginfo_t::si_perf_data is limited to an unsigned long.
    
    However, perf_event_attr::sig_data is an u64, to avoid having to deal
    with compat conversions. Due to being an u64, it may not immediately be
    clear to users that sig_data is truncated on 32 bit architectures.
    
    Add a comment to explicitly point this out, and hopefully help some
    users save time by not having to deduce themselves what's happening.
    
    Reported-by: Dmitry Vyukov <dvyukov@google.com>
    Signed-off-by: Marco Elver <elver@google.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
    Link: https://lore.kernel.org/r/20220131103407.1971678-3-elver@google.com

commit 95d29fa104523b1756323f7003294b1711c27808
Author: Marco Elver <elver@google.com>
Date:   Mon Jan 31 11:34:06 2022 +0100

    selftests/perf_events: Test modification of perf_event_attr::sig_data
    
    Test that PERF_EVENT_IOC_MODIFY_ATTRIBUTES correctly modifies
    perf_event_attr::sig_data as well.
    
    Signed-off-by: Marco Elver <elver@google.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
    Link: https://lore.kernel.org/r/20220131103407.1971678-2-elver@google.com

commit 3c25fc97f5590060464cabfa25710970ecddbc96
Author: Marco Elver <elver@google.com>
Date:   Mon Jan 31 11:34:05 2022 +0100

    perf: Copy perf_event_attr::sig_data on modification
    
    The intent has always been that perf_event_attr::sig_data should also be
    modifiable along with PERF_EVENT_IOC_MODIFY_ATTRIBUTES, because it is
    observable by user space if SIGTRAP on events is requested.
    
    Currently only PERF_TYPE_BREAKPOINT is modifiable, and explicitly copies
    relevant breakpoint-related attributes in hw_breakpoint_copy_attr().
    This misses copying perf_event_attr::sig_data.
    
    Since sig_data is not specific to PERF_TYPE_BREAKPOINT, introduce a
    helper to copy generic event-type-independent attributes on
    modification.
    
    Fixes: 97ba62b27867 ("perf: Add support for SIGTRAP on perf events")
    Reported-by: Dmitry Vyukov <dvyukov@google.com>
    Signed-off-by: Marco Elver <elver@google.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
    Link: https://lore.kernel.org/r/20220131103407.1971678-1-elver@google.com

commit a01994f5e5c79d3a35e5e8cf4252c7f2147323c3
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Thu Jan 27 12:32:51 2022 +0100

    x86/perf: Default set FREEZE_ON_SMI for all
    
    Kyle reported that rr[0] has started to malfunction on Comet Lake and
    later CPUs due to EFI starting to make use of CPL3 [1] and the PMU
    event filtering not distinguishing between regular CPL3 and SMM CPL3.
    
    Since this is a privilege violation, default disable SMM visibility
    where possible.
    
    Administrators wanting to observe SMM cycles can easily change this
    using the sysfs attribute while regular users don't have access to
    this file.
    
    [0] https://rr-project.org/
    
    [1] See the Intel white paper "Trustworthy SMM on the Intel vPro Platform"
    at https://bugzilla.kernel.org/attachment.cgi?id=300300, particularly the
    end of page 5.
    
    Reported-by: Kyle Huey <me@kylehuey.com>
    Suggested-by: Andrew Cooper <Andrew.Cooper3@citrix.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: stable@kernel.org
    Link: https://lkml.kernel.org/r/YfKChjX61OW4CkYm@hirez.programming.kicks-ass.net

commit 2cba05451a6d0c703bb74f1a250691404f27c4f1
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Mon Jan 31 11:35:53 2022 +0100

    gpio: aggregator: Fix calling into sleeping GPIO controllers
    
    If the parent GPIO controller is a sleeping controller (e.g. a GPIO
    controller connected to I2C), getting or setting a GPIO triggers a
    might_sleep() warning.  This happens because the GPIO Aggregator takes
    the can_sleep flag into account only for its internal locking, not for
    calling into the parent GPIO controller.
    
    Fix this by using the gpiod_[gs]et*_cansleep() APIs when calling into a
    sleeping GPIO controller.
    
    Reported-by: Mikko Salomäki <ms@datarespons.se>
    Fixes: 828546e24280f721 ("gpio: Add GPIO Aggregator")
    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 1d4df649cbb4b26d19bea38ecff4b65b10a1bbca
Author: Guo Ren <guoren@kernel.org>
Date:   Sun Jan 30 21:56:34 2022 +0800

    irqchip/sifive-plic: Add missing thead,c900-plic match string
    
    The thead,c900-plic has been used in opensbi to distinguish
    PLIC [1]. Although PLICs have the same behaviors in Linux,
    they are different hardware with some custom initializing in
    firmware(opensbi).
    
    Qute opensbi patch commit-msg by Samuel:
    
      The T-HEAD PLIC implementation requires setting a delegation bit
      to allow access from S-mode. Now that the T-HEAD PLIC has its own
      compatible string, set this bit automatically from the PLIC driver,
      instead of reaching into the PLIC's MMIO space from another driver.
    
    [1]: https://github.com/riscv-software-src/opensbi/commit/78c2b19218bd62653b9fb31623a42ced45f38ea6
    
    Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
    Cc: Anup Patel <anup@brainfault.org>
    Cc: Marc Zyngier <maz@kernel.org>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Samuel Holland <samuel@sholland.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Tested-by: Samuel Holland <samuel@sholland.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220130135634.1213301-3-guoren@kernel.org

commit 321a8be37e1a93cefeae990107533142c8515933
Author: Guo Ren <guoren@kernel.org>
Date:   Sun Jan 30 21:56:33 2022 +0800

    dt-bindings: update riscv plic compatible string
    
    Add the compatible string "thead,c900-plic" to the riscv plic
    bindings to support allwinner d1 SOC which contains c906 core.
    
    Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
    Cc: Anup Patel <anup@brainfault.org>
    Cc: Heiko Stuebner <heiko@sntech.de>
    Cc: Rob Herring <robh@kernel.org>
    Cc: Rob Herring <robh+dt@kernel.org>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Samuel Holland <samuel@sholland.org>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220130135634.1213301-2-guoren@kernel.org

commit eba1e44beef88aa722f07755f79f604cd5d92290
Author: Marc Zyngier <maz@kernel.org>
Date:   Wed Feb 2 10:34:54 2022 +0000

    irqchip/gic-v3-its: Skip HP notifier when no ITS is registered
    
    We have some systems out there that have both LPI support and an
    ITS, but that don't expose the ITS in their firmware tables
    (either because it is broken or because they run under a hypervisor
    that hides it...).
    
    Is such a configuration, we still register the HP notifier to free
    the allocated tables if needed, resulting in a warning as there is
    no memory to free (nothing was allocated the first place).
    
    Fix it by keying the HP notifier on the presence of at least one
    sucessfully probed ITS.
    
    Fixes: d23bc2bc1d63 ("irqchip/gic-v3-its: Postpone LPI pending table freeing and memreserve")
    Reported-by: Steev Klimaszewski <steev@kali.org>
    Tested-by: Steev Klimaszewski <steev@kali.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Cc: Valentin Schneider <valentin.schneider@arm.com>
    Link: https://lore.kernel.org/r/20220202103454.2480465-1-maz@kernel.org

commit 2c212e1baedcd782b2535a3f86bc491977677c0e
Author: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Date:   Fri Jan 28 15:06:43 2022 +0100

    KVM: s390: Return error on SIDA memop on normal guest
    
    Refuse SIDA memops on guests which are not protected.
    For normal guests, the secure instruction data address designation,
    which determines the location we access, is not under control of KVM.
    
    Fixes: 19e122776886 (KVM: S390: protvirt: Introduce instruction data area bounce buffer)
    Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>

commit b6bb1722f34bbdbabed27acdceaf585d300c5fd2
Author: Sagi Grimberg <sagi@grimberg.me>
Date:   Tue Feb 1 14:54:21 2022 +0200

    nvme-rdma: fix possible use-after-free in transport error_recovery work
    
    While nvme_rdma_submit_async_event_work is checking the ctrl and queue
    state before preparing the AER command and scheduling io_work, in order
    to fully prevent a race where this check is not reliable the error
    recovery work must flush async_event_work before continuing to destroy
    the admin queue after setting the ctrl state to RESETTING such that
    there is no race .submit_async_event and the error recovery handler
    itself changing the ctrl state.
    
    Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

commit ff9fc7ebf5c06de1ef72a69f9b1ab40af8b07f9e
Author: Sagi Grimberg <sagi@grimberg.me>
Date:   Tue Feb 1 14:54:20 2022 +0200

    nvme-tcp: fix possible use-after-free in transport error_recovery work
    
    While nvme_tcp_submit_async_event_work is checking the ctrl and queue
    state before preparing the AER command and scheduling io_work, in order
    to fully prevent a race where this check is not reliable the error
    recovery work must flush async_event_work before continuing to destroy
    the admin queue after setting the ctrl state to RESETTING such that
    there is no race .submit_async_event and the error recovery handler
    itself changing the ctrl state.
    
    Tested-by: Chris Leech <cleech@redhat.com>
    Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

commit 0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d
Author: Sagi Grimberg <sagi@grimberg.me>
Date:   Tue Feb 1 14:54:19 2022 +0200

    nvme: fix a possible use-after-free in controller reset during load
    
    Unlike .queue_rq, in .submit_async_event drivers may not check the ctrl
    readiness for AER submission. This may lead to a use-after-free
    condition that was observed with nvme-tcp.
    
    The race condition may happen in the following scenario:
    1. driver executes its reset_ctrl_work
    2. -> nvme_stop_ctrl - flushes ctrl async_event_work
    3. ctrl sends AEN which is received by the host, which in turn
       schedules AEN handling
    4. teardown admin queue (which releases the queue socket)
    5. AEN processed, submits another AER, calling the driver to submit
    6. driver attempts to send the cmd
    ==> use-after-free
    
    In order to fix that, add ctrl state check to validate the ctrl
    is actually able to accept the AER submission.
    
    This addresses the above race in controller resets because the driver
    during teardown should:
    1. change ctrl state to RESETTING
    2. flush async_event_work (as well as other async work elements)
    
    So after 1,2, any other AER command will find the
    ctrl state to be RESETTING and bail out without submitting the AER.
    
    Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

commit 3aa430d33b8dd4d3f996af9966833c7a51834fb8
Merge: c7108979a010f cad014b7b5a68
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Feb 1 21:03:15 2022 -0800

    Merge branch '1GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-02-01
    
    This series contains updates to e1000e driver only.
    
    Sasha removes CSME handshake with TGL platform as this is not supported
    and is causing hardware unit hangs to be reported.
    
    * '1GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue:
      e1000e: Handshake with CSME starts from ADL platforms
      e1000e: Separate ADP board type from TGP
    ====================
    
    Link: https://lore.kernel.org/r/20220201173754.580305-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9a8406ba1a9a2965c27e0db1d7753471d12ee9ff
Author: Liu Ying <victor.liu@nxp.com>
Date:   Mon Jan 24 10:40:07 2022 +0800

    phy: dphy: Correct clk_pre parameter
    
    The D-PHY specification (v1.2) explicitly mentions that the T-CLK-PRE
    parameter's unit is Unit Interval(UI) and the minimum value is 8.  Also,
    kernel doc of the 'clk_pre' member of struct phy_configure_opts_mipi_dphy
    mentions that it should be in UI.  However, the dphy core driver wrongly
    sets 'clk_pre' to 8000, which seems to hint that it's in picoseconds.
    
    So, let's fix the dphy core driver to correctly reflect the T-CLK-PRE
    parameter's minimum value according to the D-PHY specification.
    
    I'm assuming that all impacted custom drivers shall program values in
    TxByteClkHS cycles into hardware for the T-CLK-PRE parameter.  The D-PHY
    specification mentions that the frequency of TxByteClkHS is exactly 1/8
    the High-Speed(HS) bit rate(each HS bit consumes one UI).  So, relevant
    custom driver code is changed to program those values as
    DIV_ROUND_UP(cfg->clk_pre, BITS_PER_BYTE), then.
    
    Note that I've only tested the patch with RM67191 DSI panel on i.MX8mq EVK.
    Help is needed to test with other i.MX8mq, Meson and Rockchip platforms,
    as I don't have the hardwares.
    
    Fixes: 2ed869990e14 ("phy: Add MIPI D-PHY configuration options")
    Tested-by: Liu Ying <victor.liu@nxp.com> # RM67191 DSI panel on i.MX8mq EVK
    Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
    Reviewed-by: Neil Armstrong <narmstrong@baylibre.com> # for phy-meson-axg-mipi-dphy.c
    Tested-by: Neil Armstrong <narmstrong@baylibre.com> # for phy-meson-axg-mipi-dphy.c
    Tested-by: Guido Günther <agx@sigxcpu.org> # Librem 5 (imx8mq) with it's rather picky panel
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Signed-off-by: Liu Ying <victor.liu@nxp.com>
    Link: https://lore.kernel.org/r/20220124024007.1465018-1-victor.liu@nxp.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit ad5185735f7dab342fdd0dd41044da4c9ccfef67
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Jan 24 09:20:28 2022 -0800

    net/mlx5e: Avoid field-overflowing memcpy()
    
    In preparation for FORTIFY_SOURCE performing compile-time and run-time
    field bounds checking for memcpy(), memmove(), and memset(), avoid
    intentionally writing across neighboring fields.
    
    Use flexible arrays instead of zero-element arrays (which look like they
    are always overflowing) and split the cross-field memcpy() into two halves
    that can be appropriately bounds-checked by the compiler.
    
    We were doing:
    
            #define ETH_HLEN  14
            #define VLAN_HLEN  4
            ...
            #define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN)
            ...
            struct mlx5e_tx_wqe      *wqe  = mlx5_wq_cyc_get_wqe(wq, pi);
            ...
            struct mlx5_wqe_eth_seg  *eseg = &wqe->eth;
            struct mlx5_wqe_data_seg *dseg = wqe->data;
            ...
            memcpy(eseg->inline_hdr.start, xdptxd->data, MLX5E_XDP_MIN_INLINE);
    
    target is wqe->eth.inline_hdr.start (which the compiler sees as being
    2 bytes in size), but copying 18, intending to write across start
    (really vlan_tci, 2 bytes). The remaining 16 bytes get written into
    wqe->data[0], covering byte_count (4 bytes), lkey (4 bytes), and addr
    (8 bytes).
    
    struct mlx5e_tx_wqe {
            struct mlx5_wqe_ctrl_seg   ctrl;                 /*     0    16 */
            struct mlx5_wqe_eth_seg    eth;                  /*    16    16 */
            struct mlx5_wqe_data_seg   data[];               /*    32     0 */
    
            /* size: 32, cachelines: 1, members: 3 */
            /* last cacheline: 32 bytes */
    };
    
    struct mlx5_wqe_eth_seg {
            u8                         swp_outer_l4_offset;  /*     0     1 */
            u8                         swp_outer_l3_offset;  /*     1     1 */
            u8                         swp_inner_l4_offset;  /*     2     1 */
            u8                         swp_inner_l3_offset;  /*     3     1 */
            u8                         cs_flags;             /*     4     1 */
            u8                         swp_flags;            /*     5     1 */
            __be16                     mss;                  /*     6     2 */
            __be32                     flow_table_metadata;  /*     8     4 */
            union {
                    struct {
                            __be16     sz;                   /*    12     2 */
                            u8         start[2];             /*    14     2 */
                    } inline_hdr;                            /*    12     4 */
                    struct {
                            __be16     type;                 /*    12     2 */
                            __be16     vlan_tci;             /*    14     2 */
                    } insert;                                /*    12     4 */
                    __be32             trailer;              /*    12     4 */
            };                                               /*    12     4 */
    
            /* size: 16, cachelines: 1, members: 9 */
            /* last cacheline: 16 bytes */
    };
    
    struct mlx5_wqe_data_seg {
            __be32                     byte_count;           /*     0     4 */
            __be32                     lkey;                 /*     4     4 */
            __be64                     addr;                 /*     8     8 */
    
            /* size: 16, cachelines: 1, members: 3 */
            /* last cacheline: 16 bytes */
    };
    
    So, split the memcpy() so the compiler can reason about the buffer
    sizes.
    
    "pahole" shows no size nor member offset changes to struct mlx5e_tx_wqe
    nor struct mlx5e_umr_wqe. "objdump -d" shows no meaningful object
    code changes (i.e. only source line number induced differences and
    optimizations).
    
    Fixes: b5503b994ed5 ("net/mlx5e: XDP TX forwarding support")
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 6d5c900eb64107001e91e1f46bddc254dded8a59
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Jan 24 09:22:41 2022 -0800

    net/mlx5e: Use struct_group() for memcpy() region
    
    In preparation for FORTIFY_SOURCE performing compile-time and run-time
    field bounds checking for memcpy(), memmove(), and memset(), avoid
    intentionally writing across neighboring fields.
    
    Use struct_group() in struct vlan_ethhdr around members h_dest and
    h_source, so they can be referenced together. This will allow memcpy()
    and sizeof() to more easily reason about sizes, improve readability,
    and avoid future warnings about writing beyond the end of h_dest.
    
    "pahole" shows no size nor member offset changes to struct vlan_ethhdr.
    "objdump -d" shows no object code changes.
    
    Fixes: 34802a42b352 ("net/mlx5e: Do not modify the TX SKB")
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5b209d1a22afabfb7d644abb10510c5713a3e569
Author: Roi Dayan <roid@nvidia.com>
Date:   Tue Feb 1 15:27:48 2022 +0200

    net/mlx5e: Avoid implicit modify hdr for decap drop rule
    
    Currently the driver adds implicit modify hdr action for
    decap rules on tunnel devices if the port is an ovs port.
    This is also done if the action is drop and makes the modify
    hdr redundant and also the FW doesn't support it and will generate
    a syndrome.
    
    kernel: mlx5_core 0000:08:00.0: mlx5_cmd_check:777:(pid 102063): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x8708c3)
    
    Fix it by adding the implicit modify hdr only for fwd actions.
    
    Fixes: b16eb3c81fe2 ("net/mlx5: Support internal port as decap route device")
    Fixes: 077cdda764c7 ("net/mlx5e: TC, Fix memory leak with rules with internal port")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Ariel Levkovich <lariel@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit de47db0cf7f4a9c555ad204e06baa70b50a70d08
Author: Raed Salem <raeds@nvidia.com>
Date:   Thu Dec 2 17:49:01 2021 +0200

    net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
    
    IPsec Tunnel mode crypto offload software parser (SWP) setting in data
    path currently always set the inner L4 offset regardless of the
    encapsulated L4 header type and whether it exists in the first place,
    this breaks non TCP/UDP traffic as such.
    
    Set the SWP inner L4 offset only when the IPsec tunnel encapsulated L4
    header protocol is TCP/UDP.
    
    While at it fix inner ip protocol read for setting MLX5_ETH_WQE_SWP_INNER_L4_UDP
    flag to address the case where the ip header protocol is IPv6.
    
    Fixes: f1267798c980 ("net/mlx5: Fix checksum issue of VXLAN and IPsec crypto offload")
    Signed-off-by: Raed Salem <raeds@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5352859b3bfa0ca188b2f1d2c1436fddc781e3b6
Author: Raed Salem <raeds@nvidia.com>
Date:   Thu Dec 2 17:43:50 2021 +0200

    net/mlx5e: IPsec: Fix crypto offload for non TCP/UDP encapsulated traffic
    
    IPsec crypto offload always set the ethernet segment checksum flags with
    the inner L4 header checksum flag enabled for encapsulated IPsec offloaded
    packet regardless of the encapsulated L4 header type, and even if it
    doesn't exists in the first place, this breaks non TCP/UDP traffic as
    such.
    
    Set the inner L4 checksum flag only when the encapsulated L4 header
    protocol is TCP/UDP using software parser swp_inner_l4_offset field as
    indication.
    
    Fixes: 5cfb540ef27b ("net/mlx5e: Set IPsec WAs only in IP's non checksum partial case.")
    Signed-off-by: Raed Salem <raeds@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 736dfe4e68b868829a1e89dfef4a44c1580d4478
Author: Maxim Mikityanskiy <maximmi@nvidia.com>
Date:   Tue Jan 18 13:31:54 2022 +0200

    net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
    
    The hardware spec defines max_average_bw == 0 as "unlimited bandwidth".
    max_average_bw is calculated as `ceil / BYTES_IN_MBIT`, which can become
    0 when ceil is small, leading to an undesired effect of having no
    bandwidth limit.
    
    This commit fixes it by rounding up small values of ceil to 1 Mbit/s.
    
    Fixes: 214baf22870c ("net/mlx5e: Support HTB offload")
    Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit d8e5883d694bb053b19c4142a2d1f43a34f6fe2c
Author: Maor Dickman <maord@nvidia.com>
Date:   Sun Jan 30 16:00:41 2022 +0200

    net/mlx5: E-Switch, Fix uninitialized variable modact
    
    The variable modact is not initialized before used in command
    modify header allocation which can cause command to fail.
    
    Fix by initializing modact with zeros.
    
    Addresses-Coverity: ("Uninitialized scalar variable")
    Fixes: 8f1e0b97cc70 ("net/mlx5: E-Switch, Mark miss packets with new chain id mapping")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit ec41332e02bd0acf1f24206867bb6a02f5877a62
Author: Maor Dickman <maord@nvidia.com>
Date:   Thu Jan 13 15:11:42 2022 +0200

    net/mlx5e: Fix handling of wrong devices during bond netevent
    
    Current implementation of bond netevent handler only check if
    the handled netdev is VF representor and it missing a check if
    the VF representor is on the same phys device of the bond handling
    the netevent.
    
    Fix by adding the missing check and optimizing the check if
    the netdev is VF representor so it will not access uninitialized
    private data and crashes.
    
    BUG: kernel NULL pointer dereference, address: 000000000000036c
    PGD 0 P4D 0
    Oops: 0000 [#1] SMP NOPTI
    Workqueue: eth3bond0 bond_mii_monitor [bonding]
    RIP: 0010:mlx5e_is_uplink_rep+0xc/0x50 [mlx5_core]
    RSP: 0018:ffff88812d69fd60 EFLAGS: 00010282
    RAX: 0000000000000000 RBX: ffff8881cf800000 RCX: 0000000000000000
    RDX: ffff88812d69fe10 RSI: 000000000000001b RDI: ffff8881cf800880
    RBP: ffff8881cf800000 R08: 00000445cabccf2b R09: 0000000000000008
    R10: 0000000000000004 R11: 0000000000000008 R12: ffff88812d69fe10
    R13: 00000000fffffffe R14: ffff88820c0f9000 R15: 0000000000000000
    FS:  0000000000000000(0000) GS:ffff88846fb00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 000000000000036c CR3: 0000000103d80006 CR4: 0000000000370ea0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     mlx5e_eswitch_uplink_rep+0x31/0x40 [mlx5_core]
     mlx5e_rep_is_lag_netdev+0x94/0xc0 [mlx5_core]
     mlx5e_rep_esw_bond_netevent+0xeb/0x3d0 [mlx5_core]
     raw_notifier_call_chain+0x41/0x60
     call_netdevice_notifiers_info+0x34/0x80
     netdev_lower_state_changed+0x4e/0xa0
     bond_mii_monitor+0x56b/0x640 [bonding]
     process_one_work+0x1b9/0x390
     worker_thread+0x4d/0x3d0
     ? rescuer_thread+0x350/0x350
     kthread+0x124/0x150
     ? set_kthread_struct+0x40/0x40
     ret_from_fork+0x1f/0x30
    
    Fixes: 7e51891a237f ("net/mlx5e: Use netdev events to set/del egress acl forward-to-vport rule")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 7957837b816f11eecb9146235bb0715478f4c81f
Author: Khalid Manaa <khalidm@nvidia.com>
Date:   Wed Jan 26 14:25:55 2022 +0200

    net/mlx5e: Fix broken SKB allocation in HW-GRO
    
    In case the HW doesn't perform header-data split, it will write the whole
    packet into the data buffer in the WQ, in this case the SHAMPO CQE handler
    couldn't use the header entry to build the SKB, instead it should allocate
    a new memory to build the SKB using the function:
    mlx5e_skb_from_cqe_mpwrq_nonlinear.
    
    Fixes: f97d5c2a453e ("net/mlx5e: Add handle SHAMPO cqe support")
    Signed-off-by: Khalid Manaa <khalidm@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit b8d91145ed7cfa046cc07bcfb277465b9d45da73
Author: Khalid Manaa <khalidm@nvidia.com>
Date:   Wed Jan 26 14:14:58 2022 +0200

    net/mlx5e: Fix wrong calculation of header index in HW_GRO
    
    The HW doesn't wrap the CQE.shampo.header_index field according to the
    headers buffer size, instead it always increases it until reaching overflow
    of u16 size.
    
    Thus the mlx5e_handle_rx_cqe_mpwrq_shampo handler should mask the
    CQE header_index field to find the actual header index in the headers buffer.
    
    Fixes: f97d5c2a453e ("net/mlx5e: Add handle SHAMPO cqe support")
    Signed-off-by: Khalid Manaa <khalidm@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 880b517691908fb753019b9b27cd082e7617debd
Author: Roi Dayan <roid@nvidia.com>
Date:   Mon Jan 24 13:56:26 2022 +0200

    net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
    
    When changing mode to switchdev, rep bridge init registered to netdevice
    notifier holds the devlink lock and then takes pernet_ops_rwsem.
    At that time deleting a netns holds pernet_ops_rwsem and then takes
    the devlink lock.
    
    Example sequence is:
    $ ip netns add foo
    $ devlink dev eswitch set pci/0000:00:08.0 mode switchdev &
    $ ip netns del foo
    
    deleting netns trace:
    
    [ 1185.365555]  ? devlink_pernet_pre_exit+0x74/0x1c0
    [ 1185.368331]  ? mutex_lock_io_nested+0x13f0/0x13f0
    [ 1185.370984]  ? xt_find_table+0x40/0x100
    [ 1185.373244]  ? __mutex_lock+0x24a/0x15a0
    [ 1185.375494]  ? net_generic+0xa0/0x1c0
    [ 1185.376844]  ? wait_for_completion_io+0x280/0x280
    [ 1185.377767]  ? devlink_pernet_pre_exit+0x74/0x1c0
    [ 1185.378686]  devlink_pernet_pre_exit+0x74/0x1c0
    [ 1185.379579]  ? devlink_nl_cmd_get_dumpit+0x3a0/0x3a0
    [ 1185.380557]  ? xt_find_table+0xda/0x100
    [ 1185.381367]  cleanup_net+0x372/0x8e0
    
    changing mode to switchdev trace:
    
    [ 1185.411267]  down_write+0x13a/0x150
    [ 1185.412029]  ? down_write_killable+0x180/0x180
    [ 1185.413005]  register_netdevice_notifier+0x1e/0x210
    [ 1185.414000]  mlx5e_rep_bridge_init+0x181/0x360 [mlx5_core]
    [ 1185.415243]  mlx5e_uplink_rep_enable+0x269/0x480 [mlx5_core]
    [ 1185.416464]  ? mlx5e_uplink_rep_disable+0x210/0x210 [mlx5_core]
    [ 1185.417749]  mlx5e_attach_netdev+0x232/0x400 [mlx5_core]
    [ 1185.418906]  mlx5e_netdev_attach_profile+0x15b/0x1e0 [mlx5_core]
    [ 1185.420172]  mlx5e_netdev_change_profile+0x15a/0x1d0 [mlx5_core]
    [ 1185.421459]  mlx5e_vport_rep_load+0x557/0x780 [mlx5_core]
    [ 1185.422624]  ? mlx5e_stats_grp_vport_rep_num_stats+0x10/0x10 [mlx5_core]
    [ 1185.424006]  mlx5_esw_offloads_rep_load+0xdb/0x190 [mlx5_core]
    [ 1185.425277]  esw_offloads_enable+0xd74/0x14a0 [mlx5_core]
    
    Fix this by registering rep bridges for per net netdev notifier
    instead of global one, which operats on the net namespace without holding
    the pernet_ops_rwsem.
    
    Fixes: 19e9bfa044f3 ("net/mlx5: Bridge, add offload infrastructure")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 55b2ca702cfa744a9eb108915996a2294da47e71
Author: Dima Chumak <dchumak@nvidia.com>
Date:   Mon Jan 17 15:32:16 2022 +0200

    net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
    
    Only prio 1 is supported for nic mode when there is no ignore flow level
    support in firmware. But for switchdev mode, which supports fixed number
    of statically pre-allocated prios, this restriction is not relevant so
    it can be relaxed.
    
    Fixes: d671e109bd85 ("net/mlx5: Fix tc max supported prio for nic mode")
    Signed-off-by: Dima Chumak <dchumak@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5623ef8a118838aae65363750dfafcba734dc8cb
Author: Roi Dayan <roid@nvidia.com>
Date:   Mon Jan 17 15:00:30 2022 +0200

    net/mlx5e: TC, Reject rules with forward and drop actions
    
    Such rules are redundant but allowed and passed to the driver.
    The driver does not support offloading such rules so return an error.
    
    Fixes: 03a9d11e6eeb ("net/mlx5e: Add TC drop and mirred/redirect action parsing for SRIOV offloads")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Oz Shlomo <ozsh@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 3c5193a87b0fea090aa3f769d020337662d87b5e
Author: Maher Sanalla <msanalla@nvidia.com>
Date:   Thu Jan 13 15:48:48 2022 +0200

    net/mlx5: Use del_timer_sync in fw reset flow of halting poll
    
    Substitute del_timer() with del_timer_sync() in fw reset polling
    deactivation flow, in order to prevent a race condition which occurs
    when del_timer() is called and timer is deactivated while another
    process is handling the timer interrupt. A situation that led to
    the following call trace:
            RIP: 0010:run_timer_softirq+0x137/0x420
            <IRQ>
            recalibrate_cpu_khz+0x10/0x10
            ktime_get+0x3e/0xa0
            ? sched_clock_cpu+0xb/0xc0
            __do_softirq+0xf5/0x2ea
            irq_exit_rcu+0xc1/0xf0
            sysvec_apic_timer_interrupt+0x9e/0xc0
            asm_sysvec_apic_timer_interrupt+0x12/0x20
            </IRQ>
    
    Fixes: 38b9f903f22b ("net/mlx5: Handle sync reset request event")
    Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 4a08a131351e375a2969b98e46df260ed04dcba7
Author: Gal Pressman <gal@nvidia.com>
Date:   Sun Jan 16 09:07:22 2022 +0200

    net/mlx5e: Fix module EEPROM query
    
    When querying the module EEPROM, there was a misusage of the 'offset'
    variable vs the 'query.offset' field.
    Fix that by always using 'offset' and assigning its value to
    'query.offset' right before the mcia register read call.
    
    While at it, the cross-pages read size adjustment was changed to be more
    intuitive.
    
    Fixes: e19b0a3474ab ("net/mlx5: Refactor module EEPROM query")
    Reported-by: Wang Yugui <wangyugui@e16-tech.com>
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Maxim Mikityanskiy <maximmi@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit a2446bc77a16cefd27de712d28af2396d6287593
Author: Roi Dayan <roid@nvidia.com>
Date:   Tue Jan 4 10:38:02 2022 +0200

    net/mlx5e: TC, Reject rules with drop and modify hdr action
    
    This kind of action is not supported by firmware and generates a
    syndrome.
    
    kernel: mlx5_core 0000:08:00.0: mlx5_cmd_check:777:(pid 102063): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x8708c3)
    
    Fixes: d7e75a325cb2 ("net/mlx5e: Add offloading of E-Switch TC pedit (header re-write) actions")
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Oz Shlomo <ozsh@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 350d9a823734b5a7e767cddc3bdde5f0bcbb7ff4
Author: Vlad Buslov <vladbu@nvidia.com>
Date:   Thu Jan 6 18:45:26 2022 +0200

    net/mlx5: Bridge, ensure dev_name is null-terminated
    
    Even though net_device->name is guaranteed to be null-terminated string of
    size<=IFNAMSIZ, the test robot complains that return value of netdev_name()
    can be larger:
    
    In file included from include/trace/define_trace.h:102,
                        from drivers/net/ethernet/mellanox/mlx5/core/esw/diag/bridge_tracepoint.h:113,
                        from drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c:12:
       drivers/net/ethernet/mellanox/mlx5/core/esw/diag/bridge_tracepoint.h: In function 'trace_event_raw_event_mlx5_esw_bridge_fdb_template':
    >> drivers/net/ethernet/mellanox/mlx5/core/esw/diag/bridge_tracepoint.h:24:29: warning: 'strncpy' output may be truncated copying 16 bytes from a string of length 20 [-Wstringop-truncation]
          24 |                             strncpy(__entry->dev_name,
             |                             ^~~~~~~~~~~~~~~~~~~~~~~~~~
          25 |                                     netdev_name(fdb->dev),
             |                                     ~~~~~~~~~~~~~~~~~~~~~~
          26 |                                     IFNAMSIZ);
             |                                     ~~~~~~~~~
    
    This is caused by the fact that default value of IFNAMSIZ is 16, while
    placeholder value that is returned by netdev_name() for unnamed net devices
    is larger than that.
    
    The offending code is in a tracing function that is only called for mlx5
    representors, so there is no straightforward way to reproduce the issue but
    let's fix it for correctness sake by replacing strncpy() with strscpy() to
    ensure that resulting string is always null-terminated.
    
    Fixes: 9724fd5d9c2a ("net/mlx5: Bridge, add tracepoints")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 04f8c12f031fcd0ffa0c72822eb665ceb2c872e7
Author: Vlad Buslov <vladbu@nvidia.com>
Date:   Thu Jan 6 16:40:18 2022 +0200

    net/mlx5: Bridge, take rtnl lock in init error handler
    
    The mlx5_esw_bridge_cleanup() is expected to be called with rtnl lock
    taken, which is true for mlx5e_rep_bridge_cleanup() function but not for
    error handling code in mlx5e_rep_bridge_init(). Add missing rtnl
    lock/unlock calls and extend both mlx5_esw_bridge_cleanup() and its dual
    function mlx5_esw_bridge_init() with ASSERT_RTNL() to verify the invariant
    from now on.
    
    Fixes: 7cd6a54a8285 ("net/mlx5: Bridge, handle FDB events")
    Fixes: 19e9bfa044f3 ("net/mlx5: Bridge, add offload infrastructure")
    Signed-off-by: Vlad Buslov <vladbu@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit c7108979a010f693d9f3b0adc7aa770b33d1b77d
Merge: d0cfa548dbde3 6533e558c6505
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Feb 1 20:39:46 2022 -0800

    Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-01-31
    
    This series contains updates to i40e driver only.
    
    Jedrzej fixes a condition check which would cause an error when
    resetting bandwidth when DCB is active with one TC.
    
    Karen resolves a null pointer dereference that could occur when removing
    the driver while VSI rings are being disabled.
    
    * '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue:
      i40e: Fix reset path while removing the driver
      i40e: Fix reset bw limit when DCB enabled with 1 TC
    ====================
    
    Link: https://lore.kernel.org/r/20220201000522.505909-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d0cfa548dbde354de986911d3913897b5448faad
Author: Lior Nahmanson <liorna@nvidia.com>
Date:   Sun Jan 30 13:37:52 2022 +0200

    net: macsec: Verify that send_sci is on when setting Tx sci explicitly
    
    When setting Tx sci explicit, the Rx side is expected to use this
    sci and not recalculate it from the packet.However, in case of Tx sci
    is explicit and send_sci is off, the receiver is wrongly recalculate
    the sci from the source MAC address which most likely be different
    than the explicit sci.
    
    Fix by preventing such configuration when macsec newlink is established
    and return EINVAL error code on such cases.
    
    Fixes: c09440f7dcb3 ("macsec: introduce IEEE 802.1AE driver")
    Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
    Reviewed-by: Raed Salem <raeds@nvidia.com>
    Signed-off-by: Raed Salem <raeds@nvidia.com>
    Link: https://lore.kernel.org/r/1643542672-29403-1-git-send-email-raeds@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 63e4b45c82ed1bde979da7052229a4229ce9cabf
Author: Georgi Valkov <gvalkov@abv.bg>
Date:   Tue Feb 1 08:16:18 2022 +0100

    ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
    
    When rx_buf is allocated we need to account for IPHETH_IP_ALIGN,
    which reduces the usable size by 2 bytes. Otherwise we have 1512
    bytes usable instead of 1514, and if we receive more than 1512
    bytes, ipheth_rcvbulk_callback is called with status -EOVERFLOW,
    after which the driver malfunctiones and all communication stops.
    
    Resolves ipheth 2-1:4.2: ipheth_rcvbulk_callback: urb status: -75
    
    Fixes: f33d9e2b48a3 ("usbnet: ipheth: fix connectivity with iOS 14")
    Signed-off-by: Georgi Valkov <gvalkov@abv.bg>
    Tested-by: Jan Kiszka <jan.kiszka@siemens.com>
    Link: https://lore.kernel.org/all/B60B8A4B-92A0-49B3-805D-809A2433B46C@abv.bg/
    Link: https://lore.kernel.org/all/24851bd2769434a5fc24730dce8e8a984c5a4505.1643699778.git.jan.kiszka@siemens.com/
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 479f5547239d970d3833f15f54a6481fffdb91ec
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Jan 31 22:52:54 2022 -0800

    tcp: fix mem under-charging with zerocopy sendmsg()
    
    We got reports of following warning in inet_sock_destruct()
    
            WARN_ON(sk_forward_alloc_get(sk));
    
    Whenever we add a non zero-copy fragment to a pure zerocopy skb,
    we have to anticipate that whole skb->truesize will be uncharged
    when skb is finally freed.
    
    skb->data_len is the payload length. But the memory truesize
    estimated by __zerocopy_sg_from_iter() is page aligned.
    
    Fixes: 9b65b17db723 ("net: avoid double accounting for pure zerocopy skbs")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Talal Ahmad <talalahmad@google.com>
    Cc: Arjun Roy <arjunroy@google.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Acked-by: Soheil Hassas Yeganeh <soheil@google.com>
    Link: https://lore.kernel.org/r/20220201065254.680532-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e42e70ad6ae2ae511a6143d2e8da929366e58bd9
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Jan 31 18:23:58 2022 -0800

    af_packet: fix data-race in packet_setsockopt / packet_setsockopt
    
    When packet_setsockopt( PACKET_FANOUT_DATA ) reads po->fanout,
    no lock is held, meaning that another thread can change po->fanout.
    
    Given that po->fanout can only be set once during the socket lifetime
    (it is only cleared from fanout_release()), we can use
    READ_ONCE()/WRITE_ONCE() to document the race.
    
    BUG: KCSAN: data-race in packet_setsockopt / packet_setsockopt
    
    write to 0xffff88813ae8e300 of 8 bytes by task 14653 on cpu 0:
     fanout_add net/packet/af_packet.c:1791 [inline]
     packet_setsockopt+0x22fe/0x24a0 net/packet/af_packet.c:3931
     __sys_setsockopt+0x209/0x2a0 net/socket.c:2180
     __do_sys_setsockopt net/socket.c:2191 [inline]
     __se_sys_setsockopt net/socket.c:2188 [inline]
     __x64_sys_setsockopt+0x62/0x70 net/socket.c:2188
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffff88813ae8e300 of 8 bytes by task 14654 on cpu 1:
     packet_setsockopt+0x691/0x24a0 net/packet/af_packet.c:3935
     __sys_setsockopt+0x209/0x2a0 net/socket.c:2180
     __do_sys_setsockopt net/socket.c:2191 [inline]
     __se_sys_setsockopt net/socket.c:2188 [inline]
     __x64_sys_setsockopt+0x62/0x70 net/socket.c:2188
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x0000000000000000 -> 0xffff888106f8c000
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 14654 Comm: syz-executor.3 Not tainted 5.16.0-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 47dceb8ecdc1 ("packet: add classic BPF fanout mode")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220201022358.330621-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c6f6f2444bdbe0079e41914a35081530d0409963
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Jan 31 17:21:06 2022 -0800

    rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
    
    While looking at one unrelated syzbot bug, I found the replay logic
    in __rtnl_newlink() to potentially trigger use-after-free.
    
    It is better to clear master_dev and m_ops inside the loop,
    in case we have to replay it.
    
    Fixes: ba7d49b1f0f8 ("rtnetlink: provide api for getting and setting slave info")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Jiri Pirko <jiri@nvidia.com>
    Link: https://lore.kernel.org/r/20220201012106.216495-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 04c2a47ffb13c29778e2a14e414ad4cb5a5db4b5
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Jan 31 09:20:18 2022 -0800

    net: sched: fix use-after-free in tc_new_tfilter()
    
    Whenever tc_new_tfilter() jumps back to replay: label,
    we need to make sure @q and @chain local variables are cleared again,
    or risk use-after-free as in [1]
    
    For consistency, apply the same fix in tc_ctl_chain()
    
    BUG: KASAN: use-after-free in mini_qdisc_pair_swap+0x1b9/0x1f0 net/sched/sch_generic.c:1581
    Write of size 8 at addr ffff8880985c4b08 by task syz-executor.4/1945
    
    CPU: 0 PID: 1945 Comm: syz-executor.4 Not tainted 5.17.0-rc1-syzkaller-00495-gff58831fa02d #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]
     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
     print_address_description.constprop.0.cold+0x8d/0x336 mm/kasan/report.c:255
     __kasan_report mm/kasan/report.c:442 [inline]
     kasan_report.cold+0x83/0xdf mm/kasan/report.c:459
     mini_qdisc_pair_swap+0x1b9/0x1f0 net/sched/sch_generic.c:1581
     tcf_chain_head_change_item net/sched/cls_api.c:372 [inline]
     tcf_chain0_head_change.isra.0+0xb9/0x120 net/sched/cls_api.c:386
     tcf_chain_tp_insert net/sched/cls_api.c:1657 [inline]
     tcf_chain_tp_insert_unique net/sched/cls_api.c:1707 [inline]
     tc_new_tfilter+0x1e67/0x2350 net/sched/cls_api.c:2086
     rtnetlink_rcv_msg+0x80d/0xb80 net/core/rtnetlink.c:5583
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x331/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmmsg+0x195/0x470 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x99/0x100 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7f2647172059
    Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
    RSP: 002b:00007f2645aa5168 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
    RAX: ffffffffffffffda RBX: 00007f2647285100 RCX: 00007f2647172059
    RDX: 040000000000009f RSI: 00000000200002c0 RDI: 0000000000000006
    RBP: 00007f26471cc08d R08: 0000000000000000 R09: 0000000000000000
    R10: 9e00000000000000 R11: 0000000000000246 R12: 0000000000000000
    R13: 00007fffb3f7f02f R14: 00007f2645aa5300 R15: 0000000000022000
     </TASK>
    
    Allocated by task 1944:
     kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38
     kasan_set_track mm/kasan/common.c:45 [inline]
     set_alloc_info mm/kasan/common.c:436 [inline]
     ____kasan_kmalloc mm/kasan/common.c:515 [inline]
     ____kasan_kmalloc mm/kasan/common.c:474 [inline]
     __kasan_kmalloc+0xa9/0xd0 mm/kasan/common.c:524
     kmalloc_node include/linux/slab.h:604 [inline]
     kzalloc_node include/linux/slab.h:726 [inline]
     qdisc_alloc+0xac/0xa10 net/sched/sch_generic.c:941
     qdisc_create.constprop.0+0xce/0x10f0 net/sched/sch_api.c:1211
     tc_modify_qdisc+0x4c5/0x1980 net/sched/sch_api.c:1660
     rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5592
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x331/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmmsg+0x195/0x470 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x99/0x100 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Freed by task 3609:
     kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38
     kasan_set_track+0x21/0x30 mm/kasan/common.c:45
     kasan_set_free_info+0x20/0x30 mm/kasan/generic.c:370
     ____kasan_slab_free mm/kasan/common.c:366 [inline]
     ____kasan_slab_free+0x130/0x160 mm/kasan/common.c:328
     kasan_slab_free include/linux/kasan.h:236 [inline]
     slab_free_hook mm/slub.c:1728 [inline]
     slab_free_freelist_hook+0x8b/0x1c0 mm/slub.c:1754
     slab_free mm/slub.c:3509 [inline]
     kfree+0xcb/0x280 mm/slub.c:4562
     rcu_do_batch kernel/rcu/tree.c:2527 [inline]
     rcu_core+0x7b8/0x1540 kernel/rcu/tree.c:2778
     __do_softirq+0x29b/0x9c2 kernel/softirq.c:558
    
    Last potentially related work creation:
     kasan_save_stack+0x1e/0x40 mm/kasan/common.c:38
     __kasan_record_aux_stack+0xbe/0xd0 mm/kasan/generic.c:348
     __call_rcu kernel/rcu/tree.c:3026 [inline]
     call_rcu+0xb1/0x740 kernel/rcu/tree.c:3106
     qdisc_put_unlocked+0x6f/0x90 net/sched/sch_generic.c:1109
     tcf_block_release+0x86/0x90 net/sched/cls_api.c:1238
     tc_new_tfilter+0xc0d/0x2350 net/sched/cls_api.c:2148
     rtnetlink_rcv_msg+0x80d/0xb80 net/core/rtnetlink.c:5583
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x331/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmmsg+0x195/0x470 net/socket.c:2553
     __do_sys_sendmmsg net/socket.c:2582 [inline]
     __se_sys_sendmmsg net/socket.c:2579 [inline]
     __x64_sys_sendmmsg+0x99/0x100 net/socket.c:2579
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    The buggy address belongs to the object at ffff8880985c4800
     which belongs to the cache kmalloc-1k of size 1024
    The buggy address is located 776 bytes inside of
     1024-byte region [ffff8880985c4800, ffff8880985c4c00)
    The buggy address belongs to the page:
    page:ffffea0002617000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x985c0
    head:ffffea0002617000 order:3 compound_mapcount:0 compound_pincount:0
    flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
    raw: 00fff00000010200 0000000000000000 dead000000000122 ffff888010c41dc0
    raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000
    page dumped because: kasan: bad access detected
    page_owner tracks the page as allocated
    page last allocated via order 3, migratetype Unmovable, gfp_mask 0x1d20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL), pid 1941, ts 1038999441284, free_ts 1033444432829
     prep_new_page mm/page_alloc.c:2434 [inline]
     get_page_from_freelist+0xa72/0x2f50 mm/page_alloc.c:4165
     __alloc_pages+0x1b2/0x500 mm/page_alloc.c:5389
     alloc_pages+0x1aa/0x310 mm/mempolicy.c:2271
     alloc_slab_page mm/slub.c:1799 [inline]
     allocate_slab mm/slub.c:1944 [inline]
     new_slab+0x28a/0x3b0 mm/slub.c:2004
     ___slab_alloc+0x87c/0xe90 mm/slub.c:3018
     __slab_alloc.constprop.0+0x4d/0xa0 mm/slub.c:3105
     slab_alloc_node mm/slub.c:3196 [inline]
     slab_alloc mm/slub.c:3238 [inline]
     __kmalloc+0x2fb/0x340 mm/slub.c:4420
     kmalloc include/linux/slab.h:586 [inline]
     kzalloc include/linux/slab.h:715 [inline]
     __register_sysctl_table+0x112/0x1090 fs/proc/proc_sysctl.c:1335
     neigh_sysctl_register+0x2c8/0x5e0 net/core/neighbour.c:3787
     devinet_sysctl_register+0xb1/0x230 net/ipv4/devinet.c:2618
     inetdev_init+0x286/0x580 net/ipv4/devinet.c:278
     inetdev_event+0xa8a/0x15d0 net/ipv4/devinet.c:1532
     notifier_call_chain+0xb5/0x200 kernel/notifier.c:84
     call_netdevice_notifiers_info+0xb5/0x130 net/core/dev.c:1919
     call_netdevice_notifiers_extack net/core/dev.c:1931 [inline]
     call_netdevice_notifiers net/core/dev.c:1945 [inline]
     register_netdevice+0x1073/0x1500 net/core/dev.c:9698
     veth_newlink+0x59c/0xa90 drivers/net/veth.c:1722
    page last free stack trace:
     reset_page_owner include/linux/page_owner.h:24 [inline]
     free_pages_prepare mm/page_alloc.c:1352 [inline]
     free_pcp_prepare+0x374/0x870 mm/page_alloc.c:1404
     free_unref_page_prepare mm/page_alloc.c:3325 [inline]
     free_unref_page+0x19/0x690 mm/page_alloc.c:3404
     release_pages+0x748/0x1220 mm/swap.c:956
     tlb_batch_pages_flush mm/mmu_gather.c:50 [inline]
     tlb_flush_mmu_free mm/mmu_gather.c:243 [inline]
     tlb_flush_mmu+0xe9/0x6b0 mm/mmu_gather.c:250
     zap_pte_range mm/memory.c:1441 [inline]
     zap_pmd_range mm/memory.c:1490 [inline]
     zap_pud_range mm/memory.c:1519 [inline]
     zap_p4d_range mm/memory.c:1540 [inline]
     unmap_page_range+0x1d1d/0x2a30 mm/memory.c:1561
     unmap_single_vma+0x198/0x310 mm/memory.c:1606
     unmap_vmas+0x16b/0x2f0 mm/memory.c:1638
     exit_mmap+0x201/0x670 mm/mmap.c:3178
     __mmput+0x122/0x4b0 kernel/fork.c:1114
     mmput+0x56/0x60 kernel/fork.c:1135
     exit_mm kernel/exit.c:507 [inline]
     do_exit+0xa3c/0x2a30 kernel/exit.c:793
     do_group_exit+0xd2/0x2f0 kernel/exit.c:935
     __do_sys_exit_group kernel/exit.c:946 [inline]
     __se_sys_exit_group kernel/exit.c:944 [inline]
     __x64_sys_exit_group+0x3a/0x50 kernel/exit.c:944
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Memory state around the buggy address:
     ffff8880985c4a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
     ffff8880985c4a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
    >ffff8880985c4b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                          ^
     ffff8880985c4b80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
     ffff8880985c4c00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
    
    Fixes: 470502de5bdb ("net: sched: unlock rules update API")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Vlad Buslov <vladbu@mellanox.com>
    Cc: Jiri Pirko <jiri@mellanox.com>
    Cc: Cong Wang <xiyou.wangcong@gmail.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220131172018.3704490-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6dde7acdb3dc2e0b3bcb090aac0b3699396d309f
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Mon Jan 31 13:17:30 2022 -0800

    ethernet: smc911x: fix indentation in get/set EEPROM
    
    Build bot produced a smatch indentation warning,
    the code looks correct but it mixes spaces and tabs.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Link: https://lore.kernel.org/r/20220131211730.3940875-1-kuba@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cea267c235e1b1ec3bfc415f6bd420289bcb3bc9
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Jan 31 13:20:10 2022 -0800

    xfs: ensure log flush at the end of a synchronous fallocate call
    
    Since we've started treating fallocate more like a file write, we
    should flush the log to disk if the user has asked for synchronous
    writes either by setting it via fcntl flags, or inode flags, or with
    the sync mount option.  We've already got a helper for this, so use
    it.
    
    [The original patch by Darrick was massaged by Dave to fit this patchset]
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>

commit b39a04636fd7454911b80e7b5ab2a66b011a8145
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Jan 31 13:20:10 2022 -0800

    xfs: move xfs_update_prealloc_flags() to xfs_pnfs.c
    
    The operations that xfs_update_prealloc_flags() perform are now
    unique to xfs_fs_map_blocks(), so move xfs_update_prealloc_flags()
    to be a static function in xfs_pnfs.c and cut out all the
    other functionality that is doesn't use anymore.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit 0b02c8c0d75a738c98c35f02efb36217c170d78c
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Jan 31 13:20:09 2022 -0800

    xfs: set prealloc flag in xfs_alloc_file_space()
    
    Now that we only call xfs_update_prealloc_flags() from
    xfs_file_fallocate() in the case where we need to set the
    preallocation flag, do this in xfs_alloc_file_space() where we
    already have the inode joined into a transaction and get
    rid of the call to xfs_update_prealloc_flags() from the fallocate
    code.
    
    This also means that we now correctly avoid setting the
    XFS_DIFLAG_PREALLOC flag when xfs_is_always_cow_inode() is true, as
    these inodes will never have preallocated extents.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit fbe7e520036583a783b13ff9744e35c2a329d9a4
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Jan 31 13:20:09 2022 -0800

    xfs: fallocate() should call file_modified()
    
    In XFS, we always update the inode change and modification time when
    any fallocate() operation succeeds.  Furthermore, as various
    fallocate modes can change the file contents (extending EOF,
    punching holes, zeroing things, shifting extents), we should drop
    file privileges like suid just like we do for a regular write().
    There's already a VFS helper that figures all this out for us, so
    use that.
    
    The net effect of this is that we no longer drop suid/sgid if the
    caller is root, but we also now drop file capabilities.
    
    We also move the xfs_update_prealloc_flags() function so that it now
    is only called by the scope that needs to set the the prealloc flag.
    
    Based on a patch from Darrick Wong.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit 472c6e46f589c26057596dcba160712a5b3e02c5
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Jan 31 13:20:08 2022 -0800

    xfs: remove XFS_PREALLOC_SYNC
    
    Callers can acheive the same thing by calling xfs_log_force_inode()
    after making their modifications. There is no need for
    xfs_update_prealloc_flags() to do this.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit b7892f7d5cb2b8187c603dd8ea3a7c44059ccfc2
Author: Jean-Philippe Brucker <jean-philippe@linaro.org>
Date:   Tue Feb 1 09:31:20 2022 +0000

    tools: Ignore errors from `which' when searching a GCC toolchain
    
    When cross-building tools with clang, we run `which $(CROSS_COMPILE)gcc`
    to detect whether a GCC toolchain provides the standard libraries. It is
    only a helper because some distros put libraries where LLVM does not
    automatically find them. On other systems, LLVM detects the libc
    automatically and does not need this. There, it is completely fine not
    to have a GCC at all, but some versions of `which' display an error when
    the command is not found:
    
      which: no aarch64-linux-gnu-gcc in ($PATH)
    
    Since the error can safely be ignored, throw it to /dev/null.
    
    Fixes: cebdb7374577 ("tools: Help cross-building with clang")
    Reported-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lore.kernel.org/bpf/20220201093119.1713207-1-jean-philippe@linaro.org

commit 9f7fb8de5d9bac17b6392a14af40baf555d9129b
Merge: 9e155101c24ad f83a96e5f033f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 12:39:37 2022 -0800

    Merge tag 'spi-fix-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
    
    Pull spi fixes from Mark Brown:
     "There are quite a few fixes that have accumilated since the merge
      window here, all driver specific and none super urgent, plus a new
      device ID for the Rockchip driver"
    
    * tag 'spi-fix-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi:
      spi: mediatek: Avoid NULL pointer crash in interrupt
      spi: dt-bindings: Fix 'reg' child node schema
      spi: bcm-qspi: check for valid cs before applying chip select
      spi: uniphier: fix reference count leak in uniphier_spi_probe()
      spi: meson-spicc: add IRQ check in meson_spicc_probe
      spi: uniphier: Fix a bug that doesn't point to private data correctly
      spi: change clk_disable_unprepare to clk_unprepare
      spi: spi-rockchip: Add rk3568-spi compatible
      spi: stm32: make SPI_MASTER_MUST_TX flags only specific to STM32F4
      spi: stm32: remove inexistant variables in struct stm32_spi_cfg comment
      spi: stm32-qspi: Update spi registering

commit 9e155101c24adb32b26475ca09bab93cf8fd80c6
Merge: 83c2713a67548 b4c18c18ebf7c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 12:37:20 2022 -0800

    Merge tag 'regulator-fix-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
    
    Pull regulator fixes from Mark Brown:
     "A couple of very minor fixes for the regulator framework, nothing at
      all urgent here"
    
    * tag 'regulator-fix-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:
      regulator: MAX20086: add gpio/consumer.h
      regulator: max20086: fix error code in max20086_parse_regulators_dt()

commit 83c2713a6754815c4f533097914a8d4fbe85dcf1
Merge: 24d7f48c72362 836f35f79153c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 12:12:10 2022 -0800

    Merge tag 'platform-drivers-x86-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
    
    Pull x86 platform driver fixes from Hans de Goede:
     "This consists of various build- and bug-fixes as well as a few
      hardware-id additions.
    
      Highlights:
       - Bunch of fixes for the new x86-android-tablets module
       - Misc other fixes
       - A couple of hw-id additions"
    
    * tag 'platform-drivers-x86-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:
      platform/x86: thinkpad_acpi: Fix incorrect use of platform profile on AMD platforms
      platform/x86: amd-pmc: Correct usage of SMU version
      platform/x86: asus-tf103c-dock: Make 2 global structs static
      platform/x86: amd-pmc: Make amd_pmc_stb_debugfs_fops static
      platform/x86: ISST: Fix possible circular locking dependency detected
      platform/x86: intel_crystal_cove_charger: Fix IRQ masking / unmasking
      platform/x86: thinkpad_acpi: Add quirk for ThinkPads without a fan
      platform/x86: touchscreen_dmi: Add info for the RWC NANOTE P8 AY07J 2-in-1
      platform/surface: Reinstate platform dependency
      platform/x86: x86-android-tablets: Trivial typo fix for MODULE_AUTHOR
      platform/x86: x86-android-tablets: Fix the buttons on CZC P10T tablet
      platform/x86: x86-android-tablets: Constify the gpiod_lookup_tables arrays
      platform/x86: x86-android-tablets: Add an init() callback to struct x86_dev_info
      platform/x86: x86-android-tablets: Add support for disabling ACPI _AEI handlers
      platform/x86: x86-android-tablets: Correct crystal_cove_charger module name

commit 24d7f48c72362bc7cdb8adf06cb303fe4a2c200d
Merge: 1a2beb3d5a0b4 94fd19752b28a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 11:23:02 2022 -0800

    Merge tag 'ovl-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs
    
    Pull overlayfs fixes from Miklos Szeredi:
     "Fix a regression introduced in v5.15, affecting copy up of files with
      'noatime' or 'sync' attributes to a tmpfs upper layer"
    
    * tag 'ovl-fixes-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs:
      ovl: don't fail copy up if no fileattr support on upper
      ovl: fix NULL pointer dereference in copy up warning

commit 1a2beb3d5a0b4051067ecf49ea799bee340e0e7c
Author: Christian Brauner <brauner@kernel.org>
Date:   Mon Jan 31 15:48:54 2022 +0100

    mailmap: update Christian Brauner's email address
    
    At least one of the addresses will stop functioning after February.
    
    Signed-off-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 630c12862c21a312c15a494922cdbf9c1beb1733
Merge: 61fda95541cd0 5298d4bfe80f6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 11:13:24 2022 -0800

    Merge tag 'unicode-for-next-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode
    
    Pull unicode cleanup from Gabriel Krisman Bertazi:
     "A fix from Christoph Hellwig merging the CONFIG_UNICODE_UTF8_DATA into
      the previous CONFIG_UNICODE. It is -rc material since we don't want to
      expose the former symbol on 5.17.
    
      This has been living on linux-next for the past week"
    
    * tag 'unicode-for-next-5.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode:
      unicode: clean up the Kconfig symbol confusion

commit 61fda95541cd0287540da45bb6dcbff2aeab1af9
Merge: 26291c54e111f f26d04331360d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Feb 1 11:07:09 2022 -0800

    Merge tag 'audit-pr-20220131' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit
    
    Pull audit fix from Paul Moore:
     "A single audit patch to fix problems relating to audit queuing and
      system responsiveness when "audit=1" is specified on the kernel
      command line and the audit daemon is SIGSTOP'd for an extended period
      of time"
    
    * tag 'audit-pr-20220131' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit:
      audit: improve audit queue handling when "audit=1" on cmdline

commit a4b92cebc31d49b7e6ef0ce584c7f2a2e112877d
Author: Mark Brown <broonie@kernel.org>
Date:   Tue Feb 1 14:48:38 2022 +0000

    arm64: Enable Cortex-A510 erratum 2051678 by default
    
    The recently added configuration option for Cortex A510 erratum 2051678 does
    not have a "default y" unlike other errata fixes. This appears to simply be
    an oversight since the help text suggests enabling the option if unsure and
    there's nothing in the commit log to suggest it is intentional.
    
    Fixes: 297ae1eb23b0 ("arm64: cpufeature: List early Cortex-A510 parts as having broken dbm")
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Link: https://lore.kernel.org/r/20220201144838.20037-1-broonie@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 8cfe148a7136bc60452a5c6b7ac2d9d15c36909b
Author: Mark Rutland <mark.rutland@arm.com>
Date:   Tue Feb 1 13:29:23 2022 +0000

    kvm/arm64: rework guest entry logic
    
    In kvm_arch_vcpu_ioctl_run() we enter an RCU extended quiescent state
    (EQS) by calling guest_enter_irqoff(), and unmasked IRQs prior to
    exiting the EQS by calling guest_exit(). As the IRQ entry code will not
    wake RCU in this case, we may run the core IRQ code and IRQ handler
    without RCU watching, leading to various potential problems.
    
    Additionally, we do not inform lockdep or tracing that interrupts will
    be enabled during guest execution, which caan lead to misleading traces
    and warnings that interrupts have been enabled for overly-long periods.
    
    This patch fixes these issues by using the new timing and context
    entry/exit helpers to ensure that interrupts are handled during guest
    vtime but with RCU watching, with a sequence:
    
            guest_timing_enter_irqoff();
    
            guest_state_enter_irqoff();
            < run the vcpu >
            guest_state_exit_irqoff();
    
            < take any pending IRQs >
    
            guest_timing_exit_irqoff();
    
    Since instrumentation may make use of RCU, we must also ensure that no
    instrumented code is run during the EQS. I've split out the critical
    section into a new kvm_arm_enter_exit_vcpu() helper which is marked
    noinstr.
    
    Fixes: 1b3d546daf85ed2b ("arm/arm64: KVM: Properly account for guest CPU time")
    Reported-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Reviewed-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Cc: Alexandru Elisei <alexandru.elisei@arm.com>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: James Morse <james.morse@arm.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Paul E. McKenney <paulmck@kernel.org>
    Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Message-Id: <20220201132926.3301912-3-mark.rutland@arm.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 24f6008564183aa120d07c03d9289519c2fe02af
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Thu Jan 20 11:04:01 2022 -0600

    cgroup-v1: Require capabilities to set release_agent
    
    The cgroup release_agent is called with call_usermodehelper.  The function
    call_usermodehelper starts the release_agent with a full set fo capabilities.
    Therefore require capabilities when setting the release_agaent.
    
    Reported-by: Tabitha Sable <tabitha.c.sable@gmail.com>
    Tested-by: Tabitha Sable <tabitha.c.sable@gmail.com>
    Fixes: 81a6a5cdd2c5 ("Task Control Groups: automatic userspace notification of idle cgroups")
    Cc: stable@vger.kernel.org # v2.6.24+
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 053ca37c87af65f41f5842070c68aa53c3d035f5
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 27 15:49:49 2022 -0600

    PCI: j721e: Initialize pcie->cdns_pcie before using it
    
    Christian reported a NULL pointer dereference in j721e_pcie_probe() caused
    by 19e863828acf ("PCI: j721e: Drop redundant struct device *"), which
    removed struct j721e_pcie.dev since there's another copy in struct
    cdns_pcie.dev reachable via j721e_pcie->cdns_pcie->dev.
    
    The problem is that j721e_pcie->cdns_pcie was dereferenced before being
    initialized:
    
      j721e_pcie_probe
        pcie = devm_kzalloc()             # struct j721e_pcie
        j721e_pcie_ctrl_init(pcie)
          dev = pcie->cdns_pcie->dev      <-- dereference cdns_pcie
        switch (mode) {
        case PCI_MODE_RC:
          cdns_pcie = ...                 # alloc as part of pci_host_bridge
          pcie->cdns_pcie = cdns_pcie     <-- initialize pcie->cdns_pcie
    
    Move the cdns_pcie initialization earlier so it is done before it is used.
    This also simplifies the error exits.
    
    Fixes: 19e863828acf ("PCI: j721e: Drop redundant struct device *")
    Link: https://lore.kernel.org/r/20220127222951.GA144828@bhelgaas
    Link: https://lore.kernel.org/r/20220124122132.435743-1-christian.gmeiner@gmail.com
    Reported-by: Christian Gmeiner <christian.gmeiner@gmail.com>
    Tested-by: Christian Gmeiner <christian.gmeiner@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit cad014b7b5a6897d8c4fad13e2888978bfb7a53f
Author: Sasha Neftin <sasha.neftin@intel.com>
Date:   Tue Dec 7 13:23:42 2021 +0200

    e1000e: Handshake with CSME starts from ADL platforms
    
    Handshake with CSME/AMT on none provisioned platforms during S0ix flow
    is not supported on TGL platform and can cause to HW unit hang. Update
    the handshake with CSME flow to start from the ADL platform.
    
    Fixes: 3e55d231716e ("e1000e: Add handshake with the CSME to support S0ix")
    Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Nechama Kraus <nechamax.kraus@linux.intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 68defd528f94ed1cf11f49a75cc1875dccd781fa
Author: Sasha Neftin <sasha.neftin@intel.com>
Date:   Tue Dec 7 13:23:06 2021 +0200

    e1000e: Separate ADP board type from TGP
    
    We have the same LAN controller on different PCH's. Separate ADP board
    type from a TGP which will allow for specific fixes to be applied for
    ADP platforms.
    
    Suggested-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Suggested-by: Dima Ruinskiy <dima.ruinskiy@intel.com>
    Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
    Tested-by: Nechama Kraus <nechamax.kraus@linux.intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 46f5cbdef7d4fbb0f857a3caddec6799d0b5bb2f
Author: David Howells <dhowells@redhat.com>
Date:   Mon Jan 31 17:54:43 2022 +0000

    cifs: Fix the readahead conversion to manage the batch when reading from cache
    
    Fix the readahead conversion to correctly manage the last batch skipping
    when reading from cache.  This involves a readahead batch of one page or
    one folio, so set the batch size according to the number of constituent
    pages (should be 1 for a filesystem that doesn't do multipage folios yet).
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    cc: Steve French <smfrench@gmail.com>
    Reviewed-by: Rohith Surabattula <rohiths.msft@gmail.com>
    Reviewed-by: Shyam Prasad N <nspmangalore@gmail.com>
    cc: Jeff Layton <jlayton@kernel.org>
    cc: linux-cifs@vger.kernel.org
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 0174ee9947bd0f24fee2794b35258960d108b7aa
Author: David Howells <dhowells@redhat.com>
Date:   Thu Jan 27 16:02:58 2022 +0000

    cifs: Implement cache I/O by accessing the cache directly
    
    Move cifs to using fscache DIO API instead of the old upstream I/O API as
    that has been removed.  This is a stopgap solution as the intention is that
    at sometime in the future, the cache will move to using larger blocks and
    won't be able to store individual pages in order to deal with the potential
    for data corruption due to the backing filesystem being able insert/remove
    bridging blocks of zeros into its extent list[1].
    
    cifs then reads and writes cache pages synchronously and one page at a time.
    
    The preferred change would be to use the netfs lib, but the new I/O API can
    be used directly.  It's just that as the cache now needs to track data for
    itself, caching blocks may exceed page size...
    
    This code is somewhat borrowed from my "fallback I/O" patchset[2].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    cc: Steve French <smfrench@gmail.com>
    cc: Shyam Prasad N <nspmangalore@gmail.com>
    cc: linux-cifs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/YO17ZNOcq+9PajfQ@mit.edu [1]
    Link: https://lore.kernel.org/r/202112100957.2oEDT20W-lkp@intel.com/ [2]
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit bee9f65523218e3baeeecde9295c8fbe9bc08e0a
Author: David Howells <dhowells@redhat.com>
Date:   Thu Jan 27 16:02:50 2022 +0000

    netfs, cachefiles: Add a method to query presence of data in the cache
    
    Add a netfs_cache_ops method by which a network filesystem can ask the
    cache about what data it has available and where so that it can make a
    multipage read more efficient.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    cc: linux-cachefs@redhat.com
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Rohith Surabattula <rohiths@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 052e04a52dcd3359ba1df25a508a3a93707a3f6e
Author: David Howells <dhowells@redhat.com>
Date:   Thu Jan 27 16:02:42 2022 +0000

    cifs: Transition from ->readpages() to ->readahead()
    
    Transition the cifs filesystem from using the old ->readpages() method to
    using the new ->readahead() method.
    
    For the moment, this removes any invocation of fscache to read data from
    the local cache, leaving that to another patch.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    cc: Steve French <smfrench@gmail.com>
    cc: Shyam Prasad N <nspmangalore@gmail.com>
    cc: Matthew Wilcox <willy@infradead.org>
    cc: Jeff Layton <jlayton@kernel.org>
    cc: linux-cifs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Reviewed-by: Rohith Surabattula <rohiths@microsoft.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit fc45e6588d57b65378612fce07089276141509dc
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Thu Feb 11 12:50:52 2021 -0300

    tools headers UAPI: Sync linux/prctl.h with the kernel sources
    
    To pick the changes in:
    
      9a10064f5625d557 ("mm: add a field to store names for private anonymous memory")
    
    That don't result in any changes in tooling:
    
      $ tools/perf/trace/beauty/prctl_option.sh > before
      $ cp include/uapi/linux/prctl.h tools/include/uapi/linux/prctl.h
      $ tools/perf/trace/beauty/prctl_option.sh > after
      $ diff -u before after
      $
    
    This actually adds a new prctl arg, but it has to be dealt with
    differently, as it is not in sequence with the other arguments.
    
    Just silences this perf tools build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from latest version at 'include/uapi/linux/prctl.h'
      diff -u tools/include/uapi/linux/prctl.h include/uapi/linux/prctl.h
    
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Colin Cross <ccross@google.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 100198322b2eb7fb38750cb0fcae5cd533907410
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Tue Feb 1 12:53:16 2022 -0300

    perf beauty: Make the prctl arg regexp more strict to cope with PR_SET_VMA
    
    This new PR_SET_VMA value isn't in sequence with all the other prctl
    arguments and instead uses a big, 0x prefixed hex number: 0x53564d41 (S V M A).
    
    This makes it harder to generate a string table as it would be rather
    sparse, so make the regexp more stricter to avoid catching those.
    
    A followup patch for 'perf trace' to cope with such oddities will be
    needed, but then its a matter for the next merge window.
    
    The next patch will update the prctl.h file to cope with this perf build
    warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from latest version at 'include/uapi/linux/prctl.h'
      diff -u tools/include/uapi/linux/prctl.h include/uapi/linux/prctl.h
    
    Here is the output of this script:
    
      $ tools/perf/trace/beauty/prctl_option.sh
      static const char *prctl_options[] = {
            [1] = "SET_PDEATHSIG",
            [2] = "GET_PDEATHSIG",
            [3] = "GET_DUMPABLE",
            [4] = "SET_DUMPABLE",
            [5] = "GET_UNALIGN",
            [6] = "SET_UNALIGN",
            [7] = "GET_KEEPCAPS",
            [8] = "SET_KEEPCAPS",
            [9] = "GET_FPEMU",
            [10] = "SET_FPEMU",
            [11] = "GET_FPEXC",
            [12] = "SET_FPEXC",
            [13] = "GET_TIMING",
            [14] = "SET_TIMING",
            [15] = "SET_NAME",
            [16] = "GET_NAME",
            [19] = "GET_ENDIAN",
            [20] = "SET_ENDIAN",
            [21] = "GET_SECCOMP",
            [22] = "SET_SECCOMP",
            [23] = "CAPBSET_READ",
            [24] = "CAPBSET_DROP",
            [25] = "GET_TSC",
            [26] = "SET_TSC",
            [27] = "GET_SECUREBITS",
            [28] = "SET_SECUREBITS",
            [29] = "SET_TIMERSLACK",
            [30] = "GET_TIMERSLACK",
            [31] = "TASK_PERF_EVENTS_DISABLE",
            [32] = "TASK_PERF_EVENTS_ENABLE",
            [33] = "MCE_KILL",
            [34] = "MCE_KILL_GET",
            [35] = "SET_MM",
            [36] = "SET_CHILD_SUBREAPER",
            [37] = "GET_CHILD_SUBREAPER",
            [38] = "SET_NO_NEW_PRIVS",
            [39] = "GET_NO_NEW_PRIVS",
            [40] = "GET_TID_ADDRESS",
            [41] = "SET_THP_DISABLE",
            [42] = "GET_THP_DISABLE",
            [43] = "MPX_ENABLE_MANAGEMENT",
            [44] = "MPX_DISABLE_MANAGEMENT",
            [45] = "SET_FP_MODE",
            [46] = "GET_FP_MODE",
            [47] = "CAP_AMBIENT",
            [50] = "SVE_SET_VL",
            [51] = "SVE_GET_VL",
            [52] = "GET_SPECULATION_CTRL",
            [53] = "SET_SPECULATION_CTRL",
            [54] = "PAC_RESET_KEYS",
            [55] = "SET_TAGGED_ADDR_CTRL",
            [56] = "GET_TAGGED_ADDR_CTRL",
            [57] = "SET_IO_FLUSHER",
            [58] = "GET_IO_FLUSHER",
            [59] = "SET_SYSCALL_USER_DISPATCH",
            [60] = "PAC_SET_ENABLED_KEYS",
            [61] = "PAC_GET_ENABLED_KEYS",
            [62] = "SCHED_CORE",
      };
      static const char *prctl_set_mm_options[] = {
            [1] = "START_CODE",
            [2] = "END_CODE",
            [3] = "START_DATA",
            [4] = "END_DATA",
            [5] = "START_STACK",
            [6] = "START_BRK",
            [7] = "BRK",
            [8] = "ARG_START",
            [9] = "ARG_END",
            [10] = "ENV_START",
            [11] = "ENV_END",
            [12] = "AUXV",
            [13] = "EXE_FILE",
            [14] = "MAP",
            [15] = "MAP_SIZE",
      };
      $
    
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Colin Cross <ccross@google.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Link: https://lore.kernel.org/lkml/YflZqY0rYQ3d1bKt@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 52517d9c0c011272950e1d88f1ced297daa001e9
Merge: 1c7f0e349aa5f a4f399a1416f6
Author: Takashi Iwai <tiwai@suse.de>
Date:   Tue Feb 1 16:52:54 2022 +0100

    Merge tag 'asoc-fix-v5.17-rc2' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus
    
    ASoC: Fixes for v5.17
    
    Quite a few fixes here, including an unusually large set in the core
    spurred on by various testing efforts as well as the usual small driver
    fixes.  There are quite a few fixes for out of bounds writes in both the
    core and the various Qualcomm drivers, plus a couple of fixes for
    locking in the DPCM code.

commit d5381cc9f123d64bee1d1a124cd98faa5fa36ca6
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Thu Jul 1 13:39:15 2021 -0300

    tools headers cpufeatures: Sync with the kernel sources
    
    To pick the changes from:
    
      690a757d610e50c2 ("kvm: x86: Add CPUID support for Intel AMX")
    
    This only causes these perf files to be rebuilt:
    
      CC       /tmp/build/perf/bench/mem-memcpy-x86-64-asm.o
      CC       /tmp/build/perf/bench/mem-memset-x86-64-asm.o
    
    And addresses this perf build warning:
    
      Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h'
      diff -u tools/arch/x86/include/asm/cpufeatures.h arch/x86/include/asm/cpufeatures.h
    
    Cc: Jing Liu <jing2.liu@intel.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Link: https://lore.kernel.org/lkml/YflQCEO9FRLeTmlB@kernel.org/
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 88443d3f79b8d2b5679f2a1df1482fa024be2353
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Fri May 21 16:00:31 2021 -0300

    tools headers UAPI: Sync linux/perf_event.h with the kernel sources
    
    To pick the trivial change in:
    
      cb1c4aba055f928f ("perf: Add new macros for mem_hops field")
    
    Just comment source code alignment.
    
    This silences this perf build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/linux/perf_event.h' differs from latest version at 'include/uapi/linux/perf_event.h'
      diff -u tools/include/uapi/linux/perf_event.h include/uapi/linux/perf_event.h
    
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/lkml/YflPKLhu2AtHmPov@kernel.org/
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit e9cc5d48d4f463fbea19dd93253e98af3b612b7c
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Feb 12 11:04:23 2020 -0300

    tools include UAPI: Sync sound/asound.h copy with the kernel sources
    
    Picking the changes from:
    
      55b71f6c29f2a78a ("ALSA: uapi: use C90 comment style instead of C99 style")
      fb6723daf89083a0 ("ALSA: pcm: comment about relation between msbits hw parameter and [S|U]32 formats")
      b456abe63f60ad93 ("ALSA: pcm: introduce INFO_NO_REWINDS flag")
      5aec579e08e4f2be ("ALSA: uapi: Fix a C++ style comment in asound.h")
    
    Which entails no changes in the tooling side as it doesn't introduce new
    SNDRV_PCM_IOCTL_ ioctls.
    
    To silence this perf tools build warning:
    
      Warning: Kernel ABI header at 'tools/include/uapi/sound/asound.h' differs from latest version at 'include/uapi/sound/asound.h'
      diff -u tools/include/uapi/sound/asound.h include/uapi/sound/asound.h
    
    Cc: Mark Brown <broonie@kernel.org>
    Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Cc: Takashi Iwai <tiwai@suse.de>
    Cc: Takashi Sakamoto <o-takashi@sakamocchi.jp>
    Link: https://lore.kernel.org/all/YflN0j09T+6ODHIh@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 836f35f79153ce09d813c83f341dba4481996966
Author: Mark Pearson <markpearson@lenovo.com>
Date:   Thu Jan 27 14:03:58 2022 -0500

    platform/x86: thinkpad_acpi: Fix incorrect use of platform profile on AMD platforms
    
    Lenovo AMD based platforms have been offering platform_profiles but they
    are not working correctly. This is because the mode we are using on the
    Intel platforms (MMC) is not available on the AMD platforms.
    
    This commit adds checking of the functional capabilities returned by the
    BIOS to confirm if MMC is supported or not. Profiles will not be
    available if the platform is not MMC capable.
    
    I'm investigating and working on an alternative for AMD platforms but
    that is still work-in-progress.
    
    Signed-off-by: Mark Pearson <markpearson@lenovo.com>
    Link: https://lore.kernel.org/r/20220127190358.4078-1-markpearson@lenovo.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 1c7f0e349aa5f8f80b1cac3d4917405332e14cdf
Author: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Date:   Tue Feb 1 13:21:44 2022 +0200

    ALSA: hda: Skip codec shutdown in case the codec is not registered
    
    If the codec->registered is not set then it means that pm_runtime is
    not yet enabled and the codec->pcm_list_head has not been initialized.
    
    The access to the not initialized pcm_list_head will lead a kernel crash
    during shutdown.
    
    Reported-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
    Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Tested-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
    Fixes: b98444ed597d ("ALSA: hda: Suspend codec at shutdown")
    Link: https://lore.kernel.org/r/20220201112144.29411-1-peter.ujfalusi@linux.intel.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit f3136c4ce7acf64bee43135971ca52a880572e32
Author: Leon Romanovsky <leon@kernel.org>
Date:   Mon Jan 31 11:45:26 2022 +0200

    RDMA/mlx4: Don't continue event handler after memory allocation failure
    
    The failure to allocate memory during MLX4_DEV_EVENT_PORT_MGMT_CHANGE
    event handler will cause skip the assignment logic, but
    ib_dispatch_event() will be called anyway.
    
    Fix it by calling to return instead of break after memory allocation
    failure.
    
    Fixes: 00f5ce99dc6e ("mlx4: Use port management change event instead of smp_snoop")
    Link: https://lore.kernel.org/r/12a0e83f18cfad4b5f62654f141e240d04915e10.1643622264.git.leonro@nvidia.com
    Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
    Reviewed-by: Håkon Bugge <haakon.bugge@oracle.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit b43a76f423aa304037603fd6165c4a534d2c09a7
Author: Bernard Metzler <bmt@zurich.ibm.com>
Date:   Sun Jan 30 18:08:15 2022 +0100

    RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
    
    Code unconditionally resumed fenced SQ processing after next RDMA Read
    completion, even if other RDMA Read responses are still outstanding, or
    ORQ is full. Also adds comments for better readability of fence
    processing, and removes orq_get_tail() helper, which is not needed
    anymore.
    
    Fixes: 8b6a361b8c48 ("rdma/siw: receive path")
    Fixes: a531975279f3 ("rdma/siw: main include file")
    Link: https://lore.kernel.org/r/20220130170815.1940-1-bmt@zurich.ibm.com
    Reported-by: Jared Holzman <jared.holzman@excelero.com>
    Signed-off-by: Bernard Metzler <bmt@zurich.ibm.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit b2d2af7e5df37ee3a9ba6b405bdbb7691a5c2dfc
Author: Mark Rutland <mark.rutland@arm.com>
Date:   Tue Feb 1 13:29:24 2022 +0000

    kvm/x86: rework guest entry logic
    
    For consistency and clarity, migrate x86 over to the generic helpers for
    guest timing and lockdep/RCU/tracing management, and remove the
    x86-specific helpers.
    
    Prior to this patch, the guest timing was entered in
    kvm_guest_enter_irqoff() (called by svm_vcpu_enter_exit() and
    svm_vcpu_enter_exit()), and was exited by the call to
    vtime_account_guest_exit() within vcpu_enter_guest().
    
    To minimize duplication and to more clearly balance entry and exit, both
    entry and exit of guest timing are placed in vcpu_enter_guest(), using
    the new guest_timing_{enter,exit}_irqoff() helpers. When context
    tracking is used a small amount of additional time will be accounted
    towards guests; tick-based accounting is unnaffected as IRQs are
    disabled at this point and not enabled until after the return from the
    guest.
    
    This also corrects (benign) mis-balanced context tracking accounting
    introduced in commits:
    
      ae95f566b3d22ade ("KVM: X86: TSCDEADLINE MSR emulation fastpath")
      26efe2fd92e50822 ("KVM: VMX: Handle preemption timer fastpath")
    
    Where KVM can enter a guest multiple times, calling vtime_guest_enter()
    without a corresponding call to vtime_account_guest_exit(), and with
    vtime_account_system() called when vtime_account_guest() should be used.
    As account_system_time() checks PF_VCPU and calls account_guest_time(),
    this doesn't result in any functional problem, but is unnecessarily
    confusing.
    
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Acked-by: Paolo Bonzini <pbonzini@redhat.com>
    Reviewed-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jim Mattson <jmattson@google.com>
    Cc: Joerg Roedel <joro@8bytes.org>
    Cc: Sean Christopherson <seanjc@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
    Cc: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <20220201132926.3301912-4-mark.rutland@arm.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 72e3244512b34756a7e8aa67eff45cdcb040ac4e
Author: Mark Rutland <mark.rutland@arm.com>
Date:   Tue Feb 1 13:29:26 2022 +0000

    kvm/mips: rework guest entry logic
    
    In kvm_arch_vcpu_ioctl_run() we use guest_enter_irqoff() and
    guest_exit_irqoff() directly, with interrupts masked between these. As
    we don't handle any timer ticks during this window, we will not account
    time spent within the guest as guest time, which is unfortunate.
    
    Additionally, we do not inform lockdep or tracing that interrupts will
    be enabled during guest execution, which caan lead to misleading traces
    and warnings that interrupts have been enabled for overly-long periods.
    
    This patch fixes these issues by using the new timing and context
    entry/exit helpers to ensure that interrupts are handled during guest
    vtime but with RCU watching, with a sequence:
    
            guest_timing_enter_irqoff();
    
            guest_state_enter_irqoff();
            < run the vcpu >
            guest_state_exit_irqoff();
    
            < take any pending IRQs >
    
            guest_timing_exit_irqoff();
    
    In addition, as guest exits during the "run the vcpu" step are handled
    by kvm_mips_handle_exit(), a wrapper function is added which ensures
    that such exists are handled with a sequence:
    
            guest_state_exit_irqoff();
            < handle the exit >
            guest_state_enter_irqoff();
    
    This means that exits which stop the vCPU running will have a redundant
    guest_state_enter_irqoff() .. guest_state_exit_irqoff() sequence, which
    can be addressed with future rework.
    
    Since instrumentation may make use of RCU, we must also ensure that no
    instrumented code is run during the EQS. I've split out the critical
    section into a new kvm_mips_enter_exit_vcpu() helper which is marked
    noinstr.
    
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Cc: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: Huacai Chen <chenhuacai@kernel.org>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Paul E. McKenney <paulmck@kernel.org>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Message-Id: <20220201132926.3301912-6-mark.rutland@arm.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ef9989afda73332df566852d6e9ca695c05f10ce
Author: Mark Rutland <mark.rutland@arm.com>
Date:   Tue Feb 1 13:29:22 2022 +0000

    kvm: add guest_state_{enter,exit}_irqoff()
    
    When transitioning to/from guest mode, it is necessary to inform
    lockdep, tracing, and RCU in a specific order, similar to the
    requirements for transitions to/from user mode. Additionally, it is
    necessary to perform vtime accounting for a window around running the
    guest, with RCU enabled, such that timer interrupts taken from the guest
    can be accounted as guest time.
    
    Most architectures don't handle all the necessary pieces, and a have a
    number of common bugs, including unsafe usage of RCU during the window
    between guest_enter() and guest_exit().
    
    On x86, this was dealt with across commits:
    
      87fa7f3e98a1310e ("x86/kvm: Move context tracking where it belongs")
      0642391e2139a2c1 ("x86/kvm/vmx: Add hardirq tracing to guest enter/exit")
      9fc975e9efd03e57 ("x86/kvm/svm: Add hardirq tracing on guest enter/exit")
      3ebccdf373c21d86 ("x86/kvm/vmx: Move guest enter/exit into .noinstr.text")
      135961e0a7d555fc ("x86/kvm/svm: Move guest enter/exit into .noinstr.text")
      160457140187c5fb ("KVM: x86: Defer vtime accounting 'til after IRQ handling")
      bc908e091b326467 ("KVM: x86: Consolidate guest enter/exit logic to common helpers")
    
    ... but those fixes are specific to x86, and as the resulting logic
    (while correct) is split across generic helper functions and
    x86-specific helper functions, it is difficult to see that the
    entry/exit accounting is balanced.
    
    This patch adds generic helpers which architectures can use to handle
    guest entry/exit consistently and correctly. The guest_{enter,exit}()
    helpers are split into guest_timing_{enter,exit}() to perform vtime
    accounting, and guest_context_{enter,exit}() to perform the necessary
    context tracking and RCU management. The existing guest_{enter,exit}()
    heleprs are left as wrappers of these.
    
    Atop this, new guest_state_enter_irqoff() and guest_state_exit_irqoff()
    helpers are added to handle the ordering of lockdep, tracing, and RCU
    manageent. These are inteneded to mirror exit_to_user_mode() and
    enter_from_user_mode().
    
    Subsequent patches will migrate architectures over to the new helpers,
    following a sequence:
    
            guest_timing_enter_irqoff();
    
            guest_state_enter_irqoff();
            < run the vcpu >
            guest_state_exit_irqoff();
    
            < take any pending IRQs >
    
            guest_timing_exit_irqoff();
    
    This sequences handles all of the above correctly, and more clearly
    balances the entry and exit portions, making it easier to understand.
    
    The existing helpers are marked as deprecated, and will be removed once
    all architectures have been converted.
    
    There should be no functional change as a result of this patch.
    
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Reviewed-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
    Reviewed-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
    Message-Id: <20220201132926.3301912-2-mark.rutland@arm.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2b56a9a28a6bf09890a43161402948ed62963f36
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Wed Jan 5 10:37:00 2022 +0800

    power: supply: core: fix application of sizeof to pointer
    
    The coccinelle check report:
    ./drivers/power/supply/cw2015_battery.c:692:12-18: ERROR: application of
    sizeof to pointer
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Fixes: 25fd330370ac ("power: supply_core: Pass pointer to battery info")
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

commit 881cc731df6af99a21622e9be25a23b81adcd10b
Author: Jonathan McDowell <noodles@earth.li>
Date:   Mon Jan 31 13:56:41 2022 +0000

    net: phy: Fix qca8081 with speeds lower than 2.5Gb/s
    
    A typo in qca808x_read_status means we try to set SMII mode on the port
    rather than SGMII when the link speed is not 2.5Gb/s. This results in no
    traffic due to the mismatch in configuration between the phy and the
    mac.
    
    v2:
     Only change interface mode when the link is up
    
    Fixes: 79c7bc0521545 ("net: phy: add qca8081 read_status")
    Cc: stable@vger.kernel.org
    Signed-off-by: Jonathan McDowell <noodles@earth.li>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ee12595147ac1fbfb5bcb23837e26dd58d94b15d
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 28 22:57:01 2022 +0300

    fanotify: Fix stale file descriptor in copy_event_to_user()
    
    This code calls fd_install() which gives the userspace access to the fd.
    Then if copy_info_records_to_user() fails it calls put_unused_fd(fd) but
    that will not release it and leads to a stale entry in the file
    descriptor table.
    
    Generally you can't trust the fd after a call to fd_install().  The fix
    is to delay the fd_install() until everything else has succeeded.
    
    Fortunately it requires CAP_SYS_ADMIN to reach this code so the security
    impact is less.
    
    Fixes: f644bc449b37 ("fanotify: fix copy_event_to_user() fid error clean up")
    Link: https://lore.kernel.org/r/20220128195656.GA26981@kili
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Mathias Krause <minipli@grsecurity.net>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit 57dfd7b53dec740afe402135fdd1c5708ec337f0
Author: Sean Christopherson <seanjc@google.com>
Date:   Fri Jan 28 00:51:48 2022 +0000

    KVM: x86: Move delivery of non-APICv interrupt into vendor code
    
    Handle non-APICv interrupt delivery in vendor code, even though it means
    VMX and SVM will temporarily have duplicate code.  SVM's AVIC has a race
    condition that requires KVM to fall back to legacy interrupt injection
    _after_ the interrupt has been logged in the vIRR, i.e. to fix the race,
    SVM will need to open code the full flow anyways[*].  Refactor the code
    so that the SVM bug without introducing other issues, e.g. SVM would
    return "success" and thus invoke trace_kvm_apicv_accept_irq() even when
    delivery through the AVIC failed, and to opportunistically prepare for
    using KVM_X86_OP to fill each vendor's kvm_x86_ops struct, which will
    rely on the vendor function matching the kvm_x86_op pointer name.
    
    No functional change intended.
    
    [*] https://lore.kernel.org/all/20211213104634.199141-4-mlevitsk@redhat.com
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220128005208.4008533-3-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6ca0c6283340d819bf9c7d8e76be33c9fbd903ab
Author: Johan Hovold <johan@kernel.org>
Date:   Tue Feb 1 11:42:53 2022 +0100

    USB: serial: cp210x: add CPI Bulk Coin Recycler id
    
    Add the device id for the Crane Payment Innovation / Money Controls Bulk
    Coin Recycler:
    
            https://www.cranepi.com/en/system/files/Support/OM_BCR_EN_V1-04_0.pdf
    
    Reported-by: Scott Russell <Scott.Russell2@ncr.com>
    Cc: stable@vger.kernel.org
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit b50f8f09c622297d3cf46e332e17ba8adedec9af
Author: Johan Hovold <johan@kernel.org>
Date:   Tue Feb 1 11:42:52 2022 +0100

    USB: serial: cp210x: add NCR Retail IO box id
    
    Add the device id for NCR's Retail IO box (CP2105) used in NCR FastLane
    SelfServ Checkout - R6C:
    
            https://www.ncr.com/product-catalog/ncr-fastlane-selfserv-checkout-r6c
    
    Reported-by: Scott Russell <Scott.Russell2@ncr.com>
    Cc: stable@vger.kernel.org
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit fbb9b194e15a63c56c5664e76ccd0e85c6100cea
Author: Cameron Williams <cang1@live.co.uk>
Date:   Tue Feb 1 10:12:51 2022 +0000

    USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
    
    This patch adds support for the Brainboxes US-159, US-235 and US-320
    USB-to-Serial devices.
    
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit da5462a4dc446e7028e6d150a4b02684d1d3ea81
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Mon Jan 17 18:15:22 2022 -0800

    power: supply: fix table problem in sysfs-class-power
    
    Add a bottom table border to complete the table format and prevent
    a documentation build warning.
    
    Documentation/ABI/testing/sysfs-class-power:459: WARNING: Malformed table.
    No bottom table border found.
    
    Fixes: 1b0b6cc8030d0 ("power: supply: add charge_behaviour attributes")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Thomas Weißschuh <linux@weissschuh.net>
    Cc: Hans de Goede <hdegoede@redhat.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: linux-pm@vger.kernel.org
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

commit 7d73c602154df56802a9e75ac212505fc1e9a2b6
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Date:   Mon Jan 24 18:01:24 2022 -0800

    drm/i915/pmu: Fix KMD and GuC race on accessing busyness
    
    GuC updates shared memory and KMD reads it. Since this is not
    synchronized, we run into a race where the value read is inconsistent.
    Sometimes the inconsistency is in reading the upper MSB bytes of the
    last_switch_in value. 2 types of cases are seen - upper 8 bits are zero
    and upper 24 bits are zero. Since these are non-zero values, it is
    not trivial to determine validity of these values. Instead we read the
    values multiple times until they are consistent. In test runs, 3
    attempts results in consistent values. The upper bound is set to 6
    attempts and may need to be tuned as per any new occurences.
    
    Since the duration that gt is parked can vary, the patch also updates
    the gt timestamp on unpark before starting the worker.
    
    v2:
    - Initialize i
    - Use READ_ONCE to access engine record
    
    Fixes: 77cdd054dd2c ("drm/i915/pmu: Connect engine busyness stats from GuC to pmu")
    Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
    Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
    Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220125020124.788679-2-umesh.nerlige.ramappa@intel.com
    (cherry picked from commit 512712a824de9b856a4e61343e3e4390eba2c391)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 92c4cfaee6872038563c5b6f2e8e613f9d84d47d
Author: Jordy Zomer <jordy@pwning.systems>
Date:   Sat Jan 29 16:06:04 2022 +0100

    dma-buf: heaps: Fix potential spectre v1 gadget
    
    It appears like nr could be a Spectre v1 gadget as it's supplied by a
    user and used as an array index. Prevent the contents
    of kernel memory from being leaked to userspace via speculative
    execution by using array_index_nospec.
    
    Signed-off-by: Jordy Zomer <jordy@pwning.systems>
    Fixes: c02a81fba74f ("dma-buf: Add dma-buf heaps framework")
    Cc: <stable@vger.kernel.org> # v5.6+
    Acked-by: John Stultz <john.stultz@linaro.org>
    Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
     [sumits: added fixes and cc: stable tags]
    Link: https://patchwork.freedesktop.org/patch/msgid/20220129150604.3461652-1-jordy@pwning.systems

commit 2161ba070999a709f975910b6b9ad6b51cd6f120
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sat Jan 29 12:58:19 2022 -0800

    MIPS: KVM: fix vz.c kernel-doc notation
    
    Fix all kernel-doc warnings in mips/kvm/vz.c as reported by the
    kernel test robot:
    
      arch/mips/kvm/vz.c:471: warning: Function parameter or member 'out_compare' not described in '_kvm_vz_save_htimer'
      arch/mips/kvm/vz.c:471: warning: Function parameter or member 'out_cause' not described in '_kvm_vz_save_htimer'
      arch/mips/kvm/vz.c:471: warning: Excess function parameter 'compare' description in '_kvm_vz_save_htimer'
      arch/mips/kvm/vz.c:471: warning: Excess function parameter 'cause' description in '_kvm_vz_save_htimer'
      arch/mips/kvm/vz.c:1551: warning: No description found for return value of 'kvm_trap_vz_handle_cop_unusable'
      arch/mips/kvm/vz.c:1552: warning: expecting prototype for kvm_trap_vz_handle_cop_unusuable(). Prototype was for kvm_trap_vz_handle_cop_unusable() instead
      arch/mips/kvm/vz.c:1597: warning: No description found for return value of 'kvm_trap_vz_handle_msa_disabled'
    
    Fixes: c992a4f6a9b0 ("KVM: MIPS: Implement VZ support")
    Fixes: f4474d50c7d4 ("KVM: MIPS/VZ: Support hardware guest timer")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: linux-mips@vger.kernel.org
    Cc: Huacai Chen <chenhuacai@kernel.org>
    Cc: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
    Cc: James Hogan <jhogan@kernel.org>
    Cc: kvm@vger.kernel.org
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 50317b636e7184d15126e2dfc83db0963a38d31e
Author: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date:   Mon Jan 31 11:07:02 2022 +0100

    MIPS: octeon: Fix missed PTR->PTR_WD conversion
    
    Fixes: fa62f39dc7e2 ("MIPS: Fix build error due to PTR used in more places")
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 4ee02e20893d2f9e951c7888f2284fa608ddaa35
Author: Jonas Hahnfeld <hahnjo@hahnjo.de>
Date:   Mon Jan 31 19:35:16 2022 +0100

    ALSA: usb-audio: Correct quirk for VF0770
    
    This device provides both audio and video. The original quirk added in
    commit 48827e1d6af5 ("ALSA: usb-audio: Add quirk for VF0770") used
    USB_DEVICE to match the vendor and product ID. Depending on module order,
    if snd-usb-audio was asked first, it would match the entire device and
    uvcvideo wouldn't get to see it. Change the matching to USB_AUDIO_DEVICE
    to restore uvcvideo matching in all cases.
    
    Fixes: 48827e1d6af5 ("ALSA: usb-audio: Add quirk for VF0770")
    Reported-by: Jukka Heikintalo <heikintalo.jukka@gmail.com>
    Tested-by: Jukka Heikintalo <heikintalo.jukka@gmail.com>
    Reported-by: Paweł Susicki <pawel.susicki@gmail.com>
    Tested-by: Paweł Susicki <pawel.susicki@gmail.com>
    Cc: <stable@vger.kernel.org> # 5.4, 5.10, 5.14, 5.15
    Signed-off-by: Jonas Hahnfeld <hahnjo@hahnjo.de>
    Link: https://lore.kernel.org/r/20220131183516.61191-1-hahnjo@hahnjo.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit ff4865b3c8cd746ef72f59bdd485848b4cebd43d
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Jan 26 20:48:49 2022 +0100

    ALSA: Replace acpi_bus_get_device()
    
    Replace acpi_bus_get_device() that is going to be dropped with
    acpi_fetch_acpi_dev().
    
    No intentional functional impact.
    
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Link: https://lore.kernel.org/r/2828205.e9J7NaK4W3@kreacher
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 9cef24c8b76c1f6effe499d2f131807c90f7ce9a
Author: Lior Nahmanson <liorna@nvidia.com>
Date:   Sun Jan 30 13:29:01 2022 +0200

    net: macsec: Fix offload support for NETDEV_UNREGISTER event
    
    Current macsec netdev notify handler handles NETDEV_UNREGISTER event by
    releasing relevant SW resources only, this causes resources leak in case
    of macsec HW offload, as the underlay driver was not notified to clean
    it's macsec offload resources.
    
    Fix by calling the underlay driver to clean it's relevant resources
    by moving offload handling from macsec_dellink() to macsec_common_dellink()
    when handling NETDEV_UNREGISTER event.
    
    Fixes: 3cf3227a21d1 ("net: macsec: hardware offloading infrastructure")
    Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
    Reviewed-by: Raed Salem <raeds@nvidia.com>
    Signed-off-by: Raed Salem <raeds@nvidia.com>
    Reviewed-by: Antoine Tenart <atenart@kernel.org>
    Link: https://lore.kernel.org/r/1643542141-28956-1-git-send-email-raeds@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7af037c39b600bac2c716dd1228e8ddbe149573f
Author: Camel Guo <camelg@axis.com>
Date:   Mon Jan 31 09:38:40 2022 +0100

    net: stmmac: dump gmac4 DMA registers correctly
    
    Unlike gmac100, gmac1000, gmac4 has 27 DMA registers and they are
    located at DMA_CHAN_BASE_ADDR (0x1100). In order for ethtool to dump
    gmac4 DMA registers correctly, this commit checks if a net_device has
    gmac4 and uses different logic to dump its DMA registers.
    
    This fixes the following KASAN warning, which can normally be triggered
    by a command similar like "ethtool -d eth0":
    
    BUG: KASAN: vmalloc-out-of-bounds in dwmac4_dump_dma_regs+0x6d4/0xb30
    Write of size 4 at addr ffffffc010177100 by task ethtool/1839
     kasan_report+0x200/0x21c
     __asan_report_store4_noabort+0x34/0x60
     dwmac4_dump_dma_regs+0x6d4/0xb30
     stmmac_ethtool_gregs+0x110/0x204
     ethtool_get_regs+0x200/0x4b0
     dev_ethtool+0x1dac/0x3800
     dev_ioctl+0x7c0/0xb50
     sock_ioctl+0x298/0x6c4
     ...
    
    Fixes: fbf68229ffe7 ("net: stmmac: unify registers dumps methods")
    Signed-off-by: Camel Guo <camelg@axis.com>
    Link: https://lore.kernel.org/r/20220131083841.3346801-1-camel.guo@axis.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4223f86512877b04c932e7203648b37eec931731
Author: Arınç ÜNAL <arinc.unal@arinc9.com>
Date:   Sat Jan 29 09:27:04 2022 +0300

    net: dsa: mt7530: make NET_DSA_MT7530 select MEDIATEK_GE_PHY
    
    Make MediaTek MT753x DSA driver enable MediaTek Gigabit PHYs driver to
    properly control MT7530 and MT7531 switch PHYs.
    
    A noticeable change is that the behaviour of switchport interfaces going
    up-down-up-down is no longer there.
    
    Fixes: b8f126a8d543 ("net-next: dsa: add dsa support for Mediatek MT7530 switch")
    Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220129062703.595-1-arinc.unal@arinc9.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7baa00bef336254e2cea5d4b064afe6430a05309
Author: Jonathan Marek <jonathan@marek.ca>
Date:   Sat Jan 22 11:29:32 2022 -0500

    arm64: dts: qcom: sm8450: fix apps_smmu interrupts
    
    Update interrupts in apps_smmu to match downstream. This is fixes apps_smmu
    failing to probe when running at EL2 (expects 96 context interrupts)
    
    Fixes: 892d5395396d ("arm64: dts: qcom: sm8450: add smmu nodes")
    Signed-off-by: Jonathan Marek <jonathan@marek.ca>
    Reviewed-by: Vinod Koul <vkoul@kernel.org>
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20220122162932.7686-2-jonathan@marek.ca

commit 197769fede5824d218f1f13f7620243015801d81
Author: Jonathan Marek <jonathan@marek.ca>
Date:   Sat Jan 22 11:29:31 2022 -0500

    arm64: dts: qcom: sm8450: enable GCC_USB3_0_CLKREF_EN for usb
    
    USB doesn't work at all without this clock enabled. This fixes USB when not
    using clk_ignore_unused.
    
    Fixes: 19fd04fb9247 ("arm64: dts: qcom: sm8450: Add usb nodes")
    Signed-off-by: Jonathan Marek <jonathan@marek.ca>
    Reviewed-by: Vinod Koul <vkoul@kernel.org>
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20220122162932.7686-1-jonathan@marek.ca

commit 0fd4dcb607ce29110d6c0b481a98c4ff3d300551
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date:   Wed Dec 22 08:20:58 2021 -0800

    arm64: dts: qcom: sm8350: Correct UFS symbol clocks
    
    The introduction of '9a61f813fcc8 ("clk: qcom: regmap-mux: fix parent
    clock lookup")' broke UFS support on SM8350.
    
    The cause for this is that the symbol clocks have a specified rate in
    the "freq-table-hz" table in the UFS node, which causes the UFS code to
    request a rate change, for which the "bi_tcxo" happens to provide the
    closest rate.  Prior to the change in regmap-mux it was determined
    (incorrectly) that no change was needed and everything worked.
    
    The rates of 75 and 300MHz matches the documentation for the symbol
    clocks, but we don't represent the parent clocks today. So let's mimic
    the configuration found in other platforms, by omitting the rate for the
    symbol clocks as well to avoid the rate change.
    
    While at it also fill in the dummy symbol clocks that was dropped from
    the GCC driver as it was upstreamed.
    
    Fixes: 59c7cf814783 ("arm64: dts: qcom: sm8350: Add UFS nodes")
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Reviewed-by: Vinod Koul <vkoul@kernel.org>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20211222162058.3418902-1-bjorn.andersson@linaro.org

commit a6ed2035878e5ad2e43ed175d8812ac9399d6c40
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Jan 11 14:00:26 2022 -0600

    drm/amd: Warn users about potential s0ix problems
    
    On some OEM setups users can configure the BIOS for S3 or S2idle.
    When configured to S3 users can still choose 's2idle' in the kernel by
    using `/sys/power/mem_sleep`.  Before commit 6dc8265f9803 ("drm/amdgpu:
    always reset the asic in suspend (v2)"), the GPU would crash.  Now when
    configured this way, the system should resume but will use more power.
    
    As such, adjust the `amdpu_acpi_is_s0ix function` to warn users about
    potential power consumption issues during their first attempt at
    suspending.
    
    Reported-by: Bjoren Dasse <bjoern.daase@gmail.com>
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1824
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 3ec5586b4699cfb75cdfa09425e11d121db40773
Author: Evan Quan <evan.quan@amd.com>
Date:   Mon Jan 24 13:40:35 2022 +0800

    drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
    
    The existing way cannot handle Beige Goby well as a different
    PPTable data structure(PPTable_beige_goby_t instead of PPTable_t)
    is used there.
    
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Cc: stable@vger.kernel.org

commit 6533e558c6505e94c3e0ed4281ed5e31ec985f4d
Author: Karen Sornek <karen.sornek@intel.com>
Date:   Wed Jan 12 10:19:47 2022 +0100

    i40e: Fix reset path while removing the driver
    
    Fix the crash in kernel while dereferencing the NULL pointer,
    when the driver is unloaded and simultaneously the VSI rings
    are being stopped.
    
    The hardware requires 50msec in order to finish RX queues
    disable. For this purpose the driver spins in mdelay function
    for the operation to be completed.
    
    For example changing number of queues which requires reset would
    fail in the following call stack:
    
    1) i40e_prep_for_reset
    2) i40e_pf_quiesce_all_vsi
    3) i40e_quiesce_vsi
    4) i40e_vsi_close
    5) i40e_down
    6) i40e_vsi_stop_rings
    7) i40e_vsi_control_rx -> disable requires the delay of 50msecs
    8) continue back in i40e_down function where
       i40e_clean_tx_ring(vsi->tx_rings[i]) is going to crash
    
    When the driver was spinning vsi_release called
    i40e_vsi_free_arrays where the vsi->tx_rings resources
    were freed and the pointer was set to NULL.
    
    Fixes: 5b6d4a7f20b0 ("i40e: Fix crash during removing i40e driver")
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
    Signed-off-by: Karen Sornek <karen.sornek@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit c763ec4c10f78678d6d4415646237f07109a5a5f
Author: John Garry <john.garry@huawei.com>
Date:   Mon Jan 31 19:13:27 2022 +0800

    scsi: hisi_sas: Fix setting of hisi_sas_slot.is_internal
    
    The hisi_sas_slot.is_internal member is not set properly for ATA commands
    which the driver sends directly. A TMF struct pointer is normally used as a
    test to set this, but it is NULL for those commands. It's not ideal, but
    pass an empty TMF struct to set that member properly.
    
    Link: https://lore.kernel.org/r/1643627607-138785-1-git-send-email-john.garry@huawei.com
    Fixes: dc313f6b125b ("scsi: hisi_sas: Factor out task prep and delivery code")
    Reported-by: Xiang Chen <chenxiang66@hisilicon.com>
    Signed-off-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 1b777d4d9e383d2744fc9b3a09af6ec1893c8b1a
Author: Nick Lopez <github@glowingmonkey.org>
Date:   Sat Jan 22 01:19:06 2022 -0700

    drm/nouveau: fix off by one in BIOS boundary checking
    
    Bounds checking when parsing init scripts embedded in the BIOS reject
    access to the last byte. This causes driver initialization to fail on
    Apple eMac's with GeForce 2 MX GPUs, leaving the system with no working
    console.
    
    This is probably only seen on OpenFirmware machines like PowerPC Macs
    because the BIOS image provided by OF is only the used parts of the ROM,
    not a power-of-two blocks read from PCI directly so PCs always have
    empty bytes at the end that are never accessed.
    
    Signed-off-by: Nick Lopez <github@glowingmonkey.org>
    Fixes: 4d4e9907ff572 ("drm/nouveau/bios: guard against out-of-bounds accesses to image")
    Cc: <stable@vger.kernel.org> # v4.10+
    Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
    Reviewed-by: Karol Herbst <kherbst@redhat.com>
    Signed-off-by: Karol Herbst <kherbst@redhat.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220122081906.2633061-1-github@glowingmonkey.org

commit df7abcaa1246e2537ab4016077b5443bb3c09378
Author: John Garry <john.garry@huawei.com>
Date:   Thu Jan 27 21:12:52 2022 +0800

    scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
    
    Currently a use-after-free may occur if a sas_task is aborted by the upper
    layer before we handle the I/O completion in mpi_ssp_completion() or
    mpi_sata_completion().
    
    In this case, the following are the two steps in handling those I/O
    completions:
    
     - Call complete() to inform the upper layer handler of completion of
       the I/O.
    
     - Release driver resources associated with the sas_task in
       pm8001_ccb_task_free() call.
    
    When complete() is called, the upper layer may free the sas_task. As such,
    we should not touch the associated sas_task afterwards, but we do so in the
    pm8001_ccb_task_free() call.
    
    Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.
    
    Link: https://lore.kernel.org/r/1643289172-165636-4-git-send-email-john.garry@huawei.com
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Acked-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 61f162aa4381845acbdc7f2be4dfb694d027c018
Author: John Garry <john.garry@huawei.com>
Date:   Thu Jan 27 21:12:51 2022 +0800

    scsi: pm8001: Fix use-after-free for aborted TMF sas_task
    
    Currently a use-after-free may occur if a TMF sas_task is aborted before we
    handle the IO completion in mpi_ssp_completion(). The abort occurs due to
    timeout.
    
    When the timeout occurs, the SAS_TASK_STATE_ABORTED flag is set and the
    sas_task is freed in pm8001_exec_internal_tmf_task().
    
    However, if the I/O completion occurs later, the I/O completion still
    thinks that the sas_task is available. Fix this by clearing the ccb->task
    if the TMF times out - the I/O completion handler does nothing if this
    pointer is cleared.
    
    Link: https://lore.kernel.org/r/1643289172-165636-3-git-send-email-john.garry@huawei.com
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Acked-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 0aed75fd30dacd31144188f7ddd5d571db7511c5
Author: John Garry <john.garry@huawei.com>
Date:   Thu Jan 27 21:12:50 2022 +0800

    scsi: pm8001: Fix warning for undescribed param in process_one_iomb()
    
    make W=1 complains of an undescribed function parameter:
    
    drivers/scsi/pm8001/pm80xx_hwi.c:3938: warning: Function parameter or member 'circularQ' not described in 'process_one_iomb'
    
    Fix it.
    
    Link: https://lore.kernel.org/r/1643289172-165636-2-git-send-email-john.garry@huawei.com
    Reported-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Acked-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 3d2504663c41104b4359a15f35670cfa82de1bbf
Author: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Date:   Tue Dec 14 10:08:22 2021 +0000

    i40e: Fix reset bw limit when DCB enabled with 1 TC
    
    There was an AQ error I40E_AQ_RC_EINVAL when trying
    to reset bw limit as part of bw allocation setup.
    This was caused by trying to reset bw limit with
    DCB enabled. Bw limit should not be reset when
    DCB is enabled. The code was relying on the pf->flags
    to check if DCB is enabled but if only 1 TC is available
    this flag will not be set even though DCB is enabled.
    Add a check for number of TC and if it is 1
    don't try to reset bw limit even if pf->flags shows
    DCB as disabled.
    
    Fixes: fa38e30ac73f ("i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled")
    Suggested-by: Alexander Lobakin <alexandr.lobakin@intel.com> # Flatten the condition
    Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
    Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
    Reviewed-by: Alexander Lobakin <alexandr.lobakin@intel.com>
    Tested-by: Imam Hassan Reza Biswas <imam.hassan.reza.biswas@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 29d650f7e3ab55283b89c9f5883d0c256ce478b5
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Mon Jan 24 15:48:31 2022 -0800

    xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP*
    
    Syzbot tripped over the following complaint from the kernel:
    
    WARNING: CPU: 2 PID: 15402 at mm/util.c:597 kvmalloc_node+0x11e/0x125 mm/util.c:597
    
    While trying to run XFS_IOC_GETBMAP against the following structure:
    
    struct getbmap fubar = {
            .bmv_count      = 0x22dae649,
    };
    
    Obviously, this is a crazy huge value since the next thing that the
    ioctl would do is allocate 37GB of memory.  This is enough to make
    kvmalloc mad, but isn't large enough to trip the validation functions.
    In other words, I'm fussing with checks that were **already sufficient**
    because that's easier than dealing with 644 internal bug reports.  Yes,
    that's right, six hundred and forty-four.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
    Reviewed-by: Catherine Hoang <catherine.hoang@oracle.com>

commit 04662bac0067e2fd7f243d6abaa4d779bce14114
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sun Jan 30 14:38:18 2022 -0800

    ACPI: require CRC32 to build
    
    ACPI core now requires crc32() but the kernel build can fail when
    CRC32 is not set/enabled, so select it in the ACPI Kconfig entry.
    
    Fixes this build error:
    
    ia64-linux-ld: drivers/acpi/scan.o: in function `acpi_store_pld_crc':
    include/acpi/platform/aclinuxex.h:62: undefined reference to `crc32_le'
    
    Fixes: 882c982dada4 ("acpi: Store CRC-32 hash of the _PLD in struct acpi_device")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Guenter Roeck <linux@roeck-us.net>
    Reviewed-by: Guenter Roeck <linux@roeck-us.net>
    Tested-by: Guenter Roeck <linux@roeck-us.net>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit edb854a3680bacc9ef9b91ec0c5ff6105886f6f3
Author: Ming Lei <ming.lei@redhat.com>
Date:   Thu Jan 27 23:37:33 2022 +0800

    scsi: core: Reallocate device's budget map on queue depth change
    
    We currently use ->cmd_per_lun as initial queue depth for setting up the
    budget_map. Martin Wilck reported that it is common for the queue_depth to
    be subsequently updated in slave_configure() based on detected hardware
    characteristics.
    
    As a result, for some drivers, the static host template settings for
    cmd_per_lun and can_queue won't actually get used in practice. And if the
    default values are used to allocate the budget_map, memory may be consumed
    unnecessarily.
    
    Fix the issue by reallocating the budget_map after ->slave_configure()
    returns. At that time the device queue_depth should accurately reflect what
    the hardware needs.
    
    Link: https://lore.kernel.org/r/20220127153733.409132-1-ming.lei@redhat.com
    Cc: Bart Van Assche <bvanassche@acm.org>
    Reported-by: Martin Wilck <martin.wilck@suse.com>
    Suggested-by: Martin Wilck <martin.wilck@suse.com>
    Tested-by: Martin Wilck <mwilck@suse.com>
    Reviewed-by: Martin Wilck <mwilck@suse.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Ming Lei <ming.lei@redhat.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit ec049891b2dc16591813eacaddc476b3d27c8c14
Author: Vincenzo Frascino <vincenzo.frascino@arm.com>
Date:   Mon Jan 31 11:34:05 2022 +0000

    kselftest: Fix vdso_test_abi return status
    
    vdso_test_abi contains a batch of tests that verify the validity of the
    vDSO ABI.
    
    When a vDSO symbol is not found the relevant test is skipped reporting
    KSFT_SKIP. All the tests return values are then added in a single
    variable which is checked to verify failures. This approach can have
    side effects which result in reporting the wrong kselftest exit status.
    
    Fix vdso_test_abi verifying the return code of each test separately.
    
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Reported-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 936bd03405fc83ba039d42bc93ffd4b88418f1d3
Author: John Meneghini <jmeneghi@redhat.com>
Date:   Mon Jan 24 09:51:10 2022 -0500

    scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
    
    Running tests with a debug kernel shows that bnx2fc_recv_frame() is
    modifying the per_cpu lport stats counters in a non-mpsafe way.  Just boot
    a debug kernel and run the bnx2fc driver with the hardware enabled.
    
    [ 1391.699147] BUG: using smp_processor_id() in preemptible [00000000] code: bnx2fc_
    [ 1391.699160] caller is bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc]
    [ 1391.699174] CPU: 2 PID: 4355 Comm: bnx2fc_l2_threa Kdump: loaded Tainted: G    B
    [ 1391.699180] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013
    [ 1391.699183] Call Trace:
    [ 1391.699188]  dump_stack_lvl+0x57/0x7d
    [ 1391.699198]  check_preemption_disabled+0xc8/0xd0
    [ 1391.699205]  bnx2fc_recv_frame+0xbf9/0x1760 [bnx2fc]
    [ 1391.699215]  ? do_raw_spin_trylock+0xb5/0x180
    [ 1391.699221]  ? bnx2fc_npiv_create_vports.isra.0+0x4e0/0x4e0 [bnx2fc]
    [ 1391.699229]  ? bnx2fc_l2_rcv_thread+0xb7/0x3a0 [bnx2fc]
    [ 1391.699240]  bnx2fc_l2_rcv_thread+0x1af/0x3a0 [bnx2fc]
    [ 1391.699250]  ? bnx2fc_ulp_init+0xc0/0xc0 [bnx2fc]
    [ 1391.699258]  kthread+0x364/0x420
    [ 1391.699263]  ? _raw_spin_unlock_irq+0x24/0x50
    [ 1391.699268]  ? set_kthread_struct+0x100/0x100
    [ 1391.699273]  ret_from_fork+0x22/0x30
    
    Restore the old get_cpu/put_cpu code with some modifications to reduce the
    size of the critical section.
    
    Link: https://lore.kernel.org/r/20220124145110.442335-1-jmeneghi@redhat.com
    Fixes: d576a5e80cd0 ("bnx2fc: Improve stats update mechanism")
    Tested-by: Guangwu Zhang <guazhang@redhat.com>
    Acked-by: Saurav Kashyap <skashyap@marvell.com>
    Signed-off-by: John Meneghini <jmeneghi@redhat.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit c26b85ea16365079be8d206b20556a60a0c69ad4
Author: Ajish Koshy <Ajish.Koshy@microchip.com>
Date:   Mon Jan 24 13:52:55 2022 +0530

    scsi: pm80xx: Fix double completion for SATA devices
    
    Current code handles completions for SATA devices in mpi_sata_completion()
    and mpi_sata_event().
    
    However, at the time when any SATA event happens, for almost all the event
    types, the command is still in the target. It is therefore incorrect to
    complete the task in sata_event().
    
    There are some events for which we get sata_completions, some need recovery
    procedure and others abort. All the tasks must be completed via
    sata_completion() path.
    
    Removed the task done related code from sata_events().  For tasks where we
    don't get completions, let top layer call abort() to abort the command post
    timeout.
    
    Link: https://lore.kernel.org/r/20220124082255.86223-1-Ajish.Koshy@microchip.com
    Acked-by: Jack Wang <jinpu.wang@ionos.com>
    Co-developed-by: Viswas G <Viswas.G@microchip.com>
    Signed-off-by: Viswas G <Viswas.G@microchip.com>
    Signed-off-by: Ajish Koshy <Ajish.Koshy@microchip.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 36415a7964711822e63695ea67fede63979054d9
Author: david regan <dregan@mail.com>
Date:   Wed Jan 26 23:43:44 2022 +0100

    mtd: rawnand: brcmnand: Fixed incorrect sub-page ECC status
    
    The brcmnand driver contains a bug in which if a page (example 2k byte)
    is read from the parallel/ONFI NAND and within that page a subpage (512
    byte) has correctable errors which is followed by a subpage with
    uncorrectable errors, the page read will return the wrong status of
    correctable (as opposed to the actual status of uncorrectable.)
    
    The bug is in function brcmnand_read_by_pio where there is a check for
    uncorrectable bits which will be preempted if a previous status for
    correctable bits is detected.
    
    The fix is to stop checking for bad bits only if we already have a bad
    bits status.
    
    Fixes: 27c5b17cd1b1 ("mtd: nand: add NAND driver "library" for Broadcom STB NAND controller")
    Signed-off-by: david regan <dregan@mail.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/trinity-478e0c09-9134-40e8-8f8c-31c371225eda-1643237024774@3c-app-mailcom-lxa02

commit fcda1cb81663b5fb846803607e1d0a3180d1a5d4
Author: Kalle Valo <kvalo@kernel.org>
Date:   Fri Jan 28 15:58:41 2022 +0200

    MAINTAINERS: add DT bindings files for ath10k and ath11k
    
    The DT bindings files were missing for ath10k and ath11k so add them now.
    
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220128135841.1926-4-kvalo@kernel.org

commit e2ac75e0619b8db32447bb592f4a5b9e9d990c57
Author: Kalle Valo <kvalo@kernel.org>
Date:   Fri Jan 28 15:58:40 2022 +0200

    MAINTAINERS: hand over ath9k maintainership to Toke
    
    In practise I have been the only maintainer for ath9k for some time now but I
    don't really have time for it. Luckily Toke is willing to look after so mark
    him as maintainer. Thanks Toke!
    
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220128135841.1926-3-kvalo@kernel.org

commit 3451613c338bfecb3e037f79db4bbfa51f7a0236
Author: Kalle Valo <kvalo@kernel.org>
Date:   Fri Jan 28 15:58:39 2022 +0200

    MAINTAINERS: change Loic as wcn36xx maintainer
    
    I don't have time for being wcn36xx maintainer but Loic is willing to step up.
    Thanks Loic!
    
    Also remove Eugene's old tree, it has not been used for a long time.
    
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Acked-by: Loic Poulain <loic.poulain@linaro.org>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220128135841.1926-2-kvalo@kernel.org

commit 533da5077b63485ba88f5bb03fd6a93048a9a72d
Author: Kalle Valo <kvalo@kernel.org>
Date:   Fri Jan 28 15:58:38 2022 +0200

    MAINTAINERS: mark ath6kl as orphan
    
    I don't have time to maintain ath6kl anymore so mark it as orphan.
    
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220128135841.1926-1-kvalo@kernel.org

commit 99e675d473eb8cf2deac1376a0f840222fc1adcf
Author: Guoqing Jiang <guoqing.jiang@linux.dev>
Date:   Fri Jan 28 11:10:02 2022 +0800

    iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
    
    After commit e3beca48a45b ("irqdomain/treewide: Keep firmware node
    unconditionally allocated"). For tear down scenario, fn is only freed
    after fail to allocate ir_domain, though it also should be freed in case
    dmar_enable_qi returns error.
    
    Besides free fn, irq_domain and ir_msi_domain need to be removed as well
    if intel_setup_irq_remapping fails to enable queued invalidation.
    
    Improve the rewinding path by add out_free_ir_domain and out_free_fwnode
    lables per Baolu's suggestion.
    
    Fixes: e3beca48a45b ("irqdomain/treewide: Keep firmware node unconditionally allocated")
    Suggested-by: Lu Baolu <baolu.lu@linux.intel.com>
    Signed-off-by: Guoqing Jiang <guoqing.jiang@linux.dev>
    Link: https://lore.kernel.org/r/20220119063640.16864-1-guoqing.jiang@linux.dev
    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Link: https://lore.kernel.org/r/20220128031002.2219155-3-baolu.lu@linux.intel.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit 30209b93177a75843673de92771716c941c20ef5
Author: John Garry <john.garry@huawei.com>
Date:   Fri Jan 28 18:44:33 2022 +0800

    iommu: Fix some W=1 warnings
    
    The code is mostly free of W=1 warning, so fix the following:
    
    drivers/iommu/iommu.c:996: warning: expecting prototype for iommu_group_for_each_dev(). Prototype was for __iommu_group_for_each_dev() instead
    drivers/iommu/iommu.c:3048: warning: Function parameter or member 'drvdata' not described in 'iommu_sva_bind_device'
    drivers/iommu/ioasid.c:354: warning: Function parameter or member 'ioasid' not described in 'ioasid_get'
    drivers/iommu/omap-iommu.c:1098: warning: expecting prototype for omap_iommu_suspend_prepare(). Prototype was for omap_iommu_prepare() instead
    
    Signed-off-by: John Garry <john.garry@huawei.com>
    Reviewed-by: Robin Murphy <robin.murphy@arm.com>
    Link: https://lore.kernel.org/r/1643366673-26803-1-git-send-email-john.garry@huawei.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit b54240ad494300ff0994c4539a531727874381f4
Author: Vijayanand Jitta <quic_vjitta@quicinc.com>
Date:   Mon Jan 31 12:42:35 2022 +0530

    iommu: Fix potential use-after-free during probe
    
    Kasan has reported the following use after free on dev->iommu.
    when a device probe fails and it is in process of freeing dev->iommu
    in dev_iommu_free function, a deferred_probe_work_func runs in parallel
    and tries to access dev->iommu->fwspec in of_iommu_configure path thus
    causing use after free.
    
    BUG: KASAN: use-after-free in of_iommu_configure+0xb4/0x4a4
    Read of size 8 at addr ffffff87a2f1acb8 by task kworker/u16:2/153
    
    Workqueue: events_unbound deferred_probe_work_func
    Call trace:
     dump_backtrace+0x0/0x33c
     show_stack+0x18/0x24
     dump_stack_lvl+0x16c/0x1e0
     print_address_description+0x84/0x39c
     __kasan_report+0x184/0x308
     kasan_report+0x50/0x78
     __asan_load8+0xc0/0xc4
     of_iommu_configure+0xb4/0x4a4
     of_dma_configure_id+0x2fc/0x4d4
     platform_dma_configure+0x40/0x5c
     really_probe+0x1b4/0xb74
     driver_probe_device+0x11c/0x228
     __device_attach_driver+0x14c/0x304
     bus_for_each_drv+0x124/0x1b0
     __device_attach+0x25c/0x334
     device_initial_probe+0x24/0x34
     bus_probe_device+0x78/0x134
     deferred_probe_work_func+0x130/0x1a8
     process_one_work+0x4c8/0x970
     worker_thread+0x5c8/0xaec
     kthread+0x1f8/0x220
     ret_from_fork+0x10/0x18
    
    Allocated by task 1:
     ____kasan_kmalloc+0xd4/0x114
     __kasan_kmalloc+0x10/0x1c
     kmem_cache_alloc_trace+0xe4/0x3d4
     __iommu_probe_device+0x90/0x394
     probe_iommu_group+0x70/0x9c
     bus_for_each_dev+0x11c/0x19c
     bus_iommu_probe+0xb8/0x7d4
     bus_set_iommu+0xcc/0x13c
     arm_smmu_bus_init+0x44/0x130 [arm_smmu]
     arm_smmu_device_probe+0xb88/0xc54 [arm_smmu]
     platform_drv_probe+0xe4/0x13c
     really_probe+0x2c8/0xb74
     driver_probe_device+0x11c/0x228
     device_driver_attach+0xf0/0x16c
     __driver_attach+0x80/0x320
     bus_for_each_dev+0x11c/0x19c
     driver_attach+0x38/0x48
     bus_add_driver+0x1dc/0x3a4
     driver_register+0x18c/0x244
     __platform_driver_register+0x88/0x9c
     init_module+0x64/0xff4 [arm_smmu]
     do_one_initcall+0x17c/0x2f0
     do_init_module+0xe8/0x378
     load_module+0x3f80/0x4a40
     __se_sys_finit_module+0x1a0/0x1e4
     __arm64_sys_finit_module+0x44/0x58
     el0_svc_common+0x100/0x264
     do_el0_svc+0x38/0xa4
     el0_svc+0x20/0x30
     el0_sync_handler+0x68/0xac
     el0_sync+0x160/0x180
    
    Freed by task 1:
     kasan_set_track+0x4c/0x84
     kasan_set_free_info+0x28/0x4c
     ____kasan_slab_free+0x120/0x15c
     __kasan_slab_free+0x18/0x28
     slab_free_freelist_hook+0x204/0x2fc
     kfree+0xfc/0x3a4
     __iommu_probe_device+0x284/0x394
     probe_iommu_group+0x70/0x9c
     bus_for_each_dev+0x11c/0x19c
     bus_iommu_probe+0xb8/0x7d4
     bus_set_iommu+0xcc/0x13c
     arm_smmu_bus_init+0x44/0x130 [arm_smmu]
     arm_smmu_device_probe+0xb88/0xc54 [arm_smmu]
     platform_drv_probe+0xe4/0x13c
     really_probe+0x2c8/0xb74
     driver_probe_device+0x11c/0x228
     device_driver_attach+0xf0/0x16c
     __driver_attach+0x80/0x320
     bus_for_each_dev+0x11c/0x19c
     driver_attach+0x38/0x48
     bus_add_driver+0x1dc/0x3a4
     driver_register+0x18c/0x244
     __platform_driver_register+0x88/0x9c
     init_module+0x64/0xff4 [arm_smmu]
     do_one_initcall+0x17c/0x2f0
     do_init_module+0xe8/0x378
     load_module+0x3f80/0x4a40
     __se_sys_finit_module+0x1a0/0x1e4
     __arm64_sys_finit_module+0x44/0x58
     el0_svc_common+0x100/0x264
     do_el0_svc+0x38/0xa4
     el0_svc+0x20/0x30
     el0_sync_handler+0x68/0xac
     el0_sync+0x160/0x180
    
    Fix this by setting dev->iommu to NULL first and
    then freeing dev_iommu structure in dev_iommu_free
    function.
    
    Suggested-by: Robin Murphy <robin.murphy@arm.com>
    Signed-off-by: Vijayanand Jitta <quic_vjitta@quicinc.com>
    Link: https://lore.kernel.org/r/1643613155-20215-1-git-send-email-quic_vjitta@quicinc.com
    Signed-off-by: Joerg Roedel <jroedel@suse.de>

commit f83a96e5f033fbbd21764705cb9c04234b96218e
Author: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Date:   Mon Jan 31 15:17:08 2022 +0100

    spi: mediatek: Avoid NULL pointer crash in interrupt
    
    In some case, like after a transfer timeout, master->cur_msg pointer
    is NULL which led to a kernel crash when trying to use master->cur_msg->spi.
    mtk_spi_can_dma(), pointed by master->can_dma, doesn't use this parameter
    avoid the problem by setting NULL as second parameter.
    
    Fixes: a568231f46322 ("spi: mediatek: Add spi bus for Mediatek MT8173")
    Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
    Link: https://lore.kernel.org/r/20220131141708.888710-1-benjamin.gaignard@collabora.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 40cdc509877bacb438213b83c7541c5e24a1d9ec
Author: Filipe Manana <fdmanana@suse.com>
Date:   Tue Jan 18 13:39:34 2022 +0000

    btrfs: skip reserved bytes warning on unmount after log cleanup failure
    
    After the recent changes made by commit c2e39305299f01 ("btrfs: clear
    extent buffer uptodate when we fail to write it") and its followup fix,
    commit 651740a5024117 ("btrfs: check WRITE_ERR when trying to read an
    extent buffer"), we can now end up not cleaning up space reservations of
    log tree extent buffers after a transaction abort happens, as well as not
    cleaning up still dirty extent buffers.
    
    This happens because if writeback for a log tree extent buffer failed,
    then we have cleared the bit EXTENT_BUFFER_UPTODATE from the extent buffer
    and we have also set the bit EXTENT_BUFFER_WRITE_ERR on it. Later on,
    when trying to free the log tree with free_log_tree(), which iterates
    over the tree, we can end up getting an -EIO error when trying to read
    a node or a leaf, since read_extent_buffer_pages() returns -EIO if an
    extent buffer does not have EXTENT_BUFFER_UPTODATE set and has the
    EXTENT_BUFFER_WRITE_ERR bit set. Getting that -EIO means that we return
    immediately as we can not iterate over the entire tree.
    
    In that case we never update the reserved space for an extent buffer in
    the respective block group and space_info object.
    
    When this happens we get the following traces when unmounting the fs:
    
    [174957.284509] BTRFS: error (device dm-0) in cleanup_transaction:1913: errno=-5 IO failure
    [174957.286497] BTRFS: error (device dm-0) in free_log_tree:3420: errno=-5 IO failure
    [174957.399379] ------------[ cut here ]------------
    [174957.402497] WARNING: CPU: 2 PID: 3206883 at fs/btrfs/block-group.c:127 btrfs_put_block_group+0x77/0xb0 [btrfs]
    [174957.407523] Modules linked in: btrfs overlay dm_zero (...)
    [174957.424917] CPU: 2 PID: 3206883 Comm: umount Tainted: G        W         5.16.0-rc5-btrfs-next-109 #1
    [174957.426689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
    [174957.428716] RIP: 0010:btrfs_put_block_group+0x77/0xb0 [btrfs]
    [174957.429717] Code: 21 48 8b bd (...)
    [174957.432867] RSP: 0018:ffffb70d41cffdd0 EFLAGS: 00010206
    [174957.433632] RAX: 0000000000000001 RBX: ffff8b09c3848000 RCX: ffff8b0758edd1c8
    [174957.434689] RDX: 0000000000000001 RSI: ffffffffc0b467e7 RDI: ffff8b0758edd000
    [174957.436068] RBP: ffff8b0758edd000 R08: 0000000000000000 R09: 0000000000000000
    [174957.437114] R10: 0000000000000246 R11: 0000000000000000 R12: ffff8b09c3848148
    [174957.438140] R13: ffff8b09c3848198 R14: ffff8b0758edd188 R15: dead000000000100
    [174957.439317] FS:  00007f328fb82800(0000) GS:ffff8b0a2d200000(0000) knlGS:0000000000000000
    [174957.440402] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [174957.441164] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0
    [174957.442117] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [174957.443076] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [174957.443948] Call Trace:
    [174957.444264]  <TASK>
    [174957.444538]  btrfs_free_block_groups+0x255/0x3c0 [btrfs]
    [174957.445238]  close_ctree+0x301/0x357 [btrfs]
    [174957.445803]  ? call_rcu+0x16c/0x290
    [174957.446250]  generic_shutdown_super+0x74/0x120
    [174957.446832]  kill_anon_super+0x14/0x30
    [174957.447305]  btrfs_kill_super+0x12/0x20 [btrfs]
    [174957.447890]  deactivate_locked_super+0x31/0xa0
    [174957.448440]  cleanup_mnt+0x147/0x1c0
    [174957.448888]  task_work_run+0x5c/0xa0
    [174957.449336]  exit_to_user_mode_prepare+0x1e5/0x1f0
    [174957.449934]  syscall_exit_to_user_mode+0x16/0x40
    [174957.450512]  do_syscall_64+0x48/0xc0
    [174957.450980]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [174957.451605] RIP: 0033:0x7f328fdc4a97
    [174957.452059] Code: 03 0c 00 f7 (...)
    [174957.454320] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
    [174957.455262] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97
    [174957.456131] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000560b8ae51dd0
    [174957.457118] RBP: 0000560b8ae51ba0 R08: 0000000000000000 R09: 00007fff13563c40
    [174957.458005] R10: 00007f328fe49fc0 R11: 0000000000000246 R12: 0000000000000000
    [174957.459113] R13: 0000560b8ae51dd0 R14: 0000560b8ae51cb0 R15: 0000000000000000
    [174957.460193]  </TASK>
    [174957.460534] irq event stamp: 0
    [174957.461003] hardirqs last  enabled at (0): [<0000000000000000>] 0x0
    [174957.461947] hardirqs last disabled at (0): [<ffffffffb0e94214>] copy_process+0x934/0x2040
    [174957.463147] softirqs last  enabled at (0): [<ffffffffb0e94214>] copy_process+0x934/0x2040
    [174957.465116] softirqs last disabled at (0): [<0000000000000000>] 0x0
    [174957.466323] ---[ end trace bc7ee0c490bce3af ]---
    [174957.467282] ------------[ cut here ]------------
    [174957.468184] WARNING: CPU: 2 PID: 3206883 at fs/btrfs/block-group.c:3976 btrfs_free_block_groups+0x330/0x3c0 [btrfs]
    [174957.470066] Modules linked in: btrfs overlay dm_zero (...)
    [174957.483137] CPU: 2 PID: 3206883 Comm: umount Tainted: G        W         5.16.0-rc5-btrfs-next-109 #1
    [174957.484691] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
    [174957.486853] RIP: 0010:btrfs_free_block_groups+0x330/0x3c0 [btrfs]
    [174957.488050] Code: 00 00 00 ad de (...)
    [174957.491479] RSP: 0018:ffffb70d41cffde0 EFLAGS: 00010206
    [174957.492520] RAX: ffff8b08d79310b0 RBX: ffff8b09c3848000 RCX: 0000000000000000
    [174957.493868] RDX: 0000000000000001 RSI: fffff443055ee600 RDI: ffffffffb1131846
    [174957.495183] RBP: ffff8b08d79310b0 R08: 0000000000000000 R09: 0000000000000000
    [174957.496580] R10: 0000000000000001 R11: 0000000000000000 R12: ffff8b08d7931000
    [174957.498027] R13: ffff8b09c38492b0 R14: dead000000000122 R15: dead000000000100
    [174957.499438] FS:  00007f328fb82800(0000) GS:ffff8b0a2d200000(0000) knlGS:0000000000000000
    [174957.500990] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [174957.502117] CR2: 00007fff13563e98 CR3: 0000000404f4e005 CR4: 0000000000370ee0
    [174957.503513] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [174957.504864] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [174957.506167] Call Trace:
    [174957.506654]  <TASK>
    [174957.507047]  close_ctree+0x301/0x357 [btrfs]
    [174957.507867]  ? call_rcu+0x16c/0x290
    [174957.508567]  generic_shutdown_super+0x74/0x120
    [174957.509447]  kill_anon_super+0x14/0x30
    [174957.510194]  btrfs_kill_super+0x12/0x20 [btrfs]
    [174957.511123]  deactivate_locked_super+0x31/0xa0
    [174957.511976]  cleanup_mnt+0x147/0x1c0
    [174957.512610]  task_work_run+0x5c/0xa0
    [174957.513309]  exit_to_user_mode_prepare+0x1e5/0x1f0
    [174957.514231]  syscall_exit_to_user_mode+0x16/0x40
    [174957.515069]  do_syscall_64+0x48/0xc0
    [174957.515718]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [174957.516688] RIP: 0033:0x7f328fdc4a97
    [174957.517413] Code: 03 0c 00 f7 d8 (...)
    [174957.521052] RSP: 002b:00007fff13564ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
    [174957.522514] RAX: 0000000000000000 RBX: 00007f328feea264 RCX: 00007f328fdc4a97
    [174957.523950] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000560b8ae51dd0
    [174957.525375] RBP: 0000560b8ae51ba0 R08: 0000000000000000 R09: 00007fff13563c40
    [174957.526763] R10: 00007f328fe49fc0 R11: 0000000000000246 R12: 0000000000000000
    [174957.528058] R13: 0000560b8ae51dd0 R14: 0000560b8ae51cb0 R15: 0000000000000000
    [174957.529404]  </TASK>
    [174957.529843] irq event stamp: 0
    [174957.530256] hardirqs last  enabled at (0): [<0000000000000000>] 0x0
    [174957.531061] hardirqs last disabled at (0): [<ffffffffb0e94214>] copy_process+0x934/0x2040
    [174957.532075] softirqs last  enabled at (0): [<ffffffffb0e94214>] copy_process+0x934/0x2040
    [174957.533083] softirqs last disabled at (0): [<0000000000000000>] 0x0
    [174957.533865] ---[ end trace bc7ee0c490bce3b0 ]---
    [174957.534452] BTRFS info (device dm-0): space_info 4 has 1070841856 free, is not full
    [174957.535404] BTRFS info (device dm-0): space_info total=1073741824, used=2785280, pinned=0, reserved=49152, may_use=0, readonly=65536 zone_unusable=0
    [174957.537029] BTRFS info (device dm-0): global_block_rsv: size 0 reserved 0
    [174957.537859] BTRFS info (device dm-0): trans_block_rsv: size 0 reserved 0
    [174957.538697] BTRFS info (device dm-0): chunk_block_rsv: size 0 reserved 0
    [174957.539552] BTRFS info (device dm-0): delayed_block_rsv: size 0 reserved 0
    [174957.540403] BTRFS info (device dm-0): delayed_refs_rsv: size 0 reserved 0
    
    This also means that in case we have log tree extent buffers that are
    still dirty, we can end up not cleaning them up in case we find an
    extent buffer with EXTENT_BUFFER_WRITE_ERR set on it, as in that case
    we have no way for iterating over the rest of the tree.
    
    This issue is very often triggered with test cases generic/475 and
    generic/648 from fstests.
    
    The issue could almost be fixed by iterating over the io tree attached to
    each log root which keeps tracks of the range of allocated extent buffers,
    log_root->dirty_log_pages, however that does not work and has some
    inconveniences:
    
    1) After we sync the log, we clear the range of the extent buffers from
       the io tree, so we can't find them after writeback. We could keep the
       ranges in the io tree, with a separate bit to signal they represent
       extent buffers already written, but that means we need to hold into
       more memory until the transaction commits.
    
       How much more memory is used depends a lot on whether we are able to
       allocate contiguous extent buffers on disk (and how often) for a log
       tree - if we are able to, then a single extent state record can
       represent multiple extent buffers, otherwise we need multiple extent
       state record structures to track each extent buffer.
       In fact, my earlier approach did that:
    
       https://lore.kernel.org/linux-btrfs/3aae7c6728257c7ce2279d6660ee2797e5e34bbd.1641300250.git.fdmanana@suse.com/
    
       However that can cause a very significant negative impact on
       performance, not only due to the extra memory usage but also because
       we get a larger and deeper dirty_log_pages io tree.
       We got a report that, on beefy machines at least, we can get such
       performance drop with fsmark for example:
    
       https://lore.kernel.org/linux-btrfs/20220117082426.GE32491@xsang-OptiPlex-9020/
    
    2) We would be doing it only to deal with an unexpected and exceptional
       case, which is basically failure to read an extent buffer from disk
       due to IO failures. On a healthy system we don't expect transaction
       aborts to happen after all;
    
    3) Instead of relying on iterating the log tree or tracking the ranges
       of extent buffers in the dirty_log_pages io tree, using the radix
       tree that tracks extent buffers (fs_info->buffer_radix) to find all
       log tree extent buffers is not reliable either, because after writeback
       of an extent buffer it can be evicted from memory by the release page
       callback of the btree inode (btree_releasepage()).
    
    Since there's no way to be able to properly cleanup a log tree without
    being able to read its extent buffers from disk and without using more
    memory to track the logical ranges of the allocated extent buffers do
    the following:
    
    1) When we fail to cleanup a log tree, setup a flag that indicates that
       failure;
    
    2) Trigger writeback of all log tree extent buffers that are still dirty,
       and wait for the writeback to complete. This is just to cleanup their
       state, page states, page leaks, etc;
    
    3) When unmounting the fs, ignore if the number of bytes reserved in a
       block group and in a space_info is not 0 if, and only if, we failed to
       cleanup a log tree. Also ignore only for metadata block groups and the
       metadata space_info object.
    
    This is far from a perfect solution, but it serves to silence test
    failures such as those from generic/475 and generic/648. However having
    a non-zero value for the reserved bytes counters on unmount after a
    transaction abort, is not such a terrible thing and it's completely
    harmless, it does not affect the filesystem integrity in any way.
    
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 37b4599547e324589e011c20f74b021d6d25cb7f
Author: Tom Rix <trix@redhat.com>
Date:   Fri Jan 21 05:45:22 2022 -0800

    btrfs: fix use of uninitialized variable at rm device ioctl
    
    Clang static analysis reports this problem
    ioctl.c:3333:8: warning: 3rd function call argument is an
      uninitialized value
        ret = exclop_start_or_cancel_reloc(fs_info,
    
    cancel is only set in one branch of an if-check and is always used.  So
    initialize to false.
    
    Fixes: 1a15eb724aae ("btrfs: use btrfs_get_dev_args_from_path in dev removal ioctls")
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: Anand Jain <anand.jain@oracle.com>
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 28b21c558a3753171097193b6f6602a94169093a
Author: Filipe Manana <fdmanana@suse.com>
Date:   Fri Jan 21 15:44:39 2022 +0000

    btrfs: fix use-after-free after failure to create a snapshot
    
    At ioctl.c:create_snapshot(), we allocate a pending snapshot structure and
    then attach it to the transaction's list of pending snapshots. After that
    we call btrfs_commit_transaction(), and if that returns an error we jump
    to 'fail' label, where we kfree() the pending snapshot structure. This can
    result in a later use-after-free of the pending snapshot:
    
    1) We allocated the pending snapshot and added it to the transaction's
       list of pending snapshots;
    
    2) We call btrfs_commit_transaction(), and it fails either at the first
       call to btrfs_run_delayed_refs() or btrfs_start_dirty_block_groups().
       In both cases, we don't abort the transaction and we release our
       transaction handle. We jump to the 'fail' label and free the pending
       snapshot structure. We return with the pending snapshot still in the
       transaction's list;
    
    3) Another task commits the transaction. This time there's no error at
       all, and then during the transaction commit it accesses a pointer
       to the pending snapshot structure that the snapshot creation task
       has already freed, resulting in a user-after-free.
    
    This issue could actually be detected by smatch, which produced the
    following warning:
    
      fs/btrfs/ioctl.c:843 create_snapshot() warn: '&pending_snapshot->list' not removed from list
    
    So fix this by not having the snapshot creation ioctl directly add the
    pending snapshot to the transaction's list. Instead add the pending
    snapshot to the transaction handle, and then at btrfs_commit_transaction()
    we add the snapshot to the list only when we can guarantee that any error
    returned after that point will result in a transaction abort, in which
    case the ioctl code can safely free the pending snapshot and no one can
    access it anymore.
    
    CC: stable@vger.kernel.org # 5.10+
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit ea1d1ca4025ac6c075709f549f9aa036b5b6597d
Author: Su Yue <l@damenly.su>
Date:   Fri Jan 21 17:33:35 2022 +0800

    btrfs: tree-checker: check item_size for dev_item
    
    Check item size before accessing the device item to avoid out of bound
    access, similar to inode_item check.
    
    Signed-off-by: Su Yue <l@damenly.su>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0c982944af27d131d3b74242f3528169f66950ad
Author: Su Yue <l@damenly.su>
Date:   Fri Jan 21 17:33:34 2022 +0800

    btrfs: tree-checker: check item_size for inode_item
    
    while mounting the crafted image, out-of-bounds access happens:
    
      [350.429619] UBSAN: array-index-out-of-bounds in fs/btrfs/struct-funcs.c:161:1
      [350.429636] index 1048096 is out of range for type 'page *[16]'
      [350.429650] CPU: 0 PID: 9 Comm: kworker/u8:1 Not tainted 5.16.0-rc4 #1
      [350.429652] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
      [350.429653] Workqueue: btrfs-endio-meta btrfs_work_helper [btrfs]
      [350.429772] Call Trace:
      [350.429774]  <TASK>
      [350.429776]  dump_stack_lvl+0x47/0x5c
      [350.429780]  ubsan_epilogue+0x5/0x50
      [350.429786]  __ubsan_handle_out_of_bounds+0x66/0x70
      [350.429791]  btrfs_get_16+0xfd/0x120 [btrfs]
      [350.429832]  check_leaf+0x754/0x1a40 [btrfs]
      [350.429874]  ? filemap_read+0x34a/0x390
      [350.429878]  ? load_balance+0x175/0xfc0
      [350.429881]  validate_extent_buffer+0x244/0x310 [btrfs]
      [350.429911]  btrfs_validate_metadata_buffer+0xf8/0x100 [btrfs]
      [350.429935]  end_bio_extent_readpage+0x3af/0x850 [btrfs]
      [350.429969]  ? newidle_balance+0x259/0x480
      [350.429972]  end_workqueue_fn+0x29/0x40 [btrfs]
      [350.429995]  btrfs_work_helper+0x71/0x330 [btrfs]
      [350.430030]  ? __schedule+0x2fb/0xa40
      [350.430033]  process_one_work+0x1f6/0x400
      [350.430035]  ? process_one_work+0x400/0x400
      [350.430036]  worker_thread+0x2d/0x3d0
      [350.430037]  ? process_one_work+0x400/0x400
      [350.430038]  kthread+0x165/0x190
      [350.430041]  ? set_kthread_struct+0x40/0x40
      [350.430043]  ret_from_fork+0x1f/0x30
      [350.430047]  </TASK>
      [350.430077] BTRFS warning (device loop0): bad eb member start: ptr 0xffe20f4e start 20975616 member offset 4293005178 size 2
    
    check_leaf() is checking the leaf:
    
      corrupt leaf: root=4 block=29396992 slot=1, bad key order, prev (16140901064495857664 1 0) current (1 204 12582912)
      leaf 29396992 items 6 free space 3565 generation 6 owner DEV_TREE
      leaf 29396992 flags 0x1(WRITTEN) backref revision 1
      fs uuid a62e00e8-e94e-4200-8217-12444de93c2e
      chunk uuid cecbd0f7-9ca0-441e-ae9f-f782f9732bd8
              item 0 key (16140901064495857664 INODE_ITEM 0) itemoff 3955 itemsize 40
                      generation 0 transid 0 size 0 nbytes 17592186044416
                      block group 0 mode 52667 links 33 uid 0 gid 2104132511 rdev 94223634821136
                      sequence 100305 flags 0x2409000(none)
                      atime 0.0 (1970-01-01 08:00:00)
                      ctime 2973280098083405823.4294967295 (-269783007-01-01 21:37:03)
                      mtime 18446744071572723616.4026825121 (1902-04-16 12:40:00)
                      otime 9249929404488876031.4294967295 (622322949-04-16 04:25:58)
              item 1 key (1 DEV_EXTENT 12582912) itemoff 3907 itemsize 48
                      dev extent chunk_tree 3
                      chunk_objectid 256 chunk_offset 12582912 length 8388608
                      chunk_tree_uuid cecbd0f7-9ca0-441e-ae9f-f782f9732bd8
    
    The corrupted leaf of device tree has an inode item. The leaf passed
    checksum and others checks in validate_extent_buffer until check_leaf_item().
    Because of the key type BTRFS_INODE_ITEM, check_inode_item() is called even we
    are in the device tree. Since the
    item offset + sizeof(struct btrfs_inode_item) > eb->len, out-of-bounds access
    is triggered.
    
    The item end vs leaf boundary check has been done before
    check_leaf_item(), so fix it by checking item size in check_inode_item()
    before access of the inode item in extent buffer.
    
    Other check functions except check_dev_item() in check_leaf_item()
    have their item size checks.
    The commit for check_dev_item() is followed.
    
    No regression observed during running fstests.
    
    Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215299
    CC: stable@vger.kernel.org # 5.10+
    CC: Wenqing Liu <wenqingliu0120@gmail.com>
    Signed-off-by: Su Yue <l@damenly.su>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit e804861bd4e69cc5fe1053eedcb024982dde8e48
Author: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Date:   Thu Jan 20 20:09:16 2022 +0900

    btrfs: fix deadlock between quota disable and qgroup rescan worker
    
    Quota disable ioctl starts a transaction before waiting for the qgroup
    rescan worker completes. However, this wait can be infinite and results
    in deadlock because of circular dependency among the quota disable
    ioctl, the qgroup rescan worker and the other task with transaction such
    as block group relocation task.
    
    The deadlock happens with the steps following:
    
    1) Task A calls ioctl to disable quota. It starts a transaction and
       waits for qgroup rescan worker completes.
    2) Task B such as block group relocation task starts a transaction and
       joins to the transaction that task A started. Then task B commits to
       the transaction. In this commit, task B waits for a commit by task A.
    3) Task C as the qgroup rescan worker starts its job and starts a
       transaction. In this transaction start, task C waits for completion
       of the transaction that task A started and task B committed.
    
    This deadlock was found with fstests test case btrfs/115 and a zoned
    null_blk device. The test case enables and disables quota, and the
    block group reclaim was triggered during the quota disable by chance.
    The deadlock was also observed by running quota enable and disable in
    parallel with 'btrfs balance' command on regular null_blk devices.
    
    An example report of the deadlock:
    
      [372.469894] INFO: task kworker/u16:6:103 blocked for more than 122 seconds.
      [372.479944]       Not tainted 5.16.0-rc8 #7
      [372.485067] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      [372.493898] task:kworker/u16:6   state:D stack:    0 pid:  103 ppid:     2 flags:0x00004000
      [372.503285] Workqueue: btrfs-qgroup-rescan btrfs_work_helper [btrfs]
      [372.510782] Call Trace:
      [372.514092]  <TASK>
      [372.521684]  __schedule+0xb56/0x4850
      [372.530104]  ? io_schedule_timeout+0x190/0x190
      [372.538842]  ? lockdep_hardirqs_on+0x7e/0x100
      [372.547092]  ? _raw_spin_unlock_irqrestore+0x3e/0x60
      [372.555591]  schedule+0xe0/0x270
      [372.561894]  btrfs_commit_transaction+0x18bb/0x2610 [btrfs]
      [372.570506]  ? btrfs_apply_pending_changes+0x50/0x50 [btrfs]
      [372.578875]  ? free_unref_page+0x3f2/0x650
      [372.585484]  ? finish_wait+0x270/0x270
      [372.591594]  ? release_extent_buffer+0x224/0x420 [btrfs]
      [372.599264]  btrfs_qgroup_rescan_worker+0xc13/0x10c0 [btrfs]
      [372.607157]  ? lock_release+0x3a9/0x6d0
      [372.613054]  ? btrfs_qgroup_account_extent+0xda0/0xda0 [btrfs]
      [372.620960]  ? do_raw_spin_lock+0x11e/0x250
      [372.627137]  ? rwlock_bug.part.0+0x90/0x90
      [372.633215]  ? lock_is_held_type+0xe4/0x140
      [372.639404]  btrfs_work_helper+0x1ae/0xa90 [btrfs]
      [372.646268]  process_one_work+0x7e9/0x1320
      [372.652321]  ? lock_release+0x6d0/0x6d0
      [372.658081]  ? pwq_dec_nr_in_flight+0x230/0x230
      [372.664513]  ? rwlock_bug.part.0+0x90/0x90
      [372.670529]  worker_thread+0x59e/0xf90
      [372.676172]  ? process_one_work+0x1320/0x1320
      [372.682440]  kthread+0x3b9/0x490
      [372.687550]  ? _raw_spin_unlock_irq+0x24/0x50
      [372.693811]  ? set_kthread_struct+0x100/0x100
      [372.700052]  ret_from_fork+0x22/0x30
      [372.705517]  </TASK>
      [372.709747] INFO: task btrfs-transacti:2347 blocked for more than 123 seconds.
      [372.729827]       Not tainted 5.16.0-rc8 #7
      [372.745907] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      [372.767106] task:btrfs-transacti state:D stack:    0 pid: 2347 ppid:     2 flags:0x00004000
      [372.787776] Call Trace:
      [372.801652]  <TASK>
      [372.812961]  __schedule+0xb56/0x4850
      [372.830011]  ? io_schedule_timeout+0x190/0x190
      [372.852547]  ? lockdep_hardirqs_on+0x7e/0x100
      [372.871761]  ? _raw_spin_unlock_irqrestore+0x3e/0x60
      [372.886792]  schedule+0xe0/0x270
      [372.901685]  wait_current_trans+0x22c/0x310 [btrfs]
      [372.919743]  ? btrfs_put_transaction+0x3d0/0x3d0 [btrfs]
      [372.938923]  ? finish_wait+0x270/0x270
      [372.959085]  ? join_transaction+0xc75/0xe30 [btrfs]
      [372.977706]  start_transaction+0x938/0x10a0 [btrfs]
      [372.997168]  transaction_kthread+0x19d/0x3c0 [btrfs]
      [373.013021]  ? btrfs_cleanup_transaction.isra.0+0xfc0/0xfc0 [btrfs]
      [373.031678]  kthread+0x3b9/0x490
      [373.047420]  ? _raw_spin_unlock_irq+0x24/0x50
      [373.064645]  ? set_kthread_struct+0x100/0x100
      [373.078571]  ret_from_fork+0x22/0x30
      [373.091197]  </TASK>
      [373.105611] INFO: task btrfs:3145 blocked for more than 123 seconds.
      [373.114147]       Not tainted 5.16.0-rc8 #7
      [373.120401] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      [373.130393] task:btrfs           state:D stack:    0 pid: 3145 ppid:  3141 flags:0x00004000
      [373.140998] Call Trace:
      [373.145501]  <TASK>
      [373.149654]  __schedule+0xb56/0x4850
      [373.155306]  ? io_schedule_timeout+0x190/0x190
      [373.161965]  ? lockdep_hardirqs_on+0x7e/0x100
      [373.168469]  ? _raw_spin_unlock_irqrestore+0x3e/0x60
      [373.175468]  schedule+0xe0/0x270
      [373.180814]  wait_for_commit+0x104/0x150 [btrfs]
      [373.187643]  ? test_and_set_bit+0x20/0x20 [btrfs]
      [373.194772]  ? kmem_cache_free+0x124/0x550
      [373.201191]  ? btrfs_put_transaction+0x69/0x3d0 [btrfs]
      [373.208738]  ? finish_wait+0x270/0x270
      [373.214704]  ? __btrfs_end_transaction+0x347/0x7b0 [btrfs]
      [373.222342]  btrfs_commit_transaction+0x44d/0x2610 [btrfs]
      [373.230233]  ? join_transaction+0x255/0xe30 [btrfs]
      [373.237334]  ? btrfs_record_root_in_trans+0x4d/0x170 [btrfs]
      [373.245251]  ? btrfs_apply_pending_changes+0x50/0x50 [btrfs]
      [373.253296]  relocate_block_group+0x105/0xc20 [btrfs]
      [373.260533]  ? mutex_lock_io_nested+0x1270/0x1270
      [373.267516]  ? btrfs_wait_nocow_writers+0x85/0x180 [btrfs]
      [373.275155]  ? merge_reloc_roots+0x710/0x710 [btrfs]
      [373.283602]  ? btrfs_wait_ordered_extents+0xd30/0xd30 [btrfs]
      [373.291934]  ? kmem_cache_free+0x124/0x550
      [373.298180]  btrfs_relocate_block_group+0x35c/0x930 [btrfs]
      [373.306047]  btrfs_relocate_chunk+0x85/0x210 [btrfs]
      [373.313229]  btrfs_balance+0x12f4/0x2d20 [btrfs]
      [373.320227]  ? lock_release+0x3a9/0x6d0
      [373.326206]  ? btrfs_relocate_chunk+0x210/0x210 [btrfs]
      [373.333591]  ? lock_is_held_type+0xe4/0x140
      [373.340031]  ? rcu_read_lock_sched_held+0x3f/0x70
      [373.346910]  btrfs_ioctl_balance+0x548/0x700 [btrfs]
      [373.354207]  btrfs_ioctl+0x7f2/0x71b0 [btrfs]
      [373.360774]  ? lockdep_hardirqs_on_prepare+0x410/0x410
      [373.367957]  ? lockdep_hardirqs_on_prepare+0x410/0x410
      [373.375327]  ? btrfs_ioctl_get_supported_features+0x20/0x20 [btrfs]
      [373.383841]  ? find_held_lock+0x2c/0x110
      [373.389993]  ? lock_release+0x3a9/0x6d0
      [373.395828]  ? mntput_no_expire+0xf7/0xad0
      [373.402083]  ? lock_is_held_type+0xe4/0x140
      [373.408249]  ? vfs_fileattr_set+0x9f0/0x9f0
      [373.414486]  ? selinux_file_ioctl+0x349/0x4e0
      [373.420938]  ? trace_raw_output_lock+0xb4/0xe0
      [373.427442]  ? selinux_inode_getsecctx+0x80/0x80
      [373.434224]  ? lockdep_hardirqs_on+0x7e/0x100
      [373.440660]  ? force_qs_rnp+0x2a0/0x6b0
      [373.446534]  ? lock_is_held_type+0x9b/0x140
      [373.452763]  ? __blkcg_punt_bio_submit+0x1b0/0x1b0
      [373.459732]  ? security_file_ioctl+0x50/0x90
      [373.466089]  __x64_sys_ioctl+0x127/0x190
      [373.472022]  do_syscall_64+0x3b/0x90
      [373.477513]  entry_SYSCALL_64_after_hwframe+0x44/0xae
      [373.484823] RIP: 0033:0x7f8f4af7e2bb
      [373.490493] RSP: 002b:00007ffcbf936178 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
      [373.500197] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f8f4af7e2bb
      [373.509451] RDX: 00007ffcbf936220 RSI: 00000000c4009420 RDI: 0000000000000003
      [373.518659] RBP: 00007ffcbf93774a R08: 0000000000000013 R09: 00007f8f4b02d4e0
      [373.527872] R10: 00007f8f4ae87740 R11: 0000000000000246 R12: 0000000000000001
      [373.537222] R13: 00007ffcbf936220 R14: 0000000000000000 R15: 0000000000000002
      [373.546506]  </TASK>
      [373.550878] INFO: task btrfs:3146 blocked for more than 123 seconds.
      [373.559383]       Not tainted 5.16.0-rc8 #7
      [373.565748] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      [373.575748] task:btrfs           state:D stack:    0 pid: 3146 ppid:  2168 flags:0x00000000
      [373.586314] Call Trace:
      [373.590846]  <TASK>
      [373.595121]  __schedule+0xb56/0x4850
      [373.600901]  ? __lock_acquire+0x23db/0x5030
      [373.607176]  ? io_schedule_timeout+0x190/0x190
      [373.613954]  schedule+0xe0/0x270
      [373.619157]  schedule_timeout+0x168/0x220
      [373.625170]  ? usleep_range_state+0x150/0x150
      [373.631653]  ? mark_held_locks+0x9e/0xe0
      [373.637767]  ? do_raw_spin_lock+0x11e/0x250
      [373.643993]  ? lockdep_hardirqs_on_prepare+0x17b/0x410
      [373.651267]  ? _raw_spin_unlock_irq+0x24/0x50
      [373.657677]  ? lockdep_hardirqs_on+0x7e/0x100
      [373.664103]  wait_for_completion+0x163/0x250
      [373.670437]  ? bit_wait_timeout+0x160/0x160
      [373.676585]  btrfs_quota_disable+0x176/0x9a0 [btrfs]
      [373.683979]  ? btrfs_quota_enable+0x12f0/0x12f0 [btrfs]
      [373.691340]  ? down_write+0xd0/0x130
      [373.696880]  ? down_write_killable+0x150/0x150
      [373.703352]  btrfs_ioctl+0x3945/0x71b0 [btrfs]
      [373.710061]  ? find_held_lock+0x2c/0x110
      [373.716192]  ? lock_release+0x3a9/0x6d0
      [373.722047]  ? __handle_mm_fault+0x23cd/0x3050
      [373.728486]  ? btrfs_ioctl_get_supported_features+0x20/0x20 [btrfs]
      [373.737032]  ? set_pte+0x6a/0x90
      [373.742271]  ? do_raw_spin_unlock+0x55/0x1f0
      [373.748506]  ? lock_is_held_type+0xe4/0x140
      [373.754792]  ? vfs_fileattr_set+0x9f0/0x9f0
      [373.761083]  ? selinux_file_ioctl+0x349/0x4e0
      [373.767521]  ? selinux_inode_getsecctx+0x80/0x80
      [373.774247]  ? __up_read+0x182/0x6e0
      [373.780026]  ? count_memcg_events.constprop.0+0x46/0x60
      [373.787281]  ? up_write+0x460/0x460
      [373.792932]  ? security_file_ioctl+0x50/0x90
      [373.799232]  __x64_sys_ioctl+0x127/0x190
      [373.805237]  do_syscall_64+0x3b/0x90
      [373.810947]  entry_SYSCALL_64_after_hwframe+0x44/0xae
      [373.818102] RIP: 0033:0x7f1383ea02bb
      [373.823847] RSP: 002b:00007fffeb4d71f8 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
      [373.833641] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1383ea02bb
      [373.842961] RDX: 00007fffeb4d7210 RSI: 00000000c0109428 RDI: 0000000000000003
      [373.852179] RBP: 0000000000000003 R08: 0000000000000003 R09: 0000000000000078
      [373.861408] R10: 00007f1383daec78 R11: 0000000000000202 R12: 00007fffeb4d874a
      [373.870647] R13: 0000000000493099 R14: 0000000000000001 R15: 0000000000000000
      [373.879838]  </TASK>
      [373.884018]
                   Showing all locks held in the system:
      [373.894250] 3 locks held by kworker/4:1/58:
      [373.900356] 1 lock held by khungtaskd/63:
      [373.906333]  #0: ffffffff8945ff60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260
      [373.917307] 3 locks held by kworker/u16:6/103:
      [373.923938]  #0: ffff888127b4f138 ((wq_completion)btrfs-qgroup-rescan){+.+.}-{0:0}, at: process_one_work+0x712/0x1320
      [373.936555]  #1: ffff88810b817dd8 ((work_completion)(&work->normal_work)){+.+.}-{0:0}, at: process_one_work+0x73f/0x1320
      [373.951109]  #2: ffff888102dd4650 (sb_internal#2){.+.+}-{0:0}, at: btrfs_qgroup_rescan_worker+0x1f6/0x10c0 [btrfs]
      [373.964027] 2 locks held by less/1803:
      [373.969982]  #0: ffff88813ed56098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80
      [373.981295]  #1: ffffc90000b3b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x9e2/0x1060
      [373.992969] 1 lock held by btrfs-transacti/2347:
      [373.999893]  #0: ffff88813d4887a8 (&fs_info->transaction_kthread_mutex){+.+.}-{3:3}, at: transaction_kthread+0xe3/0x3c0 [btrfs]
      [374.015872] 3 locks held by btrfs/3145:
      [374.022298]  #0: ffff888102dd4460 (sb_writers#18){.+.+}-{0:0}, at: btrfs_ioctl_balance+0xc3/0x700 [btrfs]
      [374.034456]  #1: ffff88813d48a0a0 (&fs_info->reclaim_bgs_lock){+.+.}-{3:3}, at: btrfs_balance+0xfe5/0x2d20 [btrfs]
      [374.047646]  #2: ffff88813d488838 (&fs_info->cleaner_mutex){+.+.}-{3:3}, at: btrfs_relocate_block_group+0x354/0x930 [btrfs]
      [374.063295] 4 locks held by btrfs/3146:
      [374.069647]  #0: ffff888102dd4460 (sb_writers#18){.+.+}-{0:0}, at: btrfs_ioctl+0x38b1/0x71b0 [btrfs]
      [374.081601]  #1: ffff88813d488bb8 (&fs_info->subvol_sem){+.+.}-{3:3}, at: btrfs_ioctl+0x38fd/0x71b0 [btrfs]
      [374.094283]  #2: ffff888102dd4650 (sb_internal#2){.+.+}-{0:0}, at: btrfs_quota_disable+0xc8/0x9a0 [btrfs]
      [374.106885]  #3: ffff88813d489800 (&fs_info->qgroup_ioctl_lock){+.+.}-{3:3}, at: btrfs_quota_disable+0xd5/0x9a0 [btrfs]
    
      [374.126780] =============================================
    
    To avoid the deadlock, wait for the qgroup rescan worker to complete
    before starting the transaction for the quota disable ioctl. Clear
    BTRFS_FS_QUOTA_ENABLE flag before the wait and the transaction to
    request the worker to complete. On transaction start failure, set the
    BTRFS_FS_QUOTA_ENABLE flag again. These BTRFS_FS_QUOTA_ENABLE flag
    changes can be done safely since the function btrfs_quota_disable is not
    called concurrently because of fs_info->subvol_sem.
    
    Also check the BTRFS_FS_QUOTA_ENABLE flag in qgroup_rescan_init to avoid
    another qgroup rescan worker to start after the previous qgroup worker
    completed.
    
    CC: stable@vger.kernel.org # 5.4+
    Suggested-by: Nikolay Borisov <nborisov@suse.com>
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 2d192fc4c1abeb0d04d1c8cd54405ff4a0b0255b
Author: Qu Wenruo <wqu@suse.com>
Date:   Thu Dec 16 19:47:35 2021 +0800

    btrfs: don't start transaction for scrub if the fs is mounted read-only
    
    [BUG]
    The following super simple script would crash btrfs at unmount time, if
    CONFIG_BTRFS_ASSERT() is set.
    
     mkfs.btrfs -f $dev
     mount $dev $mnt
     xfs_io -f -c "pwrite 0 4k" $mnt/file
     umount $mnt
     mount -r ro $dev $mnt
     btrfs scrub start -Br $mnt
     umount $mnt
    
    This will trigger the following ASSERT() introduced by commit
    0a31daa4b602 ("btrfs: add assertion for empty list of transactions at
    late stage of umount").
    
    That patch is definitely not the cause, it just makes enough noise for
    developers.
    
    [CAUSE]
    We will start transaction for the following call chain during scrub:
    
      scrub_enumerate_chunks()
      |- btrfs_inc_block_group_ro()
         |- btrfs_join_transaction()
    
    However for RO mount, there is no running transaction at all, thus
    btrfs_join_transaction() will start a new transaction.
    
    Furthermore, since it's read-only mount, btrfs_sync_fs() will not call
    btrfs_commit_super() to commit the new but empty transaction.
    
    And leads to the ASSERT().
    
    The bug has been there for a long time. Only the new ASSERT() makes it
    noisy enough to be noticed.
    
    [FIX]
    For read-only scrub on read-only mount, there is no need to start a
    transaction nor to allocate new chunks in btrfs_inc_block_group_ro().
    
    Just do extra read-only mount check in btrfs_inc_block_group_ro(), and
    if it's read-only, skip all chunk allocation and go inc_block_group_ro()
    directly.
    
    CC: stable@vger.kernel.org # 5.4+
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit bd2db32e7c3e35bd4d9b8bbff689434a50893546
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 27 08:16:38 2022 +0100

    moxart: fix potential use-after-free on remove path
    
    It was reported that the mmc host structure could be accessed after it
    was freed in moxart_remove(), so fix this by saving the base register of
    the device and using it instead of the pointer dereference.
    
    Cc: Ulf Hansson <ulf.hansson@linaro.org>
    Cc: Xiyu Yang <xiyuyang19@fudan.edu.cn>
    Cc: Xin Xiong <xiongx18@fudan.edu.cn>
    Cc: Xin Tan <tanxin.ctf@gmail.com>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Yang Li <yang.lee@linux.alibaba.com>
    Cc: linux-mmc@vger.kernel.org
    Cc: stable <stable@vger.kernel.org>
    Reported-by: whitehat002 <hackyzh002@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220127071638.4057899-1-gregkh@linuxfoundation.org
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit fa4300f060e5c4ca670b705f1e9b93685ad30c5b
Author: Frank Rowand <frank.rowand@sony.com>
Date:   Thu Jan 27 13:26:43 2022 -0600

    of: unittest: update text of expected warnings
    
    The text of various warning messages triggered by unittest has
    changed.  Update the text of expected warnings to match.
    
    The expected vs actual warnings are most easily seen by filtering
    the boot console messages with the of_unittest_expect program at
    https://github.com/frowand/dt_tools.git.  The filter prefixes
    problem lines with '***', and prefixes lines that match expected
    errors with 'ok '.  All other lines are prefixed with '   '.
    Unrelated lines have been deleted in the following examples.
    
    The mismatch appears as:
    
    -> ### dt-test ### start of unittest - you will see error messages
          OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
       ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found -1
          OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
       ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found -1
          OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found 1
       ** of_unittest_expect WARNING - not found ---> OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found -1
          platform testcase-data:testcase-device2: error -ENXIO: IRQ index 0 not found
       ** of_unittest_expect WARNING - not found ---> platform testcase-data:testcase-device2: IRQ index 0 not found
       -> ### dt-test ### end of unittest - 254 passed, 0 failed
       ** EXPECT statistics:
       **
       **   EXPECT found          :   42
       **   EXPECT not found      :    4
    
    With this commit applied, the mismatch is resolved:
    
       -> ### dt-test ### start of unittest - you will see error messages
       ok OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
       ok OF: /testcase-data/phandle-tests/consumer-a: #phandle-cells = 3 found 1
       ok OF: /testcase-data/phandle-tests/consumer-b: #phandle-cells = 2 found 1
       ok platform testcase-data:testcase-device2: error -ENXIO: IRQ index 0 not found
       -> ### dt-test ### end of unittest - 254 passed, 0 failed
       ** EXPECT statistics:
       **
       **   EXPECT found          :   46
       **   EXPECT not found      :    0
    
    Fixes: 2043727c2882 ("driver core: platform: Make use of the helper function dev_err_probe()")
    Fixes: 94a4950a4acf ("of: base: Fix phandle argument length mismatch error message")
    Signed-off-by: Frank Rowand <frank.rowand@sony.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220127192643.2534941-1-frowand.list@gmail.com

commit cacfddf82baf1470e5741edeecb187260868f195
Author: JaeMan Park <jaeman@google.com>
Date:   Thu Jan 13 15:02:35 2022 +0900

    mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work
    
    In mac80211_hwsim, the probe_req frame is created and sent while
    scanning. It is sent with ieee80211_tx_info which is not initialized.
    Uninitialized ieee80211_tx_info can cause problems when using
    mac80211_hwsim with wmediumd. wmediumd checks the tx_rates field of
    ieee80211_tx_info and doesn't relay probe_req frame to other clients
    even if it is a broadcasting message.
    
    Call ieee80211_tx_prepare_skb() to initialize ieee80211_tx_info for
    the probe_req that is created by hw_scan_work in mac80211_hwsim.
    
    Signed-off-by: JaeMan Park <jaeman@google.com>
    Link: https://lore.kernel.org/r/20220113060235.546107-1-jaeman@google.com
    [fix memory leak]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit 42a79960ffa50bfe9e0bf5d6280be89bf563a5dd
Author: Benjamin Beichler <benjamin.beichler@uni-rostock.de>
Date:   Tue Jan 11 22:13:26 2022 +0000

    mac80211_hwsim: report NOACK frames in tx_status
    
    Add IEEE80211_TX_STAT_NOACK_TRANSMITTED to tx_status flags to have proper
    statistics for non-acked frames.
    
    Signed-off-by: Benjamin Beichler <benjamin.beichler@uni-rostock.de>
    Link: https://lore.kernel.org/r/20220111221327.1499881-1-benjamin.beichler@uni-rostock.de
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit f6c6804c43fa18d3cee64b55490dfbd3bef1363a
Author: Janosch Frank <frankja@linux.ibm.com>
Date:   Fri Jan 28 15:40:25 2022 +0000

    kvm: Move KVM_GET_XSAVE2 IOCTL definition at the end of kvm.h
    
    This way we can more easily find the next free IOCTL number when
    adding new IOCTLs.
    
    Fixes: be50b2065dfa ("kvm: x86: Add support for getting/setting expanded xstate buffer")
    Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
    Message-Id: <20220128154025.102666-1-frankja@linux.ibm.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a72c01a94f1d285a274219d36e2a17b4846c0615
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Wed Jan 5 16:15:59 2022 +0800

    mac80211: mlme: check for null after calling kmemdup
    
    As the possible failure of the alloc, the ifmgd->assoc_req_ies might be
    NULL pointer returned from kmemdup().
    Therefore it might be better to free the skb and return error in order
    to fail the association, like ieee80211_assoc_success().
    Also, the caller, ieee80211_do_assoc(), needs to deal with the return
    value from ieee80211_send_assoc().
    
    Fixes: 4d9ec73d2b78 ("cfg80211: Report Association Request frame IEs in association events")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220105081559.2387083-1-jiasheng@iscas.ac.cn
    [fix some paths to be errors, not success]
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

commit c816b2e65b0e86b95011418cad334f0524fc33b8
Author: TATSUKAWA KOSUKE (立川 江介) <tatsu-ab1@nec.com>
Date:   Wed Jan 26 23:35:02 2022 +0000

    n_tty: wake up poll(POLLRDNORM) on receiving data
    
    The poll man page says POLLRDNORM is equivalent to POLLIN when used as
    an event.
    $ man poll
    <snip>
                  POLLRDNORM
                         Equivalent to POLLIN.
    
    However, in n_tty driver, POLLRDNORM does not return until timeout even
    if there is terminal input, whereas POLLIN returns.
    
    The following test program works until kernel-3.17, but the test stops
    in poll() after commit 57087d515441 ("tty: Fix spurious poll() wakeups").
    
    [Steps to run test program]
      $ cc -o test-pollrdnorm test-pollrdnorm.c
      $ ./test-pollrdnorm
      foo          <-- Type in something from the terminal followed by [RET].
                       The string should be echoed back.
    
      ------------------------< test-pollrdnorm.c >------------------------
      #include <stdio.h>
      #include <errno.h>
      #include <poll.h>
      #include <unistd.h>
    
      void main(void)
      {
            int             n;
            unsigned char   buf[8];
            struct pollfd   fds[1] = {{ 0, POLLRDNORM, 0 }};
    
            n = poll(fds, 1, -1);
            if (n < 0)
                    perror("poll");
            n = read(0, buf, 8);
            if (n < 0)
                    perror("read");
            if (n > 0)
                    write(1, buf, n);
      }
      ------------------------------------------------------------------------
    
    The attached patch fixes this problem.  Many calls to
    wake_up_interruptible_poll() in the kernel source code already specify
    "POLLIN | POLLRDNORM".
    
    Fixes: 57087d515441 ("tty: Fix spurious poll() wakeups")
    Cc: stable@vger.kernel.org
    Signed-off-by: Kosuke Tatsukawa <tatsu-ab1@nec.com>
    Link: https://lore.kernel.org/r/TYCPR01MB81901C0F932203D30E452B3EA5209@TYCPR01MB8190.jpnprd01.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5432184107cd0013761bdfa6cb6079527ef87b95
Author: Pavel Hofman <pavel.hofman@ivitera.com>
Date:   Mon Jan 31 08:18:13 2022 +0100

    usb: gadget: f_uac2: Define specific wTerminalType
    
    Several users have reported that their Win10 does not enumerate UAC2
    gadget with the existing wTerminalType set to
    UAC_INPUT_TERMINAL_UNDEFINED/UAC_INPUT_TERMINAL_UNDEFINED, e.g.
    https://github.com/raspberrypi/linux/issues/4587#issuecomment-926567213.
    While the constant is officially defined by the USB terminal types
    document, e.g. XMOS firmware for UAC2 (commonly used for Win10) defines
    no undefined output terminal type in its usbaudio20.h header.
    
    Therefore wTerminalType of EP-IN is set to
    UAC_INPUT_TERMINAL_MICROPHONE and wTerminalType of EP-OUT to
    UAC_OUTPUT_TERMINAL_SPEAKER for the UAC2 gadget.
    
    Signed-off-by: Pavel Hofman <pavel.hofman@ivitera.com>
    Cc: stable <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220131071813.7433-1-pavel.hofman@ivitera.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 459702eea6132888b5c5b64c0e9c626da4ec2493
Author: Adam Ford <aford173@gmail.com>
Date:   Fri Jan 28 16:36:03 2022 -0600

    usb: gadget: udc: renesas_usb3: Fix host to USB_ROLE_NONE transition
    
    The support the external role switch a variety of situations were
    addressed, but the transition from USB_ROLE_HOST to USB_ROLE_NONE
    leaves the host up which can cause some error messages when
    switching from host to none, to gadget, to none, and then back
    to host again.
    
     xhci-hcd ee000000.usb: Abort failed to stop command ring: -110
     xhci-hcd ee000000.usb: xHCI host controller not responding, assume dead
     xhci-hcd ee000000.usb: HC died; cleaning up
     usb 4-1: device not accepting address 6, error -108
     usb usb4-port1: couldn't allocate usb_device
    
    After this happens it will not act as a host again.
    Fix this by releasing the host mode when transitioning to USB_ROLE_NONE.
    
    Fixes: 0604160d8c0b ("usb: gadget: udc: renesas_usb3: Enhance role switch support")
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
    Signed-off-by: Adam Ford <aford173@gmail.com>
    Link: https://lore.kernel.org/r/20220128223603.2362621-1-aford173@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 292d2c82b105d92082c2120a44a58de9767e44f1
Author: Jann Horn <jannh@google.com>
Date:   Wed Jan 26 21:52:14 2022 +0100

    usb: raw-gadget: fix handling of dual-direction-capable endpoints
    
    Under dummy_hcd, every available endpoint is *either* IN or OUT capable.
    But with some real hardware, there are endpoints that support both IN and
    OUT. In particular, the PLX 2380 has four available endpoints that each
    support both IN and OUT.
    
    raw-gadget currently gets confused and thinks that any endpoint that is
    usable as an IN endpoint can never be used as an OUT endpoint.
    
    Fix it by looking at the direction in the configured endpoint descriptor
    instead of looking at the hardware capabilities.
    
    With this change, I can use the PLX 2380 with raw-gadget.
    
    Fixes: f2c2e717642c ("usb: gadget: add raw-gadget interface")
    Cc: stable <stable@vger.kernel.org>
    Tested-by: Andrey Konovalov <andreyknvl@gmail.com>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Signed-off-by: Jann Horn <jannh@google.com>
    Link: https://lore.kernel.org/r/20220126205214.2149936-1-jannh@google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5c2b9c61ae5d8ad0a196d33b66ce44543be22281
Author: Tommaso Merciai <tomm.merciai@gmail.com>
Date:   Fri Jan 28 19:17:13 2022 +0100

    usb: usb251xb: add boost-up property support
    
    Add support for boost-up register of usb251xb hub.
    boost-up property control USB electrical drive strength
    This register can be set:
    
     - Normal mode -> 0x00
     - Low         -> 0x01
     - Medium      -> 0x10
     - High        -> 0x11
    
    (Normal Default)
    
    References:
     - http://www.mouser.com/catalog/specsheets/2514.pdf p29
    
    Reviewed-by: Richard Leitner <richard.leitner@linux.dev>
    Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
    Link: https://lore.kernel.org/r/20220128181713.96856-1-tomm.merciai@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit a4f399a1416f645ac701064a55b0cb5203707ac9
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 30 09:06:36 2022 +0100

    Input: wm97xx: Simplify resource management
    
    Since the commit in the Fixes tag below, 'wm->input_dev' is a managed
    resource that doesn't need to be explicitly unregistered or freed (see
    devm_input_allocate_device() documentation)
    
    So, remove some unless line of code to slightly simplify it.
    
    Fixes: c72f61e74073 ("Input: wm97xx: split out touchscreen registering")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/87dce7e80ea9b191843fa22415ca3aef5f3cc2e6.1643529968.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 0a907ee9d95e3ac35eb023d71f29eae0aaa52d1b
Author: Sean Anderson <sean.anderson@seco.com>
Date:   Thu Jan 27 14:00:03 2022 -0500

    usb: ulpi: Call of_node_put correctly
    
    of_node_put should always be called on device nodes gotten from
    of_get_*. Additionally, it should only be called after there are no
    remaining users. To address the first issue, call of_node_put if later
    steps in ulpi_register fail. To address the latter, call put_device if
    device_register fails, which will call ulpi_dev_release if necessary.
    
    Fixes: ef6a7bcfb01c ("usb: ulpi: Support device discovery via DT")
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Sean Anderson <sean.anderson@seco.com>
    Link: https://lore.kernel.org/r/20220127190004.1446909-3-sean.anderson@seco.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 092f45b13e51666fe8ecbf2d6cd247aa7e6c1f74
Author: Sean Anderson <sean.anderson@seco.com>
Date:   Thu Jan 27 14:00:02 2022 -0500

    usb: ulpi: Move of_node_put to ulpi_dev_release
    
    Drivers are not unbound from the device when ulpi_unregister_interface
    is called. Move of_node-freeing code to ulpi_dev_release which is called
    only after all users are gone.
    
    Fixes: ef6a7bcfb01c ("usb: ulpi: Support device discovery via DT")
    Cc: stable <stable@vger.kernel.org>
    Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Sean Anderson <sean.anderson@seco.com>
    Link: https://lore.kernel.org/r/20220127190004.1446909-2-sean.anderson@seco.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit baf927a833ca2c6717795ac131079f485cb7a5dc
Author: Horatiu Vultur <horatiu.vultur@microchip.com>
Date:   Mon Jan 31 09:52:01 2022 +0100

    pinctrl: microchip-sgpio: Fix support for regmap
    
    Initially the driver accessed the registers using u32 __iomem but then
    in the blamed commit it changed it to use regmap. The problem is that now
    the offset of the registers is not calculated anymore at word offset but
    at byte offset. Therefore make sure to multiply the offset with word size.
    
    Acked-by: Steen Hegelund <Steen.Hegelund@microchip.com>
    Reviewed-by: Colin Foster <colin.foster@in-advantage.com>
    Fixes: 2afbbab45c261a ("pinctrl: microchip-sgpio: update to support regmap")
    Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Link: https://lore.kernel.org/r/20220131085201.307031-1-horatiu.vultur@microchip.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 341adeec9adad0874f29a0a1af35638207352a39
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Wed Jan 26 23:33:04 2022 +0800

    net/smc: Forward wakeup to smc socket waitqueue after fallback
    
    When we replace TCP with SMC and a fallback occurs, there may be
    some socket waitqueue entries remaining in smc socket->wq, such
    as eppoll_entries inserted by userspace applications.
    
    After the fallback, data flows over TCP/IP and only clcsocket->wq
    will be woken up. Applications can't be notified by the entries
    which were inserted in smc socket->wq before fallback. So we need
    a mechanism to wake up smc socket->wq at the same time if some
    entries remaining in it.
    
    The current workaround is to transfer the entries from smc socket->wq
    to clcsock->wq during the fallback. But this may cause a crash
    like this:
    
     general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI
     CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E     5.16.0+ #107
     RIP: 0010:__wake_up_common+0x65/0x170
     Call Trace:
      <IRQ>
      __wake_up_common_lock+0x7a/0xc0
      sock_def_readable+0x3c/0x70
      tcp_data_queue+0x4a7/0xc40
      tcp_rcv_established+0x32f/0x660
      ? sk_filter_trim_cap+0xcb/0x2e0
      tcp_v4_do_rcv+0x10b/0x260
      tcp_v4_rcv+0xd2a/0xde0
      ip_protocol_deliver_rcu+0x3b/0x1d0
      ip_local_deliver_finish+0x54/0x60
      ip_local_deliver+0x6a/0x110
      ? tcp_v4_early_demux+0xa2/0x140
      ? tcp_v4_early_demux+0x10d/0x140
      ip_sublist_rcv_finish+0x49/0x60
      ip_sublist_rcv+0x19d/0x230
      ip_list_rcv+0x13e/0x170
      __netif_receive_skb_list_core+0x1c2/0x240
      netif_receive_skb_list_internal+0x1e6/0x320
      napi_complete_done+0x11d/0x190
      mlx5e_napi_poll+0x163/0x6b0 [mlx5_core]
      __napi_poll+0x3c/0x1b0
      net_rx_action+0x27c/0x300
      __do_softirq+0x114/0x2d2
      irq_exit_rcu+0xb4/0xe0
      common_interrupt+0xba/0xe0
      </IRQ>
      <TASK>
    
    The crash is caused by privately transferring waitqueue entries from
    smc socket->wq to clcsock->wq. The owners of these entries, such as
    epoll, have no idea that the entries have been transferred to a
    different socket wait queue and still use original waitqueue spinlock
    (smc socket->wq.wait.lock) to make the entries operation exclusive,
    but it doesn't work. The operations to the entries, such as removing
    from the waitqueue (now is clcsock->wq after fallback), may cause a
    crash when clcsock waitqueue is being iterated over at the moment.
    
    This patch tries to fix this by no longer transferring wait queue
    entries privately, but introducing own implementations of clcsock's
    callback functions in fallback situation. The callback functions will
    forward the wakeup to smc socket->wq if clcsock->wq is actually woken
    up and smc socket->wq has remaining entries.
    
    Fixes: 2153bd1e3d3d ("net/smc: Transfer remaining wait queue entries during fallback")
    Suggested-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Acked-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d48384c7ed6c8fe4727eaa0f3048f62afd1cd715
Author: Pawel Dembicki <paweldembicki@gmail.com>
Date:   Tue Jan 11 23:12:05 2022 +0100

    USB: serial: option: add ZTE MF286D modem
    
    Modem from ZTE MF286D is an Qualcomm MDM9250 based 3G/4G modem.
    
    T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=5000 MxCh= 0
    D:  Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
    P:  Vendor=19d2 ProdID=1485 Rev=52.87
    S:  Manufacturer=ZTE,Incorporated
    S:  Product=ZTE Technologies MSM
    S:  SerialNumber=MF286DZTED000000
    C:* #Ifs= 7 Cfg#= 1 Atr=80 MxPwr=896mA
    A:  FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=06 Prot=00
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=ff Driver=rndis_host
    E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
    I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host
    E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
    E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=87(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
    E:  Ad=86(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    E:  Ad=88(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
    E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs
    E:  Ad=05(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=89(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    
    Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit fa77ce201f7f2d823b07753575122d1ae5597fbe
Author: Stephan Brunner <s.brunner@stephan-brunner.net>
Date:   Sat Jan 8 13:00:20 2022 +0100

    USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
    
    Programmable lab power supplies made by GW Instek, such as the
    GPP-2323, have a USB port exposing a serial port to control the device.
    
    Stringing the supplied Windows driver, references to the ch341 chip are
    found. Binding the existing ch341 driver to the VID/PID of the GPP-2323
    ("GW Instek USB2.0-Serial" as per the USB product name) works out of the
    box, communication and control is now possible.
    
    This patch should work with any GPP series power supply due to
    similarities in the product line.
    
    Signed-off-by: Stephan Brunner <s.brunner@stephan-brunner.net>
    Link: https://lore.kernel.org/r/4a47b864-0816-6f6a-efee-aa20e74bcdc6@stephan-brunner.net
    Cc: stable@vger.kernel.org
    Signed-off-by: Johan Hovold <johan@kernel.org>

commit ebe2b1add1055b903e2acd86b290a85297edc0b3
Author: Udipto Goswami <quic_ugoswami@quicinc.com>
Date:   Thu Jan 27 09:39:55 2022 +0530

    usb: f_fs: Fix use-after-free for epfile
    
    Consider a case where ffs_func_eps_disable is called from
    ffs_func_disable as part of composition switch and at the
    same time ffs_epfile_release get called from userspace.
    ffs_epfile_release will free up the read buffer and call
    ffs_data_closed which in turn destroys ffs->epfiles and
    mark it as NULL. While this was happening the driver has
    already initialized the local epfile in ffs_func_eps_disable
    which is now freed and waiting to acquire the spinlock. Once
    spinlock is acquired the driver proceeds with the stale value
    of epfile and tries to free the already freed read buffer
    causing use-after-free.
    
    Following is the illustration of the race:
    
          CPU1                                  CPU2
    
       ffs_func_eps_disable
       epfiles (local copy)
                                            ffs_epfile_release
                                            ffs_data_closed
                                            if (last file closed)
                                            ffs_data_reset
                                            ffs_data_clear
                                            ffs_epfiles_destroy
    spin_lock
    dereference epfiles
    
    Fix this races by taking epfiles local copy & assigning it under
    spinlock and if epfiles(local) is null then update it in ffs->epfiles
    then finally destroy it.
    Extending the scope further from the race, protecting the ep related
    structures, and concurrent accesses.
    
    Fixes: a9e6f83c2df1 ("usb: gadget: f_fs: stop sleeping in ffs_func_eps_disable")
    Co-developed-by: Udipto Goswami <quic_ugoswami@quicinc.com>
    Reviewed-by: John Keeping <john@metanate.com>
    Signed-off-by: Pratham Pratap <quic_ppratap@quicinc.com>
    Signed-off-by: Udipto Goswami <quic_ugoswami@quicinc.com>
    Link: https://lore.kernel.org/r/1643256595-10797-1-git-send-email-quic_ugoswami@quicinc.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 3c6f13ad723e7206f03bb2752b01d18202b7fc9d
Author: Imre Deak <imre.deak@intel.com>
Date:   Wed Jan 26 12:43:56 2022 +0200

    drm/i915/adlp: Fix TypeC PHY-ready status readout
    
    The TCSS_DDI_STATUS register is indexed by tc_port not by the FIA port
    index, fix this up. This only caused an issue on TC#3/4 ports in legacy
    mode, as in all other cases the two indices either match (on TC#1/2) or
    the TCSS_DDI_STATUS_READY flag is set regardless of something being
    connected or not (on TC#1/2/3/4 in dp-alt and tbt-alt modes).
    
    Reported-and-tested-by: Chia-Lin Kao (AceLan) <acelan.kao@canonical.com>
    Fixes: 55ce306c2aa1 ("drm/i915/adl_p: Implement TC sequences")
    Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4698
    Cc: José Roberto de Souza <jose.souza@intel.com>
    Cc: <stable@vger.kernel.org> # v5.14+
    Signed-off-by: Imre Deak <imre.deak@intel.com>
    Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220126104356.2022975-1-imre.deak@intel.com
    (cherry picked from commit 516b33460c5bee78b2055637b0547bdb0e6af754)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit b3f74938d65665f892d1b7807c51140f68dc911c
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Date:   Mon Jan 10 17:55:23 2022 -0800

    drm/i915/pmu: Use PM timestamp instead of RING TIMESTAMP for reference
    
    All timestamps returned by GuC for GuC PMU busyness are captured from
    GUC PM TIMESTAMP. Since this timestamp does not tick when GuC goes idle,
    kmd uses RING_TIMESTAMP to measure busyness of an engine with an active
    context. In further stress testing, the MMIO read of the RING_TIMESTAMP
    is seen to cause a rare hang. Resolve the issue by using gt specific
    timestamp from PM which is in sync with the GuC PM timestamp.
    
    Fixes: 77cdd054dd2c ("drm/i915/pmu: Connect engine busyness stats from GuC to pmu")
    Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
    Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
    Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220111015523.225562-1-umesh.nerlige.ramappa@intel.com
    (cherry picked from commit 721fd84ea1fe957453587efad5fdc44dfba58e04)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 90a3d22ff02b196d5884e111f39271a1d4ee8e3e
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Mon Jan 24 15:24:09 2022 +0300

    drm/i915/overlay: Prevent divide by zero bugs in scaling
    
    Smatch detected a divide by zero bug in check_overlay_scaling().
    
        drivers/gpu/drm/i915/display/intel_overlay.c:976 check_overlay_scaling()
        error: potential divide by zero bug '/ rec->dst_height'.
        drivers/gpu/drm/i915/display/intel_overlay.c:980 check_overlay_scaling()
        error: potential divide by zero bug '/ rec->dst_width'.
    
    Prevent this by ensuring that the dst height and width are non-zero.
    
    Fixes: 02e792fbaadb ("drm/i915: implement drmmode overlay support v4")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220124122409.GA31673@kili
    (cherry picked from commit cf5b64f7f10b28bebb9b7c9d25e7aee5cbe43918)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 5ae13c305ef8cb54efc4f0ba4565709b9f320fed
Author: Matthew Brost <matthew.brost@intel.com>
Date:   Tue Jan 11 08:39:29 2022 -0800

    drm/i915: Lock timeline mutex directly in error path of eb_pin_timeline
    
    Don't use the interruptable version of the timeline mutex lock in the
    error path of eb_pin_timeline as the cleanup must always happen.
    
    v2:
     (John Harrison)
      - Don't check for interrupt during mutex lock
    v3:
     (Tvrtko)
      - A comment explaining why lock helper isn't used
    
    Fixes: 544460c33821 ("drm/i915: Multi-BB execbuf")
    Signed-off-by: Matthew Brost <matthew.brost@intel.com>
    Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
    Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220111163929.14017-1-matthew.brost@intel.com
    (cherry picked from commit cb935c4618bd2ff9058feee4af7088446da6a763)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 8172f41859cf7516e73eb957297e6752b3073119
Author: Matthew Brost <matthew.brost@intel.com>
Date:   Thu Jan 20 20:31:16 2022 -0800

    drm/i915: Allocate intel_engine_coredump_alloc with ALLOW_FAIL
    
    Allocate intel_engine_coredump_alloc with ALLOW_FAIL rather than
    GFP_KERNEL to fully decouple the error capture from fence signalling.
    
    v2:
     (John Harrison)
      - Fix typo in commit message (s/do/to)
    
    Fixes: 8b91cdd4f8649 ("drm/i915: Use __GFP_KSWAPD_RECLAIM in the capture code")
    
    Signed-off-by: Matthew Brost <matthew.brost@intel.com>
    Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
    Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220121043118.24886-2-matthew.brost@intel.com
    (cherry picked from commit 4f72fc3c7f3d9f29a438bb0e17c7773f2fc8242a)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit b470947c3672f7eb7c4c271d510383d896831cc2
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Thu Jan 27 16:15:00 2022 -0600

    usb: dwc3: xilinx: fix uninitialized return value
    
    A previous patch to skip part of the initialization when a USB3 PHY was
    not present could result in the return value being uninitialized in that
    case, causing spurious probe failures. Initialize ret to 0 to avoid this.
    
    Fixes: 9678f3361afc ("usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode")
    Cc: <stable@vger.kernel.org>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220127221500.177021-1-robert.hancock@calian.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 94db9cc8f8fa2d5426ce79ec4ca16028f7084224
Author: Albert Geantă <albertgeanta@gmail.com>
Date:   Mon Jan 31 03:05:23 2022 +0200

    ALSA: hda/realtek: Add quirk for ASUS GU603
    
    The ASUS GU603 (Zephyrus M16 - SSID 1043:16b2) requires a quirk similar to
    other ASUS devices for correctly routing the 4 integrated speakers. This
    fixes it by adding a corresponding quirk entry, which connects the bass
    speakers to the proper DAC.
    
    Signed-off-by: Albert Geantă <albertgeanta@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220131010523.546386-1-albertgeanta@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit ea3541961376f733373839cc90493aafa8a7f733
Author: Christian Lachner <gladiac@gmail.com>
Date:   Sat Jan 29 12:32:43 2022 +0100

    ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after reboot from Windows
    
    This commit switches the Gigabyte X570 Aorus Xtreme from using the
    ALC1220_FIXUP_CLEVO_P950 to the ALC1220_FIXUP_GB_X570 quirk. This fixes
    the no-audio after reboot from windows problem.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=205275
    Signed-off-by: Christian Lachner <gladiac@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220129113243.93068-4-gladiac@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 41a8601302ecbe704ac970552c33dc942300fc37
Author: Christian Lachner <gladiac@gmail.com>
Date:   Sat Jan 29 12:32:42 2022 +0100

    ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer chipset)
    
    Newer versions of the X570 Master come with a newer revision of the
    mainboard chipset - the X570S. These boards have the same ALC1220 codec
    but seem to initialize the codec with a different parameter in Coef 0x7
    which causes the output audio to be very low. We therefore write a
    known-good value to Coef 0x7 to fix that. As the value is the exact same
    as on the other X570(non-S) boards the same quirk-function can be shared
    between both generations.
    
    This commit adds the Gigabyte X570S Aorus Master to the list of boards
    using the ALC1220_FIXUP_GB_X570 quirk. This fixes both, the silent output
    and the no-audio after reboot from windows problems.
    
    This work has been tested by the folks over at the level1techs forum here:
    https://forum.level1techs.com/t/has-anybody-gotten-audio-working-in-linux-on-aorus-x570-master/154072
    
    Signed-off-by: Christian Lachner <gladiac@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220129113243.93068-3-gladiac@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 63394a16086fc2152869d7902621e2525e14bc40
Author: Christian Lachner <gladiac@gmail.com>
Date:   Sat Jan 29 12:32:41 2022 +0100

    ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 quirks
    
    The initial commit of the new Gigabyte X570 ALC1220 quirks lacked the
    fixup-model entry in alc882_fixup_models[]. It seemed not to cause any ill
    effects but for completeness sake this commit makes up for that.
    
    Signed-off-by: Christian Lachner <gladiac@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220129113243.93068-2-gladiac@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit b837a9f5ab3bdfab9233c9f98a6bef717673a3e5
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Jan 31 08:57:38 2022 +0100

    ALSA: hda: realtek: Fix race at concurrent COEF updates
    
    The COEF access is done with two steps: setting the index then read or
    write the data.  When multiple COEF accesses are performed
    concurrently, the index and data might be paired unexpectedly.
    In most cases, this isn't a big problem as the COEF setup is done at
    the initialization, but some dynamic changes like the mute LED may hit
    such a race.
    
    For avoiding the racy COEF accesses, this patch introduces a new
    mutex coef_mutex to alc_spec, and wrap the COEF accessing functions
    with it.
    
    Reported-by: Alexander Sergeyev <sergeev917@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220111195229.a77wrpjclqwrx4bx@localhost.localdomain
    Link: https://lore.kernel.org/r/20220131075738.24323-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 47307c31d90ae7d52cebbbc7c1d4ff213213d4e9
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 12 12:38:11 2022 -0800

    crypto: octeontx2 - Avoid stack variable overflow
    
    Building with -Warray-bounds showed a stack variable array index
    overflow. Increase the expected size of the array to avoid the warning:
    
    In file included from ./include/linux/printk.h:555,
                     from ./include/asm-generic/bug.h:22,
                     from ./arch/x86/include/asm/bug.h:84,
                     from ./include/linux/bug.h:5,
                     from ./include/linux/mmdebug.h:5,
                     from ./include/linux/gfp.h:5,
                     from ./include/linux/firmware.h:7,
                     from drivers/crypto/marvell/octeontx2/otx2_cptpf_ucode.c:5:
    drivers/crypto/marvell/octeontx2/otx2_cptpf_ucode.c: In function 'otx2_cpt_print_uc_dbg_info':
    ./include/linux/dynamic_debug.h:162:33: warning: array subscript 4 is above array bounds of 'u32[4]' {aka 'unsigned int[4]'} [-Warray-bounds]
      162 |         _dynamic_func_call(fmt, __dynamic_pr_debug,             \
          |                                 ^
    ./include/linux/dynamic_debug.h:134:17: note: in definition of macro '__dynamic_func_call'
      134 |                 func(&id, ##__VA_ARGS__);               \
          |                 ^~~~
    ./include/linux/dynamic_debug.h:162:9: note: in expansion of macro '_dynamic_func_call'
      162 |         _dynamic_func_call(fmt, __dynamic_pr_debug,             \
          |         ^~~~~~~~~~~~~~~~~~
    ./include/linux/printk.h:570:9: note: in expansion of macro 'dynamic_pr_debug'
      570 |         dynamic_pr_debug(fmt, ##__VA_ARGS__)
          |         ^~~~~~~~~~~~~~~~
    drivers/crypto/marvell/octeontx2/otx2_cptpf_ucode.c:1807:41: note: in expansion of macro 'pr_debug'
     1807 |                                         pr_debug("Mask: %8.8x %8.8x %8.8x %8.8x %8.8x",
          |                                         ^~~~~~~~
    drivers/crypto/marvell/octeontx2/otx2_cptpf_ucode.c:1765:13: note: while referencing 'mask'
     1765 |         u32 mask[4];
          |             ^~~~
    
    This is justified because the mask size (eng_grps->engs_num) can be at
    most 144 (OTX2_CPT_MAX_ENGINES bits), which is larger than available
    storage. 4 * 32 == 128, so this must be 5: 5 * 32bit = 160.
    
    Additionally clear the mask before conversion so trailing bits are zero.
    
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: Boris Brezillon <bbrezillon@kernel.org>
    Cc: Arnaud Ebalard <arno@natisbad.org>
    Cc: Srujana Challa <schalla@marvell.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Suheil Chandran <schandran@marvell.com>
    Cc: Shijith Thotton <sthotton@marvell.com>
    Cc: Lukasz Bartosik <lbartosik@marvell.com>
    Cc: linux-crypto@vger.kernel.org
    Fixes: d9d7749773e8 ("crypto: octeontx2 - add apis for custom engine groups")
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

commit 2d86293c70750e4331e9616aded33ab6b47c299d
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Sun Jan 30 08:53:17 2022 -0800

    xfs: return errors in xfs_fs_sync_fs
    
    Now that the VFS will do something with the return values from
    ->sync_fs, make ours pass on error codes.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Christian Brauner <brauner@kernel.org>

commit dd5532a4994bfda0386eb2286ec00758cee08444
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Sun Jan 30 08:53:16 2022 -0800

    quota: make dquot_quota_sync return errors from ->sync_fs
    
    Strangely, dquot_quota_sync ignores the return code from the ->sync_fs
    call, which means that quotacalls like Q_SYNC never see the error.  This
    doesn't seem right, so fix that.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Christian Brauner <brauner@kernel.org>

commit 5679897eb104cec9e99609c3f045a0c20603da4c
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Sun Jan 30 08:53:16 2022 -0800

    vfs: make sync_filesystem return errors from ->sync_fs
    
    Strangely, sync_filesystem ignores the return code from the ->sync_fs
    call, which means that syscalls like syncfs(2) never see the error.
    This doesn't seem right, so fix that.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Christian Brauner <brauner@kernel.org>

commit 2719c7160dcfaae1f73a1c0c210ad3281c19022e
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Sun Jan 30 08:53:16 2022 -0800

    vfs: make freeze_super abort when sync_filesystem returns error
    
    If we fail to synchronize the filesystem while preparing to freeze the
    fs, abort the freeze.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Christian Brauner <brauner@kernel.org>

commit 632fe0bb8c5b9c06ec961f575ee42a6fff5eceeb
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Jan 6 11:23:09 2022 +0000

    iio: Fix error handling for PM
    
    The pm_runtime_enable will increase power disable depth.
    If the probe fails, we should use pm_runtime_disable() to balance
    pm_runtime_enable(). In the PM Runtime docs:
        Drivers in ->remove() callback should undo the runtime PM changes done
        in ->probe(). Usually this means calling pm_runtime_disable(),
        pm_runtime_dont_use_autosuspend() etc.
    We should do this in error handling.
    
    Fix this problem for the following drivers: bmc150, bmg160, kmx61,
    kxcj-1013, mma9551, mma9553.
    
    Fixes: 7d0ead5c3f00 ("iio: Reconcile operation order between iio_register/unregister and pm functions")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Link: https://lore.kernel.org/r/20220106112309.16879-1-linmq006@gmail.com
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 4165456fe6b7719c0c9626022a7d96c381c94e6f
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Tue Jan 11 09:47:02 2022 +0200

    iio: addac: ad74413r: correct comparator gpio getters mask usage
    
    The value of the GPIOs is currently altered using offsets rather
    than masks. Make use of __assign_bit and the BIT macro to turn
    the offsets into masks.
    
    Fixes: fea251b6a5db ("iio: addac: add AD74413R driver")
    Signed-off-by: Cosmin Tanislav <cosmin.tanislav@analog.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Link: https://lore.kernel.org/r/20220111074703.3677392-2-cosmin.tanislav@analog.com
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 8a3e4a5614adab30b6e0eb7dbd8ef737aabbb8eb
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Tue Jan 11 09:47:01 2022 +0200

    iio: addac: ad74413r: use ngpio size when iterating over mask
    
    ngpio is the actual number of GPIOs handled by the GPIO chip,
    as opposed to the max number of GPIOs.
    
    Fixes: fea251b6a5db ("iio: addac: add AD74413R driver")
    Signed-off-by: Cosmin Tanislav <cosmin.tanislav@analog.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Link: https://lore.kernel.org/r/20220111074703.3677392-1-cosmin.tanislav@analog.com
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit e7a3290d330e3f8cf06a3cad455c49e89183137b
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 12 12:34:56 2022 -0800

    iio: addac: ad74413r: Do not reference negative array offsets
    
    Instead of aiming rx_buf at an invalid array-boundary-crossing location,
    just skip the first increment. Seen when building with -Warray-bounds:
    
    drivers/iio/addac/ad74413r.c: In function 'ad74413r_update_scan_mode':
    drivers/iio/addac/ad74413r.c:843:22: warning: array subscript -4 is below array bounds of 'u8[16]' { aka 'unsigned char[16]'} [-Warray-bounds]
      843 |         u8 *rx_buf = &st->adc_samples_buf.rx_buf[-1 * AD74413R_FRAME_SIZE];
          |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/iio/addac/ad74413r.c:84:20: note: while referencing 'rx_buf'
       84 |                 u8 rx_buf[AD74413R_FRAME_SIZE * AD74413R_CHANNEL_MAX];
          |                    ^~~~~~
    
    Cc: Lars-Peter Clausen <lars@metafoo.de>
    Cc: Michael Hennerich <Michael.Hennerich@analog.com>
    Cc: Jonathan Cameron <jic23@kernel.org>
    Cc: linux-iio@vger.kernel.org
    Fixes: fea251b6a5db ("iio: addac: add AD74413R driver")
    Reviewed-by: Cosmin Tanislav <cosmin.tanislav@analog.com>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Link: https://lore.kernel.org/r/20220112203456.3950884-1-keescook@chromium.org
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit e0a2e37f303828d030a83f33ffe14b36cb88d563
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 29 09:32:47 2022 +0100

    iio: adc: men_z188_adc: Fix a resource leak in an error handling path
    
    If iio_device_register() fails, a previous ioremap() is left unbalanced.
    
    Update the error handling path and add the missing iounmap() call, as
    already done in the remove function.
    
    Fixes: 74aeac4da66f ("iio: adc: Add MEN 16z188 ADC driver")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/320fc777863880247c2aff4a9d1a54ba69abf080.1643445149.git.christophe.jaillet@wanadoo.fr
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 26291c54e111ff6ba87a164d85d4a4e134b7315c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 15:37:07 2022 +0200

    Linux 5.17-rc2

commit 22e424feb6658c5d6789e45121830357809c59cb
Author: Dominique Martinet <asmadeus@codewreck.org>
Date:   Sat Jan 29 18:42:59 2022 +0900

    Revert "fs/9p: search open fids first"
    
    This reverts commit 478ba09edc1f2f2ee27180a06150cb2d1a686f9c.
    
    That commit was meant as a fix for setattrs with by fd (e.g. ftruncate)
    to use an open fid instead of the first fid it found on lookup.
    The proper fix for that is to use the fid associated with the open file
    struct, available in iattr->ia_file for such operations, and was
    actually done just before in 66246641609b ("9p: retrieve fid from file
    when file instance exist.")
    As such, this commit is no longer required.
    
    Furthermore, changing lookup to return open fids first had unwanted side
    effects, as it turns out the protocol forbids the use of open fids for
    further walks (e.g. clone_fid) and we broke mounts for some servers
    enforcing this rule.
    
    Note this only reverts to the old working behaviour, but it's still
    possible for lookup to return open fids if dentry->d_fsdata is not set,
    so more work is needed to make sure we respect this rule in the future,
    for example by adding a flag to the lookup functions to only match
    certain fid open modes depending on caller requirements.
    
    Link: https://lkml.kernel.org/r/20220130130651.712293-1-asmadeus@codewreck.org
    Fixes: 478ba09edc1f ("fs/9p: search open fids first")
    Cc: stable@vger.kernel.org # v5.11+
    Reported-by: ron minnich <rminnich@gmail.com>
    Reported-by: ng@0x80.stream
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit c5fe9de7903330df7641fd342733fec6fb91afa2
Merge: 27a96c4feb837 243d308037441
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 15:12:02 2022 +0200

    Merge tag 'irq_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq fixes from Borislav Petkov:
    
     - Drop an unused private data field in the AIC driver
    
     - Various fixes to the realtek-rtl driver
    
     - Make the GICv3 ITS driver compile again in !SMP configurations
    
     - Force reset of the GICv3 ITSs at probe time to avoid issues during kexec
    
     - Yet another kfree/bitmap_free conversion
    
     - Various DT updates (Renesas, SiFive)
    
    * tag 'irq_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      dt-bindings: interrupt-controller: sifive,plic: Group interrupt tuples
      dt-bindings: interrupt-controller: sifive,plic: Fix number of interrupts
      dt-bindings: irqchip: renesas-irqc: Add R-Car V3U support
      irqchip/gic-v3-its: Reset each ITS's BASERn register before probe
      irqchip/gic-v3-its: Fix build for !SMP
      irqchip/loongson-pch-ms: Use bitmap_free() to free bitmap
      irqchip/realtek-rtl: Service all pending interrupts
      irqchip/realtek-rtl: Fix off-by-one in routing
      irqchip/realtek-rtl: Map control data to virq
      irqchip/apple-aic: Drop unused ipi_hwirq field

commit 27a96c4feb837093f6075bbd97c942260d26ef33
Merge: 24f4db1f3a272 c5de60cd622a2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 15:02:32 2022 +0200

    Merge tag 'perf_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull perf fixes from Borislav Petkov:
    
     - Prevent accesses to the per-CPU cgroup context list from another CPU
       except the one it belongs to, to avoid list corruption
    
     - Make sure parent events are always woken up to avoid indefinite hangs
       in the traced workload
    
    * tag 'perf_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      perf/core: Fix cgroup event list management
      perf: Always wake the parent event

commit a1cba0e2deeb0fe5200602658ed1078a714f8667
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Wed Jan 5 02:09:20 2022 +0500

    iio: frequency: admv1013: remove the always true condition
    
    unsigned int variable is always greater than or equal to zero. Make the
    if condition simple.
    
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Fixes: da35a7b526d9 ("iio: frequency: admv1013: add support for ADMV1013")
    Link: https://lore.kernel.org/r/YdS3gJYtECMaDDjA@debian-BULLSEYE-live-builder-AMD64
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 24f4db1f3a2725a6308105081d822b26889e1018
Merge: a96d3a5b15192 809232619f5b1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 13:09:00 2022 +0200

    Merge tag 'sched_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull scheduler fix from Borislav Petkov:
     "Make sure the membarrier-rseq fence commands are part of the reported
      set when querying membarrier(2) commands through MEMBARRIER_CMD_QUERY"
    
    * tag 'sched_urgent_for_v5.17_rc2_p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      sched/membarrier: Fix membarrier-rseq fence command missing from query bitmask

commit a96d3a5b15192f401aa8fa68965ff2a5303367a9
Merge: 8dd71685dcb78 e464121f2d40e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 12:55:06 2022 +0200

    Merge tag 'x86_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 fixes from Borislav Petkov:
    
     - Add another Intel CPU model to the list of CPUs supporting the
       processor inventory unique number
    
     - Allow writing to MCE thresholding sysfs files again - a previous
       change had accidentally disabled it and no one noticed. Goes to show
       how much is this stuff used
    
    * tag 'x86_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/cpu: Add Xeon Icelake-D to list of CPUs that support PPIN
      x86/MCE/AMD: Allow thresholding interface updates after init

commit 8dd71685dcb7839f6d91417e0a9237daca363908
Merge: f8c7e4ede46fe ddf4b773aa407
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 30 11:21:50 2022 +0200

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc fixes from Andrew Morton:
     "12 patches.
    
      Subsystems affected by this patch series: sysctl, binfmt, ia64, mm
      (memory-failure, folios, kasan, and psi), selftests, and ocfs2"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>:
      ocfs2: fix a deadlock when commit trans
      jbd2: export jbd2_journal_[grab|put]_journal_head
      psi: fix "defined but not used" warnings when CONFIG_PROC_FS=n
      psi: fix "no previous prototype" warnings when CONFIG_CGROUPS=n
      mm, kasan: use compare-exchange operation to set KASAN page tag
      kasan: test: fix compatibility with FORTIFY_SOURCE
      tools/testing/scatterlist: add missing defines
      mm: page->mapping folio->mapping should have the same offset
      memory-failure: fetch compound_head after pgmap_pfn_valid()
      ia64: make IA64_MCA_RECOVERY bool instead of tristate
      binfmt_misc: fix crash when load/unload module
      include/linux/sysctl.h: fix register_sysctl_mount_point() return type

commit 8fd9415042826c7609c588e5ef45f3e84237785f
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sat Jan 29 18:54:29 2022 +0100

    arm64: dts: rockchip: align pl330 node name with dtschema
    
    Fixes dtbs_check warnings like:
    
      dmac@ff240000: $nodename:0: 'dmac@ff240000' does not match '^dma-controller(@.*)?$'
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220129175429.298836-1-krzysztof.kozlowski@canonical.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit 62966cbdda8a92f82d966a45aa671e788b2006f7
Author: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
Date:   Wed Jan 19 14:49:48 2022 +0100

    arm64: dts: rockchip: fix rk3399-puma eMMC HS400 signal integrity
    
    There are signal integrity issues running the eMMC at 200MHz on Puma
    RK3399-Q7.
    
    Similar to the work-around found for RK3399 Gru boards, lowering the
    frequency to 100MHz made the eMMC much more stable, so let's lower the
    frequency to 100MHz.
    
    It might be possible to run at 150MHz as on RK3399 Gru boards but only
    100MHz was extensively tested.
    
    Cc: Quentin Schulz <foss+kernel@0leil.net>
    Signed-off-by: Jakob Unterwurzacher <jakob.unterwurzacher@theobroma-systems.com>
    Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
    Link: https://lore.kernel.org/r/20220119134948.1444965-1-quentin.schulz@theobroma-systems.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit ad02776cf8d083e28b1ca4d93d8b1949668c27cc
Author: Peter Geis <pgwipeout@gmail.com>
Date:   Thu Jan 27 19:38:05 2022 -0500

    arm64: dts: rockchip: fix Quartz64-A ddr regulator voltage
    
    The Quartz64 Model A uses a voltage divider to ensure ddr voltage is
    within specification from the default regulator configuration.
    Adjusting this voltage is detrimental, and currently causes the ddr
    voltage to be about 0.8v.
    
    Remove the min and max voltage setpoints for the ddr regulator.
    
    Fixes: b33a22a1e7c4 ("arm64: dts: rockchip: add basic dts for Pine64 Quartz64-A")
    Signed-off-by: Peter Geis <pgwipeout@gmail.com>
    Link: https://lore.kernel.org/r/20220128003809.3291407-2-pgwipeout@gmail.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit ddf4b773aa40790dfa936bd845c18e735a49c61c
Author: Joseph Qi <joseph.qi@linux.alibaba.com>
Date:   Sat Jan 29 13:41:27 2022 -0800

    ocfs2: fix a deadlock when commit trans
    
    commit 6f1b228529ae introduces a regression which can deadlock as
    follows:
    
      Task1:                              Task2:
      jbd2_journal_commit_transaction     ocfs2_test_bg_bit_allocatable
      spin_lock(&jh->b_state_lock)        jbd_lock_bh_journal_head
      __jbd2_journal_remove_checkpoint    spin_lock(&jh->b_state_lock)
      jbd2_journal_put_journal_head
      jbd_lock_bh_journal_head
    
    Task1 and Task2 lock bh->b_state and jh->b_state_lock in different
    order, which finally result in a deadlock.
    
    So use jbd2_journal_[grab|put]_journal_head instead in
    ocfs2_test_bg_bit_allocatable() to fix it.
    
    Link: https://lkml.kernel.org/r/20220121071205.100648-3-joseph.qi@linux.alibaba.com
    Fixes: 6f1b228529ae ("ocfs2: fix race between searching chunks and release journal_head from buffer_head")
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Reported-by: Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>
    Tested-by: Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>
    Reported-by: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Andreas Dilger <adilger.kernel@dilger.ca>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Jun Piao <piaojun@huawei.com>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4cd1103d8c66b2cdb7e64385c274edb0ac5e8887
Author: Joseph Qi <joseph.qi@linux.alibaba.com>
Date:   Sat Jan 29 13:41:23 2022 -0800

    jbd2: export jbd2_journal_[grab|put]_journal_head
    
    Patch series "ocfs2: fix a deadlock case".
    
    This fixes a deadlock case in ocfs2.  We firstly export jbd2 symbols
    jbd2_journal_[grab|put]_journal_head as preparation and later use them
    in ocfs2 insread of jbd_[lock|unlock]_bh_journal_head to fix the
    deadlock.
    
    This patch (of 2):
    
    This exports symbols jbd2_journal_[grab|put]_journal_head, which will be
    used outside modules, e.g.  ocfs2.
    
    Link: https://lkml.kernel.org/r/20220121071205.100648-2-joseph.qi@linux.alibaba.com
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Cc: Andreas Dilger <adilger.kernel@dilger.ca>
    Cc: Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>
    Cc: Saeed Mirzamohammadi <saeed.mirzamohammadi@oracle.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 44585f7bc0cb01095bc2ad4258049c02bbad21ef
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Sat Jan 29 13:41:20 2022 -0800

    psi: fix "defined but not used" warnings when CONFIG_PROC_FS=n
    
    When CONFIG_PROC_FS is disabled psi code generates the following
    warnings:
    
      kernel/sched/psi.c:1364:30: warning: 'psi_cpu_proc_ops' defined but not used [-Wunused-const-variable=]
          1364 | static const struct proc_ops psi_cpu_proc_ops = {
               |                              ^~~~~~~~~~~~~~~~
      kernel/sched/psi.c:1355:30: warning: 'psi_memory_proc_ops' defined but not used [-Wunused-const-variable=]
          1355 | static const struct proc_ops psi_memory_proc_ops = {
               |                              ^~~~~~~~~~~~~~~~~~~
      kernel/sched/psi.c:1346:30: warning: 'psi_io_proc_ops' defined but not used [-Wunused-const-variable=]
          1346 | static const struct proc_ops psi_io_proc_ops = {
               |                              ^~~~~~~~~~~~~~~
    
    Make definitions of these structures and related functions conditional
    on CONFIG_PROC_FS config.
    
    Link: https://lkml.kernel.org/r/20220119223940.787748-3-surenb@google.com
    Fixes: 0e94682b73bf ("psi: introduce psi monitor")
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 51e50fbd3efc6064c30ed73a5e009018b36e290a
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Sat Jan 29 13:41:17 2022 -0800

    psi: fix "no previous prototype" warnings when CONFIG_CGROUPS=n
    
    When CONFIG_CGROUPS is disabled psi code generates the following
    warnings:
    
      kernel/sched/psi.c:1112:21: warning: no previous prototype for 'psi_trigger_create' [-Wmissing-prototypes]
          1112 | struct psi_trigger *psi_trigger_create(struct psi_group *group,
               |                     ^~~~~~~~~~~~~~~~~~
      kernel/sched/psi.c:1182:6: warning: no previous prototype for 'psi_trigger_destroy' [-Wmissing-prototypes]
          1182 | void psi_trigger_destroy(struct psi_trigger *t)
               |      ^~~~~~~~~~~~~~~~~~~
      kernel/sched/psi.c:1249:10: warning: no previous prototype for 'psi_trigger_poll' [-Wmissing-prototypes]
          1249 | __poll_t psi_trigger_poll(void **trigger_ptr,
               |          ^~~~~~~~~~~~~~~~
    
    Change the declarations of these functions in the header to provide the
    prototypes even when they are unused.
    
    Link: https://lkml.kernel.org/r/20220119223940.787748-2-surenb@google.com
    Fixes: 0e94682b73bf ("psi: introduce psi monitor")
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 27fe73394a1c6d0b07fa4d95f1bca116d1cc66e9
Author: Peter Collingbourne <pcc@google.com>
Date:   Sat Jan 29 13:41:14 2022 -0800

    mm, kasan: use compare-exchange operation to set KASAN page tag
    
    It has been reported that the tag setting operation on newly-allocated
    pages can cause the page flags to be corrupted when performed
    concurrently with other flag updates as a result of the use of
    non-atomic operations.
    
    Fix the problem by using a compare-exchange loop to update the tag.
    
    Link: https://lkml.kernel.org/r/20220120020148.1632253-1-pcc@google.com
    Link: https://linux-review.googlesource.com/id/I456b24a2b9067d93968d43b4bb3351c0cec63101
    Fixes: 2813b9c02962 ("kasan, mm, arm64: tag non slab memory allocated via pagealloc")
    Signed-off-by: Peter Collingbourne <pcc@google.com>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 09c6304e38e440b93a9ebf3f3cf75cd6cb529f91
Author: Marco Elver <elver@google.com>
Date:   Sat Jan 29 13:41:11 2022 -0800

    kasan: test: fix compatibility with FORTIFY_SOURCE
    
    With CONFIG_FORTIFY_SOURCE enabled, string functions will also perform
    dynamic checks using __builtin_object_size(ptr), which when failed will
    panic the kernel.
    
    Because the KASAN test deliberately performs out-of-bounds operations,
    the kernel panics with FORTIFY_SOURCE, for example:
    
     | kernel BUG at lib/string_helpers.c:910!
     | invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
     | CPU: 1 PID: 137 Comm: kunit_try_catch Tainted: G    B             5.16.0-rc3+ #3
     | Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
     | RIP: 0010:fortify_panic+0x19/0x1b
     | ...
     | Call Trace:
     |  kmalloc_oob_in_memset.cold+0x16/0x16
     |  ...
    
    Fix it by also hiding `ptr` from the optimizer, which will ensure that
    __builtin_object_size() does not return a valid size, preventing
    fortified string functions from panicking.
    
    Link: https://lkml.kernel.org/r/20220124160744.1244685-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reported-by: Nico Pache <npache@redhat.com>
    Reviewed-by: Nico Pache <npache@redhat.com>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0226bd64da52aa23120d1450c37a424387827a21
Author: Maor Gottlieb <maorg@nvidia.com>
Date:   Sat Jan 29 13:41:07 2022 -0800

    tools/testing/scatterlist: add missing defines
    
    The cited commits replaced preemptible with pagefault_disabled and
    flush_kernel_dcache_page with flush_dcache_page respectively, hence need
    to update the corresponding defines in the test.
    
      scatterlist.c: In function ‘sg_miter_stop’:
      scatterlist.c:919:4: warning: implicit declaration of function ‘flush_dcache_page’ [-Wimplicit-function-declaration]
          flush_dcache_page(miter->page);
          ^~~~~~~~~~~~~~~~~
      In file included from linux/scatterlist.h:8:0,
                       from scatterlist.c:9:
      scatterlist.c:922:18: warning: implicit declaration of function ‘pagefault_disabled’ [-Wimplicit-function-declaration]
          WARN_ON_ONCE(!pagefault_disabled());
                        ^
      linux/mm.h:23:25: note: in definition of macro ‘WARN_ON_ONCE’
        int __ret_warn_on = !!(condition);                      \
                               ^~~~~~~~~
    
    Link: https://lkml.kernel.org/r/20220118082105.1737320-1-maorg@nvidia.com
    Fixes: 723aca208516 ("mm/scatterlist: replace the !preemptible warning in sg_miter_stop()")
    Fixes: 0e84f5dbf8d6 ("scatterlist: replace flush_kernel_dcache_page with flush_dcache_page")
    Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 536f4217ced62b671bd759f6b549621a5654a70f
Author: Wei Yang <richard.weiyang@gmail.com>
Date:   Sat Jan 29 13:41:04 2022 -0800

    mm: page->mapping folio->mapping should have the same offset
    
    As with the other members of folio, the offset of page->mapping and
    folio->mapping must be the same.  The compile-time check was
    inadvertently removed during development.  Add it back.
    
    [willy@infradead.org: changelog redo]
    
    Link: https://lkml.kernel.org/r/20220104011734.21714-1-richard.weiyang@gmail.com
    Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
    Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 61e28cf0543c7d8e6ef88c3c305f727c5a21ba5b
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Sat Jan 29 13:41:01 2022 -0800

    memory-failure: fetch compound_head after pgmap_pfn_valid()
    
    memory_failure_dev_pagemap() at the moment assumes base pages (e.g.
    dax_lock_page()).  For devmap with compound pages fetch the
    compound_head in case a tail page memory failure is being handled.
    
    Currently this is a nop, but in the advent of compound pages in
    dev_pagemap it allows memory_failure_dev_pagemap() to keep working.
    
    Without this fix memory-failure handling (i.e.  MCEs on pmem) with
    device-dax configured namespaces will regress (and crash).
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-2-joao.m.martins@oracle.com
    Reported-by: Jane Chu <jane.chu@oracle.com>
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Reviewed-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dbecf9b8b8ce580f4e11afed9d61e8aa294cddd2
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sat Jan 29 13:40:58 2022 -0800

    ia64: make IA64_MCA_RECOVERY bool instead of tristate
    
    In linux-next, IA64_MCA_RECOVERY uses the (new) function
    make_task_dead(), which is not exported for use by modules.  Instead of
    exporting it for one user, convert IA64_MCA_RECOVERY to be a bool
    Kconfig symbol.
    
    In a config file from "kernel test robot <lkp@intel.com>" for a
    different problem, this linker error was exposed when
    CONFIG_IA64_MCA_RECOVERY=m.
    
    Fixes this build error:
    
      ERROR: modpost: "make_task_dead" [arch/ia64/kernel/mca_recovery.ko] undefined!
    
    Link: https://lkml.kernel.org/r/20220124213129.29306-1-rdunlap@infradead.org
    Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Suggested-by: Christoph Hellwig <hch@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e7f1e8834b2b2144dfbe0b2235d05e4f6f95882e
Author: Tong Zhang <ztong0001@gmail.com>
Date:   Sat Jan 29 13:40:55 2022 -0800

    binfmt_misc: fix crash when load/unload module
    
    We should unregister the table upon module unload otherwise something
    horrible will happen when we load binfmt_misc module again.  Also note
    that we should keep value returned by register_sysctl_mount_point() and
    release it later, otherwise it will leak.
    
    Also, per Christian's comment, to fully restore the old behavior that
    won't break userspace the check(binfmt_misc_header) should be
    eliminated.
    
    To reproduce:
      modprobe binfmt_misc
      modprobe -r binfmt_misc
      modprobe binfmt_misc
      modprobe -r binfmt_misc
      modprobe binfmt_misc
    
    resulting in
    
      modprobe: can't load module binfmt_misc (kernel/fs/binfmt_misc.ko): Cannot allocate memory
    
    and an unhappy kernel:
    
      binfmt_misc: Failed to create fs/binfmt_misc sysctl mount point
      binfmt_misc: Failed to create fs/binfmt_misc sysctl mount point
      BUG: unable to handle page fault for address: fffffbfff8004802
      Call Trace:
        init_misc_binfmt+0x2d/0x1000 [binfmt_misc]
    
    Link: https://lkml.kernel.org/r/20220124181812.1869535-2-ztong0001@gmail.com
    Fixes: 3ba442d5331f ("fs: move binfmt_misc sysctl to its own file")
    Signed-off-by: Tong Zhang <ztong0001@gmail.com>
    Co-developed-by: Christian Brauner<brauner@kernel.org>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6cb917411e028dcb66ce8f5db1b47361b78d7d3f
Author: Andrew Morton <akpm@linux-foundation.org>
Date:   Sat Jan 29 13:40:52 2022 -0800

    include/linux/sysctl.h: fix register_sysctl_mount_point() return type
    
    The CONFIG_SYSCTL=n stub returns the wrong type.
    
    Fixes: ee9efac48a082 ("sysctl: add helper to register a sysctl mount point")
    Reported-by: kernel test robot <lkp@intel.com>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Tong Zhang <ztong0001@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3a5286955bf5febc3d151bcb2c5e272e383b64aa
Author: Julian Braha <julianbraha@gmail.com>
Date:   Mon Jan 17 01:25:57 2022 -0500

    pinctrl: bcm63xx: fix unmet dependency on REGMAP for GPIO_REGMAP
    
    When PINCTRL_BCM63XX is selected,
    and REGMAP is not selected,
    Kbuild gives the following warning:
    
    WARNING: unmet direct dependencies detected for GPIO_REGMAP
      Depends on [n]: GPIOLIB [=y] && REGMAP [=n]
      Selected by [y]:
      - PINCTRL_BCM63XX [=y] && PINCTRL [=y]
    
    This is because PINCTRL_BCM63XX
    selects GPIO_REGMAP without selecting or depending on
    REGMAP, despite GPIO_REGMAP depending on REGMAP.
    
    This unmet dependency bug was detected by Kismet,
    a static analysis tool for Kconfig. Please advise
    if this is not the appropriate solution.
    
    Signed-off-by: Julian Braha <julianbraha@gmail.com>
    Link: https://lore.kernel.org/r/20220117062557.89568-1-julianbraha@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 5297c693d8c8e08fa742e3112cf70723f7a04da2
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 27 13:50:31 2022 -0800

    pinctrl: bcm2835: Fix a few error paths
    
    After commit 266423e60ea1 ("pinctrl: bcm2835: Change init order for gpio
    hogs") a few error paths would not unwind properly the registration of
    gpio ranges. Correct that by assigning a single error label and goto it
    whenever we encounter a fatal error.
    
    Fixes: 266423e60ea1 ("pinctrl: bcm2835: Change init order for gpio hogs")
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220127215033.267227-1-f.fainelli@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 474932a3b215de3dffd828d5ef3296275b80ea01
Merge: 1fd6bb5b47a65 500c77eed0fea
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sun Jan 30 02:27:01 2022 +0100

    Merge tag 'intel-pinctrl-v5.17-4' of gitolite.kernel.org:pub/scm/linux/kernel/git/pinctrl/intel into fixes
    
    intel-pinctrl for v5.17-4
    
    * Couple of fixes on how Intel driver handles an interrupt
    * Revert pin renaming change in ZynqMQ as it appears to be part of
      the Device Tree bindings
    * Fix ordering of the files in the Makefile
    
    The following is an automated git shortlog grouped by driver:
    
    intel:
     -  Fix a glitch when updating IRQ flags on a preconfigured line
     -  fix unexpected interrupt
    
    Place correctly CONFIG_PINCTRL_ST in the Makefile:
     - Place correctly CONFIG_PINCTRL_ST in the Makefile
    
    zynqmp:
     -  Revert "Unify pin naming"

commit dfd0dfb9a7cc04acf93435b440dd34c2ca7b4424
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Mon Jan 24 21:55:03 2022 +0300

    EDAC/xgene: Fix deferred probing
    
    The driver overrides error codes returned by platform_get_irq_optional()
    to -EINVAL for some strange reason, so if it returns -EPROBE_DEFER, the
    driver will fail the probe permanently instead of the deferred probing.
    Switch to propagating the proper error codes to platform driver code
    upwards.
    
      [ bp: Massage commit message. ]
    
    Fixes: 0d4429301c4a ("EDAC: Add APM X-Gene SoC EDAC driver")
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220124185503.6720-3-s.shtylyov@omp.ru

commit 243d30803744155a54bfb8a844cc964945cfd9a1
Merge: a0af3d1104f75 c89e5eb7dcf15
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Sat Jan 29 21:03:20 2022 +0100

    Merge tag 'irqchip-fixes-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent
    
    Pull irqchip fixes from Marc Zyngier:
    
      - Drop an unused private data field in the AIC driver
    
      - Various fixes to the realtek-rtl driver
    
      - Make the GICv3 ITS driver compile again in !SMP configurations
    
      - Force reset of the GICv3 ITSs at probe time to avoid issues during kexec
    
      - Yet another kfree/bitmap_free conversion
    
      - Various DT updates (Renesas, SiFive)
    
    Link: https://lore.kernel.org/r/20220128174217.517041-1-maz@kernel.org

commit 489f710a738e24d887823a010b8b206b4124e26f
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Sat Jan 29 09:32:33 2022 +0000

    cifs: unlock chan_lock before calling cifs_put_tcp_session
    
    While removing an smb session, we need to free up the
    tcp session for each channel for that session. We were
    doing this with chan_lock held. This results in a
    cyclic dependency with cifs_tcp_ses_lock.
    
    For now, unlock the chan_lock temporarily before calling
    cifs_put_tcp_session. This should not cause any problem
    for now, since we do not remove channels anywhere else.
    And this code segment will not be called by two threads.
    
    When we do implement the code for removing channels, we
    will need to execute proper ref counting here.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit f8c7e4ede46fe63ff10000669652648aab09d112
Merge: 4cd90083d3257 66d28b21fe6b3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 19:05:47 2022 +0200

    Merge tag 'pci-v5.17-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci fixes from Bjorn Helgaas:
    
     - Fix compilation warnings in new mt7621 driver (Sergio Paracuellos)
    
     - Restore the sysfs "rom" file for VGA shadow ROMs, which was broken
       when converting "rom" to be a static attribute (Bjorn Helgaas)
    
    * tag 'pci-v5.17-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
      PCI/sysfs: Find shadow ROM before static attribute initialization
      PCI: mt7621: Remove unused function pcie_rmw()
      PCI: mt7621: Drop of_match_ptr() to avoid unused variable

commit 4cd90083d32574e52ac839c6c7e4ff445ac4472c
Merge: e255759e5afbc 8aa0f94b0a8d5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 15:45:33 2022 +0200

    Merge tag 'gpio-fixes-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio fixes from Bartosz Golaszewski:
     "Two fixes for the gpio-simulator:
    
       - fix a bug with hogs not being set-up in gpio-sim when user-space
         sets the chip label to an empty string
    
       - include the gpio-sim documentation in the index"
    
    * tag 'gpio-fixes-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:
      gpio: sim: add doc file to index file
      gpio: sim: check the label length when setting up device properties

commit e255759e5afbc233544d7246ad325417320e90b6
Merge: bb37101b36332 fc55e63e148f1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 15:34:04 2022 +0200

    Merge tag 'char-misc-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
    
    Pull char/misc driver fixes from Greg KH:
     "Here are two small char/misc driver fixes for 5.17-rc2 that fix some
      reported issues. They are:
    
       - fix up a merge issue in the at25.c driver that ended up dropping
         some lines in the driver. The removed lines ended being needed, so
         this restores it and the driver works again.
    
       - counter core fix where the wrong error was being returned, NULL
         should be the correct error for when memory is gone here, like the
         kmalloc() core does.
    
      Both of these have been in linux-next this week with no reported
      issues"
    
    * tag 'char-misc-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
      counter: fix an IS_ERR() vs NULL bug
      eeprom: at25: Restore missing allocation

commit bb37101b36332345a1e1c1f9f2f3bcc8ad7edb65
Merge: 44aa31a2bfaab d1ad2721b1eb0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 15:23:13 2022 +0200

    Merge tag 'tty-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
    
    Pull tty/serial driver fixes from Greg KH:
     "Here are some small bug fixes and reverts for reported problems with
      the tty core and drivers. They include:
    
       - revert the fifo use for the 8250 console mode. It caused too many
         regressions and problems, and had a bug in it as well. This is
         being reworked and should show up in a later -rc1 release, but it's
         not ready for 5.17
    
       - rpmsg tty race fix
    
       - restore the cyclades.h uapi header file. Turns out a compiler test
         suite used it for some unknown reason. Bring it back just for the
         parts that are used by the builder test so they continue to build.
         No functionality is restored as no one actually has this hardware
         anymore, nor is it really tested.
    
       - stm32 driver fixes
    
       - n_gsm flow control fixes
    
       - pl011 driver fix
    
       - rs485 initialization fix
    
      All of these have been in linux-next this week with no reported
      problems"
    
    * tag 'tty-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
      kbuild: remove include/linux/cyclades.h from header file check
      serial: core: Initialize rs485 RTS polarity already on probe
      serial: pl011: Fix incorrect rs485 RTS polarity on set_mctrl
      serial: stm32: fix software flow control transfer
      serial: stm32: prevent TDR register overwrite when sending x_char
      tty: n_gsm: fix SW flow control encoding/handling
      serial: 8250: of: Fix mapped region size when using reg-offset property
      tty: rpmsg: Fix race condition releasing tty port
      tty: Partially revert the removal of the Cyclades public API
      tty: Add support for Brainboxes UC cards.
      Revert "tty: serial: Use fifo in 8250 console driver"

commit 44aa31a2bfaab2ad36614f05162cda88ade9ce65
Merge: cb323ee75d24e 79aa3e19fe8f5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 15:17:20 2022 +0200

    Merge tag 'usb-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
    
    Pull USB driver fixes from Greg KH:
     "Here are some small USB driver fixes for 5.17-rc2 that resolve a
      number of reported problems. These include:
    
       - typec driver fixes
    
       - xhci platform driver fixes for suspending
    
       - ulpi core fix
    
       - role.h build fix
    
       - new device ids
    
       - syzbot-reported bugfixes
    
       - gadget driver fixes
    
       - dwc3 driver fixes
    
       - other small fixes
    
      All of these have been in linux-next this week with no reported
      issues"
    
    * tag 'usb-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
      usb: cdnsp: Fix segmentation fault in cdns_lost_power function
      usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
      usb: gadget: at91_udc: fix incorrect print type
      usb: dwc3: xilinx: Fix error handling when getting USB3 PHY
      usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode
      usb: xhci-plat: fix crash when suspend if remote wake enable
      usb: common: ulpi: Fix crash in ulpi_match()
      usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
      ucsi_ccg: Check DEV_INT bit only when starting CCG4
      USB: core: Fix hang in usb_kill_urb by adding memory barriers
      usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
      usb: typec: tcpm: Do not disconnect when receiving VSAFE0V
      usb: typec: tcpm: Do not disconnect while receiving VBUS off
      usb: typec: Don't try to register component master without components
      usb: typec: Only attempt to link USB ports if there is fwnode
      usb: typec: tcpci: don't touch CC line if it's Vconn source
      usb: roles: fix include/linux/usb/role.h compile issue

commit cb323ee75d24e7acc2f188d123ba6df46159cf09
Merge: 3b58e9f3a301e b879f915bc48a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 15:01:08 2022 +0200

    Merge tag 'block-5.17-2022-01-28' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
    
     - NVMe pull request
          - add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs (Wu
            Zheng)
          - remove the unneeded ret variable in nvmf_dev_show (Changcheng
            Deng)
    
     - Fix for a hang regression introduced with a patch in the merge
       window, where low queue depth devices would not always get woken
       correctly (Laibin)
    
     - Small series fixing an IO accounting issue with bio backed dm devices
       (Mike, Yu)
    
    * tag 'block-5.17-2022-01-28' of git://git.kernel.dk/linux-block:
      dm: properly fix redundant bio-based IO accounting
      dm: revert partial fix for redundant bio-based IO accounting
      block: add bio_start_io_acct_time() to control start_time
      blk-mq: Fix wrong wakeup batch configuration which will cause hang
      nvme-fabrics: remove the unneeded ret variable in nvmf_dev_show
      nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs
      blk-mq: fix missing blk_account_io_done() in error path
      block: fix memory leak in disk_register_independent_access_ranges

commit 3b58e9f3a301e175d2de6f7fa1e834c4605e1c73
Merge: d66c1e79b9fcb f6133fbd37381
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 14:53:07 2022 +0200

    Merge tag 'io_uring-5.17-2022-01-28' of git://git.kernel.dk/linux-block
    
    Pull io_uring fixes from Jens Axboe:
     "Just two small fixes this time:
    
       - Fix a bug that can lead to node registration taking 1 second, when
         it should finish much quicker (Dylan)
    
       - Remove an unused argument from a function (Usama)"
    
    * tag 'io_uring-5.17-2022-01-28' of git://git.kernel.dk/linux-block:
      io_uring: remove unused argument from io_rsrc_node_alloc
      io_uring: fix bug in slow unregistering of nodes

commit d66c1e79b9fcbfc6559ea3c5b1243d590fa04179
Merge: 216e2aede2b57 8defc2a5dd8f4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 14:46:19 2022 +0200

    Merge tag 'powerpc-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc fixes from Michael Ellerman:
    
     - Fix VM debug warnings on boot triggered via __set_fixmap().
    
     - Fix a debug warning in the 64-bit Book3S PMU handling code.
    
     - Fix nested guest HFSCR handling with multiple vCPUs on Power9 or
       later.
    
     - Fix decrementer storm caused by a recent change, seen with some
       configs.
    
    Thanks to Alexey Kardashevskiy, Athira Rajeev, Christophe Leroy,
    Fabiano Rosas, Maxime Bizon, Nicholas Piggin, and Sachin Sant.
    
    * tag 'powerpc-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc/64s/interrupt: Fix decrementer storm
      KVM: PPC: Book3S HV Nested: Fix nested HFSCR being clobbered with multiple vCPUs
      powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending
      powerpc/fixmap: Fix VM debug warning on unmap

commit 216e2aede2b575016bd579e0c23661bbdbbaada7
Merge: d1e7f0919ea84 297ae1eb23b04
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 08:57:22 2022 +0200

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fixes from Catalin Marinas:
    
     - Errata workarounds for Cortex-A510: broken hardware dirty bit
       management, detection code for the TRBE (tracing) bugs with the
       actual fixes going in via the CoreSight tree.
    
     - Cortex-X2 errata handling for TRBE (inheriting the workarounds from
       Cortex-A710).
    
     - Fix ex_handler_load_unaligned_zeropad() to use the correct struct
       members.
    
     - A couple of kselftest fixes for FPSIMD.
    
     - Silence the vdso "no previous prototype" warning.
    
     - Mark start_backtrace() notrace and NOKPROBE_SYMBOL.
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: cpufeature: List early Cortex-A510 parts as having broken dbm
      kselftest/arm64: Correct logging of FPSIMD register read via ptrace
      kselftest/arm64: Skip VL_INHERIT tests for unsupported vector types
      arm64: errata: Add detection for TRBE trace data corruption
      arm64: errata: Add detection for TRBE invalid prohibited states
      arm64: errata: Add detection for TRBE ignored system register writes
      arm64: Add Cortex-A510 CPU part definition
      arm64: extable: fix load_unaligned_zeropad() reg indices
      arm64: Mark start_backtrace() notrace and NOKPROBE_SYMBOL
      arm64: errata: Update ARM64_ERRATUM_[2119858|2224489] with Cortex-X2 ranges
      arm64: Add Cortex-X2 CPU part definition
      arm64: vdso: Fix "no previous prototype" warning

commit d1e7f0919ea84911e2ab965418cd502ba6a906e1
Merge: 246e179d637ef 7f5056b9e7b71
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 08:52:27 2022 +0200

    Merge tag 'fixes-v5.17-lsm-ceph-null' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
    
    Pull security sybsystem fix from James Morris:
     "Fix NULL pointer crash in LSM via Ceph, from Vivek Goyal"
    
    * tag 'fixes-v5.17-lsm-ceph-null' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security:
      security, lsm: dentry_init_security() Handle multi LSM registration

commit 91f6d5f181f6629dd74ab71759fe92d3f4eff966
Author: Alexander Stein <alexander.stein@ew.tq-group.com>
Date:   Sat Jan 29 14:39:05 2022 +0800

    arm64: dts: imx8mq: fix lcdif port node
    
    The port node does not have a unit-address, remove it.
    This fixes the warnings:
    lcd-controller@30320000: 'port' is a required property
    lcd-controller@30320000: 'port@0' does not match any of the regexes:
    'pinctrl-[0-9]+'
    
    Fixes: commit d0081bd02a03 ("arm64: dts: imx8mq: Add NWL MIPI DSI controller")
    Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
    Reviewed-by: Fabio Estevam <festevam@gmail.com>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 5ea62d06b1899f63c4374f52c8d40c43cad69ec0
Author: Martin Kepplinger <martink@posteo.de>
Date:   Fri Jan 21 10:33:26 2022 +0100

    arm64: dts: imx8mq-librem5: fix mipi_csi1 port number to sensor
    
    Since the previous commit fixed a hardware description bug for imx8mq,
    we need to fix up all DT users like this. The mipi_csi port@0
    is connected to the sensor, not port@1.
    
    Fixes: fed7603597fa ("arm64: dts: imx8mq-librem5: describe the selfie cam")
    Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 283d45145fbf460dbaf0229cacd7ed60ec52f364
Author: Martin Kepplinger <martink@posteo.de>
Date:   Fri Jan 21 10:33:25 2022 +0100

    arm64: dts: imx8mq: fix mipi_csi bidirectional port numbers
    
    The port numbers for the imx8mq mipi csi controller are wrong and
    the mipi driver can't find any media devices as port@1 is connected
    to the CSI bridge, not port@0. And port@0 is connected to the
    source - the sensor. Fix this.
    
    Fixes: bcadd5f66c2a ("arm64: dts: imx8mq: add mipi csi phy and csi bridge descriptions")
    Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 246e179d637ef8432fb223e4a7ddced740a32350
Merge: 169387e2aa291 854d0982eef0e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 29 08:27:28 2022 +0200

    Merge tag 'docs-5.17-3' of git://git.lwn.net/linux
    
    Pull documentation fixes from Jonathan Corbet:
     "A few documentation fixes for 5.17"
    
    * tag 'docs-5.17-3' of git://git.lwn.net/linux:
      docs/vm: Fix typo in *harden*
      Documentation: arm: marvell: Extend Avanta list
      docs: fix typo in Documentation/kernel-hacking/locking.rst
      docs: Hook the RTLA documents into the kernel docs build

commit 6d58c5e21a3fe355ce6d1808e96d02a610265218
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 20 11:23:55 2022 -0600

    ARM: dts: imx7ulp: Fix 'assigned-clocks-parents' typo
    
    The correct property name is 'assigned-clock-parents', not
    'assigned-clocks-parents'. Though if the platform works with the typo, one
    has to wonder if the property is even needed.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Fixes: 8b8c7d97e2c7 ("ARM: dts: imx7ulp: Add wdog1 node")
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit ff3cfc35a4dd4b432e33eee4f6d772411d70399f
Author: Michael Walle <michael@walle.cc>
Date:   Sat Jan 15 22:04:32 2022 +0100

    arm64: dts: ls1028a: sl28: re-enable ftm_alarm0
    
    Commit dd3d936a1b17 ("arm64: dts: ls1028a: add ftm_alarm1 node to be
    used as wakeup source") disables ftm_alarm0 in the SoC dtsi but doesn't
    enable it on the board which is still using it. Re-enable it on the sl28
    board.
    
    Fixes: dd3d936a1b17 ("arm64: dts: ls1028a: add ftm_alarm1 node to be used as wakeup source")
    Reported-by: Guillaume Tucker <guillaume.tucker@collabora.com>
    Reported-by: "kernelci.org bot" <bot@kernelci.org>
    Signed-off-by: Michael Walle <michael@walle.cc>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit dbe0d009d8c23c7408da9721c1378a5f661aaa83
Author: Alexander Stein <alexander.stein@ew.tq-group.com>
Date:   Fri Jan 14 09:59:06 2022 +0100

    arm64: dts: freescale: Fix sound card model for MBa8Mx
    
    The audio codec connection on MBa8Mx is identical to MBa7 (imx7) and MBa6
    (imx6). Use the same sound card model as well.
    
    Fixes commit dfcd1b6f7620 ("arm64: dts: freescale: add initial device tree
    for TQMa8MQML with i.MX8MM")
    Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 1601033da2dd2052e0489137f7788a46a8fcd82f
Author: Mark Brown <broonie@kernel.org>
Date:   Fri Jan 28 19:24:43 2022 +0000

    ASoC: ops: Check for negative values before reading them
    
    The controls allow inputs to be specified as negative but our manipulating
    them into register fields need to be done on unsigned variables so the
    checks for negative numbers weren't taking effect properly. Do the checks
    for negative values on the variable in the ABI struct rather than on our
    local unsigned copy.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Link: https://lore.kernel.org/r/20220128192443.3504823-1-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4c38f8747c5769a272bc6557c2504d218f01914e
Merge: 4045daf0fa878 9f620684c1ef5
Author: Mark Brown <broonie@kernel.org>
Date:   Fri Jan 28 20:45:33 2022 +0000

    ASoC DPCM lockdep fixes
    
    Merge series from Takashi Iwai <tiwai@suse.de>:
    
    This is the revised patches for addressing ASoC lockdep warnings due
    to the recent DPCM locking refactoring.

commit 279eb8575fdaa92c314a54c0d583c65e26229107
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Mon Jan 24 21:55:02 2022 +0300

    EDAC/altera: Fix deferred probing
    
    The driver overrides the error codes returned by platform_get_irq() to
    -ENODEV for some strange reason, so if it returns -EPROBE_DEFER, the
    driver will fail the probe permanently instead of the deferred probing.
    Switch to propagating the proper error codes to platform driver code
    upwards.
    
      [ bp: Massage commit message. ]
    
    Fixes: 71bcada88b0f ("edac: altera: Add Altera SDRAM EDAC support")
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Acked-by: Dinh Nguyen <dinguyen@kernel.org>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220124185503.6720-2-s.shtylyov@omp.ru

commit b879f915bc48a18d4f4462729192435bb0f17052
Author: Mike Snitzer <snitzer@redhat.com>
Date:   Fri Jan 28 10:58:41 2022 -0500

    dm: properly fix redundant bio-based IO accounting
    
    Record the start_time for a bio but defer the starting block core's IO
    accounting until after IO is submitted using bio_start_io_acct_time().
    
    This approach avoids the need to mess around with any of the
    individual IO stats in response to a bio_split() that follows bio
    submission.
    
    Reported-by: Bud Brown <bubrown@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Cc: stable@vger.kernel.org
    Depends-on: e45c47d1f94e ("block: add bio_start_io_acct_time() to control start_time")
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Link: https://lore.kernel.org/r/20220128155841.39644-4-snitzer@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit f524d9c95fab54783d0038f7a3e8c014d5b56857
Author: Mike Snitzer <snitzer@redhat.com>
Date:   Fri Jan 28 10:58:40 2022 -0500

    dm: revert partial fix for redundant bio-based IO accounting
    
    Reverts a1e1cb72d9649 ("dm: fix redundant IO accounting for bios that
    need splitting") because it was too narrow in scope (only addressed
    redundant 'sectors[]' accounting and not ios, nsecs[], etc).
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Link: https://lore.kernel.org/r/20220128155841.39644-3-snitzer@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit e45c47d1f94e0cc7b6b079fdb4bcce2995e2adc4
Author: Mike Snitzer <snitzer@redhat.com>
Date:   Fri Jan 28 10:58:39 2022 -0500

    block: add bio_start_io_acct_time() to control start_time
    
    bio_start_io_acct_time() interface is like bio_start_io_acct() that
    allows start_time to be passed in. This gives drivers the ability to
    defer starting accounting until after IO is issued (but possibily not
    entirely due to bio splitting).
    
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Link: https://lore.kernel.org/r/20220128155841.39644-2-snitzer@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 169387e2aa291a4e3cb856053730fe99d6cec06f
Merge: 073819e0ff389 4db09593af0b0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 21:17:58 2022 +0200

    Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI fixes from James Bottomley:
     "Sixteen patches, mostly minor fixes and updates; however there are
      substantive driver bug fixes in pm8001, bnx2fc, zfcp, myrs and qedf"
    
    * tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: myrs: Fix crash in error case
      scsi: 53c700: Remove redundant assignment to pointer SCp
      scsi: ufs: Treat link loss as fatal error
      scsi: ufs: Use generic error code in ufshcd_set_dev_pwr_mode()
      scsi: bfa: Remove useless DMA-32 fallback configuration
      scsi: hisi_sas: Remove useless DMA-32 fallback configuration
      scsi: 3w-sas: Remove useless DMA-32 fallback configuration
      scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put()
      scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices
      scsi: pm8001: Fix bogus FW crash for maxcpus=1
      scsi: qedf: Change context reset messages to ratelimited
      scsi: qedf: Fix refcount issue when LOGO is received during TMF
      scsi: qedf: Add stag_work to all the vports
      scsi: ufs: ufshcd-pltfrm: Check the return value of devm_kstrdup()
      scsi: target: iscsi: Make sure the np under each tpg is unique
      scsi: elx: efct: Don't use GFP_KERNEL under spin lock

commit 073819e0ff389ee94dadd2d5340bfdc108ccddff
Merge: a7b4b0076b5c7 f5390cd0b43c2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 21:12:07 2022 +0200

    Merge tag 'efi-urgent-for-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi
    
    Pull EFI fixes from Ard Biesheuvel:
    
     - avoid UEFI v2.00+ runtime services on Apple Mac systems, as they have
       been reported to cause crashes, and most Macs claim to be EFI v1.10
       anyway
    
     - avoid a spurious boot time warning on arm64 systems with 64k pages
    
    * tag 'efi-urgent-for-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi:
      efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
      efi/libstub: arm64: Fix image check alignment at entry

commit 7f5056b9e7b71149bf11073f00a57fa1ac2921a9
Author: Vivek Goyal <vgoyal@redhat.com>
Date:   Wed Jan 26 15:35:14 2022 -0500

    security, lsm: dentry_init_security() Handle multi LSM registration
    
    A ceph user has reported that ceph is crashing with kernel NULL pointer
    dereference. Following is the backtrace.
    
    /proc/version: Linux version 5.16.2-arch1-1 (linux@archlinux) (gcc (GCC)
    11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP PREEMPT Thu, 20 Jan 2022
    16:18:29 +0000
    distro / arch: Arch Linux / x86_64
    SELinux is not enabled
    ceph cluster version: 16.2.7 (dd0603118f56ab514f133c8d2e3adfc983942503)
    
    relevant dmesg output:
    [   30.947129] BUG: kernel NULL pointer dereference, address:
    0000000000000000
    [   30.947206] #PF: supervisor read access in kernel mode
    [   30.947258] #PF: error_code(0x0000) - not-present page
    [   30.947310] PGD 0 P4D 0
    [   30.947342] Oops: 0000 [#1] PREEMPT SMP PTI
    [   30.947388] CPU: 5 PID: 778 Comm: touch Not tainted 5.16.2-arch1-1 #1
    86fbf2c313cc37a553d65deb81d98e9dcc2a3659
    [   30.947486] Hardware name: Gigabyte Technology Co., Ltd. B365M
    DS3H/B365M DS3H, BIOS F5 08/13/2019
    [   30.947569] RIP: 0010:strlen+0x0/0x20
    [   30.947616] Code: b6 07 38 d0 74 16 48 83 c7 01 84 c0 74 05 48 39 f7 75
    ec 31 c0 31 d2 89 d6 89 d7 c3 48 89 f8 31 d2 89 d6 89 d7 c3 0
    f 1f 40 00 <80> 3f 00 74 12 48 89 f8 48 83 c0 01 80 38 00 75 f7 48 29 f8 31
    ff
    [   30.947782] RSP: 0018:ffffa4ed80ffbbb8 EFLAGS: 00010246
    [   30.947836] RAX: 0000000000000000 RBX: ffffa4ed80ffbc60 RCX:
    0000000000000000
    [   30.947904] RDX: 0000000000000000 RSI: 0000000000000000 RDI:
    0000000000000000
    [   30.947971] RBP: ffff94b0d15c0ae0 R08: 0000000000000000 R09:
    0000000000000000
    [   30.948040] R10: 0000000000000000 R11: 0000000000000000 R12:
    0000000000000000
    [   30.948106] R13: 0000000000000001 R14: ffffa4ed80ffbc60 R15:
    0000000000000000
    [   30.948174] FS:  00007fc7520f0740(0000) GS:ffff94b7ced40000(0000)
    knlGS:0000000000000000
    [   30.948252] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [   30.948308] CR2: 0000000000000000 CR3: 0000000104a40001 CR4:
    00000000003706e0
    [   30.948376] Call Trace:
    [   30.948404]  <TASK>
    [   30.948431]  ceph_security_init_secctx+0x7b/0x240 [ceph
    49f9c4b9bf5be8760f19f1747e26da33920bce4b]
    [   30.948582]  ceph_atomic_open+0x51e/0x8a0 [ceph
    49f9c4b9bf5be8760f19f1747e26da33920bce4b]
    [   30.948708]  ? get_cached_acl+0x4d/0xa0
    [   30.948759]  path_openat+0x60d/0x1030
    [   30.948809]  do_filp_open+0xa5/0x150
    [   30.948859]  do_sys_openat2+0xc4/0x190
    [   30.948904]  __x64_sys_openat+0x53/0xa0
    [   30.948948]  do_syscall_64+0x5c/0x90
    [   30.948989]  ? exc_page_fault+0x72/0x180
    [   30.949034]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    [   30.949091] RIP: 0033:0x7fc7521e25bb
    [   30.950849] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00
    00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 0
    0 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 54 24 28 64 48 2b 14
    25
    
    Core of the problem is that ceph checks for return code from
    security_dentry_init_security() and if return code is 0, it assumes
    everything is fine and continues to call strlen(name), which crashes.
    
    Typically SELinux LSM returns 0 and sets name to "security.selinux" and
    it is not a problem. Or if selinux is not compiled in or disabled, it
    returns -EOPNOTSUP and ceph deals with it.
    
    But somehow in this configuration, 0 is being returned and "name" is
    not being initialized and that's creating the problem.
    
    Our suspicion is that BPF LSM is registering a hook for
    dentry_init_security() and returns hook default of 0.
    
    LSM_HOOK(int, 0, dentry_init_security, struct dentry *dentry,...)
    
    I have not been able to reproduce it just by doing CONFIG_BPF_LSM=y.
    Stephen has tested the patch though and confirms it solves the problem
    for him.
    
    dentry_init_security() is written in such a way that it expects only one
    LSM to register the hook. Atleast that's the expectation with current code.
    
    If another LSM returns a hook and returns default, it will simply return
    0 as of now and that will break ceph.
    
    Hence, suggestion is that change semantics of this hook a bit. If there
    are no LSMs or no LSM is taking ownership and initializing security context,
    then return -EOPNOTSUP. Also allow at max one LSM to initialize security
    context. This hook can't deal with multiple LSMs trying to init security
    context. This patch implements this new behavior.
    
    Reported-by: Stephen Muth <smuth4@gmail.com>
    Tested-by: Stephen Muth <smuth4@gmail.com>
    Suggested-by: Casey Schaufler <casey@schaufler-ca.com>
    Acked-by: Casey Schaufler <casey@schaufler-ca.com>
    Reviewed-by: Serge Hallyn <serge@hallyn.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Christian Brauner <brauner@kernel.org>
    Cc: Paul Moore <paul@paul-moore.com>
    Cc: <stable@vger.kernel.org> # 5.16.0
    Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Acked-by: Paul Moore <paul@paul-moore.com>
    Acked-by: Christian Brauner <brauner@kernel.org>
    Signed-off-by: James Morris <jmorris@namei.org>

commit a7b4b0076b5c76090b35c1eb8eebe308ce800b2d
Merge: df0001545b276 33569ef3c754a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 20:44:07 2022 +0200

    Merge tag 'pm-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull power management fixes from Rafael Wysocki:
     "These make the buffer handling in pm_show_wakelocks() more robust and
      drop an unused hibernation-related function.
    
      Specifics:
    
       - Make the buffer handling in pm_show_wakelocks() more robust by
         using sysfs_emit_at() in it to generate output (Greg
         Kroah-Hartman).
    
       - Drop register_nosave_region_late() which is not used (Amadeusz
         Sławiński)"
    
    * tag 'pm-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      PM: hibernate: Remove register_nosave_region_late()
      PM: wakeup: simplify the output logic of pm_show_wakelocks()

commit df0001545b2769e6aa33a45e26c00a4cdac48c29
Merge: 76fcbc9c7c57a 67ab5eb71b37b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 19:30:35 2022 +0200

    Merge tag 'trace-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pulltracing fixes from Steven Rostedt:
    
     - Limit mcount build time sorting to only those archs that we know it
       works for.
    
     - Fix memory leak in error path of histogram setup
    
     - Fix and clean up rel_loc array out of bounds issue
    
     - tools/rtla documentation fixes
    
     - Fix issues with histogram logic
    
    * tag 'trace-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      tracing: Don't inc err_log entry count if entry allocation fails
      tracing: Propagate is_signed to expression
      tracing: Fix smatch warning for do while check in event_hist_trigger_parse()
      tracing: Fix smatch warning for null glob in event_hist_trigger_parse()
      tools/tracing: Update Makefile to build rtla
      rtla: Make doc build optional
      tracing/perf: Avoid -Warray-bounds warning for __rel_loc macro
      tracing: Avoid -Warray-bounds warning for __rel_loc macro
      tracing/histogram: Fix a potential memory leak for kstrdup()
      ftrace: Have architectures opt-in for mcount build time sorting

commit c89e5eb7dcf1519e5e084ee82e0d29d4e751ddb7
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Jan 28 10:03:58 2022 +0100

    dt-bindings: interrupt-controller: sifive,plic: Group interrupt tuples
    
    To improve human readability and enable automatic validation, the tuples
    in "interrupts-extended" properties should be grouped using angle
    brackets.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/211705e74a2ce77de43d036c5dea032484119bf7.1643360419.git.geert@linux-m68k.org

commit 8fbc16d26d3a1ed3d80553b773be29408750987b
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Jan 28 10:03:57 2022 +0100

    dt-bindings: interrupt-controller: sifive,plic: Fix number of interrupts
    
    The number of interrupts lacks an upper bound, thus assuming one,
    causing properly grouped "interrupts-extended" properties to be flagged
    as an error by "make dtbs_check".
    
    Fix this by adding the missing "maxItems", using the architectural
    maximum of 15872 interrupts.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/f73a0aead89e1426b146c4c64f797aa035868bf0.1643360419.git.geert@linux-m68k.org

commit 76fcbc9c7c57a5d44e7ca493d8f2f6eba3964f29
Merge: a773abf72eb0c f9d87929d451d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 19:25:24 2022 +0200

    Merge branch 'ucount-rlimit-fixes-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
    
    Pull ucount rlimit fix from Eric Biederman.
    
    Make sure the ucounts have a reference to the user namespace it refers
    to, so that users that themselves don't carry such a reference around
    can safely use the ucount functions.
    
    * 'ucount-rlimit-fixes-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace:
      ucount:  Make get_ucount a safe get_user replacement

commit e8cc7a5d1ad2d44e7f43664ef6a61e31c0545a5b
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Wed Jan 26 13:32:05 2022 +0100

    dt-bindings: irqchip: renesas-irqc: Add R-Car V3U support
    
    Document support for the Interrupt Controller for External Devices
    (INT-EC) in the Renesas R-Car V3U (r8a779a0) SoC.
    
    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Tested-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/85b246cc0792663c72c1bb12a8576bd23d2299d3.1643200256.git.geert+renesas@glider.be

commit a773abf72eb0cac008743891068ca6edecc44683
Merge: 56a14c69ae5e0 da123016ca8cb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 19:19:22 2022 +0200

    Merge tag 'rcu-urgent.2022.01.26a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
    
    Pull RCU fix from Paul McKenney:
     "This fixes a brown-paper-bag bug in RCU tasks that causes things like
      BPF and ftrace to fail miserably on systems with non-power-of-two
      numbers of CPUs.
    
      It fixes a math error added in 7a30871b6a27 ("rcu-tasks: Introduce
      ->percpu_enqueue_shift for dynamic queue selection') during the v5.17
      merge window. This commit works correctly only on systems with a
      power-of-two number of CPUs, which just so happens to be the kind that
      rcutorture always uses by default.
    
      This pull request fixes the math so that things also work on systems
      that don't happen to have a power-of-two number of CPUs"
    
    * tag 'rcu-urgent.2022.01.26a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu:
      rcu-tasks: Fix computation of CPU-to-list shift counts

commit 56a14c69ae5e0a1661e4b54ebf2fbf6e7410a9ec
Merge: 3cd7cd8a62e6f 9ff5549b1d1d3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 19:06:11 2022 +0200

    Merge tag 'hyperv-fixes-signed-20220128' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux
    
    Pull hyperv fixes from Wei Liu:
    
     - Fix screen resolution for hyperv framebuffer (Michael Kelley)
    
     - Fix packet header accounting for balloon driver (Yanming Liu)
    
    * tag 'hyperv-fixes-signed-20220128' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux:
      video: hyperv_fb: Fix validation of screen resolution
      Drivers: hv: balloon: account for vmbus packet header in max_pkt_size

commit 3cd7cd8a62e6f4b81e8429db7afcb11cc155ea3c
Merge: e0152705e4630 17179d0068b20
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 19:00:26 2022 +0200

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm fixes from Paolo Bonzini:
     "Two larger x86 series:
    
       - Redo incorrect fix for SEV/SMAP erratum
    
       - Windows 11 Hyper-V workaround
    
      Other x86 changes:
    
       - Various x86 cleanups
    
       - Re-enable access_tracking_perf_test
    
       - Fix for #GP handling on SVM
    
       - Fix for CPUID leaf 0Dh in KVM_GET_SUPPORTED_CPUID
    
       - Fix for ICEBP in interrupt shadow
    
       - Avoid false-positive RCU splat
    
       - Enable Enlightened MSR-Bitmap support for real
    
      ARM:
    
       - Correctly update the shadow register on exception injection when
         running in nVHE mode
    
       - Correctly use the mm_ops indirection when performing cache
         invalidation from the page-table walker
    
       - Restrict the vgic-v3 workaround for SEIS to the two known broken
         implementations
    
      Generic code changes:
    
       - Dead code cleanup"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (43 commits)
      KVM: eventfd: Fix false positive RCU usage warning
      KVM: nVMX: Allow VMREAD when Enlightened VMCS is in use
      KVM: nVMX: Implement evmcs_field_offset() suitable for handle_vmread()
      KVM: nVMX: Rename vmcs_to_field_offset{,_table}
      KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER
      KVM: nVMX: Also filter MSR_IA32_VMX_TRUE_PINBASED_CTLS when eVMCS
      selftests: kvm: check dynamic bits against KVM_X86_XCOMP_GUEST_SUPP
      KVM: x86: add system attribute to retrieve full set of supported xsave states
      KVM: x86: Add a helper to retrieve userspace address from kvm_device_attr
      selftests: kvm: move vm_xsave_req_perm call to amx_test
      KVM: x86: Sync the states size with the XCR0/IA32_XSS at, any time
      KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
      KVM: x86: Keep MSR_IA32_XSS unchanged for INIT
      KVM: x86: Free kvm_cpuid_entry2 array on post-KVM_RUN KVM_SET_CPUID{,2}
      KVM: nVMX: WARN on any attempt to allocate shadow VMCS for vmcs02
      KVM: selftests: Don't skip L2's VMCALL in SMM test for SVM guest
      KVM: x86: Check .flags in kvm_cpuid_check_equal() too
      KVM: x86: Forcibly leave nested virt when SMM state is toggled
      KVM: SVM: drop unnecessary code in svm_hv_vmcb_dirty_nested_enlightenments()
      KVM: SVM: hyper-v: Enable Enlightened MSR-Bitmap support for real
      ...

commit e0152705e4630b4a6ae8eb716aa44ed5a90054ea
Merge: 7eb3625489813 fa62f39dc7e25
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 18:53:45 2022 +0200

    Merge tag 'mips-fixes-5.17_1' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
    
    Pull MIPS build fix from Thomas Bogendoerfer:
     "Fix for allmodconfig build"
    
    * tag 'mips-fixes-5.17_1' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux:
      MIPS: Fix build error due to PTR used in more places

commit 7eb36254898131ef2feed7629ae93bc6a2c56d18
Merge: 8157f4707360a 663d34c8df987
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 18:50:05 2022 +0200

    Merge tag 's390-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
    
    Pull s390 fixes from Vasily Gorbik:
    
     - Fix loading of modules with lots of relocations and add a regression
       test for it.
    
     - Fix machine check handling for vector validity and guarded storage
       validity failures in KVM guests.
    
     - Fix hypervisor performance data to include z/VM guests with access
       control group set.
    
     - Fix z900 build problem in uaccess code.
    
     - Update defconfigs.
    
    * tag 's390-5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
      s390/hypfs: include z/VM guests with access control group set
      s390: update defconfigs
      s390/module: test loading modules with a lot of relocations
      s390/module: fix loading modules with a lot of relocations
      s390/uaccess: fix compile error
      s390/nmi: handle vector validity failures for KVM guests
      s390/nmi: handle guarded storage validity failures for KVM guests

commit 4028bccb003cf67e46632dee7f97ddc5d7b6e685
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Wed Jan 19 04:28:09 2022 -0500

    IB/rdmavt: Validate remote_addr during loopback atomic tests
    
    The rdma-core test suite sends an unaligned remote address and expects a
    failure.
    
    ERROR: test_atomic_non_aligned_addr (tests.test_atomic.AtomicTest)
    
    The qib/hfi1 rc handling validates properly, but the test has the client
    and server on the same system.
    
    The loopback of these operations is a distinct code path.
    
    Fix by syntaxing the proposed remote address in the loopback code path.
    
    Fixes: 15703461533a ("IB/{hfi1, qib, rdmavt}: Move ruc_loopback to rdmavt")
    Link: https://lore.kernel.org/r/1642584489-141005-1-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit b856101a1774b5f1c8c99e8dfdef802856520732
Author: Mark Zhang <markzhang@nvidia.com>
Date:   Wed Jan 19 10:37:55 2022 +0200

    IB/cm: Release previously acquired reference counter in the cm_id_priv
    
    In failure flow, the reference counter acquired was not released,
    and the following error was reported:
    
      drivers/infiniband/core/cm.c:3373 cm_lap_handler() warn: inconsistent
                            refcounting 'cm_id_priv->refcount.refs.counter':
    
    Fixes: 7345201c3963 ("IB/cm: Improve the calling of cm_init_av_for_lap and cm_init_av_by_path")
    Link: https://lore.kernel.org/r/7615f23bbb5c5b66d03f6fa13e1c99d51dae6916.1642581448.git.leonro@nvidia.com
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Mark Zhang <markzhang@nvidia.com>
    Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 8157f4707360a17027538fa43b1b89b534c65eb9
Merge: f6a26318e3148 4584a768f22b7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 18:36:42 2022 +0200

    Merge tag 'ceph-for-5.17-rc2' of git://github.com/ceph/ceph-client
    
    Pull ceph fixes from Ilya Dryomov:
     "A ZERO_SIZE_PTR dereference fix from Xiubo and two fixes for async
      creates interacting with pool namespace-constrained OSD permissions
      from Jeff (marked for stable)"
    
    * tag 'ceph-for-5.17-rc2' of git://github.com/ceph/ceph-client:
      ceph: set pool_ns in new inode layout for async creates
      ceph: properly put ceph_string reference after async create attempt
      ceph: put the requests/sessions when it fails to alloc memory

commit 483529f3209f56d4c7a465d045278a2546ae7ed9
Author: David Howells <dhowells@redhat.com>
Date:   Thu Jan 27 16:02:34 2022 +0000

    Fix a warning about a malformed kernel doc comment in cifs
    
    Fix by removing the extra asterisk.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Rohith Surabattula <rohiths@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 297ae1eb23b04c5a46111ab53c8d0f69af43f402
Author: James Morse <james.morse@arm.com>
Date:   Tue Jan 25 15:40:40 2022 +0000

    arm64: cpufeature: List early Cortex-A510 parts as having broken dbm
    
    Versions of Cortex-A510 before r0p3 are affected by a hardware erratum
    where the hardware update of the dirty bit is not correctly ordered.
    
    Add these cpus to the cpu_has_broken_dbm list.
    
    Signed-off-by: James Morse <james.morse@arm.com>
    Link: https://lore.kernel.org/r/20220125154040.549272-3-james.morse@arm.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit f6a26318e3148289717b0f39ee976f9d95a93f4d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 10:00:29 2022 +0200

    ocfs2: fix subdirectory registration with register_sysctl()
    
    The kernel test robot reports that commit c42ff46f97c1 ("ocfs2: simplify
    subdirectory registration with register_sysctl()") is broken, and
    results in kernel warning messages like
    
      sysctl table check failed: fs/ocfs2/nm Not a file
      sysctl table check failed: fs/ocfs2/nm No proc_handler
      sysctl table check failed: fs/ocfs2/nm bogus .mode 0555
    
    and in fact this was already reported back in linux-next, but nobody
    seems to have reacted to that report.  Possibly that original report
    only ever made it to the lkp list.
    
    The problem seems to be that the simplification didn't actually go far
    enough, and should have converted the whole directory path to the final
    sysctl file, rather than just the two first components.
    
    So take that last step.
    
    Fixes: c42ff46f97c1 ("ocfs2: simplify subdirectory registration with register_sysctl()")
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Link: https://lore.kernel.org/all/20220128065310.GF8421@xsang-OptiPlex-9020/
    Link: https://lists.01.org/hyperkitty/list/lkp@lists.01.org/thread/KQ2F6TPJWMDVEXJM4WTUC4DU3EH3YJVT/
    Tested-by: Jan Kara <jack@suse.cz>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit df20597044e59cd383135b3d91c5b131dc333969
Merge: 9ae279ecabe3e 708e8af4924ec
Author: Catalin Marinas <catalin.marinas@arm.com>
Date:   Fri Jan 28 16:14:06 2022 +0000

    Merge tag 'trbe-cortex-a510-errata' of gitolite.kernel.org:pub/scm/linux/kernel/git/coresight/linux into for-next/fixes
    
    coresight: trbe: Workaround Cortex-A510 erratas
    
    This pull request is providing arm64 definitions to support
    TRBE Cortex-A510 erratas.
    
    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
    
    * tag 'trbe-cortex-a510-errata' of gitolite.kernel.org:pub/scm/linux/kernel/git/coresight/linux:
      arm64: errata: Add detection for TRBE trace data corruption
      arm64: errata: Add detection for TRBE invalid prohibited states
      arm64: errata: Add detection for TRBE ignored system register writes
      arm64: Add Cortex-A510 CPU part definition

commit 4045daf0fa87846a27f56329fddad2deeb5ca354
Author: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Date:   Wed Jan 26 12:03:25 2022 +0200

    ASoC: rt5682: Fix deadlock on resume
    
    On resume from suspend the following chain of events can happen:
    A rt5682_resume() -> mod_delayed_work() for jack_detect_work
    B DAPM sequence starts ( DAPM is locked now)
    
    A1. rt5682_jack_detect_handler() scheduled
     - Takes both jdet_mutex and calibrate_mutex
     - Calls in to rt5682_headset_detect() which tries to take DAPM lock, it
       starts to wait for it as B path took it already.
    B1. DAPM sequence reaches the "HP Amp", rt5682_hp_event() tries to take
        the jdet_mutex, but it is locked in A1, so it waits.
    
    Deadlock.
    
    To solve the deadlock, drop the jdet_mutex, use the jack_detect_work to do
    the jack removal handling, move the dapm lock up one level to protect the
    most of the rt5682_jack_detect_handler(), but not the jack reporting as it
    might trigger a DAPM sequence.
    The rt5682_headset_detect() can be changed to static as well.
    
    Fixes: 8deb34a90f063 ("ASoC: rt5682: fix the wrong jack type detected")
    Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
    Link: https://lore.kernel.org/r/20220126100325.16513-1-peter.ujfalusi@linux.intel.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 06feec6005c9d9500cd286ec440aabf8b2ddd94d
Author: Dmitry Osipenko <digetx@gmail.com>
Date:   Wed Jan 12 22:50:39 2022 +0300

    ASoC: hdmi-codec: Fix OOB memory accesses
    
    Correct size of iec_status array by changing it to the size of status
    array of the struct snd_aes_iec958. This fixes out-of-bounds slab
    read accesses made by memcpy() of the hdmi-codec driver. This problem
    is reported by KASAN.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
    Link: https://lore.kernel.org/r/20220112195039.1329-1-digetx@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 9f620684c1ef5a002b6622ecc7b5818e81252f48
Author: Takashi Iwai <tiwai@suse.de>
Date:   Wed Jan 19 16:52:49 2022 +0100

    ASoC: soc-pcm: Move debugfs removal out of spinlock
    
    The recent fix for DPCM locking also covered the loop in
    dpcm_be_disconnect() with the FE stream lock.  This caused an
    unexpected side effect, thought: calling debugfs_remove_recursive() in
    the spinlock may lead to lockdep splats as the code there assumes the
    SOFTIRQ-safe context.
    
    For avoiding the problem, this patch changes the disconnection
    procedure to two phases: at first, the matching entries are removed
    from the linked list, then the resources are freed outside the lock.
    
    Fixes: b7898396f4bb ("ASoC: soc-pcm: Fix and cleanup DPCM locking")
    Reported-and-tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Link: https://lore.kernel.org/r/20220119155249.26754-3-tiwai@suse.de
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3c75c0ea5da749bd1efebd1387f2e5011b8c7d78
Author: Takashi Iwai <tiwai@suse.de>
Date:   Wed Jan 19 16:52:48 2022 +0100

    ASoC: soc-pcm: Fix DPCM lockdep warning due to nested stream locks
    
    The recent change for DPCM locking caused spurious lockdep warnings.
    Actually the warnings are false-positive, as those are triggered due
    to the nested stream locks for FE and BE.  Since both locks belong to
    the same lock class, lockdep sees it as if a deadlock.
    
    For fixing this, we need to take PCM stream locks for BE with the
    nested lock primitives.  Since currently snd_pcm_stream_lock*() helper
    assumes only the top-level single locking, a new helper function
    snd_pcm_stream_lock_irqsave_nested() is defined for a single-depth
    nested lock, which is now used in the BE DAI trigger that is always
    performed inside a FE stream lock.
    
    Fixes: b2ae80663008 ("ASoC: soc-pcm: serialize BE triggers")
    Reported-and-tested-by: Hans de Goede <hdegoede@redhat.com>
    Reported-and-tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Link: https://lore.kernel.org/r/73018f3c-9769-72ea-0325-b3f8e2381e30@redhat.com
    Link: https://lore.kernel.org/alsa-devel/9a0abddd-49e9-872d-2f00-a1697340f786@samsung.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>
    Link: https://lore.kernel.org/r/20220119155249.26754-2-tiwai@suse.de
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4897e722b54f10e2e96c3eeca260caa7a8b0dbff
Merge: c2b19fd753114 29044dae2e746
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 17:51:31 2022 +0200

    Merge tag 'fsnotify_for_v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
    
    Pull fsnotify fixes from Jan Kara:
     "Fixes for userspace breakage caused by fsnotify changes ~3 years ago
      and one fanotify cleanup"
    
    * tag 'fsnotify_for_v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
      fsnotify: fix fsnotify hooks in pseudo filesystems
      fsnotify: invalidate dcache before IN_DELETE event
      fanotify: remove variable set but not used

commit a75badebfdc0b3823054bedf112edb54d6357c75
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 18 12:11:04 2022 +0300

    RDMA/siw: Fix refcounting leak in siw_create_qp()
    
    The atomic_inc() needs to be paired with an atomic_dec() on the error
    path.
    
    Fixes: 514aee660df4 ("RDMA: Globally allocate and release QP memory")
    Link: https://lore.kernel.org/r/20220118091104.GA11671@kili
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Reviewed-by: Bernard Metzler <bmt@zurich.ibm.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 36e8169ec973359f671f9ec7213547059cae972e
Author: Leon Romanovsky <leon@kernel.org>
Date:   Tue Jan 18 09:35:01 2022 +0200

    RDMA/ucma: Protect mc during concurrent multicast leaves
    
    Partially revert the commit mentioned in the Fixes line to make sure that
    allocation and erasing multicast struct are locked.
    
      BUG: KASAN: use-after-free in ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline]
      BUG: KASAN: use-after-free in ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579
      Read of size 8 at addr ffff88801bb74b00 by task syz-executor.1/25529
      CPU: 0 PID: 25529 Comm: syz-executor.1 Not tainted 5.16.0-rc7-syzkaller #0
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
      Call Trace:
       __dump_stack lib/dump_stack.c:88 [inline]
       dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
       print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247
       __kasan_report mm/kasan/report.c:433 [inline]
       kasan_report.cold+0x83/0xdf mm/kasan/report.c:450
       ucma_cleanup_multicast drivers/infiniband/core/ucma.c:491 [inline]
       ucma_destroy_private_ctx+0x914/0xb70 drivers/infiniband/core/ucma.c:579
       ucma_destroy_id+0x1e6/0x280 drivers/infiniband/core/ucma.c:614
       ucma_write+0x25c/0x350 drivers/infiniband/core/ucma.c:1732
       vfs_write+0x28e/0xae0 fs/read_write.c:588
       ksys_write+0x1ee/0x250 fs/read_write.c:643
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Currently the xarray search can touch a concurrently freeing mc as the
    xa_for_each() is not surrounded by any lock. Rather than hold the lock for
    a full scan hold it only for the effected items, which is usually an empty
    list.
    
    Fixes: 95fe51096b7a ("RDMA/ucma: Remove mc_list and rely on xarray")
    Link: https://lore.kernel.org/r/1cda5fabb1081e8d16e39a48d3a4f8160cea88b8.1642491047.git.leonro@nvidia.com
    Reported-by: syzbot+e3f96c43d19782dd14a7@syzkaller.appspotmail.com
    Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
    Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
    Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit d9e410ebbed9d091b97bdf45b8a3792e2878dc48
Author: Maor Gottlieb <maorg@nvidia.com>
Date:   Tue Jan 18 09:35:00 2022 +0200

    RDMA/cma: Use correct address when leaving multicast group
    
    In RoCE we should use cma_iboe_set_mgid() and not cma_set_mgid to generate
    the mgid, otherwise we will generate an IGMP for an incorrect address.
    
    Fixes: b5de0c60cc30 ("RDMA/cma: Fix use after free race in roce multicast join")
    Link: https://lore.kernel.org/r/913bc6783fd7a95fe71ad9454e01653ee6fb4a9a.1642491047.git.leonro@nvidia.com
    Signed-off-by: Maor Gottlieb <maorg@nvidia.com>
    Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit c2b19fd753114f8e11d313389ee1252dc3bb70d7
Merge: 145d9b498fc82 9daf0a4d32d60
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 17:19:49 2022 +0200

    Merge tag 'fs_for_v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
    
    Pull udf and quota fixes from Jan Kara:
     "Fixes for crashes in UDF when inode expansion fails and one quota
      cleanup"
    
    * tag 'fs_for_v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
      quota: cleanup double word in comment
      udf: Restore i_lenAlloc when inode expansion fails
      udf: Fix NULL ptr deref when converting from inline format

commit d5081bf5dcfb1cb83fb538708b0ac07a10a79cc4
Author: Dave Jiang <dave.jiang@intel.com>
Date:   Thu Jan 27 13:31:12 2022 -0700

    ntb: intel: fix port config status offset for SPR
    
    The field offset for port configuration status on SPR has been changed to
    bit 14 from ICX where it resides at bit 12. By chance link status detection
    continued to work on SPR. This is due to bit 12 being a configuration bit
    which is in sync with the status bit. Fix this by checking for a SPR device
    and checking correct status bit.
    
    Fixes: 26bfe3d0b227 ("ntb: intel: Add Icelake (gen4) support for Intel NTB")
    Tested-by: Jerry Dai <jerry.dai@intel.com>
    Signed-off-by: Dave Jiang <dave.jiang@intel.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 6449520391dfc3d2cef134f11a91251a054ff7d0
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Fri Jan 28 22:15:50 2022 +0800

    net: stmmac: properly handle with runtime pm in stmmac_dvr_remove()
    
    There are two issues with runtime pm handling in stmmac_dvr_remove():
    
    1. the mac is runtime suspended before stopping dma and rx/tx. We
    need to ensure the device is properly resumed back.
    
    2. the stmmaceth clk enable/disable isn't balanced in both exit and
    error handling code path. Take the exit code path for example, when we
    unbind the driver or rmmod the driver module, the mac is runtime
    suspended as said above, so the stmmaceth clk is disabled, but
            stmmac_dvr_remove()
              stmmac_remove_config_dt()
                clk_disable_unprepare()
    CCF will complain this time. The error handling code path suffers
    from the similar situtaion.
    
    Here are kernel warnings in error handling code path on Allwinner D1
    platform:
    
    [    1.604695] ------------[ cut here ]------------
    [    1.609328] bus-emac already disabled
    [    1.613015] WARNING: CPU: 0 PID: 38 at drivers/clk/clk.c:952 clk_core_disable+0xcc/0xec
    [    1.621039] CPU: 0 PID: 38 Comm: kworker/u2:1 Not tainted 5.14.0-rc4#1
    [    1.627653] Hardware name: Allwinner D1 NeZha (DT)
    [    1.632443] Workqueue: events_unbound deferred_probe_work_func
    [    1.638286] epc : clk_core_disable+0xcc/0xec
    [    1.642561]  ra : clk_core_disable+0xcc/0xec
    [    1.646835] epc : ffffffff8023c2ec ra : ffffffff8023c2ec sp : ffffffd00411bb10
    [    1.654054]  gp : ffffffff80ec9988 tp : ffffffe00143a800 t0 : ffffffff80ed6a6f
    [    1.661272]  t1 : ffffffff80ed6a60 t2 : 0000000000000000 s0 : ffffffe001509e00
    [    1.668489]  s1 : 0000000000000001 a0 : 0000000000000019 a1 : ffffffff80e80bd8
    [    1.675707]  a2 : 00000000ffffefff a3 : 00000000000000f4 a4 : 0000000000000002
    [    1.682924]  a5 : 0000000000000001 a6 : 0000000000000030 a7 : 00000000028f5c29
    [    1.690141]  s2 : 0000000000000800 s3 : ffffffe001375000 s4 : ffffffe01fdf7a80
    [    1.697358]  s5 : ffffffe001375010 s6 : ffffffff8001fc10 s7 : ffffffffffffffff
    [    1.704577]  s8 : 0000000000000001 s9 : ffffffff80ecb248 s10: ffffffe001b80000
    [    1.711794]  s11: ffffffe001b80760 t3 : 0000000000000062 t4 : ffffffffffffffff
    [    1.719012]  t5 : ffffffff80e0f6d8 t6 : ffffffd00411b8f0
    [    1.724321] status: 8000000201800100 badaddr: 0000000000000000 cause: 0000000000000003
    [    1.732233] [<ffffffff8023c2ec>] clk_core_disable+0xcc/0xec
    [    1.737810] [<ffffffff80240430>] clk_disable+0x38/0x78
    [    1.742956] [<ffffffff8001fc0c>] worker_thread+0x1a8/0x4d8
    [    1.748451] [<ffffffff8031a500>] stmmac_remove_config_dt+0x1c/0x4c
    [    1.754646] [<ffffffff8031c8ec>] sun8i_dwmac_probe+0x378/0x82c
    [    1.760484] [<ffffffff8001fc0c>] worker_thread+0x1a8/0x4d8
    [    1.765975] [<ffffffff8029a6c8>] platform_probe+0x64/0xf0
    [    1.771382] [<ffffffff8029833c>] really_probe.part.0+0x8c/0x30c
    [    1.777305] [<ffffffff8029865c>] __driver_probe_device+0xa0/0x148
    [    1.783402] [<ffffffff8029873c>] driver_probe_device+0x38/0x138
    [    1.789324] [<ffffffff802989cc>] __device_attach_driver+0xd0/0x170
    [    1.795508] [<ffffffff802988f8>] __driver_attach_async_helper+0xbc/0xc0
    [    1.802125] [<ffffffff802965ac>] bus_for_each_drv+0x68/0xb4
    [    1.807701] [<ffffffff80298d1c>] __device_attach+0xd8/0x184
    [    1.813277] [<ffffffff802967b0>] bus_probe_device+0x98/0xbc
    [    1.818852] [<ffffffff80297904>] deferred_probe_work_func+0x90/0xd4
    [    1.825122] [<ffffffff8001f8b8>] process_one_work+0x1e4/0x390
    [    1.830872] [<ffffffff8001fd80>] worker_thread+0x31c/0x4d8
    [    1.836362] [<ffffffff80026bf4>] kthreadd+0x94/0x188
    [    1.841335] [<ffffffff80026bf4>] kthreadd+0x94/0x188
    [    1.846304] [<ffffffff8001fa60>] process_one_work+0x38c/0x390
    [    1.852054] [<ffffffff80026564>] kthread+0x124/0x160
    [    1.857021] [<ffffffff8002643c>] set_kthread_struct+0x5c/0x60
    [    1.862770] [<ffffffff80001f08>] ret_from_syscall_rejected+0x8/0xc
    [    1.868956] ---[ end trace 8d5c6046255f84a0 ]---
    [    1.873675] ------------[ cut here ]------------
    [    1.878366] bus-emac already unprepared
    [    1.882378] WARNING: CPU: 0 PID: 38 at drivers/clk/clk.c:810 clk_core_unprepare+0xe4/0x168
    [    1.890673] CPU: 0 PID: 38 Comm: kworker/u2:1 Tainted: G        W    5.14.0-rc4 #1
    [    1.898674] Hardware name: Allwinner D1 NeZha (DT)
    [    1.903464] Workqueue: events_unbound deferred_probe_work_func
    [    1.909305] epc : clk_core_unprepare+0xe4/0x168
    [    1.913840]  ra : clk_core_unprepare+0xe4/0x168
    [    1.918375] epc : ffffffff8023d6cc ra : ffffffff8023d6cc sp : ffffffd00411bb10
    [    1.925593]  gp : ffffffff80ec9988 tp : ffffffe00143a800 t0 : 0000000000000002
    [    1.932811]  t1 : ffffffe01f743be0 t2 : 0000000000000040 s0 : ffffffe001509e00
    [    1.940029]  s1 : 0000000000000001 a0 : 000000000000001b a1 : ffffffe00143a800
    [    1.947246]  a2 : 0000000000000000 a3 : 00000000000000f4 a4 : 0000000000000001
    [    1.954463]  a5 : 0000000000000000 a6 : 0000000005fce2a5 a7 : 0000000000000001
    [    1.961680]  s2 : 0000000000000800 s3 : ffffffff80afeb90 s4 : ffffffe01fdf7a80
    [    1.968898]  s5 : ffffffe001375010 s6 : ffffffff8001fc10 s7 : ffffffffffffffff
    [    1.976115]  s8 : 0000000000000001 s9 : ffffffff80ecb248 s10: ffffffe001b80000
    [    1.983333]  s11: ffffffe001b80760 t3 : ffffffff80b39120 t4 : 0000000000000001
    [    1.990550]  t5 : 0000000000000000 t6 : ffffffe001600002
    [    1.995859] status: 8000000201800120 badaddr: 0000000000000000 cause: 0000000000000003
    [    2.003771] [<ffffffff8023d6cc>] clk_core_unprepare+0xe4/0x168
    [    2.009609] [<ffffffff802403a0>] clk_unprepare+0x24/0x3c
    [    2.014929] [<ffffffff8031a508>] stmmac_remove_config_dt+0x24/0x4c
    [    2.021125] [<ffffffff8031c8ec>] sun8i_dwmac_probe+0x378/0x82c
    [    2.026965] [<ffffffff8001fc0c>] worker_thread+0x1a8/0x4d8
    [    2.032463] [<ffffffff8029a6c8>] platform_probe+0x64/0xf0
    [    2.037871] [<ffffffff8029833c>] really_probe.part.0+0x8c/0x30c
    [    2.043795] [<ffffffff8029865c>] __driver_probe_device+0xa0/0x148
    [    2.049892] [<ffffffff8029873c>] driver_probe_device+0x38/0x138
    [    2.055815] [<ffffffff802989cc>] __device_attach_driver+0xd0/0x170
    [    2.061999] [<ffffffff802988f8>] __driver_attach_async_helper+0xbc/0xc0
    [    2.068616] [<ffffffff802965ac>] bus_for_each_drv+0x68/0xb4
    [    2.074193] [<ffffffff80298d1c>] __device_attach+0xd8/0x184
    [    2.079769] [<ffffffff802967b0>] bus_probe_device+0x98/0xbc
    [    2.085345] [<ffffffff80297904>] deferred_probe_work_func+0x90/0xd4
    [    2.091616] [<ffffffff8001f8b8>] process_one_work+0x1e4/0x390
    [    2.097367] [<ffffffff8001fd80>] worker_thread+0x31c/0x4d8
    [    2.102858] [<ffffffff80026bf4>] kthreadd+0x94/0x188
    [    2.107830] [<ffffffff80026bf4>] kthreadd+0x94/0x188
    [    2.112800] [<ffffffff8001fa60>] process_one_work+0x38c/0x390
    [    2.118551] [<ffffffff80026564>] kthread+0x124/0x160
    [    2.123520] [<ffffffff8002643c>] set_kthread_struct+0x5c/0x60
    [    2.129268] [<ffffffff80001f08>] ret_from_syscall_rejected+0x8/0xc
    [    2.135455] ---[ end trace 8d5c6046255f84a1 ]---
    
    Fixes: 5ec55823438e ("net: stmmac: add clocks management for gmac driver")
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e5cce44aff3be9ad2cd52f63f35edbd706181d50
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Sat Jan 15 18:02:36 2022 -0500

    IB/hfi1: Fix tstats alloc and dealloc
    
    The tstats allocation is done in the accelerated ndo_init function but the
    allocation is not tested to succeed.
    
    The deallocation is not done in the accelerated ndo_uninit function.
    
    Resolve issues by testing for an allocation failure and adding the
    free_percpu in the uninit function.
    
    Fixes: aa0616a9bd52 ("IB/hfi1: switch to core handling of rx/tx byte/packet counters")
    Link: https://lore.kernel.org/r/1642287756-182313-5-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 5f8f55b92edd621f056bdf09e572092849fabd83
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Sat Jan 15 18:02:35 2022 -0500

    IB/hfi1: Fix AIP early init panic
    
    An early failure in hfi1_ipoib_setup_rn() can lead to the following panic:
    
      BUG: unable to handle kernel NULL pointer dereference at 00000000000001b0
      PGD 0 P4D 0
      Oops: 0002 [#1] SMP NOPTI
      Workqueue: events work_for_cpu_fn
      RIP: 0010:try_to_grab_pending+0x2b/0x140
      Code: 1f 44 00 00 41 55 41 54 55 48 89 d5 53 48 89 fb 9c 58 0f 1f 44 00 00 48 89 c2 fa 66 0f 1f 44 00 00 48 89 55 00 40 84 f6 75 77 <f0> 48 0f ba 2b 00 72 09 31 c0 5b 5d 41 5c 41 5d c3 48 89 df e8 6c
      RSP: 0018:ffffb6b3cf7cfa48 EFLAGS: 00010046
      RAX: 0000000000000246 RBX: 00000000000001b0 RCX: 0000000000000000
      RDX: 0000000000000246 RSI: 0000000000000000 RDI: 00000000000001b0
      RBP: ffffb6b3cf7cfa70 R08: 0000000000000f09 R09: 0000000000000001
      R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
      R13: ffffb6b3cf7cfa90 R14: ffffffff9b2fbfc0 R15: ffff8a4fdf244690
      FS:  0000000000000000(0000) GS:ffff8a527f400000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 00000000000001b0 CR3: 00000017e2410003 CR4: 00000000007706f0
      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
      PKRU: 55555554
      Call Trace:
       __cancel_work_timer+0x42/0x190
       ? dev_printk_emit+0x4e/0x70
       iowait_cancel_work+0x15/0x30 [hfi1]
       hfi1_ipoib_txreq_deinit+0x5a/0x220 [hfi1]
       ? dev_err+0x6c/0x90
       hfi1_ipoib_netdev_dtor+0x15/0x30 [hfi1]
       hfi1_ipoib_setup_rn+0x10e/0x150 [hfi1]
       rdma_init_netdev+0x5a/0x80 [ib_core]
       ? hfi1_ipoib_free_rdma_netdev+0x20/0x20 [hfi1]
       ipoib_intf_init+0x6c/0x350 [ib_ipoib]
       ipoib_intf_alloc+0x5c/0xc0 [ib_ipoib]
       ipoib_add_one+0xbe/0x300 [ib_ipoib]
       add_client_context+0x12c/0x1a0 [ib_core]
       enable_device_and_get+0xdc/0x1d0 [ib_core]
       ib_register_device+0x572/0x6b0 [ib_core]
       rvt_register_device+0x11b/0x220 [rdmavt]
       hfi1_register_ib_device+0x6b4/0x770 [hfi1]
       do_init_one.isra.20+0x3e3/0x680 [hfi1]
       local_pci_probe+0x41/0x90
       work_for_cpu_fn+0x16/0x20
       process_one_work+0x1a7/0x360
       ? create_worker+0x1a0/0x1a0
       worker_thread+0x1cf/0x390
       ? create_worker+0x1a0/0x1a0
       kthread+0x116/0x130
       ? kthread_flush_work_fn+0x10/0x10
       ret_from_fork+0x1f/0x40
    
    The panic happens in hfi1_ipoib_txreq_deinit() because there is a NULL
    deref when hfi1_ipoib_netdev_dtor() is called in this error case.
    
    hfi1_ipoib_txreq_init() and hfi1_ipoib_rxq_init() are self unwinding so
    fix by adjusting the error paths accordingly.
    
    Other changes:
    - hfi1_ipoib_free_rdma_netdev() is deleted including the free_netdev()
      since the netdev core code deletes calls free_netdev()
    - The switch to the accelerated entrances is moved to the success path.
    
    Cc: stable@vger.kernel.org
    Fixes: d99dc602e2a5 ("IB/hfi1: Add functions to transmit datagram ipoib packets")
    Link: https://lore.kernel.org/r/1642287756-182313-4-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit b1151b74ff68cc83c2a8e1a618efe7d056e4f237
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Sat Jan 15 18:02:34 2022 -0500

    IB/hfi1: Fix alloc failure with larger txqueuelen
    
    The following allocation with large txqueuelen will result in the
    following warning:
    
      Call Trace:
       __alloc_pages_nodemask+0x283/0x2c0
       kmalloc_large_node+0x3c/0xa0
       __kmalloc_node+0x22a/0x2f0
       hfi1_ipoib_txreq_init+0x19f/0x330 [hfi1]
       hfi1_ipoib_setup_rn+0xd3/0x1a0 [hfi1]
       rdma_init_netdev+0x5a/0x80 [ib_core]
       ipoib_intf_init+0x6c/0x350 [ib_ipoib]
       ipoib_intf_alloc+0x5c/0xc0 [ib_ipoib]
       ipoib_add_one+0xbe/0x300 [ib_ipoib]
       add_client_context+0x12c/0x1a0 [ib_core]
       ib_register_client+0x147/0x190 [ib_core]
       ipoib_init_module+0xdd/0x132 [ib_ipoib]
       do_one_initcall+0x46/0x1c3
       do_init_module+0x5a/0x220
       load_module+0x14c5/0x17f0
       __do_sys_init_module+0x13b/0x180
       do_syscall_64+0x5b/0x1a0
       entry_SYSCALL_64_after_hwframe+0x65/0xca
    
    For ipoib, the txqueuelen is modified with the module parameter
    send_queue_size.
    
    Fix by changing to use kv versions of the same allocator to handle the
    large allocations.  The allocation embeds a hdr struct that is dma mapped.
    Change that struct to a pointer to a kzalloced struct.
    
    Cc: stable@vger.kernel.org
    Fixes: d99dc602e2a5 ("IB/hfi1: Add functions to transmit datagram ipoib packets")
    Link: https://lore.kernel.org/r/1642287756-182313-3-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 010a2a6623317bbf13facaff8bf50ac08468c1df
Merge: 1f84a9450d75e 5d8a8b324ff48
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 28 15:10:45 2022 +0000

    Merge tag 'ieee802154-for-net-2022-01-28' of git://git.kernel.org/pub/scm/linux/kernel/git/sschmidt/wpan
    
    Stefan Schmidt says:
    
    ====================
    pull-request: ieee802154 for net 2022-01-28
    
    An update from ieee802154 for your *net* tree.
    
    A bunch of fixes in drivers, all from Miquel Raynal.
    Clarifying the default channel in hwsim, leak fixes in at86rf230 and ca8210 as
    well as a symbol duration fix for mcr20a. Topping up the driver fixes with
    better error codes in nl802154 and a cleanup in MAINTAINERS for an orphaned
    driver.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1f84a9450d75e08af70d9e2f2d5e1c0ac0c881d2
Author: Haiyue Wang <haiyue.wang@intel.com>
Date:   Fri Jan 28 18:47:14 2022 +0800

    gve: fix the wrong AdminQ buffer queue index check
    
    The 'tail' and 'head' are 'unsigned int' type free-running count, when
    'head' is overflow, the 'int i (= tail) < u32 head' will be false:
    
    Only '- loop 0: idx = 63' result is shown, so it needs to use 'int' type
    to compare, it can handle the overflow correctly.
    
    typedef uint32_t u32;
    
    int main()
    {
            u32 tail, head;
            int stail, shead;
            int i, loop;
    
            tail = 0xffffffff;
            head = 0x00000000;
    
            for (i = tail, loop = 0; i < head; i++) {
                    unsigned int idx = i & 63;
    
                    printf("+ loop %d: idx = %u\n", loop++, idx);
            }
    
            stail = tail;
            shead = head;
            for (i = stail, loop = 0; i < shead; i++) {
                    unsigned int idx = i & 63;
    
                    printf("- loop %d: idx = %u\n", loop++, idx);
            }
    
            return 0;
    }
    
    Fixes: 5cdad90de62c ("gve: Batch AQ commands for creating and destroying queues.")
    Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8c83d39cc730378bbac64d67a551897b203a606e
Author: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
Date:   Sat Jan 15 18:02:33 2022 -0500

    IB/hfi1: Fix panic with larger ipoib send_queue_size
    
    When the ipoib send_queue_size is increased from the default the following
    panic happens:
    
      RIP: 0010:hfi1_ipoib_drain_tx_ring+0x45/0xf0 [hfi1]
      Code: 31 e4 eb 0f 8b 85 c8 02 00 00 41 83 c4 01 44 39 e0 76 60 8b 8d cc 02 00 00 44 89 e3 be 01 00 00 00 d3 e3 48 03 9d c0 02 00 00 <c7> 83 18 01 00 00 00 00 00 00 48 8b bb 30 01 00 00 e8 25 af a7 e0
      RSP: 0018:ffffc9000798f4a0 EFLAGS: 00010286
      RAX: 0000000000008000 RBX: ffffc9000aa0f000 RCX: 000000000000000f
      RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
      RBP: ffff88810ff08000 R08: ffff88889476d900 R09: 0000000000000101
      R10: 0000000000000000 R11: ffffc90006590ff8 R12: 0000000000000200
      R13: ffffc9000798fba8 R14: 0000000000000000 R15: 0000000000000001
      FS:  00007fd0f79cc3c0(0000) GS:ffff88885fb00000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: ffffc9000aa0f118 CR3: 0000000889c84001 CR4: 00000000001706e0
      Call Trace:
       <TASK>
       hfi1_ipoib_napi_tx_disable+0x45/0x60 [hfi1]
       hfi1_ipoib_dev_stop+0x18/0x80 [hfi1]
       ipoib_ib_dev_stop+0x1d/0x40 [ib_ipoib]
       ipoib_stop+0x48/0xc0 [ib_ipoib]
       __dev_close_many+0x9e/0x110
       __dev_change_flags+0xd9/0x210
       dev_change_flags+0x21/0x60
       do_setlink+0x31c/0x10f0
       ? __nla_validate_parse+0x12d/0x1a0
       ? __nla_parse+0x21/0x30
       ? inet6_validate_link_af+0x5e/0xf0
       ? cpumask_next+0x1f/0x20
       ? __snmp6_fill_stats64.isra.53+0xbb/0x140
       ? __nla_validate_parse+0x47/0x1a0
       __rtnl_newlink+0x530/0x910
       ? pskb_expand_head+0x73/0x300
       ? __kmalloc_node_track_caller+0x109/0x280
       ? __nla_put+0xc/0x20
       ? cpumask_next_and+0x20/0x30
       ? update_sd_lb_stats.constprop.144+0xd3/0x820
       ? _raw_spin_unlock_irqrestore+0x25/0x37
       ? __wake_up_common_lock+0x87/0xc0
       ? kmem_cache_alloc_trace+0x3d/0x3d0
       rtnl_newlink+0x43/0x60
    
    The issue happens when the shift that should have been a function of the
    txq item size mistakenly used the ring size.
    
    Fix by using the item size.
    
    Cc: stable@vger.kernel.org
    Fixes: d47dfc2b00e6 ("IB/hfi1: Remove cache and embed txreq in ring")
    Link: https://lore.kernel.org/r/1642287756-182313-2-git-send-email-mike.marciniszyn@cornelisnetworks.com
    Reviewed-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Mike Marciniszyn <mike.marciniszyn@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 501c8f5e3901f0de3244137e72fb39611f77a77c
Merge: 928d6fe996f69 d01ffb9eee4af
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 28 14:56:47 2022 +0000

    Merge branch 'ax25-fixes'
    
    Duoming Zhou says:
    
    ====================
    ax25: fix NPD and UAF bugs when detaching ax25 device
    
    There are NPD and UAF bugs when detaching ax25 device, we
    use lock and refcount to mitigate these bugs.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d01ffb9eee4af165d83b08dd73ebdf9fe94a519b
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Fri Jan 28 12:47:16 2022 +0800

    ax25: add refcount in ax25_dev to avoid UAF bugs
    
    If we dereference ax25_dev after we call kfree(ax25_dev) in
    ax25_dev_device_down(), it will lead to concurrency UAF bugs.
    There are eight syscall functions suffer from UAF bugs, include
    ax25_bind(), ax25_release(), ax25_connect(), ax25_ioctl(),
    ax25_getname(), ax25_sendmsg(), ax25_getsockopt() and
    ax25_info_show().
    
    One of the concurrency UAF can be shown as below:
    
      (USE)                       |    (FREE)
                                  |  ax25_device_event
                                  |    ax25_dev_device_down
    ax25_bind                     |    ...
      ...                         |      kfree(ax25_dev)
      ax25_fillin_cb()            |    ...
        ax25_fillin_cb_from_dev() |
      ...                         |
    
    The root cause of UAF bugs is that kfree(ax25_dev) in
    ax25_dev_device_down() is not protected by any locks.
    When ax25_dev, which there are still pointers point to,
    is released, the concurrency UAF bug will happen.
    
    This patch introduces refcount into ax25_dev in order to
    guarantee that there are no pointers point to it when ax25_dev
    is released.
    
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4e0f718daf97d47cf7dec122da1be970f145c809
Author: Duoming Zhou <duoming@zju.edu.cn>
Date:   Fri Jan 28 12:47:15 2022 +0800

    ax25: improve the incomplete fix to avoid UAF and NPD bugs
    
    The previous commit 1ade48d0c27d ("ax25: NPD bug when detaching
    AX25 device") introduce lock_sock() into ax25_kill_by_device to
    prevent NPD bug. But the concurrency NPD or UAF bug will occur,
    when lock_sock() or release_sock() dereferences the ax25_cb->sock.
    
    The NULL pointer dereference bug can be shown as below:
    
    ax25_kill_by_device()        | ax25_release()
                                 |   ax25_destroy_socket()
                                 |     ax25_cb_del()
      ...                        |     ...
                                 |     ax25->sk=NULL;
      lock_sock(s->sk); //(1)    |
      s->ax25_dev = NULL;        |     ...
      release_sock(s->sk); //(2) |
      ...                        |
    
    The root cause is that the sock is set to null before dereference
    site (1) or (2). Therefore, this patch extracts the ax25_cb->sock
    in advance, and uses ax25_list_lock to protect it, which can synchronize
    with ax25_cb_del() and ensure the value of sock is not null before
    dereference sites.
    
    The concurrency UAF bug can be shown as below:
    
    ax25_kill_by_device()        | ax25_release()
                                 |   ax25_destroy_socket()
      ...                        |   ...
                                 |   sock_put(sk); //FREE
      lock_sock(s->sk); //(1)    |
      s->ax25_dev = NULL;        |   ...
      release_sock(s->sk); //(2) |
      ...                        |
    
    The root cause is that the sock is released before dereference
    site (1) or (2). Therefore, this patch uses sock_hold() to increase
    the refcount of sock and uses ax25_list_lock to protect it, which
    can synchronize with ax25_cb_del() in ax25_destroy_socket() and
    ensure the sock wil not be released before dereference sites.
    
    Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 500c77eed0feabddd5b3afb48e32c204614a8eab
Author: Gerhard Engleder <gerhard@engleder-embedded.com>
Date:   Thu Jan 27 20:46:02 2022 +0100

    pinctrl: zynqmp: Revert "Unify pin naming"
    
    This reverts commit 54784ff24971ed5bd3f1056edce998148709d0a7.
    
    This patch changes the pin names from "MIO%d" to "MIO-%d", but all dts
    in arch/arm64/boot/dts/xilinx still use the old name. As a result my
    ZCU104 has no output on serial terminal and is not reachable over
    network.
    
    Signed-off-by: Gerhard Engleder <gerhard@engleder-embedded.com>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

commit 928d6fe996f69330ded6b887baf4534c5fac7988
Author: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
Date:   Thu Jan 27 21:17:14 2022 +0900

    net: stmmac: dwmac-visconti: No change to ETHER_CLOCK_SEL for unexpected speed request.
    
    Variable clk_sel_val is not initialized in the default case of the first switch statement.
    In that case, the function should return immediately without any changes to the hardware.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Fixes: b38dd98ff8d0 ("net: stmmac: Add Toshiba Visconti SoCs glue driver")
    Signed-off-by: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
    Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 665408f4c3a5c83e712871daa062721624b2b79e
Author: Phil Elwell <phil@raspberrypi.com>
Date:   Tue Jan 18 15:45:14 2022 +0000

    brcmfmac: firmware: Fix crash in brcm_alt_fw_path
    
    The call to brcm_alt_fw_path in brcmf_fw_get_firmwares is not protected
    by a check to the validity of the fwctx->req->board_type pointer. This
    results in a crash in strlcat when, for example, the WLAN chip is found
    in a USB dongle.
    
    Prevent the crash by adding the necessary check.
    
    See: https://github.com/raspberrypi/linux/issues/4833
    
    Fixes: 5ff013914c62 ("brcmfmac: firmware: Allow per-board firmware binaries")
    Signed-off-by: Phil Elwell <phil@raspberrypi.com>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220118154514.3245524-1-phil@raspberrypi.com

commit ab451ea952fe9d7afefae55ddb28943a148247fe
Author: Dai Ngo <dai.ngo@oracle.com>
Date:   Wed Jan 26 13:13:38 2022 -0800

    nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client.
    
    From RFC 7530 Section 16.34.5:
    
    o  The server has not recorded an unconfirmed { v, x, c, *, * } and
       has recorded a confirmed { v, x, c, *, s }.  If the principals of
       the record and of SETCLIENTID_CONFIRM do not match, the server
       returns NFS4ERR_CLID_INUSE without removing any relevant leased
       client state, and without changing recorded callback and
       callback_ident values for client { x }.
    
    The current code intends to do what the spec describes above but
    it forgot to set 'old' to NULL resulting to the confirmed client
    to be expired.
    
    Fixes: 2b63482185e6 ("nfsd: fix clid_inuse on mount with security change")
    Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Reviewed-by: Bruce Fields <bfields@fieldses.org>

commit 60b1e97140a487608b7cbde774b3cff1b5a99c00
Author: Rob Herring <robh@kernel.org>
Date:   Wed Jan 26 17:13:26 2022 -0600

    spi: dt-bindings: Fix 'reg' child node schema
    
    The schema for SPI child nodes' 'reg' property is not complete. 'reg' is
    a matrix of cells. The schema needs to define both the number of 'reg'
    entries and constraints on each entry.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220126231326.1636199-1-robh@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 2cbd27267ffe020af1442b95ec57f59a157ba85c
Author: Kamal Dasu <kdasu.kdev@gmail.com>
Date:   Thu Jan 27 13:53:59 2022 -0500

    spi: bcm-qspi: check for valid cs before applying chip select
    
    Apply only valid chip select value. This change fixes case where chip
    select is set to initial value of '-1' during probe and  PM supend and
    subsequent resume can try to use the value with undefined behaviour.
    Also in case where gpio based chip select, the check in
    bcm_qspi_chip_select() shall prevent undefined behaviour on resume.
    
    Fixes: fa236a7ef240 ("spi: bcm-qspi: Add Broadcom MSPI driver")
    Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220127185359.27322-1-kdasu.kdev@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit fb25621da5702c104ce0a48de5b174ced09e5b4e
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Jan 27 13:13:34 2022 +0000

    ASoC: fsl: Add missing error handling in pcm030_fabric_probe
    
    Add the missing platform_device_put() and platform_device_del()
    before return from pcm030_fabric_probe in the error handling case.
    
    Fixes: c912fa913446 ("ASoC: fsl: register the wm9712-codec")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20220127131336.30214-1-linmq006@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 17179d0068b20413de2355f84c75a93740257e20
Merge: 6a0c61703e3a5 278583055a237
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Jan 28 07:45:15 2022 -0500

    Merge tag 'kvmarm-fixes-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
    
    KVM/arm64 fixes for 5.17, take #1
    
    - Correctly update the shadow register on exception injection when
      running in nVHE mode
    
    - Correctly use the mm_ops indirection when performing cache invalidation
      from the page-table walker
    
    - Restrict the vgic-v3 workaround for SEIS to the two known broken
      implementations

commit 6a0c61703e3a5d67845a4b275e1d9d7bc1b5aad7
Author: Hou Wenlong <houwenlong93@linux.alibaba.com>
Date:   Thu Jan 27 14:54:49 2022 +0800

    KVM: eventfd: Fix false positive RCU usage warning
    
    Fix the following false positive warning:
     =============================
     WARNING: suspicious RCU usage
     5.16.0-rc4+ #57 Not tainted
     -----------------------------
     arch/x86/kvm/../../../virt/kvm/eventfd.c:484 RCU-list traversed in non-reader section!!
    
     other info that might help us debug this:
    
     rcu_scheduler_active = 2, debug_locks = 1
     3 locks held by fc_vcpu 0/330:
      #0: ffff8884835fc0b0 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x88/0x6f0 [kvm]
      #1: ffffc90004c0bb68 (&kvm->srcu){....}-{0:0}, at: vcpu_enter_guest+0x600/0x1860 [kvm]
      #2: ffffc90004c0c1d0 (&kvm->irq_srcu){....}-{0:0}, at: kvm_notify_acked_irq+0x36/0x180 [kvm]
    
     stack backtrace:
     CPU: 26 PID: 330 Comm: fc_vcpu 0 Not tainted 5.16.0-rc4+
     Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
     Call Trace:
      <TASK>
      dump_stack_lvl+0x44/0x57
      kvm_notify_acked_gsi+0x6b/0x70 [kvm]
      kvm_notify_acked_irq+0x8d/0x180 [kvm]
      kvm_ioapic_update_eoi+0x92/0x240 [kvm]
      kvm_apic_set_eoi_accelerated+0x2a/0xe0 [kvm]
      handle_apic_eoi_induced+0x3d/0x60 [kvm_intel]
      vmx_handle_exit+0x19c/0x6a0 [kvm_intel]
      vcpu_enter_guest+0x66e/0x1860 [kvm]
      kvm_arch_vcpu_ioctl_run+0x438/0x7f0 [kvm]
      kvm_vcpu_ioctl+0x38a/0x6f0 [kvm]
      __x64_sys_ioctl+0x89/0xc0
      do_syscall_64+0x3a/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Since kvm_unregister_irq_ack_notifier() does synchronize_srcu(&kvm->irq_srcu),
    kvm->irq_ack_notifier_list is protected by kvm->irq_srcu. In fact,
    kvm->irq_srcu SRCU read lock is held in kvm_notify_acked_irq(), making it
    a false positive warning. So use hlist_for_each_entry_srcu() instead of
    hlist_for_each_entry_rcu().
    
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Hou Wenlong <houwenlong93@linux.alibaba.com>
    Message-Id: <f98bac4f5052bad2c26df9ad50f7019e40434512.1643265976.git.houwenlong.hwl@antgroup.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6cbbaab60ff33f59355492c241318046befd9ffc
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 12 18:01:34 2022 +0100

    KVM: nVMX: Allow VMREAD when Enlightened VMCS is in use
    
    Hyper-V TLFS explicitly forbids VMREAD and VMWRITE instructions when
    Enlightened VMCS interface is in use:
    
    "Any VMREAD or VMWRITE instructions while an enlightened VMCS is
    active is unsupported and can result in unexpected behavior.""
    
    Windows 11 + WSL2 seems to ignore this, attempts to VMREAD VMCS field
    0x4404 ("VM-exit interruption information") are observed. Failing
    these attempts with nested_vmx_failInvalid() makes such guests
    unbootable.
    
    Microsoft confirms this is a Hyper-V bug and claims that it'll get fixed
    eventually but for the time being we need a workaround. (Temporary) allow
    VMREAD to get data from the currently loaded Enlightened VMCS.
    
    Note: VMWRITE instructions remain forbidden, it is not clear how to
    handle them properly and hopefully won't ever be needed.
    
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220112170134.1904308-6-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 892a42c10ddb945d3a4dcf07dccdf9cb98b21548
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 12 18:01:33 2022 +0100

    KVM: nVMX: Implement evmcs_field_offset() suitable for handle_vmread()
    
    In preparation to allowing reads from Enlightened VMCS from
    handle_vmread(), implement evmcs_field_offset() to get the correct
    read offset. get_evmcs_offset(), which is being used by KVM-on-Hyper-V,
    is almost what's needed but a few things need to be adjusted. First,
    WARN_ON() is unacceptable for handle_vmread() as any field can (in
    theory) be supplied by the guest and not all fields are defined in
    eVMCS v1. Second, we need to handle 'holes' in eVMCS (missing fields).
    It also sounds like a good idea to WARN_ON() if such fields are ever
    accessed by KVM-on-Hyper-V.
    
    Implement dedicated evmcs_field_offset() helper.
    
    No functional change intended.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220112170134.1904308-5-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2423a4c0d17418eca1ba1e3f48684cb2ab7523d5
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 12 18:01:32 2022 +0100

    KVM: nVMX: Rename vmcs_to_field_offset{,_table}
    
    vmcs_to_field_offset{,_table} may sound misleading as VMCS is an opaque
    blob which is not supposed to be accessed directly. In fact,
    vmcs_to_field_offset{,_table} are related to KVM defined VMCS12 structure.
    
    Rename vmcs_field_to_offset() to get_vmcs12_field_offset() for clarity.
    
    No functional change intended.
    
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220112170134.1904308-4-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 7a601e2cf61558dfd534a9ecaad09f5853ad8204
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 12 18:01:31 2022 +0100

    KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER
    
    Enlightened VMCS v1 doesn't have VMX_PREEMPTION_TIMER_VALUE field,
    PIN_BASED_VMX_PREEMPTION_TIMER is also filtered out already so it makes
    sense to filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER too.
    
    Note, none of the currently existing Windows/Hyper-V versions are known
    to enable 'save VMX-preemption timer value' when eVMCS is in use, the
    change is aimed at making the filtering future proof.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220112170134.1904308-3-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit f80ae0ef089a09e8c18da43a382c3caac9a424a7
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 12 18:01:30 2022 +0100

    KVM: nVMX: Also filter MSR_IA32_VMX_TRUE_PINBASED_CTLS when eVMCS
    
    Similar to MSR_IA32_VMX_EXIT_CTLS/MSR_IA32_VMX_TRUE_EXIT_CTLS,
    MSR_IA32_VMX_ENTRY_CTLS/MSR_IA32_VMX_TRUE_ENTRY_CTLS pair,
    MSR_IA32_VMX_TRUE_PINBASED_CTLS needs to be filtered the same way
    MSR_IA32_VMX_PINBASED_CTLS is currently filtered as guests may solely rely
    on 'true' MSR data.
    
    Note, none of the currently existing Windows/Hyper-V versions are known
    to stumble upon the unfiltered MSR_IA32_VMX_TRUE_PINBASED_CTLS, the change
    is aimed at making the filtering future proof.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220112170134.1904308-2-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b19c99b9f4486f23e3b7248dd4ce3d83e19b9032
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Jan 26 07:51:00 2022 -0500

    selftests: kvm: check dynamic bits against KVM_X86_XCOMP_GUEST_SUPP
    
    Provide coverage for the new API.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit dd6e631220181162478984d2d46dd979e04d8e75
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Jan 26 07:49:45 2022 -0500

    KVM: x86: add system attribute to retrieve full set of supported xsave states
    
    Because KVM_GET_SUPPORTED_CPUID is meant to be passed (by simple-minded
    VMMs) to KVM_SET_CPUID2, it cannot include any dynamic xsave states that
    have not been enabled.  Probing those, for example so that they can be
    passed to ARCH_REQ_XCOMP_GUEST_PERM, requires a new ioctl or arch_prctl.
    The latter is in fact worse, even though that is what the rest of the
    API uses, because it would require supported_xcr0 to be moved from the
    KVM module to the kernel just for this use.  In addition, the value
    would be nonsensical (or an error would have to be returned) until
    the KVM module is loaded in.
    
    Therefore, to limit the growth of system ioctls, add a /dev/kvm
    variant of KVM_{GET,HAS}_DEVICE_ATTR, and implement it in x86
    with just one group (0) and attribute (KVM_X86_XCOMP_GUEST_SUPP).
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 56f289a8d23addfa4408a08f07f42fcfe2a7bd69
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 27 07:31:53 2022 -0800

    KVM: x86: Add a helper to retrieve userspace address from kvm_device_attr
    
    Add a helper to handle converting the u64 userspace address embedded in
    struct kvm_device_attr into a userspace pointer, it's all too easy to
    forget the intermediate "unsigned long" cast as well as the truncation
    check.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c8980fcb210851138cb34c9a8cb0cf0c09f07bf9
Author: Roger Pau Monne <roger.pau@citrix.com>
Date:   Fri Jan 21 10:01:46 2022 +0100

    xen/x2apic: enable x2apic mode when supported for HVM
    
    There's no point in disabling x2APIC mode when running as a Xen HVM
    guest, just enable it when available.
    
    Remove some unneeded wrapping around the detection functions, and
    simply provide a xen_x2apic_available helper that's a wrapper around
    x2apic_supported.
    
    Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
    Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Link: https://lore.kernel.org/r/20220121090146.13697-1-roger.pau@citrix.com
    Signed-off-by: Juergen Gross <jgross@suse.com>

commit 9ae279ecabe3e5bb85567e6c7371f4d35cfa00d6
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 24 17:55:27 2022 +0000

    kselftest/arm64: Correct logging of FPSIMD register read via ptrace
    
    There's a cut'n'paste error in the logging for our test for reading register
    state back via ptrace, correctly say that we did a read instead of a write.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220124175527.3260234-3-broonie@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 50806fd91428a28d5daa649310dd0ca05b39c118
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 24 17:55:26 2022 +0000

    kselftest/arm64: Skip VL_INHERIT tests for unsupported vector types
    
    Currently we unconditionally test the ability to set the vector length
    inheritance flag via ptrace meaning that we generate false failures on
    systems that don't support SVE when we attempt to set the vector length
    there. Check the hwcap and mark the tests as skipped when it's not present.
    
    Fixes: 0ba1ce1e8605 ("selftests: arm64: Add coverage of ptrace flags for SVE VL inheritance")
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220124175527.3260234-2-broonie@kernel.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 145d9b498fc827b79c1260b4caa29a8e59d4c2b9
Merge: 374630e3f94ef 9b6d90e2085ca
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 11:47:05 2022 +0200

    Merge tag 'ata-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ATA fix from Damien Le Moal:
     "A single fix for 5.17-rc2, adding a missing resource allocation error
      check in the pata_platform driver, from Zhou"
    
    * tag 'ata-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: pata_platform: Fix a NULL pointer dereference in __pata_platform_probe()

commit d7da660cab47183cded65e11b64497d0f56c6edf
Author: John David Anglin <dave.anglin@bell.net>
Date:   Thu Jan 27 22:33:41 2022 +0000

    parisc: Fix sglist access in ccio-dma.c
    
    This patch implements the same bug fix to ccio-dma.c as to sba_iommu.c.
    It ensures that only the allocated entries of the sglist are accessed.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Cc: stable@vger.kernel.org
    Signed-off-by: Helge Deller <deller@gmx.de>

commit b7d6f44a0fa716a82969725516dc0b16bc7cd514
Author: John David Anglin <dave.anglin@bell.net>
Date:   Wed Jan 26 20:39:05 2022 +0000

    parisc: Fix data TLB miss in sba_unmap_sg
    
    Rolf Eike Beer reported the following bug:
    
    [1274934.746891] Bad Address (null pointer deref?): Code=15 (Data TLB miss fault) at addr 0000004140000018
    [1274934.746891] CPU: 3 PID: 5549 Comm: cmake Not tainted 5.15.4-gentoo-parisc64 #4
    [1274934.746891] Hardware name: 9000/785/C8000
    [1274934.746891]
    [1274934.746891]      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
    [1274934.746891] PSW: 00001000000001001111111000001110 Not tainted
    [1274934.746891] r00-03  000000ff0804fe0e 0000000040bc9bc0 00000000406760e4 0000004140000000
    [1274934.746891] r04-07  0000000040b693c0 0000004140000000 000000004a2b08b0 0000000000000001
    [1274934.746891] r08-11  0000000041f98810 0000000000000000 000000004a0a7000 0000000000000001
    [1274934.746891] r12-15  0000000040bddbc0 0000000040c0cbc0 0000000040bddbc0 0000000040bddbc0
    [1274934.746891] r16-19  0000000040bde3c0 0000000040bddbc0 0000000040bde3c0 0000000000000007
    [1274934.746891] r20-23  0000000000000006 000000004a368950 0000000000000000 0000000000000001
    [1274934.746891] r24-27  0000000000001fff 000000000800000e 000000004a1710f0 0000000040b693c0
    [1274934.746891] r28-31  0000000000000001 0000000041f988b0 0000000041f98840 000000004a171118
    [1274934.746891] sr00-03  00000000066e5800 0000000000000000 0000000000000000 00000000066e5800
    [1274934.746891] sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
    [1274934.746891]
    [1274934.746891] IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000406760e8 00000000406760ec
    [1274934.746891]  IIR: 48780030    ISR: 0000000000000000  IOR: 0000004140000018
    [1274934.746891]  CPU:        3   CR30: 00000040e3a9c000 CR31: ffffffffffffffff
    [1274934.746891]  ORIG_R28: 0000000040acdd58
    [1274934.746891]  IAOQ[0]: sba_unmap_sg+0xb0/0x118
    [1274934.746891]  IAOQ[1]: sba_unmap_sg+0xb4/0x118
    [1274934.746891]  RP(r2): sba_unmap_sg+0xac/0x118
    [1274934.746891] Backtrace:
    [1274934.746891]  [<00000000402740cc>] dma_unmap_sg_attrs+0x6c/0x70
    [1274934.746891]  [<000000004074d6bc>] scsi_dma_unmap+0x54/0x60
    [1274934.746891]  [<00000000407a3488>] mptscsih_io_done+0x150/0xd70
    [1274934.746891]  [<0000000040798600>] mpt_interrupt+0x168/0xa68
    [1274934.746891]  [<0000000040255a48>] __handle_irq_event_percpu+0xc8/0x278
    [1274934.746891]  [<0000000040255c34>] handle_irq_event_percpu+0x3c/0xd8
    [1274934.746891]  [<000000004025ecb4>] handle_percpu_irq+0xb4/0xf0
    [1274934.746891]  [<00000000402548e0>] generic_handle_irq+0x50/0x70
    [1274934.746891]  [<000000004019a254>] call_on_stack+0x18/0x24
    [1274934.746891]
    [1274934.746891] Kernel panic - not syncing: Bad Address (null pointer deref?)
    
    The bug is caused by overrunning the sglist and incorrectly testing
    sg_dma_len(sglist) before nents. Normally this doesn't cause a crash,
    but in this case sglist crossed a page boundary. This occurs in the
    following code:
    
            while (sg_dma_len(sglist) && nents--) {
    
    The fix is simply to test nents first and move the decrement of nents
    into the loop.
    
    Reported-by: Rolf Eike Beer <eike-kernel@sf-tec.de>
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Cc: stable@vger.kernel.org
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 9129886b88185962538180625ca8051362b01327
Author: John David Anglin <dave.anglin@bell.net>
Date:   Sat Jan 22 18:19:49 2022 +0000

    parisc: Drop __init from map_pages declaration
    
    With huge kernel pages, we randomly eat a SPARC in map_pages(). This
    is fixed by dropping __init from the declaration.
    
    However, map_pages references the __init routine memblock_alloc_try_nid
    via memblock_alloc.  Thus, it needs to be marked with __ref.
    
    memblock_alloc is only called before the kernel text is set to readonly.
    
    The __ref on free_initmem is no longer needed.
    
    Comment regarding map_pages being in the init section is removed.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Cc: stable@vger.kernel.org # v5.4+
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 0444f82766f0b5b9c8302ad802dafa5dd0e722d0
Author: Takashi Iwai <tiwai@suse.de>
Date:   Thu Jan 27 14:57:17 2022 +0100

    ALSA: hda: Fix signedness of sscanf() arguments
    
    The %x format of sscanf() takes an unsigned int pointer, while we pass
    a signed int pointer.  Practically it's OK, but this may result in a
    compile warning.  Let's fix it.
    
    Fixes: a235d5b8e550 ("ALSA: hda: Allow model option to specify PCI SSID alias")
    Reported-by: kernel test robot <lkp@intel.com>
    Link: https://lore.kernel.org/r/20220127135717.31751-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 374630e3f94efc8184a727694276088f52bcc3d1
Merge: 82b550fa99f2c 79da533d3cc71
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 09:48:20 2022 +0200

    Merge tag 'hwmon-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
    
    Pull hwmon fixes from Guenter Roeck:
    
     - Fix crash in nct6775 driver
    
     - Prevent divide by zero in adt7470 driver
    
     - Fix conditional compile warning in pmbus/ir38064 driver
    
     - Various minor fixes in lm90 driver
    
    * tag 'hwmon-for-v5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging:
      hwmon: (nct6775) Fix crash in clear_caseopen
      hwmon: (adt7470) Prevent divide by zero in adt7470_fan_write()
      hwmon: (pmbus/ir38064) Mark ir38064_of_match as __maybe_unused
      hwmon: (lm90) Fix sysfs and udev notifications
      hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649
      hwmon: (lm90) Mark alert as broken for MAX6680
      hwmon: (lm90) Mark alert as broken for MAX6654
      hwmon: (lm90) Re-enable interrupts after alert clears
      hwmon: (lm90) Reduce maximum conversion rate for G781

commit 82b550fa99f2c73636ca3f84900117c3c3272ef7
Merge: 23a46422c5614 db5aa1497d02e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 28 09:43:00 2022 +0200

    Merge tag 'drm-fixes-2022-01-28' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "This week's regular normal fixes. amdgpu and msm make up the bulk of
      it, with a scattering of fixes elsewhere.
    
      atomic:
       - fix CRTC handling during modeset
    
      privcy-screen:
       - honor acpi=off
    
      ttm:
       - build fix for um
    
      panel:
       - add orientation quirk for 1NetBook OneXPlayer
    
      amdgpu:
       - Proper fix for otg synchronization logic regression
       - DCN3.01 fixes
       - Filter out secondary radeon PCI IDs
       - udelay fixes
       - Fix a memory leak in an error path
    
      msm:
       - parameter check fixes
       - put_device balancing
       - idle/suspend fixes
    
      etnaviv:
       - relax submit size checks
    
      vc4:
       - fix potential deadlock in DSI code
    
      ast:
       - revert 1600x900 mode change"
    
    * tag 'drm-fixes-2022-01-28' of git://anongit.freedesktop.org/drm/drm: (25 commits)
      drm/privacy-screen: honor acpi=off in detect_thinkpad_privacy_screen
      Revert "drm/ast: Support 1600x900 with 108MHz PCLK"
      drm/amdgpu/display: Remove t_srx_delay_us.
      drm/amd/display: Wrap dcn301_calculate_wm_and_dlg for FPU.
      drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
      drm/amd/display/dc/calcs/dce_calcs: Fix a memleak in calculate_bandwidth()
      drm/amdgpu/display: use msleep rather than udelay for long delays
      drm/amdgpu/display: adjust msleep limit in dp_wait_for_training_aux_rd_interval
      drm/amdgpu: filter out radeon secondary ids as well
      drm/amd/display: change FIFO reset condition to embedded display only
      drm/amd/display: Correct MPC split policy for DCN301
      drm/amd/display: Fix for otg synchronization logic
      drm/etnaviv: relax submit size limits
      drm/msm/gpu: Cancel idle/boost work on suspend
      drm/msm/gpu: Wait for idle before suspending
      drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
      drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable
      drm/msm/a6xx: Add missing suspend_count increment
      drm/msm: Fix wrong size calculation
      drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
      ...

commit 42c9b28e6862d16db82a56f5667cf4d1f6658cf6
Author: Fabio Estevam <festevam@gmail.com>
Date:   Mon Dec 27 13:14:02 2021 -0300

    ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
    
    Currently, SD card fails to mount due to the following pinctrl error:
    
    [   11.170000] imx23-pinctrl 80018000.pinctrl: pin SSP1_DETECT already requested by 80018000.pinctrl; cannot claim for 80010000.spi
    [   11.180000] imx23-pinctrl 80018000.pinctrl: pin-65 (80010000.spi) status -22
    [   11.190000] imx23-pinctrl 80018000.pinctrl: could not request pin 65 (SSP1_DETECT) from group mmc0-pins-fixup.0  on device 80018000.pinctrl
    [   11.200000] mxs-mmc 80010000.spi: Error applying setting, reverse things back
    
    Fix it by removing the MX23_PAD_SSP1_DETECT pin from the hog group as it
    is already been used by the mmc0-pins-fixup pinctrl group.
    
    With this change the rootfs can be mounted and the imx23-evk board can
    boot successfully.
    
    Cc: <stable@vger.kernel.org>
    Fixes: bc3875f1a61e ("ARM: dts: mxs: modify mx23/mx28 dts files to use pinctrl headers")
    Signed-off-by: Fabio Estevam <festevam@gmail.com>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit db5aa1497d02e7770e40dd0d1bfcb4ea0b0d3906
Merge: b1d83f4c94f52 2a807341ed107
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 28 14:59:44 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-01-26' of https://gitlab.freedesktop.org/agd5f/linux into drm-fixes
    
    amd-drm-fixes-5.17-2022-01-26:
    
    amdgpu:
    - Proper fix for otg synchronization logic regression
    - DCN3.01 fixes
    - Filter out secondary radeon PCI IDs
    - udelay fixes
    - Fix a memory leak in an error path
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127041006.5695-1-alexander.deucher@amd.com

commit b1d83f4c94f52f2967cdd9b54b9ffb8bb6cfc61b
Merge: 52fa904e5167f e3d26528e083e
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 28 14:56:17 2022 +1000

    Merge branch 'etnaviv/fixes' of https://git.pengutronix.de/git/lst/linux into drm-fixes
    
    - relax submit size checks.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Lucas Stach <l.stach@pengutronix.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/8c2cb3e3a702be86db9d43ca8927b6b78ac2b1d2.camel@pengutronix.de

commit 52fa904e5167fc10f4e421727e898ee96c307518
Merge: 2fd0e5fb4ba37 6aa89ae1fb049
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 28 14:52:34 2022 +1000

    Merge tag 'drm-msm-fixes-2022-01-25' of https://gitlab.freedesktop.org/drm/msm into drm-fixes
    
    A few msm fixes.
    - parameter checks
    - put_device balancing
    - idle/suspend fixes
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Rob Clark <robdclark@gmail.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/CAF6AEGvAfsgtr==VM4wixAC_hSTuV=eNWXxX=BhZqQrbxHjKgg@mail.gmail.com

commit 2fd0e5fb4ba37dff344b7bed5176212c2d6a7063
Merge: 23ecd4c135422 7fde14d705985
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 28 14:46:11 2022 +1000

    Merge tag 'drm-misc-fixes-2022-01-27' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * drm/ast: Revert 1600x800 with 108MHz PCLK
     * drm/atomic: fix CRTC handling during modeset
     * drm/privacy-screen: Honor acpi=off
     * drm/ttm: build fix for ARCH=um
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YfJgH9fz+oo7YSXd@linux-uq9g.fritz.box

commit 23ecd4c1354226fd6ac9c5f8881666f76b9d6cbe
Merge: e783362eb54cd d3cbc6e323c92
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 28 14:37:30 2022 +1000

    Merge tag 'drm-misc-next-fixes-2022-01-21' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
    
     * vc4: Fix potential deadlock in DSI code
     * panel: Add orientation quirk for 1Netbook OneXPlayer
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yepuhj+Ks+IyJ9Dp@linux-uq9g

commit 7674b7b559b683478c3832527c59bceb169e701d
Author: Raju Rangoju <Raju.Rangoju@amd.com>
Date:   Thu Jan 27 11:32:22 2022 +0530

    net: amd-xgbe: ensure to reset the tx_timer_active flag
    
    Ensure to reset the tx_timer_active flag in xgbe_stop(),
    otherwise a port restart may result in tx timeout due to
    uncleared flag.
    
    Fixes: c635eaacbf77 ("amd-xgbe: Remove Tx coalescing")
    Co-developed-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
    Signed-off-by: Sudheesh Mavila <sudheesh.mavila@amd.com>
    Signed-off-by: Raju Rangoju <Raju.Rangoju@amd.com>
    Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
    Link: https://lore.kernel.org/r/20220127060222.453371-1-Raju.Rangoju@amd.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 33d12dc91bc41183003913b888cc492420ae6ef8
Merge: 5aac9108a180f b07f413732549
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 27 18:53:01 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    1) Remove leftovers from flowtable modules, from Geert Uytterhoeven.
    
    2) Missing refcount increment of conntrack template in nft_ct,
       from Florian Westphal.
    
    3) Reduce nft_zone selftest time, also from Florian.
    
    4) Add selftest to cover stateless NAT on fragments, from Florian Westphal.
    
    5) Do not set net_device when for reject packets from the bridge path,
       from Phil Sutter.
    
    6) Cancel register tracking info on nft_byteorder operations.
    
    7) Extend nft_concat_range selftest to cover set reload with no elements,
       from Florian Westphal.
    
    8) Remove useless update of pointer in chain blob builder, reported
       by kbuild test robot.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf:
      netfilter: nf_tables: remove assignment with no effect in chain blob builder
      selftests: nft_concat_range: add test for reload with no element add/del
      netfilter: nft_byteorder: track register operations
      netfilter: nft_reject_bridge: Fix for missing reply from prerouting
      selftests: netfilter: check stateless nat udp checksum fixup
      selftests: netfilter: reduce zone stress test running time
      netfilter: nft_ct: fix use after free when attaching zone template
      netfilter: Remove flowtable relics
    ====================
    
    Link: https://lore.kernel.org/r/20220127235235.656931-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5aac9108a180fc06e28d4e7fb00247ce603b72ee
Author: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Date:   Thu Jan 27 14:50:03 2022 +0530

    net: amd-xgbe: Fix skb data length underflow
    
    There will be BUG_ON() triggered in include/linux/skbuff.h leading to
    intermittent kernel panic, when the skb length underflow is detected.
    
    Fix this by dropping the packet if such length underflows are seen
    because of inconsistencies in the hardware descriptors.
    
    Fixes: 622c36f143fc ("amd-xgbe: Fix jumbo MTU processing on newer hardware")
    Suggested-by: Tom Lendacky <thomas.lendacky@amd.com>
    Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
    Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
    Link: https://lore.kernel.org/r/20220127092003.2812745-1-Shyam-sundar.S-k@amd.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 67ab5eb71b37b55f7c5522d080a1b42823351776
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Thu Jan 27 15:44:18 2022 -0600

    tracing: Don't inc err_log entry count if entry allocation fails
    
    tr->n_err_log_entries should only be increased if entry allocation
    succeeds.
    
    Doing it when it fails won't cause any problems other than wasting an
    entry, but should be fixed anyway.
    
    Link: https://lkml.kernel.org/r/cad1ab28f75968db0f466925e7cba5970cec6c29.1643319703.git.zanussi@kernel.org
    
    Cc: stable@vger.kernel.org
    Fixes: 2f754e771b1a6 ("tracing: Don't inc err_log entry count if entry allocation fails")
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 097f1eefedeab528cecbd35586dfe293853ffb17
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Thu Jan 27 15:44:17 2022 -0600

    tracing: Propagate is_signed to expression
    
    During expression parsing, a new expression field is created which
    should inherit the properties of the operands, such as size and
    is_signed.
    
    is_signed propagation was missing, causing spurious errors with signed
    operands.  Add it in parse_expr() and parse_unary() to fix the problem.
    
    Link: https://lkml.kernel.org/r/f4dac08742fd7a0920bf80a73c6c44042f5eaa40.1643319703.git.zanussi@kernel.org
    
    Cc: stable@vger.kernel.org
    Fixes: 100719dcef447 ("tracing: Add simple expression support to hist triggers")
    Reported-by: Yordan Karadzhov <ykaradzhov@vmware.com>
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215513
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit b59f2f2b865cedd6d1641394b9cd84399bd738ff
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Thu Jan 27 15:44:16 2022 -0600

    tracing: Fix smatch warning for do while check in event_hist_trigger_parse()
    
    The patch ec5ce0987541: "tracing: Allow whitespace to surround hist
    trigger filter" from Jan 15, 2018, leads to the following Smatch
    static checker warning:
    
        kernel/trace/trace_events_hist.c:6199 event_hist_trigger_parse()
        warn: 'p' can't be NULL.
    
    Since p is always checked for a NULL value at the top of loop and
    nothing in the rest of the loop will set it to NULL, the warning
    is correct and might as well be 1 to silence the warning.
    
    Link: https://lkml.kernel.org/r/a1d4c79766c0cf61e20438dc35244d216633fef6.1643319703.git.zanussi@kernel.org
    
    Fixes: ec5ce09875410 ("tracing: Allow whitespace to surround hist trigger filter")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 798a5b6c195d1c64fd5e9dd252381feb17e5ff22
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Thu Jan 27 15:44:15 2022 -0600

    tracing: Fix smatch warning for null glob in event_hist_trigger_parse()
    
    The recent rename of event_hist_trigger_parse() caused smatch
    re-evaluation of trace_events_hist.c and as a result an old warning
    was found:
    
        kernel/trace/trace_events_hist.c:6174 event_hist_trigger_parse()
        error: we previously assumed 'glob' could be null (see line 6166)
    
    glob should never be null (and apparently smatch can also figure that
    out and skip the warning when using the cross-function DB (but which
    can't be used with a 0day build as it takes too much time to
    generate)).
    
    Nonetheless for clarity, remove the test but add a WARN_ON() in case
    the code ever changes.
    
    Link: https://lkml.kernel.org/r/96925e5c1f116654ada7ea0613d930b1266b5e1c.1643319703.git.zanussi@kernel.org
    
    Fixes: f404da6e1d46c ("tracing: Add 'last error' error facility for hist triggers")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit aa814c51ab7cb3ddeeeeedaa37d599aee7ba6649
Author: Shuah Khan <skhan@linuxfoundation.org>
Date:   Tue Jan 25 17:22:34 2022 -0700

    tools/tracing: Update Makefile to build rtla
    
    Update tracing Makefile to build/install/clean rtla tragets.
    
    Link: https://lkml.kernel.org/r/20220126002234.79337-1-skhan@linuxfoundation.org
    
    Reviewed-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 2201aea114d4c7eedd05865df545dbb987cee5c1
Author: Shuah Khan <skhan@linuxfoundation.org>
Date:   Tue Jan 25 17:13:01 2022 -0700

    rtla: Make doc build optional
    
    rtla build fails due to doc build dependency on rst2man. Make
    doc build optional so rtla could be built without docs. Leave
    the install dependency on doc_install alone.
    
    Link: https://lkml.kernel.org/r/20220126001301.79096-1-skhan@linuxfoundation.org
    
    Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit c6d777acdf8f62d4ebaef0e5c6cd8fedbd6e8546
Author: Kees Cook <keescook@chromium.org>
Date:   Tue Jan 25 14:00:37 2022 -0800

    tracing/perf: Avoid -Warray-bounds warning for __rel_loc macro
    
    As done for trace_events.h, also fix the __rel_loc macro in perf.h,
    which silences the -Warray-bounds warning:
    
    In file included from ./include/linux/string.h:253,
                     from ./include/linux/bitmap.h:11,
                     from ./include/linux/cpumask.h:12,
                     from ./include/linux/mm_types_task.h:14,
                     from ./include/linux/mm_types.h:5,
                     from ./include/linux/buildid.h:5,
                     from ./include/linux/module.h:14,
                     from samples/trace_events/trace-events-sample.c:2:
    In function '__fortify_strcpy',
        inlined from 'perf_trace_foo_rel_loc' at samples/trace_events/./trace-events-sample.h:519:1:
    ./include/linux/fortify-string.h:47:33: warning: '__builtin_strcpy' offset 12 is out of the bounds [
    0, 4] [-Warray-bounds]
       47 | #define __underlying_strcpy     __builtin_strcpy
          |                                 ^
    ./include/linux/fortify-string.h:445:24: note: in expansion of macro '__underlying_strcpy'
      445 |                 return __underlying_strcpy(p, q);
          |                        ^~~~~~~~~~~~~~~~~~~
    
    Also make __data struct member a proper flexible array to avoid future
    problems.
    
    Link: https://lkml.kernel.org/r/20220125220037.2738923-1-keescook@chromium.org
    
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Fixes: 55de2c0b5610c ("tracing: Add '__rel_loc' using trace event macros")
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 58c5724ec2cdd72b22107ec5de00d90cc4797796
Author: Masami Hiramatsu <mhiramat@kernel.org>
Date:   Tue Jan 25 23:19:30 2022 +0900

    tracing: Avoid -Warray-bounds warning for __rel_loc macro
    
    Since -Warray-bounds checks the destination size from the type of given
    pointer, __assign_rel_str() macro gets warned because it passes the
    pointer to the 'u32' field instead of 'trace_event_raw_*' data structure.
    Pass the data address calculated from the 'trace_event_raw_*' instead of
    'u32' __rel_loc field.
    
    Link: https://lkml.kernel.org/r/20220125233154.dac280ed36944c0c2fe6f3ac@kernel.org
    
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Kees Cook <keescook@chromium.org>
    Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
    [ This did not fix the warning, but is still a nice clean up ]
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit e629e7b525a179e29d53463d992bdee759c950fb
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Tue Jan 25 12:07:15 2022 +0800

    tracing/histogram: Fix a potential memory leak for kstrdup()
    
    kfree() is missing on an error path to free the memory allocated by
    kstrdup():
    
      p = param = kstrdup(data->params[i], GFP_KERNEL);
    
    So it is better to free it via kfree(p).
    
    Link: https://lkml.kernel.org/r/tencent_C52895FD37802832A3E5B272D05008866F0A@qq.com
    
    Cc: stable@vger.kernel.org
    Fixes: d380dcde9a07c ("tracing: Fix now invalid var_ref_vals assumption in trace action")
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 4ed308c445a1e3abac8f6c17928c1cb533867e38
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Tue Jan 25 09:19:10 2022 -0500

    ftrace: Have architectures opt-in for mcount build time sorting
    
    First S390 complained that the sorting of the mcount sections at build
    time caused the kernel to crash on their architecture. Now PowerPC is
    complaining about it too. And also ARM64 appears to be having issues.
    
    It may be necessary to also update the relocation table for the values
    in the mcount table. Not only do we have to sort the table, but also
    update the relocations that may be applied to the items in the table.
    
    If the system is not relocatable, then it is fine to sort, but if it is,
    some architectures may have issues (although x86 does not as it shifts all
    addresses the same).
    
    Add a HAVE_BUILDTIME_MCOUNT_SORT that an architecture can set to say it is
    safe to do the sorting at build time.
    
    Also update the config to compile in build time sorting in the sorttable
    code in scripts/ to depend on CONFIG_BUILDTIME_MCOUNT_SORT.
    
    Link: https://lore.kernel.org/all/944D10DA-8200-4BA9-8D0A-3BED9AA99F82@linux.ibm.com/
    Link: https://lkml.kernel.org/r/20220127153821.3bc1ac6e@gandalf.local.home
    
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Russell King <linux@armlinux.org.uk>
    Cc: Yinan Liu <yinan@linux.alibaba.com>
    Cc: Ard Biesheuvel <ardb@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Reported-by: Sachin Sant <sachinp@linux.ibm.com>
    Reviewed-by: Mark Rutland <mark.rutland@arm.com>
    Tested-by: Mark Rutland <mark.rutland@arm.com> [arm64]
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Fixes: 72b3942a173c ("scripts: ftrace - move the sort-processing in ftrace_init")
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit dae1d8ac31896988e7313384c0370176a75e9b45
Author: Cristian Marussi <cristian.marussi@arm.com>
Date:   Wed Jan 26 10:27:19 2022 +0000

    selftests: skip mincore.check_file_mmap when fs lacks needed support
    
    Report mincore.check_file_mmap as SKIP instead of FAIL if the underlying
    filesystem lacks support of O_TMPFILE or fallocate since such failures
    are not really related to mincore functionality.
    
    Cc: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
    Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit ac9e0a250bb155078601a5b999aab05f2a04d1ab
Author: Cristian Marussi <cristian.marussi@arm.com>
Date:   Wed Jan 26 10:27:23 2022 +0000

    selftests: openat2: Skip testcases that fail with EOPNOTSUPP
    
    Skip testcases that fail since the requested valid flags combination is not
    supported by the underlying filesystem.
    
    Cc: Aleksa Sarai <cyphar@cyphar.com>
    Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit ea3396725aa143dd42fe388cb67e44c90d2fb719
Author: Cristian Marussi <cristian.marussi@arm.com>
Date:   Wed Jan 26 10:27:22 2022 +0000

    selftests: openat2: Add missing dependency in Makefile
    
    Add a dependency on header helpers.h to the main target; while at that add
    to helpers.h also a missing include for bool types.
    
    Cc: Aleksa Sarai <cyphar@cyphar.com>
    Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit e051cdf655fa016692008a446a060eff06222bb5
Author: Cristian Marussi <cristian.marussi@arm.com>
Date:   Wed Jan 26 10:27:21 2022 +0000

    selftests: openat2: Print also errno in failure messages
    
    In E_func() macro, on error, print also errno in order to aid debugging.
    
    Cc: Aleksa Sarai <cyphar@cyphar.com>
    Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit b9199181a9ef8252e47e207be8c23e1f50662620
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Thu Jan 27 22:44:46 2022 +0500

    selftests: futex: Use variable MAKE instead of make
    
    Recursive make commands should always use the variable MAKE, not the
    explicit command name ‘make’. This has benefits and removes the
    following warning when multiple jobs are used for the build:
    
    make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
    
    Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Reviewed-by: André Almeida <andrealmeid@collabora.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 43f2517955875be5d96b641fba33d73097fe3cd9
Author: Anitha Chrisanthus <anitha.chrisanthus@intel.com>
Date:   Thu Jan 27 10:45:46 2022 -0800

    drm/kmb: Fix for build errors with Warray-bounds
    
    This fixes the following build error
    
    drivers/gpu/drm/kmb/kmb_plane.c: In function 'kmb_plane_atomic_disable':
    drivers/gpu/drm/kmb/kmb_plane.c:165:34: error: array subscript 3 is above array bounds of 'struct layer_status[2]' [-Werror=array-bounds]
      165 |                 kmb->plane_status[plane_id].ctrl =
      LCD_CTRL_GL2_ENABLE;
      |                 ~~~~~~~~~~~~~~~~~^~~~~~~~~~
      In file included from drivers/gpu/drm/kmb/kmb_plane.c:17:
      drivers/gpu/drm/kmb/kmb_drv.h:61:41: note: while referencing 'plane_status'
      61 |         struct layer_status  plane_status[KMB_MAX_PLANES];
      |                                         ^~~~~~~~~~~~
      drivers/gpu/drm/kmb/kmb_plane.c:162:34: error: array subscript 2 is above array bounds of 'struct layer_status[2]' [-Werror=array-bounds]
      162 |  kmb->plane_status[plane_id].ctrl =  LCD_CTRL_GL1_ENABLE;
      |                 ~~~~~~~~~~~~~~~~~^~~~~~~~~~
      In file included from
      drivers/gpu/drm/kmb/kmb_plane.c:17:
      drivers/gpu/drm/kmb/kmb_drv.h:61:41: note: while referencing 'plane_status'
      61 |         struct layer_status  plane_status[KMB_MAX_PLANES];
      |
      ^~~~~~~~~~~~
    
    Fixes: 7f7b96a8a0a1 ("drm/kmb: Add support for KeemBay Display")
    Signed-off-by: Anitha Chrisanthus <anitha.chrisanthus@intel.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220127194227.2213608-1-anitha.chrisanthus@intel.com

commit 708e8af4924ec2fdd5b81fe09192c6bac2f86935
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Tue Jan 25 19:50:34 2022 +0530

    arm64: errata: Add detection for TRBE trace data corruption
    
    TRBE implementations affected by Arm erratum #1902691 might corrupt trace
    data or deadlock, when it's being written into the memory. So effectively
    TRBE is broken and hence cannot be used to capture trace data. This adds
    a new errata ARM64_ERRATUM_1902691 in arm64 errata framework.
    
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-doc@vger.kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Link: https://lore.kernel.org/r/1643120437-14352-5-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

commit 3bd94a8759de9b724b83a80942b0354acd7701eb
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Tue Jan 25 19:50:33 2022 +0530

    arm64: errata: Add detection for TRBE invalid prohibited states
    
    TRBE implementations affected by Arm erratum #2038923 might get TRBE into
    an inconsistent view on whether trace is prohibited within the CPU. As a
    result, the trace buffer or trace buffer state might be corrupted. This
    happens after TRBE buffer has been enabled by setting TRBLIMITR_EL1.E,
    followed by just a single context synchronization event before execution
    changes from a context, in which trace is prohibited to one where it isn't,
    or vice versa. In these mentioned conditions, the view of whether trace is
    prohibited is inconsistent between parts of the CPU, and the trace buffer
    or the trace buffer state might be corrupted. This adds a new errata
    ARM64_ERRATUM_2038923 in arm64 errata framework.
    
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-doc@vger.kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Link: https://lore.kernel.org/r/1643120437-14352-4-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

commit 607a9afaae09cde21ece458a8f10cb99d3f94f14
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Tue Jan 25 19:50:32 2022 +0530

    arm64: errata: Add detection for TRBE ignored system register writes
    
    TRBE implementations affected by Arm erratum #2064142 might fail to write
    into certain system registers after the TRBE has been disabled. Under some
    conditions after TRBE has been disabled, writes into certain TRBE registers
    TRBLIMITR_EL1, TRBPTR_EL1, TRBBASER_EL1, TRBSR_EL1 and TRBTRG_EL1 will be
    ignored and not be effected. This adds a new errata ARM64_ERRATUM_2064142
    in arm64 errata framework.
    
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-doc@vger.kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Link: https://lore.kernel.org/r/1643120437-14352-3-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

commit 53960faf2b731dd2f9ed6e1334634b8ba6286850
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Tue Jan 25 19:50:31 2022 +0530

    arm64: Add Cortex-A510 CPU part definition
    
    Add the CPU Partnumbers for the new Arm designs.
    
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Link: https://lore.kernel.org/r/1643120437-14352-2-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>

commit 23a46422c56144939c091c76cf389aa863ce9c18
Merge: a0f90c8815706 fd20d9738395c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 27 20:58:39 2022 +0200

    Merge tag 'net-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from netfilter and can.
    
      Current release - new code bugs:
    
       - tcp: add a missing sk_defer_free_flush() in tcp_splice_read()
    
       - tcp: add a stub for sk_defer_free_flush(), fix CONFIG_INET=n
    
       - nf_tables: set last expression in register tracking area
    
       - nft_connlimit: fix memleak if nf_ct_netns_get() fails
    
       - mptcp: fix removing ids bitmap setting
    
       - bonding: use rcu_dereference_rtnl when getting active slave
    
       - fix three cases of sleep in atomic context in drivers: lan966x, gve
    
       - handful of build fixes for esoteric drivers after netdev->dev_addr
         was made const
    
      Previous releases - regressions:
    
       - revert "ipv6: Honor all IPv6 PIO Valid Lifetime values", it broke
         Linux compatibility with USGv6 tests
    
       - procfs: show net device bound packet types
    
       - ipv4: fix ip option filtering for locally generated fragments
    
       - phy: broadcom: hook up soft_reset for BCM54616S
    
      Previous releases - always broken:
    
       - ipv4: raw: lock the socket in raw_bind()
    
       - ipv4: decrease the use of shared IPID generator to decrease the
         chance of attackers guessing the values
    
       - procfs: fix cross-netns information leakage in /proc/net/ptype
    
       - ethtool: fix link extended state for big endian
    
       - bridge: vlan: fix single net device option dumping
    
       - ping: fix the sk_bound_dev_if match in ping_lookup"
    
    * tag 'net-5.17-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (86 commits)
      net: bridge: vlan: fix memory leak in __allowed_ingress
      net: socket: rename SKB_DROP_REASON_SOCKET_FILTER
      ipv4: remove sparse error in ip_neigh_gw4()
      ipv4: avoid using shared IP generator for connected sockets
      ipv4: tcp: send zero IPID in SYNACK messages
      ipv4: raw: lock the socket in raw_bind()
      MAINTAINERS: add missing IPv4/IPv6 header paths
      MAINTAINERS: add more files to eth PHY
      net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
      net: bridge: vlan: fix single net device option dumping
      net: stmmac: skip only stmmac_ptp_register when resume from suspend
      net: stmmac: configure PTP clock source prior to PTP initialization
      Revert "ipv6: Honor all IPv6 PIO Valid Lifetime values"
      connector/cn_proc: Use task_is_in_init_pid_ns()
      pid: Introduce helper task_is_in_init_pid_ns()
      gve: Fix GFP flags when allocing pages
      net: lan966x: Fix sleep in atomic context when updating MAC table
      net: lan966x: Fix sleep in atomic context when injecting frames
      ethernet: seeq/ether3: don't write directly to netdev->dev_addr
      ethernet: 8390/etherh: don't write directly to netdev->dev_addr
      ...

commit 854d0982eef0e424e8108d09d9275aaf445b1597
Author: Paul Menzel <pmenzel@molgen.mpg.de>
Date:   Mon Jan 17 12:13:37 2022 +0100

    docs/vm: Fix typo in *harden*
    
    Fixes: df4e817b7108 ("mm: page table check")
    Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Link: https://lore.kernel.org/r/20220117111338.115455-1-pmenzel@molgen.mpg.de
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 573fe46e398f4b451d075e854d221f6197941540
Author: Pali Rohár <pali@kernel.org>
Date:   Fri Jan 21 12:58:04 2022 +0100

    Documentation: arm: marvell: Extend Avanta list
    
    Include another two SoCs from Avanta family.
    
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Link: https://lore.kernel.org/r/20220121115804.28824-1-pali@kernel.org
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 10855b45a428d8888b1a111d7f607c32a6a49a06
Author: Takahiro Itazuri <itazur@amazon.com>
Date:   Mon Jan 24 17:14:47 2022 +0900

    docs: fix typo in Documentation/kernel-hacking/locking.rst
    
    Change copy_from_user*( to copy_from_user() .
    
    Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
    Link: https://lore.kernel.org/r/20220124081447.34066-1-itazur@amazon.com
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 941518d6538afa5ea0edc26e6c009d0b3163d422
Author: Jonathan Corbet <corbet@lwn.net>
Date:   Thu Jan 20 17:00:33 2022 -0700

    docs: Hook the RTLA documents into the kernel docs build
    
    The RTLA documents were added to Documentation/ but never hooked into the
    rest of the docs build, leading to a bunch of warnings like:
    
      Documentation/tools/rtla/rtla-osnoise.rst: WARNING: document isn't included in any toctree
    
    Add some basic glue to wire these documents into the build so that they are
    available with the rest of the rendered docs.  No attempt has been made to
    turn the RTLA docs into proper RST files rather than warmed-over man pages;
    that is an exercise for the future.
    
    Fixes: d40d48e1f1f2 ("rtla: Add Documentation")
    Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
    Link: https://lore.kernel.org/r/877dau555q.fsf@meer.lwn.net
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 908a26e139e8cf21093acc56d8e90ddad2ad1eff
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Thu Jan 27 21:33:45 2022 +0500

    selftests/exec: Remove pipe from TEST_GEN_FILES
    
    pipe named FIFO special file is being created in execveat.c to perform
    some tests. Makefile doesn't need to do anything with the pipe. When it
    isn't found, Makefile generates the following build error:
    
    make: *** No rule to make target
    '../tools/testing/selftests/exec/pipe', needed by 'all'.  Stop.
    
    pipe is created and removed during test run-time.
    
    Amended change log to add pipe remove info:
    Shuah Khan <skhan@linuxfoundation.org>
    
    Fixes: 61016db15b8e ("selftests/exec: Verify execve of non-regular files fail")
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 01dabed20573804750af5c7bf8d1598a6bf7bf6e
Author: Yang Xu <xuyang2018.jy@fujitsu.com>
Date:   Thu Jan 27 17:11:37 2022 +0800

    selftests/zram: Adapt the situation that /dev/zram0 is being used
    
    If zram-generator package is installed and works, then we can not remove
    zram module because zram swap is being used. This case needs a clean zram
    environment, change this test by using hot_add/hot_remove interface. So
    even zram device is being used, we still can add zram device and remove
    them in cleanup.
    
    The two interface was introduced since kernel commit 6566d1a32bf7("zram:
    add dynamic device add/remove functionality") in v4.2-rc1. If kernel
    supports these two interface, we use hot_add/hot_remove to slove this
    problem, if not, just check whether zram is being used or built in, then
    skip it on old kernel.
    
    Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit d18da7ec3719559d6e74937266d0416e6c7e0b31
Author: Yang Xu <xuyang2018.jy@fujitsu.com>
Date:   Thu Jan 27 17:11:36 2022 +0800

    selftests/zram01.sh: Fix compression ratio calculation
    
    zram01 uses `free -m` to measure zram memory usage. The results are no
    sense because they are polluted by all running processes on the system.
    
    We Should only calculate the free memory delta for the current process.
    So use the third field of /sys/block/zram<id>/mm_stat to measure memory
    usage instead. The file is available since kernel 4.1.
    
    orig_data_size(first): uncompressed size of data stored in this disk.
    compr_data_size(second): compressed size of data stored in this disk
    mem_used_total(third): the amount of memory allocated for this disk
    
    Also remove useless zram cleanup call in zram_fill_fs and so we don't
    need to cleanup zram twice if fails.
    
    Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit fc4eb486a59d70bd35cf1209f0e68c2d8b979193
Author: Yang Xu <xuyang2018.jy@fujitsu.com>
Date:   Thu Jan 27 17:11:35 2022 +0800

    selftests/zram: Skip max_comp_streams interface on newer kernel
    
    Since commit 43209ea2d17a ("zram: remove max_comp_streams internals"), zram
    has switched to per-cpu streams. Even kernel still keep this interface for
    some reasons, but writing to max_comp_stream doesn't take any effect. So
    skip it on newer kernel ie 4.7.
    
    The code that comparing kernel version is from xfstests testsuite ext4/053.
    
    Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit dede34b2c1a88e26f8353b433e381ea355f7258d
Author: Shuah Khan <skhan@linuxfoundation.org>
Date:   Wed Jan 26 13:13:41 2022 -0700

    docs/kselftest: clarify running mainline tests on stables
    
    Update the document to clarifiy support for running mainline
    kselftest on stable releases and the reasons for not removing
    test code that can test older kernels.
    
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit ebea268ea583ba4970df425dfef8c8e21d0a4e12
Author: Jon Hunter <jonathanh@nvidia.com>
Date:   Thu Jan 13 14:31:52 2022 +0000

    arm64: tegra: Disable ISO SMMU for Tegra194
    
    Commit e762232f9466 ("arm64: tegra: Add ISO SMMU controller for Tegra194")
    added the ISO SMMU for display devices on Tegra194. The SMMU is enabled by
    default but not hooked up to the display controllers yet because we do not
    have a way to pass frame-buffer memory from the bootloader to the kernel.
    However, even though the SMMU is not hooked up to the display controllers'
    SMMU faults are being seen if a display is connected. Therefore, keep the
    ISO SMMU disabled by default for now.
    
    Fixes: e762232f9466 ("arm64: tegra: Add ISO SMMU controller for Tegra194")
    Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit 22d7ee32f1fb6d51ef8cf657c6685ca04745755a
Author: Dmitry Osipenko <digetx@gmail.com>
Date:   Thu Dec 23 17:46:50 2021 +0300

    gpu: host1x: Fix hang on Tegra186+
    
    Tegra186+ hangs if host1x hardware is disabled at a kernel boot time
    because we touch hardware before runtime PM is resumed. Move sync point
    assignment initialization to the RPM-resume callback. Older SoCs were
    unaffected because they skip that sync point initialization.
    
    Tested-by: Jon Hunter <jonathanh@nvidia.com> # T186
    Reported-by: Jon Hunter <jonathanh@nvidia.com> # T186
    Fixes: 6b6776e2ab8a ("gpu: host1x: Add initial runtime PM and OPP support")
    Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
    Signed-off-by: Thierry Reding <treding@nvidia.com>

commit f6133fbd373811066c8441737e65f384c8f31974
Author: Usama Arif <usama.arif@bytedance.com>
Date:   Thu Jan 27 14:04:44 2022 +0000

    io_uring: remove unused argument from io_rsrc_node_alloc
    
    io_ring_ctx is not used in the function.
    
    Signed-off-by: Usama Arif <usama.arif@bytedance.com>
    Link: https://lore.kernel.org/r/20220127140444.4016585-1-usama.arif@bytedance.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 10825410b956dc1ed8c5fbc8bbedaffdadde7f20
Author: Laibin Qiu <qiulaibin@huawei.com>
Date:   Thu Jan 27 18:00:47 2022 +0800

    blk-mq: Fix wrong wakeup batch configuration which will cause hang
    
    Commit 180dccb0dba4f ("blk-mq: fix tag_get wait task can't be
    awakened") will recalculate wake_batch when incrementing or decrementing
    active_queues to avoid wake_batch > hctx_max_depth. At the same time, in
    order to not affect performance as much as possible, the minimum wakeup
    batch is set to 4. But when the QD is small (such as QD=1), if inc or dec
    active_queues increases wakeup batch, that can lead to a hang:
    
    Fix this problem with the following strategies:
    QD          :  >= 32 | < 32
    ---------------------------------
    wakeup batch:  8~4   | 3~1
    
    Fixes: 180dccb0dba4f ("blk-mq: fix tag_get wait task can't be awakened")
    Link: https://lore.kernel.org/linux-block/78cafe94-a787-e006-8851-69906f0c2128@huawei.com/T/#t
    Reported-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
    Signed-off-by: Laibin Qiu <qiulaibin@huawei.com>
    Tested-by: Alex Xu (Hello71) <alex_y_xu@yahoo.ca>
    Link: https://lore.kernel.org/r/20220127100047.1763746-1-qiulaibin@huawei.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit fd20d9738395cf8e27d0a17eba34169699fccdff
Author: Tim Yi <tim.yi@pica8.com>
Date:   Thu Jan 27 15:49:53 2022 +0800

    net: bridge: vlan: fix memory leak in __allowed_ingress
    
    When using per-vlan state, if vlan snooping and stats are disabled,
    untagged or priority-tagged ingress frame will go to check pvid state.
    If the port state is forwarding and the pvid state is not
    learning/forwarding, untagged or priority-tagged frame will be dropped
    but skb memory is not freed.
    Should free skb when __allowed_ingress returns false.
    
    Fixes: a580c76d534c ("net: bridge: vlan: add per-vlan state")
    Signed-off-by: Tim Yi <tim.yi@pica8.com>
    Acked-by: Nikolay Aleksandrov <nikolay@nvidia.com>
    Link: https://lore.kernel.org/r/20220127074953.12632-1-tim.yi@pica8.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit b07f413732549e5a96e891411fbb5980f2d8e5a1
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Thu Jan 27 13:40:38 2022 +0100

    netfilter: nf_tables: remove assignment with no effect in chain blob builder
    
    cppcheck possible warnings:
    
    >> net/netfilter/nf_tables_api.c:2014:2: warning: Assignment of function parameter has no effect outside the function. Did you forget dereferencing it? [uselessAssignmentPtrArg]
        ptr += offsetof(struct nft_rule_dp, data);
        ^
    
    Reported-by: kernel test robot <yujie.liu@intel.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 364df53c081d93fcfd6b91085ff2650c7f17b3c7
Author: Menglong Dong <imagedong@tencent.com>
Date:   Thu Jan 27 17:13:01 2022 +0800

    net: socket: rename SKB_DROP_REASON_SOCKET_FILTER
    
    Rename SKB_DROP_REASON_SOCKET_FILTER, which is used
    as the reason of skb drop out of socket filter before
    it's part of a released kernel. It will be used for
    more protocols than just TCP in future series.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Link: https://lore.kernel.org/all/20220127091308.91401-2-imagedong@tencent.com/
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3c42b2019863b327caa233072c50739d4144dd16
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 26 17:34:04 2022 -0800

    ipv4: remove sparse error in ip_neigh_gw4()
    
    ./include/net/route.h:373:48: warning: incorrect type in argument 2 (different base types)
    ./include/net/route.h:373:48:    expected unsigned int [usertype] key
    ./include/net/route.h:373:48:    got restricted __be32 [usertype] daddr
    
    Fixes: 5c9f7c1dfc2e ("ipv4: Add helpers for neigh lookup for nexthop")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Link: https://lore.kernel.org/r/20220127013404.1279313-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3ede6465e756651ff5bd9b495d6cacd5ec8216e5
Merge: 153a0d187e767 23f57406b82de
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 27 08:37:05 2022 -0800

    Merge branch 'ipv4-less-uses-of-shared-ip-generator'
    
    Eric Dumazet says:
    
    ====================
    ipv4: less uses of shared IP generator
    
    From: Eric Dumazet <edumazet@google.com>
    
    We keep receiving research reports based on linux IPID generation.
    
    Before breaking part of the Internet by switching to pure
    random generator, this series reduces the need for the
    shared IP generator for TCP sockets.
    ====================
    
    Link: https://lore.kernel.org/r/20220127011022.1274803-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 23f57406b82de51809d5812afd96f210f8b627f3
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 26 17:10:22 2022 -0800

    ipv4: avoid using shared IP generator for connected sockets
    
    ip_select_ident_segs() has been very conservative about using
    the connected socket private generator only for packets with IP_DF
    set, claiming it was needed for some VJ compression implementations.
    
    As mentioned in this referenced document, this can be abused.
    (Ref: Off-Path TCP Exploits of the Mixed IPID Assignment)
    
    Before switching to pure random IPID generation and possibly hurt
    some workloads, lets use the private inet socket generator.
    
    Not only this will remove one vulnerability, this will also
    improve performance of TCP flows using pmtudisc==IP_PMTUDISC_DONT
    
    Fixes: 73f156a6e8c1 ("inetpeer: get rid of ip_id_count")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Reported-by: Ray Che <xijiache@gmail.com>
    Cc: Willy Tarreau <w@1wt.eu>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 970a5a3ea86da637471d3cd04d513a0755aba4bf
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 26 17:10:21 2022 -0800

    ipv4: tcp: send zero IPID in SYNACK messages
    
    In commit 431280eebed9 ("ipv4: tcp: send zero IPID for RST and
    ACK sent in SYN-RECV and TIME-WAIT state") we took care of some
    ctl packets sent by TCP.
    
    It turns out we need to use a similar strategy for SYNACK packets.
    
    By default, they carry IP_DF and IPID==0, but there are ways
    to ask them to use the hashed IP ident generator and thus
    be used to build off-path attacks.
    (Ref: Off-Path TCP Exploits of the Mixed IPID Assignment)
    
    One of this way is to force (before listener is started)
    echo 1 >/proc/sys/net/ipv4/ip_no_pmtu_disc
    
    Another way is using forged ICMP ICMP_FRAG_NEEDED
    with a very small MTU (like 68) to force a false return from
    ip_dont_fragment()
    
    In this patch, ip_build_and_send_pkt() uses the following
    heuristics.
    
    1) Most SYNACK packets are smaller than IPV4_MIN_MTU and therefore
    can use IP_DF regardless of the listener or route pmtu setting.
    
    2) In case the SYNACK packet is bigger than IPV4_MIN_MTU,
    we use prandom_u32() generator instead of the IPv4 hashed ident one.
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: Ray Che <xijiache@gmail.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Cc: Geoff Alexander <alexandg@cs.unm.edu>
    Cc: Willy Tarreau <w@1wt.eu>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a0f90c8815706981c483a652a6aefca51a5e191c
Author: Mathias Krause <minipli@grsecurity.net>
Date:   Thu Jan 27 18:34:19 2022 +1000

    drm/vmwgfx: Fix stale file descriptors on failed usercopy
    
    A failing usercopy of the fence_rep object will lead to a stale entry in
    the file descriptor table as put_unused_fd() won't release it. This
    enables userland to refer to a dangling 'file' object through that still
    valid file descriptor, leading to all kinds of use-after-free
    exploitation scenarios.
    
    Fix this by deferring the call to fd_install() until after the usercopy
    has succeeded.
    
    Fixes: c906965dee22 ("drm/vmwgfx: Add export fence to file descriptor support")
    Signed-off-by: Mathias Krause <minipli@grsecurity.net>
    Signed-off-by: Zack Rusin <zackr@vmware.com>
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d19a7af73b5ecaac8168712d18be72b9db166768
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Tue Jan 18 17:00:51 2022 -0500

    lockd: fix failure to cleanup client locks
    
    In my testing, we're sometimes hitting the request->fl_flags & FL_EXISTS
    case in posix_lock_inode, presumably just by random luck since we're not
    actually initializing fl_flags here.
    
    This probably didn't matter before commit 7f024fcd5c97 ("Keep read and
    write fds with each nlm_file") since we wouldn't previously unlock
    unless we knew there were locks.
    
    But now it causes lockd to give up on removing more locks.
    
    We could just initialize fl_flags, but really it seems dubious to be
    calling vfs_lock_file with random values in some of the fields.
    
    Fixes: 7f024fcd5c97 ("Keep read and write fds with each nlm_file")
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    [ cel: fixed checkpatch.pl nit ]
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 153a0d187e767c68733b8e9f46218eb1f41ab902
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 26 16:51:16 2022 -0800

    ipv4: raw: lock the socket in raw_bind()
    
    For some reason, raw_bind() forgot to lock the socket.
    
    BUG: KCSAN: data-race in __ip4_datagram_connect / raw_bind
    
    write to 0xffff8881170d4308 of 4 bytes by task 5466 on cpu 0:
     raw_bind+0x1b0/0x250 net/ipv4/raw.c:739
     inet_bind+0x56/0xa0 net/ipv4/af_inet.c:443
     __sys_bind+0x14b/0x1b0 net/socket.c:1697
     __do_sys_bind net/socket.c:1708 [inline]
     __se_sys_bind net/socket.c:1706 [inline]
     __x64_sys_bind+0x3d/0x50 net/socket.c:1706
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffff8881170d4308 of 4 bytes by task 5468 on cpu 1:
     __ip4_datagram_connect+0xb7/0x7b0 net/ipv4/datagram.c:39
     ip4_datagram_connect+0x2a/0x40 net/ipv4/datagram.c:89
     inet_dgram_connect+0x107/0x190 net/ipv4/af_inet.c:576
     __sys_connect_file net/socket.c:1900 [inline]
     __sys_connect+0x197/0x1b0 net/socket.c:1917
     __do_sys_connect net/socket.c:1927 [inline]
     __se_sys_connect net/socket.c:1924 [inline]
     __x64_sys_connect+0x3d/0x50 net/socket.c:1924
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x00000000 -> 0x0003007f
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 5468 Comm: syz-executor.5 Not tainted 5.17.0-rc1-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 966f435add4821f53bf1c507dadc3ba9aaeb5f01
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 26 14:55:35 2022 -0800

    MAINTAINERS: add missing IPv4/IPv6 header paths
    
    Add missing headers to the IP entry.
    
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 492fefbaafb9d9f49d8d14614d57c956a81f2ea1
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 26 12:24:24 2022 -0800

    MAINTAINERS: add more files to eth PHY
    
    include/linux/linkmode.h and include/linux/mii.h
    do not match anything in MAINTAINERS. Looks like
    they should be under Ethernet PHY.
    
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3c8cef9f3d86d9bf3402f5b397f92fc7026f78b6
Merge: 592ee1197f78b a5f3851b7f795
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Jan 27 06:52:50 2022 -0700

    Merge tag 'nvme-5.17-2022-01-27' of git://git.infradead.org/nvme into block-5.17
    
    Pull NVMe fixes from Christoph:
    
    "nvme fixes for Linux 5.17
    
     - add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs (Wu Zheng)
     - remove the unneeded ret variable in nvmf_dev_show (Changcheng Deng)"
    
    * tag 'nvme-5.17-2022-01-27' of git://git.infradead.org/nvme:
      nvme-fabrics: remove the unneeded ret variable in nvmf_dev_show
      nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs

commit 9e0db41e7a0b6f1271cbcfb16dbf5b8641b4e440
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Thu Jan 27 00:52:15 2022 +0800

    net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
    
    When readl_poll_timeout() timeout, we'd better directly use its return
    value.
    
    Before this patch:
    [    2.145528] dwmac-sun8i: probe of 4500000.ethernet failed with error -14
    
    After this patch:
    [    2.138520] dwmac-sun8i: probe of 4500000.ethernet failed with error -110
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dcb2c5c6ca9b9177f04abaf76e5a983d177c9414
Author: Nikolay Aleksandrov <nikolay@nvidia.com>
Date:   Wed Jan 26 15:10:25 2022 +0200

    net: bridge: vlan: fix single net device option dumping
    
    When dumping vlan options for a single net device we send the same
    entries infinitely because user-space expects a 0 return at the end but
    we keep returning skb->len and restarting the dump on retry. Fix it by
    returning the value from br_vlan_dump_dev() if it completed or there was
    an error. The only case that must return skb->len is when the dump was
    incomplete and needs to continue (-EMSGSIZE).
    
    Reported-by: Benjamin Poirier <bpoirier@nvidia.com>
    Fixes: 8dcea187088b ("net: bridge: vlan: add rtm definitions and dump support")
    Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit aa44323e1c4d2e896f5f271c202a13f4c45e5b40
Merge: 36268983e9031 0735e639f129d
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 27 13:46:18 2022 +0000

    Merge branch 'stmmac-ptp-fix'
    
    Mohammad Athari Bin Ismail says:
    
    ====================
    Fix PTP issue in stmmac
    
    This patch series to fix PTP issue in stmmac related to:
    1/ PTP clock source configuration during initialization.
    2/ PTP initialization during resume from suspend.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0735e639f129dff455aeb91da291f5c578cc33db
Author: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
Date:   Wed Jan 26 17:47:23 2022 +0800

    net: stmmac: skip only stmmac_ptp_register when resume from suspend
    
    When resume from suspend, besides skipping PTP registration, it also
    skipping PTP HW initialization. This could cause PTP clock not able to
    operate properly when resume from suspend.
    
    To fix this, only stmmac_ptp_register() is skipped when resume from
    suspend.
    
    Fixes: fe1319291150 ("stmmac: Don't init ptp again when resume from suspend/hibernation")
    Cc: <stable@vger.kernel.org> # 5.15.x
    Signed-off-by: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 94c82de43e01ef5747a95e4a590880de863fe423
Author: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
Date:   Wed Jan 26 17:47:22 2022 +0800

    net: stmmac: configure PTP clock source prior to PTP initialization
    
    For Intel platform, it is required to configure PTP clock source prior PTP
    initialization in MAC. So, need to move ptp_clk_freq_config execution from
    stmmac_ptp_register() to stmmac_init_ptp().
    
    Fixes: 76da35dc99af ("stmmac: intel: Add PSE and PCH PTP clock source selection")
    Cc: <stable@vger.kernel.org> # 5.15.x
    Signed-off-by: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3da4b7403db87d39bc2613cfd790de1de99a70ab
Author: Tom Rix <trix@redhat.com>
Date:   Wed Jan 26 10:21:42 2022 -0800

    ALSA: usb-audio: initialize variables that could ignore errors
    
    clang static analysis reports this representative issue
    mixer.c:1548:35: warning: Assigned value is garbage or undefined
            ucontrol->value.integer.value[0] = val;
                                             ^ ~~~
    
    The filter_error() macro allows errors to be ignored.
    If errors can be ignored, initialize variables
    so garbage will not be used.
    
    Fixes: 48cc42973509 ("ALSA: usb-audio: Filter error from connector kctl ops, too")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Link: https://lore.kernel.org/r/20220126182142.1184819-1-trix@redhat.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 36268983e90316b37000a005642af42234dabb36
Author: Guillaume Nault <gnault@redhat.com>
Date:   Wed Jan 26 16:38:52 2022 +0100

    Revert "ipv6: Honor all IPv6 PIO Valid Lifetime values"
    
    This reverts commit b75326c201242de9495ff98e5d5cff41d7fc0d9d.
    
    This commit breaks Linux compatibility with USGv6 tests. The RFC this
    commit was based on is actually an expired draft: no published RFC
    currently allows the new behaviour it introduced.
    
    Without full IETF endorsement, the flash renumbering scenario this
    patch was supposed to enable is never going to work, as other IPv6
    equipements on the same LAN will keep the 2 hours limit.
    
    Fixes: b75326c20124 ("ipv6: Honor all IPv6 PIO Valid Lifetime values")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 626b2dda7651a7c766108db4cdc0825db05b980d
Merge: 96b5590a48610 7a534ae89e34e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 27 11:23:26 2022 +0200

    Merge tag 'rpmsg-v5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux
    
    Pull rpmsg fixes from Bjorn Andersson:
     "The cdev cleanup in the rpmsg_char driver was not performed properly,
      resulting in unpredicable behaviour when the parent remote processor
      is stopped with any of the cdevs open by a client.
    
      Two patches transitions the implementation to use cdev_device_add()
      and cdev_del_device(), to capture the relationship between the two
      objects, and relocates the incorrectly placed cdev_del()"
    
    * tag 'rpmsg-v5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux:
      rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev
      rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev

commit 96b5590a486106206f2dab7b28555b5b1a8751c5
Merge: 0280e3c58f92b eee412e968f7b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 27 11:19:20 2022 +0200

    Merge tag 'rproc-v5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux
    
    Pull remoteproc fix from Bjorn Andersson:
     "The interaction between the various Qualcomm remoteproc drivers and
      the Qualcomm 'QMP' driver (used to communicate with the
      power-management hardware) was reworked in v5.17-rc1, but failed to
      account for the new Kconfig dependency"
    
    * tag 'rproc-v5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux:
      remoteproc: qcom: q6v5: fix service routines build errors

commit fa62f39dc7e25fc16371b958ac59b9a6fd260bea
Author: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date:   Tue Jan 25 15:19:44 2022 +0100

    MIPS: Fix build error due to PTR used in more places
    
    Use PTR_WD instead of PTR to avoid clashes with other parts.
    
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit d1ad2721b1eb05d54e81393a7ebc332d4a35c68f
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 27 08:33:04 2022 +0100

    kbuild: remove include/linux/cyclades.h from header file check
    
    The file now rightfully throws up a big warning that it should never be
    included, so remove it from the header_check test.
    
    Fixes: f23653fe6447 ("tty: Partially revert the removal of the Cyclades public API")
    Cc: stable <stable@vger.kernel.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: "Maciej W. Rozycki" <macro@embecosm.com>
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Reported-by: kernel test robot <lkp@intel.com>
    Link: https://lore.kernel.org/r/20220127073304.42399-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5d8a8b324ff48c9d9fe4f1634e33dc647d2481b4
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:26 2022 +0100

    MAINTAINERS: Remove Harry Morris bouncing address
    
    Harry's e-mail address from Cascoda bounces, I have not found any
    contributions from him since 2018 so let's drop the Maintainer entry
    from the CA8210 driver and mark it Orphan.
    
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-7-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit 79c37ca73a6e9a33f7b2b7783ba6af07a448c8a9
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:25 2022 +0100

    net: ieee802154: Return meaningful error codes from the netlink helpers
    
    Returning -1 does not indicate anything useful.
    
    Use a standard and meaningful error code instead.
    
    Fixes: a26c5fd7622d ("nl802154: add support for security layer")
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-6-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit 621b24b09eb61c63f262da0c9c5f0e93348897e5
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:24 2022 +0100

    net: ieee802154: ca8210: Stop leaking skb's
    
    Upon error the ieee802154_xmit_complete() helper is not called. Only
    ieee802154_wake_queue() is called manually. We then leak the skb
    structure.
    
    Free the skb structure upon error before returning.
    
    Fixes: ded845a781a5 ("ieee802154: Add CA8210 IEEE 802.15.4 device driver")
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-5-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit e5ce576d45bf72fd0e3dc37eff897bfcc488f6a9
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:23 2022 +0100

    net: ieee802154: at86rf230: Stop leaking skb's
    
    Upon error the ieee802154_xmit_complete() helper is not called. Only
    ieee802154_wake_queue() is called manually. In the Tx case we then leak
    the skb structure.
    
    Free the skb structure upon error before returning when appropriate.
    
    As the 'is_tx = 0' cannot be moved in the complete handler because of a
    possible race between the delay in switching to STATE_RX_AACK_ON and a
    new interrupt, we introduce an intermediate 'was_tx' boolean just for
    this purpose.
    
    There is no Fixes tag applying here, many changes have been made on this
    area and the issue kind of always existed.
    
    Suggested-by: Alexander Aring <alex.aring@gmail.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-4-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit d753c4004820a888ec007dd88b271fa9c3172c5c
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:22 2022 +0100

    net: ieee802154: mcr20a: Fix lifs/sifs periods
    
    These periods are expressed in time units (microseconds) while 40 and 12
    are the number of symbol durations these periods will last. We need to
    multiply them both with phy->symbol_duration in order to get these
    values in microseconds.
    
    Fixes: 8c6ad9cc5157 ("ieee802154: Add NXP MCR20A IEEE 802.15.4 transceiver driver")
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-3-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit 1293fccc9e892712d910ec96079d3717307f1d2d
Author: Miquel Raynal <miquel.raynal@bootlin.com>
Date:   Tue Jan 25 13:14:21 2022 +0100

    net: ieee802154: hwsim: Ensure proper channel selection at probe time
    
    Drivers are expected to set the PHY current_channel and current_page
    according to their default state. The hwsim driver is advertising being
    configured on channel 13 by default but that is not reflected in its own
    internal pib structure. In order to ensure that this driver consider the
    current channel as being 13 internally, we at least need to set the
    pib->channel field to 13.
    
    Fixes: f25da51fdc38 ("ieee802154: hwsim: add replacement for fakelb")
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    [stefan@datenfreihafen.org: fixed assigment from page to channel]
    Acked-by: Alexander Aring <aahringo@redhat.com>
    Link: https://lore.kernel.org/r/20220125121426.848337-2-miquel.raynal@bootlin.com
    Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>

commit a5f3851b7f7951e8d4ba0a9ba3b5308a5f250a2d
Author: Changcheng Deng <deng.changcheng@zte.com.cn>
Date:   Fri Jan 7 02:23:06 2022 +0000

    nvme-fabrics: remove the unneeded ret variable in nvmf_dev_show
    
    Remove unneeded variable and directly return 0.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Changcheng Deng <deng.changcheng@zte.com.cn>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 25e58af4be412d59e056da65cc1cefbd89185bd2
Author: Wu Zheng <wu.zheng@intel.com>
Date:   Mon Jun 21 19:07:01 2021 -0400

    nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs
    
    The Intel P4500/P4600 SSDs do not report a subsystem NQN despite claiming
    compliance to a standards version where reporting one is required.
    
    Add the IGNORE_DEV_SUBNQN quirk to not fail the initialization of a
    second such SSDs in a system.
    
    Signed-off-by: Zheng Wu <wu.zheng@intel.com>
    Signed-off-by: Ye Jinhe <jinhe.ye@intel.com>
    Reviewed-by: Keith Busch <kbusch@kernel.org>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

commit 46e994717807f4b935c44d81dde9dd8bcd9a4f5d
Author: Wan Jiabing <wanjiabing@vivo.com>
Date:   Fri Jan 7 10:50:50 2022 +0800

    phy: phy-mtk-tphy: Fix duplicated argument in phy-mtk-tphy
    
    Fix following coccicheck warning:
    ./drivers/phy/mediatek/phy-mtk-tphy.c:994:6-29: duplicated argument
    to && or ||
    
    The efuse_rx_imp is duplicate. Here should be efuse_tx_imp.
    
    Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
    Acked-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
    Link: https://lore.kernel.org/r/20220107025050.787720-1-wanjiabing@vivo.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit a6d95c5a628a09be129f25d5663a7e9db8261f51
Author: Jiri Bohac <jbohac@suse.cz>
Date:   Wed Jan 26 16:00:18 2022 +0100

    Revert "xfrm: xfrm_state_mtu should return at least 1280 for ipv6"
    
    This reverts commit b515d2637276a3810d6595e10ab02c13bfd0b63a.
    
    Commit b515d2637276a3810d6595e10ab02c13bfd0b63a ("xfrm: xfrm_state_mtu
    should return at least 1280 for ipv6") in v5.14 breaks the TCP MSS
    calculation in ipsec transport mode, resulting complete stalls of TCP
    connections. This happens when the (P)MTU is 1280 or slighly larger.
    
    The desired formula for the MSS is:
    MSS = (MTU - ESP_overhead) - IP header - TCP header
    
    However, the above commit clamps the (MTU - ESP_overhead) to a
    minimum of 1280, turning the formula into
    MSS = max(MTU - ESP overhead, 1280) -  IP header - TCP header
    
    With the (P)MTU near 1280, the calculated MSS is too large and the
    resulting TCP packets never make it to the destination because they
    are over the actual PMTU.
    
    The above commit also causes suboptimal double fragmentation in
    xfrm tunnel mode, as described in
    https://lore.kernel.org/netdev/20210429202529.codhwpc7w6kbudug@dwarf.suse.cz/
    
    The original problem the above commit was trying to fix is now fixed
    by commit 6596a0229541270fb8d38d989f91b78838e5e9da ("xfrm: fix MTU
    regression").
    
    Signed-off-by: Jiri Bohac <jbohac@suse.cz>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit cfc826c88a79e22ba5d8001556eb2c7efd8a01b6
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Wed Jan 12 14:17:24 2022 +0300

    phy: stm32: fix a refcount leak in stm32_usbphyc_pll_enable()
    
    This error path needs to decrement "usbphyc->n_pll_cons.counter" before
    returning.
    
    Fixes: 5b1af71280ab ("phy: stm32: rework PLL Lock detection")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220112111724.GB3019@kili
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 37291f60d0822f191748c2a54ce63b0bc669020f
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 25 18:16:00 2022 -0600

    phy: xilinx: zynqmp: Fix bus width setting for SGMII
    
    TX_PROT_BUS_WIDTH and RX_PROT_BUS_WIDTH are single registers with
    separate bit fields for each lane. The code in xpsgtr_phy_init_sgmii was
    not preserving the existing register value for other lanes, so enabling
    the PHY in SGMII mode on one lane zeroed out the settings for all other
    lanes, causing other PS-GTR peripherals such as USB3 to malfunction.
    
    Use xpsgtr_clr_set to only manipulate the desired bits in the register.
    
    Fixes: 4a33bea00314 ("phy: zynqmp: Add PHY driver for the Xilinx ZynqMP Gigabit Transceiver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Acked-by: Michal Simek <michal.simek@xilinx.com>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://lore.kernel.org/r/20220126001600.1592218-1-robert.hancock@calian.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit c7ec845f0eafc7c89efcd04a75a20d548e86beea
Merge: a92f7a6feeb38 42c66d1675640
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 26 18:57:12 2022 -0800

    Merge branch 'pid-introduce-helper-task_is_in_root_ns'
    
    Leo Yan says:
    
    ====================
    pid: Introduce helper task_is_in_root_ns()
    
    This patch series introduces a helper function task_is_in_init_pid_ns()
    to replace open code.  The two patches are extracted from the original
    series [1] for network subsystem.
    
    As a plan, we can firstly land this patch set into kernel 5.18; there
    have 5 patches are left out from original series [1], as a next step,
    I will resend them for appropriate linux-next merging.
    
    [1] https://lore.kernel.org/lkml/20211208083320.472503-1-leo.yan@linaro.org/
    ====================
    
    Link: https://lore.kernel.org/r/20220126050427.605628-1-leo.yan@linaro.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 42c66d16756402c4749d94f005a998a43e8fa338
Author: Leo Yan <leo.yan@linaro.org>
Date:   Wed Jan 26 13:04:27 2022 +0800

    connector/cn_proc: Use task_is_in_init_pid_ns()
    
    This patch replaces open code with task_is_in_init_pid_ns() to check if
    a task is in root PID namespace.
    
    Signed-off-by: Leo Yan <leo.yan@linaro.org>
    Acked-by: Balbir Singh <bsingharora@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d7e4f8545b497b3f5687e592f1c355cbaee64c8c
Author: Leo Yan <leo.yan@linaro.org>
Date:   Wed Jan 26 13:04:26 2022 +0800

    pid: Introduce helper task_is_in_init_pid_ns()
    
    Currently the kernel uses open code in multiple places to check if a
    task is in the root PID namespace with the kind of format:
    
      if (task_active_pid_ns(current) == &init_pid_ns)
          do_something();
    
    This patch creates a new helper function, task_is_in_init_pid_ns(), it
    returns true if a passed task is in the root PID namespace, otherwise
    returns false.  So it will be used to replace open codes.
    
    Suggested-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Signed-off-by: Leo Yan <leo.yan@linaro.org>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Acked-by: Balbir Singh <bsingharora@gmail.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a92f7a6feeb3884c69c1c7c1f13bccecb2228ad0
Author: Catherine Sullivan <csully@google.com>
Date:   Tue Jan 25 16:38:43 2022 -0800

    gve: Fix GFP flags when allocing pages
    
    Use GFP_ATOMIC when allocating pages out of the hotpath,
    continue to use GFP_KERNEL when allocating pages during setup.
    
    GFP_KERNEL will allow blocking which allows it to succeed
    more often in a low memory enviornment but in the hotpath we do
    not want to allow the allocation to block.
    
    Fixes: f5cedc84a30d2 ("gve: Add transmit and receive support")
    Signed-off-by: Catherine Sullivan <csully@google.com>
    Signed-off-by: David Awogbemila <awogbemila@google.com>
    Link: https://lore.kernel.org/r/20220126003843.3584521-1-awogbemila@google.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9b6d90e2085ca2ce72ef9ea78658bf270855e62e
Author: Zhou Qingyang <zhou1615@umn.edu>
Date:   Tue Jan 25 00:45:25 2022 +0800

    ata: pata_platform: Fix a NULL pointer dereference in __pata_platform_probe()
    
    In __pata_platform_probe(), devm_kzalloc() is assigned to ap->ops and
    there is a dereference of it right after that, which could introduce a
    NULL pointer dereference bug.
    
    Fix this by adding a NULL check of ap->ops.
    
    This bug was found by a static analyzer.
    
    Builds with 'make allyesconfig' show no new warnings,
    and our static analyzer no longer warns about this code.
    
    Fixes: f3d5e4f18dba ("ata: pata_of_platform: Allow to use 16-bit wide data transfer")
    Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>

commit f9d87929d451d3e649699d0f1d74f71f77ad38f5
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Jan 24 12:46:50 2022 -0600

    ucount:  Make get_ucount a safe get_user replacement
    
    When the ucount code was refactored to create get_ucount it was missed
    that some of the contexts in which a rlimit is kept elevated can be
    the only reference to the user/ucount in the system.
    
    Ordinary ucount references exist in places that also have a reference
    to the user namspace, but in POSIX message queues, the SysV shm code,
    and the SIGPENDING code there is no independent user namespace
    reference.
    
    Inspection of the the user_namespace show no instance of circular
    references between struct ucounts and the user_namespace.  So
    hold a reference from struct ucount to i's user_namespace to
    resolve this problem.
    
    Link: https://lore.kernel.org/lkml/YZV7Z+yXbsx9p3JN@fixkernel.com/
    Reported-by: Qian Cai <quic_qiancai@quicinc.com>
    Reported-by: Mathias Krause <minipli@grsecurity.net>
    Tested-by: Mathias Krause <minipli@grsecurity.net>
    Reviewed-by: Mathias Krause <minipli@grsecurity.net>
    Reviewed-by: Alexey Gladkov <legion@kernel.org>
    Fixes: d64696905554 ("Reimplement RLIMIT_SIGPENDING on top of ucounts")
    Fixes: 6e52a9f0532f ("Reimplement RLIMIT_MSGQUEUE on top of ucounts")
    Fixes: d7c9e99aee48 ("Reimplement RLIMIT_MEMLOCK on top of ucounts")
    Cc: stable@vger.kernel.org
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit eda0cf1202acf1ef47f93d8f92d4839213431424
Author: Florian Westphal <fw@strlen.de>
Date:   Wed Jan 26 12:54:54 2022 +0100

    selftests: nft_concat_range: add test for reload with no element add/del
    
    Add a specific test for the reload issue fixed with
    commit 23c54263efd7cb ("netfilter: nft_set_pipapo: allocate pcpu scratch maps on clone").
    
    Add to set, then flush set content + restore without other add/remove in
    the transaction.
    
    On kernels before the fix, this test case fails:
      net,mac with reload    [FAIL]
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit f459bfd4b9793f25e0fcf19878edd87d8dc569d9
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Wed Jan 26 01:46:58 2022 +0100

    netfilter: nft_byteorder: track register operations
    
    Cancel tracking for byteorder operation, otherwise selector + byteorder
    operation is incorrectly reduced if source and destination registers are
    the same.
    
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit aeac4554eb549037ff2f719200c0a9c1c25e7eaa
Author: Phil Sutter <phil@nwl.cc>
Date:   Tue Jan 25 20:06:03 2022 +0100

    netfilter: nft_reject_bridge: Fix for missing reply from prerouting
    
    Prior to commit fa538f7cf05aa ("netfilter: nf_reject: add reject skbuff
    creation helpers"), nft_reject_bridge did not assign to nskb->dev before
    passing nskb on to br_forward(). The shared skbuff creation helpers
    introduced in above commit do which seems to confuse br_forward() as
    reject statements in prerouting hook won't emit a packet anymore.
    
    Fix this by simply passing NULL instead of 'dev' to the helpers - they
    use the pointer for just that assignment, nothing else.
    
    Fixes: fa538f7cf05aa ("netfilter: nf_reject: add reject skbuff creation helpers")
    Signed-off-by: Phil Sutter <phil@nwl.cc>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit aad51ca71ad83273e8826d6cfdcf53c98748d1fa
Author: Florian Westphal <fw@strlen.de>
Date:   Mon Jan 24 22:09:15 2022 +0100

    selftests: netfilter: check stateless nat udp checksum fixup
    
    Add a test that sends large udp packet (which is fragmented)
    via a stateless nft nat rule, i.e. 'ip saddr set 10.2.3.4'
    and check that the datagram is received by peer.
    
    On kernels without
    commit 4e1860a38637 ("netfilter: nft_payload: do not update layer 4 checksum when mangling fragments")',
    this will fail with:
    
    cmp: EOF on /tmp/tmp.V1q0iXJyQF which is empty
    -rw------- 1 root root 4096 Jan 24 22:03 /tmp/tmp.Aaqnq4rBKS
    -rw------- 1 root root    0 Jan 24 22:03 /tmp/tmp.V1q0iXJyQF
    ERROR: in and output file mismatch when checking udp with stateless nat
    FAIL: nftables v1.0.0 (Fearless Fosdick #2)
    
    On patched kernels, this will show:
    PASS: IP statless for ns2-PFp89amx
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit c858620d2ae3489409af593f005a48a8a324da3d
Author: Florian Westphal <fw@strlen.de>
Date:   Sun Jan 23 15:45:54 2022 +0100

    selftests: netfilter: reduce zone stress test running time
    
    This selftests needs almost 3 minutes to complete, reduce the
    insertes zones to 1000.  Test now completes in about 20 seconds.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 34243b9ec856309339172b1507379074156947e8
Author: Florian Westphal <fw@strlen.de>
Date:   Sun Jan 23 15:24:00 2022 +0100

    netfilter: nft_ct: fix use after free when attaching zone template
    
    The conversion erroneously removed the refcount increment.
    In case we can use the percpu template, we need to increment
    the refcount, else it will be released when the skb gets freed.
    
    In case the slowpath is taken, the new template already has a
    refcount of 1.
    
    Fixes: 719774377622 ("netfilter: conntrack: convert to refcount_t api")
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 7355bfe0e0cc27597d530f78e259a985cb85af40
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Sun Jan 23 13:57:17 2022 +0100

    netfilter: Remove flowtable relics
    
    NF_FLOW_TABLE_IPV4 and NF_FLOW_TABLE_IPV6 are invisble, selected by
    nothing (so they can no longer be enabled), and their last real users
    have been removed (nf_flow_table_ipv6.c is empty).
    
    Clean up the leftovers.
    
    Fixes: c42ba4290b2147aa ("netfilter: flowtable: remove ipv4/ipv6 modules")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit da123016ca8cb5697366c0b2dd55059b976e67e4
Author: Paul E. McKenney <paulmck@kernel.org>
Date:   Wed Jan 26 10:42:58 2022 -0800

    rcu-tasks: Fix computation of CPU-to-list shift counts
    
    The ->percpu_enqueue_shift field is used to map from the running CPU
    number to the index of the corresponding callback list.  This mapping
    can change at runtime in response to varying callback load, resulting
    in varying levels of contention on the callback-list locks.
    
    Unfortunately, the initial value of this field is correct only if the
    system happens to have a power-of-two number of CPUs, otherwise the
    callbacks from the high-numbered CPUs can be placed into the callback list
    indexed by 1 (rather than 0), and those index-1 callbacks will be ignored.
    This can result in soft lockups and hangs.
    
    This commit therefore corrects this mapping, adding one to this shift
    count as needed for systems having odd numbers of CPUs.
    
    Fixes: 7a30871b6a27 ("rcu-tasks: Introduce ->percpu_enqueue_shift for dynamic queue selection")
    Reported-by: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Reported-by: Martin Lau <kafai@fb.com>
    Cc: Neeraj Upadhyay <neeraj.iitr10@gmail.com>
    Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

commit 4584a768f22b7669cdebabc911543621ac661341
Author: Jeff Layton <jlayton@kernel.org>
Date:   Wed Jan 26 12:36:49 2022 -0500

    ceph: set pool_ns in new inode layout for async creates
    
    Dan reported that he was unable to write to files that had been
    asynchronously created when the client's OSD caps are restricted to a
    particular namespace.
    
    The issue is that the layout for the new inode is only partially being
    filled. Ensure that we populate the pool_ns_data and pool_ns_len in the
    iinfo before calling ceph_fill_inode.
    
    Cc: stable@vger.kernel.org
    URL: https://tracker.ceph.com/issues/54013
    Fixes: 9a8d03ca2e2c ("ceph: attempt to do async create when possible")
    Reported-by: Dan van der Ster <dan@vanderster.com>
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Ilya Dryomov <idryomov@gmail.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 932a9b5870d38b87ba0a9923c804b1af7d3605b9
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Jan 25 15:39:16 2022 -0500

    ceph: properly put ceph_string reference after async create attempt
    
    The reference acquired by try_prep_async_create is currently leaked.
    Ensure we put it.
    
    Cc: stable@vger.kernel.org
    Fixes: 9a8d03ca2e2c ("ceph: attempt to do async create when possible")
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Ilya Dryomov <idryomov@gmail.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 89d43d0551a848e70e63d9ba11534aaeabc82443
Author: Xiubo Li <xiubli@redhat.com>
Date:   Wed Jan 12 12:29:04 2022 +0800

    ceph: put the requests/sessions when it fails to alloc memory
    
    When failing to allocate the sessions memory we should make sure
    the req1 and req2 and the sessions get put. And also in case the
    max_sessions decreased so when kreallocate the new memory some
    sessions maybe missed being put.
    
    And if the max_sessions is 0 krealloc will return ZERO_SIZE_PTR,
    which will lead to a distinct access fault.
    
    URL: https://tracker.ceph.com/issues/53819
    Fixes: e1a4541ec0b9 ("ceph: flush the mdlog before waiting on unsafe reqs")
    Signed-off-by: Xiubo Li <xiubli@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 3758a6c74e08bdc15ccccd6872a6ad37d165239a
Author: Evgenii Stepanov <eugenis@google.com>
Date:   Tue Jan 25 10:22:17 2022 -0800

    arm64: extable: fix load_unaligned_zeropad() reg indices
    
    In ex_handler_load_unaligned_zeropad() we erroneously extract the data and
    addr register indices from ex->type rather than ex->data. As ex->type will
    contain EX_TYPE_LOAD_UNALIGNED_ZEROPAD (i.e. 4):
     * We'll always treat X0 as the address register, since EX_DATA_REG_ADDR is
       extracted from bits [9:5]. Thus, we may attempt to dereference an
       arbitrary address as X0 may hold an arbitrary value.
     * We'll always treat X4 as the data register, since EX_DATA_REG_DATA is
       extracted from bits [4:0]. Thus we will corrupt X4 and cause arbitrary
       behaviour within load_unaligned_zeropad() and its caller.
    
    Fix this by extracting both values from ex->data as originally intended.
    
    On an MTE-enabled QEMU image we are hitting the following crash:
     Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
     Call trace:
      fixup_exception+0xc4/0x108
      __do_kernel_fault+0x3c/0x268
      do_tag_check_fault+0x3c/0x104
      do_mem_abort+0x44/0xf4
      el1_abort+0x40/0x64
      el1h_64_sync_handler+0x60/0xa0
      el1h_64_sync+0x7c/0x80
      link_path_walk+0x150/0x344
      path_openat+0xa0/0x7dc
      do_filp_open+0xb8/0x168
      do_sys_openat2+0x88/0x17c
      __arm64_sys_openat+0x74/0xa0
      invoke_syscall+0x48/0x148
      el0_svc_common+0xb8/0xf8
      do_el0_svc+0x28/0x88
      el0_svc+0x24/0x84
      el0t_64_sync_handler+0x88/0xec
      el0t_64_sync+0x1b4/0x1b8
     Code: f8695a69 71007d1f 540000e0 927df12a (f940014a)
    
    Fixes: 753b32368705 ("arm64: extable: add load_unaligned_zeropad() handler")
    Cc: <stable@vger.kernel.org> # 5.16.x
    Reviewed-by: Mark Rutland <mark.rutland@arm.com>
    Signed-off-by: Evgenii Stepanov <eugenis@google.com>
    Link: https://lore.kernel.org/r/20220125182217.2605202-1-eugenis@google.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit fc55e63e148f1db2180867da875460a00aac8bd1
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 11 20:32:43 2022 +0300

    counter: fix an IS_ERR() vs NULL bug
    
    There are 8 callers for devm_counter_alloc() and they all check for NULL
    instead of error pointers.  I think NULL is the better thing to return
    for allocation functions so update counter_alloc() and devm_counter_alloc()
    to return NULL instead of error pointers.
    
    Fixes: c18e2760308e ("counter: Provide alternative counter registration functions")
    Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com>
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220111173243.GA2192@kili
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit dd4516aee365fc9c944c9d6036b6b87363398680
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Jan 26 07:44:34 2022 -0500

    selftests: kvm: move vm_xsave_req_perm call to amx_test
    
    There is no need for tests other than amx_test to enable dynamic xsave
    states.  Remove the call to vm_xsave_req_perm from generic code,
    and move it inside the test.  While at it, allow customizing the bit
    that is requested, so that future tests can use it differently.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 05a9e065059e566f218f8778c4d17ee75db56c55
Author: Like Xu <likexu@tencent.com>
Date:   Wed Jan 26 17:22:26 2022 +0000

    KVM: x86: Sync the states size with the XCR0/IA32_XSS at, any time
    
    XCR0 is reset to 1 by RESET but not INIT and IA32_XSS is zeroed by
    both RESET and INIT. The kvm_set_msr_common()'s handling of MSR_IA32_XSS
    also needs to update kvm_update_cpuid_runtime(). In the above cases, the
    size in bytes of the XSAVE area containing all states enabled by XCR0 or
    (XCRO | IA32_XSS) needs to be updated.
    
    For simplicity and consistency, existing helpers are used to write values
    and call kvm_update_cpuid_runtime(), and it's not exactly a fast path.
    
    Fixes: a554d207dc46 ("KVM: X86: Processor States following Reset or INIT")
    Cc: stable@vger.kernel.org
    Signed-off-by: Like Xu <likexu@tencent.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220126172226.2298529-4-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4c282e51e4450b94680d6ca3b10f830483b1f243
Author: Like Xu <likexu@tencent.com>
Date:   Wed Jan 26 17:22:25 2022 +0000

    KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
    
    Do a runtime CPUID update for a vCPU if MSR_IA32_XSS is written, as the
    size in bytes of the XSAVE area is affected by the states enabled in XSS.
    
    Fixes: 203000993de5 ("kvm: vmx: add MSR logic for XSAVES")
    Cc: stable@vger.kernel.org
    Signed-off-by: Like Xu <likexu@tencent.com>
    [sean: split out as a separate patch, adjust Fixes tag]
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220126172226.2298529-3-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit be4f3b3f82271c3193ce200a996dc70682c8e622
Author: Xiaoyao Li <xiaoyao.li@intel.com>
Date:   Wed Jan 26 17:22:24 2022 +0000

    KVM: x86: Keep MSR_IA32_XSS unchanged for INIT
    
    It has been corrected from SDM version 075 that MSR_IA32_XSS is reset to
    zero on Power up and Reset but keeps unchanged on INIT.
    
    Fixes: a554d207dc46 ("KVM: X86: Processor States following Reset or INIT")
    Cc: stable@vger.kernel.org
    Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220126172226.2298529-2-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 663d34c8df98740f1e90241e78e456d00b3c6cad
Author: Vasily Gorbik <gor@linux.ibm.com>
Date:   Thu Jan 20 16:23:19 2022 +0100

    s390/hypfs: include z/VM guests with access control group set
    
    Currently if z/VM guest is allowed to retrieve hypervisor performance
    data globally for all guests (privilege class B) the query is formed in a
    way to include all guests but the group name is left empty. This leads to
    that z/VM guests which have access control group set not being included
    in the results (even local vm).
    
    Change the query group identifier from empty to "any" to retrieve
    information about all guests from any groups (or without a group set).
    
    Cc: stable@vger.kernel.org
    Fixes: 31cb4bd31a48 ("[S390] Hypervisor filesystem (s390_hypfs) for z/VM")
    Reviewed-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
    Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>

commit 811f95ff95270e6048197821434d9301e3d7f07c
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Jan 25 21:04:45 2022 +0000

    KVM: x86: Free kvm_cpuid_entry2 array on post-KVM_RUN KVM_SET_CPUID{,2}
    
    Free the "struct kvm_cpuid_entry2" array on successful post-KVM_RUN
    KVM_SET_CPUID{,2} to fix a memory leak, the callers of kvm_set_cpuid()
    free the array only on failure.
    
     BUG: memory leak
     unreferenced object 0xffff88810963a800 (size 2048):
      comm "syz-executor025", pid 3610, jiffies 4294944928 (age 8.080s)
      hex dump (first 32 bytes):
        00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00  ................
        47 65 6e 75 6e 74 65 6c 69 6e 65 49 00 00 00 00  GenuntelineI....
      backtrace:
        [<ffffffff814948ee>] kmalloc_node include/linux/slab.h:604 [inline]
        [<ffffffff814948ee>] kvmalloc_node+0x3e/0x100 mm/util.c:580
        [<ffffffff814950f2>] kvmalloc include/linux/slab.h:732 [inline]
        [<ffffffff814950f2>] vmemdup_user+0x22/0x100 mm/util.c:199
        [<ffffffff8109f5ff>] kvm_vcpu_ioctl_set_cpuid2+0x8f/0xf0 arch/x86/kvm/cpuid.c:423
        [<ffffffff810711b9>] kvm_arch_vcpu_ioctl+0xb99/0x1e60 arch/x86/kvm/x86.c:5251
        [<ffffffff8103e92d>] kvm_vcpu_ioctl+0x4ad/0x950 arch/x86/kvm/../../../virt/kvm/kvm_main.c:4066
        [<ffffffff815afacc>] vfs_ioctl fs/ioctl.c:51 [inline]
        [<ffffffff815afacc>] __do_sys_ioctl fs/ioctl.c:874 [inline]
        [<ffffffff815afacc>] __se_sys_ioctl fs/ioctl.c:860 [inline]
        [<ffffffff815afacc>] __x64_sys_ioctl+0xfc/0x140 fs/ioctl.c:860
        [<ffffffff844a3335>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
        [<ffffffff844a3335>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
        [<ffffffff84600068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Fixes: c6617c61e8fe ("KVM: x86: Partially allow KVM_SET_CPUID{,2} after KVM_RUN")
    Cc: stable@vger.kernel.org
    Reported-by: syzbot+be576ad7655690586eec@syzkaller.appspotmail.com
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220125210445.2053429-1-seanjc@google.com>
    Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ebb7fb1557b1d03b906b668aa2164b51e6b7d19a
Author: Dave Chinner <dchinner@redhat.com>
Date:   Wed Jan 26 09:19:20 2022 -0800

    xfs, iomap: limit individual ioend chain lengths in writeback
    
    Trond Myklebust reported soft lockups in XFS IO completion such as
    this:
    
     watchdog: BUG: soft lockup - CPU#12 stuck for 23s! [kworker/12:1:3106]
     CPU: 12 PID: 3106 Comm: kworker/12:1 Not tainted 4.18.0-305.10.2.el8_4.x86_64 #1
     Workqueue: xfs-conv/md127 xfs_end_io [xfs]
     RIP: 0010:_raw_spin_unlock_irqrestore+0x11/0x20
     Call Trace:
      wake_up_page_bit+0x8a/0x110
      iomap_finish_ioend+0xd7/0x1c0
      iomap_finish_ioends+0x7f/0xb0
      xfs_end_ioend+0x6b/0x100 [xfs]
      xfs_end_io+0xb9/0xe0 [xfs]
      process_one_work+0x1a7/0x360
      worker_thread+0x1fa/0x390
      kthread+0x116/0x130
      ret_from_fork+0x35/0x40
    
    Ioends are processed as an atomic completion unit when all the
    chained bios in the ioend have completed their IO. Logically
    contiguous ioends can also be merged and completed as a single,
    larger unit.  Both of these things can be problematic as both the
    bio chains per ioend and the size of the merged ioends processed as
    a single completion are both unbound.
    
    If we have a large sequential dirty region in the page cache,
    write_cache_pages() will keep feeding us sequential pages and we
    will keep mapping them into ioends and bios until we get a dirty
    page at a non-sequential file offset. These large sequential runs
    can will result in bio and ioend chaining to optimise the io
    patterns. The pages iunder writeback are pinned within these chains
    until the submission chaining is broken, allowing the entire chain
    to be completed. This can result in huge chains being processed
    in IO completion context.
    
    We get deep bio chaining if we have large contiguous physical
    extents. We will keep adding pages to the current bio until it is
    full, then we'll chain a new bio to keep adding pages for writeback.
    Hence we can build bio chains that map millions of pages and tens of
    gigabytes of RAM if the page cache contains big enough contiguous
    dirty file regions. This long bio chain pins those pages until the
    final bio in the chain completes and the ioend can iterate all the
    chained bios and complete them.
    
    OTOH, if we have a physically fragmented file, we end up submitting
    one ioend per physical fragment that each have a small bio or bio
    chain attached to them. We do not chain these at IO submission time,
    but instead we chain them at completion time based on file
    offset via iomap_ioend_try_merge(). Hence we can end up with unbound
    ioend chains being built via completion merging.
    
    XFS can then do COW remapping or unwritten extent conversion on that
    merged chain, which involves walking an extent fragment at a time
    and running a transaction to modify the physical extent information.
    IOWs, we merge all the discontiguous ioends together into a
    contiguous file range, only to then process them individually as
    discontiguous extents.
    
    This extent manipulation is computationally expensive and can run in
    a tight loop, so merging logically contiguous but physically
    discontigous ioends gains us nothing except for hiding the fact the
    fact we broke the ioends up into individual physical extents at
    submission and then need to loop over those individual physical
    extents at completion.
    
    Hence we need to have mechanisms to limit ioend sizes and
    to break up completion processing of large merged ioend chains:
    
    1. bio chains per ioend need to be bound in length. Pure overwrites
    go straight to iomap_finish_ioend() in softirq context with the
    exact bio chain attached to the ioend by submission. Hence the only
    way to prevent long holdoffs here is to bound ioend submission
    sizes because we can't reschedule in softirq context.
    
    2. iomap_finish_ioends() has to handle unbound merged ioend chains
    correctly. This relies on any one call to iomap_finish_ioend() being
    bound in runtime so that cond_resched() can be issued regularly as
    the long ioend chain is processed. i.e. this relies on mechanism #1
    to limit individual ioend sizes to work correctly.
    
    3. filesystems have to loop over the merged ioends to process
    physical extent manipulations. This means they can loop internally,
    and so we break merging at physical extent boundaries so the
    filesystem can easily insert reschedule points between individual
    extent manipulations.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reported-and-tested-by: Trond Myklebust <trondmy@hammerspace.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit d6e656cd266cdcc95abd372c7faef05bee271d1a
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Jan 25 22:05:27 2022 +0000

    KVM: nVMX: WARN on any attempt to allocate shadow VMCS for vmcs02
    
    WARN if KVM attempts to allocate a shadow VMCS for vmcs02.  KVM emulates
    VMCS shadowing but doesn't virtualize it, i.e. KVM should never allocate
    a "real" shadow VMCS for L2.
    
    The previous code WARNed but continued anyway with the allocation,
    presumably in an attempt to avoid NULL pointer dereference.
    However, alloc_vmcs (and hence alloc_shadow_vmcs) can fail, and
    indeed the sole caller does:
    
            if (enable_shadow_vmcs && !alloc_shadow_vmcs(vcpu))
                    goto out_shadow_vmcs;
    
    which makes it not a useful attempt.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220125220527.2093146-1-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4cf3d3ebe8794c449af3e0e8c1d790c97e461d20
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Jan 25 22:17:25 2022 +0000

    KVM: selftests: Don't skip L2's VMCALL in SMM test for SVM guest
    
    Don't skip the vmcall() in l2_guest_code() prior to re-entering L2, doing
    so will result in L2 running to completion, popping '0' off the stack for
    RET, jumping to address '0', and ultimately dying with a triple fault
    shutdown.
    
    It's not at all obvious why the test re-enters L2 and re-executes VMCALL,
    but presumably it serves a purpose.  The VMX path doesn't skip vmcall(),
    and the test can't possibly have passed on SVM, so just do what VMX does.
    
    Fixes: d951b2210c1a ("KVM: selftests: smm_test: Test SMM enter from L2")
    Cc: Maxim Levitsky <mlevitsk@redhat.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220125221725.2101126-1-seanjc@google.com>
    Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Tested-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 033a3ea59a19df63edb4db6bfdbb357cd028258a
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Wed Jan 26 14:18:04 2022 +0100

    KVM: x86: Check .flags in kvm_cpuid_check_equal() too
    
    kvm_cpuid_check_equal() checks for the (full) equality of the supplied
    CPUID data so .flags need to be checked too.
    
    Reported-by: Sean Christopherson <seanjc@google.com>
    Fixes: c6617c61e8fe ("KVM: x86: Partially allow KVM_SET_CPUID{,2} after KVM_RUN")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220126131804.2839410-1-vkuznets@redhat.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit f7e570780efc5cec9b2ed1e0472a7da14e864fdb
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Jan 25 22:03:58 2022 +0000

    KVM: x86: Forcibly leave nested virt when SMM state is toggled
    
    Forcibly leave nested virtualization operation if userspace toggles SMM
    state via KVM_SET_VCPU_EVENTS or KVM_SYNC_X86_EVENTS.  If userspace
    forces the vCPU out of SMM while it's post-VMXON and then injects an SMI,
    vmx_enter_smm() will overwrite vmx->nested.smm.vmxon and end up with both
    vmxon=false and smm.vmxon=false, but all other nVMX state allocated.
    
    Don't attempt to gracefully handle the transition as (a) most transitions
    are nonsencial, e.g. forcing SMM while L2 is running, (b) there isn't
    sufficient information to handle all transitions, e.g. SVM wants access
    to the SMRAM save state, and (c) KVM_SET_VCPU_EVENTS must precede
    KVM_SET_NESTED_STATE during state restore as the latter disallows putting
    the vCPU into L2 if SMM is active, and disallows tagging the vCPU as
    being post-VMXON in SMM if SMM is not active.
    
    Abuse of KVM_SET_VCPU_EVENTS manifests as a WARN and memory leak in nVMX
    due to failure to free vmcs01's shadow VMCS, but the bug goes far beyond
    just a memory leak, e.g. toggling SMM on while L2 is active puts the vCPU
    in an architecturally impossible state.
    
      WARNING: CPU: 0 PID: 3606 at free_loaded_vmcs arch/x86/kvm/vmx/vmx.c:2665 [inline]
      WARNING: CPU: 0 PID: 3606 at free_loaded_vmcs+0x158/0x1a0 arch/x86/kvm/vmx/vmx.c:2656
      Modules linked in:
      CPU: 1 PID: 3606 Comm: syz-executor725 Not tainted 5.17.0-rc1-syzkaller #0
      Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
      RIP: 0010:free_loaded_vmcs arch/x86/kvm/vmx/vmx.c:2665 [inline]
      RIP: 0010:free_loaded_vmcs+0x158/0x1a0 arch/x86/kvm/vmx/vmx.c:2656
      Code: <0f> 0b eb b3 e8 8f 4d 9f 00 e9 f7 fe ff ff 48 89 df e8 92 4d 9f 00
      Call Trace:
       <TASK>
       kvm_arch_vcpu_destroy+0x72/0x2f0 arch/x86/kvm/x86.c:11123
       kvm_vcpu_destroy arch/x86/kvm/../../../virt/kvm/kvm_main.c:441 [inline]
       kvm_destroy_vcpus+0x11f/0x290 arch/x86/kvm/../../../virt/kvm/kvm_main.c:460
       kvm_free_vcpus arch/x86/kvm/x86.c:11564 [inline]
       kvm_arch_destroy_vm+0x2e8/0x470 arch/x86/kvm/x86.c:11676
       kvm_destroy_vm arch/x86/kvm/../../../virt/kvm/kvm_main.c:1217 [inline]
       kvm_put_kvm+0x4fa/0xb00 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1250
       kvm_vm_release+0x3f/0x50 arch/x86/kvm/../../../virt/kvm/kvm_main.c:1273
       __fput+0x286/0x9f0 fs/file_table.c:311
       task_work_run+0xdd/0x1a0 kernel/task_work.c:164
       exit_task_work include/linux/task_work.h:32 [inline]
       do_exit+0xb29/0x2a30 kernel/exit.c:806
       do_group_exit+0xd2/0x2f0 kernel/exit.c:935
       get_signal+0x4b0/0x28c0 kernel/signal.c:2862
       arch_do_signal_or_restart+0x2a9/0x1c40 arch/x86/kernel/signal.c:868
       handle_signal_work kernel/entry/common.c:148 [inline]
       exit_to_user_mode_loop kernel/entry/common.c:172 [inline]
       exit_to_user_mode_prepare+0x17d/0x290 kernel/entry/common.c:207
       __syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
       syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:300
       do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x44/0xae
       </TASK>
    
    Cc: stable@vger.kernel.org
    Reported-by: syzbot+8112db3ab20e70d50c31@syzkaller.appspotmail.com
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220125220358.2091737-1-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit aa3b39f38c7a5dfdd10b3f61a0d055b85aa85451
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Dec 20 16:21:35 2021 +0100

    KVM: SVM: drop unnecessary code in svm_hv_vmcb_dirty_nested_enlightenments()
    
    Commit 3fa5e8fd0a0e4 ("KVM: SVM: delay svm_vcpu_init_msrpm after
    svm->vmcb is initialized") re-arranged svm_vcpu_init_msrpm() call in
    svm_create_vcpu(), thus making the comment about vmcb being NULL
    obsolete. Drop it.
    
    While on it, drop superfluous vmcb_is_clean() check: vmcb_mark_dirty()
    is a bit flip, an extra check is unlikely to bring any performance gain.
    Drop now-unneeded vmcb_is_clean() helper as well.
    
    Fixes: 3fa5e8fd0a0e4 ("KVM: SVM: delay svm_vcpu_init_msrpm after svm->vmcb is initialized")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20211220152139.418372-2-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 38dfa8308cfc43f671a74c753302fec26808edc0
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Dec 20 16:21:36 2021 +0100

    KVM: SVM: hyper-v: Enable Enlightened MSR-Bitmap support for real
    
    Commit c4327f15dfc7 ("KVM: SVM: hyper-v: Enlightened MSR-Bitmap support")
    introduced enlightened MSR-Bitmap support for KVM-on-Hyper-V but it didn't
    actually enable the support. Similar to enlightened NPT TLB flush and
    direct TLB flush features, the guest (KVM) has to tell L0 (Hyper-V) that
    it's using the feature by setting the appropriate feature fit in VMCB
    control area (sw reserved fields).
    
    Fixes: c4327f15dfc7 ("KVM: SVM: hyper-v: Enlightened MSR-Bitmap support")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20211220152139.418372-3-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit cdf85e0c5dc766fc7fc779466280e454a6d04f87
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:19 2022 +0000

    KVM: SVM: Don't kill SEV guest if SMAP erratum triggers in usermode
    
    Inject a #GP instead of synthesizing triple fault to try to avoid killing
    the guest if emulation of an SEV guest fails due to encountering the SMAP
    erratum.  The injected #GP may still be fatal to the guest, e.g. if the
    userspace process is providing critical functionality, but KVM should
    make every attempt to keep the guest alive.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-10-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 3280cc22aea74d78ebbea277ff8bc8d593582de3
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:18 2022 +0000

    KVM: SVM: Don't apply SEV+SMAP workaround on code fetch or PT access
    
    Resume the guest instead of synthesizing a triple fault shutdown if the
    instruction bytes buffer is empty due to the #NPF being on the code fetch
    itself or on a page table access.  The SMAP errata applies if and only if
    the code fetch was successful and ucode's subsequent data read from the
    code page encountered a SMAP violation.  In practice, the guest is likely
    hosed either way, but crashing the guest on a code fetch to emulated MMIO
    is technically wrong according to the behavior described in the APM.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-9-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 04c40f344defdbd842d8a64fcfb47ef74b39ef4e
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:17 2022 +0000

    KVM: SVM: Inject #UD on attempted emulation for SEV guest w/o insn buffer
    
    Inject #UD if KVM attempts emulation for an SEV guests without an insn
    buffer and instruction decoding is required.  The previous behavior of
    allowing emulation if there is no insn buffer is undesirable as doing so
    means KVM is reading guest private memory and thus decoding cyphertext,
    i.e. is emulating garbage.  The check was previously necessary as the
    emulation type was not provided, i.e. SVM needed to allow emulation to
    handle completion of emulation after exiting to userspace to handle I/O.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-8-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 132627c64d94b1561ba5a444824e46c9f84c3d5b
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:16 2022 +0000

    KVM: SVM: WARN if KVM attempts emulation on #UD or #GP for SEV guests
    
    WARN if KVM attempts to emulate in response to #UD or #GP for SEV guests,
    i.e. if KVM intercepts #UD or #GP, as emulation on any fault except #NPF
    is impossible since KVM cannot read guest private memory to get the code
    stream, and the CPU's DecodeAssists feature only provides the instruction
    bytes on #NPF.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-7-seanjc@google.com>
    [Warn on EMULTYPE_TRAP_UD_FORCED according to Liam Merwick's review. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4d31d9eff244e2631f028d658979ccbbdbcb423b
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:15 2022 +0000

    KVM: x86: Pass emulation type to can_emulate_instruction()
    
    Pass the emulation type to kvm_x86_ops.can_emulate_insutrction() so that
    a future commit can harden KVM's SEV support to WARN on emulation
    scenarios that should never happen.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-6-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c532f2903b69b775d27016511fbe29a14a098f95
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:14 2022 +0000

    KVM: SVM: Explicitly require DECODEASSISTS to enable SEV support
    
    Add a sanity check on DECODEASSIST being support if SEV is supported, as
    KVM cannot read guest private memory and thus relies on the CPU to
    provide the instruction byte stream on #NPF for emulation.  The intent of
    the check is to document the dependency, it should never fail in practice
    as producing hardware that supports SEV but not DECODEASSISTS would be
    non-sensical.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-5-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 0b0be065b7563ac708aaa9f69dd4941c80b3446d
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:13 2022 +0000

    KVM: SVM: Don't intercept #GP for SEV guests
    
    Never intercept #GP for SEV guests as reading SEV guest private memory
    will return cyphertext, i.e. emulating on #GP can't work as intended.
    
    Cc: stable@vger.kernel.org
    Cc: Tom Lendacky <thomas.lendacky@amd.com>
    Cc: Brijesh Singh <brijesh.singh@amd.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-4-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 31c25585695abdf03d6160aa6d829e855b256329
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:12 2022 +0000

    Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
    
    Revert a completely broken check on an "invalid" RIP in SVM's workaround
    for the DecodeAssists SMAP errata.  kvm_vcpu_gfn_to_memslot() obviously
    expects a gfn, i.e. operates in the guest physical address space, whereas
    RIP is a virtual (not even linear) address.  The "fix" worked for the
    problematic KVM selftest because the test identity mapped RIP.
    
    Fully revert the hack instead of trying to translate RIP to a GPA, as the
    non-SEV case is now handled earlier, and KVM cannot access guest page
    tables to translate RIP.
    
    This reverts commit e72436bc3a5206f95bb384e741154166ddb3202e.
    
    Fixes: e72436bc3a52 ("KVM: SVM: avoid infinite loop on NPF from bad address")
    Reported-by: Liam Merwick <liam.merwick@oracle.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-3-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 55467fcd55b89c622e62b4afe60ac0eb2fae91f2
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 01:07:11 2022 +0000

    KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests
    
    Always signal that emulation is possible for !SEV guests regardless of
    whether or not the CPU provided a valid instruction byte stream.  KVM can
    read all guest state (memory and registers) for !SEV guests, i.e. can
    fetch the code stream from memory even if the CPU failed to do so because
    of the SMAP errata.
    
    Fixes: 05d5a4863525 ("KVM: SVM: Workaround errata#1096 (insn_len maybe zero on SMAP violation)")
    Cc: stable@vger.kernel.org
    Cc: Tom Lendacky <thomas.lendacky@amd.com>
    Cc: Brijesh Singh <brijesh.singh@amd.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
    Message-Id: <20220120010719.711476-2-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 47c28d436f409f5b009dc82bd82d4971088aa391
Author: Denis Valeev <lemniscattaden@gmail.com>
Date:   Sat Jan 22 23:13:57 2022 +0300

    KVM: x86: nSVM: skip eax alignment check for non-SVM instructions
    
    The bug occurs on #GP triggered by VMware backdoor when eax value is
    unaligned. eax alignment check should not be applied to non-SVM
    instructions because it leads to incorrect omission of the instructions
    emulation.
    Apply the alignment check only to SVM instructions to fix.
    
    Fixes: d1cba6c92237 ("KVM: x86: nSVM: test eax for 4K alignment for GP errata workaround")
    Signed-off-by: Denis Valeev <lemniscattaden@gmail.com>
    Message-Id: <Yexlhaoe1Fscm59u@q>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 1ffce0924a8c86cf0590c039cd5f5c9375d32e9b
Author: Like Xu <likexu@tencent.com>
Date:   Tue Jan 25 19:52:23 2022 +0800

    KVM: x86/cpuid: Exclude unpermitted xfeatures sizes at KVM_GET_SUPPORTED_CPUID
    
    With the help of xstate_get_guest_group_perm(), KVM can exclude unpermitted
    xfeatures in cpuid.0xd.0.eax, in which case the corresponding xfeatures
    sizes should also be matched to the permitted xfeatures.
    
    To fix this inconsistency, the permitted_xcr0 and permitted_xss are defined
    consistently, which implies 'supported' plus certain permissions for this
    task, and it also fixes cpuid.0xd.1.ebx and later leaf-by-leaf queries.
    
    Fixes: 445ecdf79be0 ("kvm: x86: Exclude unpermitted xfeatures at KVM_GET_SUPPORTED_CPUID")
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20220125115223.33707-1-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 35fe7cfbab2e81f1afb23fc4212210b1de6d9633
Author: Wanpeng Li <wanpengli@tencent.com>
Date:   Tue Jan 25 01:17:00 2022 -0800

    KVM: LAPIC: Also cancel preemption timer during SET_LAPIC
    
    The below warning is splatting during guest reboot.
    
      ------------[ cut here ]------------
      WARNING: CPU: 0 PID: 1931 at arch/x86/kvm/x86.c:10322 kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]
      CPU: 0 PID: 1931 Comm: qemu-system-x86 Tainted: G          I       5.17.0-rc1+ #5
      RIP: 0010:kvm_arch_vcpu_ioctl_run+0x874/0x880 [kvm]
      Call Trace:
       <TASK>
       kvm_vcpu_ioctl+0x279/0x710 [kvm]
       __x64_sys_ioctl+0x83/0xb0
       do_syscall_64+0x3b/0xc0
       entry_SYSCALL_64_after_hwframe+0x44/0xae
      RIP: 0033:0x7fd39797350b
    
    This can be triggered by not exposing tsc-deadline mode and doing a reboot in
    the guest. The lapic_shutdown() function which is called in sys_reboot path
    will not disarm the flying timer, it just masks LVTT. lapic_shutdown() clears
    APIC state w/ LVT_MASKED and timer-mode bit is 0, this can trigger timer-mode
    switch between tsc-deadline and oneshot/periodic, which can result in preemption
    timer be cancelled in apic_update_lvtt(). However, We can't depend on this when
    not exposing tsc-deadline mode and oneshot/periodic modes emulated by preemption
    timer. Qemu will synchronise states around reset, let's cancel preemption timer
    under KVM_SET_LAPIC.
    
    Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
    Message-Id: <1643102220-35667-1-git-send-email-wanpengli@tencent.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 519669cc58368385db93fd1560c09bf3334a6ecc
Author: Jim Mattson <jmattson@google.com>
Date:   Mon Jan 24 16:43:59 2022 -0800

    KVM: VMX: Remove vmcs_config.order
    
    The maximum size of a VMCS (or VMXON region) is 4096. By definition,
    these are order 0 allocations.
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Message-Id: <20220125004359.147600-1-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c80d401c52a2d1baf2a5afeb06f0ffe678e56d23
Author: Tianchen Ding <dtcccc@linux.alibaba.com>
Date:   Tue Jan 18 18:05:18 2022 +0800

    cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
    
    subparts_cpus should be limited as a subset of cpus_allowed, but it is
    updated wrongly by using cpumask_andnot(). Use cpumask_and() instead to
    fix it.
    
    Fixes: ee8dde0cd2ce ("cpuset: Add new v2 cpuset.sched.partition flag")
    Signed-off-by: Tianchen Ding <dtcccc@linux.alibaba.com>
    Reviewed-by: Waiman Long <longman@redhat.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 66d28b21fe6b3da8d1e9f0a7ba38bc61b6c547e1
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Wed Jan 26 09:40:01 2022 -0600

    PCI/sysfs: Find shadow ROM before static attribute initialization
    
    Ville reported that the sysfs "rom" file for VGA devices disappeared after
    527139d738d7 ("PCI/sysfs: Convert "rom" to static attribute").
    
    Prior to 527139d738d7, FINAL fixups, including pci_fixup_video() where we
    find shadow ROMs, were run before pci_create_sysfs_dev_files() created the
    sysfs "rom" file.
    
    After 527139d738d7, "rom" is a static attribute and is created before FINAL
    fixups are run, so we didn't create "rom" files for shadow ROMs:
    
      acpi_pci_root_add
        ...
          pci_scan_single_device
            pci_device_add
              pci_fixup_video                    # <-- new HEADER fixup
              device_add
                ...
                  if (grp->is_visible())
                    pci_dev_rom_attr_is_visible  # after 527139d738d7
        pci_bus_add_devices
          pci_bus_add_device
            pci_fixup_device(pci_fixup_final)
              pci_fixup_video                    # <-- previous FINAL fixup
            pci_create_sysfs_dev_files
              if (pci_resource_len(pdev, PCI_ROM_RESOURCE))
                sysfs_create_bin_file("rom")     # before 527139d738d7
    
    Change pci_fixup_video() to be a HEADER fixup so it runs before sysfs
    static attributes are initialized.
    
    Rename the Loongson pci_fixup_radeon() to pci_fixup_video() and make its
    dmesg logging identical to the others since it is doing the same job.
    
    Link: https://lore.kernel.org/r/YbxqIyrkv3GhZVxx@intel.com
    Fixes: 527139d738d7 ("PCI/sysfs: Convert "rom" to static attribute")
    Link: https://lore.kernel.org/r/20220126154001.16895-1-helgaas@kernel.org
    Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Cc: stable@vger.kernel.org                      # v5.13+
    Cc: Huacai Chen <chenhuacai@kernel.org>
    Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Krzysztof Wilczyński <kw@linux.com>

commit 37c2c83ca4f1ef4b6908181ac98e18360af89b42
Author: Xin Xiong <xiongx18@fudan.edu.cn>
Date:   Tue Jan 25 18:12:15 2022 +0800

    spi: uniphier: fix reference count leak in uniphier_spi_probe()
    
    The issue happens in several error paths in uniphier_spi_probe().
    When either dma_get_slave_caps() or devm_spi_register_master() returns
    an error code, the function forgets to decrease the refcount of both
    `dma_rx` and `dma_tx` objects, which may lead to refcount leaks.
    
    Fix it by decrementing the reference count of specific objects in
    those error paths.
    
    Signed-off-by: Xin Xiong <xiongx18@fudan.edu.cn>
    Signed-off-by: Xiyu Yang <xiyuyang19@fudan.edu.cn>
    Signed-off-by: Xin Tan <tanxin.ctf@gmail.com>
    Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
    Fixes: 28d1dddc59f6 ("spi: uniphier: Add DMA transfer mode support")
    Link: https://lore.kernel.org/r/20220125101214.35677-1-xiongx18@fudan.edu.cn
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 2f6513284347432d137ce54e30baae2aa5d5f55c
Merge: 8199d0c6ad95a 77bdaf39f3c8a
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Jan 26 15:45:49 2022 +0000

    Merge branch 'lan966x-fixes'
    
    Horatiu Vultur says:
    
    ====================
    net: lan966x: Fixes for sleep in atomic context
    
    This patch series contains 2 fixes for lan966x that is sleeping in atomic
    context. The first patch fixes the injection of the frames while the second
    one fixes the updating of the MAC table.
    
    v1->v2:
     - correct the fix tag in the second patch, it was using the wrong sha.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 77bdaf39f3c8a10892bace06ed60bd063b731529
Author: Horatiu Vultur <horatiu.vultur@microchip.com>
Date:   Tue Jan 25 12:48:16 2022 +0100

    net: lan966x: Fix sleep in atomic context when updating MAC table
    
    The function lan966x_mac_wait_for_completion is used to poll the status
    of the MAC table using the function readx_poll_timeout. The problem with
    this function is that is called also from atomic context. Therefore
    update the function to use readx_poll_timeout_atomic.
    
    Fixes: e18aba8941b40b ("net: lan966x: add mactable support")
    Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b6ab149654ef1fada0b37b379c04c475c2fdc675
Author: Horatiu Vultur <horatiu.vultur@microchip.com>
Date:   Tue Jan 25 12:48:15 2022 +0100

    net: lan966x: Fix sleep in atomic context when injecting frames
    
    On lan966x, when injecting a frame it was polling the register
    QS_INJ_STATUS to see if it can continue with the injection of the frame.
    The problem was that it was using readx_poll_timeout which could sleep
    in atomic context.
    This patch fixes this issue by using readx_poll_timeout_atomic.
    
    Fixes: d28d6d2e37d10d ("net: lan966x: add port module support")
    Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8199d0c6ad95ae0d6ef84c28ab296ee4de46ed76
Merge: 429c3be8a5e26 8eb86fc2f4905
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Jan 26 15:40:02 2022 +0000

    Merge branch 'dev_addr-const-fixes'
    
    Jakub Kicinski says:
    
    ====================
    ethernet: fix some esoteric drivers after netdev->dev_addr constification
    
    Looking at recent fixes for drivers which don't get included with
    allmodconfig builds I thought it's worth grepping for more instances of:
    
      dev->dev_addr\[.*\] =
    
    This set contains the fixes.
    
    v2: add last 3 patches which fix drivers for the RiscPC ARM platform.
    Thanks to Arnd Bergmann for explaining how to build test that.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8eb86fc2f4905899a4684c1e03555e42556f4d53
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:38:01 2022 -0800

    ethernet: seeq/ether3: don't write directly to netdev->dev_addr
    
    netdev->dev_addr is const now.
    
    Compile tested rpc_defconfig w/ GCC 8.5.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5518c5246ba600f52c108474ecea615ef8ff9e25
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:38:00 2022 -0800

    ethernet: 8390/etherh: don't write directly to netdev->dev_addr
    
    netdev->dev_addr is const now.
    
    Compile tested rpc_defconfig w/ GCC 8.5.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 98ef22bbae788e05109aba16b77deb9f37bfb285
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:37:59 2022 -0800

    ethernet: i825xx: don't write directly to netdev->dev_addr
    
    netdev->dev_addr is const now.
    
    Compile tested rpc_defconfig w/ GCC 8.5.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 7f6ec2b2f01b45b39cd2ffcd49fdb30d0b6c626d
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:37:58 2022 -0800

    ethernet: broadcom/sb1250-mac: don't write directly to netdev->dev_addr
    
    netdev->dev_addr is const now.
    
    Compile tested bigsur_defconfig and sb1250_swarm_defconfig.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 14ba66a60fbfbe69bb7faf6b45e9803c2efd7a23
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:37:57 2022 -0800

    ethernet: tundra: don't write directly to netdev->dev_addr
    
    netdev->dev_addr is const now.
    
    Maintain the questionable offsetting in ndo_set_mac_address.
    
    Compile tested holly_defconfig and mpc7448_hpc2_defconfig.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 007c95120d1b054fb637dff24636a307a4889016
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 25 16:37:56 2022 -0800

    ethernet: 3com/typhoon: don't write directly to netdev->dev_addr
    
    This driver casts off the const and writes directly to netdev->dev_addr.
    This will result in a MAC address tree corruption and a warning.
    
    Compile tested ppc6xx_defconfig.
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 549f8ffc7b2f7561bea7f90930b6c5104318e87b
Author: Takashi Iwai <tiwai@suse.de>
Date:   Wed Jan 26 15:50:11 2022 +0100

    ALSA: hda: Fix UAF of leds class devs at unbinding
    
    The LED class devices that are created by HD-audio codec drivers are
    registered via devm_led_classdev_register() and associated with the
    HD-audio codec device.  Unfortunately, it turned out that the devres
    release doesn't work for this case; namely, since the codec resource
    release happens before the devm call chain, it triggers a NULL
    dereference or a UAF for a stale set_brightness_delay callback.
    
    For fixing the bug, this patch changes the LED class device register
    and unregister in a manual manner without devres, keeping the
    instances in hda_gen_spec.
    
    Reported-by: Alexander Sergeyev <sergeev917@gmail.com>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220111195229.a77wrpjclqwrx4bx@localhost.localdomain
    Link: https://lore.kernel.org/r/20220126145011.16728-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 7fde14d705985dd933a3d916d39daa72b1668098
Author: Tong Zhang <ztong0001@gmail.com>
Date:   Sun Jan 23 01:10:04 2022 -0800

    drm/privacy-screen: honor acpi=off in detect_thinkpad_privacy_screen
    
    when acpi=off is provided in bootarg, kernel crash with
    
    [    1.252739] BUG: kernel NULL pointer dereference, address: 0000000000000018
    [    1.258308] Call Trace:
    [    1.258490]  ? acpi_walk_namespace+0x147/0x147
    [    1.258770]  acpi_get_devices+0xe4/0x137
    [    1.258921]  ? drm_core_init+0xc0/0xc0 [drm]
    [    1.259108]  detect_thinkpad_privacy_screen+0x5e/0xa8 [drm]
    [    1.259337]  drm_privacy_screen_lookup_init+0xe/0xe85 [drm]
    
    The reason is that acpi_walk_namespace expects acpi related stuff
    initialized but in fact it wouldn't when acpi is set to off. In this case
    we should honor acpi=off in detect_thinkpad_privacy_screen().
    
    Signed-off-by: Tong Zhang <ztong0001@gmail.com>
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220123091004.763775-1-ztong0001@gmail.com

commit c5de60cd622a2607c043ba65e25a6e9998a369f9
Author: Namhyung Kim <namhyung@kernel.org>
Date:   Mon Jan 24 11:58:08 2022 -0800

    perf/core: Fix cgroup event list management
    
    The active cgroup events are managed in the per-cpu cgrp_cpuctx_list.
    This list is only accessed from current cpu and not protected by any
    locks.  But from the commit ef54c1a476ae ("perf: Rework
    perf_event_exit_event()"), it's possible to access (actually modify)
    the list from another cpu.
    
    In the perf_remove_from_context(), it can remove an event from the
    context without an IPI when the context is not active.  This is not
    safe with cgroup events which can have some active events in the
    context even if ctx->is_active is 0 at the moment.  The target cpu
    might be in the middle of list iteration at the same time.
    
    If the event is enabled when it's about to be closed, it might call
    perf_cgroup_event_disable() and list_del() with the cgrp_cpuctx_list
    on a different cpu.
    
    This resulted in a crash due to an invalid list pointer access during
    the cgroup list traversal on the cpu which the event belongs to.
    
    Let's fallback to IPI to access the cgrp_cpuctx_list from that cpu.
    Similarly, perf_install_in_context() should use IPI for the cgroup
    events too.
    
    Fixes: ef54c1a476ae ("perf: Rework perf_event_exit_event()")
    Signed-off-by: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/20220124195808.2252071-1-namhyung@kernel.org

commit 961c39121759ad09a89598ec4ccdd34ae0468a19
Author: James Clark <james.clark@arm.com>
Date:   Mon Dec 6 11:38:40 2021 +0000

    perf: Always wake the parent event
    
    When using per-process mode and event inheritance is set to true,
    forked processes will create a new perf events via inherit_event() ->
    perf_event_alloc(). But these events will not have ring buffers
    assigned to them. Any call to wakeup will be dropped if it's called on
    an event with no ring buffer assigned because that's the object that
    holds the wakeup list.
    
    If the child event is disabled due to a call to
    perf_aux_output_begin() or perf_aux_output_end(), the wakeup is
    dropped leaving userspace hanging forever on the poll.
    
    Normally the event is explicitly re-enabled by userspace after it
    wakes up to read the aux data, but in this case it does not get woken
    up so the event remains disabled.
    
    This can be reproduced when using Arm SPE and 'stress' which forks once
    before running the workload. By looking at the list of aux buffers read,
    it's apparent that they stop after the fork:
    
      perf record -e arm_spe// -vvv -- stress -c 1
    
    With this patch applied they continue to be printed. This behaviour
    doesn't happen when using systemwide or per-cpu mode.
    
    Reported-by: Ruben Ayrapetyan <Ruben.Ayrapetyan@arm.com>
    Signed-off-by: James Clark <james.clark@arm.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/20211206113840.130802-2-james.clark@arm.com

commit 2dd8a74fddd21b95dcc60a2d3c9eaec993419d69
Author: Lukas Wunner <lukas@wunner.de>
Date:   Sun Jan 23 05:21:14 2022 +0100

    serial: core: Initialize rs485 RTS polarity already on probe
    
    RTS polarity of rs485-enabled ports is currently initialized on uart
    open via:
    
    tty_port_open()
      tty_port_block_til_ready()
        tty_port_raise_dtr_rts()  # if (C_BAUD(tty))
          uart_dtr_rts()
            uart_port_dtr_rts()
    
    There's at least three problems here:
    
    First, if no baud rate is set, RTS polarity is not initialized.
    That's the right thing to do for rs232, but not for rs485, which
    requires that RTS is deasserted unconditionally.
    
    Second, if the DeviceTree property "linux,rs485-enabled-at-boot-time" is
    present, RTS should be deasserted as early as possible, i.e. on probe.
    Otherwise it may remain asserted until first open.
    
    Third, even though RTS is deasserted on open and close, it may
    subsequently be asserted by uart_throttle(), uart_unthrottle() or
    uart_set_termios() because those functions aren't rs485-aware.
    (Only uart_tiocmset() is.)
    
    To address these issues, move RTS initialization from uart_port_dtr_rts()
    to uart_configure_port().  Prevent subsequent modification of RTS
    polarity by moving the existing rs485 check from uart_tiocmget() to
    uart_update_mctrl().
    
    That way, RTS is initialized on probe and then remains unmodified unless
    the uart transmits data.  If rs485 is enabled at runtime (instead of at
    boot) through a TIOCSRS485 ioctl(), RTS is initialized by the uart
    driver's ->rs485_config() callback and then likewise remains unmodified.
    
    The PL011 driver initializes RTS on uart open and prevents subsequent
    modification in its ->set_mctrl() callback.  That code is obsoleted by
    the present commit, so drop it.
    
    Cc: Jan Kiszka <jan.kiszka@siemens.com>
    Cc: Su Bao Cheng <baocheng.su@siemens.com>
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/2d2acaf3a69e89b7bf687c912022b11fd29dfa1e.1642909284.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 62f676ff7898f6c1bd26ce014564773a3dc00601
Author: Jochen Mades <jochen@mades.net>
Date:   Sat Jan 23 05:10:14 2021 +0100

    serial: pl011: Fix incorrect rs485 RTS polarity on set_mctrl
    
    Commit 8d479237727c ("serial: amba-pl011: add RS485 support") sought to
    keep RTS deasserted on set_mctrl if rs485 is enabled.  However it did so
    only if deasserted RTS polarity is high.  Fix it in case it's low.
    
    Fixes: 8d479237727c ("serial: amba-pl011: add RS485 support")
    Cc: stable@vger.kernel.org # v5.15+
    Cc: Lino Sanfilippo <LinoSanfilippo@gmx.de>
    Signed-off-by: Jochen Mades <jochen@mades.net>
    [lukas: copyedit commit message, add stable designation]
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/85fa3323ba8c307943969b7343e23f34c3e652ba.1642909284.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 037b91ec7729524107982e36ec4b40f9b174f7a2
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 11 17:44:41 2022 +0100

    serial: stm32: fix software flow control transfer
    
    x_char is ignored by stm32_usart_start_tx() when xmit buffer is empty.
    
    Fix start_tx condition to allow x_char to be sent.
    
    Fixes: 48a6092fb41f ("serial: stm32-usart: Add STM32 USART Driver")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Erwan Le Ray <erwan.leray@foss.st.com>
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220111164441.6178-3-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d3d079bde07e1b7deaeb57506dc0b86010121d17
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 11 17:44:40 2022 +0100

    serial: stm32: prevent TDR register overwrite when sending x_char
    
    When sending x_char in stm32_usart_transmit_chars(), driver can overwrite
    the value of TDR register by the value of x_char. If this happens, the
    previous value that was present in TDR register will not be sent through
    uart.
    
    This code checks if the previous value in TDR register is sent before
    writing the x_char value into register.
    
    Fixes: 48a6092fb41f ("serial: stm32-usart: Add STM32 USART Driver")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220111164441.6178-2-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 8838b2af23caf1ff0610caef2795d6668a013b2d
Author: daniel.starke@siemens.com <daniel.starke@siemens.com>
Date:   Thu Jan 20 02:18:57 2022 -0800

    tty: n_gsm: fix SW flow control encoding/handling
    
    n_gsm is based on the 3GPP 07.010 and its newer version is the 3GPP 27.010.
    See https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1516
    The changes from 07.010 to 27.010 are non-functional. Therefore, I refer to
    the newer 27.010 here. Chapter 5.2.7.3 states that DC1 (XON) and DC3 (XOFF)
    are the control characters defined in ISO/IEC 646. These shall be quoted if
    seen in the data stream to avoid interpretation as flow control characters.
    
    ISO/IEC 646 refers to the set of ISO standards described as the ISO
    7-bit coded character set for information interchange. Its final version
    is also known as ITU T.50.
    See https://www.itu.int/rec/T-REC-T.50-199209-I/en
    
    To abide the standard it is needed to quote DC1 and DC3 correctly if these
    are seen as data bytes and not as control characters. The current
    implementation already tries to enforce this but fails to catch all
    defined cases. 3GPP 27.010 chapter 5.2.7.3 clearly states that the most
    significant bit shall be ignored for DC1 and DC3 handling. The current
    implementation handles only the case with the most significant bit set 0.
    Cases in which DC1 and DC3 have the most significant bit set 1 are left
    unhandled.
    
    This patch fixes this by masking the data bytes with ISO_IEC_646_MASK (only
    the 7 least significant bits set 1) before comparing them with XON
    (a.k.a. DC1) and XOFF (a.k.a. DC3) when testing which byte values need
    quotation via byte stuffing.
    
    Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
    Cc: stable@vger.kernel.org
    Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
    Link: https://lore.kernel.org/r/20220120101857.2509-1-daniel.starke@siemens.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d06b1cf28297e27127d3da54753a3a01a2fa2f28
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Wed Jan 12 13:42:14 2022 -0600

    serial: 8250: of: Fix mapped region size when using reg-offset property
    
    8250_of supports a reg-offset property which is intended to handle
    cases where the device registers start at an offset inside the region
    of memory allocated to the device. The Xilinx 16550 UART, for which this
    support was initially added, requires this. However, the code did not
    adjust the overall size of the mapped region accordingly, causing the
    driver to request an area of memory past the end of the device's
    allocation. For example, if the UART was allocated an address of
    0xb0130000, size of 0x10000 and reg-offset of 0x1000 in the device
    tree, the region of memory reserved was b0131000-b0140fff, which caused
    the driver for the region starting at b0140000 to fail to probe.
    
    Fix this by subtracting reg-offset from the mapped region size.
    
    Fixes: b912b5e2cfb3 ([POWERPC] Xilinx: of_serial support for Xilinx uart 16550.)
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220112194214.881844-1-robert.hancock@calian.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit db7f19c0aa0abcb751ff0ed694a071363f702b1d
Author: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Date:   Tue Jan 4 17:35:45 2022 +0100

    tty: rpmsg: Fix race condition releasing tty port
    
    The tty_port struct is part of the rpmsg_tty_port structure.
    The issue is that the rpmsg_tty_port structure is freed on
    rpmsg_tty_remove while it is still referenced in the tty_struct.
    Its release is not predictable due to workqueues.
    
    For instance following ftrace shows that rpmsg_tty_close is called after
    rpmsg_tty_release_cport:
    
         nr_test.sh-389     [000] .....   212.093752: rpmsg_tty_remove <-rpmsg_dev_
    remove
                 cat-1191    [001] .....   212.095697: tty_release <-__fput
          nr_test.sh-389     [000] .....   212.099166: rpmsg_tty_release_cport <-rpm
    sg_tty_remove
                 cat-1191    [001] .....   212.115352: rpmsg_tty_close <-tty_release
                 cat-1191    [001] .....   212.115371: release_tty <-tty_release_str
    
    As consequence, the port must be free only when user has released the TTY
    interface.
    
    This path :
    - Introduce the .destruct port tty ops function to release the allocated
      rpmsg_tty_port structure.
    - Introduce the .hangup tty ops function to call tty_port_hangup.
    - Manages the tty port refcounting to trig the .destruct port ops,
    - Introduces the rpmsg_tty_cleanup function to ensure that the TTY is
      removed before decreasing the port refcount.
    
    Fixes: 7c0408d80579 ("tty: add rpmsg driver")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
    Link: https://lore.kernel.org/r/20220104163545.34710-1-arnaud.pouliquen@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit f23653fe64479d96910bfda2b700b1af17c991ac
Author: Maciej W. Rozycki <macro@embecosm.com>
Date:   Wed Jan 26 09:22:54 2022 +0000

    tty: Partially revert the removal of the Cyclades public API
    
    Fix a user API regression introduced with commit f76edd8f7ce0 ("tty:
    cyclades, remove this orphan"), which removed a part of the API and
    caused compilation errors for user programs using said part, such as
    GCC 9 in its libsanitizer component[1]:
    
    .../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:160:10: fatal error: linux/cyclades.h: No such file or directory
      160 | #include <linux/cyclades.h>
          |          ^~~~~~~~~~~~~~~~~~
    compilation terminated.
    make[4]: *** [Makefile:664: sanitizer_platform_limits_posix.lo] Error 1
    
    As the absolute minimum required bring `struct cyclades_monitor' and
    ioctl numbers back then so as to make the library build again.  Add a
    preprocessor warning as to the obsolescence of the features provided.
    
    References:
    
    [1] GCC PR sanitizer/100379, "cyclades.h is removed from linux kernel
        header files", <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100379>
    
    Fixes: f76edd8f7ce0 ("tty: cyclades, remove this orphan")
    Cc: stable@vger.kernel.org # v5.13+
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Maciej W. Rozycki <macro@embecosm.com>
    Link: https://lore.kernel.org/r/alpine.DEB.2.20.2201260733430.11348@tpp.orcam.me.uk
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 152d1afa834c84530828ee031cf07a00e0fc0b8c
Author: Cameron Williams <cang1@live.co.uk>
Date:   Mon Jan 24 09:42:23 2022 +0000

    tty: Add support for Brainboxes UC cards.
    
    This commit adds support for the some of the Brainboxes PCI range of
    cards, including the UC-101, UC-235/246, UC-257, UC-268, UC-275/279,
    UC-302, UC-310, UC-313, UC-320/324, UC-346, UC-357, UC-368
    and UC-420/431.
    
    Signed-off-by: Cameron Williams <cang1@live.co.uk>
    Cc: stable <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/AM5PR0202MB2564688493F7DD9B9C610827C45E9@AM5PR0202MB2564.eurprd02.prod.outlook.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 592ee1197f78b30bd60c87db9b6c8c045c8d8314
Author: Yu Kuai <yukuai3@huawei.com>
Date:   Wed Jan 26 09:21:32 2022 +0800

    blk-mq: fix missing blk_account_io_done() in error path
    
    If blk_mq_request_issue_directly() failed from
    blk_insert_cloned_request(), the request will be accounted start.
    Currently, blk_insert_cloned_request() is only called by dm, and such
    request won't be accounted done by dm.
    
    In normal path, io will be accounted start from blk_mq_bio_to_request(),
    when the request is allocated, and such io will be accounted done from
    __blk_mq_end_request_acct() whether it succeeded or failed. Thus add
    blk_account_io_done() to fix the problem.
    
    Signed-off-by: Yu Kuai <yukuai3@huawei.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220126012132.3111551-1-yukuai3@huawei.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 6a7b9f002eca6788d346c16a6ff0c218b41f8d1d
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 26 14:33:58 2022 +0100

    Revert "tty: serial: Use fifo in 8250 console driver"
    
    This reverts commit 5021d709b31b8a14317998a33cbc78be0de9ab30.
    
    The patch is still a bit buggy, and this breaks some other hardware
    types.  It needs to be resubmitted in a non-buggy way, and make sure the
    other hardware types also continue to work properly.
    
    Fixes: 5021d709b31b ("tty: serial: Use fifo in 8250 console driver")
    Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Reported-by: Jon Hunter <jonathanh@nvidia.com>
    Link: https://lore.kernel.org/r/Ye/1+Z8mEzbKbrqG@linutronix.de
    Link: https://lore.kernel.org/r/a1ac6254-f79e-d131-fa2a-c7ad714c6d4a@nvidia.com
    Cc: Wander Lairson Costa <wander@redhat.com>
    Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e937440f7fc444a3e3f1fb75ea65292d6f433a44
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Wed Jan 26 11:04:47 2022 +0000

    spi: meson-spicc: add IRQ check in meson_spicc_probe
    
    This check misses checking for  platform_get_irq()'s call and may passes
    the negative error codes to devm_request_irq(), which takes unsigned IRQ #,
    causing it to fail with -EINVAL, overriding an original error code.
    Stop calling devm_request_irq() with invalid IRQ #s.
    
    Fixes: 454fa271bc4e ("spi: Add Meson SPICC driver")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20220126110447.24549-1-linmq006@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 8f2e5c65ec7534cce6d315fccf2c3aef023f68f0
Author: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Date:   Wed Jan 26 11:35:49 2022 +0000

    ASoC: qdsp6: q6apm-dai: only stop graphs that are started
    
    Its possible that the sound card is just opened and closed without actually
    playing stream, ex: if the audio file itself is missing.
    
    Even in such cases we do call stop on graphs that are not yet started.
    DSP can throw errors in such cases, so add a check to see if the graph
    was started before stopping it.
    
    Fixes: 9b4fe0f1cd79 ("ASoC: qdsp6: audioreach: add q6apm-dai support")
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220126113549.8853-5-srinivas.kandagatla@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit bd2347fd67d8da0fa76296507cc556da0a233bcb
Author: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Date:   Wed Jan 26 11:35:48 2022 +0000

    ASoC: codecs: wcd938x: fix return value of mixer put function
    
    wcd938x_ear_pa_put_gain, wcd938x_set_swr_port and  wcd938x_set_compander
    currently returns zero eventhough it changes the value.
    Fix this, so that change notifications are sent correctly.
    
    Fixes: e8ba1e05bdc01 ("ASoC: codecs: wcd938x: add basic controls")
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220126113549.8853-4-srinivas.kandagatla@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit fca041a3ab70a099a6d5519ecb689b6279bd04f3
Author: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Date:   Wed Jan 26 11:35:47 2022 +0000

    ASoC: codecs: lpass-rx-macro: fix sidetone register offsets
    
    For some reason we ended up with incorrect register offfset calcuations
    for sidetone. regmap clearly throw errors when accessing these incorrect
    registers as these do not belong to any read/write ranges.
    so fix them to point to correct register offsets.
    
    Fixes: f3ce6f3c9a99 ("ASoC: codecs: lpass-rx-macro: add iir widgets")
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220126113549.8853-3-srinivas.kandagatla@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit c5c1546a654f613e291a7c5d6f3660fc1eb6d0c7
Author: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Date:   Wed Jan 26 11:35:46 2022 +0000

    ASoC: codecs: wcd938x: fix incorrect used of portid
    
    Mixer controls have the channel id in mixer->reg, which is not same
    as port id. port id should be derived from chan_info array.
    So fix this. Without this, its possible that we could corrupt
    struct wcd938x_sdw_priv by accessing port_map array out of range
    with channel id instead of port id.
    
    Fixes: e8ba1e05bdc0 ("ASoC: codecs: wcd938x: add basic controls")
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    Link: https://lore.kernel.org/r/20220126113549.8853-2-srinivas.kandagatla@linaro.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 993d66140f8d1c1853a3b58b77b43b681eb64dee
Author: Fabio Estevam <festevam@gmail.com>
Date:   Sun Dec 19 19:42:15 2021 -0300

    ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
    
    GPIO7_IO00 is used as SD card detect.
    
    Properly describe this in the devicetree.
    
    Fixes: 40cdaa542cf0 ("ARM: dts: imx6q-udoo: Add initial board support")
    Signed-off-by: Fabio Estevam <festevam@gmail.com>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit 79aa3e19fe8f5be30e846df8a436bfe306e8b1a6
Author: Pawel Laszczak <pawell@cadence.com>
Date:   Tue Jan 11 10:07:37 2022 +0100

    usb: cdnsp: Fix segmentation fault in cdns_lost_power function
    
    CDNSP driver read not initialized cdns->otg_v0_regs
    which lead to segmentation fault. Patch fixes this issue.
    
    Fixes: 2cf2581cd229 ("usb: cdns3: add power lost support for system resume")
    cc: <stable@vger.kernel.org>
    Signed-off-by: Pawel Laszczak <pawell@cadence.com>
    Link: https://lore.kernel.org/r/20220111090737.10345-1-pawell@gli-login.cadence.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 23e3404de1aecc62c14ac96d4b63403c3e0f52d5
Author: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Date:   Wed Dec 22 13:48:12 2021 +0900

    spi: uniphier: Fix a bug that doesn't point to private data correctly
    
    In uniphier_spi_remove(), there is a wrong code to get private data from
    the platform device, so the driver can't be removed properly.
    
    The driver should get spi_master from the platform device and retrieve
    the private data from it.
    
    Cc: <stable@vger.kernel.org>
    Fixes: 5ba155a4d4cc ("spi: add SPI controller driver for UniPhier SoC")
    Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
    Link: https://lore.kernel.org/r/1640148492-32178-1-git-send-email-hayashi.kunihiko@socionext.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 90cafce461de108bfb07c06148395dc86c3fcd23
Author: Dongliang Mu <mudongliangabcd@gmail.com>
Date:   Mon Dec 6 18:19:31 2021 +0800

    spi: change clk_disable_unprepare to clk_unprepare
    
    The corresponding API for clk_prepare is clk_unprepare, other than
    clk_disable_unprepare.
    
    Fix this by changing clk_disable_unprepare to clk_unprepare.
    
    Fixes: 5762ab71eb24 ("spi: Add support for Armada 3700 SPI Controller")
    Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
    Link: https://lore.kernel.org/r/20211206101931.2816597-1-mudongliangabcd@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit ac55d163855924aa5af9f1560977da8f346963c8
Author: Amelie Delaunay <amelie.delaunay@foss.st.com>
Date:   Tue Dec 7 14:01:01 2021 +0100

    usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
    
    Calling dwc2_hsotg_ep_disable on ep0 (in/out) will lead to the following
    logs before returning -EINVAL:
    dwc2 49000000.usb-otg: dwc2_hsotg_ep_disable: called for ep0
    dwc2 49000000.usb-otg: dwc2_hsotg_ep_disable: called for ep0
    
    To avoid these two logs while suspending, start disabling the endpoint
    from the index 1, as done in dwc2_hsotg_udc_stop:
    
            /* all endpoints should be shutdown */
            for (ep = 1; ep < hsotg->num_of_eps; ep++) {
                    if (hsotg->eps_in[ep])
                            dwc2_hsotg_ep_disable_lock(&hsotg->eps_in[ep]->ep);
                    if (hsotg->eps_out[ep])
                            dwc2_hsotg_ep_disable_lock(&hsotg->eps_out[ep]->ep);
            }
    
    Acked-by: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
    Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
    Link: https://lore.kernel.org/r/20211207130101.270314-1-amelie.delaunay@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 26d81b29249273d39e753cc0c7b0ca62c6a6283f
Author: Miles Chen <miles.chen@mediatek.com>
Date:   Wed Jan 19 10:08:49 2022 +0800

    usb: gadget: at91_udc: fix incorrect print type
    
    Fix a build error observed with ARCH=arm DEFCONFIG=allmodconfig build.
    
    drivers/usb/gadget/udc/at91_udc.h:174:42: error: format '%d' expects argument of type 'int', but argument 3 has type 'struct gpio_desc *' [-Werror=format=]
    
    Fixes: 4a555f2b8d31 ("usb: gadget: at91_udc: Convert to GPIO descriptors")
    Reviewed-by: Macpaul Lin <macpaul.lin@mediatek.com>
    Signed-off-by: Miles Chen <miles.chen@mediatek.com>
    Link: https://lore.kernel.org/r/20220119020849.25732-1-miles.chen@mediatek.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 2cc9b1c93b1c4caa2d971856c0780fb5f7d04692
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 25 18:02:51 2022 -0600

    usb: dwc3: xilinx: Fix error handling when getting USB3 PHY
    
    The code that looked up the USB3 PHY was ignoring all errors other than
    EPROBE_DEFER in an attempt to handle the PHY not being present. Fix and
    simplify the code by using devm_phy_optional_get and dev_err_probe so
    that a missing PHY is not treated as an error and unexpected errors
    are handled properly.
    
    Fixes: 84770f028fab ("usb: dwc3: Add driver for Xilinx platforms")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220126000253.1586760-3-robert.hancock@calian.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 9678f3361afc27a3124cd2824aec0227739986fb
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 25 18:02:50 2022 -0600

    usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode
    
    It appears that the PIPE clock should not be selected when only USB 2.0
    is being used in the design and no USB 3.0 reference clock is used.
    Also, the core resets are not required if a USB3 PHY is not in use, and
    will break things if USB3 is actually used but the PHY entry is not
    listed in the device tree.
    
    Skip core resets and register settings that are only required for
    USB3 mode when no USB3 PHY is specified in the device tree.
    
    Fixes: 84770f028fab ("usb: dwc3: Add driver for Xilinx platforms")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220126000253.1586760-2-robert.hancock@calian.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 9df478463d9feb90dae24f183383961cf123a0ec
Author: Frank Li <Frank.Li@nxp.com>
Date:   Mon Jan 10 11:27:38 2022 -0600

    usb: xhci-plat: fix crash when suspend if remote wake enable
    
    Crashed at i.mx8qm platform when suspend if enable remote wakeup
    
    Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP
    Modules linked in:
    CPU: 2 PID: 244 Comm: kworker/u12:6 Not tainted 5.15.5-dirty #12
    Hardware name: Freescale i.MX8QM MEK (DT)
    Workqueue: events_unbound async_run_entry_fn
    pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    pc : xhci_disable_hub_port_wake.isra.62+0x60/0xf8
    lr : xhci_disable_hub_port_wake.isra.62+0x34/0xf8
    sp : ffff80001394bbf0
    x29: ffff80001394bbf0 x28: 0000000000000000 x27: ffff00081193b578
    x26: ffff00081193b570 x25: 0000000000000000 x24: 0000000000000000
    x23: ffff00081193a29c x22: 0000000000020001 x21: 0000000000000001
    x20: 0000000000000000 x19: ffff800014e90490 x18: 0000000000000000
    x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
    x14: 0000000000000000 x13: 0000000000000002 x12: 0000000000000000
    x11: 0000000000000000 x10: 0000000000000960 x9 : ffff80001394baa0
    x8 : ffff0008145d1780 x7 : ffff0008f95b8e80 x6 : 000000001853b453
    x5 : 0000000000000496 x4 : 0000000000000000 x3 : ffff00081193a29c
    x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff000814591620
    Call trace:
     xhci_disable_hub_port_wake.isra.62+0x60/0xf8
     xhci_suspend+0x58/0x510
     xhci_plat_suspend+0x50/0x78
     platform_pm_suspend+0x2c/0x78
     dpm_run_callback.isra.25+0x50/0xe8
     __device_suspend+0x108/0x3c0
    
    The basic flow:
            1. run time suspend call xhci_suspend, xhci parent devices gate the clock.
            2. echo mem >/sys/power/state, system _device_suspend call xhci_suspend
            3. xhci_suspend call xhci_disable_hub_port_wake, which access register,
               but clock already gated by run time suspend.
    
    This problem was hidden by power domain driver, which call run time resume before it.
    
    But the below commit remove it and make this issue happen.
            commit c1df456d0f06e ("PM: domains: Don't runtime resume devices at genpd_prepare()")
    
    This patch call run time resume before suspend to make sure clock is on
    before access register.
    
    Reviewed-by: Peter Chen <peter.chen@kernel.org>
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Frank Li <Frank.Li@nxp.com>
    Testeb-by: Abel Vesa <abel.vesa@nxp.com>
    Link: https://lore.kernel.org/r/20220110172738.31686-1-Frank.Li@nxp.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 2e3dd4a6246945bf84ea6f478365d116e661554c
Author: Jon Hunter <jonathanh@nvidia.com>
Date:   Mon Jan 17 15:00:39 2022 +0000

    usb: common: ulpi: Fix crash in ulpi_match()
    
    Commit 7495af930835 ("ARM: multi_v7_defconfig: Enable drivers for
    DragonBoard 410c") enables the CONFIG_PHY_QCOM_USB_HS for the ARM
    multi_v7_defconfig. Enabling this Kconfig is causing the kernel to crash
    on the Tegra20 Ventana platform in the ulpi_match() function.
    
    The Qualcomm USB HS PHY driver that is enabled by CONFIG_PHY_QCOM_USB_HS,
    registers a ulpi_driver but this driver does not provide an 'id_table',
    so when ulpi_match() is called on the Tegra20 Ventana platform, it
    crashes when attempting to deference the id_table pointer which is not
    valid. The Qualcomm USB HS PHY driver uses device-tree for matching the
    ULPI driver with the device and so fix this crash by using device-tree
    for matching if the id_table is not valid.
    
    Fixes: ef6a7bcfb01c ("usb: ulpi: Support device discovery via DT")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
    Link: https://lore.kernel.org/r/20220117150039.44058-1-jonathanh@nvidia.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 904edf8aeb459697129be5fde847e2a502f41fd9
Author: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
Date:   Sat Jan 22 08:33:22 2022 +0530

    usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
    
    Currently when gadget enumerates in super speed plus, the isoc
    endpoint request buffer size is not calculated correctly. Fix
    this by checking the gadget speed against USB_SPEED_SUPER_PLUS
    and update the request buffer size.
    
    Fixes: 90c4d05780d4 ("usb: fix various gadgets null ptr deref on 10gbps cabling.")
    Cc: stable <stable@vger.kernel.org>
    Signed-off-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
    Link: https://lore.kernel.org/r/1642820602-20619-1-git-send-email-quic_pkondeti@quicinc.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 825911492eb15bf8bb7fb94bc0c0421fe7a6327d
Author: Sing-Han Chen <singhanc@nvidia.com>
Date:   Wed Jan 12 17:41:43 2022 +0800

    ucsi_ccg: Check DEV_INT bit only when starting CCG4
    
    CCGx clears Bit 0:Device Interrupt in the INTR_REG
    if CCGx is reset successfully. However, there might
    be a chance that other bits in INTR_REG are not
    cleared due to internal data queued in PPM. This case
    misleads the driver that CCGx reset failed.
    
    The commit checks bit 0 in INTR_REG and ignores other
    bits. The ucsi driver would reset PPM later.
    
    Fixes: 247c554a14aa ("usb: typec: ucsi: add support for Cypress CCGx")
    Cc: stable@vger.kernel.org
    Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Sing-Han Chen <singhanc@nvidia.com>
    Signed-off-by: Wayne Chang <waynec@nvidia.com>
    Link: https://lore.kernel.org/r/20220112094143.628610-1-waynec@nvidia.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 0c566618e27f17b5807086dba8c222ca8ca3dc1e
Author: Tim Harvey <tharvey@gateworks.com>
Date:   Thu Dec 16 08:12:27 2021 -0800

    arm64: dts: imx8mn-venice-gw7902: disable gpu
    
    Since commit 99aa29932271 ("arm64: dts: imx8mn: Enable GPU")
    imx8mn-venice-gw7902 will hang during kernel init because it uses
    a MIMX8MN5CVTI which does not have a GPU.
    
    Disable pgc_gpumix to work around this. We also disable the GPU devices
    that depend on the gpumix power domain and pgc_gpu to avoid them staying
    in a probe deferred state forever.
    
    Cc: Adam Ford <aford173@gmail.com>
    Cc: Lucas Stach <l.stach@pengutronix.de>
    Signed-off-by: Tim Harvey <tharvey@gateworks.com>
    Fixes: 99aa29932271 ("arm64: dts: imx8mn: Enable GPU")
    Reviewed-by: Adam Ford <aford173@gmail.com>
    Signed-off-by: Shawn Guo <shawnguo@kernel.org>

commit c733ebb7cb67dfb146a07c0ae329a0de9ec52f36
Author: Marc Zyngier <maz@kernel.org>
Date:   Mon Jan 24 13:38:09 2022 +0000

    irqchip/gic-v3-its: Reset each ITS's BASERn register before probe
    
    A recent bug report outlined that the way GICv4.1 is handled across
    kexec is pretty bad. We can end-up in a situation where ITSs share
    memory (this is the case when SVPET==1) and reprogram the base
    registers, creating a situation where ITSs that are part of a given
    affinity group see different pointers. Which is illegal. Boo.
    
    In order to restore some sanity, reset the BASERn registers to 0
    *before* probing any ITS. Although this isn't optimised at all,
    this is only a once-per-boot cost, which shouldn't show up on
    anyone's radar.
    
    Cc: Jay Chen <jkchen@linux.alibaba.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Link: https://lore.kernel.org/r/20211216190315.GA14220@lpieralisi
    Link: https://lore.kernel.org/r/20220124133809.1291195-1-maz@kernel.org

commit 31eeb6b09f4053f32a30ce9fbcdfca31f713028d
Author: Robin Murphy <robin.murphy@arm.com>
Date:   Mon Jan 24 17:57:01 2022 +0000

    arm64: dts: juno: Remove GICv2m dma-range
    
    Although it is painstakingly honest to describe all 3 PCI windows in
    "dma-ranges", it misses the the subtle distinction that the window for
    the GICv2m range is normally programmed for Device memory attributes
    rather than Normal Cacheable like the DRAM windows. Since MMU-401 only
    offers stage 2 translation, this means that when the PCI SMMU is
    enabled, accesses through that IPA range unexpectedly lose coherency if
    mapped as cacheable at the SMMU, due to the attribute combining rules.
    Since an extra 256KB is neither here nor there when we still have 10GB
    worth of usable address space, rather than attempting to describe and
    cope with this detail let's just remove the offending range. If the SMMU
    is not used then it makes no difference anyway.
    
    Link: https://lore.kernel.org/r/856c3f7192c6c3ce545ba67462f2ce9c86ed6b0c.1643046936.git.robin.murphy@arm.com
    Fixes: 4ac4d146cb63 ("arm64: dts: juno: Describe PCI dma-ranges")
    Reported-by: Anders Roxell <anders.roxell@linaro.org>
    Acked-by: Liviu Dudau <liviu.dudau@arm.com>
    Signed-off-by: Robin Murphy <robin.murphy@arm.com>
    Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>

commit 76cea3d95513fe40000d06a3719c4bb6b53275e2
Author: Dave Airlie <airlied@redhat.com>
Date:   Thu Jan 20 14:05:27 2022 +1000

    Revert "drm/ast: Support 1600x900 with 108MHz PCLK"
    
    This reverts commit 9bb7b689274b67ecb3641e399e76f84adc627df1.
    
    This caused a regression reported to Red Hat.
    
    Fixes: 9bb7b689274b ("drm/ast: Support 1600x900 with 108MHz PCLK")
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220120040527.552068-1-airlied@gmail.com

commit 9161f365c91614e5a3f5c6dcc44c3b1b33bc59c0
Author: Christian Eggers <ceggers@arri.de>
Date:   Tue Jan 25 09:16:19 2022 +0100

    mtd: rawnand: gpmi: don't leak PM reference in error path
    
    If gpmi_nfc_apply_timings() fails, the PM runtime usage counter must be
    dropped.
    
    Reported-by: Pavel Machek <pavel@denx.de>
    Fixes: f53d4c109a66 ("mtd: rawnand: gpmi: Add ERR007117 protection for nfc_apply_timings")
    Signed-off-by: Christian Eggers <ceggers@arri.de>
    Cc: stable@vger.kernel.org
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220125081619.6286-1-ceggers@arri.de

commit 48ee4835b73c48590d05a54730dc8037ebd39d3b
Merge: 5ec1cebd59300 e783362eb54cd
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Wed Jan 26 09:40:24 2022 +0100

    Merge drm/drm-fixes into drm-misc-fixes
    
    Backmerging drm/drm-fixes into drm-misc-fixes for v5.17-rc1.
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>

commit e03c3bba351f99ad932e8f06baa9da1afc418e02
Author: Yan Yan <evitayan@google.com>
Date:   Tue Jan 18 16:00:14 2022 -0800

    xfrm: Fix xfrm migrate issues when address family changes
    
    xfrm_migrate cannot handle address family change of an xfrm_state.
    The symptons are the xfrm_state will be migrated to a wrong address,
    and sending as well as receiving packets wil be broken.
    
    This commit fixes it by breaking the original xfrm_state_clone
    method into two steps so as to update the props.family before
    running xfrm_init_state. As the result, xfrm_state's inner mode,
    outer mode, type and IP header length in xfrm_state_migrate can
    be updated with the new address family.
    
    Tested with additions to Android's kernel unit test suite:
    https://android-review.googlesource.com/c/kernel/tests/+/1885354
    
    Signed-off-by: Yan Yan <evitayan@google.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit c1aca3080e382886e2e58e809787441984a2f89b
Author: Yan Yan <evitayan@google.com>
Date:   Tue Jan 18 16:00:13 2022 -0800

    xfrm: Check if_id in xfrm_migrate
    
    This patch enables distinguishing SAs and SPs based on if_id during
    the xfrm_migrate flow. This ensures support for xfrm interfaces
    throughout the SA/SP lifecycle.
    
    When there are multiple existing SPs with the same direction,
    the same xfrm_selector and different endpoint addresses,
    xfrm_migrate might fail with ENODATA.
    
    Specifically, the code path for performing xfrm_migrate is:
      Stage 1: find policy to migrate with
        xfrm_migrate_policy_find(sel, dir, type, net)
      Stage 2: find and update state(s) with
        xfrm_migrate_state_find(mp, net)
      Stage 3: update endpoint address(es) of template(s) with
        xfrm_policy_migrate(pol, m, num_migrate)
    
    Currently "Stage 1" always returns the first xfrm_policy that
    matches, and "Stage 3" looks for the xfrm_tmpl that matches the
    old endpoint address. Thus if there are multiple xfrm_policy
    with same selector, direction, type and net, "Stage 1" might
    rertun a wrong xfrm_policy and "Stage 3" will fail with ENODATA
    because it cannot find a xfrm_tmpl with the matching endpoint
    address.
    
    The fix is to allow userspace to pass an if_id and add if_id
    to the matching rule in Stage 1 and Stage 2 since if_id is a
    unique ID for xfrm_policy and xfrm_state. For compatibility,
    if_id will only be checked if the attribute is set.
    
    Tested with additions to Android's kernel unit test suite:
    https://android-review.googlesource.com/c/kernel/tests/+/1668886
    
    Signed-off-by: Yan Yan <evitayan@google.com>
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 429c3be8a5e2695b5b92a6a12361eb89eb185495
Author: Maxim Mikityanskiy <maximmi@nvidia.com>
Date:   Tue Jan 25 12:06:54 2022 +0200

    sch_htb: Fail on unsupported parameters when offload is requested
    
    The current implementation of HTB offload doesn't support some
    parameters. Instead of ignoring them, actively return the EINVAL error
    when they are set to non-defaults.
    
    As this patch goes to stable, the driver API is not changed here. If
    future drivers support more offload parameters, the checks can be moved
    to the driver side.
    
    Note that the buffer and cbuffer parameters are also not supported, but
    the tc userspace tool assigns some default values derived from rate and
    ceil, and identifying these defaults in sch_htb would be unreliable, so
    they are still ignored.
    
    Fixes: d03b195b5aa0 ("sch_htb: Hierarchical QoS hardware offload")
    Reported-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Link: https://lore.kernel.org/r/20220125100654.424570-1-maximmi@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e2bcbd7769ee8f05e1b3d10848aace98973844e4
Author: Sean Young <sean@mess.org>
Date:   Mon Jan 24 15:30:28 2022 +0000

    tools headers UAPI: remove stale lirc.h
    
    The lirc.h file is an old copy of lirc.h from the kernel sources. It is
    out of date, and the bpf lirc tests don't need a new copy anyway. As
    long as /usr/include/linux/lirc.h is from kernel v5.2 or newer, the tests
    will compile fine.
    
    Signed-off-by: Sean Young <sean@mess.org>
    Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220124153028.394409-1-sean@mess.org
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 0e3135d3bfa5dfb658145238d2bc723a8e30c3a3
Author: He Fengqing <hefengqing@huawei.com>
Date:   Sat Jan 22 10:29:36 2022 +0000

    bpf: Fix possible race in inc_misses_counter
    
    It seems inc_misses_counter() suffers from same issue fixed in
    the commit d979617aa84d ("bpf: Fixes possible race in update_prog_stats()
    for 32bit arches"):
    As it can run while interrupts are enabled, it could
    be re-entered and the u64_stats syncp could be mangled.
    
    Fixes: 9ed9e9ba2337 ("bpf: Count the number of times recursion was prevented")
    Signed-off-by: He Fengqing <hefengqing@huawei.com>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Link: https://lore.kernel.org/r/20220122102936.1219518-1-hefengqing@huawei.com
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit c035366d9c9fe48d947ee6c43465ab43d42e20f2
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Mon Jan 24 12:30:03 2022 +0100

    PCI: mt7621: Remove unused function pcie_rmw()
    
    Function pcie_rmw() is not being used at all and can be deleted. Hence get
    rid of it, which fixes this warning:
    
      drivers/pci/controller/pcie-mt7621.c:112:20: warning: unused function 'pcie_rmw' [-Wunused-function]
    
    Fixes: 2bdd5238e756 ("PCI: mt7621: Add MediaTek MT7621 PCIe host controller driver")
    Link: https://lore.kernel.org/r/20220124113003.406224-3-sergio.paracuellos@gmail.com
    Link: https://lore.kernel.org/all/202201241754.igtHzgHv-lkp@intel.com/
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 4b77e4abb32cddb9e666e2ac411b0b0d6b8331dd
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Mon Jan 24 12:30:02 2022 +0100

    PCI: mt7621: Drop of_match_ptr() to avoid unused variable
    
    We have stubs for most OF interfaces even when CONFIG_OF is not set, so we
    allow building of pcie-mt7621.c in that case for compile testing.
    
    When CONFIG_OF is not set, "of_match_ptr(mt7621_pcie_ids)" compiles to
    NULL, which leaves mt7621_pcie_ids unused:
    
      $ make W=1
      drivers/pci/controller/pcie-mt7621.c:549:34: warning: unused variable 'mt7621_pcie_ids' [-Wunused-const-variable]
    
    Drop of_match_ptr() to avoid the unused variable warning.
    
    [bhelgaas: commit log]
    Fixes: 2bdd5238e756 ("PCI: mt7621: Add MediaTek MT7621 PCIe host controller driver")
    Link: https://lore.kernel.org/r/20220124113003.406224-2-sergio.paracuellos@gmail.com
    Link: https://lore.kernel.org/r/202201241754.igtHzgHv-lkp@intel.com
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 2a807341ed1074ab83638f2fab08dffaa373f6b8
Author: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Date:   Sun Jan 23 03:38:28 2022 +0100

    drm/amdgpu/display: Remove t_srx_delay_us.
    
    Unused. Convert the divisions into asserts on the divisor, to
    debug why it is zero. The divide by zero is suspected of causing
    kernel panics.
    
    While I have no idea where the zero is coming from I think this
    patch is a positive either way.
    
    Cc: stable@vger.kernel.org
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 25f1488bdbba63415239ff301fe61a8546140d9f
Author: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Date:   Mon Jan 24 01:23:36 2022 +0100

    drm/amd/display: Wrap dcn301_calculate_wm_and_dlg for FPU.
    
    Mirrors the logic for dcn30. Cue lots of WARNs and some
    kernel panics without this fix.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 72a8d87b87270bff0c0b2fed4d59c48d0dd840d7
Author: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Date:   Mon Jan 24 01:23:35 2022 +0100

    drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
    
    It calls populate_dml_pipes which uses doubles to initialize the
    scale_ratio_depth params. Mirrors the dcn20 logic.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ebc77bcc6e1660a011483c035d53c461c8dcc4f5
Author: Zhou Qingyang <zhou1615@umn.edu>
Date:   Tue Jan 25 00:55:51 2022 +0800

    drm/amd/display/dc/calcs/dce_calcs: Fix a memleak in calculate_bandwidth()
    
    In calculate_bandwidth(), the tag free_sclk and free_yclk are reversed,
    which could lead to a memory leak of yclk.
    
    Fix this bug by changing the location of free_sclk and free_yclk.
    
    This bug was found by a static analyzer.
    
    Builds with 'make allyesconfig' show no new warnings,
    and our static analyzer no longer warns about this code.
    
    Fixes: 2be8989d0fc2 ("drm/amd/display/dc/calcs/dce_calcs: Move some large variables from the stack to the heap")
    Signed-off-by: Zhou Qingyang <zhou1615@umn.edu>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 98fdcacb45f7cd2092151d6af2e60152811eb79c
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Jan 20 12:57:33 2022 -0500

    drm/amdgpu/display: use msleep rather than udelay for long delays
    
    Some architectures (e.g., ARM) throw an compilation error if the
    udelay is too long.  In general udelays of longer than 2000us are
    not recommended on any architecture.  Switch to msleep in these
    cases.
    
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit dc919d670c6fd1ac81ebf31625cd19579f7b3d4c
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Jan 20 12:52:13 2022 -0500

    drm/amdgpu/display: adjust msleep limit in dp_wait_for_training_aux_rd_interval
    
    Some architectures (e.g., ARM) have relatively low udelay limits.
    On most architectures, anything longer than 2000us is not recommended.
    Change the check to align with other similar checks in DC.
    
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 9e5a14bce2402e84251a10269df0235cd7ce9234
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Thu Jan 20 12:17:07 2022 -0500

    drm/amdgpu: filter out radeon secondary ids as well
    
    Older radeon boards (r2xx-r5xx) had secondary PCI functions
    which we solely there for supporting multi-head on OSs with
    special requirements.  Add them to the unsupported list
    as well so we don't attempt to bind to them.  The driver
    would fail to bind to them anyway, but this does so
    in a cleaner way that should not confuse the user.
    
    Cc: stable@vger.kernel.org
    Acked-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 7e38ac562b820915faa33a5077ca9bccf42d39d2
Author: Zhan Liu <zhan.liu@amd.com>
Date:   Wed Jan 19 17:07:53 2022 -0500

    drm/amd/display: change FIFO reset condition to embedded display only
    
    [Why]
    FIFO reset is only necessary for fast boot sequence, where otg is disabled
    and dig fe is enabled when changing dispclk. Fast boot is only enabled
    on embedded displays.
    
    [How]
    Change FIFO reset condition to "embedded display only".
    
    Signed-off-by: Zhan Liu <zhan.liu@amd.com>
    Reviewed-by: Charlene Liu <charlene.liu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ac46d93235074a6c5d280d35771c23fd8620e7d9
Author: Zhan Liu <zhan.liu@amd.com>
Date:   Wed Jan 19 16:55:16 2022 -0500

    drm/amd/display: Correct MPC split policy for DCN301
    
    [Why]
    DCN301 has seamless boot enabled. With MPC split enabled
    at the same time, system will hang.
    
    [How]
    Revert MPC split policy back to "MPC_SPLIT_AVOID". Since we have
    ODM combine enabled on DCN301, pipe split is not necessary here.
    
    Signed-off-by: Zhan Liu <zhan.liu@amd.com>
    Reviewed-by: Charlene Liu <charlene.liu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 5f0c749158158f89eba7647bdc4e8096979de981
Author: Meenakshikumar Somasundaram <meenakshikumar.somasundaram@amd.com>
Date:   Mon Nov 15 01:51:37 2021 -0500

    drm/amd/display: Fix for otg synchronization logic
    
    [Why]
    During otg sync trigger, plane states are used to decide whether the otg
    is already synchronized or not. There are scenarions when otgs are
    disabled without plane state getting disabled and in such case the otg is
    excluded from synchronization.
    
    [How]
    Introduced pipe_idx_syncd in pipe_ctx that tracks each otgs master pipe.
    When a otg is disabled/enabled, pipe_idx_syncd is reset to itself.
    On sync trigger, pipe_idx_syncd is checked to decide whether a otg is
    already synchronized and the otg is further included or excluded from
    synchronization.
    
    v2:
      Don't drop is_blanked logic
    
    Reviewed-by: Jun Lei <Jun.Lei@amd.com>
    Reviewed-by: Mustapha Ghaddar <mustapha.ghaddar@amd.com>
    Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
    Signed-off-by: meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Harry Wentland <harry.wentland@amd.com>
    Cc: torvalds@linux-foundation.org
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 809232619f5b15e31fb3563985e705454f32621f
Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date:   Mon Jan 17 15:30:10 2022 -0500

    sched/membarrier: Fix membarrier-rseq fence command missing from query bitmask
    
    The membarrier command MEMBARRIER_CMD_QUERY allows querying the
    available membarrier commands. When the membarrier-rseq fence commands
    were added, a new MEMBARRIER_CMD_PRIVATE_EXPEDITED_RSEQ_BITMASK was
    introduced with the intent to expose them with the MEMBARRIER_CMD_QUERY
    command, the but it was never added to MEMBARRIER_CMD_BITMASK.
    
    The membarrier-rseq fence commands are therefore not wired up with the
    query command.
    
    Rename MEMBARRIER_CMD_PRIVATE_EXPEDITED_RSEQ_BITMASK to
    MEMBARRIER_PRIVATE_EXPEDITED_RSEQ_BITMASK (the bitmask is not a command
    per-se), and change the erroneous
    MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_RSEQ_BITMASK (which does not
    actually exist) to MEMBARRIER_CMD_REGISTER_PRIVATE_EXPEDITED_RSEQ.
    
    Wire up MEMBARRIER_PRIVATE_EXPEDITED_RSEQ_BITMASK in
    MEMBARRIER_CMD_BITMASK. Fixing this allows discovering availability of
    the membarrier-rseq fence feature.
    
    Fixes: 2a36ab717e8f ("rseq/membarrier: Add MEMBARRIER_CMD_PRIVATE_EXPEDITED_RSEQ")
    Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: <stable@vger.kernel.org> # 5.10+
    Link: https://lkml.kernel.org/r/20220117203010.30129-1-mathieu.desnoyers@efficios.com

commit 92d25637a3a45904292c93f1863c6bbda4e3e38f
Author: Li Zhijian <lizhijian@cn.fujitsu.com>
Date:   Fri Dec 17 17:29:55 2021 +0800

    kselftest: signal all child processes
    
    We have some many cases that will create child process as well, such as
    pidfd_wait. Previously, we will signal/kill the parent process when it
    is time out, but this signal will not be sent to its child process. In
    such case, if child process doesn't terminate itself, ksefltest framework
    will hang forever.
    
    Here we group all its child processes so that kill() can signal all of
    them in timeout.
    
    Fixed change log: Shuah Khan <skhan@linuxfoundation.org>
    
    Suggested-by: yang xu <xuyang2018.jy@cn.fujitsu.com>
    Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 40d70d4d60974c28054a60316f2aec8810833526
Author: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Date:   Fri Jan 14 18:21:26 2022 -0500

    selftests: cpufreq: Write test output to stdout as well
    
    Use 'tee' to send the test output to stdout in addition to the current
    output file. This makes the output easier to handle in automated test
    systems and is superior to only later dumping the output file contents
    to stdout, since this way the test output can be interleaved with other
    log messages, like from the kernel, so that chronology is preserved,
    making it easier to detect issues.
    
    Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit f034cc1301e7d83d4ec428dd6b8ffb57ca446efb
Author: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Date:   Wed Jan 12 14:41:42 2022 -0500

    selftests: rtc: Increase test timeout so that all tests run
    
    The timeout setting for the rtc kselftest is currently 90 seconds. This
    setting is used by the kselftest runner to stop running a test if it
    takes longer than the assigned value.
    
    However, two of the test cases inside rtc set alarms. These alarms are
    set to the next beginning of the minute, so each of these test cases may
    take up to, in the worst case, 60 seconds.
    
    In order to allow for all test cases in rtc to run, even in the worst
    case, when using the kselftest runner, the timeout value should be
    increased to at least 120. Set it to 180, so there's some additional
    slack.
    
    Correct operation can be tested by running the following command right
    after the start of a minute (low second count), and checking that all
    test cases run:
    
            ./run_kselftest.sh -c rtc
    
    Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
    Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit 235528072f28b3b0a1446279b7eaddda36dbf743
Author: Michał Winiarski <michal.winiarski@intel.com>
Date:   Thu Jan 13 00:36:57 2022 +0100

    kunit: tool: Import missing importlib.abc
    
    Python 3.10.0 contains:
    9e09849d20 ("bpo-41006: importlib.util no longer imports typing (GH-20938)")
    
    It causes importlib.util to no longer import importlib.abs, which leads
    to the following error when trying to use kunit with qemu:
    AttributeError: module 'importlib' has no attribute 'abc'. Did you mean: '_abc'?
    
    Add the missing import.
    
    Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
    Reviewed-by: Daniel Latypov <dlatypov@google.com>
    Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

commit f26d04331360d42dbd6b58448bd98e4edbfbe1c5
Author: Paul Moore <paul@paul-moore.com>
Date:   Thu Jan 13 18:54:38 2022 -0500

    audit: improve audit queue handling when "audit=1" on cmdline
    
    When an admin enables audit at early boot via the "audit=1" kernel
    command line the audit queue behavior is slightly different; the
    audit subsystem goes to greater lengths to avoid dropping records,
    which unfortunately can result in problems when the audit daemon is
    forcibly stopped for an extended period of time.
    
    This patch makes a number of changes designed to improve the audit
    queuing behavior so that leaving the audit daemon in a stopped state
    for an extended period does not cause a significant impact to the
    system.
    
    - kauditd_send_queue() is now limited to looping through the
      passed queue only once per call.  This not only prevents the
      function from looping indefinitely when records are returned
      to the current queue, it also allows any recovery handling in
      kauditd_thread() to take place when kauditd_send_queue()
      returns.
    
    - Transient netlink send errors seen as -EAGAIN now cause the
      record to be returned to the retry queue instead of going to
      the hold queue.  The intention of the hold queue is to store,
      perhaps for an extended period of time, the events which led
      up to the audit daemon going offline.  The retry queue remains
      a temporary queue intended to protect against transient issues
      between the kernel and the audit daemon.
    
    - The retry queue is now limited by the audit_backlog_limit
      setting, the same as the other queues.  This allows admins
      to bound the size of all of the audit queues on the system.
    
    - kauditd_rehold_skb() now returns records to the end of the
      hold queue to ensure ordering is preserved in the face of
      recent changes to kauditd_send_queue().
    
    Cc: stable@vger.kernel.org
    Fixes: 5b52330bbfe63 ("audit: fix auditd/kernel connection state tracking")
    Fixes: f4b3ee3c85551 ("audit: improve robustness of the audit queue handling")
    Reported-by: Gaosheng Cui <cuigaosheng1@huawei.com>
    Tested-by: Gaosheng Cui <cuigaosheng1@huawei.com>
    Reviewed-by: Richard Guy Briggs <rgb@redhat.com>
    Signed-off-by: Paul Moore <paul@paul-moore.com>

commit 0280e3c58f92b2fe0e8fbbdf8d386449168de4a8
Merge: 7938d61591d33 aed28b7a2d620
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 25 20:16:03 2022 +0200

    Merge tag 'nfs-for-5.17-1' of git://git.linux-nfs.org/projects/anna/linux-nfs
    
    Pull NFS client updates from Anna Schumaker:
     "New Features:
    
       - Basic handling for case insensitive filesystems
    
       - Initial support for fs_locations and server trunking
    
      Bugfixes and Cleanups:
    
       - Cleanups to how the "struct cred *" is handled for the
         nfs_access_entry
    
       - Ensure the server has an up to date ctimes before hardlinking or
         renaming
    
       - Update 'blocks used' after writeback, fallocate, and clone
    
       - nfs_atomic_open() fixes
    
       - Improvements to sunrpc tracing
    
       - Various null check & indenting related cleanups
    
       - Some improvements to the sunrpc sysfs code:
          - Use default_groups in kobj_type
          - Fix some potential races and reference leaks
    
       - A few tracepoint cleanups in xprtrdma"
    
    [ This should have gone in during the merge window, but didn't. The
      original pull request - sent during the merge window - had gotten
      marked as spam and discarded due missing DKIM headers in the email
      from Anna.   - Linus ]
    
    * tag 'nfs-for-5.17-1' of git://git.linux-nfs.org/projects/anna/linux-nfs: (35 commits)
      SUNRPC: Don't dereference xprt->snd_task if it's a cookie
      xprtrdma: Remove definitions of RPCDBG_FACILITY
      xprtrdma: Remove final dprintk call sites from xprtrdma
      sunrpc: Fix potential race conditions in rpc_sysfs_xprt_state_change()
      net/sunrpc: fix reference count leaks in rpc_sysfs_xprt_state_change
      NFSv4.1 test and add 4.1 trunking transport
      SUNRPC allow for unspecified transport time in rpc_clnt_add_xprt
      NFSv4 handle port presence in fs_location server string
      NFSv4 expose nfs_parse_server_name function
      NFSv4.1 query for fs_location attr on a new file system
      NFSv4 store server support for fs_location attribute
      NFSv4 remove zero number of fs_locations entries error check
      NFSv4: nfs_atomic_open() can race when looking up a non-regular file
      NFSv4: Handle case where the lookup of a directory fails
      NFSv42: Fallocate and clone should also request 'blocks used'
      NFSv4: Allow writebacks to request 'blocks used'
      SUNRPC: use default_groups in kobj_type
      NFS: use default_groups in kobj_type
      NFS: Fix the verifier for case sensitive filesystem in nfs_atomic_open()
      NFS: Add a helper to remove case-insensitive aliases
      ...

commit 7938d61591d33394a21bdd7797a245b65428f44c
Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Date:   Tue Oct 19 13:27:10 2021 +0100

    drm/i915: Flush TLBs before releasing backing store
    
    We need to flush TLBs before releasing backing store otherwise userspace
    is able to encounter stale entries if a) it is not declaring access to
    certain buffers and b) it races with the backing store release from a
    such undeclared execution already executing on the GPU in parallel.
    
    The approach taken is to mark any buffer objects which were ever bound
    to the GPU and to trigger a serialized TLB flush when their backing
    store is released.
    
    Alternatively the flushing could be done on VMA unbind, at which point
    we would be able to ascertain whether there is potential a parallel GPU
    execution (which could race), but essentially it boils down to paying
    the cost of TLB flushes potentially needlessly at VMA unbind time (when
    the backing store is not known to be going away so not needed for
    safety), versus potentially needlessly at backing store relase time
    (since we at that point cannot tell whether there is anything executing
    on the GPU which uses that object).
    
    Thereforce simplicity of implementation has been chosen for now with
    scope to benchmark and refine later as required.
    
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Reported-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>
    Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Acked-by: Dave Airlie <airlied@redhat.com>
    Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
    Cc: Jon Bloomfield <jon.bloomfield@intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e3d26528e083e612314d4dcd713f3d5a26143ddc
Author: Lucas Stach <l.stach@pengutronix.de>
Date:   Thu Jan 6 19:10:21 2022 +0100

    drm/etnaviv: relax submit size limits
    
    While all userspace tried to limit commandstreams to 64K in size,
    a bug in the Mesa driver lead to command streams of up to 128K
    being submitted. Allow those to avoid breaking existing userspace.
    
    Fixes: 6dfa2fab8ddd ("drm/etnaviv: limit submit sizes")
    Cc: stable@vger.kernel.org
    Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
    Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>

commit 26fbe9772b8c459687930511444ce443011f86bf
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Mon Jan 24 15:23:45 2022 -0500

    USB: core: Fix hang in usb_kill_urb by adding memory barriers
    
    The syzbot fuzzer has identified a bug in which processes hang waiting
    for usb_kill_urb() to return.  It turns out the issue is not unlinking
    the URB; that works just fine.  Rather, the problem arises when the
    wakeup notification that the URB has completed is not received.
    
    The reason is memory-access ordering on SMP systems.  In outline form,
    usb_kill_urb() and __usb_hcd_giveback_urb() operating concurrently on
    different CPUs perform the following actions:
    
    CPU 0                                   CPU 1
    ----------------------------            ---------------------------------
    usb_kill_urb():                         __usb_hcd_giveback_urb():
      ...                                     ...
      atomic_inc(&urb->reject);               atomic_dec(&urb->use_count);
      ...                                     ...
      wait_event(usb_kill_urb_queue,
            atomic_read(&urb->use_count) == 0);
                                              if (atomic_read(&urb->reject))
                                                    wake_up(&usb_kill_urb_queue);
    
    Confining your attention to urb->reject and urb->use_count, you can
    see that the overall pattern of accesses on CPU 0 is:
    
            write urb->reject, then read urb->use_count;
    
    whereas the overall pattern of accesses on CPU 1 is:
    
            write urb->use_count, then read urb->reject.
    
    This pattern is referred to in memory-model circles as SB (for "Store
    Buffering"), and it is well known that without suitable enforcement of
    the desired order of accesses -- in the form of memory barriers -- it
    is entirely possible for one or both CPUs to execute their reads ahead
    of their writes.  The end result will be that sometimes CPU 0 sees the
    old un-decremented value of urb->use_count while CPU 1 sees the old
    un-incremented value of urb->reject.  Consequently CPU 0 ends up on
    the wait queue and never gets woken up, leading to the observed hang
    in usb_kill_urb().
    
    The same pattern of accesses occurs in usb_poison_urb() and the
    failure pathway of usb_hcd_submit_urb().
    
    The problem is fixed by adding suitable memory barriers.  To provide
    proper memory-access ordering in the SB pattern, a full barrier is
    required on both CPUs.  The atomic_inc() and atomic_dec() accesses
    themselves don't provide any memory ordering, but since they are
    present, we can use the optimized smp_mb__after_atomic() memory
    barrier in the various routines to obtain the desired effect.
    
    This patch adds the necessary memory barriers.
    
    CC: <stable@vger.kernel.org>
    Reported-and-tested-by: syzbot+76629376e06e2c2ad626@syzkaller.appspotmail.com
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Link: https://lore.kernel.org/r/Ye8K0QYee0Q0Nna2@rowland.harvard.edu
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5b67b315037250a61861119683e7fcb509deea25
Author: Alan Stern <stern@rowland.harvard.edu>
Date:   Mon Jan 24 15:14:40 2022 -0500

    usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
    
    Two people have reported (and mentioned numerous other reports on the
    web) that VIA's VL817 USB-SATA bridge does not work with the uas
    driver.  Typical log messages are:
    
    [ 3606.232149] sd 14:0:0:0: [sdg] tag#2 uas_zap_pending 0 uas-tag 1 inflight: CMD
    [ 3606.232154] sd 14:0:0:0: [sdg] tag#2 CDB: Write(16) 8a 00 00 00 00 00 18 0c c9 80 00 00 00 80 00 00
    [ 3606.306257] usb 4-4.4: reset SuperSpeed Plus Gen 2x1 USB device number 11 using xhci_hcd
    [ 3606.328584] scsi host14: uas_eh_device_reset_handler success
    
    Surprisingly, the devices do seem to work okay for some other people.
    The cause of the differing behaviors is not known.
    
    In the hope of getting the devices to work for the most users, even at
    the possible cost of degraded performance for some, this patch adds an
    unusual_devs entry for the VL817 to block it from binding to the uas
    driver by default.  Users will be able to override this entry by means
    of a module parameter, if they want.
    
    CC: <stable@vger.kernel.org>
    Reported-by: DocMAX <mail@vacharakis.de>
    Reported-and-tested-by: Thomas Weißschuh <linux@weissschuh.net>
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Link: https://lore.kernel.org/r/Ye8IsK2sjlEv1rqU@rowland.harvard.edu
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 746f96e7d6f7a276726860f696671766bfb24cf0
Author: Badhri Jagan Sridharan <badhri@google.com>
Date:   Fri Jan 21 17:55:20 2022 -0800

    usb: typec: tcpm: Do not disconnect when receiving VSAFE0V
    
    With some chargers, vbus might momentarily raise above VSAFE5V and fall
    back to 0V causing VSAFE0V to be triggered. This will
    will report a VBUS off event causing TCPM to transition to
    SNK_UNATTACHED state where it should be waiting in either SNK_ATTACH_WAIT
    or SNK_DEBOUNCED state. This patch makes TCPM avoid VSAFE0V events
    while in SNK_ATTACH_WAIT or SNK_DEBOUNCED state.
    
    Stub from the spec:
        "4.5.2.2.4.2 Exiting from AttachWait.SNK State
        A Sink shall transition to Unattached.SNK when the state of both
        the CC1 and CC2 pins is SNK.Open for at least tPDDebounce.
        A DRP shall transition to Unattached.SRC when the state of both
        the CC1 and CC2 pins is SNK.Open for at least tPDDebounce."
    
    [23.194131] CC1: 0 -> 0, CC2: 0 -> 5 [state SNK_UNATTACHED, polarity 0, connected]
    [23.201777] state change SNK_UNATTACHED -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
    [23.209949] pending state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED @ 170 ms [rev3 NONE_AMS]
    [23.300579] VBUS off
    [23.300668] state change SNK_ATTACH_WAIT -> SNK_UNATTACHED [rev3 NONE_AMS]
    [23.301014] VBUS VSAFE0V
    [23.301111] Start toggling
    
    Fixes: 28b43d3d746b8 ("usb: typec: tcpm: Introduce vsafe0v for vbus")
    Cc: stable@vger.kernel.org
    Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
    Link: https://lore.kernel.org/r/20220122015520.332507-2-badhri@google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 90b8aa9f5b09edae6928c0561f933fec9f7a9987
Author: Badhri Jagan Sridharan <badhri@google.com>
Date:   Fri Jan 21 17:55:19 2022 -0800

    usb: typec: tcpm: Do not disconnect while receiving VBUS off
    
    With some chargers, vbus might momentarily raise above VSAFE5V and fall
    back to 0V before tcpm gets to read port->tcpc->get_vbus. This will
    will report a VBUS off event causing TCPM to transition to
    SNK_UNATTACHED where it should be waiting in either SNK_ATTACH_WAIT
    or SNK_DEBOUNCED state. This patch makes TCPM avoid vbus off events
    while in SNK_ATTACH_WAIT or SNK_DEBOUNCED state.
    
    Stub from the spec:
        "4.5.2.2.4.2 Exiting from AttachWait.SNK State
        A Sink shall transition to Unattached.SNK when the state of both
        the CC1 and CC2 pins is SNK.Open for at least tPDDebounce.
        A DRP shall transition to Unattached.SRC when the state of both
        the CC1 and CC2 pins is SNK.Open for at least tPDDebounce."
    
    [23.194131] CC1: 0 -> 0, CC2: 0 -> 5 [state SNK_UNATTACHED, polarity 0, connected]
    [23.201777] state change SNK_UNATTACHED -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
    [23.209949] pending state change SNK_ATTACH_WAIT -> SNK_DEBOUNCED @ 170 ms [rev3 NONE_AMS]
    [23.300579] VBUS off
    [23.300668] state change SNK_ATTACH_WAIT -> SNK_UNATTACHED [rev3 NONE_AMS]
    [23.301014] VBUS VSAFE0V
    [23.301111] Start toggling
    
    Fixes: f0690a25a140b8 ("staging: typec: USB Type-C Port Manager (tcpm)")
    Cc: stable@vger.kernel.org
    Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
    Link: https://lore.kernel.org/r/20220122015520.332507-1-badhri@google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e464121f2d40eabc7d11823fb26db807ce945df4
Author: Tony Luck <tony.luck@intel.com>
Date:   Fri Jan 21 09:47:38 2022 -0800

    x86/cpu: Add Xeon Icelake-D to list of CPUs that support PPIN
    
    Missed adding the Icelake-D CPU to the list. It uses the same MSRs
    to control and read the inventory number as all the other models.
    
    Fixes: dc6b025de95b ("x86/mce: Add Xeon Icelake to list of CPUs that support PPIN")
    Reported-by: Ailin Xu <ailin.xu@intel.com>
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220121174743.1875294-2-tony.luck@intel.com

commit 147ab5376f18045da9f22a8262185707745bbf77
Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Date:   Mon Jan 24 12:02:28 2022 +0300

    usb: typec: Don't try to register component master without components
    
    This fixes NULL pointer dereference that happens if
    component master is registered with empty component match
    list.
    
    Fixes: 730b49aac426 ("usb: typec: port-mapper: Convert to the component framework")
    Reported-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
    Tested-by: John Stultz <john.stultz@linaro.org>
    Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Link: https://lore.kernel.org/r/20220124090228.41396-3-heikki.krogerus@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 7817adb03cfb52ebb5bdb25fd9fc8f683a1a09d9
Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Date:   Mon Jan 24 12:02:27 2022 +0300

    usb: typec: Only attempt to link USB ports if there is fwnode
    
    The code that creates the links to the USB ports attached to
    a connector inside the system assumed that the ACPI nodes
    (fwnodes) always exist for the connectors, but it can not do
    that.
    
    There is no guarantee that every USB Type-C connector has
    ACPI device node representing it in the ACPI tables, and
    even if there are the nodes in the ACPI tables, the _STA
    method in those nodes may still return 0 (which means the
    device does not exist from ACPI PoW).
    
    This fixes NULL pointer dereference that happens if the
    nodes are missing.
    
    Fixes: 730b49aac426 ("usb: typec: port-mapper: Convert to the component framework")
    Reported-and-tested-by: Robert Święcki <robert@swiecki.net>
    Reported-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
    Tested-by: Marc Zyngier <maz@kernel.org>
    Acked-by: Marc Zyngier <maz@kernel.org>
    Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Link: https://lore.kernel.org/r/20220124090228.41396-2-heikki.krogerus@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 5638b0dfb6921f69943c705383ff40fb64b987f2
Author: Xu Yang <xu.yang_2@nxp.com>
Date:   Thu Jan 13 17:29:43 2022 +0800

    usb: typec: tcpci: don't touch CC line if it's Vconn source
    
    With the AMS and Collision Avoidance, tcpm often needs to change the CC's
    termination. When one CC line is sourcing Vconn, if we still change its
    termination, the voltage of the another CC line is likely to be fluctuant
    and unstable.
    
    Therefore, we should verify whether a CC line is sourcing Vconn before
    changing its termination and only change the termination that is not
    a Vconn line. This can be done by reading the Vconn Present bit of
    POWER_ STATUS register. To determine the polarity, we can read the
    Plug Orientation bit of TCPC_CONTROL register. Since Vconn can only be
    sourced if Plug Orientation is set.
    
    Fixes: 0908c5aca31e ("usb: typec: tcpm: AMS and Collision Avoidance")
    cc: <stable@vger.kernel.org>
    Reviewed-by: Guenter Roeck <linux@roeck-us.net>
    Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
    Link: https://lore.kernel.org/r/20220113092943.752372-1-xu.yang_2@nxp.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 33569ef3c754a82010f266b7b938a66a3ccf90a4
Author: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
Date:   Wed Jan 19 11:47:51 2022 +0100

    PM: hibernate: Remove register_nosave_region_late()
    
    It is an unused wrapper forcing kmalloc allocation for registering
    nosave regions. Also, rename __register_nosave_region() to
    register_nosave_region() now that there is no need for disambiguation.
    
    Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
    Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 945c37ed564770c78dfe6b9f08bed57a1b4e60ef
Author: Linyu Yuan <quic_linyyuan@quicinc.com>
Date:   Mon Jan 10 20:43:28 2022 +0800

    usb: roles: fix include/linux/usb/role.h compile issue
    
    when CONFIG_USB_ROLE_SWITCH is not defined,
    add usb_role_switch_find_by_fwnode() definition which return NULL.
    
    Fixes: c6919d5e0cd1 ("usb: roles: Add usb_role_switch_find_by_fwnode()")
    Signed-off-by: Linyu Yuan <quic_linyyuan@quicinc.com>
    Link: https://lore.kernel.org/r/1641818608-25039-1-git-send-email-quic_linyyuan@quicinc.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit c9d967b2ce40d71e968eb839f36c936b8a9cf1ea
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 13 19:44:20 2022 +0100

    PM: wakeup: simplify the output logic of pm_show_wakelocks()
    
    The buffer handling in pm_show_wakelocks() is tricky, and hopefully
    correct.  Ensure it really is correct by using sysfs_emit_at() which
    handles all of the tricky string handling logic in a PAGE_SIZE buffer
    for us automatically as this is a sysfs file being read from.
    
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Lee Jones <lee.jones@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 8bdd24940b69c0018b64b496aa3b03a25f7295ca
Author: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date:   Tue Jan 25 15:40:06 2022 +0100

    amd: declance: use eth_hw_addr_set()
    
    Copy scattered mac address octets into an array then eth_hw_addr_set().
    
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Link: https://lore.kernel.org/r/20220125144007.64407-1-tsbogend@alpha.franken.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6aa89ae1fb049614b7e03e24485bbfb96754a02b
Author: Rob Clark <robdclark@chromium.org>
Date:   Sat Jan 8 10:09:11 2022 -0800

    drm/msm/gpu: Cancel idle/boost work on suspend
    
    With system suspend using pm_runtime_force_suspend() we can't rely on
    the pm_runtime_get_if_in_use() trick to deal with devfreq callbacks
    after (or racing with) suspend.  So flush any pending idle or boost
    work in the suspend path.
    
    Signed-off-by: Rob Clark <robdclark@chromium.org>
    Link: https://lore.kernel.org/r/20220108180913.814448-3-robdclark@gmail.com
    Signed-off-by: Rob Clark <robdclark@chromium.org>

commit 167a668ab0edf92bfd043bafd24e7f895d074173
Author: Rob Clark <robdclark@chromium.org>
Date:   Sat Jan 8 10:09:10 2022 -0800

    drm/msm/gpu: Wait for idle before suspending
    
    System suspend uses pm_runtime_force_suspend(), which cheekily bypasses
    the runpm reference counts.  This doesn't actually work so well when the
    GPU is active.  So add a reasonable delay waiting for the GPU to become
    idle.
    
    Alternatively we could just return -EBUSY in this case, but that has the
    disadvantage of causing system suspend to fail.
    
    v2: s/ret/remaining [sboyd], and switch to using active_submits count
        to ensure we aren't racing with submit cleanup (and devfreq idle
        work getting scheduled, etc)
    v3: fix inverted logic
    
    Signed-off-by: Rob Clark <robdclark@chromium.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Link: https://lore.kernel.org/r/20220108180913.814448-2-robdclark@gmail.com
    Signed-off-by: Rob Clark <robdclark@chromium.org>

commit 49d766f3a0e49624c4cf83909d56c68164e7c545
Merge: a08b41ab9e2e4 27cdfde181bca
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 25 18:29:10 2022 +0200

    Merge tag 'for-5.17-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs fixes from David Sterba:
     "Several fixes for defragmentation that got broken in 5.16 after
      refactoring and added subpage support. The observed bugs are excessive
      IO or uninterruptible ioctl.
    
      All stable material"
    
    * tag 'for-5.17-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux:
      btrfs: update writeback index when starting defrag
      btrfs: add back missing dirty page rate limiting to defrag
      btrfs: fix deadlock when reserving space during defrag
      btrfs: defrag: properly update range->start for autodefrag
      btrfs: defrag: fix wrong number of defragged sectors
      btrfs: allow defrag to be interruptible
      btrfs: fix too long loop when defragging a 1 byte file

commit 426aca16e903b387a0b0001d62207a745c67cfd3
Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date:   Tue Jan 18 19:13:37 2022 +0100

    staging: fbtft: Fix error path in fbtft_driver_module_init()
    
    If registering the platform driver fails, the function must not return
    without undoing the spi driver registration first.
    
    Fixes: c296d5f9957c ("staging: fbtft: core support")
    Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Link: https://lore.kernel.org/r/20220118181338.207943-1-u.kleine-koenig@pengutronix.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 0cea730cac824edf78ffd3302938ed5fe2b9d50d
Author: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>
Date:   Fri Dec 31 20:54:03 2021 +0100

    staging: vc04_services: Fix RCU dereference check
    
    In service_callback path RCU dereferenced pointer struct vchiq_service
    need to be accessed inside rcu read-critical section.
    
    Also userdata/user_service part of vchiq_service is accessed around
    different synchronization mechanism, getting an extra reference to a
    pointer keeps sematics simpler and avoids prolonged graceperiod.
    
    Accessing vchiq_service with rcu_read_[lock/unlock] fixes below issue.
    
    [   32.201659] =============================
    [   32.201664] WARNING: suspicious RCU usage
    [   32.201670] 5.15.11-rt24-v8+ #3 Not tainted
    [   32.201680] -----------------------------
    [   32.201685] drivers/staging/vc04_services/interface/vchiq_arm/vchiq_core.h:529 suspicious rcu_dereference_check() usage!
    [   32.201695]
    [   32.201695] other info that might help us debug this:
    [   32.201695]
    [   32.201700]
    [   32.201700] rcu_scheduler_active = 2, debug_locks = 1
    [   32.201708] no locks held by vchiq-slot/0/98.
    [   32.201715]
    [   32.201715] stack backtrace:
    [   32.201723] CPU: 1 PID: 98 Comm: vchiq-slot/0 Not tainted 5.15.11-rt24-v8+ #3
    [   32.201733] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
    [   32.201739] Call trace:
    [   32.201742]  dump_backtrace+0x0/0x1b8
    [   32.201772]  show_stack+0x20/0x30
    [   32.201784]  dump_stack_lvl+0x8c/0xb8
    [   32.201799]  dump_stack+0x18/0x34
    [   32.201808]  lockdep_rcu_suspicious+0xe4/0xf8
    [   32.201817]  service_callback+0x124/0x400
    [   32.201830]  slot_handler_func+0xf60/0x1e20
    [   32.201839]  kthread+0x19c/0x1a8
    [   32.201849]  ret_from_fork+0x10/0x20
    
    Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>
    Link: https://lore.kernel.org/r/20211231195406.5479-1-treasure4paddy@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d081a343dd18f6733f2f4d9a2521db92de9f7b75
Author: Quanfa Fu <quanfafu@gmail.com>
Date:   Sun Dec 19 17:14:46 2021 +0800

    KVM/X86: Make kvm_vcpu_reload_apic_access_page() static
    
    Make kvm_vcpu_reload_apic_access_page() static
    as it is no longer invoked directly by vmx
    and it is also no longer exported.
    
    No functional change intended.
    
    Signed-off-by: Quanfa Fu <quanfafu@gmail.com>
    Message-Id: <20211219091446.174584-1-quanfafu@gmail.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit de1956f48543e90f94b1194395f33140898b39b2
Author: David Matlack <dmatlack@google.com>
Date:   Thu Jan 20 00:38:26 2022 +0000

    KVM: selftests: Re-enable access_tracking_perf_test
    
    This selftest was accidentally removed by commit 6a58150859fd
    ("selftest: KVM: Add intra host migration tests"). Add it back.
    
    Fixes: 6a58150859fd ("selftest: KVM: Add intra host migration tests")
    Signed-off-by: David Matlack <dmatlack@google.com>
    Message-Id: <20220120003826.2805036-1-dmatlack@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b9bed78e2fa9571b7c983b20666efa0009030c71
Author: Sean Christopherson <seanjc@google.com>
Date:   Thu Jan 20 00:06:24 2022 +0000

    KVM: VMX: Set vmcs.PENDING_DBG.BS on #DB in STI/MOVSS blocking shadow
    
    Set vmcs.GUEST_PENDING_DBG_EXCEPTIONS.BS, a.k.a. the pending single-step
    breakpoint flag, when re-injecting a #DB with RFLAGS.TF=1, and STI or
    MOVSS blocking is active.  Setting the flag is necessary to make VM-Entry
    consistency checks happy, as VMX has an invariant that if RFLAGS.TF is
    set and STI/MOVSS blocking is true, then the previous instruction must
    have been STI or MOV/POP, and therefore a single-step #DB must be pending
    since the RFLAGS.TF cannot have been set by the previous instruction,
    i.e. the one instruction delay after setting RFLAGS.TF must have already
    expired.
    
    Normally, the CPU sets vmcs.GUEST_PENDING_DBG_EXCEPTIONS.BS appropriately
    when recording guest state as part of a VM-Exit, but #DB VM-Exits
    intentionally do not treat the #DB as "guest state" as interception of
    the #DB effectively makes the #DB host-owned, thus KVM needs to manually
    set PENDING_DBG.BS when forwarding/re-injecting the #DB to the guest.
    
    Note, although this bug can be triggered by guest userspace, doing so
    requires IOPL=3, and guest userspace running with IOPL=3 has full access
    to all I/O ports (from the guest's perspective) and can crash/reboot the
    guest any number of ways.  IOPL=3 is required because STI blocking kicks
    in if and only if RFLAGS.IF is toggled 0=>1, and if CPL>IOPL, STI either
    takes a #GP or modifies RFLAGS.VIF, not RFLAGS.IF.
    
    MOVSS blocking can be initiated by userspace, but can be coincident with
    a #DB if and only if DR7.GD=1 (General Detect enabled) and a MOV DR is
    executed in the MOVSS shadow.  MOV DR #GPs at CPL>0, thus MOVSS blocking
    is problematic only for CPL0 (and only if the guest is crazy enough to
    access a DR in a MOVSS shadow).  All other sources of #DBs are either
    suppressed by MOVSS blocking (single-step, code fetch, data, and I/O),
    are mutually exclusive with MOVSS blocking (T-bit task switch), or are
    already handled by KVM (ICEBP, a.k.a. INT1).
    
    This bug was originally found by running tests[1] created for XSA-308[2].
    Note that Xen's userspace test emits ICEBP in the MOVSS shadow, which is
    presumably why the Xen bug was deemed to be an exploitable DOS from guest
    userspace.  KVM already handles ICEBP by skipping the ICEBP instruction
    and thus clears MOVSS blocking as a side effect of its "emulation".
    
    [1] http://xenbits.xenproject.org/docs/xtf/xsa-308_2main_8c_source.html
    [2] https://xenbits.xen.org/xsa/advisory-308.html
    
    Reported-by: David Woodhouse <dwmw2@infradead.org>
    Reported-by: Alexander Graf <graf@amazon.de>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220120000624.655815-1-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 5c89be1dd5cfb697614bc13626ba3bd0781aa160
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Jan 24 11:36:05 2022 +0100

    KVM: x86: Move CPUID.(EAX=0x12,ECX=1) mangling to __kvm_update_cpuid_runtime()
    
    Full equality check of CPUID data on update (kvm_cpuid_check_equal()) may
    fail for SGX enabled CPUs as CPUID.(EAX=0x12,ECX=1) is currently being
    mangled in kvm_vcpu_after_set_cpuid(). Move it to
    __kvm_update_cpuid_runtime() and split off cpuid_get_supported_xcr0()
    helper  as 'vcpu->arch.guest_supported_xcr0' update needs (logically)
    to stay in kvm_vcpu_after_set_cpuid().
    
    Cc: stable@vger.kernel.org
    Fixes: feb627e8d6f6 ("KVM: x86: Forbid KVM_SET_CPUID{,2} after KVM_RUN")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220124103606.2630588-2-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2f61353cd2f789a4229b6f5c1c24a40a613357bb
Author: Yufeng Mo <moyufeng@huawei.com>
Date:   Tue Jan 25 15:03:12 2022 +0800

    net: hns3: handle empty unknown interrupt for VF
    
    Since some interrupt states may be cleared by hardware, the driver
    may receive an empty interrupt. Currently, the VF driver directly
    disables the vector0 interrupt in this case. As a result, the VF
    is unavailable. Therefore, the vector0 interrupt should be enabled
    in this case.
    
    Fixes: b90fcc5bd904 ("net: hns3: add reset handling for VF when doing Core/Global/IMP reset")
    Signed-off-by: Yufeng Mo <moyufeng@huawei.com>
    Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 74afa30630976861a1308c5ec93391f8b037a2ae
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Mon Jan 24 09:22:49 2022 -0800

    net: fec_mpc52xx: don't discard const from netdev->dev_addr
    
    Recent changes made netdev->dev_addr const, and it's passed
    directly to mpc52xx_fec_set_paddr().
    
    Similar problem exists on the probe patch, the driver needs
    to call eth_hw_addr_set().
    
    Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Fixes: adeef3e32146 ("net: constify netdev->dev_addr")
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c63003e3d99761afb280add3b30de1cf30fa522b
Author: Toke Høiland-Jørgensen <toke@redhat.com>
Date:   Mon Jan 24 15:35:29 2022 +0100

    net: cpsw: Properly initialise struct page_pool_params
    
    The cpsw driver didn't properly initialise the struct page_pool_params
    before calling page_pool_create(), which leads to crashes after the struct
    has been expanded with new parameters.
    
    The second Fixes tag below is where the buggy code was introduced, but
    because the code was moved around this patch will only apply on top of the
    commit in the first Fixes tag.
    
    Fixes: c5013ac1dd0e ("net: ethernet: ti: cpsw: move set of common functions in cpsw_priv")
    Fixes: 9ed4050c0d75 ("net: ethernet: ti: cpsw: add XDP support")
    Reported-by: Colin Foster <colin.foster@in-advantage.com>
    Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Tested-by: Colin Foster <colin.foster@in-advantage.com>
    Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 29eb31542787e1019208a2e1047bb7c76c069536
Author: Hangyu Hua <hbh25y@gmail.com>
Date:   Mon Jan 24 11:29:54 2022 +0800

    yam: fix a memory leak in yam_siocdevprivate()
    
    ym needs to be free when ym->cmd != SIOCYAMSMCS.
    
    Fixes: 0781168e23a2 ("yam: fix a missing-check bug")
    Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c74ead223deb88bdf18af8c772d7ca5a9b6c3c2b
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Sun Jan 23 23:54:58 2022 +0800

    net: stmmac: reduce unnecessary wakeups from eee sw timer
    
    Currently, on EEE capable platforms, if EEE SW timer is used, the SW
    timer cause 1 wakeup/s even if the TX has successfully entered EEE.
    Remove this unnecessary wakeup by only calling mod_timer() if we
    haven't successfully entered EEE.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4cf28e9ae6e2e11a044be1bcbcfa1b0d8675fe4d
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 24 15:32:53 2022 +0000

    ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
    
    We don't currently validate that the values being set are within the range
    we advertised to userspace as being valid, do so and reject any values
    that are out of range.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220124153253.3548853-4-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4f1e50d6a9cf9c1b8c859d449b5031cacfa8404e
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 24 15:32:52 2022 +0000

    ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
    
    We don't currently validate that the values being set are within the range
    we advertised to userspace as being valid, do so and reject any values
    that are out of range.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220124153253.3548853-3-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 817f7c9335ec01e0f5e8caffc4f1dcd5e458a4c0
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 24 15:32:51 2022 +0000

    ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
    
    We don't currently validate that the values being set are within the range
    we advertised to userspace as being valid, do so and reject any values
    that are out of range.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220124153253.3548853-2-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3e3765875b1b8864898603768fd5c93eeb552211
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 21 14:55:05 2022 +0300

    mtd: phram: Prevent divide by zero bug in phram_setup()
    
    The problem is that "erasesize" is a uint64_t type so it might be
    non-zero but the lower 32 bits are zero so when it's truncated,
    "(uint32_t)erasesize", then that value is zero. This leads to a
    divide by zero bug.
    
    Avoid the bug by delaying the divide until after we have validated
    that "erasesize" is non-zero and within the uint32_t range.
    
    Fixes: dc2b3e5cbc80 ("mtd: phram: use div_u64_rem to stop overwrite len in phram_setup")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220121115505.GI1978@kadam

commit 4cd335dae3cf25412427938d8abbaf04d46e63b5
Author: Roger Quadros <rogerq@kernel.org>
Date:   Tue Jan 18 14:35:25 2022 +0200

    mtd: rawnand: omap2: Prevent invalid configuration and build error
    
    We need to select MEMORY as well otherwise OMAP_GPMC will not be built.
    For simplicity let's select MEMORY and OMAP_GPMC unconditionally as
    this driver depends on OMAP_GPMC driver and uses symbols from there.
    
    Fixes: dbcb124acebd ("mtd: rawnand: omap2: Select GPMC device driver for ARCH_K3")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Roger Quadros <rogerq@kernel.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220118123525.8020-1-rogerq@kernel.org

commit 3dd8ba961b9356c4113b96541c752c73d98fef70
Author: Ansuel Smith <ansuelsmth@gmail.com>
Date:   Sun Jan 16 04:22:11 2022 +0100

    mtd: parsers: qcom: Fix missing free for pparts in cleanup
    
    Mtdpart doesn't free pparts when a cleanup function is declared.
    Add missing free for pparts in cleanup function for smem to fix the
    leak.
    
    Fixes: 10f3b4d79958 ("mtd: parsers: qcom: Fix leaking of partition name")
    Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220116032211.9728-2-ansuelsmth@gmail.com

commit 65d003cca335cabc0160d3cd7daa689eaa9dd3cd
Author: Ansuel Smith <ansuelsmth@gmail.com>
Date:   Sun Jan 16 04:22:10 2022 +0100

    mtd: parsers: qcom: Fix kernel panic on skipped partition
    
    In the event of a skipped partition (case when the entry name is empty)
    the kernel panics in the cleanup function as the name entry is NULL.
    Rework the parser logic by first checking the real partition number and
    then allocate the space and set the data for the valid partitions.
    
    The logic was also fundamentally wrong as with a skipped partition, the
    parts number returned was incorrect by not decreasing it for the skipped
    partitions.
    
    Fixes: 803eb124e1a6 ("mtd: parsers: Add Qcom SMEM parser")
    Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220116032211.9728-1-ansuelsmth@gmail.com

commit 079e6bdb2b1cc1da8b5c602229db782732668ae7
Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Date:   Mon Jan 3 03:03:16 2022 +0000

    mtd: parsers: qcom: Don't print error message on -EPROBE_DEFER
    
    Its possible for the main smem driver to not be loaded by the time we come
    along to parse the smem partition description but, this is a perfectly
    normal thing.
    
    No need to print out an error message in this case.
    
    Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
    Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220103030316.58301-3-bryan.odonoghue@linaro.org

commit 5c23b3f965bc9ee696bf2ed4bdc54d339dd9a455
Author: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Date:   Mon Jan 3 03:03:15 2022 +0000

    mtd: rawnand: qcom: Fix clock sequencing in qcom_nandc_probe()
    
    Interacting with a NAND chip on an IPQ6018 I found that the qcomsmem NAND
    partition parser was returning -EPROBE_DEFER waiting for the main smem
    driver to load.
    
    This caused the board to reset. Playing about with the probe() function
    shows that the problem lies in the core clock being switched off before the
    nandc_unalloc() routine has completed.
    
    If we look at how qcom_nandc_remove() tears down allocated resources we see
    the expected order is
    
    qcom_nandc_unalloc(nandc);
    
    clk_disable_unprepare(nandc->aon_clk);
    clk_disable_unprepare(nandc->core_clk);
    
    dma_unmap_resource(&pdev->dev, nandc->base_dma, resource_size(res),
                       DMA_BIDIRECTIONAL, 0);
    
    Tweaking probe() to both bring up and tear-down in that order removes the
    reset if we end up deferring elsewhere.
    
    Fixes: c76b78d8ec05 ("mtd: nand: Qualcomm NAND controller driver")
    Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
    Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20220103030316.58301-2-bryan.odonoghue@linaro.org

commit ba1b71b008e97fd747845ff3a818420b11bbe830
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Dec 30 07:27:51 2021 +0000

    mtd: rawnand: ingenic: Fix missing put_device in ingenic_ecc_get
    
    If of_find_device_by_node() succeeds, ingenic_ecc_get() doesn't have
    a corresponding put_device(). Thus add put_device() to fix the exception
    handling.
    
    Fixes: 15de8c6efd0e ("mtd: rawnand: ingenic: Separate top-level and SoC specific code")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Paul Cercueil <paul@crapouillou.net>
    Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
    Link: https://lore.kernel.org/linux-mtd/20211230072751.21622-1-linmq006@gmail.com

commit a08b41ab9e2e468647f78eb17c28e29b93006394
Merge: dd81e1c7d5fb1 9f80ccda53b94
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 25 08:02:46 2022 +0200

    Merge tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm
    
    Pull ARM fixes from Russell King:
    
     - Fix panic whe both KASAN and KPROBEs are enabled
    
     - Avoid alignment faults in copy_*_kernel_nofault()
    
     - Align SMP alternatives in modules
    
    * tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm:
      ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
      ARM: 9179/1: uaccess: avoid alignment faults in copy_[from|to]_kernel_nofault
      ARM: 9170/1: fix panic when kasan and kprobe are enabled

commit 8defc2a5dd8f4c0cb19ecbaca8d3e89ab98524da
Author: Nicholas Piggin <npiggin@gmail.com>
Date:   Tue Jan 25 00:39:28 2022 +1000

    powerpc/64s/interrupt: Fix decrementer storm
    
    The decrementer exception can fail to be cleared when the interrupt
    returns in the case where the decrementer wraps with the next timer
    still beyond decrementer_max. This results in a decrementer interrupt
    storm. This is triggerable with small decrementer system with hard
    and soft watchdogs disabled.
    
    Fix this by always programming the decrementer if there was no timer.
    
    Fixes: 0faf20a1ad16 ("powerpc/64s/interrupt: Don't enable MSR[EE] in irq handlers unless perf is in use")
    Reported-by: Alexey Kardashevskiy <aik@ozlabs.ru>
    Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220124143930.3923442-1-npiggin@gmail.com

commit 22f7ff0dea9491e90b6fe808ed40c30bd791e5c2
Author: Nicholas Piggin <npiggin@gmail.com>
Date:   Sat Jan 22 20:55:30 2022 +1000

    KVM: PPC: Book3S HV Nested: Fix nested HFSCR being clobbered with multiple vCPUs
    
    The L0 is storing HFSCR requested by the L1 for the L2 in struct
    kvm_nested_guest when the L1 requests a vCPU enter L2. kvm_nested_guest
    is not a per-vCPU structure. Hilarity ensues.
    
    Fix it by moving the nested hfscr into the vCPU structure together with
    the other per-vCPU nested fields.
    
    Fixes: 8b210a880b35 ("KVM: PPC: Book3S HV Nested: Make nested HFSCR state accessible")
    Cc: stable@vger.kernel.org # v5.15+
    Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
    Reviewed-by: Fabiano Rosas <farosas@linux.ibm.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220122105530.3477250-1-npiggin@gmail.com

commit 5ec1cebd59300ddd26dbaa96c17c508764eef911
Author: Manasi Navare <manasi.d.navare@intel.com>
Date:   Mon Oct 4 04:59:13 2021 -0700

    drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
    
    In case of a modeset where a mode gets split across multiple CRTCs
    in the driver specific implementation (bigjoiner in i915) we wrongly count
    the affected CRTCs based on the drm_crtc_mask and indicate the stolen CRTC as
    an affected CRTC in atomic_check_only().
    This triggers a warning since affected CRTCs doent match requested CRTC.
    
    To fix this in such bigjoiner configurations, we should only
    increment affected crtcs if that CRTC is enabled in UAPI not
    if it is just used internally in the driver to split the mode.
    
    v3: Add the same uapi crtc_state->enable check in requested
    crtc calc (Ville)
    
    Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Cc: Simon Ser <contact@emersion.fr>
    Cc: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
    Cc: Daniel Stone <daniels@collabora.com>
    Cc: Daniel Vetter <daniel.vetter@intel.com>
    Cc: dri-devel@lists.freedesktop.org
    Cc: <stable@vger.kernel.org> # v5.11+
    Fixes: 919c2299a893 ("drm/i915: Enable bigjoiner")
    Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
    Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20211004115913.23889-1-manasi.d.navare@intel.com

commit 4db09593af0b0b4d7d4805ebb3273df51d7cc30d
Author: Tong Zhang <ztong0001@gmail.com>
Date:   Sun Jan 23 14:57:17 2022 -0800

    scsi: myrs: Fix crash in error case
    
    In myrs_detect(), cs->disable_intr is NULL when privdata->hw_init() fails
    with non-zero. In this case, myrs_cleanup(cs) will call a NULL ptr and
    crash the kernel.
    
    [    1.105606] myrs 0000:00:03.0: Unknown Initialization Error 5A
    [    1.105872] myrs 0000:00:03.0: Failed to initialize Controller
    [    1.106082] BUG: kernel NULL pointer dereference, address: 0000000000000000
    [    1.110774] Call Trace:
    [    1.110950]  myrs_cleanup+0xe4/0x150 [myrs]
    [    1.111135]  myrs_probe.cold+0x91/0x56a [myrs]
    [    1.111302]  ? DAC960_GEM_intr_handler+0x1f0/0x1f0 [myrs]
    [    1.111500]  local_pci_probe+0x48/0x90
    
    Link: https://lore.kernel.org/r/20220123225717.1069538-1-ztong0001@gmail.com
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Signed-off-by: Tong Zhang <ztong0001@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit efd7bb1d75cf6808d67c869a29245c88a990bdea
Author: Colin Ian King <colin.king@intel.com>
Date:   Sun Jan 23 17:55:30 2022 +0000

    scsi: 53c700: Remove redundant assignment to pointer SCp
    
    Pointer SCp is being re-assigned the same value that it was initialized to
    a few lines earlier, the assignment is redundant and can be removed.
    
    Link: https://lore.kernel.org/r/20220123175530.110462-1-colin.i.king@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit c99b9b2301492b665b6e51ba6c06ec362eddcd10
Author: Kiwoong Kim <kwmad.kim@samsung.com>
Date:   Fri Jan 21 14:37:55 2022 +0900

    scsi: ufs: Treat link loss as fatal error
    
    This event is raised when link is lost as specified in UFSHCI spec and that
    means communication is not possible. Thus initializing UFS interface needs
    to be done.
    
    Make UFS driver considers Link Lost as fatal in the INT_FATAL_ERRORS
    mask. This will trigger a host reset whenever a link lost interrupt occurs.
    
    Link: https://lore.kernel.org/r/1642743475-54275-1-git-send-email-kwmad.kim@samsung.com
    Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit ad6c8a426446873febc98140d81d5353f8c0825b
Author: Kiwoong Kim <kwmad.kim@samsung.com>
Date:   Fri Jan 21 14:33:02 2022 +0900

    scsi: ufs: Use generic error code in ufshcd_set_dev_pwr_mode()
    
    The return value of ufshcd_set_dev_pwr_mode() is passed to device PM
    core. However, the function currently returns a SCSI result which the PM
    core doesn't understand.  This might lead to unexpected behaviors in
    userland; a platform reset was observed in Android.
    
    Use a generic error code for SSU failures.
    
    Link: https://lore.kernel.org/r/1642743182-54098-1-git-send-email-kwmad.kim@samsung.com
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 012d98dae453821ac31da25595ffa26d4ad49c8c
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 15 10:15:41 2022 +0100

    scsi: bfa: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL. So, if it fails, the 32-bit case will also fail
    for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lore.kernel.org/linux-kernel/YL3vSPK5DXTNvgdx@infradead.org/#t
    
    Link: https://lore.kernel.org/r/5663cef9b54004fa56cca7ce65f51eadfc3ecddb.1642238127.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 8001fa240fc0af1c3538a9fbaccd2c345ff9ab62
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 15 10:05:22 2022 +0100

    scsi: hisi_sas: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL. So, if it fails, the 32-bit case will also fail
    for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lore.kernel.org/linux-kernel/YL3vSPK5DXTNvgdx@infradead.org/#t
    
    Link: https://lore.kernel.org/r/1bf2d3660178b0e6f172e5208bc0bd68d31d9268.1642237482.git.christophe.jaillet@wanadoo.fr
    Acked-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit fb8d5ea8fd907faa3751a9e5df5d01b5f3803e35
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 15 09:53:03 2022 +0100

    scsi: 3w-sas: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL. So, if it fails, the 32-bit case will also fail
    for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lore.kernel.org/linux-kernel/YL3vSPK5DXTNvgdx@infradead.org/#t
    
    Link: https://lore.kernel.org/r/dbbe8671ca760972d80f8d35f3170b4609bee368.1642236763.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 847f9ea4c5186fdb7b84297e3eeed9e340e83fce
Author: John Meneghini <jmeneghi@redhat.com>
Date:   Fri Jan 14 23:00:44 2022 -0500

    scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put()
    
    The bnx2fc_destroy() functions are removing the interface before calling
    destroy_work. This results multiple WARNings from sysfs_remove_group() as
    the controller rport device attributes are removed too early.
    
    Replace the fcoe_port's destroy_work queue. It's not needed.
    
    The problem is easily reproducible with the following steps.
    
    Example:
    
      $ dmesg -w &
      $ systemctl enable --now fcoe
      $ fipvlan -s -c ens2f1
      $ fcoeadm -d ens2f1.802
      [  583.464488] host2: libfc: Link down on port (7500a1)
      [  583.472651] bnx2fc: 7500a1 - rport not created Yet!!
      [  583.490468] ------------[ cut here ]------------
      [  583.538725] sysfs group 'power' not found for kobject 'rport-2:0-0'
      [  583.568814] WARNING: CPU: 3 PID: 192 at fs/sysfs/group.c:279 sysfs_remove_group+0x6f/0x80
      [  583.607130] Modules linked in: dm_service_time 8021q garp mrp stp llc bnx2fc cnic uio rpcsec_gss_krb5 auth_rpcgss nfsv4 ...
      [  583.942994] CPU: 3 PID: 192 Comm: kworker/3:2 Kdump: loaded Not tainted 5.14.0-39.el9.x86_64 #1
      [  583.984105] Hardware name: HP ProLiant DL120 G7, BIOS J01 07/01/2013
      [  584.016535] Workqueue: fc_wq_2 fc_rport_final_delete [scsi_transport_fc]
      [  584.050691] RIP: 0010:sysfs_remove_group+0x6f/0x80
      [  584.074725] Code: ff 5b 48 89 ef 5d 41 5c e9 ee c0 ff ff 48 89 ef e8 f6 b8 ff ff eb d1 49 8b 14 24 48 8b 33 48 c7 c7 ...
      [  584.162586] RSP: 0018:ffffb567c15afdc0 EFLAGS: 00010282
      [  584.188225] RAX: 0000000000000000 RBX: ffffffff8eec4220 RCX: 0000000000000000
      [  584.221053] RDX: ffff8c1586ce84c0 RSI: ffff8c1586cd7cc0 RDI: ffff8c1586cd7cc0
      [  584.255089] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb567c15afc00
      [  584.287954] R10: ffffb567c15afbf8 R11: ffffffff8fbe7f28 R12: ffff8c1486326400
      [  584.322356] R13: ffff8c1486326480 R14: ffff8c1483a4a000 R15: 0000000000000004
      [  584.355379] FS:  0000000000000000(0000) GS:ffff8c1586cc0000(0000) knlGS:0000000000000000
      [  584.394419] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      [  584.421123] CR2: 00007fe95a6f7840 CR3: 0000000107674002 CR4: 00000000000606e0
      [  584.454888] Call Trace:
      [  584.466108]  device_del+0xb2/0x3e0
      [  584.481701]  device_unregister+0x13/0x60
      [  584.501306]  bsg_unregister_queue+0x5b/0x80
      [  584.522029]  bsg_remove_queue+0x1c/0x40
      [  584.541884]  fc_rport_final_delete+0xf3/0x1d0 [scsi_transport_fc]
      [  584.573823]  process_one_work+0x1e3/0x3b0
      [  584.592396]  worker_thread+0x50/0x3b0
      [  584.609256]  ? rescuer_thread+0x370/0x370
      [  584.628877]  kthread+0x149/0x170
      [  584.643673]  ? set_kthread_struct+0x40/0x40
      [  584.662909]  ret_from_fork+0x22/0x30
      [  584.680002] ---[ end trace 53575ecefa942ece ]---
    
    Link: https://lore.kernel.org/r/20220115040044.1013475-1-jmeneghi@redhat.com
    Fixes: 0cbf32e1681d ("[SCSI] bnx2fc: Avoid calling bnx2fc_if_destroy with unnecessary locks")
    Tested-by: Guangwu Zhang <guazhang@redhat.com>
    Co-developed-by: Maurizio Lombardi <mlombard@redhat.com>
    Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
    Signed-off-by: John Meneghini <jmeneghi@redhat.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 8c9db6679be4348b8aae108e11d4be2f83976e30
Author: Steffen Maier <maier@linux.ibm.com>
Date:   Tue Jan 18 17:58:03 2022 +0100

    scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices
    
    Suppose we have an environment with a number of non-NPIV FCP devices
    (virtual HBAs / FCP devices / zfcp "adapter"s) sharing the same physical
    FCP channel (HBA port) and its I_T nexus. Plus a number of storage target
    ports zoned to such shared channel. Now one target port logs out of the
    fabric causing an RSCN. Zfcp reacts with an ADISC ELS and subsequent port
    recovery depending on the ADISC result. This happens on all such FCP
    devices (in different Linux images) concurrently as they all receive a copy
    of this RSCN. In the following we look at one of those FCP devices.
    
    Requests other than FSF_QTCB_FCP_CMND can be slow until they get a
    response.
    
    Depending on which requests are affected by slow responses, there are
    different recovery outcomes. Here we want to fix failed recoveries on port
    or adapter level by avoiding recovery requests that can be slow.
    
    We need the cached N_Port_ID for the remote port "link" test with ADISC.
    Just before sending the ADISC, we now intentionally forget the old cached
    N_Port_ID. The idea is that on receiving an RSCN for a port, we have to
    assume that any cached information about this port is stale.  This forces a
    fresh new GID_PN [FC-GS] nameserver lookup on any subsequent recovery for
    the same port. Since we typically can still communicate with the nameserver
    efficiently, we now reach steady state quicker: Either the nameserver still
    does not know about the port so we stop recovery, or the nameserver already
    knows the port potentially with a new N_Port_ID and we can successfully and
    quickly perform open port recovery.  For the one case, where ADISC returns
    successfully, we re-initialize port->d_id because that case does not
    involve any port recovery.
    
    This also solves a problem if the storage WWPN quickly logs into the fabric
    again but with a different N_Port_ID. Such as on virtual WWPN takeover
    during target NPIV failover.
    [https://www.redbooks.ibm.com/abstracts/redp5477.html] In that case the
    RSCN from the storage FDISC was ignored by zfcp and we could not
    successfully recover the failover. On some later failback on the storage,
    we could have been lucky if the virtual WWPN got the same old N_Port_ID
    from the SAN switch as we still had cached.  Then the related RSCN
    triggered a successful port reopen recovery.  However, there is no
    guarantee to get the same N_Port_ID on NPIV FDISC.
    
    Even though NPIV-enabled FCP devices are not affected by this problem, this
    code change optimizes recovery time for gone remote ports as a side effect.
    The timely drop of cached N_Port_IDs prevents unnecessary slow open port
    attempts.
    
    While the problem might have been in code before v2.6.32 commit
    799b76d09aee ("[SCSI] zfcp: Decouple gid_pn requests from erp") this fix
    depends on the gid_pn_work introduced with that commit, so we mark it as
    culprit to satisfy fix dependencies.
    
    Note: Point-to-point remote port is already handled separately and gets its
    N_Port_ID from the cached peer_d_id. So resetting port->d_id in general
    does not affect PtP.
    
    Link: https://lore.kernel.org/r/20220118165803.3667947-1-maier@linux.ibm.com
    Fixes: 799b76d09aee ("[SCSI] zfcp: Decouple gid_pn requests from erp")
    Cc: <stable@vger.kernel.org> #2.6.32+
    Suggested-by: Benjamin Block <bblock@linux.ibm.com>
    Reviewed-by: Benjamin Block <bblock@linux.ibm.com>
    Signed-off-by: Steffen Maier <maier@linux.ibm.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 62afb379a0fee7e9c2f9f68e1abeb85ceddf51b9
Author: John Garry <john.garry@huawei.com>
Date:   Tue Jan 18 20:15:05 2022 +0800

    scsi: pm8001: Fix bogus FW crash for maxcpus=1
    
    According to the comment in check_fw_ready() we should not check the
    IOP1_READY field in register SCRATCH_PAD_1 for 8008 or 8009 controllers.
    
    However we check this very field in process_oq() for processing the highest
    index interrupt vector. The highest interrupt vector is checked as the FW
    is programmed to signal fatal errors through this irq.
    
    Change that function to not check IOP1_READY for those mentioned
    controllers, but do check ILA_READY in both cases.
    
    The reason I assume that this was not hit earlier was because we always
    allocated 64 MSI(X), and just did not pass the vector index check in
    process_oq(), i.e.  the handler never ran for vector index 63.
    
    Link: https://lore.kernel.org/r/1642508105-95432-1-git-send-email-john.garry@huawei.com
    Tested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Signed-off-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 64fd4af6274eb0f49d29772c228fffcf6bde1635
Author: Saurav Kashyap <skashyap@marvell.com>
Date:   Mon Jan 17 05:53:11 2022 -0800

    scsi: qedf: Change context reset messages to ratelimited
    
    If FCoE is not configured, libfc/libfcoe keeps on retrying FLOGI and after
    3 retries driver does a context reset and tries fipvlan again.  This leads
    to context reset message flooding the logs. Hence ratelimit the message to
    prevent flooding the logs.
    
    Link: https://lore.kernel.org/r/20220117135311.6256-4-njavali@marvell.com
    Signed-off-by: Saurav Kashyap <skashyap@marvell.com>
    Signed-off-by: Nilesh Javali <njavali@marvell.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 5239ab63f17cee643bd4bf6addfedebaa7d4f41e
Author: Saurav Kashyap <skashyap@marvell.com>
Date:   Mon Jan 17 05:53:10 2022 -0800

    scsi: qedf: Fix refcount issue when LOGO is received during TMF
    
    Hung task call trace was seen during LOGO processing.
    
    [  974.309060] [0000:00:00.0]:[qedf_eh_device_reset:868]: 1:0:2:0: LUN RESET Issued...
    [  974.309065] [0000:00:00.0]:[qedf_initiate_tmf:2422]: tm_flags 0x10 sc_cmd 00000000c16b930f op = 0x2a target_id = 0x2 lun=0
    [  974.309178] [0000:00:00.0]:[qedf_initiate_tmf:2431]: portid=016900 tm_flags =LUN RESET
    [  974.309222] [0000:00:00.0]:[qedf_initiate_tmf:2438]: orig io_req = 00000000ec78df8f xid = 0x180 ref_cnt = 1.
    [  974.309625] host1: rport 016900: Received LOGO request while in state Ready
    [  974.309627] host1: rport 016900: Delete port
    [  974.309642] host1: rport 016900: work event 3
    [  974.309644] host1: rport 016900: lld callback ev 3
    [  974.313243] [0000:61:00.2]:[qedf_execute_tmf:2383]:1: fcport is uploading, not executing flush.
    [  974.313295] [0000:61:00.2]:[qedf_execute_tmf:2400]:1: task mgmt command success...
    [  984.031088] INFO: task jbd2/dm-15-8:7645 blocked for more than 120 seconds.
    [  984.031136]       Not tainted 4.18.0-305.el8.x86_64 #1
    
    [  984.031166] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [  984.031209] jbd2/dm-15-8    D    0  7645      2 0x80004080
    [  984.031212] Call Trace:
    [  984.031222]  __schedule+0x2c4/0x700
    [  984.031230]  ? unfreeze_partials.isra.83+0x16e/0x1a0
    [  984.031233]  ? bit_wait_timeout+0x90/0x90
    [  984.031235]  schedule+0x38/0xa0
    [  984.031238]  io_schedule+0x12/0x40
    [  984.031240]  bit_wait_io+0xd/0x50
    [  984.031243]  __wait_on_bit+0x6c/0x80
    [  984.031248]  ? free_buffer_head+0x21/0x50
    [  984.031251]  out_of_line_wait_on_bit+0x91/0xb0
    [  984.031257]  ? init_wait_var_entry+0x50/0x50
    [  984.031268]  jbd2_journal_commit_transaction+0x112e/0x19f0 [jbd2]
    [  984.031280]  kjournald2+0xbd/0x270 [jbd2]
    [  984.031284]  ? finish_wait+0x80/0x80
    [  984.031291]  ? commit_timeout+0x10/0x10 [jbd2]
    [  984.031294]  kthread+0x116/0x130
    [  984.031300]  ? kthread_flush_work_fn+0x10/0x10
    [  984.031305]  ret_from_fork+0x1f/0x40
    
    There was a ref count issue when LOGO is received during TMF. This leads to
    one of the I/Os hanging with the driver. Fix the ref count.
    
    Link: https://lore.kernel.org/r/20220117135311.6256-3-njavali@marvell.com
    Signed-off-by: Saurav Kashyap <skashyap@marvell.com>
    Signed-off-by: Nilesh Javali <njavali@marvell.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit b70a99fd13282d7885f69bf1372e28b7506a1613
Author: Saurav Kashyap <skashyap@marvell.com>
Date:   Mon Jan 17 05:53:09 2022 -0800

    scsi: qedf: Add stag_work to all the vports
    
    Call trace seen when creating NPIV ports, only 32 out of 64 show online.
    stag work was not initialized for vport, hence initialize the stag work.
    
    WARNING: CPU: 8 PID: 645 at kernel/workqueue.c:1635 __queue_delayed_work+0x68/0x80
    CPU: 8 PID: 645 Comm: kworker/8:1 Kdump: loaded Tainted: G IOE    --------- --
     4.18.0-348.el8.x86_64 #1
    Hardware name: Dell Inc. PowerEdge MX740c/0177V9, BIOS 2.12.2 07/09/2021
    Workqueue: events fc_lport_timeout [libfc]
    RIP: 0010:__queue_delayed_work+0x68/0x80
    Code: 89 b2 88 00 00 00 44 89 82 90 00 00 00 48 01 c8 48 89 42 50 41 81
    f8 00 20 00 00 75 1d e9 60 24 07 00 44 89 c7 e9 98 f6 ff ff <0f> 0b eb
    c5 0f 0b eb a1 0f 0b eb a7 0f 0b eb ac 44 89 c6 e9 40 23
    RSP: 0018:ffffae514bc3be40 EFLAGS: 00010006
    RAX: ffff8d25d6143750 RBX: 0000000000000202 RCX: 0000000000000002
    RDX: ffff8d2e31383748 RSI: ffff8d25c000d600 RDI: ffff8d2e31383788
    RBP: ffff8d2e31380de0 R08: 0000000000002000 R09: ffff8d2e31383750
    R10: ffffffffc0c957e0 R11: ffff8d2624800000 R12: ffff8d2e31380a58
    R13: ffff8d2d915eb000 R14: ffff8d25c499b5c0 R15: ffff8d2e31380e18
    FS:  0000000000000000(0000) GS:ffff8d2d1fb00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 000055fd0484b8b8 CR3: 00000008ffc10006 CR4: 00000000007706e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    PKRU: 55555554
    Call Trace:
      queue_delayed_work_on+0x36/0x40
      qedf_elsct_send+0x57/0x60 [qedf]
      fc_lport_enter_flogi+0x90/0xc0 [libfc]
      fc_lport_timeout+0xb7/0x140 [libfc]
      process_one_work+0x1a7/0x360
      ? create_worker+0x1a0/0x1a0
      worker_thread+0x30/0x390
      ? create_worker+0x1a0/0x1a0
      kthread+0x116/0x130
      ? kthread_flush_work_fn+0x10/0x10
      ret_from_fork+0x35/0x40
     ---[ end trace 008f00f722f2c2ff ]--
    
    Initialize stag work for all the vports.
    
    Link: https://lore.kernel.org/r/20220117135311.6256-2-njavali@marvell.com
    Signed-off-by: Saurav Kashyap <skashyap@marvell.com>
    Signed-off-by: Nilesh Javali <njavali@marvell.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit a65b32748f4566f986ba2495a8236c141fa42a26
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Sun Jan 16 11:06:49 2022 +0800

    scsi: ufs: ufshcd-pltfrm: Check the return value of devm_kstrdup()
    
    devm_kstrdup() returns pointer to allocated string on success, NULL on
    failure. So it is better to check the return value of it.
    
    Link: https://lore.kernel.org/r/tencent_4257E15D4A94FF9020DDCC4BB9B21C041408@qq.com
    Reviewed-by: Bean Huo <beanhuo@micron.com>
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit a861790afaa8b6369eee8a88c5d5d73f5799c0c6
Author: ZouMingzhe <mingzhe.zou@easystack.cn>
Date:   Tue Jan 11 13:47:42 2022 +0800

    scsi: target: iscsi: Make sure the np under each tpg is unique
    
    iscsit_tpg_check_network_portal() has nested for_each loops and is supposed
    to return true when a match is found. However, the tpg loop will still
    continue after existing the tpg_np loop. If this tpg_np is not the last the
    match value will be changed.
    
    Break the outer loop after finding a match and make sure the np under each
    tpg is unique.
    
    Link: https://lore.kernel.org/r/20220111054742.19582-1-mingzhe.zou@easystack.cn
    Signed-off-by: ZouMingzhe <mingzhe.zou@easystack.cn>
    Reviewed-by: Mike Christie <michael.christie@oracle.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 61263b3a11a2594b4e898f166c31162236182b5c
Author: Yang Yingliang <yangyingliang@huawei.com>
Date:   Tue Jan 11 09:24:41 2022 +0800

    scsi: elx: efct: Don't use GFP_KERNEL under spin lock
    
    GFP_KERNEL/GFP_DMA can't be used under a spin lock. According the comment,
    els_ios_lock is used to protect els ios list so we can move down the spin
    lock to avoid using this flag under the lock.
    
    Link: https://lore.kernel.org/r/20220111012441.3232527-1-yangyingliang@huawei.com
    Fixes: 8f406ef72859 ("scsi: elx: libefc: Extended link Service I/O handling")
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Reviewed-by: James Smart <jsmart2021@gmail.com>
    Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 63ee956f69d8c181e5251c7ce58b84c1edec0f6a
Author: Alexei Starovoitov <ast@kernel.org>
Date:   Mon Jan 24 20:20:51 2022 -0800

    bpf: Fix renaming task_getsecid_subj->current_getsecid_subj.
    
    The commit 6326948f940d missed renaming of task->current LSM hook in BTF_ID.
    Fix it to silence build warning:
    WARN: resolve_btfids: unresolved symbol bpf_lsm_task_getsecid_subj
    
    Fixes: 6326948f940d ("lsm: security_task_getsecid_subj() -> security_current_getsecid_subj()")
    Acked-by: Andrii Nakryiko <andrii@kernel.org>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 5e761a2287234bc402ba7ef07129f5103bcd775c
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Jan 16 19:18:44 2022 +0100

    drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable
    
    The function performs a check on the "phy" input parameter, however, it
    is used before the check.
    
    Initialize the "dev" variable after the sanity check to avoid a possible
    NULL pointer dereference.
    
    Fixes: 5c8290284402b ("drm/msm/dsi: Split PHY drivers to separate files")
    Addresses-Coverity-ID: 1493860 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20220116181844.7400-1-jose.exposito89@gmail.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 860a7b2a87b7c743154824d0597b6c3eb3b53154
Author: Rob Clark <robdclark@chromium.org>
Date:   Thu Jan 13 08:32:13 2022 -0800

    drm/msm/a6xx: Add missing suspend_count increment
    
    Reported-by: Danylo Piliaiev <dpiliaiev@igalia.com>
    Fixes: 3ab1c5cc3939 ("drm/msm: Add param for userspace to query suspend count")
    Signed-off-by: Rob Clark <robdclark@chromium.org>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20220113163215.215367-1-robdclark@gmail.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 0a727b459ee39bd4c5ced19d6024258ac87b6b2e
Author: Xianting Tian <xianting.tian@linux.alibaba.com>
Date:   Wed Jan 12 20:33:34 2022 +0800

    drm/msm: Fix wrong size calculation
    
    For example, memory-region in .dts as below,
            reg = <0x0 0x50000000 0x0 0x20000000>
    
    We can get below values,
    struct resource r;
    r.start = 0x50000000;
    r.end   = 0x6fffffff;
    
    So the size should be:
    size = r.end - r.start + 1 = 0x20000000
    
    Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
    Fixes: 072f1f9168ed ("drm/msm: add support for "stolen" mem")
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20220112123334.749776-1-xianting.tian@linux.alibaba.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 170b22234d5495f5e0844246e23f004639ee89ba
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Jan 9 20:24:31 2022 +0100

    drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
    
    The function performs a check on the "ctx" input parameter, however, it
    is used before the check.
    
    Initialize the "base" variable after the sanity check to avoid a
    possible NULL pointer dereference.
    
    Fixes: 4259ff7ae509e ("drm/msm/dpu: add support for pcc color block in dpu driver")
    Addresses-Coverity-ID: 1493866 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Link: https://lore.kernel.org/r/20220109192431.135949-1-jose.exposito89@gmail.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 774fe0cd838d1b1419d41ab4ea0613c80d4ecbd7
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 7 08:50:22 2022 +0000

    drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy
    
    The reference taken by 'of_find_device_by_node()' must be released when
    not needed anymore.
    Add the corresponding 'put_device()' in the error handling path.
    
    Fixes: e00012b256d4 ("drm/msm/hdmi: Make HDMI core get its PHY")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20220107085026.23831-1-linmq006@gmail.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit c04c3148ca12227d92f91b355b4538cc333c9922
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Dec 30 07:09:40 2021 +0000

    drm/msm/dsi: Fix missing put_device() call in dsi_get_phy
    
    If of_find_device_by_node() succeeds, dsi_get_phy() doesn't
    a corresponding put_device(). Thus add put_device() to fix the exception
    handling.
    
    Fixes: ec31abf ("drm/msm/dsi: Separate PHY to another platform device")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20211230070943.18116-1-linmq006@gmail.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 84d46e1fc33cc56b622b2e7a91703157161ce2e9
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Thu Dec 16 11:11:03 2021 +0800

    drm/msm: remove variable set but not used
    
    The code that uses variable mdss has been removed, So the declaration
    and assignment of the variable can be removed.
    
    Eliminate the following clang warning:
    drivers/gpu/drm/msm/msm_drv.c:513:19: warning: variable 'mdss' set but
    not used [-Wunused-but-set-variable]
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Fixes: 2027e5b3413d ("drm/msm: Initialize MDSS irq domain at probe time")
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
    Link: https://lore.kernel.org/r/20211216031103.34146-1-yang.lee@linux.alibaba.com
    Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>

commit 926fd9f23b27ca6587492c3f58f4c7f4cd01dad5
Author: Eric Biggers <ebiggers@google.com>
Date:   Thu Jan 13 11:44:38 2022 -0800

    ima: fix reference leak in asymmetric_verify()
    
    Don't leak a reference to the key if its algorithm is unknown.
    
    Fixes: 947d70597236 ("ima: Support EC keys for signature verification")
    Cc: <stable@vger.kernel.org> # v5.13+
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
    Reviewed-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
    Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>

commit 79da533d3cc717ccc05ddbd3190da8a72bc2408b
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Sun Jan 23 18:23:22 2022 -0800

    hwmon: (nct6775) Fix crash in clear_caseopen
    
    Paweł Marciniak reports the following crash, observed when clearing
    the chassis intrusion alarm.
    
    BUG: kernel NULL pointer dereference, address: 0000000000000028
    PGD 0 P4D 0
    Oops: 0000 [#1] PREEMPT SMP PTI
    CPU: 3 PID: 4815 Comm: bash Tainted: G S                5.16.2-200.fc35.x86_64 #1
    Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z97 Extreme4, BIOS P2.60A 05/03/2018
    RIP: 0010:clear_caseopen+0x5a/0x120 [nct6775]
    Code: 68 70 e8 e9 32 b1 e3 85 c0 0f 85 d2 00 00 00 48 83 7c 24 ...
    RSP: 0018:ffffabcb02803dd8 EFLAGS: 00010246
    RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
    RDX: ffff8e8808192880 RSI: 0000000000000000 RDI: ffff8e87c7509a68
    RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000000000a
    R10: 000000000000000a R11: f000000000000000 R12: 000000000000001f
    R13: ffff8e87c7509828 R14: ffff8e87c7509a68 R15: ffff8e88494527a0
    FS:  00007f4db9151740(0000) GS:ffff8e8ebfec0000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000000000000028 CR3: 0000000166b66001 CR4: 00000000001706e0
    Call Trace:
     <TASK>
     kernfs_fop_write_iter+0x11c/0x1b0
     new_sync_write+0x10b/0x180
     vfs_write+0x209/0x2a0
     ksys_write+0x4f/0xc0
     do_syscall_64+0x3b/0x90
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    The problem is that the device passed to clear_caseopen() is the hwmon
    device, not the platform device, and the platform data is not set in the
    hwmon device. Store the pointer to sio_data in struct nct6775_data and
    get if from there if needed.
    
    Fixes: 2e7b9886968b ("hwmon: (nct6775) Use superio_*() function pointers in sio_data.")
    Cc: Denis Pauk <pauk.denis@gmail.com>
    Cc: Bernhard Seibold <mail@bernhard-seibold.de>
    Reported-by: Paweł Marciniak <pmarciniak@lodz.home.pl>
    Tested-by: Denis Pauk <pauk.denis@gmail.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit e52984be9a522fb55c8f3e3df860d464d6658585
Merge: de8a820df2acd f04aefd4659b7
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Mon Jan 24 12:17:58 2022 -0800

    Merge tag 'linux-can-fixes-for-5.17-20220124' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can
    
    Marc Kleine-Budde says:
    
    ====================
    pull-request: can 2022-01-24
    
    The first patch updates the email address of Brian Silverman from his
    former employer to his private address.
    
    The next patch fixes DT bindings information for the tcan4x5x SPI CAN
    driver.
    
    The following patch targets the m_can driver and fixes the
    introduction of FIFO bulk read support.
    
    Another patch for the tcan4x5x driver, which fixes the max register
    value for the regmap config.
    
    The last patch for the flexcan driver marks the RX mailbox support for
    the MCF5441X as support.
    
    * tag 'linux-can-fixes-for-5.17-20220124' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can:
      can: flexcan: mark RX via mailboxes as supported on MCF5441X
      can: tcan4x5x: regmap: fix max register value
      can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if length is 0
      dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config
      mailmap: update email address of Brian Silverman
    ====================
    
    Link: https://lore.kernel.org/r/20220124175955.3464134-1-mkl@pengutronix.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit aee744a37aaf277e74557e683cc524fbe6daeef7
Author: Aswath Govindraju <a-govindraju@ti.com>
Date:   Thu Dec 23 17:46:50 2021 +0530

    arm64: dts: ti: k3-j721s2-common-proc-board: Alias console uart to serial2
    
    On J721s2 Linux console is on main_uart8 but to be consistent with other
    J7 family of devices, alias it to ttyS2 (serial2). This also eliminates
    need to have higher number of 8250 runtime UARTs.
    
    Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
    Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
    Signed-off-by: Nishanth Menon <nm@ti.com>
    Reviewed-by: Kishon Vijay Abraham I <kishon@ti.com>
    Link: https://lore.kernel.org/r/20211223121650.26868-3-vigneshr@ti.com

commit 165216533dda560f2620ce8f61381a9ee0ca57ba
Author: Aswath Govindraju <a-govindraju@ti.com>
Date:   Thu Dec 23 17:46:49 2021 +0530

    arm64: dts: ti: k3-j721s2: Move aliases to board dts
    
    Aliases are board specific and should be in board dts files.
    So, move aliases to board dts and trim the list to interfaces that are
    actually enabled.
    
    Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
    Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
    Signed-off-by: Nishanth Menon <nm@ti.com>
    Reviewed-by: Kishon Vijay Abraham I <kishon@ti.com>
    Link: https://lore.kernel.org/r/20211223121650.26868-2-vigneshr@ti.com

commit 82880283d7fcd0a1d20964a56d6d1a5cc0df0713
Author: Sergei Trofimovich <slyich@gmail.com>
Date:   Thu Jan 20 23:37:48 2022 +0000

    objtool: Fix truncated string warning
    
    On GCC 12, the build fails due to a possible truncated string:
    
        check.c: In function 'validate_call':
        check.c:2865:58: error: '%d' directive output may be truncated writing between 1 and 10 bytes into a region of size 9 [-Werror=format-truncation=]
         2865 |                 snprintf(pvname, sizeof(pvname), "pv_ops[%d]", idx);
              |                                                          ^~
    
    In theory it's a valid bug:
    
        static char pvname[16];
        int idx;
        ...
        idx = (rel->addend / sizeof(void *));
        snprintf(pvname, sizeof(pvname), "pv_ops[%d]", idx);
    
    There are only 7 chars for %d while it could take up to 9, so the
    printed "pv_ops[%d]" string could get truncated.
    
    In reality the bug should never happen, because pv_ops only has ~80
    entries, so 7 chars for the integer is more than enough.  Still, it's
    worth fixing.  Bump the buffer size by 2 bytes to silence the warning.
    
    [ jpoimboe: changed size to 19; massaged changelog ]
    
    Fixes: db2b0c5d7b6f ("objtool: Support pv_opsindirect calls for noinstr")
    Reported-by: Adam Borowski <kilobyte@angband.pl>
    Reported-by: Martin Liška <mliska@suse.cz>
    Signed-off-by: Sergei Trofimovich <slyich@gmail.com>
    Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
    Link: https://lore.kernel.org/r/20220120233748.2062559-1-slyich@gmail.com

commit f04aefd4659b7959e50e6d0d649936c6940f9d34
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jan 21 09:22:34 2022 +0100

    can: flexcan: mark RX via mailboxes as supported on MCF5441X
    
    Most flexcan IP cores support 2 RX modes:
    - FIFO
    - mailbox
    
    The flexcan IP core on the MCF5441X cannot receive CAN RTR messages
    via mailboxes. However the mailbox mode is more performant. The commit
    
    | 1c45f5778a3b ("can: flexcan: add ethtool support to change rx-rtr setting during runtime")
    
    added support to switch from FIFO to mailbox mode on these cores.
    
    After testing the mailbox mode on the MCF5441X by Angelo Dureghello,
    this patch marks it (without RTR capability) as supported. Further the
    IP core overview table is updated, that RTR reception via mailboxes is
    not supported.
    
    Link: https://lore.kernel.org/all/20220121084425.3141218-1-mkl@pengutronix.de
    Tested-by: Angelo Dureghello <angelo@kernel-space.org>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit e59986de5ff701494e14c722b78b6e6d513e0ab5
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jan 14 18:50:54 2022 +0100

    can: tcan4x5x: regmap: fix max register value
    
    The MRAM of the tcan4x5x has a size of 2K and starts at 0x8000. There
    are no further registers in the tcan4x5x making 0x87fc the biggest
    addressable register.
    
    This patch fixes the max register value of the regmap config from
    0x8ffc to 0x87fc.
    
    Fixes: 6e1caaf8ed22 ("can: tcan4x5x: fix max register value")
    Link: https://lore.kernel.org/all/20220119064011.2943292-1-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit db72589c49fd260bfc99c7160c079675bc7417af
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jan 14 15:35:01 2022 +0100

    can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if length is 0
    
    In order to optimize FIFO access, especially on m_can cores attached
    to slow busses like SPI, in patch
    
    | e39381770ec9 ("can: m_can: Disable IRQs on FIFO bus errors")
    
    bulk read/write support has been added to the m_can_fifo_{read,write}
    functions.
    
    That change leads to the tcan driver to call
    regmap_bulk_{read,write}() with a length of 0 (for CAN frames with 0
    data length). regmap treats this as an error:
    
    | tcan4x5x spi1.0 tcan4x5x0: FIFO write returned -22
    
    This patch fixes the problem by not calling the
    cdev->ops->{read,write)_fifo() in case of a 0 length read/write.
    
    Fixes: e39381770ec9 ("can: m_can: Disable IRQs on FIFO bus errors")
    Link: https://lore.kernel.org/all/20220114155751.2651888-1-mkl@pengutronix.de
    Cc: stable@vger.kernel.org
    Cc: Matt Kline <matt@bitbashing.io>
    Cc: Chandrasekar Ramakrishnan <rcsekar@samsung.com>
    Reported-by: Michael Anochin <anochin@photo-meter.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 17a30422621c0e04cb6060d20d7edcefd7463347
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jan 14 18:47:41 2022 +0100

    dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config
    
    This tcan4x5x only comes with 2K of MRAM, a RX FIFO with a dept of 32
    doesn't fit into the MRAM. Use a depth of 16 instead.
    
    Fixes: 4edd396a1911 ("dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver")
    Link: https://lore.kernel.org/all/20220119062951.2939851-1-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 984d1efff2304833e20fce89046ef8a89fb51d15
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Mon Jan 10 09:20:19 2022 +0100

    mailmap: update email address of Brian Silverman
    
    Brian Silverman's address at bluerivertech.com is not valid anymore,
    use Brian's private email address instead.
    
    Link: https://lore.kernel.org/all/20220110082359.2019735-1-mkl@pengutronix.de
    Cc: Brian Silverman <bsilver16384@gmail.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 27cdfde181bcacd226c230b2fd831f6f5b8c215f
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Jan 20 17:41:17 2022 +0000

    btrfs: update writeback index when starting defrag
    
    When starting a defrag, we should update the writeback index of the
    inode's mapping in case it currently has a value beyond the start of the
    range we are defragging. This can help performance and often result in
    getting less extents after writeback - for e.g., if the current value
    of the writeback index sits somewhere in the middle of a range that
    gets dirty by the defrag, then after writeback we can get two smaller
    extents instead of a single, larger extent.
    
    We used to have this before the refactoring in 5.16, but it was removed
    without any reason to do so. Originally it was added in kernel 3.1, by
    commit 2a0f7f5769992b ("Btrfs: fix recursive auto-defrag"), in order to
    fix a loop with autodefrag resulting in dirtying and writing pages over
    and over, but some testing on current code did not show that happening,
    at least with the test described in that commit.
    
    So add back the behaviour, as at the very least it is a nice to have
    optimization.
    
    Fixes: 7b508037d4cac3 ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 3c9d31c715948aaff0ee6d322a91a2dec07770bf
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Jan 20 17:11:52 2022 +0000

    btrfs: add back missing dirty page rate limiting to defrag
    
    A defrag operation can dirty a lot of pages, specially if operating on
    the entire file or a large file range. Any task dirtying pages should
    periodically call balance_dirty_pages_ratelimited(), as stated in that
    function's comments, otherwise they can leave too many dirty pages in
    the system. This is what we did before the refactoring in 5.16, and
    it should have remained, just like in the buffered write path and
    relocation. So restore that behaviour.
    
    Fixes: 7b508037d4cac3 ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0cb5950f3f3b51a4e8657d106f897f2b913e0586
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Jan 20 14:27:56 2022 +0000

    btrfs: fix deadlock when reserving space during defrag
    
    When defragging we can end up collecting a range for defrag that has
    already pages under delalloc (dirty), as long as the respective extent
    map for their range is not mapped to a hole, a prealloc extent or
    the extent map is from an old generation.
    
    Most of the time that is harmless from a functional perspective at
    least, however it can result in a deadlock:
    
    1) At defrag_collect_targets() we find an extent map that meets all
       requirements but there's delalloc for the range it covers, and we add
       its range to list of ranges to defrag;
    
    2) The defrag_collect_targets() function is called at defrag_one_range(),
       after it locked a range that overlaps the range of the extent map;
    
    3) At defrag_one_range(), while the range is still locked, we call
       defrag_one_locked_target() for the range associated to the extent
       map we collected at step 1);
    
    4) Then finally at defrag_one_locked_target() we do a call to
       btrfs_delalloc_reserve_space(), which will reserve data and metadata
       space. If the space reservations can not be satisfied right away, the
       flusher might be kicked in and start flushing delalloc and wait for
       the respective ordered extents to complete. If this happens we will
       deadlock, because both flushing delalloc and finishing an ordered
       extent, requires locking the range in the inode's io tree, which was
       already locked at defrag_collect_targets().
    
    So fix this by skipping extent maps for which there's already delalloc.
    
    Fixes: eb793cf857828d ("btrfs: defrag: introduce helper to collect target file extents")
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 6596a0229541270fb8d38d989f91b78838e5e9da
Author: Jiri Bohac <jbohac@suse.cz>
Date:   Wed Jan 19 10:22:53 2022 +0100

    xfrm: fix MTU regression
    
    Commit 749439bfac6e1a2932c582e2699f91d329658196 ("ipv6: fix udpv6
    sendmsg crash caused by too small MTU") breaks PMTU for xfrm.
    
    A Packet Too Big ICMPv6 message received in response to an ESP
    packet will prevent all further communication through the tunnel
    if the reported MTU minus the ESP overhead is smaller than 1280.
    
    E.g. in a case of a tunnel-mode ESP with sha256/aes the overhead
    is 92 bytes. Receiving a PTB with MTU of 1371 or less will result
    in all further packets in the tunnel dropped. A ping through the
    tunnel fails with "ping: sendmsg: Invalid argument".
    
    Apparently the MTU on the xfrm route is smaller than 1280 and
    fails the check inside ip6_setup_cork() added by 749439bf.
    
    We found this by debugging USGv6/ipv6ready failures. Failing
    tests are: "Phase-2 Interoperability Test Scenario IPsec" /
    5.3.11 and 5.4.11 (Tunnel Mode: Fragmentation).
    
    Commit b515d2637276a3810d6595e10ab02c13bfd0b63a ("xfrm:
    xfrm_state_mtu should return at least 1280 for ipv6") attempted
    to fix this but caused another regression in TCP MSS calculations
    and had to be reverted.
    
    The patch below fixes the situation by dropping the MTU
    check and instead checking for the underflows described in the
    749439bf commit message.
    
    Signed-off-by: Jiri Bohac <jbohac@suse.cz>
    Fixes: 749439bfac6e ("ipv6: fix udpv6 sendmsg crash caused by too small MTU")
    Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

commit 379f56c24e698f14242f532b1d0a0f1747725e08
Author: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Date:   Sat Jan 15 15:14:46 2022 +0300

    mmc: core: Wait for command setting 'Power Off Notification' bit to complete
    
    SD card is allowed to signal busy on DAT0 up to 1s after the
    CMD49. According to SD spec (version 6.0 section 5.8.1.3) first host
    waits until busy of CMD49 is released and only then polls Power
    Management Status register up to 1s until the card indicates ready to
    power off.
    
    Without waiting for busy before polling status register sometimes card
    becomes unresponsive and system fails to suspend:
    
      [  205.907459] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
      [  206.421274] sunxi-mmc 1c0f000.mmc: data error, sending stop command
      [  206.421321] sunxi-mmc 1c0f000.mmc: send stop command failed
      [  206.421347] mmc0: error -110 reading status reg of PM func
      [  206.421366] PM: dpm_run_callback(): mmc_bus_suspend+0x0/0x74 returns -110
      [  206.421402] mmcblk mmc0:aaaa: PM: failed to suspend async: error -110
      [  206.437064] PM: Some devices failed to suspend, or early wake event detected
    
    Tested with Sandisk Extreme PRO A2 64GB on Allwinner A64 system.
    
    Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
    Fixes: 2c5d42769038 ("mmc: core: Add support for Power Off Notification for SD cards")
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220115121447.641524-1-andrej.skvortzov@gmail.com
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit 4d315357b3d6c315a7260420c6c6fc076e58d14b
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Wed Jan 19 20:00:06 2022 +0800

    mmc: sh_mmcif: Check for null res pointer
    
    If there is no suitable resource, platform_get_resource() will return
    NULL.
    Therefore in order to avoid the dereference of the NULL pointer, it
    should be better to check the 'res'.
    
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Cc: stable@vger.kernel.org # v5.16+
    Link: https://lore.kernel.org/r/20220119120006.1426964-1-jiasheng@iscas.ac.cn
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit 40c67c291a93f8846c4a972c9ef1b7ba4544c8d0
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Wed Jan 12 16:31:56 2022 +0800

    mmc: sdhci-of-esdhc: Check for error num after setting mask
    
    Because of the possible failure of the dma_supported(), the
    dma_set_mask_and_coherent() may return error num.
    Therefore, it should be better to check it and return the error if
    fails.
    And since the sdhci_setup_host() has already checked the return value of
    the enable_dma, we need not check it in sdhci_resume_host() again.
    
    Fixes: 5552d7ad596c ("mmc: sdhci-of-esdhc: set proper dma mask for ls104x chips")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Acked-by: Adrian Hunter <adrian.hunter@intel.com>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220112083156.1124782-1-jiasheng@iscas.ac.cn
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

commit 7865827c432bf9885ee26e5767697c3d9e21a82c
Author: Gao Xiang <hsiangkao@linux.alibaba.com>
Date:   Fri Jan 21 17:14:12 2022 +0800

    erofs: avoid unnecessary z_erofs_decompressqueue_work() declaration
    
    Just code rearrange. No logic changes.
    
    Link: https://lore.kernel.org/r/20220121091412.86086-1-hsiangkao@linux.alibaba.com
    Reviewed-by: Yue Hu <huyue2@yulong.com>
    Reviewed-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

commit e33f42b20bcb2f55cb1eeeab9956a503dcf36107
Author: Gao Xiang <hsiangkao@linux.alibaba.com>
Date:   Thu Jan 13 13:18:45 2022 +0800

    erofs: fix fsdax partition offset handling
    
    After seeking time on testing today upstream fsdax, I found it
    actually doesn't work well as below:
    
    [  186.492983] ------------[ cut here ]------------
    [  186.493629] WARNING: CPU: 1 PID: 205 at fs/iomap/iter.c:33 iomap_iter+0x2f6/0x310
    
    The problem is that m_dax_part_off should be applied to physical
    addresses and very sorry about that I didn't catch this eariler.
    
    Anyway, let's fix it up now. Also, I need to find a way to set up
    a standalone testcase to look after this later.
    
    Link: https://lore.kernel.org/r/20220113051845.244461-1-hsiangkao@linux.alibaba.com
    Fixes: de2051147771 ("fsdax: shift partition offset handling into the file systems")
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>

commit e12963c453263d5321a2c610e98cbc731233b685
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 20:19:15 2022 +0200

    pinctrl: intel: Fix a glitch when updating IRQ flags on a preconfigured line
    
    The commit af7e3eeb84e2 ("pinctrl: intel: Disable input and output buffer
    when switching to GPIO") hadn't taken into account an update of the IRQ
    flags scenario.
    
    When updating the IRQ flags on the preconfigured line the ->irq_set_type()
    is called again. In such case the sequential Rx buffer configuration
    changes may trigger a falling or rising edge interrupt that may lead,
    on some platforms, to an undesired event.
    
    This may happen because each of intel_gpio_set_gpio_mode() and
    __intel_gpio_set_direction() updates the pad configuration with a different
    value of the GPIORXDIS bit. Notable, that the intel_gpio_set_gpio_mode() is
    called only for the pads that are configured as an input. Due to this fact,
    integrate the logic of __intel_gpio_set_direction() call into the
    intel_gpio_set_gpio_mode() so that the Rx buffer won't be disabled and
    immediately re-enabled.
    
    Fixes: af7e3eeb84e2 ("pinctrl: intel: Disable input and output buffer when switching to GPIO")
    Reported-by: Kane Chen <kane.chen@intel.com>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Tested-by: Grace Kao <grace.kao@intel.com>

commit e986f0e602f19ecb7880b04dd1db415ed9bca3f6
Author: Łukasz Bartosik <lb@semihalf.com>
Date:   Mon Jan 24 13:55:29 2022 +0100

    pinctrl: intel: fix unexpected interrupt
    
    ASUS Chromebook C223 with Celeron N3350 crashes sometimes during
    cold booot. Inspection of the kernel log showed that it gets into
    an inifite loop logging the following message:
    
    ->handle_irq():  000000009cdb51e8, handle_bad_irq+0x0/0x251
    ->irq_data.chip(): 000000005ec212a7, 0xffffa043009d8e7
    ->action(): 00000
       IRQ_NOPROBE set
    unexpected IRQ trap at vector 7c
    
    The issue happens during cold boot but only if cold boot happens
    at most several dozen seconds after Chromebook is powered off. For
    longer intervals between power off and power on (cold boot) the issue
    does not reproduce. The unexpected interrupt is sourced from INT3452
    GPIO pin which is used for SD card detect. Investigation relevealed
    that when the interval between power off and power on (cold boot)
    is less than several dozen seconds then values of INT3452 GPIO interrupt
    enable and interrupt pending registers survive power off and power
    on sequence and interrupt for SD card detect pin is enabled and pending
    during probe of SD controller which causes the unexpected IRQ message.
    "Intel Pentium and Celeron Processor N- and J- Series" volume 3 doc
    mentions that GPIO interrupt enable and status registers default
    value is 0x0.
    The fix clears INT3452 GPIO interrupt enabled and interrupt pending
    registers in its probe function.
    
    Fixes: 7981c0015af2 ("pinctrl: intel: Add Intel Sunrisepoint pin controller and GPIO support")
    Signed-off-by: Łukasz Bartosik <lb@semihalf.com>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

commit 77311237eaffa240af6eae1d511b61e77a20a2ef
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 12 22:58:46 2022 +0200

    pinctrl: Place correctly CONFIG_PINCTRL_ST in the Makefile
    
    Keep Makefile entries ordered in the same way as Kconfig ones.
    
    Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

commit 1e0924bd09916fab795fc2a21ec1d148f24299fd
Author: Masami Hiramatsu <mhiramat@kernel.org>
Date:   Mon Jan 24 17:17:54 2022 +0900

    arm64: Mark start_backtrace() notrace and NOKPROBE_SYMBOL
    
    Mark the start_backtrace() as notrace and NOKPROBE_SYMBOL
    because this function is called from ftrace and lockdep to
    get the caller address via return_address(). The lockdep
    is used in kprobes, it should also be NOKPROBE_SYMBOL.
    
    Fixes: b07f3499661c ("arm64: stacktrace: Move start_backtrace() out of the header")
    Cc: <stable@vger.kernel.org> # 5.13.x
    Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
    Reviewed-by: Mark Brown <broonie@kernel.org>
    Link: https://lore.kernel.org/r/164301227374.1433152.12808232644267107415.stgit@devnote2
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit eb30d838a44c9e59a2a106884f536119859c7257
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Mon Jan 24 08:45:38 2022 +0530

    arm64: errata: Update ARM64_ERRATUM_[2119858|2224489] with Cortex-X2 ranges
    
    Errata ARM64_ERRATUM_[2119858|2224489] also affect some Cortex-X2 ranges as
    well. Lets update these errata definition and detection to accommodate all
    new Cortex-X2 based cpu MIDR ranges.
    
    Cc: Will Deacon <will@kernel.org>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Link: https://lore.kernel.org/r/1642994138-25887-3-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 72bb9dcb6c33cfac80282713c2b4f2b254cd24d1
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Mon Jan 24 08:45:37 2022 +0530

    arm64: Add Cortex-X2 CPU part definition
    
    Add the CPU Partnumbers for the new Arm designs.
    
    Cc: Will Deacon <will@kernel.org>
    Cc: Suzuki Poulose <suzuki.poulose@arm.com>
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
    Link: https://lore.kernel.org/r/1642994138-25887-2-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 9ff5549b1d1d3c3a9d71220d44bd246586160f1d
Author: Michael Kelley <mikelley@microsoft.com>
Date:   Sun Jan 16 11:18:31 2022 -0800

    video: hyperv_fb: Fix validation of screen resolution
    
    In the WIN10 version of the Synthetic Video protocol with Hyper-V,
    Hyper-V reports a list of supported resolutions as part of the protocol
    negotiation. The driver calculates the maximum width and height from
    the list of resolutions, and uses those maximums to validate any screen
    resolution specified in the video= option on the kernel boot line.
    
    This method of validation is incorrect. For example, the list of
    supported resolutions could contain 1600x1200 and 1920x1080, both of
    which fit in an 8 Mbyte frame buffer.  But calculating the max width
    and height yields 1920 and 1200, and 1920x1200 resolution does not fit
    in an 8 Mbyte frame buffer.  Unfortunately, this resolution is accepted,
    causing a kernel fault when the driver accesses memory outside the
    frame buffer.
    
    Instead, validate the specified screen resolution by calculating
    its size, and comparing against the frame buffer size.  Delete the
    code for calculating the max width and height from the list of
    resolutions, since these max values have no use.  Also add the
    frame buffer size to the info message to aid in understanding why
    a resolution might be rejected.
    
    Fixes: 67e7cdb4829d ("video: hyperv: hyperv_fb: Obtain screen resolution from Hyper-V host")
    Signed-off-by: Michael Kelley <mikelley@microsoft.com>
    Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
    Acked-by: Helge Deller <deller@gmx.de>
    Link: https://lore.kernel.org/r/1642360711-2335-1-git-send-email-mikelley@microsoft.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit 1625566ec8fd3a42e305c5118df81fb113eb60a7
Author: Xianting Tian <xianting.tian@linux.alibaba.com>
Date:   Mon Jan 24 10:04:56 2022 +0800

    KVM: remove async parameter of hva_to_pfn_remapped()
    
    The async parameter of hva_to_pfn_remapped() is not used, so remove it.
    
    Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
    Message-Id: <20220124020456.156386-1-xianting.tian@linux.alibaba.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit adb759e599990416e42e659c024a654b76c84617
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Sun Jan 23 13:42:19 2022 +0100

    x86,kvm/xen: Remove superfluous .fixup usage
    
    Commit 14243b387137 ("KVM: x86/xen: Add KVM_IRQ_ROUTING_XEN_EVTCHN and
    event channel delivery") adds superfluous .fixup usage after the whole
    .fixup section was removed in commit e5eefda5aa51 ("x86: Remove .fixup
    section").
    
    Fixes: 14243b387137 ("KVM: x86/xen: Add KVM_IRQ_ROUTING_XEN_EVTCHN and event channel delivery")
    Reported-by: Borislav Petkov <bp@alien8.de>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Message-Id: <20220123124219.GH20638@worktop.programming.kicks-ass.net>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 94fea1d8a30eadc3ef07afc0f53dc06799bb300b
Author: Sean Christopherson <seanjc@google.com>
Date:   Sat Jan 22 01:52:11 2022 +0000

    KVM: VMX: Zero host's SYSENTER_ESP iff SYSENTER is NOT used
    
    Zero vmcs.HOST_IA32_SYSENTER_ESP when initializing *constant* host state
    if and only if SYSENTER cannot be used, i.e. the kernel is a 64-bit
    kernel and is not emulating 32-bit syscalls.  As the name suggests,
    vmx_set_constant_host_state() is intended for state that is *constant*.
    When SYSENTER is used, SYSENTER_ESP isn't constant because stacks are
    per-CPU, and the VMCS must be updated whenever the vCPU is migrated to a
    new CPU.  The logic in vmx_vcpu_load_vmcs() doesn't differentiate between
    "never loaded" and "loaded on a different CPU", i.e. setting SYSENTER_ESP
    on VMCS load also handles setting correct host state when the VMCS is
    first loaded.
    
    Because a VMCS must be loaded before it is initialized during vCPU RESET,
    zeroing the field in vmx_set_constant_host_state() obliterates the value
    that was written when the VMCS was loaded.  If the vCPU is run before it
    is migrated, the subsequent VM-Exit will zero out MSR_IA32_SYSENTER_ESP,
    leading to a #DF on the next 32-bit syscall.
    
      double fault: 0000 [#1] SMP
      CPU: 0 PID: 990 Comm: stable Not tainted 5.16.0+ #97
      Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
      EIP: entry_SYSENTER_32+0x0/0xe7
      Code: <9c> 50 eb 17 0f 20 d8 a9 00 10 00 00 74 0d 25 ff ef ff ff 0f 22 d8
      EAX: 000000a2 EBX: a8d1300c ECX: a8d13014 EDX: 00000000
      ESI: a8f87000 EDI: a8d13014 EBP: a8d12fc0 ESP: 00000000
      DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00210093
      CR0: 80050033 CR2: fffffffc CR3: 02c3b000 CR4: 00152e90
    
    Fixes: 6ab8a4053f71 ("KVM: VMX: Avoid to rdmsrl(MSR_IA32_SYSENTER_ESP)")
    Cc: Lai Jiangshan <laijs@linux.alibaba.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20220122015211.1468758-1-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 9daf0a4d32d60a57f2a2533bdf4c178be7fdff7f
Author: Tom Rix <trix@redhat.com>
Date:   Sun Jan 16 04:59:36 2022 -0800

    quota: cleanup double word in comment
    
    Remove the second 'handle'.
    
    Link: https://lore.kernel.org/r/20220116125936.389767-1-trix@redhat.com
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit ea8569194b43f0f01f0a84c689388542c7254a1f
Author: Jan Kara <jack@suse.cz>
Date:   Tue Jan 18 09:57:25 2022 +0100

    udf: Restore i_lenAlloc when inode expansion fails
    
    When we fail to expand inode from inline format to a normal format, we
    restore inode to contain the original inline formatting but we forgot to
    set i_lenAlloc back. The mismatch between i_lenAlloc and i_size was then
    causing further problems such as warnings and lost data down the line.
    
    Reported-by: butt3rflyh4ck <butterflyhuangxx@gmail.com>
    CC: stable@vger.kernel.org
    Fixes: 7e49b6f2480c ("udf: Convert UDF to new truncate calling sequence")
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit 7fc3b7c2981bbd1047916ade327beccb90994eee
Author: Jan Kara <jack@suse.cz>
Date:   Mon Jan 17 18:22:13 2022 +0100

    udf: Fix NULL ptr deref when converting from inline format
    
    udf_expand_file_adinicb() calls directly ->writepage to write data
    expanded into a page. This however misses to setup inode for writeback
    properly and so we can crash on inode->i_wb dereference when submitting
    page for IO like:
    
      BUG: kernel NULL pointer dereference, address: 0000000000000158
      #PF: supervisor read access in kernel mode
    ...
      <TASK>
      __folio_start_writeback+0x2ac/0x350
      __block_write_full_page+0x37d/0x490
      udf_expand_file_adinicb+0x255/0x400 [udf]
      udf_file_write_iter+0xbe/0x1b0 [udf]
      new_sync_write+0x125/0x1c0
      vfs_write+0x28e/0x400
    
    Fix the problem by marking the page dirty and going through the standard
    writeback path to write the page. Strictly speaking we would not even
    have to write the page but we want to catch e.g. ENOSPC errors early.
    
    Reported-by: butt3rflyh4ck <butterflyhuangxx@gmail.com>
    CC: stable@vger.kernel.org
    Fixes: 52ebea749aae ("writeback: make backing_dev_info host cgroup-specific bdi_writebacks")
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit de8a820df2acd02eac1d98a99dd447634226d653
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Sun Jan 23 20:27:58 2022 +0800

    net: stmmac: remove unused members in struct stmmac_priv
    
    The tx_coalesce and mii_irq are not used at all now, so remove them.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit bdac3bbd0dc63873a9c606b8e4f814e6d61d288d
Author: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Date:   Fri Nov 26 16:43:42 2021 +0100

    spi: spi-rockchip: Add rk3568-spi compatible
    
    This adds a compatible string for the SPI controller found on
    the RK3566 and RK3568 SoCs.
    
    Signed-off-by: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
    Link: https://lore.kernel.org/r/20211126154344.724316-2-frattaroli.nicolas@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 29044dae2e746949ad4b9cbdbfb248994d1dcdb4
Author: Amir Goldstein <amir73il@gmail.com>
Date:   Thu Jan 20 23:53:05 2022 +0200

    fsnotify: fix fsnotify hooks in pseudo filesystems
    
    Commit 49246466a989 ("fsnotify: move fsnotify_nameremove() hook out of
    d_delete()") moved the fsnotify delete hook before d_delete() so fsnotify
    will have access to a positive dentry.
    
    This allowed a race where opening the deleted file via cached dentry
    is now possible after receiving the IN_DELETE event.
    
    To fix the regression in pseudo filesystems, convert d_delete() calls
    to d_drop() (see commit 46c46f8df9aa ("devpts_pty_kill(): don't bother
    with d_delete()") and move the fsnotify hook after d_drop().
    
    Add a missing fsnotify_unlink() hook in nfsdfs that was found during
    the audit of fsnotify hooks in pseudo filesystems.
    
    Note that the fsnotify hooks in simple_recursive_removal() follow
    d_invalidate(), so they require no change.
    
    Link: https://lore.kernel.org/r/20220120215305.282577-2-amir73il@gmail.com
    Reported-by: Ivan Delalande <colona@arista.com>
    Link: https://lore.kernel.org/linux-fsdevel/YeNyzoDM5hP5LtGW@visor/
    Fixes: 49246466a989 ("fsnotify: move fsnotify_nameremove() hook out of d_delete()")
    Cc: stable@vger.kernel.org # v5.3+
    Signed-off-by: Amir Goldstein <amir73il@gmail.com>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit a37d9a17f099072fe4d3a9048b0321978707a918
Author: Amir Goldstein <amir73il@gmail.com>
Date:   Thu Jan 20 23:53:04 2022 +0200

    fsnotify: invalidate dcache before IN_DELETE event
    
    Apparently, there are some applications that use IN_DELETE event as an
    invalidation mechanism and expect that if they try to open a file with
    the name reported with the delete event, that it should not contain the
    content of the deleted file.
    
    Commit 49246466a989 ("fsnotify: move fsnotify_nameremove() hook out of
    d_delete()") moved the fsnotify delete hook before d_delete() so fsnotify
    will have access to a positive dentry.
    
    This allowed a race where opening the deleted file via cached dentry
    is now possible after receiving the IN_DELETE event.
    
    To fix the regression, create a new hook fsnotify_delete() that takes
    the unlinked inode as an argument and use a helper d_delete_notify() to
    pin the inode, so we can pass it to fsnotify_delete() after d_delete().
    
    Backporting hint: this regression is from v5.3. Although patch will
    apply with only trivial conflicts to v5.4 and v5.10, it won't build,
    because fsnotify_delete() implementation is different in each of those
    versions (see fsnotify_link()).
    
    A follow up patch will fix the fsnotify_unlink/rmdir() calls in pseudo
    filesystem that do not need to call d_delete().
    
    Link: https://lore.kernel.org/r/20220120215305.282577-1-amir73il@gmail.com
    Reported-by: Ivan Delalande <colona@arista.com>
    Link: https://lore.kernel.org/linux-fsdevel/YeNyzoDM5hP5LtGW@visor/
    Fixes: 49246466a989 ("fsnotify: move fsnotify_nameremove() hook out of d_delete()")
    Cc: stable@vger.kernel.org # v5.3+
    Signed-off-by: Amir Goldstein <amir73il@gmail.com>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit ebe0582bee78e221b7d9f09ff22a530e0ddd6c96
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 23 07:53:46 2022 +0100

    net: atlantic: Use the bitmap API instead of hand-writing it
    
    Simplify code by using bitmap_weight() and bitmap_zero() instead of
    hand-writing these functions.
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Reviewed-by: Igor Russkikh <irusskikh@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2afc3b5a31f9edf3ef0f374f5d70610c79c93a42
Author: Xin Long <lucien.xin@gmail.com>
Date:   Sat Jan 22 06:40:56 2022 -0500

    ping: fix the sk_bound_dev_if match in ping_lookup
    
    When 'ping' changes to use PING socket instead of RAW socket by:
    
       # sysctl -w net.ipv4.ping_group_range="0 100"
    
    the selftests 'router_broadcast.sh' will fail, as such command
    
      # ip vrf exec vrf-h1 ping -I veth0 198.51.100.255 -b
    
    can't receive the response skb by the PING socket. It's caused by mismatch
    of sk_bound_dev_if and dif in ping_rcv() when looking up the PING socket,
    as dif is vrf-h1 if dif's master was set to vrf-h1.
    
    This patch is to fix this regression by also checking the sk_bound_dev_if
    against sdif so that the packets can stil be received even if the socket
    is not bound to the vrf device but to the real iif.
    
    Fixes: c319b4d76b9e ("net: ipv4: add IPPROTO_ICMP socket kind")
    Reported-by: Hangbin Liu <liuhangbin@gmail.com>
    Signed-off-by: Xin Long <lucien.xin@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 58cd4a088e8917b4092c7011d499e277e04a6644
Author: Vincenzo Frascino <vincenzo.frascino@arm.com>
Date:   Fri Jan 21 12:12:34 2022 +0000

    arm64: vdso: Fix "no previous prototype" warning
    
    If compiling the arm64 kernel with W=1 the following warning is produced:
    
    | arch/arm64/kernel/vdso/vgettimeofday.c:9:5: error: no previous prototype for ‘__kernel_clock_gettime’ [-Werror=missing-prototypes]
    |     9 | int __kernel_clock_gettime(clockid_t clock,
    |       |     ^~~~~~~~~~~~~~~~~~~~~~
    | arch/arm64/kernel/vdso/vgettimeofday.c:15:5: error: no previous prototype for ‘__kernel_gettimeofday’ [-Werror=missing-prototypes]
    |    15 | int __kernel_gettimeofday(struct __kernel_old_timeval *tv,
    |       |     ^~~~~~~~~~~~~~~~~~~~~
    | arch/arm64/kernel/vdso/vgettimeofday.c:21:5: error: no previous prototype for ‘__kernel_clock_getres’ [-Werror=missing-prototypes]
    |    21 | int __kernel_clock_getres(clockid_t clock_id,
    |       |     ^~~~~~~~~~~~~~~~~~~~~
    
    This patch removes "-Wmissing-prototypes" and "-Wmissing-declarations" compilers
    flags from the compilation of vgettimeofday.c to make possible to build the
    kernel with CONFIG_WERROR enabled.
    
    Cc: Will Deacon <will@kernel.org>
    Reported-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
    Tested-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Link: https://lore.kernel.org/r/20220121121234.47273-1-vincenzo.frascino@arm.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Sat Jan 22 17:43:09 2022 +0800

    net/smc: Transitional solution for clcsock race issue
    
    We encountered a crash in smc_setsockopt() and it is caused by
    accessing smc->clcsock after clcsock was released.
    
     BUG: kernel NULL pointer dereference, address: 0000000000000020
     #PF: supervisor read access in kernel mode
     #PF: error_code(0x0000) - not-present page
     PGD 0 P4D 0
     Oops: 0000 [#1] PREEMPT SMP PTI
     CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E     5.16.0-rc4+ #53
     RIP: 0010:smc_setsockopt+0x59/0x280 [smc]
     Call Trace:
      <TASK>
      __sys_setsockopt+0xfc/0x190
      __x64_sys_setsockopt+0x20/0x30
      do_syscall_64+0x34/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
     RIP: 0033:0x7f16ba83918e
      </TASK>
    
    This patch tries to fix it by holding clcsock_release_lock and
    checking whether clcsock has already been released before access.
    
    In case that a crash of the same reason happens in smc_getsockopt()
    or smc_switch_to_fallback(), this patch also checkes smc->clcsock
    in them too. And the caller of smc_switch_to_fallback() will identify
    whether fallback succeeds according to the return value.
    
    Fixes: fd57770dd198 ("net/smc: wait for pending work before clcsock release_sock")
    Link: https://lore.kernel.org/lkml/5dd7ffd1-28e2-24cc-9442-1defec27375e@linux.ibm.com/T/
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Acked-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3a5d9db7fbdfc8207ddf70d92668ced0ab330701
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Fri Jan 21 18:59:21 2022 -0800

    ibmvnic: remove unused ->wait_capability
    
    With previous bug fix, ->wait_capability flag is no longer needed and can
    be removed.
    
    Fixes: 249168ad07cd ("ibmvnic: Make CRQ interrupt tasklet wait for all capabilities crqs")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Reviewed-by: Dany Madden <drt@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 48079e7fdd0269d66b1d7d66ae88bd03162464ad
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Fri Jan 21 18:59:20 2022 -0800

    ibmvnic: don't spin in tasklet
    
    ibmvnic_tasklet() continuously spins waiting for responses to all
    capability requests. It does this to avoid encountering an error
    during initialization of the vnic. However if there is a bug in the
    VIOS and we do not receive a response to one or more queries the
    tasklet ends up spinning continuously leading to hard lock ups.
    
    If we fail to receive a message from the VIOS it is reasonable to
    timeout the login attempt rather than spin indefinitely in the tasklet.
    
    Fixes: 249168ad07cd ("ibmvnic: Make CRQ interrupt tasklet wait for all capabilities crqs")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Reviewed-by: Dany Madden <drt@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 151b6a5c06b678687f64f2d9a99fd04d5cd32b72
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Fri Jan 21 18:59:19 2022 -0800

    ibmvnic: init ->running_cap_crqs early
    
    We use ->running_cap_crqs to determine when the ibmvnic_tasklet() should
    send out the next protocol message type. i.e when we get back responses
    to all our QUERY_CAPABILITY CRQs we send out REQUEST_CAPABILITY crqs.
    Similiary, when we get responses to all the REQUEST_CAPABILITY crqs, we
    send out the QUERY_IP_OFFLOAD CRQ.
    
    We currently increment ->running_cap_crqs as we send out each CRQ and
    have the ibmvnic_tasklet() send out the next message type, when this
    running_cap_crqs count drops to 0.
    
    This assumes that all the CRQs of the current type were sent out before
    the count drops to 0. However it is possible that we send out say 6 CRQs,
    get preempted and receive all the 6 responses before we send out the
    remaining CRQs. This can result in ->running_cap_crqs count dropping to
    zero before all messages of the current type were sent and we end up
    sending the next protocol message too early.
    
    Instead initialize the ->running_cap_crqs upfront so the tasklet will
    only send the next protocol message after all responses are received.
    
    Use the cap_reqs local variable to also detect any discrepancy (either
    now or in future) in the number of capability requests we actually send.
    
    Currently only send_query_cap() is affected by this behavior (of sending
    next message early) since it is called from the worker thread (during
    reset) and from application thread (during ->ndo_open()) and they can be
    preempted. send_request_cap() is only called from the tasklet  which
    processes CRQ responses sequentially, is not be affected.  But to
    maintain the existing symmtery with send_query_capability() we update
    send_request_capability() also.
    
    Fixes: 249168ad07cd ("ibmvnic: Make CRQ interrupt tasklet wait for all capabilities crqs")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Reviewed-by: Dany Madden <drt@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit db9f0e8bf79e6da7068b5818fea0ffd9d0d4b4da
Author: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
Date:   Fri Jan 21 18:59:18 2022 -0800

    ibmvnic: Allow extra failures before disabling
    
    If auto-priority-failover (APF) is enabled and there are at least two
    backing devices of different priorities, some resets like fail-over,
    change-param etc can cause at least two back to back failovers. (Failover
    from high priority backing device to lower priority one and then back
    to the higher priority one if that is still functional).
    
    Depending on the timimg of the two failovers it is possible to trigger
    a "hard" reset and for the hard reset to fail due to failovers. When this
    occurs, the driver assumes that the network is unstable and disables the
    VNIC for a 60-second "settling time". This in turn can cause the ethtool
    command to fail with "No such device" while the vnic automatically recovers
    a little while later.
    
    Given that it's possible to have two back to back failures, allow for extra
    failures before disabling the vnic for the settling time.
    
    Fixes: f15fde9d47b8 ("ibmvnic: delay next reset if hard reset fails")
    Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.ibm.com>
    Reviewed-by: Dany Madden <drt@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 27a8caa59babb96c5890569e131bc0eb6d45daee
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 21 16:57:31 2022 -0800

    ipv4: fix ip option filtering for locally generated fragments
    
    During IP fragmentation we sanitize IP options. This means overwriting
    options which should not be copied with NOPs. Only the first fragment
    has the original, full options.
    
    ip_fraglist_prepare() copies the IP header and options from previous
    fragment to the next one. Commit 19c3401a917b ("net: ipv4: place control
    buffer handling away from fragmentation iterators") moved sanitizing
    options before ip_fraglist_prepare() which means options are sanitized
    and then overwritten again with the old values.
    
    Fixing this is not enough, however, nor did the sanitization work
    prior to aforementioned commit.
    
    ip_options_fragment() (which does the sanitization) uses ipcb->opt.optlen
    for the length of the options. ipcb->opt of fragments is not populated
    (it's 0), only the head skb has the state properly built. So even when
    called at the right time ip_options_fragment() does nothing. This seems
    to date back all the way to v2.5.44 when the fast path for pre-fragmented
    skbs had been introduced. Prior to that ip_options_build() would have been
    called for every fragment (in fact ever since v2.5.44 the fragmentation
    handing in ip_options_build() has been dead code, I'll clean it up in
    -next).
    
    In the original patch (see Link) caixf mentions fixing the handling
    for fragments other than the second one, but I'm not sure how _any_
    fragment could have had their options sanitized with the code
    as it stood.
    
    Tested with python (MTU on lo lowered to 1000 to force fragmentation):
    
      import socket
      s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
      s.setsockopt(socket.IPPROTO_IP, socket.IP_OPTIONS,
                   bytearray([7,4,5,192, 20|0x80,4,1,0]))
      s.sendto(b'1'*2000, ('127.0.0.1', 1234))
    
    Before:
    
    IP (tos 0x0, ttl 64, id 1053, offset 0, flags [+], proto UDP (17), length 996, options (RR [bad length 4] [bad ptr 5] 192.148.4.1,,RA value 256))
        localhost.36500 > localhost.search-agent: UDP, length 2000
    IP (tos 0x0, ttl 64, id 1053, offset 968, flags [+], proto UDP (17), length 996, options (RR [bad length 4] [bad ptr 5] 192.148.4.1,,RA value 256))
        localhost > localhost: udp
    IP (tos 0x0, ttl 64, id 1053, offset 1936, flags [none], proto UDP (17), length 100, options (RR [bad length 4] [bad ptr 5] 192.148.4.1,,RA value 256))
        localhost > localhost: udp
    
    After:
    
    IP (tos 0x0, ttl 96, id 42549, offset 0, flags [+], proto UDP (17), length 996, options (RR [bad length 4] [bad ptr 5] 192.148.4.1,,RA value 256))
        localhost.51607 > localhost.search-agent: UDP, bad length 2000 > 960
    IP (tos 0x0, ttl 96, id 42549, offset 968, flags [+], proto UDP (17), length 996, options (NOP,NOP,NOP,NOP,RA value 256))
        localhost > localhost: udp
    IP (tos 0x0, ttl 96, id 42549, offset 1936, flags [none], proto UDP (17), length 100, options (NOP,NOP,NOP,NOP,RA value 256))
        localhost > localhost: udp
    
    RA (20 | 0x80) is now copied as expected, RR (7) is "NOPed out".
    
    Link: https://lore.kernel.org/netdev/20220107080559.122713-1-ooppublic@163.com/
    Fixes: 19c3401a917b ("net: ipv4: place control buffer handling away from fragmentation iterators")
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: caixf <ooppublic@163.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 4064c461148ab129dfe5eaeea129b4af6cf4b9b7
Author: Jens Wiklander <jens.wiklander@linaro.org>
Date:   Tue Dec 28 21:25:57 2021 +0100

    optee: add error checks in optee_ffa_do_call_with_arg()
    
    Adds error checking in optee_ffa_do_call_with_arg() for correctness.
    
    Fixes: 4615e5a34b95 ("optee: add FF-A support")
    Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
    Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>

commit 1d10f8a1f40b965d449e8f2d5ed7b96a7c138b77
Author: Jianguo Wu <wujianguo@chinatelecom.cn>
Date:   Fri Jan 21 17:15:31 2022 +0800

    net-procfs: show net devices bound packet types
    
    After commit:7866a621043f ("dev: add per net_device packet type chains"),
    we can not get packet types that are bound to a specified net device by
    /proc/net/ptype, this patch fix the regression.
    
    Run "tcpdump -i ens192 udp -nns0" Before and after apply this patch:
    
    Before:
      [root@localhost ~]# cat /proc/net/ptype
      Type Device      Function
      0800          ip_rcv
      0806          arp_rcv
      86dd          ipv6_rcv
    
    After:
      [root@localhost ~]# cat /proc/net/ptype
      Type Device      Function
      ALL  ens192   tpacket_rcv
      0800          ip_rcv
      0806          arp_rcv
      86dd          ipv6_rcv
    
    v1 -> v2:
      - fix the regression rather than adding new /proc API as
        suggested by Stephen Hemminger.
    
    Fixes: 7866a621043f ("dev: add per net_device packet type chains")
    Signed-off-by: Jianguo Wu <wujianguo@chinatelecom.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit aa6034678e873db8bd5c5a4b73f8b88c469374d6
Author: Hangbin Liu <liuhangbin@gmail.com>
Date:   Fri Jan 21 16:25:18 2022 +0800

    bonding: use rcu_dereference_rtnl when get bonding active slave
    
    bond_option_active_slave_get_rcu() should not be used in rtnl_mutex as it
    use rcu_dereference(). Replace to rcu_dereference_rtnl() so we also can use
    this function in rtnl protected context.
    
    With this update, we can rmeove the rcu_read_lock/unlock in
    bonding .ndo_eth_ioctl and .get_ts_info.
    
    Reported-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Fixes: 94dd016ae538 ("bond: pass get_ts_info and SIOC[SG]HWTSTAMP ioctl to active device")
    Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit abc8dc34d1f6e34ed346c6e3fc554127e421b769
Author: Jerome Forissier <jerome@forissier.org>
Date:   Thu Jan 13 16:27:13 2022 +0100

    tee: optee: do not check memref size on return from Secure World
    
    Commit c650b8dc7a79 ("tee: optee: do not check memref size on return
    from Secure World") was mistakenly lost in commit 4602c5842f64 ("optee:
    refactor driver with internal callbacks"). Remove the unwanted code
    again.
    
    Fixes: 4602c5842f64 ("optee: refactor driver with internal callbacks")
    Signed-off-by: Jerome Forissier <jerome@forissier.org>
    Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
    Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>

commit 9decff5f403f9a48f639736ec0271e2870cadbb6
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Dec 26 15:32:45 2021 +0100

    optee: Use bitmap_free() to free bitmap
    
    kfree() and bitmap_free() are the same. But using the latter is more
    consistent when freeing memory allocated with bitmap_zalloc().
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
    Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>

commit 2148927e6ed43a1667baf7c2ae3e0e05a44b51a0
Author: Marek Behún <kabel@kernel.org>
Date:   Wed Jan 19 17:44:55 2022 +0100

    net: sfp: ignore disabled SFP node
    
    Commit ce0aa27ff3f6 ("sfp: add sfp-bus to bridge between network devices
    and sfp cages") added code which finds SFP bus DT node even if the node
    is disabled with status = "disabled". Because of this, when phylink is
    created, it ends with non-null .sfp_bus member, even though the SFP
    module is not probed (because the node is disabled).
    
    We need to ignore disabled SFP bus node.
    
    Fixes: ce0aa27ff3f6 ("sfp: add sfp-bus to bridge between network devices and sfp cages")
    Signed-off-by: Marek Behún <kabel@kernel.org>
    Cc: stable@vger.kernel.org # 2203cbf2c8b5 ("net: sfp: move fwnode parsing into sfp-bus layer")
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b8fb0d9b47660ddb8a8256412784aad7cee9f21a
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Thu Jan 20 11:44:39 2022 -0600

    platform/x86: amd-pmc: Correct usage of SMU version
    
    Yellow carp has been outputting versions like `1093.24.0`, but this
    is supposed to be 69.24.0. That is the MSB is being interpreted
    incorrectly.
    
    The MSB is not part of the major version, but has generally been
    treated that way thus far.  It's actually the program, and used to
    distinguish between two programs from a similar family but different
    codebase.
    
    Link: https://patchwork.freedesktop.org/patch/469993/
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Link: https://lore.kernel.org/r/20220120174439.12770-1-mario.limonciello@amd.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit f8c28b93d2628610cf793b3528f6f40fd1c7cd5b
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Jan 17 12:26:44 2022 +0100

    platform/x86: asus-tf103c-dock: Make 2 global structs static
    
    tf103c_dock_hid_ll_driver and tf103c_dock_pm_ops are not used outside of
    the driver, make them both static.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220117112644.260168-2-hdegoede@redhat.com

commit f7086daab3b540c89951b9b4c00fc49111f7cfa6
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Jan 17 12:26:43 2022 +0100

    platform/x86: amd-pmc: Make amd_pmc_stb_debugfs_fops static
    
    amd_pmc_stb_debugfs_fops is not used outside of amd-pmc.c, make it
    static.
    
    Cc: Sanket Goswami <Sanket.Goswami@amd.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220117112644.260168-1-hdegoede@redhat.com

commit 17da2d5f93692086dd096a975225ffd5622d0bf8
Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Date:   Tue Jan 11 18:25:21 2022 -0800

    platform/x86: ISST: Fix possible circular locking dependency detected
    
    As reported:
    
    [  256.104522] ======================================================
    [  256.113783] WARNING: possible circular locking dependency detected
    [  256.120093] 5.16.0-rc6-yocto-standard+ #99 Not tainted
    [  256.125362] ------------------------------------------------------
    [  256.131673] intel-speed-sel/844 is trying to acquire lock:
    [  256.137290] ffffffffc036f0d0 (punit_misc_dev_lock){+.+.}-{3:3}, at: isst_if_open+0x18/0x90 [isst_if_common]
    [  256.147171]
    [  256.147171] but task is already holding lock:
    [  256.153135] ffffffff8ee7cb50 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x2a/0x170
    [  256.160407]
    [  256.160407] which lock already depends on the new lock.
    [  256.160407]
    [  256.168712]
    [  256.168712] the existing dependency chain (in reverse order) is:
    [  256.176327]
    [  256.176327] -> #1 (misc_mtx){+.+.}-{3:3}:
    [  256.181946]        lock_acquire+0x1e6/0x330
    [  256.186265]        __mutex_lock+0x9b/0x9b0
    [  256.190497]        mutex_lock_nested+0x1b/0x20
    [  256.195075]        misc_register+0x32/0x1a0
    [  256.199390]        isst_if_cdev_register+0x65/0x180 [isst_if_common]
    [  256.205878]        isst_if_probe+0x144/0x16e [isst_if_mmio]
    ...
    [  256.241976]
    [  256.241976] -> #0 (punit_misc_dev_lock){+.+.}-{3:3}:
    [  256.248552]        validate_chain+0xbc6/0x1750
    [  256.253131]        __lock_acquire+0x88c/0xc10
    [  256.257618]        lock_acquire+0x1e6/0x330
    [  256.261933]        __mutex_lock+0x9b/0x9b0
    [  256.266165]        mutex_lock_nested+0x1b/0x20
    [  256.270739]        isst_if_open+0x18/0x90 [isst_if_common]
    [  256.276356]        misc_open+0x100/0x170
    [  256.280409]        chrdev_open+0xa5/0x1e0
    ...
    
    The call sequence suggested that misc_device /dev file can be opened
    before misc device is yet to be registered, which is done only once.
    
    Here punit_misc_dev_lock was used as common lock, to protect the
    registration by multiple ISST HW drivers, one time setup, prevent
    duplicate registry of misc device and prevent load/unload when device
    is open.
    
    We can split into locks:
    - One which just prevent duplicate call to misc_register() and one
    time setup. Also never call again if the misc_register() failed or
    required one time setup is failed. This lock is not shared with
    any misc device callbacks.
    
    - The other lock protects registry, load and unload of HW drivers.
    
    Sequence in isst_if_cdev_register()
    - Register callbacks under punit_misc_dev_open_lock
    - Call isst_misc_reg() which registers misc_device on the first
    registry which is under punit_misc_dev_reg_lock, which is not
    shared with callbacks.
    
    Sequence in isst_if_cdev_unregister
    Just opposite of isst_if_cdev_register
    
    Reported-and-tested-by: Liwei Song <liwei.song@windriver.com>
    Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
    Link: https://lore.kernel.org/r/20220112022521.54669-1-srinivas.pandruvada@linux.intel.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit a29012ab23163f78087a7e77719f05d201088700
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Jan 12 00:23:09 2022 +0100

    platform/x86: intel_crystal_cove_charger: Fix IRQ masking / unmasking
    
    The driver as originally submitted accidentally relied on Android having
    run before and Android having unmasked the 2nd level IRQ-mask for the
    charger IRQ. This worked since these are PMIC registers which are only
    reset when the battery is fully drained or disconnected.
    
    Fix the charger IRQ no longer working after loss of battery power by
    properly setting the 2nd level IRQ-mask for the charger IRQ.
    
    Note this removes the need to enable/disable our parent IRQ which just
    sets the mask bit in the 1st level IRQ-mask register, setting one of
    the 2 level masks is enough to stop the IRQ from getting reported.
    
    Fixes: 761db353d9e2 ("platform/x86: Add intel_crystal_cove_charger driver")
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220111232309.377642-1-hdegoede@redhat.com

commit b288420e773f5a9db77115b9cc3767a8ada16648
Author: Alexander Kobel <a-kobel@a-kobel.de>
Date:   Wed Jan 12 12:18:27 2022 +0100

    platform/x86: thinkpad_acpi: Add quirk for ThinkPads without a fan
    
    Some ThinkPad models, like the X1 Tablet 1st and 2nd Gen, are passively
    cooled without any fan.  Currently, an entry in /proc/acpi/ibm/fan is
    nevertheless created, and misleadingly shows
            status:         enabled
            speed:          65535
            level:          auto
    
    This patch adds a TPACPI_FAN_NOFAN quirk definition and corresponding
    handling to not initialize a fan interface at all.
    
    For the time being, the quirk is only applied for X1 Tablet 2nd Gen
    (types 20JB, 20JC; EC N1O...); further models (such as Gen1, types 20GG
    and 20GH) can be added easily once tested.
    
    Tested on a 20JCS00C00, BIOS N1OET58W (1.43), EC N1OHT34W.
    
    Signed-off-by: Alexander Kobel <a-kobel@a-kobel.de>
    Link: https://lore.kernel.org/r/12d4b825-a2b9-8cb7-6ed3-db4d66f46a60@a-kobel.de
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 512eb73cfd1208898cf10cb06094e0ee0bb53b58
Author: Yuka Kawajiri <yukx00@gmail.com>
Date:   Wed Jan 12 00:40:21 2022 +0900

    platform/x86: touchscreen_dmi: Add info for the RWC NANOTE P8 AY07J 2-in-1
    
    Add touchscreen info for RWC NANOTE P8 (AY07J) 2-in-1.
    
    Signed-off-by: Yuka Kawajiri <yukx00@gmail.com>
    Link: https://lore.kernel.org/r/20220111154019.4599-1-yukx00@gmail.com
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit c197e969e3082b9c19175d2f013a0dbd3ce52236
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Sat Jan 15 15:08:49 2022 +0100

    platform/surface: Reinstate platform dependency
    
    Microsoft Surface platform-specific devices are only present on
    Microsoft Surface platforms, which are currently limited to arm64 and
    x86.  Hence add a dependency on ARM64 || X86, to prevent asking the user
    about drivers for these devices when configuring a kernel for an
    architecture that does not support Microsoft Surface platforms.
    
    Fixes: 272479928172edf0 ("platform: surface: Propagate ACPI Dependency")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Maximilian Luz <luzmaximilian@gmail.com>
    Link: https://lore.kernel.org/r/20220115140849.269479-1-geert@linux-m68k.org
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 17f6736a020ef195f4855e807c76d2360310d143
Author: Lubomir Rintel <lkundrak@v3.sk>
Date:   Mon Jan 10 07:36:29 2022 +0100

    platform/x86: x86-android-tablets: Trivial typo fix for MODULE_AUTHOR
    
    Bring balance to the quoting of Hans' e-mail address.
    
    Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
    Link: https://lore.kernel.org/r/20220110063629.273364-1-lkundrak@v3.sk
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 5de2ffd5acd33368e472dd3255a51cac528c730e
Author: Lubomir Rintel <lkundrak@v3.sk>
Date:   Mon Jan 10 07:35:12 2022 +0100

    platform/x86: x86-android-tablets: Fix the buttons on CZC P10T tablet
    
    This switches the P10T tablet to "Android" mode, where the Home button
    sends a single sancode instead of a Windows-specific key combination and
    the other button doesn't disable the Wi-Fi.
    
    Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
    Link: https://lore.kernel.org/r/20220110063512.273252-1-lkundrak@v3.sk
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 442bf564eb0c4577d98a77e87caa10f704dddcad
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Jan 10 11:39:52 2022 +0100

    platform/x86: x86-android-tablets: Constify the gpiod_lookup_tables arrays
    
    The individual gpiod_lookup_table structs cannot be const because they
    contain a list-head which gets used when registering them.
    
    But the array of pointers to the gpiod_lookup_table-s used by a board
    can be const, constify these.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reviewed-By: Lubomir Rintel <lkundrak@V3.sk>
    Link: https://lore.kernel.org/r/20220110103952.48760-3-hdegoede@redhat.com

commit 84c2dcdd475f3f5d1d30c87404cafba4dd4b75ec
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Jan 10 11:39:51 2022 +0100

    platform/x86: x86-android-tablets: Add an init() callback to struct x86_dev_info
    
    Add an init() callback to struct x86_dev_info, board descriptions can use
    this to do some custom setup before registering the i2c_clients, platform-
    devices and servdevs.
    
    Also add an exit() callback to also allow for cleanup of the custom setup.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reviewed-By: Lubomir Rintel <lkundrak@V3.sk>
    Link: https://lore.kernel.org/r/20220110103952.48760-2-hdegoede@redhat.com

commit 4ce2a32d40260374dfce5344960c419fde23ce87
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Mon Jan 10 11:39:50 2022 +0100

    platform/x86: x86-android-tablets: Add support for disabling ACPI _AEI handlers
    
    Some of the broken DSDTs on these devices often also include broken / wrong
    _AEI (ACPI Event Interrupt) handlers, which can cause e.g. interrupt storms
    by listening to a floating GPIO pin.
    
    Add support for disabling these and disable them on the Asus ME176C and
    TF103C tablets.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reviewed-By: Lubomir Rintel <lkundrak@V3.sk>
    Link: https://lore.kernel.org/r/20220110103952.48760-1-hdegoede@redhat.com

commit ddec7abd4d93760ad5b2c7c61bf123a7707664ca
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Tue Jan 11 11:07:08 2022 +0100

    platform/x86: x86-android-tablets: Correct crystal_cove_charger module name
    
    The module was renamed to intel_crystal_cove_charger before it was
    merged, updated bq24190_modules to match.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220111100708.38585-1-hdegoede@redhat.com

commit 278583055a237270fac70518275ba877bf9e4013
Author: Marc Zyngier <maz@kernel.org>
Date:   Fri Jan 21 18:42:07 2022 +0000

    KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
    
    Injecting an exception into a guest with non-VHE is risky business.
    Instead of writing in the shadow register for the switch code to
    restore it, we override the CPU register instead. Which gets
    overriden a few instructions later by said restore code.
    
    The result is that although the guest correctly gets the exception,
    it will return to the original context in some random state,
    depending on what was there the first place... Boo.
    
    Fix the issue by writing to the shadow register. The original code
    is absolutely fine on VHE, as the state is already loaded, and writing
    to the shadow register in that case would actually be a bug.
    
    Fixes: bb666c472ca2 ("KVM: arm64: Inject AArch64 exceptions from HYP")
    Cc: stable@vger.kernel.org
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Fuad Tabba <tabba@google.com>
    Link: https://lore.kernel.org/r/20220121184207.423426-1-maz@kernel.org

commit 8aa0f94b0a8d5304ea1bd63bf1ed06f9e395e328
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sat Jan 22 23:35:36 2022 -0800

    gpio: sim: add doc file to index file
    
    Include the gpio-sim.rst file in the GPIO index (toc/table of contents).
    
    Quietens this doc build warning:
    
    Documentation/admin-guide/gpio/gpio-sim.rst: WARNING: document isn't included in any toctree
    
    Fixes: b48f6b466e44 ("gpio: sim: new testing module")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit dda8e14363f4f2bac0a1122322a35f47b5565d46
Author: Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Thu Jan 20 20:49:48 2022 +0100

    gpio: sim: check the label length when setting up device properties
    
    If the user-space sets the chip label to an empty string - we should
    check the length and not override the default name or else line hogs
    will not be properly attached.
    
    Fixes: cb8c474e79be ("gpio: sim: new testing module")
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit c9bb19368b3ab111aedf3297e65bf84c9d3aa005
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Fri Dec 17 14:58:49 2021 +0100

    s390: update defconfigs
    
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 90c5318795eefa09a9f9aef8d18a904e24962b5c
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date:   Wed Jan 19 19:26:38 2022 +0100

    s390/module: test loading modules with a lot of relocations
    
    Add a test in order to prevent regressions.
    
    Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit f3b7e73b2c6619884351a3a0a7468642f852b8a2
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date:   Wed Jan 19 19:26:37 2022 +0100

    s390/module: fix loading modules with a lot of relocations
    
    If the size of the PLT entries generated by apply_rela() exceeds
    64KiB, the first ones can no longer reach __jump_r1 with brc. Fix by
    using brcl. An alternative solution is to add a __jump_r1 copy after
    every 64KiB, however, the space savings are quite small and do not
    justify the additional complexity.
    
    Fixes: f19fbd5ed642 ("s390: introduce execute-trampolines for branches")
    Cc: stable@vger.kernel.org
    Reported-by: Andrea Righi <andrea.righi@canonical.com>
    Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 817b8b9c5396d2b2d92311b46719aad5d3339dbe
Author: Dongliang Mu <mudongliangabcd@gmail.com>
Date:   Sat Jan 22 17:48:26 2022 +0800

    HID: elo: fix memory leak in elo_probe
    
    When hid_parse() in elo_probe() fails, it forgets to call usb_put_dev to
    decrease the refcount.
    
    Fix this by adding usb_put_dev() in the error handling code of elo_probe().
    
    Fixes: fbf42729d0e9 ("HID: elo: update the reference count of the usb device structure")
    Reported-by: syzkaller <syzkaller@googlegroups.com>
    Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit fb6433b48a178d4672cb26632454ee0b21056eaa
Author: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Date:   Sat Jan 22 09:04:29 2022 +0530

    powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending
    
    Running selftest with CONFIG_PPC_IRQ_SOFT_MASK_DEBUG enabled in kernel
    triggered below warning:
    
    [  172.851380] ------------[ cut here ]------------
    [  172.851391] WARNING: CPU: 8 PID: 2901 at arch/powerpc/include/asm/hw_irq.h:246 power_pmu_disable+0x270/0x280
    [  172.851402] Modules linked in: dm_mod bonding nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables rfkill nfnetlink sunrpc xfs libcrc32c pseries_rng xts vmx_crypto uio_pdrv_genirq uio sch_fq_codel ip_tables ext4 mbcache jbd2 sd_mod t10_pi sg ibmvscsi ibmveth scsi_transport_srp fuse
    [  172.851442] CPU: 8 PID: 2901 Comm: lost_exception_ Not tainted 5.16.0-rc5-03218-g798527287598 #2
    [  172.851451] NIP:  c00000000013d600 LR: c00000000013d5a4 CTR: c00000000013b180
    [  172.851458] REGS: c000000017687860 TRAP: 0700   Not tainted  (5.16.0-rc5-03218-g798527287598)
    [  172.851465] MSR:  8000000000029033 <SF,EE,ME,IR,DR,RI,LE>  CR: 48004884  XER: 20040000
    [  172.851482] CFAR: c00000000013d5b4 IRQMASK: 1
    [  172.851482] GPR00: c00000000013d5a4 c000000017687b00 c000000002a10600 0000000000000004
    [  172.851482] GPR04: 0000000082004000 c0000008ba08f0a8 0000000000000000 00000008b7ed0000
    [  172.851482] GPR08: 00000000446194f6 0000000000008000 c00000000013b118 c000000000d58e68
    [  172.851482] GPR12: c00000000013d390 c00000001ec54a80 0000000000000000 0000000000000000
    [  172.851482] GPR16: 0000000000000000 0000000000000000 c000000015d5c708 c0000000025396d0
    [  172.851482] GPR20: 0000000000000000 0000000000000000 c00000000a3bbf40 0000000000000003
    [  172.851482] GPR24: 0000000000000000 c0000008ba097400 c0000000161e0d00 c00000000a3bb600
    [  172.851482] GPR28: c000000015d5c700 0000000000000001 0000000082384090 c0000008ba0020d8
    [  172.851549] NIP [c00000000013d600] power_pmu_disable+0x270/0x280
    [  172.851557] LR [c00000000013d5a4] power_pmu_disable+0x214/0x280
    [  172.851565] Call Trace:
    [  172.851568] [c000000017687b00] [c00000000013d5a4] power_pmu_disable+0x214/0x280 (unreliable)
    [  172.851579] [c000000017687b40] [c0000000003403ac] perf_pmu_disable+0x4c/0x60
    [  172.851588] [c000000017687b60] [c0000000003445e4] __perf_event_task_sched_out+0x1d4/0x660
    [  172.851596] [c000000017687c50] [c000000000d1175c] __schedule+0xbcc/0x12a0
    [  172.851602] [c000000017687d60] [c000000000d11ea8] schedule+0x78/0x140
    [  172.851608] [c000000017687d90] [c0000000001a8080] sys_sched_yield+0x20/0x40
    [  172.851615] [c000000017687db0] [c0000000000334dc] system_call_exception+0x18c/0x380
    [  172.851622] [c000000017687e10] [c00000000000c74c] system_call_common+0xec/0x268
    
    The warning indicates that MSR_EE being set(interrupt enabled) when
    there was an overflown PMC detected. This could happen in
    power_pmu_disable since it runs under interrupt soft disable
    condition ( local_irq_save ) and not with interrupts hard disabled.
    commit 2c9ac51b850d ("powerpc/perf: Fix PMU callbacks to clear
    pending PMI before resetting an overflown PMC") intended to clear
    PMI pending bit in Paca when disabling the PMU. It could happen
    that PMC gets overflown while code is in power_pmu_disable
    callback function. Hence add a check to see if PMI pending bit
    is set in Paca before clearing it via clear_pmi_pending.
    
    Fixes: 2c9ac51b850d ("powerpc/perf: Fix PMU callbacks to clear pending PMI before resetting an overflown PMC")
    Reported-by: Sachin Sant <sachinp@linux.ibm.com>
    Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220122033429.25395-1-atrajeev@linux.vnet.ibm.com

commit aec982603aa8cc0a21143681feb5f60ecc69d718
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Mon Dec 6 11:11:51 2021 +0000

    powerpc/fixmap: Fix VM debug warning on unmap
    
    Unmapping a fixmap entry is done by calling __set_fixmap()
    with FIXMAP_PAGE_CLEAR as flags.
    
    Today, powerpc __set_fixmap() calls map_kernel_page().
    
    map_kernel_page() is not happy when called a second time
    for the same page.
    
            WARNING: CPU: 0 PID: 1 at arch/powerpc/mm/pgtable.c:194 set_pte_at+0xc/0x1e8
            CPU: 0 PID: 1 Comm: swapper Not tainted 5.16.0-rc3-s3k-dev-01993-g350ff07feb7d-dirty #682
            NIP:  c0017cd4 LR: c00187f0 CTR: 00000010
            REGS: e1011d50 TRAP: 0700   Not tainted  (5.16.0-rc3-s3k-dev-01993-g350ff07feb7d-dirty)
            MSR:  00029032 <EE,ME,IR,DR,RI>  CR: 42000208  XER: 00000000
    
            GPR00: c0165fec e1011e10 c14c0000 c0ee2550 ff800000 c0f3d000 00000000 c001686c
            GPR08: 00001000 b00045a9 00000001 c0f58460 c0f50000 00000000 c0007e10 00000000
            GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
            GPR24: 00000000 00000000 c0ee2550 00000000 c0f57000 00000ff8 00000000 ff800000
            NIP [c0017cd4] set_pte_at+0xc/0x1e8
            LR [c00187f0] map_kernel_page+0x9c/0x100
            Call Trace:
            [e1011e10] [c0736c68] vsnprintf+0x358/0x6c8 (unreliable)
            [e1011e30] [c0165fec] __set_fixmap+0x30/0x44
            [e1011e40] [c0c13bdc] early_iounmap+0x11c/0x170
            [e1011e70] [c0c06cb0] ioremap_legacy_serial_console+0x88/0xc0
            [e1011e90] [c0c03634] do_one_initcall+0x80/0x178
            [e1011ef0] [c0c0385c] kernel_init_freeable+0xb4/0x250
            [e1011f20] [c0007e34] kernel_init+0x24/0x140
            [e1011f30] [c0016268] ret_from_kernel_thread+0x5c/0x64
            Instruction dump:
            7fe3fb78 48019689 80010014 7c630034 83e1000c 5463d97e 7c0803a6 38210010
            4e800020 81250000 712a0001 41820008 <0fe00000> 9421ffe0 93e1001c 48000030
    
    Implement unmap_kernel_page() which clears an existing pte.
    
    Reported-by: Maxime Bizon <mbizon@freebox.fr>
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Tested-by: Maxime Bizon <mbizon@freebox.fr>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/b0b752f6f6ecc60653e873f385c6f0dce4e9ab6a.1638789098.git.christophe.leroy@csgroup.eu

commit 29afbd769ca338fa14cbfbbc824f7dc457ed7f2e
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Sat Jan 15 14:51:46 2022 +0300

    phy: cadence: Sierra: fix error handling bugs in probe()
    
    There are two bugs in the error handling:
    1: If devm_of_phy_provider_register() fails then there was no cleanup.
    2: The error handling called of_node_put(child) improperly leading to
       a use after free.  We are only holding the reference inside the loop
       so the last two gotos after the loop lead to a use after free bug.
       Fix this by cleaning up the partial allocations (or partial iterations)
       in the loop before doing the goto.
    
    Fixes: a43f72ae136a ("phy: cadence: Sierra: Change MAX_LANES of Sierra to 16")
    Fixes: 44d30d622821 ("phy: cadence: Add driver for Sierra PHY")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220115115146.GC7552@kili
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 6d1e6bcb31663ee83aaea1f171f3dbfe95dd4a69
Author: Kishon Vijay Abraham I <kishon@ti.com>
Date:   Mon Jan 17 16:31:08 2022 +0530

    phy: ti: Fix missing sentinel for clk_div_table
    
    _get_table_maxdiv() tries to access "clk_div_table" array out of bound
    defined in phy-j721e-wiz.c. Add a sentinel entry to prevent
    the following global-out-of-bounds error reported by enabling KASAN.
    
    [    9.552392] BUG: KASAN: global-out-of-bounds in _get_maxdiv+0xc0/0x148
    [    9.558948] Read of size 4 at addr ffff8000095b25a4 by task kworker/u4:1/38
    [    9.565926]
    [    9.567441] CPU: 1 PID: 38 Comm: kworker/u4:1 Not tainted 5.16.0-116492-gdaadb3bd0e8d-dirty #360
    [    9.576242] Hardware name: Texas Instruments J721e EVM (DT)
    [    9.581832] Workqueue: events_unbound deferred_probe_work_func
    [    9.587708] Call trace:
    [    9.590174]  dump_backtrace+0x20c/0x218
    [    9.594038]  show_stack+0x18/0x68
    [    9.597375]  dump_stack_lvl+0x9c/0xd8
    [    9.601062]  print_address_description.constprop.0+0x78/0x334
    [    9.606830]  kasan_report+0x1f0/0x260
    [    9.610517]  __asan_load4+0x9c/0xd8
    [    9.614030]  _get_maxdiv+0xc0/0x148
    [    9.617540]  divider_determine_rate+0x88/0x488
    [    9.622005]  divider_round_rate_parent+0xc8/0x124
    [    9.626729]  wiz_clk_div_round_rate+0x54/0x68
    [    9.631113]  clk_core_determine_round_nolock+0x124/0x158
    [    9.636448]  clk_core_round_rate_nolock+0x68/0x138
    [    9.641260]  clk_core_set_rate_nolock+0x268/0x3a8
    [    9.645987]  clk_set_rate+0x50/0xa8
    [    9.649499]  cdns_sierra_phy_init+0x88/0x248
    [    9.653794]  phy_init+0x98/0x108
    [    9.657046]  cdns_pcie_enable_phy+0xa0/0x170
    [    9.661340]  cdns_pcie_init_phy+0x250/0x2b0
    [    9.665546]  j721e_pcie_probe+0x4b8/0x798
    [    9.669579]  platform_probe+0x8c/0x108
    [    9.673350]  really_probe+0x114/0x630
    [    9.677037]  __driver_probe_device+0x18c/0x220
    [    9.681505]  driver_probe_device+0xac/0x150
    [    9.685712]  __device_attach_driver+0xec/0x170
    [    9.690178]  bus_for_each_drv+0xf0/0x158
    [    9.694124]  __device_attach+0x184/0x210
    [    9.698070]  device_initial_probe+0x14/0x20
    [    9.702277]  bus_probe_device+0xec/0x100
    [    9.706223]  deferred_probe_work_func+0x124/0x180
    [    9.710951]  process_one_work+0x4b0/0xbc0
    [    9.714983]  worker_thread+0x74/0x5d0
    [    9.718668]  kthread+0x214/0x230
    [    9.721919]  ret_from_fork+0x10/0x20
    [    9.725520]
    [    9.727032] The buggy address belongs to the variable:
    [    9.732183]  clk_div_table+0x24/0x440
    
    Fixes: 091876cc355d ("phy: ti: j721e-wiz: Add support for WIZ module present in TI J721E SoC")
    Cc: stable@vger.kernel.org # v5.10+
    Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
    Link: https://lore.kernel.org/r/20220117110108.4117-1-kishon@ti.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit c1ec0cabc36718efc7fe8b4157d41b82d08ec1d2
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 21 14:55:43 2022 +0300

    hwmon: (adt7470) Prevent divide by zero in adt7470_fan_write()
    
    The "val" variable is controlled by the user and comes from
    hwmon_attr_store().  The FAN_RPM_TO_PERIOD() macro divides by "val"
    so a zero will crash the system.  Check for that and return -EINVAL.
    Negatives are also invalid so return -EINVAL for those too.
    
    Fixes: fc958a61ff6d ("hwmon: (adt7470) Convert to devm_hwmon_device_register_with_info API")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit f1e75e0d6a1ae02fa4189d7aeebab623bade2a21
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Tue Jan 18 07:53:19 2022 -0800

    hwmon: (pmbus/ir38064) Mark ir38064_of_match as __maybe_unused
    
    If CONFIG_PM is not enabled, the following warning is reported.
    
    drivers/hwmon/pmbus/ir38064.c:54:34: warning:
            unused variable 'ir38064_of_match'
    
    Mark it as __maybe_unused.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Arthur Heymans <arthur.heymans@9elements.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit d379880d9adb9f1ada3f1266aa49ea2561328e08
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Mon Jan 10 23:23:31 2022 -0800

    hwmon: (lm90) Fix sysfs and udev notifications
    
    sysfs and udev notifications need to be sent to the _alarm
    attributes, not to the value attributes.
    
    Fixes: 94dbd23ed88c ("hwmon: (lm90) Use hwmon_notify_event()")
    Cc: Dmitry Osipenko <digetx@gmail.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit f614629f9c1080dcc844a8430e3fb4c37ebbf05d
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Fri Jan 7 12:36:41 2022 -0800

    hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649
    
    Experiments with MAX6646 and MAX6648 show that the alert function of those
    chips is broken, similar to other chips supported by the lm90 driver.
    Mark it accordingly.
    
    Fixes: 4667bcb8d8fc ("hwmon: (lm90) Introduce chip parameter structure")
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit 94746b0ba479743355e0d3cc1cb9cfe3011fb8be
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Fri Jan 7 11:11:00 2022 -0800

    hwmon: (lm90) Mark alert as broken for MAX6680
    
    Experiments with MAX6680 and MAX6681 show that the alert function of those
    chips is broken, similar to other chips supported by the lm90 driver.
    Mark it accordingly.
    
    Fixes: 4667bcb8d8fc ("hwmon: (lm90) Introduce chip parameter structure")
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit a53fff96f35763d132a36c620b183fdf11022d7a
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Fri Jan 7 11:05:23 2022 -0800

    hwmon: (lm90) Mark alert as broken for MAX6654
    
    Experiments with MAX6654 show that its alert function is broken,
    similar to other chips supported by the lm90 driver. Mark it accordingly.
    
    Fixes: 229d495d8189 ("hwmon: (lm90) Add max6654 support to lm90 driver")
    Cc: Josh Lehan <krellan@google.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit bc341a1a98827925082e95db174734fc8bd68af6
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Sat Jan 8 11:37:19 2022 -0800

    hwmon: (lm90) Re-enable interrupts after alert clears
    
    If alert handling is broken, interrupts are disabled after an alert and
    re-enabled after the alert clears. However, if there is an interrupt
    handler, this does not apply if alerts were originally disabled and enabled
    when the driver was loaded. In that case, interrupts will stay disabled
    after an alert was handled though the alert handler even after the alert
    condition clears. Address the situation by always re-enabling interrupts
    after the alert condition clears if there is an interrupt handler.
    
    Fixes: 2abdc357c55d9 ("hwmon: (lm90) Unmask hardware interrupt")
    Cc: Dmitry Osipenko <digetx@gmail.com>
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit a66c5ed539277b9f2363bbace0dba88b85b36c26
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Thu Jan 6 11:48:52 2022 -0800

    hwmon: (lm90) Reduce maximum conversion rate for G781
    
    According to its datasheet, G781 supports a maximum conversion rate value
    of 8 (62.5 ms). However, chips labeled G781 and G780 were found to only
    support a maximum conversion rate value of 7 (125 ms). On the other side,
    chips labeled G781-1 and G784 were found to support a conversion rate value
    of 8. There is no known means to distinguish G780 from G781 or G784; all
    chips report the same manufacturer ID and chip revision.
    Setting the conversion rate register value to 8 on chips not supporting
    it causes unexpected behavior since the real conversion rate is set to 0
    (16 seconds) if a value of 8 is written into the conversion rate register.
    Limit the conversion rate register value to 7 for all G78x chips to avoid
    the problem.
    
    Fixes: ae544f64cc7b ("hwmon: (lm90) Add support for GMT G781")
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit 9ca8581e79e51c57e60b3b8e3b89d816448f49fe
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Sat Jan 22 10:47:22 2022 +0900

    ksmbd: fix SMB 3.11 posix extension mount failure
    
    cifs client set 4 to DataLength of create_posix context, which mean
    Mode variable of create_posix context is only available. So buffer
    validation of ksmbd should check only the size of Mode except for
    the size of Reserved variable.
    
    Fixes: 8f77150c15f8 ("ksmbd: add buffer validation for SMB2_CREATE_CONTEXT")
    Cc: stable@vger.kernel.org # v5.15+
    Reported-by: Steve French <smfrench@gmail.com>
    Tested-by: Steve French <stfrench@microsoft.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 1fd6bb5b47a65eacb063b37e6fa6df2b8fa92959
Author: Andre Przywara <andre.przywara@arm.com>
Date:   Wed Jan 5 17:29:52 2022 +0000

    pinctrl: sunxi: Fix H616 I2S3 pin data
    
    Two bugs have sneaked in the H616 pinctrl data:
    - PH9 uses the mux value of 0x3 twice (one should be 0x5 instead)
    - PH8 and PH9 use the "i2s3" function name twice in each pin
    
    For the double pin name we use the same trick we pulled for i2s0: append
    the pin function to the group name to designate the special function.
    
    Fixes: 25adc29407fb ("pinctrl: sunxi: Add support for the Allwinner H616 pin controller")
    Reported-by: SASANO Takayoshi <uaa@mx5.nisiq.net>
    Signed-off-by: Andre Przywara <andre.przywara@arm.com>
    Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
    Reviewed-by: Samuel Holland <samuel@sholland.org>
    Link: https://lore.kernel.org/r/20220105172952.23347-1-andre.przywara@arm.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit aa28514592d52043f4837a6457d6310452135ae1
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Tue Jan 4 17:42:38 2022 +0100

    pinctrl: cherryview: Trigger hwirq0 for interrupt-lines without a mapping
    
    Commit bdfbef2d29dc ("pinctrl: cherryview: Don't use selection 0 to mark
    an interrupt line as unused") made the code properly differentiate
    between unset vs (hwirq) 0 entries in the GPIO-controller interrupt-line
    to GPIO pinnumber/hwirq mapping.
    
    This is causing some boards to not boot. This commit restores the old
    behavior of triggering hwirq 0 when receiving an interrupt on an
    interrupt-line for which there is no mapping.
    
    Fixes: bdfbef2d29dc ("pinctrl: cherryview: Don't use selection 0 to mark an interrupt line as unused")
    Reported-and-tested-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Link: https://lore.kernel.org/r/20220104164238.253142-1-hdegoede@redhat.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 25d2e41cf59bd6ccd23adc2965a157053bc3ed5c
Author: Rafał Miłecki <rafal@milecki.pl>
Date:   Tue Jan 11 18:29:19 2022 +0100

    pinctrl: thunderbay: rework loops looking for groups names
    
    Make the outer loop iterate over functions as that's the real subject.
    This simplifies code (and reduces amount of lines of code) as allocating
    memory for names doesn't require extra checks anymore.
    
    While at it use local "group_names" variable. It fixes:
    drivers/pinctrl/pinctrl-thunderbay.c: In function 'thunderbay_add_functions':
    drivers/pinctrl/pinctrl-thunderbay.c:815:8: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
      815 |    grp = func->group_names;
          |        ^
    
    Ref: c26c4bfc1040 ("pinctrl: keembay: rework loops looking for groups names")
    Reported-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
    Link: https://lore.kernel.org/r/20220111172919.6567-2-zajec5@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 30cc53897470d45219fb0a5eafd0cc8b0032cd1e
Author: Rafał Miłecki <rafal@milecki.pl>
Date:   Tue Jan 11 18:29:18 2022 +0100

    pinctrl: thunderbay: comment process of building functions a bit
    
    This should make code a bit easier to follow. While at it use some "for"
    loops to simplify array iteration loops.
    
    Ref: 5d0674999cc5 ("pinctrl: keembay: comment process of building functions a bit")
    Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
    Link: https://lore.kernel.org/r/20220111172919.6567-1-zajec5@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

commit 96d9d1fa5cd505078534113308ced0aa56d8da58
Author: Yanming Liu <yanminglr@gmail.com>
Date:   Thu Jan 20 04:20:52 2022 +0800

    Drivers: hv: balloon: account for vmbus packet header in max_pkt_size
    
    Commit adae1e931acd ("Drivers: hv: vmbus: Copy packets sent by Hyper-V
    out of the ring buffer") introduced a notion of maximum packet size in
    vmbus channel and used that size to initialize a buffer holding all
    incoming packet along with their vmbus packet header. hv_balloon uses
    the default maximum packet size VMBUS_DEFAULT_MAX_PKT_SIZE which matches
    its maximum message size, however vmbus_open expects this size to also
    include vmbus packet header. This leads to 4096 bytes
    dm_unballoon_request messages being truncated to 4080 bytes. When the
    driver tries to read next packet it starts from a wrong read_index,
    receives garbage and prints a lot of "Unhandled message: type:
    <garbage>" in dmesg.
    
    Allocate the buffer with HV_HYP_PAGE_SIZE more bytes to make room for
    the header.
    
    Fixes: adae1e931acd ("Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer")
    Suggested-by: Michael Kelley (LINUX) <mikelley@microsoft.com>
    Suggested-by: Andrea Parri (Microsoft) <parri.andrea@gmail.com>
    Signed-off-by: Yanming Liu <yanminglr@gmail.com>
    Reviewed-by: Michael Kelley <mikelley@microsoft.com>
    Reviewed-by: Andrea Parri (Microsoft) <parri.andrea@gmail.com>
    Link: https://lore.kernel.org/r/20220119202052.3006981-1-yanminglr@gmail.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit 305325688ff924c52a6e12f92235a89536e022cf
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
Date:   Thu Jan 20 17:02:47 2022 -0600

    NTB/msi: Use struct_size() helper in devm_kzalloc()
    
    Make use of the struct_size() helper instead of an open-coded version,
    in order to avoid any potential type mistakes or integer overflows that,
    in the worst scenario, could lead to heap overflows.
    
    Also, address the following sparse warnings:
    drivers/ntb/msi.c:46:23: warning: using sizeof on a flexible structure
    
    Link: https://github.com/KSPP/linux/issues/174
    Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 1f52b0aba6fd37653416375cb8a1ca673acf8d5f
Author: Yazen Ghannam <yazen.ghannam@amd.com>
Date:   Mon Jan 17 16:13:28 2022 +0000

    x86/MCE/AMD: Allow thresholding interface updates after init
    
    Changes to the AMD Thresholding sysfs code prevents sysfs writes from
    updating the underlying registers once CPU init is completed, i.e.
    "threshold_banks" is set.
    
    Allow the registers to be updated if the thresholding interface is
    already initialized or if in the init path. Use the "set_lvt_off" value
    to indicate if running in the init path, since this value is only set
    during init.
    
    Fixes: a037f3ca0ea0 ("x86/mce/amd: Make threshold bank setting hotplug robust")
    Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20220117161328.19148-1-yazen.ghannam@amd.com

commit ccbed9d8d2a5351d8238f2d3f0741c9a3176f752
Author: Sean Nyekjaer <sean@geanix.com>
Date:   Mon Dec 20 13:51:43 2021 +0100

    iio: accel: fxls8962af: add padding to regmap for SPI
    
    Add missing don't care padding between address and
    data for SPI transfers
    
    Fixes: a3e0b51884ee ("iio: accel: add support for FXLS8962AF/FXLS8964AF accelerometers")
    Signed-off-by: Sean Nyekjaer <sean@geanix.com>
    Link: https://lore.kernel.org/r/20211220125144.3630539-1-sean@geanix.com
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit b0e85f95e30d4d2dc22ea123a30dba36406879a1
Author: Nuno Sá <nuno.sa@analog.com>
Date:   Fri Jan 14 14:26:08 2022 +0100

    iio:imu:adis16480: fix buffering for devices with no burst mode
    
    The trigger handler defined in the driver assumes that burst mode is
    being used. Hence, for devices that do not support it, we have to use
    the adis library default trigger implementation.
    
    Tested-by: Julia Pineda <julia.pineda@analog.com>
    Fixes: 941f130881fa9 ("iio: adis16480: support burst read function")
    Signed-off-by: Nuno Sá <nuno.sa@analog.com>
    Link: https://lore.kernel.org/r/20220114132608.241-1-nuno.sa@analog.com
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 0e33d15f1dce9e3a80a970ea7f0b27837168aeca
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Wed Jan 12 22:00:36 2022 +0200

    iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
    
    According to page 90 of the datasheet [1], AIN_BUFP is bit 6 and
    AIN_BUFM is bit 5 of the CONFIG_0 -> CONFIG_7 registers.
    
    Fix the mask used for setting these bits.
    
    [1]: https://www.analog.com/media/en/technical-documentation/data-sheets/ad7124-8.pdf
    
    Fixes: 0eaecea6e487 ("iio: adc: ad7124: Add buffered input support")
    Signed-off-by: Cosmin Tanislav <cosmin.tanislav@analog.com>
    Link: https://lore.kernel.org/r/20220112200036.694490-1-cosmin.tanislav@analog.com
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit b7a78a8adaa8849c02f174d707aead0f85dca0da
Author: Oleksij Rempel <linux@rempel-privat.de>
Date:   Fri Jan 7 09:14:01 2022 +0100

    iio: adc: tsc2046: fix memory corruption by preventing array overflow
    
    On one side we have indio_dev->num_channels includes all physical channels +
    timestamp channel. On other side we have an array allocated only for
    physical channels. So, fix memory corruption by ARRAY_SIZE() instead of
    num_channels variable.
    
    Note the first case is a cleanup rather than a fix as the software
    timestamp channel bit in active_scanmask is never set by the IIO core.
    
    Fixes: 9374e8f5a38d ("iio: adc: add ADC driver for the TI TSC2046 controller")
    Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
    Link: https://lore.kernel.org/r/20220107081401.2816357-1-o.rempel@pengutronix.de
    Cc: <Stable@vger.kernel.org>
    Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

commit 442b0c08db7e35980bed6af091877f4dda72ffca
Author: Sam Protsenko <semen.protsenko@linaro.org>
Date:   Fri Jan 14 16:46:06 2022 +0200

    soc: samsung: Fix typo in CONFIG_EXYNOS_USI description
    
    The proper name is Exynos Auto V9, not V0. It was the typo slipped in
    unnoticed, fix it.
    
    Fixes: b603377e408f ("soc: samsung: Add USI driver")
    Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
    Reviewed-by: Chanho Park <chanho61.park@samsung.com>
    Link: https://lore.kernel.org/r/20220114144606.24358-1-semen.protsenko@linaro.org
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>

commit 94bfe2bdfc5059a0870447ccf2c8048f3d016898
Author: Alim Akhtar <alim.akhtar@samsung.com>
Date:   Wed Jan 5 22:13:41 2022 +0530

    MAINTAINERS: add reviewer entry for Samsung/Exynos platform
    
    Adds myself as reviewer for Samsung/Exynos platform to help
    in review of current and upcoming SoCs patches.
    
    Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
    Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
    Link: https://lore.kernel.org/r/20220105164341.27479-1-alim.akhtar@samsung.com
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>

commit 83114df32ae779df57e0af99a8ba6c3968b2ba3d
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Jan 20 10:10:25 2022 +0000

    block: fix memory leak in disk_register_independent_access_ranges
    
    kobject_init_and_add() takes reference even when it fails.
    According to the doc of kobject_init_and_add()
    
       If this function returns an error, kobject_put() must be called to
       properly clean up the memory associated with the object.
    
    Fix this issue by adding kobject_put().
    Callback function blk_ia_ranges_sysfs_release() in kobject_put()
    can handle the pointer "iars" properly.
    
    Fixes: a2247f19ee1c ("block: Add independent access ranges support")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Link: https://lore.kernel.org/r/20220120101025.22411-1-linmq006@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit b36a2050040b2d839bdc044007cdd57101d7f881
Author: Dylan Yudaken <dylany@fb.com>
Date:   Fri Jan 21 04:38:56 2022 -0800

    io_uring: fix bug in slow unregistering of nodes
    
    In some cases io_rsrc_ref_quiesce will call io_rsrc_node_switch_start,
    and then immediately flush the delayed work queue &ctx->rsrc_put_work.
    
    However the percpu_ref_put does not immediately destroy the node, it
    will be called asynchronously via RCU. That ends up with
    io_rsrc_node_ref_zero only being called after rsrc_put_work has been
    flushed, and so the process ends up sleeping for 1 second unnecessarily.
    
    This patch executes the put code immediately if we are busy
    quiescing.
    
    Fixes: 4a38aed2a0a7 ("io_uring: batch reap of dead file registrations")
    Signed-off-by: Dylan Yudaken <dylany@fb.com>
    Link: https://lore.kernel.org/r/20220121123856.3557884-1-dylany@fb.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit dd81e1c7d5fb126e5fbc5c9e334d7b3ec29a16a0
Merge: ac5a9bb6b4fa2 aee101d7b95a0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 17:52:42 2022 +0200

    Merge tag 'powerpc-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc fixes from Michael Ellerman:
    
     - A series of bpf fixes, including an oops fix and some codegen fixes.
    
     - Fix a regression in syscall_get_arch() for compat processes.
    
     - Fix boot failure on some 32-bit systems with KASAN enabled.
    
     - A couple of other build/minor fixes.
    
    Thanks to Athira Rajeev, Christophe Leroy, Dmitry V. Levin, Jiri Olsa,
    Johan Almbladh, Maxime Bizon, Naveen N. Rao, and Nicholas Piggin.
    
    * tag 'powerpc-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
      powerpc/64s: Mask SRR0 before checking against the masked NIP
      powerpc/perf: Only define power_pmu_wants_prompt_pmi() for CONFIG_PPC64
      powerpc/32s: Fix kasan_init_region() for KASAN
      powerpc/time: Fix build failure due to do_hard_irq_enable() on PPC32
      powerpc/audit: Fix syscall_get_arch()
      powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06
      tools/bpf: Rename 'struct event' to avoid naming conflict
      powerpc/bpf: Update ldimm64 instructions during extra pass
      powerpc32/bpf: Fix codegen for bpf-to-bpf calls
      bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()

commit ac5a9bb6b4fa22135b3e371ac9787de120e18c8d
Merge: 10c64a0f28063 a0af3d1104f75
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 17:45:00 2022 +0200

    Merge tag 'irq_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq fix from Borislav Petkov:
     "A single use-after-free fix in the PCI MSI irq domain allocation path"
    
    * tag 'irq_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      PCI/MSI: Prevent UAF in error path

commit 10c64a0f280636652ec63bb1ddd34b6c8e2f5584
Merge: 0f9e042212273 0e3872499de1a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 17:35:27 2022 +0200

    Merge tag 'sched_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull scheduler fixes from Borislav Petkov:
     "A bunch of fixes: forced idle time accounting, utilization values
      propagation in the sched hierarchies and other minor cleanups and
      improvements"
    
    * tag 'sched_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      kernel/sched: Remove dl_boosted flag comment
      sched: Avoid double preemption in __cond_resched_*lock*()
      sched/fair: Fix all kernel-doc warnings
      sched/core: Accounting forceidle time for all tasks except idle task
      sched/pelt: Relax the sync of load_sum with load_avg
      sched/pelt: Relax the sync of runnable_sum with runnable_avg
      sched/pelt: Continue to relax the sync of util_sum with util_avg
      sched/pelt: Relax the sync of util_sum with util_avg
      psi: Fix uaf issue when psi trigger is destroyed while being polled

commit 0f9e04221227302d665bf64c69e5308360f4f88a
Merge: e783362eb54cd 8c16dc047b5dd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 17:31:24 2022 +0200

    Merge tag 'perf_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull perf fixes from Borislav Petkov:
    
     - Add support for accessing the general purpose counters on Alder Lake
       via MMIO
    
     - Add new LBR format v7 support which is v5 modulo TSX
    
     - Fix counter enumeration on Alder Lake hybrids
    
     - Overhaul how context time updates are done and get rid of
       perf_event::shadow_ctx_time.
    
     - The usual amount of fixes: event mask correction, supported event
       types reporting, etc.
    
    * tag 'perf_urgent_for_v5.17_rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/perf: Avoid warning for Arch LBR without XSAVE
      perf/x86/intel/uncore: Add IMC uncore support for ADL
      perf/x86/intel/lbr: Add static_branch for LBR INFO flags
      perf/x86/intel/lbr: Support LBR format V7
      perf/x86/rapl: fix AMD event handling
      perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
      perf/x86/intel: Add a quirk for the calculation of the number of counters on Alder Lake
      perf: Fix perf_event_read_local() time

commit b5fbaf7d779f5f02b7f75b080e7707222573be2a
Author: Brian Norris <briannorris@chromium.org>
Date:   Fri Jan 14 15:02:07 2022 -0800

    arm64: dts: rockchip: Switch RK3399-Gru DP to SPDIF output
    
    Commit b18c6c3c7768 ("ASoC: rockchip: cdn-dp sound output use spdif")
    switched the platform to SPDIF, but we didn't fix up the device tree.
    
    Drop the pinctrl settings, because the 'spdif_bus' pins are either:
     * unused (on kevin, bob), so the settings is ~harmless
     * used by a different function (on scarlet), which causes probe
       failures (!!)
    
    Fixes: b18c6c3c7768 ("ASoC: rockchip: cdn-dp sound output use spdif")
    Signed-off-by: Brian Norris <briannorris@chromium.org>
    Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
    Link: https://lore.kernel.org/r/20220114150129.v2.1.I46f64b00508d9dff34abe1c3e8d2defdab4ea1e5@changeid
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit ed2c66a95c0c5669880aa93d0d34c6e9694b4cbd
Author: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Date:   Thu Jan 20 13:51:56 2022 +0100

    arm64: dts: rockchip: fix rk3399-puma-haikou USB OTG mode
    
    The micro USB3.0 port available on the Haikou evaluation kit for Puma
    RK3399-Q7 SoM supports dual-role model (aka drd or OTG) but its support
    was broken until now because of missing logic around the ID pin.
    
    This adds proper support for USB OTG on Puma Haikou by "connecting" the
    GPIO used for USB ID to the USB3 controller device.
    
    Cc: Quentin Schulz <foss+kernel@0leil.net>
    Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
    Link: https://lore.kernel.org/r/20220120125156.16217-1-quentin.schulz@theobroma-systems.com
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit 5070ce86246a8a4ebacd0c15b121e6b6325bc167
Author: Al Cooper <alcooperx@gmail.com>
Date:   Wed Dec 1 13:06:53 2021 -0500

    phy: broadcom: Kconfig: Fix PHY_BRCM_USB config option
    
    The previous commit 4b402fa8e0b7 ("phy: phy-brcm-usb: support PHY on
    the BCM4908") added a second "default" line for ARCH_BCM_4908 above
    the original "default" line for ARCH_BRCMSTB. When two "default"
    lines are used, only the first is used and this change stopped
    the PHY_BRCM_USB option for being enabled for ARCH_BRCMSTB.
    The fix is to use one "default line with "||".
    
    Fixes: 4b402fa8e0b7 ("phy: phy-brcm-usb: support PHY on the BCM4908")
    Signed-off-by: Al Cooper <alcooperx@gmail.com>
    Acked-by: Rafał Miłecki <rafal@milecki.pl>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20211201180653.35097-4-alcooperx@gmail.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 42fed57046fc74586d7058bd51a1c10ac9c690cb
Author: Al Cooper <alcooperx@gmail.com>
Date:   Wed Dec 1 13:06:51 2021 -0500

    phy: usb: Leave some clocks running during suspend
    
    The PHY client driver does a phy_exit() call on suspend or rmmod and
    the PHY driver needs to know the difference because some clocks need
    to be kept running for suspend but can be shutdown on unbind/rmmod
    (or if there are no PHY clients at all).
    
    The fix is to use a PM notifier so the driver can tell if a PHY
    client is calling exit() because of a system suspend or a driver
    unbind/rmmod.
    
    Signed-off-by: Al Cooper <alcooperx@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20211201180653.35097-2-alcooperx@gmail.com
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 85a8bccfa945680dc561f06b65ea01341d2033fc
Author: Frank Wunderlich <frank-w@public-files.de>
Date:   Sun Jan 23 14:35:10 2022 +0100

    arm64: dts: rockchip: drop pclk_xpcs from gmac0 on rk3568
    
    pclk_xpcs is not supported by mainline driver and breaks dtbs_check
    
    following warnings occour, and many more
    
    rk3568-evb1-v10.dt.yaml: ethernet@fe2a0000: clocks:
        [[15, 386], [15, 389], [15, 389], [15, 184], [15, 180], [15, 181],
        [15, 389], [15, 185], [15, 172]] is too long
            From schema: Documentation/devicetree/bindings/net/snps,dwmac.yaml
    rk3568-evb1-v10.dt.yaml: ethernet@fe2a0000: clock-names:
        ['stmmaceth', 'mac_clk_rx', 'mac_clk_tx', 'clk_mac_refout', 'aclk_mac',
        'pclk_mac', 'clk_mac_speed', 'ptp_ref', 'pclk_xpcs'] is too long
            From schema: Documentation/devicetree/bindings/net/snps,dwmac.yaml
    
    after removing it, the clock and other warnings are gone.
    
    pclk_xpcs on gmac is used to support QSGMII, but this requires a driver
    supporting it.
    Once xpcs support is introduced, the clock can be added to the
    documentation and both controllers.
    
    Fixes: b8d41e5053cd ("arm64: dts: rockchip: add gmac0 node to rk3568")
    Co-developed-by: Peter Geis <pgwipeout@gmail.com>
    Signed-off-by: Peter Geis <pgwipeout@gmail.com>
    Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
    Acked-by: Michael Riesch <michael.riesch@wolfvision.net>
    Link: https://lore.kernel.org/r/20220123133510.135651-1-linux@fw-web.de
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit 2ddd96aadbd0412040ef49eda94549c32de6c92c
Author: Frank Wunderlich <frank-w@public-files.de>
Date:   Sun Jan 23 14:36:15 2022 +0100

    arm64: dts: rockchip: fix dma-controller node names on rk356x
    
    DMA-Cotrollers defined in rk356x.dtsi do not match the pattern in bindings.
    
    arch/arm64/boot/dts/rockchip/rk3568-evb1-v10.dt.yaml:
      dmac@fe530000: $nodename:0: 'dmac@fe530000' does not match '^dma-controller(@.*)?$'
            From schema: Documentation/devicetree/bindings/dma/arm,pl330.yaml
    arch/arm64/boot/dts/rockchip/rk3568-evb1-v10.dt.yaml:
      dmac@fe550000: $nodename:0: 'dmac@fe550000' does not match '^dma-controller(@.*)?$'
            From schema: Documentation/devicetree/bindings/dma/arm,pl330.yaml
    
    This Patch fixes it.
    
    Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
    Link: https://lore.kernel.org/r/20220123133615.135789-1-linux@fw-web.de
    Signed-off-by: Heiko Stuebner <heiko@sntech.de>

commit f5390cd0b43c2e54c7cf5506c7da4a37c5cef746
Author: Ard Biesheuvel <ardb@kernel.org>
Date:   Wed Jan 12 11:14:13 2022 +0100

    efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
    
    Aditya reports [0] that his recent MacbookPro crashes in the firmware
    when using the variable services at runtime. The culprit appears to be a
    call to QueryVariableInfo(), which we did not use to call on Apple x86
    machines in the past as they only upgraded from EFI v1.10 to EFI v2.40
    firmware fairly recently, and QueryVariableInfo() (along with
    UpdateCapsule() et al) was added in EFI v2.00.
    
    The only runtime service introduced in EFI v2.00 that we actually use in
    Linux is QueryVariableInfo(), as the capsule based ones are optional,
    generally not used at runtime (all the LVFS/fwupd firmware update
    infrastructure uses helper EFI programs that invoke capsule update at
    boot time, not runtime), and not implemented by Apple machines in the
    first place. QueryVariableInfo() is used to 'safely' set variables,
    i.e., only when there is enough space. This prevents machines with buggy
    firmwares from corrupting their NVRAMs when they run out of space.
    
    Given that Apple machines have been using EFI v1.10 services only for
    the longest time (the EFI v2.0 spec was released in 2006, and Linux
    support for the newly introduced runtime services was added in 2011, but
    the MacbookPro12,1 released in 2015 still claims to be EFI v1.10 only),
    let's avoid the EFI v2.0 ones on all Apple x86 machines.
    
    [0] https://lore.kernel.org/all/6D757C75-65B1-468B-842D-10410081A8E4@live.com/
    
    Cc: <stable@vger.kernel.org>
    Cc: Jeremy Kerr <jk@ozlabs.org>
    Cc: Matthew Garrett <mjg59@srcf.ucam.org>
    Reported-by: Aditya Garg <gargaditya08@live.com>
    Tested-by: Orlando Chamberlain <redecorating@protonmail.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Tested-by: Aditya Garg <gargaditya08@live.com>
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215277

commit e9b7c3a4263bdcfd31bc3d03d48ce0ded7a94635
Author: Mihai Carabas <mihai.carabas@oracle.com>
Date:   Wed Jan 19 18:14:27 2022 +0200

    efi/libstub: arm64: Fix image check alignment at entry
    
    The kernel is aligned at SEGMENT_SIZE and this is the size populated in the PE
    headers:
    
    arch/arm64/kernel/efi-header.S: .long   SEGMENT_ALIGN // SectionAlignment
    
    EFI_KIMG_ALIGN is defined as: (SEGMENT_ALIGN > THREAD_ALIGN ? SEGMENT_ALIGN :
    THREAD_ALIGN)
    
    So it depends on THREAD_ALIGN. On newer builds this message started to appear
    even though the loader is taking into account the PE header (which is stating
    SEGMENT_ALIGN).
    
    Fixes: c32ac11da3f8 ("efi/libstub: arm64: Double check image alignment at entry")
    Signed-off-by: Mihai Carabas <mihai.carabas@oracle.com>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

commit 3d787b392d169d4a2e3aee6ac6dfd6ec39722cf2
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Sat Jan 22 10:24:31 2022 +0100

    s390/uaccess: fix compile error
    
    Compiling with e.g MARCH=z900 results in compile errors:
    
       arch/s390/lib/uaccess.c: In function 'copy_from_user_mvcos':
    >> arch/s390/lib/uaccess.c:65:15: error: variable 'spec' has initializer but incomplete type
          65 |         union oac spec = {
    
    Therefore make definition of union oac visible for all MARCHs.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Nico Boehr <nrb@linux.ibm.com>
    Cc: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Fixes: 012a224e1fa3 ("s390/uaccess: introduce bit field for OAC specifier")
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit f094a39c6ba168f2df1edfd1731cca377af5f442
Author: Christian Borntraeger <borntraeger@linux.ibm.com>
Date:   Mon Jan 17 18:40:32 2022 +0100

    s390/nmi: handle vector validity failures for KVM guests
    
    The machine check validity bit tells about the context. If a KVM guest
    was running the bit tells about the guest validity and the host state is
    not affected. As a guest can disable the guest validity this might
    result in unwanted host errors on machine checks.
    
    Cc: stable@vger.kernel.org
    Fixes: c929500d7a5a ("s390/nmi: s390: New low level handling for machine check happening in guest")
    Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 1ea1d6a847d2b1d17fefd9196664b95f052a0775
Author: Christian Borntraeger <borntraeger@linux.ibm.com>
Date:   Thu Jan 13 11:44:19 2022 +0100

    s390/nmi: handle guarded storage validity failures for KVM guests
    
    machine check validity bits reflect the state of the machine check. If a
    guest does not make use of guarded storage, the validity bit might be
    off. We can not use the host CR bit to decide if the validity bit must
    be on. So ignore "invalid" guarded storage controls for KVM guests in
    the host and rely on the machine check being forwarded to the guest.  If
    no other errors happen from a host perspective everything is fine and no
    process must be killed and the host can continue to run.
    
    Cc: stable@vger.kernel.org
    Fixes: c929500d7a5a ("s390/nmi: s390: New low level handling for machine check happening in guest")
    Reported-by: Carsten Otte <cotte@de.ibm.com>
    Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
    Tested-by: Carsten Otte <cotte@de.ibm.com>
    Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 10:12:53 2022 +0200

    Linux 5.17-rc1

commit 40c843218f11625722e9a7c3ced81a83b95ecf05
Merge: 67bfce0e01927 f0ac5b85810a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 08:14:21 2022 +0200

    Merge tag 'perf-tools-for-v5.17-2022-01-22' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull more perf tools updates from Arnaldo Carvalho de Melo:
    
     - Fix printing 'phys_addr' in 'perf script'.
    
     - Fix failure to add events with 'perf probe' in ppc64 due to not
       removing leading dot (ppc64 ABIv1).
    
     - Fix cpu_map__item() python binding building.
    
     - Support event alias in form foo-bar-baz, add pmu-events and
       parse-event tests for it.
    
     - No need to setup affinities when starting a workload or attaching to
       a pid.
    
     - Use path__join() to compose a path instead of ad-hoc snprintf()
       equivalent.
    
     - Override attr->sample_period for non-libpfm4 events.
    
     - Use libperf cpumap APIs instead of accessing the internal state
       directly.
    
     - Sync x86 arch prctl headers and files changed by the new
       set_mempolicy_home_node syscall with the kernel sources.
    
     - Remove duplicate include in cpumap.h.
    
     - Remove redundant err variable.
    
    * tag 'perf-tools-for-v5.17-2022-01-22' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux:
      perf tools: Remove redundant err variable
      perf test: Add parse-events test for aliases with hyphens
      perf test: Add pmu-events test for aliases with hyphens
      perf parse-events: Support event alias in form foo-bar-baz
      perf evsel: Override attr->sample_period for non-libpfm4 events
      perf cpumap: Remove duplicate include in cpumap.h
      perf cpumap: Migrate to libperf cpumap api
      perf python: Fix cpu_map__item() building
      perf script: Fix printing 'phys_addr' failure issue
      tools headers UAPI: Sync files changed by new set_mempolicy_home_node syscall
      tools headers UAPI: Sync x86 arch prctl headers with the kernel sources
      perf machine: Use path__join() to compose a path instead of snprintf(dir, '/', filename)
      perf evlist: No need to setup affinities when disabling events for pid targets
      perf evlist: No need to setup affinities when enabling events for pid targets
      perf stat: No need to setup affinities when starting a workload
      perf affinity: Allow passing a NULL arg to affinity__cleanup()
      perf probe: Fix ppc64 'perf probe add events failed' case

commit 67bfce0e01927859618b76ff5a36a7f23b412cef
Merge: 473aec0e1f84b 6b9b6413700e1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 08:07:02 2022 +0200

    Merge tag 'trace-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull ftrace fix from Steven Rostedt:
     "Fix s390 breakage from sorting mcount tables.
    
      The latest merge of the tracing tree sorts the mcount table at build
      time. But s390 appears to do things differently (like always) and
      replaces the sorted table back to the original unsorted one. As the
      ftrace algorithm depends on it being sorted, bad things happen when it
      is not, and s390 experienced those bad things.
    
      Add a new config to tell the boot if the mcount table is sorted or
      not, and allow s390 to opt out of it"
    
    * tag 'trace-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      ftrace: Fix assuming build time sort works for s390

commit 6b9b6413700e104934734b72a3be622a76923b98
Author: Steven Rostedt (Google) <rostedt@goodmis.org>
Date:   Sat Jan 22 09:17:10 2022 -0500

    ftrace: Fix assuming build time sort works for s390
    
    To speed up the boot process, as mcount_loc needs to be sorted for ftrace
    to work properly, sorting it at build time is more efficient than boot up
    and can save milliseconds of time. Unfortunately, this change broke s390
    as it will modify the mcount_loc location after the sorting takes place
    and will put back the unsorted locations. Since the sorting is skipped at
    boot up if it is believed that it was sorted at run time, ftrace can crash
    as its algorithms are dependent on the list being sorted.
    
    Add a new config BUILDTIME_MCOUNT_SORT that is set when
    BUILDTIME_TABLE_SORT but not if S390 is set. Use this config to determine
    if sorting should take place at boot up.
    
    Link: https://lore.kernel.org/all/yt9dee51ctfn.fsf@linux.ibm.com/
    
    Fixes: 72b3942a173c ("scripts: ftrace - move the sort-processing in ftrace_init")
    Reported-by: Sven Schnelle <svens@linux.ibm.com>
    Tested-by: Heiko Carstens <hca@linux.ibm.com>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

commit 473aec0e1f84be97c7ea52c4266b7ef13ce36af3
Merge: 3689f9f8b0c52 e6340b6526eee
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 06:32:29 2022 +0200

    Merge tag 'kbuild-fixes-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
    
    Pull Kbuild fixes from Masahiro Yamada:
    
     - Bring include/uapi/linux/nfc.h into the UAPI compile-test coverage
    
     - Revert the workaround of CONFIG_CC_IMPLICIT_FALLTHROUGH
    
     - Fix build errors in certs/Makefile
    
    * tag 'kbuild-fixes-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild:
      certs: Fix build error when CONFIG_MODULE_SIG_KEY is empty
      certs: Fix build error when CONFIG_MODULE_SIG_KEY is PKCS#11 URI
      Revert "Makefile: Do not quote value for CONFIG_CC_IMPLICIT_FALLTHROUGH"
      usr/include/Makefile: add linux/nfc.h to the compile-test coverage

commit 3689f9f8b0c52dfd8f5995e4b58917f8f3ac3ee3
Merge: 1c52283265a46 15325b4f768f2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 23 06:20:44 2022 +0200

    Merge tag 'bitmap-5.17-rc1' of git://github.com/norov/linux
    
    Pull bitmap updates from Yury Norov:
    
     - introduce for_each_set_bitrange()
    
     - use find_first_*_bit() instead of find_next_*_bit() where possible
    
     - unify for_each_bit() macros
    
    * tag 'bitmap-5.17-rc1' of git://github.com/norov/linux:
      vsprintf: rework bitmap_list_string
      lib: bitmap: add performance test for bitmap_print_to_pagebuf
      bitmap: unify find_bit operations
      mm/percpu: micro-optimize pcpu_is_populated()
      Replace for_each_*_bit_from() with for_each_*_bit() where appropriate
      find: micro-optimize for_each_{set,clear}_bit()
      include/linux: move for_each_bit() macros from bitops.h to find.h
      cpumask: replace cpumask_next_* with cpumask_first_* where appropriate
      tools: sync tools/bitmap with mother linux
      all: replace find_next{,_zero}_bit with find_first{,_zero}_bit where appropriate
      cpumask: use find_first_and_bit()
      lib: add find_first_and_bit()
      arch: remove GENERIC_FIND_FIRST_BIT entirely
      include: move find.h from asm_generic to linux
      bitops: move find_bit_*_le functions from le.h to find.h
      bitops: protect find_first_{,zero}_bit properly

commit f0ac5b85810a69104ee6bc939bcbaecfe4db9a3e
Author: Minghao Chi <chi.minghao@zte.com.cn>
Date:   Wed Jan 12 08:01:09 2022 +0000

    perf tools: Remove redundant err variable
    
    Return value from perf_event__process_tracing_data() directly instead
    of taking this in another redundant variable.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: http://lore.kernel.org/lkml/20220112080109.666800-1-chi.minghao@zte.com.cn
    Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b4a7276c5e9a79c238a2fad4fb9498dd3558ad2e
Author: John Garry <john.garry@huawei.com>
Date:   Mon Jan 17 23:10:15 2022 +0800

    perf test: Add parse-events test for aliases with hyphens
    
    Add a test which allows us to test parsing an event alias with hyphens.
    
    Since these events typically do not exist on most host systems, add the
    alias to the fake pmu.
    
    Function perf_pmu__test_parse_init() has terms added to match known test
    aliases.
    
    Signed-off-by: John Garry <john.garry@huawei.com>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qi Liu <liuqi115@huawei.com>
    Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
    Cc: linuxarm@huawei.com
    Link: https://lore.kernel.org/r/1642432215-234089-4-git-send-email-john.garry@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 34fa67e72085201ea94b5332eae316951331958f
Author: John Garry <john.garry@huawei.com>
Date:   Mon Jan 17 23:10:14 2022 +0800

    perf test: Add pmu-events test for aliases with hyphens
    
    Add a test for aliases with hyphens in the name to ensure that the
    pmu-events tables are as expects. There should be no reason why these sort
    of aliases would be treated differently, but no harm in checking.
    
    Signed-off-by: John Garry <john.garry@huawei.com>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qi Liu <liuqi115@huawei.com>
    Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
    Cc: linuxarm@huawei.com
    Link: https://lore.kernel.org/r/1642432215-234089-3-git-send-email-john.garry@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 864bc8c905261f264c3ea357027cf555fe51c5a3
Author: John Garry <john.garry@huawei.com>
Date:   Mon Jan 17 23:10:13 2022 +0800

    perf parse-events: Support event alias in form foo-bar-baz
    
    Event aliasing for events whose name in the form foo-bar-baz is not
    supported, while foo-bar, foo_bar_baz, and other combinations are, i.e.
    two hyphens are not supported.
    
    The HiSilicon D06 platform has events in such form:
    
      $ ./perf list sdir-home-migrate
    
      List of pre-defined events (to be used in -e):
    
      uncore hha:
        sdir-home-migrate
       [Unit: hisi_sccl,hha]
    
      $ sudo ./perf stat -e sdir-home-migrate
      event syntax error: 'sdir-home-migrate'
                              \___ parser error
      Run 'perf list' for a list of valid events
    
       Usage: perf stat [<options>] [<command>]
    
       -e, --event <event>event selector. use 'perf list' to list available events
    
    To support, add an extra PMU event symbol type for "baz", and add a new
    rule in the bison file.
    
    Signed-off-by: John Garry <john.garry@huawei.com>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qi Liu <liuqi115@huawei.com>
    Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
    Cc: linuxarm@huawei.com
    Link: https://lore.kernel.org/r/1642432215-234089-2-git-send-email-john.garry@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3606c0e1a1050d397ad759a62607e419fd8b0ccb
Author: German Gomez <german.gomez@arm.com>
Date:   Tue Jan 18 14:40:54 2022 +0000

    perf evsel: Override attr->sample_period for non-libpfm4 events
    
    A previous patch preventing "attr->sample_period" values from being
    overridden in pfm events changed a related behaviour in arm-spe.
    
    Before said patch:
    
      perf record -c 10000 -e arm_spe_0// -- sleep 1
    
    Would yield an SPE event with period=10000. After the patch, the period
    in "-c 10000" was being ignored because the arm-spe code initializes
    sample_period to a non-zero value.
    
    This patch restores the previous behaviour for non-libpfm4 events.
    
    Fixes: ae5dcc8abe31 (“perf record: Prevent override of attr->sample_period for libpfm4 events”)
    Reported-by: Chase Conklin <chase.conklin@arm.com>
    Signed-off-by: German Gomez <german.gomez@arm.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Fastabend <john.fastabend@gmail.com>
    Cc: KP Singh <kpsingh@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Martin KaFai Lau <kafai@fb.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Song Liu <songliubraving@fb.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Yonghong Song <yhs@fb.com>
    Cc: bpf@vger.kernel.org
    Cc: netdev@vger.kernel.org
    Link: http://lore.kernel.org/lkml/20220118144054.2541-1-german.gomez@arm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 24ead7c254b42c4ea252e57bf9928154dc7744e0
Author: Lv Ruyi <lv.ruyi@zte.com.cn>
Date:   Mon Jan 17 08:37:30 2022 +0000

    perf cpumap: Remove duplicate include in cpumap.h
    
    Remove all but the first include of stdbool.h from cpumap.h.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Lv Ruyi <lv.ruyi@zte.com.cn>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220117083730.863200-1-lv.ruyi@zte.com.cn
    Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 440286993960bea4aa09d912a5497d92d09ae54c
Author: Ian Rogers <irogers@google.com>
Date:   Fri Jan 21 20:58:10 2022 -0800

    perf cpumap: Migrate to libperf cpumap api
    
    Switch from directly accessing the perf_cpu_map to using the appropriate
    libperf API when possible. Using the API simplifies the job of
    refactoring use of perf_cpu_map.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: André Almeida <andrealmeid@collabora.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Darren Hart <dvhart@infradead.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Dmitriy Vyukov <dvyukov@google.com>
    Cc: Eric Dumazet <edumazet@google.com>
    Cc: German Gomez <german.gomez@arm.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jin Yao <yao.jin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Miaoqian Lin <linmq006@gmail.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
    Cc: Song Liu <song@kernel.org>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Stephen Brennan <stephen.s.brennan@oracle.com>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Thomas Richter <tmricht@linux.ibm.com>
    Cc: Yury Norov <yury.norov@gmail.com>
    Link: http://lore.kernel.org/lkml/20220122045811.3402706-3-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 1d1d9af254ffc3bc38c59484c50c600d1d0c96da
Author: Ian Rogers <irogers@google.com>
Date:   Fri Jan 21 20:58:09 2022 -0800

    perf python: Fix cpu_map__item() building
    
    Value should be built as an integer.
    
    Switch some uses of perf_cpu_map to use the library API.
    
    Fixes: 6d18804b963b78dc ("perf cpumap: Give CPUs their own type")
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexey Bayduraev <alexey.v.bayduraev@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: André Almeida <andrealmeid@collabora.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Darren Hart <dvhart@infradead.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Dmitriy Vyukov <dvyukov@google.com>
    Cc: Eric Dumazet <edumazet@google.com>
    Cc: German Gomez <german.gomez@arm.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jin Yao <yao.jin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Miaoqian Lin <linmq006@gmail.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
    Cc: Song Liu <song@kernel.org>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Stephen Brennan <stephen.s.brennan@oracle.com>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Thomas Richter <tmricht@linux.ibm.com>
    Cc: Yury Norov <yury.norov@gmail.com>
    Link: http://lore.kernel.org/lkml/20220122045811.3402706-2-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 9edcde68d653e1f8f895fbb69a0043c6a56ae35e
Author: Yao Jin <jinyao5@huawei.com>
Date:   Fri Jan 21 14:59:54 2022 +0800

    perf script: Fix printing 'phys_addr' failure issue
    
    Perf script was failed to print the phys_addr for SPE profiling.
    One 'dummy' event is added by SPE profiling but it doesn't have PHYS_ADDR
    attribute set, perf script then exits with error.
    
    Now referring to 'addr', use evsel__do_check_stype() to check the type.
    
    Before:
    
      # perf record -e arm_spe_0/branch_filter=0,ts_enable=1,pa_enable=1,load_filter=1,jitter=0,\
                    store_filter=0,min_latency=0,event_filter=2/ -p 4064384 -- sleep 3
      # perf script -F pid,tid,addr,phys_addr
      Samples for 'dummy:u' event do not have PHYS_ADDR attribute set. Cannot print 'phys_addr' field.
    
    After:
    
      # perf record -e arm_spe_0/branch_filter=0,ts_enable=1,pa_enable=1,load_filter=1,jitter=0,\
                    store_filter=0,min_latency=0,event_filter=2/ -p 4064384 -- sleep 3
      # perf script -F pid,tid,addr,phys_addr
      4064384/4064384 ffff802f921be0d0      2f921be0d0
      4064384/4064384 ffff802f921be0d0      2f921be0d0
    
    Reviewed-by: German Gomez <german.gomez@arm.com>
    Signed-off-by: Yao Jin <jinyao5@huawei.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Hanjun Guo <guohanjun@huawei.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20220121065954.2121900-1-liwei391@huawei.com
    Signed-off-by: Wei Li <liwei391@huawei.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 16436f70abeebb29cd99444e27b310755806c1fa
Author: Ard Biesheuvel <ardb@kernel.org>
Date:   Sat Jan 22 16:16:14 2022 +0100

    irqchip/gic-v3-its: Fix build for !SMP
    
    Commit 835f442fdbce ("irqchip/gic-v3-its: Limit memreserve cpuhp state
    lifetime") added a reference to cpus_booted_once_mask, which does not
    exist on !SMP builds, breaking the build for such configurations.
    
    Given the intent of the check, short circuit it to always pass.
    
    Cc: Valentin Schneider <valentin.schneider@arm.com>
    Fixes: 835f442fdbce ("irqchip/gic-v3-its: Limit memreserve cpuhp state lifetime")
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220122151614.133766-1-ardb@kernel.org

commit e6340b6526eeec5a00fe26a6ff515afe7d0affa4
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Fri Jan 21 04:22:05 2022 +0900

    certs: Fix build error when CONFIG_MODULE_SIG_KEY is empty
    
    Since b8c96a6b466c ("certs: simplify $(srctree)/ handling and remove
    config_filename macro"), when CONFIG_MODULE_SIG_KEY is empty,
    signing_key.x509 fails to build:
    
        CERT    certs/signing_key.x509
      Usage: extract-cert <source> <dest>
      make[1]: *** [certs/Makefile:78: certs/signing_key.x509] Error 2
      make: *** [Makefile:1831: certs] Error 2
    
    Pass "" to the first argument of extract-cert to fix the build error.
    
    Link: https://lore.kernel.org/linux-kbuild/20220120094606.2skuyb26yjlnu66q@lion.mk-sys.cz/T/#u
    Fixes: b8c96a6b466c ("certs: simplify $(srctree)/ handling and remove config_filename macro")
    Reported-by: Michal Kubecek <mkubecek@suse.cz>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Tested-by: Michal Kubecek <mkubecek@suse.cz>

commit ad29a2fb3c201ef066b0a9fe10a6e14dd0d59c48
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Fri Jan 21 04:22:04 2022 +0900

    certs: Fix build error when CONFIG_MODULE_SIG_KEY is PKCS#11 URI
    
    When CONFIG_MODULE_SIG_KEY is PKCS#11 URL (pkcs11:*), signing_key.x509
    fails to build:
    
      certs/Makefile:77: *** target pattern contains no '%'.  Stop.
    
    Due to the typo, $(X509_DEP) contains a colon.
    
    Fix it.
    
    Fixes: b8c96a6b466c ("certs: simplify $(srctree)/ handling and remove config_filename macro")
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit e92e2634ef3a95376ad917452a476fccaff83fde
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Thu Jan 20 14:31:00 2022 +0900

    Revert "Makefile: Do not quote value for CONFIG_CC_IMPLICIT_FALLTHROUGH"
    
    This reverts commit cd8c917a56f20f48748dd43d9ae3caff51d5b987.
    
    Commit 129ab0d2d9f3 ("kbuild: do not quote string values in
    include/config/auto.conf") provided the final solution.
    
    Now reverting the temporary workaround.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 10756dc5b02bff370ddd351d7744bc99ada659c2
Author: Dmitry V. Levin <ldv@altlinux.org>
Date:   Mon Jan 3 04:24:02 2022 +0300

    usr/include/Makefile: add linux/nfc.h to the compile-test coverage
    
    As linux/nfc.h userspace compilation was finally fixed by commits
    79b69a83705e ("nfc: uapi: use kernel size_t to fix user-space builds")
    and 7175f02c4e5f ("uapi: fix linux/nfc.h userspace compilation errors"),
    there is no need to keep the compile-test exception for it in
    usr/include/Makefile.
    
    Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit a6501e4b380faee6bbf41bb2f833977c7ac6491a
Author: Kees Cook <keescook@chromium.org>
Date:   Tue Jan 18 10:20:03 2022 -0800

    eeprom: at25: Restore missing allocation
    
    The at25 driver regressed in v5.17-rc1 due to a broken conflict
    resolution: the allocation of the object was accidentally removed. Restore
    it.
    
    This was found when building under CONFIG_FORTIFY_SOURCE=y and
    -Warray-bounds, which complained about strncpy() being used against an
    empty object:
    
    In function 'strncpy',
        inlined from 'at25_fw_to_chip.constprop' at drivers/misc/eeprom/at25.c:312:2:
    ./include/linux/fortify-string.h:48:33: warning: '__builtin_strncpy' offset [0, 9] is out of the bounds [0, 0] [-Warray-bounds]
       48 | #define __underlying_strncpy    __builtin_strncpy
          |                                 ^
    ./include/linux/fortify-string.h:59:16: note: in expansion of macro '__underlying_strncpy'
       59 |         return __underlying_strncpy(p, q, size);
          |                ^~~~~~~~~~~~~~~~~~~~
    In function 'strncpy',
        inlined from 'at25_fram_to_chip' at drivers/misc/eeprom/at25.c:373:2,
        inlined from 'at25_probe' at drivers/misc/eeprom/at25.c:453:10:
    ./include/linux/fortify-string.h:48:33: warning: '__builtin_strncpy' offset [0, 9] is out of the bounds [0, 0] [-Warray-bounds]
       48 | #define __underlying_strncpy    __builtin_strncpy
          |                                 ^
    ./include/linux/fortify-string.h:59:16: note: in expansion of macro '__underlying_strncpy'
       59 |         return __underlying_strncpy(p, q, size);
          |                ^~~~~~~~~~~~~~~~~~~~
    
    Link: https://lore.kernel.org/lkml/CAHp75VdqK7h63fz-cPaQ2MGaVdaR2f1Fb5kKCZidUG3RwLsAVA@mail.gmail.com/
    Fixes: af40d16042d6 ("Merge v5.15-rc5 into char-misc-next")
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Jiri Prchal <jiri.prchal@aksignal.cz>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Link: https://lore.kernel.org/r/20220118182003.3385019-1-keescook@chromium.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d11a327ed95dbec756b99cbfef2a7fd85c9eeb09
Author: Marc Zyngier <maz@kernel.org>
Date:   Fri Jan 21 21:07:47 2022 +0000

    KVM: arm64: vgic-v3: Restrict SEIS workaround to known broken systems
    
    Contrary to what df652bcf1136 ("KVM: arm64: vgic-v3: Work around GICv3
    locally generated SErrors") was asserting, there is at least one other
    system out there (Cavium ThunderX2) implementing SEIS, and not in
    an obviously broken way.
    
    So instead of imposing the M1 workaround on an innocent bystander,
    let's limit it to the two known broken Apple implementations.
    
    Fixes: df652bcf1136 ("KVM: arm64: vgic-v3: Work around GICv3 locally generated SErrors")
    Reported-by: Ard Biesheuvel <ardb@kernel.org>
    Tested-by: Ard Biesheuvel <ardb@kernel.org>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220122103912.795026-1-maz@kernel.org

commit 1c52283265a462a100ae63ddf58b4e5884acde86
Merge: 8205ae327e396 6e61dde82e8bf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 11:28:23 2022 +0200

    Merge branch 'akpm' (patches from Andrew)
    
    Merge yet more updates from Andrew Morton:
     "This is the post-linux-next queue. Material which was based on or
      dependent upon material which was in -next.
    
      69 patches.
    
      Subsystems affected by this patch series: mm (migration and zsmalloc),
      sysctl, proc, and lib"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>: (69 commits)
      mm: hide the FRONTSWAP Kconfig symbol
      frontswap: remove support for multiple ops
      mm: mark swap_lock and swap_active_head static
      frontswap: simplify frontswap_register_ops
      frontswap: remove frontswap_test
      mm: simplify try_to_unuse
      frontswap: remove the frontswap exports
      frontswap: simplify frontswap_init
      frontswap: remove frontswap_curr_pages
      frontswap: remove frontswap_shrink
      frontswap: remove frontswap_tmem_exclusive_gets
      frontswap: remove frontswap_writethrough
      mm: remove cleancache
      lib/stackdepot: always do filter_irq_stacks() in stack_depot_save()
      lib/stackdepot: allow optional init and stack_table allocation by kvmalloc()
      proc: remove PDE_DATA() completely
      fs: proc: store PDE()->data into inode->i_private
      zsmalloc: replace get_cpu_var with local_lock
      zsmalloc: replace per zpage lock with pool->migrate_lock
      locking/rwlocks: introduce write_lock_nested
      ...

commit 8205ae327e396820fb7a176a94768146ac0b87ea
Merge: 1cb69c8044fd5 51620150ca2df
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 11:12:26 2022 +0200

    Merge tag '5.17-rc-part2-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs fixes from Steve French:
    
     - multichannel fixes, addressing additional reconnect and DFS scenarios
    
     - reenabling fscache support (indexing rewrite, metadata caching e.g.)
    
     - send additional version information during NTLMSSP negotiate to
       improve debugging
    
     - fix for a mount race
    
     - DFS fixes
    
     - fix for a memory leak for stable
    
    * tag '5.17-rc-part2-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6:
      cifs: update internal module number
      smb3: send NTLMSSP version information
      cifs: Support fscache indexing rewrite
      cifs: cifs_ses_mark_for_reconnect should also update reconnect bits
      cifs: update tcpStatus during negotiate and sess setup
      cifs: make status checks in version independent callers
      cifs: remove repeated state change in dfs tree connect
      cifs: fix the cifs_reconnect path for DFS
      cifs: remove unused variable ses_selected
      cifs: protect all accesses to chan_* with chan_lock
      cifs: fix the connection state transitions with multichannel
      cifs: check reconnects for channels of active tcons too
      smb3: add new defines from protocol specification
      cifs: serialize all mount attempts
      cifs: quirk for STATUS_OBJECT_NAME_INVALID returned for non-ASCII dfs refs
      cifs: alloc_path_with_tree_prefix: do not append sep. if the path is empty
      cifs: clean up an inconsistent indenting
      cifs: free ntlmsspblob allocated in negotiate

commit 1cb69c8044fd534a0e19154831234d75f7b8d447
Merge: 7fd350f6ff846 6191cf3ad59fd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 11:04:27 2022 +0200

    Merge tag 'xfs-5.17-merge-7' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs fixes from Darrick Wong:
     "One of the patches removes some dead code from xfs_ioctl32.h and the
      other fixes broken workqueue flushing in the inode garbage collector.
    
       - Minor cleanup of ioctl32 cruft
    
       - Clean up open coded inodegc workqueue function calls"
    
    * tag 'xfs-5.17-merge-7' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: flush inodegc workqueue tasks before cancel
      xfs: remove unused xfs_ioctl32.h declarations

commit 7fd350f6ff846f788ba5f6668bacf2ce4257ed8f
Merge: b68b10b626600 cef0223191452
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:59:32 2022 +0200

    Merge tag 'fscache-fixes-20220121' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs
    
    Pull more fscache updates from David Howells:
     "A set of fixes and minor updates for the fscache rewrite:
    
       - Fix mishandling of volume collisions (the wait condition is
         inverted and so it was only waiting if the volume collision was
         already resolved).
    
       - Fix miscalculation of whether there's space available in
         cachefiles.
    
       - Make sure a default cache name is set on a cache if the user hasn't
         set one by the time they bind the cache.
    
       - Adjust the way the backing inode is presented in tracepoints, add a
         tracepoint for mkdir and trace directory lookup.
    
       - Add a tracepoint for failure to set the active file mark.
    
       - Add an explanation of the checks made on the backing filesystem.
    
       - Check that the backing filesystem supports tmpfile.
    
       - Document how the page-release cancellation of the read-skip
         optimisation works.
    
      And I've included a change for netfslib:
    
       - Make ops->init_rreq() optional"
    
    * tag 'fscache-fixes-20220121' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs:
      netfs: Make ops->init_rreq() optional
      fscache: Add a comment explaining how page-release optimisation works
      cachefiles: Check that the backing filesystem supports tmpfiles
      cachefiles: Explain checks in a comment
      cachefiles: Trace active-mark failure
      cachefiles: Make some tracepoint adjustments
      cachefiles: set default tag name if it's unspecified
      cachefiles: Calculate the blockshift in terms of bytes, not pages
      fscache: Fix the volume collision wait condition

commit b68b10b6266009bc8770adf952d637250ee93135
Merge: 369af20a2c3f7 3abb28e275bfb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:43:07 2022 +0200

    Merge tag 'folio-5.17a' of git://git.infradead.org/users/willy/pagecache
    
    Pull more folio updates from Matthew Wilcox:
     "Three small folio patches.
    
      One bug fix, one patch pulled forward from the patches destined for
      5.18 and then a patch to make use of that functionality"
    
    * tag 'folio-5.17a' of git://git.infradead.org/users/willy/pagecache:
      filemap: Use folio_put_refs() in filemap_free_folio()
      mm: Add folio_put_refs()
      pagevec: Initialise folio_batch->percpu_pvec_drained

commit 369af20a2c3f738c8610d75b010ee5dc5d3c207f
Merge: b087788c20aa9 2576e153cd982
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:24:02 2022 +0200

    Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull more SCSI updates from James Bottomley:
     "This series is all the stragglers that didn't quite make the first
      merge window pull. It's mostly minor updates and bug fixes of merge
      window code"
    
    * tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi:
      scsi: nsp_cs: Check of ioremap return value
      scsi: ufs: ufs-mediatek: Fix error checking in ufs_mtk_init_va09_pwr_ctrl()
      scsi: ufs: Modify Tactive time setting conditions
      scsi: efct: Remove useless DMA-32 fallback configuration
      scsi: message: fusion: mptctl: Use dma_alloc_coherent()
      scsi: message: fusion: mptsas: Use dma_alloc_coherent()
      scsi: message: fusion: Use dma_alloc_coherent() in mptsas_exp_repmanufacture_info()
      scsi: message: fusion: mptbase: Use dma_alloc_coherent()
      scsi: message: fusion: Use dma_alloc_coherent() in mpt_alloc_fw_memory()
      scsi: message: fusion: Remove usage of the deprecated "pci-dma-compat.h" API
      scsi: megaraid: Avoid mismatched storage type sizes
      scsi: hisi_sas: Remove unused variable and check in hisi_sas_send_ata_reset_each_phy()
      scsi: aic79xx: Remove redundant error variable
      scsi: pm80xx: Port reset timeout error handling correction
      scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
      scsi: mpi3mr: Fix some spelling mistakes
      scsi: mpt3sas: Update persistent trigger pages from sysfs interface
      scsi: core: Fix scsi_mode_select() interface
      scsi: aacraid: Fix spelling of "its"
      scsi: qedf: Fix potential dereference of NULL pointer

commit b087788c20aa959f83df989b31fdcc4182b2d067
Merge: 6bdfb259d6d66 b875b39e7373d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:22:11 2022 +0200

    Merge tag 'ata-5.17-rc1-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ATA fix from Damien Le Moal:
     "A single patch to fix a compilation error in the pata_octeon_cf driver
      (mips architecture), from me"
    
    * tag 'ata-5.17-rc1-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata:
      ata: pata_octeon_cf: fix call to trace_ata_bmdma_stop()

commit 6bdfb259d6d66161011d1d618af190f52b6d57fd
Merge: 71f1b916d5ea4 e5b54867f47f7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:15:41 2022 +0200

    Merge tag 'thermal-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull more thermal control updates from Rafael Wysocki:
     "Add device IDs for Raptor Lake to the int340x thermal control driver
      (Srinivas Pandruvada)"
    
    * tag 'thermal-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      thermal: int340x: Add Raptor Lake PCI device id
      thermal: int340x: Support Raptor Lake

commit 71f1b916d5ea4a6d781b29e2470f5870a561e82e
Merge: 0809edbae347a f6f02040e0ca7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 10:09:51 2022 +0200

    Merge tag 'acpi-5.17-rc1-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull extra ACPI updates from Rafael Wysocki:
     "These fix and clean up the ACPI CPPC driver on top of the recent
      changes in it merged previously and add some new device IDs to the
      ACPI DPTF driver.
    
      Specifics:
    
       - Fix a recently introduced endianness-related issue in the ACPI CPPC
         library and clean it up on top of that (Rafael Wysocki)
    
       - Add new device IDs for the Raptor Lake SoC to the ACPI DPTF driver
         (Srinivas Pandruvada)"
    
    * tag 'acpi-5.17-rc1-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      ACPI: DPTF: Support Raptor Lake
      ACPI: CPPC: Drop redundant local variable from cpc_read()
      ACPI: CPPC: Fix up I/O port access in cpc_read()

commit 0809edbae347a224ca1b59fb8be1c2d54389c2c6
Merge: 636b5284d8fa1 18a86e5907f71
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:52:17 2022 +0200

    Merge tag 'devicetree-fixes-for-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
    
    Pull devicetree fixes and cleanups from Rob Herring:
    
     - Fix a regression when probing a child device reusing the parent
       device's DT node pointer
    
     - Refactor of_parse_phandle*() variants to static inlines
    
     - Drop Enric Balletbo i Serra as a maintainer
    
     - Fix DT schemas with arrays incorrectly encoded as a matrix
    
     - Drop unneeded pinctrl properties from schemas
    
     - Add SPI peripheral schema to SPI based displays
    
     - Clean-up several schema examples
    
     - Clean-up trivial-devices.yaml comments
    
     - Add missing, in use vendor prefixes: Wingtech, Thundercomm, Huawei,
       F(x)tec, 8devices
    
    * tag 'devicetree-fixes-for-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux:
      dt-bindings: google,cros-ec: drop Enric Balletbo i Serra from maintainers
      dt-bindings: display: bridge: drop Enric Balletbo i Serra from maintainers
      of: Check 'of_node_reused' flag on of_match_device()
      of: property: define of_property_read_u{8,16,32,64}_array() unconditionally
      of: base: make small of_parse_phandle() variants static inline
      dt-bindings: mfd: cirrus,madera: Fix 'interrupts' in example
      dt-bindings: Fix array schemas encoded as matrices
      dt-bindings: Drop unnecessary pinctrl properties
      dt-bindings: rtc: st,stm32-rtc: Make each example a separate entry
      dt-bindings: mmc: arm,pl18x: Make each example a separate entry
      dt-bindings: display: Add SPI peripheral schema to SPI based displays
      scripts/dtc: dtx_diff: remove broken example from help text
      dt-bindings: trivial-devices: fix double spaces in comments
      dt-bindings: trivial-devices: fix swapped comments
      dt-bindings: vendor-prefixes: add Wingtech
      dt-bindings: vendor-prefixes: add Thundercomm
      dt-bindings: vendor-prefixes: add Huawei
      dt-bindings: vendor-prefixes: add F(x)tec
      dt-bindings: vendor-prefixes: add 8devices
      dt-bindings: power: reset: gpio-restart: Correct default priority

commit 636b5284d8fa12cadbaa09bb7efa48473aa804f5
Merge: dc5341f41dc81 e2e83a73d7ce6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:40:01 2022 +0200

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull more kvm updates from Paolo Bonzini:
     "Generic:
    
       - selftest compilation fix for non-x86
    
       - KVM: avoid warning on s390 in mark_page_dirty
    
     x86:
    
       - fix page write-protection bug and improve comments
    
       - use binary search to lookup the PMU event filter, add test
    
       - enable_pmu module parameter support for Intel CPUs
    
       - switch blocked_vcpu_on_cpu_lock to raw spinlock
    
       - cleanups of blocked vCPU logic
    
       - partially allow KVM_SET_CPUID{,2} after KVM_RUN (5.16 regression)
    
       - various small fixes"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (46 commits)
      docs: kvm: fix WARNINGs from api.rst
      selftests: kvm/x86: Fix the warning in lib/x86_64/processor.c
      selftests: kvm/x86: Fix the warning in pmu_event_filter_test.c
      kvm: selftests: Do not indent with spaces
      kvm: selftests: sync uapi/linux/kvm.h with Linux header
      selftests: kvm: add amx_test to .gitignore
      KVM: SVM: Nullify vcpu_(un)blocking() hooks if AVIC is disabled
      KVM: SVM: Move svm_hardware_setup() and its helpers below svm_x86_ops
      KVM: SVM: Drop AVIC's intermediate avic_set_running() helper
      KVM: VMX: Don't do full kick when handling posted interrupt wakeup
      KVM: VMX: Fold fallback path into triggering posted IRQ helper
      KVM: VMX: Pass desired vector instead of bool for triggering posted IRQ
      KVM: VMX: Don't do full kick when triggering posted interrupt "fails"
      KVM: SVM: Skip AVIC and IRTE updates when loading blocking vCPU
      KVM: SVM: Use kvm_vcpu_is_blocking() in AVIC load to handle preemption
      KVM: SVM: Remove unnecessary APICv/AVIC update in vCPU unblocking path
      KVM: SVM: Don't bother checking for "running" AVIC when kicking for IPIs
      KVM: SVM: Signal AVIC doorbell iff vCPU is in guest mode
      KVM: x86: Remove defunct pre_block/post_block kvm_x86_ops hooks
      KVM: x86: Unexport LAPIC's switch_to_{hv,sw}_timer() helpers
      ...

commit dc5341f41dc81bd497828e562da135bcff9c876c
Merge: 7867e402787a2 d24846a4246b6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:37:31 2022 +0200

    Merge tag 'for-5.17/parisc-2' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
    
    Pull more parisc architecture updates from Helge Deller:
     "Fixes and enhancements:
    
       - a memory leak fix in an error path in pdc_stable (Miaoqian Lin)
    
       - two compiler warning fixes in the TOC code
    
       - added autodetection for currently used console type (serial or
         graphics) which inserts console=<type> if it's missing"
    
    * tag 'for-5.17/parisc-2' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
      parisc: pdc_stable: Fix memory leak in pdcs_register_pathentries
      parisc: Fix missing prototype for 'toc_intr' warning in toc.c
      parisc: Autodetect default output device and set console= kernel parameter
      parisc: Use safer strscpy() in setup_cmdline()
      parisc: Add visible flag to toc_stack variable

commit 7867e402787a23001cfb81ff298b7d023fee676a
Merge: b21bae9af1da9 c59cd507fb640
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:34:49 2022 +0200

    Merge tag 'riscv-for-linus-5.17-mw1' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull more RISC-V updates from Palmer Dabbelt:
    
     - Support for sv48 paging
    
     - Hart ID mappings are now sparse, which enables more CPUs to come up
       on systems with sparse hart IDs
    
     - A handful of cleanups and fixes
    
    * tag 'riscv-for-linus-5.17-mw1' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux: (27 commits)
      RISC-V: nommu_virt: Drop unused SLAB_MERGE_DEFAULT
      RISC-V: Remove redundant err variable
      riscv: dts: sifive unmatched: Add gpio poweroff
      riscv: canaan: remove useless select of non-existing config SYSCON
      RISC-V: Do not use cpumask data structure for hartid bitmap
      RISC-V: Move spinwait booting method to its own config
      RISC-V: Move the entire hart selection via lottery to SMP
      RISC-V: Use __cpu_up_stack/task_pointer only for spinwait method
      RISC-V: Do not print the SBI version during HSM extension boot print
      RISC-V: Avoid using per cpu array for ordered booting
      riscv: default to CONFIG_RISCV_SBI_V01=n
      riscv: fix boolconv.cocci warnings
      riscv: Explicit comment about user virtual address space size
      riscv: Use pgtable_l4_enabled to output mmu_type in cpuinfo
      riscv: Implement sv48 support
      asm-generic: Prepare for riscv use of pud_alloc_one and pud_free
      riscv: Allow to dynamically define VA_BITS
      riscv: Introduce functions to switch pt_ops
      riscv: Split early kasan mapping to prepare sv48 introduction
      riscv: Move KASAN mapping next to the kernel mapping
      ...

commit b21bae9af1da9b319b5f52ca8fcda76a26cd175a
Merge: 0854dc81e108c bb425a7598479
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:22:10 2022 +0200

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 fixes/cleanups from Catalin Marinas:
     "Some fixes that turned up during the merge window:
    
       - Add brackets to the io_stop_wc macro
    
       - Avoid -Warray-bounds warning with the LSE atomics inline asm
    
       - Apply __ro_after_init to memory_limit"
    
    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      arm64: mm: apply __ro_after_init to memory_limit
      arm64: atomics: lse: Dereference matching size
      asm-generic: Add missing brackets for io_stop_wc macro

commit 0854dc81e108c90cccda6d1fc54bc270f16a3cc9
Merge: 9b57f45898574 b0ac702f3329c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 22 09:02:57 2022 +0200

    Merge tag 'docs-5.17-2' of git://git.lwn.net/linux
    
    Pull documentation fixes from Jonathan Corbet:
     "Three small documentation fixes"
    
    * tag 'docs-5.17-2' of git://git.lwn.net/linux:
      Documentation: fix firewire.rst ABI file path error
      docs: ftrace: fix ambiguous sentence
      docs: staging/tee.rst: fix two typos found while reading

commit 6e61dde82e8bfe65e8ebbe43da45e615bc529236
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:15:14 2022 -0800

    mm: hide the FRONTSWAP Kconfig symbol
    
    Select FRONTSWAP from ZSWAP instead of prompting for it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-14-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1da0d94a3ec8c5f3793b7be8538b55e60ebeefe3
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:15:10 2022 -0800

    frontswap: remove support for multiple ops
    
    There is only a single instance of frontswap ops in the kernel, so
    simplify the frontswap code by removing support for multiple operations.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-13-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 633423a09cb5cfe61438283e1ce49c23cf4a0611
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:15:07 2022 -0800

    mm: mark swap_lock and swap_active_head static
    
    swap_lock and swap_active_head are only used in swapfile.c, so mark them
    static.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-12-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f328c1d16e4c764992895ac9c9425cea861b2ca0
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:15:04 2022 -0800

    frontswap: simplify frontswap_register_ops
    
    Given that frontswap_register_ops must be called from built-in code,
    there is no need to handle the case of swapfiles coming online before or
    during it, so delete the code that deals with that case.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-11-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bd9cd521496ba8d537d8f46f4167bf4221aba9a3
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:15:01 2022 -0800

    frontswap: remove frontswap_test
    
    frontswap_test is unused now, remove it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-10-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 10a9c496789fe2098bfc018650fc77b23ba08a54
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:57 2022 -0800

    mm: simplify try_to_unuse
    
    Remove the unused frontswap and pages_to_unuse arguments, and mark the
    function static now that the caller in frontswap is gone.
    
    [akpm@linux-foundation.org: fix shmem_unuse() stub, per Matthew]
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-9-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 360be5daa33fe74fc472195242ae2a2337c4320b
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:54 2022 -0800

    frontswap: remove the frontswap exports
    
    None of the frontswap API is called from modular code.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-8-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1cf53c894d15dd4b73397a56fa055d76d3db66b4
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:51 2022 -0800

    frontswap: simplify frontswap_init
    
    Just use IS_ENABLED() and remove the __frontswap_init indirection.
    
    Also remove the unused export.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-7-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3e8e1af63d7a831f576477c25d9b89049bd2d53d
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:47 2022 -0800

    frontswap: remove frontswap_curr_pages
    
    frontswap_curr_pages is never called, so remove it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-6-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0b364446d734da76e421dbfb09e5268270cefaf0
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:44 2022 -0800

    frontswap: remove frontswap_shrink
    
    frontswap_shrink is never called, so remove it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-5-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 71024cb4a0bfe7767aec7a128d0a1a13a37b7fcd
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:41 2022 -0800

    frontswap: remove frontswap_tmem_exclusive_gets
    
    frontswap_tmem_exclusive_gets is never called, so remove it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-4-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3d6035f136009f9cae380022754cba31f32570c5
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:38 2022 -0800

    frontswap: remove frontswap_writethrough
    
    frontswap_writethrough is never called, so remove it.
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-3-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0a4ee518185e902758191d968600399f3bc2be31
Author: Christoph Hellwig <hch@lst.de>
Date:   Fri Jan 21 22:14:34 2022 -0800

    mm: remove cleancache
    
    Patch series "remove Xen tmem leftovers".
    
    Since the removal of the Xen tmem driver in 2019, the cleancache hooks
    are entirely unused, as are large parts of frontswap.  This series
    against linux-next (with the folio changes included) removes
    cleancaches, and cuts down frontswap to the bits actually used by zswap.
    
    This patch (of 13):
    
    The cleancache subsystem is unused since the removal of Xen tmem driver
    in commit 814bbf49dcd0 ("xen: remove tmem driver").
    
    [akpm@linux-foundation.org: remove now-unreachable code]
    
    Link: https://lkml.kernel.org/r/20211224062246.1258487-1-hch@lst.de
    Link: https://lkml.kernel.org/r/20211224062246.1258487-2-hch@lst.de
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Konrad Rzeszutek Wilk <Konrad.wilk@oracle.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Seth Jennings <sjenning@redhat.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Cc: Vitaly Wool <vitaly.wool@konsulko.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e940066089490efde86abc519593be84362f4e53
Author: Marco Elver <elver@google.com>
Date:   Fri Jan 21 22:14:31 2022 -0800

    lib/stackdepot: always do filter_irq_stacks() in stack_depot_save()
    
    The non-interrupt portion of interrupt stack traces before interrupt
    entry is usually arbitrary.  Therefore, saving stack traces of
    interrupts (that include entries before interrupt entry) to stack depot
    leads to unbounded stackdepot growth.
    
    As such, use of filter_irq_stacks() is a requirement to ensure
    stackdepot can efficiently deduplicate interrupt stacks.
    
    Looking through all current users of stack_depot_save(), none (except
    KASAN) pass the stack trace through filter_irq_stacks() before passing
    it on to stack_depot_save().
    
    Rather than adding filter_irq_stacks() to all current users of
    stack_depot_save(), it became clear that stack_depot_save() should
    simply do filter_irq_stacks().
    
    Link: https://lkml.kernel.org/r/20211130095727.2378739-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reviewed-by: Alexander Potapenko <glider@google.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Vijayanand Jitta <vjitta@codeaurora.org>
    Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>
    Cc: Imran Khan <imran.f.khan@oracle.com>
    Cc: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2dba5eb1c73b6ba2988ced07250edeac0f8cbf5a
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Fri Jan 21 22:14:27 2022 -0800

    lib/stackdepot: allow optional init and stack_table allocation by kvmalloc()
    
    Currently, enabling CONFIG_STACKDEPOT means its stack_table will be
    allocated from memblock, even if stack depot ends up not actually used.
    The default size of stack_table is 4MB on 32-bit, 8MB on 64-bit.
    
    This is fine for use-cases such as KASAN which is also a config option
    and has overhead on its own.  But it's an issue for functionality that
    has to be actually enabled on boot (page_owner) or depends on hardware
    (GPU drivers) and thus the memory might be wasted.  This was raised as
    an issue [1] when attempting to add stackdepot support for SLUB's debug
    object tracking functionality.  It's common to build kernels with
    CONFIG_SLUB_DEBUG and enable slub_debug on boot only when needed, or
    create only specific kmem caches with debugging for testing purposes.
    
    It would thus be more efficient if stackdepot's table was allocated only
    when actually going to be used.  This patch thus makes the allocation
    (and whole stack_depot_init() call) optional:
    
     - Add a CONFIG_STACKDEPOT_ALWAYS_INIT flag to keep using the current
       well-defined point of allocation as part of mem_init(). Make
       CONFIG_KASAN select this flag.
    
     - Other users have to call stack_depot_init() as part of their own init
       when it's determined that stack depot will actually be used. This may
       depend on both config and runtime conditions. Convert current users
       which are page_owner and several in the DRM subsystem. Same will be
       done for SLUB later.
    
     - Because the init might now be called after the boot-time memblock
       allocation has given all memory to the buddy allocator, change
       stack_depot_init() to allocate stack_table with kvmalloc() when
       memblock is no longer available. Also handle allocation failure by
       disabling stackdepot (could have theoretically happened even with
       memblock allocation previously), and don't unnecessarily align the
       memblock allocation to its own size anymore.
    
    [1] https://lore.kernel.org/all/CAMuHMdW=eoVzM1Re5FVoEN87nKfiLmM2+Ah7eNu2KXEhCvbZyA@mail.gmail.com/
    
    Link: https://lkml.kernel.org/r/20211013073005.11351-1-vbabka@suse.cz
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: Dmitry Vyukov <dvyukov@google.com>
    Reviewed-by: Marco Elver <elver@google.com> # stackdepot
    Cc: Marco Elver <elver@google.com>
    Cc: Vijayanand Jitta <vjitta@codeaurora.org>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Oliver Glitta <glittao@gmail.com>
    Cc: Imran Khan <imran.f.khan@oracle.com>
    From: Colin Ian King <colin.king@canonical.com>
    Subject: lib/stackdepot: fix spelling mistake and grammar in pr_err message
    
    There is a spelling mistake of the work allocation so fix this and
    re-phrase the message to make it easier to read.
    
    Link: https://lkml.kernel.org/r/20211015104159.11282-1-colin.king@canonical.com
    Signed-off-by: Colin Ian King <colin.king@canonical.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    From: Vlastimil Babka <vbabka@suse.cz>
    Subject: lib/stackdepot: allow optional init and stack_table allocation by kvmalloc() - fixup
    
    On FLATMEM, we call page_ext_init_flatmem_late() just before
    kmem_cache_init() which means stack_depot_init() (called by page owner
    init) will not recognize properly it should use kvmalloc() and not
    memblock_alloc().  memblock_alloc() will also not issue a warning and
    return a block memory that can be invalid and cause kernel page fault when
    saving stacks, as reported by the kernel test robot [1].
    
    Fix this by moving page_ext_init_flatmem_late() below kmem_cache_init() so
    that slab_is_available() is true during stack_depot_init().  SPARSEMEM
    doesn't have this issue, as it doesn't do page_ext_init_flatmem_late(),
    but a different page_ext_init() even later in the boot process.
    
    Thanks to Mike Rapoport for pointing out the FLATMEM init ordering issue.
    
    While at it, also actually resolve a checkpatch warning in stack_depot_init()
    from DRM CI, which was supposed to be in the original patch already.
    
    [1] https://lore.kernel.org/all/20211014085450.GC18719@xsang-OptiPlex-9020/
    
    Link: https://lkml.kernel.org/r/6abd9213-19a9-6d58-cedc-2414386d2d81@suse.cz
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    From: Vlastimil Babka <vbabka@suse.cz>
    Subject: lib/stackdepot: allow optional init and stack_table allocation by kvmalloc() - fixup3
    
    Due to cd06ab2fd48f ("drm/locking: add backtrace for locking contended
    locks without backoff") landing recently to -next adding a new stack depot
    user in drivers/gpu/drm/drm_modeset_lock.c we need to add an appropriate
    call to stack_depot_init() there as well.
    
    Link: https://lkml.kernel.org/r/2a692365-cfa1-64f2-34e0-8aa5674dce5e@suse.cz
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
    Cc: Marco Elver <elver@google.com>
    Cc: Vijayanand Jitta <vjitta@codeaurora.org>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Oliver Glitta <glittao@gmail.com>
    Cc: Imran Khan <imran.f.khan@oracle.com>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    From: Vlastimil Babka <vbabka@suse.cz>
    Subject: lib/stackdepot: allow optional init and stack_table allocation by kvmalloc() - fixup4
    
    Due to 4e66934eaadc ("lib: add reference counting tracking
    infrastructure") landing recently to net-next adding a new stack depot
    user in lib/ref_tracker.c we need to add an appropriate call to
    stack_depot_init() there as well.
    
    Link: https://lkml.kernel.org/r/45c1b738-1a2f-5b5f-2f6d-86fab206d01c@suse.cz
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Cc: Jiri Slab <jirislaby@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 359745d78351c6f5442435f81549f0207ece28aa
Author: Muchun Song <songmuchun@bytedance.com>
Date:   Fri Jan 21 22:14:23 2022 -0800

    proc: remove PDE_DATA() completely
    
    Remove PDE_DATA() completely and replace it with pde_data().
    
    [akpm@linux-foundation.org: fix naming clash in drivers/nubus/proc.c]
    [akpm@linux-foundation.org: now fix it properly]
    
    Link: https://lkml.kernel.org/r/20211124081956.87711-2-songmuchun@bytedance.com
    Signed-off-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Alexey Dobriyan <adobriyan@gmail.com>
    Cc: Alexey Gladkov <gladkov.alexey@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6dfbbae14a7b961f41d80a106e1ab60e86d061c5
Author: Muchun Song <songmuchun@bytedance.com>
Date:   Fri Jan 21 22:14:20 2022 -0800

    fs: proc: store PDE()->data into inode->i_private
    
    PDE_DATA(inode) is introduced to get user private data and hide the
    layout of struct proc_dir_entry.  The inode->i_private is used to do the
    same thing as well.  Save a copy of user private data to inode->
    i_private when proc inode is allocated.  This means the user also can
    get their private data by inode->i_private.
    
    Introduce pde_data() to wrap inode->i_private so that we can remove
    PDE_DATA() from fs/proc/generic.c and make PTE_DATE() as a wrapper of
    pde_data().  It will be easier if we decide to remove PDE_DATE() in the
    future.
    
    Link: https://lkml.kernel.org/r/20211124081956.87711-1-songmuchun@bytedance.com
    Signed-off-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Alexey Dobriyan <adobriyan@gmail.com>
    Cc: Alexey Gladkov <gladkov.alexey@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a37265995c867a4e413761d846cef0445b08d6d5
Author: Mike Galbraith <umgwanakikbuti@gmail.com>
Date:   Fri Jan 21 22:14:17 2022 -0800

    zsmalloc: replace get_cpu_var with local_lock
    
    The usage of get_cpu_var() in zs_map_object() is problematic because it
    disables preemption and makes it impossible to acquire any sleeping lock
    on PREEMPT_RT such as a spinlock_t.
    
    Replace the get_cpu_var() usage with a local_lock_t which is embedded
    struct mapping_area.  It ensures that the access the struct is
    synchronized against all users on the same CPU.
    
    [minchan: remove the bit_spin_lock part and change the title]
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-10-minchan@kernel.org
    Signed-off-by: Mike Galbraith <umgwanakikbuti@gmail.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b475d42d2c43321d8bea685f54916220cb76b511
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:14:13 2022 -0800

    zsmalloc: replace per zpage lock with pool->migrate_lock
    
    The zsmalloc has used a bit for spin_lock in zpage handle to keep zpage
    object alive during several operations.  However, it causes the problem
    for PREEMPT_RT as well as introducing too complicated.
    
    This patch replaces the bit spin_lock with pool->migrate_lock rwlock.
    It could make the code simple as well as zsmalloc work under PREEMPT_RT.
    
    The drawback is the pool->migrate_lock is bigger granuarity than per
    zpage lock so the contention would be higher than old when both
    IO-related operations(i.e., zsmalloc, zsfree, zs_[map|unmap]) and
    compaction(page/zpage migration) are going in parallel(*, the
    migrate_lock is rwlock and IO related functions are all read side lock
    so there is no contention).  However, the write-side is fast
    enough(dominant overhead is just page copy) so it wouldn't affect much.
    If the lock granurity becomes more problem later, we could introduce
    table locks based on handle as a hash value.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-9-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4a57d6bbaecd28c8175dc5da013009e4158018c2
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:14:10 2022 -0800

    locking/rwlocks: introduce write_lock_nested
    
    In preparation for converting bit_spin_lock to rwlock in zsmalloc so
    that multiple writers of zspages can run at the same time but those
    zspages are supposed to be different zspage instance.  Thus, it's not
    deadlock.  This patch adds write_lock_nested to support the case for
    LOCKDEP.
    
    [minchan@kernel.org: fix write_lock_nested for RT]
      Link: https://lkml.kernel.org/r/YZfrMTAXV56HFWJY@google.com
    [bigeasy@linutronix.de: fixup write_lock_nested() implementation]
      Link: https://lkml.kernel.org/r/20211123170134.y6xb7pmpgdn4m3bn@linutronix.de
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-8-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c4549b871102db01ba23cce4bd0cdac511f8991d
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:14:07 2022 -0800

    zsmalloc: remove zspage isolation for migration
    
    zspage isolation for migration introduced additional exceptions to be
    dealt with since the zspage was isolated from class list.  The reason
    why I isolated zspage from class list was to prevent race between
    obj_malloc and page migration via allocating zpage from the zspage
    further.  However, it couldn't prevent object freeing from zspage so it
    needed corner case handling.
    
    This patch removes the whole mess.  Now, we are fine since class->lock
    and zspage->lock can prevent the race.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-7-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a41ec880aa7beeabcb3bfa476ef35b23f376133b
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:14:04 2022 -0800

    zsmalloc: move huge compressed obj from page to zspage
    
    The flag aims for zspage, not per page.  Let's move it to zspage.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-6-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3ae92ac23bd88ed18c43a5b138d5a91252c31d2a
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:14:01 2022 -0800

    zsmalloc: introduce obj_allocated
    
    The usage pattern for obj_to_head is to check whether the zpage is
    allocated or not.  Thus, introduce obj_allocated.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-5-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0a5f079b810765be3bd931fce0f88154035af897
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:13:57 2022 -0800

    zsmalloc: decouple class actions from zspage works
    
    This patch moves class stat update out of obj_malloc since it's not
    related to zspage operation.  This is a preparation to introduce new
    lock scheme in next patch.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-4-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3828a76470792aaa5f2de5c0d7fce497187c1e35
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:13:54 2022 -0800

    zsmalloc: rename zs_stat_type to class_stat_type
    
    The stat aims for class stat, not zspage so rename it.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-3-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 67f1c9cd0c561d25354c1e289cdd0d77d3112513
Author: Minchan Kim <minchan@kernel.org>
Date:   Fri Jan 21 22:13:51 2022 -0800

    zsmalloc: introduce some helper functions
    
    Patch series "zsmalloc: remove bit_spin_lock", v2.
    
    zsmalloc uses bit_spin_lock to minimize space overhead since it's zpage
    granularity lock.  However, it causes zsmalloc non-working under
    PREEMPT_RT as well as adding too much complication.
    
    This patchset tries to replace the bit_spin_lock with per-pool rwlock.
    It also removes unnecessary zspage isolation logic from class, which was
    the other part too much complication added into zsmalloc.
    
    Last patch changes the get_cpu_var to local_lock to make it work in
    PREEMPT_RT.
    
    This patch (of 9):
    
    get_zspage_mapping returns fullness as well as class_idx.  However, the
    fullness is usually not used since it could be stale in some contexts.
    It causes misleading as well as unnecessary instructions so this patch
    introduces zspage_class.
    
    obj_to_location also produces page and index but we don't need always
    the index, either so this patch introduces obj_to_page.
    
    Link: https://lkml.kernel.org/r/20211115185909.3949505-1-minchan@kernel.org
    Link: https://lkml.kernel.org/r/20211115185909.3949505-2-minchan@kernel.org
    Signed-off-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Tested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Mike Galbraith <umgwanakikbuti@gmail.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1622ed7d0743201293094162c26019d2573ecacb
Author: Baokun Li <libaokun1@huawei.com>
Date:   Fri Jan 21 22:13:48 2022 -0800

    sysctl: returns -EINVAL when a negative value is passed to proc_doulongvec_minmax
    
    When we pass a negative value to the proc_doulongvec_minmax() function,
    the function returns 0, but the corresponding interface value does not
    change.
    
    we can easily reproduce this problem with the following commands:
    
        cd /proc/sys/fs/epoll
        echo -1 > max_user_watches; echo $?; cat max_user_watches
    
    This function requires a non-negative number to be passed in, so when a
    negative number is passed in, -EINVAL is returned.
    
    Link: https://lkml.kernel.org/r/20211220092627.3744624-1-libaokun1@huawei.com
    Signed-off-by: Baokun Li <libaokun1@huawei.com>
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e565a8ed1ee4b481539b66cd6f54df9ecf1e9861
Author: Colin Ian King <colin.king@intel.com>
Date:   Fri Jan 21 22:13:45 2022 -0800

    kernel/sysctl.c: remove unused variable ten_thousand
    
    The const variable ten_thousand is not used, it is redundant and can be
    removed.
    
    Cleans up clang warning:
    
      kernel/sysctl.c:99:18: warning: unused variable 'ten_thousand' [-Wunused-const-variable]
      static const int ten_thousand = 10000;
    
    Link: https://lkml.kernel.org/r/20211221184501.574670-1-colin.i.king@gmail.com
    Fixes: c26da54dc8ca ("printk: move printk sysctl to printk/sysctl.c")
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a737a3c6744bc822d1e6a837fef550e665ddf877
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:13:41 2022 -0800

    kprobe: move sysctl_kprobes_optimization to kprobes.c
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    Move sysctl_kprobes_optimization from kernel/sysctl.c to
    kernel/kprobes.c.  Use register_sysctl() to register the sysctl
    interface.
    
    [mcgrof@kernel.org: fix compile issue when CONFIG_OPTPROBES is disabled]
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-7-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f0bc21b268c1464603192a00851cdbbf7c2cdc36
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:13:38 2022 -0800

    fs/coredump: move coredump sysctls into its own file
    
    This moves the fs/coredump.c respective sysctls to its own file.
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-6-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit fdcd4073fccc6f989308be3f1d61d8a68cd990ce
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:13:34 2022 -0800

    printk: fix build warning when CONFIG_PRINTK=n
    
    build warning when CONFIG_PRINTK=n
    
            kernel/printk/printk.c:175:5: warning: no previous prototype for
             'devkmsg_sysctl_set_loglvl' [-Wmissing-prototypes]
    
    devkmsg_sysctl_set_loglvl() is only used in sysctl.c when
    CONFIG_PRINTK=y, but it participates in the build when CONFIG_PRINTK=n.
    So add compile dependency CONFIG_PRINTK=y && CONFIG_SYSCTL=y to fix the
    build warning.
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-5-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d8c0418aac78e661b5283c9d6a1dfc61d44f26fd
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:31 2022 -0800

    kernel/sysctl.c: rename sysctl_init() to sysctl_init_bases()
    
    Rename sysctl_init() to sysctl_init_bases() so to reflect exactly what
    this is doing.
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-4-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ab171b952c6e065779687b44041038efdadb3915
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:27 2022 -0800

    fs: move namespace sysctls and declare fs base directory
    
    This moves the namespace sysctls to its own file as part of the
    kernel/sysctl.c spring cleaning
    
    Since we have now removed all sysctls for "fs", we now have to declare
    it on the filesystem code, we do that using the new helper, which
    reduces boiler plate code.
    
    We rename init_fs_shared_sysctls() to init_fs_sysctls() to reflect that
    now fs/sysctls.c is taking on the burden of being the first to register
    the base directory as well.
    
    Lastly, since init code will load in the order in which we link it we
    have to move the sysctl code to be linked in early, so that its early
    init routine runs prior to other fs code.  This way, other filesystem
    code can register their own sysctls using the helpers after this:
    
      * register_sysctl_init()
      * register_sysctl()
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-3-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 51cb8dfc5a5c39e6c70376b9dc9a14d624a9d271
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:24 2022 -0800

    sysctl: add and use base directory declarer and registration helper
    
    Patch series "sysctl: add and use base directory declarer and
    registration helper".
    
    In this patch series we start addressing base directories, and so we
    start with the "fs" sysctls.  The end goal is we end up completely
    moving all "fs" sysctl knobs out from kernel/sysctl.
    
    This patch (of 6):
    
    Add a set of helpers which can be used to declare and register base
    directory sysctls on their own.  We do this so we can later move each of
    the base sysctl directories like "fs", "kernel", etc, to their own
    respective files instead of shoving the declarations and registrations
    all on kernel/sysctl.c.  The lazy approach has caught up and with this,
    we just end up extending the list of base directories / sysctls on one
    file and this makes maintenance difficult due to merge conflicts from
    many developers.
    
    The declarations are used first by kernel/sysctl.c for registration its
    own base which over time we'll try to clean up.  It will be used in the
    next patch to demonstrate how to cleanly deal with base sysctl
    directories.
    
    [mcgrof@kernel.org: null-terminate the ctl_table arrays]
      Link: https://lkml.kernel.org/r/YafJY3rXDYnjK/gs@bombadil.infradead.org
    
    Link: https://lkml.kernel.org/r/20211129211943.640266-1-mcgrof@kernel.org
    Link: https://lkml.kernel.org/r/20211129211943.640266-2-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Eric Biggers <ebiggers@google.com>
    Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1998f19324d24df7de4e74d81503b4299eb99e7d
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:20 2022 -0800

    fs: move pipe sysctls to is own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the pipe sysctls to its own file.
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-10-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 66ad398634c21e0a42ce10002ae06c39352da0d1
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:17 2022 -0800

    fs: move fs/exec.c sysctls into its own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the fs/exec.c respective sysctls to its own file.
    
    Since checkpatch complains about style issues with the old code, this
    move also fixes a few of those minor style issues:
    
      * Use pr_warn() instead of prink(WARNING
      * New empty lines are wanted at the beginning of routines
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-9-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9c011be132972ff94bde2ae99064e29f94e85c68
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:13 2022 -0800

    fs: move namei sysctls to its own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move namei's own sysctl knobs to its own file.
    
    Other than the move we also avoid initializing two static variables to 0
    as this is not needed:
    
      * sysctl_protected_symlinks
      * sysctl_protected_hardlinks
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-8-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dd81faa88340a1fe8cd81c8ecbadd8e95c58549c
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:10 2022 -0800

    fs: move locking sysctls where they are used
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    The locking fs sysctls are only used on fs/locks.c, so move them there.
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-7-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d1d8ac9edf10e83f16d13f009439585a1f93ccb2
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:06 2022 -0800

    fs: move shared sysctls to fs/sysctls.c
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move sysctls which are shared between filesystems into a common file
    outside of kernel/sysctl.c.
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-6-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 54771613e8a7dbbba2a205ddf1b33e25a290b3fd
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:13:03 2022 -0800

    sysctl: move maxolduid as a sysctl specific const
    
    The maxolduid value is only shared for sysctl purposes for use on a max
    range.  Just stuff this into our shared const array.
    
    [akpm@linux-foundation.org: fix sysctl_vals[], per Mickaël]
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-5-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Mickaël Salaün <mic@digikod.net>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c8c0c239d5ab1e3e8d2bb0453ce642fe2c6357ec
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:59 2022 -0800

    fs: move dcache sysctls to its own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the dcache sysctl clutter out of kernel/sysctl.c.  This is a
    small one-off entry, perhaps later we can simplify this representation,
    but for now we use the helpers we have.  We won't know how we can
    simplify this further untl we're fully done with the cleanup.
    
    [arnd@arndb.de: avoid unused-function warning]
      Link: https://lkml.kernel.org/r/20211203190123.874239-2-arnd@kernel.org
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-4-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 204d5a24e15562b2816825c0f9b49d26814b77be
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:56 2022 -0800

    fs: move fs stat sysctls to file_table.c
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    We can create the sysctl dynamically on early init for fs stat to help
    with this clutter.  This dusts off the fs stat syctls knobs and puts
    them into where they are declared.
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-3-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1d67fe585049d3e2448b997af78c68cbf90ada09
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:52 2022 -0800

    fs: move inode sysctls to its own file
    
    Patch series "sysctl: 4th set of kernel/sysctl cleanups".
    
    This is slimming down the fs uses of kernel/sysctl.c to the point that
    the next step is to just get rid of the fs base directory for it and
    move that elsehwere, so that next patch series starts dealing with that
    to demo how we can end up cleaning up a full base directory from
    kernel/sysctl.c, one at a time.
    
    This patch (of 9):
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the inode sysctls to its own file.  Since we are no longer using
    this outside of fs/ remove the extern declaration of its respective proc
    helper.
    
    We use early_initcall() as it is the earliest we can use.
    
    [arnd@arndb.de: avoid unused-variable warning]
      Link: https://lkml.kernel.org/r/20211203190123.874239-1-arnd@kernel.org
    
    Link: https://lkml.kernel.org/r/20211129205548.605569-1-mcgrof@kernel.org
    Link: https://lkml.kernel.org/r/20211129205548.605569-2-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b1f2aff888af54a057c2c3c0d88a13ef5d37b52a
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:48 2022 -0800

    sysctl: share unsigned long const values
    
    Provide a way to share unsigned long values.  This will allow others to
    not have to re-invent these values.
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-9-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0df8bdd5e3b3e557ce2c2575fce0c64c5dd1045a
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:43 2022 -0800

    stackleak: move stack_erasing sysctl to stackleak.c
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the stack_erasing sysctl from kernel/sysctl.c to
    kernel/stackleak.c and use register_sysctl() to register the sysctl
    interface.
    
    [mcgrof@kernel.org: commit log update]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-8-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 26d1c80fd61e59d5e2eb6fda00e0148a6704ddeb
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:38 2022 -0800

    scsi/sg: move sg-big-buff sysctl to scsi/sg.c
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the sg-big-buff sysctl from kernel/sysctl.c to drivers/scsi/sg.c
    and use register_sysctl() to register the sysctl interface.
    
    [mcgrof@kernel.org: commit log update]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-7-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit faaa357a55e03490fb280ac211be2298e635b220
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:33 2022 -0800

    printk: move printk sysctl to printk/sysctl.c
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move printk sysctl from kernel/sysctl.c to kernel/printk/sysctl.c.
    Use register_sysctl() to register the sysctl interface.
    
    [mcgrof@kernel.org: fixed compile issues when PRINTK is not set, commit log update]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-6-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3ba442d5331ff4d4339faf4986d0841386196f92
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:28 2022 -0800

    fs: move binfmt_misc sysctl to its own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    This moves the binfmt_misc sysctl to its own file to help remove clutter
    from kernel/sysctl.c.
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-5-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ee9efac48a082904d17a20131aa73d82f058cdd6
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:23 2022 -0800

    sysctl: add helper to register a sysctl mount point
    
    The way to create a subdirectory on top of sysctl_mount_point is a bit
    obscure, and *why* we do that even so more.  Provide a helper which
    makes it clear why we do this.
    
    [akpm@linux-foundation.org: export register_sysctl_mount_point() to
    modules]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-4-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Suggested-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5475e8f03c80bbce7b43a57d861f5acc44a60b22
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:18 2022 -0800

    random: move the random sysctl declarations to its own file
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the random sysctls to their own file and use
    register_sysctl_init().
    
    [mcgrof@kernel.org: commit log update to justify the move]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-3-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6aad36d421d8bfe156508fa4edfe67827234cf0f
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:13 2022 -0800

    firmware_loader: move firmware sysctl to its own files
    
    Patch series "sysctl: 3rd set of kernel/sysctl cleanups", v2.
    
    This is the third set of patches to help address cleaning the kitchen
    seink in kernel/sysctl.c and to move sysctls away to where they are
    actually implemented / used.
    
    This patch (of 8):
    
    kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the firmware configuration sysctl table to the only place where
    it is used, and make it clear that if sysctls are disabled this is not
    used.
    
    [akpm@linux-foundation.org: export register_firmware_config_sysctl and unregister_firmware_config_sysctl to modules]
    [akpm@linux-foundation.org: use EXPORT_SYMBOL_NS_GPL instead]
    [sfr@canb.auug.org.au: fix that so it compiles]
      Link: https://lkml.kernel.org/r/20211201160626.401d828d@canb.auug.org.au
    [mcgrof@kernel.org: major commit log update to justify the move]
    
    Link: https://lkml.kernel.org/r/20211124231435.1445213-1-mcgrof@kernel.org
    Link: https://lkml.kernel.org/r/20211124231435.1445213-2-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a8f5de894f76f1c73f4a068d04897a5e2f873825
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:12:09 2022 -0800

    eventpoll: simplify sysctl declaration with register_sysctl()
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move the epoll_table sysctl to fs/eventpoll.c and use
    register_sysctl().
    
    Link: https://lkml.kernel.org/r/20211123202422.819032-9-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ad8f74315b335c55f3d8bd7c37d21d6c74d1be20
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:12:04 2022 -0800

    cdrom: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci PATH
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    Link: https://lkml.kernel.org/r/20211123202422.819032-8-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7b9ad122b52c9839e1f68f16c907990a6ad6f793
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:59 2022 -0800

    inotify: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    Move inotify_user sysctl to inotify_user.c while at it to remove clutter
    from kernel/sysctl.c.
    
    [mcgrof@kernel.org: remember to register fanotify_table]
      Link: https://lkml.kernel.org/r/YZ5A6iWLb0h3N3RC@bombadil.infradead.org
    [mcgrof@kernel.org: update commit log to reflect new path we decided to take]
    
    Link: https://lkml.kernel.org/r/20211123202422.819032-7-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 04bc883c986d9c8a64fc1f1cc2cbc328c2b2a496
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:11:54 2022 -0800

    test_sysctl: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci lib/test_sysctl.c
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    Link: https://lkml.kernel.org/r/20211123202422.819032-6-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c42ff46f97c1c25577a84fbfb111710d25a129e0
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:11:49 2022 -0800

    ocfs2: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci PATH
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    Link: https://lkml.kernel.org/r/20211123202422.819032-5-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e99f5e7479110868ac04c5f6593a15c2da61f969
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:11:44 2022 -0800

    macintosh/mac_hid.c: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci PATH
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    Link: https://lkml.kernel.org/r/20211123202422.819032-4-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e5a1fd997cc2deda1b08d5faae04625de0440a1e
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:11:39 2022 -0800

    i915: simplify subdirectory registration with register_sysctl()
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci PATH
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    Link: https://lkml.kernel.org/r/20211123202422.819032-3-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Acked-by: Jani Nikula <jani.nikula@intel.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c8dd55410ba07de602169e037cbb62e495ad1880
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 21 22:11:34 2022 -0800

    hpet: simplify subdirectory registration with register_sysctl()
    
    Patch series "sysctl: second set of kernel/sysctl cleanups", v2.
    
    This is the 2nd set of kernel/sysctl.c cleanups.  The diff stat should
    reflect how this is a much better way to deal with theses.  Fortunately
    coccinelle can be used to ensure correctness for most of these and/or
    future merge conflicts.
    
    Note that since this is part of a larger effort to cleanup
    kernel/sysctl.c I think we have no other option but to go with merging
    these patches in either Andrew's tree or keep them staged in a separate
    tree and send a merge request later.  Otherwise kernel/sysctl.c will end
    up becoming a sore spot for the next merge window.
    
    This patch (of 8):
    
    There is no need to user boiler plate code to specify a set of base
    directories we're going to stuff sysctls under.  Simplify this by using
    register_sysctl() and specifying the directory path directly.
    
    // pycocci sysctl-subdir-register-sysctl-simplify.cocci drivers/char/hpet.c
    
    @c1@
    expression E1;
    identifier subdir, sysctls;
    @@
    
    static struct ctl_table subdir[] = {
            {
                    .procname = E1,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = sysctls,
            },
            { }
    };
    
    @c2@
    identifier c1.subdir;
    
    expression E2;
    identifier base;
    @@
    
    static struct ctl_table base[] = {
            {
                    .procname = E2,
                    .maxlen = 0,
                    .mode = 0555,
                    .child = subdir,
            },
            { }
    };
    
    @c3@
    identifier c2.base;
    identifier header;
    @@
    
    header = register_sysctl_table(base);
    
    @r1 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.subdir, c1.sysctls;
    @@
    
    -static struct ctl_table subdir[] = {
    -       {
    -               .procname = E1,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = sysctls,
    -       },
    -       { }
    -};
    
    @r2 depends on c1 && c2 && c3@
    identifier c1.subdir;
    
    expression c2.E2;
    identifier c2.base;
    @@
    -static struct ctl_table base[] = {
    -       {
    -               .procname = E2,
    -               .maxlen = 0,
    -               .mode = 0555,
    -               .child = subdir,
    -       },
    -       { }
    -};
    
    @initialize:python@
    @@
    
    def make_my_fresh_expression(s1, s2):
      return '"' + s1.strip('"') + "/" + s2.strip('"') + '"'
    
    @r3 depends on c1 && c2 && c3@
    expression c1.E1;
    identifier c1.sysctls;
    expression c2.E2;
    identifier c2.base;
    identifier c3.header;
    fresh identifier E3 = script:python(E2, E1) { make_my_fresh_expression(E2, E1) };
    @@
    
    header =
    -register_sysctl_table(base);
    +register_sysctl(E3, sysctls);
    
    Generated-by: Coccinelle SmPL
    
    Link: https://lkml.kernel.org/r/20211123202422.819032-1-mcgrof@kernel.org
    Link: https://lkml.kernel.org/r/20211123202422.819032-2-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 49a4de75719b6c0f1f375df9908a95cef1e34945
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:29 2022 -0800

    dnotify: move dnotify sysctl to dnotify.c
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move dnotify sysctls to dnotify.c and use the new
    register_sysctl_init() to register the sysctl interface.
    
    [mcgrof@kernel.org: adjust the commit log to justify the move]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-10-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Acked-by: Jan Kara <jack@suse.cz>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 86b12b6c5d6b46e64bf2e8080528781032e4bd90
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:24 2022 -0800

    aio: move aio sysctl to aio.c
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    Move aio sysctl to aio.c and use the new register_sysctl_init() to
    register the sysctl interface for aio.
    
    [mcgrof@kernel.org: adjust commit log to justify the move]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-9-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2452dcb9f7f2bab5b47344148bc23a732be9195c
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:19 2022 -0800

    sysctl: use SYSCTL_ZERO to replace some static int zero uses
    
    Use the variable SYSCTL_ZERO to replace some static int boundary
    variables with a value of 0 (minolduid, min_extfrag_threshold,
    min_wakeup_granularity_ns).
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-8-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d73840ec2f747b860331bbba53677d0ce38fb9c1
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:14 2022 -0800

    sysctl: use const for typically used max/min proc sysctls
    
    When proc_dointvec_minmax() or proc_doulongvec_minmax() are used we are
    using the extra1 and extra2 parameters on the sysctl table only for a
    min and max boundary, these extra1 and extra2 arguments are then used
    for read-only operations.  So make them const to reflect this.
    
    [mcgrof@kernel.org: commit log love]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-7-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f628867da46f8867e1854e43d7200e42ec22eee2
Author: Stephen Kitt <steve@sk2.org>
Date:   Fri Jan 21 22:11:09 2022 -0800

    sysctl: make ngroups_max const
    
    ngroups_max is a read-only sysctl entry, reflecting NGROUPS_MAX.  Make
    it const, in the same way as cap_last_cap.
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-6-mcgrof@kernel.org
    Signed-off-by: Stephen Kitt <steve@sk2.org>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Xiaoming Ni <nixiaoming@huawei.com>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dd0693fdf054f2ed37202ed56649ae2cccd29474
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:05 2022 -0800

    watchdog: move watchdog sysctl interface to watchdog.c
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic of proc sysctl.
    
    So, move the watchdog syscl interface to watchdog.c.  Use
    register_sysctl() to register the sysctl interface to avoid merge
    conflicts when different features modify sysctl.c at the same time.
    
    [mcgrof@kernel.org: justify the move on the commit log]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-5-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Petr Mladek <pmladek@suse.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bbe7a10ed83a5fa0b0ff6161ecdc4e65a0e9c993
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:11:00 2022 -0800

    hung_task: move hung_task sysctl interface to hung_task.c
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    So move hung_task sysctl interface to hung_task.c and use
    register_sysctl() to register the sysctl interface.
    
    [mcgrof@kernel.org: commit log refresh and fixed 2-3 0day reported compile issues]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-4-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Petr Mladek <pmladek@suse.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 78e36f3b0dae586f623c4a37ec5eb5496f5abbe1
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:10:55 2022 -0800

    sysctl: move some boundary constants from sysctl.c to sysctl_vals
    
    sysctl has helpers which let us specify boundary values for a min or max
    int value.  Since these are used for a boundary check only they don't
    change, so move these variables to sysctl_vals to avoid adding duplicate
    variables.  This will help with our cleanup of kernel/sysctl.c.
    
    [akpm@linux-foundation.org: update it for "mm/pagealloc: sysctl: change watermark_scale_factor max limit to 30%"]
    [mcgrof@kernel.org: major rebase]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-3-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3ddd9a808cee7284931312f2f3e854c9617f44b2
Author: Xiaoming Ni <nixiaoming@huawei.com>
Date:   Fri Jan 21 22:10:50 2022 -0800

    sysctl: add a new register_sysctl_init() interface
    
    Patch series "sysctl: first set of kernel/sysctl cleanups", v2.
    
    Finally had time to respin the series of the work we had started last
    year on cleaning up the kernel/sysct.c kitchen sink.  People keeps
    stuffing their sysctls in that file and this creates a maintenance
    burden.  So this effort is aimed at placing sysctls where they actually
    belong.
    
    I'm going to split patches up into series as there is quite a bit of
    work.
    
    This first set adds register_sysctl_init() for uses of registerting a
    sysctl on the init path, adds const where missing to a few places,
    generalizes common values so to be more easy to share, and starts the
    move of a few kernel/sysctl.c out where they belong.
    
    The majority of rework on v2 in this first patch set is 0-day fixes.
    Eric Biederman's feedback is later addressed in subsequent patch sets.
    
    I'll only post the first two patch sets for now.  We can address the
    rest once the first two patch sets get completely reviewed / Acked.
    
    This patch (of 9):
    
    The kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
    dishes, this makes it very difficult to maintain.
    
    To help with this maintenance let's start by moving sysctls to places
    where they actually belong.  The proc sysctl maintainers do not want to
    know what sysctl knobs you wish to add for your own piece of code, we
    just care about the core logic.
    
    Today though folks heavily rely on tables on kernel/sysctl.c so they can
    easily just extend this table with their needed sysctls.  In order to
    help users move their sysctls out we need to provide a helper which can
    be used during code initialization.
    
    We special-case the initialization use of register_sysctl() since it
    *is* safe to fail, given all that sysctls do is provide a dynamic
    interface to query or modify at runtime an existing variable.  So the
    use case of register_sysctl() on init should *not* stop if the sysctls
    don't end up getting registered.  It would be counter productive to stop
    boot if a simple sysctl registration failed.
    
    Provide a helper for init then, and document the recommended init levels
    to use for callers of this routine.  We will later use this in
    subsequent patches to start slimming down kernel/sysctl.c tables and
    moving sysctl registration to the code which actually needs these
    sysctls.
    
    [mcgrof@kernel.org: major commit log and documentation rephrasing also moved to fs/proc/proc_sysctl.c                  ]
    
    Link: https://lkml.kernel.org/r/20211123202347.818157-1-mcgrof@kernel.org
    Link: https://lkml.kernel.org/r/20211123202347.818157-2-mcgrof@kernel.org
    Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Paul Turner <pjt@google.com>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Sebastian Reichel <sre@kernel.org>
    Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Qing Wang <wangqing@vivo.com>
    Cc: Benjamin LaHaise <bcrl@kvack.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Amir Goldstein <amir73il@gmail.com>
    Cc: Stephen Kitt <steve@sk2.org>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Clemens Ladisch <clemens@ladisch.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Julia Lawall <julia.lawall@inria.fr>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Phillip Potter <phil@philpotter.co.uk>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: Douglas Gilbert <dgilbert@interlog.com>
    Cc: James E.J. Bottomley <jejb@linux.ibm.com>
    Cc: Jani Nikula <jani.nikula@intel.com>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Martin K. Petersen <martin.petersen@oracle.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ffa65753c43142f3b803486442813744da71cff2
Author: Alistair Popple <apopple@nvidia.com>
Date:   Fri Jan 21 22:10:46 2022 -0800

    mm/migrate.c: rework migration_entry_wait() to not take a pageref
    
    This fixes the FIXME in migrate_vma_check_page().
    
    Before migrating a page migration code will take a reference and check
    there are no unexpected page references, failing the migration if there
    are.  When a thread faults on a migration entry it will take a temporary
    reference to the page to wait for the page to become unlocked signifying
    the migration entry has been removed.
    
    This reference is dropped just prior to waiting on the page lock,
    however the extra reference can cause migration failures so it is
    desirable to avoid taking it.
    
    As migration code already has a reference to the migrating page an extra
    reference to wait on PG_locked is unnecessary so long as the reference
    can't be dropped whilst setting up the wait.
    
    When faulting on a migration entry the ptl is taken to check the
    migration entry.  Removing a migration entry also requires the ptl, and
    migration code won't drop its page reference until after the migration
    entry has been removed.  Therefore retaining the ptl of a migration
    entry is sufficient to ensure the page has a reference.  Reworking
    migration_entry_wait() to hold the ptl until the wait setup is complete
    means the extra page reference is no longer needed.
    
    [apopple@nvidia.com: v5]
      Link: https://lkml.kernel.org/r/20211213033848.1973946-1-apopple@nvidia.com
    
    Link: https://lkml.kernel.org/r/20211118020754.954425-1-apopple@nvidia.com
    Signed-off-by: Alistair Popple <apopple@nvidia.com>
    Acked-by: David Hildenbrand <david@redhat.com>
    Cc: David Howells <dhowells@redhat.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jerome Glisse <jglisse@redhat.com>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Ralph Campbell <rcampbell@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit afa114d987c40e72ebbbc36bedf7d66b7cdc5883
Author: Justin Iurman <justin.iurman@uliege.be>
Date:   Fri Jan 21 18:34:49 2022 +0100

    selftests: net: ioam: expect support for Queue depth data
    
    The IOAM queue-depth data field was added a few weeks ago,
    but the test unit was not updated accordingly.
    
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Fixes: b63c5478e9cb ("ipv6: ioam: Support for Queue depth data field")
    Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
    Link: https://lore.kernel.org/r/20220121173449.26918-1-justin.iurman@uliege.be
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 63ec72bd58487935a2e40d2cdffe5c9498f1275e
Author: Kees Cook <keescook@chromium.org>
Date:   Thu Jan 20 23:39:35 2022 -0800

    mptcp: Use struct_group() to avoid cross-field memset()
    
    In preparation for FORTIFY_SOURCE performing compile-time and run-time
    field bounds checking for memcpy(), memmove(), and memset(), avoid
    intentionally writing across neighboring fields.
    
    Use struct_group() to capture the fields to be reset, so that memset()
    can be appropriately bounds-checked by the compiler.
    
    Cc: Matthieu Baerts <matthieu.baerts@tessares.net>
    Cc: mptcp@lists.linux.dev
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Link: https://lore.kernel.org/r/20220121073935.1154263-1-keescook@chromium.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 2c13c05c5ff4b9fc907b07f7311821910ebaaf8a
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 21 23:12:58 2022 +0000

    rxrpc: Adjust retransmission backoff
    
    Improve retransmission backoff by only backing off when we retransmit data
    packets rather than when we set the lost ack timer.
    
    To this end:
    
     (1) In rxrpc_resend(), use rxrpc_get_rto_backoff() when setting the
         retransmission timer and only tell it that we are retransmitting if we
         actually have things to retransmit.
    
         Note that it's possible for the retransmission algorithm to race with
         the processing of a received ACK, so we may see no packets needing
         retransmission.
    
     (2) In rxrpc_send_data_packet(), don't bump the backoff when setting the
         ack_lost_at timer, as it may then get bumped twice.
    
    With this, when looking at one particular packet, the retransmission
    intervals were seen to be 1.5ms, 2ms, 3ms, 5ms, 9ms, 17ms, 33ms, 71ms,
    136ms, 264ms, 544ms, 1.088s, 2.1s, 4.2s and 8.3s.
    
    Fixes: c410bf01933e ("rxrpc: Fix the excessive initial retransmission timeout")
    Suggested-by: Marc Dionne <marc.dionne@auristor.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Marc Dionne <marc.dionne@auristor.com>
    Tested-by: Marc Dionne <marc.dionne@auristor.com>
    cc: linux-afs@lists.infradead.org
    Link: https://lore.kernel.org/r/164138117069.2023386.17446904856843997127.stgit@warthog.procyon.org.uk/
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d24846a4246b6e61ecbd036880a4adf61681d241
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Thu Jan 20 12:18:12 2022 +0000

    parisc: pdc_stable: Fix memory leak in pdcs_register_pathentries
    
    kobject_init_and_add() takes reference even when it fails.
    According to the doc of kobject_init_and_add()：
    
       If this function returns an error, kobject_put() must be called to
       properly clean up the memory associated with the object.
    
    Fix memory leak by calling kobject_put().
    
    Fixes: 73f368cf679b ("Kobject: change drivers/parisc/pdc_stable.c to use kobject_init_and_add")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit cef0223191452b3c493a1070baad9ffe806babac
Author: Jeffle Xu <jefflexu@linux.alibaba.com>
Date:   Tue Dec 28 20:44:19 2021 +0800

    netfs: Make ops->init_rreq() optional
    
    Make the ops->init_rreq() callback optional.  This isn't required for the
    erofs changes I'm implementing to do on-demand read through fscache[1].
    Further, ceph has an empty init_rreq method that can then be removed and
    it's marked optional in the documentation.
    
    Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/20211227125444.21187-1-jefflexu@linux.alibaba.com/ [1]
    Link: https://lore.kernel.org/r/20211228124419.103020-1-jefflexu@linux.alibaba.com
    Link: https://lore.kernel.org/r/164251410387.3435901.2504600788262093313.stgit@warthog.procyon.org.uk/ # v1

commit c522e3ad296b7b692ed3960dfde467f2a34b434f
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 7 09:28:41 2022 +0000

    fscache: Add a comment explaining how page-release optimisation works
    
    Add a comment into fscache_note_page_release() to explain how the
    page-release optimisation logic works[1].  It's not entirely obvious as it
    has nothing to do with whether or not the netfs file contains data.
    
    FSCACHE_COOKIE_NO_DATA_TO_READ is set if we have no data in the cache yet
    (ie. the backing file lookup was negative, the file is 0 length or the
    cookie got invalidated).  It means that we have no data in the cache, not
    that the file is necessarily empty on the server.
    
    FSCACHE_COOKIE_HAVE_DATA is set once we've stored data in the backing file.
    From that point on, we have data we *could* read - however, it's covered by
    pages in the netfs pagecache until at such time one of those covering pages
    is released.
    
    So if we've written data to the cache (HAVE_DATA) and there wasn't any data
    in the cache when we started (NO_DATA_TO_READ), it may no longer be true
    that we can skip reading from the cache.
    
    Read skipping is done by cachefiles_prepare_read().
    
    Note that tracking is not done on a per-page basis, but only on a per-file
    basis.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/043a206f03929c2667a465314144e518070a9b2d.camel@kernel.org/ [1]
    Link: https://lore.kernel.org/r/164251408479.3435901.9540165422908194636.stgit@warthog.procyon.org.uk/ # v1

commit 6633213139d827fb9abf9a9a280f3d9e89fc7091
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 7 10:57:45 2022 +0000

    cachefiles: Check that the backing filesystem supports tmpfiles
    
    Add a check that the backing filesystem supports the creation of
    tmpfiles[1].
    
    Suggested-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/568749bd7cc02908ecf6f3d6a611b6f9cf5c4afd.camel@kernel.org/ [1]
    Link: https://lore.kernel.org/r/164251406558.3435901.1249023136670058162.stgit@warthog.procyon.org.uk/ # v1

commit 14b9d0902dfa25dac9c41bf346aa655fdeafe5b2
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 7 10:51:13 2022 +0000

    cachefiles: Explain checks in a comment
    
    Add a comment to explain the checks that cachefiles is making of the
    backing filesystem[1].
    
    Suggested-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/568749bd7cc02908ecf6f3d6a611b6f9cf5c4afd.camel@kernel.org/ [1]
    Link: https://lore.kernel.org/r/164251405621.3435901.771439791811515914.stgit@warthog.procyon.org.uk/ # v1

commit b64a3314989df8e44c114f377808407f36dbf4f4
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 14 11:05:13 2022 +0000

    cachefiles: Trace active-mark failure
    
    Add a tracepoint to log failure to apply an active mark to a file in
    addition to tracing successfully setting and unsetting the mark.
    
    Also include the backing file inode number in the message logged to dmesg.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164251404666.3435901.17331742792401482190.stgit@warthog.procyon.org.uk/ # v1

commit 8c39b8bc82aafcc8dd378bd79c76fac8e8a89c8d
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 14 11:44:54 2022 +0000

    cachefiles: Make some tracepoint adjustments
    
    Make some adjustments to tracepoints to make the tracing a bit more
    followable:
    
     (1) Standardise on displaying the backing inode number as "B=<hex>" with
         no leading zeros.
    
     (2) Make the cachefiles_lookup tracepoint log the directory inode number
         as well as the looked-up inode number.
    
     (3) Add a cachefiles_lookup tracepoint into cachefiles_get_directory() to
         log directory lookup.
    
     (4) Add a new cachefiles_mkdir tracepoint and use that to log a successful
         mkdir from cachefiles_get_directory().
    
     (5) Make the cachefiles_unlink and cachefiles_rename tracepoints log the
         inode number of the affected file/dir rather than dentry struct
         pointers.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164251403694.3435901.9797725381831316715.stgit@warthog.procyon.org.uk/ # v1

commit c7ca73155762684a896ba57edf48519b645ea528
Author: Jeffle Xu <jefflexu@linux.alibaba.com>
Date:   Fri Jan 14 15:30:29 2022 +0800

    cachefiles: set default tag name if it's unspecified
    
    fscache_acquire_cache() requires a non-empty name, while 'tag <name>'
    command is optional for cachefilesd.
    
    Thus set default tag name if it's unspecified to avoid the regression of
    cachefilesd. The logic is the same with that before rewritten.
    
    Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164251399914.3435901.4761991152407411408.stgit@warthog.procyon.org.uk/ # v1

commit 5638b067d370583c6c455f019129ce33340b4142
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 14 14:13:59 2022 +0000

    cachefiles: Calculate the blockshift in terms of bytes, not pages
    
    Cachefiles keeps track of how much space is available on the backing
    filesystem and refuses new writes permission to start if there isn't enough
    (we especially don't want ENOSPC happening).  It also tracks the amount of
    data pending in DIO writes (cache->b_writing) and reduces the amount of
    free space available by this amount before deciding if it can set up a new
    write.
    
    However, the old fscache I/O API was very much page-granularity dependent
    and, as such, cachefiles's cache->bshift was meant to be a multiplier to
    get from PAGE_SIZE to block size (ie. a blocksize of 512 would give a shift
    of 3 for a 4KiB page) - and this was incorrectly being used to turn the
    number of bytes in a DIO write into a number of blocks, leading to a
    massive over estimation of the amount of data in flight.
    
    Fix this by changing cache->bshift to be a multiplier from bytes to
    blocksize and deal with quantities of blocks, not quantities of pages.
    
    Fix also the rounding in the calculation in cachefiles_write() which needs
    a "- 1" inserting.
    
    Fixes: 047487c947e8 ("cachefiles: Implement the I/O routines")
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164251398954.3435901.7138806620218474123.stgit@warthog.procyon.org.uk/ # v1

commit 80a00ab8344f0fe4d555a1f97960215b659436e9
Author: David Howells <dhowells@redhat.com>
Date:   Fri Jan 14 13:30:17 2022 +0000

    fscache: Fix the volume collision wait condition
    
    The condition that the waits in fscache_wait_on_volume_collision() are
    waiting until are inverted.  This suddenly started happening on the
    upstream kernel with something like the following appearing in dmesg when
    running xfstests:
    
            CacheFiles: cachefiles: Inode already in use: Iafs,example.com,100055
    
    Fix them by inverting the conditions.
    
    Fixes: 62ab63352350 ("fscache: Implement volume registration")
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164251398010.3435901.943876048104930939.stgit@warthog.procyon.org.uk/ # v1

commit f6f02040e0ca7cb2e82d8aeb8f7daf5d89acc04c
Merge: 6a8d7fbf1c650 f684b10751287 a510c78e5b6f2
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Fri Jan 21 20:05:34 2022 +0100

    Merge branches 'acpi-cppc' and 'acpi-dptf'
    
    Merge new ACPI CPPC driver updates and new Raptor Lake DPTF device
    IDs for 5.17-rc1.
    
    * acpi-cppc:
      ACPI: CPPC: Drop redundant local variable from cpc_read()
      ACPI: CPPC: Fix up I/O port access in cpc_read()
    
    * acpi-dptf:
      ACPI: DPTF: Support Raptor Lake

commit 248be352bbae1a0f14d0d3511a5b0bb9665097f5
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Thu Jan 20 19:06:01 2022 +0530

    ASoC: amd: acp-mach: Fix Left and Right rt1019 amp devices
    
    We're setting wrong card codec conf for rt1019 amp devices in our
    machine driver. Due to this left and right amp channels data are
    reversed in our machines as wrong device prefix results in wrong
    value for "Mono LR Select" rt1019 mixer control. Reverse dev ids
    in codec conf with Left and Right name_prefix to fix such issue.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Link: https://lore.kernel.org/r/20220120133605.476138-1-AjitKumar.Pandey@amd.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit e26a78057c25dd56f112d536319c38735ed92ba4
Author: Alex Henrie <alexhenrie24@gmail.com>
Date:   Sun Jan 16 16:01:58 2022 -0700

    HID: apple: Set the tilde quirk flag on the Wellspring 5 and later
    
    Markus reports that his 2011 MacBook with a German ISO keyboard (USB
    product code 05ac:0246, HID country code 13) has the tilde key quirk.
    Seeing as all of the standalone Apple ISO keyboards since about 2008
    have the quirk, it seems reasonable to assume that once the integrated
    laptop keyboards started having the quirk, they likewise never stopped
    having it.
    
    Reported-by: Markus Wageringel <markus.wageringel@gmail.com>
    Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 03c82e80ec283b115c56026ecdb95c901a57c51e
Merge: 67ab55956e649 745166fcf01ce
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 21 14:32:21 2022 +0000

    Merge branch 'octeontx2-af-fixes'
    
    Subbaraya Sundeep says:
    
    ====================
    octeontx-af2: Fixes for CN10K and CN9xxx platforms
    
    This patchset has consolidated fixes in Octeontx2 driver
    handling CN10K and CN9xxx platforms. When testing the
    new CN10K hardware some issues resurfaced like accessing
    wrong register for CN10K and enabling loopback on not supported
    interfaces. Some fixes are needed for CN9xxx platforms as well.
    
    Below is the description of patches
    
    Patch 1: AF sets RX RSS action for all the VFs when a VF is
    brought up. But when a PF sets RX action for its VF like Drop/Direct
    to a queue in ntuple filter it is not retained because of AF fixup.
    This patch skips modifying VF RX RSS action if PF has already
    set its action.
    
    Patch 2: When configuring backpressure wrong register is being read for
    LBKs hence fixed it.
    
    Patch 3: Some RVU blocks may take longer time to reset but are guaranteed
    to complete the reset. Hence wait till reset is complete.
    
    Patch 4: For enabling LMAC CN10K needs another register compared
    to CN9xxx platforms. Hence changed it.
    
    Patch 5: Adds missing barrier before submitting memory pointer
    to the aura hardware.
    
    Patch 6: Increase polling time while link credit restore and also
    return proper error code when timeout occurs.
    
    Patch 7: Internal loopback not supported on LPCS interfaces like
    SGMII/QSGMII so do not enable it.
    
    Patch 8: When there is a error in message processing, AF sets the error
    response and replies back to requestor. PF forwards a invalid message to
    VF back if AF reply has error in it. This way VF lacks the actual error set
    by AF for its message. This is changed such that PF simply forwards the
    actual reply and let VF handle the error.
    
    Patch 9: ntuple filter with "flow-type ether proto 0x8842 vlan 0x92e"
    was not working since ethertype 0x8842 is NGIO protocol. Hardware
    parser explicitly parses such NGIO packets and sets the packet as
    NGIO and do not set it as tagged packet. Fix this by changing parser
    such that it sets the packet as both NGIO and tagged by using
    separate layer types.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 745166fcf01cecc4f5ff3defc6586868349a43f9
Author: Kiran Kumar K <kirankumark@marvell.com>
Date:   Fri Jan 21 12:04:47 2022 +0530

    octeontx2-af: Add KPU changes to parse NGIO as separate layer
    
    With current KPU profile NGIO is being parsed along with CTAG as
    a single layer. Because of this MCAM/ntuple rules installed with
    ethertype as 0x8842 are not being hit. Adding KPU profile changes
    to parse NGIO in separate ltype and CTAG in separate ltype.
    
    Fixes: f9c49be90c05 ("octeontx2-af: Update the default KPU profile and fixes")
    Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a8db854be28622a2477cb21cdf7f829adbb2c42d
Author: Subbaraya Sundeep <sbhatta@marvell.com>
Date:   Fri Jan 21 12:04:46 2022 +0530

    octeontx2-pf: Forward error codes to VF
    
    PF forwards its VF messages to AF and corresponding
    replies from AF to VF. AF sets proper error code in the
    replies after processing message requests. Currently PF
    checks the error codes in replies and sends invalid
    message to VF. This way VF lacks the information of
    error code set by AF for its messages. This patch
    changes that such that PF simply forwards AF replies
    so that VF can handle error codes.
    
    Fixes: d424b6c02415 ("octeontx2-pf: Enable SRIOV and added VF mbox handling")
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit df66b6ebc5dcf7253e35a640b9ec4add54195c25
Author: Geetha sowjanya <gakula@marvell.com>
Date:   Fri Jan 21 12:04:45 2022 +0530

    octeontx2-af: cn10k: Do not enable RPM loopback for LPC interfaces
    
    Internal looback is not supported to low rate LPCS interface like
    SGMII/QSGMII. Hence don't allow to enable for such interfaces.
    
    Fixes: 3ad3f8f93c81 ("octeontx2-af: cn10k: MAC internal loopback support")
    Signed-off-by: Geetha sowjanya <gakula@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1581d61b42d985cefe7b71eea67ab3bfcbf34d0f
Author: Geetha sowjanya <gakula@marvell.com>
Date:   Fri Jan 21 12:04:44 2022 +0530

    octeontx2-af: Increase link credit restore polling timeout
    
    It's been observed that sometimes link credit restore takes
    a lot of time than the current timeout. This patch increases
    the default timeout value and return the proper error value
    on failure.
    
    Fixes: 1c74b89171c3 ("octeontx2-af: Wait for TX link idle for credits change")
    Signed-off-by: Geetha sowjanya <gakula@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c5d731c54a17677939bd59ee8be4ed74d7485ba4
Author: Geetha sowjanya <gakula@marvell.com>
Date:   Fri Jan 21 12:04:43 2022 +0530

    octeontx2-pf: cn10k: Ensure valid pointers are freed to aura
    
    While freeing SQB pointers to aura, driver first memcpy to
    target address and then triggers lmtst operation to free pointer
    to the aura. We need to ensure(by adding dmb barrier)that memcpy
    is finished before pointers are freed to the aura. This patch also
    adds the missing sq context structure entry in debugfs.
    
    Fixes: ef6c8da71eaf ("octeontx2-pf: cn10K: Reserve LMTST lines per core")
    Signed-off-by: Geetha sowjanya <gakula@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit fae80edeafbbba5ef9a0423aa5e5515518626433
Author: Geetha sowjanya <gakula@marvell.com>
Date:   Fri Jan 21 12:04:42 2022 +0530

    octeontx2-af: cn10k: Use appropriate register for LMAC enable
    
    CN10K platforms uses RPM(0..2)_MTI_MAC100(0..3)_COMMAND_CONFIG
    register for lmac TX/RX enable whereas CN9xxx platforms use
    CGX_CMRX_CONFIG register. This config change was missed when
    adding support for CN10K RPM.
    
    Fixes: 91c6945ea1f9 ("octeontx2-af: cn10k: Add RPM MAC support")
    Signed-off-by: Geetha sowjanya <gakula@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 03ffbc9914bd1130fba464f0a41c01372e5fc359
Author: Geetha sowjanya <gakula@marvell.com>
Date:   Fri Jan 21 12:04:41 2022 +0530

    octeontx2-af: Retry until RVU block reset complete
    
    Few RVU blocks like SSO require more time for reset on some
    silicons. Hence retrying the block reset until success.
    
    Fixes: c0fa2cff8822c ("octeontx2-af: Handle return value in block reset")
    Signed-off-by: Geetha sowjanya <gakula@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 00bfe94e388fe12bfd0d4f6361b1b1343374ff5b
Author: Sunil Goutham <sgoutham@marvell.com>
Date:   Fri Jan 21 12:04:40 2022 +0530

    octeontx2-af: Fix LBK backpressure id count
    
    In rvu_nix_get_bpid() lbk_bpid_cnt is being read from
    wrong register. Due to this backpressure enable is failing
    for LBK VF32 onwards. This patch fixes that.
    
    Fixes: fe1939bb2340 ("octeontx2-af: Add SDP interface support")
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d225c449ab2be25273a3674f476c6c0b57c50254
Author: Subbaraya Sundeep <sbhatta@marvell.com>
Date:   Fri Jan 21 12:04:39 2022 +0530

    octeontx2-af: Do not fixup all VF action entries
    
    AF modifies all the rules destined for VF to use
    the action same as default RSS action. This fixup
    was needed because AF only installs default rules with
    RSS action. But the action in rules installed by a PF
    for its VFs should not be changed by this fixup.
    This is because action can be drop or direct to
    queue as specified by user(ntuple filters).
    This patch fixes that problem.
    
    Fixes: 967db3529eca ("octeontx2-af: add support for multicast/promisc packet")
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Naveen Mamindlapalli <naveenm@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9b57f458985742bd1c585f4c7f36d04634ce1143
Merge: 3c7c25038b6c7 20f3cf5f860f9
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 16:25:38 2022 +0200

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid
    
    Pull HID fixes from Jiri Kosina:
    
     - fix for race condition that could lead to NULL pointer dereferences
       or UAF during uhid device destruction (Jann Horn)
    
     - contact count handling regression fixes for Wacom devices (Jason
       Gerecke)
    
     - fix for handling unnumbered HID reports handling in Google Vivaldi
       driver (Dmitry Torokhov)
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid:
      HID: wacom: Avoid using stale array indicies to read contact count
      HID: wacom: Ignore the confidence flag when a touch is removed
      HID: wacom: Reset expected and received contact counts at the same time
      HID: uhid: Use READ_ONCE()/WRITE_ONCE() for ->running
      HID: uhid: Fix worker destroying device without any protection
      HID: vivaldi: Minor cleanups
      HID: vivaldi: fix handling devices not using numbered reports
      HID: Ignore battery for Elan touchscreen on HP Envy X360 15t-dr100

commit 3c7c25038b6c7d66a6816028219914379be6a5cc
Merge: f3a78227eef20 46cdc45acb089
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 16:17:03 2022 +0200

    Merge tag 'block-5.17-2022-01-21' of git://git.kernel.dk/linux-block
    
    Pull block fixes from Jens Axboe:
     "Various little minor fixes that should go into this release:
    
       - Fix issue with cloned bios and IO accounting (Christoph)
    
       - Remove redundant assignments (Colin, GuoYong)
    
       - Fix an issue with the mq-deadline async_depth sysfs interface (me)
    
       - Fix brd module loading race (Tetsuo)
    
       - Shared tag map wakeup fix (Laibin)
    
       - End of bdev read fix (OGAWA)
    
       - srcu leak fix (Ming)"
    
    * tag 'block-5.17-2022-01-21' of git://git.kernel.dk/linux-block:
      block: fix async_depth sysfs interface for mq-deadline
      block: Fix wrong offset in bio_truncate()
      block: assign bi_bdev for cloned bios in blk_rq_prep_clone
      block: cleanup q->srcu
      block: Remove unnecessary variable assignment
      brd: remove brd_devices_mutex mutex
      aoe: remove redundant assignment on variable n
      loop: remove redundant initialization of pointer node
      blk-mq: fix tag_get wait task can't be awakened

commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814
Author: Jason Gerecke <killertofu@gmail.com>
Date:   Tue Jan 18 14:38:41 2022 -0800

    HID: wacom: Avoid using stale array indicies to read contact count
    
    If we ever see a touch report with contact count data we initialize
    several variables used to read the contact count in the pre-report
    phase. These variables are never reset if we process a report which
    doesn't contain a contact count, however. This can cause the pre-
    report function to trigger a read of arbitrary memory (e.g. NULL
    if we're lucky) and potentially crash the driver.
    
    This commit restores resetting of the variables back to default
    "none" values that were used prior to the commit mentioned
    below.
    
    Link: https://github.com/linuxwacom/input-wacom/issues/276
    Fixes: 003f50ab673c (HID: wacom: Update last_slot_field during pre_report phase)
    CC: stable@vger.kernel.org
    Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
    Reviewed-by: Ping Cheng <ping.cheng@wacom.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit df03e9bd6d4806619b4cdc91a3d7695818a8e2b7
Author: Jason Gerecke <killertofu@gmail.com>
Date:   Tue Jan 18 14:37:56 2022 -0800

    HID: wacom: Ignore the confidence flag when a touch is removed
    
    AES hardware may internally re-classify a contact that it thought was
    intentional as a palm. Intentional contacts are reported as "down" with
    the confidence bit set. When this re-classification occurs, however, the
    state transitions to "up" with the confidence bit cleared. This kind of
    transition appears to be legal according to Microsoft docs, but we do
    not handle it correctly. Because the confidence bit is clear, we don't
    call `wacom_wac_finger_slot` and update userspace. This causes hung
    touches that confuse userspace and interfere with pen arbitration.
    
    This commit adds a special case to ignore the confidence flag if a contact
    is reported as removed. This ensures we do not leave a hung touch if one
    of these re-classification events occured. Ideally we'd have some way to
    also let userspace know that the touch has been re-classified as a palm
    and needs to be canceled, but that's not possible right now :)
    
    Link: https://github.com/linuxwacom/input-wacom/issues/288
    Fixes: 7fb0413baa7f (HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts)
    CC: stable@vger.kernel.org
    Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
    Reviewed-by: Ping Cheng <ping.cheng@wacom.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 546e41ac994cc185ef3de610ca849a294b5df3ba
Author: Jason Gerecke <killertofu@gmail.com>
Date:   Tue Jan 18 14:37:55 2022 -0800

    HID: wacom: Reset expected and received contact counts at the same time
    
    These two values go hand-in-hand and must be valid for the driver to
    behave correctly. We are currently lazy about updating the values and
    rely on the "expected" code flow to take care of making sure they're
    valid at the point they're needed. The "expected" flow changed somewhat
    with commit f8b6a74719b5 ("HID: wacom: generic: Support multiple tools
    per report"), however. This led to problems with the DTH-2452 due (in
    part) to *all* contacts being fully processed -- even those past the
    expected contact count. Specifically, the received count gets reset to
    0 once all expected fingers are processed, but not the expected count.
    The rest of the contacts in the report are then *also* processed since
    now the driver thinks we've only processed 0 of N expected contacts.
    
    Later commits such as 7fb0413baa7f (HID: wacom: Use "Confidence" flag to
    prevent reporting invalid contacts) worked around the DTH-2452 issue by
    skipping the invalid contacts at the end of the report, but this is not
    a complete fix. The confidence flag cannot be relied on when a contact
    is removed (see the following patch), and dealing with that condition
    re-introduces the DTH-2452 issue unless we also address this contact
    count laziness. By resetting expected and received counts at the same
    time we ensure the driver understands that there are 0 more contacts
    expected in the report. Similarly, we also make sure to reset the
    received count if for some reason we're out of sync in the pre-report
    phase.
    
    Link: https://github.com/linuxwacom/input-wacom/issues/288
    Fixes: f8b6a74719b5 ("HID: wacom: generic: Support multiple tools per report")
    CC: stable@vger.kernel.org
    Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
    Reviewed-by: Ping Cheng <ping.cheng@wacom.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit f3a78227eef20c0ba13bbf9401f0a340bca3ad16
Merge: 1f40caa080474 73031f761cb7c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 16:07:21 2022 +0200

    Merge tag 'io_uring-5.17-2022-01-21' of git://git.kernel.dk/linux-block
    
    Pull io_uring fixes from Jens Axboe:
    
     - Fix the io_uring POLLFREE handling, similarly to how it was done for
       aio (Pavel)
    
     - Remove (now) unused function (Jiapeng)
    
     - Small series fixing an issue with work cancelations. A window exists
       where work isn't locatable in the pending list, and isn't active in a
       worker yet either. (me)
    
    * tag 'io_uring-5.17-2022-01-21' of git://git.kernel.dk/linux-block:
      io-wq: delete dead lock shuffling code
      io_uring: perform poll removal even if async work removal is successful
      io-wq: add intermediate work step between pending list and active work
      io-wq: perform both unstarted and started work cancelations in one go
      io-wq: invoke work cancelation with wqe->lock held
      io-wq: make io_worker lock a raw spinlock
      io-wq: remove useless 'work' argument to __io_worker_busy()
      io_uring: fix UAF due to missing POLLFREE handling
      io_uring: Remove unused function req_ref_put

commit 1f40caa080474d0420e0b0e6c896e455acb6e236
Merge: 75242f31db6ca 2a1355f0bf41a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 13:49:22 2022 +0200

    Merge tag 'sound-fix-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
    
    Pull sound fixes from Takashi Iwai:
     "A small set of HD-audio and USB-audio fixes as well as a couple of
      ALSA core fixes. Most of them are fix-ups for the newly added CS35L41
      codec"
    
    * tag 'sound-fix-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound:
      ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409
      ALSA: core: Simplify snd_power_ref_and_wait() with the standard macro
      ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void
      ALSA: hda: cs35l41: Tidyup code
      ALSA: hda: cs35l41: Make use of the helper function dev_err_probe()
      ALSA: hda: cs35l41: Add missing default cases
      ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace
      ALSA: hda: cs35l41: Add calls to newly added test key function
      ALSA: hda: cs35l41: Avoid overwriting register patch
      ALSA: core: Fix SSID quirk lookup for subvendor=0
      ALSA: usb-audio: add mapping for MSI MPG X570S Carbon Max Wifi.
      ALSA: hda/realtek: fix speakers and micmute on HP 855 G8

commit 67ab55956e64906c9e0f049c5fc41fc28e5e48bc
Merge: 0b6d8cf2ecb98 a1222ca0681f1
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 21 11:23:33 2022 +0000

    Merge tag 'wireless-2022-01-21' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless
    
    Kalle Valo says:
    
    ====================
    wireless fixes for v5.17
    
    First set of fixes for v5.17. This is the first pull request from the
    new wireless tree and only changes to MAINTAINERS file.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 75242f31db6cabf602a5eb84c13b579099d72a65
Merge: c2c94b3b187dc 5ceee540fdc7f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 13:13:35 2022 +0200

    Merge tag 'rtc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux
    
    Pull RTC updates from Alexandre Belloni:
     "Two new drivers this cycle and a significant rework of the CMOS driver
      make the bulk of the changes.
    
      I also carry powerpc changes with the agreement of Michael.
    
      New drivers:
       - Sunplus SP7021 RTC
       - Nintendo GameCube, Wii and Wii U RTC
    
      Driver updates:
       - cmos: refactor UIP handling and presence check, fix century
       - rs5c372: offset correction support, report low voltage
       - rv8803: Epson RX8804 support"
    
    * tag 'rtc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux: (33 commits)
      rtc: sunplus: fix return value in sp_rtc_probe()
      rtc: cmos: Evaluate century appropriate
      rtc: gamecube: Fix an IS_ERR() vs NULL check
      rtc: mc146818-lib: fix signedness bug in mc146818_get_time()
      dt-bindings: rtc: qcom-pm8xxx-rtc: update register numbers
      rtc: pxa: fix null pointer dereference
      rtc: ftrtc010: Use platform_get_irq() to get the interrupt
      rtc: Move variable into switch case statement
      rtc: pcf2127: Fix typo in comment
      dt-bindings: rtc: Add Sunplus RTC json-schema
      rtc: Add driver for RTC in Sunplus SP7021
      rtc: rs5c372: fix incorrect oscillation value on r2221tl
      rtc: rs5c372: add offset correction support
      rtc: cmos: avoid UIP when writing alarm time
      rtc: cmos: avoid UIP when reading alarm time
      rtc: mc146818-lib: refactor mc146818_does_rtc_work
      rtc: mc146818-lib: refactor mc146818_get_time
      rtc: mc146818-lib: extract mc146818_avoid_UIP
      rtc: mc146818-lib: fix RTC presence check
      rtc: Check return value from mc146818_get_time()
      ...

commit 0b6d8cf2ecb98a842eaf523f31939ba362eb2235
Merge: 276c7635d7be3 3b8428b84539c
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 21 10:30:30 2022 +0000

    Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue
    
    Tony Nguyen says:
    
    ====================
    Intel Wired LAN Driver Updates 2022-01-20
    
    This series contains updates to i40e driver only.
    
    Jedrzej increases delay for EMP reset and adds checks to ensure a VF
    request to change queues can be met.
    
    Sylwester moves the placement of the Flow Director queue as to not
    fragment the queue pile which would cause later re-allocation issues.
    
    Karen prevents VF reset being invoked while another is still occurring
    to avoid reading invalid data.
    
    Joe Damato fixes some statistics fields to match the values of the
    fields they are based on.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b875b39e7373dcaccb19a600a52a956061c2c833
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Fri Jan 21 17:19:33 2022 +0900

    ata: pata_octeon_cf: fix call to trace_ata_bmdma_stop()
    
    The first argument of trace_ata_bmdma_stop() must be a pointer to a
    struct ata_port, not to a struct ata_queued_cmd.
    
    Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
    Fixes: d3e140f2b008 ("ata: pata_octeon_cf: Drop pointless VPRINTK() calls and convert the remaining one")
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>

commit c2c94b3b187dc92b2002809f489e0f24a41e91bc
Merge: 39e77c484bcd1 ccf34586758cf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 09:25:38 2022 +0200

    Merge tag 'drm-next-2022-01-21' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Dave Airlie:
     "Thanks to Daniel for taking care of things while I was out, just a set
      of merge window fixes that came in this week, two i915 display fixes
      and a bunch of misc amdgpu, along with a radeon regression fix.
    
      amdgpu:
       - SR-IOV fix
       - VCN harvest fix
       - Suspend/resume fixes
       - Tahiti fix
       - Enable GPU recovery on yellow carp
    
      radeon:
       - Fix error handling regression in radeon_driver_open_kms
    
      i915:
       - Update EHL display voltage swing table
       - Fix programming the ADL-P display TC voltage swing"
    
    * tag 'drm-next-2022-01-21' of git://anongit.freedesktop.org/drm/drm:
      drm/radeon: fix error handling in radeon_driver_open_kms
      drm/amd/amdgpu: fixing read wrong pf2vf data in SRIOV
      drm/amdgpu: apply vcn harvest quirk
      drm/i915/display/adlp: Implement new step in the TC voltage swing prog sequence
      drm/i915/display/ehl: Update voltage swing table
      drm/amd/display: Revert W/A for hard hangs on DCN20/DCN21
      drm/amdgpu: drop flags check for CHIP_IP_DISCOVERY
      drm/amdgpu: Fix rejecting Tahiti GPUs
      drm/amdgpu: don't do resets on APUs which don't support it
      drm/amdgpu: invert the logic in amdgpu_device_should_recover_gpu()
      drm/amdgpu: Enable recovery on yellow carp

commit 39e77c484bcd1865ff6abdbde6b36eb91ee1ff33
Merge: 4141a5e694588 b4966a7dc0725
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 09:16:11 2022 +0200

    Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
    
    Pull clk fixes from Stephen Boyd:
     "Some hot fixes for clk driver patches merged last week and one oops
      fix:
    
       - Fix license on recent MediaTek drivers
    
       - Initialize a variable before use in the new Visconti driver
    
       - Avoid an oops by unregistering the clk provider in si5341"
    
    * tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux:
      clk: mediatek: relicense mt7986 clock driver to GPL-2.0
      clk: visconti: Fix uninitialized variable in printk
      clk: si5341: Fix clock HW provider cleanup

commit 4141a5e694588897cbec955bc4a646075dc0afd7
Merge: 85e67d56ebdec 9c494ca4d3a53
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 09:10:46 2022 +0200

    Merge tag 'pci-v5.17-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci fix from Bjorn Helgaas:
    
     - Reserve "stolen memory" for integrated Intel GPU, even if it's not
       the first GPU to be enumerated (Lucas De Marchi)
    
    * tag 'pci-v5.17-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
      x86/gpu: Reserve stolen memory for first integrated Intel GPU

commit 85e67d56ebdecd8601d62e3aadcd2927845c97b9
Merge: 31d949782e1da 5754f9084f261
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 08:57:15 2022 +0200

    Merge tag 's390-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
    
    Pull more s390 updates from Heiko Carstens:
    
     - add Sven Schnelle as reviewer for s390 code
    
     - make uaccess code more readable
    
     - change cpu measurement facility code to also support counter second
       version number 7, and add discard support for limited samples
    
    * tag 's390-5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
      s390: add Sven Schnelle as reviewer
      s390/uaccess: introduce bit field for OAC specifier
      s390/cpumf: Support for CPU Measurement Sampling Facility LS bit
      s390/cpumf: Support for CPU Measurement Facility CSVN 7

commit 31d949782e1daf4b329337dd36b2d6d60764fe29
Merge: d701a8ccac7a1 b3bb9413e717b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 08:51:48 2022 +0200

    Merge tag 'xfs-5.17-merge-6' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull more xfs irix ioctl housecleaning from Darrick Wong:
     "Withdraw the XFS_IOC_ALLOCSP* and XFS_IOC_FREESP* ioctl definitions.
    
      This is the third and final of a series of small pull requests that
      perform some long overdue housecleaning of XFS ioctls. This time,
      we're withdrawing all variants of the ALLOCSP and FREESP ioctls from
      XFS' userspace API. This might be a little premature since we've only
      just removed the functionality, but as I pointed out in the last pull
      request, nobody (including fstests) noticed that it was broken for 20
      years.
    
      In response to the patch, we received a single comment from someone
      who stated that they 'augment' the ioctl for their own purposes, but
      otherwise acquiesced to the withdrawal. I still want to try to clobber
      these old ioctl definitions in 5.17.
    
      So remove the header definitions for these ioctls. The just-removed
      implementation has allowed callers to read stale disk contents for
      more than **21 years** and nobody noticed or complained, which implies
      a lack of users aside from exploit programs"
    
    * tag 'xfs-5.17-merge-6' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: remove the XFS_IOC_{ALLOC,FREE}SP* definitions

commit d701a8ccac7a1c0912425a01919a3cbe05f22914
Merge: 12a8fb20f1c23 4d1b97f9ce7c0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 08:47:25 2022 +0200

    Merge tag 'xfs-5.17-merge-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs irix ioctl housecleaning from Darrick Wong:
     "Remove the XFS_IOC_ALLOCSP* and XFS_IOC_FREESP* ioctl families.
    
      This is the second of a series of small pull requests that perform
      some long overdue housecleaning of XFS ioctls. This time, we're
      vacating the implementation of all variants of the ALLOCSP and FREESP
      ioctls, which are holdovers from EFS in Irix, circa 1993. Roughly
      equivalent functionality have been available for both ioctls since
      2.6.25 (April 2008):
    
       - XFS_IOC_FREESP ftruncates a file.
    
       - XFS_IOC_ALLOCSP is the equivalent of fallocate.
    
      As noted in the fix patch for CVE 2021-4155, the ALLOCSP ioctl has
      been serving up stale disk blocks since 2000, and in 21 years
      **nobody** noticed. On those grounds I think it's safe to vacate the
      implementation.
    
      Note that we lose the ability to preallocate and truncate relative to
      the current file position, but as nobody's ever implemented that for
      the VFS, I conclude that it's not in high demand.
    
      Linux has always used fallocate as the space management system call,
      whereas these Irix legacy ioctls only ever worked on XFS, and have
      been the cause of recent stale data disclosure vulnerabilities. As
      equivalent functionality is available elsewhere, remove the code"
    
    * tag 'xfs-5.17-merge-5' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls

commit 12a8fb20f1c2387eaad417587c14cb684f380735
Merge: 2c271fe77d52a 9dec0368b9640
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 21 08:44:07 2022 +0200

    Merge tag 'xfs-5.17-merge-4' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs ioctl housecleaning from Darrick Wong:
     "This is the first of a series of small pull requests that perform some
      long overdue housecleaning of XFS ioctls. This first pull request
      removes the FSSETDM ioctl, which was used to set DMAPI event
      attributes on XFS files. The DMAPI support has never been merged
      upstream and the implementation of FSSETDM itself was removed two
      years ago, so let's withdraw it completely.
    
       - Withdraw the ioctl definition for the FSSETDM ioctl"
    
    * tag 'xfs-5.17-merge-4' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: remove the XFS_IOC_FSSETDM definitions

commit 276c7635d7be3aa233251354bd7e8b77ab5dcf9c
Merge: 6f97fde8694d5 9846921dba493
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 20 20:24:03 2022 -0800

    Merge branch 'mptcp-a-few-fixes'
    
    Mat Martineau says:
    
    ====================
    mptcp: A few fixes
    
    Patch 1 fixes a RCU locking issue when processing a netlink command that
    updates endpoint flags in the in-kernel MPTCP path manager.
    
    Patch 2 fixes a typo affecting available endpoint id tracking.
    
    Patch 3 fixes IPv6 routing in the MPTCP self tests.
    ====================
    
    Link: https://lore.kernel.org/r/20220121003529.54930-1-mathew.j.martineau@linux.intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9846921dba4936d92f7608315b5d1e0a8ec3a538
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 20 16:35:29 2022 -0800

    selftests: mptcp: fix ipv6 routing setup
    
    MPJ ipv6 selftests currently lack per link route to the server
    net. Additionally, ipv6 subflows endpoints are created without any
    interface specified. The end-result is that in ipv6 self-tests
    subflows are created all on the same link, leading to expected delays
    and sporadic self-tests failures.
    
    Fix the issue by adding the missing setup bits.
    
    Fixes: 523514ed0a99 ("selftests: mptcp: add ADD_ADDR IPv6 test cases")
    Reported-and-tested-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a4c0214fbee97c46e3f41fee37931d66c0fc3cb1
Author: Geliang Tang <geliang.tang@suse.com>
Date:   Thu Jan 20 16:35:28 2022 -0800

    mptcp: fix removing ids bitmap setting
    
    In mptcp_pm_nl_rm_addr_or_subflow(), the bit of rm_list->ids[i] in the
    id_avail_bitmap should be set, not rm_list->ids[1]. This patch fixed it.
    
    Fixes: 86e39e04482b ("mptcp: keep track of local endpoint still available for each msk")
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8e9eacad7ec7a9cbf262649ebf1fa6e6f6cc7d82
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 20 16:35:27 2022 -0800

    mptcp: fix msk traversal in mptcp_nl_cmd_set_flags()
    
    The MPTCP endpoint list is under RCU protection, guarded by the
    pernet spinlock. mptcp_nl_cmd_set_flags() traverses the list
    without acquiring the spin-lock nor under the RCU critical section.
    
    This change addresses the issue performing the lookup and the endpoint
    update under the pernet spinlock.
    
    Fixes: 0f9f696a502e ("mptcp: add set_flags command in PM netlink")
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6f97fde8694d5242ace94a58bc8522a70b5f77cc
Merge: aafc2e3285c2d 830af2eba4032
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 20 20:22:30 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    1) Incorrect helper module alias in netbios_ns, from Florian Westphal.
    
    2) Remove unused variable in nf_tables.
    
    3) Uninitialized last expression in nf_tables register tracking.
    
    4) Memleak in nft_connlimit after moving stateful data out of the
       expression data area.
    
    5) Bogus invalid stats update when NF_REPEAT is returned, from Florian.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf:
      netfilter: conntrack: don't increment invalid counter on NF_REPEAT
      netfilter: nft_connlimit: memleak if nf_ct_netns_get() fails
      netfilter: nf_tables: set last expression in register tracking area
      netfilter: nf_tables: remove unused variable
      netfilter: nf_conntrack_netbios_ns: fix helper module alias
    ====================
    
    Link: https://lore.kernel.org/r/20220120125212.991271-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit aafc2e3285c2d7a79b7ee15221c19fbeca7b1509
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Jan 20 09:41:12 2022 -0800

    ipv6: annotate accesses to fn->fn_sernum
    
    struct fib6_node's fn_sernum field can be
    read while other threads change it.
    
    Add READ_ONCE()/WRITE_ONCE() annotations.
    
    Do not change existing smp barriers in fib6_get_cookie_safe()
    and __fib6_update_sernum_upto_root()
    
    syzbot reported:
    
    BUG: KCSAN: data-race in fib6_clean_node / inet6_csk_route_socket
    
    write to 0xffff88813df62e2c of 4 bytes by task 1920 on cpu 1:
     fib6_clean_node+0xc2/0x260 net/ipv6/ip6_fib.c:2178
     fib6_walk_continue+0x38e/0x430 net/ipv6/ip6_fib.c:2112
     fib6_walk net/ipv6/ip6_fib.c:2160 [inline]
     fib6_clean_tree net/ipv6/ip6_fib.c:2240 [inline]
     __fib6_clean_all+0x1a9/0x2e0 net/ipv6/ip6_fib.c:2256
     fib6_flush_trees+0x6c/0x80 net/ipv6/ip6_fib.c:2281
     rt_genid_bump_ipv6 include/net/net_namespace.h:488 [inline]
     addrconf_dad_completed+0x57f/0x870 net/ipv6/addrconf.c:4230
     addrconf_dad_work+0x908/0x1170
     process_one_work+0x3f6/0x960 kernel/workqueue.c:2307
     worker_thread+0x616/0xa70 kernel/workqueue.c:2454
     kthread+0x1bf/0x1e0 kernel/kthread.c:359
     ret_from_fork+0x1f/0x30
    
    read to 0xffff88813df62e2c of 4 bytes by task 15701 on cpu 0:
     fib6_get_cookie_safe include/net/ip6_fib.h:285 [inline]
     rt6_get_cookie include/net/ip6_fib.h:306 [inline]
     ip6_dst_store include/net/ip6_route.h:234 [inline]
     inet6_csk_route_socket+0x352/0x3c0 net/ipv6/inet6_connection_sock.c:109
     inet6_csk_xmit+0x91/0x1e0 net/ipv6/inet6_connection_sock.c:121
     __tcp_transmit_skb+0x1323/0x1840 net/ipv4/tcp_output.c:1402
     tcp_transmit_skb net/ipv4/tcp_output.c:1420 [inline]
     tcp_write_xmit+0x1450/0x4460 net/ipv4/tcp_output.c:2680
     __tcp_push_pending_frames+0x68/0x1c0 net/ipv4/tcp_output.c:2864
     tcp_push+0x2d9/0x2f0 net/ipv4/tcp.c:725
     mptcp_push_release net/mptcp/protocol.c:1491 [inline]
     __mptcp_push_pending+0x46c/0x490 net/mptcp/protocol.c:1578
     mptcp_sendmsg+0x9ec/0xa50 net/mptcp/protocol.c:1764
     inet6_sendmsg+0x5f/0x80 net/ipv6/af_inet6.c:643
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg net/socket.c:725 [inline]
     kernel_sendmsg+0x97/0xd0 net/socket.c:745
     sock_no_sendpage+0x84/0xb0 net/core/sock.c:3086
     inet_sendpage+0x9d/0xc0 net/ipv4/af_inet.c:834
     kernel_sendpage+0x187/0x200 net/socket.c:3492
     sock_sendpage+0x5a/0x70 net/socket.c:1007
     pipe_to_sendpage+0x128/0x160 fs/splice.c:364
     splice_from_pipe_feed fs/splice.c:418 [inline]
     __splice_from_pipe+0x207/0x500 fs/splice.c:562
     splice_from_pipe fs/splice.c:597 [inline]
     generic_splice_sendpage+0x94/0xd0 fs/splice.c:746
     do_splice_from fs/splice.c:767 [inline]
     direct_splice_actor+0x80/0xa0 fs/splice.c:936
     splice_direct_to_actor+0x345/0x650 fs/splice.c:891
     do_splice_direct+0x106/0x190 fs/splice.c:979
     do_sendfile+0x675/0xc40 fs/read_write.c:1245
     __do_sys_sendfile64 fs/read_write.c:1310 [inline]
     __se_sys_sendfile64 fs/read_write.c:1296 [inline]
     __x64_sys_sendfile64+0x102/0x140 fs/read_write.c:1296
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x0000026f -> 0x00000271
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 0 PID: 15701 Comm: syz-executor.2 Not tainted 5.16.0-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    The Fixes tag I chose is probably arbitrary, I do not think
    we need to backport this patch to older kernels.
    
    Fixes: c5cff8561d2d ("ipv6: add rcu grace period before freeing fib6_node")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220120174112.1126644-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ebdc1a0309629e71e5910b353e6b005f022ce171
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Jan 20 04:45:30 2022 -0800

    tcp: add a missing sk_defer_free_flush() in tcp_splice_read()
    
    Without it, splice users can hit the warning
    added in commit 79074a72d335 ("net: Flush deferred skb free on socket destroy")
    
    Fixes: f35f821935d8 ("tcp: defer skb freeing after socket lock is released")
    Fixes: 79074a72d335 ("net: Flush deferred skb free on socket destroy")
    Suggested-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Gal Pressman <gal@nvidia.com>
    Link: https://lore.kernel.org/r/20220120124530.925607-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 48cec899e357cfb92d022a9c0df6bbe72a7f6951
Author: Gal Pressman <gal@nvidia.com>
Date:   Thu Jan 20 14:34:40 2022 +0200

    tcp: Add a stub for sk_defer_free_flush()
    
    When compiling the kernel with CONFIG_INET disabled, the
    sk_defer_free_flush() should be defined as a nop.
    
    This resolves the following compilation error:
      ld: net/core/sock.o: in function `sk_defer_free_flush':
      ./include/net/tcp.h:1378: undefined reference to `__sk_defer_free_flush'
    
    Fixes: 79074a72d335 ("net: Flush deferred skb free on socket destroy")
    Reported-by: kernel test robot <lkp@intel.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Link: https://lore.kernel.org/r/20220120123440.9088-1-gal@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cbda1b16687580d5beee38273f6241ae3725960c
Author: Marek Behún <kabel@kernel.org>
Date:   Wed Jan 19 17:27:48 2022 +0100

    phylib: fix potential use-after-free
    
    Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call
    to phy_device_reset(phydev) after the put_device() call in phy_detach().
    
    The comment before the put_device() call says that the phydev might go
    away with put_device().
    
    Fix potential use-after-free by calling phy_device_reset() before
    put_device().
    
    Fixes: bafbdd527d56 ("phylib: Add device reset GPIO support")
    Signed-off-by: Marek Behún <kabel@kernel.org>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220119162748.32418-1-kabel@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a0af3d1104f752b6d0dba71788e3fddd67c857a7
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 19 18:54:52 2022 +0100

    PCI/MSI: Prevent UAF in error path
    
    When the core MSI allocation fails, then the PCI/MSI code uses an already
    freed MSI descriptor to unmask the MSI mask register in order to bring it back
    into reset state.
    
    Remove MSI_FLAG_FREE_MSI_DESCS from the PCI/MSI irqdomain flags and let the
    PCI/MSI code free the MSI descriptors after usage.
    
    Fixes: 0f62d941acf9 ("genirq/msi: Provide msi_domain_alloc/free_irqs_descs_locked()")
    Reported-by: Tong Zhang <ztong0001@gmail.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Tested-by: Tong Zhang <ztong0001@gmail.com>
    Acked-by: Bjorn Helgaas <bhelgaas@google.com>
    Link: https://lore.kernel.org/r/87r1938vbn.ffs@tglx

commit 5298d4bfe80f6ae6ae2777bcd1357b0022d98573
Author: Christoph Hellwig <hch@lst.de>
Date:   Tue Jan 18 07:56:14 2022 +0100

    unicode: clean up the Kconfig symbol confusion
    
    Turn the CONFIG_UNICODE symbol into a tristate that generates some always
    built in code and remove the confusing CONFIG_UNICODE_UTF8_DATA symbol.
    
    Note that a lot of the IS_ENABLED() checks could be turned from cpp
    statements into normal ifs, but this change is intended to be fairly
    mechanic, so that should be cleaned up later.
    
    Fixes: 2b3d04787012 ("unicode: Add utf8-data module")
    Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
    Reviewed-by: Eric Biggers <ebiggers@google.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>

commit b0ac702f3329cdc8a06dcaac73183d4b5a2b942d
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Tue Jan 18 19:39:05 2022 -0800

    Documentation: fix firewire.rst ABI file path error
    
    Adjust the path of the ABI files for firewire.rst to prevent a
    documentation build error. Prevents this problem:
    
    Sphinx parallel build error:
    docutils.utils.SystemMessage: Documentation/driver-api/firewire.rst:22: (SEVERE/4) Problems with "include" directive path:
    InputError: [Errno 2] No such file or directory: '../Documentation/driver-api/ABI/stable/firewire-cdev'.
    
    Fixes: 2f4830ef96d2 ("FireWire: add driver-api Introduction section")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Tested-by: Akira Yokosawa <akiyks@gmail.com>
    Link: https://lore.kernel.org/r/20220119033905.4779-1-rdunlap@infradead.org
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit ccf34586758cf00c0934e48f6ef6d688f01d7b19
Merge: 410482b51afec 4722f463896cc
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 21 08:37:56 2022 +1000

    Merge tag 'amd-drm-fixes-5.17-2022-01-19' of https://gitlab.freedesktop.org/agd5f/linux into drm-next
    
    amd-drm-fixes-5.17-2022-01-19:
    
    amdgpu:
    - SR-IOV fix
    - VCN harvest fix
    - Suspend/resume fixes
    - Tahiti fix
    - Enable GPU recovery on yellow carp
    
    radeon:
    - Fix error handling regression in radeon_driver_open_kms
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220120013547.5649-1-alexander.deucher@amd.com

commit 410482b51afecddb8fc29324d1b11945dfa0b682
Merge: 4efdddbce7c13 e26602be4869c
Author: Dave Airlie <airlied@redhat.com>
Date:   Fri Jan 21 08:31:29 2022 +1000

    Merge tag 'drm-intel-next-fixes-2022-01-20' of git://anongit.freedesktop.org/drm/drm-intel into drm-next
    
    - Latest updates for the EHL display voltage swing table (José Roberto de Souza)
    - Additional step is required when programming the ADL-P display TC voltage swing (José Roberto de Souza)
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yek1zdsnRPiBVvFF@tursulin-mobl2

commit c59cd507fb640c2acc6b07cb60d7f765839e18c7
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Wed Jan 19 10:39:37 2022 -0800

    RISC-V: nommu_virt: Drop unused SLAB_MERGE_DEFAULT
    
    Our nommu_virt_defconfig set SLOB=y and SLAB_MERGE_DEFAULT=n.  As of
    eb52c0fc2331 ("mm: Make SLAB_MERGE_DEFAULT depend on SL[AU]B") it's no
    longer necessary to set the second, which appears to never have had any
    effect for SLOB=y anyway.
    
    This was suggested by savedefconfig.
    
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 18a86e5907f7160fb548d0d717e0f842b310708a
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Thu Jan 20 11:40:09 2022 +0100

    dt-bindings: google,cros-ec: drop Enric Balletbo i Serra from maintainers
    
    Enric Balletbo i Serra emails bounce:
    
      <enric.balletbo@collabora.com>: Recipient address rejected: User unknown in  local recipient table
    
    so drop him from the maintainers, similarly to commit 3119c28634dd
    ("MAINTAINERS: Chrome: Drop Enric Balletbo i Serra").
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Lee Jones <lee.jones@linaro.org>
    Acked-by: Enric Balletbo i Serra <eballetbo@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220120104009.159147-2-krzysztof.kozlowski@canonical.com

commit 5e547d60dae7c66fe0c33654474eedcc1ddace67
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Thu Jan 20 11:40:08 2022 +0100

    dt-bindings: display: bridge: drop Enric Balletbo i Serra from maintainers
    
    Enric Balletbo i Serra emails bounce:
    
      <enric.balletbo@collabora.com>: Recipient address rejected: User unknown in  local recipient table
    
    so drop him from the maintainers, similarly to commit 3119c28634dd
    ("MAINTAINERS: Chrome: Drop Enric Balletbo i Serra").  Add generic DRM
    bridge maintainers to Analogix ANX7814.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Neil Armstrong <narmstrong@baylibre.com>
    Acked-by: Enric Balletbo i Serra <eballetbo@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220120104009.159147-1-krzysztof.kozlowski@canonical.com

commit 30f308999426871e1b896384093e9a681099f521
Author: Helge Deller <deller@gmx.de>
Date:   Mon Jan 17 10:10:10 2022 +0100

    parisc: Fix missing prototype for 'toc_intr' warning in toc.c
    
    Fix a missing prototype warning noticed by the kernel test robot.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 5f7ee6e37a3cadefe45378c17c4285fa41141d92
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 14 07:57:20 2022 +0100

    parisc: Autodetect default output device and set console= kernel parameter
    
    Usually palo (the PA-RISC boot loader) will check at boot time if the
    machine/firmware was configured to use the serial line (ttyS0, SERIAL_x)
    or the graphical display (tty0, graph) as default output device and add
    the correct "console=ttyS0" or "console=tty0" Linux kernel parameter to
    the kernel command line when starting the Linux kernel.
    
    But the kernel could also have been started via the HP-UX boot loader
    or directly in qemu, in which cases the console parameter is missing.
    
    This patch fixes this problem by adding the correct console= parameter
    if it's missing in the current kernel command line.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit bd25c378527f3fde38a496ac2744cbd3924f0803
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 14 07:52:07 2022 +0100

    parisc: Use safer strscpy() in setup_cmdline()
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 9b22c17a3cc5f61b195da624cbb48634b4e42055
Author: Rob Herring <robh@kernel.org>
Date:   Tue Jan 18 11:34:04 2022 -0600

    of: Check 'of_node_reused' flag on of_match_device()
    
    Commit 0f153a1b8193 ("usb: chipidea: Set the DT node on the child
    device") caused the child device to match on the parent driver
    instead of the child's driver since the child's DT node pointer matched.
    The worst case result is a loop of the parent driver probing another
    instance and creating yet another child device eventually exhausting the
    stack. If the child driver happens to match first, then everything works
    fine.
    
    A device sharing the DT node should never do DT based driver matching,
    so let's simply check of_node_reused in of_match_device() to prevent
    that.
    
    Fixes: 0f153a1b8193 ("usb: chipidea: Set the DT node on the child device")
    Link: https://lore.kernel.org/all/20220114105620.GK18506@ediswmail.ad.cirrus.com/
    Reported-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Cc: Frank Rowand <frowand.list@gmail.com>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: Tony Lindgren <tony@atomide.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Peter Chen <peter.chen@nxp.com>
    Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220118173404.1891800-1-robh@kernel.org

commit 2ca42c3ad9ed875b136065b010753a4caaaa1d38
Author: Michael Walle <michael@walle.cc>
Date:   Tue Jan 18 18:35:03 2022 +0100

    of: property: define of_property_read_u{8,16,32,64}_array() unconditionally
    
    We can get rid of all the empty stubs because all these functions call
    of_property_read_variable_u{8,16,32,64}_array() which already have an
    empty stub if CONFIG_OF is not defined.
    
    Signed-off-by: Michael Walle <michael@walle.cc>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220118173504.2867523-3-michael@walle.cc

commit 66a8f7f04979f4ad739085f01d99c8caf620b4f5
Author: Michael Walle <michael@walle.cc>
Date:   Tue Jan 18 18:35:02 2022 +0100

    of: base: make small of_parse_phandle() variants static inline
    
    Make all the smaller variants of the of_parse_phandle() static inline.
    This also let us remove the empty function stubs if CONFIG_OF is not
    defined.
    
    Suggested-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Michael Walle <michael@walle.cc>
    [robh: move index < 0 check into __of_parse_phandle_with_args]
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220118173504.2867523-2-michael@walle.cc

commit 25e20b505e0e2454ff6713c0cef4bcdd66dffb95
Author: Rob Herring <robh@kernel.org>
Date:   Tue Jan 18 19:56:11 2022 -0600

    dt-bindings: mfd: cirrus,madera: Fix 'interrupts' in example
    
    The 'interrupts' properties takes an irq number, not a phandle, and
    'interrupt-parent' isn't needed in examples.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220119015611.2442819-1-robh@kernel.org

commit 986536b952fd7070f5137358df7b055f3081dd2b
Author: Rob Herring <robh@kernel.org>
Date:   Tue Jan 18 19:56:26 2022 -0600

    dt-bindings: Fix array schemas encoded as matrices
    
    The YAML DT encoding has leaked into some array properties. Properties
    which are defined as an array should have a schema that's just an array.
    That means there should only be a single level of 'minItems',
    'maxItems', and/or 'items'.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Marc Kleine-Budde <mkl@pengutronix.de>
    Link: https://lore.kernel.org/r/20220119015627.2443334-1-robh@kernel.org

commit 3b8428b84539c78fdc8006c17ebd25afd4722d51
Author: Joe Damato <jdamato@fastly.com>
Date:   Wed Dec 8 17:56:33 2021 -0800

    i40e: fix unsigned stat widths
    
    Change i40e_update_vsi_stats and struct i40e_vsi to use u64 fields to match
    the width of the stats counters in struct i40e_rx_queue_stats.
    
    Update debugfs code to use the correct format specifier for u64.
    
    Fixes: 41c445ff0f48 ("i40e: main driver core")
    Signed-off-by: Joe Damato <jdamato@fastly.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 0f344c8129a5337dae50e31b817dd50a60ff238c
Author: Karen Sornek <karen.sornek@intel.com>
Date:   Thu Dec 2 12:52:01 2021 +0100

    i40e: Fix for failed to init adminq while VF reset
    
    Fix for failed to init adminq: -53 while VF is resetting via MAC
    address changing procedure.
    Added sync module to avoid reading deadbeef value in reinit adminq
    during software reset.
    Without this patch it is possible to trigger VF reset procedure
    during reinit adminq. This resulted in an incorrect reading of
    value from the AQP registers and generated the -53 error.
    
    Fixes: 5c3c48ac6bf5 ("i40e: implement virtual device interface")
    Signed-off-by: Grzegorz Szczurek <grzegorzx.szczurek@intel.com>
    Signed-off-by: Karen Sornek <karen.sornek@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 92947844b8beee988c0ce17082b705c2f75f0742
Author: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
Date:   Fri Nov 26 11:11:22 2021 +0100

    i40e: Fix queues reservation for XDP
    
    When XDP was configured on a system with large number of CPUs
    and X722 NIC there was a call trace with NULL pointer dereference.
    
    i40e 0000:87:00.0: failed to get tracking for 256 queues for VSI 0 err -12
    i40e 0000:87:00.0: setup of MAIN VSI failed
    
    BUG: kernel NULL pointer dereference, address: 0000000000000000
    RIP: 0010:i40e_xdp+0xea/0x1b0 [i40e]
    Call Trace:
    ? i40e_reconfig_rss_queues+0x130/0x130 [i40e]
    dev_xdp_install+0x61/0xe0
    dev_xdp_attach+0x18a/0x4c0
    dev_change_xdp_fd+0x1e6/0x220
    do_setlink+0x616/0x1030
    ? ahci_port_stop+0x80/0x80
    ? ata_qc_issue+0x107/0x1e0
    ? lock_timer_base+0x61/0x80
    ? __mod_timer+0x202/0x380
    rtnl_setlink+0xe5/0x170
    ? bpf_lsm_binder_transaction+0x10/0x10
    ? security_capable+0x36/0x50
    rtnetlink_rcv_msg+0x121/0x350
    ? rtnl_calcit.isra.0+0x100/0x100
    netlink_rcv_skb+0x50/0xf0
    netlink_unicast+0x1d3/0x2a0
    netlink_sendmsg+0x22a/0x440
    sock_sendmsg+0x5e/0x60
    __sys_sendto+0xf0/0x160
    ? __sys_getsockname+0x7e/0xc0
    ? _copy_from_user+0x3c/0x80
    ? __sys_setsockopt+0xc8/0x1a0
    __x64_sys_sendto+0x20/0x30
    do_syscall_64+0x33/0x40
    entry_SYSCALL_64_after_hwframe+0x44/0xae
    RIP: 0033:0x7f83fa7a39e0
    
    This was caused by PF queue pile fragmentation due to
    flow director VSI queue being placed right after main VSI.
    Because of this main VSI was not able to resize its
    queue allocation for XDP resulting in no queues allocated
    for main VSI when XDP was turned on.
    
    Fix this by always allocating last queue in PF queue pile
    for a flow director VSI.
    
    Fixes: 41c445ff0f48 ("i40e: main driver core")
    Fixes: 74608d17fe29 ("i40e: add support for XDP_TX action")
    Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
    Tested-by: Kiran Bhandare <kiranx.bhandare@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit d701658a50a471591094b3eb3961b4926cc8f104
Author: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Date:   Fri Nov 5 11:17:00 2021 +0000

    i40e: Fix issue when maximum queues is exceeded
    
    Before this patch VF interface vanished when
    maximum queue number was exceeded. Driver tried
    to add next queues even if there was not enough
    space. PF sent incorrect number of queues to
    the VF when there were not enough of them.
    
    Add an additional condition introduced to check
    available space in 'qp_pile' before proceeding.
    This condition makes it impossible to add queues
    if they number is greater than the number resulting
    from available space.
    Also add the search for free space in PF queue
    pair piles.
    
    Without this patch VF interfaces are not seen
    when available space for queues has been
    exceeded and following logs appears permanently
    in dmesg:
    "Unable to get VF config (-32)".
    "VF 62 failed opcode 3, retval: -5"
    "Unable to get VF config due to PF error condition, not retrying"
    
    Fixes: 7daa6bf3294e ("i40e: driver core headers")
    Fixes: 41c445ff0f48 ("i40e: main driver core")
    Signed-off-by: Jaroslaw Gawin <jaroslawx.gawin@intel.com>
    Signed-off-by: Slawomir Laba <slawomirx.laba@intel.com>
    Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
    Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 9b13bd53134c9ddd544a790125199fdbdb505e67
Author: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Date:   Thu Oct 28 13:51:14 2021 +0000

    i40e: Increase delay to 1 s after global EMP reset
    
    Recently simplified i40e_rebuild causes that FW sometimes
    is not ready after NVM update, the ping does not return.
    
    Increase the delay in case of EMP reset.
    Old delay of 300 ms was introduced for specific cards for 710 series.
    Now it works for all the cards and delay was increased.
    
    Fixes: 1fa51a650e1d ("i40e: Add delay after EMP reset for firmware to recover")
    Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
    Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 8da46c0f98a1a17bc8f6d324d82b4d26e1448869
Author: Minghao Chi <chi.minghao@zte.com.cn>
Date:   Wed Jan 12 08:27:29 2022 +0000

    RISC-V: Remove redundant err variable
    
    Return value from user_regset_copyin() directly instead of taking this
    in another redundant variable.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
    Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 46cdc45acb089c811d9a54fd50af33b96e5fae9d
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Jan 20 10:28:13 2022 -0700

    block: fix async_depth sysfs interface for mq-deadline
    
    A previous commit added this feature, but it inadvertently used the wrong
    variable to show/store the setting from/to, victimized by copy/paste. Fix
    it up so that the async_depth sysfs interface reads and writes from the
    right setting.
    
    Fixes: 07757588e507 ("block/mq-deadline: Reserve 25% of scheduler tags for synchronous requests")
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215485
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 58dfff3e984dfb96dae98008e6ea0ab92248d003
Author: Rob Herring <robh@kernel.org>
Date:   Tue Jan 18 19:53:25 2022 -0600

    dt-bindings: Drop unnecessary pinctrl properties
    
    For a single pinctrl mode, it is not necessary to define pinctrl
    properties as the tools always allow pinctrl properties.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Acked-by: Mark Brown <broonie@kernel.org>
    Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220119015325.2438277-1-robh@kernel.org

commit db3f02df1853acf4d678bcddb3f1eab23219b410
Author: Ron Economos <w6rz@comcast.net>
Date:   Thu Dec 30 22:11:06 2021 -0800

    riscv: dts: sifive unmatched: Add gpio poweroff
    
    Some of the GPIO pins on the Unmatched are wire up to control the power
    of the board, indicate that in the device tree.
    
    Signed-off-by: Ron Economos <w6rz@comcast.net>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 3c2905ea79245fd37c2ab9d9384ab85d4732e3ef
Author: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Date:   Wed Dec 29 20:24:58 2021 +0100

    riscv: canaan: remove useless select of non-existing config SYSCON
    
    The config SYSCON never existed in the kernel repository; so, the select of
    that config in ./drivers/soc/canaan/Kconfig has no effect.
    
    Presumably, this was just some mistake, assuming some symmetry in handling
    and naming of configs that simply does not exist.
    
    Remove this useless select of a non-existing config.
    
    Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 26fb751ca37846c912daa347be298bfd945cc560
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:18 2022 -0800

    RISC-V: Do not use cpumask data structure for hartid bitmap
    
    Currently, SBI APIs accept a hartmask that is generated from struct
    cpumask. Cpumask data structure can hold upto NR_CPUs value. Thus, it
    is not the correct data structure for hartids as it can be higher
    than NR_CPUs for platforms with sparse or discontguous hartids.
    
    Remove all association between hartid mask and struct cpumask.
    
    Reviewed-by: Anup Patel <anup@brainfault.org> (For Linux RISC-V changes)
    Acked-by: Anup Patel <anup@brainfault.org> (For KVM RISC-V changes)
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 2ffc48fc7071da4b2d881b0f21d37ed05feb697b
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:17 2022 -0800

    RISC-V: Move spinwait booting method to its own config
    
    The spinwait booting method should only be used for platforms with older
    firmware without SBI HSM extension or M-mode firmware because spinwait
    method can't support cpu hotplug, kexec or sparse hartid. It is better
    to move the entire spinwait implementation to its own config which can
    be disabled if required. It is enabled by default to maintain backward
    compatibility and M-mode Linux.
    
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 0b39eb38f85908e039ce8c9f09868438e029757b
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:16 2022 -0800

    RISC-V: Move the entire hart selection via lottery to SMP
    
    The booting hart selection via lottery is only useful for SMP systems.
    Moreover, the lottery selection is only necessary for systems using
    spinwait booting method. It is better to keep the entire lottery
    selection together so that it can be disabled in future.
    
    Move the lottery selection code to under CONFIG_SMP.
    
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit c78f94f35cf6486c4057317e8de3ddc4c62e12c7
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:15 2022 -0800

    RISC-V: Use __cpu_up_stack/task_pointer only for spinwait method
    
    The __cpu_up_stack/task_pointer array is only used for spinwait method
    now. The per cpu array based lookup is also fragile for platforms with
    discontiguous/sparse hartids. The spinwait method is only used for
    M-mode Linux or older firmwares without SBI HSM extension. For general
    Linux systems, ordered booting method is preferred anyways to support
    cpu hotplug and kexec.
    
    Make sure that __cpu_up_stack/task_pointer is only used for spinwait
    method. Take this opportunity to rename it to
    __cpu_spinwait_stack/task_pointer to emphasize the purpose as well.
    
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 410bb20a698d4c95c63e7f2b6f6f7d8da43795f5
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:14 2022 -0800

    RISC-V: Do not print the SBI version during HSM extension boot print
    
    The HSM extension information log also prints the SBI version v0.2. This
    is misleading as the underlying firmware SBI version may be different
    from v0.2.
    
    Remove the unncessary printing of SBI version.
    
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 9a2451f1866344d38b4a1dc20396e3a03954fcd7
Author: Atish Patra <atishp@rivosinc.com>
Date:   Thu Jan 20 01:09:13 2022 -0800

    RISC-V: Avoid using per cpu array for ordered booting
    
    Currently both order booting and spinwait approach uses a per cpu
    array to update stack & task pointer. This approach will not work for the
    following cases.
    1. If NR_CPUs are configured to be less than highest hart id.
    2. A platform has sparse hartid.
    
    This issue can be fixed for ordered booting as the booting cpu brings up
    one cpu at a time using SBI HSM extension which has opaque parameter
    that is unused until now.
    
    Introduce a common secondary boot data structure that can store the stack
    and task pointer. Secondary harts will use this data while booting up
    to setup the sp & tp.
    
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Atish Patra <atishp@rivosinc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit e2e83a73d7ce66f62c7830a85619542ef59c90e4
Author: Wei Wang <wei.w.wang@intel.com>
Date:   Wed Jan 19 23:50:03 2022 -0500

    docs: kvm: fix WARNINGs from api.rst
    
    Use the api number 134 for KVM_GET_XSAVE2, instead of 42, which has been
    used by KVM_GET_XSAVE.
    Also, fix the WARNINGs of the underlines being too short.
    
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Message-Id: <20220120045003.315177-1-wei.w.wang@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 83a34ad848937462aa64fa3d48f8c0b4034f2503
Author: Jinrong Liang <cloudliang@tencent.com>
Date:   Wed Jan 19 22:03:25 2022 +0800

    selftests: kvm/x86: Fix the warning in lib/x86_64/processor.c
    
    The following warning appears when executing
    make -C tools/testing/selftests/kvm
    
    include/x86_64/processor.h:290:2: warning: 'ecx' may be used uninitialized in this
    function [-Wmaybe-uninitialized]
      asm volatile("cpuid"
      ^~~
    lib/x86_64/processor.c:1523:21: note: 'ecx' was declared here
      uint32_t eax, ebx, ecx, edx, max_ext_leaf;
    
    Just initialize ecx to remove this warning.
    
    Fixes: c8cc43c1eae2 ("selftests: KVM: avoid failures due to reserved HyperTransport region")
    Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
    Message-Id: <20220119140325.59369-1-cloudliang@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a0f4ba7f51ea736a6b4ccf58563507d7af9128fb
Author: Jinrong Liang <cloudliang@tencent.com>
Date:   Wed Jan 19 21:39:10 2022 +0800

    selftests: kvm/x86: Fix the warning in pmu_event_filter_test.c
    
    The following warning appears when executing
    make -C tools/testing/selftests/kvm
    
    x86_64/pmu_event_filter_test.c: In function 'vcpu_supports_intel_br_retired':
    x86_64/pmu_event_filter_test.c:241:28: warning: variable 'cpuid' set but not used [-Wunused-but-set-variable]
      241 |         struct kvm_cpuid2 *cpuid;
          |                            ^~~~~
    x86_64/pmu_event_filter_test.c: In function 'vcpu_supports_amd_zen_br_retired':
    x86_64/pmu_event_filter_test.c:258:28: warning: variable 'cpuid' set but not used [-Wunused-but-set-variable]
      258 |         struct kvm_cpuid2 *cpuid;
          |                            ^~~~~
    
    Just delete the unused variables to stay away from warnings.
    
    Fixes: dc7e75b3b3ee ("selftests: kvm/x86: Add test for KVM_SET_PMU_EVENT_FILTER")
    Signed-off-by: Jinrong Liang <cloudliang@tencent.com>
    Message-Id: <20220119133910.56285-1-cloudliang@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 3938d5a2f9369d1ebd56320629fed395ce327e9c
Author: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Date:   Thu Dec 16 13:35:38 2021 +0100

    riscv: default to CONFIG_RISCV_SBI_V01=n
    
    The SBI 0.1 specification is obsolete. The current version is 0.3.
    Hence we should not rely by default on SBI 0.1 being implemented.
    
    Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 2c271fe77d52a0555161926c232cd5bc07178b39
Merge: 64f29d8856a9e 9f51ce0b9e73f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 17:38:23 2022 +0200

    Merge tag 'gpio-fixes-for-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio fixes from Bartosz Golaszewski:
     "Fix the same error check issue in two drivers. And then the drivers
      are fixed even more because the first patches were incomplete which I
      missed.
    
      Summary:
    
       - fix the error checks of platform_get_irq() in gpio-mpc8xxx and
         gpio-idt3243x"
    
    * tag 'gpio-fixes-for-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux:
      gpio: mpc8xxx: Fix an ignored error return from platform_get_irq()
      gpio: idt3243x: Fix an ignored error return from platform_get_irq()
      gpio: idt3243x: Fix IRQ check in idt_gpio_probe
      gpio: mpc8xxx: Fix IRQ check in mpc8xxx_probe

commit 6e10e21915c1ab6eaa145f7b5ebaf4500af1b011
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Sep 8 16:09:08 2021 -0300

    tools headers UAPI: Sync files changed by new set_mempolicy_home_node syscall
    
    To pick the changes in these csets:
    
      21b084fdf2a49ca1 ("mm/mempolicy: wire up syscall set_mempolicy_home_node")
    
    That add support for this new syscall in tools such as 'perf trace'.
    
    For instance, this is now possible:
    
      [root@five ~]# perf trace -e set_mempolicy_home_node
      ^C[root@five ~]#
      [root@five ~]# perf trace -v -e set_mempolicy_home_node
      Using CPUID AuthenticAMD-25-21-0
      event qualifier tracepoint filter: (common_pid != 253729 && common_pid != 3585) && (id == 450)
      mmap size 528384B
      ^C[root@five ~]
      [root@five ~]# perf trace -v -e set*  --max-events 5
      Using CPUID AuthenticAMD-25-21-0
      event qualifier tracepoint filter: (common_pid != 253734 && common_pid != 3585) && (id == 38 || id == 54 || id == 105 || id == 106 || id == 109 || id == 112 || id == 113 || id == 114 || id == 116 || id == 117 || id == 119 || id == 122 || id == 123 || id == 141 || id == 160 || id == 164 || id == 170 || id == 171 || id == 188 || id == 205 || id == 218 || id == 238 || id == 273 || id == 308 || id == 450)
      mmap size 528384B
           0.000 ( 0.008 ms): bash/253735 setpgid(pid: 253735 (bash), pgid: 253735 (bash))      = 0
        6849.011 ( 0.008 ms): bash/16046 setpgid(pid: 253736 (bash), pgid: 253736 (bash))       = 0
        6849.080 ( 0.005 ms): bash/253736 setpgid(pid: 253736 (bash), pgid: 253736 (bash))      = 0
        7437.718 ( 0.009 ms): gnome-shell/253737 set_robust_list(head: 0x7f34b527e920, len: 24) = 0
       13445.986 ( 0.010 ms): bash/16046 setpgid(pid: 253738 (bash), pgid: 253738 (bash))       = 0
      [root@five ~]#
    
    That is the filter expression attached to the raw_syscalls:sys_{enter,exit}
    tracepoints.
    
      $ find tools/perf/arch/ -name "syscall*tbl" | xargs grep -w set_mempolicy_home_node
      tools/perf/arch/mips/entry/syscalls/syscall_n64.tbl:450       common  set_mempolicy_home_node         sys_set_mempolicy_home_node
      tools/perf/arch/powerpc/entry/syscalls/syscall.tbl:450        nospu   set_mempolicy_home_node         sys_set_mempolicy_home_node
      tools/perf/arch/s390/entry/syscalls/syscall.tbl:450  common   set_mempolicy_home_node sys_set_mempolicy_home_node     sys_set_mempolicy_home_node
      tools/perf/arch/x86/entry/syscalls/syscall_64.tbl:450 common  set_mempolicy_home_node sys_set_mempolicy_home_node
      $
    
      $ grep -w set_mempolicy_home_node /tmp/build/perf/arch/x86/include/generated/asm/syscalls_64.c
            [450] = "set_mempolicy_home_node",
      $
    
    This addresses these perf build warnings:
    
      Warning: Kernel ABI header at 'tools/include/uapi/asm-generic/unistd.h' differs from latest version at 'include/uapi/asm-generic/unistd.h'
      diff -u tools/include/uapi/asm-generic/unistd.h include/uapi/asm-generic/unistd.h
      Warning: Kernel ABI header at 'tools/perf/arch/x86/entry/syscalls/syscall_64.tbl' differs from latest version at 'arch/x86/entry/syscalls/syscall_64.tbl'
      diff -u tools/perf/arch/x86/entry/syscalls/syscall_64.tbl arch/x86/entry/syscalls/syscall_64.tbl
      Warning: Kernel ABI header at 'tools/perf/arch/powerpc/entry/syscalls/syscall.tbl' differs from latest version at 'arch/powerpc/kernel/syscalls/syscall.tbl'
      diff -u tools/perf/arch/powerpc/entry/syscalls/syscall.tbl arch/powerpc/kernel/syscalls/syscall.tbl
      Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl'
      diff -u tools/perf/arch/s390/entry/syscalls/syscall.tbl arch/s390/kernel/syscalls/syscall.tbl
      Warning: Kernel ABI header at 'tools/perf/arch/mips/entry/syscalls/syscall_n64.tbl' differs from latest version at 'arch/mips/kernel/syscalls/syscall_n64.tbl'
      diff -u tools/perf/arch/mips/entry/syscalls/syscall_n64.tbl arch/mips/kernel/syscalls/syscall_n64.tbl
    
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 2a1355f0bf41a2132d522ed7a2a7eb1cc4fe3d8f
Author: Stefan Binding <sbinding@opensource.cirrus.com>
Date:   Thu Jan 20 10:56:18 2022 +0000

    ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409
    
    Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
    Signed-off-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220120105618.249144-1-vitalyr@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 3ee859e384d453d6ac68bfd5971f630d9fa46ad3
Author: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Date:   Sun Jan 9 18:36:43 2022 +0900

    block: Fix wrong offset in bio_truncate()
    
    bio_truncate() clears the buffer outside of last block of bdev, however
    current bio_truncate() is using the wrong offset of page. So it can
    return the uninitialized data.
    
    This happened when both of truncated/corrupted FS and userspace (via
    bdev) are trying to read the last of bdev.
    
    Reported-by: syzbot+ac94ae5f68b84197f41c@syzkaller.appspotmail.com
    Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
    Reviewed-by: Ming Lei <ming.lei@redhat.com>
    Link: https://lore.kernel.org/r/875yqt1c9g.fsf@mail.parknet.co.jp
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 217663f101a56ef77f82273818253fff082bf503
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Thu Jan 20 13:57:22 2022 +0100

    fanotify: remove variable set but not used
    
    The code that uses the pointer info has been removed in 7326e382c21e
    ("fanotify: report old and/or new parent+name in FAN_RENAME event").
    and fanotify_event_info() doesn't change 'event', so the declaration and
    assignment of info can be removed.
    
    Eliminate the following clang warning:
    fs/notify/fanotify/fanotify_user.c:161:24: warning: variable ‘info’ set
    but not used
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Jan Kara <jack@suse.cz>

commit 57afdc0aab094b4c811b3fe030b2567812a495f3
Merge: 6cee105e7f2ce 0959bc4bd4206
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 20 11:58:45 2022 +0000

    Merge branch 'stmmac-fixes'
    
    Yuji Ishikawa says:
    
    ====================
    net: stmmac: dwmac-visconti: Fix bit definitions and clock configuration for RMII mode
    
    This series is a fix for RMII/MII operation mode of the dwmac-visconti driver.
    It is composed of two parts:
    
    * 1/2: fix constant definitions for cleared bits in ETHER_CLK_SEL register
    * 2/2: fix configuration of ETHER_CLK_SEL register for running in RMII operation mode.
    
      net: stmmac: dwmac-visconti: Fix bit definitions for ETHER_CLK_SEL
        v1 -> v2:
          - added Fixes tag to commit message
    
      net: stmmac: dwmac-visconti: Fix clock configuration for RMII mode
        v1 -> v2:
          - added Fixes tag to commit message
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0959bc4bd4206433ed101a1332a23e93ad16ec77
Author: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
Date:   Wed Jan 19 13:46:48 2022 +0900

    net: stmmac: dwmac-visconti: Fix clock configuration for RMII mode
    
    Bit pattern of the ETHER_CLOCK_SEL register for RMII/MII mode should be fixed.
    Also, some control bits should be modified with a specific sequence.
    
    Fixes: b38dd98ff8d0 ("net: stmmac: Add Toshiba Visconti SoCs glue driver")
    Signed-off-by: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
    Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1ba1a4a90fa416a6f389206416c5f488cf8b1543
Author: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
Date:   Wed Jan 19 13:46:47 2022 +0900

    net: stmmac: dwmac-visconti: Fix bit definitions for ETHER_CLK_SEL
    
    just 0 should be used to represent cleared bits
    
    * ETHER_CLK_SEL_DIV_SEL_20
    * ETHER_CLK_SEL_TX_CLK_EXT_SEL_IN
    * ETHER_CLK_SEL_RX_CLK_EXT_SEL_IN
    * ETHER_CLK_SEL_TX_CLK_O_TX_I
    * ETHER_CLK_SEL_RMII_CLK_SEL_IN
    
    Fixes: b38dd98ff8d0 ("net: stmmac: Add Toshiba Visconti SoCs glue driver")
    Signed-off-by: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
    Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 64f29d8856a9e0d1fcdc5344f76e70c364b941cb
Merge: 67ed868d23711 a0b3a15eab6bc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 13:46:20 2022 +0200

    Merge tag 'ceph-for-5.17-rc1' of git://github.com/ceph/ceph-client
    
    Pull ceph updates from Ilya Dryomov:
     "The highlight is the new mount "device" string syntax implemented by
      Venky Shankar. It solves some long-standing issues with using
      different auth entities and/or mounting different CephFS filesystems
      from the same cluster, remounting and also misleading /proc/mounts
      contents. The existing syntax of course remains to be maintained.
    
      On top of that, there is a couple of fixes for edge cases in quota and
      a new mount option for turning on unbuffered I/O mode globally instead
      of on a per-file basis with ioctl(CEPH_IOC_SYNCIO)"
    
    * tag 'ceph-for-5.17-rc1' of git://github.com/ceph/ceph-client:
      ceph: move CEPH_SUPER_MAGIC definition to magic.h
      ceph: remove redundant Lsx caps check
      ceph: add new "nopagecache" option
      ceph: don't check for quotas on MDS stray dirs
      ceph: drop send metrics debug message
      rbd: make const pointer spaces a static const array
      ceph: Fix incorrect statfs report for small quota
      ceph: mount syntax module parameter
      doc: document new CephFS mount device syntax
      ceph: record updated mon_addr on remount
      ceph: new device mount syntax
      libceph: rename parse_fsid() to ceph_parse_fsid() and export
      libceph: generalize addr/ip parsing based on delimiter

commit 67ed868d23711e9cec9e8adb7ae5596ae76f7cbb
Merge: c5a0b6e40d0b8 ac090d9c90b08
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 13:39:13 2022 +0200

    Merge tag '5.17-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd
    
    Pull ksmbd server fixes from Steve French:
    
     - authentication fix
    
     - RDMA (smbdirect) fixes (including fix for a memory corruption, and
       some performance improvements)
    
     - multiple improvements for multichannel
    
     - misc fixes, including crediting (flow control) improvements
    
     - cleanup fixes, including some kernel doc fixes
    
    * tag '5.17-rc-ksmbd-server-fixes' of git://git.samba.org/ksmbd: (23 commits)
      ksmbd: fix guest connection failure with nautilus
      ksmbd: uninitialized variable in create_socket()
      ksmbd: smbd: fix missing client's memory region invalidation
      ksmbd: add smb-direct shutdown
      ksmbd: smbd: change the default maximum read/write, receive size
      ksmbd: smbd: create MR pool
      ksmbd: add reserved room in ipc request/response
      ksmbd: smbd: call rdma_accept() under CM handler
      ksmbd: limits exceeding the maximum allowable outstanding requests
      ksmbd: move credit charge deduction under processing request
      ksmbd: add support for smb2 max credit parameter
      ksmbd: set 445 port to smbdirect port by default
      ksmbd: register ksmbd ib client with ib_register_client()
      ksmbd: Fix smb2_get_name() kernel-doc comment
      ksmbd: Delete an invalid argument description in smb2_populate_readdir_entry()
      ksmbd: Fix smb2_set_info_file() kernel-doc comment
      ksmbd: Fix buffer_check_err() kernel-doc comment
      ksmbd: fix multi session connection failure
      ksmbd: set both ipv4 and ipv6 in FSCTL_QUERY_NETWORK_INTERFACE_INFO
      ksmbd: set RSS capable in FSCTL_QUERY_NETWORK_INTERFACE_INFO
      ...

commit 6cee105e7f2ced596373951d9ea08dacc3883c68
Author: Ido Schimmel <idosch@nvidia.com>
Date:   Thu Jan 20 10:05:46 2022 +0200

    ipv6_tunnel: Rate limit warning messages
    
    The warning messages can be invoked from the data path for every packet
    transmitted through an ip6gre netdev, leading to high CPU utilization.
    
    Fix that by rate limiting the messages.
    
    Fixes: 09c6bbf090ec ("[IPV6]: Do mandatory IPv6 tunnel endpoint checks in realtime")
    Reported-by: Maksym Yaremchuk <maksymy@nvidia.com>
    Tested-by: Maksym Yaremchuk <maksymy@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Reviewed-by: Amit Cohen <amcohen@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c5a0b6e40d0b8c040dbfc37f7403e99867768d92
Merge: 41652aae67c79 2bed2ced40c97
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 13:31:46 2022 +0200

    Merge tag 'vfio-v5.17-rc1' of git://github.com/awilliam/linux-vfio
    
    Pull VFIO updates from Alex Williamson:
    
     - Fix sparse endian warnings in IGD code (Alex Williamson)
    
     - Balance kvzalloc with kvfree (Jiacheng Shi)
    
    * tag 'vfio-v5.17-rc1' of git://github.com/awilliam/linux-vfio:
      vfio/iommu_type1: replace kfree with kvfree
      vfio/pci: Resolve sparse endian warnings in IGD support

commit e2f08207c558bc0bc8abaa557cdb29bad776ac7b
Author: Moshe Tal <moshet@nvidia.com>
Date:   Thu Jan 20 11:55:50 2022 +0200

    ethtool: Fix link extended state for big endian
    
    The link extended sub-states are assigned as enum that is an integer
    size but read from a union as u8, this is working for small values on
    little endian systems but for big endian this always give 0. Fix the
    variable in the union to match the enum size.
    
    Fixes: ecc31c60240b ("ethtool: Add link extended state")
    Signed-off-by: Moshe Tal <moshet@nvidia.com>
    Reviewed-by: Ido Schimmel <idosch@nvidia.com>
    Tested-by: Ido Schimmel <idosch@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Amit Cohen <amcohen@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d15c7e875d44367005370e6a82e8f3a382a04f9b
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:52:43 2022 -0600

    net: phy: broadcom: hook up soft_reset for BCM54616S
    
    A problem was encountered with the Bel-Fuse 1GBT-SFP05 SFP module (which
    is a 1 Gbps copper module operating in SGMII mode with an internal
    BCM54616S PHY device) using the Xilinx AXI Ethernet MAC core, where the
    module would work properly on the initial insertion or boot of the
    device, but after the device was rebooted, the link would either only
    come up at 100 Mbps speeds or go up and down erratically.
    
    I found no meaningful changes in the PHY configuration registers between
    the working and non-working boots, but the status registers seemed to
    have a lot of error indications set on the SERDES side of the device on
    the non-working boot. I suspect the problem is that whatever happens on
    the SGMII link when the device is rebooted and the FPGA logic gets
    reloaded ends up putting the module's onboard PHY into a bad state.
    
    Since commit 6e2d85ec0559 ("net: phy: Stop with excessive soft reset")
    the genphy_soft_reset call is not made automatically by the PHY core
    unless the callback is explicitly specified in the driver structure. For
    most of these Broadcom devices, there is probably a hardware reset that
    gets asserted to reset the PHY during boot, however for SFP modules
    (where the BCM54616S is commonly found) no such reset line exists, so if
    the board keeps the SFP cage powered up across a reboot, it will end up
    with no reset occurring during reboots.
    
    Hook up the genphy_soft_reset callback for BCM54616S to ensure that a
    PHY reset is performed before the device is initialized. This appears to
    fix the issue with erratic operation after a reboot with this SFP
    module.
    
    Fixes: 6e2d85ec0559 ("net: phy: Stop with excessive soft reset")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 973bf8fdd12f0e70ea351c018e68edd377a836d1
Author: Victor Nogueira <victor@mojatatu.com>
Date:   Tue Jan 18 14:19:09 2022 -0300

    net: sched: Clarify error message when qdisc kind is unknown
    
    When adding a tc rule with a qdisc kind that is not supported or not
    compiled into the kernel, the kernel emits the following error: "Error:
    Specified qdisc not found.". Found via tdc testing when ETS qdisc was not
    compiled in and it was not obvious right away what the message meant
    without looking at the kernel code.
    
    Change the error message to be more explicit and say the qdisc kind is
    unknown.
    
    Signed-off-by: Victor Nogueira <victor@mojatatu.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 41652aae67c79a50d56174468de03bdb04d61d4b
Merge: fa2e1ba3e9e39 3f0565451cc0c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 13:25:01 2022 +0200

    Merge tag 'pwm/for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm
    
    Pull pwm updates from Thierry Reding:
     "This contains a number of nice cleanups and improvements for the core
      and various drivers, as well as a minor tweak to the json-schema
      device tree bindings"
    
    * tag 'pwm/for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm:
      dt-bindings: pwm: Avoid selecting schema on node name match
      pwm: img: Use only a single idiom to get a runtime PM reference
      pwm: vt8500: Implement .apply() callback
      pwm: img: Implement .apply() callback
      pwm: twl: Implement .apply() callback
      pwm: Restore initial state if a legacy callback fails
      pwm: Prevent a glitch for legacy drivers
      pwm: Move legacy driver handling into a dedicated function

commit 47934e06b65637c88a762d9c98329ae6e3238888
Author: Congyu Liu <liu3101@purdue.edu>
Date:   Tue Jan 18 14:20:13 2022 -0500

    net: fix information leakage in /proc/net/ptype
    
    In one net namespace, after creating a packet socket without binding
    it to a device, users in other net namespaces can observe the new
    `packet_type` added by this packet socket by reading `/proc/net/ptype`
    file. This is minor information leakage as packet socket is
    namespace aware.
    
    Add a net pointer in `packet_type` to keep the net namespace of
    of corresponding packet socket. In `ptype_seq_show`, this net pointer
    must be checked when it is not NULL.
    
    Fixes: 2feb27dbe00c ("[NETNS]: Minor information leak via /proc/net/ptype file.")
    Signed-off-by: Congyu Liu <liu3101@purdue.edu>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit bb425a7598479fa0f171ec806033c440f218b0ce
Author: Peng Fan <peng.fan@nxp.com>
Date:   Wed Dec 15 14:45:58 2021 +0800

    arm64: mm: apply __ro_after_init to memory_limit
    
    This variable is only set during initialization, so mark with
    __ro_after_init.
    
    Signed-off-by: Peng Fan <peng.fan@nxp.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Link: https://lore.kernel.org/r/20211215064559.2843555-1-peng.fan@oss.nxp.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 3364c6ce23c6e347c63fc895e0d6d1e8a9407849
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 12 12:22:59 2022 -0800

    arm64: atomics: lse: Dereference matching size
    
    When building with -Warray-bounds, the following warning is generated:
    
    In file included from ./arch/arm64/include/asm/lse.h:16,
                     from ./arch/arm64/include/asm/cmpxchg.h:14,
                     from ./arch/arm64/include/asm/atomic.h:16,
                     from ./include/linux/atomic.h:7,
                     from ./include/asm-generic/bitops/atomic.h:5,
                     from ./arch/arm64/include/asm/bitops.h:25,
                     from ./include/linux/bitops.h:33,
                     from ./include/linux/kernel.h:22,
                     from kernel/printk/printk.c:22:
    ./arch/arm64/include/asm/atomic_lse.h:247:9: warning: array subscript 'long unsigned int[0]' is partly outside array bounds of 'atomic_t[1]' [-Warray-bounds]
      247 |         asm volatile(                                                   \
          |         ^~~
    ./arch/arm64/include/asm/atomic_lse.h:266:1: note: in expansion of macro '__CMPXCHG_CASE'
      266 | __CMPXCHG_CASE(w,  , acq_, 32,  a, "memory")
          | ^~~~~~~~~~~~~~
    kernel/printk/printk.c:3606:17: note: while referencing 'printk_cpulock_owner'
     3606 | static atomic_t printk_cpulock_owner = ATOMIC_INIT(-1);
          |                 ^~~~~~~~~~~~~~~~~~~~
    
    This is due to the compiler seeing an unsigned long * cast against
    something (atomic_t) that is int sized. Replace the cast with the
    matching size cast. This results in no change in binary output.
    
    Note that __ll_sc__cmpxchg_case_##name##sz already uses the same
    constraint:
    
            [v] "+Q" (*(u##sz *)ptr
    
    Which is why only the LSE form needs updating and not the
    LL/SC form, so this change is unlikely to be problematic.
    
    Cc: Will Deacon <will@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Boqun Feng <boqun.feng@gmail.com>
    Cc: linux-arm-kernel@lists.infradead.org
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Acked-by: Mark Rutland <mark.rutland@arm.com>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Link: https://lore.kernel.org/r/20220112202259.3950286-1-keescook@chromium.org
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit 440323b6cf5b9896013a78c4f578823e8243a7fd
Author: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Date:   Fri Jan 14 18:58:57 2022 +0800

    asm-generic: Add missing brackets for io_stop_wc macro
    
    After using io_stop_wc(), drivers reports following compile error when
    compiled on X86.
    
      drivers/net/ethernet/hisilicon/hns3/hns3_enet.c: In function ‘hns3_tx_push_bd’:
      drivers/net/ethernet/hisilicon/hns3/hns3_enet.c:2058:12: error: expected ‘;’ before ‘(’ token
        io_stop_wc();
                  ^
    It is because I missed to add the brackets after io_stop_wc macro. So
    let's add the missing brackets.
    
    Fixes: d5624bb29f49 ("asm-generic: introduce io_stop_wc() and add implementation for ARM64")
    Reported-by: Guangbin Huang <huangguangbin2@huawei.com>
    Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
    Link: https://lore.kernel.org/r/20220114105857.126300-1-wangxiongfeng2@huawei.com
    Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

commit fa2e1ba3e9e39072fa7a6a9d11ac432c505b4ac7
Merge: f4484d138b31e ff9fc0a31d85f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 10:57:05 2022 +0200

    Merge tag 'net-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Pull networking fixes from Jakub Kicinski:
     "Including fixes from netfilter, bpf.
    
      Quite a handful of old regression fixes but most of those are
      pre-5.16.
    
      Current release - regressions:
    
       - fix memory leaks in the skb free deferral scheme if upper layer
         protocols are used, i.e. in-kernel TCP readers like TLS
    
      Current release - new code bugs:
    
       - nf_tables: fix NULL check typo in _clone() functions
    
       - change the default to y for Vertexcom vendor Kconfig
    
       - a couple of fixes to incorrect uses of ref tracking
    
       - two fixes for constifying netdev->dev_addr
    
      Previous releases - regressions:
    
       - bpf:
          - various verifier fixes mainly around register offset handling
            when passed to helper functions
          - fix mount source displayed for bpffs (none -> bpffs)
    
       - bonding:
          - fix extraction of ports for connection hash calculation
          - fix bond_xmit_broadcast return value when some devices are down
    
       - phy: marvell: add Marvell specific PHY loopback
    
       - sch_api: don't skip qdisc attach on ingress, prevent ref leak
    
       - htb: restore minimal packet size handling in rate control
    
       - sfp: fix high power modules without diagnostic monitoring
    
       - mscc: ocelot:
          - don't let phylink re-enable TX PAUSE on the NPI port
          - don't dereference NULL pointers with shared tc filters
    
       - smsc95xx: correct reset handling for LAN9514
    
       - cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
    
       - phy: micrel: use kszphy_suspend/_resume for irq aware devices,
         avoid races with the interrupt
    
      Previous releases - always broken:
    
       - xdp: check prog type before updating BPF link
    
       - smc: resolve various races around abnormal connection termination
    
       - sit: allow encapsulated IPv6 traffic to be delivered locally
    
       - axienet: fix init/reset handling, add missing barriers, read the
         right status words, stop queues correctly
    
       - add missing dev_put() in sock_timestamping_bind_phc()
    
      Misc:
    
       - ipv4: prevent accidentally passing RTO_ONLINK to
         ip_route_output_key_hash() by sanitizing flags
    
       - ipv4: avoid quadratic behavior in netns dismantle
    
       - stmmac: dwmac-oxnas: add support for OX810SE
    
       - fsl: xgmac_mdio: add workaround for erratum A-009885"
    
    * tag 'net-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (92 commits)
      ipv4: add net_hash_mix() dispersion to fib_info_laddrhash keys
      ipv4: avoid quadratic behavior in netns dismantle
      net/fsl: xgmac_mdio: Fix incorrect iounmap when removing module
      powerpc/fsl/dts: Enable WA for erratum A-009885 on fman3l MDIO buses
      dt-bindings: net: Document fsl,erratum-a009885
      net/fsl: xgmac_mdio: Add workaround for erratum A-009885
      net: mscc: ocelot: fix using match before it is set
      net: phy: micrel: use kszphy_suspend()/kszphy_resume for irq aware devices
      net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
      nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
      net: axienet: increase default TX ring size to 128
      net: axienet: fix for TX busy handling
      net: axienet: fix number of TX ring slots for available check
      net: axienet: Fix TX ring slot available check
      net: axienet: limit minimum TX ring size
      net: axienet: add missing memory barriers
      net: axienet: reset core on initialization prior to MDIO access
      net: axienet: Wait for PhyRstCmplt after core reset
      net: axienet: increase reset timeout
      bpf, selftests: Add ringbuf memory type confusion test
      ...

commit f4484d138b31e8fa1ba410363b5b9664f68974af
Merge: 1d1df41c5a333 b1e78ef3be253
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 10:41:01 2022 +0200

    Merge branch 'akpm' (patches from Andrew)
    
    Merge more updates from Andrew Morton:
     "55 patches.
    
      Subsystems affected by this patch series: percpu, procfs, sysctl,
      misc, core-kernel, get_maintainer, lib, checkpatch, binfmt, nilfs2,
      hfs, fat, adfs, panic, delayacct, kconfig, kcov, and ubsan"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>: (55 commits)
      lib: remove redundant assignment to variable ret
      ubsan: remove CONFIG_UBSAN_OBJECT_SIZE
      kcov: fix generic Kconfig dependencies if ARCH_WANTS_NO_INSTR
      lib/Kconfig.debug: make TEST_KMOD depend on PAGE_SIZE_LESS_THAN_256KB
      btrfs: use generic Kconfig option for 256kB page size limit
      arch/Kconfig: split PAGE_SIZE_LESS_THAN_256KB from PAGE_SIZE_LESS_THAN_64KB
      configs: introduce debug.config for CI-like setup
      delayacct: track delays from memory compact
      Documentation/accounting/delay-accounting.rst: add thrashing page cache and direct compact
      delayacct: cleanup flags in struct task_delay_info and functions use it
      delayacct: fix incomplete disable operation when switch enable to disable
      delayacct: support swapin delay accounting for swapping without blkio
      panic: remove oops_id
      panic: use error_report_end tracepoint on warnings
      fs/adfs: remove unneeded variable make code cleaner
      FAT: use io_schedule_timeout() instead of congestion_wait()
      hfsplus: use struct_group_attr() for memcpy() region
      nilfs2: remove redundant pointer sbufs
      fs/binfmt_elf: use PT_LOAD p_align values for static PIE
      const_structs.checkpatch: add frequently used ops structs
      ...

commit 9f51ce0b9e73f83bab2442b36d5e247a81bd3401
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Wed Jan 19 09:04:32 2022 +0800

    gpio: mpc8xxx: Fix an ignored error return from platform_get_irq()
    
    The return from the call to platform_get_irq() is int, it can be
    a negative error code, however this is being assigned to an unsigned
    int variable 'irqn', so making 'irqn' an int.
    
    Eliminate the following coccicheck warning:
    ./drivers/gpio/gpio-mpc8xxx.c:391:5-21: WARNING: Unsigned expression
    compared with zero: mpc8xxx_gc -> irqn < 0
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Fixes: 0b39536cc699 ("gpio: mpc8xxx: Fix IRQ check in mpc8xxx_probe")
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 7c1cf55577782725ea2bc24687767c8fe8e57486
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Wed Jan 19 09:04:31 2022 +0800

    gpio: idt3243x: Fix an ignored error return from platform_get_irq()
    
    The return from the call to platform_get_irq() is int, it can be
    a negative error code, however this is being assigned to an unsigned
    int variable 'parent_irq', so making 'parent_irq' an int.
    
    Eliminate the following coccicheck warning:
    ./drivers/gpio/gpio-idt3243x.c:167:6-16: WARNING: Unsigned expression
    compared with zero: parent_irq < 0
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Fixes: 30fee1d7462a ("gpio: idt3243x: Fix IRQ check in idt_gpio_probe")
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit b1e78ef3be2533973953a35a56739fda7325875c
Author: Colin Ian King <colin.king@intel.com>
Date:   Wed Jan 19 18:10:38 2022 -0800

    lib: remove redundant assignment to variable ret
    
    The variable ret is being assigned a value that is never read.  If the
    for-loop is entered then ret is immediately re-assigned a new value.  If
    the for-loop is not executed ret is never read.  The assignment is
    redundant and can be removed.
    
    Link: https://lkml.kernel.org/r/20211230134557.83633-1-colin.i.king@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 69d0db01e210e07fe915e5da91b54a867cda040f
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 19 18:10:35 2022 -0800

    ubsan: remove CONFIG_UBSAN_OBJECT_SIZE
    
    The object-size sanitizer is redundant to -Warray-bounds, and
    inappropriately performs its checks at run-time when all information
    needed for the evaluation is available at compile-time, making it quite
    difficult to use:
    
      https://bugzilla.kernel.org/show_bug.cgi?id=214861
    
    With -Warray-bounds almost enabled globally, it doesn't make sense to
    keep this around.
    
    Link: https://lkml.kernel.org/r/20211203235346.110809-1-keescook@chromium.org
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Marco Elver <elver@google.com>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Michal Marek <michal.lkml@markovi.net>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Cc: Nathan Chancellor <nathan@kernel.org>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bece04b5b41dd7730dd06aec0d6b15c53d1fbb5a
Author: Marco Elver <elver@google.com>
Date:   Wed Jan 19 18:10:31 2022 -0800

    kcov: fix generic Kconfig dependencies if ARCH_WANTS_NO_INSTR
    
    Until recent versions of GCC and Clang, it was not possible to disable
    KCOV instrumentation via a function attribute.  The relevant function
    attribute was introduced in 540540d06e9d9 ("kcov: add
    __no_sanitize_coverage to fix noinstr for all architectures").
    
    x86 was the first architecture to want a working noinstr, and at the
    time no compiler support for the attribute existed yet.  Therefore,
    commit 0f1441b44e823 ("objtool: Fix noinstr vs KCOV") introduced the
    ability to NOP __sanitizer_cov_*() calls in .noinstr.text.
    
    However, this doesn't work for other architectures like arm64 and s390
    that want a working noinstr per ARCH_WANTS_NO_INSTR.
    
    At the time of 0f1441b44e823, we didn't yet have ARCH_WANTS_NO_INSTR,
    but now we can move the Kconfig dependency checks to the generic KCOV
    option.  KCOV will be available if:
    
            - architecture does not care about noinstr, OR
            - we have objtool support (like on x86), OR
            - GCC is 12.0 or newer, OR
            - Clang is 13.0 or newer.
    
    Link: https://lkml.kernel.org/r/20211201152604.3984495-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bbd2e05fad3e692ff2495895975bd0fce02bdbae
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Jan 19 18:10:28 2022 -0800

    lib/Kconfig.debug: make TEST_KMOD depend on PAGE_SIZE_LESS_THAN_256KB
    
    Commit b05fbcc36be1 ("btrfs: disable build on platforms having page size
    256K") disabled btrfs for configurations that used a 256kB page size.
    However, it did not fully solve the problem because CONFIG_TEST_KMOD
    selects CONFIG_BTRFS, which does not account for the dependency.  This
    results in a Kconfig warning and the failed BUILD_BUG_ON error
    returning.
    
      WARNING: unmet direct dependencies detected for BTRFS_FS
        Depends on [n]: BLOCK [=y] && !PPC_256K_PAGES && !PAGE_SIZE_256KB [=y]
        Selected by [m]:
        - TEST_KMOD [=m] && RUNTIME_TESTING_MENU [=y] && m && MODULES [=y] && NETDEVICES [=y] && NET_CORE [=y] && INET [=y] && BLOCK [=y]
    
    To resolve this, add CONFIG_PAGE_SIZE_LESS_THAN_256KB as a dependency of
    CONFIG_TEST_KMOD so there is no more invalid configuration or build
    errors.
    
    Link: https://lkml.kernel.org/r/20211129230141.228085-4-nathan@kernel.org
    Fixes: b05fbcc36be1 ("btrfs: disable build on platforms having page size 256K")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Chris Mason <clm@fb.com>
    Cc: David Sterba <dsterba@suse.com>
    Cc: Josef Bacik <josef@toxicpanda.com>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e9009095998a8de4491692e89ca303fb74047c9e
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Jan 19 18:10:25 2022 -0800

    btrfs: use generic Kconfig option for 256kB page size limit
    
    Use the newly introduced CONFIG_PAGE_SIZE_LESS_THAN_256KB to describe
    the dependency introduced by commit b05fbcc36be1 ("btrfs: disable build
    on platforms having page size 256K").
    
    Link: https://lkml.kernel.org/r/20211129230141.228085-3-nathan@kernel.org
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Acked-by: David Sterba <dsterba@suse.com>
    Cc: Chris Mason <clm@fb.com>
    Cc: Josef Bacik <josef@toxicpanda.com>
    Cc: kernel test robot <lkp@intel.com>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e4bbd20d8c2b9fb5a937bf132775f5257ccb0412
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Wed Jan 19 18:10:22 2022 -0800

    arch/Kconfig: split PAGE_SIZE_LESS_THAN_256KB from PAGE_SIZE_LESS_THAN_64KB
    
    Patch series "Fix CONFIG_TEST_KMOD with 256kB page size".
    
    The kernel test robot reported a build error [1] from a failed assertion
    in fs/btrfs/inode.c with a hexagon randconfig that includes
    CONFIG_PAGE_SIZE_256KB.  This error is the same one that was addressed
    by commit b05fbcc36be1 ("btrfs: disable build on platforms having page
    size 256K") but CONFIG_TEST_KMOD selects CONFIG_BTRFS without having the
    "page size less than 256kB dependency", which results in the error
    reappearing.
    
    The first patch introduces CONFIG_PAGE_SIZE_LESS_THAN_256KB by splitting
    it off from CONFIG_PAGE_SIZE_LESS_THAN_64KB, which was introduced in
    commit 1f0e290cc5fd ("arch: Add generic Kconfig option indicating page
    size smaller than 64k") for a similar reason in 5.16-rc3.
    
    The second patch uses that configuration option for CONFIG_BTRFS to
    reduce duplication.
    
    The third patch resolves the build error by adding
    CONFIG_PAGE_SIZE_LESS_THAN_256KB as a dependency to CONFIG_TEST_KMOD so
    that CONFIG_BTRFS does not get enabled under that invalid configuration.
    
    [1]: https://lore.kernel.org/r/202111270255.UYOoN5VN-lkp@intel.com/
    
    This patch (of 3):
    
    btrfs requires a page size smaller than 256kB.  To use that dependency
    in other places, introduce CONFIG_PAGE_SIZE_LESS_THAN_256KB and reuse
    that dependency in CONFIG_PAGE_SIZE_LESS_THAN_64KB.
    
    Link: https://lkml.kernel.org/r/20211129230141.228085-1-nathan@kernel.org
    Link: https://lkml.kernel.org/r/20211129230141.228085-2-nathan@kernel.org
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Cc: Chris Mason <clm@fb.com>
    Cc: Josef Bacik <josef@toxicpanda.com>
    Cc: David Sterba <dsterba@suse.com>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0aaa8977acbf3996d351f51b3b15295943092f63
Author: Qian Cai <quic_qiancai@quicinc.com>
Date:   Wed Jan 19 18:10:18 2022 -0800

    configs: introduce debug.config for CI-like setup
    
    Some general debugging features like kmemleak, KASAN, lockdep, UBSAN etc
    help fix many viruses like a microscope.  On the other hand, those
    features are scatter around and mixed up with more situational debugging
    options making them difficult to consume properly.  This cold help
    amplify the general debugging/testing efforts and help establish
    sensitive default values for those options across the broad.  This could
    also help different distros to collaborate on maintaining debug-flavored
    kernels.
    
    The config is based on years' experiences running daily CI inside the
    largest enterprise Linux distro company to seek regressions on
    linux-next builds on different bare-metal and virtual platforms.  It can
    be used for example,
    
      $ make ARCH=arm64 defconfig debug.config
    
    Since KASAN and KCSAN can't be enabled together, we will need to create
    a separate one for KCSAN later as well.
    
    Link: https://lkml.kernel.org/r/20211115134754.7334-1-quic_qiancai@quicinc.com
    Signed-off-by: Qian Cai <quic_qiancai@quicinc.com>
    Acked-by: Paul E. McKenney <paulmck@kernel.org>
    Cc: Marco Elver <elver@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Daniel Thompson <daniel.thompson@linaro.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Naresh Kamboju <naresh.kamboju@linaro.org>
    Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5bf18281534451bf1ad56a45a3085cd7ad46860d
Author: wangyong <wang.yong12@zte.com.cn>
Date:   Wed Jan 19 18:10:15 2022 -0800

    delayacct: track delays from memory compact
    
    Delay accounting does not track the delay of memory compact.  When there
    is not enough free memory, tasks can spend a amount of their time
    waiting for compact.
    
    To get the impact of tasks in direct memory compact, measure the delay
    when allocating memory through memory compact.
    
    Also update tools/accounting/getdelays.c:
    
        / # ./getdelays_next  -di -p 304
        print delayacct stats ON
        printing IO accounting
        PID     304
    
        CPU             count     real total  virtual total    delay total  delay average
                          277      780000000      849039485       18877296          0.068ms
        IO              count    delay total  delay average
                            0              0              0ms
        SWAP            count    delay total  delay average
                            0              0              0ms
        RECLAIM         count    delay total  delay average
                            5    11088812685           2217ms
        THRASHING       count    delay total  delay average
                            0              0              0ms
        COMPACT         count    delay total  delay average
                            3          72758              0ms
        watch: read=0, write=0, cancelled_write=0
    
    Link: https://lkml.kernel.org/r/1638619795-71451-1-git-send-email-wang.yong12@zte.com.cn
    Signed-off-by: wangyong <wang.yong12@zte.com.cn>
    Reviewed-by: Jiang Xuexin <jiang.xuexin@zte.com.cn>
    Reviewed-by: Zhang Wenya <zhang.wenya1@zte.com.cn>
    Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
    Reviewed-by: Balbir Singh <bsingharora@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ec710aa8b2385e6a2239f79120fbf9b78400865b
Author: wangyong <wang.yong12@zte.com.cn>
Date:   Wed Jan 19 18:10:12 2022 -0800

    Documentation/accounting/delay-accounting.rst: add thrashing page cache and direct compact
    
    Add thrashing page cache and direct compact related descriptions and
    update the usage of getdelays userspace utility.
    
    The following patches modifications have been updated:
    https://lore.kernel.org/all/20190312102002.31737-4-jinpuwang@gmail.com/
    https://lore.kernel.org/all/1638619795-71451-1-git-send-email-
    wang.yong12@zte.com.cn/
    
    Link: https://lkml.kernel.org/r/1639583021-92977-1-git-send-email-wang.yong12@zte.com.cn
    Signed-off-by: wangyong <wang.yong12@zte.com.cn>
    Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Cc: Balbir Singh <bsingharora@gmail.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ingo Molnar <mingo@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1193829da1a6728249cd02577a020bd64fd9c160
Author: Yang Yang <yang.yang29@zte.com.cn>
Date:   Wed Jan 19 18:10:09 2022 -0800

    delayacct: cleanup flags in struct task_delay_info and functions use it
    
    Flags in struct task_delay_info is used to distinguish the difference
    between swapin and blkio delay acountings.  But after patch "delayacct:
    support swapin delay accounting for swapping without blkio", there is no
    need to do that since swapin and blkio delay accounting use their own
    functions.
    
    Link: https://lkml.kernel.org/r/20211124065958.36703-1-yang.yang29@zte.com.cn
    Signed-off-by: Yang Yang <yang.yang29@zte.com.cn>
    Cc: Balbir Singh <bsingharora@gmail.com>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 82065b7266899fbdce4c7394d7dd02688161f0cf
Author: Yang Yang <yang.yang29@zte.com.cn>
Date:   Wed Jan 19 18:10:06 2022 -0800

    delayacct: fix incomplete disable operation when switch enable to disable
    
    When a task is created after delayacct is enabled, kernel will do all
    the delay accountings for that task.  The problems is if user disables
    delayacct by set /proc/sys/kernel/task_delayacct to zero, only blkio
    delay accounting is disabled.
    
    Now disable all the kinds of delay accountings when
    /proc/sys/kernel/task_delayacct sets to zero.
    
    Link: https://lkml.kernel.org/r/20211123140342.32962-1-ran.xiaokai@zte.com.cn
    Signed-off-by: Yang Yang <yang.yang29@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Cc: Balbir Singh <bsingharora@gmail.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a3d5dc908a5f572ce3e31fe83fd2459a1c3c5422
Author: Yang Yang <yang.yang29@zte.com.cn>
Date:   Wed Jan 19 18:10:02 2022 -0800

    delayacct: support swapin delay accounting for swapping without blkio
    
    Currently delayacct accounts swapin delay only for swapping that cause
    blkio.  If we use zram for swapping, tools/accounting/getdelays can't
    get any SWAP delay.
    
    It's useful to get zram swapin delay information, for example to adjust
    compress algorithm or /proc/sys/vm/swappiness.
    
    Reference to PSI, it accounts any kind of swapping by doing its work in
    swap_readpage(), no matter whether swapping causes blkio.  Let delayacct
    do the similar work.
    
    Link: https://lkml.kernel.org/r/20211112083813.8559-1-yang.yang29@zte.com.cn
    Signed-off-by: Yang Yang <yang.yang29@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Cc: Balbir Singh <bsingharora@gmail.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e83a4472bf9f556d01984048e398e64246c4dd6f
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Wed Jan 19 18:09:59 2022 -0800

    panic: remove oops_id
    
    The oops id has been added as part of the end of trace marker for the
    kerneloops.org project.  The id is used to automatically identify
    duplicate submissions of the same report.  Identical looking reports
    with different a id can be considered as the same oops occurred again.
    
    The early initialisation of the oops_id can create a warning if the
    random core is not yet fully initialized.  On PREEMPT_RT it is
    problematic if the id is initialized on demand from non preemptible
    context.
    
    The kernel oops project is not available since 2017.  Remove the oops_id
    and use 0 in the output in case parser rely on it.
    
    Link: https://bugs.debian.org/953172
    Link: https://lkml.kernel.org/r/Ybdi16aP2NEugWHq@linutronix.de
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Arjan van de Ven <arjan@linux.intel.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 23b36fec7e14f8cf1c17e832e53dd4761e0dfe83
Author: Marco Elver <elver@google.com>
Date:   Wed Jan 19 18:09:56 2022 -0800

    panic: use error_report_end tracepoint on warnings
    
    Introduce the error detector "warning" to the error_report event and use
    the error_report_end tracepoint at the end of a warning report.
    
    This allows in-kernel tests but also userspace to more easily determine
    if a warning occurred without polling kernel logs.
    
    [akpm@linux-foundation.org: add comma to enum list, per Andy]
    
    Link: https://lkml.kernel.org/r/20211115085630.1756817-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Wei Liu <wei.liu@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Arnd Bergmann <arnd@arndb.de>
    Cc: John Ogness <john.ogness@linutronix.de>
    Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Alexander Popov <alex.popov@linux.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 25d2e88632c9069cb21e23340e14cd19b8a0b1df
Author: Minghao Chi <chi.minghao@zte.com.cn>
Date:   Wed Jan 19 18:09:53 2022 -0800

    fs/adfs: remove unneeded variable make code cleaner
    
    Return value directly instead of taking this in a variable.
    
    Link: https://lkml.kernel.org/r/20211210023211.424609-1-chi.minghao@zte.com.cn
    Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cm>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9bb56d592532526f638468ed0781b7ab7925a1ec
Author: NeilBrown <neilb@suse.de>
Date:   Wed Jan 19 18:09:50 2022 -0800

    FAT: use io_schedule_timeout() instead of congestion_wait()
    
    congestion_wait() in this context is just a sleep - block devices do not
    support congestion signalling any more.
    
    The goal for this wait, which was introduced in commit ae78bf9c4f5f
    ("[PATCH] add -o flush for fat") is to wait for any recently written
    data to get to storage.  We currently have no direct mechanism to do
    this, so a simple wait that behaves identically to the current
    congestion_wait() is the best we can do.
    
    This is a step towards removing congestion_wait()
    
    Link: https://lkml.kernel.org/r/163936544519.22433.13400436295732112065@noble.neil.brown.name
    Signed-off-by: NeilBrown <neilb@suse.de>
    Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e35fa567a082a7547a4ec21e50a27eecf38961aa
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 19 18:09:47 2022 -0800

    hfsplus: use struct_group_attr() for memcpy() region
    
    In preparation for FORTIFY_SOURCE performing compile-time and run-time
    field bounds checking for memset(), avoid intentionally writing across
    neighboring fields.
    
    Add struct_group() to mark the "info" region (containing struct DInfo
    and struct DXInfo structs) in struct hfsplus_cat_folder and struct
    hfsplus_cat_file that are written into directly, so the compiler can
    correctly reason about the expected size of the writes.
    
    "pahole" shows no size nor member offset changes to struct
    hfsplus_cat_folder nor struct hfsplus_cat_file.  "objdump -d" shows no
    object code changes.
    
    Link: https://lkml.kernel.org/r/20211119192851.1046717-1-keescook@chromium.org
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Zhen Lei <thunder.leizhen@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e1ce8a97befa98566f49acb99c79cc233cf3a703
Author: Colin Ian King <colin.king@intel.com>
Date:   Wed Jan 19 18:09:44 2022 -0800

    nilfs2: remove redundant pointer sbufs
    
    Pointer sbufs is being assigned a value but it's not being used later
    on.  The pointer is redundant and can be removed.  Cleans up scan-build
    static analysis warning:
    
      fs/nilfs2/page.c:203:8: warning: Although the value stored to 'sbufs'
        is used in the enclosing expression, the value is never actually read
        from 'sbufs' [deadcode.DeadStores]
            sbh = sbufs = page_buffers(src);
    
    Link: https://lkml.kernel.org/r/20211211180955.550380-1-colin.i.king@gmail.com
    Link: https://lkml.kernel.org/r/1640712476-15136-1-git-send-email-konishi.ryusuke@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9630f0d60fec5fbcaa4435a66f75df1dc9704b66
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Wed Jan 19 18:09:40 2022 -0800

    fs/binfmt_elf: use PT_LOAD p_align values for static PIE
    
    Extend commit ce81bb256a22 ("fs/binfmt_elf: use PT_LOAD p_align values
    for suitable start address") which fixed PIE binaries built with
    -Wl,-z,max-page-size=0x200000, to cover static PIE binaries.  This
    fixes:
    
        https://bugzilla.kernel.org/show_bug.cgi?id=215275
    
    Tested by verifying static PIE binaries with -Wl,-z,max-page-size=0x200000 loading.
    
    Link: https://lkml.kernel.org/r/20211209174052.370537-1-hjl.tools@gmail.com
    Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
    Cc: Chris Kennelly <ckennelly@google.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Alexey Dobriyan <adobriyan@gmail.com>
    Cc: Song Liu <songliubraving@fb.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Sandeep Patil <sspatil@google.com>
    Cc: Fangrui Song <maskray@google.com>
    Cc: Nick Desaulniers <ndesaulniers@google.com>
    Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c55cdc5cd6663ff616c94ecf7204e92c7049bb5e
Author: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Date:   Wed Jan 19 18:09:37 2022 -0800

    const_structs.checkpatch: add frequently used ops structs
    
    Add commonly used structs (>50 instances) which are always or almost
    always const.
    
    Link: https://lkml.kernel.org/r/20211127101134.33101-1-rikard.falkeborn@gmail.com
    Signed-off-by: Rikard Falkeborn <rikard.falkeborn@gmail.com>
    Cc: Joe Perches <joe@perches.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b8709bce9089996528f594cd1f71f1a085761aad
Author: Joe Perches <joe@perches.com>
Date:   Wed Jan 19 18:09:34 2022 -0800

    checkpatch: improve Kconfig help test
    
    The Kconfig help test erroneously counts patch context lines as part of
    the help text.
    
    Fix that and improve the message block output.
    
    Link: https://lkml.kernel.org/r/06c0cdc157ae1502e8e9eb3624b9ea995cf11e7a.camel@perches.com
    Signed-off-by: Joe Perches <joe@perches.com>
    Tested-by: Randy Dunlap <rdunlap@infradead.org>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Andy Whitcroft <apw@canonical.com>
    Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>
    Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 36f8b348a94c12e30ca5c81eb31c9a445117ef7b
Author: Jerome Forissier <jerome@forissier.org>
Date:   Wed Jan 19 18:09:31 2022 -0800

    checkpatch: relax regexp for COMMIT_LOG_LONG_LINE
    
    One exceptions to the COMMIT_LOG_LONG_LINE rule is a file path followed
    by ':'.  That is typically some sort diagnostic message from a compiler
    or a build tool, in which case we don't want to wrap the lines but keep
    the message unmodified.
    
    The regular expression used to match this pattern currently doesn't
    accept absolute paths or + characters.  This can result in false
    positives as in the following (out-of-tree) example:
    
      ...
      /home/jerome/work/optee_repo_qemu/build/../toolchains/aarch32/bin/arm-linux-gnueabihf-ld.bfd: /home/jerome/work/toolchains-gcc10.2/aarch32/bin/../lib/gcc/arm-none-linux-gnueabihf/10.2.1/../../../../arm-none-linux-gnueabihf/lib/libstdc++.a(eh_alloc.o): in function `__cxa_allocate_exception':
      /tmp/dgboter/bbs/build03--cen7x86_64/buildbot/cen7x86_64--arm-none-linux-gnueabihf/build/src/gcc/libstdc++-v3/libsupc++/eh_alloc.cc:284: undefined reference to `malloc'
      ...
    
    Update the regular expression to match the above paths.
    
    Link: https://lkml.kernel.org/r/20210923143842.2837983-1-jerome@forissier.org
    Signed-off-by: Jerome Forissier <jerome@forissier.org>
    Acked-by: Joe Perches <joe@perches.com>
    Cc: Andy Whitcroft <apw@canonical.com>
    Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>
    Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e073e5ef90298d2d6e5e7f04b545a0815e92110c
Author: Andrey Konovalov <andreyknvl@gmail.com>
Date:   Wed Jan 19 18:09:28 2022 -0800

    lib/test_meminit: destroy cache in kmem_cache_alloc_bulk() test
    
    Make do_kmem_cache_size_bulk() destroy the cache it creates.
    
    Link: https://lkml.kernel.org/r/aced20a94bf04159a139f0846e41d38a1537debb.1640018297.git.andreyknvl@google.com
    Fixes: 03a9349ac0e0 ("lib/test_meminit: add a kmem_cache_alloc_bulk() test")
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
    Reviewed-by: Marco Elver <elver@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c7e4289cbe668c2743ac0fd623a2518dbc191dc0
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:09:25 2022 -0800

    uuid: remove licence boilerplate text from the header
    
    Remove licence boilerplate text from the UAPI header.
    
    Link: https://lkml.kernel.org/r/20211216113552.81199-2-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8e930a66993be0a5f9a97c7c1c76ef09db4ef8bb
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:09:22 2022 -0800

    uuid: discourage people from using UAPI header in new code
    
    Discourage people from using UAPI header in new code by adding a note.
    
    Link: https://lkml.kernel.org/r/20211216113552.81199-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 60c7801b121aa0e90d8aae7245859aec0ce2306f
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:09:19 2022 -0800

    kunit: replace kernel.h with the necessary inclusions
    
    When kernel.h is used in the headers it adds a lot into dependency hell,
    especially when there are circular dependencies are involved.
    
    Replace kernel.h inclusion with the list of what is really being used.
    
    Link: https://lkml.kernel.org/r/20211213204441.56204-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
    Tested-by: Brendan Higgins <brendanhiggins@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0acc968f352336a459f27ba1f23745a174933c9c
Author: Isabella Basso <isabbasso@riseup.net>
Date:   Wed Jan 19 18:09:15 2022 -0800

    test_hash.c: refactor into kunit
    
    Use KUnit framework to make tests more easily integrable with CIs.  Even
    though these tests are not yet properly written as unit tests this
    change should help in debugging.
    
    Also remove kernel messages (i.e.  through pr_info) as KUnit handles all
    debugging output and let it handle module init and exit details.
    
    Link: https://lkml.kernel.org/r/20211208183711.390454-6-isabbasso@riseup.net
    Reviewed-by: David Gow <davidgow@google.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Tested-by: David Gow <davidgow@google.com>
    Co-developed-by: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Signed-off-by: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Co-developed-by: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Signed-off-by: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Signed-off-by: Isabella Basso <isabbasso@riseup.net>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Cc: Daniel Latypov <dlatypov@google.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
    Cc: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 88168bf35c5260013daab4bddf944cd557cb6f08
Author: Isabella Basso <isabbasso@riseup.net>
Date:   Wed Jan 19 18:09:12 2022 -0800

    lib/Kconfig.debug: properly split hash test kernel entries
    
    Split TEST_HASH so that each entry only has one file.
    
    Note that there's no stringhash test file, but actually
    <linux/stringhash.h> tests are performed in lib/test_hash.c.
    
    Link: https://lkml.kernel.org/r/20211208183711.390454-5-isabbasso@riseup.net
    Reviewed-by: David Gow <davidgow@google.com>
    Tested-by: David Gow <davidgow@google.com>
    Signed-off-by: Isabella Basso <isabbasso@riseup.net>
    Cc: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Cc: Daniel Latypov <dlatypov@google.com>
    Cc: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: kernel test robot <lkp@intel.com>
    Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
    Cc: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5427d3d772a77a4d67fece057064832ec5cfa078
Author: Isabella Basso <isabbasso@riseup.net>
Date:   Wed Jan 19 18:09:09 2022 -0800

    test_hash.c: split test_hash_init
    
    Split up test_hash_init so that it calls each test more explicitly
    insofar it is possible without rewriting the entire file.  This aims at
    improving readability.
    
    Split tests performed on string_or as they don't interfere with those
    performed in hash_or.  Also separate pr_info calls about skipped tests
    as they're not part of the tests themselves, but only warn about
    (un)defined arch-specific hash functions.
    
    Link: https://lkml.kernel.org/r/20211208183711.390454-4-isabbasso@riseup.net
    Reviewed-by: David Gow <davidgow@google.com>
    Tested-by: David Gow <davidgow@google.com>
    Signed-off-by: Isabella Basso <isabbasso@riseup.net>
    Cc: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Cc: Daniel Latypov <dlatypov@google.com>
    Cc: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: kernel test robot <lkp@intel.com>
    Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
    Cc: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ae7880676bc8019ff61e49126c558ad7c4b6fa21
Author: Isabella Basso <isabbasso@riseup.net>
Date:   Wed Jan 19 18:09:05 2022 -0800

    test_hash.c: split test_int_hash into arch-specific functions
    
    Split the test_int_hash function to keep its mainloop separate from
    arch-specific chunks, which are only compiled as needed.  This aims at
    improving readability.
    
    Link: https://lkml.kernel.org/r/20211208183711.390454-3-isabbasso@riseup.net
    Reviewed-by: David Gow <davidgow@google.com>
    Tested-by: David Gow <davidgow@google.com>
    Signed-off-by: Isabella Basso <isabbasso@riseup.net>
    Cc: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Cc: Daniel Latypov <dlatypov@google.com>
    Cc: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: kernel test robot <lkp@intel.com>
    Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
    Cc: Shuah Khan <skhan@linuxfoundation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit fd0a1462405b087377e59b84e119fe7e2d08499a
Author: Isabella Basso <isabbasso@riseup.net>
Date:   Wed Jan 19 18:09:02 2022 -0800

    hash.h: remove unused define directive
    
    Patch series "test_hash.c: refactor into KUnit", v3.
    
    We refactored the lib/test_hash.c file into KUnit as part of the student
    group LKCAMP [1] introductory hackathon for kernel development.
    
    This test was pointed to our group by Daniel Latypov [2], so its full
    conversion into a pure KUnit test was our goal in this patch series, but
    we ran into many problems relating to it not being split as unit tests,
    which complicated matters a bit, as the reasoning behind the original
    tests is quite cryptic for those unfamiliar with hash implementations.
    
    Some interesting developments we'd like to highlight are:
    
     - In patch 1/5 we noticed that there was an unused define directive
       that could be removed.
    
     - In patch 4/5 we noticed how stringhash and hash tests are all under
       the lib/test_hash.c file, which might cause some confusion, and we
       also broke those kernel config entries up.
    
    Overall KUnit developments have been made in the other patches in this
    series:
    
    In patches 2/5, 3/5 and 5/5 we refactored the lib/test_hash.c file so as
    to make it more compatible with the KUnit style, whilst preserving the
    original idea of the maintainer who designed it (i.e.  George Spelvin),
    which might be undesirable for unit tests, but we assume it is enough
    for a first patch.
    
    This patch (of 5):
    
    Currently, there exist hash_32() and __hash_32() functions, which were
    introduced in a patch [1] targeting architecture specific optimizations.
    These functions can be overridden on a per-architecture basis to achieve
    such optimizations.  They must set their corresponding define directive
    (HAVE_ARCH_HASH_32 and HAVE_ARCH__HASH_32, respectively) so that header
    files can deal with these overrides properly.
    
    As the supported 32-bit architectures that have their own hash function
    implementation (i.e.  m68k, Microblaze, H8/300, pa-risc) have only been
    making use of the (more general) __hash_32() function (which only lacks
    a right shift operation when compared to the hash_32() function), remove
    the define directive corresponding to the arch-specific hash_32()
    implementation.
    
    [1] https://lore.kernel.org/lkml/20160525073311.5600.qmail@ns.sciencehorizons.net/
    
    [akpm@linux-foundation.org: hash_32_generic() becomes hash_32()]
    
    Link: https://lkml.kernel.org/r/20211208183711.390454-1-isabbasso@riseup.net
    Link: https://lkml.kernel.org/r/20211208183711.390454-2-isabbasso@riseup.net
    Reviewed-by: David Gow <davidgow@google.com>
    Tested-by: David Gow <davidgow@google.com>
    Co-developed-by: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Signed-off-by: Augusto Durães Camargo <augusto.duraes33@gmail.com>
    Co-developed-by: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Signed-off-by: Enzo Ferreira <ferreiraenzoa@gmail.com>
    Signed-off-by: Isabella Basso <isabbasso@riseup.net>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: Brendan Higgins <brendanhiggins@google.com>
    Cc: Daniel Latypov <dlatypov@google.com>
    Cc: Shuah Khan <skhan@linuxfoundation.org>
    Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
    Cc: kernel test robot <lkp@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a31f9336ed48317d61c2299d595ed14294ffe5f9
Author: Zhen Lei <thunder.leizhen@huawei.com>
Date:   Wed Jan 19 18:08:59 2022 -0800

    lib/list_debug.c: print more list debugging context in __list_del_entry_valid()
    
    Currently, the entry->prev and entry->next are considered to be valid as
    long as they are not LIST_POISON{1|2}.  However, the memory may be
    corrupted.  The prev->next is invalid probably because 'prev' is
    invalid, not because prev->next's content is illegal.
    
    Unfortunately, the printk and its subfunctions will modify the registers
    that hold the 'prev' and 'next', and we don't see this valuable
    information in the BUG context.
    
    So print the contents of 'entry->prev' and 'entry->next'.
    
    Here's an example:
      list_del corruption. prev->next should be c0ecbf74, but was c08410dc
      kernel BUG at lib/list_debug.c:53!
      ... ...
      PC is at __list_del_entry_valid+0x58/0x98
      LR is at __list_del_entry_valid+0x58/0x98
      psr: 60000093
      sp : c0ecbf30  ip : 00000000  fp : 00000001
      r10: c08410d0  r9 : 00000001  r8 : c0825e0c
      r7 : 20000013  r6 : c08410d0  r5 : c0ecbf74  r4 : c0ecbf74
      r3 : c0825d08  r2 : 00000000  r1 : df7ce6f4  r0 : 00000044
      ... ...
      Stack: (0xc0ecbf30 to 0xc0ecc000)
      bf20:                                     c0ecbf74 c0164fd0 c0ecbf70 c0165170
      bf40: c0eca000 c0840c00 c0840c00 c0824500 c0825e0c c0189bbc c088f404 60000013
      bf60: 60000013 c0e85100 000004ec 00000000 c0ebcdc0 c0ecbf74 c0ecbf74 c0825d08
      bf80: c0e807c0 c018965c 00000000 c013f2a0 c0e807c0 c013f154 00000000 00000000
      bfa0: 00000000 00000000 00000000 c01001b0 00000000 00000000 00000000 00000000
      bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
      bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
      (__list_del_entry_valid) from (__list_del_entry+0xc/0x20)
      (__list_del_entry) from (finish_swait+0x60/0x7c)
      (finish_swait) from (rcu_gp_kthread+0x560/0xa20)
      (rcu_gp_kthread) from (kthread+0x14c/0x15c)
      (kthread) from (ret_from_fork+0x14/0x24)
    
    At first, I thought prev->next was overwritten.  Later, I carefully
    analyzed the RCU code and the disassembly code.  The error occurred when
    deleting a node from the list rcu_state.gp_wq.  The System.map shows
    that the address of rcu_state is c0840c00.  Then I use gdb to obtain the
    offset of rcu_state.gp_wq.task_list.
    
      (gdb) p &((struct rcu_state *)0)->gp_wq.task_list
      $1 = (struct list_head *) 0x4dc
    
    Again:
      list_del corruption. prev->next should be c0ecbf74, but was c08410dc
    
      c08410dc = c0840c00 + 0x4dc = &rcu_state.gp_wq.task_list
    
    Because rcu_state.gp_wq has at most one node, so I can guess that "prev
    = &rcu_state.gp_wq.task_list".  But for other scenes, maybe I wasn't so
    lucky, I cannot figure out the value of 'prev'.
    
    Link: https://lkml.kernel.org/r/20211207025835.1909-1-thunder.leizhen@huawei.com
    Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
    Cc: "Paul E . McKenney" <paulmck@linux.vnet.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0425473037db40d9e322631f2d4dc6ef51f97e88
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:08:56 2022 -0800

    list: introduce list_is_head() helper and re-use it in list.h
    
    Introduce list_is_head() in the similar (*) way as it's done for
    list_entry_is_head().  Make use of it in the list.h.
    
    *) it's done as inliner and not a macro to be aligned with other
       list_is_*() APIs; while at it, make all three to have the same
       style.
    
    Link: https://lkml.kernel.org/r/20211201141824.81400-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 70ac69928e9717a313a4c72647ebe80663e397a3
Author: Alexey Dobriyan <adobriyan@gmail.com>
Date:   Wed Jan 19 18:08:53 2022 -0800

    kstrtox: uninline everything
    
    I've made a mistake of looking into lib/kstrtox.o code generation.
    
    The only function remotely performance critical is _parse_integer()
    (via /proc/*/map_files/*), everything else is not.
    
    Uninline everything, shrink lib/kstrtox.o by ~20 % !
    
    Space savings on x86_64:
    
            add/remove: 0/0 grow/shrink: 0/23 up/down: 0/-1269 (-1269 !!!)
            Function                                     old     new   delta
            kstrtoull                                     16      13      -3
            kstrtouint                                    59      48     -11
            kstrtou8                                      60      49     -11
            kstrtou16                                     61      50     -11
            _kstrtoul                                     46      35     -11
            kstrtoull_from_user                           95      83     -12
            kstrtoul_from_user                            95      83     -12
            kstrtoll                                      93      80     -13
            kstrtouint_from_user                         124      83     -41
            kstrtou8_from_user                           125      83     -42
            kstrtou16_from_user                          126      83     -43
            kstrtos8                                     101      50     -51
            kstrtos16                                    102      51     -51
            kstrtoint                                    100      49     -51
            _kstrtol                                      93      35     -58
            kstrtobool_from_user                         156      75     -81
            kstrtoll_from_user                           165      83     -82
            kstrtol_from_user                            165      83     -82
            kstrtoint_from_user                          172      83     -89
            kstrtos8_from_user                           173      83     -90
            kstrtos16_from_user                          174      83     -91
            _parse_integer                               136      10    -126
            _kstrtoull                                   308     101    -207
            Total: Before=3421236, After=3419967, chg -0.04%
    
    Link: https://lkml.kernel.org/r/YZDsFDhHst4m2Pnt@localhost.localdomain
    Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 26d98e9f78da8e49413b1cb6bcd0d63ac03b8c85
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Jan 19 18:08:50 2022 -0800

    get_maintainer: don't remind about no git repo when --nogit is used
    
    When --nogit is used with scripts/get_maintainer.pl, the script spews 4
    lines of unnecessary information (noise).  Do not print those lines when
    --nogit is specified.
    
    This change removes the printing of these 4 lines:
    
      ./scripts/get_maintainer.pl: No supported VCS found.  Add --nogit to options?
      Using a git repository produces better results.
      Try Linus Torvalds' latest git repository using:
      git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
    
    Link: https://lkml.kernel.org/r/20220102031424.3328-1-rdunlap@infradead.org
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Joe Perches <joe@perches.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7f8ca0edfe07d271ba6bef3cef5ec7fc1bbe8a68
Author: Davidlohr Bueso <dave@stgolabs.net>
Date:   Wed Jan 19 18:08:47 2022 -0800

    kernel/sys.c: only take tasklist_lock for get/setpriority(PRIO_PGRP)
    
    PRIO_PGRP needs the tasklist_lock mainly to serialize vs setpgid(2), to
    protect against any concurrent change_pid(PIDTYPE_PGID) that can move
    the task from one hlist to another while iterating.
    
    However, the remaining can only rely only on RCU:
    
    PRIO_PROCESS only does the task lookup and never iterates over tasklist
    and we already have an rcu-aware stable pointer.
    
    PRIO_USER is already racy vs setuid(2) so with creds being rcu
    protected, we can end up seeing stale data.  When removing the
    tasklist_lock there can be a race with (i) fork but this is benign as
    the child's nice is inherited and the new task is not observable by the
    user yet either, hence the return semantics do not differ.  And (ii) a
    race with exit, which is a small window and can cause us to miss a task
    which was removed from the list and it had the highest nice.
    
    Similarly change the buggy do_each_thread/while_each_thread combo in
    PRIO_USER for the rcu-safe for_each_process_thread flavor, which doesn't
    make use of next_thread/p->thread_group.
    
    [akpm@linux-foundation.org: coding style fixes]
    
    Link: https://lkml.kernel.org/r/20211210182250.43734-1-dave@stgolabs.net
    Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
    Acked-by: Oleg Nesterov <oleg@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d6986ce24fc00b0638bd29efe8fb7ba7619ed2aa
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:43 2022 -0800

    kthread: dynamically allocate memory to store kthread's full name
    
    When I was implementing a new per-cpu kthread cfs_migration, I found the
    comm of it "cfs_migration/%u" is truncated due to the limitation of
    TASK_COMM_LEN.  For example, the comm of the percpu thread on CPU10~19
    all have the same name "cfs_migration/1", which will confuse the user.
    This issue is not critical, because we can get the corresponding CPU
    from the task's Cpus_allowed.  But for kthreads corresponding to other
    hardware devices, it is not easy to get the detailed device info from
    task comm, for example,
    
        jbd2/nvme0n1p2-
        xfs-reclaim/sdf
    
    Currently there are so many truncated kthreads:
    
        rcu_tasks_kthre
        rcu_tasks_rude_
        rcu_tasks_trace
        poll_mpt3sas0_s
        ext4-rsv-conver
        xfs-reclaim/sd{a, b, c, ...}
        xfs-blockgc/sd{a, b, c, ...}
        xfs-inodegc/sd{a, b, c, ...}
        audit_send_repl
        ecryptfs-kthrea
        vfio-irqfd-clea
        jbd2/nvme0n1p2-
        ...
    
    We can shorten these names to work around this problem, but it may be
    not applied to all of the truncated kthreads.  Take 'jbd2/nvme0n1p2-'
    for example, it is a nice name, and it is not a good idea to shorten it.
    
    One possible way to fix this issue is extending the task comm size, but
    as task->comm is used in lots of places, that may cause some potential
    buffer overflows.  Another more conservative approach is introducing a
    new pointer to store kthread's full name if it is truncated, which won't
    introduce too much overhead as it is in the non-critical path.  Finally
    we make a dicision to use the second approach.  See also the discussions
    in this thread:
    https://lore.kernel.org/lkml/20211101060419.4682-1-laoar.shao@gmail.com/
    
    After this change, the full name of these truncated kthreads will be
    displayed via /proc/[pid]/comm:
    
        rcu_tasks_kthread
        rcu_tasks_rude_kthread
        rcu_tasks_trace_kthread
        poll_mpt3sas0_statu
        ext4-rsv-conversion
        xfs-reclaim/sdf1
        xfs-blockgc/sdf1
        xfs-inodegc/sdf1
        audit_send_reply
        ecryptfs-kthread
        vfio-irqfd-cleanup
        jbd2/nvme0n1p2-8
    
    Link: https://lkml.kernel.org/r/20211120112850.46047-1-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Reviewed-by: Petr Mladek <pmladek@suse.com>
    Suggested-by: Petr Mladek <pmladek@suse.com>
    Suggested-by: Steven Rostedt <rostedt@goodmis.org>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3087c61ed2c48548b74dd343a5209b87082c682d
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:40 2022 -0800

    tools/testing/selftests/bpf: replace open-coded 16 with TASK_COMM_LEN
    
    As the sched:sched_switch tracepoint args are derived from the kernel,
    we'd better make it same with the kernel.  So the macro TASK_COMM_LEN is
    converted to type enum, then all the BPF programs can get it through
    BTF.
    
    The BPF program which wants to use TASK_COMM_LEN should include the
    header vmlinux.h.  Regarding the test_stacktrace_map and
    test_tracepoint, as the type defined in linux/bpf.h are also defined in
    vmlinux.h, so we don't need to include linux/bpf.h again.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-8-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Acked-by: Andrii Nakryiko <andrii@kernel.org>
    Acked-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4cfb943537ed3716daf668ca5a33d3ce667f82a3
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:36 2022 -0800

    tools/bpf/bpftool/skeleton: replace bpf_probe_read_kernel with bpf_probe_read_kernel_str to get task comm
    
    bpf_probe_read_kernel_str() will add a nul terminator to the dst, then
    we don't care about if the dst size is big enough.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-7-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Acked-by: Andrii Nakryiko <andrii@kernel.org>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d068144d3b2cae09062ed936a3865c093ff69590
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:33 2022 -0800

    samples/bpf/test_overhead_kprobe_kern: replace bpf_probe_read_kernel with bpf_probe_read_kernel_str to get task comm
    
    bpf_probe_read_kernel_str() will add a nul terminator to the dst, then
    we don't care about if the dst size is big enough.  This patch also
    replaces the hard-coded 16 with TASK_COMM_LEN to make it grepable.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-6-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Acked-by: Andrii Nakryiko <andrii@kernel.org>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 95af469c4f609de011debc08e7a35b45201623a8
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:29 2022 -0800

    fs/binfmt_elf: replace open-coded string copy with get_task_comm
    
    It is better to use get_task_comm() instead of the open coded string
    copy as we do in other places.
    
    struct elf_prpsinfo is used to dump the task information in userspace
    coredump or kernel vmcore.  Below is the verification of vmcore,
    
      crash> ps
         PID    PPID  CPU       TASK        ST  %MEM     VSZ    RSS  COMM
            0      0   0  ffffffff9d21a940  RU   0.0       0      0  [swapper/0]
      >     0      0   1  ffffa09e40f85e80  RU   0.0       0      0  [swapper/1]
      >     0      0   2  ffffa09e40f81f80  RU   0.0       0      0  [swapper/2]
      >     0      0   3  ffffa09e40f83f00  RU   0.0       0      0  [swapper/3]
      >     0      0   4  ffffa09e40f80000  RU   0.0       0      0  [swapper/4]
      >     0      0   5  ffffa09e40f89f80  RU   0.0       0      0  [swapper/5]
            0      0   6  ffffa09e40f8bf00  RU   0.0       0      0  [swapper/6]
      >     0      0   7  ffffa09e40f88000  RU   0.0       0      0  [swapper/7]
      >     0      0   8  ffffa09e40f8de80  RU   0.0       0      0  [swapper/8]
      >     0      0   9  ffffa09e40f95e80  RU   0.0       0      0  [swapper/9]
      >     0      0  10  ffffa09e40f91f80  RU   0.0       0      0  [swapper/10]
      >     0      0  11  ffffa09e40f93f00  RU   0.0       0      0  [swapper/11]
      >     0      0  12  ffffa09e40f90000  RU   0.0       0      0  [swapper/12]
      >     0      0  13  ffffa09e40f9bf00  RU   0.0       0      0  [swapper/13]
      >     0      0  14  ffffa09e40f98000  RU   0.0       0      0  [swapper/14]
      >     0      0  15  ffffa09e40f9de80  RU   0.0       0      0  [swapper/15]
    
    It works well as expected.
    
    Some comments are added to explain why we use the hard-coded 16.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-5-laoar.shao@gmail.com
    Suggested-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7b6397d7e5dfabf2ce1e77739d2a24af31b8a43f
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:26 2022 -0800

    drivers/infiniband: replace open-coded string copy with get_task_comm
    
    We'd better use the helper get_task_comm() rather than the open-coded
    strlcpy() to get task comm.  As the comment above the hard-coded 16, we
    can replace it with TASK_COMM_LEN.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-4-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 503471ac36df60bba037c3b110d76f53a93f61b5
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:22 2022 -0800

    fs/exec: replace strncpy with strscpy_pad in __get_task_comm
    
    If the dest buffer size is smaller than sizeof(tsk->comm), the buffer
    will be without null ternimator, that may cause problem.  Using
    strscpy_pad() instead of strncpy() in __get_task_comm() can make the
    string always nul ternimated and zero padded.
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-3-laoar.shao@gmail.com
    Suggested-by: Kees Cook <keescook@chromium.org>
    Suggested-by: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 06c5088aeedafc06f8b33074d67e30077ba71b8b
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Wed Jan 19 18:08:19 2022 -0800

    fs/exec: replace strlcpy with strscpy_pad in __set_task_comm
    
    Patch series "task comm cleanups", v2.
    
    This patchset is part of the patchset "extend task comm from 16 to
    24"[1].  Now we have different opinion that dynamically allocates memory
    to store kthread's long name into a separate pointer, so I decide to
    take the useful cleanups apart from the original patchset and send it
    separately[2].
    
    These useful cleanups can make the usage around task comm less
    error-prone.  Furthermore, it will be useful if we want to extend task
    comm in the future.
    
    [1]. https://lore.kernel.org/lkml/20211101060419.4682-1-laoar.shao@gmail.com/
    [2]. https://lore.kernel.org/lkml/CALOAHbAx55AUo3bm8ZepZSZnw7A08cvKPdPyNTf=E_tPqmw5hw@mail.gmail.com/
    
    This patch (of 7):
    
    strlcpy() can trigger out-of-bound reads on the source string[1], we'd
    better use strscpy() instead.  To make it be robust against full tsk->comm
    copies that got noticed in other places, we should make sure it's zero
    padded.
    
    [1] https://github.com/KSPP/linux/issues/89
    
    Link: https://lkml.kernel.org/r/20211120112738.45980-1-laoar.shao@gmail.com
    Link: https://lkml.kernel.org/r/20211120112738.45980-2-laoar.shao@gmail.com
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
    Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Petr Mladek <pmladek@suse.com>
    Cc: Andrii Nakryiko <andrii@kernel.org>
    Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 40cbf09f060c8febef64541c463d4dd526abe445
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:08:16 2022 -0800

    kernel.h: include a note to discourage people from including it in headers
    
    Include a note at the top to discourage people from including it in
    headers.
    
    Link: https://lkml.kernel.org/r/20211209150803.4473-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 22c033989c3eb9731ad0c497dfab4231b8e367d6
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Wed Jan 19 18:08:12 2022 -0800

    include/linux/unaligned: replace kernel.h with the necessary inclusions
    
    When kernel.h is used in the headers it adds a lot into dependency hell,
    especially when there are circular dependencies are involved.
    
    Replace kernel.h inclusion with the list of what is really being used.
    
    The rest of the changes are induced by the above and may not be split.
    
    Link: https://lkml.kernel.org/r/20211209123823.20425-1-andriy.shevchenko@linux.intel.com
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>       [brcmfmac]
    Acked-by: Kalle Valo <kvalo@kernel.org>
    Cc: Arend van Spriel <aspriel@gmail.com>
    Cc: Franky Lin <franky.lin@broadcom.com>
    Cc: Hante Meuleman <hante.meuleman@broadcom.com>
    Cc: Chi-hsien Lin <chi-hsien.lin@infineon.com>
    Cc: Wright Feng <wright.feng@infineon.com>
    Cc: Chung-hsien Hsu <chung-hsien.hsu@infineon.com>
    Cc: Kalle Valo <kvalo@codeaurora.org>
    Cc: David S. Miller <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7080cead5d45b79ec0c86fa285cf9b6abc413ed8
Author: luo penghao <luo.penghao@zte.com.cn>
Date:   Wed Jan 19 18:08:09 2022 -0800

    sysctl: remove redundant ret assignment
    
    Subsequent if judgments will assign new values to ret, so the statement
    here should be deleted
    
    The clang_analyzer complains as follows:
    
      fs/proc/proc_sysctl.c:
      Value stored to 'ret' is never read
    
    Link: https://lkml.kernel.org/r/20211230063622.586360-1-luo.penghao@zte.com.cn
    Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 153ee1c41a3ec707438ae0ca6b0061f72de334ef
Author: Geert Uytterhoeven <geert+renesas@glider.be>
Date:   Wed Jan 19 18:08:06 2022 -0800

    sysctl: fix duplicate path separator in printed entries
    
    sysctl_print_dir() always terminates the printed path name with a slash,
    so printing a slash before the file part causes a duplicate like in
    
        sysctl duplicate entry: /kernel//perf_user_access
    
    Fix this by dropping the extra slash.
    
    Link: https://lkml.kernel.org/r/e3054d605dc56f83971e4b6d2f5fa63a978720ad.1641551872.git.geert+renesas@glider.be
    Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Acked-by: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 51a18734402874382ccfab288342c72d7227e122
Author: Qi Zheng <zhengqi.arch@bytedance.com>
Date:   Wed Jan 19 18:08:03 2022 -0800

    proc: convert the return type of proc_fd_access_allowed() to be boolean
    
    Convert return type of proc_fd_access_allowed() and the 'allowed' in it
    to be boolean since the return type of ptrace_may_access() is boolean.
    
    Link: https://lkml.kernel.org/r/20211219024404.29779-1-zhengqi.arch@bytedance.com
    Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Alexey Dobriyan <adobriyan@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ae62fbe299629d3b2fa61d4cf5146258c4d99fdf
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Wed Jan 19 18:08:00 2022 -0800

    proc: make the proc_create[_data]() stubs static inlines
    
    Change the proc_create[_data]() stubs which are used when CONFIG_PROC_FS
    is not set from #defines to a static inline stubs.
    
    This should fix clang -Werror builds failing due to errors like this:
    
      drivers/platform/x86/thinkpad_acpi.c:918:30: error: unused variable
       'dispatch_proc_ops' [-Werror,-Wunused-const-variable]
    
    Fixing this in include/linux/proc_fs.h should ensure that the same issue
    is also fixed in any other drivers hitting the same -Werror issue.
    
    [akpm@linux-foundation.org: fix CONFIG_PROC_FS=n]
    [akpm@linux-foundation.org: fix arch/sparc/kernel/led.c]
    [akpm@linux-foundation.org: fix build]
    
    Link: https://lkml.kernel.org/r/20211116131112.508304-1-hdegoede@redhat.com
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Alexander Viro <viro@zeniv.linux.org.uk>
    Cc: Hans de Goede <hdegoede@redhat.com>
    Cc: David Howells <dhowells@redhat.com>
    Cc: Christoph Hellwig <hch@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 25bc5b0de91bc5e7afa65f1face0087fb9e331c7
Author: David Hildenbrand <david@redhat.com>
Date:   Wed Jan 19 18:07:57 2022 -0800

    proc/vmcore: don't fake reading zeroes on surprise vmcore_cb unregistration
    
    In commit cc5f2704c934 ("proc/vmcore: convert oldmem_pfn_is_ram callback
    to more generic vmcore callbacks"), we added detection of surprise
    vmcore_cb unregistration after the vmcore was already opened.  Once
    detected, we warn the user and simulate reading zeroes from that point
    on when accessing the vmcore.
    
    The basic reason was that unexpected unregistration, for example, by
    manually unbinding a driver from a device after opening the vmcore, is
    not supported and could result in reading oldmem the vmcore_cb would
    have actually prohibited while registered.  However, something like that
    can similarly be trigger by a user that's really looking for trouble
    simply by unbinding the relevant driver before opening the vmcore -- or
    by disallowing loading the driver in the first place.  So it's actually
    of limited help.
    
    Currently, unregistration can only be triggered via virtio-mem when
    manually unbinding the driver from the device inside the VM; there is no
    way to trigger it from the hypervisor, as hypervisors don't allow for
    unplugging virtio-mem devices -- ripping out system RAM from a VM
    without coordination with the guest is usually not a good idea.
    
    The important part is that unbinding the driver and unregistering the
    vmcore_cb while concurrently reading the vmcore won't crash the system,
    and that is handled by the rwsem.
    
    To make the mechanism more future proof, let's remove the "read zero"
    part, but leave the warning in place.  For example, we could have a
    future driver (like virtio-balloon) that will contact the hypervisor to
    figure out if we already populated a page for a given PFN.
    Hotunplugging such a device and consequently unregistering the vmcore_cb
    could be triggered from the hypervisor without harming the system even
    while kdump is running.  In that case, we don't want to silently end up
    with a vmcore that contains wrong data, because the user inside the VM
    might be unaware of the hypervisor action and might easily miss the
    warning in the log.
    
    Link: https://lkml.kernel.org/r/20211111192243.22002-1-david@redhat.com
    Signed-off-by: David Hildenbrand <david@redhat.com>
    Acked-by: Baoquan He <bhe@redhat.com>
    Cc: Dave Young <dyoung@redhat.com>
    Cc: Vivek Goyal <vgoyal@redhat.com>
    Cc: Philipp Rudo <prudo@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 20c035764626c56c4f6514936b9ee4be0f4cd962
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date:   Wed Jan 19 18:07:53 2022 -0800

    mm: percpu: add generic pcpu_populate_pte() function
    
    With NEED_PER_CPU_PAGE_FIRST_CHUNK enabled, we need a function to
    populate pte, this patch adds a generic pcpu populate pte function,
    pcpu_populate_pte(), which is marked __weak and used on most
    architectures, but it is overridden on x86, which has its own
    implementation.
    
    Link: https://lkml.kernel.org/r/20211216112359.103822-5-wangkefeng.wang@huawei.com
    Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Dennis Zhou <dennis@kernel.org>
    Cc: Tejun Heo <tj@kernel.org>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Albert Ou <aou@eecs.berkeley.edu>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Paul Walmsley <paul.walmsley@sifive.com>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 23f917169ef157aa7a6bf80d8c4aad6f1282852c
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date:   Wed Jan 19 18:07:49 2022 -0800

    mm: percpu: add generic pcpu_fc_alloc/free funciton
    
    With the previous patch, we could add a generic pcpu first chunk
    allocate and free function to cleanup the duplicated definations on each
    architecture.
    
    Link: https://lkml.kernel.org/r/20211216112359.103822-4-wangkefeng.wang@huawei.com
    Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Dennis Zhou <dennis@kernel.org>
    Cc: Tejun Heo <tj@kernel.org>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Albert Ou <aou@eecs.berkeley.edu>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Paul Walmsley <paul.walmsley@sifive.com>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1ca3fb3abd2b615c4b61728de545760a6e2c2d8b
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date:   Wed Jan 19 18:07:45 2022 -0800

    mm: percpu: add pcpu_fc_cpu_to_node_fn_t typedef
    
    Add pcpu_fc_cpu_to_node_fn_t and pass it into pcpu_fc_alloc_fn_t, pcpu
    first chunk allocation will call it to alloc memblock on the
    corresponding node by it, this is prepare for the next patch.
    
    Link: https://lkml.kernel.org/r/20211216112359.103822-3-wangkefeng.wang@huawei.com
    Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Dennis Zhou <dennis@kernel.org>
    Cc: Tejun Heo <tj@kernel.org>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Albert Ou <aou@eecs.berkeley.edu>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Paul Walmsley <paul.walmsley@sifive.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7ecd19cfdfcbb625cc059dfa5b267d2436732c1c
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date:   Wed Jan 19 18:07:41 2022 -0800

    mm: percpu: generalize percpu related config
    
    Patch series "mm: percpu: Cleanup percpu first chunk function".
    
    When supporting page mapping percpu first chunk allocator on arm64, we
    found there are lots of duplicated codes in percpu embed/page first chunk
    allocator.  This patchset is aimed to cleanup them and should no function
    change.
    
    The currently supported status about 'embed' and 'page' in Archs shows
    below,
    
            embed: NEED_PER_CPU_PAGE_FIRST_CHUNK
            page:  NEED_PER_CPU_EMBED_FIRST_CHUNK
    
                    embed   page
            ------------------------
            arm64     Y      Y
            mips      Y      N
            powerpc   Y      Y
            riscv     Y      N
            sparc     Y      Y
            x86       Y      Y
            ------------------------
    
    There are two interfaces about percpu first chunk allocator,
    
     extern int __init pcpu_embed_first_chunk(size_t reserved_size, size_t dyn_size,
                                    size_t atom_size,
                                    pcpu_fc_cpu_distance_fn_t cpu_distance_fn,
    -                               pcpu_fc_alloc_fn_t alloc_fn,
    -                               pcpu_fc_free_fn_t free_fn);
    +                               pcpu_fc_cpu_to_node_fn_t cpu_to_nd_fn);
    
     extern int __init pcpu_page_first_chunk(size_t reserved_size,
    -                               pcpu_fc_alloc_fn_t alloc_fn,
    -                               pcpu_fc_free_fn_t free_fn,
    -                               pcpu_fc_populate_pte_fn_t populate_pte_fn);
    +                               pcpu_fc_cpu_to_node_fn_t cpu_to_nd_fn);
    
    The pcpu_fc_alloc_fn_t/pcpu_fc_free_fn_t is killed, we provide generic
    pcpu_fc_alloc() and pcpu_fc_free() function, which are called in the
    pcpu_embed/page_first_chunk().
    
    1) For pcpu_embed_first_chunk(), pcpu_fc_cpu_to_node_fn_t is needed to be
       provided when archs supported NUMA.
    
    2) For pcpu_page_first_chunk(), the pcpu_fc_populate_pte_fn_t is killed too,
       a generic pcpu_populate_pte() which marked '__weak' is provided, if you
       need a different function to populate pte on the arch(like x86), please
       provide its own implementation.
    
    [1] https://github.com/kevin78/linux.git percpu-cleanup
    
    This patch (of 4):
    
    The HAVE_SETUP_PER_CPU_AREA/NEED_PER_CPU_EMBED_FIRST_CHUNK/
    NEED_PER_CPU_PAGE_FIRST_CHUNK/USE_PERCPU_NUMA_NODE_ID configs, which have
    duplicate definitions on platforms that subscribe it.
    
    Move them into mm, drop these redundant definitions and instead just
    select it on applicable platforms.
    
    Link: https://lkml.kernel.org/r/20211216112359.103822-1-wangkefeng.wang@huawei.com
    Link: https://lkml.kernel.org/r/20211216112359.103822-2-wangkefeng.wang@huawei.com
    Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>     [arm64]
    Cc: Will Deacon <will@kernel.org>
    Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: Paul Walmsley <paul.walmsley@sifive.com>
    Cc: Palmer Dabbelt <palmer@dabbelt.com>
    Cc: Albert Ou <aou@eecs.berkeley.edu>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Dennis Zhou <dennis@kernel.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Tejun Heo <tj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 51620150ca2df62f8ea472ab8962be590c957288
Author: Steve French <stfrench@microsoft.com>
Date:   Wed Jan 19 22:11:33 2022 -0600

    cifs: update internal module number
    
    To 2.35
    
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 52d005337b2c94ab37273d9ad8382d4fb051defd
Author: Steve French <stfrench@microsoft.com>
Date:   Wed Jan 19 22:00:29 2022 -0600

    smb3: send NTLMSSP version information
    
    For improved debugging it can be helpful to send version information
    as other clients do during NTLMSSP negotiation. See protocol document
    MS-NLMP section 2.2.1.1
    
    Set the major and minor versions based on the kernel version, and the
    BuildNumber based on the internal cifs.ko module version number,
    and following the recommendation in the protocol documentation
    (MS-NLMP section 2.2.10) we set the NTLMRevisionCurrent field to 15.
    
    Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 20aa49541a2ea2cb767ada04cbcaf12fe3ca1275
Author: kernel test robot <lkp@intel.com>
Date:   Wed Jan 19 11:38:36 2022 +0800

    riscv: fix boolconv.cocci warnings
    
    arch/riscv/mm/init.c:48:11-16: WARNING: conversion to bool not needed here
    
     Remove unneeded conversion to bool
    
    Semantic patch information:
     Relational and logical operators evaluate to bool,
     explicit conversion is overly verbose and unneeded.
    
    Generated by: scripts/coccinelle/misc/boolconv.cocci
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 0c34e79e52bb13881c08f1a2c2390b7b88ff10c7
Merge: fc839c6d33c88 c774de22c4307
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Wed Jan 19 19:23:41 2022 -0800

    RISC-V: Introduce sv48 support without relocatable kernel
    
    This patchset allows to have a single kernel for sv39 and sv48 without
    being relocatable.
    
    The idea comes from Arnd Bergmann who suggested to do the same as x86,
    that is mapping the kernel to the end of the address space, which allows
    the kernel to be linked at the same address for both sv39 and sv48 and
    then does not require to be relocated at runtime.
    
    This implements sv48 support at runtime. The kernel will try to boot
    with 4-level page table and will fallback to 3-level if the HW does not
    support it. Folding the 4th level into a 3-level page table has almost
    no cost at runtime.
    
    Note that kasan region had to be moved to the end of the address space
    since its location must be known at compile-time and then be valid for
    both sv39 and sv48 (and sv57 that is coming).
    
    * riscv-sv48-v3:
      riscv: Explicit comment about user virtual address space size
      riscv: Use pgtable_l4_enabled to output mmu_type in cpuinfo
      riscv: Implement sv48 support
      asm-generic: Prepare for riscv use of pud_alloc_one and pud_free
      riscv: Allow to dynamically define VA_BITS
      riscv: Introduce functions to switch pt_ops
      riscv: Split early kasan mapping to prepare sv48 introduction
      riscv: Move KASAN mapping next to the kernel mapping
      riscv: Get rid of MAXPHYSMEM configs
    
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit c774de22c430733487f70d755067d9ea55dbe6de
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:53 2021 +0100

    riscv: Explicit comment about user virtual address space size
    
    Define precisely the size of the user accessible virtual space size
    for sv32/39/48 mmu types and explain why the whole virtual address
    space is split into 2 equal chunks between kernel and user space.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 73c7c8f68e7266bd558227bd9c598cb90b1673cc
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:52 2021 +0100

    riscv: Use pgtable_l4_enabled to output mmu_type in cpuinfo
    
    Now that the mmu type is determined at runtime using SATP
    characteristic, use the global variable pgtable_l4_enabled to output
    mmu type of the processor through /proc/cpuinfo instead of relying on
    device tree infos.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Reviewed-by: Palmer Dabbelt <palmerdabbelt@google.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit e8a62cc26ddf53a3c6ba2a8d33036cf7b84f3923
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:51 2021 +0100

    riscv: Implement sv48 support
    
    By adding a new 4th level of page table, give the possibility to 64bit
    kernel to address 2^48 bytes of virtual address: in practice, that offers
    128TB of virtual address space to userspace and allows up to 64TB of
    physical memory.
    
    If the underlying hardware does not support sv48, we will automatically
    fallback to a standard 3-level page table by folding the new PUD level into
    PGDIR level. In order to detect HW capabilities at runtime, we
    use SATP feature that ignores writes with an unsupported mode.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 60639f74c2f4fcc3ffa2ac0b120eaa874ccc713f
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:50 2021 +0100

    asm-generic: Prepare for riscv use of pud_alloc_one and pud_free
    
    In the following commits, riscv will almost use the generic versions of
    pud_alloc_one and pud_free but an additional check is required since those
    functions are only relevant when using at least a 4-level page table, which
    will be determined at runtime on riscv.
    
    So move the content of those functions into other functions that riscv
    can use without duplicating code.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 3270bfdb9e4a01bb15d018612a6354c1837b5f97
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:48 2021 +0100

    riscv: Allow to dynamically define VA_BITS
    
    With 4-level page table folding at runtime, we don't know at compile time
    the size of the virtual address space so we must set VA_BITS dynamically
    so that sparsemem reserves the right amount of memory for struct pages.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 840125a97abc7e676d839adc2743e8f703a156b3
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:47 2021 +0100

    riscv: Introduce functions to switch pt_ops
    
    This simply gathers the different pt_ops initialization in functions
    where a comment was added to explain why the page table operations must
    be changed along the boot process.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 2efad17e5794f4223bbeff1b2c568e3afd9a8c22
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:46 2021 +0100

    riscv: Split early kasan mapping to prepare sv48 introduction
    
    Now that kasan shadow region is next to the kernel, for sv48, this
    region won't be aligned on PGDIR_SIZE and then when populating this
    region, we'll need to get down to lower levels of the page table. So
    instead of reimplementing the page table walk for the early population,
    take advantage of the existing functions used for the final population.
    
    Note that kasan swapper initialization must also be split since memblock
    is not initialized at this point and as the last PGD is shared with the
    kernel, we'd need to allocate a PUD so postpone the kasan final
    population after the kernel population is done.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit f7ae02333d13f598da6ff6b94cf643255707f752
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Dec 6 11:46:45 2021 +0100

    riscv: Move KASAN mapping next to the kernel mapping
    
    Now that KASAN_SHADOW_OFFSET is defined at compile time as a config,
    this value must remain constant whatever the size of the virtual address
    space, which is only possible by pushing this region at the end of the
    address space next to the kernel mapping.
    
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit db1503d355a79d1d4255a9996f20e72848b74a56
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Mon Jan 17 10:57:16 2022 +0100

    riscv: Get rid of MAXPHYSMEM configs
    
    CONFIG_MAXPHYSMEM_* are actually never used, even the nommu defconfigs
    selecting the MAXPHYSMEM_2GB had no effects on PAGE_OFFSET since it was
    preempted by !MMU case right before.
    
    In addition, the move of the kernel mapping at the end of the address
    space broke the use of MAXPHYSMEM_2G with MMU since it defines PAGE_OFFSET
    at the same address as the kernel mapping.
    
    Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Fixes: 2bfc6cd81bd1 ("riscv: Move kernel mapping outside of linear mapping")
    Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
    Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Tested-by: Conor Dooley <Conor.Dooley@microchip.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 6191cf3ad59fda5901160633fef8e41b064a5246
Author: Brian Foster <bfoster@redhat.com>
Date:   Tue Jan 18 11:32:35 2022 -0800

    xfs: flush inodegc workqueue tasks before cancel
    
    The xfs_inodegc_stop() helper performs a high level flush of pending
    work on the percpu queues and then runs a cancel_work_sync() on each
    of the percpu work tasks to ensure all work has completed before
    returning.  While cancel_work_sync() waits for wq tasks to complete,
    it does not guarantee work tasks have started. This means that the
    _stop() helper can queue and instantly cancel a wq task without
    having completed the associated work. This can be observed by
    tracepoint inspection of a simple "rm -f <file>; fsfreeze -f <mnt>"
    test:
    
            xfs_destroy_inode: ... ino 0x83 ...
            xfs_inode_set_need_inactive: ... ino 0x83 ...
            xfs_inodegc_stop: ...
            ...
            xfs_inodegc_start: ...
            xfs_inodegc_worker: ...
            xfs_inode_inactivating: ... ino 0x83 ...
    
    The first few lines show that the inode is removed and need inactive
    state set, but the inactivation work has not completed before the
    inodegc mechanism stops. The inactivation doesn't actually occur
    until the fs is unfrozen and the gc mechanism starts back up. Note
    that this test requires fsfreeze to reproduce because xfs_freeze
    indirectly invokes xfs_fs_statfs(), which calls xfs_inodegc_flush().
    
    When this occurs, the workqueue try_to_grab_pending() logic first
    tries to steal the pending bit, which does not succeed because the
    bit has been set by queue_work_on(). Subsequently, it checks for
    association of a pool workqueue from the work item under the pool
    lock. This association is set at the point a work item is queued and
    cleared when dequeued for processing. If the association exists, the
    work item is removed from the queue and cancel_work_sync() returns
    true. If the pwq association is cleared, the remove attempt assumes
    the task is busy and retries (eventually returning false to the
    caller after waiting for the work task to complete).
    
    To avoid this race, we can flush each work item explicitly before
    cancel. However, since the _queue_all() already schedules each
    underlying work item, the workqueue level helpers are sufficient to
    achieve the same ordering effect. E.g., the inodegc enabled flag
    prevents scheduling any further work in the _stop() case. Use the
    drain_workqueue() helper in this particular case to make the intent
    a bit more self explanatory.
    
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit 73031f761cb7c2397d73957d14d041c31fe58c34
Author: Jens Axboe <axboe@kernel.dk>
Date:   Wed Jan 19 13:11:58 2022 -0700

    io-wq: delete dead lock shuffling code
    
    We used to have more code around the work loop, but now the goto and
    lock juggling just makes it less readable than it should. Get rid of it.
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit b4966a7dc0725b2baa12b0aeb1489d52568a2aad
Author: Sam Shih <sam.shih@mediatek.com>
Date:   Wed Jan 19 20:36:58 2022 +0800

    clk: mediatek: relicense mt7986 clock driver to GPL-2.0
    
    The previous mt7986 clock drivers were incorrectly marked as GPL-1.0.
    This patch changes the driver to the standard GPL-2.0 license.
    
    Signed-off-by: Sam Shih <sam.shih@mediatek.com>
    Link: https://lore.kernel.org/r/20220119123658.10095-2-sam.shih@mediatek.com
    Reported-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit fc839c6d33c8828514f595822f457e51328507e5
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Tue Jan 11 00:52:08 2022 +0800

    riscv: bpf: Fix eBPF's exception tables
    
    eBPF's exception tables needs to be modified to relative synchronously.
    
    Suggested-by: Tong Tiangen <tongtiangen@huawei.com>
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Fixes: 1f77ed9422cb ("riscv: switch to relative extable and other improvements")
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 96c852c8bf52af2d34654e700d9b5d2e8a99bae5
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Jan 19 13:34:30 2022 -0500

    kvm: selftests: Do not indent with spaces
    
    Some indentation with spaces crept in, likely due to terminal-based
    cut and paste.  Clean it up.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit fa68118144c63e292628945c5b8feb16b84fea7d
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Wed Jan 19 13:30:23 2022 -0500

    kvm: selftests: sync uapi/linux/kvm.h with Linux header
    
    KVM_CAP_XSAVE2 is out of sync due to a conflict.  Copy the whole
    file while at it.
    
    Reported-by: Yang Zhong <yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 805a3ebed59f81155ded218648db58bdc886a881
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Dec 6 23:03:53 2021 +0800

    riscv: mm: init: try best to remove #ifdef CONFIG_XIP_KERNEL usage
    
    Currently, the #ifdef CONFIG_XIP_KERNEL usage can be divided into the
    following three types:
    
    The first one is for functions/declarations only used in XIP case.
    
    The second one is for XIP_FIXUP case. Something as below:
    |foo_type foo;
    |#ifdef CONFIG_XIP_KERNEL
    |#define foo    (*(foo_type *)XIP_FIXUP(&foo))
    |#endif
    
    Usually, it's better to let the foo macro sit with the foo var
    together. But if various foos are defined adjacently, we can
    save some #ifdef CONFIG_XIP_KERNEL usage by grouping them together.
    
    The third one is for different implementations for XIP, usually, this
    is a #ifdef...#else...#endif case.
    
    This patch moves the pt_ops macro to adjacent #ifdef CONFIG_XIP_KERNEL
    and group first type usage cases into one.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit fe036db7d8a93cfbfd254f76e0ecf81aecbbf6b4
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Dec 6 23:03:52 2021 +0800

    riscv: mm: init: try IS_ENABLED(CONFIG_XIP_KERNEL) instead of #ifdef
    
    Try our best to replace the conditional compilation using
    "#ifdef CONFIG_XIP_KERNEL" with "IS_ENABLED(CONFIG_XIP_KERNEL)", to
    simplify the code and to increase compile coverage.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 3274a6ef3b1bd9faef940c40ef201723d5d3d056
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Dec 6 23:03:51 2021 +0800

    riscv: mm: init: remove _pt_ops and use pt_ops directly
    
    Except "pt_ops", other global vars when CONFIG_XIP_KERNEL=y is defined
    as below:
    
    |foo_type foo;
    |#ifdef CONFIG_XIP_KERNEL
    |#define foo    (*(foo_type *)XIP_FIXUP(&foo))
    |#endif
    
    Follow the same way for pt_ops to unify the style and to simplify code.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 07aabe8fb6d1ac3163cc74c856521f2ee746270b
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Dec 6 23:03:50 2021 +0800

    riscv: mm: init: try best to use IS_ENABLED(CONFIG_64BIT) instead of #ifdef
    
    Try our best to replace the conditional compilation using
    "#ifdef CONFIG_64BIT" by a check for "IS_ENABLED(CONFIG_64BIT)", to
    simplify the code and to increase compile coverage.
    
    Now we can also remove the __maybe_unused used in max_mapped_addr
    declaration.
    
    We also remove the BUG_ON check of mapping the last 4K bytes of the
    addressable memory since this is always true for every kernel actually.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 902d6364aad5fc8731ac5b19ed9a1d9c9ee0bd91
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Dec 6 23:03:49 2021 +0800

    riscv: mm: init: remove unnecessary "#ifdef CONFIG_CRASH_DUMP"
    
    The is_kdump_kernel() returns false for !CRASH_DUMP case, so we don't
    need the #ifdef CONFIG_CRASH_DUMP for is_kdump_kernel() checking.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 8326c79d10be2ddbfd3d3804206949a71cb15675
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sat Nov 13 10:43:52 2021 -0300

    tools headers UAPI: Sync x86 arch prctl headers with the kernel sources
    
    To pick the changes in this cset:
    
      980fe2fddcff2193 ("x86/fpu: Extend fpu_xstate_prctl() with guest permissions")
    
    This picks these new prctls:
    
      $ tools/perf/trace/beauty/x86_arch_prctl.sh > /tmp/before
      $ cp arch/x86/include/uapi/asm/prctl.h tools/arch/x86/include/uapi/asm/prctl.h
      $ tools/perf/trace/beauty/x86_arch_prctl.sh > /tmp/after
      $ diff -u /tmp/before /tmp/after
      --- /tmp/before       2022-01-19 14:40:05.049394977 -0300
      +++ /tmp/after        2022-01-19 14:40:35.628154565 -0300
      @@ -9,6 +9,8 @@
            [0x1021 - 0x1001]= "GET_XCOMP_SUPP",
            [0x1022 - 0x1001]= "GET_XCOMP_PERM",
            [0x1023 - 0x1001]= "REQ_XCOMP_PERM",
      +     [0x1024 - 0x1001]= "GET_XCOMP_GUEST_PERM",
      +     [0x1025 - 0x1001]= "REQ_XCOMP_GUEST_PERM",
       };
    
       #define x86_arch_prctl_codes_2_offset 0x2001
      $
    
    With this 'perf trace' can translate those numbers into strings and use
    the strings in filter expressions:
    
      # perf trace -e prctl
           0.000 ( 0.011 ms): DOM Worker/3722622 prctl(option: SET_NAME, arg2: 0x7f9c014b7df5)     = 0
           0.032 ( 0.002 ms): DOM Worker/3722622 prctl(option: SET_NAME, arg2: 0x7f9bb6b51580)     = 0
           5.452 ( 0.003 ms): StreamT~ns #30/3722623 prctl(option: SET_NAME, arg2: 0x7f9bdbdfeb70) = 0
           5.468 ( 0.002 ms): StreamT~ns #30/3722623 prctl(option: SET_NAME, arg2: 0x7f9bdbdfea70) = 0
          24.494 ( 0.009 ms): IndexedDB #556/3722624 prctl(option: SET_NAME, arg2: 0x7f562a32ae28) = 0
          24.540 ( 0.002 ms): IndexedDB #556/3722624 prctl(option: SET_NAME, arg2: 0x7f563c6d4b30) = 0
         670.281 ( 0.008 ms): systemd-userwo/3722339 prctl(option: SET_NAME, arg2: 0x564be30805c8) = 0
         670.293 ( 0.002 ms): systemd-userwo/3722339 prctl(option: SET_NAME, arg2: 0x564be30800f0) = 0
      ^C#
    
    This addresses these perf build warnings:
    
      Warning: Kernel ABI header at 'tools/arch/x86/include/uapi/asm/prctl.h' differs from latest version at 'arch/x86/include/uapi/asm/prctl.h'
      diff -u tools/arch/x86/include/uapi/asm/prctl.h arch/x86/include/uapi/asm/prctl.h
    
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit c080b4144b9dd3b7af838a194ffad3204ca15166
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Jan 18 19:53:52 2022 +0800

    btrfs: defrag: properly update range->start for autodefrag
    
    [BUG]
    After commit 7b508037d4ca ("btrfs: defrag: use defrag_one_cluster() to
    implement btrfs_defrag_file()") autodefrag no longer properly re-defrag
    the file from previously finished location.
    
    [CAUSE]
    The recent refactoring of defrag only focuses on defrag ioctl subpage
    support, doesn't take autodefrag into consideration.
    
    There are two problems involved which prevents autodefrag to restart its
    scan:
    
    - No range.start update
      Previously when one defrag target is found, range->start will be
      updated to indicate where next search should start from.
    
      But now btrfs_defrag_file() doesn't update it anymore, making all
      autodefrag to rescan from file offset 0.
    
      This would also make autodefrag to mark the same range dirty again and
      again, causing extra IO.
    
    - No proper quick exit for defrag_one_cluster()
      Currently if we reached or exceed @max_sectors limit, we just exit
      defrag_one_cluster(), and let next defrag_one_cluster() call to do a
      quick exit.
      This makes @cur increase, thus no way to properly know which range is
      defragged and which range is skipped.
    
    [FIX]
    The fix involves two modifications:
    
    - Update range->start to next cluster start
      This is a little different from the old behavior.
      Previously range->start is updated to the next defrag target.
    
      But in the end, the behavior should still be pretty much the same,
      as now we skip to next defrag target inside btrfs_defrag_file().
    
      Thus if auto-defrag determines to re-scan, then we still do the skip,
      just at a different timing.
    
    - Make defrag_one_cluster() to return >0 to indicate a quick exit
      So that btrfs_defrag_file() can also do a quick exit, without
      increasing @cur to the range end, and re-use @cur to update
      @range->start.
    
    - Add comment for btrfs_defrag_file() to mention the range->start update
      Currently only autodefrag utilize this behavior, as defrag ioctl won't
      set @max_to_defrag parameter, thus unless interrupted it will always
      try to defrag the whole range.
    
    Reported-by: Filipe Manana <fdmanana@suse.com>
    Fixes: 7b508037d4ca ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    Link: https://lore.kernel.org/linux-btrfs/0a269612-e43f-da22-c5bc-b34b1b56ebe8@mailbox.org/
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 484167da77739a8d0e225008c48e697fd3f781ae
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Jan 18 15:19:04 2022 +0800

    btrfs: defrag: fix wrong number of defragged sectors
    
    [BUG]
    There are users using autodefrag mount option reporting obvious increase
    in IO:
    
    > If I compare the write average (in total, I don't have it per process)
    > when taking idle periods on the same machine:
    >     Linux 5.16:
    >         without autodefrag: ~ 10KiB/s
    >         with autodefrag: between 1 and 2MiB/s.
    >
    >     Linux 5.15:
    >         with autodefrag:~ 10KiB/s (around the same as without
    > autodefrag on 5.16)
    
    [CAUSE]
    When autodefrag mount option is enabled, btrfs_defrag_file() will be
    called with @max_sectors = BTRFS_DEFRAG_BATCH (1024) to limit how many
    sectors we can defrag in one try.
    
    And then use the number of sectors defragged to determine if we need to
    re-defrag.
    
    But commit b18c3ab2343d ("btrfs: defrag: introduce helper to defrag one
    cluster") uses wrong unit to increase @sectors_defragged, which should
    be in unit of sector, not byte.
    
    This means, if we have defragged any sector, then @sectors_defragged
    will be >= sectorsize (normally 4096), which is larger than
    BTRFS_DEFRAG_BATCH.
    
    This makes the @max_sectors check in defrag_one_cluster() to underflow,
    rendering the whole @max_sectors check useless.
    
    Thus causing way more IO for autodefrag mount options, as now there is
    no limit on how many sectors can really be defragged.
    
    [FIX]
    Fix the problems by:
    
    - Use sector as unit when increasing @sectors_defragged
    
    - Include @sectors_defragged > @max_sectors case to break the loop
    
    - Add extra comment on the return value of btrfs_defrag_file()
    
    Reported-by: Anthony Ruhier <aruhier@mailbox.org>
    Fixes: b18c3ab2343d ("btrfs: defrag: introduce helper to defrag one cluster")
    Link: https://lore.kernel.org/linux-btrfs/0a269612-e43f-da22-c5bc-b34b1b56ebe8@mailbox.org/
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 70431bfd825d9cd5d93412c0456f253ecad6c415
Author: David Howells <dhowells@redhat.com>
Date:   Tue Nov 17 15:56:59 2020 +0000

    cifs: Support fscache indexing rewrite
    
    Change the cifs filesystem to take account of the changes to fscache's
    indexing rewrite and reenable caching in cifs.
    
    The following changes have been made:
    
     (1) The fscache_netfs struct is no more, and there's no need to register
         the filesystem as a whole.
    
     (2) The session cookie is now an fscache_volume cookie, allocated with
         fscache_acquire_volume().  That takes three parameters: a string
         representing the "volume" in the index, a string naming the cache to
         use (or NULL) and a u64 that conveys coherency metadata for the
         volume.
    
         For cifs, I've made it render the volume name string as:
    
            "cifs,<ipaddress>,<sharename>"
    
         where the sharename has '/' characters replaced with ';'.
    
         This probably needs rethinking a bit as the total name could exceed
         the maximum filename component length.
    
         Further, the coherency data is currently just set to 0.  It needs
         something else doing with it - I wonder if it would suffice simply to
         sum the resource_id, vol_create_time and vol_serial_number or maybe
         hash them.
    
     (3) The fscache_cookie_def is no more and needed information is passed
         directly to fscache_acquire_cookie().  The cache no longer calls back
         into the filesystem, but rather metadata changes are indicated at
         other times.
    
         fscache_acquire_cookie() is passed the same keying and coherency
         information as before.
    
     (4) The functions to set/reset cookies are removed and
         fscache_use_cookie() and fscache_unuse_cookie() are used instead.
    
         fscache_use_cookie() is passed a flag to indicate if the cookie is
         opened for writing.  fscache_unuse_cookie() is passed updates for the
         metadata if we changed it (ie. if the file was opened for writing).
    
         These are called when the file is opened or closed.
    
     (5) cifs_setattr_*() are made to call fscache_resize() to change the size
         of the cache object.
    
     (6) The functions to read and write data are stubbed out pending a
         conversion to use netfslib.
    
    Changes
    =======
    ver #8:
     - Abstract cache invalidation into a helper function.
     - Fix some checkpatch warnings[3].
    
    ver #7:
     - Removed the accidentally added-back call to get the super cookie in
       cifs_root_iget().
     - Fixed the right call to cifs_fscache_get_super_cookie() to take account
       of the "-o fsc" mount flag.
    
    ver #6:
     - Moved the change of gfpflags_allow_blocking() to current_is_kswapd() for
       cifs here.
     - Fixed one of the error paths in cifs_atomic_open() to jump around the
       call to use the cookie.
     - Fixed an additional successful return in the middle of cifs_open() to
       use the cookie on the way out.
     - Only get a volume cookie (and thus inode cookies) when "-o fsc" is
       supplied to mount.
    
    ver #5:
     - Fixed a couple of bits of cookie handling[2]:
       - The cookie should be released in cifs_evict_inode(), not
         cifsFileInfo_put_final().  The cookie needs to persist beyond file
         closure so that writepages will be able to write to it.
       - fscache_use_cookie() needs to be called in cifs_atomic_open() as it is
         for cifs_open().
    
    ver #4:
     - Fixed the use of sizeof with memset.
     - tcon->vol_create_time is __le64 so doesn't need cpu_to_le64().
    
    ver #3:
     - Canonicalise the cifs coherency data to make the cache portable.
     - Set volume coherency data.
    
    ver #2:
     - Use gfpflags_allow_blocking() rather than using flag directly.
     - Upgraded to -rc4 to allow for upstream changes[1].
     - fscache_acquire_volume() now returns errors.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    cc: Steve French <smfrench@gmail.com>
    cc: Shyam Prasad N <nspmangalore@gmail.com>
    cc: linux-cifs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23b55d673d7527b093cd97b7c217c82e70cd1af0 [1]
    Link: https://lore.kernel.org/r/3419813.1641592362@warthog.procyon.org.uk/ [2]
    Link: https://lore.kernel.org/r/CAH2r5muTanw9pJqzAHd01d9A8keeChkzGsCEH6=0rHutVLAF-A@mail.gmail.com/ [3]
    Link: https://lore.kernel.org/r/163819671009.215744.11230627184193298714.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906982979.143852.10672081929614953210.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967187187.1823006.247415138444991444.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021579335.640689.2681324337038770579.stgit@warthog.procyon.org.uk/ # v4
    Link: https://lore.kernel.org/r/3462849.1641593783@warthog.procyon.org.uk/ # v5
    Link: https://lore.kernel.org/r/1318953.1642024578@warthog.procyon.org.uk/ # v6
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit b767c2fc787e992daeadfff40d61c05f66c82da0
Author: Filipe Manana <fdmanana@suse.com>
Date:   Tue Jan 18 13:43:31 2022 +0000

    btrfs: allow defrag to be interruptible
    
    During defrag, at btrfs_defrag_file(), we have this loop that iterates
    over a file range in steps no larger than 256K subranges. If the range
    is too long, there's no way to interrupt it. So make the loop check in
    each iteration if there's signal pending, and if there is, break and
    return -AGAIN to userspace.
    
    Before kernel 5.16, we used to allow defrag to be cancelled through a
    signal, but that was lost with commit 7b508037d4cac3 ("btrfs: defrag:
    use defrag_one_cluster() to implement btrfs_defrag_file()").
    
    This change adds back the possibility to cancel a defrag with a signal
    and keeps the same semantics, returning -EAGAIN to user space (and not
    the usually more expected -EINTR).
    
    This is also motivated by a recent bug on 5.16 where defragging a 1 byte
    file resulted in iterating from file range 0 to (u64)-1, as hitting the
    bug triggered a too long loop, basically requiring one to reboot the
    machine, as it was not possible to cancel defrag.
    
    Fixes: 7b508037d4cac3 ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 6b34cd8e175bfbf4f3f01b6d19eae18245e1a8cc
Author: Filipe Manana <fdmanana@suse.com>
Date:   Mon Jan 17 16:28:29 2022 +0000

    btrfs: fix too long loop when defragging a 1 byte file
    
    When attempting to defrag a file with a single byte, we can end up in a
    too long loop, which is nearly infinite because at btrfs_defrag_file()
    we end up with the variable last_byte assigned with a value of
    18446744073709551615 (which is (u64)-1). The problem comes from the fact
    we end up doing:
    
        last_byte = round_up(last_byte, fs_info->sectorsize) - 1;
    
    So if last_byte was assigned 0, which is i_size - 1, we underflow and
    end up with the value 18446744073709551615.
    
    This is trivial to reproduce and the following script triggers it:
    
      $ cat test.sh
      #!/bin/bash
    
      DEV=/dev/sdj
      MNT=/mnt/sdj
    
      mkfs.btrfs -f $DEV
      mount $DEV $MNT
    
      echo -n "X" > $MNT/foobar
    
      btrfs filesystem defragment $MNT/foobar
    
      umount $MNT
    
    So fix this by not decrementing last_byte by 1 before doing the sector
    size round up. Also, to make it easier to follow, make the round up right
    after computing last_byte.
    
    Reported-by: Anthony Ruhier <aruhier@mailbox.org>
    Fixes: 7b508037d4cac3 ("btrfs: defrag: use defrag_one_cluster() to implement btrfs_defrag_file()")
    Link: https://lore.kernel.org/linux-btrfs/0a269612-e43f-da22-c5bc-b34b1b56ebe8@mailbox.org/
    CC: stable@vger.kernel.org # 5.16
    Reviewed-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d5ad5b1c04c85f01850e88231cad7dfbc9e1d30c
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Tue Jan 18 17:20:52 2022 +0500

    selftests: kvm: add amx_test to .gitignore
    
    amx_test's binary should be present in the .gitignore file for the git
    to ignore it.
    
    Fixes: bf70636d9443 ("selftest: kvm: Add amx selftest")
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Message-Id: <20220118122053.1941915-1-usama.anjum@collabora.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a3c19d5beaad25fcaa703b251c72c3a22fc09100
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:33 2021 +0000

    KVM: SVM: Nullify vcpu_(un)blocking() hooks if AVIC is disabled
    
    Nullify svm_x86_ops.vcpu_(un)blocking if AVIC/APICv is disabled as the
    hooks are necessary only to clear the vCPU's IsRunning entry in the
    Physical APIC and to update IRTE entries if the VM has a pass-through
    device attached.
    
    Opportunistically rename the helpers to clarify their AVIC relationship.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-24-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 54744e17f031cbc5c5b995b1e275df1520c8a739
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:32 2021 +0000

    KVM: SVM: Move svm_hardware_setup() and its helpers below svm_x86_ops
    
    Move svm_hardware_setup() below svm_x86_ops so that KVM can modify ops
    during setup, e.g. the vcpu_(un)blocking hooks can be nullified if AVIC
    is disabled or unsupported.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-23-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 935a7333958e91b5d0c1b0ebc75a5cefdbb34dd5
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:31 2021 +0000

    KVM: SVM: Drop AVIC's intermediate avic_set_running() helper
    
    Drop avic_set_running() in favor of calling avic_vcpu_{load,put}()
    directly, and modify the block+put path to use preempt_disable/enable()
    instead of get/put_cpu(), as it doesn't actually care about the current
    pCPU associated with the vCPU.  Opportunistically add lockdep assertions
    as being preempted in avic_vcpu_put() would lead to consuming stale data,
    even though doing so _in the current code base_ would not be fatal.
    
    Add a much needed comment explaining why svm_vcpu_blocking() needs to
    unload the AVIC and update the IRTE _before_ the vCPU starts blocking.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-22-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 635e6357f948d57bc98af8d37eb81896333822e9
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:30 2021 +0000

    KVM: VMX: Don't do full kick when handling posted interrupt wakeup
    
    When waking vCPUs in the posted interrupt wakeup handling, do exactly
    that and no more.  There is no need to kick the vCPU as the wakeup
    handler just needs to get the vCPU task running, and if it's in the guest
    then it's definitely running.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-21-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ccf8d687542f6a7288b79727bec1cc084b3771b3
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:29 2021 +0000

    KVM: VMX: Fold fallback path into triggering posted IRQ helper
    
    Move the fallback "wake_up" path into the helper to trigger posted
    interrupt helper now that the nested and non-nested paths are identical.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-20-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 296aa26644d088d8ccf0d62b0a93443f7188d5e5
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:28 2021 +0000

    KVM: VMX: Pass desired vector instead of bool for triggering posted IRQ
    
    Refactor the posted interrupt helper to take the desired notification
    vector instead of a bool so that the callers are self-documenting.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-19-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 0f65a9d337676b966316db17374fbef910ab8e4a
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:26 2021 +0000

    KVM: VMX: Don't do full kick when triggering posted interrupt "fails"
    
    Replace the full "kick" with just the "wake" in the fallback path when
    triggering a virtual interrupt via a posted interrupt fails because the
    guest is not IN_GUEST_MODE.  If the guest transitions into guest mode
    between the check and the kick, then it's guaranteed to see the pending
    interrupt as KVM syncs the PIR to IRR (and onto GUEST_RVI) after setting
    IN_GUEST_MODE.  Kicking the guest in this case is nothing more than an
    unnecessary VM-Exit (and host IRQ).
    
    Opportunistically update comments to explain the various ordering rules
    and barriers at play.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-17-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 782f64558de7bef84b90ea812deb38f0e53a8c7a
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:24 2021 +0000

    KVM: SVM: Skip AVIC and IRTE updates when loading blocking vCPU
    
    Don't bother updating the Physical APIC table or IRTE when loading a vCPU
    that is blocking, i.e. won't be marked IsRun{ning}=1, as the pCPU is
    queried if and only if IsRunning is '1'.  If the vCPU was migrated, the
    new pCPU will be picked up when avic_vcpu_load() is called by
    svm_vcpu_unblocking().
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-15-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit af52f5aa5c1b46809834b728a13a1af5aab451e9
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:23 2021 +0000

    KVM: SVM: Use kvm_vcpu_is_blocking() in AVIC load to handle preemption
    
    Use kvm_vcpu_is_blocking() to determine whether or not the vCPU should be
    marked running during avic_vcpu_load().  Drop avic_is_running, which
    really should have been named "vcpu_is_not_blocking", as it tracked if
    the vCPU was blocking, not if it was actually running, e.g. it was set
    during svm_create_vcpu() when the vCPU was obviously not running.
    
    This is technically a teeny tiny functional change, as the vCPU will be
    marked IsRunning=1 on being reloaded if the vCPU is preempted between
    svm_vcpu_blocking() and prepare_to_rcuwait().  But that's a benign change
    as the vCPU will be marked IsRunning=0 when KVM voluntarily schedules out
    the vCPU.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-14-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e422b88969489e67fd1a87a6ef4ef5c30bb53edb
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:22 2021 +0000

    KVM: SVM: Remove unnecessary APICv/AVIC update in vCPU unblocking path
    
    Remove handling of KVM_REQ_APICV_UPDATE from svm_vcpu_unblocking(), it's
    no longer needed as it was made obsolete by commit df7e4827c549 ("KVM:
    SVM: call avic_vcpu_load/avic_vcpu_put when enabling/disabling AVIC").
    Prior to that commit, the manual check was necessary to ensure the AVIC
    stuff was updated by avic_set_running() when a request to enable APICv
    became pending while the vCPU was blocking, as the request handling
    itself would not do the update.  But, as evidenced by the commit, that
    logic was flawed and subject to various races.
    
    Now that svm_refresh_apicv_exec_ctrl() does avic_vcpu_load/put() in
    response to an APICv status change, drop the manual check in the
    unblocking path.
    
    Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-13-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 202470d536b2cad22fa859f3e01202571c49ded9
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:21 2021 +0000

    KVM: SVM: Don't bother checking for "running" AVIC when kicking for IPIs
    
    Drop the avic_vcpu_is_running() check when waking vCPUs in response to a
    VM-Exit due to incomplete IPI delivery.  The check isn't wrong per se, but
    it's not 100% accurate in the sense that it doesn't guarantee that the vCPU
    was one of the vCPUs that didn't receive the IPI.
    
    The check isn't required for correctness as blocking == !running in this
    context.
    
    From a performance perspective, waking a live task is not expensive as the
    only moderately costly operation is a locked operation to temporarily
    disable preemption.  And if that is indeed a performance issue,
    kvm_vcpu_is_blocking() would be a better check than poking into the AVIC.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-12-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 31f251d4ddfa464c6dd92ee873b9b223e992a085
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:20 2021 +0000

    KVM: SVM: Signal AVIC doorbell iff vCPU is in guest mode
    
    Signal the AVIC doorbell iff the vCPU is running in the guest.  If the vCPU
    is not IN_GUEST_MODE, it's guaranteed to pick up any pending IRQs on the
    next VMRUN, which unconditionally processes the vIRR.
    
    Add comments to document the logic.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211208015236.1616697-11-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c3e8abf0f3536a46a235b0533149c2b2c2bbac27
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:19 2021 +0000

    KVM: x86: Remove defunct pre_block/post_block kvm_x86_ops hooks
    
    Drop kvm_x86_ops' pre/post_block() now that all implementations are nops.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-10-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b6d42baddf85310eb2c455cf78af2580773c4ff0
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:18 2021 +0000

    KVM: x86: Unexport LAPIC's switch_to_{hv,sw}_timer() helpers
    
    Unexport switch_to_{hv,sw}_timer() now that common x86 handles the
    transitions.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-9-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 98c25ead5eda5e9d41abe57839ad3e8caf19500c
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:17 2021 +0000

    KVM: VMX: Move preemption timer <=> hrtimer dance to common x86
    
    Handle the switch to/from the hypervisor/software timer when a vCPU is
    blocking in common x86 instead of in VMX.  Even though VMX is the only
    user of a hypervisor timer, the logic and all functions involved are
    generic x86 (unless future CPUs do something completely different and
    implement a hypervisor timer that runs regardless of mode).
    
    Handling the switch in common x86 will allow for the elimination of the
    pre/post_blocks hooks, and also lets KVM switch back to the hypervisor
    timer if and only if it was in use (without additional params).  Add a
    comment explaining why the switch cannot be deferred to kvm_sched_out()
    or kvm_vcpu_block().
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-8-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 12a8eee5686ef3ea7d8db90cd664f11e4a39e349
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:16 2021 +0000

    KVM: Move x86 VMX's posted interrupt list_head to vcpu_vmx
    
    Move the seemingly generic block_vcpu_list from kvm_vcpu to vcpu_vmx, and
    rename the list and all associated variables to clarify that it tracks
    the set of vCPU that need to be poked on a posted interrupt to the wakeup
    vector.  The list is not used to track _all_ vCPUs that are blocking, and
    the term "blocked" can be misleading as it may refer to a blocking
    condition in the host or the guest, where as the PI wakeup case is
    specifically for the vCPUs that are actively blocking from within the
    guest.
    
    No functional change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-7-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e6eec09b7bc7869a49ac0ff376415bad40030ade
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:15 2021 +0000

    KVM: Drop unused kvm_vcpu.pre_pcpu field
    
    Remove kvm_vcpu.pre_pcpu as it no longer has any users.  No functional
    change intended.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-6-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit d76fb40637fc0e84b27bf431cd72cf8fe3f813ef
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Dec 8 01:52:14 2021 +0000

    KVM: VMX: Handle PI descriptor updates during vcpu_put/load
    
    Move the posted interrupt pre/post_block logic into vcpu_put/load
    respectively, using the kvm_vcpu_is_blocking() to determining whether or
    not the wakeup handler needs to be set (and unset).  This avoids updating
    the PI descriptor if halt-polling is successful, reduces the number of
    touchpoints for updating the descriptor, and eliminates the confusing
    behavior of intentionally leaving a "stale" PI.NDST when a blocking vCPU
    is scheduled back in after preemption.
    
    The downside is that KVM will do the PID update twice if the vCPU is
    preempted after prepare_to_rcuwait() but before schedule(), but that's a
    rare case (and non-existent on !PREEMPT kernels).
    
    The notable wart is the need to send a self-IPI on the wakeup vector if
    an outstanding notification is pending after configuring the wakeup
    vector.  Ideally, KVM would just do a kvm_vcpu_wake_up() in this case,
    but the scheduler doesn't support waking a task from its preemption
    notifier callback, i.e. while the task is right in the middle of
    being scheduled out.
    
    Note, setting the wakeup vector before halt-polling is not necessary:
    once the pending IRQ will be recorded in the PIR, kvm_vcpu_has_events()
    will detect this (via kvm_cpu_get_interrupt(), kvm_apic_get_interrupt(),
    apic_has_interrupt_for_ppr() and finally vmx_sync_pir_to_irr()) and
    terminate the polling.
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
    Message-Id: <20211208015236.1616697-5-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4f5a884fc212d99654e4fb36ba98d5354f0dd18e
Merge: e09fccb5435d7 5f02ef741a785
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Tue Jan 18 04:45:32 2022 -0500

    Merge branch 'kvm-pi-raw-spinlock' into HEAD
    
    Bring in fix for VT-d posted interrupts before further changing the code in 5.17.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e09fccb5435d7b9ab3fd5dfeada8ae40cfa56e08
Author: Christian Borntraeger <borntraeger@linux.ibm.com>
Date:   Thu Jan 13 13:29:24 2022 +0100

    KVM: avoid warning on s390 in mark_page_dirty
    
    Avoid warnings on s390 like
    [ 1801.980931] CPU: 12 PID: 117600 Comm: kworker/12:0 Tainted: G            E     5.17.0-20220113.rc0.git0.32ce2abb03cf.300.fc35.s390x+next #1
    [ 1801.980938] Workqueue: events irqfd_inject [kvm]
    [...]
    [ 1801.981057] Call Trace:
    [ 1801.981060]  [<000003ff805f0f5c>] mark_page_dirty_in_slot+0xa4/0xb0 [kvm]
    [ 1801.981083]  [<000003ff8060e9fe>] adapter_indicators_set+0xde/0x268 [kvm]
    [ 1801.981104]  [<000003ff80613c24>] set_adapter_int+0x64/0xd8 [kvm]
    [ 1801.981124]  [<000003ff805fb9aa>] kvm_set_irq+0xc2/0x130 [kvm]
    [ 1801.981144]  [<000003ff805f8d86>] irqfd_inject+0x76/0xa0 [kvm]
    [ 1801.981164]  [<0000000175e56906>] process_one_work+0x1fe/0x470
    [ 1801.981173]  [<0000000175e570a4>] worker_thread+0x64/0x498
    [ 1801.981176]  [<0000000175e5ef2c>] kthread+0x10c/0x110
    [ 1801.981180]  [<0000000175de73c8>] __ret_from_fork+0x40/0x58
    [ 1801.981185]  [<000000017698440a>] ret_from_fork+0xa/0x40
    
    when writing to a guest from an irqfd worker as long as we do not have
    the dirty ring.
    
    Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
    Reluctantly-acked-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20220113122924.740496-1-borntraeger@linux.ibm.com>
    Fixes: 2efd61a608b0 ("KVM: Warn if mark_page_dirty() is called without an active vCPU")
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e337f7e063641ca4d040c8210d4bd790b81effb0
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Dec 28 23:24:37 2021 +0000

    KVM: selftests: Add a test to force emulation with a pending exception
    
    Add a VMX specific test to verify that KVM doesn't explode if userspace
    attempts KVM_RUN when emulation is required with a pending exception.
    KVM VMX's emulation support for !unrestricted_guest punts exceptions to
    userspace instead of attempting to synthesize the exception with all the
    correct state (and stack switching, etc...).
    
    Punting is acceptable as there's never been a request to support
    injecting exceptions when emulating due to invalid state, but KVM has
    historically assumed that userspace will do the right thing and either
    clear the exception or kill the guest.  Deliberately do the opposite and
    attempt to re-enter the guest with a pending exception and emulation
    required to verify KVM continues to punt the combination to userspace,
    e.g. doesn't explode, WARN, etc...
    
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211228232437.1875318-3-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit fc4fad79fc3d8841562e2a85808079da5b4835f6
Author: Sean Christopherson <seanjc@google.com>
Date:   Tue Dec 28 23:24:36 2021 +0000

    KVM: VMX: Reject KVM_RUN if emulation is required with pending exception
    
    Reject KVM_RUN if emulation is required (because VMX is running without
    unrestricted guest) and an exception is pending, as KVM doesn't support
    emulating exceptions except when emulating real mode via vm86.  The vCPU
    is hosed either way, but letting KVM_RUN proceed triggers a WARN due to
    the impossible condition.  Alternatively, the WARN could be removed, but
    then userspace and/or KVM bugs would result in the vCPU silently running
    in a bad state, which isn't very friendly to users.
    
    Originally, the bug was hit by syzkaller with a nested guest as that
    doesn't require kvm_intel.unrestricted_guest=0.  That particular flavor
    is likely fixed by commit cd0e615c49e5 ("KVM: nVMX: Synthesize
    TRIPLE_FAULT for L2 if emulation is required"), but it's trivial to
    trigger the WARN with a non-nested guest, and userspace can likely force
    bad state via ioctls() for a nested guest as well.
    
    Checking for the impossible condition needs to be deferred until KVM_RUN
    because KVM can't force specific ordering between ioctls.  E.g. clearing
    exception.pending in KVM_SET_SREGS doesn't prevent userspace from setting
    it in KVM_SET_VCPU_EVENTS, and disallowing KVM_SET_VCPU_EVENTS with
    emulation_required would prevent userspace from queuing an exception and
    then stuffing sregs.  Note, if KVM were to try and detect/prevent the
    condition prior to KVM_RUN, handle_invalid_guest_state() and/or
    handle_emulation_failure() would need to be modified to clear the pending
    exception prior to exiting to userspace.
    
     ------------[ cut here ]------------
     WARNING: CPU: 6 PID: 137812 at arch/x86/kvm/vmx/vmx.c:1623 vmx_queue_exception+0x14f/0x160 [kvm_intel]
     CPU: 6 PID: 137812 Comm: vmx_invalid_nes Not tainted 5.15.2-7cc36c3e14ae-pop #279
     Hardware name: ASUS Q87M-E/Q87M-E, BIOS 1102 03/03/2014
     RIP: 0010:vmx_queue_exception+0x14f/0x160 [kvm_intel]
     Code: <0f> 0b e9 fd fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
     RSP: 0018:ffffa45c83577d38 EFLAGS: 00010202
     RAX: 0000000000000003 RBX: 0000000080000006 RCX: 0000000000000006
     RDX: 0000000000000000 RSI: 0000000000010002 RDI: ffff9916af734000
     RBP: ffff9916af734000 R08: 0000000000000000 R09: 0000000000000000
     R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000006
     R13: 0000000000000000 R14: ffff9916af734038 R15: 0000000000000000
     FS:  00007f1e1a47c740(0000) GS:ffff99188fb80000(0000) knlGS:0000000000000000
     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
     CR2: 00007f1e1a6a8008 CR3: 000000026f83b005 CR4: 00000000001726e0
     Call Trace:
      kvm_arch_vcpu_ioctl_run+0x13a2/0x1f20 [kvm]
      kvm_vcpu_ioctl+0x279/0x690 [kvm]
      __x64_sys_ioctl+0x83/0xb0
      do_syscall_64+0x3b/0xc0
      entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Reported-by: syzbot+82112403ace4cbd780d8@syzkaller.appspotmail.com
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Message-Id: <20211228232437.1875318-2-seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit bef9a701f3ebfb60da259b04778d24128505a96c
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:31 2022 -0800

    selftests: kvm/x86: Add test for KVM_SET_PMU_EVENT_FILTER
    
    Verify that the PMU event filter works as expected.
    
    Note that the virtual PMU doesn't work as expected on AMD Zen CPUs (an
    intercepted rdmsr is counted as a retired branch instruction), but the
    PMU event filter does work.
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-7-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2ba9047424fc7243c63ac57f5fdfa754aa895e3c
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:30 2022 -0800

    selftests: kvm/x86: Introduce x86_model()
    
    Extract the x86 model number from CPUID.01H:EAX.
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-6-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 398f9240f90f4168f5882180723f743f7b682049
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:29 2022 -0800

    selftests: kvm/x86: Export x86_family() for use outside of processor.c
    
    Move this static inline function to processor.h, so that it can be
    used in individual tests, as needed.
    
    Opportunistically replace the bare 'unsigned' with 'unsigned int.'
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-5-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 21066101f42cfd86fdd835b70ce0e36c335f5f4d
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:28 2022 -0800

    selftests: kvm/x86: Introduce is_amd_cpu()
    
    Replace the one ad hoc "AuthenticAMD" CPUID vendor string comparison
    with a new function, is_amd_cpu().
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-4-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b33b9c407861985713ca18cc9ea05b7540210ad4
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:27 2022 -0800

    selftests: kvm/x86: Parameterize the CPUID vendor string check
    
    Refactor is_intel_cpu() to make it easier to reuse the bulk of the
    code for other vendors in the future.
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-3-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 7ff775aca48adc854436b92c060e5eebfffb6a4a
Author: Jim Mattson <jmattson@google.com>
Date:   Fri Jan 14 21:24:26 2022 -0800

    KVM: x86/pmu: Use binary search to check filtered events
    
    The PMU event filter may contain up to 300 events. Replace the linear
    search in reprogram_gp_counter() with a binary search.
    
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220115052431.447232-2-jmattson@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ba978e83255a759a4a07257a46ca6396a8b81787
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Mon Jan 17 07:15:02 2022 +0000

    cifs: cifs_ses_mark_for_reconnect should also update reconnect bits
    
    Recent restructuring of cifs_reconnect introduced a helper func
    named cifs_ses_mark_for_reconnect, which updates the state of tcp
    session for all the channels of a session for reconnect.
    
    However, this does not update the session state and chans_need_reconnect
    bitmask. This change fixes that.
    
    Also, cifs_mark_tcp_sess_for_reconnect should mark set the bitmask
    for all channels when the whole session is marked for reconnect.
    Fixed that here too.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 47de760655f329ce4b3d3e6276557220956d8c38
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Tue Jan 18 09:24:08 2022 +0000

    cifs: update tcpStatus during negotiate and sess setup
    
    Till the end of SMB session setup, update tcpStatus and
    avoid updating session status field. There was a typo in
    cifs_setup_session, which caused ses->status to be updated
    instead. This was causing issues during reconnect.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit c1604da708d345a1ca1cf6a5537d503b14aa4787
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Sun Jan 16 13:38:14 2022 +0000

    cifs: make status checks in version independent callers
    
    The status of tcp session, smb session and tcon have the
    same flow, irrespective of the SMB version used. Hence
    these status checks and updates should happen in the
    version independent callers of these commands.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit ece0767641740c7eea7aee5a332728e115b00eab
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Sun Jan 16 13:28:34 2022 +0000

    cifs: remove repeated state change in dfs tree connect
    
    cifs_tree_connect checks and sets the tidStatus for the tcon.
    cifs_tree_connect also calls a dfs specific tree connect
    function, which also does similar checks. This should
    not happen. Removing it with this change.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e154cb7b0ab961f9d785ed34c2d7128413e7083d
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Sun Jan 16 11:19:36 2022 +0000

    cifs: fix the cifs_reconnect path for DFS
    
    Recently, the cifs_reconnect code was refactored into
    two branches for regular vs dfs codepath. Some of my
    recent changes were missing in the dfs path, namely the
    code to enable periodic DNS query, and a missing lock.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 8a409cda978e212661b8c032e1b08b3b0b0f9d36
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Wed Jan 5 02:24:37 2022 +0500

    cifs: remove unused variable ses_selected
    
    ses_selected is being declared and set at several places. It is not
    being used. Remove it.
    
    Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 88b024f556fcd5bf1288c6333016f576cfa5f539
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Fri Nov 19 14:16:57 2021 +0000

    cifs: protect all accesses to chan_* with chan_lock
    
    A spin lock called chan_lock was introduced recently.
    But not all accesses were protected. Doing that with
    this change.
    
    To make sure that a channel is not freed when in use,
    we need to introduce a ref count. But today, we don't
    ever free channels.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit a05885ce13bd5ec9602551e32dfb1a4f26bfa542
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Wed Nov 17 15:57:22 2021 +0000

    cifs: fix the connection state transitions with multichannel
    
    Recent changes to multichannel required some adjustments in
    the way connection states transitioned during/after reconnect.
    
    Also some minor fixes:
    1. A pending switch of GlobalMid_Lock to cifs_tcp_ses_lock
    2. Relocations of the code that logs reconnect
    3. Changed some code in allocate_mid to suit the new scheme
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 3663c9045f51a7ad635a0785adef07c21b79b560
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Sat Oct 30 04:51:35 2021 +0000

    cifs: check reconnects for channels of active tcons too
    
    With the new multichannel logic, when a channel needs reconnection,
    the tree connect and other channels can still be active.
    This fix will handle cases of checking for channel reconnect,
    when the tcon does not need reconnect.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 1a1d1dbce6d5477e2bb08ce1ef0d77caa838cc8e
Author: Wei Wang <wei.w.wang@intel.com>
Date:   Mon Jan 17 20:48:17 2022 -0500

    kvm: selftests: conditionally build vm_xsave_req_perm()
    
    vm_xsave_req_perm() is currently defined and used by x86_64 only.
    Make it compiled into vm_create_with_vcpus() only when on x86_64
    machines. Otherwise, it would cause linkage errors, e.g. on s390x.
    
    Fixes: 415a3c33e8 ("kvm: selftests: Add support for KVM_CAP_XSAVE2")
    Reported-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Tested-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Message-Id: <20220118014817.30910-1-wei.w.wang@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e9737468829c2f6abc0c67e5372f8878dff11653
Author: Like Xu <likexu@tencent.com>
Date:   Mon Jan 17 15:45:31 2022 +0800

    KVM: x86/cpuid: Clear XFD for component i if the base feature is missing
    
    According to Intel extended feature disable (XFD) spec, the sub-function i
    (i > 1) of CPUID function 0DH enumerates "details for state component i.
    ECX[2] enumerates support for XFD support for this state component."
    
    If KVM does not report F(XFD) feature (e.g. due to CONFIG_X86_64),
    then the corresponding XFD support for any state component i
    should also be removed. Translate this dependency into KVM terms.
    
    Fixes: 690a757d610e ("kvm: x86: Add CPUID support for Intel AMX")
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20220117074531.76925-1-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6ff94f27fd47847d6ecb9302f9d3bd1ca991a17f
Author: David Matlack <dmatlack@google.com>
Date:   Thu Jan 13 23:30:20 2022 +0000

    KVM: x86/mmu: Improve TLB flush comment in kvm_mmu_slot_remove_write_access()
    
    Rewrite the comment in kvm_mmu_slot_remove_write_access() that explains
    why it is safe to flush TLBs outside of the MMU lock after
    write-protecting SPTEs for dirty logging. The current comment is a long
    run-on sentence that was difficult to understand. In addition it was
    specific to the shadow MMU (mentioning mmu_spte_update()) when the TDP
    MMU has to handle this as well.
    
    The new comment explains:
     - Why the TLB flush is necessary at all.
     - Why it is desirable to do the TLB flush outside of the MMU lock.
     - Why it is safe to do the TLB flush outside of the MMU lock.
    
    No functional change intended.
    
    Signed-off-by: David Matlack <dmatlack@google.com>
    Message-Id: <20220113233020.3986005-5-dmatlack@google.com>
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 5f16bcac6e280a7dade580d9627f5cf93ef6aa56
Author: David Matlack <dmatlack@google.com>
Date:   Thu Jan 13 23:30:19 2022 +0000

    KVM: x86/mmu: Document and enforce MMU-writable and Host-writable invariants
    
    SPTEs are tagged with software-only bits to indicate if it is
    "MMU-writable" and "Host-writable". These bits are used to determine why
    KVM has marked an SPTE as read-only.
    
    Document these bits and their invariants, and enforce the invariants
    with new WARNs in spte_can_locklessly_be_made_writable() to ensure they
    are not accidentally violated in the future.
    
    Opportunistically move DEFAULT_SPTE_{MMU,HOST}_WRITABLE next to
    EPT_SPTE_{MMU,HOST}_WRITABLE since the new documentation applies to
    both.
    
    No functional change intended.
    
    Signed-off-by: David Matlack <dmatlack@google.com>
    Message-Id: <20220113233020.3986005-4-dmatlack@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit f082d86ea68559e4bd1ecaffa04981b72281e28f
Author: David Matlack <dmatlack@google.com>
Date:   Thu Jan 13 23:30:18 2022 +0000

    KVM: x86/mmu: Clear MMU-writable during changed_pte notifier
    
    When handling the changed_pte notifier and the new PTE is read-only,
    clear both the Host-writable and MMU-writable bits in the SPTE. This
    preserves the invariant that MMU-writable is set if-and-only-if
    Host-writable is set.
    
    No functional change intended. Nothing currently relies on the
    aforementioned invariant and technically the changed_pte notifier is
    dead code.
    
    Signed-off-by: David Matlack <dmatlack@google.com>
    Message-Id: <20220113233020.3986005-3-dmatlack@google.com>
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 7c8a4742c4abe205ec9daf416c9d42fd6b406e8e
Author: David Matlack <dmatlack@google.com>
Date:   Thu Jan 13 23:30:17 2022 +0000

    KVM: x86/mmu: Fix write-protection of PTs mapped by the TDP MMU
    
    When the TDP MMU is write-protection GFNs for page table protection (as
    opposed to for dirty logging, or due to the HVA not being writable), it
    checks if the SPTE is already write-protected and if so skips modifying
    the SPTE and the TLB flush.
    
    This behavior is incorrect because it fails to check if the SPTE
    is write-protected for page table protection, i.e. fails to check
    that MMU-writable is '0'.  If the SPTE was write-protected for dirty
    logging but not page table protection, the SPTE could locklessly be made
    writable, and vCPUs could still be running with writable mappings cached
    in their TLB.
    
    Fix this by only skipping setting the SPTE if the SPTE is already
    write-protected *and* MMU-writable is already clear.  Technically,
    checking only MMU-writable would suffice; a SPTE cannot be writable
    without MMU-writable being set.  But check both to be paranoid and
    because it arguably yields more readable code.
    
    Fixes: 46044f72c382 ("kvm: x86/mmu: Support write protection for nesting in tdp MMU")
    Cc: stable@vger.kernel.org
    Signed-off-by: David Matlack <dmatlack@google.com>
    Message-Id: <20220113233020.3986005-2-dmatlack@google.com>
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 9d5f0c36438eeae7566ca383b2b673179e3cc613
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Tue Jan 18 09:02:43 2022 -0300

    perf machine: Use path__join() to compose a path instead of snprintf(dir, '/', filename)
    
    Its more intention revealing, and if we're interested in the odd cases
    where this may end up truncating we can do debug checks at one
    centralized place.
    
    Motivation, of all the container builds, fedora rawhide started
    complaining of:
    
      util/machine.c: In function ‘machine__create_modules’:
      util/machine.c:1419:50: error: ‘%s’ directive output may be truncated writing up to 255 bytes into a region of size between 0 and 4095 [-Werror=format-truncation=]
       1419 |                 snprintf(path, sizeof(path), "%s/%s", dir_name, dent->d_name);
            |                                                  ^~
      In file included from /usr/include/stdio.h:894,
                       from util/branch.h:9,
                       from util/callchain.h:8,
                       from util/machine.c:7:
      In function ‘snprintf’,
          inlined from ‘maps__set_modules_path_dir’ at util/machine.c:1419:3,
          inlined from ‘machine__set_modules_path’ at util/machine.c:1473:9,
          inlined from ‘machine__create_modules’ at util/machine.c:1519:7:
      /usr/include/bits/stdio2.h:71:10: note: ‘__builtin___snprintf_chk’ output between 2 and 4352 bytes into a destination of size 4096
    
    There are other places where we should use path__join(), but lets get rid of
    this one first.
    
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Acked-by: Ian Rogers <irogers@google.com>
    Link: Link: https://lore.kernel.org/r/YebZKjwgfdOz0lAs@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 9df15d842a0f77f2b8ee29386f6d714e4220df57
Author: Alain Volmat <alain.volmat@foss.st.com>
Date:   Wed Jan 19 10:32:45 2022 +0100

    spi: stm32: make SPI_MASTER_MUST_TX flags only specific to STM32F4
    
    Commit 61367d0b8f5e ("spi: stm32: Add 'SPI_SIMPLEX_RX', 'SPI_3WIRE_RX' support for stm32f4")
    allowed to properly communicate with the st-gyro-spi even when
    there is no tx_buf provided by setting the flag SPI_MASTER_MUST_TX and
    thus forcing a dummy TX buffer to work in Full Duplex.
    This behavior should kept only for the STM32F4 and not for other
    compatible since the STM32H7 do support SIMPLEX_RX and SIMPLEX_TX.
    Add the flags variable within the struct stm32_spi_cfg so that flags
    used at master registration time are compatible specific.
    
    Fixes: 61367d0b8f5e ("spi: stm32: Add 'SPI_SIMPLEX_RX', 'SPI_3WIRE_RX' support for stm32f4")
    
    Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
    Link: https://lore.kernel.org/r/20220119093245.624878-3-alain.volmat@foss.st.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3cefddb72f80dc8d49ce605628ceb6525cfd64da
Author: Alain Volmat <alain.volmat@foss.st.com>
Date:   Wed Jan 19 10:32:44 2022 +0100

    spi: stm32: remove inexistant variables in struct stm32_spi_cfg comment
    
    Variables 'can_dma' and 'has_startbit' are described within the
    struct stm32_spi_cfg comment but have never existed in this structure
    so remove them.
    
    Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
    Link: https://lore.kernel.org/r/20220119093245.624878-2-alain.volmat@foss.st.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit e4d63473d3110afd170e6e0e48494d3789d26136
Author: Patrice Chotard <patrice.chotard@foss.st.com>
Date:   Mon Jan 17 13:17:44 2022 +0100

    spi: stm32-qspi: Update spi registering
    
    Some device driver need to communicate to qspi device during the remove
    process, qspi controller must be functional when spi_unregister_master()
    is called.
    
    To ensure this, replace devm_spi_register_master() by spi_register_master()
    and spi_unregister_master() is called directly in .remove callback before
    stopping the qspi controller.
    
    This issue was put in evidence using kernel v5.11 and later
    with a spi-nor which supports the software reset feature introduced
    by commit d73ee7534cc5 ("mtd: spi-nor: core: perform a Soft Reset on
    shutdown")
    
    Fixes: c530cd1d9d5e ("spi: spi-mem: add stm32 qspi controller")
    
    Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
    Cc: <stable@vger.kernel.org> # 5.8.x
    Reviewed-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/20220117121744.29729-1-patrice.chotard@foss.st.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit b4c18c18ebf7cf1e602af88c12ef9cb0d6e5ce51
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Fri Jan 14 19:36:03 2022 -0800

    regulator: MAX20086: add gpio/consumer.h
    
    max20086-regulator.c needs <linux/gpio/consumer.h> for an enum, some
    macros, and a function prototype. (seen on ARCH=m68k)
    
    Adding this header file fixes multiple build errors:
    
    ../drivers/regulator/max20086-regulator.c: In function 'max20086_i2c_probe':
    ../drivers/regulator/max20086-regulator.c:217:26: error: storage size of 'flags' isn't known
      217 |         enum gpiod_flags flags;
    ../drivers/regulator/max20086-regulator.c:261:27: error: 'GPIOD_OUT_HIGH' undeclared (first use in this function); did you mean 'GPIOF_INIT_HIGH'?
      261 |         flags = boot_on ? GPIOD_OUT_HIGH : GPIOD_OUT_LOW;
          |                           ^~~~~~~~~~~~~~
    ../drivers/regulator/max20086-regulator.c:261:44: error: 'GPIOD_OUT_LOW' undeclared (first use in this function); did you mean 'GPIOF_INIT_LOW'?
      261 |         flags = boot_on ? GPIOD_OUT_HIGH : GPIOD_OUT_LOW;
    ../drivers/regulator/max20086-regulator.c:262:27: error: implicit declaration of function 'devm_gpiod_get'; did you mean 'devm_gpio_free'? [-Werror=implicit-function-declaration]
      262 |         chip->ena_gpiod = devm_gpiod_get(chip->dev, "enable", flags);
    ../drivers/regulator/max20086-regulator.c:217:26: warning: unused variable 'flags' [-Wunused-variable]
      217 |         enum gpiod_flags flags;
    
    Fixes: bfff546aae50 ("regulator: Add MAX20086-MAX20089 driver")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Watson Chow <watson.chow@avnet.com>
    Cc: Mark Brown <broonie@kernel.org>
    Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://lore.kernel.org/r/20220115033603.24473-1-rdunlap@infradead.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 579b2c8f72d974f27d85bbd53846f34675ee3b01
Author: Julian Braha <julianbraha@gmail.com>
Date:   Mon Jan 17 00:03:24 2022 -0500

    ASoC: mediatek: fix unmet dependency on GPIOLIB for SND_SOC_DMIC
    
    When SND_SOC_MT8195_MT6359_RT1011_RT5682 is selected,
    and GPIOLIB is not selected,
    Kbuild gives the following warning:
    
    WARNING: unmet direct dependencies detected for SND_SOC_DMIC
      Depends on [n]: SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && GPIOLIB [=n]
      Selected by [y]:
      - SND_SOC_MT8195_MT6359_RT1011_RT5682 [=y] && SOUND [=y] && !UML && SND [=y] && SND_SOC [=y] && I2C [=y] && SND_SOC_MT8195 [=y] && MTK_PMIC_WRAP [=y]
    
    This is because SND_SOC_MT8195_MT6359_RT1011_RT5682
    selects SND_SOC_DMIC without selecting or depending on
    GPIOLIB, depsite SND_SOC_DMIC depending on GPIOLIB.
    
    This unmet dependency bug was detected by Kismet,
    a static analysis tool for Kconfig. Please advise
    if this is not the appropriate solution.
    
    Signed-off-by: Julian Braha <julianbraha@gmail.com>
    Reviewed-by: Tzung-Bi Shih <tzungbi@google.com>
    Link: https://lore.kernel.org/r/20220117050324.68371-1-julianbraha@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4c907bcd9dcd233da6707059d777ab389dcbd964
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Wed Jan 19 15:31:01 2022 +0300

    ASoC: max9759: fix underflow in speaker_gain_control_put()
    
    Check for negative values of "priv->gain" to prevent an out of bounds
    access.  The concern is that these might come from the user via:
      -> snd_ctl_elem_write_user()
        -> snd_ctl_elem_write()
          -> kctl->put()
    
    Fixes: fa8d915172b8 ("ASoC: max9759: Add Amplifier Driver")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220119123101.GA9509@kili
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 8c0ae778e2874f3742bd619000b791d178c187e2
Author: Takashi Iwai <tiwai@suse.de>
Date:   Wed Jan 19 10:10:50 2022 +0100

    ALSA: core: Simplify snd_power_ref_and_wait() with the standard macro
    
    Use wait_event_cmd() macro and simplify snd_power_ref_wait()
    implementation.  This may also cover possible races in the current
    open code, too.
    
    Reviewed-by: Jaroslav Kysela <perex@perex.cz>
    Link: https://lore.kernel.org/r/20220119091050.30125-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit ff9fc0a31d85fcf0011eb4bc4ecaf47d3cc9e21c
Merge: 8eb896a77701b 79eb15da3cd68
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 19 08:14:42 2022 -0800

    Merge branch 'ipv4-avoid-pathological-hash-tables'
    
    Eric Dumazet says:
    
    ====================
    ipv4: avoid pathological hash tables
    
    This series speeds up netns dismantles on hosts
    having many active netns, by making sure two hash tables
    used for IPV4 fib contains uniformly spread items.
    
    v2: changed second patch to add fib_info_laddrhash_bucket()
        for consistency (David Ahern suggestion).
    ====================
    
    Link: https://lore.kernel.org/r/20220119100413.4077866-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 79eb15da3cd68f04b06edf73f9bbafa70a06871f
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 19 02:04:13 2022 -0800

    ipv4: add net_hash_mix() dispersion to fib_info_laddrhash keys
    
    net/ipv4/fib_semantics.c uses a hash table (fib_info_laddrhash)
    in which fib_sync_down_addr() can locate fib_info
    based on IPv4 local address.
    
    This hash table is resized based on total number of
    hashed fib_info, but the hash function is only
    using the local address.
    
    For hosts having many active network namespaces,
    all fib_info for loopback devices (IPv4 address 127.0.0.1)
    are hashed into a single bucket, making netns dismantles
    very slow.
    
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d07418afea8f1d9896aaf9dc5ae47ac4f45b220c
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 19 02:04:12 2022 -0800

    ipv4: avoid quadratic behavior in netns dismantle
    
    net/ipv4/fib_semantics.c uses an hash table of 256 slots,
    keyed by device ifindexes: fib_info_devhash[DEVINDEX_HASHSIZE]
    
    Problem is that with network namespaces, devices tend
    to use the same ifindex.
    
    lo device for instance has a fixed ifindex of one,
    for all network namespaces.
    
    This means that hosts with thousands of netns spend
    a lot of time looking at some hash buckets with thousands
    of elements, notably at netns dismantle.
    
    Simply add a per netns perturbation (net_hash_mix())
    to spread elements more uniformely.
    
    Also change fib_devindex_hashfn() to use more entropy.
    
    Fixes: aa79e66eee5d ("net: Make ifindex generation per-net namespace")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8eb896a77701bef7c80a99833ca776c9ddc317c8
Merge: baa59504c1cd0 3f7c239c7844d
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 19 08:14:25 2022 -0800

    Merge branch 'net-fsl-xgmac_mdio-add-workaround-for-erratum-a-009885'
    
    Tobias Waldekranz says:
    
    ====================
    net/fsl: xgmac_mdio: Add workaround for erratum A-009885
    
    The individual messages mostly speak for themselves.
    
    It is very possible that there are more chips out there that are
    impacted by this, but I only have access to the errata document for
    the T1024 family, so I've limited the DT changes to the exact FMan
    version used in that device. Hopefully someone from NXP can supply a
    follow-up if need be.
    
    The final commit is an unrelated fix that was brought to my attention
    by sparse.
    ====================
    
    Link: https://lore.kernel.org/r/20220118215054.2629314-1-tobias@waldekranz.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3f7c239c7844d2044ed399399d97a5f1c6008e1b
Author: Tobias Waldekranz <tobias@waldekranz.com>
Date:   Tue Jan 18 22:50:53 2022 +0100

    net/fsl: xgmac_mdio: Fix incorrect iounmap when removing module
    
    As reported by sparse: In the remove path, the driver would attempt to
    unmap its own priv pointer - instead of the io memory that it mapped
    in probe.
    
    Fixes: 9f35a7342cff ("net/fsl: introduce Freescale 10G MDIO driver")
    Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0d375d610fa96524e2ee2b46830a46a7bfa92a9f
Author: Tobias Waldekranz <tobias@waldekranz.com>
Date:   Tue Jan 18 22:50:52 2022 +0100

    powerpc/fsl/dts: Enable WA for erratum A-009885 on fman3l MDIO buses
    
    This block is used in (at least) T1024 and T1040, including their
    variants like T1023 etc.
    
    Fixes: d55ad2967d89 ("powerpc/mpc85xx: Create dts components for the FSL QorIQ DPAA FMan")
    Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ea11fc509ff26039046744d1bdfdf2747dda558c
Author: Tobias Waldekranz <tobias@waldekranz.com>
Date:   Tue Jan 18 22:50:51 2022 +0100

    dt-bindings: net: Document fsl,erratum-a009885
    
    Update FMan binding documentation with the newly added workaround for
    erratum A-009885.
    
    Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6198c722019774d38018457a8bfb9ba3ed8c931e
Author: Tobias Waldekranz <tobias@waldekranz.com>
Date:   Tue Jan 18 22:50:50 2022 +0100

    net/fsl: xgmac_mdio: Add workaround for erratum A-009885
    
    Once an MDIO read transaction is initiated, we must read back the data
    register within 16 MDC cycles after the transaction completes. Outside
    of this window, reads may return corrupt data.
    
    Therefore, disable local interrupts in the critical section, to
    maximize the probability that we can satisfy this requirement.
    
    Fixes: d55ad2967d89 ("powerpc/mpc85xx: Create dts components for the FSL QorIQ DPAA FMan")
    Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d9dfab097d90f74dd8d7198aa6e8b87bc15f2122
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:15 2022 -0600

    dt-bindings: rtc: st,stm32-rtc: Make each example a separate entry
    
    Each independent example should be a separate entry. This allows for
    'interrupts' to have different cell sizes.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-7-robh@kernel.org

commit 59449e5dc87e72e9b4a16df115625a93b0112203
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:14 2022 -0600

    dt-bindings: mmc: arm,pl18x: Make each example a separate entry
    
    Each independent example should be a separate entry. This and dropping
    'interrupt-parent' allows for 'interrupts' to have different cell sizes.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-6-robh@kernel.org

commit c476d430bfc02115e67a32a268ebd31b8d683698
Author: Rob Herring <robh@kernel.org>
Date:   Tue Dec 21 08:52:09 2021 -0400

    dt-bindings: display: Add SPI peripheral schema to SPI based displays
    
    With 'unevaluatedProperties' support enabled, several SPI based display
    binding examples have warnings:
    
    Documentation/devicetree/bindings/display/panel/samsung,ld9040.example.dt.yaml: lcd@0: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'spi-max-frequency', 'spi-cpol', 'spi-cpha' were unexpected)
    Documentation/devicetree/bindings/display/panel/kingdisplay,kd035g6-54nt.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('spi-max-frequency', 'spi-3wire' were unexpected)
    Documentation/devicetree/bindings/display/panel/ilitek,ili9322.example.dt.yaml: display@0: Unevaluated properties are not allowed ('reg' was unexpected)
    Documentation/devicetree/bindings/display/panel/samsung,s6e63m0.example.dt.yaml: display@0: Unevaluated properties are not allowed ('spi-max-frequency' was unexpected)
    Documentation/devicetree/bindings/display/panel/abt,y030xx067a.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('spi-max-frequency' was unexpected)
    Documentation/devicetree/bindings/display/panel/sony,acx565akm.example.dt.yaml: panel@2: Unevaluated properties are not allowed ('spi-max-frequency', 'reg' were unexpected)
    Documentation/devicetree/bindings/display/panel/tpo,td.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('spi-max-frequency', 'spi-cpol', 'spi-cpha' were unexpected)
    Documentation/devicetree/bindings/display/panel/lgphilips,lb035q02.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('reg', 'spi-max-frequency', 'spi-cpol', 'spi-cpha' were unexpected)
    Documentation/devicetree/bindings/display/panel/innolux,ej030na.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('spi-max-frequency' was unexpected)
    Documentation/devicetree/bindings/display/panel/sitronix,st7789v.example.dt.yaml: panel@0: Unevaluated properties are not allowed ('spi-max-frequency', 'spi-cpol', 'spi-cpha' were unexpected)
    
    Fix all of these by adding a reference to spi-peripheral-props.yaml.
    With this, the description that the binding must follow
    spi-controller.yaml is both a bit out of date and redundant, so remove
    it.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Acked-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Sam Ravnborg <sam@ravnborg.org>
    Link: https://lore.kernel.org/r/20211221125209.1195932-1-robh@kernel.org

commit d3cbc6e323c9299d10c8d2e4127c77c7d05d07b1
Author: Raymond Jay Golo <rjgolo@gmail.com>
Date:   Thu Jan 13 08:06:20 2022 +0800

    drm: panel-orientation-quirks: Add quirk for the 1Netbook OneXPlayer
    
    The 1Netbook OneXPlayer uses a panel which has been mounted
    90 degrees rotated. Add a quirk for this.
    
    Signed-off-by: Raymond Jay Golo <rjgolo@gmail.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220113000619.90988-1-rjgolo@gmail.com

commit c8e7ff41f819b0c31c66c5196933c26c18f7681f
Author: Jann Horn <jannh@google.com>
Date:   Fri Jan 14 14:33:31 2022 +0100

    HID: uhid: Use READ_ONCE()/WRITE_ONCE() for ->running
    
    The flag uhid->running can be set to false by uhid_device_add_worker()
    without holding the uhid->devlock. Mark all reads/writes of the flag
    that might race with READ_ONCE()/WRITE_ONCE() for clarity and
    correctness.
    
    Signed-off-by: Jann Horn <jannh@google.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 4ea5763fb79ed89b3bdad455ebf3f33416a81624
Author: Jann Horn <jannh@google.com>
Date:   Fri Jan 14 14:33:30 2022 +0100

    HID: uhid: Fix worker destroying device without any protection
    
    uhid has to run hid_add_device() from workqueue context while allowing
    parallel use of the userspace API (which is protected with ->devlock).
    But hid_add_device() can fail. Currently, that is handled by immediately
    destroying the associated HID device, without using ->devlock - but if
    there are concurrent requests from userspace, that's wrong and leads to
    NULL dereferences and/or memory corruption (via use-after-free).
    
    Fix it by leaving the HID device as-is in the worker. We can clean it up
    later, either in the UHID_DESTROY command handler or in the ->release()
    handler.
    
    Cc: stable@vger.kernel.org
    Fixes: 67f8ecc550b5 ("HID: uhid: fix timeout when probe races with IO")
    Signed-off-by: Jann Horn <jannh@google.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit baa59504c1cd0cca7d41954a45ee0b3dc78e41a0
Author: Tom Rix <trix@redhat.com>
Date:   Tue Jan 18 05:41:10 2022 -0800

    net: mscc: ocelot: fix using match before it is set
    
    Clang static analysis reports this issue
    ocelot_flower.c:563:8: warning: 1st function call argument
      is an uninitialized value
        !is_zero_ether_addr(match.mask->dst)) {
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    The variable match is used before it is set.  So move the
    block.
    
    Fixes: 75944fda1dfe ("net: mscc: ocelot: offload ingress skbedit and vlan actions to VCAP IS1")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f1131b9c23fb4a3540a774828ff49f421619f902
Author: Claudiu Beznea <claudiu.beznea@microchip.com>
Date:   Tue Jan 18 13:08:12 2022 +0200

    net: phy: micrel: use kszphy_suspend()/kszphy_resume for irq aware devices
    
    On a setup with KSZ9131 and MACB drivers it happens on suspend path, from
    time to time, that the PHY interrupt arrives after PHY and MACB were
    suspended (PHY via genphy_suspend(), MACB via macb_suspend()). In this
    case the phy_read() at the beginning of kszphy_handle_interrupt() will
    fail (as MACB driver is suspended at this time) leading to phy_error()
    being called and a stack trace being displayed on console. To solve this
    .suspend/.resume functions for all KSZ devices implementing
    .handle_interrupt were replaced with kszphy_suspend()/kszphy_resume()
    which disable/enable interrupt before/after calling
    genphy_suspend()/genphy_resume().
    
    The fix has been adapted for all KSZ devices which implements
    .handle_interrupt but it has been tested only on KSZ9131.
    
    Fixes: 59ca4e58b917 ("net: phy: micrel: implement generic .handle_interrupt() callback")
    Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1771afd47430f5e95c9c3a2e3a8a63e67402d3fe
Author: Ard Biesheuvel <ardb@kernel.org>
Date:   Tue Jan 18 11:22:04 2022 +0100

    net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
    
    Both versions of the CPSW driver declare a CPSW_HEADROOM_NA macro that
    takes NET_IP_ALIGN into account, but fail to use it appropriately when
    storing incoming packets in memory. This results in the IPv4 source and
    destination addresses to appear misaligned in memory, which causes
    aligment faults that need to be fixed up in software.
    
    So let's switch from CPSW_HEADROOM to CPSW_HEADROOM_NA where needed.
    This gets rid of any alignment faults on the RX path on a Beaglebone
    White.
    
    Fixes: 9ed4050c0d75 ("net: ethernet: ti: cpsw: add XDP support")
    Cc: Grygorii Strashko <grygorii.strashko@ti.com>
    Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit dded08927ca3c31a5c37f8e7f95fe98770475dd4
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Wed Jan 19 08:48:16 2022 +0100

    nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
    
    Syzbot detected a NULL pointer dereference of nfc_llcp_sock->dev pointer
    (which is a 'struct nfc_dev *') with calls to llcp_sock_sendmsg() after
    a failed llcp_sock_bind(). The message being sent is a SOCK_DGRAM.
    
    KASAN report:
    
      BUG: KASAN: null-ptr-deref in nfc_alloc_send_skb+0x2d/0xc0
      Read of size 4 at addr 00000000000005c8 by task llcp_sock_nfc_a/899
    
      CPU: 5 PID: 899 Comm: llcp_sock_nfc_a Not tainted 5.16.0-rc6-next-20211224-00001-gc6437fbf18b0 #125
      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
      Call Trace:
       <TASK>
       dump_stack_lvl+0x45/0x59
       ? nfc_alloc_send_skb+0x2d/0xc0
       __kasan_report.cold+0x117/0x11c
       ? mark_lock+0x480/0x4f0
       ? nfc_alloc_send_skb+0x2d/0xc0
       kasan_report+0x38/0x50
       nfc_alloc_send_skb+0x2d/0xc0
       nfc_llcp_send_ui_frame+0x18c/0x2a0
       ? nfc_llcp_send_i_frame+0x230/0x230
       ? __local_bh_enable_ip+0x86/0xe0
       ? llcp_sock_connect+0x470/0x470
       ? llcp_sock_connect+0x470/0x470
       sock_sendmsg+0x8e/0xa0
       ____sys_sendmsg+0x253/0x3f0
       ...
    
    The issue was visible only with multiple simultaneous calls to bind() and
    sendmsg(), which resulted in most of the bind() calls to fail.  The
    bind() was failing on checking if there is available WKS/SDP/SAP
    (respective bit in 'struct nfc_llcp_local' fields).  When there was no
    available WKS/SDP/SAP, the bind returned error but the sendmsg() to such
    socket was able to trigger mentioned NULL pointer dereference of
    nfc_llcp_sock->dev.
    
    The code looks simply racy and currently it protects several paths
    against race with checks for (!nfc_llcp_sock->local) which is NULL-ified
    in error paths of bind().  The llcp_sock_sendmsg() did not have such
    check but called function nfc_llcp_send_ui_frame() had, although not
    protected with lock_sock().
    
    Therefore the race could look like (same socket is used all the time):
      CPU0                                     CPU1
      ====                                     ====
      llcp_sock_bind()
      - lock_sock()
        - success
      - release_sock()
      - return 0
                                               llcp_sock_sendmsg()
                                               - lock_sock()
                                               - release_sock()
      llcp_sock_bind(), same socket
      - lock_sock()
        - error
                                               - nfc_llcp_send_ui_frame()
                                                 - if (!llcp_sock->local)
        - llcp_sock->local = NULL
        - nfc_put_device(dev)
                                                 - dereference llcp_sock->dev
      - release_sock()
      - return -ERRNO
    
    The nfc_llcp_send_ui_frame() checked llcp_sock->local outside of the
    lock, which is racy and ineffective check.  Instead, its caller
    llcp_sock_sendmsg(), should perform the check inside lock_sock().
    
    Reported-and-tested-by: syzbot+7f23bcddf626e0593a39@syzkaller.appspotmail.com
    Fixes: b874dec21d1c ("NFC: Implement LLCP connection less Tx path")
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8c8963b27e685ec5d45696e51f95947a8c413727
Merge: 99845220d3c3b 2d19c3fd80178
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Jan 19 11:29:15 2022 +0000

    Merge branch 'axienet-fixes'
    
    Robert Hancock says:
    
    ====================
    Xilinx axienet fixes
    
    Various fixes for the Xilinx AXI Ethernet driver.
    
    Changed since v2:
    -added Reviewed-by tags, added some explanation to commit
    messages, no code changes
    
    Changed since v1:
    -corrected a Fixes tag to point to mainline commit
    -split up reset changes into 3 patches
    -added ratelimit on netdev_warn in TX busy case
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2d19c3fd80178160dd505ccd7fed1643831227a5
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:32 2022 -0600

    net: axienet: increase default TX ring size to 128
    
    With previous changes to make the driver handle the TX ring size more
    correctly, the default TX ring size of 64 appears to significantly
    bottleneck TX performance to around 600 Mbps on a 1 Gbps link on ZynqMP.
    Increasing this to 128 seems to bring performance up to near line rate and
    shouldn't cause excess bufferbloat (this driver doesn't yet support modern
    byte-based queue management).
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit bb193e3db8b86a63f26889c99e14fd30c9ebd72a
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:31 2022 -0600

    net: axienet: fix for TX busy handling
    
    Network driver documentation indicates we should be avoiding returning
    NETDEV_TX_BUSY from ndo_start_xmit in normal cases, since it requires
    the packets to be requeued. Instead the queue should be stopped after
    a packet is added to the TX ring when there may not be enough room for an
    additional one. Also, when TX ring entries are completed, we should only
    wake the queue if we know there is room for another full maximally
    fragmented packet.
    
    Print a warning if there is insufficient space at the start of start_xmit,
    since this should no longer happen.
    
    Combined with increasing the default TX ring size (in a subsequent
    patch), this appears to recover the TX performance lost by previous changes
    to actually manage the TX ring state properly.
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit aba57a823d2985a2cc8c74a2535f3a88e68d9424
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:30 2022 -0600

    net: axienet: fix number of TX ring slots for available check
    
    The check for the number of available TX ring slots was off by 1 since a
    slot is required for the skb header as well as each fragment. This could
    result in overwriting a TX ring slot that was still in use.
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 996defd7f8b5dafc1d480b7585c7c62437f80c3c
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:29 2022 -0600

    net: axienet: Fix TX ring slot available check
    
    The check for whether a TX ring slot was available was incorrect,
    since a slot which had been loaded with transmit data but the device had
    not started transmitting would be treated as available, potentially
    causing non-transmitted slots to be overwritten. The control field in
    the descriptor should be checked, rather than the status field (which may
    only be updated when the device completes the entry).
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 70f5817deddbc6ef3faa35841cab83c280cc653a
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:28 2022 -0600

    net: axienet: limit minimum TX ring size
    
    The driver will not work properly if the TX ring size is set to below
    MAX_SKB_FRAGS + 1 since it needs to hold at least one full maximally
    fragmented packet in the TX ring. Limit setting the ring size to below
    this value.
    
    Fixes: 8b09ca823ffb4 ("net: axienet: Make RX/TX ring sizes configurable")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 95978df6fa328df619c15312e65ece469c2be2d2
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:27 2022 -0600

    net: axienet: add missing memory barriers
    
    This driver was missing some required memory barriers:
    
    Use dma_rmb to ensure we see all updates to the descriptor after we see
    that an entry has been completed.
    
    Use wmb and rmb to avoid stale descriptor status between the TX path and
    TX complete IRQ path.
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 04cc2da39698efd7eb2e30c112538922d26f848e
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:26 2022 -0600

    net: axienet: reset core on initialization prior to MDIO access
    
    In some cases where the Xilinx Ethernet core was used in 1000Base-X or
    SGMII modes, which use the internal PCS/PMA PHY, and the MGT
    transceiver clock source for the PCS was not running at the time the
    FPGA logic was loaded, the core would come up in a state where the
    PCS could not be found on the MDIO bus. To fix this, the Ethernet core
    (including the PCS) should be reset after enabling the clocks, prior to
    attempting to access the PCS using of_mdio_find_device.
    
    Fixes: 1a02556086fc (net: axienet: Properly handle PCS/PMA PHY for 1000BaseX mode)
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b400c2f4f4c53c86594dd57098970d97d488bfde
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:25 2022 -0600

    net: axienet: Wait for PhyRstCmplt after core reset
    
    When resetting the device, wait for the PhyRstCmplt bit to be set
    in the interrupt status register before continuing initialization, to
    ensure that the core is actually ready. When using an external PHY, this
    also ensures we do not start trying to access the PHY while it is still
    in reset. The PHY reset is initiated by the core reset which is
    triggered just above, but remains asserted for 5ms after the core is
    reset according to the documentation.
    
    The MgtRdy bit could also be waited for, but unfortunately when using
    7-series devices, the bit does not appear to work as documented (it
    seems to behave as some sort of link state indication and not just an
    indication the transceiver is ready) so it can't really be relied on for
    this purpose.
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2e5644b1bab2ccea9cfc7a9520af95b94eb0dbf1
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Tue Jan 18 15:41:24 2022 -0600

    net: axienet: increase reset timeout
    
    The previous timeout of 1ms was too short to handle some cases where the
    core is reset just after the input clocks were started, which will
    be introduced in an upcoming patch. Increase the timeout to 50ms. Also
    simplify the reset timeout checking to use read_poll_timeout.
    
    Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9f80ccda53b9417236945bc7ece4b519037df74d
Author: Ard Biesheuvel <ardb@kernel.org>
Date:   Tue Jan 18 19:32:17 2022 +0100

    ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
    
    When building for Thumb2, the .alt.smp.init sections that are emitted by
    the ALT_UP() patching code may not be 32-bit aligned, even though the
    fixup_smp_on_up() routine expects that. This results in alignment faults
    at module load time, which need to be fixed up by the fault handler.
    
    So let's align those sections explicitly, and prevent this from occurring.
    
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 15420269b02a63ed8c1841905d8b8b2403246004
Author: Ard Biesheuvel <ardb@kernel.org>
Date:   Tue Jan 18 13:45:09 2022 +0100

    ARM: 9179/1: uaccess: avoid alignment faults in copy_[from|to]_kernel_nofault
    
    The helpers that are used to implement copy_from_kernel_nofault() and
    copy_to_kernel_nofault() cast a void* to a pointer to a wider type,
    which may result in alignment faults on ARM if the compiler decides to
    use double-word or multiple-word load/store instructions.
    
    Only configurations that define CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
    are affected, given that commit 2423de2e6f4d ("ARM: 9115/1: mm/maccess:
    fix unaligned copy_{from,to}_kernel_nofault") ensures that dst and src
    are sufficiently aligned otherwise.
    
    So use the unaligned accessors for accessing dst and src in cases where
    they may be misaligned.
    
    Cc: <stable@vger.kernel.org> # depends on 2423de2e6f4d
    Fixes: 2df4c9a741a0 ("ARM: 9112/1: uaccess: add __{get,put}_kernel_nofault")
    Reviewed-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 8b59b0a53c840921b625378f137e88adfa87647e
Author: sparkhuang <huangshaobo6@huawei.com>
Date:   Wed Dec 15 10:08:23 2021 +0100

    ARM: 9170/1: fix panic when kasan and kprobe are enabled
    
    arm32 uses software to simulate the instruction replaced
    by kprobe. some instructions may be simulated by constructing
    assembly functions. therefore, before executing instruction
    simulation, it is necessary to construct assembly function
    execution environment in C language through binding registers.
    after kasan is enabled, the register binding relationship will
    be destroyed, resulting in instruction simulation errors and
    causing kernel panic.
    
    the kprobe emulate instruction function is distributed in three
    files: actions-common.c actions-arm.c actions-thumb.c, so disable
    KASAN when compiling these files.
    
    for example, use kprobe insert on cap_capable+20 after kasan
    enabled, the cap_capable assembly code is as follows:
    <cap_capable>:
    e92d47f0        push    {r4, r5, r6, r7, r8, r9, sl, lr}
    e1a05000        mov     r5, r0
    e280006c        add     r0, r0, #108    ; 0x6c
    e1a04001        mov     r4, r1
    e1a06002        mov     r6, r2
    e59fa090        ldr     sl, [pc, #144]  ;
    ebfc7bf8        bl      c03aa4b4 <__asan_load4>
    e595706c        ldr     r7, [r5, #108]  ; 0x6c
    e2859014        add     r9, r5, #20
    ......
    The emulate_ldr assembly code after enabling kasan is as follows:
    c06f1384 <emulate_ldr>:
    e92d47f0        push    {r4, r5, r6, r7, r8, r9, sl, lr}
    e282803c        add     r8, r2, #60     ; 0x3c
    e1a05000        mov     r5, r0
    e7e37855        ubfx    r7, r5, #16, #4
    e1a00008        mov     r0, r8
    e1a09001        mov     r9, r1
    e1a04002        mov     r4, r2
    ebf35462        bl      c03c6530 <__asan_load4>
    e357000f        cmp     r7, #15
    e7e36655        ubfx    r6, r5, #12, #4
    e205a00f        and     sl, r5, #15
    0a000001        beq     c06f13bc <emulate_ldr+0x38>
    e0840107        add     r0, r4, r7, lsl #2
    ebf3545c        bl      c03c6530 <__asan_load4>
    e084010a        add     r0, r4, sl, lsl #2
    ebf3545a        bl      c03c6530 <__asan_load4>
    e2890010        add     r0, r9, #16
    ebf35458        bl      c03c6530 <__asan_load4>
    e5990010        ldr     r0, [r9, #16]
    e12fff30        blx     r0
    e356000f        cm      r6, #15
    1a000014        bne     c06f1430 <emulate_ldr+0xac>
    e1a06000        mov     r6, r0
    e2840040        add     r0, r4, #64     ; 0x40
    ......
    
    when running in emulate_ldr to simulate the ldr instruction, panic
    occurred, and the log is as follows:
    Unable to handle kernel NULL pointer dereference at virtual address
    00000090
    pgd = ecb46400
    [00000090] *pgd=2e0fa003, *pmd=00000000
    Internal error: Oops: 206 [#1] SMP ARM
    PC is at cap_capable+0x14/0xb0
    LR is at emulate_ldr+0x50/0xc0
    psr: 600d0293 sp : ecd63af8  ip : 00000004  fp : c0a7c30c
    r10: 00000000  r9 : c30897f4  r8 : ecd63cd4
    r7 : 0000000f  r6 : 0000000a  r5 : e59fa090  r4 : ecd63c98
    r3 : c06ae294  r2 : 00000000  r1 : b7611300  r0 : bf4ec008
    Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
    Control: 32c5387d  Table: 2d546400  DAC: 55555555
    Process bash (pid: 1643, stack limit = 0xecd60190)
    (cap_capable) from (kprobe_handler+0x218/0x340)
    (kprobe_handler) from (kprobe_trap_handler+0x24/0x48)
    (kprobe_trap_handler) from (do_undefinstr+0x13c/0x364)
    (do_undefinstr) from (__und_svc_finish+0x0/0x30)
    (__und_svc_finish) from (cap_capable+0x18/0xb0)
    (cap_capable) from (cap_vm_enough_memory+0x38/0x48)
    (cap_vm_enough_memory) from
    (security_vm_enough_memory_mm+0x48/0x6c)
    (security_vm_enough_memory_mm) from
    (copy_process.constprop.5+0x16b4/0x25c8)
    (copy_process.constprop.5) from (_do_fork+0xe8/0x55c)
    (_do_fork) from (SyS_clone+0x1c/0x24)
    (SyS_clone) from (__sys_trace_return+0x0/0x10)
    Code: 0050a0e1 6c0080e2 0140a0e1 0260a0e1 (f801f0e7)
    
    Fixes: 35aa1df43283 ("ARM kprobes: instruction single-stepping support")
    Fixes: 421015713b30 ("ARM: 9017/2: Enable KASan for ARM")
    Signed-off-by: huangshaobo <huangshaobo6@huawei.com>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>

commit 1d1df41c5a33359a00e919d54eaebfb789711fdc
Merge: e9f5cbc0c851c 5fed0be8583f0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 11:50:20 2022 +0200

    Merge tag 'f2fs-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs
    
    Pull f2fs updates from Jaegeuk Kim:
     "In this round, we've tried to address some performance issues in
      f2fs_checkpoint and direct IO flows. Also, there was a work to enhance
      the page cache management used for compression. Other than them, we've
      done typical work including sysfs, code clean-ups, tracepoint, sanity
      check, in addition to bug fixes on corner cases.
    
      Enhancements:
       - use iomap for direct IO
       - try to avoid lock contention to improve f2fs_ckpt speed
       - avoid unnecessary memory allocation in compression flow
       - POSIX_FADV_DONTNEED drops the page cache containing compression
         pages
       - add some sysfs entries (gc_urgent_high_remaining, pending_discard)
    
      Bug fixes:
       - try not to expose unwritten blocks to user by DIO (this was added
         to avoid merge conflict; another patch is coming to address other
         missing case)
       - relax minor error condition for file pinning feature used in
         Android OTA
       - fix potential deadlock case in compression flow
       - should not truncate any block on pinned file
    
      In addition, we've done some code clean-ups and tracepoint/sanity
      check improvement"
    
    * tag 'f2fs-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs: (29 commits)
      f2fs: do not allow partial truncation on pinned file
      f2fs: remove redunant invalidate compress pages
      f2fs: Simplify bool conversion
      f2fs: don't drop compressed page cache in .{invalidate,release}page
      f2fs: fix to reserve space for IO align feature
      f2fs: fix to check available space of CP area correctly in update_ckpt_flags()
      f2fs: support fault injection to f2fs_trylock_op()
      f2fs: clean up __find_inline_xattr() with __find_xattr()
      f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
      f2fs: do not bother checkpoint by f2fs_get_node_info
      f2fs: avoid down_write on nat_tree_lock during checkpoint
      f2fs: compress: fix potential deadlock of compress file
      f2fs: avoid EINVAL by SBI_NEED_FSCK when pinning a file
      f2fs: add gc_urgent_high_remaining sysfs node
      f2fs: fix to do sanity check in is_alive()
      f2fs: fix to avoid panic in is_alive() if metadata is inconsistent
      f2fs: fix to do sanity check on inode type during garbage collection
      f2fs: avoid duplicate call of mark_inode_dirty
      f2fs: show number of pending discard commands
      f2fs: support POSIX_FADV_DONTNEED drop compressed page cache
      ...

commit e9f5cbc0c851c1cf98e4ecc5d72b5563d3fc5605
Merge: f1b744f65e2f9 35140d399db2b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 11:44:34 2022 +0200

    Merge tag 'trace-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing fix from Steven Rostedt:
     "tracing/scripts: Possible uninitialized variable
    
      The 0day bot discovered a possible uninitialized path in the scripts
      that sort the mcount sections at build time. Just needed to initialize
      that variable"
    
    * tag 'trace-v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
      script/sorttable: Fix some initialization problems

commit f1b744f65e2f9682347c5faf6377e61e2ab19a67
Merge: fd6f57bfda7c3 b579dfe71a6a5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 11:38:21 2022 +0200

    Merge tag 'riscv-for-linus-5.17-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux
    
    Pull RISC-V updates from Palmer Dabbelt:
    
     - Support for the DA9063 as used on the HiFive Unmatched.
    
     - Support for relative extables, which puts us in line with other
       architectures and save some space in vmlinux.
    
     - A handful of kexec fixes/improvements, including the ability to run
       crash kernels from PCI-addressable memory on the HiFive Unmatched.
    
     - Support for the SBI SRST extension, which allows systems that do not
       have an explicit driver in Linux to reboot.
    
     - A handful of fixes and cleanups, including to the defconfigs and
       device trees.
    
    * tag 'riscv-for-linus-5.17-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux: (52 commits)
      RISC-V: Use SBI SRST extension when available
      riscv: mm: fix wrong phys_ram_base value for RV64
      RISC-V: Use common riscv_cpuid_to_hartid_mask() for both SMP=y and SMP=n
      riscv: head: remove useless __PAGE_ALIGNED_BSS and .balign
      riscv: errata: alternative: mark vendor_patch_func __initdata
      riscv: head: make secondary_start_common() static
      riscv: remove cpu_stop()
      riscv: try to allocate crashkern region from 32bit addressible memory
      riscv: use hart id instead of cpu id on machine_kexec
      riscv: Don't use va_pa_offset on kdump
      riscv: dts: sifive: fu540-c000: Fix PLIC node
      riscv: dts: sifive: fu540-c000: Drop bogus soc node compatible values
      riscv: dts: sifive: Group tuples in register properties
      riscv: dts: sifive: Group tuples in interrupt properties
      riscv: dts: microchip: mpfs: Group tuples in interrupt properties
      riscv: dts: microchip: mpfs: Fix clock controller node
      riscv: dts: microchip: mpfs: Fix reference clock node
      riscv: dts: microchip: mpfs: Fix PLIC node
      riscv: dts: microchip: mpfs: Drop empty chosen node
      riscv: dts: canaan: Group tuples in interrupt properties
      ...

commit fd6f57bfda7c36f2d465cee39d5d8c623db5d7aa
Merge: 0ed905975612e c4d7f40b250c1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 11:15:19 2022 +0200

    Merge tag 'kbuild-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild
    
    Pull Kbuild updates from Masahiro Yamada:
    
     - Add new kconfig target 'make mod2noconfig', which will be useful to
       speed up the build and test iteration.
    
     - Raise the minimum supported version of LLVM to 11.0.0
    
     - Refactor certs/Makefile
    
     - Change the format of include/config/auto.conf to stop double-quoting
       string type CONFIG options.
    
     - Fix ARCH=sh builds in dash
    
     - Separate compression macros for general purposes (cmd_bzip2 etc.) and
       the ones for decompressors (cmd_bzip2_with_size etc.)
    
     - Misc Makefile cleanups
    
    * tag 'kbuild-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild: (34 commits)
      kbuild: add cmd_file_size
      arch: decompressor: remove useless vmlinux.bin.all-y
      kbuild: rename cmd_{bzip2,lzma,lzo,lz4,xzkern,zstd22}
      kbuild: drop $(size_append) from cmd_zstd
      sh: rename suffix-y to suffix_y
      doc: kbuild: fix default in `imply` table
      microblaze: use built-in function to get CPU_{MAJOR,MINOR,REV}
      certs: move scripts/extract-cert to certs/
      kbuild: do not quote string values in include/config/auto.conf
      kbuild: do not include include/config/auto.conf from shell scripts
      certs: simplify $(srctree)/ handling and remove config_filename macro
      kbuild: stop using config_filename in scripts/Makefile.modsign
      certs: remove misleading comments about GCC PR
      certs: refactor file cleaning
      certs: remove unneeded -I$(srctree) option for system_certificates.o
      certs: unify duplicated cmd_extract_certs and improve the log
      certs: use $< and $@ to simplify the key generation rule
      kbuild: remove headers_check stub
      kbuild: move headers_check.pl to usr/include/
      certs: use if_changed to re-generate the key when the key type is changed
      ...

commit 0a3d12ab5097b1d045e693412e6b366b7e82031b
Author: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>
Date:   Tue Jan 18 01:51:26 2022 +0100

    drm/vc4: Fix deadlock on DSI device attach error
    
    DSI device attach to DSI host will be done with host device's lock
    held.
    
    Un-registering host in "device attach" error path (ex: probe retry)
    will result in deadlock with below call trace and non operational
    DSI display.
    
    Startup Call trace:
    [   35.043036]  rt_mutex_slowlock.constprop.21+0x184/0x1b8
    [   35.043048]  mutex_lock_nested+0x7c/0xc8
    [   35.043060]  device_del+0x4c/0x3e8
    [   35.043075]  device_unregister+0x20/0x40
    [   35.043082]  mipi_dsi_remove_device_fn+0x18/0x28
    [   35.043093]  device_for_each_child+0x68/0xb0
    [   35.043105]  mipi_dsi_host_unregister+0x40/0x90
    [   35.043115]  vc4_dsi_host_attach+0xf0/0x120 [vc4]
    [   35.043199]  mipi_dsi_attach+0x30/0x48
    [   35.043209]  tc358762_probe+0x128/0x164 [tc358762]
    [   35.043225]  mipi_dsi_drv_probe+0x28/0x38
    [   35.043234]  really_probe+0xc0/0x318
    [   35.043244]  __driver_probe_device+0x80/0xe8
    [   35.043254]  driver_probe_device+0xb8/0x118
    [   35.043263]  __device_attach_driver+0x98/0xe8
    [   35.043273]  bus_for_each_drv+0x84/0xd8
    [   35.043281]  __device_attach+0xf0/0x150
    [   35.043290]  device_initial_probe+0x1c/0x28
    [   35.043300]  bus_probe_device+0xa4/0xb0
    [   35.043308]  deferred_probe_work_func+0xa0/0xe0
    [   35.043318]  process_one_work+0x254/0x700
    [   35.043330]  worker_thread+0x4c/0x448
    [   35.043339]  kthread+0x19c/0x1a8
    [   35.043348]  ret_from_fork+0x10/0x20
    
    Shutdown Call trace:
    [  365.565417] Call trace:
    [  365.565423]  __switch_to+0x148/0x200
    [  365.565452]  __schedule+0x340/0x9c8
    [  365.565467]  schedule+0x48/0x110
    [  365.565479]  schedule_timeout+0x3b0/0x448
    [  365.565496]  wait_for_completion+0xac/0x138
    [  365.565509]  __flush_work+0x218/0x4e0
    [  365.565523]  flush_work+0x1c/0x28
    [  365.565536]  wait_for_device_probe+0x68/0x158
    [  365.565550]  device_shutdown+0x24/0x348
    [  365.565561]  kernel_restart_prepare+0x40/0x50
    [  365.565578]  kernel_restart+0x20/0x70
    [  365.565591]  __do_sys_reboot+0x10c/0x220
    [  365.565605]  __arm64_sys_reboot+0x2c/0x38
    [  365.565619]  invoke_syscall+0x4c/0x110
    [  365.565634]  el0_svc_common.constprop.3+0xfc/0x120
    [  365.565648]  do_el0_svc+0x2c/0x90
    [  365.565661]  el0_svc+0x4c/0xf0
    [  365.565671]  el0t_64_sync_handler+0x90/0xb8
    [  365.565682]  el0t_64_sync+0x180/0x184
    
    Signed-off-by: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220118005127.29015-1-treasure4paddy@gmail.com

commit 0ed905975612ea67224af26fd6bfbac965b6d029
Merge: 39b419eaf0df0 a254a0e4093fc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 10:39:11 2022 +0200

    Merge branch 'random-5.17-rc1-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random
    
    Pull random number generator fixes from Jason Donenfeld:
    
     - Some Kconfig changes resulted in BIG_KEYS being unselectable, which
       Justin sent a patch to fix.
    
     - Geert pointed out that moving to BLAKE2s bloated vmlinux on little
       machines, like m68k, so we now compensate for this.
    
     - Numerous style and house cleaning fixes, meant to have a cleaner base
       for future changes.
    
    * 'random-5.17-rc1-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random:
      random: simplify arithmetic function flow in account()
      random: selectively clang-format where it makes sense
      random: access input_pool_data directly rather than through pointer
      random: cleanup fractional entropy shift constants
      random: prepend remaining pool constants with POOL_
      random: de-duplicate INPUT_POOL constants
      random: remove unused OUTPUT_POOL constants
      random: rather than entropy_store abstraction, use global
      random: remove unused extract_entropy() reserved argument
      random: remove incomplete last_data logic
      random: cleanup integer types
      random: cleanup poolinfo abstraction
      random: fix typo in comments
      lib/crypto: sha1: re-roll loops to reduce code size
      lib/crypto: blake2s: move hmac construction into wireguard
      lib/crypto: add prompts back to crypto libraries

commit 39b419eaf0df0de720ed417e785e6c0b004b0a51
Merge: 99613159ad749 60630924bb5af
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 19 10:29:20 2022 +0200

    Merge tag 'hwlock-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux
    
    Pull hwspinlock updates from Bjorn Andersson:
     "This contains a change to the stm32 hwspinlock driver to ensure that
      the hardware is operational even without CONFIG_PM"
    
    * tag 'hwlock-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux:
      hwspinlock: stm32: enable clock at probe

commit a1222ca0681f1db3696d703aa8df61c8b41a61ac
Author: Kalle Valo <kvalo@kernel.org>
Date:   Mon Jan 17 20:19:58 2022 +0200

    MAINTAINERS: remove extra wireless section
    
    There's an unneeded and almost empty wireless section in MAINTAINERS, seems to
    be leftovers from commit 0e324cf640fb ("MAINTAINERS: changes for wireless"). I
    don't see any need for that so let's remove it.
    
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220117181958.3509-2-kvalo@kernel.org

commit 51b667a32d616c399124328be97833ec154e0ff8
Author: Kalle Valo <kvalo@kernel.org>
Date:   Mon Jan 17 20:19:57 2022 +0200

    MAINTAINERS: add common wireless and wireless-next trees
    
    For easier maintenance we have decided to create common wireless and
    wireless-next trees for all wireless patches. Old mac80211 and wireless-drivers
    trees will not be used anymore.
    
    While at it, add a wiki link to wireless drivers section and a patchwork link
    to 802.11, mac80211 and rfkill sections. Also use https in patchwork links.
    
    Acked-by: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: Kalle Valo <kvalo@kernel.org>
    Link: https://lore.kernel.org/r/20220117181958.3509-1-kvalo@kernel.org

commit 99845220d3c3bd021819c5fea3d7cb55b2556296
Merge: 2836615aa22de 37c8d4807d1b8
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 18 19:28:28 2022 -0800

    Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf
    
    Daniel Borkmann says:
    
    ====================
    pull-request: bpf 2022-01-19
    
    We've added 12 non-merge commits during the last 8 day(s) which contain
    a total of 12 files changed, 262 insertions(+), 64 deletions(-).
    
    The main changes are:
    
    1) Various verifier fixes mainly around register offset handling when
       passed to helper functions, from Daniel Borkmann.
    
    2) Fix XDP BPF link handling to assert program type,
       from Toke Høiland-Jørgensen.
    
    3) Fix regression in mount parameter handling for BPF fs,
       from Yafang Shao.
    
    4) Fix incorrect integer literal when marking scratched stack slots
       in verifier, from Christy Lee.
    
    * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf:
      bpf, selftests: Add ringbuf memory type confusion test
      bpf, selftests: Add various ringbuf tests with invalid offset
      bpf: Fix ringbuf memory type confusion when passing to helpers
      bpf: Fix out of bounds access for ringbuf helpers
      bpf: Generally fix helper register offset check
      bpf: Mark PTR_TO_FUNC register initially with zero offset
      bpf: Generalize check_ctx_reg for reuse with other types
      bpf: Fix incorrect integer literal used for marking scratched stack.
      bpf/selftests: Add check for updating XDP bpf_link with wrong program type
      bpf/selftests: convert xdp_link test to ASSERT_* macros
      xdp: check prog type before updating BPF link
      bpf: Fix mount source show for bpffs
    ====================
    
    Link: https://lore.kernel.org/r/20220119011825.9082-1-daniel@iogearbox.net
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ccbf726171b7328f800bc98005132fd77eb1a175
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:11:11 2022 -0700

    io_uring: perform poll removal even if async work removal is successful
    
    An active work can have poll armed, hence it's not enough to just do
    the async work removal and return the value if it's different from "not
    found". Rather than make poll removal special, just fall through to do
    the remaining type lookups and removals.
    
    Reported-by: Florian Fischer <florian.fl.fischer@fau.de>
    Link: https://lore.kernel.org/io-uring/20220118151337.fac6cthvbnu7icoc@pasture/
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 361aee450c6e36c8dbab712c94a8a7835bd92e25
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:23:51 2022 -0700

    io-wq: add intermediate work step between pending list and active work
    
    We have a gap where a worker removes an item from the work list and to
    when it gets added as the workers active work. In this state, the work
    item cannot be found by cancelations. This is a small window, but it does
    exist.
    
    Add a temporary pointer to a work item that isn't on the pending work
    list anymore, but also not the active work. This is needed as we need
    to drop the wqe lock in between grabbing the work item and marking it
    as active, to ensure that signal based cancelations are properly
    ordered.
    
    Reported-by: Florian Fischer <florian.fl.fischer@fau.de>
    Link: https://lore.kernel.org/io-uring/20220118151337.fac6cthvbnu7icoc@pasture/
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit efdf518459b17e18a93c7c9cb622fd3051dabd0c
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:22:32 2022 -0700

    io-wq: perform both unstarted and started work cancelations in one go
    
    Rather than split these into two separate lookups and matches, combine
    them into one loop. This will become important when we can guarantee
    that we don't have a window where a pending work item isn't discoverable
    in either state.
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 36e4c58bf044b07204c8c7e6dd7c2384e439921a
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:18:20 2022 -0700

    io-wq: invoke work cancelation with wqe->lock held
    
    io_wqe_cancel_pending_work() grabs it internally, grab it upfront
    instead. For the running work cancelation, grab the lock around it as
    well.
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 081b58204629eff9dd93e7f68ed15c8aa6452a4b
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:13:43 2022 -0700

    io-wq: make io_worker lock a raw spinlock
    
    In preparation to nesting it under the wqe lock (which is raw due to
    being acquired from the scheduler side), change the io_worker lock from
    a normal spinlock to a raw spinlock.
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit ea6e7ceedaf11e1bad3ff21e8624694d696d276b
Author: Jens Axboe <axboe@kernel.dk>
Date:   Tue Jan 18 19:10:11 2022 -0700

    io-wq: remove useless 'work' argument to __io_worker_busy()
    
    We don't use 'work' anymore in the busy logic, remove the dead argument.
    
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 37c8d4807d1b8b521b30310dce97f6695dc2c2c6
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Wed Jan 12 12:39:48 2022 +0000

    bpf, selftests: Add ringbuf memory type confusion test
    
    Add two tests, one which asserts that ring buffer memory can be passed to
    other helpers for populating its entry area, and another one where verifier
    rejects different type of memory passed to bpf_ringbuf_submit().
    
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit 722e4db3ae0d52b2e3801280afbe19cf2d188e91
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Mon Jan 10 13:44:18 2022 +0000

    bpf, selftests: Add various ringbuf tests with invalid offset
    
    Assert that the verifier is rejecting invalid offsets on the ringbuf entries:
    
      # ./test_verifier | grep ring
      #947/u ringbuf: invalid reservation offset 1 OK
      #947/p ringbuf: invalid reservation offset 1 OK
      #948/u ringbuf: invalid reservation offset 2 OK
      #948/p ringbuf: invalid reservation offset 2 OK
    
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit a672b2e36a648afb04ad3bda93b6bda947a479a5
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Thu Jan 13 11:11:30 2022 +0000

    bpf: Fix ringbuf memory type confusion when passing to helpers
    
    The bpf_ringbuf_submit() and bpf_ringbuf_discard() have ARG_PTR_TO_ALLOC_MEM
    in their bpf_func_proto definition as their first argument, and thus both expect
    the result from a prior bpf_ringbuf_reserve() call which has a return type of
    RET_PTR_TO_ALLOC_MEM_OR_NULL.
    
    While the non-NULL memory from bpf_ringbuf_reserve() can be passed to other
    helpers, the two sinks (bpf_ringbuf_submit(), bpf_ringbuf_discard()) right now
    only enforce a register type of PTR_TO_MEM.
    
    This can lead to potential type confusion since it would allow other PTR_TO_MEM
    memory to be passed into the two sinks which did not come from bpf_ringbuf_reserve().
    
    Add a new MEM_ALLOC composable type attribute for PTR_TO_MEM, and enforce that:
    
     - bpf_ringbuf_reserve() returns NULL or PTR_TO_MEM | MEM_ALLOC
     - bpf_ringbuf_submit() and bpf_ringbuf_discard() only take PTR_TO_MEM | MEM_ALLOC
       but not plain PTR_TO_MEM arguments via ARG_PTR_TO_ALLOC_MEM
     - however, other helpers might treat PTR_TO_MEM | MEM_ALLOC as plain PTR_TO_MEM
       to populate the memory area when they use ARG_PTR_TO_{UNINIT_,}MEM in their
       func proto description
    
    Fixes: 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support for it")
    Reported-by: Alexei Starovoitov <ast@kernel.org>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit 64620e0a1e712a778095bd35cbb277dc2259281f
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Tue Jan 11 14:43:41 2022 +0000

    bpf: Fix out of bounds access for ringbuf helpers
    
    Both bpf_ringbuf_submit() and bpf_ringbuf_discard() have ARG_PTR_TO_ALLOC_MEM
    in their bpf_func_proto definition as their first argument. They both expect
    the result from a prior bpf_ringbuf_reserve() call which has a return type of
    RET_PTR_TO_ALLOC_MEM_OR_NULL.
    
    Meaning, after a NULL check in the code, the verifier will promote the register
    type in the non-NULL branch to a PTR_TO_MEM and in the NULL branch to a known
    zero scalar. Generally, pointer arithmetic on PTR_TO_MEM is allowed, so the
    latter could have an offset.
    
    The ARG_PTR_TO_ALLOC_MEM expects a PTR_TO_MEM register type. However, the non-
    zero result from bpf_ringbuf_reserve() must be fed into either bpf_ringbuf_submit()
    or bpf_ringbuf_discard() but with the original offset given it will then read
    out the struct bpf_ringbuf_hdr mapping.
    
    The verifier missed to enforce a zero offset, so that out of bounds access
    can be triggered which could be used to escalate privileges if unprivileged
    BPF was enabled (disabled by default in kernel).
    
    Fixes: 457f44363a88 ("bpf: Implement BPF ring buffer and verifier support for it")
    Reported-by: <tr3e.wang@gmail.com> (SecCoder Security Lab)
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit 6788ab23508bddb0a9d88e104284922cb2c22b77
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Mon Jan 10 14:40:40 2022 +0000

    bpf: Generally fix helper register offset check
    
    Right now the assertion on check_ptr_off_reg() is only enforced for register
    types PTR_TO_CTX (and open coded also for PTR_TO_BTF_ID), however, this is
    insufficient since many other PTR_TO_* register types such as PTR_TO_FUNC do
    not handle/expect register offsets when passed to helper functions.
    
    Given this can slip-through easily when adding new types, make this an explicit
    allow-list and reject all other current and future types by default if this is
    encountered.
    
    Also, extend check_ptr_off_reg() to handle PTR_TO_BTF_ID as well instead of
    duplicating it. For PTR_TO_BTF_ID, reg->off is used for BTF to match expected
    BTF ids if struct offset is used. This part still needs to be allowed, but the
    dynamic off from the tnum must be rejected.
    
    Fixes: 69c087ba6225 ("bpf: Add bpf_for_each_map_elem() helper")
    Fixes: eaa6bcb71ef6 ("bpf: Introduce bpf_per_cpu_ptr()")
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit d400a6cf1c8a57cdf10f35220ead3284320d85ff
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Fri Jan 14 13:58:36 2022 +0000

    bpf: Mark PTR_TO_FUNC register initially with zero offset
    
    Similar as with other pointer types where we use ldimm64, clear the register
    content to zero first, and then populate the PTR_TO_FUNC type and subprogno
    number. Currently this is not done, and leads to reuse of stale register
    tracking data.
    
    Given for special ldimm64 cases we always clear the register offset, make it
    common for all cases, so it won't be forgotten in future.
    
    Fixes: 69c087ba6225 ("bpf: Add bpf_for_each_map_elem() helper")
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit be80a1d3f9dbe5aee79a325964f7037fe2d92f30
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Mon Jan 10 14:05:49 2022 +0000

    bpf: Generalize check_ctx_reg for reuse with other types
    
    Generalize the check_ctx_reg() helper function into a more generic named one
    so that it can be reused for other register types as well to check whether
    their offset is non-zero. No functional change.
    
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Acked-by: Alexei Starovoitov <ast@kernel.org>

commit 4722f463896cc0ef1a6f1c3cb2e171e949831249
Author: Christian König <christian.koenig@amd.com>
Date:   Mon Jan 17 10:31:26 2022 +0100

    drm/radeon: fix error handling in radeon_driver_open_kms
    
    The return value was never initialized so the cleanup code executed when
    it isn't even necessary.
    
    Just add proper error handling.
    
    Fixes: ab50cb9df889 ("drm/radeon/radeon_kms: Fix a NULL pointer dereference in radeon_driver_open_kms()")
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Tested-by: Jan Stancek <jstancek@redhat.com>
    Tested-by: Borislav Petkov <bp@suse.de>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 9a458402fb69bda886aa6cbe067311b6e3d9c52a
Author: Jingwen Chen <Jingwen.Chen2@amd.com>
Date:   Thu Jan 13 19:06:59 2022 +0800

    drm/amd/amdgpu: fixing read wrong pf2vf data in SRIOV
    
    [Why]
    This fixes 892deb48269c ("drm/amdgpu: Separate vf2pf work item init from virt data exchange").
    we should read pf2vf data based at mman.fw_vram_usage_va after gmc
    sw_init. commit 892deb48269c breaks this logic.
    
    [How]
    calling amdgpu_virt_exchange_data in amdgpu_virt_init_data_exchange to
    set the right base in the right sequence.
    
    v2:
    call amdgpu_virt_init_data_exchange after gmc sw_init to make data
    exchange workqueue run
    
    v3:
    clean up the code logic
    
    v4:
    add some comment and make the code more readable
    
    Fixes: 892deb48269c ("drm/amdgpu: Separate vf2pf work item init from virt data exchange")
    Signed-off-by: Jingwen Chen <Jingwen.Chen2@amd.com>
    Reviewed-by: Horace Chen <horace.chen@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 520d9cd267618181901272a79db6154c0b83309c
Author: Guchun Chen <guchun.chen@amd.com>
Date:   Fri Jan 14 13:49:13 2022 +0800

    drm/amdgpu: apply vcn harvest quirk
    
    This is a following patch to apply the workaround only on
    those boards with a bad harvest table in ip discovery.
    
    Signed-off-by: Guchun Chen <guchun.chen@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ac090d9c90b087d6fb714e54b2a6dd1e6c373ed6
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Mon Jan 17 22:16:01 2022 +0900

    ksmbd: fix guest connection failure with nautilus
    
    MS-SMB2 describe session sign like the following.
    Session.SigningRequired MUST be set to TRUE under the following conditions:
     - If the SMB2_NEGOTIATE_SIGNING_REQUIRED bit is set in the SecurityMode
       field of the client request.
     - If the SMB2_SESSION_FLAG_IS_GUEST bit is not set in the SessionFlags
       field and Session.IsAnonymous is FALSE and either Connection.ShouldSign
       or global RequireMessageSigning is TRUE.
    
    When trying guest account connection using nautilus, The login failure
    happened on session setup. ksmbd does not allow this connection
    when the user is a guest and the connection sign is set. Just do not set
    session sign instead of error response as described in the specification.
    And this change improves the guest connection in Nautilus.
    
    Fixes: e2f34481b24d ("cifsd: add server-side procedures for SMB3")
    Cc: stable@vger.kernel.org # v5.15+
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit b207602fb04537cb21ac38fabd7577eca2fa05ae
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Sat Jan 15 14:49:00 2022 +0300

    ksmbd: uninitialized variable in create_socket()
    
    The "ksmbd_socket" variable is not initialized on this error path.
    
    Cc: stable@vger.kernel.org
    Fixes: 0626e6641f6b ("cifsd: add server handler for central processing and tranport layers")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 2fd5dcb1c8ef96c9f0fa8bda53ca480524b80ae7
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Thu Jan 13 09:51:39 2022 +0900

    ksmbd: smbd: fix missing client's memory region invalidation
    
    if the Channel of a SMB2 WRITE request is
    SMB2_CHANNEL_RDMA_V1_INVALIDTE, a client
    does not invalidate its memory regions but
    ksmbd must do it by sending a SMB2 WRITE response
    with IB_WR_SEND_WITH_INV.
    
    But if errors occur while processing a SMB2
    READ/WRITE request, ksmbd sends a response
    with IB_WR_SEND. So a client could use memory
    regions already in use.
    
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e4e2787bef7e643511cf0f352deb6bd16e7fa9b4
Author: Steve French <stfrench@microsoft.com>
Date:   Tue Jan 18 16:36:27 2022 -0600

    smb3: add new defines from protocol specification
    
    In the October updates to MS-SMB2 two additional FSCTLs
    were described.  Add the missing defines for these,
    as well as fix a typo in an earlier define.
    
    Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 6e7f90d163afa8fc2efd6ae318e7c20156a5621f
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Tue Jan 18 17:00:16 2022 -0500

    lockd: fix server crash on reboot of client holding lock
    
    I thought I was iterating over the array when actually the iteration is
    over the values contained in the array?
    
    Ugh, keep it simple.
    
    Symptoms were a null deference in vfs_lock_file() when an NFSv3 client
    that previously held a lock came back up and sent a notify.
    
    Reported-by: Jonathan Woithe <jwoithe@just42.net>
    Fixes: 7f024fcd5c97 ("Keep read and write fds with each nlm_file")
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 9c494ca4d3a535f9ca11ad6af1813983c1c6cbdd
Author: Lucas De Marchi <lucas.demarchi@intel.com>
Date:   Thu Jan 13 16:28:39 2022 -0800

    x86/gpu: Reserve stolen memory for first integrated Intel GPU
    
    "Stolen memory" is memory set aside for use by an Intel integrated GPU.
    The intel_graphics_quirks() early quirk reserves this memory when it is
    called for a GPU that appears in the intel_early_ids[] table of integrated
    GPUs.
    
    Previously intel_graphics_quirks() was marked as QFLAG_APPLY_ONCE, so it
    was called only for the first Intel GPU found.  If a discrete GPU happened
    to be enumerated first, intel_graphics_quirks() was called for it but not
    for any integrated GPU found later.  Therefore, stolen memory for such an
    integrated GPU was never reserved.
    
    For example, this problem occurs in this Alderlake-P (integrated) + DG2
    (discrete) topology where the DG2 is found first, but stolen memory is
    associated with the integrated GPU:
    
      - 00:01.0 Bridge
        `- 03:00.0 DG2 discrete GPU
      - 00:02.0 Integrated GPU (with stolen memory)
    
    Remove the QFLAG_APPLY_ONCE flag and call intel_graphics_quirks() for every
    Intel GPU.  Reserve stolen memory for the first GPU that appears in
    intel_early_ids[].
    
    [bhelgaas: commit log, add code comment, squash in
    https://lore.kernel.org/r/20220118190558.2ququ4vdfjuahicm@ldmartin-desk2]
    Link: https://lore.kernel.org/r/20220114002843.2083382-1-lucas.demarchi@intel.com
    Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Cc: stable@vger.kernel.org

commit a8e422af696133003903e440b87f10a8248051b8
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Tue Jan 18 10:18:36 2022 -0800

    xfs: remove unused xfs_ioctl32.h declarations
    
    Remove these unused ia32 compat declarations; all the bits involved have
    either been withdrawn or hoisted to the VFS.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Eric Sandeen <sandeen@redhat.com>

commit 35140d399db2b67153fc53b51a97ddb8ba3b5956
Author: Yinan Liu <yinan@linux.alibaba.com>
Date:   Tue Jan 18 14:52:41 2022 +0800

    script/sorttable: Fix some initialization problems
    
    elf_mcount_loc and mcount_sort_thread definitions are not
    initialized immediately within the function, which can cause
    the judgment logic to use uninitialized values when the
    initialization logic of subsequent code fails.
    
    Link: https://lkml.kernel.org/r/20211212113358.34208-2-yinan@linux.alibaba.com
    Link: https://lkml.kernel.org/r/20220118065241.42364-1-yinan@linux.alibaba.com
    
    Fixes: 72b3942a173c ("scripts: ftrace - move the sort-processing in ftrace_init")
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Reviewed-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Yinan Liu <yinan@linux.alibaba.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 2836615aa22de55b8fca5e32fe1b27a67cda625e
Author: Eric Dumazet <edumazet@google.com>
Date:   Tue Jan 18 03:43:40 2022 -0800

    netns: add schedule point in ops_exit_list()
    
    When under stress, cleanup_net() can have to dismantle
    netns in big numbers. ops_exit_list() currently calls
    many helpers [1] that have no schedule point, and we can
    end up with soft lockups, particularly on hosts
    with many cpus.
    
    Even for moderate amount of netns processed by cleanup_net()
    this patch avoids latency spikes.
    
    [1] Some of these helpers like fib_sync_up() and fib_sync_down_dev()
    are very slow because net/ipv4/fib_semantics.c uses host-wide hash tables,
    and ifindex is used as the only input of two hash functions.
        ifindexes tend to be the same for all netns (lo.ifindex==1 per instance)
        This will be fixed in a separate patch.
    
    Fixes: 72ad937abd0a ("net: Add support for batching network namespace cleanups")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Eric W. Biederman <ebiederm@xmission.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit fd9f4e62a39f09a7c014d7415c2b9d1390aa0504
Author: Christoph Hellwig <hch@lst.de>
Date:   Tue Jan 18 08:04:44 2022 +0100

    block: assign bi_bdev for cloned bios in blk_rq_prep_clone
    
    bio_clone_fast() sets the cloned bio to have the same ->bi_bdev as the
    source bio. This means that when request-based dm called setup_clone(),
    the cloned bio had its ->bi_bdev pointing to the dm device. After Commit
    0b6e522cdc4a ("blk-mq: use ->bi_bdev for I/O accounting")
    __blk_account_io_start() started using the request's ->bio->bi_bdev for
    I/O accounting, if it was set. This caused IO going to the underlying
    devices to use the dm device for their I/O accounting.
    
    Set up the proper ->bi_bdev in blk_rq_prep_clone based on the whole
    device bdev for the queue the request is cloned onto.
    
    Fixes: 0b6e522cdc4a ("blk-mq: use ->bi_bdev for I/O accounting")
    Reported-by: Benjamin Marzinski <bmarzins@redhat.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    [hch: the commit message is mostly from a different patch from Benjamin]
    Reviewed-by: Ming Lei <ming.lei@redhat.com>
    Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
    Link: https://lore.kernel.org/r/20220118070444.1241739-1-hch@lst.de
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 85c25662d18903874fad585d17fc398a7ba37ab0
Author: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Date:   Mon Jan 17 23:00:55 2022 +0100

    ALSA: hda: cs35l41: Make cs35l41_hda_remove() return void
    
    Up to now cs35l41_hda_remove() returns zero unconditionally. Make it
    return void instead which makes it easier to see in the callers that
    there is no error to handle.
    
    Also the return value of i2c and spi remove callbacks is ignored anyway.
    
    Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Reviewed-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117220055.120955-1-u.kleine-koenig@pengutronix.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 8c286a0f973a81201a0cef72a7ca55eda29fc35c
Author: Lucas Tanure <tanureal@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:30 2022 +0000

    ALSA: hda: cs35l41: Tidyup code
    
    Clean up and simplify cs35l41_hda_bind function
    
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-6-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit a025df02ce424fa77f6bc6aa195db21677e11274
Author: Lucas Tanure <tanureal@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:29 2022 +0000

    ALSA: hda: cs35l41: Make use of the helper function dev_err_probe()
    
    When possible use dev_err_probe help to properly deal with the
    PROBE_DEFER error, the benefit is that DEFER issue will be logged
    in the devices_deferred debugfs file.
    Using dev_err_probe() can reduce code size, and the error value
    gets printed.
    
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-5-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit cd8abf7d04c940c627ceb6f416b2142d3e7b36dd
Author: Lucas Tanure <tanureal@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:28 2022 +0000

    ALSA: hda: cs35l41: Add missing default cases
    
    Add switch default cases at gpio pins configs
    
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-4-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 77dc3a6ee2eb5851535fe3a84fc31bf0705e4a2e
Author: Lucas Tanure <tanureal@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:27 2022 +0000

    ALSA: hda: cs35l41: Move cs35l41* calls to its own symbol namespace
    
    Create own namespace and avoid polluting the global namespace
    
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-3-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 6e4320d8ecbc8711209b3075f2d896667006fa37
Author: Charles Keepax <ckeepax@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:26 2022 +0000

    ALSA: hda: cs35l41: Add calls to newly added test key function
    
    The test key now needs to be manually held when calling
    cs35l41_register_errata_patch, after patch:
    
    Add the missing function calls to this driver.
    
    Fixes: f517ba4924ad ("ASoC: cs35l41: Add support for hibernate memory retention mode")
    Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-2-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 2cb52046d186863e16ac82850c0e225462e493f1
Author: Charles Keepax <ckeepax@opensource.cirrus.com>
Date:   Mon Jan 17 16:08:25 2022 +0000

    ALSA: hda: cs35l41: Avoid overwriting register patch
    
    regmap_register_patch can't be used to apply the probe sequence as a
    patch is already registers with the regmap by
    cs35l41_register_errata_patch and only a single patch can be attached to
    a single regmap. The driver doesn't currently rely on a cache sync to
    re-apply this probe sequence so simply switch it to a multi write.
    
    Fixes: 7b2f3eb492da ("ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems")
    Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Signed-off-by: Lucas Tanure <tanureal@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220117160830.709403-1-tanureal@opensource.cirrus.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 0d3d237651fd7a01fe5dc501b0d170a43d8156ba
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Jan 17 13:09:31 2022 -0300

    perf evlist: No need to setup affinities when disabling events for pid targets
    
    When the target is a pid, not started by 'perf stat' we need to disable
    the events, and in that case there is no need to setup affinities as we
    use a dummy CPU map, with just one entry set to -1.
    
    So stop doing it to avoid this needless call to sched_getaffinity():
    
      # strace -ke sched_getaffinity perf stat -e cycles -p 241957 sleep 1
      <SNIP>
      sched_getaffinity(0, 512, [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31]) = 8
       > /usr/lib64/libc-2.33.so(sched_getaffinity@@GLIBC_2.3.4+0x1a) [0xe6eea]
       > /var/home/acme/bin/perf(affinity__setup+0x6a) [0x532a2a]
       > /var/home/acme/bin/perf(__evlist__disable.constprop.0+0x27) [0x4b9827]
       > /var/home/acme/bin/perf(cmd_stat+0x29b5) [0x431725]
       > /var/home/acme/bin/perf(run_builtin+0x6a) [0x4a2cfa]
       > /var/home/acme/bin/perf(main+0x612) [0x40f8c2]
       > /usr/lib64/libc-2.33.so(__libc_start_main+0xd4) [0x27b74]
       > /var/home/acme/bin/perf(_start+0x2d) [0x40fadd]
      <SNIP>
    
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Andi Kleen <andi@firstfloor.org>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220117160931.1191712-5-acme@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f350ee95498a3fa65c37ed597d9c051c6b2b6974
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Jan 17 13:09:30 2022 -0300

    perf evlist: No need to setup affinities when enabling events for pid targets
    
    When the target is a pid, not started by 'perf stat' we need to enable
    the events, and in that case there is no need to setup affinities as we
    use a dummy CPU map, with just one entry set to -1.
    
    So stop doing it to avoid this needless call to sched_getaffinity():
    
      # strace -ke sched_getaffinity perf stat -e cycles -p 241957 sleep 1
      <SNIP>
      sched_getaffinity(0, 512, [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31]) = 8
       > /usr/lib64/libc-2.33.so(sched_getaffinity@@GLIBC_2.3.4+0x1a) [0xe6eea]
       > /var/home/acme/bin/perf(affinity__setup+0x6a) [0x5329ca]
       > /var/home/acme/bin/perf(__evlist__enable.constprop.0+0x23) [0x4b9693]
       > /var/home/acme/bin/perf(enable_counters+0x14d) [0x42de5d]
       > /var/home/acme/bin/perf(cmd_stat+0x2358) [0x4310c8]
       > /var/home/acme/bin/perf(run_builtin+0x6a) [0x4a2cfa]
       > /var/home/acme/bin/perf(main+0x612) [0x40f8c2]
       > /usr/lib64/libc-2.33.so(__libc_start_main+0xd4) [0x27b74]
       > /var/home/acme/bin/perf(_start+0x2d) [0x40fadd]
      <SNIP>
    
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Andi Kleen <andi@firstfloor.org>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220117160931.1191712-4-acme@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 49de179577e7b05b57f625bf05cdc60a72de38d0
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Jan 17 13:09:29 2022 -0300

    perf stat: No need to setup affinities when starting a workload
    
    I.e. the simple:
    
      $ perf stat sleep 1
    
    Uses a dummy CPU map and thus there is no need to setup/cleanup
    affinities to avoid IPIs, etc.
    
    With this we're down to a sched_getaffinity() call, in the libnuma
    initialization, that probably can be removed in a followup patch.
    
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Andi Kleen <andi@firstfloor.org>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220117160931.1191712-3-acme@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 1855b796f2f672cbb25400be2d3171c26fc869a3
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Jan 17 13:09:28 2022 -0300

    perf affinity: Allow passing a NULL arg to affinity__cleanup()
    
    Just like with free(), NULL is checked to avoid having all callers do
    it.
    
    Its convenient for when not using affinity setup/cleanup for dummy CPU
    maps, i.e. CPU maps for pid targets.
    
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Andi Kleen <andi@firstfloor.org>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/r/20220117160931.1191712-2-acme@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 4624f199327a704dd1069aca1c3cadb8f2a28c6f
Author: Zechuan Chen <chenzechuan1@huawei.com>
Date:   Tue Dec 28 19:13:38 2021 +0800

    perf probe: Fix ppc64 'perf probe add events failed' case
    
    Because of commit bf794bf52a80c627 ("powerpc/kprobes: Fix kallsyms
    lookup across powerpc ABIv1 and ABIv2"), in ppc64 ABIv1, our perf
    command eliminates the need to use the prefix "." at the symbol name.
    
    But when the command "perf probe -a schedule" is executed on ppc64
    ABIv1, it obtains two symbol address information through /proc/kallsyms,
    for example:
    
      cat /proc/kallsyms | grep -w schedule
      c000000000657020 T .schedule
      c000000000d4fdb8 D schedule
    
    The symbol "D schedule" is not a function symbol, and perf will print:
    "p:probe/schedule _text+13958584"Failed to write event: Invalid argument
    
    Therefore, when searching symbols from map and adding probe point for
    them, a symbol type check is added. If the type of symbol is not a
    function, skip it.
    
    Fixes: bf794bf52a80c627 ("powerpc/kprobes: Fix kallsyms lookup across powerpc ABIv1 and ABIv2")
    Signed-off-by: Zechuan Chen <chenzechuan1@huawei.com>
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jianlin Lv <Jianlin.Lv@arm.com>
    Cc: Jin Yao <yao.jin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
    Cc: Yang Jihong <yangjihong1@huawei.com>
    Link: https://lore.kernel.org/r/20211228111338.218602-1-chenzechuan1@huawei.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit a254a0e4093fce8c832414a83940736067eed515
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Mon Jan 17 18:43:02 2022 +0100

    random: simplify arithmetic function flow in account()
    
    Now that have_bytes is never modified, we can simplify this function.
    First, we move the check for negative entropy_count to be first. That
    ensures that subsequent reads of this will be non-negative. Then,
    have_bytes and ibytes can be folded into their one use site in the
    min_t() function.
    
    Suggested-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 248045b8dea5a32ddc0aa44193d6bc70c4b9cd8e
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Sat Jan 15 14:57:22 2022 +0100

    random: selectively clang-format where it makes sense
    
    This is an old driver that has seen a lot of different eras of kernel
    coding style. In an effort to make it easier to code for, unify the
    coding style around the current norm, by accepting some of -- but
    certainly not all of -- the suggestions from clang-format. This should
    remove ambiguity in coding style, especially with regards to spacing,
    when code is being changed or amended. Consequently it also makes code
    review easier on the eyes, following one uniform style rather than
    several.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 6c0eace6e1499712583b6ee62d95161e8b3449f5
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Sat Jan 15 14:40:04 2022 +0100

    random: access input_pool_data directly rather than through pointer
    
    This gets rid of another abstraction we no longer need. It would be nice
    if we could instead make pool an array rather than a pointer, but the
    latent entropy plugin won't be able to do its magic in that case. So
    instead we put all accesses to the input pool's actual data through the
    input_pool_data array directly.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 18263c4e8e62f7329f38f5eadc568751242ca89c
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Thu Jan 13 18:18:48 2022 +0100

    random: cleanup fractional entropy shift constants
    
    The entropy estimator is calculated in terms of 1/8 bits, which means
    there are various constants where things are shifted by 3. Move these
    into our pool info enum with the other relevant constants. While we're
    at it, move an English assertion about sizes into a proper BUILD_BUG_ON
    so that the compiler can ensure this invariant.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit b3d51c1f542113342ddfbf6007e38a684b9dbec9
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Fri Jan 14 16:48:35 2022 +0100

    random: prepend remaining pool constants with POOL_
    
    The other pool constants are prepended with POOL_, but not these last
    ones. Rename them. This will then let us move them into the enum in the
    following commit.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 5b87adf30f1464477169a1d653e9baf8c012bbfe
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Thu Jan 13 16:11:21 2022 +0100

    random: de-duplicate INPUT_POOL constants
    
    We already had the POOL_* constants, so deduplicate the older INPUT_POOL
    ones. As well, fold EXTRACT_SIZE into the poolinfo enum, since it's
    related.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 0f63702718c91d89c922081ac1e6baeddc2d8b1a
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Thu Jan 13 15:51:06 2022 +0100

    random: remove unused OUTPUT_POOL constants
    
    We no longer have an output pool. Rather, we have just a wakeup bits
    threshold for /dev/random reads, presumably so that processes don't
    hang. This value, random_write_wakeup_bits, is configurable anyway. So
    all the no longer usefully named OUTPUT_POOL constants were doing was
    setting a reasonable default for random_write_wakeup_bits. This commit
    gets rid of the constants and just puts it all in the default value of
    random_write_wakeup_bits.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 90ed1e67e896cc8040a523f8428fc02f9b164394
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Jan 12 17:18:08 2022 +0100

    random: rather than entropy_store abstraction, use global
    
    Originally, the RNG used several pools, so having things abstracted out
    over a generic entropy_store object made sense. These days, there's only
    one input pool, and then an uneven mix of usage via the abstraction and
    usage via &input_pool. Rather than this uneasy mixture, just get rid of
    the abstraction entirely and have things always use the global. This
    simplifies the code and makes reading it a bit easier.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 8b2d953b91e7f60200c24067ab17b77cc7bfd0d4
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Jan 12 15:28:21 2022 +0100

    random: remove unused extract_entropy() reserved argument
    
    This argument is always set to zero, as a result of us not caring about
    keeping a certain amount reserved in the pool these days. So just remove
    it and cleanup the function signatures.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit a4bfa9b31802c14ff5847123c12b98d5e36b3985
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Jan 12 15:22:30 2022 +0100

    random: remove incomplete last_data logic
    
    There were a few things added under the "if (fips_enabled)" banner,
    which never really got completed, and the FIPS people anyway are
    choosing a different direction. Rather than keep around this halfbaked
    code, get rid of it so that we can focus on a single design of the RNG
    rather than two designs.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit d38bb0853589c939573ea50e9cb64f733e0e273d
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Sun Jan 9 17:48:58 2022 +0100

    random: cleanup integer types
    
    Rather than using the userspace type, __uXX, switch to using uXX. And
    rather than using variously chosen `char *` or `unsigned char *`, use
    `u8 *` uniformly for things that aren't strings, in the case where we
    are doing byte-by-byte traversal.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 91ec0fe138f107232cb36bc6112211db37cb5306
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Sun Jan 9 17:32:02 2022 +0100

    random: cleanup poolinfo abstraction
    
    Now that we're only using one polynomial, we can cleanup its
    representation into constants, instead of passing around pointers
    dynamically to select different polynomials. This improves the codegen
    and makes the code a bit more straightforward.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit c0a8a61e7abbf66729687ee63659ee25983fbb1e
Author: Schspa Shi <schspa@gmail.com>
Date:   Fri Jan 14 16:12:16 2022 +0800

    random: fix typo in comments
    
    s/or/for
    
    Signed-off-by: Schspa Shi <schspa@gmail.com>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 9a1536b093bb5bf60689021275fd24d513bb8db0
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Tue Jan 11 18:58:43 2022 +0100

    lib/crypto: sha1: re-roll loops to reduce code size
    
    With SHA-1 no longer being used for anything performance oriented, and
    also soon to be phased out entirely, we can make up for the space added
    by unrolled BLAKE2s by simply re-rolling SHA-1. Since SHA-1 is so much
    more complex, re-rolling it more or less takes care of the code size
    added by BLAKE2s. And eventually, hopefully we'll see SHA-1 removed
    entirely from most small kernel builds.
    
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: Ard Biesheuvel <ardb@kernel.org>
    Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit d8d83d8ab0a453e17e68b3a3bed1f940c34b8646
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Tue Jan 11 14:37:41 2022 +0100

    lib/crypto: blake2s: move hmac construction into wireguard
    
    Basically nobody should use blake2s in an HMAC construction; it already
    has a keyed variant. But unfortunately for historical reasons, Noise,
    used by WireGuard, uses HKDF quite strictly, which means we have to use
    this. Because this really shouldn't be used by others, this commit moves
    it into wireguard's noise.c locally, so that kernels that aren't using
    WireGuard don't get this superfluous code baked in. On m68k systems,
    this shaves off ~314 bytes.
    
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit e56e18985596617ae426ed5997fb2e737cffb58b
Author: Justin M. Forbes <jforbes@fedoraproject.org>
Date:   Wed Jan 12 08:01:38 2022 -0600

    lib/crypto: add prompts back to crypto libraries
    
    Commit 6048fdcc5f269 ("lib/crypto: blake2s: include as built-in") took
    away a number of prompt texts from other crypto libraries. This makes
    values flip from built-in to module when oldconfig runs, and causes
    problems when these crypto libs need to be built in for thingslike
    BIG_KEYS.
    
    Fixes: 6048fdcc5f269 ("lib/crypto: blake2s: include as built-in")
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: linux-crypto@vger.kernel.org
    Signed-off-by: Justin M. Forbes <jforbes@fedoraproject.org>
    [Jason: - moved menu into submenu of lib/ instead of root menu
            - fixed chacha sub-dependencies for CONFIG_CRYPTO]
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 99613159ad749543621da8238acf1a122880144e
Merge: fe81ba137ebcc bbd0ff07ed12f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 14:03:34 2022 +0200

    Merge tag 'dmaengine-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine
    
    Pull dmaengine updates from Vinod Koul:
     "A bunch of new support and few updates to drivers:
    
      New support:
       - DMA_MEMCPY_SG support is bought back as we have a user in Xilinx
         driver
       - Support for TI J721S2 SoC in k3-udma driver
       - Support for Ingenic MDMA and BDMA in the JZ4760
       - Support for Renesas r8a779f0 dmac
    
      Updates:
       - We are finally getting rid of slave_id, so this brings in the
         changes across tree for that
       - updates for idxd driver
       - at_xdmac driver cleanup"
    
    * tag 'dmaengine-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine: (60 commits)
      dt-bindings: dma-controller: Split interrupt fields in example
      dmaengine: pch_dma: Remove usage of the deprecated "pci-dma-compat.h" API
      dmaengine: at_xdmac: Fix race over irq_status
      dmaengine: at_xdmac: Remove a level of indentation in at_xdmac_tasklet()
      dmaengine: at_xdmac: Fix at_xdmac_lld struct definition
      dmaengine: at_xdmac: Fix lld view setting
      dmaengine: at_xdmac: Remove a level of indentation in at_xdmac_advance_work()
      dmaengine: at_xdmac: Fix concurrency over xfers_list
      dmaengine: at_xdmac: Move the free desc to the tail of the desc list
      dmaengine: at_xdmac: Fix race for the tx desc callback
      dmaengine: at_xdmac: Fix concurrency over chan's completed_cookie
      dmaengine: at_xdmac: Print debug message after realeasing the lock
      dmaengine: at_xdmac: Start transfer for cyclic channels in issue_pending
      dmaengine: at_xdmac: Don't start transactions at tx_submit level
      dmaengine: idxd: deprecate token sysfs attributes for read buffers
      dmaengine: idxd: change bandwidth token to read buffers
      dmaengine: idxd: fix wq settings post wq disable
      dmaengine: idxd: change MSIX allocation based on per wq activation
      dmaengine: idxd: fix descriptor flushing locking
      dmaengine: idxd: embed irq_entry in idxd_wq struct
      ...

commit 0e3872499de1a1230cef5221607d71aa09264bd5
Author: Hui Su <suhui_kernel@163.com>
Date:   Fri Jan 7 17:52:54 2022 +0800

    kernel/sched: Remove dl_boosted flag comment
    
    since commit 2279f540ea7d ("sched/deadline: Fix priority
    inheritance with multiple scheduling classes"), we should not
    keep it here.
    
    Signed-off-by: Hui Su <suhui_kernel@163.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Daniel Bristot de Oliveira <bristot@redhat.com>
    Link: https://lore.kernel.org/r/20220107095254.GA49258@localhost.localdomain

commit 7e406d1ff39b8ee574036418a5043c86723170cf
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Sat Dec 25 01:04:57 2021 +0100

    sched: Avoid double preemption in __cond_resched_*lock*()
    
    For PREEMPT/DYNAMIC_PREEMPT the *_unlock() will already trigger a
    preemption, no point in then calling preempt_schedule_common()
    *again*.
    
    Use _cond_resched() instead, since this is a NOP for the preemptible
    configs while it provide a preemption point for the others.
    
    Reported-by: xuhaifeng <xuhaifeng@oppo.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/YcGnvDEYBwOiV0cR@hirez.programming.kicks-ass.net

commit a315da5e686b02b20c1713dda818e8fb691526bb
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Fri Dec 17 21:59:00 2021 -0800

    sched/fair: Fix all kernel-doc warnings
    
    Quieten all kernel-doc warnings in kernel/sched/fair.c:
    
    kernel/sched/fair.c:3663: warning: No description found for return value of 'update_cfs_rq_load_avg'
    kernel/sched/fair.c:8601: warning: No description found for return value of 'asym_smt_can_pull_tasks'
    kernel/sched/fair.c:8673: warning: Function parameter or member 'sds' not described in 'update_sg_lb_stats'
    kernel/sched/fair.c:9483: warning: contents before sections
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
    Acked-by: Vincent Guittot <vincent.guittot@linaro.org>
    Link: https://lore.kernel.org/r/20211218055900.2704-1-rdunlap@infradead.org

commit b171501f258063f5c56dd2c5fdf310802d8d7dc1
Author: Cruz Zhao <CruzZhao@linux.alibaba.com>
Date:   Tue Jan 11 17:55:59 2022 +0800

    sched/core: Accounting forceidle time for all tasks except idle task
    
    There are two types of forced idle time: forced idle time from cookie'd
    task and forced idle time form uncookie'd task. The forced idle time from
    uncookie'd task is actually caused by the cookie'd task in runqueue
    indirectly, and it's more accurate to measure the capacity loss with the
    sum of both.
    
    Assuming cpu x and cpu y are a pair of SMT siblings, consider the
    following scenarios:
      1.There's a cookie'd task running on cpu x, and there're 4 uncookie'd
        tasks running on cpu y. For cpu x, there will be 80% forced idle time
        (from uncookie'd task); for cpu y, there will be 20% forced idle time
        (from cookie'd task).
      2.There's a uncookie'd task running on cpu x, and there're 4 cookie'd
        tasks running on cpu y. For cpu x, there will be 80% forced idle time
        (from cookie'd task); for cpu y, there will be 20% forced idle time
        (from uncookie'd task).
    
    The scenario1 can recurrent by stress-ng(scenario2 can recurrent similary):
        (cookie'd)taskset -c x stress-ng -c 1 -l 100
        (uncookie'd)taskset -c y stress-ng -c 4 -l 100
    
    In the above two scenarios, the total capacity loss is 1 cpu, but in
    scenario1, the cookie'd forced idle time tells us 20% cpu capacity loss, in
    scenario2, the cookie'd forced idle time tells us 80% cpu capacity loss,
    which are not accurate. It'll be more accurate to measure with cookie'd
    forced idle time and uncookie'd forced idle time.
    
    Signed-off-by: Cruz Zhao <CruzZhao@linux.alibaba.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Josh Don <joshdon@google.com>
    Link: https://lore.kernel.org/r/1641894961-9241-2-git-send-email-CruzZhao@linux.alibaba.com

commit 2d02fa8cc21a93da35cfba462bf8ab87bf2db651
Author: Vincent Guittot <vincent.guittot@linaro.org>
Date:   Tue Jan 11 14:46:59 2022 +0100

    sched/pelt: Relax the sync of load_sum with load_avg
    
    Similarly to util_avg and util_sum, don't sync load_sum with the low
    bound of load_avg but only ensure that load_sum stays in the correct range.
    
    Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Link: https://lkml.kernel.org/r/20220111134659.24961-5-vincent.guittot@linaro.org

commit 95246d1ec80b8d19d882cd8eb7ad094e63b41bb8
Author: Vincent Guittot <vincent.guittot@linaro.org>
Date:   Tue Jan 11 14:46:58 2022 +0100

    sched/pelt: Relax the sync of runnable_sum with runnable_avg
    
    Similarly to util_avg and util_sum, don't sync runnable_sum with the low
    bound of runnable_avg but only ensure that runnable_sum stays in the
    correct range.
    
    Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Link: https://lkml.kernel.org/r/20220111134659.24961-4-vincent.guittot@linaro.org

commit 7ceb77103001544a43e11d7f3a8a69a2c1f422cf
Author: Vincent Guittot <vincent.guittot@linaro.org>
Date:   Tue Jan 11 14:46:57 2022 +0100

    sched/pelt: Continue to relax the sync of util_sum with util_avg
    
    Rick reported performance regressions in bugzilla because of cpu frequency
    being lower than before:
        https://bugzilla.kernel.org/show_bug.cgi?id=215045
    
    He bisected the problem to:
    commit 1c35b07e6d39 ("sched/fair: Ensure _sum and _avg values stay consistent")
    
    This commit forces util_sum to be synced with the new util_avg after
    removing the contribution of a task and before the next periodic sync. By
    doing so util_sum is rounded to its lower bound and might lost up to
    LOAD_AVG_MAX-1 of accumulated contribution which has not yet been
    reflected in util_avg.
    
    update_tg_cfs_util() is not the only place where we round util_sum and
    lost some accumulated contributions that are not already reflected in
    util_avg. Modify update_tg_cfs_util() and detach_entity_load_avg() to not
    sync util_sum with the new util_avg. Instead of always setting util_sum to
    the low bound of util_avg, which can significantly lower the utilization,
    we propagate the difference. In addition, we also check that cfs's util_sum
    always stays above the lower bound for a given util_avg as it has been
    observed that sched_entity's util_sum is sometimes above cfs one.
    
    Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Link: https://lkml.kernel.org/r/20220111134659.24961-3-vincent.guittot@linaro.org

commit 98b0d890220d45418cfbc5157b3382e6da5a12ab
Author: Vincent Guittot <vincent.guittot@linaro.org>
Date:   Tue Jan 11 14:46:56 2022 +0100

    sched/pelt: Relax the sync of util_sum with util_avg
    
    Rick reported performance regressions in bugzilla because of cpu frequency
    being lower than before:
        https://bugzilla.kernel.org/show_bug.cgi?id=215045
    
    He bisected the problem to:
    commit 1c35b07e6d39 ("sched/fair: Ensure _sum and _avg values stay consistent")
    
    This commit forces util_sum to be synced with the new util_avg after
    removing the contribution of a task and before the next periodic sync. By
    doing so util_sum is rounded to its lower bound and might lost up to
    LOAD_AVG_MAX-1 of accumulated contribution which has not yet been
    reflected in util_avg.
    
    Instead of always setting util_sum to the low bound of util_avg, which can
    significantly lower the utilization of root cfs_rq after propagating the
    change down into the hierarchy, we revert the change of util_sum and
    propagate the difference.
    
    In addition, we also check that cfs's util_sum always stays above the
    lower bound for a given util_avg as it has been observed that
    sched_entity's util_sum is sometimes above cfs one.
    
    Fixes: 1c35b07e6d39 ("sched/fair: Ensure _sum and _avg values stay consistent")
    Reported-by: Rick Yiu <rickyiu@google.com>
    Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
    Tested-by: Sachin Sant <sachinp@linux.ibm.com>
    Link: https://lkml.kernel.org/r/20220111134659.24961-2-vincent.guittot@linaro.org

commit a06247c6804f1a7c86a2e5398a4c1f1db1471848
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Tue Jan 11 15:23:09 2022 -0800

    psi: Fix uaf issue when psi trigger is destroyed while being polled
    
    With write operation on psi files replacing old trigger with a new one,
    the lifetime of its waitqueue is totally arbitrary. Overwriting an
    existing trigger causes its waitqueue to be freed and pending poll()
    will stumble on trigger->event_wait which was destroyed.
    Fix this by disallowing to redefine an existing psi trigger. If a write
    operation is used on a file descriptor with an already existing psi
    trigger, the operation will fail with EBUSY error.
    Also bypass a check for psi_disabled in the psi_trigger_destroy as the
    flag can be flipped after the trigger is created, leading to a memory
    leak.
    
    Fixes: 0e94682b73bf ("psi: introduce psi monitor")
    Reported-by: syzbot+cdb5dd11c97cc532efad@syzkaller.appspotmail.com
    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    Analyzed-by: Eric Biggers <ebiggers@kernel.org>
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Eric Biggers <ebiggers@google.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20220111232309.1786347-1-surenb@google.com

commit 8c16dc047b5dd8f7b3bf4584fa75733ea0dde7dc
Author: Andi Kleen <ak@linux.intel.com>
Date:   Wed Dec 15 12:40:29 2021 -0800

    x86/perf: Avoid warning for Arch LBR without XSAVE
    
    Some hypervisors support Arch LBR, but without the LBR XSAVE support.
    The current Arch LBR init code prints a warning when the xsave size (0) is
    unexpected. Avoid printing the warning for the "no LBR XSAVE" case.
    
    Signed-off-by: Andi Kleen <ak@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/20211215204029.150686-1-ak@linux.intel.com

commit 5a4487f9ef5ef2fdb3215cadf0a9c3e5e8678634
Author: Kan Liang <kan.liang@linux.intel.com>
Date:   Thu Jan 13 14:05:54 2022 -0800

    perf/x86/intel/uncore: Add IMC uncore support for ADL
    
    Current ADL uncore code only supports the legacy IMC (memory controller)
    free-running counters. Besides the free-running counters, ADL also
    supports several general purpose-counters.
    
    The general-purpose counters can also be accessed via MMIO but in a
    different location. Factor out __uncore_imc_init_box() with offset as a
    parameter. The function can be shared between ADL and TGL.
    
    The event format and the layout of the control registers are a little
    bit different from other uncore counters.
    
    The intel_generic_uncore_mmio_enable_event() can be shared with client
    IMC uncore. Expose the function.
    
    Add more PCI IDs for ADL machines.
    
    Fixes: 772ed05f3c5c ("perf/x86/intel/uncore: Add Alder Lake support")
    Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/1642111554-118524-1-git-send-email-kan.liang@linux.intel.com

commit 6b19788ddc5937831ffd27525a1b793953fd2d2b
Author: Peter Zijlstra (Intel) <peterz@infradead.org>
Date:   Tue Jan 4 08:51:17 2022 -0800

    perf/x86/intel/lbr: Add static_branch for LBR INFO flags
    
    Using static_branch to replace the LBR INFO flags to optimize the LBR
    INFO parsing.
    
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Kan Liang <kan.liang@linux.intel.com>
    Link: https://lkml.kernel.org/r/1641315077-96661-2-git-send-email-peterz@infradead.org

commit 1ac7fd8159a842b3aa51f0b46a351fa3eeb8fbf3
Author: Peter Zijlstra (Intel) <peterz@infradead.org>
Date:   Tue Jan 4 08:51:16 2022 -0800

    perf/x86/intel/lbr: Support LBR format V7
    
    The Goldmont plus and Tremont have LBR format V7. The V7 has LBR_INFO,
    which is the same as LBR format V5. But V7 doesn't support TSX.
    
    Without the patch, the associated misprediction and cycles information
    in the LBR_INFO may be lost on a Goldmont plus platform.
    For Tremont, the patch only impacts the non-PEBS events. Because of the
    adaptive PEBS, the LBR_INFO is always processed for a PEBS event.
    
    Currently, two different ways are used to check the LBR capabilities,
    which make the codes complex and confusing.
    For the LBR format V4 and earlier, the global static lbr_desc array is
    used to store the flags for the LBR capabilities in each LBR format.
    For LBR format V5 and V6, the current code checks the version number
    for the LBR capabilities.
    
    There are common LBR capabilities among LBR format versions. Several
    flags for the LBR capabilities are introduced into the struct x86_pmu.
    The flags, which can be shared among LBR formats, are used to check
    the LBR capabilities. Add intel_pmu_lbr_init() to set the flags
    accordingly at boot time.
    
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Kan Liang <kan.liang@linux.intel.com>
    Link: https://lkml.kernel.org/r/1641315077-96661-1-git-send-email-peterz@infradead.org

commit 0036fb00a756a2f6e360d44e2e3d2200a8afbc9b
Author: Stephane Eranian <eranian@google.com>
Date:   Wed Jan 5 10:56:59 2022 -0800

    perf/x86/rapl: fix AMD event handling
    
    The RAPL events exposed under /sys/devices/power/events should only reflect
    what the underlying hardware actually support. This is how it works on Intel
    RAPL and Intel core/uncore PMUs in general.
    But on AMD, this was not the case. All possible RAPL events were advertised.
    
    This is what it showed on an AMD Fam17h:
    $ ls /sys/devices/power/events/
    energy-cores        energy-gpu          energy-pkg          energy-psys
    energy-ram          energy-cores.scale  energy-gpu.scale    energy-pkg.scale
    energy-psys.scale   energy-ram.scale    energy-cores.unit   energy-gpu.unit
    energy-pkg.unit     energy-psys.unit    energy-ram.unit
    
    Yet, on AMD Fam17h, only energy-pkg is supported.
    
    This patch fixes the problem. Given the way perf_msr_probe() works, the
    amd_rapl_msrs[] table has to have all entries filled out and in particular
    the group field, otherwise perf_msr_probe() defaults to making the event
    visible.
    
    With the patch applied, the kernel now only shows was is actually supported:
    
    $ ls /sys/devices/power/events/
    energy-pkg  energy-pkg.scale  energy-pkg.unit
    
    The patch also uses the RAPL_MSR_MASK because only the 32-bits LSB of the
    RAPL counters are relevant when reading power consumption.
    
    Signed-off-by: Stephane Eranian <eranian@google.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Link: https://lkml.kernel.org/r/20220105185659.643355-1-eranian@google.com

commit 96fd2e89fba1aaada6f4b1e5d25a9d9ecbe1943d
Author: Zhengjun Xing <zhengjun.xing@linux.intel.com>
Date:   Thu Dec 23 22:48:26 2021 +0800

    perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
    
    The user recently report a perf issue in the ICX platform, when test by
    perf event “uncore_imc_x/cas_count_write”,the write bandwidth is always
    very small (only 0.38MB/s), it is caused by the wrong "umask" for the
    "cas_count_write" event. When double-checking, find "cas_count_read"
    also is wrong.
    
    The public document for ICX uncore:
    
    3rd Gen Intel® Xeon® Processor Scalable Family, Codename Ice Lake,Uncore
    Performance Monitoring Reference Manual, Revision 1.00, May 2021
    
    On 2.4.7, it defines Unit Masks for CAS_COUNT:
    RD b00001111
    WR b00110000
    
    So corrected both "cas_count_read" and "cas_count_write" for ICX.
    
    Old settings:
     hswep_uncore_imc_events
            INTEL_UNCORE_EVENT_DESC(cas_count_read,  "event=0x04,umask=0x03")
            INTEL_UNCORE_EVENT_DESC(cas_count_write, "event=0x04,umask=0x0c")
    
    New settings:
     snr_uncore_imc_events
            INTEL_UNCORE_EVENT_DESC(cas_count_read,  "event=0x04,umask=0x0f")
            INTEL_UNCORE_EVENT_DESC(cas_count_write, "event=0x04,umask=0x30")
    
    Fixes: 2b3b76b5ec67 ("perf/x86/intel/uncore: Add Ice Lake server uncore support")
    Signed-off-by: Zhengjun Xing <zhengjun.xing@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
    Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
    Cc: stable@vger.kernel.org
    Link: https://lkml.kernel.org/r/20211223144826.841267-1-zhengjun.xing@linux.intel.com

commit 7fa981cad216e9f64f49e22112f610c0bfed91bc
Author: Kan Liang <kan.liang@linux.intel.com>
Date:   Tue Jan 11 10:20:38 2022 -0800

    perf/x86/intel: Add a quirk for the calculation of the number of counters on Alder Lake
    
    For some Alder Lake machine with all E-cores disabled in a BIOS, the
    below warning may be triggered.
    
    [ 2.010766] hw perf events fixed 5 > max(4), clipping!
    
    Current perf code relies on the CPUID leaf 0xA and leaf 7.EDX[15] to
    calculate the number of the counters and follow the below assumption.
    
    For a hybrid configuration, the leaf 7.EDX[15] (X86_FEATURE_HYBRID_CPU)
    is set. The leaf 0xA only enumerate the common counters. Linux perf has
    to manually add the extra GP counters and fixed counters for P-cores.
    For a non-hybrid configuration, the X86_FEATURE_HYBRID_CPU should not
    be set. The leaf 0xA enumerates all counters.
    
    However, that's not the case when all E-cores are disabled in a BIOS.
    Although there are only P-cores in the system, the leaf 7.EDX[15]
    (X86_FEATURE_HYBRID_CPU) is still set. But the leaf 0xA is updated
    to enumerate all counters of P-cores. The inconsistency triggers the
    warning.
    
    Several software ways were considered to handle the inconsistency.
    - Drop the leaf 0xA and leaf 7.EDX[15] CPUID enumeration support.
      Hardcode the number of counters. This solution may be a problem for
      virtualization. A hypervisor cannot control the number of counters
      in a Linux guest via changing the guest CPUID enumeration anymore.
    - Find another CPUID bit that is also updated with E-cores disabled.
      There may be a problem in the virtualization environment too. Because
      a hypervisor may disable the feature/CPUID bit.
    - The P-cores have a maximum of 8 GP counters and 4 fixed counters on
      ADL. The maximum number can be used to detect the case.
      This solution is implemented in this patch.
    
    Fixes: ee72a94ea4a6 ("perf/x86/intel: Fix fixed counter check warning for some Alder Lake")
    Reported-by: Damjan Marion (damarion) <damarion@cisco.com>
    Reported-by: Chan Edison <edison_chan_gz@hotmail.com>
    Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Damjan Marion (damarion) <damarion@cisco.com>
    Cc: stable@vger.kernel.org
    Link: https://lkml.kernel.org/r/1641925238-149288-1-git-send-email-kan.liang@linux.intel.com

commit 09f5e7dc7ad705289e1b1ec065439aa3c42951c4
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Mon Dec 20 13:19:52 2021 +0100

    perf: Fix perf_event_read_local() time
    
    Time readers that cannot take locks (due to NMI etc..) currently make
    use of perf_event::shadow_ctx_time, which, for that event gives:
    
      time' = now + (time - timestamp)
    
    or, alternatively arranged:
    
      time' = time + (now - timestamp)
    
    IOW, the progression of time since the last time the shadow_ctx_time
    was updated.
    
    There's problems with this:
    
     A) the shadow_ctx_time is per-event, even though the ctx_time it
        reflects is obviously per context. The direct concequence of this
        is that the context needs to iterate all events all the time to
        keep the shadow_ctx_time in sync.
    
     B) even with the prior point, the context itself might not be active
        meaning its time should not advance to begin with.
    
     C) shadow_ctx_time isn't consistently updated when ctx_time is
    
    There are 3 users of this stuff, that suffer differently from this:
    
     - calc_timer_values()
       - perf_output_read()
       - perf_event_update_userpage()       /* A */
    
     - perf_event_read_local()              /* A,B */
    
    In particular, perf_output_read() doesn't suffer at all, because it's
    sample driven and hence only relevant when the event is actually
    running.
    
    This same was supposed to be true for perf_event_update_userpage(),
    after all self-monitoring implies the context is active *HOWEVER*, as
    per commit f79256532682 ("perf/core: fix userpage->time_enabled of
    inactive events") this goes wrong when combined with counter
    overcommit, in that case those events that do not get scheduled when
    the context becomes active (task events typically) miss out on the
    EVENT_TIME update and ENABLED time is inflated (for a little while)
    with the time the context was inactive. Once the event gets rotated
    in, this gets corrected, leading to a non-monotonic timeflow.
    
    perf_event_read_local() made things even worse, it can request time at
    any point, suffering all the problems perf_event_update_userpage()
    does and more. Because while perf_event_update_userpage() is limited
    by the context being active, perf_event_read_local() users have no
    such constraint.
    
    Therefore, completely overhaul things and do away with
    perf_event::shadow_ctx_time. Instead have regular context time updates
    keep track of this offset directly and provide perf_event_time_now()
    to complement perf_event_time().
    
    perf_event_time_now() will, in adition to being context wide, also
    take into account if the context is active. For inactive context, it
    will not advance time.
    
    This latter property means the cgroup perf_cgroup_info context needs
    to grow addition state to track this.
    
    Additionally, since all this is strictly per-cpu, we can use barrier()
    to order context activity vs context time.
    
    Fixes: 7d9285e82db5 ("perf/bpf: Extend the perf_event_read_local() interface, a.k.a. "bpf: perf event change needed for subsequent bpf helpers"")
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Tested-by: Song Liu <song@kernel.org>
    Tested-by: Namhyung Kim <namhyung@kernel.org>
    Link: https://lkml.kernel.org/r/YcB06DasOBtU0b00@hirez.programming.kicks-ass.net

commit 5f02ef741a785678930f3ff0a8b6b2b0ef1bb402
Author: Marcelo Tosatti <mtosatti@redhat.com>
Date:   Tue Jan 18 04:34:43 2022 -0500

    KVM: VMX: switch blocked_vcpu_on_cpu_lock to raw spinlock
    
    blocked_vcpu_on_cpu_lock is taken from hard interrupt context
    (pi_wakeup_handler), therefore it cannot sleep.
    
    Switch it to a raw spinlock.
    
    Fixes:
    
    [41297.066254] BUG: scheduling while atomic: CPU 0/KVM/635218/0x00010001
    [41297.066323] Preemption disabled at:
    [41297.066324] [<ffffffff902ee47f>] irq_enter_rcu+0xf/0x60
    [41297.066339] Call Trace:
    [41297.066342]  <IRQ>
    [41297.066346]  dump_stack_lvl+0x34/0x44
    [41297.066353]  ? irq_enter_rcu+0xf/0x60
    [41297.066356]  __schedule_bug.cold+0x7d/0x8b
    [41297.066361]  __schedule+0x439/0x5b0
    [41297.066365]  ? task_blocks_on_rt_mutex.constprop.0.isra.0+0x1b0/0x440
    [41297.066369]  schedule_rtlock+0x1e/0x40
    [41297.066371]  rtlock_slowlock_locked+0xf1/0x260
    [41297.066374]  rt_spin_lock+0x3b/0x60
    [41297.066378]  pi_wakeup_handler+0x31/0x90 [kvm_intel]
    [41297.066388]  sysvec_kvm_posted_intr_wakeup_ipi+0x9d/0xd0
    [41297.066392]  </IRQ>
    [41297.066392]  asm_sysvec_kvm_posted_intr_wakeup_ipi+0x12/0x20
    ...
    
    Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit fe81ba137ebcc7f236780996a0b375732c07e85c
Merge: 3bf6a9e36e441 237fe8885a3fd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 10:14:49 2022 +0200

    Merge tag 'ata-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata
    
    Pull ATA updates from Damien Le Moal:
     "A larger than usual set of changes for this cycle. The bulk of the
      changes are part of a rework of libata messages and debugging features
      from Hannes. In more detail, the changes are as follows.
    
       - Small code cleanups in the pata_ali driver (unnecessary variable
         initialization and simplified return statement, from Jason and
         Colin.
    
       - Switch to using struct_group() in the sata_fsl driver, from Kees.
    
       - Convert many sysfs attribute show functions to use sysfs_emit()
         instead of snprintf(), from me.
    
       - sata_dwc_460ex driver code cleanups, from Andy.
    
       - Improve DMA setup and remove superfluous error message in
         libahci_platform, from Andy
    
       - A small code cleanup in libata to use min() instead of open coding
         test, from Changcheng.
    
       - Rework of libata messages from Hannes. This is especially focused
         on replacing compile time defined debugging messages (DPRINTK() and
         VPRINTK()) with regular dynamic debugging messages (pr_debug()) and
         traceipoint events. Both libata-core and many drivers are updated
         to have a consistent debugging level control for all drivers.
    
       - Extend compile test support to as many drivers as possible in ATA
         Kconfig to improve compile test coverage, from me.
    
       - Fixes to avoid compile time warnings (W=1) and sparse warnings in
         sata_fsl and ahci_xgene drivers, from me.
    
       - Fix the interface of the read_id() port operation method to clarify
         that the data buffer passed as an argument is little endian. This
         avoids sparse warnings in the pata_netcell, pata_it821x,
         ahci_xgene, ahci_cevaxi and ahci_brcm drivers. From me.
    
       - Small code cleanup in the pata_octeon_cf driver, from Minghao.
    
       - Improved IRQ configuration code in pata_of_platform, from Lad.
    
       - Simplified implementation of __ata_scsi_queuecmd(), from Wenchao.
    
       - Debounce delay flag renaming, from Paul.
    
       - Add support for AMD A85 FCH (Hudson D4) AHCI adapters, from Paul"
    
    * tag 'ata-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/libata: (106 commits)
      ata: pata_ali: remove redundant return statement
      ata: ahci: Add support for AMD A85 FCH (Hudson D4)
      ata: libata: Rename link flag ATA_LFLAG_NO_DB_DELAY
      ata: libata-scsi: simplify __ata_scsi_queuecmd()
      ata: pata_of_platform: Use platform_get_irq_optional() to get the interrupt
      ata: pata_samsung_cf: add compile test support
      ata: pata_pxa: add compile test support
      ata: pata_imx: add compile test support
      ata: pata_ftide010: add compile test support
      ata: pata_cs5535: add compile test support
      ata: pata_octeon_cf: remove redundant val variable
      ata: fix read_id() ata port operation interface
      ata: ahci_xgene: use correct type for port mmio address
      ata: sata_fsl: fix cmdhdr_tbl_entry and prde struct definitions
      ata: sata_fsl: fix scsi host initialization
      ata: pata_bk3710: add compile test support
      ata: ahci_seattle: add compile test support
      ata: ahci_xgene: add compile test support
      ata: ahci_tegra: add compile test support
      ata: ahci_sunxi: add compile test support
      ...

commit 3bf6a9e36e441714928d73a5adbc59562eb7ef19
Merge: 46a10fc3a2bed b03fc43e73877
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 10:05:48 2022 +0200

    Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost
    
    Pull virtio updates from Michael Tsirkin:
     "virtio,vdpa,qemu_fw_cfg: features, cleanups, and fixes.
    
       - partial support for < MAX_ORDER - 1 granularity for virtio-mem
    
       - driver_override for vdpa
    
       - sysfs ABI documentation for vdpa
    
       - multiqueue config support for mlx5 vdpa
    
       - and misc fixes, cleanups"
    
    * tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost: (42 commits)
      vdpa/mlx5: Fix tracking of current number of VQs
      vdpa/mlx5: Fix is_index_valid() to refer to features
      vdpa: Protect vdpa reset with cf_mutex
      vdpa: Avoid taking cf_mutex lock on get status
      vdpa/vdpa_sim_net: Report max device capabilities
      vdpa: Use BIT_ULL for bit operations
      vdpa/vdpa_sim: Configure max supported virtqueues
      vdpa/mlx5: Report max device capabilities
      vdpa: Support reporting max device capabilities
      vdpa/mlx5: Restore cur_num_vqs in case of failure in change_num_qps()
      vdpa: Add support for returning device configuration information
      vdpa/mlx5: Support configuring max data virtqueue
      vdpa/mlx5: Fix config_attr_mask assignment
      vdpa: Allow to configure max data virtqueues
      vdpa: Read device configuration only if FEATURES_OK
      vdpa: Sync calls set/get config/status with cf_mutex
      vdpa/mlx5: Distribute RX virtqueues in RQT object
      vdpa: Provide interface to read driver features
      vdpa: clean up get_config_size ret value handling
      virtio_ring: mark ring unused on error
      ...

commit 46a10fc3a2beddd79dafc3cd800f14bde0844387
Merge: fc9d6952a4bbb cfcabbb24d5f4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 09:32:34 2022 +0200

    Merge tag 'rproc-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux
    
    Pull remoteproc updates from Bjorn Andersson:
     "This introduces support for controlling the Cortex R7 co-processor in
      Renesas Gen3, support for R5F clusters and C71x DSPs on TI J721S2 and
      compute, audio and modem subsystems on Qualcomm SM6350.
    
      It fixes a couple of sparse errors related to memcpy_to/fromio and
      corrects the kerneldoc spelling of "Return:".
    
      The stm32 driver no longer attempts to communicate with the remote
      after the firmware has crashed"
    
    * tag 'rproc-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux: (22 commits)
      remoteproc: stm32: Improve crash recovery time
      remoteproc: rcar_rproc: Remove trailing semicolon
      remoteproc: rcar_rproc: Fix pm_runtime_get_sync error check
      remoteproc: qcom: pas: Add SM6350 CDSP support
      remoteproc: qcom: pas: Add SM6350 ADSP support
      remoteproc: qcom: pas: Add SM6350 MPSS support
      dt-bindings: remoteproc: qcom: pas: Add SM6350 adsp, cdsp & mpss
      remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
      remoteproc: imx_rproc: correct firmware reload
      remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided
      remoteproc: Add Renesas rcar driver
      dt-bindings: remoteproc: Add Renesas R-Car
      remoteproc: Fix remaining wrong return formatting in documentation
      MAINTAINERS: Removing Ohad from remoteproc/rpmsg maintenance
      remoteproc: ingenic: Request IRQ disabled
      remoteproc: k3-r5: Extend support for R5F clusters on J721S2 SoCs
      remoteproc: k3-dsp: Extend support for C71x DSPs on J721S2 SoCs
      dt-bindings: remoteproc: k3-dsp: Update bindings for J721S2 SoCs
      dt-bindings: remoteproc: k3-r5f: Update bindings for J721S2 SoCs
      remoteproc: coredump: Correct argument 2 type for memcpy_fromio
      ...

commit fc9d6952a4bbb9908062726fbfb009fa6ea5c7af
Merge: 722d94847de29 8066c615cb69b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 09:27:40 2022 +0200

    Merge tag 'rpmsg-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux
    
    Pull rpmsg updates from Bjorn Andersson:
     "This adds pr_fmt for the rpmsg_char driver, fixes error handling in
      rpmsg_dev_probe() and corrects the spelling of "Return:" in various
      places, in order to fix kerneldoc"
    
    * tag 'rpmsg-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux:
      rpmsg: core: Clean up resources on announce_create failure.
      rpmsg: Fix documentation return formatting
      rpmsg: char: Add pr_fmt() to prefix messages

commit 722d94847de29310e8aa03fcbdb41fc92c521756
Author: Jamie Hill-Daniel <jamie@hill-daniel.co.uk>
Date:   Tue Jan 18 08:06:04 2022 +0100

    vfs: fs_context: fix up param length parsing in legacy_parse_param
    
    The "PAGE_SIZE - 2 - size" calculation in legacy_parse_param() is an
    unsigned type so a large value of "size" results in a high positive
    value instead of a negative value as expected.  Fix this by getting rid
    of the subtraction.
    
    Signed-off-by: Jamie Hill-Daniel <jamie@hill-daniel.co.uk>
    Signed-off-by: William Liu <willsroot@protonmail.com>
    Tested-by: Salvatore Bonaccorso <carnil@debian.org>
    Tested-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
    Acked-by: Dan Carpenter <dan.carpenter@oracle.com>
    Acked-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8357f6fb3d9a02ac55f0d758b9c79b4647c18bcb
Merge: 6a8d7fbf1c650 5865918fe49ed
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 09:13:30 2022 +0200

    Merge tag 'pm-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull more power management updates from Rafael Wysocki:
     "This is a continuation of the rework of device power management macros
      used for declaring device power management callbacks (Paul Cercueil)"
    
    * tag 'pm-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      iio: pressure: bmp280: Use new PM macros
      PM: runtime: Add EXPORT[_GPL]_RUNTIME_DEV_PM_OPS macros
      PM: runtime: Add DEFINE_RUNTIME_DEV_PM_OPS() macro
      PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros
      PM: core: Remove static qualifier in DEFINE_SIMPLE_DEV_PM_OPS macro
      PM: core: Remove DEFINE_UNIVERSAL_DEV_PM_OPS() macro

commit 6a8d7fbf1c65034b85e7676b42449a56e4206bd3
Merge: e3a8b6a1e70c3 e3daa2607b1f4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 08:51:51 2022 +0200

    Merge tag 'acpi-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull more ACPI updates from Rafael Wysocki:
     "The most significant item here is the Platform Firmware Runtime Update
      and Telemetry (PFRUT) support designed to allow certain pieces of the
      platform firmware to be updated on the fly, among other things.
    
      Also important is the e820 handling change on x86 that should work
      around PCI BAR allocation issues on some systems shipping since 2019.
    
      The rest is just a handful of assorted fixes and cleanups on top of
      the ACPI material merged previously.
    
      Specifics:
    
       - Add support for the the Platform Firmware Runtime Update and
         Telemetry (PFRUT) interface based on ACPI to allow certain pieces
         of the platform firmware to be updated without restarting the
         system and to provide a mechanism for collecting platform firmware
         telemetry data (Chen Yu, Dan Carpenter, Yang Yingliang).
    
       - Ignore E820 reservations covering PCI host bridge windows on
         sufficiently recent x86 systems to avoid issues with allocating PCI
         BARs on systems where the E820 reservations cover the entire PCI
         host bridge memory window returned by the _CRS object in the
         system's ACPI tables (Hans de Goede).
    
       - Fix and clean up acpi_scan_init() (Rafael Wysocki).
    
       - Add more sanity checking to ACPI SPCR tables parsing (Mark
         Langsdorf).
    
       - Fix up ACPI APD (AMD Soc) driver initialization (Jiasheng Jiang).
    
       - Drop unnecessary "static" from the ACPI PCC address space handling
         driver added recently (kernel test robot)"
    
    * tag 'acpi-5.17-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      ACPI: PCC: pcc_ctx can be static
      ACPI: scan: Rename label in acpi_scan_init()
      ACPI: scan: Simplify initialization of power and sleep buttons
      ACPI: scan: Change acpi_scan_init() return value type to void
      ACPI: SPCR: check if table->serial_port.access_width is too wide
      ACPI: APD: Check for NULL pointer after calling devm_ioremap()
      x86/PCI: Ignore E820 reservations for bridge windows on newer systems
      ACPI: pfr_telemetry: Fix info leak in pfrt_log_ioctl()
      ACPI: pfr_update: Fix return value check in pfru_write()
      ACPI: tools: Introduce utility for firmware updates/telemetry
      ACPI: Introduce Platform Firmware Runtime Telemetry driver
      ACPI: Introduce Platform Firmware Runtime Update device driver
      efi: Introduce EFI_FIRMWARE_MANAGEMENT_CAPSULE_HEADER and corresponding structures

commit 5455b9ecaf231ec5c6b0cd5c6076eb64c9dbc9aa
Author: Ronnie Sahlberg <lsahlber@redhat.com>
Date:   Tue Jan 18 12:16:57 2022 +1000

    cifs: serialize all mount attempts
    
    RHBZ: 2008434
    
    Some servers, such as Windows2016 have a very low number of concurrent mounts that
    they allow from each client.
    This can be a problem if you have a more than a handful (==3 in this case)
    of cifs entries in your fstab and cause a number of the mounts there to randomly fail.
    
    Add a global mutex and use it to serialize all mount attempts.
    
    Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e3a8b6a1e70c37702054ae3c7c07ed828435d8ee
Merge: 62b488875c055 07f910f9b7295
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 06:40:47 2022 +0200

    Merge tag 'slab-for-5.17-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab
    
    Pull more slab updates from Vlastimil Babka:
     "Finish the conversion to struct slab by removing slab-specific fields
      from struct page.
    
      The first slab update (see merge commit ca1a46d6f506) did most of the
      conversion, but there was also series in iommu tree removing the
      iommu's usage of struct page 'freelist' field, blocking the final
      struct page cleanup.
    
      Now that the iommu changes have been merged, we can finish the job"
    
    * tag 'slab-for-5.17-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab:
      mm: Remove slab from struct page

commit 62b488875c0551822ac3b961d04800d4c7a655d9
Merge: 57d17378a4a04 8f67f65d121cc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 06:36:35 2022 +0200

    Merge tag 'arc-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
    
    Pull ARC fixes from Vineet Gupta:
     "Nothing too exciting for now"
    
    * tag 'arc-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc:
      arc: use swap() to make code cleaner
      arc: perf: Move static structs to where they're really used
      ARC: perf: fix misleading comment about pmu vs counter stop
      arc: Replace lkml.org links with lore
      ARC: perf: Remove redundant initialization of variable idx
      ARC: thread_info.h: correct two typos in a comment

commit 57d17378a4a042401b0c2fe211e5a0e3a276cb3d
Merge: f0033681f0fe8 9bce13ea88f85
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 06:32:11 2022 +0200

    Merge tag 'perf-tools-for-v5.17-2022-01-16' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
    
    Pull perf tool updates from Arnaldo Carvalho de Melo:
     "New features:
    
       - Add 'trace' subcommand for 'perf ftrace', setting the stage for
         more 'perf ftrace' subcommands. Not using a subcommand yields the
         previous behaviour of 'perf ftrace'.
    
       - Add 'latency' subcommand to 'perf ftrace', that can use the
         function graph tracer or a BPF optimized one, via the -b/--use-bpf
         option.
    
         E.g.:
    
            $ sudo perf ftrace latency -a -T mutex_lock sleep 1
            #   DURATION     |      COUNT | GRAPH                          |
                 0 - 1    us |       4596 | ########################       |
                 1 - 2    us |       1680 | #########                      |
                 2 - 4    us |       1106 | #####                          |
                 4 - 8    us |        546 | ##                             |
                 8 - 16   us |        562 | ###                            |
                16 - 32   us |          1 |                                |
                32 - 64   us |          0 |                                |
                64 - 128  us |          0 |                                |
               128 - 256  us |          0 |                                |
               256 - 512  us |          0 |                                |
               512 - 1024 us |          0 |                                |
                 1 - 2    ms |          0 |                                |
                 2 - 4    ms |          0 |                                |
                 4 - 8    ms |          0 |                                |
                 8 - 16   ms |          0 |                                |
                16 - 32   ms |          0 |                                |
                32 - 64   ms |          0 |                                |
                64 - 128  ms |          0 |                                |
               128 - 256  ms |          0 |                                |
               256 - 512  ms |          0 |                                |
               512 - 1024 ms |          0 |                                |
                 1 - ...   s |          0 |                                |
    
         The original implementation of this command was in the bcc tool.
    
       - Support --cputype option for hybrid events in 'perf stat'.
    
      Improvements:
    
       - Call chain improvements for ARM64.
    
       - No need to do any affinity setup when profiling pids.
    
       - Reduce multiplexing with duration_time in 'perf stat' metrics.
    
       - Improve error message for uncore events, stating that some event
         groups are can only be used in system wide (-a) mode.
    
       - perf stat metric group leader fixes/improvements, including arch
         specific changes to better support Intel topdown events.
    
       - Probe non-deprecated sysfs path first, i.e. try the path
         /sys/devices/system/cpu/cpuN/topology/thread_siblings first, then
         the old /sys/devices/system/cpu/cpuN/topology/core_cpus.
    
       - Disable debuginfod by default in 'perf record', to avoid stalls on
         distros such as Fedora 35.
    
       - Use unbuffered output in 'perf bench' when pipe/tee'ing to a file.
    
       - Enable ignore_missing_thread in 'perf trace'
    
      Fixes:
    
       - Avoid TUI crash when navigating in the annotation of recursive
         functions.
    
       - Fix hex dump character output in 'perf script'.
    
       - Fix JSON indentation to 4 spaces standard in the ARM vendor event
         files.
    
       - Fix use after free in metric__new().
    
       - Fix IS_ERR_OR_NULL() usage in the perf BPF loader.
    
       - Fix up cross-arch register support, i.e. when printing register
         names take into account the architecture where the perf.data file
         was collected.
    
       - Fix SMT fallback with large core counts.
    
       - Don't lower case MetricExpr when parsing JSON files so as not to
         lose info such as the ":G" event modifier in metrics.
    
      perf test:
    
       - Add basic stress test for sigtrap handling to 'perf test'.
    
       - Fix 'perf test' failures on s/390
    
       - Enable system wide for metricgroups test in 'perf test´.
    
       - Use 3 digits for test numbering now we can have more tests.
    
      Arch specific:
    
       - Add events for Arm Neoverse N2 in the ARM JSON vendor event files
    
       - Support PERF_MEM_LVLNUM encodings in powerpc, that came from a
         single patch series, where I incorrectly merged the kernel bits,
         that were then reverted after coordination with Michael Ellerman
         and Stephen Rothwell.
    
       - Add ARM SPE total latency as PERF_SAMPLE_WEIGHT.
    
       - Update AMD documentation, with info on raw event encoding.
    
       - Add support for global and local variants of the "p_stage_cyc" sort
         key, applicable to perf.data files collected on powerpc.
    
       - Remove duplicate and incorrect aux size checks in the ARM CoreSight
         ETM code.
    
      Refactorings:
    
       - Add a perf_cpu abstraction to disambiguate CPUs and CPU map
         indexes, fixing problems along the way.
    
       - Document CPU map methods.
    
      UAPI sync:
    
       - Update arch/x86/lib/mem{cpy,set}_64.S copies used in 'perf bench
         mem memcpy'
    
       - Sync UAPI files with the kernel sources: drm, msr-index,
         cpufeatures.
    
      Build system
    
       - Enable warnings through HOSTCFLAGS.
    
       - Drop requirement for libstdc++.so for libopencsd check
    
      libperf:
    
       - Make libperf adopt perf_counts_values__scale() from tools/perf/util/.
    
       - Add a stat multiplexing test to libperf"
    
    * tag 'perf-tools-for-v5.17-2022-01-16' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux: (115 commits)
      perf record: Disable debuginfod by default
      perf evlist: No need to do any affinity setup when profiling pids
      perf cpumap: Add is_dummy() method
      perf metric: Fix metric_leader
      perf cputopo: Fix CPU topology reading on s/390
      perf metricgroup: Fix use after free in metric__new()
      libperf tests: Update a use of the new cpumap API
      perf arm: Fix off-by-one directory path
      tools arch x86: Sync the msr-index.h copy with the kernel sources
      tools headers cpufeatures: Sync with the kernel sources
      tools headers UAPI: Update tools's copy of drm.h header
      tools arch: Update arch/x86/lib/mem{cpy,set}_64.S copies used in 'perf bench mem memcpy'
      perf pmu-events: Don't lower case MetricExpr
      perf expr: Add debug logging for literals
      perf tools: Probe non-deprecated sysfs path 1st
      perf tools: Fix SMT fallback with large core counts
      perf cpumap: Give CPUs their own type
      perf stat: Correct first_shadow_cpu to return index
      perf script: Fix flipped index and cpu
      perf c2c: Use more intention revealing iterator
      ...

commit f0033681f0fe8421baf8db125e57fa6157824c2d
Merge: 0c947b893d692 40a74870b2d1d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 18 06:26:50 2022 +0200

    Merge tag 'for-linus-5.17-ofs-1' of git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux
    
    Pull orangefs fixes from Mike Marshall:
     "Two fixes:
    
       - Fix the size of a memory allocation in orangefs_bufmap_alloc()
         (Christophe JAILLET)
    
       - Use default_groups in kobj_type (Greg KH)"
    
    * tag 'for-linus-5.17-ofs-1' of git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux:
      orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
      orangefs: use default_groups in kobj_type

commit aee101d7b95a03078945681dd7f7ea5e4a1e7686
Author: Nicholas Piggin <npiggin@gmail.com>
Date:   Mon Jan 17 23:44:03 2022 +1000

    powerpc/64s: Mask SRR0 before checking against the masked NIP
    
    Commit 314f6c23dd8d ("powerpc/64s: Mask NIP before checking against
    SRR0") masked off the low 2 bits of the NIP value in the interrupt
    stack frame in case they are non-zero and mis-compare against a SRR0
    register value of a CPU which always reads back 0 from the 2 low bits
    which are reserved.
    
    This now causes the opposite problem that an implementation which does
    implement those bits in SRR0 will mis-compare against the masked NIP
    value in which they have been cleared. QEMU is one such implementation,
    and this is allowed by the architecture.
    
    This can be triggered by sigfuz by setting low bits of PT_NIP in the
    signal context.
    
    Fix this for now by masking the SRR0 bits as well. Cleaner is probably
    to sanitise these values before putting them in registers or stack, but
    this is the quick and backportable fix.
    
    Fixes: 314f6c23dd8d ("powerpc/64s: Mask NIP before checking against SRR0")
    Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220117134403.2995059-1-npiggin@gmail.com

commit eee412e968f7b950564880bc6a7a9f00f49034da
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Fri Jan 14 17:13:38 2022 -0800

    remoteproc: qcom: q6v5: fix service routines build errors
    
    When CONFIG_QCOM_AOSS_QMP=m and CONFIG_QCOM_Q6V5_MSS=y, the builtin
    driver cannot call into the loadable module's low-level service
    functions. Trying to build with that config combo causes linker errors.
    
    There are two problems here. First, drivers/remoteproc/qcom_q6v5.c
    should #include <linux/soc/qcom/qcom_aoss.h> for the definitions of
    the service functions, depending on whether CONFIG_QCOM_AOSS_QMP is
    set/enabled or not. Second, the qcom remoteproc drivers should depend
    on QCOM_AOSS_QMP iff it is enabled (=y or =m) so that the qcom
    remoteproc drivers can be built properly.
    
    This prevents these build errors:
    
    aarch64-linux-ld: drivers/remoteproc/qcom_q6v5.o: in function `q6v5_load_state_toggle':
    qcom_q6v5.c:(.text+0xc4): undefined reference to `qmp_send'
    aarch64-linux-ld: drivers/remoteproc/qcom_q6v5.o: in function `qcom_q6v5_deinit':
    (.text+0x2e4): undefined reference to `qmp_put'
    aarch64-linux-ld: drivers/remoteproc/qcom_q6v5.o: in function `qcom_q6v5_init':
    (.text+0x778): undefined reference to `qmp_get'
    aarch64-linux-ld: (.text+0x7d8): undefined reference to `qmp_put'
    
    Fixes: c1fe10d238c0 ("remoteproc: qcom: q6v5: Use qmp_send to update co-processor load state")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: linux-remoteproc@vger.kernel.org
    Cc: Sibi Sankar <sibis@codeaurora.org>
    Cc: Stephen Boyd <swboyd@chromium.org>
    Reviewed-by: Stephen Boyd <swboyd@chromium.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20220115011338.2973-1-rdunlap@infradead.org

commit 7a534ae89e34e9b51acb5a63dd0f88308178b46a
Author: Matthias Kaehlcke <mka@chromium.org>
Date:   Mon Jan 10 10:47:37 2022 -0800

    rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev
    
    struct rpmsg_eptdev contains a struct cdev. The current code frees
    the rpmsg_eptdev struct in rpmsg_eptdev_destroy(), but the cdev is
    a managed object, therefore its release is not predictable and the
    rpmsg_eptdev could be freed before the cdev is entirely released.
    
    The cdev_device_add/del() API was created to address this issue
    (see commit '233ed09d7fda ("chardev: add helper function to register
    char devs with a struct device")'), use it instead of cdev add/del().
    
    Fixes: c0cdc19f84a4 ("rpmsg: Driver for user space endpoint interface")
    Suggested-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
    Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
    Reviewed-by: Stephen Boyd <swboyd@chromium.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20220110104706.v6.2.Idde68b05b88d4a2e6e54766c653f3a6d9e419ce6@changeid

commit b7fb2dad571d1e21173c06cef0bced77b323990a
Author: Sujit Kautkar <sujitka@chromium.org>
Date:   Mon Jan 10 10:47:36 2022 -0800

    rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev
    
    struct rpmsg_ctrldev contains a struct cdev. The current code frees
    the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the
    cdev is a managed object, therefore its release is not predictable
    and the rpmsg_ctrldev could be freed before the cdev is entirely
    released, as in the backtrace below.
    
    [   93.625603] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x7c
    [   93.636115] WARNING: CPU: 0 PID: 12 at lib/debugobjects.c:488 debug_print_object+0x13c/0x1b0
    [   93.644799] Modules linked in: veth xt_cgroup xt_MASQUERADE rfcomm algif_hash algif_skcipher af_alg uinput ip6table_nat fuse uvcvideo videobuf2_vmalloc venus_enc venus_dec videobuf2_dma_contig hci_uart btandroid btqca snd_soc_rt5682_i2c bluetooth qcom_spmi_temp_alarm snd_soc_rt5682v
    [   93.715175] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G    B             5.4.163-lockdep #26
    [   93.723855] Hardware name: Google Lazor (rev3 - 8) with LTE (DT)
    [   93.730055] Workqueue: events kobject_delayed_cleanup
    [   93.735271] pstate: 60c00009 (nZCv daif +PAN +UAO)
    [   93.740216] pc : debug_print_object+0x13c/0x1b0
    [   93.744890] lr : debug_print_object+0x13c/0x1b0
    [   93.749555] sp : ffffffacf5bc7940
    [   93.752978] x29: ffffffacf5bc7940 x28: dfffffd000000000
    [   93.758448] x27: ffffffacdb11a800 x26: dfffffd000000000
    [   93.763916] x25: ffffffd0734f856c x24: dfffffd000000000
    [   93.769389] x23: 0000000000000000 x22: ffffffd0733c35b0
    [   93.774860] x21: ffffffd0751994a0 x20: ffffffd075ec27c0
    [   93.780338] x19: ffffffd075199100 x18: 00000000000276e0
    [   93.785814] x17: 0000000000000000 x16: dfffffd000000000
    [   93.791291] x15: ffffffffffffffff x14: 6e6968207473696c
    [   93.796768] x13: 0000000000000000 x12: ffffffd075e2b000
    [   93.802244] x11: 0000000000000001 x10: 0000000000000000
    [   93.807723] x9 : d13400dff1921900 x8 : d13400dff1921900
    [   93.813200] x7 : 0000000000000000 x6 : 0000000000000000
    [   93.818676] x5 : 0000000000000080 x4 : 0000000000000000
    [   93.824152] x3 : ffffffd0732a0fa4 x2 : 0000000000000001
    [   93.829628] x1 : ffffffacf5bc7580 x0 : 0000000000000061
    [   93.835104] Call trace:
    [   93.837644]  debug_print_object+0x13c/0x1b0
    [   93.841963]  __debug_check_no_obj_freed+0x25c/0x3c0
    [   93.846987]  debug_check_no_obj_freed+0x18/0x20
    [   93.851669]  slab_free_freelist_hook+0xbc/0x1e4
    [   93.856346]  kfree+0xfc/0x2f4
    [   93.859416]  rpmsg_ctrldev_release_device+0x78/0xb8
    [   93.864445]  device_release+0x84/0x168
    [   93.868310]  kobject_cleanup+0x12c/0x298
    [   93.872356]  kobject_delayed_cleanup+0x10/0x18
    [   93.876948]  process_one_work+0x578/0x92c
    [   93.881086]  worker_thread+0x804/0xcf8
    [   93.884963]  kthread+0x2a8/0x314
    [   93.888303]  ret_from_fork+0x10/0x18
    
    The cdev_device_add/del() API was created to address this issue (see
    commit '233ed09d7fda ("chardev: add helper function to register char
    devs with a struct device")'), use it instead of cdev add/del().
    
    Fixes: c0cdc19f84a4 ("rpmsg: Driver for user space endpoint interface")
    Signed-off-by: Sujit Kautkar <sujitka@chromium.org>
    Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
    Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
    Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Reviewed-by: Stephen Boyd <swboyd@chromium.org>
    Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
    Link: https://lore.kernel.org/r/20220110104706.v6.1.Iaac908f3e3149a89190ce006ba166e2d3fd247a3@changeid

commit d8adf5b92a9d2205620874d498c39923ecea8749
Author: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Date:   Thu Jan 13 09:19:18 2022 +0100

    scripts/dtc: dtx_diff: remove broken example from help text
    
    dtx_diff suggests to use <(...) syntax to pipe two inputs into it, but
    this has never worked: The /proc/self/fds/... paths passed by the shell
    will fail the `[ -f "${dtx}" ] && [ -r "${dtx}" ]` check in compile_to_dts,
    but even with this check removed, the function cannot work: hexdump will
    eat up the DTB magic, making the subsequent dtc call fail, as a pipe
    cannot be rewound.
    
    Simply remove this broken example, as there is already an alternative one
    that works fine.
    
    Fixes: 10eadc253ddf ("dtc: create tool to diff device trees")
    Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
    Reviewed-by: Frank Rowand <frank.rowand@sony.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113081918.10387-1-matthias.schiffer@ew.tq-group.com

commit af35a8b5bab7c1e31d30b9ad78a981fae9bda903
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 14:39:20 2022 +0100

    dt-bindings: trivial-devices: fix double spaces in comments
    
    Cleanup double spaces in some of the comments.
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/13b3f66efd3b20f1d9bbb9eff1eca00757ac5367.1642080090.git.stano.jakubek@gmail.com

commit 154e5f296e2af04fc2775a6de3c76e6ee37b5609
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 14:39:01 2022 +0100

    dt-bindings: trivial-devices: fix swapped comments
    
    sparkfun,qwiic-joystick and st,24c256 had their comments incorrectly
    swapped. Swap them to make them correct.
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/7dc6ddb0b042cd243b2875e9aea81cad541d1c6b.1642080090.git.stano.jakubek@gmail.com

commit 364da22cb30eb79198922ebf53c40f589bcece9d
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 11:31:10 2022 +0100

    dt-bindings: vendor-prefixes: add Wingtech
    
    The vendor prefix for Wingtech [1] is used in device tree [2], but was
    not documented so far. Add it to the schema to document it.
    
    [1] http://www.wingtech.com/en
    [2] arch/arm64/boot/dts/qcom/msm8916-wingtech-wt88047.dts
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113103110.GA4488@standask-GA-A55M-S2HP

commit 6f2dfed0b6f078149072c34631a77902a8c85c7e
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 11:30:36 2022 +0100

    dt-bindings: vendor-prefixes: add Thundercomm
    
    The vendor prefix for Thundercomm [1] is used in device tree [2], but
    was not documented so far. Add it to the schema to document it.
    
    [1] https://www.thundercomm.com/
    [2] arch/arm64/boot/dts/qcom/sdm845-db845c.dts
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113103036.GA4456@standask-GA-A55M-S2HP

commit ca146834d6cdbde80dead9daf8e7e127fc85d31f
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 11:30:05 2022 +0100

    dt-bindings: vendor-prefixes: add Huawei
    
    The vendor prefix for Huawei [1] is used in device trees [2][3], but was
    not documented so far. Add it to the schema to document it.
    
    [1] https://www.huawei.com/en/
    [2] arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts
    [3] arch/arm64/boot/dts/qcom/msm8994-angler-rev-101.dts
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113103005.GA4421@standask-GA-A55M-S2HP

commit 8316cbbafd8bdf523fb1b3230f0701beae51679b
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 11:29:26 2022 +0100

    dt-bindings: vendor-prefixes: add F(x)tec
    
    The vendor prefix for F(x)tec [1] is used in device tree [2], but was
    not documented so far. Add it to the schema to document it.
    
    [1] https://www.fxtec.com/
    [2] arch/arm64/boot/dts/qcom/msm8998-fxtec-pro1.dts
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113102926.GA4388@standask-GA-A55M-S2HP

commit 38a9840e2e396e86e3a39d1d2daf5f46204066c7
Author: Stanislav Jakubek <stano.jakubek@gmail.com>
Date:   Thu Jan 13 11:28:42 2022 +0100

    dt-bindings: vendor-prefixes: add 8devices
    
    The vendor prefix for 8devices [1] is used in device tree [2], but was
    not documented so far. Add it to the schema to document it.
    
    [1] https://www.8devices.com/
    [2] arch/arm/boot/dts/qcom-ipq4018-jalapeno.dts
    
    Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220113102842.GA4357@standask-GA-A55M-S2HP

commit 2ba144e68edb4987a2fe1b1cf418b58cbdc4ee96
Author: Sander Vanheule <sander@svanheule.net>
Date:   Mon Jan 10 22:44:56 2022 +0100

    dt-bindings: power: reset: gpio-restart: Correct default priority
    
    Commit bcd56fe1aa97 ("power: reset: gpio-restart: increase priority
    slightly") changed the default restart priority 129, but did not update
    the documentation. Correct this, so the driver and documentation have
    the same default value.
    
    Signed-off-by: Sander Vanheule <sander@svanheule.net>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220110214456.67087-1-sander@svanheule.net

commit cc2cf6796a90bf356a8ddc854f65cea434477ea7
Author: Huichun Feng <foxhoundsk.tw@gmail.com>
Date:   Tue Jan 11 13:20:01 2022 +0800

    docs: ftrace: fix ambiguous sentence
    
    The sentence looks ambiguous, rephrase it by adding ", there".
    
    Signed-off-by: Huichun Feng <foxhoundsk.tw@gmail.com>
    Signed-off-by: Ching-Chun (Jim) Huang <jserv@ccns.ncku.edu.tw>
    Signed-off-by: Chun-Hung Tseng <henrybear327@gmail.com>
    Acked-by: Steven Rostedt <rostedt@goodmis.org>
    Link: https://lore.kernel.org/r/20220111052000.2675944-1-foxhoundsk.tw@gmail.com
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 6b0764598dc7dea21a44cd4e7ec3dd4a7aabf5c2
Author: Wang Cheng <wanngchenng@gmail.com>
Date:   Sat Jan 15 20:52:36 2022 +0800

    docs: staging/tee.rst: fix two typos found while reading
    
    Signed-off-by: Wang Cheng <wanngchenng@gmail.com>
    Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Link: https://lore.kernel.org/r/20220115125236.34886-1-wanngchenng@gmail.com
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit a2809d0e16963fdf3984409e47f145cccb0c6821
Author: Eugene Korenevsky <ekorenevsky@astralinux.ru>
Date:   Fri Jan 14 22:53:40 2022 +0300

    cifs: quirk for STATUS_OBJECT_NAME_INVALID returned for non-ASCII dfs refs
    
    Windows SMB server responds with STATUS_OBJECT_NAME_INVALID code to
    SMB2 QUERY_INFO request for "\<server>\<dfsname>\<linkpath>" DFS reference,
    where <dfsname> contains non-ASCII unicode symbols.
    
    Check such DFS reference and emulate -EREMOTE if it is actual.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215440
    Signed-off-by: Eugene Korenevsky <ekorenevsky@astralinux.ru>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 7eacba3b00a3c35c1ad189f543b1995dd0bdca9c
Author: Eugene Korenevsky <ekorenevsky@astralinux.ru>
Date:   Fri Jan 14 22:53:00 2022 +0300

    cifs: alloc_path_with_tree_prefix: do not append sep. if the path is empty
    
    alloc_path_with_tree_prefix() concatenates tree prefix and the path.
    Windows CIFS client does not add separator after the tree prefix if the path
    is empty. Let's do the same.
    
    This fixes mounting DFS namespaces with names containing non-ASCII symbols.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215440
    Signed-off-by: Eugene Korenevsky <ekorenevsky@astralinux.ru>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e5b54867f47f765fcb439e09ed763b5de617af3e
Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Date:   Fri Jan 14 15:24:35 2022 -0800

    thermal: int340x: Add Raptor Lake PCI device id
    
    Add Raptor Lake PCI ID for processor thermal device.
    
    Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit a95be874d26bed7c12a87b5493d5dac9281f707f
Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Date:   Fri Jan 14 15:24:34 2022 -0800

    thermal: int340x: Support Raptor Lake
    
    Add Raptor Lake ACPI IDs for DPTF devices.
    
    Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit a510c78e5b6f2f9b9add88071fdfc2b740d2e356
Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Date:   Fri Jan 14 15:24:33 2022 -0800

    ACPI: DPTF: Support Raptor Lake
    
    Add Raptor Lake ACPI IDs for DPTF devices.
    
    Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit f684b10751287e8b7e15e8f10ae40bdd74149bba
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Jan 12 19:27:22 2022 +0100

    ACPI: CPPC: Drop redundant local variable from cpc_read()
    
    The ret_val local variable in cpc_read() is not necessary, so
    eliminate it.
    
    No functional impact.
    
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Acked-by: Huang Rui <ray.huang@amd.com>

commit 5f51c7ce1dc36565296b3ef342585f70ec72a2a9
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Wed Jan 12 19:26:32 2022 +0100

    ACPI: CPPC: Fix up I/O port access in cpc_read()
    
    The code as currently implemented does not work on big endian systems,
    so fix it up.
    
    Fixes: a2c8f92bea5f ("ACPI: CPPC: Implement support for SystemIO registers")
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Suggested-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/linux-acpi/20220111092928.GA24968@kili/
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Acked-by: Huang Rui <ray.huang@amd.com>

commit 74ce6135ae6ef482715cff2ccd703b7295f900f2
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Mon Jan 17 09:11:30 2022 +0800

    cifs: clean up an inconsistent indenting
    
    Eliminate the follow smatch warning:
    fs/cifs/sess.c:1581 sess_auth_rawntlmssp_authenticate() warn:
    inconsistent indenting
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit e3548aaf41a200c2af359462be23bcdd76efd795
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Mon Jan 17 00:20:47 2022 -0600

    cifs: free ntlmsspblob allocated in negotiate
    
    One of my previous fixes:
    cifs: send workstation name during ntlmssp session setup
    ...changed the prototype of build_ntlmssp_negotiate_blob
    from being allocated by the caller to being allocated within
    the function. The caller needs to free this object too.
    While SMB2 version of the caller did it, I forgot to free
    for the SMB1 version. Fixing that here.
    
    Fixes: 49bd49f983b5 ("cifs: send workstation name during ntlmssp session setup")
    Cc: stable@vger.kernel.org # 5.16
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 4732f2444acd9b7eabc744f20eb5cc9694c0bfbd
Author: Like Xu <likexu@tencent.com>
Date:   Tue Jan 11 15:38:23 2022 +0800

    KVM: x86: Making the module parameter of vPMU more common
    
    The new module parameter to control PMU virtualization should apply
    to Intel as well as AMD, for situations where userspace is not trusted.
    If the module parameter allows PMU virtualization, there could be a
    new KVM_CAP or guest CPUID bits whereby userspace can enable/disable
    PMU virtualization on a per-VM basis.
    
    If the module parameter does not allow PMU virtualization, there
    should be no userspace override, since we have no precedent for
    authorizing that kind of override. If it's false, other counter-based
    profiling features (such as LBR including the associated CPUID bits
    if any) will not be exposed.
    
    Change its name from "pmu" to "enable_pmu" as we have temporary
    variables with the same name in our code like "struct kvm_pmu *pmu".
    
    Fixes: b1d66dad65dc ("KVM: x86/svm: Add module param to control PMU virtualization")
    Suggested-by : Jim Mattson <jmattson@google.com>
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20220111073823.21885-1-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ecebb966acaab2466d9857d1cc435ee1fc9eee50
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Jan 17 16:05:42 2022 +0100

    KVM: selftests: Test KVM_SET_CPUID2 after KVM_RUN
    
    KVM forbids KVM_SET_CPUID2 after KVM_RUN was performed on a vCPU unless
    the supplied CPUID data is equal to what was previously set. Test this.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220117150542.2176196-5-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 9e6d484f9991176269607bb3c54a494e32eab27a
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Jan 17 16:05:41 2022 +0100

    KVM: selftests: Rename 'get_cpuid_test' to 'cpuid_test'
    
    In preparation to reusing the existing 'get_cpuid_test' for testing
    "KVM_SET_CPUID{,2} after KVM_RUN" rename it to 'cpuid_test' to avoid
    the confusion.
    
    No functional change intended.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220117150542.2176196-4-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c6617c61e8fe44b9e9fdfede921f61cac6b5149d
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Jan 17 16:05:40 2022 +0100

    KVM: x86: Partially allow KVM_SET_CPUID{,2} after KVM_RUN
    
    Commit feb627e8d6f6 ("KVM: x86: Forbid KVM_SET_CPUID{,2} after KVM_RUN")
    forbade changing CPUID altogether but unfortunately this is not fully
    compatible with existing VMMs. In particular, QEMU reuses vCPU fds for
    CPU hotplug after unplug and it calls KVM_SET_CPUID2. Instead of full ban,
    check whether the supplied CPUID data is equal to what was previously set.
    
    Reported-by: Igor Mammedov <imammedo@redhat.com>
    Fixes: feb627e8d6f6 ("KVM: x86: Forbid KVM_SET_CPUID{,2} after KVM_RUN")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220117150542.2176196-3-vkuznets@redhat.com>
    Cc: stable@vger.kernel.org
    [Do not call kvm_find_cpuid_entry repeatedly. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit e3daa2607b1f4bb1d09a5a8ad89ad9f7327a2e63
Merge: ebf8b135c04ae 7bf2e4d5ca1c9
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 17 18:25:57 2022 +0100

    Merge branch 'acpi-pfrut'
    
    Merge support for the Platform Firmware Runtime Update and Telemetry
    interface based on ACPI.
    
    The interface provided here allows updating certain pieces of the
    platform firmware without restarting the system and collecting
    platform firmware telemetry data.
    
    This also includes a utility for accesing the new interface from user
    space.
    
    * acpi-pfrut:
      ACPI: pfr_telemetry: Fix info leak in pfrt_log_ioctl()
      ACPI: pfr_update: Fix return value check in pfru_write()
      ACPI: tools: Introduce utility for firmware updates/telemetry
      ACPI: Introduce Platform Firmware Runtime Telemetry driver
      ACPI: Introduce Platform Firmware Runtime Update device driver
      efi: Introduce EFI_FIRMWARE_MANAGEMENT_CAPSULE_HEADER and corresponding structures

commit ee3a5f9e3d9bf94159f3cc80da542fbe83502dd8
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Mon Jan 17 16:05:39 2022 +0100

    KVM: x86: Do runtime CPUID update before updating vcpu->arch.cpuid_entries
    
    kvm_update_cpuid_runtime() mangles CPUID data coming from userspace
    VMM after updating 'vcpu->arch.cpuid_entries', this makes it
    impossible to compare an update with what was previously
    supplied. Introduce __kvm_update_cpuid_runtime() version which can be
    used to tweak the input before it goes to 'vcpu->arch.cpuid_entries'
    so the upcoming update check can compare tweaked data.
    
    No functional change intended.
    
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Message-Id: <20220117150542.2176196-2-vkuznets@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a21864486f7e220bd5938c6fb637613d9635739a
Author: Like Xu <likexu@tencent.com>
Date:   Wed Jan 5 13:15:09 2022 +0800

    KVM: x86/pmu: Fix available_event_types check for REF_CPU_CYCLES event
    
    According to CPUID 0x0A.EBX bit vector, the event [7] should be the
    unrealized event "Topdown Slots" instead of the *kernel* generalized
    common hardware event "REF_CPU_CYCLES", so we need to skip the cpuid
    unavaliblity check in the intel_pmc_perf_hw_id() for the last
    REF_CPU_CYCLES event and update the confusing comment.
    
    If the event is marked as unavailable in the Intel guest CPUID
    0AH.EBX leaf, we need to avoid any perf_event creation, whether
    it's a gp or fixed counter. To distinguish whether it is a rejected
    event or an event that needs to be programmed with PERF_TYPE_RAW type,
    a new special returned value of "PERF_COUNT_HW_MAX + 1" is introduced.
    
    Fixes: 62079d8a43128 ("KVM: PMU: add proper support for fixed counter 2")
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20220105051509.69437-1-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b3bb9413e717b44e4aea833d07f14e90fb91cf97
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Tue Dec 21 13:07:38 2021 -0800

    xfs: remove the XFS_IOC_{ALLOC,FREE}SP* definitions
    
    Now that we've made these ioctls defunct, move them from xfs_fs.h to
    xfs_ioctl.c, which effectively removes them from the publicly supported
    ioctl interfaces for XFS.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Eric Sandeen <sandeen@redhat.com>

commit 4d1b97f9ce7c0d2af2bb85b12d48e6902172a28e
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Fri Jan 7 17:45:51 2022 -0800

    xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls
    
    According to the glibc compat header for Irix 4, these ioctls originated
    in April 1991 as a (somewhat clunky) way to preallocate space at the end
    of a file on an EFS filesystem.  XFS, which was released in Irix 5.3 in
    December 1993, picked up these ioctls to maintain compatibility and they
    were ported to Linux in the early 2000s.
    
    Recently it was pointed out to me they still lurk in the kernel, even
    though the Linux fallocate syscall supplanted the functionality a long
    time ago.  fstests doesn't seem to include any real functional or stress
    tests for these ioctls, which means that the code quality is ... very
    questionable.  Most notably, it was a stale disk block exposure vector
    for 21 years and nobody noticed or complained.  As mature programmers
    say, "If you're not testing it, it's broken."
    
    Given all that, let's withdraw these ioctls from the XFS userspace API.
    Normally we'd set a long deprecation process, but I estimate that there
    aren't any real users, so let's trigger a warning in dmesg and return
    -ENOTTY.
    
    See: CVE-2021-4155
    
    Augments: 983d8e60f508 ("xfs: map unwritten blocks in XFS_IOC_{ALLOC,FREE}SP just like fallocate")
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Eric Sandeen <sandeen@redhat.com>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit 9dec0368b9640c09ef5af48214e097245e57a204
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Tue Jan 11 14:05:02 2022 -0800

    xfs: remove the XFS_IOC_FSSETDM definitions
    
    Remove the definitions for these ioctls, since the functionality (and,
    weirdly, the 32-bit compat ioctl definitions) were removed from the
    kernel in November 2019.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit ebf8b135c04ae5481fc053ecb9fad66b26fd1112
Merge: c96f195deeefe 7f7b4236f2040 ee3fe99ff0a27 2cea3ec5b0099 415b4b6c447ae
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 17 18:15:07 2022 +0100

    Merge branches 'acpi-x86', 'acpi-tables', 'acpi-soc' and 'acpi-pcc'
    
    Merge additional ACPI-related updates for 5.17-rc1:
    
     - Ignore E820 reservations covering PCI host bridge windows on
       sufficiently recent x86 systems to avoid issues with allocating
       PCI BARs on systems where the E820 reservations cover the entire
       PCI host bridge memory window returned by the _CRS object in the
       system's ACPI tables (Hans de Goede).
    
     - Add more sanity checking to ACPI SPCR tables parsing (Mark
       Langsdorf).
    
     - Fix up ACPI APD (AMD Soc) driver initialization (Jiasheng Jiang).
    
     - Drop unnecessary "static" from the ACPI PCC address space handling
       driver added recently (kernel test robot).
    
    * acpi-x86:
      x86/PCI: Ignore E820 reservations for bridge windows on newer systems
    
    * acpi-tables:
      ACPI: SPCR: check if table->serial_port.access_width is too wide
    
    * acpi-soc:
      ACPI: APD: Check for NULL pointer after calling devm_ioremap()
    
    * acpi-pcc:
      ACPI: PCC: pcc_ctx can be static

commit 5765cee119bf5a36c94d20eceb37c445508934be
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Mon Jan 17 14:52:33 2022 +0000

    net: sfp: fix high power modules without diagnostic monitoring
    
    Commit 7cfa9c92d0a3 ("net: sfp: avoid power switch on address-change
    modules") unintetionally changed the semantics for high power modules
    without the digital diagnostics monitoring. We repeatedly attempt to
    read the power status from the non-existing 0xa2 address in a futile
    hope this failure is temporary:
    
    [    8.856051] sfp sfp-eth3: module NTT              0000000000000000 rev 0000  sn 0000000000000000 dc 160408
    [    8.865843] mvpp2 f4000000.ethernet eth3: switched to inband/1000base-x link mode
    [    8.873469] sfp sfp-eth3: Failed to read EEPROM: -5
    [    8.983251] sfp sfp-eth3: Failed to read EEPROM: -5
    [    9.103250] sfp sfp-eth3: Failed to read EEPROM: -5
    
    We previosuly assumed such modules were powered up in the correct mode,
    continuing without further configuration as long as the required power
    class was supported by the host.
    
    Restore this behaviour, while preserving the intent of subsequent
    patches to avoid the "Address Change Sequence not supported" warning
    if we are not going to be accessing the DDM address.
    
    Fixes: 7cfa9c92d0a3 ("net: sfp: avoid power switch on address-change modules")
    Reported-by: 照山周一郎 <teruyama@springboard-inc.jp>
    Tested-by: 照山周一郎 <teruyama@springboard-inc.jp>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 850fd2abbe02eb2b52cbb1550adbcc89b36d65de
Author: Ming Lei <ming.lei@redhat.com>
Date:   Tue Jan 11 20:34:01 2022 +0800

    block: cleanup q->srcu
    
    srcu structure has to be cleanup via cleanup_srcu_struct(), so fix it.
    
    Reported-by: syzbot+4f789823c1abc5accf13@syzkaller.appspotmail.com
    Fixes: 704b914f15fb ("blk-mq: move srcu from blk_mq_hw_ctx to request_queue")
    Signed-off-by: Ming Lei <ming.lei@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lore.kernel.org/r/20220111123401.520192-1-ming.lei@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit e6a2e5116e07ce5acc8698785c29e9e47f010fd5
Author: GuoYong Zheng <zhenggy@chinatelecom.cn>
Date:   Mon Jan 17 18:22:37 2022 +0800

    block: Remove unnecessary variable assignment
    
    The parameter "ret" should be zero when running to this line,
    no need to set to zero again, remove it.
    
    Signed-off-by: GuoYong Zheng <zhenggy@chinatelecom.cn>
    Link: https://lore.kernel.org/r/1642414957-6785-1-git-send-email-zhenggy@chinatelecom.cn
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 00358933f66c44d511368a57eb421e172447cfb9
Author: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Date:   Thu Jan 6 18:53:16 2022 +0900

    brd: remove brd_devices_mutex mutex
    
    If brd_alloc() from brd_probe() is called before brd_alloc() from
    brd_init() is called, module loading will fail with -EEXIST error.
    To close this race, call __register_blkdev() just before leaving
    brd_init().
    
    Then, we can remove brd_devices_mutex mutex, for brd_device list
    will no longer be accessed concurrently.
    
    Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
    Link: https://lore.kernel.org/r/6b074af7-c165-4fab-b7da-8270a4f6f6cd@i-love.sakura.ne.jp
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 30fee1d7462a446ade399c0819717a830cbdca69
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 14 06:51:24 2022 +0000

    gpio: idt3243x: Fix IRQ check in idt_gpio_probe
    
    platform_get_irq() returns negative error number instead 0 on failure.
    And the doc of platform_get_irq() provides a usage example:
    
        int irq = platform_get_irq(pdev, 0);
        if (irq < 0)
            return irq;
    
    Fix the check of return value to catch errors correctly.
    
    Fixes: 4195926aedca ("gpio: Add support for IDT 79RC3243x GPIO controller")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit 0b39536cc699db6850c426db7f9cb45923de40c5
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 14 06:48:20 2022 +0000

    gpio: mpc8xxx: Fix IRQ check in mpc8xxx_probe
    
    platform_get_irq() returns negative error number instead 0 on failure.
    And the doc of platform_get_irq() provides a usage example:
    
        int irq = platform_get_irq(pdev, 0);
        if (irq < 0)
            return irq;
    
    Fix the check of return value to catch errors correctly.
    
    Fixes: 76c47d1449fc ("gpio: mpc8xxx: Add ACPI support")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>

commit c831d92890e037aafee662e66172d406804e4818
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Dec 26 15:46:21 2021 +0100

    irqchip/loongson-pch-ms: Use bitmap_free() to free bitmap
    
    kfree() and bitmap_free() are the same. But using the latter is more
    consistent when freeing memory allocated with bitmap_zalloc().
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/0b982ab54844803049c217b2899baa59602faacd.1640529916.git.christophe.jaillet@wanadoo.fr

commit 5754f9084f261f6fbfdcc6e57dae97c86a6ff688
Author: Heiko Carstens <hca@linux.ibm.com>
Date:   Mon Jan 17 13:31:40 2022 +0100

    s390: add Sven Schnelle as reviewer
    
    Sven Schnelle will help reviewing s390 architecture code.
    
    Acked-by: Sven Schnelle <svens@linux.ibm.com>
    Acked-by: Alexander Gordeev <agordeev@linux.ibm.com>
    Acked-by: Vasily Gorbik <gor@linux.ibm.com>
    Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 012a224e1fa31fc256aab921f691598e03db6018
Author: Nico Boehr <nrb@linux.ibm.com>
Date:   Tue Jan 11 11:00:03 2022 +0100

    s390/uaccess: introduce bit field for OAC specifier
    
    Previously, we've used  magic values to specify the OAC
    (operand-access control) for mvcos.
    
    Instead we introduce a bit field for it.
    
    When using a bit field, we cannot use an immediate value with K
    constraint anymore, since GCC older than 10 doesn't recognize
    the bit field union as a compile time constant.
    To make things work with older compilers,
    load the OAC value through a register.
    
    Bloat-o-meter reports a slight increase in kernel size with this change:
    Total: Before=15692135, After=15693015, chg +0.01%
    
    Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
    Co-developed-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220111100003.743116-1-scgl@linux.ibm.com
    Cc: Alexander Gordeev <agordeev@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Sven Schnelle <svens@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 745f5d20e7936931f924410f32d8b0e599b5990e
Author: Thomas Richter <tmricht@linux.ibm.com>
Date:   Thu Jan 13 12:51:56 2022 +0100

    s390/cpumf: Support for CPU Measurement Sampling Facility LS bit
    
    Adds support for the CPU Measurement Sampling Facility limit sampling
    bit in the sampling device driver.
    Limited samples have no valueable information are not collected.
    
    Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
    Acked-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit a87b0fd4f9003f8521226e226cf92b18147b3519
Author: Thomas Richter <tmricht@linux.ibm.com>
Date:   Thu Jan 13 12:31:16 2022 +0100

    s390/cpumf: Support for CPU Measurement Facility CSVN 7
    
    Adds support for the CPU Measurement Counter Facility second version
    number 7.
    
    Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
    Acked-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 9ea674d7ca4f6ce080b813ac2d9a9397f13d2427
Merge: c0b7f7d7e0ad4 79074a72d335d
Author: David S. Miller <davem@davemloft.net>
Date:   Mon Jan 17 13:07:47 2022 +0000

    Merge branch 'skb-leak-fixes'
    
    Gal Pressman says:
    
    ====================
    net: Couple of skb memory leak fixes
    
    As discussed in:
    https://lore.kernel.org/netdev/20220102081253.9123-1-gal@nvidia.com/
    
    These are the two followup suggestions from Eric and Jakub.
    Patch #1 adds a sk_defer_free_flush() call to the kTLS splice_read
    handler.
    Patch #2 verifies the defer list is empty on socket destroy, and calls a
    defer free flush as well.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 79074a72d335dbd021a716d8cc65cba3b2f706ab
Author: Gal Pressman <gal@nvidia.com>
Date:   Mon Jan 17 11:27:33 2022 +0200

    net: Flush deferred skb free on socket destroy
    
    The cited Fixes patch moved to a deferred skb approach where the skbs
    are not freed immediately under the socket lock.  Add a WARN_ON_ONCE()
    to verify the deferred list is empty on socket destroy, and empty it to
    prevent potential memory leaks.
    
    Fixes: f35f821935d8 ("tcp: defer skb freeing after socket lock is released")
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit db094aa8140e6da25ba77345b24a8af0c220665e
Author: Gal Pressman <gal@nvidia.com>
Date:   Mon Jan 17 11:27:32 2022 +0200

    net/tls: Fix another skb memory leak when running kTLS traffic
    
    This patch is a followup to
    commit ffef737fd037 ("net/tls: Fix skb memory leak when running kTLS traffic")
    
    Which was missing another sk_defer_free_flush() call in
    tls_sw_splice_read().
    
    Fixes: f35f821935d8 ("tcp: defer skb freeing after socket lock is released")
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c0b7f7d7e0ad44f35745c01964b3fa2833e298cb
Author: Horatiu Vultur <horatiu.vultur@microchip.com>
Date:   Mon Jan 17 13:53:00 2022 +0100

    net: ocelot: Fix the call to switchdev_bridge_port_offload
    
    In the blamed commit, the call to the function
    switchdev_bridge_port_offload was passing the wrong argument for
    atomic_nb. It was ocelot_netdevice_nb instead of ocelot_swtchdev_nb.
    This patch fixes this issue.
    
    Fixes: 4e51bf44a03af6 ("net: bridge: move the switchdev object replay helpers to "push" mode")
    Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
    Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 960dd884ddf5621ae6284cd3a42724500a97ae4c
Author: Sander Vanheule <sander@svanheule.net>
Date:   Sun Jan 9 15:54:34 2022 +0100

    irqchip/realtek-rtl: Service all pending interrupts
    
    Instead of only servicing the lowest pending interrupt line, make sure
    all pending SoC interrupts are serviced before exiting the chained
    handler. This adds a small overhead if only one interrupt is pending,
    but should prevent rapid re-triggering of the handler.
    
    Signed-off-by: Sander Vanheule <sander@svanheule.net>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/5082ad3cb8b4eedf55075561b93eff6570299fe1.1641739718.git.sander@svanheule.net

commit 91351b5dd0fd494eb2d85e1bb6aca77b067447e0
Author: Sander Vanheule <sander@svanheule.net>
Date:   Sun Jan 9 15:54:33 2022 +0100

    irqchip/realtek-rtl: Fix off-by-one in routing
    
    There is an offset between routing values (1..6) and the connected MIPS
    CPU interrupts (2..7), but no distinction was made between these two
    values.
    
    This issue was previously hidden during testing, because an interrupt
    mapping was used where for each required interrupt another (unused)
    routing was configured, with an offset of +1.
    
    Offset the CPU IRQ numbers by -1 to retrieve the correct routing value.
    
    Fixes: 9f3a0f34b84a ("irqchip: Add support for Realtek RTL838x/RTL839x interrupt controller")
    Signed-off-by: Sander Vanheule <sander@svanheule.net>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/177b920aa8d8610615692d0e657e509f363c85ca.1641739718.git.sander@svanheule.net

commit 291e79c7e2eb6fdc016453597b78482e06199d0f
Author: Sander Vanheule <sander@svanheule.net>
Date:   Sun Jan 9 15:54:32 2022 +0100

    irqchip/realtek-rtl: Map control data to virq
    
    The driver assigned the irqchip and irq handler to the hardware irq,
    instead of the virq. This is incorrect, and only worked because these
    irq numbers happened to be the same on the devices used for testing the
    original driver.
    
    Fixes: 9f3a0f34b84a ("irqchip: Add support for Realtek RTL838x/RTL839x interrupt controller")
    Signed-off-by: Sander Vanheule <sander@svanheule.net>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/4b4936606480265db47df152f00bc2ed46340599.1641739718.git.sander@svanheule.net

commit 45378cd33905966baf16d12ab0adbd56794ee075
Author: Marc Zyngier <maz@kernel.org>
Date:   Sat Jan 8 14:01:18 2022 +0000

    irqchip/apple-aic: Drop unused ipi_hwirq field
    
    This field was never used, remove it.
    
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Acked-by: Hector Martin <marcan@marcan.st>
    Link: https://lore.kernel.org/r/20220108140118.3378937-1-maz@kernel.org

commit e26602be4869c74dd8a0f66f718b8a0ce120edb4
Author: José Roberto de Souza <jose.souza@intel.com>
Date:   Thu Jan 13 09:48:26 2022 -0800

    drm/i915/display/adlp: Implement new step in the TC voltage swing prog sequence
    
    TC voltage swing programming sequence was updated with a new step.
    
    BSpec: 54956
    Cc: stable@vger.kernel.org
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Clint Taylor <clinton.a.taylor@intel.com>
    Cc: Imre Deak <imre.deak@intel.com>
    Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
    Reviewed-by: Clint Taylor <Clinton.A.Taylor@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220113174826.50272-1-jose.souza@intel.com
    (cherry picked from commit 5ff59dddacd4738edcbd01847d9df7682348cf86)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit ef3ac01564067a4337bb798b8eddc6ea7b78fd10
Author: José Roberto de Souza <jose.souza@intel.com>
Date:   Thu Jan 13 08:04:37 2022 -0800

    drm/i915/display/ehl: Update voltage swing table
    
    EHL table was recently updated with some minor fixes.
    
    BSpec: 21257
    Cc: stable@vger.kernel.org
    Cc: Clint Taylor <clinton.a.taylor@intel.com>
    Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
    Reviewed-by: Clint Taylor <Clinton.A.Taylor@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220113160437.49059-1-jose.souza@intel.com
    (cherry picked from commit 5ec7baef52c367cdbda964aa662f7135c25bab1f)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 5576c4f24c56722a2d9fb9c447d896e5b312078b
Author: Takashi Iwai <tiwai@suse.de>
Date:   Sun Jan 16 09:28:38 2022 +0100

    ALSA: core: Fix SSID quirk lookup for subvendor=0
    
    Some weird devices set the codec SSID vendor ID 0, and
    snd_pci_quirk_lookup_id() loop aborts at the point although it should
    still try matching with the SSID device ID.  This resulted in a
    missing quirk for some old Macs.
    
    Fix the loop termination condition to check both subvendor and
    subdevice.
    
    Fixes: 73355ddd8775 ("ALSA: hda: Code refactoring snd_hda_pick_fixup()")
    Cc: <stable@vger.kernel.org>
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215495
    Link: https://lore.kernel.org/r/20220116082838.19382-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 0c947b893d69231a9add855939da7c66237ab44f
Merge: a6097180d884d 9bbf8662a27b5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 09:53:21 2022 +0200

    Merge tag '5.17-rc-part1-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6
    
    Pull cifs updates from Steve French:
    
     - multichannel patches mostly related to improving reconnect behavior
    
     - minor cleanup patches
    
    * tag '5.17-rc-part1-smb3-fixes' of git://git.samba.org/sfrench/cifs-2.6:
      cifs: fix FILE_BOTH_DIRECTORY_INFO definition
      cifs: move superblock magic defitions to magic.h
      cifs: Fix smb311_update_preauth_hash() kernel-doc comment
      cifs: avoid race during socket reconnect between send and recv
      cifs: maintain a state machine for tcp/smb/tcon sessions
      cifs: fix hang on cifs_get_next_mid()
      cifs: take cifs_tcp_ses_lock for status checks
      cifs: reconnect only the connection and not smb session where possible
      cifs: add WARN_ON for when chan_count goes below minimum
      cifs: adjust DebugData to use chans_need_reconnect for conn status
      cifs: use the chans_need_reconnect bitmap for reconnect status
      cifs: track individual channel status using chans_need_reconnect
      cifs: remove redundant assignment to pointer p

commit a6097180d884ddab769fb25588ea8598589c218c
Author: NeilBrown <neilb@suse.de>
Date:   Mon Jan 17 09:07:26 2022 +1100

    devtmpfs regression fix: reconfigure on each mount
    
    Prior to Linux v5.4 devtmpfs used mount_single() which treats the given
    mount options as "remount" options, so it updates the configuration of
    the single super_block on each mount.
    
    Since that was changed, the mount options used for devtmpfs are ignored.
    This is a regression which affect systemd - which mounts devtmpfs with
    "-o mode=755,size=4m,nr_inodes=1m".
    
    This patch restores the "remount" effect by calling reconfigure_single()
    
    Fixes: d401727ea0d7 ("devtmpfs: don't mix {ramfs,shmem}_fill_super() with mount_single()")
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3c750c7b614322a4ab50be0d57a76addb598d51d
Merge: b520085ca5798 f346f32701eba
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:48:09 2022 +0200

    Merge tag 'fbdev-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev
    
    Pull fbdev maintainership update from Helge Deller:
     "The fbdev layer is orphaned, but seems to need some care. So I'd like
      to step up as new maintainer"
    
    * tag 'fbdev-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev:
      MAINTAINERS: Add Helge as fbdev maintainer

commit b520085ca57982c4beeb9bb64b8f6018425cb61f
Merge: 4b3789512f018 762f99f4f3cb4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:27:55 2022 +0200

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input
    
    Pull input updates from Dmitry Torokhov:
     "Updates to Goodix touchscreen driver (addition of pen support) and
      Silead touchscreen driver (also addition of pen support and parsing of
      embedded firmware to determine screen size), along with assorted fixes
      for other drivers"
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input:
      Input: ti_am335x_tsc - fix a typo in a comment
      Input: zinitix - add compatible for bt532
      Input: zinitix - handle proper supply names
      dt-bindings: input/ts/zinitix: Convert to YAML, fix and extend
      Input: axp20x-pek - revert "always register interrupt handlers" change
      Input: gpio-keys - avoid clearing twice some memory
      Input: byd - fix typo in a comment
      Input: ucb1400_ts - remove redundant variable penup
      Input: ti_am335x_tsc - lower the X and Y sampling time
      Input: ti_am335x_tsc - fix STEPCONFIG setup for Z2
      Input: ti_am335x_tsc - set ADCREFM for X configuration
      Input: silead - add pen support
      Input: silead - add support for EFI-embedded fw using different min/max coordinates
      Input: goodix - 2 small fixes for pen support
      Input: goodix - improve gpiod_get() error logging
      Input: goodix - add pen support
      Input: ff-core - correct magnitude setting for rumble compatibility
      Input: palmas-pwrbutton - make a couple of arrays static const
      Input: wacom_i2c - clean up the query device fields
      Input: palmas-pwrbutton - use bitfield helpers

commit 4b3789512f018819e0c4b0776731dc4ce694c484
Merge: 96000bc956628 13462ba1815db
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:20:28 2022 +0200

    Merge tag 'i3c/for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux
    
    Pull i3c updates from Alexandre Belloni:
     "Mostly non urgent fixes and a few improvements (including runtime pm
      suport) to the Silvaco driver"
    
    * tag 'i3c/for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/i3c/linux:
      i3c: master: dw: check return of dw_i3c_master_get_free_pos()
      i3c: master: mipi-i3c-hci: correct the config reference for endianness
      i3c: master: svc: enable the interrupt in the enable ibi function
      i3c: master: svc: add the missing module device table
      i3c: master: svc: add runtime pm support
      i3c: master: svc: set ODSTOP to let I2C device see the STOP signal
      i3c: master: svc: add support for slave to stop returning data
      i3c: master: svc: separate err, fifo and disable interrupt of reset function
      i3c: master: svc: fix atomic issue
      i3c: master: svc: move module reset behind clk enable
      i3c/master/mipi-i3c-hci: Fix a potentially infinite loop in 'hci_dat_v1_get_index()'
      i3c: fix incorrect address slot lookup on 64-bit
      i3c/master/mipi-i3c-hci: Prefer kcalloc over open coded arithmetic
      i3c/master/mipi-i3c-hci: Prefer struct_size over open coded arithmetic

commit 96000bc956628dc0cc608696d5385ffc19e65a76
Merge: 2225acc322750 8cd778650ae22
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:14:18 2022 +0200

    Merge tag 'ntb-5.17' of git://github.com/jonmason/ntb
    
    Pull NTB updates from Jon Mason:
     "New AMD PCI ID for NTB, and a number of bug fixes for ntb_hw_switchtec
      for Linux v5.17"
    
    * tag 'ntb-5.17' of git://github.com/jonmason/ntb:
      ntb_hw_switchtec: Fix a minor issue in config_req_id_table()
      ntb_hw_switchtec: Remove code for disabling ID protection
      ntb_hw_switchtec: Update the way of getting VEP instance ID
      ntb_hw_switchtec: AND with the part_map for a valid tpart_vec
      ntb_hw_switchtec: Fix bug with more than 32 partitions
      ntb_hw_switchtec: Fix pff ioread to read into mmio_part_cfg_all
      ntb_hw_switchtec: fix the spelling of "its"
      NTB/msi: Fix ntbm_msi_request_threaded_irq() kernel-doc comment
      ntb_hw_amd: Add NTB PCI ID for new gen CPU

commit 2225acc32275085d5e0ce5845c6fd18d61204b49
Merge: b70b878c32ef3 ffd264bd152cb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:07:57 2022 +0200

    Merge tag 'linux-watchdog-5.17-rc1' of git://www.linux-watchdog.org/linux-watchdog
    
    Pull watchdog updates from Wim Van Sebroeck:
    
     - New device support:
         - Watchdog Timer driver for RZ/G2L
         - Realtek Otto watchdog timer
         - Apple SoC watchdog driver
         - Fintek F81966
    
     - Remove BCM63XX_WDT after support for this SoC was added to
       BCM7038_WDT
    
     - Improvements of the BCM7038_WDT and s3c2410_wdt code
    
     - Several other fixes and improvements
    
    * tag 'linux-watchdog-5.17-rc1' of git://www.linux-watchdog.org/linux-watchdog: (38 commits)
      watchdog: msc313e: Check if the WDT was running at boot
      watchdog: Add Apple SoC watchdog driver
      dt-bindings: watchdog: Add SM6350 and SM8250 compatible
      watchdog: s3c2410: Fix getting the optional clock
      watchdog: s3c2410: Use platform_get_irq() to get the interrupt
      dt-bindings: watchdog: atmel: Add missing 'interrupts' property
      watchdog: mtk_wdt: use platform_get_irq_optional
      watchdog: Add Watchdog Timer driver for RZ/G2L
      dt-bindings: watchdog: renesas,wdt: Add support for RZ/G2L
      watchdog: da9063: Add hard dependency on I2C
      watchdog: Add Realtek Otto watchdog timer
      dt-bindings: watchdog: Realtek Otto WDT binding
      watchdog: s3c2410: Add Exynos850 support
      watchdog: da9063: use atomic safe i2c transfer in reset handler
      watchdog: davinci: Use div64_ul instead of do_div
      watchdog: Remove BCM63XX_WDT
      MIPS: BCM63XX: Provide platform data to watchdog device
      watchdog: bcm7038_wdt: Add platform device id for bcm63xx-wdt
      watchdog: Allow building BCM7038_WDT for BCM63XX
      watchdog: bcm7038_wdt: Support platform data configuration
      ...

commit b70b878c32ef3971334ade7fac8f47e4629b029c
Merge: 763978ca67a3d 3cdb8e995ee2e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 08:00:56 2022 +0200

    Merge branch 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux
    
    Pull coccinelle updates from Julia Lawall:
     "Remove some semantic patches and remove a maintainer.
    
      Qing Wang <wangqing@vivo.com> reported that fen.cocci mostly finds
      false positives, so it is dropped.
      scripts/coccinelle/iterators/for_each_child.cocci also subsumes it, in
      a more correct way.
    
      Matthew Wilcox <willy@infradead.org> reported that bugon.cocci mostly
      gives false positives. It is an old script and was designed to be
      inaccurate to maximally cover problems, but most of what it is useful
      for has been done already.
    
      Gilles Muller passed away and is thus dropped from the maintainers
      list"
    
    * 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux:
      drop fen.cocci
      scripts/coccinelle: drop bugon.cocci
      MAINTAINERS: remove Gilles Muller

commit 763978ca67a3d7be3915e2035e2a6c331524c748
Merge: 98f2345773f9a a97ac8cb24a3c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 07:32:51 2022 +0200

    Merge branch 'modules-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux
    
    Pull module updates from Luis Chamberlain:
     "The biggest change here is in-kernel support for module decompression.
      This change is being made to help support LSMs like LoadPin as
      otherwise it loses link between the source of kernel module on the
      disk and binary blob that is being loaded into the kernel.
    
      kmod decompression is still done by userspace even with this is done,
      both because there are no measurable gains in not doing so and as it
      adds a secondary extra check for validating the module before loading
      it into the kernel.
    
      The rest of the changes are minor, the only other change worth
      mentionin there is Jessica Yu is now bowing out of maintenance of
      modules as she's taking a break from work.
    
      While there were other changes posted for modules, those have not yet
      received much review of testing so I'm not yet comfortable in merging
      any of those changes yet."
    
    * 'modules-next' of git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux:
      module: fix signature check failures when using in-kernel decompression
      kernel: Fix spelling mistake "compresser" -> "compressor"
      MAINTAINERS: add mailing lists for kmod and modules
      module.h: allow #define strings to work with MODULE_IMPORT_NS
      module: add in-kernel support for decompressing
      MAINTAINERS: Remove myself as modules maintainer
      module: Remove outdated comment

commit 98f2345773f9ac739350230a85f9a7f7b1fe21a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 07:26:43 2022 +0200

    unicode: fix .gitignore for generated utfdata file
    
    Commit 2b3d04787012 ("unicode: Add utf8-data module") changed the
    generated utf8data file from 'utf8data.h' to 'utf8data.c', but didn't
    change the comments or the .gitignore to match.
    
    The comments should be updated too, but at least they don't cause any
    visible breakage.  But the gitignore file needs changing to avoid git
    complaining about untracked files.
    
    Fixes: 2b3d04787012 ("unicode: Add utf8-data module")
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 429a64f6e91fbfe4912d17247c27d0d66767b1c2
Author: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Date:   Fri Jan 14 08:43:55 2022 +0530

    powerpc/perf: Only define power_pmu_wants_prompt_pmi() for CONFIG_PPC64
    
    power_pmu_wants_prompt_pmi() is used to decide if PMIs should be taken
    promptly. This is valid only for ppc64 and is used only if
    CONFIG_PPC_BOOK3S_64=y. Hence include the function under config check
    for PPC64.
    
    Fixes warning for 32-bit compilation:
    
      arch/powerpc/perf/core-book3s.c:2455:6: warning: no previous prototype for 'power_pmu_wants_prompt_pmi'
        2455 | bool power_pmu_wants_prompt_pmi(void)
             |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
    
    Fixes: 5a7745b96f43 ("powerpc/64s/perf: add power_pmu_wants_prompt_pmi to say whether perf wants PMIs to be soft-NMI")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
    Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
    [mpe: Move inside existing CONFIG_PPC64 ifdef block]
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/20220114031355.87480-1-atrajeev@linux.vnet.ibm.com

commit 35ce8ae9ae2e471f92759f9d6880eab42cc1c3b6
Merge: 6661224e66f03 a403df29789ba
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 05:49:30 2022 +0200

    Merge branch 'signal-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace
    
    Pull signal/exit/ptrace updates from Eric Biederman:
     "This set of changes deletes some dead code, makes a lot of cleanups
      which hopefully make the code easier to follow, and fixes bugs found
      along the way.
    
      The end-game which I have not yet reached yet is for fatal signals
      that generate coredumps to be short-circuit deliverable from
      complete_signal, for force_siginfo_to_task not to require changing
      userspace configured signal delivery state, and for the ptrace stops
      to always happen in locations where we can guarantee on all
      architectures that the all of the registers are saved and available on
      the stack.
    
      Removal of profile_task_ext, profile_munmap, and profile_handoff_task
      are the big successes for dead code removal this round.
    
      A bunch of small bug fixes are included, as most of the issues
      reported were small enough that they would not affect bisection so I
      simply added the fixes and did not fold the fixes into the changes
      they were fixing.
    
      There was a bug that broke coredumps piped to systemd-coredump. I
      dropped the change that caused that bug and replaced it entirely with
      something much more restrained. Unfortunately that required some
      rebasing.
    
      Some successes after this set of changes: There are few enough calls
      to do_exit to audit in a reasonable amount of time. The lifetime of
      struct kthread now matches the lifetime of struct task, and the
      pointer to struct kthread is no longer stored in set_child_tid. The
      flag SIGNAL_GROUP_COREDUMP is removed. The field group_exit_task is
      removed. Issues where task->exit_code was examined with
      signal->group_exit_code should been examined were fixed.
    
      There are several loosely related changes included because I am
      cleaning up and if I don't include them they will probably get lost.
    
      The original postings of these changes can be found at:
         https://lkml.kernel.org/r/87a6ha4zsd.fsf@email.froward.int.ebiederm.org
         https://lkml.kernel.org/r/87bl1kunjj.fsf@email.froward.int.ebiederm.org
         https://lkml.kernel.org/r/87r19opkx1.fsf_-_@email.froward.int.ebiederm.org
    
      I trimmed back the last set of changes to only the obviously correct
      once. Simply because there was less time for review than I had hoped"
    
    * 'signal-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace: (44 commits)
      ptrace/m68k: Stop open coding ptrace_report_syscall
      ptrace: Remove unused regs argument from ptrace_report_syscall
      ptrace: Remove second setting of PT_SEIZED in ptrace_attach
      taskstats: Cleanup the use of task->exit_code
      exit: Use the correct exit_code in /proc/<pid>/stat
      exit: Fix the exit_code for wait_task_zombie
      exit: Coredumps reach do_group_exit
      exit: Remove profile_handoff_task
      exit: Remove profile_task_exit & profile_munmap
      signal: clean up kernel-doc comments
      signal: Remove the helper signal_group_exit
      signal: Rename group_exit_task group_exec_task
      coredump: Stop setting signal->group_exit_task
      signal: Remove SIGNAL_GROUP_COREDUMP
      signal: During coredumps set SIGNAL_GROUP_EXIT in zap_process
      signal: Make coredump handling explicit in complete_signal
      signal: Have prepare_signal detect coredumps using signal->core_state
      signal: Have the oom killer detect coredumps using signal->core_state
      exit: Move force_uaccess back into do_exit
      exit: Guarantee make_task_dead leaks the tsk when calling do_task_exit
      ...

commit 6661224e66f03706daea8e27714436851cf01731
Merge: 79e06c4c4950b e2a58d2d3416a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 17 05:40:02 2022 +0200

    Merge tag 'unicode-for-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode
    
    Pull unicode updates from Gabriel Krisman Bertazi:
     "This includes patches from Christoph Hellwig to split the large data
      tables of the unicode subsystem into a loadable module, which allow
      users to not have them around if case-insensitive filesystems are not
      to be used. It also includes minor code fixes to unicode and its
      users, from the same author.
    
      All the patches here have been on linux-next releases for the past
      months"
    
    * tag 'unicode-for-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode:
      unicode: only export internal symbols for the selftests
      unicode: Add utf8-data module
      unicode: cache the normalization tables in struct unicode_map
      unicode: move utf8cursor to utf8-selftest.c
      unicode: simplify utf8len
      unicode: remove the unused utf8{,n}age{min,max} functions
      unicode: pass a UNICODE_AGE() tripple to utf8_load
      unicode: mark the version field in struct unicode_map unsigned
      unicode: remove the charset field from struct unicode_map
      f2fs: simplify f2fs_sb_read_encoding
      ext4: simplify ext4_sb_read_encoding

commit 3abb28e275bfbe60136db37eae6679c3e1928cd5
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Jan 7 13:03:48 2022 -0500

    filemap: Use folio_put_refs() in filemap_free_folio()
    
    This shrinks filemap_free_folio() by 55 bytes in my .config; 24 bytes
    from removing the VM_BUG_ON_FOLIO() and 31 bytes from unifying the
    small/large folio paths.
    
    We could just use folio_ref_sub() here since the caller should hold a
    reference (as the VM_BUG_ON_FOLIO() was asserting), but that's fragile.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>

commit 3fe7fa5843d204e235d92902190fecb972a3f9cc
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Dec 10 15:09:21 2021 -0500

    mm: Add folio_put_refs()
    
    This is like folio_put(), but puts N references at once instead of
    just one.  It's like put_page_refs(), but does one atomic operation
    instead of two, and is available to more than just gup.c.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: John Hubbard <jhubbard@nvidia.com>
    Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 429e3d123d9a50cc9882402e40e0ac912d88cfcf
Author: Moshe Tal <moshet@nvidia.com>
Date:   Sun Jan 16 19:39:29 2022 +0200

    bonding: Fix extraction of ports from the packet headers
    
    Wrong hash sends single stream to multiple output interfaces.
    
    The offset calculation was relative to skb->head, fix it to be relative
    to skb->data.
    
    Fixes: a815bde56b15 ("net, bonding: Refactor bond_xmit_hash for use with
    xdp_buff")
    Reviewed-by: Jussi Maki <joamaki@gmail.com>
    Reviewed-by: Saeed Mahameed <saeedm@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Moshe Tal <moshet@nvidia.com>
    Acked-by: Jay Vosburgh <jay.vosburgh@canonical.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5ceee540fdc7f1d65ca6e2b1b193ce5aa95ab99c
Author: Yang Yingliang <yangyingliang@huawei.com>
Date:   Thu Jan 6 15:57:11 2022 +0800

    rtc: sunplus: fix return value in sp_rtc_probe()
    
    If devm_ioremap_resource() fails, it should return error
    code from sp_rtc->reg_base in sp_rtc_probe().
    
    Fixes: fad6cbe9b2b4 ("rtc: Add driver for RTC in Sunplus SP7021")
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Link: https://lore.kernel.org/r/20220106075711.3216468-1-yangyingliang@huawei.com

commit ff164ae39b82ee483b24579c8e22a13a8ce5bd04
Author: Riwen Lu <luriwen@kylinos.cn>
Date:   Thu Jan 6 16:46:09 2022 +0800

    rtc: cmos: Evaluate century appropriate
    
    There's limiting the year to 2069. When setting the rtc year to 2070,
    reading it returns 1970. Evaluate century starting from 19 to count the
    correct year.
    
    $ sudo date -s 20700106
    Mon 06 Jan 2070 12:00:00 AM CST
    $ sudo hwclock -w
    $ sudo hwclock -r
    1970-01-06 12:00:49.604968+08:00
    
    Fixes: 2a4daadd4d3e5071 ("rtc: cmos: ignore bogus century byte")
    
    Signed-off-by: Riwen Lu <luriwen@kylinos.cn>
    Acked-by: Eric Wong <e@80x24.org>
    Reviewed-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Link: https://lore.kernel.org/r/20220106084609.1223688-1-luriwen@kylinos.cn

commit 900ed72c8a190e8c0b87cb17abc645b8ec713011
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:33:40 2022 +0300

    rtc: gamecube: Fix an IS_ERR() vs NULL check
    
    The devm_kzalloc() function returns NULL on error, it doesn't return
    error pointers.
    
    Fixes: 86559400b3ef ("rtc: gamecube: Add a RTC driver for the GameCube, Wii and Wii U")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Link: https://lore.kernel.org/r/20220107073340.GF22086@kili

commit 7372971c1be5b7d4fdd8ad237798bdc1d1d54162
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 11 10:19:22 2022 +0300

    rtc: mc146818-lib: fix signedness bug in mc146818_get_time()
    
    The mc146818_get_time() function returns zero on success or negative
    a error code on failure.  It needs to be type int.
    
    Fixes: d35786b3a28d ("rtc: mc146818-lib: change return values of mc146818_get_time()")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Link: https://lore.kernel.org/r/20220111071922.GE11243@kili

commit 79e06c4c4950be2abd8ca5d2428a8c915aa62c24
Merge: cb3f09f9afe52 c862dcd199759
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 16:15:14 2022 +0200

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
    
    Pull kvm updates from Paolo Bonzini:
     "RISCV:
    
       - Use common KVM implementation of MMU memory caches
    
       - SBI v0.2 support for Guest
    
       - Initial KVM selftests support
    
       - Fix to avoid spurious virtual interrupts after clearing hideleg CSR
    
       - Update email address for Anup and Atish
    
      ARM:
    
       - Simplification of the 'vcpu first run' by integrating it into KVM's
         'pid change' flow
    
       - Refactoring of the FP and SVE state tracking, also leading to a
         simpler state and less shared data between EL1 and EL2 in the nVHE
         case
    
       - Tidy up the header file usage for the nvhe hyp object
    
       - New HYP unsharing mechanism, finally allowing pages to be unmapped
         from the Stage-1 EL2 page-tables
    
       - Various pKVM cleanups around refcounting and sharing
    
       - A couple of vgic fixes for bugs that would trigger once the vcpu
         xarray rework is merged, but not sooner
    
       - Add minimal support for ARMv8.7's PMU extension
    
       - Rework kvm_pgtable initialisation ahead of the NV work
    
       - New selftest for IRQ injection
    
       - Teach selftests about the lack of default IPA space and page sizes
    
       - Expand sysreg selftest to deal with Pointer Authentication
    
       - The usual bunch of cleanups and doc update
    
      s390:
    
       - fix sigp sense/start/stop/inconsistency
    
       - cleanups
    
      x86:
    
       - Clean up some function prototypes more
    
       - improved gfn_to_pfn_cache with proper invalidation, used by Xen
         emulation
    
       - add KVM_IRQ_ROUTING_XEN_EVTCHN and event channel delivery
    
       - completely remove potential TOC/TOU races in nested SVM consistency
         checks
    
       - update some PMCs on emulated instructions
    
       - Intel AMX support (joint work between Thomas and Intel)
    
       - large MMU cleanups
    
       - module parameter to disable PMU virtualization
    
       - cleanup register cache
    
       - first part of halt handling cleanups
    
       - Hyper-V enlightened MSR bitmap support for nested hypervisors
    
      Generic:
    
       - clean up Makefiles
    
       - introduce CONFIG_HAVE_KVM_DIRTY_RING
    
       - optimize memslot lookup using a tree
    
       - optimize vCPU array usage by converting to xarray"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (268 commits)
      x86/fpu: Fix inline prefix warnings
      selftest: kvm: Add amx selftest
      selftest: kvm: Move struct kvm_x86_state to header
      selftest: kvm: Reorder vcpu_load_state steps for AMX
      kvm: x86: Disable interception for IA32_XFD on demand
      x86/fpu: Provide fpu_sync_guest_vmexit_xfd_state()
      kvm: selftests: Add support for KVM_CAP_XSAVE2
      kvm: x86: Add support for getting/setting expanded xstate buffer
      x86/fpu: Add uabi_size to guest_fpu
      kvm: x86: Add CPUID support for Intel AMX
      kvm: x86: Add XCR0 support for Intel AMX
      kvm: x86: Disable RDMSR interception of IA32_XFD_ERR
      kvm: x86: Emulate IA32_XFD_ERR for guest
      kvm: x86: Intercept #NM for saving IA32_XFD_ERR
      x86/fpu: Prepare xfd_err in struct fpu_guest
      kvm: x86: Add emulation for IA32_XFD
      x86/fpu: Provide fpu_update_guest_xfd() for IA32_XFD emulation
      kvm: x86: Enable dynamic xfeatures at KVM_SET_CPUID2
      x86/fpu: Provide fpu_enable_guest_xfd_features() for KVM
      x86/fpu: Add guest support to xfd_enable_feature()
      ...

commit cb3f09f9afe5286c0aed7a1c5cc71495de166efb
Merge: 4d66020dcef83 4eea5332d67d8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 15:53:00 2022 +0200

    Merge tag 'hyperv-next-signed-20220114' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux
    
    Pull hyperv updates from Wei Liu:
    
     - More patches for Hyper-V isolation VM support (Tianyu Lan)
    
     - Bug fixes and clean-up patches from various people
    
    * tag 'hyperv-next-signed-20220114' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux:
      scsi: storvsc: Fix storvsc_queuecommand() memory leak
      x86/hyperv: Properly deal with empty cpumasks in hyperv_flush_tlb_multi()
      Drivers: hv: vmbus: Initialize request offers message for Isolation VM
      scsi: storvsc: Fix unsigned comparison to zero
      swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap()
      x86/hyperv: Fix definition of hv_ghcb_pg variable
      Drivers: hv: Fix definition of hypercall input & output arg variables
      net: netvsc: Add Isolation VM support for netvsc driver
      scsi: storvsc: Add Isolation VM support for storvsc driver
      hyper-v: Enable swiotlb bounce buffer for Isolation VM
      x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has()
      swiotlb: Add swiotlb bounce buffer remap function for HV IVM

commit 56d99e81ecbc997a5f984684d0eeb583992b2072
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Sun Jan 16 15:43:42 2022 +0800

    net/smc: Fix hung_task when removing SMC-R devices
    
    A hung_task is observed when removing SMC-R devices. Suppose that
    a link group has two active links(lnk_A, lnk_B) associated with two
    different SMC-R devices(dev_A, dev_B). When dev_A is removed, the
    link group will be removed from smc_lgr_list and added into
    lgr_linkdown_list. lnk_A will be cleared and smcibdev(A)->lnk_cnt
    will reach to zero. However, when dev_B is removed then, the link
    group can't be found in smc_lgr_list and lnk_B won't be cleared,
    making smcibdev->lnk_cnt never reaches zero, which causes a hung_task.
    
    This patch fixes this issue by restoring the implementation of
    smc_smcr_terminate_all() to what it was before commit 349d43127dac
    ("net/smc: fix kernel panic caused by race of smc_sock"). The original
    implementation also satisfies the intention that make sure QP destroy
    earlier than CQ destroy because we will always wait for smcibdev->lnk_cnt
    reaches zero, which guarantees QP has been destroyed.
    
    Fixes: 349d43127dac ("net/smc: fix kernel panic caused by race of smc_sock")
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0a6e6b3c7db6c34e3d149f09cd714972f8753e3f
Author: Eric Dumazet <edumazet@google.com>
Date:   Sun Jan 16 01:02:20 2022 -0800

    ipv4: update fib_info_cnt under spinlock protection
    
    In the past, free_fib_info() was supposed to be called
    under RTNL protection.
    
    This eventually was no longer the case.
    
    Instead of enforcing RTNL it seems we simply can
    move fib_info_cnt changes to occur when fib_info_lock
    is held.
    
    v2: David Laight suggested to update fib_info_cnt
    only when an entry is added/deleted to/from the hash table,
    as fib_info_cnt is used to make sure hash table size
    is optimal.
    
    BUG: KCSAN: data-race in fib_create_info / free_fib_info
    
    write to 0xffffffff86e243a0 of 4 bytes by task 26429 on cpu 0:
     fib_create_info+0xe78/0x3440 net/ipv4/fib_semantics.c:1428
     fib_table_insert+0x148/0x10c0 net/ipv4/fib_trie.c:1224
     fib_magic+0x195/0x1e0 net/ipv4/fib_frontend.c:1087
     fib_add_ifaddr+0xd0/0x2e0 net/ipv4/fib_frontend.c:1109
     fib_netdev_event+0x178/0x510 net/ipv4/fib_frontend.c:1466
     notifier_call_chain kernel/notifier.c:83 [inline]
     raw_notifier_call_chain+0x53/0xb0 kernel/notifier.c:391
     __dev_notify_flags+0x1d3/0x3b0
     dev_change_flags+0xa2/0xc0 net/core/dev.c:8872
     do_setlink+0x810/0x2410 net/core/rtnetlink.c:2719
     rtnl_group_changelink net/core/rtnetlink.c:3242 [inline]
     __rtnl_newlink net/core/rtnetlink.c:3396 [inline]
     rtnl_newlink+0xb10/0x13b0 net/core/rtnetlink.c:3506
     rtnetlink_rcv_msg+0x745/0x7e0 net/core/rtnetlink.c:5571
     netlink_rcv_skb+0x14e/0x250 net/netlink/af_netlink.c:2496
     rtnetlink_rcv+0x18/0x20 net/core/rtnetlink.c:5589
     netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
     netlink_unicast+0x5fc/0x6c0 net/netlink/af_netlink.c:1345
     netlink_sendmsg+0x726/0x840 net/netlink/af_netlink.c:1921
     sock_sendmsg_nosec net/socket.c:704 [inline]
     sock_sendmsg net/socket.c:724 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2409
     ___sys_sendmsg net/socket.c:2463 [inline]
     __sys_sendmsg+0x195/0x230 net/socket.c:2492
     __do_sys_sendmsg net/socket.c:2501 [inline]
     __se_sys_sendmsg net/socket.c:2499 [inline]
     __x64_sys_sendmsg+0x42/0x50 net/socket.c:2499
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffffffff86e243a0 of 4 bytes by task 31505 on cpu 1:
     free_fib_info+0x35/0x80 net/ipv4/fib_semantics.c:252
     fib_info_put include/net/ip_fib.h:575 [inline]
     nsim_fib4_rt_destroy drivers/net/netdevsim/fib.c:294 [inline]
     nsim_fib4_rt_replace drivers/net/netdevsim/fib.c:403 [inline]
     nsim_fib4_rt_insert drivers/net/netdevsim/fib.c:431 [inline]
     nsim_fib4_event drivers/net/netdevsim/fib.c:461 [inline]
     nsim_fib_event drivers/net/netdevsim/fib.c:881 [inline]
     nsim_fib_event_work+0x15ca/0x2cf0 drivers/net/netdevsim/fib.c:1477
     process_one_work+0x3fc/0x980 kernel/workqueue.c:2298
     process_scheduled_works kernel/workqueue.c:2361 [inline]
     worker_thread+0x7df/0xa70 kernel/workqueue.c:2447
     kthread+0x2c7/0x2e0 kernel/kthread.c:327
     ret_from_fork+0x1f/0x30
    
    value changed: 0x00000d2d -> 0x00000d2e
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 31505 Comm: kworker/1:21 Not tainted 5.16.0-rc6-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    Workqueue: events nsim_fib_event_work
    
    Fixes: 48bb9eb47b27 ("netdevsim: fib: Add dummy implementation for FIB offload")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Cc: David Laight <David.Laight@ACULAB.COM>
    Cc: Ido Schimmel <idosch@mellanox.com>
    Cc: Jiri Pirko <jiri@mellanox.com>
    Reviewed-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d37823c3528e5e0705fc7746bcbc2afffb619259
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Mon Jan 10 15:29:25 2022 +0000

    powerpc/32s: Fix kasan_init_region() for KASAN
    
    It has been reported some configuration where the kernel doesn't
    boot with KASAN enabled.
    
    This is due to wrong BAT allocation for the KASAN area:
    
            ---[ Data Block Address Translation ]---
            0: 0xc0000000-0xcfffffff 0x00000000       256M Kernel rw      m
            1: 0xd0000000-0xdfffffff 0x10000000       256M Kernel rw      m
            2: 0xe0000000-0xefffffff 0x20000000       256M Kernel rw      m
            3: 0xf8000000-0xf9ffffff 0x2a000000        32M Kernel rw      m
            4: 0xfa000000-0xfdffffff 0x2c000000        64M Kernel rw      m
    
    A BAT must have both virtual and physical addresses alignment matching
    the size of the BAT. This is not the case for BAT 4 above.
    
    Fix kasan_init_region() by using block_size() function that is in
    book3s32/mmu.c. To be able to reuse it here, make it non static and
    change its name to bat_block_size() in order to avoid name conflict
    with block_size() defined in <linux/blkdev.h>
    
    Also reuse find_free_bat() to avoid an error message from setbat()
    when no BAT is available.
    
    And allocate memory outside of linear memory mapping to avoid
    wasting that precious space.
    
    With this change we get correct alignment for BATs and KASAN shadow
    memory is allocated outside the linear memory space.
    
            ---[ Data Block Address Translation ]---
            0: 0xc0000000-0xcfffffff 0x00000000       256M Kernel rw
            1: 0xd0000000-0xdfffffff 0x10000000       256M Kernel rw
            2: 0xe0000000-0xefffffff 0x20000000       256M Kernel rw
            3: 0xf8000000-0xfbffffff 0x7c000000        64M Kernel rw
            4: 0xfc000000-0xfdffffff 0x7a000000        32M Kernel rw
    
    Fixes: 7974c4732642 ("powerpc/32s: Implement dedicated kasan_init_region()")
    Cc: stable@vger.kernel.org
    Reported-by: Maxime Bizon <mbizon@freebox.fr>
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Tested-by: Maxime Bizon <mbizon@freebox.fr>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/7a50ef902494d1325227d47d33dada01e52e5518.1641818726.git.christophe.leroy@csgroup.eu

commit 87b9d74fb0be80054c729e8d6a119ca0955cedf3
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Mon Jan 10 15:29:53 2022 +0000

    powerpc/time: Fix build failure due to do_hard_irq_enable() on PPC32
    
              CC      arch/powerpc/kernel/time.o
            In file included from <command-line>:
            ./arch/powerpc/include/asm/hw_irq.h: In function 'do_hard_irq_enable':
            ././include/linux/compiler_types.h:335:45: error: call to '__compiletime_assert_35' declared with attribute error: BUILD_BUG failed
              335 |         _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
                  |                                             ^
            ././include/linux/compiler_types.h:316:25: note: in definition of macro '__compiletime_assert'
              316 |                         prefix ## suffix();                             \
                  |                         ^~~~~~
            ././include/linux/compiler_types.h:335:9: note: in expansion of macro '_compiletime_assert'
              335 |         _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
                  |         ^~~~~~~~~~~~~~~~~~~
            ./include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
               39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
                  |                                     ^~~~~~~~~~~~~~~~~~
            ./include/linux/build_bug.h:59:21: note: in expansion of macro 'BUILD_BUG_ON_MSG'
               59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
                  |                     ^~~~~~~~~~~~~~~~
            ./arch/powerpc/include/asm/hw_irq.h:483:9: note: in expansion of macro 'BUILD_BUG'
              483 |         BUILD_BUG();
                  |         ^~~~~~~~~
    
    should_hard_irq_enable() returns false on PPC32 so this BUILD_BUG() shouldn't trigger.
    
    Force inlining of should_hard_irq_enable()
    
    Fixes: 0faf20a1ad16 ("powerpc/64s/interrupt: Don't enable MSR[EE] in irq handlers unless perf is in use")
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Acked-by: Nicholas Piggin <npiggin@gmail.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/247e01e0e10f4dbc59b5ff89e81702eb1ee7641e.1641828571.git.christophe.leroy@csgroup.eu

commit 5762f980ca10dcfe5eead7c40d1c34cae61f409b
Author: Johannes Schickel <lordhoto@gmail.com>
Date:   Sat Jan 15 15:02:57 2022 +0100

    ALSA: usb-audio: add mapping for MSI MPG X570S Carbon Max Wifi.
    
    The USB audio device 0db0:419c based on the Realtek ALC4080 chip exposes
    all playback volume controls as "PCM". This is makes distinguishing the
    individual functions hard.
    
    The added mapping distinguishes all playback volume controls as their
    respective function:
     - Speaker              - for back panel output
     - Frontpanel Headphone - for front panel output
     - IEC958               - for digital output on the back panel
    
    This clarifies the individual volume control functions for users.
    
    Signed-off-by: Johannes Schickel <lordhoto@gmail.com>
    Link: https://lore.kernel.org/r/20220115140257.8751-1-lordhoto@gmail.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 4d66020dcef83314092f2c8c89152a8d122627e2
Merge: 77dbd72b982ca f37c3bbc63599
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 10:15:32 2022 +0200

    Merge tag 'trace-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
    
    Pull tracing updates from Steven Rostedt:
     "New:
    
       - The Real Time Linux Analysis (RTLA) tool is added to the tools
         directory.
    
       - Can safely filter on user space pointers with: field.ustring ~
         "match-string"
    
       - eprobes can now be filtered like any other event.
    
       - trace_marker(_raw) now uses stream_open() to allow multiple threads
         to safely write to it. Note, this could possibly break existing
         user space, but we will not know until we hear about it, and then
         can revert the change if need be.
    
       - New field in events to display when bottom halfs are disabled.
    
       - Sorting of the ftrace functions are now done at compile time
         instead of at bootup.
    
      Infrastructure changes to support future efforts:
    
       - Added __rel_loc type for trace events. Similar to __data_loc but
         the offset to the dynamic data is based off of the location of the
         descriptor and not the beginning of the event. Needed for user
         defined events.
    
       - Some simplification of event trigger code.
    
       - Make synthetic events process its callback better to not hinder
         other event callbacks that are registered. Needed for user defined
         events.
    
      And other small fixes and cleanups"
    
    * tag 'trace-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: (50 commits)
      tracing: Add ustring operation to filtering string pointers
      rtla: Add rtla timerlat hist documentation
      rtla: Add rtla timerlat top documentation
      rtla: Add rtla timerlat documentation
      rtla: Add rtla osnoise hist documentation
      rtla: Add rtla osnoise top documentation
      rtla: Add rtla osnoise man page
      rtla: Add Documentation
      rtla/timerlat: Add timerlat hist mode
      rtla: Add timerlat tool and timelart top mode
      rtla/osnoise: Add the hist mode
      rtla/osnoise: Add osnoise top mode
      rtla: Add osnoise tool
      rtla: Helper functions for rtla
      rtla: Real-Time Linux Analysis tool
      tracing/osnoise: Properly unhook events if start_per_cpu_kthreads() fails
      tracing: Remove duplicate warnings when calling trace_create_file()
      tracing/kprobes: 'nmissed' not showed correctly for kretprobe
      tracing: Add test for user space strings when filtering on string pointers
      tracing: Have syscall trace events use trace_event_buffer_lock_reserve()
      ...

commit 77dbd72b982ca648b42b4feac5f8b2ea55e4ed09
Merge: d0a231f01e5b2 b2dfc3fe73b5b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 10:08:13 2022 +0200

    Merge tag 'livepatching-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching
    
    Pull livepatching updates from Petr Mladek:
    
     - Correctly handle kobjects when a livepatch init fails
    
     - Avoid CPU hogging when searching for many livepatched symbols
    
     - Add livepatch API page into documentation
    
    * tag 'livepatching-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching:
      livepatch: Avoid CPU hogging with cond_resched
      livepatch: Fix missing unlock on error in klp_enable_patch()
      livepatch: Fix kobject refcount bug on klp_init_patch_early failure path
      Documentation: livepatch: Add livepatch API page

commit d0a231f01e5b25bacd23e6edc7c979a18a517b2b
Merge: 88db8458086b1 87c71931633bd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 08:08:11 2022 +0200

    Merge tag 'pci-v5.17-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci
    
    Pull pci updates from Bjorn Helgaas:
     "Enumeration:
       - Use pci_find_vsec_capability() instead of open-coding it (Andy
         Shevchenko)
       - Convert pci_dev_present() stub from macro to static inline to avoid
         'unused variable' errors (Hans de Goede)
       - Convert sysfs slot attributes from default_attrs to default_groups
         (Greg Kroah-Hartman)
       - Use DWORD accesses for LTR, L1 SS to avoid BayHub OZ711LV2 erratum
         (Rajat Jain)
       - Remove unnecessary initialization of static variables (Longji Guo)
    
      Resource management:
       - Always write Intel I210 ROM BAR on update to work around device
         defect (Bjorn Helgaas)
    
      PCIe native device hotplug:
       - Fix pciehp lockdep errors on Thunderbolt undock (Hans de Goede)
       - Fix infinite loop in pciehp IRQ handler on power fault (Lukas
         Wunner)
    
      Power management:
       - Convert amd64-agp, sis-agp, via-agp from legacy PCI power
         management to generic power management (Vaibhav Gupta)
    
      IOMMU:
       - Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
         so it can work with an IOMMU (Yifeng Li)
    
      Error handling:
       - Add PCI_ERROR_RESPONSE and related definitions for signaling and
         checking for transaction errors on PCI (Naveen Naidu)
       - Fabricate PCI_ERROR_RESPONSE data (~0) in config read wrappers,
         instead of in host controller drivers, when transactions fail on
         PCI (Naveen Naidu)
       - Use PCI_POSSIBLE_ERROR() to check for possible failure of config
         reads (Naveen Naidu)
    
      Peer-to-peer DMA:
       - Add Logan Gunthorpe as P2PDMA maintainer (Bjorn Helgaas)
    
      ASPM:
       - Calculate link L0s and L1 exit latencies when needed instead of
         caching them (Saheed O. Bolarinwa)
       - Calculate device L0s and L1 acceptable exit latencies when needed
         instead of caching them (Saheed O. Bolarinwa)
       - Remove struct aspm_latency since it's no longer needed (Saheed O.
         Bolarinwa)
    
      APM X-Gene PCIe controller driver:
       - Fix IB window setup, which was broken by the fact that IB resources
         are now sorted in address order instead of DT dma-ranges order (Rob
         Herring)
    
      Apple PCIe controller driver:
       - Enable clock gating to save power (Hector Martin)
       - Fix REFCLK1 enable/poll logic (Hector Martin)
    
      Broadcom STB PCIe controller driver:
       - Declare bitmap correctly for use by bitmap interfaces (Christophe
         JAILLET)
       - Clean up computation of legacy and non-legacy MSI bitmasks (Florian
         Fainelli)
       - Update suspend/resume/remove error handling to warn about errors
         and not fail the operation (Jim Quinlan)
       - Correct the "pcie" and "msi" interrupt descriptions in DT binding
         (Jim Quinlan)
       - Add DT bindings for endpoint voltage regulators (Jim Quinlan)
       - Split brcm_pcie_setup() into two functions (Jim Quinlan)
       - Add mechanism for turning on voltage regulators for connected
         devices (Jim Quinlan)
       - Turn voltage regulators for connected devices on/off when bus is
         added or removed (Jim Quinlan)
       - When suspending, don't turn off voltage regulators for wakeup
         devices (Jim Quinlan)
    
      Freescale i.MX6 PCIe controller driver:
       - Add i.MX8MM support (Richard Zhu)
    
      Freescale Layerscape PCIe controller driver:
       - Use DWC common ops instead of layerscape-specific link-up functions
         (Hou Zhiqiang)
    
      Intel VMD host bridge driver:
       - Honor platform ACPI _OSC feature negotiation for Root Ports below
         VMD (Kai-Heng Feng)
       - Add support for Raptor Lake SKUs (Karthik L Gopalakrishnan)
       - Reset everything below VMD before enumerating to work around
         failure to enumerate NVMe devices when guest OS reboots (Nirmal
         Patel)
    
      Bridge emulation (used by Marvell Aardvark and MVEBU):
       - Make emulated ROM BAR read-only by default (Pali Rohár)
       - Make some emulated legacy PCI bits read-only for PCIe devices (Pali
         Rohár)
       - Update reserved bits in emulated PCIe Capability (Pali Rohár)
       - Allow drivers to emulate different PCIe Capability versions (Pali
         Rohár)
       - Set emulated Capabilities List bit for all PCIe devices, since they
         must have at least a PCIe Capability (Pali Rohár)
    
      Marvell Aardvark PCIe controller driver:
       - Add bridge emulation definitions for PCIe DEVCAP2, DEVCTL2,
         DEVSTA2, LNKCAP2, LNKCTL2, LNKSTA2, SLTCAP2, SLTCTL2, SLTSTA2 (Pali
         Rohár)
       - Add aardvark support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2
         registers (Pali Rohár)
       - Clear all MSIs at setup to avoid spurious interrupts (Pali Rohár)
       - Disable bus mastering when unbinding host controller driver (Pali
         Rohár)
       - Mask all interrupts when unbinding host controller driver (Pali
         Rohár)
       - Fix memory leak in host controller unbind (Pali Rohár)
       - Assert PERST# when unbinding host controller driver (Pali Rohár)
       - Disable link training when unbinding host controller driver (Pali
         Rohár)
       - Disable common PHY when unbinding host controller driver (Pali
         Rohár)
       - Fix resource type checking to check only IORESOURCE_MEM, not
         IORESOURCE_MEM_64, which is a flavor of IORESOURCE_MEM (Pali Rohár)
    
      Marvell MVEBU PCIe controller driver:
       - Implement pci_remap_iospace() for ARM so mvebu can use
         devm_pci_remap_iospace() instead of the previous ARM-specific
         pci_ioremap_io() interface (Pali Rohár)
       - Use the standard pci_host_probe() instead of the device-specific
         mvebu_pci_host_probe() (Pali Rohár)
       - Replace all uses of ARM-specific pci_ioremap_io() with the ARM
         implementation of the standard pci_remap_iospace() interface and
         remove pci_ioremap_io() (Pali Rohár)
       - Skip initializing invalid Root Ports (Pali Rohár)
       - Check for errors from pci_bridge_emul_init() (Pali Rohár)
       - Ignore any bridges at non-zero function numbers (Pali Rohár)
       - Return ~0 data for invalid config read size (Pali Rohár)
       - Disallow mapping interrupts on emulated bridges (Pali Rohár)
       - Clear Root Port Memory & I/O Space Enable and Bus Master Enable at
         initialization (Pali Rohár)
       - Make type bits in Root Port I/O Base register read-only (Pali
         Rohár)
       - Disable Root Port windows when base/limit set to invalid values
         (Pali Rohár)
       - Set controller to Root Complex mode (Pali Rohár)
       - Set Root Port Class Code to PCI Bridge (Pali Rohár)
       - Update emulated Root Port secondary bus numbers to better reflect
         the actual topology (Pali Rohár)
       - Add PCI_BRIDGE_CTL_BUS_RESET support to emulated Root Ports so
         pci_reset_secondary_bus() can reset connected devices (Pali Rohár)
       - Add PCI_EXP_DEVCTL Error Reporting Enable support to emulated Root
         Ports (Pali Rohár)
       - Add PCI_EXP_RTSTA PME Status bit support to emulated Root Ports
         (Pali Rohár)
       - Add DEVCAP2, DEVCTL2 and LNKCTL2 support to emulated Root Ports on
         Armada XP and newer devices (Pali Rohár)
       - Export mvebu-mbus.c symbols to allow pci-mvebu.c to be a module
         (Pali Rohár)
       - Add support for compiling as a module (Pali Rohár)
    
      MediaTek PCIe controller driver:
       - Assert PERST# for 100ms to allow power and clock to stabilize
         (qizhong cheng)
    
      MediaTek PCIe Gen3 controller driver:
       - Disable Mediatek DVFSRC voltage request since lack of DVFSRC to
         respond to the request causes failure to exit L1 PM Substate
         (Jianjun Wang)
    
      MediaTek MT7621 PCIe controller driver:
       - Declare mt7621_pci_ops static (Sergio Paracuellos)
       - Give pcibios_root_bridge_prepare() access to host bridge windows
         (Sergio Paracuellos)
       - Move MIPS I/O coherency unit setup from driver to
         pcibios_root_bridge_prepare() (Sergio Paracuellos)
       - Add missing MODULE_LICENSE() (Sergio Paracuellos)
       - Allow COMPILE_TEST for all arches (Sergio Paracuellos)
    
      Microsoft Hyper-V host bridge driver:
       - Add hv-internal interfaces to encapsulate arch IRQ dependencies
         (Sunil Muthuswamy)
       - Add arm64 Hyper-V vPCI support (Sunil Muthuswamy)
    
      Qualcomm PCIe controller driver:
       - Undo PM setup in qcom_pcie_probe() error handling path (Christophe
         JAILLET)
       - Use __be16 type to store return value from cpu_to_be16()
         (Manivannan Sadhasivam)
       - Constify static dw_pcie_ep_ops (Rikard Falkeborn)
    
      Renesas R-Car PCIe controller driver:
       - Fix aarch32 abort handler so it doesn't check the wrong bus clock
         before accessing the host controller (Marek Vasut)
    
      TI Keystone PCIe controller driver:
       - Add register offset for ti,syscon-pcie-id and ti,syscon-pcie-mode
         DT properties (Kishon Vijay Abraham I)
    
      MicroSemi Switchtec management driver:
       - Add Gen4 automotive device IDs (Kelvin Cao)
       - Declare state_names[] as static so it's not allocated and
         initialized for every call (Kelvin Cao)
    
      Host controller driver cleanups:
       - Use of_device_get_match_data(), not of_match_device(), when we only
         need the device data in altera, artpec6, cadence, designware-plat,
         dra7xx, keystone, kirin (Fan Fei)
       - Drop pointless of_device_get_match_data() cast in j721e (Bjorn
         Helgaas)
       - Drop redundant struct device * from j721e since struct cdns_pcie
         already has one (Bjorn Helgaas)
       - Rename driver structs to *_pcie in intel-gw, iproc, ls-gen4,
         mediatek-gen3, microchip, mt7621, rcar-gen2, tegra194, uniphier,
         xgene, xilinx, xilinx-cpm for consistency across drivers (Fan Fei)
       - Fix invalid address space conversions in hisi, spear13xx (Bjorn
         Helgaas)
    
      Miscellaneous:
       - Sort Intel Device IDs by value (Andy Shevchenko)
       - Change Capability offsets to hex to match spec (Baruch Siach)
       - Correct misspellings (Krzysztof Wilczyński)
       - Terminate statement with semicolon in pci_endpoint_test.c (Ming
         Wang)"
    
    * tag 'pci-v5.17-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci: (151 commits)
      PCI: mt7621: Allow COMPILE_TEST for all arches
      PCI: mt7621: Add missing MODULE_LICENSE()
      PCI: mt7621: Move MIPS setup to pcibios_root_bridge_prepare()
      PCI: Let pcibios_root_bridge_prepare() access bridge->windows
      PCI: mt7621: Declare mt7621_pci_ops static
      PCI: brcmstb: Do not turn off WOL regulators on suspend
      PCI: brcmstb: Add control of subdevice voltage regulators
      PCI: brcmstb: Add mechanism to turn on subdev regulators
      PCI: brcmstb: Split brcm_pcie_setup() into two funcs
      dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators
      dt-bindings: PCI: Correct brcmstb interrupts, interrupt-map.
      PCI: brcmstb: Fix function return value handling
      PCI: brcmstb: Do not use __GENMASK
      PCI: brcmstb: Declare 'used' as bitmap, not unsigned long
      PCI: hv: Add arm64 Hyper-V vPCI support
      PCI: hv: Make the code arch neutral by adding arch specific interfaces
      PCI: pciehp: Use down_read/write_nested(reset_lock) to fix lockdep errors
      x86/PCI: Remove initialization of static variables to false
      PCI: Use DWORD accesses for LTR, L1 SS to avoid erratum
      misc: pci_endpoint_test: Terminate statement with semicolon
      ...

commit 88db8458086b1dcf20b56682504bdb34d2bca0e2
Merge: 175398a0972bc 3d966521a8240
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 07:54:11 2022 +0200

    Merge tag 'exfat-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat
    
    Pull exfat updates from Namjae Jeon:
    
     - Fix ->i_blocks truncation issue that still exists elsewhere.
    
     - Four cleanups & typos fixes.
    
     - Move super block magic number to magic.h
    
     - Fix missing REQ_SYNC in exfat_update_bhs().
    
    * tag 'exfat-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/linkinjeon/exfat:
      exfat: fix missing REQ_SYNC in exfat_update_bhs()
      exfat: remove argument 'sector' from exfat_get_dentry()
      exfat: move super block magic number to magic.h
      exfat: fix i_blocks for files truncated over 4 GiB
      exfat: reuse exfat_inode_info variable instead of calling EXFAT_I()
      exfat: make exfat_find_location() static
      exfat: fix typos in comments
      exfat: simplify is_valid_cluster()

commit 175398a0972bc3ca1e824be324f17d8318357eba
Merge: 49ad227d54e84 1672086167539
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 07:42:58 2022 +0200

    Merge tag 'nfsd-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
    
    Pull nfsd updates from Chuck Lever:
     "Bruce has announced he is leaving Red Hat at the end of the month and
      is stepping back from his role as NFSD co-maintainer. As a result,
      this includes a patch removing him from the MAINTAINERS file.
    
      There is one patch in here that Jeff Layton was carrying in the locks
      tree. Since he had only one for this cycle, he asked us to send it to
      you via the nfsd tree.
    
      There continues to be 0-day reports from Robert Morris @MIT. This time
      we include a fix for a crash in the COPY_NOTIFY operation.
    
      Highlights:
       - Bruce steps down as NFSD maintainer
       - Prepare for dynamic nfsd thread management
       - More work on supporting re-exporting NFS mounts
       - One fs/locks patch on behalf of Jeff Layton
    
      Notable bug fixes:
       - Fix zero-length NFSv3 WRITEs
       - Fix directory cinfo on FS's that do not support iversion
       - Fix WRITE verifiers for stable writes
       - Fix crash on COPY_NOTIFY with a special state ID"
    
    * tag 'nfsd-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux: (51 commits)
      SUNRPC: Fix sockaddr handling in svcsock_accept_class trace points
      SUNRPC: Fix sockaddr handling in the svc_xprt_create_error trace point
      fs/locks: fix fcntl_getlk64/fcntl_setlk64 stub prototypes
      nfsd: fix crash on COPY_NOTIFY with special stateid
      MAINTAINERS: remove bfields
      NFSD: Move fill_pre_wcc() and fill_post_wcc()
      Revert "nfsd: skip some unnecessary stats in the v4 case"
      NFSD: Trace boot verifier resets
      NFSD: Rename boot verifier functions
      NFSD: Clean up the nfsd_net::nfssvc_boot field
      NFSD: Write verifier might go backwards
      nfsd: Add a tracepoint for errors in nfsd4_clone_file_range()
      NFSD: De-duplicate net_generic(nf->nf_net, nfsd_net_id)
      NFSD: De-duplicate net_generic(SVC_NET(rqstp), nfsd_net_id)
      NFSD: Clean up nfsd_vfs_write()
      nfsd: Replace use of rwsem with errseq_t
      NFSD: Fix verifier returned in stable WRITEs
      nfsd: Retry once in nfsd_open on an -EOPENSTALE return
      nfsd: Add errno mapping for EREMOTEIO
      nfsd: map EBADF
      ...

commit 49ad227d54e842f436ed0122cb7c901d857b86cb
Merge: 59d41458f143b 19d1c32652bbb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 07:36:49 2022 +0200

    Merge tag '9p-for-5.17-rc1' of git://github.com/martinetd/linux
    
    Pull 9p updates from Dominique Martinet:
     "Fixes, split 9p_net_fd, and new reviewer:
    
       - fix possible uninitialized memory usage for setattr
    
       - fix fscache reading hole in a file just after it's been grown
    
       - split net/9p/trans_fd.c in its own module like other transports.
    
         The new transport module defaults to 9P_NET and is autoloaded if
         required so users should not be impacted
    
       - add Christian Schoenebeck to 9p reviewers
    
       - some more trivial cleanup"
    
    * tag '9p-for-5.17-rc1' of git://github.com/martinetd/linux:
      9p: fix enodata when reading growing file
      net/9p: show error message if user 'msize' cannot be satisfied
      MAINTAINERS: 9p: add Christian Schoenebeck as reviewer
      9p: only copy valid iattrs in 9P2000.L setattr implementation
      9p: Use BUG_ON instead of if condition followed by BUG.
      net/p9: load default transports
      9p/xen: autoload when xenbus service is available
      9p/trans_fd: split into dedicated module
      fs: 9p: remove unneeded variable
      9p/trans_virtio: Fix typo in the comment for p9_virtio_create()

commit 59d41458f143b7a20997b1e78b5c15d9d3e998c3
Merge: 2aab34f873cc6 4efdddbce7c13
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 06:52:38 2022 +0200

    Merge tag 'drm-next-2022-01-14' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm fixes from Daniel Vetter:
    "drivers fixes:
    
       - i915 fixes for ttm backend + one pm wakelock fix
    
       - amdgpu fixes, fairly big pile of small things all over. Note this
         doesn't yet containe the fixed version of the otg sync patch that
         blew up
    
       - small driver fixes: meson, sun4i, vga16fb probe fix
    
      drm core fixes:
    
       - cma-buf heap locking
    
       - ttm compilation
    
       - self refresh helper state check
    
       - wrong error message in atomic helpers
    
       - mipi-dbi buffer mapping"
    
    * tag 'drm-next-2022-01-14' of git://anongit.freedesktop.org/drm/drm: (49 commits)
      drm/mipi-dbi: Fix source-buffer address in mipi_dbi_buf_copy
      drm: fix error found in some cases after the patch d1af5cd86997
      drm/ttm: fix compilation on ARCH=um
      dma-buf: cma_heap: Fix mutex locking section
      video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
      drm/amdkfd: Fix ASIC name typos
      drm/amdkfd: Fix DQM asserts on Hawaii
      drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
      drm/amd/pm: only send GmiPwrDnControl msg on master die (v3)
      drm/amdgpu: use spin_lock_irqsave to avoid deadlock by local interrupt
      drm/amdgpu: not return error on the init_apu_flags
      drm/amdkfd: Use prange->update_list head for remove_list
      drm/amdkfd: Use prange->list head for insert_list
      drm/amdkfd: make SPDX License expression more sound
      drm/amdkfd: Check for null pointer after calling kmemdup
      drm/amd/display: invalid parameter check in dmub_hpd_callback
      Revert "drm/amdgpu: Don't inherit GEM object VMAs in child process"
      drm/amd/display: reset dcn31 SMU mailbox on failures
      drm/amdkfd: use default_groups in kobj_type
      drm/amdgpu: use default_groups in kobj_type
      ...

commit 2aab34f873cc611cf195231c3738080c8dbda7f3
Merge: f56caedaf94f9 a59466ee91aaa
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jan 16 06:43:14 2022 +0200

    Merge tag 'memblock-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
    
    Pull memblock cleanup from Mike Rapoport:
     "Remove #ifdef __KERNEL__ from memblock.h
    
      memblock.h is not a uAPI header, so __KERNEL__ guard can be deleted"
    
    * tag 'memblock-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock:
      memblock: Remove #ifdef __KERNEL__ from memblock.h

commit 830af2eba40327abec64325a5b08b1e85c37a2e0
Author: Florian Westphal <fw@strlen.de>
Date:   Thu Jan 13 21:37:58 2022 +0100

    netfilter: conntrack: don't increment invalid counter on NF_REPEAT
    
    The packet isn't invalid, REPEAT means we're trying again after cleaning
    out a stale connection, e.g. via tcp tracker.
    
    This caused increases of invalid stat counter in a test case involving
    frequent connection reuse, even though no packet is actually invalid.
    
    Fixes: 56a62e2218f5 ("netfilter: conntrack: fix NF_REPEAT handling")
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 9404bc1e58e4bed41f629da9e3b890b2ca1f8b9c
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Fri Jan 14 21:35:45 2022 +0800

    net/smc: Remove unused function declaration
    
    The declaration of smc_wr_tx_dismiss_slots() is unused.
    So remove it.
    
    Fixes: 349d43127dac ("net/smc: fix kernel panic caused by race of smc_sock")
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Reviewed-by: Dust Li <dust.li@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f542cdfa3083a309e3caafbbdf41490c4935492a
Author: Slark Xiao <slark_xiao@163.com>
Date:   Sat Jan 15 10:34:30 2022 +0800

    net: wwan: Fix MRU mismatch issue which may lead to data connection lost
    
    In pci_generic.c there is a 'mru_default' in struct mhi_pci_dev_info.
    This value shall be used for whole mhi if it's given a value for a specific product.
    But in function mhi_net_rx_refill_work(), it's still using hard code value MHI_DEFAULT_MRU.
    'mru_default' shall have higher priority than MHI_DEFAULT_MRU.
    And after checking, this change could help fix a data connection lost issue.
    
    Fixes: 5c2c85315948 ("bus: mhi: pci-generic: configurable network interface MRU")
    Signed-off-by: Shujun Wang <wsj20369@163.com>
    Signed-off-by: Slark Xiao <slark_xiao@163.com>
    Reviewed-by: Loic Poulain <loic.poulain@linaro.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 020a45aff1190c32b1087cd75b57fbf6bff46ea6
Author: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
Date:   Sat Jan 15 17:25:15 2022 +0800

    net: phy: marvell: add Marvell specific PHY loopback
    
    Existing genphy_loopback() is not applicable for Marvell PHY. Besides
    configuring bit-6 and bit-13 in Page 0 Register 0 (Copper Control
    Register), it is also required to configure same bits  in Page 2
    Register 21 (MAC Specific Control Register 2) according to speed of
    the loopback is operating.
    
    Tested working on Marvell88E1510 PHY for all speeds (1000/100/10Mbps).
    
    FIXME: Based on trial and error test, it seem 1G need to have delay between
    soft reset and loopback enablement.
    
    Fixes: 014068dcb5b1 ("net: phy: genphy_loopback: add link speed configuration")
    Cc: <stable@vger.kernel.org> # 5.15.x
    Signed-off-by: Mohammad Athari Bin Ismail <mohammad.athari.ismail@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9a9acdccdfa430457986db608ee4ae4840107057
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 15 13:45:03 2022 +0100

    net: ethernet: sun4i-emac: Fix an error handling path in emac_probe()
    
    A dma_request_chan() call is hidden in emac_configure_dma().
    It must be released in the probe if an error occurs, as already done in
    the remove function.
    
    Add the corresponding dma_release_channel() call.
    
    Fixes: 47869e82c8b8 ("sun4i-emac.c: add dma support")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 214b3369ab9b0a6f28d6c970220c209417edbc65
Author: Tom Rix <trix@redhat.com>
Date:   Sat Jan 15 09:49:18 2022 -0800

    net: ethernet: mtk_eth_soc: fix error checking in mtk_mac_config()
    
    Clang static analysis reports this problem
    mtk_eth_soc.c:394:7: warning: Branch condition evaluates
      to a garbage value
                    if (err)
                        ^~~
    
    err is not initialized and only conditionally set.
    So intitialize err.
    
    Fixes: 7e538372694b ("net: ethernet: mediatek: Re-add support SGMII")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 80f15f3bef9e9c2cc29888a6773df44de0a0c65f
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Fri Jan 14 15:36:37 2022 +0200

    net: mscc: ocelot: don't dereference NULL pointers with shared tc filters
    
    The following command sequence:
    
    tc qdisc del dev swp0 clsact
    tc qdisc add dev swp0 ingress_block 1 clsact
    tc qdisc add dev swp1 ingress_block 1 clsact
    tc filter add block 1 flower action drop
    tc qdisc del dev swp0 clsact
    
    produces the following NPD:
    
    Unable to handle kernel NULL pointer dereference at virtual address 0000000000000014
    pc : vcap_entry_set+0x14/0x70
    lr : ocelot_vcap_filter_del+0x198/0x234
    Call trace:
     vcap_entry_set+0x14/0x70
     ocelot_vcap_filter_del+0x198/0x234
     ocelot_cls_flower_destroy+0x94/0xe4
     felix_cls_flower_del+0x70/0x84
     dsa_slave_setup_tc_block_cb+0x13c/0x60c
     dsa_slave_setup_tc_block_cb_ig+0x20/0x30
     tc_setup_cb_reoffload+0x44/0x120
     fl_reoffload+0x280/0x320
     tcf_block_playback_offloads+0x6c/0x184
     tcf_block_unbind+0x80/0xe0
     tcf_block_setup+0x174/0x214
     tcf_block_offload_cmd.isra.0+0x100/0x13c
     tcf_block_offload_unbind+0x5c/0xa0
     __tcf_block_put+0x54/0x174
     tcf_block_put_ext+0x5c/0x74
     clsact_destroy+0x40/0x60
     qdisc_destroy+0x4c/0x150
     qdisc_put+0x70/0x90
     qdisc_graft+0x3f0/0x4c0
     tc_get_qdisc+0x1cc/0x364
     rtnetlink_rcv_msg+0x124/0x340
    
    The reason is that the driver isn't prepared to receive two tc filters
    with the same cookie. It unconditionally creates a new struct
    ocelot_vcap_filter for each tc filter, and it adds all filters with the
    same identifier (cookie) to the ocelot_vcap_block.
    
    The problem is here, in ocelot_vcap_filter_del():
    
            /* Gets index of the filter */
            index = ocelot_vcap_block_get_filter_index(block, filter);
            if (index < 0)
                    return index;
    
            /* Delete filter */
            ocelot_vcap_block_remove_filter(ocelot, block, filter);
    
            /* Move up all the blocks over the deleted filter */
            for (i = index; i < block->count; i++) {
                    struct ocelot_vcap_filter *tmp;
    
                    tmp = ocelot_vcap_block_find_filter_by_index(block, i);
                    vcap_entry_set(ocelot, i, tmp);
            }
    
    what will happen is ocelot_vcap_block_get_filter_index() will return the
    index (@index) of the first filter found with that cookie. This is _not_
    the index of _this_ filter, but the other one with the same cookie,
    because ocelot_vcap_filter_equal() gets fooled.
    
    Then later, ocelot_vcap_block_remove_filter() is coded to remove all
    filters that are ocelot_vcap_filter_equal() with the passed @filter.
    So unexpectedly, both filters get deleted from the list.
    
    Then ocelot_vcap_filter_del() will attempt to move all the other filters
    up, again finding them by index (@i). The block count is 2, @index was 0,
    so it will attempt to move up filter @i=0 and @i=1. It assigns tmp =
    ocelot_vcap_block_find_filter_by_index(block, i), which is now a NULL
    pointer because ocelot_vcap_block_remove_filter() has removed more than
    one filter.
    
    As far as I can see, this problem has been there since the introduction
    of tc offload support, however I cannot test beyond the blamed commit
    due to hardware availability. In any case, any fix cannot be backported
    that far, due to lots of changes to the code base.
    
    Therefore, let's go for the correct solution, which is to not call
    ocelot_vcap_filter_add() and ocelot_vcap_filter_del(), unless the filter
    is actually unique and not shared. For the shared filters, we should
    just modify the ingress port mask and call ocelot_vcap_filter_replace(),
    a function introduced by commit 95706be13b9f ("net: mscc: ocelot: create
    a function that replaces an existing VCAP filter"). This way,
    block->rules will only contain filters with unique cookies, by design.
    
    Fixes: 07d985eef073 ("net: dsa: felix: Wire up the ocelot cls_flower methods")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9bce13ea88f85344b765abe5d3dabdd0f44dc177
Author: Jiri Olsa <jolsa@redhat.com>
Date:   Thu Dec 9 21:04:25 2021 +0100

    perf record: Disable debuginfod by default
    
    Fedora 35 sets DEBUGINFOD_URLS by default, which might lead to
    unexpected stalls in perf record exit path, when we try to cache
    profiled binaries.
    
      # DEBUGINFOD_PROGRESS=1 ./perf record -a
      ^C[ perf record: Woken up 1 times to write data ]
      Downloading from https://debuginfod.fedoraproject.org/ 447069
      Downloading from https://debuginfod.fedoraproject.org/ 1502175
      Downloading \^Z
    
    Disabling DEBUGINFOD_URLS by default in perf record and adding
    debuginfod option and .perfconfig variable support to enable id.
    
      Default without debuginfo processing:
      # perf record -a
    
      Using system debuginfod setup:
      # perf record -a --debuginfod
    
      Using custom debuginfd url:
      # perf record -a --debuginfod='https://evenbetterdebuginfodserver.krava'
    
    Adding single perf_debuginfod_setup function and using
    it also in perf buildid-cache command.
    
    Signed-off-by: Jiri Olsa <jolsa@kernel.org>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Frank Ch. Eigler <fche@redhat.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Michael Petlan <mpetlan@redhat.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20211209200425.303561-1-jolsa@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 2eea0b56b0d6ace0172550477220a25d633ec5b9
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sat Jan 15 17:15:09 2022 -0300

    perf evlist: No need to do any affinity setup when profiling pids
    
    The cpumap is dummy, so no need to go on figuring out affinity.o
    
    This way we reduce the setup time for simple scenarios like:
    
            $ perf stat sleep 1
    
    Acked-by: Andi Kleen <andi@firstfloor.org>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 37be585807cb9a810f8395c39c4ee7bdbdc7b0dc
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sat Jan 15 17:11:10 2022 -0300

    perf cpumap: Add is_dummy() method
    
    Needed to check if a cpu_map is dummy, i.e. not a cpu map at all, for
    pid monitoring scenarios.
    
    This probably needs to move to libperf, but since perf itself is the
    first and so far only user, leave it at tools/perf/util/.
    
    Acked-by: Andi Kleen <andi@firstfloor.org>
    Acked-by: Ian Rogers <irogers@google.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 762f99f4f3cb41a775b5157dd761217beba65873
Merge: cf73ed894ee93 b6e43dddaea3d
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Sat Jan 15 12:09:44 2022 -0800

    Merge branch 'next' into for-linus
    
    Prepare input updates for 5.17 merge window.

commit d3e2bb4359f70c8b1d09a6f8e2f57240aab0da3f
Author: Ian Rogers <irogers@google.com>
Date:   Fri Jan 14 22:28:52 2022 -0800

    perf metric: Fix metric_leader
    
    Multiple events may have a metric_leader to aggregate into.
    
    This happens for uncore events where, for example, uncore_imc is
    expanded into uncore_imc_0, uncore_imc_1, etc.
    
    Such events all have the same metric_id and should aggregate into the
    first event.
    
    The change introducing metric_ids had a bug where the metric_id was
    compared to itself, creating an always true condition.
    
    Correct this by comparing the event in the metric_evlist and the
    metric_leader.
    
    Fixes: ec5c5b3d2c21b3f3 ("perf metric: Encode and use metric-id as qualifier")
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: http://lore.kernel.org/lkml/20220115062852.1959424-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f56caedaf94f9ced5dbfcdb0060a3e788d2078af
Merge: a33f5c380c4bd 76fd0285b4479
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 15 20:37:06 2022 +0200

    Merge branch 'akpm' (patches from Andrew)
    
    Merge misc updates from Andrew Morton:
     "146 patches.
    
      Subsystems affected by this patch series: kthread, ia64, scripts,
      ntfs, squashfs, ocfs2, vfs, and mm (slab-generic, slab, kmemleak,
      dax, kasan, debug, pagecache, gup, shmem, frontswap, memremap,
      memcg, selftests, pagemap, dma, vmalloc, memory-failure, hugetlb,
      userfaultfd, vmscan, mempolicy, oom-kill, hugetlbfs, migration, thp,
      ksm, page-poison, percpu, rmap, zswap, zram, cleanups, hmm, and
      damon)"
    
    * emailed patches from Andrew Morton <akpm@linux-foundation.org>: (146 commits)
      mm/damon: hide kernel pointer from tracepoint event
      mm/damon/vaddr: hide kernel pointer from damon_va_three_regions() failure log
      mm/damon/vaddr: use pr_debug() for damon_va_three_regions() failure logging
      mm/damon/dbgfs: remove an unnecessary variable
      mm/damon: move the implementation of damon_insert_region to damon.h
      mm/damon: add access checking for hugetlb pages
      Docs/admin-guide/mm/damon/usage: update for schemes statistics
      mm/damon/dbgfs: support all DAMOS stats
      Docs/admin-guide/mm/damon/reclaim: document statistics parameters
      mm/damon/reclaim: provide reclamation statistics
      mm/damon/schemes: account how many times quota limit has exceeded
      mm/damon/schemes: account scheme actions that successfully applied
      mm/damon: remove a mistakenly added comment for a future feature
      Docs/admin-guide/mm/damon/usage: update for kdamond_pid and (mk|rm)_contexts
      Docs/admin-guide/mm/damon/usage: mention tracepoint at the beginning
      Docs/admin-guide/mm/damon/usage: remove redundant information
      Docs/admin-guide/mm/damon/usage: update for scheme quotas and watermarks
      mm/damon: convert macro functions to static inline functions
      mm/damon: modify damon_rand() macro to static inline function
      mm/damon: move damon_rand() definition into damon.h
      ...

commit 15325b4f768f2b27b5765489eeab6ec0d6b5e902
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:13 2021 -0700

    vsprintf: rework bitmap_list_string
    
    bitmap_list_string() is very ineffective when printing bitmaps with long
    ranges of set bits because it calls find_next_bit for each bit in the
    bitmap.  We can do better by detecting ranges of set bits.
    
    In my environment, before/after is 943008/31008 ns.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit db7313005e9c2d4e80888dd18d4a83926b920e8c
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:12 2021 -0700

    lib: bitmap: add performance test for bitmap_print_to_pagebuf
    
    Functional tests for bitmap_print_to_pagebuf() are provided
    in lib/test_printf.c. This patch adds performance test for
    a case of fully set bitmap.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit ec288a2cf7ca40a939316b6df206ab845bb112d1
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:11 2021 -0700

    bitmap: unify find_bit operations
    
    bitmap_for_each_{set,clear}_region() are similar to for_each_bit()
    macros in include/linux/find.h, but interface and implementation
    of them are different.
    
    This patch adds for_each_bitrange() macros and drops unused
    bitmap_*_region() API in sake of unification.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Acked-by: Dennis Zhou <dennis@kernel.org>
    Acked-by: Ulf Hansson <ulf.hansson@linaro.org> # For MMC

commit 801a57365fc836d7ec866e2069d0b21d79925c1e
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:10 2021 -0700

    mm/percpu: micro-optimize pcpu_is_populated()
    
    bitmap_next_clear_region() calls find_next_zero_bit() and find_next_bit()
    sequentially to find a range of clear bits. In case of pcpu_is_populated()
    there's a chance to return earlier if bitmap has all bits set.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Acked-by: Dennis Zhou <dennis@kernel.org>

commit 749443de8dde3b8b420ee8b4daac4d929a6adeb9
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:08 2021 -0700

    Replace for_each_*_bit_from() with for_each_*_bit() where appropriate
    
    A couple of kernel functions call for_each_*_bit_from() with start
    bit equal to 0. Replace them with for_each_*_bit().
    
    No functional changes, but might improve on readability.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 7516be9931b8bc8bcaac8531f490b42ab11ded1e
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:07 2021 -0700

    find: micro-optimize for_each_{set,clear}_bit()
    
    The macros iterate thru all set/clear bits in a bitmap. They search a
    first bit using find_first_bit(), and the rest bits using find_next_bit().
    
    Since find_next_bit() is called shortly after find_first_bit(), we can
    save few lines of I-cache by not using find_first_bit().
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit bc9d6635c293a2ac30c6319f7cfd08860ab7948a
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:06 2021 -0700

    include/linux: move for_each_bit() macros from bitops.h to find.h
    
    for_each_bit() macros depend on find_bit() machinery, and so the
    proper place for them is the find.h header.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 9b51d9d866482a703646fd4c07e433c3d9d88efd
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:05 2021 -0700

    cpumask: replace cpumask_next_* with cpumask_first_* where appropriate
    
    cpumask_first() is a more effective analogue of 'next' version if n == -1
    (which means start == 0). This patch replaces 'next' with 'first' where
    things look trivial.
    
    There's no cpumask_first_zero() function, so create it.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 4ade0818cf048bb166e875ed4f8b456e6c2c7b3c
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:04 2021 -0700

    tools: sync tools/bitmap with mother linux
    
    Remove tools/include/asm-generic/bitops/find.h and copy
    include/linux/bitmap.h to tools. find_*_le() functions are not copied
    because not needed in tools.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit b5c7e7ec7d3418af2544452b45cc67297c857a86
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:03 2021 -0700

    all: replace find_next{,_zero}_bit with find_first{,_zero}_bit where appropriate
    
    find_first{,_zero}_bit is a more effective analogue of 'next' version if
    start == 0. This patch replaces 'next' with 'first' where things look
    trivial.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 93ba139ba8190c33009c5353ca43c8519443f467
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:02 2021 -0700

    cpumask: use find_first_and_bit()
    
    Now we have an efficient implementation for find_first_and_bit(),
    so switch cpumask to use it where appropriate.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit f68edc9297bf3f7c94abb54b9b0b053607f7587b
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:01 2021 -0700

    lib: add find_first_and_bit()
    
    Currently find_first_and_bit() is an alias to find_next_and_bit(). However,
    it is widely used in cpumask, so it worth to optimize it. This patch adds
    its own implementation for find_first_and_bit().
    
    On x86_64 find_bit_benchmark says:
    
    Before (#define find_first_and_bit(...) find_next_and_bit(..., 0):
    Start testing find_bit() with random-filled bitmap
    [  140.291468] find_first_and_bit:           46890919 ns,  32671 iterations
    Start testing find_bit() with sparse bitmap
    [  140.295028] find_first_and_bit:               7103 ns,      1 iterations
    
    After:
    Start testing find_bit() with random-filled bitmap
    [  162.574907] find_first_and_bit:           25045813 ns,  32846 iterations
    Start testing find_bit() with sparse bitmap
    [  162.578458] find_first_and_bit:               4900 ns,      1 iterations
    
    (Thanks to Alexey Klimov for thorough testing.)
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Tested-by: Alexey Klimov <aklimov@redhat.com>

commit c126a53c276048125b4a950072bab37ad0fea120
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:17:00 2021 -0700

    arch: remove GENERIC_FIND_FIRST_BIT entirely
    
    In 5.12 cycle we enabled GENERIC_FIND_FIRST_BIT config option for ARM64
    and MIPS. It increased performance and shrunk .text size; and so far
    I didn't receive any negative feedback on the change.
    
    https://lore.kernel.org/linux-arch/20210225135700.1381396-1-yury.norov@gmail.com/
    
    Now I think it's a good time to switch all architectures to use
    find_{first,last}_bit() unconditionally, and so remove corresponding
    config option.
    
    The patch does't introduce functioal changes for arc, arm, arm64, mips,
    m68k, s390 and x86, for other architectures I expect improvement both in
    performance and .text size.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Alexander Lobakin <alobakin@pm.me> (mips)
    Reviewed-by: Alexander Lobakin <alobakin@pm.me> (mips)
    Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Acked-by: Will Deacon <will@kernel.org>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 47d8c15615c0a2046d2d90b04cb80b81ddf31fb1
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:16:59 2021 -0700

    include: move find.h from asm_generic to linux
    
    find_bit API and bitmap API are closely related, but inclusion paths
    are different - include/asm-generic and include/linux, correspondingly.
    In the past it made a lot of troubles due to circular dependencies
    and/or undefined symbols. Fix this by moving find.h under include/linux.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

commit 6b8ecb84f8f64017ae6e56cd745ad88e48f68779
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:16:58 2021 -0700

    bitops: move find_bit_*_le functions from le.h to find.h
    
    It's convenient to have all find_bit declarations in one place.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit b7ec62d7ee0f0b8af6ba190501dff7f9ee6545ca
Author: Yury Norov <yury.norov@gmail.com>
Date:   Sat Aug 14 14:16:57 2021 -0700

    bitops: protect find_first_{,zero}_bit properly
    
    find_first_bit() and find_first_zero_bit() are not protected with
    ifdefs as other functions in find.h. It causes build errors on some
    platforms if CONFIG_GENERIC_FIND_FIRST_BIT is enabled.
    
    Signed-off-by: Yury Norov <yury.norov@gmail.com>
    Fixes: 2cc7b6a44ac2 ("lib: add fast path for find_first_*_bit() and find_last_bit()")
    Reported-by: kernel test robot <lkp@intel.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

commit 9bbf8662a27b56358366027d1a77c0676f85b222
Author: Eugene Korenevsky <ekorenevsky@astralinux.ru>
Date:   Tue Jan 11 11:36:50 2022 +0300

    cifs: fix FILE_BOTH_DIRECTORY_INFO definition
    
    The size of FILE_BOTH_DIRECTORY_INFO.ShortName must be 24 bytes, not 12
    (see MS-FSCC documentation).
    
    Signed-off-by: Eugene Korenevsky <ekorenevsky@astralinux.ru>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit dea2903719283c156b53741126228c4a1b40440f
Author: Jeff Layton <jlayton@kernel.org>
Date:   Mon Jan 10 19:00:02 2022 -0500

    cifs: move superblock magic defitions to magic.h
    
    Help userland apps to identify cifs and smb2 mounts.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 3ac5f2f2574a8b9e219bb5872166e5db797e349d
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Wed Jan 5 17:39:09 2022 +0800

    cifs: Fix smb311_update_preauth_hash() kernel-doc comment
    
    Add the description of @server in smb311_update_preauth_hash()
    kernel-doc comment to remove warning found by running scripts/kernel-doc,
    which is caused by using 'make W=1'.
    fs/cifs/smb2misc.c:856: warning: Function parameter or member 'server'
    not described in 'smb311_update_preauth_hash'
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 76fd0285b447991267e838842c0be7395eb454bb
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:50 2022 -0800

    mm/damon: hide kernel pointer from tracepoint event
    
    DAMON's virtual address spaces monitoring primitive uses 'struct pid *'
    of the target process as its monitoring target id.  The kernel address
    is exposed as-is to the user space via the DAMON tracepoint,
    'damon_aggregated'.
    
    Though primarily only privileged users are allowed to access that, it
    would be better to avoid unnecessarily exposing kernel pointers so.
    Because the trace result is only required to be able to distinguish each
    target, we aren't need to use the pointer as-is.
    
    This makes the tracepoint to use the index of the target in the
    context's targets list as its id in the tracepoint, to hide the kernel
    space address.
    
    Link: https://lkml.kernel.org/r/20211229131016.23641-5-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 962fe7a6b1b2f9deb1b31b3344afa3b11afdf7ab
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:47 2022 -0800

    mm/damon/vaddr: hide kernel pointer from damon_va_three_regions() failure log
    
    The failure log message for 'damon_va_three_regions()' prints the target
    id, which is a 'struct pid' pointer in the case.  To avoid exposing the
    kernel pointer via the log, this makes the log to use the index of the
    target in the context's targets list instead.
    
    Link: https://lkml.kernel.org/r/20211229131016.23641-4-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 251403f19aab6a122f4dcfb14149814e85564202
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:44 2022 -0800

    mm/damon/vaddr: use pr_debug() for damon_va_three_regions() failure logging
    
    Failure of 'damon_va_three_regions()' is logged using 'pr_err()'.  But,
    the function can fail in legal situations.  To avoid making users be
    surprised and to keep the kernel clean, this makes the log to be printed
    using 'pr_debug()'.
    
    Link: https://lkml.kernel.org/r/20211229131016.23641-3-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 70b8480812d0a3930049a44820a1fa149b090c10
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:41 2022 -0800

    mm/damon/dbgfs: remove an unnecessary variable
    
    Patch series "mm/damon: Hide unnecessary information disclosures".
    
    DAMON is exposing some unnecessary information including kernel pointer
    in kernel log and tracepoint.  This patchset hides such information.
    The first patch is only for a trivial cleanup, though.
    
    This patch (of 4):
    
    This commit removes a unnecessarily used variable in
    dbgfs_target_ids_write().
    
    Link: https://lkml.kernel.org/r/20211229131016.23641-1-sj@kernel.org
    Link: https://lkml.kernel.org/r/20211229131016.23641-2-sj@kernel.org
    Fixes: 4bc05954d007 ("mm/damon: implement a debugfs-based user space interface")
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2cd4b8e10cc31eadb5b10b1d73b3f28156f3776c
Author: Guoqing Jiang <guoqing.jiang@linux.dev>
Date:   Fri Jan 14 14:10:38 2022 -0800

    mm/damon: move the implementation of damon_insert_region to damon.h
    
    Usually, inline function is declared static since it should sit between
    storage and type.  And implement it in a header file if used by multiple
    files.
    
    And this change also fixes compile issue when backport damon to 5.10.
    
      mm/damon/vaddr.c: In function `damon_va_evenly_split_region':
      ./include/linux/damon.h:425:13: error: inlining failed in call to `always_inline' `damon_insert_region': function body not available
      425 | inline void damon_insert_region(struct damon_region *r,
          | ^~~~~~~~~~~~~~~~~~~
      mm/damon/vaddr.c:86:3: note: called from here
      86 | damon_insert_region(n, r, next, t);
         | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    Link: https://lkml.kernel.org/r/20211223085703.6142-1-guoqing.jiang@linux.dev
    Signed-off-by: Guoqing Jiang <guoqing.jiang@linux.dev>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 49f4203aae06ba9d67b500c90339b262b0a52637
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:10:35 2022 -0800

    mm/damon: add access checking for hugetlb pages
    
    The process's VMAs can be mapped by hugetlb page, but now the DAMON did
    not implement the access checking for hugetlb pte, so we can not get the
    actual access count like below if a process VMAs were mapped by hugetlb.
    
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 4194304-5476352: 0 545
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 140662370467840-140662372970496: 0 545
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 140662372970496-140662375460864: 0 545
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 140662375460864-140662377951232: 0 545
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 140662377951232-140662380449792: 0 545
      damon_aggregated: target_id=18446614368406014464 nr_regions=12 140662380449792-140662382944256: 0 545
      ......
    
    Thus this patch adds hugetlb access checking support, with this patch we
    can see below VMA mapped by hugetlb access count.
    
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296486649856-140296489914368: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296489914368-140296492978176: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296492978176-140296495439872: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296495439872-140296498311168: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296498311168-140296501198848: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296501198848-140296504320000: 1 3
      damon_aggregated: target_id=18446613056935405824 nr_regions=12 140296504320000-140296507568128: 1 2
      ......
    
    [baolin.wang@linux.alibaba.com: fix unused var warning]
      Link: https://lkml.kernel.org/r/1aaf9c11-0d8e-b92d-5c92-46e50a6e8d4e@linux.alibaba.com
    [baolin.wang@linux.alibaba.com: v3]
      Link: https://lkml.kernel.org/r/486927ecaaaecf2e3a7fbe0378ec6e1c58b50747.1640852276.git.baolin.wang@linux.alibaba.com
    
    Link: https://lkml.kernel.org/r/6afcbd1fda5f9c7c24f320d26a98188c727ceec3.1639623751.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dbcb9b9f954f71fb46be34af624c9edaaa171414
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:32 2022 -0800

    Docs/admin-guide/mm/damon/usage: update for schemes statistics
    
    This updates DAMON debugfs interface for statistics of schemes
    successfully applied regions and time/space quota limit exceeds counts.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-7-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3a619fdb8de8a3ecd4200e7d183d2c8ceb32289e
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:29 2022 -0800

    mm/damon/dbgfs: support all DAMOS stats
    
    Currently, DAMON debugfs interface is not supporting DAMON-based
    Operation Schemes (DAMOS) stats for schemes successfully applied regions
    and time/space quota limit exceeds.  This adds the support.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-6-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 81f0895f1f5ed0d2bb80559ba9fbc6ce814e7235
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:26 2022 -0800

    Docs/admin-guide/mm/damon/reclaim: document statistics parameters
    
    This adds descriptions for the DAMON_RECLAIM statistics parameters.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-5-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 60e52e7c46a127bca5ddd48b89002564f3862063
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:23 2022 -0800

    mm/damon/reclaim: provide reclamation statistics
    
    This implements new DAMON_RECLAIM parameters for statistics reporting.
    Those can be used for understanding how DAMON_RECLAIM is working, and
    for tuning the other parameters.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-4-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6268eac34ca30af7f6313504d556ec7fcd295621
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:20 2022 -0800

    mm/damon/schemes: account how many times quota limit has exceeded
    
    If the time/space quotas of a given DAMON-based operation scheme is too
    small, the scheme could show unexpectedly slow progress.  However, there
    is no good way to notice the case in runtime.  This commit extends the
    DAMOS stat to provide how many times the quota limits exceeded so that
    the users can easily notice the case and tune the scheme.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-3-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0e92c2ee9f459542c5384d9cfab24873c3dd6398
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:17 2022 -0800

    mm/damon/schemes: account scheme actions that successfully applied
    
    Patch series "mm/damon/schemes: Extend stats for better online analysis and tuning".
    
    To help online access pattern analysis and tuning of DAMON-based
    Operation Schemes (DAMOS), DAMOS provides simple statistics for each
    scheme.  Introduction of DAMOS time/space quota further made the tuning
    easier by making the risk management easier.  However, that also made
    understanding of the working schemes a little bit more difficult.
    
    For an example, progress of a given scheme can now be throttled by not
    only the aggressiveness of the target access pattern, but also the
    time/space quotas.  So, when a scheme is showing unexpectedly slow
    progress, it's difficult to know by what the progress of the scheme is
    throttled, with currently provided statistics.
    
    This patchset extends the statistics to contain some metrics that can be
    helpful for such online schemes analysis and tuning (patches 1-2),
    exports those to users (patches 3 and 5), and add documents (patches 4
    and 6).
    
    This patch (of 6):
    
    DAMON-based operation schemes (DAMOS) stats provide only the number and
    the amount of regions that the action of the scheme has tried to be
    applied.  Because the action could be failed for some reasons, the
    currently provided information is sometimes not useful or convenient
    enough for schemes profiling and tuning.  To improve this situation,
    this commit extends the DAMOS stats to provide the number and the amount
    of regions that the action has successfully applied.
    
    Link: https://lkml.kernel.org/r/20211210150016.35349-1-sj@kernel.org
    Link: https://lkml.kernel.org/r/20211210150016.35349-2-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f4c6d22c6cf282ef7d24a724b9bd978ee2b74fc6
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:14 2022 -0800

    mm/damon: remove a mistakenly added comment for a future feature
    
    Due to a mistake in patches reordering, a comment for a future feature
    called 'arbitrary monitoring target support'[1], which is still under
    development, has added.  Because it only introduces confusion and we
    don't have a plan to post the patches soon, this commit removes the
    mistakenly added part.
    
    [1] https://lore.kernel.org/linux-mm/20201215115448.25633-3-sjpark@amazon.com/
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-7-sj@kernel.org
    Fixes: 1f366e421c8f ("mm/damon/core: implement DAMON-based Operation Schemes (DAMOS)")
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 995d739cde879a35ef6e890ecf80226b605ad36c
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:11 2022 -0800

    Docs/admin-guide/mm/damon/usage: update for kdamond_pid and (mk|rm)_contexts
    
    The DAMON debugfs usage document is missing descriptions for
    'kdamond_pid', 'mk_contexts', and 'rm_contexts' debugfs files.  This
    commit adds those.
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-6-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4492bf452af532493b6591d2e090a0f8f7c11674
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:08 2022 -0800

    Docs/admin-guide/mm/damon/usage: mention tracepoint at the beginning
    
    To get detailed monitoring results from the user space, users need to
    use the damon_aggregated tracepoint.  This commit adds a brief mention
    of it at the beginning of the usage document.
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-5-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 35b43d4092008ad33d3bcccee4b262ffbf8a551c
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:05 2022 -0800

    Docs/admin-guide/mm/damon/usage: remove redundant information
    
    DAMON usage document mentions DAMON user space tool and programming
    interface twice.  This commit integrates those and remove unnecessary
    part.
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-4-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6322416b2d51f359efa7d875ab28bd195a5eb230
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:10:02 2022 -0800

    Docs/admin-guide/mm/damon/usage: update for scheme quotas and watermarks
    
    DAMOS features including time/space quota limits and watermarks are not
    described in the DAMON debugfs interface document.  This commit updates
    the document for the features.
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-3-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 88f86dcfa454784f7de550966c60fc78a3e95d6d
Author: SeongJae Park <sj@kernel.org>
Date:   Fri Jan 14 14:09:59 2022 -0800

    mm/damon: convert macro functions to static inline functions
    
    Patch series "mm/damon: Misc cleanups".
    
    This patchset contains miscellaneous cleanups for DAMON's macro
    functions and documentation.
    
    This patch (of 6):
    
    This commit converts macro functions in DAMON to static inline functions,
    for better type checking, code documentation, etc[1].
    
    [1] https://lore.kernel.org/linux-mm/20211202151213.6ec830863342220da4141bc5@linux-foundation.org/
    
    Link: https://lkml.kernel.org/r/20211209131806.19317-1-sj@kernel.org
    Link: https://lkml.kernel.org/r/20211209131806.19317-2-sj@kernel.org
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 234d68732b6c135087bdebfa0630a43ae8c27758
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:56 2022 -0800

    mm/damon: modify damon_rand() macro to static inline function
    
    damon_rand() cannot be implemented as a macro.
    
    Example:
            damon_rand(a++, b);
    
    The value of 'a' will be incremented twice, This is obviously
    unreasonable, So there fix it.
    
    Link: https://lkml.kernel.org/r/110ffcd4e420c86c42b41ce2bc9f0fe6a4f32cd3.1638795127.git.xhao@linux.alibaba.com
    Fixes: b9a6ac4e4ede ("mm/damon: adaptively adjust regions")
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reported-by: Andrew Morton <akpm@linux-foundation.org>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9b2a38d6ef25c1748e3964b0ff30a89e4ed26583
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:53 2022 -0800

    mm/damon: move damon_rand() definition into damon.h
    
    damon_rand() is called in three files:damon/core.c, damon/ paddr.c,
    damon/vaddr.c, i think there is no need to redefine this twice, So move
    it to damon.h will be a good choice.
    
    Link: https://lkml.kernel.org/r/20211202075859.51341-1-xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c89ae63eb0662b6c9f82dbfad3ef010239b8c1b1
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:50 2022 -0800

    mm/damon/schemes: add the validity judgment of thresholds
    
    In dbgfs "schemes" interface, i do some test like this:
        # cd /sys/kernel/debug/damon
        # echo "2 1 2 1 10 1 3 10 1 1 1 1 1 1 1 1 2 3" > schemes
        # cat schemes
        # 2 1 2 1 10 1 3 10 1 1 1 1 1 1 1 1 2 3 0 0
    
    There have some unreasonable places, i set the valules of these variables
    "<min_sz, max_sz> <min_nr_a, max_nr_a>, <min_age, max_age>, <wmarks.high,
    wmarks.mid, wmarks.low>" as "<2, 1>, <2, 1>, <10, 1>, <1, 2, 3>.
    
    So there add a validity judgment for these thresholds value.
    
    Link: https://lkml.kernel.org/r/d78360e52158d786fcbf20bc62c96785742e76d3.1637239568.git.xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8bd0b9da03c9154e279b1a502636103887b9fbed
Author: Yihao Han <hanyihao@vivo.com>
Date:   Fri Jan 14 14:09:47 2022 -0800

    mm/damon/vaddr: remove swap_ranges() and replace it with swap()
    
    Remove 'swap_ranges()' and replace it with the macro 'swap()' defined in
    'include/linux/minmax.h' to simplify code and improve efficiency
    
    Link: https://lkml.kernel.org/r/20211111115355.2808-1-hanyihao@vivo.com
    Signed-off-by: Yihao Han <hanyihao@vivo.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit cdeed009f3bceee41f73f0137db785fd29a05cb8
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:44 2022 -0800

    mm/damon: remove some unneeded function definitions in damon.h
    
    In damon.h some func definitions about VA & PA can only be used in its
    own file, so there no need to define in the header file, and the header
    file will look cleaner.
    
    If other files later need these functions, the prototypes can be added
    to damon.h at that time.
    
    [sj@kernel.org: remove unnecessary function prototype position changes]
     Link: https://lkml.kernel.org/r/20211118114827.20052-1-sj@kernel.org
    
    Link: https://lkml.kernel.org/r/45fd5b3ef6cce8e28dbc1c92f9dc845ccfc949d7.1636989871.git.xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Signed-off-by: SeongJae Park <sj@kernel.org>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d720bbbd70e968f8a0257393b575c3a29b56f990
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:40 2022 -0800

    mm/damon/core: use abs() instead of diff_of()
    
    In kernel, we can use abs(a - b) to get the absolute value, So there is no
    need to redefine a new one.
    
    Link: https://lkml.kernel.org/r/b24e7b82d9efa90daf150d62dea171e19390ad0b.1636989871.git.xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c46b0bb6a735db0b6140e12e750b5acb1b032982
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:37 2022 -0800

    mm/damon: add 'age' of region tracepoint support
    
    In Damon, we can get age information by analyzing the nr_access change,
    But short time sampling is not effective, we have to obtain enough data
    for analysis through long time trace, this also means that we need to
    consume more cpu resources and storage space.
    
    Now the region add a new 'age' variable, we only need to get the change of
    age value through a little time trace, for example, age has been
    increasing to 141, but nr_access shows a value of 0 at the same time,
    Through this，we can conclude that the region has a very low nr_access
    value for a long time.
    
    Link: https://lkml.kernel.org/r/b9def1262af95e0dc1d0caea447886434db01161.1636989871.git.xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b627b774911660852ce7f3f3817955ddad2bd130
Author: Xin Hao <xhao@linux.alibaba.com>
Date:   Fri Jan 14 14:09:34 2022 -0800

    mm/damon: unified access_check function naming rules
    
    Patch series "mm/damon: Do some small changes", v4.
    
    This patch (of 4):
    
    In damon/paddr.c file, two functions names start with underscore,
            static void __damon_pa_prepare_access_check(struct damon_ctx *ctx,
                            struct damon_region *r)
            static void __damon_pa_prepare_access_check(struct damon_ctx *ctx,
                            struct damon_region *r)
    In damon/vaddr.c file, there are also two functions with the same function,
            static void damon_va_prepare_access_check(struct damon_ctx *ctx,
                            struct mm_struct *mm, struct damon_region *r)
            static void damon_va_check_access(struct damon_ctx *ctx,
                            struct mm_struct *mm, struct damon_region *r)
    
    It makes sense to keep consistent, and it is not easy to be confused with
    the function that call them.
    
    Link: https://lkml.kernel.org/r/cover.1636989871.git.xhao@linux.alibaba.com
    Link: https://lkml.kernel.org/r/529054aed932a42b9c09fc9977ad4574b9e7b0bd.1636989871.git.xhao@linux.alibaba.com
    Signed-off-by: Xin Hao <xhao@linux.alibaba.com>
    Reviewed-by: SeongJae Park <sj@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 87c01d57fa23de82fff593a7d070933d08755801
Author: Alistair Popple <apopple@nvidia.com>
Date:   Fri Jan 14 14:09:31 2022 -0800

    mm/hmm.c: allow VM_MIXEDMAP to work with hmm_range_fault
    
    hmm_range_fault() can be used instead of get_user_pages() for devices
    which allow faulting however unlike get_user_pages() it will return an
    error when used on a VM_MIXEDMAP range.
    
    To make hmm_range_fault() more closely match get_user_pages() remove
    this restriction.  This requires dealing with the !ARCH_HAS_PTE_SPECIAL
    case in hmm_vma_handle_pte().  Rather than replicating the logic of
    vm_normal_page() call it directly and do a check for the zero pfn
    similar to what get_user_pages() currently does.
    
    Also add a test to hmm selftest to verify functionality.
    
    Link: https://lkml.kernel.org/r/20211104012001.2555676-1-apopple@nvidia.com
    Fixes: da4c3c735ea4 ("mm/hmm/mirror: helper to snapshot CPU page table")
    Signed-off-by: Alistair Popple <apopple@nvidia.com>
    Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jerome Glisse <jglisse@redhat.com>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Cc: Ralph Campbell <rcampbell@nvidia.com>
    Cc: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit cab0a7c115546a4865fb7439558af9077a569574
Author: Ting Liu <liuting.0x7c00@bytedance.com>
Date:   Fri Jan 14 14:09:28 2022 -0800

    mm: make some vars and functions static or __init
    
    "page_idle_ops" as a global var, but its scope of use within this
    document.  So it should be static.
    
    "page_ext_ops" is a var used in the kernel initial phase.  And other
    functions are aslo used in the kernel initial phase.  So they should be
    __init or __initdata to reclaim memory.
    
    Link: https://lkml.kernel.org/r/20211217095023.67293-1-liuting.0x7c00@bytedance.com
    Signed-off-by: Ting Liu <liuting.0x7c00@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0b8f0d870020dbd7037bfacbb73a9b3213470f90
Author: Quanfa Fu <fuqf0919@gmail.com>
Date:   Fri Jan 14 14:09:25 2022 -0800

    mm: fix some comment errors
    
    Link: https://lkml.kernel.org/r/20211101040208.460810-1-fuqf0919@gmail.com
    Signed-off-by: Quanfa Fu <fuqf0919@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7f0d267243aa9dd32944bd7d3b34afff60545edb
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Fri Jan 14 14:09:22 2022 -0800

    zram: use ATTRIBUTE_GROUPS
    
    Embrace ATTRIBUTE_GROUPS to avoid boiler plate code.  This should not
    introduce any functional changes.
    
    Link: https://lkml.kernel.org/r/20211028203600.2157356-1-mcgrof@kernel.org
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Nitin Gupta <ngupta@vflare.org>
    Cc: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f44e1e697674335f837280d5e4485d1523206ea9
Author: Zhaoyu Liu <zackary.liu.pro@gmail.com>
Date:   Fri Jan 14 14:09:19 2022 -0800

    zpool: remove the list of pools_head
    
    The list of pools_head is no longer needed because the caller has been
    deleted in commit 479305fd7172 ("zpool: remove zpool_evict()").
    
    Link: https://lkml.kernel.org/r/20211215163727.GA17196@pc
    Signed-off-by: Zhaoyu Liu <zackary.liu.pro@gmail.com>
    Cc: Dan Streetman <ddstreet@ieee.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5ee2fa2f063649570c702164f47a558a3432dd9e
Author: Huang Ying <ying.huang@intel.com>
Date:   Fri Jan 14 14:09:16 2022 -0800

    mm/rmap: fix potential batched TLB flush race
    
    In theory, the following race is possible for batched TLB flushing.
    
      CPU0                               CPU1
      ----                               ----
      shrink_page_list()
                                         unmap
                                           zap_pte_range()
                                             flush_tlb_batched_pending()
                                               flush_tlb_mm()
        try_to_unmap()
          set_tlb_ubc_flush_pending()
            mm->tlb_flush_batched = true
                                               mm->tlb_flush_batched = false
    
    After the TLB is flushed on CPU1 via flush_tlb_mm() and before
    mm->tlb_flush_batched is set to false, some PTE is unmapped on CPU0 and
    the TLB flushing is pended.  Then the pended TLB flushing will be lost.
    Although both set_tlb_ubc_flush_pending() and
    flush_tlb_batched_pending() are called with PTL locked, different PTL
    instances may be used.
    
    Because the race window is really small, and the lost TLB flushing will
    cause problem only if a TLB entry is inserted before the unmapping in
    the race window, the race is only theoretical.  But the fix is simple
    and cheap too.
    
    Syzbot has reported this too as follows:
    
        ==================================================================
        BUG: KCSAN: data-race in flush_tlb_batched_pending / try_to_unmap_one
    
        write to 0xffff8881072cfbbc of 1 bytes by task 17406 on cpu 1:
         flush_tlb_batched_pending+0x5f/0x80 mm/rmap.c:691
         madvise_free_pte_range+0xee/0x7d0 mm/madvise.c:594
         walk_pmd_range mm/pagewalk.c:128 [inline]
         walk_pud_range mm/pagewalk.c:205 [inline]
         walk_p4d_range mm/pagewalk.c:240 [inline]
         walk_pgd_range mm/pagewalk.c:277 [inline]
         __walk_page_range+0x981/0x1160 mm/pagewalk.c:379
         walk_page_range+0x131/0x300 mm/pagewalk.c:475
         madvise_free_single_vma mm/madvise.c:734 [inline]
         madvise_dontneed_free mm/madvise.c:822 [inline]
         madvise_vma mm/madvise.c:996 [inline]
         do_madvise+0xe4a/0x1140 mm/madvise.c:1202
         __do_sys_madvise mm/madvise.c:1228 [inline]
         __se_sys_madvise mm/madvise.c:1226 [inline]
         __x64_sys_madvise+0x5d/0x70 mm/madvise.c:1226
         do_syscall_x64 arch/x86/entry/common.c:50 [inline]
         do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
         entry_SYSCALL_64_after_hwframe+0x44/0xae
    
        write to 0xffff8881072cfbbc of 1 bytes by task 71 on cpu 0:
         set_tlb_ubc_flush_pending mm/rmap.c:636 [inline]
         try_to_unmap_one+0x60e/0x1220 mm/rmap.c:1515
         rmap_walk_anon+0x2fb/0x470 mm/rmap.c:2301
         try_to_unmap+0xec/0x110
         shrink_page_list+0xe91/0x2620 mm/vmscan.c:1719
         shrink_inactive_list+0x3fb/0x730 mm/vmscan.c:2394
         shrink_list mm/vmscan.c:2621 [inline]
         shrink_lruvec+0x3c9/0x710 mm/vmscan.c:2940
         shrink_node_memcgs+0x23e/0x410 mm/vmscan.c:3129
         shrink_node+0x8f6/0x1190 mm/vmscan.c:3252
         kswapd_shrink_node mm/vmscan.c:4022 [inline]
         balance_pgdat+0x702/0xd30 mm/vmscan.c:4213
         kswapd+0x200/0x340 mm/vmscan.c:4473
         kthread+0x2c7/0x2e0 kernel/kthread.c:327
         ret_from_fork+0x1f/0x30
    
        value changed: 0x01 -> 0x00
    
        Reported by Kernel Concurrency Sanitizer on:
        CPU: 0 PID: 71 Comm: kswapd0 Not tainted 5.16.0-rc1-syzkaller #0
        Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
        ==================================================================
    
    [akpm@linux-foundation.org: tweak comments]
    
    Link: https://lkml.kernel.org/r/20211201021104.126469-1-ying.huang@intel.com
    Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
    Reported-by: syzbot+aa5bebed695edaccf0df@syzkaller.appspotmail.com
    Cc: Nadav Amit <namit@vmware.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Yu Zhao <yuzhao@google.com>
    Cc: Marco Elver <elver@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8c57c07741bf28e7d867f1200aa80120b8ca663e
Author: Qi Zheng <zhengqi.arch@bytedance.com>
Date:   Fri Jan 14 14:09:12 2022 -0800

    mm: memcg/percpu: account extra objcg space to memory cgroups
    
    Similar to slab memory allocator, for each accounted percpu object there
    is an extra space which is used to store obj_cgroup membership.  Charge
    it too.
    
    [akpm@linux-foundation.org: fix layout]
    
    Link: https://lkml.kernel.org/r/20211126040606.97836-1-zhengqi.arch@bytedance.com
    Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
    Acked-by: Dennis Zhou <dennis@kernel.org>
    Cc: Tejun Heo <tj@kernel.org>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bf181c582588f8f7406d52f2ee228539b465f173
Author: Naoya Horiguchi <naoya.horiguchi@nec.com>
Date:   Fri Jan 14 14:09:09 2022 -0800

    mm/hwpoison: fix unpoison_memory()
    
    After recent soft-offline rework, error pages can be taken off from
    buddy allocator, but the existing unpoison_memory() does not properly
    undo the operation.  Moreover, due to the recent change on
    __get_hwpoison_page(), get_page_unless_zero() is hardly called for
    hwpoisoned pages.  So __get_hwpoison_page() highly likely returns -EBUSY
    (meaning to fail to grab page refcount) and unpoison just clears
    PG_hwpoison without releasing a refcount.  That does not lead to a
    critical issue like kernel panic, but unpoisoned pages never get back to
    buddy (leaked permanently), which is not good.
    
    To (partially) fix this, we need to identify "taken off" pages from
    other types of hwpoisoned pages.  We can't use refcount or page flags
    for this purpose, so a pseudo flag is defined by hacking ->private
    field.  Someone might think that put_page() is enough to cancel
    taken-off pages, but the normal free path contains some operations not
    suitable for the current purpose, and can fire VM_BUG_ON().
    
    Note that unpoison_memory() is now supposed to be cancel hwpoison events
    injected only by madvise() or
    /sys/devices/system/memory/{hard,soft}_offline_page, not by MCE
    injection, so please don't try to use unpoison when testing with MCE
    injection.
    
    [lkp@intel.com: report build failure for ARCH=i386]
    
    Link: https://lkml.kernel.org/r/20211115084006.3728254-4-naoya.horiguchi@linux.dev
    Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Reviewed-by: Yang Shi <shy828301@gmail.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Ding Hui <dinghui@sangfor.com.cn>
    Cc: Tony Luck <tony.luck@intel.com>
    Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Peter Xu <peterx@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c9fdc4d5487a16bd1f003fc8b66e91f88efb50e6
Author: Naoya Horiguchi <naoya.horiguchi@nec.com>
Date:   Fri Jan 14 14:09:06 2022 -0800

    mm/hwpoison: remove MF_MSG_BUDDY_2ND and MF_MSG_POISONED_HUGE
    
    These action_page_types are no longer used, so remove them.
    
    Link: https://lkml.kernel.org/r/20211115084006.3728254-3-naoya.horiguchi@linux.dev
    Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Acked-by: Yang Shi <shy828301@gmail.com>
    Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Ding Hui <dinghui@sangfor.com.cn>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 91d005479e06392617bacc114509d611b705eaac
Author: Naoya Horiguchi <naoya.horiguchi@nec.com>
Date:   Fri Jan 14 14:09:02 2022 -0800

    mm/hwpoison: mf_mutex for soft offline and unpoison
    
    Patch series "mm/hwpoison: fix unpoison_memory()", v4.
    
    The main purpose of this series is to sync unpoison code to recent
    changes around how hwpoison code takes page refcount.  Unpoison should
    work or simply fail (without crash) if impossible.
    
    The recent works of keeping hwpoison pages in shmem pagecache introduce
    a new state of hwpoisoned pages, but unpoison for such pages is not
    supported yet with this series.
    
    It seems that soft-offline and unpoison can be used as general purpose
    page offline/online mechanism (not in the context of memory error).  I
    think that we need some additional works to realize it because currently
    soft-offline and unpoison are assumed not to happen so frequently (print
    out too many messages for aggressive usecases).  But anyway this could
    be another interesting next topic.
    
    v1: https://lore.kernel.org/linux-mm/20210614021212.223326-1-nao.horiguchi@gmail.com/
    v2: https://lore.kernel.org/linux-mm/20211025230503.2650970-1-naoya.horiguchi@linux.dev/
    v3: https://lore.kernel.org/linux-mm/20211105055058.3152564-1-naoya.horiguchi@linux.dev/
    
    This patch (of 3):
    
    Originally mf_mutex is introduced to serialize multiple MCE events, but
    it is not that useful to allow unpoison to run in parallel with
    memory_failure() and soft offline.  So apply mf_mutex to soft offline
    and unpoison.  The memory failure handler and soft offline handler get
    simpler with this.
    
    Link: https://lkml.kernel.org/r/20211115084006.3728254-1-naoya.horiguchi@linux.dev
    Link: https://lkml.kernel.org/r/20211115084006.3728254-2-naoya.horiguchi@linux.dev
    Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Reviewed-by: Yang Shi <shy828301@gmail.com>
    Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Ding Hui <dinghui@sangfor.com.cn>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e1c63e110f977205ab9dfb38989c54e6e7b52a7b
Author: Nanyong Sun <sunnanyong@huawei.com>
Date:   Fri Jan 14 14:08:59 2022 -0800

    mm: ksm: fix use-after-free kasan report in ksm_might_need_to_copy
    
    When under the stress of swapping in/out with KSM enabled, there is a
    low probability that kasan reports the BUG of use-after-free in
    ksm_might_need_to_copy() when do swap in.  The freed object is the
    anon_vma got from page_anon_vma(page).
    
    It is because a swapcache page associated with one anon_vma now needed
    for another anon_vma, but the page's original vma was unmapped and the
    anon_vma was freed.  In this case the if condition below always return
    false and then alloc a new page to copy.  Swapin process then use the
    new page and can continue to run well, so this is harmless actually.
    
          } else if (anon_vma->root == vma->anon_vma->root &&
                     page->index == linear_page_index(vma, address)) {
    
    This patch exchange the order of above two judgment statement to avoid
    the kasan warning.  Let cpu run "page->index == linear_page_index(vma,
    address)" firstly and return false basically to skip the read of
    anon_vma->root which may trigger the kasan use-after-free warning:
    
        ==================================================================
        BUG: KASAN: use-after-free in ksm_might_need_to_copy+0x12e/0x5b0
        Read of size 8 at addr ffff88be9977dbd0 by task khugepaged/694
    
         CPU: 8 PID: 694 Comm: khugepaged Kdump: loaded Tainted: G OE - 4.18.0.x86_64
         Hardware name: 1288H V5/BC11SPSC0, BIOS 7.93 01/14/2021
        Call Trace:
         dump_stack+0xf1/0x19b
         print_address_description+0x70/0x360
         kasan_report+0x1b2/0x330
         ksm_might_need_to_copy+0x12e/0x5b0
         do_swap_page+0x452/0xe70
         __collapse_huge_page_swapin+0x24b/0x720
         khugepaged_scan_pmd+0xcae/0x1ff0
         khugepaged+0x8ee/0xd70
         kthread+0x1a2/0x1d0
         ret_from_fork+0x1f/0x40
    
        Allocated by task 2306153:
         kasan_kmalloc+0xa0/0xd0
         kmem_cache_alloc+0xc0/0x1c0
         anon_vma_clone+0xf7/0x380
         anon_vma_fork+0xc0/0x390
         copy_process+0x447b/0x4810
         _do_fork+0x118/0x620
         do_syscall_64+0x112/0x360
         entry_SYSCALL_64_after_hwframe+0x65/0xca
    
        Freed by task 2306242:
         __kasan_slab_free+0x130/0x180
         kmem_cache_free+0x78/0x1d0
         unlink_anon_vmas+0x19c/0x4a0
         free_pgtables+0x137/0x1b0
         exit_mmap+0x133/0x320
         mmput+0x15e/0x390
         do_exit+0x8c5/0x1210
         do_group_exit+0xb5/0x1b0
         __x64_sys_exit_group+0x21/0x30
         do_syscall_64+0x112/0x360
         entry_SYSCALL_64_after_hwframe+0x65/0xca
    
        The buggy address belongs to the object at ffff88be9977dba0
         which belongs to the cache anon_vma_chain of size 64
        The buggy address is located 48 bytes inside of
         64-byte region [ffff88be9977dba0, ffff88be9977dbe0)
        The buggy address belongs to the page:
        page:ffffea00fa65df40 count:1 mapcount:0 mapping:ffff888107717800 index:0x0
        flags: 0x17ffffc0000100(slab)
        ==================================================================
    
    Link: https://lkml.kernel.org/r/20211202102940.1069634-1-sunnanyong@huawei.com
    Signed-off-by: Nanyong Sun <sunnanyong@huawei.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c0e582de6066e97c83a466f0e5983e3148123526
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Fri Jan 14 14:08:56 2022 -0800

    mm/thp: drop unused trace events hugepage_[invalidate|splitting]
    
    The trace events hugepage_[invalidate|splitting], were added via the
    commit 9e813308a5c1 ("powerpc/thp: Add tracepoints to track hugepage
    invalidate").  Afterwards their call sites i.e
    trace_hugepage_[invalidate|splitting] were just dropped off, leaving
    these trace points unused.
    
    Link: https://lkml.kernel.org/r/1641546351-15109-1-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f1e8db04b68cc56edc5baee5c7cb1f9b79c3da7e
Author: Colin Ian King <colin.king@intel.com>
Date:   Fri Jan 14 14:08:53 2022 -0800

    mm/migrate: remove redundant variables used in a for-loop
    
    The variable addr is being set and incremented in a for-loop but not
    actually being used.  It is redundant and so addr and also variable
    start can be removed.
    
    Link: https://lkml.kernel.org/r/20211221185729.609630-1-colin.i.king@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dcee9bf5bf2f59c173f3645ac2274595ac6c6aea
Author: Huang Ying <ying.huang@intel.com>
Date:   Fri Jan 14 14:08:49 2022 -0800

    mm/migrate: move node demotion code to near its user
    
    Now, node_demotion and next_demotion_node() are placed between
    __unmap_and_move() and unmap_and_move().  This hurts code readability.
    So move them near their users in the file.  There's no functionality
    change in this patch.
    
    Link: https://lkml.kernel.org/r/20211206031227.3323097-1-ying.huang@intel.com
    Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
    Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: Yang Shi <shy828301@gmail.com>
    Reviewed-by: Wei Xu <weixugc@google.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: Keith Busch <kbusch@kernel.org>
    Cc: Yang Shi <yang.shi@linux.alibaba.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7813a1b5257b8eb2cb915cd08e7ba857070fdfd3
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:08:46 2022 -0800

    mm: migrate: add more comments for selecting target node randomly
    
    As Yang Shi suggested [1], it will be helpful to explain why we should
    select target node randomly now if there are multiple target nodes.
    
    [1] https://lore.kernel.org/all/CAHbLzkqSqCL+g7dfzeOw8fPyeEC0BBv13Ny1UVGHDkadnQdR=g@mail.gmail.com/
    
    Link: https://lkml.kernel.org/r/c31d36bd097c6e9e69fc0f409c43b78e53e64fc2.1637766801.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: Yang Shi <shy828301@gmail.com>
    Cc: "Huang, Ying" <ying.huang@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Cc: zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>
    Cc: Xunlei Pang <xlpang@linux.alibaba.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ac16ec835314677dd7405dfb5a5e007c3ca424c7
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:08:43 2022 -0800

    mm: migrate: support multiple target nodes demotion
    
    We have some machines with multiple memory types like below, which have
    one fast (DRAM) memory node and two slow (persistent memory) memory
    nodes.  According to current node demotion policy, if node 0 fills up,
    its memory should be migrated to node 1, when node 1 fills up, its
    memory will be migrated to node 2: node 0 -> node 1 -> node 2 ->stop.
    
    But this is not efficient and suitbale memory migration route for our
    machine with multiple slow memory nodes.  Since the distance between
    node 0 to node 1 and node 0 to node 2 is equal, and memory migration
    between slow memory nodes will increase persistent memory bandwidth
    greatly, which will hurt the whole system's performance.
    
    Thus for this case, we can treat the slow memory node 1 and node 2 as a
    whole slow memory region, and we should migrate memory from node 0 to
    node 1 and node 2 if node 0 fills up.
    
    This patch changes the node_demotion data structure to support multiple
    target nodes, and establishes the migration path to support multiple
    target nodes with validating if the node distance is the best or not.
    
      available: 3 nodes (0-2)
      node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
      node 0 size: 62153 MB
      node 0 free: 55135 MB
      node 1 cpus:
      node 1 size: 127007 MB
      node 1 free: 126930 MB
      node 2 cpus:
      node 2 size: 126968 MB
      node 2 free: 126878 MB
      node distances:
      node   0   1   2
        0:  10  20  20
        1:  20  10  20
        2:  20  20  10
    
    Link: https://lkml.kernel.org/r/00728da107789bb4ed9e0d28b1d08fd8056af2ef.1636697263.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Yang Shi <shy828301@gmail.com>
    Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
    Cc: zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>
    Cc: Xunlei Pang <xlpang@linux.alibaba.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 84b328aa81216e08804d8875d63f26bda1298788
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:08:40 2022 -0800

    mm: compaction: fix the migration stats in trace_mm_compaction_migratepages()
    
    Now the migrate_pages() has changed to return the number of {normal
    page, THP, hugetlb} instead, thus we should not use the return value to
    calculate the number of pages migrated successfully.  Instead we can
    just use the 'nr_succeeded' which indicates the number of normal pages
    migrated successfully to calculate the non-migrated pages in
    trace_mm_compaction_migratepages().
    
    Link: https://lkml.kernel.org/r/b4225251c4bec068dcd90d275ab7de88a39e2bd7.1636275127.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Cc: Zi Yan <ziy@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5d39a7ebc8be70e30176aed6f98f799bfa7439d6
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:08:37 2022 -0800

    mm: migrate: correct the hugetlb migration stats
    
    Correct the migration stats for hugetlb with using compound_nr() instead
    of thp_nr_pages(), meanwhile change 'nr_failed_pages' to record the
    number of normal pages failed to migrate, including THP and hugetlb, and
    'nr_succeeded' will record the number of normal pages migrated
    successfully.
    
    [baolin.wang@linux.alibaba.com: fix docs, per Mike]
      Link: https://lkml.kernel.org/r/141bdfc6-f898-3cc3-f692-726c5f6cb74d@linux.alibaba.com
    
    Link: https://lkml.kernel.org/r/71a4b6c22f208728fe8c78ad26375436c4ff9704.1636275127.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Reviewed-by: Zi Yan <ziy@nvidia.com>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b5bade978e9b8f42521ccef711642bd21313cf44
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date:   Fri Jan 14 14:08:34 2022 -0800

    mm: migrate: fix the return value of migrate_pages()
    
    Patch series "Improve the migration stats".
    
    According to talk with Zi Yan [1], this patch set changes the return
    value of migrate_pages() to avoid returning a number which is larger
    than the number of pages the users tried to migrate by move_pages()
    syscall.  Also fix the hugetlb migration stats and migration stats in
    trace_mm_compaction_migratepages().
    
    [1] https://lore.kernel.org/linux-mm/7E44019D-2A5D-4BA7-B4D5-00D4712F1687@nvidia.com/
    
    This patch (of 3):
    
    As Zi Yan pointed out, the syscall move_pages() can return a
    non-migrated number larger than the number of pages the users tried to
    migrate, when a THP page is failed to migrate.  This is confusing for
    users.
    
    Since other migration scenarios do not care about the actual
    non-migrated number of pages except the memory compaction migration
    which will fix in following patch.  Thus we can change the return value
    to return the number of {normal page, THP, hugetlb} instead to avoid
    this issue, and the number of THP splits will be considered as the
    number of non-migrated THP, no matter how many subpages of the THP are
    migrated successfully.  Meanwhile we should still keep the migration
    counters using the number of normal pages.
    
    Link: https://lkml.kernel.org/r/cover.1636275127.git.baolin.wang@linux.alibaba.com
    Link: https://lkml.kernel.org/r/6486fabc3e8c66ff613e150af25e89b3147977a6.1636275127.git.baolin.wang@linux.alibaba.com
    Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
    Signed-off-by: Zi Yan <ziy@nvidia.com>
    Co-developed-by: Zi Yan <ziy@nvidia.com>
    Cc: Steven Rostedt (VMware) <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d6aba4c8e20d4d2bf65d589953f6d891c178f3a3
Author: Sean Christopherson <seanjc@google.com>
Date:   Fri Jan 14 14:08:30 2022 -0800

    hugetlbfs: fix off-by-one error in hugetlb_vmdelete_list()
    
    Pass "end - 1" instead of "end" when walking the interval tree in
    hugetlb_vmdelete_list() to fix an inclusive vs.  exclusive bug.  The two
    callers that pass a non-zero "end" treat it as exclusive, whereas the
    interval tree iterator expects an inclusive "last".  E.g.  punching a
    hole in a file that precisely matches the size of a single hugepage,
    with a vma starting right on the boundary, will result in
    unmap_hugepage_range() being called twice, with the second call having
    start==end.
    
    The off-by-one error doesn't cause functional problems as
    __unmap_hugepage_range() turns into a massive nop due to
    short-circuiting its for-loop on "address < end".  But, the mmu_notifier
    invocations to invalid_range_{start,end}() are passed a bogus zero-sized
    range, which may be unexpected behavior for secondary MMUs.
    
    The bug was exposed by commit ed922739c919 ("KVM: Use interval tree to
    do fast hva lookup in memslots"), currently queued in the KVM tree for
    5.17, which added a WARN to detect ranges with start==end.
    
    Link: https://lkml.kernel.org/r/20211228234257.1926057-1-seanjc@google.com
    Fixes: 1bfad99ab425 ("hugetlbfs: hugetlb_vmtruncate_list() needs to take a range to delete")
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Reported-by: syzbot+4e697fe80a31aa7efe21@syzkaller.appspotmail.com
    Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f530243a172d2ff03f88d0056f838928d6445c6d
Author: Jann Horn <jannh@google.com>
Date:   Fri Jan 14 14:08:27 2022 -0800

    mm, oom: OOM sysrq should always kill a process
    
    The OOM kill sysrq (alt+sysrq+F) should allow the user to kill the
    process with the highest OOM badness with a single execution.
    
    However, at the moment, the OOM kill can bail out if an OOM notifier
    (e.g.  the i915 one) says that it reclaimed a tiny amount of memory from
    somewhere.  That's probably not what the user wants, so skip the bailout
    if the OOM was triggered via sysrq.
    
    Link: https://lkml.kernel.org/r/20220106102605.635656-1-jannh@google.com
    Signed-off-by: Jann Horn <jannh@google.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Acked-by: David Rientjes <rientjes@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit dad5b0232949818ae581ebd089c7013e2fdbb093
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Fri Jan 14 14:08:24 2022 -0800

    mm/mempolicy: fix all kernel-doc warnings
    
    Fix kernel-doc warnings in mempolicy.c:
    
      mempolicy.c:139: warning: No description found for return value of 'numa_map_to_online_node'
      mempolicy.c:2165: warning: Excess function parameter 'node' description in 'alloc_pages_vma'
      mempolicy.c:2973: warning: No description found for return value of 'mpol_parse_str'
    
    Link: https://lkml.kernel.org/r/20211213233216.5477-1-rdunlap@infradead.org
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 21b084fdf2a49ca1634e8e360e9ab6f9ff0dee11
Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Date:   Fri Jan 14 14:08:21 2022 -0800

    mm/mempolicy: wire up syscall set_mempolicy_home_node
    
    Link: https://lkml.kernel.org/r/20211202123810.267175-4-aneesh.kumar@linux.ibm.com
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Ben Widawsky <ben.widawsky@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Feng Tang <feng.tang@intel.com>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Huang Ying <ying.huang@intel.com>
    Cc: <linux-api@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c6018b4b254971863bd0ad36bb5e7d0fa0f0ddb0
Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Date:   Fri Jan 14 14:08:17 2022 -0800

    mm/mempolicy: add set_mempolicy_home_node syscall
    
    This syscall can be used to set a home node for the MPOL_BIND and
    MPOL_PREFERRED_MANY memory policy.  Users should use this syscall after
    setting up a memory policy for the specified range as shown below.
    
      mbind(p, nr_pages * page_size, MPOL_BIND, new_nodes->maskp,
            new_nodes->size + 1, 0);
      sys_set_mempolicy_home_node((unsigned long)p, nr_pages * page_size,
                                    home_node, 0);
    
    The syscall allows specifying a home node/preferred node from which
    kernel will fulfill memory allocation requests first.
    
    For address range with MPOL_BIND memory policy, if nodemask specifies
    more than one node, page allocations will come from the node in the
    nodemask with sufficient free memory that is closest to the home
    node/preferred node.
    
    For MPOL_PREFERRED_MANY if the nodemask specifies more than one node,
    page allocation will come from the node in the nodemask with sufficient
    free memory that is closest to the home node/preferred node.  If there
    is not enough memory in all the nodes specified in the nodemask, the
    allocation will be attempted from the closest numa node to the home node
    in the system.
    
    This helps applications to hint at a memory allocation preference node
    and fallback to _only_ a set of nodes if the memory is not available on
    the preferred node.  Fallback allocation is attempted from the node
    which is nearest to the preferred node.
    
    This helps applications to have control on memory allocation numa nodes
    and avoids default fallback to slow memory NUMA nodes.  For example a
    system with NUMA nodes 1,2 and 3 with DRAM memory and 10, 11 and 12 of
    slow memory
    
     new_nodes = numa_bitmask_alloc(nr_nodes);
    
     numa_bitmask_setbit(new_nodes, 1);
     numa_bitmask_setbit(new_nodes, 2);
     numa_bitmask_setbit(new_nodes, 3);
    
     p = mmap(NULL, nr_pages * page_size, protflag, mapflag, -1, 0);
     mbind(p, nr_pages * page_size, MPOL_BIND, new_nodes->maskp,  new_nodes->size + 1, 0);
    
     sys_set_mempolicy_home_node(p, nr_pages * page_size, 2, 0);
    
    This will allocate from nodes closer to node 2 and will make sure the
    kernel will only allocate from nodes 1, 2, and 3.  Memory will not be
    allocated from slow memory nodes 10, 11, and 12.  This differs from
    default MPOL_BIND behavior in that with default MPOL_BIND the allocation
    will be attempted from node closer to the local node.  One of the
    reasons to specify a home node is to allow allocations from cpu less
    NUMA node and its nearby NUMA nodes.
    
    With MPOL_PREFERRED_MANY on the other hand will first try to allocate
    from the closest node to node 2 from the node list 1, 2 and 3.  If those
    nodes don't have enough memory, kernel will allocate from slow memory
    node 10, 11 and 12 which ever is closer to node 2.
    
    Link: https://lkml.kernel.org/r/20211202123810.267175-3-aneesh.kumar@linux.ibm.com
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Ben Widawsky <ben.widawsky@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Feng Tang <feng.tang@intel.com>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Huang Ying <ying.huang@intel.com>
    Cc: <linux-api@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c04551162167368022a61899843821bbf015b473
Author: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Date:   Fri Jan 14 14:08:14 2022 -0800

    mm/mempolicy: use policy_node helper with MPOL_PREFERRED_MANY
    
    Patch series "mm: add new syscall set_mempolicy_home_node", v6.
    
    This patch (of 3):
    
    A followup patch will enable setting a home node with
    MPOL_PREFERRED_MANY memory policy.  To facilitate that switch to using
    policy_node helper.  There is no functional change in this patch.
    
    Link: https://lkml.kernel.org/r/20211202123810.267175-1-aneesh.kumar@linux.ibm.com
    Link: https://lkml.kernel.org/r/20211202123810.267175-2-aneesh.kumar@linux.ibm.com
    Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Ben Widawsky <ben.widawsky@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Feng Tang <feng.tang@intel.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Huang Ying <ying.huang@intel.com>
    Cc: <linux-api@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 721fb891ad0b3956d5c168b2931e3e5e4fb7ca40
Author: Chen Wandun <chenwandun@huawei.com>
Date:   Fri Jan 14 14:08:10 2022 -0800

    mm/page_isolation: unset migratetype directly for non Buddy page
    
    In unset_migratetype_isolate(), we can bypass the call to
    move_freepages_block() for non-buddy pages.
    
    It will save a few cpu cycles for some situations such as cma and
    hugetlb when allocating continue pages, in these situation function
    alloc_contig_pages will be called.
    
    alloc_contig_pages
            __alloc_contig_migrate_range
            isolate_freepages_range ==> pages has been remove from buddy
            undo_isolate_page_range
                    unset_migratetype_isolate ==> can directly set migratetype
    
    [osalvador@suse.de: changelog tweak]
    
    Link: https://lkml.kernel.org/r/20211229033649.2760586-1-chenwandun@huawei.com
    Fixes: 3c605096d315 ("mm/page_alloc: restrict max order of merging on isolated pageblock")
    Signed-off-by: Chen Wandun <chenwandun@huawei.com>
    Reviewed-by: Oscar Salvador <osalvador@suse.de>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Wang Kefeng <wangkefeng.wang@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e4b424b7ec8791087375bb1f2480a3ba05d21e0b
Author: Gang Li <ligang.bdlg@bytedance.com>
Date:   Fri Jan 14 14:08:07 2022 -0800

    vmscan: make drop_slab_node static
    
    drop_slab_node is only used in drop_slab.  So remove it's declaration
    from header file and add keyword static for it's definition.
    
    Link: https://lkml.kernel.org/r/20211111062445.5236-1-ligang.bdlg@bytedance.com
    Signed-off-by: Gang Li <ligang.bdlg@bytedance.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 692b55815cf970eb4ce428f48f2c94d1800acc4b
Author: Mike Kravetz <mike.kravetz@oracle.com>
Date:   Fri Jan 14 14:08:04 2022 -0800

    userfaultfd/selftests: clean up hugetlb allocation code
    
    The message for commit f5c73297181c ("userfaultfd/selftests: fix hugetlb
    area allocations") says there is no need to create a hugetlb file in the
    non-shared testing case.  However, the commit did not actually change
    the code to prevent creation of the file.
    
    While it is technically true that there is no need to create and use a
    hugetlb file in the case of non-shared-testing, it is useful.  This is
    because 'hole punching' of a hugetlb file has the potentially incorrect
    side effect of also removing pages from private mappings.  The
    userfaultfd test relies on this side effect for removing pages from the
    destination buffer during rounds of stress testing.
    
    Remove the incomplete code that was added to deal with no hugetlb file.
    Just keep the code that prevents reserves from being created for the
    destination area.
    
    Link: https://lkml.kernel.org/r/20220104021729.111006-1-mike.kravetz@oracle.com
    Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
    Reviewed-by: Axel Rasmussen <axelrasmussen@google.com>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Mina Almasry <almasrymina@google.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit fab51505480058dcb63d973515c748fa6c437cab
Author: Peter Xu <peterx@redhat.com>
Date:   Fri Jan 14 14:08:01 2022 -0800

    selftests/uffd: allow EINTR/EAGAIN
    
    This allow test to continue with interruptions like gdb.
    
    Link: https://lkml.kernel.org/r/20211115135219.85881-1-peterx@redhat.com
    Signed-off-by: Peter Xu <peterx@redhat.com>
    Reviewed-by: Axel Rasmussen <axelrasmussen@google.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Nadav Amit <nadav.amit@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 209376ed2a8431ccb4c40fdcef11194fc1e749b0
Author: Waiman Long <longman@redhat.com>
Date:   Fri Jan 14 14:07:58 2022 -0800

    selftests/vm: make charge_reserved_hugetlb.sh work with existing cgroup setting
    
    The hugetlb cgroup reservation test charge_reserved_hugetlb.sh assume
    that no cgroup filesystems are mounted before running the test.  That is
    not true in many cases.  As a result, the test fails to run.  Fix that
    by querying the current cgroup mount setting and using the existing
    cgroup setup instead before attempting to freshly mount a cgroup
    filesystem.
    
    Similar change is also made for hugetlb_reparenting_test.sh as well,
    though it still has problem if cgroup v2 isn't used.
    
    The patched test scripts were run on a centos 8 based system to verify
    that they ran properly.
    
    Link: https://lkml.kernel.org/r/20220106201359.1646575-1-longman@redhat.com
    Fixes: 29750f71a9b4 ("hugetlb_cgroup: add hugetlb_cgroup reservation tests")
    Signed-off-by: Waiman Long <longman@redhat.com>
    Acked-by: Mina Almasry <almasrymina@google.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e9ea874a8ffb0f8ebed4f4981531a32c5b663d79
Author: Yang Yang <yang.yang29@zte.com.cn>
Date:   Fri Jan 14 14:07:55 2022 -0800

    mm/vmstat: add events for THP max_ptes_* exceeds
    
    There are interfaces to adjust max_ptes_none, max_ptes_swap,
    max_ptes_shared values, see
      /sys/kernel/mm/transparent_hugepage/khugepaged/.
    
    But system administrator may not know which value is the best.  So Add
    those events to support adjusting max_ptes_* to suitable values.
    
    For example, if default max_ptes_swap value causes too much failures,
    and system uses zram whose IO is fast, administrator could increase
    max_ptes_swap until THP_SCAN_EXCEED_SWAP_PTE not increase anymore.
    
    Link: https://lkml.kernel.org/r/20211225094036.574157-1-yang.yang29@zte.com.cn
    Signed-off-by: Yang Yang <yang.yang29@zte.com.cn>
    Cc: "Huang, Ying" <ying.huang@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Saravanan D <saravanand@fb.com>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f77a286de48c04f7dd248b41584645afc3613bb1
Author: Yosry Ahmed <yosryahmed@google.com>
Date:   Fri Jan 14 14:07:52 2022 -0800

    mm, hugepages: make memory size variable in hugepage-mremap selftest
    
    The hugetlb vma mremap() test currently maps 1GB of memory to trigger
    pmd sharing and make sure that 'unshare' path in mremap code works.  The
    test originally only mapped 10MB of memory (as specified by the header
    comment) but was later modified to 1GB to tackle this case.
    
    However, not all machines will have 1GB of memory to spare for this
    test.  Adding a mapping size arg will allow run_vmtest.sh to pass an
    adequate mapping size, while allowing users to run the test
    independently with arbitrary size mappings.
    
    Link: https://lkml.kernel.org/r/20211124203805.3700355-1-yosryahmed@google.com
    Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Mina Almasry <almasrymina@google.com>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f47761999052b1cc987dd3e3d3adf47997358fc0
Author: Mina Almasry <almasrymina@google.com>
Date:   Fri Jan 14 14:07:48 2022 -0800

    hugetlb: add hugetlb.*.numa_stat file
    
    For hugetlb backed jobs/VMs it's critical to understand the numa
    information for the memory backing these jobs to deliver optimal
    performance.
    
    Currently this technically can be queried from /proc/self/numa_maps, but
    there are significant issues with that.  Namely:
    
    1. Memory can be mapped or unmapped.
    
    2. numa_maps are per process and need to be aggregated across all
       processes in the cgroup.  For shared memory this is more involved as
       the userspace needs to make sure it doesn't double count shared
       mappings.
    
    3. I believe querying numa_maps needs to hold the mmap_lock which adds
       to the contention on this lock.
    
    For these reasons I propose simply adding hugetlb.*.numa_stat file,
       which shows the numa information of the cgroup similarly to
       memory.numa_stat.
    
    On cgroup-v2:
       cat /sys/fs/cgroup/unified/test/hugetlb.2MB.numa_stat
       total=2097152 N0=2097152 N1=0
    
    On cgroup-v1:
       cat /sys/fs/cgroup/hugetlb/test/hugetlb.2MB.numa_stat
       total=2097152 N0=2097152 N1=0
       hierarichal_total=2097152 N0=2097152 N1=0
    
    This patch was tested manually by allocating hugetlb memory and querying
    the hugetlb.*.numa_stat file of the cgroup and its parents.
    
    [colin.i.king@googlemail.com: fix spelling mistake "hierarichal" -> "hierarchical"]
      Link: https://lkml.kernel.org/r/20211125090635.23508-1-colin.i.king@gmail.com
    [keescook@chromium.org: fix copy/paste array assignment]
      Link: https://lkml.kernel.org/r/20211203065647.2819707-1-keescook@chromium.org
    
    Link: https://lkml.kernel.org/r/20211123001020.4083653-1-almasrymina@google.com
    Signed-off-by: Mina Almasry <almasrymina@google.com>
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Reviewed-by: Shakeel Butt <shakeelb@google.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Shuah Khan <shuah@kernel.org>
    Cc: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Jue Wang <juew@google.com>
    Cc: Yang Yao <ygyao@google.com>
    Cc: Joanna Li <joannali@google.com>
    Cc: Cannon Matthews <cannonmatthews@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c4dc63f0032c77464fbd4e7a6afc22fa6913c4a7
Author: Baoquan He <bhe@redhat.com>
Date:   Fri Jan 14 14:07:44 2022 -0800

    mm/page_alloc.c: do not warn allocation failure on zone DMA if no managed pages
    
    In kdump kernel of x86_64, page allocation failure is observed:
    
     kworker/u2:2: page allocation failure: order:0, mode:0xcc1(GFP_KERNEL|GFP_DMA), nodemask=(null),cpuset=/,mems_allowed=0
     CPU: 0 PID: 55 Comm: kworker/u2:2 Not tainted 5.16.0-rc4+ #5
     Hardware name: AMD Dinar/Dinar, BIOS RDN1505B 06/05/2013
     Workqueue: events_unbound async_run_entry_fn
     Call Trace:
      <TASK>
      dump_stack_lvl+0x48/0x5e
      warn_alloc.cold+0x72/0xd6
      __alloc_pages_slowpath.constprop.0+0xc69/0xcd0
      __alloc_pages+0x1df/0x210
      new_slab+0x389/0x4d0
      ___slab_alloc+0x58f/0x770
      __slab_alloc.constprop.0+0x4a/0x80
      kmem_cache_alloc_trace+0x24b/0x2c0
      sr_probe+0x1db/0x620
      ......
      device_add+0x405/0x920
      ......
      __scsi_add_device+0xe5/0x100
      ata_scsi_scan_host+0x97/0x1d0
      async_run_entry_fn+0x30/0x130
      process_one_work+0x1e8/0x3c0
      worker_thread+0x50/0x3b0
      ? rescuer_thread+0x350/0x350
      kthread+0x16b/0x190
      ? set_kthread_struct+0x40/0x40
      ret_from_fork+0x22/0x30
      </TASK>
     Mem-Info:
     ......
    
    The above failure happened when calling kmalloc() to allocate buffer with
    GFP_DMA.  It requests to allocate slab page from DMA zone while no managed
    pages at all in there.
    
     sr_probe()
     --> get_capabilities()
         --> buffer = kmalloc(512, GFP_KERNEL | GFP_DMA);
    
    Because in the current kernel, dma-kmalloc will be created as long as
    CONFIG_ZONE_DMA is enabled.  However, kdump kernel of x86_64 doesn't have
    managed pages on DMA zone since commit 6f599d84231f ("x86/kdump: Always
    reserve the low 1M when the crashkernel option is specified").  The
    failure can be always reproduced.
    
    For now, let's mute the warning of allocation failure if requesting pages
    from DMA zone while no managed pages.
    
    [akpm@linux-foundation.org: fix warning]
    
    Link: https://lkml.kernel.org/r/20211223094435.248523-4-bhe@redhat.com
    Fixes: 6f599d84231f ("x86/kdump: Always reserve the low 1M when the crashkernel option is specified")
    Signed-off-by: Baoquan He <bhe@redhat.com>
    Acked-by: John Donnelly  <john.p.donnelly@oracle.com>
    Reviewed-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: David Laight <David.Laight@ACULAB.COM>
    Cc: Marek Szyprowski <m.szyprowski@samsung.com>
    Cc: Robin Murphy <robin.murphy@arm.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a674e48c5443d12a8a43c3ac42367aa39505d506
Author: Baoquan He <bhe@redhat.com>
Date:   Fri Jan 14 14:07:41 2022 -0800

    dma/pool: create dma atomic pool only if dma zone has managed pages
    
    Currently three dma atomic pools are initialized as long as the relevant
    kernel codes are built in.  While in kdump kernel of x86_64, this is not
    right when trying to create atomic_pool_dma, because there's no managed
    pages in DMA zone.  In the case, DMA zone only has low 1M memory
    presented and locked down by memblock allocator.  So no pages are added
    into buddy of DMA zone.  Please check commit f1d4d47c5851 ("x86/setup:
    Always reserve the first 1M of RAM").
    
    Then in kdump kernel of x86_64, it always prints below failure message:
    
     DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
     swapper/0: page allocation failure: order:5, mode:0xcc1(GFP_KERNEL|GFP_DMA), nodemask=(null),cpuset=/,mems_allowed=0
     CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.13.0-0.rc5.20210611git929d931f2b40.42.fc35.x86_64 #1
     Hardware name: Dell Inc. PowerEdge R910/0P658H, BIOS 2.12.0 06/04/2018
     Call Trace:
      dump_stack+0x7f/0xa1
      warn_alloc.cold+0x72/0xd6
      __alloc_pages_slowpath.constprop.0+0xf29/0xf50
      __alloc_pages+0x24d/0x2c0
      alloc_page_interleave+0x13/0xb0
      atomic_pool_expand+0x118/0x210
      __dma_atomic_pool_init+0x45/0x93
      dma_atomic_pool_init+0xdb/0x176
      do_one_initcall+0x67/0x320
      kernel_init_freeable+0x290/0x2dc
      kernel_init+0xa/0x111
      ret_from_fork+0x22/0x30
     Mem-Info:
     ......
     DMA: failed to allocate 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocation
     DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
    
    Here, let's check if DMA zone has managed pages, then create
    atomic_pool_dma if yes.  Otherwise just skip it.
    
    Link: https://lkml.kernel.org/r/20211223094435.248523-3-bhe@redhat.com
    Fixes: 6f599d84231f ("x86/kdump: Always reserve the low 1M when the crashkernel option is specified")
    Signed-off-by: Baoquan He <bhe@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: John Donnelly  <john.p.donnelly@oracle.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Cc: Marek Szyprowski <m.szyprowski@samsung.com>
    Cc: Robin Murphy <robin.murphy@arm.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: David Laight <David.Laight@ACULAB.COM>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 62b3107073646e0946bd97ff926832bafb846d17
Author: Baoquan He <bhe@redhat.com>
Date:   Fri Jan 14 14:07:37 2022 -0800

    mm_zone: add function to check if managed dma zone exists
    
    Patch series "Handle warning of allocation failure on DMA zone w/o
    managed pages", v4.
    
    **Problem observed:
    On x86_64, when crash is triggered and entering into kdump kernel, page
    allocation failure can always be seen.
    
     ---------------------------------
     DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
     swapper/0: page allocation failure: order:5, mode:0xcc1(GFP_KERNEL|GFP_DMA), nodemask=(null),cpuset=/,mems_allowed=0
     CPU: 0 PID: 1 Comm: swapper/0
     Call Trace:
      dump_stack+0x7f/0xa1
      warn_alloc.cold+0x72/0xd6
      ......
      __alloc_pages+0x24d/0x2c0
      ......
      dma_atomic_pool_init+0xdb/0x176
      do_one_initcall+0x67/0x320
      ? rcu_read_lock_sched_held+0x3f/0x80
      kernel_init_freeable+0x290/0x2dc
      ? rest_init+0x24f/0x24f
      kernel_init+0xa/0x111
      ret_from_fork+0x22/0x30
     Mem-Info:
     ------------------------------------
    
    ***Root cause:
    In the current kernel, it assumes that DMA zone must have managed pages
    and try to request pages if CONFIG_ZONE_DMA is enabled. While this is not
    always true. E.g in kdump kernel of x86_64, only low 1M is presented and
    locked down at very early stage of boot, so that this low 1M won't be
    added into buddy allocator to become managed pages of DMA zone. This
    exception will always cause page allocation failure if page is requested
    from DMA zone.
    
    ***Investigation:
    This failure happens since below commit merged into linus's tree.
      1a6a9044b967 x86/setup: Remove CONFIG_X86_RESERVE_LOW and reservelow= options
      23721c8e92f7 x86/crash: Remove crash_reserve_low_1M()
      f1d4d47c5851 x86/setup: Always reserve the first 1M of RAM
      7c321eb2b843 x86/kdump: Remove the backup region handling
      6f599d84231f x86/kdump: Always reserve the low 1M when the crashkernel option is specified
    
    Before them, on x86_64, the low 640K area will be reused by kdump kernel.
    So in kdump kernel, the content of low 640K area is copied into a backup
    region for dumping before jumping into kdump. Then except of those firmware
    reserved region in [0, 640K], the left area will be added into buddy
    allocator to become available managed pages of DMA zone.
    
    However, after above commits applied, in kdump kernel of x86_64, the low
    1M is reserved by memblock, but not released to buddy allocator. So any
    later page allocation requested from DMA zone will fail.
    
    At the beginning, if crashkernel is reserved, the low 1M need be locked
    down because AMD SME encrypts memory making the old backup region
    mechanims impossible when switching into kdump kernel.
    
    Later, it was also observed that there are BIOSes corrupting memory
    under 1M. To solve this, in commit f1d4d47c5851, the entire region of
    low 1M is always reserved after the real mode trampoline is allocated.
    
    Besides, recently, Intel engineer mentioned their TDX (Trusted domain
    extensions) which is under development in kernel also needs to lock down
    the low 1M. So we can't simply revert above commits to fix the page allocation
    failure from DMA zone as someone suggested.
    
    ***Solution:
    Currently, only DMA atomic pool and dma-kmalloc will initialize and
    request page allocation with GFP_DMA during bootup.
    
    So only initializ DMA atomic pool when DMA zone has available managed
    pages, otherwise just skip the initialization.
    
    For dma-kmalloc(), for the time being, let's mute the warning of
    allocation failure if requesting pages from DMA zone while no manged
    pages.  Meanwhile, change code to use dma_alloc_xx/dma_map_xx API to
    replace kmalloc(GFP_DMA), or do not use GFP_DMA when calling kmalloc() if
    not necessary.  Christoph is posting patches to fix those under
    drivers/scsi/.  Finally, we can remove the need of dma-kmalloc() as people
    suggested.
    
    This patch (of 3):
    
    In some places of the current kernel, it assumes that dma zone must have
    managed pages if CONFIG_ZONE_DMA is enabled.  While this is not always
    true.  E.g in kdump kernel of x86_64, only low 1M is presented and locked
    down at very early stage of boot, so that there's no managed pages at all
    in DMA zone.  This exception will always cause page allocation failure if
    page is requested from DMA zone.
    
    Here add function has_managed_dma() and the relevant helper functions to
    check if there's DMA zone with managed pages.  It will be used in later
    patches.
    
    Link: https://lkml.kernel.org/r/20211223094435.248523-1-bhe@redhat.com
    Link: https://lkml.kernel.org/r/20211223094435.248523-2-bhe@redhat.com
    Fixes: 6f599d84231f ("x86/kdump: Always reserve the low 1M when the crashkernel option is specified")
    Signed-off-by: Baoquan He <bhe@redhat.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Acked-by: John Donnelly  <john.p.donnelly@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: David Laight <David.Laight@ACULAB.COM>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Marek Szyprowski <m.szyprowski@samsung.com>
    Cc: Robin Murphy <robin.murphy@arm.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit eaab8e753632b8e961701d02a5bb398c820f309c
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Fri Jan 14 14:07:33 2022 -0800

    mm/page_alloc.c: modify the comment section for alloc_contig_pages()
    
    Clarify that the alloc_contig_pages() allocated range will always be
    aligned to the requested nr_pages.
    
    Link: https://lkml.kernel.org/r/1639545478-12160-1-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: David Hildenbrand <david@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 04a536bfbd0f885338eecc2a4503dfca50ac94dd
Author: Miles Chen <miles.chen@mediatek.com>
Date:   Fri Jan 14 14:07:30 2022 -0800

    include/linux/gfp.h: further document GFP_DMA32
    
    kmalloc(..., GFP_DMA32) does not return DMA32 memory because the DMA32
    kmalloc cache array is not implemented.  (Reason: there is no such user
    in kernel).
    
    Put a short comment about this so people can understand this by reading
    the comment.
    
    [1] https://lists.linuxfoundation.org/pipermail/iommu/2018-December/031696.html
    
    Link: https://lkml.kernel.org/r/20211207093610.6406-1-miles.chen@mediatek.com
    Signed-off-by: Miles Chen <miles.chen@mediatek.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit be1a13eb51077b2ec5f7f4306f93dfece503a3f1
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:07:27 2022 -0800

    mm: drop node from alloc_pages_vma
    
    alloc_pages_vma is meant to allocate a page with a vma specific memory
    policy.  The initial node parameter is always a local node so it is
    pointless to waste a function argument for this.  Drop the parameter.
    
    Link: https://lkml.kernel.org/r/YaSnlv4QpryEpesG@dhcp22.suse.cz
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Ben Widawsky <ben.widawsky@intel.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Feng Tang <feng.tang@intel.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Randy Dunlap <rdunlap@infradead.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: "Huang, Ying" <ying.huang@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ca831f29f8f25c97182e726429b38c0802200c8f
Author: Xiongwei Song <sxwjean@gmail.com>
Date:   Fri Jan 14 14:07:24 2022 -0800

    mm: page_alloc: fix building error on -Werror=array-compare
    
    Arthur Marsh reported we would hit the error below when building kernel
    with gcc-12:
    
      CC      mm/page_alloc.o
      mm/page_alloc.c: In function `mem_init_print_info':
      mm/page_alloc.c:8173:27: error: comparison between two arrays [-Werror=array-compare]
       8173 |                 if (start <= pos && pos < end && size > adj) \
            |
    
    In C++20, the comparision between arrays should be warned.
    
    Link: https://lkml.kernel.org/r/20211125130928.32465-1-sxwjean@me.com
    Signed-off-by: Xiongwei Song <sxwjean@gmail.com>
    Reported-by: Arthur Marsh <arthur.marsh@internode.on.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1611f74a94ba2e0f2d25b75008ed8e76e122097a
Author: Changcheng Deng <deng.changcheng@zte.com.cn>
Date:   Fri Jan 14 14:07:21 2022 -0800

    mm: fix boolreturn.cocci warning
    
    Return statements in functions returning bool should use true/false
    instead of 1/0.
    
    Link: https://lkml.kernel.org/r/20211126073327.74815-1-deng.changcheng@zte.com.cn
    Signed-off-by: Changcheng Deng <deng.changcheng@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 39c65a94cd9661532be150e88f8b02f4a6844a35
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Jan 14 14:07:17 2022 -0800

    mm/pagealloc: sysctl: change watermark_scale_factor max limit to 30%
    
    For embedded systems with low total memory, having to run applications
    with relatively large memory requirements, 10% max limitation for
    watermark_scale_factor poses an issue of triggering direct reclaim every
    time such application is started.  This results in slow application
    startup times and bad end-user experience.
    
    By increasing watermark_scale_factor max limit we allow vendors more
    flexibility to choose the right level of kswapd aggressiveness for their
    device and workload requirements.
    
    Link: https://lkml.kernel.org/r/20211124193604.2758863-1-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: Lukas Middendorf <kernel@tuxforce.de>
    Cc: Antti Palosaari <crope@iki.fi>
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Iurii Zaikin <yzaikin@google.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Zhang Yi <yi.zhang@huawei.com>
    Cc: Fengfei Xi <xi.fengfei@h3c.com>
    Cc: Mike Rapoport <rppt@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4034247a0d6ab281ba3293798ce67af494d86129
Author: NeilBrown <neilb@suse.de>
Date:   Fri Jan 14 14:07:14 2022 -0800

    mm: introduce memalloc_retry_wait()
    
    Various places in the kernel - largely in filesystems - respond to a
    memory allocation failure by looping around and re-trying.  Some of
    these cannot conveniently use __GFP_NOFAIL, for reasons such as:
    
     - a GFP_ATOMIC allocation, which __GFP_NOFAIL doesn't work on
     - a need to check for the process being signalled between failures
     - the possibility that other recovery actions could be performed
     - the allocation is quite deep in support code, and passing down an
       extra flag to say if __GFP_NOFAIL is wanted would be clumsy.
    
    Many of these currently use congestion_wait() which (in almost all
    cases) simply waits the given timeout - congestion isn't tracked for
    most devices.
    
    It isn't clear what the best delay is for loops, but it is clear that
    the various filesystems shouldn't be responsible for choosing a timeout.
    
    This patch introduces memalloc_retry_wait() with takes on that
    responsibility.  Code that wants to retry a memory allocation can call
    this function passing the GFP flags that were used.  It will wait
    however is appropriate.
    
    For now, it only considers __GFP_NORETRY and whatever
    gfpflags_allow_blocking() tests.  If blocking is allowed without
    __GFP_NORETRY, then alloc_page either made some reclaim progress, or
    waited for a while, before failing.  So there is no need for much
    further waiting.  memalloc_retry_wait() will wait until the current
    jiffie ends.  If this condition is not met, then alloc_page() won't have
    waited much if at all.  In that case memalloc_retry_wait() waits about
    200ms.  This is the delay that most current loops uses.
    
    linux/sched/mm.h needs to be included in some files now,
    but linux/backing-dev.h does not.
    
    Link: https://lkml.kernel.org/r/163754371968.13692.1277530886009912421@noble.neil.brown.name
    Signed-off-by: NeilBrown <neilb@suse.de>
    Cc: Dave Chinner <david@fromorbit.com>
    Cc: Michal Hocko <mhocko@suse.com>
    Cc: "Theodore Ts'o" <tytso@mit.edu>
    Cc: Jaegeuk Kim <jaegeuk@kernel.org>
    Cc: Chao Yu <chao@kernel.org>
    Cc: Darrick J. Wong <djwong@kernel.org>
    Cc: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 704687deaae768a818d7da0584ee021793a97684
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:07:11 2022 -0800

    mm: make slab and vmalloc allocators __GFP_NOLOCKDEP aware
    
    sl?b and vmalloc allocators reduce the given gfp mask for their internal
    needs.  For that they use GFP_RECLAIM_MASK to preserve the reclaim
    behavior and constrains.
    
    __GFP_NOLOCKDEP is not a part of that mask because it doesn't really
    control the reclaim behavior strictly speaking.  On the other hand it
    tells the underlying page allocator to disable reclaim recursion
    detection so arguably it should be part of the mask.
    
    Having __GFP_NOLOCKDEP in the mask will not alter the behavior in any
    form so this change is safe pretty much by definition.  It also adds a
    support for this flag to SL?B and vmalloc allocators which will in turn
    allow its use to kvmalloc as well.  A lack of the support has been
    noticed recently in
    
      http://lkml.kernel.org/r/20211119225435.GZ449541@dread.disaster.area
    
    Link: https://lkml.kernel.org/r/YZ9XtLY4AEjVuiEI@dhcp22.suse.cz
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Reported-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Acked-by: Dave Chinner <dchinner@redhat.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Chinner <david@fromorbit.com>
    Cc: Ilya Dryomov <idryomov@gmail.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Neil Brown <neilb@suse.de>
    Cc: Uladzislau Rezki (Sony) <urezki@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a421ef303008b0ceee2cfc625c3246fa7654b0ca
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:07:07 2022 -0800

    mm: allow !GFP_KERNEL allocations for kvmalloc
    
    Support for GFP_NO{FS,IO} and __GFP_NOFAIL has been implemented by
    previous patches so we can allow the support for kvmalloc.  This will
    allow some external users to simplify or completely remove their
    helpers.
    
    GFP_NOWAIT semantic hasn't been supported so far but it hasn't been
    explicitly documented so let's add a note about that.
    
    ceph_kvmalloc is the first helper to be dropped and changed to kvmalloc.
    
    Link: https://lkml.kernel.org/r/20211122153233.9924-5-mhocko@kernel.org
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Chinner <david@fromorbit.com>
    Cc: Ilya Dryomov <idryomov@gmail.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Neil Brown <neilb@suse.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 30d3f01191d305c99e8b3f8b1b328fc852270c95
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:07:04 2022 -0800

    mm/vmalloc: be more explicit about supported gfp flags.
    
    Commit b7d90e7a5ea8 ("mm/vmalloc: be more explicit about supported gfp
    flags") has been merged prematurely without the rest of the series and
    without addressed review feedback from Neil.  Fix that up now.  Only
    wording is changed slightly.
    
    Link: https://lkml.kernel.org/r/20211122153233.9924-4-mhocko@kernel.org
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Chinner <david@fromorbit.com>
    Cc: Ilya Dryomov <idryomov@gmail.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Neil Brown <neilb@suse.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9376130c390a76fac2788a5d6e1a149017b4ab50
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:07:01 2022 -0800

    mm/vmalloc: add support for __GFP_NOFAIL
    
    Dave Chinner has mentioned that some of the xfs code would benefit from
    kvmalloc support for __GFP_NOFAIL because they have allocations that
    cannot fail and they do not fit into a single page.
    
    The large part of the vmalloc implementation already complies with the
    given gfp flags so there is no work for those to be done.  The area and
    page table allocations are an exception to that.  Implement a retry loop
    for those.
    
    Add a short sleep before retrying.  1 jiffy is a completely random
    timeout.  Ideally the retry would wait for an explicit event - e.g.  a
    change to the vmalloc space change if the failure was caused by the
    space fragmentation or depletion.  But there are multiple different
    reasons to retry and this could become much more complex.  Keep the
    retry simple for now and just sleep to prevent from hogging CPUs.
    
    Link: https://lkml.kernel.org/r/20211122153233.9924-3-mhocko@kernel.org
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Chinner <david@fromorbit.com>
    Cc: Ilya Dryomov <idryomov@gmail.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Neil Brown <neilb@suse.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Uladzislau Rezki (Sony) <urezki@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 451769ebb7e792c3404db53b3c2a422990de654e
Author: Michal Hocko <mhocko@suse.com>
Date:   Fri Jan 14 14:06:57 2022 -0800

    mm/vmalloc: alloc GFP_NO{FS,IO} for vmalloc
    
    Patch series "extend vmalloc support for constrained allocations", v2.
    
    Based on a recent discussion with Dave and Neil [1] I have tried to
    implement NOFS, NOIO, NOFAIL support for the vmalloc to make life of
    kvmalloc users easier.
    
    A requirement for NOFAIL support for kvmalloc was new to me but this
    seems to be really needed by the xfs code.
    
    NOFS/NOIO was a known and a long term problem which was hoped to be
    handled by the scope API.  Those scope should have been used at the
    reclaim recursion boundaries both to document them and also to remove
    the necessity of NOFS/NOIO constrains for all allocations within that
    scope.  Instead workarounds were developed to wrap a single allocation
    instead (like ceph_kvmalloc).
    
    First patch implements NOFS/NOIO support for vmalloc.  The second one
    adds NOFAIL support and the third one bundles all together into kvmalloc
    and drops ceph_kvmalloc which can use kvmalloc directly now.
    
    [1] http://lkml.kernel.org/r/163184741778.29351.16920832234899124642.stgit@noble.brown
    
    This patch (of 4):
    
    vmalloc historically hasn't supported GFP_NO{FS,IO} requests because
    page table allocations do not support externally provided gfp mask and
    performed GFP_KERNEL like allocations.
    
    Since few years we have scope (memalloc_no{fs,io}_{save,restore}) APIs
    to enforce NOFS and NOIO constrains implicitly to all allocators within
    the scope.  There was a hope that those scopes would be defined on a
    higher level when the reclaim recursion boundary starts/stops (e.g.
    when a lock required during the memory reclaim is required etc.).  It
    seems that not all NOFS/NOIO users have adopted this approach and
    instead they have taken a workaround approach to wrap a single
    [k]vmalloc allocation by a scope API.
    
    These workarounds do not serve the purpose of a better reclaim recursion
    documentation and reduction of explicit GFP_NO{FS,IO} usege so let's
    just provide them with the semantic they are asking for without a need
    for workarounds.
    
    Add support for GFP_NOFS and GFP_NOIO to vmalloc directly.  All internal
    allocations already comply with the given gfp_mask.  The only current
    exception is vmap_pages_range which maps kernel page tables.  Infer the
    proper scope API based on the given gfp mask.
    
    [sfr@canb.auug.org.au: mm/vmalloc.c needs linux/sched/mm.h]
     Link: https://lkml.kernel.org/r/20211217232641.0148710c@canb.auug.org.au
    
    Link: https://lkml.kernel.org/r/20211122153233.9924-1-mhocko@kernel.org
    Link: https://lkml.kernel.org/r/20211122153233.9924-2-mhocko@kernel.org
    Signed-off-by: Michal Hocko <mhocko@suse.com>
    Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Neil Brown <neilb@suse.de>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Ilya Dryomov <idryomov@gmail.com>
    Cc: Jeff Layton <jlayton@kernel.org>
    Cc: Dave Chinner <dchinner@redhat.com>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit cc6266f0322fa9f7f4543564759e881d989ad866
Author: Christian König <christian.koenig@amd.com>
Date:   Fri Jan 14 14:06:54 2022 -0800

    mm/dmapool.c: revert "make dma pool to use kmalloc_node"
    
    This reverts commit 2618c60b8b5836 ("dma: make dma pool to use
    kmalloc_node").
    
    While working myself into the dmapool code I've found this little odd
    kmalloc_node().
    
    What basically happens here is that we allocate the housekeeping
    structure on the numa node where the device is attached to.  Since the
    device is never doing DMA to or from that memory this doesn't seem to
    make sense at all.
    
    So while this doesn't seem to cause much harm it's probably cleaner to
    revert the change for consistency.
    
    Link: https://lkml.kernel.org/r/20211221110724.97664-1-christian.koenig@amd.com
    Signed-off-by: Christian König <christian.koenig@amd.com>
    Cc: Yinghai Lu <yinghai.lu@sun.com>
    Cc: Andi Kleen <ak@suse.de>
    Cc: Christoph Lameter <clameter@sgi.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Greg KH <greg@kroah.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d08d2b62510e2407cf939e693aefd179dc114913
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Jan 14 14:06:51 2022 -0800

    mm: remove the total_mapcount argument from page_trans_huge_mapcount()
    
    All callers pass NULL, so we can stop calculating the value we would
    store in it.
    
    Link: https://lkml.kernel.org/r/20211220205943.456187-3-willy@infradead.org
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>
    Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: David Hildenbrand <david@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 66c7f7a6ac6624fc7e226d43913e10f1f047f579
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Jan 14 14:06:48 2022 -0800

    mm: remove the total_mapcount argument from page_trans_huge_map_swapcount()
    
    Now that we don't report it to the caller of reuse_swap_page(), we don't
    need to request it from page_trans_huge_map_swapcount().
    
    Link: https://lkml.kernel.org/r/20211220205943.456187-2-willy@infradead.org
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>
    Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: David Hildenbrand <david@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 020e87650af9f43683546729f959fdc78422a4b7
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Jan 14 14:06:44 2022 -0800

    mm: remove last argument of reuse_swap_page()
    
    None of the callers care about the total_map_swapcount() any more.
    
    Link: https://lkml.kernel.org/r/20211220205943.456187-1-willy@infradead.org
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d283d422c6c4f0264fe8ecf5ae80036bf73f4594
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Fri Jan 14 14:06:41 2022 -0800

    x86: mm: add x86_64 support for page table check
    
    Add page table check hooks into routines that modify user page tables.
    
    Link: https://lkml.kernel.org/r/20211221154650.1047963-5-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Sami Tolvanen <samitolvanen@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit df4e817b710809425d899340dbfa8504a3ca4ba5
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Fri Jan 14 14:06:37 2022 -0800

    mm: page table check
    
    Check user page table entries at the time they are added and removed.
    
    Allows to synchronously catch memory corruption issues related to double
    mapping.
    
    When a pte for an anonymous page is added into page table, we verify
    that this pte does not already point to a file backed page, and vice
    versa if this is a file backed page that is being added we verify that
    this page does not have an anonymous mapping
    
    We also enforce that read-only sharing for anonymous pages is allowed
    (i.e.  cow after fork).  All other sharing must be for file pages.
    
    Page table check allows to protect and debug cases where "struct page"
    metadata became corrupted for some reason.  For example, when refcnt or
    mapcount become invalid.
    
    Link: https://lkml.kernel.org/r/20211221154650.1047963-4-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Sami Tolvanen <samitolvanen@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 08d5b29eac7dd5e6c79b66d390ecbb9219e05931
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Fri Jan 14 14:06:33 2022 -0800

    mm: ptep_clear() page table helper
    
    We have ptep_get_and_clear() and ptep_get_and_clear_full() helpers to
    clear PTE from user page tables, but there is no variant for simple
    clear of a present PTE from user page tables without using a low level
    pte_clear() which can be either native or para-virtualised.
    
    Add a new ptep_clear() that can be used in common code to clear PTEs
    from page table.  We will need this call later in order to add a hook
    for page table check.
    
    Link: https://lkml.kernel.org/r/20211221154650.1047963-3-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Sami Tolvanen <samitolvanen@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Will Deacon <will@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 1eba86c096e35e3cc83de1ad2c26f2d70470211b
Author: Pasha Tatashin <pasha.tatashin@soleen.com>
Date:   Fri Jan 14 14:06:29 2022 -0800

    mm: change page type prior to adding page table entry
    
    Patch series "page table check", v3.
    
    Ensure that some memory corruptions are prevented by checking at the
    time of insertion of entries into user page tables that there is no
    illegal sharing.
    
    We have recently found a problem [1] that existed in kernel since 4.14.
    The problem was caused by broken page ref count and led to memory
    leaking from one process into another.  The problem was accidentally
    detected by studying a dump of one process and noticing that one page
    contains memory that should not belong to this process.
    
    There are some other page->_refcount related problems that were recently
    fixed: [2], [3] which potentially could also lead to illegal sharing.
    
    In addition to hardening refcount [4] itself, this work is an attempt to
    prevent this class of memory corruption issues.
    
    It uses a simple state machine that is independent from regular MM logic
    to check for illegal sharing at time pages are inserted and removed from
    page tables.
    
    [1] https://lore.kernel.org/all/xr9335nxwc5y.fsf@gthelen2.svl.corp.google.com
    [2] https://lore.kernel.org/all/1582661774-30925-2-git-send-email-akaher@vmware.com
    [3] https://lore.kernel.org/all/20210622021423.154662-3-mike.kravetz@oracle.com
    [4] https://lore.kernel.org/all/20211221150140.988298-1-pasha.tatashin@soleen.com
    
    This patch (of 4):
    
    There are a few places where we first update the entry in the user page
    table, and later change the struct page to indicate that this is
    anonymous or file page.
    
    In most places, however, we first configure the page metadata and then
    insert entries into the page table.  Page table check, will use the
    information from struct page to verify the type of entry is inserted.
    
    Change the order in all places to first update struct page, and later to
    update page table.
    
    This means that we first do calls that may change the type of page (anon
    or file):
    
            page_move_anon_rmap
            page_add_anon_rmap
            do_page_add_anon_rmap
            page_add_new_anon_rmap
            page_add_file_rmap
            hugepage_add_anon_rmap
            hugepage_add_new_anon_rmap
    
    And after that do calls that add entries to the page table:
    
            set_huge_pte_at
            set_pte_at
    
    Link: https://lkml.kernel.org/r/20211221154650.1047963-1-pasha.tatashin@soleen.com
    Link: https://lkml.kernel.org/r/20211221154650.1047963-2-pasha.tatashin@soleen.com
    Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Paul Turner <pjt@google.com>
    Cc: Wei Xu <weixugc@google.com>
    Cc: Greg Thelen <gthelen@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Will Deacon <will@kernel.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: Sami Tolvanen <samitolvanen@google.com>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Frederic Weisbecker <frederic@kernel.org>
    Cc: "H. Peter Anvin" <hpa@zytor.com>
    Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
    Cc: Jiri Slaby <jirislaby@kernel.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Hugh Dickins <hughd@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4b8fec2867c85e081c1c9f800e0ec82eff71134f
Author: Shuah Khan <skhan@linuxfoundation.org>
Date:   Fri Jan 14 14:06:26 2022 -0800

    docs/vm: add vmalloced-kernel-stacks document
    
    Add a new document to explain Virtually Mapped Kernel Stack Support.
    This is a compilation of information from the code and original patch
    series that introduced the Virtually Mapped Kernel Stacks feature.
    
    This document summarizes the feature and provides details on allocation,
    free, and stack overflow handling.  Provides reference to available
    tests.
    
    Link: https://lkml.kernel.org/r/20211215002004.47981-1-skhan@linuxfoundation.org
    Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Andy Lutomirski <luto@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ba535c1caf3ee78aa7719e9e4b07a0dc1d153b9e
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Jan 14 14:06:22 2022 -0800

    mm/oom_kill: allow process_mrelease to run under mmap_lock protection
    
    With exit_mmap holding mmap_write_lock during free_pgtables call,
    process_mrelease does not need to elevate mm->mm_users in order to
    prevent exit_mmap from destrying pagetables while __oom_reap_task_mm is
    walking the VMA tree.  The change prevents process_mrelease from calling
    the last mmput, which can lead to waiting for IO completion in exit_aio.
    
    Link: https://lkml.kernel.org/r/20211209191325.3069345-3-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Christian Brauner <christian@brauner.io>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Christoph Hellwig <hch@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Florian Weimer <fweimer@redhat.com>
    Cc: Jan Engelhardt <jengelh@inai.de>
    Cc: Jann Horn <jannh@google.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: Rik van Riel <riel@surriel.com>
    Cc: Roman Gushchin <guro@fb.com>
    Cc: Shakeel Butt <shakeelb@google.com>
    Cc: Tim Murray <timmurray@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit cc6dcfee72509868271d42919a3c1081b6b0dc7e
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Jan 14 14:06:18 2022 -0800

    mm: document locking restrictions for vm_operations_struct::close
    
    Add comments for vm_operations_struct::close documenting locking
    requirements for this callback and its callers.
    
    Link: https://lkml.kernel.org/r/20211209191325.3069345-2-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Christian Brauner <christian@brauner.io>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Christoph Hellwig <hch@infradead.org>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Florian Weimer <fweimer@redhat.com>
    Cc: Jan Engelhardt <jengelh@inai.de>
    Cc: Jann Horn <jannh@google.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: Rik van Riel <riel@surriel.com>
    Cc: Roman Gushchin <guro@fb.com>
    Cc: Shakeel Butt <shakeelb@google.com>
    Cc: Tim Murray <timmurray@google.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 64591e8605d6e2fba2ff38e3227645f039b8893f
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Jan 14 14:06:14 2022 -0800

    mm: protect free_pgtables with mmap_lock write lock in exit_mmap
    
    oom-reaper and process_mrelease system call should protect against races
    with exit_mmap which can destroy page tables while they walk the VMA
    tree.  oom-reaper protects from that race by setting MMF_OOM_VICTIM and
    by relying on exit_mmap to set MMF_OOM_SKIP before taking and releasing
    mmap_write_lock.  process_mrelease has to elevate mm->mm_users to
    prevent such race.
    
    Both oom-reaper and process_mrelease hold mmap_read_lock when walking
    the VMA tree.  The locking rules and mechanisms could be simpler if
    exit_mmap takes mmap_write_lock while executing destructive operations
    such as free_pgtables.
    
    Change exit_mmap to hold the mmap_write_lock when calling unlock_range,
    free_pgtables and remove_vma.  Note also that because oom-reaper checks
    VM_LOCKED flag, unlock_range() should not be allowed to race with it.
    
    Before this patch, remove_vma used to be called with no locks held,
    however with fput being executed asynchronously and vm_ops->close not
    being allowed to hold mmap_lock (it is called from __split_vma with
    mmap_sem held for write), changing that should be fine.
    
    In most cases this lock should be uncontended.  Previously, Kirill
    reported ~4% regression caused by a similar change [1].  We reran the
    same test and although the individual results are quite noisy, the
    percentiles show lower regression with 1.6% being the worst case [2].
    The change allows oom-reaper and process_mrelease to execute safely
    under mmap_read_lock without worries that exit_mmap might destroy page
    tables from under them.
    
    [1] https://lore.kernel.org/all/20170725141723.ivukwhddk2voyhuc@node.shutemov.name/
    [2] https://lore.kernel.org/all/CAJuCfpGC9-c9P40x7oy=jy5SphMcd0o0G_6U1-+JAziGKG6dGA@mail.gmail.com/
    
    Link: https://lkml.kernel.org/r/20211209191325.3069345-1-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Roman Gushchin <guro@fb.com>
    Cc: Rik van Riel <riel@surriel.com>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Kirill A. Shutemov <kirill@shutemov.name>
    Cc: Andrea Arcangeli <aarcange@redhat.com>
    Cc: Christian Brauner <christian@brauner.io>
    Cc: Christoph Hellwig <hch@infradead.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Jann Horn <jannh@google.com>
    Cc: Shakeel Butt <shakeelb@google.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: Florian Weimer <fweimer@redhat.com>
    Cc: Jan Engelhardt <jengelh@inai.de>
    Cc: Tim Murray <timmurray@google.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 36090def7bad06a6346f86a7cfdbfda2d138cb64
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Jan 14 14:06:10 2022 -0800

    mm: move tlb_flush_pending inline helpers to mm_inline.h
    
    linux/mm_types.h should only define structure definitions, to make it
    cheap to include elsewhere.  The atomic_t helper function definitions
    are particularly large, so it's better to move the helpers using those
    into the existing linux/mm_inline.h and only include that where needed.
    
    As a follow-up, we may want to go through all the indirect includes in
    mm_types.h and reduce them as much as possible.
    
    Link: https://lkml.kernel.org/r/20211207125710.2503446-2-arnd@kernel.org
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Colin Cross <ccross@google.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Yu Zhao <yuzhao@google.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 17fca131cee21724ee953a17c185c14e9533af5b
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Jan 14 14:06:07 2022 -0800

    mm: move anon_vma declarations to linux/mm_inline.h
    
    The patch to add anonymous vma names causes a build failure in some
    configurations:
    
      include/linux/mm_types.h: In function 'is_same_vma_anon_name':
      include/linux/mm_types.h:924:37: error: implicit declaration of function 'strcmp' [-Werror=implicit-function-declaration]
        924 |         return name && vma_name && !strcmp(name, vma_name);
            |                                     ^~~~~~
      include/linux/mm_types.h:22:1: note: 'strcmp' is defined in header '<string.h>'; did you forget to '#include <string.h>'?
    
    This should not really be part of linux/mm_types.h in the first place,
    as that header is meant to only contain structure defintions and need a
    minimum set of indirect includes itself.
    
    While the header clearly includes more than it should at this point,
    let's not make it worse by including string.h as well, which would pull
    in the expensive (compile-speed wise) fortify-string logic.
    
    Move the new functions into a separate header that only needs to be
    included in a couple of locations.
    
    Link: https://lkml.kernel.org/r/20211207125710.2503446-1-arnd@kernel.org
    Fixes: "mm: add a field to store names for private anonymous memory"
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Colin Cross <ccross@google.com>
    Cc: Eric Biederman <ebiederm@xmission.com>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Suren Baghdasaryan <surenb@google.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Cc: Yu Zhao <yuzhao@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 78db3412833dc9c479cd17412035f216cfd01a29
Author: Suren Baghdasaryan <surenb@google.com>
Date:   Fri Jan 14 14:06:03 2022 -0800

    mm: add anonymous vma name refcounting
    
    While forking a process with high number (64K) of named anonymous vmas
    the overhead caused by strdup() is noticeable.  Experiments with ARM64
    Android device show up to 40% performance regression when forking a
    process with 64k unpopulated anonymous vmas using the max name lengths
    vs the same process with the same number of anonymous vmas having no
    name.
    
    Introduce anon_vma_name refcounted structure to avoid the overhead of
    copying vma names during fork() and when splitting named anonymous vmas.
    
    When a vma is duplicated, instead of copying the name we increment the
    refcount of this structure.  Multiple vmas can point to the same
    anon_vma_name as long as they increment the refcount.  The name member
    of anon_vma_name structure is assigned at structure allocation time and
    is never changed.  If vma name changes then the refcount of the original
    structure is dropped, a new anon_vma_name structure is allocated to hold
    the new name and the vma pointer is updated to point to the new
    structure.
    
    With this approach the fork() performance regressions is reduced 3-4x
    times and with usecases using more reasonable number of VMAs (a few
    thousand) the regressions is not measurable.
    
    Link: https://lkml.kernel.org/r/20211019215511.3771969-3-surenb@google.com
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Colin Cross <ccross@google.com>
    Cc: Cyrill Gorcunov <gorcunov@openvz.org>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Jan Glauber <jan.glauber@gmail.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: John Stultz <john.stultz@linaro.org>
    Cc: Mel Gorman <mgorman@suse.de>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Rob Landley <rob@landley.net>
    Cc: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>
    Cc: Shaohua Li <shli@fusionio.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9a10064f5625d5572c3626c1516e0bebc6c9fe9b
Author: Colin Cross <ccross@google.com>
Date:   Fri Jan 14 14:05:59 2022 -0800

    mm: add a field to store names for private anonymous memory
    
    In many userspace applications, and especially in VM based applications
    like Android uses heavily, there are multiple different allocators in
    use.  At a minimum there is libc malloc and the stack, and in many cases
    there are libc malloc, the stack, direct syscalls to mmap anonymous
    memory, and multiple VM heaps (one for small objects, one for big
    objects, etc.).  Each of these layers usually has its own tools to
    inspect its usage; malloc by compiling a debug version, the VM through
    heap inspection tools, and for direct syscalls there is usually no way
    to track them.
    
    On Android we heavily use a set of tools that use an extended version of
    the logic covered in Documentation/vm/pagemap.txt to walk all pages
    mapped in userspace and slice their usage by process, shared (COW) vs.
    unique mappings, backing, etc.  This can account for real physical
    memory usage even in cases like fork without exec (which Android uses
    heavily to share as many private COW pages as possible between
    processes), Kernel SamePage Merging, and clean zero pages.  It produces
    a measurement of the pages that only exist in that process (USS, for
    unique), and a measurement of the physical memory usage of that process
    with the cost of shared pages being evenly split between processes that
    share them (PSS).
    
    If all anonymous memory is indistinguishable then figuring out the real
    physical memory usage (PSS) of each heap requires either a pagemap
    walking tool that can understand the heap debugging of every layer, or
    for every layer's heap debugging tools to implement the pagemap walking
    logic, in which case it is hard to get a consistent view of memory
    across the whole system.
    
    Tracking the information in userspace leads to all sorts of problems.
    It either needs to be stored inside the process, which means every
    process has to have an API to export its current heap information upon
    request, or it has to be stored externally in a filesystem that somebody
    needs to clean up on crashes.  It needs to be readable while the process
    is still running, so it has to have some sort of synchronization with
    every layer of userspace.  Efficiently tracking the ranges requires
    reimplementing something like the kernel vma trees, and linking to it
    from every layer of userspace.  It requires more memory, more syscalls,
    more runtime cost, and more complexity to separately track regions that
    the kernel is already tracking.
    
    This patch adds a field to /proc/pid/maps and /proc/pid/smaps to show a
    userspace-provided name for anonymous vmas.  The names of named
    anonymous vmas are shown in /proc/pid/maps and /proc/pid/smaps as
    [anon:<name>].
    
    Userspace can set the name for a region of memory by calling
    
       prctl(PR_SET_VMA, PR_SET_VMA_ANON_NAME, start, len, (unsigned long)name)
    
    Setting the name to NULL clears it.  The name length limit is 80 bytes
    including NUL-terminator and is checked to contain only printable ascii
    characters (including space), except '[',']','\','$' and '`'.
    
    Ascii strings are being used to have a descriptive identifiers for vmas,
    which can be understood by the users reading /proc/pid/maps or
    /proc/pid/smaps.  Names can be standardized for a given system and they
    can include some variable parts such as the name of the allocator or a
    library, tid of the thread using it, etc.
    
    The name is stored in a pointer in the shared union in vm_area_struct
    that points to a null terminated string.  Anonymous vmas with the same
    name (equivalent strings) and are otherwise mergeable will be merged.
    The name pointers are not shared between vmas even if they contain the
    same name.  The name pointer is stored in a union with fields that are
    only used on file-backed mappings, so it does not increase memory usage.
    
    CONFIG_ANON_VMA_NAME kernel configuration is introduced to enable this
    feature.  It keeps the feature disabled by default to prevent any
    additional memory overhead and to avoid confusing procfs parsers on
    systems which are not ready to support named anonymous vmas.
    
    The patch is based on the original patch developed by Colin Cross, more
    specifically on its latest version [1] posted upstream by Sumit Semwal.
    It used a userspace pointer to store vma names.  In that design, name
    pointers could be shared between vmas.  However during the last
    upstreaming attempt, Kees Cook raised concerns [2] about this approach
    and suggested to copy the name into kernel memory space, perform
    validity checks [3] and store as a string referenced from
    vm_area_struct.
    
    One big concern is about fork() performance which would need to strdup
    anonymous vma names.  Dave Hansen suggested experimenting with
    worst-case scenario of forking a process with 64k vmas having longest
    possible names [4].  I ran this experiment on an ARM64 Android device
    and recorded a worst-case regression of almost 40% when forking such a
    process.
    
    This regression is addressed in the followup patch which replaces the
    pointer to a name with a refcounted structure that allows sharing the
    name pointer between vmas of the same name.  Instead of duplicating the
    string during fork() or when splitting a vma it increments the refcount.
    
    [1] https://lore.kernel.org/linux-mm/20200901161459.11772-4-sumit.semwal@linaro.org/
    [2] https://lore.kernel.org/linux-mm/202009031031.D32EF57ED@keescook/
    [3] https://lore.kernel.org/linux-mm/202009031022.3834F692@keescook/
    [4] https://lore.kernel.org/linux-mm/5d0358ab-8c47-2f5f-8e43-23b89d6a8e95@intel.com/
    
    Changes for prctl(2) manual page (in the options section):
    
    PR_SET_VMA
            Sets an attribute specified in arg2 for virtual memory areas
            starting from the address specified in arg3 and spanning the
            size specified  in arg4. arg5 specifies the value of the attribute
            to be set. Note that assigning an attribute to a virtual memory
            area might prevent it from being merged with adjacent virtual
            memory areas due to the difference in that attribute's value.
    
            Currently, arg2 must be one of:
    
            PR_SET_VMA_ANON_NAME
                    Set a name for anonymous virtual memory areas. arg5 should
                    be a pointer to a null-terminated string containing the
                    name. The name length including null byte cannot exceed
                    80 bytes. If arg5 is NULL, the name of the appropriate
                    anonymous virtual memory areas will be reset. The name
                    can contain only printable ascii characters (including
                    space), except '[',']','\','$' and '`'.
    
                    This feature is available only if the kernel is built with
                    the CONFIG_ANON_VMA_NAME option enabled.
    
    [surenb@google.com: docs: proc.rst: /proc/PID/maps: fix malformed table]
      Link: https://lkml.kernel.org/r/20211123185928.2513763-1-surenb@google.com
    [surenb: rebased over v5.15-rc6, replaced userpointer with a kernel copy,
     added input sanitization and CONFIG_ANON_VMA_NAME config. The bulk of the
     work here was done by Colin Cross, therefore, with his permission, keeping
     him as the author]
    
    Link: https://lkml.kernel.org/r/20211019215511.3771969-2-surenb@google.com
    Signed-off-by: Colin Cross <ccross@google.com>
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Reviewed-by: Kees Cook <keescook@chromium.org>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Cyrill Gorcunov <gorcunov@openvz.org>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Jan Glauber <jan.glauber@gmail.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: John Stultz <john.stultz@linaro.org>
    Cc: Mel Gorman <mgorman@suse.de>
    Cc: Minchan Kim <minchan@kernel.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Rob Landley <rob@landley.net>
    Cc: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>
    Cc: Shaohua Li <shli@fusionio.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ac1e9acc5acf0b41d54de6a4c45471644f8b97ff
Author: Colin Cross <ccross@google.com>
Date:   Fri Jan 14 14:05:55 2022 -0800

    mm: rearrange madvise code to allow for reuse
    
    Patch series "mm: rearrange madvise code to allow for reuse", v11.
    
    Avoid performance regression of the new anon vma name field refcounting it.
    
    I checked the image sizes with allnoconfig builds:
    
      unpatched Linus' ToT
         text    data     bss     dec     hex filename
      1324759      32   73928 1398719 1557bf vmlinux
    
      After the first patch is applied (madvise refactoring)
         text    data     bss     dec     hex filename
      1322346      32   73928 1396306 154e52 vmlinux
      >>> 2413 bytes decrease vs ToT <<<
    
      After all patches applied with CONFIG_ANON_VMA_NAME=n
         text    data     bss     dec     hex filename
      1322337      32   73928 1396297 154e49 vmlinux
      >>> 2422 bytes decrease vs ToT <<<
    
      After all patches applied with CONFIG_ANON_VMA_NAME=y
         text    data     bss     dec     hex filename
      1325228      32   73928 1399188 155994 vmlinux
      >>> 469 bytes increase vs ToT <<<
    
    This patch (of 3):
    
    Refactor the madvise syscall to allow for parts of it to be reused by a
    prctl syscall that affects vmas.
    
    Move the code that walks vmas in a virtual address range into a function
    that takes a function pointer as a parameter.  The only caller for now
    is sys_madvise, which uses it to call madvise_vma_behavior on each vma,
    but the next patch will add an additional caller.
    
    Move handling all vma behaviors inside madvise_behavior, and rename it
    to madvise_vma_behavior.
    
    Move the code that updates the flags on a vma, including splitting or
    merging the vma as necessary, into a new function called
    madvise_update_vma.  The next patch will add support for updating a new
    anon_name field as well.
    
    Link: https://lkml.kernel.org/r/20211019215511.3771969-1-surenb@google.com
    Signed-off-by: Colin Cross <ccross@google.com>
    Signed-off-by: Suren Baghdasaryan <surenb@google.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Dave Hansen <dave.hansen@intel.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Oleg Nesterov <oleg@redhat.com>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Jan Glauber <jan.glauber@gmail.com>
    Cc: John Stultz <john.stultz@linaro.org>
    Cc: Rob Landley <rob@landley.net>
    Cc: Cyrill Gorcunov <gorcunov@openvz.org>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Mel Gorman <mgorman@suse.de>
    Cc: Shaohua Li <shli@fusionio.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Minchan Kim <minchan@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 36ef159f4408b08eae7f2af6d62bedd3f4343758
Author: Qi Zheng <zhengqi.arch@bytedance.com>
Date:   Fri Jan 14 14:05:51 2022 -0800

    mm: remove redundant check about FAULT_FLAG_ALLOW_RETRY bit
    
    Since commit 4064b9827063 ("mm: allow VM_FAULT_RETRY for multiple
    times") allowed VM_FAULT_RETRY for multiple times, the
    FAULT_FLAG_ALLOW_RETRY bit of fault_flag will not be changed in the page
    fault path, so the following check is no longer needed:
    
            flags & FAULT_FLAG_ALLOW_RETRY
    
    So just remove it.
    
    [akpm@linux-foundation.org: coding style fixes]
    
    Link: https://lkml.kernel.org/r/20211110123358.36511-1-zhengqi.arch@bytedance.com
    Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: David Hildenbrand <david@redhat.com>
    Cc: Kirill Shutemov <kirill@shutemov.name>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Chengming Zhou <zhouchengming@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 2c769ed7137a75a8297936fb54e6ff1f56d3d0f1
Author: chiminghao <chi.minghao@zte.com.cn>
Date:   Fri Jan 14 14:05:48 2022 -0800

    tools/testing/selftests/vm/userfaultfd.c: use swap() to make code cleaner
    
    Fix the following coccicheck REVIEW:
    
     tools/testing/selftests/vm/userfaultfd.c:1531:21-22:use swap() to make code cleaner
    
    Link: https://lkml.kernel.org/r/20211124031632.35317-1-chi.minghao@zte.com.cn
    Signed-off-by: chiminghao <chi.minghao@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4e5aa1f4c2b489bc6f3ab5ca54747b18a847289d
Author: Shakeel Butt <shakeelb@google.com>
Date:   Fri Jan 14 14:05:45 2022 -0800

    memcg: add per-memcg vmalloc stat
    
    The kvmalloc* allocation functions can fallback to vmalloc allocations
    and more often on long running machines.  In addition the kernel does
    have __GFP_ACCOUNT kvmalloc* calls.  So, often on long running machines,
    the memory.stat does not tell the complete picture which type of memory
    is charged to the memcg.  So add a per-memcg vmalloc stat.
    
    [shakeelb@google.com: page_memcg() within rcu lock, per Muchun]
      Link: https://lkml.kernel.org/r/20211222052457.1960701-1-shakeelb@google.com
    [akpm@linux-foundation.org: remove cast, per Muchun]
    [shakeelb@google.com: remove area->page[0] checks and move to page by page accounting per Michal]
      Link: https://lkml.kernel.org/r/20220104222341.3972772-1-shakeelb@google.com
    
    Link: https://lkml.kernel.org/r/20211221215336.1922823-1-shakeelb@google.com
    Signed-off-by: Shakeel Butt <shakeelb@google.com>
    Acked-by: Roman Gushchin <guro@fb.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 06b2c3b08ce134c9555d91a1cf15cd03646cc287
Author: Wang Weiyang <wangweiyang2@huawei.com>
Date:   Fri Jan 14 14:05:42 2022 -0800

    mm/memcg: use struct_size() helper in kzalloc()
    
    Make use of the struct_size() helper instead of an open-coded version,
    in order to avoid any potential type mistakes or integer overflows that,
    in the worst scenario, could lead to heap overflows.
    
    Link: https://github.com/KSPP/linux/issues/160
    Link: https://lkml.kernel.org/r/20211216022024.127375-1-wangweiyang2@huawei.com
    Signed-off-by: Wang Weiyang <wangweiyang2@huawei.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5b3be698a872c490dbed524f3e2463701ab21339
Author: Shakeel Butt <shakeelb@google.com>
Date:   Fri Jan 14 14:05:39 2022 -0800

    memcg: better bounds on the memcg stats updates
    
    Commit 11192d9c124d ("memcg: flush stats only if updated") added
    tracking of memcg stats updates which is used by the readers to flush
    only if the updates are over a certain threshold.  However each
    individual update can correspond to a large value change for a given
    stat.  For example adding or removing a hugepage to an LRU changes the
    stat by thp_nr_pages (512 on x86_64).
    
    Treating the update related to THP as one can keep the stat off, in
    theory, by (thp_nr_pages * nr_cpus * CHARGE_BATCH) before flush.
    
    To handle such scenarios, this patch adds consideration of the stat
    update value as well instead of just the update event.  In addition let
    the asyn flusher unconditionally flush the stats to put time limit on
    the stats skew and hopefully a lot less readers would need to flush.
    
    Link: https://lkml.kernel.org/r/20211118065350.697046-1-shakeelb@google.com
    Signed-off-by: Shakeel Butt <shakeelb@google.com>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: "Michal Koutný" <mkoutny@suse.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b6bf9abb0aa44e53ffe9c1e6e1d32568f5b25e4a
Author: Dan Schatzberg <schatzberg.dan@gmail.com>
Date:   Fri Jan 14 14:05:35 2022 -0800

    mm/memcg: add oom_group_kill memory event
    
    Our container agent wants to know when a container exits if it was OOM
    killed or not to report to the user.  We use memory.oom.group = 1 to
    ensure that OOM kills within the container's cgroup kill everything.
    Existing memory.events are insufficient for knowing if this triggered:
    
    1) Our current approach reads memory.events oom_kill and reports the
       container was killed if the value is non-zero. This is erroneous in
       some cases where containers create their children cgroups with
       memory.oom.group=1 as such OOM kills will get counted against the
       container cgroup's oom_kill counter despite not actually OOM killing
       the entire container.
    
    2) Reading memory.events.local will fail to identify OOM kills in leaf
       cgroups (that don't set memory.oom.group) within the container
       cgroup.
    
    This patch adds a new oom_group_kill event when memory.oom.group
    triggers to allow userspace to cleanly identify when an entire cgroup is
    oom killed.
    
    [schatzberg.dan@gmail.com: changes from Johannes and Chris]
      Link: https://lkml.kernel.org/r/20211213162511.2492267-1-schatzberg.dan@gmail.com
    
    Link: https://lkml.kernel.org/r/20211203162426.3375036-1-schatzberg.dan@gmail.com
    Signed-off-by: Dan Schatzberg <schatzberg.dan@gmail.com>
    Reviewed-by: Roman Gushchin <guro@fb.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Acked-by: Chris Down <chris@chrisdown.name>
    Reviewed-by: Shakeel Butt <shakeelb@google.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Tejun Heo <tj@kernel.org>
    Cc: Zefan Li <lizefan.x@bytedance.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Alex Shi <alexs@kernel.org>
    Cc: Wei Yang <richard.weiyang@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 46a53371f3fd9bf873fdd9c4df75b1cd86df1098
Author: Donghai Qiao <dqiao@redhat.com>
Date:   Fri Jan 14 14:05:32 2022 -0800

    mm/page_counter: remove an incorrect call to propagate_protected_usage()
    
    propagate_protected_usage() is called to propagate the usage change in
    the page_counter structure.  But there is a call to this function from
    page_counter_try_charge() when there is actually no usage change.  Hence
    this call should be removed.
    
    Link: https://lkml.kernel.org/r/20211118181125.3918222-1-dqiao@redhat.com
    Signed-off-by: Donghai Qiao <dqiao@redhat.com>
    Reviewed-by: Roman Gushchin <guro@fb.com>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 17c17367758059930246dde937cc7da9b8f3549e
Author: Muchun Song <songmuchun@bytedance.com>
Date:   Fri Jan 14 14:05:29 2022 -0800

    mm: memcontrol: make cgroup_memory_nokmem static
    
    Commit 494c1dfe855e ("mm: memcg/slab: create a new set of kmalloc-cg-<n>
    caches") makes cgroup_memory_nokmem global, however, it is unnecessary
    because there is already a function mem_cgroup_kmem_disabled() which
    exports it.
    
    Just make it static and replace it with mem_cgroup_kmem_disabled() in
    mm/slab_common.c.
    
    Link: https://lkml.kernel.org/r/20211109065418.21693-1-songmuchun@bytedance.com
    Signed-off-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Chris Down <chris@chrisdown.name>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Michal Hocko <mhocko@kernel.org>
    Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3795f46b83c66a2e4545460dec74c80b839faafe
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Fri Jan 14 14:05:26 2022 -0800

    mm/frontswap.c: use non-atomic '__set_bit()' when possible
    
    The 'a' and 'b' bitmaps are local to this function, so no concurrent
    access can occur.  So the non-atomic '__set_bit()' can be used to save a
    few cycles.
    
    Link: https://lkml.kernel.org/r/e52476da5cee57151745c5c3c934a69798dc6fa4.1638132190.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 62c9827cbb996c2c04f615ecd783ce28bcea894b
Author: Gang Li <ligang.bdlg@bytedance.com>
Date:   Fri Jan 14 14:05:23 2022 -0800

    shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
    
    Fix a data race in commit 779750d20b93 ("shmem: split huge pages beyond
    i_size under memory pressure").
    
    Here are call traces causing race:
    
       Call Trace 1:
         shmem_unused_huge_shrink+0x3ae/0x410
         ? __list_lru_walk_one.isra.5+0x33/0x160
         super_cache_scan+0x17c/0x190
         shrink_slab.part.55+0x1ef/0x3f0
         shrink_node+0x10e/0x330
         kswapd+0x380/0x740
         kthread+0xfc/0x130
         ? mem_cgroup_shrink_node+0x170/0x170
         ? kthread_create_on_node+0x70/0x70
         ret_from_fork+0x1f/0x30
    
       Call Trace 2:
         shmem_evict_inode+0xd8/0x190
         evict+0xbe/0x1c0
         do_unlinkat+0x137/0x330
         do_syscall_64+0x76/0x120
         entry_SYSCALL_64_after_hwframe+0x3d/0xa2
    
    A simple explanation:
    
    Image there are 3 items in the local list (@list).  In the first
    traversal, A is not deleted from @list.
    
      1)    A->B->C
            ^
            |
            pos (leave)
    
    In the second traversal, B is deleted from @list.  Concurrently, A is
    deleted from @list through shmem_evict_inode() since last reference
    counter of inode is dropped by other thread.  Then the @list is corrupted.
    
      2)    A->B->C
            ^  ^
            |  |
         evict pos (drop)
    
    We should make sure the inode is either on the global list or deleted from
    any local list before iput().
    
    Fixed by moving inodes back to global list before we put them.
    
    [akpm@linux-foundation.org: coding style fixes]
    
    Link: https://lkml.kernel.org/r/20211125064502.99983-1-ligang.bdlg@bytedance.com
    Fixes: 779750d20b93 ("shmem: split huge pages beyond i_size under memory pressure")
    Signed-off-by: Gang Li <ligang.bdlg@bytedance.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: <stable@vger.kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a7605426666196c5a460dd3de6f8dac1d3c21f00
Author: Yang Shi <shy828301@gmail.com>
Date:   Fri Jan 14 14:05:19 2022 -0800

    mm: shmem: don't truncate page if memory failure happens
    
    The current behavior of memory failure is to truncate the page cache
    regardless of dirty or clean.  If the page is dirty the later access
    will get the obsolete data from disk without any notification to the
    users.  This may cause silent data loss.  It is even worse for shmem
    since shmem is in-memory filesystem, truncating page cache means
    discarding data blocks.  The later read would return all zero.
    
    The right approach is to keep the corrupted page in page cache, any
    later access would return error for syscalls or SIGBUS for page fault,
    until the file is truncated, hole punched or removed.  The regular
    storage backed filesystems would be more complicated so this patch is
    focused on shmem.  This also unblock the support for soft offlining
    shmem THP.
    
    [akpm@linux-foundation.org: coding style fixes]
    [arnd@arndb.de: fix uninitialized variable use in me_pagecache_clean()]
      Link: https://lkml.kernel.org/r/20211022064748.4173718-1-arnd@kernel.org
    [Fix invalid pointer dereference in shmem_read_mapping_page_gfp() with a
     slight different implementation from what Ajay Garg <ajaygargnsit@gmail.com>
     and Muchun Song <songmuchun@bytedance.com> proposed and reworked the
     error handling of shmem_write_begin() suggested by Linus]
      Link: https://lore.kernel.org/linux-mm/20211111084617.6746-1-ajaygargnsit@gmail.com/
    
    Link: https://lkml.kernel.org/r/20211020210755.23964-6-shy828301@gmail.com
    Link: https://lkml.kernel.org/r/20211116193247.21102-1-shy828301@gmail.com
    Signed-off-by: Yang Shi <shy828301@gmail.com>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Cc: Hugh Dickins <hughd@google.com>
    Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
    Cc: Matthew Wilcox <willy@infradead.org>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Oscar Salvador <osalvador@suse.de>
    Cc: Peter Xu <peterx@redhat.com>
    Cc: Ajay Garg <ajaygargnsit@gmail.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Andy Lavr <andy.lavr@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 28b0ee3fb35047bd2bac57cc5a051b26bbd9b194
Author: Li Xinhai <lixinhai.lxh@gmail.com>
Date:   Fri Jan 14 14:05:16 2022 -0800

    mm/gup.c: stricter check on THP migration entry during follow_pmd_mask
    
    When BUG_ON check for THP migration entry, the existing code only check
    thp_migration_supported case, but not for !thp_migration_supported case.
    If !thp_migration_supported() and !pmd_present(), the original code may
    dead loop in theory.  To make the BUG_ON check consistent, we need catch
    both cases.
    
    Move the BUG_ON check one step earlier, because if the bug happen we
    should know it instead of depend on FOLL_MIGRATION been used by caller.
    
    Because pmdval instead of *pmd is read by the is_pmd_migration_entry()
    check, the existing code don't help to avoid useless locking within
    pmd_migration_entry_wait(), so remove that check.
    
    Link: https://lkml.kernel.org/r/20211217062559.737063-1-lixinhai.lxh@gmail.com
    Signed-off-by: Li Xinhai <lixinhai.lxh@gmail.com>
    Reviewed-by: "Huang, Ying" <ying.huang@intel.com>
    Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
    Cc: Zi Yan <ziy@nvidia.com>
    Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 677b2a8c1f25db5b09c1ef5bf72faa39ea81d9cf
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Fri Jan 14 14:05:13 2022 -0800

    gup: avoid multiple user access locking/unlocking in fault_in_{read/write}able
    
    fault_in_readable() and fault_in_writeable() perform __get_user() and
    __put_user() in a loop, implying multiple user access locking/unlocking.
    
    To avoid that, use user access blocks.
    
    Link: https://lkml.kernel.org/r/720dcf79314acca1a78fae56d478cc851952149d.1637084492.git.christophe.leroy@csgroup.eu
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 43b93121056c524e2af77d561900ea856d32029c
Author: chiminghao <chi.minghao@zte.com.cn>
Date:   Fri Jan 14 14:05:10 2022 -0800

    mm/truncate.c: remove unneeded variable
    
    Return value directly instead of taking this in another redundant
    variable.
    
    Link: https://lkml.kernel.org/r/20211207083222.401594-1-chi.minghao@zte.com.cn
    Signed-off-by: chiminghao <chi.minghao@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cm>
    Reviewed-by: David Hildenbrand <david@redhat.com>
    Reviewed-by: Pankaj Gupta <pankaj.gupta@ionos.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 236476180c0f5d308fb313d5570d0b067307884c
Author: Anshuman Khandual <anshuman.khandual@arm.com>
Date:   Fri Jan 14 14:05:07 2022 -0800

    mm/debug_vm_pgtable: update comments regarding migration swap entries
    
    Commit 4dd845b5a3e5 ("mm/swapops: rework swap entry manipulation code")
    had changed migtation entry related helpers.  Just update
    debug_vm_pgatble() synced documentation to reflect those changes.
    
    Link: https://lkml.kernel.org/r/1641880417-24848-1-git-send-email-anshuman.khandual@arm.com
    Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3e9d80a891df3b1a5d77db47fa7fdf33ba71e5cb
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Jan 14 14:05:04 2022 -0800

    mm,fs: split dump_mapping() out from dump_page()
    
    dump_mapping() is a big chunk of dump_page(), and it'd be handy to be
    able to call it when we don't have a struct page.  Split it out and move
    it to fs/inode.c.  Take the opportunity to simplify some of the debug
    messages a little.
    
    Link: https://lkml.kernel.org/r/20211121121056.2870061-1-willy@infradead.org
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>
    Acked-by: Michal Hocko <mhocko@suse.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 26dca996ea7b1ac7008b6b6063fc88b849e3ac3e
Author: Andrey Konovalov <andreyknvl@gmail.com>
Date:   Fri Jan 14 14:05:01 2022 -0800

    kasan: fix quarantine conflicting with init_on_free
    
    KASAN's quarantine might save its metadata inside freed objects.  As
    this happens after the memory is zeroed by the slab allocator when
    init_on_free is enabled, the memory coming out of quarantine is not
    properly zeroed.
    
    This causes lib/test_meminit.c tests to fail with Generic KASAN.
    
    Zero the metadata when the object is removed from quarantine.
    
    Link: https://lkml.kernel.org/r/2805da5df4b57138fdacd671f5d227d58950ba54.1640037083.git.andreyknvl@google.com
    Fixes: 6471384af2a6 ("mm: security: introduce init_on_alloc=1 and init_on_free=1 boot options")
    Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
    Reviewed-by: Marco Elver <elver@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f98f966cd75002a71caec1b6d209da5762c0efac
Author: Marco Elver <elver@google.com>
Date:   Fri Jan 14 14:04:57 2022 -0800

    kasan: test: add test case for double-kmem_cache_destroy()
    
    Add a test case for double-kmem_cache_destroy() detection.
    
    Link: https://lkml.kernel.org/r/20211119142219.1519617-2-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit bed0a9b591492bb285ea88cd221e0412031396ca
Author: Marco Elver <elver@google.com>
Date:   Fri Jan 14 14:04:54 2022 -0800

    kasan: add ability to detect double-kmem_cache_destroy()
    
    Because mm/slab_common.c is not instrumented with software KASAN modes,
    it is not possible to detect use-after-free of the kmem_cache passed
    into kmem_cache_destroy().  In particular, because of the s->refcount--
    and subsequent early return if non-zero, KASAN would never be able to
    see the double-free via kmem_cache_free(kmem_cache, s).  To be able to
    detect a double-kmem_cache_destroy(), check accessibility of the
    kmem_cache, and in case of failure return early.
    
    While KASAN_HW_TAGS is able to detect such bugs, by checking
    accessibility and returning early we fail more gracefully and also avoid
    corrupting reused objects (where tags mismatch).
    
    A recent case of a double-kmem_cache_destroy() was detected by KFENCE:
    https://lkml.kernel.org/r/0000000000003f654905c168b09d@google.com, which
    was not detectable by software KASAN modes.
    
    Link: https://lkml.kernel.org/r/20211119142219.1519617-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Acked-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e5f4728767d2ec9e3eb122c74e224242d21ee650
Author: Marco Elver <elver@google.com>
Date:   Fri Jan 14 14:04:51 2022 -0800

    kasan: test: add globals left-out-of-bounds test
    
    Add a test checking that KASAN generic can also detect out-of-bounds
    accesses to the left of globals.
    
    Unfortunately it seems that GCC doesn't catch this (tested GCC 10, 11).
    The main difference between GCC's globals redzoning and Clang's is that
    GCC relies on using increased alignment to producing padding, where
    Clang's redzoning implementation actually adds real data after the
    global and doesn't rely on alignment to produce padding.  I believe this
    is the main reason why GCC can't reliably catch globals out-of-bounds in
    this case.
    
    Given this is now a known issue, to avoid failing the whole test suite,
    skip this test case with GCC.
    
    Link: https://lkml.kernel.org/r/20211117130714.135656-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reported-by: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
    Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 14606001efb48a17be31a5bec626c13ca49d783a
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:47 2022 -0800

    device-dax: compound devmap support
    
    Use the newly added compound devmap facility which maps the assigned dax
    ranges as compound pages at a page size of @align.
    
    dax devices are created with a fixed @align (huge page size) which is
    enforced through as well at mmap() of the device.  Faults, consequently
    happen too at the specified @align specified at the creation, and those
    don't change throughout dax device lifetime.  MCEs unmap a whole dax
    huge page, as well as splits occurring at the configured page size.
    
    Performance measured by gup_test improves considerably for
    unpin_user_pages() and altmap with NVDIMMs:
    
      $ gup_test -f /dev/dax1.0 -m 16384 -r 10 -S -a -n 512 -w
      (pin_user_pages_fast 2M pages) put:~71 ms -> put:~22 ms
      [altmap]
      (pin_user_pages_fast 2M pages) get:~524ms put:~525 ms -> get: ~127ms put:~71ms
    
       $ gup_test -f /dev/dax1.0 -m 129022 -r 10 -S -a -n 512 -w
      (pin_user_pages_fast 2M pages) put:~513 ms -> put:~188 ms
      [altmap with -m 127004]
      (pin_user_pages_fast 2M pages) get:~4.1 secs put:~4.12 secs -> get:~1sec put:~563ms
    
    .. as well as unpin_user_page_range_dirty_lock() being just as effective
    as THP/hugetlb[0] pages.
    
    [0] https://lore.kernel.org/linux-mm/20210212130843.13865-5-joao.m.martins@oracle.com/
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-12-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6ec228b6fef5ad3a1f19e76c29640a9161415240
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:43 2022 -0800

    device-dax: remove pfn from __dev_dax_{pte,pmd,pud}_fault()
    
    After moving the page mapping to be set prior to pte insertion, the pfn
    in dev_dax_huge_fault() no longer is necessary.  Remove it, as well as
    the @pfn argument passed to the internal fault handler helpers.
    
    [akpm@linux-foundation.org: fix CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=n build]
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-11-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Suggested-by: Christoph Hellwig <hch@lst.de>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 0e7325f03f09802d1667b8860e10fe39c25bf14c
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:40 2022 -0800

    device-dax: set mapping prior to vmf_insert_pfn{,_pmd,pud}()
    
    Normally, the @page mapping is set prior to inserting the page into a
    page table entry.  Make device-dax adhere to the same ordering, rather
    than setting mapping after the PTE is inserted.
    
    The address_space never changes and it is always associated with the
    same inode and underlying pages.  So, the page mapping is set once but
    cleared when the struct pages are removed/freed (i.e.  after
    {devm_}memunmap_pages()).
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-10-joao.m.martins@oracle.com
    Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a0fb038e50d72f8e60731dc48fb83a3a141b822e
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:36 2022 -0800

    device-dax: factor out page mapping initialization
    
    Move initialization of page->mapping into a separate helper.
    
    This is in preparation to move the mapping set to be prior to inserting
    the page table entry and also for tidying up compound page handling into
    one helper.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-9-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dan Williams <dan.j.williams@intel.com>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit fc65c4eb0b2a27c30d35636650e3f4ddb07506cd
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:33 2022 -0800

    device-dax: ensure dev_dax->pgmap is valid for dynamic devices
    
    Right now, only static dax regions have a valid @pgmap pointer in its
    struct dev_dax.  Dynamic dax case however, do not.
    
    In preparation for device-dax compound devmap support, make sure that
    dev_dax pgmap field is set after it has been allocated and initialized.
    
    dynamic dax device have the @pgmap is allocated at probe() and it's
    managed by devm (contrast to static dax region which a pgmap is provided
    and dax core kfrees it).  So in addition to ensure a valid @pgmap, clear
    the pgmap when the dynamic dax device is released to avoid the same
    pgmap ranges to be re-requested across multiple region device reconfigs.
    
    Add a static_dev_dax() and use that helper in dev_dax_probe() to ensure
    the initialization differences between dynamic and static regions are
    more explicit.  While at it, consolidate the ranges initialization when
    we allocate the @pgmap for the dynamic dax region case.  Also take the
    opportunity to document the differences between static and dynamic da
    regions.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-8-joao.m.martins@oracle.com
    Suggested-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 09b80137033dbc5f1d197e99116527c0f8d253f2
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:29 2022 -0800

    device-dax: use struct_size()
    
    Use the struct_size() helper for the size of a struct with variable
    array member at the end, rather than manually calculating it.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-7-joao.m.martins@oracle.com
    Suggested-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit b9b5777f09be84d0de472ded2253d2f5101427f2
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:26 2022 -0800

    device-dax: use ALIGN() for determining pgoff
    
    Rather than calculating @pgoff manually, switch to ALIGN() instead.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-6-joao.m.martins@oracle.com
    Suggested-by: Dan Williams <dan.j.williams@intel.com>
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c4386bd8ee3a921c3c799b7197dc898ade76a453
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:22 2022 -0800

    mm/memremap: add ZONE_DEVICE support for compound pages
    
    Add a new @vmemmap_shift property for struct dev_pagemap which specifies
    that a devmap is composed of a set of compound pages of order
    @vmemmap_shift, instead of base pages.  When a compound page devmap is
    requested, all but the first page are initialised as tail pages instead
    of order-0 pages.
    
    For certain ZONE_DEVICE users like device-dax which have a fixed page
    size, this creates an opportunity to optimize GUP and GUP-fast walkers,
    treating it the same way as THP or hugetlb pages.
    
    Additionally, commit 7118fc2906e2 ("hugetlb: address ref count racing in
    prep_compound_gigantic_page") removed set_page_count() because the
    setting of page ref count to zero was redundant.  devmap pages don't
    come from page allocator though and only head page refcount is used for
    compound pages, hence initialize tail page count to zero.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-5-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 46487e0095f895c25da9feae27dc06d2aa76793d
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:18 2022 -0800

    mm/page_alloc: refactor memmap_init_zone_device() page init
    
    Move struct page init to an helper function __init_zone_device_page().
    
    This is in preparation for sharing the storage for compound page
    metadata.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-4-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Mike Kravetz <mike.kravetz@oracle.com>
    Cc: Muchun Song <songmuchun@bytedance.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 5b24eeef06701cca6852f1bf768248ccc912819b
Author: Joao Martins <joao.m.martins@oracle.com>
Date:   Fri Jan 14 14:04:15 2022 -0800

    mm/page_alloc: split prep_compound_page into head and tail subparts
    
    Patch series "mm, device-dax: Introduce compound pages in devmap", v7.
    
    This series converts device-dax to use compound pages, and moves away
    from the 'struct page per basepage on PMD/PUD' that is done today.
    
    Doing so
     1) unlocks a few noticeable improvements on unpin_user_pages() and
        makes device-dax+altmap case 4x times faster in pinning (numbers
        below and in last patch)
     2) as mentioned in various other threads it's one important step
        towards cleaning up ZONE_DEVICE refcounting.
    
    I've split the compound pages on devmap part from the rest based on
    recent discussions on devmap pending and future work planned[5][6].
    There is consensus that device-dax should be using compound pages to
    represent its PMD/PUDs just like HugeTLB and THP, and that leads to less
    specialization of the dax parts.  I will pursue the rest of the work in
    parallel once this part is merged, particular the GUP-{slow,fast}
    improvements [7] and the tail struct page deduplication memory savings
    part[8].
    
    To summarize what the series does:
    
    Patch 1: Prepare hwpoisoning to work with dax compound pages.
    
    Patches 2-3: Split the current utility function of prep_compound_page()
    into head and tail and use those two helpers where appropriate to take
    advantage of caches being warm after __init_single_page().  This is used
    when initializing zone device when we bring up device-dax namespaces.
    
    Patches 4-10: Add devmap support for compound pages in device-dax.
    memmap_init_zone_device() initialize its metadata as compound pages, and
    it introduces a new devmap property known as vmemmap_shift which
    outlines how the vmemmap is structured (defaults to base pages as done
    today).  The property describe the page order of the metadata
    essentially.  While at it do a few cleanups in device-dax in patches
    5-9.  Finally enable device-dax usage of devmap @vmemmap_shift to a
    value based on its own @align property.  @vmemmap_shift returns 0 by
    default (which is today's case of base pages in devmap, like fsdax or
    the others) and the usage of compound devmap is optional.  Starting with
    device-dax (*not* fsdax) we enable it by default.  There are a few
    pinning improvements particular on the unpinning case and altmap, as
    well as unpin_user_page_range_dirty_lock() being just as effective as
    THP/hugetlb[0] pages.
    
        $ gup_test -f /dev/dax1.0 -m 16384 -r 10 -S -a -n 512 -w
        (pin_user_pages_fast 2M pages) put:~71 ms -> put:~22 ms
        [altmap]
        (pin_user_pages_fast 2M pages) get:~524ms put:~525 ms -> get: ~127ms put:~71ms
    
         $ gup_test -f /dev/dax1.0 -m 129022 -r 10 -S -a -n 512 -w
        (pin_user_pages_fast 2M pages) put:~513 ms -> put:~188 ms
        [altmap with -m 127004]
        (pin_user_pages_fast 2M pages) get:~4.1 secs put:~4.12 secs -> get:~1sec put:~563ms
    
    Tested on x86 with 1Tb+ of pmem (alongside registering it with RDMA with
    and without altmap), alongside gup_test selftests with dynamic dax
    regions and static dax regions.  Coupled with ndctl unit tests for
    dynamic dax devices that exercise all of this.  Note, for dynamic dax
    regions I had to revert commit 8aa83e6395 ("x86/setup: Call
    early_reserve_memory() earlier"), it is a known issue that this commit
    broke efi_fake_mem=.
    
    This patch (of 11):
    
    Split the utility function prep_compound_page() into head and tail
    counterparts, and use them accordingly.
    
    This is in preparation for sharing the storage for compound page
    metadata.
    
    Link: https://lkml.kernel.org/r/20211202204422.26777-1-joao.m.martins@oracle.com
    Link: https://lkml.kernel.org/r/20211202204422.26777-3-joao.m.martins@oracle.com
    Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
    Acked-by: Mike Kravetz <mike.kravetz@oracle.com>
    Reviewed-by: Dan Williams <dan.j.williams@intel.com>
    Reviewed-by: Muchun Song <songmuchun@bytedance.com>
    Cc: Vishal Verma <vishal.l.verma@intel.com>
    Cc: Dave Jiang <dave.jiang@intel.com>
    Cc: Naoya Horiguchi <naoya.horiguchi@nec.com>
    Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: John Hubbard <jhubbard@nvidia.com>
    Cc: Jane Chu <jane.chu@oracle.com>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: Christoph Hellwig <hch@lst.de>
    Cc: Jason Gunthorpe <jgg@nvidia.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 60115fa54ad7b913b7cb5844e6b7ffeb842d55f2
Author: Kefeng Wang <wangkefeng.wang@huawei.com>
Date:   Fri Jan 14 14:04:11 2022 -0800

    mm: defer kmemleak object creation of module_alloc()
    
    Yongqiang reports a kmemleak panic when module insmod/rmmod with KASAN
    enabled(without KASAN_VMALLOC) on x86[1].
    
    When the module area allocates memory, it's kmemleak_object is created
    successfully, but the KASAN shadow memory of module allocation is not
    ready, so when kmemleak scan the module's pointer, it will panic due to
    no shadow memory with KASAN check.
    
      module_alloc
        __vmalloc_node_range
          kmemleak_vmalloc
                                    kmemleak_scan
                                      update_checksum
        kasan_module_alloc
          kmemleak_ignore
    
    Note, there is no problem if KASAN_VMALLOC enabled, the modules area
    entire shadow memory is preallocated.  Thus, the bug only exits on ARCH
    which supports dynamic allocation of module area per module load, for
    now, only x86/arm64/s390 are involved.
    
    Add a VM_DEFER_KMEMLEAK flags, defer vmalloc'ed object register of
    kmemleak in module_alloc() to fix this issue.
    
    [1] https://lore.kernel.org/all/6d41e2b9-4692-5ec4-b1cd-cbe29ae89739@huawei.com/
    
    [wangkefeng.wang@huawei.com: fix build]
      Link: https://lkml.kernel.org/r/20211125080307.27225-1-wangkefeng.wang@huawei.com
    [akpm@linux-foundation.org: simplify ifdefs, per Andrey]
      Link: https://lkml.kernel.org/r/CA+fCnZcnwJHUQq34VuRxpdoY6_XbJCDJ-jopksS5Eia4PijPzw@mail.gmail.com
    
    Link: https://lkml.kernel.org/r/20211124142034.192078-1-wangkefeng.wang@huawei.com
    Fixes: 793213a82de4 ("s390/kasan: dynamic shadow mem allocation for modules")
    Fixes: 39d114ddc682 ("arm64: add KASAN support")
    Fixes: bebf56a1b176 ("kasan: enable instrumentation of global variables")
    Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
    Reported-by: Yongqiang Liu <liuyongqiang13@huawei.com>
    Cc: Andrey Konovalov <andreyknvl@gmail.com>
    Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Will Deacon <will@kernel.org>
    Cc: Heiko Carstens <hca@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Cc: Alexander Gordeev <agordeev@linux.ibm.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 972fa3a7c17c9d60212e32ecc0205dc585b1e769
Author: Calvin Zhang <calvinzhang.cool@gmail.com>
Date:   Fri Jan 14 14:04:08 2022 -0800

    mm: kmemleak: alloc gray object for reserved region with direct map
    
    Reserved regions with direct mapping may contain references to other
    regions.  CMA region with fixed location is reserved without creating
    kmemleak_object for it.
    
    So add them as gray kmemleak objects.
    
    Link: https://lkml.kernel.org/r/20211123090641.3654006-1-calvinzhang.cool@gmail.com
    Signed-off-by: Calvin Zhang <calvinzhang.cool@gmail.com>
    Cc: Rob Herring <robh+dt@kernel.org>
    Cc: Frank Rowand <frowand.list@gmail.com>
    Cc: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ad1a3e15fcd3b8ba0f5f60f6a2fe3938274fdf65
Author: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
Date:   Fri Jan 14 14:04:04 2022 -0800

    kmemleak: fix kmemleak false positive report with HW tag-based kasan enable
    
    With HW tag-based kasan enable, We will get the warning when we free
    object whose address starts with 0xFF.
    
    It is because kmemleak rbtree stores tagged object and this freeing
    object's tag does not match with rbtree object.
    
    In the example below, kmemleak rbtree stores the tagged object in the
    kmalloc(), and kfree() gets the pointer with 0xFF tag.
    
    Call sequence:
        ptr = kmalloc(size, GFP_KERNEL);
        page = virt_to_page(ptr);
        offset = offset_in_page(ptr);
        kfree(page_address(page) + offset);
        ptr = kmalloc(size, GFP_KERNEL);
    
    A sequence like that may cause the warning as following:
    
     1) Freeing unknown object:
    
        In kfree(), we will get free unknown object warning in
        kmemleak_free(). Because object(0xFx) in kmemleak rbtree and
        pointer(0xFF) in kfree() have different tag.
    
     2) Overlap existing:
    
        When we allocate that object with the same hw-tag again, we will
        find the overlap in the kmemleak rbtree and kmemleak thread will be
        killed.
    
            kmemleak: Freeing unknown object at 0xffff000003f88000
            CPU: 5 PID: 177 Comm: cat Not tainted 5.16.0-rc1-dirty #21
            Hardware name: linux,dummy-virt (DT)
            Call trace:
             dump_backtrace+0x0/0x1ac
             show_stack+0x1c/0x30
             dump_stack_lvl+0x68/0x84
             dump_stack+0x1c/0x38
             kmemleak_free+0x6c/0x70
             slab_free_freelist_hook+0x104/0x200
             kmem_cache_free+0xa8/0x3d4
             test_version_show+0x270/0x3a0
             module_attr_show+0x28/0x40
             sysfs_kf_seq_show+0xb0/0x130
             kernfs_seq_show+0x30/0x40
             seq_read_iter+0x1bc/0x4b0
             seq_read_iter+0x1bc/0x4b0
             kernfs_fop_read_iter+0x144/0x1c0
             generic_file_splice_read+0xd0/0x184
             do_splice_to+0x90/0xe0
             splice_direct_to_actor+0xb8/0x250
             do_splice_direct+0x88/0xd4
             do_sendfile+0x2b0/0x344
             __arm64_sys_sendfile64+0x164/0x16c
             invoke_syscall+0x48/0x114
             el0_svc_common.constprop.0+0x44/0xec
             do_el0_svc+0x74/0x90
             el0_svc+0x20/0x80
             el0t_64_sync_handler+0x1a8/0x1b0
             el0t_64_sync+0x1ac/0x1b0
            ...
            kmemleak: Cannot insert 0xf2ff000003f88000 into the object search tree (overlaps existing)
            CPU: 5 PID: 178 Comm: cat Not tainted 5.16.0-rc1-dirty #21
            Hardware name: linux,dummy-virt (DT)
            Call trace:
             dump_backtrace+0x0/0x1ac
             show_stack+0x1c/0x30
             dump_stack_lvl+0x68/0x84
             dump_stack+0x1c/0x38
             create_object.isra.0+0x2d8/0x2fc
             kmemleak_alloc+0x34/0x40
             kmem_cache_alloc+0x23c/0x2f0
             test_version_show+0x1fc/0x3a0
             module_attr_show+0x28/0x40
             sysfs_kf_seq_show+0xb0/0x130
             kernfs_seq_show+0x30/0x40
             seq_read_iter+0x1bc/0x4b0
             kernfs_fop_read_iter+0x144/0x1c0
             generic_file_splice_read+0xd0/0x184
             do_splice_to+0x90/0xe0
             splice_direct_to_actor+0xb8/0x250
             do_splice_direct+0x88/0xd4
             do_sendfile+0x2b0/0x344
             __arm64_sys_sendfile64+0x164/0x16c
             invoke_syscall+0x48/0x114
             el0_svc_common.constprop.0+0x44/0xec
             do_el0_svc+0x74/0x90
             el0_svc+0x20/0x80
             el0t_64_sync_handler+0x1a8/0x1b0
             el0t_64_sync+0x1ac/0x1b0
            kmemleak: Kernel memory leak detector disabled
            kmemleak: Object 0xf2ff000003f88000 (size 128):
            kmemleak:   comm "cat", pid 177, jiffies 4294921177
            kmemleak:   min_count = 1
            kmemleak:   count = 0
            kmemleak:   flags = 0x1
            kmemleak:   checksum = 0
            kmemleak:   backtrace:
                 kmem_cache_alloc+0x23c/0x2f0
                 test_version_show+0x1fc/0x3a0
                 module_attr_show+0x28/0x40
                 sysfs_kf_seq_show+0xb0/0x130
                 kernfs_seq_show+0x30/0x40
                 seq_read_iter+0x1bc/0x4b0
                 kernfs_fop_read_iter+0x144/0x1c0
                 generic_file_splice_read+0xd0/0x184
                 do_splice_to+0x90/0xe0
                 splice_direct_to_actor+0xb8/0x250
                 do_splice_direct+0x88/0xd4
                 do_sendfile+0x2b0/0x344
                 __arm64_sys_sendfile64+0x164/0x16c
                 invoke_syscall+0x48/0x114
                 el0_svc_common.constprop.0+0x44/0xec
                 do_el0_svc+0x74/0x90
            kmemleak: Automatic memory scanning thread ended
    
    [akpm@linux-foundation.org: whitespace tweak]
    
    Link: https://lkml.kernel.org/r/20211118054426.4123-1-Kuan-Ying.Lee@mediatek.com
    Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
    Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
    Cc: Doug Berger <opendmb@gmail.com>
    Cc: Mel Gorman <mgorman@techsingularity.net>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Vlastimil Babka <vbabka@suse.cz>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c29b5b3d33a61e122cb493917ba51c82bcac4121
Author: Muchun Song <songmuchun@bytedance.com>
Date:   Fri Jan 14 14:04:01 2022 -0800

    mm: slab: make slab iterator functions static
    
    There is no external users of slab_start/next/stop(), so make them
    static.  And the memory.kmem.slabinfo is deprecated, which outputs
    nothing now, so move memcg_slab_show() into mm/memcontrol.c and rename
    it to mem_cgroup_slab_show to be consistent with other function names.
    
    Link: https://lkml.kernel.org/r/20211109133359.32881-1-songmuchun@bytedance.com
    Signed-off-by: Muchun Song <songmuchun@bytedance.com>
    Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: David Rientjes <rientjes@google.com>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7302e91f39a81a9c2efcf4bc5749d18128366945
Author: Marco Elver <elver@google.com>
Date:   Fri Jan 14 14:03:58 2022 -0800

    mm/slab_common: use WARN() if cache still has objects on destroy
    
    Calling kmem_cache_destroy() while the cache still has objects allocated
    is a kernel bug, and will usually result in the entire cache being
    leaked.  While the message in kmem_cache_destroy() resembles a warning,
    it is currently not implemented using a real WARN().
    
    This is problematic for infrastructure testing the kernel, all of which
    rely on the specific format of WARN()s to pick up on bugs.
    
    Some 13 years ago this used to be a simple WARN_ON() in slub, but commit
    d629d8195793 ("slub: improve kmem_cache_destroy() error message")
    changed it into an open-coded warning to avoid confusion with a bug in
    slub itself.
    
    Instead, turn the open-coded warning into a real WARN() with the message
    preserved, so that test systems can actually identify these issues, and
    we get all the other benefits of using a normal WARN().  The warning
    message is extended with "when called from <caller-ip>" to make it even
    clearer where the fault lies.
    
    For most configurations this is only a cosmetic change, however, note
    that WARN() here will now also respect panic_on_warn.
    
    Link: https://lkml.kernel.org/r/20211102170733.648216-1-elver@google.com
    Signed-off-by: Marco Elver <elver@google.com>
    Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: David Rientjes <rientjes@google.com>
    Cc: Christoph Lameter <cl@linux.com>
    Cc: Pekka Enberg <penberg@kernel.org>
    Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a12cf8b32ceed9c60c8bba7c46077ebffbfb9db2
Author: Amit Daniel Kachhap <amit.kachhap@arm.com>
Date:   Fri Jan 14 14:03:55 2022 -0800

    fs/ioctl: remove unnecessary __user annotation
    
    __user annotations are used by the checker (e.g sparse) to mark user
    pointers.  However here __user is applied to a struct directly, without a
    pointer being directly involved.
    
    Although the presence of __user does not cause sparse to emit a warning,
    __user should be removed for consistency with other uses of offsetof().
    
    Note: No functional changes intended.
    
    Link: https://lkml.kernel.org/r/20211122101256.7875-1-amit.kachhap@arm.com
    Signed-off-by: Amit Daniel Kachhap <amit.kachhap@arm.com>
    Cc: Vincenzo Frascino <Vincenzo.Frascino@arm.com>
    Cc: Kevin Brodsky <Kevin.Brodsky@arm.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9a25d051502ca1f19af3fd8e196c408a4a9c9fbb
Author: Colin Ian King <colin.king@intel.com>
Date:   Fri Jan 14 14:03:51 2022 -0800

    ocfs2: remove redundant assignment to variable free_space
    
    The variable 'free_space' is being initialized with a value that is not
    read, it is being re-assigned later in the two paths of an if statement.
    The early initialization is redundant and can be removed.
    
    Link: https://lkml.kernel.org/r/20220112230411.1090761-1-colin.i.king@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d141b39b398460391b98b817fa6284773e842c45
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri Jan 14 14:03:48 2022 -0800

    ocfs2: cluster: use default_groups in kobj_type
    
    There are currently two ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.
    
    Move the ocfs2 cluster sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Link: https://lkml.kernel.org/r/20220106102028.3345634-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Tested-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f018844f834a2fc3bc7ba5f6915d5020e930a086
Author: Colin Ian King <colin.king@intel.com>
Date:   Fri Jan 14 14:03:45 2022 -0800

    ocfs2: remove redundant assignment to pointer root_bh
    
    The variable 'root_bh' is being initialized with a value that is not
    read, it is being re-assigned later on closer to its use.  The early
    initialization is redundant and can be removed.
    
    Link: https://lkml.kernel.org/r/20211228013719.620923-1-colin.i.king@gmail.com
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 59430cc1141caf75840bd69877b59d7bf292829e
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri Jan 14 14:03:41 2022 -0800

    ocfs2: use default_groups in kobj_type
    
    There are currently two ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.
    
    Move the ocfs2 code to use default_groups field which has been the
    preferred way since aa30f47cf666 ("kobject: Add support for default
    attribute groups to kobj_type") so that we can soon get rid of the
    obsolete default_attrs field.
    
    Link: https://lkml.kernel.org/r/20211228144517.391660-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e07bf00c40c6cce051ca7f95a6050d2a195b4f98
Author: Joseph Qi <joseph.qi@linux.alibaba.com>
Date:   Fri Jan 14 14:03:38 2022 -0800

    ocfs2: clearly handle ocfs2_grab_pages_for_write() return value
    
    ocfs2_grab_pages_for_write() may return -EAGAIN if write context type is
    mmap and it could not lock the target page.  In this case, we exit with
    no error and no target page.  And then trigger the caller page_mkwrite()
    to retry.
    
    Since there are other caller types, e.g.  buffer and direct io, make the
    return value handling more clear.
    
    Link: https://lkml.kernel.org/r/20211206065051.103353-1-joseph.qi@linux.alibaba.com
    Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 783cc68d6143da3c8bc6322b80abd96640f6066f
Author: Zhang Mingyu <zhang.mingyu@zte.com.cn>
Date:   Fri Jan 14 14:03:35 2022 -0800

    ocfs2: use BUG_ON instead of if condition followed by BUG.
    
    This issue was detected with the help of Coccinelle.
    
    Link: https://lkml.kernel.org/r/20211105014424.75372-1-zhang.mingyu@zte.com.cn
    Signed-off-by: Zhang Mingyu <zhang.mingyu@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
    Cc: Mark Fasheh <mark@fasheh.com>
    Cc: Joel Becker <jlbec@evilplan.org>
    Cc: Junxiao Bi <junxiao.bi@oracle.com>
    Cc: Changwei Ge <gechangwei@live.cn>
    Cc: Gang He <ghe@suse.com>
    Cc: Jun Piao <piaojun@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9eec1d897139e5de287af5d559a02b811b844d82
Author: Zheng Liang <zhengliang6@huawei.com>
Date:   Fri Jan 14 14:03:31 2022 -0800

    squashfs: provide backing_dev_info in order to disable read-ahead
    
    Commit c1f6925e1091 ("mm: put readahead pages in cache earlier") causes
    the read performance of squashfs to deteriorate.Through testing, we find
    that the performance will be back by closing the readahead of squashfs.
    
    So we want to learn the way of ubifs, provides backing_dev_info and
    disable read-ahead
    
    We tested the following data by fio.
    squashfs image blocksize=128K
    test command:
    
      fio --name basic --bs=? --filename="/mnt/test_file" --rw=? --iodepth=1 --ioengine=psync --runtime=200 --time_based
    
      turn on squashfs readahead in 5.10 kernel
      bs(k)      read/randread           MB/s
      4            randread              271
      128          randread              231
      1024         randread              246
      4            read                  310
      128          read                  245
      1024         read                  247
    
      turn off squashfs readahead in 5.10 kernel
      bs(k)      read/randread           MB/s
      4            randread              293
      128          randread              330
      1024         randread              363
      4            read                  338
      128          read                  360
      1024         read                  365
    
      turn on squashfs readahead and revert the
      commit c1f6925e1091("mm: put readahead
      pages in cache earlier") in 5.10 kernel
      bs(k)      read/randread           MB/s
      4           randread               289
      128         randread               306
      1024        randread               335
      4           read                   337
      128         read                   336
      1024        read                   338
    
    Link: https://lkml.kernel.org/r/20211116113141.1391026-1-zhengliang6@huawei.com
    Signed-off-by: Zheng Liang <zhengliang6@huawei.com>
    Reviewed-by: Phillip Lougher <phillip@squashfs.org.uk>
    Cc: Zhang Yi <yi.zhang@huawei.com>
    Cc: Hou Tao <houtao1@huawei.com>
    Cc: Miao Xie <miaoxie@huawei.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 7e0af97853954afd995598ac8dac670a734ade17
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Fri Jan 14 14:03:28 2022 -0800

    fs/ntfs/attrib.c: fix one kernel-doc comment
    
    The comments for the file should not be in kernel-doc format:
    
    /**
     * attrib.c - NTFS attribute operations.  Part of the Linux-NTFS
    
    as it causes it to be incorrectly identified for function
    ntfs_map_runlist_nolock(), causing some warnings found by running
    scripts/kernel-doc.:
    
      fs/ntfs/attrib.c:25: warning: Incorrect use of kernel-doc format:  * ntfs_map_runlist_nolock - map (a part of) a runlist of an ntfs inode
      fs/ntfs/attrib.c:71: warning: Function parameter or member 'ni' not described in 'ntfs_map_runlist_nolock'
      fs/ntfs/attrib.c:71: warning: Function parameter or member 'vcn' not described in 'ntfs_map_runlist_nolock'
      fs/ntfs/attrib.c:71: warning: Function parameter or member 'ctx' not described in 'ntfs_map_runlist_nolock'
      fs/ntfs/attrib.c:71: warning: expecting prototype for attrib.c - NTFS attribute operations.  Part of the Linux(). Prototype was for ntfs_map_runlist_nolock() instead
    
    Link: https://lkml.kernel.org/r/20220106015145.67067-1-yang.lee@linux.alibaba.com
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Anton Altaparmakov <anton@tuxera.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 9a69f2b0e4180dc289d0f68842f9e8b146e926f7
Author: Drew Fustini <dfustini@baylibre.com>
Date:   Fri Jan 14 14:03:25 2022 -0800

    scripts/spelling.txt: add "oveflow"
    
    Add typo "oveflow" for "overflow".  This typo was found and fixed in
    tools/testing/selftests/bpf/prog_tests/btf_dump.c
    
    Link: https://lore.kernel.org/all/20211122070528.837806-1-dfustini@baylibre.com/
    Link: https://lkml.kernel.org/r/20211122072302.839102-1-dfustini@baylibre.com
    Signed-off-by: Drew Fustini <dfustini@baylibre.com>
    Suggested-by: Gustavo A. R. Silva <gustavoars@kernel.org>
    Cc: Colin Ian King <colin.king@intel.com>
    Cc: Drew Fustini <dfustini@baylibre.com>
    Cc: zuoqilin <zuoqilin@yulong.com>
    Cc: Tom Saeger <tom.saeger@oracle.com>
    Cc: Sven Eckelmann <sven@narfation.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit a7eddfc92bbd2463a89dd22011c047509e6c52a8
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Fri Jan 14 14:03:22 2022 -0800

    ia64: topology: use default_groups in kobj_type
    
    There are currently two ways to create a set of sysfs files for a kobj_type,
    through the default_attrs field, and the default_groups field.
    
    Move the ia64 topology sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Link: https://lkml.kernel.org/r/20220104154800.1287947-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Mike Rapoport <rppt@kernel.org>
    Cc: David Hildenbrand <david@redhat.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit c5c2135412bdb11b419e41a0c128e423d8bf4f65
Author: Jason Wang <wangborong@cdjrlc.com>
Date:   Fri Jan 14 14:03:19 2022 -0800

    ia64: fix typo in a comment
    
    The double `the' in a comment is repeated, thus it should be removed.
    
    Link: https://lkml.kernel.org/r/20211113030316.22650-1-wangborong@cdjrlc.com
    Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 6c4420b09267050bc47b3999d80457a8dabaeb89
Author: Yang Guang <yang.guang5@zte.com.cn>
Date:   Fri Jan 14 14:03:16 2022 -0800

    arch/ia64/kernel/setup.c: use swap() to make code cleaner
    
    Use the macro 'swap()' defined in 'include/linux/minmax.h' to avoid
    opencoding it.
    
    Link: https://lkml.kernel.org/r/20211104001908.695110-1-yang.guang5@zte.com.cn
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Yang Guang <yang.guang5@zte.com.cn>
    Cc: David Yang <davidcomponentone@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit f2fed022aa0a1bce86ca02e16f6c5832711e6424
Author: Yang Guang <yang.guang5@zte.com.cn>
Date:   Fri Jan 14 14:03:13 2022 -0800

    ia64: module: use swap() to make code cleaner
    
    Use the macro 'swap()' defined in 'include/linux/minmax.h' to avoid
    opencoding it.
    
    Link: https://lkml.kernel.org/r/20211104062642.1506539-1-yang.guang5@zte.com.cn
    Signed-off-by: Yang Guang <yang.guang5@zte.com.cn>
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Cc: David Yang <davidcomponentone@gmail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit ff78f6679d2e223e073fcbdc8f70b6bc0abadf99
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:03:10 2022 -0800

    trace/hwlat: make use of the helper function kthread_run_on_cpu()
    
    Replace kthread_create_on_cpu/wake_up_process() with kthread_run_on_cpu()
    to simplify the code.
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-7-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 11e4e3523da98c065a6c249013ace0d388e41c25
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:03:06 2022 -0800

    trace/osnoise: make use of the helper function kthread_run_on_cpu()
    
    Replace kthread_create_on_cpu/wake_up_process() with kthread_run_on_cpu()
    to simplify the code.
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-6-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3b9cb4ba4b54ecc6cf7d04ea9085d2ad2be48733
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:03:02 2022 -0800

    rcutorture: make use of the helper function kthread_run_on_cpu()
    
    Replace kthread_create_on_node/kthread_bind/wake_up_process() with
    kthread_run_on_cpu() to simplify the code.
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-5-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 64ed3a049e3e81b801e7c5bb052416152443f585
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:02:59 2022 -0800

    ring-buffer: make use of the helper function kthread_run_on_cpu()
    
    Replace kthread_create/kthread_bind/wake_up_process() with
    kthread_run_on_cpu() to simplify the code.
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-4-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit e0850113937b843c69b50b5d9087978ae4254be7
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:02:55 2022 -0800

    RDMA/siw: make use of the helper function kthread_run_on_cpu()
    
    Replace kthread_create/kthread_bind/wake_up_process() with
    kthread_run_on_cpu() to simplify the code.
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-3-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 800977f6f32e452cba6b04ef21d2f5383ca29209
Author: Cai Huoqing <caihuoqing@baidu.com>
Date:   Fri Jan 14 14:02:52 2022 -0800

    kthread: add the helper function kthread_run_on_cpu()
    
    Add a new helper function kthread_run_on_cpu(), which includes
    kthread_create_on_cpu/wake_up_process().
    
    In some cases, use kthread_run_on_cpu() directly instead of
    kthread_create_on_node/kthread_bind/wake_up_process() or
    kthread_create_on_cpu/wake_up_process() or
    kthreadd_create/kthread_bind/wake_up_process() to simplify the code.
    
    [akpm@linux-foundation.org: export kthread_create_on_cpu to modules]
    
    Link: https://lkml.kernel.org/r/20211022025711.3673-2-caihuoqing@baidu.com
    Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Bernard Metzler <bmt@zurich.ibm.com>
    Cc: Cai Huoqing <caihuoqing@baidu.com>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: Davidlohr Bueso <dave@stgolabs.net>
    Cc: Doug Ledford <dledford@redhat.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jason Gunthorpe <jgg@ziepe.ca>
    Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
    Cc: Josh Triplett <josh@joshtriplett.org>
    Cc: Lai Jiangshan <jiangshanlai@gmail.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: "Paul E . McKenney" <paulmck@kernel.org>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 3cdb8e995ee2e393b66d2abe156b90475009ec41
Author: Julia Lawall <Julia.Lawall@inria.fr>
Date:   Sun Dec 26 11:36:48 2021 +0100

    drop fen.cocci
    
    This semantic patch does not take into account the fact that of_node_put
    can be safely applied to NULL.  Thus it gives only false positives.
    Drop it.
    
    Reported-by: Qing Wang <wangqing@vivo.com>
    Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

commit 92b2dadaa624d69465dd94ce3d0f30fc2f70170e
Author: Julia Lawall <Julia.Lawall@inria.fr>
Date:   Sat Nov 27 19:10:43 2021 +0100

    scripts/coccinelle: drop bugon.cocci
    
    The BUG_ON script was never safe, in that it was not able to check
    whether the condition was side-effecting.  At this point, BUG_ON
    should be well known, so it has probably outlived its usefuless.
    
    Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
    Suggested-by: Matthew Wilcox <willy@infradead.org>

commit 6fed105a5640e148032ad37208be280ce8cb6915
Author: Julia Lawall <Julia.Lawall@inria.fr>
Date:   Sat Nov 27 19:09:26 2021 +0100

    MAINTAINERS: remove Gilles Muller
    
    Gilles Muller passed away on November 17, 2021.  We would like
    to thank him for his continued support for the development of
    Coccinelle.
    
    Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>

commit a33f5c380c4bd3fa5278d690421b72052456d9fe
Merge: 112450df61b73 4a9bca86806fa
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Jan 15 07:47:40 2022 +0200

    Merge tag 'xfs-5.17-merge-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs fixes from Darrick Wong:
     "These are the last few obvious fixes that I found while stress testing
      online fsck for XFS prior to initiating a design review of the whole
      giant machinery.
    
       - Fix a minor locking inconsistency in readdir
    
       - Fix incorrect fs feature bit validation for secondary superblocks"
    
    * tag 'xfs-5.17-merge-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: fix online fsck handling of v5 feature bits on secondary supers
      xfs: take the ILOCK when readdir inspects directory mapping data

commit 9d6d7f1cb67cdee15f1a0e85aacfb924e0e02435
Author: Eric Dumazet <edumazet@google.com>
Date:   Fri Jan 14 08:43:28 2022 -0800

    af_unix: annote lockless accesses to unix_tot_inflight & gc_in_progress
    
    wait_for_unix_gc() reads unix_tot_inflight & gc_in_progress
    without synchronization.
    
    Adds READ_ONCE()/WRITE_ONCE() and their associated comments
    to better document the intent.
    
    BUG: KCSAN: data-race in unix_inflight / wait_for_unix_gc
    
    write to 0xffffffff86e2b7c0 of 4 bytes by task 9380 on cpu 0:
     unix_inflight+0x1e8/0x260 net/unix/scm.c:63
     unix_attach_fds+0x10c/0x1e0 net/unix/scm.c:121
     unix_scm_to_skb net/unix/af_unix.c:1674 [inline]
     unix_dgram_sendmsg+0x679/0x16b0 net/unix/af_unix.c:1817
     unix_seqpacket_sendmsg+0xcc/0x110 net/unix/af_unix.c:2258
     sock_sendmsg_nosec net/socket.c:704 [inline]
     sock_sendmsg net/socket.c:724 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2409
     ___sys_sendmsg net/socket.c:2463 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2549
     __do_sys_sendmmsg net/socket.c:2578 [inline]
     __se_sys_sendmmsg net/socket.c:2575 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2575
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    read to 0xffffffff86e2b7c0 of 4 bytes by task 9375 on cpu 1:
     wait_for_unix_gc+0x24/0x160 net/unix/garbage.c:196
     unix_dgram_sendmsg+0x8e/0x16b0 net/unix/af_unix.c:1772
     unix_seqpacket_sendmsg+0xcc/0x110 net/unix/af_unix.c:2258
     sock_sendmsg_nosec net/socket.c:704 [inline]
     sock_sendmsg net/socket.c:724 [inline]
     ____sys_sendmsg+0x39a/0x510 net/socket.c:2409
     ___sys_sendmsg net/socket.c:2463 [inline]
     __sys_sendmmsg+0x267/0x4c0 net/socket.c:2549
     __do_sys_sendmmsg net/socket.c:2578 [inline]
     __se_sys_sendmmsg net/socket.c:2575 [inline]
     __x64_sys_sendmmsg+0x53/0x60 net/socket.c:2575
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    value changed: 0x00000002 -> 0x00000004
    
    Reported by Kernel Concurrency Sanitizer on:
    CPU: 1 PID: 9375 Comm: syz-executor.1 Not tainted 5.16.0-rc7-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    
    Fixes: 9915672d4127 ("af_unix: limit unix_tot_inflight")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220114164328.2038499-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 252745240ba0ae774d2f80c5e185ed59fbc4fb41
Author: Christophe Leroy <christophe.leroy@csgroup.eu>
Date:   Fri Jan 14 11:26:25 2022 +0000

    powerpc/audit: Fix syscall_get_arch()
    
    Commit 770cec16cdc9 ("powerpc/audit: Simplify syscall_get_arch()")
    and commit 898a1ef06ad4 ("powerpc/audit: Avoid unneccessary #ifdef
    in syscall_get_arguments()")
    replaced test_tsk_thread_flag(task, TIF_32BIT)) by is_32bit_task().
    
    But is_32bit_task() applies on current task while be want the test
    done on task 'task'
    
    So add a new macro is_tsk_32bit_task() to check any task.
    
    Fixes: 770cec16cdc9 ("powerpc/audit: Simplify syscall_get_arch()")
    Fixes: 898a1ef06ad4 ("powerpc/audit: Avoid unneccessary #ifdef in syscall_get_arguments()")
    Cc: stable@vger.kernel.org
    Reported-by: Dmitry V. Levin <ldv@altlinux.org>
    Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/c55cddb8f65713bf5859ed675d75a50cb37d5995.1642159570.git.christophe.leroy@csgroup.eu

commit 3f5f766d5f7f95a69a630da3544a1a0cee1cdddf
Author: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Date:   Thu Jan 6 17:15:12 2022 +0530

    powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06
    
    Johan reported the below crash with test_bpf on ppc64 e5500:
    
      test_bpf: #296 ALU_END_FROM_LE 64: 0x0123456789abcdef -> 0x67452301 jited:1
      Oops: Exception in kernel mode, sig: 4 [#1]
      BE PAGE_SIZE=4K SMP NR_CPUS=24 QEMU e500
      Modules linked in: test_bpf(+)
      CPU: 0 PID: 76 Comm: insmod Not tainted 5.14.0-03771-g98c2059e008a-dirty #1
      NIP:  8000000000061c3c LR: 80000000006dea64 CTR: 8000000000061c18
      REGS: c0000000032d3420 TRAP: 0700   Not tainted (5.14.0-03771-g98c2059e008a-dirty)
      MSR:  0000000080089000 <EE,ME>  CR: 88002822  XER: 20000000 IRQMASK: 0
      <...>
      NIP [8000000000061c3c] 0x8000000000061c3c
      LR [80000000006dea64] .__run_one+0x104/0x17c [test_bpf]
      Call Trace:
       .__run_one+0x60/0x17c [test_bpf] (unreliable)
       .test_bpf_init+0x6a8/0xdc8 [test_bpf]
       .do_one_initcall+0x6c/0x28c
       .do_init_module+0x68/0x28c
       .load_module+0x2460/0x2abc
       .__do_sys_init_module+0x120/0x18c
       .system_call_exception+0x110/0x1b8
       system_call_common+0xf0/0x210
      --- interrupt: c00 at 0x101d0acc
      <...>
      ---[ end trace 47b2bf19090bb3d0 ]---
    
      Illegal instruction
    
    The illegal instruction turned out to be 'ldbrx' emitted for
    BPF_FROM_[L|B]E, which was only introduced in ISA v2.06. Guard use of
    the same and implement an alternative approach for older processors.
    
    Fixes: 156d0e290e969c ("powerpc/ebpf/jit: Implement JIT compiler for extended BPF")
    Reported-by: Johan Almbladh <johan.almbladh@anyfinetworks.com>
    Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Tested-by: Johan Almbladh <johan.almbladh@anyfinetworks.com>
    Acked-by: Johan Almbladh <johan.almbladh@anyfinetworks.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/d1e51c6fdf572062cf3009a751c3406bda01b832.1641468127.git.naveen.n.rao@linux.vnet.ibm.com

commit 88a71086c48ae98e93c0208044827621e9717f7e
Author: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Date:   Thu Jan 6 17:15:08 2022 +0530

    tools/bpf: Rename 'struct event' to avoid naming conflict
    
    On ppc64le, trying to build bpf seltests throws the below warning:
      In file included from runqslower.bpf.c:5:
      ./runqslower.h:7:8: error: redefinition of 'event'
      struct event {
             ^
      /home/naveen/linux/tools/testing/selftests/bpf/tools/build/runqslower/vmlinux.h:156602:8:
      note: previous definition is here
      struct event {
             ^
    
    This happens since 'struct event' is defined in
    drivers/net/ethernet/alteon/acenic.h . Rename the one in runqslower to a
    more appropriate 'runq_event' to avoid the naming conflict.
    
    Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Acked-by: Daniel Borkmann <daniel@iogearbox.net>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/c13cb3767d26257ca4387b8296b632b433a58db6.1641468127.git.naveen.n.rao@linux.vnet.ibm.com

commit f9320c49993ca3c0ec0f9a7026b313735306bb8b
Author: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Date:   Thu Jan 6 17:15:07 2022 +0530

    powerpc/bpf: Update ldimm64 instructions during extra pass
    
    These instructions are updated after the initial JIT, so redo codegen
    during the extra pass. Rename bpf_jit_fixup_subprog_calls() to clarify
    that this is more than just subprog calls.
    
    Fixes: 69c087ba6225b5 ("bpf: Add bpf_for_each_map_elem() helper")
    Cc: stable@vger.kernel.org # v5.15
    Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Tested-by: Jiri Olsa <jolsa@redhat.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/7cc162af77ba918eb3ecd26ec9e7824bc44b1fae.1641468127.git.naveen.n.rao@linux.vnet.ibm.com

commit fab07611fb2e6a15fac05c4583045ca5582fd826
Author: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Date:   Thu Jan 6 17:15:06 2022 +0530

    powerpc32/bpf: Fix codegen for bpf-to-bpf calls
    
    Pad instructions emitted for BPF_CALL so that the number of instructions
    generated does not change for different function addresses. This is
    especially important for calls to other bpf functions, whose address
    will only be known during extra pass.
    
    Fixes: 51c66ad849a703 ("powerpc/bpf: Implement extended BPF on PPC32")
    Cc: stable@vger.kernel.org # v5.13+
    Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/52d8fe51f7620a6f27f377791564d79d75463576.1641468127.git.naveen.n.rao@linux.vnet.ibm.com

commit b992f01e66150fc5e90be4a96f5eb8e634c8249e
Author: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Date:   Thu Jan 6 17:15:05 2022 +0530

    bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
    
    task_pt_regs() can return NULL on powerpc for kernel threads. This is
    then used in __bpf_get_stack() to check for user mode, resulting in a
    kernel oops. Guard against this by checking return value of
    task_pt_regs() before trying to obtain the call chain.
    
    Fixes: fa28dcb82a38f8 ("bpf: Introduce helper bpf_get_task_stack()")
    Cc: stable@vger.kernel.org # v5.9+
    Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
    Acked-by: Daniel Borkmann <daniel@iogearbox.net>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Link: https://lore.kernel.org/r/d5ef83c361cc255494afd15ff1b4fb02a36e1dcf.1641468127.git.naveen.n.rao@linux.vnet.ibm.com

commit b03fc43e73877e180c1803a33aea3e7396642367
Author: Eli Cohen <elic@nvidia.com>
Date:   Tue Jan 11 20:34:00 2022 +0200

    vdpa/mlx5: Fix tracking of current number of VQs
    
    Modify the code such that ndev->cur_num_vqs better reflects the actual
    number of data virtqueues. The value can be accurately realized after
    features have been negotiated.
    
    This is to prevent possible failures when modifying the RQT object if
    the cur_num_vqs bears invalid value.
    
    No issue was actually encountered but this also makes the code more
    readable.
    
    Fixes: c5a5cd3d3217 ("vdpa/mlx5: Support configuring max data virtqueue")
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220111183400.38418-5-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit f8ae3a489b21b05c39a0a1a7734f2a0188852177
Author: Eli Cohen <elic@nvidia.com>
Date:   Tue Jan 11 20:33:59 2022 +0200

    vdpa/mlx5: Fix is_index_valid() to refer to features
    
    Make sure the decision whether an index received through a callback is
    valid or not consults the negotiated features.
    
    The motivation for this was due to a case encountered where I shut down
    the VM. After the reset operation was called features were already
    clear, I got get_vq_state() call which caused out array bounds
    access since is_index_valid() reported the index value.
    
    So this is more of not hit a bug since the call shouldn't have been made
    first place.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220111183400.38418-4-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 680ab9d69a04cfd9f3f5fedaacbc1974b2959121
Author: Eli Cohen <elic@nvidia.com>
Date:   Tue Jan 11 20:33:58 2022 +0200

    vdpa: Protect vdpa reset with cf_mutex
    
    Call reset using the wrapper function vdpa_reset() to make sure the
    operation is serialized with cf_mutex.
    
    This comes to protect from the following possible scenario:
    
    vhost_vdpa_set_status() could call the reset op. Since the call is not
    protected by cf_mutex, a netlink thread calling vdpa_dev_config_fill
    could get passed the VIRTIO_CONFIG_S_FEATURES_OK check in
    vdpa_dev_config_fill() and end up reporting wrong features.
    
    Fixes: 5f6e85953d8f ("vdpa: Read device configuration only if FEATURES_OK")
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220111183400.38418-3-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit f6d955d80830b6e6f6a170be68cc3628f36365dd
Author: Eli Cohen <elic@nvidia.com>
Date:   Tue Jan 11 20:33:57 2022 +0200

    vdpa: Avoid taking cf_mutex lock on get status
    
    Avoid the wrapper holding cf_mutex since it is not protecting anything.
    To avoid confusion and unnecessary overhead incurred by it, remove.
    
    Fixes: f489f27bc0ab ("vdpa: Sync calls set/get config/status with cf_mutex")
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220111183400.38418-2-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit b2ce6197c9c9be0ecc2a636f3b2f35886ce09a98
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:46 2022 +0200

    vdpa/vdpa_sim_net: Report max device capabilities
    
    Configure max supported virtqueues features on the management device.
    This info can be retrieved using:
    
    $ vdpa mgmtdev show
    vdpasim_net:
      supported_classes net
      max_supported_vqs 2
      dev_features MAC ANY_LAYOUT VERSION_1 ACCESS_PLATFORM
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-15-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 47a1401ac95f95936148b813843ee51d516921ea
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:45 2022 +0200

    vdpa: Use BIT_ULL for bit operations
    
    All masks in this file are 64 bits. Change BIT to BIT_ULL.
    
    Other occurences use (1 << val) which yields a 32 bit value. Change them
    to use BIT_ULL too.
    
    Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-14-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit cbe777e98b3a420a6d66b7ce7780334c48eccc88
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:44 2022 +0200

    vdpa/vdpa_sim: Configure max supported virtqueues
    
    Configure max supported virtqueues on the management device.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-13-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 79de65edf8891725616f4992cee5d5963900f07a
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:43 2022 +0200

    vdpa/mlx5: Report max device capabilities
    
    Configure max supported virtqueues and features on the management
    device.
    This info can be retrieved using:
    
    $ vdpa mgmtdev show
    auxiliary/mlx5_core.sf.1:
      supported_classes net
      max_supported_vqs 257
      dev_features CSUM GUEST_CSUM MTU HOST_TSO4 HOST_TSO6 STATUS CTRL_VQ MQ \
                   CTRL_MAC_ADDR VERSION_1 ACCESS_PLATFORM
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-12-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>

commit cd2629f6df1cab5b3df34705ae7f3bde6147fce3
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:42 2022 +0200

    vdpa: Support reporting max device capabilities
    
    Add max_supported_vqs and supported_features fields to struct
    vdpa_mgmt_dev. Upstream drivers need to feel these values according to
    the device capabilities.
    
    These values are reported back in a netlink message when showing management
    devices.
    
    Examples:
    
    $ auxiliary/mlx5_core.sf.1:
      supported_classes net
      max_supported_vqs 257
      dev_features CSUM GUEST_CSUM MTU HOST_TSO4 HOST_TSO6 STATUS CTRL_VQ MQ \
                   CTRL_MAC_ADDR VERSION_1 ACCESS_PLATFORM
    
    $ vdpa -j mgmtdev show
    {"mgmtdev":{"auxiliary/mlx5_core.sf.1":{"supported_classes":["net"], \
      "max_supported_vqs":257,"dev_features":["CSUM","GUEST_CSUM","MTU", \
      "HOST_TSO4","HOST_TSO6","STATUS","CTRL_VQ","MQ","CTRL_MAC_ADDR", \
      "VERSION_1","ACCESS_PLATFORM"]}}}
    
    $ vdpa -jp mgmtdev show
    {
        "mgmtdev": {
            "auxiliary/mlx5_core.sf.1": {
                "supported_classes": [ "net" ],
                "max_supported_vqs": 257,
                "dev_features": ["CSUM","GUEST_CSUM","MTU","HOST_TSO4", \
                                 "HOST_TSO6","STATUS","CTRL_VQ","MQ", \
                                 "CTRL_MAC_ADDR","VERSION_1","ACCESS_PLATFORM"]
            }
        }
    }
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-11-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>

commit 37e07e705888e4c3502f204e9c6785c9c2d6d86a
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:41 2022 +0200

    vdpa/mlx5: Restore cur_num_vqs in case of failure in change_num_qps()
    
    Restore ndev->cur_num_vqs to the original value in case change_num_qps()
    fails.
    
    Fixes: 52893733f2c5 ("vdpa/mlx5: Add multiqueue support")
    Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-10-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 612f330ec56f12c0d099286c45f82d835845f136
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:40 2022 +0200

    vdpa: Add support for returning device configuration information
    
    Add netlink attribute to store the negotiated features. This can be used
    by userspace to get the current state of the vdpa instance.
    
    Examples:
    
    $ vdpa dev config show vdpa-a
    vdpa-a: mac 00:00:00:00:88:88 link up link_announce false max_vq_pairs 16 mtu 1500
      negotiated_features CSUM GUEST_CSUM MTU MAC HOST_TSO4 HOST_TSO6 STATUS \
      CTRL_VQ MQ CTRL_MAC_ADDR VERSION_1 ACCESS_PLATFORM
    
    $ vdpa -j dev config show vdpa-a
    {"config":{"vdpa-a":{"mac":"00:00:00:00:88:88","link ":"up","link_announce":false, \
     "max_vq_pairs":16,"mtu":1500,"negotiated_features":["CSUM","GUEST_CSUM","MTU","MAC", \
     "HOST_TSO4","HOST_TSO6","STATUS","CTRL_VQ","MQ","CTRL_MAC_ADDR","VERSION_1", \
     "ACCESS_PLATFORM"]}}}
    
    $ vdpa -jp dev config show vdpa-a
    {
        "config": {
            "vdpa-a": {
                "mac": "00:00:00:00:88:88",
                "link ": "up",
                "link_announce ": false,
                "max_vq_pairs": 16,
                "mtu": 1500,
                "negotiated_features": [
    "CSUM","GUEST_CSUM","MTU","MAC","HOST_TSO4","HOST_TSO6","STATUS","CTRL_VQ","MQ", \
    "CTRL_MAC_ADDR","VERSION_1","ACCESS_PLATFORM"
    ]
            }
        }
    }
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-9-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 75560522eaef2f7c7b2fec3c22e1254244f52372
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:39 2022 +0200

    vdpa/mlx5: Support configuring max data virtqueue
    
    Check whether the max number of data virtqueue pairs was provided when a
    adding a new device and verify the new value does not exceed device
    capabilities.
    
    In addition, change the arrays holding virtqueue and callback contexts
    to be dynamically allocated.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-8-elic@nvidia.com
    
    Includes fixup:
    
    vdpa/mlx5: fix error handling in mlx5_vdpa_dev_add()
    
    Clang build fails with
    mlx5_vnet.c:2574:6: error: variable 'mvdev' is used uninitialized whenever
      'if' condition is true
            if (!ndev->vqs || !ndev->event_cbs) {
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    mlx5_vnet.c:2660:14: note: uninitialized use occurs here
            put_device(&mvdev->vdev.dev);
                        ^~~~~
    This because mvdev is set after trying to allocate ndev->vqs,event_cbs.
    So move the allocation to after mvdev is set but before the arrays
    are used in init_mvqs()
    
    Signed-off-by: Tom Rix <trix@redhat.com>
    Link: https://lore.kernel.org/r/20220107211352.3940570-1-trix@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    
    Includes fixup:
    
    vdpa/mlx5: fix endian-ness for max vqs
    
    sparse warnings: (new ones prefixed by >>)
    >> drivers/vdpa/mlx5/net/mlx5_vnet.c:1247:23: sparse: sparse: cast to restricted __le16
    >> drivers/vdpa/mlx5/net/mlx5_vnet.c:1247:23: sparse: sparse: cast from restricted __virtio16
    
    > 1247                  num = le16_to_cpu(ndev->config.max_virtqueue_pairs);
    
    Address this using the appropriate wrapper.
    
    Cc: "Eli Cohen" <elic@nvidia.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Reviewed-by: Eli Cohen <elic@nvidia.com>

commit e3137056e6dedee205fccd06da031a285c6e34f5
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:38 2022 +0200

    vdpa/mlx5: Fix config_attr_mask assignment
    
    Fix VDPA_ATTR_DEV_NET_CFG_MACADDR assignment to be explicit 64 bit
    assignment.
    
    No issue was seen since the value is well below 64 bit max value.
    Nevertheless it needs to be fixed.
    
    Fixes: a007d940040c ("vdpa/mlx5: Support configuration of MAC")
    Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-7-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit aba21aff772b8622e08f07219069be793429a48f
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:37 2022 +0200

    vdpa: Allow to configure max data virtqueues
    
    Add netlink support to configure the max virtqueue pairs for a device.
    At least one pair is required. The maximum is dictated by the device.
    
    Example:
    $ vdpa dev add name vdpa-a mgmtdev auxiliary/mlx5_core.sf.1 max_vqp 4
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-6-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 30ef7a8ac8a07046b9ac9206d3a732a9f76b2e60
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:36 2022 +0200

    vdpa: Read device configuration only if FEATURES_OK
    
    Avoid reading device configuration during feature negotiation. Read
    device status and verify that VIRTIO_CONFIG_S_FEATURES_OK is set.
    
    Protect the entire operation, including configuration read with cf_mutex
    to ensure integrity of the results.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-5-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 73bc0dbb591baea322a7319c735e5f6c7dba9cfb
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:35 2022 +0200

    vdpa: Sync calls set/get config/status with cf_mutex
    
    Add wrappers to get/set status and protect these operations with
    cf_mutex to serialize these operations with respect to get/set config
    operations.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-4-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit a7f46ba42485394edf9836969e220878f4908465
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:34 2022 +0200

    vdpa/mlx5: Distribute RX virtqueues in RQT object
    
    Distribute the available rx virtqueues amongst the available RQT
    entries.
    
    RQTs require to have a power of two entries. When creating or modifying
    the RQT, use the lowest number of power of two entries that is not less
    than the number of rx virtqueues. Distribute them in the available
    entries such that some virtqueus may be referenced twice.
    
    This allows to configure any number of virtqueue pairs when multiqueue
    is used.
    
    Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-3-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit a64917bc2e9b1e0aa716b783c4ec879fdd280300
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Jan 5 13:46:33 2022 +0200

    vdpa: Provide interface to read driver features
    
    Provide an interface to read the negotiated features. This is needed
    when building the netlink message in vdpa_dev_net_config_fill().
    
    Also fix the implementation of vdpa_dev_net_config_fill() to use the
    negotiated features instead of the device features.
    
    To make APIs clearer, make the following name changes to struct
    vdpa_config_ops so they better describe their operations:
    
    get_features -> get_device_features
    set_features -> set_driver_features
    
    Finally, add get_driver_features to return the negotiated features and
    add implementation to all the upstream drivers.
    
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20220105114646.577224-2-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 870aaff92e959e29d40f9cfdb5ed06ba2fc2dae0
Author: Laura Abbott <labbott@kernel.org>
Date:   Thu Jan 6 08:09:25 2022 -0500

    vdpa: clean up get_config_size ret value handling
    
    The return type of get_config_size is size_t so it makes
    sense to change the type of the variable holding its result.
    
    That said, this already got taken care of (differently, and arguably
    not as well) by commit 3ed21c1451a1 ("vdpa: check that offsets are
    within bounds").
    
    The added 'c->off > size' test in that commit will be done as an
    unsigned comparison on 32-bit (safe due to not being signed).
    
    On a 64-bit platform, it will be done as a signed comparison, but in
    that case the comparison will be done in 64-bit, and 'c->off' being an
    u32 it will be valid thanks to the extended range (ie both values will
    be positive in 64 bits).
    
    So this was a real bug, but it was already addressed and marked for stable.
    
    Signed-off-by: Laura Abbott <labbott@kernel.org>
    Reported-by: Luo Likang <luolikang@nsfocus.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 1861ba626ae9b98136f3e504208cdef6b29cd3ec
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Thu Jan 6 07:57:46 2022 -0500

    virtio_ring: mark ring unused on error
    
    A recently added error path does not mark ring unused when exiting on
    OOM, which will lead to BUG on the next entry in debug builds.
    
    TODO: refactor code so we have START_USE and END_USE in the same function.
    
    Fixes: fc6d70f40b3d ("virtio_ring: check desc == NULL when using indirect with packed")
    Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>
    Cc: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 080063920777af65105e5953e2851e036376e3ea
Author: Xianting Tian <xianting.tian@linux.alibaba.com>
Date:   Tue Dec 28 11:09:24 2021 +0800

    vhost/test: fix memory leak of vhost virtqueues
    
    We need free the vqs in .release(), which are allocated in .open().
    
    Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
    Link: https://lore.kernel.org/r/20211228030924.3468439-1-xianting.tian@linux.alibaba.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 97143b70aa847f2b0a1f959dde126b76ff7b5376
Author: Eli Cohen <elic@nvidia.com>
Date:   Thu Dec 30 16:20:24 2021 +0200

    vdpa/mlx5: Fix wrong configuration of virtio_version_1_0
    
    Remove overriding of virtio_version_1_0 which forced the virtqueue
    object to version 1.
    
    Fixes: 1a86b377aa21 ("vdpa/mlx5: Add VDPA driver for supported mlx5 devices")
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20211230142024.142979-1-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Parav Pandit <parav@nvidia.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>

commit 49814ce9e21a8b6d6158b2e502fe6bacef4d99b6
Author: Peng Hao <flyingpenghao@gmail.com>
Date:   Wed Dec 22 19:20:14 2021 +0800

    virtio/virtio_pci_legacy_dev: ensure the correct return value
    
    When pci_iomap return NULL, the return value is zero.
    
    Signed-off-by: Peng Hao <flyingpeng@tencent.com>
    Link: https://lore.kernel.org/r/20211222112014.87394-1-flyingpeng@tencent.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit cf4a4493ff70874f8af26d75d4346c591c298e89
Author: Peng Hao <flyingpenghao@gmail.com>
Date:   Wed Dec 22 09:12:25 2021 +0800

    virtio/virtio_mem: handle a possible NULL as a memcpy parameter
    
    There is a check for vm->sbm.sb_states before, and it should check
    it here as well.
    
    Signed-off-by: Peng Hao <flyingpeng@tencent.com>
    Link: https://lore.kernel.org/r/20211222011225.40573-1-flyingpeng@tencent.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Fixes: 5f1f79bbc9e2 ("virtio-mem: Paravirtualized memory hotplug")
    Cc: stable@vger.kernel.org # v5.8+

commit 2b68224ec61bb66aa2a24ad099b6af65138fa888
Author: Dapeng Mi <dapeng1.mi@intel.com>
Date:   Fri Dec 10 15:35:46 2021 +0800

    virtio: fix a typo in function "vp_modern_remove" comments.
    
    Function name "vp_modern_remove" in comments is written to
    "vp_modern_probe" incorrectly. Change it.
    
    Signed-off-by: Dapeng Mi <dapeng1.mi@intel.com>
    Link: https://lore.kernel.org/r/20211210073546.700783-1-dapeng1.mi@intel.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

commit 6017599bb25c20b7a68cbb8e7d534bdc1c36b5e4
Author: 王贇 <yun.wang@linux.alibaba.com>
Date:   Thu Dec 9 11:29:25 2021 +0800

    virtio-pci: fix the confusing error message
    
    The error message on the failure of pfn check should tell
    virtio-pci rather than virtio-mmio, just fix it.
    
    Signed-off-by: Michael Wang <yun.wang@linux.alibaba.com>
    Suggested-by: Michael S. Tsirkin <mst@redhat.com>
    Link: https://lore.kernel.org/r/ae5e154e-ac59-f0fa-a7c7-091a2201f581@linux.alibaba.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 9f8b4ae2ac7dc5ff6e5dfa723c1ef2bad80a8c68
Author: Johan Hovold <johan@kernel.org>
Date:   Wed Dec 1 14:25:28 2021 +0100

    firmware: qemu_fw_cfg: remove sysfs entries explicitly
    
    Explicitly remove the file entries from sysfs before dropping the final
    reference for symmetry reasons and for consistency with the rest of the
    driver.
    
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Link: https://lore.kernel.org/r/20211201132528.30025-5-johan@kernel.org
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 1b656e9aad7f4886ed466094d1dc5ee4dd900d20
Author: Johan Hovold <johan@kernel.org>
Date:   Wed Dec 1 14:25:27 2021 +0100

    firmware: qemu_fw_cfg: fix sysfs information leak
    
    Make sure to always NUL-terminate file names retrieved from the firmware
    to avoid accessing data beyond the entry slab buffer and exposing it
    through sysfs in case the firmware data is corrupt.
    
    Fixes: 75f3e8e47f38 ("firmware: introduce sysfs driver for QEMU's fw_cfg device")
    Cc: stable@vger.kernel.org      # 4.6
    Cc: Gabriel Somlo <somlo@cmu.edu>
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Link: https://lore.kernel.org/r/20211201132528.30025-4-johan@kernel.org
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 6004e351da50565fb561be85d45151dc9c370023
Author: Johan Hovold <johan@kernel.org>
Date:   Wed Dec 1 14:25:26 2021 +0100

    firmware: qemu_fw_cfg: fix kobject leak in probe error path
    
    An initialised kobject must be freed using kobject_put() to avoid
    leaking associated resources (e.g. the object name).
    
    Commit fe3c60684377 ("firmware: Fix a reference count leak.") "fixed"
    the leak in the first error path of the file registration helper but
    left the second one unchanged. This "fix" would however result in a NULL
    pointer dereference due to the release function also removing the never
    added entry from the fw_cfg_entry_cache list. This has now been
    addressed.
    
    Fix the remaining kobject leak by restoring the common error path and
    adding the missing kobject_put().
    
    Fixes: 75f3e8e47f38 ("firmware: introduce sysfs driver for QEMU's fw_cfg device")
    Cc: stable@vger.kernel.org      # 4.6
    Cc: Gabriel Somlo <somlo@cmu.edu>
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Link: https://lore.kernel.org/r/20211201132528.30025-3-johan@kernel.org
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit d3e305592d69e21e36b76d24ca3c01971a2d09be
Author: Johan Hovold <johan@kernel.org>
Date:   Wed Dec 1 14:25:25 2021 +0100

    firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
    
    Commit fe3c60684377 ("firmware: Fix a reference count leak.") "fixed"
    a kobject leak in the file registration helper by properly calling
    kobject_put() for the entry in case registration of the object fails
    (e.g. due to a name collision).
    
    This would however result in a NULL pointer dereference when the
    release function tries to remove the never added entry from the
    fw_cfg_entry_cache list.
    
    Fix this by moving the list-removal out of the release function.
    
    Note that the offending commit was one of the benign looking umn.edu
    fixes which was reviewed but not reverted. [1][2]
    
    [1] https://lore.kernel.org/r/202105051005.49BFABCE@keescook
    [2] https://lore.kernel.org/all/YIg7ZOZvS3a8LjSv@kroah.com
    
    Fixes: fe3c60684377 ("firmware: Fix a reference count leak.")
    Cc: stable@vger.kernel.org      # 5.8
    Cc: Qiushi Wu <wu000273@umn.edu>
    Cc: Kees Cook <keescook@chromium.org>
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Link: https://lore.kernel.org/r/20211201132528.30025-2-johan@kernel.org
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 28cc408be72cebb0f3fcc37bc74ab3196d4de726
Author: Eugenio Pérez <eperezma@redhat.com>
Date:   Thu Nov 4 20:52:48 2021 +0100

    vdpa: Mark vdpa_config_ops.get_vq_notification as optional
    
    Since vhost_vdpa_mmap checks for its existence before calling it.
    
    Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
    Link: https://lore.kernel.org/r/20211104195248.2088904-1-eperezma@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

commit 23118b09e6e11a03cb40a86875d5d342257ae1ec
Author: Eugenio Pérez <eperezma@redhat.com>
Date:   Thu Nov 4 20:58:33 2021 +0100

    vdpa: Avoid duplicate call to vp_vdpa get_status
    
    It has no sense to call get_status twice, since we already have a
    variable for that.
    
    Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
    Link: https://lore.kernel.org/r/20211104195833.2089796-1-eperezma@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>

commit 10aa250b2f7d87d0921c5e991fd49e607050d486
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Nov 7 17:14:56 2021 +0100

    eni_vdpa: Simplify 'eni_vdpa_probe()'
    
    When 'pcim_enable_device()' is used, some resources become automagically
    managed.
    There is no need to call 'pci_free_irq_vectors()' when the driver is
    removed. The same will already be done by 'pcim_release()'.
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/02045bdcbbb25f79bae4827f66029cfcddc90381.1636301587.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 60af39c1f4cc92cc2785ef745c0c97558134d539
Author: Eli Cohen <elic@nvidia.com>
Date:   Wed Nov 24 19:09:49 2021 +0200

    net/mlx5_vdpa: Offer VIRTIO_NET_F_MTU when setting MTU
    
    Make sure to offer VIRTIO_NET_F_MTU since we configure the MTU based on
    what was queried from the device.
    
    This allows the virtio driver to allocate large enough buffers based on
    the reported MTU.
    
    Signed-off-by: Eli Cohen <elic@nvidia.com>
    Link: https://lore.kernel.org/r/20211124170949.51725-1-elic@nvidia.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Reviewed-by: Si-Wei Liu <si-wei.liu@oracle.com>

commit 57c5a5b304b0d3798b2d3dc75bd6c960d78ee8ff
Author: David Hildenbrand <david@redhat.com>
Date:   Fri Nov 26 14:42:09 2021 +0100

    virtio-mem: prepare fake page onlining code for granularity smaller than MAX_ORDER - 1
    
    Let's prepare our fake page onlining code for subblock size smaller than
    MAX_ORDER - 1: we might get called for ranges not covering properly
    aligned MAX_ORDER - 1 pages. We have to detect the order to use
    dynamically.
    
    Signed-off-by: David Hildenbrand <david@redhat.com>
    Link: https://lore.kernel.org/r/20211126134209.17332-3-david@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Zi Yan <ziy@nvidia.com>
    Reviewed-by: Eric Ren <renzhengeek@gmail.com>

commit 6639032acc085775452a2c92fdb8a6f601c9c075
Author: David Hildenbrand <david@redhat.com>
Date:   Fri Nov 26 14:42:08 2021 +0100

    virtio-mem: prepare page onlining code for granularity smaller than MAX_ORDER - 1
    
    Let's prepare our page onlining code for subblock size smaller than
    MAX_ORDER - 1: we'll get called for a MAX_ORDER - 1 page but might have
    some subblocks in the range plugged and some unplugged. In that case,
    fallback to subblock granularity to properly only expose the plugged
    parts to the buddy.
    
    Signed-off-by: David Hildenbrand <david@redhat.com>
    Link: https://lore.kernel.org/r/20211126134209.17332-2-david@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Reviewed-by: Zi Yan <ziy@nvidia.com>
    Reviewed-by: Eric Ren <renzhengeek@gmail.com>

commit 539fec78edb4e084e7c532affc56cc42d4ceea4b
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Fri Nov 26 17:47:53 2021 +0100

    vdpa: add driver_override support
    
    `driver_override` allows to control which of the vDPA bus drivers
    binds to a vDPA device.
    
    If `driver_override` is not set, the previous behaviour is followed:
    devices use the first vDPA bus driver loaded (unless auto binding
    is disabled).
    
    Tested on Fedora 34 with driverctl(8):
      $ modprobe virtio-vdpa
      $ modprobe vhost-vdpa
      $ modprobe vdpa-sim-net
    
      $ vdpa dev add mgmtdev vdpasim_net name dev1
    
      # dev1 is attached to the first vDPA bus driver loaded
      $ driverctl -b vdpa list-devices
        dev1 virtio_vdpa
    
      $ driverctl -b vdpa set-override dev1 vhost_vdpa
    
      $ driverctl -b vdpa list-devices
        dev1 vhost_vdpa [*]
    
      Note: driverctl(8) integrates with udev so the binding is
      preserved.
    
    Suggested-by: Jason Wang <jasowang@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Link: https://lore.kernel.org/r/20211126164753.181829-3-sgarzare@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 9c25cdeb5f3ca9ef0d683ee8c29b7cb61a174165
Author: Stefano Garzarella <sgarzare@redhat.com>
Date:   Fri Nov 26 17:47:52 2021 +0100

    docs: document sysfs ABI for vDPA bus
    
    Add missing documentation of sysfs ABI for vDPA bus in
    the new Documentation/ABI/testing/sysfs-bus-vdpa file.
    
    Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
    Link: https://lore.kernel.org/r/20211126164753.181829-2-sgarzare@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Acked-by: Jason Wang <jasowang@redhat.com>

commit 0f420c383a2bb414ebccedf9289b5b815f1295fe
Author: Zhu Lingshan <lingshan.zhu@intel.com>
Date:   Wed Dec 1 16:12:55 2021 +0800

    ifcvf/vDPA: fix misuse virtio-net device config size for blk dev
    
    This commit fixes a misuse of virtio-net device config size issue
    for virtio-block devices.
    
    A new member config_size in struct ifcvf_hw is introduced and would
    be initialized through vdpa_dev_add() to record correct device
    config size.
    
    To be more generic, rename ifcvf_hw.net_config to ifcvf_hw.dev_config,
    the helpers ifcvf_read/write_net_config() to ifcvf_read/write_dev_config()
    
    Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
    Reported-and-suggested-by: Stefano Garzarella <sgarzare@redhat.com>
    Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
    Fixes: 6ad31d162a4e ("vDPA/ifcvf: enable Intel C5000X-PL virtio-block for vDPA")
    Cc: <stable@vger.kernel.org>
    Link: https://lore.kernel.org/r/20211201081255.60187-1-lingshan.zhu@intel.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit b4d80c8dda229c830f0ba38c103e5263c2a7bc64
Author: Guanjun <guanjun@linux.alibaba.com>
Date:   Mon Dec 6 16:48:18 2021 +0800

    vduse: moving kvfree into caller
    
    This free action should be moved into caller 'vduse_ioctl' in
    concert with the allocation.
    
    No functional change.
    
    Signed-off-by: Guanjun <guanjun@linux.alibaba.com>
    Link: https://lore.kernel.org/r/1638780498-55571-1-git-send-email-guanjun@linux.alibaba.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit 2076207128948b766ef1fe344e0444fc9271a847
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Thu Nov 25 13:00:17 2021 -0500

    hwrng: virtio - unregister device before reset
    
    unregister after reset is clearly wrong - device
    can be used while it's reset. There's an attempt to
    protect against that using hwrng_removed but it
    seems racy since access can be in progress
    when the flag is set.
    
    Just unregister, then reset seems simpler and cleaner.
    NB: we might be able to drop hwrng_removed in a follow-up patch.
    
    Signed-off-by: Laurent Vivier <lvivier@redhat.com>
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit d9679d0013a66849f23057978f92e76b255c50aa
Author: Michael S. Tsirkin <mst@redhat.com>
Date:   Wed Oct 13 06:55:44 2021 -0400

    virtio: wrap config->reset calls
    
    This will enable cleanups down the road.
    The idea is to disable cbs, then add "flush_queued_cbs" callback
    as a parameter, this way drivers can flush any work
    queued after callbacks have been disabled.
    
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
    Link: https://lore.kernel.org/r/20211013105226.20225-1-mst@redhat.com
    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

commit c4849f88164b13dd141885e28210f599741b304b
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Fri Jan 7 10:44:17 2022 -0600

    drm/amd/display: Revert W/A for hard hangs on DCN20/DCN21
    
    The WA from commit 2a50edbf10c8 ("drm/amd/display: Apply w/a for hard hang
    on HPD") and commit 1bd3bc745e7f ("drm/amd/display: Extend w/a for hard
    hang on HPD to dcn20") causes a regression in s0ix where the system will
    fail to resume properly on many laptops.  Pull the workarounds out to
    avoid that s0ix regression in the common case.  This HPD hang happens with
    an external device in special circumstances and a new W/A will need to be
    developed for this in the future.
    
    Cc: stable@vger.kernel.org
    Cc: Qingqing Zhuo <qingqing.zhuo@amd.com>
    Reported-by: Scott Bruce <smbruce@gmail.com>
    Reported-by: Chris Hixon <linux-kernel-bugs@hixontech.com>
    Reported-by: spasswolf@web.de
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215436
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1821
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1852
    Fixes: 2a50edbf10c8 ("drm/amd/display: Apply w/a for hard hang on HPD")
    Fixes: 1bd3bc745e7f ("drm/amd/display: Extend w/a for hard hang on HPD to dcn20")
    Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit d82ce3cd30aa28db3e94ffc36ebf0af2ff12801d
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Fri Jan 14 09:59:29 2022 -0500

    drm/amdgpu: drop flags check for CHIP_IP_DISCOVERY
    
    Support for IP based discovery is in place now so this
    check is no longer required.
    
    Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 3993a799fc971bc9b918bd969aa55864447b5dde
Author: Lukas Fink <lukas.fink1@gmail.com>
Date:   Fri Jan 14 07:51:41 2022 +0100

    drm/amdgpu: Fix rejecting Tahiti GPUs
    
    eb4fd29afd4a ("drm/amdgpu: bind to any 0x1002 PCI diplay class device") added
    generic bindings to amdgpu so that that it binds to all display class devices
    with VID 0x1002 and then rejects those in amdgpu_pci_probe.
    
    Unfortunately it reuses a driver_data value of 0 to detect those new bindings,
    which is already used to denote CHIP_TAHITI ASICs.
    
    The driver_data value given to those new bindings was changed in
    dd0761fd24ea1 ("drm/amdgpu: set CHIP_IP_DISCOVERY as the asic type by default")
    to CHIP_IP_DISCOVERY (=36), but it seems that the check in amdgpu_pci_probe
    was forgotten to be changed. Therefore, it still rejects Tahiti GPUs.
    
    Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1860
    Fixes: eb4fd29afd4a ("drm/amdgpu: bind to any 0x1002 PCI diplay class device")
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Lukas Fink <lukas.fink1@gmail.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit e8309d50e97851ff135c4e33325d37b032666b94
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Wed Jan 12 22:38:51 2022 -0500

    drm/amdgpu: don't do resets on APUs which don't support it
    
    It can cause a hang.  This is normally not enabled for GPU
    hangs on these asics, but was recently enabled for handling
    aborted suspends.  This causes hangs on some platforms
    on suspend.
    
    Fixes: daf8de0874ab5b ("drm/amdgpu: always reset the asic in suspend (v2)")
    Cc: stable@vger.kernel.org
    Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1858
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 0ffb1fd1582a78649f22253d81515997fff88bc4
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Tue Jan 11 17:41:44 2022 -0500

    drm/amdgpu: invert the logic in amdgpu_device_should_recover_gpu()
    
    Rather than opting into GPU recovery support, default to on, and
    opt out if it's not working on a particular GPU.  This avoids the
    need to add new asics to this list since this is a core feature.
    
    Reviewed-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Guchun Chen <guchun.chen@amd.com>
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 4175c32be5ef0ff254d6931931ec412e8029c32a
Author: CHANDAN VURDIGERE NATARAJ <chandan.vurdigerenataraj@amd.com>
Date:   Tue Jan 11 19:02:26 2022 +0530

    drm/amdgpu: Enable recovery on yellow carp
    
    Add yellow carp to devices which support recovery
    
    Signed-off-by: CHANDAN VURDIGERE NATARAJ <chandan.vurdigerenataraj@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit f346f32701ebacf6fe397f6f1d254256f73da321
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 14 19:11:21 2022 +0100

    MAINTAINERS: Add Helge as fbdev maintainer
    
    The fbdev layer is orphaned, but seems to need some care.
    So I'd like to step up as new maintainer.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

commit c862dcd199759d4a45e65dab47b03e3e8a144e3a
Author: Yang Zhong <yang.zhong@intel.com>
Date:   Thu Jan 13 13:08:25 2022 -0500

    x86/fpu: Fix inline prefix warnings
    
    Fix sparse warnings in xstate and remove inline prefix.
    
    Fixes: 980fe2fddcff ("x86/fpu: Extend fpu_xstate_prctl() with guest permissions")
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Message-Id: <20220113180825.322333-1-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit bf70636d9443c9e0718fd98765ba634e631ed079
Author: Yang Zhong <yang.zhong@intel.com>
Date:   Thu Dec 23 09:53:22 2021 -0500

    selftest: kvm: Add amx selftest
    
    This selftest covers two aspects of AMX.  The first is triggering #NM
    exception and checking the MSR XFD_ERR value.  The second case is
    loading tile config and tile data into guest registers and trapping to
    the host side for a complete save/load of the guest state.  TMM0
    is also checked against memory data after save/restore.
    
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20211223145322.2914028-4-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6559b4a523cd65f6005b4592833b16ba970abdf5
Author: Yang Zhong <yang.zhong@intel.com>
Date:   Thu Dec 23 09:53:21 2021 -0500

    selftest: kvm: Move struct kvm_x86_state to header
    
    Those changes can avoid dereferencing pointer compile issue
    when amx_test.c reference state->xsave.
    
    Move struct kvm_x86_state definition to processor.h.
    
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20211223145322.2914028-3-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 551447cfa5dc208b7fba7aa98391d5cc8149fa5a
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Thu Dec 23 09:53:20 2021 -0500

    selftest: kvm: Reorder vcpu_load_state steps for AMX
    
    For AMX support it is recommended to load XCR0 after XFD, so
    that KVM does not see XFD=0, XCR=1 for a save state that will
    eventually be disabled (which would lead to premature allocation
    of the space required for that save state).
    
    It is also required to load XSAVE data after XCR0 and XFD, so
    that KVM can trigger allocation of the extra space required to
    store AMX state.
    
    Adjust vcpu_load_state to obey these new requirements.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20211223145322.2914028-2-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b5274b1b7ba89fe8ed38cc470041cd6ba0dfb79b
Author: Kevin Tian <kevin.tian@intel.com>
Date:   Wed Jan 5 04:35:32 2022 -0800

    kvm: x86: Disable interception for IA32_XFD on demand
    
    Always intercepting IA32_XFD causes non-negligible overhead when this
    register is updated frequently in the guest.
    
    Disable r/w emulation after intercepting the first WRMSR(IA32_XFD)
    with a non-zero value.
    
    Disable WRMSR emulation implies that IA32_XFD becomes out-of-sync
    with the software states in fpstate and the per-cpu xfd cache. This
    leads to two additional changes accordingly:
    
      - Call fpu_sync_guest_vmexit_xfd_state() after vm-exit to bring
        software states back in-sync with the MSR, before handle_exit_irqoff()
        is called.
    
      - Always trap #NM once write interception is disabled for IA32_XFD.
        The #NM exception is rare if the guest doesn't use dynamic
        features. Otherwise, there is at most one exception per guest
        task given a dynamic feature.
    
    p.s. We have confirmed that SDM is being revised to say that
    when setting IA32_XFD[18] the AMX register state is not guaranteed
    to be preserved. This clarification avoids adding mess for a creative
    guest which sets IA32_XFD[18]=1 before saving active AMX state to
    its own storage.
    
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-22-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 5429cead01192ff4019ea0b13316268d14fd1ec2
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 5 04:35:31 2022 -0800

    x86/fpu: Provide fpu_sync_guest_vmexit_xfd_state()
    
    KVM can disable the write emulation for the XFD MSR when the vCPU's fpstate
    is already correctly sized to reduce the overhead.
    
    When write emulation is disabled the XFD MSR state after a VMEXIT is
    unknown and therefore not in sync with the software states in fpstate and
    the per CPU XFD cache.
    
    Provide fpu_sync_guest_vmexit_xfd_state() which has to be invoked after a
    VMEXIT before enabling interrupts when write emulation is disabled for the
    XFD MSR.
    
    It could be invoked unconditionally even when write emulation is enabled
    for the price of a pointless MSR read.
    
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-21-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 415a3c33e847349c0f76575b3ebfdfae2f5a681a
Author: Wei Wang <wei.w.wang@intel.com>
Date:   Wed Jan 5 04:35:30 2022 -0800

    kvm: selftests: Add support for KVM_CAP_XSAVE2
    
    When KVM_CAP_XSAVE2 is supported, userspace is expected to allocate
    buffer for KVM_GET_XSAVE2 and KVM_SET_XSAVE using the size returned
    by KVM_CHECK_EXTENSION(KVM_CAP_XSAVE2).
    
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Signed-off-by: Guang Zeng <guang.zeng@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-20-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit be50b2065dfa3d88428fdfdc340d154d96bf6848
Author: Guang Zeng <guang.zeng@intel.com>
Date:   Wed Jan 5 04:35:29 2022 -0800

    kvm: x86: Add support for getting/setting expanded xstate buffer
    
    With KVM_CAP_XSAVE, userspace uses a hardcoded 4KB buffer to get/set
    xstate data from/to KVM. This doesn't work when dynamic xfeatures
    (e.g. AMX) are exposed to the guest as they require a larger buffer
    size.
    
    Introduce a new capability (KVM_CAP_XSAVE2). Userspace VMM gets the
    required xstate buffer size via KVM_CHECK_EXTENSION(KVM_CAP_XSAVE2).
    KVM_SET_XSAVE is extended to work with both legacy and new capabilities
    by doing properly-sized memdup_user() based on the guest fpu container.
    KVM_GET_XSAVE is kept for backward-compatible reason. Instead,
    KVM_GET_XSAVE2 is introduced under KVM_CAP_XSAVE2 as the preferred
    interface for getting xstate buffer (4KB or larger size) from KVM
    (Link: https://lkml.org/lkml/2021/12/15/510)
    
    Also, update the api doc with the new KVM_GET_XSAVE2 ioctl.
    
    Signed-off-by: Guang Zeng <guang.zeng@intel.com>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-19-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c60427dd50ba9b20063ccaed0e98d62e886d7a3b
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 5 04:35:28 2022 -0800

    x86/fpu: Add uabi_size to guest_fpu
    
    Userspace needs to inquire KVM about the buffer size to work
    with the new KVM_SET_XSAVE and KVM_GET_XSAVE2. Add the size info
    to guest_fpu for KVM to access.
    
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-18-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 690a757d610e50c2c3acd2e4bc3992cfc63feff2
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:27 2022 -0800

    kvm: x86: Add CPUID support for Intel AMX
    
    Extend CPUID emulation to support XFD, AMX_TILE, AMX_INT8 and
    AMX_BF16. Adding those bits into kvm_cpu_caps finally activates all
    previous logics in this series.
    
    Hide XFD on 32bit host kernels. Otherwise it leads to a weird situation
    where KVM tells userspace to migrate MSR_IA32_XFD and then rejects
    attempts to read/write the MSR.
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-17-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 86aff7a4799286635efd94dab17b513544703cad
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:26 2022 -0800

    kvm: x86: Add XCR0 support for Intel AMX
    
    Two XCR0 bits are defined for AMX to support XSAVE mechanism. Bit 17
    is for tilecfg and bit 18 is for tiledata.
    
    The value of XCR0[17:18] is always either 00b or 11b. Also, SDM
    recommends that only 64-bit operating systems enable Intel AMX by
    setting XCR0[18:17]. 32-bit host kernel never sets the tile bits in
    vcpu->arch.guest_supported_xcr0.
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-16-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 61f208134a871047f1d642ed3b813f4f71e30b0e
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:25 2022 -0800

    kvm: x86: Disable RDMSR interception of IA32_XFD_ERR
    
    This saves one unnecessary VM-exit in guest #NM handler, given that the
    MSR is already restored with the guest value before the guest is resumed.
    
    Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-15-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 548e83650a51dce0d188b9e41b1e2ca5d63597cf
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:24 2022 -0800

    kvm: x86: Emulate IA32_XFD_ERR for guest
    
    Emulate read/write to IA32_XFD_ERR MSR.
    
    Only the saved value in the guest_fpu container is touched in the
    emulation handler. Actual MSR update is handled right before entering
    the guest (with preemption disabled)
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Zeng Guang <guang.zeng@intel.com>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-14-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit ec5be88ab29fd9145c7ced20b58fb96f7c6b6890
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:23 2022 -0800

    kvm: x86: Intercept #NM for saving IA32_XFD_ERR
    
    Guest IA32_XFD_ERR is generally modified in two places:
    
      - Set by CPU when #NM is triggered;
      - Cleared by guest in its #NM handler;
    
    Intercept #NM for the first case when a nonzero value is written
    to IA32_XFD. Nonzero indicates that the guest is willing to do
    dynamic fpstate expansion for certain xfeatures, thus KVM needs to
    manage and virtualize guest XFD_ERR properly. The vcpu exception
    bitmap is updated in XFD write emulation according to guest_fpu::xfd.
    
    Save the current XFD_ERR value to the guest_fpu container in the #NM
    VM-exit handler. This must be done with interrupt disabled, otherwise
    the unsaved MSR value may be clobbered by host activity.
    
    The saving operation is conducted conditionally only when guest_fpu:xfd
    includes a non-zero value. Doing so also avoids misread on a platform
    which doesn't support XFD but #NM is triggered due to L1 interception.
    
    Queueing #NM to the guest is postponed to handle_exception_nmi(). This
    goes through the nested_vmx check so a virtual vmexit is queued instead
    when #NM is triggered in L2 but L1 wants to intercept it.
    
    Restore the host value (always ZERO outside of the host #NM
    handler) before enabling interrupt.
    
    Restore the guest value from the guest_fpu container right before
    entering the guest (with interrupt disabled).
    
    Suggested-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-13-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 1df4fd834e8e2c00973ac2003ad0e6feb8750b31
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:22 2022 -0800

    x86/fpu: Prepare xfd_err in struct fpu_guest
    
    When XFD causes an instruction to generate #NM, IA32_XFD_ERR
    contains information about which disabled state components are
    being accessed. The #NM handler is expected to check this
    information and then enable the state components by clearing
    IA32_XFD for the faulting task (if having permission).
    
    If the XFD_ERR value generated in guest is consumed/clobbered
    by the host before the guest itself doing so, it may lead to
    non-XFD-related #NM treated as XFD #NM in host (due to non-zero
    value in XFD_ERR), or XFD-related #NM treated as non-XFD #NM in
    guest (XFD_ERR cleared by the host #NM handler).
    
    Introduce a new field in fpu_guest to save the guest xfd_err value.
    KVM is expected to save guest xfd_err before interrupt is enabled
    and restore it right before entering the guest (with interrupt
    disabled).
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-12-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 820a6ee944e74e57255ac2e90916ecdaade57b95
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:21 2022 -0800

    kvm: x86: Add emulation for IA32_XFD
    
    Intel's eXtended Feature Disable (XFD) feature allows the software
    to dynamically adjust fpstate buffer size for XSAVE features which
    have large state.
    
    Because guest fpstate has been expanded for all possible dynamic
    xstates at KVM_SET_CPUID2, emulation of the IA32_XFD MSR is
    straightforward. For write just call fpu_update_guest_xfd() to
    update the guest fpu container once all the sanity checks are passed.
    For read simply return the cached value in the container.
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Zeng Guang <guang.zeng@intel.com>
    Signed-off-by: Wei Wang <wei.w.wang@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-11-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 8eb9a48ac1e86a8a59f7123b529d6e498fb1f163
Author: Kevin Tian <kevin.tian@intel.com>
Date:   Wed Jan 5 04:35:20 2022 -0800

    x86/fpu: Provide fpu_update_guest_xfd() for IA32_XFD emulation
    
    Guest XFD can be updated either in the emulation path or in the
    restore path.
    
    Provide a wrapper to update guest_fpu::fpstate::xfd. If the guest
    fpstate is currently in-use, also update the per-cpu xfd cache and
    the actual MSR.
    
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-10-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 5ab2f45bba4894a0db4af8567da3efd6228dd010
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:19 2022 -0800

    kvm: x86: Enable dynamic xfeatures at KVM_SET_CPUID2
    
    KVM can request fpstate expansion in two approaches:
    
      1) When intercepting guest updates to XCR0 and XFD MSR;
    
      2) Before vcpu runs (e.g. at KVM_SET_CPUID2);
    
    The first option doesn't waste memory for legacy guest if it doesn't
    support XFD. However doing so introduces more complexity and also
    imposes an order requirement in the restoring path, i.e. XCR0/XFD
    must be restored before XSTATE.
    
    Given that the agreement is to do the static approach. This is
    considered a better tradeoff though it does waste 8K memory for
    legacy guest if its CPUID includes dynamically-enabled xfeatures.
    
    Successful fpstate expansion requires userspace VMM to acquire
    guest xstate permissions before calling KVM_SET_CPUID2.
    
    Also take the chance to adjust the indent in kvm_set_cpuid().
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-9-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 0781d60f658e25fbad3b6e4261f54eb1cd3dc302
Author: Sean Christopherson <seanjc@google.com>
Date:   Wed Jan 5 04:35:18 2022 -0800

    x86/fpu: Provide fpu_enable_guest_xfd_features() for KVM
    
    Provide a wrapper for expanding the guest fpstate buffer according
    to requested xfeatures. KVM wants to call this wrapper to manage
    any dynamic xstate used by the guest.
    
    Suggested-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
    Message-Id: <20220105123532.12586-8-yang.zhong@intel.com>
    [Remove unnecessary 32-bit check. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit c270ce393dfd700e7510a4579568deeefba954fd
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 5 04:35:17 2022 -0800

    x86/fpu: Add guest support to xfd_enable_feature()
    
    Guest support for dynamically enabled FPU features requires a few
    modifications to the enablement function which is currently invoked from
    the #NM handler:
    
      1) Use guest permissions and sizes for the update
    
      2) Update fpu_guest state accordingly
    
      3) Take into account that the enabling can be triggered either from a
         running guest via XSETBV and MSR_IA32_XFD write emulation or from
         a guest restore. In the latter case the guests fpstate is not the
         current tasks active fpstate.
    
    Split the function and implement the guest mechanics throughout the
    callchain.
    
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-7-yang.zhong@intel.com>
    [Add 32-bit stub for __xfd_enable_feature. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit b0237dad2d7f8820b5b415291431d8259e787470
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:16 2022 -0800

    x86/fpu: Make XFD initialization in __fpstate_reset() a function argument
    
    vCPU threads are different from native tasks regarding to the initial XFD
    value. While all native tasks follow a fixed value (init_fpstate::xfd)
    established by the FPU core at boot, vCPU threads need to obey the reset
    value (i.e. ZERO) defined by the specification, to meet the expectation of
    the guest.
    
    Let the caller supply an argument and adjust the host and guest related
    invocations accordingly.
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-6-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a97ac8cb24a3c3ad74794adb83717ef1605d1b47
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Thu Jan 13 16:51:52 2022 -0800

    module: fix signature check failures when using in-kernel decompression
    
    The new flag MODULE_INIT_COMPRESSED_FILE unintentionally trips check in
    module_sig_check(). The check was supposed to catch case when version
    info or magic was removed from a signed module, making signature
    invalid, but it was coded too broadly and was catching this new flag as
    well.
    
    Change the check to only test the 2 particular flags affecting signature
    validity.
    
    Fixes: b1ae6dc41eaa ("module: add in-kernel support for decompressing")
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Reviewed-by: Douglas Anderson <dianders@chromium.org>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit 91502a9a0b0d5252cf3f32ebd898823c2f5aadab
Author: Alexander Sergeyev <sergeev917@gmail.com>
Date:   Fri Jan 14 19:50:50 2022 +0300

    ALSA: hda/realtek: fix speakers and micmute on HP 855 G8
    
    There are several PCI ids associated with HP EliteBook 855 G8 Notebook
    PC. Commit 0e68c4b11f1e6 ("ALSA: hda/realtek: fix mute/micmute LEDs for
    HP 855 G8") covers 0x103c:0x8896, while this commit covers 0x103c:0x8895
    which needs some additional work on top of the quirk from 0e68c4b11f1e6.
    
    Note that the device can boot up with working speakers and micmute LED
    without this patch, but the success rate would be quite low (order of
    16 working boots across 709 boots) at least for the built-in drivers
    scenario. This also means that there are some timing issues during early
    boot and this patch is a workaround.
    
    With this patch applied speakers and headphones are consistenly working,
    as well as mute/micmute LEDs and the internal microphone.
    
    Signed-off-by: Alexander Sergeyev <sergeev917@gmail.com>
    Link: https://lore.kernel.org/r/20220114165050.ouw2nknuspclynro@localhost.localdomain
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 94fd19752b28aa66c98e7991734af91dfc529f8f
Author: Miklos Szeredi <mszeredi@redhat.com>
Date:   Fri Jan 14 16:57:56 2022 +0100

    ovl: don't fail copy up if no fileattr support on upper
    
    Christoph Fritz is reporting that failure to copy up fileattr when upper
    doesn't support fileattr or xattr results in a regression.
    
    Return success in these failure cases; this reverts overlayfs to the old
    behavior.
    
    Add a pr_warn_once() in these cases to still let the user know about the
    copy up failures.
    
    Reported-by: Christoph Fritz <chf.fritz@googlemail.com>
    Fixes: 72db82115d2b ("ovl: copy up sync/noatime fileattr flags")
    Cc: <stable@vger.kernel.org> # v5.15
    Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

commit aed28b7a2d620cb5cd0c554cb889075c02e25e8e
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Jan 13 12:20:36 2022 -0500

    SUNRPC: Don't dereference xprt->snd_task if it's a cookie
    
    Fixes: e26d9972720e ("SUNRPC: Clean up scheduling of autoclose")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit c0f26167ddcf94fb94e80fcb20aaac7f7db13c1a
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Jan 13 12:20:30 2022 -0500

    xprtrdma: Remove definitions of RPCDBG_FACILITY
    
    Deprecated. dprintk is no longer used in xprtrdma.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit c03061e7a210b4fe37440a1940fc198744a55ca4
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Jan 13 12:20:23 2022 -0500

    xprtrdma: Remove final dprintk call sites from xprtrdma
    
    Deprecated. This information is available via tracepoints.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 112450df61b7373529b0fe4c122ad13b89d80a8a
Merge: 3bad80dab94a1 bf3c39f5da434
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 16:19:38 2022 +0100

    Merge branch 'i2c/for-mergewindow' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux
    
    Pull i2c updates from Wolfram Sang:
     "Mostly driver updates and refactorization.
    
      The removal of the XLR driver and the i801 refactoring stand out a
      little. In the core, we enabled async suspend/resume for I2C
      controllers and their clients. No issues were reported during the test
      phase in -next. We will see how this goes for mainline"
    
    * 'i2c/for-mergewindow' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux: (54 commits)
      i2c: sh_mobile: remove unneeded semicolon
      i2c: riic: Use platform_get_irq() to get the interrupt
      i2c: sh_mobile: Use platform_get_irq_optional() to get the interrupt
      i2c: bcm2835: Use platform_get_irq() to get the interrupt
      i2c: aspeed: Remove unused includes
      dt-bindings: i2c: aspeed: Drop stray '#interrupt-cells'
      i2c: sh_mobile: update to new DMAENGINE API when terminating
      i2c: rcar: update to new DMAENGINE API when terminating
      i2c: exynos5: Fix getting the optional clock
      i2c: designware-pci: Convert to use dev_err_probe()
      i2c: designware-pci: use __maybe_unused for PM functions
      i2c: designware-pci: Group MODULE_*() macros
      i2c: designware-pci: Add a note about struct dw_scl_sda_cfg usage
      i2c: designware-pci: Fix to change data types of hcnt and lcnt parameters
      i2c: designware: Do not complete i2c read without RX_FULL interrupt
      eeprom: at24: Add support for 24c1025 EEPROM
      dt-bindings: at24: add at24c1025
      i2c: tegra: use i2c_timings for bus clock freq
      dt-bindings: at24: Rework special case compatible handling
      i2c: i801: Don't clear status flags twice in interrupt mode
      ...

commit 3bad80dab94a16c9b7991105e3bffd5fe5957e9a
Merge: 871bfa02d08d9 d47c7407b4c88
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 16:02:28 2022 +0100

    Merge tag 'char-misc-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc
    
    Pull char/misc and other driver updates from Greg KH:
     "Here is the large set of char, misc, and other "small" driver
      subsystem changes for 5.17-rc1.
    
      Lots of different things are in here for char/misc drivers such as:
    
       - habanalabs driver updates
    
       - mei driver updates
    
       - lkdtm driver updates
    
       - vmw_vmci driver updates
    
       - android binder driver updates
    
       - other small char/misc driver updates
    
      Also smaller driver subsystems have also been updated, including:
    
       - fpga subsystem updates
    
       - iio subsystem updates
    
       - soundwire subsystem updates
    
       - extcon subsystem updates
    
       - gnss subsystem updates
    
       - phy subsystem updates
    
       - coresight subsystem updates
    
       - firmware subsystem updates
    
       - comedi subsystem updates
    
       - mhi subsystem updates
    
       - speakup subsystem updates
    
       - rapidio subsystem updates
    
       - spmi subsystem updates
    
       - virtual driver updates
    
       - counter subsystem updates
    
      Too many individual changes to summarize, the shortlog contains the
      full details.
    
      All of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'char-misc-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: (406 commits)
      counter: 104-quad-8: Fix use-after-free by quad8_irq_handler
      dt-bindings: mux: Document mux-states property
      dt-bindings: ti-serdes-mux: Add defines for J721S2 SoC
      counter: remove old and now unused registration API
      counter: ti-eqep: Convert to new counter registration
      counter: stm32-lptimer-cnt: Convert to new counter registration
      counter: stm32-timer-cnt: Convert to new counter registration
      counter: microchip-tcb-capture: Convert to new counter registration
      counter: ftm-quaddec: Convert to new counter registration
      counter: intel-qep: Convert to new counter registration
      counter: interrupt-cnt: Convert to new counter registration
      counter: 104-quad-8: Convert to new counter registration
      counter: Update documentation for new counter registration functions
      counter: Provide alternative counter registration functions
      counter: stm32-timer-cnt: Convert to counter_priv() wrapper
      counter: stm32-lptimer-cnt: Convert to counter_priv() wrapper
      counter: ti-eqep: Convert to counter_priv() wrapper
      counter: ftm-quaddec: Convert to counter_priv() wrapper
      counter: intel-qep: Convert to counter_priv() wrapper
      counter: microchip-tcb-capture: Convert to counter_priv() wrapper
      ...

commit 4ee7e4a6c9b298da44029ed9ec8ed23ae49cc209
Author: Christoph Fritz <chf.fritz@googlemail.com>
Date:   Wed Jan 12 19:33:21 2022 +0100

    ovl: fix NULL pointer dereference in copy up warning
    
    This patch is fixing a NULL pointer dereference to get a recently
    introduced warning message working.
    
    Fixes: 5b0a414d06c3 ("ovl: fix filattr copy-up failure")
    Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
    Cc: <stable@vger.kernel.org> # v5.15
    Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

commit a6e62743621ea29bea461774c0bcc68e5de59068
Author: Thomas Richter <tmricht@linux.ibm.com>
Date:   Wed Nov 24 10:03:43 2021 +0100

    perf cputopo: Fix CPU topology reading on s/390
    
    Commit fdf1e29b6118c18f ("perf expr: Add metric literals for topology.")
    fails on s390:
    
     # ./perf test -Fv 7
       ...
     # FAILED tests/expr.c:173 #num_dies >= #num_packages
       ---- end ----
       Simple expression parser: FAILED!
     #
    
    Investigating this issue leads to these functions:
     build_cpu_topology()
       +--> has_die_topology(void)
            {
               struct utsname uts;
    
               if (uname(&uts) < 0)
                      return false;
               if (strncmp(uts.machine, "x86_64", 6))
                      return false;
               ....
            }
    
    which always returns false on s390. The caller build_cpu_topology()
    checks has_die_topology() return value. On false the
    the struct cpu_topology::die_cpu_list is not contructed and has zero
    entries. This leads to the failing comparison: #num_dies >= #num_packages.
    s390 of course has a positive number of packages.
    
    Fix this by adding s390 architecture to support CPU die list.
    
    Output after:
     # ./perf test -Fv 7
      7: Simple expression parser                                        :
      --- start ---
      division by zero
      syntax error
      ---- end ----
      Simple expression parser: Ok
     #
    
    Fixes: fdf1e29b6118c18f ("perf expr: Add metric literals for topology.")
    Reviewed-by: Ian Rogers <irogers@google.com>
    Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
    Cc: Heiko Carstens <hca@linux.ibm.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Sumanth Korikkar <sumanthk@linux.ibm.com>
    Cc: Sven Schnelle <svens@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Link: https://lore.kernel.org/r/20211124090343.9436-1-tmricht@linux.ibm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit e000ea0beffb5497425054b151369fe37a792ece
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Wed Dec 8 18:11:13 2021 +0100

    perf metricgroup: Fix use after free in metric__new()
    
    We shouldn't free() something that will be used in the next line, fix
    it.
    
    Fixes: b85a4d61d3022608 ("perf metric: Allow modifiers on metrics")
    Addresses-Coverity-ID: 1494000
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: http://lore.kernel.org/lkml/20211208171113.22089-1-jose.exposito89@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 4efdddbce7c1329f00c458e85dcaf105aebdc0ed
Merge: 820e690e4eb88 5eb877b282fec
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 14 15:42:27 2022 +0100

    Merge tag 'amd-drm-next-5.17-2022-01-12' of https://gitlab.freedesktop.org/agd5f/linux into drm-next
    
    amd-drm-next-5.17-2022-01-12:
    
    amdgpu:
    - SR-IOV fixes
    - Suspend/resume fixes
    - Display fixes
    - DMCUB fixes
    - DP alt mode fixes
    - RAS fixes
    - UBSAN fix
    - Navy Flounder VCN fix
    - ttm resource manager cleanup
    - default_groups change for kobj_type
    - vkms fix
    - Aldebaran fixes
    
    amdkfd:
    - SDMA ECC interrupt fix
    - License clarification
    - Pointer check fix
    - DQM fixes for hawaii
    - default_groups change for kobj_type
    - Typo fixes
    
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    From: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220113030537.5758-1-alexander.deucher@amd.com

commit 820e690e4eb88eaee68bf0b2d89fa9597bc00a45
Merge: 71e4a7029045e 5d474cc501b90
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 14 15:41:47 2022 +0100

    Merge tag 'drm-misc-next-fixes-2022-01-14' of git://anongit.freedesktop.org/drm/drm-misc into drm-next
    
     * atomic helpers: Fix error messages
     * mipi-dbi: Fix buffer mapping
    
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/YeGHu7qU92pjuQOn@linux-uq9g

commit 99fc11bb5b6f19d2c3671d6cf38571cb3dedb472
Author: Ian Rogers <irogers@google.com>
Date:   Thu Jan 13 22:51:05 2022 -0800

    libperf tests: Update a use of the new cpumap API
    
    Fixes a build breakage.
    
    Fixes: 6d18804b963b78dc ("perf cpumap: Give CPUs their own type")
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: colin ian king <colin.king@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
    Link: http://lore.kernel.org/lkml/20220114065105.1806542-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 46f57d2410150985f81da7cbbb5fdcda01d02ac2
Author: Ian Rogers <irogers@google.com>
Date:   Thu Jan 13 22:48:22 2022 -0800

    perf arm: Fix off-by-one directory path
    
    Relative path include works in the regular build due to -I paths but may
    fail in other situations.
    
    Fixes: 83869019c74cc2d0 ("perf arch: Support register names from all archs")
    Reviewed-by: German Gomez <german.gomez@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Alexandre Truong <alexandre.truong@arm.com>
    Cc: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Link: https://lore.kernel.org/r/20220114064822.1806019-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit e652ab64e5846d3fe5ac2c0405d55d79ecc52c36
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Fri Aug 7 08:45:47 2020 -0300

    tools arch x86: Sync the msr-index.h copy with the kernel sources
    
    To pick up the changes in:
    
      89aa94b4a218339b ("x86/msr: Add AMD CPPC MSR definitions")
    
    Addressing these tools/perf build warnings:
    
        diff -u tools/arch/x86/include/asm/msr-index.h arch/x86/include/asm/msr-index.h
        Warning: Kernel ABI header at 'tools/arch/x86/include/asm/msr-index.h' differs from latest version at 'arch/x86/include/asm/msr-index.h'
    
    That makes the beautification scripts to pick some new entries:
    
      $ tools/perf/trace/beauty/tracepoints/x86_msr.sh > before
      $ cp arch/x86/include/asm/msr-index.h tools/arch/x86/include/asm/msr-index.h
      $ tools/perf/trace/beauty/tracepoints/x86_msr.sh > after
      $ diff -u before after
      --- before    2022-01-13 10:59:51.743416890 -0300
      +++ after     2022-01-13 11:00:00.776644178 -0300
      @@ -303,6 +303,11 @@
              [0xc0010299 - x86_AMD_V_KVM_MSRs_offset] = "AMD_RAPL_POWER_UNIT",
              [0xc001029a - x86_AMD_V_KVM_MSRs_offset] = "AMD_CORE_ENERGY_STATUS",
              [0xc001029b - x86_AMD_V_KVM_MSRs_offset] = "AMD_PKG_ENERGY_STATUS",
      +       [0xc00102b0 - x86_AMD_V_KVM_MSRs_offset] = "AMD_CPPC_CAP1",
      +       [0xc00102b1 - x86_AMD_V_KVM_MSRs_offset] = "AMD_CPPC_ENABLE",
      +       [0xc00102b2 - x86_AMD_V_KVM_MSRs_offset] = "AMD_CPPC_CAP2",
      +       [0xc00102b3 - x86_AMD_V_KVM_MSRs_offset] = "AMD_CPPC_REQ",
      +       [0xc00102b4 - x86_AMD_V_KVM_MSRs_offset] = "AMD_CPPC_STATUS",
              [0xc00102f0 - x86_AMD_V_KVM_MSRs_offset] = "AMD_PPIN_CTL",
              [0xc00102f1 - x86_AMD_V_KVM_MSRs_offset] = "AMD_PPIN",
       };
      $
    
    And this gets rebuilt:
    
      CC       /tmp/build/perf/trace/beauty/tracepoints/x86_msr.o
      INSTALL  trace_plugins
      LD       /tmp/build/perf/trace/beauty/tracepoints/perf-in.o
      LD       /tmp/build/perf/trace/beauty/perf-in.o
      LD       /tmp/build/perf/perf-in.o
      LINK     /tmp/build/perf/perf
    
    Now one can trace systemwide asking to see backtraces to where those
    MSRs are being read/written with:
    
      # perf trace -e msr:*_msr/max-stack=32/ --filter="msr>=AMD_CPPC_CAP1 && msr<=AMD_CPPC_STATUS"
      ^C#
    
    If we use -v (verbose mode) we can see what it does behind the scenes:
    
      # perf trace -v -e msr:*_msr/max-stack=32/ --filter="msr>=AMD_CPPC_CAP1 && msr<=AMD_CPPC_STATUS"
      <SNIP>
      New filter for msr:read_msr: (msr>=0xc00102b0 && msr<=0xc00102b4) && (common_pid != 2612102 && common_pid != 3841)
      New filter for msr:write_msr: (msr>=0xc00102b0 && msr<=0xc00102b4) && (common_pid != 2612102 && common_pid != 3841)
      <SNIP>
      ^C#
    
    Example with a frequent msr:
    
      # perf trace -v -e msr:*_msr/max-stack=32/ --filter="msr==IA32_SPEC_CTRL" --max-events 2
      Using CPUID AuthenticAMD-25-21-0
      0x48
      New filter for msr:read_msr: (msr==0x48) && (common_pid != 2612129 && common_pid != 3841)
      0x48
      New filter for msr:write_msr: (msr==0x48) && (common_pid != 2612129 && common_pid != 3841)
      mmap size 528384B
      Looking at the vmlinux_path (8 entries long)
      symsrc__init: build id mismatch for vmlinux.
      Using /proc/kcore for kernel data
      Using /proc/kallsyms for symbols
           0.000 Timer/2525383 msr:write_msr(msr: IA32_SPEC_CTRL, val: 6)
                                             do_trace_write_msr ([kernel.kallsyms])
                                             do_trace_write_msr ([kernel.kallsyms])
                                             __switch_to_xtra ([kernel.kallsyms])
                                             __switch_to ([kernel.kallsyms])
                                             __schedule ([kernel.kallsyms])
                                             schedule ([kernel.kallsyms])
                                             futex_wait_queue_me ([kernel.kallsyms])
                                             futex_wait ([kernel.kallsyms])
                                             do_futex ([kernel.kallsyms])
                                             __x64_sys_futex ([kernel.kallsyms])
                                             do_syscall_64 ([kernel.kallsyms])
                                             entry_SYSCALL_64_after_hwframe ([kernel.kallsyms])
                                             __futex_abstimed_wait_common64 (/usr/lib64/libpthread-2.33.so)
           0.030 :0/0 msr:write_msr(msr: IA32_SPEC_CTRL, val: 2)
                                             do_trace_write_msr ([kernel.kallsyms])
                                             do_trace_write_msr ([kernel.kallsyms])
                                             __switch_to_xtra ([kernel.kallsyms])
                                             __switch_to ([kernel.kallsyms])
                                             __schedule ([kernel.kallsyms])
                                             schedule_idle ([kernel.kallsyms])
                                             do_idle ([kernel.kallsyms])
                                             cpu_startup_entry ([kernel.kallsyms])
                                             secondary_startup_64_no_verify ([kernel.kallsyms])
      #
    
    Acked-by: Huang Rui <ray.huang@amd.com>
    Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Cc: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Ian Rogers <irogers@google.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Link: https://lore.kernel.org/all/YeA2PAvHV+uHRhLj@kernel.org
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 871bfa02d08d9c0ed981c50082b7afd367d3700b
Merge: 29ec39fcf11e4 7f435e42fd6b6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 15:32:09 2022 +0100

    Merge tag 'for-linus' of git://github.com/openrisc/linux
    
    Pull OpenRISC updates from Stafford Horne:
     "A few fixups and enhancements for OpenRISC:
    
       - Fix to add proper wrapper for clone3 to save callee saved regs
    
       - Cleanups for clone, fork and switch
    
       - Add support for common clk so OpenRISC and use more drivers"
    
    * tag 'for-linus' of git://github.com/openrisc/linux:
      openrisc: init: Add support for common clk
      openrisc: Add clone3 ABI wrapper
      openrisc: Use delay slot for clone and fork wrappers
      openrisc: Cleanup switch code and comments

commit 29ec39fcf11e4583eb8d5174f756ea109c77cc44
Merge: 3fb561b1e0bf4 f1aa0e47c2926
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 15:17:26 2022 +0100

    Merge tag 'powerpc-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
    
    Pull powerpc updates from Michael Ellerman:
    
     - Optimise radix KVM guest entry/exit by 2x on Power9/Power10.
    
     - Allow firmware to tell us whether to disable the entry and uaccess
       flushes on Power10 or later CPUs.
    
     - Add BPF_PROBE_MEM support for 32 and 64-bit BPF jits.
    
     - Several fixes and improvements to our hard lockup watchdog.
    
     - Activate HAVE_DYNAMIC_FTRACE_WITH_REGS on 32-bit.
    
     - Allow building the 64-bit Book3S kernel without hash MMU support, ie.
       Radix only.
    
     - Add KUAP (SMAP) support for 40x, 44x, 8xx, Book3E (64-bit).
    
     - Add new encodings for perf_mem_data_src.mem_hops field, and use them
       on Power10.
    
     - A series of small performance improvements to 64-bit interrupt entry.
    
     - Several commits fixing issues when building with the clang integrated
       assembler.
    
     - Many other small features and fixes.
    
    Thanks to Alan Modra, Alexey Kardashevskiy, Ammar Faizi, Anders Roxell,
    Arnd Bergmann, Athira Rajeev, Cédric Le Goater, Christophe JAILLET,
    Christophe Leroy, Christoph Hellwig, Daniel Axtens, David Yang, Erhard
    Furtner, Fabiano Rosas, Greg Kroah-Hartman, Guo Ren, Hari Bathini, Jason
    Wang, Joel Stanley, Julia Lawall, Kajol Jain, Kees Cook, Laurent Dufour,
    Madhavan Srinivasan, Mark Brown, Minghao Chi, Nageswara R Sastry, Naresh
    Kamboju, Nathan Chancellor, Nathan Lynch, Nicholas Piggin, Nick Child,
    Oliver O'Halloran, Peiwei Hu, Randy Dunlap, Ravi Bangoria, Rob Herring,
    Russell Currey, Sachin Sant, Sean Christopherson, Segher Boessenkool,
    Thadeu Lima de Souza Cascardo, Tyrel Datwyler, Xiang wangx, and Yang
    Guang.
    
    * tag 'powerpc-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux: (240 commits)
      powerpc/xmon: Dump XIVE information for online-only processors.
      powerpc/opal: use default_groups in kobj_type
      powerpc/cacheinfo: use default_groups in kobj_type
      powerpc/sched: Remove unused TASK_SIZE_OF
      powerpc/xive: Add missing null check after calling kmalloc
      powerpc/floppy: Remove usage of the deprecated "pci-dma-compat.h" API
      selftests/powerpc: Add a test of sigreturning to an unaligned address
      powerpc/64s: Use EMIT_WARN_ENTRY for SRR debug warnings
      powerpc/64s: Mask NIP before checking against SRR0
      powerpc/perf: Fix spelling of "its"
      powerpc/32: Fix boot failure with GCC latent entropy plugin
      powerpc/code-patching: Replace patch_instruction() by ppc_inst_write() in selftests
      powerpc/code-patching: Move code patching selftests in its own file
      powerpc/code-patching: Move instr_is_branch_{i/b}form() in code-patching.h
      powerpc/code-patching: Move patch_exception() outside code-patching.c
      powerpc/code-patching: Use test_trampoline for prefixed patch test
      powerpc/code-patching: Fix patch_branch() return on out-of-range failure
      powerpc/code-patching: Reorganise do_patch_instruction() to ease error handling
      powerpc/code-patching: Fix unmap_patch_area() error handling
      powerpc/code-patching: Fix error handling in do_patch_instruction()
      ...

commit 71e4a7029045e3904e0e9242b4a7cd84d47b8fe5
Merge: ad783ff5a20f8 016017a195b86
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 14 15:15:56 2022 +0100

    Merge tag 'drm-misc-fixes-2022-01-14' of git://anongit.freedesktop.org/drm/drm-misc into drm-next
    
    Two DT bindings fixes for meson, a device refcounting fix for sun4i, a
    probe fix for vga16fb, a locking fix for the CMA dma-buf heap and a
    compilation fix for ttm.
    
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    [danvet: I made sure I have exactly the same conflict resolution as
    Linus in 8d0749b4f83b ("Merge tag 'drm-next-2022-01-07' of
    git://anongit.freedesktop.org/drm/drm") to avoid further conflict fun.
    From: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220114125454.zs46ny52lrxk3ljz@houat

commit 094d00f8ca58c5d29b25e23b4daaed1ff1f13b41
Author: Marc Zyngier <maz@kernel.org>
Date:   Fri Jan 14 08:57:58 2022 +0000

    KVM: arm64: pkvm: Use the mm_ops indirection for cache maintenance
    
    CMOs issued from EL2 cannot directly use the kernel helpers,
    as EL2 doesn't have a mapping of the guest pages. Oops.
    
    Instead, use the mm_ops indirection to use helpers that will
    perform a mapping at EL2 and allow the CMO to be effective.
    
    Fixes: 25aa28691bb9 ("KVM: arm64: Move guest CMOs to the fault handlers")
    Reviewed-by: Quentin Perret <qperret@google.com>
    Signed-off-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220114125038.1336965-1-maz@kernel.org

commit 3fb561b1e0bf4c75bc5f4d799845b08fa5ab3853
Merge: 3ceff4ea07410 d3115128bdafb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 15:08:36 2022 +0100

    Merge tag 'mips_5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux
    
    Pull MIPS updates from Thomas Bogendoerfer:
    
     - add support for more BCM47XX based devices
    
     - add MIPS support for brcmstb PCIe controller
    
     - add Loongson 2K1000 reset driver
    
     - remove board support for rbtx4938/rbtx4939
    
     - remove support for TX4939 SoCs
    
     - fixes and cleanups
    
    * tag 'mips_5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux: (59 commits)
      MIPS: ath79: drop _machine_restart again
      PCI: brcmstb: Augment driver for MIPs SOCs
      MIPS: bmips: Remove obsolete DMA mapping support
      MIPS: bmips: Add support PCIe controller device nodes
      dt-bindings: PCI: Add compatible string for Brcmstb 74[23]5 MIPs SOCs
      MIPS: compressed: Fix build with ZSTD compression
      MIPS: BCM47XX: Add support for Netgear WN2500RP v1 & v2
      MIPS: BCM47XX: Add support for Netgear R6300 v1
      MIPS: BCM47XX: Add LEDs and buttons for Asus RTN-10U
      MIPS: BCM47XX: Add board entry for Linksys WRT320N v1
      MIPS: BCM47XX: Define Linksys WRT310N V2 buttons
      MIPS: Remove duplicated include in local.h
      MIPS: retire "asm/llsc.h"
      MIPS: rework local_t operation on MIPS64
      MIPS: fix local_{add,sub}_return on MIPS64
      mips/pci: remove redundant ret variable
      MIPS: Loongson64: Add missing of_node_put() in ls2k_reset_init()
      MIPS: new Kconfig option ZBOOT_LOAD_ADDRESS
      MIPS: enable both vmlinux.gz.itb and vmlinuz for generic
      MIPS: signal: Return immediately if call fails
      ...

commit 3ceff4ea07410763d5d4cccd60349bf7691e7e61
Merge: e1a7aa25ff456 081c73701ef0c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 14:55:38 2022 +0100

    Merge tag 'sound-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
    
    Pull sound updates from Takashi Iwai:
     "It's a relatively calm development cycle, but still lots of updates in
      the driver side like Intel SOF. Below are some highlights:
    
      ALSA / ASoC core:
       - A new kselftest for ALSA control API
       - PCM NO_REWINDS support
       - Potential race fixes around control removals
       - Unify x86 SG-buffer memory allocation code
       - Cleanups and race fixes for ASoC DPCM locking
    
      ASoC:
       - Refinements and cleanups around the delay() APIs
       - Wider use of dev_err_probe().
       - Continuing cleanups and improvements to the SOF code
       - Support for pin switches in simple-card derived cards
       - Support for AMD Renoir ACP, Asahi Kasei Microdevices AKM4375, Intel
         systems using NAU8825 and MAX98390, Mediatek MT8915, nVidia Tegra20
         S/PDIF, Qualcomm systems using ALC5682I-VS and Texas Instruments
         TLV320ADC3xxx
    
      HD-audio / USB-audio:
       - Fix deadlock at HD-audio codec unbinding
       - Fixes for Tegra194 HD-audio, new HDA support for CS35L41 codec
       - Quirks for Lenovo and HP machines, Gigabyte mobo, Bose device
    
      Misc:
       - Fix virmidi drain behavior
    
      Note that the merge of CS35L41 codec support is still half-baked, and
      at least one ACPI change is missing. Although this won't hinder the
      kernel build itself, we're going to catch up before RC1"
    
    * tag 'sound-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound: (415 commits)
      ALSA: hda: intel-dsp-config: reorder the config table
      ALSA: hda: intel-dsp-config: add JasperLake support
      ALSA: hda: cs35l41: fix double free on error in probe()
      ALSA: hda: Fix dependencies of CS35L41 on SPI/I2C buses
      ALSA: hda: Fix dependency on ASoC cs35l41 codec
      ASoC: cs35l41: Add support for hibernate memory retention mode
      ASoC: cs35l41: Update handling of test key registers
      ALSA: intel_hdmi: Check for error num after setting mask
      ASoC: wcd9335: Keep a RX port value for each SLIM RX mux
      ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
      ALSA: virmidi: Remove duplicated code
      ALSA: seq: virmidi: Add a drain operation
      ASoC: topology: Fix typo
      ASoC: fsl_asrc: refine the check of available clock divider
      ASoC: Intel: bytcr_rt5640: Add support for external GPIO jack-detect
      ASoC: Intel: bytcr_rt5640: Support retrieving the codec IRQ from the AMCR0F28 ACPI dev
      ASoC: rt5640: Add support for boards with an external jack-detect GPIO
      ASoC: rt5640: Allow snd_soc_component_set_jack() to override the codec IRQ
      ASoC: rt5640: Change jack_work to a delayed_work
      ASoC: rt5640: Fix possible NULL pointer deref on resume
      ...

commit 791f3465c4afde02d7f16cf7424ca87070b69396
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Fri Jan 14 11:59:10 2022 +0000

    io_uring: fix UAF due to missing POLLFREE handling
    
    Fixes a problem described in 50252e4b5e989
    ("aio: fix use-after-free due to missing POLLFREE handling")
    and copies the approach used there.
    
    In short, we have to forcibly eject a poll entry when we meet POLLFREE.
    We can't rely on io_poll_get_ownership() as can't wait for potentially
    running tw handlers, so we use the fact that wqs are RCU freed. See
    Eric's patch and comments for more details.
    
    Reported-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209010455.42744-6-ebiggers@kernel.org
    Reported-and-tested-by: syzbot+5426c7ed6868c705ca14@syzkaller.appspotmail.com
    Fixes: 221c5eb233823 ("io_uring: add support for IORING_OP_POLL")
    Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
    Link: https://lore.kernel.org/r/4ed56b6f548f7ea337603a82315750449412748a.1642161259.git.asml.silence@gmail.com
    [axboe: drop non-functional change from patch]
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 5d474cc501b90b82c182b5d00439eb6790a82e21
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Tue Jan 11 14:26:34 2022 +0100

    drm/mipi-dbi: Fix source-buffer address in mipi_dbi_buf_copy
    
    Set the source-buffer address after mapping the buffer into the
    kernel's address space. Makes MIPI DBI helpers work again.
    
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
    Fixes: c47160d8edcd ("drm/mipi-dbi: Remove dependency on GEM CMA helper library")
    Reviewed-by: Noralf Trønnes <noralf@tronnes.org>
    Reported-by: Noralf Trønnes <noralf@tronnes.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220111132634.18302-1-tzimmermann@suse.de
    (cherry picked from commit 9d31993451f6bb4059a9b9eec4856b2225e36df0)
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>

commit e1a7aa25ff45636a6c1930bf2430c8b802e93d9c
Merge: fb3b0673b7d5b c77b1f8a8faee
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Jan 14 14:37:34 2022 +0100

    Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
    
    Pull SCSI updates from James Bottomley:
     "This series consists of the usual driver updates (ufs, pm80xx, lpfc,
      mpi3mr, mpt3sas, hisi_sas, libsas) and minor updates and bug fixes.
    
      The most impactful change is likely the switch from GFP_DMA to
      GFP_KERNEL in a bunch of drivers, but even that shouldn't affect too
      many people"
    
    * tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi: (121 commits)
      scsi: mpi3mr: Bump driver version to 8.0.0.61.0
      scsi: mpi3mr: Fixes around reply request queues
      scsi: mpi3mr: Enhanced Task Management Support Reply handling
      scsi: mpi3mr: Use TM response codes from MPI3 headers
      scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
      scsi: mpi3mr: Print cable mngnt and temp threshold events
      scsi: mpi3mr: Support Prepare for Reset event
      scsi: mpi3mr: Add Event acknowledgment logic
      scsi: mpi3mr: Gracefully handle online FW update operation
      scsi: mpi3mr: Detect async reset that occurred in firmware
      scsi: mpi3mr: Add IOC reinit function
      scsi: mpi3mr: Handle offline FW activation in graceful manner
      scsi: mpi3mr: Code refactor of IOC init - part2
      scsi: mpi3mr: Code refactor of IOC init - part1
      scsi: mpi3mr: Fault IOC when internal command gets timeout
      scsi: mpi3mr: Display IOC firmware package version
      scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
      scsi: mpi3mr: Increase internal cmnds timeout to 60s
      scsi: mpi3mr: Do access status validation before adding devices
      scsi: mpi3mr: Add support for PCIe Managed Switch SES device
      ...

commit bd672b7559efcd3ae3faf0b0e3846e30983e8ace
Author: Claudio Suarez <cssk@net-c.es>
Date:   Thu Dec 2 10:51:12 2021 +0100

    drm: fix error found in some cases after the patch d1af5cd86997
    
    The patch d1af5cd86997 ("drm: get rid of DRM_DEBUG_* log
    calls in drm core, files drm_a*.c") fails when the drm_device
    cannot be found in the parameter plane_state->crtc.
    Fix it using plane_state->plane.
    
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Fixes: 6e22dc358377 ("drm: get rid of DRM_DEBUG_* log calls in drm core, files drm_a*.c")
    Signed-off-by: Claudio Suarez <cssk@net-c.es>
    [danvet: fix Fixes: line]
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/YaiXEARd8z2C463h@gineta.localdomain
    (cherry picked from commit 521d459b1935628a7caa0753429f880dae2dbfc9)
    Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>

commit ad783ff5a20f851c6d9bca03d12d44f98f494af7
Merge: 8f18a987ca761 69e630016ef4e
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 14 13:39:50 2022 +0100

    Merge tag 'drm-misc-next-fixes-2022-01-13' of git://anongit.freedesktop.org/drm/drm-misc into drm-next
    
     * Fix use of CRTC state's active vs enable in atomic helper
    
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    From: Thomas Zimmermann <tzimmermann@suse.de>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yd/i/zj9vEHisSSB@linux-uq9g

commit b2dfc3fe73b5b305b13467e39386f77133590ea8
Merge: 50a0f3f55e382 f5bdb34bf0c93
Author: Petr Mladek <pmladek@suse.com>
Date:   Fri Jan 14 13:36:32 2022 +0100

    Merge branch 'for-5.17/kallsyms' into for-linus

commit 8f18a987ca761583a09d8e41f9938f61480deca3
Merge: cb6846fbb83b5 6ef295e342974
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Jan 14 13:34:39 2022 +0100

    Merge tag 'drm-intel-next-fixes-2022-01-13' of git://anongit.freedesktop.org/drm/drm-intel into drm-next
    
    - Hold runtime PM wakelock during PXP unbind (Juston Li)
    - Three fixes for the TTM backend fault handling (Matthew Auld)
    - Make sure to unmap when purging in the TTM backend (Matthew Auld)
    
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/Yd/xzyCM87rfrwQT@tursulin-mobl2

commit 016017a195b86d9761e91cb052438bf71207a12f
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Mon Dec 20 11:15:22 2021 +0100

    drm/ttm: fix compilation on ARCH=um
    
    Even if it's probably not really useful, it can get selected
    by e.g. randconfig builds, and then failing to compile is an
    annoyance. Unfortunately, it's hard to fix in Kconfig, since
    DRM_TTM is selected by many things that don't really depend
    on any specific architecture, and just depend on PCI (which
    is indeed now available in ARCH=um via simulation/emulation).
    
    Fix this in the code instead by just ifdef'ing the relevant
    two lines that depend on "real X86".
    
    Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
    Link: https://patchwork.freedesktop.org/patch/msgid/20211220111519.a4c8c6eff702.Ie4cf4e68698f6a9f546b83379bc52c266504424f@changeid

commit d90d0c175cf2982789d336dda928c0f69d3e8a9d
Author: Kai-Heng Feng <kai.heng.feng@canonical.com>
Date:   Fri Jan 14 15:14:30 2022 +0800

    net: stmmac: Fix "Unbalanced pm_runtime_enable!" warning
    
    If the device is PCI based like intel-eth-pci, pm_runtime_enable() is
    already called by pci_pm_init().
    
    So only pm_runtime_enable() when it's not already enabled.
    
    Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 99218cbf81bf21355a3de61cd46a706d36e900e6
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 14 06:57:24 2022 +0000

    lib82596: Fix IRQ check in sni_82596_probe
    
    platform_get_irq() returns negative error number instead 0 on failure.
    And the doc of platform_get_irq() provides a usage example:
    
        int irq = platform_get_irq(pdev, 0);
        if (irq < 0)
            return irq;
    
    Fix the check of return value to catch errors correctly.
    
    Fixes: 115978859272 ("i825xx: Move the Intel 82586/82593/82596 based drivers")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ea938248557a52e231a31f338eac4baee36a8626
Author: Michael Ellerman <mpe@ellerman.id.au>
Date:   Fri Jan 14 14:13:16 2022 +1100

    net: apple: bmac: Fix build since dev_addr constification
    
    Since commit adeef3e32146 ("net: constify netdev->dev_addr") the bmac
    driver no longer builds with the following errors (pmac32_defconfig):
    
      linux/drivers/net/ethernet/apple/bmac.c: In function ‘bmac_probe’:
      linux/drivers/net/ethernet/apple/bmac.c:1287:20: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)j)’
       1287 |   dev->dev_addr[j] = rev ? bitrev8(addr[j]): addr[j];
            |                    ^
    
    Fix it by making the modifications to a local macaddr variable and then
    passing that to eth_hw_addr_set().
    
    We don't use the existing addr variable because the bitrev8() would
    mutate it, but it is already used unreversed later in the function.
    
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Reviewed-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6c8dc12cd925e5fa8c152633338b2b35c4c89258
Author: Michael Ellerman <mpe@ellerman.id.au>
Date:   Fri Jan 14 14:12:52 2022 +1100

    net: apple: mace: Fix build since dev_addr constification
    
    Since commit adeef3e32146 ("net: constify netdev->dev_addr") the mace
    driver no longer builds with various errors (pmac32_defconfig):
    
      linux/drivers/net/ethernet/apple/mace.c: In function ‘mace_probe’:
      linux/drivers/net/ethernet/apple/mace.c:170:20: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)j)’
        170 |   dev->dev_addr[j] = rev ? bitrev8(addr[j]): addr[j];
            |                    ^
      linux/drivers/net/ethernet/apple/mace.c: In function ‘mace_reset’:
      linux/drivers/net/ethernet/apple/mace.c:349:32: warning: passing argument 2 of ‘__mace_set_address’ discards ‘const’ qualifier from pointer target type
        349 |     __mace_set_address(dev, dev->dev_addr);
            |                             ~~~^~~~~~~~~~
      linux/drivers/net/ethernet/apple/mace.c:93:62: note: expected ‘void *’ but argument is of type ‘const unsigned char *’
         93 | static void __mace_set_address(struct net_device *dev, void *addr);
            |                                                        ~~~~~~^~~~
      linux/drivers/net/ethernet/apple/mace.c: In function ‘__mace_set_address’:
      linux/drivers/net/ethernet/apple/mace.c:388:36: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)i)’
        388 |  out_8(&mb->padr, dev->dev_addr[i] = p[i]);
            |                                    ^
    
    Fix it by making the modifications to a local macaddr variable and then
    passing that to eth_hw_addr_set(), as well as adding some missing const
    qualifiers.
    
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Reviewed-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2255634100bffe0abc1a300f20aee26980891ba4
Author: Li Zhijian <lizhijian@fujitsu.com>
Date:   Fri Jan 14 11:02:46 2022 +0800

    kselftests/net: list all available tests in usage()
    
    So that users can run/query them easily.
    
    $ ./fcnal-test.sh -h
    usage: fcnal-test.sh OPTS
    
            -4          IPv4 tests only
            -6          IPv6 tests only
            -t <test>   Test name/set to run
            -p          Pause on fail
            -P          Pause after each test
            -v          Be verbose
    
    Tests:
            ipv4_ping ipv4_tcp ipv4_udp ipv4_bind ipv4_runtime ipv4_netfilter ipv6_ping ipv6_tcp ipv6_udp ipv6_bind ipv6_runtime ipv6_netfilter use_cases
    
    Suggested-by: David Ahern <dsahern@gmail.com>
    Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0bf3885324a8599e3af4c7379b8d4f621c9bbffa
Author: Markus Reichl <m.reichl@fivetechno.de>
Date:   Thu Jan 13 21:01:11 2022 +0100

    net: usb: Correct reset handling of smsc95xx
    
    On boards with LAN9514 and no preconfigured MAC address we don't get an
    ip address from DHCP after commit a049a30fc27c ("net: usb: Correct PHY handling
    of smsc95xx") anymore. Adding an explicit reset before starting the phy
    fixes the issue.
    
    [1]
    https://lore.kernel.org/netdev/199eebbd6b97f52b9119c9fa4fd8504f8a34de18.camel@collabora.com/
    
    From: Gabriel Hojda <ghojda@yo2urs.ro>
    Fixes: a049a30fc27c ("net: usb: Correct PHY handling of smsc95xx")
    Signed-off-by: Gabriel Hojda <ghojda@yo2urs.ro>
    Signed-off-by: Markus Reichl <m.reichl@fivetechno.de>
    Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9deb48b53e7f4056c2eaa2dc2ee3338df619e4f6
Author: Sergey Shtylyov <s.shtylyov@omp.ru>
Date:   Thu Jan 13 22:46:07 2022 +0300

    bcmgenet: add WOL IRQ check
    
    The driver neglects to check the result of platform_get_irq_optional()'s
    call and blithely passes the negative error codes to devm_request_irq()
    (which takes *unsigned* IRQ #), causing it to fail with -EINVAL.
    Stop calling devm_request_irq() with the invalid IRQ #s.
    
    Fixes: 8562056f267d ("net: bcmgenet: request Wake-on-LAN interrupt")
    Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e24aeff6db738be7ce24999a41e91299b5fe14be
Author: Stephen Boyd <swboyd@chromium.org>
Date:   Fri Jan 7 15:23:05 2022 -0800

    HID: vivaldi: Minor cleanups
    
    Perform some minor cleanups on this driver. Include header files for
    struct definitions that are used, drop a forward declaration that isn't
    useful, and mark a sysfs attribute static as it isn't used outside this
    file.
    
    Cc: Sean O'Brien <seobrien@chromium.org>
    Cc: Ting Shen <phoenixshen@chromium.org>
    Signed-off-by: Stephen Boyd <swboyd@chromium.org>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit f37c3bbc635994eda203a6da4ba0f9d05165a8d6
Author: Steven Rostedt <rostedt@goodmis.org>
Date:   Thu Jan 13 20:08:40 2022 -0500

    tracing: Add ustring operation to filtering string pointers
    
    Since referencing user space pointers is special, if the user wants to
    filter on a field that is a pointer to user space, then they need to
    specify it.
    
    Add a ".ustring" attribute to the field name for filters to state that the
    field is pointing to user space such that the kernel can take the
    appropriate action to read that pointer.
    
    Link: https://lore.kernel.org/all/yt9d8rvmt2jq.fsf@linux.ibm.com/
    
    Fixes: 77360f9bbc7e ("tracing: Add test for user space strings when filtering on string pointers")
    Tested-by: Sven Schnelle <svens@linux.ibm.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 3fe6acd4dc922237b30e55473c9349c6ce0690f3
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Fri Jan 7 12:09:36 2022 -0800

    HID: vivaldi: fix handling devices not using numbered reports
    
    Unfortunately details of USB HID transport bled into HID core and
    handling of numbered/unnumbered reports is quite a mess, with
    hid_report_len() calculating the length according to USB rules,
    and hid_hw_raw_request() adding report ID to the buffer for both
    numbered and unnumbered reports.
    
    Untangling it all requres a lot of changes in HID, so for now let's
    handle this in the driver.
    
    [jkosina@suse.cz: microoptimize field->report->id to report->id]
    Fixes: 14c9c014babe ("HID: add vivaldi HID driver")
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Tested-by: Stephen Boyd <swboyd@chromium.org> # CoachZ
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 237fe8885a3fdab169bf670790c9f40046af45d3
Author: Colin Ian King <colin.king@intel.com>
Date:   Wed Jan 12 23:47:41 2022 +0000

    ata: pata_ali: remove redundant return statement
    
    A return statement is unnecessarily complicated, currently value
    in variable mask is bitwise-masked and the variable is being
    updated and then returned. Just updating the mask is all that is
    required as the following statement is a return.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit a17ab7aba5df4135ef77d7f6d7105e1ea414936f
Author: Paul Menzel <pmenzel@molgen.mpg.de>
Date:   Wed Jan 5 16:36:18 2022 +0100

    ata: ahci: Add support for AMD A85 FCH (Hudson D4)
    
    Add support for the AMD A85 FCH (Hudson D4) AHCI adapter.
    
    Since this adapter does not require the default 200 ms debounce delay
    in sata_link_resume(), create a new board board_ahci_no_debounce_delay
    with the link flag ATA_LFLAG_NO_DEBOUNCE_DELAY, and, for now, configure
    the AMD A85 FCH (Hudson D4) to use it. On the ASUS F2A85-M PRO it
    reduces the Linux kernel boot time by the expected 200 ms from 787 ms
    to 585 ms.
    
    Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Cc: Tejun Heo <tj@kernel.org>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit b9ba367c513dbc165dd6c01266a59db4be2a3564
Author: Paul Menzel <pmenzel@molgen.mpg.de>
Date:   Wed Jan 5 16:36:16 2022 +0100

    ata: libata: Rename link flag ATA_LFLAG_NO_DB_DELAY
    
    Rename the link flag ATA_LFLAG_NO_DB_DELAY to
    ATA_LFLAG_NO_DEBOUNCE_DELAY. The new name is longer, but clearer.
    
    Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 84eac327af543f03172085d5ef9f98ea25a51191
Author: Wenchao Hao <haowenchao@huawei.com>
Date:   Wed Jan 5 19:13:54 2022 -0500

    ata: libata-scsi: simplify __ata_scsi_queuecmd()
    
    This patch cleans up the code of __ata_scsi_queuecmd(). Since each
    branch of the "if" condition check that scmd->cmd_len is not zero, move
    this check out of the "if" to simplify the conditions being checked in
    the "else" branch.
    
    While at it, avoid the if-else-if-else structure using if-else if
    structure and remove the redundant rc local variable.
    
    This patch does not change the function logic.
    
    Signed-off-by: Wenchao Hao <haowenchao@huawei.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit db6a3f47cecc3da00d13fc68738aaa96e31f7c04
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Jan 5 18:17:21 2022 +0000

    ata: pata_of_platform: Use platform_get_irq_optional() to get the interrupt
    
    platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
    allocation of IRQ resources in DT core code, this causes an issue
    when using hierarchical interrupt domains using "interrupts" property
    in the node as this bypasses the hierarchical setup and messes up the
    irq chaining.
    
    In preparation for removal of static setup of IRQ resource from DT core
    code use platform_get_irq_optional().
    
    Note the code does not set the IRQ flags as this is handled
    automatically for DT.
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit b6a64a860e1319dfbabc55b351c8b6583bd67413
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:48:17 2022 +0900

    ata: pata_samsung_cf: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable SAMSUNG_DEV_IDE.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 7767c73a3565ae975e7f1de7900815be4267cc3c
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:35:57 2022 +0900

    ata: pata_pxa: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_PXA.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 7dc3c053bddf735b305bacfc620aa5cf6874ffe6
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:31:34 2022 +0900

    ata: pata_imx: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_MXC.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 2aa566716f43776aee1cb46b3bb40af67b080d06
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:24:52 2022 +0900

    ata: pata_ftide010: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARM.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit dc5d7b3cfd7833d41c2e2fad5fd5af5c95d05d04
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:19:30 2022 +0900

    ata: pata_cs5535: add compile test support
    
    Add Kconfig dependendy on X86_64 && COMPILE_TEST to allow compile tests
    with configs that do not have X86_32 enabled on X86_64 hosts.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 9c2fd3fb43bdf2641093fe287d1944ec3c88eeda
Author: Minghao Chi <chi.minghao@zte.com.cn>
Date:   Tue Jan 4 11:25:45 2022 +0000

    ata: pata_octeon_cf: remove redundant val variable
    
    Return value from DIV_ROUND_UP() directly instead
    of taking this in another redundant variable.
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Minghao Chi <chi.minghao@zte.com.cn>
    Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

commit 0561e514c944da874ccdfbe2922f71b4c333c7e1
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 17:54:18 2022 +0900

    ata: fix read_id() ata port operation interface
    
    Drivers that need to tweak a device IDENTIFY data implement the
    read_id() port operation. The IDENTIFY data buffer is passed as an
    argument to the read_id() operation for drivers to use. However, when
    this operation is called, the IDENTIFY data is not yet converted to CPU
    endian and contains le16 words.
    
    Change the interface of the read_id operation to pass a __le16 * pointer
    to the IDENTIFY data buffer to clarify the buffer endianness. Fix the
    pata_netcell, pata_it821x, ahci_xgene, ahci_ceva and ahci_brcm drivers
    implementation of this operation and modify the code to corretly deal
    with identify data words manipulation to avoid sparse warnings such as:
    
    drivers/ata/ahci_xgene.c:262:33: warning: invalid assignment: &=
    drivers/ata/ahci_xgene.c:262:33:    left side has type unsigned short
    drivers/ata/ahci_xgene.c:262:33:    right side has type restricted __le16
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 2bce69072a0db6c3444650023c6f35bfd7a23d29
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 17:49:54 2022 +0900

    ata: ahci_xgene: use correct type for port mmio address
    
    Sparse complains about an incorrect type for port_mmio pointer
    variables:
    
    drivers/ata/ahci_xgene.c:196:41: warning: incorrect type in initializer
    (different address spaces)
    drivers/ata/ahci_xgene.c:196:41:    expected void *port_mmio
    drivers/ata/ahci_xgene.c:196:41:    got void [noderef] __iomem *
    
    Fix this by declaring port_mmio as "void __iomem *" instead of "void *".
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit f8bc938ee6c60ec862fb5311789b6e277555f0b0
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 19:04:49 2022 +0900

    ata: sata_fsl: fix cmdhdr_tbl_entry and prde struct definitions
    
    The fields of the cmdhdr_tbl_entry structure all store __le32 values,
    and so are the dba and ddc_and_ext fields of the prde structure. Define
    these fields using the __le32 type to avoid sparse warnings about
    incorrect type in assignment.
    
    The debug message in sata_fsl_setup_cmd_hdr_entry() is changed to
    display the correct values of the cmdhdr_tbl_entry fields on big endian
    systems.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit e5b48ee30aec1fe6dff05e36b22e886c665b4736
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 16:14:46 2022 +0900

    ata: sata_fsl: fix scsi host initialization
    
    When compiling with W=1, the sata_fsl driver compilation throws the
    warning:
    
    drivers/ata/sata_fsl.c:1385:22: error: initialized field overwritten
    [-Werror=override-init]
     1385 |         .can_queue = SATA_FSL_QUEUE_DEPTH,
    
    This is due to the driver scsi host template initialization overwriting
    the can_queue field that is already set using the ATA_NCQ_SHT()
    initializer macro, resulting in the same field being initialized twice
    in the host template declaration.
    
    To remove this warning, introduce the ATA_SUBBASE_SHT_QD() and
    ATA_NCQ_SHT_QD() initialization macros to allow specifying a queue depth
    different from the default ATA_DEF_QUEUE using an additional argument to
    the macro.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit a3d11c275b647b5b56b907011b432e00f7ddb683
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:17:42 2022 +0900

    ata: pata_bk3710: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_DAVINCI.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit a33a348d0aca38107c435eef20c449cf13dd9447
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:11:15 2022 +0900

    ata: ahci_seattle: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_SEATTLE.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit b7c9b00fb050c6b3fea6e32f1adbe0194296eb1f
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:09:23 2022 +0900

    ata: ahci_xgene: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable PHY_XGENE.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 3d98cbf7096ea50bbb4256c7781555bb69a07e52
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:08:01 2022 +0900

    ata: ahci_tegra: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_TEGRA.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit c05b911afffa6a1842dd3bb9d54a8db178722e40
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:06:12 2022 +0900

    ata: ahci_sunxi: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_SUNXI.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 368c7edc15e5e505ab56d6caad60fd11ee2bc428
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 15:01:01 2022 +0900

    ata: ahci_mvebu: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_MVEBU.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 28a53d3160acd7e44a39a146da20e3e672fb0d96
Author: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Date:   Tue Jan 4 14:59:00 2022 +0900

    ata: ahci_mtk: add compile test support
    
    Add Kconfig dependendy on COMPILE_TEST to allow compile tests with
    configs that do not enable ARCH_MEDIATEK.
    
    Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Hannes Reinecke <hare@suse.de>

commit 5dce5904e3b9bc11d9635dd3458c7ff32caebb59
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:33 2021 +0100

    rtla: Add rtla timerlat hist documentation
    
    Man page for rtla timerlat hist mode.
    
    Link: https://lkml.kernel.org/r/4a184003fdb81e23be3fe5ec882b1c89d5a95458.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit df337d014b573fe567cd190753a4f5fa69281870
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:32 2021 +0100

    rtla: Add rtla timerlat top documentation
    
    Man page for rtla timerlat top mode.
    
    Link: https://lkml.kernel.org/r/58c3d6212e6c6f1f012deb2e998dd082da92075f.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 29380d4055e524de918c76a861df17d14a4b7224
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:31 2021 +0100

    rtla: Add rtla timerlat documentation
    
    Man page for rtla timerlat tool.
    
    Link: https://lkml.kernel.org/r/78678b8d024bf5a3a79f831ac9441b96e8d2f56e.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit e7041c6b3c123ef2160ff7a948e458f8241e4e03
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:30 2021 +0100

    rtla: Add rtla osnoise hist documentation
    
    Man page for rtla osnoise hist mode.
    
    Link: https://lkml.kernel.org/r/d43cc5d516b8db180575c4b66c4aa67c6a724a8d.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit b1be48307de4ccb315036c58bb1363a93c27d188
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:29 2021 +0100

    rtla: Add rtla osnoise top documentation
    
    Man page for rtla osnoise top mode.
    
    Link: https://lkml.kernel.org/r/445aa2173ca152fc2e68719e3c1a2547dd01efd3.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 496082df01bb08a40f9207d918734cf908c5f107
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:28 2021 +0100

    rtla: Add rtla osnoise man page
    
    Man page for rtla osnoise command.
    
    Link: https://lkml.kernel.org/r/304747c602e46f6396e3bb75dfdcb42ae3656dca.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit d40d48e1f1f25abe755521e33a67f5d2b8b9443c
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:27 2021 +0100

    rtla: Add Documentation
    
    Adds the basis for rtla documentation. This patch also
    includes the rtla(1) man page.
    
    As suggested by Jonathan Corbet, we are placing these man
    pages at Documentation/tools/rtla, using rst format. It
    is not linked to the official documentation, though.
    
    The Makefile is based on bpftool's Documentation one.
    
    Link: https://lkml.kernel.org/r/5f510f3e962fc0cd531c43f5a815544dd720c3f2.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Suggested-by: Steven Rostedt <rostedt@goodmis.org>
    Suggested-by: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 1eeb6328e8b3a917ba0be4965f272147dbd4cf55
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:26 2021 +0100

    rtla/timerlat: Add timerlat hist mode
    
    The rtla hist hist mode displays a histogram of each tracer event
    occurrence, both for IRQ and timer latencies. The tool also allows
    many configurations of the timerlat tracer and the collection of
    the tracer output.
    
    Here is one example of the rtla timerlat hist mode output:
      ---------- %< ----------
     [root@alien ~]# rtla timerlat hist -c 0-3 -d 1M
     # RTLA timerlat histogram
     # Time unit is microseconds (us)
     # Duration:   0 00:01:00
     Index   IRQ-000   Thr-000   IRQ-001   Thr-001   IRQ-002   Thr-002   IRQ-003   Thr-003
     0         58572         0     59373         0     58691         0     58895         0
     1          1422     57021       628     57241      1310     56160      1102     56805
     2             6      2931         0      2695         0      3567         4      3031
     3             1        40         0        53         0       260         0       142
     4             0         7         0         5         0         6         0        17
     5             0         2         0         5         0         7         0         4
     6             0         0         0         2         0         1         0         1
     8             0         0         0         0         0         0         0         1
     over:         0         0         0         0         0         0         0         0
     count:    60001     60001     60001     60001     60001     60001     60001     60001
     min:          0         1         0         1         0         1         0         1
     avg:          0         1         0         1         0         1         0         1
     max:          3         5         1         6         1         6         2         8
      ---------- >% ----------
    
    Running
     - rtla timerlat hist --help
    provides information about the available options.
    
    Link: https://lkml.kernel.org/r/7049ed3c46b7d6aceab18ffe7770003dfc4ddceb.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit a828cd18bc4ad72ff6d64c0dd23dc814a6741fed
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:25 2021 +0100

    rtla: Add timerlat tool and timelart top mode
    
    The rtla timerlat tool is an interface for the timerlat tracer.
    The timerlat tracer dispatches a kernel thread per-cpu. These threads set a
    periodic timer to wake themselves up and go back to sleep. After the
    wakeup, they collect and generate useful information for the debugging of
    operating system timer latency.
    
    The timerlat tracer outputs information in two ways. It periodically
    prints the timer latency at the timer IRQ handler and the Thread handler.
    It also provides information for each noise via the osnoise tracepoints.
    
    The rtla timerlat top mode displays a summary of the periodic output from
    the timerlat tracer.
    
    Here is one example of the rtla timerlat tool output:
     ---------- %< ----------
    [root@alien ~]# rtla timerlat top -c 0-3 -d 1m
                                         Timer Latency
      0 00:01:00   |          IRQ Timer Latency (us)        |         Thread Timer Latency (us)
    CPU COUNT      |      cur       min       avg       max |      cur       min       avg       max
      0 #60001     |        0         0         0         3 |        1         1         1         6
      1 #60001     |        0         0         0         3 |        2         1         1         5
      2 #60001     |        0         0         1         6 |        1         1         2         7
      3 #60001     |        0         0         0         7 |        1         1         1        11
     ---------- >% ----------
    
    Running:
      # rtla timerlat --help
      # rtla timerlat top --help
    provides information about the available options.
    
    Link: https://lkml.kernel.org/r/e95032e20c2b88c962195bf7693bb53c9ebcced8.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 829a6c0b5698c7d51aa2bcd16963fcd9de295476
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:24 2021 +0100

    rtla/osnoise: Add the hist mode
    
    The rtla osnoise hist tool collects all osnoise:sample_threshold
    occurrence in a histogram, displaying the results in a user-friendly
    way. The tool also allows many configurations of the osnoise tracer
    and the collection of the tracer output.
    
    Here is one example of the rtla osnoise hist tool output:
      ---------- %< ----------
     [root@f34 ~]# rtla osnoise hist --bucket-size 10 --entries 100 -c 0-8 -d 1M -r 9000 -P F:1
     # RTLA osnoise histogram
     # Time unit is microseconds (us)
     # Duration:   0 00:01:00
     Index   CPU-000   CPU-001   CPU-002   CPU-003   CPU-004   CPU-005   CPU-006   CPU-007   CPU-008
     0           430       434       352       455       440       463       467       436       484
     10           88        88        92       141       120       100       126       166       100
     20           19         7        12        22         8         8        13        13        16
     30            6         0         2         0         1         2         2         1         0
     50            0         0         0         0         0         0         1         0         0
     over:         0         0         0         0         0         0         0         0         0
     count:      543       529       458       618       569       573       609       616       600
     min:          0         0         0         0         0         0         0         0         0
     avg:          0         0         0         0         0         0         0         0         0
     max:         30        20        30        20        30        30        50        30        20
      ---------- >% ----------
    
    Running
     - rtla osnoise hist --help
    
    provides information about the available options.
    
    Link: https://lkml.kernel.org/r/c68060544de89b8b62510ed91c7369f162eb465b.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 1eceb2fc2ca549a170d7ee7cd1fde2daeda646ac
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:23 2021 +0100

    rtla/osnoise: Add osnoise top mode
    
    The rtla osnoise tool is an interface for the osnoise tracer. The
    osnoise tracer dispatches a kernel thread per-cpu. These threads read
    the time in a loop while with preemption, softirqs and IRQs enabled,
    thus allowing all the sources of osnoise during its execution. The
    osnoise threads take note of the entry and exit point of any source
    of interferences, increasing a per-cpu interference counter. The
    osnoise tracer also saves an interference counter for each source
    of interference.
    
    The rtla osnoise top mode displays information about the periodic
    summary from the osnoise tracer.
    
    One example of rtla osnoise top output is:
    
    [root@alien ~]# rtla osnoise top -c 0-3 -d 1m -q -r 900000 -P F:1
                                             Operating System Noise
    duration:   0 00:01:00 | time is in us
    CPU Period       Runtime        Noise  % CPU Aval   Max Noise   Max Single          HW          NMI          IRQ      Softirq       Thread
      0 #58         52200000         1031    99.99802          91           60           0            0        52285            0          101
      1 #59         53100000            5    99.99999           5            5           0            9        53122            0           18
      2 #59         53100000            7    99.99998           7            7           0            8        53115            0           18
      3 #59         53100000         8274    99.98441         277           23           0            9        53778            0          660
    
    "rtla osnoise top --help" works and provide information about the
    available options.
    
    Link: https://lkml.kernel.org/r/0d796993abf587ae5a170bb8415c49368d4999e1.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 0605bf009f18d558758df9edef59698bf1389b28
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:22 2021 +0100

    rtla: Add osnoise tool
    
    The osnoise tool is the interface for the osnoise tracer. The osnoise
    tool will have multiple "modes" with different outputs. At this point,
    no mode is included.
    
    The osnoise.c includes the osnoise_context abstraction. It serves to
    read-save-change-restore the default values from tracing/osnoise/
    directory. When the context is deleted, the default values are restored.
    
    It also includes some other helper functions for managing osnoise
    tracer sessions.
    
    With these bits and pieces in place, we can start adding some
    functionality to rtla.
    
    Link: https://lkml.kernel.org/r/2d44c21ff561f503b4c7b1813892761818118460.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit b1696371d865fa28bd20adb13d1820ef031f2ee2
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:21 2021 +0100

    rtla: Helper functions for rtla
    
    This is a set of utils and tracer helper functions. They are used by
    rtla mostly to parse config, display data and some trace operations that
    are not part of libtracefs (because they are only useful it for this
    case).
    
    Link: https://lkml.kernel.org/r/a94c128aba9e6e66d502b7094f2e8c7ac95b12e5.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 79ce8f43ac5ac16d6d63729e858da42b0460d87b
Author: Daniel Bristot de Oliveira <bristot@kernel.org>
Date:   Fri Dec 10 19:11:20 2021 +0100

    rtla: Real-Time Linux Analysis tool
    
    The rtla is a meta-tool that includes a set of commands that aims
    to analyze the real-time properties of Linux. But instead of testing
    Linux as a black box, rtla leverages kernel tracing capabilities to
    provide precise information about the properties and root causes of
    unexpected results.
    
    rtla --help works and provide information about the available options.
    
    This is just the "main" and the Makefile, no function yet.
    
    Link: https://lkml.kernel.org/r/bf9118ed43a09e6c054c9a491cbe7411ad1acd89.1639158831.git.bristot@kernel.org
    
    Cc: Tao Zhou <tao.zhou@linux.dev>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Juri Lelli <juri.lelli@redhat.com>
    Cc: Clark Williams <williams@redhat.com>
    Cc: John Kacur <jkacur@redhat.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
    Cc: linux-rt-users@vger.kernel.org
    Cc: linux-trace-devel@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 0878355b51f5f26632e652c848a8e174bb02d22d
Author: Nikita Yushchenko <nikita.yushchenko@virtuozzo.com>
Date:   Sun Jan 9 18:34:59 2022 +0300

    tracing/osnoise: Properly unhook events if start_per_cpu_kthreads() fails
    
    If start_per_cpu_kthreads() called from osnoise_workload_start() returns
    error, event hooks are left in broken state: unhook_irq_events() called
    but unhook_thread_events() and unhook_softirq_events() not called, and
    trace_osnoise_callback_enabled flag not cleared.
    
    On the next tracer enable, hooks get not installed due to
    trace_osnoise_callback_enabled flag.
    
    And on the further tracer disable an attempt to remove non-installed
    hooks happened, hitting a WARN_ON_ONCE() in tracepoint_remove_func().
    
    Fix the error path by adding the missing part of cleanup.
    While at this, introduce osnoise_unhook_events() to avoid code
    duplication between this error path and normal tracer disable.
    
    Link: https://lkml.kernel.org/r/20220109153459.3701773-1-nikita.yushchenko@virtuozzo.com
    
    Cc: stable@vger.kernel.org
    Fixes: bce29ac9ce0b ("trace: Add osnoise tracer")
    Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
    Signed-off-by: Nikita Yushchenko <nikita.yushchenko@virtuozzo.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 6e1b4bd1911d814077d77e2ac6529d74ee68c0f6
Author: Yuntao Wang <ytcoode@gmail.com>
Date:   Mon Jan 10 00:22:32 2022 +0800

    tracing: Remove duplicate warnings when calling trace_create_file()
    
    Since the same warning message is already printed in the
    trace_create_file() function, there is no need to print it again.
    
    Link: https://lkml.kernel.org/r/20220109162232.361747-1-ytcoode@gmail.com
    
    Signed-off-by: Yuntao Wang <ytcoode@gmail.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit dfea08a2116fe327f79d8f4d4b2cf6e0c88be11f
Author: Xiangyang Zhang <xyz.sun.ok@gmail.com>
Date:   Fri Jan 7 23:02:42 2022 +0800

    tracing/kprobes: 'nmissed' not showed correctly for kretprobe
    
    The 'nmissed' column of the 'kprobe_profile' file for kretprobe is
    not showed correctly, kretprobe can be skipped by two reasons,
    shortage of kretprobe_instance which is counted by tk->rp.nmissed,
    and kprobe itself is missed by some reason, so to show the sum.
    
    Link: https://lkml.kernel.org/r/20220107150242.5019-1-xyz.sun.ok@gmail.com
    
    Cc: stable@vger.kernel.org
    Fixes: 4a846b443b4e ("tracing/kprobes: Cleanup kprobe tracer code")
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Signed-off-by: Xiangyang Zhang <xyz.sun.ok@gmail.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 77360f9bbc7e5e2ab7a2c8b4c0244fbbfcfc6f62
Author: Steven Rostedt <rostedt@goodmis.org>
Date:   Mon Jan 10 11:55:32 2022 -0500

    tracing: Add test for user space strings when filtering on string pointers
    
    Pingfan reported that the following causes a fault:
    
      echo "filename ~ \"cpu\"" > events/syscalls/sys_enter_openat/filter
      echo 1 > events/syscalls/sys_enter_at/enable
    
    The reason is that trace event filter treats the user space pointer
    defined by "filename" as a normal pointer to compare against the "cpu"
    string. The following bug happened:
    
     kvm-03-guest16 login: [72198.026181] BUG: unable to handle page fault for address: 00007fffaae8ef60
     #PF: supervisor read access in kernel mode
     #PF: error_code(0x0001) - permissions violation
     PGD 80000001008b7067 P4D 80000001008b7067 PUD 2393f1067 PMD 2393ec067 PTE 8000000108f47867
     Oops: 0001 [#1] PREEMPT SMP PTI
     CPU: 1 PID: 1 Comm: systemd Kdump: loaded Not tainted 5.14.0-32.el9.x86_64 #1
     Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
     RIP: 0010:strlen+0x0/0x20
     Code: 48 89 f9 74 09 48 83 c1 01 80 39 00 75 f7 31 d2 44 0f b6 04 16 44 88 04 11
           48 83 c2 01 45 84 c0 75 ee c3 0f 1f 80 00 00 00 00 <80> 3f 00 74 10 48 89 f8
           48 83 c0 01 80 38 00 75 f7 48 29 f8 c3 31
     RSP: 0018:ffffb5b900013e48 EFLAGS: 00010246
     RAX: 0000000000000018 RBX: ffff8fc1c49ede00 RCX: 0000000000000000
     RDX: 0000000000000020 RSI: ffff8fc1c02d601c RDI: 00007fffaae8ef60
     RBP: 00007fffaae8ef60 R08: 0005034f4ddb8ea4 R09: 0000000000000000
     R10: ffff8fc1c02d601c R11: 0000000000000000 R12: ffff8fc1c8a6e380
     R13: 0000000000000000 R14: ffff8fc1c02d6010 R15: ffff8fc1c00453c0
     FS:  00007fa86123db40(0000) GS:ffff8fc2ffd00000(0000) knlGS:0000000000000000
     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
     CR2: 00007fffaae8ef60 CR3: 0000000102880001 CR4: 00000000007706e0
     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
     PKRU: 55555554
     Call Trace:
      filter_pred_pchar+0x18/0x40
      filter_match_preds+0x31/0x70
      ftrace_syscall_enter+0x27a/0x2c0
      syscall_trace_enter.constprop.0+0x1aa/0x1d0
      do_syscall_64+0x16/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
     RIP: 0033:0x7fa861d88664
    
    The above happened because the kernel tried to access user space directly
    and triggered a "supervisor read access in kernel mode" fault. Worse yet,
    the memory could not even be loaded yet, and a SEGFAULT could happen as
    well. This could be true for kernel space accessing as well.
    
    To be even more robust, test both kernel and user space strings. If the
    string fails to read, then simply have the filter fail.
    
    Note, TASK_SIZE is used to determine if the pointer is user or kernel space
    and the appropriate strncpy_from_kernel/user_nofault() function is used to
    copy the memory. For some architectures, the compare to TASK_SIZE may always
    pick user space or kernel space. If it gets it wrong, the only thing is that
    the filter will fail to match. In the future, this needs to be fixed to have
    the event denote which should be used. But failing a filter is much better
    than panicing the machine, and that can be solved later.
    
    Link: https://lore.kernel.org/all/20220107044951.22080-1-kernelfans@gmail.com/
    Link: https://lkml.kernel.org/r/20220110115532.536088fd@gandalf.local.home
    
    Cc: stable@vger.kernel.org
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Reported-by: Pingfan Liu <kernelfans@gmail.com>
    Tested-by: Pingfan Liu <kernelfans@gmail.com>
    Fixes: 87a342f5db69d ("tracing/filters: Support filtering for char * strings")
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 6840f9094f2bd788a316d8cb0a4e42538d3e47dd
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Thu Jan 13 16:44:19 2022 -0500

    pagevec: Initialise folio_batch->percpu_pvec_drained
    
    When UBSAN is enabled, it reports an invalid value in __pagevec_release()
    when accessing pvec->percpu_pvec_drained, which is simply whatever
    garbage was on the stack.  Initialise it when initialising the rest of
    the folio_batch.
    
    Fixes: 10331795fb79 ("pagevec: Add folio_batch")
    Reported-by: Randy Dunlap <rdunlap@infradead.org>
    Tested-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>

commit 3e2a56e6f639492311e0a8533f0a7aed60816308
Author: Steven Rostedt <rostedt@goodmis.org>
Date:   Fri Jan 7 17:56:56 2022 -0500

    tracing: Have syscall trace events use trace_event_buffer_lock_reserve()
    
    Currently, the syscall trace events call trace_buffer_lock_reserve()
    directly, which means that it misses out on some of the filtering
    optimizations provided by the helper function
    trace_event_buffer_lock_reserve(). Have the syscall trace events call that
    instead, as it was missed when adding the update to use the temp buffer
    when filtering.
    
    Link: https://lkml.kernel.org/r/20220107225839.823118570@goodmis.org
    
    Cc: stable@vger.kernel.org
    Cc: Ingo Molnar <mingo@kernel.org>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Tom Zanussi <zanussi@kernel.org>
    Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
    Fixes: 0fc1b09ff1ff4 ("tracing: Use temp buffer when filtering events")
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit ecbe794e777aab99de3b753110801a9cda747d2d
Author: Geliang Tang <geliang.tang@suse.com>
Date:   Wed Dec 22 19:00:25 2021 +0800

    tracing: Fix mismatched comment in __string_len
    
    Here __assign_str_len() should be used for the __string_len type, instead
    of __assign_str() in the comment.
    
    Link: https://lkml.kernel.org/r/5c012db463392d0e6d4f0636203d778962ad060a.1640170494.git.geliang.tang@suse.com
    
    Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
    Fixes: 883b4aee4dec6 ("tracing: Add trace_event helper macros __string_len() and __assign_str_len()")
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 8147dc78e6e4b645f8277bdf377f2193ddfcdee1
Author: Steven Rostedt (VMware) <rostedt@goodmis.org>
Date:   Mon Dec 6 15:18:58 2021 -0500

    ftrace: Add test to make sure compiled time sorts work
    
    Now that ftrace function pointers are sorted at compile time, add a test
    that makes sure they are sorted at run time. This test is only run if it is
    configured in.
    
    Link: https://lkml.kernel.org/r/20211206151858.4d21a24d@gandalf.local.home
    
    Cc: Yinan Liu <yinan@linux.alibaba.com>
    Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

commit 72b3942a173c387b27860ba1069636726e208777
Author: Yinan Liu <yinan@linux.alibaba.com>
Date:   Sun Dec 12 19:33:58 2021 +0800

    scripts: ftrace - move the sort-processing in ftrace_init
    
    When the kernel starts, the initialization of ftrace takes
    up a portion of the time (approximately 6~8ms) to sort mcount
    addresses. We can save this time by moving mcount-sorting to
    compile time.
    
    Link: https://lkml.kernel.org/r/20211212113358.34208-2-yinan@linux.alibaba.com
    
    Signed-off-by: Yinan Liu <yinan@linux.alibaba.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 1c1857d400355e96f0fe8b32adc6fa7594d03b52
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Tue Dec 14 10:26:46 2021 +0800

    tracing/probes: check the return value of kstrndup() for pbuf
    
    kstrndup() is a memory allocation-related function, it returns NULL when
    some internal memory errors happen. It is better to check the return
    value of it so to catch the memory error in time.
    
    Link: https://lkml.kernel.org/r/tencent_4D6E270731456EB88712ED7F13883C334906@qq.com
    
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Fixes: a42e3c4de964 ("tracing/probe: Add immediate string parameter support")
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 8c7224245557707c613f130431cafbaaa4889615
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Tue Dec 14 09:28:02 2021 +0800

    tracing/uprobes: Check the return value of kstrdup() for tu->filename
    
    kstrdup() returns NULL when some internal memory errors happen, it is
    better to check the return value of it so to catch the memory error in
    time.
    
    Link: https://lkml.kernel.org/r/tencent_3C2E330722056D7891D2C83F29C802734B06@qq.com
    
    Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
    Fixes: 33ea4b24277b ("perf/core: Implement the 'perf_uprobe' PMU")
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 289e7b0f7eb47b87a0441e6c81336316f301eb39
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Mon Dec 13 11:08:53 2021 +0100

    tracing: Account bottom half disabled sections.
    
    Disabling only bottom halves via local_bh_disable() disables also
    preemption but this remains invisible to tracing. On a CONFIG_PREEMPT
    kernel one might wonder why there is no scheduling happening despite the
    N flag in the trace. The reason might be the a rcu_read_lock_bh()
    section.
    
    Add a 'b' to the tracing output if in task context with disabled bottom
    halves.
    
    Link: https://lkml.kernel.org/r/YbcbtdtC/bjCKo57@linutronix.de
    
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 818d9150f2b22a0053bf568fa11ad3be804ce5c4
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 11 10:25:29 2022 +0300

    clk: visconti: Fix uninitialized variable in printk
    
    The "pll_clck" variable is uninitialized.  The "ret" error code was
    supposed to be printed instead.
    
    Fixes: b4cbe606dc36 ("clk: visconti: Add support common clock driver and reset driver")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220111072529.GJ11243@kili
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 49a8f2bc8d88702783c7e163ec84374e9a022f71
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Wed Jan 12 14:38:16 2022 -0600

    clk: si5341: Fix clock HW provider cleanup
    
    The call to of_clk_add_hw_provider was not undone on remove or on probe
    failure, which could cause an oops on a subsequent attempt to retrieve
    clocks for the removed device. Switch to the devm version of the
    function to avoid this issue.
    
    Fixes: 3044a860fd09 ("clk: Add Si5341/Si5340 driver")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220112203816.1784610-1-robert.hancock@calian.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit a6431e351c6ec5bb6800787d259b343088f369a3
Author: Colin Ian King <colin.king@intel.com>
Date:   Thu Jan 13 00:05:45 2022 +0000

    aoe: remove redundant assignment on variable n
    
    The variable n is being bit-wise or'd with a value and reassigned
    before being returned. The update of n is redundant, replace
    the |= operator with | instead. Cleans up clang scan warning:
    
    drivers/block/aoe/aoecmd.c:125:9: warning: Although the value stored
    to 'n' is used in the enclosing expression, the value is never
    actually read from 'n' [deadcode.DeadStores]
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Link: https://lore.kernel.org/r/20220113000545.1307091-1-colin.i.king@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 413ec8057bc3d368574abd05dd27e747063b2f59
Author: Colin Ian King <colin.king@intel.com>
Date:   Thu Jan 13 00:14:32 2022 +0000

    loop: remove redundant initialization of pointer node
    
    The pointer node is being initialized with a value that is never
    read, it is being re-assigned the same value a little futher on.
    Remove the redundant initialization. Cleans up clang scan warning:
    
    drivers/block/loop.c:823:19: warning: Value stored to 'node' during
    its initialization is never read [deadcode.DeadStores]
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Link: https://lore.kernel.org/r/20220113001432.1331871-1-colin.i.king@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 180dccb0dba4f5e84a4a70c1be1d34cbb6528b32
Author: Laibin Qiu <qiulaibin@huawei.com>
Date:   Thu Jan 13 10:55:36 2022 +0800

    blk-mq: fix tag_get wait task can't be awakened
    
    In case of shared tags, there might be more than one hctx which
    allocates from the same tags, and each hctx is limited to allocate at
    most:
            hctx_max_depth = max((bt->sb.depth + users - 1) / users, 4U);
    
    tag idle detection is lazy, and may be delayed for 30sec, so there
    could be just one real active hctx(queue) but all others are actually
    idle and still accounted as active because of the lazy idle detection.
    Then if wake_batch is > hctx_max_depth, driver tag allocation may wait
    forever on this real active hctx.
    
    Fix this by recalculating wake_batch when inc or dec active_queues.
    
    Fixes: 0d2602ca30e41 ("blk-mq: improve support for shared tags maps")
    Suggested-by: Ming Lei <ming.lei@redhat.com>
    Suggested-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Laibin Qiu <qiulaibin@huawei.com>
    Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Link: https://lore.kernel.org/r/20220113025536.1479653-1-qiulaibin@huawei.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit c84b8a3fef663933007e885535591b9d30bdc860
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Fri Jan 14 00:20:05 2022 +0800

    io_uring: Remove unused function req_ref_put
    
    Fix the following clang warnings:
    
    fs/io_uring.c:1195:20: warning: unused function 'req_ref_put'
    [-Wunused-function].
    
    Fixes: aa43477b0402 ("io_uring: poll rework")
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Link: https://lore.kernel.org/r/20220113162005.3011-1-jiapeng.chong@linux.alibaba.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit fb3b0673b7d5b477ed104949450cd511337ba3c6
Merge: 747c19eb7539b 869b6ca39c08c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 13 11:19:07 2022 -0800

    Merge tag 'mailbox-v5.17' of git://git.linaro.org/landing-teams/working/fujitsu/integration
    
    Pull mailbox updates from Jassi Brar:
    
     - qcom: misc updates to qcom-ipcc driver
    
     - mpfs: change compatible string
    
     - pcc:
         - fix handling of subtypes
         - avoid uninitialized variable
    
     - mtk:
         - add missing of_node_put
         - enable control_by_sw
         - silent probe-defer prints
         - fix gce_num for mt8192
    
     - zynq: add missing of_node_put
    
     - imx: check for NULL instead of IS_ERR
    
     - appple: switch to generic compatibles
    
     - hi3660: convert comments to kernel-doc notation
    
    * tag 'mailbox-v5.17' of git://git.linaro.org/landing-teams/working/fujitsu/integration:
      dt-bindings: mailbox: Add more protocol and client ID
      mailbox: qcom-ipcc: Support interrupt wake up from suspend
      mailbox: qcom-ipcc: Support more IPCC instance
      mailbox: qcom-ipcc: Dynamic alloc for channel arrangement
      mailbox: change mailbox-mpfs compatible string
      mailbox: pcc: Handle all PCC subtypes correctly in pcc_mbox_irq
      mailbox: pcc: Avoid using the uninitialized variable 'dev'
      mailbox: mtk: add missing of_node_put before return
      mailbox: zynq: add missing of_node_put before return
      mailbox: imx: Fix an IS_ERR() vs NULL bug
      mailbox: hi3660: convert struct comments to kernel-doc notation
      mailbox: add control_by_sw for mt8195
      mailbox: mtk-cmdq: Silent EPROBE_DEFER errors for clks
      mailbox: fix gce_num of mt8192 driver data
      mailbox: apple: Bind to generic compatibles
      dt-bindings: mailbox: apple,mailbox: Add generic and t6000 compatibles

commit 747c19eb7539b5e6bb15ed57a0a14ebf9f3adb8e
Merge: feb7a43de5ef6 c0fe82baaeb27
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 13 11:09:11 2022 -0800

    Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma
    
    Pull rdma updates from Jason Gunthorpe:
     "Another small cycle. Mostly cleanups and bug fixes, quite a bit
      assisted from bots. There are a few new syzkaller splats that haven't
      been solved yet but they should get into the rcs in a few weeks, I
      think.
    
      Summary:
    
       - Update drivers to use common helpers for GUIDs, pkeys, bitmaps,
         memset_startat, and others
    
       - General code cleanups from bots
    
       - Simplify some of the rxe pool code in preparation for a larger
         rework
    
       - Clean out old stuff from hns, including all support for hip06
         devices
    
       - Fix a bug where GID table entries could be missed if the table had
         holes in it
    
       - Rename paths and sessions in rtrs for better understandability
    
       - Consolidate the roce source port selection code
    
       - NDR speed support in mlx5"
    
    * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma: (83 commits)
      RDMA/irdma: Remove the redundant return
      RDMA/rxe: Use the standard method to produce udp source port
      RDMA/irdma: Make the source udp port vary
      RDMA/hns: Replace get_udp_sport with rdma_get_udp_sport
      RDMA/core: Calculate UDP source port based on flow label or lqpn/rqpn
      IB/qib: Fix typos
      RDMA/rtrs-clt: Rename rtrs_clt to rtrs_clt_sess
      RDMA/rtrs-srv: Rename rtrs_srv to rtrs_srv_sess
      RDMA/rtrs-clt: Rename rtrs_clt_sess to rtrs_clt_path
      RDMA/rtrs-srv: Rename rtrs_srv_sess to rtrs_srv_path
      RDMA/rtrs: Rename rtrs_sess to rtrs_path
      RDMA/hns: Modify the hop num of HIP09 EQ to 1
      IB/iser: Align coding style across driver
      IB/iser: Remove un-needed casting to/from void pointer
      IB/iser: Don't suppress send completions
      IB/iser: Rename ib_ret local variable
      IB/iser: Fix RNR errors
      IB/iser: Remove deprecated pi_guard module param
      IB/mlx5: Expose NDR speed through MAD
      RDMA/cxgb4: Set queue pair state when being queried
      ...

commit fb80445c438c78b40b547d12b8d56596ce4ccfeb
Author: Kevin Bracey <kevin@bracey.fi>
Date:   Wed Jan 12 19:02:10 2022 +0200

    net_sched: restore "mpu xxx" handling
    
    commit 56b765b79e9a ("htb: improved accuracy at high rates") broke
    "overhead X", "linklayer atm" and "mpu X" attributes.
    
    "overhead X" and "linklayer atm" have already been fixed. This restores
    the "mpu X" handling, as might be used by DOCSIS or Ethernet shaping:
    
        tc class add ... htb rate X overhead 4 mpu 64
    
    The code being fixed is used by htb, tbf and act_police. Cake has its
    own mpu handling. qdisc_calculate_pkt_len still uses the size table
    containing values adjusted for mpu by user space.
    
    iproute2 tc has always passed mpu into the kernel via a tc_ratespec
    structure, but the kernel never directly acted on it, merely stored it
    so that it could be read back by `tc class show`.
    
    Rather, tc would generate length-to-time tables that included the mpu
    (and linklayer) in their construction, and the kernel used those tables.
    
    Since v3.7, the tables were no longer used. Along with "mpu", this also
    broke "overhead" and "linklayer" which were fixed in 01cb71d2d47b
    ("net_sched: restore "overhead xxx" handling", v3.10) and 8a8e3d84b171
    ("net_sched: restore "linklayer atm" handling", v3.11).
    
    "overhead" was fixed by simply restoring use of tc_ratespec::overhead -
    this had originally been used by the kernel but was initially omitted
    from the new non-table-based calculations.
    
    "linklayer" had been handled in the table like "mpu", but the mode was
    not originally passed in tc_ratespec. The new implementation was made to
    handle it by getting new versions of tc to pass the mode in an extended
    tc_ratespec, and for older versions of tc the table contents were analysed
    at load time to deduce linklayer.
    
    As "mpu" has always been given to the kernel in tc_ratespec,
    accompanying the mpu-based table, we can restore system functionality
    with no userspace change by making the kernel act on the tc_ratespec
    value.
    
    Fixes: 56b765b79e9a ("htb: improved accuracy at high rates")
    Signed-off-by: Kevin Bracey <kevin@bracey.fi>
    Cc: Eric Dumazet <edumazet@google.com>
    Cc: Jiri Pirko <jiri@resnulli.us>
    Cc: Vimalkumar <j.vimal@gmail.com>
    Link: https://lore.kernel.org/r/20220112170210.1014351-1-kevin@bracey.fi
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d72d69abfdb6e0375981cfdda8eb45143f12c77d
Author: Siva Mullati <siva.mullati@intel.com>
Date:   Fri Jan 7 15:22:35 2022 +0530

    drm/i915/gvt: Make DRM_I915_GVT depend on X86
    
    GVT is not supported on non-x86 platforms, So add
    dependency of X86 on config parameter DRM_I915_GVT.
    
    Fixes: 0ad35fed618c ("drm/i915: gvt: Introduce the basic architecture of GVT-g")
    Signed-off-by: Siva Mullati <siva.mullati@intel.com>
    Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>
    Link: http://patchwork.freedesktop.org/patch/msgid/20220107095235.243448-1-siva.mullati@intel.com
    Reviewed-by: Zhi Wang <zhi.a.wang@intel.com>
    Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>

commit 91c64a4f1cb01cf0ec50f0372ff8ca9d3022b7d0
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sat Oct 2 22:23:34 2021 -0700

    drm/i915/gvt: clean up kernel-doc in gtt.c
    
    Fix kernel-doc warnings in gtt.c:
    
    gtt.c:1152: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
     * Check if can do 2M page
    gtt.c:1152: warning: missing initial short description on line:
     * Check if can do 2M page
    gtt.c:2209: warning: expecting prototype for intel_vgpu_emulate_gtt_mmio_read(). Prototype was for intel_vgpu_emulate_ggtt_mmio_read() instead
    
    Fixes: a752b070a678 ("drm/i915/gvt: Fix function comment doc errors")
    Fixes: 2707e4446688 ("drm/i915/gvt: vGPU graphics memory virtualization")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Zhenyu Wang <zhenyuw@linux.intel.com>
    Cc: Zhi Wang <zhi.a.wang@intel.com>
    Cc: Colin Xu <colin.xu@intel.com>
    Cc: Jani Nikula <jani.nikula@linux.intel.com>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Cc: intel-gfx@lists.freedesktop.org
    Cc: intel-gvt-dev@lists.freedesktop.org
    Cc: dri-devel@lists.freedesktop.org
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>
    Link: http://patchwork.freedesktop.org/patch/msgid/20211003052334.15764-1-rdunlap@infradead.org
    Reviewed-by: Zhi Wang <zhi.a.wang@intel.com>
    Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>

commit c4d7f40b250c1a4d74ed259e84807f58032507b6
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Jan 10 03:15:29 2022 +0900

    kbuild: add cmd_file_size
    
    Some architectures support self-extracting kernel, which embeds the
    compressed vmlinux.
    
    It has 4 byte data at the end so the decompressor can know the vmlinux
    size beforehand.
    
    GZIP natively has it in the trailer, but for the other compression
    algorithms, the hand-crafted trailer is added.
    
    It is unneeded to generate such _corrupted_ compressed files because
    it is possible to pass the size data as a separate file.
    
    For example, the assembly code:
    
         .incbin "compressed-vmlinux-with-size-data"
    
    can be transformed to:
    
         .incbin "compressed-vmlinux"
         .incbin "size-data"
    
    My hope is, after some reworks of the decompressors, the macros
    cmd_{bzip2,lzma,lzo,lz4,xzkern,zstd22}_with_size will go away.
    
    This new macro, cmd_file_size, will be useful to generate a separate
    size-data file.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 53e7b5dfb752399cd903ecb6e921dcaef57c8ea5
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Jan 10 03:15:28 2022 +0900

    arch: decompressor: remove useless vmlinux.bin.all-y
    
    Presumably, arch/{parisc,s390,sh}/boot/compressed/Makefile copied
    arch/x86/boot/compressed/Makefile, but vmlinux.bin.all-y is useless
    here because it is the same as $(obj)/vmlinux.bin.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 7ce7e984ab2b218d6e92d5165629022fe2daf9ee
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Jan 10 03:15:27 2022 +0900

    kbuild: rename cmd_{bzip2,lzma,lzo,lz4,xzkern,zstd22}
    
    GZIP-compressed files end with 4 byte data that represents the size
    of the original input. The decompressors (the self-extracting kernel)
    exploit it to know the vmlinux size beforehand. To mimic the GZIP's
    trailer, Kbuild provides cmd_{bzip2,lzma,lzo,lz4,xzkern,zstd22}.
    Unfortunately these macros are used everywhere despite the appended
    size data is only useful for the decompressors.
    
    There is no guarantee that such hand-crafted trailers are safely ignored.
    In fact, the kernel refuses compressed initramdfs with the garbage data.
    That is why usr/Makefile overrides size_append to make it no-op.
    
    To limit the use of such broken compressed files, this commit renames
    the existing macros as follows:
    
      cmd_bzip2   --> cmd_bzip2_with_size
      cmd_lzma    --> cmd_lzma_with_size
      cmd_lzo     --> cmd_lzo_with_size
      cmd_lz4     --> cmd_lz4_with_size
      cmd_xzkern  --> cmd_xzkern_with_size
      cmd_zstd22  --> cmd_zstd22_with_size
    
    To keep the decompressors working, I updated the following Makefiles
    accordingly:
    
      arch/arm/boot/compressed/Makefile
      arch/h8300/boot/compressed/Makefile
      arch/mips/boot/compressed/Makefile
      arch/parisc/boot/compressed/Makefile
      arch/s390/boot/compressed/Makefile
      arch/sh/boot/compressed/Makefile
      arch/x86/boot/compressed/Makefile
    
    I reused the current macro names for the normal usecases; they produce
    the compressed data in the proper format.
    
    I did not touch the following:
    
      arch/arc/boot/Makefile
      arch/arm64/boot/Makefile
      arch/csky/boot/Makefile
      arch/mips/boot/Makefile
      arch/riscv/boot/Makefile
      arch/sh/boot/Makefile
      kernel/Makefile
    
    This means those Makefiles will stop appending the size data.
    
    I dropped the 'override size_append' hack from usr/Makefile.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 64d8aaa4ef388b22372de4dc9ce3b9b3e5f45b6c
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Jan 10 03:15:26 2022 +0900

    kbuild: drop $(size_append) from cmd_zstd
    
    The appended file size is only used by the decompressors, which some
    architectures support.
    
    As the comment "zstd22 is used for kernel compression" says, cmd_zstd22
    is used in arch/{mips,s390,x86}/boot/compressed/Makefile.
    
    On the other hand, there is no good reason to append the file size to
    cmd_zstd since it is used for other purposes.
    
    Actually cmd_zstd is only used in usr/Makefile, where the appended file
    size is rather harmful.
    
    The initramfs with its file size appended is considered as corrupted
    data, so commit 65e00e04e5ae ("initramfs: refactor the initramfs build
    rules") added 'override size_append := :' to make it no-op.
    
    As a conclusion, this $(size_append) should not exist here.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 82977af93a0dc4e70f60ca2137b67f65ebe47fc7
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Jan 10 03:15:25 2022 +0900

    sh: rename suffix-y to suffix_y
    
    'export suffix-y' does not work reliably because hyphens are disallowed
    in shell variables.
    
    A similar issue was fixed by commit 2bfbe7881ee0 ("kbuild: Do not use
    hyphen in exported variable name").
    
    If I do similar in dash, ARCH=sh fails to build.
    
      $ mv linux linux~
      $ cd linux~
      $ dash
      $ make O=foo/bar ARCH=sh CROSS_COMPILE=sh4-linux-gnu- defconfig all
      make[1]: Entering directory '/home/masahiro/linux~/foo/bar'
        [ snip ]
      make[4]: *** No rule to make target 'arch/sh/boot/compressed/vmlinux.bin.', needed by 'arch/sh/boot/compressed/piggy.o'.  Stop.
      make[3]: *** [/home/masahiro/linux~/arch/sh/boot/Makefile:40: arch/sh/boot/compressed/vmlinux] Error 2
      make[2]: *** [/home/masahiro/linux~/arch/sh/Makefile:194: zImage] Error 2
      make[1]: *** [/home/masahiro/linux~/Makefile:350: __build_one_by_one] Error 2
      make[1]: Leaving directory '/home/masahiro/linux~/foo/bar'
      make: *** [Makefile:219: __sub-make] Error 2
    
    The maintainer of GNU Make stated that there is no consistent way to
    export variables that do not meet the shell's naming criteria.
    (https://savannah.gnu.org/bugs/?55719)
    
    Consequently, you cannot use hyphens in exported variables.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit a6fadfd757ceb2f206948b1b54b9c13e77292644
Author: Kyoungkyu Park <choryu.park@choryu.space>
Date:   Thu Jan 13 13:17:08 2022 +0900

    net: qmi_wwan: Add Hucom Wireless HM-211S/K
    
    The Hucom Wireless HM-211S/K is an LTE module based on Qualcomm MDM9207.
    This module supports LTE Band 1, 3, 5, 7, 8 and WCDMA Band 1.
    
    Manual testing showed that only interface
    number two replies to QMI messages.
    
    T:  Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
    D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
    P:  Vendor=22de ProdID=9051 Rev= 3.18
    S:  Manufacturer=Android
    S:  Product=Android
    S:  SerialNumber=0123456789ABCDEF
    C:* #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA
    I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
    E:  Ad=83(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
    E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    E:  Ad=85(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
    E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
    E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
    
    Signed-off-by: Kyoungkyu Park <choryu.park@choryu.space>
    Acked-by: Bjørn Mork <bjorn@mork.no>
    Link: https://lore.kernel.org/r/Yd+nxAA6KorDpQFv@choryu-tfx5470h
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c0fe82baaeb2719f910359684c0817057f79a84a
Merge: c40238e3b8c98 df0cc57e057f1
Author: Jason Gunthorpe <jgg@ziepe.ca>
Date:   Thu Jan 13 13:21:03 2022 -0400

    Merge tag 'v5.16' into rdma.git for-next
    
    To resolve minor conflict in:
            drivers/infiniband/hw/mlx5/mlx5_ib.h
    
    By merging both hunks.
    
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit feb7a43de5ef625ad74097d8fd3481d5dbc06a59
Merge: fd04899208d20 74a5257a0c175
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 13 09:05:29 2022 -0800

    Merge tag 'irq-msi-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull MSI irq updates from Thomas Gleixner:
     "Rework of the MSI interrupt infrastructure.
    
      This is a treewide cleanup and consolidation of MSI interrupt handling
      in preparation for further changes in this area which are necessary
      to:
    
       - address existing shortcomings in the VFIO area
    
       - support the upcoming Interrupt Message Store functionality which
         decouples the message store from the PCI config/MMIO space"
    
    * tag 'irq-msi-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (94 commits)
      genirq/msi: Populate sysfs entry only once
      PCI/MSI: Unbreak pci_irq_get_affinity()
      genirq/msi: Convert storage to xarray
      genirq/msi: Simplify sysfs handling
      genirq/msi: Add abuse prevention comment to msi header
      genirq/msi: Mop up old interfaces
      genirq/msi: Convert to new functions
      genirq/msi: Make interrupt allocation less convoluted
      platform-msi: Simplify platform device MSI code
      platform-msi: Let core code handle MSI descriptors
      bus: fsl-mc-msi: Simplify MSI descriptor handling
      soc: ti: ti_sci_inta_msi: Remove ti_sci_inta_msi_domain_free_irqs()
      soc: ti: ti_sci_inta_msi: Rework MSI descriptor allocation
      NTB/msi: Convert to msi_on_each_desc()
      PCI: hv: Rework MSI handling
      powerpc/mpic_u3msi: Use msi_for_each-desc()
      powerpc/fsl_msi: Use msi_for_each_desc()
      powerpc/pasemi/msi: Convert to msi_on_each_dec()
      powerpc/cell/axon_msi: Convert to msi_on_each_desc()
      powerpc/4xx/hsta: Rework MSI handling
      ...

commit fd04899208d2057b2de808e8447cfd806fd0a607
Merge: 147cc5838c0f5 35e13e9da9afb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 13 09:02:27 2022 -0800

    Merge tag 'timers-core-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull timer updates from Thomas Gleixner:
     "Updates for the time(r) subsystem:
    
      Core:
    
       - Make the clocksource watchdog more robust by better validation
         checks of the measurement.
    
      Drivers:
    
       - New drivers for MStar and SSD20xd SOCs
    
       - The usual cleanups and improvements all over the place"
    
    * tag 'timers-core-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      dt-bindings: timer: Add Mstar MSC313e timer devicetree bindings documentation
      clocksource/drivers/msc313e: Add support for ssd20xd-based platforms
      clocksource/drivers: Add MStar MSC313e timer support
      clocksource/drivers/pistachio: Fix -Wunused-but-set-variable warning
      clocksource/drivers/timer-imx-sysctr: Set cpumask to cpu_possible_mask
      clocksource/drivers/imx-sysctr: Mark two variable with __ro_after_init
      clocksource/drivers/renesas,ostm: Make RENESAS_OSTM symbol visible
      clocksource/drivers/renesas-ostm: Add RZ/G2L OSTM support
      dt-bindings: timer: renesas: ostm: Document Renesas RZ/G2L OSTM
      clocksource/drivers/exynos_mct: Fix silly typo resulting in checkpatch warning
      clocksource: Reduce the default clocksource_watchdog() retries to 2
      clocksource: Avoid accidental unstable marking of clocksources
      dt-bindings: timer: tpm-timer: Add imx8ulp compatible string
      reset: Add of_reset_control_get_optional_exclusive()
      clocksource/drivers/exynos_mct: Refactor resources allocation
      dt-bindings: timer: remove rockchip,rk3066-timer compatible string from rockchip,rk-timer.yaml
      dt-bindings: timer: cadence_ttc: Add power-domains

commit 147cc5838c0f5c76e908b816e924ca378e0d4735
Merge: 455e73a07f6e2 67d50b5f9114a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 13 08:53:45 2022 -0800

    Merge tag 'irq-core-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull irq updates from Thomas Gleixner:
     "Updates for the interrupt subsystem:
    
      Core:
    
       - Provide a new interface for affinity hints to provide a separation
         between hint and actual affinity change which has become a hidden
         property of the current interface
    
       - Fix up the in tree usage of the affinity hint interfaces
    
      Drivers:
    
       - No new irqchip drivers!
    
       - Fix GICv3 redistributor table reservation with RT across kexec
    
       - Fix GICv4.1 redistributor view of the VPE table across kexec
    
       - Add support for extra interrupts on spear-shirq
    
       - Make obtaining some interrupts optional for the Renesas drivers
    
       - Various cleanups and bug fixes"
    
    * tag 'irq-core-2022-01-13' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (25 commits)
      irqchip/renesas-intc-irqpin: Use platform_get_irq_optional() to get the interrupt
      irqchip/renesas-irqc: Use platform_get_irq_optional() to get the interrupt
      irqchip/gic-v4: Disable redistributors' view of the VPE table at boot time
      irqchip/ingenic-tcu: Use correctly sized arguments for bit field
      irqchip/gic-v2m: Add const to of_device_id
      irqchip/imx-gpcv2: Mark imx_gpcv2_instance with __ro_after_init
      irqchip/spear-shirq: Add support for IRQ 0..6
      irqchip/gic-v3-its: Limit memreserve cpuhp state lifetime
      irqchip/gic-v3-its: Postpone LPI pending table freeing and memreserve
      irqchip/gic-v3-its: Give the percpu rdist struct its own flags field
      net/mlx4: Use irq_update_affinity_hint()
      net/mlx5: Use irq_set_affinity_and_hint()
      hinic: Use irq_set_affinity_and_hint()
      scsi: lpfc: Use irq_set_affinity()
      mailbox: Use irq_update_affinity_hint()
      ixgbe: Use irq_update_affinity_hint()
      be2net: Use irq_update_affinity_hint()
      enic: Use irq_update_affinity_hint()
      RDMA/irdma: Use irq_update_affinity_hint()
      scsi: mpt3sas: Use irq_set_affinity_and_hint()
      ...

commit 87c71931633bd15e9cfd51d4a4d9cd685e8cdb55
Merge: f5d3ca6fffeb7 73a0c2be75cf7
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:53 2022 -0600

    Merge branch 'pci/driver-cleanup'
    
    - Use of_device_get_match_data(), not of_match_device(), when we only need
      the device data in altera, artpec6, cadence, designware-plat, dra7xx,
      keystone, kirin (Fan Fei)
    
    - Drop pointless of_device_get_match_data() cast in j721e (Bjorn Helgaas)
    
    - Drop redundant struct device * from j721e since struct cdns_pcie already
      has one (Bjorn Helgaas)
    
    - Rename driver structs to *_pcie in intel-gw, iproc, ls-gen4,
      mediatek-gen3, microchip, mt7621, rcar-gen2, tegra194, uniphier, xgene,
      xilinx, xilinx-cpm for consistency across drivers (Fan Fei)
    
    - Fix invalid address space conversions in hisi, spear13xx (Bjorn Helgaas)
    
    * pci/driver-cleanup:
      PCI: spear13xx: Avoid invalid address space conversions
      PCI: hisi: Avoid invalid address space conversions
      PCI: xilinx-cpm: Rename xilinx_cpm_pcie_port to xilinx_cpm_pcie
      PCI: xilinx: Rename xilinx_pcie_port to xilinx_pcie
      PCI: xgene: Rename xgene_pcie_port to xgene_pcie
      PCI: uniphier: Rename uniphier_pcie_priv to uniphier_pcie
      PCI: tegra194: Rename tegra_pcie_dw to tegra194_pcie
      PCI: rcar-gen2: Rename rcar_pci_priv to rcar_pci
      PCI: mt7621: Rename mt7621_pci_ to mt7621_pcie_
      PCI: microchip: Rename mc_port to mc_pcie
      PCI: mediatek-gen3: Rename mtk_pcie_port to mtk_gen3_pcie
      PCI: ls-gen4: Rename ls_pcie_g4 to ls_g4_pcie
      PCI: iproc: Rename iproc_pcie_pltfm_ to iproc_pltfm_pcie_
      PCI: iproc: Rename iproc_pcie_bcma_ to iproc_bcma_pcie_
      PCI: intel-gw: Rename intel_pcie_port to intel_pcie
      PCI: j721e: Drop redundant struct device *
      PCI: j721e: Drop pointless of_device_get_match_data() cast
      PCI: kirin: Prefer of_device_get_match_data()
      PCI: keystone: Prefer of_device_get_match_data()
      PCI: dra7xx: Prefer of_device_get_match_data()
      PCI: designware-plat: Prefer of_device_get_match_data()
      PCI: cadence: Prefer of_device_get_match_data()
      PCI: artpec6: Prefer of_device_get_match_data()
      PCI: altera: Prefer of_device_get_match_data()
    
    # Conflicts:
    #       drivers/pci/controller/pcie-mt7621.c

commit f5d3ca6fffeb71f304a7accae229c279e70b2216
Merge: da43f08db2369 c78b9a9cbde5f
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:52 2022 -0600

    Merge branch 'pci/errors'
    
    - Add PCI_ERROR_RESPONSE and related definitions for signaling and checking
      for transaction errors on PCI (Naveen Naidu)
    
    - Fabricate PCI_ERROR_RESPONSE data (~0) in config read wrappers, instead
      of in host controller drivers, when transactions fail on PCI (Naveen
      Naidu)
    
    - Use PCI_POSSIBLE_ERROR() to check for possible failure of config reads
      (Naveen Naidu)
    
    * pci/errors:
      PCI: xgene: Use PCI_ERROR_RESPONSE to identify config read errors
      PCI: hv: Use PCI_ERROR_RESPONSE to identify config read errors
      PCI: keystone: Use PCI_ERROR_RESPONSE to identify config read errors
      PCI: Use PCI_ERROR_RESPONSE to identify config read errors
      PCI: cpqphp: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI/PME: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI/DPC: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI: pciehp: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI: vmd: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI/ERR: Use PCI_POSSIBLE_ERROR() to check config reads
      PCI: rockchip-host: Drop error data fabrication when config read fails
      PCI: rcar-host: Drop error data fabrication when config read fails
      PCI: altera: Drop error data fabrication when config read fails
      PCI: mvebu: Drop error data fabrication when config read fails
      PCI: aardvark: Drop error data fabrication when config read fails
      PCI: kirin: Drop error data fabrication when config read fails
      PCI: histb: Drop error data fabrication when config read fails
      PCI: exynos: Drop error data fabrication when config read fails
      PCI: mediatek: Drop error data fabrication when config read fails
      PCI: iproc: Drop error data fabrication when config read fails
      PCI: thunder: Drop error data fabrication when config read fails
      PCI: Drop error data fabrication when config read fails
      PCI: Use PCI_SET_ERROR_RESPONSE() for disconnected devices
      PCI: Set error response data when config read fails
      PCI: Add PCI_ERROR_RESPONSE and related definitions

commit da43f08db236987f9421ccb14a675ce8bfd51707
Merge: 2709f0338d4c8 560dbc4654fa0
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:52 2022 -0600

    Merge branch 'pci/misc'
    
    - Sort Intel Device IDs by value (Andy Shevchenko)
    
    - Change Capability offsets to hex to match spec (Baruch Siach)
    
    - Correct misspellings (Krzysztof Wilczyński)
    
    - Terminate statement with semicolon in pci_endpoint_test.c (Ming Wang)
    
    * pci/misc:
      misc: pci_endpoint_test: Terminate statement with semicolon
      PCI: Correct misspelled words
      PCI: Change capability register offsets to hex
      PCI: Sort Intel Device IDs by value

commit 2709f0338d4c8cb17e11b448f0257afefae57475
Merge: a99f501f3e4d2 3be9d243b2172
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:51 2022 -0600

    Merge branch 'remotes/lorenzo/pci/bridge-emul'
    
    - Make emulated ROM BAR read-only by default (Pali Rohár)
    
    - Make some emulated legacy PCI bits read-only for PCIe devices (Pali
      Rohár)
    
    - Update reserved bits in emulated PCIe Capability (Pali Rohár)
    
    - Allow drivers to emulate different PCIe Capability versions (Pali Rohár)
    
    - Set emulated Capabilities List bit for all PCIe devices, since they must
      have at least a PCIe Capability (Pali Rohár)
    
    * remotes/lorenzo/pci/bridge-emul:
      PCI: pci-bridge-emul: Set PCI_STATUS_CAP_LIST for PCIe device
      PCI: pci-bridge-emul: Correctly set PCIe capabilities
      PCI: pci-bridge-emul: Fix definitions of reserved bits
      PCI: pci-bridge-emul: Properly mark reserved PCIe bits in PCI config space
      PCI: pci-bridge-emul: Make expansion ROM Base Address register read-only

commit a99f501f3e4d203b1306303f27a5d43b2f5d184e
Merge: 18b026da34c6b 61f0aa4da397b
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:51 2022 -0600

    Merge branch 'remotes/lorenzo/pci/xilinx-nwl'
    
    - Declare bitmap correctly and as part of struct nwl_msi managed resource
      (Christophe JAILLET)
    
    * remotes/lorenzo/pci/xilinx-nwl:
      PCI: xilinx-nwl: Simplify code and fix a memory leak

commit 18b026da34c6b4b01742572d334d17919d6b5bc0
Merge: ec5d85e7f0952 c7a75d07827a1
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:51 2022 -0600

    Merge branch 'remotes/lorenzo/pci/xgene'
    
    - Use bitmap ops for MSI allocator (Christophe JAILLET)
    
    - Fix IB window setup, which was broken by the fact that IB resources are
      now sorted in address order instead of DT dma-ranges order (Rob Herring)
    
    * remotes/lorenzo/pci/xgene:
      PCI: xgene: Fix IB window setup
      PCI: xgene-msi: Use bitmap_zalloc() when applicable

commit ec5d85e7f0952ca72407edf9b7f5748ca6611c94
Merge: 4ceca42d396eb 922bfd001d1ac
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:50 2022 -0600

    Merge branch 'remotes/lorenzo/pci/vmd'
    
    - Reset everything below VMD before enumerating to work around failure to
      enumerate NVMe devices when guest OS reboots (Nirmal Patel)
    
    - Honor platform ACPI _OSC feature negotiation for Root Ports below VMD
      (Kai-Heng Feng)
    
    - Add support for Raptor Lake SKUs (Karthik L Gopalakrishnan)
    
    * remotes/lorenzo/pci/vmd:
      PCI: vmd: Add DID 8086:A77F for all Intel Raptor Lake SKU's
      PCI: vmd: Honor ACPI _OSC on PCIe features
      PCI: vmd: Clean up domain before enumeration

commit 4ceca42d396eb5b7a80301e7d49a6d0012a17a43
Merge: f0eb209fed997 d2a14b54989e9
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:50 2022 -0600

    Merge branch 'remotes/lorenzo/pci/rcar'
    
    - Fix aarch32 abort handler so it doesn't check the wrong bus clock before
      accessing the host controller (Marek Vasut)
    
    * remotes/lorenzo/pci/rcar:
      PCI: rcar: Check if device is runtime suspended instead of __clk_is_enabled()

commit f0eb209fed997810d7af807e660b60eadad38781
Merge: 0de15dbbd648d 840a720aaa14d
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:50 2022 -0600

    Merge branch 'remotes/lorenzo/pci/qcom'
    
    - Undo PM setup in qcom_pcie_probe() error handling path (Christophe
      JAILLET)
    
    - Use __be16 type to store return value from cpu_to_be16() (Manivannan
      Sadhasivam)
    
    - Constify static dw_pcie_ep_ops (Rikard Falkeborn)
    
    * remotes/lorenzo/pci/qcom:
      PCI: qcom-ep: Constify static dw_pcie_ep_ops
      PCI: qcom: Use __be16 type to store return value from cpu_to_be16()
      PCI: qcom: Fix an error handling path in 'qcom_pcie_probe()'

commit 0de15dbbd648dc4f941d4d79da5ec0615c966545
Merge: fc10f9d6671a3 0746ae1be1217
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:49 2022 -0600

    Merge branch 'remotes/lorenzo/pci/mvebu'
    
    - Implement pci_remap_iospace() for ARM so mvebu can use
      devm_pci_remap_iospace() instead of the previous ARM-specific
      pci_ioremap_io() interface (Pali Rohár)
    
    - Use the standard pci_host_probe() instead of the device-specific
      mvebu_pci_host_probe() (Pali Rohár)
    
    - Replace all uses of ARM-specific pci_ioremap_io() with the
      ARM implementation of the standard pci_remap_iospace() interface and
      remove pci_ioremap_io() (Pali Rohár)
    
    - Skip initializing invalid Root Ports (Pali Rohár)
    
    - Check for errors from pci_bridge_emul_init() (Pali Rohár)
    
    - Ignore any bridges at non-zero function numbers (Pali Rohár)
    
    - Return ~0 data for invalid config read size (Pali Rohár)
    
    - Disallow mapping interrupts on emulated bridges (Pali Rohár)
    
    - Clear Root Port Memory & I/O Space Enable and Bus Master Enable at
      initialization (Pali Rohár)
    
    - Make type bits in Root Port I/O Base register read-only (Pali Rohár)
    
    - Disable Root Port windows when base/limit set to invalid values (Pali
      Rohár)
    
    - Set controller to Root Complex mode (Pali Rohár)
    
    - Set Root Port Class Code to PCI Bridge (Pali Rohár)
    
    - Update emulated Root Port secondary bus numbers to better reflect the
      actual topology (Pali Rohár)
    
    - Add PCI_BRIDGE_CTL_BUS_RESET support to emulated Root Ports so
      pci_reset_secondary_bus() can reset connected devices (Pali Rohár)
    
    - Add PCI_EXP_DEVCTL Error Reporting Enable support to emulated Root Ports
      (Pali Rohár)
    
    - Add PCI_EXP_RTSTA PME Status bit support to emulated Root Ports (Pali
      Rohár)
    
    - Add DEVCAP2, DEVCTL2 and LNKCTL2 support to emulated Root Ports on Armada
      XP and newer devices (Pali Rohár)
    
    - Export mvebu-mbus.c symbols to allow pci-mvebu.c to be a module (Pali
      Rohár)
    
    - Add support for compiling as a module (Pali Rohár)
    
    * remotes/lorenzo/pci/mvebu:
      PCI: mvebu: Add support for compiling driver as module
      bus: mvebu-mbus: Export symbols for public API window functions
      PCI: mvebu: Fix support for DEVCAP2, DEVCTL2 and LNKCTL2 registers on emulated bridge
      PCI: mvebu: Fix support for PCI_EXP_RTSTA on emulated bridge
      PCI: mvebu: Fix support for PCI_EXP_DEVCTL on emulated bridge
      PCI: mvebu: Fix support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge
      PCI: mvebu: Fix configuring secondary bus of PCIe Root Port via emulated bridge
      PCI: mvebu: Set PCI Bridge Class Code to PCI Bridge
      PCI: mvebu: Setup PCIe controller to Root Complex mode
      PCI: mvebu: Propagate errors when updating PCI_IO_BASE and PCI_MEM_BASE registers
      PCI: mvebu: Do not modify PCI IO type bits in conf_write
      PCI: mvebu: Fix support for bus mastering and PCI_COMMAND on emulated bridge
      PCI: mvebu: Disallow mapping interrupts on emulated bridges
      PCI: mvebu: Handle invalid size of read config request
      PCI: mvebu: Check that PCI bridge specified in DT has function number zero
      PCI: mvebu: Check for errors from pci_bridge_emul_init() call
      PCI: mvebu: Check for valid ports
      arm: ioremap: Remove unused ARM-specific function pci_ioremap_io()
      arm: ioremap: Replace pci_ioremap_io() usage by pci_remap_iospace()
      PCI: mvebu: Remove custom mvebu_pci_host_probe() function
      PCI: mvebu: Replace pci_ioremap_io() usage by devm_pci_remap_iospace()
      arm: ioremap: Implement standard PCI function pci_remap_iospace()

commit fc10f9d6671a3aacf1161dcc52582c27e3585a64
Merge: 96fe57938406c 44ddb791f8f41
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:49 2022 -0600

    Merge branch 'pci/host/mt7621'
    
    - Declare mt7621_pci_ops static (Sergio Paracuellos)
    
    - Give pcibios_root_bridge_prepare() access to host bridge windows (Sergio
      Paracuellos)
    
    - Move MIPS I/O coherency unit setup from driver to
      pcibios_root_bridge_prepare() (Sergio Paracuellos)
    
    - Add missing MODULE_LICENSE() (Sergio Paracuellos)
    
    - Allow COMPILE_TEST for all arches (Sergio Paracuellos)
    
    * pci/host/mt7621:
      PCI: mt7621: Allow COMPILE_TEST for all arches
      PCI: mt7621: Add missing MODULE_LICENSE()
      PCI: mt7621: Move MIPS setup to pcibios_root_bridge_prepare()
      PCI: Let pcibios_root_bridge_prepare() access bridge->windows
      PCI: mt7621: Declare mt7621_pci_ops static

commit 96fe57938406c37507e90da1ac2f325458798025
Merge: fd785c64f3554 ab344fd43f295
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:48 2022 -0600

    Merge branch 'remotes/lorenzo/pci/mediatek-gen3'
    
    - Disable Mediatek DVFSRC voltage request since lack of DVFSRC to respond
      to the request causes failure to exit L1 PM Substate (Jianjun Wang)
    
    * remotes/lorenzo/pci/mediatek-gen3:
      PCI: mediatek-gen3: Disable DVFSRC voltage request

commit fd785c64f3554a15a70a27486f81d38af397feca
Merge: 0dfa6f6e68858 65ace9a85fa7f
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:48 2022 -0600

    Merge branch 'remotes/lorenzo/pci/mediatek'
    
    - Assert PERST# for 100ms to allow power and clock to stabilize (qizhong
      cheng)
    
    * remotes/lorenzo/pci/mediatek:
      PCI: mediatek: Assert PERST# for 100ms for power and clock to stabilize

commit 0dfa6f6e68858e8a7a22cde98e2c0866c29cc9eb
Merge: 6553ff3dd95f9 7dcf07ac88676
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:48 2022 -0600

    Merge branch 'remotes/lorenzo/pci/keystone'
    
    - Add register offset for ti,syscon-pcie-id and ti,syscon-pcie-mode DT
      properties (Kishon Vijay Abraham I)
    
    * remotes/lorenzo/pci/keystone:
      PCI: keystone: Use phandle argument from "ti,syscon-pcie-id"/"ti,syscon-pcie-mode"
      dt-bindings: PCI: ti,am65: Fix "ti,syscon-pcie-id"/"ti,syscon-pcie-mode" to take argument

commit 6553ff3dd95f9e53faffab50a049222ae2c084f7
Merge: 28b75189f038a d9932b4691566
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:47 2022 -0600

    Merge branch 'pci/host/hv'
    
    - Add hv-internal interfaces to encapsulate arch IRQ dependencies (Sunil
      Muthuswamy)
    
    - Add arm64 Hyper-V vPCI support (Sunil Muthuswamy)
    
    * pci/host/hv:
      PCI: hv: Add arm64 Hyper-V vPCI support
      PCI: hv: Make the code arch neutral by adding arch specific interfaces

commit 28b75189f038af1392142906d9ff29bea46f8e4c
Merge: 2948ce70e636d 50b620303a14e
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:47 2022 -0600

    Merge branch 'remotes/lorenzo/pci/endpoint'
    
    - Return failure from pci_epc_set_msi() if no interrupts are available (Li
      Chen)
    
    * remotes/lorenzo/pci/endpoint:
      PCI: endpoint: Return -EINVAL when interrupts num is smaller than 1

commit 2948ce70e636d3803a17baa25d5e7d1e8ec844ae
Merge: c5f62d30e99cc d23f0c11aca27
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:47 2022 -0600

    Merge branch 'remotes/lorenzo/pci/dwc'
    
    - Don't ioremap NULL when DT lacks ATU resource (Tim Harvey)
    
    - Drop redundant qcom-ep error message for platform_get_irq_byname()
      failure (Krzysztof Wilczyński)
    
    - Add i.MX8MM support (Richard Zhu)
    
    - Use DWC common ops instead of layerscape-specific link-up functions (Hou
      Zhiqiang)
    
    * remotes/lorenzo/pci/dwc:
      PCI: layerscape: Change to use the DWC common link-up check function
      PCI: imx: Add the imx8mm pcie support
      dt-bindings: imx6q-pcie: Add PHY phandles and name properties
      PCI: qcom-ep: Remove surplus dev_err() when using platform_get_irq_byname()
      PCI: dwc: Do not remap invalid res

commit c5f62d30e99cc0d111bfba9d33ed05d576b3f7ee
Merge: 3164f27b5fd69 11ed8b8624b80
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:46 2022 -0600

    Merge branch 'pci/host/brcmstb'
    
    - Declare bitmap correctly for use by bitmap interfaces (Christophe
      JAILLET)
    
    - Clean up computation of legacy and non-legacy MSI bitmasks (Florian
      Fainelli)
    
    - Update suspend/resume/remove error handling to warn about errors and not
      fail the operation (Jim Quinlan)
    
    - Correct the "pcie" and "msi" interrupt descriptions in DT binding (Jim
      Quinlan)
    
    - Add DT bindings for endpoint voltage regulators (Jim Quinlan)
    
    - Split brcm_pcie_setup() into two functions (Jim Quinlan)
    
    - Add mechanism for turning on voltage regulators for connected devices
      (Jim Quinlan)
    
    - Turn voltage regulators for connected devices on/off when bus is added or
      removed (Jim Quinlan)
    
    - When suspending, don't turn off voltage regulators for wakeup devices
      (Jim Quinlan)
    
    * pci/host/brcmstb:
      PCI: brcmstb: Do not turn off WOL regulators on suspend
      PCI: brcmstb: Add control of subdevice voltage regulators
      PCI: brcmstb: Add mechanism to turn on subdev regulators
      PCI: brcmstb: Split brcm_pcie_setup() into two funcs
      dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators
      dt-bindings: PCI: Correct brcmstb interrupts, interrupt-map.
      PCI: brcmstb: Fix function return value handling
      PCI: brcmstb: Do not use __GENMASK
      PCI: brcmstb: Declare 'used' as bitmap, not unsigned long

commit 3164f27b5fd692ef6e0a5464b31534d09cc73949
Merge: 800cee8b04d18 75d36df680783
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:46 2022 -0600

    Merge branch 'remotes/lorenzo/pci/apple'
    
    - Enable clock gating to save power (Hector Martin)
    
    - Fix REFCLK1 enable/poll logic (Hector Martin)
    
    * remotes/lorenzo/pci/apple:
      PCI: apple: Fix REFCLK1 enable/poll logic
      PCI: apple: Enable clock gating

commit 800cee8b04d18db7ea4140aa6fb294508a2d20eb
Merge: d03f92c43f974 2070b2ddea89f
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:46 2022 -0600

    Merge branch 'remotes/lorenzo/pci/aardvark'
    
    - Add bridge emulation definitions for PCIe DEVCAP2, DEVCTL2, DEVSTA2,
      LNKCAP2, LNKCTL2, LNKSTA2, SLTCAP2, SLTCTL2, SLTSTA2 (Pali Rohár)
    
    - Add aardvark support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers
      (Pali Rohár)
    
    - Clear all MSIs at setup to avoid spurious interrupts (Pali Rohár)
    
    - Disable bus mastering when unbinding host controller driver (Pali Rohár)
    
    - Mask all interrupts when unbinding host controller driver (Pali Rohár)
    
    - Fix memory leak in host controller unbind (Pali Rohár)
    
    - Assert PERST# when unbinding host controller driver (Pali Rohár)
    
    - Disable link training when unbinding host controller driver (Pali Rohár)
    
    - Disable common PHY when unbinding host controller driver (Pali Rohár)
    
    - Fix resource type checking to check only IORESOURCE_MEM, not
      IORESOURCE_MEM_64, which is a flavor of IORESOURCE_MEM (Pali Rohár)
    
    * remotes/lorenzo/pci/aardvark:
      PCI: aardvark: Fix checking for MEM resource type
      PCI: aardvark: Disable common PHY when unbinding driver
      PCI: aardvark: Disable link training when unbinding driver
      PCI: aardvark: Assert PERST# when unbinding driver
      PCI: aardvark: Fix memory leak in driver unbind
      PCI: aardvark: Mask all interrupts when unbinding driver
      PCI: aardvark: Disable bus mastering when unbinding driver
      PCI: aardvark: Comment actions in driver remove method
      PCI: aardvark: Clear all MSIs at setup
      PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge
      PCI: pci-bridge-emul: Add definitions for missing capabilities registers
      PCI: pci-bridge-emul: Add description for class_revision field

commit d03f92c43f9741c06ab1e4ff9b51830705cfa176
Merge: 54f98a8b1382b e445375882883
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:45 2022 -0600

    Merge branch 'pci/virtualization'
    
    - Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller so it
      can work with an IOMMU (Yifeng Li)
    
    * pci/virtualization:
      PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller

commit 54f98a8b1382bbb387dd23d6a289f88ded78cb2f
Merge: 05642e2f64600 b76521f6482d2
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:45 2022 -0600

    Merge branch 'pci/switchtec'
    
    - Add Gen4 automotive device IDs (Kelvin Cao)
    
    - Declare state_names[] as static so it's not allocated and initialized for
      every call (Kelvin Cao)
    
    * pci/switchtec:
      PCI/switchtec: Declare local state_names[] as static
      PCI/switchtec: Add Gen4 automotive device IDs

commit 05642e2f64600a54f076dd0a3bbe2518d4c5cfe7
Merge: c6ff0f8dc05fc 500b55b05d0a2
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:45 2022 -0600

    Merge branch 'pci/resource'
    
    - Always write Intel I210 ROM BAR on update to work around device defect
      (Bjorn Helgaas)
    
    * pci/resource:
      PCI: Work around Intel I210 ROM BAR overlap defect

commit c6ff0f8dc05fc4137e0bc4a2e2d468430027df98
Merge: 446cc1c51a5a5 69f457b18fa2b
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:44 2022 -0600

    Merge branch 'pci/p2pdma'
    
    - Add Logan Gunthorpe as P2PDMA maintainer (Bjorn Helgaas)
    
    - Optimize by using percpu_ref_tryget_live_rcu() inside RCU critical
      section (Christophe JAILLET)
    
    * pci/p2pdma:
      PCI/P2PDMA: Use percpu_ref_tryget_live_rcu() inside RCU critical section
      MAINTAINERS: Add Logan Gunthorpe as P2PDMA maintainer

commit 446cc1c51a5a562fea13bdf875d77e813615058d
Merge: 7475f9319adc8 0aeddbd0cb078
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:44 2022 -0600

    Merge branch 'pci/legacy-pm-removal'
    
    - Convert amd64-agp, sis-agp, via-agp from legacy PCI power management to
      generic power management (Vaibhav Gupta)
    
    * pci/legacy-pm-removal:
      via-agp: convert to generic power management
      sis-agp: convert to generic power management
      amd64-agp: convert to generic power management

commit 7475f9319adc8fc3d3fbb34e6271e4e376c4d7f7
Merge: fb6c45130a4ad 085a9f43433f3
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:43 2022 -0600

    Merge branch 'pci/hotplug'
    
    - Fix infinite loop in pciehp IRQ handler on power fault (Lukas Wunner)
    
    - Removed commented-out ibmphp functions (Vihas Mak)
    
    - Fix pciehp lockdep errors on Thunderbolt undock (Hans de Goede)
    
    * pci/hotplug:
      PCI: pciehp: Use down_read/write_nested(reset_lock) to fix lockdep errors
      PCI: ibmphp: Remove commented-out functions
      PCI: pciehp: Fix infinite loop in IRQ handler upon power fault

commit fb6c45130a4ad48cc7bf27399fe812379de013a8
Merge: 7498e41fb537d 346865f074535
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:43 2022 -0600

    Merge branch 'pci/enumeration'
    
    - Use pci_find_vsec_capability() instead of open-coding it (Andy
      Shevchenko)
    
    - Convert pci_dev_present() stub from macro to static inline to avoid
      'unused variable' errors (Hans de Goede)
    
    - Convert sysfs slot attributes from default_attrs to default_groups (Greg
      Kroah-Hartman)
    
    - Use DWORD accesses for LTR, L1 SS to avoid BayHub OZ711LV2 erratum (Rajat
      Jain)
    
    - Remove unnecessary initialization of static variables (Longji Guo)
    
    * pci/enumeration:
      x86/PCI: Remove initialization of static variables to false
      PCI: Use DWORD accesses for LTR, L1 SS to avoid erratum
      PCI/sysfs: Use default_groups in kobj_type for slot attrs
      PCI: Convert pci_dev_present() stub to static inline
      PCI: Use pci_find_vsec_capability() when looking for TBT devices

commit 7498e41fb537d7174d12f564e9dd7009b3a02c5f
Merge: fa55b7dcdc43c fa285baf84430
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Thu Jan 13 09:57:43 2022 -0600

    Merge branch 'pci/aspm'
    
    - Calculate link L0s and L1 exit latencies when needed instead of caching
      them (Saheed O. Bolarinwa)
    
    - Calculate device L0s and L1 acceptable exit latencies when needed instead
      of caching them (Saheed O. Bolarinwa)
    
    - Remove struct aspm_latency since it's no longer needed (Saheed O.
      Bolarinwa)
    
    * pci/aspm:
      PCI/ASPM: Remove struct aspm_latency
      PCI/ASPM: Stop caching device L0s, L1 acceptable exit latencies
      PCI/ASPM: Stop caching link L0s, L1 exit latencies
      PCI/ASPM: Move pci_function_0() upward

commit 285ac8dca4df48e9a29fcc1c7f27602e1299a819
Author: Colin Ian King <colin.king@intel.com>
Date:   Thu Jan 13 09:24:17 2022 +0000

    kernel: Fix spelling mistake "compresser" -> "compressor"
    
    There is a spelling mistake in a pr_err error message. Fix it.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit 1a48db3fef499f615b56093947ec4b0d3d8e3021
Author: Anna Schumaker <Anna.Schumaker@Netapp.com>
Date:   Mon Nov 15 11:54:25 2021 -0500

    sunrpc: Fix potential race conditions in rpc_sysfs_xprt_state_change()
    
    We need to use test_and_set_bit() when changing xprt state flags to
    avoid potentially getting xps->xps_nactive out of sync.
    
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 776d794f28c95051bc70405a7b1fa40115658a18
Author: Xiyu Yang <xiyuyang19@fudan.edu.cn>
Date:   Thu Sep 9 12:32:38 2021 +0800

    net/sunrpc: fix reference count leaks in rpc_sysfs_xprt_state_change
    
    The refcount leak issues take place in an error handling path. When the
    3rd argument buf doesn't match with "offline", "online" or "remove", the
    function simply returns -EINVAL and forgets to decrease the reference
    count of a rpc_xprt object and a rpc_xprt_switch object increased by
    rpc_sysfs_xprt_kobj_get_xprt() and
    rpc_sysfs_xprt_kobj_get_xprt_switch(), causing reference count leaks of
    both unused objects.
    
    Fix this issue by jumping to the error handling path labelled with
    out_put when buf matches none of "offline", "online" or "remove".
    
    Signed-off-by: Xiyu Yang <xiyuyang19@fudan.edu.cn>
    Signed-off-by: Xin Xiong <xiongx18@fudan.edu.cn>
    Signed-off-by: Xin Tan <tanxin.ctf@gmail.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 4ca9f31a2be66d5fbf34b5b91ef17de7480992e1
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:35 2021 -0500

    NFSv4.1 test and add 4.1 trunking transport
    
    For each location returned in FS_LOCATION query, establish a
    transport to the server, send EXCHANGE_ID and test for trunking,
    if successful, add the transport to the exiting client.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit b8a09619a56334414cbd7f935a0796240d0cc07e
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:34 2021 -0500

    SUNRPC allow for unspecified transport time in rpc_clnt_add_xprt
    
    If the supplied argument doesn't specify the transport type, use the
    type of the existing rpc clnt and its existing transport.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit a8d54baba7c65db2d3278873def61f8d3753d766
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:33 2021 -0500

    NFSv4 handle port presence in fs_location server string
    
    An fs_location attribute returns a string that can be ipv4, ipv6,
    or DNS name. An ip location can have a port appended to it and if
    no port is present a default port needs to be set. If rpc_pton()
    fails to parse, try calling rpc_uaddr2socaddr() that can convert
    an universal address.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit f5b27cc6761e27ee6387a24df1a99ca77b360fea
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:32 2021 -0500

    NFSv4 expose nfs_parse_server_name function
    
    Make nfs_parse_server_name available outside of nfs4namespace.c.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 1976b2b31462151403c9fc110204fcc2a77bdfd1
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Wed Jan 12 10:27:38 2022 -0500

    NFSv4.1 query for fs_location attr on a new file system
    
    Query the server for other possible trunkable locations for a given
    file system on a 4.1+ mount.
    
    v2:
    -- added missing static to nfs4_discover_trunking,
    reported by the kernel test robot
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 486e5ed88827dabd295cd55f368d513ee8c30eb1
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Thu Jul 1 13:39:15 2021 -0300

    tools headers cpufeatures: Sync with the kernel sources
    
    To pick the changes from:
    
      d341db8f48ea4331 ("x86/cpufeatures: Add AMD Collaborative Processor Performance Control feature flag")
    
    This only causes these perf files to be rebuilt:
    
      CC       /tmp/build/perf/bench/mem-memcpy-x86-64-asm.o
      CC       /tmp/build/perf/bench/mem-memset-x86-64-asm.o
    
    And addresses this perf build warning:
    
      Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h'
      diff -u tools/arch/x86/include/asm/cpufeatures.h arch/x86/include/asm/cpufeatures.h
    
    Cc: Huang Rui <ray.huang@amd.com>
    Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f1dcda0f79548c04f585108e2e165cb4fec951e8
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon May 3 11:48:26 2021 -0300

    tools headers UAPI: Update tools's copy of drm.h header
    
    Picking the changes from:
    
      43d5ac7d07023cd1 ("drm: document DRM_IOCTL_MODE_GETFB2")
    
    It is just a comment, so no changes and silences these perf build warnings:
    
      Warning: Kernel ABI header at 'tools/include/uapi/drm/drm.h' differs from latest version at 'include/uapi/drm/drm.h'
      diff -u tools/include/uapi/drm/drm.h include/uapi/drm/drm.h
    
    Cc: Simon Ser <contact@emersion.fr>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 35cb8c713a496e8c114eed5e2a5a30b359876df2
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Sun May 9 10:19:37 2021 -0300

    tools arch: Update arch/x86/lib/mem{cpy,set}_64.S copies used in 'perf bench mem memcpy'
    
    To bring in the change made in this cset:
    
      f94909ceb1ed4bfd ("x86: Prepare asm files for straight-line-speculation")
    
    It silences these perf tools build warnings, no change in the tools:
    
      Warning: Kernel ABI header at 'tools/arch/x86/lib/memcpy_64.S' differs from latest version at 'arch/x86/lib/memcpy_64.S'
      diff -u tools/arch/x86/lib/memcpy_64.S arch/x86/lib/memcpy_64.S
      Warning: Kernel ABI header at 'tools/arch/x86/lib/memset_64.S' differs from latest version at 'arch/x86/lib/memset_64.S'
      diff -u tools/arch/x86/lib/memset_64.S arch/x86/lib/memset_64.S
    
    The code generated was checked before and after using 'objdump -d /tmp/build/perf/bench/mem-memcpy-x86-64-asm.o',
    no changes.
    
    Cc: Borislav Petkov <bp@suse.de>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 1aa77e716c6f2332f2d4664f747ff4eba731825b
Merge: c0dd94558d0e4 455e73a07f6e2
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Thu Jan 13 10:20:59 2022 -0300

    Merge remote-tracking branch 'torvalds/master' into perf/core
    
    To pick up fixes and get in line with other trees, powerpc kernel
    mostly this time, but BPF as well.
    
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 20c9398d3309d170300d67643b851fd26783af24
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Thu Jan 13 16:36:42 2022 +0800

    net/smc: Resolve the race between SMC-R link access and clear
    
    We encountered some crashes caused by the race between SMC-R
    link access and link clear that triggered by abnormal link
    group termination, such as port error.
    
    Here is an example of this kind of crashes:
    
     BUG: kernel NULL pointer dereference, address: 0000000000000000
     Workqueue: smc_hs_wq smc_listen_work [smc]
     RIP: 0010:smc_llc_flow_initiate+0x44/0x190 [smc]
     Call Trace:
      <TASK>
      ? __smc_buf_create+0x75a/0x950 [smc]
      smcr_lgr_reg_rmbs+0x2a/0xbf [smc]
      smc_listen_work+0xf72/0x1230 [smc]
      ? process_one_work+0x25c/0x600
      process_one_work+0x25c/0x600
      worker_thread+0x4f/0x3a0
      ? process_one_work+0x600/0x600
      kthread+0x15d/0x1a0
      ? set_kthread_struct+0x40/0x40
      ret_from_fork+0x1f/0x30
      </TASK>
    
    smc_listen_work()                     __smc_lgr_terminate()
    ---------------------------------------------------------------
                                        | smc_lgr_free()
                                        |  |- smcr_link_clear()
                                        |      |- memset(lnk, 0)
    smc_listen_rdma_reg()               |
     |- smcr_lgr_reg_rmbs()             |
         |- smc_llc_flow_initiate()     |
             |- access lnk->lgr (panic) |
    
    These crashes are similarly caused by clearing SMC-R link
    resources when some functions is still accessing to them.
    This patch tries to fix the issue by introducing reference
    count of SMC-R links and ensuring that the sensitive resources
    of links won't be cleared until reference count reaches zero.
    
    The operation to the SMC-R link reference count can be concluded
    as follows:
    
    object          [hold or initialized as 1]         [put]
    --------------------------------------------------------------------
    links           smcr_link_init()                   smcr_link_clear()
    connections     smc_conn_create()                  smc_conn_free()
    
    Through this way, the clear of SMC-R links is later than the
    free of all the smc connections above it, thus avoiding the
    unsafe reference to SMC-R links.
    
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ea89c6c0983c39702a4a52ccaa4702e0cb71179b
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Thu Jan 13 16:36:41 2022 +0800

    net/smc: Introduce a new conn->lgr validity check helper
    
    It is no longer suitable to identify whether a smc connection
    is registered in a link group through checking if conn->lgr
    is NULL, because conn->lgr won't be reset even the connection
    is unregistered from a link group.
    
    So this patch introduces a new helper smc_conn_lgr_valid() and
    replaces all the check of conn->lgr in original implementation
    with the new helper to judge if conn->lgr is valid to use.
    
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 91341fa0003befd097e190ec2a4bf63ad957c49a
Author: Eric Dumazet <edumazet@google.com>
Date:   Thu Jan 13 01:22:29 2022 -0800

    inet: frags: annotate races around fqdir->dead and fqdir->high_thresh
    
    Both fields can be read/written without synchronization,
    add proper accessors and documentation.
    
    Fixes: d5dd88794a13 ("inet: fix various use-after-free in defrags units")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3ba8c6258eb19a6212b066a383788174dd9779ab
Merge: de0e444706ed9 61f434b0280ed
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 13 12:55:40 2022 +0000

    Merge branch 'smc-race-fixes'
    
    Wen Gu says:
    
    ====================
    net/smc: Fixes for race in smc link group termination
    
    We encountered some crashes recently and they are caused by the
    race between the access and free of link/link group in abnormal
    smc link group termination. The crashes can be reproduced in
    frequent abnormal link group termination, like setting RNICs up/down.
    
    This set of patches tries to fix this by extending the life cycle
    of link/link group to ensure that they won't be referred to after
    cleared or freed.
    
    v1 -> v2:
    - Improve some comments.
    
    - Move codes of waking up lgrs_deleted wait queue from smc_lgr_free()
      to __smc_lgr_free().
    
    - Move codes of waking up links_deleted wait queue from smcr_link_clear()
      to __smcr_link_clear().
    
    - Move codes of smc_ibdev_cnt_dec() and put_device() from smcr_link_clear()
      to __smcr_link_clear()
    
    - Move smc_lgr_put() to the end of __smcr_link_clear().
    
    - Call smc_lgr_put() after 'out' tag in smcr_link_init() when link
      initialization fails.
    
    - Modify the location where smc connection holds the lgr or link.
    
        before:
          * hold lgr in smc_lgr_register_conn().
          * hold link in smcr_lgr_conn_assign_link().
        after:
          * hold both lgr and link in smc_conn_create().
    
      Modify the location to symmetrical with the place where smc connections
      put the lgr or link, which is smc_conn_free().
    
    - Initialize conn->freed as zero in smc_conn_create().
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 61f434b0280ed65495831f1b6e1a5c21a90f47c6
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Thu Jan 13 16:36:40 2022 +0800

    net/smc: Resolve the race between link group access and termination
    
    We encountered some crashes caused by the race between the access
    and the termination of link groups.
    
    Here are some of panic stacks we met:
    
    1) Race between smc_clc_wait_msg() and __smc_lgr_terminate()
    
     BUG: kernel NULL pointer dereference, address: 00000000000002f0
     Workqueue: smc_hs_wq smc_listen_work [smc]
     RIP: 0010:smc_clc_wait_msg+0x3eb/0x5c0 [smc]
     Call Trace:
      <TASK>
      ? smc_clc_send_accept+0x45/0xa0 [smc]
      ? smc_clc_send_accept+0x45/0xa0 [smc]
      smc_listen_work+0x783/0x1220 [smc]
      ? finish_task_switch+0xc4/0x2e0
      ? process_one_work+0x1ad/0x3c0
      process_one_work+0x1ad/0x3c0
      worker_thread+0x4c/0x390
      ? rescuer_thread+0x320/0x320
      kthread+0x149/0x190
      ? set_kthread_struct+0x40/0x40
      ret_from_fork+0x1f/0x30
      </TASK>
    
    smc_listen_work()                abnormal case like port error
    ---------------------------------------------------------------
                                    | __smc_lgr_terminate()
                                    |  |- smc_conn_kill()
                                    |      |- smc_lgr_unregister_conn()
                                    |          |- set conn->lgr = NULL
    smc_clc_wait_msg()              |
     |- access conn->lgr (panic)    |
    
    2) Race between smc_setsockopt() and __smc_lgr_terminate()
    
     BUG: kernel NULL pointer dereference, address: 00000000000002e8
     RIP: 0010:smc_setsockopt+0x17a/0x280 [smc]
     Call Trace:
      <TASK>
      __sys_setsockopt+0xfc/0x190
      __x64_sys_setsockopt+0x20/0x30
      do_syscall_64+0x34/0x90
      entry_SYSCALL_64_after_hwframe+0x44/0xae
      </TASK>
    
    smc_setsockopt()                 abnormal case like port error
    --------------------------------------------------------------
                                    | __smc_lgr_terminate()
                                    |  |- smc_conn_kill()
                                    |      |- smc_lgr_unregister_conn()
                                    |          |- set conn->lgr = NULL
    mod_delayed_work()              |
     |- access conn->lgr (panic)    |
    
    There are some other panic places and they are caused by the
    similar reason as described above, which is accessing link
    group after termination, thus getting a NULL pointer or invalid
    resource.
    
    Currently, there seems to be no synchronization between the
    link group access and a sudden termination of it. This patch
    tries to fix this by introducing reference count of link group
    and not freeing link group until reference count is zero.
    
    Link group might be referred to by links or smc connections. So
    the operation to the link group reference count can be concluded
    as follows:
    
    object          [hold or initialized as 1]       [put]
    -------------------------------------------------------------------
    link group      smc_lgr_create()                 smc_lgr_free()
    connections     smc_conn_create()                smc_conn_free()
    links           smcr_link_init()                 smcr_link_clear()
    
    Througth this way, we extend the life cycle of link group and
    ensure it is longer than the life cycle of connections and links
    above it, so that avoid invalid access to link group after its
    termination.
    
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit de0e444706ed98f2a13275a988d8595184be6d5c
Author: Li Zhijian <lizhijian@fujitsu.com>
Date:   Thu Jan 13 15:28:59 2022 +0800

    kselftests/net: adapt the timeout to the largest runtime
    
    timeout in settings is used by each case under the same directory, so
    it should adapt to the maximum runtime.
    
    A normally running net/fib_nexthops.sh may be killed by this unsuitable
    timeout. Furthermore, since the defect[1] of kselftests framework,
    net/fib_nexthops.sh which might take at least (300 * 4) seconds would
    block the whole kselftests framework previously.
    $ git grep -w 'sleep 300' tools/testing/selftests/net
    tools/testing/selftests/net/fib_nexthops.sh:    sleep 300
    tools/testing/selftests/net/fib_nexthops.sh:    sleep 300
    tools/testing/selftests/net/fib_nexthops.sh:    sleep 300
    tools/testing/selftests/net/fib_nexthops.sh:    sleep 300
    
    Enlarge the timeout by plus 300 based on the obvious largest runtime
    to avoid the blocking.
    
    [1]: https://www.spinics.net/lists/kernel/msg4185370.html
    
    Signed-off-by: Zhou Jie <zhoujie2011@fujitsu.com>
    Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 33cb0ff30cff104e753f7882c99e54cf67ea7903
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Wed Jan 12 22:21:27 2022 +0200

    net: mscc: ocelot: don't let phylink re-enable TX PAUSE on the NPI port
    
    Since commit b39648079db4 ("net: mscc: ocelot: disable flow control on
    NPI interface"), flow control should be disabled on the DSA CPU port
    when used in NPI mode.
    
    However, the commit blamed in the Fixes: tag below broke this, because
    it allowed felix_phylink_mac_link_up() to overwrite SYS_PAUSE_CFG_PAUSE_ENA
    for the DSA CPU port.
    
    This issue became noticeable since the device tree update from commit
    8fcea7be5736 ("arm64: dts: ls1028a: mark internal links between Felix
    and ENETC as capable of flow control").
    
    The solution is to check whether this is the currently configured NPI
    port from ocelot_phylink_mac_link_up(), and to not modify the statically
    disabled PAUSE frame transmission if it is.
    
    When the port is configured for lossless mode as opposed to tail drop
    mode, but the link partner (DSA master) doesn't observe the transmitted
    PAUSE frames, the switch termination throughput is much worse, as can be
    seen below.
    
    Before:
    
    root@debian:~# iperf3 -c 192.168.100.2
    Connecting to host 192.168.100.2, port 5201
    [  5] local 192.168.100.1 port 37504 connected to 192.168.100.2 port 5201
    [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
    [  5]   0.00-1.00   sec  28.4 MBytes   238 Mbits/sec  357   22.6 KBytes
    [  5]   1.00-2.00   sec  33.6 MBytes   282 Mbits/sec  426   19.8 KBytes
    [  5]   2.00-3.00   sec  34.0 MBytes   285 Mbits/sec  343   21.2 KBytes
    [  5]   3.00-4.00   sec  32.9 MBytes   276 Mbits/sec  354   22.6 KBytes
    [  5]   4.00-5.00   sec  32.3 MBytes   271 Mbits/sec  297   18.4 KBytes
    ^C[  5]   5.00-5.06   sec  2.05 MBytes   270 Mbits/sec   45   19.8 KBytes
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate         Retr
    [  5]   0.00-5.06   sec   163 MBytes   271 Mbits/sec  1822             sender
    [  5]   0.00-5.06   sec  0.00 Bytes  0.00 bits/sec                  receiver
    
    After:
    
    root@debian:~# iperf3 -c 192.168.100.2
    Connecting to host 192.168.100.2, port 5201
    [  5] local 192.168.100.1 port 49470 connected to 192.168.100.2 port 5201
    [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
    [  5]   0.00-1.00   sec   112 MBytes   941 Mbits/sec  259    143 KBytes
    [  5]   1.00-2.00   sec   110 MBytes   920 Mbits/sec  329    144 KBytes
    [  5]   2.00-3.00   sec   112 MBytes   936 Mbits/sec  255    144 KBytes
    [  5]   3.00-4.00   sec   110 MBytes   927 Mbits/sec  355    105 KBytes
    [  5]   4.00-5.00   sec   110 MBytes   926 Mbits/sec  350    156 KBytes
    [  5]   5.00-6.00   sec   110 MBytes   925 Mbits/sec  305    148 KBytes
    [  5]   6.00-7.00   sec   110 MBytes   924 Mbits/sec  320    143 KBytes
    [  5]   7.00-8.00   sec   110 MBytes   925 Mbits/sec  273   97.6 KBytes
    [  5]   8.00-9.00   sec   109 MBytes   913 Mbits/sec  299    141 KBytes
    [  5]   9.00-10.00  sec   110 MBytes   922 Mbits/sec  287    146 KBytes
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate         Retr
    [  5]   0.00-10.00  sec  1.08 GBytes   926 Mbits/sec  3032             sender
    [  5]   0.00-10.00  sec  1.08 GBytes   925 Mbits/sec                  receiver
    
    Fixes: de274be32cb2 ("net: dsa: felix: set TX flow control according to the phylink_mac_link_up resolution")
    Reported-by: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d7b4303411025b675e8c0927307c578a0ce3f75c
Author: Colin Ian King <colin.king@intel.com>
Date:   Wed Jan 12 23:55:33 2022 +0000

    atm: iphase: remove redundant pointer skb
    
    The pointer skb is redundant, it is assigned a value that is never
    read and hence can be removed. Cleans up clang scan warning:
    
    drivers/atm/iphase.c:205:18: warning: Although the value stored
    to 'skb' is used in the enclosing expression, the value is never
    actually read from 'skb' [deadcode.DeadStores]
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a0b3a15eab6bc2e90008460b646d53e7d9dcdbbb
Author: Jeff Layton <jlayton@kernel.org>
Date:   Mon Jan 10 18:28:33 2022 -0500

    ceph: move CEPH_SUPER_MAGIC definition to magic.h
    
    The uapi headers are missing the ceph definition. Move it there so
    userland apps can ID cephfs.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Ilya Dryomov <idryomov@gmail.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 76bdbc7ac777adb6bc316bfe3f57b3de93c50985
Author: Xiubo Li <xiubli@redhat.com>
Date:   Thu Jan 6 09:35:52 2022 +0800

    ceph: remove redundant Lsx caps check
    
    The newcaps has already included the Ls, no need to check it again.
    
    Signed-off-by: Xiubo Li <xiubli@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 94cc0877cad0bc6ca84686c4fa874bf530eb8b88
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Nov 30 14:12:13 2021 -0500

    ceph: add new "nopagecache" option
    
    CephFS is a bit unlike most other filesystems in that it only
    conditionally does buffered I/O based on the caps that it gets from the
    MDS. In most cases, unless there is contended access for an inode the
    MDS does give Fbc caps to the client, so the unbuffered codepaths are
    only infrequently traveled and are difficult to test.
    
    At one time, the "-o sync" mount option would give you this behavior,
    but that was removed in commit 7ab9b3807097 ("ceph: Don't use
    ceph-sync-mode for synchronous-fs.").
    
    Add a new mount option to tell the client to ignore Fbc caps when doing
    I/O, and to use the synchronous codepaths exclusively, even on
    non-O_DIRECT file descriptors. We already have an ioctl that forces this
    behavior on a per-file basis, so we can just always set the CEPH_F_SYNC
    flag in the file description on such mounts.
    
    Additionally, this patch also changes the client to not request Fbc when
    doing direct I/O. We aren't using the cache with O_DIRECT so we don't
    have any need for those caps.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Acked-by: Greg Farnum <gfarnum@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 0078ea3b0566e3da09ae8e1e4fbfd708702f2876
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Nov 9 09:54:49 2021 -0500

    ceph: don't check for quotas on MDS stray dirs
    
    玮文 胡 reported seeing the WARN_RATELIMIT pop when writing to an
    inode that had been transplanted into the stray dir. The client was
    trying to look up the quotarealm info from the parent and that tripped
    the warning.
    
    Change the ceph_vino_is_reserved helper to not throw a warning for
    MDS stray directories (0x100 - 0x1ff), only for reserved dirs that
    are not in that range.
    
    Also, fix ceph_has_realms_with_quotas to return false when encountering
    a reserved inode.
    
    URL: https://tracker.ceph.com/issues/53180
    Reported-by: Hu Weiwen <sehuww@mail.scut.edu.cn>
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Luis Henriques <lhenriques@suse.de>
    Reviewed-by: Xiubo Li <xiubli@redhat.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit af9ceae83cd26c9319bb2cdab23bb16d39300cbd
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Jan 26 13:41:38 2021 -0500

    ceph: drop send metrics debug message
    
    This pops every second and isn't very useful.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Reviewed-by: Xiubo Li <xiubli@redhat.com>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 435a120a47eed0b3a1ac7b86cf1f7707bf2242ce
Author: Colin Ian King <colin.i.king@googlemail.com>
Date:   Sat Nov 27 17:21:04 2021 +0000

    rbd: make const pointer spaces a static const array
    
    Don't populate the const array spaces on the stack but make it static
    const and make the pointer an array to remove a dereference. Shrinks
    object code a little too.  Also clean up intent, currently it is spaces
    and should be a tab.
    
    Signed-off-by: Colin Ian King <colin.i.king@googlemail.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 8e55ba8caae5cd380b1c9c81a426602a667e110e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Nov 10 23:30:21 2021 +0530

    ceph: Fix incorrect statfs report for small quota
    
    Problem:
    The statfs reports incorrect free/available space for quota less then
    CEPH_BLOCK size (4M).
    
    Solution:
    For quota less than CEPH_BLOCK size, smaller block size of 4K is used.
    But if quota is less than 4K, it is decided to go with binary use/free
    of 4K block. For quota size less than 4K size, report the
    total=used=4K,free=0 when quota is full and total=free=4K,used=0
    otherwise.
    
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit adbed05ed62d1f3b6f6c5cb88ec52c1ffafc0fd9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Nov 3 10:30:39 2021 +0530

    ceph: mount syntax module parameter
    
    Add read-only module parameters for supported mount syntaxes. Primary
    user is the user-space mount helper for catching v2 syntax bugs during
    testing by cross verifying if the kernel supports v2 syntax on mount
    failure.
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit e1b9eb50763d108166651ca67aae09893332c6b0
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 14 15:35:54 2021 +0530

    doc: document new CephFS mount device syntax
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 2167f2cc686a97911a0b06ba9c97cec304b7c432
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 14 15:35:53 2021 +0530

    ceph: record updated mon_addr on remount
    
    Note that the new monitors are just shown in /proc/mounts.
    Ceph does not (re)connect to new monitors yet.
    
    [ jlayton: s/printk\(KERN_NOTICE/pr_notice(/
               s/strcmp/strcmp_null/ ]
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 7b19b4db5add8d9f50e854907a82a10ba4d27c42
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 14 15:35:52 2021 +0530

    ceph: new device mount syntax
    
    Old mount device syntax (source) has the following problems:
    
    - mounts to the same cluster but with different fsnames
      and/or creds have identical device string which can
      confuse xfstests.
    
    - Userspace mount helper tool resolves monitor addresses
      and fill in mon addrs automatically, but that means the
      device shown in /proc/mounts is different than what was
      used for mounting.
    
    New device syntax is as follows:
    
      cephuser@fsid.mycephfs2=/path
    
    Note, there is no "monitor address" in the device string.
    That gets passed in as mount option. This keeps the device
    string same when monitor addresses change (on remounts).
    
    Also note that the userspace mount helper tool is backward
    compatible. I.e., the mount helper will fallback to using
    old syntax after trying to mount with the new syntax.
    
    [ idryomov: drop CEPH_MON_ADDR_MNTOPT_DELIM ]
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 4153c7fc937a2afa077dbdb9fe3189b9981f423c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 14 15:35:51 2021 +0530

    libceph: rename parse_fsid() to ceph_parse_fsid() and export
    
    ... as it is too generic. also, use __func__ when logging
    rather than hardcoding the function name.
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit 2d7c86a8f9cdce1408c4f3c69d94d007eff2f179
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 14 15:35:50 2021 +0530

    libceph: generalize addr/ip parsing based on delimiter
    
    ... and remove hardcoded function name in ceph_parse_ips().
    
    [ idryomov: delim parameter, drop CEPH_ADDR_PARSE_DEFAULT_DELIM ]
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Ilya Dryomov <idryomov@gmail.com>

commit de2d807b294d3d2ce5e59043ae2634016765d076
Author: Maxim Mikityanskiy <maximmi@nvidia.com>
Date:   Wed Jan 12 12:28:05 2022 +0200

    sch_api: Don't skip qdisc attach on ingress
    
    The attach callback of struct Qdisc_ops is used by only a few qdiscs:
    mq, mqprio and htb. qdisc_graft() contains the following logic
    (pseudocode):
    
        if (!qdisc->ops->attach) {
            if (ingress)
                do ingress stuff;
            else
                do egress stuff;
        }
        if (!ingress) {
            ...
            if (qdisc->ops->attach)
                qdisc->ops->attach(qdisc);
        } else {
            ...
        }
    
    As we see, the attach callback is not called if the qdisc is being
    attached to ingress (TC_H_INGRESS). That wasn't a problem for mq and
    mqprio, since they contain a check that they are attached to TC_H_ROOT,
    and they can't be attached to TC_H_INGRESS anyway.
    
    However, the commit cited below added the attach callback to htb. It is
    needed for the hardware offload, but in the non-offload mode it
    simulates the "do egress stuff" part of the pseudocode above. The
    problem is that when htb is attached to ingress, neither "do ingress
    stuff" nor attach() is called. It results in an inconsistency, and the
    following message is printed to dmesg:
    
    unregister_netdevice: waiting for lo to become free. Usage count = 2
    
    This commit addresses the issue by running "do ingress stuff" in the
    ingress flow even in the attach callback is present, which is fine,
    because attach isn't going to be called afterwards.
    
    The bug was found by syzbot and reported by Eric.
    
    Fixes: d03b195b5aa0 ("sch_htb: Hierarchical QoS hardware offload")
    Signed-off-by: Maxim Mikityanskiy <maximmi@nvidia.com>
    Reported-by: Eric Dumazet <edumazet@google.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 078c6a1cbd4cd7496048786beec2e312577bebbf
Author: Pawel Dembicki <paweldembicki@gmail.com>
Date:   Tue Jan 11 23:11:32 2022 +0100

    net: qmi_wwan: add ZTE MF286D modem 19d2:1485
    
    Modem from ZTE MF286D is an Qualcomm MDM9250 based 3G/4G modem.
    
    T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=5000 MxCh= 0
    D:  Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
    P:  Vendor=19d2 ProdID=1485 Rev=52.87
    S:  Manufacturer=ZTE,Incorporated
    S:  Product=ZTE Technologies MSM
    S:  SerialNumber=MF286DZTED000000
    C:* #Ifs= 7 Cfg#= 1 Atr=80 MxPwr=896mA
    A:  FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=06 Prot=00
    I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=ff Driver=rndis_host
    E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
    I:* If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=rndis_host
    E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=01(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=85(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
    E:  Ad=84(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=03(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
    E:  Ad=87(I) Atr=03(Int.) MxPS=  10 Ivl=32ms
    E:  Ad=86(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
    E:  Ad=88(I) Atr=03(Int.) MxPS=   8 Ivl=32ms
    E:  Ad=8e(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=0f(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    I:* If#= 6 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=usbfs
    E:  Ad=05(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    E:  Ad=89(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
    
    Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
    Acked-by: Bjørn Mork <bjorn@mork.no>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 081c73701ef0c2a4f6a127da824a641ae6505fbe
Author: Brent Lu <brent.lu@intel.com>
Date:   Thu Jan 13 18:52:20 2022 +0800

    ALSA: hda: intel-dsp-config: reorder the config table
    
    Entries without dmi_table nor codec_hid field need to be placed after
    entries with these two fields or they will be always selected.
    
    Signed-off-by: Brent Lu <brent.lu@intel.com>
    Link: https://lore.kernel.org/r/20220113105220.1114694-3-brent.lu@intel.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 19980aa10d2d944ed8fe345ce2eb87c2cb4bedf8
Author: Brent Lu <brent.lu@intel.com>
Date:   Thu Jan 13 18:52:19 2022 +0800

    ALSA: hda: intel-dsp-config: add JasperLake support
    
    Add rules to select SOF driver for Jasper Lake systems if digital
    microphone is present or the system is a Chromebook.
    
    Signed-off-by: Brent Lu <brent.lu@intel.com>
    Link: https://lore.kernel.org/r/20220113105220.1114694-2-brent.lu@intel.com
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 7d70984a1ad4c445dff08edb9aacce8906b6a222
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Thu Jan 13 12:22:38 2022 +0100

    netfilter: nft_connlimit: memleak if nf_ct_netns_get() fails
    
    Check if nf_ct_netns_get() fails then release the limit object
    previously allocated via kmalloc().
    
    Fixes: 37f319f37d90 ("netfilter: nft_connlimit: move stateful fields out of expression data")
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 54329e6f7beea6af56c1230da293acc97d6a6ee7
Author: Weizhao Ouyang <o451686892@gmail.com>
Date:   Tue Jan 4 15:35:45 2022 +0800

    dma-buf: cma_heap: Fix mutex locking section
    
    Fix cma_heap_buffer mutex locking critical section to protect vmap_cnt
    and vaddr.
    
    Fixes: a5d2d29e24be ("dma-buf: heaps: Move heap-helper logic into the cma_heap implementation")
    Signed-off-by: Weizhao Ouyang <o451686892@gmail.com>
    Acked-by: John Stultz <john.stultz@linaro.org>
    Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220104073545.124244-1-o451686892@gmail.com

commit 180d0eb290a5d11e6d3d99fea0841ceae2893901
Author: Helge Deller <deller@gmx.de>
Date:   Thu Jan 13 11:58:05 2022 +0100

    parisc: Add visible flag to toc_stack variable
    
    Add the visible flag to the toc_stack variable to make it visible for
    assembly code and to avoid a sparse warning.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 13462ba1815db5a96891293a9cfaa2451f7bd623
Author: Tom Rix <trix@redhat.com>
Date:   Sat Jan 8 07:09:48 2022 -0800

    i3c: master: dw: check return of dw_i3c_master_get_free_pos()
    
    Clang static analysis reports this problem
    dw-i3c-master.c:799:9: warning: The result of the left shift is
      undefined because the left operand is negative
                          COMMAND_PORT_DEV_INDEX(pos) |
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    pos can be negative because dw_i3c_master_get_free_pos() can return an
    error.  So check for an error.
    
    Fixes: 1dd728f5d4d4 ("i3c: master: Add driver for Synopsys DesignWare IP")
    Signed-off-by: Tom Rix <trix@redhat.com>
    Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
    Link: https://lore.kernel.org/r/20220108150948.3988790-1-trix@redhat.com

commit 455e73a07f6e288b0061dfcf4fcf54fa9fe06458
Merge: d9b5941bb5933 4afd2a9355a9d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 17:02:27 2022 -0800

    Merge tag 'clk-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
    
    Pull clk updates from Stephen Boyd:
     "We have a couple patches in the framework core this time around but
      they're mostly minor cleanups and some debugfs stuff. The real work
      that's in here is the typical pile of clk driver updates and new SoC
      support.
    
      Per usual (or maybe just recent trends), Qualcomm gains a handful of
      SoC drivers additions and has the largest diffstat. After that there
      are quite a few updates to the Allwinner (sunxi) drivers to support
      modular drivers and Renesas is heavily updated to add more support for
      various clks.
    
      Overall it looks pretty normal.
    
      New Drivers:
       - Add MDMA and BDMA clks to Ingenic JZ4760 and JZ4770
       - MediaTek mt7986 SoC basic support
       - Clock and reset driver for Toshiba Visconti SoCs
       - Initial clock driver for the Exynos7885 SoC (Samsung Galaxy A8)
       - Allwinner D1 clks
       - Lan966x Generic Clock Controller driver and associated DT bindings
       - Qualcomm SDX65, SM8450, and MSM8976 GCC clks
       - Qualcomm SDX65 and SM8450 RPMh clks
    
      Updates:
       - Set suppress_bind_attrs to true for i.MX8ULP driver
       - Switch from do_div to div64_ul for throughout all i.MX drivers
       - Fix imx8mn_clko1_sels for i.MX8MN
       - Remove unused IPG_AUDIO_ROOT from i.MX8MP
       - Switch parent for audio_root_clk to audio ahb in i.MX8MP driver
       - Removal of all remaining uses of __clk_lookup() in
         drivers/clk/samsung
       - Refactoring of the CPU clocks registration to use common interface
       - An update of the Exynos850 driver (support for more clock domains)
         required by the E850-96 development board
       - Prep for runtime PM and generic power domains on Tegra
       - Support modular Allwinner clk drivers via platform bus
       - Lan966x clock driver extended to support clock gating
       - Add serial (SCI1), watchdog (WDT), timer (OSTM), SPI (RSPI), and
         thermal (TSU) clocks and resets on Renesas RZ/G2L
       - Rework SDHI clock handling in the Renesas R-Car Gen3 and RZ/G2
         clock drivers, and in the Renesas SDHI driver
       - Make the Cortex-A55 (I) clock on Renesas RZ/G2L programmable
       - Document support for the new Renesas R-Car S4-8 (R8A779F0) SoC
       - Add support for the new Renesas R-Car S4-8 (R8A779F0) SoC
       - Add GPU clock and resets on Renesas RZ/G2L
       - Add clk-provider.h to various Qualcomm clk drivers
       - devm version of clk_hw_register_gate()
       - kerneldoc fixes in a couple drivers"
    
    * tag 'clk-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux: (131 commits)
      clk: visconti: Remove pointless NULL check in visconti_pll_add_lookup()
      clk: mediatek: add mt7986 clock support
      clk: mediatek: add mt7986 clock IDs
      dt-bindings: clock: mediatek: document clk bindings for mediatek mt7986 SoC
      clk: mediatek: clk-gate: Use regmap_{set/clear}_bits helpers
      clk: mediatek: clk-gate: Shrink by adding clockgating bit check helper
      clk: x86: Fix clk_gate_flags for RV_CLK_GATE
      clk: x86: Use dynamic con_id string during clk registration
      ACPI: APD: Add a fmw property clk-name
      drivers: acpi: acpi_apd: Remove unused device property "is-rv"
      x86: clk: clk-fch: Add support for newer family of AMD's SOC
      clk: ingenic: Add MDMA and BDMA clocks
      dt-bindings: clk/ingenic: Add MDMA and BDMA clocks
      clk: bm1880: remove kfrees on static allocations
      clk: Drop unused COMMON_CLK_STM32MP157_SCMI config
      clk: st: clkgen-mux: search reg within node or parent
      clk: st: clkgen-fsyn: search reg within node or parent
      clk: Enable/Disable runtime PM for clk_summary
      MAINTAINERS: Add entries for Toshiba Visconti PLL and clock controller
      clk: visconti: Add support common clock driver and reset driver
      ...

commit d9b5941bb5933932051e315de18a43db7d3c9e13
Merge: 4eb766f64d120 9e87a8da747bf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:59:22 2022 -0800

    Merge tag 'leds-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds
    
    Pull LED updates from Pavel Machek:
     "Nothing major is happening here"
    
    * tag 'leds-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds:
      leds: lp55xx: initialise output direction from dts
      ARM: dts: omap3-n900: Fix lp5523 for multi color
      leds: ktd2692: Drop calling dev_of_node() in ktd2692_parse_dt
      leds: lgm-sso: Get rid of duplicate of_node assignment
      leds: tca6507: Get rid of duplicate of_node assignment
      leds: leds-fsg: Drop FSG3 LED driver
      leds: lp50xx: remove unused variable
      dt-bindings: leds: Replace moonlight with indicator in mt6360 example
      leds: led-core: Update fwnode with device_set_node
      leds: tca6507: use swap() to make code cleaner
      leds: Add mt6360 driver
      dt-bindings: leds: Add bindings for MT6360 LED

commit 4eb766f64d120f0b80ec24282df789b7db2ff838
Merge: ce990f1de0bc6 e623611b4d3f7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:47:05 2022 -0800

    Merge tag 'devicetree-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux
    
    Pull devicetree updates from Rob Herring:
     "Bindings:
    
       - DT schema conversions for Samsung clocks, RNG bindings, Qcom
         Command DB and rmtfs, gpio-restart, i2c-mux-gpio, i2c-mux-pinctl,
         Tegra I2C and BPMP, pwm-vibrator, Arm DSU, and Cadence macb
    
       - DT schema conversions for Broadcom platforms: interrupt
         controllers, STB GPIO, STB waketimer, STB reset, iProc MDIO mux,
         iProc PCIe, Cygnus PCIe PHY, PWM, USB BDC, BCM6328 LEDs, TMON,
         SYSTEMPORT, AMAC, Northstar 2 PCIe PHY, GENET, moca PHY, GISB
         arbiter, and SATA
    
       - Add binding schemas for Tegra210 EMC table, TI DC-DC converters,
    
       - Clean-ups of MDIO bus schemas to fix 'unevaluatedProperties' issues
    
       - More fixes due to 'unevaluatedProperties' enabling
    
       - Data type fixes and clean-ups of binding examples found in
         preparation to move to validating DTB files directly (instead of
         intermediate YAML representation.
    
       - Vendor prefixes for T-Head Semiconductor, OnePlus, and Sunplus
    
       - Add various new compatible strings
    
      DT core:
    
       - Silence a warning for overlapping reserved memory regions
    
       - Reimplement unittest overlay tracking
    
       - Fix stack frame size warning in unittest
    
       - Clean-ups of early FDT scanning functions
    
       - Fix handling of "linux,usable-memory-range" on EFI booted systems
    
       - Add support for 'fail' status on CPU nodes
    
       - Improve error message in of_phandle_iterator_next()
    
       - kbuild: Disable duplicate unit-address warnings for disabled nodes"
    
    * tag 'devicetree-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux: (114 commits)
      dt-bindings: net: mdio: Drop resets/reset-names child properties
      dt-bindings: clock: samsung: convert S5Pv210 to dtschema
      dt-bindings: clock: samsung: convert Exynos5410 to dtschema
      dt-bindings: clock: samsung: convert Exynos5260 to dtschema
      dt-bindings: clock: samsung: extend Exynos7 bindings with UFS
      dt-bindings: clock: samsung: convert Exynos7 to dtschema
      dt-bindings: clock: samsung: convert Exynos5433 to dtschema
      dt-bindings: i2c: maxim,max96712: Add bindings for Maxim Integrated MAX96712
      dt-bindings: iio: adi,ltc2983: Fix 64-bit property sizes
      dt-bindings: power: maxim,max17040: Fix incorrect type for 'maxim,rcomp'
      dt-bindings: interrupt-controller: arm,gic-v3: Fix 'interrupts' cell size in example
      dt-bindings: iio/magnetometer: yamaha,yas530: Fix invalid 'interrupts' in example
      dt-bindings: clock: imx5: Drop clock consumer node from example
      dt-bindings: Drop required 'interrupt-parent'
      dt-bindings: net: ti,dp83869: Drop value on boolean 'ti,max-output-impedance'
      dt-bindings: net: wireless: mt76: Fix 8-bit property sizes
      dt-bindings: PCI: snps,dw-pcie-ep: Drop conflicting 'max-functions' schema
      dt-bindings: i2c: st,stm32-i2c: Make each example a separate entry
      dt-bindings: net: stm32-dwmac: Make each example a separate entry
      dt-bindings: net: Cleanup MDIO node schemas
      ...

commit ce990f1de0bc6ff3de43d385e0985efa980fba24
Merge: 64ad9461521b1 54bb4a91b281e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:42:00 2022 -0800

    Merge tag 'for-linus-5.17-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
    
    Pull xen updates from Juergen Gross:
    
     - a fix for the Xen gntdev driver
    
     - a fix for running as Xen dom0 booted via EFI and the EFI framebuffer
       being located above 4GB
    
     - a series for support of mapping other guest's memory by using zone
       device when running as Xen guest on Arm
    
    * tag 'for-linus-5.17-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip:
      dt-bindings: xen: Clarify "reg" purpose
      arm/xen: Read extended regions from DT and init Xen resource
      xen/unpopulated-alloc: Add mechanism to use Xen resource
      xen/balloon: Bring alloc(free)_xenballooned_pages helpers back
      arm/xen: Switch to use gnttab_setup_auto_xlat_frames() for DT
      xen/unpopulated-alloc: Drop check for virt_addr_valid() in fill_list()
      xen/x86: obtain upper 32 bits of video frame buffer address for Dom0
      xen/gntdev: fix unmap notification order

commit 64ad9461521b1a357846ef6cedc4bccd48a046e0
Merge: 8e5b0adeea193 9cdbeec409680
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:31:19 2022 -0800

    Merge tag 'x86_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 core updates from Borislav Petkov:
    
     - Get rid of all the .fixup sections because this generates
       misleading/wrong stacktraces and confuse RELIABLE_STACKTRACE and
       LIVEPATCH as the backtrace misses the function which is being fixed
       up.
    
     - Add Straight Line Speculation mitigation support which uses a new
       compiler switch -mharden-sls= which sticks an INT3 after a RET or an
       indirect branch in order to block speculation after them. Reportedly,
       CPUs do speculate behind such insns.
    
     - The usual set of cleanups and improvements
    
    * tag 'x86_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (32 commits)
      x86/entry_32: Fix segment exceptions
      objtool: Remove .fixup handling
      x86: Remove .fixup section
      x86/word-at-a-time: Remove .fixup usage
      x86/usercopy: Remove .fixup usage
      x86/usercopy_32: Simplify __copy_user_intel_nocache()
      x86/sgx: Remove .fixup usage
      x86/checksum_32: Remove .fixup usage
      x86/vmx: Remove .fixup usage
      x86/kvm: Remove .fixup usage
      x86/segment: Remove .fixup usage
      x86/fpu: Remove .fixup usage
      x86/xen: Remove .fixup usage
      x86/uaccess: Remove .fixup usage
      x86/futex: Remove .fixup usage
      x86/msr: Remove .fixup usage
      x86/extable: Extend extable functionality
      x86/entry_32: Remove .fixup usage
      x86/entry_64: Remove .fixup usage
      x86/copy_mc_64: Remove .fixup usage
      ...

commit 8e5b0adeea19309c8ce0e3c9119061554973efa9
Merge: 13eaa5bda0df8 a9f4a6e92b3b3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:26:58 2022 -0800

    Merge tag 'perf_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull perf updates from Borislav Petkov:
     "Cleanup of the perf/kvm interaction."
    
    * tag 'perf_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      perf: Drop guest callback (un)register stubs
      KVM: arm64: Drop perf.c and fold its tiny bits of code into arm.c
      KVM: arm64: Hide kvm_arm_pmu_available behind CONFIG_HW_PERF_EVENTS=y
      KVM: arm64: Convert to the generic perf callbacks
      KVM: x86: Move Intel Processor Trace interrupt handler to vmx.c
      KVM: Move x86's perf guest info callbacks to generic KVM
      KVM: x86: More precisely identify NMI from guest when handling PMI
      KVM: x86: Drop current_vcpu for kvm_running_vcpu + kvm_arch_vcpu variable
      perf/core: Use static_call to optimize perf_guest_info_callbacks
      perf: Force architectures to opt-in to guest callbacks
      perf: Add wrappers for invoking guest callbacks
      perf/core: Rework guest callbacks to prepare for static_call support
      perf: Drop dead and useless guest "support" from arm, csky, nds32 and riscv
      perf: Stop pretending that perf can handle multiple guest callbacks
      KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest
      KVM: x86: Register perf callbacks after calling vendor's hardware_setup()
      perf: Protect perf_guest_cbs with RCU

commit 13eaa5bda0df8f5c1c4f2a4fb4a0bc20787dcc68
Merge: 362f533a2a109 66dc1b791c583
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 16:15:51 2022 -0800

    Merge tag 'iommu-updates-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
    
    Pull iommu updates from Joerg Roedel:
    
     - Identity domain support for virtio-iommu
    
     - Move flush queue code into iommu-dma
    
     - Some fixes for AMD IOMMU suspend/resume support when x2apic is used
    
     - Arm SMMU Updates from Will Deacon:
          - Revert evtq and priq back to their former sizes
          - Return early on short-descriptor page-table allocation failure
          - Fix page fault reporting for Adreno GPU on SMMUv2
          - Make SMMUv3 MMU notifier ops 'const'
          - Numerous new compatible strings for Qualcomm SMMUv2 implementations
    
     - Various smaller fixes and cleanups
    
    * tag 'iommu-updates-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu: (38 commits)
      iommu/iova: Temporarily include dma-mapping.h from iova.h
      iommu: Move flush queue data into iommu_dma_cookie
      iommu/iova: Move flush queue code to iommu-dma
      iommu/iova: Consolidate flush queue code
      iommu/vt-d: Use put_pages_list
      iommu/amd: Use put_pages_list
      iommu/amd: Simplify pagetable freeing
      iommu/iova: Squash flush_cb abstraction
      iommu/iova: Squash entry_dtor abstraction
      iommu/iova: Fix race between FQ timeout and teardown
      iommu/amd: Fix typo in *glues … together* in comment
      iommu/vt-d: Remove unused dma_to_mm_pfn function
      iommu/vt-d: Drop duplicate check in dma_pte_free_pagetable()
      iommu/vt-d: Use bitmap_zalloc() when applicable
      iommu/amd: Remove useless irq affinity notifier
      iommu/amd: X2apic mode: mask/unmask interrupts on suspend/resume
      iommu/amd: X2apic mode: setup the INTX registers on mask/unmask
      iommu/amd: X2apic mode: re-enable after resume
      iommu/amd: Restore GA log/tail pointer on host resume
      iommu/iova: Move fast alloc size roundup into alloc_iova_fast()
      ...

commit 362f533a2a1098fe95020cb59340023e9b11d062
Merge: 3acbdbf42e943 be185c2988b48
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 15:57:59 2022 -0800

    Merge tag 'cxl-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl
    
    Pull CXL (Compute Express Link) updates from Dan Williams:
     "The highlight is initial support for CXL memory hotplug. The static
      NUMA node (ACPI SRAT Physical Address to Proximity Domain) information
      known to platform firmware is extended to support the potential
      performance-class / memory-target nodes dynamically created from
      available CXL memory device capacity.
    
      New unit test infrastructure is added for validating health
      information payloads.
    
      Fixes to module reload stress and stack usage from exposure in -next
      are included. A symbol rename and some other miscellaneous fixups are
      included as well.
    
      Summary:
    
       - Rework ACPI sub-table infrastructure to optionally be used outside
         of __init scenarios and use it for CEDT.CFMWS sub-table parsing.
    
       - Add support for extending num_possible_nodes by the potential
         hotplug CXL memory ranges
    
       - Extend tools/testing/cxl with mock memory device health information
    
       - Fix a module-reload workqueue race
    
       - Fix excessive stack-frame usage
    
       - Rename the driver context data structure from "cxl_mem" since that
         name collides with a proposed driver name
    
       - Use EXPORT_SYMBOL_NS_GPL instead of -DDEFAULT_SYMBOL_NAMESPACE at
         build time"
    
    * tag 'cxl-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl:
      cxl/core: Remove cxld_const_init in cxl_decoder_alloc()
      cxl/pmem: Fix module reload vs workqueue state
      ACPI: NUMA: Add a node and memblk for each CFMWS not in SRAT
      cxl/test: Mock acpi_table_parse_cedt()
      cxl/acpi: Convert CFMWS parsing to ACPI sub-table helpers
      ACPI: Add a context argument for table parsing handlers
      ACPI: Teach ACPI table parsing about the CEDT header format
      ACPI: Keep sub-table parsing infrastructure available for modules
      tools/testing/cxl: add mock output for the GET_HEALTH_INFO command
      cxl/memdev: Remove unused cxlmd field
      cxl/core: Convert to EXPORT_SYMBOL_NS_GPL
      cxl/memdev: Change cxl_mem to a more descriptive name
      cxl/mbox: Remove bad comment
      cxl/pmem: Fix reference counting for delayed work

commit 3acbdbf42e943d85174401357a6b6243479d4c76
Merge: 8834147f95056 9e05e95ca8dae
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 15:46:11 2022 -0800

    Merge tag 'libnvdimm-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
    
    Pull dax and libnvdimm updates from Dan Williams:
     "The bulk of this is a rework of the dax_operations API after
      discovering the obstacles it posed to the work-in-progress DAX+reflink
      support for XFS and other copy-on-write filesystem mechanics.
    
      Primarily the need to plumb a block_device through the API to handle
      partition offsets was a sticking point and Christoph untangled that
      dependency in addition to other cleanups to make landing the
      DAX+reflink support easier.
    
      The DAX_PMEM_COMPAT option has been around for 4 years and not only
      are distributions shipping userspace that understand the current
      configuration API, but some are not even bothering to turn this option
      on anymore, so it seems a good time to remove it per the deprecation
      schedule. Recall that this was added after the device-dax subsystem
      moved from /sys/class/dax to /sys/bus/dax for its sysfs organization.
      All recent functionality depends on /sys/bus/dax.
    
      Some other miscellaneous cleanups and reflink prep patches are
      included as well.
    
      Summary:
    
       - Simplify the dax_operations API:
    
          - Eliminate bdev_dax_pgoff() in favor of the filesystem
            maintaining and applying a partition offset to all its DAX iomap
            operations.
    
          - Remove wrappers and device-mapper stacked callbacks for
            ->copy_from_iter() and ->copy_to_iter() in favor of moving
            block_device relative offset responsibility to the
            dax_direct_access() caller.
    
          - Remove the need for an @bdev in filesystem-DAX infrastructure
    
          - Remove unused uio helpers copy_from_iter_flushcache() and
            copy_mc_to_iter() as only the non-check_copy_size() versions are
            used for DAX.
    
       - Prepare XFS for the pending (next merge window) DAX+reflink support
    
       - Remove deprecated DEV_DAX_PMEM_COMPAT support
    
       - Cleanup a straggling misuse of the GUID api"
    
    * tag 'libnvdimm-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: (38 commits)
      iomap: Fix error handling in iomap_zero_iter()
      ACPI: NFIT: Import GUID before use
      dax: remove the copy_from_iter and copy_to_iter methods
      dax: remove the DAXDEV_F_SYNC flag
      dax: simplify dax_synchronous and set_dax_synchronous
      uio: remove copy_from_iter_flushcache() and copy_mc_to_iter()
      iomap: turn the byte variable in iomap_zero_iter into a ssize_t
      memremap: remove support for external pgmap refcounts
      fsdax: don't require CONFIG_BLOCK
      iomap: build the block based code conditionally
      dax: fix up some of the block device related ifdefs
      fsdax: shift partition offset handling into the file systems
      dax: return the partition offset from fs_dax_get_by_bdev
      iomap: add a IOMAP_DAX flag
      xfs: pass the mapping flags to xfs_bmbt_to_iomap
      xfs: use xfs_direct_write_iomap_ops for DAX zeroing
      xfs: move dax device handling into xfs_{alloc,free}_buftarg
      ext4: cleanup the dax handling in ext4_fill_super
      ext2: cleanup the dax handling in ext2_fill_super
      fsdax: decouple zeroing from the iomap buffered I/O code
      ...

commit ed6ae5ca437d9d238117d90e95f7f2cc27da1b31
Author: Ignat Korchagin <ignat@cloudflare.com>
Date:   Fri Jan 7 12:38:42 2022 +0000

    sit: allow encapsulated IPv6 traffic to be delivered locally
    
    While experimenting with FOU encapsulation Amir noticed that encapsulated IPv6
    traffic fails to be delivered, if the peer IP address is configured locally.
    
    It can be easily verified by creating a sit interface like below:
    
    $ sudo ip link add name fou_test type sit remote 127.0.0.1 encap fou encap-sport auto encap-dport 1111
    $ sudo ip link set fou_test up
    
    and sending some IPv4 and IPv6 traffic to it
    
    $ ping -I fou_test -c 1 1.1.1.1
    $ ping6 -I fou_test -c 1 fe80::d0b0:dfff:fe4c:fcbc
    
    "tcpdump -i any udp dst port 1111" will confirm that only the first IPv4 ping
    was encapsulated and attempted to be delivered.
    
    This seems like a limitation: for example, in a cloud environment the "peer"
    service may be arbitrarily scheduled on any server within the cluster, where all
    nodes are trying to send encapsulated traffic. And the unlucky node will not be
    able to. Moreover, delivering encapsulated IPv4 traffic locally is allowed.
    
    But I may not have all the context about this restriction and this code predates
    the observable git history.
    
    Reported-by: Amir Razmjou <arazmjou@cloudflare.com>
    Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
    Reviewed-by: David Ahern <dsahern@kernel.org>
    Link: https://lore.kernel.org/r/20220107123842.211335-1-ignat@cloudflare.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 44ddb791f8f41f5f9f2ab4280a27c179ca7a8aed
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Wed Jan 12 15:28:10 2022 -0600

    PCI: mt7621: Allow COMPILE_TEST for all arches
    
    Since all MIPS-specific code has been removed from driver, allow it to be
    enabled for COMPILE_TEST on all architectures.
    
    Mark it as tristate and remove MIPS the MIPS dependency.
    
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit e4b1cd02dc8d7967a79edccd510724831e5cdee8
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Tue Dec 7 11:49:23 2021 +0100

    PCI: mt7621: Add missing MODULE_LICENSE()
    
    The MT7621 PCIe host controller driver can be built as a module, but it
    lacks a MODULE_LICENSE(), which causes a build error:
    
      ERROR: modpost: missing MODULE_LICENSE() in drivers/pci/controller/pcie-mt7621.o
    
    Add MODULE_LICENSE() to the driver.
    
    Fixes: 2bdd5238e756 ("PCI: mt7621: Add MediaTek MT7621 PCIe host controller driver")
    Link: https://lore.kernel.org/r/20211207104924.21327-5-sergio.paracuellos@gmail.com
    Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Krzysztof Wilczyński <kw@linux.com>

commit 8834147f9505661859ce44549bf601e2a06bba7c
Merge: 8975f8974888b d7bdba1c81f7e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 13:45:12 2022 -0800

    Merge tag 'fscache-rewrite-20220111' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs
    
    Pull fscache rewrite from David Howells:
     "This is a set of patches that rewrites the fscache driver and the
      cachefiles driver, significantly simplifying the code compared to
      what's upstream, removing the complex operation scheduling and object
      state machine in favour of something much smaller and simpler.
    
      The series is structured such that the first few patches disable
      fscache use by the network filesystems using it, remove the cachefiles
      driver entirely and as much of the fscache driver as can be got away
      with without causing build failures in the network filesystems.
    
      The patches after that recreate fscache and then cachefiles,
      attempting to add the pieces in a logical order. Finally, the
      filesystems are reenabled and then the very last patch changes the
      documentation.
    
      [!] Note: I have dropped the cifs patch for the moment, leaving local
          caching in cifs disabled. I've been having trouble getting that
          working. I think I have it done, but it needs more testing (there
          seem to be some test failures occurring with v5.16 also from
          xfstests), so I propose deferring that patch to the end of the
          merge window.
    
      WHY REWRITE?
      ============
    
      Fscache's operation scheduling API was intended to handle sequencing
      of cache operations, which were all required (where possible) to run
      asynchronously in parallel with the operations being done by the
      network filesystem, whilst allowing the cache to be brought online and
      offline and to interrupt service for invalidation.
    
      With the advent of the tmpfile capacity in the VFS, however, an
      opportunity arises to do invalidation much more simply, without having
      to wait for I/O that's actually in progress: Cachefiles can simply
      create a tmpfile, cut over the file pointer for the backing object
      attached to a cookie and abandon the in-progress I/O, dismissing it
      upon completion.
    
      Future work here would involve using Omar Sandoval's vfs_link() with
      AT_LINK_REPLACE[1] to allow an extant file to be displaced by a new
      hard link from a tmpfile as currently I have to unlink the old file
      first.
    
      These patches can also simplify the object state handling as I/O
      operations to the cache don't all have to be brought to a stop in
      order to invalidate a file. To that end, and with an eye on to writing
      a new backing cache model in the future, I've taken the opportunity to
      simplify the indexing structure.
    
      I've separated the index cookie concept from the file cookie concept
      by C type now. The former is now called a "volume cookie" (struct
      fscache_volume) and there is a container of file cookies. There are
      then just the two levels. All the index cookie levels are collapsed
      into a single volume cookie, and this has a single printable string as
      a key. For instance, an AFS volume would have a key of something like
      "afs,example.com,1000555", combining the filesystem name, cell name
      and volume ID. This is freeform, but must not have '/' chars in it.
    
      I've also eliminated all pointers back from fscache into the network
      filesystem. This required the duplication of a little bit of data in
      the cookie (cookie key, coherency data and file size), but it's not
      actually that much. This gets rid of problems with making sure we keep
      netfs data structures around so that the cache can access them.
    
      These patches mean that most of the code that was in the drivers
      before is simply gone and those drivers are now almost entirely new
      code. That being the case, there doesn't seem any particular reason to
      try and maintain bisectability across it. Further, there has to be a
      point in the middle where things are cut over as there's a single
      point everything has to go through (ie. /dev/cachefiles) and it can't
      be in use by two drivers at once.
    
      ISSUES YET OUTSTANDING
      ======================
    
      There are some issues still outstanding, unaddressed by this patchset,
      that will need fixing in future patchsets, but that don't stop this
      series from being usable:
    
      (1) The cachefiles driver needs to stop using the backing filesystem's
          metadata to store information about what parts of the cache are
          populated. This is not reliable with modern extent-based
          filesystems.
    
          Fixing this is deferred to a separate patchset as it involves
          negotiation with the network filesystem and the VM as to how much
          data to download to fulfil a read - which brings me on to (2)...
    
      (2) NFS (and CIFS with the dropped patch) do not take account of how
          the cache would like I/O to be structured to meet its granularity
          requirements. Previously, the cache used page granularity, which
          was fine as the network filesystems also dealt in page
          granularity, and the backing filesystem (ext4, xfs or whatever)
          did whatever it did out of sight. However, we now have folios to
          deal with and the cache will now have to store its own metadata to
          track its contents.
    
          The change I'm looking at making for cachefiles is to store
          content bitmaps in one or more xattrs and making a bit in the map
          correspond to something like a 256KiB block. However, the size of
          an xattr and the fact that they have to be read/updated in one go
          means that I'm looking at covering 1GiB of data per 512-byte map
          and storing each map in an xattr. Cachefiles has the potential to
          grow into a fully fledged filesystem of its very own if I'm not
          careful.
    
          However, I'm also looking at changing things even more radically
          and going to a different model of how the cache is arranged and
          managed - one that's more akin to the way, say, openafs does
          things - which brings me on to (3)...
    
      (3) The way cachefilesd does culling is very inefficient for large
          caches and it would be better to move it into the kernel if I can
          as cachefilesd has to keep asking the kernel if it can cull a
          file. Changing the way the backend works would allow this to be
          addressed.
    
      BITS THAT MAY BE CONTROVERSIAL
      ==============================
    
      There are some bits I've added that may be controversial:
    
      (1) I've provided a flag, S_KERNEL_FILE, that cachefiles uses to check
          if a files is already being used by some other kernel service
          (e.g. a duplicate cachefiles cache in the same directory) and
          reject it if it is. This isn't entirely necessary, but it helps
          prevent accidental data corruption.
    
          I don't want to use S_SWAPFILE as that has other effects, but
          quite possibly swapon() should set S_KERNEL_FILE too.
    
          Note that it doesn't prevent userspace from interfering, though
          perhaps it should. (I have made it prevent a marked directory from
          being rmdir-able).
    
      (2) Cachefiles wants to keep the backing file for a cookie open whilst
          we might need to write to it from network filesystem writeback.
          The problem is that the network filesystem unuses its cookie when
          its file is closed, and so we have nothing pinning the cachefiles
          file open and it will get closed automatically after a short time
          to avoid EMFILE/ENFILE problems.
    
          Reopening the cache file, however, is a problem if this is being
          done due to writeback triggered by exit(). Some filesystems will
          oops if we try to open a file in that context because they want to
          access current->fs or suchlike.
    
          To get around this, I added the following:
    
          (A) An inode flag, I_PINNING_FSCACHE_WB, to be set on a network
              filesystem inode to indicate that we have a usage count on the
              cookie caching that inode.
    
          (B) A flag in struct writeback_control, unpinned_fscache_wb, that
              is set when __writeback_single_inode() clears the last dirty
              page from i_pages - at which point it clears
              I_PINNING_FSCACHE_WB and sets this flag.
    
              This has to be done here so that clearing I_PINNING_FSCACHE_WB
              can be done atomically with the check of PAGECACHE_TAG_DIRTY
              that clears I_DIRTY_PAGES.
    
          (C) A function, fscache_set_page_dirty(), which if it is not set,
              sets I_PINNING_FSCACHE_WB and calls fscache_use_cookie() to
              pin the cache resources.
    
          (D) A function, fscache_unpin_writeback(), to be called by
              ->write_inode() to unuse the cookie.
    
          (E) A function, fscache_clear_inode_writeback(), to be called when
              the inode is evicted, before clear_inode() is called. This
              cleans up any lingering I_PINNING_FSCACHE_WB.
    
          The network filesystem can then use these tools to make sure that
          fscache_write_to_cache() can write locally modified data to the
          cache as well as to the server.
    
          For the future, I'm working on write helpers for netfs lib that
          should allow this facility to be removed by keeping track of the
          dirty regions separately - but that's incomplete at the moment and
          is also going to be affected by folios, one way or another, since
          it deals with pages"
    
    Link: https://lore.kernel.org/all/510611.1641942444@warthog.procyon.org.uk/
    Tested-by: Dominique Martinet <asmadeus@codewreck.org> # 9p
    Tested-by: kafs-testing@auristor.com # afs
    Tested-by: Jeff Layton <jlayton@kernel.org> # ceph
    Tested-by: Dave Wysochanski <dwysocha@redhat.com> # nfs
    Tested-by: Daire Byrne <daire@dneg.com> # nfs
    
    * tag 'fscache-rewrite-20220111' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs: (67 commits)
      9p, afs, ceph, nfs: Use current_is_kswapd() rather than gfpflags_allow_blocking()
      fscache: Add a tracepoint for cookie use/unuse
      fscache: Rewrite documentation
      ceph: add fscache writeback support
      ceph: conversion to new fscache API
      nfs: Implement cache I/O by accessing the cache directly
      nfs: Convert to new fscache volume/cookie API
      9p: Copy local writes to the cache when writing to the server
      9p: Use fscache indexing rewrite and reenable caching
      afs: Skip truncation on the server of data we haven't written yet
      afs: Copy local writes to the cache when writing to the server
      afs: Convert afs to use the new fscache API
      fscache, cachefiles: Display stat of culling events
      fscache, cachefiles: Display stats of no-space events
      cachefiles: Allow cachefiles to actually function
      fscache, cachefiles: Store the volume coherency data
      cachefiles: Implement the I/O routines
      cachefiles: Implement cookie resize for truncate
      cachefiles: Implement begin and end I/O operation
      cachefiles: Implement backing file wrangling
      ...

commit fe7498ef791710a8bb79008850ce7fcbd3903657
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Tue Dec 7 11:49:21 2021 +0100

    PCI: mt7621: Move MIPS setup to pcibios_root_bridge_prepare()
    
    On the MIPS ralink mt7621 platform, we need to set up I/O coherency units
    based on the host bridge apertures.
    
    To remove this arch dependency from the driver itself, move the coherency
    setup from the driver to pcibios_root_bridge_prepare().
    
    [bhelgaas: squash add/remove into one patch, commit log]
    Link: https://lore.kernel.org/r/20211207104924.21327-3-sergio.paracuellos@gmail.com
    Link: https://lore.kernel.org/r/20211207104924.21327-4-sergio.paracuellos@gmail.com
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Guenter Roeck <linux@roeck-us.net>             # arch/mips
    Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>   # arch/mips

commit 661c4c4f2693a8cdd42a93a2418244b8f5115e6b
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Tue Dec 7 11:49:20 2021 +0100

    PCI: Let pcibios_root_bridge_prepare() access bridge->windows
    
    When pci_register_host_bridge() is called, bridge->windows are already
    available. However these windows are being moved temporarily from there.
    
    To let pcibios_root_bridge_prepare() have access to these windows, move the
    windows movement after calling this function. This is useful for the MIPS
    ralink mt7621 platform so it can set up I/O coherence units and avoid
    custom MIPS code in the mt7621 PCIe controller driver.
    
    Link: https://lore.kernel.org/r/20211207104924.21327-2-sergio.paracuellos@gmail.com
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Acked-by: Arnd Bergmann <arnd@arndb.de>

commit 8975f8974888b3cd25aa8cf9eba24edbb9230bb2
Merge: 1fb38c934c6e6 073c3ab6ae012
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 13:30:58 2022 -0800

    Merge tag 'fuse-update-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse
    
    Pull fuse updates from Miklos Szeredi:
    
     - Fix a regression introduced in 5.15
    
     - Extend the size of the FUSE_INIT request to accommodate for more
       flags. There's a slight possibility of a regression for obscure fuse
       servers; if this happens, then more complexity will need to be added
       to the protocol
    
     - Allow the DAX property to be controlled by the server on a per-inode
       basis in virtiofs
    
     - Allow sending security context to the server when creating a file or
       directory
    
    * tag 'fuse-update-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse:
      Documentation/filesystem/dax: DAX on virtiofs
      fuse: mark inode DONT_CACHE when per inode DAX hint changes
      fuse: negotiate per inode DAX in FUSE_INIT
      fuse: enable per inode DAX
      fuse: support per inode DAX in fuse protocol
      fuse: make DAX mount option a tri-state
      fuse: add fuse_should_enable_dax() helper
      fuse: Pass correct lend value to filemap_write_and_wait_range()
      fuse: send security context of inode on file
      fuse: extend init flags

commit 1fb38c934c6e6fad1559f7fe22504b42b7110f8a
Merge: 3d3d6733065c9 f05f2429eec60
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 13:28:06 2022 -0800

    Merge tag 'fs_for_v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
    
    Pull UDF / reiserfs updates from Jan Kara:
     "One UDF fix and one reiserfs cleanup"
    
    * tag 'fs_for_v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
      udf: Fix error handling in udf_new_inode()
      reiserfs: don't use congestion_wait()

commit d068eebbd4822b6c14a7ea375dfe53ca5c69c776
Author: Michal Koutný <mkoutny@suse.com>
Date:   Fri Dec 17 16:48:54 2021 +0100

    cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy
    
    The commit 1f1562fcd04a ("cgroup/cpuset: Don't let child cpusets
    restrict parent in default hierarchy") inteded to relax the check only
    on the default hierarchy (or v2 mode) but it dropped the check in v1
    too.
    
    This patch returns and separates the legacy-only validations so that
    they can be considered only in the v1 mode, which should enforce the old
    constraints for the sake of compatibility.
    
    Fixes: 1f1562fcd04a ("cgroup/cpuset: Don't let child cpusets restrict parent in default hierarchy")
    Suggested-by: Waiman Long <longman@redhat.com>
    Signed-off-by: Michal Koutný <mkoutny@suse.com>
    Reviewed-by: Waiman Long <longman@redhat.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit da48157092e7dd25e8c0fa38e0ccd93219a66046
Author: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Date:   Wed Nov 17 16:29:52 2021 +0100

    PCI: mt7621: Declare mt7621_pci_ops static
    
    Sparse complains about mt7621_pci_ops symbol is not declared and asks if
    it should be declared as static instead. Sparse is right. Hence declare
    symbol as static.
    
    Link: https://lore.kernel.org/r/20211117152952.12271-1-sergio.paracuellos@gmail.com
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Krzysztof Wilczyński <kw@linux.com>

commit 3d3d6733065c9670f8df6630990d4885933b1e55
Merge: f079ab01b5609 8cc3b1ccd930f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 13:19:35 2022 -0800

    Merge tag 'fsnotify_for_v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs
    
    Pull fanotify updates from Jan Kara:
     "Support for new FAN_RENAME fanotify event and support for reporting
      child info in directory fanotify events (FAN_REPORT_TARGET_FID)"
    
    * tag 'fsnotify_for_v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
      fanotify: wire up FAN_RENAME event
      fanotify: report old and/or new parent+name in FAN_RENAME event
      fanotify: record either old name new name or both for FAN_RENAME
      fanotify: record old and new parent and name in FAN_RENAME event
      fanotify: support secondary dir fh and name in fanotify_info
      fanotify: use helpers to parcel fanotify_info buffer
      fanotify: use macros to get the offset to fanotify_info buffer
      fsnotify: generate FS_RENAME event with rich information
      fanotify: introduce group flag FAN_REPORT_TARGET_FID
      fsnotify: separate mark iterator type from object type enum
      fsnotify: clarify object type argument

commit f079ab01b5609fb0c9acc52c88168bf1eed82373
Merge: 6020c204be997 4d7bd0eb72e58
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 12:51:41 2022 -0800

    Merge tag 'iomap-5.17' of git://git.infradead.org/users/willy/linux
    
    Pull iomap updates from Matthew Wilcox:
     "Convert xfs/iomap to use folios.
    
      This should be all that is needed for XFS to use large folios. There
      is no code in this pull request to create large folios, but no
      additional changes should be needed to XFS or iomap once they are
      created.
    
      Usually this would have come from Darrick, and we had intended that it
      would come that route. Between the holidays and various things which
      Darrick needed to work on, he asked if I could send things directly.
    
      There weren't any other iomap patches pending for this release, which
      probably also played a role"
    
    * tag 'iomap-5.17' of git://git.infradead.org/users/willy/linux: (26 commits)
      iomap: Inline __iomap_zero_iter into its caller
      xfs: Support large folios
      iomap: Support large folios in invalidatepage
      iomap: Convert iomap_migrate_page() to use folios
      iomap: Convert iomap_add_to_ioend() to take a folio
      iomap: Simplify iomap_do_writepage()
      iomap: Simplify iomap_writepage_map()
      iomap,xfs: Convert ->discard_page to ->discard_folio
      iomap: Convert iomap_write_end_inline to take a folio
      iomap: Convert iomap_write_begin() and iomap_write_end() to folios
      iomap: Convert __iomap_zero_iter to use a folio
      iomap: Allow iomap_write_begin() to be called with the full length
      iomap: Convert iomap_page_mkwrite to use a folio
      iomap: Convert readahead and readpage to use a folio
      iomap: Convert iomap_read_inline_data to take a folio
      iomap: Use folio offsets instead of page offsets
      iomap: Convert bio completions to use folios
      iomap: Pass the iomap_page into iomap_set_range_uptodate
      iomap: Add iomap_invalidate_folio
      iomap: Convert iomap_releasepage to use a folio
      ...

commit 6020c204be997e3f5129839ff9c801800fb4336e
Merge: 81ff0be4b9e3b 6b24ca4a1a8d4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 12:37:02 2022 -0800

    Merge tag 'folio-5.17' of git://git.infradead.org/users/willy/pagecache
    
    Pull folio conversion updates from Matthew Wilcox:
     "Convert much of the page cache to use folios
    
      This stops just short of actually enabling large folios. It converts
      everything that I noticed needs to be converted, but there may still
      be places I've overlooked which still have page size assumptions.
    
      The big change here is using large entries in the page cache XArray
      instead of many small entries. That only affects shmem for now, but
      it's a pretty big change for shmem since it changes where memory needs
      to be allocated (at split time instead of insertion)"
    
    * tag 'folio-5.17' of git://git.infradead.org/users/willy/pagecache: (49 commits)
      mm: Use multi-index entries in the page cache
      XArray: Add xas_advance()
      truncate,shmem: Handle truncates that split large folios
      truncate: Convert invalidate_inode_pages2_range to folios
      fs: Convert vfs_dedupe_file_range_compare to folios
      mm: Remove pagevec_remove_exceptionals()
      mm: Convert find_lock_entries() to use a folio_batch
      filemap: Return only folios from find_get_entries()
      filemap: Convert filemap_get_read_batch() to use a folio_batch
      filemap: Convert filemap_read() to use a folio
      truncate: Add invalidate_complete_folio2()
      truncate: Convert invalidate_inode_pages2_range() to use a folio
      truncate: Skip known-truncated indices
      truncate,shmem: Add truncate_inode_folio()
      shmem: Convert part of shmem_undo_range() to use a folio
      mm: Add unmap_mapping_folio()
      truncate: Add truncate_cleanup_folio()
      filemap: Add filemap_release_folio()
      filemap: Use a folio in filemap_page_mkwrite
      filemap: Use a folio in filemap_map_pages
      ...

commit 11ed8b8624b8085f706864b4addcd304b1e4fc38
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:30 2022 -0500

    PCI: brcmstb: Do not turn off WOL regulators on suspend
    
    If any downstream device can be a wakeup device, do not turn off the
    regulators as the device will need them on.
    
    Link: https://lore.kernel.org/r/20220106160332.2143-8-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 93e41f3fca3d4a0f927b784012338c37f80a8a80
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:29 2022 -0500

    PCI: brcmstb: Add control of subdevice voltage regulators
    
    This Broadcom STB PCIe RC driver has one port and connects directly to one
    device, be it a switch or an endpoint.  We want to be able to leverage the
    recently added mechanism that allocates and turns on/off subdevice
    regulators.
    
    All that needs to be done is to put the regulator DT nodes in the bridge
    below host and to set the pci_ops methods add_bus and remove_bus.
    
    Note that the pci_subdev_regulators_add_bus() method is wrapped for two
    reasons:
    
       1. To achieve link up after the voltage regulators are turned on.
    
       2. If, in the case of an unsuccessful link up, to redirect any PCIe
          accesses to subdevices, e.g. the scan for DEV/ID.  This redirection
          is needed because the Broadcom PCIe HW will issue a CPU abort if such
          an access is made when the link is down.
    
    [bhelgaas: fold in
    https://lore.kernel.org/r/20220112013100.48029-1-jim2101024@gmail.com]
    Link: https://lore.kernel.org/r/20220106160332.2143-7-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 67211aadcb4b968d0fdc57bc27240fa71500c2d4
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:28 2022 -0500

    PCI: brcmstb: Add mechanism to turn on subdev regulators
    
    Add a mechanism to identify standard PCIe regulators in the DT, allocate
    them, and turn them on before the rest of the bus is scanned during
    pci_host_probe().
    
    The allocated structure that contains the regulators is stored in the port
    driver dev.driver_data field.  Here is a point-by-point of how and when
    this mechanism is activated:
    
    If:
        -- PCIe RC driver sets pci_ops {add,remove)_bus to
           pci_subdev_regulators_{add,remove}_bus during its probe.
        -- There is a DT node "RB" under the host bridge DT node.
        -- During the RC driver's pci_host_probe() the add_bus callback
           is invoked where (bus->parent && pci_is_root_bus(bus->parent)
           is true
    
    Then:
        -- A struct subdev_regulators structure will be allocated and
           assigned to bus->dev.driver_data.
        -- regulator_bulk_{get,enable} will be invoked on &bus->dev
           and the former will search for and process any
           vpcie{12v,3v3,3v3aux}-supply properties that reside in node "RB".
        -- The regulators will be turned off/on for any unbind/bind operations.
        -- The regulators will be turned off/on for any suspend/resumes, but
           only if the RC driver handles this on its own.  This will appear
           in a later commit for the pcie-brcmstb.c driver.
    
    The unabridged reason for doing this is as follows.  We would like the
    Broadcom STB PCIe root complex driver (and others) to be able to turn
    off/on regulators[1] that provide power to endpoint[2] devices.  Typically,
    the drivers of these endpoint devices are stock Linux drivers that are not
    aware that these regulator(s) exist and must be turned on for the driver to
    be probed.  The simple solution of course is to turn these regulators on at
    boot and keep them on.  However, this solution does not satisfy at least
    three of our usage modes:
    
      1. For example, one customer uses multiple PCIe controllers, but wants
         the ability to, by script invoking and unbind, turn any or all of them
         and their subdevices off to save power, e.g. when in battery mode.
    
      2. Another example is when a watchdog script discovers that an endpoint
         device is in an unresponsive state and would like to unbind, power
         toggle, and re-bind just the PCIe endpoint and controller.
    
      3. Of course we also want power turned off during suspend mode.  However,
         some endpoint devices may be able to "wake" during suspend and we need
         to recognise this case and veto the nominal act of turning off its
         regulator.  Such is the case with Wake-on-LAN and Wake-on-WLAN support
         where the PCIe endpoint device needs to be kept powered on in order to
         receive network packets and wake the system.
    
    In all of these cases it is advantageous for the PCIe controller to govern
    the turning off/on the regulators needed by the endpoint device.  The first
    two cases can be done by simply unbinding and binding the PCIe controller,
    if the controller has control of these regulators.
    
    [1] These regulators typically govern the actual power supply to the
        endpoint chip.  Sometimes they may be the official PCIe socket
        power -- such as 3.3v or aux-3.3v.  Sometimes they are truly
        the regulator(s) that supply power to the EP chip.
    
    [2] The 99% configuration of our boards is a single endpoint device
        attached to the PCIe controller.  I use the term endpoint but it could
        possibly mean a switch as well.
    
    Link: https://lore.kernel.org/r/20220106160332.2143-6-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 830aa6f29f07a4e2f1a947dfa72b3ccddb46dd21
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:27 2022 -0500

    PCI: brcmstb: Split brcm_pcie_setup() into two funcs
    
    We need to take some code in brcm_pcie_setup() and put it in a new function
    brcm_pcie_linkup().  In future commits the brcm_pcie_linkup() function will
    be called indirectly by pci_host_probe() as opposed to the host driver
    invoking it directly.
    
    Some code that was executed after the PCIe linkup is now placed so that it
    executes prior to linkup, since this code has to run prior to the
    invocation of pci_host_probe().
    
    Link: https://lore.kernel.org/r/20220106160332.2143-5-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit ea372f45cfff7774c57f685b0c1a86951a15e18a
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:26 2022 -0500

    dt-bindings: PCI: Add bindings for Brcmstb EP voltage regulators
    
    Add bindings for Brcmstb EP voltage regulators.  A new mechanism is to be
    added to the Linux PCI subsystem that will allocate and turn on/off
    regulators.  These are standard regulators -- vpcie12v, vpcie3v3, and
    vpcie3v3aux -- placed in the DT in the bridge node under the host bridge
    device.
    
    The use of a regulator property in the PCIe EP subnode such as
    "vpcie12v-supply" depends on a pending pullreq to the pci-bus.yaml
    file at
    
      https://github.com/devicetree-org/dt-schema/pull/63
    
    Link: https://lore.kernel.org/r/20220106160332.2143-4-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Rob Herring <robh@kernel.org>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>

commit 504253e44a9dc91e535f84273ebded324de4d2f6
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:25 2022 -0500

    dt-bindings: PCI: Correct brcmstb interrupts, interrupt-map.
    
    The "pcie" and "msi" interrupts were given the same interrupt when they are
    actually different.  Interrupt-map only had the INTA entry; add the INTB,
    INTC, and INTD entries.
    
    Link: https://lore.kernel.org/r/20220106160332.2143-3-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Acked-by: Rob Herring <robh@kernel.org>

commit 41ac424ac188d9d04c9831fd0fe6bce73ae2ec03
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Jan 6 11:03:24 2022 -0500

    PCI: brcmstb: Fix function return value handling
    
    Do at least a dev_err() on some calls to reset_control_rearm() and
    brcm_phy_stop().  In some cases it may not make sense to return this error
    value "above" as doing so will cause more trouble than is warranted.
    
    Link: https://lore.kernel.org/r/20220106160332.2143-2-jim2101024@gmail.com
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>

commit 09a710d952b985331ff0ffa2b648f2ae4da5507a
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Mon Nov 22 11:04:58 2021 -0800

    PCI: brcmstb: Do not use __GENMASK
    
    Define the legacy MSI interrupt bitmask as well as the non-legacy interrupt
    bitmask using GENMASK and then use them in brcm_msi_set_regs() in place of
    __GENMASK().
    
    Link: https://lore.kernel.org/r/20211122190459.3189616-1-f.fainelli@gmail.com
    Reported-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>

commit bf7325882525b580c4e41cd36845bcf8113307fe
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Nov 7 09:32:58 2021 +0100

    PCI: brcmstb: Declare 'used' as bitmap, not unsigned long
    
    The 'used' field of 'struct brcm_msi' is used as a bitmap.  Declare it with
    DECLARE_BITMAP() and adjust users accordingly.
    
    This fixes a harmless Coverity warning about array vs singleton usage.
    
    This bitmap can be used for either legacy or MSI interrupts, which require
    a size of BRCM_INT_PCI_MSI_LEGACY_NR or BRCM_INT_PCI_MSI_NR respectively.
    Add a BUILD_BUG_ON() to ensure it is large enough.
    
    Suggested-by: Krzysztof Wilczynski <kw@linux.com>
    Addresses-Coverity: "Out-of-bounds access (ARRAY_VS_SINGLETON)"
    Link: https://lore.kernel.org/r/e6d9da2112aab2939d1507b90962d07bfd735b4c.1636273671.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

commit 81ff0be4b9e3bcfee022d71cf89d72f7e2ed41ba
Merge: 57ea81971b729 bc128349588d5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 11:33:50 2022 -0800

    Merge tag 'spdx-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx
    
    Pull SPDX/License update from Greg KH:
     "Here is a single change that fixes up the description of the 'LGPL-2.1
      or later' identifiers so that the tools properly acknowledge that this
      is a valid license.
    
      This change has been in linux-next for weeks with no reported problems"
    
    * tag 'spdx-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx:
      LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiers

commit 57ea81971b7296b42fc77424af44c5915d3d4ae2
Merge: 342465f5337f7 cbb4f5f435995
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 11:27:57 2022 -0800

    Merge tag 'usb-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
    
    Pull USB and Thunderbolt updates from Greg KH:
     "Here is the big set of USB and Thunderbolt driver changes for
      5.17-rc1.
    
      Nothing major in here, just lots of little updates and cleanups. These
      include:
    
       - some USB header fixes picked from Ingo's header-splitup work
    
       - more USB4/Thunderbolt hardware support added
    
       - USB gadget driver updates and additions
    
       - USB typec additions (includes some acpi changes, which were acked
         by the ACPI maintainer)
    
       - core USB fixes as found by syzbot that were too late for 5.16-final
    
       - USB dwc3 driver updates
    
       - USB dwc2 driver updates
    
       - platform_get_irq() conversions of some USB drivers
    
       - other minor USB driver updates and additions
    
      All of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'usb-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (111 commits)
      docs: ABI: fixed formatting in configfs-usb-gadget-uac2
      usb: gadget: u_audio: Subdevice 0 for capture ctls
      usb: gadget: u_audio: fix calculations for small bInterval
      usb: dwc2: gadget: initialize max_speed from params
      usb: dwc2: do not gate off the hardware if it does not support clock gating
      usb: dwc3: qcom: Fix NULL vs IS_ERR checking in dwc3_qcom_probe
      headers/deps: USB: Optimize <linux/usb/ch9.h> dependencies, remove <linux/device.h>
      USB: common: debug: add needed kernel.h include
      headers/prep: Fix non-standard header section: drivers/usb/host/ohci-tmio.c
      headers/prep: Fix non-standard header section: drivers/usb/cdns3/core.h
      headers/prep: usb: gadget: Fix namespace collision
      USB: core: Fix bug in resuming hub's handling of wakeup requests
      USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
      usb: dwc3: dwc3-qcom: Add missing platform_device_put() in dwc3_qcom_acpi_register_core
      usb: gadget: clear related members when goto fail
      usb: gadget: don't release an existing dev->buf
      usb: dwc2: Simplify a bitmap declaration
      usb: Remove usb_for_each_port()
      usb: typec: port-mapper: Convert to the component framework
      usb: Link the ports to the connectors they are attached to
      ...

commit 8a59bb93b7e3cca389af44781a429ac12ac49be6
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:30 2021 -0500

    NFSv4 store server support for fs_location attribute
    
    Define and store if server returns it supports fs_locations attribute
    as a capability.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 90e12a3191040bd3854d3e236c35921e4e92a044
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Thu Dec 9 14:53:29 2021 -0500

    NFSv4 remove zero number of fs_locations entries error check
    
    Remove the check for the zero length fs_locations reply in the
    xdr decoding, and instead check for that in the migration code.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 342465f5337f7bd5b8bd3b6f939ac12b620cbb43
Merge: 22ef12195e13c 93a770b7e1677
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 11:21:52 2022 -0800

    Merge tag 'tty-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
    
    Pull tty/serial driver updates from Greg KH:
     "Here is the big set of tty/serial driver updates for 5.17-rc1.
    
      Nothing major in here, just lots of good updates and fixes, including:
    
       - more tty core cleanups from Jiri as well as mxser driver cleanups.
         This is the majority of the core diffstat
    
       - tty documentation updates from Jiri
    
       - platform_get_irq() updates
    
       - various serial driver updates for new features and hardware
    
       - fifo usage for 8250 console, reducing cpu load a lot
    
       - LED fix for keyboards, long-time bugfix that went through many
         revisions
    
       - minor cleanups
    
      All have been in linux-next for a while with no reported problems"
    
    * tag 'tty-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty: (119 commits)
      serial: core: Keep mctrl register state and cached copy in sync
      serial: stm32: correct loop for dma error handling
      serial: stm32: fix flow control transfer in DMA mode
      serial: stm32: rework TX DMA state condition
      serial: stm32: move tx dma terminate DMA to shutdown
      serial: pl011: Drop redundant DTR/RTS preservation on close/open
      serial: pl011: Drop CR register reset on set_termios
      serial: pl010: Drop CR register reset on set_termios
      serial: liteuart: fix MODULE_ALIAS
      serial: 8250_bcm7271: Fix return error code in case of dma_alloc_coherent() failure
      Revert "serdev: BREAK/FRAME/PARITY/OVERRUN notification prototype V2"
      tty: goldfish: Use platform_get_irq() to get the interrupt
      serdev: BREAK/FRAME/PARITY/OVERRUN notification prototype V2
      tty: serial: meson: Drop the legacy compatible strings and clock code
      serial: pmac_zilog: Use platform_get_irq() to get the interrupt
      serial: bcm63xx: Use platform_get_irq() to get the interrupt
      serial: ar933x: Use platform_get_irq() to get the interrupt
      serial: vt8500: Use platform_get_irq() to get the interrupt
      serial: altera_jtaguart: Use platform_get_irq_optional() to get the interrupt
      serial: pxa: Use platform_get_irq() to get the interrupt
      ...

commit 22ef12195e13c5ec58320dbf99ef85059a2c0820
Merge: 6dc69d3d0d18d fa783154524a7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 11:18:49 2022 -0800

    Merge tag 'staging-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
    
    Pull staging driver updates from Greg KH:
     "Here's the big set of staging driver updates for 5.17-rc1
    
      Nothing major in here at all, just lots and lots of tiny cleanups.
      Overall more code was removed than added, which is always nice, but
      not a huge change.
    
      Majority of the work happened in the r8188eu driver, that had hundreds
      of cleanups happen on it, but almost all other staging drivers had
      cleanups as well. No new functionality was added, cleanups only.
    
      All of these have been in linux-next for a while with no reported
      problems"
    
    * tag 'staging-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging: (308 commits)
      staging: r8188eu: rename camelcase variable uintPeerChannel
      staging: r8188eu: make BW20_24G_Diff a 1-D array
      staging: r8188eu: make OFDM_24G_Diff a 1-D array
      staging: r8188eu: BW40_24G_Diff is set but not used
      staging: r8188eu: CCK_24G_Diff is set but not used
      staging: r8188eu: make Index24G_BW40_Base a 1-D array
      staging: r8188eu: make Index24G_CCK_Base a 1-D array
      staging: r8188eu: rfPath is always 0
      staging: r8188eu: remove unneeded parameter from rtl8188e_SetHalODMVar
      staging: pi433: add comment to rx_lock mutex definition
      staging: pi433: fix frequency deviation check
      staging: vc04_services: rename BM2835 to BCM2835 in headers comments
      staging: vc04_services: rename string literal containing bm2835_* to bcm2835*_
      staging: vc04_services: rename variables containing bm2835_* to bcm2835_*
      staging: vc04_services: rename functions containing bm2835_* to bcm2835_*
      staging: vc04_services: rename structures bm2835_mmal_dev and bm2835_mmal_v4l2_ctrl
      staging: greybus: audio: Check null pointer
      staging: r8188eu: add spaces around P2P_AP_P2P_CH_SWITCH_PROCESS_WK
      staging: r8188eu: turbo scan is always off for r8188eu
      staging: r8188eu: cmd_issued_cnt is set but not used
      ...

commit 6dc69d3d0d18d587ab9d809fe060ba4417cf0279
Merge: e3084ed48fd6b c9512fd032acf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 11:11:34 2022 -0800

    Merge tag 'driver-core-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
    
    Pull driver core updates from Greg KH:
     "Here is the set of changes for the driver core for 5.17-rc1.
    
      Lots of little things here, including:
    
       - kobj_type cleanups
    
       - auxiliary_bus documentation updates
    
       - auxiliary_device conversions for some drivers (relevant subsystems
         all have provided acks for these)
    
       - kernfs lock contention reduction for some workloads
    
       - other tiny cleanups and changes.
    
      All of these have been in linux-next for a while with no reported
      issues"
    
    * tag 'driver-core-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (43 commits)
      kobject documentation: remove default_attrs information
      drivers/firmware: Add missing platform_device_put() in sysfb_create_simplefb
      debugfs: lockdown: Allow reading debugfs files that are not world readable
      driver core: Make bus notifiers in right order in really_probe()
      driver core: Move driver_sysfs_remove() after driver_sysfs_add()
      firmware: edd: remove empty default_attrs array
      firmware: dmi-sysfs: use default_groups in kobj_type
      qemu_fw_cfg: use default_groups in kobj_type
      firmware: memmap: use default_groups in kobj_type
      sh: sq: use default_groups in kobj_type
      headers/uninline: Uninline single-use function: kobject_has_children()
      devtmpfs: mount with noexec and nosuid
      driver core: Simplify async probe test code by using ktime_ms_delta()
      nilfs2: use default_groups in kobj_type
      kobject: remove kset from struct kset_uevent_ops callbacks
      driver core: make kobj_type constant.
      driver core: platform: document registration-failure requirement
      vdpa/mlx5: Use auxiliary_device driver data helpers
      net/mlx5e: Use auxiliary_device driver data helpers
      soundwire: intel: Use auxiliary_device driver data helpers
      ...

commit 5865918fe49ed3cb9d7b5d21f41aff8a68fbceb1
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:23 2022 +0000

    iio: pressure: bmp280: Use new PM macros
    
    Use the new EXPORT_RUNTIME_DEV_PM_OPS() macro. It allows the underlying
    dev_pm_ops struct as well as the suspend/resume callbacks to be detected
    as dead code in the case where CONFIG_PM is disabled, without having to
    wrap everything inside #ifdef CONFIG_PM guards.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit d59ff7d9d84b03d22c5107f794e28fc8e1fce3a6
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:22 2022 +0000

    PM: runtime: Add EXPORT[_GPL]_RUNTIME_DEV_PM_OPS macros
    
    Similar to EXPORT[_GPL]_SIMPLE_DEV_PM_OPS, but for users with runtime-PM
    suspend/resume callbacks.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 9d8619190031af0a314bee865262d8975473e4dd
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:21 2022 +0000

    PM: runtime: Add DEFINE_RUNTIME_DEV_PM_OPS() macro
    
    A lot of drivers create a dev_pm_ops struct with the system sleep
    suspend/resume callbacks set to pm_runtime_force_suspend() and
    pm_runtime_force_resume().
    
    These drivers can now use the DEFINE_RUNTIME_DEV_PM_OPS() macro, which
    will use pm_runtime_force_{suspend,resume}() as the system sleep
    callbacks, while having the same dead code removal characteristic that
    is already provided by DEFINE_SIMPLE_DEV_PM_OPS().
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 0ae101fdd3297b7165755340e05386f1e1379709
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:20 2022 +0000

    PM: core: Add EXPORT[_GPL]_SIMPLE_DEV_PM_OPS macros
    
    These macros are defined conditionally, according to CONFIG_PM:
    - if CONFIG_PM is enabled, these macros resolve to
      DEFINE_SIMPLE_DEV_PM_OPS(), and the dev_pm_ops symbol will be
      exported.
    
    - if CONFIG_PM is disabled, these macros will result in a dummy static
      dev_pm_ops to be created with the __maybe_unused flag. The dev_pm_ops
      will then be discarded by the compiler, along with the provided
      callback functions if they are not used anywhere else.
    
    In the second case, the symbol is not exported, which should be
    perfectly fine - users of the symbol should all use the pm_ptr() or
    pm_sleep_ptr() macro, so the dev_pm_ops marked as "extern" in the
    client's code will never be accessed.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 52cc1d7f9786d2be44a3ab9b5b48416a7618e713
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:19 2022 +0000

    PM: core: Remove static qualifier in DEFINE_SIMPLE_DEV_PM_OPS macro
    
    Keep this macro in line with the other ones. This makes it possible to
    use them in the cases where the underlying dev_pm_ops structure is
    exported.
    
    Restore the "static" qualifier in the two drivers where the
    DEFINE_SIMPLE_DEV_PM_OPS macro was used.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 3f4b32511a77bc5a05cfbf26fec94c4e1b1cf46a
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:17:18 2022 +0000

    PM: core: Remove DEFINE_UNIVERSAL_DEV_PM_OPS() macro
    
    The deprecated UNIVERSAL_DEV_PM_OPS() macro uses the provided callbacks
    for both runtime PM and system sleep, which is very likely to be a
    mistake, as a system sleep can be triggered while a given device is
    already PM-suspended, which would cause the suspend callback to be
    called twice.
    
    The amount of users of UNIVERSAL_DEV_PM_OPS() is also tiny (16
    occurences) compared to the number of places where
    SET_SYSTEM_SLEEP_PM_OPS() is used with pm_runtime_force_suspend() and
    pm_runtime_force_resume(), which makes me think that none of these cases
    are actually valid.
    
    As the new macro DEFINE_UNIVERSAL_DEV_PM_OPS() which was introduced to
    replace UNIVERSAL_DEV_PM_OPS() is currently unused, remove it before
    someone starts to use it in yet another invalid case.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit e3084ed48fd6b661fe434da0cb36d7d6706cf27f
Merge: 2ab9c9675fe89 7442936633bd1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:56:08 2022 -0800

    Merge tag 'pinctrl-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
    
    Pull pin control bulk updates from Linus Walleij:
     "Core changes:
    
       - New standard enumerator and corresponding device tree bindings for
         output impedance pin configuration. (Implemented and used in the
         Renesas rzg2l driver.)
    
       - Cleanup of Kconfig and Makefile to be somewhat orderly and
         alphabetic.
    
      New drivers:
    
       - Samsung Exynos 7885 pin controller.
    
       - Ocelot LAN966x pin controller.
    
       - Qualcomm SDX65 pin controller.
    
       - Qualcomm SM8450 pin controller.
    
       - Qualcomm PM8019, PM8226 and PM2250 pin controllers.
    
       - NXP/Freescale i.MXRT1050 pin controller.
    
       - Intel Thunder Bay pin controller.
    
      Enhancements:
    
       - Introduction of the string library helper function
         "kasprintf_strarray()" and subsequent use in Rockchip, ST and
         Armada pin control drivers, as well as the GPIO mockup driver.
    
       - The Ocelot pin controller has been extensively rewritten to use
         regmap and other modern kernel infrastructure.
    
       - The Microchip SGPIO driver has been converted to use regmap.
    
       - The SPEAr driver had been converted to use regmap.
    
       - Substantial cleanups and janitorial on the Apple pin control driver
         that was merged for v5.16.
    
       - Janitorial to remove of_node assignments in the GPIO portions that
         anyway get this handled in the GPIO core.
    
       - Minor cleanups and improvements in several pin controllers"
    
    * tag 'pinctrl-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl: (98 commits)
      pinctrl: imx: fix assigning groups names
      dt-bindings: pinctrl: mt8195: add wrapping node of pin configurations
      pinctrl: bcm: ns: use generic groups & functions helpers
      pinctrl: imx: fix allocation result check
      pinctrl: samsung: Use platform_get_irq_optional() to get the interrupt
      pinctrl: Propagate firmware node from a parent device
      dt-bindings: pinctrl: qcom: Add SDX65 pinctrl bindings
      pinctrl: add one more "const" for generic function groups
      pinctrl: keembay: rework loops looking for groups names
      pinctrl: keembay: comment process of building functions a bit
      pinctrl: imx: prepare for making "group_names" in "function_desc" const
      ARM: dts: gpio-ranges property is now required
      pinctrl: aspeed: fix unmet dependencies on MFD_SYSCON for PINCTRL_ASPEED
      pinctrl: Get rid of duplicate of_node assignment in the drivers
      pinctrl-sunxi: don't call pinctrl_gpio_direction()
      pinctrl-bcm2835: don't call pinctrl_gpio_direction()
      pinctrl: bcm2835: Silence uninit warning
      pinctrl: Sort Kconfig and Makefile entries alphabetically
      pinctrl: Add Intel Thunder Bay pinctrl driver
      dt-bindings: pinctrl: Add bindings for Intel Thunderbay pinctrl driver
      ...

commit 9e87a8da747bf72365abb79e6f64fcca955b4f56
Author: Merlijn Wajer <merlijn@wizzup.org>
Date:   Sun Dec 12 23:40:07 2021 +0100

    leds: lp55xx: initialise output direction from dts
    
    Commit a5d3d1adc95f ("leds: lp55xx: Initialize enable GPIO direction to
    output") attempts to fix this, but the fix did not work since at least
    for the Nokia N900 the value needs to be set to HIGH, per the device
    tree. So rather than hardcoding the value to a potentially invalid value
    for some devices, let's set direction in lp55xx_init_device.
    
    Fixes: a5d3d1adc95f ("leds: lp55xx: Initialize enable GPIO direction to output")
    Fixes: 92a81562e695 ("leds: lp55xx: Add multicolor framework support to lp55xx")
    Fixes: ac219bf3c9bd ("leds: lp55xx: Convert to use GPIO descriptors")
    Signed-off-by: Merlijn Wajer <merlijn@wizzup.org>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit e9af026a3b24f59d7af4609f73e0ef60a4d6d516
Author: Sicelo A. Mhlongo <absicsz@gmail.com>
Date:   Sun Dec 12 23:40:06 2021 +0100

    ARM: dts: omap3-n900: Fix lp5523 for multi color
    
    Since the LED multicolor framework support was added in commit
    92a81562e695 ("leds: lp55xx: Add multicolor framework support to lp55xx")
    LEDs on this platform stopped working.
    
    Fixes: 92a81562e695 ("leds: lp55xx: Add multicolor framework support to lp55xx")
    Fixes: ac219bf3c9bd ("leds: lp55xx: Convert to use GPIO descriptors")
    Signed-off-by: Merlijn Wajer <merlijn@wizzup.org>
    Signed-off-by: Sicelo A. Mhlongo <absicsz@gmail.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit a05f5d0e6aebd5c562d7f61b0fd3904d3e3994d1
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Mon Dec 13 19:03:31 2021 +0000

    leds: ktd2692: Drop calling dev_of_node() in ktd2692_parse_dt
    
    output of dev_of_node() is already assigned to "np" variable in
    ktd2692_parse_dt(). Use "np" variable to check if OF node is NULL
    instead of calling dev_of_node() again.
    
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 2702c9be20acf61c5c4cdee273792c3a4c92db12
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Tue Dec 14 16:27:39 2021 +0200

    leds: lgm-sso: Get rid of duplicate of_node assignment
    
    GPIO library does copy the of_node from the parent device of
    the GPIO chip, there is no need to repeat this in the individual
    drivers. Remove assignment here.
    
    For the details one may look into the of_gpio_dev_init() implementation.
    
    Call graph:
       --> sso_gpio_gc_init()
         --> devm_gpiochip_add_data
           --> devm_gpiochip_add_data_with_key
             --> gpiochip_add_data_with_key()
               --> of_gpio_dev_init()
    
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 27d1a6210d27c973f6bb31a24836099fb8c925ab
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date:   Tue Dec 14 16:27:38 2021 +0200

    leds: tca6507: Get rid of duplicate of_node assignment
    
    GPIO library does copy the of_node from the parent device of
    the GPIO chip, there is no need to repeat this in the individual
    drivers. Remove assignment here.
    
    For the details one may look into the of_gpio_dev_init() implementation.
    
    Call graph:
       --> tca6507_probe_gpios()
         --> gpiochip_add_data()
           --> gpiochip_add_data_with_key()
             --> of_gpio_dev_init()
    
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit b7f1ac9bb6413b739ea91bd61bdf23c9130a8007
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Mon Nov 22 11:28:51 2021 +0100

    leds: leds-fsg: Drop FSG3 LED driver
    
    The board file using this driver has been deleted and the
    FSG3 LEDs can be modeled using a system controller and some
    register bit LEDs in the device tree so this driver is no
    longer needed.
    
    Reported-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Cc: Krzysztof Hałasa <khalasa@piap.pl>
    Cc: Rod Whitby <rod@whitby.id.au>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 6212264be7df1d6b5b9eec4f1f1539abb071ff85
Author: Sven Schuchmann <schuchmann@schleissheimer.de>
Date:   Fri Nov 26 16:28:46 2021 +0100

    leds: lp50xx: remove unused variable
    
    During code review this unused variable was found. Remove it.
    
    Signed-off-by: Sven Schuchmann <schuchmann@schleissheimer.de>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 8018708d2d39a08144f39f0a61e49cdb943c2b2e
Author: ChiYuan Huang <cy_huang@richtek.com>
Date:   Wed Nov 17 15:22:06 2021 +0800

    dt-bindings: leds: Replace moonlight with indicator in mt6360 example
    
    Replace moonlight with indicator in mt6360 example to prevent the below
    build error:
    
    Error: Documentation/devicetree/bindings/leds/leds-mt6360.example.dts:114.24-25
    syntax error
    FATAL ERROR: Unable to parse input tree
    make[1]: *** [scripts/Makefile.lib:385:
    Documentation/devicetree/bindings/leds/leds-mt6360.example.dt.yaml]
    Error 1
    
    Link: https://lore.kernel.org/lkml/CAL_JsqJRMVE163LaHTbtFARc4f_qg33bfQx+sD3ukce_xQF+gA@mail.gmail.com/
    Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
    Reviewed-by: Gene Chen <gene_chen@richtek.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 495b8966f7ad92cac9ff84b52ce6365b1bf9c68c
Author: Sander Vanheule <sander@svanheule.net>
Date:   Sat Nov 13 22:11:13 2021 +0100

    leds: led-core: Update fwnode with device_set_node
    
    Update a newly created device's fwnode and of_node pointers using the
    recently added device_set_node helper. This keeps some firmware node
    specifics out of led-class and should help tracking future changes
    regarding device firmware node updates.
    
    Signed-off-by: Sander Vanheule <sander@svanheule.net>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit fa019ba4f202bce2aa1c6fcaead828d9625b9084
Author: Yihao Han <hanyihao@vivo.com>
Date:   Sun Nov 14 19:24:28 2021 -0800

    leds: tca6507: use swap() to make code cleaner
    
    Use the macro 'swap()' defined in 'include/linux/minmax.h' to avoid
    opencoding it.
    
    Signed-off-by: Yihao Han <hanyihao@vivo.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 2ab9c9675fe892e7fe9fa8c0a6125e2b40d2889d
Merge: 49008f0cc1ef0 8d4ff8187bb2b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:43:08 2022 -0800

    Merge tag 'media/v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
    
    Pull media fixes from Mauro Carvalho Chehab:
    
     - some fixes at si2157 tuning logic
    
     - a warning fix on atomisp when used with clang
    
    * tag 'media/v5.17-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media:
      media: si2157: add support for DVB-C Annex C
      media: si2157: fix bandwidth stored in dev
      media: si2157: fix 6MHz & 6.1MHz bandwidth setting
      media: atomisp: Do not define input_system_cfg2400_t twice

commit 679f8652064bfa2f622c7b2bab86b1bf3207d6bc
Author: Gene Chen <gene_chen@richtek.com>
Date:   Mon Nov 15 15:03:11 2021 +0100

    leds: Add mt6360 driver
    
    Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode,
    3-channel RGB LED support Register/Flash/Breath Mode, and 1-channel for
    moonlight LED.
    
    Signed-off-by: Gene Chen <gene_chen@richtek.com>
    Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
    Signed-off-by: Pavel Machek <pavel@ucw.cz>

commit 415b4b6c447ae03cb1d9cfc91df39616c92f15e2
Author: kernel test robot <lkp@intel.com>
Date:   Thu Jan 6 01:45:56 2022 +0800

    ACPI: PCC: pcc_ctx can be static
    
    drivers/acpi/acpi_pcc.c:34:22: warning: symbol 'pcc_ctx' was not declared. Should it be static?
    
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: kernel test robot <lkp@intel.com>
    Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 49008f0cc1ef0b86ccfa0d1d99e67741d46bd35b
Merge: c9193f48e94de eaac0b590a47c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:40:11 2022 -0800

    Merge tag 'for-5.17/dm-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
    
    Pull device mapper updates from Mike Snitzer:
    
     - Fixes and improvements to dm btree and dm space map code in
       persistent-data library used by thinp and cache.
    
     - Update DM integrity to use struct_group() to zero struct
       journal_sector.
    
     - Update DM sysfs to use default_groups in kobj_type.
    
    * tag 'for-5.17/dm-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
      dm sysfs: use default_groups in kobj_type
      dm integrity: Use struct_group() to zero struct journal_sector
      dm space map common: add bounds check to sm_ll_lookup_bitmap()
      dm btree: add a defensive bounds check to insert_at()
      dm btree remove: change a bunch of BUG_ON() calls to proper errors
      dm btree spine: eliminate duplicate le32_to_cpu() in node_check()
      dm btree spine: remove extra node_check function declaration

commit c9193f48e94deaeff0c9abbc67b9584e8ddc42ed
Merge: d3c810803576d d85bd8233fff0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:35:23 2022 -0800

    Merge tag 'for-5.17/drivers-2022-01-11' of git://git.kernel.dk/linux-block
    
    Pull block driver updates from Jens Axboe:
    
     - mtip32xx pci cleanups (Bjorn)
    
     - mtip32xx conversion to generic power management (Vaibhav)
    
     - rsxx pci powermanagement cleanups (Bjorn)
    
     - Remove the rsxx driver. This hardware never saw much adoption, and
       it's been end of lifed for a while. (Christoph)
    
     - MD pull request from Song:
          - REQ_NOWAIT support (Vishal Verma)
          - raid6 benchmark optimization (Dirk Müller)
          - Fix for acct bioset (Xiao Ni)
          - Clean up max_queued_requests (Mariusz Tkaczyk)
          - PREEMPT_RT optimization (Davidlohr Bueso)
          - Use default_groups in kobj_type (Greg Kroah-Hartman)
    
     - Use attribute groups in pktcdvd and rnbd (Greg)
    
     - NVMe pull request from Christoph:
          - increment request genctr on completion (Keith Busch, Geliang
            Tang)
          - add a 'iopolicy' module parameter (Hannes Reinecke)
          - print out valid arguments when reading from /dev/nvme-fabrics
            (Hannes Reinecke)
    
     - Use struct_group() in drbd (Kees)
    
     - null_blk fixes (Ming)
    
     - Get rid of congestion logic in pktcdvd (Neil)
    
     - Floppy ejection hang fix (Tasos)
    
     - Floppy max user request size fix (Xiongwei)
    
     - Loop locking fix (Tetsuo)
    
    * tag 'for-5.17/drivers-2022-01-11' of git://git.kernel.dk/linux-block: (32 commits)
      md: use default_groups in kobj_type
      md: Move alloc/free acct bioset in to personality
      lib/raid6: Use strict priority ranking for pq gen() benchmarking
      lib/raid6: skip benchmark of non-chosen xor_syndrome functions
      md: fix spelling of "its"
      md: raid456 add nowait support
      md: raid10 add nowait support
      md: raid1 add nowait support
      md: add support for REQ_NOWAIT
      md: drop queue limitation for RAID1 and RAID10
      md/raid5: play nice with PREEMPT_RT
      block/rnbd-clt-sysfs: use default_groups in kobj_type
      pktcdvd: convert to use attribute groups
      block: null_blk: only set set->nr_maps as 3 if active poll_queues is > 0
      nvme: add 'iopolicy' module parameter
      nvme: drop unused variable ctrl in nvme_setup_cmd
      nvme: increment request genctr on completion
      nvme-fabrics: print out valid arguments when reading from /dev/nvme-fabrics
      block: remove the rsxx driver
      rsxx: Drop PCI legacy power management
      ...

commit d3c810803576d867265277df8e94eee386351c9d
Merge: 42a7b4ed45e76 f029cedb9bb5b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:26:52 2022 -0800

    Merge tag 'for-5.17/block-2022-01-11' of git://git.kernel.dk/linux-block
    
    Pull block updates from Jens Axboe:
    
     - Unify where the struct request handling code is located in the blk-mq
       code (Christoph)
    
     - Header cleanups (Christoph)
    
     - Clean up the io_context handling code (Christoph, me)
    
     - Get rid of ->rq_disk in struct request (Christoph)
    
     - Error handling fix for add_disk() (Christoph)
    
     - request allocation cleanusp (Christoph)
    
     - Documentation updates (Eric, Matthew)
    
     - Remove trivial crypto unregister helper (Eric)
    
     - Reduce shared tag overhead (John)
    
     - Reduce poll_stats memory overhead (me)
    
     - Known indirect function call for dio (me)
    
     - Use atomic references for struct request (me)
    
     - Support request list issue for block and NVMe (me)
    
     - Improve queue dispatch pinning (Ming)
    
     - Improve the direct list issue code (Keith)
    
     - BFQ improvements (Jan)
    
     - Direct completion helper and use it in mmc block (Sebastian)
    
     - Use raw spinlock for the blktrace code (Wander)
    
     - fsync error handling fix (Ye)
    
     - Various fixes and cleanups (Lukas, Randy, Yang, Tetsuo, Ming, me)
    
    * tag 'for-5.17/block-2022-01-11' of git://git.kernel.dk/linux-block: (132 commits)
      MAINTAINERS: add entries for block layer documentation
      docs: block: remove queue-sysfs.rst
      docs: sysfs-block: document virt_boundary_mask
      docs: sysfs-block: document stable_writes
      docs: sysfs-block: fill in missing documentation from queue-sysfs.rst
      docs: sysfs-block: add contact for nomerges
      docs: sysfs-block: sort alphabetically
      docs: sysfs-block: move to stable directory
      block: don't protect submit_bio_checks by q_usage_counter
      block: fix old-style declaration
      nvme-pci: fix queue_rqs list splitting
      block: introduce rq_list_move
      block: introduce rq_list_for_each_safe macro
      block: move rq_list macros to blk-mq.h
      block: drop needless assignment in set_task_ioprio()
      block: remove unnecessary trailing '\'
      bio.h: fix kernel-doc warnings
      block: check minor range in device_add_disk()
      block: use "unsigned long" for blk_validate_block_size().
      block: fix error unwinding in device_add_disk
      ...

commit 42a7b4ed45e7667836fae4fb0e1ac6340588b1b0
Merge: 7e7b69654724c 3cc7fdb9f90a2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:20:35 2022 -0800

    Merge tag 'for-5.17/io_uring-2022-01-11' of git://git.kernel.dk/linux-block
    
    Pull io_uring updates from Jens Axboe:
    
     - Support for prioritized work completions (Hao)
    
     - Simplification of reissue (Pavel)
    
     - Add support for CQE skip (Pavel)
    
     - Memory leak fix going to 5.15-stable (Pavel)
    
     - Re-write of internal poll. This both cleans up that code, and gets us
       ready to fix the POLLFREE issue (Pavel)
    
     - Various cleanups (GuoYong, Pavel, Hao)
    
    * tag 'for-5.17/io_uring-2022-01-11' of git://git.kernel.dk/linux-block: (31 commits)
      io_uring: fix not released cached task refs
      io_uring: remove redundant tab space
      io_uring: remove unused function parameter
      io_uring: use completion batching for poll rem/upd
      io_uring: single shot poll removal optimisation
      io_uring: poll rework
      io_uring: kill poll linking optimisation
      io_uring: move common poll bits
      io_uring: refactor poll update
      io_uring: remove double poll on poll update
      io_uring: code clean for some ctx usage
      io_uring: batch completion in prior_task_list
      io_uring: split io_req_complete_post() and add a helper
      io_uring: add helper for task work execution code
      io_uring: add a priority tw list for irq completion work
      io-wq: add helper to merge two wq_lists
      io_uring: reuse io_req_task_complete for timeouts
      io_uring: tweak iopoll CQE_SKIP event counting
      io_uring: simplify selected buf handling
      io_uring: move up io_put_kbuf() and io_put_rw_kbuf()
      ...

commit e179f045f90d8947d3c2addebd620341b7daa4a1
Author: Yevhen Orlov <yevhen.orlov@plvision.eu>
Date:   Tue Jan 11 03:11:29 2022 +0200

    net: marvell: prestera: Fix deinit sequence for router
    
    * Add missed call prestera_router_fini in prestera_switch_fini
    * Add prestera_router_hw_fini, which verify lists are empty
    
    Fixes: 69204174cc5c ("net: marvell: prestera: Add prestera router infra")
    Signed-off-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
    Link: https://lore.kernel.org/r/20220111011129.5457-1-yevhen.orlov@plvision.eu
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 32d098bb2e494cf282968ae654dadf7299bb73b0
Author: Yevhen Orlov <yevhen.orlov@plvision.eu>
Date:   Tue Jan 11 03:10:51 2022 +0200

    net: marvell: prestera: Refactor router functions
    
    * Reverse xmas tree variables order
    * User friendly messages on error paths
    * Refactor __prestera_inetaddr_event to use early return
    
    Signed-off-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
    Link: https://lore.kernel.org/r/20220111011051.4941-1-yevhen.orlov@plvision.eu
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6a1ba8758f67e37a48fd2f940032a2b186bcf021
Author: Yevhen Orlov <yevhen.orlov@plvision.eu>
Date:   Tue Jan 11 03:10:14 2022 +0200

    net: marvell: prestera: Refactor get/put VR functions
    
    * Use refcount, instead of uint
    * Increment/decrement recount inside get/put
    * Fix error path in __prestera_vr_create. Remove unnecessary kfree.
    * Make __prestera_vr_destroy symmetric to "create"
    
    Fixes: bca5859bc6c6 ("net: marvell: prestera: add hardware router objects accounting")
    Signed-off-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
    Link: https://lore.kernel.org/r/20220111011014.4418-1-yevhen.orlov@plvision.eu
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9c0c2c7aa23cbf78277557cfe8ec8bb7689225fe
Author: Yevhen Orlov <yevhen.orlov@plvision.eu>
Date:   Tue Jan 11 03:08:26 2022 +0200

    net: marvell: prestera: Cleanup router struct
    
    Field "aborted" was added in
    69204174cc5c ("net: marvell: prestera: Add prestera router infra").
    It will not be used. So remove.
    
    Signed-off-by: Yevhen Orlov <yevhen.orlov@plvision.eu>
    Link: https://lore.kernel.org/r/20220111010826.3779-1-yevhen.orlov@plvision.eu
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7e7b69654724c72bd3219b71f58937845dca0b2b
Merge: daadb3bd0e8d3 f857acfc457ea
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed Jan 12 10:08:11 2022 -0800

    Merge tag 'dma-mapping-5.17' of git://git.infradead.org/users/hch/dma-mapping
    
    Pull dma-mapping updates from Christoph Hellwig:
    
     - refactor the dma-direct coherent allocator
    
     - turn an macro into an inline in scatterlist.h (Logan Gunthorpe)
    
    * tag 'dma-mapping-5.17' of git://git.infradead.org/users/hch/dma-mapping:
      lib/scatterlist: cleanup macros into static inline functions
      dma-direct: add a dma_direct_use_pool helper
      dma-direct: factor the swiotlb code out of __dma_direct_alloc_pages
      dma-direct: drop two CONFIG_DMA_RESTRICTED_POOL conditionals
      dma-direct: warn if there is no pool for force unencrypted allocations
      dma-direct: fail allocations that can't be made coherent
      dma-direct: refactor the !coherent checks in dma_direct_alloc
      dma-direct: factor out a helper for DMA_ATTR_NO_KERNEL_MAPPING allocations
      dma-direct: clean up the remapping checks in dma_direct_alloc
      dma-direct: always leak memory that can't be re-encrypted
      dma-direct: don't call dma_set_decrypted for remapped allocations
      dma-direct: factor out dma_set_{de,en}crypted helpers

commit c0dd94558d0e473aa92254e1c48a47900c911e69
Author: Ian Rogers <irogers@google.com>
Date:   Thu Nov 25 23:13:05 2021 -0800

    perf pmu-events: Don't lower case MetricExpr
    
    This patch changes MetricExpr to be written out in the same case. This
    enables events in metrics to use modifiers like 'G' which currently
    yield parse errors when made lower case. To keep tests passing the
    literal #smt_on is compared in a non-case sensitive way - #SMT_on is
    present in at least SkylakeX metrics.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: http://lore.kernel.org/lkml/20211126071305.3733878-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f56ef30a31d388663e78b9be687d67748c9b7297
Author: Ian Rogers <irogers@google.com>
Date:   Tue Nov 23 16:12:28 2021 -0800

    perf expr: Add debug logging for literals
    
    Useful for diagnosing problems with metrics.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Konstantin Khlebnikov <koct9i@gmail.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: http://lore.kernel.org/lkml/20211124001231.3277836-1-irogers@google.com
    [ Fixed up perf_cpu conflict, i.e. we need to append ".cpu" to cpu__max_present_cpu() result ]
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 4a9bca86806fa6fc4fbccf050c1bd36a4778948a
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Fri Jan 7 17:45:51 2022 -0800

    xfs: fix online fsck handling of v5 feature bits on secondary supers
    
    While I was auditing the code in xfs_repair that adds feature bits to
    existing V5 filesystems, I decided to have a look at how online fsck
    handles feature bits, and I found a few problems:
    
    1) ATTR2 is added to the primary super when an xattr is set to a file,
    but that isn't consistently propagated to secondary supers.  This isn't
    a corruption, merely a discrepancy that repair will fix if it ever has
    to restore the primary from a secondary.  Hence, if we find a mismatch
    on a secondary, this is a preen condition, not a corruption.
    
    2) There are more compat and ro_compat features now than there used to
    be, but we mask off the newer features from testing.  This means we
    ignore inconsistencies in the INOBTCOUNT and BIGTIME features, which is
    wrong.  Get rid of the masking and compare directly.
    
    3) NEEDSREPAIR, when set on a secondary, is ignored by everyone.  Hence
    a mismatch here should also be flagged for preening, and online repair
    should clear the flag.  Right now we ignore it due to (2).
    
    4) log_incompat features are ephemeral, since we can clear the feature
    bit as soon as the log no longer contains live records for a particular
    log feature.  As such, the only copy we care about is the one in the
    primary super.  If we find any bits set in the secondary super, we
    should flag that for preening, and clear the bits if the user elects to
    repair it.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit 6dd8646939a770e4ec0220c1c19d6af25c5877b7
Author: Ian Rogers <irogers@google.com>
Date:   Tue Nov 23 16:12:31 2021 -0800

    perf tools: Probe non-deprecated sysfs path 1st
    
    Following Documentation/ABI/stable/sysfs-devices-system-cpu the
    /sys/devices/system/cpu/cpuX/topology/core_cpus is deprecated in favor
    of thread_siblings, so probe thread_siblings before falling back on
    core_cpus.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Konstantin Khlebnikov <koct9i@gmail.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: https://lore.kernel.org/r/20211124001231.3277836-4-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 0ce05781f4905fcfbbb489519e36be71c7b0bbcc
Author: Ian Rogers <irogers@google.com>
Date:   Tue Nov 23 16:12:30 2021 -0800

    perf tools: Fix SMT fallback with large core counts
    
    strtoull can only read a 64-bit bitmap. On an AMD EPYC core_cpus may look
    like:
    
    00000000,00000000,00000000,00000001,00000000,00000000,00000000,00000001
    
    and so the sibling wasn't spotted. Fix by writing a simple hweight string
    parser.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Konstantin Khlebnikov <koct9i@gmail.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: https://lore.kernel.org/r/20211124001231.3277836-3-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 6d18804b963b78dcd53851f11e9080408b3d85c2
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:51 2022 -0800

    perf cpumap: Give CPUs their own type
    
    A common problem is confusing CPU map indices with the CPU, by wrapping
    the CPU with a struct then this is avoided. This approach is similar to
    atomic_t.
    
    Committer notes:
    
    To make it build with BUILD_BPF_SKEL=1 these files needed the
    conversions to 'struct perf_cpu' usage:
    
      tools/perf/util/bpf_counter.c
      tools/perf/util/bpf_counter_cgroup.c
      tools/perf/util/bpf_ftrace.c
    
    Also perf_env__get_cpu() was removed back in "perf cpumap: Switch
    cpu_map__build_map to cpu function".
    
    Additionally these needed to be fixed for the ARM builds to complete:
    
      tools/perf/arch/arm/util/cs-etm.c
      tools/perf/arch/arm64/util/pmu.c
    
    Suggested-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-49-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit ce37ab3eb2490aba60ab1a622a4c6c6ee9a7cc66
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:50 2022 -0800

    perf stat: Correct first_shadow_cpu to return index
    
    perf_stat__update_shadow_stats() and perf_stat__print_shadow_stats() use
    a cpu map index rather than a CPU, but first_shadow_cpu is returning the
    wrong value for this. Change first_shadow_cpu to
    first_shadow_cpu_map_idx to make things agree.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-48-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b57af1b4017abff969425dffd6f59ddfdedce8cb
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:49 2022 -0800

    perf script: Fix flipped index and cpu
    
    perf_counts are accessed by the densely packed index.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-47-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 84d2f4f0375d4857f9f9e57a9ad75cbf0f34e108
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:48 2022 -0800

    perf c2c: Use more intention revealing iterator
    
    Use perf_cpu_map__for_each_cpu() in setup_nodes.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-46-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7263f3498ba8b6e65c1d810ccafec64cd61a6dc1
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:47 2022 -0800

    perf bpf: Rename 'cpu' to 'cpu_map_idx'
    
    Synchronize the caller in evsel with the called function.
    
    Shorten 3 lines of code in bperf_read by using
    perf_cpu_map__for_each_cpu().
    
    This code is frequently using variables named cpu as cpu map indices,
    which doesn't matter as all CPUs are in the CPU map. It is strange in
    some cases the cpumap is used at all.
    
    Committer notes:
    
    Found when building with BUILD_BPF_SKEL=1:
    
    Remove unused 'num_cpu' variable in bperf__read().
    
    Make 'j' an 'int' as it is used in perf_cpu_map__for_each_cpu() to compare against an 'int'
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-45-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 91802e73f77146d69afa0be7eafc983ec84b2bb0
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:46 2022 -0800

    libperf: Sync evsel documentation
    
    cpu was renamed cpu_map_idx, for clarity.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-44-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 5b1af93dbc7e64ab1b872129cfe1f2318cc29c67
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:45 2022 -0800

    perf stat: Swap variable name cpu to index
    
    The use of CPU is error prone, switch to cpu_map_idx.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-43-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 379c224bef724cf52bd3d2364d29fc63f3e743d3
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:44 2022 -0800

    perf stat: Correct check_per_pkg() cpu
    
    Code was incorrectly using the cpu map index as the CPU.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-42-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit aa11e55a39950c0151e12abd30c7223dfc6f6a2c
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:43 2022 -0800

    perf test: Use perf_cpu_map__for_each_cpu()
    
    Clean up variable naming to make cpu and index clearer.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-41-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 6f844b1fdd3bc3a25995ff83edea32a73bfa72d9
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:42 2022 -0800

    perf evsel: Rename variable cpu to index
    
    Make naming less error prone.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-40-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 1fa497d4c01d497e25131ccdd5def6f24dd1f330
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:41 2022 -0800

    perf evsel: Reduce scope of evsel__ignore_missing_thread
    
    Move to being static.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-39-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 2daa08c4d9cd9d0845094d718920e5d105c11558
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:40 2022 -0800

    perf evsel: Rename CPU around get_group_fd
    
    CPU is really a cpu map index, change names to make code more intention
    revealing.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-38-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit da8c94c065174099853a207d9716a49d339b265f
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:39 2022 -0800

    perf stat: Correct variable name for read counter
    
    Switch from cpu to cpu_map_idx to reduce confusion.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-37-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7ac0089d138f80dcd7ba8ca368a9b2bdfe780b16
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:38 2022 -0800

    perf evsel: Pass cpu not cpu map index to synthesize
    
    evsel__write_stat_event() was incorrectly passing a cpu map index rather
    than a CPU to perf_event__synthesize_stat().
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-36-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 472832d2c000b9611feaea66fe521055c3dbf17a
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:37 2022 -0800

    perf evlist: Refactor evlist__for_each_cpu()
    
    Previously evlist__for_each_cpu() needed to iterate over the evlist in
    an inner loop and call "skip" routines. Refactor this so that the
    iteratr is smarter and the next function can update both the current CPU
    and evsel.
    
    By using a cpu map index, fix apparent off-by-1 in __run_perf_stat's
    call to perf_evsel__close_cpu().
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-35-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 80b82f3b65e94ba22d3f12a98f7ecc56cc14c903
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:36 2022 -0800

    libperf: Allow NULL in perf_cpu_map__idx()
    
    Return -1, not found, if NULL is passed.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-34-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f9551b3f6249cfe8ea5b5f8716675ccf2f6ec737
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:35 2022 -0800

    perf script: Use for each cpu to aid readability
    
    Use perf_cpu_map__for_each_cpu() to help with readability.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-33-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7ea82fbee4598e51e8bf47566b252cd5745d5b17
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:34 2022 -0800

    perf stat: Use perf_cpu_map__for_each_cpu()
    
    Correct in print_counter() where an index was being used as a cpu.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-32-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit ab90caa7b2d0b708cfee16b33325ca24de4d8f25
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:33 2022 -0800

    perf stat: Rename aggr_data cpu to imply it's an index
    
    Trying to make cpu maps less error prone.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-31-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7316268ff740c29dfb52649ff8074a5aa17ec0ce
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:32 2022 -0800

    perf counts: Switch name cpu to cpu_map_idx
    
    Try to reduce confusion in particular when the cpu map doesn't contain
    an entry for every CPU.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-30-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 47ffe806674f67e729627edd689b10827b1790eb
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:31 2022 -0800

    libperf: Use cpu not index for evsel mmap
    
    Fix issue where evsel's CPU map index was being used as the mmap cpu.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-29-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7e3d1784c8a4d9c643a6ed0a2c44ee94dee8f7a6
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:30 2022 -0800

    libperf: Switch cpu to more accurate cpu_map_idx
    
    Modify variable names and adopt perf_cpu_map__for_each_cpu() in
    perf_evsel__open().
    
    Renaming is done by looking for consistency in API usage.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-28-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 2ca0a3718da24953689b1771589ac63b60f17358
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:29 2022 -0800

    perf evsel: Derive CPUs and threads in alloc_counts
    
    Passing the number of CPUs and threads allows for an evsel's counts to
    be mismatched to its cpu map. To avoid this always derive the counts
    size from the cpu map. Change openat-syscall-all-cpus to set the cpus
    to allow for this to work.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-27-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7365f105e37429d28757f7f68d4850723ce18aa1
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:28 2022 -0800

    perf stat-display: Avoid use of core for CPU
    
    Correct use of cpumap index in print_no_aggr_metric().
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-26-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 34794913e2dc08a464499f795073a021feeb3b47
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:27 2022 -0800

    perf cpumap: Add CPU to aggr_cpu_id
    
    With no aggregration, such as 'perf stat -A', the aggr_cpu_id lacks a
    way to describe per CPU aggregation and the core is set to the CPU in
    places like print_counter_aggrdata in stat-display.c.
    
    Setting the core to the CPU is undesirable as the CPU will exceed valid
    core values and lead to confusion. Add a CPU variable to address this.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-25-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit f9e891ea172235f902972069b87be3bdc7c48f5a
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:26 2022 -0800

    perf stat: Fix memory leak in check_per_pkg()
    
    If the key is already present then free the key used for lookup.
    
    Found with:
    $ perf stat -M IO_Read_BW /bin/true
    
    ==1749112==ERROR: LeakSanitizer: detected memory leaks
    
    Direct leak of 32 byte(s) in 4 object(s) allocated from:
        #0 0x7f6f6fa7d7cf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
        #1 0x55acecd9d7a6 in check_per_pkg util/stat.c:343
        #2 0x55acecd9d9c5 in process_counter_values util/stat.c:365
        #3 0x55acecd9e0ab in process_counter_maps util/stat.c:421
        #4 0x55acecd9e292 in perf_stat_process_counter util/stat.c:443
        #5 0x55aceca8553e in read_counters ./tools/perf/builtin-stat.c:470
        #6 0x55aceca88fe3 in __run_perf_stat ./tools/perf/builtin-stat.c:1023
        #7 0x55aceca89146 in run_perf_stat ./tools/perf/builtin-stat.c:1048
        #8 0x55aceca90858 in cmd_stat ./tools/perf/builtin-stat.c:2555
        #9 0x55acecc05fa5 in run_builtin ./tools/perf/perf.c:313
        #10 0x55acecc064fe in handle_internal_command ./tools/perf/perf.c:365
        #11 0x55acecc068bb in run_argv ./tools/perf/perf.c:409
        #12 0x55acecc070aa in main ./tools/perf/perf.c:539
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-24-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit bd26bddfd93688d10984251249b84e1f6d91de27
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:25 2022 -0800

    perf cpumap: Trim the cpu_aggr_map
    
    cpu_aggr_map__new() removes duplicates, when this happens shrink the
    array.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-23-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 92aad5c33f531187cc6013c8e51620212cdfefe1
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:24 2022 -0800

    perf cpumap: Add some comments to cpu_aggr_map
    
    Move cpu_aggr_map__empty_new() to be with other cpu_aggr_map function.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-22-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit dfc66beff7fa95b9eb507ccb48fb325569bc2f74
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:23 2022 -0800

    perf cpumap: Move 'has' function to libperf
    
    Make the cpu map argument const for consistency with the rest of the
    API. Modify cpu_map__idx accordingly.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-21-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 973aeb3c7ada35b75442126c745bb6074cb3e172
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:22 2022 -0800

    perf cpumap: Rename cpu_map__get_X_aggr_by_cpu functions
    
    The functions don't use a cpu_map so reduce them to being like
    constructors of aggr_cpu_id.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-20-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 5f50e15c1510c77b37e10c6b22912bf4bf11476b
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:21 2022 -0800

    perf cpumap: Refactor cpu_map__build_map()
    
    Turn it into a cpu_aggr_map__new(). Pass helper functions. Refactor
    builtin-stat calls to manually pass function pointers. Try to reduce
    some copy-paste code.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-19-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit adff2c634357115a0f94a9a5054061b497df7f72
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:20 2022 -0800

    perf cpumap: Remove cpu_map__cpu(), use libperf function
    
    Switch the remaining few users of cpu_map__cpu() to perf_cpu_map__cpu()
    and remove the function.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-18-irogers@google.com
    [ Did the conversion to perf_ftrace__latency_prepare_bpf() as well, used when building with BUILD_BPF_SKEL=1 ]
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 4e90e5cc74c6b1c1b9abff8b53cec5be1fb5e839
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:19 2022 -0800

    perf cpumap: Remove map from function names that don't use a map
    
    Move to the cpu name and document for consistency.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-17-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 194a3a202564153493789997643181737a6ae4b9
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:18 2022 -0800

    perf cpumap: Document cpu__get_node() and remove redundant function
    
    cpu_map__get_node_id() isn't used externally and merely delegates to
    cpu__get_node().
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-16-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 51b826fadf4fc42c8614b752b6cb0cb516589ade
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:17 2022 -0800

    perf cpumap: Rename empty functions
    
    Remove cpu_map from name as a cpu_map isn't used. Pass a const pointer
    rather than by value to avoid unnecessary copying.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-15-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3ac23d199c2bc3bc2a2b31c803e7c5d841959670
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:16 2022 -0800

    perf cpumap: Simplify equal function name
    
    Rename cpu_map__compare_aggr_cpu_id() to aggr_cpu_id__equal(), the
    cpu_map part of the name is misleading. Equal better describes the
    function than compare.
    
    Switch to const pointer rather than value as struct given the number of
    variables in aggr_cpu_id().
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-14-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 63e0fa873d8820b996a01a83d832bf1b3969e9b6
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:15 2022 -0800

    perf cpumap: Remove unused cpu_map__socket()
    
    Unused function so remove.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-13-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 49679da388f4c45b0ca444dcf8bb5f59a02f8f4e
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:14 2022 -0800

    perf cpumap: Add comments to aggr_cpu_id()
    
    This code is already tested in topology.c.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-12-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 86d94048e234c94af88a528ab4d5ef16e8a89f8a
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:13 2022 -0800

    perf cpumap: Remove map+index get_node()
    
    Migrate final users to appropriate cpu variant.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-11-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 3f6233dc7798044637426ae1099d88aa375c467f
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:12 2022 -0800

    perf cpumap: Remove map+index get_core()
    
    Migrate final users to appropriate cpu variant.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-10-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 1cdae3d6734779a637bc4e6ec24e7f615b4e71be
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:11 2022 -0800

    perf cpumap: Remove map+index get_die()
    
    Migrate final users to appropriate cpu variant.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-9-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 448a69d9f34d02920cffba741ca0a2e34a5bb316
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:10 2022 -0800

    perf cpumap: Remove map+index get_socket()
    
    Migrate final users to appropriate cpu variant.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-8-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit eff54c24bb147afc0a1423b49bfa1b8eaa85a88f
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:09 2022 -0800

    perf cpumap: Switch cpu_map__build_map() to cpu function
    
    Avoid error prone cpu_map + idx variant. Remove now unused functions.
    
    Committer notes:
    
    Remove by now unused perf_env__get_cpu().
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-7-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 88031a0de7d68d132014154b9e5307428e8ed70d
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:08 2022 -0800

    perf stat: Switch to cpu version of cpu_map__get()
    
    Avoid possible bugs where the wrong index is passed with the cpu_map.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-6-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit a023283fadef8a3f6916ba2b0c37955d76ffaf4d
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:07 2022 -0800

    perf stat: Switch aggregation to use for_each loop
    
    Tidy up the use of cpu and index to hopefully make the code less error
    prone. Avoid unused warnings with (void) which will be removed in a
    later patch.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-5-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 01843ca0197783d0951a1948ebeaaed9a47ce55d
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:06 2022 -0800

    perf stat: Correct aggregation CPU map
    
    Switch the perf_cpu_map in aggr_update_shadow from
    the evlist to the counter's cpu map, so the index is appropriate. This
    addresses a problem where uncore counts, with a cpumap like:
    $ cat /sys/devices/uncore_imc_0/cpumask
    0,18
    Don't aggregate counts in CPUs based on the index of those values in the
    cpumap (0 and 1) but on the actual CPU (0 and 18). Thereby correcting
    metric calculations in per-socket mode for counters without a full
    cpumask.
    
    On a SkylakeX with a tweaked DRAM_BW_Use metric, to remove unnecessary
    scaling, this gives:
    
    Before:
    $ /perf stat --per-socket -M DRAM_BW_Use -I 1000
         1.001102293 S0        1              27.01 MiB  uncore_imc/cas_count_write/ #   103.00 DRAM_BW_Use
         1.001102293 S0        1              30.22 MiB  uncore_imc/cas_count_read/
         1.001102293 S0        1      1,001,102,293 ns   duration_time
         1.001102293 S1        1              20.10 MiB  uncore_imc/cas_count_write/ #     0.00 DRAM_BW_Use
         1.001102293 S1        1              32.74 MiB  uncore_imc/cas_count_read/
         1.001102293 S1        0      <not counted> ns   duration_time
         2.003517973 S0        1              83.04 MiB  uncore_imc/cas_count_write/ #   920.00 DRAM_BW_Use
         2.003517973 S0        1             145.95 MiB  uncore_imc/cas_count_read/
         2.003517973 S0        1      1,002,415,680 ns   duration_time
         2.003517973 S1        1             302.45 MiB  uncore_imc/cas_count_write/ #     0.00 DRAM_BW_Use
         2.003517973 S1        1             290.99 MiB  uncore_imc/cas_count_read/
         2.003517973 S1        0      <not counted> ns   duration_time
    
    After:
    $ perf stat --per-socket -M DRAM_BW_Use -I 1000
         1.001080840 S0        1              24.96 MiB  uncore_imc/cas_count_write/ #    54.00 DRAM_BW_Use
         1.001080840 S0        1              33.64 MiB  uncore_imc/cas_count_read/
         1.001080840 S0        1      1,001,080,840 ns   duration_time
         1.001080840 S1        1              42.43 MiB  uncore_imc/cas_count_write/ #    84.00 DRAM_BW_Use
         1.001080840 S1        1              47.05 MiB  uncore_imc/cas_count_read/
         1.001080840 S1        0      <not counted> ns   duration_time
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Tested-by: John Garry <john.garry@huawei.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: James Clark <james.clark@arm.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-4-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit ca2c9b76bc3c75ac116ef199b75e7ca4e27e7acb
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:05 2022 -0800

    perf stat: Add aggr creators that are passed a cpu
    
    The cpu_map and index can get confused. Add variants of the cpu_map__get
    routines that are passed a cpu. Make the existing cpu_map__get routines
    use the new functions with a view to remove them when no longer used.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: John Garry <john.garry@huawei.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-3-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 818ab78c03aad94fabc18d386e9c73b539a1f447
Author: Ian Rogers <irogers@google.com>
Date:   Tue Jan 4 22:13:04 2022 -0800

    libperf: Add comments to 'struct perf_cpu_map'
    
    A particular observed problem is confusing the index with the CPU value,
    documentation should hopefully reduce this type of problem.
    
    Reviewed-by: James Clark <james.clark@arm.com>
    Reviewed-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Kan Liang <kan.liang@linux.intel.com>
    Cc: Leo Yan <leo.yan@linaro.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
    Cc: Mike Leach <mike.leach@linaro.org>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Paul Clarke <pc@us.ibm.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Riccardo Mancini <rickyman7@gmail.com>
    Cc: Stephane Eranian <eranian@google.com>
    Cc: Suzuki Poulouse <suzuki.poulose@arm.com>
    Cc: Vineet Singh <vineet.singh@intel.com>
    Cc: coresight@lists.linaro.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: zhengjun.xing@intel.com
    Link: https://lore.kernel.org/r/20220105061351.120843-2-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit dcffc5ebb80dd5887b91091b8ecd082c9ed75361
Author: Ian Rogers <irogers@google.com>
Date:   Thu Dec 23 10:39:48 2021 -0800

    perf evsel: Improve error message for uncore events
    
    When a group has multiple events and the leader fails it can yield
    errors like:
    
      $ perf stat -e '{uncore_imc/cas_count_read/},instructions' /bin/true
      Error:
      The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (uncore_imc/cas_count_read/).
      /bin/dmesg | grep -i perf may provide additional information.
    
    However, when not the group leader <not supported> is given:
    
      $ perf stat -e '{instructions,uncore_imc/cas_count_read/}' /bin/true
      ...
               1,619,057      instructions
         <not supported> MiB  uncore_imc/cas_count_read/
    
    This is necessary because get_group_fd will fail if the leader fails and
    is the direct result of the check on line 750 of builtin-stat.c in
    stat_handle_error that returns COUNTER_SKIP for the latter case.
    
    This patch improves the error message to:
    
      $ perf stat -e '{uncore_imc/cas_count_read/},instructions' /bin/true
      Error:
      Invalid event (uncore_imc/cas_count_read/) in per-thread mode, enable system wide with '-a'.
    
    v2. Changed the test to use !target__has_cpu as suggested by Namhyung Kim.
    
    Signed-off-by: Ian Rogers <irogers@google.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: https://lore.kernel.org/r/20211223183948.3423989-2-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit b4bb6f05e4b25e66825956006c3d5cbe5b73eaec
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Jan 12 14:21:45 2022 -0300

    Revert "perf powerpc: Add data source encodings for power10 platform"
    
    This was in a patchkit mixing up kernel with tools/ parts and I
    mistakenly got it merged in the perf tools tree, revert it, it'll go via
    the PowerPC kernel tree.
    
    This reverts commit af2b24f228a0373ac65eb7a502e0bc31e2c0269d.
    
    Cc: kajoljain <kjain@linux.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Link: http://lore.kernel.org/lkml/20220112171659.531d22ce@canb.auug.org.au
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 8de78328f041f10a2b546fdb3791a87ba6b742e6
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Wed Jan 12 14:19:21 2022 -0300

    Revert "perf powerpc: Add encodings to represent data based on newer composite PERF_MEM_LVLNUM* fields"
    
    This was in a patchkit mixing up kernel with tools/ parts and I
    mistakenly got it merged in the perf tools tree, revert it, it'll go via
    the PowerPC kernel tree.
    
    This reverts commit 0ebce3d65f1f53c936fdd51e975bd876ba7ed64f.
    
    Cc: kajoljain <kjain@linux.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Stephen Rothwell <sfr@canb.auug.org.au>
    Link: http://lore.kernel.org/lkml/20220112171659.531d22ce@canb.auug.org.au
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 62942e9fda9fd1def10ffcbd5e1c025b3c9eec17
Author: Adrian Hunter <adrian.hunter@intel.com>
Date:   Wed Jan 12 10:50:57 2022 +0200

    perf script: Fix hex dump character output
    
    Using grep -C with perf script -D can give erroneous results as grep loses
    lines due to non-printable characters, for example, below the 0020, 0060
    and 0070 lines are missing:
    
     $ perf script -D | grep -C10 AUX | head
     .  0010:  08 00 00 00 00 00 00 00 1f 00 00 00 00 00 00 00  ................
     .  0030:  01 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00  ................
     .  0040:  00 08 00 00 00 00 00 00 02 00 00 00 00 00 00 00  ................
     .  0050:  00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00  ................
     .  0080:  02 00 00 00 00 00 00 00 1b 00 00 00 00 00 00 00  ................
     .  0090:  00 00 00 00 00 00 00 00                          ........
    
     0 0 0x450 [0x98]: PERF_RECORD_AUXTRACE_INFO type: 1
       PMU Type            8
       Time Shift          31
    
    perf's isprint() is a custom implementation from the kernel, but the
    kernel's _ctype appears to include characters from Latin-1 Supplement which
    is not compatible with, for example, UTF-8. Fix by checking also isascii().
    
    After:
    
     $ tools/perf/perf script -D | grep -C10 AUX | head
     .  0010:  08 00 00 00 00 00 00 00 1f 00 00 00 00 00 00 00  ................
     .  0020:  03 84 32 2f 00 00 00 00 63 7c 4f d2 fa ff ff ff  ..2/....c|O.....
     .  0030:  01 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00  ................
     .  0040:  00 08 00 00 00 00 00 00 02 00 00 00 00 00 00 00  ................
     .  0050:  00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00  ................
     .  0060:  00 02 00 00 00 00 00 00 00 c0 03 00 00 00 00 00  ................
     .  0070:  e2 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00  ................
     .  0080:  02 00 00 00 00 00 00 00 1b 00 00 00 00 00 00 00  ................
     .  0090:  00 00 00 00 00 00 00 00                          ........
    
    Fixes: 3052ba56bcb58904 ("tools perf: Move from sane_ctype.h obtained from git to the Linux's original")
    Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Link: http://lore.kernel.org/lkml/20220112085057.277205-1-adrian.hunter@intel.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 2716a5271d54e401856113ef7bdec1e06260f1dd
Merge: 4e5bd03ae3465 72f1f7e46c6e9
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Wed Jan 12 09:05:06 2022 -0800

    Merge branch 'arm-ox810se-add-ethernet-support'
    
    Neil Armstrong says:
    
    ====================
    ARM: ox810se: Add Ethernet support
    
    This adds support for the Synopsys DWMAC controller found in the
    OX820SE SoC, by using almost the same glue code as the OX820.
    ====================
    
    Link: https://lore.kernel.org/r/20220104145646.135877-1-narmstrong@baylibre.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 72f1f7e46c6e96b2ae300d750de01ac75d625b4e
Author: Neil Armstrong <narmstrong@baylibre.com>
Date:   Tue Jan 4 15:56:45 2022 +0100

    net: stmmac: dwmac-oxnas: Add support for OX810SE
    
    Add support for OX810SE dwmac glue setup, which is a simplified version
    of the OX820 introduced later with more control on the PHY interface.
    
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8973d7b8638f1c2615eec495dfe70122a01a9e1b
Author: Neil Armstrong <narmstrong@baylibre.com>
Date:   Tue Jan 4 15:56:44 2022 +0100

    dt-bindings: net: oxnas-dwmac: Add bindings for OX810SE
    
    Add SoC specific bindings for OX810SE support.
    
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e623611b4d3f722b57ceeaf4368ac787837408e7
Merge: 785576c9356fb b398123bff3bc
Author: Rob Herring <robh@kernel.org>
Date:   Wed Jan 12 10:14:09 2022 -0600

    Merge branch 'dt/linus' into dt/next
    
    Pick a fix which didn't make it into v5.16.

commit 785576c9356fb249e2715fe25f47c773385574ce
Author: Rob Herring <robh@kernel.org>
Date:   Tue Jan 11 11:02:47 2022 -0600

    dt-bindings: net: mdio: Drop resets/reset-names child properties
    
    resets/reset-names are device specific and don't belong in the MDIO bus
    schema. For example, it doesn't match what is defined for the
    "qca,ar9331-switch" binding which defines "reset-names" to be "switch"
    rather than "phy". Neither name is that useful IMO.
    
    Other child properties are also device specific, but those won't conflict
    with device schemas.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220111170248.3160841-1-robh@kernel.org

commit 9cdbeec4096804083944d05da96bbaf59a1eb4f9
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Tue Jan 11 12:11:14 2022 +0100

    x86/entry_32: Fix segment exceptions
    
    The LKP robot reported that commit in Fixes: caused a failure. Turns out
    the ldt_gdt_32 selftest turns into an infinite loop trying to clear the
    segment.
    
    As discovered by Sean, what happens is that PARANOID_EXIT_TO_KERNEL_MODE
    in the handle_exception_return path overwrites the entry stack data with
    the task stack data, restoring the "bad" segment value.
    
    Instead of having the exception retry the instruction, have it emulate
    the full instruction. Replace EX_TYPE_POP_ZERO with EX_TYPE_POP_REG
    which will do the equivalent of: POP %reg; MOV $imm, %reg.
    
    In order to encode the segment registers, add them as registers 8-11 for
    32-bit.
    
    By setting regs->[defg]s the (nested) RESTORE_REGS will pop this value
    at the end of the exception handler and by increasing regs->sp, it will
    have skipped the stack slot.
    
    This was debugged by Sean Christopherson <seanjc@google.com>.
    
     [ bp: Add EX_REG_GS too. ]
    
    Fixes: aa93e2ad7464 ("x86/entry_32: Remove .fixup usage")
    Reported-by: kernel test robot <oliver.sang@intel.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: Borislav Petkov <bp@suse.de>
    Link: https://lore.kernel.org/r/Yd1l0gInc4zRcnt/@hirez.programming.kicks-ass.net

commit c96f195deeefecd8ef95c5aa508671dd246bf119
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Tue Jan 11 17:53:29 2022 +0100

    ACPI: scan: Rename label in acpi_scan_init()
    
    Rename the "out" label in acpi_scan_init() to "unlock", which is
    a better match for its purpose, and fix up its alignment.
    
    No functional impact.
    
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>

commit 681e7187aef46f8d4e0fd0ddd2f888e3e5533cb2
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Tue Jan 11 17:52:00 2022 +0100

    ACPI: scan: Simplify initialization of power and sleep buttons
    
    It should be perfectly fine to use ACPI if the "fixed" power or sleep
    buttons cannot be initialized.  Moreover, running acpi_bus_scan()
    successfully on ACPI_ROOT_OBJECT generally causes many devices to
    be enumerated and probed, possibly including the entire PCI bus, so
    unregistering acpi_root if the registration of the "fixed" buttons
    fails is rather unhelpful.
    
    For this reason, do not fail acpi_scan_init() when
    acpi_bus_scan_fixed() fails and turn the latter into a void function.
    
    While at it, drop the outdated and misleading comment from
    acpi_bus_scan_fixed().
    
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>

commit b6c55b162bcee62c43c18e59f38a4590be543032
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Tue Jan 11 17:50:22 2022 +0100

    ACPI: scan: Change acpi_scan_init() return value type to void
    
    The only caller of acpi_scan_init(), acpi_init(), doesn't check its
    return value, so turn it into a void function.
    
    This avoids complaints from the Smatch static checker that the
    function should return a negative error code when it fails, which
    is not really a problem in this particular case.
    
    No intentional functional impact.
    
    Link: https://lore.kernel.org/linux-acpi/20220106082317.GA9123@kili/
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
    Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Reviewed-by: Hans de Goede <hdegoede@redhat.com>

commit 4e5bd03ae34652cd932ab4c91c71c511793df75c
Author: Jie Wang <wangjie125@huawei.com>
Date:   Wed Jan 12 20:54:18 2022 +0800

    net: bonding: fix bond_xmit_broadcast return value error bug
    
    In Linux bonding scenario, one packet is copied to several copies and sent
    by all slave device of bond0 in mode 3(broadcast mode). The mode 3 xmit
    function bond_xmit_broadcast() only ueses the last slave device's tx result
    as the final result. In this case, if the last slave device is down, then
    it always return NET_XMIT_DROP, even though the other slave devices xmit
    success. It may cause the tx statistics error, and cause the application
    (e.g. scp) consider the network is unreachable.
    
    For example, use the following command to configure server A.
    
    echo 3 > /sys/class/net/bond0/bonding/mode
    ifconfig bond0 up
    ifenslave bond0 eth0 eth1
    ifconfig bond0 192.168.1.125
    ifconfig eth0 up
    ifconfig eth1 down
    The slave device eth0 and eth1 are connected to server B(192.168.1.107).
    Run the ping 192.168.1.107 -c 3 -i 0.2 command, the following information
    is displayed.
    
    PING 192.168.1.107 (192.168.1.107) 56(84) bytes of data.
    64 bytes from 192.168.1.107: icmp_seq=1 ttl=64 time=0.077 ms
    64 bytes from 192.168.1.107: icmp_seq=2 ttl=64 time=0.056 ms
    64 bytes from 192.168.1.107: icmp_seq=3 ttl=64 time=0.051 ms
    
     192.168.1.107 ping statistics
    0 packets transmitted, 3 received
    
    Actually, the slave device eth0 of the bond successfully sends three
    ICMP packets, but the result shows that 0 packets are transmitted.
    
    Also if we use scp command to get remote files, the command end with the
    following printings.
    
    ssh_exchange_identification: read: Connection timed out
    
    So this patch modifies the bond_xmit_broadcast to return NET_XMIT_SUCCESS
    if one slave device in the bond sends packets successfully. If all slave
    devices send packets fail, the discarded packets stats is increased. The
    skb is released when there is no slave device in the bond or the last slave
    device is down.
    
    Fixes: ae46f184bc1f ("bonding: propagate transmit status")
    Signed-off-by: Jie Wang <wangjie125@huawei.com>
    Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 7b9b1d449a7cef675d6926c4538edee8e601d823
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 12 04:59:39 2022 -0800

    net/smc: fix possible NULL deref in smc_pnet_add_eth()
    
    I missed that @ndev value can be NULL.
    
    I prefer not factorizing this NULL check, and instead
    clearly document where a NULL might be expected.
    
    general protection fault, probably for non-canonical address 0xdffffc00000000ba: 0000 [#1] PREEMPT SMP KASAN
    KASAN: null-ptr-deref in range [0x00000000000005d0-0x00000000000005d7]
    CPU: 0 PID: 19875 Comm: syz-executor.2 Not tainted 5.16.0-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:__lock_acquire+0xd7a/0x5470 kernel/locking/lockdep.c:4897
    Code: 14 0e 41 bf 01 00 00 00 0f 86 c8 00 00 00 89 05 5c 20 14 0e e9 bd 00 00 00 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 9f 2e 00 00 49 81 3e 20 c5 1a 8f 0f 84 52 f3 ff
    RSP: 0018:ffffc900057071d0 EFLAGS: 00010002
    RAX: dffffc0000000000 RBX: 1ffff92000ae0e65 RCX: 1ffff92000ae0e4c
    RDX: 00000000000000ba RSI: 0000000000000000 RDI: 0000000000000001
    RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000001
    R10: fffffbfff1b24ae2 R11: 000000000008808a R12: 0000000000000000
    R13: ffff888040ca4000 R14: 00000000000005d0 R15: 0000000000000000
    FS:  00007fbd683e0700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000001b2be22000 CR3: 0000000013fea000 CR4: 00000000003526f0
    Call Trace:
     <TASK>
     lock_acquire kernel/locking/lockdep.c:5637 [inline]
     lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602
     __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
     _raw_spin_lock_irqsave+0x39/0x50 kernel/locking/spinlock.c:162
     ref_tracker_alloc+0x182/0x440 lib/ref_tracker.c:84
     netdev_tracker_alloc include/linux/netdevice.h:3859 [inline]
     smc_pnet_add_eth net/smc/smc_pnet.c:372 [inline]
     smc_pnet_enter net/smc/smc_pnet.c:492 [inline]
     smc_pnet_add+0x49a/0x14d0 net/smc/smc_pnet.c:555
     genl_family_rcv_msg_doit+0x228/0x320 net/netlink/genetlink.c:731
     genl_family_rcv_msg net/netlink/genetlink.c:775 [inline]
     genl_rcv_msg+0x328/0x580 net/netlink/genetlink.c:792
     netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494
     genl_rcv+0x24/0x40 net/netlink/genetlink.c:803
     netlink_unicast_kernel net/netlink/af_netlink.c:1317 [inline]
     netlink_unicast+0x539/0x7e0 net/netlink/af_netlink.c:1343
     netlink_sendmsg+0x904/0xe00 net/netlink/af_netlink.c:1919
     sock_sendmsg_nosec net/socket.c:705 [inline]
     sock_sendmsg+0xcf/0x120 net/socket.c:725
     ____sys_sendmsg+0x6e8/0x810 net/socket.c:2413
     ___sys_sendmsg+0xf3/0x170 net/socket.c:2467
     __sys_sendmsg+0xe5/0x1b0 net/socket.c:2496
     do_syscall_x64 arch/x86/entry/common.c:50 [inline]
     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Fixes: b60645248af3 ("net/smc: add net device tracker to struct smc_pnetentry")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit fcfb894d5952786db3b2b2b9cd3a95cdcedb6ff0
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 12 04:53:00 2022 -0800

    net: bridge: fix net device refcount tracking issue in error path
    
    I left one dev_put() in br_add_if() error path and sure enough
    syzbot found its way.
    
    As the tracker is allocated in new_nbp(), we must make sure
    to properly free it.
    
    We have to call dev_put_track(dev, &p->dev_tracker) before
    @p object is freed, of course. This is not an issue because
    br_add_if() owns a reference on @dev.
    
    Fixes: b2dcdc7f731d ("net: bridge: add net device refcount tracker")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0bbed88af55ed804d19aeb23b32b72b29e1435ee
Merge: c12837d1bb310 998c0bd2b3715
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Jan 12 14:39:54 2022 +0000

    Merge branch 'ipa-fixes'
    
    Alex Elder says:
    
    ====================
    net: ipa: fix two replenish bugs
    
    This series contains two fixes for bugs in the IPA receive buffer
    replenishing code.  The (new) second patch defines a bitmap to
    represent endpoint the replenish enabled flag.  Its purpose is to
    prepare for the third patch, which adds an additional flag.
    
    Version 2 of this series uses bitmap operations in the second bug
    fix rather than an atomic variable, as suggested by Jakub.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 998c0bd2b3715244da7639cc4e6a2062cb79c3f4
Author: Alex Elder <elder@linaro.org>
Date:   Wed Jan 12 07:30:12 2022 -0600

    net: ipa: prevent concurrent replenish
    
    We have seen cases where an endpoint RX completion interrupt arrives
    while replenishing for the endpoint is underway.  This causes another
    instance of replenishing to begin as part of completing the receive
    transaction.  If this occurs it can lead to transaction corruption.
    
    Use a new flag to ensure only one replenish instance for an endpoint
    executes at a time.
    
    Fixes: 84f9bd12d46db ("soc: qcom: ipa: IPA endpoints")
    Signed-off-by: Alex Elder <elder@linaro.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c1aaa01dbf4cef95af3e04a5a43986c290e06ea3
Author: Alex Elder <elder@linaro.org>
Date:   Wed Jan 12 07:30:11 2022 -0600

    net: ipa: use a bitmap for endpoint replenish_enabled
    
    Define a new replenish_flags bitmap to contain Boolean flags
    associated with an endpoint's replenishing state.  Replace the
    replenish_enabled field with a flag in that bitmap.  This is to
    prepare for the next patch, which adds another flag.
    
    Signed-off-by: Alex Elder <elder@linaro.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6c0e3b5ce94947b311348c367db9e11dcb2ccc93
Author: Alex Elder <elder@linaro.org>
Date:   Wed Jan 12 07:30:10 2022 -0600

    net: ipa: fix atomic update in ipa_endpoint_replenish()
    
    In ipa_endpoint_replenish(), if an error occurs when attempting to
    replenish a receive buffer, we just quit and try again later.  In
    that case we increment the backlog count to reflect that the attempt
    was unsuccessful.  Then, if the add_one flag was true we increment
    the backlog again.
    
    This second increment is not included in the backlog local variable
    though, and its value determines whether delayed work should be
    scheduled.  This is a bug.
    
    Fix this by determining whether 1 or 2 should be added to the
    backlog before adding it in a atomic_add_return() call.
    
    Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
    Fixes: 84f9bd12d46db ("soc: qcom: ipa: IPA endpoints")
    Signed-off-by: Alex Elder <elder@linaro.org>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c12837d1bb31032bead9060dec99ef310d5b9fb7
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 12 03:14:45 2022 -0800

    ref_tracker: use __GFP_NOFAIL more carefully
    
    syzbot was able to trigger this warning from new_slab()
                    /*
                     * All existing users of the __GFP_NOFAIL are blockable, so warn
                     * of any new users that actually require GFP_NOWAIT
                     */
                    if (WARN_ON_ONCE(!can_direct_reclaim))
                            goto fail;
    
    Indeed, we should use __GFP_NOFAIL if direct reclaim is possible.
    
    Hopefully in the future we will be able to use SLAB_NOFAILSLAB
    option so that syzbot can benefit from full ref_tracker
    even in the presence of memory fault injections.
    
    WARNING: CPU: 0 PID: 13 at mm/page_alloc.c:5081 __alloc_pages_slowpath.constprop.0+0x1b7b/0x20d0 mm/page_alloc.c:5081 mm/page_alloc.c:5081
    Modules linked in:
    CPU: 0 PID: 13 Comm: ksoftirqd/0 Not tainted 5.16.0-rc5-syzkaller #0
    Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
    RIP: 0010:__alloc_pages_slowpath.constprop.0+0x1b7b/0x20d0 mm/page_alloc.c:5081 mm/page_alloc.c:5081
    Code: 90 08 00 00 48 81 c7 d8 04 00 00 48 89 f8 48 c1 e8 03 42 80 3c 30 00 0f 84 f0 ea ff ff e8 3d 82 09 00 e9 e6 ea ff ff 4d 89 fd <0f> 0b 48 b8 00 00 00 00 00 fc ff df 48 8b 54 24 30 48 c1 ea 03 80
    RSP: 0018:ffffc90000d272b8 EFLAGS: 00010246
    
    RAX: 0000000000000000 RBX: ffff88813fffc300 RCX: 0000000000000000
    RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88813fffc348
    RBP: ffff88813fffc300 R08: 00000000000013dc R09: 00000000000013c8
    R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
    R13: ffffc90000d274e8 R14: dffffc0000000000 R15: ffffc90000d274e8
    FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007ffefe6000f8 CR3: 000000001d21e000 CR4: 00000000003506f0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     __alloc_pages+0x412/0x500 mm/page_alloc.c:5382 mm/page_alloc.c:5382
     alloc_pages+0x1a7/0x300 mm/mempolicy.c:2191 mm/mempolicy.c:2191
     alloc_slab_page mm/slub.c:1793 [inline]
     allocate_slab mm/slub.c:1938 [inline]
     alloc_slab_page mm/slub.c:1793 [inline] mm/slub.c:1993
     allocate_slab mm/slub.c:1938 [inline] mm/slub.c:1993
     new_slab+0x349/0x4a0 mm/slub.c:1993 mm/slub.c:1993
     ___slab_alloc+0x918/0xfe0 mm/slub.c:3022 mm/slub.c:3022
     __slab_alloc.constprop.0+0x4d/0xa0 mm/slub.c:3109 mm/slub.c:3109
     slab_alloc_node mm/slub.c:3200 [inline]
     slab_alloc mm/slub.c:3242 [inline]
     slab_alloc_node mm/slub.c:3200 [inline] mm/slub.c:3259
     slab_alloc mm/slub.c:3242 [inline] mm/slub.c:3259
     kmem_cache_alloc_trace+0x289/0x2c0 mm/slub.c:3259 mm/slub.c:3259
     kmalloc include/linux/slab.h:590 [inline]
     kzalloc include/linux/slab.h:724 [inline]
     kmalloc include/linux/slab.h:590 [inline] lib/ref_tracker.c:74
     kzalloc include/linux/slab.h:724 [inline] lib/ref_tracker.c:74
     ref_tracker_alloc+0xe1/0x430 lib/ref_tracker.c:74 lib/ref_tracker.c:74
     netdev_tracker_alloc include/linux/netdevice.h:3855 [inline]
     dev_hold_track include/linux/netdevice.h:3872 [inline]
     netdev_tracker_alloc include/linux/netdevice.h:3855 [inline] net/core/dst.c:52
     dev_hold_track include/linux/netdevice.h:3872 [inline] net/core/dst.c:52
     dst_init+0xe0/0x520 net/core/dst.c:52 net/core/dst.c:52
     dst_alloc+0x16b/0x1f0 net/core/dst.c:96 net/core/dst.c:96
     rt_dst_alloc+0x73/0x450 net/ipv4/route.c:1614 net/ipv4/route.c:1614
     ip_route_input_mc net/ipv4/route.c:1720 [inline]
     ip_route_input_mc net/ipv4/route.c:1720 [inline] net/ipv4/route.c:2465
     ip_route_input_rcu.part.0+0x4fe/0xcc0 net/ipv4/route.c:2465 net/ipv4/route.c:2465
     ip_route_input_rcu net/ipv4/route.c:2420 [inline]
     ip_route_input_rcu net/ipv4/route.c:2420 [inline] net/ipv4/route.c:2416
     ip_route_input_noref+0x1b8/0x2a0 net/ipv4/route.c:2416 net/ipv4/route.c:2416
     ip_rcv_finish_core.constprop.0+0x288/0x1e90 net/ipv4/ip_input.c:354 net/ipv4/ip_input.c:354
     ip_rcv_finish+0x135/0x2f0 net/ipv4/ip_input.c:427 net/ipv4/ip_input.c:427
     NF_HOOK include/linux/netfilter.h:307 [inline]
     NF_HOOK include/linux/netfilter.h:301 [inline]
     NF_HOOK include/linux/netfilter.h:307 [inline] net/ipv4/ip_input.c:540
     NF_HOOK include/linux/netfilter.h:301 [inline] net/ipv4/ip_input.c:540
     ip_rcv+0xaa/0xd0 net/ipv4/ip_input.c:540 net/ipv4/ip_input.c:540
     __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5350 net/core/dev.c:5350
     __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5464 net/core/dev.c:5464
     process_backlog+0x2a5/0x6c0 net/core/dev.c:5796 net/core/dev.c:5796
     __napi_poll+0xaf/0x440 net/core/dev.c:6364 net/core/dev.c:6364
     napi_poll net/core/dev.c:6431 [inline]
     napi_poll net/core/dev.c:6431 [inline] net/core/dev.c:6518
     net_rx_action+0x801/0xb40 net/core/dev.c:6518 net/core/dev.c:6518
     __do_softirq+0x29b/0x9c2 kernel/softirq.c:558 kernel/softirq.c:558
     run_ksoftirqd kernel/softirq.c:921 [inline]
     run_ksoftirqd kernel/softirq.c:921 [inline] kernel/softirq.c:913
     run_ksoftirqd+0x2d/0x60 kernel/softirq.c:913 kernel/softirq.c:913
     smpboot_thread_fn+0x645/0x9c0 kernel/smpboot.c:164 kernel/smpboot.c:164
     kthread+0x405/0x4f0 kernel/kthread.c:327 kernel/kthread.c:327
     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 arch/x86/entry/entry_64.S:295
    
    Fixes: 4e66934eaadc ("lib: add reference counting tracking infrastructure")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d9932b46915664c88709d59927fa67e797adec56
Author: Sunil Muthuswamy <sunilmut@microsoft.com>
Date:   Wed Jan 5 11:32:36 2022 -0800

    PCI: hv: Add arm64 Hyper-V vPCI support
    
    Add arm64 Hyper-V vPCI support by implementing the arch specific
    interfaces. Introduce an IRQ domain and chip specific to Hyper-v vPCI that
    is based on SPIs. The IRQ domain parents itself to the arch GIC IRQ domain
    for basic vector management.
    
    [bhelgaas: squash in fix from Yang Li <yang.lee@linux.alibaba.com>:
    https://lore.kernel.org/r/20220112003324.62755-1-yang.lee@linux.alibaba.com]
    Link: https://lore.kernel.org/r/1641411156-31705-3-git-send-email-sunilmut@linux.microsoft.com
    Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Michael Kelley <mikelley@microsoft.com>

commit 831c1ae725f7d2f8f858b0840692b48e75b49331
Author: Sunil Muthuswamy <sunilmut@microsoft.com>
Date:   Wed Jan 5 11:32:35 2022 -0800

    PCI: hv: Make the code arch neutral by adding arch specific interfaces
    
    Encapsulate arch dependencies in Hyper-V vPCI through a set of
    arch-dependent interfaces. Adding these arch specific interfaces will
    allow for an implementation for other architectures, such as arm64.
    
    There are no functional changes expected from this patch.
    
    Link: https://lore.kernel.org/r/1641411156-31705-2-git-send-email-sunilmut@linux.microsoft.com
    Signed-off-by: Sunil Muthuswamy <sunilmut@microsoft.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
    Reviewed-by: Marc Zyngier <maz@kernel.org>
    Reviewed-by: Michael Kelley <mikelley@microsoft.com>

commit f7a6021aaf02088870559f82fc13c58cda7fea1a
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Jan 11 10:50:48 2022 +0800

    ASoC: cpcap: Check for NULL pointer after calling of_get_child_by_name
    
    If the device does not exist, of_get_child_by_name() will return NULL
    pointer.
    And devm_snd_soc_register_component() does not check it.
    Also, I have noticed that cpcap_codec_driver has not been used yet.
    Therefore, it should be better to check it in order to avoid the future
    dereference of the NULL pointer.
    
    Fixes: f6cdf2d3445d ("ASoC: cpcap: new codec")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220111025048.524134-1-jiasheng@iscas.ac.cn
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4fbcc1a4cb20fe26ad0225679c536c80f1648221
Author: Jordy Zomer <jordy@pwning.systems>
Date:   Tue Jan 11 17:44:51 2022 +0100

    nfc: st21nfca: Fix potential buffer overflows in EVT_TRANSACTION
    
    It appears that there are some buffer overflows in EVT_TRANSACTION.
    This happens because the length parameters that are passed to memcpy
    come directly from skb->data and are not guarded in any way.
    
    Signed-off-by: Jordy Zomer <jordy@pwning.systems>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2a4d75bfe41232608f5596a6d1369f92ccb20817
Author: Miroslav Lichvar <mlichvar@redhat.com>
Date:   Tue Jan 11 16:10:53 2022 +0100

    net: fix sock_timestamping_bind_phc() to release device
    
    Don't forget to release the device in sock_timestamping_bind_phc() after
    it was used to get the vclock indices.
    
    Fixes: d463126e23f1 ("net: sock: extend SO_TIMESTAMPING for PHC binding")
    Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
    Cc: Yangbo Lu <yangbo.lu@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3486eb774f9d6c2cafcfed31936c9a9b7adf8f05
Author: Michael Walle <michael@walle.cc>
Date:   Tue Jan 11 09:12:06 2022 +0100

    Revert "of: net: support NVMEM cells with MAC in text format"
    
    This reverts commit 9ed319e411915e882bb4ed99be3ae78667a70022.
    
    We can already post process a nvmem cell value in a particular driver.
    Instead of having yet another place to convert the values, the post
    processing hook of the nvmem provider should be used in this case.
    
    Signed-off-by: Michael Walle <michael@walle.cc>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 085a9f43433f30cbe8a1ade62d9d7827c3217f4d
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Fri Dec 17 15:17:09 2021 +0100

    PCI: pciehp: Use down_read/write_nested(reset_lock) to fix lockdep errors
    
    Use down_read_nested() and down_write_nested() when taking the
    ctrl->reset_lock rw-sem, passing the number of PCIe hotplug controllers in
    the path to the PCI root bus as lock subclass parameter.
    
    This fixes the following false-positive lockdep report when unplugging a
    Lenovo X1C8 from a Lenovo 2nd gen TB3 dock:
    
      pcieport 0000:06:01.0: pciehp: Slot(1): Link Down
      pcieport 0000:06:01.0: pciehp: Slot(1): Card not present
      ============================================
      WARNING: possible recursive locking detected
      5.16.0-rc2+ #621 Not tainted
      --------------------------------------------
      irq/124-pciehp/86 is trying to acquire lock:
      ffff8e5ac4299ef8 (&ctrl->reset_lock){.+.+}-{3:3}, at: pciehp_check_presence+0x23/0x80
    
      but task is already holding lock:
      ffff8e5ac4298af8 (&ctrl->reset_lock){.+.+}-{3:3}, at: pciehp_ist+0xf3/0x180
    
       other info that might help us debug this:
       Possible unsafe locking scenario:
    
             CPU0
             ----
        lock(&ctrl->reset_lock);
        lock(&ctrl->reset_lock);
    
       *** DEADLOCK ***
    
       May be due to missing lock nesting notation
    
      3 locks held by irq/124-pciehp/86:
       #0: ffff8e5ac4298af8 (&ctrl->reset_lock){.+.+}-{3:3}, at: pciehp_ist+0xf3/0x180
       #1: ffffffffa3b024e8 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pciehp_unconfigure_device+0x31/0x110
       #2: ffff8e5ac1ee2248 (&dev->mutex){....}-{3:3}, at: device_release_driver+0x1c/0x40
    
      stack backtrace:
      CPU: 4 PID: 86 Comm: irq/124-pciehp Not tainted 5.16.0-rc2+ #621
      Hardware name: LENOVO 20U90SIT19/20U90SIT19, BIOS N2WET30W (1.20 ) 08/26/2021
      Call Trace:
       <TASK>
       dump_stack_lvl+0x59/0x73
       __lock_acquire.cold+0xc5/0x2c6
       lock_acquire+0xb5/0x2b0
       down_read+0x3e/0x50
       pciehp_check_presence+0x23/0x80
       pciehp_runtime_resume+0x5c/0xa0
       device_for_each_child+0x45/0x70
       pcie_port_device_runtime_resume+0x20/0x30
       pci_pm_runtime_resume+0xa7/0xc0
       __rpm_callback+0x41/0x110
       rpm_callback+0x59/0x70
       rpm_resume+0x512/0x7b0
       __pm_runtime_resume+0x4a/0x90
       __device_release_driver+0x28/0x240
       device_release_driver+0x26/0x40
       pci_stop_bus_device+0x68/0x90
       pci_stop_bus_device+0x2c/0x90
       pci_stop_and_remove_bus_device+0xe/0x20
       pciehp_unconfigure_device+0x6c/0x110
       pciehp_disable_slot+0x5b/0xe0
       pciehp_handle_presence_or_link_change+0xc3/0x2f0
       pciehp_ist+0x179/0x180
    
    This lockdep warning is triggered because with Thunderbolt, hotplug ports
    are nested. When removing multiple devices in a daisy-chain, each hotplug
    port's reset_lock may be acquired recursively. It's never the same lock, so
    the lockdep splat is a false positive.
    
    Because locks at the same hierarchy level are never acquired recursively, a
    per-level lockdep class is sufficient to fix the lockdep warning.
    
    The choice to use one lockdep subclass per pcie-hotplug controller in the
    path to the root-bus was made to conserve class keys because their number
    is limited and the complexity grows quadratically with number of keys
    according to Documentation/locking/lockdep-design.rst.
    
    Link: https://lore.kernel.org/linux-pci/20190402021933.GA2966@mit.edu/
    Link: https://lore.kernel.org/linux-pci/de684a28-9038-8fc6-27ca-3f6f2f6400d7@redhat.com/
    Link: https://lore.kernel.org/r/20211217141709.379663-1-hdegoede@redhat.com
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=208855
    Reported-by: "Theodore Ts'o" <tytso@mit.edu>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Reviewed-by: Lukas Wunner <lukas@wunner.de>
    Cc: stable@vger.kernel.org

commit fe75e84a8fe17449ea16b73cfcfc9e7d06a49130
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Wed Jan 12 12:29:05 2022 +0100

    netfilter: nf_tables: set last expression in register tracking area
    
    nft_rule_for_each_expr() sets on last to nft_rule_last(), however, this
    is coming after track.last field is set on.
    
    Use nft_expr_last() to set track.last accordingly.
    
    Fixes: 12e4ecfa244b ("netfilter: nf_tables: add register tracking infrastructure")
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 0499f419b76f94ede08304aad5851144813ac55c
Author: Javier Martinez Canillas <javierm@redhat.com>
Date:   Mon Jan 10 10:56:25 2022 +0100

    video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
    
    The vga16fb framebuffer driver only supports Enhanced Graphics Adapter
    (EGA) and Video Graphics Array (VGA) 16 color graphic cards.
    
    But it doesn't check if the adapter is one of those or if a VGA16 mode
    is used. This means that the driver will be probed even if a VESA BIOS
    Extensions (VBE) or Graphics Output Protocol (GOP) interface is used.
    
    This issue has been present for a long time but it was only exposed by
    commit d391c5827107 ("drivers/firmware: move x86 Generic System
    Framebuffers support") since the platform device registration to match
    the {vesa,efi}fb drivers is done later as a consequence of that change.
    
    All non-x86 architectures though treat orig_video_isVGA as a boolean so
    only do the supported video mode check for x86 and not for other arches.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=215001
    Fixes: d391c5827107 ("drivers/firmware: move x86 Generic System Framebuffers support")
    Reported-by: Kris Karas <bugs-a21@moonlit-rail.com>
    Cc: <stable@vger.kernel.org> # 5.15.x
    Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
    Tested-by: Kris Karas <bugs-a21@moonlit-rail.com>
    Acked-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220110095625.278836-3-javierm@redhat.com

commit f3193ea1b6779023334faa72b214ece457e02656
Author: Karl Kurbjun <kkurbjun@gmail.com>
Date:   Sun Jan 9 20:49:35 2022 -0700

    HID: Ignore battery for Elan touchscreen on HP Envy X360 15t-dr100
    
    Battery status on Elan tablet driver is reported for the HP ENVY x360
    15t-dr100. There is no separate battery for the Elan controller resulting in a
    battery level report of 0% or 1% depending on whether a stylus has interacted
    with the screen. These low battery level reports causes a variety of bad
    behavior in desktop environments. This patch adds the appropriate quirk to
    indicate that the batery status is unused for this target.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Karl Kurbjun <kkurbjun@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 869b6ca39c08c5b10eeb29d4b3c4bc433bf8ba5e
Author: Huang Yiwei <quic_hyiwei@quicinc.com>
Date:   Mon Nov 22 13:05:09 2021 +0800

    dt-bindings: mailbox: Add more protocol and client ID
    
    Add more protocol and client ID which can be used in device
    tree properties.
    
    Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit afaf2ba5b430c538297cb59012ea17d28a1f8a26
Author: Huang Yiwei <quic_hyiwei@quicinc.com>
Date:   Mon Nov 22 13:05:08 2021 +0800

    mailbox: qcom-ipcc: Support interrupt wake up from suspend
    
    Use IRQF_NO_SUSPEND flag instead of enable_irq_wake to
    support interrupt wake up from suspend.
    
    Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 1f43e5230aebb17aea35238dc26e297a61095ac0
Author: Huang Yiwei <quic_hyiwei@quicinc.com>
Date:   Mon Nov 22 13:05:07 2021 +0800

    mailbox: qcom-ipcc: Support more IPCC instance
    
    Since hardware is supporting multiple IPCC instance,
    use ipcc_%d instead of ipcc as the irq name to support
    in driver.
    
    Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit e9d50e4b4d04165097a71e20e0a77e7ad7053dd0
Author: Huang Yiwei <quic_hyiwei@quicinc.com>
Date:   Mon Nov 22 13:05:06 2021 +0800

    mailbox: qcom-ipcc: Dynamic alloc for channel arrangement
    
    Dynamic alloc for channel arrangement instead of static alloced
    array, it is more flexible and can reduce memory usage.
    
    Signed-off-by: Huang Yiwei <quic_hyiwei@quicinc.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit f10b1fc0161cd99e54c5687fcc63368aa255e05e
Author: Conor Dooley <conor.dooley@microchip.com>
Date:   Fri Dec 17 09:33:12 2021 +0000

    mailbox: change mailbox-mpfs compatible string
    
    The Polarfire SoC is currently using two different compatible string
    prefixes. Fix this by changing "polarfire-soc-*" strings to "mpfs-*" in
    its system controller in order to match the compatible string used in
    the soc binding and device tree.
    
    Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
    Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 7215a7857e796c655ae1184b313556102fa8bc40
Author: Sudeep Holla <sudeep.holla@arm.com>
Date:   Thu Dec 9 09:21:46 2021 +0000

    mailbox: pcc: Handle all PCC subtypes correctly in pcc_mbox_irq
    
    Commit c45ded7e1135 ("mailbox: pcc: Add support for PCCT extended PCC
    subspaces(type 3/4)") enabled the type3/4 of PCCT, but the change in
    pcc_mbox_irq breaks the other PCC subtypes.
    
    The kernel reports a warning on an Ampere eMag server
    
    -->8
     CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.16.0-rc4 #127
     Hardware name: MiTAC RAPTOR EV-883832-X3-0001/RAPTOR, BIOS 0.14 02/22/2019
     Call trace:
      dump_backtrace+0x0/0x200
      show_stack+0x20/0x30
      dump_stack_lvl+0x68/0x84
      dump_stack+0x18/0x34
      __report_bad_irq+0x54/0x17c
      note_interrupt+0x330/0x428
      handle_irq_event_percpu+0x90/0x98
      handle_irq_event+0x4c/0x148
      handle_fasteoi_irq+0xc4/0x188
      generic_handle_domain_irq+0x44/0x68
      gic_handle_irq+0x84/0x2ec
      call_on_irq_stack+0x28/0x34
      do_interrupt_handler+0x88/0x90
      el1_interrupt+0x48/0xb0
      el1h_64_irq_handler+0x18/0x28
      el1h_64_irq+0x7c/0x80
    
    Fixes: c45ded7e1135 ("mailbox: pcc: Add support for PCCT extended PCC subspaces(type 3/4)")
    Reported-by: Justin He <justin.he@arm.com>
    Tested-by: Justin He <justin.he@arm.com>
    Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 960c4056aadcf61983f8eaac159927a052f8cf01
Author: Sudeep Holla <sudeep.holla@arm.com>
Date:   Thu Dec 9 08:21:43 2021 +0000

    mailbox: pcc: Avoid using the uninitialized variable 'dev'
    
    Smatch static checker warns:
    
      |  drivers/mailbox/pcc.c:292 pcc_mbox_request_channel()
      |  error: uninitialized symbol 'dev'.
    
    Fix the same by using pr_err instead of dev_err as the variable 'dev'
    is uninitialized at that stage.
    
    Fixes: ce028702ddbc ("mailbox: pcc: Move bulk of PCCT parsing into pcc_mbox_probe")
    Cc: Jassi Brar <jassisinghbrar@gmail.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit af8d0f6d222d12ed7bba447e5eb277a5908b8968
Author: Wang Qing <wangqing@vivo.com>
Date:   Tue Jan 11 23:15:47 2022 -0600

    mailbox: mtk: add missing of_node_put before return
    
    Fix following coccicheck warning:
    WARNING: Function "for_each_child_of_node"
    should have of_node_put() before return.
    
    Early exits from for_each_child_of_node should decrement the
    node reference counter.
    
    Signed-off-by: Wang Qing <wangqing@vivo.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 2453128847ca1edbecbe33dbe063a04489d64842
Author: Wang Qing <wangqing@vivo.com>
Date:   Mon Dec 13 01:44:20 2021 -0800

    mailbox: zynq: add missing of_node_put before return
    
    Fix following coccicheck warning:
    WARNING: Function "for_each_available_child_of_node"
    should have of_node_put() before return.
    
    Early exits from for_each_available_child_of_node should decrement the
    node reference counter.
    
    Signed-off-by: Wang Qing <wangqing@vivo.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 05d06f37196b2e3abeff2b98b785c8803865e646
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Wed Nov 24 17:51:26 2021 +0300

    mailbox: imx: Fix an IS_ERR() vs NULL bug
    
    The devm_kzalloc() function does not return error pointers, it returns
    NULL on failure.
    
    Fixes: 97961f78e8bc ("mailbox: imx: support i.MX8ULP S4 MU")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Peng Fan <peng.fan@nxp.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 79daec8b9c02e04e2afb11eefa71698b913b2c55
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sun Nov 14 19:31:19 2021 -0800

    mailbox: hi3660: convert struct comments to kernel-doc notation
    
    Convert hi3660 struct comments to kernel-doc notation and fix
    other kernel-doc warnings:
    
    drivers/mailbox/hi3660-mailbox.c:47: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
        * Hi3660 mailbox channel information
    drivers/mailbox/hi3660-mailbox.c:62: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
        * Hi3660 mailbox controller data
    hi3660-mailbox.c:53: warning: contents before sections
    hi3660-mailbox.c:67: warning: contents before sections
    
    Fixes: 41c0e939d70d ("mailbox: Add support for Hi3660 mailbox")
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: kernel test robot <lkp@intel.com>
    Cc: Ruyi Wang <wangruyi@huawei.com>
    Cc: Kaihua Zhong <zhongkaihua@huawei.com>
    Reviewed-by: Leo Yan <leo.yan@linaro.org>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 9388501fbb99a1b6a23f28634d125567a3b45a3d
Author: jason-jh.lin <jason-jh.lin@mediatek.com>
Date:   Fri Dec 10 14:11:38 2021 +0800

    mailbox: add control_by_sw for mt8195
    
    To make sure the GCE request signal to SPM is not trigger by
    other HW modules and cause suspend premature wake.
    
    Set 0x7 (the bit 0~2 as 1) to GCE_GCTL_VALUE, to configure the
    request signal control by SW and release the request to SPM.
    
    Signed-off-by: jason-jh.lin <jason-jh.lin@mediatek.com>
    Reviewed-by: Tzung-Bi Shih <tzungbi@google.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 99867e5a87502a3e636059f39b2f668931767868
Author: Hsin-Yi Wang <hsinyi@chromium.org>
Date:   Mon Dec 13 15:05:01 2021 +0800

    mailbox: mtk-cmdq: Silent EPROBE_DEFER errors for clks
    
    Silent the error if it's EPROBE_DEFER for clks.
    
    Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 35ca43710f792ce183312fdc7e4b2bb0b721a173
Author: jason-jh.lin <jason-jh.lin@mediatek.com>
Date:   Thu Dec 23 22:51:55 2021 +0800

    mailbox: fix gce_num of mt8192 driver data
    
    Because mt8192 only have 1 gce, the gce_num should be 1.
    
    Fixes: 85dfdbfc13ea ("mailbox: cmdq: add multi-gce clocks support for mt8195")
    Signed-off-by: jason-jh.lin <jason-jh.lin@mediatek.com>
    Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit 1fa68a3593ae5b9168a08ad4f72d2d7dbbeedb41
Author: Hector Martin <marcan@marcan.st>
Date:   Thu Dec 16 00:55:27 2021 +0900

    mailbox: apple: Bind to generic compatibles
    
    As with other blocks, we intend to have drivers bind to generic
    compatibles as long as there are no SoC-specific quirks. This allows
    forward-compatibility with future SoCs.
    
    No upstream DTs instantiate this yet, so it's still safe to make this
    breaking change.
    
    Signed-off-by: Hector Martin <marcan@marcan.st>
    Reviewed-by: Sven Peter <sven@svenpeter.dev>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit b29d644b5589d5b9f002f4a5a53699a33e1c08f0
Author: Hector Martin <marcan@marcan.st>
Date:   Thu Dec 16 00:55:26 2021 +0900

    dt-bindings: mailbox: apple,mailbox: Add generic and t6000 compatibles
    
    Much as we've done with other blocks, let's introduce generic
    compatibles so drivers can bind to those and still work with future
    SoCs, as long as the hardware remains the same. Also go ahead and add
    compatibles for the new t600x SoCs (we group those as t6000).
    
    Note that no DTs instantiate devices with this binding yet.
    
    Reviewed-by: Mark Kettenis <kettenis@openbsd.org>
    Signed-off-by: Hector Martin <marcan@marcan.st>
    Reviewed-by: Sven Peter <sven@svenpeter.dev>
    Reviewed-by: Sven Peter <sven@svenpeter.dev>
    Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>

commit edcb501e543cecaff5e3d079c798911e680fea65
Author: Colin Ian King <colin.king@intel.com>
Date:   Sun Jan 9 23:17:16 2022 +0000

    net: phy: at803x: make array offsets static
    
    Don't populate the read-only const array offsets on the stack
    but instead make it static. Also makes the object code a little smaller.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220109231716.59012-1-colin.i.king@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e110978d6e060a3e633e3e5e427770a66b330d48
Author: Colin Ian King <colin.king@intel.com>
Date:   Sun Jan 9 20:24:18 2022 +0000

    nfc: pn544: make array rset_cmd static const
    
    Don't populate the read-only array rset_cmd on the stack but
    instead it static const. Also makes the object code a little smaller.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220109202418.50641-1-colin.i.king@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cb963a19d99fc42d9abf4238968ef85fcc2ef3e3
Author: Eric Dumazet <edumazet@google.com>
Date:   Mon Jan 10 01:47:50 2022 -0800

    net: sched: do not allocate a tracker in tcf_exts_init()
    
    While struct tcf_exts has a net pointer, it is not refcounted
    until tcf_exts_get_net() is called.
    
    Fixes: dbdcda634ce3 ("net: sched: add netns refcount tracker to struct tcf_exts")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220110094750.236478-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 29b3881b7977db792f93ebe440423811d5cfee56
Merge: 274c224062ff9 48d67543e01d7
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Tue Jan 11 20:36:11 2022 -0800

    Merge branch 'ipv4-fix-accidental-rto_onlink-flags-passed-to-ip_route_output_key_hash'
    
    Guillaume Nault says:
    
    ====================
    ipv4: Fix accidental RTO_ONLINK flags passed to ip_route_output_key_hash()
    
    The IPv4 stack generally uses the last bit of ->flowi4_tos as a flag
    indicating link scope for route lookups (RTO_ONLINK). Therefore, we
    have to be careful when copying a TOS value to ->flowi4_tos. In
    particular, the ->tos field of IPv4 packets may have this bit set
    because of ECN. Also tunnel keys generally accept any user value for
    the tos.
    
    This series fixes several places where ->flowi4_tos was set from
    non-sanitised values and the flowi4 structure was later used by
    ip_route_output_key_hash().
    
    Note that the IPv4 stack usually clears the RTO_ONLINK bit using
    RT_TOS(). However this macro is based on an obsolete interpretation of
    the old IPv4 TOS field (RFC 1349) and clears the three high order bits
    too. Since we don't need to clear these bits and since it doesn't make
    sense to clear only one of the ECN bits, this patch series uses
    INET_ECN_MASK instead.
    
    All patches were compile tested only.
    ====================
    
    Link: https://lore.kernel.org/r/cover.1641821242.git.gnault@redhat.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 48d67543e01d73292e0bb66d3f10fc422e79e031
Author: Guillaume Nault <gnault@redhat.com>
Date:   Mon Jan 10 14:43:14 2022 +0100

    mlx5: Don't accidentally set RTO_ONLINK before mlx5e_route_lookup_ipv4_get()
    
    Mask the ECN bits before calling mlx5e_route_lookup_ipv4_get(). The
    tunnel key might have the last ECN bit set. This interferes with the
    route lookup process as ip_route_output_key_hash() interpretes this bit
    specially (to restrict the route scope).
    
    Found by code inspection, compile tested only.
    
    Fixes: c7b9038d8af6 ("net/mlx5e: TC preparation refactoring for routing update event")
    Fixes: 9a941117fb76 ("net/mlx5e: Maximize ip tunnel key usage on the TC offloading path")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a915deaa9abe4fb3a440312c954253a6a733608e
Author: Guillaume Nault <gnault@redhat.com>
Date:   Mon Jan 10 14:43:11 2022 +0100

    libcxgb: Don't accidentally set RTO_ONLINK in cxgb_find_route()
    
    Mask the ECN bits before calling ip_route_output_ports(). The tos
    variable might be passed directly from an IPv4 header, so it may have
    the last ECN bit set. This interferes with the route lookup process as
    ip_route_output_key_hash() interpretes this bit specially (to restrict
    the route scope).
    
    Found by code inspection, compile tested only.
    
    Fixes: 804c2f3e36ef ("libcxgb,iw_cxgb4,cxgbit: add cxgb_find_route()")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f7716b318568b22fbf0e3be99279a979e217cf71
Author: Guillaume Nault <gnault@redhat.com>
Date:   Mon Jan 10 14:43:09 2022 +0100

    gre: Don't accidentally set RTO_ONLINK in gre_fill_metadata_dst()
    
    Mask the ECN bits before initialising ->flowi4_tos. The tunnel key may
    have the last ECN bit set, which will interfere with the route lookup
    process as ip_route_output_key_hash() interpretes this bit specially
    (to restrict the route scope).
    
    Found by code inspection, compile tested only.
    
    Fixes: 962924fa2b7a ("ip_gre: Refactor collect metatdata mode tunnel xmit to ip_md_tunnel_xmit")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 23e7b1bfed61e301853b5e35472820d919498278
Author: Guillaume Nault <gnault@redhat.com>
Date:   Mon Jan 10 14:43:06 2022 +0100

    xfrm: Don't accidentally set RTO_ONLINK in decode_session4()
    
    Similar to commit 94e2238969e8 ("xfrm4: strip ECN bits from tos field"),
    clear the ECN bits from iph->tos when setting ->flowi4_tos.
    This ensures that the last bit of ->flowi4_tos is cleared, so
    ip_route_output_key_hash() isn't going to restrict the scope of the
    route lookup.
    
    Use ~INET_ECN_MASK instead of IPTOS_RT_MASK, because we have no reason
    to clear the high order bits.
    
    Found by code inspection, compile tested only.
    
    Fixes: 4da3089f2b58 ("[IPSEC]: Use TOS when doing tunnel lookups")
    Signed-off-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 274c224062ff9545d8df2a6e4764a5fd660d792e
Author: Conley Lee <conleylee@foxmail.com>
Date:   Tue Jan 11 11:05:53 2022 +0800

    net: ethernet: sun4i-emac: replace magic number with macro
    
    This patch remove magic numbers in sun4i-emac.c and replace with macros
    defined in sun4i-emac.h
    
    Signed-off-by: Conley Lee <conleylee@foxmail.com>
    Tested-by: Corentin Labbe <clabbe.montjoie@gmail.com>
    Link: https://lore.kernel.org/r/tencent_71466C2135CD1780B19D7844BE3F167C940A@qq.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 284a4d94e8e74fbd731ee67e29196656ca823423
Author: Matt Johnston <matt@codeconstruct.com.au>
Date:   Mon Jan 10 10:18:06 2022 +0800

    mctp: test: zero out sockaddr
    
    MCTP now requires that padding bytes are zero.
    
    Signed-off-by: Matt Johnston <matt@codeconstruct.com.au>
    Fixes: 1e4b50f06d97 ("mctp: handle the struct sockaddr_mctp padding fields")
    Link: https://lore.kernel.org/r/20220110021806.2343023-1-matt@codeconstruct.com.au
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 96dd8754881022d4372359b1c0efcdbc732a0ea7
Author: Luis Chamberlain <mcgrof@kernel.org>
Date:   Tue Jan 11 19:15:12 2022 -0800

    MAINTAINERS: add mailing lists for kmod and modules
    
    Add the linux-modules list for kmod and linux modules changes.
    
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit ca321ec74322e3c49552fc1ffc80b42d0dbf1a84
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Sat Jan 8 15:06:57 2022 +0100

    module.h: allow #define strings to work with MODULE_IMPORT_NS
    
    The MODULE_IMPORT_NS() macro does not allow defined strings to work
    properly with it, so add a layer of indirection to allow this to happen.
    
    Cc: Luis Chamberlain <mcgrof@kernel.org>
    Cc: Jessica Yu <jeyu@kernel.org>
    Cc: Matthias Maennich <maennich@google.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Matthias Maennich <maennich@google.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit b1ae6dc41eaaa98bb75671e0f3665bfda248c3e7
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Wed Jan 5 13:55:12 2022 -0800

    module: add in-kernel support for decompressing
    
    Current scheme of having userspace decompress kernel modules before
    loading them into the kernel runs afoul of LoadPin security policy, as
    it loses link between the source of kernel module on the disk and binary
    blob that is being loaded into the kernel. To solve this issue let's
    implement decompression in kernel, so that we can pass a file descriptor
    of compressed module file into finit_module() which will keep LoadPin
    happy.
    
    To let userspace know what compression/decompression scheme kernel
    supports it will create /sys/module/compression attribute. kmod can read
    this attribute and decide if it can pass compressed file to
    finit_module(). New MODULE_INIT_COMPRESSED_DATA flag indicates that the
    kernel should attempt to decompress the data read from file descriptor
    prior to trying load the module.
    
    To simplify things kernel will only implement single decompression
    method matching compression method selected when generating modules.
    This patch implements gzip and xz; more can be added later,
    
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit ef307fc2a9bd776114f9c85bc676ad76fe8f0f2a
Author: Jessica Yu <jeyu@kernel.org>
Date:   Thu Dec 9 09:43:13 2021 +0100

    MAINTAINERS: Remove myself as modules maintainer
    
    Luis has done a great job maintaining modules so far. As I'm planning to
    take a break from work soon, I think we're ready to transition over fully.
    
    Signed-off-by: Jessica Yu <jeyu@kernel.org>
    Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit 9dc3c3f691bca10d3aa94887eee33bf629840b23
Author: Yu Chen <chen.yu@easystack.cn>
Date:   Mon Nov 22 06:26:48 2021 -0800

    module: Remove outdated comment
    
    Since commit e513cc1c07e2 ("module: Remove stop_machine from module
    unloading") this comment is no longer correct. Remove it.
    
    Signed-off-by: Yu Chen <chen.yu@easystack.cn>
    Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

commit 4afd2a9355a9deb16ea42b896820dacf49843a8f
Merge: 1d0bd126d9282 b5bc83bb70a5c ec97d23c8e22c
Author: Stephen Boyd <sboyd@kernel.org>
Date:   Tue Jan 11 18:31:00 2022 -0800

    Merge branches 'clk-ingenic' and 'clk-mediatek' into clk-next
    
     - Add MDMA and BDMA clks to Ingenic JZ4760 and JZ4770
     - MediaTek mt7986 SoC basic support
    
    * clk-ingenic:
      clk: ingenic: Add MDMA and BDMA clocks
      dt-bindings: clk/ingenic: Add MDMA and BDMA clocks
    
    * clk-mediatek:
      clk: mediatek: add mt7986 clock support
      clk: mediatek: add mt7986 clock IDs
      dt-bindings: clock: mediatek: document clk bindings for mediatek mt7986 SoC
      clk: mediatek: clk-gate: Use regmap_{set/clear}_bits helpers
      clk: mediatek: clk-gate: Shrink by adding clockgating bit check helper

commit 1d0bd126d9282ce198c85a6f83036f68e1c6cc3c
Merge: f691c9b526627 b739bca9f3344 4e31bfa37662f 5dcc0ef8873ea c861c1be38978
Author: Stephen Boyd <sboyd@kernel.org>
Date:   Tue Jan 11 18:30:50 2022 -0800

    Merge branches 'clk-socfpga', 'clk-toshiba', 'clk-st' and 'clk-bitmain' into clk-next
    
     - Clock and reset driver for Toshiba Visconti SoCs
    
    * clk-socfpga:
      clk: socfpga: s10: Make use of the helper function devm_platform_ioremap_resource()
      clk: socfpga: agilex: Make use of the helper function devm_platform_ioremap_resource()
      clk: socfpga: remove redundant assignment after a mask operation
      clk: socfpga: remove redundant assignment on division
    
    * clk-toshiba:
      clk: visconti: Remove pointless NULL check in visconti_pll_add_lookup()
      MAINTAINERS: Add entries for Toshiba Visconti PLL and clock controller
      clk: visconti: Add support common clock driver and reset driver
      dt-bindings: clock: Add DT bindings for SMU of Toshiba Visconti TMPV770x SoC
      dt-bindings: clock: Add DT bindings for PLL of Toshiba Visconti TMPV770x SoC
    
    * clk-st:
      clk: Drop unused COMMON_CLK_STM32MP157_SCMI config
      clk: st: clkgen-mux: search reg within node or parent
      clk: st: clkgen-fsyn: search reg within node or parent
    
    * clk-bitmain:
      clk: bm1880: remove kfrees on static allocations

commit f691c9b526627933b332a1e4c3c7f8635021dba3
Merge: 151768f34854e fcfc6ea4a400e 176a3200ef6d8 14350ed95867c 87e55700f3598
Author: Stephen Boyd <sboyd@kernel.org>
Date:   Tue Jan 11 18:30:43 2022 -0800

    Merge branches 'clk-nvidia', 'clk-imx', 'clk-samsung' and 'clk-qcom' into clk-next
    
    * clk-nvidia:
      clk: tegra: Support runtime PM and power domain
      clk: tegra: Make vde a child of pll_p on tegra114
    
    * clk-imx:
      clk: imx8mp: Fix the parent clk of the audio_root_clk
      clk: imx8mp: Remove IPG_AUDIO_ROOT from imx8mp-clock.h
      clk: imx8mn: Fix imx8mn_clko1_sels
      clk: imx: Use div64_ul instead of do_div
      clk: imx: imx8ulp: set suppress_bind_attrs to true
    
    * clk-samsung:
      clk: samsung: Add initial Exynos7885 clock driver
      clk: samsung: clk-pll: Add support for pll1417x
      clk: samsung: Make exynos850_register_cmu shared
      dt-bindings: clock: Document Exynos7885 CMU bindings
      dt-bindings: clock: Add bindings definitions for Exynos7885 CMU
      clk: samsung: exynos850: Add missing sysreg clocks
      dt-bindings: clock: Add bindings for Exynos850 sysreg clocks
      clk: samsung: exynos850: Register clocks early
      clk: samsung: exynos850: Keep some crucial clocks running
      clk: samsung: exynos850: Implement CMU_CMGP domain
      dt-bindings: clock: Add bindings for Exynos850 CMU_CMGP
      clk: samsung: exynos850: Implement CMU_APM domain
      dt-bindings: clock: Add bindings for Exynos850 CMU_APM
      clk: samsung: Update CPU clk registration
      clk: samsung: Remove meaningless __init and extern from header files
      clk: samsung: remove __clk_lookup() usage
      dt-bindings: clock: samsung: add IDs for some core clocks
    
    * clk-qcom: (25 commits)
      clk: qcom: gcc-sc7280: Mark gcc_cfg_noc_lpass_clk always enabled
      clk: qcom: clk-alpha-pll: Increase PLL lock detect poll time
      clk: qcom: turingcc-qcs404: explicitly include clk-provider.h
      clk: qcom: q6sstop-qcs404: explicitly include clk-provider.h
      clk: qcom: mmcc-apq8084: explicitly include clk-provider.h
      clk: qcom: lpasscc-sdm845: explicitly include clk-provider.h
      clk: qcom: lpasscc-sc7280: explicitly include clk-provider.h
      clk: qcom: gcc-sm6350: explicitly include clk-provider.h
      clk: qcom: gcc-msm8994: explicitly include clk-provider.h
      clk: qcom: gcc-sm8350: explicitly include clk-provider.h
      clk: qcom: Add MSM8976/56 Global Clock Controller (GCC) driver
      dt-bindings: clk: qcom: Document MSM8976 Global Clock Controller
      clk: qcom: Add clock driver for SM8450
      clk: qcom: Add SDX65 GCC support
      clk: qcom: Add LUCID_EVO PLL type for SDX65
      dt-bindings: clock: Add SM8450 GCC clock bindings
      dt-bindings: clock: Add SDX65 GCC clock bindings
      clk: qcom: rpmh: add support for SM8450 rpmh clocks
      dt-bindings: clock: Add RPMHCC bindings for SM8450
      clk: qcom: smd-rpm: Drop binary value handling for buffered clock
      ...

commit 151768f34854e2c9f466ecfc0827742ec5de302b
Merge: 270bbc725328d 1fdaaa13b44fd 6fc058a72f3b7 c1001a62f2f59 4f1e19b658444
Author: Stephen Boyd <sboyd@kernel.org>
Date:   Tue Jan 11 18:30:35 2022 -0800

    Merge branches 'clk-x86', 'clk-stm', 'clk-amlogic' and 'clk-allwinner' into clk-next
    
    * clk-x86:
      clk: x86: Fix clk_gate_flags for RV_CLK_GATE
      clk: x86: Use dynamic con_id string during clk registration
      ACPI: APD: Add a fmw property clk-name
      drivers: acpi: acpi_apd: Remove unused device property "is-rv"
      x86: clk: clk-fch: Add support for newer family of AMD's SOC
      clk: Introduce clk-tps68470 driver
      platform/x86: int3472: Deal with probe ordering issues
      platform/x86: int3472: Pass tps68470_regulator_platform_data to the tps68470-regulator MFD-cell
      platform/x86: int3472: Pass tps68470_clk_platform_data to the tps68470-regulator MFD-cell
      platform/x86: int3472: Add get_sensor_adev_and_name() helper
      platform/x86: int3472: Split into 2 drivers
      platform_data: Add linux/platform_data/tps68470.h file
      i2c: acpi: Add i2c_acpi_new_device_by_fwnode() function
      i2c: acpi: Use acpi_dev_ready_for_enumeration() helper
      ACPI: delay enumeration of devices with a _DEP pointing to an INT3472 device
    
    * clk-stm:
      clk: stm32: Fix ltdc's clock turn off by clk_disable_unused() after system enter shell
    
    * clk-amlogic:
      clk: meson: gxbb: Fix the SDM_EN bit for MPLL0 on GXBB
    
    * clk-allwinner:
      clk: sunxi-ng: Add support for the D1 SoC clocks
      clk: sunxi-ng: gate: Add macros for gates with fixed dividers
      clk: sunxi-ng: mux: Add macros using clk_parent_data and clk_hw
      clk: sunxi-ng: mp: Add macros using clk_parent_data and clk_hw
      clk: sunxi-ng: div: Add macros using clk_parent_data and clk_hw
      dt-bindings: clk: Add compatibles for D1 CCUs
      clk: sunxi-ng: Allow the CCU core to be built as a module
      clk: sunxi-ng: Convert early providers to platform drivers
      clk: sunxi-ng: Allow drivers to be built as modules
      clk: sunxi-ng: Export symbols used by CCU drivers

commit 270bbc725328d905812ba024acd8f71786912fba
Merge: ecb64bbff7ddd a5ce1d5118705 8f6b28c5b1782 d66e4c985dd48 1bb294a7981c7
Author: Stephen Boyd <sboyd@kernel.org>
Date:   Tue Jan 11 18:30:10 2022 -0800

    Merge branches 'clk-doc', 'clk-renesas', 'clk-at91', 'clk-cleanup' and 'clk-debugfs' into clk-next
    
    * clk-doc:
      clk: Gemini: fix struct name in kernel-doc
      clk: zynq: pll: Fix kernel-doc warnings
      clk: imx: pllv1: fix kernel-doc notation for struct clk_pllv1
    
    * clk-renesas: (31 commits)
      clk: renesas: r9a07g044: Add GPU clock and reset entries
      clk: renesas: r9a07g044: Add mux and divider for G clock
      clk: renesas: r9a07g044: Rename CLK_PLL3_DIV4 macro
      clk: renesas: cpg-mssr: Add support for R-Car S4-8
      clk: renesas: rcar-gen4: Introduce R-Car Gen4 CPG driver
      dt-bindings: clock: Add r8a779f0 CPG Core Clock Definitions
      dt-bindings: power: Add r8a779f0 SYSC power domain definitions
      clk: renesas: r9a07g044: Add TSU clock and reset entry
      mmc: renesas_sdhi: Simplify an expression
      mmc: renesas_sdhi: Use devm_clk_get_optional() to obtain CD clock
      dt-bindings: clock: renesas,cpg-mssr: Document r8a779f0
      clk: renesas: cpg-mssr: propagate return value of_genpd_add_provider_simple()
      clk: renesas: cpg-mssr: Check return value of pm_genpd_init()
      clk: renesas: rzg2l: propagate return value of_genpd_add_provider_simple()
      clk: renesas: rzg2l: Check return value of pm_genpd_init()
      clk: renesas: r9a07g044: Add RSPI clock and reset entries
      clk: renesas: r9a07g044: Change core clock "I" from DEF_FIXED->DEF_DIV
      clk: renesas: rzg2l: Add CPG_PL1_DDIV macro
      mmc: renesas_sdhi: Parse DT for SDnH
      mmc: renesas_sdhi: Use dev_err_probe when getting clock fails
      ...
    
    * clk-at91:
      clk: lan966x: Extend lan966x clock driver for clock gating support
      dt-bindings: clock: lan966x: Extend includes with clock gates
      dt-bindings: clock: lan966x: Extend for clock gate support
      clk: gate: Add devm_clk_hw_register_gate()
      clk: lan966x: Add lan966x SoC clock driver
      dt-bindings: clock: lan966x: Add LAN966X Clock Controller
      dt-bindings: clock: lan966x: Add binding includes for lan966x SoC clock IDs
    
    * clk-cleanup:
      clk: stm32mp1: remove redundant assignment to pointer data
      clk: __clk_core_init() never takes NULL
      clk: clk_core_get() can also return NULL
      clk/ti/adpll: Make const pointer error a static const array
    
    * clk-debugfs:
      clk: Enable/Disable runtime PM for clk_summary
      clk: Emit a stern warning with writable debugfs enabled
      clk: Add write operation for clk_parent debugfs node

commit daadb3bd0e8d3e317e36bc2c1542e86c528665e5
Merge: 6ae71436cda74 f16cc980d649e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 17:24:45 2022 -0800

    Merge tag 'locking_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull locking updates from Borislav Petkov:
     "Lots of cleanups and preparation. Highlights:
    
       - futex: Cleanup and remove runtime futex_cmpxchg detection
    
       - rtmutex: Some fixes for the PREEMPT_RT locking infrastructure
    
       - kcsan: Share owner_on_cpu() between mutex,rtmutex and rwsem and
         annotate the racy owner->on_cpu access *once*.
    
       - atomic64: Dead-Code-Elemination"
    
    [ Description above by Peter Zijlstra ]
    
    * tag 'locking_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      locking/atomic: atomic64: Remove unusable atomic ops
      futex: Fix additional regressions
      locking: Allow to include asm/spinlock_types.h from linux/spinlock_types_raw.h
      x86/mm: Include spinlock_t definition in pgtable.
      locking: Mark racy reads of owner->on_cpu
      locking: Make owner_on_cpu() into <linux/sched.h>
      lockdep/selftests: Adapt ww-tests for PREEMPT_RT
      lockdep/selftests: Skip the softirq related tests on PREEMPT_RT
      lockdep/selftests: Unbalanced migrate_disable() & rcu_read_lock().
      lockdep/selftests: Avoid using local_lock_{acquire|release}().
      lockdep: Remove softirq accounting on PREEMPT_RT.
      locking/rtmutex: Add rt_mutex_lock_nest_lock() and rt_mutex_lock_killable().
      locking/rtmutex: Squash self-deadlock check for ww_rt_mutex.
      locking: Remove rt_rwlock_is_contended().
      sched: Trigger warning if ->migration_disabled counter underflows.
      futex: Fix sparc32/m68k/nds32 build regression
      futex: Remove futex_cmpxchg detection
      futex: Ensure futex_atomic_cmpxchg_inatomic() is present
      kernel/locking: Use a pointer in ww_mutex_trylock().

commit 6ae71436cda740148640046d58190a5bbc3ac86d
Merge: 01367e86e9094 82762d2af31a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 17:14:59 2022 -0800

    Merge tag 'sched_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull scheduler updates from Borislav Petkov:
     "Mostly minor things this time; some highlights:
    
       - core-sched: Add 'Forced Idle' accounting; this allows to track how
         much CPU time is 'lost' due to core scheduling constraints.
    
       - psi: Fix for MEM_FULL; a task running reclaim would be counted as a
         runnable task and prevent MEM_FULL from being reported.
    
       - cpuacct: Long standing fixes for some cgroup accounting issues.
    
       - rt: Bandwidth timer could, under unusual circumstances, be failed
         to armed, leading to indefinite throttling."
    
    [ Description above by Peter Zijlstra ]
    
    * tag 'sched_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      sched/fair: Replace CFS internal cpu_util() with cpu_util_cfs()
      sched/fair: Cleanup task_util and capacity type
      sched/rt: Try to restart rt period timer when rt runtime exceeded
      sched/fair: Document the slow path and fast path in select_task_rq_fair
      sched/fair: Fix per-CPU kthread and wakee stacking for asym CPU capacity
      sched/fair: Fix detection of per-CPU kthreads waking a task
      sched/cpuacct: Make user/system times in cpuacct.stat more precise
      sched/cpuacct: Fix user/system in shown cpuacct.usage*
      cpuacct: Convert BUG_ON() to WARN_ON_ONCE()
      cputime, cpuacct: Include guest time in user time in cpuacct.stat
      psi: Fix PSI_MEM_FULL state when tasks are in memstall and doing reclaim
      sched/core: Forced idle accounting
      psi: Add a missing SPDX license header
      psi: Remove repeated verbose comment

commit 01367e86e90948b1ae8f66b2c23aadd7e8374e34
Merge: 3e3a138a46906 552a23a0e5d0a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 17:06:42 2022 -0800

    Merge tag 'Wcast-function-type-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux
    
    Pull cast-function-type warning addition from Gustavo A. R. Silva:
     "This globally enables -Wcast-function-type.
    
      We need to make sure new function cast mismatches are not introduced
      in the kernel in order to avoid tripping CFI checking"
    
    * tag 'Wcast-function-type-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux:
      Makefile: Enable -Wcast-function-type

commit 3e3a138a46906641d95599040f2470a60740c399
Merge: c1eb8f6cff344 b0343ab330ae4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 16:09:36 2022 -0800

    Merge tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm
    
    Pull ARM updates from Russell King:
    
     - amba bus irq rework
    
     - add kfence support
    
     - support for Cortex M33 and M55 CPUs
    
     - kbuild updates for decompressor
    
     - let core code manage thread_info::cpu
    
     - avoid unpredictable NOP encoding in decompressor
    
     - reduce information printed in calltraces
    
    * tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm:
      ARM: reduce the information printed in call traces
      ARM: 9168/1: Add support for Cortex-M55 processor
      ARM: 9167/1: Add support for Cortex-M33 processor
      ARM: 9166/1: Support KFENCE for ARM
      ARM: 9165/1: mm: Provide is_write_fault()
      ARM: 9164/1: mm: Provide set_memory_valid()
      ARM: 9163/1: amba: Move of_amba_device_decode_irq() into amba_probe()
      ARM: 9162/1: amba: Kill sysfs attribute file of irq
      ARM: 9161/1: mm: mark private VM_FAULT_X defines as vm_fault_t
      ARM: 9159/1: decompressor: Avoid UNPREDICTABLE NOP encoding
      ARM: 9158/1: leave it to core code to manage thread_info::cpu
      ARM: 9154/1: decompressor: do not copy source files while building

commit c1eb8f6cff3442b0b7eff5b801c9745ea9abcb14
Merge: f18e2d8772696 68d247ad38b1e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:42:45 2022 -0800

    Merge tag 'for-5.17/parisc-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
    
    Pull parisc architecture updates from Helge Deller:
    
     - Fix lpa and lpa_user defines (John David Anglin)
    
     - Fix symbol lookup of init functions with an __is_kernel() fix (Helge
       Deller)
    
     - Fix wrong pdc_toc_pim_11 and pdc_toc_pim_20 definitions (Helge
       Deller)
    
     - Add lws_atomic_xchg and lws_atomic_store syscalls (John David Anglin)
    
     - Rewrite light-weight syscall and futex code (John David Anglin)
    
     - Enable TOC (transfer of contents) feature unconditionally (Helge
       Deller)
    
     - Improve fault handler messages (John David Anglin)
    
     - Improve build process (Masahiro Yamada)
    
     - Reduce kernel code footprint of user access functions (Helge Deller)
    
     - Fix build error due to outX() macros (Bart Van Assche)
    
     - Ue default_groups in kobj_type in pdc_stable (Greg Kroah-Hartman)
    
     - Default to 16 CPUs on 32-bit kernel (Helge Deller)
    
    * tag 'for-5.17/parisc-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux:
      parisc: Default to 16 CPUs on 32-bit kernel
      sections: Fix __is_kernel() to include init ranges
      parisc: Re-use toc_stack as hpmc_stack
      parisc: Enable TOC (transfer of contents) feature unconditionally
      parisc: io: Improve the outb(), outw() and outl() macros
      parisc: pdc_stable: use default_groups in kobj_type
      parisc: Add kgdb io_module to read chars via PDC
      parisc: Fix pdc_toc_pim_11 and pdc_toc_pim_20 definitions
      parisc: Add lws_atomic_xchg and lws_atomic_store syscalls
      parisc: Rewrite light-weight syscall and futex code
      parisc: Enhance page fault termination message
      parisc: Don't call faulthandler_disabled() in do_page_fault()
      parisc: Switch user access functions to signal errors in r29 instead of r8
      parisc: Avoid calling faulthandler_disabled() twice
      parisc: Fix lpa and lpa_user defines
      parisc: Define depi_safe macro
      parisc: decompressor: do not copy source files while building

commit f18e2d877269672597088c308ca75d7d52620028
Merge: f12fc75ef7db4 b6aa86cff44cf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:38:11 2022 -0800

    Merge tag 'x86_build_for_v5.17_rc1-p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull missed x86 build updates from Borislav Petkov:
     "In the heat of the battle between me and the tip pull requests, I've
      sent you the tip:x86/build branch without the two top-most commits
      from Ingo (it appears I hadn't fast-forwarded my local branch, sorry
      about that).
    
      Therefore, here's a part 2 of x86/build for 5.17.
    
       - Make x86 defconfigs more useful by enabling
         CONFIG_LOCALVERSION_AUTO and CONFIG_KALLSYMS_ALL
    
      And while you merge that, I'll be at the blackboard, writing:
    
        I will always fast-forward local branches before tagging and sending pull requests to Linus.
        I will always fast-forward local branches before tagging and sending pull requests to Linus.
        I will always fast-forward local branches before tagging and sending pull requests..."
    
    * tag 'x86_build_for_v5.17_rc1-p2' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/kbuild: Enable CONFIG_KALLSYMS_ALL=y in the defconfigs
      x86/defconfig: Enable CONFIG_LOCALVERSION_AUTO=y in the defconfig

commit f12fc75ef7db44d71d5a509e2f1bec6966b73776
Merge: f69212114220e 42f4046bc4ba5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:36:30 2022 -0800

    Merge tag 'efi-next-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi
    
    Pull EFI updates from Ard Biesheuvel:
    
     - support taking the measurement of the initrd when loaded via the
       LoadFile2 protocol
    
     - kobject API cleanup from Greg
    
     - some header file whitespace fixes
    
    * tag 'efi-next-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi:
      efi: use default_groups in kobj_type
      efi/libstub: measure loaded initrd info into the TPM
      efi/libstub: consolidate initrd handling across architectures
      efi/libstub: x86/mixed: increase supported argument count
      efi/libstub: add prototype of efi_tcg2_protocol::hash_log_extend_event()
      include/linux/efi.h: Remove unneeded whitespaces before tabs

commit f69212114220edf8372867088b97b47760b6839d
Merge: 5672cdfba4fef db0dd9cee8227
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:26:52 2022 -0800

    Merge tag 'for-linus-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml
    
    Pull UML updates from Richard Weinberger:
    
     - set_fs removal
    
     - Devicetree support
    
     - Many cleanups from Al
    
     - Various virtio and build related fixes
    
    * tag 'for-linus-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml: (31 commits)
      um: virtio_uml: Allow probing from devicetree
      um: Add devicetree support
      um: Extract load file helper from initrd.c
      um: remove set_fs
      hostfs: Fix writeback of dirty pages
      um: Use swap() to make code cleaner
      um: header debriding - sigio.h
      um: header debriding - os.h
      um: header debriding - net_*.h
      um: header debriding - mem_user.h
      um: header debriding - activate_ipi()
      um: common-offsets.h debriding...
      um, x86: bury crypto_tfm_ctx_offset
      um: unexport handle_page_fault()
      um: remove a dangling extern of syscall_trace()
      um: kill unused cpu()
      uml/i386: missing include in barrier.h
      um: stop polluting the namespace with registers.h contents
      logic_io instance of iounmap() needs volatile on argument
      um: move amd64 variant of mmap(2) to arch/x86/um/syscalls_64.c
      ...

commit 5672cdfba4fefd6178b6c4078cb1bb7bf6ce0573
Merge: 3f67eaed57dae aa39cc675799b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:23:27 2022 -0800

    Merge tag 'for-linus-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs
    
    Pull JFFS2, UBI and UBIFS updates from Richard Weinberger:
     "JFFS2:
       - Fix for a deadlock in jffs2_write_begin()
    
      UBI:
       - Fixes in comments
    
      UBIFS:
       - Expose error counters in sysfs
       - Many bugfixes found by Hulk Robot and others"
    
    * tag 'for-linus-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rw/ubifs:
      jffs2: GC deadlock reading a page that is used in jffs2_write_begin()
      ubifs: read-only if LEB may always be taken in ubifs_garbage_collect
      ubifs: fix double return leb in ubifs_garbage_collect
      ubifs: fix slab-out-of-bounds in ubifs_change_lp
      ubifs: fix snprintf() length check
      ubifs: Document sysfs nodes
      ubifs: Export filesystem error counters
      ubifs: Error path in ubifs_remount_rw() seems to wrongly free write buffers
      ubifs: Make use of the helper macro kthread_run()
      ubi: Fix a mistake in comment
      ubifs: Fix spelling mistakes

commit 3f67eaed57dae339603441cf0c0a74ec77a9fc03
Merge: 8481c323e4ea0 feae43f8aa883
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:21:54 2022 -0800

    Merge tag 'dlm-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm
    
    Pull dlm updates from David Teigland:
     "This set includes the normal collection of minor fixes and cleanups,
      new kmem caches for network messaging structs, a start on some basic
      tracepoints, and some new debugfs files for inserting test messages"
    
    * tag 'dlm-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm: (32 commits)
      fs: dlm: print cluster addr if non-cluster node connects
      fs: dlm: memory cache for lowcomms hotpath
      fs: dlm: memory cache for writequeue_entry
      fs: dlm: memory cache for midcomms hotpath
      fs: dlm: remove wq_alloc mutex
      fs: dlm: use event based wait for pending remove
      fs: dlm: check for pending users filling buffers
      fs: dlm: use list_empty() to check last iteration
      fs: dlm: fix build with CONFIG_IPV6 disabled
      fs: dlm: replace use of socket sk_callback_lock with sock_lock
      fs: dlm: don't call kernel_getpeername() in error_report()
      fs: dlm: fix potential buffer overflow
      fs: dlm:Remove unneeded semicolon
      fs: dlm: remove double list_first_entry call
      fs: dlm: filter user dlm messages for kernel locks
      fs: dlm: add lkb waiters debugfs functionality
      fs: dlm: add lkb debugfs functionality
      fs: dlm: allow create lkb with specific id range
      fs: dlm: add debugfs rawmsg send functionality
      fs: dlm: let handle callback data as void
      ...

commit 8481c323e4ea0a65f0578107a3e668c1c69cf474
Merge: 1dbfae0113f14 74382e277ae97
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:20:32 2022 -0800

    Merge tag 'gfs2-v5.16-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2
    
    Pull gfs2 updates from Andreas Gruenbacher:
     "Various minor gfs2 cleanups and fixes"
    
    * tag 'gfs2-v5.16-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2:
      gfs2: dump inode object for iopen glocks
      gfs2: Fix gfs2_instantiate description
      gfs2: Remove redundant check for GLF_INSTANTIATE_NEEDED
      gfs2: remove redundant set of INSTANTIATE_NEEDED
      gfs2: Fix __gfs2_holder_init function name in kernel-doc comment

commit 65552b02a10acea68127081faf414b84a65d1855
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Tue Jan 4 17:38:36 2022 -0800

    xfs: take the ILOCK when readdir inspects directory mapping data
    
    I was poking around in the directory code while diagnosing online fsck
    bugs, and noticed that xfs_readdir doesn't actually take the directory
    ILOCK when it calls xfs_dir2_isblock.  xfs_dir_open most probably loaded
    the data fork mappings and the VFS took i_rwsem (aka IOLOCK_SHARED) so
    we're protected against writer threads, but we really need to follow the
    locking model like we do in other places.
    
    To avoid unnecessarily cycling the ILOCK for fairly small directories,
    change the block/leaf _getdents functions to consume the ILOCK hold that
    the parent readdir function took to decide on a _getdents implementation.
    
    It is ok to cycle the ILOCK in readdir because the VFS takes the IOLOCK
    in the appropriate mode during lookups and writes, and we don't want to
    be holding the ILOCK when we copy directory entries to userspace in case
    there's a page fault.  We really only need it to protect against data
    fork lookups, like we do for other files.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit 1dbfae0113f1423b42c304989a3cc8a7dd0ea53e
Merge: 11fc88c2e49ba 6eeaf88fd586f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:07:49 2022 -0800

    Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
    
    Pull ext4 updates from Ted Ts'o:
     "Convert ext4 to use the new mount API, and add support for the
      FS_IOC_GETFSLABEL and FS_IOC_SETFSLABEL ioctls.
    
      In addition the usual large number of clean ups and bug fixes, in
      particular for the fast_commit feature"
    
    * tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4: (48 commits)
      ext4: don't use the orphan list when migrating an inode
      ext4: use BUG_ON instead of if condition followed by BUG
      ext4: fix a copy and paste typo
      ext4: set csum seed in tmp inode while migrating to extents
      ext4: remove unnecessary 'offset' assignment
      ext4: remove redundant o_start statement
      ext4: drop an always true check
      ext4: remove unused assignments
      ext4: remove redundant statement
      ext4: remove useless resetting io_end_size in mpage_process_page()
      ext4: allow to change s_last_trim_minblks via sysfs
      ext4: change s_last_trim_minblks type to unsigned long
      ext4: implement support for get/set fs label
      ext4: only set EXT4_MOUNT_QUOTA when journalled quota file is specified
      ext4: don't use kfree() on rcu protected pointer sbi->s_qf_names
      ext4: avoid trim error on fs with small groups
      ext4: fix an use-after-free issue about data=journal writeback mode
      ext4: fix null-ptr-deref in '__ext4_journal_ensure_credits'
      ext4: initialize err_blk before calling __ext4_get_inode_loc
      ext4: fix a possible ABBA deadlock due to busy PA
      ...

commit 11fc88c2e49ba8e3ca827dc9bdd7b7216be30a36
Merge: d601e58c5f290 7e937bb3cbe1f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 15:01:50 2022 -0800

    Merge tag 'xfs-5.17-merge-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
    
    Pull xfs updates from Darrick Wong:
     "The big new feature here is that the mount code now only bothers to
      try to free stale COW staging extents if the fs unmounted uncleanly.
      This should reduce mount times, particularly on filesystems supporting
      reflink and containing a large number of allocation groups.
    
      Everything else this cycle are bugfixes, as the iomap folios
      conversion should be plenty enough excitement for anyone. That and I
      ran out of brain bandwidth after Thanksgiving last year.
    
      Summary:
    
       - Fix log recovery with da btree buffers when metauuid is in use.
    
       - Fix type coercion problems in xattr buffer size validation.
    
       - Fix a bug in online scrub dir leaf bestcount checking.
    
       - Only run COW recovery when recovering the log.
    
       - Fix symlink target buffer UAF problems and symlink locking problems
         by not exposing xfs innards to the VFS.
    
       - Fix incorrect quotaoff lock usage.
    
       - Don't let transactions cancel cleanly if they have deferred work
         items attached.
    
       - Fix a UAF when we're deciding if we need to relog an intent item.
    
       - Reduce kvmalloc overhead for log shadow buffers.
    
       - Clean up sysfs attr group usage.
    
       - Fix a bug where scrub's bmap/rmap checking could race with a quota
         file block allocation due to insufficient locking.
    
       - Teach scrub to complain about invalid project ids"
    
    * tag 'xfs-5.17-merge-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux:
      xfs: warn about inodes with project id of -1
      xfs: hold quota inode ILOCK_EXCL until the end of dqalloc
      xfs: Remove redundant assignment of mp
      xfs: reduce kvmalloc overhead for CIL shadow buffers
      xfs: sysfs: use default_groups in kobj_type
      xfs: prevent UAF in xfs_log_item_in_current_chkpt
      xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list()
      xfs: Fix comments mentioning xfs_ialloc
      xfs: check sb_meta_uuid for dabuf buffer recovery
      xfs: fix a bug in the online fsck directory leaf1 bestcount check
      xfs: only run COW extent recovery when there are no live extents
      xfs: don't expose internal symlink metadata buffers to the vfs
      xfs: fix quotaoff mutex usage now that we don't support disabling it
      xfs: shut down filesystem if we xfs_trans_cancel with deferred work items

commit d601e58c5f2901783428bc1181e83ff783592b6b
Merge: 9149fe8ba7ff7 36c86a9e1be3b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 14:53:40 2022 -0800

    Merge tag 'for-5.17-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
    
    Pull btrfs updates from David Sterba:
     "This end of the year branch is intentionally not that exciting. Most
      of the changes are under the hood, but there are some minor user
      visible improvements and several performance improvements too.
    
      Features:
    
       - make send work with concurrent block group relocation.
    
         We're not allowed to prevent send failing or silently producing
         some bad stream but with more fine grained locking and checks it's
         possible. The send vs deduplication exclusion could reuse the same
         logic in the future.
    
       - new exclusive operation 'balance paused' to allow adding a device
         to filesystem with paused balance
    
       - new sysfs file for fsid stored in the per-device directory to help
         distinguish devices when seeding is enabled, the fsid may differ
         from the one reported by the filesystem
    
      Performance improvements:
    
       - less metadata needed for directory logging, directory deletion is
         20-40% faster
    
       - in zoned mode, cache zone information during mount to speed up
         repeated queries (about 50% speedup)
    
       - free space tree entries get indexed and searched by size (latency
         -30%, search run time -30%)
    
       - less contention in tree node locking when inserting a key and no
         splits are needed (files/sec in fsmark improves by 1-20%)
    
      Fixes:
    
       - fix ENOSPC failure when attempting direct IO write into NOCOW range
    
       - fix deadlock between quota enable and other quota operations
    
       - global reserve minimum calculations fixed to account for free space
         tree
    
       - in zoned mode, fix condition for chunk allocation that may not find
         the right zone for reuse and could lead to early ENOSPC
    
      Core:
    
       - global reserve stealing got simplified and cleaned up in evict
    
       - remove async transaction commit based on manual transaction refs,
         reuse existing kthread and mechanisms to let it commit transaction
         before timeout
    
       - preparatory work for extent tree v2, add wrappers for global tree
         roots, truncation path cleanups
    
       - remove readahead framework, it's a bit overengineered and used only
         for scrub, and yet it does not cover all its needs, there is
         another readahead built in the b-tree search that is now used,
         performance drop on HDD is about 5% which is acceptable and scrub
         is often throttled anyway, on SSDs there's no reported drop but
         slight improvement
    
       - self tests report extent tree state when error occurs
    
       - replace assert with debugging information when an uncommitted
         transaction is found at unmount time
    
      Other:
    
       - error handling improvements
    
       - other cleanups and refactoring"
    
    * tag 'for-5.17-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux: (115 commits)
      btrfs: output more debug messages for uncommitted transaction
      btrfs: respect the max size in the header when activating swap file
      btrfs: fix argument list that the kdoc format and script verified
      btrfs: remove unnecessary parameter type from compression_decompress_bio
      btrfs: selftests: dump extent io tree if extent-io-tree test failed
      btrfs: scrub: cleanup the argument list of scrub_stripe()
      btrfs: scrub: cleanup the argument list of scrub_chunk()
      btrfs: remove reada infrastructure
      btrfs: scrub: use btrfs_path::reada for extent tree readahead
      btrfs: scrub: remove the unnecessary path parameter for scrub_raid56_parity()
      btrfs: refactor unlock_up
      btrfs: skip transaction commit after failure to create subvolume
      btrfs: zoned: fix chunk allocation condition for zoned allocator
      btrfs: add extent allocator hook to decide to allocate chunk or not
      btrfs: zoned: unset dedicated block group on allocation failure
      btrfs: zoned: drop redundant check for REQ_OP_ZONE_APPEND and btrfs_is_zoned
      btrfs: zoned: sink zone check into btrfs_repair_one_zone
      btrfs: zoned: simplify btrfs_check_meta_write_pointer
      btrfs: zoned: encapsulate inode locking for zoned relocation
      btrfs: sysfs: add devinfo/fsid to retrieve actual fsid from the device
      ...

commit 9149fe8ba7ff798ea1c6b1fa05eeb59f95f9a94a
Merge: 579f3a6d32a9c 09c543798c3cd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 14:51:10 2022 -0800

    Merge tag 'erofs-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs
    
    Pull erofs updates from Gao Xiang:
     "In this cycle, tail-packing data inline for compressed files is now
      supported so that tail pcluster can be stored and read together with
      inode metadata in order to save data I/O and storage space.
    
      In addition to that, to prepare for the upcoming subpage, folio and
      fscache features, we also introduce meta buffers to get rid of
      erofs_get_meta_page() since it was too close to the page itself.
    
      In addition, in order to show supported kernel features and control
      sync decompression strategy, new sysfs nodes are introduced in this
      cycle as well.
    
      Summary:
    
       - add sysfs interface and a sysfs node to control sync decompression
    
       - add tail-packing inline support for compressed files
    
       - get rid of erofs_get_meta_page()"
    
    * tag 'erofs-for-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs:
      erofs: use meta buffers for zmap operations
      erofs: use meta buffers for xattr operations
      erofs: use meta buffers for super operations
      erofs: use meta buffers for inode operations
      erofs: introduce meta buffer operations
      erofs: add on-disk compressed tail-packing inline support
      erofs: support inline data decompression
      erofs: support unaligned data decompression
      erofs: introduce z_erofs_fixup_insize
      erofs: tidy up z_erofs_lz4_decompress
      erofs: clean up erofs_map_blocks tracepoints
      erofs: Replace zero-length array with flexible-array member
      erofs: add sysfs node to control sync decompression strategy
      erofs: add sysfs interface
      erofs: rename lz4_0pading to zero_padding

commit 579f3a6d32a9c3d1cf5c2b1bd66817a2db31a968
Author: Paul E. McKenney <paulmck@kernel.org>
Date:   Tue Jan 11 13:54:31 2022 -0800

    drivers/pcmcia: Fix ifdef covering yenta_pm_ops
    
    Currently, yenta_dev_suspend_noirq(), yenta_dev_resume_noirq(), and
    yenta_pm_ops are covered by "#ifdef CONFIG_PM", which results in
    compiler warnings in kernels built with CONFIG_PM_SLEEP=n and
    CONFIG_PM=y:
    
      drivers/pcmcia/yenta_socket.c:1322:12: warning: ‘yenta_dev_resume_noirq’ defined but not used [-Wunused-function]
       1322 | static int yenta_dev_resume_noirq(struct device *dev)
            |            ^~~~~~~~~~~~~~~~~~~~~~
      drivers/pcmcia/yenta_socket.c:1303:12: warning: ‘yenta_dev_suspend_noirq’ defined but not used [-Wunused-function]
       1303 | static int yenta_dev_suspend_noirq(struct device *dev)
            |            ^~~~~~~~~~~~~~~~~~~~~~~
    
    This affects kernels built without suspend and hibernation.
    
    Avoid these warnings by using "#ifdef CONFIG_PM_SLEEP".
    
    Fixes: 3daaf2c7aae8 ("pcmcia: Make use of the helper macro SET_NOIRQ_SYSTEM_SLEEP_PM_OPS()")
    Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit d7bdba1c81f7e7bad12c7c7ce55afa3c7b0821ef
Author: David Howells <dhowells@redhat.com>
Date:   Wed Dec 22 17:21:04 2021 +0000

    9p, afs, ceph, nfs: Use current_is_kswapd() rather than gfpflags_allow_blocking()
    
    In 9p, afs ceph, and nfs, gfpflags_allow_blocking() (which wraps a
    test for __GFP_DIRECT_RECLAIM being set) is used to determine if
    ->releasepage() should wait for the completion of a DIO write to fscache
    with something like:
    
            if (folio_test_fscache(folio)) {
                    if (!gfpflags_allow_blocking(gfp) || !(gfp & __GFP_FS))
                            return false;
                    folio_wait_fscache(folio);
            }
    
    Instead, current_is_kswapd() should be used instead.
    
    Note that this is based on a patch originally by Zhaoyang Huang[1].  In
    addition to extending it to the other network filesystems and putting it on
    top of my fscache rewrite, it also needs to include linux/swap.h in a bunch
    of places.  Can current_is_kswapd() be moved to linux/mm.h?
    
    Changes
    =======
    ver #5:
     - Dropping the changes for cifs.
    
    Originally-signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
    Co-developed-by: David Howells <dhowells@redhat.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
    cc: Dominique Martinet <asmadeus@codewreck.org>
    cc: Marc Dionne <marc.dionne@auristor.com>
    cc: Steve French <smfrench@gmail.com>
    cc: Trond Myklebust <trond.myklebust@hammerspace.com>
    cc: linux-cachefs@redhat.com
    cc: v9fs-developer@lists.sourceforge.net
    cc: linux-afs@lists.infradead.org
    cc: ceph-devel@vger.kernel.org
    cc: linux-cifs@vger.kernel.org
    cc: linux-nfs@vger.kernel.org
    cc: linux-mm@kvack.org
    Link: https://lore.kernel.org/r/1638952658-20285-1-git-send-email-huangzhaoyang@gmail.com/ [1]
    Link: https://lore.kernel.org/r/164021590773.640689.16777975200823659231.stgit@warthog.procyon.org.uk/ # v4

commit 5dfbfe71e32406f08480185d396d94cf7fc7a7d6
Merge: 84bfcc0b69940 bd303368b776e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 14:26:55 2022 -0800

    Merge tag 'fs.idmapped.v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux
    
    Pull fs idmapping updates from Christian Brauner:
     "This contains the work to enable the idmapping infrastructure to
      support idmapped mounts of filesystems mounted with an idmapping.
    
      In addition this contains various cleanups that avoid repeated
      open-coding of the same functionality and simplify the code in quite a
      few places.
    
      We also finish the renaming of the mapping helpers we started a few
      kernel releases back and move them to a dedicated header to not
      continue polluting the fs header needlessly with low-level idmapping
      helpers. With this series the fs header only contains idmapping
      helpers that interact with fs objects.
    
      Currently we only support idmapped mounts for filesystems mounted
      without an idmapping themselves. This was a conscious decision
      mentioned in multiple places (cf. [1]).
    
      As explained at length in [3] it is perfectly fine to extend support
      for idmapped mounts to filesystem's mounted with an idmapping should
      the need arise. The need has been there for some time now (cf. [2]).
    
      Before we can port any filesystem that is mountable with an idmapping
      to support idmapped mounts in the coming cycles, we need to first
      extend the mapping helpers to account for the filesystem's idmapping.
      This again, is explained at length in our documentation at [3] and
      also in the individual commit messages so here's an overview.
    
      Currently, the low-level mapping helpers implement the remapping
      algorithms described in [3] in a simplified manner as we could rely on
      the fact that all filesystems supporting idmapped mounts are mounted
      without an idmapping.
    
      In contrast, filesystems mounted with an idmapping are very likely to
      not use an identity mapping and will instead use a non-identity
      mapping. So the translation step from or into the filesystem's
      idmapping in the remapping algorithm cannot be skipped for such
      filesystems.
    
      Non-idmapped filesystems and filesystems not supporting idmapped
      mounts are unaffected by this change as the remapping algorithms can
      take the same shortcut as before. If the low-level helpers detect that
      they are dealing with an idmapped mount but the underlying filesystem
      is mounted without an idmapping we can rely on the previous shortcut
      and can continue to skip the translation step from or into the
      filesystem's idmapping. And of course, if the low-level helpers detect
      that they are not dealing with an idmapped mount they can simply
      return the relevant id unchanged; no remapping needs to be performed
      at all.
    
      These checks guarantee that only the minimal amount of work is
      performed. As before, if idmapped mounts aren't used the low-level
      helpers are idempotent and no work is performed at all"
    
    Link: 2ca4dcc4909d ("fs/mount_setattr: tighten permission checks") [1]
    Link: https://github.com/containers/podman/issues/10374 [2]
    Link: Documentations/filesystems/idmappings.rst [3]
    Link: a65e58e791a1 ("fs: document and rename fsid helpers") [4]
    
    * tag 'fs.idmapped.v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux:
      fs: support mapped mounts of mapped filesystems
      fs: add i_user_ns() helper
      fs: port higher-level mapping helpers
      fs: remove unused low-level mapping helpers
      fs: use low-level mapping helpers
      docs: update mapping documentation
      fs: account for filesystem mappings
      fs: tweak fsuidgid_has_mapping()
      fs: move mapping helpers
      fs: add is_idmapped_mnt() helper

commit e6435f1e02f410e3507f02a37c0fbb17971ddc7c
Author: David Howells <dhowells@redhat.com>
Date:   Mon Dec 6 15:54:04 2021 +0000

    fscache: Add a tracepoint for cookie use/unuse
    
    Add a tracepoint to track fscache_use/unuse_cookie().
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/164021588628.640689.12942919367404043608.stgit@warthog.procyon.org.uk/ # v4

commit e0484344c0413e1fcd5642b77d49c7648fb194ec
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 10 13:25:03 2021 +0000

    fscache: Rewrite documentation
    
    Rewrite the fscache documentation.
    
    Changes
    =======
    ver #3:
     - The volume coherency data is now an arbitrarily-sized blob, not a u64.
    
    ver #2:
     - Put quoting around some bits of C being referred to in the docs[1].
     - Stripped the markup off the ref to the netfs lib doc[2].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/20211130175119.63d0e7aa@canb.auug.org.au/ [1]
    Link: https://lore.kernel.org/r/20211130162311.105fcfa5@canb.auug.org.au/ [2]
    Link: https://lore.kernel.org/r/163819672252.215744.15454333549935901588.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906986754.143852.17703291789683936950.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967193834.1823006.15991526817786159772.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021585970.640689.3162537597817521032.stgit@warthog.procyon.org.uk/ # v4

commit 1702e79734104d711a84ff55bd6a93c21947bc01
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Dec 7 08:44:51 2021 -0500

    ceph: add fscache writeback support
    
    When updating the backing store from the pagecache (a'la writepage or
    writepages), write to the cache first. This allows us to keep caching
    files even when they are being written, as long as we have appropriate
    caps.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Link: https://lore.kernel.org/r/20211129162907.149445-3-jlayton@kernel.org/ # v1
    Link: https://lore.kernel.org/r/20211207134451.66296-3-jlayton@kernel.org/ # v2
    Link: https://lore.kernel.org/r/163906985808.143852.1383891557313186623.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967190257.1823006.16713609520911954804.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021585020.640689.6765214932458435472.stgit@warthog.procyon.org.uk/ # v4

commit 400e1286c0ec3fd13d7ac0705c3c175bcb6d2899
Author: Jeff Layton <jlayton@kernel.org>
Date:   Tue Dec 7 08:44:50 2021 -0500

    ceph: conversion to new fscache API
    
    Now that the fscache API has been reworked and simplified, change ceph
    over to use it.
    
    With the old API, we would only instantiate a cookie when the file was
    open for reads. Change it to instantiate the cookie when the inode is
    instantiated and call use/unuse when the file is opened/closed.
    
    Also, ensure we resize the cached data on truncates, and invalidate the
    cache in response to the appropriate events. This will allow us to
    plumb in write support later.
    
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Link: https://lore.kernel.org/r/20211129162907.149445-2-jlayton@kernel.org/ # v1
    Link: https://lore.kernel.org/r/20211207134451.66296-2-jlayton@kernel.org/ # v2
    Link: https://lore.kernel.org/r/163906984277.143852.14697110691303589000.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967188351.1823006.5065634844099079351.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021581427.640689.14128682147127509264.stgit@warthog.procyon.org.uk/ # v4

commit 0046686da0ef692a6381260c3aa44291187eafc9
Author: Ian Rogers <irogers@google.com>
Date:   Thu Dec 23 10:39:47 2021 -0800

    perf test: Enable system wide for metricgroups test
    
    Uncore events as group leaders fail in per-thread mode causing exit
    errors. Enable system-wide for metricgroup testing. This fixes the HPC
    metric group when tested on skylakex.
    
    Fixes: 4a87dea9e60fe100 ("perf test: Workload test of metric and metricgroups")
    Signed-off-by: Ian Rogers <irogers@google.com>
    Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Stephane Eranian <eranian@google.com>
    Link: https://lore.kernel.org/r/20211223183948.3423989-1-irogers@google.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 7f435e42fd6b65fd8759963156e1ef0fb7d213f8
Author: Stafford Horne <shorne@gmail.com>
Date:   Tue Jan 11 11:55:37 2022 +0900

    openrisc: init: Add support for common clk
    
    When testing the new litex_mmc driver it was found to not work on
    OpenRISC due to missing support for common clk.  This patch does the
    basic initialization to allow OpenRISC to use the common clk framework.
    
    Signed-off-by: Stafford Horne <shorne@gmail.com>
    Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>

commit 84bfcc0b6994057905cf98d2c5cedef48b3322b5
Merge: 5d7e52237c59e 65e38e32a959d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 13:11:10 2022 -0800

    Merge tag 'integrity-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
    
    Pull integrity subsystem updates from Mimi Zohar:
     "The few changes are all kexec related:
    
       - The MOK keys are loaded onto the .platform keyring in order to
         verify the kexec kernel image signature.
    
         However, the MOK keys should only be trusted when secure boot is
         enabled. Before loading the MOK keys onto the .platform keyring,
         make sure the system is booted in secure boot mode.
    
       - When carrying the IMA measurement list across kexec, limit dumping
         the measurement list to when dynamic debug or CONFIG_DEBUG is
         enabled.
    
       - kselftest: add kexec_file_load selftest support for PowerNV and
         other cleanup"
    
    * tag 'integrity-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity:
      selftests/kexec: Enable secureboot tests for PowerPC
      ima: silence measurement list hexdump during kexec
      selftests/kexec: update searching for the Kconfig
      selftest/kexec: fix "ignored null byte in input" warning
      integrity: Do not load MOK and MOKx when secure boot be disabled
      ima: Fix undefined arch_ima_get_secureboot() and co

commit 5d7e52237c59e37a25da854196fc70e9b09704d9
Merge: a135ce4400bb8 ed98ea2128b6f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 13:08:21 2022 -0800

    Merge tag 'audit-pr-20220110' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit
    
    Pull audit updates from Paul Moore:
     "Four audit patches for v5.17:
    
       - Harden the code through additional use of the struct_size() macro
         and zero-length arrays to flexible-array conversions.
    
       - Ensure that processes which generate userspace audit records are
         not exempt from the kernel's audit throttling when the audit queues
         are being overrun"
    
    * tag 'audit-pr-20220110' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit:
      audit: replace zero-length array with flexible-array member
      audit: use struct_size() helper in audit_[send|make]_reply()
      audit: ensure userspace is penalized the same as the kernel when under pressure
      audit: use struct_size() helper in kmalloc()

commit a135ce4400bb87f229ab33a663987327d9e0b2a0
Merge: dabd40ecaf693 6cd9d4b978915
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 13:03:06 2022 -0800

    Merge tag 'selinux-pr-20220110' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux
    
    Pull selinux updates from Paul Moore:
     "Nothing too significant, but five SELinux patches for v5.17 that do
      the following:
    
       - Harden the code through additional use of the struct_size() macro
    
       - Plug some memory leaks
    
       - Clean up the code via removal of the security_add_mnt_opt() LSM
         hook and minor tweaks to selinux_add_opt()
    
       - Rename security_task_getsecid_subj() to better reflect its actual
         behavior/use - now called security_current_getsecid_subj()"
    
    * tag 'selinux-pr-20220110' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux:
      selinux: minor tweaks to selinux_add_opt()
      selinux: fix potential memleak in selinux_add_opt()
      security,selinux: remove security_add_mnt_opt()
      selinux: Use struct_size() helper in kmalloc()
      lsm: security_task_getsecid_subj() -> security_current_getsecid_subj()

commit dabd40ecaf693a18afd4c59c8d7280610d95b66e
Merge: 4aa1b8257fba5 d99a8af48a3de
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:58:41 2022 -0800

    Merge tag 'tpmdd-next-v5.17-fixed' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd
    
    Pull TPM updates from Jarkko Sakkinen:
     "Other than bug fixes for TPM, this includes a patch for asymmetric
      keys to allow to look up and verify with self-signed certificates
      (keys without so called AKID - Authority Key Identifier) using a new
      "dn:" prefix in the query"
    
    * tag 'tpmdd-next-v5.17-fixed' of git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd:
      lib: remove redundant assignment to variable ret
      tpm: fix NPE on probe for missing device
      tpm: fix potential NULL pointer access in tpm_del_char_device
      tpm: Add Upgrade/Reduced mode support for TPM2 modules
      char: tpm: cr50: Set TPM_FIRMWARE_POWER_MANAGED based on device property
      keys: X.509 public key issuer lookup without AKID
      tpm_tis: Fix an error handling path in 'tpm_tis_core_init()'
      tpm: tpm_tis_spi_cr50: Add default RNG quality
      tpm/st33zp24: drop unneeded over-commenting
      tpm: add request_locality before write TPM_INT_ENABLE

commit 5eb877b282fecc8b8a6ac6d4ce0d5057f9d3bad0
Author: Kent Russell <kent.russell@amd.com>
Date:   Tue Jan 11 12:28:27 2022 -0500

    drm/amdkfd: Fix ASIC name typos
    
    Three misspelled ASICs in comments here, so fix the spelling
    
    Signed-off-by: Kent Russell <kent.russell@amd.com>
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 6f4cb84ae0f6d56d0b5071a0057df9c7cfb82ce1
Author: Felix Kuehling <Felix.Kuehling@amd.com>
Date:   Tue Dec 7 22:03:52 2021 -0500

    drm/amdkfd: Fix DQM asserts on Hawaii
    
    start_nocpsch would never set dqm->sched_running on Hawaii due to an
    early return statement. This would trigger asserts in other functions
    and end up in inconsistent states.
    
    Bug: https://github.com/RadeonOpenCompute/ROCm/issues/1624
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Reviewed-by: Kent Russell <kent.russell@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit dc5d4aff2e99c312df8abbe1ee9a731d2913bc1b
Author: Harry Wentland <harry.wentland@amd.com>
Date:   Tue Jan 4 10:45:41 2022 -0500

    drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
    
    For some reason this file isn't using the appropriate register
    headers for DCN headers, which means that on DCN2 we're getting
    the VIEWPORT_DIMENSION offset wrong.
    
    This means that we're not correctly carving out the framebuffer
    memory correctly for a framebuffer allocated by EFI and
    therefore see corruption when loading amdgpu before the display
    driver takes over control of the framebuffer scanout.
    
    Fix this by checking the DCE_HWIP and picking the correct offset
    accordingly.
    
    Long-term we should expose this info from DC as GMC shouldn't
    need to know about DCN registers.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Harry Wentland <harry.wentland@amd.com>
    Reviewed-by: Huang Rui <ray.huang@amd.com>
    Acked-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 15084a8e1658ddaea42c7d3a72ccbcec2b85f54c
Author: Tao Zhou <tao.zhou1@amd.com>
Date:   Mon Jan 10 15:12:38 2022 +0800

    drm/amd/pm: only send GmiPwrDnControl msg on master die (v3)
    
    PMFW only returns 0 on master die and sends NACK back on other dies for
    the message.
    
    v2: only send GmiPwrDnControl msg on master die instead of all
    dies.
    v3: remove the pointer check for get_socket_id and get_die_id as they
    should be present on Aldebaran.
    
    Signed-off-by: Tao Zhou <tao.zhou1@amd.com>
    Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 2096b74b1da5ca418827b54ac4904493bd9de89c
Author: Guchun Chen <guchun.chen@amd.com>
Date:   Fri Jan 7 16:31:20 2022 +0800

    drm/amdgpu: use spin_lock_irqsave to avoid deadlock by local interrupt
    
    This is observed in SRIOV case with virtual KMS as display.
    
    _raw_spin_lock_irqsave+0x37/0x40
    drm_handle_vblank+0x69/0x350 [drm]
    ? try_to_wake_up+0x432/0x5c0
    ? amdgpu_vkms_prepare_fb+0x1c0/0x1c0 [amdgpu]
    drm_crtc_handle_vblank+0x17/0x20 [drm]
    amdgpu_vkms_vblank_simulate+0x4d/0x80 [amdgpu]
    __hrtimer_run_queues+0xfb/0x230
    hrtimer_interrupt+0x109/0x220
    __sysvec_apic_timer_interrupt+0x64/0xe0
    asm_call_irq_on_stack+0x12/0x20
    
    Fixes: 84ec374bd580 ("drm/amdgpu: create amdgpu_vkms (v4)")
    Signed-off-by: Guchun Chen <guchun.chen@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Tested-by: Kelly Zytaruk <kelly.zytaruk@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 4eaf21b752891fffab3d51ac96e81194cda32d1c
Author: Prike Liang <Prike.Liang@amd.com>
Date:   Fri Nov 26 15:12:22 2021 +0800

    drm/amdgpu: not return error on the init_apu_flags
    
    In some APU project we needn't always assign flags to identify each other,
    so we may not need return an error.
    
    Signed-off-by: Prike Liang <Prike.Liang@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Huang Rui <ray.huang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit b121862c787c2a84ed5f42597aeeff5c1ead8f5b
Author: Felix Kuehling <Felix.Kuehling@amd.com>
Date:   Wed Dec 8 17:51:43 2021 -0500

    drm/amdkfd: Use prange->update_list head for remove_list
    
    The remove_list head was only used for keeping track of existing ranges
    that are to be removed from the svms->list. The update_list was used for
    new or existing ranges that need updated attributes. These two cases are
    mutually exclusive (i.e. the same range will never be on both lists).
    Therefore we can use the update_list head to track the remove_list and
    save another 16 bytes in the svm_range struct.
    
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Reviewed-by: Philip Yang <Philip.Yang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ef3b4137aa09a9ad38f42d4de087cedf1b98c521
Author: Felix Kuehling <Felix.Kuehling@amd.com>
Date:   Wed Dec 8 17:33:48 2021 -0500

    drm/amdkfd: Use prange->list head for insert_list
    
    There are seven list_heads in struct svm_range: list, update_list,
    remove_list, insert_list, svm_bo_list, deferred_list, child_list. This
    patch and the next one remove two of them that are redundant.
    
    The insert_list head was only used for new ranges that are not on the
    svms->list yet. So we can use that list head for keeping track of
    new ranges before they get added, and use list_move_tail to move them
    to the svms->list when ready.
    
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Reviewed-by: Philip Yang <Philip.Yang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 9b7a4de9f126d8c8d59052088213990159417d5b
Author: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Date:   Thu Dec 16 10:45:03 2021 +0100

    drm/amdkfd: make SPDX License expression more sound
    
    Commit b5f57384805a ("drm/amdkfd: Add sysfs bitfields and enums to uAPI")
    adds include/uapi/linux/kfd_sysfs.h with the "GPL-2.0 OR MIT WITH
    Linux-syscall-note" SPDX-License expression.
    
    The command ./scripts/spdxcheck.py warns:
    
      include/uapi/linux/kfd_sysfs.h: 1:48 Exception not valid for license MIT: Linux-syscall-note
    
    For a uapi header, the file under GPLv2 License must be combined with the
    Linux-syscall-note, but combining the MIT License with the
    Linux-syscall-note makes no sense, as the note provides an exception for
    GPL-licensed code, not for permissively licensed code.
    
    So, reorganize the SPDX expression to only combine the note with the GPL
    License condition. This makes spdxcheck happy again.
    
    Fixes: b5f57384805a ("drm/amdkfd: Add sysfs bitfields and enums to uAPI")
    Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Reviewed-by: kstewart@linuxfoundation.org
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit abfaf0eee97925905e742aa3b0b72e04a918fa9e
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Wed Jan 5 17:09:43 2022 +0800

    drm/amdkfd: Check for null pointer after calling kmemdup
    
    As the possible failure of the allocation, kmemdup() may return NULL
    pointer.
    Therefore, it should be better to check the 'props2' in order to prevent
    the dereference of NULL pointer.
    
    Fixes: 3a87177eb141 ("drm/amdkfd: Add topology support for dGPUs")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 978ffac878fd64039f95798b15b430032d2d89d5
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Jan 9 19:42:45 2022 +0100

    drm/amd/display: invalid parameter check in dmub_hpd_callback
    
    The function performs a check on the "adev" input parameter, however, it
    is used before the check.
    
    Initialize the "dev" variable after the sanity check to avoid a possible
    NULL pointer dereference.
    
    Fixes: e27c41d5b0681 ("drm/amd/display: Support for DMUB HPD interrupt handling")
    Addresses-Coverity-ID: 1493909 ("Null pointer dereference")
    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 8b5da5a458c95ad49571a6a6285800bf13409616
Author: Rajneesh Bhardwaj <rajneesh.bhardwaj@amd.com>
Date:   Mon Jan 10 12:14:10 2022 -0500

    Revert "drm/amdgpu: Don't inherit GEM object VMAs in child process"
    
    This reverts commit fbcdbfde87509d523132b59f661a355c731139d0.
    
    Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
    Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 83293f7f3d15fc56e86bd5067a2c88b6b233ac3a
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Fri Jan 7 15:40:10 2022 -0600

    drm/amd/display: reset dcn31 SMU mailbox on failures
    
    Otherwise future commands may fail as well leading to downstream
    problems that look like they stemmed from a timeout the first time
    but really didn't.
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 5fea167ec0a134cb61fde848a3c344f77f0c13a5
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 10:57:13 2022 +0100

    drm/amdkfd: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the amdkfd sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Cc: Felix Kuehling <Felix.Kuehling@amd.com>
    Cc: Alex Deucher <alexander.deucher@amd.com>
    Cc: "Christian König" <christian.koenig@amd.com>
    Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: amd-gfx@lists.freedesktop.org
    Cc: dri-devel@lists.freedesktop.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 7ff61cdcc8609a19f3eddf3fffc09a05ad6d6865
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 10:56:10 2022 +0100

    drm/amdgpu: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the amdgpu sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Cc: Alex Deucher <alexander.deucher@amd.com>
    Cc: "Christian König" <christian.koenig@amd.com>
    Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Cc: Hawking Zhang <Hawking.Zhang@amd.com>
    Cc: John Clements <john.clements@amd.com>
    Cc: Felix Kuehling <Felix.Kuehling@amd.com>
    Cc: Jonathan Kim <jonathan.kim@amd.com>
    Cc: Kevin Wang <kevin1.wang@amd.com>
    Cc: shaoyunl <shaoyun.liu@amd.com>
    Cc: Tao Zhou <tao.zhou1@amd.com>
    Cc: amd-gfx@lists.freedesktop.org
    Cc: dri-devel@lists.freedesktop.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 4cc9f86f851847e5ebfb56212d81f1a30b9d392b
Author: Tom St Denis <tom.stdenis@amd.com>
Date:   Fri Jan 7 06:57:41 2022 -0500

    drm/amd/amdgpu: Add pcie indirect support to amdgpu_mm_wreg_mmio_rlc()
    
    The function amdgpu_mm_wreg_mmio_rlc() is used by debugfs to write to
    MMIO registers.  It didn't support registers beyond the BAR mapped MMIO
    space.  This adds pcie indirect write support.
    
    Signed-off-by: Tom St Denis <tom.stdenis@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 575e55ee4fbc2c641a29b0054b3473e9fa81ae76
Author: Nirmoy Das <nirmoy.das@amd.com>
Date:   Fri Jan 7 09:51:15 2022 +0100

    drm/amdgpu: recover gart table at resume
    
    Get rid off pin/unpin of gart BO at resume/suspend and
    instead pin only once and try to recover gart content
    at resume time. This is much more stable in case there
    is OOM situation at 2nd call to amdgpu_device_evict_resources()
    while evicting GART table.
    
    v3: remove gart recovery from other places
    v2: pin gart at amdgpu_gart_table_vram_alloc()
    
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Nirmoy Das <nirmoy.das@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ec6aae9711a8e5fca24a537b9ae952e38a1ebb71
Author: Nirmoy Das <nirmoy.das@amd.com>
Date:   Fri Jan 7 09:51:14 2022 +0100

    drm/amdgpu: do not pass ttm_resource_manager to vram_mgr
    
    Do not allow exported amdgpu_vram_mgr_*() to accept
    any ttm_resource_manager pointer. Also there is no need
    to force other module to call a ttm function just to
    eventually call vram_mgr functions.
    
    v2: pass adev's vram_mgr instead of adev
    
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Nirmoy Das <nirmoy.das@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit ffb378fb3069520da3c2be3c1269250ec9c028ab
Author: Nirmoy Das <nirmoy.das@amd.com>
Date:   Fri Jan 7 09:51:13 2022 +0100

    drm/amdkfd: remove unused function
    
    Remove unused amdgpu_amdkfd_get_vram_usage()
    
    CC: Felix.Kuehling@amd.com
    
    Signed-off-by: Nirmoy Das <nirmoy.das@amd.com>
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Fixes: dfcbe6d5f4a340 ("drm/amdgpu: Remove unused function pointers")

commit 1dd8b1b987fad93b647cb0fa5289d69b4c889dc2
Author: Nirmoy Das <nirmoy.das@amd.com>
Date:   Fri Jan 7 17:42:28 2022 -0500

    drm/amdgpu: do not pass ttm_resource_manager to gtt_mgr
    
    Do not allow exported amdgpu_gtt_mgr_*() to accept
    any ttm_resource_manager pointer. Also there is no need
    to force other module to call a ttm function just to
    eventually call gtt_mgr functions.
    
    v4: remove unused adev.
    v3: upcast mgr from ttm resopurce manager instead of
    getting it from adev.
    v2: pass adev's gtt_mgr instead of adev.
    
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Signed-off-by: Nirmoy Das <nirmoy.das@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 62d5f9f7110ad374db67ab4820f4ff2d916c3cdb
Author: Leslie Shi <Yuliang.Shi@amd.com>
Date:   Wed Jan 5 10:57:20 2022 +0800

    drm/amdgpu: Unmap MMIO mappings when device is not unplugged
    
    Patch: 3efb17ae7e92 ("drm/amdgpu: Call amdgpu_device_unmap_mmio() if device
    is unplugged to prevent crash in GPU initialization failure") makes call to
    amdgpu_device_unmap_mmio() conditioned on device unplugged. This patch unmaps
    MMIO mappings even when device is not unplugged.
    
    v2: Add condition of drm_dev_enter() to deleted unmaps in patch
    "drm/amdgpu: Unmap all MMIO mappings"
    
    Signed-off-by: Leslie Shi <Yuliang.Shi@amd.com>
    Reviewed-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 6638391b9f78abaa41f05fe4e0d2ee6f6390c398
Author: Peng Ju Zhou <PengJu.Zhou@amd.com>
Date:   Thu Jan 6 11:52:26 2022 +0800

    drm/amdgpu: Enable second VCN for certain Navy Flounder.
    
    Certain Navy Flounder cards have 2 VCNs, enable it.
    
    Signed-off-by: Peng Ju Zhou <PengJu.Zhou@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Guchun Chen <guchun.chen@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 63ad5371cd1e379519395c49a4b6a652c36c98e5
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Wed Jan 5 12:48:16 2022 -0600

    drm/amd/display: explicitly set is_dsc_supported to false before use
    
    When UBSAN is enabled a case is shown on unplugging the display that
    this variable hasn't been initialized by `update_dsc_caps`, presumably
    when the display was unplugged it wasn't copied from the DPCD.
    
    Link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956497
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Acked-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit b54ce6c92cf57ff276e4539750c140c9c96416f3
Author: Jiawei Gu <Jiawei.Gu@amd.com>
Date:   Thu Jan 6 17:07:05 2022 +0800

    drm/amdgpu: Clear garbage data in err_data before usage
    
    Memory of err_data should be cleaned before usage
    when there're multiple entry in ras ih.
    Otherwise garbage data from last loop will be used.
    
    Signed-off-by: Jiawei Gu <Jiawei.Gu@amd.com>
    Reviewed-by: Tao Zhou <tao.zhou1@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 4aa1b8257fba5931511a7e152bcbbb3dd673c6c1
Merge: c288ea679840d fbb3485f1f931
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:41:13 2022 -0800

    Merge branch 'pcmcia-next' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/linux
    
    Pull pcmcia updates from Dominik Brodowski:
     "A number of odd cleanups and fixes, including one for a small race in
      the handling of the pccardd kernel thread"
    
    * 'pcmcia-next' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/linux:
      pcmcia: fix setting of kthread task states
      MAINTAINERS: update PCMCIA tree
      pcmcia: use sysfs_emit{,_at} for sysfs output
      pcmcia: make pcmcia_release_io() void, as no-one is interested in return value
      pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in nonstatic_find_mem_region()
      pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in __nonstatic_find_io_region()
      pcmcia: comment out unused exca_readw() function
      pcmcia: Make use of the helper macro SET_NOIRQ_SYSTEM_SLEEP_PM_OPS()
      pcmcia: clean up dead drivers for CompuLab CM-X255/CM-X270 boards

commit 8cd778650ae223cd306588042b55d0290ef81037
Author: Kelvin Cao <kelvin.cao@microchip.com>
Date:   Thu Dec 23 17:23:34 2021 -0800

    ntb_hw_switchtec: Fix a minor issue in config_req_id_table()
    
    The req_id_table_size field is 16-bit wide, use ioread16() to read the
    value.
    
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 1d3cfc2835c1754d19a743dc346a9e58cf0c07c0
Author: Kelvin Cao <kelvin.cao@microchip.com>
Date:   Thu Dec 23 17:23:33 2021 -0800

    ntb_hw_switchtec: Remove code for disabling ID protection
    
    ID protection is a firmware setting for NT window access control. With
    it enabled, only the posted requests with requester IDs in the requester
    ID table will be allowed to access the NT windows. Otherwise all posted
    requests are allowed. Normally user will configure it statically via the
    Switchtec config file, and it will take effect when the firmware boots
    up. The driver can also toggle the ID protection setting dynamically,
    which will overwrite the static setting in the Switchtec config file as
    a side effect.
    
    Currently, the driver disables the ID protection. However, it's not
    necessary to disable the ID protection at the driver level as the driver
    has already configured the proper requester IDs in the requester ID
    table to allow the corresponding posted requests to hit the NT windows.
    Remove the code that disables the ID protection to make the static
    setting prevail.
    
    Note: ID protection is not applicable to non-posted requests.
    
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 2f58265e163df2dc3f49118bcb38771b66f7e979
Author: Kelvin Cao <kelvin.cao@microchip.com>
Date:   Thu Dec 23 17:23:32 2021 -0800

    ntb_hw_switchtec: Update the way of getting VEP instance ID
    
    Gen4 firmware adds DMA VEP and NVMe VEP support in VEP (virtual EP)
    instance ID register in addtion to management EP. Update the way of
    getting management VEP instance ID.
    
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 857e239c3ef57e6ba0ff148de96e14249a4d669b
Author: Jeremy Pallotta <jmpallotta@gmail.com>
Date:   Thu Dec 23 17:23:31 2021 -0800

    ntb_hw_switchtec: AND with the part_map for a valid tpart_vec
    
    Some firmware versions return 1 in the target partition vector for
    undefined partitions. AND with the part_map to give a valid tpart_vec.
    
    Signed-off-by: Jeremy Pallotta <jmpallotta@gmail.com>
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 7ff351c86b6b258f387502ab2c9b9d04f82c1c3d
Author: Wesley Sheng <wesley.sheng@microchip.com>
Date:   Thu Dec 23 17:23:30 2021 -0800

    ntb_hw_switchtec: Fix bug with more than 32 partitions
    
    Switchtec could support as mush as 48 partitions, but ffs & fls are
    for 32 bit argument, in case of partition index larger than 31, the
    current code could not parse the peer partition index correctly.
    Change to the 64 bit version __ffs64 & fls64 accordingly to fix this
    bug.
    
    Fixes: 3df54c870f52 ("ntb_hw_switchtec: Allow using Switchtec NTB in multi-partition setups")
    Signed-off-by: Wesley Sheng <wesley.sheng@microchip.com>
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 32c3d375b0ed84b6acb51ae5ebef35ff0d649d85
Author: Jeremy Pallotta <jmpallotta@gmail.com>
Date:   Thu Dec 23 17:23:29 2021 -0800

    ntb_hw_switchtec: Fix pff ioread to read into mmio_part_cfg_all
    
    Array mmio_part_cfg_all holds the partition configuration of all
    partitions, with partition number as index. Fix this by reading into
    mmio_part_cfg_all for pff.
    
    Fixes: 0ee28f26f378 ("NTB: switchtec_ntb: Add link management")
    Signed-off-by: Jeremy Pallotta <jmpallotta@gmail.com>
    Signed-off-by: Kelvin Cao <kelvin.cao@microchip.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 78c5335b1aa6a2ba60dbad7e5bf10b3ef517c18a
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Wed Dec 22 16:48:02 2021 -0800

    ntb_hw_switchtec: fix the spelling of "its"
    
    Use the possessive "its" instead of the contraction "it's" (it is)
    in user messages.
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Kurt Schwemmer <kurt.schwemmer@microsemi.com>
    Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit e70dc094265c0418bbd895d9657611ac8d509a1c
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Wed Dec 22 09:55:13 2021 +0800

    NTB/msi: Fix ntbm_msi_request_threaded_irq() kernel-doc comment
    
    Add the description of @msi_desc and change the @devname to @name
    in ntbm_msi_request_threaded_irq() kernel-doc comment to remove
    some warnings found by running scripts/kernel-doc, which is caused
    by using 'make W=1'.
    drivers/ntb/msi.c:285: warning: Function parameter or member 'name' not
    described in 'ntbm_msi_request_threaded_irq'
    drivers/ntb/msi.c:285: warning: Function parameter or member 'msi_desc'
    not described in 'ntbm_msi_request_threaded_irq'
    drivers/ntb/msi.c:285: warning: Excess function parameter 'devname'
    description in 'ntbm_msi_request_threaded_irq'
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit 0d5924ec4b89613910366c890305e46821a31f01
Author: Sanjay R Mehta <sanju.mehta@amd.com>
Date:   Fri Dec 17 03:56:20 2021 -0600

    ntb_hw_amd: Add NTB PCI ID for new gen CPU
    
    Add NTB support for new generation of processor
    
    Signed-off-by: Sanjay R Mehta <sanju.mehta@amd.com>
    Signed-off-by: Jon Mason <jdmason@kudzu.us>

commit c288ea679840de4dee2ce6da5d0f139e3774ad86
Merge: 1151e3cd5a737 ffe31c9ed35d7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:31:35 2022 -0800

    Merge tag 'gpio-updates-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
    
    Pull gpio updates from Bartosz Golaszewski:
     "The gpio-sim module is back, this time without any changes to
      configfs. This results in a less elegant user-space interface but I
      never got any follow-up on the committable items and didn't want to
      delay this module for several more months.
    
      Other than that we have support for several new models and some
      support going away. We started working on converting GPIO drivers to
      using fwnode exclusively in order to limit references to OF symbols to
      gpiolib-of.c exclusively. We also have regular tweaks and improvements
      all over the place.
    
      Summary:
    
       - new testing module: gpio-sim that is scheduled to replace
         gpio-mockup
    
       - initial changes aiming at converting all GPIO drivers to using the
         fwnode interface and limiting any references to OF symbols to
         gpiolib-of.c
    
       - add support for Tegra234 and Tegra241 to gpio-tegra186
    
       - add support for new models (SSD201 and SSD202D) to gpio-msc313
    
       - add basic support for interrupts to gpio-aggregator
    
       - add support for AMDIF031 HID device to gpio-amdpt
    
       - drop support for unused platforms in gpio-xlp
    
       - cleanup leftovers from the removal of the legacy Samsung Exynos
         GPIO driver
    
       - use raw spinlocks in gpio-aspeed and gpio-aspeed-sgpio to make
         PREEMPT_RT happy
    
       - generalize the common 'ngpios' device property by reading it in the
         core gpiolib code so that we can remove duplicate reads from
         drivers
    
       - allow line names from device properties to override names set by
         drivers
    
       - code shrink in gpiod_add_lookup_table()
    
       - add new model to the DT bindings for gpio-vf610
    
       - convert DT bindings for tegra devices to YAML
    
       - improvements to interrupt handling in gpio-rcar and gpio-rockchip
    
       - updates to intel drivers from Andy (details in the merge commit)
    
       - some minor tweaks, improvements and coding-style fixes all around
         the subsystem"
    
    * tag 'gpio-updates-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux: (59 commits)
      gpio: rcar: Propagate errors from devm_request_irq()
      gpio: rcar: Use platform_get_irq() to get the interrupt
      gpio: ts5500: Use platform_get_irq() to get the interrupt
      gpio: dwapb: Switch to use fwnode instead of of_node
      gpiolib: acpi: make fwnode take precedence in struct gpio_chip
      dt-bindings: gpio: samsung: drop unused bindings
      gpio: max3191x: Use bitmap_free() to free bitmap
      gpio: regmap: Switch to use fwnode instead of of_node
      gpio: tegra186: Add support for Tegra241
      dt-bindings: gpio: Add Tegra241 support
      gpio: brcmstb: Use local variable to access OF node
      gpio: Remove unused local OF node pointers
      gpio: sim: add missing fwnode_handle_put() in gpio_sim_probe()
      gpio: msc313: Add support for SSD201 and SSD202D
      gpio: msc313: Code clean ups
      dt-bindings: gpio: msc313: Add offsets for ssd20xd
      dt-bindings: gpio: msc313: Add compatible for ssd20xd
      gpio: sim: fix uninitialized ret variable
      gpio: Propagate firmware node from a parent device
      gpio: Setup parent device and get rid of unnecessary of_node assignment
      ...

commit 1151e3cd5a7375ebc839ad3e6c51d87700fe019e
Merge: 1cc8d14c412cf 356f3f2c5756b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:27:04 2022 -0800

    Merge tag 'mmc-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc
    
    Pull MMC updates from Ulf Hansson:
     "MMC core:
       - Use common polling loop for CMD1
       - Add support for DT compatibles for card quirks and use it for ti,wl1251
       - Fixup storing of the OCR mask for MMC_QUIRK_NONSTD_SDIO
    
      MMC host:
       - dw_mmc: Add support for MMC_GEN_CMDs
       - dw_mmc: Fixup calculation of the data timeout
       - dw_mmc-exynos: Add support for the ARTPEC-8 variant
       - jz4740: Add support for bi-directional DMA channels
       - mmci: Add support for eMMC HS200 mode for the stm32 sdmmc variant
       - mmci: Add support for stm32 sdmmc variant revision v2.2
       - mtk-sd: A couple of various minor improvements
       - omap_hsmmc: Drop redundant initialization for the ti,wl1251 chip
       - sdhci-esdhc-imx: Add support for the i.MXRT series variant
       - sdhci-esdhc-imx: Add Haibo Chen as maintainer
       - sdhci-pci: Add support for the Intel ADL variant
       - sdhci-pci-gli: GL975[50]: Add support for the Apple ARM64 variant
       - sdhci-pci-o2micro: Improve support for SDR104/HS200"
    
    * tag 'mmc-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc: (54 commits)
      dt-bindings: mmc: synopsys-dw-mshc: integrate Altera and Imagination
      mmc: pwrseq: Use bitmap_free() to free bitmap
      dt-bindings: mmc: PL18x stop relying on order of dma-names
      dt-bindings: mmc: sdhci-msm: Add compatible string for msm8994
      mmc: au1xmmc: propagate errors from platform_get_irq()
      mmc: sdhci-pci-o2micro: Restore the SD clock's base clock frequency
      mmc: sdhci-pci-o2micro: Improve card input timing at SDR104/HS200 mode
      mmc: mtk-sd: Assign src_clk parent to src_clk_cg for legacy DTs
      mmc: mtk-sd: Fix usage of devm_clk_get_optional()
      mmc: mtk-sd: Take action for no-sdio device-tree parameter
      mmc: mtk-sd: Use BIT() and GENMASK() macros to describe fields
      mmc: mtk-sd: Use readl_poll_timeout instead of open-coded polling
      MAINTAINERS: Add i.MX sdhci maintainer
      mmc: jz4740: Support using a bi-directional DMA channel
      dt-bindings: mmc: ingenic: Support using bi-directional DMA channel
      mmc: dw_mmc: Do not wait for DTO in case of error
      mmc: dw_mmc: Add driver callbacks for data read timeout
      mmc: dw_mmc-exynos: Add support for ARTPEC-8
      dt-bindings: mmc: exynos-dw-mshc: Add support for ARTPEC-8
      mmc: meson-mx-sdio: add IRQ check
      ...

commit 1cc8d14c412cfb6c4eaad4453c557ff289506741
Merge: fa722ecb93c22 ec961cf324115
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:24:20 2022 -0800

    Merge tag 'backlight-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight
    
    Pull backlight updates from Lee Jones:
     "New Functionality:
       - Prepare and add support for ACPI enumeration; lp855x_bl
    
      Fix-ups:
       - Use Regmap API to conduct endianess conversions; qcom-wled
       - Remove superfluous code; qcom-wled
       - Fix formatting issues; qcom-wled
    
      Bug Fixes:
       - Provide error checking/validation of DT supplied strings; qcom-wled
       - Request dynamic amount of values when reading from DT; qcom-wled
       - Fix off-by-one issue when reading from DT; qcom-wled"
    
    * tag 'backlight-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight:
      backlight: qcom-wled: Respect enabled-strings in set_brightness
      backlight: qcom-wled: Remove unnecessary double whitespace
      backlight: qcom-wled: Provide enabled_strings default for WLED 4 and 5
      backlight: qcom-wled: Remove unnecessary 4th default string in WLED3
      backlight: qcom-wled: Override default length with qcom,enabled-strings
      backlight: qcom-wled: Fix off-by-one maximum with default num_strings
      backlight: qcom-wled: Use cpu_to_le16 macro to perform conversion
      backlight: qcom-wled: Pass number of elements to read to read_u32_array
      backlight: qcom-wled: Validate enabled string indices in DT
      backlight: lp855x: Add support ACPI enumeration
      backlight: lp855x: Add dev helper variable to lp855x_probe()
      backlight: lp855x: Move device_config setting out of lp855x_configure()

commit fa722ecb93c22f084c9a9913469a940a8f0e1d5b
Merge: 282aa44c21708 e565615c54869
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:22:06 2022 -0800

    Merge tag 'mfd-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd
    
    Pull MFD updates from Lee Jones:
     "New Device Support:
       - Add support for Lakefield PCH to Intel LPSS PCI
    
      Remove Device Support:
       - Remove support for ROHM BD70528 Power Management IC
    
      New Functionality:
       - Add support for SMBus and I2C mode to Dialog DA9062/61 PMIC
       - Enable I2C4 on Microsoft Surface Go & Go 2
    
      Fix-ups:
       - Device Tree changes (inc. YAML conversion); maxim,max77686,
         rohm,bd9571mwv, syscon, brcm,twd, google,cros-ec
       - Use __maybe_unused instead of #ifery; atmel-flexcom
       - Allow the Regmap API to handle endianess internally; ntxec
       - Utilise I2C's .resume_noirq call-back; atmel-flexcom
       - Remove unused code; ti_am335x_tscadc
       - Use CPU-id instead of ACPI _HRV to ID variants; intel_soc_pmic_core
       - Allow device to power-off right from .probe(); tps65910
       - Trivial (whitespace, typos, etc); da9063
    
      Bug Fixes:
       - Fix ordering issues during probe; intel-lpss-acpi
       - Fix correct clock speed; intel-lpss-pci"
    
    * tag 'mfd-next-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd: (25 commits)
      mfd: google,cros-ec: Fix property name for MediaTek rpmsg
      dt-bindings: mfd: Fix typo "DA9093" -> "DA9063"
      mfd: ntxec: Change return type of ntxec_reg8 from __be16 to u16
      mfd: tps65910: Set PWR_OFF bit during driver probe
      mfd: intel_soc_pmic: Use CPU-id check instead of _HRV check to differentiate variants
      mfd: intel-lpss: Fix I2C4 not being available on the Microsoft Surface Go & Go 2
      dt-bindings: mfd: Add Broadcom's Timer-Watchdog block
      dt-bindings: mfd: Add Freecom system controller
      mfd: Kconfig: Change INTEL_SOC_PMIC_CHTDC_TI to bool
      dt-bindings: mfd: syscon: Add samsung,exynos850-sysreg
      mfd: da9062: Support SMBus and I2C mode
      mfd: intel-lpss-pci: Fix clock speed for 38a8 UART
      mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
      mfd: ti_am335x_tscadc: Drop the CNTRLREG_TSC_8WIRE macro
      mfd: stmpe: Support disabling sub-functions
      mfd: atmel-flexcom: Use .resume_noirq
      mfd: atmel-flexcom: Remove #ifdef CONFIG_PM_SLEEP
      dt-bindings: mfd: bd9571mwv: Convert to json-schema
      mfd: intel-lpss: Add Intel Lakefield PCH PCI IDs
      dt-bindings: mfd: maxim,max77686: Convert to dtschema
      ...

commit 282aa44c21708835517ffaa31c63ab651248cf5e
Merge: fef8dfaea9d6c 19629ae482f18
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:19:47 2022 -0800

    Merge tag 'spi-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
    
    Pull spi updates from Mark Brown:
     "This has mostly been a quiet release for the SPI subsystem, almost all
      cleanups and fixes to existing drivers.
    
      A couple of changes that stand out:
    
       - Cleanups and support for version specific features in the
         DesignWare controller.
    
       - Removal of support for Netlogic devices from the XLP driver, the
         platform had previously been removed by MIPS so the support
         couldn't be used.
    
       - Conversion of several DT bindings to YAML format"
    
    * tag 'spi-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi: (53 commits)
      spi: don't include ptp_clock_kernel.h in spi.h
      spi: spi-meson-spifc: Add missing pm_runtime_disable() in meson_spifc_probe
      spi: atmel: Fix typo
      spi: dt-bindings: mediatek,spi-mtk-nor: Fix example 'interrupts' property
      spi: qcom: geni: handle timeout for gpi mode
      spi: qcom: geni: set the error code for gpi transfer
      spi: spi-mux: Add reference to spi-peripheral-props.yaml schema
      spi: ar934x: fix transfer size
      spi: pxa2xx: Propagate firmware node
      spi: dw: Propagate firmware node
      spi: dln2: Propagate firmware node
      spi: ar934x: fix transfer and word delays
      spi: uniphier: Fix a bug that doesn't point to private data correctly
      spi: spi-mtk-nor: add new clock name 'axi' for spi nor
      spi: atmel,quadspi: Define sama7g5 QSPI
      spi: atmel,quadspi: Convert to json-schema
      spi: Fix incorrect cs_setup delay handling
      dt-bindings: mtd: spi-nor: Add a reference to spi-peripheral-props.yaml
      spi: dt-bindings: cdns,qspi-nor: Move peripheral-specific properties out
      spi: dt-bindings: add schema listing peripheral-specific properties
      ...

commit fef8dfaea9d6c444b6c2174b3a2b0fca4d226c5e
Merge: 2d7852c379408 bfff546aae50a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 12:17:45 2022 -0800

    Merge tag 'regulator-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
    
    Pull regulator updates from Mark Brown:
     "This has been a fairly quiet release for the regulator API, the main
      thing has been the addition of helpers for interrupt handling from
      Matti Vaittinen.
    
      We do also have support for quite a few new devices.
    
      Summary:
    
       - Helpers for trivial interrupt notifications, making it easier for
         drivers to handle error interrupts.
    
       - Support for Dialog DA914x, Maxim MAX2008x, Qualcomm PM8826,
         PMG1100, and PM8450 and TI TPS68470"
    
    * tag 'regulator-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator: (30 commits)
      regulator: Add MAX20086-MAX20089 driver
      dt-bindings: regulators: Add bindings for Maxim MAX20086-MAX20089
      regulator: qcom_smd: Align probe function with rpmh-regulator
      regulator: remove redundant ret variable
      regulator: qcom-labibb: OCP interrupts are not a failure while disabled
      regulator: dt-bindings: samsung,s5m8767: Move fixed string BUCK9 to 'properties'
      regulator: Introduce tps68470-regulator driver
      drivers/regulator: remove redundant ret variable
      regulator: fix bullet lists of regulator_ops comment
      regulator: Fix type of regulator-coupled-max-spread property
      regulator: maxim,max8973: Document interrupts property
      regulator: qcom-rpmh: Add support for PM8450 regulators
      regulator: qcom,rpmh: Add compatible for PM8450
      regulator: da9121: Add DA914x binding info
      regulator: da9121: Remove erroneous compatible from binding
      regulator: da9121: Add DA914x support
      regulator: da9121: Prevent current limit change when enabled
      regulator: qcom-rpmh: Add PMG1110 regulators
      dt-bindings: regulator: Add compatible for pmg1110
      regulator: qcom_spmi: Add pm8226 regulators
      ...

commit bf3c39f5da43499c52d4127b7f2f495b69dfeebf
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Sat Jan 8 13:41:09 2022 +0800

    i2c: sh_mobile: remove unneeded semicolon
    
    Eliminate the following coccicheck warning:
    ./drivers/i2c/busses/i2c-sh_mobile.c:849:3-4: Unneeded semicolon
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
    Signed-off-by: Wolfram Sang <wsa@kernel.org>

commit 2d7852c3794085920e50e69bd050881d605bd44d
Merge: c01d85c2190bf b56a7cbf40c89
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:48:51 2022 -0800

    Merge tag 'regmap-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap
    
    Pull regmap updates from Mark Brown:
     "A very quiet release for regmap:
    
       - Allow a custom _update_bits() operation for devices with no bus.
    
       - Fix an issue with creation of the debugfs directory when attaching
         a device to an existing no device regmap.
    
       - A trivial formatting fix"
    
    [ The custom _update_bits comit came in earlier through the networking
      tree that had merged it for its own needs ]
    
    * tag 'regmap-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap:
      regmap: debugfs: Fix indentation
      regmap: Call regmap_debugfs_exit() prior to _init()

commit c01d85c2190bf694ccd041e7d19c36eacf005840
Merge: 347708875a2fa 9ce47e43a0f08
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:35:28 2022 -0800

    Merge tag 'mtd/for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux
    
    Pull MTD updates from Miquel Raynal:
     "MTD core changes:
    
       - mtdchar: Prevent unbounded allocation in MEMWRITE ioctl
    
       - gen_probe: Use bitmap_zalloc() when applicable
    
       - Introduce an expert mode for forensics and debugging purposes
    
       - Clear out unregistered devices a bit more
    
       - Provide unique name for nvmem device
    
       - Remove unused header file <linux/mtd/latch-addr-flash.h>
    
       - Fixed breaking list in __mtd_del_partition.
    
      MTD device changes:
    
       - Warn about failure to unregister mtd device in sst25l, mchp48l640,
         mchp23k256, and dataflash drivers.
    
      Raw NAND core changes:
    
       - Export nand_read_page_hwecc_oob_first()
    
      GPMC memory controller for OMAP2 NAND controller changes:
    
       - Add support for AM64 SoC and allow build on K3 platforms
    
       - Use a compatible match table when checking for NAND controller
    
       - Use platform_get_irq() to get the interrupt
    
      Raw NAND controller changes:
    
       - OMAP2 NAND controller:
          - Document the missing 'rb-gpios' DT property
          - Drop unused variable
          - Fix force_8bit flag behaviour for DMA mode
          - Move to exec_op interface
          - Use platform_get_irq() to get the interrupt
    
       - Renesas:
          - Add new NAND controller driver with its bindings and MAINTAINERS entry
    
       - Onenand:
          - Remove redundant variable ooblen
    
       - MPC5121:
          - Remove unused variable in ads5121_select_chip()
    
       - GPMI:
          - Add ERR007117 protection for nfc_apply_timings
          - Remove explicit default gpmi clock setting for i.MX6
          - Use platform_get_irq_byname() to get the interrupt
          - Remove unneeded variable
    
       - Ingenic:
          - JZ4740 needs 'oob_first' read page function
    
       - Davinci:
          - Rewrite function description
          - Avoid duplicated page read
          - Don't calculate ECC when reading page
    
      SPI NOR core changes:
    
       - Add Pratyush as SPI NOR co-maintainer.
    
       - Flash parameters initialization was done in a spaghetti way. Clean
         flash parameters initialization.
    
       - Rework the flash_info flags and clarify where one should be used.
    
       - Initialize all flash parameters based on JESD216 SFDP where
         possible. Flash parameters and settings that are SFDP discoverable
         should not be duplicated via flash_info flags at flash declaration.
    
       - Remove debugfs entries that duplicate sysfs entries.
    
      SPI NOR manufacturer driver changes:
    
       - Use late_init() hook in various drivers to make it clear that those
         flash parameters are either not declared in the JESD216 SFDP
         standard, or the SFDP tables which define those flash parameters
         are not defined by the flash.
    
       - Fix mtd size for s3an flashes.
    
       - Write 2 bytes when disabling Octal DTR mode: 1 byte long
         transactions are not allowed in 8D-8D-8D mode.
    
      Hyperbus changes:
    
       - Couple of fixes in Renesas hyperbus rpc-if driver to avoid crash on
         module remove and for missing check for error value in probe"
    
    * tag 'mtd/for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux: (71 commits)
      mtd: spi-nor: Remove debugfs entries that duplicate sysfs entries
      mtd: spi-nor: micron-st: write 2 bytes when disabling Octal DTR mode
      mtd: spi-nor: spansion: write 2 bytes when disabling Octal DTR mode
      mtd: spi-nor: core: use 2 data bytes for template ops
      mtd: spi-nor: Constify part specific fixup hooks
      mtd: spi-nor: core: Remove reference to spi-nor.c
      mtd: rawnand: gpmi: Use platform_get_irq_byname() to get the interrupt
      mtd: rawnand: omap_elm: Use platform_get_irq() to get the interrupt
      mtd: rawnand: omap2: Select GPMC device driver for ARCH_K3
      memory: omap-gpmc: Use a compatible match table when checking for NAND controller
      memory: omap-gpmc: Add support for GPMC on AM64 SoC
      dt-bindings: memory-controllers: ti,gpmc: Add compatible for AM64
      memory: omap-gpmc: Use platform_get_irq() to get the interrupt
      MAINTAINERS: Add an entry for Renesas NAND controller
      mtd: rawnand: renesas: Add new NAND controller driver
      dt-bindings: mtd: renesas: Describe Renesas R-Car Gen3 & RZ/N1 NAND controller
      mtd: rawnand: gpmi: remove unneeded variable
      mtd: rawnand: omap2: drop unused variable
      mtd: rawnand: omap2: fix force_8bit flag behaviour for DMA mode
      mtd: rawnand: omap2: Add compatible for AM64 SoC
      ...

commit 347708875a2fac81dd99ec826248ec29ac28f441
Merge: 46a67e7648848 3367d1bd738c0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:26:57 2022 -0800

    Merge tag 'platform-drivers-x86-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86
    
    Pull x86 platform driver updates from Hans de Goede:
     "Highlights:
    
      New drivers:
       - asus-tf103c-dock
       - intel_crystal_cove_charger
       - lenovo-yogabook-wmi
       - simatic-ipc platform-code + led driver + watchdog driver
       - x86-android-tablets (kernel module to workaround DSDT bugs on
         these)
    
      amd-pmc:
       - bug-fixes
       - smar trace buffer support
    
      asus-wmi:
       - support for custom fan curves
    
      int3472 (camera info ACPI object for Intel IPU3/SkyCam cameras):
       - ACPI core + int3472 changes to delay enumeration of camera sensor
         I2C clients until the PMIC for the sensor has been fully probed
       - Add support for board data (DSDT info is incomplete) for setting up
         the tps68470 PMIC used on some boards with these cameras
       - Add board data for the Microsoft Surface Go (original, v2 and v3)
    
      thinkpad_acpi:
       - various cleanups
       - support for forced battery discharging (for battery calibration)
       - support to inhibit battery charging
       - this includes power_supply core changes to add new APIs for this
    
      think_lmi:
       - enhanced BIOS password support
    
      various other small fixes and hardware-id additions"
    
    * tag 'platform-drivers-x86-v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86: (78 commits)
      power: supply: Provide stubs for charge_behaviour helpers
      platform/x86: x86-android-tablets: Fix GPIO lookup leak on error-exit
      platform/x86: int3472: Add board data for Surface Go 3
      platform/x86: Add Asus TF103C dock driver
      platform/x86: x86-android-tablets: Add TM800A550L data
      platform/x86: x86-android-tablets: Add Asus MeMO Pad 7 ME176C data
      platform/x86: x86-android-tablets: Add Asus TF103C data
      platform/x86: x86-android-tablets: Add support for preloading modules
      platform/x86: x86-android-tablets: Add support for registering GPIO lookup tables
      platform/x86: x86-android-tablets: Add support for instantiating serdevs
      platform/x86: x86-android-tablets: Add support for instantiating platform-devs
      platform/x86: x86-android-tablets: Add support for PMIC interrupts
      platform/x86: x86-android-tablets: Don't return -EPROBE_DEFER from a non probe() function
      platform/x86: touchscreen_dmi: Remove the Glavey TM800A550L entry
      platform/x86: touchscreen_dmi: Enable pen support on the Chuwi Hi10 Plus and Pro
      platform/x86: touchscreen_dmi: Correct min/max values for Chuwi Hi10 Pro (CWI529) tablet
      platform/x86: Add intel_crystal_cove_charger driver
      power: supply: fix charge_behaviour attribute initialization
      platform/x86: intel-uncore-frequency: use default_groups in kobj_type
      x86/platform/uv: use default_groups in kobj_type
      ...

commit 46a67e764884878b61007c9cea40295d02a24fe1
Merge: 039053c11965a a1ee1c08fcd5a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:23:25 2022 -0800

    Merge tag 'hsi-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi
    
    Pull HSI update from Sebastian Reichel:
    
     - avoid returning free'd object in hsi_new_client error path
    
    * tag 'hsi-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi:
      HSI: core: Fix return freed object in hsi_new_client

commit 039053c11965a33250e75009e37dab8e7580fa4e
Merge: 7db48b6b4a03c 25fd330370ac4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:20:27 2022 -0800

    Merge tag 'for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply
    
    Pull power supply and reset updates from Sebastian Reichel:
     "Power-supply core:
    
       - introduce "No Battery" health status
    
       - use library interpolation
    
       - add power_supply_battery_info documentation
    
       - migrate power_supply_battery_info to be fully heap allocated making
         it more obvious that it needs to be free'd manually
    
      Drivers:
    
       - max77976-charger: new driver
    
       - qcom-smbb: add pm8226 charger support
    
       - bq25890-charger: support battery temperature readings
    
       - ab8500: continue migrating towards using standard core APIs"
    
    * tag 'for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply: (28 commits)
      power: supply_core: Pass pointer to battery info
      power: supply: ab8500: Fix the error handling path of ab8500_charger_probe()
      power: reset: mt6397: Check for null res pointer
      power: bq25890: add POWER_SUPPLY_PROP_TEMP
      power: supply: qcom_smbb: support pm8226
      dt-bindings: power: supply: pm8941-charger: add pm8226
      power: supply: ab8500: Standardize capacity lookup
      power: supply: ab8500: Standardize temp res lookup
      power: supply: ab8500: Standardize CV voltage
      power: supply: ab8500: Standardize CC current
      power: supply: ab8500: Make recharge capacity a constant
      power: supply: ab8500: Standardize termination current
      power: supply: ab8500: Standardize internal resistance
      power: supply: ab8500_fg: Init battery data in bind()
      power: supply: ab8500: Standardize voltages
      power: supply: ab8500: Standardize technology
      power: supply: ab8500: Standardize design capacity
      power: supply: ab8500: Use only one battery type
      power: supply: ab8500: Drop unused battery types
      power: supply: ab8500: Standardize operating temperature
      ...

commit 7db48b6b4a03c067159a1dbd8f917453ae3154cb
Merge: 26b88fba2ad9b 081c8919b02bc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 11:12:57 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial
    
    Pull trivial tree removal from Jiri Kosina:
     "Remove any mentions of trivial tree from the documentation and
      MAINTAINERS.
    
      This has been discussed on ksummit-discuss@ some time ago (link is
      provided in the commit message, together with the reasoning). It's a
      general agreement that reason for such a tree to exist is currently
      pretty much non-existent"
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial:
      Documentation: remove trivial tree

commit 26b88fba2ad9b573b8433926294fe48fbf815deb
Merge: 4a110907a1183 cd598d21294e0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 10:53:57 2022 -0800

    Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid
    
    Pull HID updates from Jiri Kosina:
     "Highlights:
    
       - support for USI style pens (Tero Kristo, Mika Westerberg)
    
       - quirk for devices that need inverted X/Y axes (Alistair Francis)
    
       - small core code cleanups and deduplication (Benjamin Tissoires)
    
       - Apple Magic Keyboard support improvements (José Expósito, Alex
         Henrie, Benjamin Berg)
    
       - locking performance improvement for hidraw code (André Almeida)
    
       - PM wakeup support for i2c-hid driver (Matthias Kaehlcke
    
       - new driver to support for LetSketch device (Hans de Goede)
    
       - proper batter reporting for hid-magicmouse USB-connected devices
         (José Expósito)"
    
    * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid: (32 commits)
      HID: magicmouse: Fix an error handling path in magicmouse_probe()
      HID: address kernel-doc warnings
      HID: intel-ish-hid: ishtp-fw-loader: Fix a kernel-doc formatting issue
      HID: intel-ish-hid: ipc: Specify no cache snooping on TGL and ADL
      HID: hid-uclogic-params: Invalid parameter check in uclogic_params_frame_init_v1_buttonpad
      HID: hid-uclogic-params: Invalid parameter check in uclogic_params_huion_init
      HID: hid-uclogic-params: Invalid parameter check in uclogic_params_get_str_desc
      HID: hid-uclogic-params: Invalid parameter check in uclogic_params_init
      HID: Add new Letsketch tablet driver
      HID: apple: Add Magic Keyboard 2021 with fingerprint reader FN key mapping
      HID: apple: Add 2021 magic keyboard FN key mapping
      HID: magicmouse: set Magic Trackpad 2021 name
      HID: magicmouse: set device name when it has been personalized
      HID: apple: Add 2021 Magic Keyboard with number pad
      HID: apple: Add 2021 Magic Keyboard with fingerprint reader
      HID: i2c-hid-of: Expose the touchscreen-inverted properties
      HID: quirks: Allow inverting the absolute X/Y values
      HID: hidraw: Replace hidraw device table mutex with a rwsem
      HID: thrustmaster use swap() to make code cleaner
      HID: debug: Add USI usages
      ...

commit b579dfe71a6a5c3967ca9ad648673b6ca10ab0d5
Author: Anup Patel <anup@brainfault.org>
Date:   Wed Jun 9 17:43:22 2021 +0530

    RISC-V: Use SBI SRST extension when available
    
    The SBI SRST extension provides a standard way to poweroff and
    reboot the system irrespective to whether Linux RISC-V S-mode
    is running natively (HS-mode) or inside Guest/VM (VS-mode).
    
    The SBI SRST extension is available in the SBI v0.3 specification.
    (Refer, https://github.com/riscv/riscv-sbi-doc/releases/tag/v0.3.0-rc1)
    
    This patch extends Linux RISC-V SBI implementation to detect
    and use SBI SRST extension.
    
    Signed-off-by: Anup Patel <anup.patel@wdc.com>
    Reviewed-by: Atish Patra <atish.patra@wdc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 4a110907a118346cfafc3aa3a75a632fac11b7a9
Merge: 5c947d0dbae80 00f5117c5f785
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 10:25:36 2022 -0800

    Merge tag 'hwmon-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging
    
    Pull hwmon updates from Guenter Roeck:
     "New drivers:
    
       - PMBus driver for MPS Multi-phase mp5023
    
       - PMBus driver for Delta AHE-50DC fan control module
    
       - Driver for NZXT RGB&Fan Controller/Smart Device v2
    
       - Driver for Texas Instruments INA238
    
       - Driver to support X370 Asus WMI
    
       - Driver to support B550 Asus WMI
    
      Other notable changes:
    
       - Cleanup of ntc_thermistor driver, and added support for Samsung
         1404-001221 NTC
    
       - Improve detection of LM84, MAX1617, and MAX1617A in adm1021 driver
    
       - Clean up tmp401 driver, and convert to with_info API
    
       - Add support for regulators and IR38060, IR38164 IR38263 to ir38064
         PMBus driver
    
       - Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh to
         k10temp driver
    
       - Add support for F81966 to f71882fg driver
    
       - Add support for ONSEMI N34TS04 to jc42 driver
    
       - Clean up and simplify dell-smm driver
    
       - Add support for ROG STRIX B550-A/X570-I GAMING to nct6775 driver
    
      And various other minor improvements and fixes"
    
    * tag 'hwmon-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: (49 commits)
      hwmon: (nzxt-smart2) make array detect_fans_report static const
      hwmon: (xgene-hwmon) Add free before exiting xgene_hwmon_probe
      hwmon: (nzxt-smart2) Fix "unused function" warning
      hwmon: (dell-smm) Pack the whole smm_regs struct
      hwmon: (nct6775) Additional check for ChipID before ASUS WMI usage
      hwmon: (mr75203) fix wrong power-up delay value
      hwmon/pmbus: (ir38064) Fix spelling mistake "comaptible" -> "compatible"
      hwmon/pmbus: (ir38064) Expose a regulator
      hwmon/pmbus: (ir38064) Add of_match_table
      hwmon/pmbus: (ir38064) Add support for IR38060, IR38164 IR38263
      hwmon: add driver for NZXT RGB&Fan Controller/Smart Device v2.
      hwmon: (nct6775) add ROG STRIX B550-A/X570-I GAMING
      hwmon: (pmbus) Add support for MPS Multi-phase mp5023
      dt-bindings: add Delta AHE-50DC fan control module
      hwmon: (pmbus) Add Delta AHE-50DC fan control module driver
      hwmon: prefix kernel-doc comments for structs with struct
      hwmon: (ntc_thermistor) Add Samsung 1404-001221 NTC
      hwmon: (ntc_thermistor) Drop OF dependency
      hwmon: (dell-smm) Unify i8k_ioctl() and i8k_ioctl_unlocked()
      hwmon: (dell-smm) Simplify ioctl handler
      ...

commit 5c947d0dbae8038ec1c8b538891f6475350542ee
Merge: 6f38be8f2ccd9 5f21d7d283dd8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 10:21:35 2022 -0800

    Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6
    
    Pull crypto updates from Herbert Xu:
     "Algorithms:
    
       - Drop alignment requirement for data in aesni
    
       - Use synchronous seeding from the /dev/random in DRBG
    
       - Reseed nopr DRBGs every 5 minutes from /dev/random
    
       - Add KDF algorithms currently used by security/DH
    
       - Fix lack of entropy on some AMD CPUs with jitter RNG
    
      Drivers:
    
       - Add support for the D1 variant in sun8i-ce
    
       - Add SEV_INIT_EX support in ccp
    
       - PFVF support for GEN4 host driver in qat
    
       - Compression support for GEN4 devices in qat
    
       - Add cn10k random number generator support"
    
    * 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6: (145 commits)
      crypto: af_alg - rewrite NULL pointer check
      lib/mpi: Add the return value check of kcalloc()
      crypto: qat - fix definition of ring reset results
      crypto: hisilicon - cleanup warning in qm_get_qos_value()
      crypto: kdf - select SHA-256 required for self-test
      crypto: x86/aesni - don't require alignment of data
      crypto: ccp - remove unneeded semicolon
      crypto: stm32/crc32 - Fix kernel BUG triggered in probe()
      crypto: s390/sha512 - Use macros instead of direct IV numbers
      crypto: sparc/sha - remove duplicate hash init function
      crypto: powerpc/sha - remove duplicate hash init function
      crypto: mips/sha - remove duplicate hash init function
      crypto: sha256 - remove duplicate generic hash init function
      crypto: jitter - add oversampling of noise source
      MAINTAINERS: update SEC2 driver maintainers list
      crypto: ux500 - Use platform_get_irq() to get the interrupt
      crypto: hisilicon/qm - disable qm clock-gating
      crypto: omap-aes - Fix broken pm_runtime_and_get() usage
      MAINTAINERS: update caam crypto driver maintainers list
      crypto: octeontx2 - prevent underflow in get_cores_bmap()
      ...

commit 6f38be8f2ccd9babf04b9b23539108542a59fcb8
Merge: 1be5bdf8cd5a1 87d6576ddf8ac
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 10:00:04 2022 -0800

    Merge tag 'docs-5.17' of git://git.lwn.net/linux
    
    Pull documentation updates from Jonathan Corbet:
     "This isn't a hugely busy cycle for documentation, but a few
      significant things still showed up:
    
       - A documentation section for ARC processors
    
       - Reworked and enhanced KUnit documentation
    
       - The ability to pick your own theme for HTML builds; if the default
         "Read the Docs" theme isn't ugly enough for you, you can now pick
         an uglier one.
    
       - More Chinese translation work
    
      Plus the usual assortment of fixes and cleanups"
    
    * tag 'docs-5.17' of git://git.lwn.net/linux: (53 commits)
      scripts: sphinx-pre-install: Fix ctex support on Debian
      docs: discourage use of list tables
      docs: 5.Posting.rst: describe Fixes: and Link: tags
      Documentation: kgdb: Replace deprecated remotebaud
      docs: automarkup.py: Fix invalid HTML link output and broken URI fragments
      Documentation: refer to config RANDOMIZE_BASE for kernel address-space randomization
      Documentation: kgdb: properly capitalize the MAGIC_SYSRQ config
      docs/zh_CN: Update and fix a couple of typos
      scripts: sphinx-pre-install: add required ctex dependency
      Documentation: KUnit: Restyled Frequently Asked Questions
      Documentation: KUnit: Restyle Test Style and Nomenclature page
      Documentation: KUnit: Rework writing page to focus on writing tests
      Documentation: kunit: Reorganize documentation related to running tests
      Documentation: KUnit: Added KUnit Architecture
      Documentation: KUnit: Rewrite getting started
      Documentation: KUnit: Rewrite main page
      docs/zh_CN: Add zh_CN/accounting/delay-accounting.rst
      Documentation/sphinx: fix typos of "its"
      docs/zh_CN: Add sched-domains translation
      doc: fs: remove bdev_try_to_free_page related doc
      ...

commit 653c3d33893e34e7822b78de6377cbca26231edd
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:56 2022 +0100

    dt-bindings: clock: samsung: convert S5Pv210 to dtschema
    
    Convert Samsung S5Pv210 SoC clock controller bindings to DT schema
    format.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-8-krzysztof.kozlowski@canonical.com

commit cc190b1f5ac071b12c31052750f1856bd673b980
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:55 2022 +0100

    dt-bindings: clock: samsung: convert Exynos5410 to dtschema
    
    Convert Samsung Exynos5410 SoC clock controller bindings to DT schema
    format.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-7-krzysztof.kozlowski@canonical.com

commit 2ae8dab876faf6a069d2dff4dd3e9d38d34779f3
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:54 2022 +0100

    dt-bindings: clock: samsung: convert Exynos5260 to dtschema
    
    Convert Samsung Exynos5260 SoC clock controller bindings to DT schema
    format.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-6-krzysztof.kozlowski@canonical.com

commit c47db13bdf66b32bf2da8e561c13cc1253268b16
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:53 2022 +0100

    dt-bindings: clock: samsung: extend Exynos7 bindings with UFS
    
    The UFS for Exynos7 SoC clock controller requires additional input
    clocks for the FSYS1 clock controller.  Update the bindings to reflect
    this, at least in theory.  In practice, these input clocks are ignored,
    so it is rather adjusting of bindings to existing DTS, without affecting
    any real users.  I understand that is not how it should be done,
    though...
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-5-krzysztof.kozlowski@canonical.com

commit 5de80c3b57eb4a44c1bccf17070c3a62f07bd7df
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:52 2022 +0100

    dt-bindings: clock: samsung: convert Exynos7 to dtschema
    
    Convert Samsung Exynos7 SoC clock controller bindings to DT schema
    format.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-4-krzysztof.kozlowski@canonical.com

commit 23652cf52d664b54bb7e7dbb1327966683d6ed7f
Author: Krzysztof Kozlowski <krzk@kernel.org>
Date:   Sun Jan 2 12:53:51 2022 +0100

    dt-bindings: clock: samsung: convert Exynos5433 to dtschema
    
    Convert Samsung Exynos5433 SoC clock controller bindings to DT schema
    format.
    
    Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Acked-by: Stephen Boyd <sboyd@kernel.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220102115356.75796-3-krzysztof.kozlowski@canonical.com

commit 66bdc2bfdfa5ca8c69a9fe169a23e1c698d26f08
Author: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Date:   Thu Dec 30 13:33:54 2021 +0100

    dt-bindings: i2c: maxim,max96712: Add bindings for Maxim Integrated MAX96712
    
    Add bindings for Maxim Integrated MAX96712 deserializer. The MAX96712
    deserializer converts GMSL2 or GMSL1 serial inputs into MIPI CSI-2 D-PHY
    or C-PHY formatted outputs.
    
    Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
    Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20211230123354.623876-1-niklas.soderlund+renesas@ragnatech.se

commit 960616d57eecccb943e76735fbca1790fa0ce31d
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:20:26 2022 -0600

    dt-bindings: iio: adi,ltc2983: Fix 64-bit property sizes
    
    The '/bits/ 64' notation applies the next <> list of values. Another <> list
    is encoded as 32-bits by default. IOW, each <> list needs to be preceeded
    with '/bits/ 64'.
    
    While the dts format allows this, as a rule we don't mix sizes for DT
    properties since all size information is lost in the dtb file.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Nuno Sá <nuno.sa@analog.com>
    Link: https://lore.kernel.org/r/20220107032026.2408196-1-robh@kernel.org

commit f19638bbd0291e600523e0ea1e868a386d304840
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:04:33 2022 -0600

    dt-bindings: power: maxim,max17040: Fix incorrect type for 'maxim,rcomp'
    
    The 'maxim,rcomp' is defined as a uint32, but the description and users all
    say it is uint8-array with 1 or 2 elements. The tools missed checking this
    case.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Link: https://lore.kernel.org/r/20220107030433.2381616-1-robh@kernel.org

commit e3a3356d1745befbe62b9f0ada1a38f10a54ff2a
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:13 2022 -0600

    dt-bindings: interrupt-controller: arm,gic-v3: Fix 'interrupts' cell size in example
    
    The 2nd example has an interrupts cells size of 4, but the 'interrupts'
    property has 3 cells. The example should also be separate since the cell
    size differs in each example.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Marc Zyngier <maz@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-5-robh@kernel.org

commit 7b5bfc00e8035fe0369e8944693292cc21f9a41f
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:12 2022 -0600

    dt-bindings: iio/magnetometer: yamaha,yas530: Fix invalid 'interrupts' in example
    
    'interrupts' does not take a phandle, so remove it in the example.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-4-robh@kernel.org

commit 9cc9b193d595da2df78853318106a181a3f8c627
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:09 2022 -0600

    dt-bindings: clock: imx5: Drop clock consumer node from example
    
    The example nodes have different sized interrupt cells which is not valid
    given no interrupt-parent is specified. As provider examples don't need to
    show the consumer side in the first place, just drop the consumer node.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Stephen Boyd <sboyd@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-1-robh@kernel.org

commit da4b3d88b0862141417f16121f378efffe44240f
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:19:04 2022 -0600

    dt-bindings: Drop required 'interrupt-parent'
    
    'interrupt-parent' is never required as it can be in a parent node or a
    parent node itself can be an interrupt provider. Where exactly it lives is
    outside the scope of a binding schema.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Acked-by: Lee Jones <lee.jones@linaro.org>
    Acked-by: Bartosz Golaszewski <brgl@bgdev.pl>
    Link: https://lore.kernel.org/r/20220107031905.2406176-1-robh@kernel.org

commit 70dfc4177269dc589efef05f128b8d4c61f61056
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:05:13 2022 -0600

    dt-bindings: net: ti,dp83869: Drop value on boolean 'ti,max-output-impedance'
    
    DT booleans don't have a value and 'ti,max-output-impedance' is defined and
    used as a boolean. So drop the bogus value in the example.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220107030513.2385482-1-robh@kernel.org

commit 434a4010de07b6f5f497f9109aae8cb9868abdc9
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:04:17 2022 -0600

    dt-bindings: net: wireless: mt76: Fix 8-bit property sizes
    
    The '/bits/ 8' notation applies the next <> list of values. Another <> list
    is encoded as 32-bits by default. IOW, each <> list needs to be preceeded
    with '/bits/ 8'.
    
    While the dts format allows this, as a rule we don't mix sizes for DT
    properties since all size information is lost in the dtb file.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220107030419.2380198-1-robh@kernel.org

commit 437b168028911c8e622130919e583fb5011bf0a4
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 21:03:57 2022 -0600

    dt-bindings: PCI: snps,dw-pcie-ep: Drop conflicting 'max-functions' schema
    
    'max-functions' is already defined in pci-ep.yaml schema as a uint8 and all
    users of it expect an uint8. Drop the conflicting schema.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220107030358.2378221-1-robh@kernel.org

commit f364d2c622f569a41e513514de4882d5f2f8d986
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:30:36 2022 -0600

    dt-bindings: i2c: st,stm32-i2c: Make each example a separate entry
    
    Each independent example should be a separate entry. This allows for
    'interrupts' to have different cell sizes.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220106183037.1443931-1-robh@kernel.org

commit 8b31766c7ac0d231297afc87bef2191c21d304f0
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:16 2022 -0600

    dt-bindings: net: stm32-dwmac: Make each example a separate entry
    
    Each independent example should be a separate entry. This allows for
    'interrupts' to have different cell sizes.
    
    The first example also has a phandle in 'interrupts', so drop the phandle.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-8-robh@kernel.org

commit b2d28642d1087e8a95205fa2b1d7453c8723a1ea
Author: Rob Herring <robh@kernel.org>
Date:   Wed Jan 5 09:10:09 2022 -0600

    dt-bindings: net: Cleanup MDIO node schemas
    
    The schemas for MDIO bus nodes range from missing to duplicating
    everything in mdio.yaml. The MDIO bus node schemas only need to
    reference mdio.yaml, define any binding specific properties, and define
    'unevaluatedProperties: false'. This ensures that MDIO nodes only
    contain defined properties. With this, any duplicated properties can
    be removed.
    
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: Chen-Yu Tsai <wens@csie.org>
    Cc: Vivien Didelot <vivien.didelot@gmail.com>
    Cc: Florian Fainelli <f.fainelli@gmail.com>
    Cc: Vladimir Oltean <olteanv@gmail.com>
    Cc: Joakim Zhang <qiangqing.zhang@nxp.com>
    Cc: Heiner Kallweit <hkallweit1@gmail.com>
    Cc: Russell King <linux@armlinux.org.uk>
    Cc: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
    Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
    Cc: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
    Cc: "Fernández Rojas" <noltari@gmail.com>
    Cc: John Crispin <john@phrozen.org>
    Cc: "G. Jaya Kumaran" <vineetha.g.jaya.kumaran@intel.com>
    Cc: Linus Walleij <linus.walleij@linaro.org>
    Cc: Joel Stanley <joel@jms.id.au>
    Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
    Cc: Oleksij Rempel <o.rempel@pengutronix.de>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
    Cc: Jose Abreu <joabreu@synopsys.com>
    Cc: netdev@vger.kernel.org
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Link: https://lore.kernel.org/r/20220105151009.3093506-1-robh@kernel.org

commit 343e53754b21ae45530623222aa079fecd3cf942
Author: Christy Lee <christylee@fb.com>
Date:   Fri Jan 7 16:58:54 2022 -0800

    bpf: Fix incorrect integer literal used for marking scratched stack.
    
    env->scratched_stack_slots is a 64-bit value, we should use ULL
    instead of UL literal values.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Christy Lee <christylee@fb.com>
    Acked-by: Song Liu <songliubraving@fb.com>
    Link: https://lore.kernel.org/r/20220108005854.658596-1-christylee@fb.com
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 1be5bdf8cd5a194d981e65687367b0828c839c37
Merge: 1c824bf768d69 b473a3891c463
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:51:26 2022 -0800

    Merge tag 'kcsan.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
    
    Pull KCSAN updates from Paul McKenney:
     "This provides KCSAN fixes and also the ability to take memory barriers
      into account for weakly-ordered systems. This last can increase the
      probability of detecting certain types of data races"
    
    * tag 'kcsan.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu: (29 commits)
      kcsan: Only test clear_bit_unlock_is_negative_byte if arch defines it
      kcsan: Avoid nested contexts reading inconsistent reorder_access
      kcsan: Turn barrier instrumentation into macros
      kcsan: Make barrier tests compatible with lockdep
      kcsan: Support WEAK_MEMORY with Clang where no objtool support exists
      compiler_attributes.h: Add __disable_sanitizer_instrumentation
      objtool, kcsan: Remove memory barrier instrumentation from noinstr
      objtool, kcsan: Add memory barrier instrumentation to whitelist
      sched, kcsan: Enable memory barrier instrumentation
      mm, kcsan: Enable barrier instrumentation
      x86/qspinlock, kcsan: Instrument barrier of pv_queued_spin_unlock()
      x86/barriers, kcsan: Use generic instrumentation for non-smp barriers
      asm-generic/bitops, kcsan: Add instrumentation for barriers
      locking/atomics, kcsan: Add instrumentation for barriers
      locking/barriers, kcsan: Support generic instrumentation
      locking/barriers, kcsan: Add instrumentation for barriers
      kcsan: selftest: Add test case to check memory barrier instrumentation
      kcsan: Ignore GCC 11+ warnings about TSan runtime support
      kcsan: test: Add test cases for memory barrier instrumentation
      kcsan: test: Match reordered or normal accesses
      ...

commit 036a05f50bd777134b1955f400e8d24c0149fef4
Author: Toke Høiland-Jørgensen <toke@redhat.com>
Date:   Fri Jan 7 23:11:15 2022 +0100

    bpf/selftests: Add check for updating XDP bpf_link with wrong program type
    
    Add a check to the xdp_link selftest that the kernel rejects replacing an
    XDP program with a different program type on link update.
    
    v2:
    - Split this out into its own patch.
    
    Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Link: https://lore.kernel.org/r/20220107221115.326171-3-toke@redhat.com
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 4b27480dcaa71e7ee9f56907e419c6a1511fd2b2
Author: Toke Høiland-Jørgensen <toke@redhat.com>
Date:   Fri Jan 7 23:11:14 2022 +0100

    bpf/selftests: convert xdp_link test to ASSERT_* macros
    
    Convert the selftest to use the preferred ASSERT_* macros instead of the
    deprecated CHECK().
    
    v2:
    - Don't add if statements around checks if they weren't there before.
    
    Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Link: https://lore.kernel.org/r/20220107221115.326171-2-toke@redhat.com
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 382778edc8262b7535f00523e9eb22edba1b9816
Author: Toke Høiland-Jørgensen <toke@redhat.com>
Date:   Fri Jan 7 23:11:13 2022 +0100

    xdp: check prog type before updating BPF link
    
    The bpf_xdp_link_update() function didn't check the program type before
    updating the program, which made it possible to install any program type as
    an XDP program, which is obviously not good. Syzbot managed to trigger this
    by swapping in an LWT program on the XDP hook which would crash in a helper
    call.
    
    Fix this by adding a check and bailing out if the types don't match.
    
    Fixes: 026a4c28e1db ("bpf, xdp: Implement LINK_UPDATE for BPF XDP link")
    Reported-by: syzbot+983941aa85af6ded1fd9@syzkaller.appspotmail.com
    Acked-by: Andrii Nakryiko <andrii@kernel.org>
    Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
    Link: https://lore.kernel.org/r/20220107221115.326171-1-toke@redhat.com
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit 1c824bf768d69fce36de748c60c7197a2b838944
Merge: e7d38f16c20bf c438b7d860b4c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:38:03 2022 -0800

    Merge tag 'lkmm.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
    
    Pull memory model documentation updates from Paul McKenney:
     "This series contains documentation and litmus tests for locking,
      courtesy of Boqun Feng"
    
    * tag 'lkmm.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu:
      tools/memory-model: litmus: Add two tests for unlock(A)+lock(B) ordering
      tools/memory-model: doc: Describe the requirement of the litmus-tests directory
      tools/memory-model: Provide extra ordering for unlock+lock pair on the same CPU

commit e7d38f16c20bf2a9b2502bb1d7407360d09a836a
Merge: a229327733b86 f80fe66c38d56
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:29:44 2022 -0800

    Merge tag 'rcu.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu
    
    Pull RCU updates from Paul McKenney:
    
     - Documentation updates, perhaps most notably Neil Brown's writeup of
       the reference-counting analogy to RCU.
    
     - Expedited grace-period cleanups.
    
     - Remove CONFIG_RCU_FAST_NO_HZ due to lack of valid users. I have asked
       around, posted a blog entry, and sent this series to LKML without
       result.
    
     - Miscellaneous fixes.
    
     - RCU callback offloading updates, perhaps most notably Frederic
       Weisbecker's updates allowing CPUs booted in the de-offloaded state
       to be offloaded at runtime.
    
     - nolibc fixes from Willy Tarreau and Anmar Faizi, but also including
       Mark Brown's addition of gettid().
    
     - RCU Tasks Trace fixes, including changes that increase the
       scalability of call_rcu_tasks_trace() for the BPF folks (Martin Lau
       and KP Singh).
    
     - Various fixes including those from Wander Lairson Costa and Li
       Zhijian.
    
     - Fixes plus addition of tests for the increased call_rcu_tasks_trace()
       scalability.
    
    * tag 'rcu.2022.01.09a' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu: (87 commits)
      rcu/nocb: Merge rcu_spawn_cpu_nocb_kthread() and rcu_spawn_one_nocb_kthread()
      rcu/nocb: Allow empty "rcu_nocbs" kernel parameter
      rcu/nocb: Create kthreads on all CPUs if "rcu_nocbs=" or "nohz_full=" are passed
      rcu/nocb: Optimize kthreads and rdp initialization
      rcu/nocb: Prepare nocb_cb_wait() to start with a non-offloaded rdp
      rcu/nocb: Remove rcu_node structure from nocb list when de-offloaded
      rcu-tasks: Use fewer callbacks queues if callback flood ends
      rcu-tasks: Use separate ->percpu_dequeue_lim for callback dequeueing
      rcu-tasks: Use more callback queues if contention encountered
      rcu-tasks: Avoid raw-spinlocked wakeups from call_rcu_tasks_generic()
      rcu-tasks: Count trylocks to estimate call_rcu_tasks() contention
      rcu-tasks: Add rcupdate.rcu_task_enqueue_lim to set initial queueing
      rcu-tasks: Make rcu_barrier_tasks*() handle multiple callback queues
      rcu-tasks: Use workqueues for multiple rcu_tasks_invoke_cbs() invocations
      rcu-tasks: Abstract invocations of callbacks
      rcu-tasks: Abstract checking of callback lists
      rcu-tasks: Add a ->percpu_enqueue_lim to the rcu_tasks structure
      rcu-tasks: Inspect stalled task's trc state in locked state
      rcu-tasks: Use spin_lock_rcu_node() and friends
      rcutorture: Combine n_max_cbs from all kthreads in a callback flood
      ...

commit a229327733b86aa585effdb0d27a87b12aa51597
Merge: e9e64f85b416a d12013c80e152
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:23:59 2022 -0800

    Merge tag 'printk-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux
    
    Pull printk updates from Petr Mladek:
    
     - Remove some twists in the console registration code. It does not
       change the existing behavior except for one corner case. The proper
       default console (with tty binding) will be registered again even when
       it has been removed in the meantime. It is actually a bug fix.
       Anyway, this modified behavior requires some manual interaction.
    
     - Optimize gdb extension for huge ring buffers.
    
     - Do not use atomic operations for a local bitmap variable.
    
     - Update git links in MAINTAINERS.
    
    * tag 'printk-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux:
      MAINTAIERS/printk: Add link to printk git
      MAINTAINERS/vsprintf: Update link to printk git tree
      scripts/gdb: lx-dmesg: read records individually
      printk/console: Clean up boot console handling in register_console()
      printk/console: Remove need_default_console variable
      printk/console: Remove unnecessary need_default_console manipulation
      printk/console: Rename has_preferred_console to need_default_console
      printk/console: Split out code that enables default console
      vsprintf: Use non-atomic bitmap API when applicable

commit e9e64f85b416a276329134cd83ef8ad78b95a118
Merge: ea1ca66d3cc07 2a8ab0fbd110d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:19:29 2022 -0800

    Merge branch 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq
    
    Pull workqueue updates from Tejun Heo:
    
     - The code around workqueue scheduler hooks got reorganized early 2019
       which unfortuately introdued a couple subtle and rare race conditions
       where preemption can mangle internal workqueue state triggering a
       WARN and possibly causing a stall or at least delay in execution.
    
       Frederic fixed both early December and the fixes were sitting in
       for-5.16-fixes which I forgot to push. They are here now. I'll
       forward them to stable after they land.
    
     - The scheduler hook reorganization has more implicatoins for workqueue
       code in that the hooks are now more strictly synchronized and thus
       the interacting operations can become more straight-forward.
    
       Lai is in the process of simplifying workqueue code and this pull
       request contains some of the patches.
    
    * 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq:
      workqueue: Remove the cacheline_aligned for nr_running
      workqueue: Move the code of waking a worker up in unbind_workers()
      workqueue: Remove schedule() in unbind_workers()
      workqueue: Remove outdated comment about exceptional workers in unbind_workers()
      workqueue: Remove the advanced kicking of the idle workers in rebind_workers()
      workqueue: Remove the outdated comment before wq_worker_sleeping()
      workqueue: Fix unbind_workers() VS wq_worker_sleeping() race
      workqueue: Fix unbind_workers() VS wq_worker_running() race
      workqueue: Upgrade queue_work_on() comment

commit ea1ca66d3cc07b00241fcee82328f387359f32f5
Merge: 68514dacf2715 d4296faebd337
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Jan 11 09:14:37 2022 -0800

    Merge branch 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup
    
    Pull cgroup updates from Tejun Heo:
     "Nothing too interesting. The only two noticeable changes are a subtle
      cpuset behavior fix and trace event id field being expanded to u64
      from int. Most others are code cleanups"
    
    * 'for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup:
      cpuset: convert 'allowed' in __cpuset_node_allowed() to be boolean
      cgroup/rstat: check updated_next only for root
      cgroup: rstat: explicitly put loop variant in while
      cgroup: return early if it is already on preloaded list
      cgroup/cpuset: Don't let child cpusets restrict parent in default hierarchy
      cgroup: Trace event cgroup id fields should be u64
      cgroup: fix a typo in comment
      cgroup: get the wrong css for css_alloc() during cgroup_init_subsys()
      cgroup: rstat: Mark benign data race to silence KCSAN

commit 346865f0745357f9f4704614ce1d9a8e6f27dbc4
Author: Longji Guo <guolongji@uniontech.com>
Date:   Fri Dec 3 16:07:58 2021 +0800

    x86/PCI: Remove initialization of static variables to false
    
    Remove the initialization of pci_ignore_seg to false which is pointless.
    
    Link: https://lore.kernel.org/r/20211203080758.962-1-guolongji@uniontech.com
    Signed-off-by: Longji Guo <guolongji@uniontech.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 68514dacf2715d11b91ca50d88de047c086fea9c
Author: Jan Kara <jack@suse.cz>
Date:   Mon Jan 10 19:19:23 2022 +0100

    select: Fix indefinitely sleeping task in poll_schedule_timeout()
    
    A task can end up indefinitely sleeping in do_select() ->
    poll_schedule_timeout() when the following race happens:
    
      TASK1 (thread1)             TASK2                   TASK1 (thread2)
      do_select()
        setup poll_wqueues table
        with 'fd'
                                  write data to 'fd'
                                    pollwake()
                                      table->triggered = 1
                                                          closes 'fd' thread1 is
                                                            waiting for
        poll_schedule_timeout()
          - sees table->triggered
          table->triggered = 0
          return -EINTR
        loop back in do_select()
    
    But at this point when TASK1 loops back, the fdget() in the setup of
    poll_wqueues fails.  So now so we never find 'fd' is ready for reading
    and sleep in poll_schedule_timeout() indefinitely.
    
    Treat an fd that got closed as a fd on which some event happened.  This
    makes sure cannot block indefinitely in do_select().
    
    Another option would be to return -EBADF in this case but that has a
    potential of subtly breaking applications that excercise this behavior
    and it happens to work for them.  So returning fd as active seems like a
    safer choice.
    
    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    CC: stable@vger.kernel.org
    Signed-off-by: Jan Kara <jack@suse.cz>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 4353594eb0980c80e24ebb20d9c871ff95b3b789
Author: Rajat Jain <rajatja@google.com>
Date:   Tue Dec 21 17:21:05 2021 -0800

    PCI: Use DWORD accesses for LTR, L1 SS to avoid erratum
    
    Some devices have an erratum such that they only support DWORD accesses to
    some registers.  E.g., this Bayhub O2 device ([VID:DID] = [0x1217:0x8621])
    only supports DWORD accesses to LTR latency registers and L1 PM substates
    control registers:
    
      https://github.com/rajatxjain/public_shared/blob/main/OZ711LV2_appnote.pdf
    
    The L1 PM substate control registers are DWORD sized, and hence their
    access in the kernel is already DWORD sized, so we don't need to do
    anything for them.
    
    However, the LTR registers being WORD sized, are in need of a solution.
    Convert the WORD sized accesses to these registers into DWORD sized
    accesses while saving and restoring them.
    
    Link: https://lore.kernel.org/r/20211222012105.3438916-1-rajatja@google.com
    Signed-off-by: Rajat Jain <rajatja@google.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 560dbc4654fa013fadcbcd9647904051d6fadc11
Author: Ming Wang <wangming01@loongson.cn>
Date:   Sat Jan 8 17:09:37 2022 +0800

    misc: pci_endpoint_test: Terminate statement with semicolon
    
    Terminate the misc_device->fops assignment statement with a semicolon.
    
    Link: https://lore.kernel.org/r/1641632977-6588-1-git-send-email-wangming01@loongson.cn
    Fixes: 2c156ac71c6b ("misc: Add host side PCI driver for PCI test function device")
    Signed-off-by: Ming Wang <wangming01@loongson.cn>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 10b1a5a99c6ac42be7a490676aec626fba28b048
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 11 10:22:32 2022 +0300

    ALSA: hda: cs35l41: fix double free on error in probe()
    
    If we encounter an error after the kfree(acpi_hw_cfg); then the goto
    err; will result in a double free.
    
    Fixes: 7b2f3eb492da ("ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Link: https://lore.kernel.org/r/20220111072232.GG11243@kili
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 74382e277ae97b4bcfac6f8b61df7a500d392500
Author: Bob Peterson <rpeterso@redhat.com>
Date:   Tue Dec 14 10:40:12 2021 -0500

    gfs2: dump inode object for iopen glocks
    
    Before this patch, glock dumps would not dump the gl_object for iopen
    glocks. This information can help us debug problems related to eviction:
    when AN iopen glock is blocked we can see the status of its underlying
    inode and its flags, etc.
    
    Signed-off-by: Bob Peterson <rpeterso@redhat.com>
    Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

commit ee3fe99ff0a27108ac38d9766ac0e92f5ec35692
Author: Mark Langsdorf <mlangsdo@redhat.com>
Date:   Wed Jan 5 11:47:14 2022 -0600

    ACPI: SPCR: check if table->serial_port.access_width is too wide
    
    If table->serial_port.access_width is more than 29, it causes
    undefined behavior when ACPI_ACCESS_BIT_WIDTH shifts it to
    (1 << ((size) + 2)):
    
    [    0.000000] UBSAN: Undefined behaviour in drivers/acpi/spcr.c:114:11
    [    0.000000] shift exponent 102 is too large for 32-bit type 'int'
    
    Use the new ACPI_ACCESS_ defines to test that serial_port.access_width
    is less than 30 and set it to 6 if it is not.
    
    Signed-off-by: Mark Langsdorf <mlangsdo@redhat.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 69e630016ef4e4a1745310c446f204dc6243e907
Author: Liu Ying <victor.liu@nxp.com>
Date:   Thu Dec 30 12:06:26 2021 +0800

    drm/atomic: Check new_crtc_state->active to determine if CRTC needs disable in self refresh mode
    
    Actual hardware state of CRTC is controlled by the member 'active' in
    struct drm_crtc_state instead of the member 'enable', according to the
    kernel doc of the member 'enable'.  In fact, the drm client modeset
    and atomic helpers are using the member 'active' to do the control.
    
    Referencing the member 'enable' of new_crtc_state, the function
    crtc_needs_disable() may fail to reflect if CRTC needs disable in
    self refresh mode, e.g., when the framebuffer emulation will be blanked
    through the client modeset helper with the next commit, the member
    'enable' of new_crtc_state is still true while the member 'active' is
    false, hence the relevant potential encoder and bridges won't be disabled.
    
    So, let's check new_crtc_state->active to determine if CRTC needs disable
    in self refresh mode instead of new_crtc_state->enable.
    
    Fixes: 1452c25b0e60 ("drm: Add helpers to kick off self refresh mode in drivers")
    Cc: Sean Paul <seanpaul@chromium.org>
    Cc: Rob Clark <robdclark@chromium.org>
    Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
    Cc: Maxime Ripard <mripard@kernel.org>
    Cc: Thomas Zimmermann <tzimmermann@suse.de>
    Cc: David Airlie <airlied@linux.ie>
    Cc: Daniel Vetter <daniel@ffwll.ch>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Liu Ying <victor.liu@nxp.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20211230040626.646807-1-victor.liu@nxp.com

commit 2cea3ec5b0099d0e9dd6752aa86e08bce38d6b32
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Jan 7 11:35:16 2022 +0800

    ACPI: APD: Check for NULL pointer after calling devm_ioremap()
    
    Because devres_alloc() may fail, devm_ioremap() may return NULL.
    
    Then, 'clk_data->base' will be assigned to clkdev->data->base in
    platform_device_register_data().
    
    The PTR_ERR_OR_ZERO() check on clk_data does not cover 'base', so
    it is better to add an explicit check against NULL after updating
    it.
    
    Fixes: 3f4ba94e3615 ("ACPI: APD: Add AMD misc clock handler support")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    [ rjw: Changelog rewrite ]
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 500b55b05d0a21c4adddf4c3b29ee6f32b502046
Author: Bjorn Helgaas <bhelgaas@google.com>
Date:   Tue Dec 21 10:45:07 2021 -0600

    PCI: Work around Intel I210 ROM BAR overlap defect
    
    Per PCIe r5, sec 7.5.1.2.4, a device must not claim accesses to its
    Expansion ROM unless both the Memory Space Enable and the Expansion ROM
    Enable bit are set.  But apparently some Intel I210 NICs don't work
    correctly if the ROM BAR overlaps another BAR, even if the Expansion ROM is
    disabled.
    
    Michael reported that on a Kontron SMARC-sAL28 ARM64 system with U-Boot
    v2021.01-rc3, the ROM BAR overlaps BAR 3, and networking doesn't work at
    all:
    
      BAR 0: 0x40000000 (32-bit, non-prefetchable) [size=1M]
      BAR 3: 0x40200000 (32-bit, non-prefetchable) [size=16K]
      ROM:   0x40200000 (disabled) [size=1M]
    
      NETDEV WATCHDOG: enP2p1s0 (igb): transmit queue 0 timed out
      Hardware name: Kontron SMARC-sAL28 (Single PHY) on SMARC Eval 2.0 carrier (DT)
      igb 0002:01:00.0 enP2p1s0: Reset adapter
    
    Previously, pci_std_update_resource() wrote the assigned ROM address to the
    BAR only when the ROM was enabled.  This meant that the I210 ROM BAR could
    be left with an address assigned by firmware, which might overlap with
    other BARs.
    
    Quirk these I210 devices so pci_std_update_resource() always writes the
    assigned address to the ROM BAR, whether or not the ROM is enabled.
    
    Link: https://lore.kernel.org/r/20211223163754.GA1267351@bhelgaas
    Link: https://lore.kernel.org/r/20201230185317.30915-1-michael@walle.cc
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=211105
    Reported-by: Michael Walle <michael@walle.cc>
    Tested-by: Michael Walle <michael@walle.cc>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit 7f7b4236f2040d19df1ddaf30047128b41e78de7
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Fri Dec 17 15:13:48 2021 +0100

    x86/PCI: Ignore E820 reservations for bridge windows on newer systems
    
    Some BIOS-es contain a bug where they add addresses which map to system
    RAM in the PCI host bridge window returned by the ACPI _CRS method, see
    commit 4dc2287c1805 ("x86: avoid E820 regions when allocating address
    space").
    
    To work around this bug Linux excludes E820 reserved addresses when
    allocating addresses from the PCI host bridge window since 2010.
    
    Recently (2019) some systems have shown-up with E820 reservations which
    cover the entire _CRS returned PCI bridge memory window, causing all
    attempts to assign memory to PCI BARs which have not been setup by the
    BIOS to fail. For example here are the relevant dmesg bits from a
    Lenovo IdeaPad 3 15IIL 81WE:
    
     [mem 0x000000004bc50000-0x00000000cfffffff] reserved
     pci_bus 0000:00: root bus resource [mem 0x65400000-0xbfffffff window]
    
    The ACPI specifications appear to allow this new behavior:
    
    The relationship between E820 and ACPI _CRS is not really very clear.
    ACPI v6.3, sec 15, table 15-374, says AddressRangeReserved means:
    
      This range of addresses is in use or reserved by the system and is
      not to be included in the allocatable memory pool of the operating
      system's memory manager.
    
    and it may be used when:
    
      The address range is in use by a memory-mapped system device.
    
    Furthermore, sec 15.2 says:
    
      Address ranges defined for baseboard memory-mapped I/O devices, such
      as APICs, are returned as reserved.
    
    A PCI host bridge qualifies as a baseboard memory-mapped I/O device,
    and its apertures are in use and certainly should not be included in
    the general allocatable pool, so the fact that some BIOS-es reports
    the PCI aperture as "reserved" in E820 doesn't seem like a BIOS bug.
    
    So it seems that the excluding of E820 reserved addresses is a mistake.
    
    Ideally Linux would fully stop excluding E820 reserved addresses,
    but then the old systems this was added for will regress.
    Instead keep the old behavior for old systems, while ignoring
    the E820 reservations for any systems from now on.
    
    Old systems are defined here as BIOS year < 2018, this was chosen to make
    sure that E820 reservations will not be used on the currently affected
    systems, while at the same time also taking into account that the systems
    for which the E820 checking was originally added may have received BIOS
    updates for quite a while (esp. CVE related ones), giving them a more
    recent BIOS year then 2010.
    
    BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=206459
    BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1868899
    BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1871793
    BugLink: https://bugs.launchpad.net/bugs/1878279
    BugLink: https://bugs.launchpad.net/bugs/1931715
    BugLink: https://bugs.launchpad.net/bugs/1932069
    BugLink: https://bugs.launchpad.net/bugs/1921649
    Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
    Acked-by: Bjorn Helgaas <bhelgaas@google.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit d3115128bdafb62628ab41861a4f06f6d02ac320
Author: Lech Perczak <lech.perczak@gmail.com>
Date:   Mon Jan 10 23:48:44 2022 +0100

    MIPS: ath79: drop _machine_restart again
    
    Commit 81424d0ad0d4 ("MIPS: ath79: Use the reset controller to restart
    OF machines") removed setup of _machine_restart on OF machines to use
    reset handler in reset controller driver.
    While removing remnants of non-OF machines in commit 3a77e0d75eed
    ("MIPS: ath79: drop machfiles"), this was introduced again, making it
    impossible to use additional restart handlers registered through device
    tree. Drop setting _machine_restart altogether, and ath79_restart
    function, which is no longer used after this.
    
    Fixes: 3a77e0d75eed ("MIPS: ath79: drop machfiles")
    Cc: John Crispin <john@phrozen.org>
    Cc: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 879cf8006475642b747aaaa4d06f7044ab2de794
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Tue Jan 11 10:26:58 2022 +0300

    regulator: max20086: fix error code in max20086_parse_regulators_dt()
    
    This code accidentally returns PTR_ERR(NULL) which is success.  It
    should return a negative error code.
    
    Fixes: bfff546aae50 ("regulator: Add MAX20086-MAX20089 driver")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://lore.kernel.org/r/20220111072657.GK11243@kili
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit a64067f4cecaaa4deed8e33d3266bc0bcc189142
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Fri Jan 7 15:47:10 2022 -0600

    ASoC: simple-card: fix probe failure on platform component
    
    A previous change to simple-card resulted in asoc_simple_parse_dai
    attempting to retrieve the dai_name for platform components, which are
    unlikely to have a valid DAI name. This caused simple-card to fail to
    probe when using the xlnx_formatter_pcm as the platform component, since
    it does not register any DAI components.
    
    Since the dai_name is not used for platform components, just skip trying
    to retrieve it for those.
    
    Fixes: f107294c6422 ("ASoC: simple-card: support snd_soc_dai_link_component style for cpu")
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220107214711.1100162-6-robert.hancock@calian.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 68d247ad38b1ef46bd945a5220fa6d28c901c2f2
Author: Helge Deller <deller@gmx.de>
Date:   Tue Jan 11 11:54:48 2022 +0100

    parisc: Default to 16 CPUs on 32-bit kernel
    
    Qemu currently supports up to 16 CPUs, so increase the default from 4 to 16.
    Bload-o-meter shows only an increase of 800 bytes with this change.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 16f035d9e264d95d61d5f4056bb00d8169a7a3d1
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 7 01:13:02 2022 +0100

    sections: Fix __is_kernel() to include init ranges
    
    With CONFIG_KALLSYMS_ALL=y, the function is_ksym_addr() is used to
    determine if a symbol is from inside the kernel range. For that the
    given symbol address is checked if it's inside the _stext to _end range.
    
    Although this is correct, some architectures (e.g. parisc) may have the
    init area before the _stext address and as such the check in
    is_ksym_addr() fails.  By extending the range check to include the init
    section, __is_kernel() will now detect symbols in this range as well.
    
    This fixes an issue on parisc where addresses of kernel functions in
    init sections aren't resolved to their symbol names.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit e486288d116ab4885e42757de1e0e1ee5541c86e
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 7 14:16:26 2022 +0100

    parisc: Re-use toc_stack as hpmc_stack
    
    No need to have an own hpmc_stack. Just re-use the toc_stack of the
    monarch CPU as either a TOC or a HPMC will happen at the same time.
    This reduces the kernel memory footprint by 16k.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit d6ab9fc74513ae6501afcdae2547334a03b9a5c9
Author: Helge Deller <deller@gmx.de>
Date:   Fri Jan 7 14:05:11 2022 +0100

    parisc: Enable TOC (transfer of contents) feature unconditionally
    
    Before this patch, the TOC code used a pre-allocated stack of 16kb for
    each possible CPU. That space overhead was the reason why the TOC
    feature wasn't enabled by default for 32-bit kernels.
    
    This patch rewrites the TOC code to use a per-cpu stack. That way we use
    much less memory now and as such we enable the TOC feature by default on
    all kernels.
    
    Additionally the dump of the registers and the stacktrace wasn't
    serialized, which led to multiple CPUs printing the stack backtrace at
    once which rendered the output unreadable.
    Now the backtraces are nicely serialized by a lock.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit aa8589aac8e335e5e2e9a9de72a53913892e92f9
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Dec 9 15:47:25 2021 -0500

    PCI: brcmstb: Augment driver for MIPs SOCs
    
    The current brcmstb driver works for Arm and Arm64.  A few things are
    modified here for us to support MIPs as well.
    
      o There are four outbound range register groups and each directs a window
        of up to 128MB.  Even though there are four 128MB DT "ranges" in the
        bmips PCIe DT node, these ranges are contiguous and are collapsed into
        a single range by the OF range parser.  Now the driver assumes a single
        range -- for MIPs only -- and splits it back into 128MB sizes.
    
      o For bcm7425, the config space accesses must be 32-bit reads or
        writes.  In addition, the 4k config space register array is missing
        and not used.
    
      o The registers for the upper 32-bits of the outbound window address do
        not exist.
    
      o Burst size must be set to 256 (this refers to an internal bus).
    
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit d552ddeaab4a15a8dc157ac007833aa0b3706862
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Dec 9 15:47:24 2021 -0500

    MIPS: bmips: Remove obsolete DMA mapping support
    
    The code in 'arch/mips/bmips/dma.c' performed DMA mapping for inbound
    regions.  This mapping was and is required for the Broadcom STB PCIe
    controller HW.  This code is removed as the current 'struct device' has a
    @dma_range_map field which performs the same functionality by processing
    the "dma-ranges" DT property.
    
    Subsequently, ARCH_HAS_PHYS_TO_DMA is now unset since the dma_to_phys()
    and phys_to_dma() functions are removed.
    
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 6fffb01e3b78ba3a38baf49c1dc7eeb5edfd5818
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Dec 9 15:47:23 2021 -0500

    MIPS: bmips: Add support PCIe controller device nodes
    
    For Broadcom STB PCIe HW. The 7425 and 7435 are MIPs-based SOCs.  Not much
    difference between the two for the DT properties except that they have
    slightly different PCIe interrupt assignments.
    
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 145790e55d82e30182f48b0b94149ba41e3aabcc
Author: Jim Quinlan <jim2101024@gmail.com>
Date:   Thu Dec 9 15:47:22 2021 -0500

    dt-bindings: PCI: Add compatible string for Brcmstb 74[23]5 MIPs SOCs
    
    The Broadcom STB Arm and MIPs SOCs use the same PCIe controller
    HW, although the MIPs version is older.
    
    Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit a59466ee91aaa9d43889a4c51e01de087d188448
Author: Karolina Drobnik <karolinadrobnik@gmail.com>
Date:   Tue Jan 11 10:28:47 2022 +0000

    memblock: Remove #ifdef __KERNEL__ from memblock.h
    
    memblock.h is not a uAPI header, so __KERNEL__ guard can be deleted
    
    Signed-off-by: Karolina Drobnik <karolinadrobnik@gmail.com>
    Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
    Link: https://lore.kernel.org/r/20220111102847.673746-1-karolinadrobnik@gmail.com

commit c71af3dae3e34d2fde0c19623cf7f8483321f0e3
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 7 08:36:32 2022 +0000

    drm/sun4i: dw-hdmi: Fix missing put_device() call in sun8i_hdmi_phy_get
    
    The reference taken by 'of_find_device_by_node()' must be released when
    not needed anymore.
    Add the corresponding 'put_device()' in the error handling path.
    
    Fixes: 9bf3797796f5 ("drm/sun4i: dw-hdmi: Make HDMI PHY into a platform device")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: Maxime Ripard <maxime@cerno.tech>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220107083633.20843-1-linmq006@gmail.com

commit 1e9d74660d4df625b0889e77018f9e94727ceacd
Author: Yafang Shao <laoar.shao@gmail.com>
Date:   Sat Jan 8 13:46:23 2022 +0000

    bpf: Fix mount source show for bpffs
    
    We noticed our tc ebpf tools can't start after we upgrade our in-house kernel
    version from 4.19 to 5.10. That is because of the behaviour change in bpffs
    caused by commit d2935de7e4fd ("vfs: Convert bpf to use the new mount API").
    
    In our tc ebpf tools, we do strict environment check. If the environment is
    not matched, we won't allow to start the ebpf progs. One of the check is whether
    bpffs is properly mounted. The mount information of bpffs in kernel-4.19 and
    kernel-5.10 are as follows:
    
    - kernel 4.19
    $ mount -t bpf bpffs /sys/fs/bpf
    $ mount -t bpf
    bpffs on /sys/fs/bpf type bpf (rw,relatime)
    
    - kernel 5.10
    $ mount -t bpf bpffs /sys/fs/bpf
    $ mount -t bpf
    none on /sys/fs/bpf type bpf (rw,relatime)
    
    The device name in kernel-5.10 is displayed as none instead of bpffs, then our
    environment check fails. Currently we modify the tools to adopt to the kernel
    behaviour change, but I think we'd better change the kernel code to keep the
    behavior consistent.
    
    After this change, the mount information will be displayed the same with the
    behavior in kernel-4.19, for example:
    
    $ mount -t bpf bpffs /sys/fs/bpf
    $ mount -t bpf
    bpffs on /sys/fs/bpf type bpf (rw,relatime)
    
    Fixes: d2935de7e4fd ("vfs: Convert bpf to use the new mount API")
    Suggested-by: Daniel Borkmann <daniel@iogearbox.net>
    Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Cc: David Howells <dhowells@redhat.com>
    Cc: Al Viro <viro@zeniv.linux.org.uk>
    Link: https://lore.kernel.org/bpf/20220108134623.32467-1-laoar.shao@gmail.com

commit cf46eacbc156a82d6643eb10afe8969abad5a35f
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Tue Jan 11 10:40:30 2022 +0100

    netfilter: nf_tables: remove unused variable
    
    > Remove unused variable and fix missing initialization.
    >
    > >> net/netfilter/nf_tables_api.c:8266:6: warning: variable 'i' set but not used [-Wunused-but-set-variable]
    >            int i;
    >                ^
    
    Fixes: 2c865a8a28a1 ("netfilter: nf_tables: add rule blob layout")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 0e906607b9c5ee22312c9af4d8adb45c617ea38a
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 15:51:38 2022 +0100

    netfilter: nf_conntrack_netbios_ns: fix helper module alias
    
    The helper gets registered as 'netbios-ns', not netbios_ns.
    Intentionally not adding a fixes-tag because i don't want this to go to
    stable. This wasn't noticed for a very long time so no so no need to risk
    regressions.
    
    Reported-by: Yi Chen <yiche@redhat.com>
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit d47c7407b4c88cf66098eba8893bc38279f301fc
Merge: 663d8fb0f84c0 547d2167c5c3c
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Tue Jan 11 10:22:25 2022 +0100

    Merge tag 'gnss-5.17-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/gnss into char-misc-next
    
    Johan writes:
    
    GNSS updates for 5.17-rc1
    
    Here are the GNSS updates for 5.17-rc1, including:
    
     - support for GNSS receivers with USB interface
     - support for Sierra Wireless XM1210
    
    All have been in linux-next with no reported issues.
    
    * tag 'gnss-5.17-rc1' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/gnss:
      gnss: usb: add support for Sierra Wireless XM1210
      gnss: add USB support
      gnss: drop stray semicolons

commit 19d1c32652bbbf406063025354845fdddbcecd3a
Author: Dominique Martinet <asmadeus@codewreck.org>
Date:   Mon Jan 10 20:10:31 2022 +0900

    9p: fix enodata when reading growing file
    
    Reading from a file that was just extended by a write, but the write had
    not yet reached the server would return ENODATA as illustrated by this
    command:
    $ xfs_io -c 'open -ft test' -c 'w 4096 1000' -c 'r 0 1000'
    wrote 1000/1000 bytes at offset 4096
    1000.000000 bytes, 1 ops; 0.0001 sec (5.610 MiB/sec and 5882.3529 ops/sec)
    pread: No data available
    
    Fix this case by having netfs assume zeroes when reads from server come
    short like AFS and CEPH do
    
    Link: https://lkml.kernel.org/r/20220110111444.926753-1-asmadeus@codewreck.org
    Cc: stable@vger.kernel.org
    Fixes: eb497943fa21 ("9p: Convert to using the netfs helper lib to do reads and caching")
    Co-authored-by: David Howells <dhowells@redhat.com>
    Reviewed-by: David Howells <dhowells@redhat.com>
    Tested-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 7d6019b602de660bfc6a542a68630006ace83b90
Author: Saeed Mahameed <saeedm@nvidia.com>
Date:   Mon Jan 10 12:52:46 2022 -0800

    Revert "net: vertexcom: default to disabled on kbuild"
    
    This reverts commit 6bf950a8ff72920340dfdec93c18bd3f5f35de6a.
    
    To align with other vendors, NET_VENDOR configs are supposed to be ON by
    default, while their drivers should default to OFF.
    
    Suggested-by: Jakub Kicinski <kuba@kernel.org>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
    Link: https://lore.kernel.org/r/20220110205246.66298-1-saeed@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 51edb2ff1c6fc27d3fa73f0773a31597ecd8e230
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Mon Jan 10 20:48:17 2022 +0100

    netfilter: nf_tables: typo NULL check in _clone() function
    
    This should check for NULL in case memory allocation fails.
    
    Reported-by: Julian Wiedmann <jwiedmann.dev@gmail.com>
    Fixes: 3b9e2ea6c11b ("netfilter: nft_limit: move stateful fields out of expression data")
    Fixes: 37f319f37d90 ("netfilter: nft_connlimit: move stateful fields out of expression data")
    Fixes: 33a24de37e81 ("netfilter: nft_last: move stateful fields out of expression data")
    Fixes: ed0a0c60f0e5 ("netfilter: nft_quota: move stateful fields out of expression data")
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
    Link: https://lore.kernel.org/r/20220110194817.53481-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit fe8152b38d3a994c4c6fdbc0cd6551d569a5715a
Merge: fe2437ccbd278 3a571fc19673b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 20:48:19 2022 -0800

    Merge tag 'devprop-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull device properties framework updates from Rafael Wysocki:
     "These update the handling of software nodes and graph properties, and
      the MAINTAINERS entry for the former.
    
      Specifics:
    
       - Remove device_add_properties() which does not work correctly if
         software nodes holding additional device properties are shared or
         reused (Heikki Krogerus).
    
       - Fix nargs_prop property handling for software nodes (Clément
         Léger).
    
       - Update documentation of ACPI device properties (Sakari Ailus).
    
       - Update the handling of graph properties in the generic framework to
         match the DT case (Sakari Ailus).
    
       - Update software nodes entry in MAINTAINERS (Andy Shevchenko)"
    
    * tag 'devprop-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      software node: Update MAINTAINERS data base
      software node: fix wrong node passed to find nargs_prop
      device property: Drop fwnode_graph_get_remote_node()
      device property: Use fwnode_graph_for_each_endpoint() macro
      device property: Implement fwnode_graph_get_endpoint_count()
      Documentation: ACPI: Update references
      Documentation: ACPI: Fix data node reference documentation
      device property: Fix documentation for FWNODE_GRAPH_DEVICE_DISABLED
      device property: Fix fwnode_graph_devcon_match() fwnode leak
      device property: Remove device_add_properties() API
      driver core: Don't call device_remove_properties() from device_del()
      PCI: Convert to device_create_managed_software_node()

commit fe2437ccbd278af683d32196fdea59a3b95f144e
Merge: b35b6d4d71365 fff489ff0722b
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 20:43:54 2022 -0800

    Merge tag 'thermal-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull thermal control updates from Rafael Wysocki:
     "These add a new driver for Renesas RZ/G2L TSU, update a few existing
      thermal control drivers and clean up the tmon utility.
    
      Specifics:
    
       - Add new TSU driver and DT bindings for the Renesas RZ/G2L platform
         (Biju Das).
    
       - Fix missing check when calling reset_control_deassert() in the
         rz2gl thermal driver (Biju Das).
    
       - In preparation for FORTIFY_SOURCE performing compile-time and
         run-time field bounds checking for memcpy(), avoid intentionally
         writing across neighboring fields in the int340x thermal control
         driver (Kees Cook).
    
       - Fix RFIM mailbox write commands handling in the int340x thermal
         control driver (Sumeet Pawnikar).
    
       - Fix PM issue occurring in the iMX thermal control driver during
         suspend/resume by implementing PM runtime support in it (Oleksij
         Rempel).
    
       - Add 'const' annotation to thermal_cooling_ops in the Intel
         powerclamp driver (Rikard Falkeborn).
    
       - Fix missing ADC bit set in the iMX8MP thermal driver to enable the
         sensor (Paul Gerber).
    
       - Drop unused local variable definition from tmon (ran jianping)"
    
    * tag 'thermal-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
      thermal/drivers/int340x: Fix RFIM mailbox write commands
      thermal/drivers/rz2gl: Add error check for reset_control_deassert()
      thermal/drivers/imx8mm: Enable ADC when enabling monitor
      thermal/drivers: Add TSU driver for RZ/G2L
      dt-bindings: thermal: Document Renesas RZ/G2L TSU
      thermal/drivers/intel_powerclamp: Constify static thermal_cooling_device_ops
      thermal/drivers/imx: Implement runtime PM support
      thermal: tools: tmon: remove unneeded local variable
      thermal: int340x: Use struct_group() for memcpy() region

commit b35b6d4d71365fbfb6f2cc8edc331b3882ca817e
Merge: bca21755b9fc0 78e6e4dfd8f0c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 20:34:00 2022 -0800

    Merge tag 'pm-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull power management updates from Rafael Wysocki:
     "The most signigicant change here is the addition of a new cpufreq
      'P-state' driver for AMD processors as a better replacement for the
      venerable acpi-cpufreq driver.
    
      There are also other cpufreq updates (in the core, intel_pstate, ARM
      drivers), PM core updates (mostly related to adding new macros for
      declaring PM operations which should make the lives of driver
      developers somewhat easier), and a bunch of assorted fixes and
      cleanups.
    
      Summary:
    
       - Add new P-state driver for AMD processors (Huang Rui).
    
       - Fix initialization of min and max frequency QoS requests in the
         cpufreq core (Rafael Wysocki).
    
       - Fix EPP handling on Alder Lake in intel_pstate (Srinivas
         Pandruvada).
    
       - Make intel_pstate update cpuinfo.max_freq when notified of HWP
         capabilities changes and drop a redundant function call from that
         driver (Rafael Wysocki).
    
       - Improve IRQ support in the Qcom cpufreq driver (Ard Biesheuvel,
         Stephen Boyd, Vladimir Zapolskiy).
    
       - Fix double devm_remap() in the Mediatek cpufreq driver (Hector
         Yuan).
    
       - Introduce thermal pressure helpers for cpufreq CPU cooling (Lukasz
         Luba).
    
       - Make cpufreq use default_groups in kobj_type (Greg Kroah-Hartman).
    
       - Make cpuidle use default_groups in kobj_type (Greg Kroah-Hartman).
    
       - Fix two comments in cpuidle code (Jason Wang, Yang Li).
    
       - Allow model-specific normal EPB value to be used in the intel_epb
         sysfs attribute handling code (Srinivas Pandruvada).
    
       - Simplify locking in pm_runtime_put_suppliers() (Rafael Wysocki).
    
       - Add safety net to supplier device release in the runtime PM core
         code (Rafael Wysocki).
    
       - Capture device status before disabling runtime PM for it (Rafael
         Wysocki).
    
       - Add new macros for declaring PM operations to allow drivers to
         avoid guarding them with CONFIG_PM #ifdefs or __maybe_unused and
         update some drivers to use these macros (Paul Cercueil).
    
       - Allow ACPI hardware signature to be honoured during restore from
         hibernation (David Woodhouse).
    
       - Update outdated operating performance points (OPP) documentation
         (Tang Yizhou).
    
       - Reduce log severity for informative message regarding frequency
         transition failures in devfreq (Tzung-Bi Shih).
    
       - Add DRAM frequency controller devfreq driver for Allwinner sunXi
         SoCs (Samuel Holland).
    
       - Add missing COMMON_CLK dependency to sun8i devfreq driver (Arnd
         Bergmann).
    
       - Add support for new layout of Psys PowerLimit Register on SPR to
         the Intel RAPL power capping driver (Zhang Rui).
    
       - Fix typo in a comment in idle_inject.c (Jason Wang).
    
       - Remove unused function definition from the DTPM (Dynamit Thermal
         Power Management) power capping framework (Daniel Lezcano).
    
       - Reduce DTPM trace verbosity (Daniel Lezcano)"
    
    * tag 'pm-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (53 commits)
      x86, sched: Fix undefined reference to init_freq_invariance_cppc() build error
      cpufreq: amd-pstate: Fix Kconfig dependencies for AMD P-State
      cpufreq: amd-pstate: Fix struct amd_cpudata kernel-doc comment
      cpuidle: use default_groups in kobj_type
      x86: intel_epb: Allow model specific normal EPB value
      MAINTAINERS: Add AMD P-State driver maintainer entry
      Documentation: amd-pstate: Add AMD P-State driver introduction
      cpufreq: amd-pstate: Add AMD P-State performance attributes
      cpufreq: amd-pstate: Add AMD P-State frequencies attributes
      cpufreq: amd-pstate: Add boost mode support for AMD P-State
      cpufreq: amd-pstate: Add trace for AMD P-State module
      cpufreq: amd-pstate: Introduce the support for the processors with shared memory solution
      cpufreq: amd-pstate: Add fast switch function for AMD P-State
      cpufreq: amd-pstate: Introduce a new AMD P-State driver to support future processors
      ACPI: CPPC: Add CPPC enable register function
      ACPI: CPPC: Check present CPUs for determining _CPC is valid
      ACPI: CPPC: Implement support for SystemIO registers
      x86/msr: Add AMD CPPC MSR definitions
      x86/cpufeatures: Add AMD Collaborative Processor Performance Control feature flag
      cpufreq: use default_groups in kobj_type
      ...

commit bca21755b9fc00dbe371994b53389eb5d70b8e72
Merge: 63045bfd3c8db 70df8e1bdc941
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 20:26:56 2022 -0800

    Merge tag 'acpi-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
    
    Pull ACPI updates from Rafael Wysocki:
     "These are usual ACPICA code updates (although there are more of them
      than in the last few releases), a noticeable EC driver update (which
      mostly consists of cleanups, though), the device enumeration quirks
      handling rework from Hans, some updates eliminating unnecessary CPU
      cache flushing in some places (processor idle and system-wide PM code)
      and a bunch of assorted cleanups and fixes.
    
      Specifics:
    
       - Update ACPICA code in the kernel to the 20211217 upstream release
         including the following changes:
    
          - iASL/Disassembler: Additional support for NHLT table (Bob
            Moore).
          - Change a return_ACPI_STATUS (AE_BAD_PARAMETER) (Bob Moore).
          - Fix a couple of warnings under MSVC (Bob Moore).
          - iASL: Add TDEL table to both compiler/disassembler (Bob Moore).
          - iASL/NHLT table: "Specific Data" field support (Bob Moore).
          - Use original data_table_region pointer for accesses (Jessica
            Clarke).
          - Use original pointer for virtual origin tables (Jessica Clarke).
          - Macros: Remove ACPI_PHYSADDR_TO_PTR (Jessica Clarke).
          - Avoid subobject buffer overflow when validating RSDP signature
            (Jessica Clarke).
          - iASL: Add suppport for AGDI table (Ilkka Koskinen).
          - Hardware: Do not flush CPU cache when entering S4 and S5 (Kirill
            A. Shutemov).
          - Expand the ACPI_ACCESS_ definitions (Mark Langsdorf).
          - Utilities: Avoid deleting the same object twice in a row (Rafael
            Wysocki).
          - Executer: Fix REFCLASS_REFOF case in acpi_ex_opcode_1A_0T_1R()
            (Rafael Wysocki).
          - Fix AEST Processor generic resource substructure data field byte
            length (Shuuichirou Ishii).
          - Fix wrong interpretation of PCC address (Sudeep Holla).
          - Add support for PCC Opregion special context data (Sudeep
            Holla).
    
       - Implement OperationRegion handler for PCC Type 3 subtype (Sudeep
         Holla).
    
       - Introduce acpi_fetch_acpi_dev() as a replacement for
         acpi_bus_get_device() and use it in the ACPI subsystem (Rafael
         Wysocki).
    
       - Avoid using _CID for device enumaration if _HID is missing or
         invalid (Rafael Wysocki).
    
       - Rework quirk handling during ACPI device enumeration and add some
         new quirks for known broken platforms (Hans de Goede).
    
       - Avoid unnecessary or redundant CPU cache flushing during system PM
         transitions (Kirill A. Shutemov).
    
       - Add PM debug messages related to power resources (Rafael Wysocki).
    
       - Fix kernel-doc comment in the PCI host bridge ACPI driver (Yang
         Li).
    
       - Rework flushing of EC work while suspended to idle and clean up the
         handling of events in the ACPI EC driver (Rafael Wysocki).
    
       - Prohibit ec_sys module parameter write_support from being used when
         the system is locked down (Hans de Goede).
    
       - Make the ACPI processor thermal driver use cpufreq_cpu_get() to
         check for presence of cpufreq policy (Manfred Spraul).
    
       - Avoid unnecessary CPU cache flushing in the ACPI processor idle
         driver (Kirill A. Shutemov).
    
       - Replace kernel.h with the necessary inclusions in the ACPI
         processor driver (Andy Shevchenko).
    
       - Use swap() instead of open coding it in the ACPI processor idle
         driver (Guo Zhengkui).
    
       - Fix the handling of defective LPAT in the ACPI xpower PMIC driver
         and clean up some definitions of PMIC data structures (Hans de
         Goede).
    
       - Fix outdated comment in the ACPI DPTF driver (Sumeet Pawnikar).
    
       - Add AEST to the list of known ACPI table signatures (Shuuichirou
         Ishii).
    
       - Make ACPI NUMA code take hotpluggable memblocks into account when
         CONFIG_MEMORY_HOTPLUG is not set (Vitaly Kuznetsov).
    
       - Use default_groups in kobj_type in the ACPI sysfs code (Greg
         Kroah-Hartman).
    
       - Rearrange _CPC structure documentation (Andy Shevchenko).
    
       - Drop an always true check from the ACPI thermal driver (Adam
         Borowski).
    
       - Add new "not charging" quirk for Lenovo ThinkPads to the ACPI
         battery driver (Thomas Weißschuh)"
    
    * tag 'acpi-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (64 commits)
      ACPI: PCC: Implement OperationRegion handler for the PCC Type 3 subtype
      ACPI / x86: Skip AC and battery devices on x86 Android tablets with broken DSDTs
      ACPI / x86: Introduce an acpi_quirk_skip_acpi_ac_and_battery() helper
      ACPI: processor: thermal: avoid cpufreq_get_policy()
      serdev: Do not instantiate serdevs on boards with known bogus DSDT entries
      i2c: acpi: Do not instantiate I2C-clients on boards with known bogus DSDT entries
      ACPI / x86: Add acpi_quirk_skip_[i2c_client|serdev]_enumeration() helpers
      ACPI: scan: Create platform device for BCM4752 and LNV4752 ACPI nodes
      PCI/ACPI: Fix acpi_pci_osc_control_set() kernel-doc comment
      ACPI: battery: Add the ThinkPad "Not Charging" quirk
      ACPI: sysfs: use default_groups in kobj_type
      ACPICA: Update version to 20211217
      ACPICA: iASL/NHLT table: "Specific Data" field support
      ACPICA: iASL: Add suppport for AGDI table
      ACPICA: iASL: Add TDEL table to both compiler/disassembler
      ACPICA: Fixed a couple of warnings under MSVC
      ACPICA: Change a return_ACPI_STATUS (AE_BAD_PARAMETER)
      ACPICA: Hardware: Do not flush CPU cache when entering S4 and S5
      ACPICA: Add support for PCC Opregion special context data
      ACPICA: Fix wrong interpretation of PCC address
      ...

commit 63045bfd3c8dbe9c8bee7e33291202725154cb2c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 19:33:36 2022 -0800

    netfilter: nf_tables: don't use 'data_size' uninitialized
    
    Commit 2c865a8a28a1 ("netfilter: nf_tables: add rule blob layout") never
    initialized the new 'data_size' variable.
    
    I'm not sure how it ever worked, but it might have worked almost by
    accident - gcc seems to occasionally miss these kinds of 'variable used
    uninitialized' situations, but I've seen it do so because it ended up
    zero-initializing them due to some other simplification.
    
    But clang is very unhappy about it all, and correctly reports
    
        net/netfilter/nf_tables_api.c:8278:4: error: variable 'data_size' is uninitialized when used here [-Werror,-Wuninitialized]
                                data_size += sizeof(*prule) + rule->dlen;
                                ^~~~~~~~~
        net/netfilter/nf_tables_api.c:8263:30: note: initialize the variable 'data_size' to silence this warning
                unsigned int size, data_size;
                                            ^
                                             = 0
        1 error generated.
    
    and this fix just initializes 'data_size' to zero before the loop.
    
    Fixes: 2c865a8a28a1 ("netfilter: nf_tables: add rule blob layout")
    Cc: Pablo Neira Ayuso <pablo@netfilter.org>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: David Miller <davem@davemloft.net>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8efd0d9c316af470377894a6a0f9ff63ce18c177
Merge: 9bcbf894b6872 8aaaf2f3af2ae
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 19:06:09 2022 -0800

    Merge tag '5.17-net-next' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
    
    Pull networking updates from Jakub Kicinski:
     "Core
      ----
    
       - Defer freeing TCP skbs to the BH handler, whenever possible, or at
         least perform the freeing outside of the socket lock section to
         decrease cross-CPU allocator work and improve latency.
    
       - Add netdevice refcount tracking to locate sources of netdevice and
         net namespace refcount leaks.
    
       - Make Tx watchdog less intrusive - avoid pausing Tx and restarting
         all queues from a single CPU removing latency spikes.
    
       - Various small optimizations throughout the stack from Eric Dumazet.
    
       - Make netdev->dev_addr[] constant, force modifications to go via
         appropriate helpers to allow us to keep addresses in ordered data
         structures.
    
       - Replace unix_table_lock with per-hash locks, improving performance
         of bind() calls.
    
       - Extend skb drop tracepoint with a drop reason.
    
       - Allow SO_MARK and SO_PRIORITY setsockopt under CAP_NET_RAW.
    
      BPF
      ---
    
       - New helpers:
          - bpf_find_vma(), find and inspect VMAs for profiling use cases
          - bpf_loop(), runtime-bounded loop helper trading some execution
            time for much faster (if at all converging) verification
          - bpf_strncmp(), improve performance, avoid compiler flakiness
          - bpf_get_func_arg(), bpf_get_func_ret(), bpf_get_func_arg_cnt()
            for tracing programs, all inlined by the verifier
    
       - Support BPF relocations (CO-RE) in the kernel loader.
    
       - Further the support for BTF_TYPE_TAG annotations.
    
       - Allow access to local storage in sleepable helpers.
    
       - Convert verifier argument types to a composable form with different
         attributes which can be shared across types (ro, maybe-null).
    
       - Prepare libbpf for upcoming v1.0 release by cleaning up APIs,
         creating new, extensible ones where missing and deprecating those
         to be removed.
    
      Protocols
      ---------
    
       - WiFi (mac80211/cfg80211):
          - notify user space about long "come back in N" AP responses,
            allow it to react to such temporary rejections
          - allow non-standard VHT MCS 10/11 rates
          - use coarse time in airtime fairness code to save CPU cycles
    
       - Bluetooth:
          - rework of HCI command execution serialization to use a common
            queue and work struct, and improve handling errors reported in
            the middle of a batch of commands
          - rework HCI event handling to use skb_pull_data, avoiding packet
            parsing pitfalls
          - support AOSP Bluetooth Quality Report
    
       - SMC:
          - support net namespaces, following the RDMA model
          - improve connection establishment latency by pre-clearing buffers
          - introduce TCP ULP for automatic redirection to SMC
    
       - Multi-Path TCP:
          - support ioctls: SIOCINQ, OUTQ, and OUTQNSD
          - support socket options: IP_TOS, IP_FREEBIND, IP_TRANSPARENT,
            IPV6_FREEBIND, and IPV6_TRANSPARENT, TCP_CORK and TCP_NODELAY
          - support cmsgs: TCP_INQ
          - improvements in the data scheduler (assigning data to subflows)
          - support fastclose option (quick shutdown of the full MPTCP
            connection, similar to TCP RST in regular TCP)
    
       - MCTP (Management Component Transport) over serial, as defined by
         DMTF spec DSP0253 - "MCTP Serial Transport Binding".
    
      Driver API
      ----------
    
       - Support timestamping on bond interfaces in active/passive mode.
    
       - Introduce generic phylink link mode validation for drivers which
         don't have any quirks and where MAC capability bits fully express
         what's supported. Allow PCS layer to participate in the validation.
         Convert a number of drivers.
    
       - Add support to set/get size of buffers on the Rx rings and size of
         the tx copybreak buffer via ethtool.
    
       - Support offloading TC actions as first-class citizens rather than
         only as attributes of filters, improve sharing and device resource
         utilization.
    
       - WiFi (mac80211/cfg80211):
          - support forwarding offload (ndo_fill_forward_path)
          - support for background radar detection hardware
          - SA Query Procedures offload on the AP side
    
      New hardware / drivers
      ----------------------
    
       - tsnep - FPGA based TSN endpoint Ethernet MAC used in PLCs with
         real-time requirements for isochronous communication with protocols
         like OPC UA Pub/Sub.
    
       - Qualcomm BAM-DMUX WWAN - driver for data channels of modems
         integrated into many older Qualcomm SoCs, e.g. MSM8916 or MSM8974
         (qcom_bam_dmux).
    
       - Microchip LAN966x multi-port Gigabit AVB/TSN Ethernet Switch driver
         with support for bridging, VLANs and multicast forwarding
         (lan966x).
    
       - iwlmei driver for co-operating between Intel's WiFi driver and
         Intel's Active Management Technology (AMT) devices.
    
       - mse102x - Vertexcom MSE102x Homeplug GreenPHY chips
    
       - Bluetooth:
          - MediaTek MT7921 SDIO devices
          - Foxconn MT7922A
          - Realtek RTL8852AE
    
      Drivers
      -------
    
       - Significantly improve performance in the datapaths of: lan78xx,
         ax88179_178a, lantiq_xrx200, bnxt.
    
       - Intel Ethernet NICs:
          - igb: support PTP/time PEROUT and EXTTS SDP functions on
            82580/i354/i350 adapters
          - ixgbevf: new PF -> VF mailbox API which avoids the risk of
            mailbox corruption with ESXi
          - iavf: support configuration of VLAN features of finer
            granularity, stacked tags and filtering
          - ice: PTP support for new E822 devices with sub-ns precision
          - ice: support firmware activation without reboot
    
       - Mellanox Ethernet NICs (mlx5):
          - expose control over IRQ coalescing mode (CQE vs EQE) via ethtool
          - support TC forwarding when tunnel encap and decap happen between
            two ports of the same NIC
          - dynamically size and allow disabling various features to save
            resources for running in embedded / SmartNIC scenarios
    
       - Broadcom Ethernet NICs (bnxt):
          - use page frag allocator to improve Rx performance
          - expose control over IRQ coalescing mode (CQE vs EQE) via ethtool
    
       - Other Ethernet NICs:
          - amd-xgbe: add Ryzen 6000 (Yellow Carp) Ethernet support
    
       - Microsoft cloud/virtual NIC (mana):
          - add XDP support (PASS, DROP, TX)
    
       - Mellanox Ethernet switches (mlxsw):
          - initial support for Spectrum-4 ASICs
          - VxLAN with IPv6 underlay
    
       - Marvell Ethernet switches (prestera):
          - support flower flow templates
          - add basic IP forwarding support
    
       - NXP embedded Ethernet switches (ocelot & felix):
          - support Per-Stream Filtering and Policing (PSFP)
          - enable cut-through forwarding between ports by default
          - support FDMA to improve packet Rx/Tx to CPU
    
       - Other embedded switches:
          - hellcreek: improve trapping management (STP and PTP) packets
          - qca8k: support link aggregation and port mirroring
    
       - Qualcomm 802.11ax WiFi (ath11k):
          - qca6390, wcn6855: enable 802.11 power save mode in station mode
          - BSS color change support
          - WCN6855 hw2.1 support
          - 11d scan offload support
          - scan MAC address randomization support
          - full monitor mode, only supported on QCN9074
          - qca6390/wcn6855: report signal and tx bitrate
          - qca6390: rfkill support
          - qca6390/wcn6855: regdb.bin support
    
       - Intel WiFi (iwlwifi):
          - support SAR GEO Offset Mapping (SGOM) and Time-Aware-SAR (TAS)
            in cooperation with the BIOS
          - support for Optimized Connectivity Experience (OCE) scan
          - support firmware API version 68
          - lots of preparatory work for the upcoming Bz device family
    
       - MediaTek WiFi (mt76):
          - Specific Absorption Rate (SAR) support
          - mt7921: 160 MHz channel support
    
       - RealTek WiFi (rtw88):
          - Specific Absorption Rate (SAR) support
          - scan offload
    
       - Other WiFi NICs
          - ath10k: support fetching (pre-)calibration data from nvmem
          - brcmfmac: configure keep-alive packet on suspend
          - wcn36xx: beacon filter support"
    
    * tag '5.17-net-next' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next: (2048 commits)
      tcp: tcp_send_challenge_ack delete useless param `skb`
      net/qla3xxx: Remove useless DMA-32 fallback configuration
      rocker: Remove useless DMA-32 fallback configuration
      hinic: Remove useless DMA-32 fallback configuration
      lan743x: Remove useless DMA-32 fallback configuration
      net: enetc: Remove useless DMA-32 fallback configuration
      cxgb4vf: Remove useless DMA-32 fallback configuration
      cxgb4: Remove useless DMA-32 fallback configuration
      cxgb3: Remove useless DMA-32 fallback configuration
      bnx2x: Remove useless DMA-32 fallback configuration
      et131x: Remove useless DMA-32 fallback configuration
      be2net: Remove useless DMA-32 fallback configuration
      vmxnet3: Remove useless DMA-32 fallback configuration
      bna: Simplify DMA setting
      net: alteon: Simplify DMA setting
      myri10ge: Simplify DMA setting
      qlcnic: Simplify DMA setting
      net: allwinner: Fix print format
      page_pool: remove spinlock in page_pool_refill_alloc_cache()
      amt: fix wrong return type of amt_send_membership_update()
      ...

commit 9bcbf894b6872216ef61faf17248ec234e3db6bc
Merge: 75b950ef6166e 68b9bcc8a534c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 18:55:43 2022 -0800

    Merge tag 'media/v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
    
    Pull media updates from Mauro Carvalho Chehab:
    
     - New sensor driver: ov5693
    
     - A new driver for STM32 Chrom-ART Accelerator
    
     - Added V4L2 core helper functions for VP9 codec
    
     - Hantro driver has gained support for VP9 codecs
    
     - Added support for Maxim MAX96712 Quad GMSL2 Deserializer
    
     - The staging atomisp driver has gained lots of improvements, fixes and
       cleanups. It now works with userptr
    
     - Lots of random driver improvements as usual
    
    * tag 'media/v5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: (397 commits)
      media: ipu3-cio2: Add support for instantiating i2c-clients for VCMs
      media: ipu3-cio2: Call cio2_bridge_init() before anything else
      media: ipu3-cio2: Defer probing until the PMIC is fully setup
      media: hantro: Add support for Allwinner H6
      media: dt-bindings: allwinner: document H6 Hantro G2 binding
      media: hantro: Convert imx8m_vpu_g2_irq to helper
      media: hantro: move postproc enablement for old cores
      media: hantro: vp9: add support for legacy register set
      media: hantro: vp9: use double buffering if needed
      media: hantro: add support for reset lines
      media: hantro: Fix probe func error path
      media: i2c: hi846: use pm_runtime_force_suspend/resume for system suspend
      media: i2c: hi846: check return value of regulator_bulk_disable()
      media: hi556: Support device probe in non-zero ACPI D state
      media: ov5675: Support device probe in non-zero ACPI D state
      media: imx208: Support device probe in non-zero ACPI D state
      media: ov2740: support device probe in non-zero ACPI D state
      media: ov5670: Support device probe in non-zero ACPI D state
      media: ov8856: support device probe in non-zero ACPI D state
      media: ov8865: Disable only enabled regulators on error path
      ...

commit 75b950ef6166e4ef52e43e7ec80985c5705f7e81
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 18:50:10 2022 -0800

    Revert "drm/amd/display: Fix for otg synchronization logic"
    
    This reverts commit a896f870f8a5f23ec961d16baffd3fda1f8be57c.
    
    It causes odd flickering on my Radeon RX580 (PCI ID 1002:67df rev e7,
    subsystem ID 1da2:e353).
    
    Bisected right to this commit, and reverting it fixes things.
    
    Link: https://lore.kernel.org/all/CAHk-=wg9hDde_L3bK9tAfdJ4N=TJJ+SjO3ZDONqH5=bVoy_Mzg@mail.gmail.com/
    Cc: Alex Deucher <alexdeucher@gmail.com>
    Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
    Cc: Harry Wentland <harry.wentland@amd.com>
    Cc: Dave Airlie <airlied@gmail.com>
    Cc: Christian Koenig <christian.koenig@amd.com>
    Cc: Jun Lei <Jun.Lei@amd.com>
    Cc: Mustapha Ghaddar <mustapha.ghaddar@amd.com>
    Cc: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
    Cc: meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>
    Cc: Daniel Wheeler <daniel.wheeler@amd.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

commit 8d0749b4f83bf4768ceae45ee6a79e6e7eddfc2a
Merge: bf4eebf8cfa2c cb6846fbb83b5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 12:58:46 2022 -0800

    Merge tag 'drm-next-2022-01-07' of git://anongit.freedesktop.org/drm/drm
    
    Pull drm updates from Dave Airlie:
     "Highlights are support for privacy screens found in new laptops, a
      bunch of nomodeset refactoring, and i915 enables ADL-P systems by
      default, while starting to add RPL-S support.
    
      vmwgfx adds GEM and support for OpenGL 4.3 features in userspace.
    
      Lots of internal refactorings around dma reservations, and lots of
      driver refactoring as well.
    
      Summary:
    
      core:
       - add privacy screen support
       - move nomodeset option into drm subsystem
       - clean up nomodeset handling in drivers
       - make drm_irq.c legacy
       - fix stack_depot name conflicts
       - remove DMA_BUF_SET_NAME ioctl restrictions
       - sysfs: send hotplug event
       - replace several DRM_* logging macros with drm_*
       - move hashtable to legacy code
       - add error return from gem_create_object
       - cma-helper: improve interfaces, drop CONFIG_DRM_KMS_CMA_HELPER
       - kernel.h related include cleanups
       - support XRGB2101010 source buffers
    
      ttm:
       - don't include drm hashtable
       - stop pruning fences after wait
       - documentation updates
    
      dma-buf:
       - add dma_resv selftest
       - add debugfs helpers
       - remove dma_resv_get_excl_unlocked
       - documentation
       - make fences mandatory in dma_resv_add_excl_fence
    
      dp:
       - add link training delay helpers
    
      gem:
       - link shmem/cma helpers into separate modules
       - use dma_resv iteratior
       - import dma-buf namespace into gem helper modules
    
      scheduler:
       - fence grab fix
       - lockdep fixes
    
      bridge:
       - switch to managed MIPI DSI helpers
       - register and attach during probe fixes
       - convert to YAML in several places.
    
      panel:
       - add bunch of new panesl
    
      simpledrm:
       - support FB_DAMAGE_CLIPS
       - support virtual screen sizes
       - add Apple M1 support
    
      amdgpu:
       - enable seamless boot for DCN 3.01
       - runtime PM fixes
       - use drm_kms_helper_connector_hotplug_event
       - get all fences at once
       - use generic drm fb helpers
       - PSR/DPCD/LTTPR/DSC/PM/RAS/OLED/SRIOV fixes
       - add smart trace buffer (STB) for supported GPUs
       - display debugfs entries
       - new SMU debug option
       - Documentation update
    
      amdkfd:
       - IP discovery enumeration refactor
       - interface between driver fixes
       - SVM fixes
       - kfd uapi header to define some sysfs bitfields.
    
      i915:
       - support VESA panel backlights
       - enable ADL-P by default
       - add eDP privacy screen support
       - add Raptor Lake S (RPL-S) support
       - DG2 page table support
       - lots of GuC/HuC fw refactoring
       - refactored i915->gt interfaces
       - CD clock squashing support
       - enable 10-bit gamma support
       - update ADL-P DMC fw to v2.14
       - enable runtime PM autosuspend by default
       - ADL-P DSI support
       - per-lane DP drive settings for ICL+
       - add support for pipe C/D DMC firmware
       - Atomic gamma LUT updates
       - remove CCS FB stride restrictions on ADL-P
       - VRR platform support for display 11
       - add support for display audio codec keepalive
       - lots of display refactoring
       - fix runtime PM handling during PXP suspend
       - improved eviction performance with async TTM moves
       - async VMA unbinding improvements
       - VMA locking refactoring
       - improved error capture robustness
       - use per device iommu checks
       - drop bits stealing from i915_sw_fence function ptr
       - remove dma_resv_prune
       - add IC cache invalidation on DG2
    
      nouveau:
       - crc fixes
       - validate LUTs in atomic check
       - set HDMI AVI RGB quant to full
    
      tegra:
       - buffer objects reworks for dma-buf compat
       - NVDEC driver uAPI support
       - power management improvements
    
      etnaviv:
       - IOMMU enabled system support
       - fix > 4GB command buffer mapping
       - close a DoS vector
       - fix spurious GPU resets
    
      ast:
       - fix i2c initialization
    
      rcar-du:
       - DSI output support
    
      exynos:
       - replace legacy gpio interface
       - implement generic GEM object mmap
    
      msm:
       - dpu plane state cleanup in prep for multirect
       - dpu debugfs cleanups
       - dp support for sc7280
       - a506 support
       - removal of struct_mutex
       - remove old eDP sub-driver
    
      anx7625:
       - support MIPI DSI input
       - support HDMI audio
       - fix reading EDID
    
      lvds:
       - fix bridge DT bindings
    
      megachips:
       - probe both bridges before registering
    
      dw-hdmi:
       - allow interlace on bridge
    
      ps8640:
       - enable runtime PM
       - support aux-bus
    
      tx358768:
       - enable reference clock
       - add pulse mode support
    
      ti-sn65dsi86:
       - use regmap bulk write
       - add PWM support
    
      etnaviv:
       - get all fences at once
    
      gma500:
       - gem object cleanups
    
      kmb:
       - enable fb console
    
      radeon:
       - use dma_resv_wait_timeout
    
      rockchip:
       - add DSP hold timeout
       - suspend/resume fixes
       - PLL clock fixes
       - implement mmap in GEM object functions
       - use generic fbdev emulation
    
      sun4i:
       - use CMA helpers without vmap support
    
      vc4:
       - fix HDMI-CEC hang with display is off
       - power on HDMI controller while disabling
       - support 4K@60Hz modes
       - support 10-bit YUV 4:2:0 output
    
      vmwgfx:
       - fix leak on probe errors
       - fail probing on broken hosts
       - new placement for MOB page tables
       - hide internal BOs from userspace
       - implement GEM support
       - implement GL 4.3 support
    
      virtio:
       - overflow fixes
    
      xen:
       - implement mmap as GEM object function
    
      omapdrm:
       - fix scatterlist export
       - support virtual planes
    
      mediatek:
       - MT8192 support
       - CMDQ refinement"
    
    * tag 'drm-next-2022-01-07' of git://anongit.freedesktop.org/drm/drm: (1241 commits)
      drm/amdgpu: no DC support for headless chips
      drm/amd/display: fix dereference before NULL check
      drm/amdgpu: always reset the asic in suspend (v2)
      drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable platform
      drm/amd/display: Fix the uninitialized variable in enable_stream_features()
      drm/amdgpu: fix runpm documentation
      amdgpu/pm: Make sysfs pm attributes as read-only for VFs
      drm/amdgpu: save error count in RAS poison handler
      drm/amdgpu: drop redundant semicolon
      drm/amd/display: get and restore link res map
      drm/amd/display: support dynamic HPO DP link encoder allocation
      drm/amd/display: access hpo dp link encoder only through link resource
      drm/amd/display: populate link res in both detection and validation
      drm/amd/display: define link res and make it accessible to all link interfaces
      drm/amd/display: 3.2.167
      drm/amd/display: [FW Promotion] Release 0.0.98
      drm/amd/display: Undo ODM combine
      drm/amd/display: Add reg defs for DCN303
      drm/amd/display: Changed pipe split policy to allow for multi-display pipe split
      drm/amd/display: Set optimize_pwr_state for DCN31
      ...

commit b6e43dddaea3dbfa93327f986beb3ec5e8157c4c
Author: Qinghua Jin <qhjin.dev@gmail.com>
Date:   Mon Jan 10 12:46:05 2022 -0800

    Input: ti_am335x_tsc - fix a typo in a comment
    
    change 'postion' to 'position'
    
    Signed-off-by: Qinghua Jin <qhjin.dev@gmail.com>
    Link: https://lore.kernel.org/r/20220106084215.355295-1-qhjin.dev@gmail.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit bf4eebf8cfa2cd50e20b7321dfb3effdcdc6e909
Merge: 4369b3cec2134 ad659ccb54128
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 12:16:48 2022 -0800

    Merge tag 'linux-kselftest-kunit-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull KUnit updates from Shuah Khan:
     "This consists of several fixes and enhancements. A few highlights:
    
       - Option --kconfig_add option allows easily tweaking kunitconfigs
    
       - make build subcommand can reconfigure if needed
    
       - doesn't error on tests without test plans
    
       - doesn't crash if no parameters are generated
    
       - defaults --jobs to # of cups
    
       - reports test parameter results as (K)TAP subtests"
    
    * tag 'linux-kselftest-kunit-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      kunit: tool: Default --jobs to number of CPUs
      kunit: tool: fix newly introduced typechecker errors
      kunit: tool: make `build` subcommand also reconfigure if needed
      kunit: tool: delete kunit_parser.TestResult type
      kunit: tool: use dataclass instead of collections.namedtuple
      kunit: tool: suggest using decode_stacktrace.sh on kernel crash
      kunit: tool: reconfigure when the used kunitconfig changes
      kunit: tool: revamp message for invalid kunitconfig
      kunit: tool: add --kconfig_add to allow easily tweaking kunitconfigs
      kunit: tool: move Kconfig read_from_file/parse_from_string to package-level
      kunit: tool: print parsed test results fully incrementally
      kunit: Report test parameter results as (K)TAP subtests
      kunit: Don't crash if no parameters are generated
      kunit: tool: Report an error if any test has no subtests
      kunit: tool: Do not error on tests without test plans
      kunit: add run_checks.py script to validate kunit changes
      Documentation: kunit: remove claims that kunit is a mocking framework
      kunit: tool: fix --json output for skipped tests

commit 4369b3cec2134a6b8ff59b0ed5cca2f816d6e388
Merge: ca1a46d6f5064 e89908201e250
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 12:08:12 2022 -0800

    Merge tag 'linux-kselftest-next-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
    
    Pull Kselftest update from Shuah Khan:
     "Fixes to build errors, false negatives, and several code cleanups,
      including the ARRAY_SIZE cleanup that removes 25+ duplicates
      ARRAY_SIZE defines from individual tests"
    
    * tag 'linux-kselftest-next-5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest:
      selftests/vm: remove ARRAY_SIZE define from individual tests
      selftests/timens: remove ARRAY_SIZE define from individual tests
      selftests/sparc64: remove ARRAY_SIZE define from adi-test
      selftests/seccomp: remove ARRAY_SIZE define from seccomp_benchmark
      selftests/rseq: remove ARRAY_SIZE define from individual tests
      selftests/net: remove ARRAY_SIZE define from individual tests
      selftests/landlock: remove ARRAY_SIZE define from common.h
      selftests/ir: remove ARRAY_SIZE define from ir_loopback.c
      selftests/core: remove ARRAY_SIZE define from close_range_test.c
      selftests/cgroup: remove ARRAY_SIZE define from cgroup_util.h
      selftests/arm64: remove ARRAY_SIZE define from vec-syscfg.c
      tools: fix ARRAY_SIZE defines in tools and selftests hdrs
      selftests: cgroup: build error multiple outpt files
      selftests/move_mount_set_group remove unneeded conversion to bool
      selftests/mount: remove unneeded conversion to bool
      selftests: harness: avoid false negatives if test has no ASSERTs
      selftests/ftrace: make kprobe profile testcase description unique
      selftests: clone3: clone3: add case CLONE3_ARGS_NO_TEST
      selftests: timers: Remove unneeded semicolon
      kselftests: timers:Remove unneeded semicolon

commit ca1a46d6f5064c129f7ca6bcfd8f035d69da175c
Merge: d93aebbd76a07 9d6c59c1c0d62
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:58:12 2022 -0800

    Merge tag 'slab-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab
    
    Pull slab updates from Vlastimil Babka:
    
     - Separate struct slab from struct page - an offshot of the page folio
       work.
    
       Struct page fields used by slab allocators are moved from struct page
       to a new struct slab, that uses the same physical storage. Similar to
       struct folio, it always is a head page. This brings better type
       safety, separation of large kmalloc allocations from true slabs, and
       cleanup of related objcg code.
    
     - A SLAB_MERGE_DEFAULT config optimization.
    
    * tag 'slab-for-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab: (33 commits)
      mm/slob: Remove unnecessary page_mapcount_reset() function call
      bootmem: Use page->index instead of page->freelist
      zsmalloc: Stop using slab fields in struct page
      mm/slub: Define struct slab fields for CONFIG_SLUB_CPU_PARTIAL only when enabled
      mm/slub: Simplify struct slab slabs field definition
      mm/sl*b: Differentiate struct slab fields by sl*b implementations
      mm/kfence: Convert kfence_guarded_alloc() to struct slab
      mm/kasan: Convert to struct folio and struct slab
      mm/slob: Convert SLOB to use struct slab and struct folio
      mm/memcg: Convert slab objcgs from struct page to struct slab
      mm: Convert struct page to struct slab in functions used by other subsystems
      mm/slab: Finish struct page to struct slab conversion
      mm/slab: Convert most struct page to struct slab by spatch
      mm/slab: Convert kmem_getpages() and kmem_freepages() to struct slab
      mm/slub: Finish struct page to struct slab conversion
      mm/slub: Convert most struct page to struct slab by spatch
      mm/slub: Convert pfmemalloc_match() to take a struct slab
      mm/slub: Convert __free_slab() to use struct slab
      mm/slub: Convert alloc_slab_page() to return a struct slab
      mm/slub: Convert print_page_info() to print_slab_info()
      ...

commit d93aebbd76a07a8101d2f7393dc18be3e235f11b
Merge: 9d3a1e0a88e76 6c8e11e08a5b7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:52:16 2022 -0800

    Merge branch 'random-5.17-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random
    
    Pull random number generator updates from Jason Donenfeld:
     "These a bit more numerous than usual for the RNG, due to folks
      resubmitting patches that had been pending prior and generally renewed
      interest.
    
      There are a few categories of patches in here:
    
       1) Dominik Brodowski and I traded a series back and forth for a some
          weeks that fixed numerous issues related to seeds being provided
          at extremely early boot by the firmware, before other parts of the
          kernel or of the RNG have been initialized, both fixing some
          crashes and addressing correctness around early boot randomness.
          One of these is marked for stable.
    
       2) I replaced the RNG's usage of SHA-1 with BLAKE2s in the entropy
          extractor, and made the construction a bit safer and more
          standard. This was sort of a long overdue low hanging fruit, as we
          were supposed to have phased out SHA-1 usage quite some time ago
          (even if all we needed here was non-invertibility). Along the way
          it also made extraction 131% faster. This required a bit of
          Kconfig and symbol plumbing to make things work well with the
          crypto libraries, which is one of the reasons why I'm sending you
          this pull early in the cycle.
    
       3) I got rid of a truly superfluous call to RDRAND in the hot path,
          which resulted in a whopping 370% increase in performance.
    
       4) Sebastian Andrzej Siewior sent some patches regarding PREEMPT_RT,
          the full series of which wasn't ready yet, but the first two
          preparatory cleanups were good on their own. One of them touches
          files in kernel/irq/, which is the other reason why I'm sending
          you this pull early in the cycle.
    
       5) Other assorted correctness fixes from Eric Biggers, Jann Horn,
          Mark Brown, Dominik Brodowski, and myself"
    
    * 'random-5.17-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/crng/random:
      random: don't reset crng_init_cnt on urandom_read()
      random: avoid superfluous call to RDRAND in CRNG extraction
      random: early initialization of ChaCha constants
      random: use IS_ENABLED(CONFIG_NUMA) instead of ifdefs
      random: harmonize "crng init done" messages
      random: mix bootloader randomness into pool
      random: do not throw away excess input to crng_fast_load
      random: do not re-init if crng_reseed completes before primary init
      random: fix crash on multiple early calls to add_bootloader_randomness()
      random: do not sign extend bytes for rotation when mixing
      random: use BLAKE2s instead of SHA1 in extraction
      lib/crypto: blake2s: include as built-in
      random: fix data race on crng init time
      random: fix data race on crng_node_pool
      irq: remove unused flags argument from __handle_irq_event_percpu()
      random: remove unused irq_flags argument from add_interrupt_randomness()
      random: document add_hwgenerator_randomness() with other input functions
      MAINTAINERS: add git tree for random.c

commit 9d3a1e0a88e76bcb914e269cba0bfed6f4584a5e
Merge: 404dbad38248f 1e6d69c7b9cd7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:50:57 2022 -0800

    Merge tag 'seccomp-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
    
    Pull seccomp updates from Kees Cook:
     "The core seccomp code hasn't changed for this cycle, but the selftests
      were improved while helping to debug the recent signal handling
      refactoring work Eric did.
    
      Summary:
    
       - Improve seccomp selftests in support of signal handler refactoring
         (Kees Cook)"
    
    * tag 'seccomp-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
      selftests/seccomp: Report event mismatches more clearly
      selftests/seccomp: Stop USER_NOTIF test if kcmp() fails

commit 404dbad38248fc07b721f4201318418ce94fcb02
Merge: ff8be964208e6 a5d05b07961a2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:48:37 2022 -0800

    Merge tag 'pstore-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
    
    Pull pstore update from Kees Cook:
    
     - Add boot param for early ftrace recording in pstore (Uwe
       Kleine-König)
    
    * tag 'pstore-v5.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux:
      pstore/ftrace: Allow immediate recording

commit ff8be964208e6b6f1341f0645857c67830a78379
Merge: 7e740ae635040 da0119a9123c7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:45:23 2022 -0800

    Merge tag 'edac_updates_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras
    
    Pull EDAC updates from Borislav Petkov:
    
     - Add support for version 3 of the Synopsys DDR controller to
       synopsys_edac
    
     - Add support for DRR5 and new models 0x10-0x1f and 0x50-0x5f of AMD
       family 0x19 CPUs to amd64_edac
    
     - The usual set of fixes and cleanups
    
    * tag 'edac_updates_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras:
      EDAC/amd64: Add support for family 19h, models 50h-5fh
      EDAC/sb_edac: Remove redundant initialization of variable rc
      RAS/CEC: Remove a repeated 'an' in a comment
      EDAC/amd64: Add support for AMD Family 19h Models 10h-1Fh and A0h-AFh
      EDAC: Add RDDR5 and LRDDR5 memory types
      EDAC/sifive: Fix non-kernel-doc comment
      dt-bindings: memory: Add entry for version 3.80a
      EDAC/synopsys: Enable the driver on Intel's N5X platform
      EDAC/synopsys: Add support for version 3 of the Synopsys EDAC DDR
      EDAC/synopsys: Use the quirk for version instead of ddr version

commit 7e740ae6350407d68d2069ce79a6344bf1b58fe1
Merge: 48a60bdb2be80 3376136300a00
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:43:09 2022 -0800

    Merge tag 'ras_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull RAS updates from Borislav Petkov:
     "A relatively big amount of movements in RAS-land this time around:
    
       - First part of a series to move the AMD address translation code
         from arch/x86/ to amd64_edac as that is its only user anyway
    
       - Some MCE error injection improvements to the AMD side
    
       - Reorganization of the #MC handler code and the facilities it calls
         to make it noinstr-safe
    
       - Add support for new AMD MCA bank types and non-uniform banks layout
    
       - The usual set of cleanups and fixes"
    
    * tag 'ras_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (24 commits)
      x86/mce: Reduce number of machine checks taken during recovery
      x86/mce/inject: Avoid out-of-bounds write when setting flags
      x86/MCE/AMD, EDAC/mce_amd: Support non-uniform MCA bank type enumeration
      x86/MCE/AMD, EDAC/mce_amd: Add new SMCA bank types
      x86/mce: Check regs before accessing it
      x86/mce: Mark mce_start() noinstr
      x86/mce: Mark mce_timed_out() noinstr
      x86/mce: Move the tainting outside of the noinstr region
      x86/mce: Mark mce_read_aux() noinstr
      x86/mce: Mark mce_end() noinstr
      x86/mce: Mark mce_panic() noinstr
      x86/mce: Prevent severity computation from being instrumented
      x86/mce: Allow instrumentation during task work queueing
      x86/mce: Remove noinstr annotation from mce_setup()
      x86/mce: Use mce_rdmsrl() in severity checking code
      x86/mce: Remove function-local cpus variables
      x86/mce: Do not use memset to clear the banks bitmaps
      x86/mce/inject: Set the valid bit in MCA_STATUS before error injection
      x86/mce/inject: Check if a bank is populated before injecting
      x86/mce: Get rid of cpu_missing
      ...

commit 48a60bdb2be807767eba6878fdf2fe5bea5d8d27
Merge: 5ba13c1c4d848 985faa78687de
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:34:10 2022 -0800

    Merge tag 'core_entry_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull thread_info flag accessor helper updates from Borislav Petkov:
     "Add a set of thread_info.flags accessors which snapshot it before
      accesing it in order to prevent any potential data races, and convert
      all users to those new accessors"
    
    * tag 'core_entry_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      powerpc: Snapshot thread flags
      powerpc: Avoid discarding flags in system_call_exception()
      openrisc: Snapshot thread flags
      microblaze: Snapshot thread flags
      arm64: Snapshot thread flags
      ARM: Snapshot thread flags
      alpha: Snapshot thread flags
      sched: Snapshot thread flags
      entry: Snapshot thread flags
      x86: Snapshot thread flags
      thread_info: Add helpers to snapshot thread flags

commit 5ba13c1c4d848870ed4d25e411ac567c473686f0
Merge: 133d9c53c9dcb 5abb065dca730
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 11:32:57 2022 -0800

    Merge tag 'core_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull notifier fix from Borislav Petkov:
     "Return an error when a notifier callback has been registered already"
    
    * tag 'core_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      notifier: Return an error when a callback has already been registered

commit d5962fb7d69073bf68fb647531cfd4f0adf84be3
Author: Dario Petrillo <dario.pk1@gmail.com>
Date:   Mon Jan 10 00:44:41 2022 +0100

    perf annotate: Avoid TUI crash when navigating in the annotation of recursive functions
    
    In 'perf report', entering a recursive function from inside of itself
    (either directly of indirectly through some other function) results in
    calling symbol__annotate2 multiple() times, and freeing the whole
    disassembly when exiting from the innermost instance.
    
    The first issue causes the function's disassembly to be duplicated, and
    the latter a heap use-after-free (and crash) when trying to access the
    disassembly again.
    
    I reproduced the bug on perf 5.11.22 (Ubuntu 20.04.3 LTS) and 5.16.rc8
    with the following testcase (compile with gcc recursive.c -o recursive).
    To reproduce:
    
    - perf record ./recursive
    - perf report
    - enter fibonacci and annotate it
    - move the cursor on one of the "callq fibonacci" instructions and press enter
      - at this point there will be two copies of the function in the disassembly
    - go back by pressing q, and perf will crash
    
      #include <stdio.h>
    
      int fibonacci(int n)
      {
          if(n <= 2) return 1;
          return fibonacci(n-1) + fibonacci(n-2);
      }
    
      int main()
      {
          printf("%d\n", fibonacci(40));
      }
    
    This patch addresses the issue by annotating a function and freeing the
    associated memory on exit only if no annotation is already present, so
    that a recursive function is only annotated on entry.
    
    Signed-off-by: Dario Petrillo <dario.pk1@gmail.com>
    Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
    Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
    Cc: Jiri Olsa <jolsa@redhat.com>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Namhyung Kim <namhyung@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: stable@kernel.org
    Link: http://lore.kernel.org/lkml/20220109234441.325106-1-dario.pk1@gmail.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 136dff3a6b71dc16c30b35cc390feb0bfc32ed50
Author: Yufan Chen <wiz.chen@gmail.com>
Date:   Sun Jan 9 11:34:16 2022 +0900

    ksmbd: add smb-direct shutdown
    
    When killing ksmbd server after connecting rdma, ksmbd threads does not
    terminate properly because the rdma connection is still alive.
    This patch add shutdown operation to disconnect rdma connection while
    ksmbd threads terminate.
    
    Signed-off-by: Yufan Chen <wiz.chen@gmail.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 4d02c4fdc0e256b493f9a3b604c7ff18f0019f17
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Fri Jan 7 14:45:31 2022 +0900

    ksmbd: smbd: change the default maximum read/write, receive size
    
    Due to restriction that cannot handle multiple
    buffer descriptor structures, decrease the maximum
    read/write size for Windows clients.
    
    And set the maximum fragmented receive size
    in consideration of the receive queue size.
    
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit c9f189271cff85d5d735e25dfa4bc95952ec12d8
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Fri Jan 7 14:45:30 2022 +0900

    ksmbd: smbd: create MR pool
    
    Create a memory region pool because rdma_rw_ctx_init()
    uses memory registration if memory registration yields
    better performance than using multiple SGE entries.
    
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 41dbda16a0902798e732abc6599de256b9dc3b27
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Thu Jan 6 10:30:31 2022 +0900

    ksmbd: add reserved room in ipc request/response
    
    Whenever new parameter is added to smb configuration, It is possible
    to break the execution of the IPC daemon by mismatch size of
    request/response. This patch tries to reserve space in ipc request/response
    in advance to prevent that.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 99b7650ac51847e81b4d5139824e321e6cb76130
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Tue Jan 4 14:56:26 2022 +0900

    ksmbd: smbd: call rdma_accept() under CM handler
    
    if CONFIG_LOCKDEP is enabled, the following
    kernel warning message is generated because
    rdma_accept() checks whehter the handler_mutex
    is held by lockdep_assert_held. CM(Connection
    Manager) holds the mutex before CM handler
    callback is called.
    
    [   63.211405 ] WARNING: CPU: 1 PID: 345 at drivers/infiniband/core/cma.c:4405 rdma_accept+0x17a/0x350
    [   63.212080 ] RIP: 0010:rdma_accept+0x17a/0x350
    ...
    [   63.214036 ] Call Trace:
    [   63.214098 ]  <TASK>
    [   63.214185 ]  smb_direct_accept_client+0xb4/0x170 [ksmbd]
    [   63.214412 ]  smb_direct_prepare+0x322/0x8c0 [ksmbd]
    [   63.214555 ]  ? rcu_read_lock_sched_held+0x3a/0x70
    [   63.214700 ]  ksmbd_conn_handler_loop+0x63/0x270 [ksmbd]
    [   63.214826 ]  ? ksmbd_conn_alive+0x80/0x80 [ksmbd]
    [   63.214952 ]  kthread+0x171/0x1a0
    [   63.215039 ]  ? set_kthread_struct+0x40/0x40
    [   63.215128 ]  ret_from_fork+0x22/0x30
    
    To avoid this, move creating a queue pair and accepting
    a client from transport_ops->prepare() to
    smb_direct_handle_connect_request().
    
    Acked-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit b589f5db6d4af8f14d70e31e1276b4c017668a26
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Fri Dec 31 09:26:25 2021 +0900

    ksmbd: limits exceeding the maximum allowable outstanding requests
    
    If the client ignores the CreditResponse received from the server and
    continues to send the request, ksmbd limits the requests if it exceeds
    smb2 max credits.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 914d7e5709ac59ded70bea7956d408fe2acd7c3c
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Wed Dec 29 23:10:03 2021 +0900

    ksmbd: move credit charge deduction under processing request
    
    Moves the credit charge deduction from total_credits under the processing
    a request. When repeating smb2 lock request and other command request,
    there will be a problem that ->total_credits does not decrease.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 004443b3f6d722b455cf963ed7c3edd7f4772405
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Wed Dec 29 23:08:46 2021 +0900

    ksmbd: add support for smb2 max credit parameter
    
    Add smb2 max credits parameter to adjust maximum credits value to limit
    number of outstanding requests.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit cb097b3dd5ece9596a0a0b7e33893c02a9bde8c6
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Wed Dec 29 23:02:50 2021 +0900

    ksmbd: set 445 port to smbdirect port by default
    
    When SMB Direct is used with iWARP, Windows use 5445 port for smb direct
    port, 445 port for SMB. This patch check ib_device using ib_client to
    know if NICs type is iWARP or Infiniband.
    
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 31928a001bed0d9642711d2eba520fc46d41c376
Author: Hyunchul Lee <hyc.lee@gmail.com>
Date:   Wed Dec 29 23:02:15 2021 +0900

    ksmbd: register ksmbd ib client with ib_register_client()
    
    Register ksmbd ib client with ib_register_client() to find the rdma capable
    network adapter. If ops.get_netdev(Chelsio NICs) is NULL, ksmbd will find
    it using ib_device_get_by_netdev in old way.
    
    Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit befee3775b6dabd7ec1bd8a44584f7f6f8fc8329
Author: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Date:   Fri Dec 3 07:50:38 2021 +0530

    perf powerpc: Update global/local variants for p_stage_cyc
    
    Update the arch_support_sort_key() function in powerpc to enable
    presenting local and global variants of sort key 'p_stage_cyc'.
    
    Update the "se_header" strings for these in arch_perf_header_entry()
    along with instruction latency.
    
    Reported-by: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
    Tested-by: Nageswara R Sastry <rnsastry@linux.ibm.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: linuxppc-dev@lists.ozlabs.org
    Link: https://lore.kernel.org/r/20211203022038.48240-2-atrajeev@linux.vnet.ibm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit e3304c21357268ecbe156ed6247a03dc78d3fce4
Author: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Date:   Fri Dec 3 07:50:37 2021 +0530

    perf sort: Include global and local variants for p_stage_cyc sort key
    
    Sort key 'p_stage_cyc' is used to present the latency cycles spent in
    pipeline stages.
    
    perf has local 'p_stage_cyc' sort key to display this info. There is no
    global variant available for this sort key. The local variant shows
    latency in a single sample, whereas the global value will be useful to
    present the total latency (sum of latencies) in the hist entry. It
    represents the latency number multiplied by the number of samples.
    
    Add global ('p_stage_cyc') and local variant ('local_p_stage_cyc') for
    this sort key. Use 'local_p_stage_cyc' as default option for "mem" sort
    mode.
    
    Also add this to the list of dynamic sort keys and made the
    "dynamic_headers" and "arch_specific_sort_keys" as static.
    
    Reported-by: Namhyung Kim <namhyung@kernel.org>
    Signed-off-by: Athira Jajeev <atrajeev@linux.vnet.ibm.com>
    Tested-by: Nageswara R Sastry <rnsastry@linux.ibm.com>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Kajol Jain <kjain@linux.ibm.com>
    Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: linuxppc-dev@lists.ozlabs.org
    Link: https://lore.kernel.org/r/20211203022038.48240-1-atrajeev@linux.vnet.ibm.com
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit debe70e488968e82282db48fbbcf84b5080f742c
Merge: 65f8d08cf838d 133d9c53c9dcb
Author: Arnaldo Carvalho de Melo <acme@redhat.com>
Date:   Mon Jan 10 15:35:41 2022 -0300

    Merge remote-tracking branch 'torvalds/master' into perf/core
    
    To pick up fixes.
    
    Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>

commit 6eeaf88fd586f05aaf1d48cb3a139d2a5c6eb055
Author: Theodore Ts'o <tytso@mit.edu>
Date:   Wed Jan 5 23:59:56 2022 -0500

    ext4: don't use the orphan list when migrating an inode
    
    We probably want to remove the indirect block to extents migration
    feature after a deprecation window, but until then, let's fix a
    potential data loss problem caused by the fact that we put the
    tmp_inode on the orphan list.  In the unlikely case where we crash and
    do a journal recovery, the data blocks belonging to the inode being
    migrated are also represented in the tmp_inode on the orphan list ---
    and so its data blocks will get marked unallocated, and available for
    reuse.
    
    Instead, stop putting the tmp_inode on the oprhan list.  So in the
    case where we crash while migrating the inode, we'll leak an inode,
    which is not a disaster.  It will be easily fixed the next time we run
    fsck, and it's better than potentially having blocks getting claimed
    by two different files, and losing data as a result.
    
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Reviewed-by: Lukas Czerner <lczerner@redhat.com>
    Cc: stable@kernel.org

commit a2e3965df40af2f48ee6c97ed573adb91ced5dac
Author: xu xin <xu.xin16@zte.com.cn>
Date:   Tue Dec 28 07:32:52 2021 +0000

    ext4: use BUG_ON instead of if condition followed by BUG
    
    BUG_ON would be better.
    
    This issue was detected with the help of Coccinelle.
    
    Reported-by: Zeal robot <zealci@zte.com.cn>
    Reviewed-by: Lukas Czerner <lczerner@redhat.com>
    Signed-off-by: xu xin <xu.xin16@zte.com.cn>
    Link: https://lore.kernel.org/r/20211228073252.580296-1-xu.xin16@zte.com.cn
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit da9e480212582b336b97848c69fdd4ac8860065b
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Wed Dec 15 14:43:09 2021 +0300

    ext4: fix a copy and paste typo
    
    This was obviously supposed to be an ext4 struct, not xfs.  GCC
    doesn't care either way so it doesn't affect the build or runtime.
    
    Fixes: cebe85d570cf ("ext4: switch to the new mount api")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Reviewed-by: Lukas Czerner <lczerner@redhat.com>
    Link: https://lore.kernel.org/r/20211215114309.GB14552@kili
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit e81c9302a6c3c008f5c30beb73b38adb0170ff2d
Author: Luís Henriques <lhenriques@suse.de>
Date:   Tue Dec 14 17:50:58 2021 +0000

    ext4: set csum seed in tmp inode while migrating to extents
    
    When migrating to extents, the temporary inode will have it's own checksum
    seed.  This means that, when swapping the inodes data, the inode checksums
    will be incorrect.
    
    This can be fixed by recalculating the extents checksums again.  Or simply
    by copying the seed into the temporary inode.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=213357
    Reported-by: Jeroen van Wolffelaar <jeroen@wolffelaar.nl>
    Signed-off-by: Luís Henriques <lhenriques@suse.de>
    Link: https://lore.kernel.org/r/20211214175058.19511-1-lhenriques@suse.de
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit ae6ec194b55273e52351ee70d694594dcabe405d
Author: luo penghao <luo.penghao@zte.com.cn>
Date:   Wed Dec 8 07:53:07 2021 +0000

    ext4: remove unnecessary 'offset' assignment
    
    Although it is in the loop, offset is reassigned at the beginning of the
    while loop.  And after the loop, the value will not be used
    
    The clang_analyzer complains as follows:
    
    fs/ext4/dir.c:306:3 warning:
    
    Value stored to 'offset' is never read
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
    Link: https://lore.kernel.org/r/20211208075307.404703-1-luo.penghao@zte.com.cn
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit a6dbc76c4d9cc961bfb31a495fb27ee06e037e35
Author: luo penghao <luo.penghao@zte.com.cn>
Date:   Wed Dec 8 07:51:57 2021 +0000

    ext4: remove redundant o_start statement
    
    The if will goto out of the loop, and until the end of the
    function execution, o_start will not be used again.
    
    The clang_analyzer complains as follows:
    
    fs/ext4/move_extent.c:635:5 warning:
    
    Value stored to 'o_start' is never read
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
    Link: https://lore.kernel.org/r/20211208075157.404535-1-luo.penghao@zte.com.cn
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 037e7c525d988867811b3613549971a3253b2f7b
Author: Adam Borowski <kilobyte@angband.pl>
Date:   Mon Nov 15 18:20:20 2021 +0100

    ext4: drop an always true check
    
    EXT_FIRST_INDEX(ptr) is ptr+12, which can't possibly be null; gcc-12
    warns about this.
    
    Signed-off-by: Adam Borowski <kilobyte@angband.pl>
    Reviewed-by: Andreas Dilger <adilger@dilger.ca>
    Link: https://lore.kernel.org/r/20211115172020.57853-1-kilobyte@angband.pl
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit fac888b2be9993d0c740013d26d69c8784acc293
Author: luo penghao <luo.penghao@zte.com.cn>
Date:   Thu Nov 4 06:40:07 2021 +0000

    ext4: remove unused assignments
    
    The eh assignment in these two places is meaningless, because the
    function will goto to merge, which will not use eh.
    
    The clang_analyzer complains as follows:
    
    fs/ext4/extents.c:1988:4 warning:
    fs/ext4/extents.c:2016:4 warning:
    
    Value stored to 'eh' is never read
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
    Link: https://lore.kernel.org/r/20211104064007.2919-1-luo.penghao@zte.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit a660be97eb00c4d87bf881e1226fbd9d812690b7
Author: luo penghao <luo.penghao@zte.com.cn>
Date:   Thu Nov 4 06:34:06 2021 +0000

    ext4: remove redundant statement
    
    The local variable assignment at the end of the function is meaningless.
    
    The clang_analyzer complains as follows:
    
    fs/ext4/fast_commit.c:779:2 warning:
    
    Value stored to 'dst' is never read
    
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
    Link: https://lore.kernel.org/r/20211104063406.2747-1-luo.penghao@zte.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit effc5b3b0d20ffcb692f107cd347289bfcd6890b
Author: Nghia Le <nghialm78@gmail.com>
Date:   Tue Oct 26 05:18:03 2021 +0700

    ext4: remove useless resetting io_end_size in mpage_process_page()
    
    The command "make clang-analyzer" detects dead stores in
    mpage_process_page() function.
    
    Do not reset io_end_size to 0 in the current paths, as the function
    exits on those paths without further using io_end_size.
    
    Signed-off-by: Nghia Le <nghialm78@gmail.com>
    Link: https://lore.kernel.org/r/20211025221803.3326-1-nghialm78@gmail.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 4a69aecbfb30a3fc85bf8028386c047d5607a97a
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Wed Nov 3 15:51:22 2021 +0100

    ext4: allow to change s_last_trim_minblks via sysfs
    
    Ext4 has an optimization mechanism for batched disacrd (FITRIM) that
    should help speed up subsequent calls of FITRIM ioctl by skipping the
    groups that were previously trimmed. However because the FITRIM allows
    to set the minimum size of an extent to trim, ext4 stores the last
    minimum extent size and only avoids trimming the group if it was
    previously trimmed with minimum extent size equal to, or smaller than
    the current call.
    
    There is currently no way to bypass the optimization without
    umount/mount cycle. This becomes a problem when the file system is
    live migrated to a different storage, because the optimization will
    prevent possibly useful discard calls to the storage.
    
    Fix it by exporting the s_last_trim_minblks via sysfs interface which
    will allow us to set the minimum size to the number of blocks larger
    than subsequent FITRIM call, effectively bypassing the optimization.
    
    By setting the s_last_trim_minblks to ULONG_MAX the optimization will be
    effectively cleared regardless of the previous state, or file system
    configuration.
    
    For example:
    getconf ULONG_MAX > /sys/fs/ext4/dm-1/last_trim_minblks
    
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Reported-by: Laurent GUERBY <laurent@guerby.net>
    Reviewed-by: Andreas Dilger <adilger@dilger.ca>
    Link: https://lore.kernel.org/r/20211103145122.17338-2-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 2327fb2e23416cfb2795ccca2f77d4d65925be99
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Wed Nov 3 15:51:21 2021 +0100

    ext4: change s_last_trim_minblks type to unsigned long
    
    There is no good reason for the s_last_trim_minblks to be atomic. There is
    no data integrity needed and there is no real danger in setting and
    reading it in a racy manner. Change it to be unsigned long, the same type
    as s_clusters_per_group which is the maximum that's allowed.
    
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Suggested-by: Andreas Dilger <adilger@dilger.ca>
    Reviewed-by: Andreas Dilger <adilger@dilger.ca>
    Link: https://lore.kernel.org/r/20211103145122.17338-1-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit bbc605cdb1e15aafaec899fedc385dc75dddac0e
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Mon Dec 13 14:56:18 2021 +0100

    ext4: implement support for get/set fs label
    
    Implement support for FS_IOC_GETFSLABEL and FS_IOC_SETFSLABEL ioctls for
    online reading and setting of file system label.
    
    ext4_ioctl_getlabel() is simple, just get the label from the primary
    superblock. This might not be the first sb on the file system if
    'sb=' mount option is used.
    
    In ext4_ioctl_setlabel() we update what ext4 currently views as a
    primary superblock and then proceed to update backup superblocks. There
    are two caveats:
     - the primary superblock might not be the first superblock and so it
       might not be the one used by userspace tools if read directly
       off the disk.
     - because the primary superblock might not be the first superblock we
       potentialy have to update it as part of backup superblock update.
       However the first sb location is a bit more complicated than the rest
       so we have to account for that.
    
    The superblock modification is created generic enough so the
    infrastructure can be used for other potential superblock modification
    operations, such as chaning UUID.
    
    Tested with generic/492 with various configurations. I also checked the
    behavior with 'sb=' mount options, including very large file systems
    with and without sparse_super/sparse_super2.
    
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Link: https://lore.kernel.org/r/20211213135618.43303-1-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 4c1bd5a90c4e716e5bde33f01a40bb66dc4a9903
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Tue Jan 4 15:35:18 2022 +0100

    ext4: only set EXT4_MOUNT_QUOTA when journalled quota file is specified
    
    Only set EXT4_MOUNT_QUOTA when journalled quota file is specified,
    otherwise simply disabling specific quota type (usrjquota=) will also
    set the EXT4_MOUNT_QUOTA super block option.
    
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Fixes: e6e268cb6822 ("ext4: move quota configuration out of handle_mount_opt()")
    Link: https://lore.kernel.org/r/20220104143518.134465-2-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 13b215a9e657808414a2159b0dec90f1c31ebe05
Author: Lukas Czerner <lczerner@redhat.com>
Date:   Tue Jan 4 15:35:17 2022 +0100

    ext4: don't use kfree() on rcu protected pointer sbi->s_qf_names
    
    During ext4 mount api rework the commit e6e268cb6822 ("ext4: move quota
    configuration out of handle_mount_opt()") introduced a bug where we
    would kfree(sbi->s_qf_names[i]) before assigning the new quota name in
    ext4_apply_quota_options().
    
    This is wrong because we're using kfree() on rcu prointer that could be
    simultaneously accessed from ext4_show_quota_options() during remount.
    Fix it by using rcu_replace_pointer() to replace the old qname with the
    new one and then kfree_rcu() the old quota name.
    
    Also use get_qf_name() instead of sbi->s_qf_names in strcmp() to silence
    the sparse warning.
    
    Fixes: e6e268cb6822 ("ext4: move quota configuration out of handle_mount_opt()")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Lukas Czerner <lczerner@redhat.com>
    Link: https://lore.kernel.org/r/20220104143518.134465-1-lczerner@redhat.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 173b6e383d2a204c9921ffc1eca3b87aa2106c33
Author: Jan Kara <jack@suse.cz>
Date:   Fri Nov 12 16:22:02 2021 +0100

    ext4: avoid trim error on fs with small groups
    
    A user reported FITRIM ioctl failing for him on ext4 on some devices
    without apparent reason.  After some debugging we've found out that
    these devices (being LVM volumes) report rather large discard
    granularity of 42MB and the filesystem had 1k blocksize and thus group
    size of 8MB. Because ext4 FITRIM implementation puts discard
    granularity into minlen, ext4_trim_fs() declared the trim request as
    invalid. However just silently doing nothing seems to be a more
    appropriate reaction to such combination of parameters since user did
    not specify anything wrong.
    
    CC: Lukas Czerner <lczerner@redhat.com>
    Fixes: 5c2ed62fd447 ("ext4: Adjust minlen with discard_granularity in the FITRIM ioctl")
    Signed-off-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/20211112152202.26614-1-jack@suse.cz
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 5c48a7df91499e371ef725895b2e2d21a126e227
Author: Zhang Yi <yi.zhang@huawei.com>
Date:   Sat Dec 25 17:09:37 2021 +0800

    ext4: fix an use-after-free issue about data=journal writeback mode
    
    Our syzkaller report an use-after-free issue that accessing the freed
    buffer_head on the writeback page in __ext4_journalled_writepage(). The
    problem is that if there was a truncate racing with the data=journalled
    writeback procedure, the writeback length could become zero and
    bget_one() refuse to get buffer_head's refcount, then the truncate
    procedure release buffer once we drop page lock, finally, the last
    ext4_walk_page_buffers() trigger the use-after-free problem.
    
    sync                               truncate
    ext4_sync_file()
     file_write_and_wait_range()
                                       ext4_setattr(0)
                                        inode->i_size = 0
      ext4_writepage()
       len = 0
       __ext4_journalled_writepage()
        page_bufs = page_buffers(page)
        ext4_walk_page_buffers(bget_one) <- does not get refcount
                                        do_invalidatepage()
                                          free_buffer_head()
        ext4_walk_page_buffers(page_bufs) <- trigger use-after-free
    
    After commit bdf96838aea6 ("ext4: fix race between truncate and
    __ext4_journalled_writepage()"), we have already handled the racing
    case, so the bget_one() and bput_one() are not needed. So this patch
    simply remove these hunk, and recheck the i_size to make it safe.
    
    Fixes: bdf96838aea6 ("ext4: fix race between truncate and __ext4_journalled_writepage()")
    Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
    Cc: stable@vger.kernel.org
    Link: https://lore.kernel.org/r/20211225090937.712867-1-yi.zhang@huawei.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 298b5c521746d69c07beb2757292fb5ccc1b0f85
Author: Ye Bin <yebin10@huawei.com>
Date:   Fri Dec 24 18:03:41 2021 +0800

    ext4: fix null-ptr-deref in '__ext4_journal_ensure_credits'
    
    We got issue as follows when run syzkaller test:
    [ 1901.130043] EXT4-fs error (device vda): ext4_remount:5624: comm syz-executor.5: Abort forced by user
    [ 1901.130901] Aborting journal on device vda-8.
    [ 1901.131437] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.16: Detected aborted journal
    [ 1901.131566] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.11: Detected aborted journal
    [ 1901.132586] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.18: Detected aborted journal
    [ 1901.132751] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.9: Detected aborted journal
    [ 1901.136149] EXT4-fs error (device vda) in ext4_reserve_inode_write:6035: Journal has aborted
    [ 1901.136837] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-fuzzer: Detected aborted journal
    [ 1901.136915] ==================================================================
    [ 1901.138175] BUG: KASAN: null-ptr-deref in __ext4_journal_ensure_credits+0x74/0x140 [ext4]
    [ 1901.138343] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.13: Detected aborted journal
    [ 1901.138398] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.1: Detected aborted journal
    [ 1901.138808] Read of size 8 at addr 0000000000000000 by task syz-executor.17/968
    [ 1901.138817]
    [ 1901.138852] EXT4-fs error (device vda): ext4_journal_check_start:61: comm syz-executor.30: Detected aborted journal
    [ 1901.144779] CPU: 1 PID: 968 Comm: syz-executor.17 Not tainted 4.19.90-vhulk2111.1.0.h893.eulerosv2r10.aarch64+ #1
    [ 1901.146479] Hardware name: linux,dummy-virt (DT)
    [ 1901.147317] Call trace:
    [ 1901.147552]  dump_backtrace+0x0/0x2d8
    [ 1901.147898]  show_stack+0x28/0x38
    [ 1901.148215]  dump_stack+0xec/0x15c
    [ 1901.148746]  kasan_report+0x108/0x338
    [ 1901.149207]  __asan_load8+0x58/0xb0
    [ 1901.149753]  __ext4_journal_ensure_credits+0x74/0x140 [ext4]
    [ 1901.150579]  ext4_xattr_delete_inode+0xe4/0x700 [ext4]
    [ 1901.151316]  ext4_evict_inode+0x524/0xba8 [ext4]
    [ 1901.151985]  evict+0x1a4/0x378
    [ 1901.152353]  iput+0x310/0x428
    [ 1901.152733]  do_unlinkat+0x260/0x428
    [ 1901.153056]  __arm64_sys_unlinkat+0x6c/0xc0
    [ 1901.153455]  el0_svc_common+0xc8/0x320
    [ 1901.153799]  el0_svc_handler+0xf8/0x160
    [ 1901.154265]  el0_svc+0x10/0x218
    [ 1901.154682] ==================================================================
    
    This issue may happens like this:
            Process1                               Process2
    ext4_evict_inode
      ext4_journal_start
       ext4_truncate
         ext4_ind_truncate
           ext4_free_branches
             ext4_ind_truncate_ensure_credits
               ext4_journal_ensure_credits_fn
                 ext4_journal_restart
                   handle->h_transaction = NULL;
                                               mount -o remount,abort  /mnt
                                               -> trigger JBD abort
                   start_this_handle -> will return failed
      ext4_xattr_delete_inode
        ext4_journal_ensure_credits
          ext4_journal_ensure_credits_fn
            __ext4_journal_ensure_credits
              jbd2_handle_buffer_credits
                journal = handle->h_transaction->t_journal; ->null-ptr-deref
    
    Now, indirect truncate process didn't handle error. To solve this issue
    maybe simply add check handle is abort in '__ext4_journal_ensure_credits'
    is enough, and i also think this is necessary.
    
    Cc: stable@kernel.org
    Signed-off-by: Ye Bin <yebin10@huawei.com>
    Link: https://lore.kernel.org/r/20211224100341.3299128-1-yebin10@huawei.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit c27c29c6af4f3f4ce925a2111c256733c5a5b430
Author: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
Date:   Wed Dec 1 08:34:21 2021 -0800

    ext4: initialize err_blk before calling __ext4_get_inode_loc
    
    It is not guaranteed that __ext4_get_inode_loc will definitely set
    err_blk pointer when it returns EIO. To avoid using uninitialized
    variables, let's first set err_blk to 0.
    
    Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20211201163421.2631661-1-harshads@google.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 8c80fb312d7abf8bcd66cca1d843a80318a2c522
Author: Chunguang Xu <brookxu@tencent.com>
Date:   Tue Nov 23 09:17:57 2021 +0800

    ext4: fix a possible ABBA deadlock due to busy PA
    
    We found on older kernel (3.10) that in the scenario of insufficient
    disk space, system may trigger an ABBA deadlock problem, it seems that
    this problem still exists in latest kernel, try to fix it here. The
    main process triggered by this problem is that task A occupies the PA
    and waits for the jbd2 transaction finish, the jbd2 transaction waits
    for the completion of task B's IO (plug_list), but task B waits for
    the release of PA by task A to finish discard, which indirectly forms
    an ABBA deadlock. The related calltrace is as follows:
    
        Task A
        vfs_write
        ext4_mb_new_blocks()
        ext4_mb_mark_diskspace_used()       JBD2
        jbd2_journal_get_write_access()  -> jbd2_journal_commit_transaction()
      ->schedule()                          filemap_fdatawait()
     |                                              |
     | Task B                                       |
     | do_unlinkat()                                |
     | ext4_evict_inode()                           |
     | jbd2_journal_begin_ordered_truncate()        |
     | filemap_fdatawrite_range()                   |
     | ext4_mb_new_blocks()                         |
      -ext4_mb_discard_group_preallocations() <-----
    
    Here, try to cancel ext4_mb_discard_group_preallocations() internal
    retry due to PA busy, and do a limited number of retries inside
    ext4_mb_discard_preallocations(), which can circumvent the above
    problems, but also has some advantages:
    
    1. Since the PA is in a busy state, if other groups have free PAs,
       keeping the current PA may help to reduce fragmentation.
    2. Continue to traverse forward instead of waiting for the current
       group PA to be released. In most scenarios, the PA discard time
       can be reduced.
    
    However, in the case of smaller free space, if only a few groups have
    space, then due to multiple traversals of the group, it may increase
    CPU overhead. But in contrast, I feel that the overall benefit is
    better than the cost.
    
    Signed-off-by: Chunguang Xu <brookxu@tencent.com>
    Reported-by: kernel test robot <lkp@intel.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/1637630277-23496-1-git-send-email-brookxu.cn@gmail.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit dfac1a167068d60b36cc8f2081394a28b6fc424b
Author: Qing Wang <wangqing@vivo.com>
Date:   Tue Oct 12 20:28:51 2021 -0700

    ext4: replace snprintf in show functions with sysfs_emit
    
    coccicheck complains about the use of snprintf() in sysfs show functions.
    
    Fix the coccicheck warning:
    WARNING: use scnprintf or sprintf.
    
    Use sysfs_emit instead of scnprintf or sprintf makes more sense.
    
    Signed-off-by: Qing Wang <wangqing@vivo.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/1634095731-4528-1-git-send-email-wangqing@vivo.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 4013d47a5307fdb5c13370b5392498b00fedd274
Author: Jan Kara <jack@suse.cz>
Date:   Thu Oct 7 17:53:36 2021 +0200

    ext4: make sure to reset inode lockdep class when quota enabling fails
    
    When we succeed in enabling some quota type but fail to enable another
    one with quota feature, we correctly disable all enabled quota types.
    However we forget to reset i_data_sem lockdep class. When the inode gets
    freed and reused, it will inherit this lockdep class (i_data_sem is
    initialized only when a slab is created) and thus eventually lockdep
    barfs about possible deadlocks.
    
    Reported-and-tested-by: syzbot+3b6f9218b1301ddda3e2@syzkaller.appspotmail.com
    Signed-off-by: Jan Kara <jack@suse.cz>
    Cc: stable@kernel.org
    Link: https://lore.kernel.org/r/20211007155336.12493-3-jack@suse.cz
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 15fc69bbbbbc8c72e5f6cc4e1be0f51283c5448e
Author: Jan Kara <jack@suse.cz>
Date:   Thu Oct 7 17:53:35 2021 +0200

    ext4: make sure quota gets properly shutdown on error
    
    When we hit an error when enabling quotas and setting inode flags, we do
    not properly shutdown quota subsystem despite returning error from
    Q_QUOTAON quotactl. This can lead to some odd situations like kernel
    using quota file while it is still writeable for userspace. Make sure we
    properly cleanup the quota subsystem in case of error.
    
    Signed-off-by: Jan Kara <jack@suse.cz>
    Cc: stable@kernel.org
    Link: https://lore.kernel.org/r/20211007155336.12493-2-jack@suse.cz
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>

commit 380a0091cab482489e9b19e07f2a166ad2b76d5c
Author: Ye Bin <yebin10@huawei.com>
Date:   Thu Dec 23 09:55:06 2021 +0800

    ext4: Fix BUG_ON in ext4_bread when write quota data
    
    We got issue as follows when run syzkaller:
    [  167.936972] EXT4-fs error (device loop0): __ext4_remount:6314: comm rep: Abort forced by user
    [  167.938306] EXT4-fs (loop0): Remounting filesystem read-only
    [  167.981637] Assertion failure in ext4_getblk() at fs/ext4/inode.c:847: '(EXT4_SB(inode->i_sb)->s_mount_state & EXT4_FC_REPLAY) || handle != NULL || create == 0'
    [  167.983601] ------------[ cut here ]------------
    [  167.984245] kernel BUG at fs/ext4/inode.c:847!
    [  167.984882] invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
    [  167.985624] CPU: 7 PID: 2290 Comm: rep Tainted: G    B             5.16.0-rc5-next-20211217+ #123
    [  167.986823] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014
    [  167.988590] RIP: 0010:ext4_getblk+0x17e/0x504
    [  167.989189] Code: c6 01 74 28 49 c7 c0 a0 a3 5c 9b b9 4f 03 00 00 48 c7 c2 80 9c 5c 9b 48 c7 c6 40 b6 5c 9b 48 c7 c7 20 a4 5c 9b e8 77 e3 fd ff <0f> 0b 8b 04 244
    [  167.991679] RSP: 0018:ffff8881736f7398 EFLAGS: 00010282
    [  167.992385] RAX: 0000000000000094 RBX: 1ffff1102e6dee75 RCX: 0000000000000000
    [  167.993337] RDX: 0000000000000001 RSI: ffffffff9b6e29e0 RDI: ffffed102e6dee66
    [  167.994292] RBP: ffff88816a076210 R08: 0000000000000094 R09: ffffed107363fa09
    [  167.995252] R10: ffff88839b1fd047 R11: ffffed107363fa08 R12: ffff88816a0761e8
    [  167.996205] R13: 0000000000000000 R14: 0000000000000021 R15: 0000000000000001
    [  167.997158] FS:  00007f6a1428c740(0000) GS:ffff88839b000000(0000) knlGS:0000000000000000
    [  167.998238] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  167.999025] CR2: 00007f6a140716c8 CR3: 0000000133216000 CR4: 00000000000006e0
    [  167.999987] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [  168.000944] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [  168.001899] Call Trace:
    [  168.002235]  <TASK>
    [  168.007167]  ext4_bread+0xd/0x53
    [  168.007612]  ext4_quota_write+0x20c/0x5c0
    [  168.010457]  write_blk+0x100/0x220
    [  168.010944]  remove_free_dqentry+0x1c6/0x440
    [  168.011525]  free_dqentry.isra.0+0x565/0x830
    [  168.012133]  remove_tree+0x318/0x6d0
    [  168.014744]  remove_tree+0x1eb/0x6d0
    [  168.017346]  remove_tree+0x1eb/0x6d0
    [  168.019969]  remove_tree+0x1eb/0x6d0
    [  168.022128]  qtree_release_dquot+0x291/0x340
    [  168.023297]  v2_release_dquot+0xce/0x120
    [  168.023847]  dquot_release+0x197/0x3e0
    [  168.024358]  ext4_release_dquot+0x22a/0x2d0
    [  168.024932]  dqput.part.0+0x1c9/0x900
    [  168.025430]  __dquot_drop+0x120/0x190
    [  168.025942]  ext4_clear_inode+0x86/0x220
    [  168.026472]  ext4_evict_inode+0x9e8/0xa22
    [  168.028200]  evict+0x29e/0x4f0
    [  168.028625]  dispose_list+0x102/0x1f0
    [  168.029148]  evict_inodes+0x2c1/0x3e0
    [  168.030188]  generic_shutdown_super+0xa4/0x3b0
    [  168.030817]  kill_block_super+0x95/0xd0
    [  168.031360]  deactivate_locked_super+0x85/0xd0
    [  168.031977]  cleanup_mnt+0x2bc/0x480
    [  168.033062]  task_work_run+0xd1/0x170
    [  168.033565]  do_exit+0xa4f/0x2b50
    [  168.037155]  do_group_exit+0xef/0x2d0
    [  168.037666]  __x64_sys_exit_group+0x3a/0x50
    [  168.038237]  do_syscall_64+0x3b/0x90
    [  168.038751]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    In order to reproduce this problem, the following conditions need to be met:
    1. Ext4 filesystem with no journal;
    2. Filesystem image with incorrect quota data;
    3. Abort filesystem forced by user;
    4. umount filesystem;
    
    As in ext4_quota_write:
    ...
             if (EXT4_SB(sb)->s_journal && !handle) {
                     ext4_msg(sb, KERN_WARNING, "Quota write (off=%llu, len=%llu)"
                             " cancelled because transaction is not started",
                             (unsigned long long)off, (unsigned long long)len);
                     return -EIO;
             }
    ...
    We only check handle if NULL when filesystem has journal. There is need
    check handle if NULL even when filesystem has no journal.
    
    Signed-off-by: Ye Bin <yebin10@huawei.com>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Link: https://lore.kernel.org/r/20211223015506.297766-1-yebin10@huawei.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit ab047d516dea72f011c15c04a929851e4d053109
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Thu Dec 23 17:44:36 2021 +0100

    ext4: destroy ext4_fc_dentry_cachep kmemcache on module removal
    
    The kmemcache for ext4_fc_dentry_cachep remains registered after module
    removal.
    
    Destroy ext4_fc_dentry_cachep kmemcache on module removal.
    
    Fixes: aa75f4d3daaeb ("ext4: main fast-commit commit path")
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Reviewed-by: Lukas Czerner <lczerner@redhat.com>
    Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20211110134640.lyku5vklvdndw6uk@linutronix.de
    Link: https://lore.kernel.org/r/YbiK3JetFFl08bd7@linutronix.de
    Link: https://lore.kernel.org/r/20211223164436.2628390-1-bigeasy@linutronix.de
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 9725958bb75cdfa10f2ec11526fdb23e7485e8e4
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Thu Dec 23 11:23:37 2021 +0800

    ext4: fast commit may miss tracking unwritten range during ftruncate
    
    If use FALLOC_FL_KEEP_SIZE to alloc unwritten range at bottom, the
    inode->i_size will not include the unwritten range. When call
    ftruncate with fast commit enabled, it will miss to track the
    unwritten range.
    
    Change to trace the full range during ftruncate.
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20211223032337.5198-3-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 0b5b5a62b945a141e64011b2f90ee7e46f14be98
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Thu Dec 23 11:23:36 2021 +0800

    ext4: use ext4_ext_remove_space() for fast commit replay delete range
    
    For now ,we use ext4_punch_hole() during fast commit replay delete range
    procedure. But it will be affected by inode->i_size, which may not
    correct during fast commit replay procedure. The following test will
    failed.
    
    -create & write foo (len 1000K)
    -falloc FALLOC_FL_ZERO_RANGE foo (range 400K - 600K)
    -create & fsync bar
    -falloc FALLOC_FL_PUNCH_HOLE foo (range 300K-500K)
    -fsync foo
    -crash before a full commit
    
    After the fast_commit reply procedure, the range 400K-500K will not be
    removed. Because in this case, when calling ext4_punch_hole() the
    inode->i_size is 0, and it just retruns with doing nothing.
    
    Change to use ext4_ext_remove_space() instead of ext4_punch_hole()
    to remove blocks of inode directly.
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20211223032337.5198-2-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 5e4d0eba1ccaf19f93222abdeda5a368be141785
Author: Xin Yin <yinxin.x@bytedance.com>
Date:   Tue Dec 21 10:28:39 2021 +0800

    ext4: fix fast commit may miss tracking range for FALLOC_FL_ZERO_RANGE
    
    when call falloc with FALLOC_FL_ZERO_RANGE, to set an range to unwritten,
    which has been already initialized. If the range is align to blocksize,
    fast commit will not track range for this change.
    
    Also track range for unwritten range in ext4_map_blocks().
    
    Signed-off-by: Xin Yin <yinxin.x@bytedance.com>
    Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>
    Link: https://lore.kernel.org/r/20211221022839.374606-1-yinxin.x@bytedance.com
    Signed-off-by: Theodore Ts'o <tytso@mit.edu>
    Cc: stable@kernel.org

commit 74a5257a0c175810d620b5e631c4e7554955ac25
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Jan 10 19:12:45 2022 +0100

    genirq/msi: Populate sysfs entry only once
    
    The MSI entries for multi-MSI are populated en bloc for the MSI descriptor,
    but the current code invokes the population inside the per interrupt loop
    which triggers a warning in the sysfs code and causes the interrupt
    allocation to fail.
    
    Move it outside of the loop so it works correctly for single and multi-MSI.
    
    Fixes: bf5e758f02fc ("genirq/msi: Simplify sysfs handling")
    Reported-by: Borislav Petkov <bp@alien8.de>
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Tested-by: Borislav Petkov <bp@suse.de>
    Link: https://lore.kernel.org/r/87leznqx2a.ffs@tglx

commit 133d9c53c9dcbb1b8f317e402e79c44d9eb725c9
Merge: 3c6d4056663da 9102fa3460415
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 10:20:15 2022 -0800

    Merge tag 'x86_vdso_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 vdso updates from Borislav Petkov:
     "Remove -nostdlib compiler flag now that the vDSO uses the linker
      instead of the compiler driver to link files"
    
    * tag 'x86_vdso_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/purgatory: Remove -nostdlib compiler flag
      x86/vdso: Remove -nostdlib compiler flag

commit 3c6d4056663dad0ea0b87b21fe98415b9dbcdd5b
Merge: 25f8c7785e254 5fe392ff9d1f7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 10:18:58 2022 -0800

    Merge tag 'x86_build_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 build fix from Borislav Petkov:
     "A fix for cross-compiling the compressed stub on arm64 with clang"
    
    * tag 'x86_build_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/boot/compressed: Move CLANG_FLAGS to beginning of KBUILD_CFLAGS

commit 25f8c7785e254779fbd2127c4eced81811e8e421
Merge: 308319e990ae9 244122b4d2e52
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 10:09:22 2022 -0800

    Merge tag 'x86_cpu_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 cpuid updates from Borislav Petkov:
    
     - Enable the short string copies for CPUs which support them, in
       copy_user_enhanced_fast_string()
    
     - Avoid writing MSR_CSTAR on Intel due to TDX guests raising a #VE trap
    
    * tag 'x86_cpu_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/lib: Add fast-short-rep-movs check to copy_user_enhanced_fast_string()
      x86/cpu: Don't write CSTAR MSR on Intel CPUs

commit 308319e990ae95b2a752fa0a1730f88598ca0dc7
Merge: 2e97a0c02b94f 0be4838f018c1
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 10:02:27 2022 -0800

    Merge tag 'x86_cleanups_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 cleanups from Borislav Petkov:
     "The mandatory set of random minor cleanups all over tip"
    
    * tag 'x86_cleanups_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/events/amd/iommu: Remove redundant assignment to variable shift
      x86/boot/string: Add missing function prototypes
      x86/fpu: Remove duplicate copy_fpstate_to_sigframe() prototype
      x86/uaccess: Move variable into switch case statement

commit 2e97a0c02b94f2ecd5cbf29ded90c5db055e8ad0
Merge: 4a692ae360615 4d5cff69fbddb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 10:00:03 2022 -0800

    Merge tag 'x86_misc_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull misc x86 updates from Borislav Petkov:
     "The pile which we cannot find the proper topic for so we stick it in
      x86/misc:
    
       - Add support for decoding instructions which do MMIO accesses in
         order to use it in SEV and TDX guests
    
       - An include fix and reorg to allow for removing set_fs in UML later"
    
    * tag 'x86_misc_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/mtrr: Remove the mtrr_bp_init() stub
      x86/sev-es: Use insn_decode_mmio() for MMIO implementation
      x86/insn-eval: Introduce insn_decode_mmio()
      x86/insn-eval: Introduce insn_get_modrm_reg_ptr()
      x86/insn-eval: Handle insn_get_opcode() failure

commit 2a8ab0fbd110dec25795a98aaa232ede36f6c855
Merge: 84f91c62d6754 45c753f5f24d2
Author: Tejun Heo <tj@kernel.org>
Date:   Mon Jan 10 07:54:04 2022 -1000

    Merge branch 'workqueue/for-5.16-fixes' into workqueue/for-5.17
    
    for-5.16-fixes contains two subtle race conditions which were introduced by
    scheduler side code cleanups. The branch didn't get pushed out, so merge
    into for-5.17.

commit 4a692ae360615026b25d64c29fc7c12c0ef63c5f
Merge: bfed6efb8e136 b64dfcde1ca9c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:51:38 2022 -0800

    Merge tag 'x86_mm_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 mm updates from Borislav Petkov:
    
     - Flush *all* mappings from the TLB after switching to the trampoline
       pagetable to prevent any stale entries' presence
    
     - Flush global mappings from the TLB, in addition to the CR3-write,
       after switching off of the trampoline_pgd during boot to clear the
       identity mappings
    
     - Prevent instrumentation issues resulting from the above changes
    
    * tag 'x86_mm_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/mm: Prevent early boot triple-faults with instrumentation
      x86/mm: Include spinlock_t definition in pgtable.
      x86/mm: Flush global TLB when switching to trampoline page-table
      x86/mm/64: Flush global TLB on boot and AP bringup
      x86/realmode: Add comment for Global bit usage in trampoline_pgd
      x86/mm: Add missing <asm/cpufeatures.h> dependency to <asm/page_64.h>

commit bfed6efb8e136c0e0a4cc854f2aaa2ed6ac1b9e0
Merge: d3c20bfb74935 2056e2989bf47
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:44:09 2022 -0800

    Merge tag 'x86_sgx_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 SGX updates from Borislav Petkov:
    
     - Add support for handling hw errors in SGX pages: poisoning,
       recovering from poison memory and error injection into SGX pages
    
     - A bunch of changes to the SGX selftests to simplify and allow of SGX
       features testing without the need of a whole SGX software stack
    
     - Add a sysfs attribute which is supposed to show the amount of SGX
       memory in a NUMA node, similar to what /proc/meminfo is to normal
       memory
    
     - The usual bunch of fixes and cleanups too
    
    * tag 'x86_sgx_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (24 commits)
      x86/sgx: Fix NULL pointer dereference on non-SGX systems
      selftests/sgx: Fix corrupted cpuid macro invocation
      x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node
      x86/sgx: Fix minor documentation issues
      selftests/sgx: Add test for multiple TCS entry
      selftests/sgx: Enable multiple thread support
      selftests/sgx: Add page permission and exception test
      selftests/sgx: Rename test properties in preparation for more enclave tests
      selftests/sgx: Provide per-op parameter structs for the test enclave
      selftests/sgx: Add a new kselftest: Unclobbered_vdso_oversubscribed
      selftests/sgx: Move setup_test_encl() to each TEST_F()
      selftests/sgx: Encpsulate the test enclave creation
      selftests/sgx: Dump segments and /proc/self/maps only on failure
      selftests/sgx: Create a heap for the test enclave
      selftests/sgx: Make data measurement for an enclave segment optional
      selftests/sgx: Assign source for each segment
      selftests/sgx: Fix a benign linker warning
      x86/sgx: Add check for SGX pages to ghes_do_memory_failure()
      x86/sgx: Add hook to error injection address validation
      x86/sgx: Hook arch_memory_failure() into mainline code
      ...

commit d3c20bfb74935e31e47fe979a9d3d74c6d9c9040
Merge: 01d5e7872c1c2 df0114f1f8711
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:42:36 2022 -0800

    Merge tag 'x86_cache_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 resource control fixlet from Borislav Petkov:
     "A minor code cleanup removing a redundant assignment"
    
    * tag 'x86_cache_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/resctrl: Remove redundant assignment to variable chunks

commit 01d5e7872c1c2c04f4fd419c9a4968e148efc5a0
Merge: cd36722d74733 20f07a044a76a
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:33:40 2022 -0800

    Merge tag 'x86_sev_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 SEV updates from Borislav Petkov:
     "The accumulated pile of x86/sev generalizations and cleanups:
    
       - Share the SEV string unrolling logic with TDX as TDX guests need it
         too
    
       - Cleanups and generalzation of code shared by SEV and TDX"
    
    * tag 'x86_sev_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/sev: Move common memory encryption code to mem_encrypt.c
      x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c
      x86/sev: Use CC_ATTR attribute to generalize string I/O unroll
      x86/sev: Remove do_early_exception() forward declarations
      x86/head64: Carve out the guest encryption postprocessing into a helper
      x86/sev: Get rid of excessive use of defines
      x86/sev: Shorten GHCB terminate macro names

commit cd36722d74733b748ae812e37dcfe035b420de67
Merge: e59451fd3bfa2 9e4d52a00a021
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:21:36 2022 -0800

    Merge tag 'x86_platform_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 platform fix from Borislav Petkov:
     "A single DT compatibility fix for the Intel media processor CE4100
      driver"
    
    * tag 'x86_platform_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/ce4100: Replace "ti,pcf8575" by "nxp,pcf8575"

commit e59451fd3bfa263c775c7dffb7c3df9a787c97bb
Merge: 191cf7fab9ef5 6da5175dbe1c2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:09:36 2022 -0800

    Merge tag 'x86_paravirt_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 paravirtualization fix from Borislav Petkov:
     "Define the INTERRUPT_RETURN macro only when CONFIG_XEN_PV is enabled
      as it is its only user"
    
    * tag 'x86_paravirt_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/paravirt: Fix build PARAVIRT_XXL=y without XEN_PV

commit fff489ff0722bec127a05667bec00ea45cf9f77e
Merge: 125521addcd68 2685c77b80a80
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 18:08:30 2022 +0100

    Merge branch 'thermal-int340x'
    
    Merge int340x thermal driver update fixing RFIM mailbox write
    commands handling for 5.17-rc1.
    
    * thermal-int340x:
      thermal/drivers/int340x: Fix RFIM mailbox write commands

commit 191cf7fab9ef5f5d4a2b2ad0094ef76ba18a7439
Merge: 8cc1e20765f03 0fe4ff885f8a5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 09:05:26 2022 -0800

    Merge tag 'x86_fpu_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
    
    Pull x86 fpu update from Borislav Petkov:
     "A single x86/fpu update for 5.17:
    
       - Exclude AVX opmask registers use from AVX512 state tracking as they
         don't contribute to frequency throttling"
    
    * tag 'x86_fpu_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86/fpu: Correct AVX512 state tracking

commit 5fed0be8583f08c1548b4dcd9e5ee0d1133d0730
Author: Jaegeuk Kim <jaegeuk@kernel.org>
Date:   Fri Jan 7 20:08:45 2022 -0800

    f2fs: do not allow partial truncation on pinned file
    
    If the pinned file has a hole by partial truncation, application that has
    the block map will be broken.
    
    Reviewed-by: Chao Yu <chao@kernel.org>
    Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

commit 78e6e4dfd8f0cbb477a6f9571123edcbd5873c28
Merge: c001a52df4b6f ffb9bfa8e470f 702f21db4995f 36fd3609d0dd7
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 18:00:31 2022 +0100

    Merge branches 'pm-opp', 'pm-devfreq' and 'powercap'
    
    Merge an operating performance points (OPP) update, devfreq updates
    and power capping updates for 5.17-rc1:
    
     - Update outdated OPP documentation (Tang Yizhou).
    
     - Reduce log severity for informative message regarding frequency
       transition failures in devfreq (Tzung-Bi Shih).
    
     - Add DRAM frequency controller devfreq driver for Allwinner sunXi
       SoCs (Samuel Holland).
    
     - Add missing COMMON_CLK dependency to the sun8i devfreq driver (Arnd
       Bergmann).
    
     - Add support for new layout of Psys PowerLimit Register on SPR to
       the Intel RAPL power capping driver (Zhang Rui).
    
     - Fix typo in a comment in idle_inject.c (Jason Wang).
    
     - Remove unused function definition from the DTPM (Dynamit Thermal
       Power Management) power capping framework (Daniel Lezcano).
    
     - Reduce DTPM trace verbosity (Daniel Lezcano).
    
    * pm-opp:
      Documentation: power: Update outdated contents in opp.rst
    
    * pm-devfreq:
      PM / devfreq: Reduce log severity for informative message
      PM / devfreq: sun8i: addd COMMON_CLK dependency
      PM / devfreq: Add a driver for the sun8i/sun50i MBUS
    
    * powercap:
      powercap/drivers/dtpm: Reduce trace verbosity
      powercap/drivers/dtpm: Remove unused function definition
      powercap: fix typo in a comment in idle_inject.c
      powercap: intel_rapl: support new layout of Psys PowerLimit Register on SPR

commit 8cc1e20765f03a29442484a9acbc97e31578af92
Merge: f0d43b3a3809f 1a0ae068bf6b6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:59:33 2022 -0800

    Merge tag 'm68k-for-v5.17-tag1' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k
    
    Pull m68k updates from Geert Uytterhoeven:
    
     - enable memtest functionality
    
     - defconfig updates
    
    * tag 'm68k-for-v5.17-tag1' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k:
      m68k: defconfig: Update defconfigs for v5.16-rc1
      m68k: Enable memtest functionality

commit f0d43b3a3809f280806825df2454fd83f71874c4
Merge: 9b9e211360044 0704a8586f756
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:58:16 2022 -0800

    Merge tag 's390-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
    
    Pull s390 updates from Heiko Carstens:
     "Besides all the small improvements and cleanups the most notable part
      is the fast vector/SIMD implementation of the ChaCha20 stream cipher,
      which is an adaptation of Andy Polyakov's code for the kernel.
    
      Summary:
    
       - add fast vector/SIMD implementation of the ChaCha20 stream cipher,
         which mainly adapts Andy Polyakov's code for the kernel
    
       - add status attribute to AP queue device so users can easily figure
         out its status
    
       - fix race in page table release code, and and lots of documentation
    
       - remove uevent suppress from cio device driver, since it turned out
         that it generated more problems than it solved problems
    
       - quite a lot of virtual vs physical address confusion fixes
    
       - various other small improvements and cleanups all over the place"
    
    * tag 's390-5.17-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux: (39 commits)
      s390/dasd: use default_groups in kobj_type
      s390/sclp_sd: use default_groups in kobj_type
      s390/pci: simplify __pciwb_mio() inline asm
      s390: remove unused TASK_SIZE_OF
      s390/crash_dump: fix virtual vs physical address handling
      s390/crypto: fix compile error for ChaCha20 module
      s390/mm: check 2KB-fragment page on release
      s390/mm: better annotate 2KB pagetable fragments handling
      s390/mm: fix 2KB pgtable release race
      s390/sclp: release SCLP early buffer after kernel initialization
      s390/nmi: disable interrupts on extended save area update
      s390/zcrypt: CCA control CPRB sending
      s390/disassembler: update opcode table
      s390/uv: fix memblock virtual vs physical address confusion
      s390/smp: fix memblock_phys_free() vs memblock_free() confusion
      s390/sclp: fix memblock_phys_free() vs memblock_free() confusion
      s390/exit: remove dead reference to do_exit from copy_thread
      s390/ap: add missing virt_to_phys address conversion
      s390/pgalloc: use pointers instead of unsigned long values
      s390/pgalloc: add virt/phys address handling to base asce functions
      ...

commit c001a52df4b6f90bfbfb4a6d6721aa7cd2bf2ebd
Merge: 5561f25beb30b 7dfc5b6e909e8 50a4606655582 74d9555580c48
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 17:57:13 2022 +0100

    Merge branches 'pm-cpuidle', 'pm-core' and 'pm-sleep'
    
    Merge cpuidle updates, PM core updates and one hiberation-related
    update for 5.17-rc1:
    
     - Make cpuidle use default_groups in kobj_type (Greg Kroah-Hartman).
    
     - Fix two comments in cpuidle code (Jason Wang, Yang Li).
    
     - Simplify locking in pm_runtime_put_suppliers() (Rafael Wysocki).
    
     - Add safety net to supplier device release in the runtime PM core
       code (Rafael Wysocki).
    
     - Capture device status before disabling runtime PM for it (Rafael
       Wysocki).
    
     - Add new macros for declaring PM operations to allow drivers to
       avoid guarding them with CONFIG_PM #ifdefs or __maybe_unused and
       update some drivers to use these macros (Paul Cercueil).
    
     - Allow ACPI hardware signature to be honoured during restore from
       hibernation (David Woodhouse).
    
    * pm-cpuidle:
      cpuidle: use default_groups in kobj_type
      cpuidle: Fix cpuidle_remove_state_sysfs() kerneldoc comment
      cpuidle: menu: Fix typo in a comment
    
    * pm-core:
      PM: runtime: Simplify locking in pm_runtime_put_suppliers()
      mmc: mxc: Use the new PM macros
      mmc: jz4740: Use the new PM macros
      PM: runtime: Add safety net to supplier device release
      PM: runtime: Capture device status before disabling runtime PM
      PM: core: Add new *_PM_OPS macros, deprecate old ones
      PM: core: Redefine pm_ptr() macro
      r8169: Avoid misuse of pm_ptr() macro
    
    * pm-sleep:
      PM: hibernate: Allow ACPI hardware signature to be honoured

commit 5561f25beb30bfd95559972858125320411e00d9
Merge: 4ecc933b7d1f4 6c4ab1b86dac3
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 17:54:45 2022 +0100

    Merge branch 'pm-cpufreq'
    
    Merge cpufreq updates for 5.17-rc1:
    
     - Add new P-state driver for AMD processors (Huang Rui).
    
     - Fix initialization of min and max frequency QoS requests in the
       cpufreq core (Rafael Wysocki).
    
     - Fix EPP handling on Alder Lake in intel_pstate (Srinivas Pandruvada).
    
     - Make intel_pstate update cpuinfo.max_freq when notified of HWP
       capabilities changes and drop a redundant function call from that
       driver (Rafael Wysocki).
    
     - Improve IRQ support in the Qcom cpufreq driver (Ard Biesheuvel,
       Stephen Boyd, Vladimir Zapolskiy).
    
     - Fix double devm_remap() in the Mediatek cpufreq driver (Hector Yuan).
    
     - Introduce thermal pressure helpers for cpufreq CPU cooling (Lukasz
       Luba).
    
     - Make cpufreq use default_groups in kobj_type (Greg Kroah-Hartman).
    
    * pm-cpufreq: (32 commits)
      x86, sched: Fix undefined reference to init_freq_invariance_cppc() build error
      cpufreq: amd-pstate: Fix Kconfig dependencies for AMD P-State
      cpufreq: amd-pstate: Fix struct amd_cpudata kernel-doc comment
      MAINTAINERS: Add AMD P-State driver maintainer entry
      Documentation: amd-pstate: Add AMD P-State driver introduction
      cpufreq: amd-pstate: Add AMD P-State performance attributes
      cpufreq: amd-pstate: Add AMD P-State frequencies attributes
      cpufreq: amd-pstate: Add boost mode support for AMD P-State
      cpufreq: amd-pstate: Add trace for AMD P-State module
      cpufreq: amd-pstate: Introduce the support for the processors with shared memory solution
      cpufreq: amd-pstate: Add fast switch function for AMD P-State
      cpufreq: amd-pstate: Introduce a new AMD P-State driver to support future processors
      ACPI: CPPC: Add CPPC enable register function
      ACPI: CPPC: Check present CPUs for determining _CPC is valid
      ACPI: CPPC: Implement support for SystemIO registers
      x86/msr: Add AMD CPPC MSR definitions
      x86/cpufeatures: Add AMD Collaborative Processor Performance Control feature flag
      cpufreq: use default_groups in kobj_type
      cpufreq: mediatek-hw: Fix double devm_remap in hotplug case
      cpufreq: intel_pstate: Update cpuinfo.max_freq on HWP_CAP changes
      ...

commit 9b9e211360044c12d7738973c944d6f300134881
Merge: a7ac314061375 945409a6ef442
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:49:37 2022 -0800

    Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
    
    Pull arm64 updates from Catalin Marinas:
    
     - KCSAN enabled for arm64.
    
     - Additional kselftests to exercise the syscall ABI w.r.t. SVE/FPSIMD.
    
     - Some more SVE clean-ups and refactoring in preparation for SME
       support (scalable matrix extensions).
    
     - BTI clean-ups (SYM_FUNC macros etc.)
    
     - arm64 atomics clean-up and codegen improvements.
    
     - HWCAPs for FEAT_AFP (alternate floating point behaviour) and
       FEAT_RPRESS (increased precision of reciprocal estimate and
       reciprocal square root estimate).
    
     - Use SHA3 instructions to speed-up XOR.
    
     - arm64 unwind code refactoring/unification.
    
     - Avoid DC (data cache maintenance) instructions when DCZID_EL0.DZP ==
       1 (potentially set by a hypervisor; user-space already does this).
    
     - Perf updates for arm64: support for CI-700, HiSilicon PCIe PMU,
       Marvell CN10K LLC-TAD PMU, miscellaneous clean-ups.
    
     - Other fixes and clean-ups; highlights: fix the handling of erratum
       1418040, correct the calculation of the nomap region boundaries,
       introduce io_stop_wc() mapped to the new DGH instruction (data
       gathering hint).
    
    * tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux: (81 commits)
      arm64: Use correct method to calculate nomap region boundaries
      arm64: Drop outdated links in comments
      arm64: perf: Don't register user access sysctl handler multiple times
      drivers: perf: marvell_cn10k: fix an IS_ERR() vs NULL check
      perf/smmuv3: Fix unused variable warning when CONFIG_OF=n
      arm64: errata: Fix exec handling in erratum 1418040 workaround
      arm64: Unhash early pointer print plus improve comment
      asm-generic: introduce io_stop_wc() and add implementation for ARM64
      arm64: Ensure that the 'bti' macro is defined where linkage.h is included
      arm64: remove __dma_*_area() aliases
      docs/arm64: delete a space from tagged-address-abi
      arm64: Enable KCSAN
      kselftest/arm64: Add pidbench for floating point syscall cases
      arm64/fp: Add comments documenting the usage of state restore functions
      kselftest/arm64: Add a test program to exercise the syscall ABI
      kselftest/arm64: Allow signal tests to trigger from a function
      kselftest/arm64: Parameterise ptrace vector length information
      arm64/sve: Minor clarification of ABI documentation
      arm64/sve: Generalise vector length configuration prctl() for SME
      arm64/sve: Make sysctl interface for SVE reusable by SME
      ...

commit c40238e3b8c98993e3c70057f6099e24cc2380f7
Author: Zhu Yanjun <yanjun.zhu@linux.dev>
Date:   Mon Jan 10 02:37:33 2022 -0500

    RDMA/irdma: Remove the redundant return
    
    The type of the function i40iw_remove is void. So remove
    the unnecessary return.
    
    Link: https://lore.kernel.org/r/20220110073733.3221379-1-yanjun.zhu@linux.dev
    Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Acked-by: Shiraz Saleem <shiraz.saleem@intel.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit a7ac314061375c7805e0d3a26aad6eb0c41100df
Merge: bb4ed26e7e837 733e417518a69
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:42:28 2022 -0800

    Merge tag 'asm-generic-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic
    
    Pull asm-generic cleanups from Arnd Bergmann:
     "A few minor cleanups for cross-architecture code: Alexandre Ghiti
      deals with removing some leftovers from drivers and features that have
      been removed, and Wasin Thonkaew has a cosmetic change"
    
    * tag 'asm-generic-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic:
      asm-generic/error-injection.h: fix a spelling mistake, and a coding style issue
      arch: Remove leftovers from prism54 wireless driver
      arch: Remove leftovers from mandatory file locking
      Documentation, arch: Remove leftovers from CIFS_WEAK_PW_HASH
      Documentation, arch: Remove leftovers from raw device

commit bb4ed26e7e837ca3034d4105491436d54c430038
Merge: aca48b2dd1e70 299e6f788eab0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:32:37 2022 -0800

    Merge tag 'newsoc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull RISC-V SoC updates from Arnd Bergmann:
     "Add support for StarFive JH7100 RISC-V SoC
    
      This adds support for the StarFive JH7100, including the necessary
      device drivers and DT files for the BeagleV Starlight prototype board,
      with additional boards to be added later. This SoC promises to be the
      first usable low-cost platform for RISC-V.
    
      I've taken this through the SoC tree in the anticipation of adding a
      few other Arm based SoCs as well, but those did not pass the review in
      time, so it's only this one"
    
    * tag 'newsoc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
      reset: starfive-jh7100: Fix 32bit compilation
      RISC-V: Add BeagleV Starlight Beta device tree
      RISC-V: Add initial StarFive JH7100 device tree
      serial: 8250_dw: Add StarFive JH7100 quirk
      dt-bindings: serial: snps-dw-apb-uart: Add JH7100 uarts
      pinctrl: starfive: Add pinctrl driver for StarFive SoCs
      dt-bindings: pinctrl: Add StarFive JH7100 bindings
      dt-bindings: pinctrl: Add StarFive pinctrl definitions
      reset: starfive-jh7100: Add StarFive JH7100 reset driver
      dt-bindings: reset: Add Starfive JH7100 reset bindings
      dt-bindings: reset: Add StarFive JH7100 reset definitions
      clk: starfive: Add JH7100 clock generator driver
      dt-bindings: clock: starfive: Add JH7100 bindings
      dt-bindings: clock: starfive: Add JH7100 clock definitions
      dt-bindings: interrupt-controller: Add StarFive JH7100 plic
      dt-bindings: timer: Add StarFive JH7100 clint
      RISC-V: Add StarFive SoC Kconfig option

commit aca48b2dd1e70bb1be23bf5eb2fa50da9f6c2579
Merge: e85195d5bf897 8b0c59c622dc4
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:24:40 2022 -0800

    Merge tag 'dt-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC devicetree updates from Arnd Bergmann:
     "As usual, this is the bulk of the updates for the SoC tree, adding
      more devices to existing files, addressing issues from ever improving
      automated checking, and fixing minor issues.
    
      The most interesting bits as usual are the new platforms. All the
      newly supported SoCs belong into existing families this time:
    
       - Qualcomm gets support for two newly announced platforms, both of
         which can now work in production environments: the SDX65 5G modem
         that can run a minimal Linux on its Cortex-A7 core, and the
         Snapdragon 8 Gen 1, their latest high-end phone SoC.
    
       - Renesas adds support for R-Car S4-8, the most recent automotive
         Server/Communication SoC.
    
       - TI adds support for J721s2, a new automotive SoC in the K3 family.
    
       - Mediatek MT7986a/b is a SoC used in Wifi routers, the latest
         generation following their popular MT76xx series. Only basic
         support is added for now.
    
       - NXP i.MX8 ULP8 is a new low-power variant of the widespread i.MX8
         series.
    
       - TI SPEAr320s is a minor variant of the old SPEAr320 SoC that we
         have supported for a long time.
    
      New boards with the existing SoCs include
    
       - Aspeed AST2500/AST2600 BMCs in TYAN, Facebook and Yadro servers
    
       - AT91/SAMA5 based evaluation board
    
       - NXP gains twenty new development and industrial boards for their
         i.MX and Layerscape SoCs
    
       - Intel IXP4xx now supports the final two machines in device tree
         that were previously only supported in old style board files.
    
       - Mediatek MT6589 is used in the Fairphone FP1 phone from 2013, while
         MT8183 is used in the Acer Chromebook 314.
    
       - Qualcomm gains support for the reference machines using the two new
         SoCs, plus a number of Chromebook variants and phones based on the
         Snapdragon 7c, 845 and 888 SoCs, including various Sony Xperia
         devices and the Microsoft Surface Duo 2.
    
       - ST STM32 now supports the Engicam i.Core STM32MP1 carrier board.
    
       - Tegra now boots various older Android devices based on 32-bit chips
         out of the box, including a number of ASUS Transformer tablets.
    
         There is also a new Jetson AGX Orin developer kit.
    
       - Apple support adds the missing device trees for all the remaining
         M1 Macbook and iMac variants, though not yet the M1 Pro/Max
         versions.
    
       - Allwinner now supports another version of the Tanix TX6 set-top box
         based on the H6 SoC.
    
       - Broadcom gains support for the Netgear RAXE500 Wireless router
         based on BCM4908"
    
    * tag 'dt-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (574 commits)
      Revert "ARM: dts: BCM5301X: define RTL8365MB switch on Asus RT-AC88U"
      arm64: dts: qcom: sm6125: Avoid using missing SM6125_VDDCX
      arm64: dts: qcom: sm8450-qrd: Enable USB nodes
      arm64: dts: qcom: sm8450: Add usb nodes
      ARM: dts: aspeed: add LCLK setting into LPC KCS nodes
      dt-bindings: ipmi: bt-bmc: add 'clocks' as a required property
      ARM: dts: aspeed: add LCLK setting into LPC IBT node
      ARM: dts: aspeed: p10: Add TPM device
      ARM: dts: aspeed: p10: Enable USB host ports
      ARM: dts: aspeed: Add TYAN S8036 BMC machine
      ARM: dts: aspeed: tyan-s7106: Add uart_routing and fix vuart config
      ARM: dts: aspeed: Adding Facebook Bletchley BMC
      ARM: dts: aspeed: g220a: Enable secondary flash
      ARM: dts: Add openbmc-flash-layout-64-alt.dtsi
      ARM: dts: aspeed: Add secure boot controller node
      dt-bindings: aspeed: Add Secure Boot Controller bindings
      ARM: dts: Remove "spidev" nodes
      dt-bindings: pinctrl: samsung: Add pin drive definitions for Exynos850
      dt-bindings: arm: samsung: Document E850-96 board binding
      dt-bindings: Add vendor prefix for WinLink
      ...

commit 70df8e1bdc941431af2370270f5140291dcbb282
Merge: af8fefd744448 7e29a225c7508 bcf6f1759adff 17f18417d6da0 1a901c914dfbe e5b5d25444e9e e96c1197aca62
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 17:22:15 2022 +0100

    Merge branches 'acpi-tables', 'acpi-numa', 'acpi-sysfs', 'acpi-cppc', 'acpi-thermal' and 'acpi-battery'
    
    Merge ACPI tables parsing code update, NUMA-related ACPI update, CPPC
    documentation update, ACPI sysfs attributes handling update and ACPI
    thermal and battery drivers updates for 5.17-rc1:
    
     - Add AEST to the list of known ACPI table signatures (Shuuichirou
       Ishii).
    
     - Make ACPI NUMA code take hotpluggable memblocks into account when
       CONFIG_MEMORY_HOTPLUG is not set (Vitaly Kuznetsov).
    
     - Use default_groups in kobj_type in the ACPI sysfs code (Greg
       Kroah-Hartman).
    
     - Rearrange _CPC structure documentation (Andy Shevchenko).
    
     - Drop an always true check from the ACPI thermal driver (Adam
       Borowski).
    
     - Add new "not charging" quirk for Lenovo ThinkPads to the ACPI
       battery driver (Thomas Weißschuh).
    
    * acpi-tables:
      ACPI: tables: Add AEST to the list of known table signatures
    
    * acpi-numa:
      ACPI: NUMA: Process hotpluggable memblocks when !CONFIG_MEMORY_HOTPLUG
    
    * acpi-sysfs:
      ACPI: sysfs: use default_groups in kobj_type
    
    * acpi-cppc:
      ACPI: CPPC: Amend documentation in the comments
    
    * acpi-thermal:
      ACPI: thermal: drop an always true check
    
    * acpi-battery:
      ACPI: battery: Add the ThinkPad "Not Charging" quirk

commit e85195d5bf8979f6db3f12cf8f1294887bf6b037
Merge: 0dca3c5e017ab 13ee75c7b57c5
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:13:52 2022 -0800

    Merge tag 'drivers-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC driver updates from Arnd Bergmann:
     "There are cleanups and minor bugfixes across several SoC specific
      drivers, for Qualcomm, Samsung, NXP i.MX, AT91, Tegra, Keystone,
      Renesas, ZynqMP
    
      Noteworthy new features are:
    
       - The op-tee firmware driver gains support for asynchronous
         notifications from secure-world firmware.
    
       - Qualcomm platforms gain support for new SoC types in various
         drivers: power domain, cache controller, RPM sleep, soc-info
    
       - Samsung SoC drivers gain support for new SoCs in ChipID and PMU, as
         well as a new USIv2 driver that handles various types of serial
         communiction (uart, i2c, spi)
    
       - Renesas adds support for R-Car S4-8 (R8A779F0) in multiple drivers,
         as well as memory controller support for RZ/G2L (R9A07G044).
    
       - Apple M1 gains support for the PMGR power management driver"
    
    * tag 'drivers-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc: (94 commits)
      soc: qcom: rpmh-rsc: Fix typo in a comment
      soc: qcom: socinfo: Add SM6350 and SM7225
      dt-bindings: arm: msm: Don't mark LLCC interrupt as required
      dt-bindings: firmware: scm: Add SM6350 compatible
      dt-bindings: arm: msm: Add LLCC for SM6350
      soc: qcom: rpmhpd: Sort power-domain definitions and lists
      soc: qcom: rpmhpd: Remove mx/cx relationship on sc7280
      soc: qcom: rpmhpd: Rename rpmhpd struct names
      soc: qcom: rpmhpd: sm8450: Add the missing .peer for sm8450_cx_ao
      soc: qcom: socinfo: add SM8450 ID
      soc: qcom: rpmhpd: Add SM8450 power domains
      dt-bindings: power: rpmpd: Add SM8450 to rpmpd binding
      soc: qcom: smem: Update max processor count
      dt-bindings: arm: qcom: Document SM8450 SoC and boards
      dt-bindings: firmware: scm: Add SM8450 compatible
      dt-bindings: arm: cpus: Add kryo780 compatible
      soc: qcom: rpmpd: Add support for sm6125
      dt-bindings: qcom-rpmpd: Add sm6125 power domains
      soc: qcom: aoss: constify static struct thermal_cooling_device_ops
      PM: AVS: qcom-cpr: Use div64_ul instead of do_div
      ...

commit 0dca3c5e017ab81ebe21eb9096f657c45a6b17a4
Merge: 1135ec008ef37 0d2589aa5ca99
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:12:26 2022 -0800

    Merge tag 'defconfig-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM defconfig updates from Arnd Bergmann:
     "These are the usual changes to enable newly added driver by default,
      and to do some housekeeping around changing Kconfig symbols"
    
    * tag 'defconfig-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
      arm64: defconfig: Enable Samsung I2C driver
      ARM: configs: at91: Enable crypto software implementations
      ARM: configs: at91: sama7: Enable SPI NOR and QSPI controller
      ARM: config: multi v7: Enable NVIDIA Tegra20 APB DMA driver
      ARM: config: multi v7: Enable NVIDIA Tegra20 S/PDIF driver
      ARM: tegra_defconfig: Enable S/PDIF driver
      ARM: imx_v6_v7_defconfig: Enable for DHCOM devices required RTC_DRV_RV3029C2
      ARM: config: multi v7: Enable display drivers used by Tegra devices
      ARM: tegra_defconfig: Enable drivers wanted by Acer Chromebooks and ASUS tablets
      ARM: configs: gemini: Activate crypto driver
      arm64: defconfig: enable drivers for booting i.MX8ULP
      arm64: defconfig: Enable R-Car S4-8
      arm64: defconfig: enable drivers for TQ TQMa8MxML-MBa8Mx
      arm64: defconfig: Enable OV5640
      arm64: defconfig: Enable VIDEO_IMX_MEDIA

commit 1135ec008ef3745cd1cee5bc543cfe48427c22a9
Merge: df0cc57e057f1 fe47ec5fa8ec2
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon Jan 10 08:10:20 2022 -0800

    Merge tag 'soc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
    
    Pull ARM SoC updates from Arnd Bergmann:
     "These are all minor bug fixes and cleanups to code in arch/arm and
      arch/arm64 that is specific to one SoC, updating Kconfig symbols, the
      MAINTAINERS file, and removing some dead code"
    
    * tag 'soc-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc:
      arm64: exynos: Enable Exynos Multi-Core Timer driver
      ARM: ixp4xx: remove unused header file pata_ixp4xx_cf.h
      ARM: ixp4xx: remove dead configs CPU_IXP43X and CPU_IXP46X
      MAINTAINERS: Add Florian as BCM5301X and BCM53573 maintainer
      ARM: samsung: Remove HAVE_S3C2410_I2C and use direct dependencies
      ARM: imx: rename DEBUG_IMX21_IMX27_UART to DEBUG_IMX27_UART
      ARM: imx: remove dead left-over from i.MX{27,31,35} removal
      ARM: s3c: add one more "fallthrough" statement in Jive
      ARM: s3c: include header for prototype of s3c2410_modify_misccr
      ARM: shmobile: rcar-gen2: Add missing of_node_put()

commit 86599dbe2c5272588f859858239d1f52321eb0f9
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Mon Jan 10 08:04:14 2022 -0600

    tracing: Add helper functions to simplify event_command.parse() callback handling
    
    The event_command.parse() callback is responsible for parsing and
    registering triggers.  The existing command implementions for this
    callback duplicate a lot of the same code, so to clean up and
    consolidate those implementations, introduce a handful of helper
    functions for implementors to use.
    
    This also makes it easier for new commands to be implemented and
    allows them to focus more on the customizations they provide rather
    than obscuring and complicating it with boilerplate code.
    
    Link: https://lkml.kernel.org/r/c1ff71f594d45177706571132bd3119491097221.1641823001.git.zanussi@kernel.org
    
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 2378a2d6b6cf863bdd566aae495336c72bdaec99
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Mon Jan 10 08:04:13 2022 -0600

    tracing: Remove ops param from event_command reg()/unreg() callbacks
    
    The event_trigger_ops for an event_command are already accessible via
    event_trigger_data.ops so remove the redundant ops from the callback.
    
    Link: https://lkml.kernel.org/r/4c6f2a41820452f9cacddc7634ad442928aa2aa6.1641823001.git.zanussi@kernel.org
    
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit fb339e531bfccbd12d49b165f37636e62778b69f
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Mon Jan 10 08:04:12 2022 -0600

    tracing: Change event_trigger_ops func() to trigger()
    
    The name of the func() callback on event_trigger_ops is too generic
    and is easily confused with other callbacks with that name, so change
    it to something that reflects its actual purpose.
    
    In this case, the main purpose of the callback is to implement an
    event trigger, so call it trigger() instead.
    
    Also add some more documentation to event_trigger_ops describing the
    callbacks a bit better.
    
    Link: https://lkml.kernel.org/r/36ab812e3ee74ee03ae0043fda41a858ee728c00.1641823001.git.zanussi@kernel.org
    
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit 9ec5a7d16899ed9062cc4c3dd3a13e1771411ab3
Author: Tom Zanussi <zanussi@kernel.org>
Date:   Mon Jan 10 08:04:11 2022 -0600

    tracing: Change event_command func() to parse()
    
    The name of the func() callback on event_command is too generic and is
    easily confused with other callbacks with that name, so change it to
    something that reflects its actual purpose.
    
    In this case, the main purpose of the callback is to parse an event
    command, so call it parse() instead.
    
    Link: https://lkml.kernel.org/r/7784e321840752ed88aac0b349c0c685fc9247b1.1641823001.git.zanussi@kernel.org
    
    Signed-off-by: Tom Zanussi <zanussi@kernel.org>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

commit af8fefd7444480bb8fd8d74f977dbac4693ac3ed
Merge: 5847d2d2efaab 1b15b69800e2f 5f96ba5655212 75f32fa3a6fba
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 17:08:49 2022 +0100

    Merge branches 'acpi-x86', 'acpi-pmic' and 'acpi-dptf'
    
    Merge x86-specific ACPI updates, PMIC driver ACPI updates and a DPTF
    driver update for 5.17-rc1:
    
     - Rework the handling of device enumeration quirks in the x86-specific
       code and add new quirks for known-broken platforms (Hans de Goede).
    
     - Fix the handling of defective LPAT in the ACPI xpower PMIC driver
       and clean up some definitions of PMIC data structures (Hans de
       Goede).
    
     - Fix outdated comment in the ACPI DPTF driver (Sumeet Pawnikar).
    
    * acpi-x86:
      ACPI / x86: Skip AC and battery devices on x86 Android tablets with broken DSDTs
      ACPI / x86: Introduce an acpi_quirk_skip_acpi_ac_and_battery() helper
      mmc: sdhci-acpi: Use the new soc_intel_is_byt() helper
      mmc: sdhci-acpi: Remove special handling for GPD win/pocket devices
      ACPI / x86: Add PWM2 on the Xiaomi Mi Pad 2 to the always_present list
      ACPI / x86: Add not-present quirk for the PCI0.SDHB.BRC1 device on the GPD win
      ACPI / x86: Allow specifying acpi_device_override_status() quirks by path
      ACPI: Change acpi_device_always_present() into acpi_device_override_status()
      ACPI / x86: Drop PWM2 device on Lenovo Yoga Book from always present table
    
    * acpi-pmic:
      ACPI: PMIC: xpower: Fix _TMP ACPI errors
      ACPI: PMIC: allow drivers to provide a custom lpat_raw_to_temp() function
      ACPI: PMIC: constify all struct intel_pmic_opregion_data declarations
    
    * acpi-dptf:
      ACPI: DPTF: Update device ID in a comment

commit 2576e153cd982d540b212e989458edc42ad1b390
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Thu Dec 30 10:11:37 2021 +0800

    scsi: nsp_cs: Check of ioremap return value
    
    Since it is possible for ioremap() to fail, 'data->MmioAddress' could be
    NULL. Skip entry if ioremap() fails.
    
    Link: https://lore.kernel.org/r/20211230021137.1823352-1-jiasheng@iscas.ac.cn
    Fixes: 0e6f9d270840 ("pcmcia: use pcmcia_loop_config in scsi pcmcia drivers")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 5847d2d2efaab724b7ab374b6fca105e24509c92
Merge: b659ea768ae37 b66f868494148 8120832d8f82a
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 16:57:59 2022 +0100

    Merge branches 'acpi-ec' and 'acpi-processor'
    
    Merge ACPI EC driver updates and ACPI processor driver updates for
    5.17-rc1:
    
     - Rework flushing of EC work while suspended to idle and clean up
       the handling of events in the ACPI EC driver (Rafael Wysocki).
    
     - Prohibit ec_sys module parameter write_support from being used
       when the system is locked down (Hans de Goede).
    
     - Make the ACPI processor thermal driver use cpufreq_cpu_get() to
       check for presence of cpufreq policy (Manfred Spraul).
    
     - Avoid unnecessary CPU cache flushing in the ACPI processor idle
       driver (Kirill A. Shutemov).
    
     - Replace kernel.h with the necessary inclusions in the ACPI
       processor driver (Andy Shevchenko).
    
     - Use swap() instead of open coding it in the ACPI processor idle
       driver (Guo Zhengkui).
    
    * acpi-ec:
      ACPI: EC: Mark the ec_sys write_support param as module_param_hw()
      ACPI: EC: Relocate acpi_ec_create_query() and drop acpi_ec_delete_query()
      ACPI: EC: Make the event work state machine visible
      ACPI: EC: Avoid queuing unnecessary work in acpi_ec_submit_event()
      ACPI: EC: Rename three functions
      ACPI: EC: Simplify locking in acpi_ec_event_handler()
      ACPI: EC: Rearrange the loop in acpi_ec_event_handler()
      ACPI: EC: Fold acpi_ec_check_event() into acpi_ec_event_handler()
      ACPI: EC: Pass one argument to acpi_ec_query()
      ACPI: EC: Call advance_transaction() from acpi_ec_dispatch_gpe()
      ACPI: EC: Rework flushing of EC work while suspended to idle
    
    * acpi-processor:
      ACPI: processor: thermal: avoid cpufreq_get_policy()
      ACPI: processor: idle: Only flush cache on entering C3
      ACPI: processor idle: Use swap() instead of open coding it
      ACPI: processor: Replace kernel.h with the necessary inclusions

commit 16720861675393a35974532b3c837d9fd7bfe08c
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Sat Jan 8 16:59:54 2022 -0500

    SUNRPC: Fix sockaddr handling in svcsock_accept_class trace points
    
    Avoid potentially hazardous memory copying and the needless use of
    "%pIS" -- in the kernel, an RPC service listener is always bound to
    ANYADDR. Having the network namespace is helpful when recording
    errors, though.
    
    Fixes: a0469f46faab ("SUNRPC: Replace dprintk call sites in TCP state change callouts")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit dc6c6fb3d639756a532bcc47d4a9bf9f3965881b
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Sun Jan 9 13:26:51 2022 -0500

    SUNRPC: Fix sockaddr handling in the svc_xprt_create_error trace point
    
    While testing, I got an unexpected KASAN splat:
    
    Jan 08 13:50:27 oracle-102.nfsv4.dev kernel: BUG: KASAN: stack-out-of-bounds in trace_event_raw_event_svc_xprt_create_err+0x190/0x210 [sunrpc]
    Jan 08 13:50:27 oracle-102.nfsv4.dev kernel: Read of size 28 at addr ffffc9000008f728 by task mount.nfs/4628
    
    The memcpy() in the TP_fast_assign section of this trace point
    copies the size of the destination buffer in order that the buffer
    won't be overrun.
    
    In other similar trace points, the source buffer for this memcpy is
    a "struct sockaddr_storage" so the actual length of the source
    buffer is always long enough to prevent the memcpy from reading
    uninitialized or unallocated memory.
    
    However, for this trace point, the source buffer can be as small as
    a "struct sockaddr_in". For AF_INET sockaddrs, the memcpy() reads
    memory that follows the source buffer, which is not always valid
    memory.
    
    To avoid copying past the end of the passed-in sockaddr, make the
    source address's length available to the memcpy(). It would be a
    little nicer if the tracing infrastructure was more friendly about
    storing socket addresses that are not AF_INET, but I could not find
    a way to make printk("%pIS") work with a dynamic array.
    
    Reported-by: KASAN
    Fixes: 4b8f380e46e4 ("SUNRPC: Tracepoint to record errors in svc_xpo_create()")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 3ba880a12df5aa4488c18281701b5b1bc3d4531a
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Wed Dec 22 07:09:30 2021 +0000

    scsi: ufs: ufs-mediatek: Fix error checking in ufs_mtk_init_va09_pwr_ctrl()
    
    The function regulator_get() returns an error pointer. Use IS_ERR() to
    validate the return value.
    
    Link: https://lore.kernel.org/r/20211222070930.9449-1-linmq006@gmail.com
    Fixes: cf137b3ea49a ("scsi: ufs-mediatek: Support VA09 regulator operations")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit b659ea768ae372e2f82c6346120f2e7272a42ac9
Merge: 77e2a04745ff8 0890186a96586 3c89857a66ef1 5b6a8f1445bc8 843438deebe24
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date:   Mon Jan 10 16:48:27 2022 +0100

    Merge branches 'acpi-scan', 'acpi-pm', 'acpi-power' and 'acpi-pci'
    
    Merge ACPI device enumeration updates, ACPI power management updates
    and PCI host bridge ACPI driver updates for 5.17-rc1:
    
     - Introduce acpi_fetch_acpi_dev() as a replacement for
       acpi_bus_get_device() and use it in the ACPI subsystem (Rafael
       Wysocki).
    
     - Avoid using _CID for device enumaration if _HID is missing or
       invalid (Rafael Wysocki).
    
     - Rework quirk handling during ACPI device enumeration and add some
       new quirks for known broken platforms (Hans de Goede).
    
     - Avoid unnecessary or redundant CPU cache flushing during system
       PM transitions (Kirill A. Shutemov).
    
     - Add PM debug messages related to power resources (Rafael Wysocki).
    
     - Fix kernel-doc comment in the PCI host bridge ACPI driver (Yang Li).
    
    * acpi-scan:
      serdev: Do not instantiate serdevs on boards with known bogus DSDT entries
      i2c: acpi: Do not instantiate I2C-clients on boards with known bogus DSDT entries
      ACPI / x86: Add acpi_quirk_skip_[i2c_client|serdev]_enumeration() helpers
      ACPI: scan: Create platform device for BCM4752 and LNV4752 ACPI nodes
      ACPI: Use acpi_fetch_acpi_dev() instead of acpi_bus_get_device()
      ACPI: scan: Introduce acpi_fetch_acpi_dev()
      ACPI: scan: Do not add device IDs from _CID if _HID is not valid
    
    * acpi-pm:
      ACPI: PM: Remove redundant cache flushing
      ACPI: PM: Avoid CPU cache flush when entering S4
    
    * acpi-power:
      ACPI: PM: Emit debug messages when enabling/disabling wakeup power
    
    * acpi-pci:
      PCI/ACPI: Fix acpi_pci_osc_control_set() kernel-doc comment

commit 9008661e19606bdf6dddd33073b70872da400590
Author: SEO HOYOUNG <hy50.seo@samsung.com>
Date:   Fri Jan 7 06:39:24 2022 +0900

    scsi: ufs: Modify Tactive time setting conditions
    
    The Tactive time determines the waiting time before burst at hibern8 exit
    and is determined by hardware at linkup time. However, in the case of
    Samsung devices, increase host's Tactive time +100us for stability. If the
    HCI's Tactive time is equal or greater than the device, +100us should be
    set.
    
    Link: https://lore.kernel.org/r/20220106213924.186263-1-hy50.seo@samsung.com
    Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
    Acked-by: Avri Altman <Avri.Altman@wdc.com>
    Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 1aa7d9799e85addc29c06ece99bf1eae1ef9198f
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 19:57:04 2022 +0100

    scsi: efct: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.  So, if it fails, the 32 bits case will also
    fail for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    While at it, return the error code returned by dma_set_mask_and_coherent()
    instead of -1.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Link: https://lore.kernel.org/r/958bcb2a6e86344c14f38369e8e7079615a2b0e3.1641754613.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 7bf2e4d5ca1c94a9b0f730498b3d01768a72dcbd
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:34:07 2022 +0300

    ACPI: pfr_telemetry: Fix info leak in pfrt_log_ioctl()
    
    The "data_info" struct is copied to the user.  It has a 4 byte struct
    hole after the last struct member so we need to memset that to avoid
    copying uninitialized stack data to the user.
    
    Fixes: b0013e037a8b ("ACPI: Introduce Platform Firmware Runtime Telemetry driver")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 706dc3b91989a1286b0eb75a1cd816596c590e5c
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:39 2022 +0100

    scsi: message: fusion: mptctl: Use dma_alloc_coherent()
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia
    Lawall in [2].
    
    When memory is allocated in kbuf_alloc_2_sgl() GFP_KERNEL can be used
    because this function already uses the GFP_USER flag for some memory
    allocation and not spin_lock is taken in the between.
    
    When memory is allocated in mptctl_do_mpt_command() GFP_KERNEL can be used
    because this function already uses copy_from_user() and this function can
    sleep.
    
    When memory is allocated in mptctl_hp_hostinfo() GFP_KERNEL can be used
    because this function already uses mpt_config() and this function has an
    explicit might_sleep().
    
    When memory is allocated in mptctl_hp_targetinfo() GFP_KERNEL can be used
    because this function already uses mpt_config() and this function has an
    explicit might_sleep().
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    
    Link: https://lore.kernel.org/r/516375d6d06114484533baf03aae351306100246.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 76a334d756c596f2f283e1d0054477ba0f0eacf6
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:33 2022 +0100

    scsi: message: fusion: mptsas: Use dma_alloc_coherent()
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia
    Lawall in [2].
    
    In all these places where some memory is allocated GFP_KERNEL can be used
    because they already call mpt_config() which has an explicit might_sleep().
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    
    Link: https://lore.kernel.org/r/443b81ecb08b2fe6f789bb2fdff13a53c809e401.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 7a960b3a5e37f05d7d319bf257a8cf6ee9d18e7c
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:26 2022 +0100

    scsi: message: fusion: Use dma_alloc_coherent() in mptsas_exp_repmanufacture_info()
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia Lawall
    in [2].
    
    The only caller of mptsas_exp_repmanufacture_info() is
    mptsas_probe_one_phy(). This function already calls sas_end_device_alloc()
    or sas_expander_alloc(). They both already use GFP_KERNEL.
    
    As no spin_lock is held at this point, it is safe to also use GFP_KERNEL
    here.
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    
    Link: https://lore.kernel.org/r/d78d4a5b096897932808ed7e3a4540db1687c25d.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 5c5e6b6f61e0196141db38b84b30ef9b3bcca0f2
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:19 2022 +0100

    scsi: message: fusion: mptbase: Use dma_alloc_coherent()
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia
    Lawall in [2].
    
    In all these places where some memory is allocated GFP_KERNEL can be used
    because they already call mpt_config() which has an explicit might_sleep().
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    
    Link: https://lore.kernel.org/r/3bea2452deb8cc8be65982e87efa4c6861caa01c.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit 2d50607260a6c142f49222346814fee30eeaba9e
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:13 2022 +0100

    scsi: message: fusion: Use dma_alloc_coherent() in mpt_alloc_fw_memory()
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia Lawall
    in [2].
    
    mpt_alloc_fw_memory() should still use GFP_ATOMIC, because it can be called
    from mpt_do_upload() which might sleep.
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    
    Link: https://lore.kernel.org/r/db3db9db219005b75659561d08117d312d0cfb13.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit b114dda6f2f10cc8b2ddcde3285a576fe3f12c5d
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:54:05 2022 +0100

    scsi: message: fusion: Remove usage of the deprecated "pci-dma-compat.h" API
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia Lawall
    in [2].
    
    A coccinelle script has been used to perform the needed transformation.  It
    can be found in [3].
    
    In this patch, all functions but pci_alloc_consistent() are handled.
    pci_alloc_consistent() needs more attention and explanation.
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    [3]: https://lore.kernel.org/kernel-janitors/20200716192821.321233-1-christophe.jaillet@wanadoo.fr/
    
    Link: https://lore.kernel.org/r/e38e897fbd3314718315b0e357c824e3f01775d6.1641500561.git.christophe.jaillet@wanadoo.fr
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit e958b5884725dac86d36c1e7afe5a55f31feb0b2
Author: Robert Hancock <robert.hancock@calian.com>
Date:   Fri Jan 7 15:47:06 2022 -0600

    ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple of period bytes
    
    This patch is based on one in the Xilinx kernel tree, "ASoc: xlnx: Make
    buffer bytes multiple of period bytes" by Devarsh Thakkar. The same
    issue exists in the mainline version of the driver. The original
    patch description is as follows:
    
    "The Xilinx Audio Formatter IP has a constraint on period
    bytes to be multiple of 64. This leads to driver changing
    the period size to suitable frames such that period bytes
    are multiple of 64.
    
    Now since period bytes and period size are updated but not
    the buffer bytes, this may make the buffer bytes unaligned
    and not multiple of period bytes.
    
    When this happens we hear popping noise as while DMA is being
    done the buffer bytes are not enough to complete DMA access
    for last period of frame within the application buffer boundary.
    
    To avoid this, align buffer bytes too as multiple of 64, and
    set another constraint to always enforce number of periods as
    integer. Now since, there is already a rule in alsa core
    to enforce Buffer size = Number of Periods * Period Size
    this automatically aligns buffer bytes as multiple of period
    bytes."
    
    Fixes: 6f6c3c36f091 ("ASoC: xlnx: add pcm formatter platform driver")
    Cc: Devarsh Thakkar <devarsh.thakkar@xilinx.com>
    Signed-off-by: Robert Hancock <robert.hancock@calian.com>
    Link: https://lore.kernel.org/r/20220107214711.1100162-2-robert.hancock@calian.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 8d4ff8187bb2b0c9025269f0da42ed16c878cb18
Author: Robert Schlabbach <robert_s@gmx.net>
Date:   Thu Jan 6 23:52:49 2022 +0100

    media: si2157: add support for DVB-C Annex C
    
    DVB-C Annex C is mostly DVB-C Annex A with only minor differences, so
    simply add it to the DVB-C Annex A switch case, so that tuning attempts
    no longer result in -EINVAL.
    
    Link: https://lore.kernel.org/linux-media/trinity-fd7dd9e4-c319-4761-89b6-555fa7b23776-1641509569422@3c-app-gmx-bap68
    Signed-off-by: Robert Schlabbach <robert_s@gmx.net>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

commit 9658105d0e5b1437db161b4227721065d44585b9
Author: Robert Schlabbach <robert_s@gmx.net>
Date:   Thu Jan 6 23:51:39 2022 +0100

    media: si2157: fix bandwidth stored in dev
    
    Make digital tuning store the bandwidth in Hz in the private dev struct,
    rather than the hardware-specific bandwidth property code, so that the
    get_bandwidth() function returns the bandwidth in Hz, just as it already
    does when using analog tuning.
    
    Link: https://lore.kernel.org/linux-media/trinity-931c0e68-88af-46cc-91a1-986754798a4f-1641509499366@3c-app-gmx-bap68
    Reported-by: Robert Schlabbach <robert_s@gmx.net>
    Signed-off-by: Robert Schlabbach <robert_s@gmx.net>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

commit 95c4cd1d19e3e1d4894457a6f015e3a045bc9b06
Author: Robert Schlabbach <robert_s@gmx.net>
Date:   Thu Jan 6 23:49:47 2022 +0100

    media: si2157: fix 6MHz & 6.1MHz bandwidth setting
    
    Commit 98c65a3dac95 ("media: si2157: add support for 1.7MHz and 6.1
    MHz") introduced two bugs: The 6.1MHz setting was always used for any
    bandwidth less than 7MHz due to missing "else" keywords, and then the
    setting was not specified as decimal 10, but as hexadecimal 0x10, which
    makes the tuner refuse the tune command. In sum, it is not possible to
    tune to any channels of less than 7MHz bandwidth anymore.
    
    Add the missing "else" keywords and convert all bandwidth settings to
    decimal to avoid any future decimal vs. hexadecimal confusion.
    
    Remove the use of the undefined bandwidth setting 0x0f for bandwidths
    greater than 8MHz, which is also refused by the tune command, in favour
    of using the default bandwidth setting 8 for any bandwidths greater than
    7MHz.
    
    Link: https://lore.kernel.org/linux-media/trinity-d0015ea1-1da5-4c7d-a75b-781fb26dc339-1641509387112@3c-app-gmx-bap68
    Fixes: 98c65a3dac95 ("media: si2157: add support for 1.7MHz and 6.1 MHz")
    Reported-by: Robert Schlabbach <robert_s@gmx.net>
    Signed-off-by: Robert Schlabbach <robert_s@gmx.net>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

commit a89eeb9937a0124e609e9355cd48cdfe35c8b8b7
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Dec 27 17:42:43 2021 +0100

    media: atomisp: Do not define input_system_cfg2400_t twice
    
    When CONFIG_VIDEO_ATOMISP_ISP2401 is disabled, clang warns:
    
    ./drivers/staging/media/atomisp//pci/isp2400_input_system_local.h:32:40:
    error: redefinition of typedef 'input_system_cfg2400_t' is a C11 feature
    [-Werror,-Wtypedef-redefinition]
    typedef struct input_system_cfg2400_s           input_system_cfg2400_t;
                                                    ^
    ./drivers/staging/media/atomisp//pci/input_system_local.h:22:40: note:
    previous definition is here
    typedef struct input_system_cfg2400_s           input_system_cfg2400_t;
                                                    ^
    1 error generated.
    
    input_system_cfg2400_t's typedef was copied from
    isp2400_input_system_local.h to input_system_local.h, rather than moved.
    Remove the one in isp2400_input_system_local.h so that there is no more
    warning, which can break the build under -Werror.
    
    Link: https://github.com/ClangBuiltLinux/linux/issues/1557
    
    Link: https://lore.kernel.org/linux-media/20211227164243.2329724-1-nathan@kernel.org
    Fixes: 4005ecee616a ("media: atomisp: shift some structs from input_system_local")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

commit 6ef295e34297433c78ea02dfcf1c649a769050bb
Author: Matthew Auld <matthew.auld@intel.com>
Date:   Thu Jan 6 17:49:10 2022 +0000

    drm/i915/ttm: ensure we unmap when purging
    
    Purging can happen during swapping out, or directly invoked with the
    madvise ioctl. In such cases this doesn't involve a ttm move, which
    skips umapping the object.
    
    v2(Thomas):
    - add ttm_truncate helper, and just call into i915_ttm_move_notify() to
      handle the unmapping step
    
    Fixes: 213d50927763 ("drm/i915/ttm: Introduce a TTM i915 gem object backend")
    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220106174910.280616-4-matthew.auld@intel.com
    (cherry picked from commit ab4911b7d411ab2ef3b38322178b9138e156c393)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 8ee262ba79a19a4dba9949397b1cf5761679670c
Author: Matthew Auld <matthew.auld@intel.com>
Date:   Thu Jan 6 17:49:09 2022 +0000

    drm/i915/ttm: add unmap_virtual callback
    
    Ensure we call ttm_bo_unmap_virtual when releasing the pages.
    Importantly this should now handle the ttm swapping case, and all other
    places that already call into i915_ttm_move_notify().
    
    v2: fix up the selftest
    
    Fixes: cf3e3e86d779 ("drm/i915: Use ttm mmap handling for ttm bo's.")
    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220106174910.280616-3-matthew.auld@intel.com
    (cherry picked from commit 903e0387270eef14a711c0feb23b7bf62d2480df)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 03ee5956781b2245b1c77334ecdea6386fd3bfba
Author: Matthew Auld <matthew.auld@intel.com>
Date:   Thu Jan 6 17:49:08 2022 +0000

    drm/i915/ttm: only fault WILLNEED objects
    
    Don't attempt to fault and re-populate purged objects. By some fluke
    this passes the dontneed-after-mmap IGT, but for the wrong reasons.
    
    Fixes: cf3e3e86d779 ("drm/i915: Use ttm mmap handling for ttm bo's.")
    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220106174910.280616-2-matthew.auld@intel.com
    (cherry picked from commit f3cb4a2de5410147b53e53416a3af0ffe26b5f4e)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit 4c2602ba8d74c35d550ed3d518809c697de08d88
Author: Matthew Auld <matthew.auld@intel.com>
Date:   Thu Jan 6 17:49:07 2022 +0000

    drm/i915: don't call free_mmap_offset when purging
    
    The TTM backend is in theory the only user here(also purge should only
    be called once we have dropped the pages), where it is setup at object
    creation and is only removed once the object is destroyed. Also
    resetting the node here might be iffy since the ttm fault handler
    uses the stored fake offset to determine the page offset within the pages
    array.
    
    This also blows up in the dontneed-before-mmap test, since the
    expectation is that the vma_node will live on, until the object is
    destroyed:
    
    <2> [749.062902] kernel BUG at drivers/gpu/drm/i915/gem/i915_gem_ttm.c:943!
    <4> [749.062923] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
    <4> [749.062928] CPU: 0 PID: 1643 Comm: gem_madvise Tainted: G     U  W         5.16.0-rc8-CI-CI_DRM_11046+ #1
    <4> [749.062933] Hardware name: Gigabyte Technology Co., Ltd. GB-Z390 Garuda/GB-Z390 Garuda-CF, BIOS IG1c 11/19/2019
    <4> [749.062937] RIP: 0010:i915_ttm_mmap_offset.cold.35+0x5b/0x5d [i915]
    <4> [749.063044] Code: 00 48 c7 c2 a0 23 4e a0 48 c7 c7 26 df 4a a0 e8 95 1d d0 e0 bf 01 00 00 00 e8 8b ec cf e0 31 f6 bf 09 00 00 00 e8 5f 30 c0 e0 <0f> 0b 48 c7 c1 24 4b 56 a0 ba 5b 03 00 00 48 c7 c6 c0 23 4e a0 48
    <4> [749.063052] RSP: 0018:ffffc90002ab7d38 EFLAGS: 00010246
    <4> [749.063056] RAX: 0000000000000240 RBX: ffff88811f2e61c0 RCX: 0000000000000006
    <4> [749.063060] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000009
    <4> [749.063063] RBP: ffffc90002ab7e58 R08: 0000000000000001 R09: 0000000000000001
    <4> [749.063067] R10: 000000000123d0f8 R11: ffffc90002ab7b20 R12: ffff888112a1a000
    <4> [749.063071] R13: 0000000000000004 R14: ffff88811f2e61c0 R15: ffff888112a1a000
    <4> [749.063074] FS:  00007f6e5fcad500(0000) GS:ffff8884ad600000(0000) knlGS:0000000000000000
    <4> [749.063078] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    <4> [749.063081] CR2: 00007efd264e39f0 CR3: 0000000115fd6005 CR4: 00000000003706f0
    <4> [749.063085] Call Trace:
    <4> [749.063087]  <TASK>
    <4> [749.063089]  __assign_mmap_offset+0x41/0x300 [i915]
    <4> [749.063171]  __assign_mmap_offset_handle+0x159/0x270 [i915]
    <4> [749.063248]  ? i915_gem_dumb_mmap_offset+0x70/0x70 [i915]
    <4> [749.063325]  drm_ioctl_kernel+0xae/0x140
    <4> [749.063330]  drm_ioctl+0x201/0x3d0
    <4> [749.063333]  ? i915_gem_dumb_mmap_offset+0x70/0x70 [i915]
    <4> [749.063409]  ? do_user_addr_fault+0x200/0x670
    <4> [749.063415]  __x64_sys_ioctl+0x6d/0xa0
    <4> [749.063419]  do_syscall_64+0x3a/0xb0
    <4> [749.063423]  entry_SYSCALL_64_after_hwframe+0x44/0xae
    <4> [749.063428] RIP: 0033:0x7f6e5f100317
    
    Testcase: igt/gem_madvise/dontneed-before-mmap
    Fixes: cf3e3e86d779 ("drm/i915: Use ttm mmap handling for ttm bo's.")
    Signed-off-by: Matthew Auld <matthew.auld@intel.com>
    Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220106174910.280616-1-matthew.auld@intel.com
    (cherry picked from commit 658a0c632625e1db51837ff754fe18a6a7f2ccf8)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit f9535d28ac93c3cc326f7215fccd0abe1d3a6083
Author: Juston Li <juston.li@intel.com>
Date:   Thu Jan 6 12:02:36 2022 -0800

    drm/i915/pxp: Hold RPM wakelock during PXP unbind
    
    Similar to commit b8d8436840ca ("drm/i915/gt: Hold RPM wakelock during
    PXP suspend") but to fix the same warning for unbind during shutdown:
    
    ------------[ cut here ]------------
    RPM wakelock ref not held during HW access
    WARNING: CPU: 0 PID: 4139 at drivers/gpu/drm/i915/intel_runtime_pm.h:115
    gen12_fwtable_write32+0x1b7/0
    Modules linked in: 8021q ccm rfcomm cmac algif_hash algif_skcipher
    af_alg uinput snd_hda_codec_hdmi vf industrialio iwl7000_mac80211
    cros_ec_sensorhub lzo_rle lzo_compress zram iwlwifi cfg80211 joydev
    CPU: 0 PID: 4139 Comm: halt Tainted: G     U  W
    5.10.84 #13 344e11e079c4a03940d949e537eab645f6
    RIP: 0010:gen12_fwtable_write32+0x1b7/0x200
    Code: 48 c7 c7 fc b3 b5 89 31 c0 e8 2c f3 ad ff 0f 0b e9 04 ff ff ff c6
    05 71 e9 1d 01 01 48 c7 c7 d67
    RSP: 0018:ffffa09ec0bb3bb0 EFLAGS: 00010246
    RAX: 12dde97bbd260300 RBX: 00000000000320f0 RCX: ffffffff89e60ea0
    RDX: 0000000000000000 RSI: 00000000ffffdfff RDI: ffffffff89e60e70
    RBP: ffffa09ec0bb3bd8 R08: 0000000000000000 R09: ffffa09ec0bb3950
    R10: 00000000ffffdfff R11: ffffffff89e91160 R12: 0000000000000000
    R13: 0000000028121969 R14: ffff9515c32f0990 R15: 0000000040000000
    FS:  0000790dcf225740(0000) GS:ffff951737800000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 000058b25efae147 CR3: 0000000133ea6001 CR4: 0000000000770ef0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
    PKRU: 55555554
    Call Trace:
     intel_pxp_fini_hw+0x2f/0x39
     i915_pxp_tee_component_unbind+0x1c/0x42
     component_unbind+0x32/0x48
     component_unbind_all+0x80/0x9d
     take_down_master+0x24/0x36
     component_master_del+0x56/0x70
     mei_pxp_remove+0x2c/0x68
     mei_cl_device_remove+0x35/0x68
     device_release_driver_internal+0x100/0x1a1
     mei_cl_bus_remove_device+0x21/0x79
     mei_cl_bus_remove_devices+0x3b/0x51
     mei_stop+0x3b/0xae
     mei_me_shutdown+0x23/0x58
     device_shutdown+0x144/0x1d3
     kernel_power_off+0x13/0x4c
     __se_sys_reboot+0x1d4/0x1e9
     do_syscall_64+0x43/0x55
     entry_SYSCALL_64_after_hwframe+0x44/0xa9
    RIP: 0033:0x790dcf316273
    Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00
    00 89 fa be 69 19 12 28 bf ad8
    RSP: 002b:00007ffca0df9198 EFLAGS: 00000202 ORIG_RAX: 00000000000000a9
    RAX: ffffffffffffffda RBX: 000000004321fedc RCX: 0000790dcf316273
    RDX: 000000004321fedc RSI: 0000000028121969 RDI: 00000000fee1dead
    RBP: 00007ffca0df9200 R08: 0000000000000007 R09: 0000563ce8cd8970
    R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffca0df9308
    R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000003
    ---[ end trace 2f501b01b348f114 ]---
    ACPI: Preparing to enter system sleep state S5
    reboot: Power down
    
    Changes since v1:
     - Rebase to latest drm-tip
    
    Fixes: 0cfab4cb3c4e ("drm/i915/pxp: Enable PXP power management")
    Suggested-by: Lee Shawn C <shawn.c.lee@intel.com>
    Signed-off-by: Juston Li <juston.li@intel.com>
    Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
    Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20220106200236.489656-2-juston.li@intel.com
    (cherry picked from commit 57ded5fc98b11d76dae505ca3591b61c9dbbbda7)
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

commit f66229aa355f7e0dc0dc20cbc1f4d45c3176eed2
Merge: 2e88c6a805fc5 f517ba4924ad0
Author: Takashi Iwai <tiwai@suse.de>
Date:   Mon Jan 10 14:33:42 2022 +0100

    Merge tag 'asoc-v5.17-2' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus
    
    ASoC: Updates for v5.17
    
    A few more updates for v5.17, nothing hugely stand out in the few days
    since the initial pull request was sent.

commit 19629ae482f1800b50a5bdf2504ac57171d2bb82
Merge: 44ea62813f0ab 80bb73a9fbcde
Author: Mark Brown <broonie@kernel.org>
Date:   Mon Jan 10 13:00:14 2022 +0000

    Merge branch 'for-5.16' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi into spi-5.17
    
    One small fix that didn't get sent separately.

commit 35e13e9da9afbce13c1d36465504ece4e65f24fe
Merge: 6629c07699263 1a5620671a1b6
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Jan 10 13:57:17 2022 +0100

    Merge branch 'clocksource' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu into timers/core
    
    Pull clocksource watchdog updates from Paul McKenney:
    
     - Avoid accidental unstable marking of clocksources by rejecting
       clocksource measurements where the source of the skew is the delay
       reading reference clocksource itself.  This change avoids many of the
       current false positives caused by epic cache-thrashing workloads.
    
     - Reduce the default clocksource_watchdog() retries to 2, thus offsetting
       the increased overhead due to #1 above rereading the reference
       clocksource.
    
    Link: https://lore.kernel.org/lkml/20220105001723.GA536708@paulmck-ThinkPad-P17-Gen-1

commit 67d50b5f9114ae55d45e08e1fd1d6ae152622bf3
Merge: 0422fe2666aea cd448b24c621b
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Jan 10 13:55:41 2022 +0100

    Merge tag 'irqchip-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/core
    
    Pull irqchip updates from Marc Zyngier:
    
     - Fix GICv3 redistributor table reservation with RT across kexec
    
     - Fix GICv4.1 redistributor view of the VPE table across kexec
    
     - Add support for extra interrupts on spear-shirq
    
     - Make obtaining some interrupts optional for the Renesas drivers
    
     - Various cleanups and bug fixes
    
    Link: https://lore.kernel.org/lkml/20220108130807.4109738-1-maz@kernel.org

commit 6629c0769926306454b113effe1aad243bd49bde
Merge: 2585cf9dfaadd 7647204c2e81b
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Jan 10 13:53:16 2022 +0100

    Merge tag 'timers-v5.17-rc1' of https://git.linaro.org/people/daniel.lezcano/linux into timers/core
    
    Pull clocksource/events updates from Daniel Lezcano:
    
     - Refactor resource allocation on the Exynos_mct driver without
       functional changes (Marek Szyprowski)
    
     - Add imx8ulp compatible string for NPX TPM driver (Jacky Bai)
    
     - Fix comma introduced by error by replacing it by the initial
       semicolon on the Exynos_mct (Will Deacon)
    
     - Add OSTM driver support on Renesas. The reset line must be
       deasserted before accessing the registers. This change depends on an
       external change resulting in a shared immutable branch
       'reset/of-get-optional-exclusive' from
       git://git.pengutronix.de/pza/linux (Biju Das)
    
     - Make the OSTM Kconfig option visible to user in order to let him
       disable it when ARM architected timers is enabled (Biju Das)
    
     - Tag two variables on iMX sysctr _ro_afterinit (Peng Fan)
    
     - Set the cpumask to cpu_possible_mask in order to have full benefit
       of the DYNIRQ flag on iMX sysctr (Peng Fan)
    
     - Tag __maybe_unused a variable in the Pistachio timer driver in order
       to fix a warning reported by the kernel test robot (Drew Fustini)
    
     - Add MStar MSC313e timer support and the ssd20xd-based variant, as
       well as the DT bindings (Romain Perier)
    
     - Remove the incompatible compatible string for the rk3066 (Johan
       Jonker)
    
     - Fix dts_check warnings on the cadence ttc driver by adding the power
       domain bindings (Michal Simek)
    
    Link: https://lore.kernel.org/lkml/e093c706-c98d-29ee-0102-78b6d41c6164@linaro.org

commit 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7
Author: Juan Vazquez <juvazq@linux.microsoft.com>
Date:   Sat Jan 8 16:17:58 2022 -0800

    scsi: storvsc: Fix storvsc_queuecommand() memory leak
    
    Fix possible memory leak in error path of storvsc_queuecommand() when
    DMA mapping fails.
    
    Signed-off-by: Juan Vazquez <juvazq@linux.microsoft.com>
    Reviewed-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
    Link: https://lore.kernel.org/r/20220109001758.6401-1-juvazq@linux.microsoft.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit 16f2f4e679cfdaa9552574484f104014908a76c6
Author: David Howells <dhowells@redhat.com>
Date:   Fri Aug 27 15:19:34 2021 +0100

    nfs: Implement cache I/O by accessing the cache directly
    
    Move NFS to using fscache DIO API instead of the old upstream I/O API as
    that has been removed.  This is a stopgap solution as the intention is that
    at sometime in the future, the cache will move to using larger blocks and
    won't be able to store individual pages in order to deal with the potential
    for data corruption due to the backing filesystem being able insert/remove
    bridging blocks of zeros into its extent list[1].
    
    NFS then reads and writes cache pages synchronously and one page at a time.
    
    The preferred change would be to use the netfs lib, but the new I/O API can
    be used directly.  It's just that as the cache now needs to track data for
    itself, caching blocks may exceed page size...
    
    This code is somewhat borrowed from my "fallback I/O" patchset[2].
    
    Changes
    =======
    ver #3:
     - Restore lost =n fallback for nfs_fscache_release_page()[2].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: Dave Wysochanski <dwysocha@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    cc: Trond Myklebust <trond.myklebust@hammerspace.com>
    cc: Anna Schumaker <anna.schumaker@netapp.com>
    cc: linux-nfs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/YO17ZNOcq+9PajfQ@mit.edu [1]
    Link: https://lore.kernel.org/r/202112100957.2oEDT20W-lkp@intel.com/ [2]
    Link: https://lore.kernel.org/r/163189108292.2509237.12615909591150927232.stgit@warthog.procyon.org.uk/ [2]
    Link: https://lore.kernel.org/r/163906981318.143852.17220018647843475985.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967184451.1823006.6450645559828329590.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021577632.640689.11069627070150063812.stgit@warthog.procyon.org.uk/ # v4

commit a6b5a28eb56c3f4988f7ff5290b954ba296e309a
Author: Dave Wysochanski <dwysocha@redhat.com>
Date:   Sat Nov 14 13:43:54 2020 -0500

    nfs: Convert to new fscache volume/cookie API
    
    Change the nfs filesystem to support fscache's indexing rewrite and
    reenable caching in nfs.
    
    The following changes have been made:
    
     (1) The fscache_netfs struct is no more, and there's no need to register
         the filesystem as a whole.
    
     (2) The session cookie is now an fscache_volume cookie, allocated with
         fscache_acquire_volume().  That takes three parameters: a string
         representing the "volume" in the index, a string naming the cache to
         use (or NULL) and a u64 that conveys coherency metadata for the
         volume.
    
         For nfs, I've made it render the volume name string as:
    
            "nfs,<ver>,<family>,<address>,<port>,<fsidH>,<fsidL>*<,param>[,<uniq>]"
    
     (3) The fscache_cookie_def is no more and needed information is passed
         directly to fscache_acquire_cookie().  The cache no longer calls back
         into the filesystem, but rather metadata changes are indicated at
         other times.
    
         fscache_acquire_cookie() is passed the same keying and coherency
         information as before.
    
     (4) fscache_enable/disable_cookie() have been removed.
    
         Call fscache_use_cookie() and fscache_unuse_cookie() when a file is
         opened or closed to prevent a cache file from being culled and to keep
         resources to hand that are needed to do I/O.
    
         If a file is opened for writing, we invalidate it with
         FSCACHE_INVAL_DIO_WRITE in lieu of doing writeback to the cache,
         thereby making it cease caching until all currently open files are
         closed.  This should give the same behaviour as the uptream code.
         Making the cache store local modifications isn't straightforward for
         NFS, so that's left for future patches.
    
     (5) fscache_invalidate() now needs to be given uptodate auxiliary data and
         a file size.  It also takes a flag to indicate if this was due to a
         DIO write.
    
     (6) Call nfs_fscache_invalidate() with FSCACHE_INVAL_DIO_WRITE on a file
         to which a DIO write is made.
    
     (7) Call fscache_note_page_release() from nfs_release_page().
    
     (8) Use a killable wait in nfs_vm_page_mkwrite() when waiting for
         PG_fscache to be cleared.
    
     (9) The functions to read and write data to/from the cache are stubbed out
         pending a conversion to use netfslib.
    
    Changes
    =======
    ver #3:
     - Added missing =n fallback for nfs_fscache_release_file()[1][2].
    
    ver #2:
     - Use gfpflags_allow_blocking() rather than using flag directly.
     - fscache_acquire_volume() now returns errors.
     - Remove NFS_INO_FSCACHE as it's no longer used.
     - Need to unuse a cookie on file-release, not inode-clear.
    
    Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
    Co-developed-by: David Howells <dhowells@redhat.com>
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: Dave Wysochanski <dwysocha@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    cc: Trond Myklebust <trond.myklebust@hammerspace.com>
    cc: Anna Schumaker <anna.schumaker@netapp.com>
    cc: linux-nfs@vger.kernel.org
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/202112100804.nksO8K4u-lkp@intel.com/ [1]
    Link: https://lore.kernel.org/r/202112100957.2oEDT20W-lkp@intel.com/ [2]
    Link: https://lore.kernel.org/r/163819668938.215744.14448852181937731615.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906979003.143852.2601189243864854724.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967182112.1823006.7791504655391213379.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021575950.640689.12069642327533368467.stgit@warthog.procyon.org.uk/ # v4

commit 93c846143d8630d1fd465b69703b0f0021a543dc
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 18 09:06:42 2020 +0000

    9p: Copy local writes to the cache when writing to the server
    
    When writing to the server from v9fs_vfs_writepage(), copy the data to the
    cache object too.
    
    To make this possible, the cookie must have its active users count
    incremented when the page is dirtied and kept incremented until we manage
    to clean up all the pages.  This allows the writeback to take place after
    the last file struct is released.
    
    This is done by taking a use on the cookie in v9fs_set_page_dirty() if we
    haven't already done so (controlled by the I_PINNING_FSCACHE_WB flag) and
    dropping the pin in v9fs_write_inode() if __writeback_single_inode() clears
    all the outstanding dirty pages (conveyed by the unpinned_fscache_wb flag
    in the writeback_control struct).
    
    Inode eviction must also clear the flag after truncating away all the
    outstanding pages.
    
    In the future this will be handled more gracefully by netfslib.
    
    Changes
    =======
    ver #3:
     - Canonicalise the coherency data to make it endianness-independent.
    
    ver #2:
     - Fix an unused-var warning due to CONFIG_9P_FSCACHE=n[1].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Tested-by: Dominique Martinet <asmadeus@codewreck.org>
    cc: Eric Van Hensbergen <ericvh@gmail.com>
    cc: Latchesar Ionkov <lucho@ionkov.net>
    cc: v9fs-developer@lists.sourceforge.net
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819667027.215744.13815687931204222995.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906978015.143852.10646669694345706328.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967180760.1823006.5831751873616248910.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021574522.640689.13849966660182529125.stgit@warthog.procyon.org.uk/ # v4

commit 24e42e32d347f0787a6f99aeb590f3aaa7221093
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 18 09:06:42 2020 +0000

    9p: Use fscache indexing rewrite and reenable caching
    
    Change the 9p filesystem to take account of the changes to fscache's
    indexing rewrite and reenable caching in 9p.
    
    The following changes have been made:
    
     (1) The fscache_netfs struct is no more, and there's no need to register
         the filesystem as a whole.
    
     (2) The session cookie is now an fscache_volume cookie, allocated with
         fscache_acquire_volume().  That takes three parameters: a string
         representing the "volume" in the index, a string naming the cache to
         use (or NULL) and a u64 that conveys coherency metadata for the
         volume.
    
         For 9p, I've made it render the volume name string as:
    
            "9p,<devname>,<cachetag>"
    
         where the cachetag is replaced by the aname if it wasn't supplied.
    
         This probably needs rethinking a bit as the aname can have slashes in
         it.  It might be better to hash the cachetag and use the hash or I
         could substitute commas for the slashes or something.
    
     (3) The fscache_cookie_def is no more and needed information is passed
         directly to fscache_acquire_cookie().  The cache no longer calls back
         into the filesystem, but rather metadata changes are indicated at
         other times.
    
         fscache_acquire_cookie() is passed the same keying and coherency
         information as before.
    
     (4) The functions to set/reset/flush cookies are removed and
         fscache_use_cookie() and fscache_unuse_cookie() are used instead.
    
         fscache_use_cookie() is passed a flag to indicate if the cookie is
         opened for writing.  fscache_unuse_cookie() is passed updates for the
         metadata if we changed it (ie. if the file was opened for writing).
    
         These are called when the file is opened or closed.
    
     (5) wait_on_page_bit[_killable]() is replaced with the specific wait
         functions for the bits waited upon.
    
     (6) I've got rid of some of the 9p-specific cache helper functions and
         called things like fscache_relinquish_cookie() directly as they'll
         optimise away if v9fs_inode_cookie() returns an unconditional NULL
         (which will be the case if CONFIG_9P_FSCACHE=n).
    
     (7) v9fs_vfs_setattr() is made to call fscache_resize() to change the size
         of the cache object.
    
    Notes:
    
     (A) We should call fscache_invalidate() if we detect that the server's
         copy of a file got changed by a third party, but I don't know where to
         do that.  We don't need to do that when allocating the cookie as we
         get a check-and-invalidate when we initially bind to the cache object.
    
     (B) The copy-to-cache-on-writeback side of things will be handled in
         separate patch.
    
    Changes
    =======
    ver #3:
     - Canonicalise the cookie key and coherency data to make them
       endianness-independent.
    
    ver #2:
     - Use gfpflags_allow_blocking() rather than using flag directly.
     - fscache_acquire_volume() now returns errors.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Tested-by: Dominique Martinet <asmadeus@codewreck.org>
    cc: Eric Van Hensbergen <ericvh@gmail.com>
    cc: Latchesar Ionkov <lucho@ionkov.net>
    cc: v9fs-developer@lists.sourceforge.net
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819664645.215744.1555314582005286846.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906975017.143852.3459573173204394039.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967178512.1823006.17377493641569138183.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021573143.640689.3977487095697717967.stgit@warthog.procyon.org.uk/ # v4

commit 51500b71d500f251037ed339047a4d9e7d7e295b
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date:   Thu Jan 6 10:46:11 2022 +0100

    x86/hyperv: Properly deal with empty cpumasks in hyperv_flush_tlb_multi()
    
    KASAN detected the following issue:
    
     BUG: KASAN: slab-out-of-bounds in hyperv_flush_tlb_multi+0xf88/0x1060
     Read of size 4 at addr ffff8880011ccbc0 by task kcompactd0/33
    
     CPU: 1 PID: 33 Comm: kcompactd0 Not tainted 5.14.0-39.el9.x86_64+debug #1
     Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine,
         BIOS Hyper-V UEFI Release v4.0 12/17/2019
     Call Trace:
      dump_stack_lvl+0x57/0x7d
      print_address_description.constprop.0+0x1f/0x140
      ? hyperv_flush_tlb_multi+0xf88/0x1060
      __kasan_report.cold+0x7f/0x11e
      ? hyperv_flush_tlb_multi+0xf88/0x1060
      kasan_report+0x38/0x50
      hyperv_flush_tlb_multi+0xf88/0x1060
      flush_tlb_mm_range+0x1b1/0x200
      ptep_clear_flush+0x10e/0x150
    ...
     Allocated by task 0:
      kasan_save_stack+0x1b/0x40
      __kasan_kmalloc+0x7c/0x90
      hv_common_init+0xae/0x115
      hyperv_init+0x97/0x501
      apic_intr_mode_init+0xb3/0x1e0
      x86_late_time_init+0x92/0xa2
      start_kernel+0x338/0x3eb
      secondary_startup_64_no_verify+0xc2/0xcb
    
     The buggy address belongs to the object at ffff8880011cc800
      which belongs to the cache kmalloc-1k of size 1024
     The buggy address is located 960 bytes inside of
      1024-byte region [ffff8880011cc800, ffff8880011ccc00)
    
    'hyperv_flush_tlb_multi+0xf88/0x1060' points to
    hv_cpu_number_to_vp_number() and '960 bytes' means we're trying to get
    VP_INDEX for CPU#240. 'nr_cpus' here is exactly 240 so we're trying to
    access past hv_vp_index's last element. This can (and will) happen
    when 'cpus' mask is empty and cpumask_last() will return '>=nr_cpus'.
    
    Commit ad0a6bad4475 ("x86/hyperv: check cpu mask after interrupt has
    been disabled") tried to deal with empty cpumask situation but
    apparently didn't fully fix the issue.
    
    'cpus' cpumask which is passed to hyperv_flush_tlb_multi() is
    'mm_cpumask(mm)' (which is '&mm->cpu_bitmap'). This mask changes every
    time the particular mm is scheduled/unscheduled on some CPU (see
    switch_mm_irqs_off()), disabling IRQs on the CPU which is performing remote
    TLB flush has zero influence on whether the particular process can get
    scheduled/unscheduled on _other_ CPUs so e.g. in the case where the mm was
    scheduled on one other CPU and got unscheduled during
    hyperv_flush_tlb_multi()'s execution will lead to cpumask becoming empty.
    
    It doesn't seem that there's a good way to protect 'mm_cpumask(mm)'
    from changing during hyperv_flush_tlb_multi()'s execution. It would be
    possible to copy it in the very beginning of the function but this is a
    waste. It seems we can deal with changing cpumask just fine.
    
    When 'cpus' cpumask changes during hyperv_flush_tlb_multi()'s
    execution, there are two possible issues:
    - 'Under-flushing': we will not flush TLB on a CPU which got added to
    the mask while hyperv_flush_tlb_multi() was already running. This is
    not a problem as this is equal to mm getting scheduled on that CPU
    right after TLB flush.
    - 'Over-flushing': we may flush TLB on a CPU which is already cleared
    from the mask. First, extra TLB flush preserves correctness. Second,
    Hyper-V's TLB flush hypercall takes 'mm->pgd' argument so Hyper-V may
    avoid the flush if CR3 doesn't match.
    
    Fix the immediate issue with cpumask_last()/hv_cpu_number_to_vp_number()
    and remove the pointless cpumask_empty() check from the beginning of the
    function as it really doesn't protect anything. Also, avoid the hypercall
    altogether when 'flush->processor_mask' ends up being empty.
    
    Fixes: ad0a6bad4475 ("x86/hyperv: check cpu mask after interrupt has been disabled")
    Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
    Reviewed-by: Michael Kelley <mikelley@microsoft.com>
    Link: https://lore.kernel.org/r/20220106094611.1404218-1-vkuznets@redhat.com
    Signed-off-by: Wei Liu <wei.liu@kernel.org>

commit d12013c80e1524e3e85c01d50adcefd70b1a8b6f
Merge: 73d86812a3596 5e8ba485b2522
Author: Petr Mladek <pmladek@suse.com>
Date:   Mon Jan 10 12:15:08 2022 +0100

    Merge branch 'console-registration-cleanup' into for-linus

commit 3375aa77135f6aeb1107ed839a2050a4118444bc
Author: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date:   Mon Dec 27 19:00:26 2021 +0100

    ARM: dts: meson8b: Fix the UART device-tree schema validation
    
    The dt-bindings for the UART controller only allow the following values
    for Meson8 SoCs:
    - "amlogic,meson8b-uart", "amlogic,meson-ao-uart"
    - "amlogic,meson8b-uart"
    
    Use the correct fallback compatible string "amlogic,meson-ao-uart" for
    AO UART. Drop the "amlogic,meson-uart" compatible string from the EE
    domain UART controllers.
    
    Also update the order of the clocks to match the order defined in the
    yaml bindings.
    
    Fixes: b02d6e73f5fc96 ("ARM: dts: meson8b: use stable UART bindings with correct gate clock")
    Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20211227180026.4068352-4-martin.blumenstingl@googlemail.com

commit 57007bfb5469ba31cacf69d52195e8b75f43e32d
Author: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date:   Mon Dec 27 19:00:25 2021 +0100

    ARM: dts: meson8: Fix the UART device-tree schema validation
    
    The dt-bindings for the UART controller only allow the following values
    for Meson8 SoCs:
    - "amlogic,meson8-uart", "amlogic,meson-ao-uart"
    - "amlogic,meson8-uart"
    
    Use the correct fallback compatible string "amlogic,meson-ao-uart" for
    AO UART. Drop the "amlogic,meson-uart" compatible string from the EE
    domain UART controllers.
    
    Also update the order of the clocks to match the order defined in the
    yaml schema.
    
    Fixes: 6ca77502050eff ("ARM: dts: meson8: use stable UART bindings with correct gate clock")
    Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20211227180026.4068352-3-martin.blumenstingl@googlemail.com

commit 5225e1b87432dcf0d0fc3440824b91d04c1d6cc1
Author: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date:   Mon Dec 27 19:00:24 2021 +0100

    ARM: dts: meson: Fix the UART compatible strings
    
    The dt-bindings for the UART controller only allow the following values
    for Meson6 SoCs:
    - "amlogic,meson6-uart", "amlogic,meson-ao-uart"
    - "amlogic,meson6-uart"
    
    Use the correct fallback compatible string "amlogic,meson-ao-uart" for
    AO UART. Drop the "amlogic,meson-uart" compatible string from the EE
    domain UART controllers.
    
    Fixes: ec9b59162fd831 ("ARM: dts: meson6: use stable UART bindings")
    Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
    Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
    Link: https://lore.kernel.org/r/20211227180026.4068352-2-martin.blumenstingl@googlemail.com

commit 081c8919b02bc1077279cd03972d7ec6f53a6c6b
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 10:18:19 2022 +0100

    Documentation: remove trivial tree
    
    As has been discussed some time ago on ksumitt-discuss@ mailinglist,
    the need for trivial tree diminished over time as all the tooling and
    processess became much more mature and it's quite natural these days
    for trivial patches to flow through subsystem trees anyway, so the
    spin-off of a trivial tree doesn't make sense any more, and is not worth
    the merge conflicts it might sometimes create.
    
    So remove any mentions of it from kernel documentation for good.
    
    Link: https://lore.kernel.org/all/nycvar.YFH.7.76.2104222334290.18270@cbobk.fhfr.pm/
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit da0119a9123c73269657fc61f537223d6affef02
Merge: a9e6b3819b365 567617baac2a5 0b8bf9cb142da
Author: Borislav Petkov <bp@suse.de>
Date:   Mon Jan 10 10:07:00 2022 +0100

    Merge branches 'edac-misc' and 'edac-amd64' into edac-updates-for-v5.17
    
    Signed-off-by: Borislav Petkov <bp@suse.de>

commit cd598d21294e088c3c9e518a7e9098f94ae8cf6a
Merge: f7716563441ae 415e701cee522
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:59:32 2022 +0100

    Merge branch 'for-5.17/thrustmaster' into for-linus

commit f7716563441ae29cc91954a7744ff7bfdd344b2d
Merge: 50ae0cfc28c8a 33812fc7c8d77
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:58:34 2022 +0100

    Merge branch 'for-5.17/magicmouse' into for-linus
    
    - proper batter reporting for hid-magicmouse USB-connected devices (José Expósito)

commit 50ae0cfc28c8a98ded16bf7a47f8bbdbbf3702e1
Merge: 3551a3ff8229e 03dada294d083
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:57:51 2022 +0100

    Merge branch 'for-5.17/logitech' into for-linus
    
    - add Filipe Laíns as a code reviewer for hid-logitech family of drivers

commit 3551a3ff8229e15d2a4b47b8234923bc72da65ef
Merge: 906095af85e8b 33a5c27934517
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:56:57 2022 +0100

    Merge branch 'for-5.17/letsketch' into for-linus
    
    - new driver to support for LetSketch device (Hans de Goede)

commit 906095af85e8b2e53ee9f8c50b3dff365aa09df8
Merge: c524559acd5d0 d951ae1ce8033
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:56:27 2022 +0100

    Merge branch 'for-5.17/i2c-hid' into for-linus
    
    - PM wakeup support for i2c-hid driver (Matthias Kaehlcke)

commit c524559acd5d0903fa6e3b8e608bf5851de7217a
Merge: fce0d27584371 8590222e4b021
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:55:44 2022 +0100

    Merge branch 'for-5.17/hidraw' into for-linus
    
    - locking performance improvement for hidraw code (André Almeida)

commit fce0d275843712db6f9b611856f539da29ad5529
Merge: 8a2094d679d92 7f84e2439ed2e
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:54:31 2022 +0100

    Merge branch 'for-5.17/apple' into for-linus
    
    - Apple Magic Keyboard support improvements (José Expósito, Alex Henrie,
      Benjamin Berg)

commit 8a2094d679d921d104d3296528d4fa419702ce1c
Merge: 3809fe4798611 b60d3c803d760
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Mon Jan 10 09:49:13 2022 +0100

    Merge branch 'for-5.17/core' into for-linus
    
    - support for USI style pens (Tero Kristo, Mika Westerberg)
    - quirk for devices that need inverted X/Y axes (Alistair Francis)
    - small core code cleanups and deduplication (Benjamin Tissoires)

commit 3d966521a824082952990492442c7b486fefb48c
Author: Yuezhang.Mo <Yuezhang.Mo@sony.com>
Date:   Mon Aug 16 11:30:51 2021 +0800

    exfat: fix missing REQ_SYNC in exfat_update_bhs()
    
    If 'dirsync' is enabled, all directory updates within the
    filesystem should be done synchronously. exfat_update_bh()
    does as this, but exfat_update_bhs() does not.
    
    Reviewed-by: Andy.Wu <Andy.Wu@sony.com>
    Reviewed-by: Aoyama, Wataru <wataru.aoyama@sony.com>
    Reviewed-by: Kobayashi, Kento <Kento.A.Kobayashi@sony.com>
    Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>
    Signed-off-by: Yuezhang.Mo <Yuezhang.Mo@sony.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit c71510b3fa27f96840c5737d8a47dd7b370e376c
Author: Yuezhang.Mo <Yuezhang.Mo@sony.com>
Date:   Thu Dec 16 21:58:37 2021 +0900

    exfat: remove argument 'sector' from exfat_get_dentry()
    
    No any function uses argument 'sector', remove it.
    
    Reviewed-by: Andy.Wu <Andy.Wu@sony.com>
    Reviewed-by: Aoyama, Wataru <wataru.aoyama@sony.com>
    Acked-by: Sungjong Seo <sj1557.seo@samsung.com>
    Signed-off-by: Yuezhang.Mo <Yuezhang.Mo@sony.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit 1ed147e29e505de819aaa5b57919c25348f72e1f
Author: Namjae Jeon <linkinjeon@kernel.org>
Date:   Thu Nov 25 21:01:11 2021 +0900

    exfat: move super block magic number to magic.h
    
    Move exfat superblock magic number from local definition to magic.h.
    It is also needed by userspace programs that call fstatfs().
    
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit 92fba084b79e6bc7b12fc118209f1922c1a2df56
Author: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Date:   Mon Nov 22 22:02:37 2021 +0900

    exfat: fix i_blocks for files truncated over 4 GiB
    
    In exfat_truncate(), the computation of inode->i_blocks is wrong if
    the file is larger than 4 GiB because a 32-bit variable is used as a
    mask. This is fixed and simplified by using round_up().
    
    Also fix the same buggy computation in exfat_read_root() and another
    (correct) one in exfat_fill_inode(). The latter was fixed another way
    last month but can be simplified by using round_up() as well. See:
    
      commit 0c336d6e33f4 ("exfat: fix incorrect loading of i_blocks for
                            large files")
    
    Fixes: 98d917047e8b ("exfat: add file operations")
    Cc: stable@vger.kernel.org # v5.7+
    Suggested-by: Matthew Wilcox <willy@infradead.org>
    Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>
    Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit 7dee6f57d7f22a89dd214518c778aec448270d4c
Author: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Date:   Tue Nov 2 22:23:58 2021 +0100

    exfat: reuse exfat_inode_info variable instead of calling EXFAT_I()
    
    Also add a local "struct exfat_inode_info *ei" variable to
    exfat_truncate() to simplify the code.
    
    Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit 8cf058834b11c08b344fc4549b03d723f16c9241
Author: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Date:   Tue Nov 2 22:23:57 2021 +0100

    exfat: make exfat_find_location() static
    
    Make exfat_find_location() static.
    
    Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit 6fa96cd5ad7a0c8f3f3f6b2b5f062721e8f17a54
Author: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Date:   Tue Nov 2 22:23:56 2021 +0100

    exfat: fix typos in comments
    
    Fix typos in comments.
    
    Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit e21a28bbcc0c5dc8ab86af77edb530d6fc0c20ff
Author: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
Date:   Tue Nov 2 22:23:55 2021 +0100

    exfat: simplify is_valid_cluster()
    
    Simplify is_valid_cluster().
    
    Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com>
    Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>

commit f029cedb9bb5bab7f1bb3042be348f2dac0ee66e
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:33 2021 -0800

    MAINTAINERS: add entries for block layer documentation
    
    Include Documentation/block/ and Documentation/ABI/stable/sysfs-block in
    the "BLOCK LAYER" maintainers file entry.
    
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-9-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 208e4f9c0028e9181220460600b1df0bc677e796
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:32 2021 -0800

    docs: block: remove queue-sysfs.rst
    
    This has been replaced by Documentation/ABI/stable/sysfs-block, which is
    the correct place for sysfs documentation.
    
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-8-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 8bc2f7c67061cb39e317a45ad9870f529b1fb190
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:31 2021 -0800

    docs: sysfs-block: document virt_boundary_mask
    
    /sys/block/<disk>/queue/virt_boundary_mask is completely undocumented.
    Document it.
    
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-7-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 1163010418a7f0c60c309743498cb6c5cd828ecc
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:30 2021 -0800

    docs: sysfs-block: document stable_writes
    
    /sys/block/<disk>/queue/stable_writes is completely undocumented.
    Document it.
    
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-6-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 849ab826e10531f106846e8e9eeae8d00a198f6e
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:29 2021 -0800

    docs: sysfs-block: fill in missing documentation from queue-sysfs.rst
    
    sysfs documentation is supposed to go in Documentation/ABI/.
    However, /sys/block/<disk>/queue/* are documented in
    Documentation/block/queue-sysfs.rst, and sometimes redundantly in
    Documentation/ABI/stable/sysfs-block too.
    
    Let's consolidate this documentation into Documentation/ABI/.
    
    Therefore, copy the relevant docs from queue-sysfs.rst into sysfs-block.
    
    This primarily means adding the 25 missing files that were documented in
    queue-sysfs.rst only, as well as mentioning the RO/RW status of files.
    
    Documentation/ABI/ requires "Date" and "Contact" fields.  For the Date
    fields, I used the date of the commit which added support for each file.
    For the "Contact" fields, I used linux-block.
    
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-5-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 8b0551a74b4a9396a7f6ddb0c5f6f3c8465e9d45
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:28 2021 -0800

    docs: sysfs-block: add contact for nomerges
    
    The nomerges file was missing a "Contact" entry.  Use linux-block.
    
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-4-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 07c9093c429361dd405499b1e433e4170b81551f
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:27 2021 -0800

    docs: sysfs-block: sort alphabetically
    
    Sort the documentation for the files alphabetically by file path so that
    there is a logical order and it's clear where to add new files.
    
    With two small exceptions, this patch doesn't change the documentation
    itself and just reorders it:
    
    - In /sys/block/<disk>/<part>/stat, I replaced <part> with <partition>
      to be consistent with the other files.
    - The description for /sys/block/<disk>/<part>/stat referred to another
      file "above", which I reworded.
    
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Hannes Reinecke <hare@suse.de>
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-3-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit ae7a7a53498f452eb927cd4b4eed0bccded85ebf
Author: Eric Biggers <ebiggers@google.com>
Date:   Wed Dec 8 16:38:26 2021 -0800

    docs: sysfs-block: move to stable directory
    
    The block layer sysfs ABI is widely used by userspace software and is
    considered stable.
    
    Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
    Reviewed-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Link: https://lore.kernel.org/r/20211209003833.6396-2-ebiggers@kernel.org
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 9d497e2941c30a060ba62d5485b3bc9d91ffb09e
Author: Ming Lei <ming.lei@redhat.com>
Date:   Tue Jan 4 21:42:23 2022 +0800

    block: don't protect submit_bio_checks by q_usage_counter
    
    Commit cc9c884dd7f4 ("block: call submit_bio_checks under q_usage_counter")
    uses q_usage_counter to protect submit_bio_checks for avoiding IO after
    disk is deleted by del_gendisk().
    
    Turns out the protection isn't necessary, because once
    blk_mq_freeze_queue_wait() in del_gendisk() returns:
    
    1) all in-flight IO has been done
    
    2) all new IO will be failed in __bio_queue_enter() because
       q_usage_counter is dead, and GD_DEAD is set
    
    3) both disk and request queue instance are safe since caller of
    submit_bio() guarantees that the disk can't be closed.
    
    Once submit_bio_checks() needn't the protection of q_usage_counter, we can
    move submit_bio_checks before calling blk_mq_submit_bio() and
    ->submit_bio(). With this change, we needn't to throttle queue with
    holding one allocated request, then precise driver tag or request won't be
    wasted in throttling. Meantime we can unify the bio check for both bio
    based and request based driver.
    
    Cc: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Ming Lei <ming.lei@redhat.com>
    Link: https://lore.kernel.org/r/20220104134223.590803-1-ming.lei@redhat.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit 00f5117c5f785b95b13663e52dcdcf684a47d4e3
Author: Colin Ian King <colin.king@intel.com>
Date:   Sun Jan 9 19:45:58 2022 +0000

    hwmon: (nzxt-smart2) make array detect_fans_report static const
    
    Don't populate the read-only array detect_fans_report on the stack but
    instead it static const. Also makes the object code a little smaller.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Link: https://lore.kernel.org/r/20220109194558.45811-1-colin.i.king@gmail.com
    Signed-off-by: Guenter Roeck <linux@roeck-us.net>

commit 8650381f33fba33e162db2266ce74f1b87a2f71c
Author: Rob Herring <robh@kernel.org>
Date:   Fri Dec 3 16:45:23 2021 -0600

    dt-bindings: net: Add missing properties used in examples
    
    With 'unevaluatedProperties' support implemented, the following warnings
    are generated in the net bindings:
    
    Documentation/devicetree/bindings/net/qca,ar71xx.example.dt.yaml: ethernet@19000000: Unevaluated properties are not allowed ('qca,ethcfg' was unexpected)
    Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40028000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
    Documentation/devicetree/bindings/net/ti,cpsw-switch.example.dt.yaml: mdio@1000: Unevaluated properties are not allowed ('clocks', 'clock-names' were unexpected)
    Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.example.dt.yaml: mdio@f00: Unevaluated properties are not allowed ('clocks', 'clock-names' were unexpected)
    
    Add the missing properties/nodes as necessary.
    
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: "Andreas Färber" <afaerber@suse.de>
    Cc: Manivannan Sadhasivam <mani@kernel.org>
    Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
    Cc: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
    Cc: "G. Jaya Kumaran" <vineetha.g.jaya.kumaran@intel.com>
    Cc: Oleksij Rempel <o.rempel@pengutronix.de>
    Cc: Christophe Roullier <christophe.roullier@foss.st.com>
    Cc: Grygorii Strashko <grygorii.strashko@ti.com>
    Cc: netdev@vger.kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: linux-actions@lists.infradead.org
    Cc: linux-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20211206174153.2296977-1-robh@kernel.org

commit 1d01efaf1824aea57cbcf96b27d6f36441898a4b
Author: Rob Herring <robh@kernel.org>
Date:   Mon Dec 6 11:41:47 2021 -0600

    dt-bindings: net: snps,dwmac: Enable burst length properties for more compatibles
    
    With 'unevaluatedProperties' support implemented, the properties
    'snps,pbl', 'snps,txpbl', and 'snps,rxpbl' are not allowed in the
    examples for some of the DWMAC versions:
    
    Documentation/devicetree/bindings/net/intel,dwmac-plat.example.dt.yaml: ethernet@3a000000: Unevaluated properties are not allowed ('snps,pbl', 'mdio0' were unexpected)
    Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@5800a000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
    Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40028000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
    Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40027000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
    Documentation/devicetree/bindings/net/toshiba,visconti-dwmac.example.dt.yaml: ethernet@28000000: Unevaluated properties are not allowed ('snps,txpbl', 'snps,rxpbl', 'mdio0' were unexpected)
    
    This appears to be an oversight, so fix it by allowing the properties
    on the v3.50a, v4.10a, and v4.20a versions of the DWMAC.
    
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
    Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
    Cc: Jose Abreu <joabreu@synopsys.com>
    Cc: netdev@vger.kernel.org
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Thierry Reding <treding@nvidia.com>
    Link: https://lore.kernel.org/r/20211206174147.2296770-1-robh@kernel.org

commit ad31ce56c434bbd792f3ee79160cedaf20f7f238
Author: Rob Herring <robh@kernel.org>
Date:   Mon Dec 6 11:41:39 2021 -0600

    dt-bindings: net: mdio: Allow any child node name
    
    An MDIO bus can have devices other than ethernet PHYs on it, so it
    should allow for any node name rather than just 'ethernet-phy'.
    
    Cc: Andrew Lunn <andrew@lunn.ch>
    Cc: Heiner Kallweit <hkallweit1@gmail.com>
    Cc: Russell King <linux@armlinux.org.uk>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: Florian Fainelli <f.fainelli@gmail.com>
    Cc: netdev@vger.kernel.org
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Thierry Reding <treding@nvidia.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20211206174139.2296497-1-robh@kernel.org

commit 8aaaf2f3af2ae212428f4db1af34214225f5cec3
Merge: 208dd45d8d050 dd3ca4c5184ea
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 16:59:30 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
    
    Merge in fixes directly in prep for the 5.17 merge window.
    No conflicts.
    
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 15e2721b19acb1bfb18ac90775503b75d8aecbb2
Author: Christian Schoenebeck <linux_oss@crudebyte.com>
Date:   Thu Dec 30 14:23:18 2021 +0100

    net/9p: show error message if user 'msize' cannot be satisfied
    
    If user supplied a large value with the 'msize' option, then
    client would silently limit that 'msize' value to the maximum
    value supported by transport. That's a bit confusing for users
    of not having any indication why the preferred 'msize' value
    could not be satisfied.
    
    Link: https://lkml.kernel.org/r/783ba37c1566dd715b9a67d437efa3b77e3cd1a7.1640870037.git.linux_oss@crudebyte.com
    Reported-by: Vivek Goyal <vgoyal@redhat.com>
    Signed-off-by: Christian Schoenebeck <linux_oss@crudebyte.com>
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit deadd8746ec72bd6cbc351a004809f8a49a61d4b
Author: Christian Schoenebeck <linux_oss@crudebyte.com>
Date:   Tue Jan 4 13:53:59 2022 +0100

    MAINTAINERS: 9p: add Christian Schoenebeck as reviewer
    
    Volunteering as reviewer for 9p patches. As I am quite familiar with the
    9p code base in the Linux kernel already, plus being current maintainer
    of 9p in QEMU this move probably makes sense.
    
    Link: https://lkml.kernel.org/r/E1n4jXv-000445-GK@lizzy.crudebyte.com
    Signed-off-by: Christian Schoenebeck <linux_oss@crudebyte.com>
    [Dominique: reworded description]
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 3cb6ee991496b67ee284c6895a0ba007e2d7bac3
Author: Christian Brauner <brauner@kernel.org>
Date:   Mon Nov 29 12:44:34 2021 +0100

    9p: only copy valid iattrs in 9P2000.L setattr implementation
    
    The 9P2000.L setattr method v9fs_vfs_setattr_dotl() copies struct iattr
    values without checking whether they are valid causing unitialized
    values to be copied. The 9P2000 setattr method v9fs_vfs_setattr() method
    gets this right. Check whether struct iattr fields are valid first
    before copying in v9fs_vfs_setattr_dotl() too and make sure that all
    other fields are set to 0 apart from {g,u}id which should be set to
    INVALID_{G,U}ID. This ensure that they can be safely sent over the wire
    or printed for debugging later on.
    
    Link: https://lkml.kernel.org/r/20211129114434.3637938-1-brauner@kernel.org
    Link: https://lkml.kernel.org/r/000000000000a0d53f05d1c72a4c%40google.com
    Cc: Eric Van Hensbergen <ericvh@gmail.com>
    Cc: Latchesar Ionkov <lucho@ionkov.net>
    Cc: Dominique Martinet <asmadeus@codewreck.org>
    Cc: stable@kernel.org
    Cc: v9fs-developer@lists.sourceforge.net
    Reported-by: syzbot+dfac92a50024b54acaa4@syzkaller.appspotmail.com
    Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
    [Dominique: do not set a/mtime with just ATTR_A/MTIME as discussed]
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit a7a427d1543f89ad57fda5d6b9bb70f4cecb2fba
Author: Zhang Mingyu <zhang.mingyu@zte.com.cn>
Date:   Fri Nov 12 09:25:47 2021 +0000

    9p: Use BUG_ON instead of if condition followed by BUG.
    
    This issue was detected with the help of Coccinelle.
    
    Link: https://lkml.kernel.org/r/20211112092547.9153-1-zhang.mingyu@zte.com.cn
    Reported-by: Zeal Robot <zealci@zte.com.cn>
    Signed-off-by: Zhang Mingyu <zhang.mingyu@zte.com.cn>
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 019641d1b57dff018972b23c95e898f9ff18222f
Author: Thomas Weißschuh <linux@weissschuh.net>
Date:   Wed Nov 3 20:38:23 2021 +0100

    net/p9: load default transports
    
    Now that all transports are split into modules it may happen that no
    transports are registered when v9fs_get_default_trans() is called.
    When that is the case try to load more transports from modules.
    
    Link: https://lkml.kernel.org/r/20211103193823.111007-5-linux@weissschuh.net
    Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
    [Dominique: constify v9fs_get_trans_by_name argument as per patch1v2]
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 99aa673e2925c89a20eeb5477383c4f2e97d0146
Author: Thomas Weißschuh <linux@weissschuh.net>
Date:   Wed Nov 3 20:38:22 2021 +0100

    9p/xen: autoload when xenbus service is available
    
    Link: https://lkml.kernel.org/r/20211103193823.111007-4-linux@weissschuh.net
    Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 1c582c6dc4244d88f702dc3afd5b47225332edf6
Author: Thomas Weißschuh <linux@weissschuh.net>
Date:   Wed Nov 3 20:38:21 2021 +0100

    9p/trans_fd: split into dedicated module
    
    This allows these transports only to be used when needed.
    
    Link: https://lkml.kernel.org/r/20211103193823.111007-3-linux@weissschuh.net
    Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
    [Dominique: Kconfig NET_9P_FD: -depends VIRTIO, +default NET_9P]
    Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>

commit 0bbeb64cb063d746cdb2fdc8c1e3f4d51e268b23
Author: Qin Jian <qinjian@cqplus1.com>
Date:   Wed Dec 22 15:05:57 2021 +0800

    dt-bindings: vendor-prefixes: Add Sunplus
    
    Add vendor prefix for Sunplus Technology Co., Ltd. (http://www.sunplus.com)
    
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Qin Jian <qinjian@cqplus1.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/2e74a1339a5ea54d92fdc4d1998a2b169e23b82b.1640154492.git.qinjian@cqplus1.com

commit 208dd45d8d050360b46ded439a057bcc7cbf3b09
Author: Benjamin Yim <yan2228598786@gmail.com>
Date:   Sun Jan 9 21:08:24 2022 +0800

    tcp: tcp_send_challenge_ack delete useless param `skb`
    
    After this parameter is passed in, there is no usage, and deleting it will
     not bring any impact.
    
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Benjamin Yim <yan2228598786@gmail.com>
    Link: https://lore.kernel.org/r/20220109130824.2776-1-yan2228598786@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 0959a82ab3e569509cbab111564bea1c916bb204
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 19:49:09 2022 +0100

    net/qla3xxx: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
    1.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/3011689e8c77d49d7e44509d5a8241320ec408c5.1641754134.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7ac2d77c97d0a0eb789dd13b3c1718eb0b3180f7
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 17:04:48 2022 +0100

    rocker: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/9ba2d13099d216f3df83e50ad33a05504c90fe7c.1641744274.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 004464835bfc6e24c9fa468153f52f4e4f1d610e
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 16:57:50 2022 +0100

    hinic: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/23541c28df8d0dcd3663b5dbe0f76af71e70e9cc.1641743855.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e20a471256b0adccfa6b61aa12c4888abb542320
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 16:50:19 2022 +0100

    lan743x: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/ef548716606f257939df9738a801f15b6edf2568.1641743405.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit cfcfc8f5a54b2e125b3be857f630ffc37822df26
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 16:41:43 2022 +0100

    net: enetc: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/dbecd4eb49a9586ee343b5473dda4b84c42112e9.1641742884.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 030f9ce8c739a5cfa420291188023b7741b7bc73
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 14:59:48 2022 +0100

    cxgb4vf: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
    1.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/b14986ea39cea2ca9a6cd0476a3fc167c853ee67.1641736772.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7fc7fc5da61bfb0ed6056243de3bb17bfbce9f53
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 14:53:27 2022 +0100

    cxgb4: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So, if dma_set_mask_and_coherent() succeeds, 'highdma' is known to be true.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/56db10d53be0897ff1be5f37d64b91cb7e1d932c.1641736387.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 544bdad074945c341b03a43f98efcc4e067d7b1b
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 14:51:22 2022 +0100

    cxgb3: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
    1.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/a0e2539aefb0034091aca02c98440ea9459f1258.1641736234.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 3aa440503be5ee1c63b63ec5da41c50e56bd9ae4
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 13:19:28 2022 +0100

    bnx2x: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Moreover, dma_set_mask_and_coherent() returns 0 or -EIO, so the return
    code of the function can be used directly.
    
    Finally, inline bnx2x_set_coherency_mask() because it is now only a wrapper
    for a single dma_set_mask_and_coherent() call.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/29608a525876afddceabf8f11b2ba606da8748fc.1641730747.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 948f6b297f6df4abaac207768ca1b7f7a7f55ffb
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 12:13:47 2022 +0100

    et131x: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    Moreover, dma_set_mask_and_coherent() returns 0 or -EIO, so the return
    code of the function can be used directly. There is no need to 'rc = -EIO'
    explicitly.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/b9aa46e7e5a5aa61f56aac5ea439930f41ad9946.1641726804.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 942e78916f0c8385c60823082bed0c3f5f0c7fa6
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 10:03:49 2022 +0100

    be2net: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So if dma_set_mask_and_coherent() succeeds, 'netdev->features' will have
    NETIF_F_HIGHDMA in all cases. Move the assignment of this feature in
    be_netdev_init() instead be_probe() which is a much logical place.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/637696d7141faa68c29fc34b70f9aa67d5e605f0.1641718999.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c38f30683956722b2de31f026e73c8622a2fade3
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Jan 9 09:50:22 2022 +0100

    vmxnet3: Remove useless DMA-32 fallback configuration
    
    As stated in [1], dma_set_mask() with a 64-bit mask never fails if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So if dma_set_mask_and_coherent() succeeds, 'dma64' is know to be 'true'.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/43e5dcf1a5e9e9c5d2d86f87810d6e93e3d22e32.1641718188.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9aaa82d2e8d5d39472aebef5d3fcf033421b645f
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 8 17:16:16 2022 +0100

    bna: Simplify DMA setting
    
    As stated in [1], dma_set_mask() with a 64-bit mask will never fail if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So, if dma_set_mask_and_coherent() succeeds, 'using_dac' is known to be
    'true'. This variable can be removed.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/1d5a7b3f4fa735f1233c3eb3fa07e71df95fad75.1641658516.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ba8a5863497251ca32786ad3db5e24b7375ddde2
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 8 15:26:06 2022 +0100

    net: alteon: Simplify DMA setting
    
    As stated in [1], dma_set_mask() with a 64-bit mask will never fail if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    If dma_set_mask_and_coherent() succeeds, 'ap->pci_using_dac' is known to be
    1. So 'pci_using_dac' can be removed from the 'struct ace_private'.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/1a414c05c27b21c661aef61dffe1adcd1578b1f5.1641651917.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 21ef11eaf3f78dda7fd20abe6e60e27038cb06a3
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 8 15:22:13 2022 +0100

    myri10ge: Simplify DMA setting
    
    As stated in [1], dma_set_mask() with a 64-bit mask will never fail if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    If dma_set_mask_and_coherent() succeeds, 'dac_enabled' is known to be 1.
    
    Simplify code and remove some dead code accordingly.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/e92b0c3a3c1574a97a4e6fd0c30225f10fa59d18.1641651693.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a72dc1992de85ca712836c845458fa72824e355e
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sat Jan 8 14:48:59 2022 +0100

    qlcnic: Simplify DMA setting
    
    As stated in [1], dma_set_mask() with a 64-bit mask will never fail if
    dev->dma_mask is non-NULL.
    So, if it fails, the 32 bits case will also fail for the same reason.
    
    So qlcnic_set_dma_mask(), (in qlcnic_main.c) can be simplified a lot and
    inlined directly in its only caller.
    
    If dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be 1.
    So it can be removed from all the calling chain.
    
    qlcnic_setup_netdev() can finally be simplified as-well.
    
    [1]: https://lkml.org/lkml/2021/6/7/398
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Link: https://lore.kernel.org/r/4996ab0337d62ec6a54b2edf234cd5ced4b4d7ad.1641649611.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 009e4ee381a0b6176969fe3026fc5eafe05705d0
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 7 19:44:38 2022 -0800

    net: allwinner: Fix print format
    
    Kees reports quoted commit introduced the following warning on arm64:
    
    drivers/net/ethernet/allwinner/sun4i-emac.c:922:60: error: format '%x' expects argument of type 'unsigned int', but argument 3 has type 'resource_size_t' {aka 'long long unsigned int'} [-Werror=format=]
      922 |         netdev_info(ndev, "get io resource from device: 0x%x, size = %u\n",
          |                                                           ~^
          |                                                            |                                      |                                                            unsigned int
          |                                                           %llx
      923 |                     regs->start, resource_size(regs));
          |                     ~~~~~~~~~~~
          |                         |
          |                         resource_size_t {aka long long unsigned int}
    
    .. and another one like that for resource_size().
    
    Switch to %pa and a cast.
    
    Reported-by: Kees Cook <keescook@chromium.org>
    Fixes: 47869e82c8b8 ("sun4i-emac.c: add dma support")
    Link: https://lore.kernel.org/r/20220108034438.2227343-1-kuba@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 07b17f0f7485bcbc7902cf6f56a89f5b716344bd
Author: Yunsheng Lin <linyunsheng@huawei.com>
Date:   Fri Jan 7 17:00:42 2022 +0800

    page_pool: remove spinlock in page_pool_refill_alloc_cache()
    
    As page_pool_refill_alloc_cache() is only called by
    __page_pool_get_cached(), which assumes non-concurrent access
    as suggested by the comment in __page_pool_get_cached(), and
    ptr_ring allows concurrent access between consumer and producer,
    so remove the spinlock in page_pool_refill_alloc_cache().
    
    Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
    Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>
    Link: https://lore.kernel.org/r/20220107090042.13605-1-linyunsheng@huawei.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit dd3ca4c5184ea98e40acb8eb293d85b88ea04ee2
Author: Taehee Yoo <ap420073@gmail.com>
Date:   Sun Jan 9 16:37:02 2022 +0000

    amt: fix wrong return type of amt_send_membership_update()
    
    amt_send_membership_update() would return -1 but it's return type is bool.
    So, it should be used TRUE instead of -1.
    
    Fixes: cbc21dc1cfe9 ("amt: add data plane of amt interface")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Taehee Yoo <ap420073@gmail.com>
    Link: https://lore.kernel.org/r/20220109163702.6331-1-ap420073@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d668769eb9c52b150753f1653f7f5a0aeb8239d2
Author: Pavel Skripkin <paskripkin@gmail.com>
Date:   Fri Jan 7 01:57:16 2022 +0300

    net: mcs7830: handle usb read errors properly
    
    Syzbot reported uninit value in mcs7830_bind(). The problem was in
    missing validation check for bytes read via usbnet_read_cmd().
    
    usbnet_read_cmd() internally calls usb_control_msg(), that returns
    number of bytes read. Code should validate that requested number of bytes
    was actually read.
    
    So, this patch adds missing size validation check inside
    mcs7830_get_reg() to prevent uninit value bugs
    
    Reported-and-tested-by: syzbot+003c0a286b9af5412510@syzkaller.appspotmail.com
    Fixes: 2a36d7083438 ("USB: driver for mcs7830 (aka DeLOCK) USB ethernet adapter")
    Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
    Reviewed-by: Arnd Bergmann <arnd@arndb.de>
    Link: https://lore.kernel.org/r/20220106225716.7425-1-paskripkin@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6738fc77ffa2575f38b88d85583450184d59ed94
Merge: 342402c426902 1c7fab70df085
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 16:30:37 2022 -0800

    Merge branch 'net-skb-introduce-kfree_skb_with_reason'
    
    Menglong Dong says:
    
    ====================
    net: skb: introduce kfree_skb_with_reason()
    
    In this series patch, the interface kfree_skb_with_reason() is
    introduced(), which is used to collect skb drop reason, and pass
    it to 'kfree_skb' tracepoint. Therefor, 'drop_monitor' or eBPF is
    able to monitor abnormal skb with detail reason.
    
    In fact, this series patches are out of the intelligence of David
    and Steve, I'm just a truck man :/
    
    Previous discussion is here:
    
    https://lore.kernel.org/netdev/20211118105752.1d46e990@gandalf.local.home/
    https://lore.kernel.org/netdev/67b36bd8-2477-88ac-83a0-35a1eeaf40c9@gmail.com/
    
    In the first patch, kfree_skb_with_reason() is introduced and
    the 'reason' field is added to 'kfree_skb' tracepoint. In the
    second patch, 'kfree_skb()' in replaced with 'kfree_skb_with_reason()'
    in tcp_v4_rcv(). In the third patch, 'kfree_skb_with_reason()' is
    used in __udp4_lib_rcv().
    
    Changes since v3:
    - fix some code style problems in skb.h
    
    Changes since v2:
    - rename kfree_skb_with_reason() to kfree_skb_reason()
    - make kfree_skb() static inline, as Jakub suggested
    
    Changes since v1:
    - rename some drop reason, as David suggested
    - add the third patch
    ====================
    
    Link: https://lore.kernel.org/r/20220109063628.526990-1-imagedong@tencent.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 1c7fab70df085d866a3765955f397ca2b4025b15
Author: Menglong Dong <imagedong@tencent.com>
Date:   Sun Jan 9 14:36:28 2022 +0800

    net: skb: use kfree_skb_reason() in __udp4_lib_rcv()
    
    Replace kfree_skb() with kfree_skb_reason() in __udp4_lib_rcv.
    New drop reason 'SKB_DROP_REASON_UDP_CSUM' is added for udp csum
    error.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 85125597419aec3aa7b8f3b8713e415f997796f2
Author: Menglong Dong <imagedong@tencent.com>
Date:   Sun Jan 9 14:36:27 2022 +0800

    net: skb: use kfree_skb_reason() in tcp_v4_rcv()
    
    Replace kfree_skb() with kfree_skb_reason() in tcp_v4_rcv(). Following
    drop reasons are added:
    
    SKB_DROP_REASON_NO_SOCKET
    SKB_DROP_REASON_PKT_TOO_SMALL
    SKB_DROP_REASON_TCP_CSUM
    SKB_DROP_REASON_TCP_FILTER
    
    After this patch, 'kfree_skb' event will print message like this:
    
    $           TASK-PID     CPU#  |||||  TIMESTAMP  FUNCTION
    $              | |         |   |||||     |         |
              <idle>-0       [000] ..s1.    36.113438: kfree_skb: skbaddr=(____ptrval____) protocol=2048 location=(____ptrval____) reason: NO_SOCKET
    
    The reason of skb drop is printed too.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c504e5c2f9648a1e5c2be01e8c3f59d394192bd3
Author: Menglong Dong <imagedong@tencent.com>
Date:   Sun Jan 9 14:36:26 2022 +0800

    net: skb: introduce kfree_skb_reason()
    
    Introduce the interface kfree_skb_reason(), which is able to pass
    the reason why the skb is dropped to 'kfree_skb' tracepoint.
    
    Add the 'reason' field to 'trace_kfree_skb', therefor user can get
    more detail information about abnormal skb with 'drop_monitor' or
    eBPF.
    
    All drop reasons are defined in the enum 'skb_drop_reason', and
    they will be print as string in 'kfree_skb' tracepoint in format
    of 'reason: XXX'.
    
    ( Maybe the reasons should be defined in a uapi header file, so that
    user space can use them? )
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 342402c426902c59491b43d3056a1039e5ca02db
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 13:33:21 2022 -0800

    net/mlx5e: Fix build error in fec_set_block_stats()
    
    Build bot reports:
    
    drivers/net/ethernet/mellanox/mlx5/core/en_stats.c: In function 'fec_set_block_stats':
    drivers/net/ethernet/mellanox/mlx5/core/en_stats.c:1235:48: error: 'outl' undeclared (first use in this function); did you mean 'out'?
        1235 |         if (mlx5_core_access_reg(mdev, in, sz, outl, sz, MLX5_REG_PPCNT, 0, 0))
             |                                                ^~~~
             |                                                out
    
    Reported-by: kernel test robot <lkp@intel.com>
    Suggested-by: Leon Romanovsky <leon@kernel.org>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Link: https://lore.kernel.org/r/20220109213321.2292830-1-kuba@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8a27c4d226b5aa76a5ea22b6b9cd5d232e040a5f
Merge: 4ccdcc8ffd955 8c6f36d93449e
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 16:27:26 2022 -0800

    Merge branch 'bnxt_en-update-for-net-next'
    
    Michael Chan says:
    
    ====================
    bnxt_en: Update for net-next
    
    This series adds better error and debug logging for firmware messages.
    We now also use the firmware provided timeout value for long running
    commands instead of capping it to 40 seconds.
    ====================
    
    Link: https://lore.kernel.org/r/1641772485-10421-1-git-send-email-michael.chan@broadcom.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8c6f36d93449e8de7b49a67727e3d09b67c73126
Author: Edwin Peer <edwin.peer@broadcom.com>
Date:   Sun Jan 9 18:54:45 2022 -0500

    bnxt_en: improve firmware timeout messaging
    
    While it has always been possible to infer that an HWRM command was
    abandoned due to an unhealthy firmware status by the shortened timeout
    reported, this change improves the log messaging to account for this
    case explicitly. In the interests of further clarity, the firmware
    status is now also reported in these new messages.
    
    v2: Remove inline keyword for hwrm_wait_must_abort() in .c file.
    
    Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
    Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bce9a0b7900836df223ab638090df0cb8430d9e8
Author: Edwin Peer <edwin.peer@broadcom.com>
Date:   Sun Jan 9 18:54:44 2022 -0500

    bnxt_en: use firmware provided max timeout for messages
    
    Some older devices cannot accommodate the 40 seconds timeout
    cap for long running commands (such as NVRAM commands) due to
    hardware limitations. Allow these devices to request more time for
    these long running commands, but print a warning, since the longer
    timeout may cause the hung task watchdog to trigger. In the case of a
    firmware update operation, this is preferable to failing outright.
    
    v2: Use bp->hwrm_cmd_max_timeout directly without the constants.
    
    Fixes: 881d8353b05e ("bnxt_en: Add an upper bound for all firmware command timeouts.")
    Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 662c9b22f5b568fe79e69b06f3c926cad965bfd2
Author: Edwin Peer <edwin.peer@broadcom.com>
Date:   Sun Jan 9 18:54:43 2022 -0500

    bnxt_en: improve VF error messages when PF is unavailable
    
    The current driver design relies on the PF netdev being open in order
    to intercept the following HWRM commands from a VF:
        - HWRM_FUNC_VF_CFG
        - HWRM_CFA_L2_FILTER_ALLOC
        - HWRM_PORT_PHY_QCFG (only if FW_CAP_LINK_ADMIN is not supported)
    
    If the PF is closed, then VFs are subjected to rather inscrutable error
    messages in response to any configuration requests involving the above
    command types. Recent firmware distinguishes this problem case from
    other errors by returning HWRM_ERR_CODE_PF_UNAVAILABLE. In most cases,
    the appropriate course of action is still to fail, but this can now be
    accomplished with the aid of more user informative log messages. For L2
    filter allocations that are already asynchronous, an automatic retry
    seems more appropriate.
    
    v2: Delete extra newline.
    
    Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8fa4219dba8e621aa1e78dfa7eeab10f55acb3c0
Author: Edwin Peer <edwin.peer@broadcom.com>
Date:   Sun Jan 9 18:54:42 2022 -0500

    bnxt_en: add dynamic debug support for HWRM messages
    
    Add logging of firmware messages. These can be useful for diagnosing
    issues in the field, but due to their verbosity are only appropriate
    at a debug message level.
    
    Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
    Signed-off-by: Michael Chan <michael.chan@broadcom.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4ccdcc8ffd955490feec05380223db6a48961eb5
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Dec 27 12:17:57 2021 -0700

    iwlwifi: mvm: Use div_s64 instead of do_div in iwl_mvm_ftm_rtt_smoothing()
    
    When building ARCH=arm allmodconfig:
    
    drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c: In function ‘iwl_mvm_ftm_rtt_smoothing’:
    ./include/asm-generic/div64.h:222:35: error: comparison of distinct pointer types lacks a cast [-Werror]
      222 |         (void)(((typeof((n)) *)0) == ((uint64_t *)0));  \
          |                                   ^~
    drivers/net/wireless/intel/iwlwifi/mvm/ftm-initiator.c:1070:9: note: in expansion of macro ‘do_div’
     1070 |         do_div(rtt_avg, 100);
          |         ^~~~~~
    
    do_div() has to be used with an unsigned 64-bit integer dividend but
    rtt_avg is a signed 64-bit integer.
    
    div_s64() expects a signed 64-bit integer dividend and signed 32-bit
    divisor, which fits this scenario, so use that function here to fix the
    warning.
    
    Fixes: 8b0f92549f2c ("iwlwifi: mvm: fix 32-bit build in FTM")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lore.kernel.org/r/20211227191757.2354329-1-nathan@kernel.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6f022c2ddbcefaee79502ce5386dfe351d457070
Author: Paul Blakey <paulb@nvidia.com>
Date:   Thu Jan 6 17:38:04 2022 +0200

    net: openvswitch: Fix ct_state nat flags for conns arriving from tc
    
    Netfilter conntrack maintains NAT flags per connection indicating
    whether NAT was configured for the connection. Openvswitch maintains
    NAT flags on the per packet flow key ct_state field, indicating
    whether NAT was actually executed on the packet.
    
    When a packet misses from tc to ovs the conntrack NAT flags are set.
    However, NAT was not necessarily executed on the packet because the
    connection's state might still be in NEW state. As such, openvswitch
    wrongly assumes that NAT was executed and sets an incorrect flow key
    NAT flags.
    
    Fix this, by flagging to openvswitch which NAT was actually done in
    act_ct via tc_skb_ext and tc_skb_cb to the openvswitch module, so
    the packet flow key NAT flags will be correctly set.
    
    Fixes: b57dc7c13ea9 ("net/sched: Introduce action ct")
    Signed-off-by: Paul Blakey <paulb@nvidia.com>
    Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
    Link: https://lore.kernel.org/r/20220106153804.26451-1-paulb@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 77bbcb60f734fe25e1d17a7bdc9a4260868efb0f
Merge: 9f3248c9dd519 4a80e026981b7
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 15:59:22 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter updates for net-next
    
    The following patchset contains Netfilter updates for net-next. This
    includes one patch to update ovs and act_ct to use nf_ct_put() instead
    of nf_conntrack_put().
    
    1) Add netns_tracker to nfnetlink_log and masquerade, from Eric Dumazet.
    
    2) Remove redundant rcu read-size lock in nf_tables packet path.
    
    3) Replace BUG() by WARN_ON_ONCE() in nft_payload.
    
    4) Consolidate rule verdict tracing.
    
    5) Replace WARN_ON() by WARN_ON_ONCE() in nf_tables core.
    
    6) Make counter support built-in in nf_tables.
    
    7) Add new field to conntrack object to identify locally generated
       traffic, from Florian Westphal.
    
    8) Prevent NAT from shadowing well-known ports, from Florian Westphal.
    
    9) Merge nf_flow_table_{ipv4,ipv6} into nf_flow_table_inet, also from
       Florian.
    
    10) Remove redundant pointer in nft_pipapo AVX2 support, from Colin Ian King.
    
    11) Replace opencoded max() in conntrack, from Jiapeng Chong.
    
    12) Update conntrack to use refcount_t API, from Florian Westphal.
    
    13) Move ip_ct_attach indirection into the nf_ct_hook structure.
    
    14) Constify several pointer object in the netfilter codebase,
        from Florian Westphal.
    
    15) Tree-wide replacement of nf_conntrack_put() by nf_ct_put(), also
        from Florian.
    
    16) Fix egress splat due to incorrect rcu notation, from Florian.
    
    17) Move stateful fields of connlimit, last, quota, numgen and limit
        out of the expression data area.
    
    18) Build a blob to represent the ruleset in nf_tables, this is a
        requirement of the new register tracking infrastructure.
    
    19) Add NFT_REG32_NUM to define the maximum number of 32-bit registers.
    
    20) Add register tracking infrastructure to skip redundant
        store-to-register operations, this includes support for payload,
        meta and bitwise expresssions.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next: (32 commits)
      netfilter: nft_meta: cancel register tracking after meta update
      netfilter: nft_payload: cancel register tracking after payload update
      netfilter: nft_bitwise: track register operations
      netfilter: nft_meta: track register operations
      netfilter: nft_payload: track register operations
      netfilter: nf_tables: add register tracking infrastructure
      netfilter: nf_tables: add NFT_REG32_NUM
      netfilter: nf_tables: add rule blob layout
      netfilter: nft_limit: move stateful fields out of expression data
      netfilter: nft_limit: rename stateful structure
      netfilter: nft_numgen: move stateful fields out of expression data
      netfilter: nft_quota: move stateful fields out of expression data
      netfilter: nft_last: move stateful fields out of expression data
      netfilter: nft_connlimit: move stateful fields out of expression data
      netfilter: egress: avoid a lockdep splat
      net: prefer nf_ct_put instead of nf_conntrack_put
      netfilter: conntrack: avoid useless indirection during conntrack destruction
      netfilter: make function op structures const
      netfilter: core: move ip_ct_attach indirection to struct nf_ct_hook
      netfilter: conntrack: convert to refcount_t api
      ...
    ====================
    
    Link: https://lore.kernel.org/r/20220109231640.104123-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4a80e026981b791da3937470ace84796490c7796
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:26 2022 +0100

    netfilter: nft_meta: cancel register tracking after meta update
    
    The meta expression might mangle the packet metadata, cancel register
    tracking since any metadata in the registers is stale.
    
    Finer grain register tracking cancellation by inspecting the meta type
    on the register is also possible.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit cc003c7ee6094bca65435ca4bdbba8c98a7c859f
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:25 2022 +0100

    netfilter: nft_payload: cancel register tracking after payload update
    
    The payload expression might mangle the packet, cancel register tracking
    since any payload data in the registers is stale.
    
    Finer grain register tracking cancellation by inspecting the payload
    base, offset and length on the register is also possible.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit be5650f8f47e8cffbbbcad08b71103685e971f20
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:24 2022 +0100

    netfilter: nft_bitwise: track register operations
    
    Check if the destination register already contains the data that this
    bitwise expression performs. This allows to skip this redundant
    operation.
    
    If the destination contains a different bitwise operation, cancel the
    register tracking information. If the destination contains no bitwise
    operation, update the register tracking information.
    
    Update the payload and meta expression to check if this bitwise
    operation has been already performed on the register. Hence, both the
    payload/meta and the bitwise expressions are reduced.
    
    There is also a special case: If source register != destination register
    and source register is not updated by a previous bitwise operation, then
    transfer selector from the source register to the destination register.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 9b17afb2c88bbadcc15b96f0275c426ae3d89a33
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:23 2022 +0100

    netfilter: nft_meta: track register operations
    
    Check if the destination register already contains the data that this
    meta store expression performs. This allows to skip this redundant
    operation. If the destination contains a different selector, update
    the register tracking information.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit a7c176bf9f0e916f7544f6a00d898b0c90de1887
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:22 2022 +0100

    netfilter: nft_payload: track register operations
    
    Check if the destination register already contains the data that this
    payload store expression performs. This allows to skip this redundant
    operation. If the destination contains a different selector, update
    the register tracking information.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 12e4ecfa244be2f117ef5304d2d866b65e70bff3
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:21 2022 +0100

    netfilter: nf_tables: add register tracking infrastructure
    
    This patch adds new infrastructure to skip redundant selector store
    operations on the same register to achieve a performance boost from
    the packet path.
    
    This is particularly noticeable in pure linear rulesets but it also
    helps in rulesets which are already heaving relying in maps to avoid
    ruleset linear inspection.
    
    The idea is to keep data of the most recurrent store operations on
    register to reuse them with cmp and lookup expressions.
    
    This infrastructure allows for dynamic ruleset updates since the ruleset
    blob reduction happens from the kernel.
    
    Userspace still needs to be updated to maximize register utilization to
    cooperate to improve register data reuse / reduce number of store on
    register operations.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 642c8eff5c6099dfde386ca3906fa55dc98f9ade
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:20 2022 +0100

    netfilter: nf_tables: add NFT_REG32_NUM
    
    Add a definition including the maximum number of 32-bits registers that
    are used a scratchpad memory area to store data.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 2c865a8a28a10e9800a3dd07ca339d24563e3d65
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:19 2022 +0100

    netfilter: nf_tables: add rule blob layout
    
    This patch adds a blob layout per chain to represent the ruleset in the
    packet datapath.
    
            size (unsigned long)
            struct nft_rule_dp
              struct nft_expr
              ...
            struct nft_rule_dp
              struct nft_expr
              ...
            struct nft_rule_dp (is_last=1)
    
    The new structure nft_rule_dp represents the rule in a more compact way
    (smaller memory footprint) compared to the control-plane nft_rule
    structure.
    
    The ruleset blob is a read-only data structure. The first field contains
    the blob size, then the rules containing expressions. There is a trailing
    rule which is used by the tracing infrastructure which is equivalent to
    the NULL rule marker in the previous representation. The blob size field
    does not include the size of this trailing rule marker.
    
    The ruleset blob is generated from the commit path.
    
    This patch reuses the infrastructure available since 0cbc06b3faba
    ("netfilter: nf_tables: remove synchronize_rcu in commit phase") to
    build the array of rules per chain.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 3b9e2ea6c11bff72ac1d607f6b954e7666b47409
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:18 2022 +0100

    netfilter: nft_limit: move stateful fields out of expression data
    
    In preparation for the rule blob representation.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 369b6cb5d391750fc01ce951c2500281d2975705
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:17 2022 +0100

    netfilter: nft_limit: rename stateful structure
    
    From struct nft_limit to nft_limit_priv.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 567882eb3d441fef2aa42a75a9688a31979d29f5
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:16 2022 +0100

    netfilter: nft_numgen: move stateful fields out of expression data
    
    In preparation for the rule blob representation.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit ed0a0c60f0e50fa52853620672af97edde3d3a03
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:15 2022 +0100

    netfilter: nft_quota: move stateful fields out of expression data
    
    In preparation for the rule blob representation.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 33a24de37e814572491bcb35f42c0de74ad67586
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:14 2022 +0100

    netfilter: nft_last: move stateful fields out of expression data
    
    In preparation for the rule blob representation.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 37f319f37d9005693dff085bb72852eeebc803ef
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date:   Sun Jan 9 17:11:13 2022 +0100

    netfilter: nft_connlimit: move stateful fields out of expression data
    
    In preparation for the rule blob representation.
    
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 6316136ec6e3dd1c302f7e7289a9ee46ecc610ae
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 15:46:16 2022 +0100

    netfilter: egress: avoid a lockdep splat
    
    include/linux/netfilter_netdev.h:97 suspicious rcu_dereference_check() usage!
    2 locks held by sd-resolve/1100:
     0: ..(rcu_read_lock_bh){1:3}, at: ip_finish_output2
     1: ..(rcu_read_lock_bh){1:3}, at: __dev_queue_xmit
     __dev_queue_xmit+0 ..
    
    The helper has two callers, one uses rcu_read_lock, the other
    rcu_read_lock_bh().  Annotate the dereference to reflect this.
    
    Fixes: 42df6e1d221dd ("netfilter: Introduce egress hook")
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 408bdcfce8dfd6902f75fbcd3b99d8b24b506597
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 05:03:26 2022 +0100

    net: prefer nf_ct_put instead of nf_conntrack_put
    
    Its the same as nf_conntrack_put(), but without the
    need for an indirect call.  The downside is a module dependency on
    nf_conntrack, but all of these already depend on conntrack anyway.
    
    Cc: Paul Blakey <paulb@mellanox.com>
    Cc: dev@openvswitch.org
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 6ae7989c9af0d98ab64196f4f4c6f6499454bd23
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 05:03:25 2022 +0100

    netfilter: conntrack: avoid useless indirection during conntrack destruction
    
    nf_ct_put() results in a usesless indirection:
    
    nf_ct_put -> nf_conntrack_put -> nf_conntrack_destroy -> rcu readlock +
    indirect call of ct_hooks->destroy().
    
    There are two _put helpers:
    nf_ct_put and nf_conntrack_put.  The latter is what should be used in
    code that MUST NOT cause a linker dependency on the conntrack module
    (e.g. calls from core network stack).
    
    Everyone else should call nf_ct_put() instead.
    
    A followup patch will convert a few nf_conntrack_put() calls to
    nf_ct_put(), in particular from modules that already have a conntrack
    dependency such as act_ct or even nf_conntrack itself.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 285c8a7a58158cb1805c97ff03875df2ba2ea1fe
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 05:03:24 2022 +0100

    netfilter: make function op structures const
    
    No functional changes, these structures should be const.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 3fce16493dc1aa2c9af3d7e7bd360dfe203a3e6a
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 05:03:23 2022 +0100

    netfilter: core: move ip_ct_attach indirection to struct nf_ct_hook
    
    ip_ct_attach predates struct nf_ct_hook, we can place it there and
    remove the exported symbol.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 719774377622bc4025d2a74f551b5dc2158c6c30
Author: Florian Westphal <fw@strlen.de>
Date:   Fri Jan 7 05:03:22 2022 +0100

    netfilter: conntrack: convert to refcount_t api
    
    Convert nf_conn reference counting from atomic_t to refcount_t based api.
    refcount_t api provides more runtime sanity checks and will warn on
    certain constructs, e.g. refcount_inc() on a zero reference count, which
    usually indicates use-after-free.
    
    For this reason template allocation is changed to init the refcount to
    1, the subsequenct add operations are removed.
    
    Likewise, init_conntrack() is changed to set the initial refcount to 1
    instead refcount_inc().
    
    This is safe because the new entry is not (yet) visible to other cpus.
    
    Signed-off-by: Florian Westphal <fw@strlen.de>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 613a0c67d12f33dcbeec2836f5fe60d05b4c18c0
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Sun Dec 26 01:12:41 2021 +0800

    netfilter: conntrack: Use max() instead of doing it manually
    
    Fix following coccicheck warning:
    
    ./include/net/netfilter/nf_conntrack.h:282:16-17: WARNING opportunity
    for max().
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

commit 9f3248c9dd51912ded87562a892ad947da2eebfa
Merge: d5c8725cc913f b9f9dbad0bd1c
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 14:14:08 2022 -0800

    Merge tag 'for-net-next-2022-01-07' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next
    
    Luiz Augusto von Dentz says:
    
    ====================
    bluetooth-next pull request for net-next:
    
     - Add support for Foxconn QCA 0xe0d0
     - Fix HCI init sequence on MacBook Air 8,1 and 8,2
     - Fix Intel firmware loading on legacy ROM devices
    
    * tag 'for-net-next-2022-01-07' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next:
      Bluetooth: hci_sock: fix endian bug in hci_sock_setsockopt()
      Bluetooth: L2CAP: uninitialized variables in l2cap_sock_setsockopt()
      Bluetooth: btqca: sequential validation
      Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0
      Bluetooth: btintel: Fix broken LED quirk for legacy ROM devices
      Bluetooth: hci_event: Rework hci_inquiry_result_with_rssi_evt
      Bluetooth: btbcm: disable read tx power for MacBook Air 8,1 and 8,2
      Bluetooth: hci_qca: Fix NULL vs IS_ERR_OR_NULL check in qca_serdev_probe
      Bluetooth: hci_bcm: Check for error irq
    ====================
    
    Link: https://lore.kernel.org/r/20220107210942.3750887-1-luiz.dentz@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit f4bb93a82f94a1e23e532f0b4b1859f1f4605968
Merge: 6dc9a23e29061 89d58aebe14a3
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Sun Jan 9 14:00:49 2022 -0800

    Merge tag 'linux-can-fixes-for-5.16-20220109' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can
    
    Marc Kleine-Budde says:
    
    ====================
    pull-request: can 2022-01-09
    
    The first patch is by Johan Hovold and fixes a mem leak in the error
    path of the softing_cs driver.
    
    The next patch is by me and fixes a set but not used variable warning
    in the softing driver.
    
    Jiasheng Jiang's patch for the xilinx_can driver adds the missing
    error checking when getting the IRQ.
    
    Lad Prabhakar contributes a patch for the rcar_canfd driver to fix a
    mem leak in the error path.
    
    The last patch is by Brian Silverman and properly initializes the send
    USB messages to avoid spurious CAN error frames.
    
    * tag 'linux-can-fixes-for-5.16-20220109' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can:
      can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
      can: rcar_canfd: rcar_canfd_channel_probe(): make sure we free CAN network device
      can: xilinx_can: xcan_probe(): check for error irq
      can: softing: softing_startstop(): fix set but not used variable warning
      can: softing_cs: softingcs_probe(): fix memleak on registration failure
    ====================
    
    Link: https://lore.kernel.org/r/20220109134040.1945428-1-mkl@pengutronix.de
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit b0fd4b1bf995172b9efcee23600d4f69571c321c
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Thu Dec 2 23:36:41 2021 +0800

    riscv: mm: fix wrong phys_ram_base value for RV64
    
    Currently, if 64BIT and !XIP_KERNEL, the phys_ram_base is always 0,
    no matter the real start of dram reported by memblock is.
    
    Fixes: 6d7f91d914bc ("riscv: Get rid of CONFIG_PHYS_RAM_BASE in kernel physical address conversion")
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit fbb3485f1f931102d8ba606f1c28123f5b48afa3
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Sun Jan 9 10:02:51 2022 +0100

    pcmcia: fix setting of kthread task states
    
    We need to set TASK_INTERRUPTIBLE before calling kthread_should_stop().
    Otherwise, kthread_stop() might see that the pccardd thread is still
    in TASK_RUNNING state and fail to wake it up.
    
    Additionally, we only need to set the state back to TASK_RUNNING if
    kthread_should_stop() breaks the loop.
    
    Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
    Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Fixes: d3046ba809ce ("pcmcia: fix a boot time warning in pcmcia cs code")
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>

commit 869c70609248102f3a2e95a39b6233ff6ea2c932
Author: Sean Christopherson <seanjc@google.com>
Date:   Mon Nov 29 21:43:42 2021 +0000

    RISC-V: Use common riscv_cpuid_to_hartid_mask() for both SMP=y and SMP=n
    
    Use what is currently the SMP=y version of riscv_cpuid_to_hartid_mask()
    for both SMP=y and SMP=n to fix a build failure with KVM=m and SMP=n due
    to boot_cpu_hartid not being exported.  This also fixes a second bug
    where the SMP=n version assumes the sole CPU in the system is in the
    incoming mask, which may not hold true in kvm_riscv_vcpu_sbi_ecall() if
    the KVM guest VM has multiple vCPUs (on a SMP=n system).
    
    Fixes: 1ef46c231df4 ("RISC-V: Implement new SBI v0.2 extensions")
    Reported-by: Adam Borowski <kilobyte@angband.pl>
    Reviewed-by: Anup Patel <anup.patel@wdc.com>
    Signed-off-by: Sean Christopherson <seanjc@google.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 51f23e5318a0882068254e20d3999e9421cfd66e
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Nov 29 00:07:41 2021 +0800

    riscv: head: remove useless __PAGE_ALIGNED_BSS and .balign
    
    After commit 83e7b8769a08 ("RISC-V: move empty_zero_page definition to
    C and export it"), the empty_zero_page has been moved outside head.S,
    the __PAGE_ALIGNED_BSS and .balign LoCs are useless, clean up them.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 1546541fbc90b0dcadcdadf1c828daf0a8f9d88d
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Nov 29 00:07:40 2021 +0800

    riscv: errata: alternative: mark vendor_patch_func __initdata
    
    The function pointer vendor_patch_func is only used during init, so
    mark it as __initdata.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 153c46faf6ae4961451bed2878ff9e93736efe50
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Nov 29 00:07:38 2021 +0800

    riscv: head: make secondary_start_common() static
    
    There are no users outside head.S so make secondary_start_common()
    static.
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 7f3de1adb377960bc061b1d7ee477527d499d2bd
Author: Jisheng Zhang <jszhang@kernel.org>
Date:   Mon Nov 29 00:07:37 2021 +0800

    riscv: remove cpu_stop()
    
    Except arch_cpu_idle_dead(), no users of this function. So remove
    cpu_stop() and fold its code into arch_cpu_idle_dead().
    
    Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit decf89f86ecd3c3c3de81c562010d5797bea3de1
Author: Nick Kossifidis <mick@ics.forth.gr>
Date:   Fri Nov 26 20:04:11 2021 +0200

    riscv: try to allocate crashkern region from 32bit addressible memory
    
    When allocating crash kernel region without explicitly specifying its
    base address/size, memblock_phys_alloc_range will attempt to allocate
    memory top to bottom (memblock.bottom_up is false), so the crash
    kernel region will end up in highmem on 64bit systems. This way
    swiotlb can't work on the crash kernel, since there won't be any
    32bit addressible memory available for the bounce buffers.
    
    Try to allocate 32bit addressible memory if available, for the
    crash kernel by restricting the top search address to be less
    than SZ_4G. If that fails fallback to the previous behavior.
    
    I tested this on HiFive Unmatched where the pci-e controller needs
    swiotlb to work, with this patch it's possible to access the pci-e
    controller on crash kernel and mount the rootfs from the nvme.
    
    Signed-off-by: Nick Kossifidis <mick@ics.forth.gr>
    Fixes: e53d28180d4d ("RISC-V: Add kdump support")
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 0e105f1d0037d677dff3c697d22f9551e6c39af8
Author: Nick Kossifidis <mick@ics.forth.gr>
Date:   Fri Nov 26 20:04:10 2021 +0200

    riscv: use hart id instead of cpu id on machine_kexec
    
    raw_smp_processor_id() doesn't return the hart id as stated in
    arch/riscv/include/asm/smp.h, use smp_processor_id() instead
    to get the cpu id, and cpuid_to_hartid_map() to pass the hart id
    to the next kernel. This fixes kexec on HiFive Unleashed/Unmatched
    where cpu ids and hart ids don't match (on qemu-virt they match).
    
    Fixes: fba8a8674f68 ("RISC-V: Add kexec support")
    Signed-off-by: Nick Kossifidis <mick@ics.forth.gr>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit a11c07f032a0e9a562a32ece73af96b0e754c4b3
Author: Nick Kossifidis <mick@ics.forth.gr>
Date:   Fri Nov 26 20:04:09 2021 +0200

    riscv: Don't use va_pa_offset on kdump
    
    On kdump instead of using an intermediate step to relocate the kernel,
    that lives in a "control buffer" outside the current kernel's mapping,
    we jump to the crash kernel directly by calling riscv_kexec_norelocate().
    The current implementation uses va_pa_offset while switching to physical
    addressing, however since we moved the kernel outside the linear mapping
    this won't work anymore since riscv_kexec_norelocate() is part of the
    kernel mapping and we should use kernel_map.va_kernel_pa_offset, and also
    take XIP kernel into account.
    
    We don't really need to use va_pa_offset on riscv_kexec_norelocate, we
    can just set STVEC to the physical address of the new kernel instead and
    let the hart jump to the new kernel on the next instruction after setting
    SATP to zero. This fixes kdump and is also simpler/cleaner.
    
    I tested this on the latest qemu and HiFive Unmatched and works as
    expected.
    
    Fixes: 2bfc6cd81bd1 ("riscv: Move kernel mapping outside of linear mapping")
    Signed-off-by: Nick Kossifidis <mick@ics.forth.gr>
    Reviewed-by: Alexandre Ghiti <alex@ghiti.fr>
    Cc: stable@vger.kernel.org
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 0ea9fc15b1d7d6636d429e74ffe3f86bf2f2f7d6
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Tue Nov 23 17:05:07 2021 +0100

    fs/locks: fix fcntl_getlk64/fcntl_setlk64 stub prototypes
    
    My patch to rework oabi fcntl64() introduced a harmless
    sparse warning when file locking is disabled:
    
       arch/arm/kernel/sys_oabi-compat.c:251:51: sparse: sparse: incorrect type in argument 3 (different address spaces) @@     expected struct flock64 [noderef] __user *user @@     got struct flock64 * @@
       arch/arm/kernel/sys_oabi-compat.c:251:51: sparse:     expected struct flock64 [noderef] __user *user
       arch/arm/kernel/sys_oabi-compat.c:251:51: sparse:     got struct flock64 *
       arch/arm/kernel/sys_oabi-compat.c:265:55: sparse: sparse: incorrect type in argument 4 (different address spaces) @@     expected struct flock64 [noderef] __user *user @@     got struct flock64 * @@
       arch/arm/kernel/sys_oabi-compat.c:265:55: sparse:     expected struct flock64 [noderef] __user *user
       arch/arm/kernel/sys_oabi-compat.c:265:55: sparse:     got struct flock64 *
    
    When file locking is enabled, everything works correctly and the
    right data gets passed, but the stub declarations in linux/fs.h
    did not get modified when the calling conventions changed in an
    earlier patch.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 7e2d8c29ecdd ("ARM: 9111/1: oabi-compat: rework fcntl64() emulation")
    Fixes: a75d30c77207 ("fs/locks: pass kernel struct flock to fcntl_getlk/setlk")
    Cc: Christoph Hellwig <hch@lst.de>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>
    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 893eae9ac7e4c23c70874c3981fdcf3311655874
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:32 2021 +0100

    riscv: dts: sifive: fu540-c000: Fix PLIC node
    
    Fix the device node for the Platform-Level Interrupt Controller (PLIC):
      - Add missing "#address-cells" property,
      - Sort properties according to DT bindings.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 8fc6e62a549c61abd594e8435017a31cfca43475
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:31 2021 +0100

    riscv: dts: sifive: fu540-c000: Drop bogus soc node compatible values
    
    "make dtbs_check":
    
        arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dt.yaml: soc: $nodename:0: '/' was expected
            From schema: Documentation/devicetree/bindings/riscv/sifive.yaml
        arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dt.yaml: soc: compatible: 'oneOf' conditional failed, one must be fixed:
            'sifive,fu540-c000' is not one of ['sifive,hifive-unleashed-a00']
            'sifive,fu540-c000' is not one of ['sifive,hifive-unmatched-a00']
            'sifive,fu540-c000' was expected
            'sifive,fu740-c000' was expected
            'sifive,fu540' was expected
            'sifive,fu740' was expected
            From schema: Documentation/devicetree/bindings/riscv/sifive.yaml
    
    This happens because the "soc" subnode declares compatibility with
    "sifive,fu540-c000" and "sifive,fu540", while these are only intended
    for the root node.
    
    Fix this by removing the bogus compatible values from the "soc" node.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 8e9b1c9555c1128bcda473383ae9ba3742b59fa8
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:30 2021 +0100

    riscv: dts: sifive: Group tuples in register properties
    
    To improve human readability and enable automatic validation, the tuples
    in "reg" properties containing register blocks should be grouped using
    angle brackets.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit cc79be0e0c9f9e529641b286af54dc5ed26d9407
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:29 2021 +0100

    riscv: dts: sifive: Group tuples in interrupt properties
    
    To improve human readability and enable automatic validation, the tuples
    in the various properties containing interrupt specifiers should be
    grouped.
    
    Fix this by grouping the tuples of "interrupts" and
    "interrupts-extended" properties using angle brackets.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit e35b07a7df9b8accce88d30a4cfa9000c34e6cf3
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:28 2021 +0100

    riscv: dts: microchip: mpfs: Group tuples in interrupt properties
    
    To improve human readability and enable automatic validation, the tuples
    in the various properties containing interrupt specifiers should be
    grouped.
    
    Fix this by grouping the tuples of "interrupts" and
    "interrupts-extended" properties using angle brackets.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 9e85020ccf8c83b89867cd69f54b3ac4a9cf7580
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:27 2021 +0100

    riscv: dts: microchip: mpfs: Fix clock controller node
    
    Fix the device node for the clock controller:
      - Remove bogus "reg-names" property,
      - Remove unneeded "clock-output-names" property.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 9d7b3078628f591e4007210c0d5d3f94805cff55
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:26 2021 +0100

    riscv: dts: microchip: mpfs: Fix reference clock node
    
    "make dtbs_check" reports:
    
        arch/riscv/boot/dts/microchip/microchip-mpfs-icicle-kit.dt.yaml: soc: refclk: {'compatible': ['fixed-clock'], '#clock-cells': [[0]], 'clock-frequency': [[600000000]], 'clock-output-names': ['msspllclk'], 'phandle': [[7]]} should not be valid under {'type': 'object'}
            From schema: dtschema/schemas/simple-bus.yaml
    
    Fix this by moving the node out of the "soc" subnode.
    While at it, rename it to "msspllclk", and drop the now superfluous
    "clock-output-names" property.
    Move the actual clock-frequency value to the board DTS, since it is not
    set until bitstream programming time.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 53abf98005a6bcabb4ddeff642ba36cd1cf4184a
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:25 2021 +0100

    riscv: dts: microchip: mpfs: Fix PLIC node
    
    Fix the device node for the Platform-Level Interrupt Controller (PLIC):
      - Add missing "#address-cells" property,
      - Sort properties according to DT bindings.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 53ef07326ad0d6ae7fefded22bc53b427d542761
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:24 2021 +0100

    riscv: dts: microchip: mpfs: Drop empty chosen node
    
    It does not make sense to have an (empty) chosen node in an SoC-specific
    .dtsi, as chosen is meant for system-specific configuration.
    It is already provided in microchip-mpfs-icicle-kit.dts anyway.
    
    Fixes: 0fa6107eca4186ad ("RISC-V: Initial DTS for Microchip ICICLE board")
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
    Tested-by: Conor Dooley <conor.dooley@microchip.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 75c0dc0437e69fd87e9f4563216978532ec6609d
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:23 2021 +0100

    riscv: dts: canaan: Group tuples in interrupt properties
    
    To improve human readability and enable automatic validation, the tuples
    in the various properties containing interrupt specifiers should be
    grouped.
    
    Fix this by grouping the tuples of "interrupts" and
    "interrupts-extended" properties using angle brackets.
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Tested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit fe38b4d6129ce0cbe2a1d1d91d4160acbacbb37b
Author: Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Fri Dec 17 13:49:22 2021 +0100

    riscv: dts: canaan: Fix SPI FLASH node names
    
    "make dtbs_check":
    
        arch/riscv/boot/dts/canaan/sipeed_maix_bit.dt.yaml: spi-flash@0: $nodename:0: 'spi-flash@0' does not match '^flash(@.*)?$'
                From schema: Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
    
    Fix this by renaming all SPI FLASH nodes to "flash".
    
    Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
    Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
    Tested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 292c33c95defd0b814fec1fc8cd60d16556cf7b8
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Fri Jan 7 08:52:28 2022 +0800

    block: fix old-style declaration
    
    Move the 'inline' keyword to the front of 'void'.
    
    Remove a warning found by clang(make W=1 LLVM=1)
    ./include/linux/blk-mq.h:259:1: warning: ‘inline’ is not at beginning of
    declaration
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Link: https://lore.kernel.org/r/20220107005228.103927-1-yang.lee@linux.alibaba.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit d5c8725cc913f1ab8e2f10a4eda2930bfdc03f1f
Merge: 82192cb497f9e bc3897f79f790
Author: David S. Miller <davem@davemloft.net>
Date:   Sun Jan 9 16:57:50 2022 +0000

    Merge tag 'linux-can-next-for-5.17-20220108' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next
    
    Marc Kleine-Budde says:
    
    ====================
    pull-request: can-next 2022-01-08
    
    this is a pull request of 22 patches for net-next/master.
    
    The first patch is by Tom Rix and fixes an uninitialized variable in
    the janz-ican3 driver (introduced in linux-can-next-for-5.17-20220105).
    
    The next 13 patches are by my and target the mcp251xfd driver. First
    several cleanup patches, then the driver is prepared for the upcoming
    ethtool ring parameter and IRQ coalescing support, which is added in a
    later pull request.
    
    The remaining 8 patches are by Dario Binacchi and me and enhance the
    flexcan driver. The driver is moved into a sub directory. An ethtool
    private flag is added to optionally disable CAN RTR frame reception,
    to make use of more RX buffers. The resulting RX buffer configuration
    can be read by ethtool ring parameter support. Finally documentation
    for the ethtool private flag is added to the
    Documentation/networking/device_drivers/can directory.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3cc7fdb9f90a25ae92250bf9e6cf3b9556b230e9
Author: Pavel Begunkov <asml.silence@gmail.com>
Date:   Sun Jan 9 00:53:22 2022 +0000

    io_uring: fix not released cached task refs
    
    tctx_task_work() may get run after io_uring cancellation and so there
    will be no one to put cached in tctx task refs that may have been added
    back by tw handlers using inline completion infra, Call
    io_uring_drop_tctx_refs() at the end of the main tw handler to release
    them.
    
    Cc: stable@vger.kernel.org # 5.15+
    Reported-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Fixes: e98e49b2bbf7 ("io_uring: extend task put optimisations")
    Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
    Link: https://lore.kernel.org/r/69f226b35fbdb996ab799a8bbc1c06bf634ccec1.1641688805.git.asml.silence@gmail.com
    Signed-off-by: Jens Axboe <axboe@kernel.dk>

commit c5c7440fe7f74645940d5c9e2c49cd7efb706a4f
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Fri Jan 7 18:57:22 2022 +0000

    MIPS: compressed: Fix build with ZSTD compression
    
    Fix the following build issues:
    
    mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `FSE_buildDTable_internal':
     decompress.c:(.text.FSE_buildDTable_internal+0x2cc): undefined reference to `__clzdi2'
       mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `BIT_initDStream':
       decompress.c:(.text.BIT_initDStream+0x7c): undefined reference to `__clzdi2'
       mips64el-linux-ld: decompress.c:(.text.BIT_initDStream+0x158): undefined reference to `__clzdi2'
       mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `ZSTD_buildFSETable_body_default.constprop.0':
     decompress.c:(.text.ZSTD_buildFSETable_body_default.constprop.0+0x2a8): undefined reference to `__clzdi2'
       mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `FSE_readNCount_body_default':
     decompress.c:(.text.FSE_readNCount_body_default+0x130): undefined reference to `__ctzdi2'
     mips64el-linux-ld: decompress.c:(.text.FSE_readNCount_body_default+0x1a4): undefined reference to `__ctzdi2'
     mips64el-linux-ld: decompress.c:(.text.FSE_readNCount_body_default+0x2e4): undefined reference to `__clzdi2'
       mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `HUF_readStats_body_default':
     decompress.c:(.text.HUF_readStats_body_default+0x184): undefined reference to `__clzdi2'
     mips64el-linux-ld: decompress.c:(.text.HUF_readStats_body_default+0x1b4): undefined reference to `__clzdi2'
       mips64el-linux-ld: arch/mips/boot/compressed/decompress.o: in function `ZSTD_DCtx_getParameter':
     decompress.c:(.text.ZSTD_DCtx_getParameter+0x60): undefined reference to `__clzdi2'
    
    Fixes: a510b616131f ("MIPS: Add support for ZSTD-compressed kernels")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Nick Terrell <terrelln@fb.com>
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 4da27b6d550427a0560a15df36de99cb17629216
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 6 19:51:41 2022 -0800

    MIPS: BCM47XX: Add support for Netgear WN2500RP v1 & v2
    
    Add support for the Netgear WN2500 RP v1 and v2 Wi-Fi range extenders
    based on the BCM5357 chipset and supporting 802.11n and 802.11ac.
    
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 15e690af5cc3cd8f5d14ee2aa3a093f80196110e
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 6 19:51:40 2022 -0800

    MIPS: BCM47XX: Add support for Netgear R6300 v1
    
    Add support for the Netgear R6300 v1 Wi-Fi router using a Broadcom
    BCM4706 chipset and supporting 802.11n and 802.11ac.
    
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit aecf89f2f8e8a604c33085c230a1f04ea325de64
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 6 19:51:39 2022 -0800

    MIPS: BCM47XX: Add LEDs and buttons for Asus RTN-10U
    
    Add the definitions for the buttons and LEDs used on the Asus RTN-10U
    router.
    
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 3829e4f10a232964cc728c0479c8097922e5e073
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 6 19:51:38 2022 -0800

    MIPS: BCM47XX: Add board entry for Linksys WRT320N v1
    
    This router is based on a Broadcom BCM4717A1 chipset and supports
    802.11n Wi-Fi. Add a board entry for that router and register LEDs and
    buttons accordingly.
    
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit eea175eedf3e2f71b9538d21e643e7a1be4923df
Author: Florian Fainelli <f.fainelli@gmail.com>
Date:   Thu Jan 6 19:51:37 2022 -0800

    MIPS: BCM47XX: Define Linksys WRT310N V2 buttons
    
    Update the buttons registration code to register the two buttons (WPS,
    system rester) using the existing BCM47XX_BOARD_LINKSYS_WRT310NV2 board
    entry.
    
    Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit f1da418b0c418d8c73b6314ea4e7391720dafe4f
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Fri Jan 7 08:31:28 2022 +0800

    MIPS: Remove duplicated include in local.h
    
    Fix following includecheck warning:
    ./arch/mips/include/asm/local.h: asm/asm.h is included more than once.
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

commit 89d58aebe14a365c25ba6645414afdbf4e41cea4
Author: Brian Silverman <bsilver16384@gmail.com>
Date:   Wed Jan 5 16:29:50 2022 -0800

    can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
    
    No information is deliberately sent in hf->flags in host -> device
    communications, but the open-source candleLight firmware echoes it
    back, which can result in the GS_CAN_FLAG_OVERFLOW flag being set and
    generating spurious ERRORFRAMEs.
    
    While there also initialize the reserved member with 0.
    
    Fixes: d08e973a77d1 ("can: gs_usb: Added support for the GS_USB CAN devices")
    Link: https://lore.kernel.org/all/20220106002952.25883-1-brian.silverman@bluerivertech.com
    Link: https://github.com/candle-usb/candleLight_fw/issues/87
    Cc: stable@vger.kernel.org
    Signed-off-by: Brian Silverman <brian.silverman@bluerivertech.com>
    [mkl: initialize the reserved member, too]
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 72b1e360572f9fa7d08ee554f1da29abce23f288
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Thu Jan 6 11:48:00 2022 +0000

    can: rcar_canfd: rcar_canfd_channel_probe(): make sure we free CAN network device
    
    Make sure we free CAN network device in the error path. There are
    several jumps to fail label after allocating the CAN network device
    successfully. This patch places the free_candev() under fail label so
    that in failure path a jump to fail label frees the CAN network
    device.
    
    Fixes: 76e9353a80e9 ("can: rcar_canfd: Add support for RZ/G2L family")
    Link: https://lore.kernel.org/all/20220106114801.20563-1-prabhakar.mahadev-lad.rj@bp.renesas.com
    Reported-by: Pavel Machek <pavel@denx.de>
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit c6564c13dae25cd7f8e1de5127b4da4500ee5844
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Dec 24 10:13:24 2021 +0800

    can: xilinx_can: xcan_probe(): check for error irq
    
    For the possible failure of the platform_get_irq(), the returned irq
    could be error number and will finally cause the failure of the
    request_irq().
    
    Consider that platform_get_irq() can now in certain cases return
    -EPROBE_DEFER, and the consequences of letting request_irq()
    effectively convert that into -EINVAL, even at probe time rather than
    later on. So it might be better to check just now.
    
    Fixes: b1201e44f50b ("can: xilinx CAN controller support")
    Link: https://lore.kernel.org/all/20211224021324.1447494-1-jiasheng@iscas.ac.cn
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 370d988cc529598ebaec6487d4f84c2115dc696b
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Sat Jan 8 21:57:51 2022 +0100

    can: softing: softing_startstop(): fix set but not used variable warning
    
    In the function softing_startstop() the variable error_reporting is
    assigned but not used. The code that uses this variable is commented
    out. Its stated that the functionality is not finally verified.
    
    To fix the warning:
    
    | drivers/net/can/softing/softing_fw.c:424:9: error: variable 'error_reporting' set but not used [-Werror,-Wunused-but-set-variable]
    
    remove the comment, activate the code, but add a "0 &&" to the if
    expression and rely on the optimizer rather than the preprocessor to
    remove the code.
    
    Link: https://lore.kernel.org/all/20220109103126.1872833-1-mkl@pengutronix.de
    Fixes: 03fd3cf5a179 ("can: add driver for Softing card")
    Cc: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 2e88c6a805fc5311e27e0f6efe243842634052ab
Author: Takashi Iwai <tiwai@suse.de>
Date:   Sun Jan 9 09:13:37 2022 +0100

    ALSA: hda: Fix dependencies of CS35L41 on SPI/I2C buses
    
    CS35L41 SPI and I2C drivers depend on those buses, hence they have to
    have dependencies in Kconfig; otherwise it may result in missing
    symbols.
    
    Fixes: 7b2f3eb492da ("ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems")
    Reported-by: kernel test robot <lkp@intel.com>
    Link: https://lore.kernel.org/r/20220109081337.30623-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 9df136b555221e8eb3f4e5d3958d8fe11783abcf
Author: Nikita Travkin <nikita@trvn.ru>
Date:   Sat Jan 8 23:23:49 2022 -0800

    Input: zinitix - add compatible for bt532
    
    Zinitix BT532 is another touch controller that seem to implement the
    same interface as an already supported BT541. Add it to the driver.
    
    Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Nikita Travkin <nikita@trvn.ru>
    Link: https://lore.kernel.org/r/20220106072840.36851-5-nikita@trvn.ru
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit c54be0e32e54abdf7b89d56fe9edebc2f319acee
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sat Jan 8 23:23:10 2022 -0800

    Input: zinitix - handle proper supply names
    
    The supply names of the Zinitix touchscreen were a bit confused, the new
    bindings rectifies this.
    
    To deal with old and new devicetrees, first check if we have "vddo" and in
    case that exists assume the old supply names. Else go and look for the new
    ones.
    
    We cannot just get the regulators since we would get an OK and a dummy
    regulator: we need to check explicitly for the old supply name.
    
    Use struct device *dev as a local variable instead of the I2C client since
    the device is what we are actually obtaining the resources from.
    
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    [Slightly changed the legacy regulator detection]
    Signed-off-by: Nikita Travkin <nikita@trvn.ru>
    Link: https://lore.kernel.org/r/20220106072840.36851-4-nikita@trvn.ru
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit fdbb8025263246d770b802567757871db7a05913
Author: Linus Walleij <linus.walleij@linaro.org>
Date:   Sat Jan 8 23:21:55 2022 -0800

    dt-bindings: input/ts/zinitix: Convert to YAML, fix and extend
    
    This converts the Zinitix BT4xx and BT5xx touchscreen bindings to YAML,
    fix them up a bit and extends them.
    
    We list all the existing BT4xx and BT5xx components with compatible
    strings.  These are all similar, use the same bindings and work in
    similar ways.
    
    We rename the supplies from the erroneous vdd/vddo to the actual supply
    names vcca/vdd as specified on the actual component. It is long
    established that supplies shall be named after the supply pin names of a
    component.  The confusion probably stems from that in a certain product
    the rails to the component were named vdd/vddo. Drop some notes on how OS
    implementations should avoid confusion by first looking for vddo, and if
    that exists assume the legacy binding pair and otherwise use vcca/vdd.
    
    Add reset-gpios as sometimes manufacturers pulls a GPIO line to the reset
    line on the chip.
    
    Add optional touchscreen-fuzz-x and touchscreen-fuzz-y properties.
    
    Reviewed-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    [Fixed dt_schema_check]
    Signed-off-by: Nikita Travkin <nikita@trvn.ru>
    Link: https://lore.kernel.org/r/20220106072840.36851-3-nikita@trvn.ru
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit 8a78050ee257c8d4292ea8a6b52bb9c894306b9b
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sat Jan 8 23:09:20 2022 -0800

    Input: axp20x-pek - revert "always register interrupt handlers" change
    
    The power button on Cherry Trail systems with an AXP288 PMIC is connected
    to both the power button pin of the PMIC as well as to a power button GPIO
    on the Cherry Trail SoC itself. This leads to double power button event
    reporting which is a problem.
    
    Since reporting power button presses through the PMIC is not supported on
    all PMICs used on Cherry Trail systems, we want to keep the GPIO
    power button events, so the axp20x-pek code checks for the presence of
    a GPIO power button and in that case does not register its input-device.
    
    On most systems the GPIO power button also can wake-up the system from
    suspend, so the axp20x-pek driver would also not register its interrupt
    handler. But on some systems there was a bug causing wakeup by the GPIO
    power button handler to not work.
    
    Commit 9747070c11d6 ("Input: axp20x-pek - always register interrupt
    handlers") was added as a work around for this registering the axp20x-pek
    interrupts, but not the input-device on Cherry Trail systems.
    
    In the mean time the root-cause of the GPIO power button wakeup events
    not working has been found and fixed by the "pinctrl: cherryview: Do not
    allow the same interrupt line to be used by 2 pins" patch,
    so this is no longer necessary.
    
    This reverts the workaround going back to only registering the
    interrupt handlers on systems where we also register the input-device.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Acked-by: Chen-Yu Tsai <wens@csie.org>
    Link: https://lore.kernel.org/r/20220106111647.66520-1-hdegoede@redhat.com
    Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

commit d99a8af48a3de727173415ccb17f6b6ba60d5573
Author: Colin Ian King <colin.king@intel.com>
Date:   Thu Dec 30 13:45:57 2021 +0000

    lib: remove redundant assignment to variable ret
    
    Variable ret is being assigned a value that is never read. If the
    for-loop is entered then ret is immediately re-assigned a new
    value. If the for-loop is not executed ret is never read. The
    assignment is redundant and can be removed.
    
    Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit 84cc69589700b90a4c8d27b481a51fce8cca6051
Author: Patrick Williams <patrick@stwcx.xyz>
Date:   Thu Dec 23 09:49:31 2021 -0600

    tpm: fix NPE on probe for missing device
    
    When using the tpm_tis-spi driver on a system missing the physical TPM,
    a null pointer exception was observed.
    
        [    0.938677] Unable to handle kernel NULL pointer dereference at virtual address 00000004
        [    0.939020] pgd = 10c753cb
        [    0.939237] [00000004] *pgd=00000000
        [    0.939808] Internal error: Oops: 5 [#1] SMP ARM
        [    0.940157] CPU: 0 PID: 48 Comm: kworker/u4:1 Not tainted 5.15.10-dd1e40c #1
        [    0.940364] Hardware name: Generic DT based system
        [    0.940601] Workqueue: events_unbound async_run_entry_fn
        [    0.941048] PC is at tpm_tis_remove+0x28/0xb4
        [    0.941196] LR is at tpm_tis_core_init+0x170/0x6ac
    
    This is due to an attempt in 'tpm_tis_remove' to use the drvdata, which
    was not initialized in 'tpm_tis_core_init' prior to the first error.
    
    Move the initialization of drvdata earlier so 'tpm_tis_remove' has
    access to it.
    
    Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
    Fixes: 79ca6f74dae0 ("tpm: fix Atmel TPM crash caused by too frequent queries")
    Cc: stable@vger.kernel.org
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit eabad7ba2c752392ae50f24a795093fb115b686d
Author: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Date:   Mon Dec 20 16:06:35 2021 +0100

    tpm: fix potential NULL pointer access in tpm_del_char_device
    
    Some SPI controller drivers unregister the controller in the shutdown
    handler (e.g. BCM2835). If such a controller is used with a TPM 2 slave
    chip->ops may be accessed when it is already NULL:
    
    At system shutdown the pre-shutdown handler tpm_class_shutdown() shuts down
    TPM 2 and sets chip->ops to NULL. Then at SPI controller unregistration
    tpm_tis_spi_remove() is called and eventually calls tpm_del_char_device()
    which tries to shut down TPM 2 again. Thereby it accesses chip->ops again:
    (tpm_del_char_device calls tpm_chip_start which calls tpm_clk_enable which
    calls chip->ops->clk_enable).
    
    Avoid the NULL pointer access by testing if chip->ops is valid and skipping
    the TPM 2 shutdown procedure in case it is NULL.
    
    Cc: stable@vger.kernel.org
    Signed-off-by: Lino Sanfilippo <LinoSanfilippo@gmx.de>
    Fixes: 39d0099f9439 ("powerpc/pseries: Add shutdown() to vio_driver and vio_bus")
    Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
    Tested-by: Stefan Berger <stefanb@linux.ibm.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit 0aa698787aa2a9e8840987e54ba2982559de6404
Author: axelj <axelj@axis.com>
Date:   Mon Dec 13 08:09:25 2021 +0100

    tpm: Add Upgrade/Reduced mode support for TPM2 modules
    
    If something went wrong during the TPM firmware upgrade, like power
    failure or the firmware image file get corrupted, the TPM might end
    up in Upgrade or Failure mode upon the next start. The state is
    persistent between the TPM power cycle/restart.
    
    According to TPM specification:
     * If the TPM is in Upgrade mode, it will answer with TPM2_RC_UPGRADE
       to all commands except TPM2_FieldUpgradeData(). It may also accept
       other commands if it is able to complete them using the previously
       installed firmware.
     * If the TPM is in Failure mode, it will allow performing TPM
       initialization but will not provide any crypto operations.
       Will happily respond to Field Upgrade calls.
    
    Change the behavior of the tpm2_auto_startup(), so it detects the active
    running mode of the TPM by adding the following checks.  If
    tpm2_do_selftest() call returns TPM2_RC_UPGRADE, the TPM is in Upgrade
    mode.
    If the TPM is in Failure mode, it will successfully respond to both
    tpm2_do_selftest() and tpm2_startup() calls. Although, will fail to
    answer to tpm2_get_cc_attrs_tbl(). Use this fact to conclude that TPM is
    in Failure mode.
    
    If detected that the TPM is in the Upgrade or Failure mode, the function
    sets TPM_CHIP_FLAG_FIRMWARE_UPGRADE_MODE flag.
    
    The TPM_CHIP_FLAG_FIRMWARE_UPGRADE_MODE flag is used later during driver
    initialization/deinitialization to disable functionality which makes no
    sense or will fail in the current TPM state. Following functionality is
    affected:
     * Do not register TPM as a hwrng
     * Do not register sysfs entries which provide information impossible to
       obtain in limited mode
     * Do not register resource managed character device
    
    Signed-off-by: axelj <axelj@axis.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit 5887d7f4a8c4310a75ca45f576f26b3d21250881
Author: Rob Barnes <robbarnes@google.com>
Date:   Mon Dec 6 12:03:09 2021 +0000

    char: tpm: cr50: Set TPM_FIRMWARE_POWER_MANAGED based on device property
    
    Set TPM_FIRMWARE_POWER_MANAGED flag based on 'firmware-power-managed'
    ACPI DSD property. For the CR50 TPM, this flag defaults to true when
    the property is unset.
    
    When this flag is set to false, the CR50 TPM driver will always send
    a shutdown command whenever the system suspends.
    
    Signed-off-by: Rob Barnes <robbarnes@google.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit 7d30198ee24f2ddcc4fefcd38a9b76bd8ab31360
Author: Andrew Zaborowski <andrew.zaborowski@intel.com>
Date:   Tue Nov 9 16:16:49 2021 +0100

    keys: X.509 public key issuer lookup without AKID
    
    There are non-root X.509 v3 certificates in use out there that contain
    no Authority Key Identifier extension (RFC5280 section 4.2.1.1).  For
    trust verification purposes the kernel asymmetric key type keeps two
    struct asymmetric_key_id instances that the key can be looked up by,
    and another two to look up the key's issuer.  The x509 public key type
    and the PKCS7 type generate them from the SKID and AKID extensions in
    the certificate.  In effect current code has no way to look up the
    issuer certificate for verification without the AKID.
    
    To remedy this, add a third asymmetric_key_id blob to the arrays in
    both asymmetric_key_id's (for certficate subject) and in the
    public_keys_signature's auth_ids (for issuer lookup), using just raw
    subject and issuer DNs from the certificate.  Adapt
    asymmetric_key_ids() and its callers to use the third ID for lookups
    when none of the other two are available.  Attempt to keep the logic
    intact when they are, to minimise behaviour changes.  Adapt the
    restrict functions' NULL-checks to include that ID too.  Do not modify
    the lookup logic in pkcs7_verify.c, the AKID extensions are still
    required there.
    
    Internally use a new "dn:" prefix to the search specifier string
    generated for the key lookup in find_asymmetric_key().  This tells
    asymmetric_key_match_preparse to only match the data against the raw
    DN in the third ID and shouldn't conflict with search specifiers
    already in use.
    
    In effect implement what (2) in the struct asymmetric_key_id comment
    (include/keys/asymmetric-type.h) is probably talking about already, so
    do not modify that comment.  It is also how "openssl verify" looks up
    issuer certificates without the AKID available.  Lookups by the raw
    DN are unambiguous only provided that the CAs respect the condition in
    RFC5280 4.2.1.1 that the AKID may only be omitted if the CA uses
    a single signing key.
    
    The following is an example of two things that this change enables.
    A self-signed ceritficate is generated following the example from
    https://letsencrypt.org/docs/certificates-for-localhost/, and can be
    looked up by an identifier and verified against itself by linking to a
    restricted keyring -- both things not possible before due to the missing
    AKID extension:
    
    $ openssl req -x509 -out localhost.crt -outform DER -keyout localhost.key \
      -newkey rsa:2048 -nodes -sha256 \
      -subj '/CN=localhost' -extensions EXT -config <( \
       echo -e "[dn]\nCN=localhost\n[req]\ndistinguished_name = dn\n[EXT]\n" \
              "subjectAltName=DNS:localhost\nkeyUsage=digitalSignature\n" \
              "extendedKeyUsage=serverAuth")
    $ keyring=`keyctl newring test @u`
    $ trusted=`keyctl padd asymmetric trusted $keyring < localhost.crt`; \
      echo $trusted
    39726322
    $ keyctl search $keyring asymmetric dn:3112301006035504030c096c6f63616c686f7374
    39726322
    $ keyctl restrict_keyring $keyring asymmetric key_or_keyring:$trusted
    $ keyctl padd asymmetric verified $keyring < localhost.crt
    
    Signed-off-by: Andrew Zaborowski <andrew.zaborowski@intel.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
    Acked-by: David Howells <dhowells@redhat.com>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit e96d52822f5ac0a25de78f95cd23421bcbc93584
Author: Christophe Jaillet <christophe.jaillet@wanadoo.fr>
Date:   Sat Nov 6 17:42:04 2021 +0100

    tpm_tis: Fix an error handling path in 'tpm_tis_core_init()'
    
    Commit 79ca6f74dae0 ("tpm: fix Atmel TPM crash caused by too frequent
    queries") has moved some code around without updating the error handling
    path.
    
    This is now pointless to 'goto out_err' when neither 'clk_enable()' nor
    'ioremap()' have been called yet.
    
    Make a direct return instead to avoid undoing things that have not been
    done.
    
    Fixes: 79ca6f74dae0 ("tpm: fix Atmel TPM crash caused by too frequent queries")
    Signed-off-by: Christophe Jaillet <christophe.jaillet@wanadoo.fr>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit d2704808f24fbc869ba54df82d4b1af49ab496e2
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Date:   Fri Oct 29 10:09:15 2021 +0200

    tpm: tpm_tis_spi_cr50: Add default RNG quality
    
    To allow this device to fill the kernel's entropy pool at boot,
    setup a default quality for the hwrng found in Cr50.
    
    After some testing with rngtest and dieharder it was, in short,
    discovered that the RNG produces fair quality randomness, giving
    around 99.93% successes in rngtest FIPS140-2.
    
    Notably, though, when testing with dieharder it was noticed that
    we get 3 WEAK results over 114, which isn't optimal, and also
    the p-values distribution wasn't uniform in all the cases, so a
    conservative quality value was chosen by applying an arbitrary
    penalty to the calculated values.
    
    For reference, this is how the values were calculated:
    
    The dieharder results were averaged, then normalized (0-1000)
    and re-averaged with the rngtest result (where the result was
    given a score of 99.93% of 1000, so 999.3), then aggregated
    together and averaged again.
    An arbitrary penalty of -100 was applied due to the retrieved
    value, which brings us finally to 700.
    
    Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit f04510f26f82aa7cd0bf932760f01b01a010869f
Author: Sohaib Mohamed <sohaib.amhmd@gmail.com>
Date:   Wed Oct 13 11:21:50 2021 +0200

    tpm/st33zp24: drop unneeded over-commenting
    
    Remove parameter descriptions from all static functions.
    Remove the comment altogether that does not tell what the function does.
    
    Suggested-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Sohaib Mohamed <sohaib.amhmd@gmail.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit 0ef333f5ba7f24f5d8478425c163d3097f1c7afd
Author: Chen Jun <chenjun102@huawei.com>
Date:   Wed Oct 13 06:25:56 2021 +0000

    tpm: add request_locality before write TPM_INT_ENABLE
    
    Locality is not appropriately requested before writing the int mask.
    Add the missing boilerplate.
    
    Fixes: e6aef069b6e9 ("tpm_tis: convert to using locality callbacks")
    Signed-off-by: Chen Jun <chenjun102@huawei.com>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

commit b6aa86cff44cf099299d3a5e66348cb709cd7964
Author: Ingo Molnar <mingo@kernel.org>
Date:   Wed Jan 5 01:35:58 2022 +0100

    x86/kbuild: Enable CONFIG_KALLSYMS_ALL=y in the defconfigs
    
    Most distro kernels have this option enabled, to improve debug output.
    
    Lockdep also selects it.
    
    Enable this in the defconfig kernel as well, to make it more
    representative of what people are using on x86.
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    Link: https://lore.kernel.org/r/YdTn7gssoMVDMgMw@gmail.com

commit ced4913efb0acc844ed65cc01d091a85d83a2082
Author: Johan Hovold <johan@kernel.org>
Date:   Wed Dec 22 11:48:43 2021 +0100

    can: softing_cs: softingcs_probe(): fix memleak on registration failure
    
    In case device registration fails during probe, the driver state and
    the embedded platform device structure needs to be freed using
    platform_device_put() to properly free all resources (e.g. the device
    name).
    
    Fixes: 0a0b7a5f7a04 ("can: add driver for Softing card")
    Link: https://lore.kernel.org/all/20211222104843.6105-1-johan@kernel.org
    Cc: stable@vger.kernel.org # 2.6.38
    Signed-off-by: Johan Hovold <johan@kernel.org>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit bc3897f79f7901902bb44d62dd1ad1b2b48e9378
Author: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Date:   Fri Jan 7 09:13:06 2022 +0100

    docs: networking: device drivers: can: add flexcan
    
    Add initial documentation for Flexcan driver.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-8-mkl@pengutronix.de
    Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 32db1660ee01acebd18fc5759254930c874368af
Author: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Date:   Fri Jan 7 09:13:05 2022 +0100

    docs: networking: device drivers: add can sub-folder
    
    Add the container for CAN drivers documentation.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-7-mkl@pengutronix.de
    Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 74fc5a452ec3d7c051fed5e97494effb2e747d1d
Author: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Date:   Sat Jan 8 19:16:33 2022 +0100

    can: flexcan: add ethtool support to get rx/tx ring parameters
    
    This patch adds ethtool support to get the number of message buffers
    configured for reception/transmission, which may also depends on
    runtime configurations such as the 'rx-rtr' flag state.
    
    Link: https://lore.kernel.org/all/20220108181633.420433-1-dario.binacchi@amarulasolutions.com
    Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    [mkl: port to net-next/master, replace __sw_hweight64 by simpler calculation]
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 1c45f5778a3be5a67e8b318ab83664014ffa1f3e
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Tue Jan 4 16:28:00 2022 +0100

    can: flexcan: add ethtool support to change rx-rtr setting during runtime
    
    This patch adds a private flag to the flexcan driver to switch the
    "rx-rtr" setting on and off.
    
    "rx-rtr" on  - Receive RTR frames. (default)
                   The CAN controller can and will receive RTR frames.
    
                   On some IP cores the controller cannot receive RTR
                   frames in the more performant "RX mailbox" mode and
                   will use "RX FIFO" mode instead.
    
    "rx-rtr" off - Waive ability to receive RTR frames. (not supported on all IP cores)
                   This mode activates the "RX mailbox mode" for better
                   performance, on some IP cores RTR frames cannot be
                   received anymore.
    
    The "RX FIFO" mode uses a FIFO with a depth of 6 CAN frames.
    The "RX mailbox" mode uses up to 62 mailboxes.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-6-mkl@pengutronix.de
    Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    Co-developed-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 074b07d94e0bb6ddce5690a9b7e2373088e8b33a
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Wed Jan 5 14:15:03 2022 -0500

    nfsd: fix crash on COPY_NOTIFY with special stateid
    
    RTM says "If the special ONE stateid is passed to
    nfs4_preprocess_stateid_op(), it returns status=0 but does not set
    *cstid. nfsd4_copy_notify() depends on stid being set if status=0, and
    thus can crash if the client sends the right COPY_NOTIFY RPC."
    
    RFC 7862 says "The cna_src_stateid MUST refer to either open or locking
    states provided earlier by the server.  If it is invalid, then the
    operation MUST fail."
    
    The RFC doesn't specify an error, and the choice doesn't matter much as
    this is clearly illegal client behavior, but bad_stateid seems
    reasonable.
    
    Simplest is just to guarantee that nfs4_preprocess_stateid_op, called
    with non-NULL cstid, errors out if it can't return a stateid.
    
    Reported-by: rtm@csail.mit.edu
    Fixes: 624322f1adc5 ("NFSD add COPY_NOTIFY operation")
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Reviewed-by: Olga Kornievskaia <kolga@netapp.com>
    Tested-by: Olga Kornievskaia <kolga@netapp.com>

commit 7f4f5d70adfd88a08d6e122cfe2cf637ff84dd11
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Wed Jan 5 20:12:13 2022 -0500

    MAINTAINERS: remove bfields
    
    I'm cutting back on my responsibilities.  The NFS server and file
    locking code are in good hands.
    
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit fcb5e3fa012351f3b96024c07bc44834c2478213
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Fri Dec 24 14:36:49 2021 -0500

    NFSD: Move fill_pre_wcc() and fill_post_wcc()
    
    These functions are related to file handle processing and have
    nothing to do with XDR encoding or decoding. Also they are no longer
    NFSv3-specific. As a clean-up, move their definitions to a more
    appropriate location. WCC is also an NFSv3-specific term, so rename
    them as general-purpose helpers.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 58f258f65267542959487dbe8b5641754411843d
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Fri Dec 24 14:22:28 2021 -0500

    Revert "nfsd: skip some unnecessary stats in the v4 case"
    
    On the wire, I observed NFSv4 OPEN(CREATE) operations sometimes
    returning a reasonable-looking value in the cinfo.before field and
    zero in the cinfo.after field.
    
    RFC 8881 Section 10.8.1 says:
    > When a client is making changes to a given directory, it needs to
    > determine whether there have been changes made to the directory by
    > other clients.  It does this by using the change attribute as
    > reported before and after the directory operation in the associated
    > change_info4 value returned for the operation.
    
    and
    
    > ... The post-operation change
    > value needs to be saved as the basis for future change_info4
    > comparisons.
    
    A good quality client implementation therefore saves the zero
    cinfo.after value. During a subsequent OPEN operation, it will
    receive a different non-zero value in the cinfo.before field for
    that directory, and it will incorrectly believe the directory has
    changed, triggering an undesirable directory cache invalidation.
    
    There are filesystem types where fs_supports_change_attribute()
    returns false, tmpfs being one. On NFSv4 mounts, this means the
    fh_getattr() call site in fill_pre_wcc() and fill_post_wcc() is
    never invoked. Subsequently, nfsd4_change_attribute() is invoked
    with an uninitialized @stat argument.
    
    In fill_pre_wcc(), @stat contains stale stack garbage, which is
    then placed on the wire. In fill_post_wcc(), ->fh_post_wc is all
    zeroes, so zero is placed on the wire. Both of these values are
    meaningless.
    
    This fix can be applied immediately to stable kernels. Once there
    are more regression tests in this area, this optimization can be
    attempted again.
    
    Fixes: 428a23d2bf0c ("nfsd: skip some unnecessary stats in the v4 case")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 75acacb6583df0b9328dc701d8eeea05af49b8b5
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 28 14:27:56 2021 -0500

    NFSD: Trace boot verifier resets
    
    According to commit bbf2f098838a ("nfsd: Reset the boot verifier on
    all write I/O errors"), the Linux NFS server forces all clients to
    resend pending unstable writes if any server-side write or commit
    operation encounters an error (say, ENOSPC). This is a rare and
    quite exceptional event that could require administrative recovery
    action, so it should be made trace-able. Example trace event:
    
    nfsd-938   [002]  7174.945558: nfsd_writeverf_reset: boot_time=        61cc920d xid=0xdcd62036 error=-28 new verifier=0x08aecc6142515904
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 3988a57885eeac05ef89f0ab4d7e47b52fbcf630
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Dec 30 10:22:05 2021 -0500

    NFSD: Rename boot verifier functions
    
    Clean up: These functions handle what the specs call a write
    verifier, which in the Linux NFS server implementation is now
    divorced from the server's boot instance
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 91d2e9b56cf5c80f9efc530d494968369a8a0e0d
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Wed Dec 29 14:43:16 2021 -0500

    NFSD: Clean up the nfsd_net::nfssvc_boot field
    
    There are two boot-time fields in struct nfsd_net: one called
    boot_time and one called nfssvc_boot. The latter is used only to
    form write verifiers, but its documenting comment declares:
    
            /* Time of server startup */
    
    Since commit 27c438f53e79 ("nfsd: Support the server resetting the
    boot verifier"), this field can be reset at any time; it's no
    longer tied to server restart. So that comment is stale.
    
    Also, according to pahole, struct timespec64 is 16 bytes long on
    x86_64. The nfssvc_boot field is used only to form a write verifier,
    which is 8 bytes long.
    
    Let's clarify this situation by manufacturing an 8-byte verifier
    in nfs_reset_boot_verifier() and storing only that in struct
    nfsd_net.
    
    We're grabbing 128 bits of time, so compress all of those into a
    64-bit verifier instead of throwing out the high-order bits.
    In the future, the siphash_key can be re-used for other hashed
    objects per-nfsd_net.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit cdc556600c0133575487cc69fb3128440b3c3e92
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Dec 30 10:26:18 2021 -0500

    NFSD: Write verifier might go backwards
    
    When vfs_iter_write() starts to fail because a file system is full,
    a bunch of writes can fail at once with ENOSPC. These writes
    repeatedly invoke nfsd_reset_boot_verifier() in quick succession.
    
    Ensure that the time it grabs doesn't go backwards due to an ntp
    adjustment going on at the same time.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit a2f4c3fa4db94ba44d32a72201927cfd132a8e82
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Sat Dec 18 20:38:00 2021 -0500

    nfsd: Add a tracepoint for errors in nfsd4_clone_file_range()
    
    Since a clone error commit can cause the boot verifier to change,
    we should trace those errors.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    [ cel: Addressed a checkpatch.pl splat in fs/nfsd/vfs.h ]

commit 2c445a0e72cb1fbfbdb7f9473c53556ee27c1d90
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 28 14:26:03 2021 -0500

    NFSD: De-duplicate net_generic(nf->nf_net, nfsd_net_id)
    
    Since this pointer is used repeatedly, move it to a stack variable.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit fb7622c2dbd1aa41133a8c73e1137b833c074519
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 28 12:41:32 2021 -0500

    NFSD: De-duplicate net_generic(SVC_NET(rqstp), nfsd_net_id)
    
    Since this pointer is used repeatedly, move it to a stack variable.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 33388b3aefefd4d83764dab8038cb54068161a44
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 28 14:19:41 2021 -0500

    NFSD: Clean up nfsd_vfs_write()
    
    The RWF_SYNC and !RWF_SYNC arms are now exactly alike except that
    the RWF_SYNC arm resets the boot verifier twice in a row. Fix that
    redundancy and de-duplicate the code.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 555dbf1a9aac6d3150c8b52fa35f768a692f4eeb
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Sat Dec 18 20:38:01 2021 -0500

    nfsd: Replace use of rwsem with errseq_t
    
    The nfsd_file nf_rwsem is currently being used to separate file write
    and commit instances to ensure that we catch errors and apply them to
    the correct write/commit.
    We can improve scalability at the expense of a little accuracy (some
    extra false positives) by replacing the nf_rwsem with more careful
    use of the errseq_t mechanism to track errors across the different
    operations.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    [ cel: rebased on zero-verifier fix ]

commit f11ad7aa653130b71e2e89bed207f387718216d5
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 28 12:35:43 2021 -0500

    NFSD: Fix verifier returned in stable WRITEs
    
    RFC 8881 explains the purpose of the write verifier this way:
    
    > The final portion of the result is the field writeverf. This field
    > is the write verifier and is a cookie that the client can use to
    > determine whether a server has changed instance state (e.g., server
    > restart) between a call to WRITE and a subsequent call to either
    > WRITE or COMMIT.
    
    But then it says:
    
    > This cookie MUST be unchanged during a single instance of the
    > NFSv4.1 server and MUST be unique between instances of the NFSv4.1
    > server. If the cookie changes, then the client MUST assume that
    > any data written with an UNSTABLE4 value for committed and an old
    > writeverf in the reply has been lost and will need to be
    > recovered.
    
    RFC 1813 has similar language for NFSv3. NFSv2 does not have a write
    verifier since it doesn't implement the COMMIT procedure.
    
    Since commit 19e0663ff9bc ("nfsd: Ensure sampling of the write
    verifier is atomic with the write"), the Linux NFS server has
    returned a boot-time-based verifier for UNSTABLE WRITEs, but a zero
    verifier for FILE_SYNC and DATA_SYNC WRITEs. FILE_SYNC and DATA_SYNC
    WRITEs are not followed up with a COMMIT, so there's no need for
    clients to compare verifiers for stable writes.
    
    However, by returning a different verifier for stable and unstable
    writes, the above commit puts the Linux NFS server a step farther
    out of compliance with the first MUST above. At least one NFS client
    (FreeBSD) noticed the difference, making this a potential
    regression.
    
    Reported-by: Rick Macklem <rmacklem@uoguelph.ca>
    Link: https://lore.kernel.org/linux-nfs/YQXPR0101MB096857EEACF04A6DF1FC6D9BDD749@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM/T/
    Fixes: 19e0663ff9bc ("nfsd: Ensure sampling of the write verifier is atomic with the write")
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 12bcbd40fd931472c7fc9cf3bfe66799ece93ed8
Author: Jeff Layton <jeff.layton@primarydata.com>
Date:   Sat Dec 18 20:37:56 2021 -0500

    nfsd: Retry once in nfsd_open on an -EOPENSTALE return
    
    If we get back -EOPENSTALE from an NFSv4 open, then we either got some
    unhandled error or the inode we got back was not the same as the one
    associated with the dentry.
    
    We really have no recourse in that situation other than to retry the
    open, and if it fails to just return nfserr_stale back to the client.
    
    Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
    Signed-off-by: Lance Shelton <lance.shelton@hammerspace.com>
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit a2694e51f60c5a18c7e43d1a9feaa46d7f153e65
Author: Jeff Layton <jeff.layton@primarydata.com>
Date:   Sat Dec 18 20:37:55 2021 -0500

    nfsd: Add errno mapping for EREMOTEIO
    
    The NFS client can occasionally return EREMOTEIO when signalling issues
    with the server.  ...map to NFSERR_IO.
    
    Signed-off-by: Jeff Layton <jeff.layton@primarydata.com>
    Signed-off-by: Lance Shelton <lance.shelton@hammerspace.com>
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit b3d0db706c77d02055910fcfe2f6eb5155ff9d5e
Author: Peng Tao <tao.peng@primarydata.com>
Date:   Sat Dec 18 20:37:54 2021 -0500

    nfsd: map EBADF
    
    Now that we have open file cache, it is possible that another client
    deletes the file and DP will not know about it. Then IO to MDS would
    fail with BADSTATEID and knfsd would start state recovery, which
    should fail as well and then nfs read/write will fail with EBADF.
    And it triggers a WARN() in nfserrno().
    
    -----------[ cut here ]------------
    WARNING: CPU: 0 PID: 13529 at fs/nfsd/nfsproc.c:758 nfserrno+0x58/0x70 [nfsd]()
    nfsd: non-standard errno: -9
    modules linked in: nfsv3 nfs_layout_flexfiles rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_connt
    pata_acpi floppy
    CPU: 0 PID: 13529 Comm: nfsd Tainted: G        W       4.1.5-00307-g6e6579b #7
    Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014
     0000000000000000 00000000464e6c9c ffff88079085fba8 ffffffff81789936
     0000000000000000 ffff88079085fc00 ffff88079085fbe8 ffffffff810a08ea
     ffff88079085fbe8 ffff88080f45c900 ffff88080f627d50 ffff880790c46a48
     all Trace:
     [<ffffffff81789936>] dump_stack+0x45/0x57
     [<ffffffff810a08ea>] warn_slowpath_common+0x8a/0xc0
     [<ffffffff810a0975>] warn_slowpath_fmt+0x55/0x70
     [<ffffffff81252908>] ? splice_direct_to_actor+0x148/0x230
     [<ffffffffa02fb8c0>] ? fsid_source+0x60/0x60 [nfsd]
     [<ffffffffa02f9918>] nfserrno+0x58/0x70 [nfsd]
     [<ffffffffa02fba57>] nfsd_finish_read+0x97/0xb0 [nfsd]
     [<ffffffffa02fc7a6>] nfsd_splice_read+0x76/0xa0 [nfsd]
     [<ffffffffa02fcca1>] nfsd_read+0xc1/0xd0 [nfsd]
     [<ffffffffa0233af2>] ? svc_tcp_adjust_wspace+0x12/0x30 [sunrpc]
     [<ffffffffa03073da>] nfsd3_proc_read+0xba/0x150 [nfsd]
     [<ffffffffa02f7a03>] nfsd_dispatch+0xc3/0x210 [nfsd]
     [<ffffffffa0233af2>] ? svc_tcp_adjust_wspace+0x12/0x30 [sunrpc]
     [<ffffffffa0232913>] svc_process_common+0x453/0x6f0 [sunrpc]
     [<ffffffffa0232cc3>] svc_process+0x113/0x1b0 [sunrpc]
     [<ffffffffa02f740f>] nfsd+0xff/0x170 [nfsd]
     [<ffffffffa02f7310>] ? nfsd_destroy+0x80/0x80 [nfsd]
     [<ffffffff810bf3a8>] kthread+0xd8/0xf0
     [<ffffffff810bf2d0>] ? kthread_create_on_node+0x1b0/0x1b0
     [<ffffffff817912a2>] ret_from_fork+0x42/0x70
     [<ffffffff810bf2d0>] ? kthread_create_on_node+0x1b0/0x1b0
    
    Signed-off-by: Peng Tao <tao.peng@primarydata.com>
    Signed-off-by: Lance Shelton <lance.shelton@hammerspace.com>
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 6a2f774424bfdcc2df3e17de0cefe74a4269cad5
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Tue Dec 21 11:52:06 2021 -0500

    NFSD: Fix zero-length NFSv3 WRITEs
    
    The Linux NFS server currently responds to a zero-length NFSv3 WRITE
    request with NFS3ERR_IO. It responds to a zero-length NFSv4 WRITE
    with NFS4_OK and count of zero.
    
    RFC 1813 says of the WRITE procedure's @count argument:
    
    count
             The number of bytes of data to be written. If count is
             0, the WRITE will succeed and return a count of 0,
             barring errors due to permissions checking.
    
    RFC 8881 has similar language for NFSv4, though NFSv4 removed the
    explicit @count argument because that value is already contained in
    the opaque payload array.
    
    The synthetic client pynfs's WRT4 and WRT15 tests do emit zero-
    length WRITEs to exercise this spec requirement. Commit fdec6114ee1f
    ("nfsd4: zero-length WRITE should succeed") addressed the same
    problem there with the same fix.
    
    But interestingly the Linux NFS client does not appear to emit zero-
    length WRITEs, instead squelching them. I'm not aware of a test that
    can generate such WRITEs for NFSv3, so I wrote a naive C program to
    generate a zero-length WRITE and test this fix.
    
    Fixes: 8154ef2776aa ("NFSD: Clean up legacy NFS WRITE argument XDR decoders")
    Reported-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 47446d74f1707049067fee038507cdffda805631
Author: Vasily Averin <vvs@virtuozzo.com>
Date:   Fri Dec 17 09:49:39 2021 +0300

    nfsd4: add refcount for nfsd4_blocked_lock
    
    nbl allocated in nfsd4_lock can be released by a several ways:
    directly in nfsd4_lock(), via nfs4_laundromat(), via another nfs
    command RELEASE_LOCKOWNER or via nfsd4_callback.
    This structure should be refcounted to be used and released correctly
    in all these cases.
    
    Refcount is initialized to 1 during allocation and is incremented
    when nbl is added into nbl_list/nbl_lru lists.
    
    Usually nbl is linked into both lists together, so only one refcount
    is used for both lists.
    
    However nfsd4_lock() should keep in mind that nbl can be present
    in one of lists only. This can happen if nbl was handled already
    by nfs4_laundromat/nfsd4_callback/etc.
    
    Refcount is decremented if vfs_lock_file() returns FILE_LOCK_DEFERRED,
    because nbl can be handled already by nfs4_laundromat/nfsd4_callback/etc.
    
    Refcount is not changed in find_blocked_lock() because of it reuses counter
    released after removing nbl from lists.
    
    Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 40595cdc93edf4110c0f0c0b06f8d82008f23929
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Thu Dec 16 12:20:13 2021 -0500

    nfs: block notification on fs with its own ->lock
    
    NFSv4.1 supports an optional lock notification feature which notifies
    the client when a lock comes available.  (Normally NFSv4 clients just
    poll for locks if necessary.)  To make that work, we need to request a
    blocking lock from the filesystem.
    
    We turned that off for NFS in commit f657f8eef3ff ("nfs: don't atempt
    blocking locks on nfs reexports") [sic] because it actually blocks the
    nfsd thread while waiting for the lock.
    
    Thanks to Vasily Averin for pointing out that NFS isn't the only
    filesystem with that problem.
    
    Any filesystem that leaves ->lock NULL will use posix_lock_file(), which
    does the right thing.  Simplest is just to assume that any filesystem
    that defines its own ->lock is not safe to request a blocking lock from.
    
    So, this patch mostly reverts commit f657f8eef3ff ("nfs: don't atempt
    blocking locks on nfs reexports") [sic] and commit b840be2f00c0 ("lockd:
    don't attempt blocking locks on nfs reexports"), and instead uses a
    check of ->lock (Vasily's suggestion) to decide whether to support
    blocking lock notifications on a given filesystem.  Also add a little
    documentation.
    
    Perhaps someday we could add back an export flag later to allow
    filesystems with "good" ->lock methods to support blocking lock
    notifications.
    
    Reported-by: Vasily Averin <vvs@virtuozzo.com>
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    [ cel: Description rewritten to address checkpatch nits ]
    [ cel: Fixed warning when SUNRPC debugging is disabled ]
    [ cel: Fixed NULL check ]
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
    Reviewed-by: Vasily Averin <vvs@virtuozzo.com>

commit cd2e999c7c394ae916d8be741418b3c6c1dddea8
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Dec 13 10:20:45 2021 -0500

    NFSD: De-duplicate nfsd4_decode_bitmap4()
    
    Clean up. Trond points out that xdr_stream_decode_uint32_array()
    does the same thing as nfsd4_decode_bitmap4().
    
    Suggested-by: Trond Myklebust <trondmy@hammerspace.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 3dcd1d8aab00c5d3a0a3725253c86440b1a0f5a7
Author: J. Bruce Fields <bfields@redhat.com>
Date:   Tue Dec 7 17:32:21 2021 -0500

    nfsd: improve stateid access bitmask documentation
    
    The use of the bitmaps is confusing.  Add a cross-reference to make it
    easier to find the existing comment.  Add an updated reference with URL
    to make it quicker to look up.  And a bit more editorializing about the
    value of this.
    
    Signed-off-by: J. Bruce Fields <bfields@redhat.com>
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit 70e94d757b3e1f46486d573729d84c8955c81dce
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Thu Oct 21 12:11:45 2021 -0400

    NFSD: Combine XDR error tracepoints
    
    Clean up: The garbage_args and cant_encode tracepoints report the
    same information as each other, so combine them into a single
    tracepoint class to reduce code duplication and slightly reduce the
    size of trace.o.
    
    Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

commit c5c88591040ee7d84d037328eed9019d3ffab821
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Jan 7 14:29:15 2022 +0100

    can: flexcan: add more quirks to describe RX path capabilities
    
    Most flexcan IP cores support 2 RX modes:
    - FIFO
    - mailbox
    
    Some IP core versions cannot receive CAN RTR messages via mailboxes.
    This patch adds quirks to document this.
    
    This information will be used in a later patch to switch from FIFO to
    more performant mailbox mode at the expense of losing the ability to
    receive RTR messages. This trade off is beneficial in certain use
    cases.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-5-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 34ea4e1c99f1f177f87e4ae7896caef238dd741a
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Thu Jan 6 12:45:46 2022 +0100

    can: flexcan: rename RX modes
    
    Most flexcan IP cores support 2 RX modes:
    - FIFO
    - mailbox
    
    The names for these modes were chosen to reflect the name of the
    rx-offload mode they are using.
    
    The name of the RX modes should better reflect their difference with
    regards the flexcan IP core. So this patch renames the various
    occurrences of OFF_FIFO to RX_FIFO and OFF_TIMESTAMP to RX_MAILBOX:
    
    | FLEXCAN_TX_MB_RESERVED_OFF_FIFO -> FLEXCAN_TX_MB_RESERVED_RX_FIFO
    | FLEXCAN_TX_MB_RESERVED_OFF_TIMESTAMP -> FLEXCAN_TX_MB_RESERVED_RX_MAILBOX
    | FLEXCAN_QUIRK_USE_OFF_TIMESTAMP -> FLEXCAN_QUIRK_USE_RX_MAILBOX
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-4-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 01bb4dccd92b4dc21f6af3312e5696924e371111
Author: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Date:   Tue Jan 4 14:20:25 2022 +0100

    can: flexcan: allow to change quirks at runtime
    
    This is a preparation patch for the upcoming support to change the
    rx-rtr capability via the ethtool API.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-3-mkl@pengutronix.de
    Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit bfd00e021cf162049946a9e0047b0997d2b35fec
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Tue Jan 4 16:15:01 2022 +0100

    can: flexcan: move driver into separate sub directory
    
    This patch moves the flexcan driver into a separate directory, a later
    patch will add more files.
    
    Link: https://lore.kernel.org/all/20220107193105.1699523-2-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 3044a4f271d278858321675d367b37bcafca186c
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Sat Oct 23 00:27:13 2021 +0200

    can: mcp251xfd: introduce and make use of mcp251xfd_is_fd_mode()
    
    This patch replaces the open coded check, if the chip's FIFOs are
    configured for CAN-FD mode, by the newly introduced function
    mcp251xfd_is_fd_mode().
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-14-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 55bc37c85587d0c53a666a685a49752e28a31396
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri May 21 19:58:06 2021 +0200

    can: mcp251xfd: move ring init into separate function
    
    This patch moves the ring initialization from the mcp251xfd core file
    into a separate one to make the driver a bit more orderly.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-13-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 335c818c5a7ace740da837a8bb8591d5896938db
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri May 21 19:51:32 2021 +0200

    can: mcp251xfd: move chip FIFO init into separate file
    
    This patch moves the chip FIFO initialization from the mcp251xfd core
    file into a separate one to make the driver a bit more orderly.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-12-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 1e846c7aeb067fefbd53f03db56e69d160781d9d
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri May 21 19:51:32 2021 +0200

    can: mcp251xfd: move TEF handling into separate file
    
    This patch moves the TEF handling from the mcp251xfd core file into a
    separate one to make the driver a bit more orderly.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-11-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 09b0eb92fec7d5d8e6307c369e62e7c3926dd447
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri May 21 19:51:32 2021 +0200

    can: mcp251xfd: move TX handling into separate file
    
    This patch moves the TX handling from the mcp251xfd core file into a
    separate one to make the driver a bit more orderly.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-10-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 319fdbc9433c6a74fdb3993c9f5d9a1334068a21
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri May 21 19:51:32 2021 +0200

    can: mcp251xfd: move RX handling into separate file
    
    This patch moves the RX handling from the mcp251xfd core file into a
    separate one to make the driver a bit more orderly.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-9-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit cae9071bc5ea3096a5604e48e854740c12f7c1ec
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Sat May 1 11:57:49 2021 +0200

    can: mcp251xfd: mcp251xfd.h: sort function prototypes
    
    The .c files in the Makefile are ordered alphabetically. This patch
    groups the function prototypes by their corresponding .c file and
    brings the into the same order.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-8-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 58d0b0a99275c35971d2e27d317013331bd3a8c0
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Mon Nov 15 20:12:05 2021 +0100

    can: mcp251xfd: mcp251xfd_handle_rxovif(): denote RX overflow message to debug + add rate limiting
    
    A RX overflow usually happens during high system load. Printing
    overflow messages to the kernel log, which on embedded systems often
    is outputted on the serial console, even increases the system load.
    
    To decrease the system load in these situations, denote the messages
    to debug level and wrap them with net_ratelimit().
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-7-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit d84ca2217b0065ec0f27a7c34ed073ed6449e213
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Sun Apr 25 21:39:19 2021 +0200

    can: mcp251xfd: mcp251xfd_open(): make use of pm_runtime_resume_and_get()
    
    With patch
    
    | dd8088d5a896 PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter
    
    the usual pm_runtime_get_sync() and pm_runtime_put_noidle()
    in-case-of-error dance is no longer needed. Convert the mcp251xfd
    driver to use this function.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-6-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit e91aae8efc4eebd33bdebe067ab248c242cc0135
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Oct 22 18:45:05 2021 +0200

    can: mcp251xfd: mcp251xfd_open(): open_candev() first
    
    This patch exchanges the order of open_candev() and
    pm_runtime_get_sync(), so that open_candev() is called first.
    
    A usual reason why open_candev() fails is missing CAN bit rate
    configuration. It makes no sense to resume the device from PM sleep
    first just to put it to sleep if the bit rate is not configured.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-5-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 3bd9d8ce6f8c5c43ee2f1106021db0f98882cc75
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Tue Oct 19 17:05:25 2021 +0200

    can: mcp251xfd: add missing newline to printed strings
    
    This patch adds the missing newline to printed strings.
    
    Fixes: 55e5b97f003e ("can: mcp25xxfd: add driver for Microchip MCP25xxFD SPI CAN")
    Link: https://lore.kernel.org/all/20220105154300.1258636-4-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 99e7cc3b3f85d9a583ab83f386315c59443509ae
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Fri Apr 23 11:26:56 2021 +0200

    can: mcp251xfd: mcp251xfd_tef_obj_read(): fix typo in error message
    
    This patch fixes a typo in the error message in
    mcp251xfd_tef_obj_read(), if trying to read too many objects.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-3-mkl@pengutronix.de
    Fixes: 55e5b97f003e ("can: mcp25xxfd: add driver for Microchip MCP25xxFD SPI CAN")
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit 2d2116691adff8c3e24a5cb9076ea01b217b985d
Author: Marc Kleine-Budde <mkl@pengutronix.de>
Date:   Sat Nov 27 19:59:34 2021 +0100

    can: mcp251xfd: remove double blank lines
    
    This patch removes double blank lines from the driver.
    
    Link: https://lore.kernel.org/all/20220105154300.1258636-2-mkl@pengutronix.de
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit c579792562837ec2e64b006cfc9423e4177a4d26
Author: Tom Rix <trix@redhat.com>
Date:   Sat Jan 8 06:33:19 2022 -0800

    can: janz-ican3: initialize dlc variable
    
    Clang static analysis reports this problem
    janz-ican3.c:1311:2: warning: Undefined or garbage value returned to caller
            return dlc;
            ^~~~~~~~~~
    
    dlc is only set with this conditional
            if (!(cf->can_id & CAN_RTR_FLAG))
                    dlc = cf->len;
    
    But is always returned.  So initialize dlc to 0.
    
    Fixes: cc4b08c31b5c ("can: do not increase tx_bytes statistics for RTR frames")
    Link: https://lore.kernel.org/all/20220108143319.3986923-1-trix@redhat.com
    Signed-off-by: Tom Rix <trix@redhat.com>
    Acked-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
    Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

commit a403df29789ba38796edb97dad9bfb47836b68c0
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Dec 20 16:29:29 2021 -0600

    ptrace/m68k: Stop open coding ptrace_report_syscall
    
    The generic function ptrace_report_syscall does a little more
    than syscall_trace on m68k.  The function ptrace_report_syscall
    stops early if PT_TRACED is not set, it sets ptrace_message,
    and returns the result of fatal_signal_pending.
    
    Setting ptrace_message to a passed in value of 0 is effectively not
    setting ptrace_message, making that additional work a noop.
    
    Returning the result of fatal_signal_pending and letting the caller
    ignore the result becomes a noop in this change.
    
    When a process is ptraced, the flag PT_PTRACED is always set in
    current->ptrace.  Testing for PT_PTRACED in ptrace_report_syscall is
    just an optimization to fail early if the process is not ptraced.
    Later on in ptrace_notify, ptrace_stop will test current->ptrace under
    tasklist_lock and skip performing any work if the task is not ptraced.
    
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Link: https://lkml.kernel.org/r/20220103213312.9144-8-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 4264178416cd52a55a3eccbefb3973866e060280
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Dec 20 16:28:53 2021 -0600

    ptrace: Remove unused regs argument from ptrace_report_syscall
    
    Link: https://lkml.kernel.org/r/20220103213312.9144-7-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 6707d0fc60576fa8ef2dfa2f9009b606df35ba24
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Dec 20 17:15:09 2021 -0600

    ptrace: Remove second setting of PT_SEIZED in ptrace_attach
    
    The code is totally redundant remove it.
    
    Link: https://lkml.kernel.org/r/20220103213312.9144-6-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 1b5a42d9c85f0e731f01c8d1129001fd8531a8a0
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Jan 3 11:32:36 2022 -0600

    taskstats: Cleanup the use of task->exit_code
    
    In the function bacct_add_task the code reading task->exit_code was
    introduced in commit f3cef7a99469 ("[PATCH] csa: basic accounting over
    taskstats"), and it is not entirely clear what the taskstats interface
    is trying to return as only returning the exit_code of the first task
    in a process doesn't make a lot of sense.
    
    As best as I can figure the intent is to return task->exit_code after
    a task exits.  The field is returned with per task fields, so the
    exit_code of the entire process is not wanted.  Only the value of the
    first task is returned so this is not a useful way to get the per task
    ptrace stop code.  The ordinary case of returning this value is
    returning after a task exits, which also precludes use for getting
    a ptrace value.
    
    It is common to for the first task of a process to also be the last
    task of a process so this field may have done something reasonable by
    accident in testing.
    
    Make ac_exitcode a reliable per task value by always returning it for
    every exited task.
    
    Setting ac_exitcode in a sensible mannter makes it possible to continue
    to provide this value going forward.
    
    Cc: Balbir Singh <bsingharora@gmail.com>
    Fixes: f3cef7a99469 ("[PATCH] csa: basic accounting over taskstats")
    Link: https://lkml.kernel.org/r/20220103213312.9144-5-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 2d18f7f456209ed8a8fc138b8bc535dbdaf84695
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Mon Dec 20 19:16:34 2021 -0600

    exit: Use the correct exit_code in /proc/<pid>/stat
    
    Since do_proc_statt was modified to return process wide values instead
    of per task values the exit_code calculation has never been updated.
    Update it now to return the process wide exit_code when it is requested
    and available.
    
    History-Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
    Fixes: bf719d26a5c1 ("[PATCH] distinct tgid/tid CPU usage")
    Link: https://lkml.kernel.org/r/20220103213312.9144-4-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 907c311f37ba04ccebd00a9b9f3ba718e318a1de
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Tue Dec 21 10:11:01 2021 -0600

    exit: Fix the exit_code for wait_task_zombie
    
    The function wait_task_zombie is defined to always returns the process not
    thread exit status.  Unfortunately when process group exit support
    was added to wait_task_zombie the WNOWAIT case was overlooked.
    
    Usually tsk->exit_code and tsk->signal->group_exit_code will be in sync
    so fixing this is bug probably has no effect in practice.  But fix
    it anyway so that people aren't scratching their heads about why
    the two code paths are different.
    
    History-Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
    Fixes: 2c66151cbc2c ("[PATCH] sys_exit() threading improvements, BK-curr")
    Link: https://lkml.kernel.org/r/20220103213312.9144-3-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 270b6541e603a7fae0cad7af3dc3bca6adb343f3
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Thu Dec 23 10:05:19 2021 -0600

    exit: Coredumps reach do_group_exit
    
    The comment about coredumps not reaching do_group_exit and the
    corresponding BUG_ON are bogus.
    
    What happens and has happened for years is that get_signal calls
    do_coredump (which sets SIGNAL_GROUP_EXIT and group_exit_code) and
    then do_group_exit passing the signal number.  Then do_group_exit
    ignores the exit_code it is passed and uses signal->group_exit_code
    from the coredump.
    
    The comment and BUG_ON were correct when they were added during the
    2.5 development cycle, but became obsolete and incorrect when
    get_signal was changed to fall through to do_group_exit after
    do_coredump in 2.6.10-rc2.
    
    So remove the stale comment and BUG_ON
    
    Fixes: 63bd6144f191 ("[PATCH] Invalid BUG_ONs in signal.c")
    History-Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
    Link: https://lkml.kernel.org/r/20220103213312.9144-2-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 2873cd31a20c25b5e763b35e5fb886f0938c6dd5
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 10:03:24 2022 -0600

    exit: Remove profile_handoff_task
    
    All profile_handoff_task does is notify the task_free_notifier chain.
    The helpers task_handoff_register and task_handoff_unregister are used
    to add and delete entries from that chain and are never called.
    
    So remove the dead code and make it much easier to read and reason
    about __put_task_struct.
    
    Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
    Link: https://lkml.kernel.org/r/87fspyw6m0.fsf@email.froward.int.ebiederm.org
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 2d4bcf886e42f0f4846a3d9bdc3a90d278903a2e
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 11:23:02 2022 -0600

    exit: Remove profile_task_exit & profile_munmap
    
    When I say remove I mean remove.  All profile_task_exit and
    profile_munmap do is call a blocking notifier chain.  The helpers
    profile_task_register and profile_task_unregister are not called
    anywhere in the tree.  Which means this is all dead code.
    
    So remove the dead code and make it easier to read do_exit.
    
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Link: https://lkml.kernel.org/r/20220103213312.9144-1-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 6410349ea5e177f3e53c2006d2041eed47e986ae
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Tue Dec 21 19:10:27 2021 -0800

    signal: clean up kernel-doc comments
    
    Fix kernel-doc warnings in kernel/signal.c:
    
    kernel/signal.c:1830: warning: Function parameter or member 'force_coredump' not described in 'force_sig_seccomp'
    kernel/signal.c:2873: warning: missing initial short description on line:
     * signal_delivered -
    
    Also add a closing parenthesis to the comments in signal_delivered().
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Alexander Viro <viro@zeniv.linux.org.uk>
    Cc: Richard Weinberger <richard@nod.at>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: "Eric W. Biederman" <ebiederm@xmission.com>
    Cc: Jens Axboe <axboe@kernel.dk>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Marco Elver <elver@google.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Link: https://lkml.kernel.org/r/20211222031027.29694-1-rdunlap@infradead.org
    Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>

commit 49697335e0b441b0553598c1b48ee9ebb053d2f1
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Thu Jun 24 02:14:30 2021 -0500

    signal: Remove the helper signal_group_exit
    
    This helper is misleading.  It tests for an ongoing exec as well as
    the process having received a fatal signal.
    
    Sometimes it is appropriate to treat an on-going exec differently than
    a process that is shutting down due to a fatal signal.  In particular
    taking the fast path out of exit_signals instead of retargeting
    signals is not appropriate during exec, and not changing the the exit
    code in do_group_exit during exec.
    
    Removing the helper makes it more obvious what is going on as both
    cases must be coded for explicitly.
    
    While removing the helper fix the two cases where I have observed
    using signal_group_exit resulted in the wrong result.
    
    In exit_signals only test for SIGNAL_GROUP_EXIT so that signals are
    retargetted during an exec.
    
    In do_group_exit use 0 as the exit code during an exec as de_thread
    does not set group_exit_code.  As best as I can determine
    group_exit_code has been is set to 0 most of the time during
    de_thread.  During a thread group stop group_exit_code is set to the
    stop signal and when the thread group receives SIGCONT group_exit_code
    is reset to 0.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-8-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 60700e38fb68e800607ca7a027060d5419fc5798
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sun Jun 6 13:47:53 2021 -0500

    signal: Rename group_exit_task group_exec_task
    
    The only remaining user of group_exit_task is exec.  Rename the field
    so that it is clear which part of the code uses it.
    
    Update the comment above the definition of group_exec_task to document
    how it is currently used.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-7-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 6ac79ec5378b675f91021c8073cde0eea59f81ad
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Fri Nov 19 12:11:54 2021 -0600

    coredump: Stop setting signal->group_exit_task
    
    Currently the coredump code sets group_exit_task so that
    signal_group_exit() will return true during a coredump.  Now that the
    coredump code always sets SIGNAL_GROUP_EXIT there is no longer a need
    to set signal->group_exit_task.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-6-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 2f824d4d197e02275562359a2ae5274177ce500c
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 09:48:31 2022 -0600

    signal: Remove SIGNAL_GROUP_COREDUMP
    
    After the previous cleanups "signal->core_state" is set whenever
    SIGNAL_GROUP_COREDUMP is set and "signal->core_state" is tested
    whenver the code wants to know if a coredump is in progress.  The
    remaining tests of SIGNAL_GROUP_COREDUMP also test to see if
    SIGNAL_GROUP_EXIT is set.  Similarly the only place that sets
    SIGNAL_GROUP_COREDUMP also sets SIGNAL_GROUP_EXIT.
    
    Which makes SIGNAL_GROUP_COREDUMP unecessary and redundant. So stop
    setting SIGNAL_GROUP_COREDUMP, stop testing SIGNAL_GROUP_COREDUMP, and
    remove it's definition.
    
    With the setting of SIGNAL_GROUP_COREDUMP gone, coredump_finish no
    longer needs to clear SIGNAL_GROUP_COREDUMP out of signal->flags
    by setting SIGNAL_GROUP_EXIT.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-5-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 752dc9707567f39ed7850e21796cf2b467d71ad5
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 09:44:58 2022 -0600

    signal: During coredumps set SIGNAL_GROUP_EXIT in zap_process
    
    There are only a few places that test SIGNAL_GROUP_EXIT and
    are not also already testing SIGNAL_GROUP_COREDUMP.
    
    This will not affect the callers of signal_group_exit as zap_process
    also sets group_exit_task so signal_group_exit will continue to return
    true at the same times.
    
    This does not affect wait_task_zombie as the none of the threads
    wind up in EXIT_ZOMBIE state during a coredump.
    
    This does not affect oom_kill.c:__task_will_free_mem as
    sig->core_state is tested and handled before SIGNAL_GROUP_EXIT is
    tested for.
    
    This does not affect complete_signal as signal->core_state is tested
    for to ensure the coredump case is handled appropriately.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-4-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 7ba03471ac4ad2432e5ccf67d9d4ab03c177578a
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 11:01:12 2022 -0600

    signal: Make coredump handling explicit in complete_signal
    
    Ever since commit 6cd8f0acae34 ("coredump: ensure that SIGKILL always
    kills the dumping thread") it has been possible for a SIGKILL received
    during a coredump to set SIGNAL_GROUP_EXIT and trigger a process
    shutdown (for a second time).
    
    Update the logic to explicitly allow coredumps so that coredumps can
    set SIGNAL_GROUP_EXIT and shutdown like an ordinary process.
    
    Link: https://lkml.kernel.org/r/87zgo6ytyf.fsf_-_@email.froward.int.ebiederm.org
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit a0287db0f1d6918919203ba31fd7cda59bf889e8
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Sat Jan 8 09:34:50 2022 -0600

    signal: Have prepare_signal detect coredumps using signal->core_state
    
    In preparation for removing the flag SIGNAL_GROUP_COREDUMP, change
    prepare_signal to test signal->core_state instead of the flag
    SIGNAL_GROUP_COREDUMP.
    
    Both fields are protected by siglock and both live in signal_struct so
    there are no real tradeoffs here, just a change to which field is
    being tested.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-1-ebiederm@xmission.com
    Link: https://lkml.kernel.org/r/875yqu14co.fsf_-_@email.froward.int.ebiederm.org
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 98b24b16b2aebffabf5b8670f44f19666c1e029f
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Fri Nov 19 11:29:48 2021 -0600

    signal: Have the oom killer detect coredumps using signal->core_state
    
    In preparation for removing the flag SIGNAL_GROUP_COREDUMP, change
    __task_will_free_mem to test signal->core_state instead of the flag
    SIGNAL_GROUP_COREDUMP.
    
    Both fields are protected by siglock and both live in signal_struct so
    there are no real tradeoffs here, just a change to which field is
    being tested.
    
    Link: https://lkml.kernel.org/r/20211213225350.27481-3-ebiederm@xmission.com
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit bbd0ff07ed12fda9dbd0cc5f239bb678a775833a
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:10 2022 -0600

    dt-bindings: dma-controller: Split interrupt fields in example
    
    Best practice for multi-cell property values is to bracket each multi-cell
    value.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-2-robh@kernel.org
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit de77c3a5b95c95a4915142071643d94e3e1ada35
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Fri Jan 7 12:18:12 2022 -0600

    exit: Move force_uaccess back into do_exit
    
    With kernel threads on architectures that still have set_fs/get_fs
    running as KERNEL_DS moving force_uaccess_begin does not appear safe.
    Calling force_uaccess_begin is a noop on anything people care about.
    
    Update the comment to explain why this code while looking like an
    obvious candidate for moving to make_task_dead probably needs to
    remain in do_exit until set_fs/get_fs are entirely removed from the
    kernel.
    
    Fixes: 05ea0424f0e2 ("exit: Move oops specific logic from do_exit into make_task_dead")
    Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
    Link: https://lkml.kernel.org/r/YdUxGKRcSiDy8jGg@zeniv-ca.linux.org.uk
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 912616f142bfeb1dc41f40dbe7ce38331886a94a
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Jan 5 16:30:21 2022 -0600

    exit: Guarantee make_task_dead leaks the tsk when calling do_task_exit
    
    Change the task state to EXIT_DEAD and take an extra rcu_refernce
    to guarantee the task will not be reaped and that it will not be
    freed.
    
    Link: https://lkml.kernel.org/r/YdUzjrLAlRiNLQp2@zeniv-ca.linux.org.uk
    Pointed-out-by: Al Viro <viro@zeniv.linux.org.uk>
    Fixes: 7f80a2fd7db9 ("exit: Stop poorly open coding do_task_dead in make_task_dead")
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 64aa8f4b6df107f46b6ac3e5331819824626b0af
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Jan 6 22:52:10 2022 +0100

    dmaengine: pch_dma: Remove usage of the deprecated "pci-dma-compat.h" API
    
    In [1], Christoph Hellwig has proposed to remove the wrappers in
    include/linux/pci-dma-compat.h.
    
    Some reasons why this API should be removed have been given by Julia
    Lawall in [2].
    
    A coccinelle script has been used to perform the needed transformation.
    It can be found in [3].
    
    [1]: https://lore.kernel.org/kernel-janitors/20200421081257.GA131897@infradead.org/
    [2]: https://lore.kernel.org/kernel-janitors/alpine.DEB.2.22.394.2007120902170.2424@hadrien/
    [3]: https://lore.kernel.org/kernel-janitors/20200716192821.321233-1-christophe.jaillet@wanadoo.fr/
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Reviewed-by: Arnd Bergmann <arnd@arndb.de>
    Link: https://lore.kernel.org/r/b88f25f3d07be92dd75494dc129a85619afb1366.1641500561.git.christophe.jaillet@wanadoo.fr
    Signed-off-by: Vinod Koul <vkoul@kernel.org>

commit 85be9ae7b63092895b6e7ac87a3ef383c679866c
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Jan 5 14:59:48 2022 -0600

    exit/xtensa: In arch/xtensa/entry.S:Linvalid_mask call make_task_dead
    
    There have historically been two big uses of do_exit.  The first is
    it's design use to be the guts of the exit(2) system call.  The second
    use is to terminate a task after something catastrophic has happened
    like a NULL pointer in kernel code.  The function make_task_dead
    has been added to accomidate the second use.
    
    The call to do_exit in Linvalidmask is clearly not a normal userspace
    exit.  As failure handling there are two possible ways to go.
    If userspace can trigger the issue force_exit_sig should be called.
    Otherwise make_task_dead probably from the implementation of die
    is appropriate.
    
    Replace the call of do_exit in Linvalidmask with make_task_dead as
    I don't know xtensa and especially xtensa assembly language well
    enough to do anything else.
    
    Link: https://lkml.kernel.org/r/YdUmN7n4W5YETUhW@zeniv-ca.linux.org.uk
    Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit 0704a8586f75663cf30a283bbeeca09eb4e60a07
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 10:54:01 2022 +0100

    s390/dasd: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the s390 dasd sysfs code to use default_groups field
    which has been the preferred way since commit aa30f47cf666 ("kobject:
    Add support for default attribute groups to kobj_type") so that we can
    soon get rid of the obsolete default_attrs field.
    
    Cc: Stefan Haberland <sth@linux.ibm.com>
    Cc: Jan Hoeppner <hoeppner@linux.ibm.com>
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Cc: Alexander Gordeev <agordeev@linux.ibm.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220106095401.3274637-1-gregkh@linuxfoundation.org
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 1350f36d3825e8f9563bbffb047d6ee634949667
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 10:52:52 2022 +0100

    s390/sclp_sd: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the sclp_sd sysfs code to use default_groups field which
    has been the preferred way since commit aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can
    soon get rid of the obsolete default_attrs field.
    
    Cc: Vasily Gorbik <gor@linux.ibm.com>
    Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
    Cc: Alexander Gordeev <agordeev@linux.ibm.com>
    Cc: Peter Oberparleiter <oberpar@linux.ibm.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220106095252.3273905-1-gregkh@linuxfoundation.org
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 3367d1bd738c01b2737eaab7d922bfe5f1a41f38
Author: Thomas Weißschuh <linux@weissschuh.net>
Date:   Sat Jan 8 16:31:58 2022 +0100

    power: supply: Provide stubs for charge_behaviour helpers
    
    When CONFIG_SYSFS is not enabled provide stubs for the helper functions
    to not break their callers.
    
    Fixes: 539b9c94ac83 ("power: supply: add helpers for charge_behaviour sysfs")
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
    Link: https://lore.kernel.org/r/20220108153158.189489-1-linux@weissschuh.net
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 02fb09459435add44bb00191ce9b040c6b4f3aae
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sat Jan 8 16:49:47 2022 +0100

    platform/x86: x86-android-tablets: Fix GPIO lookup leak on error-exit
    
    Fix leaking the registered gpiod_lookup tables when the kcalloc() for the
    i2c_clients array fails.
    
    Fixes: ef2ac11493e2 ("platform/x86: x86-android-tablets: Add support for registering GPIO lookup tables")
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220108154947.136593-1-hdegoede@redhat.com

commit 62ac88a7b4619627ad2fc87f9910d63664805e85
Author: Daniel Scally <djrscally@gmail.com>
Date:   Thu Jan 6 23:20:45 2022 +0000

    platform/x86: int3472: Add board data for Surface Go 3
    
    The Surface Go 3 needs some board data in order to configure the
    TPS68470 PMIC - add entries to the tables in tps68470_board_data.c
    that define the configuration that's needed.
    
    Signed-off-by: Daniel Scally <djrscally@gmail.com>
    Link: https://lore.kernel.org/r/20220106232045.41291-1-djrscally@gmail.com
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>

commit 751971af2e3615dc5bd12674080bc795505fefeb
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Dec 27 11:48:51 2021 -0700

    csky: Fix function name in csky_alignment() and die()
    
    When building ARCH=csky defconfig:
    
    arch/csky/kernel/traps.c: In function 'die':
    arch/csky/kernel/traps.c:112:17: error: implicit declaration of function
    'make_dead_task' [-Werror=implicit-function-declaration]
      112 |                 make_dead_task(SIGSEGV);
          |                 ^~~~~~~~~~~~~~
    
    The function's name is make_task_dead(), change it so there is no more
    build error.
    
    Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Reviewed-by: Guo Ren <guoren@kernel.org>
    Link: https://lkml.kernel.org/r/20211227184851.2297759-4-nathan@kernel.org
    Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>

commit ab4ababdf77ccc56c7301c751dff49c79709c51c
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Dec 27 11:48:50 2021 -0700

    h8300: Fix build errors from do_exit() to make_task_dead() transition
    
    When building ARCH=h8300 defconfig:
    
    arch/h8300/kernel/traps.c: In function 'die':
    arch/h8300/kernel/traps.c:109:2: error: implicit declaration of function
    'make_dead_task' [-Werror=implicit-function-declaration]
      109 |  make_dead_task(SIGSEGV);
          |  ^~~~~~~~~~~~~~
    
    arch/h8300/mm/fault.c: In function 'do_page_fault':
    arch/h8300/mm/fault.c:54:2: error: implicit declaration of function
    'make_dead_task' [-Werror=implicit-function-declaration]
       54 |  make_dead_task(SIGKILL);
          |  ^~~~~~~~~~~~~~
    
    The function's name is make_task_dead(), change it so there is no more
    build error.
    
    Additionally, include linux/sched/task.h in arch/h8300/kernel/traps.c
    to avoid the same error because do_exit()'s declaration is in kernel.h
    but make_task_dead()'s is in task.h, which is not included in traps.c.
    
    Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lkml.kernel.org/r/20211227184851.2297759-3-nathan@kernel.org
    Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>

commit 4f0712ccec09c071e221242a2db9a6779a55a949
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Mon Dec 27 11:48:49 2021 -0700

    hexagon: Fix function name in die()
    
    When building ARCH=hexagon defconfig:
    
    arch/hexagon/kernel/traps.c:217:2: error: implicit declaration of
    function 'make_dead_task' [-Werror,-Wimplicit-function-declaration]
            make_dead_task(err);
            ^
    
    The function's name is make_task_dead(), change it so there is no more
    build error.
    
    Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lkml.kernel.org/r/20211227184851.2297759-2-nathan@kernel.org
    Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>

commit e32cf5dfbe227b355776948b2c9b5691b84d1cbd
Author: Eric W. Biederman <ebiederm@xmission.com>
Date:   Wed Dec 22 22:10:09 2021 -0600

    kthread: Generalize pf_io_worker so it can point to struct kthread
    
    The point of using set_child_tid to hold the kthread pointer was that
    it already did what is necessary.  There are now restrictions on when
    set_child_tid can be initialized and when set_child_tid can be used in
    schedule_tail.  Which indicates that continuing to use set_child_tid
    to hold the kthread pointer is a bad idea.
    
    Instead of continuing to use the set_child_tid field of task_struct
    generalize the pf_io_worker field of task_struct and use it to hold
    the kthread pointer.
    
    Rename pf_io_worker (which is a void * pointer) to worker_private so
    it can be used to store kthreads struct kthread pointer.  Update the
    kthread code to store the kthread pointer in the worker_private field.
    Remove the places where set_child_tid had to be dealt with carefully
    because kthreads also used it.
    
    Link: https://lkml.kernel.org/r/CAHk-=wgtFAA9SbVYg0gR1tqPMC17-NYcs0GQkaYg1bGhh1uJQQ@mail.gmail.com
    Link: https://lkml.kernel.org/r/87a6grvqy8.fsf_-_@email.froward.int.ebiederm.org
    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>

commit da17d6905d29ddcdc04b2fdc37ed8cf1e8437cc8
Author: Stephen Boyd <swboyd@chromium.org>
Date:   Fri Jan 7 11:42:32 2022 -0800

    of/fdt: Don't worry about non-memory region overlap for no-map
    
    In commit 8a5a75e5e9e5 ("of/fdt: Make sure no-map does not remove
    already reserved regions") we returned -EBUSY when trying to mark
    regions as no-map when they intersect with reserved memory. The goal was
    to find bad no-map reserved memory DT nodes that would unmap the kernel
    text/data sections.
    
    The problem is the reserved memory check will still trigger if the DT
    has a /memreserve/ that completely subsumes the no-map memory carveouts
    in the reserved memory node _and_ that region is also not part of the
    memory reg property. For example in sc7180.dtsi we have the following
    reserved-memory and memory node:
    
          memory@80000000 {
              /* We expect the bootloader to fill in the size */
              reg = <0 0x80000000 0 0>;
          };
    
          smem_mem: memory@80900000 {
                  reg = <0x0 0x80900000 0x0 0x200000>;
                  no-map;
          };
    
    and the memreserve filled in by the bootloader is
    
          /memreserve/ 0x80800000 0x400000;
    
    while the /memory node is transformed into
    
          memory@80000000 {
              /* The bootloader fills in the size, and adds another region */
              reg = <0 0x80000000 0 0x00800000>,
                    <0 0x80c00000 0 0x7f200000>;
          };
    
    The smem region is doubly reserved via /memreserve/ and by not being
    part of the /memory reg property. This leads to the following warning
    printed at boot.
    
     OF: fdt: Reserved memory: failed to reserve memory for node 'memory@80900000': base 0x0000000080900000, size 2 MiB
    
    Otherwise nothing really goes wrong because the smem region is not going
    to be mapped by the kernel's direct linear mapping given that it isn't
    part of the memory node. Therefore, let's only consider this to be a
    problem if we're trying to mark a region as no-map and it is actually
    memory that we're intending to keep out of the kernel's direct mapping
    but it's already been reserved.
    
    Acked-by: Mike Rapoport <rppt@kernel.org>
    Cc: Douglas Anderson <dianders@chromium.org>
    Cc: Nicolas Boichat <drinkcat@chromium.org>
    Cc: Quentin Perret <qperret@google.com>
    Cc: Jan Kiszka <jan.kiszka@siemens.com>
    Fixes: 8a5a75e5e9e5 ("of/fdt: Make sure no-map does not remove already reserved regions")
    Signed-off-by: Stephen Boyd <swboyd@chromium.org>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220107194233.2793146-1-swboyd@chromium.org

commit 2b35e9684d093569fd4743719bccdd7409eb9f8e
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Fri Jan 7 08:28:26 2022 +0800

    of: unittest: remove unneeded semicolon
    
    Eliminate the following coccicheck warning:
    ./drivers/of/unittest.c:1961:2-3: Unneeded semicolon
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220107002826.77939-1-yang.lee@linux.alibaba.com

commit 5d05b811b5acb92fc581a7b328b36646c86f5ab9
Author: Baruch Siach <baruch@tkos.co.il>
Date:   Thu Dec 30 18:31:53 2021 +0200

    of: base: Improve argument length mismatch error
    
    The cells_name field of of_phandle_iterator might be NULL. Use the
    phandle name instead. With this change instead of:
    
      OF: /soc/pinctrl@1000000: (null) = 3 found 2
    
    We get:
    
      OF: /soc/pinctrl@1000000: phandle pinctrl@1000000 needs 3, found 2
    
    Which is a more helpful messages making DT debugging easier.
    
    In this particular example the phandle name looks like duplicate of the
    same node name. But note that the first node is the parent node
    (it->parent), while the second is the phandle target (it->node). They
    happen to be the same in the case that triggered this improvement. See
    commit 72cb4c48a46a ("arm64: dts: qcom: ipq6018: Fix gpio-ranges
    property").
    
    Signed-off-by: Baruch Siach <baruch@tkos.co.il>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/f6a68e0088a552ea9dfd4d8e3b5b586d92594738.1640881913.git.baruch@tkos.co.il

commit cbb4f5f435995a56ef770e35bfafb4bcff8f0ada
Author: Pavel Hofman <pavel.hofman@ivitera.com>
Date:   Sat Jan 8 11:56:08 2022 +0100

    docs: ABI: fixed formatting in configfs-usb-gadget-uac2
    
    Added missing tab, line breaks.
    
    Fixes: e3088ebc1b97 ("docs: ABI: added missing num_requests param to UAC2")
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Pavel Hofman <pavel.hofman@ivitera.com>
    Link: https://lore.kernel.org/r/20220108105608.10726-1-pavel.hofman@ivitera.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 94a4950a4acff39b5847cc1fee4f65e160813493
Author: Baruch Siach <baruch@tkos.co.il>
Date:   Thu Dec 30 18:31:52 2021 +0200

    of: base: Fix phandle argument length mismatch error message
    
    The cell_count field of of_phandle_iterator is the number of cells we
    expect in the phandle arguments list when cells_name is missing. The
    error message should show the number of cells we actually see.
    
    Fixes: af3be70a3211 ("of: Improve of_phandle_iterator_next() error message")
    Cc: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Baruch Siach <baruch@tkos.co.il>
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/96519ac55be90a63fa44afe01480c30d08535465.1640881913.git.baruch@tkos.co.il

commit 0422fe2666aea4c0986f4c89dc107731aa6a7a81
Merge: 4b3ddc6462e83 d1587f7bfe9a0
Author: Ingo Molnar <mingo@kernel.org>
Date:   Sat Jan 8 10:53:57 2022 +0100

    Merge branch 'linus' into irq/core, to fix conflict
    
    Conflicts:
            drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>

commit c199d5d0a79d4eb11623e0eb645b27d271f8d713
Author: Miguel Ojeda <ojeda@kernel.org>
Date:   Fri Dec 31 20:59:25 2021 +0100

    doc: kbuild: fix default in `imply` table
    
    `BAZ` takes `FOO`'s value as default (as far as `BAR` allows it).
    
    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit c0ee9bba55e1fda8ca22a2ac714d54737def50d4
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:55 2021 +0900

    microblaze: use built-in function to get CPU_{MAJOR,MINOR,REV}
    
    Use built-in functions instead of shell commands to avoid forking
    processes.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 340a02535ee785c64c62a9c45706597a0139e972
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:54 2021 +0900

    certs: move scripts/extract-cert to certs/
    
    extract-cert is only used in certs/Makefile.
    
    Move it there and build extract-cert on demand.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 129ab0d2d9f38b9d43df35235fc66c6740d6928b
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:53 2021 +0900

    kbuild: do not quote string values in include/config/auto.conf
    
    The previous commit fixed up all shell scripts to not include
    include/config/auto.conf.
    
    Now that include/config/auto.conf is only included by Makefiles,
    we can change it into a more Make-friendly form.
    
    Previously, Kconfig output string values enclosed with double-quotes
    (both in the .config and include/config/auto.conf):
    
        CONFIG_X="foo bar"
    
    Unlike shell, Make handles double-quotes (and single-quotes as well)
    verbatim. We must rip them off when used.
    
    There are some patterns:
    
      [1] $(patsubst "%",%,$(CONFIG_X))
      [2] $(CONFIG_X:"%"=%)
      [3] $(subst ",,$(CONFIG_X))
      [4] $(shell echo $(CONFIG_X))
    
    These are not only ugly, but also fragile.
    
    [1] and [2] do not work if the value contains spaces, like
       CONFIG_X=" foo bar "
    
    [3] does not work correctly if the value contains double-quotes like
       CONFIG_X="foo\"bar"
    
    [4] seems to work better, but has a cost of forking a process.
    
    Anyway, quoted strings were always PITA for our Makefiles.
    
    This commit changes Kconfig to stop quoting in include/config/auto.conf.
    
    These are the string type symbols referenced in Makefiles or scripts:
    
        ACPI_CUSTOM_DSDT_FILE
        ARC_BUILTIN_DTB_NAME
        ARC_TUNE_MCPU
        BUILTIN_DTB_SOURCE
        CC_IMPLICIT_FALLTHROUGH
        CC_VERSION_TEXT
        CFG80211_EXTRA_REGDB_KEYDIR
        EXTRA_FIRMWARE
        EXTRA_FIRMWARE_DIR
        EXTRA_TARGETS
        H8300_BUILTIN_DTB
        INITRAMFS_SOURCE
        LOCALVERSION
        MODULE_SIG_HASH
        MODULE_SIG_KEY
        NDS32_BUILTIN_DTB
        NIOS2_DTB_SOURCE
        OPENRISC_BUILTIN_DTB
        SOC_CANAAN_K210_DTB_SOURCE
        SYSTEM_BLACKLIST_HASH_LIST
        SYSTEM_REVOCATION_KEYS
        SYSTEM_TRUSTED_KEYS
        TARGET_CPU
        UNUSED_KSYMS_WHITELIST
        XILINX_MICROBLAZE0_FAMILY
        XILINX_MICROBLAZE0_HW_VER
        XTENSA_VARIANT_NAME
    
    I checked them one by one, and fixed up the code where necessary.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 7d153696e5db1e37387c2f7ec06ffc8d4aac70a4
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:52 2021 +0900

    kbuild: do not include include/config/auto.conf from shell scripts
    
    Richard Weinberger pointed out the risk of sourcing the kernel config
    from shell scripts [1], and proposed some patches [2], [3]. It is a good
    point, but it took a long time because I was wondering how to fix this.
    
    This commit goes with simple grep approach because there are only a few
    scripts including the kernel configuration.
    
    scripts/link_vmlinux.sh has references to a bunch of CONFIG options,
    all of which are boolean. I added is_enabled() helper as
    scripts/package/{mkdebian,builddeb} do.
    
    scripts/gen_autoksyms.sh uses 'eval', stating "to expand the whitelist
    path". I removed it since it is the issue we are trying to fix.
    
    I was a bit worried about the cost of invoking the grep command over
    again. I extracted the grep parts from it, and measured the cost. It
    was approximately 0.03 sec, which I hope is acceptable.
    
    [test code]
    
      $ cat test-grep.sh
      #!/bin/sh
    
      is_enabled() {
              grep -q "^$1=y" include/config/auto.conf
      }
    
      is_enabled CONFIG_LTO_CLANG
      is_enabled CONFIG_LTO_CLANG
      is_enabled CONFIG_STACK_VALIDATION
      is_enabled CONFIG_UNWINDER_ORC
      is_enabled CONFIG_FTRACE_MCOUNT_USE_OBJTOOL
      is_enabled CONFIG_VMLINUX_VALIDATION
      is_enabled CONFIG_FRAME_POINTER
      is_enabled CONFIG_GCOV_KERNEL
      is_enabled CONFIG_LTO_CLANG
      is_enabled CONFIG_RETPOLINE
      is_enabled CONFIG_X86_SMAP
      is_enabled CONFIG_LTO_CLANG
      is_enabled CONFIG_VMLINUX_MAP
      is_enabled CONFIG_KALLSYMS_ALL
      is_enabled CONFIG_KALLSYMS_ABSOLUTE_PERCPU
      is_enabled CONFIG_KALLSYMS_BASE_RELATIVE
      is_enabled CONFIG_DEBUG_INFO_BTF
      is_enabled CONFIG_KALLSYMS
      is_enabled CONFIG_DEBUG_INFO_BTF
      is_enabled CONFIG_BPF
      is_enabled CONFIG_BUILDTIME_TABLE_SORT
      is_enabled CONFIG_KALLSYMS
    
      $ time ./test-grep.sh
      real    0m0.036s
      user    0m0.027s
      sys     m0.009s
    
    [1]: https://lore.kernel.org/all/1919455.eZKeABUfgV@blindfold/
    [2]: https://lore.kernel.org/all/20180219092245.26404-1-richard@nod.at/
    [3]: https://lore.kernel.org/all/20210920213957.1064-2-richard@nod.at/
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit b8c96a6b466ca3b91530a4ec7f7404f40f8f4d0b
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:51 2021 +0900

    certs: simplify $(srctree)/ handling and remove config_filename macro
    
    The complex macro, config_filename, was introduced to do:
    
     [1] drop double-quotes from the string value
     [2] add $(srctree)/ prefix in case the file is not found in $(objtree)
     [3] escape spaces and more
    
    [1] will be more generally handled by Kconfig later.
    
    As for [2], Kbuild uses VPATH to search for files in $(objtree),
    $(srctree) in this order. GNU Make can natively handle it.
    
    As for [3], converting $(space) to $(space_escape) back and forth looks
    questionable to me. It is well-known that GNU Make cannot handle file
    paths with spaces in the first place.
    
    Instead of using the complex macro, use $< so it will be expanded to
    the file path of the key.
    
    Remove config_filename, finally.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 4db9c2e3d055cc11e64b5c9bbaa70b5a552adf0f
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:50 2021 +0900

    kbuild: stop using config_filename in scripts/Makefile.modsign
    
    Toward the goal of removing the config_filename macro, drop
    the double-quotes and add $(srctree)/ prefix in an ad hoc way.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 5410f3e810f64366ada353efa5e7559be040fb71
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:49 2021 +0900

    certs: remove misleading comments about GCC PR
    
    This dependency is necessary irrespective of the mentioned GCC PR
    because the embedded certificates are build artifacts and must be
    generated by extract_certs before *.S files are compiled.
    
    The comment sounds like we are hoping to remove these dependencies
    someday. No, we cannot remove them.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 5cca36069d4c2942a46f98f47b9e7160fd547e03
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:48 2021 +0900

    certs: refactor file cleaning
    
    'make clean' removes files listed in 'targets'. It is redundant to
    specify both 'targets' and 'clean-files'.
    
    Move 'targets' assignments out of the ifeq-conditionals so
    scripts/Makefile.clean can see them.
    
    One effective change is that certs/certs/signing_key.x509 is now
    deleted by 'make clean' instead of 'make mrproper. This certificate
    is embedded in the kernel. It is not used in any way by external
    module builds.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 3958f2156b418c9dce0a4402a59d95b122a92a04
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:47 2021 +0900

    certs: remove unneeded -I$(srctree) option for system_certificates.o
    
    The .incbin directive in certs/system_certificates.S includes
    certs/signing_key.x509 and certs/x509_certificate_list, both of which
    are generated by extract_certs, i.e. exist in $(objtree).
    
    This option -I$(srctree) is unneeded.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 1c4bd9f77a1c1b8502ca929fdbe2ef45bfebd09a
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:46 2021 +0900

    certs: unify duplicated cmd_extract_certs and improve the log
    
    cmd_extract_certs is defined twice. Unify them.
    
    The current log shows the input file $(2), which might be empty.
    You cannot know what is being created from the log, "EXTRACT_CERTS".
    
    Change the log to show the output file with better alignment.
    
    [Before]
    
      EXTRACT_CERTS   certs/signing_key.pem
      CC      certs/system_keyring.o
      EXTRACT_CERTS
      AS      certs/system_certificates.o
      CC      certs/common.o
      CC      certs/blacklist.o
      EXTRACT_CERTS
      AS      certs/revocation_certificates.o
    
    [After]
    
      CERT    certs/signing_key.x509
      CC      certs/system_keyring.o
      CERT    certs/x509_certificate_list
      AS      certs/system_certificates.o
      CC      certs/common.o
      CC      certs/blacklist.o
      CERT    certs/x509_revocation_list
      AS      certs/revocation_certificates.o
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit c537e4d04eb75274bf03e6a2a8d6ece25d9d16f6
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Tue Dec 14 11:53:45 2021 +0900

    certs: use $< and $@ to simplify the key generation rule
    
    Do not repeat $(obj)/x509.genkey or $(obj)/signing_key.pem
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nicolas Schier <n.schier@avm.de>

commit 4fbce819337a6705559788ff7e9583a4703edcb7
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Dec 6 11:35:07 2021 +0900

    kbuild: remove headers_check stub
    
    Linux 5.15 is out. Remove this stub now.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>

commit 50a483405c420f5f35b8dbb71425459835ae44eb
Author: Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon Dec 6 11:35:06 2021 +0900

    kbuild: move headers_check.pl to usr/include/
    
    This script is only used by usr/include/Makefile. Make it local to
    the directory.
    
    Update the comment in include/uapi/linux/soundcard.h because
    'make headers_check' is no longer functional.
    
    Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

commit 3e4518035a23e02ef818ea22570868a82956c6b0
Author: Takashi Iwai <tiwai@suse.de>
Date:   Fri Jan 7 10:26:47 2022 +0100

    ALSA: hda: Fix dependency on ASoC cs35l41 codec
    
    The recently added support for CS35L41 codec unconditionally selects
    CONFIG_SND_SOC_CS35L41_LIB, but this can't work unless the top-level
    CONFIG_SND_SOC is enabled.  This patch adds the proper dependency.
    
    Fixes: 7b2f3eb492da ("ALSA: hda: cs35l41: Add support for CS35L41 in HDA systems")
    Link: https://lore.kernel.org/r/20220107092647.20258-1-tiwai@suse.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 6b24ca4a1a8d4ee3221d6d44ddbb99f542e4bda3
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Sat Jun 27 22:19:08 2020 -0400

    mm: Use multi-index entries in the page cache
    
    We currently store large folios as 2^N consecutive entries.  While this
    consumes rather more memory than necessary, it also turns out to be buggy.
    A writeback operation which starts within a tail page of a dirty folio will
    not write back the folio as the xarray's dirty bit is only set on the
    head index.  With multi-index entries, the dirty bit will be found no
    matter where in the folio the operation starts.
    
    This does end up simplifying the page cache slightly, although not as
    much as I had hoped.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 25a8de7f8d970ffa7263bd9d32a08138cd949f17
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Aug 27 07:21:49 2021 -0400

    XArray: Add xas_advance()
    
    Add a new helper function to help iterate over multi-index entries.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit b9a8a4195c7d3a51235a4fc974a46ad4e9689ffd
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Wed May 27 17:59:22 2020 -0400

    truncate,shmem: Handle truncates that split large folios
    
    Handle folio splitting in the parts of the truncation functions which
    already handle partial pages.  Factor all that code out into a new
    function called truncate_inode_partial_folio().
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit f6357c3a9d3ea5a00c5bf52845b633d649da6722
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Thu May 20 08:17:44 2021 -0400

    truncate: Convert invalidate_inode_pages2_range to folios
    
    If we're going to unmap a folio, we have to be sure to unmap the entire
    folio, not just the part of it which lies after the search index.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 338f379cf7c21e3bc31186f303ac99dc5d2cc613
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Mon Dec 14 07:57:07 2020 -0500

    fs: Convert vfs_dedupe_file_range_compare to folios
    
    We still only operate on a single page of data at a time due to using
    kmap().  A more complex implementation would work on each page in a folio,
    but it's not clear that such a complex implementation would be worthwhile.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 1613fac9aaf840af76faa747ea428a714af98dbd
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Tue Dec 7 14:28:49 2021 -0500

    mm: Remove pagevec_remove_exceptionals()
    
    All of its callers now call folio_batch_remove_exceptionals().
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 51dcbdac28d4dde915f78adf08bb3fac87f516e9
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Tue Dec 7 14:15:07 2021 -0500

    mm: Convert find_lock_entries() to use a folio_batch
    
    find_lock_entries() already only returned the head page of folios, so
    convert it to return a folio_batch instead of a pagevec.  That cascades
    through converting truncate_inode_pages_range() to
    delete_from_page_cache_batch() and page_cache_delete_batch().
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 0e499ed3d7a216706e02eeded562627d3e69dcfd
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Tue Sep 1 23:17:50 2020 -0400

    filemap: Return only folios from find_get_entries()
    
    The callers have all been converted to work on folios, so convert
    find_get_entries() to return a batch of folios instead of pages.
    We also now return multiple large folios in a single call.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Jan Kara <jack@suse.cz>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>

commit 25d6a23e8d280861dfe81193e18143afb2c0d777
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Mon Dec 6 15:25:33 2021 -0500

    filemap: Convert filemap_get_read_batch() to use a folio_batch
    
    This change ripples all the way through the filemap_read() call chain and
    removes a lot of messing about converting folios to pages and back again.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit d996fc7f615feb5986f67829e18a8d8400f41361
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Sun Oct 31 22:22:19 2021 -0400

    filemap: Convert filemap_read() to use a folio
    
    We know the pagevec always contains folios, but use page_folio() anyway
    instead of casting.  Removes a few calls to legacy functions.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 78f426608f21c997975adb96641b7ac82d4d15b1
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Wed Jul 28 15:52:34 2021 -0400

    truncate: Add invalidate_complete_folio2()
    
    Convert invalidate_complete_page2() to invalidate_complete_folio2().
    Use filemap_free_folio() to free the page instead of calling ->freepage
    manually.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit fae9bc4a90176868cbbbecc693acb0ff2607818d
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Thu Dec 2 23:25:01 2021 -0500

    truncate: Convert invalidate_inode_pages2_range() to use a folio
    
    If we're going to unmap a folio, we have to be sure to unmap the entire
    folio, not just the part of it which lies after the search index.
    
    We cannot yet remove the struct page from invalidate_inode_pages2_range()
    because the page pointer in the pvec might be a shadow/dax/swap entry
    instead of actually a page.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit ccbbf761d440b0d5afcbf232db37435dc38d6161
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Nov 26 13:25:38 2021 -0500

    truncate: Skip known-truncated indices
    
    If we've truncated an entire folio, we can skip over all the indices
    covered by this folio.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 1e84a3d997b74c33491899e31d48774f252213ab
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Thu Dec 2 16:01:55 2021 -0500

    truncate,shmem: Add truncate_inode_folio()
    
    Convert all callers of truncate_inode_page() to call
    truncate_inode_folio() instead, and move the declaration to mm/internal.h.
    Move the assertion that the caller is not passing in a tail page to
    generic_error_remove_page().  We can't entirely remove the struct page
    from the callers yet because the page pointer in the pvec might be a
    shadow/dax/swap entry instead of actually a page.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 7b774aab7941e195d3130caa856da6904333988b
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Fri Dec 3 08:50:01 2021 -0500

    shmem: Convert part of shmem_undo_range() to use a folio
    
    find_lock_entries() never returns tail pages.  We cannot use page_folio()
    here as the pagevec may also contain swap entries, so simply cast for
    now.  This is an intermediate step which will be fully removed by the
    end of this series.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 3506659e18a61ae525f3b9b4f5af23b4b149d4db
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Sun Nov 28 14:53:35 2021 -0500

    mm: Add unmap_mapping_folio()
    
    Convert both callers of unmap_mapping_page() to call unmap_mapping_folio()
    instead.  Also move zap_details from linux/mm.h to mm/memory.c
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Reviewed-by: William Kucharski <william.kucharski@oracle.com>

commit 6dc701ee9fabfc929cae2d7acc957bf38e4c3264
Author: Sven Peter <sven@svenpeter.dev>
Date:   Sat Dec 11 13:36:32 2021 +0100

    MAINTAINERS: Add Apple watchdog to ARM/APPLE MACHINE SUPPORT
    
    Add apple_wdt.c under the ARM/APPLE MACHINE SUPPORT entry.
    
    Signed-off-by: Sven Peter <sven@svenpeter.dev>
    Signed-off-by: Hector Martin <marcan@marcan.st>

commit 82192cb497f9eca6c0d44dbc173e68d59ea2f3c9
Merge: bf44077c1b3ae 9fe890cc5bb84
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 7 19:25:57 2022 -0800

    Merge branch 'ena-capabilities-field-and-cosmetic-changes'
    
    Arthur Kiyanovski says:
    
    ====================
    ENA: capabilities field and cosmetic changes
    
    Add a new capabilities bitmask field to get indication of
    capabilities supported by the device. Use the capabilities
    field to query the device for ENI stats support.
    
    Other patches are cosmetic changes like fixing readme
    mistakes, removing unused variables etc...
    ====================
    
    Link: https://lore.kernel.org/r/20220107202346.3522-1-akiyano@amazon.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9fe890cc5bb84d6859d9a2422830b7fd6fd20521
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:46 2022 +0000

    net: ena: Extract recurring driver reset code into a function
    
    Create an inline function for resetting the driver
    to reduce code duplication.
    
    Signed-off-by: Nati Koler <nkoler@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d0e8831d6c93b030bc757b89aec4dc304d6e55b6
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:45 2022 +0000

    net: ena: Change the name of bad_csum variable
    
    Changed bad_csum to csum_bad to align with csum_unchecked & csum_good
    
    Signed-off-by: Nati Koler <nkoler@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 9b648bb1d89ef058196cff4fe3bd678ab7ebdb19
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:44 2022 +0000

    net: ena: Add debug prints for invalid req_id resets
    
    Add qid and req_id to error prints when ENA_REGS_RESET_INV_TX_REQ_ID
    reset occurs.
    
    Switch from %hu to %u, since u16 should be printed with %u, as
    explained in [1].
    
    [1] - https://www.kernel.org/doc/html/latest/core-api/printk-formats.html
    
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c215941abacff64b686004731d42e68dcda5b8d8
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:43 2022 +0000

    net: ena: Remove ena_calc_queue_size_ctx struct
    
    This struct was used to pass data from callee function to its caller.
    Its usage can be avoided.
    
    Removing it results in less code without any damage to code readability.
    Also it allows to consolidate ring size calculation into a single
    function (ena_calc_io_queue_size()).
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit e3445469803387ce4940fdb30081498104c57abf
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:42 2022 +0000

    net: ena: Move reset completion print to the reset function
    
    The print that indicates that device reset has finished is
    currently called from ena_restore_device().
    
    Move it to ena_fw_reset_device() as it is the more natural
    location for it.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 09f8676eae1d20f840c418503001d29d1ecaa584
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:41 2022 +0000

    net: ena: Remove redundant return code check
    
    The ena_com_indirect_table_fill_entry() function only returns -EINVAL
    or 0, no need to check for -EOPNOTSUPP.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 273a2397fc9157c04e904b6ae37f723aa910a0d1
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:40 2022 +0000

    net: ena: Update LLQ header length in ena documentation
    
    LLQ entry length is 128 bytes. Therefore the maximum header in
    the entry is calculated by:
    tx_max_header_size =
    LLQ_ENTRY_SIZE - DESCRIPTORS_NUM_BEFORE_HEADER * 16 =
    128 - 2 * 16 = 96
    
    This patch updates the documentation so that it states the correct
    max header length.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 394c48e08bbcbf4c235cd667adb8a826a49d3fd4
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:39 2022 +0000

    net: ena: Change ENI stats support check to use capabilities field
    
    Use the capabilities field to query the device for ENI stats
    support.
    
    This replaces the previous method that tried to get the ENI stats
    during ena_probe() and used the success or failure as an indication
    for support by the device.
    
    Remove eni_stats_supported field from struct ena_adapter. This field
    was used for the previous method of queriying for ENI stats support.
    
    Change the severity level of the print in case of
    ena_com_get_eni_stats() failure from info to error.
    With the previous method of querying form ENI stats support, failure
    to get ENI stats was normal for devices that don't support it.
    With the use of the capabilities field such a failure is unexpected,
    as it is called only if the device reported that it supports ENI
    stats.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a2d5d6a70fa5211e071747876fa6a7621c7257fd
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:38 2022 +0000

    net: ena: Add capabilities field with support for ENI stats capability
    
    This bitmask field indicates what capabilities are supported by the
    device.
    
    The capabilities field differs from the 'supported_features' field which
    indicates what sub-commands for the set/get feature commands are
    supported. The sub-commands are specified in the 'feature_id' field of
    the 'ena_admin_set_feat_cmd' struct in the following way:
    
            struct ena_admin_set_feat_cmd cmd;
    
            cmd.aq_common_descriptor.opcode = ENA_ADMIN_SET_FEATURE;
            cmd.feat_common.feature_
    
    The 'capabilities' field, on the other hand, specifies different
    capabilities of the device. For example, whether the device supports
    querying of ENI stats.
    
    Also add an enumerator which contains all the capabilities. The
    first added capability macro is for ENI stats feature.
    
    Capabilities are queried along with the other device attributes (in
    ena_com_get_dev_attr_feat()) during device initialization and are stored
    in the ena_com_dev struct. They can be later queried using the
    ena_com_get_cap() helper function.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 7dcf922152278a54acad15ce0b7864dc6baafd12
Author: Arthur Kiyanovski <akiyano@amazon.com>
Date:   Fri Jan 7 20:23:37 2022 +0000

    net: ena: Change return value of ena_calc_io_queue_size() to void
    
    ena_calc_io_queue_size() always returns 0, therefore make it a
    void function and update the calling function to stop checking
    the return value.
    
    Signed-off-by: Shay Agroskin <shayagr@amazon.com>
    Signed-off-by: Arthur Kiyanovski <akiyano@amazon.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bf44077c1b3ae86668bce02d9466e7134a6569ec
Author: Eric Dumazet <edumazet@google.com>
Date:   Fri Jan 7 10:39:53 2022 -0800

    af_packet: fix tracking issues in packet_do_bind()
    
    It appears that my changes in packet_do_bind() were
    slightly wrong.
    
    syzbot found that calling bind() twice would trigger
    a false positive.
    
    Remove proto_curr/dev_curr variables and rewrite things
    to be less confusing (like not having to use netdev_tracker_alloc(),
    and instead use the standard dev_hold_track())
    
    Fixes: f1d9268e0618 ("net: add net device refcount tracker to struct packet_type")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Link: https://lore.kernel.org/r/20220107183953.3886647-1-eric.dumazet@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6dc9a23e29061e50c36523270de60039ccf536fa
Author: Sunil Goutham <sgoutham@marvell.com>
Date:   Fri Jan 7 12:25:05 2022 +0530

    octeontx2-af: Fix interrupt name strings
    
    Fixed interrupt name string logic which currently results
    in wrong memory location being accessed while dumping
    /proc/interrupts.
    
    Fixes: 4826090719d4 ("octeontx2-af: Enable CPT HW interrupts")
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Link: https://lore.kernel.org/r/1641538505-28367-1-git-send-email-sbhatta@marvell.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d8caa2ed47de0e55828a3bd0a81bbb81aa9e7e11
Merge: 5cad43a52ee3c 8401e87f5a36d
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 7 19:00:46 2022 -0800

    Merge branch 'mptcp-refactoring-for-one-selftest-and-csum-validation'
    
    Mat Martineau says:
    
    ====================
    mptcp: Refactoring for one selftest and csum validation
    
    Patch 1 changes the MPTCP join self tests to depend more on events
    rather than delays, so the script runs faster and has more consistent
    results.
    
    Patches 2 and 3 get rid of some duplicate code in MPTCP's checksum
    validation by modifying and leveraging an existing helper function.
    ====================
    
    Link: https://lore.kernel.org/r/20220107192524.445137-1-mathew.j.martineau@linux.intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8401e87f5a36d370cbf1e9d4ba602a553ce9324a
Author: Geliang Tang <geliang.tang@suse.com>
Date:   Fri Jan 7 11:25:24 2022 -0800

    mptcp: reuse __mptcp_make_csum in validate_data_csum
    
    This patch reused __mptcp_make_csum() in validate_data_csum() instead of
    open-coding.
    
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit c312ee219100e86143a1d3cc10b367bc43a0e0b8
Author: Geliang Tang <geliang.tang@suse.com>
Date:   Fri Jan 7 11:25:23 2022 -0800

    mptcp: change the parameter of __mptcp_make_csum
    
    This patch changed the type of the last parameter of __mptcp_make_csum()
    from __sum16 to __wsum. And export this function in protocol.h.
    
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 327b9a94e2a805dea5238940c9660ca367dbfdef
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Fri Jan 7 11:25:22 2022 -0800

    selftests: mptcp: more stable join tests-cases
    
    MPTCP join self-tests are a bit fragile as they reply on
    delays instead of events to catch-up with the expected
    sockets states.
    
    Replace the delay with state checking where possible and
    reduce the number of sleeps in the most complex scenarios.
    
    This will both reduce the tests run-time and will improve
    stability.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5cad43a52ee3caf451cd645baa4beb53a1733dae
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Fri Jan 7 16:42:29 2022 +0200

    net: dsa: felix: add port fast age support
    
    Add support for flushing the MAC table on a given port in the ocelot
    switch library, and use this functionality in the felix DSA driver.
    
    This operation is needed when a port leaves a bridge to become
    standalone, and when the learning is disabled, and when the STP state
    changes to a state where no FDB entry should be present.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Link: https://lore.kernel.org/r/20220107144229.244584-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a14e6b69f393d651913edcbe4ec0dec27b8b4b40
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Fri Jan 7 18:43:32 2022 +0200

    net: mscc: ocelot: fix incorrect balancing with down LAG ports
    
    Assuming the test setup described here:
    https://patchwork.kernel.org/project/netdevbpf/cover/20210205130240.4072854-1-vladimir.oltean@nxp.com/
    (swp1 and swp2 are in bond0, and bond0 is in a bridge with swp0)
    
    it can be seen that when swp1 goes down (on either board A or B), then
    traffic that should go through that port isn't forwarded anywhere.
    
    A dump of the PGID table shows the following:
    
    PGID_DST[0] = ports 0
    PGID_DST[1] = ports 1
    PGID_DST[2] = ports 2
    PGID_DST[3] = ports 3
    PGID_DST[4] = ports 4
    PGID_DST[5] = ports 5
    PGID_DST[6] = no ports
    PGID_AGGR[0] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[1] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[2] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[3] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[4] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[5] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[6] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[7] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[8] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[9] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[10] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[11] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[12] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[13] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[14] = ports 0, 1, 2, 3, 4, 5
    PGID_AGGR[15] = ports 0, 1, 2, 3, 4, 5
    PGID_SRC[0] = ports 1, 2
    PGID_SRC[1] = ports 0
    PGID_SRC[2] = ports 0
    PGID_SRC[3] = no ports
    PGID_SRC[4] = no ports
    PGID_SRC[5] = no ports
    PGID_SRC[6] = ports 0, 1, 2, 3, 4, 5
    
    Whereas a "good" PGID configuration for that setup should have looked
    like this:
    
    PGID_DST[0] = ports 0
    PGID_DST[1] = ports 1, 2
    PGID_DST[2] = ports 1, 2
    PGID_DST[3] = ports 3
    PGID_DST[4] = ports 4
    PGID_DST[5] = ports 5
    PGID_DST[6] = no ports
    PGID_AGGR[0] = ports 0, 2, 3, 4, 5
    PGID_AGGR[1] = ports 0, 2, 3, 4, 5
    PGID_AGGR[2] = ports 0, 2, 3, 4, 5
    PGID_AGGR[3] = ports 0, 2, 3, 4, 5
    PGID_AGGR[4] = ports 0, 2, 3, 4, 5
    PGID_AGGR[5] = ports 0, 2, 3, 4, 5
    PGID_AGGR[6] = ports 0, 2, 3, 4, 5
    PGID_AGGR[7] = ports 0, 2, 3, 4, 5
    PGID_AGGR[8] = ports 0, 2, 3, 4, 5
    PGID_AGGR[9] = ports 0, 2, 3, 4, 5
    PGID_AGGR[10] = ports 0, 2, 3, 4, 5
    PGID_AGGR[11] = ports 0, 2, 3, 4, 5
    PGID_AGGR[12] = ports 0, 2, 3, 4, 5
    PGID_AGGR[13] = ports 0, 2, 3, 4, 5
    PGID_AGGR[14] = ports 0, 2, 3, 4, 5
    PGID_AGGR[15] = ports 0, 2, 3, 4, 5
    PGID_SRC[0] = ports 1, 2
    PGID_SRC[1] = ports 0
    PGID_SRC[2] = ports 0
    PGID_SRC[3] = no ports
    PGID_SRC[4] = no ports
    PGID_SRC[5] = no ports
    PGID_SRC[6] = ports 0, 1, 2, 3, 4, 5
    
    In other words, in the "bad" configuration, the attempt is to remove the
    inactive swp1 from the destination ports via PGID_DST. But when a MAC
    table entry is learned, it is learned towards PGID_DST 1, because that
    is the logical port id of the LAG itself (it is equal to the lowest
    numbered member port). So when swp1 becomes inactive, if we set
    PGID_DST[1] to contain just swp1 and not swp2, the packet will not have
    any chance to reach the destination via swp2.
    
    The "correct" way to remove swp1 as a destination is via PGID_AGGR
    (remove swp1 from the aggregation port groups for all aggregation
    codes). This means that PGID_DST[1] and PGID_DST[2] must still contain
    both swp1 and swp2. This makes the MAC table still treat packets
    destined towards the single-port LAG as "multicast", and the inactive
    ports are removed via the aggregation code tables.
    
    The change presented here is a design one: the ocelot_get_bond_mask()
    function used to take an "only_active_ports" argument. We don't need
    that. The only call site that specifies only_active_ports=true,
    ocelot_set_aggr_pgids(), must retrieve the entire bonding mask, because
    it must program that into PGID_DST. Additionally, it must also clear the
    inactive ports from the bond mask here, which it can't do if bond_mask
    just contains the active ports:
    
            ac = ocelot_read_rix(ocelot, ANA_PGID_PGID, i);
            ac &= ~bond_mask;  <---- here
            /* Don't do division by zero if there was no active
             * port. Just make all aggregation codes zero.
             */
            if (num_active_ports)
                    ac |= BIT(aggr_idx[i % num_active_ports]);
            ocelot_write_rix(ocelot, ac, ANA_PGID_PGID, i);
    
    So it becomes the responsibility of ocelot_set_aggr_pgids() to take
    ocelot_port->lag_tx_active into consideration when populating the
    aggr_idx array.
    
    Fixes: 23ca3b727ee6 ("net: mscc: ocelot: rebalance LAGs on link up/down events")
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20220107164332.402133-1-vladimir.oltean@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit a5e7d9bbc38eddd19a094191477fbd799c07b90b
Merge: ffef737fd0372 5322c68e588dd
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 7 18:51:46 2022 -0800

    Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue
    
    Tony Nguyen says:
    
    ====================
    40GbE Intel Wired LAN Driver Updates 2022-01-07
    
    This series contains updates to i40e and iavf drivers.
    
    Karen limits per VF MAC filters so that one VF does not consume all
    filters for i40e.
    
    Jedrzej reduces busy wait time for admin queue calls for i40e.
    
    Mateusz updates firmware versions to reflect new supported NVM images
    and renames an error to remove non-inclusive language for i40e.
    
    Yang Li fixes a set but not used warning for i40e.
    
    Jason Wang removes an unneeded variable for iavf.
    
    * '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue:
      iavf: remove an unneeded variable
      i40e: remove variables set but not used
      i40e: Remove non-inclusive language
      i40e: Update FW API version
      i40e: Minimize amount of busy-waiting during AQ send
      i40e: Add ensurance of MacVlan resources for every trusted VF
    ====================
    
    Link: https://lore.kernel.org/r/20220107175704.438387-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit ccd36795be48956248dc308f4525c06c7f419d76
Author: Krzysztof Wilczyński <kw@linux.com>
Date:   Fri Jan 7 22:59:42 2022 +0000

    PCI: Correct misspelled words
    
    Fix a number of misspelled words, and while at it, correct two phrases used
    to indicate a status of an operation where words used have been cleverly
    truncated and thus always trigger a spellchecking error while performing a
    static code analysis over the PCI tree.
    
    [bhelgaas: reverse sense of quirk ternary]
    Link: https://lore.kernel.org/r/20220107225942.121484-1-kw@linux.com
    Signed-off-by: Krzysztof Wilczyński <kw@linux.com>
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

commit ffef737fd0372ca462b5be3e7a592a8929a82752
Author: Gal Pressman <gal@nvidia.com>
Date:   Sun Jan 2 10:12:53 2022 +0200

    net/tls: Fix skb memory leak when running kTLS traffic
    
    The cited Fixes commit introduced a memory leak when running kTLS
    traffic (with/without hardware offloads).
    I'm running nginx on the server side and wrk on the client side and get
    the following:
    
      unreferenced object 0xffff8881935e9b80 (size 224):
      comm "softirq", pid 0, jiffies 4294903611 (age 43.204s)
      hex dump (first 32 bytes):
        80 9b d0 36 81 88 ff ff 00 00 00 00 00 00 00 00  ...6............
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
      backtrace:
        [<00000000efe2a999>] build_skb+0x1f/0x170
        [<00000000ef521785>] mlx5e_skb_from_cqe_mpwrq_linear+0x2bc/0x610 [mlx5_core]
        [<00000000945d0ffe>] mlx5e_handle_rx_cqe_mpwrq+0x264/0x9e0 [mlx5_core]
        [<00000000cb675b06>] mlx5e_poll_rx_cq+0x3ad/0x17a0 [mlx5_core]
        [<0000000018aac6a9>] mlx5e_napi_poll+0x28c/0x1b60 [mlx5_core]
        [<000000001f3369d1>] __napi_poll+0x9f/0x560
        [<00000000cfa11f72>] net_rx_action+0x357/0xa60
        [<000000008653b8d7>] __do_softirq+0x282/0x94e
        [<00000000644923c6>] __irq_exit_rcu+0x11f/0x170
        [<00000000d4085f8f>] irq_exit_rcu+0xa/0x20
        [<00000000d412fef4>] common_interrupt+0x7d/0xa0
        [<00000000bfb0cebc>] asm_common_interrupt+0x1e/0x40
        [<00000000d80d0890>] default_idle+0x53/0x70
        [<00000000f2b9780e>] default_idle_call+0x8c/0xd0
        [<00000000c7659e15>] do_idle+0x394/0x450
    
    I'm not familiar with these areas of the code, but I've added this
    sk_defer_free_flush() to tls_sw_recvmsg() based on a hunch and it
    resolved the issue.
    
    Fixes: f35f821935d8 ("tcp: defer skb freeing after socket lock is released")
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Link: https://lore.kernel.org/r/20220102081253.9123-1-gal@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit bda487ac4bebf871255cc6f23e16f702cea0ca7c
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Mon Oct 25 05:44:10 2021 +0000

    cifs: avoid race during socket reconnect between send and recv
    
    When a TCP connection gets reestablished by the sender in cifs_reconnect,
    There is a chance for race condition with demultiplex thread waiting in
    cifs_readv_from_socket on the old socket. It will now return -ECONNRESET.
    
    This condition is handled by comparing socket pointer before and after
    sock_recvmsg. If the socket pointer has changed, we should not call
    cifs_reconnect again, but instead retry with new socket.
    
    Also fixed another bug in my prev mchan commits.
    We should always reestablish session (even if binding) on a channel
    that needs reconnection.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 73f9bfbe3d818bb52266d5c9f3ba57d97842ffe7
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Mon Jul 19 17:37:52 2021 +0000

    cifs: maintain a state machine for tcp/smb/tcon sessions
    
    If functions like cifs_negotiate_protocol, cifs_setup_session,
    cifs_tree_connect are called in parallel on different channels,
    each of these will be execute the requests. This maybe unnecessary
    in some cases, and only the first caller may need to do the work.
    
    This is achieved by having more states for the tcp/smb/tcon session
    status fields. And tracking the state of reconnection based on the
    state machine.
    
    For example:
    for tcp connections:
    CifsNew/CifsNeedReconnect ->
      CifsNeedNegotiate ->
        CifsInNegotiate ->
          CifsNeedSessSetup ->
            CifsInSessSetup ->
              CifsGood
    
    for smb sessions:
    CifsNew/CifsNeedReconnect ->
      CifsGood
    
    for tcon:
    CifsNew/CifsNeedReconnect ->
      CifsInFilesInvalidate ->
        CifsNeedTcon ->
          CifsInTcon ->
            CifsGood
    
    If any channel reconnect sees that it's in the middle of
    transition to CifsGood, then they can skip the function.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 1913e1116a3174648cf2e6faedf29204f31cc438
Author: Enzo Matsumiya <ematsumiya@suse.de>
Date:   Fri Jan 7 19:51:39 2022 -0300

    cifs: fix hang on cifs_get_next_mid()
    
    Mount will hang if using SMB1 and DFS.
    
    This is because every call to get_next_mid() will, unconditionally,
    mark tcpStatus to CifsNeedReconnect before even establishing the
    initial connect, because "reconnect" variable was not initialized.
    
    Initializing "reconnect" to false fix this issue.
    
    Fixes: 220c5bc25d87 ("cifs: take cifs_tcp_ses_lock for status checks")
    Signed-off-by: Enzo Matsumiya <ematsumiya@suse.de>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 080dc5e5656c1cc1cdefb501b9b645a07519f763
Author: Shyam Prasad N <sprasad@microsoft.com>
Date:   Mon Jul 19 17:05:53 2021 +0000

    cifs: take cifs_tcp_ses_lock for status checks
    
    While checking/updating status for tcp ses, smb ses or tcon,
    we take GlobalMid_Lock. This doesn't make any sense.
    Replaced it with cifs_tcp_ses_lock.
    
    Ideally, we should take a spin lock per struct.
    But since tcp ses, smb ses and tcon objects won't add up to a lot,
    I think there should not be too much contention.
    
    Also, in few other places, these are checked without locking.
    Added locking for these.
    
    Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
    Signed-off-by: Steve French <stfrench@microsoft.com>

commit 4e31bfa37662f72e8e7e3ae46eb5f845a5854229
Author: Nathan Chancellor <nathan@kernel.org>
Date:   Fri Jan 7 11:33:03 2022 -0700

    clk: visconti: Remove pointless NULL check in visconti_pll_add_lookup()
    
    Clang warns:
    
    drivers/clk/visconti/pll.c:292:20: warning: address of array 'ctx->clk_data.hws' will always evaluate to 'true' [-Wpointer-bool-conversion]
            if (ctx->clk_data.hws && id)
                ~~~~~~~~~~~~~~^~~ ~~
    1 warning generated.
    
    This array cannot be NULL if ctx is not NULL, which is allocated in
    visconti_init_pll(), so just remove the check, which matches other clk
    drivers.
    
    Fixes: b4cbe606dc36 ("clk: visconti: Add support common clock driver and reset driver")
    Link: https://github.com/ClangBuiltLinux/linux/issues/1564
    Reported-by: kernel test robot <lkp@intel.com>
    Signed-off-by: Nathan Chancellor <nathan@kernel.org>
    Link: https://lore.kernel.org/r/20220107183303.2337676-1-nathan@kernel.org
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit d062a79b7c80064d5b40bcd78009fe30adde5cea
Author: Nanyong Sun <sunnanyong@huawei.com>
Date:   Tue Nov 23 22:06:38 2021 +0800

    riscv/mm: Enable THP migration
    
    Add two THP helpers required to create PMD migration swap entries,
    and enable THP migration via ARCH_ENABLE_THP_MIGRATION. This can
    reduce time of THP migration without splitting and guarantee the
    migrated pages are still contiguous.
    
    Signed-off-by: Nanyong Sun <sunnanyong@huawei.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit fba88ede6a312705e147860c45ed9b3c3d9c6f85
Author: Nanyong Sun <sunnanyong@huawei.com>
Date:   Tue Nov 23 22:06:37 2021 +0800

    riscv/mm: Adjust PAGE_PROT_NONE to comply with THP semantics
    
    This is a preparation for enabling THP migration.
    As the commit b65399f6111b("arm64/mm: Change THP helpers
    to comply with generic MM semantics") mentioned, pmd_present()
    and pmd_trans_huge() are expected to behave in the following
    manner:
    -------------------------------------------------------------------------
    |       PMD states      |       pmd_present     |       pmd_trans_huge  |
    -------------------------------------------------------------------------
    |       Mapped          |       Yes             |       Yes             |
    -------------------------------------------------------------------------
    |       Splitting       |       Yes             |       Yes             |
    -------------------------------------------------------------------------
    |       Migration/Swap  |       No              |       No              |
    -------------------------------------------------------------------------
    
    At present the PROT_NONE bit reuses the READ bit could not comply with
    above semantics with two problems:
    1. When splitting a PMD THP, PMD is first invalidated with
    pmdp_invalidate()->pmd_mkinvalid(), which clears the PRESENT bit
    and PROT_NONE bit/READ bit, if the PMD is read-only, then the PAGE_LEAF
    property is also cleared, which results in pmd_present() return false.
    2. When migrating, the swap entry only clear the PRESENT bit
    and PROT_NONE bit/READ bit, the W/X bit may be set, so _PAGE_LEAF may be
    true which results in pmd_present() return true.
    
    Solution:
    Adjust PROT_NONE bit from READ to GLOBAL bit can satisfy the above rules:
    1. GLOBAL bit has no other meanings, not like the R/W/X bit, which is
    also relative with _PAGE_LEAF property.
    2. GLOBAL bit is at bit 5, making swap entry start from bit 6, bit 0-5
    are zero, which means the PRESENT, PROT_NONE, and PAGE_LEAF are
    all false, then the pmd_present() and pmd_trans_huge() return false when
    in migration/swap.
    
    Signed-off-by: Nanyong Sun <sunnanyong@huawei.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 104f062fd1b9c8571dba6a3020649da6bbc66259
Author: Zhu Yanjun <yanjun.zhu@linux.dev>
Date:   Thu Jan 6 13:03:59 2022 -0500

    RDMA/rxe: Use the standard method to produce udp source port
    
    Use the standard method to produce udp source port.
    
    Link: https://lore.kernel.org/r/20220106180359.2915060-5-yanjun.zhu@linux.dev
    Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 69e609ba96620aaca3c3bdcbaba5f8dee3b12f5f
Author: Zhu Yanjun <yanjun.zhu@linux.dev>
Date:   Thu Jan 6 13:03:58 2022 -0500

    RDMA/irdma: Make the source udp port vary
    
    Get the source udp port number for a QP based on the grh.flow_label or
    lqpn/rqrpn. This provides a better spread of traffic across NIC RX queues.
    
    Link: https://lore.kernel.org/r/20220106180359.2915060-4-yanjun.zhu@linux.dev
    Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Acked-by: Shiraz Saleem <shiraz.saleem@intel.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 93f8df548187f6aca50d3398a88cf5ebf130525e
Author: Zhu Yanjun <yanjun.zhu@linux.dev>
Date:   Thu Jan 6 13:03:57 2022 -0500

    RDMA/hns: Replace get_udp_sport with rdma_get_udp_sport
    
    Several drivers have the same function xxx_get_udp_sport. So this
    function is moved to ib_verbs.h.
    
    Link: https://lore.kernel.org/r/20220106180359.2915060-3-yanjun.zhu@linux.dev
    Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Acked-by: Wenpeng Liang <liangwenpeng@huawei.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 18451db82ef7f943c60a7fce685f16172bda5106
Author: Zhu Yanjun <yanjun.zhu@linux.dev>
Date:   Thu Jan 6 13:03:56 2022 -0500

    RDMA/core: Calculate UDP source port based on flow label or lqpn/rqpn
    
    Calculate and set UDP source port based on the flow label. If flow label
    is not defined in GRH then calculate it based on lqpn/rqpn.
    
    Link: https://lore.kernel.org/r/20220106180359.2915060-2-yanjun.zhu@linux.dev
    Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
    Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 19e43f1276b38716ad558c2018535e475cb9f3cf
Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Date:   Thu Dec 16 11:19:30 2021 -0500

    drm/amd/display: Add version check before using DP alt query interface
    
    [Why]
    To maintain compatibility with firmware older than 4.0.11.
    
    Those firmware may have interrmittent hangs with RDCSPIPE or the PHY,
    but we shouldn't regress their previous behavior.
    
    [How]
    Use the new path if firmware is development or 4.0.11 or newer. Use the
    legacy path otherwise.
    
    Fixes: 41f91315b5be5a ("drm/amd/display: Query DMCUB for dp alt status")
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Hansen Dsouza <hansen.dsouza@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 214993e106ea84a82e2c644bff3dbbe601b11e04
Author: Mikita Lipski <mikita.lipski@amd.com>
Date:   Wed Dec 15 11:01:45 2021 -0500

    drm/amd/display: introduce mpo detection flags
    
    [why]
    We want to know if new crtc state is enabling MPO configuration before
    enabling it.
    [how]
    Detect if both primary and overlay planes are enabled on the same CRTC.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Mikita Lipski <mikita.lipski@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 46a74381e5ea54dc78ad7c29659dad0b1eb66b0d
Author: Charlene Liu <Charlene.Liu@amd.com>
Date:   Thu Dec 16 16:33:04 2021 -0500

    drm/amd/display: Add check for forced_clocks debug option
    
    [why]
    driver missed the check.
    
    [how]
    add the check.
    add min display clock = 100mhz check based on dccg doc.
    
    [note]
    add SetPhyclkVoltageByFreq as confirmed with smu, but not enabled in
    this change.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Charlene Liu <Charlene.Liu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 79d6b9351f086e0f914a26915d96ab52286ec46c
Author: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Date:   Wed Dec 15 18:18:41 2021 -0500

    drm/amd/display: Don't reinitialize DMCUB on s0ix resume
    
    [Why]
    PSP will suspend and resume DMCUB. Driver should just wait for DMCUB to
    finish the auto load before continuining instead of placing it into
    reset, wiping its firmware state and reinitializing.
    
    If we don't let DMCUB fully finish initializing for S0ix then some state
    will be lost and screen corruption can occur due to incorrect address
    translation.
    
    [How]
    Use dmub_srv callbacks to determine in DMCUB is running and wait for
    auto-load to complete before continuining.
    
    In S0ix DMCUB will be running and DAL fw so initialize will skip.
    
    In S3 DMCUB will not be running and we will do a full hardware init.
    
    In S3 DMCUB will be running but will not be DAL fw so we will also do
    a full hardware init.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Mikita Lipski <Mikita.Lipski@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 580013b2cef8babc204b7b78ff093140e112b194
Author: Wenjing Liu <wenjing.liu@amd.com>
Date:   Mon Dec 13 18:29:27 2021 -0500

    drm/amd/display: unhard code link to phy idx mapping in dc link and clean up
    
    [why]
    1. Current code hard codes link to PHY mapping in dc link level per asic
    per revision.
    This is not scalable. In long term the mapping will be obatined from
    DMUB and store in dc resource.
    
    2. Depending on DCN revision and endpoint type, the definition of
    dio_output_idx dio_output_type and phy_idx are not  consistent. We need
    to unify the meaning of these hardware indices across different system
    configuration.
    
    [how]
    1. Temporarly move the hardcoded mapping to dc_resource level, which
    should have full awareness of asic specific configuration and add a TODO
    comment to move the mapping to DMUB.
    
    2. populate dio_output_idx/phy_idx for all configuration, define
    usb4_enabled bit instead of dio_output_type as an external enum.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Eric Yang <Eric.Yang2@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Wenjing Liu <wenjing.liu@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 771ced73fccd0ac19bb956eaacce3669cfccc805
Author: Yi-Ling Chen <Yi-Ling.Chen2@amd.com>
Date:   Mon Dec 13 16:13:26 2021 +0800

    drm/amd/display: Fix underflow for fused display pipes case
    
    [Why]
    Depend on res_pool->res_cap->num_timing_generator to query timing
    gernerator information, it would case underflow at the fused display
    pipes case.
    Due to the res_pool->res_cap->num_timing_generator records default
    timing generator resource built in driver, not the current chip.
    
    [How]
    Some ASICs would be fused display pipes less than the default setting.
    In dcnxx_resource_construct function, driver would obatin real timing
    generator count and store it into res_pool->timing_generator_count.
    
    Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
    Reviewed-by: Anthony Koo <Anthony.Koo@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Yi-Ling Chen <Yi-Ling.Chen2@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit eac4c54bf7f17fb4681b85e5fe383b74d6261a2b
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Wed Dec 29 13:56:09 2021 -0600

    drm/amdgpu: don't set s3 and s0ix at the same time
    
    This makes it clearer which codepaths are in use specifically in
    one state or the other.
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Acked-by: Evan Quan <evan.quan@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit e53d9665ab003df0ece8f869fcd3c2bbbecf7190
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Wed Dec 29 13:58:02 2021 -0600

    drm/amdgpu: explicitly check for s0ix when evicting resources
    
    This codepath should be running in both s0ix and s3, but only does
    currently because s3 and s0ix are both set in the s0ix case.
    
    Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
    Acked-by: Evan Quan <evan.quan@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit f38b0d48cae88395a05e49cb885fa6ce657e1cc9
Author: Evan Quan <evan.quan@amd.com>
Date:   Thu Dec 30 17:53:54 2021 +0800

    drm/amd/pm: keep the BACO feature enabled for suspend
    
    To pair with the workaround which always reset the ASIC in suspend.
    Otherwise, the reset which relies on BACO will fail.
    
    Fixes: daf8de0874ab5b ("drm/amdgpu: always reset the asic in suspend (v2)")
    
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Reviewed-by: Guchun Chen <guchun.chen@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 216a9873198bdc5c670a9f71d58fafd30227c9c8
Author: James Yao <yiqing.yao@amd.com>
Date:   Wed Dec 29 18:10:32 2021 +0800

    drm/amdgpu: add dummy event6 for vega10
    
    [why]
    Malicious mailbox event1 fails driver loading on vega10.
    A dummy event6 prevent driver from taking response from malicious event1 as its own.
    
    [how]
    On vega10, send a mailbox event6 before sending event1.
    
    Signed-off-by: James Yao <yiqing.yao@amd.com>
    Reviewed-by: Jingwen Chen <Jingwen.Chen2@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit 5b0ce2d41b70bba49b91b10c55984714490354ed
Author: yipechai <YiPeng.Chai@amd.com>
Date:   Wed Dec 29 16:17:28 2021 +0800

    drm/amdkfd: enable sdma ecc interrupt event can be handled by event_interrupt_wq_v9
    
    Enable sdma ecc interrupt event can be handled by event_interrupt_wq_v9.
    
    Signed-off-by: yipechai <YiPeng.Chai@amd.com>
    Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

commit d4296faebd337e5f76c0fddb815de33d2b0ad118
Author: Qi Zheng <zhengqi.arch@bytedance.com>
Date:   Sun Dec 19 10:41:54 2021 +0800

    cpuset: convert 'allowed' in __cpuset_node_allowed() to be boolean
    
    Convert 'allowed' in __cpuset_node_allowed() to be boolean since the
    return types of node_isset() and __cpuset_node_allowed() are both
    boolean.
    
    Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit b56a7cbf40c895cbe8b67ce5649a26b7a7bc48be
Author: Mark Brown <broonie@kernel.org>
Date:   Fri Jan 7 19:11:45 2022 +0000

    regmap: debugfs: Fix indentation
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Link: https://lore.kernel.org/r/20220107191145.813876-1-broonie@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 445ecdf79be0c71ca248f7611aeefceaea3ec59f
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:15 2022 -0800

    kvm: x86: Exclude unpermitted xfeatures at KVM_GET_SUPPORTED_CPUID
    
    KVM_GET_SUPPORTED_CPUID should not include any dynamic xstates in
    CPUID[0xD] if they have not been requested with prctl. Otherwise
    a process which directly passes KVM_GET_SUPPORTED_CPUID to
    KVM_SET_CPUID2 would now fail even if it doesn't intend to use a
    dynamically enabled feature. Userspace must know that prctl is
    required and allocate >4K xstate buffer before setting any dynamic
    bit.
    
    Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-5-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit cc04b6a21d431359eceeec0d812b492088b04af5
Author: Jing Liu <jing2.liu@intel.com>
Date:   Wed Jan 5 04:35:14 2022 -0800

    kvm: x86: Fix xstate_required_size() to follow XSTATE alignment rule
    
    CPUID.0xD.1.EBX enumerates the size of the XSAVE area (in compacted
    format) required by XSAVES. If CPUID.0xD.i.ECX[1] is set for a state
    component (i), this state component should be located on the next
    64-bytes boundary following the preceding state component in the
    compacted layout.
    
    Fix xstate_required_size() to follow the alignment rule. AMX is the
    first state component with 64-bytes alignment to catch this bug.
    
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-4-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 36487e6228c4cb04257c92266a04078a384bc4ec
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 5 04:35:13 2022 -0800

    x86/fpu: Prepare guest FPU for dynamically enabled FPU features
    
    To support dynamically enabled FPU features for guests prepare the guest
    pseudo FPU container to keep track of the currently enabled xfeatures and
    the guest permissions.
    
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-3-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 980fe2fddcff21937c93532b4597c8ea450346c1
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Wed Jan 5 04:35:12 2022 -0800

    x86/fpu: Extend fpu_xstate_prctl() with guest permissions
    
    KVM requires a clear separation of host user space and guest permissions
    for dynamic XSTATE components.
    
    Add a guest permissions member to struct fpu and a separate set of prctl()
    arguments: ARCH_GET_XCOMP_GUEST_PERM and ARCH_REQ_XCOMP_GUEST_PERM.
    
    The semantics are equivalent to the host user space permission control
    except for the following constraints:
    
      1) Permissions have to be requested before the first vCPU is created
    
      2) Permissions are frozen when the first vCPU is created to ensure
         consistency. Any attempt to expand permissions via the prctl() after
         that point is rejected.
    
    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Jing Liu <jing2.liu@intel.com>
    Signed-off-by: Yang Zhong <yang.zhong@intel.com>
    Message-Id: <20220105123532.12586-2-yang.zhong@intel.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 96c1a6285568d31a8125c36974a140fccbe548af
Author: Michael Roth <michael.roth@amd.com>
Date:   Fri Dec 10 10:46:12 2021 -0600

    kvm: selftests: move ucall declarations into ucall_common.h
    
    Now that core kvm_util declarations have special home in
    kvm_util_base.h, move ucall-related declarations out into a separate
    header.
    
    Signed-off-by: Michael Roth <michael.roth@amd.com>
    Message-Id: <20211210164620.11636-3-michael.roth@amd.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 7d9a662ed9f0403e7b94940dceb81552b8edb931
Author: Michael Roth <michael.roth@amd.com>
Date:   Fri Dec 10 10:46:11 2021 -0600

    kvm: selftests: move base kvm_util.h declarations to kvm_util_base.h
    
    Between helper macros and interfaces that will be introduced in
    subsequent patches, much of kvm_util.h would end up being declarations
    specific to ucall. Ideally these could be separated out into a separate
    header since they are not strictly required for writing guest tests and
    are mostly self-contained interfaces other than a reliance on a few
    core declarations like struct kvm_vm. This doesn't make a big
    difference as far as how tests will be compiled/written since all these
    interfaces will still be packaged up into a single/common libkvm.a used
    by all tests, but it is still nice to be able to compartmentalize to
    improve readabilty and reduce merge conflicts in the future for common
    tasks like adding new interfaces to kvm_util.h.
    
    Furthermore, some of the ucall declarations will be arch-specific,
    requiring various #ifdef'ery in kvm_util.h. Ideally these declarations
    could live in separate arch-specific headers, e.g.
    include/<arch>/ucall.h, which would handle arch-specific declarations
    as well as pulling in common ucall-related declarations shared by all
    archs.
    
    One simple way to do this would be to #include ucall.h at the bottom of
    kvm_util.h, after declarations it relies upon like struct kvm_vm.
    This is brittle however, and doesn't scale easily to other sets of
    interfaces that may be added in the future.
    
    Instead, move all declarations currently in kvm_util.h into
    kvm_util_base.h, then have kvm_util.h #include it. With this change,
    non-base declarations can be selectively moved/introduced into separate
    headers, which can then be included in kvm_util.h so that individual
    tests don't need to be touched. Subsequent patches will then move
    ucall-related declarations into a separate header to meet the above
    goals.
    
    Signed-off-by: Michael Roth <michael.roth@amd.com>
    Message-Id: <20211210164620.11636-2-michael.roth@amd.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 8ee304396e2f3db9c2856fb8f63548f906e6f2e1
Author: hasheddan <georgedanielmangum@gmail.com>
Date:   Sat Nov 20 09:26:05 2021 -0500

    riscv/head: fix misspelling of guaranteed
    
    Fixes misspelling of guaranteed in comment describing why fetching fence
    is guaranteed to work when switching to kernel page tables.
    
    Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit 44ea62813f0ab3d718de480504f4dfd0bdd01858
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Sep 3 18:31:40 2021 -0700

    spi: don't include ptp_clock_kernel.h in spi.h
    
    Commit b42faeee718c ("spi: Add a PTP system timestamp
    to the transfer structure") added an include of ptp_clock_kernel.h
    to spi.h for struct ptp_system_timestamp but a forward declaration
    is enough. Let's use that to limit the number of objects we have
    to rebuild every time we touch networking headers.
    
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>
    Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Link: https://lore.kernel.org/r/20210904013140.2377609-1-kuba@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 530792efa6cb86f5612ff093333fec735793b582
Author: Fabio Estevam <festevam@denx.de>
Date:   Fri Jan 7 13:33:07 2022 -0300

    regmap: Call regmap_debugfs_exit() prior to _init()
    
    Since commit cffa4b2122f5 ("regmap: debugfs: Fix a memory leak when
    calling regmap_attach_dev"), the following debugfs error is seen
    on i.MX boards:
    
    debugfs: Directory 'dummy-iomuxc-gpr@20e0000' with parent 'regmap' already present!
    
    In the attempt to fix the memory leak, the above commit added a NULL check
    for map->debugfs_name. For the first debufs entry, map->debugfs_name is NULL
    and then the new name is allocated via kasprintf().
    
    For the second debugfs entry, map->debugfs_name() is no longer NULL, so
    it will keep using the old entry name and the duplicate name error is seen.
    
    Quoting Mark Brown:
    
    "That means that if the device gets freed we'll end up with the old debugfs
    file hanging around pointing at nothing.
    ...
    To be more explicit this means we need a call to regmap_debugfs_exit()
    which will clean up all the existing debugfs stuff before we loose
    references to it."
    
    Call regmap_debugfs_exit() prior to regmap_debugfs_init() to fix
    the problem.
    
    Tested on i.MX6Q and i.MX6SX boards.
    
    Fixes: cffa4b2122f5 ("regmap: debugfs: Fix a memory leak when calling regmap_attach_dev")
    Suggested-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Fabio Estevam <festevam@denx.de>
    Link: https://lore.kernel.org/r/20220107163307.335404-1-festevam@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit f517ba4924ad026f2583553db02f3c8bc69de88b
Author: Charles Keepax <ckeepax@opensource.cirrus.com>
Date:   Fri Jan 7 16:06:36 2022 +0000

    ASoC: cs35l41: Add support for hibernate memory retention mode
    
    The cs35l41 supports a low power DSP memory retention mode. Add support
    for entering this mode when then device is not in use.
    
    Co-authored-by: David Rhodes <david.rhodes@cirrus.com>
    Signed-off-by: David Rhodes <david.rhodes@cirrus.com>
    Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220107160636.6555-3-ckeepax@opensource.cirrus.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit d92321bbe46b0ecae0941461379d39599610d869
Author: Charles Keepax <ckeepax@opensource.cirrus.com>
Date:   Fri Jan 7 16:06:35 2022 +0000

    ASoC: cs35l41: Update handling of test key registers
    
    In preparation for the addition of PM runtime support move the test
    key out of the register patches themselves. This is necessary to
    allow the test key to be held during cache synchronisation, which is
    required by the OTP settings which were unpacked from the device and
    written by the driver.
    
    Also whilst at it, the driver uses a mixture of accessing the test key
    register by name and by address, consistently use the name.
    
    Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
    Link: https://lore.kernel.org/r/20220107160636.6555-2-ckeepax@opensource.cirrus.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 5322c68e588dd018365fe59f9a9930ef11813337
Author: Jason Wang <wangborong@cdjrlc.com>
Date:   Sun Dec 12 16:10:01 2021 +0800

    iavf: remove an unneeded variable
    
    The variable `ret_code' used for returning is never changed in function
    `iavf_shutdown_adminq'. So that it can be removed and just return its
    initial value 0 at the end of `iavf_shutdown_adminq' function.
    
    Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit a127adf2fc836eafffffc43d449ab1a3d20d6f3b
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Mon Dec 13 11:11:07 2021 +0800

    i40e: remove variables set but not used
    
    The code that uses variables pe_cntx_size and pe_filt_size
    has been removed, so they should be removed as well.
    
    Eliminate the following clang warnings:
    drivers/net/ethernet/intel/i40e/i40e_common.c:4139:20:
    warning: variable 'pe_filt_size' set but not used.
    drivers/net/ethernet/intel/i40e/i40e_common.c:4139:6:
    warning: variable 'pe_cntx_size' set but not used.
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 17b33d4319605f1f60d1348a50c49e22666b694b
Author: Mateusz Palczewski <mateusz.palczewski@intel.com>
Date:   Mon Dec 6 11:36:42 2021 +0100

    i40e: Remove non-inclusive language
    
    Remove non-inclusive language from the driver.
    
    Signed-off-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 9c83ca8a638d84a43e8e2631d357865cf8fc5b3a
Author: Mateusz Palczewski <mateusz.palczewski@intel.com>
Date:   Tue Nov 23 15:00:13 2021 +0100

    i40e: Update FW API version
    
    Update FW API versions to the newest supported NVM images.
    
    Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
    Signed-off-by: Mateusz Palczewski <mateusz.palczewski@intel.com>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit ef39584ddb15bddba6b1482dc78cc0633a8f13ef
Author: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Date:   Tue Nov 16 13:13:29 2021 +0000

    i40e: Minimize amount of busy-waiting during AQ send
    
    The i40e_asq_send_command will now use a non blocking usleep_range if
    possible (non-atomic context), instead of busy-waiting udelay. The
    usleep_range function uses hrtimers to provide better performance and
    removes the negative impact of busy-waiting in time-critical
    environments.
    
    1. Rename i40e_asq_send_command to i40e_asq_send_command_atomic
       and add 5th parameter to inform if called from an atomic context.
       Call inside usleep_range (if non-atomic) or udelay (if atomic).
    
    2. Change i40e_asq_send_command to invoke
       i40e_asq_send_command_atomic(..., false).
    
    3. Change two functions:
        - i40e_aq_set_vsi_uc_promisc_on_vlan
        - i40e_aq_set_vsi_mc_promisc_on_vlan
       to explicitly use i40e_asq_send_command_atomic(..., true)
       instead of i40e_asq_send_command, as they use spinlocks and do some
       work in an atomic context.
       All other calls to i40e_asq_send_command remain unchanged.
    
    Signed-off-by: Dawid Lukwinski <dawid.lukwinski@intel.com>
    Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
    Tested-by: Tony Brelinski <tony.brelinski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit cfb1d572c986a39fd288f48a6305d81e6f8d04a3
Author: Karen Sornek <karen.sornek@intel.com>
Date:   Thu Jun 17 09:19:26 2021 +0200

    i40e: Add ensurance of MacVlan resources for every trusted VF
    
    Trusted VF can use up every resource available, leaving nothing
    to other trusted VFs.
    Introduce define, which calculates MacVlan resources available based
    on maximum available MacVlan resources, bare minimum for each VF and
    number of currently allocated VFs.
    
    Signed-off-by: Przemyslaw Patynowski <przemyslawx.patynowski@intel.com>
    Signed-off-by: Karen Sornek <karen.sornek@intel.com>
    Tested-by: Tony Brelinski <tony.brelinski@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 1751fc1db36f6f411709e143d5393f92d12137a9
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Thu Jan 6 18:24:03 2022 -0500

    NFSv4: nfs_atomic_open() can race when looking up a non-regular file
    
    If the file type changes back to being a regular file on the server
    between the failed OPEN and our LOOKUP, then we need to re-run the OPEN.
    
    Fixes: 0dd2b474d0b6 ("nfs: implement i_op->atomic_open()")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit ac795161c93699d600db16c1a8cc23a65a1eceaf
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Thu Jan 6 18:24:02 2022 -0500

    NFSv4: Handle case where the lookup of a directory fails
    
    If the application sets the O_DIRECTORY flag, and tries to open a
    regular file, nfs_atomic_open() will punt to doing a regular lookup.
    If the server then returns a regular file, we will happily return a
    file descriptor with uninitialised open state.
    
    The fix is to return the expected ENOTDIR error in these cases.
    
    Reported-by: Lyu Tao <tao.lyu@epfl.ch>
    Fixes: 0dd2b474d0b6 ("nfs: implement i_op->atomic_open()")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 2056e2989bf47ad7274ecc5e9dda2add53c112f9
Author: Dave Hansen <dave.hansen@linux.intel.com>
Date:   Tue Jan 4 09:15:27 2022 -0800

    x86/sgx: Fix NULL pointer dereference on non-SGX systems
    
    == Problem ==
    
    Nathan Chancellor reported an oops when aceessing the
    'sgx_total_bytes' sysfs file:
    
            https://lore.kernel.org/all/YbzhBrimHGGpddDM@archlinux-ax161/
    
    The sysfs output code accesses the sgx_numa_nodes[] array
    unconditionally.  However, this array is allocated during SGX
    initialization, which only occurs on systems where SGX is
    supported.
    
    If the sysfs file is accessed on systems without SGX support,
    sgx_numa_nodes[] is NULL and an oops occurs.
    
    == Solution ==
    
    To fix this, hide the entire nodeX/x86/ attribute group on
    systems without SGX support using the ->is_visible attribute
    group callback.
    
    Unfortunately, SGX is initialized via a device_initcall() which
    occurs _after_ the ->is_visible() callback.  Instead of moving
    SGX initialization earlier, call sysfs_update_group() during
    SGX initialization to update the group visiblility.
    
    This update requires moving the SGX sysfs code earlier in
    sgx/main.c.  There are no code changes other than the addition of
    arch_update_sysfs_visibility() and a minor whitespace fixup to
    arch_node_attr_is_visible() which checkpatch caught.
    
    CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: linux-sgx@vger.kernel.org
    Cc: x86@kernel.org
    Fixes: 50468e431335 ("x86/sgx: Add an attribute for the amount of SGX memory in a NUMA node")
    Reported-by: Nathan Chancellor <nathan@kernel.org>
    Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
    Tested-by: Nathan Chancellor <nathan@kernel.org>
    Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
    Link: https://lkml.kernel.org/r/20220104171527.5E8416A8@davehans-spike.ostc.intel.com

commit c25af830ab2608ef1dd5e4dada702ce1437ea8e7
Author: Kevin Bracey <kevin@bracey.fi>
Date:   Thu Jan 6 23:56:37 2022 +0200

    sch_cake: revise Diffserv docs
    
    Documentation incorrectly stated that CS1 is equivalent to LE for
    diffserv8. But when LE was added to the table, CS1 was pushed into tin
    1, leaving only LE in tin 0.
    
    Also "TOS1" no longer exists, as that is the same codepoint as LE.
    
    Make other tweaks properly distinguishing codepoints from classes and
    putting current Diffserve codepoints ahead of legacy ones.
    
    Signed-off-by: Kevin Bracey <kevin@bracey.fi>
    Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
    Link: https://lore.kernel.org/r/20220106215637.3132391-1-kevin@bracey.fi
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 87d6576ddf8ac25f36597bc93ca17f6628289c16
Author: Mauro Carvalho Chehab <mchehab@kernel.org>
Date:   Thu Jan 6 01:41:02 2022 +0100

    scripts: sphinx-pre-install: Fix ctex support on Debian
    
    The name of the package with ctexhook.sty is different on
    Debian/Ubuntu.
    
    Reported-by: Akira Yokosawa <akiyks@gmail.com>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
    Tested-by: Akira Yokosawa <akiyks@gmail.com>
    Link: https://lore.kernel.org/r/63882425609a2820fac78f5e94620abeb7ed5f6f.1641429634.git.mchehab@kernel.org
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit db67eb748e7a8e9310accf3eff606b40008ef145
Author: Jonathan Corbet <corbet@lwn.net>
Date:   Mon Jan 3 15:33:47 2022 -0700

    docs: discourage use of list tables
    
    Our documentation encourages the use of list-table formats, but that advice
    runs counter to the objective of keeping the plain-text documentation as
    useful and readable as possible.  Turn that advice around the other way so
    that people don't keep adding these tables.
    
    Acked-by: Christoph Hellwig <hch@lst.de>
    Acked-by: Randy Dunlap <rdunlap@infradead.org>
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit bf33a9d42d0c1003bca4aebfabcd22e69aae979f
Author: Thorsten Leemhuis <linux@leemhuis.info>
Date:   Tue Jan 4 17:53:33 2022 +0100

    docs: 5.Posting.rst: describe Fixes: and Link: tags
    
    Explain Fixes: and Link: tags in Documentation/process/5.Posting.rst,
    which are missing in this file for unknown reasons and only described in
    Documentation/process/submitting-patches.rst.
    
    Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
    CC: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
    Link: https://lore.kernel.org/r/c4a5f5e25fa84b26fd383bba6eafde4ab57c9de7.1641314856.git.linux@leemhuis.info
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 689d8014d92ae9e0a861e82a81d8b4410c0f790e
Author: Christian Löhle <CLoehle@hyperstone.com>
Date:   Wed Jan 5 09:58:38 2022 +0000

    Documentation: kgdb: Replace deprecated remotebaud
    
    Using set remotebaud to set the baud rate was deprecated in
    gdb-7.7 and completely removed from the command parser in gdb-7.8
    (released in 2014). Adopt set serial baud instead.
    
    Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
    Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>
    Link: https://lore.kernel.org/r/4050689967ed46baaa3bfadda53a0e73@hyperstone.com
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 7cc4c09269109d31fc325fb8390e452d7e558de0
Author: James Clark <james.clark@arm.com>
Date:   Wed Jan 5 14:36:39 2022 +0000

    docs: automarkup.py: Fix invalid HTML link output and broken URI fragments
    
    Since commit d18b01789ae5 ("docs: Add automatic cross-reference for
    documentation pages"), references that were already explicitly defined
    with "ref:" and referred to other pages with a path have been doubled.
    This is reported as the following error by Firefox:
    
      Start tag "a" seen but an element of the same type was already open.
      End tag "a" violates nesting rules.
    
    As well as the invalid HTML, this also obscures the URI fragment links
    to subsections because the second link overrides the first. For example
    on the page admin-guide/hw-vuln/mds.html the last link should be to the
    "Default Mitigations" subsection using a # URI fragment:
    
      admin-guide/hw-vuln/l1tf.html#default-mitigations
    
    But it is obsured by a second link to the whole page:
    
      admin-guide/hw-vuln/l1tf.html
    
    The full HTML with the double <a> tags looks like this:
    
      <a class="reference internal" href="l1tf.html#default-mitigations">
        <span class="std std-ref">
          <a class="reference internal" href="l1tf.html">
            <span class="doc">L1TF - L1 Terminal Fault</span>
          </a>
        </span>
      </a>
    
    After this commit, there is only a single link:
    
      <a class="reference internal" href="l1tf.html#default-mitigations">
        <span class="std std-ref">Documentation/admin-guide/hw-vuln//l1tf.rst</span>
      </a>
    
    Now that the second link is removed, the browser correctly jumps to the
    default-mitigations subsection when clicking the link.
    
    The fix is to check that nodes in the document to be modified are not
    already references. A reference is counted as any text that is a
    descendant of a reference type node. Only plain text should be converted
    to new references, otherwise the doubling occurs.
    
    Testing
    =======
    
     * Test that the build stdout is the same (ignoring ordering), and that
       no new warnings are printed.
    
     * Diff all .html files and check that the only modifications occur
       to the bad double links.
    
     * The auto linking of bare references to pages without "ref:" is still
       working.
    
    Fixes: d18b01789ae5 ("docs: Add automatic cross-reference for documentation pages")
    Reviewed-by: Nícolas F. R. A. Prado <n@nfraprado.net>
    Signed-off-by: James Clark <james.clark@arm.com>
    Link: https://lore.kernel.org/r/20220105143640.330602-2-james.clark@arm.com
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>

commit 405329fc9aeef1e3e2eccaadf32b539ad6c7120f
Author: Michael Roth <michael.roth@amd.com>
Date:   Thu Dec 16 11:13:54 2021 -0600

    KVM: SVM: include CR3 in initial VMSA state for SEV-ES guests
    
    Normally guests will set up CR3 themselves, but some guests, such as
    kselftests, and potentially CONFIG_PVH guests, rely on being booted
    with paging enabled and CR3 initialized to a pre-allocated page table.
    
    Currently CR3 updates via KVM_SET_SREGS* are not loaded into the guest
    VMCB until just prior to entering the guest. For SEV-ES/SEV-SNP, this
    is too late, since it will have switched over to using the VMSA page
    prior to that point, with the VMSA CR3 copied from the VMCB initial
    CR3 value: 0.
    
    Address this by sync'ing the CR3 value into the VMCB save area
    immediately when KVM_SET_SREGS* is issued so it will find it's way into
    the initial VMSA.
    
    Suggested-by: Tom Lendacky <thomas.lendacky@amd.com>
    Signed-off-by: Michael Roth <michael.roth@amd.com>
    Message-Id: <20211216171358.61140-10-michael.roth@amd.com>
    [Remove vmx_post_set_cr3; add a remark about kvm_set_cr3 not calling the
     new hook. - Paolo]
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 907d139318b5109e5b676b32b0f4a2c666a8d9ac
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Mon Dec 13 11:07:40 2021 +0100

    KVM: VMX: Provide vmread version using asm-goto-with-outputs
    
    Use asm-goto-output for smaller fast path code.
    
    Message-Id: <YbcbbGW2GcMx6KpD@hirez.programming.kicks-ass.net>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 55749769fe608fa3f4a075e42e89d237c8e37637
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Fri Dec 10 16:36:24 2021 +0000

    KVM: x86: Fix wall clock writes in Xen shared_info not to mark page dirty
    
    When dirty ring logging is enabled, any dirty logging without an active
    vCPU context will cause a kernel oops. But we've already declared that
    the shared_info page doesn't get dirty tracking anyway, since it would
    be kind of insane to mark it dirty every time we deliver an event channel
    interrupt. Userspace is supposed to just assume it's always dirty any
    time a vCPU can run or event channels are routed.
    
    So stop using the generic kvm_write_wall_clock() and just write directly
    through the gfn_to_pfn_cache that we already have set up.
    
    We can make kvm_write_wall_clock() static in x86.c again now, but let's
    not remove the 'sec_hi_ofs' argument even though it's not used yet. At
    some point we *will* want to use that for KVM guests too.
    
    Fixes: 629b5348841a ("KVM: x86/xen: update wallclock region")
    Reported-by: butt3rflyh4ck <butterflyhuangxx@gmail.com>
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211210163625.2886-6-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 14243b387137a4afbe1df5d9dc15182d6657bb79
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Fri Dec 10 16:36:23 2021 +0000

    KVM: x86/xen: Add KVM_IRQ_ROUTING_XEN_EVTCHN and event channel delivery
    
    This adds basic support for delivering 2 level event channels to a guest.
    
    Initially, it only supports delivery via the IRQ routing table, triggered
    by an eventfd. In order to do so, it has a kvm_xen_set_evtchn_fast()
    function which will use the pre-mapped shared_info page if it already
    exists and is still valid, while the slow path through the irqfd_inject
    workqueue will remap the shared_info page if necessary.
    
    It sets the bits in the shared_info page but not the vcpu_info; that is
    deferred to __kvm_xen_has_interrupt() which raises the vector to the
    appropriate vCPU.
    
    Add a 'verbose' mode to xen_shinfo_test while adding test cases for this.
    
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211210163625.2886-5-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 1cfc9c4b9d4606a1e90e7dbc50058b9f0c1d43a6
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Fri Dec 10 16:36:22 2021 +0000

    KVM: x86/xen: Maintain valid mapping of Xen shared_info page
    
    Use the newly reinstated gfn_to_pfn_cache to maintain a kernel mapping
    of the Xen shared_info page so that it can be accessed in atomic context.
    
    Note that we do not participate in dirty tracking for the shared info
    page and we do not explicitly mark it dirty every single tim we deliver
    an event channel interrupts. We wouldn't want to do that even if we *did*
    have a valid vCPU context with which to do so.
    
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211210163625.2886-4-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 982ed0de4753ed6e71dbd40f82a5a066baf133ed
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Fri Dec 10 16:36:21 2021 +0000

    KVM: Reinstate gfn_to_pfn_cache with invalidation support
    
    This can be used in two modes. There is an atomic mode where the cached
    mapping is accessed while holding the rwlock, and a mode where the
    physical address is used by a vCPU in guest mode.
    
    For the latter case, an invalidation will wake the vCPU with the new
    KVM_REQ_GPC_INVALIDATE, and the architecture will need to refresh any
    caches it still needs to access before entering guest mode again.
    
    Only one vCPU can be targeted by the wake requests; it's simple enough
    to make it wake all vCPUs or even a mask but I don't see a use case for
    that additional complexity right now.
    
    Invalidation happens from the invalidate_range_start MMU notifier, which
    needs to be able to sleep in order to wake the vCPU and wait for it.
    
    This means that revalidation potentially needs to "wait" for the MMU
    operation to complete and the invalidate_range_end notifier to be
    invoked. Like the vCPU when it takes a page fault in that period, we
    just spin — fixing that in a future patch by implementing an actual
    *wait* may be another part of shaving this particularly hirsute yak.
    
    As noted in the comments in the function itself, the only case where
    the invalidate_range_start notifier is expected to be called *without*
    being able to sleep is when the OOM reaper is killing the process. In
    that case, we expect the vCPU threads already to have exited, and thus
    there will be nothing to wake, and no reason to wait. So we clear the
    KVM_REQUEST_WAIT bit and send the request anyway, then complain loudly
    if there actually *was* anything to wake up.
    
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211210163625.2886-3-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 2efd61a608b0039911924d2e5d7028eb37496e85
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Fri Dec 10 16:36:20 2021 +0000

    KVM: Warn if mark_page_dirty() is called without an active vCPU
    
    The various kvm_write_guest() and mark_page_dirty() functions must only
    ever be called in the context of an active vCPU, because if dirty ring
    tracking is enabled it may simply oops when kvm_get_running_vcpu()
    returns NULL for the vcpu and then kvm_dirty_ring_get() dereferences it.
    
    This oops was reported by "butt3rflyh4ck" <butterflyhuangxx@gmail.com> in
    https://lore.kernel.org/kvm/CAFcO6XOmoS7EacN_n6v4Txk7xL7iqRa2gABg3F7E3Naf5uG94g@mail.gmail.com/
    
    That actual bug will be fixed under separate cover but this warning
    should help to prevent new ones from being added.
    
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211210163625.2886-2-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit f3f26dae05e39f0f286f588669b54d49b61dcfb8
Author: David Woodhouse <dwmw@amazon.co.uk>
Date:   Thu Dec 9 15:09:38 2021 +0000

    x86/kvm: Silence per-cpu pr_info noise about KVM clocks and steal time
    
    I made the actual CPU bringup go nice and fast... and then Linux spends
    half a minute printing stupid nonsense about clocks and steal time for
    each of 256 vCPUs. Don't do that. Nobody cares.
    
    Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
    Message-Id: <20211209150938.3518-12-dwmw2@infradead.org>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 018d70ffcfec8a01f77b0d840527203d337dd7f9
Author: Eric Hankland <ehankland@google.com>
Date:   Tue Nov 30 15:42:21 2021 +0800

    KVM: x86: Update vPMCs when retiring branch instructions
    
    When KVM retires a guest branch instruction through emulation,
    increment any vPMCs that are configured to monitor "branch
    instructions retired," and update the sample period of those counters
    so that they will overflow at the right time.
    
    Signed-off-by: Eric Hankland <ehankland@google.com>
    [jmattson:
      - Split the code to increment "branch instructions retired" into a
        separate commit.
      - Moved/consolidated the calls to kvm_pmu_trigger_event() in the
        emulation of VMLAUNCH/VMRESUME to accommodate the evolution of
        that code.
    ]
    Fixes: f5132b01386b ("KVM: Expose a version 2 architectural PMU to a guests")
    Signed-off-by: Jim Mattson <jmattson@google.com>
    Message-Id: <20211130074221.93635-7-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 9cd803d496e72cd1dd3287c9a6cb4afa636ee16a
Author: Eric Hankland <ehankland@google.com>
Date:   Tue Nov 30 15:42:20 2021 +0800

    KVM: x86: Update vPMCs when retiring instructions
    
    When KVM retires a guest instruction through emulation, increment any
    vPMCs that are configured to monitor "instructions retired," and
    update the sample period of those counters so that they will overflow
    at the right time.
    
    Signed-off-by: Eric Hankland <ehankland@google.com>
    [jmattson:
      - Split the code to increment "branch instructions retired" into a
        separate commit.
      - Added 'static' to kvm_pmu_incr_counter() definition.
      - Modified kvm_pmu_incr_counter() to check pmc->perf_event->state ==
        PERF_EVENT_STATE_ACTIVE.
    ]
    Fixes: f5132b01386b ("KVM: Expose a version 2 architectural PMU to a guests")
    Signed-off-by: Jim Mattson <jmattson@google.com>
    [likexu:
      - Drop checks for pmc->perf_event or event state or event type
      - Increase a counter once its umask bits and the first 8 select bits are matched
      - Rewrite kvm_pmu_incr_counter() with a less invasive approach to the host perf;
      - Rename kvm_pmu_record_event to kvm_pmu_trigger_event;
      - Add counter enable and CPL check for kvm_pmu_trigger_event();
    ]
    Cc: Peter Zijlstra <peterz@infradead.org>
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20211130074221.93635-6-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 40ccb96d5483c7ef773f50db15f82f0ab587cf8a
Author: Like Xu <likexu@tencent.com>
Date:   Tue Nov 30 15:42:19 2021 +0800

    KVM: x86/pmu: Add pmc->intr to refactor kvm_perf_overflow{_intr}()
    
    Depending on whether intr should be triggered or not, KVM registers
    two different event overflow callbacks in the perf_event context.
    
    The code skeleton of these two functions is very similar, so
    the pmc->intr can be stored into pmc from pmc_reprogram_counter()
    which provides smaller instructions footprint against the
    u-architecture branch predictor.
    
    The __kvm_perf_overflow() can be called in non-nmi contexts
    and a flag is needed to distinguish the caller context and thus
    avoid a check on kvm_is_in_guest(), otherwise we might get
    warnings from suspicious RCU or check_preemption_disabled().
    
    Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20211130074221.93635-5-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6ed1298eb0bf6641b0a66c2c38369f5767a2575c
Author: Like Xu <likexu@tencent.com>
Date:   Tue Nov 30 15:42:18 2021 +0800

    KVM: x86/pmu: Reuse pmc_perf_hw_id() and drop find_fixed_event()
    
    Since we set the same semantic event value for the fixed counter in
    pmc->eventsel, returning the perf_hw_id for the fixed counter via
    find_fixed_event() can be painlessly replaced by pmc_perf_hw_id()
    with the help of pmc_is_fixed() check.
    
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20211130074221.93635-4-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 7c174f305cbee6bdba5018aae02b84369e7ab995
Author: Like Xu <likexu@tencent.com>
Date:   Tue Nov 30 15:42:17 2021 +0800

    KVM: x86/pmu: Refactoring find_arch_event() to pmc_perf_hw_id()
    
    The find_arch_event() returns a "unsigned int" value,
    which is used by the pmc_reprogram_counter() to
    program a PERF_TYPE_HARDWARE type perf_event.
    
    The returned value is actually the kernel defined generic
    perf_hw_id, let's rename it to pmc_perf_hw_id() with simpler
    incoming parameters for better self-explanation.
    
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20211130074221.93635-3-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 761875634a5e2c3fed36c439fc4acac6f85a96eb
Author: Like Xu <likexu@tencent.com>
Date:   Tue Nov 30 15:42:16 2021 +0800

    KVM: x86/pmu: Setup pmc->eventsel for fixed PMCs
    
    The current pmc->eventsel for fixed counter is underutilised. The
    pmc->eventsel can be setup for all known available fixed counters
    since we have mapping between fixed pmc index and
    the intel_arch_events array.
    
    Either gp or fixed counter, it will simplify the later checks for
    consistency between eventsel and perf_hw_id.
    
    Signed-off-by: Like Xu <likexu@tencent.com>
    Message-Id: <20211130074221.93635-2-likexu@tencent.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 006a0f0607e1504950dd8fa3b6ca8e438ec6c9d2
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Thu Dec 9 14:10:04 2021 -0500

    KVM: x86: avoid out of bounds indices for fixed performance counters
    
    Because IceLake has 4 fixed performance counters but KVM only
    supports 3, it is possible for reprogram_fixed_counters to pass
    to reprogram_fixed_counter an index that is out of bounds for the
    fixed_pmc_events array.
    
    Ultimately intel_find_fixed_event, which is the only place that uses
    fixed_pmc_events, handles this correctly because it checks against the
    size of fixed_pmc_events anyway.  Every other place operates on the
    fixed_counters[] array which is sized according to INTEL_PMC_MAX_FIXED.
    However, it is cleaner if the unsupported performance counters are culled
    early on in reprogram_fixed_counters.
    
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 5b61178cd2fd67890a70ae9febbd4df20bbd8c40
Author: Lai Jiangshan <laijs@linux.alibaba.com>
Date:   Thu Dec 16 10:19:38 2021 +0800

    KVM: VMX: Mark VCPU_EXREG_CR3 dirty when !CR0_PG -> CR0_PG if EPT + !URG
    
    When !CR0_PG -> CR0_PG, vcpu->arch.cr3 becomes active, but GUEST_CR3 is
    still vmx->ept_identity_map_addr if EPT + !URG.  So VCPU_EXREG_CR3 is
    considered to be dirty and GUEST_CR3 needs to be updated in this case.
    
    Reported-by: Maxim Levitsky <mlevitsk@redhat.com>
    Suggested-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
    Message-Id: <20211216021938.11752-4-jiangshanlai@gmail.com>
    Fixes: c62c7bd4f95b ("KVM: VMX: Update vmcs.GUEST_CR3 only when the guest CR3 is dirty")
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 6b123c3a89a90ac6418e4d64b1e23f09d458a77d
Author: Lai Jiangshan <laijs@linux.alibaba.com>
Date:   Thu Dec 16 10:19:37 2021 +0800

    KVM: x86/mmu: Reconstruct shadow page root if the guest PDPTEs is changed
    
    For shadow paging, the page table needs to be reconstructed before the
    coming VMENTER if the guest PDPTEs is changed.
    
    But not all paths that call load_pdptrs() will cause the page tables to be
    reconstructed. Normally, kvm_mmu_reset_context() and kvm_mmu_free_roots()
    are used to launch later reconstruction.
    
    The commit d81135a57aa6("KVM: x86: do not reset mmu if CR0.CD and
    CR0.NW are changed") skips kvm_mmu_reset_context() after load_pdptrs()
    when changing CR0.CD and CR0.NW.
    
    The commit 21823fbda552("KVM: x86: Invalidate all PGDs for the current
    PCID on MOV CR3 w/ flush") skips kvm_mmu_free_roots() after
    load_pdptrs() when rewriting the CR3 with the same value.
    
    The commit a91a7c709600("KVM: X86: Don't reset mmu context when
    toggling X86_CR4_PGE") skips kvm_mmu_reset_context() after
    load_pdptrs() when changing CR4.PGE.
    
    Guests like linux would keep the PDPTEs unchanged for every instance of
    pagetable, so this missing reconstruction has no problem for linux
    guests.
    
    Fixes: d81135a57aa6("KVM: x86: do not reset mmu if CR0.CD and CR0.NW are changed")
    Fixes: 21823fbda552("KVM: x86: Invalidate all PGDs for the current PCID on MOV CR3 w/ flush")
    Fixes: a91a7c709600("KVM: X86: Don't reset mmu context when toggling X86_CR4_PGE")
    Suggested-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
    Message-Id: <20211216021938.11752-3-jiangshanlai@gmail.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a9f2705ec84449e3b8d70c804766f8e97e23080d
Author: Lai Jiangshan <laijs@linux.alibaba.com>
Date:   Thu Dec 16 10:19:36 2021 +0800

    KVM: VMX: Save HOST_CR3 in vmx_set_host_fs_gs()
    
    The host CR3 in the vcpu thread can only be changed when scheduling,
    so commit 15ad9762d69f ("KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()")
    changed vmx.c to only save it in vmx_prepare_switch_to_guest().
    
    However, it also has to be synced in vmx_sync_vmcs_host_state() when switching VMCS.
    vmx_set_host_fs_gs() is called in both places, so rename it to
    vmx_set_vmcs_host_state() and make it update HOST_CR3.
    
    Fixes: 15ad9762d69f ("KVM: VMX: Save HOST_CR3 in vmx_prepare_switch_to_guest()")
    Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
    Message-Id: <20211216021938.11752-2-jiangshanlai@gmail.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 46cbc0400f85987954f6e2c110409f8f60725232
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Dec 10 18:13:37 2021 -0500

    Revert "KVM: X86: Update mmu->pdptrs only when it is changed"
    
    This reverts commit 24cd19a28cb7174df502162641d6e1e12e7ffbd9.
    Sean Christopherson reports:
    
    "Commit 24cd19a28cb7 ('KVM: X86: Update mmu->pdptrs only when it is
    changed') breaks nested VMs with EPT in L0 and PAE shadow paging in L2.
    Reproducing is trivial, just disable EPT in L1 and run a VM.  I haven't
    investigating how it breaks things."
    
    Reviewed-by: Sean Christopherson <seanjc@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit a6fec53947cf48e14cc41e2a69dd7d2aa7a00e65
Author: Peter Gonda <pgonda@google.com>
Date:   Wed Dec 8 11:16:42 2021 -0800

    selftests: KVM: sev_migrate_tests: Add mirror command tests
    
    Add tests to confirm mirror vms can only run correct subset of commands.
    
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Sean Christopherson <seanjc@google.com>
    Cc: Marc Orr <marcorr@google.com>
    Signed-off-by: Peter Gonda <pgonda@google.com>
    Message-Id: <20211208191642.3792819-4-pgonda@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 427d046a41bbad295552fa0a7496e15d98eae389
Author: Peter Gonda <pgonda@google.com>
Date:   Wed Dec 8 11:16:41 2021 -0800

    selftests: KVM: sev_migrate_tests: Fix sev_ioctl()
    
    TEST_ASSERT in SEV ioctl was allowing errors because it checked return
    value was good OR the FW error code was OK. This TEST_ASSERT should
    require both (aka. AND) values are OK. Removes the LAUNCH_START from the
    mirror VM because this call correctly fails because mirror VMs cannot
    call this command. Currently issues with the PSP driver functions mean
    the firmware error is not always reset to SEV_RET_SUCCESS when a call is
    successful. Mainly sev_platform_init() doesn't correctly set the fw
    error if the platform has already been initialized.
    
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Sean Christopherson <seanjc@google.com>
    Cc: Marc Orr <marcorr@google.com>
    Signed-off-by: Peter Gonda <pgonda@google.com>
    Message-Id: <20211208191642.3792819-3-pgonda@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 4c66b56781eb114d478d8488e614a4f832a44a2c
Author: Peter Gonda <pgonda@google.com>
Date:   Wed Dec 8 11:16:40 2021 -0800

    selftests: KVM: sev_migrate_tests: Fix test_sev_mirror()
    
    Mirrors should not be able to call LAUNCH_START. Remove the call on the
    mirror to correct the test before fixing sev_ioctl() to correctly assert
    on this failed ioctl.
    
    Cc: Paolo Bonzini <pbonzini@redhat.com>
    Cc: Sean Christopherson <seanjc@google.com>
    Cc: Marc Orr <marcorr@google.com>
    Signed-off-by: Peter Gonda <pgonda@google.com>
    Message-Id: <20211208191642.3792819-2-pgonda@google.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 1b0c9d00aa2cf93dd26760dc9e4cf4725fc5ec03
Merge: 7fd55a02a426f 497685f2c743f
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Jan 7 10:43:02 2022 -0500

    Merge tag 'kvm-riscv-5.17-1' of https://github.com/kvm-riscv/linux into HEAD
    
    KVM/riscv changes for 5.17, take #1
    
    - Use common KVM implementation of MMU memory caches
    - SBI v0.2 support for Guest
    - Initial KVM selftests support
    - Fix to avoid spurious virtual interrupts after clearing hideleg CSR
    - Update email address for Anup and Atish

commit 7fd55a02a426ffff378e0acceff4a381bcbbfca0
Merge: 5e4e84f1124aa 1c53a1ae36120
Author: Paolo Bonzini <pbonzini@redhat.com>
Date:   Fri Jan 7 10:42:19 2022 -0500

    Merge tag 'kvmarm-5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
    
    KVM/arm64 updates for Linux 5.16
    
    - Simplification of the 'vcpu first run' by integrating it into
      KVM's 'pid change' flow
    
    - Refactoring of the FP and SVE state tracking, also leading to
      a simpler state and less shared data between EL1 and EL2 in
      the nVHE case
    
    - Tidy up the header file usage for the nvhe hyp object
    
    - New HYP unsharing mechanism, finally allowing pages to be
      unmapped from the Stage-1 EL2 page-tables
    
    - Various pKVM cleanups around refcounting and sharing
    
    - A couple of vgic fixes for bugs that would trigger once
      the vcpu xarray rework is merged, but not sooner
    
    - Add minimal support for ARMv8.7's PMU extension
    
    - Rework kvm_pgtable initialisation ahead of the NV work
    
    - New selftest for IRQ injection
    
    - Teach selftests about the lack of default IPA space and
      page sizes
    
    - Expand sysreg selftest to deal with Pointer Authentication
    
    - The usual bunch of cleanups and doc update

commit 4d2a3c169b9ad27dfdf2bf8d9362596477840656
Author: Qinghua Jin <qhjin.dev@gmail.com>
Date:   Thu Jan 6 16:27:22 2022 +0800

    IB/qib: Fix typos
    
    Change 'postion' to 'position'.
    
    Link: https://lore.kernel.org/r/20220106082722.354680-1-qhjin.dev@gmail.com
    Signed-off-by: Qinghua Jin <qhjin.dev@gmail.com>
    Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 315d049ad1951cef02d9337a2469cac51cca6932
Author: Kees Cook <keescook@chromium.org>
Date:   Wed Jan 5 09:36:33 2022 -0800

    scsi: megaraid: Avoid mismatched storage type sizes
    
    Remove needless use of mbox_t, replacing with just struct
    mbox_out. Silences compiler warnings under a -Warray-bounds build:
    
    drivers/scsi/megaraid.c: In function 'megaraid_probe_one':
    drivers/scsi/megaraid.c:3615:30: error: array subscript 'mbox_t[0]' is partly outside array bounds of 'unsigned char[15]' [-Werror=array-bounds]
     3615 |         mbox->m_out.xferaddr = (u32)adapter->buf_dma_handle;
          |         ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    drivers/scsi/megaraid.c:3599:23: note: while referencing 'raw_mbox'
     3599 |         unsigned char raw_mbox[sizeof(struct mbox_out)];
          |                       ^~~~~~~~
    
    Link: https://lore.kernel.org/r/20220105173633.2421129-1-keescook@chromium.org
    Cc: Kashyap Desai <kashyap.desai@broadcom.com>
    Cc: Sumit Saxena <sumit.saxena@broadcom.com>
    Cc: Shivasharan S <shivasharan.srikanteshwara@broadcom.com>
    Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
    Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
    Cc: megaraidlinux.pdl@broadcom.com
    Cc: linux-scsi@vger.kernel.org
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit dc35616e6c2907b0c0c391a205802d8880f7fd85
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:12:10 2022 +0300

    netrom: fix api breakage in nr_setsockopt()
    
    This needs to copy an unsigned int from user space instead of a long to
    avoid breaking user space with an API change.
    
    I have updated all the integer overflow checks from ULONG to UINT as
    well.  This is a slight API change but I do not expect it to affect
    anything in real life.
    
    Fixes: 3087a6f36ee0 ("netrom: fix copying in user data in nr_setsockopt")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 9371937092d5fd502032c1bb4475b36b39b1f1b3
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:13:12 2022 +0300

    ax25: uninitialized variable in ax25_setsockopt()
    
    The "opt" variable is unsigned long but we only copy 4 bytes from
    the user so the lower 4 bytes are uninitialized.
    
    I have changed the integer overflow checks from ULONG to UINT as well.
    This is a slight API change but I don't expect it to break anything.
    
    Fixes: a7b75c5a8c41 ("net: pass a sockptr_t into ->setsockopt")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 5d9224fb076e9a2023e0b06d6a164d644612c0c0
Author: Xiang Chen <chenxiang66@hisilicon.com>
Date:   Tue Jan 4 20:42:06 2022 +0800

    scsi: hisi_sas: Remove unused variable and check in hisi_sas_send_ata_reset_each_phy()
    
    In commit 29e2bac87421 ("scsi: hisi_sas: Fix some issues related to
    asd_sas_port->phy_list"), we use asd_sas_port->phy_mask instead of
    accessing asd_sas_port->phy_list, and it is enough to use
    asd_sas_port->phy_mask to check the state of phy, so remove the unused
    check and variable.
    
    Link: https://lore.kernel.org/r/1641300126-53574-1-git-send-email-chenxiang66@hisilicon.com
    Fixes: 29e2bac87421 ("scsi: hisi_sas: Fix some issues related to asd_sas_port->phy_list")
    Reported-by: Nathan Chancellor <nathan@kernel.org>
    Reported-by: Colin King <colin.i.king@gmail.com>
    Acked-by: John Garry <john.garry@huawei.com>
    Signed-off-by: Xiang Chen <chenxiang66@hisilicon.com>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>

commit f3433d79cd50d399f0bec5b784db2aa9f923feb9
Author: Vaishali Thakkar <vaishali.thakkar@ionos.com>
Date:   Wed Jan 5 19:07:08 2022 +0100

    RDMA/rtrs-clt: Rename rtrs_clt to rtrs_clt_sess
    
    Structure rtrs_clt is used for sessions. So to avoid confusions rename it
    to rtrs_clt_sess.
    
    Transformations are done with the help of following coccinelle script.
    
    @@
    @@
    struct
    - rtrs_clt
    + rtrs_clt_sess
    
    Link: https://lore.kernel.org/r/20220105180708.7774-6-jinpu.wang@ionos.com
    Signed-off-by: Vaishali Thakkar <vaishali.thakkar@ionos.com>
    Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit f7ecac6a0927fba05321fd2997d33688ee547f21
Author: Vaishali Thakkar <vaishali.thakkar@ionos.com>
Date:   Wed Jan 5 19:07:07 2022 +0100

    RDMA/rtrs-srv: Rename rtrs_srv to rtrs_srv_sess
    
    Structure rtrs_srv is used for sessions so in order to avoid confusions
    rename it to rtrs_srv_sess.
    
    All changes were done with the help of following Coccinelle script:
    
    @@
    @@
    struct
    - rtrs_srv
    + rtrs_srv_sess
    
    Link: https://lore.kernel.org/r/20220105180708.7774-5-jinpu.wang@ionos.com
    Signed-off-by: Vaishali Thakkar <vaishali.thakkar@ionos.com>
    Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit caa84d95c78f35168847e2ab861a3a7f87033d36
Author: Vaishali Thakkar <vaishali.thakkar@ionos.com>
Date:   Wed Jan 5 19:07:06 2022 +0100

    RDMA/rtrs-clt: Rename rtrs_clt_sess to rtrs_clt_path
    
    rtrs_clt_sess is used for paths and not sessions on the client side. This
    creates confusion so let's rename it to rtrs_clt_path. Also, rename
    related variables and functions.
    
    Coccinelle is used to do the transformations for most of the occurrences
    and remaining ones were handled manually.
    
    Link: https://lore.kernel.org/r/20220105180708.7774-4-jinpu.wang@ionos.com
    Signed-off-by: Vaishali Thakkar <vaishali.thakkar@ionos.com>
    Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit ae4c81644e9105d9f7f713bb0d444737bb6a0cf1
Author: Vaishali Thakkar <vaishali.thakkar@ionos.com>
Date:   Wed Jan 5 19:07:05 2022 +0100

    RDMA/rtrs-srv: Rename rtrs_srv_sess to rtrs_srv_path
    
    rtrs_srv_sess is used for paths and not sessions on the server side. This
    creates confusion so let's rename it to rtrs_srv_path. Also, rename
    related variables and functions.
    
    Coccinelle is used to do the transformations for most of the occurrences
    and remaining ones were handled manually.
    
    Link: https://lore.kernel.org/r/20220105180708.7774-3-jinpu.wang@ionos.com
    Signed-off-by: Vaishali Thakkar <vaishali.thakkar@ionos.com>
    Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit d9372794717f44b6e746d8fbab66763b6d753e71
Author: Vaishali Thakkar <vaishali.thakkar@ionos.com>
Date:   Wed Jan 5 19:07:04 2022 +0100

    RDMA/rtrs: Rename rtrs_sess to rtrs_path
    
    rtrs_sess is in fact a path. This makes it confusing and difficult to get
    into the code. So let's rename the structure and related use cases of it.
    
    Coccinelle was used to do the transformation for most of the occurrences
    and remaining ones were handled manually.
    
    Link: https://lore.kernel.org/r/20220105180708.7774-2-jinpu.wang@ionos.com
    Signed-off-by: Vaishali Thakkar <vaishali.thakkar@ionos.com>
    Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit b69c5b5886f3986f94ded29896211d520c57aea1
Merge: fff63521cd6e1 eabd0f88b0d2d
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 7 14:04:19 2022 +0000

    Merge branch 'octeontx2-ptp-bugs'
    
    Subbaraya Sundeep says:
    
    ====================
    octeontx2: Fix PTP bugs
    
    This patchset addresses two problems found when using
    ptp.
    Patch 1 - Increases the refcount of ptp device before use
    which was missing and it lead to refcount increment after use
    bug when module is loaded and unloaded couple of times.
    Patch 2 - PTP resources allocated by VF are not being freed
    during VF teardown. This patch fixes that.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit eabd0f88b0d2d433c5dfe88218d4ce1c11ef04b8
Author: Rakesh Babu Saladi <rsaladi2@marvell.com>
Date:   Fri Jan 7 12:00:30 2022 +0530

    octeontx2-nicvf: Free VF PTP resources.
    
    When a VF is removed respective PTP resources are not
    being freed currently. This patch fixes it.
    
    Fixes: 43510ef4ddad ("octeontx2-nicvf: Add PTP hardware clock support to NIX VF")
    Signed-off-by: Rakesh Babu Saladi <rsaladi2@marvell.com>
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 93440f4888cf049dbd22b41aaf94d2e2153b3eb8
Author: Subbaraya Sundeep <sbhatta@marvell.com>
Date:   Fri Jan 7 12:00:29 2022 +0530

    octeontx2-af: Increment ptp refcount before use
    
    Before using the ptp pci device by AF driver increment
    the reference count of it.
    
    Fixes: a8b90c9d26d6 ("octeontx2-af: Add PTP device id for CN10K and 95O silcons")
    Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
    Signed-off-by: Sunil Goutham <sgoutham@marvell.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8a3fa72f4b389a17b8bab5ebfb8b660eeb9f9921
Author: Wenpeng Liang <liangwenpeng@huawei.com>
Date:   Fri Dec 31 18:13:41 2021 +0800

    RDMA/hns: Modify the hop num of HIP09 EQ to 1
    
    HIP09 EQ does not support level 2 addressing.
    
    Link: https://lore.kernel.org/r/20211231101341.45759-3-liangwenpeng@huawei.com
    Signed-off-by: Wenpeng Liang <liangwenpeng@huawei.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit 0770bd4187c555e6df087f7abc252eeacb0842ec
Author: David Howells <dhowells@redhat.com>
Date:   Wed Jul 22 10:44:34 2020 +0100

    afs: Skip truncation on the server of data we haven't written yet
    
    Don't send a truncation RPC to the server if we're only shortening data
    that's in the pagecache and is beyond the server's EOF.
    
    Also don't automatically force writeback on setattr, but do wait to store
    RPCs that are in the region to be removed on a shortening truncation.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: kafs-testing@auristor.com
    Acked-by: Jeff Layton <jlayton@kernel.org>
    cc: Marc Dionne <marc.dionne@auristor.com>
    cc: linux-afs@lists.infradead.org
    Link: https://lore.kernel.org/r/163819663275.215744.4781075713714590913.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906972600.143852.14237659724463048094.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967177522.1823006.15336589054269480601.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021571880.640689.1837025861707111004.stgit@warthog.procyon.org.uk/ # v4

commit c7f75ef33b6dcd4269d0f6ee8c50221ee3390733
Author: David Howells <dhowells@redhat.com>
Date:   Thu Feb 6 14:22:30 2020 +0000

    afs: Copy local writes to the cache when writing to the server
    
    When writing to the server from afs_writepage() or afs_writepages(), copy
    the data to the cache object too.
    
    To make this possible, the cookie must have its active users count
    incremented when the page is dirtied and kept incremented until we manage
    to clean up all the pages.  This allows the writeback to take place after
    the last file struct is released.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Tested-by: kafs-testing@auristor.com
    Acked-by: Jeff Layton <jlayton@kernel.org>
    cc: Marc Dionne <marc.dionne@auristor.com>
    cc: linux-afs@lists.infradead.org
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819662333.215744.7531373404219224438.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906970998.143852.674420788614608063.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967176564.1823006.16666056085593949570.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021570208.640689.9193494979708031862.stgit@warthog.procyon.org.uk/ # v4

commit 523d27cda149cfc8c99159c0f68f690e4d3b9d14
Author: David Howells <dhowells@redhat.com>
Date:   Thu Feb 6 14:22:21 2020 +0000

    afs: Convert afs to use the new fscache API
    
    Change the afs filesystem to support the new afs driver.
    
    The following changes have been made:
    
     (1) The fscache_netfs struct is no more, and there's no need to register
         the filesystem as a whole.  There's also no longer a cell cookie.
    
     (2) The volume cookie is now an fscache_volume cookie, allocated with
         fscache_acquire_volume().  This function takes three parameters: a
         string representing the "volume" in the index, a string naming the
         cache to use (or NULL) and a u64 that conveys coherency metadata for
         the volume.
    
         For afs, I've made it render the volume name string as:
    
            "afs,<cell>,<volume_id>"
    
         and the coherency data is currently 0.
    
     (3) The fscache_cookie_def is no more and needed information is passed
         directly to fscache_acquire_cookie().  The cache no longer calls back
         into the filesystem, but rather metadata changes are indicated at
         other times.
    
         fscache_acquire_cookie() is passed the same keying and coherency
         information as before, except that these are now stored in big endian
         form instead of cpu endian.  This makes the cache more copyable.
    
     (4) fscache_use_cookie() and fscache_unuse_cookie() are called when a file
         is opened or closed to prevent a cache file from being culled and to
         keep resources to hand that are needed to do I/O.
    
         fscache_use_cookie() is given an indication if the cache is likely to
         be modified locally (e.g. the file is open for writing).
    
         fscache_unuse_cookie() is given a coherency update if we had the file
         open for writing and will update that.
    
     (5) fscache_invalidate() is now given uptodate auxiliary data and a file
         size.  It can also take a flag to indicate if this was due to a DIO
         write.  This is wrapped into afs_fscache_invalidate() now for
         convenience.
    
     (6) fscache_resize() now gets called from the finalisation of
         afs_setattr(), and afs_setattr() does use/unuse of the cookie around
         the call to support this.
    
     (7) fscache_note_page_release() is called from afs_release_page().
    
     (8) Use a killable wait in nfs_vm_page_mkwrite() when waiting for
         PG_fscache to be cleared.
    
    Render the parts of the cookie key for an afs inode cookie as big endian.
    
    Changes
    =======
    ver #2:
     - Use gfpflags_allow_blocking() rather than using flag directly.
     - fscache_acquire_volume() now returns errors.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Acked-by: Jeff Layton <jlayton@kernel.org>
    Tested-by: kafs-testing@auristor.com
    cc: Marc Dionne <marc.dionne@auristor.com>
    cc: linux-afs@lists.infradead.org
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819661382.215744.1485608824741611837.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906970002.143852.17678518584089878259.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967174665.1823006.1301789965454084220.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021568841.640689.6684240152253400380.stgit@warthog.procyon.org.uk/ # v4

commit 9f08ebc3438baaaefcc79654b330209b83397f17
Author: David Howells <dhowells@redhat.com>
Date:   Fri Oct 22 09:17:58 2021 +0100

    fscache, cachefiles: Display stat of culling events
    
    Add a stat counter of culling events whereby the cache backend culls a file
    to make space (when asked by cachefilesd in this case) and display in
    /proc/fs/fscache/stats.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819654165.215744.3797804661644212436.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906961387.143852.9291157239960289090.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967168266.1823006.14436200166581605746.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021567619.640689.4339228906248763197.stgit@warthog.procyon.org.uk/ # v4

commit 3929eca769b5a231010b4978acc61c0735da198f
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 21:58:29 2021 +0100

    fscache, cachefiles: Display stats of no-space events
    
    Add stat counters of no-space events that caused caching not to happen and
    display in /proc/fs/fscache/stats.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819653216.215744.17210522251617386509.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906958369.143852.7257100711818401748.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967166917.1823006.14842444049198947892.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021566184.640689.4417328329632709265.stgit@warthog.procyon.org.uk/ # v4

commit ecd1a5f62eed35d812de8fe20703e21b551c6560
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 21:04:23 2021 +0000

    cachefiles: Allow cachefiles to actually function
    
    Remove the block that allowed cachefiles to be compiled but prevented it
    from actually starting a cache.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819649497.215744.2872504990762846767.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906956491.143852.4951522864793559189.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967165374.1823006.14248189932202373809.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021564379.640689.7921380491176827442.stgit@warthog.procyon.org.uk/ # v4

commit 32e150037dce368d129996ffe5f98217b1974d9e
Author: David Howells <dhowells@redhat.com>
Date:   Tue Dec 14 09:51:43 2021 +0000

    fscache, cachefiles: Store the volume coherency data
    
    Store the volume coherency data in an xattr and check it when we rebind the
    volume.  If it doesn't match the cache volume is moved to the graveyard and
    rebuilt anew.
    
    Changes
    =======
    ver #4:
     - Remove a couple of debugging prints.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    Link: https://lore.kernel.org/r/163967164397.1823006.2950539849831291830.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021563138.640689.15851092065380543119.stgit@warthog.procyon.org.uk/ # v4

commit 047487c947e8b96b94579c3a33207bd4e266b4c6
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 00:19:46 2021 +0100

    cachefiles: Implement the I/O routines
    
    Implement the I/O routines for cachefiles.  There are two sets of routines
    here: preparation and actual I/O.
    
    Preparation for read involves looking to see whether there is data present,
    and how much.  Netfslib tells us what it wants us to do and we have the
    option of adjusting shrinking and telling it whether to read from the
    cache, download from the server or simply clear a region.
    
    Preparation for write involves checking for space and defending against
    possibly running short of space, if necessary punching out a hole in the
    file so that we don't leave old data in the cache if we update the
    coherency information.
    
    Then there's a read routine and a write routine.  They wait for the cookie
    state to move to something appropriate and then start a potentially
    asynchronous direct I/O operation upon it.
    
    Changes
    =======
    ver #2:
     - Fix a misassigned variable[1].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/YaZOCk9zxApPattb@archlinux-ax161/ [1]
    Link: https://lore.kernel.org/r/163819647945.215744.17827962047487125939.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906954666.143852.1504887120569779407.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967163110.1823006.9206718511874339672.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021562168.640689.8802250542405732391.stgit@warthog.procyon.org.uk/ # v4

commit 7623ed6772de31cadcc474b87bcbc1db84cc1e8e
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:50:10 2021 +0100

    cachefiles: Implement cookie resize for truncate
    
    Implement resizing an object, using truncate and/or fallocate to adjust the
    object.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819646631.215744.13819016478175576761.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906952877.143852.4140962906331914859.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967162168.1823006.5941985259926902274.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021560394.640689.9972155785508094960.stgit@warthog.procyon.org.uk/ # v4

commit 287fd611238dd4b7e32fd3a8985aa387d26c4f29
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 11:05:53 2021 +0100

    cachefiles: Implement begin and end I/O operation
    
    Implement the methods for beginning and ending an I/O operation.
    
    When called to begin an I/O operation, we are guaranteed that the cookie
    has reached a certain stage (we're called by fscache after it has done a
    suitable wait).
    
    If a file is available, we paste a ref over into the cache resources for
    the I/O routines to use.  This means that the object can be invalidated
    whilst the I/O is ongoing without the need to synchronise as the file
    pointer in the object is replaced, but the file pointer in the cache
    resources is unaffected.
    
    Ending the operation just requires ditching any refs we have and dropping
    the access guarantee that fscache got for us on the cookie.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819645033.215744.2199344081658268312.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906951916.143852.9531384743995679857.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967161222.1823006.4461476204800357263.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021559030.640689.3684291785218094142.stgit@warthog.procyon.org.uk/ # v4

commit 1f08c925e7a38002bde509e66f6f891468848511
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:50:10 2021 +0100

    cachefiles: Implement backing file wrangling
    
    Implement the wrangling of backing files, including the following pieces:
    
     (1) Lookup and creation of a file on disk, using a tmpfile if the file
         isn't yet present.  The file is then opened, sized for DIO and the
         file handle is attached to the cachefiles_object struct.  The inode is
         marked to indicate that it's in use by a kernel service.
    
     (2) Invalidation of an object, creating a tmpfile and switching the file
         pointer in the cachefiles object.
    
     (3) Committing a file to disk, including setting the coherency xattr on it
         and, if necessary, creating a hard link to it.
    
         Note that this would be a good place to use Omar Sandoval's vfs_link()
         with AT_LINK_REPLACE[1] as I may have to unlink an old file before I
         can link a tmpfile into place.
    
     (4) Withdrawal of open objects when a cache is being withdrawn or a cookie
         is relinquished.  This involves committing or discarding the file.
    
    Changes
    =======
    ver #2:
     - Fix logging of wrong error[1].
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/20211203094950.GA2480@kili/ [1]
    Link: https://lore.kernel.org/r/163819644097.215744.4505389616742411239.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906949512.143852.14222856795032602080.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967158526.1823006.17482695321424642675.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021557060.640689.16373541458119269871.stgit@warthog.procyon.org.uk/ # v4

commit 07a90e97400c15967c8754fa271ba24d9df71ab5
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:50:10 2021 +0100

    cachefiles: Implement culling daemon commands
    
    Implement the ability for the userspace daemon to try and cull a file or
    directory in the cache.  Two daemon commands are implemented:
    
     (1) The "inuse" command.  This queries if a file is in use or whether it
         can be deleted.  It checks the S_KERNEL_FILE flag on the inode
         referred to by the specified filename.
    
     (2) The "cull" command.  This asks for a file or directory to be removed,
         where removal means either unlinking it or moving it to the graveyard
         directory for userspace to dismantle.
    
    Changes
    =======
    ver #2:
     - Fix logging of wrong error[1].
     - Need to unmark an inode we've moved to the graveyard before unlocking.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/20211203094950.GA2480@kili/ [1]
    Link: https://lore.kernel.org/r/163819643179.215744.13641580295708315695.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906945705.143852.8177595531814485350.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967155792.1823006.1088936326902550910.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021555037.640689.9472627499842585255.stgit@warthog.procyon.org.uk/ # v4

commit 169379eaef933ca98c279257cacb313a02f9984d
Author: David Howells <dhowells@redhat.com>
Date:   Thu Nov 18 08:58:08 2021 +0000

    cachefiles: Mark a backing file in use with an inode flag
    
    Use an inode flag, S_KERNEL_FILE, to mark that a backing file is in use by
    the kernel to prevent cachefiles or other kernel services from interfering
    with that file.
    
    Using S_SWAPFILE instead isn't really viable as that has other effects in
    the I/O paths.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819642273.215744.6414248677118690672.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906943215.143852.16972351425323967014.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967154118.1823006.13227551961786743991.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021541207.640689.564689725898537127.stgit@warthog.procyon.org.uk/ # v4
    Link: https://lore.kernel.org/r/164021552299.640689.10578652796777392062.stgit@warthog.procyon.org.uk/ # v4

commit 72b957856b0c09eee542afcff29705dd0adda654
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 17 16:11:07 2021 +0000

    cachefiles: Implement metadata/coherency data storage in xattrs
    
    Use an xattr on each backing file in the cache to store some metadata, such
    as the content type and the coherency data.
    
    Five content types are defined:
    
     (0) No content stored.
    
     (1) The file contains a single monolithic blob and must be all or nothing.
         This would be used for something like an AFS directory or a symlink.
    
     (2) The file is populated with content completely up to a point with
         nothing beyond that.
    
     (3) The file has a map attached and is sparsely populated.  This would be
         stored in one or more additional xattrs.
    
     (4) The file is dirty, being in the process of local modification and the
         contents are not necessarily represented correctly by the metadata.
         The file should be deleted if this is seen on binding.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819641320.215744.16346770087799536862.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906942248.143852.5423738045012094252.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967151734.1823006.9301249989443622576.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021550471.640689.553853918307994335.stgit@warthog.procyon.org.uk/ # v4

commit 5d439467b802f5c6393b20d57662500dfb177c8f
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 17 15:48:06 2021 +0000

    cachefiles: Implement key to filename encoding
    
    Implement a function to encode a binary cookie key as something that can be
    used as a filename.  Four options are considered:
    
     (1) All printable chars with no '/' characters.  Prepend a 'D' to indicate
         the encoding but otherwise use as-is.
    
     (2) Appears to be an array of __be32.  Encode as 'S' plus a list of
         hex-encoded 32-bit ints separated by commas.  If a number is 0, it is
         rendered as "" instead of "0".
    
     (3) Appears to be an array of __le32.  Encoded as (2) but with a 'T'
         encoding prefix.
    
     (4) Encoded as base64 with an 'E' prefix plus a second char indicating how
         much padding is involved.  A non-standard base64 encoding is used
         because '/' cannot be used in the encoded form.
    
    If (1) is not possible, whichever of (2), (3) or (4) produces the shortest
    string is selected (hex-encoding a number may be less dense than base64
    encoding it).
    
    Note that the prefix characters have to be selected from the set [DEIJST@]
    lest cachefilesd remove the files because it recognise the name.
    
    Changes
    =======
    ver #2:
     - Fix a short allocation that didn't allow for a string terminator[1]
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/bcefb8f2-576a-b3fc-cc29-89808ebfd7c1@linux.alibaba.com/ [1]
    Link: https://lore.kernel.org/r/163819640393.215744.15212364106412961104.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906940529.143852.17352132319136117053.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967149827.1823006.6088580775428487961.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021549223.640689.14762875188193982341.stgit@warthog.procyon.org.uk/ # v4

commit df98e87f2091774c377ddfaedfe64bd90ed4bdca
Author: David Howells <dhowells@redhat.com>
Date:   Wed Nov 17 16:22:21 2021 +0000

    cachefiles: Implement object lifecycle funcs
    
    Implement allocate, get, see and put functions for the cachefiles_object
    struct.  The members of the struct we're going to need are also added.
    
    Additionally, implement a lifecycle tracepoint.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819639457.215744.4600093239395728232.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906939569.143852.3594314410666551982.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967148857.1823006.6332962598220464364.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021547762.640689.8422781599594931000.stgit@warthog.procyon.org.uk/ # v4

commit 13871bad1ef7f41947c816a9e342aa9fa8643c5e
Author: David Howells <dhowells@redhat.com>
Date:   Tue Nov 16 16:30:25 2021 +0000

    cachefiles: Add tracepoints for calls to the VFS
    
    Add tracepoints in cachefiles to monitor when it does various VFS
    operations, such as mkdir.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819638517.215744.12773133137536579766.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906938316.143852.17227990869551737803.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967147139.1823006.4909879317496543392.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021546287.640689.3501604495002415631.stgit@warthog.procyon.org.uk/ # v4

commit fe2140e2f57fef8562e0f9b7cd447d2b08dc2f35
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 09:55:21 2021 +0100

    cachefiles: Implement volume support
    
    Implement support for creating the directory layout for a volume on disk
    and setting up and withdrawing volume caching.
    
    Each volume has a directory named for the volume key under the root of the
    cache (prefixed with an 'I' to indicate to cachefilesd that it's an index)
    and then creates a bunch of hash bucket subdirectories under that (named as
    '@' plus a hex number) in which cookie files will be created.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819635314.215744.13081522301564537723.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906936397.143852.17788457778396467161.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967143860.1823006.7185205806080225038.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021545212.640689.5064821392307582927.stgit@warthog.procyon.org.uk/ # v4

commit d1065b0a6fd9397edd3094c56b777d0d8ec1290d
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 14:29:06 2021 +0000

    cachefiles: Implement cache registration and withdrawal
    
    Do the following:
    
     (1) Fill out cachefiles_daemon_add_cache() so that it sets up the cache
         directories and registers the cache with cachefiles.
    
     (2) Add a function to do the top-level part of cache withdrawal and
         unregistration.
    
     (3) Add a function to sync a cache.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819633175.215744.10857127598041268340.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906935445.143852.15545194974036410029.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967142904.1823006.244055483596047072.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021543872.640689.14370017789605073222.stgit@warthog.procyon.org.uk/ # v4

commit 32759f7d7af5454c616574190c388e1a59184f92
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:34:55 2021 +0100

    cachefiles: Implement a function to get/create a directory in the cache
    
    Implement a function to get/create structural directories in the cache.
    This is used for setting up a cache and creating volume substructures.  The
    directory in memory are marked with the S_KERNEL_FILE inode flag whilst
    they're in use to tell rmdir to reject attempts to remove them.
    
    Changes
    =======
    ver #3:
     - Return an indication as to whether the directory was freshly created.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819631182.215744.3322471539523262619.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906933130.143852.962088616746509062.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967141952.1823006.7832985646370603833.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021542169.640689.18266858945694357839.stgit@warthog.procyon.org.uk/ # v4

commit 1bd9c4e4f0494915b2391f373d25096579f835ff
Author: David Howells <dhowells@redhat.com>
Date:   Thu Nov 18 08:58:08 2021 +0000

    vfs, cachefiles: Mark a backing file in use with an inode flag
    
    Use an inode flag, S_KERNEL_FILE, to mark that a backing file is in use by
    the kernel to prevent cachefiles or other kernel services from interfering
    with that file.
    
    Alter rmdir to reject attempts to remove a directory marked with this flag.
    This is used by cachefiles to prevent cachefilesd from removing them.
    
    Using S_SWAPFILE instead isn't really viable as that has other effects in
    the I/O paths.
    
    Changes
    =======
    ver #3:
     - Check for the object pointer being NULL in the tracepoints rather than
       the caller.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819630256.215744.4815885535039369574.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906931596.143852.8642051223094013028.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967141000.1823006.12920680657559677789.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021541207.640689.564689725898537127.stgit@warthog.procyon.org.uk/ # v4

commit 80f94f29f677d32a1edabc055acfe91c00803592
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:59:46 2021 +0100

    cachefiles: Provide a function to check how much space there is
    
    Provide a function to check how much space there is.  This also flips the
    state on the cache and will signal the daemon to inform it of the change
    and to ask it to do some culling if necessary.
    
    We will also need to subtract the amount of data currently being written to
    the cache (cache->b_writing) from the amount of available space to avoid
    hitting ENOSPC accidentally.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819629322.215744.13457425294680841213.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906930100.143852.1681026700865762069.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967140058.1823006.7781243664702837128.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021539957.640689.12477177372616805706.stgit@warthog.procyon.org.uk/ # v4

commit 8667d434b2a993b34a9dae6f6673bf93870fac25
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 15:12:07 2021 +0000

    cachefiles: Register a miscdev and parse commands over it
    
    Register a misc device with which to talk to the daemon.  The misc device
    holds a cache set up through it around and closing the device kills the
    cache.
    
    cachefilesd communicates with the kernel by passing it single-line text
    commands.  Parse these and use them to parameterise the cache state.  This
    does not implement the command to actually bring a cache online.  That's
    left for later.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819628388.215744.17712097043607299608.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906929128.143852.14065207858943654011.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967139085.1823006.3514846391807454287.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021538400.640689.9172006906288062041.stgit@warthog.procyon.org.uk/ # v4

commit 254947d47945f2fa02e9b3366594fad2ed127618
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 14:59:10 2021 +0000

    cachefiles: Add security derivation
    
    Implement code to derive a new set of creds for the cachefiles to use when
    making VFS or I/O calls and to change the auditing info since the
    application interacting with the network filesystem is not accessing the
    cache directly.  Cachefiles uses override_creds() to change the effective
    creds temporarily.
    
    set_security_override_from_ctx() is called to derive the LSM 'label' that
    the cachefiles driver will act with.  set_create_files_as() is called to
    determine the LSM 'label' that will be applied to files and directories
    created in the cache.  These functions alter the new creds.
    
    Also implement a couple of functions to wrap the calls to begin/end cred
    overriding.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819627469.215744.3603633690679962985.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906928172.143852.15886637013364286786.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967138138.1823006.7620933448261939504.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021537001.640689.4081334436031700558.stgit@warthog.procyon.org.uk/ # v4

commit 1493bf74bcf2434a840eacef60c0f56966faa11a
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 09:08:54 2021 +0100

    cachefiles: Add cache error reporting macro
    
    Add a macro to report a cache I/O error and to tell fscache that the cache
    is in trouble.
    
    Also add a pointer to the fscache cache cookie from the cachefiles_cache
    struct as we need that to pass to fscache_io_error().
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819626562.215744.1503690975344731661.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906927235.143852.13694625647880837563.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967137158.1823006.2065038830569321335.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021536053.640689.5306822604644352548.stgit@warthog.procyon.org.uk/ # v4

commit ecf5a6ce15f90d1fe6bc326c720d21fc0e73fc88
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:42:18 2021 +0100

    cachefiles: Add a couple of tracepoints for logging errors
    
    Add two trace points to log errors, one for vfs operations like mkdir or
    create, and one for I/O operations, like read, write or truncate.
    
    Also add the beginnings of a struct that is going to represent a data file
    and place a debugging ID in it for the tracepoints to record.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819625632.215744.17907340966178411033.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906926297.143852.18267924605548658911.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967135390.1823006.2512120406360156424.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021534029.640689.1875723624947577095.stgit@warthog.procyon.org.uk/ # v4

commit a70f6526267e9f5fbf958a69c6112938b0b14bc4
Author: David Howells <dhowells@redhat.com>
Date:   Thu Oct 21 08:15:26 2021 +0100

    cachefiles: Add some error injection support
    
    Add support for injecting ENOSPC or EIO errors.  This needs to be enabled
    by CONFIG_CACHEFILES_ERROR_INJECTION=y.  Once enabled, ENOSPC on things
    like write and mkdir can be triggered by:
    
            echo 1 >/proc/sys/cachefiles/error_injection
    
    and EIO can be triggered on most operations by:
    
            echo 2 >/proc/sys/cachefiles/error_injection
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819624706.215744.6911916249119962943.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906925343.143852.5465695512984025812.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967134412.1823006.7354285948280296595.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021532340.640689.18209494225772443698.stgit@warthog.procyon.org.uk/ # v4

commit 8390fbc46570dca6f1c7b170f19c612f9ec91a92
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 14:45:38 2021 +0000

    cachefiles: Define structs
    
    Define the cachefiles_cache struct that's going to carry the cache-level
    parameters and state of a cache.
    
    Define the beginning of the cachefiles_object struct that's going to carry
    the state for a data storage object.  For the moment this is just a
    debugging ID for logging purposes.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819623690.215744.2824739137193655547.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906924292.143852.15881439716653984905.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967131405.1823006.4480555941533935597.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021530610.640689.846094074334176928.stgit@warthog.procyon.org.uk/ # v4

commit 77443f6171f32626f24b2f97494c71a6bd83831a
Author: David Howells <dhowells@redhat.com>
Date:   Fri Nov 26 14:32:29 2021 +0000

    cachefiles: Introduce rewritten driver
    
    Introduce basic skeleton of the rewritten cachefiles driver including
    config options so that it can be enabled for compilation.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819622766.215744.9108359326983195047.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906923341.143852.3856498104256721447.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967130320.1823006.15791456613198441566.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021528993.640689.9069695476048171884.stgit@warthog.procyon.org.uk/ # v4

commit 16a96bdf92d5af06f9fa6a01a4b08e2fdfed2e5b
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:06:34 2021 +0100

    fscache: Provide a function to resize a cookie
    
    Provide a function to change the size of the storage attached to a cookie,
    to match the size of the file being cached when it's changed by truncate or
    fallocate:
    
            void fscache_resize_cookie(struct fscache_cookie *cookie,
                                       loff_t new_size);
    
    This acts synchronously and is expected to run under the inode lock of the
    caller.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819621839.215744.7895597119803515402.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906922387.143852.16394459879816147793.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967128998.1823006.10740669081985775576.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021527861.640689.3466382085497236267.stgit@warthog.procyon.org.uk/ # v4

commit 1f67e6d0b18853c641d861a671f46a4964a88510
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:06:34 2021 +0100

    fscache: Provide a function to note the release of a page
    
    Provide a function to be called from a network filesystem's releasepage
    method to indicate that a page has been released that might have been a
    reflection of data upon the server - and now that data must be reloaded
    from the server or the cache.
    
    This is used to end an optimisation for empty files, in particular files
    that have just been created locally, whereby we know there cannot yet be
    any data that we would need to read from the server or the cache.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819617128.215744.4725572296135656508.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906920354.143852.7511819614661372008.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967128061.1823006.611781655060034988.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021525963.640689.9264556596205140044.stgit@warthog.procyon.org.uk/ # v4

commit 69c1b87516e327a60b39f96b778fe683259408bf
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jan 7 07:54:24 2022 +0000

    spi: spi-meson-spifc: Add missing pm_runtime_disable() in meson_spifc_probe
    
    If the probe fails, we should use pm_runtime_disable() to balance
    pm_runtime_enable().
    Add missing pm_runtime_disable() for meson_spifc_probe.
    
    Fixes: c3e4bc5434d2 ("spi: meson: Add support for Amlogic Meson SPIFC")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20220107075424.7774-1-linmq006@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit c8c9cb6d9fbeace1c5509f4bb2f3c32095cda0d0
Author: Qinghua Jin <qhjin.dev@gmail.com>
Date:   Fri Jan 7 10:46:31 2022 +0800

    spi: atmel: Fix typo
    
    Change 'actualy' to 'actually'
    
    Signed-off-by: Qinghua Jin <qhjin.dev@gmail.com>
    Link: https://lore.kernel.org/r/20220107024631.396862-1-qhjin.dev@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit bfff546aae50ae68ed395bf0e0848188d27b0ba3
Author: Watson Chow <watson.chow@avnet.com>
Date:   Fri Jan 7 00:43:50 2022 +0200

    regulator: Add MAX20086-MAX20089 driver
    
    The MAX20086-MAX20089 are dual/quad power protectors for cameras. Add a
    driver that supports controlling the outputs individually. Additional
    features, such as overcurrent detection, may be added later if needed.
    
    Signed-off-by: Watson Chow <watson.chow@avnet.com>
    Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://lore.kernel.org/r/20220106224350.16957-3-laurent.pinchart+renesas@ideasonboard.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 764aaa4e031a9acd26babc622cabe652f57bbb04
Author: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Date:   Fri Jan 7 00:43:49 2022 +0200

    dt-bindings: regulators: Add bindings for Maxim MAX20086-MAX20089
    
    The MAX20086-MAX20089 are dual/quad power protectors for cameras. Add
    corresponding DT bindings.
    
    Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
    Link: https://lore.kernel.org/r/20220106224350.16957-2-laurent.pinchart+renesas@ideasonboard.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 36c86a9e1be3b29f9f075a946df55dfe1d818019
Author: Qu Wenruo <wqu@suse.com>
Date:   Thu Dec 16 19:47:36 2021 +0800

    btrfs: output more debug messages for uncommitted transaction
    
    Print extra information about how many dirty bytes an uncommitted
    has at the end of mount.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c2f822635df873c510bda6fb7fd1b10b7c31be2d
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 16 15:00:32 2021 +0000

    btrfs: respect the max size in the header when activating swap file
    
    If we extended the size of a swapfile after its header was created (by the
    mkswap utility) and then try to activate it, we will map the entire file
    when activating the swap file, instead of limiting to the max size defined
    in the swap file's header.
    
    Currently test case generic/643 from fstests fails because we do not
    respect that size limit defined in the swap file's header.
    
    So fix this by not mapping file ranges beyond the max size defined in the
    swap header.
    
    This is the same type of bug that iomap used to have, and was fixed in
    commit 36ca7943ac18ae ("mm/swap: consider max pages in
    iomap_swapfile_add_extent").
    
    Fixes: ed46ff3d423780 ("Btrfs: support swap files")
    CC: stable@vger.kernel.org # 5.4+
    Reviewed-and-tested-by: Josef Bacik <josef@toxicpanda.com
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit be8d1a2ab98998d369c14c3deb600a31708a66c5
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Mon Dec 20 15:23:06 2021 +0800

    btrfs: fix argument list that the kdoc format and script verified
    
    The warnings were found by running scripts/kernel-doc, which is
    caused by using 'make W=1'.
    
    fs/btrfs/extent_io.c:3210: warning: Function parameter or member
    'bio_ctrl' not described in 'btrfs_bio_add_page'
    fs/btrfs/extent_io.c:3210: warning: Excess function parameter 'bio'
    description in 'btrfs_bio_add_page'
    fs/btrfs/extent_io.c:3210: warning: Excess function parameter
    'prev_bio_flags' description in 'btrfs_bio_add_page'
    fs/btrfs/space-info.c:1602: warning: Excess function parameter 'root'
    description in 'btrfs_reserve_metadata_bytes'
    fs/btrfs/space-info.c:1602: warning: Function parameter or member
    'fs_info' not described in 'btrfs_reserve_metadata_bytes'
    
    Note: this is fixing only the warnings regarding parameter list, the
    first line is not strictly conforming to the kdoc format as the btrfs
    codebase does not stick to that and keeps the first line more free form
    (because it's only for internal use).
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    [ add note ]
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 4a9e803e5b392e2b1e511d0097f6d2c7e6ea41e7
Author: Su Yue <l@damenly.su>
Date:   Mon Dec 27 18:18:39 2021 +0800

    btrfs: remove unnecessary parameter type from compression_decompress_bio
    
    btrfs_decompress_bio, the only caller of compression_decompress_bio gets
    type from @cb and passes it to compression_decompress_bio.
    However, compression_decompress_bio can get compression type directly
    from @cb.
    
    So remove the parameter and access it through @cb.  No functional
    change.
    
    Reviewed-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: Su Yue <l@damenly.su>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 856e47946c6da280816ed9b9c32083c102838ba0
Author: Qu Wenruo <wqu@suse.com>
Date:   Thu Dec 30 16:45:13 2021 +0800

    btrfs: selftests: dump extent io tree if extent-io-tree test failed
    
    When code modifying extent-io-tree get modified and got that selftest
    failed, it can take some time to pin down the cause.
    
    To make it easier to expose the problem, dump the extent io tree if the
    selftest failed.
    
    This can save developers debug time, especially since the selftest we
    can not use the trace events, thus have to manually add debug trace
    points.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 2ae8ae3d3def4c3ba73a58cc2531c42f0916f14e
Author: Qu Wenruo <wqu@suse.com>
Date:   Wed Dec 15 14:59:42 2021 +0800

    btrfs: scrub: cleanup the argument list of scrub_stripe()
    
    The argument list of btrfs_stripe() has similar problems of
    scrub_chunk():
    
    - Duplicated and ambiguous @base argument
      Can be fetched from btrfs_block_group::bg.
    
    - Ambiguous argument @length
      It's again device extent length
    
    - Ambiguous argument @num
      The instinctive guess would be mirror number, but in fact it's stripe
      index.
    
    Fix it by:
    
    - Remove @base parameter
    
    - Rename @length to @dev_extent_len
    
    - Rename @num to @stripe_index
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d04fbe19aefd28570a442e79aae226dd742ddc4c
Author: Qu Wenruo <wqu@suse.com>
Date:   Wed Dec 15 14:59:41 2021 +0800

    btrfs: scrub: cleanup the argument list of scrub_chunk()
    
    The argument list of scrub_chunk() has the following problems:
    
    - Duplicated @chunk_offset
      It is the same as btrfs_block_group::start.
    
    - Confusing @length
      The most instinctive guess is chunk length, and one may want to delete
      it, but the truth is, it's the device extent length.
    
    Fix this by:
    
    - Remove @chunk_offset
      Use btrfs_block_group::start instead.
    
    - Rename @length to @dev_extent_len
      Also rename the caller to remove the ambiguous naming.
    
    - Rename @cache to @bg
      The "_cache" suffix for btrfs_block_group has been removed for a while.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit f26c92386028563a1e988bb277c6c5ce2e8010ee
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Dec 14 21:01:45 2021 +0800

    btrfs: remove reada infrastructure
    
    Currently there is only one user for btrfs metadata readahead, and
    that's scrub.
    
    But even for the single user, it's not providing the correct
    functionality it needs, as scrub needs reada for commit root, which
    current readahead can't provide. (Although it's pretty easy to add such
    feature).
    
    Despite this, there are some extra problems related to metadata
    readahead:
    
    - Duplicated feature with btrfs_path::reada
    
    - Partly duplicated feature of btrfs_fs_info::buffer_radix
      Btrfs already caches its metadata in buffer_radix, while readahead
      tries to read the tree block no matter if it's already cached.
    
    - Poor layer separation
      Metadata readahead works kinda at device level.
      This is definitely not the correct layer it should be, since metadata
      is at btrfs logical address space, it should not bother device at all.
    
      This brings extra chance for bugs to sneak in, while brings
      unnecessary complexity.
    
    - Dead code
      In the very beginning of scrub.c we have #undef DEBUG, rendering all
      the debug related code useless and unable to test.
    
    Thus here I purpose to remove the metadata readahead mechanism
    completely.
    
    [BENCHMARK]
    There is a full benchmark for the scrub performance difference using the
    old btrfs_reada_add() and btrfs_path::reada.
    
    For the worst case (no dirty metadata, slow HDD), there could be a 5%
    performance drop for scrub.
    For other cases (even SATA SSD), there is no distinguishable performance
    difference.
    
    The number is reported scrub speed, in MiB/s.
    The resolution is limited by the reported duration, which only has a
    resolution of 1 second.
    
            Old             New             Diff
    SSD     455.3           466.332         +2.42%
    HDD     103.927         98.012          -5.69%
    
    Comprehensive test methodology is in the cover letter of the patch.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit dcf62b204c06ac22a988c8563b20e479d206befc
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Dec 14 21:01:44 2021 +0800

    btrfs: scrub: use btrfs_path::reada for extent tree readahead
    
    For scrub, we trigger two readaheads for two trees, extent tree to get
    where to scrub, and csum tree to get the data checksum.
    
    For csum tree we already trigger readahead in
    btrfs_lookup_csums_range(), by setting path->reada.
    But for extent tree we don't have any path based readahead.
    
    Add the readahead for extent tree as well, so we can later remove the
    btrfs_reada_add() based readahead.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 2522dbe86b54ff07eb0819a20534c0d33c5414cd
Author: Qu Wenruo <wqu@suse.com>
Date:   Tue Dec 14 21:01:43 2021 +0800

    btrfs: scrub: remove the unnecessary path parameter for scrub_raid56_parity()
    
    In function scrub_stripe() we allocated two btrfs_path's, one @path for
    extent tree search and another @ppath for full stripe extent tree search
    for RAID56.
    
    This is totally umncessary, as the @ppath usage is completely inside
    scrub_raid56_parity(), thus we can move the path allocation into
    scrub_raid56_parity() completely.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c1227996438050ee1a592db40404a088a205e66f
Author: Nikolay Borisov <nborisov@suse.com>
Date:   Tue Dec 14 15:39:39 2021 +0200

    btrfs: refactor unlock_up
    
    The purpose of this function is to unlock all nodes in a btrfs path
    which are above 'lowest_unlock' and whose slot used is different than 0.
    As such it used slightly awkward structure of 'if' as well as somewhat
    cryptic "no_skip" control variable which denotes whether we should
    check the current level of skipability or no.
    
    This patch does the following (cosmetic) refactorings:
    
    * Renames 'no_skip' to 'check_skip' and makes it a boolean. This
      variable controls whether we are below the lowest_unlock/skip_level
      levels.
    
    * Consolidates the 2 conditions which warrant checking whether the
      current level should be skipped under 1 common if (check_skip) branch,
      this increase indentation level but is not critical.
    
    * Consolidates the 'skip_level < i && i >= lowest_unlock' and
      'i >= lowest_unlock && i > skip_level' condition into a common branch
      since those are identical.
    
    * Eliminates the local extent_buffer variable as in this case it doesn't
      bring anything to function readability.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Nikolay Borisov <nborisov@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 1b58ae0e4d3ede95ee968a3f097298a57cf711ba
Author: Filipe Manana <fdmanana@suse.com>
Date:   Mon Dec 13 08:45:14 2021 +0000

    btrfs: skip transaction commit after failure to create subvolume
    
    At ioctl.c:create_subvol(), when we fail to create a subvolume we always
    commit the transaction. In most cases this is a no-op, since all the error
    paths, except for one, abort the transaction - the only exception is when
    we fail to insert the new root item into the root tree, in that case we
    don't abort the transaction because we didn't do anything that is
    irreversible - however we end up committing the transaction which although
    is not a functional problem, it adds unnecessary rotation of the backup
    roots in the superblock and unnecessary work.
    
    So change that to commit a transaction only when no error happened,
    otherwise just call btrfs_end_transaction() to release our reference on
    the transaction.
    
    Reviewed-by: Nikolay Borisov <nborisov@suse.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 82187d2ecdfb22ab7ee05f388402a39236d31428
Author: Naohiro Aota <naohiro.aota@wdc.com>
Date:   Wed Dec 8 00:35:49 2021 +0900

    btrfs: zoned: fix chunk allocation condition for zoned allocator
    
    The ZNS specification defines a limit on the number of "active"
    zones. That limit impose us to limit the number of block groups which
    can be used for an allocation at the same time. Not to exceed the
    limit, we reuse the existing active block groups as much as possible
    when we can't activate any other zones without sacrificing an already
    activated block group in commit a85f05e59bc1 ("btrfs: zoned: avoid
    chunk allocation if active block group has enough space").
    
    However, the check is wrong in two ways. First, it checks the
    condition for every raid index (ffe_ctl->index). Even if it reaches
    the condition and "ffe_ctl->max_extent_size >=
    ffe_ctl->min_alloc_size" is met, there can be other block groups
    having enough space to hold ffe_ctl->num_bytes. (Actually, this won't
    happen in the current zoned code as it only supports SINGLE
    profile. But, it can happen once it enables other RAID types.)
    
    Second, it checks the active zone availability depending on the
    raid index. The raid index is just an index for
    space_info->block_groups, so it has nothing to do with chunk allocation.
    
    These mistakes are causing a faulty allocation in a certain
    situation. Consider we are running zoned btrfs on a device whose
    max_active_zone == 0 (no limit). And, suppose no block group have a
    room to fit ffe_ctl->num_bytes but some room to meet
    ffe_ctl->min_alloc_size (i.e. max_extent_size > num_bytes >=
    min_alloc_size).
    
    In this situation, the following occur:
    
    - With SINGLE raid_index, it reaches the chunk allocation checking
      code
    - The check returns true because we can activate a new zone (no limit)
    - But, before allocating the chunk, it iterates to the next raid index
      (RAID5)
    - Since there are no RAID5 block groups on zoned mode, it again
      reaches the check code
    - The check returns false because of btrfs_can_activate_zone()'s "if
      (raid_index != BTRFS_RAID_SINGLE)" part
    - That results in returning -ENOSPC without allocating a new chunk
    
    As a result, we end up hitting -ENOSPC too early.
    
    Move the check to the right place in the can_allocate_chunk() hook,
    and do the active zone check depending on the allocation flag, not on
    the raid index.
    
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 50475cd57706359d6cc652be88369dace7a4c2eb
Author: Naohiro Aota <naohiro.aota@wdc.com>
Date:   Wed Dec 8 00:35:48 2021 +0900

    btrfs: add extent allocator hook to decide to allocate chunk or not
    
    Introduce a new hook for an extent allocator policy. With the new
    hook, a policy can decide to allocate a new block group or not. If
    not, it will return -ENOSPC, so btrfs_reserve_extent() will cut the
    allocation size in half and retry the allocation if min_alloc_size is
    large enough.
    
    The hook has a place holder and will be replaced with the real
    implementation in the next patch.
    
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 1ada69f61c88abb75a1038ee457633325658a183
Author: Naohiro Aota <naohiro.aota@wdc.com>
Date:   Wed Dec 8 00:35:47 2021 +0900

    btrfs: zoned: unset dedicated block group on allocation failure
    
    Allocating an extent from a block group can fail for various reasons.
    When an allocation from a dedicated block group (for tree-log or
    relocation data) fails, we need to unregister it as a dedicated one so
    that we can allocate a new block group for the dedicated one.
    
    However, we are returning early when the block group in case it is
    read-only, fully used, or not be able to activate the zone. As a result,
    we keep the non-usable block group as a dedicated one, leading to
    further allocation failure. With many block groups, the allocator will
    iterate hopeless loop to find a free extent, results in a hung task.
    
    Fix the issue by delaying the return and doing the proper cleanups.
    
    CC: stable@vger.kernel.org # 5.16
    Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 736727100067267708d221632ffff4083fc0b278
Author: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Date:   Tue Dec 7 06:28:37 2021 -0800

    btrfs: zoned: drop redundant check for REQ_OP_ZONE_APPEND and btrfs_is_zoned
    
    REQ_OP_ZONE_APPEND can only work on zoned devices, so it is redundant to
    check if the filesystem is zoned when REQ_OP_ZONE_APPEND is set as the
    bio's bio_op.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 554aed7da29bcadb3ee3cfdc1376da660d3fc849
Author: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Date:   Tue Dec 7 06:28:36 2021 -0800

    btrfs: zoned: sink zone check into btrfs_repair_one_zone
    
    Sink zone check into btrfs_repair_one_zone() so we don't need to do it
    in all callers.
    
    Also as btrfs_repair_one_zone() doesn't return a sensible error, make it
    a boolean function and return false in case it got called on a non-zoned
    filesystem and true on a zoned filesystem.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 8fdf54fe69a7a0f11542c2dd322b590a5b935918
Author: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Date:   Tue Dec 7 06:28:35 2021 -0800

    btrfs: zoned: simplify btrfs_check_meta_write_pointer
    
    btrfs_check_meta_write_pointer() will always be called with a NULL
    'cache_ret' argument.
    
    As there's no need to check if we have a valid block_group passed in
    remove these checks.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 869f4cdc73f9378986755030c684c011f0b71517
Author: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Date:   Tue Dec 7 06:28:34 2021 -0800

    btrfs: zoned: encapsulate inode locking for zoned relocation
    
    Encapsulate the inode lock needed for serializing the data relocation
    writes on a zoned filesystem into a helper.
    
    This streamlines the code reading flow and hides special casing for
    zoned filesystems.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a26d60dedf9af81df7aeaef66353eb391f85e7a9
Author: Anand Jain <anand.jain@oracle.com>
Date:   Thu Oct 21 23:31:17 2021 +0800

    btrfs: sysfs: add devinfo/fsid to retrieve actual fsid from the device
    
    In the case of the seed device, the fsid can be different from the mounted
    sprout fsid.  The userland has to read the device superblock to know the
    fsid but, that idea fails if the device is missing. So add a sysfs
    interface devinfo/<devid>/fsid to show the fsid of the device.
    
    For example:
      $ cd /sys/fs/btrfs/b10b02a5-f9de-4276-b9e8-2bfd09a578a8
    
      $ cat devinfo/1/fsid
      c44d771f-639d-4df3-99ec-5bc7ad2af93b
      $ cat  devinfo/3/fsid
      b10b02a5-f9de-4276-b9e8-2bfd09a578a8
    
    Though it's related to seeding, the name of the sysfs file is plain fsid as it
    matches what blkid says.  A path to the device's fsid will aid scripting.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Anand Jain <anand.jain@oracle.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c18e3235646a8ba74d013067a6475c8d262d3776
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Thu Dec 2 15:34:32 2021 -0500

    btrfs: reserve extra space for the free space tree
    
    Filipe reported a problem where sometimes he'd get an ENOSPC abort when
    running delayed refs with generic/619 and the free space tree enabled.
    This is partly because we do not reserve space for modifying the free
    space tree, nor do we have a block rsv associated with that tree.
    
    The delayed_refs_rsv tracks the amount of space required to run delayed
    refs.  This means 1 modification means 1 change to the extent root.
    With the free space tree this turns into 2 changes, because modifying 1
    extent means updating the extent tree and potentially updating the free
    space tree to either remove that entry or add the free space.  Thus if
    we have the FST enabled, simply double the reservation size for our
    modification.
    
    Reviewed-by: Nikolay Borisov <nborisov@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 9506f9538206acb9a3c24d1ffbd587733b185732
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Thu Dec 2 15:34:31 2021 -0500

    btrfs: include the free space tree in the global rsv minimum calculation
    
    Filipe reported a problem where generic/619 was failing with an ENOSPC
    abort while running delayed refs, like the following
    
      BTRFS: Transaction aborted (error -28)
      WARNING: CPU: 3 PID: 522920 at fs/btrfs/free-space-tree.c:1049 add_to_free_space_tree+0xe5/0x110 [btrfs]
      CPU: 3 PID: 522920 Comm: kworker/u16:19 Tainted: G        W         5.16.0-rc2-btrfs-next-106 #1
      Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
      Workqueue: events_unbound btrfs_async_reclaim_metadata_space [btrfs]
      RIP: 0010:add_to_free_space_tree+0xe5/0x110 [btrfs]
      RSP: 0000:ffffa65087fb7b20 EFLAGS: 00010282
      RAX: 0000000000000000 RBX: 0000000000001000 RCX: 0000000000000000
      RDX: 0000000000000001 RSI: ffffffff9131eeaa RDI: 00000000ffffffff
      RBP: ffff8d62e26481b8 R08: ffffffff9ad97ce0 R09: 0000000000000001
      R10: 0000000000000000 R11: 0000000000000001 R12: 00000000ffffffe4
      R13: ffff8d61c25fe688 R14: ffff8d61ebd88800 R15: ffff8d61ebd88a90
      FS:  0000000000000000(0000) GS:ffff8d64ed400000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      CR2: 00007fa46a8b1000 CR3: 0000000148d18003 CR4: 0000000000370ee0
      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
      Call Trace:
       <TASK>
       __btrfs_free_extent+0x516/0x950 [btrfs]
       __btrfs_run_delayed_refs+0x2b1/0x1250 [btrfs]
       btrfs_run_delayed_refs+0x86/0x210 [btrfs]
       flush_space+0x403/0x630 [btrfs]
       ? call_rcu_tasks_generic+0x50/0x80
       ? lock_release+0x223/0x4a0
       ? btrfs_get_alloc_profile+0xb5/0x290 [btrfs]
       ? do_raw_spin_unlock+0x4b/0xa0
       btrfs_async_reclaim_metadata_space+0x139/0x320 [btrfs]
       process_one_work+0x24c/0x5b0
       worker_thread+0x55/0x3c0
       ? process_one_work+0x5b0/0x5b0
       kthread+0x17c/0x1a0
       ? set_kthread_struct+0x40/0x40
       ret_from_fork+0x22/0x30
    
    There's a couple of reasons for this, but in generic/619's case the
    largest reason is because it is a very small file system, ad we do not
    reserve enough space for the global reserve.
    
    With the free space tree we now have the free space tree that we need to
    modify when running delayed refs.  This means we need the global reserve
    to take this into account when it calculates the minimum size it needs
    to be.  This is especially important for very small file systems.
    
    Fix this by adjusting the minimum global block rsv size math to include
    the size of the free space tree when calculating the size.
    
    Reviewed-by: Nikolay Borisov <nborisov@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c9d328c0c4b0dc2e27c219d041855e74bb073ab0
Author: Qu Wenruo <wqu@suse.com>
Date:   Mon Dec 6 13:52:58 2021 +0800

    btrfs: scrub: merge SCRUB_PAGES_PER_RD_BIO and SCRUB_PAGES_PER_WR_BIO
    
    These two values were introduced in commit ff023aac3119 ("Btrfs: add code
    to scrub to copy read data to another disk") as an optimization.
    
    But the truth is, block layer scheduler can do whatever it wants to
    merge/split bios to improve performance.
    
    Doing such "optimization" is not really going to affect much, especially
    considering how good current block layer optimizations are doing.
    Remove such old and immature optimization from our code.
    
    Since we're here, also change BUG_ON()s using these two macros to use
    ASSERT()s.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0bb3acdc48243c0db9fd93fc904ce81bdb4049c9
Author: Qu Wenruo <wqu@suse.com>
Date:   Mon Dec 6 13:52:57 2021 +0800

    btrfs: update SCRUB_MAX_PAGES_PER_BLOCK
    
    Use BTRFS_MAX_METADATA_BLOCKSIZE and SZ_4K (minimal sectorsize) to
    calculate this value.
    
    And remove one stale comment on the value, in fact with recent subpage
    support, BTRFS_MAX_METADATA_BLOCKSIZE * PAGE_SIZE is already beyond
    BTRFS_STRIPE_LEN, just we don't use the full page.
    
    Also since we're here, update the BUG_ON() related to
    SCRUB_MAX_PAGES_PER_BLOCK to ASSERT().
    
    As those ASSERT() are really only for developers to catch early obvious
    bugs, not to let end users suffer.
    
    Signed-off-by: Qu Wenruo <wqu@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 8697b8f88e2a750685b73c16c2a1bd438795ae90
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:20 2021 -0500

    btrfs: do not check -EAGAIN when truncating inodes in the log root
    
    We only throttle the btrfs_truncate_inode_items if the root is
    SHAREABLE, which isn't set on the log root, which means this loop is
    unnecessary.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit e48dac7f6f4c0410aa38dbd59b991f2b24b286ae
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:19 2021 -0500

    btrfs: make should_throttle loop local in btrfs_truncate_inode_items
    
    We reset this bool on every loop through the truncate loop, make this
    variable local to the loop.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 0adbc6190c34b2e39f67b086cefc260e30045f48
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:18 2021 -0500

    btrfs: combine extra if statements in btrfs_truncate_inode_items
    
    We have
    
        if (del_item)
                // do something
        else
                // something else
        if (del_item)
                // do yet another thing
        else
                // something else entirely
    
    back to back in btrfs_truncate_inode_items, collapse these two sets of
    if statements into one.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 376b91d5702f8db14beb55148039684f808e0693
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:17 2021 -0500

    btrfs: convert BUG() for pending_del_nr into an ASSERT
    
    This is a logic correctness check, convert it into an ASSERT() instead
    of a BUG().
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 56e1edb0e3334db479b8400abc5a9c03602e5ae8
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:16 2021 -0500

    btrfs: convert BUG_ON() in btrfs_truncate_inode_items to ASSERT
    
    We have a correctness BUG_ON() in btrfs_truncate_inode_items to make
    sure that we're always using min_type == BTRFS_EXTENT_DATA_KEY if
    new_size is > 0.  Convert this to an ASSERT.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 71d18b53540f106a394cb35ed93b487b76678b06
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:15 2021 -0500

    btrfs: add inode to truncate control
    
    In the future we're going to want to use btrfs_truncate_inode_items
    without looking up the associated inode.  In order to accommodate this
    add the inode to btrfs_truncate_control and handle the case where
    control->inode is NULL appropriately.  This is fairly straightforward,
    we simply need to add a helper for the trace points, as the file extent
    map update is controlled by a flag on btrfs_truncate_control.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 487e81d2a4009d17dcfe7c67b78b75cd96bcdde3
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:14 2021 -0500

    btrfs: pass the ino via truncate control
    
    In the future we are going to want to truncate inode items without
    needing to have an btrfs_inode to pass in, so add ino to the
    btrfs_truncate_control and use that to look up the inode items to
    truncate.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 655807b8957ba84a583104c422a8f53725997d55
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:13 2021 -0500

    btrfs: use a flag to control when to clear the file extent range
    
    We only care about updating the file extent range when we are doing a
    normal truncation.  We skip this for tree logging currently, but we can
    also skip this for eviction as well.  Using a flag makes it more
    explicit when we want to do this work.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 5caa490ed8f07488e47378999bd4ad451bf8858b
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:12 2021 -0500

    btrfs: control extent reference updates with a control flag for truncate
    
    We've had weird bugs in the past where we forgot to adjust the truncate
    path to deal with the fact that we can be called by the tree log path.
    Instead of checking if our root is a LOG_ROOT use a flag on the
    btrfs_truncate_control to indicate that we don't want to do extent
    reference updates during this truncate.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 462b728ea83fa85f1c0d2b79efb6187745444ce5
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:11 2021 -0500

    btrfs: only call inode_sub_bytes in truncate paths that care
    
    We currently have a bunch of awkward checks to make sure we only update
    the inode i_bytes if we're truncating the real inode.  Instead keep
    track of the number of bytes we need to sub in the
    btrfs_truncate_control, and then do the appropriate adjustment in the
    truncate paths that care.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit c2ddb612a8b320dde8641a74c35e107aa496d5f3
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:10 2021 -0500

    btrfs: only update i_size in truncate paths that care
    
    We currently will update the i_size of the inode as we truncate it down,
    however we skip this if we're calling btrfs_truncate_inode_items from
    the tree log code.  However we also don't care about this in the case of
    evict.  Instead keep track of this value in the btrfs_truncate_control
    and then have btrfs_truncate() and the free space cache truncate path
    both do the i_size update themselves.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d9ac19c3806434af2a92b4008dbf39c2a67c60cf
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:09 2021 -0500

    btrfs: add truncate control struct
    
    I'm going to be adding more arguments and counters to
    btrfs_truncate_inode_items, so add a control struct to handle all of the
    extra arguments to make it easier to follow.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 7097a941bf75ed1f632342937984a24f0b1d76a4
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:08 2021 -0500

    btrfs: remove found_extent from btrfs_truncate_inode_items
    
    We only set this if we find a normal file extent, del_item == 1, and the
    file extent points to a real extent and isn't a hole extent.  We can use
    del_item == 1 && extent_start != 0 to get the same information that
    found_extent provides, so remove this variable and use the other
    variables instead.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 2adc75d61203a7d7d0178e1c5402e1f792ac4636
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:07 2021 -0500

    btrfs: move btrfs_kill_delayed_inode_items into evict
    
    We have a special case in btrfs_truncate_inode_items() to call
    btrfs_kill_delayed_inode_items() if min_type == 0, which is only called
    during evict.
    
    Instead move this out into evict proper, and add some comments because I
    erroneously attempted to remove this code altogether without
    understanding what we were doing.
    
    Evict is updating the inode only because we only care about making sure
    the i_nlink count has hit disk.  If we had pending deletions we don't
    want to process those via the delayed inode updates, we simply want to
    drop all of them and reclaim the reserved metadata space.  Then from
    there the btrfs_truncate_inode_items() will do the work to remove all of
    the items as appropriate.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 275312a03c625a35c33440d3937804b17f894e4f
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:06 2021 -0500

    btrfs: remove free space cache inode check in btrfs_truncate_inode_items
    
    We no longer have inode cache feature, so this check is extraneous as
    the only inode cache is in the tree_root, which is not marked as
    SHAREABLE.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 9a4a1429acbe0508095dbb2c54e9e8b78dfe52f0
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:05 2021 -0500

    btrfs: move extent locking outside of btrfs_truncate_inode_items
    
    Currently we are locking the extent and dropping the extent cache for
    any inodes we truncate, unless they're in the tree log.  We call this
    helper from:
    
    - truncate
    - evict
    - tree log
    - free space cache truncation
    
    For evict we've already dropped all of the extent cache for this inode
    once we've gotten here, and we're the only one accessing this inode, so
    this step is unnecessary.
    
    For the tree log code we already skip this part.
    
    Pull this work into the truncate path and the free space cache
    truncation path.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 54f03ab1e19b04dea546f83ae70b3285bc61b9f8
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:04 2021 -0500

    btrfs: move btrfs_truncate_inode_items to inode-item.c
    
    This is an inode item related manipulation with a few vfs related
    adjustments.  I'm going to remove the vfs related code from this helper
    and simplify it a lot, but I want those changes to be easily seen via
    git blame, so move this function now and then the simplification work
    can be done.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 26c2c4540d6d5c85a22a857ccda304361f1afeaf
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Fri Dec 3 17:18:03 2021 -0500

    btrfs: add an inode-item.h
    
    We have a few helpers in inode-item.c, and I'm going to make a few
    changes to how we do truncate in the future, so break out these
    definitions into their own header file to trim down ctree.h some and
    make it easier to do the work on truncate in the future.
    
    Reviewed-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 727e60604f6a61b8e4330e8fe63a8cf0a067d29d
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:40 2021 +0000

    btrfs: remove stale comment about locking at btrfs_search_slot()
    
    The comment refers to the old extent buffer locking code, where we used to
    have custom locks that had blocking and spinning behaviour modes. That is
    not the case anymore, since we have transitioned to rw semaphores, so the
    comment does not offer any value anymore. Remove it.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit bb8e9a608055e016aace6db269432ba52a57dcc1
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:39 2021 +0000

    btrfs: remove BUG_ON() after splitting leaf
    
    After calling split_leaf() we BUG_ON() if the returned value is greater
    than zero. However split_leaf() only returns 0, in case of success, or a
    negative value in case of an error.
    
    The reason for the BUG_ON() is that if we ever get a positive return
    value from split_leaf(), we can not simply propagate it to the callers
    of btrfs_search_slot(), as that would be interpreted as "key not found"
    and not as an error. That means it could result in callers ending up
    causing some potential silent corruption.
    
    So change the BUG_ON() to an ASSERT(), and in case assertions are
    disabled, produce a warning and set the return value to an error, to make
    it not possible to get into a silent corruption and having the error not
    noticed.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 109324cfda067b84b948002584849a02dd0a6641
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:38 2021 +0000

    btrfs: move leaf search logic out of btrfs_search_slot()
    
    There's quite a significant amount of code for doing the key search for a
    leaf at btrfs_search_slot(), with a couple labels and gotos in it, plus
    btrfs_search_slot() is already big enough.
    
    So move the logic that does the key search on a leaf into a new helper
    function. This makes it better organized, removing the need for the labels
    and the gotos, as well as reducing the indentation level and the size of
    btrfs_search_slot().
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit e5e1c1741b3de3f8d06fe4b700d83709a7da0610
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:37 2021 +0000

    btrfs: remove useless condition check before splitting leaf
    
    When inserting a key, we check if the write_lock_level is less than 1,
    and if so we set it to 1, release the path and retry the tree traversal.
    
    However that is unnecessary, because when ins_len is greater than 0, we
    know that write_lock_level can never be less than 1.
    
    The logic to retry is also buggy, because in case ins_len was decremented,
    due to an exact key match and the search is not meant for item extension
    (path->search_for_extension is 0), we retry without incrementing ins_len,
    which would make the next retry decrement it again by the same amount.
    
    So remove the check for write_lock_level being less than 1 and add an
    assertion to assert it's always >= 1.
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit e2e58d0f8dc55533c24fc7b3e101092f571b4a43
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:36 2021 +0000

    btrfs: try to unlock parent nodes earlier when inserting a key
    
    When inserting a new key, we release the write lock on the leaf's parent
    only after doing the binary search on the leaf. This is because if the
    key ends up at slot 0, we will have to update the key at slot 0 of the
    parent node. The same reasoning applies to any other upper level nodes
    when their slot is 0. We also need to keep the parent locked in case the
    leaf does not have enough free space to insert the new key/item, because
    in that case we will split the leaf and we will need to add a new key to
    the parent due to a new leaf resulting from the split operation.
    
    However if the leaf has enough space for the new key and the key does not
    end up at slot 0 of the leaf we could release our write lock on the parent
    before doing the binary search on the leaf to figure out the destination
    slot. That leads to reducing the amount of time other tasks are blocked
    waiting to lock the parent, therefore increasing parallelism when there
    are other tasks that are trying to access other leaves accessible through
    the same parent. This also applies to other upper nodes besides the
    immediate parent, when their slot is 0, since we keep locks on them until
    we figure out if the leaf slot is slot 0 or not.
    
    In fact, having the key ending at up slot 0 when is rare. Typically it
    only happens when the key is less than or equals to the smallest, the
    "left most", key of the entire btree, during a split attempt when we try
    to push to the right sibling leaf or when the caller just wants to update
    the item of an existing key. It's also very common that a leaf has enough
    space to insert a new key, since after a split we move about half of the
    keys from one into the new leaf.
    
    So unlock the parent, and any other upper level nodes, when during a key
    insertion we notice the key is greater then the first key in the leaf and
    the leaf has enough free space. After unlocking the upper level nodes, do
    the binary search using a low boundary of slot 1 and not slot 0, to figure
    out the slot where the key will be inserted (or where the key already is
    in case it exists and the caller wants to modify its item data).
    This extra comparison, with the first key, is cheap and the key is very
    likely already in a cache line because it immediately follows the header
    of the extent buffer and we have recently read the level field of the
    header (which in fact is the last field of the header).
    
    The following fs_mark test was run on a non-debug kernel (debian's default
    kernel config), with a 12 cores intel CPU, and using a NVMe device:
    
      $ cat run-fsmark.sh
      #!/bin/bash
    
      DEV=/dev/nvme0n1
      MNT=/mnt/nvme0n1
      MOUNT_OPTIONS="-o ssd"
      MKFS_OPTIONS="-O no-holes -R free-space-tree"
      FILES=100000
      THREADS=$(nproc --all)
      FILE_SIZE=0
    
      echo "performance" | \
            tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
    
      mkfs.btrfs -f $MKFS_OPTIONS $DEV
      mount $MOUNT_OPTIONS $DEV $MNT
    
      OPTS="-S 0 -L 10 -n $FILES -s $FILE_SIZE -t $THREADS -k"
      for ((i = 1; i <= $THREADS; i++)); do
          OPTS="$OPTS -d $MNT/d$i"
      done
    
      fs_mark $OPTS
    
      umount $MNT
    
    Before this change:
    
    FSUse%        Count         Size    Files/sec     App Overhead
         0      1200000            0     165273.6          5958381
         0      2400000            0     190938.3          6284477
         0      3600000            0     181429.1          6044059
         0      4800000            0     173979.2          6223418
         0      6000000            0     139288.0          6384560
         0      7200000            0     163000.4          6520083
         1      8400000            0      57799.2          5388544
         1      9600000            0      66461.6          5552969
         2     10800000            0      49593.5          5163675
         2     12000000            0      57672.1          4889398
    
    After this change:
    
    FSUse%        Count         Size    Files/sec            App Overhead
         0      1200000            0     167987.3 (+1.6%)         6272730
         0      2400000            0     198563.9 (+4.0%)         6048847
         0      3600000            0     197436.6 (+8.8%)         6163637
         0      4800000            0     202880.7 (+16.6%)        6371771
         1      6000000            0     167275.9 (+20.1%)        6556733
         1      7200000            0     204051.2 (+25.2%)        6817091
         1      8400000            0      69622.8 (+20.5%)        5525675
         1      9600000            0      69384.5 (+4.4%)         5700723
         1     10800000            0      61454.1 (+23.9%)        5363754
         3     12000000            0      61908.7 (+7.3%)         5370196
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit fb81212c07b1d1870fefdf883d2d4e8a9386308b
Author: Filipe Manana <fdmanana@suse.com>
Date:   Thu Dec 2 10:30:35 2021 +0000

    btrfs: allow generic_bin_search() to take low boundary as an argument
    
    Right now generic_bin_search() always uses a low boundary slot of 0, but
    in the next patch we'll want to often skip slot 0 when searching for a
    key. So make generic_bin_search() have the low boundary slot specified
    as an argument, and move the check for the extent buffer level from
    btrfs_bin_search() to generic_bin_search() to avoid adding another
    wrapper around generic_bin_search().
    
    Reviewed-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 120de408e4b97504a2d9b5ca534b383de2c73d49
Author: Josef Bacik <josef@toxicpanda.com>
Date:   Wed Nov 24 14:14:24 2021 -0500

    btrfs: check the root node for uptodate before returning it
    
    Now that we clear the extent buffer uptodate if we fail to write it out
    we need to check to see if our root node is uptodate before we search
    down it.  Otherwise we could return stale data (or potentially corrupt
    data that was caught by the write verification step) and think that the
    path is OK to search down.
    
    CC: stable@vger.kernel.org # 5.4+
    Reviewed-by: Nikolay Borisov <nborisov@suse.com>
    Signed-off-by: Josef Bacik <josef@toxicpanda.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit a174c0a2e857081195db6888323802f0fae793ef
Author: Nikolay Borisov <nborisov@suse.com>
Date:   Thu Nov 25 11:14:43 2021 +0200

    btrfs: allow device add if balance is paused
    
    Currently paused balance precludes adding a device since they are both
    considered exclusive ops and we can have at most one running at a time.
    This is problematic in case a filesystem encounters an ENOSPC situation
    while balance is running, in this case the only thing the user can do
    is mount the fs with "skip_balance" which pauses balance and delete some
    data to free up space for balance. However, it should be possible to add
    a new device when balance is paused.
    
    Fix this by allowing device add to proceed when balance is paused.
    
    Signed-off-by: Nikolay Borisov <nborisov@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit 621a1ee1d399c77dd4604aeab3e0f6319f649dbc
Author: Nikolay Borisov <nborisov@suse.com>
Date:   Thu Nov 25 11:14:42 2021 +0200

    btrfs: make device add compatible with paused balance in btrfs_exclop_start_try_lock
    
    This is needed to enable device add to work in cases when a file system
    has been mounted with 'skip_balance' mount option.
    
    Signed-off-by: Nikolay Borisov <nborisov@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit efc0e69c2feab8efcdbb9efdb9aae892d11b1545
Author: Nikolay Borisov <nborisov@suse.com>
Date:   Thu Nov 25 11:14:41 2021 +0200

    btrfs: introduce exclusive operation BALANCE_PAUSED state
    
    Current set of exclusive operation states is not sufficient to handle
    all practical use cases. In particular there is a need to be able to add
    a device to a filesystem that have paused balance. Currently there is no
    way to distinguish between a running and a paused balance. Fix this by
    introducing BTRFS_EXCLOP_BALANCE_PAUSED which is going to be set in 2
    occasions:
    
    1. When a filesystem is mounted with skip_balance and there is an
       unfinished balance it will now be into BALANCE_PAUSED instead of
       simply BALANCE state.
    
    2. When a running balance is paused.
    
    Signed-off-by: Nikolay Borisov <nborisov@suse.com>
    Reviewed-by: David Sterba <dsterba@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit d96b34248c2f4ea8cd09286090f2f6f77102eaab
Author: Filipe Manana <fdmanana@suse.com>
Date:   Mon Nov 22 12:03:38 2021 +0000

    btrfs: make send work with concurrent block group relocation
    
    We don't allow send and balance/relocation to run in parallel in order
    to prevent send failing or silently producing some bad stream. This is
    because while send is using an extent (specially metadata) or about to
    read a metadata extent and expecting it belongs to a specific parent
    node, relocation can run, the transaction used for the relocation is
    committed and the extent gets reallocated while send is still using the
    extent, so it ends up with a different content than expected. This can
    result in just failing to read a metadata extent due to failure of the
    validation checks (parent transid, level, etc), failure to find a
    backreference for a data extent, and other unexpected failures. Besides
    reallocation, there's also a similar problem of an extent getting
    discarded when it's unpinned after the transaction used for block group
    relocation is committed.
    
    The restriction between balance and send was added in commit 9e967495e0e0
    ("Btrfs: prevent send failures and crashes due to concurrent relocation"),
    kernel 5.3, while the more general restriction between send and relocation
    was added in commit 1cea5cf0e664 ("btrfs: ensure relocation never runs
    while we have send operations running"), kernel 5.14.
    
    Both send and relocation can be very long running operations. Relocation
    because it has to do a lot of IO and expensive backreference lookups in
    case there are many snapshots, and send due to read IO when operating on
    very large trees. This makes it inconvenient for users and tools to deal
    with scheduling both operations.
    
    For zoned filesystem we also have automatic block group relocation, so
    send can fail with -EAGAIN when users least expect it or send can end up
    delaying the block group relocation for too long. In the future we might
    also get the automatic block group relocation for non zoned filesystems.
    
    This change makes it possible for send and relocation to run in parallel.
    This is achieved the following way:
    
    1) For all tree searches, send acquires a read lock on the commit root
       semaphore;
    
    2) After each tree search, and before releasing the commit root semaphore,
       the leaf is cloned and placed in the search path (struct btrfs_path);
    
    3) After releasing the commit root semaphore, the changed_cb() callback
       is invoked, which operates on the leaf and writes commands to the pipe
       (or file in case send/receive is not used with a pipe). It's important
       here to not hold a lock on the commit root semaphore, because if we did
       we could deadlock when sending and receiving to the same filesystem
       using a pipe - the send task blocks on the pipe because it's full, the
       receive task, which is the only consumer of the pipe, triggers a
       transaction commit when attempting to create a subvolume or reserve
       space for a write operation for example, but the transaction commit
       blocks trying to write lock the commit root semaphore, resulting in a
       deadlock;
    
    4) Before moving to the next key, or advancing to the next change in case
       of an incremental send, check if a transaction used for relocation was
       committed (or is about to finish its commit). If so, release the search
       path(s) and restart the search, to where we were before, so that we
       don't operate on stale extent buffers. The search restarts are always
       possible because both the send and parent roots are RO, and no one can
       add, remove of update keys (change their offset) in RO trees - the
       only exception is deduplication, but that is still not allowed to run
       in parallel with send;
    
    5) Periodically check if there is contention on the commit root semaphore,
       which means there is a transaction commit trying to write lock it, and
       release the semaphore and reschedule if there is contention, so as to
       avoid causing any significant delays to transaction commits.
    
    This leaves some room for optimizations for send to have less path
    releases and re searching the trees when there's relocation running, but
    for now it's kept simple as it performs quite well (on very large trees
    with resulting send streams in the order of a few hundred gigabytes).
    
    Test case btrfs/187, from fstests, stresses relocation, send and
    deduplication attempting to run in parallel, but without verifying if send
    succeeds and if it produces correct streams. A new test case will be added
    that exercises relocation happening in parallel with send and then checks
    that send succeeds and the resulting streams are correct.
    
    A final note is that for now this still leaves the mutual exclusion
    between send operations and deduplication on files belonging to a root
    used by send operations. A solution for that will be slightly more complex
    but it will eventually be built on top of this change.
    
    Signed-off-by: Filipe Manana <fdmanana@suse.com>
    Signed-off-by: David Sterba <dsterba@suse.com>

commit fff63521cd6e197738db9297076d83b4081ac80f
Merge: 14676c04783c6 269bda9e7da48
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 7 11:29:45 2022 +0000

    Merge branch 'mptcp-fixes'
    
    Mat Martineau says:
    
    ====================
    mptcp: Fixes for buffer reclaim and option writing
    
    Here are three fixes dealing with a syzkaller crash MPTCP triggers in
    the memory manager in 5.16-rc8, and some option writing problems.
    
    Patches 1 and 2 fix some corner cases in MPTCP option writing.
    
    Patch 3 addresses a crash that syzkaller found a way to trigger in the mm
    subsystem by passing an invalid value to __sk_mem_reduce_allocated().
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 269bda9e7da48eafb599d01c96199caa2f7547e5
Author: Mat Martineau <mathew.j.martineau@linux.intel.com>
Date:   Thu Jan 6 14:06:38 2022 -0800

    mptcp: Check reclaim amount before reducing allocation
    
    syzbot found a page counter underflow that was triggered by MPTCP's
    reclaim code:
    
    page_counter underflow: -4294964789 nr_pages=4294967295
    WARNING: CPU: 2 PID: 3785 at mm/page_counter.c:56 page_counter_cancel+0xcf/0xe0 mm/page_counter.c:56
    Modules linked in:
    CPU: 2 PID: 3785 Comm: kworker/2:6 Not tainted 5.16.0-rc1-syzkaller #0
    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
    Workqueue: events mptcp_worker
    
    RIP: 0010:page_counter_cancel+0xcf/0xe0 mm/page_counter.c:56
    Code: c7 04 24 00 00 00 00 45 31 f6 eb 97 e8 2a 2b b5 ff 4c 89 ea 48 89 ee 48 c7 c7 00 9e b8 89 c6 05 a0 c1 ba 0b 01 e8 95 e4 4b 07 <0f> 0b eb a8 4c 89 e7 e8 25 5a fb ff eb c7 0f 1f 00 41 56 41 55 49
    RSP: 0018:ffffc90002d4f918 EFLAGS: 00010082
    
    RAX: 0000000000000000 RBX: ffff88806a494120 RCX: 0000000000000000
    RDX: ffff8880688c41c0 RSI: ffffffff815e8f28 RDI: fffff520005a9f15
    RBP: ffffffff000009cb R08: 0000000000000000 R09: 0000000000000000
    R10: ffffffff815e2cfe R11: 0000000000000000 R12: ffff88806a494120
    R13: 00000000ffffffff R14: 0000000000000000 R15: 0000000000000001
    FS:  0000000000000000(0000) GS:ffff88802cc00000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000001b2de21000 CR3: 000000005ad59000 CR4: 0000000000150ee0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     page_counter_uncharge+0x2e/0x60 mm/page_counter.c:160
     drain_stock+0xc1/0x180 mm/memcontrol.c:2219
     refill_stock+0x139/0x2f0 mm/memcontrol.c:2271
     __sk_mem_reduce_allocated+0x24d/0x550 net/core/sock.c:2945
     __mptcp_rmem_reclaim net/mptcp/protocol.c:167 [inline]
     __mptcp_mem_reclaim_partial+0x124/0x410 net/mptcp/protocol.c:975
     mptcp_mem_reclaim_partial net/mptcp/protocol.c:982 [inline]
     mptcp_alloc_tx_skb net/mptcp/protocol.c:1212 [inline]
     mptcp_sendmsg_frag+0x18c6/0x2190 net/mptcp/protocol.c:1279
     __mptcp_push_pending+0x232/0x720 net/mptcp/protocol.c:1545
     mptcp_release_cb+0xfe/0x200 net/mptcp/protocol.c:2975
     release_sock+0xb4/0x1b0 net/core/sock.c:3306
     mptcp_worker+0x51e/0xc10 net/mptcp/protocol.c:2443
     process_one_work+0x9b2/0x1690 kernel/workqueue.c:2298
     worker_thread+0x658/0x11f0 kernel/workqueue.c:2445
     kthread+0x405/0x4f0 kernel/kthread.c:327
     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
     </TASK>
    
    __mptcp_mem_reclaim_partial() could call __mptcp_rmem_reclaim() with a
    negative value, which passed that negative value to
    __sk_mem_reduce_allocated() and triggered the splat above.
    
    Check for a reclaim amount that is positive and large enough for
    __mptcp_rmem_reclaim() to actually adjust rmem_fwd_alloc (much like
    the sk_mem_reclaim_partial() code the function is based on).
    
    v2: Use '>' instead of '>=', since SK_MEM_QUANTUM - 1 would get
    right-shifted into nothing by __mptcp_rmem_reclaim.
    
    Fixes: 6511882cdd82 ("mptcp: allocate fwd memory separately on the rx and tx path")
    Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/252
    Reported-and-tested-by: syzbot+bc9e2d2dbcb347dd215a@syzkaller.appspotmail.com
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Michal Hocko <mhocko@suse.com>
    Acked-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 110b6d1fe98fd7af9893992459b651594d789293
Author: Geliang Tang <geliang.tang@suse.com>
Date:   Thu Jan 6 14:06:37 2022 -0800

    mptcp: fix a DSS option writing error
    
    'ptr += 1;' was omitted in the original code.
    
    If the DSS is the last option -- which is what we have most of the
    time -- that's not an issue. But it is if we need to send something else
    after like a RM_ADDR or an MP_PRIO.
    
    Fixes: 1bff1e43a30e ("mptcp: optimize out option generation")
    Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 04fac2cae9422a3401c172571afbcfdd58fa5c7e
Author: Matthieu Baerts <matthieu.baerts@tessares.net>
Date:   Thu Jan 6 14:06:36 2022 -0800

    mptcp: fix opt size when sending DSS + MP_FAIL
    
    When these two options had to be sent -- which is not common -- the DSS
    size was not being taken into account in the remaining size.
    
    Additionally in this situation, the reported size was only the one of
    the MP_FAIL which can cause issue if at the end, we need to write more
    in the TCP options than previously said.
    
    Here we use a dedicated variable for MP_FAIL size to keep the
    WARN_ON_ONCE() just after.
    
    Fixes: c25aeb4e0953 ("mptcp: MP_FAIL suboption sending")
    Acked-and-tested-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ca1a6705b271d458d54bbeb072af97ec468d3b37
Merge: 26abf15c49e0f e9d09baca6762
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 7 11:27:07 2022 +0000

    Merge branch 'mptcp-next'
    
    Mat Martineau says:
    
    ====================
    mptcp: New features and cleanup
    
    These patches have been tested in the MPTCP tree for a longer than usual
    time (thanks to holiday schedules), and are ready for the net-next
    branch. Changes include feature updates, small fixes, refactoring, and
    some selftest changes.
    
    Patch 1 fixes an OUTQ ioctl issue with TCP fallback sockets.
    
    Patches 2, 3, and 6 add support of the MPTCP fastclose option (quick
    shutdown of the full MPTCP connection, similar to TCP RST in regular
    TCP), and a related self test.
    
    Patch 4 cleans up some accept and poll code that is no longer needed
    after the fastclose changes.
    
    Patch 5 add userspace disconnect using AF_UNSPEC, which is used when
    testing fastclose and makes the MPTCP socket's handling of AF_UNSPEC in
    connect() more TCP-like.
    
    Patches 7-11 refactor subflow creation to make better use of multiple
    local endpoints and to better handle individual connection failures when
    creating multiple subflows. Includes self test updates.
    
    Patch 12 cleans up the way subflows are added to the MPTCP connection
    list, eliminating the need for calls throughout the MPTCP code that had
    to check the intermediate "join list" for entries to shift over to the
    main "connection list".
    
    Patch 13 refactors the MPTCP release_cb flags to use separate storage
    for values only accessed with the socket lock held (no atomic ops
    needed), and for values that need atomic operations.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e9d09baca67625cfb41c0f2b547b9dbb4043ae95
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:26 2022 -0800

    mptcp: avoid atomic bit manipulation when possible
    
    Currently the msk->flags bitmask carries both state for the
    mptcp_release_cb() - mostly touched under the mptcp data lock
    - and others state info touched even outside such lock scope.
    
    As a consequence, msk->flags is always manipulated with
    atomic operations.
    
    This change splits such bitmask in two separate fields, so
    that we use plain bit operations when touching the
    cb-related info.
    
    The MPTCP_PUSH_PENDING bit needs additional care, as it is the
    only CB related field currently accessed either under the mptcp
    data lock or the mptcp socket lock.
    Let's add another mask just for such bit's sake.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3e5014909b5661b3da59990d72a317a45ba3b284
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:25 2022 -0800

    mptcp: cleanup MPJ subflow list handling
    
    We can simplify the join list handling leveraging the
    mptcp_release_cb(): if we can acquire the msk socket
    lock at mptcp_finish_join time, move the new subflow
    directly into the conn_list, otherwise place it on join_list and
    let the release_cb process such list.
    
    Since pending MPJ connection are now always processed
    in a timely way, we can avoid flushing the join list
    every time we have to process all the current subflows.
    
    Additionally we can now use the mptcp data lock to protect
    the join_list, removing the additional spin lock.
    
    Finally, the MPJ handshake is now always finalized under the
    msk socket lock, we can drop the additional synchronization
    between mptcp_finish_join() and mptcp_close().
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 46e967d187ed1693b34379ac4e27fd4e1fb40a45
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:24 2022 -0800

    selftests: mptcp: add tests for subflow creation failure
    
    Verify that, when multiple endpoints are available, subflows
    creation proceed even when the first additional subflow creation
    fails - due to packet drop on the relevant link
    
    Co-developed-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a88c9e49693759f9eb49dcda6c45a0d32b07634c
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:23 2022 -0800

    mptcp: do not block subflows creation on errors
    
    If the MPTCP configuration allows for multiple subflows
    creation, and the first additional subflows never reach
    the fully established status - e.g. due to packets drop or
    reset - the in kernel path manager do not move to the
    next subflow.
    
    This patch introduces a new PM helper to cope with MPJ
    subflow creation failure and delay and hook it where appropriate.
    
    Such helper triggers additional subflow creation, as needed
    and updates the PM subflow counter, if the current one is
    closing.
    
    Additionally start all the needed additional subflows
    as soon as the MPTCP socket is fully established, so we don't
    have to cope with slow MPJ handshake blocking the next subflow
    creation.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 86e39e04482b0aadf3ee3ed5fcf2d63816559d36
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:22 2022 -0800

    mptcp: keep track of local endpoint still available for each msk
    
    Include into the path manager status a bitmap tracking the list
    of local endpoints still available - not yet used - for the
    relevant mptcp socket.
    
    Keep such map updated at endpoint creation/deletion time, so
    that we can easily skip already used endpoint at local address
    selection time.
    
    The endpoint used by the initial subflow is lazyly accounted at
    subflow creation time: the usage bitmap is be up2date before
    endpoint selection and we avoid such unneeded task in some relevant
    scenarios - e.g. busy servers accepting incoming subflows but
    not creating any additional ones nor annuncing additional addresses.
    
    Overall this allows for fair local endpoints usage in case of
    subflow failure.
    
    As a side effect, this patch also enforces that each endpoint
    is used at most once for each mptcp connection.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 71b077e48377222c5fdae9ddcc58fe03cdff6932
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:21 2022 -0800

    mptcp: clean-up MPJ option writing
    
    Check for all MPJ variant at once, this reduces the number
    of conditionals traversed on average and will simplify the
    next patch.
    
    No functional change intended.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f7d6a237d7422809d458d754016de2844017cb4d
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:20 2022 -0800

    mptcp: fix per socket endpoint accounting
    
    Since full-mesh endpoint support, the reception of a single ADD_ADDR
    option can cause multiple subflows creation. When such option is
    accepted we increment 'add_addr_accepted' by one. When we received
    a paired RM_ADDR option, we deleted all the relevant subflows,
    decrementing 'add_addr_accepted' by one for each of them.
    
    We have a similar issue for 'local_addr_used'
    
    Fix them moving the pm endpoint accounting outside the subflow
    traversal.
    
    Fixes: 1a0d6136c5f0 ("mptcp: local addresses fullmesh")
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 05be5e273c84f6329b3cac4f5bb7b1fe6eaefd5d
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:19 2022 -0800

    selftests: mptcp: add disconnect tests
    
    Performs several disconnect/reconnect on the same socket,
    ensuring the overall transfer is succesful.
    
    The new test leverages ioctl(SIOCOUTQ) to ensure all the
    pending data is acked before disconnecting.
    
    Additionally order alphabetically the test program arguments list
    for better maintainability.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 3d1d6d66e15612801bec79b190af746622f0d427
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:18 2022 -0800

    mptcp: implement support for user-space disconnect
    
    Handle explicitly AF_UNSPEC in mptcp_stream_connnect() to
    allow user-space to disconnect established MPTCP connections
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 71ba088ce0aa87370b18a1d35cd742f352d51c24
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:17 2022 -0800

    mptcp: cleanup accept and poll
    
    After the previous patch,  msk->subflow will never be deleted during
    the whole msk lifetime. We don't need anymore to acquire references to
    it in mptcp_stream_accept() and we can use the listener subflow accept
    queue to simplify mptcp_poll() for listener socket.
    
    Overall this removes a lock pair and 4 more atomic operations per
    accept().
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b29fcfb54cd70caca5b11c80d8d238854938884a
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:16 2022 -0800

    mptcp: full disconnect implementation
    
    The current mptcp_disconnect() implementation lacks several
    steps, we additionally need to reset the msk socket state
    and flush the subflow list.
    
    Factor out the needed helper to avoid code duplication.
    
    Additionally ensure that the initial subflow is disposed
    only after mptcp_close(), just reset it at disconnect time.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f284c0c7732189fa77567dc061c5f4205c4fa05b
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:15 2022 -0800

    mptcp: implement fastclose xmit path
    
    Allow the MPTCP xmit path to add MP_FASTCLOSE suboption
    on RST egress packets.
    
    Additionally reorder related options writing to reduce
    the number of conditionals required in the fast path.
    
    Co-developed-by: Geliang Tang <geliang.tang@suse.com>
    Signed-off-by: Geliang Tang <geliang.tang@suse.com>
    Co-developed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 58cd405b83b388c75a4c24926e5d4aeae8d1eaf5
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu Jan 6 16:20:14 2022 -0800

    mptcp: keep snd_una updated for fallback socket
    
    After shutdown, for fallback MPTCP sockets, we always have
    
    write_seq == snd_una+1
    
    The above will foul OUTQ ioctl(). Keep snd_una in sync with
    write_seq even after shutdown.
    
    Signed-off-by: Paolo Abeni <pabeni@redhat.com>
    Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 26abf15c49e0fbbcb6dbd70c52ecbde221f1b0fa
Merge: e4a3d6a6a19a8 745a13061aa07
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 7 11:10:57 2022 +0000

    Merge tag 'mlx5-updates-2022-01-06' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
    
    Saeed Mahameed says:
    
    ====================
    mlx5-updates-2022-01-06
    
    1) Expose FEC per lane block counters via ethtool
    
    2) Trivial fixes/updates/cleanup to mlx5e netdev driver
    
    3) Fix htmldoc build warning
    
    4) Spread mlx5 SFs (sub-functions) to all available CPU cores: Commits 1..5
    
    Shay Drory Says:
    ================
    Before this patchset, mlx5 subfunction shared the same IRQs (MSI-X) with
    their peers subfunctions, causing them to use same CPU cores.
    
    In large scale, this is very undesirable, SFs use small number of cpu
    cores and all of them will be packed on the same CPU cores, not
    utilizing all CPU cores in the system.
    
    In this patchset we want to achieve two things.
     a) Spread IRQs used by SFs to all cpu cores
     b) Pack less SFs in the same IRQ, will result in multiple IRQs per core.
    
    In this patchset, we spread SFs over all online cpus available to mlx5
    irqs in Round-Robin manner. e.g.: Whenever a SF is created, pick the next
    CPU core with least number of SF IRQs bound to it, SFs will share IRQs on
    the same core until a certain limit, when such limit is reached, we
    request a new IRQ and add it to that CPU core IRQ pool, when out of IRQs,
    pick any IRQ with least number of SF users.
    
    This enhancement is done in order to achieve a better distribution of
    the SFs over all the available CPUs, which reduces application latency,
    as shown bellow.
    
    Machine details:
    Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz with 56 cores.
    PCI Express 3 with BW of 126 Gb/s.
    ConnectX-5 Ex; EDR IB (100Gb/s) and 100GbE; dual-port QSFP28; PCIe4.0
    x16.
    
    Base line test description:
    Single SF on the system. One instance of netperf is running on-top the
    SF.
    Numbers: latency = 15.136 usec, CPU Util = 35%
    
    Test description:
    There are 250 SFs on the system. There are 3 instances of netperf
    running, on-top three different SFs, in parallel.
    
    Perf numbers:
     # netperf     SFs         latency(usec)     latency    CPU utilization
       affinity    affinity    (lower is better) increase %
     1 cpu=0       cpu={0}     ~23 (app 1-3)     35%        75%
     2 cpu=0,2,4   cpu={0}     app 1: 21.625     30%        68% (CPU 0)
                               app 2-3: 16.5     9%         15% (CPU 2,4)
     3 cpu=0       cpu={0,2,4} app 1: ~16        7%         84% (CPU 0)
                               app 2-3: ~17.9    14%        22% (CPU 2,4)
     4 cpu=0,2,4   cpu={0,2,4} 15.2 (app 1-3)    0%         33% (CPU 0,2,4)
    
     - The first two entries (#1 and #2) show current state. e.g.: SFs are
       using the same CPU. The last two entries (#3 and #4) shows the latency
       reduction improvement of this patch. e.g.: SFs are on different CPUs.
     - Whenever we use several CPUs, in case there is a different CPU
       utilization, write the utilization of each CPU separately.
     - Whenever the latency result of the netperf instances were different,
       write the latency of each netperf instances separately.
    
    Commands:
     - for netperf CPU=0:
    $ for i in {1..3}; do taskset -c 0 netperf -H 1${i}.1.1.1 -t TCP_RR  -- \
      -o RT_LATENCY -r8 & done
    
     - for netperf CPU=0,2,4
    $ for i in {1..3}; do taskset -c $(( ($i - 1) * 2  )) netperf -H \
      1${i}.1.1.1 -t TCP_RR  -- -o RT_LATENCY -r8 & done
    
    ================
    
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 14676c04783c6363b71072c01b42bb7838eb56eb
Merge: 29507144c9981 4f6626b0e1408
Author: David S. Miller <davem@davemloft.net>
Date:   Fri Jan 7 11:09:37 2022 +0000

    Merge tag 'mlx5-fixes-2022-01-06' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux
    
    Saeed Mahameed says:
    
    ====================
    mlx5 fixes 2022-01-06
    
    This series provides bug fixes to mlx5 driver.
    Please pull and let me know if there is any problem.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit f5bdb34bf0c9314548f2d8e2360b703ff3610303
Author: David Vernet <void@manifault.com>
Date:   Wed Dec 29 13:56:47 2021 -0800

    livepatch: Avoid CPU hogging with cond_resched
    
    When initializing a 'struct klp_object' in klp_init_object_loaded(), and
    performing relocations in klp_resolve_symbols(), klp_find_object_symbol()
    is invoked to look up the address of a symbol in an already-loaded module
    (or vmlinux). This, in turn, calls kallsyms_on_each_symbol() or
    module_kallsyms_on_each_symbol() to find the address of the symbol that is
    being patched.
    
    It turns out that symbol lookups often take up the most CPU time when
    enabling and disabling a patch, and may hog the CPU and cause other tasks
    on that CPU's runqueue to starve -- even in paths where interrupts are
    enabled.  For example, under certain workloads, enabling a KLP patch with
    many objects or functions may cause ksoftirqd to be starved, and thus for
    interrupts to be backlogged and delayed. This may end up causing TCP
    retransmits on the host where the KLP patch is being applied, and in
    general, may cause any interrupts serviced by softirqd to be delayed while
    the patch is being applied.
    
    So as to ensure that kallsyms_on_each_symbol() does not end up hogging the
    CPU, this patch adds a call to cond_resched() in kallsyms_on_each_symbol()
    and module_kallsyms_on_each_symbol(), which are invoked when doing a symbol
    lookup in vmlinux and a module respectively.  Without this patch, if a
    live-patch is applied on a 36-core Intel host with heavy TCP traffic, a
    ~10x spike is observed in TCP retransmits while the patch is being applied.
    Additionally, collecting sched events with perf indicates that ksoftirqd is
    awakened ~1.3 seconds before it's eventually scheduled.  With the patch, no
    increase in TCP retransmit events is observed, and ksoftirqd is scheduled
    shortly after it's awakened.
    
    Signed-off-by: David Vernet <void@manifault.com>
    Acked-by: Miroslav Benes <mbenes@suse.cz>
    Acked-by: Song Liu <song@kernel.org>
    Signed-off-by: Petr Mladek <pmladek@suse.com>
    Link: https://lore.kernel.org/r/20211229215646.830451-1-void@manifault.com

commit 7dcf07ac88676a365ce3245b44af2be432f21120
Author: Kishon Vijay Abraham I <kishon@ti.com>
Date:   Fri Nov 26 14:01:16 2021 +0530

    PCI: keystone: Use phandle argument from "ti,syscon-pcie-id"/"ti,syscon-pcie-mode"
    
    Get "syscon" pcie_mode and pcie_id offset from the argument of
    "ti,syscon-pcie-id" and "ti,syscon-pcie-mode" phandle respectively.
    Previously a subnode to "syscon" node was added which has the
    exact memory mapped address of pcie_mode and pcie_id but now the
    offset of pcie_mode and pcie_id within "syscon" is now being passed
    as argument to "ti,syscon-pcie-id" and "ti,syscon-pcie-mode" phandle.
    
    If the offset is not provided in "ti,syscon-pcie-id"/"ti,syscon-pcie-mode",
    the full memory mapped address of pcie_ctrl is used in order to maintain
    old DT compatibility.
    
    Similar change for J721E is as discussed in [1]
    
    [1] -> http://lore.kernel.org/r/CAL_JsqKiUcO76bo1GoepWM1TusJWoty_BRy2hFSgtEVMqtrvvQ@mail.gmail.com
    
    Link: https://lore.kernel.org/r/20211126083119.16570-3-kishon@ti.com
    Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

commit d91e775e661f6dc2c2f83e9dcf7339af14dc41de
Author: Kishon Vijay Abraham I <kishon@ti.com>
Date:   Fri Nov 26 14:01:15 2021 +0530

    dt-bindings: PCI: ti,am65: Fix "ti,syscon-pcie-id"/"ti,syscon-pcie-mode" to take argument
    
    Fix binding documentation of "ti,syscon-pcie-id" and "ti,syscon-pcie-mode"
    to take phandle with argument. The argument is the register offset within
    "syscon" used to configure PCIe controller. Similar change for j721e is
    discussed in [1]
    
    [1] -> http://lore.kernel.org/r/CAL_JsqKiUcO76bo1GoepWM1TusJWoty_BRy2hFSgtEVMqtrvvQ@mail.gmail.com
    
    Link: https://lore.kernel.org/r/20211126083119.16570-2-kishon@ti.com
    Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Reviewed-by: Rob Herring <robh@kernel.org>

commit 7b2932162f66ab33a00a7cdb6d3b2db6dfdbf634
Author: Niklas Schnelle <schnelle@linux.ibm.com>
Date:   Wed Jan 5 16:10:54 2022 +0100

    s390/pci: simplify __pciwb_mio() inline asm
    
    The PCI Write Barrier instruction ignores the registers encoded in it.
    There is thus no need to explicitly set the register to zero or to
    associate it with a variable at all. In the resulting binary this removes
    an unnecessary lghi and it makes the code simpler.
    
    Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
    Signed-off-by: Heiko Carstens <hca@linux.ibm.com>

commit 50b620303a14e885529410d26800f92a735724d6
Author: Li Chen <lchen@ambarella.com>
Date:   Tue Dec 21 02:59:56 2021 +0000

    PCI: endpoint: Return -EINVAL when interrupts num is smaller than 1
    
    In pci_epc_set_msi() we should return immediately if there are no
    interrupts to configure; update the code to return early.
    
    Link: https://lore.kernel.org/r/CH2PR19MB402491B9E503694DBCAC6005A07C9@CH2PR19MB4024.namprd19.prod.outlook.com
    Signed-off-by: Li Chen <lchen@ambarella.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Reviewed-by: Kishon Vijay Abraham I <kishon@ti.com>

commit c9512fd032acfe6f5198c30b6e7e52e0a7df5d31
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Tue Jan 4 11:50:24 2022 +0100

    kobject documentation: remove default_attrs information
    
    Since commit aa30f47cf666 ("kobject: Add support for default attribute
    groups to kobj_type") we have been encouraging the use of default_groups
    instead of default_attrs, so reflect that information in the
    documentation as well so that no new users get added while the kernel is
    converted over to not use this field anymore.
    
    Cc: "Rafael J. Wysocki" <rafael@kernel.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Cc: linux-doc@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Link: https://lore.kernel.org/r/20220104105024.1014313-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 65ace9a85fa7f88aec4d9d842061108161fa47bc
Author: qizhong cheng <qizhong.cheng@mediatek.com>
Date:   Mon Dec 27 21:31:10 2021 +0800

    PCI: mediatek: Assert PERST# for 100ms for power and clock to stabilize
    
    Described in PCIe CEM specification sections 2.2 (PERST# Signal) and
    2.2.1 (Initial Power-Up (G3 to S0)). The deassertion of PERST# should
    be delayed 100ms (TPVPERL) for the power and clock to become stable.
    
    Link: https://lore.kernel.org/r/20211227133110.14500-1-qizhong.cheng@mediatek.com
    Signed-off-by: qizhong cheng <qizhong.cheng@mediatek.com>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
    Acked-by: Pali Rohár <pali@kernel.org>

commit 9d6c59c1c0d62a314a2b46839699b200cccd2d08
Merge: eb52c0fc2331f b01af5c0b0414
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Fri Jan 7 11:13:28 2022 +0100

    Merge branch 'for-5.17/struct-slab' into for-linus
    
    Series "Separate struct slab from struct page" v4
    
    This is originally an offshoot of the folio work by Matthew. One of the more
    complex parts of the struct page definition are the parts used by the slab
    allocators. It would be good for the MM in general if struct slab were its own
    data type, and it also helps to prevent tail pages from slipping in anywhere.
    As Matthew requested in his proof of concept series, I have taken over the
    development of this series, so it's a mix of patches from him (often modified
    by me) and my own.
    
    One big difference is the use of coccinelle to perform the relatively trivial
    parts of the conversions automatically and at once, instead of a larger number
    of smaller incremental reviewable steps. Thanks to Julia Lawall and Luis
    Chamberlain for all their help!
    
    Another notable difference is (based also on review feedback) I don't represent
    with a struct slab the large kmalloc allocations which are not really a slab,
    but use page allocator directly. When going from an object address to a struct
    slab, the code tests first folio slab flag, and only if it's set it converts to
    struct slab. This makes the struct slab type stronger.
    
    Finally, although Matthew's version didn't use any of the folio work, the
    initial support has been merged meanwhile so my version builds on top of it
    where appropriate. This eliminates some of the redundant compound_head()
    being performed e.g. when testing the slab flag.
    
    To sum up, after this series, struct page fields used by slab allocators are
    moved from struct page to a new struct slab, that uses the same physical
    storage. The availability of the fields is further distinguished by the
    selected slab allocator implementation. The advantages include:
    
    - Similar to folios, if the slab is of order > 0, struct slab always is
      guaranteed to be the head page. Additionally it's guaranteed to be an actual
      slab page, not a large kmalloc. This removes uncertainty and potential for
      bugs.
    - It's not possible to accidentally use fields of the slab implementation that's
      not configured.
    - Other subsystems cannot use slab's fields in struct page anymore (some
      existing non-slab usages had to be adjusted in this series), so slab
      implementations have more freedom in rearranging them in the struct slab.
    
    Link: https://lore.kernel.org/all/20220104001046.12263-1-vbabka@suse.cz/

commit 08276bdae68b022a7726edf7416b6748e3df5395
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 23:50:01 2021 +0100

    vfs, fscache: Implement pinning of cache usage for writeback
    
    Cachefiles has a problem in that it needs to keep the backing file for a
    cookie open whilst there are local modifications pending that need to be
    written to it.  However, we don't want to keep the file open indefinitely,
    as that causes EMFILE/ENFILE/ENOMEM problems.
    
    Reopening the cache file, however, is a problem if this is being done due
    to writeback triggered by exit().  Some filesystems will oops if we try to
    open a file in that context because they want to access current->fs or
    other resources that have already been dismantled.
    
    To get around this, I added the following:
    
     (1) An inode flag, I_PINNING_FSCACHE_WB, to be set on a network filesystem
         inode to indicate that we have a usage count on the cookie caching
         that inode.
    
     (2) A flag in struct writeback_control, unpinned_fscache_wb, that is set
         when __writeback_single_inode() clears the last dirty page from
         i_pages - at which point it clears I_PINNING_FSCACHE_WB and sets this
         flag.
    
         This has to be done here so that clearing I_PINNING_FSCACHE_WB can be
         done atomically with the check of PAGECACHE_TAG_DIRTY that clears
         I_DIRTY_PAGES.
    
     (3) A function, fscache_set_page_dirty(), which if it is not set, sets
         I_PINNING_FSCACHE_WB and calls fscache_use_cookie() to pin the cache
         resources.
    
     (4) A function, fscache_unpin_writeback(), to be called by ->write_inode()
         to unuse the cookie.
    
     (5) A function, fscache_clear_inode_writeback(), to be called when the
         inode is evicted, before clear_inode() is called.  This cleans up any
         lingering I_PINNING_FSCACHE_WB.
    
    The network filesystem can then use these tools to make sure that
    fscache_write_to_cache() can write locally modified data to the cache as
    well as to the server.
    
    For the future, I'm working on write helpers for netfs lib that should
    allow this facility to be removed by keeping track of the dirty regions
    separately - but that's incomplete at the moment and is also going to be
    affected by folios, one way or another, since it deals with pages
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819615157.215744.17623791756928043114.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906917856.143852.8224898306177154573.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967124567.1823006.14188359004568060298.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021524705.640689.17824932021727663017.stgit@warthog.procyon.org.uk/ # v4

commit b6e16652d6c0e4f9e9b120f66966ec153f0623fc
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:06:34 2021 +0100

    fscache: Implement higher-level write I/O interface
    
    Provide a higher-level function than fscache_write() to perform a write
    from an inode's pagecache to the cache, whilst fending off concurrent
    writes by means of the PG_fscache mark on a page:
    
            void fscache_write_to_cache(struct fscache_cookie *cookie,
                                        struct address_space *mapping,
                                        loff_t start,
                                        size_t len,
                                        loff_t i_size,
                                        netfs_io_terminated_t term_func,
                                        void *term_func_priv,
                                        bool caching);
    
    If caching is false, this function does nothing except call (*term_func)()
    if given.  It assumes that, in such a case, PG_fscache will not have been
    set on the pages.
    
    Otherwise, if caching is true, this function requires the source pages to
    have had PG_fscache set on them before calling.  start and len define the
    region of the file to be modified and i_size indicates the new file size.
    The source pages are extracted from the mapping.
    
    term_func and term_func_priv work as for fscache_write().  The PG_fscache
    marks will be cleared at the end of the operation, before term_func is
    called or the function otherwise returns.
    
    There is an additonal helper function to clear the PG_fscache bits from a
    range of pages:
    
            void fscache_clear_page_bits(struct fscache_cookie *cookie,
                                         struct address_space *mapping,
                                         loff_t start, size_t len,
                                         bool caching);
    
    If caching is true, the pages to be managed are expected to be located on
    mapping in the range defined by start and len.  If caching is false, it
    does nothing.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819614155.215744.5528123235123721230.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906916346.143852.15632773570362489926.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967123599.1823006.12946816026724657428.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021522672.640689.4381958316198807813.stgit@warthog.procyon.org.uk/ # v4

commit 9af1c6c3089b294ffa240e0fbba356666698b6d0
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:06:34 2021 +0100

    fscache: Implement raw I/O interface
    
    Provide a pair of functions to perform raw I/O on the cache.  The first
    function allows an arbitrary asynchronous direct-IO read to be made against
    a cache object, though the read should be aligned and sized appropriately
    for the backing device:
    
            int fscache_read(struct netfs_cache_resources *cres,
                             loff_t start_pos,
                             struct iov_iter *iter,
                             enum netfs_read_from_hole read_hole,
                             netfs_io_terminated_t term_func,
                             void *term_func_priv);
    
    The cache resources must have been previously initialised by
    fscache_begin_read_operation().  A read operation is sent to the backing
    filesystem, starting at start_pos within the file.  The size of the read is
    specified by the iterator, as is the location of the output buffer.
    
    If there is a hole in the data it can be ignored and left to the backing
    filesystem to deal with (NETFS_READ_HOLE_IGNORE), a hole at the beginning
    can be skipped over and the buffer padded with zeros
    (NETFS_READ_HOLE_CLEAR) or -ENODATA can be given (NETFS_READ_HOLE_FAIL).
    
    If term_func is not NULL, the operation may be performed asynchronously.
    Upon completion, successful or otherwise, (*term_func)() will be called and
    passed term_func_priv, along with an error or the amount of data
    transferred.  If the op is run asynchronously, fscache_read() will return
    -EIOCBQUEUED.
    
    The second function allows an arbitrary asynchronous direct-IO write to be
    made against a cache object, though the write should be aligned and sized
    appropriately for the backing device:
    
            int fscache_write(struct netfs_cache_resources *cres,
                              loff_t start_pos,
                              struct iov_iter *iter,
                              netfs_io_terminated_t term_func,
                              void *term_func_priv);
    
    This works in very similar way to fscache_read(), except that there's no
    need to deal with holes (they're just overwritten).
    
    The caller is responsible for preventing concurrent overlapping writes.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819613224.215744.7877577215582621254.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906915386.143852.16936177636106480724.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967122632.1823006.7487049517698562172.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021521420.640689.12747258780542678309.stgit@warthog.procyon.org.uk/ # v4

commit 3a11b3a86366ccbf0818b088ffecadf8b2d61177
Author: David Howells <dhowells@redhat.com>
Date:   Tue Sep 14 09:47:45 2021 +0100

    netfs: Pass more information on how to deal with a hole in the cache
    
    Pass more information to the cache on how to deal with a hole if it
    encounters one when trying to read from the cache.  Three options are
    provided:
    
     (1) NETFS_READ_HOLE_IGNORE.  Read the hole along with the data, assuming
         it to be a punched-out extent by the backing filesystem.
    
     (2) NETFS_READ_HOLE_CLEAR.  If there's a hole, erase the requested region
         of the cache and clear the read buffer.
    
     (3) NETFS_READ_HOLE_FAIL.  Fail the read if a hole is detected.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819612321.215744.9738308885948264476.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906914460.143852.6284247083607910189.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967119923.1823006.15637375885194297582.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021519762.640689.16994364383313159319.stgit@warthog.procyon.org.uk/ # v4

commit ed1235eb78a7421cd0ac2ad09e931f8f07ccdc7c
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 23:10:46 2021 +0100

    fscache: Provide a function to let the netfs update its coherency data
    
    Provide a function to let the netfs update its coherency data:
    
            void fscache_update_cookie(struct fscache_cookie *cookie,
                                       const void *aux_data,
                                       const loff_t *object_size);
    
    This will update the auxiliary data and/or the size of the object attached
    to a cookie if either pointer is not-NULL and flag that the disk needs to
    be updated.
    
    Note that fscache_unuse_cookie() also allows this to be done.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819610438.215744.4223265964131424954.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906913530.143852.18150303220217653820.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967117795.1823006.7493373142653442595.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021518440.640689.6369952464473039268.stgit@warthog.procyon.org.uk/ # v4

commit 8e7a867bb7309fbf47e8c2a68798b919fc02523f
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 23:06:16 2021 +0100

    fscache: Provide read/write stat counters for the cache
    
    Provide read/write stat counters for the cache backend to use.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819609532.215744.10821082637727410554.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906912598.143852.12960327989649429069.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967113830.1823006.3222957649202368162.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021517502.640689.6077928311710357342.stgit@warthog.procyon.org.uk/ # v4

commit cdf262f29488e6c3432911ec487ea41918fcbcd7
Author: David Howells <dhowells@redhat.com>
Date:   Thu Nov 11 23:14:29 2021 +0000

    fscache: Count data storage objects in a cache
    
    Count the data storage objects that are currently allocated in a cache.
    This is used to pin certain cache structures until cache withdrawal is
    complete.
    
    Three helpers are provided to manage and make use of the count:
    
     (1) void fscache_count_object(struct fscache_cache *cache);
    
         This should be called by the cache backend to note that an object has
         been allocated and attached to the cache.
    
     (2) void fscache_uncount_object(struct fscache_cache *cache);
    
         This should be called by the backend to note that an object has been
         destroyed.  This sends a wakeup event that allows cache withdrawal to
         proceed if it was waiting for that object.
    
     (3) void fscache_wait_for_objects(struct fscache_cache *cache);
    
         This can be used by the backend to wait for all outstanding cache
         object to be destroyed.
    
    Each cache's counter is displayed as part of /proc/fs/fscache/caches.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819608594.215744.1812706538117388252.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906911646.143852.168184059935530127.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967111846.1823006.9868154941573671255.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021516219.640689.4934796654308958158.stgit@warthog.procyon.org.uk/ # v4

commit d64f4554dd177c5891c02424a8d9e80590b55b35
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:06:34 2021 +0100

    fscache: Provide a means to begin an operation
    
    Provide a function to begin a read operation:
    
            int fscache_begin_read_operation(
                    struct netfs_cache_resources *cres,
                    struct fscache_cookie *cookie)
    
    This is primarily intended to be called by network filesystems on behalf of
    netfslib, but may also be called to use the I/O access functions directly.
    It attaches the resources required by the cache to cres struct from the
    supplied cookie.
    
    This holds access to the cache behind the cookie for the duration of the
    operation and forces cache withdrawal and cookie invalidation to perform
    synchronisation on the operation.  cres->inval_counter is set from the
    cookie at this point so that it can be compared at the end of the
    operation.
    
    Note that this does not guarantee that the cache state is fully set up and
    able to perform I/O immediately; looking up and creation may be left in
    progress in the background.  The operations intended to be called by the
    network filesystem, such as reading and writing, are expected to wait for
    the cookie to move to the correct state.
    
    This will, however, potentially sleep, waiting for a certain minimum state
    to be set or for operations such as invalidate to advance far enough that
    I/O can resume.
    
    
    Also provide a function for the cache to call to wait for the cache object
    to get to a state where it can be used for certain things:
    
            bool fscache_wait_for_operation(struct netfs_cache_resources *cres,
                                            enum fscache_want_stage stage);
    
    This looks at the cache resources provided by the begin function and waits
    for them to get to an appropriate stage.  There's a choice of wanting just
    some parameters (FSCACHE_WANT_PARAM) or the ability to do I/O
    (FSCACHE_WANT_READ or FSCACHE_WANT_WRITE).
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819603692.215744.146724961588817028.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906910672.143852.13856103384424986357.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967110245.1823006.2239170567540431836.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021513617.640689.16627329360866150606.stgit@warthog.procyon.org.uk/ # v4

commit d24af13e2e2358a602740c7817ea90da43d3e740
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:53:34 2021 +0100

    fscache: Implement cookie invalidation
    
    Add a function to invalidate the cache behind a cookie:
    
            void fscache_invalidate(struct fscache_cookie *cookie,
                                    const void *aux_data,
                                    loff_t size,
                                    unsigned int flags)
    
    This causes any cached data for the specified cookie to be discarded.  If
    the cookie is marked as being in use, a new cache object will be created if
    possible and future I/O will use that instead.  In-flight I/O should be
    abandoned (writes) or reconsidered (reads).  Each time it is called
    cookie->inval_counter is incremented and this can be used to detect
    invalidation at the end of an I/O operation.
    
    The coherency data attached to the cookie can be updated and the cookie
    size should be reset.  One flag is available, FSCACHE_INVAL_DIO_WRITE,
    which should be used to indicate invalidation due to a DIO write on a
    file.  This will temporarily disable caching for this cookie.
    
    Changes
    =======
    ver #2:
     - Should only change to inval state if can get access to cache.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819602231.215744.11206598147269491575.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906909707.143852.18056070560477964891.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967107447.1823006.5945029409592119962.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021512640.640689.11418616313147754172.stgit@warthog.procyon.org.uk/ # v4

commit 12bb21a29c19aae50cfad4e2bb5c943108f34a7d
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:53:34 2021 +0100

    fscache: Implement cookie user counting and resource pinning
    
    Provide a pair of functions to count the number of users of a cookie (open
    files, writeback, invalidation, resizing, reads, writes), to obtain and pin
    resources for the cookie and to prevent culling for the whilst there are
    users.
    
    The first function marks a cookie as being in use:
    
            void fscache_use_cookie(struct fscache_cookie *cookie,
                                    bool will_modify);
    
    The caller should indicate the cookie to use and whether or not the caller
    is in a context that may modify the cookie (e.g. a file open O_RDWR).
    
    If the cookie is not already resourced, fscache will ask the cache backend
    in the background to do whatever it needs to look up, create or otherwise
    obtain the resources necessary to access data.  This is pinned to the
    cookie and may not be culled, though it may be withdrawn if the cache as a
    whole is withdrawn.
    
    The second function removes the in-use mark from a cookie and, optionally,
    updates the coherency data:
    
            void fscache_unuse_cookie(struct fscache_cookie *cookie,
                                      const void *aux_data,
                                      const loff_t *object_size);
    
    If non-NULL, the aux_data buffer and/or the object_size will be saved into
    the cookie and will be set on the backing store when the object is
    committed.
    
    If this removes the last usage on a cookie, the cookie is placed onto an
    LRU list from which it will be removed and closed after a couple of seconds
    if it doesn't get reused.  This prevents resource overload in the cache -
    in particular it prevents it from holding too many files open.
    
    Changes
    =======
    ver #2:
     - Fix fscache_unuse_cookie() to use atomic_dec_and_lock() to avoid a
       potential race if the cookie gets reused before it completes the
       unusement.
     - Added missing transition to LRU_DISCARDING state.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819600612.215744.13678350304176542741.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906907567.143852.16979631199380722019.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967106467.1823006.6790864931048582667.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021511674.640689.10084988363699111860.stgit@warthog.procyon.org.uk/ # v4

commit 5d00e426f95e7ea036fec2a0aceb3f71d6dbdf92
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:53:34 2021 +0100

    fscache: Implement simple cookie state machine
    
    Implement a very simple cookie state machine to handle lookup,
    invalidation, withdrawal, relinquishment and, to be added later, commit on
    LRU discard.
    
    Three cache methods are provided: ->lookup_cookie() to look up and, if
    necessary, create a data storage object; ->withdraw_cookie() to free the
    resources associated with that object and potentially delete it; and
    ->prepare_to_write(), to do prepare for changes to the cached data to be
    modified locally.
    
    Changes
    =======
    ver #3:
     - Fix a race between LRU discard and relinquishment whereby the former
       would override the latter and thus the latter would never happen[1].
    
    ver #2:
     - Don't hold n_accesses elevated whilst cache is bound to a cookie, but
       rather add a flag that prevents the state machine from being queued when
       n_accesses reaches 0.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/599331.1639410068@warthog.procyon.org.uk/ [1]
    Link: https://lore.kernel.org/r/163819599657.215744.15799615296912341745.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906903925.143852.1805855338154353867.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967105456.1823006.14730395299835841776.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021510706.640689.7961423370243272583.stgit@warthog.procyon.org.uk/ # v4

commit 29f18e79fe7c5f8011befeda9be6b220a350f947
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:00:26 2021 +0100

    fscache: Add a function for a cache backend to note an I/O error
    
    Add a function to the backend API to note an I/O error in a cache.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819598741.215744.891281275151382095.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906901316.143852.15225412215771586528.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967100721.1823006.16435671567428949398.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021508840.640689.11902836226570620424.stgit@warthog.procyon.org.uk/ # v4

commit bfa22da3ed652aa15acd4246fa13a0de6dbe4a59
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:26:17 2021 +0100

    fscache: Provide and use cache methods to lookup/create/free a volume
    
    Add cache methods to lookup, create and remove a volume.
    
    Looking up or creating the volume requires the cache pinning for access;
    freeing the volume requires the volume pinning for access.  The
    ->acquire_volume() method is used to ask the cache backend to lookup and,
    if necessary, create a volume; the ->free_volume() method is used to free
    the resources for a volume.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819597821.215744.5225318658134989949.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906898645.143852.8537799955945956818.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967099771.1823006.1455197910571061835.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021507345.640689.4073511598838843040.stgit@warthog.procyon.org.uk/ # v4

commit 2e0c76aee25f33c482abda6224bd87732359354d
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:00:26 2021 +0100

    fscache: Implement functions add/remove a cache
    
    Implement functions to allow the cache backend to add or remove a cache:
    
     (1) Declare a cache to be live:
    
            int fscache_add_cache(struct fscache_cache *cache,
                                  const struct fscache_cache_ops *ops,
                                  void *cache_priv);
    
         Take a previously acquired cache cookie, set the operations table and
         private data and mark the cache open for access.
    
     (2) Withdraw a cache from service:
    
            void fscache_withdraw_cache(struct fscache_cache *cache);
    
         This marks the cache as withdrawn and thus prevents further
         cache-level and volume-level accesses.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819596022.215744.8799712491432238827.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906896599.143852.17049208999019262884.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967097870.1823006.3470041000971522030.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021505541.640689.1819714759326331054.stgit@warthog.procyon.org.uk/ # v4

commit a7733fb632722a2f085f9324f14783effe268ed3
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:53:34 2021 +0100

    fscache: Implement cookie-level access helpers
    
    Add a number of helper functions to manage access to a cookie, pinning the
    cache object in place for the duration to prevent cache withdrawal from
    removing it:
    
     (1) void fscache_init_access_gate(struct fscache_cookie *cookie);
    
         This function initialises the access count when a cache binds to a
         cookie.  An extra ref is taken on the access count to prevent wakeups
         while the cache is active.  We're only interested in the wakeup when a
         cookie is being withdrawn and we're waiting for it to quiesce - at
         which point the counter will be decremented before the wait.
    
         The FSCACHE_COOKIE_NACC_ELEVATED flag is set on the cookie to keep
         track of the extra ref in order to handle a race between
         relinquishment and withdrawal both trying to drop the extra ref.
    
     (2) bool fscache_begin_cookie_access(struct fscache_cookie *cookie,
                                          enum fscache_access_trace why);
    
         This function attempts to begin access upon a cookie, pinning it in
         place if it's cached.  If successful, it returns true and leaves a the
         access count incremented.
    
     (3) void fscache_end_cookie_access(struct fscache_cookie *cookie,
                                        enum fscache_access_trace why);
    
         This function drops the access count obtained by (2), permitting
         object withdrawal to take place when it reaches zero.
    
    A tracepoint is provided to track changes to the access counter on a
    cookie.
    
    Changes
    =======
    ver #2:
     - Don't hold n_accesses elevated whilst cache is bound to a cookie, but
       rather add a flag that prevents the state machine from being queued when
       n_accesses reaches 0.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819595085.215744.1706073049250505427.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906895313.143852.10141619544149102193.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967095980.1823006.1133648159424418877.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021503063.640689.8870918985269528670.stgit@warthog.procyon.org.uk/ # v4

commit e6acd3299badbfb5fb0231d42481d4f5dedf5599
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:26:17 2021 +0100

    fscache: Implement volume-level access helpers
    
    Add a pair of helper functions to manage access to a volume, pinning the
    volume in place for the duration to prevent cache withdrawal from removing
    it:
    
            bool fscache_begin_volume_access(struct fscache_volume *volume,
                                             enum fscache_access_trace why);
            void fscache_end_volume_access(struct fscache_volume *volume,
                                           enum fscache_access_trace why);
    
    The way the access gate on the volume works/will work is:
    
      (1) If the cache tests as not live (state is not FSCACHE_CACHE_IS_ACTIVE),
          then we return false to indicate access was not permitted.
    
      (2) If the cache tests as live, then we increment the volume's n_accesses
          count and then recheck the cache liveness, ending the access if it
          ceased to be live.
    
      (3) When we end the access, we decrement the volume's n_accesses and wake
          up the any waiters if it reaches 0.
    
      (4) Whilst the cache is caching, the volume's n_accesses is kept
          artificially incremented to prevent wakeups from happening.
    
      (5) When the cache is taken offline, the state is changed to prevent new
          accesses, the volume's n_accesses is decremented and we wait for it to
          become 0.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819594158.215744.8285859817391683254.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906894315.143852.5454793807544710479.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967095028.1823006.9173132503876627466.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021501546.640689.9631510472149608443.stgit@warthog.procyon.org.uk/ # v4

commit 23e12e285a6ab7320a8bceead29cfe13190a6e3c
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:00:26 2021 +0100

    fscache: Implement cache-level access helpers
    
    Add a pair of functions to pin/unpin a cache that we're wanting to do a
    high-level access to (such as creating or removing a volume):
    
            bool fscache_begin_cache_access(struct fscache_cache *cache,
                                            enum fscache_access_trace why);
            void fscache_end_cache_access(struct fscache_cache *cache,
                                          enum fscache_access_trace why);
    
    The way the access gate works/will work is:
    
     (1) If the cache tests as not live (state is not FSCACHE_CACHE_IS_ACTIVE),
         then we return false to indicate access was not permitted.
    
     (2) If the cache tests as live, then we increment the n_accesses count and
         then recheck the liveness, ending the access if it ceased to be live.
    
     (3) When we end the access, we decrement n_accesses and wake up the any
         waiters if it reaches 0.
    
     (4) Whilst the cache is caching, n_accesses is kept artificially
         incremented to prevent wakeups from happening.
    
     (5) When the cache is taken offline, the state is changed to prevent new
         accesses, n_accesses is decremented and we wait for n_accesses to
         become 0.
    
    Note that some of this is implemented in a later patch.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819593239.215744.7537428720603638088.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906893368.143852.14164004598465617981.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967093977.1823006.6967886507023056409.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021499995.640689.18286203753480287850.stgit@warthog.procyon.org.uk/ # v4

commit 7f3283aba39a0f395700c3b5defa4ec49d9914b3
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:53:34 2021 +0100

    fscache: Implement cookie registration
    
    Add functions to the fscache API to allow data file cookies to be acquired
    and relinquished by the network filesystem.  It is intended that the
    filesystem will create such cookies per-inode under a volume.
    
    To request a cookie, the filesystem should call:
    
            struct fscache_cookie *
            fscache_acquire_cookie(struct fscache_volume *volume,
                                   u8 advice,
                                   const void *index_key,
                                   size_t index_key_len,
                                   const void *aux_data,
                                   size_t aux_data_len,
                                   loff_t object_size)
    
    
    The filesystem must first have created a volume cookie, which is passed in
    here.  If it passes in NULL then the function will just return a NULL
    cookie.
    
    A binary key should be passed in index_key and is of size index_key_len.
    This is saved in the cookie and is used to locate the associated data in
    the cache.
    
    A coherency data buffer of size aux_data_len will be allocated and
    initialised from the buffer pointed to by aux_data.  This is used to
    validate cache objects when they're opened and is stored on disk with them
    when they're committed.  The data is stored in the cookie and will be
    updateable by various functions in later patches.
    
    The object_size must also be given.  This is also used to perform a
    coherency check and to size the backing storage appropriately.
    
    This function disallows a cookie from being acquired twice in parallel,
    though it will cause the second user to wait if the first is busy
    relinquishing its cookie.
    
    
    When a network filesystem has finished with a cookie, it should call:
    
            void
            fscache_relinquish_cookie(struct fscache_volume *volume,
                                      bool retire)
    
    If retire is true, any backing data will be discarded immediately.
    
    Changes
    =======
    ver #3:
     - fscache_hash()'s size parameter is now in bytes.  Use __le32 as the unit
       to round up to.
     - When comparing cookies, simply see if the attributes are the same rather
       than subtracting them to produce a strcmp-style return[1].
     - Add a check to see if the cookie is still hashed at the point of
       freeing.
    
    ver #2:
     - Don't hold n_accesses elevated whilst cache is bound to a cookie, but
       rather add a flag that prevents the state machine from being queued when
       n_accesses reaches 0.
     - Remove the unused cookie pointer field from the fscache_acquire
       tracepoint.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/CAHk-=whtkzB446+hX0zdLsdcUJsJ=8_-0S1mE_R+YurThfUbLA@mail.gmail.com/ [1]
    Link: https://lore.kernel.org/r/163819590658.215744.14934902514281054323.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906891983.143852.6219772337558577395.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967088507.1823006.12659006350221417165.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021498432.640689.12743483856927722772.stgit@warthog.procyon.org.uk/ # v4

commit 62ab63352350e881ae693a8236b35d7d0516c78b
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:26:17 2021 +0100

    fscache: Implement volume registration
    
    Add functions to the fscache API to allow volumes to be acquired and
    relinquished by the network filesystem.  A volume is an index of data
    storage cache objects.  A volume is represented by a volume cookie in the
    API.  A filesystem would typically create a volume for a superblock and
    then create per-inode cookies within it.
    
    To request a volume, the filesystem calls:
    
            struct fscache_volume *
            fscache_acquire_volume(const char *volume_key,
                                   const char *cache_name,
                                   const void *coherency_data,
                                   size_t coherency_len)
    
    The volume_key is a printable string used to match the volume in the cache.
    It should not contain any '/' characters.  For AFS, for example, this would
    be "afs,<cellname>,<volume_id>", e.g. "afs,example.com,523001".
    
    The cache_name can be NULL, but if not it should be a string indicating the
    name of the cache to use if there's more than one available.
    
    The coherency data, if given, is an arbitrarily-sized blob that's attached
    to the volume and is compared when the volume is looked up.  If it doesn't
    match, the old volume is judged to be out of date and it and everything
    within it is discarded.
    
    Acquiring a volume twice concurrently is disallowed, though the function
    will wait if an old volume cookie is being relinquishing.
    
    
    When a network filesystem has finished with a volume, it should return the
    volume cookie by calling:
    
            void
            fscache_relinquish_volume(struct fscache_volume *volume,
                                      const void *coherency_data,
                                      bool invalidate)
    
    If invalidate is true, the entire volume will be discarded; if false, the
    volume will be synced and the coherency data will be updated.
    
    Changes
    =======
    ver #4:
     - Removed an extraneous param from kdoc on fscache_relinquish_volume()[3].
    
    ver #3:
     - fscache_hash()'s size parameter is now in bytes.  Use __le32 as the unit
       to round up to.
     - When comparing cookies, simply see if the attributes are the same rather
       than subtracting them to produce a strcmp-style return[2].
     - Make the coherency data an arbitrary blob rather than a u64, but don't
       store it for the moment.
    
    ver #2:
     - Fix error check[1].
     - Make a fscache_acquire_volume() return errors, including EBUSY if a
       conflicting volume cookie already exists.  No error is printed now -
       that's left to the netfs.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/20211203095608.GC2480@kili/ [1]
    Link: https://lore.kernel.org/r/CAHk-=whtkzB446+hX0zdLsdcUJsJ=8_-0S1mE_R+YurThfUbLA@mail.gmail.com/ [2]
    Link: https://lore.kernel.org/r/20211220224646.30e8205c@canb.auug.org.au/ [3]
    Link: https://lore.kernel.org/r/163819588944.215744.1629085755564865996.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906890630.143852.13972180614535611154.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967086836.1823006.8191672796841981763.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021495816.640689.4403156093668590217.stgit@warthog.procyon.org.uk/ # v4

commit 9549332df4ed4e761a1d41c83f2c25d28bb22431
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:00:26 2021 +0100

    fscache: Implement cache registration
    
    Implement a register of caches and provide functions to manage it.
    
    Two functions are provided for the cache backend to use:
    
     (1) Acquire a cache cookie:
    
            struct fscache_cache *fscache_acquire_cache(const char *name)
    
         This gets the cache cookie for a cache of the specified name and moves
         it to the preparation state.  If a nameless cache cookie exists, that
         will be given this name and used.
    
     (2) Relinquish a cache cookie:
    
            void fscache_relinquish_cache(struct fscache_cache *cache);
    
         This relinquishes a cache cookie, cleans it and makes it available if
         it's still referenced by a network filesystem.
    
    Note that network filesystems don't deal with cache cookies directly, but
    rather go straight to the volume registration.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819587157.215744.13523139317322503286.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906889665.143852.10378009165231294456.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967085081.1823006.2218944206363626210.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021494847.640689.10109692261640524343.stgit@warthog.procyon.org.uk/ # v4

commit e8a07c9d22afdace966353231d0273d29efe0890
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 15:45:28 2021 +0100

    fscache: Implement a hash function
    
    Implement a function to generate hashes.  It needs to be stable over time
    and endianness-independent as the hashes will appear on disk in future
    patches.  It can assume that its input is a multiple of four bytes in size
    and alignment.
    
    This is borrowed from the VFS and simplified.  le32_to_cpu() is added to
    make it endianness-independent.
    
    Changes
    =======
    ver #3:
     - Read the data being hashed in an endianness-independent way[1].
     - Change the size parameter to be in bytes rather than words.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/CAHk-=whtkzB446+hX0zdLsdcUJsJ=8_-0S1mE_R+YurThfUbLA@mail.gmail.com [1]
    Link: https://lore.kernel.org/r/163819586113.215744.1699465806130102367.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906888735.143852.10944614318596881429.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967082342.1823006.8915671045444488742.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021493624.640689.9990442668811178628.stgit@warthog.procyon.org.uk/ # v4

commit 1e1236b841166f1d2daf36fdf6bb3e656bc5f5ca
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:34:41 2021 +0100

    fscache: Introduce new driver
    
    Introduce basic skeleton of the new, rewritten fscache driver.
    
    Changes
    =======
    ver #3:
     - Use remove_proc_subtree(), not remove_proc_entry() to remove a populated
       dir.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819584034.215744.4290533472390439030.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906887770.143852.3577888294989185666.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967080039.1823006.5702921801104057922.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021491014.640689.4292699878317589512.stgit@warthog.procyon.org.uk/ # v4

commit a39c41b853ee51f4dcd19f5556f860ae8e2f23d3
Author: David Howells <dhowells@redhat.com>
Date:   Wed Oct 20 14:30:37 2021 +0100

    netfs: Pass a flag to ->prepare_write() to say if there's no alloc'd space
    
    Pass a flag to ->prepare_write() to indicate if there's definitely no
    space allocated in the cache yet (for instance if we've already checked as
    we were asked to do a read).
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819583123.215744.12783808230464471417.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906886835.143852.6689886781122679769.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967079100.1823006.12889542712309574359.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021489334.640689.3131206613015409076.stgit@warthog.procyon.org.uk/ # v4

commit 9e1aa6b8f484dde5ada1212092d20ea3f55c24e8
Author: David Howells <dhowells@redhat.com>
Date:   Tue Oct 12 12:05:27 2021 +0100

    netfs: Display the netfs inode number in the netfs_read tracepoint
    
    Display the netfs inode number in the netfs_read tracepoint so that this
    can be used to correlate with the cachefiles_prep_read tracepoint.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819581097.215744.17476611915583897051.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906885903.143852.12229407815154182247.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967078164.1823006.15286989199782861123.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021487412.640689.7544388469390936443.stgit@warthog.procyon.org.uk/ # v4

commit 2cee6fbb7f01bcb25f11ef1439e89a29de4c0c1d
Author: David Howells <dhowells@redhat.com>
Date:   Mon Oct 25 21:53:44 2021 +0100

    fscache: Remove the contents of the fscache driver, pending rewrite
    
    Remove the code that comprises the fscache driver as it's going to be
    substantially rewritten, with the majority of the code being erased in the
    rewrite.
    
    A small piece of linux/fscache.h is left as that is #included by a bunch of
    network filesystems.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819578724.215744.18210619052245724238.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906884814.143852.6727245089843862889.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967077097.1823006.1377665951499979089.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021485548.640689.13876080567388696162.stgit@warthog.procyon.org.uk/ # v4

commit 850cba069c266d6f31b81c5a199052a3482a63fc
Author: David Howells <dhowells@redhat.com>
Date:   Sun Oct 31 12:58:05 2021 +0000

    cachefiles: Delete the cachefiles driver pending rewrite
    
    Delete the code from the cachefiles driver to make it easier to rewrite and
    resubmit in a logical manner.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819577641.215744.12718114397770666596.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906883770.143852.4149714614981373410.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967076066.1823006.7175712134577687753.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021483619.640689.7586546280515844702.stgit@warthog.procyon.org.uk/ # v4

commit 01491a756578d8602dfdfc79f2638c519bfdadb7
Author: David Howells <dhowells@redhat.com>
Date:   Mon Oct 25 21:41:26 2021 +0100

    fscache, cachefiles: Disable configuration
    
    Disable fscache and cachefiles in Kconfig whilst it is rewritten.
    
    Signed-off-by: David Howells <dhowells@redhat.com>
    Reviewed-by: Jeff Layton <jlayton@kernel.org>
    cc: linux-cachefs@redhat.com
    Link: https://lore.kernel.org/r/163819576672.215744.12444272479560406780.stgit@warthog.procyon.org.uk/ # v1
    Link: https://lore.kernel.org/r/163906882835.143852.11073015983885872901.stgit@warthog.procyon.org.uk/ # v2
    Link: https://lore.kernel.org/r/163967075113.1823006.277316290062782998.stgit@warthog.procyon.org.uk/ # v3
    Link: https://lore.kernel.org/r/164021481179.640689.2004199594774033658.stgit@warthog.procyon.org.uk/ # v4

commit b9f9dbad0bd1c302d357fdd327c398f51f5fc2b1
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:17:27 2022 +0300

    Bluetooth: hci_sock: fix endian bug in hci_sock_setsockopt()
    
    This copies a u16 into the high bits of an int, which works on a big
    endian system but not on a little endian system.
    
    Fixes: 09572fca7223 ("Bluetooth: hci_sock: Add support for BT_{SND,RCV}BUF")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 2b70d4f9b20635ac328836e50d183632e1930f94
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Fri Jan 7 10:16:44 2022 +0300

    Bluetooth: L2CAP: uninitialized variables in l2cap_sock_setsockopt()
    
    The "opt" variable is a u32, but on some paths only the top bytes
    were initialized and the others contained random stack data.
    
    Fixes: a7b75c5a8c41 ("net: pass a sockptr_t into ->setsockopt")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 4fac8a7ac80b18068fce4feb2376e41c48d67c31
Author: Sai Teja Aluvala <quic_saluvala@quicinc.com>
Date:   Fri Jan 7 11:50:53 2022 +0530

    Bluetooth: btqca: sequential validation
    
    Added Sequential validation support & patch command config
    
    Signed-off-by: Sai Teja Aluvala <quic_saluvala@quicinc.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 1cd563ebd0dc062127a85e84f934f4c697bb43ef
Author: Aaron Ma <aaron.ma@canonical.com>
Date:   Fri Jan 7 11:59:09 2022 +0800

    Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0
    
    Add an ID of Qualcomm Bluetooth SoC WCN6855.
    
    T:  Bus=05 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#=  4 Spd=12   MxCh= 0
    D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=0489 ProdID=e0d0 Rev= 0.01
    C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
    I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
    E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
    E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
    I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
    I:* If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
    I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
    I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
    I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
    I:  If#= 1 Alt= 6 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  63 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  63 Ivl=1ms
    I:  If#= 1 Alt= 7 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    E:  Ad=83(I) Atr=01(Isoc) MxPS=  65 Ivl=1ms
    E:  Ad=03(O) Atr=01(Isoc) MxPS=  65 Ivl=1ms
    
    Signed-off-by: Aaron Ma <aaron.ma@canonical.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 95655456e7cee858a23793f67025765b4c4c227b
Author: Tedd Ho-Jeong An <tedd.an@intel.com>
Date:   Thu Jan 6 16:34:54 2022 -0800

    Bluetooth: btintel: Fix broken LED quirk for legacy ROM devices
    
    This patch fixes the broken LED quirk for Intel legacy ROM devices.
    To fix the LED issue that doesn't turn off immediately, the host sends
    the SW RFKILL command while shutting down the interface and it puts the
    devices in SW RFKILL state.
    
    Once the device is in SW RFKILL state, it can only accept HCI_Reset to
    exit from the SW RFKILL state. This patch checks the quirk for broken
    LED and sends the HCI_Reset before sending the HCI_Intel_Read_Version
    command.
    
    The affected legacy ROM devices are
     - 8087:07dc
     - 8087:0a2a
     - 8087:0aa7
    
    Fixes: ffcba827c0a1d ("Bluetooth: btintel: Fix the LED is not turning off immediately")
    Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 1b1f98dd70dcfd25476adabcbe72484312e879f7
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Jan 7 10:08:51 2022 +0800

    ALSA: intel_hdmi: Check for error num after setting mask
    
    To maintain the consistency of the code, it should be better to add the
    sanity check after calling dma_set_mask_and_coherent(), like
    tegra_pcm_dma_allocate() in `sound/soc/tegra/tegra_pcm.c`.
    
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220107020851.3095591-1-jiasheng@iscas.ac.cn
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit e4a3d6a6a19a88cd021a3f4332c1c9b68faa8ae0
Merge: 8947c390b2202 0dbc416218751
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 6 20:06:32 2022 -0800

    Merge branch '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue
    
    Tony Nguyen says:
    
    ====================
    100GbE Intel Wired LAN Driver Updates 2022-01-06
    
    Victor adds restoring of advanced rules after reset.
    
    Wojciech improves usage of switchdev control VSI by utilizing the
    device's advanced rules for forwarding.
    
    Christophe Jaillet removes some unneeded calls to zero bitmaps, changes
    some bitmap operations that don't need to be atomic, and converts a
    kfree() to a more appropriate bitmap_free().
    
    * '100GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue:
      ice: Use bitmap_free() to free bitmap
      ice: Optimize a few bitmap operations
      ice: Slightly simply ice_find_free_recp_res_idx
      ice: improve switchdev's slow-path
      ice: replay advanced rules after reset
    ====================
    
    Link: https://lore.kernel.org/r/20220106183013.3777622-1-anthony.l.nguyen@intel.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 8947c390b22021cfcee3abe83e52acb38cc308be
Merge: 42379b9542283 4735402173e6e
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 6 20:00:48 2022 -0800

    Merge branch 'mlxsw-add-spectrum-4-support'
    
    Ido Schimmel says:
    
    ====================
    mlxsw: Add Spectrum-4 support
    
    This patchset adds Spectrum-4 support in mlxsw. It builds on top of a
    previous patchset merged in commit 10184da91666 ("Merge branch
    'mlxsw-Spectrum-4-prep'") and makes two additional changes before adding
    Spectrum-4 support.
    
    Patchset overview:
    
    Patches #1-#2 add a few Spectrum-4 specific variants of existing ACL
    keys. The new variants are needed because the size of certain key
    elements (e.g., local port) was increased in Spectrum-4.
    
    Patches #3-#6 are preparations.
    
    Patch #7 implements the Spectrum-4 variant of the Bloom filter hash
    function. The Bloom filter is used to optimize ACL lookups by
    potentially skipping certain lookups if they are guaranteed not to
    match. See additional info in merge commit ae6750e0a5ef ("Merge branch
    'mlxsw-spectrum_acl-Add-Bloom-filter-support'").
    
    Patch #8 finally adds Spectrum-4 support.
    ====================
    
    Link: https://lore.kernel.org/r/20220106160652.821176-1-idosch@nvidia.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4735402173e6eed18d7e04cfc4bc358d8b2965db
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:52 2022 +0200

    mlxsw: spectrum: Extend to support Spectrum-4 ASIC
    
    Extend existing driver for Spectrum, Spectrum-2 and Spectrum-3 ASICs
    to support Spectrum-4 ASIC as well.
    
    Currently there is no released firmware version for Spectrum-4, so the
    driver is not enforcing a minimum version.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 852ee4191dd2046203c2fece6a9402ce28118f80
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:51 2022 +0200

    mlxsw: spectrum_acl_bloom_filter: Add support for Spectrum-4 calculation
    
    Spectrum-4 will calculate hash function for bloom filter differently
    from the existing ASICs.
    
    First, two hash functions will be used to calculate 16 bits result.
    The final result will be combination of the two results - 6 bits which
    are result of CRC-6 will be used as MSB and 10 bits which are result of
    CRC-10 will be used as LSB.
    
    Second, while in Spectrum{2,3}, there is a padding in each chunk, so the
    chunks use a sequence of whole bytes, in Spectrum-4 there is no padding,
    so each chunk use 20 bytes minus 2 bits, so it is necessary to align the
    chunks to be without holes.
    
    Add dedicated 'mlxsw_sp_acl_bf_ops' for Spectrum-4 and add the required
    tables for CRC calculations.
    
    All the details are documented as part of the code for future use.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 58723d2f77717373d44721a2c65f8af5917102b7
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:50 2022 +0200

    mlxsw: Add operations structure for bloom filter calculation
    
    Spectrum-4 will calculate hash function for bloom filter differently from
    the existing ASICs.
    
    There are two changes:
    1. Instead of using one hash function to calculate 16 bits output (CRC-16),
       two functions will be used.
    2. The chunks will be built differently, without padding.
    
    As preparation for support of Spectrum-4 bloom filter, add 'ops'
    structure to allow handling different calculation for different ASICs.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 29409f363e2dfdab41bb2f3019116a0a585e8d0b
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:49 2022 +0200

    mlxsw: spectrum_acl_bloom_filter: Rename Spectrum-2 specific objects for future use
    
    Spectrum-4 will calculate hash function for bloom filter differently from
    the existing ASICs.
    
    There are two changes:
    1. Instead of using one hash function to calculate 16 bits output (CRC-16),
       two functions will be used.
    2. The chunks will be built differently, without padding.
    
    As preparation for support of Spectrum-4 bloom filter, rename CRC table
    to include "sp2" prefix and "crc16", as next patch will add two additional
    tables. In addition, rename all the dedicated functions and defines for
    Spectrum-{2,3} to include "sp2" prefix.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5d5c3ba9e4121b7738d10be3825f4d9a5a1d80ef
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:48 2022 +0200

    mlxsw: spectrum_acl_bloom_filter: Make mlxsw_sp_acl_bf_key_encode() more flexible
    
    Spectrum-4 will calculate hash function for bloom filter differently from
    the existing ASICs.
    
    One of the changes is related to the way that the chunks will be build -
    without padding.
    
    As preparation for support of Spectrum-4 bloom filter, make
    mlxsw_sp_acl_bf_key_encode() more flexible, so it will be able to use it
    for Spectrum-4 as well.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4711671297ecfe5a5e9976f449c6161133f5ebb1
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:47 2022 +0200

    mlxsw: spectrum_acl_bloom_filter: Reorder functions to make the code more aesthetic
    
    Currently, mlxsw_sp_acl_bf_rule_count_index_get() is implemented before
    mlxsw_sp_acl_bf_index_get() but is used after it.
    
    Adding a new function for Spectrum-4 would make them further apart still.
    Fix by moving them around.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Reviewed-by: Petr Machata <petrm@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 07ff135958dd293988f21ca74c51499a8bb90f88
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:46 2022 +0200

    mlxsw: Introduce flex key elements for Spectrum-4
    
    Spectrum-4 ASIC will support more virtual routers and local ports
    compared to the existing ASICs. Therefore, the virtual router and local
    port ACL key elements need to be increased.
    
    Introduce new key elements for Spectrum-4 to be aligned with the elements
    used already for other Spectrum ASICs.
    
    The key blocks layout is the same for Spectrum-4, so use the existing
    code for encode_block() and clear_block(), just create separate blocks.
    
    Note that size of `VIRT_ROUTER_MSB` is 4 bits in Spectrum-4,
    therefore declare it using `MLXSW_AFK_ELEMENT_INST_U32()`, in order to
    be able to set `.avoid_size_check` to true.
    Otherwise, `mlxsw_afk_blocks_check()` will fail and warn.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 6d5d8ebb881c425df10980c0188f7495caf2232f
Author: Amit Cohen <amcohen@nvidia.com>
Date:   Thu Jan 6 18:06:45 2022 +0200

    mlxsw: Rename virtual router flex key element
    
    In Spectrum-4, the size of the virtual router ACL key element increased
    from 11 bits to 12 bits.
    
    In order to reuse the existing virtual router ACL key element
    enumerators for Spectrum-4, rename 'VIRT_ROUTER_8_10' and
    'VIRT_ROUTER_0_7' to 'VIRT_ROUTER_MSB' and 'VIRT_ROUTER_LSB',
    respectively.
    
    No functional changes intended.
    
    Signed-off-by: Amit Cohen <amcohen@nvidia.com>
    Signed-off-by: Ido Schimmel <idosch@nvidia.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 42379b9542283bcb86ceedb245ff644d6f59037d
Merge: 257367c0c9d80 d1a9b84183e81
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 6 19:56:31 2022 -0800

    Merge branch 'dpaa2-eth-small-cleanup'
    
    Ioana Ciornei says:
    
    ====================
    dpaa2-eth: small cleanup
    
    These 3 patches are just part of a small cleanup on the dpaa2-eth and
    the dpaa2-switch drivers.
    
    In case we are hitting a case in which the fwnode of the root dprc
    device we initiate a deferred probe. On the dpaa2-switch side, if we are
    on the remove path, make sure that we check for a non-NULL pointer
    before accessing the port private structure.
    ====================
    
    Link: https://lore.kernel.org/r/20220106135905.81923-1-ioana.ciornei@nxp.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit d1a9b84183e818c6c3540a454d6ad278b56718b2
Author: Ioana Ciornei <ioana.ciornei@nxp.com>
Date:   Thu Jan 6 15:59:05 2022 +0200

    dpaa2-switch: check if the port priv is valid
    
    Before accessing the port private structure make sure that there is
    still a non-NULL pointer there. A NULL pointer access can happen when we
    are on the remove path, some switch ports are unregistered and some are
    in the process of unregistering.
    
    Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4e30e98c4b4c8c3bd2ff048e4f4bc74c8948a9fb
Author: Ioana Ciornei <ioana.ciornei@nxp.com>
Date:   Thu Jan 6 15:59:04 2022 +0200

    dpaa2-mac: return -EPROBE_DEFER from dpaa2_mac_open in case the fwnode is not set
    
    We could get into a situation when the fwnode of the parent device is
    not yet set because its probe didn't yet finish. When this happens, any
    caller of the dpaa2_mac_open() will not have the fwnode available, thus
    cause problems at the PHY connect time.
    
    Avoid this by just returning -EPROBE_DEFER from the dpaa2_mac_open when
    this happens.
    
    Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5b1e38c0792cc7a44997328de37d393f81b2501a
Author: Robert-Ionut Alexa <robert-ionut.alexa@nxp.com>
Date:   Thu Jan 6 15:59:03 2022 +0200

    dpaa2-mac: bail if the dpmacs fwnode is not found
    
    The parent pointer node handler must be declared with a NULL
    initializer. Before using it, a check must be performed to make
    sure that a valid address has been assigned to it.
    
    Signed-off-by: Robert-Ionut Alexa <robert-ionut.alexa@nxp.com>
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 5f21d7d283dd82865bdb0123795b3accf0d42b67
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Dec 31 09:40:36 2021 +0800

    crypto: af_alg - rewrite NULL pointer check
    
    Because of the possible alloc failure of the alloc_page(), it could
    return NULL pointer.
    And there is a check below the sg_assign_page().
    But it will be more logical to move the NULL check before the
    sg_assign_page().
    
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

commit dd827abe296fe4249b2f8c9b95f72f814ea8348c
Author: Zizhuang Deng <sunsetdzz@gmail.com>
Date:   Thu Dec 30 15:03:31 2021 +0800

    lib/mpi: Add the return value check of kcalloc()
    
    Add the return value check of kcalloc() to avoid potential
    NULL ptr dereference.
    
    Fixes: a8ea8bdd9df9 ("lib/mpi: Extend the MPI library")
    Signed-off-by: Zizhuang Deng <sunsetdzz@gmail.com>
    Reviewed-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
    Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

commit ec97d23c8e22c96e8c9cad7d3f93d593abfc8b06
Author: Sam Shih <sam.shih@mediatek.com>
Date:   Fri Dec 17 20:11:48 2021 +0800

    clk: mediatek: add mt7986 clock support
    
    Add MT7986 clock support, include topckgen, apmixedsys,
    infracfg, and ethernet subsystem clocks.
    
    Signed-off-by: Sam Shih <sam.shih@mediatek.com>
    Link: https://lore.kernel.org/r/20211217121148.6753-4-sam.shih@mediatek.com
    Reviewed-by: Ryder Lee <ryder.lee@kernel.org>
    [sboyd@kernel.org: Fix typos in Kconfig, there are more existing typos
    from where they were copied from of but whatever]
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 29507144c99814cd5e1ed9873db21ffc634f6c95
Merge: 36595d8ad46d9 23c54263efd7c
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 6 18:37:44 2022 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf
    
    Pablo Neira Ayuso says:
    
    ====================
    Netfilter fixes for net
    
    The following patchset contains Netfilter fixes for net:
    
    1) Refcount leak in ipt_CLUSTERIP rule loading path, from Xin Xiong.
    
    2) Use socat in netfilter selftests, from Hangbin Liu.
    
    3) Skip layer checksum 4 update for IP fragments.
    
    4) Missing allocation of pcpu scratch maps on clone in
       nft_set_pipapo, from Florian Westphal.
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf:
      netfilter: nft_set_pipapo: allocate pcpu scratch maps on clone
      netfilter: nft_payload: do not update layer 4 checksum when mangling fragments
      selftests: netfilter: switch to socat for tests using -q option
      netfilter: ipt_CLUSTERIP: fix refcount leak in clusterip_tg_check()
    ====================
    
    Link: https://lore.kernel.org/r/20220106215139.170824-1-pablo@netfilter.org
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 4470c830f9791203e7514c6b4d3a0df194e3ee0d
Author: Sam Shih <sam.shih@mediatek.com>
Date:   Fri Dec 17 20:11:47 2021 +0800

    clk: mediatek: add mt7986 clock IDs
    
    Add MT7986 clock dt-bindings, include topckgen, apmixedsys,
    infracfg, and ethernet subsystem clocks.
    
    Signed-off-by: Sam Shih <sam.shih@mediatek.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20211217121148.6753-3-sam.shih@mediatek.com
    Reviewed-by: Ryder Lee <ryder.lee@kernel.org>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 261446b2653e7b9d594f1de764691477775e2f07
Author: Sam Shih <sam.shih@mediatek.com>
Date:   Fri Dec 17 20:11:46 2021 +0800

    dt-bindings: clock: mediatek: document clk bindings for mediatek mt7986 SoC
    
    This patch adds the binding documentation for topckgen, apmixedsys,
    infracfg, and ethernet subsystem clocks.
    
    Signed-off-by: Sam Shih <sam.shih@mediatek.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20211217121148.6753-2-sam.shih@mediatek.com
    Reviewed-by: Ryder Lee <ryder.lee@kernel.org>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit d95abcab7b4aef11b29a5342b11fa60fd211929f
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Date:   Mon Jan 3 15:37:12 2022 +0100

    clk: mediatek: clk-gate: Use regmap_{set/clear}_bits helpers
    
    Appropriately change calls to regmap_update_bits() with regmap_set_bits()
    and regmap_clear_bits() for improved readability.
    
    Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Link: https://lore.kernel.org/r/20220103143712.46675-2-angelogioacchino.delregno@collabora.com
    Reviewed-by: Chen-Yu Tsai <wenst@chromium.org>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 4233463866796affc6674888e4cbaa24e0ff7965
Author: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Date:   Mon Jan 3 15:37:11 2022 +0100

    clk: mediatek: clk-gate: Shrink by adding clockgating bit check helper
    
    Add a clockgating bit check helper and use it in functions
    mtk_cg_bit_is_cleared(), mtk_cg_bit_is_set() to shrink the
    file size.
    
    Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
    Link: https://lore.kernel.org/r/20220103143712.46675-1-angelogioacchino.delregno@collabora.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 257367c0c9d800ef3065b440161596896e179038
Merge: 710ad98c363a6 eff14fcd032bc
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Thu Jan 6 18:07:25 2022 -0800

    Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next
    
    Alexei Starovoitov says:
    
    ====================
    pull-request: bpf-next 2022-01-06
    
    We've added 41 non-merge commits during the last 2 day(s) which contain
    a total of 36 files changed, 1214 insertions(+), 368 deletions(-).
    
    The main changes are:
    
    1) Various fixes in the verifier, from Kris and Daniel.
    
    2) Fixes in sockmap, from John.
    
    3) bpf_getsockopt fix, from Kuniyuki.
    
    4) INET_POST_BIND fix, from Menglong.
    
    5) arm64 JIT fix for bpf pseudo funcs, from Hou.
    
    6) BPF ISA doc improvements, from Christoph.
    
    * https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next: (41 commits)
      bpf: selftests: Add bind retry for post_bind{4, 6}
      bpf: selftests: Use C99 initializers in test_sock.c
      net: bpf: Handle return value of BPF_CGROUP_RUN_PROG_INET{4,6}_POST_BIND()
      bpf/selftests: Test bpf_d_path on rdonly_mem.
      libbpf: Add documentation for bpf_map batch operations
      selftests/bpf: Don't rely on preserving volatile in PT_REGS macros in loop3
      xdp: Add xdp_do_redirect_frame() for pre-computed xdp_frames
      xdp: Move conversion to xdp_frame out of map functions
      page_pool: Store the XDP mem id
      page_pool: Add callback to init pages when they are allocated
      xdp: Allow registering memory model without rxq reference
      samples/bpf: xdpsock: Add timestamp for Tx-only operation
      samples/bpf: xdpsock: Add time-out for cleaning Tx
      samples/bpf: xdpsock: Add sched policy and priority support
      samples/bpf: xdpsock: Add cyclic TX operation capability
      samples/bpf: xdpsock: Add clockid selection support
      samples/bpf: xdpsock: Add Dest and Src MAC setting for Tx-only operation
      samples/bpf: xdpsock: Add VLAN support for Tx-only operation
      libbpf 1.0: Deprecate bpf_object__find_map_by_offset() API
      libbpf 1.0: Deprecate bpf_map__is_offload_neutral()
      ...
    ====================
    
    Link: https://lore.kernel.org/r/20220107013626.53943-1-alexei.starovoitov@gmail.com
    Signed-off-by: Jakub Kicinski <kuba@kernel.org>

commit 1fdaaa13b44fdcbe3b6bed9cf5b67f9efac50610
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Sun Dec 12 23:35:27 2021 +0530

    clk: x86: Fix clk_gate_flags for RV_CLK_GATE
    
    In newer SoC we have to clear bit for disabling 48MHz oscillator
    clock gate. Remove CLK_GATE_SET_TO_DISABLE flag for proper enable
    and disable of 48MHz clock.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
    Link: https://lore.kernel.org/r/20211212180527.1641362-6-AjitKumar.Pandey@amd.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit c33917b439e0cd24182e40726e18104f66d48933
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Sun Dec 12 23:35:26 2021 +0530

    clk: x86: Use dynamic con_id string during clk registration
    
    Replace hard coded con_id string with fch_data->name. We have clk
    consumers looking up with different clock names, hence use dynamic
    con_id string during clk lookup registration. fch_data->name will
    be initialized in acpi driver based on fmw property value.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
    Link: https://lore.kernel.org/r/20211212180527.1641362-5-AjitKumar.Pandey@amd.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 7fdb98e8a768b3ccc05494d3ea4436047f512b9d
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Sun Dec 12 23:35:25 2021 +0530

    ACPI: APD: Add a fmw property clk-name
    
    Add a new device property to fetch clk-name from firmware.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
    Link: https://lore.kernel.org/r/20211212180527.1641362-4-AjitKumar.Pandey@amd.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 3663f26b389b3951426971b44bb9312fdff0efec
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Sun Dec 12 23:35:24 2021 +0530

    drivers: acpi: acpi_apd: Remove unused device property "is-rv"
    
    Initially "is-rv" device property is added for 48MHz fixed clock
    support on Raven or RV architecture. It's unused now as we moved
    to pci device_id based selection to extend such support on other
    architectures. This change removed unused code from acpi driver.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
    Link: https://lore.kernel.org/r/20211212180527.1641362-3-AjitKumar.Pandey@amd.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 65ab884ac9cd8454435b5159ade540004f1a24fe
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Sun Dec 12 23:35:23 2021 +0530

    x86: clk: clk-fch: Add support for newer family of AMD's SOC
    
    FCH controller clock configuration slightly differs across AMD's
    SOC architectures. Newer family of SOC only support a 48MHz fix
    clock while stoney SOC family has a clk_mux to choose 48MHz and
    25 MHz clk. At present fixed clk support is only enabled for RV
    architecture using "is-rv" device property initialized from boot
    loader. This limit 48MHz fixed clock gate support to RV platform
    unless we add similar device property in boot loader for other
    architectures.
    
    Add pci_device_id table with Stoney platform id and replace "is-rv"
    device property check with pci id match to add clk mux support with
    25MHz and 48MHz clk support based on clk mux selection. This enable
    48Mhz fixed fch clock support by default on all newer SOC's except
    stoney. Also replace RV with FIXED as a generic naming conventions
    across all platforms and changed module description.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Reviewed-by: Mario Limonciello <Mario.Limonciello@amd.com>
    Link: https://lore.kernel.org/r/20211212180527.1641362-2-AjitKumar.Pandey@amd.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit b5bc83bb70a5ca8fc090de3221fd8f1d4400241a
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Mon Dec 20 19:33:19 2021 +0000

    clk: ingenic: Add MDMA and BDMA clocks
    
    The Ingenic JZ4760 and JZ4770 both have an extra DMA core named BDMA
    dedicated to the NAND and BCH controller, but which can also do
    memory-to-memory transfers. The JZ4760 additionally has a DMA core named
    MDMA dedicated to memory-to-memory transfers. The programming manual for
    the JZ4770 does have a bit for a MDMA clock, but does not seem to have
    the hardware wired in.
    
    Add the BDMA and MDMA clocks to the JZ4760 CGU code, and the BDMA clock
    to the JZ4770 code, so that the BDMA and MDMA controllers can be used.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Link: https://lore.kernel.org/r/20211220193319.114974-3-paul@crapouillou.net
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit 51d04bcfb82a005d38b6f1011dc04a810d359aea
Author: Paul Cercueil <paul@crapouillou.net>
Date:   Mon Dec 20 19:33:18 2021 +0000

    dt-bindings: clk/ingenic: Add MDMA and BDMA clocks
    
    The Ingenic JZ4760 and JZ4770 both have an extra DMA core named BDMA
    dedicated to the NAND and BCH controller, but which can also do
    memory-to-memory transfers. The JZ4760 additionally has a DMA core named
    MDMA dedicated to memory-to-memory transfers. The programming manual for
    the JZ4770 does have a bit for a MDMA clock, but does not seem to have
    the hardware wired in.
    
    Add macros for the MDMA and BDMA clocks to the dt-bindings include
    files, so that they can be used within Device Tree files.
    
    Signed-off-by: Paul Cercueil <paul@crapouillou.net>
    Link: https://lore.kernel.org/r/20211220193319.114974-2-paul@crapouillou.net
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit c861c1be3897845313a0df47804b1db37c7052e1
Author: Conor Dooley <conor.dooley@microchip.com>
Date:   Thu Dec 23 15:42:44 2021 +0000

    clk: bm1880: remove kfrees on static allocations
    
    bm1880_clk_unregister_pll & bm1880_clk_unregister_div both try to
    free statically allocated variables, so remove those kfrees.
    
    For example, if we take L703 kfree(div_hw):
    - div_hw is a bm1880_div_hw_clock pointer
    - in bm1880_clk_register_plls this is pointed to an element of arg1:
      struct bm1880_div_hw_clock *clks
    - in the probe, where bm1880_clk_register_plls is called arg1 is
      bm1880_div_clks, defined on L371:
      static struct bm1880_div_hw_clock bm1880_div_clks[]
    
    Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
    Fixes: 1ab4601da55b ("clk: Add common clock driver for BM1880 SoC")
    Link: https://lore.kernel.org/r/20211223154244.1024062-1-conor.dooley@microchip.com
    Signed-off-by: Stephen Boyd <sboyd@kernel.org>

commit eff14fcd032bc1b403c1716f6823b3c72c58096a
Merge: 44bab87d8ca6f f734248174936
Author: Alexei Starovoitov <ast@kernel.org>
Date:   Thu Jan 6 17:08:35 2022 -0800

    Merge branch 'net: bpf: handle return value of post_bind{4,6} and add selftests for it'
    
    Menglong Dong says:
    
    ====================
    
    From: Menglong Dong <imagedong@tencent.com>
    
    The return value of BPF_CGROUP_RUN_PROG_INET{4,6}_POST_BIND() in
    __inet_bind() is not handled properly. While the return value
    is non-zero, it will set inet_saddr and inet_rcv_saddr to 0 and
    exit:
    
            err = BPF_CGROUP_RUN_PROG_INET4_POST_BIND(sk);
            if (err) {
                    inet->inet_saddr = inet->inet_rcv_saddr = 0;
                    goto out_release_sock;
            }
    
    Let's take UDP for example and see what will happen. For UDP
    socket, it will be added to 'udp_prot.h.udp_table->hash' and
    'udp_prot.h.udp_table->hash2' after the sk->sk_prot->get_port()
    called success. If 'inet->inet_rcv_saddr' is specified here,
    then 'sk' will be in the 'hslot2' of 'hash2' that it don't belong
    to (because inet_saddr is changed to 0), and UDP packet received
    will not be passed to this sock. If 'inet->inet_rcv_saddr' is not
    specified here, the sock will work fine, as it can receive packet
    properly, which is wired, as the 'bind()' is already failed.
    
    To undo the get_port() operation, introduce the 'put_port' field
    for 'struct proto'. For TCP proto, it is inet_put_port(); For UDP
    proto, it is udp_lib_unhash(); For icmp proto, it is
    ping_unhash().
    
    Therefore, after sys_bind() fail caused by
    BPF_CGROUP_RUN_PROG_INET4_POST_BIND(), it will be unbinded, which
    means that it can try to be binded to another port.
    
    The second patch use C99 initializers in test_sock.c
    
    The third patch is the selftests for this modification.
    
    Changes since v4:
    - use C99 initializers in test_sock.c before adding the test case
    
    Changes since v3:
    - add the third patch which use C99 initializers in test_sock.c
    
    Changes since v2:
    - NULL check for sk->sk_prot->put_port
    
    Changes since v1:
    - introduce 'put_port' field for 'struct proto'
    - add selftests for it
    ====================
    
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>

commit f7342481749365d9ac5f24fb971659a64e045bb5
Author: Menglong Dong <imagedong@tencent.com>
Date:   Thu Jan 6 21:20:22 2022 +0800

    bpf: selftests: Add bind retry for post_bind{4, 6}
    
    With previous patch, kernel is able to 'put_port' after sys_bind()
    fails. Add the test for that case: rebind another port after
    sys_bind() fails. If the bind success, it means previous bind
    operation is already undoed.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220106132022.3470772-4-imagedong@tencent.com

commit 6fd92c7f0c3846340fee20f62dacb17d0a15c0d3
Author: Menglong Dong <imagedong@tencent.com>
Date:   Thu Jan 6 21:20:21 2022 +0800

    bpf: selftests: Use C99 initializers in test_sock.c
    
    Use C99 initializers for the initialization of 'tests' in test_sock.c.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220106132022.3470772-3-imagedong@tencent.com

commit 91a760b26926265a60c77ddf016529bcf3e17a04
Author: Menglong Dong <imagedong@tencent.com>
Date:   Thu Jan 6 21:20:20 2022 +0800

    net: bpf: Handle return value of BPF_CGROUP_RUN_PROG_INET{4,6}_POST_BIND()
    
    The return value of BPF_CGROUP_RUN_PROG_INET{4,6}_POST_BIND() in
    __inet_bind() is not handled properly. While the return value
    is non-zero, it will set inet_saddr and inet_rcv_saddr to 0 and
    exit:
    
            err = BPF_CGROUP_RUN_PROG_INET4_POST_BIND(sk);
            if (err) {
                    inet->inet_saddr = inet->inet_rcv_saddr = 0;
                    goto out_release_sock;
            }
    
    Let's take UDP for example and see what will happen. For UDP
    socket, it will be added to 'udp_prot.h.udp_table->hash' and
    'udp_prot.h.udp_table->hash2' after the sk->sk_prot->get_port()
    called success. If 'inet->inet_rcv_saddr' is specified here,
    then 'sk' will be in the 'hslot2' of 'hash2' that it don't belong
    to (because inet_saddr is changed to 0), and UDP packet received
    will not be passed to this sock. If 'inet->inet_rcv_saddr' is not
    specified here, the sock will work fine, as it can receive packet
    properly, which is wired, as the 'bind()' is already failed.
    
    To undo the get_port() operation, introduce the 'put_port' field
    for 'struct proto'. For TCP proto, it is inet_put_port(); For UDP
    proto, it is udp_lib_unhash(); For icmp proto, it is
    ping_unhash().
    
    Therefore, after sys_bind() fail caused by
    BPF_CGROUP_RUN_PROG_INET4_POST_BIND(), it will be unbinded, which
    means that it can try to be binded to another port.
    
    Signed-off-by: Menglong Dong <imagedong@tencent.com>
    Signed-off-by: Alexei Starovoitov <ast@kernel.org>
    Link: https://lore.kernel.org/bpf/20220106132022.3470772-2-imagedong@tencent.com

commit 4f6626b0e140867fd6d5a2e9d4ceaef97f10f46a
Author: Moshe Shemesh <moshe@nvidia.com>
Date:   Sun Dec 5 11:20:59 2021 +0200

    Revert "net/mlx5: Add retry mechanism to the command entry index allocation"
    
    This reverts commit 410bd754cd73c4a2ac3856d9a03d7b08f9c906bf.
    
    The reverted commit had added a retry mechanism to the command entry
    index allocation. The previous patch ensures that there is a free
    command entry index once the command work handler holds the command
    semaphore. Thus the retry mechanism is not needed.
    
    Fixes: 410bd754cd73 ("net/mlx5: Add retry mechanism to the command entry index allocation")
    Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
    Reviewed-by: Eran Ben Elisha <eranbe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 8e715cd613a1e872b9d918e912d90b399785761a
Author: Moshe Shemesh <moshe@nvidia.com>
Date:   Sun Dec 5 12:07:49 2021 +0200

    net/mlx5: Set command entry semaphore up once got index free
    
    Avoid a race where command work handler may fail to allocate command
    entry index, by holding the command semaphore down till command entry
    index is being freed.
    
    Fixes: 410bd754cd73 ("net/mlx5: Add retry mechanism to the command entry index allocation")
    Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
    Reviewed-by: Eran Ben Elisha <eranbe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 07f6dc4024ea1d2314b9c8b81fd4e492864fcca1
Author: Maor Dickman <maord@nvidia.com>
Date:   Mon Jan 3 15:04:18 2022 +0200

    net/mlx5e: Sync VXLAN udp ports during uplink representor profile change
    
    Currently during NIC profile disablement all VXLAN udp ports offloaded to the
    HW are flushed and during its enablement the driver send notification to
    the stack to inform the core that the entire UDP tunnel port state has been
    lost, uplink representor doesn't have the same behavior which can cause
    VXLAN udp ports offload to be in bad state while moving between modes while
    VXLAN interface exist.
    
    Fixed by aligning the uplink representor profile behavior to the NIC behavior.
    
    Fixes: 84db66124714 ("net/mlx5e: Move set vxlan nic info to profile init")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit a1c7c49c2091926962f8c1c866d386febffec5d8
Author: Shay Drory <shayd@nvidia.com>
Date:   Thu Dec 30 08:54:08 2021 +0200

    net/mlx5: Fix access to sf_dev_table on allocation failure
    
    Even when SF devices are supported, the SF device table allocation
    can still fail.
    In such case mlx5_sf_dev_supported still reports true, but SF device
    table is invalid. This can result in NULL table access.
    
    Hence, fix it by adding NULL table check.
    
    Fixes: 1958fc2f0712 ("net/mlx5: SF, Add auxiliary device driver")
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Parav Pandit <parav@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit b6dfff21a170af5c695ebaa153b7f5e297ddca03
Author: Paul Blakey <paulb@nvidia.com>
Date:   Wed Jun 16 10:55:56 2021 +0300

    net/mlx5e: Fix matching on modified inner ip_ecn bits
    
    Tunnel device follows RFC 6040, and during decapsulation inner
    ip_ecn might change depending on inner and outer ip_ecn as follows:
    
     +---------+----------------------------------------+
     |Arriving |         Arriving Outer Header          |
     |   Inner +---------+---------+---------+----------+
     |  Header | Not-ECT | ECT(0)  | ECT(1)  |   CE     |
     +---------+---------+---------+---------+----------+
     | Not-ECT | Not-ECT | Not-ECT | Not-ECT | <drop>   |
     |  ECT(0) |  ECT(0) | ECT(0)  | ECT(1)  |   CE*    |
     |  ECT(1) |  ECT(1) | ECT(1)  | ECT(1)* |   CE*    |
     |    CE   |   CE    |  CE     | CE      |   CE     |
     +---------+---------+---------+---------+----------+
    
    Cells marked above are changed from original inner packet ip_ecn value.
    
    Tc then matches on the modified inner ip_ecn, but hw offload which
    matches the inner ip_ecn value before decap, will fail.
    
    Fix that by mapping all the cases of outer and inner ip_ecn matching,
    and only supporting cases where we know inner wouldn't be changed by
    decap, or in the outer ip_ecn=CE case, inner ip_ecn didn't matter.
    
    Fixes: bcef735c59f2 ("net/mlx5e: Offload TC matching on tos/ttl for ip tunnels")
    Signed-off-by: Paul Blakey <paulb@nvidia.com>
    Reviewed-by: Oz Shlomo <ozsh@nvidia.com>
    Reviewed-by: Eli Cohen <elic@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 01c3fd113ef50490ffd43f78f347ef6bb008510b
Author: Aya Levin <ayal@nvidia.com>
Date:   Sun Oct 24 16:52:23 2021 +0300

    Revert "net/mlx5e: Block offload of outer header csum for GRE tunnel"
    
    This reverts commit 54e1217b90486c94b26f24dcee1ee5ef5372f832.
    
    Although the NIC doesn't support offload of outer header CSUM, using
    gso_partial_features allows offloading the tunnel's segmentation. The
    driver relies on the stack CSUM calculation of the outer header. For
    this, NETIF_F_GSO_GRE_CSUM must be a member of the device's features.
    
    Fixes: 54e1217b9048 ("net/mlx5e: Block offload of outer header csum for GRE tunnel")
    Signed-off-by: Aya Levin <ayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 64050cdad0983ad8060e33c3f4b5aee2366bcebd
Author: Aya Levin <ayal@nvidia.com>
Date:   Sun Oct 24 11:47:41 2021 +0300

    Revert "net/mlx5e: Block offload of outer header csum for UDP tunnels"
    
    This reverts commit 6d6727dddc7f93fcc155cb8d0c49c29ae0e71122.
    
    Although the NIC doesn't support offload of outer header CSUM, using
    gso_partial_features allows offloading the tunnel's segmentation. The
    driver relies on the stack CSUM calculation of the outer header. For
    this, NETIF_F_GSO_UDP_TUNNEL_CSUM must be a member of the device's
    features.
    
    Fixes: 6d6727dddc7f ("net/mlx5e: Block offload of outer header csum for UDP tunnels")
    Signed-off-by: Aya Levin <ayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 9e72a55a3c9d54b38a704bb7292d984574a81d9d
Author: Maor Dickman <maord@nvidia.com>
Date:   Thu Dec 30 11:20:10 2021 +0200

    net/mlx5e: Don't block routes with nexthop objects in SW
    
    Routes with nexthop objects is currently not supported by multipath offload
    and any attempts to use it is blocked, however this also block adding SW
    routes with nexthop.
    
    Resolve this by returning NOTIFY_DONE instead of an error which will allow such
    a route to be created in SW but not offloaded.
    
    This fix also solve an issue which block adding such routes on different devices
    due to missing check if the route FIB device is one of multipath devices.
    
    Fixes: 6a87afc072c3 ("mlx5: Fail attempts to use routes with nexthop objects")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 885751eb1b01d276e38f57d78c583e4ce006c5ed
Author: Maor Dickman <maord@nvidia.com>
Date:   Wed Dec 29 16:10:41 2021 +0200

    net/mlx5e: Fix wrong usage of fib_info_nh when routes with nexthop objects are used
    
    Creating routes with nexthop objects while in switchdev mode leads to access to
    un-allocated memory and trigger bellow call trace due to hitting WARN_ON.
    This is caused due to illegal usage of fib_info_nh in TC tunnel FIB event handling to
    resolve the FIB device while fib_info built in with nexthop.
    
    Fixed by ignoring attempts to use nexthop objects with routes until support can be
    properly added.
    
    WARNING: CPU: 1 PID: 1724 at include/net/nexthop.h:468 mlx5e_tc_tun_fib_event+0x448/0x570 [mlx5_core]
    CPU: 1 PID: 1724 Comm: ip Not tainted 5.15.0_for_upstream_min_debug_2021_11_09_02_04 #1
    RIP: 0010:mlx5e_tc_tun_fib_event+0x448/0x570 [mlx5_core]
    RSP: 0018:ffff8881349f7910 EFLAGS: 00010202
    RAX: ffff8881492f1980 RBX: ffff8881349f79e8 RCX: 0000000000000000
    RDX: ffff8881349f79e8 RSI: 0000000000000000 RDI: 0000000000000000
    RBP: ffff8881349f7950 R08: 00000000000000fe R09: 0000000000000001
    R10: 0000000000000000 R11: 0000000000000000 R12: ffff88811e9d0000
    R13: ffff88810eb62000 R14: ffff888106710268 R15: 0000000000000018
    FS:  00007f1d5ca6e800(0000) GS:ffff88852c880000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 00007ffedba44ff8 CR3: 0000000129808004 CR4: 0000000000370ea0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Call Trace:
     <TASK>
     atomic_notifier_call_chain+0x42/0x60
     call_fib_notifiers+0x21/0x40
     fib_table_insert+0x479/0x6d0
     ? try_charge_memcg+0x480/0x6d0
     inet_rtm_newroute+0x65/0xb0
     rtnetlink_rcv_msg+0x2af/0x360
     ? page_add_file_rmap+0x13/0x130
     ? do_set_pte+0xcd/0x120
     ? rtnl_calcit.isra.0+0x120/0x120
     netlink_rcv_skb+0x4e/0xf0
     netlink_unicast+0x1ee/0x2b0
     netlink_sendmsg+0x22e/0x460
     sock_sendmsg+0x33/0x40
     ____sys_sendmsg+0x1d1/0x1f0
     ___sys_sendmsg+0xab/0xf0
     ? __mod_memcg_lruvec_state+0x40/0x60
     ? __mod_lruvec_page_state+0x95/0xd0
     ? page_add_new_anon_rmap+0x4e/0xf0
     ? __handle_mm_fault+0xec6/0x1470
     __sys_sendmsg+0x51/0x90
     ? internal_get_user_pages_fast+0x480/0xa10
     do_syscall_64+0x3d/0x90
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Fixes: 8914add2c9e5 ("net/mlx5e: Handle FIB events to update tunnel endpoint device")
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit de31854ece175e12ff3c35d07f340988823aed34
Author: Dima Chumak <dchumak@nvidia.com>
Date:   Wed Nov 24 09:37:26 2021 +0200

    net/mlx5e: Fix nullptr on deleting mirroring rule
    
    Deleting a Tc rule with multiple outputs, one of which is internal port,
    like this one:
    
      tc filter del dev enp8s0f0_0 ingress protocol ip pref 5 flower \
          dst_mac 0c:42:a1:d1:d0:88 \
          src_mac e4:ea:09:08:00:02 \
          action tunnel_key  set \
              src_ip 0.0.0.0 \
              dst_ip 7.7.7.8 \
              id 8 \
              dst_port 4789 \
          action mirred egress mirror dev vxlan_sys_4789 pipe \
          action mirred egress redirect dev enp8s0f0_1
    
    Triggers a call trace:
    
      BUG: kernel NULL pointer dereference, address: 0000000000000230
      RIP: 0010:del_sw_hw_rule+0x2b/0x1f0 [mlx5_core]
      Call Trace:
       tree_remove_node+0x16/0x30 [mlx5_core]
       mlx5_del_flow_rules+0x51/0x160 [mlx5_core]
       __mlx5_eswitch_del_rule+0x4b/0x170 [mlx5_core]
       mlx5e_tc_del_fdb_flow+0x295/0x550 [mlx5_core]
       mlx5e_flow_put+0x1f/0x70 [mlx5_core]
       mlx5e_delete_flower+0x286/0x390 [mlx5_core]
       tc_setup_cb_destroy+0xac/0x170
       fl_hw_destroy_filter+0x94/0xc0 [cls_flower]
       __fl_delete+0x15e/0x170 [cls_flower]
       fl_delete+0x36/0x80 [cls_flower]
       tc_del_tfilter+0x3a6/0x6e0
       rtnetlink_rcv_msg+0xe5/0x360
       ? rtnl_calcit.isra.0+0x110/0x110
       netlink_rcv_skb+0x46/0x110
       netlink_unicast+0x16b/0x200
       netlink_sendmsg+0x202/0x3d0
       sock_sendmsg+0x33/0x40
       ____sys_sendmsg+0x1c3/0x200
       ? copy_msghdr_from_user+0xd6/0x150
       ___sys_sendmsg+0x88/0xd0
       ? ___sys_recvmsg+0x88/0xc0
       ? do_futex+0x10c/0x460
       __sys_sendmsg+0x59/0xa0
       do_syscall_64+0x48/0x140
       entry_SYSCALL_64_after_hwframe+0x44/0xa9
    
    Fix by disabling offloading for flows matching
    esw_is_chain_src_port_rewrite() which have more than one output.
    
    Fixes: 10742efc20a4 ("net/mlx5e: VF tunnel TX traffic offloading")
    Signed-off-by: Dima Chumak <dchumak@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 0b7cfa4082fbf550595bc0e40f05614bd83bf0cd
Author: Aya Levin <ayal@nvidia.com>
Date:   Thu Dec 23 14:38:28 2021 +0200

    net/mlx5e: Fix page DMA map/unmap attributes
    
    Driver initiates DMA sync, hence it may skip CPU sync. Add
    DMA_ATTR_SKIP_CPU_SYNC as input attribute both to dma_map_page and
    dma_unmap_page to avoid redundant sync with the CPU.
    When forcing the device to work with SWIOTLB, the extra sync might cause
    data corruption. The driver unmaps the whole page while the hardware
    used just a part of the bounce buffer. So syncing overrides the entire
    page with bounce buffer that only partially contains real data.
    
    Fixes: bc77b240b3c5 ("net/mlx5e: Add fragmented memory support for RX multi packet WQE")
    Fixes: db05815b36cb ("net/mlx5e: Add XSK zero-copy support")
    Signed-off-by: Aya Levin <ayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 6968e707d371ef80511448c6771daf445b4a5cf5
Author: Bart Van Assche <bvanassche@acm.org>
Date:   Thu Jan 6 09:29:00 2022 -0800

    parisc: io: Improve the outb(), outw() and outl() macros
    
    This patch fixes the following build error for source file
    drivers/scsi/pcmcia/sym53c500_cs.c:
    
    In file included from ./include/linux/bug.h:5,
                     from ./include/linux/cpumask.h:14,
                     from ./include/linux/mm_types_task.h:14,
                     from ./include/linux/mm_types.h:5,
                     from ./include/linux/buildid.h:5,
                     from ./include/linux/module.h:14,
                     from drivers/scsi/pcmcia/sym53c500_cs.c:42:
    drivers/scsi/pcmcia/sym53c500_cs.c: In function ‘SYM53C500_intr’:
    ./arch/parisc/include/asm/bug.h:28:2: error: expected expression before ‘do’
       28 |  do {        \
          |  ^~
    ./arch/parisc/include/asm/io.h:276:20: note: in expansion of macro ‘BUG’
      276 | #define outb(x, y) BUG()
          |                    ^~~
    drivers/scsi/pcmcia/sym53c500_cs.c:124:19: note: in expansion of macro ‘outb’
      124 | #define REG0(x)  (outb(C4_IMG, (x) + CONFIG4))
          |                   ^~~~
    drivers/scsi/pcmcia/sym53c500_cs.c:362:2: note: in expansion of macro ‘REG0’
      362 |  REG0(port_base);
          |  ^~~~
    
    Cc: James E.J. Bottomley <James.Bottomley@HansenPartnership.com>
    Cc: Helge Deller <deller@gmx.de>
    Cc: Geert Uytterhoeven <geert@linux-m68k.org>
    Cc: linux-parisc@vger.kernel.org
    Signed-off-by: Bart Van Assche <bvanassche@acm.org>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 75c09aad79e4686367cbadb7dfe69c59d1537902
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 10:51:17 2022 +0100

    parisc: pdc_stable: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the parisc pdc_stable sysfs code to use default_groups
    field which has been the preferred way since aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
    Cc: Helge Deller <deller@gmx.de>
    Cc: linux-parisc@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit c1c72d9bbf2bf91670ac589adf037f433642fff5
Author: Helge Deller <deller@gmx.de>
Date:   Wed Jan 5 22:44:12 2022 +0100

    parisc: Add kgdb io_module to read chars via PDC
    
    Add a simplistic keyboard driver for usage of PDC I/O functions
    with kgdb. This driver makes it possible to use KGDB with QEMU.
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 712a270d2db967b387338c26c3dc04ccac3fcec3
Author: Helge Deller <deller@gmx.de>
Date:   Wed Jan 5 22:38:10 2022 +0100

    parisc: Fix pdc_toc_pim_11 and pdc_toc_pim_20 definitions
    
    The definitions for pdc_toc_pim_11 and pdc_toc_pim_20 are wrong since they
    include an entry for a hversion field which doesn't exist in the specification.
    
    Fix this and clean up some whitespaces so that the whole file will be in
    sync with it's copy in the SeaBIOS-hppa sources.
    
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org # v5.16

commit 72c3dd8207de4178ae50553666129af7231f86e7
Author: John David Anglin <dave.anglin@bell.net>
Date:   Tue Jan 4 21:48:11 2022 +0000

    parisc: Add lws_atomic_xchg and lws_atomic_store syscalls
    
    This patch adds two new LWS routines - lws_atomic_xchg and lws_atomic_store.
    
    These are simpler than the CAS routines.  Currently, we use the CAS
    routines for atomic stores.  This is inefficient since it requires
    both winning the spinlock and a successful CAS operation.
    
    Change has been tested on c8000 and rp3440.
    
    In v2, I moved the code to disble/enable page faults inside the spinlocks.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit d0585d742ff2d82accd26c661c60a6d260429c4a
Author: John David Anglin <dave.anglin@bell.net>
Date:   Tue Jan 4 21:44:32 2022 +0000

    parisc: Rewrite light-weight syscall and futex code
    
    The parisc architecture lacks general hardware support for compare and swap.
    Particularly for userspace, it is difficult to implement software atomic
    support. Page faults in critical regions can cause processes to sleep and
    block the forward progress of other processes.  Thus, it is essential that
    page faults be disabled in critical regions. For performance reasons, we
    also need to disable external interrupts in critical regions.
    
    In order to do this, we need a mechanism to trigger COW breaks outside the
    critical region. Fortunately, parisc has the "stbys,e" instruction. When
    the leftmost byte of a word is addressed, this instruction triggers all
    the exceptions of a normal store but it does not write to memory. Thus,
    we can use it to trigger COW breaks outside the critical region without
    modifying the data that is to be updated atomically.
    
    COW breaks occur randomly.  So even if we have priviously executed a "stbys,e"
    instruction, we still need to disable pagefaults around the critical region.
    If a fault occurs in the critical region, we return -EAGAIN. I had to add
    a wrapper around _arch_futex_atomic_op_inuser() as I found in testing that
    returning -EAGAIN caused problems for some processes even though it is
    listed as a possible return value.
    
    The patch implements the above. The code no longer attempts to sleep with
    interrupts disabled and I haven't seen any stalls with the change.
    
    I have attempted to merge common code and streamline the fast path.  In the
    futex code, we only compute the spinlock address once.
    
    I eliminated some debug code in the original CAS routine that just made the
    flow more complicated.
    
    I don't clip the arguments when called from wide mode. As a result, the LWS
    routines should work when called from 64-bit processes.
    
    I defined TASK_PAGEFAULT_DISABLED offset for use in the lws_pagefault_disable
    and lws_pagefault_enable macros.
    
    Since we now disable interrupts on the gateway page where necessary, it
    might be possible to allow processes to be scheduled when they are on the
    gateway page.
    
    Change has been tested on c8000 and rp3440. It improves glibc build and test
    time by about 10%.
    
    In v2, I removed the lws_atomic_xchg and and lws_atomic_store calls. I
    also removed the bug fixes that were not directly related to this patch.
    
    In v3, I removed the code to force interruptions from
    arch_futex_atomic_op_inuser(). It is always called with page faults
    disabled, so this code had no effect.
    
    In v4, I fixed a typo in depi_safe line.
    
    In v5, I moved the code to disable/enable page faults inside the spinlocks.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 20dda87bdc6567e864942ead40bc149ebbe3ae79
Author: John David Anglin <dave.anglin@bell.net>
Date:   Tue Jan 4 21:40:02 2022 +0000

    parisc: Enhance page fault termination message
    
    In debugging kernel panics, I believe it is useful to know what type
    of page fault caused the termination. "Bad Address" is too vague.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 9d90a90855ceb9ce0fb9b46b0591ac211e4b4612
Author: John David Anglin <dave.anglin@bell.net>
Date:   Tue Jan 4 21:34:26 2022 +0000

    parisc: Don't call faulthandler_disabled() in do_page_fault()
    
    It is dangerous to call faulthandler_disabled() when user_mode(regs)
    is true.  The task pagefault_disabled counter is racy and it is not
    updated atomically on parisc. As a result, calling faulthandler_disabled()
    may cause erroneous termination.
    
    We now handle execption fixups and termination when user_mode(regs) is
    false in handle_interruption(). Thus, we can just remove the
    faulthandler_disabled() check from do_page_fault().
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 4b9d2a731c3d22a05c1bccdb11b6e00054ff5fda
Author: Helge Deller <deller@gmx.de>
Date:   Thu Dec 23 21:46:35 2021 +0100

    parisc: Switch user access functions to signal errors in r29 instead of r8
    
    Use register r29 instead of register r8 to signal faults when accessing
    user memory. In case of faults, the fixup routine will store -EFAULT in
    this register.
    
    This change saves up to 752 bytes on a 32bit kernel, partly because the
    compiler doesn't need to save and restore the old r8 value on the stack.
    
    bloat-o-meter results for usage with r29 register:
    add/remove: 0/0 grow/shrink: 23/86 up/down: 228/-980 (-752)
    
    bloat-o-meter results for usage with r28 register:
    add/remove: 0/0 grow/shrink: 28/83 up/down: 296/-956 (-660)
    
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 9e9d4b460f23bab61672eae397417d03917d116c
Author: John David Anglin <dave.anglin@bell.net>
Date:   Wed Dec 22 16:52:26 2021 +0000

    parisc: Avoid calling faulthandler_disabled() twice
    
    In handle_interruption(), we call faulthandler_disabled() to check whether the
    fault handler is not disabled. If the fault handler is disabled, we immediately
    call do_page_fault(). It then calls faulthandler_disabled(). If disabled,
    do_page_fault() attempts to fixup the exception by jumping to no_context:
    
    no_context:
    
            if (!user_mode(regs) && fixup_exception(regs)) {
                    return;
            }
    
            parisc_terminate("Bad Address (null pointer deref?)", regs, code, address);
    
    Apart from the error messages, the two blocks of code perform the same
    function.
    
    We can avoid two calls to faulthandler_disabled() by a simple revision
    to the code in handle_interruption().
    
    Note: I didn't try to fix the formatting of this code block.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit db19c6f1a2a353cc8dec35b4789733a3cf6e2838
Author: John David Anglin <dave.anglin@bell.net>
Date:   Wed Dec 22 16:01:31 2021 +0000

    parisc: Fix lpa and lpa_user defines
    
    While working on the rewrite to the light-weight syscall and futex code, I
    experimented with using a hash index based on the user physical address of
    atomic variable. This exposed two problems with the lpa and lpa_user defines.
    
    Because of the copy instruction, the pa argument needs to be an early clobber
    argument. This prevents gcc from allocating the va and pa arguments to the same
    register.
    
    Secondly, the lpa instruction can cause a page fault so we need to catch
    exceptions.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Fixes: 116d753308cf ("parisc: Use lpa instruction to load physical addresses in driver code")
    Signed-off-by: Helge Deller <deller@gmx.de>
    Cc: stable@vger.kernel.org # v5.2+

commit 45458aa49abe3b0ac68ce86b3d4ca3a97eaeac53
Author: John David Anglin <dave.anglin@bell.net>
Date:   Tue Dec 21 15:04:53 2021 -0500

    parisc: Define depi_safe macro
    
    The depi instruction is similar to the extru instruction on 64-bit machines.
    It leaves the most-significant 32 bits of the target register in an undefined
    state.  On 64-bit machines, the macro uses depdi to perform safe deposits in
    the least-significant 32 bits.
    
    Signed-off-by: John David Anglin <dave.anglin@bell.net>
    Signed-off-by: Helge Deller <deller@gmx.de>

commit 745a13061aa079b36d83ba7f36dc051dbfccd888
Author: Saeed Mahameed <saeedm@nvidia.com>
Date:   Thu Jan 6 15:07:07 2022 -0800

    Documentation: devlink: mlx5.rst: Fix htmldoc build warning
    
    Fix the following build warning:
    
    Documentation/networking/devlink/mlx5.rst:13: WARNING: Error parsing content block for the "list-table" directive:
    +uniform two-level bullet list expected, but row 2 does not contain the same number of items as row 1 (2 vs 3).
    ...
    
    Add the missing item in the first row.
    
    Fixes: 0844fa5f7b89 ("net/mlx5: Let user configure io_eq_size param")
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5dd29f40b25f91f1b65043f2225b843a8d0cb1df
Author: Gal Pressman <gal@nvidia.com>
Date:   Wed Dec 22 14:03:39 2021 +0200

    net/mlx5e: Add recovery flow in case of error CQE
    
    The rep legacy RQ completion handling was missing the appropriate
    handling of error CQEs (dump the CQE and queue a recover work), fix it
    by calling trigger_report() when needed.
    
    Since all CQE handling flows do the exact same error CQE handling,
    extract it to a common helper function.
    
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Reviewed-by: Aya Levin <ayal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 68511b48bfbe8ebce9c1a55f2ea656b0144f046c
Author: Roi Dayan <roid@nvidia.com>
Date:   Mon Jan 3 10:57:01 2022 +0200

    net/mlx5e: TC, Remove redundant error logging
    
    Remove redundant and trivial error logging when trying to
    offload mirred device with unsupported devices.
    Using OVS could hit those a lot and the errors are still
    logged in extack.
    
    Signed-off-by: Roi Dayan <roid@nvidia.com>
    Reviewed-by: Maor Dickman <maord@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit be23511eb5c460db42bb29c2c208667a27163b10
Author: Saeed Mahameed <saeedm@nvidia.com>
Date:   Tue Sep 14 23:26:17 2021 -0700

    net/mlx5e: Refactor set_pflag_cqe_based_moder
    
    Rearrange the code and use cqe_mode_to_period_mode() helper.
    
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit b5f42903704f868fcb45f78d6f782958b282d382
Author: Gal Pressman <gal@nvidia.com>
Date:   Mon Nov 29 10:57:31 2021 +0200

    net/mlx5e: Move HW-GRO and CQE compression check to fix features flow
    
    Feature dependencies should be resolved in fix features rather than in
    set features flow. Move the check that disables HW-GRO in case CQE
    compression is enabled from set_feature_hw_gro() to
    mlx5e_fix_features().
    
    Signed-off-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit bc2a7b5c6b379d0f6e685b29fe04d2f7310c693d
Author: Aya Levin <ayal@nvidia.com>
Date:   Tue Dec 21 15:16:32 2021 +0200

    net/mlx5e: Fix feature check per profile
    
    Remove redundant space when constructing the feature's enum. Validate
    against the indented enum value.
    
    Fixes: 6c72cb05d4b8 ("net/mlx5e: Use bitmap field for profile features")
    Signed-off-by: Aya Levin <ayal@nvidia.com>
    Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 7846665d3504812acaebf920d1141851379a7f37
Author: Maor Dickman <maord@nvidia.com>
Date:   Thu Dec 9 14:03:01 2021 +0200

    net/mlx5e: Unblock setting vid 0 for VF in case PF isn't eswitch manager
    
    When using libvirt to passthrough VF to VM it will always set the VF vlan
    to 0 even if user didn’t request it, this will cause libvirt to fail to
    boot in case the PF isn't eswitch owner.
    
    Example of such case is the DPU host PF which isn't eswitch manager, so
    any attempt to passthrough VF of it using libvirt will fail.
    
    Fix it by not returning error in case set VF vlan is called with vid 0.
    
    Signed-off-by: Maor Dickman <maord@nvidia.com>
    Reviewed-by: Roi Dayan <roid@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 0a1498ebfa55b860e8ec929d73585bcd3fd81a4e
Author: Lama Kayal <lkayal@nvidia.com>
Date:   Mon Sep 13 16:06:35 2021 +0300

    net/mlx5e: Expose FEC counters via ethtool
    
    Add FEC counters' statistics of corrected_blocks and
    uncorrectable_blocks, along with their lanes via ethtool.
    
    HW supports corrected_blocks and uncorrectable_blocks counters both for
    RS-FEC mode and FC-FEC mode. In FC mode these counters are accumulated
    per lane, while in RS mode the correction method crosses lanes, thus
    only total corrected_blocks and uncorrectable_blocks are reported in
    this mode.
    
    Signed-off-by: Lama Kayal <lkayal@nvidia.com>
    Reviewed-by: Gal Pressman <gal@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit f79a609ea6bf54ad2d2c24e4de4524288b221666
Author: Maher Sanalla <msanalla@nvidia.com>
Date:   Wed Jan 5 14:50:11 2022 +0200

    net/mlx5: Update log_max_qp value to FW max capability
    
    log_max_qp in driver's default profile #2 was set to 18, but FW actually
    supports 17 at the most - a situation that led to the concerning print
    when the driver is loaded:
    "log_max_qp value in current profile is 18, changing to HCA capabaility
    limit (17)"
    
    The expected behavior from mlx5_profile #2 is to match the maximum FW
    capability in regards to log_max_qp. Thus, log_max_qp in profile #2 is
    initialized to a defined static value (0xff) - which basically means that
    when loading this profile, log_max_qp value  will be what the currently
    installed FW supports at most.
    
    Signed-off-by: Maher Sanalla <msanalla@nvidia.com>
    Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 061f5b23588a2b2a499643c8c798dcdb271bc059
Author: Shay Drory <shayd@nvidia.com>
Date:   Tue Nov 23 12:50:19 2021 +0200

    net/mlx5: SF, Use all available cpu for setting cpu affinity
    
    Currently all SFs are using the same CPUs. Spreading SF over CPUs, in
    round-robin manner, in order to achieve better distribution of the SFs
    over available CPUs.
    
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Reviewed-by: Parav Pandit <parav@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 79b60ca83b6fa63ef307d2edcc77ee6581da8971
Author: Shay Drory <shayd@nvidia.com>
Date:   Sun Dec 12 14:51:27 2021 +0200

    net/mlx5: Introduce API for bulk request and release of IRQs
    
    Currently IRQs are requested one by one. To balance spreading IRQs
    among cpus using such scheme requires remembering cpu mask for the
    cpus used for a given device. This complicates the IRQ allocation
    scheme in subsequent patch.
    
    Hence, prepare the code for bulk IRQs allocation. This enables
    spreading IRQs among cpus in subsequent patch.
    
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Parav Pandit <parav@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 424544df97b0197b1d87d2fd1c18c6b936aa02b1
Author: Shay Drory <shayd@nvidia.com>
Date:   Tue Nov 23 10:48:07 2021 +0200

    net/mlx5: Split irq_pool_affinity logic to new file
    
    The downstream patches add more functionality to irq_pool_affinity.
    Move the irq_pool_affinity logic to a new file in order to ease the
    coding and maintenance of it.
    
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 30c6afa735db60b4fb6ca81da568d11d19aa2c15
Author: Shay Drory <shayd@nvidia.com>
Date:   Tue Nov 23 09:14:58 2021 +0200

    net/mlx5: Move affinity assignment into irq_request
    
    Move affinity binding of the IRQ to irq_request function in order to
    bind the IRQ before inserting it to the xarray.
    
    After this change, the IRQ is ready for use when inserted to the xarray.
    
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 5256a46bf53872d9888c0d9c34382262b3006599
Author: Shay Drory <shayd@nvidia.com>
Date:   Sun Nov 14 13:01:21 2021 +0200

    net/mlx5: Introduce control IRQ request API
    
    Currently, IRQ layer have a separate flow for ctrl and comp IRQs, and
    the distinction between ctrl and comp IRQs is done in the IRQ layer.
    
    In order to ease the coding and maintenance of the IRQ layer,
    introduce a new API for requesting control IRQs -
    mlx5_ctrl_irq_request(struct mlx5_core_dev *dev).
    
    Signed-off-by: Shay Drory <shayd@nvidia.com>
    Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 20f80ffcedfaaa3d15acccd5b622ebb769ac759b
Author: Saeed Mahameed <saeedm@nvidia.com>
Date:   Thu Dec 23 11:28:09 2021 -0800

    net/mlx5: mlx5e_hv_vhca_stats_create return type to void
    
    Callers of this functions ignore its return value, as reported by
    Wang Qing, in one of the return paths, it returns positive values.
    
    Since return value is ignored anyways, void out the return type of the
    function.
    
    Reported-by: Wang Qing <wangqing@vivo.com>
    Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>

commit 6c8e11e08a5b74bb8a5cdd5cbc1e5143df0fba72
Author: Jann Horn <jannh@google.com>
Date:   Mon Jan 3 16:59:31 2022 +0100

    random: don't reset crng_init_cnt on urandom_read()
    
    At the moment, urandom_read() (used for /dev/urandom) resets crng_init_cnt
    to zero when it is called at crng_init<2. This is inconsistent: We do it
    for /dev/urandom reads, but not for the equivalent
    getrandom(GRND_INSECURE).
    
    (And worse, as Jason pointed out, we're only doing this as long as
    maxwarn>0.)
    
    crng_init_cnt is only read in crng_fast_load(); it is relevant at
    crng_init==0 for determining when to switch to crng_init==1 (and where in
    the RNG state array to write).
    
    As far as I understand:
    
     - crng_init==0 means "we have nothing, we might just be returning the same
       exact numbers on every boot on every machine, we don't even have
       non-cryptographic randomness; we should shove every bit of entropy we
       can get into the RNG immediately"
     - crng_init==1 means "well we have something, it might not be
       cryptographic, but at least we're not gonna return the same data every
       time or whatever, it's probably good enough for TCP and ASLR and stuff;
       we now have time to build up actual cryptographic entropy in the input
       pool"
     - crng_init==2 means "this is supposed to be cryptographically secure now,
       but we'll keep adding more entropy just to be sure".
    
    The current code means that if someone is pulling data from /dev/urandom
    fast enough at crng_init==0, we'll keep resetting crng_init_cnt, and we'll
    never make forward progress to crng_init==1. It seems to be intended to
    prevent an attacker from bruteforcing the contents of small individual RNG
    inputs on the way from crng_init==0 to crng_init==1, but that's misguided;
    crng_init==1 isn't supposed to provide proper cryptographic security
    anyway, RNG users who care about getting secure RNG output have to wait
    until crng_init==2.
    
    This code was inconsistent, and it probably made things worse - just get
    rid of it.
    
    Signed-off-by: Jann Horn <jannh@google.com>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 2ee25b6968b1b3c66ffa408de23d023c1bce81cf
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Thu Dec 30 17:50:52 2021 +0100

    random: avoid superfluous call to RDRAND in CRNG extraction
    
    RDRAND is not fast. RDRAND is actually quite slow. We've known this for
    a while, which is why functions like get_random_u{32,64} were converted
    to use batching of our ChaCha-based CRNG instead.
    
    Yet CRNG extraction still includes a call to RDRAND, in the hot path of
    every call to get_random_bytes(), /dev/urandom, and getrandom(2).
    
    This call to RDRAND here seems quite superfluous. CRNG is already
    extracting things based on a 256-bit key, based on good entropy, which
    is then reseeded periodically, updated, backtrack-mutated, and so
    forth. The CRNG extraction construction is something that we're already
    relying on to be secure and solid. If it's not, that's a serious
    problem, and it's unlikely that mixing in a measly 32 bits from RDRAND
    is going to alleviate things.
    
    And in the case where the CRNG doesn't have enough entropy yet, we're
    already initializing the ChaCha key row with RDRAND in
    crng_init_try_arch_early().
    
    Removing the call to RDRAND improves performance on an i7-11850H by
    370%. In other words, the vast majority of the work done by
    extract_crng() prior to this commit was devoted to fetching 32 bits of
    RDRAND.
    
    Reviewed-by: Theodore Ts'o <tytso@mit.edu>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 96562f286884e2db89c74215b199a1084b5fb7f7
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Fri Dec 31 09:26:08 2021 +0100

    random: early initialization of ChaCha constants
    
    Previously, the ChaCha constants for the primary pool were only
    initialized in crng_initialize_primary(), called by rand_initialize().
    However, some randomness is actually extracted from the primary pool
    beforehand, e.g. by kmem_cache_create(). Therefore, statically
    initialize the ChaCha constants for the primary pool.
    
    Cc: Herbert Xu <herbert@gondor.apana.org.au>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: <linux-crypto@vger.kernel.org>
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 7b87324112df2e1f9b395217361626362dcfb9fb
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Thu Dec 30 15:59:26 2021 +0100

    random: use IS_ENABLED(CONFIG_NUMA) instead of ifdefs
    
    Rather than an awkward combination of ifdefs and __maybe_unused, we can
    ensure more source gets parsed, regardless of the configuration, by
    using IS_ENABLED for the CONFIG_NUMA conditional code. This makes things
    cleaner and easier to follow.
    
    I've confirmed that on !CONFIG_NUMA, we don't wind up with excess code
    by accident; the generated object file is the same.
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 161212c7fd1d9069b232785c75492e50941e2ea8
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Wed Dec 29 22:10:07 2021 +0100

    random: harmonize "crng init done" messages
    
    We print out "crng init done" for !TRUST_CPU, so we should also print
    out the same for TRUST_CPU.
    
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 57826feeedb63b091f807ba8325d736775d39afd
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Dec 29 22:10:06 2021 +0100

    random: mix bootloader randomness into pool
    
    If we're trusting bootloader randomness, crng_fast_load() is called by
    add_hwgenerator_randomness(), which sets us to crng_init==1. However,
    usually it is only called once for an initial 64-byte push, so bootloader
    entropy will not mix any bytes into the input pool. So it's conceivable
    that crng_init==1 when crng_initialize_primary() is called later, but
    then the input pool is empty. When that happens, the crng state key will
    be overwritten with extracted output from the empty input pool. That's
    bad.
    
    In contrast, if we're not trusting bootloader randomness, we call
    crng_slow_load() *and* we call mix_pool_bytes(), so that later
    crng_initialize_primary() isn't drawing on nothing.
    
    In order to prevent crng_initialize_primary() from extracting an empty
    pool, have the trusted bootloader case mirror that of the untrusted
    bootloader case, mixing the input into the pool.
    
    [linux@dominikbrodowski.net: rewrite commit message]
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 73c7733f122e8d0107f88655a12011f68f69e74b
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Dec 29 22:10:05 2021 +0100

    random: do not throw away excess input to crng_fast_load
    
    When crng_fast_load() is called by add_hwgenerator_randomness(), we
    currently will advance to crng_init==1 once we've acquired 64 bytes, and
    then throw away the rest of the buffer. Usually, that is not a problem:
    When add_hwgenerator_randomness() gets called via EFI or DT during
    setup_arch(), there won't be any IRQ randomness. Therefore, the 64 bytes
    passed by EFI exactly matches what is needed to advance to crng_init==1.
    Usually, DT seems to pass 64 bytes as well -- with one notable exception
    being kexec, which hands over 128 bytes of entropy to the kexec'd kernel.
    In that case, we'll advance to crng_init==1 once 64 of those bytes are
    consumed by crng_fast_load(), but won't continue onward feeding in bytes
    to progress to crng_init==2. This commit fixes the issue by feeding
    any leftover bytes into the next phase in add_hwgenerator_randomness().
    
    [linux@dominikbrodowski.net: rewrite commit message]
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 9c3ddde3f811aabbb83778a2a615bf141b4909ef
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Dec 29 22:10:04 2021 +0100

    random: do not re-init if crng_reseed completes before primary init
    
    If the bootloader supplies sufficient material and crng_reseed() is called
    very early on, but not too early that wqs aren't available yet, then we
    might transition to crng_init==2 before rand_initialize()'s call to
    crng_initialize_primary() made. Then, when crng_initialize_primary() is
    called, if we're trusting the CPU's RDRAND instructions, we'll
    needlessly reinitialize the RNG and emit a message about it. This is
    mostly harmless, as numa_crng_init() will allocate and then free what it
    just allocated, and excessive calls to invalidate_batched_entropy()
    aren't so harmful. But it is funky and the extra message is confusing,
    so avoid the re-initialization all together by checking for crng_init <
    2 in crng_initialize_primary(), just as we already do in crng_reseed().
    
    Reviewed-by: Dominik Brodowski <linux@dominikbrodowski.net>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit f7e67b8e803185d0aabe7f29d25a35c8be724a78
Author: Dominik Brodowski <linux@dominikbrodowski.net>
Date:   Wed Dec 29 22:10:03 2021 +0100

    random: fix crash on multiple early calls to add_bootloader_randomness()
    
    Currently, if CONFIG_RANDOM_TRUST_BOOTLOADER is enabled, multiple calls
    to add_bootloader_randomness() are broken and can cause a NULL pointer
    dereference, as noted by Ivan T. Ivanov. This is not only a hypothetical
    problem, as qemu on arm64 may provide bootloader entropy via EFI and via
    devicetree.
    
    On the first call to add_hwgenerator_randomness(), crng_fast_load() is
    executed, and if the seed is long enough, crng_init will be set to 1.
    On subsequent calls to add_bootloader_randomness() and then to
    add_hwgenerator_randomness(), crng_fast_load() will be skipped. Instead,
    wait_event_interruptible() and then credit_entropy_bits() will be called.
    If the entropy count for that second seed is large enough, that proceeds
    to crng_reseed().
    
    However, both wait_event_interruptible() and crng_reseed() depends
    (at least in numa_crng_init()) on workqueues. Therefore, test whether
    system_wq is already initialized, which is a sufficient indicator that
    workqueue_init_early() has progressed far enough.
    
    If we wind up hitting the !system_wq case, we later want to do what
    would have been done there when wqs are up, so set a flag, and do that
    work later from the rand_initialize() call.
    
    Reported-by: Ivan T. Ivanov <iivanov@suse.de>
    Fixes: 18b915ac6b0a ("efi/random: Treat EFI_RNG_PROTOCOL output as bootloader randomness")
    Cc: stable@vger.kernel.org
    Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
    [Jason: added crng_need_done state and related logic.]
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 0d9488ffbf2faddebc6bac055bfa6c93b94056a3
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Fri Dec 24 19:17:58 2021 +0100

    random: do not sign extend bytes for rotation when mixing
    
    By using `char` instead of `unsigned char`, certain platforms will sign
    extend the byte when `w = rol32(*bytes++, input_rotate)` is called,
    meaning that bit 7 is overrepresented when mixing. This isn't a real
    problem (unless the mixer itself is already broken) since it's still
    invertible, but it's not quite correct either. Fix this by using an
    explicit unsigned type.
    
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 9f9eff85a008b095eafc5f4ecbaf5aca689271c1
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Tue Dec 21 16:31:27 2021 +0100

    random: use BLAKE2s instead of SHA1 in extraction
    
    This commit addresses one of the lower hanging fruits of the RNG: its
    usage of SHA1.
    
    BLAKE2s is generally faster, and certainly more secure, than SHA1, which
    has [1] been [2] really [3] very [4] broken [5]. Additionally, the
    current construction in the RNG doesn't use the full SHA1 function, as
    specified, and allows overwriting the IV with RDRAND output in an
    undocumented way, even in the case when RDRAND isn't set to "trusted",
    which means potential malicious IV choices. And its short length means
    that keeping only half of it secret when feeding back into the mixer
    gives us only 2^80 bits of forward secrecy. In other words, not only is
    the choice of hash function dated, but the use of it isn't really great
    either.
    
    This commit aims to fix both of these issues while also keeping the
    general structure and semantics as close to the original as possible.
    Specifically:
    
       a) Rather than overwriting the hash IV with RDRAND, we put it into
          BLAKE2's documented "salt" and "personal" fields, which were
          specifically created for this type of usage.
       b) Since this function feeds the full hash result back into the
          entropy collector, we only return from it half the length of the
          hash, just as it was done before. This increases the
          construction's forward secrecy from 2^80 to a much more
          comfortable 2^128.
       c) Rather than using the raw "sha1_transform" function alone, we
          instead use the full proper BLAKE2s function, with finalization.
    
    This also has the advantage of supplying 16 bytes at a time rather than
    SHA1's 10 bytes, which, in addition to having a faster compression
    function to begin with, means faster extraction in general. On an Intel
    i7-11850H, this commit makes initial seeding around 131% faster.
    
    BLAKE2s itself has the nice property of internally being based on the
    ChaCha permutation, which the RNG is already using for expansion, so
    there shouldn't be any issue with newness, funkiness, or surprising CPU
    behavior, since it's based on something already in use.
    
    [1] https://eprint.iacr.org/2005/010.pdf
    [2] https://www.iacr.org/archive/crypto2005/36210017/36210017.pdf
    [3] https://eprint.iacr.org/2015/967.pdf
    [4] https://shattered.io/static/shattered.pdf
    [5] https://www.usenix.org/system/files/sec20-leurent.pdf
    
    Reviewed-by: Theodore Ts'o <tytso@mit.edu>
    Reviewed-by: Eric Biggers <ebiggers@google.com>
    Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Jean-Philippe Aumasson <jeanphilippe.aumasson@gmail.com>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 6048fdcc5f269c7f31d774c295ce59081b36e6f9
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Wed Dec 22 14:56:58 2021 +0100

    lib/crypto: blake2s: include as built-in
    
    In preparation for using blake2s in the RNG, we change the way that it
    is wired-in to the build system. Instead of using ifdefs to select the
    right symbol, we use weak symbols. And because ARM doesn't need the
    generic implementation, we make the generic one default only if an arch
    library doesn't need it already, and then have arch libraries that do
    need it opt-in. So that the arch libraries can remain tristate rather
    than bool, we then split the shash part from the glue code.
    
    Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
    Acked-by: Ard Biesheuvel <ardb@kernel.org>
    Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Cc: Masahiro Yamada <masahiroy@kernel.org>
    Cc: linux-kbuild@vger.kernel.org
    Cc: linux-crypto@vger.kernel.org
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 009ba8568be497c640cab7571f7bfd18345d7b24
Author: Eric Biggers <ebiggers@google.com>
Date:   Mon Dec 20 16:41:57 2021 -0600

    random: fix data race on crng init time
    
    _extract_crng() does plain loads of crng->init_time and
    crng_global_init_time, which causes undefined behavior if
    crng_reseed() and RNDRESEEDCRNG modify these corrently.
    
    Use READ_ONCE() and WRITE_ONCE() to make the behavior defined.
    
    Don't fix the race on crng->init_time by protecting it with crng->lock,
    since it's not a problem for duplicate reseedings to occur.  I.e., the
    lockless access with READ_ONCE() is fine.
    
    Fixes: d848e5f8e1eb ("random: add new ioctl RNDRESEEDCRNG")
    Fixes: e192be9d9a30 ("random: replace non-blocking pool with a Chacha20-based CRNG")
    Cc: stable@vger.kernel.org
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Acked-by: Paul E. McKenney <paulmck@kernel.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 5d73d1e320c3fd94ea15ba5f79301da9a8bcc7de
Author: Eric Biggers <ebiggers@google.com>
Date:   Mon Dec 20 16:41:56 2021 -0600

    random: fix data race on crng_node_pool
    
    extract_crng() and crng_backtrack_protect() load crng_node_pool with a
    plain load, which causes undefined behavior if do_numa_crng_init()
    modifies it concurrently.
    
    Fix this by using READ_ONCE().  Note: as per the previous discussion
    https://lore.kernel.org/lkml/20211219025139.31085-1-ebiggers@kernel.org/T/#u,
    READ_ONCE() is believed to be sufficient here, and it was requested that
    it be used here instead of smp_load_acquire().
    
    Also change do_numa_crng_init() to set crng_node_pool using
    cmpxchg_release() instead of mb() + cmpxchg(), as the former is
    sufficient here but is more lightweight.
    
    Fixes: 1e7f583af67b ("random: make /dev/urandom scalable for silly userspace programs")
    Cc: stable@vger.kernel.org
    Signed-off-by: Eric Biggers <ebiggers@google.com>
    Acked-by: Paul E. McKenney <paulmck@kernel.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 5320eb42dec7a7ef3ab7da3c5c0d7f889a5181e5
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Tue Dec 7 13:17:34 2021 +0100

    irq: remove unused flags argument from __handle_irq_event_percpu()
    
    The __IRQF_TIMER bit from the flags argument was used in
    add_interrupt_randomness() to distinguish the timer interrupt from other
    interrupts. This is no longer the case.
    
    Remove the flags argument from __handle_irq_event_percpu().
    
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 703f7066f40599c290babdb79dd61319264987e9
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date:   Tue Dec 7 13:17:33 2021 +0100

    random: remove unused irq_flags argument from add_interrupt_randomness()
    
    Since commit
       ee3e00e9e7101 ("random: use registers from interrupted code for CPU's w/o a cycle counter")
    
    the irq_flags argument is no longer used.
    
    Remove unused irq_flags.
    
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Dexuan Cui <decui@microsoft.com>
    Cc: H. Peter Anvin <hpa@zytor.com>
    Cc: Haiyang Zhang <haiyangz@microsoft.com>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: K. Y. Srinivasan <kys@microsoft.com>
    Cc: Stephen Hemminger <sthemmin@microsoft.com>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Wei Liu <wei.liu@kernel.org>
    Cc: linux-hyperv@vger.kernel.org
    Cc: x86@kernel.org
    Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
    Acked-by: Wei Liu <wei.liu@kernel.org>
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 2b6c6e3d9ce3aa0e547ac25d60e06fe035cd9f79
Author: Mark Brown <broonie@kernel.org>
Date:   Wed Dec 1 17:44:49 2021 +0000

    random: document add_hwgenerator_randomness() with other input functions
    
    The section at the top of random.c which documents the input functions
    available does not document add_hwgenerator_randomness() which might lead
    a reader to overlook it. Add a brief note about it.
    
    Signed-off-by: Mark Brown <broonie@kernel.org>
    [Jason: reorganize position of function in doc comment and also document
     add_bootloader_randomness() while we're at it.]
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 9bafaa9375cbf892033f188d8cb624ae328754b5
Author: Jason A. Donenfeld <Jason@zx2c4.com>
Date:   Sat Dec 25 01:50:07 2021 +0100

    MAINTAINERS: add git tree for random.c
    
    This is handy not just for humans, but also so that the 0-day bot can
    automatically test posted mailing list patches against the right tree.
    
    Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>

commit 44bab87d8ca6f0544a9f8fc97bdf33aa5b3c899e
Author: Hao Luo <haoluo@google.com>
Date:   Thu Jan 6 12:55:25 2022 -0800

    bpf/selftests: Test bpf_d_path on rdonly_mem.
    
    The second parameter of bpf_d_path() can only accept writable
    memories. Rdonly_mem obtained from bpf_per_cpu_ptr() can not
    be passed into bpf_d_path for modification. This patch adds
    a selftest to verify this behavior.
    
    Signed-off-by: Hao Luo <haoluo@google.com>
    Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
    Acked-by: Yonghong Song <yhs@fb.com>
    Link: https://lore.kernel.org/bpf/20220106205525.2116218-1-haoluo@google.com

commit e59618f0f46fa6cf86d5b82380e0f453756b282b
Author: Grant Seltzer <grantseltzer@gmail.com>
Date:   Thu Jan 6 15:13:05 2022 -0500

    libbpf: Add documentation for bpf_map batch operations
    
    This adds documention for:
    
    - bpf_map_delete_batch()
    - bpf_map_lookup_batch()
    - bpf_map_lookup_and_delete_batch()
    - bpf_map_update_batch()
    
    This also updates the public API for the `keys` parameter
    of `bpf_map_delete_batch()`, and both the
    `keys` and `values` parameters of `bpf_map_update_batch()`
    to be constants.
    
    Signed-off-by: Grant Seltzer <grantseltzer@gmail.com>
    Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
    Acked-by: Yonghong Song <yhs@fb.com>
    Link: https://lore.kernel.org/bpf/20220106201304.112675-1-grantseltzer@gmail.com

commit f5f60d235e7058da13a643c33fc7599c05ec0b73
Author: Wei Yang <richard.weiyang@gmail.com>
Date:   Sat Dec 25 00:09:32 2021 +0000

    cgroup/rstat: check updated_next only for root
    
    After commit dc26532aed0a ("cgroup: rstat: punt root-level optimization to
    individual controllers"), each rstat on updated_children list has its
    ->updated_next not NULL.
    
    This means we can remove the check on ->updated_next, if we make sure
    the subtree from @root is on list, which could be done by checking
    updated_next for root.
    
    tj: Coding style fixes.
    
    Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
    Reviewed-by: Michal Koutný <mkoutny@suse.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit 70bc793382a0e37ba4e35e4d1a317b280b829a44
Author: Andrii Nakryiko <andrii@kernel.org>
Date:   Thu Jan 6 12:51:56 2022 -0800

    selftests/bpf: Don't rely on preserving volatile in PT_REGS macros in loop3
    
    PT_REGS*() macro on some architectures force-cast struct pt_regs to
    other types (user_pt_regs, etc) and might drop volatile modifiers, if any.
    Volatile isn't really required as pt_regs value isn't supposed to change
    during the BPF program run, so this is correct behavior.
    
    But progs/loop3.c relies on that volatile modifier to ensure that loop
    is preserved. Fix loop3.c by declaring i and sum variables as volatile
    instead. It preserves the loop and makes the test pass on all
    architectures (including s390x which is currently broken).
    
    Fixes: 3cc31d794097 ("libbpf: Normalize PT_REGS_xxx() macro definitions")
    Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Link: https://lore.kernel.org/bpf/20220106205156.955373-1-andrii@kernel.org

commit 0da41f7348fff193d01d031ce255088fa98324b7
Author: Wei Yang <richard.weiyang@gmail.com>
Date:   Sat Dec 25 00:09:31 2021 +0000

    cgroup: rstat: explicitly put loop variant in while
    
    Instead of do while unconditionally, let's put the loop variant in
    while.
    
    Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
    Reviewed-by: Michal Koutný <mkoutny@suse.com>
    Signed-off-by: Tejun Heo <tj@kernel.org>

commit f6fdf773daa399e688de70098ef4feaa5ea8e67c
Merge: 3b247eeaecfef 3969341813eb5
Author: Mark Brown <broonie@kernel.org>
Date:   Thu Jan 6 20:26:24 2022 +0000

    ASoC: imx-card: several improvement and fixes
    
    Merge series from Shengjiu Wang <shengjiu.wang@nxp.com>:
    
    Several improvement and fixes for AK codecs supported on i.MX platfroms

commit 42f4046bc4ba56c6e4d2af7a9d7f70eaa563daec
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 5 19:37:16 2022 +0100

    efi: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the firmware efi sysfs code to use default_groups
    field which has been the preferred way since aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Cc: Ard Biesheuvel <ardb@kernel.org>
    Cc: linux-efi@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

commit f046fff8bc4c4d8f8a478022e76e40b818f692df
Author: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Date:   Fri Nov 19 13:47:45 2021 +0200

    efi/libstub: measure loaded initrd info into the TPM
    
    In an effort to ensure the initrd observed and used by the OS is
    the same one that was meant to be loaded, which is difficult to
    guarantee otherwise, let's measure the initrd if the EFI stub and
    specifically the newly introduced LOAD_FILE2 protocol was used.
    
    Modify the initrd loading sequence so that the contents of the initrd
    are measured into PCR9.  Note that the patch is currently using
    EV_EVENT_TAG to create the eventlog entry instead of EV_IPL.  According
    to the TCP PC Client specification this is used for PCRs defined for OS
    and application usage.
    
    Co-developed-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
    Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
    Link: https://lore.kernel.org/r/20211119114745.1560453-5-ilias.apalodimas@linaro.org
    [ardb: add braces to initializer of tagged_event_data]
    Link: https://github.com/ClangBuiltLinux/linux/issues/1547
    Signed-off-by: Ard Biesheuvel <ardb@kernel.org>

commit d85bd8233fff000567cda4e108112bcb33478616
Merge: 050f461e28c5d 1745e857e73a2
Author: Jens Axboe <axboe@kernel.dk>
Date:   Thu Jan 6 12:36:04 2022 -0700

    Merge branch 'md-next' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/song/md into for-5.17/drivers
    
    Pull MD updates from Song:
    
    "The major changes are:
    
    - REQ_NOWAIT support, by Vishal Verma
    - raid6 benchmark optimization, by Dirk Müller
    - Fix for acct bioset, by Xiao Ni
    - Clean up max_queued_requests, by Mariusz Tkaczyk
    - PREEMPT_RT optimization, by Davidlohr Bueso
    - Use default_groups in kobj_type, by Greg Kroah-Hartman"
    
    * 'md-next' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/song/md:
      md: use default_groups in kobj_type
      md: Move alloc/free acct bioset in to personality
      lib/raid6: Use strict priority ranking for pq gen() benchmarking
      lib/raid6: skip benchmark of non-chosen xor_syndrome functions
      md: fix spelling of "its"
      md: raid456 add nowait support
      md: raid10 add nowait support
      md: raid1 add nowait support
      md: add support for REQ_NOWAIT
      md: drop queue limitation for RAID1 and RAID10
      md/raid5: play nice with PREEMPT_RT

commit 34bf20ce986c441c1088ed09a33e0bb96e52f99a
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Mon Dec 27 14:40:52 2021 -0500

    NFSv42: Fallocate and clone should also request 'blocks used'
    
    Both fallocate and clone can end up updating the blocks used attribute.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 85847280b11666ae24aac519e06f0742fab72064
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Mon Dec 27 14:40:51 2021 -0500

    NFSv4: Allow writebacks to request 'blocks used'
    
    When doing a non-pNFS write, allow the writeback code to specify that it
    also needs to update 'blocks used'.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 86439fa2678d1ae752ac9c787aac1c145b87b4c2
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Tue Dec 28 15:48:23 2021 +0100

    SUNRPC: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the sunrpc sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Cc: "J. Bruce Fields" <bfields@fieldses.org>
    Cc: Chuck Lever <chuck.lever@oracle.com>
    Cc: Trond Myklebust <trond.myklebust@hammerspace.com>
    Cc: Anna Schumaker <anna.schumaker@netapp.com>
    Cc: linux-nfs@vger.kernel.org
    Cc: netdev@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 01f34245722b9dac0b2667db4dc17d2049b99c76
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Tue Dec 28 15:41:38 2021 +0100

    NFS: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the NFS code to use default_groups field which has been the
    preferred way since aa30f47cf666 ("kobject: Add support for default
    attribute groups to kobj_type") so that we can soon get rid of the
    obsolete default_attrs field.
    
    Cc: Trond Myklebust <trond.myklebust@hammerspace.com>
    Cc: Anna Schumaker <anna.schumaker@netapp.com>
    Cc: linux-nfs@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 68eaba4ca924a97a863c5c81c0b23a11dcb6db90
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Fri Dec 17 15:36:58 2021 -0500

    NFS: Fix the verifier for case sensitive filesystem in nfs_atomic_open()
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 00bdadc7accfce944dc30fbc205cd28a7eed657b
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Fri Dec 17 15:36:57 2021 -0500

    NFS: Add a helper to remove case-insensitive aliases
    
    When dealing with case insensitive names, the client has no idea how the
    server performs the mapping, so cannot collapse the dentries into a
    single representative. So both rename and unlink need to deal with the
    fact that there could be several dentries representing the file, and
    have to somehow force them to be revalidated. Use d_prune_aliases() as a
    big hammer approach.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 8ce37abdeb4c73842d16620e1da151765ac86b5e
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Fri Dec 17 15:36:56 2021 -0500

    NFS: Invalidate negative dentries on all case insensitive directory changes
    
    If we create a file, rename it, or hardlink it, then we need to assume
    that cached negative dentries need to be revalidated.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 98ca3ee60b9e4b039cc3ef21a169e775afa9bd0c
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Fri Dec 17 15:36:55 2021 -0500

    NFSv4: Just don't cache negative dentries on case insensitive servers
    
    If the directory contents change, we cannot rely on the negative dentry
    being cacheable.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 1ab5be4ac5b1c9ce39ce1037c45b68d2ce6eede0
Author: Trond Myklebust <trond.myklebust@primarydata.com>
Date:   Fri Dec 17 15:36:54 2021 -0500

    NFSv4: Add some support for case insensitive filesystems
    
    Add capabilities to allow the NFS client to recognise when it is dealing
    with case insensitive and case preserving filesystems.
    
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit b05bf5c63b326ce1da84ef42498d8e0e292e694c
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Mon Jan 3 14:50:16 2022 -0500

    NFSv4.1: Fix uninitialised variable in devicenotify
    
    When decode_devicenotify_args() exits with no entries, we need to
    ensure that the struct cb_devicenotifyargs is initialised to
    { 0, NULL } in order to avoid problems in
    nfs4_callback_devicenotify().
    
    Reported-by: <rtm@csail.mit.edu>
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit fbd2057e5329d3502a27491190237b6be52a1cb6
Author: Xiaoke Wang <xkernel.wang@foxmail.com>
Date:   Fri Dec 17 01:01:33 2021 +0800

    nfs: nfs4clinet: check the return value of kstrdup()
    
    kstrdup() returns NULL when some internal memory errors happen, it is
    better to check the return value of it so to catch the memory error in
    time.
    
    Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 2c52c8376db7160a1dd8a681c61c9258405ef143
Author: Olga Kornievskaia <kolga@netapp.com>
Date:   Mon Nov 29 15:33:56 2021 -0500

    NFSv4 only print the label when its queried
    
    When the bitmask of the attributes doesn't include the security label,
    don't bother printing it. Since the label might not be null terminated,
    adjust the printing format accordingly.
    
    Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit c4f0396688b5916b3a95bcb004d158634f2234ff
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Thu Nov 18 17:37:41 2021 +0800

    SUNRPC: clean up some inconsistent indenting
    
    Eliminate the follow smatch warning:
    
    net/sunrpc/xprtsock.c:1912 xs_local_connect() warn: inconsistent
    indenting.
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 35e0f9a9af4869a4b1a3943da08d3a29ac6c4a42
Author: Xu Wang <vulab@iscas.ac.cn>
Date:   Wed Nov 10 09:32:17 2021 +0000

    sunrpc: Remove unneeded null check
    
    In g_verify_token_header, the null check of 'ret'
    is unneeded to be done twice.
    
    Signed-off-by: Xu Wang <vulab@iscas.ac.cn>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit c72a826829ccfb38019187a3a5ba6d3584b7b7dc
Author: Gustavo A. R. Silva <gustavoars@kernel.org>
Date:   Tue Aug 10 18:31:01 2021 -0500

    nfs41: pnfs: filelayout: Replace one-element array with flexible-array member
    
    There is a regular need in the kernel to provide a way to declare having
    a dynamically sized set of trailing elements in a structure. Kernel code
    should always use “flexible array members”[1] for these cases. The older
    style of one-element or zero-length arrays should no longer be used[2].
    
    Refactor the code a bit according to the use of a flexible-array member
    in struct nfs4_file_layout_dsaddr instead of a one-element array, and
    use the struct_size() helper.
    
    This helps with the ongoing efforts to globally enable -Warray-bounds
    and get us closer to being able to tighten the FORTIFY_SOURCE routines
    on memcpy().
    
    This issue was found with the help of Coccinelle and audited and fixed,
    manually.
    
    [1] https://en.wikipedia.org/wiki/Flexible_array_member
    [2] https://www.kernel.org/doc/html/v5.10/process/deprecated.html#zero-length-and-one-element-arrays
    
    Link: https://github.com/KSPP/linux/issues/79
    Link: https://github.com/KSPP/linux/issues/109
    Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 4b0c359b813bbf115f5e2219ea8c0e4fad92400b
Author: Pierguido Lambri <plambri@redhat.com>
Date:   Mon Dec 13 08:38:48 2021 +0000

    SUNRPC: Add source address/port to rpc_socket* traces
    
    The rpc_socket* traces now show also the source address
    and port. An example is:
    
    kworker/u17:1-951   [005] 134218.925343: rpc_socket_close:
       socket:[46913] srcaddr=192.168.100.187:793 dstaddr=192.168.100.129:2049
       state=4 (DISCONNECTING) sk_state=7 (CLOSE)
    kworker/u17:0-242   [006] 134360.841370: rpc_socket_connect:
       error=-115 socket:[56322] srcaddr=192.168.100.187:769
       dstaddr=192.168.100.129:2049 state=2 (CONNECTING) sk_state=2 (SYN_SENT)
           <idle>-0     [006] 134360.841859: rpc_socket_state_change: socket:[56322]
       srcaddr=192.168.100.187:769 dstaddr=192.168.100.129:2049 state=2 (CONNECTING)
       sk_state=1 (ESTABLISHED)
    
    Signed-off-by: Pierguido Lambri <plambri@redhat.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 6ff9d99bb88faebf134ca668842349d9718e5464
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Wed Dec 15 16:38:16 2021 -0500

    NFS: Ensure the server has an up to date ctime before renaming
    
    Renaming a file is required by POSIX to update the file ctime, so
    ensure that the file data is synced to disk so that we don't clobber the
    updated ctime by writing back after creating the hard link.
    
    Fixes: f2c2c552f119 ("NFS: Move delegation recall into the NFSv4 callback for rename_setup()")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 204975036b34f55237bc44c8a302a88468ef21b5
Author: Trond Myklebust <trond.myklebust@hammerspace.com>
Date:   Wed Dec 15 16:38:15 2021 -0500

    NFS: Ensure the server has an up to date ctime before hardlinking
    
    Creating a hard link is required by POSIX to update the file ctime, so
    ensure that the file data is synced to disk so that we don't clobber the
    updated ctime by writing back after creating the hard link.
    
    Fixes: 9f7682728728 ("NFS: Move the delegation return down into nfs4_proc_link()")
    Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 6238aec83f3fb12132f964937e5bbcf248fea8f9
Author: NeilBrown <neilb@suse.de>
Date:   Tue Sep 28 09:47:57 2021 +1000

    NFS: don't store 'struct cred *' in struct nfs_access_entry
    
    Storing the 'struct cred *' in nfs_access_entry is problematic.
    An active 'cred' can keep a 'struct key *' active, and a quota is
    imposed on the number of such keys that a user can maintain.
    Cached 'nfs_access_entry' structs have indefinite lifetime, and having
    these keep 'struct key's alive imposes on that quota.
    
    So remove the 'struct cred *' and replace it with the fields we need:
      kuid_t, kgid_t, and struct group_info *
    
    This makes the 'struct nfs_access_entry' 64 bits larger.
    
    New function "access_cmp" is introduced which is identical to
    cred_fscmp() except that the second arg is an 'nfs_access_entry', rather
    than a 'cred'
    
    Fixes: b68572e07c58 ("NFS: change access cache to use 'struct cred'.")
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 73fbb3fa647bdb5b60469af8101c741ece03a825
Author: NeilBrown <neilb@suse.de>
Date:   Tue Sep 28 09:47:57 2021 +1000

    NFS: pass cred explicitly for access tests
    
    Storing the 'struct cred *' in nfs_access_entry is problematic.
    An active 'cred' can keep a 'struct key *' active, and a quota is
    imposed on the number of such keys that a user can maintain.
    Cached 'nfs_access_entry' structs have indefinite lifetime, and having
    these keep 'struct key's alive imposes on that quota.
    
    So a future patch will remove the ->cred ref from nfs_access_entry.
    
    To prepare, change various functions to not assume there is a 'cred' in
    the nfs_access_entry, but to pass the cred around explicitly.
    
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit b5e7b59c3480f355910f9d2c6ece5857922a5e54
Author: NeilBrown <neilb@suse.de>
Date:   Tue Sep 28 09:47:57 2021 +1000

    NFS: change nfs_access_get_cached to only report the mask
    
    Currently the nfs_access_get_cached family of functions report a
    'struct nfs_access_entry' as the result, with both .mask and .cred set.
    However the .cred is never used.  This is probably good and there is no
    guarantee that it won't be freed before use.
    
    Change to only report the 'mask' - as this is all that is used or needed.
    
    Signed-off-by: NeilBrown <neilb@suse.de>
    Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

commit 7e937bb3cbe1f6b9840a43f879aa6e3f1a5e6537
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Wed Jan 5 11:14:19 2022 -0800

    xfs: warn about inodes with project id of -1
    
    Inodes aren't supposed to have a project id of -1U (aka 4294967295) but
    the kernel hasn't always validated FSSETXATTR correctly.  Flag this as
    something for the sysadmin to check out.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit eae44cb341ec49f993867b44398b13c6d28600dc
Author: Darrick J. Wong <djwong@kernel.org>
Date:   Wed Jan 5 11:13:57 2022 -0800

    xfs: hold quota inode ILOCK_EXCL until the end of dqalloc
    
    Online fsck depends on callers holding ILOCK_EXCL from the time they
    decide to update a block mapping until after they've updated the reverse
    mapping records to guarantee the stability of both mapping records.
    Unfortunately, the quota code drops ILOCK_EXCL at the first transaction
    roll in the dquot allocation process, which breaks that assertion.  This
    leads to sporadic failures in the online rmap repair code if the repair
    code grabs the AGF after bmapi_write maps a new block into the quota
    file's data fork but before it can finish the deferred rmap update.
    
    Fix this by rewriting the function to hold the ILOCK until after the
    transaction commit like all other bmap updates do, and get rid of the
    dqread wrapper that does nothing but complicate the codebase.
    
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>
    Reviewed-by: Dave Chinner <dchinner@redhat.com>

commit f4901a182d33d05a3b7020e2af97c635f6c47959
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Wed Jan 5 11:12:37 2022 -0800

    xfs: Remove redundant assignment of mp
    
    mp is being initialized to log->l_mp but this is never read
    as record is overwritten later on. Remove the redundant
    assignment.
    
    Cleans up the following clang-analyzer warning:
    
    fs/xfs/xfs_log_recover.c:3543:20: warning: Value stored to 'mp' during
    its initialization is never read [clang-analyzer-deadcode.DeadStores].
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit 8dc9384b7d75012856b02ff44c37566a55fc2abf
Author: Dave Chinner <dchinner@redhat.com>
Date:   Tue Jan 4 17:22:18 2022 -0800

    xfs: reduce kvmalloc overhead for CIL shadow buffers
    
    Oh, let me count the ways that the kvmalloc API sucks dog eggs.
    
    The problem is when we are logging lots of large objects, we hit
    kvmalloc really damn hard with costly order allocations, and
    behaviour utterly sucks:
    
         - 49.73% xlog_cil_commit
             - 31.62% kvmalloc_node
                - 29.96% __kmalloc_node
                   - 29.38% kmalloc_large_node
                      - 29.33% __alloc_pages
                         - 24.33% __alloc_pages_slowpath.constprop.0
                            - 18.35% __alloc_pages_direct_compact
                               - 17.39% try_to_compact_pages
                                  - compact_zone_order
                                     - 15.26% compact_zone
                                          5.29% __pageblock_pfn_to_page
                                          3.71% PageHuge
                                        - 1.44% isolate_migratepages_block
                                             0.71% set_pfnblock_flags_mask
                                       1.11% get_pfnblock_flags_mask
                               - 0.81% get_page_from_freelist
                                  - 0.59% _raw_spin_lock_irqsave
                                     - do_raw_spin_lock
                                          __pv_queued_spin_lock_slowpath
                            - 3.24% try_to_free_pages
                               - 3.14% shrink_node
                                  - 2.94% shrink_slab.constprop.0
                                     - 0.89% super_cache_count
                                        - 0.66% xfs_fs_nr_cached_objects
                                           - 0.65% xfs_reclaim_inodes_count
                                                0.55% xfs_perag_get_tag
                                       0.58% kfree_rcu_shrink_count
                            - 2.09% get_page_from_freelist
                               - 1.03% _raw_spin_lock_irqsave
                                  - do_raw_spin_lock
                                       __pv_queued_spin_lock_slowpath
                         - 4.88% get_page_from_freelist
                            - 3.66% _raw_spin_lock_irqsave
                               - do_raw_spin_lock
                                    __pv_queued_spin_lock_slowpath
                - 1.63% __vmalloc_node
                   - __vmalloc_node_range
                      - 1.10% __alloc_pages_bulk
                         - 0.93% __alloc_pages
                            - 0.92% get_page_from_freelist
                               - 0.89% rmqueue_bulk
                                  - 0.69% _raw_spin_lock
                                     - do_raw_spin_lock
                                          __pv_queued_spin_lock_slowpath
               13.73% memcpy_erms
             - 2.22% kvfree
    
    On this workload, that's almost a dozen CPUs all trying to compact
    and reclaim memory inside kvmalloc_node at the same time. Yet it is
    regularly falling back to vmalloc despite all that compaction, page
    and shrinker reclaim that direct reclaim is doing. Copying all the
    metadata is taking far less CPU time than allocating the storage!
    
    Direct reclaim should be considered extremely harmful.
    
    This is a high frequency, high throughput, CPU usage and latency
    sensitive allocation. We've got memory there, and we're using
    kvmalloc to allow memory allocation to avoid doing lots of work to
    try to do contiguous allocations.
    
    Except it still does *lots of costly work* that is unnecessary.
    
    Worse: the only way to avoid the slowpath page allocation trying to
    do compaction on costly allocations is to turn off direct reclaim
    (i.e. remove __GFP_RECLAIM_DIRECT from the gfp flags).
    
    Unfortunately, the stupid kvmalloc API then says "oh, this isn't a
    GFP_KERNEL allocation context, so you only get kmalloc!". This
    cuts off the vmalloc fallback, and this leads to almost instant OOM
    problems which ends up in filesystems deadlocks, shutdowns and/or
    kernel crashes.
    
    I want some basic kvmalloc behaviour:
    
    - kmalloc for a contiguous range with fail fast semantics - no
      compaction direct reclaim if the allocation enters the slow path.
    - run normal vmalloc (i.e. GFP_KERNEL) if kmalloc fails
    
    The really, really stupid part about this is these kvmalloc() calls
    are run under memalloc_nofs task context, so all the allocations are
    always reduced to GFP_NOFS regardless of the fact that kvmalloc
    requires GFP_KERNEL to be passed in. IOWs, we're already telling
    kvmalloc to behave differently to the gfp flags we pass in, but it
    still won't allow vmalloc to be run with anything other than
    GFP_KERNEL.
    
    So, this patch open codes the kvmalloc() in the commit path to have
    the above described behaviour. The result is we more than halve the
    CPU time spend doing kvmalloc() in this path and transaction commits
    with 64kB objects in them more than doubles. i.e. we get ~5x
    reduction in CPU usage per costly-sized kvmalloc() invocation and
    the profile looks like this:
    
      - 37.60% xlog_cil_commit
            16.01% memcpy_erms
          - 8.45% __kmalloc
             - 8.04% kmalloc_order_trace
                - 8.03% kmalloc_order
                   - 7.93% alloc_pages
                      - 7.90% __alloc_pages
                         - 4.05% __alloc_pages_slowpath.constprop.0
                            - 2.18% get_page_from_freelist
                            - 1.77% wake_all_kswapds
    ....
                                        - __wake_up_common_lock
                                           - 0.94% _raw_spin_lock_irqsave
                         - 3.72% get_page_from_freelist
                            - 2.43% _raw_spin_lock_irqsave
          - 5.72% vmalloc
             - 5.72% __vmalloc_node_range
                - 4.81% __get_vm_area_node.constprop.0
                   - 3.26% alloc_vmap_area
                      - 2.52% _raw_spin_lock
                   - 1.46% _raw_spin_lock
                  0.56% __alloc_pages_bulk
          - 4.66% kvfree
             - 3.25% vfree
                - __vfree
                   - 3.23% __vunmap
                      - 1.95% remove_vm_area
                         - 1.06% free_vmap_area_noflush
                            - 0.82% _raw_spin_lock
                         - 0.68% _raw_spin_lock
                      - 0.92% _raw_spin_lock
             - 1.40% kfree
                - 1.36% __free_pages
                   - 1.35% __free_pages_ok
                      - 1.02% _raw_spin_lock_irqsave
    
    It's worth noting that over 50% of the CPU time spent allocating
    these shadow buffers is now spent on spinlocks. So the shadow buffer
    allocation overhead is greatly reduced by getting rid of direct
    reclaim from kmalloc, and could probably be made even less costly if
    vmalloc() didn't use global spinlocks to protect it's structures.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit 219aac5d469f7c0bc8ca299dcdeab70380076d24
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Mon Jan 3 11:10:18 2022 -0800

    xfs: sysfs: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the xfs sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Cc: "Darrick J. Wong" <djwong@kernel.org>
    Cc: linux-xfs@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Darrick J. Wong <djwong@kernel.org>
    Signed-off-by: Darrick J. Wong <djwong@kernel.org>

commit 1745e857e73a2e29379013438ee271e9aadab2e0
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 11:03:35 2022 +0100

    md: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the md rdev sysfs code to use default_groups field which
    has been the preferred way since commit aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Cc: Song Liu <song@kernel.org>
    Cc: linux-raid@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Song Liu <song@kernel.org>

commit 3e718b44756e2829e7189a9504aa7a6d7f394d6c
Author: Rob Herring <robh@kernel.org>
Date:   Thu Jan 6 12:25:17 2022 -0600

    spi: dt-bindings: mediatek,spi-mtk-nor: Fix example 'interrupts' property
    
    A phandle for 'interrupts' value is wrong and should be one or more numbers.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Link: https://lore.kernel.org/r/20220106182518.1435497-9-robh@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 0dbc41621875122f68a653997eb3c3010d76e86a
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Sun Dec 26 15:38:57 2021 +0100

    ice: Use bitmap_free() to free bitmap
    
    kfree() and bitmap_free() are the same. But using the latter is more
    consistent when freeing memory allocated with bitmap_zalloc().
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit e75ed29db5315b4706953a5462f9c783532cb776
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Thu Dec 23 10:03:37 2021 +0100

    ice: Optimize a few bitmap operations
    
    When a bitmap is local to a function, it is safe to use the non-atomic
    __[set|clear]_bit(). No concurrent accesses can occur.
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Tested-by: Gurucharan G <gurucharanx.g@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit a5c259b162844f3ceaf3d082344bf6938728aca9
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Wed Nov 17 22:21:19 2021 +0100

    ice: Slightly simply ice_find_free_recp_res_idx
    
    The 'possible_idx' bitmap is set just after it is zeroed, so we can save
    the first step.
    
    The 'free_idx' bitmap is used only at the end of the function as the
    result of a bitmap xor operation. So there is no need to explicitly
    zero it before.
    
    So, slightly simply the code and remove 2 useless 'bitmap_zero()' call
    
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit c1e5da5dd4659753407534e323c0579aa79c3bd1
Author: Wojciech Drewek <wojciech.drewek@intel.com>
Date:   Tue Oct 26 12:38:40 2021 +0200

    ice: improve switchdev's slow-path
    
    In current switchdev implementation, every VF PR is assigned to
    individual ring on switchdev ctrl VSI. For slow-path traffic, there
    is a mapping VF->ring done in software based on src_vsi value (by
    calling ice_eswitch_get_target_netdev function).
    
    With this change, HW solution is introduced which is more
    efficient. For each VF, src MAC (VF's MAC) filter will be created,
    which forwards packets to the corresponding switchdev ctrl VSI queue
    based on src MAC address.
    
    This filter has to be removed and then replayed in case of
    resetting one VF. Keep information about this rule in repr->mac_rule,
    thanks to that we know which rule has to be removed and replayed
    for a given VF.
    
    In case of CORE/GLOBAL all rules are removed
    automatically. We have to take care of readding them. This is done
    by ice_replay_vsi_adv_rule.
    
    When driver leaves switchdev mode, remove all advanced rules
    from switchdev ctrl VSI. This is done by ice_rem_adv_rule_for_vsi.
    
    Flag repr->rule_added is needed because in some cases reset
    might be triggered before VF sends request to add MAC.
    
    Co-developed-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
    Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
    Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 31834aaa4e2a26d8d1f6b36703bb35cfdb8fc98c
Author: Yang Yingliang <yangyingliang@huawei.com>
Date:   Thu Jan 6 15:54:48 2022 +0800

    ACPI: pfr_update: Fix return value check in pfru_write()
    
    In case of error, memremap() returns NULL pointer not
    ERR_PTR(). The IS_ERR() test in the return value check
    should be replaced with NULL test.
    
    Fixes: 0db89fa243e5 ("ACPI: Introduce Platform Firmware Runtime Update device driver")
    Reported-by: Hulk Robot <hulkci@huawei.com>
    Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
    Acked-by: Chen Yu <yu.c.chen@intel.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit 6c4ab1b86dac3954d15c00c1a6396d60a1023fab
Author: Huang Rui <ray.huang@amd.com>
Date:   Thu Jan 6 15:43:06 2022 +0800

    x86, sched: Fix undefined reference to init_freq_invariance_cppc() build error
    
    The init_freq_invariance_cppc function is implemented in smpboot and depends on
    CONFIG_SMP.
    
      MODPOST vmlinux.symvers
      MODINFO modules.builtin.modinfo
      GEN     modules.builtin
      LD      .tmp_vmlinux.kallsyms1
    ld: drivers/acpi/cppc_acpi.o: in function `acpi_cppc_processor_probe':
    /home/ray/brahma3/linux/drivers/acpi/cppc_acpi.c:819: undefined reference to `init_freq_invariance_cppc'
    make: *** [Makefile:1161: vmlinux] Error 1
    
    See https://lore.kernel.org/lkml/484af487-7511-647e-5c5b-33d4429acdec@infradead.org/.
    
    Fixes: 41ea667227ba ("x86, sched: Calculate frequency invariance for AMD systems")
    Reported-by: kernel test robot <lkp@intel.com>
    Reported-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Huang Rui <ray.huang@amd.com>
    [ rjw: Subject edits ]
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit ca2770c65b56374374fa00c349883e67c16943de
Author: Max Gurtovoy <mgurtovoy@nvidia.com>
Date:   Wed Dec 15 15:57:21 2021 +0200

    IB/iser: Align coding style across driver
    
    The following changes were made:
    1. Align function signatures to 80 characters per line.
    2. Remove tabs for variable assignment and use 1 space instead.
    3. Don't compare to NULL in "if" clause.
    4. Remove strange indentations.
    
    This will ease on the maintenance of the driver for the future.
    
    Link: https://lore.kernel.org/r/20211215135721.3662-7-mgurtovoy@nvidia.com
    Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
    Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

commit d4cb5d3630ec135c3c1f9a2669695cd36feaf897
Merge: 5a7ac592c56c6 ce3fe7a4ac6a4
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Thu Jan 6 09:42:26 2022 -0800

    RISC-V: Clean up the defconfigs
    
    It's been a while since cleaning up the defconfigs, so I manually
    checked up on each change.  This found a handful of minor issues, which
    have been fixed in-line.

commit ce3fe7a4ac6a4ddea2aa21d34a6076e87cd206e5
Author: Palmer Dabbelt <palmer@rivosinc.com>
Date:   Fri Nov 19 08:44:13 2021 -0800

    RISC-V: defconfigs: Remove redundant K210 DT source
    
    The "k210_generic" DT has been the default in Kconfig since 67d96729a9e
    ("riscv: Update Canaan Kendryte K210 device tree"), so drop it from the
    defconfigs to avoid diff with savedefconfig.
    
    Reviewed-by: Anup Patel <anup@brainfault.org>
    Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>

commit a2e6840b37b45d04e095c47f961211b7697cb063
Author: Huang Rui <ray.huang@amd.com>
Date:   Thu Jan 6 15:43:05 2022 +0800

    cpufreq: amd-pstate: Fix Kconfig dependencies for AMD P-State
    
    The AMD P-State driver is based on ACPI CPPC function, so ACPI should be
    dependence of this driver in the kernel config.
    
    In file included from ../drivers/cpufreq/amd-pstate.c:40:0:
    ../include/acpi/processor.h:226:2: error: unknown type name ‘phys_cpuid_t’
      phys_cpuid_t phys_id; /* CPU hardware ID such as APIC ID for x86 */
      ^~~~~~~~~~~~
    ../include/acpi/processor.h:355:1: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
     phys_cpuid_t acpi_get_phys_id(acpi_handle, int type, u32 acpi_id);
     ^~~~~~~~~~~~
     phys_addr_t
      CC      drivers/rtc/rtc-rv3029c2.o
    ../include/acpi/processor.h:356:1: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
     phys_cpuid_t acpi_map_madt_entry(u32 acpi_id);
     ^~~~~~~~~~~~
     phys_addr_t
    ../include/acpi/processor.h:357:20: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
     int acpi_map_cpuid(phys_cpuid_t phys_id, u32 acpi_id);
                        ^~~~~~~~~~~~
                        phys_addr_t
    
    See https://lore.kernel.org/lkml/20e286d4-25d7-fb6e-31a1-4349c805aae3@infradead.org/.
    
    Reported-by: Randy Dunlap <rdunlap@infradead.org>
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: Huang Rui <ray.huang@amd.com>
    [ rjw: Subject edits ]
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit bdc4fd3d48e7e97dd7efc14affe384280e197071
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Thu Jan 6 10:16:05 2022 +0800

    cpufreq: amd-pstate: Fix struct amd_cpudata kernel-doc comment
    
    Add the description of @req and @boost_supported in struct amd_cpudata
    kernel-doc comment to remove warnings found by running scripts/kernel-doc,
    which is caused by using 'make W=1'.
    
    drivers/cpufreq/amd-pstate.c:104: warning: Function parameter or member
    'req' not described in 'amd_cpudata'
    drivers/cpufreq/amd-pstate.c:104: warning: Function parameter or member
    'boost_supported' not described in 'amd_cpudata'
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Acked-by: Huang Rui <ray.huang@amd.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

commit c36a2b97162720ff373985f13d819e05f1ba128d
Author: Victor Raj <victor.raj@intel.com>
Date:   Tue Oct 26 12:38:39 2021 +0200

    ice: replay advanced rules after reset
    
    ice_replay_vsi_adv_rule will replay advanced rules for a given VSI.
    Exit this function when list of rules for given recipe is empty.
    Do not add rule when given vsi_handle does not match vsi_handle
    from the rule info.
    
    Use ICE_MAX_NUM_RECIPES instead of ICE_SW_LKUP_LAST in order to find
    advanced rules as well.
    
    Signed-off-by: Victor Raj <victor.raj@intel.com>
    Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
    Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>
    Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>

commit 07f910f9b7295b6a28b337fedb56e612684c5659
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Mon Oct 4 14:46:50 2021 +0100

    mm: Remove slab from struct page
    
    All members of struct slab can now be removed from struct page.
    This shrinks the definition of struct page by 30 LOC, making
    it easier to understand.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>

commit 9cc960a164f1e8491c22d0fdb57a1a50dfe5d7c0
Merge: b01af5c0b0414 aade40b62745c
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Thu Jan 6 18:03:29 2022 +0100

    Merge branch 'core' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu into slab-struct_slab-part2-v1
    
    Merge iommu tree for a series that removes usage of struct page
    'freelist' field.

commit 3b247eeaecfefe35ecca1578b0ed48be65bc6ca3
Author: Yassine Oudjana <y.oudjana@protonmail.com>
Date:   Tue Jan 4 03:35:36 2022 +0000

    ASoC: wcd9335: Keep a RX port value for each SLIM RX mux
    
    Currently, rx_port_value is a single unsigned int that gets overwritten
    when slim_rx_mux_put() is called for any RX mux, then the same value is
    read when slim_rx_mux_get() is called for any of them. This results in
    slim_rx_mux_get() reporting the last value set by slim_rx_mux_put()
    regardless of which SLIM RX mux is in question.
    
    Turn rx_port_value into an array and store a separate value for each
    SLIM RX mux.
    
    Signed-off-by: Yassine Oudjana <y.oudjana@protonmail.com>
    Link: https://lore.kernel.org/r/20220104033356.343685-1-y.oudjana@protonmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 0c031fd37f69deb0cd8c43bbfcfccd62ebd7e952
Author: Xiao Ni <xni@redhat.com>
Date:   Fri Dec 10 17:31:15 2021 +0800

    md: Move alloc/free acct bioset in to personality
    
    bioset acct is only needed for raid0 and raid5. Therefore, md_run only
    allocates it for raid0 and raid5. However, this does not cover
    personality takeover, which may cause uninitialized bioset. For example,
    the following repro steps:
    
      mdadm -CR /dev/md0 -l1 -n2 /dev/loop0 /dev/loop1
      mdadm --wait /dev/md0
      mkfs.xfs /dev/md0
      mdadm /dev/md0 --grow -l5
      mount /dev/md0 /mnt
    
    causes panic like:
    
    [  225.933939] BUG: kernel NULL pointer dereference, address: 0000000000000000
    [  225.934903] #PF: supervisor instruction fetch in kernel mode
    [  225.935639] #PF: error_code(0x0010) - not-present page
    [  225.936361] PGD 0 P4D 0
    [  225.936677] Oops: 0010 [#1] PREEMPT SMP DEBUG_PAGEALLOC KASAN PTI
    [  225.937525] CPU: 27 PID: 1133 Comm: mount Not tainted 5.16.0-rc3+ #706
    [  225.938416] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-2.module_el8.4.0+547+a85d02ba 04/01/2014
    [  225.939922] RIP: 0010:0x0
    [  225.940289] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
    [  225.941196] RSP: 0018:ffff88815897eff0 EFLAGS: 00010246
    [  225.941897] RAX: 0000000000000000 RBX: 0000000000092800 RCX: ffffffff81370a39
    [  225.942813] RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000092800
    [  225.943772] RBP: 1ffff1102b12fe04 R08: fffffbfff0b43c01 R09: fffffbfff0b43c01
    [  225.944807] R10: ffffffff85a1e007 R11: fffffbfff0b43c00 R12: ffff88810eaaaf58
    [  225.945757] R13: 0000000000000000 R14: ffff88810eaaafb8 R15: ffff88815897f040
    [  225.946709] FS:  00007ff3f2505080(0000) GS:ffff888fb5e00000(0000) knlGS:0000000000000000
    [  225.947814] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [  225.948556] CR2: ffffffffffffffd6 CR3: 000000015aa5a006 CR4: 0000000000370ee0
    [  225.949537] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [  225.950455] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    [  225.951414] Call Trace:
    [  225.951787]  <TASK>
    [  225.952120]  mempool_alloc+0xe5/0x250
    [  225.952625]  ? mempool_resize+0x370/0x370
    [  225.953187]  ? rcu_read_lock_sched_held+0xa1/0xd0
    [  225.953862]  ? rcu_read_lock_bh_held+0xb0/0xb0
    [  225.954464]  ? sched_clock_cpu+0x15/0x120
    [  225.955019]  ? find_held_lock+0xac/0xd0
    [  225.955564]  bio_alloc_bioset+0x1ed/0x2a0
    [  225.956080]  ? lock_downgrade+0x3a0/0x3a0
    [  225.956644]  ? bvec_alloc+0xc0/0xc0
    [  225.957135]  bio_clone_fast+0x19/0x80
    [  225.957651]  raid5_make_request+0x1370/0x1b70
    [  225.958286]  ? sched_clock_cpu+0x15/0x120
    [  225.958797]  ? __lock_acquire+0x8b2/0x3510
    [  225.959339]  ? raid5_get_active_stripe+0xce0/0xce0
    [  225.959986]  ? lock_is_held_type+0xd8/0x130
    [  225.960528]  ? rcu_read_lock_sched_held+0xa1/0xd0
    [  225.961135]  ? rcu_read_lock_bh_held+0xb0/0xb0
    [  225.961703]  ? sched_clock_cpu+0x15/0x120
    [  225.962232]  ? lock_release+0x27a/0x6c0
    [  225.962746]  ? do_wait_intr_irq+0x130/0x130
    [  225.963302]  ? lock_downgrade+0x3a0/0x3a0
    [  225.963815]  ? lock_release+0x6c0/0x6c0
    [  225.964348]  md_handle_request+0x342/0x530
    [  225.964888]  ? set_in_sync+0x170/0x170
    [  225.965397]  ? blk_queue_split+0x133/0x150
    [  225.965988]  ? __blk_queue_split+0x8b0/0x8b0
    [  225.966524]  ? submit_bio_checks+0x3b2/0x9d0
    [  225.967069]  md_submit_bio+0x127/0x1c0
    [...]
    
    Fix this by moving alloc/free of acct bioset to pers->run and pers->free.
    
    While we are on this, properly handle md_integrity_register() error in
    raid0_run().
    
    Fixes: daee2024715d (md: check level before create and exit io_acct_set)
    Cc: stable@vger.kernel.org
    Acked-by: Guoqing Jiang <guoqing.jiang@linux.dev>
    Signed-off-by: Xiao Ni <xni@redhat.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit 36dacddbf0bdba86cd00f066b4d724157eeb63f1
Author: Dirk Müller <dmueller@suse.de>
Date:   Wed Jan 5 17:38:47 2022 +0100

    lib/raid6: Use strict priority ranking for pq gen() benchmarking
    
    On x86_64, currently 3 variants of AVX512, 3 variants of AVX2
    and 3 variants of SSE2 are benchmarked on initialization, taking
    between 144-153 jiffies. Testing across a hardware pool of
    various generations of intel cpus I could not find a single
    case where SSE2 won over AVX2 or AVX512. There are cases where
    AVX2 wins over AVX512 however.
    
    Change "prefer" into an integer priority field (similar to
    how recov selection works) to have more than one ranking level
    available, which is backwards compatible with existing behavior.
    
    Give AVX2/512 variants higher priority over SSE2 in order to skip
    SSE testing when AVX is available. in a AVX2/x86_64/HZ=250 case this
    saves in the order of 200ms of initialization time.
    
    Signed-off-by: Dirk Müller <dmueller@suse.de>
    Acked-by: Paul Menzel <pmenzel@molgen.mpg.de>
    Signed-off-by: Song Liu <song@kernel.org>

commit 38640c480939d56cc8b03d58642fc5261761a697
Author: Dirk Müller <dmueller@suse.de>
Date:   Wed Jan 5 17:38:46 2022 +0100

    lib/raid6: skip benchmark of non-chosen xor_syndrome functions
    
    In commit fe5cbc6e06c7 ("md/raid6 algorithms: delta syndrome functions")
    a xor_syndrome() benchmarking was added also to the raid6_choose_gen()
    function. However, the results of that benchmarking were intentionally
    discarded and did not influence the choice. It picked the
    xor_syndrome() variant related to the best performing gen_syndrome().
    
    Reduce runtime of raid6_choose_gen() without modifying its outcome by
    only benchmarking the xor_syndrome() of the best gen_syndrome() variant.
    
    For a HZ=250 x86_64 system with avx2 and without avx512 this removes
    5 out of 6 xor() benchmarks, saving 340ms of raid6 initialization time.
    
    Signed-off-by: Dirk Müller <dmueller@suse.de>
    Signed-off-by: Song Liu <song@kernel.org>

commit dd3dc5f416b7247a4b5d7bac6698be623c180572
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Sat Dec 25 18:24:11 2021 -0800

    md: fix spelling of "its"
    
    Use the possessive "its" instead of the contraction "it's"
    in printed messages.
    
    Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
    Cc: Song Liu <song@kernel.org>
    Cc: linux-raid@vger.kernel.org
    Signed-off-by: Song Liu <song@kernel.org>

commit bf2c411bb1cfc45f73eb6c55b5755bcb990063ae
Author: Vishal Verma <vverma@digitalocean.com>
Date:   Tue Dec 21 20:06:22 2021 +0000

    md: raid456 add nowait support
    
    Returns EAGAIN in case the raid456 driver would block waiting for reshape.
    
    Reviewed-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Vishal Verma <vverma@digitalocean.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2
Author: Vishal Verma <vverma@digitalocean.com>
Date:   Tue Dec 21 20:06:21 2021 +0000

    md: raid10 add nowait support
    
    This adds nowait support to the RAID10 driver. Very similar to
    raid1 driver changes. It makes RAID10 driver return with EAGAIN
    for situations where it could wait for eg:
    
      - Waiting for the barrier,
      - Reshape operation,
      - Discard operation.
    
    wait_barrier() and regular_request_wait() fn are modified to return bool
    to support error for wait barriers. They returns true in case of wait
    or if wait is not required and returns false if wait was required
    but not performed to support nowait.
    
    Reviewed-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Vishal Verma <vverma@digitalocean.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit 5aa705039c4fca84575539bfa2b8a28454a3d2ca
Author: Vishal Verma <vverma@digitalocean.com>
Date:   Tue Dec 21 20:06:20 2021 +0000

    md: raid1 add nowait support
    
    This adds nowait support to the RAID1 driver. It makes RAID1 driver
    return with EAGAIN for situations where it could wait for eg:
    
      - Waiting for the barrier,
    
    wait_barrier() fn is modified to return bool to support error for
    wait barriers. It returns true in case of wait or if wait is not
    required and returns false if wait was required but not performed
    to support nowait.
    
    Reviewed-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Vishal Verma <vverma@digitalocean.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit f51d46d0e7cb5b8494aa534d276a9d8915a2443d
Author: Vishal Verma <vverma@digitalocean.com>
Date:   Tue Dec 21 20:06:19 2021 +0000

    md: add support for REQ_NOWAIT
    
    commit 021a24460dc2 ("block: add QUEUE_FLAG_NOWAIT") added support
    for checking whether a given bdev supports handling of REQ_NOWAIT or not.
    Since then commit 6abc49468eea ("dm: add support for REQ_NOWAIT and enable
    it for linear target") added support for REQ_NOWAIT for dm. This uses
    a similar approach to incorporate REQ_NOWAIT for md based bios.
    
    This patch was tested using t/io_uring tool within FIO. A nvme drive
    was partitioned into 2 partitions and a simple raid 0 configuration
    /dev/md0 was created.
    
    md0 : active raid0 nvme4n1p1[1] nvme4n1p2[0]
          937423872 blocks super 1.2 512k chunks
    
    Before patch:
    
    $ ./t/io_uring /dev/md0 -p 0 -a 0 -d 1 -r 100
    
    Running top while the above runs:
    
    $ ps -eL | grep $(pidof io_uring)
    
      38396   38396 pts/2    00:00:00 io_uring
      38396   38397 pts/2    00:00:15 io_uring
      38396   38398 pts/2    00:00:13 iou-wrk-38397
    
    We can see iou-wrk-38397 io worker thread created which gets created
    when io_uring sees that the underlying device (/dev/md0 in this case)
    doesn't support nowait.
    
    After patch:
    
    $ ./t/io_uring /dev/md0 -p 0 -a 0 -d 1 -r 100
    
    Running top while the above runs:
    
    $ ps -eL | grep $(pidof io_uring)
    
      38341   38341 pts/2    00:10:22 io_uring
      38341   38342 pts/2    00:10:37 io_uring
    
    After running this patch, we don't see any io worker thread
    being created which indicated that io_uring saw that the
    underlying device does support nowait. This is the exact behaviour
    noticed on a dm device which also supports nowait.
    
    For all the other raid personalities except raid0, we would need
    to train pieces which involves make_request fn in order for them
    to correctly handle REQ_NOWAIT.
    
    Reviewed-by: Jens Axboe <axboe@kernel.dk>
    Signed-off-by: Vishal Verma <vverma@digitalocean.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit a92ce0feffeed8b91f02dac85246d1205e4a64b6
Author: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Date:   Fri Dec 17 10:29:55 2021 +0100

    md: drop queue limitation for RAID1 and RAID10
    
    As suggested by Neil Brown[1], this limitation seems to be
    deprecated.
    
    With plugging in use, writes are processed behind the raid thread
    and conf->pending_count is not increased. This limitation occurs only
    if caller doesn't use plugs.
    
    It can be avoided and often it is (with plugging). There are no reports
    that queue is growing to enormous size so remove queue limitation for
    non-plugged IOs too.
    
    [1] https://lore.kernel.org/linux-raid/162496301481.7211.18031090130574610495@noble.neil.brown.name
    
    Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
    Signed-off-by: Song Liu <song@kernel.org>

commit 770b1d216d7371c94c88713824da4be4bc39a4e0
Author: Davidlohr Bueso <dave@stgolabs.net>
Date:   Mon Nov 15 17:23:17 2021 -0800

    md/raid5: play nice with PREEMPT_RT
    
    raid_run_ops() relies on the implicitly disabled preemption for
    its percpu ops, although this is really about CPU locality. This
    breaks RT semantics as it can take regular (and thus sleeping)
    spinlocks, such as stripe_lock.
    
    Add a local_lock such that non-RT does not change and continues
    to be just map to preempt_disable/enable, but makes RT happy as
    the region will use a per-CPU spinlock and thus be preemptible
    and still guarantee CPU locality.
    
    Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
    Signed-off-by: Song Liu <songliubraving@fb.com>

commit 7112550890d7e415188a3351ec0a140be60f6deb
Author: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
Date:   Thu Jan 6 20:35:21 2022 +0530

    ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
    
    RT1019 components was initially registered with i2c1 and i2c2 but
    now changed to i2c0 and i2c1 in most of our AMD platforms. Change
    default rt1019 components to 10EC1019:00 and 10EC1019:01 which is
    aligned with most of AMD machines.
    
    Any exception to rt1019 device ids in near future board design can
    be handled using dmi based quirk for that machine.
    
    Signed-off-by: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
    Link: https://lore.kernel.org/r/20220106150525.396170-1-AjitKumar.Pandey@amd.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit f8039ea55d4ccac2238a247a574f0acb3bc1dc4b
Author: Vinod Koul <vkoul@kernel.org>
Date:   Mon Jan 3 12:41:18 2022 +0530

    spi: qcom: geni: handle timeout for gpi mode
    
    We missed adding handle_err for gpi mode, so add a new function
    spi_geni_handle_err() which would call handle_fifo_timeout() or newly
    added handle_gpi_timeout() based on mode
    
    Fixes: b59c122484ec ("spi: spi-geni-qcom: Add support for GPI dma")
    Reported-by: Douglas Anderson <dianders@chromium.org>
    Reviewed-by: Douglas Anderson <dianders@chromium.org>
    Signed-off-by: Vinod Koul <vkoul@kernel.org>
    Link: https://lore.kernel.org/r/20220103071118.27220-2-vkoul@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 74b86d6af81be73bb74995ebeba74417e84b6b6f
Author: Vinod Koul <vkoul@kernel.org>
Date:   Mon Jan 3 12:41:17 2022 +0530

    spi: qcom: geni: set the error code for gpi transfer
    
    Before we invoke spi_finalize_current_transfer() in
    spi_gsi_callback_result() we should set the spi->cur_msg->status as
    appropriate (0 for success, error otherwise).
    
    The helps to return error on transfer and not wait till it timesout on
    error
    
    Fixes: b59c122484ec ("spi: spi-geni-qcom: Add support for GPI dma")
    Signed-off-by: Vinod Koul <vkoul@kernel.org>
    Reviewed-by: Douglas Anderson <dianders@chromium.org>
    Link: https://lore.kernel.org/r/20220103071118.27220-1-vkoul@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 4b46daf028e2f4a051047791b8a3bfc9bc37d684
Author: Stefan Sauer <st_kost@gmx.de>
Date:   Thu Jan 6 13:38:21 2022 +0100

    ALSA: virmidi: Remove duplicated code
    
    seq_virmidi.c: snd_virmidi_new() is already setting seq_mode to
    SNDRV_VIRMIDI_SEQ_DISPATCH.
    
    Signed-off-by: Stefan Sauer <st_kost@gmx.de>
    Link: https://lore.kernel.org/r/20220106123821.16691-1-st_kost@gmx.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 7560ee032b3f87fa5c4f03e99a064c6cd326951e
Author: Stefan Sauer <st_kost@gmx.de>
Date:   Thu Jan 6 13:41:45 2022 +0100

    ALSA: seq: virmidi: Add a drain operation
    
    If a driver does not supply a drain operation for outputs, a default code
    path will execute msleep(50). Especially for a virtual midi device
    this severely limmits the throughput.
    
    This implementation for the virtual midi driver simply flushes the output
    workqueue.
    
    Signed-off-by: Stefan Sauer <st_kost@gmx.de>
    Link: https://lore.kernel.org/r/20220106124145.17254-1-st_kost@gmx.de
    Signed-off-by: Takashi Iwai <tiwai@suse.de>

commit 93a770b7e16772530196674ffc79bb13fa927dc6
Author: Lukas Wunner <lukas@wunner.de>
Date:   Sun Jan 2 18:52:44 2022 +0100

    serial: core: Keep mctrl register state and cached copy in sync
    
    struct uart_port contains a cached copy of the Modem Control signals.
    It is used to skip register writes in uart_update_mctrl() if the new
    signal state equals the old signal state.  It also avoids a register
    read to obtain the current state of output signals.
    
    When a uart_port is registered, uart_configure_port() changes signal
    state but neglects to keep the cached copy in sync.  That may cause
    a subsequent register write to be incorrectly skipped.  Fix it before
    it trips somebody up.
    
    This behavior has been present ever since the serial core was introduced
    in 2002:
    https://git.kernel.org/history/history/c/33c0d1b0c3eb
    
    So far it was never an issue because the cached copy is initialized to 0
    by kzalloc() and when uart_configure_port() is executed, at most DTR has
    been set by uart_set_options() or sunsu_console_setup().  Therefore,
    a stable designation seems unnecessary.
    
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/bceeaba030b028ed810272d55d5fc6f3656ddddb.1641129752.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 195437d14fb424a2ee50d51441181f16fd549789
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 4 19:24:45 2022 +0100

    serial: stm32: correct loop for dma error handling
    
    In this error handling, "transmit_chars_dma" function will call
    "transmit_chars_pio" once per characters. But "transmit_chars_pio" will
    continue to send characters while xmit buffer is not empty.
    
    Remove this useless loop, one call is sufficient.
    
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220104182445.4195-5-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 2a3bcfe03725472607110507b6860d823e0deb41
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 4 19:24:44 2022 +0100

    serial: stm32: fix flow control transfer in DMA mode
    
    If flow control is enabled, framework will call stop_tx to
    pause transfer and then call start_tx to resume transfer.
    
    Clear USART_CR3_DMAT bit in stop_tx ops to pause DMA transfer.
    
    Signed-off-by: Erwan Le Ray <erwan.leray@foss.st.com>
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220104182445.4195-4-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 9a135f16d228857c5c1212a58050196883343d1e
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 4 19:24:43 2022 +0100

    serial: stm32: rework TX DMA state condition
    
    TX DMA state condition is handled by tx_dma_busy boolean.
    This boolean is set when dma descriptor is requested and reset when dma
    channel is stopped (dma_terminate).
    
    In stm32_usart_serial_remove(), stm32_usart_stop_tx() and
    stm32_usart_transmit_chars_dma() fallback error case, DMA channel is
    stopped but tx_dma_busy is not handled.
    
    Rework the driver by using two new functions to solve this issue:
    - stm32_usart_tx_dma_started return true if DMA TX have a descriptor.
    - stm32_usart_tx_dma_enabled return true if DMAT bit is set.
    
    stm32_usart_tx_dma_started uses tx_dma_busy flag to prevent dual DMA
    transaction at the same time. This flag is set when a DMA transaction
    begins and is unset when dmaengine_terminate_async function is called.
    A new DMA transaction cannot be created if this flag is set.
    
    Create a new function "stm32_usart_tx_dma_terminate" to be sure the flag
    is unset after each call of dmaengine_terminate_async.
    
    Signed-off-by: Erwan Le Ray <erwan.leray@foss.st.com>
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220104182445.4195-3-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 56a23f9319e86e1d62a109896e2c7e52c414e67d
Author: Valentin Caron <valentin.caron@foss.st.com>
Date:   Tue Jan 4 19:24:42 2022 +0100

    serial: stm32: move tx dma terminate DMA to shutdown
    
    Terminate DMA transaction and clear CR3_DMAT when shutdown is requested,
    instead of when remove is requested. If DMA transfer is not stopped in
    shutdown ops, driver will fail to start a new DMA transfer after next
    startup ops.
    
    Fixes: 3489187204eb ("serial: stm32: adding dma support")
    Signed-off-by: Erwan Le Ray <erwan.leray@foss.st.com>
    Signed-off-by: Valentin Caron <valentin.caron@foss.st.com>
    Link: https://lore.kernel.org/r/20220104182445.4195-2-valentin.caron@foss.st.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 49a80424e3ec23ee2748f360348e167d5c748256
Author: Lukas Wunner <lukas@wunner.de>
Date:   Sun Jan 2 18:49:44 2022 +0100

    serial: pl011: Drop redundant DTR/RTS preservation on close/open
    
    Commit d8d8ffa47783 ("amba-pl011: do not disable RTS during shutdown")
    amended the PL011 serial driver to leave DTR/RTS polarity untouched on
    tty close.  That change made sense.
    
    But the commit also added code to save DTR/RTS state to an internal
    variable on tty close and restore it on tty open.  That part of the
    commit makes less sense:  The driver has no ->pm() callback, so the uart
    remains powered after tty close and automatically preserves register
    state, including DTR/RTS.
    
    Saving and restoring registers isn't the job of the ->startup() and
    ->shutdown() callbacks anyway.  Rather, it should happen in ->pm().
    
    Additionally, after pl011_startup() restores the state, the serial core
    overrides it in uart_port_dtr_rts() if a baud rate has been set:
    
    tty_port_open()
      uart_port_activate()
        uart_startup()
          uart_port_startup()
            pl011_startup()       # restores DTR/RTS from uap->old_cr
      tty_port_block_til_ready()
        tty_port_raise_dtr_rts    # if (C_BAUD(tty))
          uart_dtr_rts()
            uart_port_dtr_rts()   # raises DTR/RTS
    
    The serial core also overrides DTR/RTS on tty close in uart_shutdown()
    if C_HUPCL(tty) is set.  So a user-defined DTR/RTS polarity won't
    survive a close/open cycle anyway, unless the user has set the baud rate
    to zero and disabled hupcl on the tty.
    
    Bottom line is, the code to save and restore DTR/RTS has no effect.
    Remove it.
    
    Cc: Linus Walleij <linus.walleij@linaro.org>
    Cc: Russell King <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/e22089ab49e6e78822c50c8c4db46bf3ee885623.1641129328.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e368cc656fd6d0075f1c3ab9676e2001451e3e04
Author: Lukas Wunner <lukas@wunner.de>
Date:   Sun Jan 2 18:45:44 2022 +0100

    serial: pl011: Drop CR register reset on set_termios
    
    pl011_set_termios() briefly resets the CR register to zero, thereby
    glitching DTR/RTS signals.  With rs485 this may result in the bus being
    occupied for no reason.
    
    Where does this register write originate from?
    
    The PL011 driver was forked from the PL010 driver in 2004:
    https://git.kernel.org/history/history/c/157c0342e591
    
    Until this commit, the PL010 driver's IRQ handler ambauart_int()
    modified the CR register without holding the port spinlock.
    
    ambauart_set_termios() also modified that register.  To prevent
    concurrent read-modify-writes by the IRQ handler and to prevent
    transmission while changing baudrate, ambauart_set_termios() had to
    disable interrupts.  On the PL010, that is achieved by writing zero to
    the CR register.
    
    However, on the PL011, interrupts are disabled in the IMSC register,
    not in the CR register.
    
    Additionally, the commit amended both the PL010 and PL011 driver to
    acquire the port spinlock in the IRQ handler, obviating the need to
    disable interrupts in ->set_termios().
    
    So the CR register write is obsolete for two reasons.  Drop it.
    
    Cc: Russell King <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/f49f945375f5ccb979893c49f1129f51651ac738.1641129062.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 08a0c6dff91c965e39905cf200d22db989203ccb
Author: Lukas Wunner <lukas@wunner.de>
Date:   Sun Jan 2 18:42:44 2022 +0100

    serial: pl010: Drop CR register reset on set_termios
    
    pl010_set_termios() briefly resets the CR register to zero.
    
    Where does this register write come from?
    
    The PL010 driver's IRQ handler ambauart_int() originally modified the CR
    register without holding the port spinlock.  ambauart_set_termios() also
    modified that register.  To prevent concurrent read-modify-writes by the
    IRQ handler and to prevent transmission while changing baudrate,
    ambauart_set_termios() had to disable interrupts.  That is achieved by
    writing zero to the CR register.
    
    However in 2004 the PL010 driver was amended to acquire the port
    spinlock in the IRQ handler, obviating the need to disable interrupts in
    ->set_termios():
    https://git.kernel.org/history/history/c/157c0342e591
    
    That rendered the CR register write obsolete.  Drop it.
    
    Cc: Russell King <rmk+kernel@armlinux.org.uk>
    Signed-off-by: Lukas Wunner <lukas@wunner.de>
    Link: https://lore.kernel.org/r/fcaff16e5b1abb4cc3da5a2879ac13f278b99ed0.1641128728.git.lukas@wunner.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 556172fabd226ba14b70c1740d0826a4717473dc
Author: Alyssa Ross <hi@alyssa.is>
Date:   Tue Jan 4 13:10:28 2022 +0000

    serial: liteuart: fix MODULE_ALIAS
    
    modprobe can't handle spaces in aliases.
    
    Fixes: 1da81e5562fa ("drivers/tty/serial: add LiteUART driver")
    Signed-off-by: Alyssa Ross <hi@alyssa.is>
    Link: https://lore.kernel.org/r/20220104131030.1674733-1-hi@alyssa.is
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 0e479b460e342c5fe138391b29d7bfa0a6204af2
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date:   Wed Jan 5 18:07:03 2022 +0000

    serial: 8250_bcm7271: Fix return error code in case of dma_alloc_coherent() failure
    
    In case of dma_alloc_coherent() failure return -ENOMEM instead of
    returning -EINVAL.
    
    Reported-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
    Acked-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
    Link: https://lore.kernel.org/r/20220105180704.8989-1-prabhakar.mahadev-lad.rj@bp.renesas.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 663d8fb0f84c0f3aade8974fbf3a2ddb255f54a5
Author: William Breathitt Gray <vilhelm.gray@gmail.com>
Date:   Wed Jan 5 18:30:52 2022 +0900

    counter: 104-quad-8: Fix use-after-free by quad8_irq_handler
    
    On unbind an irq might be pending which results in quad8_irq_handler()
    calling counter_push_event() for a counter that is already unregistered.
    This patch fixes that situation by passing the struct counter_device dev
    to devm_request_irq() rather than the parent's so that the irq handler
    is cleaned before the counter is unregistered.
    
    Fixes: 7aa2ba0df651 ("counter: 104-quad-8: Add IRQ support for the ACCES 104-QUAD-8")
    Cc: Syed Nayyar Waris <syednwaris@gmail.com>
    Reported-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
    Link: https://lore.kernel.org/r/20220105093052.258791-1-vilhelm.gray@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit eaac0b590a47c717ef36cbfd1c528cd154c965a1
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Jan 6 11:02:31 2022 +0100

    dm sysfs: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the dm sysfs code to use default_groups field which has
    been the preferred way since aa30f47cf666 ("kobject: Add support for
    default attribute groups to kobj_type") so that we can soon get rid of
    the obsolete default_attrs field.
    
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>

commit f069c7ab6cfb07edf9e3dc2071928225587794f1
Author: Kees Cook <keescook@chromium.org>
Date:   Mon Dec 13 14:33:25 2021 -0800

    dm integrity: Use struct_group() to zero struct journal_sector
    
    In preparation for FORTIFY_SOURCE performing compile-time and run-time
    field bounds checking for memset(), avoid intentionally writing across
    neighboring fields.
    
    Add struct_group() to mark region of struct journal_sector that should be
    initialized to zero.
    
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>

commit 0589e8889dce8e0f0ea5bbf757f38865e2a469c1
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Dec 31 08:04:25 2021 +0000

    drivers/firmware: Add missing platform_device_put() in sysfb_create_simplefb
    
    Add the missing platform_device_put() before return from
    sysfb_create_simplefb() in the error handling case.
    
    Fixes: 8633ef82f101 ("drivers/firmware: consolidate EFI framebuffer setup for all arches")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20211231080431.15385-1-linmq006@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 358fcf5ddbec4e6706405847d6a666f5933a6c25
Author: Michal Suchanek <msuchanek@suse.de>
Date:   Tue Jan 4 18:05:05 2022 +0100

    debugfs: lockdown: Allow reading debugfs files that are not world readable
    
    When the kernel is locked down the kernel allows reading only debugfs
    files with mode 444. Mode 400 is also valid but is not allowed.
    
    Make the 444 into a mask.
    
    Fixes: 5496197f9b08 ("debugfs: Restrict debugfs when the kernel is locked down")
    Signed-off-by: Michal Suchanek <msuchanek@suse.de>
    Link: https://lore.kernel.org/r/20220104170505.10248-1-msuchanek@suse.de
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 00eb74ea2c14418042347eaa34c6b73ac6ec1e76
Author: Lu Baolu <baolu.lu@linux.intel.com>
Date:   Fri Dec 31 11:39:01 2021 +0800

    driver core: Make bus notifiers in right order in really_probe()
    
    If a driver cannot be bound to a device, the correct bus notifier order
    should be:
    
     - BUS_NOTIFY_BIND_DRIVER: driver is about to be bound
     - BUS_NOTIFY_DRIVER_NOT_BOUND: driver failed to be bound
    
    or no notifier if the failure happens before the actual binding.
    
    The really_probe() notifies a BUS_NOTIFY_DRIVER_NOT_BOUND event without
    a BUS_NOTIFY_BIND_DRIVER if .dma_configure() returns failure. This
    change makes the notifiers in order.
    
    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Link: https://lore.kernel.org/r/20211231033901.2168664-3-baolu.lu@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 885e50253bfd6750327a265405461496d6af1639
Author: Lu Baolu <baolu.lu@linux.intel.com>
Date:   Fri Dec 31 11:39:00 2021 +0800

    driver core: Move driver_sysfs_remove() after driver_sysfs_add()
    
    The driver_sysfs_remove() should be called after driver_sysfs_add() in
    really_probe(). The out-of-order driver_sysfs_remove() tries to remove
    some nonexistent nodes under the device and driver sysfs nodes. This is
    allowed, hence this change doesn't fix any problem, just a cleanup.
    
    Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
    Link: https://lore.kernel.org/r/20211231033901.2168664-2-baolu.lu@linux.intel.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 33812fc7c8d77a43b7e2bf36a0d5a57c277a4b0c
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date:   Tue Dec 28 22:09:17 2021 +0100

    HID: magicmouse: Fix an error handling path in magicmouse_probe()
    
    If the timer introduced by the commit below is started, then it must be
    deleted in the error handling of the probe. Otherwise it would trigger
    once the driver is no more.
    
    Fixes: 0b91b4e4dae6 ("HID: magicmouse: Report battery level over USB")
    Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    Tested-by: José Expósito <jose.exposito89@gmail.com>
    Reported-by: <syzbot+a437546ec71b04dfb5ac@syzkaller.appspotmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 3809fe479861194e310c23ed48b010c7c0f72d22
Author: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Date:   Thu Dec 16 10:21:57 2021 +0100

    HID: address kernel-doc warnings
    
    The command ./scripts/kernel-doc -none include/linux/hid.h reports:
    
      include/linux/hid.h:818: warning: cannot understand function prototype: 'struct hid_ll_driver '
      include/linux/hid.h:1135: warning: expecting prototype for hid_may_wakeup(). Prototype was for hid_hw_may_wakeup() instead
    
    Address those kernel-doc warnings.
    
    Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 98b6b62cd5569a158868b62dc7866b5aae5d9a38
Author: Yang Li <yang.lee@linux.alibaba.com>
Date:   Thu Dec 16 12:01:46 2021 +0800

    HID: intel-ish-hid: ishtp-fw-loader: Fix a kernel-doc formatting issue
    
    This function had kernel-doc that not used a hash to separate
    the function name from the one line description.
    
    The warning was found by running scripts/kernel-doc, which is
    caused by using 'make W=1'.
    
    drivers/hid/intel-ish-hid/ishtp-fw-loader.c:271: warning: This comment
    starts with '/**', but isn't a kernel-doc comment. Refer
    Documentation/doc-guide/kernel-doc.rst
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit bcad6d1bd9177740176ea79f6d0fc9f5b07e0c43
Author: Ye Xiang <xiang.ye@intel.com>
Date:   Fri Dec 17 15:45:41 2021 +0800

    HID: intel-ish-hid: ipc: Specify no cache snooping on TGL and ADL
    
    Specify that both TGL and ADL don't support DMA cache snooping.
    
    Signed-off-by: Ye Xiang <xiang.ye@intel.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit aa320fdbbbb482c19100f51461bd0069753ce3d7
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Wed Jan 5 18:29:15 2022 +0100

    HID: hid-uclogic-params: Invalid parameter check in uclogic_params_frame_init_v1_buttonpad
    
    The function performs a check on the hdev input parameters, however, it
    is used before the check.
    
    Initialize the udev variable after the sanity check to avoid a
    possible NULL pointer dereference.
    
    Fixes: 9614219e9310e ("HID: uclogic: Extract tablet parameter discovery into a module")
    Addresses-Coverity-ID: 1443763 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit ff6b548afe4d9d1ff3a0f6ef79e8cbca25d8f905
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Wed Jan 5 18:29:14 2022 +0100

    HID: hid-uclogic-params: Invalid parameter check in uclogic_params_huion_init
    
    The function performs a check on its input parameters, however, the
    hdev parameter is used before the check.
    
    Initialize the stack variables after checking the input parameters to
    avoid a possible NULL pointer dereference.
    
    Fixes: 9614219e9310e ("HID: uclogic: Extract tablet parameter discovery into a module")
    Addresses-Coverity-ID: 1443804 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 0a94131d6920916ccb6a357037c535533af08819
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Wed Jan 5 18:29:13 2022 +0100

    HID: hid-uclogic-params: Invalid parameter check in uclogic_params_get_str_desc
    
    The function performs a check on the hdev input parameters, however, it
    is used before the check.
    
    Initialize the udev variable after the sanity check to avoid a
    possible NULL pointer dereference.
    
    Fixes: 9614219e9310e ("HID: uclogic: Extract tablet parameter discovery into a module")
    Addresses-Coverity-ID: 1443827 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit f364c571a5c77e96de2d32062ff019d6b8d2e2bc
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Wed Jan 5 18:29:12 2022 +0100

    HID: hid-uclogic-params: Invalid parameter check in uclogic_params_init
    
    The function performs a check on its input parameters, however, the
    hdev parameter is used before the check.
    
    Initialize the stack variables after checking the input parameters to
    avoid a possible NULL pointer dereference.
    
    Fixes: 9614219e9310e ("HID: uclogic: Extract tablet parameter discovery into a module")
    Addresses-Coverity-ID: 1443831 ("Null pointer dereference")
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 601a5bc1aeef772ab1f47582fd322957799f5ab5
Author: Pavel Hofman <pavel.hofman@ivitera.com>
Date:   Wed Jan 5 11:46:43 2022 +0100

    usb: gadget: u_audio: Subdevice 0 for capture ctls
    
    Both capture and playback alsa devices use subdevice 0. Yet capture-side
    ctls are defined for subdevice 1. The patch sets subdevice 0 for them.
    
    Fixes: 02de698ca812 ("usb: gadget: u_audio: add bi-directional volume and mute support")
    Signed-off-by: Pavel Hofman <pavel.hofman@ivitera.com>
    Link: https://lore.kernel.org/r/20220105104643.90125-1-pavel.hofman@ivitera.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit f2f69bf65df12176843ca11eab99949ba69e128b
Author: John Keeping <john@metanate.com>
Date:   Tue Jan 4 18:32:42 2022 +0000

    usb: gadget: u_audio: fix calculations for small bInterval
    
    If bInterval is 1, then p_interval is 8000 and p_interval_mil is 8E9,
    which is too big for a 32-bit value.  While the storage is indeed
    64-bit, this value is used as the divisor in do_div() which will
    truncate it into a uint32_t leading to incorrect calculated values.
    
    Switch back to keeping the base value in struct snd_uac_chip which fits
    easily into an int, meaning that the division can be done in two steps
    with the divisor fitting safely into a uint32_t on both steps.
    
    Fixes: 6fec018a7e70 ("usb: gadget: u_audio.c: Adding Playback Pitch ctl for sync playback")
    Tested-by: Pavel Hofman <pavel.hofman@ivitera.com>
    Signed-off-by: John Keeping <john@metanate.com>
    Link: https://lore.kernel.org/r/20220104183243.718258-1-john@metanate.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 92ef98a4caacad6d4a1490dda45d81ae5ccf5bc9
Author: John Keeping <john@metanate.com>
Date:   Thu Jan 6 11:57:31 2022 +0000

    usb: dwc2: gadget: initialize max_speed from params
    
    DWC2 may be paired with a full-speed PHY which is not capable of
    high-speed operation.  Report this correctly to the gadget core by
    setting max_speed from the core parameters.
    
    Prior to commit 5324bad66f09f ("usb: dwc2: gadget: implement
    udc_set_speed()") this didn't cause the hardware to be configured
    incorrectly, although the speed may have been reported incorrectly.  But
    after that commit params.speed is updated based on a value passed in by
    the gadget core which may set it to a faster speed than is supported by
    the hardware.  Initialising the max_speed parameter ensures the speed
    passed to dwc2_gadget_set_speed() will be one supported by the hardware.
    
    Fixes: 5324bad66f09f ("usb: dwc2: gadget: implement udc_set_speed()")
    Acked-by: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
    Signed-off-by: John Keeping <john@metanate.com>
    Link: https://lore.kernel.org/r/20220106115731.1473909-1-john@metanate.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 34146c68083f1aef6709196b3dc888c1ceffd357
Author: Dinh Nguyen <dinguyen@kernel.org>
Date:   Tue Jan 4 07:59:22 2022 -0600

    usb: dwc2: do not gate off the hardware if it does not support clock gating
    
    We should not be clearing the HCD_FLAG_HW_ACCESSIBLE bit if the hardware
    does not support clock gating.
    
    Fixes: 50fb0c128b6e ("usb: dwc2: Add clock gating entering flow by system suspend")
    Acked-by: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
    Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
    Link: https://lore.kernel.org/r/20220104135922.734776-1-dinguyen@kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit b52fe2dbb3e655eb1483000adfab68a219549e13
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Wed Dec 22 11:18:23 2021 +0000

    usb: dwc3: qcom: Fix NULL vs IS_ERR checking in dwc3_qcom_probe
    
    Since the acpi_create_platform_device() function may return error
    pointers, dwc3_qcom_create_urs_usb_platdev() function may return error
    pointers too. Using IS_ERR_OR_NULL() to check the return value to fix this.
    
    Fixes: c25c210f590e ("usb: dwc3: qcom: add URS Host support for sdm845 ACPI boot")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Link: https://lore.kernel.org/r/20211222111823.22887-1-linmq006@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit fa783154524a71ab74e293cd8251155e5971952b
Author: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
Date:   Tue Jan 4 17:09:39 2022 +0100

    staging: r8188eu: rename camelcase variable uintPeerChannel
    
    Rename camelcase hungarian notated variable uintPeerChannel into
    peer_channel.
    
    Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
    Link: https://lore.kernel.org/r/20220104160945.460113-1-alb3rt0.m3rciai@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 27aad6cef4b54f8fa8ea5cf0ef8acf2aa8058992
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:26 2022 +0100

    staging: r8188eu: make BW20_24G_Diff a 1-D array
    
    Make BW20_24G_Diff a one-dimensional array. This driver uses only
    BW20_24G_Diff[0].
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-8-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 2c02b728b648bab403fc9316fc984b5eab643395
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:25 2022 +0100

    staging: r8188eu: make OFDM_24G_Diff a 1-D array
    
    Make OFDM_24G_Diff one-dimensional array. This driver uses only
    OFDM_24G_Diff[0].
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-7-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 41b7c4edff83bb2d8f622a0b426fefc6b076c42b
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:24 2022 +0100

    staging: r8188eu: BW40_24G_Diff is set but not used
    
    The BW40_24G_Diff array is set but not used. Remove it.
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-6-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit ef2efa86392a93c1d31a66dd8748eeaf78cb8ae0
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:23 2022 +0100

    staging: r8188eu: CCK_24G_Diff is set but not used
    
    The CCK_24G_Diff array is set but not used. Remove it.
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-5-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit eeb35e4a2742e2a977d3d540873c25bd50dd2fbc
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:22 2022 +0100

    staging: r8188eu: make Index24G_BW40_Base a 1-D array
    
    Make Index24G_BW40_Base a one-dimensional array. This driver uses
    only Index24G_BW40_Base[0].
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-4-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit e9a14094c724ab4d519882d6f67ba3e6b9cc38be
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:21 2022 +0100

    staging: r8188eu: make Index24G_CCK_Base a 1-D array
    
    Make Index24G_CCK_Base a one-dimensional array. This driver uses only
    Index24G_CCK_Base[0].
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-3-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d1dfe7fb11598a9575750a711bd2d0d06a2c1325
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Jan 5 09:34:20 2022 +0100

    staging: r8188eu: rfPath is always 0
    
    The rfPath variable in Hal_ReadTxPowerInfo88E is always 0. Remove the
    variable and use 0 directly.
    
    Acked-by: Michael Straube <straube.linux@gmail.com>
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Link: https://lore.kernel.org/r/20220105083426.177128-2-martin@kaiser.cx
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 6a0d9b79bff6ff64bf65b66776af88b21c1ff581
Author: Michael Straube <straube.linux@gmail.com>
Date:   Tue Jan 4 10:07:32 2022 +0100

    staging: r8188eu: remove unneeded parameter from rtl8188e_SetHalODMVar
    
    Function rtl8188e_SetHalODMVar is always called with HAL_ODM_STA_INFO.
    Remove the unneeded parameter eVariable from the function.
    
    Signed-off-by: Michael Straube <straube.linux@gmail.com>
    Link: https://lore.kernel.org/r/20220104090732.13994-1-straube.linux@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 6b2ad1636995895dba74f9c65f4a5cb22fd3f677
Author: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Date:   Tue Jan 4 12:26:16 2022 +1300

    staging: pi433: add comment to rx_lock mutex definition
    
    Checkpatch reports: CHECK: struct mutex definition without comment.
    Fix this by documenting what rx_mutex struct is used for in pi433
    driver.
    
    Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
    Link: https://lore.kernel.org/r/20220103232616.GA11161@mail.google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 70d8e20c24a4ef42ee200cc7b7b93a01f0ebaa0e
Author: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Date:   Tue Jan 4 11:23:34 2022 +1300

    staging: pi433: fix frequency deviation check
    
    rf69 datasheet states that frequency deviation must exceed 600 Hz but
    also that frequency deviation + (bitrate / 2) should be less than equal
    to 500 kHz to ensure proper modulation.
    
    This patch validates that both conditions are met so RF intersymbol
    interference is less likely to happen due to misconfiguration of the uC
    
    Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
    Link: https://lore.kernel.org/r/20220103222334.GA6814@mail.google.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 72279d17df54d5e4e7910b39c61a3f3464e36633
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date:   Wed Jan 5 14:59:53 2022 -0800

    Bluetooth: hci_event: Rework hci_inquiry_result_with_rssi_evt
    
    This rework the handling of hci_inquiry_result_with_rssi_evt to not use
    a union to represent the different inquiry responses.
    
    Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
    Tested-by: Soenke Huster <soenke.huster@eknoes.de>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit 709c81b55c6aa74a6cdad27bdc224f50962b6ad9
Author: Rob Herring <robh@kernel.org>
Date:   Wed Jan 5 12:32:33 2022 -0600

    spi: spi-mux: Add reference to spi-peripheral-props.yaml schema
    
    The spi-mux serves as both a SPI peripheral and controller, so add a
    reference to spi-peripheral-props.yaml in addition to
    spi-controller.yaml. This is necessary to avoid unevaluatedProperties
    warnings once those are fully enabled.
    
    Signed-off-by: Rob Herring <robh@kernel.org>
    Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
    Link: https://lore.kernel.org/r/20220105183234.3426649-1-robh@kernel.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 14e2976fbabdacb01335d7f91eeebbc89c67ddb1
Author: Konrad Dybcio <konrad.dybcio@somainline.org>
Date:   Thu Dec 30 03:34:42 2021 +0100

    regulator: qcom_smd: Align probe function with rpmh-regulator
    
    The RPMh regulator driver is much newer and gets more attention, which in
    consequence makes it do a few things better. Update qcom_smd-regulator's
    probe function to mimic what rpmh-regulator does to address a couple of
    issues:
    
    - Probe defer now works correctly, before it used to, well,
      kinda just die.. This fixes reliable probing on (at least) PM8994,
      because Linux apparently cannot deal with supply map dependencies yet..
    
    - Regulator data is now matched more sanely: regulator data is matched
      against each individual regulator node name and throwing an -EINVAL if
      data is missing, instead of just assuming everything is fine and
      iterating over all subsequent array members.
    
    - status = "disabled" will now work for disabling individual regulators in
      DT. Previously it didn't seem to do much if anything at all.
    
    Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
    Link: https://lore.kernel.org/r/20211230023442.1123424-1-konrad.dybcio@somainline.org
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 00ac838924f73b51e82994c7fc870f0a994e4d34
Author: Qinghua Jin <qhjin.dev@gmail.com>
Date:   Thu Jan 6 17:28:47 2022 +0800

    ASoC: topology: Fix typo
    
    change 'postion' to 'position'
    
    Signed-off-by: Qinghua Jin <qhjin.dev@gmail.com>
    Link: https://lore.kernel.org/r/20220106092847.357035-1-qhjin.dev@gmail.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 320386343451ab6a3577e0ee200dac56a6182944
Author: Shengjiu Wang <shengjiu.wang@nxp.com>
Date:   Wed Jan 5 19:08:03 2022 +0800

    ASoC: fsl_asrc: refine the check of available clock divider
    
    According to RM, the clock divider range is from 1 to 8, clock
    prescaling ratio may be any power of 2 from 1 to 128.
    So the supported divider is not all the value between
    1 and 1024, just limited value in that range.
    
    Create table for the supported divder and add function to
    check the clock divider is available by comparing with
    the table.
    
    Fixes: d0250cf4f2ab ("ASoC: fsl_asrc: Add an option to select internal ratio mode")
    Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
    Link: https://lore.kernel.org/r/1641380883-20709-1-git-send-email-shengjiu.wang@nxp.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 44125fd5315154c6b8326b5c27646af3b33ba25c
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:28 2022 +0100

    ASoC: Intel: bytcr_rt5640: Add support for external GPIO jack-detect
    
    Some boards have the codec IRQ hooked-up as normally, so the driver can
    still do things like headset vs headphones and button-press detection,
    but instead of using one of the JD pins of the codec, an external GPIO
    is used to report the jack-presence switch status of the jack.
    
    Add support for boards which have this setup and which specify which
    external GPIO to use in the special Android AMCR0F28 ACPI device.
    
    And add a quirk for the Asus TF103C tablet which uses this setup.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-7-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 45ed0166c39f878162872babc88830d91426beb5
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:27 2022 +0100

    ASoC: Intel: bytcr_rt5640: Support retrieving the codec IRQ from the AMCR0F28 ACPI dev
    
    Some X86 tablets, which ship with Android as factory installed OS,
    specify codec IRQs/GPIOS in a special Android AMCR0F28 ACPI device.
    
    Add support for retrieving the codec IRQ from this ACPI device instead
    of from the 10EC5640 device describing the codec itself and enable this
    on Asus MemoPad 7 ME176C tablets.
    
    This fixes jack-detect not working on these tablets.
    
    Cc: Stephan Gerhold <stephan@gerhold.net>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-6-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 701d636a224a77a4371f57ca2d4322ab0401a866
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:26 2022 +0100

    ASoC: rt5640: Add support for boards with an external jack-detect GPIO
    
    Some boards have the codec IRQ hooked-up as normally, so the driver can
    still do things like headset vs headphones and button-press detection,
    but instead of using one of the JD pins of the codec, an external GPIO
    is used to report the jack-presence switch status of the jack.
    
    Add support for this.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-5-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit b35a9ab4904973a68b4473c2985b8ac0b6d57089
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:25 2022 +0100

    ASoC: rt5640: Allow snd_soc_component_set_jack() to override the codec IRQ
    
    On some boards where the firmware/fwnode information is in essence
    read-only (x86 + ACPI boards) the i2c_client for the codec may contain
    the wrong IRQ or no IRQ at all.
    
    Since we only request the IRQ once snd_soc_component_set_jack() gets
    called, allow machine drivers to override the IRQ with the proper one
    through the data parameter to snd_soc_component_set_jack().
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-4-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit a3b1aaf7aef9fa945810de3fd7c15b2e93ecdbfd
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:24 2022 +0100

    ASoC: rt5640: Change jack_work to a delayed_work
    
    Change jack_work from a struct work_struct to a struct delayed_work, this
    is a preparation patch for adding support for boards where an external
    GPIO is used for jack-detect, rather then one of the JD pins of the codec.
    
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-3-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit a2d6d84db2e7bcc831aed90f33334c70a1b060a3
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Thu Jan 6 12:01:23 2022 +0100

    ASoC: rt5640: Fix possible NULL pointer deref on resume
    
    Commit 2b9c8d2b3c89 ("ASoC: rt5640: Add the HDA header support") adds
    re-queuing of the jack_work on resume when rt5640->jd_src != 0.
    
    But the jack_work will unconditionally deref rt5640->jack and that might
    be NULL. E.g. the sound/soc/intel/boards/bytcr_rt5640.c machine driver
    call snd_soc_component_set_jack(codec, NULL, NULL) from pre_suspend to
    disable the IRQ to avoid spurious wakeups, so when rt5640_resume()
    runs rt5640->jack will be NULL in this case.
    
    Make the queueing of the work conditional on rt5640->jack instead of
    on rt5640->jd_src to fix this.
    
    Fixes: 2b9c8d2b3c89 ("ASoC: rt5640: Add the HDA header support")
    Cc: Oder Chiou <oder_chiou@realtek.com>
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Link: https://lore.kernel.org/r/20220106110128.66049-2-hdegoede@redhat.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3969341813eb56d2dfc39bb64229359a6ae3c195
Author: Shengjiu Wang <shengjiu.wang@nxp.com>
Date:   Tue Jan 4 18:40:35 2022 +0800

    ASoC: imx-card: improve the sound quality for low rate
    
    According to RM, on auto mode:
    For codec AK4458 and AK4497, the lowest ratio of MLCK/FS is 256
    if sample rate is 8kHz-48kHz,
    For codec AK5558, the lowest ratio of MLCK/FS is 512 if sample
    rate is 8kHz-48kHz.
    
    With these setting the sound quality for 8kHz-48kHz can be improved.
    
    Fixes: aa736700f42f ("ASoC: imx-card: Add imx-card machine driver")
    Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
    Link: https://lore.kernel.org/r/1641292835-19085-4-git-send-email-shengjiu.wang@nxp.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit f331ae5fa59fbfb748317b290648fc3f1a50d932
Author: Shengjiu Wang <shengjiu.wang@nxp.com>
Date:   Tue Jan 4 18:40:34 2022 +0800

    ASoC: imx-card: Fix mclk calculation issue for akcodec
    
    Transfer the refined slots and slot_width to akcodec_get_mclk_rate()
    for mclk calculation, otherwise the mclk frequency does not match
    with the slots and slot_width for S16_LE format, because the default
    slot_width is 32.
    
    Fixes: aa736700f42f ("ASoC: imx-card: Add imx-card machine driver")
    Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
    Link: https://lore.kernel.org/r/1641292835-19085-3-git-send-email-shengjiu.wang@nxp.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3349b3d0c63b8b6fcca58156d72407f0b2e101ac
Author: Shengjiu Wang <shengjiu.wang@nxp.com>
Date:   Tue Jan 4 18:40:33 2022 +0800

    ASoC: imx-card: Need special setting for ak4497 on i.MX8MQ
    
    The SAI on i.MX8MQ don't support one2one ratio for mclk:bclk, so
    the mclk frequency exceeds the supported range of codec for
    the case that sample rate is larger than 705kHZ and format is
    S32_LE. Update the supported width for such case.
    
    Fixes: aa736700f42f ("ASoC: imx-card: Add imx-card machine driver")
    Signed-off-by: Shengjiu Wang <shengjiu.wang@nxp.com>
    Link: https://lore.kernel.org/r/1641292835-19085-2-git-send-email-shengjiu.wang@nxp.com
    Signed-off-by: Mark Brown <broonie@kernel.org>

commit 3318ae23bbcb14b7f68e9006756ba6d970955635
Author: Aditya Garg <gargaditya08@live.com>
Date:   Mon Jan 3 13:28:42 2022 +0000

    Bluetooth: btbcm: disable read tx power for MacBook Air 8,1 and 8,2
    
    The MacBook Air 8,1 and 8,2 also need querying of LE Tx power
    to be disabled for Bluetooth to work.
    
    Signed-off-by: Aditya Garg <gargaditya08@live.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    Cc: stable@vger.kernel.org

commit 36595d8ad46d9e4c41cc7c48c4405b7c3322deac
Author: Wen Gu <guwen@linux.alibaba.com>
Date:   Thu Jan 6 20:42:08 2022 +0800

    net/smc: Reset conn->lgr when link group registration fails
    
    SMC connections might fail to be registered in a link group due to
    unable to find a usable link during its creation. As a result,
    smc_conn_create() will return a failure and most resources related
    to the connection won't be applied or initialized, such as
    conn->abort_work or conn->lnk.
    
    If smc_conn_free() is invoked later, it will try to access the
    uninitialized resources related to the connection, thus causing
    a warning or crash.
    
    This patch tries to fix this by resetting conn->lgr to NULL if an
    abnormal exit occurs in smc_lgr_register_conn(), thus avoiding the
    access to uninitialized resources in smc_conn_free().
    
    Meanwhile, the new created link group should be terminated if smc
    connections can't be registered in it. So smc_lgr_cleanup_early() is
    modified to take care of link group only and invoked to terminate
    unusable link group by smc_conn_create(). The call to smc_conn_free()
    is moved out from smc_lgr_cleanup_early() to smc_conn_abort().
    
    Fixes: 56bc3b2094b4 ("net/smc: assign link to a new connection")
    Suggested-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
    Acked-by: Karsten Graul <kgraul@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 6845667146a28c09b5dfc401c1ad112374087944
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Dec 24 08:02:49 2021 +0000

    Bluetooth: hci_qca: Fix NULL vs IS_ERR_OR_NULL check in qca_serdev_probe
    
    The function devm_gpiod_get_index() return error pointers on error.
    Thus devm_gpiod_get_index_optional() could return NULL and error pointers.
    The same as devm_gpiod_get_optional() function. Using IS_ERR_OR_NULL()
    check to catch error pointers.
    
    Fixes: 77131dfe ("Bluetooth: hci_qca: Replace devm_gpiod_get() with devm_gpiod_get_optional()")
    Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit b38cd3b42fba66cc538edb9cf77e07881f43f8e2
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Fri Dec 24 10:53:18 2021 +0800

    Bluetooth: hci_bcm: Check for error irq
    
    For the possible failure of the platform_get_irq(), the returned irq
    could be error number and will finally cause the failure of the
    request_irq().
    Consider that platform_get_irq() can now in certain cases return
    -EPROBE_DEFER, and the consequences of letting request_irq() effectively
    convert that into -EINVAL, even at probe time rather than later on.
    So it might be better to check just now.
    
    Fixes: 0395ffc1ee05 ("Bluetooth: hci_bcm: Add PM for BCM devices")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

commit d5a73ec96cc57cf67e51b12820fc2354e7ca46f8
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Thu Jan 6 18:04:10 2022 +0800

    fsl/fman: Check for null pointer after calling devm_ioremap
    
    As the possible failure of the allocation, the devm_ioremap() may return
    NULL pointer.
    Take tgec_initialization() as an example.
    If allocation fails, the params->base_addr will be NULL pointer and will
    be assigned to tgec->regs in tgec_config().
    Then it will cause the dereference of NULL pointer in set_mac_address(),
    which is called by tgec_init().
    Therefore, it should be better to add the sanity check after the calling
    of the devm_ioremap().
    
    Fixes: 3933961682a3 ("fsl/fman: Add FMan MAC driver")
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 710ad98c363a66a0cd8526465426c5c5f8377ee0
Author: Daniel Borkmann <daniel@iogearbox.net>
Date:   Thu Jan 6 01:46:06 2022 +0100

    veth: Do not record rx queue hint in veth_xmit
    
    Laurent reported that they have seen a significant amount of TCP retransmissions
    at high throughput from applications residing in network namespaces talking to
    the outside world via veths. The drops were seen on the qdisc layer (fq_codel,
    as per systemd default) of the phys device such as ena or virtio_net due to all
    traffic hitting a _single_ TX queue _despite_ multi-queue device. (Note that the
    setup was _not_ using XDP on veths as the issue is generic.)
    
    More specifically, after edbea9220251 ("veth: Store queue_mapping independently
    of XDP prog presence") which made it all the way back to v4.19.184+,
    skb_record_rx_queue() would set skb->queue_mapping to 1 (given 1 RX and 1 TX
    queue by default for veths) instead of leaving at 0.
    
    This is eventually retained and callbacks like ena_select_queue() will also pick
    single queue via netdev_core_pick_tx()'s ndo_select_queue() once all the traffic
    is forwarded to that device via upper stack or other means. Similarly, for others
    not implementing ndo_select_queue() if XPS is disabled, netdev_pick_tx() might
    call into the skb_tx_hash() and check for prior skb_rx_queue_recorded() as well.
    
    In general, it is a _bad_ idea for virtual devices like veth to mess around with
    queue selection [by default]. Given dev->real_num_tx_queues is by default 1,
    the skb->queue_mapping was left untouched, and so prior to edbea9220251 the
    netdev_core_pick_tx() could do its job upon __dev_queue_xmit() on the phys device.
    
    Unbreak this and restore prior behavior by removing the skb_record_rx_queue()
    from veth_xmit() altogether.
    
    If the veth peer has an XDP program attached, then it would return the first RX
    queue index in xdp_md->rx_queue_index (unless configured in non-default manner).
    However, this is still better than breaking the generic case.
    
    Fixes: edbea9220251 ("veth: Store queue_mapping independently of XDP prog presence")
    Fixes: 638264dc9022 ("veth: Support per queue XDP ring")
    Reported-by: Laurent Bernaille <laurent.bernaille@datadoghq.com>
    Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
    Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
    Cc: Toshiaki Makita <toshiaki.makita1@gmail.com>
    Cc: Eric Dumazet <eric.dumazet@gmail.com>
    Cc: Paolo Abeni <pabeni@redhat.com>
    Cc: John Fastabend <john.fastabend@gmail.com>
    Cc: Willem de Bruijn <willemb@google.com>
    Acked-by: John Fastabend <john.fastabend@gmail.com>
    Reviewed-by: Eric Dumazet <edumazet@google.com>
    Acked-by: Toshiaki Makita <toshiaki.makita1@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b33721baccd5d4e6651cd8f619524a316ff22cd3
Author: Gaston Gonzalez <gascoar@gmail.com>
Date:   Wed Jan 5 17:35:48 2022 -0300

    staging: vc04_services: rename BM2835 to BCM2835 in headers comments
    
    In the kernel, when referring to the chip BCM2835, it is more suitable
    to use BCM2835 to BM2835. To avoid confusion, and to make things more
    consistent, rename the headers titles accordingly.
    
    Suggested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
    Link: https://lore.kernel.org/r/19acea9e9da0d3ebb1a7e6bce511a3c09e8c80c3.1641414449.git.gascoar@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 948d91b66b1f48e88774ba95cb392da0d4411b74
Author: Gaston Gonzalez <gascoar@gmail.com>
Date:   Wed Jan 5 17:35:46 2022 -0300

    staging: vc04_services: rename string literal containing bm2835_* to bcm2835*_
    
    In the kernel, all names related to the chip BCM2835 are always named
    bcm2835_*. To avoid confusion, and to make things more consistent,
    rename the string term bm2835_* to bcm2835_*.
    
    While at it, some realignments were made to improve readability.
    
    Suggested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
    Link: https://lore.kernel.org/r/91caae07fce0e4511f283388304e935526ba29ed.1641414449.git.gascoar@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit eccbcf75a75b6b0327ae7aa6d2cf96a3b99eda84
Author: Gaston Gonzalez <gascoar@gmail.com>
Date:   Wed Jan 5 17:35:45 2022 -0300

    staging: vc04_services: rename variables containing bm2835_* to bcm2835_*
    
    In the kernel, all names related to the chip BCM2835 are always named
    bcm2835_*. To avoid confusion, and to make things more consistent,
    rename all variables using bm2835_* to bcm2835_*.
    
    While at it, some realignments were made to improve readability.
    
    Suggested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
    Link: https://lore.kernel.org/r/a0af5deacebc2da9b21772c7677e1a9627edbed6.1641414449.git.gascoar@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit d6776424667cbbfe15d2482a220b620d3257a9bb
Author: Gaston Gonzalez <gascoar@gmail.com>
Date:   Wed Jan 5 17:35:44 2022 -0300

    staging: vc04_services: rename functions containing bm2835_* to bcm2835_*
    
    In the kernel, all names related to the chip BCM2835 are always named
    bcm2835_*. To avoid confusion, and to make things more consistent,
    rename functions using bm2835_* to bcm2835_*.
    
    While at it, some realignments were made to improve readability.
    
    Suggested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
    Link: https://lore.kernel.org/r/d3b6f67421c75829105f793cfb9ec1414b926bf6.1641414449.git.gascoar@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 710ec044517e0b9f34203d885a3d18e6dcbe1e66
Author: Gaston Gonzalez <gascoar@gmail.com>
Date:   Wed Jan 5 17:35:43 2022 -0300

    staging: vc04_services: rename structures bm2835_mmal_dev and bm2835_mmal_v4l2_ctrl
    
    In the kernel, all names related to the chip BCM2835 are always named
    bcm2835_*. To avoid confusion, and to make things more consistent,
    rename the structures bm2835_mmal_dev and bm2835_mmal_v4l2_ctrl
    accordingly.
    
    While at it, one realignment was made to improve readability.
    
    Suggested-by: Stefan Wahren <stefan.wahren@i2se.com>
    Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
    Link: https://lore.kernel.org/r/a893f24fc5ee6c276ea982f141b42ec0a00d7194.1641414449.git.gascoar@gmail.com
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit c288bc0db2d1938691ef283ce61ae6122e562bc3
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 5 19:41:01 2022 +0100

    ethernet: ibmveth: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the ibmveth sysfs code to use default_groups
    field which has been the preferred way since aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Cc: Michael Ellerman <mpe@ellerman.id.au>
    Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: Cristobal Forno <cforno12@linux.ibm.com>
    Cc: "David S. Miller" <davem@davemloft.net>
    Cc: Jakub Kicinski <kuba@kernel.org>
    Cc: linuxppc-dev@lists.ozlabs.org
    Cc: netdev@vger.kernel.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Reviewed-by: Tyrel Datwyler <tyreld@linux.ibm.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 2e81948177d769106754085c3e03534e6cc1f623
Author: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Date:   Tue Jan 4 23:06:28 2022 +0800

    staging: greybus: audio: Check null pointer
    
    As the possible alloc failure of devm_kcalloc(), it could return null
    pointer.
    Therefore, 'strings' should be checked and return NULL if alloc fails to
    prevent the dereference of the NULL pointer.
    Also, the caller should also deal with the return value of the
    gb_generate_enum_strings() and return -ENOMEM if returns NULL.
    Moreover, because the memory allocated with devm_kzalloc() will be
    freed automatically when the last reference to the device is dropped,
    the 'gbe' in gbaudio_tplg_create_enum_kctl() and
    gbaudio_tplg_create_enum_ctl() do not need to free manually.
    But the 'control' in gbaudio_tplg_create_widget() and
    gbaudio_tplg_process_kcontrols() has a specially error handle to
    cleanup.
    So it should be better to cleanup 'control' when fails.
    
    Fixes: e65579e335da ("greybus: audio: topology: Enable enumerated control support")
    Reviewed-by: Alex Elder <elder@linaro.org>
    Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
    Link: https://lore.kernel.org/r/20220104150628.1987906-1-jiasheng@iscas.ac.cn
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 43d012123122cc69feacab55b71369f386c19566
Author: Dan Carpenter <dan.carpenter@oracle.com>
Date:   Thu Jan 6 14:57:54 2022 +0300

    rocker: fix a sleeping in atomic bug
    
    This code is holding the &ofdpa->flow_tbl_lock spinlock so it is not
    allowed to sleep.  That means we have to pass the OFDPA_OP_FLAG_NOWAIT
    flag to ofdpa_flow_tbl_del().
    
    Fixes: 936bd486564a ("rocker: use FIB notifications instead of switchdev calls")
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 0746ae1be12177ebda0666eefa82583cbaeeefd6
Author: Pali Rohár <pali@kernel.org>
Date:   Fri Nov 26 15:43:07 2021 +0100

    PCI: mvebu: Add support for compiling driver as module
    
    Now when driver uses devm_pci_remap_iospace() function, it is possible
    implement ->remove() callback for unbinding device from driver.
    
    Implement mvebu_pcie_remove() callback with proper cleanup phase, drop
    driver's suppress_bind_attrs flag and switch type of CONFIG_PCI_MVEBU
    option from bool to tristate.
    
    This allows to compile pci-mvebu.c driver as loadable module pci-mvebu.ko
    with ability to unload it.
    
    Link: https://lore.kernel.org/r/20211126144307.7568-3-pali@kernel.org
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

commit 859186e238ffb7ca980dbb7af9abd799ceedbcb3
Author: Pali Rohár <pali@kernel.org>
Date:   Fri Nov 26 15:43:06 2021 +0100

    bus: mvebu-mbus: Export symbols for public API window functions
    
    This would allow to compile pci-mvebu.c driver as module.
    
    Link: https://lore.kernel.org/r/20211126144307.7568-2-pali@kernel.org
    Signed-off-by: Pali Rohár <pali@kernel.org>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>

commit 3407d826c18d9aed3c51545cc26ff9a2fda65463
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 5 19:26:34 2022 +0100

    firmware: edd: remove empty default_attrs array
    
    The default_attrs array of attributes for the edd sysfs entries is
    totally empty for some reason, and a list of attributes is added later
    after the object is created (which should be fixed up later as it's
    racy).  Because this pointer is never used, and is empty, and we are
    trying to remove all default_attrs usages, just delete it.
    
    Link: https://lore.kernel.org/r/20220105182634.2802684-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit ab6d0f57be58c075bd249a97c81c3557b5e3e7cf
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 5 19:17:19 2022 +0100

    firmware: dmi-sysfs: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the firmware dmi-sysfs sysfs code to use default_groups
    field which has been the preferred way since aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Link: https://lore.kernel.org/r/20220105181719.2737782-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit f68ae7823a9dc7737d0e4265cf65119a50c9ec69
Merge: 8ab1ff9b1ec81 d08aea21c89dc
Author: Wolfram Sang <wsa@kernel.org>
Date:   Thu Jan 6 14:26:39 2022 +0100

    Merge tag 'at24-updates-for-v5.17' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux into i2c/for-mergewindow
    
    at24 updates for v5.17
    
    - add support for a new model: Microchip 24c1025
    - reorganize the compatible definitions in the DT binding document
    - drop the at24_client structure by retrieving the struct device associated
      with the chip's regmap

commit ad8a5d1d2f577843dba14e4727c86e952ffbd5f1
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Wed Jan 5 19:31:33 2022 +0100

    qemu_fw_cfg: use default_groups in kobj_type
    
    There are currently 2 ways to create a set of sysfs files for a
    kobj_type, through the default_attrs field, and the default_groups
    field.  Move the firmware qemu_fw_cfg sysfs code to use default_groups
    field which has been the preferred way since aa30f47cf666 ("kobject: Add
    support for default attribute groups to kobj_type") so that we can soon
    get rid of the obsolete default_attrs field.
    
    Cc: Gabriel Somlo <somlo@cmu.edu>
    Cc: "Michael S. Tsirkin" <mst@redhat.com>
    Cc: qemu-devel@nongnu.org
    Acked-by: Michael S. Tsirkin <mst@redhat.com>
    Link: https://lore.kernel.org/r/20220105183133.2812848-1-gregkh@linuxfoundation.org
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

commit 33a5c2793451770cb6dcf0cc35c76cfd4b045513
Author: Hans de Goede <hdegoede@redhat.com>
Date:   Sun Dec 12 22:23:33 2021 +0100

    HID: Add new Letsketch tablet driver
    
    Add a new driver for the LetSketch / VSON WP9620N drawing tablet. This
    drawing tablet is also sold under other brand names such as Case U,
    presumably this driver will work for all of them. But it has only been
    tested with a LetSketch WP9620N model.
    
    These tablets also work without a special HID driver, but then only
    part of the active area works and both the pad and stylus buttons are
    hardwired to special key-combos. E.g. the 2 stylus buttons send right
    mouse clicks / resp. "e" key presses.
    
    BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2005575
    BugLink: https://github.com/DIGImend/digimend-kernel-drivers/issues/528
    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 7f84e2439ed2e2c7afdced9564dda1220e932704
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Jan 2 18:51:13 2022 +0100

    HID: apple: Add Magic Keyboard 2021 with fingerprint reader FN key mapping
    
    Use the function key table introduced for the Magic Keyboard 2021
    without fingerprint reader in the models with fingerprint reader and/or
    numpad.
    
    Tested with the ANSI variant of the keyboard with and without numpad.
    
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 531cb56972f2773c941499fcfb639cd5128dfb27
Author: Benjamin Berg <bberg@redhat.com>
Date:   Mon Nov 8 13:50:38 2021 +0100

    HID: apple: Add 2021 magic keyboard FN key mapping
    
    The new 2021 apple models have a different FN key assignment. Add a new
    translation table and use that for the 2021 magic keyboard.
    
    Signed-off-by: Benjamin Berg <bberg@redhat.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 5768701edcb7d7ff8abaa085996a5c1cb30d765e
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Dec 12 19:21:00 2021 +0100

    HID: magicmouse: set Magic Trackpad 2021 name
    
    The Apple Magic Trackpad 2021 (3rd generation) has the same product ID
    as the 2nd generation. However, when connected through Bluetooth, the
    version has changed from 0x107 to 0x110.
    
    The other meaningful change is that the name has dropped the generation
    number and now it is just "Apple Inc. Magic Trackpad", like the first
    generation model.
    
    Set the device name correctly to ensure the same driver settings are
    loaded, whether connected via Bluetooth or USB.
    
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 0aa45fcc42d82753a257abbc7138922d8250e06f
Author: José Expósito <jose.exposito89@gmail.com>
Date:   Sun Dec 12 19:20:59 2021 +0100

    HID: magicmouse: set device name when it has been personalized
    
    If the Apple Magic Trackpad 2 has been connected to a Mac, the name
    is automatically personalized showing its owner name. For example:
    "José Expósito's Trackpad".
    
    When connected through Bluetooth, the personalized name is reported,
    however, when connected through USB the generic name is reported.
    
    Set the device name correctly to ensure the same driver settings are
    loaded, whether connected via Bluetooth or USB.
    
    Signed-off-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit b2dcadef207719a9b3520cb9f1c9237c320d3ccd
Author: Alex Henrie <alexhenrie24@gmail.com>
Date:   Wed Dec 1 23:16:51 2021 -0700

    HID: apple: Add 2021 Magic Keyboard with number pad
    
    Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 9f92d61f01dd31305e53d3d6c036e93269070167
Author: Alex Henrie <alexhenrie24@gmail.com>
Date:   Wed Dec 1 23:16:50 2021 -0700

    HID: apple: Add 2021 Magic Keyboard with fingerprint reader
    
    Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
    Tested-by: José Expósito <jose.exposito89@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>

commit 0cf765fb00ce083c017f2571ac449cf7912cdb06
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date:   Wed Jan 5 23:22:37 2022 +0800

    sfc: Use swap() instead of open coding it
    
    Clean the following coccicheck warning:
    
    ./drivers/net/ethernet/sfc/efx_channels.c:870:36-37: WARNING opportunity
    for swap().
    
    ./drivers/net/ethernet/sfc/efx_channels.c:824:36-37: WARNING opportunity
    for swap().
    
    Reported-by: Abaci Robot <abaci@linux.alibaba.com>
    Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
    Acked-by: Martin Habets <habetsm.xilinx@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit ccd21ec5b8dd9b8a528a70315cee95fc1dd79d20
Author: Tom Rix <trix@redhat.com>
Date:   Wed Jan 5 06:10:20 2022 -0800

    ethtool: use phydev variable
    
    In ethtool_get_phy_stats(), the phydev varaible is set to
    dev->phydev but dev->phydev is still used.  Replace
    dev->phydev uses with phydev.
    
    Signed-off-by: Tom Rix <trix@redhat.com>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 8876769bf93687d8b17d8143d39ca7a1aaeaecc6
Author: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Date:   Wed Jan 5 13:15:15 2022 +0000

    net: macb: use .mac_select_pcs() interface
    
    Convert the PCS selection to use mac_select_pcs, which allows the PCS
    to perform any validation it needs.
    
    We must use separate phylink_pcs instances for the USX and SGMII PCS,
    rather than just changing the "ops" pointer before re-setting it to
    phylink as this interface queries the PCS, rather than requesting it
    to be changed.
    
    Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
    Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 44073187990d5629804ce0627525f6ea5cfef171
Author: Eric Dumazet <edumazet@google.com>
Date:   Wed Jan 5 03:48:42 2022 -0800

    ppp: ensure minimum packet size in ppp_write()
    
    It seems pretty clear ppp layer assumed user space
    would always be kind to provide enough data
    in their write() to a ppp device.
    
    This patch makes sure user provides at least
    2 bytes.
    
    It adds PPP_PROTO_LEN macro that could replace
    in net-next many occurrences of hard-coded 2 value.
    
    I replaced only one occurrence to ease backports
    to stable kernels.
    
    The bug manifests in the following report:
    
    BUG: KMSAN: uninit-value in ppp_send_frame+0x28d/0x27c0 drivers/net/ppp/ppp_generic.c:1740
     ppp_send_frame+0x28d/0x27c0 drivers/net/ppp/ppp_generic.c:1740
     __ppp_xmit_process+0x23e/0x4b0 drivers/net/ppp/ppp_generic.c:1640
     ppp_xmit_process+0x1fe/0x480 drivers/net/ppp/ppp_generic.c:1661
     ppp_write+0x5cb/0x5e0 drivers/net/ppp/ppp_generic.c:513
     do_iter_write+0xb0c/0x1500 fs/read_write.c:853
     vfs_writev fs/read_write.c:924 [inline]
     do_writev+0x645/0xe00 fs/read_write.c:967
     __do_sys_writev fs/read_write.c:1040 [inline]
     __se_sys_writev fs/read_write.c:1037 [inline]
     __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037
     do_syscall_x64 arch/x86/entry/common.c:51 [inline]
     do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Uninit was created at:
     slab_post_alloc_hook mm/slab.h:524 [inline]
     slab_alloc_node mm/slub.c:3251 [inline]
     __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974
     kmalloc_reserve net/core/skbuff.c:354 [inline]
     __alloc_skb+0x545/0xf90 net/core/skbuff.c:426
     alloc_skb include/linux/skbuff.h:1126 [inline]
     ppp_write+0x11d/0x5e0 drivers/net/ppp/ppp_generic.c:501
     do_iter_write+0xb0c/0x1500 fs/read_write.c:853
     vfs_writev fs/read_write.c:924 [inline]
     do_writev+0x645/0xe00 fs/read_write.c:967
     __do_sys_writev fs/read_write.c:1040 [inline]
     __se_sys_writev fs/read_write.c:1037 [inline]
     __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037
     do_syscall_x64 arch/x86/entry/common.c:51 [inline]
     do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82
     entry_SYSCALL_64_after_hwframe+0x44/0xae
    
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Cc: Paul Mackerras <paulus@samba.org>
    Cc: linux-ppp@vger.kernel.org
    Reported-by: syzbot <syzkaller@googlegroups.com>
    Acked-by: Guillaume Nault <gnault@redhat.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit eac1b93c14d645ef147b049ace0d5230df755548
Author: Coco Li <lixiaoyan@google.com>
Date:   Wed Jan 5 02:48:38 2022 -0800

    gro: add ability to control gro max packet size
    
    Eric Dumazet suggested to allow users to modify max GRO packet size.
    
    We have seen GRO being disabled by users of appliances (such as
    wifi access points) because of claimed bufferbloat issues,
    or some work arounds in sch_cake, to split GRO/GSO packets.
    
    Instead of disabling GRO completely, one can chose to limit
    the maximum packet size of GRO packets, depending on their
    latency constraints.
    
    This patch adds a per device gro_max_size attribute
    that can be changed with ip link command.
    
    ip link set dev eth0 gro_max_size 16000
    
    Suggested-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: Coco Li <lixiaoyan@google.com>
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 007747a984ea5e895b7d8b056b24ebf431e1e71d
Author: Miroslav Lichvar <mlichvar@redhat.com>
Date:   Wed Jan 5 11:33:26 2022 +0100

    net: fix SOF_TIMESTAMPING_BIND_PHC to work with multiple sockets
    
    When multiple sockets using the SOF_TIMESTAMPING_BIND_PHC flag received
    a packet with a hardware timestamp (e.g. multiple PTP instances in
    different PTP domains using the UDPv4/v6 multicast or L2 transport),
    the timestamps received on some sockets were corrupted due to repeated
    conversion of the same timestamp (by the same or different vclocks).
    
    Fix ptp_convert_timestamp() to not modify the shared skb timestamp
    and return the converted timestamp as a ktime_t instead. If the
    conversion fails, return 0 to not confuse the application with
    timestamps corresponding to an unexpected PHC.
    
    Fixes: d7c088265588 ("net: socket: support hardware timestamp conversion to PHC bound")
    Signed-off-by: Miroslav Lichvar <mlichvar@redhat.com>
    Cc: Yangbo Lu <yangbo.lu@nxp.com>
    Cc: Richard Cochran <richardcochran@gmail.com>
    Acked-by: Richard Cochran <richardcochran@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1b26d364e4e9bd6540a8e7bcaf50e7f35041feb5
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 00:11:50 2022 +0200

    net: dsa: warn about dsa_port and dsa_switch bit fields being non atomic
    
    As discussed during review here:
    https://patchwork.kernel.org/project/netdevbpf/patch/20220105132141.2648876-3-vladimir.oltean@nxp.com/
    
    we should inform developers about pitfalls of concurrent access to the
    boolean properties of dsa_switch and dsa_port, now that they've been
    converted to bit fields. No other measure than a comment needs to be
    taken, since the code paths that update these bit fields are not
    concurrent with each other.
    
    Suggested-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 63cfc65753d604edc6cfe07e6fba2bf8ececb293
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 00:11:49 2022 +0200

    net: dsa: don't enumerate dsa_switch and dsa_port bit fields using commas
    
    This is a cosmetic incremental fixup to commits
    7787ff776398 ("net: dsa: merge all bools of struct dsa_switch into a single u32")
    bde82f389af1 ("net: dsa: merge all bools of struct dsa_port into a single u8")
    
    The desire to make this change was enunciated after posting these
    patches here:
    https://patchwork.kernel.org/project/netdevbpf/cover/20220105132141.2648876-1-vladimir.oltean@nxp.com/
    
    but due to a slight timing overlap (message posted at 2:28 p.m. UTC,
    merge commit is at 2:46 p.m. UTC), that comment was missed and the
    changes were applied as-is.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit af8c6db1975160753995932f43e1cd40d508aa6d
Merge: d093d17c9554b 11fd667dac315
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 6 11:59:10 2022 +0000

    Merge branch 'dsa-init-cleanups'
    
    Vladimir Oltean says:
    
    ====================
    DSA initialization cleanups
    
    These patches contain miscellaneous work that makes the DSA init code
    path symmetric with the teardown path, and some additional patches
    carried by Ansuel Smith for his register access over Ethernet work, but
    those patches can be applied as-is too.
    https://patchwork.kernel.org/project/netdevbpf/patch/20211214224409.5770-3-ansuelsmth@gmail.com/
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 11fd667dac315ea3f2469961f6d2869271a46cae
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:17 2022 +0200

    net: dsa: setup master before ports
    
    It is said that as soon as a network interface is registered, all its
    resources should have already been prepared, so that it is available for
    sending and receiving traffic. One of the resources needed by a DSA
    slave interface is the master.
    
    dsa_tree_setup
    -> dsa_tree_setup_ports
       -> dsa_port_setup
          -> dsa_slave_create
             -> register_netdevice
    -> dsa_tree_setup_master
       -> dsa_master_setup
          -> sets up master->dsa_ptr, which enables reception
    
    Therefore, there is a short period of time after register_netdevice()
    during which the master isn't prepared to pass traffic to the DSA layer
    (master->dsa_ptr is checked by eth_type_trans). Same thing during
    unregistration, there is a time frame in which packets might be missed.
    
    Note that this change opens us to another race: dsa_master_find_slave()
    will get invoked potentially earlier than the slave creation, and later
    than the slave deletion. Since dp->slave starts off as a NULL pointer,
    the earlier calls aren't a problem, but the later calls are. To avoid
    use-after-free, we should zeroize dp->slave before calling
    dsa_slave_destroy().
    
    In practice I cannot really test real life improvements brought by this
    change, since in my systems, netdevice creation races with PHY autoneg
    which takes a few seconds to complete, and that masks quite a few races.
    Effects might be noticeable in a setup with fixed links all the way to
    an external system.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 1e3f407f3cacc5dcfe27166c412ed9bc263d82bf
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:16 2022 +0200

    net: dsa: first set up shared ports, then non-shared ports
    
    After commit a57d8c217aad ("net: dsa: flush switchdev workqueue before
    tearing down CPU/DSA ports"), the port setup and teardown procedure
    became asymmetric.
    
    The fact of the matter is that user ports need the shared ports to be up
    before they can be used for CPU-initiated termination. And since we
    register net devices for the user ports, those won't be functional until
    we also call the setup for the shared (CPU, DSA) ports. But we may do
    that later, depending on the port numbering scheme of the hardware we
    are dealing with.
    
    It just makes sense that all shared ports are brought up before any user
    port is. I can't pinpoint any issue due to the current behavior, but
    let's change it nonetheless, for consistency's sake.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c146f9bc195a9dc3ad7fd000a14540e7c9df952d
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:15 2022 +0200

    net: dsa: hold rtnl_mutex when calling dsa_master_{setup,teardown}
    
    DSA needs to simulate master tracking events when a binding is first
    with a DSA master established and torn down, in order to give drivers
    the simplifying guarantee that ->master_state_change calls are made
    only when the master's readiness state to pass traffic changes.
    master_state_change() provide a operational bool that DSA driver can use
    to understand if DSA master is operational or not.
    To avoid races, we need to block the reception of
    NETDEV_UP/NETDEV_CHANGE/NETDEV_GOING_DOWN events in the netdev notifier
    chain while we are changing the master's dev->dsa_ptr (this changes what
    netdev_uses_dsa(dev) reports).
    
    The dsa_master_setup() and dsa_master_teardown() functions optionally
    require the rtnl_mutex to be held, if the tagger needs the master to be
    promiscuous, these functions call dev_set_promiscuity(). Move the
    rtnl_lock() from that function and make it top-level.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit a1ff94c2973c43bc1e2677ac63ebb15b1d1ff846
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:14 2022 +0200

    net: dsa: stop updating master MTU from master.c
    
    At present there are two paths for changing the MTU of the DSA master.
    
    The first is:
    
    dsa_tree_setup
    -> dsa_tree_setup_ports
       -> dsa_port_setup
          -> dsa_slave_create
             -> dsa_slave_change_mtu
                -> dev_set_mtu(master)
    
    The second is:
    
    dsa_tree_setup
    -> dsa_tree_setup_master
       -> dsa_master_setup
          -> dev_set_mtu(dev)
    
    So the dev_set_mtu() call from dsa_master_setup() has been effectively
    superseded by the dsa_slave_change_mtu(slave_dev, ETH_DATA_LEN) that is
    done from dsa_slave_create() for each user port. The later function also
    updates the master MTU according to the largest user port MTU from the
    tree. Therefore, updating the master MTU through a separate code path
    isn't needed.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit e31dbd3b6aba585231cd84a87adeb22e7c6a8c19
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:13 2022 +0200

    net: dsa: merge rtnl_lock sections in dsa_slave_create
    
    Currently dsa_slave_create() has two sequences of rtnl_lock/rtnl_unlock
    in a row. Remove the rtnl_unlock() and rtnl_lock() in between, such that
    the operation can execute slighly faster.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit 904e112ad431492b34f235f59738e8312802bbf9
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date:   Thu Jan 6 01:11:12 2022 +0200

    net: dsa: reorder PHY initialization with MTU setup in slave.c
    
    In dsa_slave_create() there are 2 sections that take rtnl_lock():
    MTU change and netdev registration. They are separated by PHY
    initialization.
    
    There isn't any strict ordering requirement except for the fact that
    netdev registration should be last. Therefore, we can perform the MTU
    change a bit later, after the PHY setup. A future change will then be
    able to merge the two rtnl_lock sections into one.
    
    Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
    Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit c4251db3b9d2ad4411f95e65ca00ea0f6800319b
Merge: 502a2ce9cdf42 45a98ef4922de
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 6 11:55:45 2022 +0000

    Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec
    
    Steffen Klassert says:
    
    ====================
    pull request (net): ipsec 2022-01-06
    
    1) Fix xfrm policy lookups for ipv6 gre packets by initializing
       fl6_gre_key properly. From Ghalem Boudour.
    
    2) Fix the dflt policy check on forwarding when there is no
       policy configured. The check was done for the wrong direction.
       From Nicolas Dichtel.
    
    3) Use the correct 'struct xfrm_user_offload' when calculating
       netlink message lenghts in xfrm_sa_len(). From Eric Dumazet.
    
    4) Tread inserting xfrm interface id 0 as an error.
       From Antony Antony.
    
    5) Fail if xfrm state or policy is inserted with XFRMA_IF_ID 0,
       xfrm interfaces with id 0 are not allowed.
       From Antony Antony.
    
    6) Fix inner_ipproto setting in the sec_path for tunnel mode.
       From  Raed Salem.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit d093d17c9554be794b1bd83971fb6d0ae3ea77b1
Merge: 4e023b44d5cec 4e484b3e969b5
Author: David S. Miller <davem@davemloft.net>
Date:   Thu Jan 6 11:54:20 2022 +0000

    Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next
    
    Steffen Klassert says:
    
    ====================
    pull request (net-next): ipsec-next 2022-01-06
    
    1) Fix some clang_analyzer warnings about never read variables.
       From luo penghao.
    
    2) Check for pols[0] only once in xfrm_expand_policies().
       From Jean Sacren.
    
    3) The SA curlft.use_time was updated only on SA cration time.
       Update whenever the SA is used. From Antony Antony
    
    4) Add support for SM3 secure hash.
       From Xu Jia.
    
    5) Add support for SM4 symmetric cipher algorithm.
       From Xu Jia.
    
    6) Add a rate limit for SA mapping change messages.
       From Antony Antony.
    ====================
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

commit b01af5c0b0414f96e6c3891e704d1c40faa18813
Author: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Date:   Sun Dec 12 06:52:41 2021 +0000

    mm/slob: Remove unnecessary page_mapcount_reset() function call
    
    After commit 401fb12c68c2 ("mm/sl*b: Differentiate struct slab fields by
    sl*b implementations"), we can reorder fields of struct slab depending
    on slab allocator.
    
    For now, page_mapcount_reset() is called because page->_mapcount and
    slab->units have same offset. But this is not necessary for struct slab.
    Use unused field for units instead.
    
    Signed-off-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Link: https://lore.kernel.org/r/20211212065241.GA886691@odroid

commit c5e97ed154589524a1df4ae2be55c4cfdb0d0573
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Mon Oct 4 14:46:48 2021 +0100

    bootmem: Use page->index instead of page->freelist
    
    page->freelist is for the use of slab.  Using page->index is the same
    set of bits as page->freelist, and by using an integer instead of a
    pointer, we can avoid casts.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Dave Hansen <dave.hansen@linux.intel.com>
    Cc: Andy Lutomirski <luto@kernel.org>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Borislav Petkov <bp@alien8.de>
    Cc: <x86@kernel.org>
    Cc: "H. Peter Anvin" <hpa@zytor.com>

commit ffedd09fa9b06d0d79e123bbf4ec81125456d982
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date:   Mon Oct 4 14:46:47 2021 +0100

    zsmalloc: Stop using slab fields in struct page
    
    The ->freelist and ->units members of struct page are for the use of
    slab only.  I'm not particularly familiar with zsmalloc, so generate the
    same code by using page->index to store 'page' (page->index and
    page->freelist are at the same offset in struct page).  This should be
    cleaned up properly at some point by somebody who is familiar with
    zsmalloc.
    
    Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: Minchan Kim <minchan@kernel.org>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: Nitin Gupta <ngupta@vflare.org>
    Cc: Sergey Senozhatsky <senozhatsky@chromium.org>

commit 9c01e9af171f13cf6573f404ecaf96dfa48233ab
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Wed Nov 10 14:12:45 2021 +0100

    mm/slub: Define struct slab fields for CONFIG_SLUB_CPU_PARTIAL only when enabled
    
    The fields 'next' and 'slabs' are only used when CONFIG_SLUB_CPU_PARTIAL
    is enabled. We can put their definition to #ifdef to prevent accidental
    use when disabled.
    
    Currenlty show_slab_objects() and slabs_cpu_partial_show() contain code
    accessing the slabs field that's effectively dead with
    CONFIG_SLUB_CPU_PARTIAL=n through the wrappers slub_percpu_partial() and
    slub_percpu_partial_read_once(), but to prevent a compile error, we need
    to hide all this code behind #ifdef.
    
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Reviewed-by: Roman Gushchin <guro@fb.com>
    Tested-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>

commit 662188c3a20eba75babc5a910a5f1b4278069f85
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Wed Nov 10 12:57:43 2021 +0100

    mm/slub: Simplify struct slab slabs field definition
    
    Before commit b47291ef02b0 ("mm, slub: change percpu partial accounting
    from objects to pages") we had to fit two integer fields into a native
    word size, so we used short int on 32-bit and int on 64-bit via #ifdef.
    After that commit there is only one integer field, so we can simply
    define it as int everywhere.
    
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Reviewed-by: Roman Gushchin <guro@fb.com>

commit 401fb12c68c257b9c9116b1475c0ac26b646fcc0
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Thu Nov 4 11:30:58 2021 +0100

    mm/sl*b: Differentiate struct slab fields by sl*b implementations
    
    With a struct slab definition separate from struct page, we can go
    further and define only fields that the chosen sl*b implementation uses.
    This means everything between __page_flags and __page_refcount
    placeholders now depends on the chosen CONFIG_SL*B. Some fields exist in
    all implementations (slab_list) but can be part of a union in some, so
    it's simpler to repeat them than complicate the definition with ifdefs
    even more.
    
    The patch doesn't change physical offsets of the fields, although it
    could be done later - for example it's now clear that tighter packing in
    SLOB could be possible.
    
    This should also prevent accidental use of fields that don't exist in
    given implementation. Before this patch virt_to_cache() and
    cache_from_obj() were visible for SLOB (albeit not used), although they
    rely on the slab_cache field that isn't set by SLOB. With this patch
    it's now a compile error, so these functions are now hidden behind
    an #ifndef CONFIG_SLOB.
    
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Reviewed-by: Roman Gushchin <guro@fb.com>
    Tested-by: Marco Elver <elver@google.com> # kfence
    Reviewed-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Tested-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Marco Elver <elver@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: <kasan-dev@googlegroups.com>

commit 8dae0cfed57357c0a627f377386ade1591f4d9ea
Author: Vlastimil Babka <vbabka@suse.cz>
Date:   Wed Nov 3 18:19:48 2021 +0100

    mm/kfence: Convert kfence_guarded_alloc() to struct slab
    
    The function sets some fields that are being moved from struct page to
    struct slab so it needs to be converted.
    
    Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
    Tested-by: Marco Elver <elver@google.com>
    Cc: Alexander Potapenko <glider@google.com>
    Cc: Marco Elver <elver@google.com>
    Cc: Dmitry Vyukov <dvyukov@google.com>
    Cc: <kasan-dev@googlegroups.com>

commit 6e48a966dfd18987fec9385566a67d36e2b5fc11
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
D