[PATCH 5.10 00/95] 5.10.200-rc1 review

[PATCH 5.10 00/95] 5.10.200-rc1 review

[Greg Kroah-Hartman]

This is the start of the stable review cycle for the 5.10.200 release.
There are 95 patches in this series, all will be posted as a response
to this one.  If anyone has any issues with these being applied, please
let me know.

Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
or in the git tree and branch at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Linux 5.10.200-rc1

Mark Hasemeyer <markhas@chromium.org>
    ALSA: hda: intel-dsp-config: Fix JSL Chromebook quirk detection

Cameron Williams <cang1@live.co.uk>
    tty: 8250: Add support for Intashield IS-100

Cameron Williams <cang1@live.co.uk>
    tty: 8250: Add support for Brainboxes UP cards

Cameron Williams <cang1@live.co.uk>
    tty: 8250: Add support for additional Brainboxes UC cards

Cameron Williams <cang1@live.co.uk>
    tty: 8250: Remove UC-257 and UC-431

Andrey Konovalov <andreyknvl@gmail.com>
    usb: raw-gadget: properly handle interrupted requests

LihaSika <lihasika@gmail.com>
    usb: storage: set 1.50 as the lower bcdDevice for older "Super Top" compatibility

Vicki Pfau <vi@endrift.com>
    PCI: Prevent xHCI driver from claiming AMD VanGogh USB3 DRD device

Lukas Magel <lukas.magel@posteo.net>
    can: isotp: isotp_sendmsg(): fix TX state detection and wait behavior

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: isotp_bind(): do not validate unused address information

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: add local echo tx processing and tx without FC

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: handle wait_event_interruptible() return values

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: check CAN address family in isotp_bind()

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: isotp_bind(): return -EINVAL on incorrect CAN ID formatting

Oliver Hartkopp <socketcan@hartkopp.net>
    can: isotp: set max PDU size to 64 kByte

Patrick Menschel <menschel.p@posteo.de>
    can: isotp: Add error message if txqueuelen is too small

Patrick Menschel <menschel.p@posteo.de>
    can: isotp: add symbolic error message to isotp_module_init()

Patrick Menschel <menschel.p@posteo.de>
    can: isotp: change error format from decimal to symbolic error names

Ian Rogers <irogers@google.com>
    perf evlist: Avoid frequency mode for the dummy event

Namhyung Kim <namhyung@kernel.org>
    perf tools: Get rid of evlist__add_on_all_cpus()

Adrian Hunter <adrian.hunter@intel.com>
    perf evlist: Add evlist__add_dummy_on_all_cpus()

Michael Ellerman <mpe@ellerman.id.au>
    powerpc/mm: Fix boot crash with FLATMEM

Su Hui <suhui@nfschina.com>
    net: chelsio: cxgb4: add an error code check in t4_load_phy_fw

Liming Sun <limings@nvidia.com>
    platform/mellanox: mlxbf-tmfifo: Fix a warning message

Tomas Henzl <thenzl@redhat.com>
    scsi: mpt3sas: Fix in error path

Jorge Maidana <jorgem.linux@gmail.com>
    fbdev: uvesafb: Call cn_del_callback() at the end of uvesafb_exit()

Shuming Fan <shumingf@realtek.com>
    ASoC: rt5650: fix the wrong result of key button

Florian Westphal <fw@strlen.de>
    netfilter: nfnetlink_log: silence bogus compiler warning

William A. Kennington III <william@wkennington.com>
    spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0

Arnd Bergmann <arnd@arndb.de>
    fbdev: atyfb: only use ioremap_uc() on i386 and ia64

Dmitry Torokhov <dmitry.torokhov@gmail.com>
    Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport

Zhang Shurong <zhang_shurong@foxmail.com>
    dmaengine: ste_dma40: Fix PM disable depth imbalance in d40_probe

Ben Wolsieffer <ben.wolsieffer@hefring.com>
    irqchip/stm32-exti: add missing DT IRQ flag translation

Anup Patel <apatel@ventanamicro.com>
    irqchip/riscv-intc: Mark all INTC nodes as initialized

