SCH.cx – The Fifth Weekly Release Candidate Version of Linux 5.11 Begins Testing. The Linux kernel was upgraded to Linux 5.11-rc4 last week. Linus Torvalds has formed a fairly normal release cycle for this description. However, Linux 5.11-rc5 was merged and issued on Sunday. He complained in today’s announcement: “This rc seems to have been quite calm for a long time, and the update rate is very small.
“In fact, more than 40% of non-merged commits appeared this Sunday, and people gave me all the work of the week. The end result is that rc5 is slightly larger than usual… but most of them are It’s a mixed bag of repairs, many of which are really trivial lines or lines…In other words, there is nothing here that allows me to say “um”.”
In general, Linux 5.11-rc5 seems to be in a fairly stable state. One notable fix this week is to fix the Itanium IA64 kernel build, as its default kernel configuration has been problematic in the past month since the beginning of the 5.11 cycle.
What remains to be fixed is the AMD CPU frequency patch on Linux 5.11, which also provides some good benefits in other workloads. On Monday, Linus will probably have more results and details in the community (or look at the early details).
The stable version of Linux 5.11 will be launched in February.
* Linux 5.11-rc5
@ 2021-01-25 1:06 Linus Torvalds
2021-01-25 3:48 ` Guenter Roeck
2021-01-25 20:34 ` Chris Wilson
0 siblings, 2 replies; 20+ messages in thread
From: Linus Torvalds @ 2021-01-25 1:06 UTC (permalink / raw)
To: Linux Kernel Mailing List
So this rc looked fairly calm and small, all the way up until today.
In fact, over 40% of the non-merge commits came in today, as people
unloaded their work for the week on me. The end result is a slightly
larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
kind of odd outlier).
Nothing particularly stands out. We had a couple of splice()
regressions that came in during the previous release as part of the
"get rid of set_fs()" development, but they were for odd cases that
most people would never notice. I think it's just that 5.10 is now
getting more widely deployed so people see the fallout from that
rather fundamental change in the last release. And the only reason I
even reacted to those is just because I ended up being involved with
some of the tty patches during the early calm period of the past week.
There's a few more still pending.
But the bulk of it all is all the usual miscellaneous fixes all over
the place, and a lot of it is truly trivial one- or few-liners. Just
under half the patch is for drivers, with the rest being the usual mix
of tooling, arch updates, filesystem and core (mm, scheduling,
networking).
Nothing here makes me go "Uhhuh" in other words.
Linus
---
Aaron Liu (1):
drm/amdgpu: update mmhub mgcg&ls for mmhub_v2_3
Adrian Hunter (2):
scsi: docs: ABI: sysfs-driver-ufs: Add DeepSleep power mode
perf evlist: Fix id index for heterogeneous systems
Al Cooper (1):
mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
Alan Stern (1):
USB: gadget: dummy-hcd: Fix errors in port-reset handling
Alban Bedel (1):
net: mscc: ocelot: Fix multicast to the CPU port
Alex Leibovich (1):
mmc: sdhci-xenon: fix 1.8v regulator stabilization
Alexander Guril (1):
Kernel: fork.c: Fix coding style: Do not use {} around
single-line statements
Alexander Lobakin (2):
PHY: Ingenic: fix unconditional build of phy-ingenic-usb
skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
Alexander Shishkin (1):
intel_th: pci: Add Alder Lake-P support
Alexandru Ardelean (1):
iio: adc: ti_am335x_adc: remove omitted iio_kfifo_free()
Andrey Konovalov (4):
kasan, arm64: fix pointer tags in KASAN reports
kasan: fix HW_TAGS boot parameters
kasan, mm: fix conflicts with init_on_alloc/free
kasan, mm: fix resetting page_alloc tags for HW_TAGS
Andrii Nakryiko (2):
bpf: Allow empty module BTFs
libbpf: Allow loading empty BTFs
Andy Lutomirski (2):
x86/fpu: Add kernel_fpu_begin_mask() to selectively initialize state
x86/mmx: Use KFPU_387 for MMX string operations
Andy Shevchenko (1):
sh: Drop ARCH_NR_GPIOS definition
Anshuman Gupta (2):
drm/i915/hdcp: Update CP property in update_pipe
drm/i915/hdcp: Get conn while content_type changed
Aric Cyr (1):
drm/amd/display: Allow PSTATE chnage when no displays are enabled
Arnd Bergmann (4):
phy: mediatek: allow compile-testing the dsi phy
scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression
crypto: omap-sham - Fix link error without crypto-engine
ubsan: disable unsigned-overflow check for i386
Arnold Gozum (1):
platform/x86: intel-vbtn: Support for tablet mode on Dell Inspiron 7352
Baruch Siach (1):
gpio: mvebu: fix pwm .get_state period calculation
Billy Tsai (1):
pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting
Bing Guo (1):
drm/amd/display: Change function decide_dp_link_settings to
avoid infinite looping
Björn Töpel (1):
MAINTAINERS: Update my email address
Bongsu Jeon (1):
net: nfc: nci: fix the wrong NCI_CORE_INIT parameters
Borislav Petkov (1):
x86/topology: Make __max_die_per_package available unconditionally
Brian King (1):
scsi: ibmvfc: Set default timeout to avoid crash during migration
Chaitanya Kulkarni (1):
nvmet: set right status on error in id-ns handler
Chao Leng (2):
nvme-rdma: avoid request double completion for concurrent
nvme_rdma_timeout
nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout
Chris Chiu (1):
ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
Chris Wilson (2):
drm/i915/gt: Prevent use of engine->wa_ctx after error
drm/i915: Check for rq->hwsp validity after acquiring RCU lock
Christian König (1):
drm/ttm: stop using GFP_TRANSHUGE_LIGHT
Christoph Hellwig (6):
sh: remove CONFIG_IDE from most defconfig
nvme-pci: refactor nvme_unmap_data
nvme-pci: fix error unwind in nvme_map_data
kernfs: implement ->read_iter
kernfs: implement ->write_iter
kernfs: wire up ->splice_read and ->splice_write
Christophe Leroy (1):
spi: fsl: Fix driver breakage when SPI_CS_HIGH is not set in spi->mode
Chuck Lever (1):
SUNRPC: Move the svc_xdr_recvfrom tracepoint again
Chunguang Xu (1):
timekeeping: Remove unused get_seconds()
Cong Wang (1):
cls_flower: call nla_ok() before nla_next()
Dan Carpenter (2):
iio: sx9310: Off by one in sx9310_read_thresh()
net: dsa: b53: fix an off by one in checking "vlan->vid"
Dan Williams (1):
mm: fix page reference leak in soft_offline_page()
Daniel Borkmann (1):
bpf: Fix signed_{sub,add32}_overflows type handling
Daniel Latypov (4):
Documentation: kunit: include example of a parameterized test
kunit: tool: surface and address more typing issues
kunit: tool: fix minor typing issue with None status
kunit: tool: move kunitconfig parsing into __init__, make it optional
Daniel Vetter (1):
drm/syncobj: Fix use-after-free
David Gow (1):
kunit: tool: Fix spelling of "diagnostic" in kunit_parser
David Lechner (1):
counter:ti-eqep: remove floor
David Sterba (1):
btrfs: no need to run delayed refs after commit_fs_roots during commit
Dexuan Cui (1):
x86/hyperv: Initialize clockevents after LAPIC is initialized
Dinghao Liu (1):
scsi: fnic: Fix memleak in vnic_dev_init_devcmd2
Douglas Anderson (4):
pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0
pinctrl: qcom: No need to read-modify-write the interrupt status
pinctrl: qcom: Properly clear "intr_ack_high" interrupts when unmasking
pinctrl: qcom: Don't clear pending interrupts when enabling
Enke Chen (1):
tcp: fix TCP_USER_TIMEOUT with zero window
Eric Biggers (1):
fs: fix lazytime expiration handling in __writeback_single_inode()
Eric Dumazet (4):
net_sched: reject silly cell_log in qdisc_get_rtab()
net_sched: gen_estimator: support large ewma log
net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
tcp: do not mess with cloned skbs in tcp_add_backlog()
Eugene Korenevsky (1):
ehci: fix EHCI host controller initialization sequence
Fabio Estevam (1):
Revert "i2c: imx: Remove unused .id_table support"
Felix Fietkau (3):
mac80211: fix fast-rx encryption check
mac80211: fix encryption key selection for 802.3 xmit
mac80211: do not drop tx nulldata packets on encrypted links
Filipe Manana (1):
btrfs: send: fix invalid clone operations when cloning from the
same file and root
Gayatri Kammela (1):
x86/cpu: Add another Alder Lake CPU to the Intel family
Geert Uytterhoeven (7):
platform/surface: SURFACE_PLATFORMS should depend on ACPI
sh/intc: Restore devm_ioremap() alignment
ntp: Fix RTC synchronization on 32-bit platforms
mdio-bitbang: Export mdiobb_{read,write}()
sh_eth: Make PHY access aware of Runtime PM to fix reboot crash
openrisc: io: Add missing __iomem annotation to iounmap()
sh_eth: Fix power down vs. is_opened flag ordering
Gilad Reti (2):
bpf: Support PTR_TO_MEM{,_OR_NULL} register spilling
selftests/bpf: Add verifier test for PTR_TO_MEM spill
Grant Grundler (1):
net: usb: cdc_ncm: don't spew notifications
Greg Kroah-Hartman (1):
Revert "driver core: Reorder devices on successful probe"
Guillaume Nault (2):
udp: mask TOS bits in udp_v4_early_demux()
netfilter: rpfilter: mask ecn bits before fib lookup
Hangbin Liu (1):
selftests: net: fib_tests: remove duplicate log test
Hannes Reinecke (1):
dm: avoid filesystem lookup in dm_get_dev_t()
Hans de Goede (4):
platform/x86: touchscreen_dmi: Add swap-x-y quirk for Goodix
touchscreen on Estar Beauty HD tablet
platform/x86: intel-vbtn: Drop HP Stream x360 Convertible PC 11
from allow-list
platform/x86: hp-wmi: Don't log a warning on
HPWMI_RET_UNKNOWN_COMMAND errors
ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
Heikki Krogerus (1):
platform/x86: i2c-multi-instantiate: Don't create platform
device for INT3515 ACPI nodes
Hsin-Yi Wang (1):
pinctrl: mediatek: Fix fallback call path
Huacai Chen (1):
irqchip/loongson-liointc: Fix build warnings
Huang Rui (1):
drm/amdgpu: remove gpu info firmware of green sardine
Hyunwook (Wooky) Baek (1):
x86/sev-es: Handle string port IO to kernel memory properly
Ignat Korchagin (1):
dm crypt: fix copy and paste bug in crypt_alloc_req_aead
Ilan Peer (1):
cfg80211: Save the regulatory domain with a lock
Ilya Dryomov (3):
libceph: zero out session key and connection secret
libceph, ceph: disambiguate ceph_connection_operations handlers
libceph: fix "Boolean result is used in bitwise operation" warning
J. Bruce Fields (1):
nfsd4: readdirplus shouldn't return parent of export
JC Kuo (1):
xhci: tegra: Delay for disabling LFPS detector
Jaegeuk Kim (2):
scsi: ufs: Fix livelock of ufshcd_clear_ua_wluns()
scsi: ufs: Fix tm request when non-fatal error happens
Jake Wang (1):
drm/amd/display: Update dram_clock_change_latency for DCN2.1
Jann Horn (1):
signal: Add missing __user annotation to copy_siginfo_from_user_any
Javed Hasan (1):
scsi: libfc: Avoid invoking response handler twice if ep is
already completed
Jeannie Stevenson (1):
platform/x86: thinkpad_acpi: Add P53/73 firmware to
fan_quirk_table for dual fan control
Jens Axboe (4):
task_work: unconditionally run task_work from get_signal()
io_uring: iopoll requests should also wake task ->in_idle state
io_uring: fix SQPOLL IORING_OP_CLOSE cancelation state
io_uring: account io_uring internal files as REQ_F_INFLIGHT
Jiapeng Zhong (2):
fs/cifs: Assign boolean values to a bool variable
fs/cifs: Simplify bool comparison.
Jiaxun Yang (1):
platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
Jin Yao (1):
perf script: Fix overrun issue for dynamically-allocated PMU type number
Jinyang He (1):
sh: Remove unused HAVE_COPY_THREAD_TLS macro
Jinzhou Su (1):
drm/amdgpu: modify GCR_GENERAL_CNTL for Vangogh
Jiri Olsa (1):
bpf: Prevent double bpf_prog_put call from bpf_tracing_prog_attach
Jisheng Zhang (1):
mmc: sdhci-of-dwcmshc: fix rpmb access
Johannes Berg (1):
cfg80211/mac80211: fix kernel-doc for SAR APIs
John Garry (4):
driver core: platform: Add extra error check in
devm_platform_get_irqs_affinity()
Driver core: platform: Add extra error check in
devm_platform_get_irqs_affinity()
perf metricgroup: Fix for metrics containing duration_time
perf metricgroup: Fix system PMU metrics
John Ogness (3):
printk: ringbuffer: fix line counting
printk: fix kmsg_dump_get_buffer length calulations
printk: fix buffer overflow potential for print_text()
Josef Bacik (4):
btrfs: don't get an EINTR during drop_snapshot for reloc
btrfs: do not double free backref nodes on error
btrfs: fix lockdep splat in btrfs_recover_relocation
btrfs: don't clear ret in btrfs_start_dirty_block_groups
Josh Poimboeuf (3):
objtool: Don't add empty symbols to the rbtree
objtool: Don't fail the kernel build on fatal errors
objtool: Don't fail on missing symbol table
KP Singh (3):
bpf: Local storage helpers should check nullness of owner ptr passed
bpf: Fix typo in bpf_inode_storage.c
bpf: Update local storage test to check handling of null ptrs
Kai Vehmanen (2):
ALSA: hda: Add AlderLake-P PCI ID and HDMI codec vid
ASoC: SOF: Intel: fix page fault at probe if i915 init fails
Kai-Chuan Hsieh (1):
ALSA: hda: Add Cometlake-R PCI ID
Kai-Heng Feng (4):
ASoC: SOF: Intel: hda: Resume codec to do jack detection
ASoC: SOF: Intel: hda: Modify existing helper to disable WAKEEN
ASoC: SOF: Intel: hda: Avoid checking jack on system suspend
ALSA: hda: Balance runtime/system PM if direct-complete is disabled
Kent Gibson (3):
gpiolib: cdev: fix frame size warning in gpio_ioctl()
tools: gpio: fix %llu warning in gpio-event-mon.c
tools: gpio: fix %llu warning in gpio-watch.c
Kirill Tkhai (1):
crypto: xor - Fix divide error in do_xor_speed()
Klaus Jensen (1):
nvme-pci: allow use of cmb on v1.4 controllers
Krzysztof Kozlowski (1):
i2c: sprd: depend on COMMON_CLK to fix compile tests
Kuniyuki Iwashima (1):
tcp: Fix potential use-after-free due to double kfree()
Lai Jiangshan (1):
workqueue: Use cpu_possible_mask instead of cpu_active_mask to
break affinity
Lars-Peter Clausen (1):
iio: ad5504: Fix setting power-down state
Lecopzer Chen (2):
kasan: fix unaligned address is unhandled in kasan_remove_zero_shadow
kasan: fix incorrect arguments passing in kasan_add_zero_shadow
Levi Yun (1):
mm/memblock: Fix typo in comment of memblock_phys_alloc_try_nid()
Linus Torvalds (3):
tty: implement write_iter
tty: fix up hung_up_tty_write() conversion
Linux 5.11-rc5
Longfang Liu (1):
USB: ehci: fix an interrupt calltrace error
Lorenzo Bianconi (2):
iio: common: st_sensors: fix possible infinite loop in
st_sensors_irq_thread
mac80211: check if atf has been disabled in __ieee80211_schedule_txq
Lukas Bulwahn (1):
scsi: docs: ABI: sysfs-driver-ufs: Rectify table formatting
Marc Zyngier (1):
irqchip/bcm2836: Fix IPI acknowledgement after conversion to
handle_percpu_devid_irq
Mark Pearson (1):
platform/x86: thinkpad_acpi: correct palmsensor error checking
Martin Blumenstingl (1):
mtd: rawnand: intel: check the mtd name only after setting the variable
Martin Wilck (1):
scsi: scsi_transport_srp: Don't block target in failfast state
Mathias Kresin (1):
irqchip/mips-cpu: Set IPI domain parent chip
Mathias Nyman (1):
xhci: make sure TRB is fully written before giving it to the controller
Matteo Croce (2):
ipv6: create multicast route with RTPROT_KERNEL
ipv6: set multicast flag on the multicast route
Mauro Carvalho Chehab (2):
MAINTAINERS: update references to stm32 audio bindings
cfg80211: fix a kerneldoc markup
Maxim Mikityanskiy (1):
xsk: Clear pool even for inactive queues
Meng Li (1):
drivers core: Free dma_range_map when driver probe failed
Michael Ellerman (1):
selftests/powerpc: Only test lwm/stmw on big endian
Michael Hennerich (1):
spi: cadence: cache reference clock rate during probe
Mika Westerberg (1):
thunderbolt: Drop duplicated 0x prefix from format string
Mike Rapoport (3):
ia64: fix build failure caused by memory model changes
x86/setup: don't remove E820_TYPE_RAM for pfn 0
mm: fix initialization of struct page for holes in memory layout
Mikko Perttunen (2):
i2c: tegra: Wait for config load atomically while in ISR
i2c: bpmp-tegra: Ignore unknown I2C_M flags
Mikulas Patocka (2):
dm integrity: fix a crash if "recalculate" used without "internal_hash"
dm integrity: conditionally disable "recalculate" feature
Miquel Raynal (3):
mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft
ECC engine
mtd: spinand: Fix MTD_OPS_AUTO_OOB requests
mtd: rawnand: omap: Use BCH private fields in the specific OOB layout
Mircea Cirjaliu (1):
bpf: Fix helper bpf_map_peek_elem_proto pointing to wrong callback
Nathan Chancellor (2):
pinctrl: nomadik: Remove unused variable in nmk_gpio_dbg_show_one
MAINTAINERS: add a couple more files to the Clang/LLVM section
Necip Fazil Yildiran (1):
sh: dma: fix kconfig dependency for G2_DMA
Nicholas Kazlauskas (1):
drm/amd/display: Use hardware sequencer functions for PG control
Nicholas Piggin (1):
powerpc/64s: fix scv entry fallback flush vs interrupt
Nicolas Saenz Julienne (1):
drm/vc4: Unify PCM card's driver_name
Nikita Shubin (1):
gpiolib: add a warning on gpiochip->to_irq defined
Oded Gabbay (5):
habanalabs: fix dma_addr passed to dma_mmap_coherent
habanalabs: fix reset process in case of failures
habanalabs: prevent soft lockup during unmap
habanalabs: fix backward compatibility of idle check
habanalabs: disable FW events on device removal
Ofir Bitton (1):
habanalabs: zero pci counters packet before submit to FW
Oleksandr Mazur (1):
net: core: devlink: use right genl user_ptr when handling port
param get/set
Pali Rohár (1):
serial: mvebu-uart: fix tx lost characters at power off
Pan Bian (3):
drm/atomic: put state on error path
net: systemport: free dev before on error path
lightnvm: fix memory leak when submit fails
Patrik Jakobsson (1):
usb: bdc: Make bdc pci driver depend on BROKEN
Paul Cercueil (2):
pinctrl: ingenic: Fix JZ4760 support
pinctrl: ingenic: Rename registers from JZ4760_GPIO_* to JZ4770_GPIO_*
Pavel Begunkov (5):
io_uring: fix false positive sqo warning on flush
io_uring: fix uring_flush in exit_files() warning
io_uring: fix skipping disabling sqo on exec
io_uring: fix short read retries for non-reg files
io_uring: fix sleeping under spin in __io_clean_op
Peter Chen (4):
usb: cdns3: imx: fix writing read-only memory issue
usb: cdns3: imx: fix can't create core device the second time issue
usb: cdns3: imx: improve driver .remove API
MAINTAINERS: update Peter Chen's email address
Peter Collingbourne (1):
mmc: core: don't initialize block size from ext_csd if not present
Peter Zijlstra (13):
x86/entry: Fix noinstr fail
x86/sev: Fix nonistr violation
locking/lockdep: Cure noinstr fail
locking/lockdep: Avoid noinstr warning for DEBUG_LOCKDEP
x86/mce: Remove explicit/superfluous tracing
x86: __always_inline __{rd,wr}msr()
sched: Don't run cpu-online with balance_push() enabled
kthread: Extract KTHREAD_IS_PER_CPU
workqueue: Tag bound workers with KTHREAD_IS_PER_CPU
workqueue: Restrict affinity change to rescuer
sched: Prepare to use balance_push in ttwu()
sched: Fix CPU hotplug / tighten is_per_cpu_kthread()
sched: Relax the set_cpus_allowed_ptr() semantics
Prike Liang (1):
drm/amdgpu/pm: no need GPU status set since
mmnbif_gpu_BIF_DOORBELL_FENCE_CNTL added in FSDL
Qais Yousef (1):
arm64: kprobes: Fix Uexpected kernel BRK exception at EL1
Qinglang Miao (2):
sh: intc: Convert to DEFINE_SHOW_ATTRIBUTE
sh: mm: Convert to DEFINE_SHOW_ATTRIBUTE
Rafael J. Wysocki (2):
x86: PM: Register syscore_ops for scale invariance
driver core: Extend device_is_dependent()
Randy Dunlap (5):
platform/surface: surface_gpe: Fix non-PM_SLEEP build warnings
arch/sh: hyphenate Non-Uniform in Kconfig prompt
scsi: ufs: ufshcd-pltfrm depends on HAS_IOMEM
x86/xen: fix 'nopvspin' build error
gpio: sifive: select IRQ_DOMAIN_HIERARCHY rather than depend on it
Rasmus Villemoes (1):
net: dsa: mv88e6xxx: also read STU state in mv88e6250_g1_vtu_getnext
Revanth Rajashekar (1):
nvme: check the PRINFO bit before deciding the host buffer length
Ricky Wu (1):
misc: rtsx: init value of aspm_enabled
Roger Quadros (1):
MAINTAINERS: Update address for Cadence USB3 driver
Roman Gushchin (1):
mm: memcg/slab: optimize objcg stock draining
Ronnie Sahlberg (1):
cifs: do not fail __smb_send_rqst if non-fatal signals are pending
Ryan Chen (1):
usb: gadget: aspeed: fix stop dma register setting.
Sandipan Das (1):
selftests/powerpc: Fix exit status of pkey tests
Saravana Kannan (1):
driver core: Fix device link device name collision
Sean Nyekjaer (1):
mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
Shakeel Butt (2):
mm: memcg: fix memcg file_dirty numa stat
mm: fix numa stats for thp migration
Shayne Chen (1):
mac80211: fix incorrect strlen of .write in debugfs
Shin'ichiro Kawasaki (1):
scsi: target: tcmu: Fix use-after-free of se_cmd->priv
Shyam Sundar S K (1):
platform/x86: amd-pmc: Fix CONFIG_DEBUG_FS check
Slaveyko Slaveykov (1):
drivers: iio: temperature: Add delay after the addressed reset
command in mlx90632.c
Song Liu (1):
bpf: Reject too big ctx_size_in for raw_tp test run
Sowjanya Komatineni (1):
i2c: tegra: Create i2c_writesl_vi() to use with VI I2C for filling TX FIFO
Srinivas Kandagatla (2):
MAINTAINERS: update maintainers of qcom audio
MAINTAINERS: update qcom ASoC drivers list
Srinivas Pandruvada (2):
tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency
tools/power/x86/intel-speed-select: Set higher of
cpuinfo_max_freq or base_frequency
Stafford Horne (1):
soc: litex: Fix compile warning when device tree is not configured
Stanislav Fomichev (1):
bpf: Don't leak memory in bpf getsockopt when optlen == 0
Stephan Gerhold (2):
ASoC: hdmi-codec: Fix return value in hdmi_codec_set_jack()
dt-bindings: iio: accel: bma255: Fix bmc150/bmi055 compatible
Stephen Boyd (1):
iio: sx9310: Fix semtech,avg-pos-strength setting when > 16
Suman Anna (1):
irqchip/pruss: Simplify the TI_PRUSS_INTC Kconfig
Sung Lee (1):
drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
Takashi Iwai (8):
ALSA: usb-audio: Always apply the hw constraints for implicit fb sync
ALSA: hda/via: Add minimum mute flag
ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
ALSA: usb-audio: Fix UAC1 rate setup for secondary endpoints
ALSA: usb-audio: Set sample rate for all sharing EPs on UAC1
ALSA: usb-audio: Avoid implicit feedback on Pioneer devices
cachefiles: Drop superfluous readpages aops NULL check
ALSA: usb-audio: Fix hw constraints dependencies
Tariq Toukan (1):
net: Disable NETIF_F_HW_TLS_RX when RXCSUM is disabled
Thierry Reding (1):
gpio: tegra: Add missing dependencies
Thinh Nguyen (1):
usb: udc: core: Use lock when write to soft_connect
Thomas Gleixner (5):
genirq: Export irq_check_status_bit()
sparc/mm/highmem: flush cache and TLB
mm/highmem: prepare for overriding set_pte_at()
mips/mm/highmem: use set_pte() for kmap_local()
powerpc/mm/highmem: use __set_pte_at() for kmap_local()
Thomas Zimmermann (1):
drm/vram-helper: Reuse existing page mappings in vmap
Tianjia Zhang (1):
X.509: Fix crash caused by NULL pointer
Tony Lindgren (1):
phy: cpcap-usb: Fix warning for missing regulator_disable
Tvrtko Ursulin (1):
drm/i915/pmu: Don't grab wakeref when enabling events
Tyrel Datwyler (1):
scsi: ibmvfc: Fix missing cast of ibmvfc_event pointer to u64 handle
Valentin Schneider (1):
sched/core: Print out straggler tasks in sched_cpu_dying()
Ville Syrjälä (1):
drm/i915: Only enable DFP 4:4:4->4:2:0 conversion when
outputting YCbCr 4:4:4
Vincent Mailhol (3):
can: dev: can_restart: fix use after free bug
can: vxcan: vxcan_xmit: fix use after free bug
can: peak_usb: fix use after free bugs
Vladimir Oltean (1):
net: mscc: ocelot: allow offloading of bridge on top of LAG
Vladimir Stempen (1):
drm/amd/display: Fixed corruptions on HPDRX link loss restore
Wang Hui (1):
stm class: Fix module init return on allocation failure
Wang Qing (2):
arch: sh: remove duplicate include
sh: mach-sh03: remove duplicate include
Wolfram Sang (1):
i2c: octeon: check correct size of maximum RECV_LEN packet
Xiao Ni (1):
md: Set prev_flush_start and flush_bio in an atomic way
Xiaoming Ni (1):
proc_sysctl: fix oops caused by incorrect command parameters
Yanfei Xu (1):
kthread: remove comments about old _do_fork() helper
Yazen Ghannam (1):
x86/cpu/amd: Set __max_die_per_package on AMD
Yingjie Wang (1):
octeontx2-af: Fix missing check bugs in rvu_cgx.c
Yuchung Cheng (1):
tcp: fix TCP socket rehash stats mis-accounting
Zenghui Yu (1):
genirq/msi: Initialize msi_alloc_info before calling
msi_domain_prepare_irqs()
Zheng Yongjun (1):
irqchip/irq-sl28cpld: Convert comma to semicolon
lianzhi chang (1):
udf: fix the problem that the disc content is not displayed
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 1:06 Linux 5.11-rc5 Linus Torvalds
@ 2021-01-25 3:48 ` Guenter Roeck
2021-01-25 3:56 ` Bhaskar Chowdhury
2021-01-25 20:34 ` Chris Wilson
1 sibling, 1 reply; 20+ messages in thread
From: Guenter Roeck @ 2021-01-25 3:48 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
> So this rc looked fairly calm and small, all the way up until today.
>
> In fact, over 40% of the non-merge commits came in today, as people
> unloaded their work for the week on me. The end result is a slightly
> larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
> kind of odd outlier).
>
> Nothing particularly stands out. We had a couple of splice()
> regressions that came in during the previous release as part of the
> "get rid of set_fs()" development, but they were for odd cases that
> most people would never notice. I think it's just that 5.10 is now
> getting more widely deployed so people see the fallout from that
> rather fundamental change in the last release. And the only reason I
> even reacted to those is just because I ended up being involved with
> some of the tty patches during the early calm period of the past week.
> There's a few more still pending.
>
> But the bulk of it all is all the usual miscellaneous fixes all over
> the place, and a lot of it is truly trivial one- or few-liners. Just
> under half the patch is for drivers, with the rest being the usual mix
> of tooling, arch updates, filesystem and core (mm, scheduling,
> networking).
>
> Nothing here makes me go "Uhhuh" in other words.
>
Looking pretty good now.
Build results:
total: 153 pass: 153 fail: 0
Qemu test results:
total: 430 pass: 430 fail: 0
Guenter
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 3:48 ` Guenter Roeck
@ 2021-01-25 3:56 ` Bhaskar Chowdhury
2021-01-25 4:06 ` Guenter Roeck
0 siblings, 1 reply; 20+ messages in thread
From: Bhaskar Chowdhury @ 2021-01-25 3:56 UTC (permalink / raw)
To: Guenter Roeck; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]
On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>> So this rc looked fairly calm and small, all the way up until today.
>>
>> In fact, over 40% of the non-merge commits came in today, as people
>> unloaded their work for the week on me. The end result is a slightly
>> larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
>> kind of odd outlier).
>>
>> Nothing particularly stands out. We had a couple of splice()
>> regressions that came in during the previous release as part of the
>> "get rid of set_fs()" development, but they were for odd cases that
>> most people would never notice. I think it's just that 5.10 is now
>> getting more widely deployed so people see the fallout from that
>> rather fundamental change in the last release. And the only reason I
>> even reacted to those is just because I ended up being involved with
>> some of the tty patches during the early calm period of the past week.
>> There's a few more still pending.
>>
>> But the bulk of it all is all the usual miscellaneous fixes all over
>> the place, and a lot of it is truly trivial one- or few-liners. Just
>> under half the patch is for drivers, with the rest being the usual mix
>> of tooling, arch updates, filesystem and core (mm, scheduling,
>> networking).
>>
>> Nothing here makes me go "Uhhuh" in other words.
>>
>
>Looking pretty good now.
>
>Build results:
> total: 153 pass: 153 fail: 0
>Qemu test results:
> total: 430 pass: 430 fail: 0
>
>Guenter
Hey,
Mind letting us know ,what you are running? Any automated stuff? Any specific
tool or tools?? Scripts???
Bloody curious to know Guenter ...if those stuff are expose able to public
consumption , please do provide the pointer too (I am being lazy to find it)
~Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 3:56 ` Bhaskar Chowdhury
@ 2021-01-25 4:06 ` Guenter Roeck
2021-01-25 4:11 ` Bhaskar Chowdhury
0 siblings, 1 reply; 20+ messages in thread
From: Guenter Roeck @ 2021-01-25 4:06 UTC (permalink / raw)
To: Bhaskar Chowdhury, Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1.1: Type: text/plain, Size: 2081 bytes --]
On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
> On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>> On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>>> So this rc looked fairly calm and small, all the way up until today.
>>>
>>> In fact, over 40% of the non-merge commits came in today, as people
>>> unloaded their work for the week on me. The end result is a slightly
>>> larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
>>> kind of odd outlier).
>>>
>>> Nothing particularly stands out. We had a couple of splice()
>>> regressions that came in during the previous release as part of the
>>> "get rid of set_fs()" development, but they were for odd cases that
>>> most people would never notice. I think it's just that 5.10 is now
>>> getting more widely deployed so people see the fallout from that
>>> rather fundamental change in the last release. And the only reason I
>>> even reacted to those is just because I ended up being involved with
>>> some of the tty patches during the early calm period of the past week.
>>> There's a few more still pending.
>>>
>>> But the bulk of it all is all the usual miscellaneous fixes all over
>>> the place, and a lot of it is truly trivial one- or few-liners. Just
>>> under half the patch is for drivers, with the rest being the usual mix
>>> of tooling, arch updates, filesystem and core (mm, scheduling,
>>> networking).
>>>
>>> Nothing here makes me go "Uhhuh" in other words.
>>>
>>
>> Looking pretty good now.
>>
>> Build results:
>> total: 153 pass: 153 fail: 0
>> Qemu test results:
>> total: 430 pass: 430 fail: 0
>>
>> Guenter
>
> Hey,
>
> Mind letting us know ,what you are running? Any automated stuff? Any specific
> tool or tools?? Scripts???
>
> Bloody curious to know Guenter ...if those stuff are expose able to public
> consumption , please do provide the pointer too (I am being lazy to find it)
>
Results:
https://kerneltests.org/builders
Script repository:
https://github.com/groeck/linux-build-test
Guenter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 4:06 ` Guenter Roeck
@ 2021-01-25 4:11 ` Bhaskar Chowdhury
0 siblings, 0 replies; 20+ messages in thread
From: Bhaskar Chowdhury @ 2021-01-25 4:11 UTC (permalink / raw)
To: Guenter Roeck; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8; format=flowed, Size: 2200 bytes --]
On 20:06 Sun 24 Jan 2021, Guenter Roeck wrote:
>On 1/24/21 7:56 PM, Bhaskar Chowdhury wrote:
>> On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote:
>>> On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote:
>>>> So this rc looked fairly calm and small, all the way up until today.
>>>>
>>>> In fact, over 40% of the non-merge commits came in today, as people
>>>> unloaded their work for the week on me. The end result is a slightly
>>>> larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some
>>>> kind of odd outlier).
>>>>
>>>> Nothing particularly stands out. We had a couple of splice()
>>>> regressions that came in during the previous release as part of the
>>>> "get rid of set_fs()" development, but they were for odd cases that
>>>> most people would never notice. I think it's just that 5.10 is now
>>>> getting more widely deployed so people see the fallout from that
>>>> rather fundamental change in the last release. And the only reason I
>>>> even reacted to those is just because I ended up being involved with
>>>> some of the tty patches during the early calm period of the past week.
>>>> There's a few more still pending.
>>>>
>>>> But the bulk of it all is all the usual miscellaneous fixes all over
>>>> the place, and a lot of it is truly trivial one- or few-liners. Just
>>>> under half the patch is for drivers, with the rest being the usual mix
>>>> of tooling, arch updates, filesystem and core (mm, scheduling,
>>>> networking).
>>>>
>>>> Nothing here makes me go "Uhhuh" in other words.
>>>>
>>>
>>> Looking pretty good now.
>>>
>>> Build results:
>>> total: 153 pass: 153 fail: 0
>>> Qemu test results:
>>> total: 430 pass: 430 fail: 0
>>>
>>> Guenter
>>
>> Hey,
>>
>> Mind letting us know ,what you are running? Any automated stuff? Any specific
>> tool or tools?? Scripts???
>>
>> Bloody curious to know Guenter ...if those stuff are expose able to public
>> consumption , please do provide the pointer too (I am being lazy to find it)
>>
>
>Results:
> https://kerneltests.org/builders
>Script repository:
> https://github.com/groeck/linux-build-test
>
>Guenter
>
Thanks a bunch!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 1:06 Linux 5.11-rc5 Linus Torvalds
2021-01-25 3:48 ` Guenter Roeck
@ 2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49 ` Linus Torvalds
2021-01-25 21:04 ` Mike Rapoport
1 sibling, 2 replies; 20+ messages in thread
From: Chris Wilson @ 2021-01-25 20:34 UTC (permalink / raw)
To: Linus Torvalds, Mike Rapoport; +Cc: Andrew Morton, Linux Kernel Mailing List
Quoting Linus Torvalds (2021-01-25 01:06:40)
> Mike Rapoport (3):
...
> mm: fix initialization of struct page for holes in memory layout
We have half a dozen or so different machines in CI that are silently
failing to boot, that we believe is bisected to this patch.
17:56 tsa : ickle: dolphin: I hit the following patch in my bisection, and the hang is also dependent on kconfig
17:56 tsa : first bad commit: [d3921cb8be29ce5668c64e23ffdaeec5f8c69399] mm: fix initialization of struct page for holes in
memory layout
17:57 tsa : couldn't reproduce on older CI kconfig, current one does it
https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/blob/master/kconfig/debug
Here's a boot dmesg from some affected machines from just before the merge
with rc5:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bsw-cyan/boot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bdw-samus/boot.html
-Chris
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 20:34 ` Chris Wilson
@ 2021-01-25 20:49 ` Linus Torvalds
2021-01-25 21:33 ` Mike Rapoport
2021-02-04 18:19 ` Mike Rapoport
2021-01-25 21:04 ` Mike Rapoport
1 sibling, 2 replies; 20+ messages in thread
From: Linus Torvalds @ 2021-01-25 20:49 UTC (permalink / raw)
To: Chris Wilson; +Cc: Mike Rapoport, Andrew Morton, Linux Kernel Mailing List
On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <[email protected]> wrote:
>
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> > mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing to boot, that we believe is bisected to this patch.
That commit reverts cleanly - so if you can verify that reverting it
fixes your CI machines, I think that that's the right thing to do for
now, unless Mike can figure out some obvious "Duh!" moment from your
working dmesg.
Mike: should we perhaps revert the first patch too (commit
bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
Linus
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49 ` Linus Torvalds
@ 2021-01-25 21:04 ` Mike Rapoport
2021-01-25 21:13 ` Chris Wilson
1 sibling, 1 reply; 20+ messages in thread
From: Mike Rapoport @ 2021-01-25 21:04 UTC (permalink / raw)
To: Chris Wilson; +Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List
On Mon, Jan 25, 2021 at 08:34:34PM +0000, Chris Wilson wrote:
> Quoting Linus Torvalds (2021-01-25 01:06:40)
> > Mike Rapoport (3):
> ...
> > mm: fix initialization of struct page for holes in memory layout
>
> We have half a dozen or so different machines in CI that are silently
> failing to boot, that we believe is bisected to this patch.
>
> 17:56 tsa : ickle: dolphin: I hit the following patch in my bisection, and the hang is also dependent on kconfig
> 17:56 tsa : first bad commit: [d3921cb8be29ce5668c64e23ffdaeec5f8c69399] mm: fix initialization of struct page for holes in
> memory layout
> 17:57 tsa : couldn't reproduce on older CI kconfig, current one does it
> https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/blob/master/kconfig/debug
>
> Here's a boot dmesg from some affected machines from just before the merge
> with rc5:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bsw-cyan/boot.html
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bdw-samus/boot.html
Is there any way to get early console from these machines?
> -Chris
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:04 ` Mike Rapoport
@ 2021-01-25 21:13 ` Chris Wilson
2021-01-26 16:37 ` Mike Rapoport
2021-01-28 21:00 ` Pavel Machek
0 siblings, 2 replies; 20+ messages in thread
From: Chris Wilson @ 2021-01-25 21:13 UTC (permalink / raw)
To: Mike Rapoport; +Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List
Quoting Mike Rapoport (2021-01-25 21:04:56)
> On Mon, Jan 25, 2021 at 08:34:34PM +0000, Chris Wilson wrote:
> > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > Mike Rapoport (3):
> > ...
> > > mm: fix initialization of struct page for holes in memory layout
> >
> > We have half a dozen or so different machines in CI that are silently
> > failing to boot, that we believe is bisected to this patch.
> >
> > 17:56 tsa : ickle: dolphin: I hit the following patch in my bisection, and the hang is also dependent on kconfig
> > 17:56 tsa : first bad commit: [d3921cb8be29ce5668c64e23ffdaeec5f8c69399] mm: fix initialization of struct page for holes in
> > memory layout
> > 17:57 tsa : couldn't reproduce on older CI kconfig, current one does it
> > https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/blob/master/kconfig/debug
> >
> > Here's a boot dmesg from some affected machines from just before the merge
> > with rc5:
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.html
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bsw-cyan/boot.html
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bdw-samus/boot.html
>
> Is there any way to get early console from these machines?
12:16 tsa : none of those have good hook for serial
Nothing on the console and no serial console option, and panics before
netconsole.
Maybe some early_printk and boot_delay if you think there's something to
see with those, but I'll have to ask Tomi nicely tomorrow.
-Chris
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 20:49 ` Linus Torvalds
@ 2021-01-25 21:33 ` Mike Rapoport
2021-01-25 21:46 ` Chris Wilson
2021-02-04 18:19 ` Mike Rapoport
1 sibling, 1 reply; 20+ messages in thread
From: Mike Rapoport @ 2021-01-25 21:33 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Chris Wilson, Andrew Morton, Linux Kernel Mailing List
On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <[email protected]> wrote:
> >
> > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > Mike Rapoport (3):
> > ...
> > > mm: fix initialization of struct page for holes in memory layout
> >
> > We have half a dozen or so different machines in CI that are silently
> > failing to boot, that we believe is bisected to this patch.
>
> That commit reverts cleanly - so if you can verify that reverting it
> fixes your CI machines, I think that that's the right thing to do for
> now, unless Mike can figure out some obvious "Duh!" moment from your
> working dmesg.
Unfortunately not, at least at 11pm :(
Maybe tomorrow I'll have something smarter to say.
> Mike: should we perhaps revert the first patch too (commit
> bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
I wonder, maybe actually this one is causing troubles?
Chris, would it be possible to check what happens if you revert only
bde9cfa3afe4?
> Linus
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:33 ` Mike Rapoport
@ 2021-01-25 21:46 ` Chris Wilson
2021-01-26 9:33 ` Chris Wilson
2021-01-26 16:24 ` Mike Rapoport
0 siblings, 2 replies; 20+ messages in thread
From: Chris Wilson @ 2021-01-25 21:46 UTC (permalink / raw)
To: Linus Torvalds, Mike Rapoport; +Cc: Andrew Morton, Linux Kernel Mailing List
Quoting Mike Rapoport (2021-01-25 21:33:48)
> On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <[email protected]> wrote:
> > >
> > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > Mike Rapoport (3):
> > > ...
> > > > mm: fix initialization of struct page for holes in memory layout
> > >
> > > We have half a dozen or so different machines in CI that are silently
> > > failing to boot, that we believe is bisected to this patch.
> >
> > That commit reverts cleanly - so if you can verify that reverting it
> > fixes your CI machines, I think that that's the right thing to do for
> > now, unless Mike can figure out some obvious "Duh!" moment from your
> > working dmesg.
>
> Unfortunately not, at least at 11pm :(
> Maybe tomorrow I'll have something smarter to say.
CI does confirm that the revert of d3921cb8be29 brings the machines back
to life.
> > Mike: should we perhaps revert the first patch too (commit
> > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
>
> I wonder, maybe actually this one is causing troubles?
>
> Chris, would it be possible to check what happens if you revert only
> bde9cfa3afe4?
Queued for CI, will be run in about an hour.
-Chris
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:46 ` Chris Wilson
@ 2021-01-26 9:33 ` Chris Wilson
2021-01-26 16:24 ` Mike Rapoport
1 sibling, 0 replies; 20+ messages in thread
From: Chris Wilson @ 2021-01-26 9:33 UTC (permalink / raw)
To: Linus Torvalds, Mike Rapoport; +Cc: Andrew Morton, Linux Kernel Mailing List
Quoting Chris Wilson (2021-01-25 21:46:19)
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
> >
> > I wonder, maybe actually this one is causing troubles?
> >
> > Chris, would it be possible to check what happens if you revert only
> > bde9cfa3afe4?
>
> Queued for CI, will be run in about an hour.
I ran just the revert of bde9cfa3afe4 through CI twice, on both occasions
all machines failed to boot.
-Chris
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:46 ` Chris Wilson
2021-01-26 9:33 ` Chris Wilson
@ 2021-01-26 16:24 ` Mike Rapoport
2021-01-26 18:45 ` Linus Torvalds
1 sibling, 1 reply; 20+ messages in thread
From: Mike Rapoport @ 2021-01-26 16:24 UTC (permalink / raw)
To: Chris Wilson; +Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List
On Mon, Jan 25, 2021 at 09:46:19PM +0000, Chris Wilson wrote:
> Quoting Mike Rapoport (2021-01-25 21:33:48)
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > > On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <[email protected]> wrote:
> > > >
> > > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > > Mike Rapoport (3):
> > > > ...
> > > > > mm: fix initialization of struct page for holes in memory layout
> > > >
> > > > We have half a dozen or so different machines in CI that are silently
> > > > failing to boot, that we believe is bisected to this patch.
> > >
> > > That commit reverts cleanly - so if you can verify that reverting it
> > > fixes your CI machines, I think that that's the right thing to do for
> > > now, unless Mike can figure out some obvious "Duh!" moment from your
> > > working dmesg.
> >
> > Unfortunately not, at least at 11pm :(
> > Maybe tomorrow I'll have something smarter to say.
>
> CI does confirm that the revert of d3921cb8be29 brings the machines back
> to life.
I still cannot see what could possibly go wrong, so let's revert
d3921cb8be29 for now and I'll continue to work with Chris to debug this.
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
This change should be quite innocuous, we anyway never allocate pfn 0 but
treat 0 as memory start in many places.
> > I wonder, maybe actually this one is causing troubles?
> >
> > Chris, would it be possible to check what happens if you revert only
> > bde9cfa3afe4?
>
> Queued for CI, will be run in about an hour.
> -Chris
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:13 ` Chris Wilson
@ 2021-01-26 16:37 ` Mike Rapoport
2021-01-28 21:00 ` Pavel Machek
1 sibling, 0 replies; 20+ messages in thread
From: Mike Rapoport @ 2021-01-26 16:37 UTC (permalink / raw)
To: Chris Wilson; +Cc: Linus Torvalds, Andrew Morton, Linux Kernel Mailing List
On Mon, Jan 25, 2021 at 09:13:59PM +0000, Chris Wilson wrote:
> Quoting Mike Rapoport (2021-01-25 21:04:56)
> > On Mon, Jan 25, 2021 at 08:34:34PM +0000, Chris Wilson wrote:
> > > Quoting Linus Torvalds (2021-01-25 01:06:40)
> > > > Mike Rapoport (3):
> > > ...
> > > > mm: fix initialization of struct page for holes in memory layout
> > >
> > > We have half a dozen or so different machines in CI that are silently
> > > failing to boot, that we believe is bisected to this patch.
> > >
> > > 17:56 tsa : ickle: dolphin: I hit the following patch in my bisection, and the hang is also dependent on kconfig
> > > 17:56 tsa : first bad commit: [d3921cb8be29ce5668c64e23ffdaeec5f8c69399] mm: fix initialization of struct page for holes in
> > > memory layout
> > > 17:57 tsa : couldn't reproduce on older CI kconfig, current one does it
> > > https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/blob/master/kconfig/debug
> > >
> > > Here's a boot dmesg from some affected machines from just before the merge
> > > with rc5:
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.html
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bsw-cyan/boot.html
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bdw-samus/boot.html
> >
> > Is there any way to get early console from these machines?
>
> 12:16 tsa : none of those have good hook for serial
>
> Nothing on the console and no serial console option, and panics before
> netconsole.
>
> Maybe some early_printk and boot_delay if you think there's something to
> see with those, but I'll have to ask Tomi nicely tomorrow.
I think there could be an early panic at some point of mm initialization.
So if it was possible to see early printks somehow that would have been
helpful.
> -Chris
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-26 16:24 ` Mike Rapoport
@ 2021-01-26 18:45 ` Linus Torvalds
2021-01-27 9:38 ` Greg KH
0 siblings, 1 reply; 20+ messages in thread
From: Linus Torvalds @ 2021-01-26 18:45 UTC (permalink / raw)
To: Mike Rapoport, stable
Cc: Chris Wilson, Andrew Morton, Linux Kernel Mailing List
On Tue, Jan 26, 2021 at 8:25 AM Mike Rapoport <[email protected]> wrote:
>
> On Mon, Jan 25, 2021 at 09:46:19PM +0000, Chris Wilson wrote:
> >
> > CI does confirm that the revert of d3921cb8be29 brings the machines back
> > to life.
>
> I still cannot see what could possibly go wrong, so let's revert
> d3921cb8be29 for now and I'll continue to work with Chris to debug this.
Ok, reverted in my tree.
And added stable to the cc, so that they know not to pick up that
commit d3921cb8be29, despite it being marked for stable.
Linus
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-26 18:45 ` Linus Torvalds
@ 2021-01-27 9:38 ` Greg KH
0 siblings, 0 replies; 20+ messages in thread
From: Greg KH @ 2021-01-27 9:38 UTC (permalink / raw)
To: Linus Torvalds
Cc: Mike Rapoport, stable, Chris Wilson, Andrew Morton,
Linux Kernel Mailing List
On Tue, Jan 26, 2021 at 10:45:10AM -0800, Linus Torvalds wrote:
> On Tue, Jan 26, 2021 at 8:25 AM Mike Rapoport <[email protected]> wrote:
> >
> > On Mon, Jan 25, 2021 at 09:46:19PM +0000, Chris Wilson wrote:
> > >
> > > CI does confirm that the revert of d3921cb8be29 brings the machines back
> > > to life.
> >
> > I still cannot see what could possibly go wrong, so let's revert
> > d3921cb8be29 for now and I'll continue to work with Chris to debug this.
>
> Ok, reverted in my tree.
>
> And added stable to the cc, so that they know not to pick up that
> commit d3921cb8be29, despite it being marked for stable.
I've dropped it from the 5.10.y queue now, thanks for letting me know.
greg k-h
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 21:13 ` Chris Wilson
2021-01-26 16:37 ` Mike Rapoport
@ 2021-01-28 21:00 ` Pavel Machek
1 sibling, 0 replies; 20+ messages in thread
From: Pavel Machek @ 2021-01-28 21:00 UTC (permalink / raw)
To: Chris Wilson
Cc: Mike Rapoport, Linus Torvalds, Andrew Morton, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi!
/-/blob/master/kconfig/debug
> > >
> > > Here's a boot dmesg from some affected machines from just before the merge
> > > with rc5:
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/shard-skl1/boot18.txt
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-skl-6600u/boot.html
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bsw-cyan/boot.html
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9676/fi-bdw-samus/boot.html
> >
> > Is there any way to get early console from these machines?
>
> 12:16 tsa : none of those have good hook for serial
>
> Nothing on the console and no serial console option, and panics before
> netconsole.
In some experiments I was successful with console=ttyUSB kind of
setup...
...and I kind of wonder if we should work on getting it workig on more
machines, at that seems to be only reasonable way.
Umm...
Actually, we still have VGA and can put console on that, no?
early_printk option should really work quite early on PC.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-01-25 20:49 ` Linus Torvalds
2021-01-25 21:33 ` Mike Rapoport
@ 2021-02-04 18:19 ` Mike Rapoport
2021-02-04 18:32 ` Linus Torvalds
1 sibling, 1 reply; 20+ messages in thread
From: Mike Rapoport @ 2021-02-04 18:19 UTC (permalink / raw)
To: Linus Torvalds
Cc: Chris Wilson, Andrew Morton, Linux Kernel Mailing List, stable
On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> On Mon, Jan 25, 2021 at 12:35 PM Chris Wilson <[email protected]> wrote:
>
> Mike: should we perhaps revert the first patch too (commit
> bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
Unfortunately, I was too optimistic and didn't take into account that this
commit changes the way /dev/mem sees the first page of memory.
There were reports of slackware users about issues with lilo after upgrade
from 5.10.11 to 5.10.12
https://www.linuxquestions.org/questions/slackware-14/slackware-current-lilo-vesa-warnings-after-recent-updates-4175689617/#post6214439
The root cause is that lilo is no longer able to access the first memory
page via /dev/mem because its type was changed from E820_TYPE_RESERVED to
E820_TYPE_RAM, so this became a part of the "System RAM" resource and
devmem_is_allowed() considers it disallowed area.
So here's the revert of bde9cfa3afe4 as well.
From a7fdc4117010d393dd77b99da5b573a5c98453ce Mon Sep 17 00:00:00 2001
From: Mike Rapoport <[email protected]>
Date: Thu, 4 Feb 2021 20:12:37 +0200
Subject: [PATCH] Revert "x86/setup: don't remove E820_TYPE_RAM for pfn 0"
This reverts commit bde9cfa3afe4324ec251e4af80ebf9b7afaf7afe.
Changing the first memory page type from E820_TYPE_RESERVED to
E820_TYPE_RAM makes it a part of "System RAM" resource rather than a
reserved resource and this in turn causes devmem_is_allowed() to treat is
as area that can be accessed but it is filled with zeroes instead of the
actual data as previously.
The change in /dev/mem output causes lilo to fail as was reported at
slakware users forum [1], and probably other legacy applications will
experience similar problems.
[1] https://www.linuxquestions.org/questions/slackware-14/slackware-current-lilo-vesa-warnings-after-recent-updates-4175689617/#post6214439
Signed-off-by: Mike Rapoport <[email protected]>
---
arch/x86/kernel/setup.c | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 3412c4595efd..740f3bdb3f61 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -660,6 +660,17 @@ static void __init trim_platform_memory_ranges(void)
static void __init trim_bios_range(void)
{
+ /*
+ * A special case is the first 4Kb of memory;
+ * This is a BIOS owned area, not kernel ram, but generally
+ * not listed as such in the E820 table.
+ *
+ * This typically reserves additional memory (64KiB by default)
+ * since some BIOSes are known to corrupt low memory. See the
+ * Kconfig help text for X86_RESERVE_LOW.
+ */
+ e820__range_update(0, PAGE_SIZE, E820_TYPE_RAM, E820_TYPE_RESERVED);
+
/*
* special case: Some BIOSes report the PC BIOS
* area (640Kb -> 1Mb) as RAM even though it is not.
@@ -717,15 +728,6 @@ early_param("reservelow", parse_reservelow);
static void __init trim_low_memory_range(void)
{
- /*
- * A special case is the first 4Kb of memory;
- * This is a BIOS owned area, not kernel ram, but generally
- * not listed as such in the E820 table.
- *
- * This typically reserves additional memory (64KiB by default)
- * since some BIOSes are known to corrupt low memory. See the
- * Kconfig help text for X86_RESERVE_LOW.
- */
memblock_reserve(0, ALIGN(reserve_low, PAGE_SIZE));
}
--
2.29.2
> Linus
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-02-04 18:19 ` Mike Rapoport
@ 2021-02-04 18:32 ` Linus Torvalds
2021-02-05 6:54 ` Greg KH
0 siblings, 1 reply; 20+ messages in thread
From: Linus Torvalds @ 2021-02-04 18:32 UTC (permalink / raw)
To: Mike Rapoport
Cc: Chris Wilson, Andrew Morton, Linux Kernel Mailing List, stable
On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport <[email protected]> wrote:
>
> On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> >
> > Mike: should we perhaps revert the first patch too (commit
> > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
>
> Unfortunately, I was too optimistic and didn't take into account that this
> commit changes the way /dev/mem sees the first page of memory.
>
> There were reports of slackware users about issues with lilo after upgrade
> from 5.10.11 to 5.10.12
Ok, applied to mainline.
Greg & stable people - this is now commit 5c279c4cf206 ("Revert
"x86/setup: don't remove E820_TYPE_RAM for pfn 0"") in my tree.
Although maybe you just want to revert the commit in stable, rather
than take it from upstream? Same difference.
Linus
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: Linux 5.11-rc5
2021-02-04 18:32 ` Linus Torvalds
@ 2021-02-05 6:54 ` Greg KH
0 siblings, 0 replies; 20+ messages in thread
From: Greg KH @ 2021-02-05 6:54 UTC (permalink / raw)
To: Linus Torvalds
Cc: Mike Rapoport, Chris Wilson, Andrew Morton,
Linux Kernel Mailing List, stable
On Thu, Feb 04, 2021 at 10:32:56AM -0800, Linus Torvalds wrote:
> On Thu, Feb 4, 2021 at 10:19 AM Mike Rapoport <[email protected]> wrote:
> >
> > On Mon, Jan 25, 2021 at 12:49:39PM -0800, Linus Torvalds wrote:
> > >
> > > Mike: should we perhaps revert the first patch too (commit
> > > bde9cfa3afe4: "x86/setup: don't remove E820_TYPE_RAM for pfn 0")?
> >
> > Unfortunately, I was too optimistic and didn't take into account that this
> > commit changes the way /dev/mem sees the first page of memory.
> >
> > There were reports of slackware users about issues with lilo after upgrade
> > from 5.10.11 to 5.10.12
>
> Ok, applied to mainline.
>
> Greg & stable people - this is now commit 5c279c4cf206 ("Revert
> "x86/setup: don't remove E820_TYPE_RAM for pfn 0"") in my tree.
> Although maybe you just want to revert the commit in stable, rather
> than take it from upstream? Same difference.
Taking it from upstream makes it easier to track over time what happend.
I've queued it up now, thanks!
greg k-h
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, back to index
Thread overview: 20+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-25 1:06 Linux 5.11-rc5 Linus Torvalds
2021-01-25 3:48 ` Guenter Roeck
2021-01-25 3:56 ` Bhaskar Chowdhury
2021-01-25 4:06 ` Guenter Roeck
2021-01-25 4:11 ` Bhaskar Chowdhury
2021-01-25 20:34 ` Chris Wilson
2021-01-25 20:49 ` Linus Torvalds
2021-01-25 21:33 ` Mike Rapoport
2021-01-25 21:46 ` Chris Wilson
2021-01-26 9:33 ` Chris Wilson
2021-01-26 16:24 ` Mike Rapoport
2021-01-26 18:45 ` Linus Torvalds
2021-01-27 9:38 ` Greg KH
2021-02-04 18:19 ` Mike Rapoport
2021-02-04 18:32 ` Linus Torvalds
2021-02-05 6:54 ` Greg KH
2021-01-25 21:04 ` Mike Rapoport
2021-01-25 21:13 ` Chris Wilson
2021-01-26 16:37 ` Mike Rapoport
2021-01-28 21:00 ` Pavel Machek
LKML Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git
git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git
git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
[email protected]
public-inbox-index lkml
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git
