* Linux 5.18-rc6
@ 2022-05-08 21:09 Linus Torvalds
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Linus Torvalds @ 2022-05-08 21:09 UTC (permalink / raw)
To: Linux Kernel Mailing List
So 5.18 is looking like it's going to be one of the larger releases in
numbers of commits (we'll see where it ends up - it's going to be
neck-and-neck with 5.14 right now, but won't be as big as 5.13 was).
But despite the merge window being big, the release candidates have
generally been quite modest in size, and rc6 continues that trend. I
keep expecting the other shoe to drop, but 5.18 just seems to be quite
well-behaved.
Let's see if this jinxes it, but nothing looks particularly scary
here. rc6 looks to be mostly some driver updates (network drivers and
rdma stand out, small random fixes elsewhere), with the usual
smattering of architecture updates (x86 kvm fixes, but also a
long-standing x86 kernel FP use issue, and a smattering of parisc and
powerpc fixes). And some wireguard selftest updates.
The rest is mostly some btrfs fixes, some core networking, and just
random small one-offs elsewhere.
Please do go test it all out - because things may look good now, but
continued testing is the only thing that will make sure.
Thanks,
Linus
---
Adam Wujek (1):
hwmon: (pmbus) disable PEC if not enabled
Ajit Kumar Pandey (1):
ASoC: SOF: Fix NULL pointer exception in sof_pci_probe callback
Andreas Larsson (2):
can: grcan: grcan_probe(): fix broken system id check for errata
workaround needs
can: grcan: only use the NAPI poll budget for RX
Andrei Lalaev (1):
gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
André Almeida (1):
futex: MAINTAINERS, .mailmap: Update André's email address
Andy Chi (1):
ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops
Ariel Levkovich (4):
net/mlx5e: Fix wrong source vport matching on tunnel rule
net/mlx5e: TC, Fix ct_clear overwriting ct action metadata
net/mlx5e: TC, fix decap fallback to uplink when int port not supported
net/mlx5e: Avoid checking offload capability in post_parse action
Armin Wolf (1):
hwmon: (adt7470) Fix warning on module removal
Arun Ramadoss (1):
net: dsa: ksz9477: port mirror sniffing limited to one port
Ashish Mhetre (1):
iommu: arm-smmu: disable large page mappings for Nvidia arm-smmu
Aya Levin (1):
net/mlx5: Fix slab-out-of-bounds while reading resource dump menu
Bartosz Golaszewski (1):
MAINTAINERS: update the GPIO git tree entry
Baruch Siach (1):
gpio: mvebu: drop pwm base assignment
Bob Pearson (4):
RDMA/rxe: Fix "Replace mr by rkey in responder resources"
RDMA/rxe: Recheck the MR in when generating a READ reply
RDMA/rxe: Do not call dev_mc_add/del() under a spinlock
RDMA/rxe: Change mcg_lock to a _bh lock
Brian Norris (1):
mmc: core: Set HS clock speed before sending HS CMD13
Cheng Xu (1):
RDMA/siw: Fix a condition race issue in MPA request processing
Chengfeng Ye (1):
firewire: fix potential uaf in outbound_phy_packet_callback()
ChiYuan Huang (1):
ASoC: rt9120: Correct the reg 0x09 size to one byte
Christian Borntraeger (1):
KVM: s390: vsie/gmap: reduce gmap_rmap overhead
Chung-Chiang Cheng (2):
btrfs: export a helper for compression hard check
btrfs: do not allow compression on nodatacow files
Codrin Ciubotariu (2):
ASoC: atmel: mchp-pdmc: set prepare_slave_config
ASoC: dmaengine: Restore NULL prepare_slave_config() callback
Corey Minyard (2):
ipmi: When handling send message responses, don't process the message
ipmi:ipmi_ipmb: Fix null-ptr-deref in ipmi_unregister_smi()
Daniel Hellstrom (1):
can: grcan: use ofdev->dev when allocating DMA memory
David Howells (1):
rxrpc: Enable IPv6 checksums on transport socket
David Sterba (1):
btrfs: sysfs: export the balance paused state of exclusive operation
David Stevens (1):
iommu/vt-d: Calculate mask for non-aligned flushes
Denis Pauk (1):
hwmon: (asus_wmi_sensors) Fix CROSSHAIR VI HERO name
Duoming Zhou (5):
RDMA/irdma: Fix deadlock in irdma_cleanup_cm_core()
can: grcan: grcan_close(): fix deadlock
nfc: replace improper check device_is_registered() in netlink
related functions
nfc: nfcmrvl: main: reorder destructive operations in
nfcmrvl_nci_unregister_dev to avoid bugs
NFC: netlink: fix sleep in atomic bug when firmware download timeout
Eric Dumazet (3):
net: igmp: respect RCU rules in ip_mc_source() and ip_mc_msfilter()
mld: respect RCU rules in ip6_mc_source() and ip6_mc_msfilter()
tcp: resalt the secret every 10 seconds
Fabien Parent (1):
drm/bridge: ite-it6505: add missing Kconfig option select
Fenghua Yu (1):
mm: Fix PASID use-after-free issue
Filipe Manana (4):
btrfs: always log symlinks in full mode
btrfs: do not BUG_ON() on failure to update inode when setting xattr
btrfs: skip compression property for anything other than files and dirs
btrfs: fix assertion failure when logging directory key range item
Guenter Roeck (1):
hwmon: (xdpe12284) Fix build warning seen if
CONFIG_SENSORS_XDPE122_REGULATOR is disabled
Hangbin Liu (2):
selftests/net: add missing tests to Makefile
selftests/net/forwarding: add missing tests to Makefile
Haowen Bai (1):
s390/dasd: Use kzalloc instead of kmalloc/memset
Haren Myneni (1):
powerpc/pseries/vas: Use QoS credits from the userspace
Harry Wentland (1):
drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
Hector Martin (2):
iommu/dart: Add missing module owner to ops structure
dt-bindings: pci: apple,pcie: Drop max-link-speed from example
Helge Deller (10):
Revert "parisc: Mark cr16 CPU clocksource unstable on all SMP machines"
Revert "parisc: Mark sched_clock unstable only if clocks are not
syncronized"
Revert "parisc: Fix patch code locking and flushing"
parisc: Only list existing CPUs in cpu_possible_mask
parisc: Update 32- and 64-bit defconfigs
parisc: Re-enable GENERIC_CPU_DEVICES for !SMP
parisc: Merge model and model name into one line in /proc/cpuinfo
parisc: Change MAX_ADDRESS to become unsigned long long
parisc: Mark cr16 clock unstable on all SMP machines
Revert "parisc: Increase parisc_cache_flush_threshold setting"
Hui Wang (1):
ALSA: hda/realtek: Fix mute led issue on thinkpad with cs35l41 s-codec
Ido Schimmel (1):
selftests: mirror_gre_bridge_1q: Avoid changing PVID while
interface is operational
Jakob Koschel (1):
firewire: remove check of list iterator against head past the loop body
Jan Höppner (2):
s390/dasd: Fix read for ESE with blksize < 4k
s390/dasd: Fix read inconsistency for ESE DASD devices
Janis Schoetterl-Glausch (1):
KVM: s390: Fix lockdep issue in vm memop
Jann Horn (1):
selftests/seccomp: Don't call read() on TTY from background pgrp
Jason A. Donenfeld (6):
wireguard: selftests: make routing loop test non-fatal
wireguard: selftests: limit parallelism to $(nproc) tests at once
wireguard: selftests: use newer toolchains to fill out architectures
wireguard: selftests: restore support for ccache
wireguard: selftests: bump package deps
wireguard: selftests: set panic_on_warn=1 from cmdline
Javier Martinez Canillas (1):
fbdev: Make fb_release() return -ENODEV if fbdev was unregistered
Jens Axboe (1):
io_uring: assign non-fixed early for async work
Ji-Ze Hong (Peter Hong) (1):
hwmon: (f71882fg) Fix negative temperature
John Stultz (1):
MAINTAINERS: Update email address for John Stultz
Josh Poimboeuf (1):
MAINTAINERS: Update Josh Poimboeuf's email address
Julia Lawall (1):
parisc: Fix typos in comments
Kajol Jain (1):
powerpc/papr_scm: Fix buffer overflow issue with CONFIG_FORTIFY_SOURCE
Krzysztof Kozlowski (1):
dt-bindings: ufs: cdns,ufshc: Add power-domains
Kuogee Hsieh (1):
drm/msm/dp: remove fail safe mode related code
Kurt Kanzenbach (1):
timekeeping: Mark NMI safe time accessors as notrace
Kyle Huey (1):
KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
Linus Torvalds (1):
Linux 5.18-rc6
Lu Baolu (1):
iommu/vt-d: Drop stop marker messages
Maciej W. Rozycki (1):
MIPS: Fix CP0 counter erratum detection for R4k CPUs
Marc Kleine-Budde (2):
selftests/net: so_txtime: fix parsing of start time stamp on 32
bit systems
selftests/net: so_txtime: usage(): fix documentation of default clock
Marek Marczykowski-Górecki (1):
drm/amdgpu: do not use passthrough mode in Xen dom0
Mark Bloch (1):
net/mlx5: Fix matching on inner TTC
Mark Brown (8):
ASoC: wm8958: Fix change notifications for DSP controls
ASoC: da7219: Fix change notifications for tone generator frequency
ASoC: meson: Fix event generation for AUI ACODEC mux
ASoC: meson: Fix event generation for AUI CODEC mux
ASoC: meson: Fix event generation for G12A tohdmi mux
ASoC: max98090: Reject invalid values in custom control put()
ASoC: max98090: Generate notifications on changes for custom control
ASoC: ops: Validate input values in snd_soc_put_volsw_range()
Mark Zhang (1):
net/mlx5e: Fix the calling of update_buffer_lossy() API
Matthew Hagan (1):
net: sfp: Add tx-fault workaround for Huawei MA5671A SFP ONT
Matthew Wilcox (Oracle) (2):
block: Do not call folio_next() on an unreferenced folio
mm/readahead: Fix readahead with large folios
Michael Chan (2):
bnxt_en: Initiallize bp->ptp_lock first before using it
bnxt_en: Fix unnecessary dropping of RX packets
Michael Ellerman (1):
powerpc/vdso: Fix incorrect CFI in gettimeofday.S
Ming Lei (1):
Revert "block: release rq qos structures for queue without disk"
Moshe Shemesh (2):
net/mlx5: Fix deadlock in sync reset flow
net/mlx5: Avoid double clear or set of sync reset requested
Moshe Tal (1):
net/mlx5e: Fix trust state reset in reload
Mustafa Ismail (1):
RDMA/irdma: Fix possible crash due to NULL netdev in notifier
Naohiro Aota (2):
btrfs: zoned: move non-changing condition check out of the loop
btrfs: zoned: activate block group properly on unlimited active
zone device
Neil Armstrong (2):
ASoC: meson: axg-tdm-interface: Fix formatters in trigger"
ASoC: meson: axg-card: Fix nonatomic links
Nick Kossifidis (1):
RISC-V: relocate DTB if it's outside memory region
Nicolin Chen (1):
iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
Niels Dossche (2):
firewire: core: extend card->lock in fw_core_handle_bus_reset
net: mdio: Fix ENOMEM return value in BCM6368 mux bus controller
Nobuhiro Iwamatsu (1):
gpio: visconti: Fix fwnode of GPIO IRQ
Olga Kornievskaia (1):
SUNRPC release the transport of a relocated task with an
assigned transport
Oliver Hartkopp (1):
can: isotp: remove re-binding of bound socket
Olivier Moysan (1):
ASoC: simple-card-utils: fix sysclk shutdown
Paul Blakey (1):
net/mlx5e: CT: Fix queued up restore put() executing after
relevant ft release
Peter Gonda (1):
KVM: SEV: Mark nested locking of vcpu->lock
Pierre-Louis Bossart (1):
ASoC: soc-ops: fix error handling
Puyou Lu (1):
gpio: pca953x: fix irq_stat not updated when irq is disabled
(irq_mask not set)
Qiao Ma (1):
hinic: fix bug of wq out of bound access
Qu Wenruo (1):
btrfs: force v2 space cache usage for subpage mount
Rob Herring (4):
dt-bindings: hwmon: ti,tmp421: Fix type for 'ti,n-factor'
dt-bindings: leds-mt6360: Drop redundant 'unevaluatedProperties'
dt-bindings: pinctrl: Allow values for drive-push-pull and
drive-open-drain
dt-bindings: Drop redundant 'maxItems/minItems' in if/then schemas
Robin Murphy (1):
iommu: Make sysfs robust for non-API groups
Russell King (Oracle) (1):
net: dsa: b53: convert to phylink_pcs
Samuel Holland (1):
mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
Sandipan Das (1):
kvm: x86/cpuid: Only provide CPUID leaf 0xA if host has architectural PMU
Sean Christopherson (4):
KVM: x86/mmu: Don't treat fully writable SPTEs as volatile (modulo A/D)
KVM: x86/mmu: Move shadow-present check out of spte_has_volatile_bits()
KVM: x86/mmu: Use atomic XCHG to write TDP MMU SPTEs with volatile bits
KVM: VMX: Exit to userspace if vCPU has injected exception and
invalid state
Sergey Shtylyov (1):
smsc911x: allow using IRQ0
Shaik Sajida Bhanu (1):
mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
Shiraz Saleem (1):
RDMA/irdma: Reduce iWARP QP destroy time
Shravya Kumbham (2):
net: emaclite: Don't advertise 1000BASE-T and do auto negotiation
net: emaclite: Add error handling for of_address_to_resource()
Somnath Kotur (1):
bnxt_en: Fix possible bnxt_open() failure caused by wrong RFS flag
Stefan Haberland (2):
s390/dasd: fix data corruption for ESE devices
s390/dasd: prevent double format of tracks for ESE devices
Sven Schnelle (1):
s390: disable -Warray-bounds
Takashi Sakamoto (1):
ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
Tan Tee Min (1):
net: stmmac: disable Split Header (SPH) for Intel platforms
Tatyana Nikolova (1):
RDMA/irdma: Flush iWARP QP if modified to ERR from RTR state
Tetsuo Handa (1):
net: rds: acquire refcount on TCP sockets
Thomas Gleixner (2):
pci_irq_vector() can't be used in atomic context any longer.
This conflicts with the usage of this function in
nic_mbx_intr_handler().
x86/fpu: Prevent FPU state corruption
Thomas Pfaff (1):
genirq: Synchronize interrupt thread startup
Trond Myklebust (5):
NFSv4: Don't invalidate inode attributes on delegation return
SUNRPC: Don't leak sockets in xs_local_connect()
SUNRPC: Ensure timely close of disconnected AF_LOCAL sockets
SUNRPC: Ensure gss-proxy connects on setup
Revert "SUNRPC: attempt AF_LOCAL connect on setup"
Vlad Buslov (4):
net/mlx5e: Don't match double-vlan packets if cvlan is not set
net/mlx5e: Lag, Fix use-after-free in fib event handler
net/mlx5e: Lag, Fix fib_info pointer assignment
net/mlx5e: Lag, Don't skip fib events on current dst
Vladimir Oltean (1):
selftests: ocelot: tc_flower_chains: specify conform-exceed
action for policer
Willy Tarreau (9):
secure_seq: use the 64 bits of the siphash for port offset calculation
tcp: use different parts of the port_offset for index and offset
tcp: add small random increments to the source port
tcp: dynamically allocate the perturb table used by source ports
tcp: increase source port perturb table to 2^16
tcp: drop the hash_32() part from the index calculation
floppy: use a statically allocated error counter
ataflop: use a statically allocated error counters
blk-mq: remove the error_count from struct request
Yang Yingliang (5):
iommu/dart: check return value after calling platform_get_resource()
net: ethernet: mediatek: add missing of_node_put() in mtk_sgmii_init()
net: dsa: mt7530: add missing of_node_put() in mt7530_setup()
net: stmmac: dwmac-sun8i: add missing of_node_put() in
sun8i_dwmac_register_mdio_mux()
net: cpsw: add missing of_node_put() in cpsw_probe_dt()
Zev Weiss (1):
hwmon: (pmbus) delta-ahe50dc-fan: work around hardware quirk
Zihao Wang (1):
ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
^ permalink raw reply [flat|nested] 12+ messages in thread
* Build regressions/improvements in v5.18-rc6
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
@ 2022-05-09 8:40 ` Geert Uytterhoeven
2022-05-09 9:13 ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck
2 siblings, 1 reply; 12+ messages in thread
From: Geert Uytterhoeven @ 2022-05-09 8:40 UTC (permalink / raw)
To: linux-kernel
Below is the list of build error/warning regressions/improvements in
v5.18-rc6[1] compared to v5.17[2].
Summarized:
- build errors: +14/-5
- build warnings: +36/-21
JFYI, when comparing v5.18-rc6[1] to v5.18-rc5[3], the summaries are:
- build errors: +1/-0
- build warnings: +0/-1
Note that there may be false regressions, as some logs are incomplete.
Still, they're build errors/warnings.
Happy fixing! ;-)
Thanks to the linux-next team for providing the build service.
[1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/c5eb0a61238dd6faf37f58c9ce61c9980aaffd7a/ (131 out of 138 configs)
[2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/f443e374ae131c168a065ea1748feac6b2e76613/ (96 out of 138 configs)
[3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/672c0c5173427e6b3e2a9bbb7be51ceeec78093a/ (all 138 configs)
*** ERRORS ***
14 error regressions:
+ /kisskb/src/arch/m68k/include/asm/bitops.h: error: array subscript 2 is above array bounds of 'long unsigned int[1]' [-Werror=array-bounds]: => 329:20
+ /kisskb/src/arch/sh/kernel/machvec.c: error: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Werror=array-bounds]: => 105:33
+ /kisskb/src/arch/sparc/kernel/irq_32.c: error: array subscript [16, 79] is outside array bounds of 'struct tt_entry[1]' [-Werror=array-bounds]: => 261:46, 262:14, 259:14, 258:14, 263:14
+ /kisskb/src/drivers/gpu/drm/r128/r128_cce.c: error: case label does not reduce to an integer constant: => 417:2, 418:2
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'X86_VENDOR_AMD' undeclared (first use in this function): => 149:37
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'struct cpuinfo_um' has no member named 'x86_vendor': => 149:22
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: control reaches end of non-void function [-Werror=return-type]: => 150:1
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: 'struct cpuinfo_um' has no member named 'x86_cache_size': => 88:22
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: control reaches end of non-void function [-Werror=return-type]: => 89:1
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: implicit declaration of function '__copy_user_nocache' [-Werror=implicit-function-declaration]: => 100:2
+ /kisskb/src/drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c: error: case label does not reduce to an integer constant: => 4917:4
+ /kisskb/src/drivers/scsi/aacraid/commsup.c: error: case label does not reduce to an integer constant: => 1983:2
+ /kisskb/src/include/linux/sh_intc.h: error: division 'sizeof (void *) / sizeof (void)' does not compute the number of array elements [-Werror=sizeof-pointer-div]: => 100:63
+ {standard input}: Error: branch to a symbol in another ISA mode: => 1295
5 error improvements:
- /kisskb/src/drivers/vfio/pci/vfio_pci_rdwr.c: error: assignment makes pointer from integer without a cast [-Werror=int-conversion]: 324:9, 317:9 =>
- /kisskb/src/drivers/vfio/pci/vfio_pci_rdwr.c: error: implicit declaration of function 'ioport_map' [-Werror=implicit-function-declaration]: 317:11 =>
- /kisskb/src/drivers/vfio/pci/vfio_pci_rdwr.c: error: implicit declaration of function 'ioport_unmap' [-Werror=implicit-function-declaration]: 338:15 =>
- error: arch/powerpc/kvm/book3s_64_entry.o: relocation truncated to fit: R_PPC64_REL14 (stub) against symbol `machine_check_common' defined in .text section in arch/powerpc/kernel/head_64.o: (.text+0x3e4) =>
- error: arch/powerpc/kvm/book3s_64_entry.o: relocation truncated to fit: R_PPC64_REL14 (stub) against symbol `system_reset_common' defined in .text section in arch/powerpc/kernel/head_64.o: (.text+0x3ec) =>
*** WARNINGS ***
36 warning regressions:
+ ./.config.32r1_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 94
+ ./.config.32r2_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 94
+ ./.config.32r6_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 96
+ ./.config.64r1_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 97
+ ./.config.64r2_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 97
+ ./.config.64r6_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 99
+ ./.config.micro32r2_defconfig: warning: override: CPU_BIG_ENDIAN changes choice state: => 95
+ .config: warning: override: CPU_BIG_ENDIAN changes choice state: => 93, 98, 96, 95, 94
+ .config: warning: override: reassigning to symbol MIPS_CPS_NS16550_SHIFT: 13516, 13503 => 13758, 13763, 13769
+ /kisskb/src/arch/m68k/include/asm/string.h: warning: '__builtin_memset' offset [0, 11] is out of the bounds [0, 0] [-Warray-bounds]: => 68:25
+ /kisskb/src/arch/sh/kernel/cpu/sh2/../../entry-common.S: Warning: overflow in branch to __restore_all; converted into longer instruction sequence: => 85
+ /kisskb/src/arch/sh/kernel/cpu/sh2/../../entry-common.S: Warning: overflow in branch to syscall_exit_work; converted into longer instruction sequence: => 360, 357
+ /kisskb/src/arch/sh/kernel/machvec.c: warning: array subscript 'struct sh_machine_vector[0]' is partly outside array bounds of 'long int[1]' [-Warray-bounds]: => 105:33
+ /kisskb/src/drivers/net/ethernet/i825xx/sun3_82586.c: warning: array subscript 1 is above array bounds of 'volatile struct transmit_cmd_struct *[1]' [-Warray-bounds]: => 989:122, 989:108
+ /kisskb/src/drivers/scsi/mpt3sas/mpt3sas_base.c: warning: array subscript 'Mpi2SasIOUnitPage1_t {aka struct _MPI2_CONFIG_PAGE_SASIOUNIT_1}[0]' is partly outside array bounds of 'unsigned char[20]' [-Warray-bounds]: => 5396:40, 5400:40, 5403:43
+ /kisskb/src/fs/ext4/readpage.c: warning: the frame size of 1136 bytes is larger than 1024 bytes [-Wframe-larger-than=]: => 407:1
+ /kisskb/src/fs/mpage.c: warning: the frame size of 1088 bytes is larger than 1024 bytes [-Wframe-larger-than=]: => 303:1
+ /kisskb/src/fs/mpage.c: warning: the frame size of 1148 bytes is larger than 1024 bytes [-Wframe-larger-than=]: => 636:1
+ /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/aarch64-linux/bin/../lib/gcc/aarch64-linux/5.5.0/plugin/include/config/elfos.h: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]: => 102:21, 170:24
+ /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/aarch64-linux/bin/../lib/gcc/aarch64-linux/5.5.0/plugin/include/defaults.h: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]: => 126:24
+ modpost: WARNING: modpost: EXPORT symbol "___rw_read_enter" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "___rw_read_exit" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "___rw_read_try" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "___rw_write_enter" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__ashldi3" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__ashrdi3" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__copy_1page" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__divdi3" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__lshrdi3" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__muldi3" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__ndelay" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "__udelay" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "_mcount" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "bzero_1page" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: EXPORT symbol "empty_zero_page" [vmlinux] version generation failed, symbol will not be versioned.: => N/A
+ modpost: WARNING: modpost: vmlinux.o(.text.unlikely+0x45d4): Section mismatch in reference from the function __trace_event_discard_commit() to the variable .init.data:initcall_level_names: => N/A
21 warning improvements:
- /kisskb/src/samples/seccomp/user-trap.c: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]: 83:2, 50:2 =>
- /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/../lib/gcc/aarch64-buildroot-linux-gnu/5.4.0/plugin/include/config/elfos.h: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]: 170:24, 102:21 =>
- /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/../lib/gcc/aarch64-buildroot-linux-gnu/5.4.0/plugin/include/defaults.h: warning: invalid suffix on literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]: 126:24 =>
- modpost: WARNING: modpost: EXPORT symbol "___rw_read_enter" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "___rw_read_exit" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "___rw_read_try" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "___rw_write_enter" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__ashldi3" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__ashrdi3" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__copy_1page" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__divdi3" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__lshrdi3" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__muldi3" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__ndelay" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "__udelay" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "_mcount" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "bzero_1page" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: EXPORT symbol "empty_zero_page" [vmlinux] version ...: N/A =>
- modpost: WARNING: modpost: vmlinux.o(.text.unlikely+0x4530): Section mismatch in reference from the function __trace_event_discard_commit() to the variable .init.data:initcall_level_names: N/A =>
- warning: LSE atomics not supported by binutils: N/A =>
- warning: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum: N/A =>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Build regressions/improvements in v5.18-rc6B
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
@ 2022-05-09 9:13 ` Geert Uytterhoeven
0 siblings, 0 replies; 12+ messages in thread
From: Geert Uytterhoeven @ 2022-05-09 9:13 UTC (permalink / raw)
To: linux-kernel; +Cc: linux-crypto, sparclinux
On Mon, 9 May 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v5.18-rc6[1] to v5.18-rc5[3], the summaries are:
> - build errors: +1/-0
+ /kisskb/src/crypto/blake2b_generic.c: error: the frame size of 2288 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]: => 109:1
sparc64-gcc11/sparc-allmodconfig
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/c5eb0a61238dd6faf37f58c9ce61c9980aaffd7a/ (131 out of 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/672c0c5173427e6b3e2a9bbb7be51ceeec78093a/ (all 138 configs)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 12+ messages in thread
* Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
@ 2022-05-09 10:47 ` Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20 ` Linus Torvalds
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck
2 siblings, 1 reply; 12+ messages in thread
From: Regzbot (on behalf of Thorsten Leemhuis) @ 2022-05-09 10:47 UTC (permalink / raw)
To: LKML, Linus Torvalds, Linux regressions mailing list
Hi Linus! Here's a quick compilation of open reports about regressions in
5.18-rc that I'm currently aware of; most of the reports are quite
recent and there afaics is nothing that looks particularly worrisome.
Sorry, I didn't get around to sent any reports in that past few weeks, I
simply didn't find enough time to get on top of things to compile a
meaningful report. But I nevertheless had an eye on things an poked some
developers when it seemed there wasn't any progress.
On reason why I was short on time: the number of tracked open
regressions increased a bit over the past few weeks. Most of them are
found in older cycles. Listing them all here would make the report quite
long and hard to read -- and people then might stop reading them, which
I'd like to avoid. That's why I stopped including all and only focused
on the ones in the current cycle. Is that okay for you? Or would you
prefer to have at least those from the previous cycle listed as well? Or
at least all that were bisected? Or should I split things up over
multiple reports? Or is having the others on the website enough for
everyone?
Ciao, Thorsten
---
Hi, this is regzbot, the Linux kernel regression tracking bot.
Currently I'm aware of 5 regressions in linux-mainline that
where introduced this cycle. Find the current status below
and the latest on the web:
https://linux-regtracking.leemhuis.info/regzbot/mainline/
Regressions from previous cycles are listed there as well.
Bye bye, hope to see you soon for the next report.
Regzbot (on behalf of Thorsten Leemhuis)
========================================================
current cycle (v5.17.. aka v5.18-rc), culprit identified
========================================================
[ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
-----------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
Introduced in b5cfe6f7a6e1 (v5.18-rc1)
Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
[ *NEW* ] net: atlantic: Crash on resume after suspend (5.17.5 and 5.15.36)
---------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/9-Ehc_xXSwdXcvZqKD5aSqsqeNj5Izco4MYEwnx5cySXVEc9-x_WC4C3kAoCqNTi-H38frroUK17iobNVnkLtW36V6VWGSQEOHXhmVMm5iQ=@protonmail.com/
https://lore.kernel.org/stable/9-Ehc_xXSwdXcvZqKD5aSqsqeNj5Izco4MYEwnx5cySXVEc9-x_WC4C3kAoCqNTi-H38frroUK17iobNVnkLtW36V6VWGSQEOHXhmVMm5iQ=@protonmail.com/
By Jordan Leppert; 4 days ago; 22 activities, latest 1 days ago.
Introduced in cbe6c3a8f8f4 (v5.18-rc4)
Recent activities from: Manuel Ullmann (11), Jordan Leppert (4), Holger
Hoffstätte (4), Thorsten Leemhuis (2), Igor Russkikh (1)
Noteworthy links:
* [PATCH] net: atlantic: always deep reset on pm op, fixing null deref regression
https://lore.kernel.org/lkml/87czgt2bsb.fsf@posteo.de/
4 days ago, by Manuel Ullmann; thread monitored.
* [PATCH v2] net: atlantic: always deep reset on pm op, fixing null deref regression
https://lore.kernel.org/lkml/877d6zirmy.fsf@posteo.de/
3 days ago, by Manuel Ullmann; thread monitored.
* [PATCH v3] net: atlantic: always deep reset on pm op, fixing null deref regression
https://lore.kernel.org/lkml/8735hniqcm.fsf@posteo.de/
3 days ago, by Manuel Ullmann; thread monitored.
* [PATCH net-next v4] net: atlantic: always deep reset on pm op, fixing up my null deref regression
https://lore.kernel.org/lkml/87zgjtz4sb.fsf@posteo.de/
1 days ago, by Manuel Ullmann; thread monitored.
* [PATCH net-next v5] net: atlantic: always deep reset on pm op, fixing up my null deref regression
https://lore.kernel.org/lkml/87fsllcd80.fsf@posteo.de/
1 days ago, by Manuel Ullmann; thread monitored.
* [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression
https://lore.kernel.org/lkml/87bkw8dfmp.fsf@posteo.de/
1 days ago, by Manuel Ullmann; thread monitored.
* [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression
https://lore.kernel.org/lkml/87bkw8dfmp.fsf@posteo.de/
1 days ago, by Manuel Ullmann; thread monitored.
[ *NEW* ] net: dpaa2: TSO offload on lx2160a causes fatal exception in interrupt
--------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/7ca81e6b-85fd-beff-1c2b-62c86c9352e9@leemhuis.info/
https://lore.kernel.org/netdev/7ca81e6b-85fd-beff-1c2b-62c86c9352e9@leemhuis.info/
By Unkown; 5 days ago; 2 activities, latest 5 days ago.
Introduced in 3dc709e0cd47 (v5.18-rc1)
Recent activities from: Ioana Ciornei (1), Thorsten Leemhuis (1)
Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215886
====================================================
current cycle (v5.17.. aka v5.18-rc), unkown culprit
====================================================
[ *NEW* ] rdma: hangs in blktests since 5.18-rc1+
-------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/e7c31ebb-60c0-cd57-2009-5e9383ecc472@gmail.com/
https://lore.kernel.org/linux-rdma/e7c31ebb-60c0-cd57-2009-5e9383ecc472@gmail.com/
By Bob Pearson; 2 days ago; 10 activities, latest 0 days ago.
Introduced in v5.17..v5.18-rc6
Recent activities from: Yanjun Zhu (3), Bob Pearson (3), Bart Van
Assche (2), Zhu Yanjun (1), Jason Gunthorpe (1)
[ *NEW* ] input/usb/???: bcm5974 trackpad causes error: xhci_hcd rejecting DMA map of vmalloc memory
----------------------------------------------------------------------------------------------------
https://linux-regtracking.leemhuis.info/regzbot/regression/76e24afa-ad7d-bf6d-d610-df61851b3e2b@leemhuis.info/
https://lore.kernel.org/linux-usb/76e24afa-ad7d-bf6d-d610-df61851b3e2b@leemhuis.info/
By Satadru Pramanik; 5 days ago; 1 activities, latest 5 days ago.
Introduced in v5.17..v5.18-rc4
Recent activities from: Thorsten Leemhuis (1)
Noteworthy links:
* https://bugzilla.kernel.org/show_bug.cgi?id=215890
=============
End of report
=============
All regressions marked '[ *NEW* ]' were added since the previous report,
which can be found here:
https://lore.kernel.org/r/164779309771.379023.10823585483674878438@leemhuis.info
Thanks for your attention, have a nice day!
Regzbot, your hard working Linux kernel regression tracking robot
P.S.: Wanna know more about regzbot or how to use it to track regressions
for your subsystem? Then check out the getting started guide or the
reference documentation:
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
The short version: if you see a regression report you want to see
tracked, just send a reply to the report where you Cc
regressions@lists.linux.dev with a line like this:
#regzbot introduced: v5.13..v5.14-rc1
If you want to fix a tracked regression, just do what is expected
anyway: add a 'Link:' tag with the url to the report, e.g.:
Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
@ 2022-05-09 17:20 ` Linus Torvalds
2022-05-09 19:04 ` Hans de Goede
0 siblings, 1 reply; 12+ messages in thread
From: Linus Torvalds @ 2022-05-09 17:20 UTC (permalink / raw)
To: Regzbot (on behalf of Thorsten Leemhuis),
Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen
Cc: LKML, Linux regressions mailing list
On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
Leemhuis) <regressions@leemhuis.info> wrote:
>
> Hi Linus! Here's a quick compilation of open reports about regressions in
> 5.18-rc that I'm currently aware of; most of the reports are quite
> recent and there afaics is nothing that looks particularly worrisome.
Well, the Intel GPU issue seems likely to cause problems for lots of people:
> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
> -----------------------------------------------------------------------------------------
> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>
> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>
> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
Although it looks possible that it mainly affects old chipsets (ie the
two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
idea how they compare).
That probably means there are a lot of machines out there, but likely
not the kind that most kernel developers will be testing, so not a ton
of reports until it hits distro kernels etc.
It looks like Maarten is already involved.
Linus
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-09 17:20 ` Linus Torvalds
@ 2022-05-09 19:04 ` Hans de Goede
2022-05-10 14:41 ` Maarten Lankhorst
2022-05-17 15:50 ` Hans de Goede
0 siblings, 2 replies; 12+ messages in thread
From: Hans de Goede @ 2022-05-09 19:04 UTC (permalink / raw)
To: Linus Torvalds, Regzbot (on behalf of Thorsten Leemhuis),
Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen
Cc: LKML, Linux regressions mailing list
Hi,
On 5/9/22 19:20, Linus Torvalds wrote:
> On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>>
>> Hi Linus! Here's a quick compilation of open reports about regressions in
>> 5.18-rc that I'm currently aware of; most of the reports are quite
>> recent and there afaics is nothing that looks particularly worrisome.
>
> Well, the Intel GPU issue seems likely to cause problems for lots of people:
>
>> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
>> -----------------------------------------------------------------------------------------
>> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>
>> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
>> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>>
>> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
>
> Although it looks possible that it mainly affects old chipsets (ie the
> two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
> idea how they compare).
>
> That probably means there are a lot of machines out there, but likely
> not the kind that most kernel developers will be testing, so not a ton
> of reports until it hits distro kernels etc.
>
> It looks like Maarten is already involved.
This is being tracked here:
https://gitlab.freedesktop.org/drm/intel/-/issues/5806
I've just tested a patch from Maarten which fixes things for me,
so hopefully we can get this resolved soon.
Regards,
Hans
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux 5.18-rc6
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
@ 2022-05-09 23:06 ` Guenter Roeck
2 siblings, 0 replies; 12+ messages in thread
From: Guenter Roeck @ 2022-05-09 23:06 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, May 08, 2022 at 02:09:27PM -0700, Linus Torvalds wrote:
> So 5.18 is looking like it's going to be one of the larger releases in
> numbers of commits (we'll see where it ends up - it's going to be
> neck-and-neck with 5.14 right now, but won't be as big as 5.13 was).
> But despite the merge window being big, the release candidates have
> generally been quite modest in size, and rc6 continues that trend. I
> keep expecting the other shoe to drop, but 5.18 just seems to be quite
> well-behaved.
>
> Let's see if this jinxes it, but nothing looks particularly scary
> here. rc6 looks to be mostly some driver updates (network drivers and
> rdma stand out, small random fixes elsewhere), with the usual
> smattering of architecture updates (x86 kvm fixes, but also a
> long-standing x86 kernel FP use issue, and a smattering of parisc and
> powerpc fixes). And some wireguard selftest updates.
>
> The rest is mostly some btrfs fixes, some core networking, and just
> random small one-offs elsewhere.
>
> Please do go test it all out - because things may look good now, but
> continued testing is the only thing that will make sure.
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 489 pass: 489 fail: 0
... and even the parisc warning is gone now.
Guenter
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-09 19:04 ` Hans de Goede
@ 2022-05-10 14:41 ` Maarten Lankhorst
2022-05-17 15:50 ` Hans de Goede
1 sibling, 0 replies; 12+ messages in thread
From: Maarten Lankhorst @ 2022-05-10 14:41 UTC (permalink / raw)
To: Hans de Goede, Linus Torvalds,
Regzbot (on behalf of Thorsten Leemhuis),
Jani Nikula, Matthew Auld, Joonas Lahtinen
Cc: LKML, Linux regressions mailing list
Op 09-05-2022 om 21:04 schreef Hans de Goede:
> Hi,
>
> On 5/9/22 19:20, Linus Torvalds wrote:
>> On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
>> Leemhuis) <regressions@leemhuis.info> wrote:
>>> Hi Linus! Here's a quick compilation of open reports about regressions in
>>> 5.18-rc that I'm currently aware of; most of the reports are quite
>>> recent and there afaics is nothing that looks particularly worrisome.
>> Well, the Intel GPU issue seems likely to cause problems for lots of people:
>>
>>> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
>>> -----------------------------------------------------------------------------------------
>>> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>
>>> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
>>> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>>>
>>> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
>> Although it looks possible that it mainly affects old chipsets (ie the
>> two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
>> idea how they compare).
>>
>> That probably means there are a lot of machines out there, but likely
>> not the kind that most kernel developers will be testing, so not a ton
>> of reports until it hits distro kernels etc.
>>
>> It looks like Maarten is already involved.
> This is being tracked here:
> https://gitlab.freedesktop.org/drm/intel/-/issues/5806
>
> I've just tested a patch from Maarten which fixes things for me,
> so hopefully we can get this resolved soon.
>
> Regards,
>
> Hans
>
Hey,
I'm still waiting on feedback on the last patch there, can you test it?
That should be the real fix most likely, waiting for binding to complete before using the vma.
~Maarten
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-09 19:04 ` Hans de Goede
2022-05-10 14:41 ` Maarten Lankhorst
@ 2022-05-17 15:50 ` Hans de Goede
2022-05-19 16:09 ` Hans de Goede
1 sibling, 1 reply; 12+ messages in thread
From: Hans de Goede @ 2022-05-17 15:50 UTC (permalink / raw)
To: Linus Torvalds, Regzbot (on behalf of Thorsten Leemhuis),
Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen
Cc: LKML, Linux regressions mailing list
Hi,
On 5/9/22 21:04, Hans de Goede wrote:
> Hi,
>
> On 5/9/22 19:20, Linus Torvalds wrote:
>> On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
>> Leemhuis) <regressions@leemhuis.info> wrote:
>>>
>>> Hi Linus! Here's a quick compilation of open reports about regressions in
>>> 5.18-rc that I'm currently aware of; most of the reports are quite
>>> recent and there afaics is nothing that looks particularly worrisome.
>>
>> Well, the Intel GPU issue seems likely to cause problems for lots of people:
>>
>>> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
>>> -----------------------------------------------------------------------------------------
>>> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>
>>> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
>>> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>>>
>>> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
>>
>> Although it looks possible that it mainly affects old chipsets (ie the
>> two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
>> idea how they compare).
>>
>> That probably means there are a lot of machines out there, but likely
>> not the kind that most kernel developers will be testing, so not a ton
>> of reports until it hits distro kernels etc.
>>
>> It looks like Maarten is already involved.
>
> This is being tracked here:
> https://gitlab.freedesktop.org/drm/intel/-/issues/5806
>
> I've just tested a patch from Maarten which fixes things for me,
> so hopefully we can get this resolved soon.
Maarten, it would be nice if we can get this fixed before 5.18
is released. What is the status of getting your:
https://patchwork.freedesktop.org/patch/485889/
patch for this merged ?
Regards,
Hans
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-17 15:50 ` Hans de Goede
@ 2022-05-19 16:09 ` Hans de Goede
2022-05-21 5:01 ` Linus Torvalds
0 siblings, 1 reply; 12+ messages in thread
From: Hans de Goede @ 2022-05-19 16:09 UTC (permalink / raw)
To: Linus Torvalds, Regzbot (on behalf of Thorsten Leemhuis),
Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen
Cc: LKML, Linux regressions mailing list
Hi,
On 5/17/22 17:50, Hans de Goede wrote:
> Hi,
>
> On 5/9/22 21:04, Hans de Goede wrote:
>> Hi,
>>
>> On 5/9/22 19:20, Linus Torvalds wrote:
>>> On Mon, May 9, 2022 at 3:47 AM Regzbot (on behalf of Thorsten
>>> Leemhuis) <regressions@leemhuis.info> wrote:
>>>>
>>>> Hi Linus! Here's a quick compilation of open reports about regressions in
>>>> 5.18-rc that I'm currently aware of; most of the reports are quite
>>>> recent and there afaics is nothing that looks particularly worrisome.
>>>
>>> Well, the Intel GPU issue seems likely to cause problems for lots of people:
>>>
>>>> [ *NEW* ] drm/i915: BYT rendering broken due to "Remove short-term pins from execbuf, v6"
>>>> -----------------------------------------------------------------------------------------
>>>> https://linux-regtracking.leemhuis.info/regzbot/regression/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>> https://lore.kernel.org/dri-devel/1366349e-f96a-3f2c-3094-f5cd1a6fa31f@redhat.com/
>>>>
>>>> By Hans de Goede; 0 days ago; 2 activities, latest 0 days ago.
>>>> Introduced in b5cfe6f7a6e1 (v5.18-rc1)
>>>>
>>>> Recent activities from: Tvrtko Ursulin (1), Hans de Goede (1)
>>>
>>> Although it looks possible that it mainly affects old chipsets (ie the
>>> two reports are for a Bay Trail chip and a Core 2 Duo chip - I have no
>>> idea how they compare).
>>>
>>> That probably means there are a lot of machines out there, but likely
>>> not the kind that most kernel developers will be testing, so not a ton
>>> of reports until it hits distro kernels etc.
>>>
>>> It looks like Maarten is already involved.
>>
>> This is being tracked here:
>> https://gitlab.freedesktop.org/drm/intel/-/issues/5806
>>
>> I've just tested a patch from Maarten which fixes things for me,
>> so hopefully we can get this resolved soon.
>
> Maarten, it would be nice if we can get this fixed before 5.18
> is released. What is the status of getting your:
>
> https://patchwork.freedesktop.org/patch/485889/
A quick status update, this is fixed by:
https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=7b1d6924f27ba24b9e47abb9bd53d0bbc430a835
Which was just pushed to:
https://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-fixes
Note this is not part of any pending drm-fixes* pull-reqs yet though.
Regards,
Hans
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-19 16:09 ` Hans de Goede
@ 2022-05-21 5:01 ` Linus Torvalds
2022-05-21 11:30 ` Thorsten Leemhuis
0 siblings, 1 reply; 12+ messages in thread
From: Linus Torvalds @ 2022-05-21 5:01 UTC (permalink / raw)
To: Hans de Goede
Cc: Regzbot (on behalf of Thorsten Leemhuis),
Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen,
LKML, Linux regressions mailing list
On Thu, May 19, 2022 at 6:10 AM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Note this is not part of any pending drm-fixes* pull-reqs yet though.
It has now hit my tree as part of Dave's drm pull today.
Will go out after the usual basic build test.
Linus
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6)
2022-05-21 5:01 ` Linus Torvalds
@ 2022-05-21 11:30 ` Thorsten Leemhuis
0 siblings, 0 replies; 12+ messages in thread
From: Thorsten Leemhuis @ 2022-05-21 11:30 UTC (permalink / raw)
To: Linus Torvalds, Hans de Goede
Cc: Maarten Lankhorst, Jani Nikula, Matthew Auld, Joonas Lahtinen,
LKML, Linux regressions mailing list
On 21.05.22 07:01, Linus Torvalds wrote:
> On Thu, May 19, 2022 at 6:10 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Note this is not part of any pending drm-fixes* pull-reqs yet though.
>
> It has now hit my tree as part of Dave's drm pull today.
Great, just like Hans I have been watching the progress of that patch
closely. A fix for a regression on the Raspi CM4 also landed in the past
24 hours.
I assume you'll also get the patch "objtool: Fix objtool regression on
x32 systems"
(https://lore.kernel.org/all/165304401319.4207.18392602354110557584.tip-bot2@tip-bot2/
) today or tomorrow.
That leaves the following post-5.17 regressions on my list where no fix
is in sight yet:
* Laptop with Ryzen 4600H fails to resume video
https://lore.kernel.org/stable/2584945.lGaqSPkdTl@geek500.localdomain/
(doesn't look like it first, but this apparently is a post-5.17
regression, as the commit causing it was backported; note, the Laptop
has some other problems with suspend that make the first suspend fail;
Mario is working hard with the reporter to find a fix)
* dpaa2: TSO offload on lx2160a causes fatal exception in interrupt
https://bugzilla.kernel.org/show_bug.cgi?id=215886
Debugging is ongoing, there is a patch now, but it's not clear yet if it
helps.
* the netperf.Throughput_Mbps -18.0% regression that made it into mainline:
https://lore.kernel.org/lkml/20220420013526.GB14333@xsang-OptiPlex-9020/
Didn't follow that one closely, as you were active in the discussion
yourself.
HTH, Ciao, Thorsten
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2022-05-21 11:33 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-08 21:09 Linux 5.18-rc6 Linus Torvalds
2022-05-09 8:40 ` Build regressions/improvements in v5.18-rc6 Geert Uytterhoeven
2022-05-09 9:13 ` Build regressions/improvements in v5.18-rc6B Geert Uytterhoeven
2022-05-09 10:47 ` Linux regressions report for mainline [2022-05-09] (was: Linux 5.18-rc6) Regzbot (on behalf of Thorsten Leemhuis)
2022-05-09 17:20 ` Linus Torvalds
2022-05-09 19:04 ` Hans de Goede
2022-05-10 14:41 ` Maarten Lankhorst
2022-05-17 15:50 ` Hans de Goede
2022-05-19 16:09 ` Hans de Goede
2022-05-21 5:01 ` Linus Torvalds
2022-05-21 11:30 ` Thorsten Leemhuis
2022-05-09 23:06 ` Linux 5.18-rc6 Guenter Roeck
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).