5.4.93-rc1 review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 5.4.93-rc1 review
This is the start of the stable review cycle for the 5.4.93 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 27 Jan 2021 18:31:44 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.93-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.4.93-rc1
Enke Chen <[email protected]>
tcp: fix TCP_USER_TIMEOUT with zero window
Eric Dumazet <[email protected]>
tcp: do not mess with cloned skbs in tcp_add_backlog()
Dan Carpenter <[email protected]>
net: dsa: b53: fix an off by one in checking "vlan->vid"
Tariq Toukan <[email protected]>
net: Disable NETIF_F_HW_TLS_RX when RXCSUM is disabled
Vladimir Oltean <[email protected]>
net: mscc: ocelot: allow offloading of bridge on top of LAG
Matteo Croce <[email protected]>
ipv6: set multicast flag on the multicast route
Eric Dumazet <[email protected]>
net_sched: reject silly cell_log in qdisc_get_rtab()
Eric Dumazet <[email protected]>
net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
Matteo Croce <[email protected]>
ipv6: create multicast route with RTPROT_KERNEL
Guillaume Nault <[email protected]>
udp: mask TOS bits in udp_v4_early_demux()
Lecopzer Chen <[email protected]>
kasan: fix incorrect arguments passing in kasan_add_zero_shadow
Lecopzer Chen <[email protected]>
kasan: fix unaligned address is unhandled in kasan_remove_zero_shadow
Alexander Lobakin <[email protected]>
skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
Pan Bian <[email protected]>
lightnvm: fix memory leak when submit fails
Geert Uytterhoeven <[email protected]>
sh_eth: Fix power down vs. is_opened flag ordering
Rasmus Villemoes <[email protected]>
net: dsa: mv88e6xxx: also read STU state in mv88e6250_g1_vtu_getnext
Necip Fazil Yildiran <[email protected]>
sh: dma: fix kconfig dependency for G2_DMA
Guillaume Nault <[email protected]>
netfilter: rpfilter: mask ecn bits before fib lookup
Yazen Ghannam <[email protected]>
x86/cpu/amd: Set __max_die_per_package on AMD
Paul Cercueil <[email protected]>
pinctrl: ingenic: Fix JZ4760 support
Rafael J. Wysocki <[email protected]>
driver core: Extend device_is_dependent()
JC Kuo <[email protected]>
xhci: tegra: Delay for disabling LFPS detector
Mathias Nyman <[email protected]>
xhci: make sure TRB is fully written before giving it to the controller
Patrik Jakobsson <[email protected]>
usb: bdc: Make bdc pci driver depend on BROKEN
Thinh Nguyen <[email protected]>
usb: udc: core: Use lock when write to soft_connect
Ryan Chen <[email protected]>
usb: gadget: aspeed: fix stop dma register setting.
Longfang Liu <[email protected]>
USB: ehci: fix an interrupt calltrace error
Eugene Korenevsky <[email protected]>
ehci: fix EHCI host controller initialization sequence
Pali Rohár <[email protected]>
serial: mvebu-uart: fix tx lost characters at power off
Wang Hui <[email protected]>
stm class: Fix module init return on allocation failure
Alexander Shishkin <[email protected]>
intel_th: pci: Add Alder Lake-P support
Andy Lutomirski <[email protected]>
x86/mmx: Use KFPU_387 for MMX string operations
Mathias Kresin <[email protected]>
irqchip/mips-cpu: Set IPI domain parent chip
Ronnie Sahlberg <[email protected]>
cifs: do not fail __smb_send_rqst if non-fatal signals are pending
Lars-Peter Clausen <[email protected]>
iio: ad5504: Fix setting power-down state
Vincent Mailhol <[email protected]>
can: peak_usb: fix use after free bugs
Vincent Mailhol <[email protected]>
can: vxcan: vxcan_xmit: fix use after free bug
Vincent Mailhol <[email protected]>
can: dev: can_restart: fix use after free bug
Hangbin Liu <[email protected]>
selftests: net: fib_tests: remove duplicate log test
Hans de Goede <[email protected]>
platform/x86: intel-vbtn: Drop HP Stream x360 Convertible PC 11 from allow-list
Wolfram Sang <[email protected]>
i2c: octeon: check correct size of maximum RECV_LEN packet
Ariel Marcovitch <[email protected]>
powerpc: Fix alignment bug within the init sections
Arnd Bergmann <[email protected]>
scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression
Billy Tsai <[email protected]>
pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting
Youling Tang <[email protected]>
powerpc: Use the common INIT_DATA_SECTION macro in vmlinux.lds.S
Ben Skeggs <[email protected]>
drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0
Ben Skeggs <[email protected]>
drm/nouveau/mmu: fix vram heap sizing
Ben Skeggs <[email protected]>
drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
Ben Skeggs <[email protected]>
drm/nouveau/privring: ack interrupts the same way as RM
Ben Skeggs <[email protected]>
drm/nouveau/bios: fix issue shadowing expansion ROMs
Wayne Lin <[email protected]>
drm/amd/display: Fix to be able to stop crc calculation
Victor Zhao <[email protected]>
drm/amdgpu/psp: fix psp gfx ctrl cmds
Sagar Shrikant Kadam <[email protected]>
riscv: defconfig: enable gpio support for HiFive Unleashed
Sagar Shrikant Kadam <[email protected]>
dts: phy: add GPIO number and active state used for phy reset
Sagar Shrikant Kadam <[email protected]>
dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
David Woodhouse <[email protected]>
x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
David Woodhouse <[email protected]>
xen: Fix event channel callback via INTX/GSI
Arnd Bergmann <[email protected]>
arm64: make atomic helpers __always_inline
Peter Geis <[email protected]>
clk: tegra30: Add hda clock default rates to clock driver
Seth Miller <[email protected]>
HID: Ignore battery for Elan touchscreen on ASUS UX550
Filipe Laíns <[email protected]>
HID: logitech-dj: add the G602 receiver
Damien Le Moal <[email protected]>
riscv: Fix sifive serial driver
Damien Le Moal <[email protected]>
riscv: Fix kernel time_init()
Ewan D. Milne <[email protected]>
scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
Nilesh Javali <[email protected]>
scsi: qedi: Correct max length of CHAP secret
Can Guo <[email protected]>
scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
Anthony Iliopoulos <[email protected]>
dm integrity: select CRYPTO_SKCIPHER
Kai-Heng Feng <[email protected]>
HID: multitouch: Enable multi-input for Synaptics pointstick/touchpad device
Cezary Rojewski <[email protected]>
ASoC: Intel: haswell: Add missing pm_ops
Chris Wilson <[email protected]>
drm/i915/gt: Prevent use of engine->wa_ctx after error
Daniel Vetter <[email protected]>
drm/syncobj: Fix use-after-free
Pan Bian <[email protected]>
drm/atomic: put state on error path
Mikulas Patocka <[email protected]>
dm integrity: fix a crash if "recalculate" used without "internal_hash"
Hannes Reinecke <[email protected]>
dm: avoid filesystem lookup in dm_get_dev_t()
Alex Leibovich <[email protected]>
mmc: sdhci-xenon: fix 1.8v regulator stabilization
Peter Collingbourne <[email protected]>
mmc: core: don't initialize block size from ext_csd if not present
Filipe Manana <[email protected]>
btrfs: send: fix invalid clone operations when cloning from the same file and root
Josef Bacik <[email protected]>
btrfs: don't clear ret in btrfs_start_dirty_block_groups
Josef Bacik <[email protected]>
btrfs: fix lockdep splat in btrfs_recover_relocation
Josef Bacik <[email protected]>
btrfs: don't get an EINTR during drop_snapshot for reloc
Hans de Goede <[email protected]>
ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
Takashi Iwai <[email protected]>
ALSA: hda/via: Add minimum mute flag
Takashi Iwai <[email protected]>
ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
Jiaxun Yang <[email protected]>
platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
Heikki Krogerus <[email protected]>
platform/x86: i2c-multi-instantiate: Don't create platform device for INT3515 ACPI nodes
Mikko Perttunen <[email protected]>
i2c: bpmp-tegra: Ignore unknown I2C_M flags
-------------
Diffstat:
Documentation/admin-guide/kernel-parameters.txt | 4 ++ Makefile | 4 +- arch/arm/xen/enlighten.c | 2 +- arch/arm64/include/asm/atomic.h | 10 +-- arch/powerpc/kernel/vmlinux.lds.S | 25 +++---- .../riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 2 + arch/riscv/configs/defconfig | 2 + arch/riscv/kernel/time.c | 3 + arch/sh/drivers/dma/Kconfig | 3 +- arch/x86/kernel/cpu/amd.c | 4 +- arch/x86/lib/mmx_32.c | 20 ++++-- arch/x86/xen/enlighten_hvm.c | 11 ++- drivers/acpi/scan.c | 2 + drivers/base/core.c | 17 ++++- drivers/clk/tegra/clk-tegra30.c | 2 + drivers/gpu/drm/amd/amdgpu/psp_gfx_if.h | 2 +- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crc.c | 2 +- drivers/gpu/drm/drm_atomic_helper.c | 2 +- drivers/gpu/drm/drm_syncobj.c | 8 ++- drivers/gpu/drm/i915/gt/intel_lrc.c | 3 + drivers/gpu/drm/nouveau/dispnv50/disp.c | 4 +- drivers/gpu/drm/nouveau/dispnv50/disp.h | 2 +- drivers/gpu/drm/nouveau/dispnv50/wimmc37b.c | 2 +- drivers/gpu/drm/nouveau/nvkm/subdev/bios/shadow.c | 2 +- drivers/gpu/drm/nouveau/nvkm/subdev/i2c/auxgm200.c | 8 +-- drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gf100.c | 10 ++- drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gk104.c | 10 ++- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/base.c | 6 +- drivers/hid/hid-ids.h | 1 + drivers/hid/hid-input.c | 2 + drivers/hid/hid-logitech-dj.c | 4 ++ drivers/hid/hid-multitouch.c | 4 ++ drivers/hwtracing/intel_th/pci.c | 5 ++ drivers/hwtracing/stm/heartbeat.c | 6 +- drivers/i2c/busses/i2c-octeon-core.c | 2 +- drivers/i2c/busses/i2c-tegra-bpmp.c | 2 +- drivers/iio/dac/ad5504.c | 4 +- drivers/irqchip/irq-mips-cpu.c | 7 ++ drivers/lightnvm/core.c | 3 +- drivers/md/Kconfig | 1 + drivers/md/dm-integrity.c | 6 ++ drivers/md/dm-table.c | 15 +++- drivers/mmc/core/queue.c | 4 +- drivers/mmc/host/sdhci-xenon.c | 7 +- drivers/net/can/dev.c | 4 +- drivers/net/can/usb/peak_usb/pcan_usb_fd.c | 8 +-- drivers/net/can/vxcan.c | 6 +- drivers/net/dsa/b53/b53_common.c | 2 +- drivers/net/dsa/mv88e6xxx/global1_vtu.c | 4 ++ drivers/net/ethernet/mscc/ocelot.c | 4 +- drivers/net/ethernet/renesas/sh_eth.c | 4 +- drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c | 2 +- drivers/pinctrl/pinctrl-ingenic.c | 24 +++---- drivers/platform/x86/i2c-multi-instantiate.c | 31 ++++++--- drivers/platform/x86/ideapad-laptop.c | 15 +++- drivers/platform/x86/intel-vbtn.c | 6 -- drivers/scsi/megaraid/megaraid_sas_base.c | 6 +- drivers/scsi/qedi/qedi_main.c | 4 +- drivers/scsi/sd.c | 4 +- drivers/scsi/ufs/ufshcd.c | 11 ++- drivers/tty/serial/mvebu-uart.c | 10 ++- drivers/tty/serial/sifive.c | 1 + drivers/usb/gadget/udc/aspeed-vhub/epn.c | 5 +- drivers/usb/gadget/udc/bdc/Kconfig | 2 +- drivers/usb/gadget/udc/core.c | 13 +++- drivers/usb/host/ehci-hcd.c | 12 ++++ drivers/usb/host/ehci-hub.c | 3 + drivers/usb/host/xhci-ring.c | 2 + drivers/usb/host/xhci-tegra.c | 7 ++ drivers/xen/events/events_base.c | 10 --- drivers/xen/platform-pci.c | 1 - drivers/xen/xenbus/xenbus.h | 1 + drivers/xen/xenbus/xenbus_comms.c | 8 --- drivers/xen/xenbus/xenbus_probe.c | 81 ++++++++++++++++++---- fs/btrfs/block-group.c | 3 +- fs/btrfs/extent-tree.c | 10 ++- fs/btrfs/send.c | 15 ++++ fs/btrfs/volumes.c | 2 + fs/cifs/transport.c | 4 +- include/asm-generic/bitops/atomic.h | 6 +- include/net/inet_connection_sock.h | 3 + include/xen/xenbus.h | 2 +- mm/kasan/init.c | 23 +++--- net/core/dev.c | 5 ++ net/core/skbuff.c | 6 +- net/ipv4/inet_connection_sock.c | 1 + net/ipv4/netfilter/ipt_rpfilter.c | 2 +- net/ipv4/tcp.c | 1 + net/ipv4/tcp_input.c | 1 + net/ipv4/tcp_ipv4.c | 25 +++---- net/ipv4/tcp_output.c | 1 + net/ipv4/tcp_timer.c | 14 ++-- net/ipv4/udp.c | 3 +- net/ipv6/addrconf.c | 3 +- net/sched/cls_tcindex.c | 8 ++- net/sched/sch_api.c | 3 +- sound/core/seq/oss/seq_oss_synth.c | 3 +- sound/pci/hda/patch_via.c | 1 + sound/soc/intel/boards/haswell.c | 1 + tools/testing/selftests/net/fib_tests.sh | 1 - 100 files changed, 469 insertions(+), 214 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/86 i2c: bpmp-tegra: Ignore unknown I2C_M flags
From: Mikko Perttunen <[email protected]>
commit bc1c2048abbe3c3074b4de91d213595c57741a6b upstream.
In order to not to start returning errors when new I2C_M flags are added, change behavior to just ignore all flags that we don't know about. This includes the I2C_M_DMA_SAFE flag that already exists but causes -EINVAL to be returned for valid transactions.
--- drivers/i2c/busses/i2c-tegra-bpmp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-tegra-bpmp.c +1 -1
@@ -80,7 +80,7 @@ static int tegra_bpmp_xlate_flags(u16 fl flags &= ~I2C_M_RECV_LEN ; } -return (flags !=0 ) ? -EINVAL :0 ; +return 0 ; }/**
Greg Kroah-Hartman
maintainerPATCH 2/86 platform/x86: i2c-multi-instantiate: Dont create platform device for INT3515 ACPI nodes
In reply to Greg Kroah-HartmanFrom: Heikki Krogerus <[email protected]>
commit 9bba96275576da0cf78ede62aeb2fc975ed8a32d upstream.
There are several reports about the tps6598x causing interrupt flood on boards with the INT3515 ACPI node, which then causes instability. There appears to be several problems with the interrupt. One problem is that the I2CSerialBus resources do not always map to the Interrupt resource with the same index, but that is not the only problem. We have not been able to come up with a solution for all the issues, and because of that disabling the device for now.
The PD controller on these platforms is autonomous, and the purpose for the driver is primarily to supply status to the userspace, so this will not affect any functionality.
--- drivers/platform/x86/i2c-multi-instantiate.c | 31 ++++++++++++++++++++------- 1 file changed, 23 insertions(+), 8 deletions(-)
drivers/platform/x86/i2c-multi-instantiate.c +23 -8
@@ -166,13 +166,29 @@ static const struct i2c_inst_data bsg215 {} }; -static const struct i2c_inst_data int3515_data[] = { - {"tps6598x" ,IRQ_RESOURCE_APIC ,0 }, - {"tps6598x" ,IRQ_RESOURCE_APIC ,1 }, - {"tps6598x" ,IRQ_RESOURCE_APIC ,2 }, - {"tps6598x" ,IRQ_RESOURCE_APIC ,3 }, - {} -}; +/* +* Device with _HID INT3515 (TI PD controllers) has some unresolved interrupt +* issues. The most common problem seen is interrupt flood. +* +* There are at least two known causes. Firstly, on some boards, the +* I2CSerialBus resource index does not match the Interrupt resource, i.e. they +* are not one-to-one mapped like in the array below. Secondly, on some boards +* the IRQ line from the PD controller is not actually connected at all. But the +* interrupt flood is also seen on some boards where those are not a problem, so +* there are some other problems as well. +* +* Because of the issues with the interrupt, the device is disabled for now. If +* you wish to debug the issues, uncomment the below, and add an entry for the +* INT3515 device to the i2c_multi_instance_ids table. +* +* static const struct i2c_inst_data int3515_data[] = { +* { "tps6598x", IRQ_RESOURCE_APIC, 0 }, +* { "tps6598x", IRQ_RESOURCE_APIC, 1 }, +* { "tps6598x", IRQ_RESOURCE_APIC, 2 }, +* { "tps6598x", IRQ_RESOURCE_APIC, 3 }, +* { } +* }; +*/ /* * Note new device-ids must also be added to i2c_multi_instantiate_ids in
@@ -181,7 +197,6 @@ static const struct i2c_inst_data int351static const struct acpi_device_id i2c_multi_inst_acpi_ids[] = { {"BSG1160" , (unsigned long )bsg1160_data }, {"BSG2150" , (unsigned long )bsg2150_data }, - {"INT3515" , (unsigned long )int3515_data }, { } };MODULE_DEVICE_TABLE (acpi, i2c_multi_inst_acpi_ids);
Greg Kroah-Hartman
maintainerPATCH 3/86 platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
In reply to Greg Kroah-HartmanFrom: Jiaxun Yang <[email protected]>
commit f419e5940f1d9892ea6f45acdaca572b9e73ff39 upstream.
Newer ideapads (e.g.: Yoga 14s, 720S 14) come with ELAN0634 touchpad do not use EC to switch touchpad.
Reading VPCCMD_R_TOUCHPAD will return zero thus touchpad may be blocked unexpectedly.
Writing VPCCMD_W_TOUCHPAD may cause a spurious key press.
Add has_touchpad_switch to workaround these machines.
--
v2: Specify touchpad to ELAN0634
v3: Stupid missing ! in v2
v4: Correct acpi_dev_present usage (Hans)
--- drivers/platform/x86/ideapad-laptop.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
drivers/platform/x86/ideapad-laptop.c +14 -1
@@ -92,6 +92,7 @@ struct ideapad_private {struct dentry *debug;unsigned long cfg;bool has_hw_rfkill_switch; +bool has_touchpad_switch;const char *fnesc_guid; };
@@ -535,7 +536,9 @@ static umode_t ideapad_is_visible(struct }else if (attr == &dev_attr_fn_lock.attr) { supported =acpi_has_method (priv->adev->handle,"HALS" ) &&acpi_has_method (priv->adev->handle,"SALS" ); - }else + }else if (attr == &dev_attr_touchpad.attr) + supported = priv->has_touchpad_switch; +else supported = true;return supported ? attr->mode :0 ;
@@ -867,6 +870,9 @@ static void ideapad_sync_touchpad_state( {unsigned long value; +if (!priv->has_touchpad_switch) +return ; +/* Without reading from EC touchpad LED doesn't switch state */ if (!read_ec_data (priv->adev->handle,VPCCMD_R_TOUCHPAD , &value)) {/* Some IdeaPads don't really turn off touchpad - they only
@@ -989,6 +995,9 @@ static int ideapad_acpi_add(struct platf priv->platform_device = pdev; priv->has_hw_rfkill_switch =dmi_check_system (hw_rfkill_list); +/* Most ideapads with ELAN0634 touchpad don't use EC touchpad switch */ + priv->has_touchpad_switch = !acpi_dev_present ("ELAN0634" ,NULL ,-1 ); + ret =ideapad_sysfs_init (priv);if (ret)return ret;
@@ -1006,6 +1015,10 @@ static int ideapad_acpi_add(struct platfif (!priv->has_hw_rfkill_switch)write_ec_cmd (priv->adev->handle,VPCCMD_W_RF ,1 ); +/* The same for Touchpad */ +if (!priv->has_touchpad_switch) +write_ec_cmd (priv->adev->handle,VPCCMD_W_TOUCHPAD ,1 ); +for (i =0 ; i <IDEAPAD_RFKILL_DEV_NUM ; i++)if (test_bit (ideapad_rfk_data[i].cfgbit, &priv->cfg))ideapad_register_rfkill (priv, i);
Greg Kroah-Hartman
maintainerPATCH 4/86 ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
commit 217bfbb8b0bfa24619b11ab75c135fec99b99b20 upstream.
snd_seq_oss_synth_make_info() didn't check the error code from snd_seq_oss_midi_make_info(), and this leads to the call of strlcpy() with the uninitialized string as the source, which may lead to the access over the limit.
Add the proper error check for avoiding the failure.
--- sound/core/seq/oss/seq_oss_synth.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
sound/core/seq/oss/seq_oss_synth.c +2 -1
@@ -611,7 +611,8 @@ snd_seq_oss_synth_make_info(struct seq_oif (info->is_midi) {struct midi_info minf; -snd_seq_oss_midi_make_info (dp, info->midi_mapped, &minf); +if (snd_seq_oss_midi_make_info (dp, info->midi_mapped, &minf)) +return -ENXIO ; inf->synth_type =SYNTH_TYPE_MIDI ; inf->synth_subtype =0 ; inf->nr_voices =16 ;
Greg Kroah-Hartman
maintainerPATCH 5/86 ALSA: hda/via: Add minimum mute flag
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
commit 67ea698c3950d10925be33c21ca49ffb64e21842 upstream.
It turned out that VIA codecs also mute the sound in the lowest mixer level. Turn on the dac_min_mute flag to indicate the mute-as-minimum in TLV like already done in Conexant and IDT codecs.
--- sound/pci/hda/patch_via.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_via.c +1 -0
@@ -113,6 +113,7 @@ static struct via_spec *via_new_spec(str spec->codec_type =VT1708S ; spec->gen.indep_hp =1 ; spec->gen.keep_eapd_on =1 ; + spec->gen.dac_min_mute =1 ; spec->gen.pcm_playback_hook = via_playback_pcm_hook; spec->gen.add_stereo_mix_input =HDA_HINT_STEREO_MIX_AUTO ; codec->power_save_node =1 ;
Greg Kroah-Hartman
maintainerPATCH 6/86 ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
commit 78a18fec5258c8df9435399a1ea022d73d3eceb9 upstream.
Set the acpi_device pointer which acpi_bus_get_device() returns-by- reference to NULL on errors.
We've recently had 2 cases where callers of acpi_bus_get_device() did not properly error check the return value, so set the returned- by-reference acpi_device pointer to NULL, because at least some callers of acpi_bus_get_device() expect that to be done on errors.
[ rjw: This issue was exposed by commit 71da201f38df ("ACPI: scan:
Defer enumeration of devices with _DEP lists") which caused it to be much more likely to occur on some systems, but the real defect had been introduced by an earlier commit. ]
--- drivers/acpi/scan.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/acpi/scan.c +2 -0
@@ -587,6 +587,8 @@ static int acpi_get_device_data(acpi_hanif (!device)return -EINVAL ; + *device =NULL ; + status =acpi_get_data_full (handle, acpi_scan_drop_device, (void **)device, callback);if (ACPI_FAILURE (status) || !*device) {
Greg Kroah-Hartman
maintainerPATCH 7/86 btrfs: dont get an EINTR during drop_snapshot for reloc
In reply to Greg Kroah-HartmanFrom: Josef Bacik <[email protected]>
commit 18d3bff411c8d46d40537483bdc0b61b33ce0371 upstream.
This was partially fixed by f3e3d9cc3525 ("btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree"), however it missed a spot when we restart a trans handle because we need to end the transaction. The fix is the same, simply use btrfs_join_transaction() instead of btrfs_start_transaction() when deleting reloc roots.
--- fs/btrfs/extent-tree.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
fs/btrfs/extent-tree.c +9 -1
@@ -5390,7 +5390,15 @@ int btrfs_drop_snapshot(struct btrfs_roo goto out_free; } - trans =btrfs_start_transaction (tree_root,0 ); +/* +* Use join to avoid potential EINTR from transaction +* start. See wait_reserve_ticket and the whole +* reservation callchain. +*/ +if (for_reloc) + trans =btrfs_join_transaction (tree_root); +else + trans =btrfs_start_transaction (tree_root,0 );if (IS_ERR (trans)) { err =PTR_ERR (trans); goto out_free;
Greg Kroah-Hartman
maintainerPATCH 8/86 btrfs: fix lockdep splat in btrfs_recover_relocation
In reply to Greg Kroah-HartmanFrom: Josef Bacik <[email protected]>
commit fb286100974e7239af243bc2255a52f29442f9c8 upstream.
While testing the error paths of relocation I hit the following lockdep splat:
======================================================
WARNING: possible circular locking dependency detected
5.10.0-rc6+ #217 Not tainted
------------------------------------------------------
mount/779 is trying to acquire lock:
ffffa0e676945418 (&fs_info->balance_mutex){+.+.}-{3:3}, at: btrfs_recover_balance+0x2f0/0x340
but task is already holding lock:
ffffa0e60ee31da8 (btrfs-root-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x27/0x100
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (btrfs-root-00){++++}-{3:3}:
down_read_nested+0x43/0x130 __btrfs_tree_read_lock+0x27/0x100 btrfs_read_lock_root_node+0x31/0x40 btrfs_search_slot+0x462/0x8f0 btrfs_update_root+0x55/0x2b0 btrfs_drop_snapshot+0x398/0x750 clean_dirty_subvols+0xdf/0x120 btrfs_recover_relocation+0x534/0x5a0 btrfs_start_pre_rw_mount+0xcb/0x170 open_ctree+0x151f/0x1726 btrfs_mount_root.cold+0x12/0xea legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 vfs_kern_mount.part.0+0x71/0xb0 btrfs_mount+0x10d/0x380 legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 path_mount+0x433/0xc10 __x64_sys_mount+0xe3/0x120 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9
-> #1 (sb_internal#2){.+.+}-{0:0}:
start_transaction+0x444/0x700 insert_balance_item.isra.0+0x37/0x320 btrfs_balance+0x354/0xf40 btrfs_ioctl_balance+0x2cf/0x380 __x64_sys_ioctl+0x83/0xb0 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9
-> #0 (&fs_info->balance_mutex){+.+.}-{3:3}:
__lock_acquire+0x1120/0x1e10 lock_acquire+0x116/0x370 __mutex_lock+0x7e/0x7b0 btrfs_recover_balance+0x2f0/0x340 open_ctree+0x1095/0x1726 btrfs_mount_root.cold+0x12/0xea legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 vfs_kern_mount.part.0+0x71/0xb0 btrfs_mount+0x10d/0x380 legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 path_mount+0x433/0xc10 __x64_sys_mount+0xe3/0x120 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9
other info that might help us debug this:
Chain exists of:
&fs_info->balance_mutex --> sb_internal#2 --> btrfs-root-00
Possible unsafe locking scenario: CPU0 CPU1
---- ----
lock(btrfs-root-00);
lock(sb_internal#2);
lock(btrfs-root-00);
lock(&fs_info->balance_mutex);*** DEADLOCK ***
2 locks held by mount/779:
#0: ffffa0e60dc040e0 (&type->s_umount_key#47/1){+.+.}-{3:3}, at: alloc_super+0xb5/0x380 #1: ffffa0e60ee31da8 (btrfs-root-00){++++}-{3:3}, at: __btrfs_tree_read_lock+0x27/0x100
stack backtrace: CPU: 0 PID: 779 Comm: mount Not tainted 5.10.0-rc6+ #217 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014 Call Trace: dump_stack+0x8b/0xb0 check_noncircular+0xcf/0xf0 ? trace_call_bpf+0x139/0x260 __lock_acquire+0x1120/0x1e10 lock_acquire+0x116/0x370 ? btrfs_recover_balance+0x2f0/0x340 __mutex_lock+0x7e/0x7b0 ? btrfs_recover_balance+0x2f0/0x340 ? btrfs_recover_balance+0x2f0/0x340 ? rcu_read_lock_sched_held+0x3f/0x80 ? kmem_cache_alloc_trace+0x2c4/0x2f0 ? btrfs_get_64+0x5e/0x100 btrfs_recover_balance+0x2f0/0x340 open_ctree+0x1095/0x1726 btrfs_mount_root.cold+0x12/0xea ? rcu_read_lock_sched_held+0x3f/0x80 legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 vfs_kern_mount.part.0+0x71/0xb0 btrfs_mount+0x10d/0x380 ? __kmalloc_track_caller+0x2f2/0x320 legacy_get_tree+0x30/0x50 vfs_get_tree+0x28/0xc0 ? capable+0x3a/0x60 path_mount+0x433/0xc10 __x64_sys_mount+0xe3/0x120 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9
This is straightforward to fix, simply release the path before we setup the balance_ctl.
--- fs/btrfs/volumes.c | 2 ++ 1 file changed, 2 insertions(+)
fs/btrfs/volumes.c +2 -0
@@ -4409,6 +4409,8 @@ int btrfs_recover_balance(struct btrfs_fbtrfs_warn (fs_info,"balance: cannot set exclusive op status, resume manually" ); +btrfs_release_path (path); +mutex_lock (&fs_info->balance_mutex);BUG_ON (fs_info->balance_ctl);spin_lock (&fs_info->balance_lock);
Greg Kroah-Hartman
maintainerPATCH 9/86 btrfs: dont clear ret in btrfs_start_dirty_block_groups
In reply to Greg Kroah-HartmanFrom: Josef Bacik <[email protected]>
commit 34d1eb0e599875064955a74712f08ff14c8e3d5f upstream.
If we fail to update a block group item in the loop we'll break, however we'll do btrfs_run_delayed_refs and lose our error value in ret, and thus not clean up properly. Fix this by only running the delayed refs if there was no failure.
--- fs/btrfs/block-group.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/btrfs/block-group.c +2 -1
@@ -2497,7 +2497,8 @@ again:* Go through delayed refs for all the stuff we've just kicked off * and then loop back (just once) */ - ret =btrfs_run_delayed_refs (trans,0 ); +if (!ret) + ret =btrfs_run_delayed_refs (trans,0 );if (!ret && loops ==0 ) { loops++;spin_lock (&cur_trans->dirty_bgs_lock);
Greg Kroah-Hartman
maintainerPATCH 10/86 btrfs: send: fix invalid clone operations when cloning from the same file and root
In reply to Greg Kroah-HartmanFrom: Filipe Manana <[email protected]>
commit 518837e65068c385dddc0a87b3e577c8be7c13b1 upstream.
When an incremental send finds an extent that is shared, it checks which file extent items in the range refer to that extent, and for those it emits clone operations, while for others it emits regular write operations to avoid corruption at the destination (as described and fixed by commit d906d49fc5f4 ("Btrfs: send, fix file corruption due to incorrect cloning operations")).
However when the root we are cloning from is the send root, we are cloning from the inode currently being processed and the source file range has several extent items that partially point to the desired extent, with an offset smaller than the offset in the file extent item for the range we want to clone into, it can cause the algorithm to issue a clone operation that starts at the current eof of the file being processed in the receiver side, in which case the receiver will fail, with EINVAL, when attempting to execute the clone operation.
Example reproducer:
$ cat test-send-clone.sh #!/bin/bash
DEV=/dev/sdi
MNT=/mnt/sdi
mkfs.btrfs -f $DEV >/dev/null
mount $DEV $MNT
# Create our test file with a single and large extent (1M) and with
# different content for different file ranges that will be reflinked
# later.
xfs_io -f \
-c "pwrite -S 0xab 0 128K" \
-c "pwrite -S 0xcd 128K 128K" \
-c "pwrite -S 0xef 256K 256K" \
-c "pwrite -S 0x1a 512K 512K" \
$MNT/foobar btrfs subvolume snapshot -r $MNT $MNT/snap1
btrfs send -f /tmp/snap1.send $MNT/snap1
# Now do a series of changes to our file such that we end up with
# different parts of the extent reflinked into different file offsets
# and we overwrite a large part of the extent too, so no file extent
# items refer to that part that was overwritten. This used to confuse
# the algorithm used by the kernel to figure out which file ranges to
# clone, making it attempt to clone from a source range starting at
# the current eof of the file, resulting in the receiver to fail since
# it is an invalid clone operation.
#
xfs_io -c "reflink $MNT/foobar 64K 1M 960K" \
-c "reflink $MNT/foobar 0K 512K 256K" \
-c "reflink $MNT/foobar 512K 128K 256K" \
-c "pwrite -S 0x73 384K 640K" \
$MNT/foobar btrfs subvolume snapshot -r $MNT $MNT/snap2 btrfs send -f /tmp/snap2.send -p $MNT/snap1 $MNT/snap2
echo -e "\nFile digest in the original filesystem:" md5sum $MNT/snap2/foobar
# Now unmount the filesystem, create a new one, mount it and try to
# apply both send streams to recreate both snapshots. umount $DEV
mkfs.btrfs -f $DEV >/dev/null
mount $DEV $MNT
btrfs receive -f /tmp/snap1.send $MNT
btrfs receive -f /tmp/snap2.send $MNT
# Must match what we got in the original filesystem of course. echo -e "\nFile digest in the new filesystem:" md5sum $MNT/snap2/foobar
umount $MNT
When running the reproducer, the incremental send operation fails due to an invalid clone operation:
$ ./test-send-clone.sh wrote 131072/131072 bytes at offset 0 128 KiB, 32 ops; 0.0015 sec (80.906 MiB/sec and 20711.9741 ops/sec) wrote 131072/131072 bytes at offset 131072 128 KiB, 32 ops; 0.0013 sec (90.514 MiB/sec and 23171.6148 ops/sec) wrote 262144/262144 bytes at offset 262144 256 KiB, 64 ops; 0.0025 sec (98.270 MiB/sec and 25157.2327 ops/sec) wrote 524288/524288 bytes at offset 524288 512 KiB, 128 ops; 0.0052 sec (95.730 MiB/sec and 24506.9883 ops/sec) Create a readonly snapshot of '/mnt/sdi' in '/mnt/sdi/snap1' At subvol /mnt/sdi/snap1 linked 983040/983040 bytes at offset 1048576 960 KiB, 1 ops; 0.0006 sec (1.419 GiB/sec and 1550.3876 ops/sec) linked 262144/262144 bytes at offset 524288 256 KiB, 1 ops; 0.0020 sec (120.192 MiB/sec and 480.7692 ops/sec) linked 262144/262144 bytes at offset 131072 256 KiB, 1 ops; 0.0018 sec (133.833 MiB/sec and 535.3319 ops/sec) wrote 655360/655360 bytes at offset 393216 640 KiB, 160 ops; 0.0093 sec (66.781 MiB/sec and 17095.8436 ops/sec) Create a readonly snapshot of '/mnt/sdi' in '/mnt/sdi/snap2' At subvol /mnt/sdi/snap2
File digest in the original filesystem:
9c13c61cb0b9f5abf45344375cb04dfa /mnt/sdi/snap2/foobar At subvol snap1
At snapshot snap2
ERROR: failed to clone extents to foobar: Invalid argument
File digest in the new filesystem:
132f0396da8f48d2e667196bff882cfc /mnt/sdi/snap2/foobar
The clone operation is invalid because its source range starts at the current eof of the file in the receiver, causing the receiver to get an EINVAL error from the clone operation when attempting it.
For the example above, what happens is the following:
1) When processing the extent at file offset 1M, the algorithm checks that the extent is shared and can be (fully or partially) found at file offset 0.
At this point the file has a size (and eof) of 1M at the receiver;
2) It finds that our extent item at file offset 1M has a data offset of 64K and, since the file extent item at file offset 0 has a data offset of 0, it issues a clone operation, from the same file and root, that has a source range offset of 64K, destination offset of 1M and a length of 64K, since the extent item at file offset 0 refers only to the first 128K of the shared extent.
After this clone operation, the file size (and eof) at the receiver is increased from 1M to 1088K (1M + 64K);
3) Now there's still 896K (960K - 64K) of data left to clone or write, so it checks for the next file extent item, which starts at file offset 128K. This file extent item has a data offset of 0 and a length of 256K, so a clone operation with a source range offset of 256K, a destination offset of 1088K (1M + 64K) and length of 128K is issued.
After this operation the file size (and eof) at the receiver increases from 1088K to 1216K (1088K + 128K);
4) Now there's still 768K (896K - 128K) of data left to clone or write, so it checks for the next file extent item, located at file offset 384K. This file extent item points to a different extent, not the one we want to clone, with a length of 640K. So we issue a write operation into the file range 1216K (1088K + 128K, end of the last clone operation), with a length of 640K and with a data matching the one we can find for that range in send root.
After this operation, the file size (and eof) at the receiver increases from 1216K to 1856K (1216K + 640K);
5) Now there's still 128K (768K - 640K) of data left to clone or write, so we look into the file extent item, which is for file offset 1M and it points to the extent we want to clone, with a data offset of 64K and a length of 960K.
However this matches the file offset we started with, the start of the range to clone into. So we can't for sure find any file extent item from here onwards with the rest of the data we want to clone, yet we proceed and since the file extent item points to the shared extent, with a data offset of 64K, we issue a clone operation with a source range starting at file offset 1856K, which matches the file extent item's offset, 1M, plus the amount of data cloned and written so far, which is 64K (step 2) + 128K (step 3) + 640K (step 4). This clone operation is invalid since the source range offset matches the current eof of the file in the receiver. We should have stopped looking for extents to clone at this point and instead fallback to write, which would simply the contain the data in the file range from 1856K to 1856K + 128K.
So fix this by stopping the loop that looks for file ranges to clone at clone_range() when we reach the current eof of the file being processed, if we are cloning from the same file and using the send root as the clone root. This ensures any data not yet cloned will be sent to the receiver through a write operation.
A test case for fstests will follow soon.
--- fs/btrfs/send.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
fs/btrfs/send.c +15 -0
@@ -5519,6 +5519,21 @@ static int clone_range(struct send_ctx *break ; offset += clone_len; clone_root->offset += clone_len; + +/* +* If we are cloning from the file we are currently processing, +* and using the send root as the clone root, we must stop once +* the current clone offset reaches the current eof of the file +* at the receiver, otherwise we would issue an invalid clone +* operation (source range going beyond eof) and cause the +* receiver to fail. So if we reach the current eof, bail out +* and fallback to a regular write. +*/ +if (clone_root->root == sctx->send_root && + clone_root->ino == sctx->cur_ino && + clone_root->offset >= sctx->cur_inode_next_write_offset) +break ; + data_offset += clone_len; next: path->slots[0 ]++;
Greg Kroah-Hartman
maintainerPATCH 11/86 mmc: core: dont initialize block size from ext_csd if not present
In reply to Greg Kroah-HartmanFrom: Peter Collingbourne <[email protected]>
commit b503087445ce7e45fabdee87ca9e460d5b5b5168 upstream.
If extended CSD was not available, the eMMC driver would incorrectly set the block size to 0, as the data_sector_size field of ext_csd was never initialized. This issue was exposed by commit 817046ecddbc ("block: Align max_hw_sectors to logical blocksize") which caused max_sectors and max_hw_sectors to be set to 0 after setting the block size to 0, resulting in a kernel panic in bio_split when attempting to read from the device. Fix it by only reading the block size from ext_csd if it is available.
--- drivers/mmc/core/queue.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/mmc/core/queue.c +3 -1
@@ -370,8 +370,10 @@ static void mmc_setup_queue(struct mmc_q "merging was advertised but not possible");blk_queue_max_segments (mq->queue,mmc_get_max_segments (host)); -if (mmc_card_mmc (card)) +if (mmc_card_mmc (card) && card->ext_csd.data_sector_size) { block_size = card->ext_csd.data_sector_size; +WARN_ON (block_size !=512 && block_size !=4096 ); + }blk_queue_logical_block_size (mq->queue, block_size);/*
Greg Kroah-Hartman
maintainerPATCH 12/86 mmc: sdhci-xenon: fix 1.8v regulator stabilization
In reply to Greg Kroah-HartmanFrom: Alex Leibovich <[email protected]>
commit 1a3ed0dc3594d99ff341ec63865a40519ea24b8d upstream.
Automatic Clock Gating is a feature used for the power consumption optimisation. It turned out that during early init phase it may prevent the stable voltage switch to 1.8V - due to that on some platforms an endless printout in dmesg can be observed: "mmc1: 1.8V regulator output did not became stable" Fix the problem by disabling the ACG at very beginning of the sdhci_init and let that be enabled later.
--- drivers/mmc/host/sdhci-xenon.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/mmc/host/sdhci-xenon.c +6 -1
@@ -167,7 +167,12 @@ static void xenon_reset_exit(struct sdhc/* Disable tuning request and auto-retuning again */ xenon_retune_setup (host); -xenon_set_acg (host, true); +/* +* The ACG should be turned off at the early init time, in order +* to solve a possible issues with the 1.8V regulator stabilization. +* The feature is enabled in later stage. +*/ +xenon_set_acg (host, false);xenon_set_sdclk_off_idle (host, sdhc_id, false);
Greg Kroah-Hartman
maintainerPATCH 13/86 dm: avoid filesystem lookup in dm_get_dev_t()
In reply to Greg Kroah-HartmanFrom: Hannes Reinecke <[email protected]>
commit 809b1e4945774c9ec5619a8f4e2189b7b3833c0c upstream.
This reverts commit644bda6f3460 ("dm table: fall back to getting device using name_to_dev_t()")
dm_get_dev_t() is just used to convert an arbitrary 'path' string into a dev_t. It doesn't presume that the device is present; that check will be done later, as the only caller is dm_get_device(), which does a dm_get_table_device() later on, which will properly open the device.
So if the path string already _is_ in major:minor representation we can convert it directly, avoiding a recursion into the filesystem to lookup the block device.
This avoids a hang in multipath_message() when the filesystem is inaccessible.
--- drivers/md/dm-table.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/md/dm-table.c +12 -3
@@ -428,14 +428,23 @@ int dm_get_device(struct dm_target *ti, {int r;dev_t dev; +unsigned int major, minor; +char dummy;struct dm_dev_internal *dd;struct dm_table *t = ti->table;BUG_ON (!t); - dev =dm_get_dev_t (path); -if (!dev) -return -ENODEV ; +if (sscanf (path,"%u:%u%c" , &major, &minor, &dummy) ==2 ) { +/* Extract the major/minor numbers */ + dev =MKDEV (major, minor); +if (MAJOR (dev) != major ||MINOR (dev) != minor) +return -EOVERFLOW ; + }else { + dev =dm_get_dev_t (path); +if (!dev) +return -ENODEV ; + } dd =find_device (&t->devices, dev);if (!dd) {
Greg Kroah-Hartman
maintainerPATCH 14/86 dm integrity: fix a crash if "recalculate" used without "internal_hash"
In reply to Greg Kroah-HartmanFrom: Mikulas Patocka <[email protected]>
commit 2d06dfecb132a1cc2e374a44eae83b5c4356b8b4 upstream.
Recalculate can only be specified with internal_hash.
--- drivers/md/dm-integrity.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/md/dm-integrity.c +6 -0
@@ -4059,6 +4059,12 @@ try_smaller_buffer: r = -ENOMEM ; goto bad; } + }else { +if (ic->sb->flags &cpu_to_le32 (SB_FLAG_RECALCULATING )) { + ti->error ="Recalculate can only be specified with internal_hash" ; + r = -EINVAL ; + goto bad; + } } ic->bufio = dm_bufio_client_create(ic->meta_dev ? ic->meta_dev->bdev : ic->dev->bdev,
Greg Kroah-Hartman
maintainerPATCH 15/86 drm/atomic: put state on error path
In reply to Greg Kroah-HartmanFrom: Pan Bian <[email protected]>
commit 43b67309b6b2a3c08396cc9b3f83f21aa529d273 upstream.
Put the state before returning error code.
--- drivers/gpu/drm/drm_atomic_helper.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/drm_atomic_helper.c +1 -1
@@ -2948,7 +2948,7 @@ int drm_atomic_helper_set_config(struct ret =handle_conflicting_encoders (state, true);if (ret) -return ret; + goto fail; ret =drm_atomic_commit (state);
Greg Kroah-Hartman
maintainerPATCH 16/86 drm/syncobj: Fix use-after-free
In reply to Greg Kroah-HartmanFrom: Daniel Vetter <[email protected]>
commit a37eef63bc9e16e06361b539e528058146af80ab upstream.
While reviewing Christian's annotation patch I noticed that we have a user-after-free for the WAIT_FOR_SUBMIT case: We drop the syncobj reference before we've completed the waiting.
Of course usually there's nothing bad happening here since userspace keeps the reference, but we can't rely on userspace to play nice here!
--- drivers/gpu/drm/drm_syncobj.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_syncobj.c +5 -3
@@ -326,19 +326,18 @@ int drm_syncobj_find_fence(struct drm_fireturn -ENOENT ; *fence =drm_syncobj_fence_get (syncobj); -drm_syncobj_put (syncobj);if (*fence) { ret =dma_fence_chain_find_seqno (fence, point);if (!ret) -return 0 ; + goto out;dma_fence_put (*fence); }else { ret = -EINVAL ; }if (!(flags &DRM_SYNCOBJ_WAIT_FLAGS_WAIT_FOR_SUBMIT )) -return ret; + goto out;memset (&wait,0 ,sizeof (wait)); wait.task = current;
@@ -370,6 +369,9 @@ int drm_syncobj_find_fence(struct drm_fiif (wait.node.next)drm_syncobj_remove_wait (syncobj, &wait); +out: +drm_syncobj_put (syncobj); +return ret; }EXPORT_SYMBOL (drm_syncobj_find_fence);
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Greg Kroah-Hartman
maintainerPATCH 17/86 drm/i915/gt: Prevent use of engine->wa_ctx after error
In reply to Greg Kroah-HartmanFrom: Chris Wilson <[email protected]>
commit 488751a0ef9b5ce572c47301ce62d54fc6b5a74d upstream.
On error we unpin and free the wa_ctx.vma, but do not clear any of the derived flags. During lrc_init, we look at the flags and attempt to dereference the wa_ctx.vma if they are set. To protect the error path where we try to limp along without the wa_ctx, make sure we clear those flags!
(cherry-picked from 5b4dc95cf7f573e927fbbd406ebe54225d41b9b2)
--- drivers/gpu/drm/i915/gt/intel_lrc.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/i915/gt/intel_lrc.c +3 -0
@@ -2245,6 +2245,9 @@ err:static void lrc_destroy_wa_ctx (struct intel_engine_cs *engine) {i915_vma_unpin_and_release (&engine->wa_ctx.vma,0 ); + +/* Called on error unwind, clear all flags to prevent further use */ +memset (&engine->wa_ctx,0 ,sizeof (engine->wa_ctx)); }typedef u32 *(*wa_bb_func_t )(struct intel_engine_cs *engine,u32 *batch);
Greg Kroah-Hartman
maintainerPATCH 18/86 ASoC: Intel: haswell: Add missing pm_ops
In reply to Greg Kroah-HartmanFrom: Cezary Rojewski <[email protected]>
[ Upstream commit bb224c3e3e41d940612d4cc9573289cdbd5cb8f5 ]
haswell machine board is missing pm_ops what prevents it from undergoing suspend-resume procedure successfully. Assign default snd_soc_pm_ops so this is no longer the case.
--- sound/soc/intel/boards/haswell.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/intel/boards/haswell.c +1 -0
@@ -206,6 +206,7 @@ static struct platform_driver haswell_audio = { .probe = haswell_audio_probe, .driver = { .name = "haswell-audio", + .pm = &snd_soc_pm_ops, }, };
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 19/86 HID: multitouch: Enable multi-input for Synaptics pointstick/touchpad device
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
[ Upstream commit c3d6eb6e54373f297313b65c1f2319d36914d579 ]
Pointstick and its left/right buttons on HP EliteBook 850 G7 need multi-input quirk to work correctly.
--- drivers/hid/hid-multitouch.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/hid/hid-multitouch.c +4 -0
@@ -2084,6 +2084,10 @@ static const struct hid_device_id mt_devices[] = {HID_DEVICE (BUS_I2C ,HID_GROUP_MULTITOUCH_WIN_8 , USB_VENDOR_ID_SYNAPTICS, 0xce08) }, + { .driver_data = MT_CLS_WIN_8_FORCE_MULTI_INPUT, +HID_DEVICE (BUS_I2C ,HID_GROUP_MULTITOUCH_WIN_8 , + USB_VENDOR_ID_SYNAPTICS, 0xce09) }, + /* TopSeed panels */ { .driver_data = MT_CLS_TOPSEED, MT_USB_DEVICE(USB_VENDOR_ID_TOPSEED2,
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 20/86 dm integrity: select CRYPTO_SKCIPHER
In reply to Greg Kroah-HartmanFrom: Anthony Iliopoulos <[email protected]>
[ Upstream commit f7b347acb5f6c29d9229bb64893d8b6a2c7949fb ]
The integrity target relies on skcipher for encryption/decryption, but certain kernel configurations may not enable CRYPTO_SKCIPHER, leading to compilation errors due to unresolved symbols. Explicitly select CRYPTO_SKCIPHER for DM_INTEGRITY, since it is unconditionally dependent on it.
--- drivers/md/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/md/Kconfig +1 -0
@@ -565,6 +565,7 @@ config DM_INTEGRITY select BLK_DEV_INTEGRITY select DM_BUFIO select CRYPTO + select CRYPTO_SKCIPHER select ASYNC_XOR ---help--- This device-mapper target emulates a block device that has
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 21/86 scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
In reply to Greg Kroah-HartmanFrom: Can Guo <[email protected]>
[ Upstream commit 35fc4cd34426c242ab015ef280853b7bff101f48 ]
Users can initiate resets to specific SCSI device/target/host through IOCTL. When this happens, the SCSI cmd passed to eh_device/target/host _reset_handler() callbacks is initialized with a request whose tag is -1. In this case it is not right for eh_device_reset_handler() callback to count on the LUN get from hba->lrb[-1]. Fix it by getting LUN from the SCSI device associated with the SCSI cmd.
--- drivers/scsi/ufs/ufshcd.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
drivers/scsi/ufs/ufshcd.c +4 -7
@@ -5980,19 +5980,16 @@ static int ufshcd_eh_device_reset_handler(struct scsi_cmnd *cmd) {struct Scsi_Host *host;struct ufs_hba *hba; -unsigned int tag;u32 pos;int err; -u8 resp =0xF ; -struct ufshcd_lrb *lrbp; +u8 resp =0xF , lun;unsigned long flags; host = cmd->device->host; hba =shost_priv (host); - tag = cmd->request->tag; - lrbp = &hba->lrb[tag]; - err =ufshcd_issue_tm_cmd (hba, lrbp->lun,0 ,UFS_LOGICAL_RESET , &resp); + lun =ufshcd_scsi_to_upiu_lun (cmd->device->lun); + err =ufshcd_issue_tm_cmd (hba, lun,0 ,UFS_LOGICAL_RESET , &resp);if (err || resp !=UPIU_TASK_MANAGEMENT_FUNC_COMPL ) {if (!err) err = resp;
@@ -6001,7 +5998,7 @@ static int ufshcd_eh_device_reset_handler(struct scsi_cmnd *cmd)/* clear the commands that were pending for corresponding LUN */ for_each_set_bit (pos, &hba->outstanding_reqs, hba->nutrs) { -if (hba->lrb[pos].lun == lrbp->lun) { +if (hba->lrb[pos].lun == lun) { err =ufshcd_clear_cmd (hba, pos);if (err)break ;
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 22/86 scsi: qedi: Correct max length of CHAP secret
In reply to Greg Kroah-HartmanFrom: Nilesh Javali <[email protected]>
[ Upstream commit d50c7986fbf0e2167279e110a2ed5bd8e811c660 ]
The CHAP secret displayed garbage characters causing iSCSI login authentication failure. Correct the CHAP password max length.
--- drivers/scsi/qedi/qedi_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/qedi/qedi_main.c +2 -2
@@ -2175,7 +2175,7 @@ qedi_show_boot_tgt_info(struct qedi_ctx *qedi, int type, chap_name);break ;case ISCSI_BOOT_TGT_CHAP_SECRET : - rc =sprintf (buf,"%.*s\n" ,NVM_ISCSI_CFG_CHAP_NAME_MAX_LEN , + rc =sprintf (buf,"%.*s\n" ,NVM_ISCSI_CFG_CHAP_PWD_MAX_LEN , chap_secret);break ;case ISCSI_BOOT_TGT_REV_CHAP_NAME :
@@ -2183,7 +2183,7 @@ qedi_show_boot_tgt_info(struct qedi_ctx *qedi, int type, mchap_name);break ;case ISCSI_BOOT_TGT_REV_CHAP_SECRET : - rc =sprintf (buf,"%.*s\n" ,NVM_ISCSI_CFG_CHAP_NAME_MAX_LEN , + rc =sprintf (buf,"%.*s\n" ,NVM_ISCSI_CFG_CHAP_PWD_MAX_LEN , mchap_secret);break ;case ISCSI_BOOT_TGT_FLAGS :
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 23/86 scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
In reply to Greg Kroah-HartmanFrom: Ewan D. Milne <[email protected]>
[ Upstream commit e5cc9002caafacbaa8dab878d17a313192c3b03b ]
The block layer code will split a large zeroout request into multiple bios and if WRITE SAME is disabled because the storage device reports that it does not support it (or support the length used), we can get an error message from the block layer despite the setting of RQF_QUIET on the first request. This is because more than one request may have already been submitted.
Fix this by setting RQF_QUIET when BLK_STS_TARGET is returned to fail the request early, we don't need to log a message because we did not actually submit the command to the device, and the block layer code will handle the error by submitting individual write bios.
--- drivers/scsi/sd.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/scsi/sd.c +3 -1
@@ -934,8 +934,10 @@ static blk_status_t sd_setup_write_zeroes_cmnd(struct scsi_cmnd *cmd) } } -if (sdp->no_write_same) +if (sdp->no_write_same) { + rq->rq_flags |=RQF_QUIET ;return BLK_STS_TARGET ; + }if (sdkp->ws16 || lba >0xffffffff || nr_blocks >0xffff )return sd_setup_write_same16_cmnd (cmd, false);
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 24/86 riscv: Fix kernel time_init()
In reply to Greg Kroah-HartmanFrom: Damien Le Moal <[email protected]>
[ Upstream commit 11f4c2e940e2f317c9d8fb5a79702f2a4a02ff98 ]
If of_clk_init() is not called in time_init(), clock providers defined in the system device tree are not initialized, resulting in failures for other devices to initialize due to missing clocks.
Similarly to other architectures and to the default kernel time_init() implementation, call of_clk_init() before executing timer_probe() in time_init().
--- arch/riscv/kernel/time.c | 3 +++ 1 file changed, 3 insertions(+)
arch/riscv/kernel/time.c +3 -0
@@ -4,6 +4,7 @@* Copyright (C) 2017 SiFive */ +#include <linux/of_clk.h> #include <linux/clocksource.h> #include <linux/delay.h> #include <asm/sbi.h>
@@ -24,5 +25,7 @@ void __init time_init(void) riscv_timebase = prop; lpj_fine = riscv_timebase /HZ ; + +of_clk_init (NULL );timer_probe (); }
Signature · 1 line
2.27.0
Hello!
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.93 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 27 Jan 2021 18:31:44 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.93-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
Sanity results from Linaro’s test farm.
Regressions detected.
Summary
------------------------------------------------------------------------
kernel: 5.4.93-rc1
git repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
git branch: linux-5.4.y
git commit: 3deaa28e41d9780b3b462686a676fa1d21f55ad3
git describe: v5.4.92-87-g3deaa28e41d9
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.4.y-sanity/build/v5.4.92-87-g3deaa28e41d9
Regressions (compared to build v5.4.92)
------------------------------------------------------------------------
x86_64:
build:
* clang-10-allnoconfig
* clang-10-tinyconfig
* gcc-8-allnoconfig
* gcc-8-tinyconfig
* gcc-9-allnoconfig
* gcc-9-tinyconfig
* gcc-10-allnoconfig
* gcc-10-tinyconfig
riscv:
build:
* clang-10-defconfig
* clang-11-defconfig
* gcc-8-defconfig
* gcc-9-defconfig
* gcc-10-defconfig
i386:
build:
* gcc-8-allnoconfig
* gcc-8-tinyconfig
* gcc-9-allnoconfig
* gcc-9-tinyconfig
* gcc-10-allnoconfig
* gcc-10-tinyconfig
No fixes (compared to build v5.4.92)
Ran 665 total tests in the following environments and test suites.
Environments
--------------
- arc
- arm
- arm64
- i386
- juno-r2
- mips
- parisc
- powerpc
- riscv
- s390
- sh
- sparc
- x15
- x86
- x86_64
Test Suites
-----------
* build
* linux-log-parser
* ltp-smoketest-tests
i386 and x86_64 errors as reported on 5.10. Additionally, RISC-V errors look like this:
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- 'CC=sccache riscv64-linux-gnu-gcc' 'HOSTCC=sccache gcc'
Error: /builds/1nZcZgrKHH9C31BJVZOjOhHXH0s/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts:88.27-28 syntax error
FATAL ERROR: Unable to parse input tree
make[3]: *** [scripts/Makefile.lib:285: arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dtb] Error 1
make[3]: Target '__build' not remade because of errors.
make[2]: *** [/builds/1nZcZgrKHH9C31BJVZOjOhHXH0s/scripts/Makefile.build:496: arch/riscv/boot/dts/sifive] Error 2
make[2]: Target '__build' not remade because of errors.
make[1]: *** [/builds/1nZcZgrKHH9C31BJVZOjOhHXH0s/Makefile:1272: dtbs] Error 2
We'll try to get more info.
Greetings!
Daniel Díaz
[email protected]
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Greg Kroah-Hartman
maintainerPATCH 25/86 riscv: Fix sifive serial driver
In reply to Greg Kroah-HartmanFrom: Damien Le Moal <[email protected]>
[ Upstream commit 1f1496a923b6ba16679074fe77100e1b53cdb880 ]
Setup the port uartclk in sifive_serial_probe() so that the base baud rate is correctly printed during device probe instead of always showing "0". I.e. the probe message is changed from
38000000.serial: ttySIF0 at MMIO 0x38000000 (irq = 1, base_baud = 0) is a SiFive UART v0
to the correct:
38000000.serial: ttySIF0 at MMIO 0x38000000 (irq = 1, base_baud = 115200) is a SiFive UART v0
--- drivers/tty/serial/sifive.c | 1 + 1 file changed, 1 insertion(+)
drivers/tty/serial/sifive.c +1 -0
@@ -973,6 +973,7 @@ static int sifive_serial_probe(struct platform_device *pdev)/* Set up clock divider */ ssp->clkin_rate =clk_get_rate (ssp->clk); ssp->baud_rate =SIFIVE_DEFAULT_BAUD_RATE ; + ssp->port.uartclk = ssp->baud_rate *16 ;__ssp_update_div (ssp);platform_set_drvdata (pdev, ssp);
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 26/86 HID: logitech-dj: add the G602 receiver
In reply to Greg Kroah-HartmanFrom: Filipe Laíns <[email protected]>
[ Upstream commit e400071a805d6229223a98899e9da8c6233704a1 ]
Tested. The device gets correctly exported to userspace and I can see mouse and keyboard events.
--- drivers/hid/hid-logitech-dj.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/hid/hid-logitech-dj.c +4 -0
@@ -1862,6 +1862,10 @@ static const struct hid_device_id logi_dj_receivers[] = { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xc531), .driver_data = recvr_type_gaming_hidpp}, + {/* Logitech G602 receiver (0xc537) */ +HID_USB_DEVICE (USB_VENDOR_ID_LOGITECH , + 0xc537), + .driver_data = recvr_type_gaming_hidpp}, { /* Logitech lightspeed receiver (0xc539) */HID_USB_DEVICE (USB_VENDOR_ID_LOGITECH , USB_DEVICE_ID_LOGITECH_NANO_RECEIVER_LIGHTSPEED_1),
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 27/86 HID: Ignore battery for Elan touchscreen on ASUS UX550
In reply to Greg Kroah-HartmanFrom: Seth Miller <[email protected]>
[ Upstream commit 7c38e769d5c508939ce5dc26df72602f3c902342 ]
Battery status is being reported for the Elan touchscreen on ASUS UX550 laptops despite not having a batter. It always shows either 0 or 1%.
--- drivers/hid/hid-ids.h | 1 + drivers/hid/hid-input.c | 2 ++ 2 files changed, 3 insertions(+)
drivers/hid/hid-ids.h +1 -0
@@ -393,6 +393,7 @@#define USB_DEVICE_ID_TOSHIBA_CLICK_L9W 0x0401#define USB_DEVICE_ID_HP_X2 0x074d#define USB_DEVICE_ID_HP_X2_10_COVER 0x0755 +#define USB_DEVICE_ID_ASUS_UX550_TOUCHSCREEN 0x2706#define USB_VENDOR_ID_ELECOM 0x056e#define USB_DEVICE_ID_ELECOM_BM084 0x0061
drivers/hid/hid-input.c +2 -0
@@ -322,6 +322,8 @@ static const struct hid_device_id hid_battery_quirks[] = { {HID_BLUETOOTH_DEVICE (USB_VENDOR_ID_LOGITECH ,USB_DEVICE_ID_LOGITECH_DINOVO_EDGE_KBD ), HID_BATTERY_QUIRK_IGNORE }, + { HID_USB_DEVICE(USB_VENDOR_ID_ELAN, USB_DEVICE_ID_ASUS_UX550_TOUCHSCREEN), + HID_BATTERY_QUIRK_IGNORE }, {} };
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 28/86 clk: tegra30: Add hda clock default rates to clock driver
In reply to Greg Kroah-HartmanFrom: Peter Geis <[email protected]>
[ Upstream commit f4eccc7fea203cfb35205891eced1ab51836f362 ]
Current implementation defaults the hda clocks to clk_m. This causes hda to run too slow to operate correctly. Fix this by defaulting to pll_p and setting the frequency to the correct rate.
This matches upstream t124 and downstream t30.
--- drivers/clk/tegra/clk-tegra30.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/clk/tegra/clk-tegra30.c +2 -0
@@ -1263,6 +1263,8 @@ static struct tegra_clk_init_table init_table[] __initdata = { { TEGRA30_CLK_I2S3_SYNC, TEGRA30_CLK_CLK_MAX, 24000000, 0 }, { TEGRA30_CLK_I2S4_SYNC, TEGRA30_CLK_CLK_MAX, 24000000, 0 }, { TEGRA30_CLK_VIMCLK_SYNC, TEGRA30_CLK_CLK_MAX, 24000000, 0 }, + { TEGRA30_CLK_HDA, TEGRA30_CLK_PLL_P, 102000000, 0 }, + { TEGRA30_CLK_HDA2CODEC_2X, TEGRA30_CLK_PLL_P, 48000000, 0 },/* must be the last entry */ { TEGRA30_CLK_CLK_MAX, TEGRA30_CLK_CLK_MAX, 0, 0 }, };
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 29/86 arm64: make atomic helpers __always_inline
In reply to Greg Kroah-HartmanFrom: Arnd Bergmann <[email protected]>
[ Upstream commit c35a824c31834d947fb99b0c608c1b9f922b4ba0 ]
With UBSAN enabled and building with clang, there are occasionally warnings like
WARNING: modpost: vmlinux.o(.text+0xc533ec): Section mismatch in reference from the function arch_atomic64_or() to the variable .init.data:numa_nodes_parsed The function arch_atomic64_or() references
the variable __initdata numa_nodes_parsed.
This is often because arch_atomic64_or lacks a __initdata
annotation or the annotation of numa_nodes_parsed is wrong.
for functions that end up not being inlined as intended but operating on __initdata variables. Mark these as __always_inline, along with the corresponding asm-generic wrappers.
--- arch/arm64/include/asm/atomic.h | 10 +++++----- include/asm-generic/bitops/atomic.h | 6 +++--- 2 files changed, 8 insertions(+), 8 deletions(-)
arch/arm64/include/asm/atomic.h +5 -5
@@ -17,7 +17,7 @@#include <asm/lse.h> #define ATOMIC_OP (op) \ -static inline void arch_##op(int i, atomic_t *v) \ +static __always_inline void arch_##op(int i, atomic_t *v) \ { \ __lse_ll_sc_body(op, i, v); \ }
@@ -32,7 +32,7 @@ ATOMIC_OP(atomic_sub)#undef ATOMIC_OP#define ATOMIC_FETCH_OP (name, op) \ -static inline int arch_##op##name(int i, atomic_t *v) \ +static __always_inline int arch_##op##name(int i, atomic_t *v) \ { \ return __lse_ll_sc_body(op##name, i, v); \ }
@@ -56,7 +56,7 @@ ATOMIC_FETCH_OPS(atomic_sub_return)#undef ATOMIC_FETCH_OPS#define ATOMIC64_OP (op) \ -static inline void arch_##op(long i, atomic64_t *v) \ +static __always_inline void arch_##op(long i, atomic64_t *v) \ { \ __lse_ll_sc_body(op, i, v); \ }
@@ -71,7 +71,7 @@ ATOMIC64_OP(atomic64_sub)#undef ATOMIC64_OP#define ATOMIC64_FETCH_OP (name, op) \ -static inline long arch_##op##name(long i, atomic64_t *v) \ +static __always_inline long arch_##op##name(long i, atomic64_t *v) \ { \ return __lse_ll_sc_body(op##name, i, v); \ }
@@ -94,7 +94,7 @@ ATOMIC64_FETCH_OPS(atomic64_sub_return)#undef ATOMIC64_FETCH_OP#undef ATOMIC64_FETCH_OPS -static inline long arch_atomic64_dec_if_positive (atomic64_t *v) +static __always_inline long arch_atomic64_dec_if_positive (atomic64_t *v) {return __lse_ll_sc_body (atomic64_dec_if_positive, v); }
include/asm-generic/bitops/atomic.h +3 -3
@@ -11,19 +11,19 @@* See Documentation/atomic_bitops.txt for details. */ -static inline void set_bit (unsigned int nr,volatile unsigned long *p) +static __always_inline void set_bit(unsigned int nr, volatile unsigned long *p) { p +=BIT_WORD (nr);atomic_long_or (BIT_MASK (nr), (atomic_long_t *)p); } -static inline void clear_bit (unsigned int nr,volatile unsigned long *p) +static __always_inline void clear_bit(unsigned int nr, volatile unsigned long *p) { p +=BIT_WORD (nr);atomic_long_andnot (BIT_MASK (nr), (atomic_long_t *)p); } -static inline void change_bit (unsigned int nr,volatile unsigned long *p) +static __always_inline void change_bit(unsigned int nr, volatile unsigned long *p) { p +=BIT_WORD (nr);atomic_long_xor (BIT_MASK (nr), (atomic_long_t *)p);
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 30/86 xen: Fix event channel callback via INTX/GSI
In reply to Greg Kroah-HartmanFrom: David Woodhouse <[email protected]>
[ Upstream commit 3499ba8198cad47b731792e5e56b9ec2a78a83a2 ]
For a while, event channel notification via the PCI platform device has been broken, because we attempt to communicate with xenstore before we even have notifications working, with the xs_reset_watches() call in xs_init().
We tend to get away with this on Xen versions below 4.0 because we avoid calling xs_reset_watches() anyway, because xenstore might not cope with reading a non-existent key. And newer Xen *does* have the vector callback support, so we rarely fall back to INTX/GSI delivery.
To fix it, clean up a bit of the mess of xs_init() and xenbus_probe() startup. Call xs_init() directly from xenbus_init() only in the !XS_HVM case, deferring it to be called from xenbus_probe() in the XS_HVM case instead.
Then fix up the invocation of xenbus_probe() to happen either from its device_initcall if the callback is available early enough, or when the callback is finally set up. This means that the hack of calling xenbus_probe() from a workqueue after the first interrupt, or directly from the PCI platform device setup, is no longer needed.
--- arch/arm/xen/enlighten.c | 2 +- drivers/xen/events/events_base.c | 10 ---- drivers/xen/platform-pci.c | 1 - drivers/xen/xenbus/xenbus.h | 1 + drivers/xen/xenbus/xenbus_comms.c | 8 --- drivers/xen/xenbus/xenbus_probe.c | 81 +++++++++++++++++++++++++------ include/xen/xenbus.h | 2 +- 7 files changed, 70 insertions(+), 35 deletions(-)
arch/arm/xen/enlighten.c +1 -1
@@ -371,7 +371,7 @@ static int __init xen_guest_init(void) }gnttab_init ();if (!xen_initial_domain ()) -xenbus_probe (NULL ); +xenbus_probe ();/* * Making sure board specific code will not set up ops for
drivers/xen/events/events_base.c +0 -10
@@ -1988,16 +1988,6 @@ static struct irq_chip xen_percpu_chip __read_mostly = { .irq_ack = ack_dynirq, }; -int xen_set_callback_via (uint64_t via) -{ -struct xen_hvm_param a; - a.domid =DOMID_SELF ; - a.index =HVM_PARAM_CALLBACK_IRQ ; - a.value = via; -return HYPERVISOR_hvm_op (HVMOP_set_param, &a); -} -EXPORT_SYMBOL_GPL (xen_set_callback_via); -#ifdef CONFIG_XEN_PVHVM /* Vector callbacks are better than PCI interrupts to receive event * channel notifications because we can receive vector callbacks on any
drivers/xen/platform-pci.c +0 -1
@@ -149,7 +149,6 @@ static int platform_pci_probe(struct pci_dev *pdev, ret =gnttab_init ();if (ret) goto grant_out; -xenbus_probe (NULL );return 0 ; grant_out:gnttab_free_auto_xlat_frames ();
drivers/xen/xenbus/xenbus.h +1 -0
@@ -115,6 +115,7 @@ int xenbus_probe_node(struct xen_bus_type *bus,const char *type, const char *nodename);int xenbus_probe_devices (struct xen_bus_type *bus); +void xenbus_probe (void );void xenbus_dev_changed (const char *node,struct xen_bus_type *bus);
drivers/xen/xenbus/xenbus_comms.c +0 -8
@@ -57,16 +57,8 @@ DEFINE_MUTEX(xs_response_mutex);static int xenbus_irq;static struct task_struct *xenbus_task; -static DECLARE_WORK(probe_work, xenbus_probe); - -static irqreturn_t wake_waiting (int irq,void *unused) { -if (unlikely (xenstored_ready ==0 )) { - xenstored_ready =1 ; -schedule_work (&probe_work); - } -wake_up (&xb_waitq);return IRQ_HANDLED ; }
drivers/xen/xenbus/xenbus_probe.c +67 -14
107 lines not on this page · raw message
include/xen/xenbus.h +1 -1
@@ -187,7 +187,7 @@ void xs_suspend_cancel(void);struct work_struct ; -void xenbus_probe (struct work_struct *); +void xenbus_probe (void );#define XENBUS_IS_ERR_READ (str) ({ \ if (!IS_ERR(str) && strlen(str) == 0) { \
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 31/86 x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
In reply to Greg Kroah-HartmanFrom: David Woodhouse <[email protected]>
[ Upstream commit b36b0fe96af13460278bf9b173beced1bd15f85d ]
It's useful to be able to test non-vector event channel delivery, to make sure Linux will work properly on older Xen which doesn't have it.
It's also useful for those working on Xen and Xen-compatible hypervisors, because there are guest kernels still in active use which use PCI INTX even when vector delivery is available.
--- Documentation/admin-guide/kernel-parameters.txt | 4 ++++ arch/x86/xen/enlighten_hvm.c | 11 ++++++++++- 2 files changed, 14 insertions(+), 1 deletion(-)
Documentation/admin-guide/kernel-parameters.txt +4 -0
@@ -5452,6 +5452,10 @@ This option is obsoleted by the "nopv" option, which has equivalent effect for XEN platform. + xen_no_vector_callback + [KNL,X86,XEN] Disable the vector callback for Xen + event channel interrupts. + xen_scrub_pages= [XEN] Boolean option to control scrubbing pages before giving them back to Xen, for use by other domains. Can be also changed at runtime
arch/x86/xen/enlighten_hvm.c +10 -1
@@ -175,6 +175,8 @@ static int xen_cpu_dead_hvm(unsigned int cpu)return 0 ; } +static bool no_vector_callback__initdata ; +static void __init xen_hvm_guest_init (void ) {if (xen_pv_domain ())
@@ -194,7 +196,7 @@ static void __init xen_hvm_guest_init(void)xen_panic_handler_init (); -if (xen_feature (XENFEAT_hvm_callback_vector)) +if (!no_vector_callback &&xen_feature (XENFEAT_hvm_callback_vector)) xen_have_vector_callback =1 ;xen_hvm_smp_init ();
@@ -220,6 +222,13 @@ static __init int xen_parse_nopv(char *arg) }early_param ("xen_nopv" , xen_parse_nopv); +static __init int xen_parse_no_vector_callback (char *arg) +{ + no_vector_callback = true; +return 0 ; +} +early_param ("xen_no_vector_callback" , xen_parse_no_vector_callback); +bool __init xen_hvm_need_lapic (void ) {if (xen_pv_domain ())
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 32/86 dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
In reply to Greg Kroah-HartmanFrom: Sagar Shrikant Kadam <[email protected]>
[ Upstream commit be969b7cfbcfa8a835a528f1dc467f0975c6d883 ]
HiFive unleashed A00 board has VSC8541-01 ethernet phy, this device is identified as a Revision B device as described in device identification registers. In order to use this phy in the unmanaged mode, it requires a specific reset sequence of logical 0-1-0-1 transition on the NRESET pin as documented here [1].
Currently, the bootloader (fsbl or u-boot-spl) takes care of the phy reset. If due to some reason the phy device hasn't received the reset by the prior stages before the linux macb driver comes into the picture, the MACB mii bus gets probed but the mdio scan fails and is not even able to read the phy ID registers. It gives an error message:
"libphy: MACB_mii_bus: probedmdio_bus 10090000.ethernet-ffffffff: MDIO device at address 0 is missing."
Thus adding the device OUI (Organizationally Unique Identifier) to the phy device node helps to probe the phy device.
[1]: VSC8541-01 datasheet:
https://www.mouser.com/ds/2/523/Microsemi_VSC8541-01_Datasheet_10496_V40-1148034.pdf
--- arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 1 + 1 file changed, 1 insertion(+)
arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts +1 -0
@@ -83,6 +83,7 @@ phy-mode = "gmii"; phy-handle = <&phy0>; phy0: ethernet-phy@0 { + compatible = "ethernet-phy-id0007.0771"; reg = <0>; }; };
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 33/86 dts: phy: add GPIO number and active state used for phy reset
In reply to Greg Kroah-HartmanFrom: Sagar Shrikant Kadam <[email protected]>
[ Upstream commit a0fa9d727043da2238432471e85de0bdb8a8df65 ]
The GEMGXL_RST line on HiFive Unleashed is pulled low and is using GPIO number 12. Add these reset-gpio details to dt-node using which the linux phylib can reset the phy.
--- arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts | 1 + 1 file changed, 1 insertion(+)
arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts +1 -0
@@ -85,6 +85,7 @@ phy0: ethernet-phy@0 { compatible = "ethernet-phy-id0007.0771"; reg = <0>; + reset-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; }; };
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 34/86 riscv: defconfig: enable gpio support for HiFive Unleashed
In reply to Greg Kroah-HartmanFrom: Sagar Shrikant Kadam <[email protected]>
[ Upstream commit 0983834a83931606a647c275e5d4165ce4e7b49f ]
Ethernet phy VSC8541-01 on HiFive Unleashed has its reset line connected to a gpio, so enable GPIO driver's required to reset the phy.
--- arch/riscv/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+)
arch/riscv/configs/defconfig +2 -0
@@ -62,6 +62,8 @@ CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_VIRTIO=y CONFIG_SPI=y CONFIG_SPI_SIFIVE=y +CONFIG_GPIOLIB=y +CONFIG_GPIO_SIFIVE=y # CONFIG_PTP_1588_CLOCK is not set CONFIG_DRM=y CONFIG_DRM_RADEON=y
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 35/86 drm/amdgpu/psp: fix psp gfx ctrl cmds
In reply to Greg Kroah-HartmanFrom: Victor Zhao <[email protected]>
[ Upstream commit f14a5c34d143f6627f0be70c0de1d962f3a6ff1c ]
psp GFX_CTRL_CMD_ID_CONSUME_CMD different for windows and linux, according to psp, linux cmds are not correct.
v2: only correct GFX_CTRL_CMD_ID_CONSUME_CMD.
--- drivers/gpu/drm/amd/amdgpu/psp_gfx_if.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/amdgpu/psp_gfx_if.h +1 -1
@@ -44,7 +44,7 @@ enum psp_gfx_crtl_cmd_idGFX_CTRL_CMD_ID_DISABLE_INT =0x00060000 ,/* disable PSP-to-Gfx interrupt */ GFX_CTRL_CMD_ID_MODE1_RST =0x00070000 ,/* trigger the Mode 1 reset */ GFX_CTRL_CMD_ID_GBR_IH_SET =0x00080000 ,/* set Gbr IH_RB_CNTL registers */ -GFX_CTRL_CMD_ID_CONSUME_CMD =0x000A0000 ,/* send interrupt to psp for updating write pointer of vf */ +GFX_CTRL_CMD_ID_CONSUME_CMD =0x00090000 ,/* send interrupt to psp for updating write pointer of vf */ GFX_CTRL_CMD_ID_DESTROY_GPCOM_RING =0x000C0000 ,/* destroy GPCOM ring */ GFX_CTRL_CMD_ID_MAX = 0x000F0000, /* max command ID */
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 36/86 drm/amd/display: Fix to be able to stop crc calculation
In reply to Greg Kroah-HartmanFrom: Wayne Lin <[email protected]>
[ Upstream commit 02ce73b01e09e388614b22b7ebc71debf4a588f0 ]
[Why]
Find out when we try to disable CRC calculation, crc generation is still enabled. Main reason is that dc_stream_configure_crc() will never get called when the source is AMDGPU_DM_PIPE_CRC_SOURCE_NONE.
[How]
Add checking condition that when source is AMDGPU_DM_PIPE_CRC_SOURCE_NONE, we should also call dc_stream_configure_crc() to disable crc calculation. Also, clean up crc window when disable crc calculation.
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crc.c +1 -1
@@ -113,7 +113,7 @@ int amdgpu_dm_crtc_configure_crc_source(struct drm_crtc *crtc,mutex_lock (&adev->dm.dc_lock);/* Enable CRTC CRC generation if necessary. */ -if (dm_is_crc_source_crtc (source)) { +if (dm_is_crc_source_crtc (source) || source ==AMDGPU_DM_PIPE_CRC_SOURCE_NONE ) {if (!dc_stream_configure_crc (stream_state->ctx->dc, stream_state, enable, enable)) { ret = -EINVAL ;
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 37/86 drm/nouveau/bios: fix issue shadowing expansion ROMs
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit 402a89660e9dc880710b12773076a336c9dab3d7 ]
This issue has generally been covered up by the presence of additional expansion ROMs after the ones we're interested in, with header fetches of subsequent images loading enough of the ROM to hide the issue.
Noticed on GA102, which lacks a type 0x70 image compared to TU102,.
[ 906.364197] nouveau 0000:09:00.0: bios: 00000000: type 00, 65024 bytes [ 906.381205] nouveau 0000:09:00.0: bios: 0000fe00: type 03, 91648 bytes [ 906.405213] nouveau 0000:09:00.0: bios: 00026400: type e0, 22016 bytes [ 906.410984] nouveau 0000:09:00.0: bios: 0002ba00: type e0, 366080 bytes
vs
[ 22.961901] nouveau 0000:09:00.0: bios: 00000000: type 00, 60416 bytes [ 22.984174] nouveau 0000:09:00.0: bios: 0000ec00: type 03, 71168 bytes [ 23.010446] nouveau 0000:09:00.0: bios: 00020200: type e0, 48128 bytes [ 23.028220] nouveau 0000:09:00.0: bios: 0002be00: type e0, 140800 bytes [ 23.080196] nouveau 0000:09:00.0: bios: 0004e400: type 70, 7168 bytes
--- drivers/gpu/drm/nouveau/nvkm/subdev/bios/shadow.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/nouveau/nvkm/subdev/bios/shadow.c +1 -1
@@ -75,7 +75,7 @@ shadow_image(struct nvkm_bios *bios, int idx, u32 offset, struct shadow *mthd)nvkm_debug (subdev,"%08x: type %02x, %d bytes\n" , image.base, image.type, image.size); -if (!shadow_fetch (bios, mthd, image.size)) { +if (!shadow_fetch (bios, mthd, image.base + image.size)) {nvkm_debug (subdev,"%08x: fetch failed\n" , image.base);return 0 ; }
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 38/86 drm/nouveau/privring: ack interrupts the same way as RM
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit e05e06cd34f5311f677294a08b609acfbc315236 ]
Whatever it is that we were doing before doesn't work on Ampere.
--- drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gf100.c | 10 +++++++--- drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gk104.c | 10 +++++++--- 2 files changed, 14 insertions(+), 6 deletions(-)
drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gf100.c +7 -3
@@ -22,6 +22,7 @@* Authors: Ben Skeggs */ #include "priv.h" +#include <subdev/timer.h> static void gf100_ibus_intr_hub (struct nvkm_subdev *ibus,int i)
@@ -31,7 +32,6 @@ gf100_ibus_intr_hub(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x122124 + (i *0x0400 ));u32 stat =nvkm_rd32 (device,0x122128 + (i *0x0400 ));nvkm_debug (ibus,"HUB%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x122128 + (i *0x0400 ),0x00000200 ,0x00000000 ); } static void
@@ -42,7 +42,6 @@ gf100_ibus_intr_rop(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x124124 + (i *0x0400 ));u32 stat =nvkm_rd32 (device,0x124128 + (i *0x0400 ));nvkm_debug (ibus,"ROP%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x124128 + (i *0x0400 ),0x00000200 ,0x00000000 ); } static void
@@ -53,7 +52,6 @@ gf100_ibus_intr_gpc(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x128124 + (i *0x0400 ));u32 stat =nvkm_rd32 (device,0x128128 + (i *0x0400 ));nvkm_debug (ibus,"GPC%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x128128 + (i *0x0400 ),0x00000200 ,0x00000000 ); }void
@@ -90,6 +88,12 @@ gf100_ibus_intr(struct nvkm_subdev *ibus) intr1 &= ~stat; } } + +nvkm_mask (device,0x121c4c ,0x0000003f ,0x00000002 ); +nvkm_msec (device,2000 , + if (!(nvkm_rd32(device, 0x121c4c) & 0x0000003f)) + break; + ); } static int
drivers/gpu/drm/nouveau/nvkm/subdev/ibus/gk104.c +7 -3
@@ -22,6 +22,7 @@* Authors: Ben Skeggs */ #include "priv.h" +#include <subdev/timer.h> static void gk104_ibus_intr_hub (struct nvkm_subdev *ibus,int i)
@@ -31,7 +32,6 @@ gk104_ibus_intr_hub(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x122124 + (i *0x0800 ));u32 stat =nvkm_rd32 (device,0x122128 + (i *0x0800 ));nvkm_debug (ibus,"HUB%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x122128 + (i *0x0800 ),0x00000200 ,0x00000000 ); } static void
@@ -42,7 +42,6 @@ gk104_ibus_intr_rop(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x124124 + (i *0x0800 ));u32 stat =nvkm_rd32 (device,0x124128 + (i *0x0800 ));nvkm_debug (ibus,"ROP%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x124128 + (i *0x0800 ),0x00000200 ,0x00000000 ); } static void
@@ -53,7 +52,6 @@ gk104_ibus_intr_gpc(struct nvkm_subdev *ibus, int i)u32 data =nvkm_rd32 (device,0x128124 + (i *0x0800 ));u32 stat =nvkm_rd32 (device,0x128128 + (i *0x0800 ));nvkm_debug (ibus,"GPC%d: %06x %08x (%08x)\n" , i, addr, data, stat); -nvkm_mask (device,0x128128 + (i *0x0800 ),0x00000200 ,0x00000000 ); }void
@@ -90,6 +88,12 @@ gk104_ibus_intr(struct nvkm_subdev *ibus) intr1 &= ~stat; } } + +nvkm_mask (device,0x12004c ,0x0000003f ,0x00000002 ); +nvkm_msec (device,2000 , + if (!(nvkm_rd32(device, 0x12004c) & 0x0000003f)) + break; + ); } static int
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 39/86 drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit ba6e9ab0fcf3d76e3952deb12b5f993991621d9c ]
Noticed while debugging GA102.
--- drivers/gpu/drm/nouveau/nvkm/subdev/i2c/auxgm200.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/nouveau/nvkm/subdev/i2c/auxgm200.c +4 -4
@@ -33,7 +33,7 @@ static void gm200_i2c_aux_fini(struct gm200_i2c_aux *aux) {struct nvkm_device *device = aux->base.pad->i2c->subdev.device; -nvkm_mask (device,0x00d954 + (aux->ch *0x50 ),0x00310000 ,0x00000000 ); +nvkm_mask (device,0x00d954 + (aux->ch *0x50 ),0x00710000 ,0x00000000 ); } static int
@@ -54,10 +54,10 @@ gm200_i2c_aux_init(struct gm200_i2c_aux *aux)AUX_ERR (&aux->base,"begin idle timeout %08x" , ctrl);return -EBUSY ; } - }while (ctrl &0x03010000 ); + }while (ctrl &0x07010000 );/* set some magic, and wait up to 1ms for it to appear */ -nvkm_mask (device,0x00d954 + (aux->ch *0x50 ),0x00300000 , ureq); +nvkm_mask (device,0x00d954 + (aux->ch *0x50 ),0x00700000 , ureq); timeout =1000 ; do { ctrl = nvkm_rd32(device, 0x00d954 + (aux->ch * 0x50));
@@ -67,7 +67,7 @@ gm200_i2c_aux_init(struct gm200_i2c_aux *aux)gm200_i2c_aux_fini (aux);return -EBUSY ; } - }while ((ctrl &0x03000000 ) != urep); + }while ((ctrl &0x07000000 ) != urep);return 0 ; }
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 40/86 drm/nouveau/mmu: fix vram heap sizing
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit add42781ad76c5ae65127bf13852a4c6b2f08849 ]
--- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/base.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/nouveau/nvkm/subdev/mmu/base.c +3 -3
@@ -316,9 +316,9 @@ nvkm_mmu_vram(struct nvkm_mmu *mmu) {struct nvkm_device *device = mmu->subdev.device;struct nvkm_mm *mm = &device->fb->ram->vram; -const u32 sizeN =nvkm_mm_heap_size (mm,NVKM_RAM_MM_NORMAL ); -const u32 sizeU =nvkm_mm_heap_size (mm,NVKM_RAM_MM_NOMAP ); -const u32 sizeM =nvkm_mm_heap_size (mm,NVKM_RAM_MM_MIXED ); +const u64 sizeN =nvkm_mm_heap_size (mm,NVKM_RAM_MM_NORMAL ); +const u64 sizeU =nvkm_mm_heap_size (mm,NVKM_RAM_MM_NOMAP ); +const u64 sizeM =nvkm_mm_heap_size (mm,NVKM_RAM_MM_MIXED );u8 type =NVKM_MEM_KIND * !!mmu->func->kind;u8 heap =NVKM_MEM_VRAM ;int heapM, heapN, heapU;
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 41/86 drm/nouveau/kms/nv50-: fix case where notifier buffer is at offset 0
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit caeb6ab899c3d36a74cda6e299c6e1c9c4e2a22e ]
VRAM offset 0 is a valid address, triggered on GA102.
--- drivers/gpu/drm/nouveau/dispnv50/disp.c | 4 ++-- drivers/gpu/drm/nouveau/dispnv50/disp.h | 2 +- drivers/gpu/drm/nouveau/dispnv50/wimmc37b.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/nouveau/dispnv50/disp.c +2 -2
@@ -132,7 +132,7 @@ nv50_dmac_destroy(struct nv50_dmac *dmac)int nv50_dmac_create (struct nvif_device *device,struct nvif_object *disp, -const s32 *oclass,u8 head,void *data,u32 size,u64 syncbuf, +const s32 *oclass,u8 head,void *data,u32 size,s64 syncbuf,struct nv50_dmac *dmac) {struct nouveau_cli *cli = (void *)device->object.client;
@@ -167,7 +167,7 @@ nv50_dmac_create(struct nvif_device *device, struct nvif_object *disp,if (ret)return ret; -if (!syncbuf) +if (syncbuf <0 )return 0 ; ret = nvif_object_init(&dmac->base.user, 0xf0000000, NV_DMA_IN_MEMORY,
drivers/gpu/drm/nouveau/dispnv50/disp.h +1 -1
@@ -70,7 +70,7 @@ struct nv50_dmac {int nv50_dmac_create (struct nvif_device *device,struct nvif_object *disp,const s32 *oclass,u8 head,void *data,u32 size, -u64 syncbuf,struct nv50_dmac *dmac); +s64 syncbuf,struct nv50_dmac *dmac);void nv50_dmac_destroy (struct nv50_dmac *);u32 *evo_wait (struct nv50_dmac *,int nr);
drivers/gpu/drm/nouveau/dispnv50/wimmc37b.c +1 -1
@@ -68,7 +68,7 @@ wimmc37b_init_(const struct nv50_wimm_func *func, struct nouveau_drm *drm,int ret; ret =nv50_dmac_create (&drm->client.device, &disp->disp->object, - &oclass,0 , &args,sizeof (args),0 , + &oclass,0 , &args,sizeof (args),-1 , &wndw->wimm);if (ret) {NV_ERROR (drm,"wimm%04x allocation failed: %d\n" , oclass, ret);
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 42/86 powerpc: Use the common INIT_DATA_SECTION macro in vmlinux.lds.S
In reply to Greg Kroah-HartmanFrom: Youling Tang <[email protected]>
[ Upstream commit fdcfeaba38e5b183045f5b079af94f97658eabe6 ]
Use the common INIT_DATA_SECTION rule for the linker script in an effort to regularize the linker script.
--- arch/powerpc/kernel/vmlinux.lds.S | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-)
arch/powerpc/kernel/vmlinux.lds.S +1 -18
@@ -223,21 +223,7 @@ SECTIONS EXIT_TEXT } - .init.data : AT(ADDR(.init.data) - LOAD_OFFSET) { - INIT_DATA - } - - .init.setup : AT(ADDR(.init.setup) - LOAD_OFFSET) { - INIT_SETUP(16) - } - - .initcall.init : AT(ADDR(.initcall.init) - LOAD_OFFSET) { - INIT_CALLS - } - - .con_initcall.init : AT(ADDR(.con_initcall.init) - LOAD_OFFSET) { - CON_INITCALL - } + INIT_DATA_SECTION(16) . = ALIGN(8); __ftr_fixup : AT(ADDR(__ftr_fixup) - LOAD_OFFSET) {
@@ -265,9 +251,6 @@ SECTIONS __stop___fw_ftr_fixup = .; } #endif - .init.ramfs : AT(ADDR(.init.ramfs) - LOAD_OFFSET) { - INIT_RAM_FS - } PERCPU_SECTION(L1_CACHE_BYTES)
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 43/86 pinctrl: aspeed: g6: Fix PWMG0 pinctrl setting
In reply to Greg Kroah-HartmanFrom: Billy Tsai <[email protected]>
[ Upstream commit 92ff62a7bcc17d47c0ce8dddfb7a6e1a2e55ebf4 ]
The SCU offset for signal PWM8 in group PWM8G0 is wrong, fix it from SCU414 to SCU4B4.
--- drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.c +1 -1
@@ -334,7 +334,7 @@ FUNC_GROUP_DECL(RMII4, F24, E23, E24, E25, C25, C24, B26, B25, B24);#define D22 40SIG_EXPR_LIST_DECL_SESG (D22 ,SD1CLK ,SD1 ,SIG_DESC_SET (SCU414 ,8 )); -SIG_EXPR_LIST_DECL_SEMG (D22 ,PWM8 ,PWM8G0 ,PWM8 ,SIG_DESC_SET (SCU414 ,8 )); +SIG_EXPR_LIST_DECL_SEMG (D22 ,PWM8 ,PWM8G0 ,PWM8 ,SIG_DESC_SET (SCU4B4 ,8 ));PIN_DECL_2 (D22 ,GPIOF0 ,SD1CLK ,PWM8 );GROUP_DECL (PWM8G0 ,D22 );
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 44/86 scsi: megaraid_sas: Fix MEGASAS_IOC_FIRMWARE regression
In reply to Greg Kroah-HartmanFrom: Arnd Bergmann <[email protected]>
[ Upstream commit b112036535eda34460677ea883eaecc3a45a435d ]
Phil Oester reported that a fix for a possible buffer overrun that I sent caused a regression that manifests in this output:
Event Message: A PCI parity error was detected on a component at bus 0 device 5 function 0.
Severity: Critical
Message ID: PCI1308
The original code tried to handle the sense data pointer differently when using 32-bit 64-bit DMA addressing, which would lead to a 32-bit dma_addr_t value of 0x11223344 to get stored
32-bit kernel: 44 33 22 11 ?? ?? ?? ?? 64-bit LE kernel: 44 33 22 11 00 00 00 00 64-bit BE kernel: 00 00 00 00 44 33 22 11
or a 64-bit dma_addr_t value of 0x1122334455667788 to get stored as
32-bit kernel: 88 77 66 55 ?? ?? ?? ??
64-bit kernel: 88 77 66 55 44 33 22 11
In my patch, I tried to ensure that the same value is used on both 32-bit and 64-bit kernels, and picked what seemed to be the most sensible combination, storing 32-bit addresses in the first four bytes (as 32-bit kernels already did), and 64-bit addresses in eight consecutive bytes (as 64-bit kernels already did), but evidently this was incorrect.
Always storing the dma_addr_t pointer as 64-bit little-endian, i.e. initializing the second four bytes to zero in case of 32-bit addressing, apparently solved the problem for Phil, and is consistent with what all 64-bit little-endian machines did before.
I also checked in the history that in previous versions of the code, the pointer was always in the first four bytes without padding, and that previous attempts to fix 64-bit user space, big-endian architectures and 64-bit DMA were clearly flawed and seem to have introduced made this worse.
--- drivers/scsi/megaraid/megaraid_sas_base.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/scsi/megaraid/megaraid_sas_base.c +2 -4
@@ -8174,11 +8174,9 @@ megasas_mgmt_fw_ioctl(struct megasas_instance *instance, goto out; } +/* always store 64 bits regardless of addressing */ sense_ptr = (void *)cmd->frame + ioc->sense_off; -if (instance->consistent_mask_64bit) -put_unaligned_le64 (sense_handle, sense_ptr); -else -put_unaligned_le32 (sense_handle, sense_ptr); +put_unaligned_le64 (sense_handle, sense_ptr); }/*
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 45/86 powerpc: Fix alignment bug within the init sections
In reply to Greg Kroah-HartmanFrom: Ariel Marcovitch <[email protected]>
[ Upstream commit 2225a8dda263edc35a0e8b858fe2945cf6240fde ]
This is a bug that causes early crashes in builds with an .exit.text section smaller than a page and an .init.text section that ends in the beginning of a physical page (this is kinda random, which might explain why this wasn't really encountered before).
The init sections are ordered like this:
.init.text
.exit.text
.init.data
Currently, these sections aren't page aligned.
Because the init code might become read-only at runtime and because the .init.text section can potentially reside on the same physical page as .init.data, the beginning of .init.data might be mapped read-only along with .init.text.
Then when the kernel tries to modify a variable in .init.data (like kthreadd_done, used in kernel_init()) the kernel panics.
To avoid this, make _einittext page aligned and also align .exit.text to make sure .init.data is always seperated from the text segments.
--- arch/powerpc/kernel/vmlinux.lds.S | 8 ++++++++ 1 file changed, 8 insertions(+)
arch/powerpc/kernel/vmlinux.lds.S +8 -0
@@ -210,6 +210,12 @@ SECTIONS .init.text : AT(ADDR(.init.text) - LOAD_OFFSET) { _sinittext = .; INIT_TEXT + + /* + *.init.text might be RO so we must ensure this section ends on + * a page boundary. + */ + . = ALIGN(PAGE_SIZE); _einittext = .; #ifdef CONFIG_PPC64 *(.tramp.ftrace.init);
@@ -223,6 +229,8 @@ SECTIONS EXIT_TEXT } + . = ALIGN(PAGE_SIZE); + INIT_DATA_SECTION(16) . = ALIGN(8);
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 46/86 i2c: octeon: check correct size of maximum RECV_LEN packet
In reply to Greg Kroah-HartmanFrom: Wolfram Sang <[email protected]>
[ Upstream commit 1b2cfa2d1dbdcc3b6dba1ecb7026a537a1d7277f ]
I2C_SMBUS_BLOCK_MAX defines already the maximum number as defined in the SMBus 2.0 specs. No reason to add one to it.
--- drivers/i2c/busses/i2c-octeon-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-octeon-core.c +1 -1
@@ -347,7 +347,7 @@ static int octeon_i2c_read(struct octeon_i2c *i2c, int target,if (result)return result;if (recv_len && i ==0 ) { -if (data[i] >I2C_SMBUS_BLOCK_MAX +1 ) +if (data[i] >I2C_SMBUS_BLOCK_MAX )return -EPROTO ; length += data[i]; }
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 47/86 platform/x86: intel-vbtn: Drop HP Stream x360 Convertible PC 11 from allow-list
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
[ Upstream commit 070222731be52d741e55d8967b1764482b81e54c ]
THe HP Stream x360 Convertible PC 11 DSDT has the following VGBS function:
Method (VGBS, 0, Serialized)
{
If ((^^PCI0.LPCB.EC0.ROLS == Zero))
{
VBDS = Zero
}
Else
{
VBDS = Zero
}
Return (VBDS) /* \_SB_.VGBI.VBDS */
}Which is obviously wrong, because it always returns 0 independent of the 2-in-1 being in laptop or tablet mode. This causes the intel-vbtn driver to initially report SW_TABLET_MODE = 1 to userspace, which is known to cause problems when the 2-in-1 is actually in laptop mode.
During earlier testing this turned out to not be a problem because the 2-in-1 would do a Notify(..., 0xCC) or Notify(..., 0xCD) soon after the intel-vbtn driver loaded, correcting the SW_TABLET_MODE state.
Further testing however has shown that this Notify() soon after the intel-vbtn driver loads, does not always happen. When the Notify does not happen, then intel-vbtn reports SW_TABLET_MODE = 1 resulting in a non-working touchpad.
IOW the tablet-mode reporting is not reliable on this device, so it should be dropped from the allow-list, fixing the touchpad sometimes not working.
--- drivers/platform/x86/intel-vbtn.c | 6 ------ 1 file changed, 6 deletions(-)
drivers/platform/x86/intel-vbtn.c +0 -6
@@ -191,12 +191,6 @@ static const struct dmi_system_id dmi_switches_allow_list[] = { DMI_MATCH(DMI_PRODUCT_NAME, "Venue 11 Pro 7130"), }, }, - { - .matches = { -DMI_MATCH (DMI_SYS_VENDOR ,"Hewlett-Packard" ), - DMI_MATCH(DMI_PRODUCT_NAME, "HP Stream x360 Convertible PC 11"), - }, - }, { .matches = { DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 48/86 selftests: net: fib_tests: remove duplicate log test
In reply to Greg Kroah-HartmanFrom: Hangbin Liu <[email protected]>
[ Upstream commit fd23d2dc180fccfad4b27a8e52ba1bc415d18509 ]
The previous test added an address with a specified metric and check if correspond route was created. I somehow added two logs for the same test. Remove the duplicated one.
--- tools/testing/selftests/net/fib_tests.sh | 1 - 1 file changed, 1 deletion(-)
tools/testing/selftests/net/fib_tests.sh +0 -1
@@ -1055,7 +1055,6 @@ ipv6_addr_metric_test() check_route6 "2001:db8:104::1 dev dummy2 proto kernel metric 260" log_test $? 0 "Set metric with peer route on local side" - log_test $? 0 "User specified metric on local address" check_route6 "2001:db8:104::2 dev dummy2 proto kernel metric 260" log_test $? 0 "Set metric with peer route on peer side"
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 49/86 can: dev: can_restart: fix use after free bug
In reply to Greg Kroah-HartmanFrom: Vincent Mailhol <[email protected]>
[ Upstream commit 03f16c5075b22c8902d2af739969e878b0879c94 ]
After calling netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the netif_rx_ni() in:
stats->rx_bytes += cf->len;
Reordering the lines solves the issue.
--- drivers/net/can/dev.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/can/dev.c +2 -2
@@ -567,11 +567,11 @@ static void can_restart(struct net_device *dev) } cf->can_id |=CAN_ERR_RESTARTED ; -netif_rx_ni (skb); - stats->rx_packets++; stats->rx_bytes += cf->can_dlc; +netif_rx_ni (skb); + restart:netdev_dbg (dev,"restarted\n" ); priv->can_stats.restarts++;
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 50/86 can: vxcan: vxcan_xmit: fix use after free bug
In reply to Greg Kroah-HartmanFrom: Vincent Mailhol <[email protected]>
[ Upstream commit 75854cad5d80976f6ea0f0431f8cedd3bcc475cb ]
After calling netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the canfd_frame cfd which aliases skb memory is accessed after the netif_rx_ni().
--- drivers/net/can/vxcan.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/net/can/vxcan.c +4 -2
@@ -39,6 +39,7 @@ static netdev_tx_t vxcan_xmit(struct sk_buff *skb, struct net_device *dev)struct net_device *peer;struct canfd_frame *cfd = (struct canfd_frame *)skb->data;struct net_device_stats *peerstats, *srcstats = &dev->stats; +u8 len;if (can_dropped_invalid_skb (dev, skb))return NETDEV_TX_OK ;
@@ -61,12 +62,13 @@ static netdev_tx_t vxcan_xmit(struct sk_buff *skb, struct net_device *dev) skb->dev = peer; skb->ip_summed =CHECKSUM_UNNECESSARY ; + len = cfd->len;if (netif_rx_ni (skb) ==NET_RX_SUCCESS ) { srcstats->tx_packets++; - srcstats->tx_bytes += cfd->len; + srcstats->tx_bytes += len; peerstats = &peer->stats; peerstats->rx_packets++; - peerstats->rx_bytes += cfd->len; + peerstats->rx_bytes += len; } out_unlock:
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 51/86 can: peak_usb: fix use after free bugs
In reply to Greg Kroah-HartmanFrom: Vincent Mailhol <[email protected]>
[ Upstream commit 50aca891d7a554db0901b245167cd653d73aaa71 ]
After calling peak_usb_netif_rx_ni(skb), dereferencing skb is unsafe. Especially, the can_frame cf which aliases skb memory is accessed after the peak_usb_netif_rx_ni().
Reordering the lines solves the issue.
--- drivers/net/can/usb/peak_usb/pcan_usb_fd.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/net/can/usb/peak_usb/pcan_usb_fd.c +4 -4
@@ -512,11 +512,11 @@ static int pcan_usb_fd_decode_canmsg(struct pcan_usb_fd_if *usb_if,else memcpy (cfd->data, rm->d, cfd->len); -peak_usb_netif_rx (skb, &usb_if->time_ref,le32_to_cpu (rm->ts_low)); - netdev->stats.rx_packets++; netdev->stats.rx_bytes += cfd->len; +peak_usb_netif_rx (skb, &usb_if->time_ref,le32_to_cpu (rm->ts_low)); +return 0 ; }
@@ -578,11 +578,11 @@ static int pcan_usb_fd_decode_status(struct pcan_usb_fd_if *usb_if,if (!skb)return -ENOMEM ; -peak_usb_netif_rx (skb, &usb_if->time_ref,le32_to_cpu (sm->ts_low)); - netdev->stats.rx_packets++; netdev->stats.rx_bytes += cf->can_dlc; +peak_usb_netif_rx (skb, &usb_if->time_ref,le32_to_cpu (sm->ts_low)); +return 0 ; }
Signature · 1 line
2.27.0
Greg Kroah-Hartman
maintainerPATCH 52/86 iio: ad5504: Fix setting power-down state
In reply to Greg Kroah-HartmanFrom: Lars-Peter Clausen <[email protected]>
commit efd597b2839a9895e8a98fcb0b76d2f545802cd4 upstream.
The power-down mask of the ad5504 is actually a power-up mask. Meaning if a bit is set the corresponding channel is powered up and if it is not set the channel is powered down.
The driver currently has this the wrong way around, resulting in the channel being powered up when requested to be powered down and vice versa.
--- drivers/iio/dac/ad5504.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iio/dac/ad5504.c +2 -2
@@ -188,9 +188,9 @@ static ssize_t ad5504_write_dac_powerdowreturn ret;if (pwr_down) - st->pwr_down_mask |= (1 << chan->channel); -else st->pwr_down_mask &= ~(1 << chan->channel); +else + st->pwr_down_mask |= (1 << chan->channel); ret = ad5504_spi_write(st, AD5504_ADDR_CTRL, AD5504_DAC_PWRDWN_MODE(st->pwr_down_mode) |
Greg Kroah-Hartman
maintainerPATCH 53/86 cifs: do not fail __smb_send_rqst if non-fatal signals are pending
In reply to Greg Kroah-HartmanFrom: Ronnie Sahlberg <[email protected]>
commit 214a5ea081e77346e4963dd6d20c5539ff8b6ae6 upstream.
RHBZ 1848178
The original intent of returning an error in this function in the patch:
"CIFS: Mask off signals when sending SMB packets"
was to avoid interrupting packet send in the middle of sending the data (and thus breaking an SMB connection), but we also don't want to fail the request for non-fatal signals even before we have had a chance to try to send it (the reported problem could be reproduced e.g. by exiting a child process when the parent process was in the midst of calling futimens to update a file's timestamps).
In addition, since the signal may remain pending when we enter the sending loop, we may end up not sending the whole packet before TCP buffers become full. In this case the code returns -EINTR but what we need here is to return -ERESTARTSYS instead to allow system calls to be restarted.
--- fs/cifs/transport.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/cifs/transport.c +2 -2
@@ -339,7 +339,7 @@ __smb_send_rqst(struct TCP_Server_Info *if (ssocket ==NULL )return -EAGAIN ; -if (signal_pending (current)) { +if (fatal_signal_pending (current)) {cifs_dbg (FYI ,"signal pending before send request\n" );return -ERESTARTSYS ; }
@@ -431,7 +431,7 @@ unmask:if (signal_pending (current) && (total_len != send_length)) {cifs_dbg (FYI ,"signal is pending after attempt to send\n" ); - rc = -EINTR ; + rc = -ERESTARTSYS ; }/* uncork it */
Greg Kroah-Hartman
maintainerPATCH 54/86 irqchip/mips-cpu: Set IPI domain parent chip
In reply to Greg Kroah-HartmanFrom: Mathias Kresin <[email protected]>
commit 599b3063adf4bf041a87a69244ee36aded0d878f upstream.
Since commit 55567976629e ("genirq/irqdomain: Allow partial trimming of irq_data hierarchy") the irq_data chain is valided.
The irq_domain_trim_hierarchy() function doesn't consider the irq + ipi domain hierarchy as valid, since the ipi domain has the irq domain set as parent, but the parent domain has no chip set. Hence the boot ends in a kernel panic.
Set the chip for the parent domain as it is done in the mips gic irq driver, to have a valid irq_data chain.
--- drivers/irqchip/irq-mips-cpu.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/irqchip/irq-mips-cpu.c +7 -0
@@ -197,6 +197,13 @@ static int mips_cpu_ipi_alloc(struct irqif (ret)return ret; + ret =irq_domain_set_hwirq_and_chip (domain->parent, virq + i, hwirq, + &mips_mt_cpu_irq_controller, +NULL ); + +if (ret) +return ret; + ret =irq_set_irq_type (virq + i,IRQ_TYPE_LEVEL_HIGH );if (ret)return ret;
Greg Kroah-Hartman
maintainerPATCH 55/86 x86/mmx: Use KFPU_387 for MMX string operations
In reply to Greg Kroah-HartmanFrom: Andy Lutomirski <[email protected]>
commit 67de8dca50c027ca0fa3b62a488ee5035036a0da upstream.
The default kernel_fpu_begin() doesn't work on systems that support XMM but haven't yet enabled CR4.OSFXSR. This causes crashes when _mmx_memcpy() is called too early because LDMXCSR generates #UD when the aforementioned bit is clear.
Fix it by using kernel_fpu_begin_mask(KFPU_387) explicitly.
--- arch/x86/lib/mmx_32.c | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-)
arch/x86/lib/mmx_32.c +15 -5
@@ -26,6 +26,16 @@#include <asm/fpu/api.h> #include <asm/asm.h> +/* +* Use KFPU_387. MMX instructions are not affected by MXCSR, +* but both AMD and Intel documentation states that even integer MMX +* operations will result in #MF if an exception is pending in FCW. +* +* EMMS is not needed afterwards because, after calling kernel_fpu_end(), +* any subsequent user of the 387 stack will reinitialize it using +* KFPU_387. +*/ +void *_mmx_memcpy (void *to,const void *from,size_t len) {void *p;
@@ -37,7 +47,7 @@ void *_mmx_memcpy(void *to, const void * p = to; i = len >>6 ;/* len/64 */ -kernel_fpu_begin (); +kernel_fpu_begin_mask (KFPU_387 ); __asm__ __volatile__ ( "1: prefetch (%0)\n" /* This set is 28 bytes */
@@ -127,7 +137,7 @@ static void fast_clear_page(void *page) {int i; -kernel_fpu_begin (); +kernel_fpu_begin_mask (KFPU_387 ); __asm__ __volatile__ ( " pxor %%mm0, %%mm0\n" : :
@@ -160,7 +170,7 @@ static void fast_copy_page(void *to, voi {int i; -kernel_fpu_begin (); +kernel_fpu_begin_mask (KFPU_387 );/* * maybe the prefetch stuff can go before the expensive fnsave...
@@ -247,7 +257,7 @@ static void fast_clear_page(void *page) {int i; -kernel_fpu_begin (); +kernel_fpu_begin_mask (KFPU_387 ); __asm__ __volatile__ ( " pxor %%mm0, %%mm0\n" : :
@@ -282,7 +292,7 @@ static void fast_copy_page(void *to, voi {int i; -kernel_fpu_begin (); +kernel_fpu_begin_mask (KFPU_387 ); __asm__ __volatile__ ( "1: prefetch (%0)\n"
Re: [PATCH 5.4 55/86] x86/mmx: Use KFPU_387 for MMX string operations
Quoted 11 lines · Greg Kroah-Hartman
From: Andy Lutomirski <[email protected]>
commit
67de8dca50c027ca0fa3b62a488ee5035036a0daupstream.The default
kernel_fpu_begin()doesn't work on systems that support XMM but haven't yet enabled CR4.OSFXSR. This causes crashes when_mmx_memcpy()is called too early because LDMXCSR generates #UD when the aforementioned bit is clear.Fix it by using
kernel_fpu_begin_mask(KFPU_387)explicitly.
Quoted 9 lines
Fixes 7ad816762f9b ("x86/fpu: Reset MXCSR to default in kernel_fpu_begin()")Reported-by Krzysztof Mazur <[email protected]>Signed-off-by Andy Lutomirski <[email protected]>Signed-off-by Borislav Petkov <[email protected]>Tested-by Krzysztof Mazur <[email protected]>Cc <[email protected]>Link https://lkml.kernel.org/r/e7bf21855fe99e5f3baa27446e32623358f69e8d.1611205691.git.luto@kernel.org open hereSigned-off-by Greg Kroah-Hartman <[email protected]>
Similar to 5.10.11, we also need https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e45122893a9870813f9bd7b4add4f613e6f29008 in 5.4.93:
Otherwise, the kernel will fail to compile if CONFIG_X86_USE_3DNOW=y
arch/x86/lib/mmx_32.c: In function '_mmx_memcpy':arch/x86/lib/mmx_32.c:50:2: error: implicit declaration of function 'kernel_fpu_begin_mask'; did you mean 'kernel_fpu_begin'? [-Werror=implicit-function-declaration]
50 | kernel_fpu_begin_mask(KFPU_387);
| ^~~~~~~~~~~~~~~~~~~~~
| kernel_fpu_begin
arch/x86/lib/mmx_32.c:50:24: error: 'KFPU_387' undeclared (first use in this function)
50 | kernel_fpu_begin_mask(KFPU_387);
| ^~~~~~~~
arch/x86/lib/mmx_32.c:50:24: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/lib/mmx_32.c: In function 'fast_clear_page':
arch/x86/lib/mmx_32.c:140:24: error: 'KFPU_387' undeclared (first use in this function)
140 | kernel_fpu_begin_mask(KFPU_387);
| ^~~~~~~~
arch/x86/lib/mmx_32.c: In function 'fast_copy_page':
arch/x86/lib/mmx_32.c:173:24: error: 'KFPU_387' undeclared (first use in this function)
173 | kernel_fpu_begin_mask(KFPU_387);
| ^~~~~~~~Thanks,
Krzysztof
Greg Kroah-Hartman
maintainerPATCH 56/86 intel_th: pci: Add Alder Lake-P support
In reply to Greg Kroah-HartmanFrom: Alexander Shishkin <[email protected]>
commit cb5c681ab9037e25fcca20689c82cf034566d610 upstream.
This adds support for the Trace Hub in Alder Lake-P.
--- drivers/hwtracing/intel_th/pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/hwtracing/intel_th/pci.c +5 -0
@@ -259,6 +259,11 @@ static const struct pci_device_id intel_ .driver_data = (kernel_ulong_t)&intel_th_2x, }, { +/* Alder Lake-P */ + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x51a6), + .driver_data = (kernel_ulong_t)&intel_th_2x, + }, + {/* Emmitsburg PCH */ PCI_DEVICE (PCI_VENDOR_ID_INTEL ,0x1bcc ), .driver_data = (kernel_ulong_t)&intel_th_2x,
Greg Kroah-Hartman
maintainerPATCH 57/86 stm class: Fix module init return on allocation failure
In reply to Greg Kroah-HartmanFrom: Wang Hui <[email protected]>
commit 927633a6d20af319d986f3e42c3ef9f6d7835008 upstream.
In stm_heartbeat_init(): return value gets reset after the first iteration by stm_source_register_device(), so allocation failures after that will, after a clean up, return success. Fix that.
--- drivers/hwtracing/stm/heartbeat.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/hwtracing/stm/heartbeat.c +4 -2
@@ -64,7 +64,7 @@ static void stm_heartbeat_unlink(structstatic int stm_heartbeat_init (void ) { -int i, ret = -ENOMEM ; +int i, ret;if (nr_devs <0 || nr_devs >STM_HEARTBEAT_MAX )return -EINVAL ;
@@ -72,8 +72,10 @@ static int stm_heartbeat_init(void)for (i =0 ; i < nr_devs; i++) { stm_heartbeat[i].data.name =kasprintf (GFP_KERNEL ,"heartbeat.%d" , i); -if (!stm_heartbeat[i].data.name) +if (!stm_heartbeat[i].data.name) { + ret = -ENOMEM ; goto fail_unregister; + } stm_heartbeat[i].data.nr_chans =1 ; stm_heartbeat[i].data.link = stm_heartbeat_link;
Greg Kroah-Hartman
maintainerPATCH 58/86 serial: mvebu-uart: fix tx lost characters at power off
In reply to Greg Kroah-HartmanFrom: Pali Rohár <[email protected]>
commit 54ca955b5a4024e2ce0f206b03adb7109bc4da26 upstream.
Commit c685af1108d7 ("serial: mvebu-uart: fix tx lost characters") fixed tx lost characters at low baud rates but started causing tx lost characters when kernel is going to power off or reboot.
TX_EMP tells us when transmit queue is empty therefore all characters were transmitted. TX_RDY tells us when CPU can send a new character.
Therefore we need to use different check prior transmitting new character and different check after all characters were sent.
This patch splits polling code into two functions: wait_for_xmitr() which waits for TX_RDY and wait_for_xmite() which waits for TX_EMP.
When rebooting A3720 platform without this patch on UART is print only:
[ 42.699�
And with this patch on UART is full output:
[ 39.530216] reboot: Restarting system
--- drivers/tty/serial/mvebu-uart.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/tty/serial/mvebu-uart.c +9 -1
@@ -648,6 +648,14 @@ static void wait_for_xmitr(struct uart_p (val & STAT_TX_RDY(port)), 1, 10000); } +static void wait_for_xmite (struct uart_port *port) +{ +u32 val; + +readl_poll_timeout_atomic (port->membase +UART_STAT , val, + (val &STAT_TX_EMP ),1 ,10000 ); +} +static void mvebu_uart_console_putchar (struct uart_port *port,int ch) {wait_for_xmitr (port);
@@ -675,7 +683,7 @@ static void mvebu_uart_console_write(struart_console_write (port, s, count, mvebu_uart_console_putchar); -wait_for_xmitr (port); +wait_for_xmite (port);if (ier)writel (ier, port->membase +UART_CTRL (port));
Greg Kroah-Hartman
maintainerPATCH 59/86 ehci: fix EHCI host controller initialization sequence
In reply to Greg Kroah-HartmanFrom: Eugene Korenevsky <[email protected]>
commit 280a9045bb18833db921b316a5527d2b565e9f2e upstream.
According to EHCI spec, EHCI HC clears USBSTS.HCHalted whenever USBCMD.RS=1.
However, it is a good practice to wait some time after setting USBCMD.RS (approximately 100ms) until USBSTS.HCHalted become zero.
Without this waiting, VirtualBox's EHCI virtual HC accidentally hangs (see BugLink).
--- drivers/usb/host/ehci-hcd.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/usb/host/ehci-hcd.c +12 -0
@@ -574,6 +574,7 @@ static int ehci_run (struct usb_hcd *hcdstruct ehci_hcd *ehci =hcd_to_ehci (hcd);u32 temp;u32 hcc_params; +int rc; hcd->uses_new_polling =1 ;
@@ -629,9 +630,20 @@ static int ehci_run (struct usb_hcd *hcddown_write (&ehci_cf_port_reset_rwsem); ehci->rh_state =EHCI_RH_RUNNING ;ehci_writel (ehci,FLAG_CF , &ehci->regs->configured_flag); + +/* Wait until HC become operational */ ehci_readl (ehci, &ehci->regs->command);/* unblock posted writes */ msleep (5 ); + rc =ehci_handshake (ehci, &ehci->regs->status,STS_HALT ,0 ,100 *1000 ); +up_write (&ehci_cf_port_reset_rwsem); + +if (rc) { +ehci_err (ehci,"USB %x.%x, controller refused to start: %d\n" , + ((ehci->sbrn &0xf0 )>>4 ), (ehci->sbrn &0x0f ), rc); +return rc; + } + ehci->last_periodic_enable =ktime_get_real (); temp =HC_VERSION (ehci,ehci_readl (ehci, &ehci->caps->hc_capbase));
Greg Kroah-Hartman
maintainerPATCH 60/86 USB: ehci: fix an interrupt calltrace error
In reply to Greg Kroah-HartmanFrom: Longfang Liu <[email protected]>
commit 643a4df7fe3f6831d14536fd692be85f92670a52 upstream.
The system that use Synopsys USB host controllers goes to suspend when using USB audio player. This causes the USB host controller continuous send interrupt signal to system, When the number of interrupts exceeds 100000, the system will forcibly close the interrupts and output a calltrace error.
When the system goes to suspend, the last interrupt is reported to the driver. At this time, the system has set the state to suspend. This causes the last interrupt to not be processed by the system and not clear the interrupt flag. This uncleared interrupt flag constantly triggers new interrupt event. This causing the driver to receive more than 100,000 interrupts, which causes the system to forcibly close the interrupt report and report the calltrace error.
so, when the driver goes to sleep and changes the system state to suspend, the interrupt flag needs to be cleared.
--- drivers/usb/host/ehci-hub.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/host/ehci-hub.c +3 -0
@@ -345,6 +345,9 @@ static int ehci_bus_suspend (struct usb_unlink_empty_async_suspended (ehci); +/* Some Synopsys controllers mistakenly leave IAA turned on */ +ehci_writel (ehci,STS_IAA , &ehci->regs->status); +/* Any IAA cycle that started before the suspend is now invalid */ end_iaa_cycle (ehci);ehci_handle_start_intr_unlinks (ehci);
Greg Kroah-Hartman
maintainerPATCH 61/86 usb: gadget: aspeed: fix stop dma register setting.
In reply to Greg Kroah-HartmanFrom: Ryan Chen <[email protected]>
commit 4e0dcf62ab4cf917d0cbe751b8bf229a065248d4 upstream.
The vhub engine has two dma mode, one is descriptor list, another is single stage DMA. Each mode has different stop register setting. Descriptor list operation (bit2) : 0 disable reset, 1: enable reset Single mode operation (bit0) : 0 : disable, 1: enable
--- drivers/usb/gadget/udc/aspeed-vhub/epn.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/usb/gadget/udc/aspeed-vhub/epn.c +4 -1
@@ -420,7 +420,10 @@ static void ast_vhub_stop_active_req(stru32 state, reg, loops;/* Stop DMA activity */ -writel (0 , ep->epn.regs +AST_VHUB_EP_DMA_CTLSTAT ); +if (ep->epn.desc_mode) +writel (VHUB_EP_DMA_CTRL_RESET , ep->epn.regs +AST_VHUB_EP_DMA_CTLSTAT ); +else +writel (0 , ep->epn.regs +AST_VHUB_EP_DMA_CTLSTAT );/* Wait for it to complete */ for (loops =0 ; loops <1000 ; loops++) {
Greg Kroah-Hartman
maintainerPATCH 62/86 usb: udc: core: Use lock when write to soft_connect
In reply to Greg Kroah-HartmanFrom: Thinh Nguyen <[email protected]>
commit c28095bc99073ddda65e4f31f6ae0d908d4d5cd8 upstream.
Use lock to guard against concurrent access for soft-connect/disconnect operations when writing to soft_connect sysfs.
--- drivers/usb/gadget/udc/core.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/usb/gadget/udc/core.c +10 -3
@@ -1477,10 +1477,13 @@ static ssize_t soft_connect_store(struct struct device_attribute *attr, const char *buf, size_t n) { struct usb_udc *udc = container_of(dev, struct usb_udc, dev); +ssize_t ret; +mutex_lock (&udc_lock);if (!udc->driver) {dev_err (dev,"soft-connect without a gadget driver\n" ); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto out; }if (sysfs_streq (buf,"connect" )) {
@@ -1491,10 +1494,14 @@ static ssize_t soft_connect_store(structusb_gadget_udc_stop (udc); }else {dev_err (dev,"unsupported command '%s'\n" , buf); -return -EINVAL ; + ret = -EINVAL ; + goto out; } -return n; + ret = n; +out: +mutex_unlock (&udc_lock); +return ret; }static DEVICE_ATTR_WO (soft_connect);
Greg Kroah-Hartman
maintainerPATCH 63/86 usb: bdc: Make bdc pci driver depend on BROKEN
In reply to Greg Kroah-HartmanFrom: Patrik Jakobsson <[email protected]>
commit ef02684c4e67d8c35ac83083564135bc7b1d3445 upstream.
The bdc pci driver is going to be removed due to it not existing in the wild. This patch turns off compilation of the driver so that stable kernels can also pick up the change. This helps the out-of-tree facetimehd webcam driver as the pci id conflicts with bdc.
--- drivers/usb/gadget/udc/bdc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/gadget/udc/bdc/Kconfig +1 -1
@@ -17,7 +17,7 @@ if USB_BDC_UDC comment "Platform Support" config USB_BDC_PCI tristate "BDC support for PCIe based platforms" - depends on USB_PCI + depends on USB_PCI && BROKEN default USB_BDC_UDC help Enable support for platforms which have BDC connected through PCIe, such as Lego3 FPGA platform.
Greg Kroah-Hartman
maintainerPATCH 64/86 xhci: make sure TRB is fully written before giving it to the controller
In reply to Greg Kroah-HartmanFrom: Mathias Nyman <[email protected]>
commit 576667bad341516edc4e18eb85acb0a2b4c9c9d9 upstream.
Once the command ring doorbell is rung the xHC controller will parse all command TRBs on the command ring that have the cycle bit set properly.
If the driver just started writing the next command TRB to the ring when hardware finished the previous TRB, then HW might fetch an incomplete TRB as long as its cycle bit set correctly.
A command TRB is 16 bytes (128 bits) long.
Driver writes the command TRB in four 32 bit chunks, with the chunk containing the cycle bit last. This does however not guarantee that chunks actually get written in that order.
This was detected in stress testing when canceling URBs with several connected USB devices.
Two consecutive "Set TR Dequeue pointer" commands got queued right after each other, and the second one was only partially written when the controller parsed it, causing the dequeue pointer to be set to bogus values. This was seen as error messages:
"Mismatch between completed Set TR Deq Ptr command & xHCI internal state"
Solution is to add a write memory barrier before writing the cycle bit.
--- drivers/usb/host/xhci-ring.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/host/xhci-ring.c +2 -0
@@ -2918,6 +2918,8 @@ static void queue_trb(struct xhci_hcd *x trb->field[0 ] =cpu_to_le32 (field1); trb->field[1 ] =cpu_to_le32 (field2); trb->field[2 ] =cpu_to_le32 (field3); +/* make sure TRB is fully written before giving it to the controller */ +wmb (); trb->field[3 ] =cpu_to_le32 (field4);trace_xhci_queue_trb (ring, trb);
Greg Kroah-Hartman
maintainerPATCH 65/86 xhci: tegra: Delay for disabling LFPS detector
In reply to Greg Kroah-HartmanFrom: JC Kuo <[email protected]>
commit da7e0c3c2909a3d9bf8acfe1db3cb213bd7febfb upstream.
Occasionally, we are seeing some SuperSpeed devices resumes right after being directed to U3. This commits add 500us delay to ensure LFPS detector is disabled before sending ACK to firmware.
[ 16.099363] tegra-xusb 70090000.usb: entering ELPG [ 16.104343] tegra-xusb 70090000.usb: 2-1 isn't suspended: 0x0c001203 [ 16.114576] tegra-xusb 70090000.usb: not all ports suspended: -16 [ 16.120789] tegra-xusb 70090000.usb: entering ELPG failed
The register write passes through a few flop stages of 32KHz clock domain. NVIDIA ASIC designer reviewed RTL and suggests 500us delay.
--- drivers/usb/host/xhci-tegra.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/usb/host/xhci-tegra.c +7 -0
@@ -562,6 +562,13 @@ static void tegra_xusb_mbox_handle(struc enable);if (err <0 )break ; + +/* +* wait 500us for LFPS detector to be disabled before +* sending ACK +*/ +if (!enable) +usleep_range (500 ,1000 ); }if (err <0 ) {
Greg Kroah-Hartman
maintainerPATCH 66/86 driver core: Extend device_is_dependent()
In reply to Greg Kroah-HartmanFrom: Rafael J. Wysocki <[email protected]>
commit 3d1cf435e201d1fd63e4346b141881aed086effd upstream.
If the device passed as the target (second argument) to device_is_dependent() is not completely registered (that is, it has been initialized, but not added yet), but the parent pointer of it is set, it may be missing from the list of the parent's children and device_for_each_child() called by device_is_dependent() cannot be relied on to catch that dependency.
For this reason, modify device_is_dependent() to check the ancestors of the target device by following its parent pointer in addition to the device_for_each_child() walk.
--- drivers/base/core.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
drivers/base/core.c +16 -1
@@ -106,6 +106,16 @@ int device_links_read_lock_held(void)#endif #endif /* !CONFIG_SRCU */ +static bool device_is_ancestor (struct device *dev,struct device *target) +{ +while (target->parent) { + target = target->parent; +if (dev == target) +return true; + } +return false; +} +/** * device_is_dependent - Check if one device depends on another one * @dev: Device to check dependencies for.
@@ -119,7 +129,12 @@ static int device_is_dependent(struct destruct device_link *link;int ret; -if (dev == target) +/* +* The "ancestors" check is needed to catch the case when the target +* device has not been completely initialized yet and it is still +* missing from the list of children of its parent device. +*/ +if (dev == target ||device_is_ancestor (dev, target))return 1 ; ret =device_for_each_child (dev, target, device_is_dependent);
Greg Kroah-Hartman
maintainerPATCH 67/86 pinctrl: ingenic: Fix JZ4760 support
In reply to Greg Kroah-HartmanFrom: Paul Cercueil <[email protected]>
commit 9a85c09a3f507b925d75cb0c7c8f364467038052 upstream.
- JZ4760 and JZ4760B have a similar register layout as the JZ4740, and don't use the new register layout, which was introduced with the JZ4770 SoC and not the JZ4760 or JZ4760B SoCs.
- The JZ4740 code path only expected two function modes to be configurable for each pin, and wouldn't work with more than two. Fix it for the JZ4760, which has four configurable function modes.
--- drivers/pinctrl/pinctrl-ingenic.c | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-)
drivers/pinctrl/pinctrl-ingenic.c +12 -12
@@ -1378,7 +1378,7 @@ static inline bool ingenic_gpio_get_valustatic void ingenic_gpio_set_value (struct ingenic_gpio_chip *jzgc,u8 offset,int value) { -if (jzgc->jzpc->version >=ID_JZ4760 ) +if (jzgc->jzpc->version >=ID_JZ4770 )ingenic_gpio_set_bit (jzgc,JZ4760_GPIO_PAT0 , offset, !!value);else ingenic_gpio_set_bit (jzgc,JZ4740_GPIO_DATA , offset, !!value);
@@ -1389,7 +1389,7 @@ static void irq_set_type(struct ingenic_ {u8 reg1, reg2; -if (jzgc->jzpc->version >=ID_JZ4760 ) { +if (jzgc->jzpc->version >=ID_JZ4770 ) { reg1 =JZ4760_GPIO_PAT1 ; reg2 =JZ4760_GPIO_PAT0 ; }else {
@@ -1464,7 +1464,7 @@ static void ingenic_gpio_irq_enable(strustruct ingenic_gpio_chip *jzgc =gpiochip_get_data (gc);int irq = irqd->hwirq; -if (jzgc->jzpc->version >=ID_JZ4760 ) +if (jzgc->jzpc->version >=ID_JZ4770 )ingenic_gpio_set_bit (jzgc,JZ4760_GPIO_INT , irq, true);else ingenic_gpio_set_bit (jzgc,JZ4740_GPIO_SELECT , irq, true);
@@ -1480,7 +1480,7 @@ static void ingenic_gpio_irq_disable(stringenic_gpio_irq_mask (irqd); -if (jzgc->jzpc->version >=ID_JZ4760 ) +if (jzgc->jzpc->version >=ID_JZ4770 )ingenic_gpio_set_bit (jzgc,JZ4760_GPIO_INT , irq, false);else ingenic_gpio_set_bit (jzgc,JZ4740_GPIO_SELECT , irq, false);
@@ -1505,7 +1505,7 @@ static void ingenic_gpio_irq_ack(structirq_set_type (jzgc, irq,IRQ_TYPE_LEVEL_HIGH ); } -if (jzgc->jzpc->version >=ID_JZ4760 ) +if (jzgc->jzpc->version >=ID_JZ4770 )ingenic_gpio_set_bit (jzgc,JZ4760_GPIO_FLAG , irq, false);else ingenic_gpio_set_bit (jzgc,JZ4740_GPIO_DATA , irq, true);
@@ -1562,7 +1562,7 @@ static void ingenic_gpio_irq_handler(strchained_irq_enter (irq_chip, desc); -if (jzgc->jzpc->version >=ID_JZ4760 ) +if (jzgc->jzpc->version >=ID_JZ4770 ) flag =ingenic_gpio_read_reg (jzgc,JZ4760_GPIO_FLAG );else flag =ingenic_gpio_read_reg (jzgc,JZ4740_GPIO_FLAG );
@@ -1643,7 +1643,7 @@ static int ingenic_gpio_get_direction(ststruct ingenic_pinctrl *jzpc = jzgc->jzpc;unsigned int pin = gc->base + offset; -if (jzpc->version >=ID_JZ4760 ) +if (jzpc->version >=ID_JZ4770 )return ingenic_get_pin_config (jzpc, pin,JZ4760_GPIO_INT ) ||ingenic_get_pin_config (jzpc, pin,JZ4760_GPIO_PAT1 );
@@ -1676,7 +1676,7 @@ static int ingenic_pinmux_set_pin_fn(stringenic_shadow_config_pin (jzpc, pin,JZ4760_GPIO_PAT1 , func &0x2 );ingenic_shadow_config_pin (jzpc, pin,JZ4760_GPIO_PAT0 , func &0x1 );ingenic_shadow_config_pin_load (jzpc, pin); - }else if (jzpc->version >=ID_JZ4760 ) { + }else if (jzpc->version >=ID_JZ4770 ) {ingenic_config_pin (jzpc, pin,JZ4760_GPIO_INT , false);ingenic_config_pin (jzpc, pin,GPIO_MSK , false);ingenic_config_pin (jzpc, pin,JZ4760_GPIO_PAT1 , func &0x2 );
@@ -1684,7 +1684,7 @@ static int ingenic_pinmux_set_pin_fn(str }else {ingenic_config_pin (jzpc, pin,JZ4740_GPIO_FUNC , true);ingenic_config_pin (jzpc, pin,JZ4740_GPIO_TRIG , func &0x2 ); -ingenic_config_pin (jzpc, pin,JZ4740_GPIO_SELECT , func >0 ); +ingenic_config_pin (jzpc, pin,JZ4740_GPIO_SELECT , func &0x1 ); }return 0 ;
@@ -1734,7 +1734,7 @@ static int ingenic_pinmux_gpio_set_direcingenic_shadow_config_pin (jzpc, pin,GPIO_MSK , true);ingenic_shadow_config_pin (jzpc, pin,JZ4760_GPIO_PAT1 , input);ingenic_shadow_config_pin_load (jzpc, pin); - }else if (jzpc->version >=ID_JZ4760 ) { + }else if (jzpc->version >=ID_JZ4770 ) {ingenic_config_pin (jzpc, pin,JZ4760_GPIO_INT , false);ingenic_config_pin (jzpc, pin,GPIO_MSK , true);ingenic_config_pin (jzpc, pin,JZ4760_GPIO_PAT1 , input);
@@ -1764,7 +1764,7 @@ static int ingenic_pinconf_get(struct piunsigned int offt = pin /PINS_PER_GPIO_CHIP ;bool pull; -if (jzpc->version >=ID_JZ4760 ) +if (jzpc->version >=ID_JZ4770 ) pull = !ingenic_get_pin_config (jzpc, pin,JZ4760_GPIO_PEN );else pull = !ingenic_get_pin_config (jzpc, pin,JZ4740_GPIO_PULL_DIS );
@@ -1796,7 +1796,7 @@ static int ingenic_pinconf_get(struct pistatic void ingenic_set_bias (struct ingenic_pinctrl *jzpc,unsigned int pin,bool enabled) { -if (jzpc->version >=ID_JZ4760 ) +if (jzpc->version >=ID_JZ4770 )ingenic_config_pin (jzpc, pin,JZ4760_GPIO_PEN , !enabled);else ingenic_config_pin (jzpc, pin,JZ4740_GPIO_PULL_DIS , !enabled);
Greg Kroah-Hartman
maintainerPATCH 68/86 x86/cpu/amd: Set __max_die_per_package on AMD
In reply to Greg Kroah-HartmanFrom: Yazen Ghannam <[email protected]>
commit 76e2fc63ca40977af893b724b00cc2f8e9ce47a4 upstream.
Set the maximum DIE per package variable on AMD using the NodesPerProcessor topology value. This will be used by RAPL, among others, to determine the maximum number of DIEs on the system in order to do per-DIE manipulations.
[ bp: Productize into a proper patch. ]
--- arch/x86/kernel/cpu/amd.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/amd.c +2 -2
@@ -545,12 +545,12 @@ static void bsp_init_amd(struct cpuinfo_u32 ecx; ecx =cpuid_ecx (0x8000001e ); - nodes_per_socket = ((ecx >>8 ) &7 ) +1 ; + __max_die_per_package = nodes_per_socket = ((ecx >>8 ) &7 ) +1 ; }else if (boot_cpu_has (X86_FEATURE_NODEID_MSR )) {u64 value;rdmsrl (MSR_FAM10H_NODE_ID , value); - nodes_per_socket = ((value >>3 ) &7 ) +1 ; + __max_die_per_package = nodes_per_socket = ((value >>3 ) &7 ) +1 ; } if (!boot_cpu_has(X86_FEATURE_AMD_SSBD) &&
Greg Kroah-Hartman
maintainerPATCH 69/86 netfilter: rpfilter: mask ecn bits before fib lookup
In reply to Greg Kroah-HartmanFrom: Guillaume Nault <[email protected]>
commit 2e5a6266fbb11ae93c468dfecab169aca9c27b43 upstream.
RT_TOS() only masks one of the two ECN bits. Therefore rpfilter_mt() treats Not-ECT or ECT(1) packets in a different way than those with ECT(0) or CE.
Reproducer:
Create two netns, connected with a veth:
$ ip netns add ns0 $ ip netns add ns1 $ ip link add name veth01 netns ns0 type veth peer name veth10 netns ns1 $ ip -netns ns0 link set dev veth01 up $ ip -netns ns1 link set dev veth10 up $ ip -netns ns0 address add 192.0.2.10/32 dev veth01 $ ip -netns ns1 address add 192.0.2.11/32 dev veth10
Add a route to ns1 in ns0:
$ ip -netns ns0 route add 192.0.2.11/32 dev veth01
In ns1, only packets with TOS 4 can be routed to ns0:
$ ip -netns ns1 route add 192.0.2.10/32 tos 4 dev veth10
Ping from ns0 to ns1 works regardless of the ECN bits, as long as TOS is 4:
$ ip netns exec ns0 ping -Q 4 192.0.2.11 # TOS 4, Not-ECT
... 0% packet loss ...
$ ip netns exec ns0 ping -Q 5 192.0.2.11 # TOS 4, ECT(1)
... 0% packet loss ...
$ ip netns exec ns0 ping -Q 6 192.0.2.11 # TOS 4, ECT(0)
... 0% packet loss ...
$ ip netns exec ns0 ping -Q 7 192.0.2.11 # TOS 4, CE
... 0% packet loss ...Now use iptable's rpfilter module in ns1:
$ ip netns exec ns1 iptables-legacy -t raw -A PREROUTING -m rpfilter --invert -j DROP
Not-ECT and ECT(1) packets still pass:
$ ip netns exec ns0 ping -Q 4 192.0.2.11 # TOS 4, Not-ECT
... 0% packet loss ...
$ ip netns exec ns0 ping -Q 5 192.0.2.11 # TOS 4, ECT(1)
... 0% packet loss ...But ECT(0) and ECN packets are dropped:
$ ip netns exec ns0 ping -Q 6 192.0.2.11 # TOS 4, ECT(0)
... 100% packet loss ...
$ ip netns exec ns0 ping -Q 7 192.0.2.11 # TOS 4, CE
... 100% packet loss ...After this patch, rpfilter doesn't drop ECT(0) and CE packets anymore.
--- net/ipv4/netfilter/ipt_rpfilter.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/netfilter/ipt_rpfilter.c +1 -1
@@ -76,7 +76,7 @@ static bool rpfilter_mt(const struct sk_ flow.daddr = iph->saddr; flow.saddr =rpfilter_get_saddr (iph->daddr); flow.flowi4_mark = info->flags &XT_RPFILTER_VALID_MARK ? skb->mark :0 ; - flow.flowi4_tos =RT_TOS (iph->tos); + flow.flowi4_tos = iph->tos &IPTOS_RT_MASK ; flow.flowi4_scope =RT_SCOPE_UNIVERSE ; flow.flowi4_oif =l3mdev_master_ifindex_rcu (xt_in (par));
Greg Kroah-Hartman
maintainerPATCH 70/86 sh: dma: fix kconfig dependency for G2_DMA
In reply to Greg Kroah-HartmanFrom: Necip Fazil Yildiran <[email protected]>
commit f477a538c14d07f8c45e554c8c5208d588514e98 upstream.
When G2_DMA is enabled and SH_DMA is disabled, it results in the following Kbuild warning:
WARNING: unmet direct dependencies detected for SH_DMA_API
Depends on [n]: SH_DMA [=n]
Selected by [y]:
- G2_DMA [=y] && SH_DREAMCAST [=y]
The reason is that G2_DMA selects SH_DMA_API without depending on or selecting SH_DMA while SH_DMA_API depends on SH_DMA.
When G2_DMA was first introduced with commit 40f49e7ed77f ("sh: dma: Make G2 DMA configurable."), this wasn't an issue since SH_DMA_API didn't have such dependency, and this way was the only way to enable it since SH_DMA_API was non-visible. However, later SH_DMA_API was made visible and dependent on SH_DMA with commit d8902adcc1a9 ("dmaengine: sh: Add Support SuperH DMA Engine driver").
Let G2_DMA depend on SH_DMA_API instead to avoid Kbuild issues.
--- arch/sh/drivers/dma/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/sh/drivers/dma/Kconfig +1 -2
@@ -63,8 +63,7 @@ config PVR2_DMA config G2_DMA tristate "G2 Bus DMA support" - depends on SH_DREAMCAST - select SH_DMA_API + depends on SH_DREAMCAST && SH_DMA_API help This enables support for the DMA controller for the Dreamcast's G2 bus. Drivers that want this will generally enable this on
Greg Kroah-Hartman
maintainerPATCH 71/86 net: dsa: mv88e6xxx: also read STU state in mv88e6250_g1_vtu_getnext
In reply to Greg Kroah-HartmanFrom: Rasmus Villemoes <[email protected]>
commit 87fe04367d842c4d97a77303242d4dd4ac351e46 upstream.
mv88e6xxx_port_vlan_join checks whether the VTU already contains an entry for the given vid (via mv88e6xxx_vtu_getnext), and if so, merely changes the relevant .member[] element and loads the updated entry into the VTU.
However, at least for the mv88e6250, the on-stack struct mv88e6xxx_vtu_entry vlan never has its .state[] array explicitly initialized, neither in mv88e6xxx_port_vlan_join() nor inside the getnext implementation. So the new entry has random garbage for the STU bits, breaking VLAN filtering.
When the VTU entry is initially created, those bits are all zero, and we should make sure to keep them that way when the entry is updated.
--- drivers/net/dsa/mv88e6xxx/global1_vtu.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/dsa/mv88e6xxx/global1_vtu.c +4 -0
@@ -351,6 +351,10 @@ int mv88e6250_g1_vtu_getnext(struct mv88if (err)return err; + err =mv88e6185_g1_stu_data_read (chip, entry); +if (err) +return err; +/* VTU DBNum[3:0] are located in VTU Operation 3:0 * VTU DBNum[5:4] are located in VTU Operation 9:8 */
Greg Kroah-Hartman
maintainerPATCH 72/86 sh_eth: Fix power down vs. is_opened flag ordering
In reply to Greg Kroah-HartmanFrom: Geert Uytterhoeven <[email protected]>
commit f6a2e94b3f9d89cb40771ff746b16b5687650cbb upstream.
sh_eth_close() does a synchronous power down of the device before marking it closed. Revert the order, to make sure the device is never marked opened while suspended.
While at it, use pm_runtime_put() instead of pm_runtime_put_sync(), as there is no reason to do a synchronous power down.
--- drivers/net/ethernet/renesas/sh_eth.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/renesas/sh_eth.c +2 -2
@@ -2640,10 +2640,10 @@ static int sh_eth_close(struct net_devic/* Free all the skbuffs in the Rx queue and the DMA buffer. */ sh_eth_ring_free (ndev); -pm_runtime_put_sync (&mdp->pdev->dev); - mdp->is_opened =0 ; +pm_runtime_put (&mdp->pdev->dev); +return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 73/86 lightnvm: fix memory leak when submit fails
In reply to Greg Kroah-HartmanFrom: Pan Bian <[email protected]>
commit 97784481757fba7570121a70dd37ca74a29f50a8 upstream.
The allocated page is not released if error occurs in nvm_submit_io_sync_raw(). __free_page() is moved ealier to avoid possible memory leak issue.
--- drivers/lightnvm/core.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/lightnvm/core.c +1 -2
@@ -849,11 +849,10 @@ static int nvm_bb_chunk_sense(struct nvm rqd.ppa_addr =generic_to_dev_addr (dev, ppa); ret =nvm_submit_io_sync_raw (dev, &rqd); +__free_page (page);if (ret)return ret; -__free_page (page); -return rqd.error; }
Greg Kroah-Hartman
maintainerPATCH 74/86 skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
In reply to Greg Kroah-HartmanFrom: Alexander Lobakin <[email protected]>
commit 66c556025d687dbdd0f748c5e1df89c977b6c02a upstream.
Commit 3226b158e67c ("net: avoid 32 x truesize under-estimation for tiny skbs") ensured that skbs with data size lower than 1025 bytes will be kmalloc'ed to avoid excessive page cache fragmentation and memory consumption.
However, the fix adressed only __napi_alloc_skb() (primarily for virtio_net and napi_get_frags()), but the issue can still be achieved through __netdev_alloc_skb(), which is still used by several drivers. Drivers often allocate a tiny skb for headers and place the rest of the frame to frags (so-called copybreak).
Mirror the condition to __netdev_alloc_skb() to handle this case too.
Since v1 [0]:
- fix "Fixes:" tag;
- refine commit message (mention copybreak usecase).
[0] https://lore.kernel.org/netdev/[email protected]
--- net/core/skbuff.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
net/core/skbuff.c +5 -1
@@ -431,7 +431,11 @@ struct sk_buff *__netdev_alloc_skb(struc len +=NET_SKB_PAD ; -if ((len >SKB_WITH_OVERHEAD (PAGE_SIZE )) || +/* If requested length is either too small or too big, +* we use kmalloc() for skb->head allocation. +*/ +if (len <=SKB_WITH_OVERHEAD (1024 ) || + len >SKB_WITH_OVERHEAD (PAGE_SIZE ) || (gfp_mask & (__GFP_DIRECT_RECLAIM |GFP_DMA ))) { skb =__alloc_skb (len, gfp_mask,SKB_ALLOC_RX ,NUMA_NO_NODE );if (!skb)
Greg Kroah-Hartman
maintainerPATCH 75/86 kasan: fix unaligned address is unhandled in kasan_remove_zero_shadow
In reply to Greg Kroah-HartmanFrom: Lecopzer Chen <[email protected]>
commit a11a496ee6e2ab6ed850233c96b94caf042af0b9 upstream.
During testing kasan_populate_early_shadow and kasan_remove_zero_shadow, if the shadow start and end address in kasan_remove_zero_shadow() is not aligned to PMD_SIZE, the remain unaligned PTE won't be removed.
In the test case for kasan_remove_zero_shadow():
shadow_start: 0xffffffb802000000, shadow end: 0xffffffbfbe000000
3-level page table:
PUD_SIZE: 0x40000000 PMD_SIZE: 0x200000 PAGE_SIZE: 4K0xffffffbf80000000 ~ 0xffffffbfbdf80000 will not be removed because in kasan_remove_pud_table(), kasan_pmd_table(*pud) is true but the next address is 0xffffffbfbdf80000 which is not aligned to PUD_SIZE.
In the correct condition, this should fallback to the next level kasan_remove_pmd_table() but the condition flow always continue to skip the unaligned part.
Fix by correcting the condition when next and addr are neither aligned.
--- mm/kasan/init.c | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-)
mm/kasan/init.c +12 -8
@@ -388,9 +388,10 @@ static void kasan_remove_pmd_table(pmd_tif (kasan_pte_table (*pmd)) {if (IS_ALIGNED (addr,PMD_SIZE ) && -IS_ALIGNED (next,PMD_SIZE )) +IS_ALIGNED (next,PMD_SIZE )) {pmd_clear (pmd); -continue ; +continue ; + } } pte =pte_offset_kernel (pmd, addr);kasan_remove_pte_table (pte, addr, next);
@@ -413,9 +414,10 @@ static void kasan_remove_pud_table(pud_tif (kasan_pmd_table (*pud)) {if (IS_ALIGNED (addr,PUD_SIZE ) && -IS_ALIGNED (next,PUD_SIZE )) +IS_ALIGNED (next,PUD_SIZE )) {pud_clear (pud); -continue ; +continue ; + } } pmd =pmd_offset (pud, addr); pmd_base =pmd_offset (pud,0 );
@@ -439,9 +441,10 @@ static void kasan_remove_p4d_table(p4d_tif (kasan_pud_table (*p4d)) {if (IS_ALIGNED (addr,P4D_SIZE ) && -IS_ALIGNED (next,P4D_SIZE )) +IS_ALIGNED (next,P4D_SIZE )) {p4d_clear (p4d); -continue ; +continue ; + } } pud =pud_offset (p4d, addr);kasan_remove_pud_table (pud, addr, next);
@@ -473,9 +476,10 @@ void kasan_remove_zero_shadow(void *starif (kasan_p4d_table (*pgd)) {if (IS_ALIGNED (addr,PGDIR_SIZE ) && -IS_ALIGNED (next,PGDIR_SIZE )) +IS_ALIGNED (next,PGDIR_SIZE )) {pgd_clear (pgd); -continue ; +continue ; + } } p4d =p4d_offset (pgd, addr);
Greg Kroah-Hartman
maintainerPATCH 76/86 kasan: fix incorrect arguments passing in kasan_add_zero_shadow
In reply to Greg Kroah-HartmanFrom: Lecopzer Chen <[email protected]>
commit 5dabd1712cd056814f9ab15f1d68157ceb04e741 upstream.
kasan_remove_zero_shadow() shall use original virtual address, start and size, instead of shadow address.
--- mm/kasan/init.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
mm/kasan/init.c +1 -2
@@ -503,7 +503,6 @@ int kasan_add_zero_shadow(void *start, u ret =kasan_populate_early_shadow (shadow_start, shadow_end);if (ret) -kasan_remove_zero_shadow (shadow_start, - size >>KASAN_SHADOW_SCALE_SHIFT ); +kasan_remove_zero_shadow (start, size);return ret; }
Greg Kroah-Hartman
maintainerPATCH 77/86 udp: mask TOS bits in udp_v4_early_demux()
In reply to Greg Kroah-HartmanFrom: Guillaume Nault <[email protected]>
commit 8d2b51b008c25240914984208b2ced57d1dd25a5 upstream.
udp_v4_early_demux() is the only function that calls ip_mc_validate_source() with a TOS that hasn't been masked with IPTOS_RT_MASK.
This results in different behaviours for incoming multicast UDPv4 packets, depending on if ip_mc_validate_source() is called from the early-demux path (udp_v4_early_demux) or from the regular input path (ip_route_input_noref).
ECN would normally not be used with UDP multicast packets, so the practical consequences should be limited on that side. However, IPTOS_RT_MASK is used to also masks the TOS' high order bits, to align with the non-early-demux path behaviour.
Reproducer:
Setup two netns, connected with veth:
$ ip netns add ns0 $ ip netns add ns1 $ ip -netns ns0 link set dev lo up $ ip -netns ns1 link set dev lo up $ ip link add name veth01 netns ns0 type veth peer name veth10 netns ns1 $ ip -netns ns0 link set dev veth01 up $ ip -netns ns1 link set dev veth10 up $ ip -netns ns0 address add 192.0.2.10 peer 192.0.2.11/32 dev veth01 $ ip -netns ns1 address add 192.0.2.11 peer 192.0.2.10/32 dev veth10
In ns0, add route to multicast address 224.0.2.0/24 using source address 198.51.100.10:
$ ip -netns ns0 address add 198.51.100.10/32 dev lo $ ip -netns ns0 route add 224.0.2.0/24 dev veth01 src 198.51.100.10
In ns1, define route to 198.51.100.10, only for packets with TOS 4:
$ ip -netns ns1 route add 198.51.100.10/32 tos 4 dev veth10
Also activate rp_filter in ns1, so that incoming packets not matching the above route get dropped:
$ ip netns exec ns1 sysctl -wq net.ipv4.conf.veth10.rp_filter=1
Now try to receive packets on 224.0.2.11:
$ ip netns exec ns1 socat UDP-RECVFROM:1111,ip-add-membership=224.0.2.11:veth10,ignoreeof -
In ns0, send packet to 224.0.2.11 with TOS 4 and ECT(0) (that is, tos 6 for socat):
$ echo test0 | ip netns exec ns0 socat - UDP-DATAGRAM:224.0.2.11:1111,bind=:1111,tos=6
The "test0" message is properly received by socat in ns1, because early-demux has no cached dst to use, so source address validation is done by ip_route_input_mc(), which receives a TOS that has the ECN bits masked.
Now send another packet to 224.0.2.11, still with TOS 4 and ECT(0):
$ echo test1 | ip netns exec ns0 socat - UDP-DATAGRAM:224.0.2.11:1111,bind=:1111,tos=6
The "test1" message isn't received by socat in ns1, because, now, early-demux has a cached dst to use and calls ip_mc_validate_source() immediately, without masking the ECN bits.
--- net/ipv4/udp.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/ipv4/udp.c +2 -1
@@ -2495,7 +2495,8 @@ int udp_v4_early_demux(struct sk_buff *s*/ if (!inet_sk (sk)->inet_daddr && in_dev)return ip_mc_validate_source (skb, iph->daddr, - iph->saddr, iph->tos, + iph->saddr, + iph->tos &IPTOS_RT_MASK , skb->dev, in_dev, &itag); }return 0 ;
Greg Kroah-Hartman
maintainerPATCH 78/86 ipv6: create multicast route with RTPROT_KERNEL
In reply to Greg Kroah-HartmanFrom: Matteo Croce <[email protected]>
commit a826b04303a40d52439aa141035fca5654ccaccd upstream.
The ff00::/8 multicast route is created without specifying the fc_protocol field, so the default RTPROT_BOOT value is used:
$ ip -6 -d route unicast ::1 dev lo proto kernel scope global metric 256 pref medium unicast fe80::/64 dev eth0 proto kernel scope global metric 256 pref medium unicast ff00::/8 dev eth0 proto boot scope global metric 256 pref medium
As the documentation says, this value identifies routes installed during boot, but the route is created when interface is set up. Change the value to RTPROT_KERNEL which is a better value.
--- net/ipv6/addrconf.c | 1 + 1 file changed, 1 insertion(+)
net/ipv6/addrconf.c +1 -0
@@ -2454,6 +2454,7 @@ static void addrconf_add_mroute(struct n .fc_flags = RTF_UP, .fc_type = RTN_UNICAST, .fc_nlinfo.nl_net = dev_net(dev), + .fc_protocol = RTPROT_KERNEL, };ipv6_addr_set (&cfg.fc_dst,htonl (0xFF000000 ),0 ,0 ,0 );
Greg Kroah-Hartman
maintainerPATCH 79/86 net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
commit bcd0cf19ef8258ac31b9a20248b05c15a1f4b4b0 upstream.
tc_index being 16bit wide, we need to check that TCA_TCINDEX_SHIFT attribute is not silly.
UBSAN: shift-out-of-bounds in net/sched/cls_tcindex.c:260:29 shift exponent 255 is too large for 32-bit type 'int' CPU: 0 PID: 8516 Comm: syz-executor228 Not tainted 5.10.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x107/0x163 lib/dump_stack.c:120 ubsan_epilogue+0xb/0x5a lib/ubsan.c:148 __ubsan_handle_shift_out_of_bounds.cold+0xb1/0x181 lib/ubsan.c:395 valid_perfect_hash net/sched/cls_tcindex.c:260 [inline] tcindex_set_parms.cold+0x1b/0x215 net/sched/cls_tcindex.c:425 tcindex_change+0x232/0x340 net/sched/cls_tcindex.c:546 tc_new_tfilter+0x13fb/0x21b0 net/sched/cls_api.c:2127 rtnetlink_rcv_msg+0x8b6/0xb80 net/core/rtnetlink.c:5555 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2494 netlink_unicast_kernel net/netlink/af_netlink.c:1304 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1330 netlink_sendmsg+0x907/0xe40 net/netlink/af_netlink.c:1919 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:672 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2336 ___sys_sendmsg+0xf3/0x170 net/socket.c:2390 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2423 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9
--- net/sched/cls_tcindex.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
net/sched/cls_tcindex.c +6 -2
@@ -366,9 +366,13 @@ tcindex_set_parms(struct net *net, strucif (tb[TCA_TCINDEX_MASK ]) cp->mask =nla_get_u16 (tb[TCA_TCINDEX_MASK ]); -if (tb[TCA_TCINDEX_SHIFT ]) +if (tb[TCA_TCINDEX_SHIFT ]) { cp->shift =nla_get_u32 (tb[TCA_TCINDEX_SHIFT ]); - +if (cp->shift >16 ) { + err = -EINVAL ; + goto errout; + } + }if (!cp->hash) {/* Hash not specified, use perfect hash if the upper limit * of the hashing index is below the threshold.
Greg Kroah-Hartman
maintainerPATCH 80/86 net_sched: reject silly cell_log in qdisc_get_rtab()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
commit e4bedf48aaa5552bc1f49703abd17606e7e6e82a upstream.
iproute2 probably never goes beyond 8 for the cell exponent, but stick to the max shift exponent for signed 32bit.
UBSAN reported:
UBSAN: shift-out-of-bounds in net/sched/sch_api.c:389:22 shift exponent 130 is too large for 32-bit type 'int' CPU: 1 PID: 8450 Comm: syz-executor586 Not tainted 5.11.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x183/0x22e lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:148 [inline] __ubsan_handle_shift_out_of_bounds+0x432/0x4d0 lib/ubsan.c:395 __detect_linklayer+0x2a9/0x330 net/sched/sch_api.c:389 qdisc_get_rtab+0x2b5/0x410 net/sched/sch_api.c:435 cbq_init+0x28f/0x12c0 net/sched/sch_cbq.c:1180 qdisc_create+0x801/0x1470 net/sched/sch_api.c:1246 tc_modify_qdisc+0x9e3/0x1fc0 net/sched/sch_api.c:1662 rtnetlink_rcv_msg+0xb1d/0xe60 net/core/rtnetlink.c:5564 netlink_rcv_skb+0x1f0/0x460 net/netlink/af_netlink.c:2494 netlink_unicast_kernel net/netlink/af_netlink.c:1304 [inline] netlink_unicast+0x7de/0x9b0 net/netlink/af_netlink.c:1330 netlink_sendmsg+0xaa6/0xe90 net/netlink/af_netlink.c:1919 sock_sendmsg_nosec net/socket.c:652 [inline] sock_sendmsg net/socket.c:672 [inline] ____sys_sendmsg+0x5a2/0x900 net/socket.c:2345 ___sys_sendmsg net/socket.c:2399 [inline] __sys_sendmsg+0x319/0x400 net/socket.c:2432 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xa9
--- net/sched/sch_api.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/sched/sch_api.c +2 -1
@@ -409,7 +409,8 @@ struct qdisc_rate_table *qdisc_get_rtab( {struct qdisc_rate_table *rtab; -if (tab ==NULL || r->rate ==0 || r->cell_log ==0 || +if (tab ==NULL || r->rate ==0 || + r->cell_log ==0 || r->cell_log >=32 ||nla_len (tab) !=TC_RTAB_SIZE ) {NL_SET_ERR_MSG (extack,"Invalid rate table parameters for searching" );return NULL ;
Greg Kroah-Hartman
maintainerPATCH 81/86 ipv6: set multicast flag on the multicast route
In reply to Greg Kroah-HartmanFrom: Matteo Croce <[email protected]>
commit ceed9038b2783d14e0422bdc6fd04f70580efb4c upstream.
The multicast route ff00::/8 is created with type RTN_UNICAST:
$ ip -6 -d route unicast ::1 dev lo proto kernel scope global metric 256 pref medium unicast fe80::/64 dev eth0 proto kernel scope global metric 256 pref medium unicast ff00::/8 dev eth0 proto kernel scope global metric 256 pref medium
Set the type to RTN_MULTICAST which is more appropriate.
--- net/ipv6/addrconf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv6/addrconf.c +1 -1
@@ -2452,7 +2452,7 @@ static void addrconf_add_mroute(struct n .fc_ifindex = dev->ifindex, .fc_dst_len = 8, .fc_flags = RTF_UP, - .fc_type = RTN_UNICAST, + .fc_type = RTN_MULTICAST, .fc_nlinfo.nl_net = dev_net(dev), .fc_protocol = RTPROT_KERNEL, };
Greg Kroah-Hartman
maintainerPATCH 82/86 net: mscc: ocelot: allow offloading of bridge on top of LAG
In reply to Greg Kroah-HartmanFrom: Vladimir Oltean <[email protected]>
commit 79267ae22615496655feee2db0848f6786bcf67a upstream.
The blamed commit was too aggressive, and it made ocelot_netdevice_event react only to network interface events emitted for the ocelot switch ports.
In fact, only the PRECHANGEUPPER should have had that check.
When we ignore all events that are not for us, we miss the fact that the upper of the LAG changes, and the bonding interface gets enslaved to a bridge. This is an operation we could offload under certain conditions.
--- drivers/net/ethernet/mscc/ocelot.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/net/ethernet/mscc/ocelot.c +1 -3
@@ -1716,10 +1716,8 @@ static int ocelot_netdevice_event(structstruct net_device *dev =netdev_notifier_info_to_dev (ptr);int ret =0 ; -if (!ocelot_netdevice_dev_check (dev)) -return 0 ; -if (event ==NETDEV_PRECHANGEUPPER && +ocelot_netdevice_dev_check (dev) &&netif_is_lag_master (info->upper_dev)) {struct netdev_lag_upper_info *lag_upper_info = info->upper_info;struct netlink_ext_ack *extack;
Greg Kroah-Hartman
maintainerPATCH 83/86 net: Disable NETIF_F_HW_TLS_RX when RXCSUM is disabled
In reply to Greg Kroah-HartmanFrom: Tariq Toukan <[email protected]>
commit a3eb4e9d4c9218476d05c52dfd2be3d6fdce6b91 upstream.
With NETIF_F_HW_TLS_RX packets are decrypted in HW. This cannot be logically done when RXCSUM offload is off.
--- net/core/dev.c | 5 +++++ 1 file changed, 5 insertions(+)
net/core/dev.c +5 -0
@@ -8692,6 +8692,11 @@ static netdev_features_t netdev_fix_feat } } +if ((features &NETIF_F_HW_TLS_RX ) && !(features &NETIF_F_RXCSUM )) { +netdev_dbg (dev,"Dropping TLS RX HW offload feature since no RXCSUM feature.\n" ); + features &= ~NETIF_F_HW_TLS_RX ; + } +return features; }
Greg Kroah-Hartman
maintainerPATCH 84/86 net: dsa: b53: fix an off by one in checking "vlan->vid"
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
commit 8e4052c32d6b4b39c1e13c652c7e33748d447409 upstream.
The > comparison should be >= to prevent accessing one element beyond the end of the dev->vlans[] array in the caller function, b53_vlan_add(). The "dev->vlans" array is allocated in the b53_switch_init() function and it has "dev->num_vlans" elements.
--- drivers/net/dsa/b53/b53_common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/dsa/b53/b53_common.c +1 -1
@@ -1330,7 +1330,7 @@ int b53_vlan_prepare(struct dsa_switch *if ((is5325 (dev) ||is5365 (dev)) && vlan->vid_begin ==0 )return -EOPNOTSUPP ; -if (vlan->vid_end > dev->num_vlans) +if (vlan->vid_end >= dev->num_vlans)return -ERANGE ;b53_enable_vlan (dev, true, ds->vlan_filtering);
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.93 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 27 Jan 2021 18:31:44 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.93-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.4:
12 builds: 12 pass, 0 fail
26 boots: 26 pass, 0 fail
56 tests: 56 pass, 0 failLinux version: 5.4.93-rc1-g3deaa28e41d9
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04Jon
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.93 release. There are 86 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 27 Jan 2021 18:31:44 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.93-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.4:
12 builds: 12 pass, 0 fail
26 boots: 26 pass, 0 fail
56 tests: 56 pass, 0 failLinux version: 5.4.93-rc1-g3deaa28e41d9
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04Jon
Greg Kroah-Hartman
maintainerPATCH 85/86 tcp: do not mess with cloned skbs in tcp_add_backlog()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
commit b160c28548bc0a87cbd16d5af6d3edcfd70b8c9a upstream.
Heiner Kallweit reported that some skbs were sent with the following invalid GSO properties :
- gso_size > 0
- gso_type == 0
This was triggerring a WARN_ON_ONCE() in rtl8169_tso_csum_v2.
Juerg Haefliger was able to reproduce a similar issue using a lan78xx NIC and a workload mixing TCP incoming traffic and forwarded packets.
The problem is that tcp_add_backlog() is writing
over gso_segs and gso_size even if the incoming packet will not be coalesced to the backlog tail packet.
While skb_try_coalesce() would bail out if tail packet is cloned, this overwriting would lead to corruptions of other packets cooked by lan78xx, sharing a common super-packet.
The strategy used by lan78xx is to use a big skb, and split it into all received packets using skb_clone() to avoid copies. The drawback of this strategy is that all the small skb share a common struct skb_shared_info.
This patch rewrites TCP gso_size/gso_segs handling to only happen on the tail skb, since skb_try_coalesce() made sure it was not cloned.
--- net/ipv4/tcp_ipv4.c | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-)
net/ipv4/tcp_ipv4.c +13 -12
@@ -1657,6 +1657,7 @@ int tcp_v4_early_demux(struct sk_buff *sbool tcp_add_backlog (struct sock *sk,struct sk_buff *skb) {u32 limit =READ_ONCE (sk->sk_rcvbuf) +READ_ONCE (sk->sk_sndbuf); +u32 tail_gso_size, tail_gso_segs;struct skb_shared_info *shinfo;const struct tcphdr *th;struct tcphdr *thtail;
@@ -1664,6 +1665,7 @@ bool tcp_add_backlog(struct sock *sk, stunsigned int hdrlen;bool fragstolen;u32 gso_segs; +u32 gso_size;int delta;/* In case all data was pulled from skb frags (in __pskb_pull_tail()),
@@ -1689,13 +1691,6 @@ bool tcp_add_backlog(struct sock *sk, st*/ th = (const struct tcphdr *)skb->data; hdrlen = th->doff *4 ; - shinfo =skb_shinfo (skb); - -if (!shinfo->gso_size) - shinfo->gso_size = skb->len - hdrlen; - -if (!shinfo->gso_segs) - shinfo->gso_segs =1 ; tail = sk->sk_backlog.tail;if (!tail)
@@ -1718,6 +1713,15 @@ bool tcp_add_backlog(struct sock *sk, st goto no_coalesce;__skb_pull (skb, hdrlen); + + shinfo =skb_shinfo (skb); + gso_size = shinfo->gso_size ?: skb->len; + gso_segs = shinfo->gso_segs ?:1 ; + + shinfo =skb_shinfo (tail); + tail_gso_size = shinfo->gso_size ?: (tail->len - hdrlen); + tail_gso_segs = shinfo->gso_segs ?:1 ; +if (skb_try_coalesce (tail, skb, &fragstolen, &delta)) {TCP_SKB_CB (tail)->end_seq =TCP_SKB_CB (skb)->end_seq;
@@ -1744,11 +1748,8 @@ bool tcp_add_backlog(struct sock *sk, st }/* Not as strict as GRO. We only need to carry mss max value */ -skb_shinfo (tail)->gso_size =max (shinfo->gso_size, -skb_shinfo (tail)->gso_size); - - gso_segs =skb_shinfo (tail)->gso_segs + shinfo->gso_segs; -skb_shinfo (tail)->gso_segs =min_t (u32, gso_segs,0xFFFF ); + shinfo->gso_size =max (gso_size, tail_gso_size); + shinfo->gso_segs =min_t (u32, gso_segs + tail_gso_segs,0xFFFF ); sk->sk_backlog.len += delta; __NET_INC_STATS(sock_net(sk),
Greg Kroah-Hartman
maintainerPATCH 86/86 tcp: fix TCP_USER_TIMEOUT with zero window
In reply to Greg Kroah-HartmanFrom: Enke Chen <[email protected]>
commit 9d9b1ee0b2d1c9e02b2338c4a4b0a062d2d3edac upstream.
The TCP session does not terminate with TCP_USER_TIMEOUT when data remain untransmitted due to zero window.
The number of unanswered zero-window probes (tcp_probes_out) is reset to zero with incoming acks irrespective of the window size, as described in tcp_probe_timer():
RFC 1122 4.2.2.17 requires the sender to stay open indefinitely as long as the receiver continues to respond probes. We support this by default and reset icsk_probes_out with incoming ACKs.
This counter, however, is the wrong one to be used in calculating the duration that the window remains closed and data remain untransmitted. Thanks to Jonathan Maxwell <[email protected]> for diagnosing the actual issue.
In this patch a new timestamp is introduced for the socket in order to track the elapsed time for the zero-window probes that have not been answered with any non-zero window ack.
--- include/net/inet_connection_sock.h | 3 +++ net/ipv4/inet_connection_sock.c | 1 + net/ipv4/tcp.c | 1 + net/ipv4/tcp_input.c | 1 + net/ipv4/tcp_output.c | 1 + net/ipv4/tcp_timer.c | 14 +++++++------- 6 files changed, 14 insertions(+), 7 deletions(-)
include/net/inet_connection_sock.h +3 -0
@@ -83,6 +83,8 @@ struct inet_connection_sock_af_ops {* @icsk_ext_hdr_len: Network protocol overhead (IP/IPv6 options) * @icsk_ack: Delayed ACK control data * @icsk_mtup; MTU probing control data +* @icsk_probes_tstamp: Probe timestamp (cleared by non-zero window ack) +* @icsk_user_timeout: TCP_USER_TIMEOUT value */ struct inet_connection_sock {/* inet_sock has to be the first member! */
@@ -133,6 +135,7 @@ struct inet_connection_sock {u32 probe_timestamp; } icsk_mtup; +u32 icsk_probes_tstamp;u32 icsk_user_timeout;u64 icsk_ca_priv[104 /sizeof (u64)];
net/ipv4/inet_connection_sock.c +1 -0
@@ -840,6 +840,7 @@ struct sock *inet_csk_clone_lock(const s newicsk->icsk_retransmits =0 ; newicsk->icsk_backoff =0 ; newicsk->icsk_probes_out =0 ; + newicsk->icsk_probes_tstamp =0 ;/* Deinitialize accept_queue to trap illegal accesses. */ memset (&newicsk->icsk_accept_queue,0 ,sizeof (newicsk->icsk_accept_queue));
net/ipv4/tcp.c +1 -0
@@ -2627,6 +2627,7 @@ int tcp_disconnect(struct sock *sk, int icsk->icsk_backoff =0 ; tp->snd_cwnd =2 ; icsk->icsk_probes_out =0 ; + icsk->icsk_probes_tstamp =0 ; icsk->icsk_rto =TCP_TIMEOUT_INIT ; tp->snd_ssthresh =TCP_INFINITE_SSTHRESH ; tp->snd_cwnd =TCP_INIT_CWND ;
net/ipv4/tcp_input.c +1 -0
@@ -3286,6 +3286,7 @@ static void tcp_ack_probe(struct sock *sreturn ;if (!after (TCP_SKB_CB (head)->end_seq,tcp_wnd_end (tp))) { icsk->icsk_backoff =0 ; + icsk->icsk_probes_tstamp =0 ;inet_csk_clear_xmit_timer (sk,ICSK_TIME_PROBE0 );/* Socket must be waked up by subsequent tcp_data_snd_check(). * This function is not for random using!
net/ipv4/tcp_output.c +1 -0
@@ -3835,6 +3835,7 @@ void tcp_send_probe0(struct sock *sk)/* Cancel probe timer, if it is not required. */ icsk->icsk_probes_out =0 ; icsk->icsk_backoff =0 ; + icsk->icsk_probes_tstamp =0 ;return ; }
net/ipv4/tcp_timer.c +7 -7
@@ -344,6 +344,7 @@ static void tcp_probe_timer(struct sockif (tp->packets_out || !skb) { icsk->icsk_probes_out =0 ; + icsk->icsk_probes_tstamp =0 ;return ; }
@@ -355,13 +356,12 @@ static void tcp_probe_timer(struct sock* corresponding system limit. We also implement similar policy when * we use RTO to probe window in tcp_retransmit_timer(). */ -if (icsk->icsk_user_timeout) { -u32 elapsed =tcp_model_timeout (sk, icsk->icsk_probes_out, -tcp_probe0_base (sk)); - -if (elapsed >= icsk->icsk_user_timeout) - goto abort; - } +if (!icsk->icsk_probes_tstamp) + icsk->icsk_probes_tstamp = tcp_jiffies32; +else if (icsk->icsk_user_timeout && + (s32)(tcp_jiffies32 - icsk->icsk_probes_tstamp) >= +msecs_to_jiffies (icsk->icsk_user_timeout)) + goto abort; max_probes =sock_net (sk)->ipv4.sysctl_tcp_retries2;if (sock_flag (sk,SOCK_DEAD )) {