Gustavo A. R. Silva <gustavoars@kernel.org>
    net: sched: cls_u32: Fix allocation size in u32_init()

Juergen Gross <jgross@suse.com>
    x86: Fix .brk attribute in linker script

Hangyu Hua <hbh25y@gmail.com>
    rpmsg: Fix possible refcount leak in rpmsg_register_device_override()

Bjorn Andersson <quic_bjorande@quicinc.com>
    rpmsg: glink: Release driver_override

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    rpmsg: Fix calling device_lock() on non-initialized device

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    rpmsg: Fix kfree() of static memory on setting driver_override

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    rpmsg: Constify local variable in field store macro

Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
    driver: platform: Add helper for safer setting of driver_override

John Sperbeck <jsperbeck@google.com>
    objtool/x86: add missing embedded_insn check

Baokun Li <libaokun1@huawei.com>
    ext4: avoid overlapping preallocations due to overflow

Baokun Li <libaokun1@huawei.com>
    ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow

Baokun Li <libaokun1@huawei.com>
    ext4: add two helper functions extent_logical_end() and pa_logical_end()

Josh Poimboeuf <jpoimboe@kernel.org>
    x86/mm: Fix RESERVE_BRK() for older binutils

Josh Poimboeuf <jpoimboe@redhat.com>
    x86/mm: Simplify RESERVE_BRK()

Chao Yu <chao@kernel.org>
    f2fs: fix to do sanity check on inode type during garbage collection

Steve French <stfrench@microsoft.com>
    smbdirect: missing rc checks while waiting for rdma events

Wang Hai <wanghai38@huawei.com>
    kobject: Fix slab-out-of-bounds in fill_kobj_path()

Thomas Gleixner <tglx@linutronix.de>
    x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility

Robert Hancock <robert.hancock@calian.com>
    iio: adc: xilinx-xadc: Don't clobber preset voltage/temperature thresholds

Bartosz Golaszewski <bgolaszewski@baylibre.com>
    iio: adc: xilinx: use more devres helpers and remove remove()

Bartosz Golaszewski <bgolaszewski@baylibre.com>
    iio: adc: xilinx: use devm_krealloc() instead of kfree() + kcalloc()

Bartosz Golaszewski <bgolaszewski@baylibre.com>
    iio: adc: xilinx: use helper variable for &pdev->dev

Alessandro Carminati <alessandro.carminati@gmail.com>
    clk: Sanitize possible_parent_show to Handle Return Value of of_clk_get_parent_name

Al Viro <viro@zeniv.linux.org.uk>
    sparc32: fix a braino in fault handling in csum_and_copy_..._user()

Peter Zijlstra <peterz@infradead.org>
    perf/core: Fix potential NULL deref

Peng Fan <peng.fan@nxp.com>
    nvmem: imx: correct nregs for i.MX6UL

Peng Fan <peng.fan@nxp.com>
    nvmem: imx: correct nregs for i.MX6SLL

Peng Fan <peng.fan@nxp.com>
    nvmem: imx: correct nregs for i.MX6ULL

Ekansh Gupta <quic_ekangupt@quicinc.com>
    misc: fastrpc: Clean buffers on remote invocation failures

Yujie Liu <yujie.liu@intel.com>
    tracing/kprobes: Fix the description of variable length arguments

Jian Zhang <zhangjian.3032@bytedance.com>
    i2c: aspeed: Fix i2c bus hang in slave read

Alain Volmat <alain.volmat@foss.st.com>
    i2c: stm32f7: Fix PEC handling in case of SMBUS transfers

Herve Codina <herve.codina@bootlin.com>
    i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node()

Herve Codina <herve.codina@bootlin.com>
    i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node()

Herve Codina <herve.codina@bootlin.com>
    i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node()

Marek Szyprowski <m.szyprowski@samsung.com>
    iio: exynos-adc: request second interupt only when touchscreen mode is used

Haibo Li <haibo.li@mediatek.com>
    kasan: print the original fault addr when access invalid shadow

