libbpf: Initialize *nl_pid so gcc 10 is happy
Subsystems (16)
Sasha Levin
maintainerPATCH 15/38 scsi: target: fix PR IN / READ FULL STATUS for FC
In reply to Sasha LevinFrom: Bodo Stroesser <[email protected]>
[ Upstream commit 8fed04eb79a74cbf471dfaa755900a51b37273ab ]
Creation of the response to READ FULL STATUS fails for FC based reservations. Reason is the too high loop limit (< 24) in fc_get_pr_transport_id(). The string representation of FC WWPN is 23 chars long only ("11:22:33:44:55:66:77:88"). So when i is 23, the loop body is executed a last time for the ending '\0' of the string and thus hex2bin() reports an error.
--- drivers/target/target_core_fabric_lib.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/target/target_core_fabric_lib.c +1 -1
@@ -63,7 +63,7 @@ static int fc_get_pr_transport_id(* encoded TransportID. */ ptr = &se_nacl->initiatorname[0 ]; -for (i =0 ; i <24 ; ) { +for (i =0 ; i <23 ; ) {if (!strncmp (&ptr[i],":" ,1 )) { i++;continue ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 16/38 scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
In reply to Sasha LevinFrom: Bodo Stroesser <[email protected]>
[ Upstream commit 066f79a5fd6d1b9a5cc57b5cd445b3e4bb68a5b2 ]
In case command ring buffer becomes inconsistent, tcmu sets device flag TCMU_DEV_BIT_BROKEN. If the bit is set, tcmu rejects new commands from LIO core with TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE, and no longer processes completions from the ring. The reset_ring attribute can be used to completely clean up the command ring, so after reset_ring the ring no longer is inconsistent.
Therefore reset_ring also should reset bit TCMU_DEV_BIT_BROKEN to allow normal processing.
--- drivers/target/target_core_user.c | 1 + 1 file changed, 1 insertion(+)
drivers/target/target_core_user.c +1 -0
@@ -2073,6 +2073,7 @@ static void tcmu_reset_ring(struct tcmu_dev *udev, u8 err_level) mb->cmd_tail =0 ; mb->cmd_head =0 ;tcmu_flush_dcache_range (mb,sizeof (*mb)); +clear_bit (TCMU_DEV_BIT_BROKEN , &udev->flags);del_timer (&udev->cmd_timer);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 18/38 efi/x86: Don't remap text<->rodata gap read-only for mixed mode
In reply to Sasha LevinFrom: Ard Biesheuvel <[email protected]>
[ Upstream commit f6103162008dfd37567f240b50e5e1ea7cf2e00c ]
Commit
d9e3d2c4f10320 ("efi/x86: Don't map the entire kernel text RW for mixed mode")
updated the code that creates the 1:1 memory mapping to use read-only attributes for the 1:1 alias of the kernel's text and rodata sections, to protect it from inadvertent modification. However, it failed to take into account that the unused gap between text and rodata is given to the page allocator for general use.
If the vmap'ed stack happens to be allocated from this region, any by-ref output arguments passed to EFI runtime services that are allocated on the stack (such as the 'datasize' argument taken by GetVariable() when invoked from efivar_entry_size()) will be referenced via a read-only mapping, resulting in a page fault if the EFI code tries to write to it:
BUG: unable to handle page fault for address: 00000000386aae88 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD fd61063 P4D fd61063 PUD fd62063 PMD 386000e1 Oops: 0003 [#1] SMP PTI CPU: 2 PID: 255 Comm: systemd-sysv-ge Not tainted 5.6.0-rc4-default+ #22 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0008:0x3eaeed95 Code: ... <89> 03 be 05 00 00 80 a1 74 63 b1 3e 83 c0 48 e8 44 d2 ff ff eb 05 RSP: 0018:000000000fd73fa0 EFLAGS: 00010002 RAX: 0000000000000001 RBX: 00000000386aae88 RCX: 000000003e9f1120 RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000001 RBP: 000000000fd73fd8 R08: 00000000386aae88 R09: 0000000000000000 R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000 R13: ffffc0f040220000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f21160ac940(0000) GS:ffff9cf23d500000(0000) knlGS:0000000000000000 CS: 0008 DS: 0018 ES: 0018 CR0: 0000000080050033 CR2: 00000000386aae88 CR3: 000000000fd6c004 CR4: 00000000003606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: Modules linked in: CR2: 00000000386aae88 ---[ end trace a8bfbd202e712834 ]---
Let's fix this by remapping text and rodata individually, and leave the gaps mapped read-write.
--- arch/x86/platform/efi/efi_64.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
arch/x86/platform/efi/efi_64.c +10 -2
@@ -202,7 +202,7 @@ virt_to_phys_or_null_size(void *va, unsigned long size)int __init efi_setup_page_tables (unsigned long pa_memmap,unsigned num_pages) { -unsigned long pfn, text, pf; +unsigned long pfn, text, pf, rodata;struct page *page;unsigned npages;pgd_t *pgd = efi_mm.pgd;
@@ -256,7 +256,7 @@ int __init efi_setup_page_tables(unsigned long pa_memmap, unsigned num_pages) efi_scratch.phys_stack =page_to_phys (page +1 );/* stack grows down */ - npages = (__end_rodata_aligned - _text) >>PAGE_SHIFT ; + npages = (_etext - _text) >>PAGE_SHIFT ; text =__pa (_text); pfn = text >>PAGE_SHIFT ;
@@ -266,6 +266,14 @@ int __init efi_setup_page_tables(unsigned long pa_memmap, unsigned num_pages)return 1 ; } + npages = (__end_rodata - __start_rodata) >>PAGE_SHIFT ; + rodata =__pa (__start_rodata); + pfn = rodata >>PAGE_SHIFT ; +if (kernel_map_pages_in_pgd (pgd, pfn, rodata, npages, pf)) { +pr_err ("Failed to map kernel rodata 1:1\n" ); +return 1 ; + } +return 0 ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 30/38 i2c: tegra: Better handle case where CPU0 is busy for a long time
In reply to Sasha LevinFrom: Dmitry Osipenko <[email protected]>
[ Upstream commit a900aeac253729411cf33c6cb598c152e9e4137f ]
Boot CPU0 always handle I2C interrupt and under some rare circumstances (like running KASAN + NFS root) it may stuck in uninterruptible state for a significant time. In this case we will get timeout if I2C transfer is running on a sibling CPU, despite of IRQ being raised. In order to handle this rare condition, the IRQ status needs to be checked after completion timeout.
--- drivers/i2c/busses/i2c-tegra.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-)
drivers/i2c/busses/i2c-tegra.c +15 -12
@@ -1000,14 +1000,13 @@ tegra_i2c_poll_completion_timeout(struct tegra_i2c_dev *i2c_dev, do { u32 status = i2c_readl(i2c_dev, I2C_INT_STATUS); - if (status) { + if (status) tegra_i2c_isr(i2c_dev->irq, i2c_dev); - if (completion_done(complete)) { - s64 delta = ktime_ms_delta(ktimeout, ktime); + if (completion_done(complete)) { + s64 delta = ktime_ms_delta(ktimeout, ktime); - return msecs_to_jiffies(delta) ?: 1; - } + return msecs_to_jiffies(delta) ?: 1; } ktime = ktime_get();
@@ -1034,14 +1033,18 @@ tegra_i2c_wait_completion_timeout(struct tegra_i2c_dev *i2c_dev,disable_irq (i2c_dev->irq);/* -* There is a chance that completion may happen after IRQ -* synchronization, which is done by disable_irq(). +* Under some rare circumstances (like running KASAN + +* NFS root) CPU, which handles interrupt, may stuck in +* uninterruptible state for a significant time. In this +* case we will get timeout if I2C transfer is running on +* a sibling CPU, despite of IRQ being raised. +* +* In order to handle this rare condition, the IRQ status +* needs to be checked after timeout. */ -if (ret ==0 &&completion_done (complete)) { -dev_warn (i2c_dev->dev, -"completion done after timeout\n" ); - ret =1 ; - } +if (ret ==0 ) + ret =tegra_i2c_poll_completion_timeout (i2c_dev, + complete,0 ); }return ret;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 31/38 i2c: tegra: Synchronize DMA before termination
In reply to Sasha LevinFrom: Dmitry Osipenko <[email protected]>
[ Upstream commit 8814044fe0fa182abc9ff818d3da562de98bc9a7 ]
DMA transfer could be completed, but CPU (which handles DMA interrupt) may get too busy and can't handle the interrupt in a timely manner, despite of DMA IRQ being raised. In this case the DMA state needs to synchronized before terminating DMA transfer in order not to miss the DMA transfer completion.
--- drivers/i2c/busses/i2c-tegra.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/i2c/busses/i2c-tegra.c +9 -0
@@ -1223,6 +1223,15 @@ static int tegra_i2c_xfer_msg(struct tegra_i2c_dev *i2c_dev, time_left =tegra_i2c_wait_completion_timeout ( i2c_dev, &i2c_dev->dma_complete, xfer_time); +/* +* Synchronize DMA first, since dmaengine_terminate_sync() +* performs synchronization after the transfer's termination +* and we want to get a completion if transfer succeeded. +*/ +dmaengine_synchronize (i2c_dev->msg_read ? + i2c_dev->rx_dma_chan : + i2c_dev->tx_dma_chan); +dmaengine_terminate_sync (i2c_dev->msg_read ? i2c_dev->rx_dma_chan : i2c_dev->tx_dma_chan);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 1/38 libbpf: Initialize *nl_pid so gcc 10 is happy
From: Jeremy Cline <[email protected]>
[ Upstream commit 4734b0fefbbf98f8c119eb8344efa19dac82cd2c ]
Builds of Fedora's kernel-tools package started to fail with "may be used uninitialized" warnings for nl_pid in bpf_set_link_xdp_fd() and bpf_get_link_xdp_info() on the s390 architecture.
Although libbpf_netlink_open() always returns a negative number when it does not set *nl_pid, the compiler does not determine this and thus believes the variable might be used uninitialized. Assuage gcc's fears by explicitly initializing nl_pid.
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1807781
--- tools/lib/bpf/netlink.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/lib/bpf/netlink.c +2 -2
@@ -141,7 +141,7 @@ int bpf_set_link_xdp_fd(int ifindex, int fd, __u32 flags)struct ifinfomsg ifinfo;char attrbuf[64 ]; } req; -__u32 nl_pid; +__u32 nl_pid =0 ; sock =libbpf_netlink_open (&nl_pid);if (sock <0 )
@@ -256,7 +256,7 @@ int bpf_get_link_xdp_info(int ifindex, struct xdp_link_info *info, {struct xdp_id_md xdp_id = {};int sock, ret; -__u32 nl_pid; +__u32 nl_pid =0 ;__u32 mask;if (flags & ~XDP_FLAGS_MASK || !info_size)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 3/38 x86: hyperv: report value of misc_features
From: Olaf Hering <[email protected]>
[ Upstream commit 97d9f1c43bedd400301d6f1eff54d46e8c636e47 ]
A few kernel features depend on ms_hyperv.misc_features, but unlike its siblings ->features and ->hints, the value was never reported during boot.
--- arch/x86/kernel/cpu/mshyperv.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/mshyperv.c +2 -2
@@ -227,8 +227,8 @@ static void __init ms_hyperv_init_platform(void) ms_hyperv.misc_features =cpuid_edx (HYPERV_CPUID_FEATURES ); ms_hyperv.hints =cpuid_eax (HYPERV_CPUID_ENLIGHTMENT_INFO ); -pr_info ("Hyper-V: features 0x%x, hints 0x%x\n" , - ms_hyperv.features, ms_hyperv.hints); +pr_info ("Hyper-V: features 0x%x, hints 0x%x, misc 0x%x\n" , + ms_hyperv.features, ms_hyperv.hints, ms_hyperv.misc_features); ms_hyperv.max_vp_index =cpuid_eax (HYPERV_CPUID_IMPLEMENT_LIMITS ); ms_hyperv.max_lp_index =cpuid_ebx (HYPERV_CPUID_IMPLEMENT_LIMITS );
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 5/38 hwmon: (drivetemp) Use drivetemp's true module name in Kconfig section
In reply to Sasha LevinFrom: Ann T Ropea <[email protected]>
[ Upstream commit 6bdf8f3efe867c5893e27431a555e41f54ed7f9a ]
The addition of the support for reading the temperature of ATA drives as per commit 5b46903d8bf3 ("hwmon: Driver for disk and solid state drives with temperature sensors") lists in the respective Kconfig section the name of the module to be optionally built as "satatemp".
However, building the kernel modules with "CONFIG_SENSORS_DRIVETEMP=m", does not generate a file named "satatemp.ko".
Instead, the rest of the original commit uses the term "drivetemp" and a file named "drivetemp.ko" ends up in the kernel's modules directory. This file has the right ingredients:
$ strings /path/to/drivetemp.ko | grep ^description description=Hard drive temperature monitor
and modprobing it produces the expected result:
# drivetemp is not loaded $ sensors -u drivetemp-scsi-4-0 Specified sensor(s) not found! $ sudo modprobe drivetemp $ sensors -u drivetemp-scsi-4-0 drivetemp-scsi-4-0 Adapter: SCSI adapter temp1: temp1_input: 35.000 temp1_max: 60.000 temp1_min: 0.000 temp1_crit: 70.000 temp1_lcrit: -40.000 temp1_lowest: 20.000 temp1_highest: 36.000
Fix Kconfig by referring to the true name of the module.
--- drivers/hwmon/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/Kconfig +1 -1
@@ -403,7 +403,7 @@ config SENSORS_DRIVETEMP hard disk drives. This driver can also be built as a module. If so, the module - will be called satatemp. + will be called drivetemp. config SENSORS_DS620 tristate "Dallas Semiconductor DS620"
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 6/38 hwmon: (drivetemp) Return -ENODATA for invalid temperatures
In reply to Sasha LevinFrom: Guenter Roeck <[email protected]>
[ Upstream commit ed08ebb7124e90a99420bb913d602907d377d03d ]
Holger Hoffstätte observed that Samsung 850 Pro may return invalid temperatures for a short period of time after resume. Return -ENODATA to userspace if this is observed.
--- drivers/hwmon/drivetemp.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/hwmon/drivetemp.c +6 -0
@@ -264,12 +264,18 @@ static int drivetemp_get_scttemp(struct drivetemp_data *st, u32 attr, long *val)return err;switch (attr) {case hwmon_temp_input: +if (!temp_is_valid (buf[SCT_STATUS_TEMP ])) +return -ENODATA ; *val =temp_from_sct (buf[SCT_STATUS_TEMP ]);break ;case hwmon_temp_lowest: +if (!temp_is_valid (buf[SCT_STATUS_TEMP_LOWEST ])) +return -ENODATA ; *val =temp_from_sct (buf[SCT_STATUS_TEMP_LOWEST ]);break ;case hwmon_temp_highest: +if (!temp_is_valid (buf[SCT_STATUS_TEMP_HIGHEST ])) +return -ENODATA ; *val =temp_from_sct (buf[SCT_STATUS_TEMP_HIGHEST ]);break ;default :
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 9/38 xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
In reply to Sasha LevinFrom: "Darrick J. Wong" <[email protected]>
[ Upstream commit c142932c29e533ee892f87b44d8abc5719edceec ]
In the reflink extent remap function, it turns out that uirec (the block mapping corresponding only to the part of the passed-in mapping that got unmapped) was not fully initialized. Specifically, br_state was not being copied from the passed-in struct to the uirec. This could lead to unpredictable results such as the reflinked mapping being marked unwritten in the destination file.
--- fs/xfs/xfs_reflink.c | 1 + 1 file changed, 1 insertion(+)
fs/xfs/xfs_reflink.c +1 -0
@@ -1051,6 +1051,7 @@ xfs_reflink_remap_extent( uirec.br_startblock = irec->br_startblock + rlen; uirec.br_startoff = irec->br_startoff + rlen; uirec.br_blockcount = unmap_len - rlen; + uirec.br_state = irec->br_state; unmap_len = rlen;/* If this isn't a real mapping, we're done. */
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 10/38 ALSA: hda: Release resources at error in delayed probe
In reply to Sasha LevinFrom: Takashi Iwai <[email protected]>
[ Upstream commit 2393e7555b531a534152ffe7bfd1862cacedaacb ]
snd-hda-intel driver handles the most of its probe task in the delayed work (either via workqueue or via firmware loader). When an error happens in the later delayed probe, we can't deregister the device itself because the probe callback already returned success and the device was bound. So, for now, we set hda->init_failed flag and make the rest untouched until the device gets really unbound. However, this leaves the device up running, keeping the resources without any use that prevents other operations.
In this patch, we release the resources at first when a probe error happens in the delayed probe stage, but keeps the top-level object, so that the PM and other ops can still refer to the object itself.
Also for simplicity, snd_hda_intel object is allocated via devm, so that we can get rid of the explicit kfree calls.
--- sound/pci/hda/hda_intel.c | 29 ++++++++++++++++------------- sound/pci/hda/hda_intel.h | 1 + 2 files changed, 17 insertions(+), 13 deletions(-)
sound/pci/hda/hda_intel.c +16 -13
@@ -1203,10 +1203,8 @@ static void azx_vs_set_state(struct pci_dev *pci,if (!disabled) {dev_info (chip->card->dev,"Start delayed initialization\n" ); -if (azx_probe_continue (chip) <0 ) { +if (azx_probe_continue (chip) <0 )dev_err (chip->card->dev,"initialization error\n" ); - hda->init_failed = true; - } } }else { dev_info(chip->card->dev, "%s via vga_switcheroo\n",
@@ -1339,12 +1337,15 @@ static int register_vga_switcheroo(struct azx *chip)/* * destructor */ -static int azx_free (struct azx *chip) +static void azx_free (struct azx *chip) {struct pci_dev *pci = chip->pci; struct hda_intel *hda = container_of(chip, struct hda_intel, chip);struct hdac_bus *bus =azx_bus (chip); +if (hda->freed) +return ; +if (azx_has_pm_runtime (chip) && chip->running)pm_runtime_get_noresume (&pci->dev); chip->running =0 ;
@@ -1388,9 +1389,8 @@ static int azx_free(struct azx *chip)if (chip->driver_caps &AZX_DCAPS_I915_COMPONENT )snd_hdac_i915_exit (bus); -kfree (hda); -return 0 ; + hda->freed =1 ; }static int azx_dev_disconnect (struct snd_device *device)
@@ -1406,7 +1406,8 @@ static int azx_dev_disconnect(struct snd_device *device)static int azx_dev_free (struct snd_device *device) { -return azx_free (device->device_data); +azx_free (device->device_data); +return 0 ; }#ifdef SUPPORT_VGA_SWITCHEROO
@@ -1773,7 +1774,7 @@ static int azx_create(struct snd_card *card, struct pci_dev *pci,if (err <0 )return err; - hda =kzalloc (sizeof (*hda),GFP_KERNEL ); + hda =devm_kzalloc (&pci->dev,sizeof (*hda),GFP_KERNEL );if (!hda) {pci_disable_device (pci);return -ENOMEM ;
@@ -1814,7 +1815,6 @@ static int azx_create(struct snd_card *card, struct pci_dev *pci, err =azx_bus_init (chip, model[dev]);if (err <0 ) { -kfree (hda);pci_disable_device (pci);return err; }
@@ -2340,13 +2340,16 @@ static int azx_probe_continue(struct azx *chip)pm_runtime_put_autosuspend (&pci->dev); out_free: -if (err <0 || !hda->need_i915_power) +if (err <0 ) { +azx_free (chip); +return err; + } + +if (!hda->need_i915_power)display_power (chip, false); -if (err <0 ) - hda->init_failed =1 ;complete_all (&hda->probe_wait);to_hda_bus (bus)->bus_probing =0 ; -return err; +return 0 ; }static void azx_remove (struct pci_dev *pci)
sound/pci/hda/hda_intel.h +1 -0
@@ -27,6 +27,7 @@ struct hda_intel { unsigned int use_vga_switcheroo:1; unsigned int vga_switcheroo_registered:1; unsigned int init_failed:1; /* delayed init failed */ + unsigned int freed:1; /* resources already released */ bool need_i915_power:1; /* the hda controller needs i915 power */ };
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 14/38 drm/amdgpu: fix wrong vram lost counter increment V2
In reply to Sasha LevinFrom: Evan Quan <[email protected]>
[ Upstream commit 028cfb2444b94d4f394a6fa4ca46182481236e91 ]
Vram lost counter is wrongly increased by two during baco reset.
V2: assumed vram lost for mode1 reset on all ASICs
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 20 ++++++++++++++++++-- drivers/gpu/drm/amd/amdgpu/cik.c | 2 -- drivers/gpu/drm/amd/amdgpu/nv.c | 4 ---- drivers/gpu/drm/amd/amdgpu/soc15.c | 4 ---- drivers/gpu/drm/amd/amdgpu/vi.c | 2 -- 5 files changed, 18 insertions(+), 14 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +18 -2
@@ -1953,8 +1953,24 @@ static void amdgpu_device_fill_reset_magic(struct amdgpu_device *adev)*/ static bool amdgpu_device_check_vram_lost (struct amdgpu_device *adev) { -return !!memcmp (adev->gart.ptr, adev->reset_magic, -AMDGPU_RESET_MAGIC_NUM ); +if (memcmp (adev->gart.ptr, adev->reset_magic, +AMDGPU_RESET_MAGIC_NUM )) +return true; + +if (!adev->in_gpu_reset) +return false; + +/* +* For all ASICs with baco/mode1 reset, the VRAM is +* always assumed to be lost. +*/ +switch (amdgpu_asic_reset_method (adev)) { +case AMD_RESET_METHOD_BACO : +case AMD_RESET_METHOD_MODE1 : +return true; +default : +return false; + } }/**
drivers/gpu/drm/amd/amdgpu/cik.c +0 -2
@@ -1358,8 +1358,6 @@ static int cik_asic_reset(struct amdgpu_device *adev)int r;if (cik_asic_reset_method (adev) ==AMD_RESET_METHOD_BACO ) { -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev); r =amdgpu_dpm_baco_reset (adev); }else { r =cik_asic_pci_config_reset (adev);
drivers/gpu/drm/amd/amdgpu/nv.c +0 -4
@@ -351,8 +351,6 @@ static int nv_asic_reset(struct amdgpu_device *adev)struct smu_context *smu = &adev->smu;if (nv_asic_reset_method (adev) ==AMD_RESET_METHOD_BACO ) { -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev); ret =smu_baco_enter (smu);if (ret)return ret;
@@ -360,8 +358,6 @@ static int nv_asic_reset(struct amdgpu_device *adev)if (ret)return ret; }else { -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev); ret =nv_asic_mode1_reset (adev); }
drivers/gpu/drm/amd/amdgpu/soc15.c +0 -4
@@ -569,14 +569,10 @@ static int soc15_asic_reset(struct amdgpu_device *adev)switch (soc15_asic_reset_method (adev)) {case AMD_RESET_METHOD_BACO : -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev);return soc15_asic_baco_reset (adev);case AMD_RESET_METHOD_MODE2 :return amdgpu_dpm_mode2_reset (adev);default : -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev);return soc15_asic_mode1_reset (adev); } }
drivers/gpu/drm/amd/amdgpu/vi.c +0 -2
@@ -765,8 +765,6 @@ static int vi_asic_reset(struct amdgpu_device *adev)int r;if (vi_asic_reset_method (adev) ==AMD_RESET_METHOD_BACO ) { -if (!adev->in_suspend) -amdgpu_inc_vram_lost (adev); r =amdgpu_dpm_baco_reset (adev); }else { r =vi_asic_pci_config_reset (adev);
Signature · 6 lines
2.20.1 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Sasha Levin
maintainerPATCH 13/38 ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
In reply to Sasha LevinFrom: Roy Spliet <[email protected]>
[ Upstream commit 3ba21113bd33d49f3c300a23fc08cf114c434995 ]
This fixes runtime PM not working after a suspend-to-RAM cycle at least for the codec-less HDA device found on NVIDIA GPUs.
--- sound/pci/hda/hda_intel.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
sound/pci/hda/hda_intel.c +3 -1
@@ -2354,8 +2354,10 @@ static int azx_probe_continue(struct azx *chip)set_default_power_save (chip); -if (azx_has_pm_runtime (chip)) +if (azx_has_pm_runtime (chip)) { +pm_runtime_use_autosuspend (&pci->dev);pm_runtime_put_autosuspend (&pci->dev); + } out_free:if (err <0 ) {
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 12/38 ALSA: hda: Skip controller resume if not needed
In reply to Sasha LevinFrom: Takashi Iwai <[email protected]>
[ Upstream commit c4c8dd6ef807663e42a5f04ea77cd62029eb99fa ]
The HD-audio controller does system-suspend and resume operations by directly calling its helpers __azx_runtime_suspend() and __azx_runtime_resume(). However, in general, we don't have to resume always the device fully at the system resume; typically, if a device has been runtime-suspended, we can leave it to runtime resume.
Usually for achieving this, the driver would call pm_runtime_force_suspend() and pm_runtime_force_resume() pairs in the system suspend and resume ops. Unfortunately, this doesn't work for the resume path in our case. For handling the jack detection at the system resume, a child codec device may need the (literally) forcibly resume even if it's been runtime-suspended, and for that, the controller device must be also resumed even if it's been suspended.
This patch is an attempt to improve the situation. It replaces the direct __azx_runtime_suspend()/_resume() calls with with pm_runtime_force_suspend() and pm_runtime_force_resume() with a slight trick as we've done for the codec side. More exactly:
- azx_has_pm_runtime() check is dropped from azx_runtime_suspend() and azx_runtime_resume(), so that it can be properly executed from the system-suspend/resume path
- The WAKEEN handling depends on the card's power state now; it's set and cleared only for the runtime-suspend
- azx_resume() checks whether any codec may need the forcible resume beforehand. If the forcible resume is required, it does temporary PM refcount up/down for actually triggering the runtime resume.
- A new helper function, hda_codec_need_resume(), is introduced for checking whether the codec needs a forcible runtime-resume, and the existing code is rewritten with that.
--- include/sound/hda_codec.h | 5 +++++ sound/pci/hda/hda_codec.c | 2 +- sound/pci/hda/hda_intel.c | 38 +++++++++++++++++++++++++++----------- 3 files changed, 33 insertions(+), 12 deletions(-)
include/sound/hda_codec.h +5 -0
@@ -494,6 +494,11 @@ void snd_hda_update_power_acct(struct hda_codec *codec);static inline void snd_hda_set_power_save (struct hda_bus *bus,int delay) {}#endif +static inline bool hda_codec_need_resume (struct hda_codec *codec) +{ +return !codec->relaxed_resume && codec->jacktbl.used; +} +#ifdef CONFIG_SND_HDA_PATCH_LOADER /* * patch firmware
sound/pci/hda/hda_codec.c +1 -1
@@ -2951,7 +2951,7 @@ static int hda_codec_runtime_resume(struct device *dev)static int hda_codec_force_resume (struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); -bool forced_resume = !codec->relaxed_resume && codec->jacktbl.used; +bool forced_resume =hda_codec_need_resume (codec);int ret;/* The get/put pair below enforces the runtime resume even if the
sound/pci/hda/hda_intel.c +27 -11
@@ -1027,7 +1027,7 @@ static int azx_suspend(struct device *dev) chip = card->private_data; bus =azx_bus (chip);snd_power_change_state (card, SNDRV_CTL_POWER_D3hot); -__azx_runtime_suspend (chip); +pm_runtime_force_suspend (dev);if (bus->irq >=0 ) {free_irq (bus->irq, chip); bus->irq =-1 ;
@@ -1044,7 +1044,9 @@ static int azx_suspend(struct device *dev)static int azx_resume (struct device *dev) {struct snd_card *card =dev_get_drvdata (dev); +struct hda_codec *codec;struct azx *chip; +bool forced_resume = false;if (!azx_is_pm_ready (card))return 0 ;
@@ -1055,7 +1057,20 @@ static int azx_resume(struct device *dev) chip->msi =0 ;if (azx_acquire_irq (chip,1 ) <0 )return -EIO ; -__azx_runtime_resume (chip, false); + +/* check for the forced resume */ +list_for_each_codec (codec, &chip->bus) { +if (hda_codec_need_resume (codec)) { + forced_resume = true; +break ; + } + } + +if (forced_resume) +pm_runtime_get_noresume (dev); +pm_runtime_force_resume (dev); +if (forced_resume) +pm_runtime_put (dev);snd_power_change_state (card,SNDRV_CTL_POWER_D0 );trace_azx_resume (chip);
@@ -1102,12 +1117,12 @@ static int azx_runtime_suspend(struct device *dev)if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ;/* enable controller wake up event */ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | -STATESTS_INT_MASK ); +if (snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | +STATESTS_INT_MASK ); + }__azx_runtime_suspend (chip);trace_azx_runtime_suspend (chip);
@@ -1118,17 +1133,18 @@ static int azx_runtime_resume(struct device *dev) {struct snd_card *card =dev_get_drvdata (dev);struct azx *chip; +bool from_rt =snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ;if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ; -__azx_runtime_resume (chip, true); +__azx_runtime_resume (chip, from_rt);/* disable controller Wake Up event*/ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & - ~STATESTS_INT_MASK ); +if (from_rt) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & + ~STATESTS_INT_MASK ); + }trace_azx_runtime_resume (chip);return 0 ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 20/38 objtool: Support Clang non-section symbols in ORC dump
In reply to Sasha LevinFrom: Josh Poimboeuf <[email protected]>
[ Upstream commit 8782e7cab51b6bf01a5a86471dd82228af1ac185 ]
Historically, the relocation symbols for ORC entries have only been section symbols:
.text+0: sp:sp+8 bp:(und) type:call end:0
However, the Clang assembler is aggressive about stripping section symbols. In that case we will need to use function symbols:
freezing_slow_path+0: sp:sp+8 bp:(und) type:call end:0
In preparation for the generation of such entries in "objtool orc generate", add support for reading them in "objtool orc dump".
--- tools/objtool/orc_dump.c | 44 ++++++++++++++++++++++++---------------- 1 file changed, 27 insertions(+), 17 deletions(-)
tools/objtool/orc_dump.c +27 -17
@@ -66,7 +66,7 @@ int orc_dump(const char *_objname)char *name;size_t nr_sections;Elf64_Addr orc_ip_addr =0 ; -size_t shstrtab_idx; +size_t shstrtab_idx, strtab_idx =0 ;Elf *elf;Elf_Scn *scn;GElf_Shdr sh;
@@ -127,6 +127,8 @@ int orc_dump(const char *_objname)if (!strcmp (name,".symtab" )) { symtab = data; + }else if (!strcmp (name,".strtab" )) { + strtab_idx = i; }else if (!strcmp (name,".orc_unwind" )) { orc = data->d_buf; orc_size = sh.sh_size;
@@ -138,7 +140,7 @@ int orc_dump(const char *_objname) } } -if (!symtab || !orc || !orc_ip) +if (!symtab || !strtab_idx || !orc || !orc_ip)return 0 ;if (orc_size %sizeof (*orc) !=0 ) {
@@ -159,21 +161,29 @@ int orc_dump(const char *_objname)return -1 ; } - scn =elf_getscn (elf, sym.st_shndx); -if (!scn) { -WARN_ELF ("elf_getscn" ); -return -1 ; - } - -if (!gelf_getshdr (scn, &sh)) { -WARN_ELF ("gelf_getshdr" ); -return -1 ; - } - - name =elf_strptr (elf, shstrtab_idx, sh.sh_name); -if (!name || !*name) { -WARN_ELF ("elf_strptr" ); -return -1 ; +if (GELF_ST_TYPE (sym.st_info) ==STT_SECTION ) { + scn =elf_getscn (elf, sym.st_shndx); +if (!scn) { +WARN_ELF ("elf_getscn" ); +return -1 ; + } + +if (!gelf_getshdr (scn, &sh)) { +WARN_ELF ("gelf_getshdr" ); +return -1 ; + } + + name =elf_strptr (elf, shstrtab_idx, sh.sh_name); +if (!name) { +WARN_ELF ("elf_strptr" ); +return -1 ; + } + }else { + name =elf_strptr (elf, strtab_idx, sym.st_name); +if (!name) { +WARN_ELF ("elf_strptr" ); +return -1 ; + } }printf ("%s+%llx:" , name, (unsigned long long )rela.r_addend);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 23/38 net: stmmac: socfpga: Allow all RGMII modes
In reply to Sasha LevinFrom: Atsushi Nemoto <[email protected]>
[ Upstream commit a7a0d6269652846671312b29992143f56e2866b8 ]
Allow all the RGMII modes to be used. (Not only "rgmii", "rgmii-id" but "rgmii-txid", "rgmii-rxid")
--- drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/ethernet/stmicro/stmmac/dwmac-socfpga.c +2 -0
@@ -241,6 +241,8 @@ static int socfpga_set_phy_mode_common(int phymode, u32 *val)switch (phymode) {case PHY_INTERFACE_MODE_RGMII :case PHY_INTERFACE_MODE_RGMII_ID : +case PHY_INTERFACE_MODE_RGMII_RXID : +case PHY_INTERFACE_MODE_RGMII_TXID : *val =SYSMGR_EMACGRP_CTRL_PHYSEL_ENUM_RGMII ;break ;case PHY_INTERFACE_MODE_MII :
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 25/38 mac80211: fix channel switch trigger from unknown mesh peer
In reply to Sasha LevinFrom: Tamizh chelvam <[email protected]>
[ Upstream commit 93e2d04a1888668183f3fb48666e90b9b31d29e6 ]
Previously mesh channel switch happens if beacon contains CSA IE without checking the mesh peer info. Due to that channel switch happens even if the beacon is not from its own mesh peer. Fixing that by checking if the CSA originated from the same mesh network before proceeding for channel switch.
--- net/mac80211/mesh.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
net/mac80211/mesh.c +7 -4
@@ -1257,15 +1257,15 @@ static void ieee80211_mesh_rx_bcn_presp(struct ieee80211_sub_if_data *sdata, sdata->u.mesh.mshcfg.rssi_threshold < rx_status->signal)mesh_neighbour_update (sdata, mgmt->sa, &elems, rx_status); + +if (ifmsh->csa_role !=IEEE80211_MESH_CSA_ROLE_INIT && + !sdata->vif.csa_active) +ieee80211_mesh_process_chnswitch (sdata, &elems, true); }if (ifmsh->sync_ops) ifmsh->sync_ops->rx_bcn_presp (sdata, stype, mgmt, &elems, rx_status); - -if (ifmsh->csa_role !=IEEE80211_MESH_CSA_ROLE_INIT && - !sdata->vif.csa_active) -ieee80211_mesh_process_chnswitch (sdata, &elems, true); }int ieee80211_mesh_finish_csa (struct ieee80211_sub_if_data *sdata)
@@ -1373,6 +1373,9 @@ static void mesh_rx_csa_frame(struct ieee80211_sub_if_data *sdata,ieee802_11_parse_elems (pos, len - baselen, true, &elems, mgmt->bssid,NULL ); +if (!mesh_matches_local (sdata, &elems)) +return ; + ifmsh->chsw_ttl = elems.mesh_chansw_params_ie->mesh_ttl;if (!--ifmsh->chsw_ttl) fwd_csa = false;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 28/38 i2c: remove i2c_new_probed_device API
In reply to Sasha LevinFrom: Wolfram Sang <[email protected]>
[ Upstream commit 3c1d1613be80c2e17f1ddf672df1d8a8caebfd0d ]
All in-tree users have been converted to the new i2c_new_scanned_device function, so remove this deprecated one.
--- drivers/i2c/i2c-core-base.c | 13 ------------- include/linux/i2c.h | 6 ------ 2 files changed, 19 deletions(-)
drivers/i2c/i2c-core-base.c +0 -13
@@ -2269,19 +2269,6 @@ i2c_new_scanned_device(struct i2c_adapter *adap, }EXPORT_SYMBOL_GPL (i2c_new_scanned_device); -struct i2c_client * -i2c_new_probed_device (struct i2c_adapter *adap, -struct i2c_board_info *info, -unsigned short const *addr_list, -int (*probe)(struct i2c_adapter *adap,unsigned short addr)) -{ -struct i2c_client *client; - - client =i2c_new_scanned_device (adap, info, addr_list, probe); -return IS_ERR (client) ?NULL : client; -} -EXPORT_SYMBOL_GPL (i2c_new_probed_device); -struct i2c_adapter *i2c_get_adapter (int nr) {struct i2c_adapter *adapter;
include/linux/i2c.h +0 -6
@@ -453,12 +453,6 @@ i2c_new_scanned_device(struct i2c_adapter *adap,unsigned short const *addr_list, int (*probe)(struct i2c_adapter *adap, unsigned short addr)); -struct i2c_client * -i2c_new_probed_device (struct i2c_adapter *adap, -struct i2c_board_info *info, -unsigned short const *addr_list, -int (*probe)(struct i2c_adapter *adap,unsigned short addr)); -/* Common custom probe functions */ int i2c_probe_func_quick_read (struct i2c_adapter *adap,unsigned short addr);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 29/38 arm64: Delete the space separator in __emit_inst
In reply to Sasha LevinFrom: Fangrui Song <[email protected]>
[ Upstream commit c9a4ef66450145a356a626c833d3d7b1668b3ded ]
In assembly, many instances of __emit_inst(x) expand to a directive. In a few places __emit_inst(x) is used as an assembler macro argument. For example, in arch/arm64/kvm/hyp/entry.S
ALTERNATIVE(nop, SET_PSTATE_PAN(1), ARM64_HAS_PAN, CONFIG_ARM64_PAN)
expands to the following by the C preprocessor:
alternative_insn nop, .inst (0xd500401f | ((0) << 16 | (4) << 5) | ((!!1) << 8)), 4, 1
Both comma and space are separators, with an exception that content inside a pair of parentheses/quotes is not split, so the clang integrated assembler splits the arguments to:
nop, .inst, (0xd500401f | ((0) << 16 | (4) << 5) | ((!!1) << 8)), 4, 1
GNU as preprocesses the input with do_scrub_chars(). Its arm64 backend (along with many other non-x86 backends) sees:
alternative_insn nop,.inst(0xd500401f|((0)<<16|(4)<<5)|((!!1)<<8)),4,1 # .inst(...) is parsed as one argument
while its x86 backend sees:
alternative_insn nop,.inst (0xd500401f|((0)<<16|(4)<<5)|((!!1)<<8)),4,1 # The extra space before '(' makes the whole .inst (...) parsed as two arguments
The non-x86 backend's behavior is considered unintentional
(https://sourceware.org/bugzilla/show_bug.cgi?id=25750).
So drop the space separator inside .inst (...) to make the clang integrated assembler work.
--- arch/arm64/include/asm/sysreg.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/arm64/include/asm/sysreg.h +3 -1
@@ -49,7 +49,9 @@#ifndef CONFIG_BROKEN_GAS_INST #ifdef __ASSEMBLY__ -#define __emit_inst (x) .inst (x) +// The space separator is omitted so that __emit_inst(x) can be parsed as +// either an assembler directive or an assembler macro argument. +#define __emit_inst (x) .inst(x)#else #define __emit_inst (x) ".inst " __stringify((x)) "\n\t"#endif
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 21/38 xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
In reply to Sasha LevinFrom: Juergen Gross <[email protected]>
[ Upstream commit 6b51fd3f65a22e3d1471b18a1d56247e246edd46 ]
xenbus_map_ring_valloc() maps a ring page and returns the status of the used grant (0 meaning success).
There are Xen hypervisors which might return the value 1 for the status of a failed grant mapping due to a bug. Some callers of xenbus_map_ring_valloc() test for errors by testing the returned status to be less than zero, resulting in no error detected and crashing later due to a not available ring page.
Set the return value of xenbus_map_ring_valloc() to GNTST_general_error in case the grant status reported by Xen is greater than zero.
This is part of XSA-316.
--- drivers/xen/xenbus/xenbus_client.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/xen/xenbus/xenbus_client.c +8 -1
@@ -448,7 +448,14 @@ EXPORT_SYMBOL_GPL(xenbus_free_evtchn);int xenbus_map_ring_valloc (struct xenbus_device *dev,grant_ref_t *gnt_refs,unsigned int nr_grefs,void **vaddr) { -return ring_ops->map (dev, gnt_refs, nr_grefs, vaddr); +int err; + + err = ring_ops->map (dev, gnt_refs, nr_grefs, vaddr); +/* Some hypervisors are buggy and can return 1. */ +if (err >0 ) + err = GNTST_general_error; + +return err; }EXPORT_SYMBOL_GPL (xenbus_map_ring_valloc);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 32/38 ext4: use matching invalidatepage in ext4_writepage
In reply to Sasha LevinFrom: yangerkun <[email protected]>
[ Upstream commit c2a559bc0e7ed5a715ad6b947025b33cb7c05ea7 ]
Run generic/388 with journal data mode sometimes may trigger the warning in ext4_invalidatepage. Actually, we should use the matching invalidatepage in ext4_writepage.
--- fs/ext4/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/inode.c +1 -1
@@ -1974,7 +1974,7 @@ static int ext4_writepage(struct page *page,bool keep_towrite = false;if (unlikely (ext4_forced_shutdown (EXT4_SB (inode->i_sb)))) { -ext4_invalidatepage (page,0 ,PAGE_SIZE ); + inode->i_mapping->a_ops->invalidatepage (page,0 ,PAGE_SIZE );unlock_page (page);return -EIO ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 33/38 ext4: increase wait time needed before reuse of deleted inode numbers
In reply to Sasha LevinFrom: Theodore Ts'o <[email protected]>
[ Upstream commit a17a9d935dc4a50acefaf319d58030f1da7f115a ]
Current wait times have proven to be too short to protect against inode reuses that lead to metadata inconsistencies.
Now that we will retry the inode allocation if we can't find any recently deleted inodes, it's a lot safer to increase the recently deleted time from 5 seconds to a minute.
Google-Bug-Id: 36602237
--- fs/ext4/ialloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/ialloc.c +1 -1
@@ -663,7 +663,7 @@ static int find_group_other(struct super_block *sb, struct inode *parent,* block has been written back to disk. (Yes, these values are * somewhat arbitrary...) */ -#define RECENTCY_MIN 5 +#define RECENTCY_MIN 60#define RECENTCY_DIRTY 300static int recently_deleted (struct super_block *sb,ext4_group_t group,int ino)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 36/38 blk-mq: Put driver tag in blk_mq_dispatch_rq_list() when no budget
In reply to Sasha LevinFrom: John Garry <[email protected]>
[ Upstream commit 5fe56de799ad03e92d794c7936bf363922b571df ]
If in blk_mq_dispatch_rq_list() we find no budget, then we break of the dispatch loop, but the request may keep the driver tag, evaulated in 'nxt' in the previous loop iteration.
Fix by putting the driver tag for that request.
--- block/blk-mq.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
block/blk-mq.c +3 -1
@@ -1205,8 +1205,10 @@ bool blk_mq_dispatch_rq_list(struct request_queue *q, struct list_head *list, rq = list_first_entry(list, struct request, queuelist); hctx = rq->mq_hctx; -if (!got_budget && !blk_mq_get_dispatch_budget (hctx)) +if (!got_budget && !blk_mq_get_dispatch_budget (hctx)) { +blk_mq_put_driver_tag (rq);break ; + }if (!blk_mq_get_driver_tag (rq)) {/*
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 37/38 irqchip/meson-gpio: Fix HARDIRQ-safe -> HARDIRQ-unsafe lock order
In reply to Sasha LevinFrom: Marc Zyngier <[email protected]>
[ Upstream commit 0a66d6f90cf7d704c6a0f663f7058099eb8c97b0 ]
Running a lockedp-enabled kernel on a vim3l board (Amlogic SM1) leads to the following splat:
[ 13.557138] WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
[ 13.587485] ip/456 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
[ 13.625922] ffff000059908cf0 (&irq_desc_lock_class){-.-.}-{2:2}, at: __setup_irq+0xf8/0x8d8
[ 13.632273] which would create a new lock dependency:
[ 13.637272] (&irq_desc_lock_class){-.-.}-{2:2} -> (&ctl->lock){+.+.}-{2:2}
[ 13.644209]
[ 13.644209] but this new dependency connects a HARDIRQ-irq-safe lock:
[ 13.654122] (&irq_desc_lock_class){-.-.}-{2:2}
[ 13.654125]
[ 13.654125] ... which became HARDIRQ-irq-safe at:
[ 13.664759] lock_acquire+0xec/0x368
[ 13.666926] _raw_spin_lock+0x60/0x88
[ 13.669979] handle_fasteoi_irq+0x30/0x178
[ 13.674082] generic_handle_irq+0x38/0x50
[ 13.678098] __handle_domain_irq+0x6c/0xc8
[ 13.682209] gic_handle_irq+0x5c/0xb0
[ 13.685872] el1_irq+0xd0/0x180
[ 13.689010] arch_cpu_idle+0x40/0x220
[ 13.692732] default_idle_call+0x54/0x60
[ 13.696677] do_idle+0x23c/0x2e8
[ 13.699903] cpu_startup_entry+0x30/0x50
[ 13.703852] rest_init+0x1e0/0x2b4
[ 13.707301] arch_call_rest_init+0x18/0x24
[ 13.711449] start_kernel+0x4ec/0x51c
[ 13.715167]
[ 13.715167] to a HARDIRQ-irq-unsafe lock:
[ 13.722426] (&ctl->lock){+.+.}-{2:2}
[ 13.722430]
[ 13.722430] ... which became HARDIRQ-irq-unsafe at:
[ 13.732319] ...
[ 13.732324] lock_acquire+0xec/0x368
[ 13.735985] _raw_spin_lock+0x60/0x88
[ 13.739452] meson_gpio_irq_domain_alloc+0xcc/0x290
[ 13.744392] irq_domain_alloc_irqs_hierarchy+0x24/0x60
[ 13.749586] __irq_domain_alloc_irqs+0x160/0x2f0
[ 13.754254] irq_create_fwspec_mapping+0x118/0x320
[ 13.759073] irq_create_of_mapping+0x78/0xa0
[ 13.763360] of_irq_get+0x6c/0x80
[ 13.766701] of_mdiobus_register_phy+0x10c/0x238 [of_mdio]
[ 13.772227] of_mdiobus_register+0x158/0x380 [of_mdio]
[ 13.777388] mdio_mux_init+0x180/0x2e8 [mdio_mux]
[ 13.782128] g12a_mdio_mux_probe+0x290/0x398 [mdio_mux_meson_g12a]
[ 13.788349] platform_drv_probe+0x5c/0xb0
[ 13.792379] really_probe+0xe4/0x448
[ 13.795979] driver_probe_device+0xe8/0x140
[ 13.800189] __device_attach_driver+0x94/0x120
[ 13.804639] bus_for_each_drv+0x84/0xd8
[ 13.808474] __device_attach+0xe4/0x168
[ 13.812361] device_initial_probe+0x1c/0x28
[ 13.816592] bus_probe_device+0xa4/0xb0
[ 13.820430] deferred_probe_work_func+0xa8/0x100
[ 13.825064] process_one_work+0x264/0x688
[ 13.829088] worker_thread+0x4c/0x458
[ 13.832768] kthread+0x154/0x158
[ 13.836018] ret_from_fork+0x10/0x18
[ 13.839612]
[ 13.839612] other info that might help us debug this:
[ 13.839612]
[ 13.850354] Possible interrupt unsafe locking scenario:
[ 13.850354]
[ 13.855720] CPU0 CPU1
[ 13.858774] ---- ----
[ 13.863242] lock(&ctl->lock);
[ 13.866330] local_irq_disable();
[ 13.872233] lock(&irq_desc_lock_class);
[ 13.878705] lock(&ctl->lock);
[ 13.884297] <Interrupt>
[ 13.886857] lock(&irq_desc_lock_class);
[ 13.891014]
[ 13.891014] *** DEADLOCK ***The issue can occur when CPU1 is doing something like irq_set_type() and CPU0 performing an interrupt allocation, for example. Taking an interrupt (like the one being reconfigured) would lead to a deadlock.
A solution to this is:
- Reorder the locking so that meson_gpio_irq_update_bits takes the lock itself at all times, instead of relying on the caller to lock or not, hence making the RMW sequence atomic,
- Rework the critical section in meson_gpio_irq_request_channel to only cover the allocation itself, and let the gpio_irq_sel_pin callback deal with its own locking if required,
- Take the private spin-lock with interrupts disabled at all times
--- drivers/irqchip/irq-meson-gpio.c | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-)
drivers/irqchip/irq-meson-gpio.c +10 -8
@@ -144,12 +144,17 @@ struct meson_gpio_irq_controller {static void meson_gpio_irq_update_bits (struct meson_gpio_irq_controller *ctl,unsigned int reg,u32 mask,u32 val) { +unsigned long flags;u32 tmp; +spin_lock_irqsave (&ctl->lock, flags); + tmp =readl_relaxed (ctl->base + reg); tmp &= ~mask; tmp |= val;writel_relaxed (tmp, ctl->base + reg); + +spin_unlock_irqrestore (&ctl->lock, flags); }static void meson_gpio_irq_init_dummy (struct meson_gpio_irq_controller *ctl)
@@ -196,14 +201,15 @@ meson_gpio_irq_request_channel(struct meson_gpio_irq_controller *ctl,unsigned long hwirq, u32 **channel_hwirq) { + unsigned long flags;unsigned int idx; -spin_lock (&ctl->lock); +spin_lock_irqsave (&ctl->lock, flags);/* Find a free channel */ idx =find_first_zero_bit (ctl->channel_map,NUM_CHANNEL );if (idx >=NUM_CHANNEL ) { -spin_unlock (&ctl->lock); +spin_unlock_irqrestore (&ctl->lock, flags);pr_err ("No channel available\n" );return -ENOSPC ; }
@@ -211,6 +217,8 @@ meson_gpio_irq_request_channel(struct meson_gpio_irq_controller *ctl,/* Mark the channel as used */ set_bit (idx, ctl->channel_map); +spin_unlock_irqrestore (&ctl->lock, flags); +/* * Setup the mux of the channel to route the signal of the pad * to the appropriate input of the GIC
@@ -225,8 +233,6 @@ meson_gpio_irq_request_channel(struct meson_gpio_irq_controller *ctl,*/ *channel_hwirq = &(ctl->channel_irqs[idx]); -spin_unlock (&ctl->lock); -pr_debug ("hwirq %lu assigned to channel %d - irq %u\n" , hwirq, idx, **channel_hwirq);
@@ -287,13 +293,9 @@ static int meson_gpio_irq_type_setup(struct meson_gpio_irq_controller *ctl, val |=REG_EDGE_POL_LOW (params, idx); } -spin_lock (&ctl->lock); -meson_gpio_irq_update_bits (ctl,REG_EDGE_POL ,REG_EDGE_POL_MASK (params, idx), val); -spin_unlock (&ctl->lock); -return 0 ; }
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 11/38 ALSA: hda: Keep the controller initialization even if no codecs found
In reply to Sasha LevinFrom: Takashi Iwai <[email protected]>
[ Upstream commit 9479e75fca370a5220784f7596bf598c4dad0b9b ]
Currently, when the HD-audio controller driver doesn't detect any codecs, it tries to abort the probe. But this abort happens at the delayed probe, i.e. the primary probe call already returned success, hence the driver is never unbound until user does so explicitly. As a result, it may leave the HD-audio device in the running state without the runtime PM. More badly, if the device is a HD-audio bus that is tied with a GPU, GPU cannot reach to the full power down and consumes unnecessarily much power.
This patch changes the logic after no-codec situation; it continues probing without the further codec initialization but keep the controller driver running normally.
--- sound/pci/hda/hda_intel.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
sound/pci/hda/hda_intel.c +7 -5
@@ -2009,7 +2009,7 @@ static int azx_first_init(struct azx *chip)/* codec detection */ if (!azx_bus (chip)->codec_mask) {dev_err (card->dev,"no codecs found!\n" ); -return -ENODEV ; +/* keep running the rest for the runtime PM */ }if (azx_acquire_irq (chip,0 ) <0 )
@@ -2303,9 +2303,11 @@ static int azx_probe_continue(struct azx *chip)#endif /* create codec instances */ - err =azx_probe_codecs (chip, azx_max_codecs[chip->driver_type]); -if (err <0 ) - goto out_free; +if (bus->codec_mask) { + err =azx_probe_codecs (chip, azx_max_codecs[chip->driver_type]); +if (err <0 ) + goto out_free; + }#ifdef CONFIG_SND_HDA_PATCH_LOADER if (chip->fw) {
@@ -2319,7 +2321,7 @@ static int azx_probe_continue(struct azx *chip) #endif }#endif -if ((probe_only[dev] &1 ) ==0 ) { +if (bus->codec_mask && !(probe_only[dev] &1 )) { err =azx_codec_configure (chip);if (err <0 ) goto out_free;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 22/38 ALSA: hda: call runtime_allow() for all hda controllers
In reply to Sasha LevinFrom: Hui Wang <[email protected]>
[ Upstream commit 9a6418487b566503c772cb6e7d3d44e652b019b0 ]
Before the pci_driver->probe() is called, the pci subsystem calls runtime_forbid() and runtime_get_sync() on this pci dev, so only call runtime_put_autosuspend() is not enough to enable the runtime_pm on this device.
For controllers with vgaswitcheroo feature, the pci/quirks.c will call runtime_allow() for this dev, then the controllers could enter rt_idle/suspend/resume, but for non-vgaswitcheroo controllers like Intel hda controllers, the runtime_pm is not enabled because the runtime_allow() is not called.
Since it is no harm calling runtime_allow() twice, here let hda driver call runtime_allow() for all controllers. Then the runtime_pm is enabled on all controllers after the put_autosuspend() is called.
--- sound/pci/hda/hda_intel.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/hda_intel.c +1 -0
@@ -2356,6 +2356,7 @@ static int azx_probe_continue(struct azx *chip)if (azx_has_pm_runtime (chip)) {pm_runtime_use_autosuspend (&pci->dev); +pm_runtime_allow (&pci->dev);pm_runtime_put_autosuspend (&pci->dev); }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 38/38 hwmon: (jc42) Fix name to have no illegal characters
In reply to Sasha LevinFrom: Sascha Hauer <[email protected]>
[ Upstream commit c843b382e61b5f28a3d917712c69a344f632387c ]
The jc42 driver passes I2C client's name as hwmon device name. In case of device tree probed devices this ends up being part of the compatible string, "jc-42.4-temp". This name contains hyphens and the hwmon core doesn't like this:
jc42 2-0018: hwmon: 'jc-42.4-temp' is not a valid name attribute, please fix
This changes the name to "jc42" which doesn't have any illegal characters.
--- drivers/hwmon/jc42.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/jc42.c +1 -1
@@ -506,7 +506,7 @@ static int jc42_probe(struct i2c_client *client, const struct i2c_device_id *id) } data->config = config; - hwmon_dev =devm_hwmon_device_register_with_info (dev, client->name, + hwmon_dev =devm_hwmon_device_register_with_info (dev,"jc42" , data, &jc42_chip_info,NULL );return PTR_ERR_OR_ZERO (hwmon_dev);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 34/38 ext4: convert BUG_ON's to WARN_ON's in mballoc.c
In reply to Sasha LevinFrom: Theodore Ts'o <[email protected]>
[ Upstream commit 907ea529fc4c3296701d2bfc8b831dd2a8121a34 ]
If the in-core buddy bitmap gets corrupted (or out of sync with the block bitmap), issue a WARN_ON and try to recover. In most cases this involves skipping trying to allocate out of a particular block group. We can end up declaring the file system corrupted, which is fair, since the file system probably should be checked before we proceed any further.
Google-Bug-Id: 34811296
Google-Bug-Id: 34639169
--- fs/ext4/mballoc.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/ext4/mballoc.c +4 -2
@@ -1936,7 +1936,8 @@ void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac,int free; free = e4b->bd_info->bb_free; -BUG_ON (free <=0 ); +if (WARN_ON (free <=0 )) +return ; i = e4b->bd_info->bb_first_free;
@@ -1959,7 +1960,8 @@ void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac, }mb_find_extent (e4b, i, ac->ac_g_ex.fe_len, &ex); -BUG_ON (ex.fe_len <=0 ); +if (WARN_ON (ex.fe_len <=0 )) +break ;if (free < ex.fe_len) {ext4_grp_locked_error (sb, e4b->bd_group,0 ,0 , "%d free clusters as per "
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 35/38 irqchip/gic-v4.1: Add support for VPENDBASER's Dirty+Valid signaling
In reply to Sasha LevinFrom: Marc Zyngier <[email protected]>
[ Upstream commit 96806229ca033f85310bc5c203410189f8a1d2ee ]
When a vPE is made resident, the GIC starts parsing the virtual pending table to deliver pending interrupts. This takes place asynchronously, and can at times take a long while. Long enough that the vcpu enters the guest and hits WFI before any interrupt has been signaled yet. The vcpu then exits, blocks, and now gets a doorbell. Rince, repeat.
In order to avoid the above, a (optional on GICv4, mandatory on v4.1) feature allows the GIC to feedback to the hypervisor whether it is done parsing the VPT by clearing the GICR_VPENDBASER.Dirty bit. The hypervisor can then wait until the GIC is ready before actually running the vPE.
Plug the detection code as well as polling on vPE schedule. While at it, tidy-up the kernel message that displays the GICv4 optional features.
--- drivers/irqchip/irq-gic-v3-its.c | 19 +++++++++++++++++++ drivers/irqchip/irq-gic-v3.c | 11 +++++++---- include/linux/irqchip/arm-gic-v3.h | 2 ++ 3 files changed, 28 insertions(+), 4 deletions(-)
drivers/irqchip/irq-gic-v3-its.c +19 -0
@@ -14,6 +14,7 @@#include <linux/dma-iommu.h> #include <linux/efi.h> #include <linux/interrupt.h> +#include <linux/iopoll.h> #include <linux/irqdomain.h> #include <linux/list.h> #include <linux/log2.h>
@@ -3516,6 +3517,20 @@ static int its_vpe_set_affinity(struct irq_data *d,return IRQ_SET_MASK_OK_DONE ; } +static void its_wait_vpt_parse_complete (void ) +{ +void __iomem *vlpi_base =gic_data_rdist_vlpi_base (); +u64 val; + +if (!gic_rdists->has_vpend_valid_dirty) +return ; + +WARN_ON_ONCE (readq_relaxed_poll_timeout (vlpi_base +GICR_VPENDBASER , + val, + !(val & GICR_VPENDBASER_Dirty), +10 ,500 )); +} +static void its_vpe_schedule (struct its_vpe *vpe) {void __iomem *vlpi_base =gic_data_rdist_vlpi_base ();
@@ -3546,6 +3561,8 @@ static void its_vpe_schedule(struct its_vpe *vpe) val |= vpe->idai ?GICR_VPENDBASER_IDAI :0 ; val |= GICR_VPENDBASER_Valid;gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); + +its_wait_vpt_parse_complete (); }static void its_vpe_deschedule (struct its_vpe *vpe)
@@ -3752,6 +3769,8 @@ static void its_vpe_4_1_schedule(struct its_vpe *vpe, val |=FIELD_PREP (GICR_VPENDBASER_4_1_VPEID , vpe->vpe_id);gicr_write_vpendbaser (val, vlpi_base +GICR_VPENDBASER ); + +its_wait_vpt_parse_complete (); } static void its_vpe_4_1_deschedule(struct its_vpe *vpe,
drivers/irqchip/irq-gic-v3.c +7 -4
@@ -866,6 +866,7 @@ static int __gic_update_rdist_properties(struct redist_region *region, gic_data.rdists.has_rvpeid &= !!(typer &GICR_TYPER_RVPEID ); gic_data.rdists.has_direct_lpi &= (!!(typer & GICR_TYPER_DirectLPIS) | gic_data.rdists.has_rvpeid); + gic_data.rdists.has_vpend_valid_dirty &= !!(typer &GICR_TYPER_DIRTY );/* Detect non-sensical configurations */ if (WARN_ON_ONCE (gic_data.rdists.has_rvpeid && !gic_data.rdists.has_vlpis)) {
@@ -886,10 +887,11 @@ static void gic_update_rdist_properties(void)if (WARN_ON (gic_data.ppi_nr ==UINT_MAX )) gic_data.ppi_nr =0 ;pr_info ("%d PPIs implemented\n" , gic_data.ppi_nr); -pr_info ("%sVLPI support, %sdirect LPI support, %sRVPEID support\n" , - !gic_data.rdists.has_vlpis ?"no " :"" , - !gic_data.rdists.has_direct_lpi ?"no " :"" , - !gic_data.rdists.has_rvpeid ?"no " :"" ); +if (gic_data.rdists.has_vlpis) +pr_info ("GICv4 features: %s%s%s\n" , + gic_data.rdists.has_direct_lpi ?"DirectLPI " :"" , + gic_data.rdists.has_rvpeid ?"RVPEID " :"" , + gic_data.rdists.has_vpend_valid_dirty ?"Valid+Dirty " :"" ); }/* Check whether it's single security state view */
@@ -1614,6 +1616,7 @@ static int __init gic_init_bases(void __iomem *dist_base, gic_data.rdists.has_rvpeid = true; gic_data.rdists.has_vlpis = true; gic_data.rdists.has_direct_lpi = true; + gic_data.rdists.has_vpend_valid_dirty = true;if (WARN_ON (!gic_data.domain) ||WARN_ON (!gic_data.rdists.rdist)) { err = -ENOMEM ;
include/linux/irqchip/arm-gic-v3.h +2 -0
@@ -241,6 +241,7 @@#define GICR_TYPER_PLPIS (1U << 0)#define GICR_TYPER_VLPIS (1U << 1) +#define GICR_TYPER_DIRTY (1U << 2)#define GICR_TYPER_DirectLPIS (1U << 3)#define GICR_TYPER_LAST (1U << 4)#define GICR_TYPER_RVPEID (1U << 7)
@@ -665,6 +666,7 @@ struct rdists {bool has_vlpis;bool has_rvpeid;bool has_direct_lpi; +bool has_vpend_valid_dirty; };struct irq_domain ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 27/38 sched/vtime: Work around an unitialized variable warning
In reply to Sasha LevinFrom: Borislav Petkov <[email protected]>
[ Upstream commit e0d648f9d883ec1efab261af158d73aa30e9dd12 ]
Work around this warning:
kernel/sched/cputime.c: In function ‘kcpustat_field’:
kernel/sched/cputime.c:1007:6: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
because GCC can't see that val is used only when err is 0.
--- kernel/sched/cputime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/sched/cputime.c +2 -2
@@ -1003,12 +1003,12 @@ u64 kcpustat_field(struct kernel_cpustat *kcpustat, enum cpu_usage_stat usage, int cpu) {u64 *cpustat = kcpustat->cpustat; +u64 val = cpustat[usage];struct rq *rq; -u64 val;int err;if (!vtime_accounting_enabled_cpu (cpu)) -return cpustat[usage]; +return val; rq =cpu_rq (cpu);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 26/38 sched/isolation: Allow "isolcpus=" to skip unknown sub-parameters
In reply to Sasha LevinFrom: Peter Xu <[email protected]>
[ Upstream commit 3662daf023500dc084fa3b96f68a6f46179ddc73 ]
The "isolcpus=" parameter allows sub-parameters before the cpulist is specified, and if the parser detects an unknown sub-parameters the whole parameter will be ignored.
This design is incompatible with itself when new sub-parameters are added. An older kernel will not recognize the new sub-parameter and will invalidate the whole parameter so the CPU isolation will not take effect. It emits a warning:
isolcpus: Error, unknown flag
The better and compatible way is to allow "isolcpus=" to skip unknown sub-parameters, so that even if new sub-parameters are added an older kernel will still be able to behave as usual even if with the new sub-parameter specified on the command line.
Ideally this should have been there when the first sub-parameter for "isolcpus=" was introduced.
--- kernel/sched/isolation.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-)
kernel/sched/isolation.c +19 -2
@@ -149,6 +149,9 @@ __setup("nohz_full=", housekeeping_nohz_full_setup);static int __init housekeeping_isolcpus_setup (char *str) {unsigned int flags =0 ; +bool illegal = false; +char *par; +int len;while (isalpha (*str)) {if (!strncmp (str,"nohz," ,5 )) {
@@ -169,8 +172,22 @@ static int __init housekeeping_isolcpus_setup(char *str)continue ; } -pr_warn ("isolcpus: Error, unknown flag\n" ); -return 0 ; +/* +* Skip unknown sub-parameter and validate that it is not +* containing an invalid character. +*/ +for (par = str, len =0 ; *str && *str !=',' ; str++, len++) { +if (!isalpha (*str) && *str !='_' ) + illegal = true; + } + +if (illegal) { +pr_warn ("isolcpus: Invalid flag %.*s\n" , len, par); +return 0 ; + } + +pr_info ("isolcpus: Skipped unknown flag %.*s\n" , len, par); + str++; }/* Default behaviour for isolcpus without flags */
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 24/38 net/cxgb4: Check the return from t4_query_params properly
In reply to Sasha LevinFrom: Jason Gunthorpe <[email protected]>
[ Upstream commit c799fca8baf18d1bbbbad6c3b736eefbde8bdb90 ]
Positive return values are also failures that don't set val, although this probably can't happen. Fixes gcc 10 warning:
drivers/net/ethernet/chelsio/cxgb4/t4_hw.c: In function ‘t4_phy_fw_ver’:drivers/net/ethernet/chelsio/cxgb4/t4_hw.c:3747:14: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
3747 | *phy_fw_ver = val;
--- drivers/net/ethernet/chelsio/cxgb4/t4_hw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/chelsio/cxgb4/t4_hw.c +1 -1
@@ -3748,7 +3748,7 @@ int t4_phy_fw_ver(struct adapter *adap, int *phy_fw_ver) FW_PARAMS_PARAM_Z_V(FW_PARAMS_PARAM_DEV_PHYFW_VERSION)); ret =t4_query_params (adap, adap->mbox, adap->pf,0 ,1 , ¶m, &val); -if (ret <0 ) +if (ret)return ret; *phy_fw_ver = val;return 0 ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 19/38 objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
In reply to Sasha LevinFrom: Josh Poimboeuf <[email protected]>
[ Upstream commit bd841d6154f5f41f8a32d3c1b0bc229e326e640a ]
CONFIG_UBSAN_TRAP causes GCC to emit a UD2 whenever it encounters an unreachable code path. This includes __builtin_unreachable(). Because the BUG() macro uses __builtin_unreachable() after it emits its own UD2, this results in a double UD2. In this case objtool rightfully detects that the second UD2 is unreachable:
init/main.o: warning: objtool: repair_env_string()+0x1c8: unreachable instruction
We weren't able to figure out a way to get rid of the double UD2s, so just silence the warning.
--- tools/objtool/check.c | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-)
tools/objtool/check.c +15 -2
@@ -2307,14 +2307,27 @@ static bool ignore_unreachable_insn(struct instruction *insn) !strcmp(insn->sec->name, ".altinstr_aux"))return true; +if (!insn->func) +return false; + +/* +* CONFIG_UBSAN_TRAP inserts a UD2 when it sees +* __builtin_unreachable(). The BUG() macro has an unreachable() after +* the UD2, which causes GCC's undefined trap logic to emit another UD2 +* (or occasionally a JMP to UD2). +*/ +if (list_prev_entry (insn, list)->dead_end && + (insn->type ==INSN_BUG || + (insn->type ==INSN_JUMP_UNCONDITIONAL && + insn->jump_dest && insn->jump_dest->type ==INSN_BUG ))) +return true; +/* * Check if this (or a subsequent) instruction is related to * CONFIG_UBSAN or CONFIG_KASAN. * * End the search at 5 instructions to avoid going into the weeds. */ -if (!insn->func) -return false;for (i =0 ; i <5 ; i++) {if (is_kasan_insn (insn) ||is_ubsan_insn (insn))
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 17/38 clk: asm9260: fix __clk_hw_register_fixed_rate_with_accuracy typo
In reply to Sasha LevinFrom: Arnd Bergmann <[email protected]>
[ Upstream commit 924ed1f5c181132897c5928af7f3afd28792889c ]
The __clk_hw_register_fixed_rate_with_accuracy() function (with two '_') does not exist, and apparently never did:
drivers/clk/clk-asm9260.c: In function 'asm9260_acc_init':drivers/clk/clk-asm9260.c:279:7: error: implicit declaration of function '__clk_hw_register_fixed_rate_with_accuracy'; did you mean 'clk_hw_register_fixed_rate_with_accuracy'? [-Werror=implicit-function-declaration]
279 | hw = __clk_hw_register_fixed_rate_with_accuracy(NULL, NULL, pll_clk,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| clk_hw_register_fixed_rate_with_accuracy
drivers/clk/clk-asm9260.c:279:5: error: assignment to 'struct clk_hw *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
279 | hw = __clk_hw_register_fixed_rate_with_accuracy(NULL, NULL, pll_clk,
| ^From what I can tell, __clk_hw_register_fixed_rate() is the correct API here, so use that instead.
--- drivers/clk/clk-asm9260.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/clk/clk-asm9260.c +1 -1
@@ -276,7 +276,7 @@ static void __init asm9260_acc_init(struct device_node *np)/* TODO: Convert to DT parent scheme */ ref_clk =of_clk_get_parent_name (np,0 ); - hw =__clk_hw_register_fixed_rate_with_accuracy (NULL ,NULL , pll_clk, + hw =__clk_hw_register_fixed_rate (NULL ,NULL , pll_clk, ref_clk,NULL ,NULL ,0 , rate,0 ,CLK_FIXED_RATE_PARENT_ACCURACY );
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 8/38 xfs: acquire superblock freeze protection on eofblocks scans
In reply to Sasha LevinFrom: Brian Foster <[email protected]>
[ Upstream commit 4b674b9ac852937af1f8c62f730c325fb6eadcdb ]
The filesystem freeze sequence in XFS waits on any background eofblocks or cowblocks scans to complete before the filesystem is quiesced. At this point, the freezer has already stopped the transaction subsystem, however, which means a truncate or cowblock cancellation in progress is likely blocked in transaction allocation. This results in a deadlock between freeze and the associated scanner.
Fix this problem by holding superblock write protection across calls into the block reapers. Since protection for background scans is acquired from the workqueue task context, trylock to avoid a similar deadlock between freeze and blocking on the write lock.
--- fs/xfs/xfs_icache.c | 10 ++++++++++ fs/xfs/xfs_ioctl.c | 5 ++++- 2 files changed, 14 insertions(+), 1 deletion(-)
fs/xfs/xfs_icache.c +10 -0
@@ -907,7 +907,12 @@ xfs_eofblocks_worker( {struct xfs_mount *mp =container_of (to_delayed_work (work), struct xfs_mount, m_eofblocks_work); + +if (!sb_start_write_trylock (mp->m_super)) +return ;xfs_icache_free_eofblocks (mp,NULL ); +sb_end_write (mp->m_super); +xfs_queue_eofblocks (mp); }
@@ -934,7 +939,12 @@ xfs_cowblocks_worker( {struct xfs_mount *mp =container_of (to_delayed_work (work), struct xfs_mount, m_cowblocks_work); + +if (!sb_start_write_trylock (mp->m_super)) +return ;xfs_icache_free_cowblocks (mp,NULL ); +sb_end_write (mp->m_super); +xfs_queue_cowblocks (mp); }
fs/xfs/xfs_ioctl.c +4 -1
@@ -2264,7 +2264,10 @@ xfs_file_ioctl(if (error)return error; -return xfs_icache_free_eofblocks (mp, &keofb); +sb_start_write (mp->m_super); + error =xfs_icache_free_eofblocks (mp, &keofb); +sb_end_write (mp->m_super); +return error; }default :
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 7/38 afs: Fix length of dump of bad YFSFetchStatus record
In reply to Sasha LevinFrom: David Howells <[email protected]>
[ Upstream commit 3efe55b09a92a59ed8214db801683cf13c9742c4 ]
Fix the length of the dump of a bad YFSFetchStatus record. The function was copied from the AFS version, but the YFS variant contains bigger fields and extra information, so expand the dump to match.
--- fs/afs/yfsclient.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/afs/yfsclient.c +3 -3
@@ -165,15 +165,15 @@ static void xdr_dump_bad(const __be32 *bp)int i;pr_notice ("YFS XDR: Bad status record\n" ); -for (i =0 ; i <5 *4 *4 ; i +=16 ) { +for (i =0 ; i <6 *4 *4 ; i +=16 ) {memcpy (x, bp,16 ); bp +=4 ;pr_notice ("%03x: %08x %08x %08x %08x\n" , i,ntohl (x[0 ]),ntohl (x[1 ]),ntohl (x[2 ]),ntohl (x[3 ])); } -memcpy (x, bp,4 ); -pr_notice ("0x50: %08x\n" ,ntohl (x[0 ])); +memcpy (x, bp,8 ); +pr_notice ("0x60: %08x %08x\n" ,ntohl (x[0 ]),ntohl (x[1 ])); }/*
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 4/38 signal: check sig before setting info in kill_pid_usb_asyncio
In reply to Sasha LevinFrom: Zhiqiang Liu <[email protected]>
[ Upstream commit eaec2b0bd30690575c581eebffae64bfb7f684ac ]
In kill_pid_usb_asyncio, if signal is not valid, we do not need to set info struct.
--- kernel/signal.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/signal.c +3 -3
@@ -1510,15 +1510,15 @@ int kill_pid_usb_asyncio(int sig, int errno, sigval_t addr,unsigned long flags;int ret = -EINVAL ; +if (!valid_signal (sig)) +return ret; +clear_siginfo (&info); info.si_signo = sig; info.si_errno = errno; info.si_code =SI_ASYNCIO ; *((sigval_t *)&info.si_pid) = addr; -if (!valid_signal (sig)) -return ret; -rcu_read_lock (); p =pid_task (pid,PIDTYPE_PID );if (!p) {
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 2/38 net: fec: set GPR bit on suspend by DT configuration.
In reply to Sasha LevinFrom: Martin Fuzzey <[email protected]>
[ Upstream commit da722186f6549d752ea5b5fbc18111833c81a133 ]
On some SoCs, such as the i.MX6, it is necessary to set a bit in the SoC level GPR register before suspending for wake on lan to work.
The fec platform callback sleep_mode_enable was intended to allow this but the platform implementation was NAK'd back in 2015 [1]
This means that, currently, wake on lan is broken on mainline for the i.MX6 at least.
So implement the required bit setting in the fec driver by itself by adding a new optional DT property indicating the GPR register and adding the offset and bit information to the driver.
[1] https://www.spinics.net/lists/netdev/msg310922.html
--- drivers/net/ethernet/freescale/fec.h | 7 + drivers/net/ethernet/freescale/fec_main.c | 149 +++++++++++++++++----- 2 files changed, 127 insertions(+), 29 deletions(-)
drivers/net/ethernet/freescale/fec.h +7 -0
@@ -488,6 +488,12 @@ struct fec_enet_priv_rx_q {struct sk_buff *rx_skbuff[RX_RING_SIZE ]; }; +struct fec_stop_mode_gpr { +struct regmap *gpr; +u8 reg; +u8 bit; +}; +/* The FEC buffer descriptors track the ring buffers. The rx_bd_base and * tx_bd_base always point to the base of the buffer descriptors. The * cur_rx and cur_tx point to the currently available buffer.
@@ -562,6 +568,7 @@ struct fec_enet_private {int hwts_tx_en;struct delayed_work time_keep;struct regulator *reg_phy; +struct fec_stop_mode_gpr stop_gpr;unsigned int tx_align;unsigned int rx_align;
drivers/net/ethernet/freescale/fec_main.c +120 -29
237 lines not on this page · raw message
Signature · 1 line
2.20.1
Re: [PATCH AUTOSEL 5.6 12/38] ALSA: hda: Skip controller resume if not needed
In reply to Sasha LevinQuoted 35 lines · Sasha Levin
From: Takashi Iwai <[email protected]>
[ Upstream commit
c4c8dd6ef807663e42a5f04ea77cd62029eb99fa]The HD-audio controller does system-suspend and resume operations by directly calling its helpers
__azx_runtime_suspend()and__azx_runtime_resume(). However, in general, we don't have to resume always the device fully at the system resume; typically, if a device has been runtime-suspended, we can leave it to runtime resume.Usually for achieving this, the driver would call
pm_runtime_force_suspend()andpm_runtime_force_resume()pairs in the system suspend and resume ops. Unfortunately, this doesn't work for the resume path in our case. For handling the jack detection at the system resume, a child codec device may need the (literally) forcibly resume even if it's been runtime-suspended, and for that, the controller device must be also resumed even if it's been suspended.This patch is an attempt to improve the situation. It replaces the direct __azx_runtime_suspend()/_resume() calls with with
pm_runtime_force_suspend()andpm_runtime_force_resume()with a slight trick as we've done for the codec side. More exactly:-
azx_has_pm_runtime()check is dropped fromazx_runtime_suspend()andazx_runtime_resume(), so that it can be properly executed from the system-suspend/resume path- The WAKEEN handling depends on the card's power state now; it's set and cleared only for the runtime-suspend
-
azx_resume()checks whether any codec may need the forcible resume beforehand. If the forcible resume is required, it does temporary PM refcount up/down for actually triggering the runtime resume.
Quoted 8 lines
- A new helper function,
hda_codec_need_resume(), is introduced for checking whether the codec needs a forcible runtime-resume, and the existing code is rewritten with that.Signed-off-by Takashi Iwai <[email protected]>Signed-off-by Sasha Levin <[email protected]>
This commit is known to cause a regression, and the fix patch is included in today's pull request. If we apply this, better to wait for the next batch including its fix.
thanks,
Takashi
Quoted 124 lines
--- include/sound/hda_codec.h | 5 +++++ sound/pci/hda/hda_codec.c | 2 +- sound/pci/hda/hda_intel.c | 38 +++++++++++++++++++++++++++----------- 3 files changed, 33 insertions(+), 12 deletions(-)include/sound/hda_codec.h +5
-0@@ -494,6 +494,11 @@ void snd_hda_update_power_acct(struct hda_codec *codec);static inline void snd_hda_set_power_save (struct hda_bus *bus,int delay) {}#endif +static inline bool hda_codec_need_resume (struct hda_codec *codec) +{ +return !codec->relaxed_resume && codec->jacktbl.used; +} +#ifdef CONFIG_SND_HDA_PATCH_LOADER /* * patch firmware sound/pci/hda/hda_codec.c +1
-1@@ -2951,7 +2951,7 @@ static int hda_codec_runtime_resume(struct device *dev)static int hda_codec_force_resume (struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); -bool forced_resume = !codec->relaxed_resume && codec->jacktbl.used; +bool forced_resume =hda_codec_need_resume (codec);int ret;/* The get/put pair below enforces the runtime resume even if the sound/pci/hda/hda_intel.c +27
-11@@ -1027,7 +1027,7 @@ static int azx_suspend(struct device *dev) chip = card->private_data; bus =azx_bus (chip);snd_power_change_state (card, SNDRV_CTL_POWER_D3hot); -__azx_runtime_suspend (chip); +pm_runtime_force_suspend (dev);if (bus->irq >=0 ) {free_irq (bus->irq, chip); bus->irq =-1 ;@@ -1044,7 +1044,9 @@ static int azx_suspend(struct device *dev)static int azx_resume (struct device *dev) {struct snd_card *card =dev_get_drvdata (dev); +struct hda_codec *codec;struct azx *chip; +bool forced_resume = false;if (!azx_is_pm_ready (card))return 0 ;@@ -1055,7 +1057,20 @@ static int azx_resume(struct device *dev) chip->msi =0 ;if (azx_acquire_irq (chip,1 ) <0 )return -EIO ; -__azx_runtime_resume (chip, false); + +/* check for the forced resume */ +list_for_each_codec (codec, &chip->bus) { +if (hda_codec_need_resume (codec)) { + forced_resume = true; +break ; + } + } + +if (forced_resume) +pm_runtime_get_noresume (dev); +pm_runtime_force_resume (dev); +if (forced_resume) +pm_runtime_put (dev);snd_power_change_state (card,SNDRV_CTL_POWER_D0 );trace_azx_resume (chip);@@ -1102,12 +1117,12 @@ static int azx_runtime_suspend(struct device *dev)if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ;/* enable controller wake up event */ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | -STATESTS_INT_MASK ); +if (snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | +STATESTS_INT_MASK ); + }__azx_runtime_suspend (chip);trace_azx_runtime_suspend (chip);@@ -1118,17 +1133,18 @@ static int azx_runtime_resume(struct device *dev) {struct snd_card *card =dev_get_drvdata (dev);struct azx *chip; +bool from_rt =snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ;if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ; -__azx_runtime_resume (chip, true); +__azx_runtime_resume (chip, from_rt);/* disable controller Wake Up event*/ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & - ~STATESTS_INT_MASK ); +if (from_rt) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & + ~STATESTS_INT_MASK ); + }trace_azx_runtime_resume (chip);return 0 ;Signature · 1 line
2.20.1
Re: [PATCH AUTOSEL 5.6 28/38] i2c: remove i2c_new_probed_device API
In reply to Sasha LevinQuoted 10 lines · Sasha Levin
From: Wolfram Sang <[email protected]>
[ Upstream commit
3c1d1613be80c2e17f1ddf672df1d8a8caebfd0d]All in-tree users have been converted to the new
i2c_new_scanned_devicefunction, so remove this deprecated one.Signed-off-by Wolfram Sang <[email protected]>Signed-off-by Wolfram Sang <[email protected]>Signed-off-by Sasha Levin <[email protected]>
This should not be backported. It is only since this merge window that all in-tree users are converted!
Sasha Levin
maintainerRe: [PATCH AUTOSEL 5.6 28/38] i2c: remove i2c_new_probed_device API
Quoted 8 lines · Wolfram Sang
Quoted 7 lines · Sasha Levin
From: Wolfram Sang <[email protected]>
[ Upstream commit
3c1d1613be80c2e17f1ddf672df1d8a8caebfd0d]All in-tree users have been converted to the new
i2c_new_scanned_devicefunction, so remove this deprecated one.
Quoted 6 lines
Quoted 3 lines
Signed-off-by Wolfram Sang <[email protected]>Signed-off-by Wolfram Sang <[email protected]>Signed-off-by Sasha Levin <[email protected]>This should not be backported. It is only since this merge window that all in-tree users are converted!
Uh, I'm not sure how this snuck through. I've droped it, sorry!
Signature · 2 lines
Thanks, Sasha
Re: [PATCH AUTOSEL 5.6 30/38] i2c: tegra: Better handle case where CPU0 is busy for a long time
In reply to Sasha LevinQuoted 11 lines · Sasha Levin
From: Dmitry Osipenko <[email protected]>
[ Upstream commit
a900aeac253729411cf33c6cb598c152e9e4137f]Boot CPU0 always handle I2C interrupt and under some rare circumstances (like running KASAN + NFS root) it may stuck in uninterruptible state for a significant time. In this case we will get timeout if I2C transfer is running on a sibling CPU, despite of IRQ being raised. In order to handle this rare condition, the IRQ status needs to be checked after completion timeout.
Quoted 6 lines
Signed-off-by Dmitry Osipenko <[email protected]>Signed-off-by Wolfram Sang <wsa-z923LK4zBo2bacvFa/[email protected]>Signed-off-by Sasha Levin <[email protected]>--- drivers/i2c/busses/i2c-tegra.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-)
Hi Sasha,
can you drop this from the v5.6 stable queue please? Jon discovered that this patch introduces a regression in v5.7, and since we don't have a good understanding of why this is breaking things I think it'd be best if we reverted it for v5.7 until we come up with a good fix.
I think the same applies for the other i2c/tegra patch that's 31/38 of this series.
Thanks,
Thierry
Re: [PATCH AUTOSEL 5.6 12/38] ALSA: hda: Skip controller resume if not needed
In reply to Takashi Iwai(Minus "Linux kernel", that list has enough volume)
Op 24-04-2020 om 13:44 schreef Takashi Iwai:
Quoted 41 lines
Quoted 39 lines · Sasha Levin
From: Takashi Iwai <[email protected]>
[ Upstream commit
c4c8dd6ef807663e42a5f04ea77cd62029eb99fa]The HD-audio controller does system-suspend and resume operations by directly calling its helpers
__azx_runtime_suspend()and__azx_runtime_resume(). However, in general, we don't have to resume always the device fully at the system resume; typically, if a device has been runtime-suspended, we can leave it to runtime resume.Usually for achieving this, the driver would call
pm_runtime_force_suspend()andpm_runtime_force_resume()pairs in the system suspend and resume ops. Unfortunately, this doesn't work for the resume path in our case. For handling the jack detection at the system resume, a child codec device may need the (literally) forcibly resume even if it's been runtime-suspended, and for that, the controller device must be also resumed even if it's been suspended.This patch is an attempt to improve the situation. It replaces the direct __azx_runtime_suspend()/_resume() calls with with
pm_runtime_force_suspend()andpm_runtime_force_resume()with a slight trick as we've done for the codec side. More exactly:-
azx_has_pm_runtime()check is dropped fromazx_runtime_suspend()andazx_runtime_resume(), so that it can be properly executed from the system-suspend/resume path- The WAKEEN handling depends on the card's power state now; it's set and cleared only for the runtime-suspend
-
azx_resume()checks whether any codec may need the forcible resume beforehand. If the forcible resume is required, it does temporary PM refcount up/down for actually triggering the runtime resume.- A new helper function,
hda_codec_need_resume(), is introduced for checking whether the codec needs a forcible runtime-resume, and the existing code is rewritten with that.
Quoted 8 lines
Quoted 4 lines
Signed-off-by Takashi Iwai <[email protected]>Signed-off-by Sasha Levin <[email protected]>This commit is known to cause a regression, and the fix patch is included in today's pull request. If we apply this, better to wait for the next batch including its fix.
These six patches, plus Takashi's fix on top of them, do not seem to have made it to 5.6.7 or 5.6.8 in the end. Is there a plan to include them in 5.6.9? Thanks,
Roy
Quoted 131 lines
thanks,
Takashi
Quoted 124 lines
--- include/sound/hda_codec.h | 5 +++++ sound/pci/hda/hda_codec.c | 2 +- sound/pci/hda/hda_intel.c | 38 +++++++++++++++++++++++++++----------- 3 files changed, 33 insertions(+), 12 deletions(-)include/sound/hda_codec.h +5
-0@@ -494,6 +494,11 @@ void snd_hda_update_power_acct(struct hda_codec *codec);static inline void snd_hda_set_power_save (struct hda_bus *bus,int delay) {}#endif +static inline bool hda_codec_need_resume (struct hda_codec *codec) +{ +return !codec->relaxed_resume && codec->jacktbl.used; +} +#ifdef CONFIG_SND_HDA_PATCH_LOADER /* * patch firmware sound/pci/hda/hda_codec.c +1
-1@@ -2951,7 +2951,7 @@ static int hda_codec_runtime_resume(struct device *dev)static int hda_codec_force_resume (struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); -bool forced_resume = !codec->relaxed_resume && codec->jacktbl.used; +bool forced_resume =hda_codec_need_resume (codec);int ret;/* The get/put pair below enforces the runtime resume even if the sound/pci/hda/hda_intel.c +27
-11@@ -1027,7 +1027,7 @@ static int azx_suspend(struct device *dev) chip = card->private_data; bus =azx_bus (chip);snd_power_change_state (card, SNDRV_CTL_POWER_D3hot); -__azx_runtime_suspend (chip); +pm_runtime_force_suspend (dev);if (bus->irq >=0 ) {free_irq (bus->irq, chip); bus->irq =-1 ;@@ -1044,7 +1044,9 @@ static int azx_suspend(struct device *dev)static int azx_resume (struct device *dev) {struct snd_card *card =dev_get_drvdata (dev); +struct hda_codec *codec;struct azx *chip; +bool forced_resume = false;if (!azx_is_pm_ready (card))return 0 ;@@ -1055,7 +1057,20 @@ static int azx_resume(struct device *dev) chip->msi =0 ;if (azx_acquire_irq (chip,1 ) <0 )return -EIO ; -__azx_runtime_resume (chip, false); + +/* check for the forced resume */ +list_for_each_codec (codec, &chip->bus) { +if (hda_codec_need_resume (codec)) { + forced_resume = true; +break ; + } + } + +if (forced_resume) +pm_runtime_get_noresume (dev); +pm_runtime_force_resume (dev); +if (forced_resume) +pm_runtime_put (dev);snd_power_change_state (card,SNDRV_CTL_POWER_D0 );trace_azx_resume (chip);@@ -1102,12 +1117,12 @@ static int azx_runtime_suspend(struct device *dev)if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ;/* enable controller wake up event */ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | -STATESTS_INT_MASK ); +if (snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) | +STATESTS_INT_MASK ); + }__azx_runtime_suspend (chip);trace_azx_runtime_suspend (chip);@@ -1118,17 +1133,18 @@ static int azx_runtime_resume(struct device *dev) {struct snd_card *card =dev_get_drvdata (dev);struct azx *chip; +bool from_rt =snd_power_get_state (card) ==SNDRV_CTL_POWER_D0 ;if (!azx_is_pm_ready (card))return 0 ; chip = card->private_data; -if (!azx_has_pm_runtime (chip)) -return 0 ; -__azx_runtime_resume (chip, true); +__azx_runtime_resume (chip, from_rt);/* disable controller Wake Up event*/ -azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & - ~STATESTS_INT_MASK ); +if (from_rt) { +azx_writew (chip,WAKEEN ,azx_readw (chip,WAKEEN ) & + ~STATESTS_INT_MASK ); + }trace_azx_runtime_resume (chip);return 0 ;Signature · 1 line
2.20.1
Sasha Levin
maintainerRe: [PATCH AUTOSEL 5.6 30/38] i2c: tegra: Better handle case where CPU0 is busy for a long time
In reply to Thierry RedingQuoted 21 lines · Thierry Reding
Quoted 11 lines · Sasha Levin
From: Dmitry Osipenko <[email protected]>
[ Upstream commit
a900aeac253729411cf33c6cb598c152e9e4137f]Boot CPU0 always handle I2C interrupt and under some rare circumstances (like running KASAN + NFS root) it may stuck in uninterruptible state for a significant time. In this case we will get timeout if I2C transfer is running on a sibling CPU, despite of IRQ being raised. In order to handle this rare condition, the IRQ status needs to be checked after completion timeout.
Quoted 6 lines
Signed-off-by Dmitry Osipenko <[email protected]>Signed-off-by Wolfram Sang <wsa-z923LK4zBo2bacvFa/[email protected]>Signed-off-by Sasha Levin <[email protected]>--- drivers/i2c/busses/i2c-tegra.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-)Hi Sasha,
Quoted 7 lines
can you drop this from the v5.6 stable queue please? Jon discovered that this patch introduces a regression in v5.7, and since we don't have a good understanding of why this is breaking things I think it'd be best if we reverted it for v5.7 until we come up with a good fix.
I think the same applies for the other i2c/tegra patch that's 31/38 of this series.
I've dropped both of these, thanks!
Signature · 2 lines
Thanks, Sasha
Sasha Levin
maintainerRe: [PATCH AUTOSEL 5.6 12/38] ALSA: hda: Skip controller resume if not needed
In reply to Roy SplietQuoted 49 lines · Roy Spliet
(Minus "Linux kernel", that list has enough volume)
Op 24-04-2020 om 13:44 schreef Takashi Iwai:
Quoted 46 lines
Quoted 43 lines · Sasha Levin
From: Takashi Iwai <[email protected]>
[ Upstream commit
c4c8dd6ef807663e42a5f04ea77cd62029eb99fa]The HD-audio controller does system-suspend and resume operations by directly calling its helpers
__azx_runtime_suspend()and__azx_runtime_resume(). However, in general, we don't have to resume always the device fully at the system resume; typically, if a device has been runtime-suspended, we can leave it to runtime resume.Usually for achieving this, the driver would call
pm_runtime_force_suspend()andpm_runtime_force_resume()pairs in the system suspend and resume ops. Unfortunately, this doesn't work for the resume path in our case. For handling the jack detection at the system resume, a child codec device may need the (literally) forcibly resume even if it's been runtime-suspended, and for that, the controller device must be also resumed even if it's been suspended.This patch is an attempt to improve the situation. It replaces the direct __azx_runtime_suspend()/_resume() calls with with
pm_runtime_force_suspend()andpm_runtime_force_resume()with a slight trick as we've done for the codec side. More exactly:-
azx_has_pm_runtime()check is dropped fromazx_runtime_suspend()andazx_runtime_resume(), so that it can be properly executed from the system-suspend/resume path- The WAKEEN handling depends on the card's power state now; it's set and cleared only for the runtime-suspend
-
azx_resume()checks whether any codec may need the forcible resume beforehand. If the forcible resume is required, it does temporary PM refcount up/down for actually triggering the runtime resume.- A new helper function,
hda_codec_need_resume(), is introduced for checking whether the codec needs a forcible runtime-resume, and the existing code is rewritten with that.Signed-off-by Takashi Iwai <[email protected]>Signed-off-by Sasha Levin <[email protected]>
Quoted 5 lines
Quoted 3 lines
This commit is known to cause a regression, and the fix patch is included in today's pull request. If we apply this, better to wait for the next batch including its fix.
These six patches, plus Takashi's fix on top of them, do not seem to have made it to 5.6.7 or 5.6.8 in the end. Is there a plan to include
AUTOSEL stuff take a while to hit the stable trees, if you want patches in quicker they should be tagged for stable...
Quoted 1 line
them in 5.6.9?
What are the commit ids?
Signature · 2 lines
Thanks, Sasha