Right on schedule two weeks after the 6.4 release, here we are and the
merge window is closed.
Nothing hugely unusual stands out - we had some VM annoyance, but the
fixes for that don't even show in the diffstat, which is (as usual)
dominated by drivers, with tooling and architecture updates a distant
second and third.
And even if you filter out all the drivers, tooling and architecture
changes out, the diff is still dominated by header file updates (much
of it due to some re-organization around our atomic ops) and
documentation updates.
At only after you filter out _that_ do you start seeing the core
changes - various filesystem updates (btrfs, ovlfs, f2fs, ext4), core
networking code, and then core kernel and mm updates.
Anyway, none of it looks hugely unusual. The biggest single mention
probably goes to what wasn't merged, with the bcachefs pull request
resulting in a long thread (we didn't hit a hundred emails yet, but
it's not far away).
Let's calm this party down. I have this slight suspicion that this may
be one of those releases that may drag out, not because there are any
particular issues I expect problems with, but simply due to lot of
Europe going on vacation for the month of August. But who knows...
We'll see how things develop.
And below is obviously just the usual shortlog of my merges, since at
around 12k non-merge commits, the full shortlog is much too big (even
if this was a fairly small merge window).
Linus
---
Adrian Glaubitz (1):
sh updates
Alex Williamson (1):
VFIO updates
Alexander Gordeev (3):
s390 updates (x2)
more s390 updates
Alexandre Belloni (2):
i3c updates
RTC updates
Amir Goldstein (2):
overlayfs update
more overlayfs updates
Andreas Gruenbacher (1):
gfs2 updates
Andrew Morton (3):
mm updates
non-mm updates
hotfixes
Ard Biesheuvel (1):
EFI updates
Arnd Bergmann (7):
ARM SoC devicetree updates
new ARM SoC support
ARM SoC driver updates
ARM SoC defconfig updates
ARM SoC updates
SoC fixes
asm-generic updates
Bartosz Golaszewski (1):
gpio updates
Bjorn Andersson (2):
hwspinlock update
remoteproc updates
Bjorn Helgaas (1):
pci updates
Borislav Petkov (14):
EDAC updates
RAS updates
x86 instruction alternatives updates
x86 build update
x86 resource control updates
x86 confidential computing update
x86 cpu updates
x86 microcode loader updates
misc x86 updates
x86 mtrr updates
x86 SEV updates
SGX update
x86 fpu fix
irq update
Casey Schaufler (1):
smack updates
Catalin Marinas (2):
arm64 updates
arm64 fix
Christian Brauner (7):
ntfs updates
misc vfs updates
vfs rename locking updates
vfs file handling updates
vfs mount updates
vfs fix
vfs fixes
Christoph Hellwig (2):
dma-mapping updates
dma-mapping fixes
Chuck Lever (2):
nfsd updates
nfsd fix
Damien Le Moal (2):
zonefs updates
ata updates
Dan Williams (1):
CXL updates
Daniel Thompson (1):
kgdb updates
Darrick Wong (4):
xfs updates
iomap updates
more xfs updates
xfs fix
Dave Airlie (2):
drm updates
drm fixes
Dave Hansen (4):
x86 irq updates
x86 platform updates
x86 tdx updates
x86 cleanups
David Kleikamp (1):
jfs updates
David Sterba (1):
btrfs updates
David Teigland (1):
dlm updates
David Woodhouse (1):
mm fix
Dinh Nguyen (1):
nios2 updates
Dmitry Torokhov (1):
input updates
Eric Biggers (2):
fscrypt update
fsverity updates
Gao Xiang (1):
erofs updates
Geert Uytterhoeven (1):
m68k updates
Greg KH (5):
Char/Misc updates
driver core updates
staging driver updates
tty/serial driver updates
USB / Thunderbolt driver updates
Guenter Roeck (1):
hwmon updates
Guo Ren (1):
arch/csky update
Gustavo Silva (1):
flexible-array update
Hans de Goede (1):
x86 platform driver updates
Helge Deller (3):
fbdev updates
parisc updates
more parisc architecture updates
Herbert Xu (1):
crypto updates
Huacai Chen (1):
LoongArch updates
Ilya Dryomov (1):
ceph updates
Ingo Molar (1):
objtool updates
Ingo Molnar (4):
scheduler updates
locking updates
perf events updates
x86 mm updates
Jaegeuk Kim (1):
f2fs updates
Jakub Kicinski (2):
networking changes
networking fixes
James Bottomley (2):
SCSI updates
more SCSI updates
Jan Kara (3):
fsnotify updates
misc filesystem updates
fsnotify fix
Jason Gunthorpe (2):
iommufd updates
rdma updates
Jassi Brar (1):
mailbox updates
Jens Axboe (5):
splice updates
io_uring updates
block updates
io_uring fixes
more block updates
Jiri Kosina (1):
HID updates
Joerg Roedel (1):
iommu updates
John Johansen (1):
apparmor updates
Jon Mason (1):
NTB updates
Jonathan Corbet (4):
documentation updates
arm documentation move
arm64 documentation move
mode documentation updates
Juergen Gross (1):
xen updates
Kees Cook (4):
execve updates
pstore updates
hardening updates
hardening fixes
Konstantin Komarov (1):
ntfs3 updates
Lee Jones (3):
MFD updates
LED updates
backlight updates
Linus Walleij (1):
pin control updates
Luis Chamberlain (4):
module updates
sysctl updates
sysctl fix
another sysctl fix
Mark Brown (5):
regmap updates
regulator updates
spi updates
regulator fix
spi fixes
Masahiro Yamada (1):
Kbuild updates
Masami Hiramatsu (1):
probes updates
Mauro Carvalho Chehab (1):
media updates
Max Filippov (1):
xtensa updates
Michael Ellerman (2):
powerpc updates
powerpc fixes
Michael Tsirkin (1):
virtio updates
Mickaël Salaün (1):
landlock updates
Miguel Ojeda (2):
rust updates
auxdisplay update
Mike Rapoport (1):
memblock updates
Mike Snitzer (1):
device mapper updates
Mimi Zohar (1):
integrity subsystem updates
Namhyung Kim (2):
perf tools updates
more perf tools updates
Palmer Dabbelt (2):
RISC-V updates
more RISC-V updates
Paolo Bonzini (1):
kvm updates
Paul McKenney (2):
RCU updates
nolibc updates
Paul Moore (3):
audit update
selinux updates
lsm updates
Peter Zijlstra (1):
scope-based resource management infrastructure
Petr Mladek (1):
livepatching update
Rafael Wysocki (6):
ACPI updates
power management updates
thermal control updates
ACPI fix
more power management updates
more ACPI updates
Rob Herring (2):
devicetree updates
more devicetree updates
Russell King (1):
ARM updates
Sebastian Reichel (2):
power supply and reset updates
HSI updates
Shuah Khan (2):
KUnit updates
kselftest updates
Stephen Boyd (2):
clk updates
more clk updates
Steve French (3):
ksmbd server updates
smb client updates
more smb client updates
Steven Rostedt (4):
tracing fix
tracing updates
tracing tooling updates
tracing fixes
Takashi Iwai (2):
sound updates
sound fixes
Takashi Sakamoto (1):
firewire updates
Ted Ts'o (1):
ext4 updates
Tejun Heo (3):
workqueue updates
ordered workqueue creation updates
cgroup updates
Thierry Reding (1):
pwm updates
Thomas Bogendoerfer (2):
MIPS updates
MIPS fixes
Thomas Gleixner (8):
debugobjects update
irq updates
x86 boot updates
SMP updates
timer updates
x86 core updates
x86 fix (x2)
Trond Myklebust (1):
NFS client updates
Tzung-Bi Shih (1):
chrome platform updates
Ulf Hansson (2):
MMC updates
mmc fix
Vinod Koul (3):
soundwire updates
phy updates
dmaengine updates
Vishal Verma (1):
nvdimm and DAX updates
Vlastimil Babka (1):
slab updates
Wim Van Sebroeck (1):
watchdog updates
Wolfram Sang (2):
i2c updates
more i2c updates
Yury Norov (1):
bitmap updates
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20230627 was the first linux-next after
the merge window opened.)
Commits in v6.5-rc1 (relative to v6.4): 11730
Commits in next-20230627: 11468
Commits with the same SHA1: 11053
Commits with the same patch_id: 144 (1)
Commits with the same subject line: 15 (1)
(1) not counting those in the lines above.
So commits in -rc1 that were in next-20230627: 11212 95%
Some breakdown of the list of extra commits (relative to next-20230627)
in -rc1:
Top ten first word of commit summary:
37 drm
29 parisc
28 perf
25 s390
25 net
20 xfs
19 mm
17 dt-bindings
15 riscv
15 alsa
Top ten authors:
30 [email protected]
25 [email protected]
14 [email protected]
11 [email protected]
9 [email protected]
9 [email protected]
8 [email protected]
8 [email protected]
8 [email protected]
7 [email protected]
Top ten commiters:
44 [email protected]
34 [email protected]
31 [email protected]
30 [email protected]
27 [email protected]
25 [email protected]
23 [email protected]
22 [email protected]
22 [email protected]
16 [email protected]
There are also 256 commits in next-20230627 that didn't make it into
v6.5-rc1.
Top ten first word of commit summary:
30 x86
25 arm64
22 dt-bindings
18 drm
17 bluetooth
14 mm
12 soc
12 nvmem
10 media
9 virtio_ring
Top ten authors:
38 [email protected]
10 [email protected]
10 [email protected]
9 [email protected]
7 [email protected]
7 [email protected]
6 [email protected]
5 [email protected]
5 [email protected]
4 [email protected]
Top ten commiters:
42 [email protected]
25 [email protected]
19 [email protected]
17 [email protected]
14 [email protected]
12 [email protected]
9 [email protected]
8 [email protected]
7 [email protected]
7 [email protected]
--
Cheers,
Stephen Rothwell
Below is the list of build error/warning regressions/improvements in
v6.5-rc1[1] compared to v6.4[2].
Summarized:
- build errors: +3/-4
- build warnings: +36/-18
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/06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5/ (all 162 configs)
[2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (160 out of 162 configs)
*** ERRORS ***
3 error regressions:
+ /kisskb/src/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c: error: the frame size of 1392 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]: => 1036:1
+ error: modpost: "__xchg_called_with_bad_pointer" [lib/atomic64_test.ko] undefined!: => N/A
+ {standard input}: Error: unknown pseudo-op: `.glo': => 1097
4 error improvements:
- /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn31/display_mode_vba_31.c: error: the frame size of 2208 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]: 7179:1 =>
- /kisskb/src/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn314/display_mode_vba_314.c: error: the frame size of 2208 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]: 7224:1 =>
- /kisskb/src/drivers/net/wireless/cisco/airo.c: error: 'status_rid.currentXmitRate' is used uninitialized [-Werror=uninitialized]: 6163:45 =>
- {standard input}: Error: unknown pseudo-op: `.': 1118 =>
*** WARNINGS ***
36 warning regressions:
+ modpost: WARNING: modpost: "__udelay" [drivers/char/hw_random/st-rng.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/gpio/gpio-aggregator.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/iio/pressure/mprls0025pa.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/net/phy/microchip_t1s.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/net/wireless/realtek/rtw89/rtw89_8851b.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/phy/qualcomm/phy-qcom-sgmii-eth.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/pinctrl/qcom/pinctrl-msm.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/pwm/pwm-microchip-core.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/soc/qcom/qcom_ice.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [drivers/spi/spi-rzv2m-csi.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: "__udelay" [sound/soc/loongson/snd-soc-loongson-i2s-pci.ko] has no CRC!: => N/A
+ modpost: WARNING: modpost: drivers/cpufreq/sparc-us2e-cpufreq: section mismatch in reference: cpufreq_us2e_driver+0x20 (section: .data) -> us2e_freq_cpu_init (section: .init.text): => N/A
+ modpost: WARNING: modpost: drivers/cpufreq/sparc-us3-cpufreq: section mismatch in reference: cpufreq_us3_driver+0x20 (section: .data) -> us3_freq_cpu_init (section: .init.text): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x14 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x30 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x4c (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x68 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0x84 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xa0 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xbc (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_ext_maps+0xd8 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x14 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x30 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x4c (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x68 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0x84 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0xa0 (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed: section mismatch in reference: qed_mfw_legacy_maps+0xbc (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x14 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x30 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x4c (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x68 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0x84 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0xa0 (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede: section mismatch in reference: qede_forced_speed_maps+0xbc (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): => N/A
+ modpost: WARNING: modpost: vmlinux: section mismatch in reference: __trace_event_discard_commit+0xe0 (section: .text.unlikely) -> initcall_level_names (section: .init.data): => N/A
18 warning improvements:
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/adl_pci9118.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/amplc_pci230.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/cb_das16_cs.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/cb_pcidas.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/das800.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/mpc624.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/ni_atmio.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/ni_labpc_common.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/pcl812.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/pcl816.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/pcl818.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/comedi/drivers/rti800.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "__udelay" [drivers/net/ethernet/stmicro/stmmac/dwmac-altr-socfpga.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: "empty_zero_page" [drivers/md/dm-flakey.ko] has no CRC!: N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o: section mismatch in reference: qed_mfw_ext_maps (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qed/qed.o: section mismatch in reference: qed_mfw_legacy_maps (section: .data) -> qed_mfw_legacy_bb_100g (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: drivers/net/ethernet/qlogic/qede/qede.o: section mismatch in reference: qede_forced_speed_maps (section: .data) -> qede_forced_speed_100000 (section: .init.rodata): N/A =>
- modpost: WARNING: modpost: vmlinux.o: section mismatch in reference: __trace_event_discard_commit (section: .text.unlikely) -> initcall_level_names (section: .init.data): N/A =>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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
On Mon, 10 Jul 2023, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.5-rc1[1] compared to v6.4[2].
>
> Summarized:
> - build errors: +3/-4
> - build warnings: +36/-18
>
> 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/06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5/ (all 162 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (160 out of 162 configs)
>
>
> *** ERRORS ***
>
> 3 error regressions:
> + /kisskb/src/drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c: error: the frame size of 1392 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]: => 1036:1
m68k-gcc8/m68k-allmodconfig
> + error: modpost: "__xchg_called_with_bad_pointer" [lib/atomic64_test.ko] undefined!: => N/A
sparc64-gcc11/sparc64-allmodconfig
> + {standard input}: Error: unknown pseudo-op: `.glo': => 1097
sh4-gcc11/sh-allmodconfig (ICE)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
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
On Sun, Jul 09, 2023 at 02:17:59PM -0700, Linus Torvalds wrote:
> Right on schedule two weeks after the 6.4 release, here we are and the
> merge window is closed.
>
Build results:
total: 157 pass: 156 fail: 1
Failed builds:
sparc64:allmodconfig
Qemu test results:
total: 520 pass: 502 fail: 18
Failed tests:
<all sh4>
The failures are tracked at
https://linux-regtracking.leemhuis.info/regzbot/mainline/.
The following patches are needed to fix the problems.
sh: mach-r2d: Handle virq offset in cascaded IRL demux
sparc: mark __arch_xchg() as __always_inline
Guenter
Hi--
On 7/10/23 03:00, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v6.5-rc1[1] compared to v6.4[2].
>
> Summarized:
> - build errors: +3/-4
> - build warnings: +36/-18
>
> 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/06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5/ (all 162 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (160 out of 162 configs)
>
>
> *** WARNINGS ***
>
> 36 warning regressions:
> + modpost: WARNING: modpost: drivers/cpufreq/sparc-us2e-cpufreq: section mismatch in reference: cpufreq_us2e_driver+0x20 (section: .data) -> us2e_freq_cpu_init (section: .init.text): => N/A
> + modpost: WARNING: modpost: drivers/cpufreq/sparc-us3-cpufreq: section mismatch in reference: cpufreq_us3_driver+0x20 (section: .data) -> us3_freq_cpu_init (section: .init.text): => N/A
The way that I read this is that these __init functions (us2e_freq_cpu_init and us3_freq_cpu_init)
should not be marked as __init since they can be called at any time by exercising the CPU hotplug
code path.
--
~Randy
On 10-07-23, 22:33, Randy Dunlap wrote:
> Hi--
>
> On 7/10/23 03:00, Geert Uytterhoeven wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v6.5-rc1[1] compared to v6.4[2].
> >
> > Summarized:
> > - build errors: +3/-4
> > - build warnings: +36/-18
> >
> > 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/06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5/ (all 162 configs)
> > [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6995e2de6891c724bfeb2db33d7b87775f913ad1/ (160 out of 162 configs)
> >
> >
> > *** WARNINGS ***
> >
> > 36 warning regressions:
>
> > + modpost: WARNING: modpost: drivers/cpufreq/sparc-us2e-cpufreq: section mismatch in reference: cpufreq_us2e_driver+0x20 (section: .data) -> us2e_freq_cpu_init (section: .init.text): => N/A
> > + modpost: WARNING: modpost: drivers/cpufreq/sparc-us3-cpufreq: section mismatch in reference: cpufreq_us3_driver+0x20 (section: .data) -> us3_freq_cpu_init (section: .init.text): => N/A
>
> The way that I read this is that these __init functions (us2e_freq_cpu_init and us3_freq_cpu_init)
> should not be marked as __init since they can be called at any time by exercising the CPU hotplug
> code path.
I have prepared a patch for this, waiting for some builds to finish
before sending it.
--
viresh
Subject: [PATCH] cpufreq: sparc: Don't mark cpufreq callbacks with __init
These callbacks can be called again by the cpufreq core after the driver
is initialized and must be kept around. We currently get section
mismatch build warnings.
Don't mark them with __init.
Fixes: dcfce7c2cee4 ("cpufreq: sparc: Don't allocate cpufreq_driver dynamically")
Reported-by: Geert Uytterhoeven <[email protected]>
Signed-off-by: Viresh Kumar <[email protected]>
---
drivers/cpufreq/sparc-us2e-cpufreq.c | 2 +-
drivers/cpufreq/sparc-us3-cpufreq.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/sparc-us2e-cpufreq.c b/drivers/cpufreq/sparc-us2e-cpufreq.c
index d3510cfdb3eb..2783d3d55fce 100644
--- a/drivers/cpufreq/sparc-us2e-cpufreq.c
+++ b/drivers/cpufreq/sparc-us2e-cpufreq.c
@@ -269,7 +269,7 @@ static int us2e_freq_target(struct cpufreq_policy *policy, unsigned int index)
return smp_call_function_single(cpu, __us2e_freq_target, &index, 1);
}
-static int __init us2e_freq_cpu_init(struct cpufreq_policy *policy)
+static int us2e_freq_cpu_init(struct cpufreq_policy *policy)
{
unsigned int cpu = policy->cpu;
unsigned long clock_tick = sparc64_get_clock_tick(cpu) / 1000;
diff --git a/drivers/cpufreq/sparc-us3-cpufreq.c b/drivers/cpufreq/sparc-us3-cpufreq.c
index 91d1ed558136..6c3657679a88 100644
--- a/drivers/cpufreq/sparc-us3-cpufreq.c
+++ b/drivers/cpufreq/sparc-us3-cpufreq.c
@@ -117,7 +117,7 @@ static int us3_freq_target(struct cpufreq_policy *policy, unsigned int index)
return smp_call_function_single(cpu, update_safari_cfg, &new_bits, 1);
}
-static int __init us3_freq_cpu_init(struct cpufreq_policy *policy)
+static int us3_freq_cpu_init(struct cpufreq_policy *policy)
{
unsigned int cpu = policy->cpu;
unsigned long clock_tick = sparc64_get_clock_tick(cpu) / 1000;