Ivan Vecera <ivecera@redhat.com>
    i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR

Pablo Neira Ayuso <pablo@netfilter.org>
    gtp: fix fragmentation needed check with gso

Pablo Neira Ayuso <pablo@netfilter.org>
    gtp: uapi: fix GTPA_MAX

Fred Chen <fred.chenchen03@gmail.com>
    tcp: fix wrong RTO timeout when received SACK reneging

Douglas Anderson <dianders@chromium.org>
    r8152: Release firmware if we have an error in probe

Douglas Anderson <dianders@chromium.org>
    r8152: Cancel hw_phy_work if we have an error in probe

Douglas Anderson <dianders@chromium.org>
    r8152: Run the unload routine if we have errors during probe

Douglas Anderson <dianders@chromium.org>
    r8152: Increase USB control msg timeout to 5000ms as per spec

Shigeru Yoshida <syoshida@redhat.com>
    net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg

Christophe JAILLET <christophe.jaillet@wanadoo.fr>
    net: ieee802154: adf7242: Fix some potential buffer overflow in adf7242_stats_show()

Sasha Neftin <sasha.neftin@intel.com>
    igc: Fix ambiguity in the ethtool advertising

Eric Dumazet <edumazet@google.com>
    neighbour: fix various data-races

Mateusz Palczewski <mateusz.palczewski@intel.com>
    igb: Fix potential memory leak in igb_add_ethtool_nfc_entry

Kunwu Chan <chentao@kylinos.cn>
    treewide: Spelling fix in comment

Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
    r8169: fix the KCSAN reported data race in rtl_rx while reading desc->opts1

Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
    r8169: fix the KCSAN reported data-race in rtl_tx while reading TxDescArray[entry].opts1

Lukasz Majczak <lma@semihalf.com>
    drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper()

Wolfram Sang <wsa+renesas@sang-engineering.com>
    mmc: renesas_sdhi: use custom mask for TMIO_MASK_ALL

Kemeng Shi <shikemeng@huaweicloud.com>
    mm/page_alloc: correct start page when guard page debug is enabled

Maximilian Heyne <mheyne@amazon.de>
    virtio-mmio: fix memory leak of vm_dev

Gavin Shan <gshan@redhat.com>
    virtio_balloon: Fix endless deflation and inflation on arm64

Rodríguez Barbarin, José Javier <JoseJavier.Rodriguez@duagon.com>
    mcb-lpc: Reallocate memory region to avoid memory overlapping

Rodríguez Barbarin, José Javier <JoseJavier.Rodriguez@duagon.com>
    mcb: Return actual parsed size when reading chameleon table

Francis Laniel <flaniel@linux.microsoft.com>
    selftests/ftrace: Add new test case which checks non unique symbol


-------------

