5.15.72-rc1 review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 5.15.72-rc1 review
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +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.15.72-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.15.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.15.72-rc1
Ian Rogers <[email protected]>
perf evsel: Add tool event helpers
John Garry <[email protected]>
perf pmu: Fix alias events list
Chris Wilson <[email protected]>
drm/i915/gem: Really move i915_gem_context.link under ref protection
Nadav Amit <[email protected]>
x86/alternative: Fix race in try_get_desc()
Florian Fischer <[email protected]>
perf list: Print all available tool events
Wei Li <[email protected]>
perf tools: Enhance the matching of sub-commands abbreviations
James Clark <[email protected]>
perf tools: Check vmlinux/kallsyms arguments in all tools
Jin Yao <[email protected]>
perf list: Display hybrid PMU events with cpu type
Ian Rogers <[email protected]>
perf parse-events: Identify broken modifiers
Ian Rogers <[email protected]>
perf parse-events: Add new "metric-id" term
Ian Rogers <[email protected]>
perf parse-events: Add const to evsel name
Ian Rogers <[email protected]>
perf metric: Only add a referenced metric once
Ian Rogers <[email protected]>
perf metric: Add documentation and rename a variable.
Jim Mattson <[email protected]>
KVM: x86: Hide IA32_PLATFORM_DCA_CAP[31:0] from the guest
Florian Fainelli <[email protected]>
clk: iproc: Do not rely on node name for correct PLL setup
Han Xu <[email protected]>
clk: imx: imx6sx: remove the SET_RATE_PARENT flag for QSPI clocks
Al Viro <[email protected]>
don't use __kernel_write() on kmap_local_page()
Stefan Roesch <[email protected]>
fs: split off setxattr_copy and do_setxattr function from setxattr
Angus Chen <[email protected]>
vdpa/ifcvf: fix the calculation of queuepair
Wang Yufen <[email protected]>
selftests: Fix the if conditions of in test_extra_filter()
Lukas Wunner <[email protected]>
net: phy: Don't WARN for PHY_UP state in mdio_bus_phy_resume()
Junxiao Chang <[email protected]>
net: stmmac: power up/down serdes in stmmac_open/release
Hans de Goede <[email protected]>
wifi: mac80211: fix regression with non-QoS drivers
Michael Kelley <[email protected]>
nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
Peng Wu <[email protected]>
net/mlxbf_gige: Fix an IS_ERR() vs NULL bug in mlxbf_gige_mdio_probe
Rafael Mendonca <[email protected]>
cxgb4: fix missing unlock on ETHOFLD desc collect fail path
Hangyu Hua <[email protected]>
net: sched: act_ct: fix possible refcount leak in tcf_ct_init()
Peilin Ye <[email protected]>
usbnet: Fix memory leak in usbnet_disconnect()
Pali Rohár <[email protected]>
gpio: mvebu: Fix check for pwm support on non-A8K platforms
Yang Yingliang <[email protected]>
Input: melfas_mip4 - fix return value check in mip4_probe()
Brian Norris <[email protected]>
Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in suspend/resume time"
Francesco Dolcini <[email protected]>
drm/bridge: lt8912b: fix corrupted image output
Philippe Schenker <[email protected]>
drm/bridge: lt8912b: set hdmi or dvi mode
Philippe Schenker <[email protected]>
drm/bridge: lt8912b: add vsync hsync
Martin Povišer <[email protected]>
ASoC: tas2770: Reinit regcache on reset
Johan Hovold <[email protected]>
arm64: dts: qcom: sm8350: fix UFS PHY serdes size
Shengjiu Wang <[email protected]>
ASoC: imx-card: Fix refcount issue with of_node_put
Samuel Holland <[email protected]>
soc: sunxi: sram: Fix debugfs info for A64 SRAM C
Samuel Holland <[email protected]>
soc: sunxi: sram: Fix probe function ordering issues
Cai Huoqing <[email protected]>
soc: sunxi_sram: Make use of the helper function devm_platform_ioremap_resource()
Samuel Holland <[email protected]>
soc: sunxi: sram: Prevent the driver from being unbound
Samuel Holland <[email protected]>
soc: sunxi: sram: Actually claim SRAM regions
Romain Naour <[email protected]>
ARM: dts: am5748: keep usb4_tm disabled
Richard Zhu <[email protected]>
reset: imx7: Fix the iMX8MP PCIe PHY PERST support
YuTong Chang <[email protected]>
ARM: dts: am33xx: Fix MMCHS0 dma properties
Tianyu Lan <[email protected]>
swiotlb: max mapping size takes min align mask into account
Hans Verkuil <[email protected]>
media: v4l2-compat-ioctl32.c: zero buffer passed to v4l2_compat_get_array_args()
Nicolas Dufresne <[email protected]>
media: rkvdec: Disable H.264 error detection
Hangyu Hua <[email protected]>
media: dvb_vb2: fix possible out of bound access
Shuai Xue <[email protected]>
mm,hwpoison: check mm when killing accessing process
Minchan Kim <[email protected]>
mm: fix madivse_pageout mishandling on non-LRU page
Alistair Popple <[email protected]>
mm/migrate_device.c: flush TLB while holding PTL
Binyi Han <[email protected]>
mm: fix dereferencing possible ERR_PTR
Maurizio Lombardi <[email protected]>
mm: prevent page_frag_alloc() from corrupting the memory
Mel Gorman <[email protected]>
mm/page_alloc: fix race condition between build_all_zonelists and page allocation
Wenchao Chen <[email protected]>
mmc: hsq: Fix data stomping during mmc recovery
Sergei Antonov <[email protected]>
mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
Niklas Cassel <[email protected]>
libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
Maxime Coquelin <[email protected]>
vduse: prevent uninitialized memory accesses
Bokun Zhang <[email protected]>
drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV
Chris Wilson <[email protected]>
drm/i915/gt: Restrict forced preemption to the active context
Yang Shi <[email protected]>
powerpc/64s/radix: don't need to broadcast IPI for radix pmd collapse flush
Ulf Hansson <[email protected]>
Revert "firmware: arm_scmi: Add clock management to the SCMI power domain"
Alexander Couzens <[email protected]>
net: mt7531: only do PLL once after the reset
Greg Kroah-Hartman <[email protected]>
mm/damon/dbgfs: fix memory leak when using debugfs_lookup()
ChenXiaoSong <[email protected]>
ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
Linus Walleij <[email protected]>
ARM: dts: integrator: Tag PCI host with device_type
Jarkko Sakkinen <[email protected]>
x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd
Aidan MacDonald <[email protected]>
clk: ingenic-tcu: Properly enable registers before accessing timers
Marc Kleine-Budde <[email protected]>
can: c_can: don't cache TX messages for C_CAN cores
Sebastian Krzyszkowiak <[email protected]>
Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address
Frank Wunderlich <[email protected]>
net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
Mario Limonciello <[email protected]>
thunderbolt: Explicitly reset plug events delay back to USB4 spec value
Heikki Krogerus <[email protected]>
usb: typec: ucsi: Remove incorrect warning
Hongling Zeng <[email protected]>
uas: ignore UAS for Thinkplus chips
Hongling Zeng <[email protected]>
usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
Hongling Zeng <[email protected]>
uas: add no-uas quirk for Hiksemi usb_disk
Ming Lei <[email protected]>
cgroup: cgroup_get_from_id() must check the looked-up kn is a directory
Shakeel Butt <[email protected]>
cgroup: reduce dependency on cgroup_mutex
Alexander Sergeyev <[email protected]>
ALSA: hda/realtek: fix speakers and micmute on HP 855 G8
Mohan Kumar <[email protected]>
ALSA: hda: Fix Nvidia dp infoframe
Takashi Iwai <[email protected]>
ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation
Takashi Iwai <[email protected]>
ALSA: hda: Do disconnect jacks at codec unbind
-------------
Diffstat:
Makefile | 4 +- arch/arm/boot/dts/am33xx-l4.dtsi | 3 +- arch/arm/boot/dts/am5748.dtsi | 4 + arch/arm/boot/dts/integratorap.dts | 1 + arch/arm64/boot/dts/qcom/sm8350.dtsi | 2 +- arch/powerpc/mm/book3s64/radix_pgtable.c | 9 -- arch/x86/kernel/alternative.c | 45 ++++--- arch/x86/kernel/cpu/sgx/main.c | 15 ++- arch/x86/kvm/cpuid.c | 2 - drivers/ata/libata-core.c | 4 + drivers/clk/bcm/clk-iproc-pll.c | 12 +- drivers/clk/imx/clk-imx6sx.c | 4 +- drivers/clk/ingenic/tcu.c | 15 +-- drivers/firmware/arm_scmi/scmi_pm_domain.c | 26 ---- drivers/gpio/gpio-mvebu.c | 15 +-- drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 + drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 27 +++- drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 13 -- drivers/gpu/drm/bridge/lontium-lt8912b.c | 13 +- drivers/gpu/drm/i915/gem/i915_gem_context.c | 8 +- drivers/gpu/drm/i915/gt/intel_engine_types.h | 15 +++ .../gpu/drm/i915/gt/intel_execlists_submission.c | 21 ++- drivers/input/keyboard/snvs_pwrkey.c | 2 +- drivers/input/touchscreen/melfas_mip4.c | 2 +- drivers/media/dvb-core/dvb_vb2.c | 11 ++ drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 2 + drivers/mmc/host/mmc_hsq.c | 2 +- drivers/mmc/host/moxart-mmc.c | 17 +-- drivers/net/can/c_can/c_can.h | 17 ++- drivers/net/can/c_can/c_can_main.c | 11 +- drivers/net/dsa/mt7530.c | 15 ++- drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.c | 28 ++-- .../ethernet/mellanox/mlxbf_gige/mlxbf_gige_mdio.c | 4 +- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 23 ++-- drivers/net/phy/phy_device.c | 10 +- drivers/net/usb/qmi_wwan.c | 1 + drivers/net/usb/usbnet.c | 7 +- drivers/nvme/host/core.c | 6 +- drivers/reset/reset-imx7.c | 1 + drivers/soc/sunxi/sunxi_sram.c | 27 ++-- drivers/staging/media/rkvdec/rkvdec-h264.c | 4 +- drivers/thunderbolt/switch.c | 1 + drivers/usb/storage/unusual_uas.h | 21 +++ drivers/usb/typec/ucsi/ucsi.c | 2 - drivers/vdpa/ifcvf/ifcvf_base.c | 4 +- drivers/vdpa/vdpa_user/vduse_dev.c | 9 +- fs/coredump.c | 38 +++++- fs/internal.h | 27 ++++ fs/ntfs/super.c | 3 +- fs/read_write.c | 22 +-- fs/xattr.c | 84 ++++++++---- kernel/cgroup/cgroup.c | 54 +++++--- kernel/dma/swiotlb.c | 13 +- mm/damon/dbgfs.c | 19 ++- mm/madvise.c | 7 +- mm/memory-failure.c | 3 + mm/migrate.c | 5 +- mm/page_alloc.c | 65 +++++++-- mm/secretmem.c | 2 +- net/mac80211/tx.c | 4 + net/sched/act_ct.c | 5 +- sound/pci/hda/hda_bind.c | 6 +- sound/pci/hda/hda_jack.c | 11 ++ sound/pci/hda/hda_jack.h | 1 + sound/pci/hda/patch_hdmi.c | 23 +++- sound/pci/hda/patch_realtek.c | 12 ++ sound/soc/codecs/tas2770.c | 3 + sound/soc/fsl/imx-card.c | 4 + tools/perf/Documentation/perf-list.txt | 4 + tools/perf/builtin-annotate.c | 4 + tools/perf/builtin-c2c.c | 9 +- tools/perf/builtin-kmem.c | 2 +- tools/perf/builtin-kvm.c | 9 +- tools/perf/builtin-list.c | 42 ++++-- tools/perf/builtin-lock.c | 5 +- tools/perf/builtin-mem.c | 5 +- tools/perf/builtin-probe.c | 5 + tools/perf/builtin-record.c | 4 + tools/perf/builtin-sched.c | 8 +- tools/perf/builtin-script.c | 7 +- tools/perf/builtin-stat.c | 4 +- tools/perf/builtin-timechart.c | 3 +- tools/perf/builtin-top.c | 4 + tools/perf/util/evsel.c | 59 ++++++-- tools/perf/util/evsel.h | 14 ++ tools/perf/util/metricgroup.c | 78 +++++++++-- tools/perf/util/metricgroup.h | 2 +- tools/perf/util/parse-events-hybrid.c | 34 +++-- tools/perf/util/parse-events-hybrid.h | 6 +- tools/perf/util/parse-events.c | 148 +++++++++++++++------ tools/perf/util/parse-events.h | 13 +- tools/perf/util/parse-events.l | 1 + tools/perf/util/parse-events.y | 10 ++ tools/perf/util/pfm.c | 3 +- tools/perf/util/pmu.c | 40 +++++- tools/perf/util/pmu.h | 4 +- tools/testing/selftests/net/reuseport_bpf.c | 2 +- 97 files changed, 1022 insertions(+), 407 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/83 ALSA: hda: Do disconnect jacks at codec unbind
From: Takashi Iwai <[email protected]>
[ Upstream commit 37c4fd0db7c961145d9d1909ecab386fdf703c26 ]
The HD-audio codec driver remove may happen also at dynamically unbinding during operation, hence it needs manual triggers of snd_device_disconnect() calls, while it's missing for the jack objects that are associated with the codec.
This patch adds the manual disconnection call for jacks when the remove happens without card->shutdown (i.e. not under the full removal).
Stable-dep-of: ead3d3c5b54f ("ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation")
--- sound/pci/hda/hda_bind.c | 2 ++ sound/pci/hda/hda_jack.c | 11 +++++++++++ sound/pci/hda/hda_jack.h | 1 + 3 files changed, 14 insertions(+)
sound/pci/hda/hda_bind.c +2 -0
@@ -14,6 +14,7 @@#include <sound/core.h> #include <sound/hda_codec.h> #include "hda_local.h" +#include "hda_jack.h" /* * find a matching codec id
@@ -158,6 +159,7 @@ static int hda_codec_driver_remove(struct device *dev)refcount_dec (&codec->pcm_ref);snd_hda_codec_disconnect_pcms (codec); +snd_hda_jack_tbl_disconnect (codec);wait_event (codec->remove_sleep, !refcount_read (&codec->pcm_ref));snd_power_sync_ref (codec->bus->card);
sound/pci/hda/hda_jack.c +11 -0
@@ -158,6 +158,17 @@ snd_hda_jack_tbl_new(struct hda_codec *codec, hda_nid_t nid, int dev_id)return jack; } +void snd_hda_jack_tbl_disconnect (struct hda_codec *codec) +{ +struct hda_jack_tbl *jack = codec->jacktbl.list; +int i; + +for (i =0 ; i < codec->jacktbl.used; i++, jack++) { +if (!codec->bus->shutdown && jack->jack) +snd_device_disconnect (codec->card, jack->jack); + } +} +void snd_hda_jack_tbl_clear (struct hda_codec *codec) {struct hda_jack_tbl *jack = codec->jacktbl.list;
sound/pci/hda/hda_jack.h +1 -0
@@ -69,6 +69,7 @@ struct hda_jack_tbl * snd_hda_jack_tbl_get_from_tag(struct hda_codec *codec, unsigned char tag, int dev_id); +void snd_hda_jack_tbl_disconnect (struct hda_codec *codec);void snd_hda_jack_tbl_clear (struct hda_codec *codec);void snd_hda_jack_set_dirty_all (struct hda_codec *codec);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 2/83 ALSA: hda: Fix hang at HD-audio codec unbinding due to refcount saturation
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
[ Upstream commit ead3d3c5b54f76da79c079e61bacb4279ec56965 ]
We fixed the potential deadlock at dynamic unbinding the HD-audio codec at the commit 7206998f578d ("ALSA: hda: Fix potential deadlock at codec unbinding"), but ironically, this caused another potential deadlock. The current code uses refcount_dec() and waits for the pending task with wait_event for dropping the refcount to 0. This works fine when PCMs are assigned and actually waiting for the refcount drop.
Meanwhile, when there was no PCM assigned, the refcount_dec() call itself was supposed to drop to zero -- alas, it doesn't in reality; refcount_dec() complains, spews kernel warning and it saturates instead of dropping to 0, due to the nature of refcount_dec() implementation. This eventually blocks the wait_event() wakeup and the code get stuck there.
For avoiding the problem, we call refcount_dec_and_test() and skips the sync-wait if it already reaches to zero.
The patch does a slight code reshuffling to make sure to invoke other disconnect calls before the sync-wait, too.
--- sound/pci/hda/hda_bind.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/pci/hda/hda_bind.c +2 -2
@@ -157,10 +157,10 @@ static int hda_codec_driver_remove(struct device *dev)return codec->bus->core.ext_ops->hdev_detach (&codec->core); } -refcount_dec (&codec->pcm_ref);snd_hda_codec_disconnect_pcms (codec);snd_hda_jack_tbl_disconnect (codec); -wait_event (codec->remove_sleep, !refcount_read (&codec->pcm_ref)); +if (!refcount_dec_and_test (&codec->pcm_ref)) +wait_event (codec->remove_sleep, !refcount_read (&codec->pcm_ref));snd_power_sync_ref (codec->bus->card);if (codec->patch_ops.free)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 3/83 ALSA: hda: Fix Nvidia dp infoframe
In reply to Greg Kroah-HartmanFrom: Mohan Kumar <[email protected]>
[ Upstream commit f89e409402e2aeb3bc3aa44d2b7a597959e4e6af ]
Nvidia HDA HW expects infoframe data bytes order same for both HDMI and DP i.e infoframe data starts from 5th bytes offset. As dp infoframe structure has 4th byte as valid infoframe data, use hdmi infoframe structure for nvidia dp infoframe to match HW behvaior.
--- sound/pci/hda/patch_hdmi.c | 23 +++++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-)
sound/pci/hda/patch_hdmi.c +19 -4
@@ -162,6 +162,8 @@ struct hdmi_spec {bool dyn_pin_out;bool dyn_pcm_assign;bool dyn_pcm_no_legacy; +bool nv_dp_workaround;/* workaround DP audio infoframe for Nvidia */ +bool intel_hsw_fixup;/* apply Intel platform-specific fixups */ /* * Non-generic VIA/NVIDIA specific
@@ -671,15 +673,24 @@ static void hdmi_pin_setup_infoframe(struct hda_codec *codec, int ca, int active_channels, int conn_type) { + struct hdmi_spec *spec = codec->spec;union audio_infoframe ai;memset (&ai,0 ,sizeof (ai)); -if (conn_type ==0 ) {/* HDMI */ +if ((conn_type ==0 ) ||/* HDMI */ +/* Nvidia DisplayPort: Nvidia HW expects same layout as HDMI */ + (conn_type ==1 && spec->nv_dp_workaround)) {struct hdmi_audio_infoframe *hdmi_ai = &ai.hdmi; - hdmi_ai->type =0x84 ; - hdmi_ai->ver =0x01 ; - hdmi_ai->len =0x0a ; +if (conn_type ==0 ) {/* HDMI */ + hdmi_ai->type =0x84 ; + hdmi_ai->ver =0x01 ; + hdmi_ai->len =0x0a ; + }else {/* Nvidia DP */ + hdmi_ai->type =0x84 ; + hdmi_ai->ver =0x1b ; + hdmi_ai->len =0x11 <<2 ; + } hdmi_ai->CC02_CT47 = active_channels -1 ; hdmi_ai->CA = ca;hdmi_checksum_audio_infoframe (hdmi_ai);
@@ -3539,6 +3550,7 @@ static int patch_nvhdmi_2ch(struct hda_codec *codec) spec->pcm_playback.rates =SUPPORTED_RATES ; spec->pcm_playback.maxbps =SUPPORTED_MAXBPS ; spec->pcm_playback.formats =SUPPORTED_FORMATS ; + spec->nv_dp_workaround = true;return 0 ; }
@@ -3678,6 +3690,7 @@ static int patch_nvhdmi(struct hda_codec *codec) spec->chmap.ops.chmap_cea_alloc_validate_get_type = nvhdmi_chmap_cea_alloc_validate_get_type; spec->chmap.ops.chmap_validate = nvhdmi_chmap_validate; + spec->nv_dp_workaround = true; codec->link_down_at_suspend =1 ;
@@ -3701,6 +3714,7 @@ static int patch_nvhdmi_legacy(struct hda_codec *codec) spec->chmap.ops.chmap_cea_alloc_validate_get_type = nvhdmi_chmap_cea_alloc_validate_get_type; spec->chmap.ops.chmap_validate = nvhdmi_chmap_validate; + spec->nv_dp_workaround = true; codec->link_down_at_suspend =1 ;
@@ -3874,6 +3888,7 @@ static int patch_tegra_hdmi(struct hda_codec *codec) spec->chmap.ops.chmap_cea_alloc_validate_get_type = nvhdmi_chmap_cea_alloc_validate_get_type; spec->chmap.ops.chmap_validate = nvhdmi_chmap_validate; + spec->nv_dp_workaround = true;return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 4/83 ALSA: hda/realtek: fix speakers and micmute on HP 855 G8
In reply to Greg Kroah-HartmanFrom: Alexander Sergeyev <[email protected]>
[ Upstream commit 91502a9a0b0d5252cf3f32ebd898823c2f5aadab ]
There are several PCI ids associated with HP EliteBook 855 G8 Notebook PC. Commit 0e68c4b11f1e6 ("ALSA: hda/realtek: fix mute/micmute LEDs for HP 855 G8") covers 0x103c:0x8896, while this commit covers 0x103c:0x8895 which needs some additional work on top of the quirk from 0e68c4b11f1e6.
Note that the device can boot up with working speakers and micmute LED without this patch, but the success rate would be quite low (order of 16 working boots across 709 boots) at least for the built-in drivers scenario. This also means that there are some timing issues during early boot and this patch is a workaround.
With this patch applied speakers and headphones are consistenly working, as well as mute/micmute LEDs and the internal microphone.
Stable-dep-of: 496322302bf1 ("ALSA: hda/realtek: Add a quirk for HP OMEN 16 (8902) mute LED")
--- sound/pci/hda/patch_realtek.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
sound/pci/hda/patch_realtek.c +12 -0
@@ -6939,6 +6939,7 @@ enum {ALC256_FIXUP_MIC_NO_PRESENCE_AND_RESUME ,ALC285_FIXUP_LEGION_Y9000X_SPEAKERS ,ALC285_FIXUP_LEGION_Y9000X_AUTOMUTE , + ALC285_FIXUP_HP_SPEAKERS_MICMUTE_LED, };/* A special fixup for Lenovo C940 and Yoga Duet 7;
@@ -8753,6 +8754,16 @@ static const struct hda_fixup alc269_fixups[] = { .chained = true, .chain_id =ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC }, + [ALC285_FIXUP_HP_SPEAKERS_MICMUTE_LED] = { + .type = HDA_FIXUP_VERBS, + .v.verbs = (const struct hda_verb []) { + {0x20 ,AC_VERB_SET_COEF_INDEX ,0x19 }, + {0x20 ,AC_VERB_SET_PROC_COEF ,0x8e11 }, + { } + }, + .chained = true, + .chain_id = ALC285_FIXUP_HP_MUTE_LED, + }, };static const struct snd_pci_quirk alc269_fixup_tbl[] = {
@@ -8976,6 +8987,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {SND_PCI_QUIRK (0x103c ,0x8870 ,"HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC" ,ALC285_FIXUP_HP_GPIO_AMP_INIT ),SND_PCI_QUIRK (0x103c ,0x8873 ,"HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC" ,ALC285_FIXUP_HP_GPIO_AMP_INIT ),SND_PCI_QUIRK (0x103c ,0x888d ,"HP ZBook Power 15.6 inch G8 Mobile Workstation PC" ,ALC236_FIXUP_HP_GPIO_LED ), +SND_PCI_QUIRK (0x103c ,0x8895 ,"HP EliteBook 855 G8 Notebook PC" ,ALC285_FIXUP_HP_SPEAKERS_MICMUTE_LED ),SND_PCI_QUIRK (0x103c ,0x8896 ,"HP EliteBook 855 G8 Notebook PC" ,ALC285_FIXUP_HP_MUTE_LED ),SND_PCI_QUIRK (0x103c ,0x8898 ,"HP EliteBook 845 G8 Notebook PC" ,ALC285_FIXUP_HP_LIMIT_INT_MIC_BOOST ), SND_PCI_QUIRK(0x103c, 0x88d0, "HP Pavilion 15-eh1xxx (mainboard 88D0)", ALC287_FIXUP_HP_GPIO_LED),
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 5/83 cgroup: reduce dependency on cgroup_mutex
In reply to Greg Kroah-HartmanFrom: Shakeel Butt <[email protected]>
[ Upstream commit be288169712f3dea0bc6b50c00b3ab53d85f1435 ]
Currently cgroup_get_from_path() and cgroup_get_from_id() grab cgroup_mutex before traversing the default hierarchy to find the kernfs_node corresponding to the path/id and then extract the linked cgroup. Since cgroup_mutex is still held, it is guaranteed that the cgroup will be alive and the reference can be taken on it.
However similar guarantee can be provided without depending on the cgroup_mutex and potentially reducing avenues of cgroup_mutex contentions. The kernfs_node's priv pointer is RCU protected pointer and with just rcu read lock we can grab the reference on the cgroup without cgroup_mutex. So, remove cgroup_mutex from them.
Stable-dep-of: df02452f3df0 ("cgroup: cgroup_get_from_id() must check the looked-up kn is a directory")
--- kernel/cgroup/cgroup.c | 51 ++++++++++++++++++++++++------------------ 1 file changed, 29 insertions(+), 22 deletions(-)
kernel/cgroup/cgroup.c +29 -22
@@ -6021,17 +6021,20 @@ struct cgroup *cgroup_get_from_id(u64 id)struct kernfs_node *kn;struct cgroup *cgrp =NULL ; -mutex_lock (&cgroup_mutex); kn =kernfs_find_and_get_node_by_id (cgrp_dfl_root.kf_root, id);if (!kn) - goto out_unlock; + goto out; + +rcu_read_lock (); - cgrp = kn->priv; -if (cgroup_is_dead (cgrp) || !cgroup_tryget (cgrp)) + cgrp =rcu_dereference (*(void __rcu __force **)&kn->priv); +if (cgrp && !cgroup_tryget (cgrp)) cgrp =NULL ; + +rcu_read_unlock (); +kernfs_put (kn); -out_unlock: -mutex_unlock (&cgroup_mutex); +out:return cgrp; }EXPORT_SYMBOL_GPL (cgroup_get_from_id);
@@ -6585,30 +6588,34 @@ struct cgroup_subsys_state *css_from_id(int id, struct cgroup_subsys *ss)* * Find the cgroup at @path on the default hierarchy, increment its * reference count and return it. Returns pointer to the found cgroup on -* success, ERR_PTR(-ENOENT) if @path doesn't exist and ERR_PTR(-ENOTDIR) -* if @path points to a non-directory. +* success, ERR_PTR(-ENOENT) if @path doesn't exist or if the cgroup has already +* been released and ERR_PTR(-ENOTDIR) if @path points to a non-directory. */ struct cgroup *cgroup_get_from_path (const char *path) {struct kernfs_node *kn; -struct cgroup *cgrp; - -mutex_lock (&cgroup_mutex); +struct cgroup *cgrp =ERR_PTR (-ENOENT ); kn =kernfs_walk_and_get (cgrp_dfl_root.cgrp.kn, path); -if (kn) { -if (kernfs_type (kn) ==KERNFS_DIR ) { - cgrp = kn->priv; -cgroup_get_live (cgrp); - }else { - cgrp =ERR_PTR (-ENOTDIR ); - } -kernfs_put (kn); - }else { - cgrp =ERR_PTR (-ENOENT ); +if (!kn) + goto out; + +if (kernfs_type (kn) !=KERNFS_DIR ) { + cgrp =ERR_PTR (-ENOTDIR ); + goto out_kernfs; } -mutex_unlock (&cgroup_mutex); +rcu_read_lock (); + + cgrp =rcu_dereference (*(void __rcu __force **)&kn->priv); +if (!cgrp || !cgroup_tryget (cgrp)) + cgrp =ERR_PTR (-ENOENT ); + +rcu_read_unlock (); + +out_kernfs: +kernfs_put (kn); +out:return cgrp; }EXPORT_SYMBOL_GPL (cgroup_get_from_path);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 6/83 cgroup: cgroup_get_from_id() must check the looked-up kn is a directory
In reply to Greg Kroah-HartmanFrom: Ming Lei <[email protected]>
[ Upstream commit df02452f3df069a59bc9e69c84435bf115cb6e37 ]
cgroup has to be one kernfs dir, otherwise kernel panic is caused, especially cgroup id is provide from userspace.
--- kernel/cgroup/cgroup.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
kernel/cgroup/cgroup.c +4 -1
@@ -6025,6 +6025,9 @@ struct cgroup *cgroup_get_from_id(u64 id)if (!kn) goto out; +if (kernfs_type (kn) !=KERNFS_DIR ) + goto put; +rcu_read_lock (); cgrp =rcu_dereference (*(void __rcu __force **)&kn->priv);
@@ -6032,7 +6035,7 @@ struct cgroup *cgroup_get_from_id(u64 id) cgrp =NULL ;rcu_read_unlock (); - +put:kernfs_put (kn); out:return cgrp;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 7/83 uas: add no-uas quirk for Hiksemi usb_disk
In reply to Greg Kroah-HartmanFrom: Hongling Zeng <[email protected]>
commit a625a4b8806cc1e928b7dd2cca1fee709c9de56e upstream.
The UAS mode of Hiksemi is reported to fail to work on several platforms with the following error message, then after re-connecting the device will be offlined and not working at all.
[ 592.518442][ 2] sd 8:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 18
inflight: CMD
[ 592.527575][ 2] sd 8:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 03 6f 88 00 00
04 00 00
[ 592.536330][ 2] sd 8:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1
inflight: CMD
[ 592.545266][ 2] sd 8:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 07 44 1a 88 00
00 08 00These disks have a broken uas implementation, the tag field of the status iu-s is not set properly,so we need to fall-back to usb-storage.
--- drivers/usb/storage/unusual_uas.h | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/usb/storage/unusual_uas.h +7 -0
@@ -52,6 +52,13 @@ UNUSUAL_DEV(0x059f, 0x1061, 0x0000, 0x99 USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_NO_REPORT_OPCODES | US_FL_NO_SAME), +/* Reported-by: Hongling Zeng <[email protected]> */ +UNUSUAL_DEV (0x090c ,0x2000 ,0x0000 ,0x9999 , +"Hiksemi" , +"External HDD" , +USB_SC_DEVICE ,USB_PR_DEVICE ,NULL , + US_FL_IGNORE_UAS), +/* * Apricorn USB3 dongle sometimes returns "USBSUSBSUSBS" in response to SCSI * commands in UAS mode. Observed with the 1.28 firmware; are there others?
Greg Kroah-Hartman
maintainerPATCH 8/83 usb-storage: Add Hiksemi USB3-FW to IGNORE_UAS
In reply to Greg Kroah-HartmanFrom: Hongling Zeng <[email protected]>
commit e00b488e813f0f1ad9f778e771b7cd2fe2877023 upstream.
The UAS mode of Hiksemi USB_HDD is reported to fail to work on several platforms with the following error message, then after re-connecting the device will be offlined and not working at all.
[ 592.518442][ 2] sd 8:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 18
inflight: CMD
[ 592.527575][ 2] sd 8:0:0:0: [sda] tag#17 CDB: Write(10) 2a 00 03 6f 88 00 00
04 00 00
[ 592.536330][ 2] sd 8:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1
inflight: CMD
[ 592.545266][ 2] sd 8:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 07 44 1a 88 00
00 08 00These disks have a broken uas implementation, the tag field of the status iu-s is not set properly,so we need to fall-back to usb-storage.
--- drivers/usb/storage/unusual_uas.h | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/usb/storage/unusual_uas.h +7 -0
@@ -83,6 +83,13 @@ UNUSUAL_DEV(0x0bc2, 0x331a, 0x0000, 0x99 USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_NO_REPORT_LUNS), +/* Reported-by: Hongling Zeng <[email protected]> */ +UNUSUAL_DEV (0x0bda ,0x9210 ,0x0000 ,0x9999 , +"Hiksemi" , +"External HDD" , +USB_SC_DEVICE ,USB_PR_DEVICE ,NULL , +US_FL_IGNORE_UAS ), +/* Reported-by: Benjamin Tissoires <[email protected]> */ UNUSUAL_DEV(0x13fd, 0x3940, 0x0000, 0x9999, "Initio Corporation",
Greg Kroah-Hartman
maintainerPATCH 9/83 uas: ignore UAS for Thinkplus chips
In reply to Greg Kroah-HartmanFrom: Hongling Zeng <[email protected]>
commit 0fb9703a3eade0bb84c635705d9c795345e55053 upstream.
The UAS mode of Thinkplus(0x17ef, 0x3899) is reported to influence performance and trigger kernel panic on several platforms with the following error message:
[ 39.702439] xhci_hcd 0000:0c:00.3: ERROR Transfer event for disabled
endpoint or incorrect stream ring
[ 39.702442] xhci_hcd 0000:0c:00.3: @000000026c61f810 00000000 00000000
1b000000 05038000[ 720.545894][13] Workqueue: usb_hub_wq hub_event
[ 720.550971][13] ffff88026c143c38 0000000000016300 ffff8802755bb900 ffff880
26cb80000
[ 720.559673][13] ffff88026c144000 ffff88026ca88100 0000000000000000 ffff880
26cb80000
[ 720.568374][13] ffff88026cb80000 ffff88026c143c50 ffffffff8186ae25 ffff880
26ca880f8
[ 720.577076][13] Call Trace:
[ 720.580201][13] [<ffffffff8186ae25>] schedule+0x35/0x80
[ 720.586137][13] [<ffffffff8186b0ce>] schedule_preempt_disabled+0xe/0x10
[ 720.593623][13] [<ffffffff8186cb94>] __mutex_lock_slowpath+0x164/0x1e0
[ 720.601012][13] [<ffffffff8186cc3f>] mutex_lock+0x2f/0x40
[ 720.607141][13] [<ffffffff8162b8e9>] usb_disconnect+0x59/0x290Falling back to USB mass storage can solve this problem, so ignore UAS function of this chip.
--- drivers/usb/storage/unusual_uas.h | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/usb/storage/unusual_uas.h +7 -0
@@ -132,6 +132,13 @@ UNUSUAL_DEV(0x154b, 0xf00d, 0x0000, 0x99 USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_NO_ATA_1X), +/* Reported-by: Hongling Zeng <[email protected]> */ +UNUSUAL_DEV (0x17ef ,0x3899 ,0x0000 ,0x9999 , +"Thinkplus" , +"External HDD" , +USB_SC_DEVICE ,USB_PR_DEVICE ,NULL , +US_FL_IGNORE_UAS ), +/* Reported-by: Hans de Goede <[email protected]> */ UNUSUAL_DEV(0x2109, 0x0711, 0x0000, 0x9999, "VIA",
Greg Kroah-Hartman
maintainerPATCH 10/83 usb: typec: ucsi: Remove incorrect warning
In reply to Greg Kroah-HartmanFrom: Heikki Krogerus <[email protected]>
commit 415ba26cb73f7d22a892043301b91b57ae54db02 upstream.
Sink only devices do not have any source capabilities, so the driver should not warn about that. Also DRP (Dual Role Power) capable devices, such as USB Type-C docking stations, do not return any source capabilities unless they are plugged to a power supply themselves.
--- drivers/usb/typec/ucsi/ucsi.c | 2 -- 1 file changed, 2 deletions(-)
drivers/usb/typec/ucsi/ucsi.c +0 -2
@@ -515,8 +515,6 @@ static int ucsi_get_pdos(struct ucsi_con num_pdos * sizeof(u32));if (ret <0 )dev_err (ucsi->dev,"UCSI_GET_PDOS failed (%d)\n" , ret); -if (ret ==0 && offset ==0 ) -dev_warn (ucsi->dev,"UCSI_GET_PDOS returned 0 bytes\n" );return ret; }
Greg Kroah-Hartman
maintainerPATCH 11/83 thunderbolt: Explicitly reset plug events delay back to USB4 spec value
In reply to Greg Kroah-HartmanFrom: Mario Limonciello <[email protected]>
commit 31f87f705b3c1635345d8e8a493697099b43e508 upstream.
If any software has interacted with the USB4 registers before the Linux USB4 CM runs, it may have modified the plug events delay. It has been observed that if this value too large, it's possible that hotplugged devices will negotiate a fallback mode instead in Linux.
To prevent this, explicitly align the plug events delay with the USB4 spec value of 10ms.
--- drivers/thunderbolt/switch.c | 1 + 1 file changed, 1 insertion(+)
drivers/thunderbolt/switch.c +1 -0
@@ -2281,6 +2281,7 @@ int tb_switch_configure(struct tb_switch* additional capabilities. */ sw->config.cmuv =USB4_VERSION_1_0 ; + sw->config.plug_events_delay =0xa ;/* Enumerate the switch */ ret = tb_sw_write(sw, (u32 *)&sw->config + 1, TB_CFG_SWITCH,
Greg Kroah-Hartman
maintainerPATCH 12/83 net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
In reply to Greg Kroah-HartmanFrom: Frank Wunderlich <[email protected]>
commit 797666cd5af041ffb66642fff62f7389f08566a2 upstream.
Add support for Dell 5811e (EM7455) with USB-id 0x413c:0x81c2.
--- drivers/net/usb/qmi_wwan.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/usb/qmi_wwan.c +1 -0
@@ -1393,6 +1393,7 @@ static const struct usb_device_id produc {QMI_FIXED_INTF(0x413c, 0x81b3, 8)}, /* Dell Wireless 5809e Gobi(TM) 4G LTE Mobile Broadband Card (rev3) */ {QMI_FIXED_INTF(0x413c, 0x81b6, 8)}, /* Dell Wireless 5811e */ {QMI_FIXED_INTF(0x413c, 0x81b6, 10)}, /* Dell Wireless 5811e */ + {QMI_FIXED_INTF(0x413c, 0x81c2, 8)}, /* Dell Wireless 5811e */ {QMI_FIXED_INTF(0x413c, 0x81cc, 8)}, /* Dell Wireless 5816e */ {QMI_FIXED_INTF(0x413c, 0x81d7, 0)}, /* Dell Wireless 5821e */ {QMI_FIXED_INTF(0x413c, 0x81d7, 1)}, /* Dell Wireless 5821e preproduction config */
Greg Kroah-Hartman
maintainerPATCH 13/83 Input: snvs_pwrkey - fix SNVS_HPVIDR1 register address
In reply to Greg Kroah-HartmanFrom: Sebastian Krzyszkowiak <[email protected]>
commit e62563db857f81d75c5726a35bc0180bed6d1540 upstream.
Both i.MX6 and i.MX8 reference manuals list 0xBF8 as SNVS_HPVIDR1 (chapters 57.9 and 6.4.5 respectively).
Without this, trying to read the revision number results in 0 on all revisions, causing the i.MX6 quirk to apply on all platforms, which in turn causes the driver to synthesise power button release events instead of passing the real one as they happen even on platforms like i.MX8 where that's not wanted.
--- drivers/input/keyboard/snvs_pwrkey.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/input/keyboard/snvs_pwrkey.c +1 -1
@@ -20,7 +20,7 @@#include <linux/mfd/syscon.h> #include <linux/regmap.h> -#define SNVS_HPVIDR1_REG 0xF8 +#define SNVS_HPVIDR1_REG 0xBF8#define SNVS_LPSR_REG 0x4C/* LP Status Register */ #define SNVS_LPCR_REG 0x38/* LP Control Register */ #define SNVS_HPSR_REG 0x14
Greg Kroah-Hartman
maintainerPATCH 14/83 can: c_can: dont cache TX messages for C_CAN cores
In reply to Greg Kroah-HartmanFrom: Marc Kleine-Budde <[email protected]>
commit 81d192c2ce74157e717e1fc4b68791f82f7499d4 upstream.
As Jacob noticed, the optimization introduced in 387da6bc7a82 ("can:c_can: cache frames to operate as a true FIFO") doesn't properly work on C_CAN, but on D_CAN IP cores. The exact reasons are still unknown.
For now disable caching if CAN frames in the TX path for C_CAN cores.
--- drivers/net/can/c_can/c_can.h | 17 +++++++++++++++-- drivers/net/can/c_can/c_can_main.c | 11 +++++------ 2 files changed, 20 insertions(+), 8 deletions(-)
drivers/net/can/c_can/c_can.h +15 -2
@@ -236,9 +236,22 @@ static inline u8 c_can_get_tx_tail(const return ring->tail & (ring->obj_num - 1); } -static inline u8 c_can_get_tx_free (const struct c_can_tx_ring *ring) +static inline u8 c_can_get_tx_free (const struct c_can_priv *priv, +const struct c_can_tx_ring *ring) { -return ring->obj_num - (ring->head - ring->tail); +u8 head =c_can_get_tx_head (ring); +u8 tail =c_can_get_tx_tail (ring); + +if (priv->type ==BOSCH_D_CAN ) +return ring->obj_num - (ring->head - ring->tail); + +/* This is not a FIFO. C/D_CAN sends out the buffers +* prioritized. The lowest buffer number wins. +*/ +if (head < tail) +return 0 ; + +return ring->obj_num - head; }#endif /* C_CAN_H */
drivers/net/can/c_can/c_can_main.c +5 -6
@@ -430,7 +430,7 @@ static void c_can_setup_receive_object(sstatic bool c_can_tx_busy (const struct c_can_priv *priv,const struct c_can_tx_ring *tx_ring) { -if (c_can_get_tx_free (tx_ring) >0 ) +if (c_can_get_tx_free (priv, tx_ring) >0 )return false;netif_stop_queue (priv->dev);
@@ -438,7 +438,7 @@ static bool c_can_tx_busy(const struct c/* Memory barrier before checking tx_free (head and tail) */ smp_mb (); -if (c_can_get_tx_free (tx_ring) ==0 ) { +if (c_can_get_tx_free (priv, tx_ring) ==0 ) { netdev_dbg(priv->dev, "Stopping tx-queue (tx_head=0x%08x, tx_tail=0x%08x, len=%d).\n", tx_ring->head, tx_ring->tail,
@@ -466,7 +466,7 @@ static netdev_tx_t c_can_start_xmit(stru idx =c_can_get_tx_head (tx_ring); tx_ring->head++; -if (c_can_get_tx_free (tx_ring) ==0 ) +if (c_can_get_tx_free (priv, tx_ring) ==0 )netif_stop_queue (dev);if (idx <c_can_get_tx_tail (tx_ring))
@@ -751,7 +751,7 @@ static void c_can_do_tx(struct net_devicreturn ; tx_ring->tail += pkts; -if (c_can_get_tx_free (tx_ring)) { +if (c_can_get_tx_free (priv, tx_ring)) {/* Make sure that anybody stopping the queue after * this sees the new tx_ring->tail. */
@@ -764,8 +764,7 @@ static void c_can_do_tx(struct net_deviccan_led_event (dev,CAN_LED_EVENT_TX ); tail =c_can_get_tx_tail (tx_ring); - -if (tail ==0 ) { +if (priv->type ==BOSCH_D_CAN && tail ==0 ) {u8 head =c_can_get_tx_head (tx_ring);/* Start transmission for all cached messages */
Greg Kroah-Hartman
maintainerPATCH 15/83 clk: ingenic-tcu: Properly enable registers before accessing timers
In reply to Greg Kroah-HartmanFrom: Aidan MacDonald <[email protected]>
commit 6726d552a6912e88cf63fe2bda87b2efa0efc7d0 upstream.
Access to registers is guarded by ingenic_tcu_{enable,disable}_regs() so the stop bit can be cleared before accessing a timer channel, but those functions did not clear the stop bit on SoCs with a global TCU clock gate.
Testing on the X1000 has revealed that the stop bits must be cleared _and_ the global TCU clock must be ungated to access timer registers. This appears to be the norm on Ingenic SoCs, and is specified in the documentation for the X1000 and numerous JZ47xx SoCs.
If the stop bit isn't cleared, register writes don't take effect and the system can be left in a broken state, eg. the watchdog timer may not run.
The bug probably went unnoticed because stop bits are zeroed when the SoC is reset, and the kernel does not set them unless a timer gets disabled at runtime. However, it is possible that a bootloader or a previous kernel (if using kexec) leaves the stop bits set and we should not rely on them being cleared.
Fixing this is easy: have ingenic_tcu_{enable,disable}_regs() always clear the stop bit, regardless of the presence of a global TCU gate.
--- drivers/clk/ingenic/tcu.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-)
drivers/clk/ingenic/tcu.c +5 -10
@@ -100,15 +100,11 @@ static bool ingenic_tcu_enable_regs(strubool enabled = false;/* -* If the SoC has no global TCU clock, we must ungate the channel's -* clock to be able to access its registers. -* If we have a TCU clock, it will be enabled automatically as it has -* been attached to the regmap. +* According to the programming manual, a timer channel's registers can +* only be accessed when the channel's stop bit is clear. */ -if (!tcu->clk) { - enabled = !!ingenic_tcu_is_enabled (hw); -regmap_write (tcu->map,TCU_REG_TSCR ,BIT (info->gate_bit)); - } + enabled = !!ingenic_tcu_is_enabled (hw); +regmap_write (tcu->map,TCU_REG_TSCR ,BIT (info->gate_bit));return enabled; }
@@ -119,8 +115,7 @@ static void ingenic_tcu_disable_regs(strconst struct ingenic_tcu_clk_info *info = tcu_clk->info;struct ingenic_tcu *tcu = tcu_clk->tcu; -if (!tcu->clk) -regmap_write (tcu->map,TCU_REG_TSSR ,BIT (info->gate_bit)); +regmap_write (tcu->map,TCU_REG_TSSR ,BIT (info->gate_bit)); }static u8 ingenic_tcu_get_parent (struct clk_hw *hw)
Greg Kroah-Hartman
maintainerPATCH 16/83 x86/sgx: Do not fail on incomplete sanitization on premature stop of ksgxd
In reply to Greg Kroah-HartmanFrom: Jarkko Sakkinen <[email protected]>
commit 133e049a3f8c91b175029fb6a59b6039d5e79cba upstream.
Unsanitized pages trigger WARN_ON() unconditionally, which can panic the whole computer, if /proc/sys/kernel/panic_on_warn is set.
In sgx_init(), if misc_register() fails or misc_register() succeeds but neither sgx_drv_init() nor sgx_vepc_init() succeeds, then ksgxd will be prematurely stopped. This may leave unsanitized pages, which will result a false warning.
Refine __sgx_sanitize_pages() to return:
1. Zero when the sanitization process is complete or ksgxd has been requested to stop.
2. The number of unsanitized pages otherwise.
--- arch/x86/kernel/cpu/sgx/main.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)
arch/x86/kernel/cpu/sgx/main.c +9 -6
@@ -46,9 +46,13 @@ static LIST_HEAD(sgx_dirty_page_list);* Reset post-kexec EPC pages to the uninitialized state. The pages are removed * from the input list, and made available for the page allocator. SECS pages * prepending their children in the input list are left intact. +* +* Return 0 when sanitization was successful or kthread was stopped, and the +* number of unsanitized pages otherwise. */ -static void __sgx_sanitize_pages (struct list_head *dirty_page_list) +static unsigned long __sgx_sanitize_pages (struct list_head *dirty_page_list) { +unsigned long left_dirty =0 ;struct sgx_epc_page *page;LIST_HEAD (dirty);int ret;
@@ -56,7 +60,7 @@ static void __sgx_sanitize_pages(struct/* dirty_page_list is thread-local, no need for a lock: */ while (!list_empty (dirty_page_list)) {if (kthread_should_stop ()) -return ; +return 0 ; page = list_first_entry(dirty_page_list, struct sgx_epc_page, list);
@@ -71,12 +75,14 @@ static void __sgx_sanitize_pages(struct }else {/* The page is not yet clean - move to the dirty list. */ list_move_tail (&page->list, &dirty); + left_dirty++; }cond_resched (); }list_splice (&dirty, dirty_page_list); +return left_dirty; }static bool sgx_reclaimer_age (struct sgx_epc_page *epc_page)
@@ -427,10 +433,7 @@ static int ksgxd(void *p)* required for SECS pages, whose child pages blocked EREMOVE. */ __sgx_sanitize_pages (&sgx_dirty_page_list); -__sgx_sanitize_pages (&sgx_dirty_page_list); - -/* sanity check: */ -WARN_ON (!list_empty (&sgx_dirty_page_list)); +WARN_ON (__sgx_sanitize_pages (&sgx_dirty_page_list));while (!kthread_should_stop ()) {if (try_to_freeze ())
Greg Kroah-Hartman
maintainerPATCH 17/83 ARM: dts: integrator: Tag PCI host with device_type
In reply to Greg Kroah-HartmanFrom: Linus Walleij <[email protected]>
commit 4952aa696a9f221c5e34e5961e02fca41ef67ad6 upstream.
The DT parser is dependent on the PCI device being tagged as device_type = "pci" in order to parse memory ranges properly. Fix this up.
--- arch/arm/boot/dts/integratorap.dts | 1 + 1 file changed, 1 insertion(+)
arch/arm/boot/dts/integratorap.dts +1 -0
@@ -153,6 +153,7 @@ pci: pciv3@62000000 { compatible = "arm,integrator-ap-pci", "v3,v360epc-pci"; + device_type = "pci"; #interrupt-cells = <1>; #size-cells = <2>; #address-cells = <3>;
Greg Kroah-Hartman
maintainerPATCH 18/83 ntfs: fix BUG_ON in ntfs_lookup_inode_by_name()
In reply to Greg Kroah-HartmanFrom: ChenXiaoSong <[email protected]>
commit 1b513f613731e2afc05550e8070d79fac80c661e upstream.
Syzkaller reported BUG_ON as follows:
------------[ cut here ]------------ kernel BUG at fs/ntfs/dir.c:86! invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 3 PID: 758 Comm: a.out Not tainted 5.19.0-next-20220808 #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:ntfs_lookup_inode_by_name+0xd11/0x2d10 Code: ff e9 b9 01 00 00 e8 1e fe d6 fe 48 8b 7d 98 49 8d 5d 07 e8 91 85 29 ff 48 c7 45 98 00 00 00 00 e9 5a fb ff ff e8 ff fd d6 fe <0f> 0b e8 f8 fd d6 fe 0f 0b e8 f1 fd d6 fe 48 8b b5 50 ff ff ff 4c RSP: 0018:ffff888079607978 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000000 RDX: ffff88807cf10000 RSI: ffffffff82a4a081 RDI: 0000000000000003 RBP: ffff888079607a70 R08: 0000000000000001 R09: ffff88807a6d01d7 R10: ffffed100f4da03a R11: 0000000000000000 R12: ffff88800f0fb110 R13: ffff88800f0ee000 R14: ffff88800f0fb000 R15: 0000000000000001 FS: 00007f33b63c7540(0000) GS:ffff888108580000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f33b635c090 CR3: 000000000f39e005 CR4: 0000000000770ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> load_system_files+0x1f7f/0x3620 ntfs_fill_super+0xa01/0x1be0 mount_bdev+0x36a/0x440 ntfs_mount+0x3a/0x50 legacy_get_tree+0xfb/0x210 vfs_get_tree+0x8f/0x2f0 do_new_mount+0x30a/0x760 path_mount+0x4de/0x1880 __x64_sys_mount+0x2b3/0x340 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f33b62ff9ea Code: 48 8b 0d a9 f4 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 76 f4 0b 00 f7 d8 64 89 01 48 RSP: 002b:00007ffd0c471aa8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f33b62ff9ea RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd0c471be0 RBP: 00007ffd0c471c60 R08: 00007ffd0c471ae0 R09: 00007ffd0c471c24 R10: 0000000000000000 R11: 0000000000000202 R12: 000055bac5afc160 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]---
Fix this by adding sanity check on extended system files' directory inode to ensure that it is directory, just like ntfs_extend_init() when mounting ntfs3.
--- fs/ntfs/super.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/ntfs/super.c +2 -1
@@ -2092,7 +2092,8 @@ get_ctx_vol_failed:// TODO: Initialize security. /* Get the extended system files' directory inode. */ vol->extend_ino =ntfs_iget (sb, FILE_Extend); -if (IS_ERR (vol->extend_ino) ||is_bad_inode (vol->extend_ino)) { +if (IS_ERR (vol->extend_ino) ||is_bad_inode (vol->extend_ino) || + !S_ISDIR (vol->extend_ino->i_mode)) {if (!IS_ERR (vol->extend_ino))iput (vol->extend_ino);ntfs_error (sb,"Failed to load $Extend." );
Greg Kroah-Hartman
maintainerPATCH 19/83 mm/damon/dbgfs: fix memory leak when using debugfs_lookup()
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
commit 1552fd3ef7dbe07208b8ae84a0a6566adf7dfc9d upstream.
When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. Fix this up by properly calling dput().
--- mm/damon/dbgfs.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
mm/damon/dbgfs.c +14 -5
@@ -443,6 +443,7 @@ static int dbgfs_rm_context(char *name)struct dentry *root, *dir, **new_dirs;struct damon_ctx **new_ctxs;int i, j; +int ret =0 ;if (damon_nr_running_ctxs ())return -EBUSY ;
@@ -457,14 +458,16 @@ static int dbgfs_rm_context(char *name) new_dirs =kmalloc_array (dbgfs_nr_ctxs -1 ,sizeof (*dbgfs_dirs),GFP_KERNEL ); -if (!new_dirs) -return -ENOMEM ; +if (!new_dirs) { + ret = -ENOMEM ; + goto out_dput; + } new_ctxs =kmalloc_array (dbgfs_nr_ctxs -1 ,sizeof (*dbgfs_ctxs),GFP_KERNEL );if (!new_ctxs) { -kfree (new_dirs); -return -ENOMEM ; + ret = -ENOMEM ; + goto out_new_dirs; }for (i =0 , j =0 ; i < dbgfs_nr_ctxs; i++) {
@@ -484,7 +487,13 @@ static int dbgfs_rm_context(char *name) dbgfs_ctxs = new_ctxs; dbgfs_nr_ctxs--; -return 0 ; + goto out_dput; + +out_new_dirs: +kfree (new_dirs); +out_dput: +dput (dir); +return ret; } static ssize_t dbgfs_rm_context_write(struct file *file,
Greg Kroah-Hartman
maintainerPATCH 20/83 net: mt7531: only do PLL once after the reset
In reply to Greg Kroah-HartmanFrom: Alexander Couzens <[email protected]>
commit 42bc4fafe359ed6b73602b7a2dba0dd99588f8ce upstream.
Move the PLL init of the switch out of the pad configuration of the port 6 (usally cpu port).
Fix a unidirectional 100 mbit limitation on 1 gbit or 2.5 gbit links for outbound traffic on port 5 or port 6.
--- drivers/net/dsa/mt7530.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)
drivers/net/dsa/mt7530.c +9 -6
@@ -501,14 +501,19 @@ static bool mt7531_dual_sgmii_supported(static int mt7531_pad_setup (struct dsa_switch *ds,phy_interface_t interface) { -struct mt7530_priv *priv = ds->priv; +return 0 ; +} + +static void +mt7531_pll_setup (struct mt7530_priv *priv) +{u32 top_sig;u32 hwstrap;u32 xtal;u32 val;if (mt7531_dual_sgmii_supported (priv)) -return 0 ; +return ; val =mt7530_read (priv,MT7531_CREV ); top_sig =mt7530_read (priv,MT7531_TOP_SIG_SR );
@@ -587,8 +592,6 @@ mt7531_pad_setup(struct dsa_switch *ds, val |=EN_COREPLL ;mt7530_write (priv,MT7531_PLLGP_EN , val);usleep_range (25 ,35 ); - -return 0 ; } static void
@@ -2292,6 +2295,8 @@ mt7531_setup(struct dsa_switch *ds)SYS_CTRL_PHY_RST |SYS_CTRL_SW_RST | SYS_CTRL_REG_RST); +mt7531_pll_setup (priv); +if (mt7531_dual_sgmii_supported (priv)) { priv->p5_intf_sel =P5_INTF_SEL_GMAC5_SGMII ;
@@ -2867,8 +2872,6 @@ mt7531_cpu_port_config(struct dsa_switchcase 6 : interface =PHY_INTERFACE_MODE_2500BASEX ; -mt7531_pad_setup (ds, interface); - priv->p6_interface = interface;break ;default :
Greg Kroah-Hartman
maintainerPATCH 21/83 Revert "firmware: arm_scmi: Add clock management to the SCMI power domain"
In reply to Greg Kroah-HartmanFrom: Ulf Hansson <[email protected]>
commit 3c6656337852e9f1a4079d172f3fddfbf00868f9 upstream.
This reverts commit a3b884cef873 ("firmware: arm_scmi: Add clock management to the SCMI power domain").
Using the GENPD_FLAG_PM_CLK tells genpd to gate/ungate the consumer device's clock(s) during runtime suspend/resume through the PM clock API. More precisely, in genpd_runtime_resume() the clock(s) for the consumer device would become ungated prior to the driver-level ->runtime_resume() callbacks gets invoked.
This behaviour isn't a good fit for all platforms/drivers. For example, a driver may need to make some preparations of its device in its ->runtime_resume() callback, like calling clk_set_rate() before the clock(s) should be ungated. In these cases, it's easier to let the clock(s) to be managed solely by the driver, rather than at the PM domain level.
For these reasons, let's drop the use GENPD_FLAG_PM_CLK for the SCMI PM domain, as to enable it to be more easily adopted across ARM platforms.
--- drivers/firmware/arm_scmi/scmi_pm_domain.c | 26 -------------------------- 1 file changed, 26 deletions(-)
drivers/firmware/arm_scmi/scmi_pm_domain.c +0 -26
@@ -8,7 +8,6 @@#include <linux/err.h> #include <linux/io.h> #include <linux/module.h> -#include <linux/pm_clock.h> #include <linux/pm_domain.h> #include <linux/scmi_protocol.h>
@@ -53,27 +52,6 @@ static int scmi_pd_power_off(struct genereturn scmi_pd_power (domain, false); } -static int scmi_pd_attach_dev (struct generic_pm_domain *pd,struct device *dev) -{ -int ret; - - ret =pm_clk_create (dev); -if (ret) -return ret; - - ret =of_pm_clk_add_clks (dev); -if (ret >=0 ) -return 0 ; - -pm_clk_destroy (dev); -return ret; -} - -static void scmi_pd_detach_dev (struct generic_pm_domain *pd,struct device *dev) -{ -pm_clk_destroy (dev); -} -static int scmi_pm_domain_probe (struct scmi_device *sdev) {int num_domains, i;
@@ -124,10 +102,6 @@ static int scmi_pm_domain_probe(struct s scmi_pd->genpd.name = scmi_pd->name; scmi_pd->genpd.power_off = scmi_pd_power_off; scmi_pd->genpd.power_on = scmi_pd_power_on; - scmi_pd->genpd.attach_dev = scmi_pd_attach_dev; - scmi_pd->genpd.detach_dev = scmi_pd_detach_dev; - scmi_pd->genpd.flags =GENPD_FLAG_PM_CLK | -GENPD_FLAG_ACTIVE_WAKEUP ;pm_genpd_init (&scmi_pd->genpd,NULL , state ==SCMI_POWER_STATE_GENERIC_OFF );
Greg Kroah-Hartman
maintainerPATCH 22/83 powerpc/64s/radix: dont need to broadcast IPI for radix pmd collapse flush
In reply to Greg Kroah-HartmanFrom: Yang Shi <[email protected]>
commit bedf03416913d88c796288f9dca109a53608c745 upstream.
The IPI broadcast is used to serialize against fast-GUP, but fast-GUP will move to use RCU instead of disabling local interrupts in fast-GUP. Using an IPI is the old-styled way of serializing against fast-GUP although it still works as expected now.
And fast-GUP now fixed the potential race with THP collapse by checking whether PMD is changed or not. So IPI broadcast in radix pmd collapse flush is not necessary anymore. But it is still needed for hash TLB.
--- arch/powerpc/mm/book3s64/radix_pgtable.c | 9 --------- 1 file changed, 9 deletions(-)
arch/powerpc/mm/book3s64/radix_pgtable.c +0 -9
@@ -954,15 +954,6 @@ pmd_t radix__pmdp_collapse_flush(struct pmd = *pmdp;pmd_clear (pmdp); -/* -* pmdp collapse_flush need to ensure that there are no parallel gup -* walk after this call. This is needed so that we can have stable -* page ref count when collapsing a page. We don't allow a collapse page -* if we have gup taken on the page. We can ensure that by sending IPI -* because gup walk happens with IRQ disabled. -*/ -serialize_against_pte_lookup (vma->vm_mm); -radix__flush_tlb_collapsed_pmd (vma->vm_mm, address);return pmd;
Greg Kroah-Hartman
maintainerPATCH 23/83 drm/i915/gt: Restrict forced preemption to the active context
In reply to Greg Kroah-HartmanFrom: Chris Wilson <[email protected]>
commit 6ef7d362123ecb5bf6d163bb9c7fd6ba2d8c968c upstream.
When we submit a new pair of contexts to ELSP for execution, we start a timer by which point we expect the HW to have switched execution to the pending contexts. If the promotion to the new pair of contexts has not occurred, we declare the executing context to have hung and force the preemption to take place by resetting the engine and resubmitting the new contexts.
This can lead to an unfair situation where almost all of the preemption timeout is consumed by the first context which just switches into the second context immediately prior to the timer firing and triggering the preemption reset (assuming that the timer interrupts before we process the CS events for the context switch). The second context hasn't yet had a chance to yield to the incoming ELSP (and send the ACk for the promotion) and so ends up being blamed for the reset.
If we see that a context switch has occurred since setting the preemption timeout, but have not yet received the ACK for the ELSP promotion, rearm the preemption timer and check again. This is especially significant if the first context was not schedulable and so we used the shortest timer possible, greatly increasing the chance of accidentally blaming the second innocent context.
--- drivers/gpu/drm/i915/gt/intel_engine_types.h | 15 +++++++++++++ drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 21 ++++++++++++++++++- 2 files changed, 35 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_engine_types.h +15 -0
@@ -144,6 +144,21 @@ struct intel_engine_execlists {struct timer_list preempt;/** +* @preempt_target: active request at the time of the preemption request +* +* We force a preemption to occur if the pending contexts have not +* been promoted to active upon receipt of the CS ack event within +* the timeout. This timeout maybe chosen based on the target, +* using a very short timeout if the context is no longer schedulable. +* That short timeout may not be applicable to other contexts, so +* if a context switch should happen within before the preemption +* timeout, we may shoot early at an innocent context. To prevent this, +* we record which context was active at the time of the preemption +* request and only reset that context upon the timeout. +*/ +const struct i915_request *preempt_target; + +/** * @ccid: identifier for contexts submitted to this engine */ u32 ccid;
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +20 -1
@@ -1225,6 +1225,9 @@ static unsigned long active_preempt_timeif (!rq)return 0 ; +/* Only allow ourselves to force reset the currently active context */ + engine->execlists.preempt_target = rq; +/* Force a fast reset for terminated contexts (ignoring sysfs!) */ if (unlikely (intel_context_is_banned (rq->context) ||bad_request (rq)))return 1 ;
@@ -2401,8 +2404,24 @@ static void execlists_submission_taskletGEM_BUG_ON (inactive - post >ARRAY_SIZE (post));if (unlikely (preempt_timeout (engine))) { +const struct i915_request *rq = *engine->execlists.active; + +/* +* If after the preempt-timeout expired, we are still on the +* same active request/context as before we initiated the +* preemption, reset the engine. +* +* However, if we have processed a CS event to switch contexts, +* but not yet processed the CS event for the pending +* preemption, reset the timer allowing the new context to +* gracefully exit. +*/ cancel_timer (&engine->execlists.preempt); - engine->execlists.error_interrupt |=ERROR_PREEMPT ; +if (rq == engine->execlists.preempt_target) + engine->execlists.error_interrupt |=ERROR_PREEMPT ; +else +set_timer_ms (&engine->execlists.preempt, +active_preempt_timeout (engine, rq)); }if (unlikely (READ_ONCE (engine->execlists.error_interrupt))) {
Greg Kroah-Hartman
maintainerPATCH 24/83 drm/amdgpu: Add amdgpu suspend-resume code path under SRIOV
In reply to Greg Kroah-HartmanFrom: Bokun Zhang <[email protected]>
commit 3b7329cf5a767c1be38352d43066012e220ad43c upstream.
- Under SRIOV, we need to send REQ_GPU_FINI to the hypervisor during the suspend time. Furthermore, we cannot request a mode 1 reset under SRIOV as VF. Therefore, we will skip it as it is called in suspend_noirq() function.
- In the resume code path, we need to send REQ_GPU_INIT to the hypervisor and also resume PSP IP block under SRIOV.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 ++++ drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 27 ++++++++++++++++++++++++++- 2 files changed, 30 insertions(+), 1 deletion(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c +4 -0
@@ -1056,6 +1056,10 @@ bool amdgpu_acpi_should_gpu_reset(struct {if (adev->flags &AMD_IS_APU )return false; + +if (amdgpu_sriov_vf (adev)) +return false; +return pm_suspend_target_state !=PM_SUSPEND_TO_IDLE ; }
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +26 -1
@@ -3137,7 +3137,8 @@ static int amdgpu_device_ip_resume_phasecontinue ;if (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_COMMON || adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_GMC || - adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_IH ) { + adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_IH || + (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_PSP &&amdgpu_sriov_vf (adev))) { r = adev->ip_blocks[i].version->funcs->resume (adev);if (r) {
@@ -4001,12 +4002,20 @@ static void amdgpu_device_evict_resourceint amdgpu_device_suspend (struct drm_device *dev,bool fbcon) {struct amdgpu_device *adev =drm_to_adev (dev); +int r =0 ;if (dev->switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ; adev->in_suspend = true; +if (amdgpu_sriov_vf (adev)) { +amdgpu_virt_fini_data_exchange (adev); + r =amdgpu_virt_request_full_gpu (adev, false); +if (r) +return r; + } +if (amdgpu_acpi_smart_shift_update (dev,AMDGPU_SS_DEV_D3 ))DRM_WARN ("smart shift update failed\n" );
@@ -4035,6 +4044,9 @@ int amdgpu_device_suspend(struct drm_dev*/ amdgpu_device_evict_resources (adev); +if (amdgpu_sriov_vf (adev)) +amdgpu_virt_release_full_gpu (adev, false); +return 0 ; }
@@ -4053,6 +4065,12 @@ int amdgpu_device_resume(struct drm_devistruct amdgpu_device *adev =drm_to_adev (dev);int r =0 ; +if (amdgpu_sriov_vf (adev)) { + r =amdgpu_virt_request_full_gpu (adev, true); +if (r) +return r; + } +if (dev->switch_power_state ==DRM_SWITCH_POWER_OFF )return 0 ;
@@ -4067,6 +4085,13 @@ int amdgpu_device_resume(struct drm_devi } r =amdgpu_device_ip_resume (adev); + +/* no matter what r is, always need to properly release full GPU */ +if (amdgpu_sriov_vf (adev)) { +amdgpu_virt_init_data_exchange (adev); +amdgpu_virt_release_full_gpu (adev, true); + } +if (r) {dev_err (adev->dev,"amdgpu_device_ip_resume failed (%d).\n" , r);return r;
Greg Kroah-Hartman
maintainerPATCH 25/83 vduse: prevent uninitialized memory accesses
In reply to Greg Kroah-HartmanFrom: Maxime Coquelin <[email protected]>
commit 46f8a29272e51b6df7393d58fc5cb8967397ef2b upstream.
If the VDUSE application provides a smaller config space than the driver expects, the driver may use uninitialized memory from the stack.
This patch prevents it by initializing the buffer passed by the driver to store the config value.
This fix addresses CVE-2022-2308.
Message-Id: <[email protected]>
--- drivers/vdpa/vdpa_user/vduse_dev.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/vdpa/vdpa_user/vduse_dev.c +7 -2
@@ -655,10 +655,15 @@ static void vduse_vdpa_get_config(struct {struct vduse_dev *dev =vdpa_to_vduse (vdpa); -if (offset > dev->config_size || - len > dev->config_size - offset) +/* Initialize the buffer in case of partial copy. */ +memset (buf,0 , len); + +if (offset > dev->config_size)return ; +if (len > dev->config_size - offset) + len = dev->config_size - offset; +memcpy (buf, dev->config + offset, len); }
Greg Kroah-Hartman
maintainerPATCH 26/83 libata: add ATA_HORKAGE_NOLPM for Pioneer BDR-207M and BDR-205
In reply to Greg Kroah-HartmanFrom: Niklas Cassel <[email protected]>
commit ea08aec7e77bfd6599489ec430f9f859ab84575a upstream.
Commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile") added an explicit entry for AMD Green Sardine AHCI controller using the board_ahci_mobile configuration (this configuration has later been renamed to board_ahci_low_power).
The board_ahci_low_power configuration enables support for low power modes.
This explicit entry takes precedence over the generic AHCI controller entry, which does not enable support for low power modes.
Therefore, when commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile") was backported to stable kernels, it make some Pioneer optical drives, which was working perfectly fine before the commit was backported, stop working.
The real problem is that the Pioneer optical drives do not handle low power modes correctly. If these optical drives would have been tested on another AHCI controller using the board_ahci_low_power configuration, this issue would have been detected earlier.
Unfortunately, the board_ahci_low_power configuration is only used in less than 15% of the total AHCI controller entries, so many devices have never been tested with an AHCI controller with low power modes.
--- drivers/ata/libata-core.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/ata/libata-core.c +4 -0
@@ -3961,6 +3961,10 @@ static const struct ata_blacklist_entry { "PIONEER DVD-RW DVR-212D", NULL, ATA_HORKAGE_NOSETXFER }, { "PIONEER DVD-RW DVR-216D", NULL, ATA_HORKAGE_NOSETXFER }, +/* These specific Pioneer models have LPM issues */ + { "PIONEER BD-RW BDR-207M", NULL, ATA_HORKAGE_NOLPM }, + { "PIONEER BD-RW BDR-205", NULL, ATA_HORKAGE_NOLPM }, +/* Crucial BX100 SSD 500GB has broken LPM support */ { "CT500BX100SSD1", NULL, ATA_HORKAGE_NOLPM },
Greg Kroah-Hartman
maintainerPATCH 27/83 mmc: moxart: fix 4-bit bus width and remove 8-bit bus width
In reply to Greg Kroah-HartmanFrom: Sergei Antonov <[email protected]>
commit 35ca91d1338ae158f6dcc0de5d1e86197924ffda upstream.
According to the datasheet [1] at page 377, 4-bit bus width is turned on by bit 2 of the Bus Width Register. Thus the current bitmask is wrong: define BUS_WIDTH_4 BIT(1)
BIT(1) does not work but BIT(2) works. This has been verified on real MOXA hardware with FTSDC010 controller revision 1_6_0.
The corrected value of BUS_WIDTH_4 mask collides with: define BUS_WIDTH_8 BIT(2). Additionally, 8-bit bus width mode isn't supported according to the datasheet, so let's remove the corresponding code.
[1]
https://bitbucket.org/Kasreyn/mkrom-uc7112lx/src/master/documents/FIC8120_DS_v1.2.pdf
--- drivers/mmc/host/moxart-mmc.c | 17 +++-------------- 1 file changed, 3 insertions(+), 14 deletions(-)
drivers/mmc/host/moxart-mmc.c +3 -14
@@ -111,8 +111,8 @@#define CLK_DIV_MASK 0x7f/* REG_BUS_WIDTH */ -#define BUS_WIDTH_8 BIT(2) -#define BUS_WIDTH_4 BIT(1) +#define BUS_WIDTH_4_SUPPORT BIT(3) +#define BUS_WIDTH_4 BIT(2)#define BUS_WIDTH_1 BIT(0)#define MMC_VDD_360 23
@@ -524,9 +524,6 @@ static void moxart_set_ios(struct mmc_hocase MMC_BUS_WIDTH_4 :writel (BUS_WIDTH_4 , host->base +REG_BUS_WIDTH );break ; -case MMC_BUS_WIDTH_8 : -writel (BUS_WIDTH_8 , host->base +REG_BUS_WIDTH ); -break ;default :writel (BUS_WIDTH_1 , host->base +REG_BUS_WIDTH );break ;
@@ -651,16 +648,8 @@ static int moxart_probe(struct platform_dmaengine_slave_config (host->dma_chan_rx, &cfg); } -switch ((readl (host->base +REG_BUS_WIDTH ) >>3 ) &3 ) { -case 1 : +if (readl (host->base +REG_BUS_WIDTH ) &BUS_WIDTH_4_SUPPORT ) mmc->caps |=MMC_CAP_4_BIT_DATA ; -break ; -case 2 : - mmc->caps |=MMC_CAP_4_BIT_DATA |MMC_CAP_8_BIT_DATA ; -break ; -default : -break ; - }writel (0 , host->base +REG_INTERRUPT_MASK );
Greg Kroah-Hartman
maintainerPATCH 28/83 mmc: hsq: Fix data stomping during mmc recovery
In reply to Greg Kroah-HartmanFrom: Wenchao Chen <[email protected]>
commit e7afa79a3b35a27a046a2139f8b20bd6b98155c2 upstream.
The block device uses multiple queues to access emmc. There will be up to 3 requests in the hsq of the host. The current code will check whether there is a request doing recovery before entering the queue, but it will not check whether there is a request when the lock is issued. The request is in recovery mode. If there is a request in recovery, then a read and write request is initiated at this time, and the conflict between the request and the recovery request will cause the data to be trampled.
--- drivers/mmc/host/mmc_hsq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mmc/host/mmc_hsq.c +1 -1
@@ -34,7 +34,7 @@ static void mmc_hsq_pump_requests(structspin_lock_irqsave (&hsq->lock, flags);/* Make sure we are not already running a request now */ -if (hsq->mrq) { +if (hsq->mrq || hsq->recovery_halt) {spin_unlock_irqrestore (&hsq->lock, flags);return ; }
Greg Kroah-Hartman
maintainerPATCH 29/83 mm/page_alloc: fix race condition between build_all_zonelists and page allocation
In reply to Greg Kroah-HartmanFrom: Mel Gorman <[email protected]>
commit 3d36424b3b5850bd92f3e89b953a430d7cfc88ef upstream.
Patrick Daly reported the following problem;
NODE_DATA(nid)->node_zonelists[ZONELIST_FALLBACK] - before offline operation [0] - ZONE_MOVABLE [1] - ZONE_NORMAL [2] - NULL For a GFP_KERNEL allocation, alloc_pages_slowpath() will save the offset of ZONE_NORMAL in ac->preferred_zoneref. If a concurrent memory_offline operation removes the last page from ZONE_MOVABLE, build_all_zonelists() & build_zonerefs_node() will update node_zonelists as shown below. Only populated zones are added. NODE_DATA(nid)->node_zonelists[ZONELIST_FALLBACK] - after offline operation [0] - ZONE_NORMAL [1] - NULL [2] - NULL
The race is simple -- page allocation could be in progress when a memory hot-remove operation triggers a zonelist rebuild that removes zones. The allocation request will still have a valid ac->preferred_zoneref that is now pointing to NULL and triggers an OOM kill.
This problem probably always existed but may be slightly easier to trigger due to 6aa303defb74 ("mm, vmscan: only allocate and reclaim from zones with pages managed by the buddy allocator") which distinguishes between zones that are completely unpopulated versus zones that have valid pages not managed by the buddy allocator (e.g. reserved, memblock, ballooning etc). Memory hotplug had multiple stages with timing considerations around managed/present page updates, the zonelist rebuild and the zone span updates. As David Hildenbrand puts it
memory offlining adjusts managed+present pages of the zone essentially in one go. If after the adjustments, the zone is no longer populated (present==0), we rebuild the zone lists.
Once that's done, we try shrinking the zone (start+spanned pages) -- which results in zone_start_pfn == 0 if there are no more pages. That happens *after* rebuilding the zonelists via remove_pfn_range_from_zone().
The only requirement to fix the race is that a page allocation request identifies when a zonelist rebuild has happened since the allocation request started and no page has yet been allocated. Use a seqlock_t to track zonelist updates with a lockless read-side of the zonelist and protecting the rebuild and update of the counter with a spinlock.
--- mm/page_alloc.c | 53 +++++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 43 insertions(+), 10 deletions(-)
mm/page_alloc.c +43 -10
@@ -4581,6 +4581,30 @@ void fs_reclaim_release(gfp_t gfp_mask)EXPORT_SYMBOL_GPL (fs_reclaim_release);#endif +/* +* Zonelists may change due to hotplug during allocation. Detect when zonelists +* have been rebuilt so allocation retries. Reader side does not lock and +* retries the allocation if zonelist changes. Writer side is protected by the +* embedded spin_lock. +*/ +static DEFINE_SEQLOCK (zonelist_update_seq); + +static unsigned int zonelist_iter_begin (void ) +{ +if (IS_ENABLED (CONFIG_MEMORY_HOTREMOVE )) +return read_seqbegin (&zonelist_update_seq); + +return 0 ; +} + +static unsigned int check_retry_zonelist (unsigned int seq) +{ +if (IS_ENABLED (CONFIG_MEMORY_HOTREMOVE )) +return read_seqretry (&zonelist_update_seq, seq); + +return seq; +} +/* Perform direct synchronous page reclaim */ static unsigned long __perform_reclaim(gfp_t gfp_mask, unsigned int order,
@@ -4888,6 +4912,7 @@ __alloc_pages_slowpath(gfp_t gfp_mask, uint compaction_retries;int no_progress_loops;unsigned int cpuset_mems_cookie; +unsigned int zonelist_iter_cookie;int reserve_flags;/*
@@ -4898,11 +4923,12 @@ __alloc_pages_slowpath(gfp_t gfp_mask, u (__GFP_ATOMIC|__GFP_DIRECT_RECLAIM))) gfp_mask &= ~__GFP_ATOMIC; -retry_cpuset: +restart: compaction_retries =0 ; no_progress_loops =0 ; compact_priority =DEF_COMPACT_PRIORITY ; cpuset_mems_cookie =read_mems_allowed_begin (); + zonelist_iter_cookie =zonelist_iter_begin ();/* * The fast path uses conservative alloc_flags to succeed only until
@@ -5061,9 +5087,13 @@ retry: goto retry; -/* Deal with possible cpuset update races before we start OOM killing */ -if (check_retry_cpuset (cpuset_mems_cookie, ac)) - goto retry_cpuset; +/* +* Deal with possible cpuset update races or zonelist updates to avoid +* a unnecessary OOM kill. +*/ +if (check_retry_cpuset (cpuset_mems_cookie, ac) || +check_retry_zonelist (zonelist_iter_cookie)) + goto restart;/* Reclaim has failed us, start killing things */ page =__alloc_pages_may_oom (gfp_mask, order, ac, &did_some_progress);
@@ -5083,9 +5113,13 @@ retry: } nopage: -/* Deal with possible cpuset update races before we fail */ -if (check_retry_cpuset (cpuset_mems_cookie, ac)) - goto retry_cpuset; +/* +* Deal with possible cpuset update races or zonelist updates to avoid +* a unnecessary OOM kill. +*/ +if (check_retry_cpuset (cpuset_mems_cookie, ac) || +check_retry_zonelist (zonelist_iter_cookie)) + goto restart;/* * Make sure that __GFP_NOFAIL request doesn't leak out and make sure
@@ -6367,9 +6401,8 @@ static void __build_all_zonelists(void *int nid;int __maybe_unused cpu;pg_data_t *self = data; -static DEFINE_SPINLOCK (lock); -spin_lock (&lock); +write_seqlock (&zonelist_update_seq);#ifdef CONFIG_NUMA memset (node_load,0 ,sizeof (node_load));
@@ -6402,7 +6435,7 @@ static void __build_all_zonelists(void *#endif } -spin_unlock (&lock); +write_sequnlock (&zonelist_update_seq); }static noinline void__init
Greg Kroah-Hartman
maintainerPATCH 30/83 mm: prevent page_frag_alloc() from corrupting the memory
In reply to Greg Kroah-HartmanFrom: Maurizio Lombardi <[email protected]>
commit dac22531bbd4af2426c4e29e05594415ccfa365d upstream.
A number of drivers call page_frag_alloc() with a fragment's size > PAGE_SIZE.
In low memory conditions, __page_frag_cache_refill() may fail the order 3 cache allocation and fall back to order 0; In this case, the cache will be smaller than the fragment, causing memory corruptions.
Prevent this from happening by checking if the newly allocated cache is large enough for the fragment; if not, the allocation will fail and page_frag_alloc() will return NULL.
--- mm/page_alloc.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
mm/page_alloc.c +12 -0
@@ -5600,6 +5600,18 @@ refill:/* reset page count bias and offset to start of new frag */ nc->pagecnt_bias =PAGE_FRAG_CACHE_MAX_SIZE +1 ; offset = size - fragsz; +if (unlikely (offset <0 )) { +/* +* The caller is trying to allocate a fragment +* with fragsz > PAGE_SIZE but the cache isn't big +* enough to satisfy the request, this may +* happen in low memory conditions. +* We don't release the cache page because +* it could make memory pressure worse +* so we simply return NULL here. +*/ +return NULL ; + } } nc->pagecnt_bias--;
Greg Kroah-Hartman
maintainerPATCH 31/83 mm: fix dereferencing possible ERR_PTR
In reply to Greg Kroah-HartmanFrom: Binyi Han <[email protected]>
commit 4eb5bbde3ccb710d3b85bfb13466612e56393369 upstream.
Smatch checker complains that 'secretmem_mnt' dereferencing possible ERR_PTR(). Let the function return if 'secretmem_mnt' is ERR_PTR, to avoid deferencing it.
--- mm/secretmem.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/secretmem.c +1 -1
@@ -283,7 +283,7 @@ static int secretmem_init(void) secretmem_mnt =kern_mount (&secretmem_fs);if (IS_ERR (secretmem_mnt)) - ret =PTR_ERR (secretmem_mnt); +return PTR_ERR (secretmem_mnt);/* prevent secretmem mappings from ever getting PROT_EXEC */ secretmem_mnt->mnt_flags |=MNT_NOEXEC ;
Greg Kroah-Hartman
maintainerPATCH 32/83 mm/migrate_device.c: flush TLB while holding PTL
In reply to Greg Kroah-HartmanFrom: Alistair Popple <[email protected]>
commit 60bae73708963de4a17231077285bd9ff2f41c44 upstream.
When clearing a PTE the TLB should be flushed whilst still holding the PTL to avoid a potential race with madvise/munmap/etc. For example consider the following sequence:
CPU0 CPU1
---- ----
migrate_vma_collect_pmd()
pte_unmap_unlock()
madvise(MADV_DONTNEED)
-> zap_pte_range() pte_offset_map_lock()
[ PTE not present, TLB not flushed ] pte_unmap_unlock()
[ page is still accessible via stale TLB ]
flush_tlb_range()
In this case the page may still be accessed via the stale TLB entry after madvise returns. Fix this by flushing the TLB while holding the PTL.
--- mm/migrate.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
mm/migrate.c +3 -2
@@ -2422,13 +2422,14 @@ next: migrate->dst[migrate->npages] =0 ; migrate->src[migrate->npages++] = mpfn; } -arch_leave_lazy_mmu_mode (); -pte_unmap_unlock (ptep -1 , ptl);/* Only flush the TLB if we actually modified any entries */ if (unmapped)flush_tlb_range (walk->vma, start, end); +arch_leave_lazy_mmu_mode (); +pte_unmap_unlock (ptep -1 , ptl); +return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 33/83 mm: fix madivse_pageout mishandling on non-LRU page
In reply to Greg Kroah-HartmanFrom: Minchan Kim <[email protected]>
commit 58d426a7ba92870d489686dfdb9d06b66815a2ab upstream.
MADV_PAGEOUT tries to isolate non-LRU pages and gets a warning from isolate_lru_page below.
Fix it by checking PageLRU in advance.
------------[ cut here ]------------ trying to isolate tail page WARNING: CPU: 0 PID: 6175 at mm/folio-compat.c:158 isolate_lru_page+0x130/0x140 Modules linked in: CPU: 0 PID: 6175 Comm: syz-executor.0 Not tainted 5.18.12 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:isolate_lru_page+0x130/0x140
--- mm/madvise.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
mm/madvise.c +5 -2
@@ -436,8 +436,11 @@ regular_page:continue ; } -/* Do not interfere with other mappings of this page */ -if (page_mapcount (page) !=1 ) +/* +* Do not interfere with other mappings of this page and +* non-LRU page. +*/ +if (!PageLRU (page) ||page_mapcount (page) !=1 )continue ;VM_BUG_ON_PAGE (PageTransCompound (page), page);
Greg Kroah-Hartman
maintainerPATCH 34/83 mm,hwpoison: check mm when killing accessing process
In reply to Greg Kroah-HartmanFrom: Shuai Xue <[email protected]>
commit 77677cdbc2aa4b5d5d839562793d3d126201d18d upstream.
The GHES code calls memory_failure_queue() from IRQ context to queue work into workqueue and schedule it on the current CPU. Then the work is processed in memory_failure_work_func() by kworker and calls memory_failure().
When a page is already poisoned, commit a3f5d80ea401 ("mm,hwpoison: send SIGBUS with error virutal address") make memory_failure() call kill_accessing_process() that:
- holds mmap locking of current->mm
- does pagetable walk to find the error virtual address
- and sends SIGBUS to the current process with error info.
However, the mm of kworker is not valid, resulting in a null-pointer dereference. So check mm when killing the accessing process.
--- mm/memory-failure.c | 3 +++ 1 file changed, 3 insertions(+)
mm/memory-failure.c +3 -0
@@ -700,6 +700,9 @@ static int kill_accessing_process(struct }; priv.tk.tsk = p; +if (!p->mm) +return -EFAULT ; +mmap_read_lock (p->mm); ret =walk_page_range (p->mm,0 ,TASK_SIZE , &hwp_walk_ops, (void *)&priv);
Greg Kroah-Hartman
maintainerPATCH 35/83 media: dvb_vb2: fix possible out of bound access
In reply to Greg Kroah-HartmanFrom: Hangyu Hua <[email protected]>
commit 37238699073e7e93f05517e529661151173cd458 upstream.
vb2_core_qbuf and vb2_core_querybuf don't check the range of b->index controlled by the user.
Fix this by adding range checking code before using them.
--- drivers/media/dvb-core/dvb_vb2.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/media/dvb-core/dvb_vb2.c +11 -0
@@ -358,6 +358,12 @@ int dvb_vb2_reqbufs(struct dvb_vb2_ctx *int dvb_vb2_querybuf (struct dvb_vb2_ctx *ctx,struct dmx_buffer *b) { +struct vb2_queue *q = &ctx->vb_q; + +if (b->index >= q->num_buffers) { +dprintk (1 ,"[%s] buffer index out of range\n" , ctx->name); +return -EINVAL ; + }vb2_core_querybuf (&ctx->vb_q, b->index, b);dprintk (3 ,"[%s] index=%d\n" , ctx->name, b->index);return 0 ;
@@ -382,8 +388,13 @@ int dvb_vb2_expbuf(struct dvb_vb2_ctx *cint dvb_vb2_qbuf (struct dvb_vb2_ctx *ctx,struct dmx_buffer *b) { +struct vb2_queue *q = &ctx->vb_q;int ret; +if (b->index >= q->num_buffers) { +dprintk (1 ,"[%s] buffer index out of range\n" , ctx->name); +return -EINVAL ; + } ret =vb2_core_qbuf (&ctx->vb_q, b->index, b,NULL );if (ret) { dprintk(1, "[%s] index=%d errno=%d\n", ctx->name,
Greg Kroah-Hartman
maintainerPATCH 36/83 media: rkvdec: Disable H.264 error detection
In reply to Greg Kroah-HartmanFrom: Nicolas Dufresne <[email protected]>
commit 3a99c4474112f49a5459933d8758614002ca0ddc upstream.
Quite often, the HW get stuck in error condition if a stream error was detected. As documented, the HW should stop immediately and self reset. There is likely a problem or a miss-understanding of the self reset mechanism, as unless we make a long pause, the next command will then report an error even if there is no error in it.
Disabling error detection fixes the issue, and let the decoder continue after an error. This patch is safe for backport into older kernels.
--- drivers/staging/media/rkvdec/rkvdec-h264.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/staging/media/rkvdec/rkvdec-h264.c +2 -2
@@ -1124,8 +1124,8 @@ static int rkvdec_h264_run(struct rkvdecschedule_delayed_work (&rkvdec->watchdog_work,msecs_to_jiffies (2000 )); -writel (0xffffffff , rkvdec->regs +RKVDEC_REG_STRMD_ERR_EN ); -writel (0xffffffff , rkvdec->regs +RKVDEC_REG_H264_ERR_E ); +writel (0 , rkvdec->regs +RKVDEC_REG_STRMD_ERR_EN ); +writel (0 , rkvdec->regs +RKVDEC_REG_H264_ERR_E );writel (1 , rkvdec->regs +RKVDEC_REG_PREF_LUMA_CACHE_COMMAND );writel (1 , rkvdec->regs +RKVDEC_REG_PREF_CHR_CACHE_COMMAND );
Greg Kroah-Hartman
maintainerPATCH 37/83 media: v4l2-compat-ioctl32.c: zero buffer passed to v4l2_compat_get_array_args()
In reply to Greg Kroah-HartmanFrom: Hans Verkuil <[email protected]>
commit 4e768c8e34e639cff66a0f175bc4aebf472e4305 upstream.
The v4l2_compat_get_array_args() function can leave uninitialized memory in the buffer it is passed. So zero it before copying array elements from userspace into the buffer.
--- drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/media/v4l2-core/v4l2-compat-ioctl32.c +2 -0
@@ -1033,6 +1033,8 @@ int v4l2_compat_get_array_args(struct fi {int err =0 ; +memset (mbuf,0 , array_size); +switch (cmd) {case VIDIOC_G_FMT32 :case VIDIOC_S_FMT32 :
Greg Kroah-Hartman
maintainerPATCH 38/83 swiotlb: max mapping size takes min align mask into account
In reply to Greg Kroah-HartmanFrom: Tianyu Lan <[email protected]>
commit 82806744fd7dde603b64c151eeddaa4ee62193fd upstream.
swiotlb_find_slots() skips slots according to io tlb aligned mask calculated from min aligned mask and original physical address offset. This affects max mapping size. The mapping size can't achieve the IO_TLB_SEGSIZE * IO_TLB_SIZE when original offset is non-zero. This will cause system boot up failure in Hyper-V Isolation VM where swiotlb force is enabled. Scsi layer use return value of dma_max_mapping_size() to set max segment size and it finally calls swiotlb_max_mapping_size(). Hyper-V storage driver sets min align mask to 4k - 1. Scsi layer may pass 256k length of request buffer with 0~4k offset and Hyper-V storage driver can't get swiotlb bounce buffer via DMA API. Swiotlb_find_slots() can't find 256k length bounce buffer with offset. Make swiotlb_max_mapping _size() take min align mask into account.
--- kernel/dma/swiotlb.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
kernel/dma/swiotlb.c +12 -1
@@ -709,7 +709,18 @@ dma_addr_t swiotlb_map(struct device *desize_t swiotlb_max_mapping_size (struct device *dev) { -return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE ; +int min_align_mask =dma_get_min_align_mask (dev); +int min_align =0 ; + +/* +* swiotlb_find_slots() skips slots according to +* min align mask. This affects max mapping size. +* Take it into acount here. +*/ +if (min_align_mask) + min_align =roundup (min_align_mask,IO_TLB_SIZE ); + +return ((size_t )IO_TLB_SIZE ) *IO_TLB_SEGSIZE - min_align; }bool is_swiotlb_active (struct device *dev)
Greg Kroah-Hartman
maintainerPATCH 39/83 ARM: dts: am33xx: Fix MMCHS0 dma properties
In reply to Greg Kroah-HartmanFrom: YuTong Chang <[email protected]>
[ Upstream commit 2eb502f496f7764027b7958d4e74356fed918059 ]
According to technical manual(table 11-24), the DMA of MMCHS0 should be direct mapped.
Message-Id: <[email protected]>
--- arch/arm/boot/dts/am33xx-l4.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/arm/boot/dts/am33xx-l4.dtsi +1 -2
@@ -1500,8 +1500,7 @@ mmc1: mmc@0 { compatible = "ti,am335-sdhci"; ti,needs-special-reset; - dmas = <&edma_xbar 24 0 0 - &edma_xbar 25 0 0>; + dmas = <&edma 24 0>, <&edma 25 0>; dma-names = "tx", "rx"; interrupts = <64>; reg = <0x0 0x1000>;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 40/83 reset: imx7: Fix the iMX8MP PCIe PHY PERST support
In reply to Greg Kroah-HartmanFrom: Richard Zhu <[email protected]>
[ Upstream commit 051d9eb403887bb11852b7a4f744728a6a4b1b58 ]
On i.MX7/iMX8MM/iMX8MQ, the initialized default value of PERST bit(BIT3) of SRC_PCIEPHY_RCR is 1b'1.
But i.MX8MP has one inversed default value 1b'0 of PERST bit.
And the PERST bit should be kept 1b'1 after power and clocks are stable. So fix the i.MX8MP PCIe PHY PERST support here.
--- drivers/reset/reset-imx7.c | 1 + 1 file changed, 1 insertion(+)
drivers/reset/reset-imx7.c +1 -0
@@ -329,6 +329,7 @@ static int imx8mp_reset_set(struct reset_controller_dev *rcdev,break ;case IMX8MP_RESET_PCIE_CTRL_APPS_EN : +case IMX8MP_RESET_PCIEPHY_PERST : value = assert ?0 : bit;break ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 41/83 ARM: dts: am5748: keep usb4_tm disabled
In reply to Greg Kroah-HartmanFrom: Romain Naour <[email protected]>
[ Upstream commit 6a6d9ecff14a2a46c1deeffa3eb3825349639bdd ]
Commit bcbb63b80284 ("ARM: dts: dra7: Separate AM57 dtsi files") disabled usb4_tm for am5748 devices since USB4 IP is not present in this SoC.
The commit log explained the difference between AM5 and DRA7 families:
AM5 and DRA7 SoC families have different set of modules in them so the SoC sepecific dtsi files need to be separated.
e.g. Some of the major differences between AM576 and DRA76
DRA76x AM576x
USB3 x
USB4 x
ATL x
VCP x
MLB x
ISS x
PRU-ICSS1 x
PRU-ICSS2 x
Then commit 176f26bcd41a ("ARM: dts: Add support for dra762 abz package") removed usb4_tm part from am5748.dtsi and introcuded new ti-sysc errors in dmesg:
ti-sysc 48940000.target-module: clock get error for fck: -2
ti-sysc: probe of 48940000.target-module failed with error -2
Message-Id: <[email protected]>
--- arch/arm/boot/dts/am5748.dtsi | 4 ++++ 1 file changed, 4 insertions(+)
arch/arm/boot/dts/am5748.dtsi +4 -0
@@ -25,6 +25,10 @@ status = "disabled"; }; +&usb4_tm { + status = "disabled"; +}; + &atl_tm { status = "disabled"; };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 42/83 soc: sunxi: sram: Actually claim SRAM regions
In reply to Greg Kroah-HartmanFrom: Samuel Holland <[email protected]>
[ Upstream commit fd362baad2e659ef0fb5652f023a606b248f1781 ]
sunxi_sram_claim() checks the sram_desc->claimed flag before updating the register, with the intent that only one device can claim a region. However, this was ineffective because the flag was never set.
--- drivers/soc/sunxi/sunxi_sram.c | 1 + 1 file changed, 1 insertion(+)
drivers/soc/sunxi/sunxi_sram.c +1 -0
@@ -254,6 +254,7 @@ int sunxi_sram_claim(struct device *dev)writel (val | ((device << sram_data->offset) & mask), base + sram_data->reg); + sram_desc->claimed = true;spin_unlock (&sram_lock);return 0 ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 43/83 soc: sunxi: sram: Prevent the driver from being unbound
In reply to Greg Kroah-HartmanFrom: Samuel Holland <[email protected]>
[ Upstream commit 90e10a1fcd9b24b4ba8c0d35136127473dcd829e ]
This driver exports a regmap tied to the platform device (as opposed to a syscon, which exports a regmap tied to the OF node). Because of this, the driver can never be unbound, as that would destroy the regmap. Use builtin_platform_driver_probe() to enforce this limitation.
--- drivers/soc/sunxi/sunxi_sram.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/soc/sunxi/sunxi_sram.c +2 -3
@@ -330,7 +330,7 @@ static struct regmap_config sunxi_sram_emac_clock_regmap = { .writeable_reg = sunxi_sram_regmap_accessible_reg, }; -static int sunxi_sram_probe (struct platform_device *pdev) +static int __init sunxi_sram_probe (struct platform_device *pdev) {struct resource *res;struct dentry *d;
@@ -412,9 +412,8 @@ static struct platform_driver sunxi_sram_driver = { .name = "sunxi-sram", .of_match_table = sunxi_sram_dt_match, }, - .probe = sunxi_sram_probe, }; -module_platform_driver (sunxi_sram_driver); +builtin_platform_driver_probe (sunxi_sram_driver, sunxi_sram_probe);MODULE_AUTHOR ("Maxime Ripard <[email protected]>" );MODULE_DESCRIPTION ("Allwinner sunXi SRAM Controller Driver" );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 44/83 soc: sunxi_sram: Make use of the helper function devm_platform_ioremap_resource()
In reply to Greg Kroah-HartmanFrom: Cai Huoqing <[email protected]>
[ Upstream commit 1f3753a5f042fea6539986f9caf2552877527d8a ]
Use the devm_platform_ioremap_resource() helper instead of calling platform_get_resource() and devm_ioremap_resource() separately
Stable-dep-of: 49fad91a7b89 ("soc: sunxi: sram: Fix probe function ordering issues")
--- drivers/soc/sunxi/sunxi_sram.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/soc/sunxi/sunxi_sram.c +1 -3
@@ -332,7 +332,6 @@ static struct regmap_config sunxi_sram_emac_clock_regmap = {static int __init sunxi_sram_probe (struct platform_device *pdev) { -struct resource *res;struct dentry *d;struct regmap *emac_clock;const struct sunxi_sramc_variant *variant;
@@ -343,8 +342,7 @@ static int __init sunxi_sram_probe(struct platform_device *pdev)if (!variant)return -EINVAL ; - res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); - base =devm_ioremap_resource (&pdev->dev, res); + base =devm_platform_ioremap_resource (pdev,0 );if (IS_ERR (base))return PTR_ERR (base);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 45/83 soc: sunxi: sram: Fix probe function ordering issues
In reply to Greg Kroah-HartmanFrom: Samuel Holland <[email protected]>
[ Upstream commit 49fad91a7b8941979c3e9a35f9894ac45bc5d3d6 ]
Errors from debugfs are intended to be non-fatal, and should not prevent the driver from probing.
Since debugfs file creation is treated as infallible, move it below the parts of the probe function that can fail. This prevents an error elsewhere in the probe function from causing the file to leak. Do the same for the call to of_platform_populate().
Finally, checkpatch suggests an octal literal for the file permissions.
--- drivers/soc/sunxi/sunxi_sram.c | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-)
drivers/soc/sunxi/sunxi_sram.c +5 -8
@@ -332,9 +332,9 @@ static struct regmap_config sunxi_sram_emac_clock_regmap = {static int __init sunxi_sram_probe (struct platform_device *pdev) { -struct dentry *d;struct regmap *emac_clock;const struct sunxi_sramc_variant *variant; +struct device *dev = &pdev->dev; sram_dev = &pdev->dev;
@@ -346,13 +346,6 @@ static int __init sunxi_sram_probe(struct platform_device *pdev)if (IS_ERR (base))return PTR_ERR (base); -of_platform_populate (pdev->dev.of_node,NULL ,NULL , &pdev->dev); - - d =debugfs_create_file ("sram" ,S_IRUGO ,NULL ,NULL , - &sunxi_sram_fops); -if (!d) -return -ENOMEM ; -if (variant->num_emac_clocks >0 ) { emac_clock =devm_regmap_init_mmio (&pdev->dev, base, &sunxi_sram_emac_clock_regmap);
@@ -361,6 +354,10 @@ static int __init sunxi_sram_probe(struct platform_device *pdev)return PTR_ERR (emac_clock); } +of_platform_populate (dev->of_node,NULL ,NULL , dev); + +debugfs_create_file ("sram" ,0444 ,NULL ,NULL , &sunxi_sram_fops); +return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 46/83 soc: sunxi: sram: Fix debugfs info for A64 SRAM C
In reply to Greg Kroah-HartmanFrom: Samuel Holland <[email protected]>
[ Upstream commit e3c95edb1bd8b9c2cb0caa6ae382fc8080f6a0ed ]
The labels were backward with respect to the register values. The SRAM is mapped to the CPU when the register value is 1.
--- drivers/soc/sunxi/sunxi_sram.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/soc/sunxi/sunxi_sram.c +2 -2
@@ -78,8 +78,8 @@ static struct sunxi_sram_desc sun4i_a10_sram_d = {static struct sunxi_sram_desc sun50i_a64_sram_c = { .data =SUNXI_SRAM_DATA ("C" ,0x4 ,24 ,1 , -SUNXI_SRAM_MAP (0 ,1 ,"cpu" ), -SUNXI_SRAM_MAP (1 ,0 ,"de2" )), +SUNXI_SRAM_MAP (1 ,0 ,"cpu" ), +SUNXI_SRAM_MAP (0 ,1 ,"de2" )), };static const struct of_device_id sunxi_sram_dt_ids[] = {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 47/83 ASoC: imx-card: Fix refcount issue with of_node_put
In reply to Greg Kroah-HartmanFrom: Shengjiu Wang <[email protected]>
[ Upstream commit d56ba9a04d7548d4149c46ec86a0e3cc41a70f4a ]
imx_card_parse_of will search all the node with loop, if there is defer probe happen in the middle of loop, the previous released codec node will be released twice, then cause refcount issue.
Here assign NULL to pointer of released nodes to fix the issue.
--- sound/soc/fsl/imx-card.c | 4 ++++ 1 file changed, 4 insertions(+)
sound/soc/fsl/imx-card.c +4 -0
@@ -698,6 +698,10 @@ static int imx_card_parse_of(struct imx_card_data *data)of_node_put (cpu);of_node_put (codec);of_node_put (platform); + + cpu =NULL ; + codec =NULL ; + platform =NULL ; }return 0 ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 48/83 arm64: dts: qcom: sm8350: fix UFS PHY serdes size
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
[ Upstream commit 40e9541959100e017533e18e44d07eed44f91dc5 ]
The size of the UFS PHY serdes register region is 0x1c4 and the corresponding 'reg' property should specifically not include the adjacent regions that are defined in the child node (e.g. tx and rx).
--- arch/arm64/boot/dts/qcom/sm8350.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/qcom/sm8350.dtsi +1 -1
@@ -1109,7 +1109,7 @@ ufs_mem_phy: phy@1d87000 { compatible = "qcom,sm8350-qmp-ufs-phy"; - reg = <0 0x01d87000 0 0xe10>; + reg = <0 0x01d87000 0 0x1c4>; #address-cells = <2>; #size-cells = <2>; #clock-cells = <1>;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 49/83 ASoC: tas2770: Reinit regcache on reset
In reply to Greg Kroah-HartmanFrom: Martin Povišer <[email protected]>
[ Upstream commit 0a0342ede303fc420f3a388e1ae82da3ae8ff6bd ]
On probe of the ASoC component, the device is reset but the regcache is retained. This means the regcache gets out of sync if the codec is rebound to a sound card for a second time. Fix it by reinitializing the regcache to defaults after the device is reset.
--- sound/soc/codecs/tas2770.c | 3 +++ 1 file changed, 3 insertions(+)
sound/soc/codecs/tas2770.c +3 -0
@@ -495,6 +495,8 @@ static struct snd_soc_dai_driver tas2770_dai_driver[] = { }, }; +static const struct regmap_config tas2770_i2c_regmap; +static int tas2770_codec_probe (struct snd_soc_component *component) { struct tas2770_priv *tas2770 =
@@ -508,6 +510,7 @@ static int tas2770_codec_probe(struct snd_soc_component *component) }tas2770_reset (tas2770); +regmap_reinit_cache (tas2770->regmap, &tas2770_i2c_regmap);return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 50/83 drm/bridge: lt8912b: add vsync hsync
In reply to Greg Kroah-HartmanFrom: Philippe Schenker <[email protected]>
[ Upstream commit da73a94fa282f78d485bd0aab36c8ac15b6f792c ]
Currently the bridge driver does not take care whether or not the display needs positive/negative vertical/horizontal syncs. Pass these two flags to the bridge from the EDID that was read out from the display.
--- drivers/gpu/drm/bridge/lontium-lt8912b.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/gpu/drm/bridge/lontium-lt8912b.c +8 -1
@@ -266,7 +266,7 @@ static int lt8912_video_setup(struct lt8912 *lt)u32 hactive, h_total, hpw, hfp, hbp;u32 vactive, v_total, vpw, vfp, vbp;u8 settle =0x08 ; -int ret; +int ret, hsync_activehigh, vsync_activehigh;if (!lt)return -EINVAL ;
@@ -276,12 +276,14 @@ static int lt8912_video_setup(struct lt8912 *lt) hpw = lt->mode.hsync_len; hbp = lt->mode.hback_porch; h_total = hactive + hfp + hpw + hbp; + hsync_activehigh = lt->mode.flags &DISPLAY_FLAGS_HSYNC_HIGH ; vactive = lt->mode.vactive; vfp = lt->mode.vfront_porch; vpw = lt->mode.vsync_len; vbp = lt->mode.vback_porch; v_total = vactive + vfp + vpw + vbp; + vsync_activehigh = lt->mode.flags &DISPLAY_FLAGS_VSYNC_HIGH ;if (vactive <=600 ) settle =0x04 ;
@@ -315,6 +317,11 @@ static int lt8912_video_setup(struct lt8912 *lt) ret |=regmap_write (lt->regmap[I2C_CEC_DSI ],0x3e , hfp &0xff ); ret |=regmap_write (lt->regmap[I2C_CEC_DSI ],0x3f , hfp >>8 ); + ret |=regmap_update_bits (lt->regmap[I2C_MAIN ],0xab ,BIT (0 ), + vsync_activehigh ?BIT (0 ) :0 ); + ret |=regmap_update_bits (lt->regmap[I2C_MAIN ],0xab ,BIT (1 ), + hsync_activehigh ?BIT (1 ) :0 ); +return ret; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 51/83 drm/bridge: lt8912b: set hdmi or dvi mode
In reply to Greg Kroah-HartmanFrom: Philippe Schenker <[email protected]>
[ Upstream commit 6dd1de12e1243f2013e4fabf31e99e63b1a860d0 ]
The Lontium LT8912 does have a setting for DVI or HDMI. This patch reads from EDID what the display needs and sets it accordingly.
--- drivers/gpu/drm/bridge/lontium-lt8912b.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/bridge/lontium-lt8912b.c +2 -0
@@ -321,6 +321,8 @@ static int lt8912_video_setup(struct lt8912 *lt) vsync_activehigh ? BIT(0) : 0); ret |=regmap_update_bits (lt->regmap[I2C_MAIN ],0xab ,BIT (1 ), hsync_activehigh ?BIT (1 ) :0 ); + ret |=regmap_update_bits (lt->regmap[I2C_MAIN ],0xb2 ,BIT (0 ), + lt->connector.display_info.is_hdmi ?BIT (0 ) :0 );return ret; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 52/83 drm/bridge: lt8912b: fix corrupted image output
In reply to Greg Kroah-HartmanFrom: Francesco Dolcini <[email protected]>
[ Upstream commit 051ad2788d35ca07aec8402542e5d38429f2426a ]
Correct I2C address for the register list in lt8912_write_lvds_config(), these registers are on the first I2C address (0x48), the current function is just writing garbage to the wrong registers and this creates multiple issues (artifacts and output completely corrupted) on some HDMI displays.
Correct I2C address comes from Lontium documentation and it is the one used on other out-of-tree LT8912B drivers [1].
[1] https://github.com/boundarydevices/linux/blob/boundary-imx_5.10.x_2.0.0/drivers/video/lt8912.c#L296
--- drivers/gpu/drm/bridge/lontium-lt8912b.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/bridge/lontium-lt8912b.c +1 -1
@@ -186,7 +186,7 @@ static int lt8912_write_lvds_config(struct lt8912 *lt) {0x03, 0xff}, }; -return regmap_multi_reg_write (lt->regmap[I2C_CEC_DSI ], seq,ARRAY_SIZE (seq)); +return regmap_multi_reg_write (lt->regmap[I2C_MAIN ], seq,ARRAY_SIZE (seq)); };static inline struct lt8912 *bridge_to_lt8912 (struct drm_bridge *b)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 53/83 Revert "drm: bridge: analogix/dp: add panel prepare/unprepare in suspend/resume time"
In reply to Greg Kroah-HartmanFrom: Brian Norris <[email protected]>
[ Upstream commit cc62d98bd56d45de4531844ca23913a15136c05b ]
This reverts commit 211f276ed3d96e964d2d1106a198c7f4a4b3f4c0.
For quite some time, core DRM helpers already ensure that any relevant connectors/CRTCs/etc. are disabled, as well as their associated components (e.g., bridges) when suspending the system. Thus, analogix_dp_bridge_{enable,disable}() already get called, which in turn call drm_panel_{prepare,unprepare}(). This makes these drm_panel_*() calls redundant.
Besides redundancy, there are a few problems with this handling:
(1) drm_panel_{prepare,unprepare}() are *not* reference-counted APIs and are not in general designed to be handled by multiple callers -- although some panel drivers have a coarse 'prepared' flag that mitigates some damage, at least. So at a minimum this is redundant and confusing, but in some cases, this could be actively harmful.
(2) The error-handling is a bit non-standard. We ignored errors in suspend(), but handled errors in resume(). And recently, people noticed that the clk handling is unbalanced in error paths, and getting *that* right is not actually trivial, given the current way errors are mostly ignored.
(3) In the particular way analogix_dp_{suspend,resume}() get used (e.g., in rockchip_dp_*(), as a late/early callback), we don't necessarily have a proper PM relationship between the DP/bridge device and the panel device. So while the DP bridge gets resumed, the panel's parent device (e.g., platform_device) may still be suspended, and so any prepare() calls may fail.
So remove the superfluous, possibly-harmful suspend()/resume() handling of panel state.
--- drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 13 ------------- 1 file changed, 13 deletions(-)
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c +0 -13
@@ -1860,12 +1860,6 @@ EXPORT_SYMBOL_GPL(analogix_dp_remove);int analogix_dp_suspend (struct analogix_dp_device *dp) {clk_disable_unprepare (dp->clock); - -if (dp->plat_data->panel) { -if (drm_panel_unprepare (dp->plat_data->panel)) -DRM_ERROR ("failed to turnoff the panel\n" ); - } -return 0 ; }EXPORT_SYMBOL_GPL (analogix_dp_suspend);
@@ -1880,13 +1874,6 @@ int analogix_dp_resume(struct analogix_dp_device *dp)return ret; } -if (dp->plat_data->panel) { -if (drm_panel_prepare (dp->plat_data->panel)) { -DRM_ERROR ("failed to setup the panel\n" ); -return -EBUSY ; - } - } -return 0 ; }EXPORT_SYMBOL_GPL (analogix_dp_resume);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 54/83 Input: melfas_mip4 - fix return value check in mip4_probe()
In reply to Greg Kroah-HartmanFrom: Yang Yingliang <[email protected]>
[ Upstream commit a54dc27bd25f20ee3ea2009584b3166d25178243 ]
devm_gpiod_get_optional() may return ERR_PTR(-EPROBE_DEFER), add a minus sign to fix it.
--- drivers/input/touchscreen/melfas_mip4.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/input/touchscreen/melfas_mip4.c +1 -1
@@ -1453,7 +1453,7 @@ static int mip4_probe(struct i2c_client *client, const struct i2c_device_id *id) "ce", GPIOD_OUT_LOW);if (IS_ERR (ts->gpio_ce)) { error =PTR_ERR (ts->gpio_ce); -if (error !=EPROBE_DEFER ) +if (error != -EPROBE_DEFER )dev_err (&client->dev,"Failed to get gpio: %d\n" , error);return error;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 55/83 gpio: mvebu: Fix check for pwm support on non-A8K platforms
In reply to Greg Kroah-HartmanFrom: Pali Rohár <[email protected]>
[ Upstream commit 4335417da2b8d6d9b2d4411b5f9e248e5bb2d380 ]
pwm support incompatible with Armada 80x0/70x0 API is not only in Armada 370, but also in Armada XP, 38x and 39x. So basically every non-A8K platform. Fix check for pwm support appropriately.
--- drivers/gpio/gpio-mvebu.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)
drivers/gpio/gpio-mvebu.c +6 -9
@@ -793,8 +793,12 @@ static int mvebu_pwm_probe(struct platform_device *pdev,u32 offset;u32 set; -if (of_device_is_compatible (mvchip->chip.of_node, -"marvell,armada-370-gpio" )) { +if (mvchip->soc_variant ==MVEBU_GPIO_SOC_VARIANT_A8K ) { +int ret =of_property_read_u32 (dev->of_node, +"marvell,pwm-offset" , &offset); +if (ret <0 ) +return 0 ; + }else {/* * There are only two sets of PWM configuration registers for * all the GPIO lines on those SoCs which this driver reserves
@@ -804,13 +808,6 @@ static int mvebu_pwm_probe(struct platform_device *pdev,if (!platform_get_resource_byname (pdev,IORESOURCE_MEM ,"pwm" ))return 0 ; offset =0 ; - }else if (mvchip->soc_variant ==MVEBU_GPIO_SOC_VARIANT_A8K ) { -int ret =of_property_read_u32 (dev->of_node, -"marvell,pwm-offset" , &offset); -if (ret <0 ) -return 0 ; - }else { -return 0 ; }if (IS_ERR (mvchip->clk))
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 56/83 usbnet: Fix memory leak in usbnet_disconnect()
In reply to Greg Kroah-HartmanFrom: Peilin Ye <[email protected]>
[ Upstream commit a43206156263fbaf1f2b7f96257441f331e91bb7 ]
Currently usbnet_disconnect() unanchors and frees all deferred URBs using usb_scuttle_anchored_urbs(), which does not free urb->context, causing a memory leak as reported by syzbot.
Use a usb_get_from_anchor() while loop instead, similar to what we did in commit 19cfe912c37b ("Bluetooth: btusb: Fix memory leak in play_deferred"). Also free urb->sg.
--- drivers/net/usb/usbnet.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/net/usb/usbnet.c +6 -1
@@ -1599,6 +1599,7 @@ void usbnet_disconnect (struct usb_interface *intf)struct usbnet *dev;struct usb_device *xdev;struct net_device *net; +struct urb *urb; dev =usb_get_intfdata (intf);usb_set_intfdata (intf,NULL );
@@ -1615,7 +1616,11 @@ void usbnet_disconnect (struct usb_interface *intf) net = dev->net;unregister_netdev (net); -usb_scuttle_anchored_urbs (&dev->deferred); +while ((urb =usb_get_from_anchor (&dev->deferred))) { +dev_kfree_skb (urb->context); +kfree (urb->sg); +usb_free_urb (urb); + }if (dev->driver_info->unbind) dev->driver_info->unbind (dev, intf);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 57/83 net: sched: act_ct: fix possible refcount leak in tcf_ct_init()
In reply to Greg Kroah-HartmanFrom: Hangyu Hua <[email protected]>
[ Upstream commit 6e23ec0ba92d426c77a73a9ccab16346e5e0ef49 ]
nf_ct_put need to be called to put the refcount got by tcf_ct_fill_params to avoid possible refcount leak when tcf_ct_flow_table_get fails.
--- net/sched/act_ct.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/sched/act_ct.c +4 -1
@@ -1306,7 +1306,7 @@ static int tcf_ct_init(struct net *net, struct nlattr *nla, err =tcf_ct_flow_table_get (params);if (err) - goto cleanup; + goto cleanup_params;spin_lock_bh (&c->tcf_lock); goto_ch =tcf_action_set_ctrlact (*a, parm->action, goto_ch);
@@ -1321,6 +1321,9 @@ static int tcf_ct_init(struct net *net, struct nlattr *nla,return res; +cleanup_params: +if (params->tmpl) +nf_ct_put (params->tmpl); cleanup:if (goto_ch)tcf_chain_put_by_act (goto_ch);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 58/83 cxgb4: fix missing unlock on ETHOFLD desc collect fail path
In reply to Greg Kroah-HartmanFrom: Rafael Mendonca <[email protected]>
[ Upstream commit c635ebe8d911a93bd849a9419b01a58783de76f1 ]
The label passed to the QDESC_GET for the ETHOFLD TXQ, RXQ, and FLQ, is the 'out' one, which skips the 'out_unlock' label, and thus doesn't unlock the 'uld_mutex' before returning. Additionally, since commit 5148e5950c67 ("cxgb4: add EOTID tracking and software context dump"), the access to these ETHOFLD hardware queues should be protected by the 'mqprio_mutex' instead.
--- .../net/ethernet/chelsio/cxgb4/cudbg_lib.c | 28 +++++++++++++------ 1 file changed, 19 insertions(+), 9 deletions(-)
drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.c +19 -9
@@ -14,6 +14,7 @@#include "cudbg_entity.h" #include "cudbg_lib.h" #include "cudbg_zlib.h" +#include "cxgb4_tc_mqprio.h" static const u32 t6_tp_pio_array[][IREG_NUM_ELEM ] = { {0x7e40 ,0x7e44 ,0x020 ,28 },/* t6_tp_pio_regs_20_to_3b */
@@ -3458,7 +3459,7 @@ int cudbg_collect_qdesc(struct cudbg_init *pdbg_init,for (i =0 ; i < utxq->ntxq; i++)QDESC_GET_TXQ (&utxq->uldtxq[i].q,cudbg_uld_txq_to_qtype (j), - out_unlock); + out_unlock_uld); } }
@@ -3475,7 +3476,7 @@ int cudbg_collect_qdesc(struct cudbg_init *pdbg_init,for (i =0 ; i < urxq->nrxq; i++)QDESC_GET_RXQ (&urxq->uldrxq[i].rspq,cudbg_uld_rxq_to_qtype (j), - out_unlock); + out_unlock_uld); }/* ULD FLQ */
@@ -3487,7 +3488,7 @@ int cudbg_collect_qdesc(struct cudbg_init *pdbg_init,for (i =0 ; i < urxq->nrxq; i++)QDESC_GET_FLQ (&urxq->uldrxq[i].fl,cudbg_uld_flq_to_qtype (j), - out_unlock); + out_unlock_uld); }/* ULD CIQ */
@@ -3500,29 +3501,34 @@ int cudbg_collect_qdesc(struct cudbg_init *pdbg_init,for (i =0 ; i < urxq->nciq; i++)QDESC_GET_RXQ (&urxq->uldrxq[base + i].rspq,cudbg_uld_ciq_to_qtype (j), - out_unlock); + out_unlock_uld); } } +mutex_unlock (&uld_mutex); + +if (!padap->tc_mqprio) + goto out; +mutex_lock (&padap->tc_mqprio->mqprio_mutex);/* ETHOFLD TXQ */ if (s->eohw_txq)for (i =0 ; i < s->eoqsets; i++)QDESC_GET_TXQ (&s->eohw_txq[i].q, -CUDBG_QTYPE_ETHOFLD_TXQ , out); +CUDBG_QTYPE_ETHOFLD_TXQ , out_unlock_mqprio);/* ETHOFLD RXQ and FLQ */ if (s->eohw_rxq) {for (i =0 ; i < s->eoqsets; i++)QDESC_GET_RXQ (&s->eohw_rxq[i].rspq, -CUDBG_QTYPE_ETHOFLD_RXQ , out); +CUDBG_QTYPE_ETHOFLD_RXQ , out_unlock_mqprio);for (i =0 ; i < s->eoqsets; i++)QDESC_GET_FLQ (&s->eohw_rxq[i].fl, -CUDBG_QTYPE_ETHOFLD_FLQ , out); +CUDBG_QTYPE_ETHOFLD_FLQ , out_unlock_mqprio); } -out_unlock: -mutex_unlock (&uld_mutex); +out_unlock_mqprio: +mutex_unlock (&padap->tc_mqprio->mqprio_mutex); out: qdesc_info->qdesc_entry_size =sizeof (*qdesc_entry);
@@ -3559,6 +3565,10 @@ int cudbg_collect_qdesc(struct cudbg_init *pdbg_init,#undef QDESC_GETreturn rc; + +out_unlock_uld: +mutex_unlock (&uld_mutex); + goto out; } int cudbg_collect_flash(struct cudbg_init *pdbg_init,
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 59/83 net/mlxbf_gige: Fix an IS_ERR() vs NULL bug in mlxbf_gige_mdio_probe
In reply to Greg Kroah-HartmanFrom: Peng Wu <[email protected]>
[ Upstream commit 4774db8dfc6a2e6649920ebb2fc8e2f062c2080d ]
The devm_ioremap() function returns NULL on error, it doesn't return error pointers.
--- drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_mdio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_mdio.c +2 -2
@@ -244,8 +244,8 @@ int mlxbf_gige_mdio_probe(struct platform_device *pdev, struct mlxbf_gige *priv) } priv->clk_io =devm_ioremap (dev, res->start,resource_size (res)); -if (IS_ERR (priv->clk_io)) -return PTR_ERR (priv->clk_io); +if (!priv->clk_io) +return -ENOMEM ;mlxbf_gige_mdio_cfg (priv);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 60/83 nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
In reply to Greg Kroah-HartmanFrom: Michael Kelley <[email protected]>
[ Upstream commit c292a337d0e45a292c301e3cd51c35aa0ae91e95 ]
The IOC_PR_CLEAR and IOC_PR_RELEASE ioctls are non-functional on NVMe devices because the nvme_pr_clear() and nvme_pr_release() functions set the IEKEY field incorrectly. The IEKEY field should be set only when the key is zero (i.e, not specified). The current code does it backwards.
Furthermore, the NVMe spec describes the persistent reservation "clear" function as an option on the reservation release command. The current implementation of nvme_pr_clear() erroneously uses the reservation register command.
Fix these errors. Note that NVMe version 1.3 and later specify that setting the IEKEY field will return an error of Invalid Field in Command. The fix will set IEKEY when the key is zero, which is appropriate as these ioctls consider a zero key to be "unspecified", and the intention of the spec change is to require a valid key.
Tested on a version 1.4 PCI NVMe device in an Azure VM.
--- drivers/nvme/host/core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/nvme/host/core.c +3 -3
@@ -2056,14 +2056,14 @@ static int nvme_pr_preempt(struct block_device *bdev, u64 old, u64 new,static int nvme_pr_clear (struct block_device *bdev,u64 key) { -u32 cdw10 =1 | (key ?1 <<3 :0 ); +u32 cdw10 =1 | (key ?0 :1 <<3 ); -return nvme_pr_command (bdev, cdw10, key,0 , nvme_cmd_resv_register); +return nvme_pr_command (bdev, cdw10, key,0 , nvme_cmd_resv_release); }static int nvme_pr_release (struct block_device *bdev,u64 key,enum pr_type type) { -u32 cdw10 =nvme_pr_type (type) <<8 | (key ?1 <<3 :0 ); +u32 cdw10 =nvme_pr_type (type) <<8 | (key ?0 :1 <<3 );return nvme_pr_command (bdev, cdw10, key,0 , nvme_cmd_resv_release); }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 61/83 wifi: mac80211: fix regression with non-QoS drivers
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
[ Upstream commit d873697ef2b7e1b6fdd8e9d449d9354bd5d29a4a ]
Commit 10cb8e617560 ("mac80211: enable QoS support for nl80211 ctrl port") changed ieee80211_tx_control_port() to aways call __ieee80211_select_queue() without checking local->hw.queues.
__ieee80211_select_queue() returns a queue-id between 0 and 3, which means that now ieee80211_tx_control_port() may end up setting the queue-mapping for a skb to a value higher then local->hw.queues if local->hw.queues is less then 4.
Specifically this is a problem for ralink rt2500-pci cards where local->hw.queues is 2. There this causes rt2x00queue_get_tx_queue() to return NULL and the following error to be logged: "ieee80211 phy0:rt2x00mac_tx: Error - Attempt to send packet over invalid queue 2", after which association with the AP fails.
Other callers of __ieee80211_select_queue() skip calling it when local->hw.queues < IEEE80211_NUM_ACS, add the same check to ieee80211_tx_control_port(). This fixes ralink rt2500-pci and similar cards when less then 4 tx-queues no longer working.
--- net/mac80211/tx.c | 4 ++++ 1 file changed, 4 insertions(+)
net/mac80211/tx.c +4 -0
@@ -5719,6 +5719,9 @@ int ieee80211_tx_control_port(struct wiphy *wiphy, struct net_device *dev,skb_reset_network_header (skb);skb_reset_mac_header (skb); +if (local->hw.queues <IEEE80211_NUM_ACS ) + goto start_xmit; +/* update QoS header to prioritize control port frames if possible, * priorization also happens for control port frames send over * AF_PACKET
@@ -5734,6 +5737,7 @@ int ieee80211_tx_control_port(struct wiphy *wiphy, struct net_device *dev,rcu_read_unlock (); +start_xmit:/* mutex lock is only needed for incrementing the cookie counter */ mutex_lock (&local->mtx);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 62/83 net: stmmac: power up/down serdes in stmmac_open/release
In reply to Greg Kroah-HartmanFrom: Junxiao Chang <[email protected]>
[ Upstream commit 49725ffc15fc4e9fae68c55b691fd25168cbe5c1 ]
This commit fixes DMA engine reset timeout issue in suspend/resume with ADLink I-Pi SMARC Plus board which dmesg shows:
...
[ 54.678271] PM: suspend exit [ 54.754066] intel-eth-pci 0000:00:1d.2 enp0s29f2: PHY [stmmac-3:01] driver [Maxlinear Ethernet GPY215B] (irq=POLL) [ 54.755808] intel-eth-pci 0000:00:1d.2 enp0s29f2: Register MEM_TYPE_PAGE_POOL RxQ-0 ... [ 54.780482] intel-eth-pci 0000:00:1d.2 enp0s29f2: Register MEM_TYPE_PAGE_POOL RxQ-7 [ 55.784098] intel-eth-pci 0000:00:1d.2: Failed to reset the dma [ 55.784111] intel-eth-pci 0000:00:1d.2 enp0s29f2: stmmac_hw_setup: DMA engine initialization failed [ 55.784115] intel-eth-pci 0000:00:1d.2 enp0s29f2: stmmac_open: Hw setup failed
...
The issue is related with serdes which impacts clock. There is serdes in ADLink I-Pi SMARC board ethernet controller. Please refer to commit b9663b7ca6ff78 ("net: stmmac: Enable SERDES power up/down sequence") for detial. When issue is reproduced, DMA engine clock is not ready because serdes is not powered up.
To reproduce DMA engine reset timeout issue with hardware which has serdes in GBE controller, install Ubuntu. In Ubuntu GUI, click "Power Off/Log Out" -> "Suspend" menu, it disables network interface, then goes to sleep mode. When it wakes up, it enables network interface again. Stmmac driver is called in this way:
1. stmmac_release: Stop network interface. In this function, it disables DMA engine and network interface;
2. stmmac_suspend: It is called in kernel suspend flow. But because network interface has been disabled(netif_running(ndev) is false), it does nothing and returns directly;
3. System goes into S3 or S0ix state. Some time later, system is waken up by keyboard or mouse;
4. stmmac_resume: It does nothing because network interface has been disabled;
5. stmmac_open: It is called to enable network interace again. DMA engine is initialized in this API, but serdes is not power on so there will be DMA engine reset timeout issue.
Similarly, serdes powerdown should be added in stmmac_release. Network interface might be disabled by cmd "ifconfig eth0 down", DMA engine, phy and mac have been disabled in ndo_stop callback, serdes should be powered down as well. It doesn't make sense that serdes is on while other components have been turned off.
If ethernet interface is in enabled state(netif_running(ndev) is true) before suspend/resume, the issue couldn't be reproduced because serdes could be powered up in stmmac_resume.
Because serdes_powerup is added in stmmac_open, it doesn't need to be called in probe function.
--- .../net/ethernet/stmicro/stmmac/stmmac_main.c | 23 +++++++++++-------- 1 file changed, 13 insertions(+), 10 deletions(-)
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c +13 -10
@@ -3757,6 +3757,15 @@ static int stmmac_open(struct net_device *dev) goto init_error; } +if (priv->plat->serdes_powerup) { + ret = priv->plat->serdes_powerup (dev, priv->plat->bsp_priv); +if (ret <0 ) { +netdev_err (priv->dev,"%s: Serdes powerup failed\n" , + __func__); + goto init_error; + } + } + ret =stmmac_hw_setup (dev, true);if (ret <0 ) {netdev_err (priv->dev,"%s: Hw setup failed\n" , __func__);
@@ -3846,6 +3855,10 @@ static int stmmac_release(struct net_device *dev)/* Disable the MAC Rx/Tx */ stmmac_mac_set (priv, priv->ioaddr, false); +/* Powerdown Serdes if there is */ +if (priv->plat->serdes_powerdown) + priv->plat->serdes_powerdown (dev, priv->plat->bsp_priv); +netif_carrier_off (dev);stmmac_release_ptp (priv);
@@ -7224,14 +7237,6 @@ int stmmac_dvr_probe(struct device *device, goto error_netdev_register; } -if (priv->plat->serdes_powerup) { - ret = priv->plat->serdes_powerup (ndev, - priv->plat->bsp_priv); - -if (ret <0 ) - goto error_serdes_powerup; - } -#ifdef CONFIG_DEBUG_FS stmmac_init_fs (ndev);#endif
@@ -7246,8 +7251,6 @@ int stmmac_dvr_probe(struct device *device,return ret; -error_serdes_powerup: -unregister_netdev (ndev); error_netdev_register:phylink_destroy (priv->phylink); error_xpcs_setup:
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 63/83 net: phy: Dont WARN for PHY_UP state in mdio_bus_phy_resume()
In reply to Greg Kroah-HartmanFrom: Lukas Wunner <[email protected]>
[ Upstream commit ea64cdfad124922c931633e39287c5a31a9b14a1 ]
Commit 744d23c71af3 ("net: phy: Warn about incorrect mdio_bus_phy_resume() state") introduced a WARN() on resume from system sleep if a PHY is not in PHY_HALTED state.
Commit 6dbe852c379f ("net: phy: Don't WARN for PHY_READY state in mdio_bus_phy_resume()") added an exemption for PHY_READY state from the WARN().
It turns out PHY_UP state needs to be exempted as well because the following may happen on suspend:
mdio_bus_phy_suspend()
phy_stop_machine()
phydev->state = PHY_UP # if (phydev->state >= PHY_UP)--- drivers/net/phy/phy_device.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/net/phy/phy_device.c +6 -4
@@ -315,11 +315,13 @@ static __maybe_unused int mdio_bus_phy_resume(struct device *dev) phydev->suspended_by_mdio_bus =0 ; -/* If we manged to get here with the PHY state machine in a state neither -* PHY_HALTED nor PHY_READY this is an indication that something went wrong -* and we should most likely be using MAC managed PM and we are not. +/* If we managed to get here with the PHY state machine in a state +* neither PHY_HALTED, PHY_READY nor PHY_UP, this is an indication +* that something went wrong and we should most likely be using +* MAC managed PM, but we are not. */ -WARN_ON (phydev->state !=PHY_HALTED && phydev->state !=PHY_READY ); +WARN_ON (phydev->state !=PHY_HALTED && phydev->state !=PHY_READY && + phydev->state !=PHY_UP ); ret =phy_init_hw (phydev);if (ret <0 )
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 64/83 selftests: Fix the if conditions of in test_extra_filter()
In reply to Greg Kroah-HartmanFrom: Wang Yufen <[email protected]>
[ Upstream commit bc7a319844891746135dc1f34ab9df78d636a3ac ]
The socket 2 bind the addr in use, bind should fail with EADDRINUSE. So if bind success or errno != EADDRINUSE, testcase should be failed.
--- tools/testing/selftests/net/reuseport_bpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/net/reuseport_bpf.c +1 -1
@@ -330,7 +330,7 @@ static void test_extra_filter(const struct test_params p)if (bind (fd1, addr,sockaddr_size ()))error (1 , errno,"failed to bind recv socket 1" ); -if (!bind (fd2, addr,sockaddr_size ()) && errno !=EADDRINUSE ) +if (!bind (fd2, addr,sockaddr_size ()) || errno !=EADDRINUSE )error (1 , errno,"bind socket 2 should fail with EADDRINUSE" );free (addr);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 65/83 vdpa/ifcvf: fix the calculation of queuepair
In reply to Greg Kroah-HartmanFrom: Angus Chen <[email protected]>
[ Upstream commit db5db1a00d0816207be3a0166fcb4f523eaf3b52 ]
The q_pair_id to address a queue pair in the lm bar should be calculated by queue_id / 2 rather than queue_id / nr_vring.
Message-Id: <[email protected]>
--- drivers/vdpa/ifcvf/ifcvf_base.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/vdpa/ifcvf/ifcvf_base.c +2 -2
@@ -327,7 +327,7 @@ u16 ifcvf_get_vq_state(struct ifcvf_hw *hw, u16 qid)u32 q_pair_id; ifcvf_lm = (struct ifcvf_lm_cfg __iomem *)hw->lm_cfg; - q_pair_id = qid / hw->nr_vring; + q_pair_id = qid /2 ; avail_idx_addr = &ifcvf_lm->vring_lm_cfg[q_pair_id].idx_addr[qid %2 ]; last_avail_idx =ifc_ioread16 (avail_idx_addr);
@@ -341,7 +341,7 @@ int ifcvf_set_vq_state(struct ifcvf_hw *hw, u16 qid, u16 num)u32 q_pair_id; ifcvf_lm = (struct ifcvf_lm_cfg __iomem *)hw->lm_cfg; - q_pair_id = qid / hw->nr_vring; + q_pair_id = qid /2 ; avail_idx_addr = &ifcvf_lm->vring_lm_cfg[q_pair_id].idx_addr[qid %2 ]; hw->vring[qid].last_avail_idx = num;ifc_iowrite16 (num, avail_idx_addr);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 66/83 fs: split off setxattr_copy and do_setxattr function from setxattr
In reply to Greg Kroah-HartmanFrom: Stefan Roesch <[email protected]>
[ Upstream commit 1a91794ce8481a293c5ef432feb440aee1455619 ]
This splits of the setup part of the function setxattr in its own dedicated function called setxattr_copy. In addition it also exposes a new function called do_setxattr for making the setxattr call.
This makes it possible to call these two functions from io_uring in the processing of an xattr request.
Stable-dep-of: 06bbaa6dc53c ("[coredump] don't use __kernel_write() on kmap_local_page()")
--- fs/internal.h | 24 +++++++++++++++ fs/xattr.c | 84 ++++++++++++++++++++++++++++++++++++--------------- 2 files changed, 83 insertions(+), 25 deletions(-)
fs/internal.h +24 -0
@@ -195,3 +195,27 @@ long splice_file_to_pipe(struct file *in,struct pipe_inode_info *opipe, loff_t *offset, size_t len, unsigned int flags); + +/* +* fs/xattr.c: +*/ +struct xattr_name { +char name[XATTR_NAME_MAX +1 ]; +}; + +struct xattr_ctx { +/* Value of attribute */ +union { +const void __user *cvalue; +void __user *value; + }; +void *kvalue; +size_t size; +/* Attribute name */ +struct xattr_name *kname; +unsigned int flags; +}; + +int setxattr_copy (const char __user *name,struct xattr_ctx *ctx); +int do_setxattr (struct user_namespace *mnt_userns,struct dentry *dentry, +struct xattr_ctx *ctx);
fs/xattr.c +59 -25
109 lines not on this page · raw message
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 67/83 dont use __kernel_write() on kmap_local_page()
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
[ Upstream commit 06bbaa6dc53cb72040db952053432541acb9adc7 ]
passing kmap_local_page() result to __kernel_write() is unsafe - random ->write_iter() might (and 9p one does) get unhappy when passed ITER_KVEC with pointer that came from kmap_local_page().
Fix by providing a variant of __kernel_write() that takes an iov_iter from caller (__kernel_write() becomes a trivial wrapper) and adding dump_emit_page() that parallels dump_emit(), except that instead of __kernel_write() it uses __kernel_write_iter() with ITER_BVEC source.
--- fs/coredump.c | 38 +++++++++++++++++++++++++++++++++----- fs/internal.h | 3 +++ fs/read_write.c | 22 ++++++++++++++-------- 3 files changed, 50 insertions(+), 13 deletions(-)
fs/coredump.c +33 -5
@@ -902,6 +902,38 @@ static int __dump_skip(struct coredump_params *cprm, size_t nr) } } +static int dump_emit_page (struct coredump_params *cprm,struct page *page) +{ +struct bio_vec bvec = { + .bv_page = page, + .bv_offset =0 , + .bv_len =PAGE_SIZE , + }; +struct iov_iter iter; +struct file *file = cprm->file; +loff_t pos = file->f_pos; +ssize_t n; + +if (cprm->to_skip) { +if (!__dump_skip (cprm, cprm->to_skip)) +return 0 ; + cprm->to_skip =0 ; + } +if (cprm->written +PAGE_SIZE > cprm->limit) +return 0 ; +if (dump_interrupted ()) +return 0 ; +iov_iter_bvec (&iter,WRITE , &bvec,1 ,PAGE_SIZE ); + n =__kernel_write_iter (cprm->file, &iter, &pos); +if (n !=PAGE_SIZE ) +return 0 ; + file->f_pos = pos; + cprm->written +=PAGE_SIZE ; + cprm->pos +=PAGE_SIZE ; + +return 1 ; +} +int dump_emit (struct coredump_params *cprm,const void *addr,int nr) {if (cprm->to_skip) {
@@ -933,7 +965,6 @@ int dump_user_range(struct coredump_params *cprm, unsigned long start,for (addr = start; addr < start + len; addr +=PAGE_SIZE ) {struct page *page; -int stop;/* * To avoid having to allocate page tables for virtual address
@@ -944,10 +975,7 @@ int dump_user_range(struct coredump_params *cprm, unsigned long start,*/ page =get_dump_page (addr);if (page) { -void *kaddr =kmap_local_page (page); - - stop = !dump_emit (cprm, kaddr,PAGE_SIZE ); -kunmap_local (kaddr); +int stop = !dump_emit_page (cprm, page);put_page (page);if (stop)return 0 ;
fs/internal.h +3 -0
@@ -16,6 +16,7 @@ struct shrink_control;struct fs_context ;struct user_namespace ;struct pipe_inode_info ; +struct iov_iter ;/* * block/bdev.c
@@ -219,3 +220,5 @@ struct xattr_ctx {int setxattr_copy (const char __user *name,struct xattr_ctx *ctx);int do_setxattr (struct user_namespace *mnt_userns,struct dentry *dentry,struct xattr_ctx *ctx); + +ssize_t __kernel_write_iter (struct file *file,struct iov_iter *from,loff_t *pos);
fs/read_write.c +14 -8
@@ -512,14 +512,9 @@ static ssize_t new_sync_write(struct file *filp, const char __user *buf, size_t }/* caller is responsible for file_start_write/file_end_write */ -ssize_t __kernel_write (struct file *file,const void *buf,size_t count,loff_t *pos) +ssize_t __kernel_write_iter (struct file *file,struct iov_iter *from,loff_t *pos) { -struct kvec iov = { - .iov_base = (void *)buf, - .iov_len =min_t (size_t, count,MAX_RW_COUNT ), - };struct kiocb kiocb; -struct iov_iter iter;ssize_t ret;if (WARN_ON_ONCE (!(file->f_mode &FMODE_WRITE )))
@@ -535,8 +530,7 @@ ssize_t __kernel_write(struct file *file, const void *buf, size_t count, loff_tinit_sync_kiocb (&kiocb, file); kiocb.ki_pos = pos ? *pos :0 ; -iov_iter_kvec (&iter,WRITE , &iov,1 , iov.iov_len); - ret = file->f_op->write_iter (&kiocb, &iter); + ret = file->f_op->write_iter (&kiocb, from);if (ret >0 ) {if (pos) *pos = kiocb.ki_pos;
@@ -546,6 +540,18 @@ ssize_t __kernel_write(struct file *file, const void *buf, size_t count, loff_tinc_syscw (current);return ret; } + +/* caller is responsible for file_start_write/file_end_write */ +ssize_t __kernel_write (struct file *file,const void *buf,size_t count,loff_t *pos) +{ +struct kvec iov = { + .iov_base = (void *)buf, + .iov_len =min_t (size_t, count,MAX_RW_COUNT ), + }; +struct iov_iter iter; +iov_iter_kvec (&iter,WRITE , &iov,1 , iov.iov_len); +return __kernel_write_iter (file, &iter, pos); +}/* * This "EXPORT_SYMBOL_GPL()" is more of a "EXPORT_SYMBOL_DONTUSE()", * but autofs is one of the few internal kernel users that actually
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 68/83 clk: imx: imx6sx: remove the SET_RATE_PARENT flag for QSPI clocks
In reply to Greg Kroah-HartmanFrom: Han Xu <[email protected]>
[ Upstream commit b1ff1bfe81e763420afd5f3f25f0b3cbfd97055c ]
There is no dedicate parent clock for QSPI so SET_RATE_PARENT flag should not be used. For instance, the default parent clock for QSPI is pll2_bus, which is also the parent clock for quite a few modules, such as MMDC, once GPMI NAND set clock rate for EDO5 mode can cause system hang due to pll2_bus rate changed.
--- drivers/clk/imx/clk-imx6sx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/clk/imx/clk-imx6sx.c +2 -2
@@ -280,13 +280,13 @@ static void __init imx6sx_clocks_init(struct device_node *ccm_node) hws[IMX6SX_CLK_SSI3_SEL ] =imx_clk_hw_mux ("ssi3_sel" , base +0x1c ,14 ,2 , ssi_sels,ARRAY_SIZE (ssi_sels)); hws[IMX6SX_CLK_SSI2_SEL ] =imx_clk_hw_mux ("ssi2_sel" , base +0x1c ,12 ,2 , ssi_sels,ARRAY_SIZE (ssi_sels)); hws[IMX6SX_CLK_SSI1_SEL ] =imx_clk_hw_mux ("ssi1_sel" , base +0x1c ,10 ,2 , ssi_sels,ARRAY_SIZE (ssi_sels)); - hws[IMX6SX_CLK_QSPI1_SEL ] =imx_clk_hw_mux_flags ("qspi1_sel" , base +0x1c ,7 ,3 , qspi1_sels,ARRAY_SIZE (qspi1_sels),CLK_SET_RATE_PARENT ); + hws[IMX6SX_CLK_QSPI1_SEL ] =imx_clk_hw_mux ("qspi1_sel" , base +0x1c ,7 ,3 , qspi1_sels,ARRAY_SIZE (qspi1_sels)); hws[IMX6SX_CLK_PERCLK_SEL ] =imx_clk_hw_mux ("perclk_sel" , base +0x1c ,6 ,1 , perclk_sels,ARRAY_SIZE (perclk_sels)); hws[IMX6SX_CLK_VID_SEL ] =imx_clk_hw_mux ("vid_sel" , base +0x20 ,21 ,3 , vid_sels,ARRAY_SIZE (vid_sels)); hws[IMX6SX_CLK_ESAI_SEL ] =imx_clk_hw_mux ("esai_sel" , base +0x20 ,19 ,2 , audio_sels,ARRAY_SIZE (audio_sels)); hws[IMX6SX_CLK_CAN_SEL ] =imx_clk_hw_mux ("can_sel" , base +0x20 ,8 ,2 , can_sels,ARRAY_SIZE (can_sels)); hws[IMX6SX_CLK_UART_SEL ] =imx_clk_hw_mux ("uart_sel" , base +0x24 ,6 ,1 , uart_sels,ARRAY_SIZE (uart_sels)); - hws[IMX6SX_CLK_QSPI2_SEL ] =imx_clk_hw_mux_flags ("qspi2_sel" , base +0x2c ,15 ,3 , qspi2_sels,ARRAY_SIZE (qspi2_sels),CLK_SET_RATE_PARENT ); + hws[IMX6SX_CLK_QSPI2_SEL ] =imx_clk_hw_mux ("qspi2_sel" , base +0x2c ,15 ,3 , qspi2_sels,ARRAY_SIZE (qspi2_sels)); hws[IMX6SX_CLK_SPDIF_SEL ] =imx_clk_hw_mux ("spdif_sel" , base +0x30 ,20 ,2 , audio_sels,ARRAY_SIZE (audio_sels)); hws[IMX6SX_CLK_AUDIO_SEL ] =imx_clk_hw_mux ("audio_sel" , base +0x30 ,7 ,2 , audio_sels,ARRAY_SIZE (audio_sels)); hws[IMX6SX_CLK_ENET_PRE_SEL ] =imx_clk_hw_mux ("enet_pre_sel" , base +0x34 ,15 ,3 , enet_pre_sels,ARRAY_SIZE (enet_pre_sels));
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 69/83 clk: iproc: Do not rely on node name for correct PLL setup
In reply to Greg Kroah-HartmanFrom: Florian Fainelli <[email protected]>
[ Upstream commit 1b24a132eba7a1c19475ba2510ec1c00af3ff914 ]
After commit 31fd9b79dc58 ("ARM: dts: BCM5301X: update CRU block description") a warning from clk-iproc-pll.c was generated due to a duplicate PLL name as well as the console stopped working. Upon closer inspection it became clear that iproc_pll_clk_setup() used the Device Tree node unit name as an unique identifier as well as a parent name to parent all clocks under the PLL.
BCM5301X was the first platform on which that got noticed because of the DT node unit name renaming but the same assumptions hold true for any user of the iproc_pll_clk_setup() function.
The first 'clock-output-names' property is always guaranteed to be unique as well as providing the actual desired PLL clock name, so we utilize that to register the PLL and as a parent name of all children clock.
--- drivers/clk/bcm/clk-iproc-pll.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
drivers/clk/bcm/clk-iproc-pll.c +8 -4
@@ -736,6 +736,7 @@ void iproc_pll_clk_setup(struct device_node *node,const char *parent_name;struct iproc_clk *iclk_array;struct clk_hw_onecell_data *clk_data; +const char *clk_name;if (WARN_ON (!pll_ctrl) ||WARN_ON (!clk_ctrl))return ;
@@ -783,7 +784,12 @@ void iproc_pll_clk_setup(struct device_node *node, iclk = &iclk_array[0 ]; iclk->pll = pll; - init.name = node->name; + ret =of_property_read_string_index (node,"clock-output-names" , +0 , &clk_name); +if (WARN_ON (ret)) + goto err_pll_register; + + init.name = clk_name; init.ops = &iproc_pll_ops; init.flags =0 ; parent_name =of_clk_get_parent_name (node,0 );
@@ -803,13 +809,11 @@ void iproc_pll_clk_setup(struct device_node *node, goto err_pll_register; clk_data->hws[0 ] = &iclk->hw; + parent_name = clk_name;/* now initialize and register all leaf clocks */ for (i =1 ; i < num_clks; i++) { -const char *clk_name; -memset (&init,0 ,sizeof (init)); - parent_name = node->name; ret =of_property_read_string_index (node,"clock-output-names" , i, &clk_name);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 70/83 KVM: x86: Hide IA32_PLATFORM_DCA_CAP[31:0] from the guest
In reply to Greg Kroah-HartmanFrom: Jim Mattson <[email protected]>
[ Upstream commit aae2e72229cdb21f90df2dbe4244c977e5d3265b ]
The only thing reported by CPUID.9 is the value of IA32_PLATFORM_DCA_CAP[31:0] in EAX. This MSR doesn't even exist in the guest, since CPUID.1:ECX.DCA[bit 18] is clear in the guest.
Clear CPUID.9 in KVM_GET_SUPPORTED_CPUID.
Message-Id: <[email protected]>
--- arch/x86/kvm/cpuid.c | 2 -- 1 file changed, 2 deletions(-)
arch/x86/kvm/cpuid.c +0 -2
@@ -718,8 +718,6 @@ static inline int __do_cpuid_func(struct kvm_cpuid_array *array, u32 function) entry->edx =0 ; }break ; -case 9 : -break ;case 0xa : {/* Architectural Performance Monitoring */ struct x86_pmu_capability cap;union cpuid10_eax eax;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 71/83 perf metric: Add documentation and rename a variable.
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
[ Upstream commit 68074811dfb9529bb7cade0e67d42c7f7bf209e6 ]
Documentation to make current functionality clearer.
Rename a variable called 'metric' to 'metric_name' as it can be ambiguous as to whether a string is the name of a metric or the expression.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/metricgroup.c | 59 ++++++++++++++++++++++++++++++++--- 1 file changed, 54 insertions(+), 5 deletions(-)
tools/perf/util/metricgroup.c +54 -5
@@ -772,13 +772,27 @@ int __weak arch_get_runtimeparam(struct pmu_event *pe __maybe_unused)struct metricgroup_add_iter_data {struct list_head *metric_list; -const char *metric; +const char *metric_name;struct expr_ids *ids;int *ret;bool *has_match;bool metric_no_group; }; +/** +* __add_metric - Add a metric to metric_list. +* @metric_list: The list the metric is added to. +* @pe: The pmu_event containing the metric to be added. +* @metric_no_group: Should events written to events be grouped "{}" or +* global. Grouping is the default but due to multiplexing the +* user may override. +* @runtime: A special argument for the parser only known at runtime. +* @mp: The pointer to a location holding the first metric added to metric +* list. It is initialized here if this is the first metric. +* @parent: The last entry in a linked list of metrics being +* added/resolved. This is maintained to detect recursion. +* @ids: Storage for parent list. +*/ static int __add_metric(struct list_head *metric_list, struct pmu_event *pe, bool metric_no_group,
@@ -1068,7 +1082,7 @@ static int metricgroup__add_metric_sys_event_iter(struct pmu_event *pe,struct metric *m =NULL ;int ret; -if (!match_pe_metric (pe, d->metric)) +if (!match_pe_metric (pe, d->metric_name))return 0 ; ret =add_metric (d->metric_list, pe, d->metric_no_group, &m,NULL , d->ids);
@@ -1087,7 +1101,22 @@ static int metricgroup__add_metric_sys_event_iter(struct pmu_event *pe,return ret; } -static int metricgroup__add_metric (const char *metric,bool metric_no_group, +/** +* metricgroup__add_metric - Find and add a metric, or a metric group. +* @metric_name: The name of the metric or metric group. For example, "IPC" +* could be the name of a metric and "TopDownL1" the name of a +* metric group. +* @metric_no_group: Should events written to events be grouped "{}" or +* global. Grouping is the default but due to multiplexing the +* user may override. +* @events: an out argument string of events that need to be parsed and +* associated with the metric. For example, the metric "IPC" would +* create an events string like "{instructions,cycles}:W". +* @metric_list: The list that the metric or metric group are added to. +* @map: The map that is searched for metrics, most commonly the table for the +* architecture perf is running upon. +*/ +static int metricgroup__add_metric (const char *metric_name,bool metric_no_group,struct strbuf *events,struct list_head *metric_list,struct pmu_events_map *map)
@@ -1099,7 +1128,11 @@ static int metricgroup__add_metric(const char *metric, bool metric_no_group,int i, ret;bool has_match = false; -map_for_each_metric (pe, i, map, metric) { +/* +* Iterate over all metrics seeing if metric matches either the name or +* group. When it does add the metric to the list. +*/ +map_for_each_metric (pe, i, map, metric_name) { has_match = true; m =NULL ;
@@ -1122,7 +1155,7 @@ static int metricgroup__add_metric(const char *metric, bool metric_no_group, .fn = metricgroup__add_metric_sys_event_iter, .data = (void *) &(struct metricgroup_add_iter_data ) { .metric_list = &list, - .metric = metric, + .metric_name = metric_name, .metric_no_group = metric_no_group, .ids = &ids, .has_match = &has_match,
@@ -1161,6 +1194,22 @@ static int metricgroup__add_metric(const char *metric, bool metric_no_group,return ret; } +/** +* metricgroup__add_metric_list - Find and add metrics, or metric groups, +* specified in a list. +* @list: the list of metrics or metric groups. For example, "IPC,CPI,TopDownL1" +* would match the IPC and CPI metrics, and TopDownL1 would match all +* the metrics in the TopDownL1 group. +* @metric_no_group: Should events written to events be grouped "{}" or +* global. Grouping is the default but due to multiplexing the +* user may override. +* @events: an out argument string of events that need to be parsed and +* associated with the metric. For example, the metric "IPC" would +* create an events string like "{instructions,cycles}:W". +* @metric_list: The list that metrics are added to. +* @map: The map that is searched for metrics, most commonly the table for the +* architecture perf is running upon. +*/ static int metricgroup__add_metric_list(const char *list, bool metric_no_group, struct strbuf *events, struct list_head *metric_list,
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 72/83 perf metric: Only add a referenced metric once
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
[ Upstream commit a3de76903dd0786a8661e9e6eb9054a7519e10e7 ]
If a metric references other metrics then the same other metrics may be referenced more than once, but the events and metric ref are only needed once.
An example of this is in tests/parse-metric.c where DCache_L2_Hits references the metric DCache_L2_All_Hits twice, once directly and once through DCache_L2_All.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/metricgroup.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
tools/perf/util/metricgroup.c +9 -3
@@ -836,12 +836,18 @@ static int __add_metric(struct list_head *metric_list, *mp = m; }else {/* -* We got here for the referenced metric, via the -* recursive metricgroup__add_metric call, add -* it to the parent group. +* This metric was referenced in a metric higher in the +* tree. Check if the same metric is already resolved in the +* metric_refs list. */ m = *mp; +list_for_each_entry (ref, &m->metric_refs, list) { +if (!strcmp (pe->metric_name, ref->metric_name)) +return 0 ; + } + +/*Add the new referenced metric to the pare the parent group. */ ref =malloc (sizeof (*ref));if (!ref)return -ENOMEM ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 73/83 perf parse-events: Add const to evsel name
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
[ Upstream commit 8e8bbfb311a26a17834f1839e15e2c29ea5e58c6 ]
The evsel name is strdup-ed before assignment and so can be const.
A later change will add another similar string.
Using const makes it clearer that these are not out arguments.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/parse-events-hybrid.c | 15 +++++++++------ tools/perf/util/parse-events-hybrid.h | 6 ++++-- tools/perf/util/parse-events.c | 15 ++++++++------- tools/perf/util/parse-events.h | 7 ++++--- tools/perf/util/pmu.c | 2 +- tools/perf/util/pmu.h | 2 +- 6 files changed, 27 insertions(+), 20 deletions(-)
tools/perf/util/parse-events-hybrid.c +9 -6
@@ -38,7 +38,7 @@ static void config_hybrid_attr(struct perf_event_attr *attr,static int create_event_hybrid (__u32 config_type,int *idx,struct list_head *list, -struct perf_event_attr *attr,char *name, +struct perf_event_attr *attr,const char *name,struct list_head *config_terms,struct perf_pmu *pmu) {
@@ -70,7 +70,7 @@ static int pmu_cmp(struct parse_events_state *parse_state,static int add_hw_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -char *name,struct list_head *config_terms) +const char *name,struct list_head *config_terms) {struct perf_pmu *pmu;int ret;
@@ -94,7 +94,8 @@ static int add_hw_hybrid(struct parse_events_state *parse_state, }static int create_raw_event_hybrid (int *idx,struct list_head *list, -struct perf_event_attr *attr,char *name, +struct perf_event_attr *attr, +const char *name,struct list_head *config_terms,struct perf_pmu *pmu) {
@@ -113,7 +114,7 @@ static int create_raw_event_hybrid(int *idx, struct list_head *list,static int add_raw_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -char *name,struct list_head *config_terms) +const char *name,struct list_head *config_terms) {struct perf_pmu *pmu;int ret;
@@ -138,7 +139,8 @@ static int add_raw_hybrid(struct parse_events_state *parse_state,int parse_events__add_numeric_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -char *name,struct list_head *config_terms, +const char *name, +struct list_head *config_terms,bool *hybrid) { *hybrid = false;
@@ -159,7 +161,8 @@ int parse_events__add_numeric_hybrid(struct parse_events_state *parse_state, }int parse_events__add_cache_hybrid (struct list_head *list,int *idx, -struct perf_event_attr *attr,char *name, +struct perf_event_attr *attr, +const char *name,struct list_head *config_terms,bool *hybrid,struct parse_events_state *parse_state)
tools/perf/util/parse-events-hybrid.h +4 -2
@@ -11,11 +11,13 @@int parse_events__add_numeric_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -char *name,struct list_head *config_terms, +const char *name, +struct list_head *config_terms,bool *hybrid);int parse_events__add_cache_hybrid (struct list_head *list,int *idx, -struct perf_event_attr *attr,char *name, +struct perf_event_attr *attr, +const char *name,struct list_head *config_terms,bool *hybrid,struct parse_events_state *parse_state);
tools/perf/util/parse-events.c +8 -7
@@ -347,7 +347,7 @@ static int parse_events__is_name_term(struct parse_events_term *term)return term->type_term ==PARSE_EVENTS__TERM_TYPE_NAME ; } -static char *get_config_name (struct list_head *head_terms) +static const char *get_config_name (struct list_head *head_terms) {struct parse_events_term *term;
@@ -365,7 +365,7 @@ static struct evsel * __add_event(struct list_head *list, int *idx, struct perf_event_attr *attr, bool init_attr, - char *name, struct perf_pmu *pmu, + const char *name, struct perf_pmu *pmu, struct list_head *config_terms, bool auto_merge_stats, const char *cpu_list) {
@@ -404,14 +404,14 @@ __add_event(struct list_head *list, int *idx, }struct evsel *parse_events__add_event (int idx,struct perf_event_attr *attr, -char *name,struct perf_pmu *pmu) +const char *name,struct perf_pmu *pmu) {return __add_event (NULL , &idx, attr, false, name, pmu,NULL , false,NULL ); }static int add_event (struct list_head *list,int *idx, -struct perf_event_attr *attr,char *name, +struct perf_event_attr *attr,const char *name,struct list_head *config_terms) { return __add_event(list, idx, attr, true, name, NULL, config_terms,
@@ -474,7 +474,8 @@ int parse_events_add_cache(struct list_head *list, int *idx, {struct perf_event_attr attr;LIST_HEAD (config_terms); -char name[MAX_NAME_LEN ], *config_name; +char name[MAX_NAME_LEN ]; +const char *config_name;int cache_type =-1 , cache_op =-1 , cache_result =-1 ;char *op_result[2 ] = { op_result1, op_result2 };int i, n, ret;
@@ -2038,7 +2039,7 @@ int parse_events__modifier_event(struct list_head *list, char *str, bool add)return 0 ; } -int parse_events_name (struct list_head *list,char *name) +int parse_events_name (struct list_head *list,const char *name) {struct evsel *evsel;
@@ -3295,7 +3296,7 @@ char *parse_events_formats_error_string(char *additional_terms)struct evsel *parse_events__add_event_hybrid (struct list_head *list,int *idx,struct perf_event_attr *attr, -char *name,struct perf_pmu *pmu, +const char *name,struct perf_pmu *pmu,struct list_head *config_terms) { return __add_event(list, idx, attr, true, name, pmu,
tools/perf/util/parse-events.h +4 -3
@@ -162,7 +162,7 @@ void parse_events_terms__purge(struct list_head *terms);void parse_events__clear_array (struct parse_events_array *a);int parse_events__modifier_event (struct list_head *list,char *str,bool add);int parse_events__modifier_group (struct list_head *list,char *event_mod); -int parse_events_name (struct list_head *list,char *name); +int parse_events_name (struct list_head *list,const char *name); int parse_events_add_tracepoint(struct list_head *list, int *idx, const char *sys, const char *event, struct parse_events_error *error,
@@ -200,7 +200,7 @@ int parse_events_add_pmu(struct parse_events_state *parse_state, bool use_alias);struct evsel *parse_events__add_event (int idx,struct perf_event_attr *attr, -char *name,struct perf_pmu *pmu); +const char *name,struct perf_pmu *pmu); int parse_events_multi_pmu_add(struct parse_events_state *parse_state, char *str,
@@ -267,7 +267,8 @@ int perf_pmu__test_parse_init(void);struct evsel *parse_events__add_event_hybrid (struct list_head *list,int *idx,struct perf_event_attr *attr, -char *name,struct perf_pmu *pmu, +const char *name, +struct perf_pmu *pmu,struct list_head *config_terms);#endif /* __PERF_PARSE_EVENTS_H */
tools/perf/util/pmu.c +1 -1
@@ -1906,7 +1906,7 @@ int perf_pmu__caps_parse(struct perf_pmu *pmu) }void perf_pmu__warn_invalid_config (struct perf_pmu *pmu,__u64 config, -char *name) +const char *name) {struct perf_pmu_format *format;__u64 masks =0 , bits;
tools/perf/util/pmu.h +1 -1
@@ -134,7 +134,7 @@ int perf_pmu__convert_scale(const char *scale, char **end, double *sval);int perf_pmu__caps_parse (struct perf_pmu *pmu);void perf_pmu__warn_invalid_config (struct perf_pmu *pmu,__u64 config, -char *name); +const char *name);bool perf_pmu__has_hybrid (void );int perf_pmu__match (char *pattern,char *name,char *tok);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 74/83 perf parse-events: Add new "metric-id" term
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
[ Upstream commit 2b62b3a611715d3ca612e3225cf436277ed9648b ]
Add a new "metric-id" term to events so that metric parsing can set an ID that can be reliably looked up.
Metric parsing currently will turn a metric like "instructions/cycles" into a parse events string of "{instructions,cycles}:W".
However, parse-events may change "instructions" into "instructions:u" if perf_event_paranoid=2.
When this happens expr__resolve_id currently fails as stat-shadow adds the ID "instructions:u" to match with the counter value and the metric tries to look up the ID just "instructions".
A later patch will use the new term.
An example of the current problem:
$ echo -1 > /proc/sys/kernel/perf_event_paranoid $ perf stat -M IPC /bin/true Performance counter stats for '/bin/true':
1,217,161 inst_retired.any # 0.97 IPC
1,250,389 cpu_clk_unhalted.thread
0.002064773 seconds time elapsed
0.002378000 seconds user
0.000000000 seconds sys$ echo 2 > /proc/sys/kernel/perf_event_paranoid $ perf stat -M IPC /bin/true Performance counter stats for '/bin/true':
150,298 inst_retired.any:u # nan IPC
187,095 cpu_clk_unhalted.thread:u
0.002042731 seconds time elapsed
0.000000000 seconds user
0.002377000 seconds sysNote: nan IPC is printed as an effect of "perf metric: Use NAN for missing event IDs." but earlier versions of perf just fail with a parse error and display no value.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/evsel.c | 17 +++++ tools/perf/util/evsel.h | 2 + tools/perf/util/parse-events-hybrid.c | 25 ++++--- tools/perf/util/parse-events-hybrid.h | 4 +- tools/perf/util/parse-events.c | 95 ++++++++++++++++++--------- tools/perf/util/parse-events.h | 5 +- tools/perf/util/parse-events.l | 1 + tools/perf/util/pfm.c | 3 +- 8 files changed, 107 insertions(+), 45 deletions(-)
tools/perf/util/evsel.c +17 -0
@@ -410,6 +410,11 @@ struct evsel *evsel__clone(struct evsel *orig)if (evsel->filter ==NULL ) goto out_err; } +if (orig->metric_id) { + evsel->metric_id =strdup (orig->metric_id); +if (evsel->metric_id ==NULL ) + goto out_err; + } evsel->cgrp =cgroup__get (orig->cgrp); evsel->tp_format = orig->tp_format; evsel->handler = orig->handler;
@@ -779,6 +784,17 @@ const char *evsel__name(struct evsel *evsel)return "unknown" ; } +const char *evsel__metric_id (const struct evsel *evsel) +{ +if (evsel->metric_id) +return evsel->metric_id; + +if (evsel->core.attr.type ==PERF_TYPE_SOFTWARE && evsel->tool_event) +return "duration_time" ; + +return "unknown" ; +} +const char *evsel__group_name (struct evsel *evsel) {return evsel->group_name ?:"anon group" ;
@@ -1432,6 +1448,7 @@ void evsel__exit(struct evsel *evsel)zfree (&evsel->group_name);zfree (&evsel->name);zfree (&evsel->pmu_name); +zfree (&evsel->metric_id);evsel__zero_per_pkg (evsel);hashmap__free (evsel->per_pkg_mask); evsel->per_pkg_mask =NULL ;
tools/perf/util/evsel.h +2 -0
@@ -68,6 +68,7 @@ struct evsel {double scale;const char *unit;struct cgroup *cgrp; +const char *metric_id;enum perf_tool_event tool_event;/* parse modifier helper */ int exclude_GH;
@@ -261,6 +262,7 @@ bool evsel__match_bpf_counter_events(const char *name);int __evsel__hw_cache_type_op_res_name (u8 type,u8 op,u8 result,char *bf,size_t size);const char *evsel__name (struct evsel *evsel); +const char *evsel__metric_id (const struct evsel *evsel);const char *evsel__group_name (struct evsel *evsel);int evsel__group_desc (struct evsel *evsel,char *buf,size_t size);
tools/perf/util/parse-events-hybrid.c +15 -10
@@ -39,6 +39,7 @@ static void config_hybrid_attr(struct perf_event_attr *attr,static int create_event_hybrid (__u32 config_type,int *idx,struct list_head *list,struct perf_event_attr *attr,const char *name, +const char *metric_id,struct list_head *config_terms,struct perf_pmu *pmu) {
@@ -47,7 +48,7 @@ static int create_event_hybrid(__u32 config_type, int *idx,__u64 config = attr->config;config_hybrid_attr (attr, config_type, pmu->type); - evsel =parse_events__add_event_hybrid (list, idx, attr, name, + evsel =parse_events__add_event_hybrid (list, idx, attr, name, metric_id, pmu, config_terms);if (evsel) evsel->pmu_name =strdup (pmu->name);
@@ -70,7 +71,8 @@ static int pmu_cmp(struct parse_events_state *parse_state,static int add_hw_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -const char *name,struct list_head *config_terms) +const char *name,const char *metric_id, +struct list_head *config_terms) {struct perf_pmu *pmu;int ret;
@@ -84,7 +86,7 @@ static int add_hw_hybrid(struct parse_events_state *parse_state,copy_config_terms (&terms, config_terms); ret =create_event_hybrid (PERF_TYPE_HARDWARE , &parse_state->idx, list, attr, name, - &terms, pmu); + metric_id, &terms, pmu);free_config_terms (&terms);if (ret)return ret;
@@ -96,13 +98,14 @@ static int add_hw_hybrid(struct parse_events_state *parse_state,static int create_raw_event_hybrid (int *idx,struct list_head *list,struct perf_event_attr *attr,const char *name, +const char *metric_id,struct list_head *config_terms,struct perf_pmu *pmu) {struct evsel *evsel; attr->type = pmu->type; - evsel =parse_events__add_event_hybrid (list, idx, attr, name, + evsel =parse_events__add_event_hybrid (list, idx, attr, name, metric_id, pmu, config_terms);if (evsel) evsel->pmu_name =strdup (pmu->name);
@@ -114,7 +117,8 @@ static int create_raw_event_hybrid(int *idx, struct list_head *list,static int add_raw_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -const char *name,struct list_head *config_terms) +const char *name,const char *metric_id, +struct list_head *config_terms) {struct perf_pmu *pmu;int ret;
@@ -127,7 +131,7 @@ static int add_raw_hybrid(struct parse_events_state *parse_state,copy_config_terms (&terms, config_terms); ret =create_raw_event_hybrid (&parse_state->idx, list, attr, - name, &terms, pmu); + name, metric_id, &terms, pmu);free_config_terms (&terms);if (ret)return ret;
@@ -139,7 +143,7 @@ static int add_raw_hybrid(struct parse_events_state *parse_state,int parse_events__add_numeric_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -const char *name, +const char *name,const char *metric_id,struct list_head *config_terms,bool *hybrid) {
@@ -152,17 +156,18 @@ int parse_events__add_numeric_hybrid(struct parse_events_state *parse_state, *hybrid = true;if (attr->type !=PERF_TYPE_RAW ) { -return add_hw_hybrid (parse_state, list, attr, name, +return add_hw_hybrid (parse_state, list, attr, name, metric_id, config_terms); } -return add_raw_hybrid (parse_state, list, attr, name, +return add_raw_hybrid (parse_state, list, attr, name, metric_id, config_terms); }int parse_events__add_cache_hybrid (struct list_head *list,int *idx,struct perf_event_attr *attr,const char *name, +const char *metric_id,struct list_head *config_terms,bool *hybrid,struct parse_events_state *parse_state)
@@ -183,7 +188,7 @@ int parse_events__add_cache_hybrid(struct list_head *list, int *idx,copy_config_terms (&terms, config_terms); ret =create_event_hybrid (PERF_TYPE_HW_CACHE , idx, list, - attr, name, &terms, pmu); + attr, name, metric_id, &terms, pmu);free_config_terms (&terms);if (ret)return ret;
tools/perf/util/parse-events-hybrid.h +2 -2
@@ -11,13 +11,13 @@int parse_events__add_numeric_hybrid (struct parse_events_state *parse_state,struct list_head *list,struct perf_event_attr *attr, -const char *name, +const char *name,const char *metric_id,struct list_head *config_terms,bool *hybrid);int parse_events__add_cache_hybrid (struct list_head *list,int *idx,struct perf_event_attr *attr, -const char *name, +const char *name,const char *metric_id,struct list_head *config_terms,bool *hybrid,struct parse_events_state *parse_state);
tools/perf/util/parse-events.c +64 -31
216 lines not on this page · raw message
tools/perf/util/parse-events.h +4 -1
@@ -87,6 +87,7 @@ enum {PARSE_EVENTS__TERM_TYPE_PERCORE ,PARSE_EVENTS__TERM_TYPE_AUX_OUTPUT ,PARSE_EVENTS__TERM_TYPE_AUX_SAMPLE_SIZE , +PARSE_EVENTS__TERM_TYPE_METRIC_ID , __PARSE_EVENTS__TERM_TYPE_NR, };
@@ -200,7 +201,8 @@ int parse_events_add_pmu(struct parse_events_state *parse_state, bool use_alias);struct evsel *parse_events__add_event (int idx,struct perf_event_attr *attr, -const char *name,struct perf_pmu *pmu); +const char *name,const char *metric_id, +struct perf_pmu *pmu); int parse_events_multi_pmu_add(struct parse_events_state *parse_state, char *str,
@@ -268,6 +270,7 @@ int perf_pmu__test_parse_init(void);struct evsel *parse_events__add_event_hybrid (struct list_head *list,int *idx,struct perf_event_attr *attr,const char *name, +const char *metric_id,struct perf_pmu *pmu,struct list_head *config_terms);
tools/perf/util/parse-events.l +1 -0
@@ -295,6 +295,7 @@ no-overwrite { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_NOOVERWRITE); } percore { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_PERCORE); } aux-output { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_AUX_OUTPUT); } aux-sample-size { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_AUX_SAMPLE_SIZE); } +metric-id { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_METRIC_ID); } r{num_raw_hex} { return raw(yyscanner); } r0x{num_raw_hex} { return raw(yyscanner); } , { return ','; }
tools/perf/util/pfm.c +2 -1
@@ -87,7 +87,8 @@ int parse_libpfm_events_option(const struct option *opt, const char *str, pmu =perf_pmu__find_by_type ((unsigned int )attr.type); evsel =parse_events__add_event (evlist->core.nr_entries, - &attr, q, pmu); + &attr, q,/*metric_id=*/ NULL , + pmu);if (evsel ==NULL ) goto error;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 75/83 perf parse-events: Identify broken modifiers
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
[ Upstream commit eabd4523395e4a8f2b049165642801f2ab8ff893 ]
Previously the broken modifier causes a usage message to printed but nothing else.
After:
$ perf stat -e 'cycles:kk' -a sleep 2
event syntax error: 'cycles:kk'
\___ Bad modifier
Run 'perf list' for a list of valid eventsUsage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list available events
$ perf stat -e '{instructions,cycles}:kk' -a sleep 2
event syntax error: '..ns,cycles}:kk'
\___ Bad modifier
Run 'perf list' for a list of valid eventsUsage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list available events
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/parse-events.y | 10 ++++++++++ 1 file changed, 10 insertions(+)
tools/perf/util/parse-events.y +10 -0
@@ -183,6 +183,11 @@ group_def ':' PE_MODIFIER_EVENT err = parse_events__modifier_group(list, $3); free($3); if (err) { + struct parse_events_state *parse_state = _parse_state; + struct parse_events_error *error = parse_state->error; + + parse_events__handle_error(error, @3.first_column, + strdup("Bad modifier"), NULL); free_list_evsel(list); YYABORT; }
@@ -240,6 +245,11 @@ event_name PE_MODIFIER_EVENT err = parse_events__modifier_event(list, $2, false); free($2); if (err) { + struct parse_events_state *parse_state = _parse_state; + struct parse_events_error *error = parse_state->error; + + parse_events__handle_error(error, @2.first_column, + strdup("Bad modifier"), NULL); free_list_evsel(list); YYABORT; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 76/83 perf list: Display hybrid PMU events with cpu type
In reply to Greg Kroah-HartmanFrom: Jin Yao <[email protected]>
[ Upstream commit 0e0ae8742207c3b477cf0357b8115cec7b19612c ]
Add a new option '--cputype' to 'perf list' to display core-only PMU events or atom-only PMU events.
Each hybrid PMU event has been assigned with a PMU name, this patch compares the PMU name before listing the result.
For example:
perf list --cputype atom
...
cache:
core_reject_l2q.any
[Counts the number of request that were not accepted into the L2Q because the L2Q is FULL. Unit: cpu_atom]
...
The "Unit: cpu_atom" is displayed in the brief description section to indicate this is an atom event.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/Documentation/perf-list.txt | 4 +++ tools/perf/builtin-list.c | 42 ++++++++++++++++++-------- tools/perf/util/metricgroup.c | 7 ++++- tools/perf/util/metricgroup.h | 2 +- tools/perf/util/parse-events.c | 8 +++-- tools/perf/util/parse-events.h | 3 +- tools/perf/util/pmu.c | 29 +++++++++++++++--- tools/perf/util/pmu.h | 2 +- 8 files changed, 73 insertions(+), 24 deletions(-)
tools/perf/Documentation/perf-list.txt +4 -0
@@ -39,6 +39,10 @@ any extra expressions computed by perf stat. --deprecated:: Print deprecated events. By default the deprecated events are hidden. +--cputype:: +Print events applying cpu with this type for hybrid platform +(e.g. --cputype core or --cputype atom) + [[EVENT_MODIFIERS]] EVENT MODIFIERS ---------------
tools/perf/builtin-list.c +30 -12
102 lines not on this page · raw message
tools/perf/util/metricgroup.c +6 -1
@@ -11,6 +11,7 @@#include "evsel.h" #include "strbuf.h" #include "pmu.h" +#include "pmu-hybrid.h" #include "expr.h" #include "rblist.h" #include <string.h>
@@ -616,7 +617,7 @@ static int metricgroup__print_sys_event_iter(struct pmu_event *pe, void *data) }void metricgroup__print (bool metrics,bool metricgroups,char *filter, -bool raw,bool details) +bool raw,bool details,const char *pmu_name) {struct pmu_events_map *map =pmu_events_map__find ();struct pmu_event *pe;
@@ -642,6 +643,10 @@ void metricgroup__print(bool metrics, bool metricgroups, char *filter,break ;if (!pe->metric_expr)continue ; +if (pmu_name &&perf_pmu__is_hybrid (pe->pmu) && +strcmp (pmu_name, pe->pmu)) { +continue ; + }if (metricgroup__print_pmu_event (pe, metricgroups, filter, raw, details, &groups, metriclist) <0 )
tools/perf/util/metricgroup.h +1 -1
@@ -53,7 +53,7 @@ int metricgroup__parse_groups_test(struct evlist *evlist, struct rblist *metric_events);void metricgroup__print (bool metrics,bool groups,char *filter, -bool raw,bool details); +bool raw,bool details,const char *pmu_name);bool metricgroup__has_metric (const char *metric);int arch_get_runtimeparam (struct pmu_event *pe__maybe_unused );void metricgroup__rblist_exit (struct rblist *metric_events);
tools/perf/util/parse-events.c +5 -3
@@ -3034,7 +3034,8 @@ void print_symbol_events(const char *event_glob, unsigned type,* Print the help text for the event symbols: */ void print_events (const char *event_glob,bool name_only,bool quiet_flag, -bool long_desc,bool details_flag,bool deprecated) +bool long_desc,bool details_flag,bool deprecated, +const char *pmu_name) {print_symbol_events (event_glob,PERF_TYPE_HARDWARE , event_symbols_hw,PERF_COUNT_HW_MAX , name_only);
@@ -3046,7 +3047,7 @@ void print_events(const char *event_glob, bool name_only, bool quiet_flag,print_hwcache_events (event_glob, name_only);print_pmu_events (event_glob, name_only, quiet_flag, long_desc, - details_flag, deprecated); + details_flag, deprecated, pmu_name);if (event_glob !=NULL )return ;
@@ -3072,7 +3073,8 @@ void print_events(const char *event_glob, bool name_only, bool quiet_flag,print_sdt_events (NULL ,NULL , name_only); -metricgroup__print (true, true,NULL , name_only, details_flag); +metricgroup__print (true, true,NULL , name_only, details_flag, + pmu_name);print_libpfm_events (name_only, long_desc); }
tools/perf/util/parse-events.h +2 -1
@@ -221,7 +221,8 @@ void parse_events_evlist_error(struct parse_events_state *parse_state, int idx, const char *str);void print_events (const char *event_glob,bool name_only,bool quiet, -bool long_desc,bool details_flag,bool deprecated); +bool long_desc,bool details_flag,bool deprecated, +const char *pmu_name);struct event_symbol {const char *symbol;
tools/perf/util/pmu.c +24 -5
@@ -1608,6 +1608,7 @@ static int cmp_sevent(const void *a, const void *b) {const struct sevent *as = a;const struct sevent *bs = b; +int ret;/* Put extra events last */ if (!!as->desc != !!bs->desc)
@@ -1623,7 +1624,13 @@ static int cmp_sevent(const void *a, const void *b)if (as->is_cpu != bs->is_cpu)return bs->is_cpu - as->is_cpu; -return strcmp (as->name, bs->name); + ret =strcmp (as->name, bs->name); +if (!ret) { +if (as->pmu && bs->pmu) +return strcmp (as->pmu, bs->pmu); + } + +return ret; }static void wordwrap (char *s,int start,int max,int corr)
@@ -1653,7 +1660,8 @@ bool is_pmu_core(const char *name) }void print_pmu_events (const char *event_glob,bool name_only,bool quiet_flag, -bool long_desc,bool details_flag,bool deprecated) +bool long_desc,bool details_flag,bool deprecated, +const char *pmu_name) {struct perf_pmu *pmu;struct perf_pmu_alias *alias;
@@ -1679,10 +1687,16 @@ void print_pmu_events(const char *event_glob, bool name_only, bool quiet_flag, pmu =NULL ; j =0 ;while ((pmu =perf_pmu__scan (pmu)) !=NULL ) { +if (pmu_name &&perf_pmu__is_hybrid (pmu->name) && +strcmp (pmu_name, pmu->name)) { +continue ; + } +list_for_each_entry (alias, &pmu->aliases, list) {char *name = alias->desc ? alias->name :format_alias (buf,sizeof (buf), pmu, alias); -bool is_cpu =is_pmu_core (pmu->name); +bool is_cpu =is_pmu_core (pmu->name) || +perf_pmu__is_hybrid (pmu->name);if (alias->deprecated && !deprecated)continue ;
@@ -1730,8 +1744,13 @@ void print_pmu_events(const char *event_glob, bool name_only, bool quiet_flag,qsort (aliases, len,sizeof (struct sevent ), cmp_sevent);for (j =0 ; j < len; j++) {/* Skip duplicates */ -if (j >0 && !strcmp (aliases[j].name, aliases[j -1 ].name)) -continue ; +if (j >0 && !strcmp (aliases[j].name, aliases[j -1 ].name)) { +if (!aliases[j].pmu || !aliases[j -1 ].pmu || + !strcmp (aliases[j].pmu, aliases[j -1 ].pmu)) { +continue ; + } + } +if (name_only) {printf ("%s " , aliases[j].name);continue ;
tools/perf/util/pmu.h +1 -1
@@ -111,7 +111,7 @@ struct perf_pmu *perf_pmu__scan(struct perf_pmu *pmu);bool is_pmu_core (const char *name);void print_pmu_events (const char *event_glob,bool name_only,bool quiet,bool long_desc,bool details_flag, -bool deprecated); +bool deprecated,const char *pmu_name);bool pmu_have_event (const char *pname,const char *name); int perf_pmu__scan_file(struct perf_pmu *pmu, const char *name, const char *fmt, ...) __scanf(3, 4);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 77/83 perf tools: Check vmlinux/kallsyms arguments in all tools
In reply to Greg Kroah-HartmanFrom: James Clark <[email protected]>
[ Upstream commit 7cc72553ac03ec20afe2dec91dce4624ccd379b8 ]
Only perf report checked the validity of these arguments so apply the same check to all tools that read them for consistency.
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/builtin-annotate.c | 4 ++++ tools/perf/builtin-c2c.c | 4 ++++ tools/perf/builtin-probe.c | 5 +++++ tools/perf/builtin-record.c | 4 ++++ tools/perf/builtin-sched.c | 4 ++++ tools/perf/builtin-script.c | 3 +++ tools/perf/builtin-top.c | 4 ++++ 7 files changed, 28 insertions(+)
tools/perf/builtin-annotate.c +4 -0
@@ -591,6 +591,10 @@ int cmd_annotate(int argc, const char **argv)return ret; } + ret =symbol__validate_sym_arguments (); +if (ret) +return ret; +if (quiet)perf_quiet_option ();
tools/perf/builtin-c2c.c +4 -0
@@ -2770,6 +2770,10 @@ static int perf_c2c__report(int argc, const char **argv)if (c2c.stats_only) c2c.use_stdio = true; + err =symbol__validate_sym_arguments (); +if (err) + goto out; +if (!input_name || !strlen (input_name)) input_name ="perf.data" ;
tools/perf/builtin-probe.c +5 -0
@@ -21,6 +21,7 @@#include "util/build-id.h" #include "util/strlist.h" #include "util/strfilter.h" +#include "util/symbol.h" #include "util/symbol_conf.h" #include "util/debug.h" #include <subcmd/parse-options.h>
@@ -629,6 +630,10 @@ __cmd_probe(int argc, const char **argv) params.command ='a' ; } + ret =symbol__validate_sym_arguments (); +if (ret) +return ret; +if (params.quiet) {if (verbose !=0 ) {pr_err (" Error: -v and -q are exclusive.\n" );
tools/perf/builtin-record.c +4 -0
@@ -2680,6 +2680,10 @@ int cmd_record(int argc, const char **argv)if (quiet)perf_quiet_option (); + err =symbol__validate_sym_arguments (); +if (err) +return err; +/* Make system wide (-a) the default target. */ if (!argc &&target__none (&rec->opts.target)) rec->opts.target.system_wide = true;
tools/perf/builtin-sched.c +4 -0
@@ -3538,6 +3538,7 @@ int cmd_sched(int argc, const char **argv) .fork_event = replay_fork_event, };unsigned int i; +int ret;for (i =0 ; i <ARRAY_SIZE (sched.curr_pid); i++) sched.curr_pid[i] =-1 ;
@@ -3598,6 +3599,9 @@ int cmd_sched(int argc, const char **argv)parse_options_usage (NULL , timehist_options,"n" , true);return -EINVAL ; } + ret =symbol__validate_sym_arguments (); +if (ret) +return ret;return perf_sched__timehist (&sched); }else {
tools/perf/builtin-script.c +3 -0
@@ -3839,6 +3839,9 @@ int cmd_script(int argc, const char **argv) data.path = input_name; data.force = symbol_conf.force; +if (symbol__validate_sym_arguments ()) +return -1 ; +if (argc >1 && !strncmp (argv[0 ],"rec" ,strlen ("rec" ))) { rec_script_path =get_script_path (argv[1 ],RECORD_SUFFIX );if (!rec_script_path)
tools/perf/builtin-top.c +4 -0
@@ -1618,6 +1618,10 @@ int cmd_top(int argc, const char **argv)if (argc)usage_with_options (top_usage, options); + status =symbol__validate_sym_arguments (); +if (status) + goto out_delete_evlist; +if (annotate_check_args (&top.annotation_opts) <0 ) goto out_delete_evlist;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 78/83 perf tools: Enhance the matching of sub-commands abbreviations
In reply to Greg Kroah-HartmanFrom: Wei Li <[email protected]>
[ Upstream commit ae0f4eb34fc3014f7eba78fab90a0e98e441a4cd ]
We support short command 'rec*' for 'record' and 'rep*' for 'report' in lots of sub-commands, but the matching is not quite strict currnetly.
It may be puzzling sometime, like we mis-type a 'recport' to report but it will perform 'record' in fact without any message.
To fix this, add a check to ensure that the short cmd is valid prefix of the real command.
Committer testing:
[root@quaco ~]# perf c2c re sleep 1
Usage: perf c2c {record|report}
-v, --verbose be more verbose (show counter open errors, etc)
# perf c2c rec sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.038 MB perf.data (16 samples) ] # perf c2c recport sleep 1
Usage: perf c2c {record|report}
-v, --verbose be more verbose (show counter open errors, etc)
# perf c2c record sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.038 MB perf.data (15 samples) ] # perf c2c records sleep 1
Usage: perf c2c {record|report}
-v, --verbose be more verbose (show counter open errors, etc)
#
Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/builtin-c2c.c | 5 +++-- tools/perf/builtin-kmem.c | 2 +- tools/perf/builtin-kvm.c | 9 +++++---- tools/perf/builtin-lock.c | 5 +++-- tools/perf/builtin-mem.c | 5 +++-- tools/perf/builtin-sched.c | 4 ++-- tools/perf/builtin-script.c | 4 ++-- tools/perf/builtin-stat.c | 4 ++-- tools/perf/builtin-timechart.c | 3 ++- 9 files changed, 23 insertions(+), 18 deletions(-)
tools/perf/builtin-c2c.c +3 -2
@@ -44,6 +44,7 @@#include "../perf.h" #include "pmu.h" #include "pmu-hybrid.h" +#include "string2.h" struct c2c_hists {struct hists hists;
@@ -3026,9 +3027,9 @@ int cmd_c2c(int argc, const char **argv)if (!argc)usage_with_options (c2c_usage, c2c_options); -if (!strncmp (argv[0 ],"rec" ,3 )) { +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) {return perf_c2c__record (argc, argv); - }else if (!strncmp (argv[0 ],"rep" ,3 )) { + }else if (strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ])) {return perf_c2c__report (argc, argv); }else {usage_with_options (c2c_usage, c2c_options);
tools/perf/builtin-kmem.c +1 -1
@@ -1946,7 +1946,7 @@ int cmd_kmem(int argc, const char **argv) kmem_page =1 ; } -if (!strncmp (argv[0 ],"rec" ,3 )) { +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) {symbol__init (NULL );return __cmd_record (argc, argv); }
tools/perf/builtin-kvm.c +5 -4
@@ -24,6 +24,7 @@#include "util/ordered-events.h" #include "util/kvm-stat.h" #include "ui/ui.h" +#include "util/string2.h" #include <sys/prctl.h> #ifdef HAVE_TIMERFD_SUPPORT
@@ -1500,10 +1501,10 @@ static int kvm_cmd_stat(const char *file_name, int argc, const char **argv) goto perf_stat; } -if (!strncmp (argv[1 ],"rec" ,3 )) +if (strlen (argv[1 ]) >2 &&strstarts ("record" , argv[1 ]))return kvm_events_record (&kvm, argc -1 , argv +1 ); -if (!strncmp (argv[1 ],"rep" ,3 )) +if (strlen (argv[1 ]) >2 &&strstarts ("report" , argv[1 ]))return kvm_events_report (&kvm, argc -1 , argv +1 );#ifdef HAVE_TIMERFD_SUPPORT
@@ -1631,9 +1632,9 @@ int cmd_kvm(int argc, const char **argv) } } -if (!strncmp (argv[0 ],"rec" ,3 )) +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ]))return __cmd_record (file_name, argc, argv); -else if (!strncmp (argv[0 ],"rep" ,3 )) +else if (strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ]))return __cmd_report (file_name, argc, argv);else if (!strncmp (argv[0 ],"diff" ,4 ))return cmd_diff (argc, argv);
tools/perf/builtin-lock.c +3 -2
@@ -18,6 +18,7 @@#include "util/session.h" #include "util/tool.h" #include "util/data.h" +#include "util/string2.h" #include <sys/types.h> #include <sys/prctl.h>
@@ -997,9 +998,9 @@ int cmd_lock(int argc, const char **argv)if (!argc)usage_with_options (lock_usage, lock_options); -if (!strncmp (argv[0 ],"rec" ,3 )) { +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) {return __cmd_record (argc, argv); - }else if (!strncmp (argv[0 ],"report" ,6 )) { + }else if (strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ])) { trace_handler = &report_lock_ops;if (argc) { argc = parse_options(argc, argv,
tools/perf/builtin-mem.c +3 -2
@@ -20,6 +20,7 @@#include "util/symbol.h" #include "util/pmu.h" #include "util/pmu-hybrid.h" +#include "util/string2.h" #include <linux/err.h> #define MEM_OPERATION_LOAD 0x1
@@ -496,9 +497,9 @@ int cmd_mem(int argc, const char **argv) mem.input_name ="perf.data" ; } -if (!strncmp (argv[0 ],"rec" ,3 )) +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ]))return __cmd_record (argc, argv, &mem); -else if (!strncmp (argv[0 ],"rep" ,3 )) +else if (strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ]))return report_events (argc, argv, &mem);else usage_with_options (mem_usage, mem_options);
tools/perf/builtin-sched.c +2 -2
@@ -3554,7 +3554,7 @@ int cmd_sched(int argc, const char **argv)if (!strcmp (argv[0 ],"script" ))return cmd_script (argc, argv); -if (!strncmp (argv[0 ],"rec" ,3 )) { +if (strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) {return __cmd_record (argc, argv); }else if (!strncmp (argv[0 ],"lat" ,3 )) { sched.tp_handler = &lat_ops;
@@ -3574,7 +3574,7 @@ int cmd_sched(int argc, const char **argv) sched.tp_handler = &map_ops;setup_sorting (&sched, latency_options, latency_usage);return perf_sched__map (&sched); - }else if (!strncmp (argv[0 ],"rep" ,3 )) { + }else if (strlen (argv[0 ]) >2 &&strstarts ("replay" , argv[0 ])) { sched.tp_handler = &replay_ops;if (argc) { argc =parse_options (argc, argv, replay_options, replay_usage,0 );
tools/perf/builtin-script.c +2 -2
@@ -3842,13 +3842,13 @@ int cmd_script(int argc, const char **argv)if (symbol__validate_sym_arguments ())return -1 ; -if (argc >1 && !strncmp (argv[0 ],"rec" ,strlen ("rec" ))) { +if (argc >1 &&strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) { rec_script_path =get_script_path (argv[1 ],RECORD_SUFFIX );if (!rec_script_path)return cmd_record (argc, argv); } -if (argc >1 && !strncmp (argv[0 ],"rep" ,strlen ("rep" ))) { +if (argc >1 &&strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ])) { rep_script_path =get_script_path (argv[1 ],REPORT_SUFFIX );if (!rep_script_path) { fprintf(stderr,
tools/perf/builtin-stat.c +2 -2
@@ -2255,11 +2255,11 @@ int cmd_stat(int argc, const char **argv) }else stat_config.csv_sep =DEFAULT_SEPARATOR ; -if (argc && !strncmp (argv[0 ],"rec" ,3 )) { +if (argc &&strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) { argc =__cmd_record (argc, argv);if (argc <0 )return -1 ; - }else if (argc && !strncmp (argv[0 ],"rep" ,3 )) + }else if (argc &&strlen (argv[0 ]) >2 &&strstarts ("report" , argv[0 ]))return __cmd_report (argc, argv); interval = stat_config.interval;
tools/perf/builtin-timechart.c +2 -1
@@ -35,6 +35,7 @@#include "util/tool.h" #include "util/data.h" #include "util/debug.h" +#include "util/string2.h" #include <linux/err.h> #ifdef LACKS_OPEN_MEMSTREAM_PROTOTYPE
@@ -1983,7 +1984,7 @@ int cmd_timechart(int argc, const char **argv)return -1 ; } -if (argc && !strncmp (argv[0 ],"rec" ,3 )) { +if (argc &&strlen (argv[0 ]) >2 &&strstarts ("record" , argv[0 ])) { argc =parse_options (argc, argv, timechart_record_options, timechart_record_usage,PARSE_OPT_STOP_AT_NON_OPTION );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 79/83 perf list: Print all available tool events
In reply to Greg Kroah-HartmanFrom: Florian Fischer <[email protected]>
[ Upstream commit 75eafc970bd9d36d906960a81376549f5dc99696 ]
Introduce names for the new tool events 'user_time' and 'system_time'.
$ perf list ... duration_time [Tool event] user_time [Tool event] system_time [Tool event] ...
Committer testing:
Before:
$ perf list | grep Tool duration_time [Tool event] $
After:
$ perf list | grep Tool
duration_time [Tool event]
user_time [Tool event]
system_time [Tool event]
$Stable-dep-of: 71c86cda750b ("perf parse-events: Remove "not supported" hybrid cache events")
--- tools/perf/util/evsel.c | 19 ++++++++++------ tools/perf/util/evsel.h | 1 + tools/perf/util/parse-events.c | 40 +++++++++++++++++++++++++++++----- 3 files changed, 47 insertions(+), 13 deletions(-)
tools/perf/util/evsel.c +12 -7
@@ -600,6 +600,17 @@ static int evsel__sw_name(struct evsel *evsel, char *bf, size_t size)return r +evsel__add_modifiers (evsel, bf + r, size - r); } +const char *evsel__tool_names[PERF_TOOL_MAX ] = { +"duration_time" , +"user_time" , +"system_time" , +}; + +static int evsel__tool_name (enum perf_tool_event ev,char *bf,size_t size) +{ +return scnprintf (bf, size,"%s" , evsel__tool_names[ev]); +} +static int __evsel__bp_name (char *bf,size_t size,u64 addr,u64 type) {int r;
@@ -726,12 +737,6 @@ static int evsel__raw_name(struct evsel *evsel, char *bf, size_t size)return ret +evsel__add_modifiers (evsel, bf + ret, size - ret); } -static int evsel__tool_name (char *bf,size_t size) -{ -int ret =scnprintf (bf, size,"duration_time" ); -return ret; -} -const char *evsel__name (struct evsel *evsel) {char bf[128 ];
@@ -757,7 +762,7 @@ const char *evsel__name(struct evsel *evsel)case PERF_TYPE_SOFTWARE :if (evsel->tool_event) -evsel__tool_name (bf,sizeof (bf)); +evsel__tool_name (evsel->tool_event, bf,sizeof (bf));else evsel__sw_name (evsel, bf,sizeof (bf));break ;
tools/perf/util/evsel.h +1 -0
@@ -257,6 +257,7 @@ extern const char *evsel__hw_cache_op[PERF_COUNT_HW_CACHE_OP_MAX][EVSEL__MAX_ALIextern const char *evsel__hw_cache_result[PERF_COUNT_HW_CACHE_RESULT_MAX ][EVSEL__MAX_ALIASES ];extern const char *evsel__hw_names[PERF_COUNT_HW_MAX ];extern const char *evsel__sw_names[PERF_COUNT_SW_MAX ]; +extern const char *evsel__tool_names[PERF_TOOL_MAX ];extern char *evsel__bpf_counter_events;bool evsel__match_bpf_counter_events (const char *name);
tools/perf/util/parse-events.c +34 -6
@@ -156,6 +156,21 @@ struct event_symbol event_symbols_sw[PERF_COUNT_SW_MAX] = { }, }; +struct event_symbol event_symbols_tool[PERF_TOOL_MAX ] = { + [PERF_TOOL_DURATION_TIME ] = { + .symbol ="duration_time" , + .alias ="" , + }, + [PERF_TOOL_USER_TIME ] = { + .symbol ="user_time" , + .alias ="" , + }, + [PERF_TOOL_SYSTEM_TIME ] = { + .symbol ="system_time" , + .alias ="" , + }, +}; +#define __PERF_EVENT_FIELD (config, name) \ ((config & PERF_EVENT_##name##_MASK) >> PERF_EVENT_##name##_SHIFT)
@@ -2934,21 +2949,34 @@ int print_hwcache_events(const char *event_glob, bool name_only)return evt_num; } -static void print_tool_event (const char *name,const char *event_glob, +static void print_tool_event (const struct event_symbol *syms,const char *event_glob,bool name_only) { -if (event_glob && !strglobmatch (name, event_glob)) +if (syms->symbol ==NULL ) +return ; + +if (event_glob && !(strglobmatch (syms->symbol, event_glob) || + (syms->alias &&strglobmatch (syms->alias, event_glob))))return ; +if (name_only) -printf ("%s " , name); -else +printf ("%s " , syms->symbol); +else { +char name[MAX_NAME_LEN ]; +if (syms->alias &&strlen (syms->alias)) +snprintf (name,MAX_NAME_LEN ,"%s OR %s" , syms->symbol, syms->alias); +else +strlcpy (name, syms->symbol,MAX_NAME_LEN );printf (" %-50s [%s]\n" , name,"Tool event" ); - + } }void print_tool_events (const char *event_glob,bool name_only) { -print_tool_event ("duration_time" , event_glob, name_only); +// Start at 1 because the first enum entry symbols no tool event +for (int i =1 ; i <PERF_TOOL_MAX ; ++i) { +print_tool_event (event_symbols_tool + i, event_glob, name_only); + }if (pager_in_use ())printf ("\n" ); }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 80/83 x86/alternative: Fix race in try_get_desc()
In reply to Greg Kroah-HartmanFrom: Nadav Amit <[email protected]>
commit efd608fa7403ba106412b437f873929e2c862e28 upstream.
I encountered some occasional crashes of poke_int3_handler() when kprobes are set, while accessing desc->vec.
The text poke mechanism claims to have an RCU-like behavior, but it does not appear that there is any quiescent state to ensure that nobody holds reference to desc. As a result, the following race appears to be possible, which can lead to memory corruption.
CPU0 CPU1
---- ----
text_poke_bp_batch()
-> smp_store_release(&bp_desc, &desc)
[ notice that desc is on
the stack ] poke_int3_handler() [ int3 might be kprobe's so sync events are do not help ] -> try_get_desc(descp=&bp_desc) desc = __READ_ONCE(bp_desc) if (!desc) [false, success]
WRITE_ONCE(bp_desc, NULL);
atomic_dec_and_test(&desc.refs)
[ success, desc space on the stack
is being reused and might have
non-zero value. ]
arch_atomic_inc_not_zero(&desc->refs)
[ might succeed since desc points to
stack memory that was freed and might be reused. ]
Fix this issue with small backportable patch. Instead of trying to make RCU-like behavior for bp_desc, just eliminate the unnecessary level of indirection of bp_desc, and hold the whole descriptor as a global. Anyhow, there is only a single descriptor at any given moment.
--- arch/x86/kernel/alternative.c | 45 +++++++++++++++++++++--------------------- 1 file changed, 23 insertions(+), 22 deletions(-)
arch/x86/kernel/alternative.c +23 -22
@@ -1200,22 +1200,23 @@ struct bp_patching_desc {atomic_t refs; }; -static struct bp_patching_desc *bp_desc; +static struct bp_patching_desc bp_desc;static __always_inline -struct bp_patching_desc *try_get_desc(struct bp_patching_desc **descp) +struct bp_patching_desc *try_get_desc(void) { -/* rcu_dereference */ -struct bp_patching_desc *desc =__READ_ONCE (*descp); +struct bp_patching_desc *desc = &bp_desc; -if (!desc || !arch_atomic_inc_not_zero (&desc->refs)) +if (!arch_atomic_inc_not_zero (&desc->refs))return NULL ;return desc; } -static __always_inline void put_desc(struct bp_patching_desc *desc) +static __always_inline void put_desc(void) { +struct bp_patching_desc *desc = &bp_desc; +smp_mb__before_atomic ();arch_atomic_dec (&desc->refs); }
@@ -1248,15 +1249,15 @@ noinstr int poke_int3_handler(struct pt_/* * Having observed our INT3 instruction, we now must observe -* bp_desc: +* bp_desc with non-zero refcount: * -* bp_desc = desc INT3 +* bp_desc.refs = 1 INT3 * WMB RMB -* write INT3 if (desc) +* write INT3 if (bp_desc.refs != 0) */ smp_rmb (); - desc =try_get_desc (&bp_desc); + desc =try_get_desc ();if (!desc)return 0 ;
@@ -1310,7 +1311,7 @@ noinstr int poke_int3_handler(struct pt_ ret =1 ; out_put: -put_desc (desc); +put_desc ();return ret; }
@@ -1341,18 +1342,20 @@ static int tp_vec_nr;*/ static void text_poke_bp_batch (struct text_poke_loc *tp,unsigned int nr_entries) { -struct bp_patching_desc desc = { - .vec = tp, - .nr_entries = nr_entries, - .refs =ATOMIC_INIT (1 ), - };unsigned char int3 =INT3_INSN_OPCODE ;unsigned int i;int do_sync;lockdep_assert_held (&text_mutex); -smp_store_release (&bp_desc, &desc);/* rcu_assign_pointer */ + bp_desc.vec = tp; + bp_desc.nr_entries = nr_entries; + +/* +* Corresponds to the implicit memory barrier in try_get_desc() to +* ensure reading a non-zero refcount provides up to date bp_desc data. +*/ +atomic_set_release (&bp_desc.refs,1 );/* * Corresponding read barrier in int3 notifier for making sure the
@@ -1440,12 +1443,10 @@ static void text_poke_bp_batch(struct tetext_poke_sync ();/* -* Remove and synchronize_rcu(), except we have a very primitive -* refcount based completion. +* Remove and wait for refs to be zero. */ -WRITE_ONCE (bp_desc,NULL );/* RCU_INIT_POINTER */ -if (!atomic_dec_and_test (&desc.refs)) -atomic_cond_read_acquire (&desc.refs, !VAL ); +if (!atomic_dec_and_test (&bp_desc.refs)) +atomic_cond_read_acquire (&bp_desc.refs, !VAL ); } static void text_poke_loc_init(struct text_poke_loc *tp, void *addr,
Greg Kroah-Hartman
maintainerPATCH 81/83 drm/i915/gem: Really move i915_gem_context.link under ref protection
In reply to Greg Kroah-HartmanFrom: Chris Wilson <[email protected]>
commit d119888b09bd567e07c6b93a07f175df88857e02 upstream.
i915_perf assumes that it can use the i915_gem_context reference to protect its i915->gem.contexts.list iteration. However, this requires that we do not remove the context from the list until after we drop the final reference and release the struct. If, as currently, we remove the context from the list during context_close(), the link.next pointer may be poisoned while we are holding the context reference and cause a GPF:
[ 4070.573157] i915 0000:00:02.0: [drm:i915_perf_open_ioctl [i915]] filtering on ctx_id=0x1fffff ctx_id_mask=0x1fffff [ 4070.574881] general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP [ 4070.574897] CPU: 1 PID: 284392 Comm: amd_performance Tainted: G E 5.17.9 #180 [ 4070.574903] Hardware name: Intel Corporation NUC7i5BNK/NUC7i5BNB, BIOS BNKBL357.86A.0052.2017.0918.1346 09/18/2017 [ 4070.574907] RIP: 0010:oa_configure_all_contexts.isra.0+0x222/0x350 [i915] [ 4070.574982] Code: 08 e8 32 6e 10 e1 4d 8b 6d 50 b8 ff ff ff ff 49 83 ed 50 f0 41 0f c1 04 24 83 f8 01 0f 84 e3 00 00 00 85 c0 0f 8e fa 00 00 00 <49> 8b 45 50 48 8d 70 b0 49 8d 45 50 48 39 44 24 10 0f 85 34 fe ff [ 4070.574990] RSP: 0018:ffffc90002077b78 EFLAGS: 00010202 [ 4070.574995] RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000000 [ 4070.575000] RDX: 0000000000000001 RSI: ffffc90002077b20 RDI: ffff88810ddc7c68 [ 4070.575004] RBP: 0000000000000001 R08: ffff888103242648 R09: fffffffffffffffc [ 4070.575008] R10: ffffffff82c50bc0 R11: 0000000000025c80 R12: ffff888101bf1860 [ 4070.575012] R13: dead0000000000b0 R14: ffffc90002077c04 R15: ffff88810be5cabc [ 4070.575016] FS: 00007f1ed50c0780(0000) GS:ffff88885ec80000(0000) knlGS:0000000000000000 [ 4070.575021] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4070.575025] CR2: 00007f1ed5590280 CR3: 000000010ef6f005 CR4: 00000000003706e0 [ 4070.575029] Call Trace: [ 4070.575033] <TASK> [ 4070.575037] lrc_configure_all_contexts+0x13e/0x150 [i915] [ 4070.575103] gen8_enable_metric_set+0x4d/0x90 [i915] [ 4070.575164] i915_perf_open_ioctl+0xbc0/0x1500 [i915] [ 4070.575224] ? asm_common_interrupt+0x1e/0x40 [ 4070.575232] ? i915_oa_init_reg_state+0x110/0x110 [i915] [ 4070.575290] drm_ioctl_kernel+0x85/0x110 [ 4070.575296] ? update_load_avg+0x5f/0x5e0 [ 4070.575302] drm_ioctl+0x1d3/0x370 [ 4070.575307] ? i915_oa_init_reg_state+0x110/0x110 [i915] [ 4070.575382] ? gen8_gt_irq_handler+0x46/0x130 [i915] [ 4070.575445] __x64_sys_ioctl+0x3c4/0x8d0 [ 4070.575451] ? __do_softirq+0xaa/0x1d2 [ 4070.575456] do_syscall_64+0x35/0x80 [ 4070.575461] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 4070.575467] RIP: 0033:0x7f1ed5c10397 [ 4070.575471] Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 da 0d 00 f7 d8 64 89 01 48 [ 4070.575478] RSP: 002b:00007ffd65c8d7a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 4070.575484] RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 00007f1ed5c10397 [ 4070.575488] RDX: 00007ffd65c8d7c0 RSI: 0000000040106476 RDI: 0000000000000006 [ 4070.575492] RBP: 00005620972f9c60 R08: 000000000000000a R09: 0000000000000005 [ 4070.575496] R10: 000000000000000d R11: 0000000000000246 R12: 000000000000000a [ 4070.575500] R13: 000000000000000d R14: 0000000000000000 R15: 00007ffd65c8d7c0 [ 4070.575505] </TASK> [ 4070.575507] Modules linked in: nls_ascii(E) nls_cp437(E) vfat(E) fat(E) i915(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) crct10dif_pclmul(E) crc32_pclmul(E) crc32c_intel(E) aesni_intel(E) crypto_simd(E) intel_gtt(E) cryptd(E) ttm(E) rapl(E) intel_cstate(E) drm_kms_helper(E) cfbfillrect(E) syscopyarea(E) cfbimgblt(E) intel_uncore(E) sysfillrect(E) mei_me(E) sysimgblt(E) i2c_i801(E) fb_sys_fops(E) mei(E) intel_pch_thermal(E) i2c_smbus(E) cfbcopyarea(E) video(E) button(E) efivarfs(E) autofs4(E) [ 4070.575549] ---[ end trace 0000000000000000 ]---
v3: fix incorrect syntax of spin_lock() replacing spin_lock_irqsave()
v2: irqsave not required in a worker, neither conversion to irq safe
elsewhere (Tvrtko),
- perf: it's safe to call gen8_configure_context() even if context has been closed, no need to check,
- drop unrelated cleanup (Andi, Tvrtko)
--- drivers/gpu/drm/i915/gem/i915_gem_context.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_context.c +4 -4
@@ -997,6 +997,10 @@ void i915_gem_context_release(struct kretrace_i915_context_free (ctx);GEM_BUG_ON (!i915_gem_context_is_closed (ctx)); +spin_lock (&ctx->i915->gem.contexts.lock); +list_del (&ctx->link); +spin_unlock (&ctx->i915->gem.contexts.lock); +if (ctx->syncobj)drm_syncobj_put (ctx->syncobj);
@@ -1228,10 +1232,6 @@ static void context_close(struct i915_ge*/ lut_close (ctx); -spin_lock (&ctx->i915->gem.contexts.lock); -list_del (&ctx->link); -spin_unlock (&ctx->i915->gem.contexts.lock); -mutex_unlock (&ctx->mutex);/*
Greg Kroah-Hartman
maintainerPATCH 82/83 perf pmu: Fix alias events list
In reply to Greg Kroah-HartmanFrom: John Garry <[email protected]>
commit e0257a01d6689c273a019756ed5e13911cc1bfed upstream.
Commit 0e0ae8742207c3b4 ("perf list: Display hybrid PMU events with cpu type") changes the event list for uncore PMUs or arm64 heterogeneous CPU systems, such that duplicate aliases are incorrectly listed per PMU (which they should not be), like:
# perf list ... unc_cbo_cache_lookup.any_es [Unit: uncore_cbox L3 Lookup any request that access cache and found line in E or S-state] unc_cbo_cache_lookup.any_es [Unit: uncore_cbox L3 Lookup any request that access cache and found line in E or S-state] unc_cbo_cache_lookup.any_i [Unit: uncore_cbox L3 Lookup any request that access cache and found line in I-state] unc_cbo_cache_lookup.any_i [Unit: uncore_cbox L3 Lookup any request that access cache and found line in I-state] ...
Notice how the events are listed twice.
The named commit changed how we remove duplicate events, in that events for different PMUs are not treated as duplicates. I suppose this is to handle how "Each hybrid pmu event has been assigned with a pmu name".
Fix PMU alias listing by restoring behaviour to remove duplicates for non-hybrid PMUs.
--- tools/perf/util/pmu.c | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-)
tools/perf/util/pmu.c +17 -6
@@ -1659,6 +1659,21 @@ bool is_pmu_core(const char *name)return !strcmp (name,"cpu" ) ||is_arm_pmu_core (name); } +static bool pmu_alias_is_duplicate (struct sevent *alias_a, +struct sevent *alias_b) +{ +/* Different names -> never duplicates */ +if (strcmp (alias_a->name, alias_b->name)) +return false; + +/* Don't remove duplicates for hybrid PMUs */ +if (perf_pmu__is_hybrid (alias_a->pmu) && +perf_pmu__is_hybrid (alias_b->pmu)) +return false; + +return true; +} +void print_pmu_events (const char *event_glob,bool name_only,bool quiet_flag,bool long_desc,bool details_flag,bool deprecated,const char *pmu_name)
@@ -1744,12 +1759,8 @@ void print_pmu_events(const char *event_qsort (aliases, len,sizeof (struct sevent ), cmp_sevent);for (j =0 ; j < len; j++) {/* Skip duplicates */ -if (j >0 && !strcmp (aliases[j].name, aliases[j -1 ].name)) { -if (!aliases[j].pmu || !aliases[j -1 ].pmu || - !strcmp (aliases[j].pmu, aliases[j -1 ].pmu)) { -continue ; - } - } +if (j >0 &&pmu_alias_is_duplicate (&aliases[j], &aliases[j -1 ])) +continue ;if (name_only) {printf ("%s " , aliases[j].name);
Greg Kroah-Hartman
maintainerPATCH 83/83 perf evsel: Add tool event helpers
In reply to Greg Kroah-HartmanFrom: Ian Rogers <[email protected]>
commit 79932d161fda7f2d18761ace5f25445f7b525741 upstream.
Convert to and from a string. Fix evsel__tool_name() as array is off-by-1. Support more than just duration_time as a metric-id.
--- tools/perf/util/evsel.c | 41 +++++++++++++++++++++++++++++++---------- tools/perf/util/evsel.h | 11 +++++++++++ 2 files changed, 42 insertions(+), 10 deletions(-)
tools/perf/util/evsel.c +31 -10
@@ -59,6 +59,33 @@ struct perf_missing_features perf_missinstatic clockid_t clockid; +static const char *const perf_tool_event__tool_names[PERF_TOOL_MAX ] = { +NULL , +"duration_time" , +"user_time" , +"system_time" , +}; + +const char *perf_tool_event__to_str (enum perf_tool_event ev) +{ +if (ev >PERF_TOOL_NONE && ev <PERF_TOOL_MAX ) +return perf_tool_event__tool_names[ev]; + +return NULL ; +} + +enum perf_tool_event perf_tool_event__from_str (const char *str) +{ +int i; + +perf_tool_event__for_each_event (i) { +if (!strcmp (str, perf_tool_event__tool_names[i])) +return i; + } +return PERF_TOOL_NONE ; +} + +static int evsel__no_extra_init (struct evsel *evsel__maybe_unused ) {return 0 ;
@@ -600,15 +627,9 @@ static int evsel__sw_name(struct evsel *return r +evsel__add_modifiers (evsel, bf + r, size - r); } -const char *evsel__tool_names[PERF_TOOL_MAX ] = { -"duration_time" , -"user_time" , -"system_time" , -}; -static int evsel__tool_name (enum perf_tool_event ev,char *bf,size_t size) { -return scnprintf (bf, size,"%s" , evsel__tool_names[ev]); +return scnprintf (bf, size,"%s" ,perf_tool_event__to_str (ev)); }static int __evsel__bp_name (char *bf,size_t size,u64 addr,u64 type)
@@ -761,7 +782,7 @@ const char *evsel__name(struct evsel *evbreak ;case PERF_TYPE_SOFTWARE : -if (evsel->tool_event) +if (evsel__is_tool (evsel))evsel__tool_name (evsel->tool_event, bf,sizeof (bf));else evsel__sw_name (evsel, bf,sizeof (bf));
@@ -794,8 +815,8 @@ const char *evsel__metric_id(const strucif (evsel->metric_id)return evsel->metric_id; -if (evsel->core.attr.type ==PERF_TYPE_SOFTWARE && evsel->tool_event) -return "duration_time" ; +if (evsel__is_tool (evsel)) +return perf_tool_event__to_str (evsel->tool_event);return "unknown" ; }
tools/perf/util/evsel.h +11 -0
@@ -30,6 +30,12 @@ enum perf_tool_event { PERF_TOOL_DURATION_TIME = 1, }; +const char *perf_tool_event__to_str (enum perf_tool_event ev); +enum perf_tool_event perf_tool_event__from_str (const char *str); + +#define perf_tool_event__for_each_event (ev) \ + for ((ev) = PERF_TOOL_DURATION_TIME; (ev) < PERF_TOOL_MAX; ev++) +/** struct evsel - event selector * * @evlist - evlist this evsel is in, if it is in one.
@@ -265,6 +271,11 @@ int __evsel__hw_cache_type_op_res_name(uconst char *evsel__name (struct evsel *evsel);const char *evsel__metric_id (const struct evsel *evsel); +static inline bool evsel__is_tool (const struct evsel *evsel) +{ +return evsel->tool_event !=PERF_TOOL_NONE ; +} +const char *evsel__group_name (struct evsel *evsel);int evsel__group_desc (struct evsel *evsel,char *buf,size_t size);
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +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.15.72-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.15:
10 builds: 10 pass, 0 fail
28 boots: 28 pass, 0 fail
114 tests: 114 pass, 0 failLinux version: 5.15.72-rc1-g6b8312581f86
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04Jon
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
perf fails to build.
In file included from util/evlist.h:13,
from builtin-annotate.c:21:util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?
266 | extern const char *evsel__tool_names[PERF_TOOL_MAX];
| ^~~~~~~~~~~~~
| PERF_TXN_MAX
In file included from util/hist.h:8,
from builtin-diff.c:13:
util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?
266 | extern const char *evsel__tool_names[PERF_TOOL_MAX];
| ^~~~~~~~~~~~~
| PERF_TXN_MAX
In file included from util/evlist.h:13,
from builtin-evlist.c:11:
util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?
266 | extern const char *evsel__tool_names[PERF_TOOL_MAX];
| ^~~~~~~~~~~~~
| PERF_TXN_MAX
In file included from tools/perf/util/evlist.h:13,
from builtin-ftrace.c:24:
tools/perf/util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?
266 | extern const char *evsel__tool_names[PERF_TOOL_MAX];
| ^~~~~~~~~~~~~
| PERF_TXN_MAX
builtin-annotate.c: In function ‘cmd_annotate’:
builtin-annotate.c:594:8: error: implicit declaration of function ‘symbol__validate_sym_arguments’ [-Werror=implicit-function-declaration]
594 | ret = symbol__validate_sym_arguments();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Guenter
Quoted 11 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
perf fails to build.
Same here.
Signature · 1 line
Florian
Greg Kroah-Hartman
maintainerQuoted 32 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
perf fails to build.
In file included from
util/evlist.h:13,
from builtin-annotate.c:21:util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?266 | extern const char *evsel__tool_names[PERF_TOOL_MAX]; | ^~~~~~~~~~~~~ | PERF_TXN_MAX In file included from util/hist.h:8, from builtin-diff.c:13: util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’? 266 | extern const char *evsel__tool_names[PERF_TOOL_MAX]; | ^~~~~~~~~~~~~ | PERF_TXN_MAX In file included from util/evlist.h:13, from builtin-evlist.c:11: util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’? 266 | extern const char *evsel__tool_names[PERF_TOOL_MAX]; | ^~~~~~~~~~~~~ | PERF_TXN_MAXIn file included from
tools/perf/util/evlist.h:13,
from builtin-ftrace.c:24:
Quoted 8 lines
tools/perf/util/evsel.h:266:38: error: ‘PERF_TOOL_MAX’ undeclared here (not in a function); did you mean ‘PERF_TXN_MAX’?266 | extern const char *evsel__tool_names[PERF_TOOL_MAX]; | ^~~~~~~~~~~~~ | PERF_TXN_MAX builtin-annotate.c: In function ‘cmd_annotate’: builtin-annotate.c:594:8: error: implicit declaration of function ‘symbol__validate_sym_arguments’ [-Werror=implicit-function-declaration] 594 | ret = symbol__validate_sym_arguments(); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks, I've dropped all perf patches from the 5.15 queue right now as they seem to have been added incorrectly.
That being said, I can't build perf for 5.15.y now anyway, so something older must have broken my system, glad it's building for you...
thanks
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
Build results:
total: 159 pass: 157 fail: 2 Failed builds: i386:tools/perf x86_64:tools/perf Qemu test results: total: 486 pass: 486 fail: 0
Perf build failures as already reported.
Guenter
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +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.15.72-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.72-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. I am still seeing the drm related regression and didn't get a chance to isolate. Will try to do it this week.
thanks,
-- Shuah
Shuah Khan
Tested-byQuoted 17 lines · Shuah Khan
Quoted 16 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +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.15.72-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.15.y and the diffstat can be found below.thanks,
Quoted 8 lines
Quoted 2 lines
greg k-h
Compiled and booted on my test system. I am still seeing the drm related regression and didn't get a chance to isolate. Will try to do it this week.
Tested-by Shuah Khan <[email protected]>
Sorry for the confusion. This 5.15.72 is just fine. The drm issue I am seeing is on 5.10.147 and started in 5.10.146. I isolated it in 5.4 and testing the same on 5.10 - will send responses to those threads.
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
5.15.72-rc1 compiled and booted with no errors or regressions on my x86_64 test system.
-srw
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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.
Successfully cross-compiled for arm64 (bcm2711_defconfig, GCC 10.2.0) and powerpc (ps3_defconfig, GCC 12.1.0).
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +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.15.72-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.15.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro's test farm.
Regressions while building perf on arm, arm64, x86_64 and i386 as other reported build log [1].
A part from that perf build failure, no new test failures found.
[1] https://builds.tuxbuild.com/2FcCmZZxrIrCmIDx2eq38erKAj8/
## Build
* kernel: 5.15.72-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.15.y
* git commit: ['6b8312581f86c31858502556391330b10956a92b']
* git describe: v5.15.71-84-g6b8312581f86
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.71-84-g6b8312581f86
## Test Regressions (compared to v5.15.71)
* arm, arm64, x86_64 and i386 build
- gcc-10-lkftconfig-perf
## No Metric Regressions (compared to v5.15.71)
## No Test Fixes (compared to v5.15.71)
## No Metric Fixes (compared to v5.15.71)
## Test result summary
total: 102006, pass: 90385, fail: 665, skip: 10658, xfail: 298
## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 332 total, 324 passed, 7 failed, 1 skipped
* arm64: 70 total, 65 passed, 4 failed, 1 skipped
* i386: 61 total, 54 passed, 7 failed
* mips: 61 total, 56 passed, 5 failed
* parisc: 14 total, 14 passed, 0 failed
* powerpc: 68 total, 60 passed, 8 failed
* riscv: 26 total, 25 passed, 1 failed
* s390: 29 total, 26 passed, 3 failed
* sh: 26 total, 24 passed, 2 failed
* sparc: 14 total, 14 passed, 0 failed
* x86_64: 66 total, 57 passed, 9 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-open-posix-tests
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* packetdrill
* rcutorture
* v4l2-compliance
* vdso
--
Linaro LKFT
https://lkft.linaro.org
Hi Greg,
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
Build test (gcc version 12.2.1 20220925):
mips: 62 configs -> no failure
arm: 99 configs -> no failure
arm64: 3 configs -> no failurex86_64: 4 configs -> no failure alpha allmodconfig -> no failure csky allmodconfig -> no failure powerpc allmodconfig -> no failure riscv allmodconfig -> no failure s390 allmodconfig -> no failure xtensa allmodconfig -> no failure
Boot test:x86_64: Booted on my test laptop. No regression.x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]
[1]. https://openqa.qa.codethink.co.uk/tests/1946
[2]. https://openqa.qa.codethink.co.uk/tests/1949
--
Regards
Sudip
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.15.72 release. There are 83 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, 05 Oct 2022 07:07:06 +0000. Anything received after that time might be too late.
No regressions found on WSL x86_64 and WSL ARM64
Built, booted, and compared dmesg results against 5.15.71.
Thank you. :)