* Linux 5.19-rc1
@ 2022-06-06 0:42 Linus Torvalds
2022-06-06 8:22 ` Build regressions/improvements in v5.19-rc1 Geert Uytterhoeven
` (3 more replies)
0 siblings, 4 replies; 6+ messages in thread
From: Linus Torvalds @ 2022-06-06 0:42 UTC (permalink / raw)
To: Linux Kernel Mailing List
So the last two weeks were _fairly_ normal, although I will gripe and
moan a bit about how many late pull requests I got. The second week
started out very calm, but that was sadly only because a _lot_ of
people left their final pull request pretty late. Not very pleasant at
all.
But what does make me pretty pleased is that pretty much all of the
pull requests were signed tags. I still don't technically _require_
signatures for pulls from kernel.org, but I've been (not very subtly)
encouraging people to use them, and we're getting there. It's just
good hygiene.
And to cap off the good news, this is the first merge window when
Andrew participated all through git, and the first time in basically
Linux history when I didn't have a single patch-bomb to apply (I still
do individual random patches, and expect to always do them, but no
more "big series of raw patches").
So on the whole it's all very good.
Anyway, apart from those three "process" issues, things look perfectly
normal. Judging by the merge window, this release is going to be on
the bigger side, but certainly not breaking any records, and nothing
looks particularly odd or crazy. The diffstat is skewed by yet another
drop of generated AMD GPU register descriptor headers, but I guess
even that is "normal" by now. Certainly not a new thing. And if you
ignore that drivers/gpu/drm/amd/include/ subdirectory, the stats look
like they tend to do: roughly 60% drivers, with the rest being
architecture updates, tooling, documentation and some relatively minor
core kernel updates (filesystems, mm, networking etc. Oh, and the core
module handling got split up into more manageable pieces rather than
one big file).
One thing of note is how the long-time ARM generic kernel work (aka
"multiplatform") is pretty much done after 10+ years. Congrats to
everybody involved. The StrongARM platforms remain with their separate
kernels, and are expected to stay so, but compared to where things
were a decade ago, this is a pretty big step.
So hey, let's start calming things down and testing this all.
Linus
---
Luis Chamberlain (1):
modules updates
Al Viro (4):
file descriptor updates
mount handling updates
vfs pathname updates
file descriptor fix
Alex Williamson (1):
vfio updates
Alexandre Belloni (2):
i3c updates
RTC updates
Andreas Gruenbacher (1):
gfs2 updates
Andrew Morton (6):
MM updates
misc updates
hotfixes
more MM updates
delay-accounting update
mm hotfixes
Anna Schumaker (1):
NFS client updates
Ard Biesheuvel (2):
EFI updates
more EFI updates
Arnaldo Carvalho de Melo (3):
perf tool updates
more perf tools updates
more perf tools updates
Arnd Bergmann (11):
32-bit ARM SoC updates
ARM DT updates
ARM driver updates
ARM defconfig updates
ARMv4T/v5 multiplatform support
asm-generic updates
more ARM multiplatform updates
more ARM SoC updates
asm-generic fixes
initial Loongarch architecture code
yet more ARM multiplatform updates
Bartosz Golaszewski (2):
gpio updates
gpio fixes
Bjorn Andersson (2):
remoteproc updates
rpmsg updates
Bjorn Helgaas (2):
pci updates
pci fixes
Borislav Petkov (18):
EDAC updates
AMD SEV-SNP support
x86 RAS updates
Intel TDX support
x86 CPU feature updates
x86 asm updates
x86 build updates
x86 cleanups
core x86 updates
x86 fpu updates
x86 mm fixlet
x86 platform updates
x86 kdump fixlet
x86 APIC updates
x86 splitlock updates
misc x86 updates
x86 microcode loader update
x86 vdso update
Casey Schaufler (1):
smack update
Catalin Marinas (2):
arm64 updates
arm64 fixes
Christian Brauner (1):
fs idmapping updates
Christoph Hellwig (1):
dma-mapping updates
Chuck Lever (1):
nfsd updates
Corey Minyard (1):
IPMI update
Damien Le Moal (3):
ata updates
zonefs updates
zonefs fix
Dan Williams (2):
libnvdimm and DAX updates
cxl updates
Darrick Wong (1):
iomap updates
Dave Airlie (2):
drm updates
more drm updates
Dave Chinner (2):
xfs updates
more xfs updates
Dave Hansen (1):
x86 SGX updates
David Kleikamp (1):
jfs updates
David Sterba (1):
btrfs updates
David Teigland (1):
dlm updates
Dmitry Torokhov (1):
input updates
Dominik Brodowski (1):
pcmcia updates
Eric Biederman (3):
ipc sysctl namespace updates
kthread updates
ptrace_stop cleanups
Eric Biggers (2):
fscrypt updates
fsverity updates
Gao Xiang (2):
erofs (and fscache) updates
more erofs updates
Geert Uytterhoeven (1):
m68k updates
Greg KH (6):
SPDX updates
staging driver updates
tty and serial driver updates
USB / Thunderbolt updates
char / misc / other smaller driver subsystem updates
driver core updates
Greg Ungerer (1):
m68knommu updates
Guenter Roeck (1):
hwmon updates
Guo Ren (1):
arch/csky updates
Gustavo Silva (3):
Wstringop-overflow fixes
misc hardening updates
checkpatch update
Hans de Goede (1):
x86 platform driver updates
Heiko Carstens (2):
s390 updates
more s390 updates
Helge Deller (3):
parisc architecture updates
fbdev fixes and updates
more parisc architecture updates
Herbert Xu (1):
crypto updates
Ilya Dryomov (1):
ceph updates
Ingo Molnar (4):
locking updates
objtool updates
perf events updates
scheduler updates
Jaegeuk Kim (1):
f2fs updates
Jakub Kicinski (2):
networking updates
networking fixes
James Bottomley (2):
SCSI updates
more SCSI updates
Jan Kara (2):
writeback and ext2 cleanups
fsnotify updates
Jarkko Sakkinen (1):
tpm updates
Jason Donenfeld (1):
random number generator updates
Jason Gunthorpe (1):
rdma updates
Jassi Brar (1):
mailbox updates
Jens Axboe (13):
io_uring updates
io_uring xattr support
io_uring socket() support
io_uring 'more data in socket' support
io_uring NVMe command passthrough
writeback fix
cdrom updates
block updates
block driver updates
more io_uring updates
block fixes
block request execute cleanups
more block driver updates
Jiri Kosina (1):
HID updates
Joerg Roedel (1):
iommu updates
Jonathan Corbet (2):
documentation updates
documentation fixes
Juergen Gross (2):
xen updates
more xen updates
Kees Cook (4):
kernel hardening updates
seccomp updates
execve updates
kernel hardening fix
Konstantin Komarov (1):
ntfs3 updates
Lee Jones (1):
MFD updates
Linus Walleij (1):
pin control updates
Luis Chamberlain (1):
sysctl updates
Mark Brown (5):
regmap updates
regulator updates
spi updates
spi fixes
regulator fix
Masahiro Yamada (2):
Kbuild updates
more Kbuild updates
Matthew Wilcox (1):
page cache updates
Mauro Carvalho Chehab (1):
media updates
Max Filippov (1):
xtensa architecture updates
Michael Ellerman (1):
powerpc updates
Michael Tsirkin (1):
virtio updates
Michal Simek (1):
microblaze updates
Mickaël Salaün (1):
Landlock updates
Miguel Ojeda (1):
clang-format updates
Mike Rapoport (1):
memblock test suite updates
Mike Snitzer (2):
device mapper updates
device mapper fixes
Miklos Szeredi (1):
overlayfs updates
Mimi Zohar (1):
IMA updates
Miquel Raynal (1):
mtd updates
Namjae Jeon (1):
exfat updates
Palmer Dabbelt (2):
RISC-V updates
more RISC-V updates
Paolo Bonzini (1):
kvm updates
Paul McKenney (3):
nolibc library updates
LKMM update
RCU update
Paul Moore (1):
selinux updates
Pavel Machek (1):
LED updates
Petr Mladek (3):
printk updates
printk fixup
livepatching cleanup
Rafael Wysocki (7):
ACPI updates
power management updates
thermal control updates
device properties framework updates
more ACPI updates
additional thermal control update
more power management updates
Richard Weinberger (2):
UML updates
JFFS2, UBI and UBIFS updates
Rob Herring (2):
devicetree updates
devicetree fixes
Russell King (1):
ARM updates
Sebastian Reichel (1):
power supply and reset updates
Shuah Khan (2):
Kselftest updates
KUnit updates
Stafford Horne (1):
OpenRISC updates
Stephen Boyd (1):
clk updates
Steve French (3):
cifs client updates
ksmbd server updates
cifs client fixes
Steven Rostedt (2):
tracing updates
tracing tool updates
Takashi Iwai (2):
sound updates
sound fixes
Ted Ts'o (1):
ext4 updates
Tejun Heo (2):
cgroup updates
workqueue update
Thierry Reding (2):
pwm updates
hardware timestamping subsystem
Thomas Bogendoerfer (1):
MIPS updates
Thomas Gleixner (16):
irqpoll update
debugobjects fixlet
CPU hotplug updates
interrupt handling updates
timer and timekeeping updates
x86 PCI irq routing updates
objtool fixes
perf fixlet
perf fixes
scheduler fix
clockevent/clocksource updates
x86 boot update
x86 cleanups
x86 microcode updates
x86 mm cleanup
x86 SGX fix
Tzung-Bi Shih (1):
chrome platform updates
Ulf Hansson (1):
MMC updates
Vineet Gupta (1):
ARC updates
Vinod Koul (1):
dmaengine updates
Vlastimil Babka (1):
slab updates
Wei Liu (1):
hyperv updates
Wim Van Sebroeck (1):
watchdog updates
Wolfram Sang (1):
i2c updates
Yury Norov (1):
bitmap updates
^ permalink raw reply [flat|nested] 6+ messages in thread
* Build regressions/improvements in v5.19-rc1
2022-06-06 0:42 Linux 5.19-rc1 Linus Torvalds
@ 2022-06-06 8:22 ` Geert Uytterhoeven
2022-06-06 9:08 ` Geert Uytterhoeven
2022-06-06 8:36 ` Linux 5.19-rc1 Sudip Mukherjee
` (2 subsequent siblings)
3 siblings, 1 reply; 6+ messages in thread
From: Geert Uytterhoeven @ 2022-06-06 8:22 UTC (permalink / raw)
To: linux-kernel
Below is the list of build error/warning regressions/improvements in
v5.19-rc1[1] compared to v5.18[2].
Summarized:
- build errors: +9/-10
- build warnings: +3/-24
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/f2906aa863381afb0015a9eb7fefad885d4e5a56/ (all 135 configs)
[2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4b0986a3613c92f4ec1bdc7f60ec66fea135991f/ (131 out of 135 configs)
*** ERRORS ***
9 error regressions:
+ /kisskb/src/arch/um/include/asm/page.h: error: too few arguments to function 'to_phys': => 105:20
+ /kisskb/src/arch/xtensa/kernel/entry.S: Error: unknown pseudo-op: `.bss': => 2176
+ /kisskb/src/drivers/nvdimm/pmem.c: error: conflicting types for 'to_phys': => 48:20
+ /kisskb/src/drivers/nvdimm/pmem.c: error: control reaches end of non-void function [-Werror=return-type]: => 324:1
+ /kisskb/src/drivers/tty/serial/sh-sci.c: error: unused variable 'sport' [-Werror=unused-variable]: => 2655:26
+ /kisskb/src/include/linux/fortify-string.h: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]: => 344:25
+ /kisskb/src/include/ufs/ufshci.h: error: initializer element is not constant: => 245:36
+ error: relocation truncated to fit: R_SPARC_WDISP22 against `.init.text': => (.head.text+0x5100), (.head.text+0x5040)
+ error: relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o: => (.init.text+0xa4)
10 error improvements:
- /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 =>
- error: arch/sparc/kernel/head_32.o: relocation truncated to fit: R_SPARC_WDISP22 against `.init.text': (.head.text+0x5100), (.head.text+0x5040) =>
- error: arch/sparc/kernel/head_32.o: relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o: (.init.text+0xa4) =>
*** WARNINGS ***
3 warning regressions:
+ .config: warning: override: ARCH_RV32I changes choice state: => 3860
+ arch/m68k/configs/multi_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 61
+ arch/m68k/configs/sun3_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 37
24 warning improvements:
- .config: warning: override: reassigning to symbol GCC_PLUGIN_RANDSTRUCT: 12475, 12253 =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14410): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14428): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14440): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14458): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14470): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14488): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x144a0): Section mismatch in reference from the variable qed_mfw_legacy_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x144f0): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14508): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14520): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14538): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14550): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14568): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14580): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o(.data+0x14598): Section mismatch in reference from the variable qed_mfw_ext_maps to the variable .init.rodata:qed_mfw_legacy_bb_100g: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4790): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47a8): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47c0): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47d8): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x47f0): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4808): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o(.data+0x4820): Section mismatch in reference from the variable qede_forced_speed_maps to the variable .init.rodata:qede_forced_speed_100000: 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 =>
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] 6+ messages in thread
* Re: Linux 5.19-rc1
2022-06-06 0:42 Linux 5.19-rc1 Linus Torvalds
2022-06-06 8:22 ` Build regressions/improvements in v5.19-rc1 Geert Uytterhoeven
@ 2022-06-06 8:36 ` Sudip Mukherjee
2022-06-06 11:51 ` Ammar Faizi
2022-06-06 15:39 ` Guenter Roeck
3 siblings, 0 replies; 6+ messages in thread
From: Sudip Mukherjee @ 2022-06-06 8:36 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Jun 05, 2022 at 05:42:33PM -0700, Linus Torvalds wrote:
> So the last two weeks were _fairly_ normal, although I will gripe and
> moan a bit about how many late pull requests I got. The second week
> started out very calm, but that was sadly only because a _lot_ of
> people left their final pull request pretty late. Not very pleasant at
> all.
>
<snip>
>
> So hey, let's start calming things down and testing this all.
Build fails with:
arm allmodconfig
mips loongson2k_defconfig
Both have been reported earlier:
https://lore.kernel.org/lkml/Yps1Jw6PJdLBya1W@debian/
https://lore.kernel.org/lkml/YpncSXSTTyKGprLi@debian/
--
Regards
Sudip
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Build regressions/improvements in v5.19-rc1
2022-06-06 8:22 ` Build regressions/improvements in v5.19-rc1 Geert Uytterhoeven
@ 2022-06-06 9:08 ` Geert Uytterhoeven
0 siblings, 0 replies; 6+ messages in thread
From: Geert Uytterhoeven @ 2022-06-06 9:08 UTC (permalink / raw)
To: linux-kernel
Cc: Kees Cook, nvdimm, linux-um, linux-xtensa, linux-sh,
linuxppc-dev, linux-scsi, sparclinux
On Mon, 6 Jun 2022, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.19-rc1[1] compared to v5.18[2].
>
> Summarized:
> - build errors: +9/-10
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/f2906aa863381afb0015a9eb7fefad885d4e5a56/ (all 135 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4b0986a3613c92f4ec1bdc7f60ec66fea135991f/ (131 out of 135 configs)
> 9 error regressions:
> + /kisskb/src/arch/um/include/asm/page.h: error: too few arguments to function 'to_phys': => 105:20
> + /kisskb/src/drivers/nvdimm/pmem.c: error: conflicting types for 'to_phys': => 48:20
> + /kisskb/src/drivers/nvdimm/pmem.c: error: control reaches end of non-void function [-Werror=return-type]: => 324:1
um-x86_64/um-allyesconfig
> + /kisskb/src/arch/xtensa/kernel/entry.S: Error: unknown pseudo-op: `.bss': => 2176
xtensa-gcc11/xtensa-allmodconfig
> + /kisskb/src/drivers/tty/serial/sh-sci.c: error: unused variable 'sport' [-Werror=unused-variable]: => 2655:26
sh4-gcc11/se7619_defconfig
sh4-gcc11/sh-allmodconfig
Fix available
https://lore.kernel.org/all/4ed0a7a0d3fa912a5b44c451884818f2c138ef42.1644914600.git.geert+renesas@glider.be
> + /kisskb/src/include/linux/fortify-string.h: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]: => 344:25
powerpc-gcc11/ppc64_book3e_allmodconfig
> + /kisskb/src/include/ufs/ufshci.h: error: initializer element is not constant: => 245:36
mipsel-gcc5/mips-allmodconfig
powerpc-gcc5/powerpc-allmodconfig
FTR, include/ufs/ufshci.h lacks a MAINTAINERS entry.
> + error: relocation truncated to fit: R_SPARC_WDISP22 against `.init.text': => (.head.text+0x5100), (.head.text+0x5040)
> + error: relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o: => (.init.text+0xa4)
sparc64-gcc5/sparc-allmodconfig
> 3 warning regressions:
> + arch/m68k/configs/multi_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 61
> + arch/m68k/configs/sun3_defconfig: warning: symbol value 'm' invalid for ZPOOL: => 37
Will be fixed by the m68k defconfig update for v5.20.
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] 6+ messages in thread
* Re: Linux 5.19-rc1
2022-06-06 0:42 Linux 5.19-rc1 Linus Torvalds
2022-06-06 8:22 ` Build regressions/improvements in v5.19-rc1 Geert Uytterhoeven
2022-06-06 8:36 ` Linux 5.19-rc1 Sudip Mukherjee
@ 2022-06-06 11:51 ` Ammar Faizi
2022-06-06 15:39 ` Guenter Roeck
3 siblings, 0 replies; 6+ messages in thread
From: Ammar Faizi @ 2022-06-06 11:51 UTC (permalink / raw)
To: Linus Torvalds, Linux Kernel Mailing List
On 6/6/22 7:42 AM, Linus Torvalds wrote:
> So hey, let's start calming things down and testing this all.
Doesn't compile with clang 15, the fix is there:
https://lore.kernel.org/lkml/20220523150521.2947108-1-nathan@kernel.org/
Error:
```
ammarfaizi2@integral2:~/work/linux.work$ git log -n 1
commit f2906aa863381afb0015a9eb7fefad885d4e5a56 (HEAD -> master, tag: v5.19-rc1, @torvalds/linux/master)
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Jun 5 17:18:54 2022 -0700
Linux 5.19-rc1
ammarfaizi2@integral2:~/work/linux.work$
ammarfaizi2@integral2:~/work/linux.work$ taskset -c 0-7 make -j8 && taskset -c 0-7 make modules -j8
DESCEND objtool
CALL scripts/atomic/check-atomics.sh
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC [M] drivers/misc/cardreader/rts5261.o
CC [M] drivers/misc/altera-stapl/altera-lpt.o
CC [M] drivers/misc/altera-stapl/altera-jtag.o
CC [M] drivers/misc/altera-stapl/altera-comp.o
drivers/misc/cardreader/rts5261.c:406:13: error: variable 'setting_reg2' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
} else if (efuse_valid == 0) {
^~~~~~~~~~~~~~~~
drivers/misc/cardreader/rts5261.c:412:30: note: uninitialized use occurs here
pci_read_config_dword(pdev, setting_reg2, &lval2);
^~~~~~~~~~~~
drivers/misc/cardreader/rts5261.c:406:9: note: remove the 'if' if its condition is always true
} else if (efuse_valid == 0) {
^~~~~~~~~~~~~~~~~~~~~~
drivers/misc/cardreader/rts5261.c:364:32: note: initialize the variable 'setting_reg2' to silence this warning
u16 setting_reg1, setting_reg2;
^
= 0
1 error generated.
make[3]: *** [scripts/Makefile.build:249: drivers/misc/cardreader/rts5261.o] Error 1
make[2]: *** [scripts/Makefile.build:466: drivers/misc/cardreader] Error 2
make[2]: *** Waiting for unfinished jobs....
```
--
Ammar Faizi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Linux 5.19-rc1
2022-06-06 0:42 Linux 5.19-rc1 Linus Torvalds
` (2 preceding siblings ...)
2022-06-06 11:51 ` Ammar Faizi
@ 2022-06-06 15:39 ` Guenter Roeck
3 siblings, 0 replies; 6+ messages in thread
From: Guenter Roeck @ 2022-06-06 15:39 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Jun 05, 2022 at 05:42:33PM -0700, Linus Torvalds wrote:
> So the last two weeks were _fairly_ normal, although I will gripe and
> moan a bit about how many late pull requests I got. The second week
> started out very calm, but that was sadly only because a _lot_ of
> people left their final pull request pretty late. Not very pleasant at
> all.
>
. ... ]
>
> So hey, let's start calming things down and testing this all.
>
Build results:
total: 147 pass: 145 fail: 2
Failed builds:
arm:allmodconfig
powerpc:allmodconfig
Qemu test results:
total: 489 pass: 489 fail: 0
arm:allmodconfig:
Error log:
ERROR: modpost: missing MODULE_LICENSE() in drivers/watchdog/gxp-wdt.o
Guess that one is on me. Fix is at
https://patchwork.kernel.org/project/linux-watchdog/patch/20220603131419.2948578-1-linux@roeck-us.net/
powerpc:allmodconfig:
Error: External symbol 'memset' referenced from prom_init.c
make[3]: [arch/powerpc/kernel/Makefile:202: arch/powerpc/kernel/prom_init_check] Error 1 (ignored)
powerpc64-linux-ld: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/display_mode_lib.o uses hard float,
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.o uses soft float
powerpc64-linux-ld: failed to merge target specific data of
file drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.o
powerpc64-linux-ld: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/display_mode_lib.o uses hard float,
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn315/dcn315_resource.o uses soft float
powerpc64-linux-ld: failed to merge target specific data of file
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn315/dcn315_resource.o
powerpc64-linux-ld: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/display_mode_lib.o uses hard float,
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn316/dcn316_resource.o uses soft float
powerpc64-linux-ld: failed to merge target specific data of file
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn316/dcn316_resource.o
Bisects to commit 41b7a347bf14 ("powerpc: Book3S 64-bit outline-only KASAN support")
which seems to change dependencies.
There is also a runtime warning, seen with various qemu arm boot tests.
WARNING: CPU: 0 PID: 1 at lib/refcount.c:28 of_platform_bus_create+0x33c/0x3dc
refcount_t: underflow; use-after-free.
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.19.0-rc1 #1
Hardware name: ARM-Versatile (Device Tree Support)
unwind_backtrace from show_stack+0x10/0x14
show_stack from dump_stack_lvl+0x38/0x5c
dump_stack_lvl from __warn+0xc8/0x1d4
__warn from warn_slowpath_fmt+0x90/0xc8
warn_slowpath_fmt from of_platform_bus_create+0x33c/0x3dc
of_platform_bus_create from of_platform_bus_create+0x1ec/0x3dc
of_platform_bus_create from of_platform_populate+0x68/0xd8
of_platform_populate from customize_machine+0x1c/0x30
customize_machine from do_one_initcall+0x8c/0x2fc
do_one_initcall from kernel_init_freeable+0x190/0x220
kernel_init_freeable from kernel_init+0x10/0x108
kernel_init from ret_from_fork+0x14/0x3c
This is fixed with commit d2ca1fd2bc70 ("ARM: 9207/1: amba: fix refcount
underflow if amba_device_add() fails") in linux-next.
Guenter
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-06-06 15:39 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-06 0:42 Linux 5.19-rc1 Linus Torvalds
2022-06-06 8:22 ` Build regressions/improvements in v5.19-rc1 Geert Uytterhoeven
2022-06-06 9:08 ` Geert Uytterhoeven
2022-06-06 8:36 ` Linux 5.19-rc1 Sudip Mukherjee
2022-06-06 11:51 ` Ammar Faizi
2022-06-06 15:39 ` 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).