Diffstat:

 Makefile                                           |   4 +-
 arch/powerpc/kernel/setup-common.c                 |   2 +
 arch/powerpc/mm/mem.c                              |   1 -
 arch/sparc/lib/checksum_32.S                       |   2 +-
 arch/x86/include/asm/i8259.h                       |   2 +
 arch/x86/include/asm/setup.h                       |  46 +--
 arch/x86/kernel/acpi/boot.c                        |   3 +
 arch/x86/kernel/i8259.c                            |  38 +-
 arch/x86/kernel/setup.c                            |   5 -
 arch/x86/kernel/vmlinux.lds.S                      |   2 +-
 drivers/base/driver.c                              |  69 ++++
 drivers/base/platform.c                            |  28 +-
 drivers/clk/clk.c                                  |  21 +-
 drivers/dma/ste_dma40.c                            |   1 +
 drivers/gpu/drm/drm_dp_mst_topology.c              |   6 +-
 drivers/i2c/busses/i2c-aspeed.c                    |   3 +-
 drivers/i2c/busses/i2c-stm32f7.c                   |   9 +-
 drivers/i2c/muxes/i2c-demux-pinctrl.c              |   2 +-
 drivers/i2c/muxes/i2c-mux-gpmux.c                  |   2 +-
 drivers/i2c/muxes/i2c-mux-pinctrl.c                |   2 +-
 drivers/iio/adc/exynos_adc.c                       |  24 +-
 drivers/iio/adc/xilinx-xadc-core.c                 | 179 ++++-----
 drivers/input/mouse/synaptics.c                    |   1 +
 drivers/input/rmi4/rmi_smbus.c                     |  50 ++-
 drivers/irqchip/irq-riscv-intc.c                   |  10 +-
 drivers/irqchip/irq-stm32-exti.c                   |   1 +
 drivers/mcb/mcb-lpc.c                              |  35 +-
 drivers/mcb/mcb-parse.c                            |  15 +-
 drivers/misc/fastrpc.c                             |  10 +-
 drivers/mmc/host/renesas_sdhi_core.c               |   3 +-
 drivers/mmc/host/tmio_mmc.h                        |   2 +-
 drivers/net/ethernet/chelsio/cxgb4/t4_hw.c         |   2 +
 drivers/net/ethernet/intel/i40e/i40e_txrx.c        |   2 +-
 drivers/net/ethernet/intel/igb/igb_ethtool.c       |   6 +-
 drivers/net/ethernet/intel/igc/igc_ethtool.c       |  35 +-
 drivers/net/ethernet/realtek/r8169_main.c          |   4 +-
 drivers/net/ethernet/toshiba/ps3_gelic_wireless.c  |   2 +-
 drivers/net/gtp.c                                  |   5 +-
 drivers/net/ieee802154/adf7242.c                   |   5 +-
 drivers/net/usb/r8152.c                            |  11 +-
 drivers/net/usb/smsc95xx.c                         |   4 +-
 drivers/nvmem/imx-ocotp.c                          |   6 +-
 drivers/pci/quirks.c                               |   8 +-
 drivers/platform/mellanox/mlxbf-tmfifo.c           |  21 +-
 drivers/rpmsg/qcom_glink_native.c                  |   2 +
 drivers/rpmsg/rpmsg_core.c                         |  37 +-
 drivers/rpmsg/rpmsg_internal.h                     |   5 +-
 drivers/scsi/mpt3sas/mpt3sas_scsih.c               |   4 +-
 drivers/spi/spi-npcm-fiu.c                         |   5 +-
 drivers/tty/serial/8250/8250_pci.c                 | 122 +++++-
 drivers/usb/gadget/legacy/raw_gadget.c             |  26 +-
 drivers/usb/storage/unusual_cypress.h              |   2 +-
 drivers/video/fbdev/aty/atyfb_base.c               |   4 +
 drivers/video/fbdev/uvesafb.c                      |   2 +-
 drivers/virtio/virtio_balloon.c                    |   6 +-
 drivers/virtio/virtio_mmio.c                       |  19 +-
 fs/cifs/smbdirect.c                                |  14 +-
 fs/ext4/mballoc.c                                  |  51 +--
 fs/ext4/mballoc.h                                  |  14 +
 fs/f2fs/gc.c                                       |   3 +-
 include/linux/device/driver.h                      |   2 +
 include/linux/kasan.h                              |   6 +-
 include/linux/pci_ids.h                            |   1 +
 include/linux/platform_device.h                    |   6 +-
 include/linux/rpmsg.h                              |  14 +-
 include/uapi/linux/can/isotp.h                     |  25 +-
 include/uapi/linux/gtp.h                           |   2 +-
 kernel/events/core.c                               |   3 +-
 kernel/trace/trace_kprobe.c                        |   4 +-
 lib/kobject.c                                      |  12 +-
 mm/kasan/report.c                                  |   4 +-
 mm/page_alloc.c                                    |   2 +-
 net/can/isotp.c                                    | 446 +++++++++++++--------
 net/core/neighbour.c                               |  67 ++--
 net/ipv4/tcp_input.c                               |   9 +-
 net/netfilter/nfnetlink_log.c                      |   2 +-
 net/sched/cls_u32.c                                |   2 +-
 sound/hda/intel-dsp-config.c                       |   6 +
 sound/soc/codecs/rt5645.c                          |   2 +
 tools/objtool/check.c                              |   2 +-
 tools/perf/util/evlist.c                           |  21 +
 tools/perf/util/evlist.h                           |   5 +
 .../ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc |  13 +
 83 files changed, 1088 insertions(+), 573 deletions(-)

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Florian Fainelli]

On 11/6/23 05:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

perf fails to build with:

util/evlist.c: In function 'evlist__add_aux_dummy':
util/evlist.c:269:31: warning: implicit declaration of function 
'evlist__dummy_event'; did you mean 'evsel__is_dummy_event'? 
[-Wimplicit-function-declaration]
   269 |         struct evsel *evsel = evlist__dummy_event(evlist);
       |                               ^~~~~~~~~~~~~~~~~~~
       |                               evsel__is_dummy_event
util/evlist.c:269:31: warning: initialization of 'struct evsel *' from 
'int' makes pointer from integer without a cast [-Wint-conversion]

...

   LINK 
/local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/perf
/local/stbopt_p/toolchains_303/stbgcc-12.3-0.2/bin/../lib/gcc/aarch64-unknown-linux-musl/12.3.0/../../../../aarch64-unknown-linux-musl/bin/ld: 
/local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/perf-in.o: 
in function `evlist__add_aux_dummy':
/local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/util/evlist.c:269: 
undefined reference to `evlist__dummy_event'
collect2: error: ld returned 1 exit status

-- 
Florian

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Daniel Díaz]

Hello!

On 06/11/23 7:03 a. m., Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

There seems to be a problem building for RISC-V with GCC 8, 12, and Clang 17. This is with defconfig, allnoconfig, tinyconfig:

-----8<-----
/builds/linux/drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_init':
/builds/linux/drivers/irqchip/irq-riscv-intc.c:119:17: error: implicit declaration of function 'fwnode_dev_initialized'; did you mean 'zone_is_initialized'? [-Werror=implicit-function-declaration]
   119 |                 fwnode_dev_initialized(of_fwnode_handle(node), true);
       |                 ^~~~~~~~~~~~~~~~~~~~~~
       |                 zone_is_initialized
cc1: some warnings being treated as errors
make[3]: *** [/builds/linux/scripts/Makefile.build:286: drivers/irqchip/irq-riscv-intc.o] Error 1
make[3]: Target '__build' not remade because of errors.
make[2]: *** [/builds/linux/scripts/Makefile.build:503: drivers/irqchip] Error 2
make[2]: Target '__build' not remade because of errors.
make[1]: *** [/builds/linux/Makefile:1832: drivers] Error 2
make[1]: Target '__all' not remade because of errors.
make: *** [Makefile:192: __sub-make] Error 2
make: Target '__all' not remade because of errors.
----->8-----

Currently bisecting.

Greetings!

Daniel Díaz
daniel.diaz@linaro.org

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Daniel Díaz]

Hello!

On Mon, 6 Nov 2023 at 11:53, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> On 06/11/23 7:03 a. m., Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.200 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >       https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> > or in the git tree and branch at:
> >       git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> There seems to be a problem building for RISC-V with GCC 8, 12, and Clang 17. This is with defconfig, allnoconfig, tinyconfig:
>
> -----8<-----
> /builds/linux/drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_init':
> /builds/linux/drivers/irqchip/irq-riscv-intc.c:119:17: error: implicit declaration of function 'fwnode_dev_initialized'; did you mean 'zone_is_initialized'? [-Werror=implicit-function-declaration]
>    119 |                 fwnode_dev_initialized(of_fwnode_handle(node), true);
>        |                 ^~~~~~~~~~~~~~~~~~~~~~
>        |                 zone_is_initialized
> cc1: some warnings being treated as errors
> make[3]: *** [/builds/linux/scripts/Makefile.build:286: drivers/irqchip/irq-riscv-intc.o] Error 1
> make[3]: Target '__build' not remade because of errors.
> make[2]: *** [/builds/linux/scripts/Makefile.build:503: drivers/irqchip] Error 2
> make[2]: Target '__build' not remade because of errors.
> make[1]: *** [/builds/linux/Makefile:1832: drivers] Error 2
> make[1]: Target '__all' not remade because of errors.
> make: *** [Makefile:192: __sub-make] Error 2
> make: Target '__all' not remade because of errors.
> ----->8-----
>
> Currently bisecting.

-----8<-----
Bisection done!
First commit presenting NEW behaviour: 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b

commit 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b
Author: Anup Patel <apatel@ventanamicro.com>
Date:   Tue Oct 3 10:13:51 2023 +0530

    irqchip/riscv-intc: Mark all INTC nodes as initialized

    [ Upstream commit e13cd66bd821be417c498a34928652db4ac6b436 ]
----->8-----

Reverting that commit makes the build happy again.

Greetings!

Daniel Díaz
daniel.diaz@linaro.org

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

Hi!

> > This is the start of the stable review cycle for the 5.10.200 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > and the diffstat can be found below.
> 
> There seems to be a problem building for RISC-V with GCC 8, 12, and Clang 17. This is with defconfig, allnoconfig, tinyconfig:
> 
> -----8<-----
> /builds/linux/drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_init':
> /builds/linux/drivers/irqchip/irq-riscv-intc.c:119:17: error: implicit declaration of function 'fwnode_dev_initialized'; did you mean 'zone_is_initialized'? [-Werror=implicit-function-declaration]
>   119 |                 fwnode_dev_initialized(of_fwnode_handle(node), true);
>       |                 ^~~~~~~~~~~~~~~~~~~~~~
>       |                 zone_is_initialized
> cc1: some warnings being treated as errors
> make[3]: *** [/builds/linux/scripts/Makefile.build:286: drivers/irqchip/irq-riscv-intc.o] Error 1
> make[3]: Target '__build' not remade because of errors.
> make[2]: *** [/builds/linux/scripts/Makefile.build:503: drivers/irqchip] Error 2
> make[2]: Target '__build' not remade because of errors.
> make[1]: *** [/builds/linux/Makefile:1832: drivers] Error 2
> make[1]: Target '__all' not remade because of errors.
> make: *** [Makefile:192: __sub-make] Error 2
> make: Target '__all' not remade because of errors.
> ----->8-----

We see same problems in our risc-v build:

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/5468492319

> Currently bisecting.

Thank you!

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

Hi!

> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.

There's something wrong here.

251e8b0a0 1aee91 o: 4.14| nfsd: lock_rename() needs both directories to live on the same fs

Is present in 4.14-stable but not 5.10-stable.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Dominique Martinet]

Greg Kroah-Hartman wrote on Mon, Nov 06, 2023 at 02:03:28PM +0100:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.

Tested on:
- arm i.MX6ULL (Armadillo 640)
- arm64 i.MX8MP (Armadillo G4)

No obvious regression in dmesg or basic tests:
Tested-by: Dominique Martinet <dominique.martinet@atmark-techno.com>


By the way, I wanted to start semi-automatize this (for 5.10
specifically since that's the kernel we're based on) and started
watching the linux-stable-rc.git's linux-5.10.y branch, specifically the
rev in this command:

  git ls-remote git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git refs/heads/linux-5.10.y

And there were two different "Linux 5.10.200-rc1" commits on the 1st,
3rd before the final rev on the 6th (this mail) as I assume you were
preparing this branch (and it's perfectly fine!)
Is there anything appropriate to watch instead, or should I setup mail
filters to see the announce mail instead of trying to second-guess the
git repo?


While I'm asking questions, I'm also comparing the dmesg output from one
version to the next by hand (as ordering etc changes a bit from one run
to the next it's a bit hard to automate reliably), if you're aware of a
fuzzy-diff for dmesg outputs or should I just kludge that in a corner?
(Should have noticed the MMC quirk regression[1] in 5.10.199 if I had been
doing that properly last time... It's too easy to miss when a line just
disappears and there's no error
[1] https://lore.kernel.org/all/20231103004220.1666641-1-asmadeus@codewreck.org/
(not yet in master))


-- 
Dominique Martinet | Asmadeus

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

Hi!

> > This is the start of the stable review cycle for the 5.10.200 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> 
> There's something wrong here.
> 
> 251e8b0a0 1aee91 o: 4.14| nfsd: lock_rename() needs both directories to live on the same fs
> 
> Is present in 4.14-stable but not 5.10-stable.

|22de5d11e 41bae5 o: 4.14| ASoC: simple-card: fixup asoc_simple_probe() error handling

This one is in 4.19 and 4.14-stable, but not in 5.10.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Jon Hunter]

On Mon, 06 Nov 2023 14:03:28 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

All tests passing for Tegra ...

Test results for stable-v5.10:
    10 builds:	10 pass, 0 fail
    26 boots:	26 pass, 0 fail
    68 tests:	68 pass, 0 fail

Linux version:	5.10.200-rc1-gfed6441dbe52
Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
                tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
                tegra20-ventana, tegra210-p2371-2180,
                tegra210-p3450-0000, tegra30-cardhu-a04

Tested-by: Jon Hunter <jonathanh@nvidia.com>

Jon

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Shuah Khan]

On 11/6/23 06:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 

Compiled and booted on my test system. No dmesg regressions.

Tested-by: Shuah Khan <skhan@linuxfoundation.org>

thanks,
-- Shuah

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Naresh Kamboju]

On Mon, 6 Nov 2023 at 19:01, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
>         https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> or in the git tree and branch at:
>         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h


Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
The riscv build regressions reported.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

NOTE:
The riscv build failures already reported as others.

## Build
* kernel: 5.10.200-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.10.y
* git commit: fed6441dbe524de2cf3a6a40d5d65c369bf583a0
* git describe: v5.10.199-96-gfed6441dbe52
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.199-96-gfed6441dbe52

## Test Regressions (compared to v5.10.199)

* riscv, build
  - clang-17-allnoconfig
  - clang-17-defconfig
  - clang-17-tinyconfig
  - gcc-12-allmodconfig
  - gcc-12-allnoconfig
  - gcc-12-defconfig
  - gcc-12-tinyconfig
  - gcc-8-allmodconfig
  - gcc-8-allnoconfig
  - gcc-8-defconfig
  - gcc-8-tinyconfig


## Metric Regressions (compared to v5.10.199)

## Test Fixes (compared to v5.10.199)

## Metric Fixes (compared to v5.10.199)

## Test result summary
total: 90579, pass: 71963, fail: 2500, skip: 16053, xfail: 63

## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 116 total, 116 passed, 0 failed
* arm64: 42 total, 42 passed, 0 failed
* i386: 35 total, 35 passed, 0 failed
* mips: 23 total, 23 passed, 0 failed
* parisc: 3 total, 0 passed, 3 failed
* powerpc: 24 total, 24 passed, 0 failed
* riscv: 11 total, 0 passed, 11 failed
* s390: 11 total, 11 passed, 0 failed
* sh: 9 total, 9 passed, 0 failed
* sparc: 7 total, 7 passed, 0 failed
* x86_64: 37 total, 37 passed, 0 failed

## Test suites summary
* boot
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-exec
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-filesystems-epoll
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-sigaltstack
* kselftest-size
* kselftest-tc-testing
* kselftest-timens
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-user_events
* kselftest-vDSO
* kselftest-vm
* kselftest-watchdog
* kselftest-x86
* kselftest-zram
* kunit
* libgpiod
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* perf
* rcutorture
* v4l2-compliance

--
Linaro LKFT
https://lkft.linaro.org

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Guenter Roeck]

On Mon, Nov 06, 2023 at 02:03:28PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.200 release.
> There are 95 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> Anything received after that time might be too late.
> 

Build results:
	total: 159 pass: 149 fail: 10
Failed builds:
	i386:tools/perf
	x86_64:tools/perf
	<all riscv32/riscv64>
Qemu test results:
	total: 495 pass: 456 fail: 39
Failed tests:
	<all riscv32/riscv64>

All failures have already been reported, so I wn't go into detail.

Guenter

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Greg Kroah-Hartman]

On Mon, Nov 06, 2023 at 09:37:56AM -0800, Florian Fainelli wrote:
> On 11/6/23 05:03, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.200 release.
> > There are 95 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> perf fails to build with:
> 
> util/evlist.c: In function 'evlist__add_aux_dummy':
> util/evlist.c:269:31: warning: implicit declaration of function
> 'evlist__dummy_event'; did you mean 'evsel__is_dummy_event'?
> [-Wimplicit-function-declaration]
>   269 |         struct evsel *evsel = evlist__dummy_event(evlist);
>       |                               ^~~~~~~~~~~~~~~~~~~
>       |                               evsel__is_dummy_event
> util/evlist.c:269:31: warning: initialization of 'struct evsel *' from 'int'
> makes pointer from integer without a cast [-Wint-conversion]
> 
> ...
> 
>   LINK /local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/perf
> /local/stbopt_p/toolchains_303/stbgcc-12.3-0.2/bin/../lib/gcc/aarch64-unknown-linux-musl/12.3.0/../../../../aarch64-unknown-linux-musl/bin/ld: /local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/perf-in.o:
> in function `evlist__add_aux_dummy':
> /local/users/fainelli/buildroot/output/arm64/build/linux-custom/tools/perf/util/evlist.c:269:
> undefined reference to `evlist__dummy_event'
> collect2: error: ld returned 1 exit status

Will go fix that now, thanks.

greg k-h

Re: [PATCH 5.10 00/95] 5.10.200-rc1 review

[Greg Kroah-Hartman]

On Mon, Nov 06, 2023 at 12:14:21PM -0600, Daniel Díaz wrote:
> Hello!
> 
> On Mon, 6 Nov 2023 at 11:53, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> > On 06/11/23 7:03 a. m., Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.200 release.
> > > There are 95 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 08 Nov 2023 13:02:46 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > >       https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.200-rc1.gz
> > > or in the git tree and branch at:
> > >       git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > There seems to be a problem building for RISC-V with GCC 8, 12, and Clang 17. This is with defconfig, allnoconfig, tinyconfig:
> >
> > -----8<-----
> > /builds/linux/drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_init':
> > /builds/linux/drivers/irqchip/irq-riscv-intc.c:119:17: error: implicit declaration of function 'fwnode_dev_initialized'; did you mean 'zone_is_initialized'? [-Werror=implicit-function-declaration]
> >    119 |                 fwnode_dev_initialized(of_fwnode_handle(node), true);
> >        |                 ^~~~~~~~~~~~~~~~~~~~~~
> >        |                 zone_is_initialized
> > cc1: some warnings being treated as errors
> > make[3]: *** [/builds/linux/scripts/Makefile.build:286: drivers/irqchip/irq-riscv-intc.o] Error 1
> > make[3]: Target '__build' not remade because of errors.
> > make[2]: *** [/builds/linux/scripts/Makefile.build:503: drivers/irqchip] Error 2
> > make[2]: Target '__build' not remade because of errors.
> > make[1]: *** [/builds/linux/Makefile:1832: drivers] Error 2
> > make[1]: Target '__all' not remade because of errors.
> > make: *** [Makefile:192: __sub-make] Error 2
> > make: Target '__all' not remade because of errors.
> > ----->8-----
> >
> > Currently bisecting.
> 
> -----8<-----
> Bisection done!
> First commit presenting NEW behaviour: 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b
> 
> commit 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b
> Author: Anup Patel <apatel@ventanamicro.com>
> Date:   Tue Oct 3 10:13:51 2023 +0530
> 
>     irqchip/riscv-intc: Mark all INTC nodes as initialized
> 
>     [ Upstream commit e13cd66bd821be417c498a34928652db4ac6b436 ]
> ----->8-----
> 
> Reverting that commit makes the build happy again.

Thanks, will go drop that now.

greg k-h