6.13.7-rc1 review
Subsystems (4)
Greg Kroah-Hartman
maintainerPATCH 121/207 ALSA: usx2y: validate nrpacks module parameter on probe
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Murad Masimov <[email protected]>
[ Upstream commit 172a0f509723fe4741d4b8e9190cf434b18320d8 ]
The module parameter defines number of iso packets per one URB. User is allowed to set any value to the parameter of type int, which can lead to various kinds of weird and incorrect behavior like integer overflows, truncations, etc. Number of packets should be a small non-negative number.
Since this parameter is read-only, its value can be validated on driver probe.
--- sound/usb/usx2y/usbusx2y.c | 11 +++++++++++ sound/usb/usx2y/usbusx2y.h | 26 ++++++++++++++++++++++++++ sound/usb/usx2y/usbusx2yaudio.c | 27 --------------------------- 3 files changed, 37 insertions(+), 27 deletions(-)
sound/usb/usx2y/usbusx2y.c +11 -0
@@ -151,6 +151,12 @@ static int snd_usx2y_card_used[SNDRV_CARDS];static void snd_usx2y_card_private_free (struct snd_card *card);static void usx2y_unlinkseq (struct snd_usx2y_async_seq *s); +#ifdef USX2Y_NRPACKS_VARIABLE +int nrpacks =USX2Y_NRPACKS ;/* number of packets per urb */ +module_param (nrpacks, int,0444 ); +MODULE_PARM_DESC (nrpacks,"Number of packets per URB." ); +#endif +/* * pipe 4 is used for switching the lamps, setting samplerate, volumes .... */
@@ -432,6 +438,11 @@ static int snd_usx2y_probe(struct usb_interface *intf,struct snd_card *card;int err; +#ifdef USX2Y_NRPACKS_VARIABLE +if (nrpacks <0 || nrpacks >USX2Y_NRPACKS_MAX ) +return -EINVAL ; +#endif + if (le16_to_cpu(device->descriptor.idVendor) != 0x1604 || (le16_to_cpu(device->descriptor.idProduct) != USB_ID_US122 && le16_to_cpu(device->descriptor.idProduct) != USB_ID_US224 &&
sound/usb/usx2y/usbusx2y.h +26 -0
@@ -7,6 +7,32 @@#define NRURBS 2 +/* Default value used for nr of packs per urb. +* 1 to 4 have been tested ok on uhci. +* To use 3 on ohci, you'd need a patch: +* look for "0000425-linux-2.6.9-rc4-mm1_ohci-hcd.patch.gz" on +* "https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000425" +* +* 1, 2 and 4 work out of the box on ohci, if I recall correctly. +* Bigger is safer operation, smaller gives lower latencies. +*/ +#define USX2Y_NRPACKS 4 + +#define USX2Y_NRPACKS_MAX 1024 + +/* If your system works ok with this module's parameter +* nrpacks set to 1, you might as well comment +* this define out, and thereby produce smaller, faster code. +* You'd also set USX2Y_NRPACKS to 1 then. +*/ +#define USX2Y_NRPACKS_VARIABLE 1 + +#ifdef USX2Y_NRPACKS_VARIABLE +extern int nrpacks; +#define nr_of_packs () nrpacks +#else +#define nr_of_packs () USX2Y_NRPACKS +#endif #define URBS_ASYNC_SEQ 10#define URB_DATA_LEN_ASYNC_SEQ 32
sound/usb/usx2y/usbusx2yaudio.c +0 -27
@@ -28,33 +28,6 @@#include "usx2y.h" #include "usbusx2y.h" -/* Default value used for nr of packs per urb. -* 1 to 4 have been tested ok on uhci. -* To use 3 on ohci, you'd need a patch: -* look for "0000425-linux-2.6.9-rc4-mm1_ohci-hcd.patch.gz" on -* "https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000425" -* -* 1, 2 and 4 work out of the box on ohci, if I recall correctly. -* Bigger is safer operation, smaller gives lower latencies. -*/ -#define USX2Y_NRPACKS 4 - -/* If your system works ok with this module's parameter -* nrpacks set to 1, you might as well comment -* this define out, and thereby produce smaller, faster code. -* You'd also set USX2Y_NRPACKS to 1 then. -*/ -#define USX2Y_NRPACKS_VARIABLE 1 - -#ifdef USX2Y_NRPACKS_VARIABLE -static int nrpacks =USX2Y_NRPACKS ;/* number of packets per urb */ -#define nr_of_packs () nrpacks -module_param (nrpacks, int,0444 ); -MODULE_PARM_DESC (nrpacks,"Number of packets per URB." ); -#else -#define nr_of_packs () USX2Y_NRPACKS -#endif -static int usx2y_urb_capt_retire (struct snd_usx2y_substream *subs) {struct urb *urb = subs->completed_urb;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 122/207 llc: do not use skb_get() before dev_queue_xmit()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 64e6a754d33d31aa844b3ee66fb93ac84ca1565e ]
syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING.
In this case, e1000 driver calls eth_skb_pad(), while the skb is shared.
Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c
Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change.
We need to audit other skb_get() uses in net/llc.
[1]
kernel BUG at net/core/skbuff.c:2178 !
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]
--- net/llc/llc_s_ac.c | 49 +++++++++++++++++++++++++--------------------- 1 file changed, 27 insertions(+), 22 deletions(-)
net/llc/llc_s_ac.c +27 -22
@@ -24,7 +24,7 @@#include <net/llc_s_ac.h> #include <net/llc_s_ev.h> #include <net/llc_sap.h> - +#include <net/sock.h> /** * llc_sap_action_unitdata_ind - forward UI PDU to network layer
@@ -40,6 +40,26 @@ int llc_sap_action_unitdata_ind(struct llc_sap *sap, struct sk_buff *skb)return 0 ; } +static int llc_prepare_and_xmit (struct sk_buff *skb) +{ +struct llc_sap_state_ev *ev =llc_sap_ev (skb); +struct sk_buff *nskb; +int rc; + + rc =llc_mac_hdr_init (skb, ev->saddr.mac, ev->daddr.mac); +if (rc) +return rc; + + nskb =skb_clone (skb,GFP_ATOMIC ); +if (!nskb) +return -ENOMEM ; + +if (skb->sk) +skb_set_owner_w (nskb, skb->sk); + +return dev_queue_xmit (nskb); +} +/** * llc_sap_action_send_ui - sends UI PDU resp to UNITDATA REQ to MAC layer * @sap: SAP
@@ -52,17 +72,12 @@ int llc_sap_action_unitdata_ind(struct llc_sap *sap, struct sk_buff *skb)int llc_sap_action_send_ui (struct llc_sap *sap,struct sk_buff *skb) {struct llc_sap_state_ev *ev =llc_sap_ev (skb); -int rc;llc_pdu_header_init (skb,LLC_PDU_TYPE_U , ev->saddr.lsap, ev->daddr.lsap,LLC_PDU_CMD );llc_pdu_init_as_ui_cmd (skb); - rc =llc_mac_hdr_init (skb, ev->saddr.mac, ev->daddr.mac); -if (likely (!rc)) { -skb_get (skb); - rc =dev_queue_xmit (skb); - } -return rc; + +return llc_prepare_and_xmit (skb); }/**
@@ -77,17 +92,12 @@ int llc_sap_action_send_ui(struct llc_sap *sap, struct sk_buff *skb)int llc_sap_action_send_xid_c (struct llc_sap *sap,struct sk_buff *skb) {struct llc_sap_state_ev *ev =llc_sap_ev (skb); -int rc;llc_pdu_header_init (skb,LLC_PDU_TYPE_U_XID , ev->saddr.lsap, ev->daddr.lsap,LLC_PDU_CMD );llc_pdu_init_as_xid_cmd (skb,LLC_XID_NULL_CLASS_2 ,0 ); - rc =llc_mac_hdr_init (skb, ev->saddr.mac, ev->daddr.mac); -if (likely (!rc)) { -skb_get (skb); - rc =dev_queue_xmit (skb); - } -return rc; + +return llc_prepare_and_xmit (skb); }/**
@@ -133,17 +143,12 @@ int llc_sap_action_send_xid_r(struct llc_sap *sap, struct sk_buff *skb)int llc_sap_action_send_test_c (struct llc_sap *sap,struct sk_buff *skb) {struct llc_sap_state_ev *ev =llc_sap_ev (skb); -int rc;llc_pdu_header_init (skb,LLC_PDU_TYPE_U , ev->saddr.lsap, ev->daddr.lsap,LLC_PDU_CMD );llc_pdu_init_as_test_cmd (skb); - rc =llc_mac_hdr_init (skb, ev->saddr.mac, ev->daddr.mac); -if (likely (!rc)) { -skb_get (skb); - rc =dev_queue_xmit (skb); - } -return rc; + +return llc_prepare_and_xmit (skb); }int llc_sap_action_send_test_r (struct llc_sap *sap,struct sk_buff *skb)
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 123/207 hwmon: fix a NULL vs IS_ERR_OR_NULL() check in xgene_hwmon_probe()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xinghuo Chen <[email protected]>
[ Upstream commit 10fce7ebe888fa8c97eee7e317a47e7603e5e78d ]
The devm_memremap() function returns error pointers on error, it doesn't return NULL.
--- drivers/hwmon/xgene-hwmon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/xgene-hwmon.c +1 -1
@@ -706,7 +706,7 @@ static int xgene_hwmon_probe(struct platform_device *pdev) goto out; } -if (!ctx->pcc_comm_addr) { +if (IS_ERR_OR_NULL (ctx->pcc_comm_addr)) {dev_err (&pdev->dev,"Failed to ioremap PCC comm region\n" ); rc = -ENOMEM ;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 124/207 drm/sched: Fix preprocessor guard
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Philipp Stanner <[email protected]>
[ Upstream commit 23e0832d6d7be2d3c713f9390c060b6f1c48bf36 ]
When writing the header guard for gpu_scheduler_trace.h, a typo, apparently, occurred.
Fix the typo and document the scope of the guard.
--- drivers/gpu/drm/scheduler/gpu_scheduler_trace.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/scheduler/gpu_scheduler_trace.h +2 -2
@@ -21,7 +21,7 @@* */ -#if !defined(_GPU_SCHED_TRACE_H) || defined(TRACE_HEADER_MULTI_READ ) +#if !defined(_GPU_SCHED_TRACE_H_) || defined(TRACE_HEADER_MULTI_READ )#define _GPU_SCHED_TRACE_H_#include <linux/stringify.h>
@@ -106,7 +106,7 @@ TRACE_EVENT(drm_sched_job_wait_dep, __entry->seqno) ); -#endif +#endif /* _GPU_SCHED_TRACE_H_ */ /* This part must be outside protection */ #undef TRACE_INCLUDE_PATH
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 125/207 be2net: fix sleeping while atomic bugs in be_ndo_bridge_getlink
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nikolay Aleksandrov <[email protected]>
[ Upstream commit 1a82d19ca2d6835904ee71e2d40fd331098f94a0 ]
Partially revert commit b71724147e73 ("be2net: replace polling with sleeping in the FW completion path") w.r.t mcc mutex it introduces and the use of usleep_range. The be2net be_ndo_bridge_getlink() callback is called with rcu_read_lock, so this code has been broken for a long time. Both the mutex_lock and the usleep_range can cause the issue Ian Kumlien reported[1]. The call path is:be_ndo_bridge_getlink -> be_cmd_get_hsw_config -> be_mcc_notify_wait -> be_mcc_wait_compl -> usleep_range()
[1] https://lore.kernel.org/netdev/CAA85sZveppNgEVa_FD+qhOMtG_AavK9_mFiU+jWrMtXmwqefGA@mail.gmail.com/
--- drivers/net/ethernet/emulex/benet/be.h | 2 +- drivers/net/ethernet/emulex/benet/be_cmds.c | 197 ++++++++++---------- drivers/net/ethernet/emulex/benet/be_main.c | 2 +- 3 files changed, 100 insertions(+), 101 deletions(-)
drivers/net/ethernet/emulex/benet/be.h +1 -1
@@ -562,7 +562,7 @@ struct be_adapter {struct be_dma_mem mbox_mem_alloced;struct be_mcc_obj mcc_obj; -struct mutex mcc_lock;/* For serializing mcc cmds to BE card */ +spinlock_t mcc_lock;/* For serializing mcc cmds to BE card */ spinlock_t mcc_cq_lock;u16 cfg_num_rx_irqs;/* configured via set-channels */
drivers/net/ethernet/emulex/benet/be_cmds.c +98 -99
787 lines not on this page · raw message
drivers/net/ethernet/emulex/benet/be_main.c +1 -1
@@ -5667,8 +5667,8 @@ static int be_drv_init(struct be_adapter *adapter) }mutex_init (&adapter->mbox_lock); -mutex_init (&adapter->mcc_lock);mutex_init (&adapter->rx_filter_lock); +spin_lock_init (&adapter->mcc_lock);spin_lock_init (&adapter->mcc_cq_lock);init_completion (&adapter->et_cmd_compl);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 126/207 net: hns3: make sure ptp clock is unregister and freed if hclge_ptp_get_cycle returns an error
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peiyang Wang <[email protected]>
[ Upstream commit b7365eab39831487a84e63a9638209b68dc54008 ]
During the initialization of ptp, hclge_ptp_get_cycle might return an error and returned directly without unregister clock and free it. To avoid that, call hclge_ptp_destroy_clock to unregist and free clock if hclge_ptp_get_cycle failed.
--- drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_ptp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_ptp.c +1 -1
@@ -483,7 +483,7 @@ int hclge_ptp_init(struct hclge_dev *hdev) ret =hclge_ptp_get_cycle (hdev);if (ret) -return ret; + goto out; } ret =hclge_ptp_int_en (hdev, true);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 127/207 drm/xe: Remove double pageflip
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Maarten Lankhorst <[email protected]>
[ Upstream commit 30bfc151f0c1ec80c27a80a7651b2c15c648ad16 ]
This is already handled below in the code by fixup_initial_plane_config.
--- drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 ---------- 1 file changed, 10 deletions(-)
drivers/gpu/drm/xe/display/xe_plane_initial.c +0 -10
@@ -194,8 +194,6 @@ intel_find_initial_plane_obj(struct intel_crtc *crtc,to_intel_plane (crtc->base.primary);struct intel_plane_state *plane_state =to_intel_plane_state (plane->base.state); -struct intel_crtc_state *crtc_state = -to_intel_crtc_state (crtc->base.state);struct drm_framebuffer *fb;struct i915_vma *vma;
@@ -241,14 +239,6 @@ intel_find_initial_plane_obj(struct intel_crtc *crtc,atomic_or (plane->frontbuffer_bit, &to_intel_frontbuffer (fb)->bits); plane_config->vma = vma; - -/* -* Flip to the newly created mapping ASAP, so we can re-use the -* first part of GGTT for WOPCM, prevent flickering, and prevent -* the lookup of sysmem scratch pages. -*/ - plane->check_plane (crtc_state, plane_state); - plane->async_flip (NULL , plane, crtc_state, plane_state, true);return ; nofb:
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 128/207 HID: hid-steam: Fix use-after-free when detaching device
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Vicki Pfau <[email protected]>
[ Upstream commit e53fc232a65f7488ab75d03a5b95f06aaada7262 ]
When a hid-steam device is removed it must clean up the client_hdev used for intercepting hidraw access. This can lead to scheduling deferred work to reattach the input device. Though the cleanup cancels the deferred work, this was done before the client_hdev itself is cleaned up, so it gets rescheduled. This patch fixes the ordering to make sure the deferred work is properly canceled.
--- drivers/hid/hid-steam.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hid/hid-steam.c +1 -1
@@ -1327,11 +1327,11 @@ static void steam_remove(struct hid_device *hdev)return ; } +hid_destroy_device (steam->client_hdev);cancel_delayed_work_sync (&steam->mode_switch);cancel_work_sync (&steam->work_connect);cancel_work_sync (&steam->rumble_work);cancel_work_sync (&steam->unregister_work); -hid_destroy_device (steam->client_hdev); steam->client_hdev =NULL ; steam->client_opened =0 ;if (steam->quirks &STEAM_QUIRK_WIRELESS ) {
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 129/207 net: ipa: Fix v4.7 resource group names
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Weiss <[email protected]>
[ Upstream commit 5eb3dc1396aa7e315486b24df80df782912334b7 ]
In the downstream IPA driver there's only one group defined for source and destination, and the destination group doesn't have a _DPL suffix.
--- drivers/net/ipa/data/ipa_data-v4.7.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
drivers/net/ipa/data/ipa_data-v4.7.c +5 -7
@@ -28,12 +28,10 @@ enum ipa_resource_type {enum ipa_rsrc_group_id {/* Source resource group identifiers */ IPA_RSRC_GROUP_SRC_UL_DL =0 , -IPA_RSRC_GROUP_SRC_UC_RX_Q ,IPA_RSRC_GROUP_SRC_COUNT ,/* Last in set; not a source group */ /* Destination resource group identifiers */ -IPA_RSRC_GROUP_DST_UL_DL_DPL =0 , -IPA_RSRC_GROUP_DST_UNUSED_1 , +IPA_RSRC_GROUP_DST_UL_DL =0 ,IPA_RSRC_GROUP_DST_COUNT ,/* Last; not a destination group */ };
@@ -81,7 +79,7 @@ static const struct ipa_gsi_endpoint_data ipa_gsi_endpoint_data[] = { }, .endpoint = { .config = { - .resource_group = IPA_RSRC_GROUP_DST_UL_DL_DPL, + .resource_group = IPA_RSRC_GROUP_DST_UL_DL, .aggregation = true, .status_enable = true, .rx = {
@@ -128,7 +126,7 @@ static const struct ipa_gsi_endpoint_data ipa_gsi_endpoint_data[] = { }, .endpoint = { .config = { - .resource_group = IPA_RSRC_GROUP_DST_UL_DL_DPL, + .resource_group = IPA_RSRC_GROUP_DST_UL_DL, .qmap = true, .aggregation = true, .rx = {
@@ -197,12 +195,12 @@ static const struct ipa_resource ipa_resource_src[] = {/* Destination resource configuration data for an SoC having IPA v4.7 */ static const struct ipa_resource ipa_resource_dst[] = { [IPA_RESOURCE_TYPE_DST_DATA_SECTORS ] = { - .limits[IPA_RSRC_GROUP_DST_UL_DL_DPL ] = { + .limits[IPA_RSRC_GROUP_DST_UL_DL ] = { .min =7 , .max =7 , }, }, [IPA_RESOURCE_TYPE_DST_DPS_DMARS ] = { - .limits[IPA_RSRC_GROUP_DST_UL_DL_DPL ] = { + .limits[IPA_RSRC_GROUP_DST_UL_DL ] = { .min =2 , .max =2 , }, },
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 130/207 net: ipa: Fix QSB data for v4.7
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Weiss <[email protected]>
[ Upstream commit 6a2843aaf551d87beb92d774f7d5b8ae007fe774 ]
As per downstream reference, max_writes should be 12 and max_reads should be 13.
--- drivers/net/ipa/data/ipa_data-v4.7.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ipa/data/ipa_data-v4.7.c +2 -2
@@ -38,8 +38,8 @@ enum ipa_rsrc_group_id {/* QSB configuration data for an SoC having IPA v4.7 */ static const struct ipa_qsb_data ipa_qsb_data[] = { [IPA_QSB_MASTER_DDR ] = { - .max_writes =8 , - .max_reads =0 ,/* no limit (hardware max) */ + .max_writes =12 , + .max_reads =13 , .max_reads_beats =120 , }, };
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 131/207 net: ipa: Enable checksum for IPA_ENDPOINT_AP_MODEM_{RX,TX} for v4.7
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Weiss <[email protected]>
[ Upstream commit 934e69669e32eb653234898424ae007bae2f636e ]
Enable the checksum option for these two endpoints in order to allow mobile data to actually work. Without this, no packets seem to make it through the IPA.
--- drivers/net/ipa/data/ipa_data-v4.7.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/ipa/data/ipa_data-v4.7.c +2 -0
@@ -104,6 +104,7 @@ static const struct ipa_gsi_endpoint_data ipa_gsi_endpoint_data[] = { .filter_support = true, .config = { .resource_group = IPA_RSRC_GROUP_SRC_UL_DL, + .checksum = true, .qmap = true, .status_enable = true, .tx = {
@@ -127,6 +128,7 @@ static const struct ipa_gsi_endpoint_data ipa_gsi_endpoint_data[] = { .endpoint = { .config = { .resource_group = IPA_RSRC_GROUP_DST_UL_DL, + .checksum = true, .qmap = true, .aggregation = true, .rx = {
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 132/207 ppp: Fix KMSAN uninit-value warning with bpf
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jiayuan Chen <[email protected]>
[ Upstream commit 4c2d14c40a68678d885eab4008a0129646805bae ]
Syzbot caught an "KMSAN: uninit-value" warning [1], which is caused by the ppp driver not initializing a 2-byte header when using socket filter.
The following code can generate a PPP filter BPF program:
'''
struct bpf_program fp;pcap_t *handle;
handle = pcap_open_dead(DLT_PPP_PPPD, 65535); pcap_compile(handle, &fp, "ip and outbound", 0, 0); bpf_dump(&fp, 1);
'''
Its output is:
'''
(000) ldh [2]
(001) jeq #0x21 jt 2 jf 5
(002) ldb [0]
(003) jeq #0x1 jt 4 jf 5
(004) ret #65535
(005) ret #0
'''
Wen can find similar code at the following link:
https://github.com/ppp-project/ppp/blob/master/pppd/options.c#L1680
The maintainer of this code repository is also the original maintainer of the ppp driver.
As you can see the BPF program skips 2 bytes of data and then reads the 'Protocol' field to determine if it's an IP packet. Then it read the first byte of the first 2 bytes to determine the direction.
The issue is that only the first byte indicating direction is initialized in current ppp driver code while the second byte is not initialized.
For normal BPF programs generated by libpcap, uninitialized data won't be used, so it's not a problem. However, for carefully crafted BPF programs, such as those generated by syzkaller [2], which start reading from offset 0, the uninitialized data will be used and caught by KMSAN.
[1] https://syzkaller.appspot.com/bug?extid=853242d9c9917165d791
[2] https://syzkaller.appspot.com/text?tag=ReproC&x=11994913980000
--- drivers/net/ppp/ppp_generic.c | 28 +++++++++++++++++++--------- 1 file changed, 19 insertions(+), 9 deletions(-)
drivers/net/ppp/ppp_generic.c +19 -9
@@ -72,6 +72,17 @@#define PPP_PROTO_LEN 2#define PPP_LCP_HDRLEN 4 +/* The filter instructions generated by libpcap are constructed +* assuming a four-byte PPP header on each packet, where the last +* 2 bytes are the protocol field defined in the RFC and the first +* byte of the first 2 bytes indicates the direction. +* The second byte is currently unused, but we still need to initialize +* it to prevent crafted BPF programs from reading them which would +* cause reading of uninitialized data. +*/ +#define PPP_FILTER_OUTBOUND_TAG 0x0100 +#define PPP_FILTER_INBOUND_TAG 0x0000 +/* * An instance of /dev/ppp can be associated with either a ppp * interface unit or a ppp channel. In both cases, file->private_data
@@ -1762,10 +1773,10 @@ ppp_send_frame(struct ppp *ppp, struct sk_buff *skb)if (proto <0x8000 ) {#ifdef CONFIG_PPP_FILTER -/* check if we should pass this packet */ -/* the filter instructions are constructed assuming -a four-byte PPP header on each packet */ - *(u8 *)skb_push (skb,2 ) =1 ; +/* check if the packet passes the pass and active filters. +* See comment for PPP_FILTER_OUTBOUND_TAG above. +*/ + *(__be16 *)skb_push (skb,2 ) =htons (PPP_FILTER_OUTBOUND_TAG );if (ppp->pass_filter &&bpf_prog_run (ppp->pass_filter, skb) ==0 ) {if (ppp->debug &1 )
@@ -2482,14 +2493,13 @@ ppp_receive_nonmp_frame(struct ppp *ppp, struct sk_buff *skb)/* network protocol frame - give it to the kernel */ #ifdef CONFIG_PPP_FILTER -/* check if the packet passes the pass and active filters */ -/* the filter instructions are constructed assuming -a four-byte PPP header on each packet */ if (ppp->pass_filter || ppp->active_filter) {if (skb_unclone (skb,GFP_ATOMIC )) goto err; - - *(u8 *)skb_push (skb,2 ) =0 ; +/* Check if the packet passes the pass and active filters. +* See comment for PPP_FILTER_INBOUND_TAG above. +*/ + *(__be16 *)skb_push (skb,2 ) =htons (PPP_FILTER_INBOUND_TAG );if (ppp->pass_filter &&bpf_prog_run (ppp->pass_filter, skb) ==0 ) {if (ppp->debug &1 )
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 133/207 ethtool: linkstate: migrate linkstate functions to support multi-PHY setups
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oleksij Rempel <[email protected]>
[ Upstream commit fe55b1d401c697c2ef126fe3ebbcaa6885fced5a ]
Adapt linkstate_get_sqi() and linkstate_get_sqi_max() to take a phy_device argument directly, enabling support for setups with multiple PHYs. The previous assumption of a single PHY attached to a net_device no longer holds.
Use ethnl_req_get_phydev() to identify the appropriate PHY device for the operation. Update linkstate_prepare_data() and related logic to accommodate this change, ensuring compatibility with multi-PHY configurations.
Stable-dep-of: 637399bf7e77 ("net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device")
--- net/ethtool/linkstate.c | 23 +++++++++++++++-------- 1 file changed, 15 insertions(+), 8 deletions(-)
net/ethtool/linkstate.c +15 -8
@@ -26,9 +26,8 @@ const struct nla_policy ethnl_linkstate_get_policy[] = { NLA_POLICY_NESTED(ethnl_header_policy_stats), }; -static int linkstate_get_sqi (struct net_device *dev) +static int linkstate_get_sqi (struct phy_device *phydev) { -struct phy_device *phydev = dev->phydev;int ret;if (!phydev)
@@ -46,9 +45,8 @@ static int linkstate_get_sqi(struct net_device *dev)return ret; } -static int linkstate_get_sqi_max (struct net_device *dev) +static int linkstate_get_sqi_max (struct phy_device *phydev) { -struct phy_device *phydev = dev->phydev;int ret;if (!phydev)
@@ -100,19 +98,28 @@ static int linkstate_prepare_data(const struct ethnl_req_info *req_base, {struct linkstate_reply_data *data =LINKSTATE_REPDATA (reply_base);struct net_device *dev = reply_base->dev; +struct nlattr **tb = info->attrs; +struct phy_device *phydev;int ret; + phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_LINKSTATE_HEADER ], + info->extack); +if (IS_ERR (phydev)) { + ret =PTR_ERR (phydev); + goto out; + } + ret =ethnl_ops_begin (dev);if (ret <0 )return ret; data->link =__ethtool_get_link (dev); - ret =linkstate_get_sqi (dev); + ret =linkstate_get_sqi (phydev);if (linkstate_sqi_critical_error (ret)) goto out; data->sqi = ret; - ret =linkstate_get_sqi_max (dev); + ret =linkstate_get_sqi_max (phydev);if (linkstate_sqi_critical_error (ret)) goto out; data->sqi_max = ret;
@@ -127,9 +134,9 @@ static int linkstate_prepare_data(const struct ethnl_req_info *req_base, sizeof(data->link_stats) / 8);if (req_base->flags ÐTOOL_FLAG_STATS ) { -if (dev->phydev) +if (phydev) data->link_stats.link_down_events = -READ_ONCE (dev->phydev->link_down_events); +READ_ONCE (phydev->link_down_events);if (dev->ethtool_ops->get_link_ext_stats) dev->ethtool_ops->get_link_ext_stats(dev,
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 134/207 net: ethtool: plumb PHY stats to PHY drivers
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jakub Kicinski <[email protected]>
[ Upstream commit b7a2c1fe6b55364e61b4b54b991eb43a47bb1104 ]
Introduce support for standardized PHY statistics reporting in ethtool by extending the PHYLIB framework. Add the functions phy_ethtool_get_phy_stats() and phy_ethtool_get_link_ext_stats() to provide a consistent interface for retrieving PHY-level and link-specific statistics. These functions are used within the ethtool implementation to avoid direct access to the phy_device structure outside of the PHYLIB framework.
A new structure, ethtool_phy_stats, is introduced to standardize PHY statistics such as packet counts, byte counts, and error counters. Drivers are updated to include callbacks for retrieving PHY and link-specific statistics, ensuring values are explicitly set only for supported fields, initialized with ETHTOOL_STAT_NOT_SET to avoid ambiguity.
Stable-dep-of: 637399bf7e77 ("net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device")
--- drivers/net/phy/phy.c | 43 ++++++++++++++++++++++++++++++++++++ drivers/net/phy/phy_device.c | 2 ++ include/linux/ethtool.h | 23 +++++++++++++++++++ include/linux/phy.h | 36 ++++++++++++++++++++++++++++++ include/linux/phylib_stubs.h | 42 +++++++++++++++++++++++++++++++++++ net/ethtool/linkstate.c | 5 +++-- net/ethtool/stats.c | 18 +++++++++++++++ 7 files changed, 167 insertions(+), 2 deletions(-)
drivers/net/phy/phy.c +43 -0
@@ -615,6 +615,49 @@ int phy_ethtool_get_stats(struct phy_device *phydev, }EXPORT_SYMBOL (phy_ethtool_get_stats); +/** +* __phy_ethtool_get_phy_stats - Retrieve standardized PHY statistics +* @phydev: Pointer to the PHY device +* @phy_stats: Pointer to ethtool_eth_phy_stats structure +* @phydev_stats: Pointer to ethtool_phy_stats structure +* +* Fetches PHY statistics using a kernel-defined interface for consistent +* diagnostics. Unlike phy_ethtool_get_stats(), which allows custom stats, +* this function enforces a standardized format for better interoperability. +*/ +void __phy_ethtool_get_phy_stats (struct phy_device *phydev, +struct ethtool_eth_phy_stats *phy_stats, +struct ethtool_phy_stats *phydev_stats) +{ +if (!phydev->drv || !phydev->drv->get_phy_stats) +return ; + +mutex_lock (&phydev->lock); + phydev->drv->get_phy_stats (phydev, phy_stats, phydev_stats); +mutex_unlock (&phydev->lock); +} + +/** +* __phy_ethtool_get_link_ext_stats - Retrieve extended link statistics for a PHY +* @phydev: Pointer to the PHY device +* @link_stats: Pointer to the structure to store extended link statistics +* +* Populates the ethtool_link_ext_stats structure with link down event counts +* and additional driver-specific link statistics, if available. +*/ +void __phy_ethtool_get_link_ext_stats (struct phy_device *phydev, +struct ethtool_link_ext_stats *link_stats) +{ + link_stats->link_down_events =READ_ONCE (phydev->link_down_events); + +if (!phydev->drv || !phydev->drv->get_link_stats) +return ; + +mutex_lock (&phydev->lock); + phydev->drv->get_link_stats (phydev, link_stats); +mutex_unlock (&phydev->lock); +} +/** * phy_ethtool_get_plca_cfg - Get PLCA RS configuration * @phydev: the phy_device struct
drivers/net/phy/phy_device.c +2 -0
@@ -3773,6 +3773,8 @@ static const struct ethtool_phy_ops phy_ethtool_phy_ops = {static const struct phylib_stubs __phylib_stubs = { .hwtstamp_get = __phy_hwtstamp_get, .hwtstamp_set = __phy_hwtstamp_set, + .get_phy_stats = __phy_ethtool_get_phy_stats, + .get_link_ext_stats = __phy_ethtool_get_link_ext_stats, };static void phylib_register_stubs (void )
include/linux/ethtool.h +23 -0
@@ -412,6 +412,29 @@ struct ethtool_eth_phy_stats { ); }; +/** +* struct ethtool_phy_stats - PHY-level statistics counters +* @rx_packets: Total successfully received frames +* @rx_bytes: Total successfully received bytes +* @rx_errors: Total received frames with errors (e.g., CRC errors) +* @tx_packets: Total successfully transmitted frames +* @tx_bytes: Total successfully transmitted bytes +* @tx_errors: Total transmitted frames with errors +* +* This structure provides a standardized interface for reporting +* PHY-level statistics counters. It is designed to expose statistics +* commonly provided by PHYs but not explicitly defined in the IEEE +* 802.3 standard. +*/ +struct ethtool_phy_stats { +u64 rx_packets; +u64 rx_bytes; +u64 rx_errors; +u64 tx_packets; +u64 tx_bytes; +u64 tx_errors; +}; +/* Basic IEEE 802.3 MAC Ctrl statistics (30.3.3.*), not otherwise exposed * via a more targeted API. */
include/linux/phy.h +36 -0
@@ -1090,6 +1090,35 @@ struct phy_driver {int (*cable_test_get_status)(struct phy_device *dev,bool *finished);/* Get statistics from the PHY using ethtool */ +/** +* @get_phy_stats: Retrieve PHY statistics. +* @dev: The PHY device for which the statistics are retrieved. +* @eth_stats: structure where Ethernet PHY stats will be stored. +* @stats: structure where additional PHY-specific stats will be stored. +* +* Retrieves the supported PHY statistics and populates the provided +* structures. The input structures are pre-initialized with +* `ETHTOOL_STAT_NOT_SET`, and the driver must only modify members +* corresponding to supported statistics. Unmodified members will remain +* set to `ETHTOOL_STAT_NOT_SET` and will not be returned to userspace. +*/ +void (*get_phy_stats)(struct phy_device *dev, +struct ethtool_eth_phy_stats *eth_stats, +struct ethtool_phy_stats *stats); + +/** +* @get_link_stats: Retrieve link statistics. +* @dev: The PHY device for which the statistics are retrieved. +* @link_stats: structure where link-specific stats will be stored. +* +* Retrieves link-related statistics for the given PHY device. The input +* structure is pre-initialized with `ETHTOOL_STAT_NOT_SET`, and the +* driver must only modify members corresponding to supported +* statistics. Unmodified members will remain set to +* `ETHTOOL_STAT_NOT_SET` and will not be returned to userspace. +*/ +void (*get_link_stats)(struct phy_device *dev, +struct ethtool_link_ext_stats *link_stats);/** @get_sset_count: Number of statistic counters */ int (*get_sset_count)(struct phy_device *dev);/** @get_strings: Names of the statistic counters */
@@ -2065,6 +2094,13 @@ int phy_ethtool_get_strings(struct phy_device *phydev, u8 *data);int phy_ethtool_get_sset_count (struct phy_device *phydev);int phy_ethtool_get_stats (struct phy_device *phydev,struct ethtool_stats *stats,u64 *data); + +void __phy_ethtool_get_phy_stats (struct phy_device *phydev, +struct ethtool_eth_phy_stats *phy_stats, +struct ethtool_phy_stats *phydev_stats); +void __phy_ethtool_get_link_ext_stats (struct phy_device *phydev, +struct ethtool_link_ext_stats *link_stats); +int phy_ethtool_get_plca_cfg (struct phy_device *phydev,struct phy_plca_cfg *plca_cfg); int phy_ethtool_set_plca_cfg(struct phy_device *phydev,
include/linux/phylib_stubs.h +42 -0
64 lines not on this page · raw message
net/ethtool/linkstate.c +3 -2
@@ -3,6 +3,7 @@#include "netlink.h" #include "common.h" #include <linux/phy.h> +#include <linux/phylib_stubs.h> struct linkstate_req_info {struct ethnl_req_info base;
@@ -135,8 +136,8 @@ static int linkstate_prepare_data(const struct ethnl_req_info *req_base,if (req_base->flags ÐTOOL_FLAG_STATS ) {if (phydev) - data->link_stats.link_down_events = -READ_ONCE (phydev->link_down_events); +phy_ethtool_get_link_ext_stats (phydev, + &data->link_stats);if (dev->ethtool_ops->get_link_ext_stats) dev->ethtool_ops->get_link_ext_stats(dev,
net/ethtool/stats.c +18 -0
@@ -1,5 +1,8 @@// SPDX-License-Identifier: GPL-2.0-only +#include <linux/phy.h> +#include <linux/phylib_stubs.h> +#include "netlink.h" #include "common.h" #include "bitset.h"
@@ -20,6 +23,7 @@ struct stats_reply_data {struct ethtool_eth_mac_stats mac_stats;struct ethtool_eth_ctrl_stats ctrl_stats;struct ethtool_rmon_stats rmon_stats; +struct ethtool_phy_stats phydev_stats; );const struct ethtool_rmon_hist_range *rmon_ranges; };
@@ -120,8 +124,15 @@ static int stats_prepare_data(const struct ethnl_req_info *req_base,struct stats_reply_data *data =STATS_REPDATA (reply_base);enum ethtool_mac_stats_src src = req_info->src;struct net_device *dev = reply_base->dev; +struct nlattr **tb = info->attrs; +struct phy_device *phydev;int ret; + phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_STATS_HEADER ], + info->extack); +if (IS_ERR (phydev)) +return PTR_ERR (phydev); + ret =ethnl_ops_begin (dev);if (ret <0 )return ret;
@@ -145,6 +156,13 @@ static int stats_prepare_data(const struct ethnl_req_info *req_base, data->ctrl_stats.src = src; data->rmon_stats.src = src; +if (test_bit (ETHTOOL_STATS_ETH_PHY , req_info->stat_mask) && + src ==ETHTOOL_MAC_STATS_SRC_AGGREGATE ) { +if (phydev) +phy_ethtool_get_phy_stats (phydev, &data->phy_stats, + &data->phydev_stats); + } +if (test_bit (ETHTOOL_STATS_ETH_PHY , req_info->stat_mask) && dev->ethtool_ops->get_eth_phy_stats) dev->ethtool_ops->get_eth_phy_stats (dev, &data->phy_stats);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 135/207 net: ethtool: netlink: Allow NULL nlattrs when getting a phy_device
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Maxime Chevallier <[email protected]>
[ Upstream commit 637399bf7e77797811adf340090b561a8f9d1213 ]
ethnl_req_get_phydev() is used to lookup a phy_device, in the case an ethtool netlink command targets a specific phydev within a netdev's topology.
It takes as a parameter a const struct nlattr *header that's used for error handling :
if (!phydev) {
NL_SET_ERR_MSG_ATTR(extack, header,
"no phy matching phyindex");
return ERR_PTR(-ENODEV);
}In the notify path after a ->set operation however, there's no request attributes available.
The typical callsite for the above function looks like:
phydev = ethnl_req_get_phydev(req_base, tb[ETHTOOL_A_XXX_HEADER], info->extack);
So, when tb is NULL (such as in the ethnl notify path), we have a nice crash.
It turns out that there's only the PLCA command that is in that case, as the other phydev-specific commands don't have a notification.
This commit fixes the crash by passing the cmd index and the nlattr array separately, allowing NULL-checking it directly inside the helper.
--- net/ethtool/cabletest.c | 8 ++++---- net/ethtool/linkstate.c | 2 +- net/ethtool/netlink.c | 6 +++--- net/ethtool/netlink.h | 5 +++-- net/ethtool/phy.c | 2 +- net/ethtool/plca.c | 6 +++--- net/ethtool/pse-pd.c | 4 ++-- net/ethtool/stats.c | 2 +- net/ethtool/strset.c | 2 +- 9 files changed, 19 insertions(+), 18 deletions(-)
net/ethtool/cabletest.c +4 -4
@@ -72,8 +72,8 @@ int ethnl_act_cable_test(struct sk_buff *skb, struct genl_info *info) dev = req_info.dev;rtnl_lock (); - phydev =ethnl_req_get_phydev (&req_info, - tb[ETHTOOL_A_CABLE_TEST_HEADER ], + phydev =ethnl_req_get_phydev (&req_info, tb, +ETHTOOL_A_CABLE_TEST_HEADER , info->extack);if (IS_ERR_OR_NULL (phydev)) { ret = -EOPNOTSUPP ;
@@ -339,8 +339,8 @@ int ethnl_act_cable_test_tdr(struct sk_buff *skb, struct genl_info *info) goto out_dev_put;rtnl_lock (); - phydev =ethnl_req_get_phydev (&req_info, - tb[ETHTOOL_A_CABLE_TEST_TDR_HEADER ], + phydev =ethnl_req_get_phydev (&req_info, tb, +ETHTOOL_A_CABLE_TEST_TDR_HEADER , info->extack);if (IS_ERR_OR_NULL (phydev)) { ret = -EOPNOTSUPP ;
net/ethtool/linkstate.c +1 -1
@@ -103,7 +103,7 @@ static int linkstate_prepare_data(const struct ethnl_req_info *req_base,struct phy_device *phydev;int ret; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_LINKSTATE_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_LINKSTATE_HEADER , info->extack);if (IS_ERR (phydev)) { ret =PTR_ERR (phydev);
net/ethtool/netlink.c +3 -3
@@ -210,7 +210,7 @@ int ethnl_parse_header_dev_get(struct ethnl_req_info *req_info, }struct phy_device *ethnl_req_get_phydev (const struct ethnl_req_info *req_info, -const struct nlattr *header, +struct nlattr **tb,unsigned int header,struct netlink_ext_ack *extack) {struct phy_device *phydev;
@@ -224,8 +224,8 @@ struct phy_device *ethnl_req_get_phydev(const struct ethnl_req_info *req_info,return req_info->dev->phydev; phydev =phy_link_topo_get_phy (req_info->dev, req_info->phy_index); -if (!phydev) { -NL_SET_ERR_MSG_ATTR (extack, header, +if (!phydev && tb) { +NL_SET_ERR_MSG_ATTR (extack, tb[header],"no phy matching phyindex" );return ERR_PTR (-ENODEV ); }
net/ethtool/netlink.h +3 -2
@@ -275,7 +275,8 @@ static inline void ethnl_parse_header_dev_put(struct ethnl_req_info *req_info)* ethnl_req_get_phydev() - Gets the phy_device targeted by this request, * if any. Must be called under rntl_lock(). * @req_info: The ethnl request to get the phy from. -* @header: The netlink header, used for error reporting. +* @tb: The netlink attributes array, for error reporting. +* @header: The netlink header index, used for error reporting. * @extack: The netlink extended ACK, for error reporting. * * The caller must hold RTNL, until it's done interacting with the returned
@@ -289,7 +290,7 @@ static inline void ethnl_parse_header_dev_put(struct ethnl_req_info *req_info)* is returned. */ struct phy_device *ethnl_req_get_phydev (const struct ethnl_req_info *req_info, -const struct nlattr *header, +struct nlattr **tb,unsigned int header,struct netlink_ext_ack *extack);/**
net/ethtool/phy.c +1 -1
@@ -125,7 +125,7 @@ static int ethnl_phy_parse_request(struct ethnl_req_info *req_base,struct phy_req_info *req_info =PHY_REQINFO (req_base);struct phy_device *phydev; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_PHY_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_PHY_HEADER , extack);if (!phydev)return 0 ;
net/ethtool/plca.c +3 -3
@@ -62,7 +62,7 @@ static int plca_get_cfg_prepare_data(const struct ethnl_req_info *req_base,struct phy_device *phydev;int ret; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_PLCA_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_PLCA_HEADER , info->extack);// check that the PHY device is available and connected if (IS_ERR_OR_NULL (phydev)) {
@@ -152,7 +152,7 @@ ethnl_set_plca(struct ethnl_req_info *req_info, struct genl_info *info)bool mod = false;int ret; - phydev =ethnl_req_get_phydev (req_info, tb[ETHTOOL_A_PLCA_HEADER ], + phydev =ethnl_req_get_phydev (req_info, tb,ETHTOOL_A_PLCA_HEADER , info->extack);// check that the PHY device is available and connected if (IS_ERR_OR_NULL (phydev))
@@ -211,7 +211,7 @@ static int plca_get_status_prepare_data(const struct ethnl_req_info *req_base,struct phy_device *phydev;int ret; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_PLCA_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_PLCA_HEADER , info->extack);// check that the PHY device is available and connected if (IS_ERR_OR_NULL (phydev)) {
net/ethtool/pse-pd.c +2 -2
@@ -64,7 +64,7 @@ static int pse_prepare_data(const struct ethnl_req_info *req_base,if (ret <0 )return ret; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_PSE_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_PSE_HEADER , info->extack);if (IS_ERR (phydev))return -ENODEV ;
@@ -261,7 +261,7 @@ ethnl_set_pse(struct ethnl_req_info *req_info, struct genl_info *info)struct phy_device *phydev;int ret; - phydev =ethnl_req_get_phydev (req_info, tb[ETHTOOL_A_PSE_HEADER ], + phydev =ethnl_req_get_phydev (req_info, tb,ETHTOOL_A_PSE_HEADER , info->extack); ret =ethnl_set_pse_validate (phydev, info);if (ret)
net/ethtool/stats.c +1 -1
@@ -128,7 +128,7 @@ static int stats_prepare_data(const struct ethnl_req_info *req_base,struct phy_device *phydev;int ret; - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_STATS_HEADER ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_STATS_HEADER , info->extack);if (IS_ERR (phydev))return PTR_ERR (phydev);
net/ethtool/strset.c +1 -1
@@ -299,7 +299,7 @@ static int strset_prepare_data(const struct ethnl_req_info *req_base,return 0 ; } - phydev =ethnl_req_get_phydev (req_base, tb[ETHTOOL_A_HEADER_FLAGS ], + phydev =ethnl_req_get_phydev (req_base, tb,ETHTOOL_A_HEADER_FLAGS , info->extack);/* phydev can be NULL, check for errors only */
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 136/207 vlan: enforce underlying device type
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oscar Maes <[email protected]>
[ Upstream commit b33a534610067ade2bdaf2052900aaad99701353 ]
Currently, VLAN devices can be created on top of non-ethernet devices.
Besides the fact that it doesn't make much sense, this also causes a bug which leaks the address of a kernel function to usermode.
When creating a VLAN device, we initialize GARP (garp_init_applicant) and MRP (mrp_init_applicant) for the underlying device.
As part of the initialization process, we add the multicast address of each applicant to the underlying device, by calling dev_mc_add.
__dev_mc_add uses dev->addr_len to determine the length of the new multicast address.
This causes an out-of-bounds read if dev->addr_len is greater than 6, since the multicast addresses provided by GARP and MRP are only 6 bytes long.
This behaviour can be reproduced using the following commands:
ip tunnel add gretest mode ip6gre local ::1 remote ::2 dev lo ip l set up dev gretest
ip link add link gretest name vlantest type vlan id 100
Then, the following command will display the address of garp_pdu_rcv:
ip maddr show | grep 01:80:c2:00:00:21
Fix the bug by enforcing the type of the underlying device during VLAN device initialization.
--- net/8021q/vlan.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/8021q/vlan.c +2 -1
@@ -131,7 +131,8 @@ int vlan_check_real_dev(struct net_device *real_dev, {const char *name = real_dev->name; -if (real_dev->features &NETIF_F_VLAN_CHALLENGED ) { +if (real_dev->features &NETIF_F_VLAN_CHALLENGED || + real_dev->type !=ARPHRD_ETHER ) {pr_info ("VLANs not supported on %s\n" , name);NL_SET_ERR_MSG_MOD (extack,"VLANs not supported on device" );return -EOPNOTSUPP ;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 137/207 x86/sgx: Fix size overflows in sgx_encl_create()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jarkko Sakkinen <[email protected]>
[ Upstream commit 0d3e0dfd68fb9e6b0ec865be9f3377cc3ff55733 ]
The total size calculated for EPC can overflow u64 given the added up page for SECS. Further, the total size calculated for shmem can overflow even when the EPC size stays within limits of u64, given that it adds the extra space for 128 byte PCMD structures (one for each page).
Address this by pre-evaluating the micro-architectural requirement of
SGX: the address space size must be power of two. This is eventually checked up by ECREATE but the pre-check has the additional benefit of making sure that there is some space for additional data.
--- arch/x86/kernel/cpu/sgx/ioctl.c | 7 +++++++ 1 file changed, 7 insertions(+)
arch/x86/kernel/cpu/sgx/ioctl.c +7 -0
@@ -64,6 +64,13 @@ static int sgx_encl_create(struct sgx_encl *encl, struct sgx_secs *secs)struct file *backing;long ret; +/* +* ECREATE would detect this too, but checking here also ensures +* that the 'encl_size' calculations below can never overflow. +*/ +if (!is_power_of_2 (secs->size)) +return -EINVAL ; + va_page =sgx_encl_grow (encl, true);if (IS_ERR (va_page))return PTR_ERR (va_page);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 138/207 exfat: fix just enough dentries but allocate a new cluster to dir
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuezhang Mo <[email protected]>
[ Upstream commit 6697f819a10b238ccf01998c3f203d65d8374696 ]
This commit fixes the condition for allocating cluster to parent directory to avoid allocating new cluster to parent directory when there are just enough empty directory entries at the end of the parent directory.
--- fs/exfat/namei.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/exfat/namei.c +1 -1
@@ -237,7 +237,7 @@ static int exfat_search_empty_slot(struct super_block *sb, dentry =0 ; } -while (dentry + num_entries < total_entries && +while (dentry + num_entries <= total_entries && clu.dir !=EXFAT_EOF_CLUSTER ) { i = dentry & (dentries_per_clu -1 );
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 139/207 exfat: fix soft lockup in exfat_clear_bitmap
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Namjae Jeon <[email protected]>
[ Upstream commit 9da33619e0ca53627641bc97d1b93ec741299111 ]
bitmap clear loop will take long time in __exfat_free_cluster() if data size of file/dir enty is invalid.
If cluster bit in bitmap is already clear, stop clearing bitmap go to out of loop.
--- fs/exfat/balloc.c | 10 ++++++++-- fs/exfat/exfat_fs.h | 2 +- fs/exfat/fatent.c | 11 +++++++---- 3 files changed, 16 insertions(+), 7 deletions(-)
fs/exfat/balloc.c +8 -2
@@ -141,7 +141,7 @@ int exfat_set_bitmap(struct inode *inode, unsigned int clu, bool sync)return 0 ; } -void exfat_clear_bitmap (struct inode *inode,unsigned int clu,bool sync) +int exfat_clear_bitmap (struct inode *inode,unsigned int clu,bool sync) {int i, b;unsigned int ent_idx;
@@ -150,13 +150,17 @@ void exfat_clear_bitmap(struct inode *inode, unsigned int clu, bool sync)struct exfat_mount_options *opts = &sbi->options;if (!is_valid_cluster (sbi, clu)) -return ; +return -EIO ; ent_idx =CLUSTER_TO_BITMAP_ENT (clu); i =BITMAP_OFFSET_SECTOR_INDEX (sb, ent_idx); b =BITMAP_OFFSET_BIT_IN_SECTOR (sb, ent_idx); +if (!test_bit_le (b, sbi->vol_amap[i]->b_data)) +return -EIO ; +clear_bit_le (b, sbi->vol_amap[i]->b_data); +exfat_update_bh (sbi->vol_amap[i], sync);if (opts->discard) {
@@ -171,6 +175,8 @@ void exfat_clear_bitmap(struct inode *inode, unsigned int clu, bool sync) opts->discard =0 ; } } + +return 0 ; }/*
fs/exfat/exfat_fs.h +1 -1
@@ -456,7 +456,7 @@ int exfat_count_num_clusters(struct super_block *sb,int exfat_load_bitmap (struct super_block *sb);void exfat_free_bitmap (struct exfat_sb_info *sbi);int exfat_set_bitmap (struct inode *inode,unsigned int clu,bool sync); -void exfat_clear_bitmap (struct inode *inode,unsigned int clu,bool sync); +int exfat_clear_bitmap (struct inode *inode,unsigned int clu,bool sync);unsigned int exfat_find_free_bitmap (struct super_block *sb,unsigned int clu);int exfat_count_used_clusters (struct super_block *sb,unsigned int *ret_count);int exfat_trim_fs (struct inode *inode,struct fstrim_range *range);
fs/exfat/fatent.c +7 -4
@@ -175,6 +175,7 @@ static int __exfat_free_cluster(struct inode *inode, struct exfat_chain *p_chainBITMAP_OFFSET_SECTOR_INDEX (sb,CLUSTER_TO_BITMAP_ENT (clu));if (p_chain->flags ==ALLOC_NO_FAT_CHAIN ) { +int err;unsigned int last_cluster = p_chain->dir + p_chain->size -1 ; do { bool sync = false;
@@ -189,7 +190,9 @@ static int __exfat_free_cluster(struct inode *inode, struct exfat_chain *p_chain cur_cmap_i = next_cmap_i; } -exfat_clear_bitmap (inode, clu, (sync &&IS_DIRSYNC (inode))); + err =exfat_clear_bitmap (inode, clu, (sync &&IS_DIRSYNC (inode))); +if (err) +break ; clu++; num_clusters++; }while (num_clusters < p_chain->size);
@@ -210,12 +213,13 @@ static int __exfat_free_cluster(struct inode *inode, struct exfat_chain *p_chain cur_cmap_i = next_cmap_i; } -exfat_clear_bitmap (inode, clu, (sync &&IS_DIRSYNC (inode))); +if (exfat_clear_bitmap (inode, clu, (sync &&IS_DIRSYNC (inode)))) +break ; clu = n_clu; num_clusters++;if (err) - goto dec_used_clus; +break ;if (num_clusters >= sbi->num_clusters -EXFAT_FIRST_CLUSTER ) {/*
@@ -229,7 +233,6 @@ static int __exfat_free_cluster(struct inode *inode, struct exfat_chain *p_chain }while (clu !=EXFAT_EOF_CLUSTER ); } -dec_used_clus: sbi->used_clusters -= num_clusters;return 0 ; }
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 140/207 exfat: short-circuit zero-byte writes in exfat_file_write_iter
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Sandeen <[email protected]>
[ Upstream commit fda94a9919fd632033979ad7765a99ae3cab9289 ]
When generic_write_checks() returns zero, it means that iov_iter_count() is zero, and there is no work to do.
Simply return success like all other filesystems do, rather than proceeding down the write path, which today yields an -EFAULT in generic_perform_write() via the (fault_in_iov_iter_readable(i, bytes) == bytes) check when bytes == 0.
--- fs/exfat/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/exfat/file.c +1 -1
@@ -587,7 +587,7 @@ static ssize_t exfat_file_write_iter(struct kiocb *iocb, struct iov_iter *iter) valid_size = ei->valid_size; ret =generic_write_checks (iocb, iter); -if (ret <0 ) +if (ret <=0 ) goto unlock;if (iocb->ki_flags &IOCB_DIRECT ) {
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 141/207 net-timestamp: support TCP GSO case for a few missing flags
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Xing <[email protected]>
[ Upstream commit 3c9231ea6497dfc50ac0ef69fff484da27d0df66 ]
When I read through the TSO codes, I found out that we probably miss initializing the tx_flags of last seg when TSO is turned off, which means at the following points no more timestamp (for this last one) will be generated. There are three flags to be handled in this patch:
1. SKBTX_HW_TSTAMP
2. SKBTX_BPF
3. SKBTX_SCHED_TSTAMP
Note that SKBTX_BPF[1] was added in 6.14.0-rc2 by commit 6b98ec7e882af ("bpf: Add BPF_SOCK_OPS_TSTAMP_SCHED_CB callback") and only belongs to net-next branch material for now. The common issue of the above three flags can be fixed by this single patch.
This patch initializes the tx_flags to SKBTX_ANY_TSTAMP like what the UDP GSO does to make the newly segmented last skb inherit the tx_flags so that requested timestamp will be generated in each certain layer, or else that last one has zero value of tx_flags which leads to no timestamp at all.
--- net/ipv4/tcp_offload.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
net/ipv4/tcp_offload.c +7 -4
@@ -13,12 +13,15 @@#include <net/tcp.h> #include <net/protocol.h> -static void tcp_gso_tstamp (struct sk_buff *skb,unsigned int ts_seq, +static void tcp_gso_tstamp (struct sk_buff *skb,struct sk_buff *gso_skb,unsigned int seq,unsigned int mss) { +u32 flags =skb_shinfo (gso_skb)->tx_flags &SKBTX_ANY_TSTAMP ; +u32 ts_seq =skb_shinfo (gso_skb)->tskey; +while (skb) {if (before (ts_seq, seq + mss)) { -skb_shinfo (skb)->tx_flags |=SKBTX_SW_TSTAMP ; +skb_shinfo (skb)->tx_flags |= flags;skb_shinfo (skb)->tskey = ts_seq;return ; }
@@ -193,8 +196,8 @@ struct sk_buff *tcp_gso_segment(struct sk_buff *skb, th =tcp_hdr (skb); seq =ntohl (th->seq); -if (unlikely (skb_shinfo (gso_skb)->tx_flags &SKBTX_SW_TSTAMP )) -tcp_gso_tstamp (segs,skb_shinfo (gso_skb)->tskey, seq, mss); +if (unlikely (skb_shinfo (gso_skb)->tx_flags &SKBTX_ANY_TSTAMP )) +tcp_gso_tstamp (segs, gso_skb, seq, mss); newcheck = ~csum_fold (csum_add (csum_unfold (th->check), delta));
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 142/207 ublk: set_params: properly check if parameters can be applied
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Uday Shankar <[email protected]>
[ Upstream commit 5ac60242b0173be83709603ebaf27a473f16c4e4 ]
The parameters set by the set_params call are only applied to the block device in the start_dev call. So if a device has already been started, a subsequently issued set_params on that device will not have the desired effect, and should return an error. There is an existing check for this
- set_params fails on devices in the LIVE state. But this check is not sufficient to cover the recovery case. In this case, the device will be in the QUIESCED or FAIL_IO states, so set_params will succeed. But this success is misleading, because the parameters will not be applied, since the device has already been started (by a previous ublk server). The bit UB_STATE_USED is set on completion of the start_dev; use it to detect and fail set_params commands which arrive too late to be applied (after start_dev).
--- drivers/block/ublk_drv.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/block/ublk_drv.c +5 -2
@@ -2716,9 +2716,12 @@ static int ublk_ctrl_set_params(struct ublk_device *ub,if (ph.len >sizeof (struct ublk_params )) ph.len =sizeof (struct ublk_params ); -/* parameters can only be changed when device isn't live */ mutex_lock (&ub->mutex); -if (ub->dev_info.state ==UBLK_S_DEV_LIVE ) { +if (test_bit (UB_STATE_USED , &ub->state)) { +/* +* Parameters can only be changed when device hasn't +* been started yet +*/ ret = -EACCES ; }else if (copy_from_user (&ub->params, argp, ph.len)) { ret = -EFAULT ;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 143/207 sched/fair: Fix potential memory corruption in child_cfs_rq_on_list
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zecheng Li <[email protected]>
[ Upstream commit 3b4035ddbfc8e4521f85569998a7569668cccf51 ]
child_cfs_rq_on_list attempts to convert a 'prev' pointer to a cfs_rq. This 'prev' pointer can originate from struct rq's leaf_cfs_rq_list, making the conversion invalid and potentially leading to memory corruption. Depending on the relative positions of leaf_cfs_rq_list and the task group (tg) pointer within the struct, this can cause a memory fault or access garbage data.
The issue arises in list_add_leaf_cfs_rq, where both cfs_rq->leaf_cfs_rq_list and rq->leaf_cfs_rq_list are added to the same leaf list. Also, rq->tmp_alone_branch can be set to rq->leaf_cfs_rq_list.
This adds a check if (prev == &rq->leaf_cfs_rq_list) after the main conditional in child_cfs_rq_on_list. This ensures that the container_of operation will convert a correct cfs_rq struct.
This check is sufficient because only cfs_rqs on the same CPU are added to the list, so verifying the 'prev' pointer against the current rq's list head is enough.
Fixes a potential memory corruption issue that due to current struct layout might not be manifesting as a crash but could lead to unpredictable behavior when the layout changes.
--- kernel/sched/fair.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
kernel/sched/fair.c +4 -2
@@ -4046,15 +4046,17 @@ static inline bool child_cfs_rq_on_list(struct cfs_rq *cfs_rq) {struct cfs_rq *prev_cfs_rq;struct list_head *prev; +struct rq *rq =rq_of (cfs_rq);if (cfs_rq->on_list) { prev = cfs_rq->leaf_cfs_rq_list.prev; }else { -struct rq *rq =rq_of (cfs_rq); - prev = rq->tmp_alone_branch; } +if (prev == &rq->leaf_cfs_rq_list) +return false; + prev_cfs_rq = container_of(prev, struct cfs_rq, leaf_cfs_rq_list);return (prev_cfs_rq->tg->parent == cfs_rq->tg);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 144/207 nvme-tcp: fix signedness bug in nvme_tcp_init_connection()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
[ Upstream commit 528361c49962708a60f51a1afafeb00987cebedf ]
The kernel_recvmsg() function returns an int which could be either negative error codes or the number of bytes received. The problem is that the condition:
if (ret < sizeof(*icresp)) {is type promoted to type unsigned long and negative values are treated as high positive values which is success, when they should be treated as failure. Handle invalid positive returns separately from negative error codes to avoid this problem.
--- drivers/nvme/host/tcp.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/nvme/host/tcp.c +3 -3
@@ -1521,11 +1521,11 @@ static int nvme_tcp_init_connection(struct nvme_tcp_queue *queue) msg.msg_flags =MSG_WAITALL ; ret =kernel_recvmsg (queue->sock, &msg, &iov,1 , iov.iov_len, msg.msg_flags); -if (ret <sizeof (*icresp)) { +if (ret >=0 && ret <sizeof (*icresp)) + ret = -ECONNRESET ; +if (ret <0 ) {pr_warn ("queue %d: failed to receive icresp, error %d\n" ,nvme_tcp_queue_id (queue), ret); -if (ret >=0 ) - ret = -ECONNRESET ; goto free_icresp; } ret = -ENOTCONN ;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 145/207 net: dsa: mt7530: Fix traffic flooding for MMIO devices
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lorenzo Bianconi <[email protected]>
[ Upstream commit ccc2f5a436fbb0ae1fb598932a9b8e48423c1959 ]
On MMIO devices (e.g. MT7988 or EN7581) unicast traffic received on lanX port is flooded on all other user ports if the DSA switch is configured without VLAN support since PORT_MATRIX in PCR regs contains all user ports. Similar to MDIO devices (e.g. MT7530 and MT7531) fix the issue defining default VLAN-ID 0 for MT7530 MMIO devices.
--- drivers/net/dsa/mt7530.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
drivers/net/dsa/mt7530.c +2 -6
@@ -2591,7 +2591,8 @@ mt7531_setup_common(struct dsa_switch *ds)if (ret <0 )return ret; -return 0 ; +/* Setup VLAN ID 0 for VLAN-unaware bridges */ +return mt7530_setup_vlan0 (priv); } static int
@@ -2687,11 +2688,6 @@ mt7531_setup(struct dsa_switch *ds)if (ret)return ret; -/* Setup VLAN ID 0 for VLAN-unaware bridges */ - ret =mt7530_setup_vlan0 (priv); -if (ret) -return ret; - ds->assisted_learning_on_cpu_port = true; ds->mtu_enforcement_ingress = true;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 146/207 drm/bochs: Fix DPMS regression
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
[ Upstream commit 80da96d735094ea22985ced98bc57fe3a4422921 ]
The recent rewrite with the use of regular atomic helpers broke the DPMS unblanking on X11. Fix it by moving the call of bochs_hw_blank(false) from CRTC mode_set_nofb() to atomic_enable().
--- drivers/gpu/drm/tiny/bochs.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/tiny/bochs.c +3 -2
@@ -335,8 +335,6 @@ static void bochs_hw_setmode(struct bochs_device *bochs, struct drm_display_mode bochs->xres, bochs->yres, bochs->bpp, bochs->yres_virtual); -bochs_hw_blank (bochs, false); -bochs_dispi_write (bochs,VBE_DISPI_INDEX_ENABLE ,0 );bochs_dispi_write (bochs,VBE_DISPI_INDEX_BPP , bochs->bpp);bochs_dispi_write (bochs,VBE_DISPI_INDEX_XRES , bochs->xres);
@@ -506,6 +504,9 @@ static int bochs_crtc_helper_atomic_check(struct drm_crtc *crtc,static void bochs_crtc_helper_atomic_enable (struct drm_crtc *crtc,struct drm_atomic_state *state) { +struct bochs_device *bochs =to_bochs_device (crtc->dev); + +bochs_hw_blank (bochs, false); } static void bochs_crtc_helper_atomic_disable(struct drm_crtc *crtc,
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 147/207 mctp i3c: handle NULL header address
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matt Johnston <[email protected]>
[ Upstream commit cf7ee25e70c6edfac4553d6b671e8b19db1d9573 ]
daddr can be NULL if there is no neighbour table entry present, in that case the tx packet should be dropped.
saddr will usually be set by MCTP core, but check for NULL in case a packet is transmitted by a different protocol.
--- drivers/net/mctp/mctp-i3c.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/net/mctp/mctp-i3c.c +3 -0
@@ -507,6 +507,9 @@ static int mctp_i3c_header_create(struct sk_buff *skb, struct net_device *dev, {struct mctp_i3c_internal_hdr *ihdr; +if (!daddr || !saddr) +return -EINVAL ; +skb_push (skb,sizeof (struct mctp_i3c_internal_hdr ));skb_reset_mac_header (skb); ihdr = (void *)skb_mac_header (skb);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 148/207 net: ipv6: fix dst ref loop in ila lwtunnel
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Justin Iurman <[email protected]>
[ Upstream commit 0e7633d7b95b67f1758aea19f8e85621c5f506a3 ]
This patch follows commit 92191dd10730 ("net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels") and, on a second thought, the same patch is also needed for ila (even though the config that triggered the issue was pathological, but still, we don't want that to happen).
--- net/ipv6/ila/ila_lwt.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/ipv6/ila/ila_lwt.c +2 -1
@@ -88,7 +88,8 @@ static int ila_output(struct net *net, struct sock *sk, struct sk_buff *skb) goto drop; } -if (ilwt->connected) { +/* cache only if we don't create a dst reference loop */ +if (ilwt->connected && orig_dst->lwtstate != dst->lwtstate) {local_bh_disable ();dst_cache_set_ip6 (&ilwt->dst_cache, dst, &fl6.saddr);local_bh_enable ();
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 149/207 net: ipv6: fix missing dst ref drop in ila lwtunnel
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Justin Iurman <[email protected]>
[ Upstream commit 5da15a9c11c1c47ef573e6805b60a7d8a1687a2a ]
Add missing skb_dst_drop() to drop reference to the old dst before adding the new dst to the skb.
--- net/ipv6/ila/ila_lwt.c | 1 + 1 file changed, 1 insertion(+)
net/ipv6/ila/ila_lwt.c +1 -0
@@ -96,6 +96,7 @@ static int ila_output(struct net *net, struct sock *sk, struct sk_buff *skb) } } +skb_dst_drop (skb);skb_dst_set (skb, dst);return dst_output (net, sk, skb);
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 150/207 gpio: rcar: Fix missing of_node_put() call
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fabrizio Castro <[email protected]>
[ Upstream commit 391b41f983bf7ff853de44704d8e14e7cc648a9b ]
of_parse_phandle_with_fixed_args() requires its caller to call into of_node_put() on the node pointer from the output structure, but such a call is currently missing.
Call into of_node_put() to rectify that.
--- drivers/gpio/gpio-rcar.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/gpio/gpio-rcar.c +6 -1
@@ -468,7 +468,12 @@ static int gpio_rcar_parse_dt(struct gpio_rcar_priv *p, unsigned int *npins) p->info = *info; ret =of_parse_phandle_with_fixed_args (np,"gpio-ranges" ,3 ,0 , &args); - *npins = ret ==0 ? args.args[2 ] :RCAR_MAX_GPIO_PER_BANK ; +if (ret) { + *npins =RCAR_MAX_GPIO_PER_BANK ; + }else { + *npins = args.args[2 ]; +of_node_put (args.np); + }if (*npins ==0 || *npins >RCAR_MAX_GPIO_PER_BANK ) { dev_warn(p->dev, "Invalid number of gpio lines %u, using %u\n",
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 151/207 Revert "drivers/card_reader/rtsx_usb: Restore interrupt based detection"
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christian Heusel <[email protected]>
commit 2397d61ee45cddb8f3bd3a3a9840ef0f0b5aa843 upstream.
This reverts commit 235b630eda072d7e7b102ab346d6b8a2c028a772.
This commit was found responsible for issues with SD card recognition, as users had to re-insert their cards in the readers and wait for a while. As for some people the SD card was involved in the boot process it also caused boot failures.
--- drivers/misc/cardreader/rtsx_usb.c | 15 --------------- 1 file changed, 15 deletions(-)
drivers/misc/cardreader/rtsx_usb.c +0 -15
@@ -286,7 +286,6 @@ static int rtsx_usb_get_status_with_bulkint rtsx_usb_get_card_status (struct rtsx_ucr *ucr,u16 *status) {int ret; -u8 interrupt_val =0 ;u16 *buf;if (!status)
@@ -309,20 +308,6 @@ int rtsx_usb_get_card_status(struct rtsx ret =rtsx_usb_get_status_with_bulk (ucr, status); } -rtsx_usb_read_register (ucr,CARD_INT_PEND , &interrupt_val); -/* Cross check presence with interrupts */ -if (*status &XD_CD ) -if (!(interrupt_val &XD_INT )) - *status &= ~XD_CD ; - -if (*status &SD_CD ) -if (!(interrupt_val &SD_INT )) - *status &= ~SD_CD ; - -if (*status &MS_CD ) -if (!(interrupt_val &MS_INT )) - *status &= ~MS_CD ; -/* usb_control_msg may return positive when success */ if (ret <0 )return ret;
Greg Kroah-Hartman
maintainerPATCH 152/207 usb: renesas_usbhs: Call clk_put()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
commit b5ea08aa883da05106fcc683d12489a4292d1122 upstream.
Clocks acquired with of_clk_get() need to be freed with clk_put(). Call clk_put() on priv->clks[0] on error path.
--- drivers/usb/renesas_usbhs/common.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/usb/renesas_usbhs/common.c +3 -1
@@ -312,8 +312,10 @@ static int usbhsc_clk_get(struct device priv->clks[1 ] =of_clk_get (dev_of_node (dev),1 );if (PTR_ERR (priv->clks[1 ]) == -ENOENT ) priv->clks[1 ] =NULL ; -else if (IS_ERR (priv->clks[1 ])) +else if (IS_ERR (priv->clks[1 ])) { +clk_put (priv->clks[0 ]);return PTR_ERR (priv->clks[1 ]); + }return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 153/207 xhci: Restrict USB4 tunnel detection for USB3 devices to Intel hosts
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marc Zyngier <[email protected]>
commit 487cfd4a8e3dc42d34a759017978a4edaf85fce0 upstream.
When adding support for USB3-over-USB4 tunnelling detection, a check for an Intel-specific capability was added. This capability, which goes by ID 206, is used without any check that we are actually dealing with an Intel host.
As it turns out, the Cadence XHCI controller *also* exposes an extended capability numbered 206 (for unknown purposes), but of course doesn't have the Intel-specific registers that the tunnelling code is trying to access. Fun follows.
The core of the problems is that the tunnelling code blindly uses vendor-specific capabilities without any check (the Intel-provided documentation I have at hand indicates that 192-255 are indeed vendor-specific).
Restrict the detection code to Intel HW for real, preventing any further explosion on my (non-Intel) HW.
--- drivers/usb/host/xhci-hub.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/usb/host/xhci-hub.c +8 -0
@@ -12,6 +12,7 @@#include <linux/slab.h> #include <linux/unaligned.h> #include <linux/bitfield.h> +#include <linux/pci.h> #include "xhci.h" #include "xhci-trace.h"
@@ -770,9 +771,16 @@ static int xhci_exit_test_mode(struct xhenum usb_link_tunnel_mode xhci_port_is_tunneled (struct xhci_hcd *xhci,struct xhci_port *port) { +struct usb_hcd *hcd;void __iomem *base;u32 offset; +/* Don't try and probe this capability for non-Intel hosts */ + hcd =xhci_to_hcd (xhci); +if (!dev_is_pci (hcd->self.controller) || +to_pci_dev (hcd->self.controller)->vendor !=PCI_VENDOR_ID_INTEL ) +return USB_LINK_UNKNOWN ; + base = &xhci->cap_regs->hc_capbase; offset =xhci_find_next_ext_cap (base,0 ,XHCI_EXT_CAPS_INTEL_SPR_SHADOW );
Greg Kroah-Hartman
maintainerPATCH 154/207 usb: renesas_usbhs: Use devm_usb_get_phy()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
commit e0c92440938930e7fa7aa6362780d39cdea34449 upstream.
The gpriv->transceiver is retrieved in probe() through usb_get_phy() but never released. Use devm_usb_get_phy() to handle this scenario.
This issue was identified through code investigation. No issue was found without this change.
--- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/renesas_usbhs/mod_gadget.c +1 -1
@@ -1094,7 +1094,7 @@ int usbhs_mod_gadget_probe(struct usbhs_ goto usbhs_mod_gadget_probe_err_gpriv; } - gpriv->transceiver =usb_get_phy (USB_PHY_TYPE_UNDEFINED ); + gpriv->transceiver =devm_usb_get_phy (dev,USB_PHY_TYPE_UNDEFINED );dev_info (dev,"%stransceiver found\n" , !IS_ERR (gpriv->transceiver) ?"" :"no " );
Greg Kroah-Hartman
maintainerPATCH 155/207 usb: hub: lack of clearing xHC resources
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pawel Laszczak <[email protected]>
commit 2b66ef84d0d2a0ea955b40bd306f5e3abbc5cf9c upstream.
The xHC resources allocated for USB devices are not released in correct order after resuming in case when while suspend device was reconnected.
This issue has been detected during the fallowing scenario:
- connect hub HS to root port
- connect LS/FS device to hub port
- wait for enumeration to finish
- force host to suspend
- reconnect hub attached to root port
- wake host
For this scenario during enumeration of USB LS/FS device the Cadence xHC reports completion error code for xHC commands because the xHC resources used for devices has not been properly released.
XHCI specification doesn't mention that device can be reset in any order so, we should not treat this issue as Cadence xHC controller bug. Similar as during disconnecting in this case the device resources should be cleared starting form the last usb device in tree toward the root hub. To fix this issue usbcore driver should call hcd->driver->reset_device for all USB devices connected to hub which was reconnected while suspending.
--- drivers/usb/core/hub.c | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+)
drivers/usb/core/hub.c +33 -0
@@ -6066,6 +6066,36 @@ void usb_hub_cleanup(void) }/* usb_hub_cleanup() */ /** +* hub_hc_release_resources - clear resources used by host controller +* @udev: pointer to device being released +* +* Context: task context, might sleep +* +* Function releases the host controller resources in correct order before +* making any operation on resuming usb device. The host controller resources +* allocated for devices in tree should be released starting from the last +* usb device in tree toward the root hub. This function is used only during +* resuming device when usb device require reinitialization – that is, when +* flag udev->reset_resume is set. +* +* This call is synchronous, and may not be used in an interrupt context. +*/ +static void hub_hc_release_resources (struct usb_device *udev) +{ +struct usb_hub *hub =usb_hub_to_struct_hub (udev); +struct usb_hcd *hcd =bus_to_hcd (udev->bus); +int i; + +/* Release up resources for all children before this device */ +for (i =0 ; i < udev->maxchild; i++) +if (hub->ports[i]->child) +hub_hc_release_resources (hub->ports[i]->child); + +if (hcd->driver->reset_device) + hcd->driver->reset_device (hcd, udev); +} + +/** * usb_reset_and_verify_device - perform a USB port reset to reinitialize a device * @udev: device to reset (not in SUSPENDED or NOTATTACHED state) *
@@ -6129,6 +6159,9 @@ static int usb_reset_and_verify_device(s bos = udev->bos; udev->bos =NULL ; +if (udev->reset_resume) +hub_hc_release_resources (udev); +mutex_lock (hcd->address0_mutex);for (i =0 ; i <PORT_INIT_TRIES ; ++i) {
Greg Kroah-Hartman
maintainerPATCH 156/207 usb: quirks: Add DELAY_INIT and NO_LPM for Prolific Mass Storage Card Reader
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Miao Li <[email protected]>
commit ff712188daa3fe3ce7e11e530b4dca3826dae14a upstream.
When used on Huawei hisi platforms, Prolific Mass Storage Card Reader which the VID:PID is in 067b:2731 might fail to enumerate at boot time and doesn't work well with LPM enabled, combination quirks:
USB_QUIRK_DELAY_INIT + USB_QUIRK_NO_LPM
fixed the problems.
--- drivers/usb/core/quirks.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/core/quirks.c +4 -0
@@ -341,6 +341,10 @@ static const struct usb_device_id usb_qu { USB_DEVICE(0x0638, 0x0a13), .driver_info = USB_QUIRK_STRING_FETCH_255 }, + /* Prolific Single-LUN Mass Storage Card Reader */ + { USB_DEVICE(0x067b, 0x2731), .driver_info = USB_QUIRK_DELAY_INIT | + USB_QUIRK_NO_LPM }, + /* Saitek Cyborg Gold Joystick */ { USB_DEVICE(0x06a3, 0x0006), .driver_info = USB_QUIRK_CONFIG_INTF_STRINGS },
Greg Kroah-Hartman
maintainerPATCH 157/207 usb: xhci: Fix host controllers "dying" after suspend and resume
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michal Pecio <[email protected]>
commit c7c1f3b05c67173f462d73d301d572b3f9e57e3b upstream.
A recent cleanup went a bit too far and dropped clearing the cycle bit of link TRBs, so it stays different from the rest of the ring half of the time. Then a race occurs: if the xHC reaches such link TRB before more commands are queued, the link's cycle bit unintentionally matches the xHC's cycle so it follows the link and waits for further commands. If more commands are queued before the xHC gets there, inc_enq() flips the bit so the xHC later sees a mismatch and stops executing commands.
This function is called before suspend and 50% of times after resuming the xHC is doomed to get stuck sooner or later. Then some Stop Endpoint command fails to complete in 5 seconds and this shows up
xhci_hcd 0000:00:10.0: xHCI host not responding to stop endpoint command xhci_hcd 0000:00:10.0: xHCI host controller not responding, assume dead xhci_hcd 0000:00:10.0: HC died; cleaning up
followed by loss of all USB decives on the affected bus. That's if you are lucky, because if Set Deq gets stuck instead, the failure is silent.
Likely responsible for kernel bug 219824. I found this while searching for possible causes of that regression and reproduced it locally before hearing back from the reporter. To repro, simply wait for link cycle to become set (debugfs), then suspend, resume and wait. To accelerate the failure I used a script which repeatedly starts and stops a UVC camera.
Some HCs get fully reinitialized on resume and they are not affected.
--- drivers/usb/host/xhci.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/usb/host/xhci.c +5 -1
@@ -779,8 +779,12 @@ static void xhci_clear_command_ring(strustruct xhci_segment *seg; ring = xhci->cmd_ring; -xhci_for_each_ring_seg (ring->first_seg, seg) +xhci_for_each_ring_seg (ring->first_seg, seg) { +/* erase all TRBs before the link */ memset (seg->trbs,0 ,sizeof (union xhci_trb ) * (TRBS_PER_SEGMENT -1 )); +/* clear link cycle bit */ + seg->trbs[TRBS_PER_SEGMENT -1 ].link.control &=cpu_to_le32 (~TRB_CYCLE ); + }xhci_initialize_ring_info (ring);/*
Greg Kroah-Hartman
maintainerPATCH 158/207 usb: typec: ucsi: Fix NULL pointer access
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrei Kuchynski <[email protected]>
commit b13abcb7ddd8d38de769486db5bd917537b32ab1 upstream.
Resources should be released only after all threads that utilize them have been destroyed.
This commit ensures that resources are not released prematurely by waiting for the associated workqueue to complete before deallocating them.
--- drivers/usb/typec/ucsi/ucsi.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
drivers/usb/typec/ucsi/ucsi.c +7 -6
@@ -1825,11 +1825,11 @@ static int ucsi_init(struct ucsi *ucsi) err_unregister:for (con = connector; con->port; con++) { +if (con->wq) +destroy_workqueue (con->wq);ucsi_unregister_partner (con);ucsi_unregister_altmodes (con,UCSI_RECIPIENT_CON );ucsi_unregister_port_psy (con); -if (con->wq) -destroy_workqueue (con->wq);usb_power_delivery_unregister_capabilities (con->port_sink_caps); con->port_sink_caps =NULL ;
@@ -2013,10 +2013,6 @@ void ucsi_unregister(struct ucsi *ucsi)for (i =0 ; i < ucsi->cap.num_connectors; i++) {cancel_work_sync (&ucsi->connector[i].work); -ucsi_unregister_partner (&ucsi->connector[i]); -ucsi_unregister_altmodes (&ucsi->connector[i], -UCSI_RECIPIENT_CON ); -ucsi_unregister_port_psy (&ucsi->connector[i]);if (ucsi->connector[i].wq) {struct ucsi_work *uwork;
@@ -2032,6 +2028,11 @@ void ucsi_unregister(struct ucsi *ucsi)destroy_workqueue (ucsi->connector[i].wq); } +ucsi_unregister_partner (&ucsi->connector[i]); +ucsi_unregister_altmodes (&ucsi->connector[i], +UCSI_RECIPIENT_CON ); +ucsi_unregister_port_psy (&ucsi->connector[i]); +usb_power_delivery_unregister_capabilities (ucsi->connector[i].port_sink_caps); ucsi->connector[i].port_sink_caps =NULL ;usb_power_delivery_unregister_capabilities (ucsi->connector[i].port_source_caps);
Greg Kroah-Hartman
maintainerPATCH 159/207 usb: renesas_usbhs: Flush the notify_hotplug_work
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
commit 552ca6b87e3778f3dd5b87842f95138162e16c82 upstream.
When performing continuous unbind/bind operations on the USB drivers available on the Renesas RZ/G2L SoC, a kernel crash with the message "Unable to handle kernel NULL pointer dereference at virtual address" may occur. This issue points to the usbhsc_notify_hotplug() function.
Flush the delayed work to avoid its execution when driver resources are unavailable.
--- drivers/usb/renesas_usbhs/common.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/renesas_usbhs/common.c +2 -0
@@ -781,6 +781,8 @@ static void usbhs_remove(struct platformdev_dbg (&pdev->dev,"usb remove\n" ); +flush_delayed_work (&priv->notify_hotplug_work); +/* power off */ if (!usbhs_get_dparam (priv, runtime_pwctrl))usbhsc_power_ctrl (priv,0 );
Greg Kroah-Hartman
maintainerPATCH 160/207 usb: xhci: Enable the TRB overfetch quirk on VIA VL805
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michal Pecio <[email protected]>
commit c133ec0e5717868c9967fa3df92a55e537b1aead upstream.
Raspberry Pi is a major user of those chips and they discovered a bug - when the end of a transfer ring segment is reached, up to four TRBs can be prefetched from the next page even if the segment ends with link TRB and on page boundary (the chip claims to support standard 4KB pages).
It also appears that if the prefetched TRBs belong to a different ring whose doorbell is later rung, they may be used without refreshing from system RAM and the endpoint will stay idle if their cycle bit is stale.
Other users complain about IOMMU faults on x86 systems, unsurprisingly.
Deal with it by using existing quirk which allocates a dummy page after each transfer ring segment. This was seen to resolve both problems. RPi came up with a more efficient solution, shortening each segment by four TRBs, but it complicated the driver and they ditched it for this quirk.
Also rename the quirk and add VL805 device ID macro.
--- drivers/usb/host/xhci-mem.c | 3 ++- drivers/usb/host/xhci-pci.c | 10 +++++++--- drivers/usb/host/xhci.h | 2 +- 3 files changed, 10 insertions(+), 5 deletions(-)
drivers/usb/host/xhci-mem.c +2 -1
@@ -2437,7 +2437,8 @@ int xhci_mem_init(struct xhci_hcd *xhci,* and our use of dma addresses in the trb_address_map radix tree needs * TRB_SEGMENT_SIZE alignment, so we pick the greater alignment need. */ -if (xhci->quirks &XHCI_ZHAOXIN_TRB_FETCH ) +if (xhci->quirks &XHCI_TRB_OVERFETCH ) +/* Buggy HC prefetches beyond segment bounds - allocate dummy space at the end */ xhci->segment_pool =dma_pool_create ("xHCI ring segments" , dev,TRB_SEGMENT_SIZE *2 ,TRB_SEGMENT_SIZE *2 , xhci->page_size *2 );else
drivers/usb/host/xhci-pci.c +7 -3
@@ -38,6 +38,8 @@#define PCI_DEVICE_ID_ETRON_EJ168 0x7023#define PCI_DEVICE_ID_ETRON_EJ188 0x7052 +#define PCI_DEVICE_ID_VIA_VL805 0x3483 +#define PCI_DEVICE_ID_INTEL_LYNXPOINT_XHCI 0x8c31#define PCI_DEVICE_ID_INTEL_LYNXPOINT_LP_XHCI 0x9c31#define PCI_DEVICE_ID_INTEL_WILDCATPOINT_LP_XHCI 0x9cb1
@@ -418,8 +420,10 @@ static void xhci_pci_quirks(struct devic pdev->device == 0x3432) xhci->quirks |=XHCI_BROKEN_STREAMS ; -if (pdev->vendor ==PCI_VENDOR_ID_VIA && pdev->device ==0x3483 ) +if (pdev->vendor ==PCI_VENDOR_ID_VIA && pdev->device ==PCI_DEVICE_ID_VIA_VL805 ) { xhci->quirks |=XHCI_LPM_SUPPORT ; + xhci->quirks |=XHCI_TRB_OVERFETCH ; + }if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && pdev->device ==PCI_DEVICE_ID_ASMEDIA_1042_XHCI ) {
@@ -467,11 +471,11 @@ static void xhci_pci_quirks(struct devicif (pdev->device ==0x9202 ) { xhci->quirks |=XHCI_RESET_ON_RESUME ; - xhci->quirks |=XHCI_ZHAOXIN_TRB_FETCH ; + xhci->quirks |=XHCI_TRB_OVERFETCH ; }if (pdev->device ==0x9203 ) - xhci->quirks |=XHCI_ZHAOXIN_TRB_FETCH ; + xhci->quirks |=XHCI_TRB_OVERFETCH ; } if (pdev->vendor == PCI_VENDOR_ID_CDNS &&
drivers/usb/host/xhci.h +1 -1
@@ -1628,7 +1628,7 @@ struct xhci_hcd {#define XHCI_EP_CTX_BROKEN_DCS BIT_ULL(42)#define XHCI_SUSPEND_RESUME_CLKS BIT_ULL(43)#define XHCI_RESET_TO_DEFAULT BIT_ULL(44) -#define XHCI_ZHAOXIN_TRB_FETCH BIT_ULL(45) +#define XHCI_TRB_OVERFETCH BIT_ULL(45)#define XHCI_ZHAOXIN_HOST BIT_ULL(46)#define XHCI_WRITE_64_HI_LO BIT_ULL(47)#define XHCI_CDNS_SCTX_QUIRK BIT_ULL(48)
Greg Kroah-Hartman
maintainerPATCH 161/207 usb: gadget: u_ether: Set is_suspend flag if remote wakeup fails
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prashanth K <[email protected]>
commit 17c2c87c37862c3e95b55f660681cc6e8d66660e upstream.
Currently while UDC suspends, u_ether attempts to remote wakeup the host if there are any pending transfers. However, if remote wakeup fails, the UDC remains suspended but the is_suspend flag is not set. And since is_suspend flag isn't set, the subsequent eth_start_xmit() would queue USB requests to suspended UDC.
To fix this, bail out from gether_suspend() only if remote wakeup operation is successful.
--- drivers/usb/gadget/function/u_ether.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/usb/gadget/function/u_ether.c +2 -2
@@ -1052,8 +1052,8 @@ void gether_suspend(struct gether *link)* There is a transfer in progress. So we trigger a remote * wakeup to inform the host. */ -ether_wakeup_host (dev->port_usb); -return ; +if (!ether_wakeup_host (dev->port_usb)) +return ; }spin_lock_irqsave (&dev->lock, flags); link->is_suspend = true;
Greg Kroah-Hartman
maintainerPATCH 162/207 usb: atm: cxacru: fix a flaw in existing endpoint checks
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nikita Zhandarovich <[email protected]>
commit c90aad369899a607cfbc002bebeafd51e31900cd upstream.
Syzbot once again identified a flaw in usb endpoint checking, see [1]. This time the issue stems from a commit authored by me (2eabb655a968 ("usb: atm: cxacru: fix endpoint checking in cxacru_bind()")).
While using usb_find_common_endpoints() may usually be enough to discard devices with wrong endpoints, in this case one needs more than just finding and identifying the sufficient number of endpoints of correct types - one needs to check the endpoint's address as well.
Since cxacru_bind() fills URBs with CXACRU_EP_CMD address in mind, switch the endpoint verification approach to usb_check_XXX_endpoints() instead to fix incomplete ep testing.
[1] Syzbot report:
usb 5-1: BOGUS urb xfer, pipe 3 != type 1
WARNING: CPU: 0 PID: 1378 at drivers/usb/core/urb.c:504 usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... RIP: 0010:usb_submit_urb+0xc4e/0x18c0 drivers/usb/core/urb.c:503 ... Call Trace: <TASK> cxacru_cm+0x3c8/0xe50 drivers/usb/atm/cxacru.c:649 cxacru_card_status drivers/usb/atm/cxacru.c:760 [inline] cxacru_bind+0xcf9/0x1150 drivers/usb/atm/cxacru.c:1223 usbatm_usb_probe+0x314/0x1d30 drivers/usb/atm/usbatm.c:1058 cxacru_usb_probe+0x184/0x220 drivers/usb/atm/cxacru.c:1377 usb_probe_interface+0x641/0xbb0 drivers/usb/core/driver.c:396 really_probe+0x2b9/0xad0 drivers/base/dd.c:658 __driver_probe_device+0x1a2/0x390 drivers/base/dd.c:800 driver_probe_device+0x50/0x430 drivers/base/dd.c:830
...
--- drivers/usb/atm/cxacru.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
drivers/usb/atm/cxacru.c +7 -6
@@ -1131,7 +1131,10 @@ static int cxacru_bind(struct usbatm_datstruct cxacru_data *instance;struct usb_device *usb_dev =interface_to_usbdev (intf);struct usb_host_endpoint *cmd_ep = usb_dev->ep_in[CXACRU_EP_CMD ]; -struct usb_endpoint_descriptor *in, *out; +static const u8 ep_addrs[] = { +CXACRU_EP_CMD +USB_DIR_IN , +CXACRU_EP_CMD +USB_DIR_OUT , +0 };int ret;/* instance init */
@@ -1179,13 +1182,11 @@ static int cxacru_bind(struct usbatm_dat }if (usb_endpoint_xfer_int (&cmd_ep->desc)) - ret =usb_find_common_endpoints (intf->cur_altsetting, -NULL ,NULL , &in, &out); + ret =usb_check_int_endpoints (intf, ep_addrs);else - ret =usb_find_common_endpoints (intf->cur_altsetting, - &in, &out,NULL ,NULL ); + ret =usb_check_bulk_endpoints (intf, ep_addrs); -if (ret) { +if (!ret) {usb_err (usbatm_instance,"cxacru_bind: interface has incorrect endpoints\n" ); ret = -ENODEV ; goto fail;
Greg Kroah-Hartman
maintainerPATCH 163/207 usb: dwc3: Set SUSPENDENABLE soon after phy init
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thinh Nguyen <[email protected]>
commit cc5bfc4e16fc1d1c520cd7bb28646e82b6e69217 upstream.
After phy initialization, some phy operations can only be executed while in lower P states. Ensure GUSB3PIPECTL.SUSPENDENABLE and GUSB2PHYCFG.SUSPHY are set soon after initialization to avoid blocking phy ops.
Previously the SUSPENDENABLE bits are only set after the controller initialization, which may not happen right away if there's no gadget driver or xhci driver bound. Revise this to clear SUSPENDENABLE bits only when there's mode switching (change in GCTL.PRTCAPDIR).
--- drivers/usb/dwc3/core.c | 69 +++++++++++++++++++++++++++++------------------- drivers/usb/dwc3/core.h | 2 - drivers/usb/dwc3/drd.c | 4 +- 3 files changed, 45 insertions(+), 30 deletions(-)
drivers/usb/dwc3/core.c +42 -27
@@ -131,11 +131,24 @@ void dwc3_enable_susphy(struct dwc3 *dwc } } -void dwc3_set_prtcap (struct dwc3 *dwc,u32 mode) +void dwc3_set_prtcap (struct dwc3 *dwc,u32 mode,bool ignore_susphy) { +unsigned int hw_mode;u32 reg; reg =dwc3_readl (dwc->regs,DWC3_GCTL ); + +/* +* For DRD controllers, GUSB3PIPECTL.SUSPENDENABLE and +* GUSB2PHYCFG.SUSPHY should be cleared during mode switching, +* and they can be set after core initialization. +*/ + hw_mode =DWC3_GHWPARAMS0_MODE (dwc->hwparams.hwparams0); +if (hw_mode ==DWC3_GHWPARAMS0_MODE_DRD && !ignore_susphy) { +if (DWC3_GCTL_PRTCAP (reg) != mode) +dwc3_enable_susphy (dwc, false); + } + reg &= ~(DWC3_GCTL_PRTCAPDIR (DWC3_GCTL_PRTCAP_OTG )); reg |=DWC3_GCTL_PRTCAPDIR (mode);dwc3_writel (dwc->regs,DWC3_GCTL , reg);
@@ -216,7 +229,7 @@ static void __dwc3_set_mode(struct work_spin_lock_irqsave (&dwc->lock, flags); -dwc3_set_prtcap (dwc, desired_dr_role); +dwc3_set_prtcap (dwc, desired_dr_role, false);spin_unlock_irqrestore (&dwc->lock, flags);
@@ -658,16 +671,7 @@ static int dwc3_ss_phy_setup(struct dwc3*/ reg &= ~DWC3_GUSB3PIPECTL_UX_EXIT_PX ; -/* -* Above DWC_usb3.0 1.94a, it is recommended to set -* DWC3_GUSB3PIPECTL_SUSPHY to '0' during coreConsultant configuration. -* So default value will be '0' when the core is reset. Application -* needs to set it to '1' after the core initialization is completed. -* -* Similarly for DRD controllers, GUSB3PIPECTL.SUSPENDENABLE must be -* cleared after power-on reset, and it can be set after core -* initialization. -*/ +/* Ensure the GUSB3PIPECTL.SUSPENDENABLE is cleared prior to phy init. */ reg &= ~DWC3_GUSB3PIPECTL_SUSPHY ;if (dwc->u2ss_inp3_quirk)
@@ -747,15 +751,7 @@ static int dwc3_hs_phy_setup(struct dwc3break ; } -/* -* Above DWC_usb3.0 1.94a, it is recommended to set -* DWC3_GUSB2PHYCFG_SUSPHY to '0' during coreConsultant configuration. -* So default value will be '0' when the core is reset. Application -* needs to set it to '1' after the core initialization is completed. -* -* Similarly for DRD controllers, GUSB2PHYCFG.SUSPHY must be cleared -* after power-on reset, and it can be set after core initialization. -*/ +/* Ensure the GUSB2PHYCFG.SUSPHY is cleared prior to phy init. */ reg &= ~DWC3_GUSB2PHYCFG_SUSPHY ;if (dwc->dis_enblslpm_quirk)
@@ -830,6 +826,25 @@ static int dwc3_phy_init(struct dwc3 *dw goto err_exit_usb3_phy; } +/* +* Above DWC_usb3.0 1.94a, it is recommended to set +* DWC3_GUSB3PIPECTL_SUSPHY and DWC3_GUSB2PHYCFG_SUSPHY to '0' during +* coreConsultant configuration. So default value will be '0' when the +* core is reset. Application needs to set it to '1' after the core +* initialization is completed. +* +* Certain phy requires to be in P0 power state during initialization. +* Make sure GUSB3PIPECTL.SUSPENDENABLE and GUSB2PHYCFG.SUSPHY are clear +* prior to phy init to maintain in the P0 state. +* +* After phy initialization, some phy operations can only be executed +* while in lower P states. Ensure GUSB3PIPECTL.SUSPENDENABLE and +* GUSB2PHYCFG.SUSPHY are set soon after initialization to avoid +* blocking phy ops. +*/ + if (!DWC3_VER_IS_WITHIN(DWC3, ANY, 194A)) +dwc3_enable_susphy (dwc, true); +return 0 ; err_exit_usb3_phy:
@@ -1568,7 +1583,7 @@ static int dwc3_core_init_mode(struct dwswitch (dwc->dr_mode) {case USB_DR_MODE_PERIPHERAL : -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE , false);if (dwc->usb2_phy)otg_set_vbus (dwc->usb2_phy->otg, false);
@@ -1580,7 +1595,7 @@ static int dwc3_core_init_mode(struct dwreturn dev_err_probe (dev, ret,"failed to initialize gadget\n" );break ;case USB_DR_MODE_HOST : -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_HOST ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_HOST , false);if (dwc->usb2_phy)otg_set_vbus (dwc->usb2_phy->otg, true);
@@ -1625,7 +1640,7 @@ static void dwc3_core_exit_mode(struct d }/* de-assert DRVVBUS for HOST and OTG mode */ -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE , true); }static void dwc3_get_software_properties (struct dwc3 *dwc)
@@ -2437,7 +2452,7 @@ static int dwc3_resume_common(struct dwcif (ret)return ret; -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_DEVICE , true);dwc3_gadget_resume (dwc);break ;case DWC3_GCTL_PRTCAP_HOST :
@@ -2445,7 +2460,7 @@ static int dwc3_resume_common(struct dwc ret =dwc3_core_init_for_resume (dwc);if (ret)return ret; -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_HOST ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_HOST , true);break ; }/* Restore GUSB2PHYCFG bits that were modified in suspend */
@@ -2474,7 +2489,7 @@ static int dwc3_resume_common(struct dwcif (ret)return ret; -dwc3_set_prtcap (dwc, dwc->current_dr_role); +dwc3_set_prtcap (dwc, dwc->current_dr_role, true);dwc3_otg_init (dwc);if (dwc->current_otg_role ==DWC3_OTG_ROLE_HOST ) {
drivers/usb/dwc3/core.h +1 -1
@@ -1556,7 +1556,7 @@ struct dwc3_gadget_ep_cmd_params {#define DWC3_HAS_OTG BIT(3)/* prototypes */ -void dwc3_set_prtcap (struct dwc3 *dwc,u32 mode); +void dwc3_set_prtcap (struct dwc3 *dwc,u32 mode,bool ignore_susphy);void dwc3_set_mode (struct dwc3 *dwc,u32 mode);u32 dwc3_core_fifo_space (struct dwc3_ep *dep,u8 type);
drivers/usb/dwc3/drd.c +2 -2
@@ -173,7 +173,7 @@ void dwc3_otg_init(struct dwc3 *dwc)* block "Initialize GCTL for OTG operation". */ /* GCTL.PrtCapDir=2'b11 */ -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_OTG ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_OTG , true);/* GUSB2PHYCFG0.SusPHY=0 */ reg =dwc3_readl (dwc->regs,DWC3_GUSB2PHYCFG (0 )); reg &= ~DWC3_GUSB2PHYCFG_SUSPHY ;
@@ -556,7 +556,7 @@ int dwc3_drd_init(struct dwc3 *dwc)dwc3_drd_update (dwc); }else { -dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_OTG ); +dwc3_set_prtcap (dwc,DWC3_GCTL_PRTCAP_OTG , true);/* use OTG block to get ID event */ irq =dwc3_otg_get_irq (dwc);
Greg Kroah-Hartman
maintainerPATCH 164/207 usb: dwc3: gadget: Prevent irq storm when TH re-executes
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Badhri Jagan Sridharan <[email protected]>
commit 69c58deec19628c8a686030102176484eb94fed4 upstream.
While commit d325a1de49d6 ("usb: dwc3: gadget: Prevent losing events in event cache") makes sure that top half(TH) does not end up overwriting the cached events before processing them when the TH gets invoked more than one time, returning IRQ_HANDLED results in occasional irq storm where the TH hogs the CPU. The irq storm can be prevented by the flag before event handler busy is cleared. Default enable interrupt moderation in all versions which support them.
ftrace event stub during dwc3 irq storm:
irq/504_dwc3-1111 ( 1111) [000] .... 70.000866: irq_handler_exit: irq=14 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000872: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000874: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000881: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000883: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000889: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000892: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000898: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000901: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000907: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000909: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000915: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000918: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000924: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000927: irq_handler_exit: irq=504 ret=handled
irq/504_dwc3-1111 ( 1111) [000] .... 70.000933: irq_handler_entry: irq=504 name=dwc3
irq/504_dwc3-1111 ( 1111) [000] .... 70.000935: irq_handler_exit: irq=504 ret=handled
....--- drivers/usb/dwc3/core.c | 16 ++++++---------- drivers/usb/dwc3/gadget.c | 10 +++++++--- 2 files changed, 13 insertions(+), 13 deletions(-)
drivers/usb/dwc3/core.c +6 -10
@@ -1830,8 +1830,6 @@ static void dwc3_get_properties(struct d dwc->tx_thr_num_pkt_prd = tx_thr_num_pkt_prd; dwc->tx_max_burst_prd = tx_max_burst_prd; - dwc->imod_interval =0 ; - dwc->tx_fifo_resize_max_num = tx_fifo_resize_max_num; }
@@ -1849,21 +1847,19 @@ static void dwc3_check_params(struct dwcunsigned int hwparam_gen =DWC3_GHWPARAMS3_SSPHY_IFC (dwc->hwparams.hwparams3); -/* Check for proper value of imod_interval */ -if (dwc->imod_interval && !dwc3_has_imod (dwc)) { -dev_warn (dwc->dev,"Interrupt moderation not supported\n" ); - dwc->imod_interval =0 ; - } -/* +* Enable IMOD for all supporting controllers. +* +* Particularly, DWC_usb3 v3.00a must enable this feature for +* the following reason: +* * Workaround for STAR 9000961433 which affects only version * 3.00a of the DWC_usb3 core. This prevents the controller * interrupt from being masked while handling events. IMOD * allows us to work around this issue. Enable it for the * affected version. */ -if (!dwc->imod_interval && - DWC3_VER_IS(DWC3, 300A)) +if (dwc3_has_imod ((dwc))) dwc->imod_interval =1 ;/* Check the maximum_speed parameter */
drivers/usb/dwc3/gadget.c +7 -3
@@ -4494,14 +4494,18 @@ static irqreturn_t dwc3_process_event_budwc3_writel (dwc->regs,DWC3_GEVNTSIZ (0 ),DWC3_GEVNTSIZ_SIZE (evt->length)); + evt->flags &= ~DWC3_EVENT_PENDING ; +/* +* Add an explicit write memory barrier to make sure that the update of +* clearing DWC3_EVENT_PENDING is observed in dwc3_check_event_buf() +*/ +wmb (); +if (dwc->imod_interval) {dwc3_writel (dwc->regs,DWC3_GEVNTCOUNT (0 ),DWC3_GEVNTCOUNT_EHB );dwc3_writel (dwc->regs,DWC3_DEV_IMOD (0 ), dwc->imod_interval); } -/* Keep the clearing of DWC3_EVENT_PENDING at the end */ - evt->flags &= ~DWC3_EVENT_PENDING ; -return ret; }
Greg Kroah-Hartman
maintainerPATCH 165/207 usb: typec: ucsi: increase timeout for PPM reset operations
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fedor Pchelkin <[email protected]>
commit bf4f9ae1cb08ccaafbe6874be6c46f59b83ae778 upstream.
It is observed that on some systems an initial PPM reset during the boot phase can trigger a timeout:
[ 6.482546] ucsi_acpi USBC000:00: failed to reset PPM! [ 6.482551] ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Still, increasing the timeout value, albeit being the most straightforward solution, eliminates the problem: the initial PPM reset may take up to ~8000-10000ms on some Lenovo laptops. When it is reset after the above period of time (or even if ucsi_reset_ppm() is not called overall), UCSI works as expected.
Moreover, if the ucsi_acpi module is loaded/unloaded manually after the system has booted, reading the CCI values and resetting the PPM works perfectly, without any timeout. Thus it's only a boot-time issue.
The reason for this behavior is not clear but it may be the consequence of some tricks that the firmware performs or be an actual firmware bug. As a workaround, increase the timeout to avoid failing the UCSI initialization prematurely.
--- drivers/usb/typec/ucsi/ucsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/typec/ucsi/ucsi.c +1 -1
@@ -25,7 +25,7 @@* difficult to estimate the time it takes for the system to process the command * before it is actually passed to the PPM. */ -#define UCSI_TIMEOUT_MS 5000 +#define UCSI_TIMEOUT_MS 10000/* * UCSI_SWAP_TIMEOUT_MS - Timeout for role swap requests
Greg Kroah-Hartman
maintainerPATCH 166/207 usb: typec: tcpci_rt1711h: Unmask alert interrupts to fix functionality
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: AngeloGioacchino Del Regno <[email protected]>
commit d6b82dafd17db0658f089b9cdec573982ca82bc5 upstream.
During probe, the TCPC alert interrupts are getting masked to avoid unwanted interrupts during chip setup: this is ok to do but there is no unmasking happening at any later time, which means that the chip will not raise any interrupt, essentially making it not functional as, while internally it does perform all of the intended functions, it won't signal anything to the outside.
Unmask the alert interrupts to fix functionality.
--- drivers/usb/typec/tcpm/tcpci_rt1711h.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/usb/typec/tcpm/tcpci_rt1711h.c +11 -0
@@ -334,6 +334,11 @@ static int rt1711h_probe(struct i2c_clie {int ret;struct rt1711h_chip *chip; +const u16 alert_mask =TCPC_ALERT_TX_SUCCESS |TCPC_ALERT_TX_DISCARDED | +TCPC_ALERT_TX_FAILED |TCPC_ALERT_RX_HARD_RST | +TCPC_ALERT_RX_STATUS |TCPC_ALERT_POWER_STATUS | +TCPC_ALERT_CC_STATUS |TCPC_ALERT_RX_BUF_OVF | +TCPC_ALERT_FAULT ; chip =devm_kzalloc (&client->dev,sizeof (*chip),GFP_KERNEL );if (!chip)
@@ -382,6 +387,12 @@ static int rt1711h_probe(struct i2c_clie dev_name(chip->dev), chip);if (ret <0 )return ret; + +/* Enable alert interrupts */ + ret =rt1711h_write16 (chip,TCPC_ALERT_MASK , alert_mask); +if (ret <0 ) +return ret; +enable_irq_wake (client->irq);return 0 ;
Greg Kroah-Hartman
maintainerPATCH 167/207 usb: gadget: Set self-powered based on MaxPower and bmAttributes
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prashanth K <[email protected]>
commit 40e89ff5750fca2c1d6da93f98a2038716bba86c upstream.
Currently the USB gadget will be set as bus-powered based solely on whether its bMaxPower is greater than 100mA, but this may miss devices that may legitimately draw less than 100mA but still want to report as bus-powered. Similarly during suspend & resume, USB gadget is incorrectly marked as bus/self powered without checking the bmAttributes field. Fix these by configuring the USB gadget as self or bus powered based on bmAttributes, and explicitly set it as bus-powered if it draws more than 100mA.
--- drivers/usb/gadget/composite.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-)
drivers/usb/gadget/composite.c +11 -5
@@ -1050,10 +1050,11 @@ static int set_config(struct usb_composielse usb_gadget_set_remote_wakeup (gadget,0 ); done: -if (power <=USB_SELF_POWER_VBUS_MAX_DRAW ) -usb_gadget_set_selfpowered (gadget); -else +if (power >USB_SELF_POWER_VBUS_MAX_DRAW || + !(c->bmAttributes &USB_CONFIG_ATT_SELFPOWER ))usb_gadget_clear_selfpowered (gadget); +else +usb_gadget_set_selfpowered (gadget);usb_gadget_vbus_draw (gadget, power);if (result >=0 && cdev->delayed_status)
@@ -2615,7 +2616,9 @@ void composite_suspend(struct usb_gadget cdev->suspended =1 ; -usb_gadget_set_selfpowered (gadget); +if (cdev->config->bmAttributes &USB_CONFIG_ATT_SELFPOWER ) +usb_gadget_set_selfpowered (gadget); +usb_gadget_vbus_draw (gadget,2 ); }
@@ -2649,8 +2652,11 @@ void composite_resume(struct usb_gadgetelse maxpower =min (maxpower,900U ); -if (maxpower >USB_SELF_POWER_VBUS_MAX_DRAW ) +if (maxpower >USB_SELF_POWER_VBUS_MAX_DRAW || + !(cdev->config->bmAttributes &USB_CONFIG_ATT_SELFPOWER ))usb_gadget_clear_selfpowered (gadget); +else +usb_gadget_set_selfpowered (gadget);usb_gadget_vbus_draw (gadget, maxpower); }else {
Greg Kroah-Hartman
maintainerPATCH 168/207 usb: gadget: Fix setting self-powered state on suspend
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marek Szyprowski <[email protected]>
commit c783e1258f29c5caac9eea0aea6b172870f1baf8 upstream.
cdev->config might be NULL, so check it before dereferencing.
--- drivers/usb/gadget/composite.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/usb/gadget/composite.c +2 -1
@@ -2616,7 +2616,8 @@ void composite_suspend(struct usb_gadget cdev->suspended =1 ; -if (cdev->config->bmAttributes &USB_CONFIG_ATT_SELFPOWER ) +if (cdev->config && + cdev->config->bmAttributes &USB_CONFIG_ATT_SELFPOWER )usb_gadget_set_selfpowered (gadget);usb_gadget_vbus_draw (gadget,2 );
Greg Kroah-Hartman
maintainerPATCH 169/207 usb: gadget: Check bmAttributes only if configuration is valid
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Prashanth K <[email protected]>
commit 8e812e9355a6f14dffd54a33d951ca403b9732f5 upstream.
If the USB configuration is not valid, then avoid checking for bmAttributes to prevent null pointer deference.
--- drivers/usb/gadget/composite.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/gadget/composite.c +1 -1
@@ -1051,7 +1051,7 @@ static int set_config(struct usb_composiusb_gadget_set_remote_wakeup (gadget,0 ); done:if (power >USB_SELF_POWER_VBUS_MAX_DRAW || - !(c->bmAttributes &USB_CONFIG_ATT_SELFPOWER )) + (c && !(c->bmAttributes &USB_CONFIG_ATT_SELFPOWER )))usb_gadget_clear_selfpowered (gadget);else usb_gadget_set_selfpowered (gadget);
Greg Kroah-Hartman
maintainerPATCH 170/207 kbuild: userprogs: use correct lld when linking through clang
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Weißschuh <[email protected]>
commit dfc1b168a8c4b376fa222b27b97c2c4ad4b786e1 upstream.
The userprog infrastructure links objects files through $(CC). Either explicitly by manually calling $(CC) on multiple object files or implicitly by directly compiling a source file to an executable. The documentation at Documentation/kbuild/llvm.rst indicates that ld.lld would be used for linking if LLVM=1 is specified.
However clang instead will use either a globally installed cross linker from $PATH called ${target}-ld or fall back to the system linker, which probably does not support crosslinking.
For the normal kernel build this is not an issue because the linker is always executed directly, without the compiler being involved.
Explicitly pass --ld-path to clang so $(LD) is respected.
As clang 13.0.1 is required to build the kernel, this option is available.
--- Makefile | 5 +++++ 1 file changed, 5 insertions(+)
Makefile +5 -0
@@ -1122,6 +1122,11 @@ endif KBUILD_USERCFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CPPFLAGS) $(KBUILD_CFLAGS)) KBUILD_USERLDFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CPPFLAGS) $(KBUILD_CFLAGS)) +# userspace programs are linked via the compiler, use the correct linker +ifeq ($(CONFIG_CC_IS_CLANG)$(CONFIG_LD_IS_LLD),yy) +KBUILD_USERLDFLAGS += --ld-path=$(LD) +endif + # make the checker run with the right architecture CHECKFLAGS += --arch=$(ARCH)
Greg Kroah-Hartman
maintainerPATCH 171/207 acpi: typec: ucsi: Introduce a ->poll_cci method
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christian A. Ehrhardt <[email protected]>
commit 976e7e9bdc7719a023a4ecccd2e3daec9ab20a40 upstream.
For the ACPI backend of UCSI the UCSI "registers" are just a memory copy of the register values in an opregion. The ACPI implementation in the BIOS ensures that the opregion contents are synced to the embedded controller and it ensures that the registers (in particular CCI) are synced back to the opregion on notifications. While there is an ACPI call that syncs the actual registers to the opregion there is rarely a need to do this and on some ACPI implementations it actually breaks in various interesting ways.
The only reason to force a sync from the embedded controller is to poll CCI while notifications are disabled. Only the ucsi core knows if this is the case and guessing based on the current command is suboptimal, i.e. leading to the following spurious assertion splat:
WARNING: CPU: 3 PID: 76 at drivers/usb/typec/ucsi/ucsi.c:1388 ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi] CPU: 3 UID: 0 PID: 76 Comm: kworker/3:0 Not tainted 6.12.11-200.fc41.x86_64 #1 Hardware name: LENOVO 21D0/LNVNB161216, BIOS J6CN45WW 03/17/2023 Workqueue: events_long ucsi_init_work [typec_ucsi] RIP: 0010:ucsi_reset_ppm+0x1b4/0x1c0 [typec_ucsi] Call Trace: <TASK> ucsi_init_work+0x3c/0xac0 [typec_ucsi] process_one_work+0x179/0x330 worker_thread+0x252/0x390 kthread+0xd2/0x100 ret_from_fork+0x34/0x50 ret_from_fork_asm+0x1a/0x30 </TASK>
Thus introduce a ->poll_cci() method that works like ->read_cci() with an additional forced sync and document that this should be used when polling with notifications disabled. For all other backends that presumably don't have this issue use the same implementation for both methods.
--- drivers/usb/typec/ucsi/ucsi.c | 10 +++++----- drivers/usb/typec/ucsi/ucsi.h | 2 ++ drivers/usb/typec/ucsi/ucsi_acpi.c | 21 ++++++++++++++------- drivers/usb/typec/ucsi/ucsi_ccg.c | 1 + drivers/usb/typec/ucsi/ucsi_glink.c | 1 + drivers/usb/typec/ucsi/ucsi_stm32g0.c | 1 + drivers/usb/typec/ucsi/ucsi_yoga_c630.c | 1 + 7 files changed, 25 insertions(+), 12 deletions(-)
drivers/usb/typec/ucsi/ucsi.c +5 -5
@@ -1346,7 +1346,7 @@ static int ucsi_reset_ppm(struct ucsi *umutex_lock (&ucsi->ppm_lock); - ret = ucsi->ops->read_cci (ucsi, &cci); + ret = ucsi->ops->poll_cci (ucsi, &cci);if (ret <0 ) goto out;
@@ -1364,7 +1364,7 @@ static int ucsi_reset_ppm(struct ucsi *u tmo = jiffies +msecs_to_jiffies (UCSI_TIMEOUT_MS ); do { - ret = ucsi->ops->read_cci(ucsi, &cci); + ret = ucsi->ops->poll_cci(ucsi, &cci); if (ret < 0) goto out; if (cci & UCSI_CCI_COMMAND_COMPLETE)
@@ -1393,7 +1393,7 @@ static int ucsi_reset_ppm(struct ucsi *u/* Give the PPM time to process a reset before reading CCI */ msleep (20 ); - ret = ucsi->ops->read_cci (ucsi, &cci); + ret = ucsi->ops->poll_cci (ucsi, &cci);if (ret) goto out;
@@ -1929,8 +1929,8 @@ struct ucsi *ucsi_create(struct device *struct ucsi *ucsi;if (!ops || - !ops->read_version || !ops->read_cci || !ops->read_message_in || - !ops->sync_control || !ops->async_control) + !ops->read_version || !ops->read_cci || !ops->poll_cci || + !ops->read_message_in || !ops->sync_control || !ops->async_control)return ERR_PTR (-EINVAL ); ucsi =kzalloc (sizeof (*ucsi),GFP_KERNEL );
drivers/usb/typec/ucsi/ucsi.h +2 -0
@@ -61,6 +61,7 @@ struct dentry;* struct ucsi_operations - UCSI I/O operations * @read_version: Read implemented UCSI version * @read_cci: Read CCI register +* @poll_cci: Read CCI register while polling with notifications disabled * @read_message_in: Read message data from UCSI * @sync_control: Blocking control operation * @async_control: Non-blocking control operation
@@ -75,6 +76,7 @@ struct dentry;struct ucsi_operations {int (*read_version)(struct ucsi *ucsi,u16 *version);int (*read_cci)(struct ucsi *ucsi,u32 *cci); +int (*poll_cci)(struct ucsi *ucsi,u32 *cci);int (*read_message_in)(struct ucsi *ucsi,void *val,size_t val_len);int (*sync_control)(struct ucsi *ucsi,u64 command);int (*async_control)(struct ucsi *ucsi,u64 command);
drivers/usb/typec/ucsi/ucsi_acpi.c +14 -7
@@ -59,19 +59,24 @@ static int ucsi_acpi_read_version(structstatic int ucsi_acpi_read_cci (struct ucsi *ucsi,u32 *cci) {struct ucsi_acpi *ua =ucsi_get_drvdata (ucsi); -int ret; - -if (UCSI_COMMAND (ua->cmd) ==UCSI_PPM_RESET ) { - ret =ucsi_acpi_dsm (ua,UCSI_DSM_FUNC_READ ); -if (ret) -return ret; - }memcpy (cci, ua->base +UCSI_CCI ,sizeof (*cci));return 0 ; } +static int ucsi_acpi_poll_cci (struct ucsi *ucsi,u32 *cci) +{ +struct ucsi_acpi *ua =ucsi_get_drvdata (ucsi); +int ret; + + ret =ucsi_acpi_dsm (ua,UCSI_DSM_FUNC_READ ); +if (ret) +return ret; + +return ucsi_acpi_read_cci (ucsi, cci); +} +static int ucsi_acpi_read_message_in (struct ucsi *ucsi,void *val,size_t val_len) {struct ucsi_acpi *ua =ucsi_get_drvdata (ucsi);
@@ -94,6 +99,7 @@ static int ucsi_acpi_async_control(strucstatic const struct ucsi_operations ucsi_acpi_ops = { .read_version = ucsi_acpi_read_version, .read_cci = ucsi_acpi_read_cci, + .poll_cci = ucsi_acpi_poll_cci, .read_message_in = ucsi_acpi_read_message_in, .sync_control = ucsi_sync_control_common, .async_control = ucsi_acpi_async_control
@@ -142,6 +148,7 @@ static int ucsi_gram_sync_control(structstatic const struct ucsi_operations ucsi_gram_ops = { .read_version = ucsi_acpi_read_version, .read_cci = ucsi_acpi_read_cci, + .poll_cci = ucsi_acpi_poll_cci, .read_message_in = ucsi_gram_read_message_in, .sync_control = ucsi_gram_sync_control, .async_control = ucsi_acpi_async_control
drivers/usb/typec/ucsi/ucsi_ccg.c +1 -0
@@ -664,6 +664,7 @@ err_put:static const struct ucsi_operations ucsi_ccg_ops = { .read_version = ucsi_ccg_read_version, .read_cci = ucsi_ccg_read_cci, + .poll_cci = ucsi_ccg_read_cci, .read_message_in = ucsi_ccg_read_message_in, .sync_control = ucsi_ccg_sync_control, .async_control = ucsi_ccg_async_control,
drivers/usb/typec/ucsi/ucsi_glink.c +1 -0
@@ -206,6 +206,7 @@ static void pmic_glink_ucsi_connector_ststatic const struct ucsi_operations pmic_glink_ucsi_ops = { .read_version = pmic_glink_ucsi_read_version, .read_cci = pmic_glink_ucsi_read_cci, + .poll_cci = pmic_glink_ucsi_read_cci, .read_message_in = pmic_glink_ucsi_read_message_in, .sync_control = ucsi_sync_control_common, .async_control = pmic_glink_ucsi_async_control,
drivers/usb/typec/ucsi/ucsi_stm32g0.c +1 -0
@@ -424,6 +424,7 @@ static irqreturn_t ucsi_stm32g0_irq_handstatic const struct ucsi_operations ucsi_stm32g0_ops = { .read_version = ucsi_stm32g0_read_version, .read_cci = ucsi_stm32g0_read_cci, + .poll_cci = ucsi_stm32g0_read_cci, .read_message_in = ucsi_stm32g0_read_message_in, .sync_control = ucsi_sync_control_common, .async_control = ucsi_stm32g0_async_control,
drivers/usb/typec/ucsi/ucsi_yoga_c630.c +1 -0
@@ -74,6 +74,7 @@ static int yoga_c630_ucsi_async_control(const struct ucsi_operations yoga_c630_ucsi_ops = { .read_version = yoga_c630_ucsi_read_version, .read_cci = yoga_c630_ucsi_read_cci, + .poll_cci = yoga_c630_ucsi_read_cci, .read_message_in = yoga_c630_ucsi_read_message_in, .sync_control = ucsi_sync_control_common, .async_control = yoga_c630_ucsi_async_control,
Greg Kroah-Hartman
maintainerPATCH 172/207 KVM: SVM: Set RFLAGS.IF=1 in C code, to get VMRUN out of the STI shadow
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit be45bc4eff33d9a7dae84a2150f242a91a617402 upstream.
Enable/disable local IRQs, i.e. set/clear RFLAGS.IF, in the common svm_vcpu_enter_exit() just after/before guest_state_{enter,exit}_irqoff() so that VMRUN is not executed in an STI shadow. AMD CPUs have a quirk (some would say "bug"), where the STI shadow bleeds into the guest's intr_state field if a #VMEXIT occurs during injection of an event, i.e. if the VMRUN doesn't complete before the subsequent #VMEXIT.
The spurious "interrupts masked" state is relatively benign, as it only occurs during event injection and is transient. Because KVM is already injecting an event, the guest can't be in HLT, and if KVM is querying IRQ blocking for injection, then KVM would need to force an immediate exit anyways since injecting multiple events is impossible.
However, because KVM copies int_state verbatim from vmcb02 to vmcb12, the spurious STI shadow is visible to L1 when running a nested VM, which can trip sanity checks, e.g. in VMware's VMM.
Hoist the STI+CLI all the way to C code, as the aforementioned calls to guest_state_{enter,exit}_irqoff() already inform lockdep that IRQs are enabled/disabled, and taking a fault on VMRUN with RFLAGS.IF=1 is already possible. I.e. if there's kernel code that is confused by running with RFLAGS.IF=1, then it's already a problem. In practice, since GIF=0 also blocks NMIs, the only change in exposure to non-KVM code (relative to surrounding VMRUN with STI+CLI) is exception handling code, and except for the kvm_rebooting=1 case, all exception in the core VM-Enter/VM-Exit path are fatal.
Use the "raw" variants to enable/disable IRQs to avoid tracing in the "no instrumentation" code; the guest state helpers also take care of tracing IRQ state.
Oppurtunstically document why KVM needs to do STI in the first place.
--- arch/x86/kvm/svm/svm.c | 14 ++++++++++++++ arch/x86/kvm/svm/vmenter.S | 10 +--------- 2 files changed, 15 insertions(+), 9 deletions(-)
arch/x86/kvm/svm/svm.c +14 -0
@@ -4178,6 +4178,18 @@ static noinstr void svm_vcpu_enter_exit(guest_state_enter_irqoff (); +/* +* Set RFLAGS.IF prior to VMRUN, as the host's RFLAGS.IF at the time of +* VMRUN controls whether or not physical IRQs are masked (KVM always +* runs with V_INTR_MASKING_MASK). Toggle RFLAGS.IF here to avoid the +* temptation to do STI+VMRUN+CLI, as AMD CPUs bleed the STI shadow +* into guest state if delivery of an event during VMRUN triggers a +* #VMEXIT, and the guest_state transitions already tell lockdep that +* IRQs are being enabled/disabled. Note! GIF=0 for the entirety of +* this path, so IRQs aren't actually unmasked while running host code. +*/ +raw_local_irq_enable (); +amd_clear_divider ();if (sev_es_guest (vcpu->kvm))
@@ -4186,6 +4198,8 @@ static noinstr void svm_vcpu_enter_exit(else __svm_vcpu_run (svm, spec_ctrl_intercepted); +raw_local_irq_disable (); +guest_state_exit_irqoff (); }
arch/x86/kvm/svm/vmenter.S +1 -9
@@ -170,12 +170,8 @@ SYM_FUNC_START(__svm_vcpu_run) mov VCPU_RDI(%_ASM_DI), %_ASM_DI /* Enter guest mode */ - sti - 3: vmrun %_ASM_AX 4: - cli - /* Pop @svm to RAX while it's the only available register. */ pop %_ASM_AX
@@ -340,12 +336,8 @@ SYM_FUNC_START(__svm_sev_es_vcpu_run) mov KVM_VMCB_pa(%rax), %rax /* Enter guest mode */ - sti - 1: vmrun %rax - -2: cli - +2: /* IMPORTANT: Stuff the RSB immediately after VM-Exit, before RET! */ FILL_RETURN_BUFFER %rax, RSB_CLEAR_LOOPS, X86_FEATURE_RSB_VMEXIT
Greg Kroah-Hartman
maintainerPATCH 173/207 KVM: SVM: Save host DR masks on CPUs with DebugSwap
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit b2653cd3b75f62f29b72df4070e20357acb52bc4 upstream.
When running SEV-SNP guests on a CPU that supports DebugSwap, always save the host's DR0..DR3 mask MSR values irrespective of whether or not DebugSwap is enabled, to ensure the host values aren't clobbered by the CPU. And for now, also save DR0..DR3, even though doing so isn't necessary (see below).
SVM_VMGEXIT_AP_CREATE is deeply flawed in that it allows the *guest* to create a VMSA with guest-controlled SEV_FEATURES. A well behaved guest can inform the hypervisor, i.e. KVM, of its "requested" features, but on CPUs without ALLOWED_SEV_FEATURES support, nothing prevents the guest from lying about which SEV features are being enabled (or not!).
If a misbehaving guest enables DebugSwap in a secondary vCPU's VMSA, the CPU will load the DR0..DR3 mask MSRs on #VMEXIT, i.e. will clobber the MSRs with '0' if KVM doesn't save its desired value.
Note, DR0..DR3 themselves are "ok", as DR7 is reset on #VMEXIT, and KVM restores all DRs in common x86 code as needed via hw_breakpoint_restore(). I.e. there is no risk of host DR0..DR3 being clobbered (when it matters). However, there is a flaw in the opposite direction; because the guest can lie about enabling DebugSwap, i.e. can *disable* DebugSwap without KVM's knowledge, KVM must not rely on the CPU to restore DRs. Defer fixing that wart, as it's more of a documentation issue than a bug in the code.
Note, KVM added support for DebugSwap on commit d1f85fbe836e ("KVM: SEV:
Enable data breakpoints in SEV-ES"), but that is not an appropriate Fixes, as the underlying flaw exists in hardware, not in KVM. I.e. all kernels that support SEV-SNP need to be patched, not just kernels with KVM's full support for DebugSwap (ignoring that DebugSwap support landed first).
Opportunistically fix an incorrect statement in the comment; on CPUs without DebugSwap, the CPU does NOT save or load debug registers, i.e.
--- arch/x86/kvm/svm/sev.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
arch/x86/kvm/svm/sev.c +10 -3
@@ -4567,6 +4567,8 @@ void sev_es_vcpu_reset(struct vcpu_svm *void sev_es_prepare_switch_to_guest (struct vcpu_svm *svm,struct sev_es_save_area *hostsa) { +struct kvm *kvm = svm->vcpu.kvm; +/* * All host state for SEV-ES guests is categorized into three swap types * based on how it is handled by hardware during a world switch:
@@ -4590,10 +4592,15 @@ void sev_es_prepare_switch_to_guest(stru/* * If DebugSwap is enabled, debug registers are loaded but NOT saved by -* the CPU (Type-B). If DebugSwap is disabled/unsupported, the CPU both -* saves and loads debug registers (Type-A). +* the CPU (Type-B). If DebugSwap is disabled/unsupported, the CPU does +* not save or load debug registers. Sadly, on CPUs without +* ALLOWED_SEV_FEATURES, KVM can't prevent SNP guests from enabling +* DebugSwap on secondary vCPUs without KVM's knowledge via "AP Create". +* Save all registers if DebugSwap is supported to prevent host state +* from being clobbered by a misbehaving guest. */ -if (sev_vcpu_has_debug_swap (svm)) { +if (sev_vcpu_has_debug_swap (svm) || + (sev_snp_guest (kvm) &&cpu_feature_enabled (X86_FEATURE_DEBUG_SWAP ))) { hostsa->dr0 =native_get_debugreg (0 ); hostsa->dr1 =native_get_debugreg (1 ); hostsa->dr2 =native_get_debugreg (2 );
Greg Kroah-Hartman
maintainerPATCH 174/207 KVM: SVM: Drop DEBUGCTL[5:2] from guests effective value
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit ee89e8013383d50a27ea9bf3c8a69eed6799856f upstream.
Drop bits 5:2 from the guest's effective DEBUGCTL value, as AMD changed the architectural behavior of the bits and broke backwards compatibility. On CPUs without BusLockTrap (or at least, in APMs from before ~2023), bits 5:2 controlled the behavior of external pins:
Performance-Monitoring/Breakpoint Pin-Control (PBi)—Bits 5:2, read/write. Software uses thesebits to control the type of information reported by the four external performance-monitoring/breakpoint pins on the processor. When a PBi bit is cleared to 0, the corresponding external pin (BPi) reports performance-monitor information. When a PBi bit is set to 1, the corresponding external pin (BPi) reports breakpoint information.
With the introduction of BusLockTrap, presumably to be compatible with Intel CPUs, AMD redefined bit 2 to be BLCKDB:
Bus Lock #DB Trap (BLCKDB)—Bit 2, read/write. Software sets this bit to enable generation of a #DB trap following successful execution of a bus lock when CPL is > 0.
and redefined bits 5:3 (and bit 6) as "6:3 Reserved MBZ".
Ideally, KVM would treat bits 5:2 as reserved. Defer that change to a feature cleanup to avoid breaking existing guest in LTS kernels. For now, drop the bits to retain backwards compatibility (of a sort).
Note, dropping bits 5:2 is still a guest-visible change, e.g. if the guest is enabling LBRs *and* the legacy PBi bits, then the state of the PBi bits is visible to the guest, whereas now the guest will always see '0'.
--- arch/x86/kvm/svm/svm.c | 12 ++++++++++++ arch/x86/kvm/svm/svm.h | 2 +- 2 files changed, 13 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/svm.c +12 -0
@@ -3169,6 +3169,18 @@ static int svm_set_msr(struct kvm_vcpu *kvm_pr_unimpl_wrmsr (vcpu, ecx, data);break ; } + +/* +* AMD changed the architectural behavior of bits 5:2. On CPUs +* without BusLockTrap, bits 5:2 control "external pins", but +* on CPUs that support BusLockDetect, bit 2 enables BusLockTrap +* and bits 5:3 are reserved-to-zero. Sadly, old KVM allowed +* the guest to set bits 5:2 despite not actually virtualizing +* Performance-Monitoring/Breakpoint external pins. Drop bits +* 5:2 for backwards compatibility. +*/ + data &= ~GENMASK (5 ,2 ); +if (data &DEBUGCTL_RESERVED_BITS )return 1 ;
arch/x86/kvm/svm/svm.h +1 -1
@@ -591,7 +591,7 @@ static inline bool is_vnmi_enabled(struc/* svm.c */ #define MSR_INVALID 0xffffffffU -#define DEBUGCTL_RESERVED_BITS (~(0x3fULL)) +#define DEBUGCTL_RESERVED_BITS (~(DEBUGCTLMSR_BTF | DEBUGCTLMSR_LBR))extern bool dump_invalid_vmcb;
Greg Kroah-Hartman
maintainerPATCH 175/207 KVM: SVM: Suppress DEBUGCTL.BTF on AMD
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit d0eac42f5cecce009d315655bee341304fbe075e upstream.
Mark BTF as reserved in DEBUGCTL on AMD, as KVM doesn't actually support BTF, and fully enabling BTF virtualization is non-trivial due to interactions with the emulator, guest_debug, #DB interception, nested SVM, etc.
Don't inject #GP if the guest attempts to set BTF, as there's no way to communicate lack of support to the guest, and instead suppress the flag and treat the WRMSR as (partially) unsupported.
In short, make KVM behave the same on AMD and Intel (VMX already squashes BTF).
Note, due to other bugs in KVM's handling of DEBUGCTL, the only way BTF has "worked" in any capacity is if the guest simultaneously enables LBRs.
--- arch/x86/kvm/svm/svm.c | 9 +++++++++ arch/x86/kvm/svm/svm.h | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/svm.c +9 -0
@@ -3181,6 +3181,15 @@ static int svm_set_msr(struct kvm_vcpu **/ data &= ~GENMASK (5 ,2 ); +/* +* Suppress BTF as KVM doesn't virtualize BTF, but there's no +* way to communicate lack of support to the guest. +*/ +if (data &DEBUGCTLMSR_BTF ) { +kvm_pr_unimpl_wrmsr (vcpu,MSR_IA32_DEBUGCTLMSR , data); + data &= ~DEBUGCTLMSR_BTF ; + } +if (data &DEBUGCTL_RESERVED_BITS )return 1 ;
arch/x86/kvm/svm/svm.h +1 -1
@@ -591,7 +591,7 @@ static inline bool is_vnmi_enabled(struc/* svm.c */ #define MSR_INVALID 0xffffffffU -#define DEBUGCTL_RESERVED_BITS (~(DEBUGCTLMSR_BTF | DEBUGCTLMSR_LBR)) +#define DEBUGCTL_RESERVED_BITS (~DEBUGCTLMSR_LBR)extern bool dump_invalid_vmcb;
Greg Kroah-Hartman
maintainerPATCH 176/207 KVM: x86: Snapshot the hosts DEBUGCTL in common x86
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit fb71c795935652fa20eaf9517ca9547f5af99a76 upstream.
Move KVM's snapshot of DEBUGCTL to kvm_vcpu_arch and take the snapshot in common x86, so that SVM can also use the snapshot.
Opportunistically change the field to a u64. While bits 63:32 are reserved on AMD, not mentioned at all in Intel's SDM, and managed as an "unsigned long" by the kernel, DEBUGCTL is an MSR and therefore a 64-bit value.
--- arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/vmx/vmx.c | 8 ++------ arch/x86/kvm/vmx/vmx.h | 2 -- arch/x86/kvm/x86.c | 1 + 4 files changed, 4 insertions(+), 8 deletions(-)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -761,6 +761,7 @@ struct kvm_vcpu_arch {u32 pkru;u32 hflags;u64 efer; +u64 host_debugctl;u64 apic_base;struct kvm_lapic *apic;/* kernel irqchip context */ bool load_eoi_exitmap_pending;
arch/x86/kvm/vmx/vmx.c +2 -6
@@ -1514,16 +1514,12 @@ void vmx_vcpu_load_vmcs(struct kvm_vcpu*/ void vmx_vcpu_load (struct kvm_vcpu *vcpu,int cpu) { -struct vcpu_vmx *vmx =to_vmx (vcpu); -if (vcpu->scheduled_out && !kvm_pause_in_guest (vcpu->kvm))shrink_ple_window (vcpu);vmx_vcpu_load_vmcs (vcpu, cpu,NULL );vmx_vcpu_pi_load (vcpu, cpu); - - vmx->host_debugctlmsr =get_debugctlmsr (); }void vmx_vcpu_put (struct kvm_vcpu *vcpu)
@@ -7469,8 +7465,8 @@ fastpath_t vmx_vcpu_run(struct kvm_vcpu }/* MSR_IA32_DEBUGCTLMSR is zeroed on vmexit. Restore it if needed */ -if (vmx->host_debugctlmsr) -update_debugctlmsr (vmx->host_debugctlmsr); +if (vcpu->arch.host_debugctl) +update_debugctlmsr (vcpu->arch.host_debugctl);#ifndef CONFIG_X86_64 /*
arch/x86/kvm/vmx/vmx.h +0 -2
@@ -337,8 +337,6 @@ struct vcpu_vmx {/* apic deadline value in host tsc */ u64 hv_deadline_tsc; -unsigned long host_debugctlmsr; -/* * Only bits masked by msr_ia32_feature_control_valid_bits can be set in * msr_ia32_feature_control. FEAT_CTL_LOCKED is always included
arch/x86/kvm/x86.c +1 -0
@@ -4976,6 +4976,7 @@ void kvm_arch_vcpu_load(struct kvm_vcpu/* Save host pkru register if supported */ vcpu->arch.host_pkru =read_pkru (); + vcpu->arch.host_debugctl =get_debugctlmsr ();/* Apply any externally detected TSC adjustments (due to suspend) */ if (unlikely (vcpu->arch.tsc_offset_adjustment)) {
Greg Kroah-Hartman
maintainerPATCH 177/207 KVM: SVM: Manually context switch DEBUGCTL if LBR virtualization is disabled
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit 433265870ab3455b418885bff48fa5fd02f7e448 upstream.
Manually load the guest's DEBUGCTL prior to VMRUN (and restore the host's value on #VMEXIT) if it diverges from the host's value and LBR virtualization is disabled, as hardware only context switches DEBUGCTL if LBR virtualization is fully enabled. Running the guest with the host's value has likely been mildly problematic for quite some time, e.g. it will result in undesirable behavior if BTF diverges (with the caveat that KVM now suppresses guest BTF due to lack of support).
But the bug became fatal with the introduction of Bus Lock Trap ("Detect" in kernel paralance) support for AMD (commit 408eb7417a92 ("x86/bus_lock: Add support for AMD")), as a bus lock in the guest will trigger an unexpected #DB.
Note, suppressing the bus lock #DB, i.e. simply resuming the guest without injecting a #DB, is not an option. It wouldn't address the general issue with DEBUGCTL, e.g. for things like BTF, and there are other guest-visible side effects if BusLockTrap is left enabled.
If BusLockTrap is disabled, then DR6.BLD is reserved-to-1; any attempts to clear it by software are ignored. But if BusLockTrap is enabled, software can clear DR6.BLD:
Software enables bus lock trap by setting DebugCtl MSR[BLCKDB] (bit 2) to 1. When bus lock trap is enabled, ... The processor indicates that this #DB was caused by a bus lock by clearing DR6[BLD] (bit 11). DR6[11] previously had been defined to be always 1.
and clearing DR6.BLD is "sticky" in that it's not set (i.e. lowered) by other #DBs:
All other #DB exceptions leave DR6[BLD] unmodified
E.g. leaving BusLockTrap enable can confuse a legacy guest that writes '0' to reset DR6.
--- arch/x86/kvm/svm/svm.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
arch/x86/kvm/svm/svm.c +14 -0
@@ -4277,6 +4277,16 @@ static __no_kcsan fastpath_t svm_vcpu_ruclgi ();kvm_load_guest_xsave_state (vcpu); +/* +* Hardware only context switches DEBUGCTL if LBR virtualization is +* enabled. Manually load DEBUGCTL if necessary (and restore it after +* VM-Exit), as running with the host's DEBUGCTL can negatively affect +* guest state and can even be fatal, e.g. due to Bus Lock Detect. +*/ +if (!(svm->vmcb->control.virt_ext &LBR_CTL_ENABLE_MASK ) && + vcpu->arch.host_debugctl != svm->vmcb->save.dbgctl) +update_debugctlmsr (svm->vmcb->save.dbgctl); +kvm_wait_lapic_expire (vcpu);/*
@@ -4304,6 +4314,10 @@ static __no_kcsan fastpath_t svm_vcpu_ruif (unlikely (svm->vmcb->control.exit_code ==SVM_EXIT_NMI ))kvm_before_interrupt (vcpu,KVM_HANDLING_NMI ); +if (!(svm->vmcb->control.virt_ext &LBR_CTL_ENABLE_MASK ) && + vcpu->arch.host_debugctl != svm->vmcb->save.dbgctl) +update_debugctlmsr (vcpu->arch.host_debugctl); +kvm_load_host_xsave_state (vcpu);stgi ();
Greg Kroah-Hartman
maintainerPATCH 178/207 KVM: x86: Snapshot the hosts DEBUGCTL after disabling IRQs
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sean Christopherson <[email protected]>
commit 189ecdb3e112da703ac0699f4ec76aa78122f911 upstream.
Snapshot the host's DEBUGCTL after disabling IRQs, as perf can toggle debugctl bits from IRQ context, e.g. when enabling/disabling events via smp_call_function_single(). Taking the snapshot (long) before IRQs are disabled could result in KVM effectively clobbering DEBUGCTL due to using a stale snapshot.
--- arch/x86/kvm/x86.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/x86/kvm/x86.c +2 -1
@@ -4976,7 +4976,6 @@ void kvm_arch_vcpu_load(struct kvm_vcpu/* Save host pkru register if supported */ vcpu->arch.host_pkru =read_pkru (); - vcpu->arch.host_debugctl =get_debugctlmsr ();/* Apply any externally detected TSC adjustments (due to suspend) */ if (unlikely (vcpu->arch.tsc_offset_adjustment)) {
@@ -10961,6 +10960,8 @@ static int vcpu_enter_guest(struct kvm_vset_debugreg (0 ,7 ); } + vcpu->arch.host_debugctl =get_debugctlmsr (); +guest_timing_enter_irqoff ();for (;;) {
Greg Kroah-Hartman
maintainerPATCH 179/207 KVM: x86: Explicitly zero EAX and EBX when PERFMON_V2 isnt supported by KVM
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xiaoyao Li <[email protected]>
commit f9dc8fb3afc968042bdaf4b6e445a9272071c9f3 upstream.
Fix a goof where KVM sets CPUID.0x80000022.EAX to CPUID.0x80000022.EBX instead of zeroing both when PERFMON_V2 isn't supported by KVM. In practice, barring a buggy CPU (or vCPU model when running nested) only the !enable_pmu case is affected, as KVM always supports PERFMON_V2 if it's available in hardware, i.e. CPUID.0x80000022.EBX will be '0' if PERFMON_V2 is unsupported.
For the !enable_pmu case, the bug is relatively benign as KVM will refuse to enable PMU capabilities, but a VMM that reflects KVM's supported CPUID into the guest could inadvertently induce #GPs in the guest due to advertising support for MSRs that KVM refuses to emulate.
--- arch/x86/kvm/cpuid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/cpuid.c +1 -1
@@ -1393,7 +1393,7 @@ static inline int __do_cpuid_func(struct entry->ecx = entry->edx =0 ;if (!enable_pmu || !kvm_cpu_cap_has (X86_FEATURE_PERFMON_V2 )) { - entry->eax = entry->ebx; + entry->eax = entry->ebx =0 ;break ; }
Greg Kroah-Hartman
maintainerPATCH 180/207 cdx: Fix possible UAF error in driver_override_show()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Qiu-ji Chen <[email protected]>
commit 91d44c1afc61a2fec37a9c7a3485368309391e0b upstream.
Fixed a possible UAF problem in driver_override_show() in drivers/cdx/cdx.c
This function driver_override_show() is part of DEVICE_ATTR_RW, which includes both driver_override_show() and driver_override_store(). These functions can be executed concurrently in sysfs.
The driver_override_store() function uses driver_set_override() to update the driver_override value, and driver_set_override() internally locks the device (device_lock(dev)). If driver_override_show() reads cdx_dev->driver_override without locking, it could potentially access a freed pointer if driver_override_store() frees the string concurrently. This could lead to printing a kernel address, which is a security risk since DEVICE_ATTR can be read by all users.
Additionally, a similar pattern is used in drivers/amba/bus.c, as well as many other bus drivers, where device_lock() is taken in the show function, and it has been working without issues.
This potential bug was detected by our experimental static analysis tool, which analyzes locking APIs and paired functions to identify data races and atomicity violations.
--- drivers/cdx/cdx.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/cdx/cdx.c +5 -1
@@ -470,8 +470,12 @@ static ssize_t driver_override_show(stru struct device_attribute *attr, char *buf) { struct cdx_device *cdx_dev = to_cdx_device(dev); +ssize_t len; -return sysfs_emit (buf,"%s\n" , cdx_dev->driver_override); +device_lock (dev); + len =sysfs_emit (buf,"%s\n" , cdx_dev->driver_override); +device_unlock (dev); +return len; }static DEVICE_ATTR_RW (driver_override);
Greg Kroah-Hartman
maintainerPATCH 181/207 mei: me: add panther lake P DID
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Usyskin <[email protected]>
commit a8e8ffcc3afce2ee5fb70162aeaef3f03573ee1e upstream.
Add Panther Lake P device id.
--- drivers/misc/mei/hw-me-regs.h | 2 ++ drivers/misc/mei/pci-me.c | 2 ++ 2 files changed, 4 insertions(+)
drivers/misc/mei/hw-me-regs.h +2 -0
@@ -117,6 +117,8 @@#define MEI_DEV_ID_LNL_M 0xA870/* Lunar Lake Point M */ +#define MEI_DEV_ID_PTL_P 0xE470/* Panther Lake P */ +/* * MEI HW Section */
drivers/misc/mei/pci-me.c +2 -0
@@ -124,6 +124,8 @@ static const struct pci_device_id mei_me {MEI_PCI_DEVICE(MEI_DEV_ID_LNL_M, MEI_ME_PCH15_CFG)}, + {MEI_PCI_DEVICE(MEI_DEV_ID_PTL_P, MEI_ME_PCH15_CFG)}, +/* required last entry */ {0, } };
Greg Kroah-Hartman
maintainerPATCH 182/207 mei: vsc: Use "wakeuphostint" when getting the host wakeup GPIO
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit fdb1ada57cf8b8752cdf54f08709d76d74999544 upstream.
The _CRS ACPI resources table has 2 entries for the host wakeup GPIO, the first one being a regular GpioIo () resource while the second one is a GpioInt () resource for the same pin.
The acpi_gpio_mapping table used by vsc-tp.c maps the first Gpio () resource to "wakeuphost-gpios" where as the second GpioInt () entry is mapped to "wakeuphostint-gpios".
Using "wakeuphost" to request the GPIO as was done until now, means that the gpiolib-acpi code does not know that the GPIO is active-low as that info is only available in the GpioInt () entry.
Things were still working before due to the following happening:
1. Since the 2 entries point to the same pin they share a struct gpio_desc
2. The SPI core creates the SPI device vsc-tp.c binds to and calls acpi_dev_gpio_irq_get(). This does use the second entry and sets FLAG_ACTIVE_LOW in gpio_desc.flags .
3. vsc_tp_probe() requests the "wakeuphost" GPIO and inherits the active-low flag set by acpi_dev_gpio_irq_get()
But there is a possible scenario where things do not work:
1. - 3. happen as above
4. After requesting the "wakeuphost" GPIO, the "resetfw" GPIO is requested next, but its USB GPIO controller is not available yet, so this call returns -EPROBE_DEFER.
5. The gpio_desc for "wakeuphost" is put() and during this the active-low flag is cleared from gpio_desc.flags .
6. Later on vsc_tp_probe() requests the "wakeuphost" GPIO again, but now it is not marked active-low.
The difference can also be seen in /sys/kernel/debug/gpio, which contains the following line for this GPIO:
gpio-535 ( |wakeuphost ) in hi IRQ ACTIVE LOW
If the second scenario is hit the "ACTIVE LOW" at the end disappears and things do not work.
Fix this by requesting the GPIO through the "wakeuphostint" mapping instead which provides active-low info without relying on acpi_dev_gpio_irq_get() pre-populating this info in the gpio_desc.
--- drivers/misc/mei/vsc-tp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/misc/mei/vsc-tp.c +1 -1
@@ -502,7 +502,7 @@ static int vsc_tp_probe(struct spi_devicif (ret)return ret; - tp->wakeuphost =devm_gpiod_get (dev,"wakeuphost" ,GPIOD_IN ); + tp->wakeuphost =devm_gpiod_get (dev,"wakeuphostint" ,GPIOD_IN );if (IS_ERR (tp->wakeuphost))return PTR_ERR (tp->wakeuphost);
Greg Kroah-Hartman
maintainerPATCH 183/207 intel_th: pci: Add Arrow Lake support
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Pawel Chmielewski <[email protected]>
commit b5edccae9f447a92d475267d94c33f4926963eec upstream.
Add support for the Trace Hub in Arrow Lake.
--- drivers/hwtracing/intel_th/pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/hwtracing/intel_th/pci.c +5 -0
@@ -335,6 +335,11 @@ static const struct pci_device_id intel_ .driver_data = (kernel_ulong_t)&intel_th_2x, }, { +/* Arrow Lake */ + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x7724), + .driver_data = (kernel_ulong_t)&intel_th_2x, + }, + {/* Alder Lake CPU */ PCI_DEVICE (PCI_VENDOR_ID_INTEL ,0x466f ), .driver_data = (kernel_ulong_t)&intel_th_2x,
Greg Kroah-Hartman
maintainerPATCH 184/207 intel_th: pci: Add Panther Lake-H support
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Shishkin <[email protected]>
commit a70034d6c0d5f3cdee40bb00a578e17fd2ebe426 upstream.
Add support for the Trace Hub in Panther Lake-H.
--- drivers/hwtracing/intel_th/pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/hwtracing/intel_th/pci.c +5 -0
@@ -340,6 +340,11 @@ static const struct pci_device_id intel_ .driver_data = (kernel_ulong_t)&intel_th_2x, }, { +/* Panther Lake-H */ + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0xe324), + .driver_data = (kernel_ulong_t)&intel_th_2x, + }, + {/* Alder Lake CPU */ PCI_DEVICE (PCI_VENDOR_ID_INTEL ,0x466f ), .driver_data = (kernel_ulong_t)&intel_th_2x,
Greg Kroah-Hartman
maintainerPATCH 185/207 intel_th: pci: Add Panther Lake-P/U support
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Shishkin <[email protected]>
commit 49114ff05770264ae233f50023fc64a719a9dcf9 upstream.
Add support for the Trace Hub in Panther Lake-P/U.
--- drivers/hwtracing/intel_th/pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/hwtracing/intel_th/pci.c +5 -0
@@ -345,6 +345,11 @@ static const struct pci_device_id intel_ .driver_data = (kernel_ulong_t)&intel_th_2x, }, { +/* Panther Lake-P/U */ + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0xe424), + .driver_data = (kernel_ulong_t)&intel_th_2x, + }, + {/* Alder Lake CPU */ PCI_DEVICE (PCI_VENDOR_ID_INTEL ,0x466f ), .driver_data = (kernel_ulong_t)&intel_th_2x,
Greg Kroah-Hartman
maintainerPATCH 186/207 char: misc: deallocate static minor in error path
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thadeu Lima de Souza Cascardo <[email protected]>
commit 6d991f569c5ef6eaeadf1238df2c36e3975233ad upstream.
When creating sysfs files fail, the allocated minor must be freed such that it can be later reused. That is specially harmful for static minor numbers, since those would always fail to register later on.
--- drivers/char/misc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/char/misc.c +1 -1
@@ -264,8 +264,8 @@ int misc_register(struct miscdevice *misdevice_create_with_groups (&misc_class, misc->parent, dev, misc, misc->groups,"%s" , misc->name);if (IS_ERR (misc->this_device)) { +misc_minor_free (misc->minor);if (is_dynamic) { -misc_minor_free (misc->minor); misc->minor =MISC_DYNAMIC_MINOR ; } err =PTR_ERR (misc->this_device);
Greg Kroah-Hartman
maintainerPATCH 187/207 drivers: core: fix device leak in __fw_devlink_relax_cycles()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Luca Ceresoli <[email protected]>
commit 78eb41f518f414378643ab022241df2a9dcd008b upstream.
Commit bac3b10b78e5 ("driver core: fw_devlink: Stop trying to optimize cycle detection logic") introduced a new struct device *con_dev and a get_dev_from_fwnode() call to get it, but without adding a corresponding put_device().
--- drivers/base/core.c | 1 + 1 file changed, 1 insertion(+)
drivers/base/core.c +1 -0
@@ -2079,6 +2079,7 @@ static bool __fw_devlink_relax_cycles(st out: sup_handle->flags &= ~FWNODE_FLAG_VISITED ;put_device (sup_dev); +put_device (con_dev);put_device (par_dev);return ret; }
Greg Kroah-Hartman
maintainerPATCH 188/207 slimbus: messaging: Free transaction ID in delayed interrupt scenario
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Visweswara Tanuku <[email protected]>
commit dcb0d43ba8eb9517e70b1a0e4b0ae0ab657a0e5a upstream.
In case of interrupt delay for any reason, slim_do_transfer() returns timeout error but the transaction ID (TID) is not freed. This results into invalid memory access inside qcom_slim_ngd_rx_msgq_cb() due to invalid TID.
Fix the issue by freeing the TID in slim_do_transfer() before returning timeout error to avoid invalid memory access.
Call trace: __memcpy_fromio+0x20/0x190 qcom_slim_ngd_rx_msgq_cb+0x130/0x290 [slim_qcom_ngd_ctrl] vchan_complete+0x2a0/0x4a0 tasklet_action_common+0x274/0x700 tasklet_action+0x28/0x3c _stext+0x188/0x620 run_ksoftirqd+0x34/0x74 smpboot_thread_fn+0x1d8/0x464 kthread+0x178/0x238 ret_from_fork+0x10/0x20 Code: aa0003e8 91000429 f100044a 3940002b (3800150b) ---[ end trace 0fe00bec2b975c99 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt.
--- drivers/slimbus/messaging.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/slimbus/messaging.c +3 -2
@@ -148,8 +148,9 @@ int slim_do_transfer(struct slim_control } ret = ctrl->xfer_msg (ctrl, txn); - -if (!ret && need_tid && !txn->msg->comp) { +if (ret == -ETIMEDOUT ) { +slim_free_txn_tid (ctrl, txn); + }else if (!ret && need_tid && !txn->msg->comp) {unsigned long ms = txn->rl +HZ ; time_left = wait_for_completion_timeout(txn->comp,
Greg Kroah-Hartman
maintainerPATCH 189/207 bus: mhi: host: pci_generic: Use pci_try_reset_function() to avoid deadlock
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Manivannan Sadhasivam <[email protected]>
commit a321d163de3d8aa38a6449ab2becf4b1581aed96 upstream.
There are multiple places from where the recovery work gets scheduled asynchronously. Also, there are multiple places where the caller waits synchronously for the recovery to be completed. One such place is during the PM shutdown() callback.
If the device is not alive during recovery_work, it will try to reset the device using pci_reset_function(). This function internally will take the device_lock() first before resetting the device. By this time, if the lock has already been acquired, then recovery_work will get stalled while waiting for the lock. And if the lock was already acquired by the caller which waits for the recovery_work to be completed, it will lead to deadlock.
This is what happened on the X1E80100 CRD device when the device died before shutdown() callback. Driver core calls the driver's shutdown() callback while holding the device_lock() leading to deadlock.
And this deadlock scenario can occur on other paths as well, like during the PM suspend() callback, where the driver core would hold the device_lock() before calling driver's suspend() callback. And if the recovery_work was already started, it could lead to deadlock. This is also observed on the X1E80100 CRD.
So to fix both issues, use pci_try_reset_function() in recovery_work. This function first checks for the availability of the device_lock() before trying to reset the device. If the lock is available, it will acquire it and reset the device. Otherwise, it will return -EAGAIN. If that happens, recovery_work will fail with the error message "Recovery failed" as not much could be done.
--- drivers/bus/mhi/host/pci_generic.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/bus/mhi/host/pci_generic.c +3 -2
@@ -1040,8 +1040,9 @@ static void mhi_pci_recovery_work(struct err_unprepare:mhi_unprepare_after_power_down (mhi_cntrl); err_try_reset: -if (pci_reset_function (pdev)) -dev_err (&pdev->dev,"Recovery failed\n" ); + err =pci_try_reset_function (pdev); +if (err) +dev_err (&pdev->dev,"Recovery failed: %d\n" , err); }static void health_check (struct timer_list *t)
Greg Kroah-Hartman
maintainerPATCH 190/207 eeprom: digsy_mtc: Make GPIO lookup table match the device
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Shevchenko <[email protected]>
commit 038ef0754aae76f79b147b8867f9250e6a976872 upstream.
The dev_id value in the GPIO lookup table must match to the device instance name, which in this case is combined of name and platform device ID, i.e. "spi_gpio.1". But the table assumed that there was no platform device ID defined, which is wrong. Fix the dev_id value accordingly.
--- drivers/misc/eeprom/digsy_mtc_eeprom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/misc/eeprom/digsy_mtc_eeprom.c +1 -1
@@ -50,7 +50,7 @@ static struct platform_device digsy_mtc_ };static struct gpiod_lookup_table eeprom_spi_gpiod_table = { - .dev_id ="spi_gpio" , + .dev_id ="spi_gpio.1" , .table = {GPIO_LOOKUP ("gpio@b00" ,GPIO_EEPROM_CLK ,"sck" ,GPIO_ACTIVE_HIGH ),
Greg Kroah-Hartman
maintainerPATCH 191/207 drivers: virt: acrn: hsm: Use kzalloc to avoid info leak in pmcmd_ioctl
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Haoyu Li <[email protected]>
commit 819cec1dc47cdeac8f5dd6ba81c1dbee2a68c3bb upstream.
In the "pmcmd_ioctl" function, three memory objects allocated by kmalloc are initialized by "hcall_get_cpu_state", which are then copied to user space. The initializer is indeed implemented in "acrn_hypercall2" (arch/x86/include/asm/acrn.h). There is a risk of information leakage due to uninitialized bytes.
--- drivers/virt/acrn/hsm.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/virt/acrn/hsm.c +3 -3
@@ -49,7 +49,7 @@ static int pmcmd_ioctl(u64 cmd, void __uswitch (cmd &PMCMD_TYPE_MASK ) {case ACRN_PMCMD_GET_PX_CNT :case ACRN_PMCMD_GET_CX_CNT : - pm_info =kmalloc (sizeof (u64),GFP_KERNEL ); + pm_info =kzalloc (sizeof (u64),GFP_KERNEL );if (!pm_info)return -ENOMEM ;
@@ -64,7 +64,7 @@ static int pmcmd_ioctl(u64 cmd, void __ukfree (pm_info);break ;case ACRN_PMCMD_GET_PX_DATA : - px_data =kmalloc (sizeof (*px_data),GFP_KERNEL ); + px_data =kzalloc (sizeof (*px_data),GFP_KERNEL );if (!px_data)return -ENOMEM ;
@@ -79,7 +79,7 @@ static int pmcmd_ioctl(u64 cmd, void __ukfree (px_data);break ;case ACRN_PMCMD_GET_CX_DATA : - cx_data =kmalloc (sizeof (*cx_data),GFP_KERNEL ); + cx_data =kzalloc (sizeof (*cx_data),GFP_KERNEL );if (!cx_data)return -ENOMEM ;
Greg Kroah-Hartman
maintainerPATCH 192/207 iio: filter: admv8818: Force initialization of SDO
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sam Winchenbach <[email protected]>
commit cc2c3540d9477a9931fb0fd851fcaeba524a5b35 upstream.
When a weak pull-up is present on the SDO line, regmap_update_bits fails to write both the SOFTRESET and SDOACTIVE bits because it incorrectly reads them as already set.
Since the soft reset disables the SDO line, performing a read-modify-write operation on ADI_SPI_CONFIG_A to enable the SDO line doesn't make sense. This change directly writes to the register instead of using regmap_update_bits.
--- drivers/iio/filter/admv8818.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-)
drivers/iio/filter/admv8818.c +4 -10
@@ -574,21 +574,15 @@ static int admv8818_init(struct admv8818struct spi_device *spi = st->spi;unsigned int chip_id; - ret =regmap_update_bits (st->regmap,ADMV8818_REG_SPI_CONFIG_A , -ADMV8818_SOFTRESET_N_MSK | -ADMV8818_SOFTRESET_MSK , -FIELD_PREP (ADMV8818_SOFTRESET_N_MSK ,1 ) | -FIELD_PREP (ADMV8818_SOFTRESET_MSK ,1 )); + ret =regmap_write (st->regmap,ADMV8818_REG_SPI_CONFIG_A , +ADMV8818_SOFTRESET_N_MSK |ADMV8818_SOFTRESET_MSK );if (ret) {dev_err (&spi->dev,"ADMV8818 Soft Reset failed.\n" );return ret; } - ret =regmap_update_bits (st->regmap,ADMV8818_REG_SPI_CONFIG_A , -ADMV8818_SDOACTIVE_N_MSK | -ADMV8818_SDOACTIVE_MSK , -FIELD_PREP (ADMV8818_SDOACTIVE_N_MSK ,1 ) | -FIELD_PREP (ADMV8818_SDOACTIVE_MSK ,1 )); + ret =regmap_write (st->regmap,ADMV8818_REG_SPI_CONFIG_A , +ADMV8818_SDOACTIVE_N_MSK |ADMV8818_SDOACTIVE_MSK );if (ret) {dev_err (&spi->dev,"ADMV8818 SDO Enable failed.\n" );return ret;
Greg Kroah-Hartman
maintainerPATCH 193/207 iio: light: apds9306: fix max_scale_nano values
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Javier Carrasco <[email protected]>
commit a96d3e2beca0e51c8444d0a3b6b3ec484c4c5a8f upstream.
The two provided max_scale_nano values must be multiplied by 100 and 10 respectively to achieve nano units. According to the comments:
Max scale for apds0306 is 16.326432 → the fractional part is 0.326432, which is 326432000 in NANO. The current value is 3264320.
Max scale for apds0306-065 is 14.09721 → the fractional part is 0.09712, which is 97120000 in NANO. The current value is 9712000.
Update max_scale_nano initialization to use the right NANO fractional parts.
--- drivers/iio/light/apds9306.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iio/light/apds9306.c +2 -2
@@ -108,11 +108,11 @@ static const struct part_id_gts_multipli { .part_id = 0xB1, .max_scale_int = 16, - .max_scale_nano = 3264320, + .max_scale_nano = 326432000, }, { .part_id = 0xB3, .max_scale_int = 14, - .max_scale_nano = 9712000, + .max_scale_nano = 97120000, }, };
Greg Kroah-Hartman
maintainerPATCH 194/207 iio: dac: ad3552r: clear reset status flag
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Angelo Dureghello <[email protected]>
commit e17b9f20da7d2bc1f48878ab2230523b2512d965 upstream.
Clear reset status flag, to keep error status register clean after reset (ad3552r manual, rev B table 38).
Reset error flag was left to 1, so debugging registers, the "Error Status Register" was dirty (0x01). It is important to clear this bit, so if there is any reset event over normal working mode, it is possible to detect it.
--- drivers/iio/dac/ad3552r.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/iio/dac/ad3552r.c +6 -0
@@ -410,6 +410,12 @@ static int ad3552r_reset(struct ad3552r_return ret; } +/* Clear reset error flag, see ad3552r manual, rev B table 38. */ + ret =ad3552r_write_reg (dac,AD3552R_REG_ADDR_ERR_STATUS , +AD3552R_MASK_RESET_STATUS ); +if (ret) +return ret; + return ad3552r_update_reg_field(dac, AD3552R_REG_ADDR_INTERFACE_CONFIG_A, AD3552R_MASK_ADDR_ASCENSION,
Greg Kroah-Hartman
maintainerPATCH 195/207 iio: adc: ad7192: fix channel select
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Burri <[email protected]>
commit 21d7241faf406e8aee3ce348451cc362d5db6a02 upstream.
Channel configuration doesn't work as expected.
For FIELD_PREP the bit mask is needed and not the bit number.
--- drivers/iio/adc/ad7192.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iio/adc/ad7192.c +1 -1
@@ -1082,7 +1082,7 @@ static int ad7192_update_scan_mode(struc conf &= ~AD7192_CONF_CHAN_MASK ;for_each_set_bit (i, scan_mask,8 ) - conf |=FIELD_PREP (AD7192_CONF_CHAN_MASK , i); + conf |=FIELD_PREP (AD7192_CONF_CHAN_MASK ,BIT (i)); ret =ad_sd_write_reg (&st->sd,AD7192_REG_CONF ,3 , conf);if (ret <0 )
Greg Kroah-Hartman
maintainerPATCH 196/207 iio: adc: at91-sama5d2_adc: fix sama7g5 realbits value
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nayab Sayed <[email protected]>
commit aa5119c36d19639397d29ef305aa53a5ecd72b27 upstream.
The number of valid bits in SAMA7G5 ADC channel data register are 16. Hence changing the realbits value to 16
--- drivers/iio/adc/at91-sama5d2_adc.c | 68 +++++++++++++++++++++---------------- 1 file changed, 40 insertions(+), 28 deletions(-)
drivers/iio/adc/at91-sama5d2_adc.c +40 -28
@@ -329,7 +329,7 @@ static const struct at91_adc_reg_layout#define AT91_HWFIFO_MAX_SIZE_STR "128"#define AT91_HWFIFO_MAX_SIZE 128 -#define AT91_SAMA5D2_CHAN_SINGLE (index, num, addr) \ +#define AT91_SAMA_CHAN_SINGLE (index, num, addr, rbits) \ { \ .type = IIO_VOLTAGE, \ .channel = num, \
@@ -337,7 +337,7 @@ static const struct at91_adc_reg_layout .scan_index = index, \ .scan_type = { \ .sign = 'u', \ - .realbits = 14, \ + .realbits = rbits, \ .storagebits = 16, \ }, \ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \
@@ -350,7 +350,13 @@ static const struct at91_adc_reg_layout .indexed = 1, \ } -#define AT91_SAMA5D2_CHAN_DIFF (index, num, num2, addr) \ +#define AT91_SAMA5D2_CHAN_SINGLE (index, num, addr) \ + AT91_SAMA_CHAN_SINGLE(index, num, addr, 14) + +#define AT91_SAMA7G5_CHAN_SINGLE (index, num, addr) \ + AT91_SAMA_CHAN_SINGLE(index, num, addr, 16) + +#define AT91_SAMA_CHAN_DIFF (index, num, num2, addr, rbits) \ { \ .type = IIO_VOLTAGE, \ .differential = 1, \
@@ -360,7 +366,7 @@ static const struct at91_adc_reg_layout .scan_index = index, \ .scan_type = { \ .sign = 's', \ - .realbits = 14, \ + .realbits = rbits, \ .storagebits = 16, \ }, \ .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \
@@ -373,6 +379,12 @@ static const struct at91_adc_reg_layout .indexed = 1, \ } +#define AT91_SAMA5D2_CHAN_DIFF (index, num, num2, addr) \ + AT91_SAMA_CHAN_DIFF(index, num, num2, addr, 14) + +#define AT91_SAMA7G5_CHAN_DIFF (index, num, num2, addr) \ + AT91_SAMA_CHAN_DIFF(index, num, num2, addr, 16) +#define AT91_SAMA5D2_CHAN_TOUCH (num, name, mod) \ { \ .type = IIO_POSITIONRELATIVE, \
@@ -666,30 +678,30 @@ static const struct iio_chan_spec at91_s };static const struct iio_chan_spec at91_sama7g5_adc_channels[] = { -AT91_SAMA5D2_CHAN_SINGLE (0 ,0 ,0x60 ), -AT91_SAMA5D2_CHAN_SINGLE (1 ,1 ,0x64 ), -AT91_SAMA5D2_CHAN_SINGLE (2 ,2 ,0x68 ), -AT91_SAMA5D2_CHAN_SINGLE (3 ,3 ,0x6c ), -AT91_SAMA5D2_CHAN_SINGLE (4 ,4 ,0x70 ), -AT91_SAMA5D2_CHAN_SINGLE (5 ,5 ,0x74 ), -AT91_SAMA5D2_CHAN_SINGLE (6 ,6 ,0x78 ), -AT91_SAMA5D2_CHAN_SINGLE (7 ,7 ,0x7c ), -AT91_SAMA5D2_CHAN_SINGLE (8 ,8 ,0x80 ), -AT91_SAMA5D2_CHAN_SINGLE (9 ,9 ,0x84 ), -AT91_SAMA5D2_CHAN_SINGLE (10 ,10 ,0x88 ), -AT91_SAMA5D2_CHAN_SINGLE (11 ,11 ,0x8c ), -AT91_SAMA5D2_CHAN_SINGLE (12 ,12 ,0x90 ), -AT91_SAMA5D2_CHAN_SINGLE (13 ,13 ,0x94 ), -AT91_SAMA5D2_CHAN_SINGLE (14 ,14 ,0x98 ), -AT91_SAMA5D2_CHAN_SINGLE (15 ,15 ,0x9c ), -AT91_SAMA5D2_CHAN_DIFF (16 ,0 ,1 ,0x60 ), -AT91_SAMA5D2_CHAN_DIFF (17 ,2 ,3 ,0x68 ), -AT91_SAMA5D2_CHAN_DIFF (18 ,4 ,5 ,0x70 ), -AT91_SAMA5D2_CHAN_DIFF (19 ,6 ,7 ,0x78 ), -AT91_SAMA5D2_CHAN_DIFF (20 ,8 ,9 ,0x80 ), -AT91_SAMA5D2_CHAN_DIFF (21 ,10 ,11 ,0x88 ), -AT91_SAMA5D2_CHAN_DIFF (22 ,12 ,13 ,0x90 ), -AT91_SAMA5D2_CHAN_DIFF (23 ,14 ,15 ,0x98 ), +AT91_SAMA7G5_CHAN_SINGLE (0 ,0 ,0x60 ), +AT91_SAMA7G5_CHAN_SINGLE (1 ,1 ,0x64 ), +AT91_SAMA7G5_CHAN_SINGLE (2 ,2 ,0x68 ), +AT91_SAMA7G5_CHAN_SINGLE (3 ,3 ,0x6c ), +AT91_SAMA7G5_CHAN_SINGLE (4 ,4 ,0x70 ), +AT91_SAMA7G5_CHAN_SINGLE (5 ,5 ,0x74 ), +AT91_SAMA7G5_CHAN_SINGLE (6 ,6 ,0x78 ), +AT91_SAMA7G5_CHAN_SINGLE (7 ,7 ,0x7c ), +AT91_SAMA7G5_CHAN_SINGLE (8 ,8 ,0x80 ), +AT91_SAMA7G5_CHAN_SINGLE (9 ,9 ,0x84 ), +AT91_SAMA7G5_CHAN_SINGLE (10 ,10 ,0x88 ), +AT91_SAMA7G5_CHAN_SINGLE (11 ,11 ,0x8c ), +AT91_SAMA7G5_CHAN_SINGLE (12 ,12 ,0x90 ), +AT91_SAMA7G5_CHAN_SINGLE (13 ,13 ,0x94 ), +AT91_SAMA7G5_CHAN_SINGLE (14 ,14 ,0x98 ), +AT91_SAMA7G5_CHAN_SINGLE (15 ,15 ,0x9c ), +AT91_SAMA7G5_CHAN_DIFF (16 ,0 ,1 ,0x60 ), +AT91_SAMA7G5_CHAN_DIFF (17 ,2 ,3 ,0x68 ), +AT91_SAMA7G5_CHAN_DIFF (18 ,4 ,5 ,0x70 ), +AT91_SAMA7G5_CHAN_DIFF (19 ,6 ,7 ,0x78 ), +AT91_SAMA7G5_CHAN_DIFF (20 ,8 ,9 ,0x80 ), +AT91_SAMA7G5_CHAN_DIFF (21 ,10 ,11 ,0x88 ), +AT91_SAMA7G5_CHAN_DIFF (22 ,12 ,13 ,0x90 ), +AT91_SAMA7G5_CHAN_DIFF (23 ,14 ,15 ,0x98 ),IIO_CHAN_SOFT_TIMESTAMP (24 ),AT91_SAMA5D2_CHAN_TEMP (AT91_SAMA7G5_ADC_TEMP_CHANNEL ,"temp" ,0xdc ), };
Greg Kroah-Hartman
maintainerPATCH 197/207 mm: hugetlb: Add huge page size param to huge_ptep_get_and_clear()
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ryan Roberts <[email protected]>
commit 02410ac72ac3707936c07ede66e94360d0d65319 upstream.
In order to fix a bug, arm64 needs to be told the size of the huge page for which the huge_pte is being cleared in huge_ptep_get_and_clear(). Provide for this by adding an unsigned long sz parameter to the function. This follows the same pattern as huge_pte_clear() and set_huge_pte_at().
This commit makes the required interface modifications to the core mm as well as all arches that implement this function (arm64, loongarch, mips, parisc, powerpc, riscv, s390, sparc). The actual arm64 bug will be fixed in a separate commit.
--- arch/arm64/include/asm/hugetlb.h | 4 ++-- arch/arm64/mm/hugetlbpage.c | 8 +++++--- arch/loongarch/include/asm/hugetlb.h | 6 ++++-- arch/mips/include/asm/hugetlb.h | 6 ++++-- arch/parisc/include/asm/hugetlb.h | 2 +- arch/parisc/mm/hugetlbpage.c | 2 +- arch/powerpc/include/asm/hugetlb.h | 6 ++++-- arch/riscv/include/asm/hugetlb.h | 3 ++- arch/riscv/mm/hugetlbpage.c | 2 +- arch/s390/include/asm/hugetlb.h | 18 +++++++++++++----- arch/s390/mm/hugetlbpage.c | 4 ++-- arch/sparc/include/asm/hugetlb.h | 2 +- arch/sparc/mm/hugetlbpage.c | 2 +- include/asm-generic/hugetlb.h | 2 +- include/linux/hugetlb.h | 4 +++- mm/hugetlb.c | 4 ++-- 16 files changed, 47 insertions(+), 28 deletions(-)
arch/arm64/include/asm/hugetlb.h +2 -2
@@ -42,8 +42,8 @@ extern int huge_ptep_set_access_flags(st unsigned long addr, pte_t *ptep, pte_t pte, int dirty);#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEAR -extern pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep); +extern pte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, +pte_t *ptep,unsigned long sz);#define __HAVE_ARCH_HUGE_PTEP_SET_WRPROTECTextern void huge_ptep_set_wrprotect (struct mm_struct *mm,unsigned long addr,pte_t *ptep);
arch/arm64/mm/hugetlbpage.c +5 -3
@@ -396,8 +396,8 @@ void huge_pte_clear(struct mm_struct *mm__pte_clear (mm, addr, ptep); } -pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +pte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, +pte_t *ptep,unsigned long sz) {int ncontig;size_t pgsize;
@@ -549,6 +549,8 @@ bool __init arch_hugetlb_valid_size(unsipte_t huge_ptep_modify_prot_start (struct vm_area_struct *vma,unsigned long addr,pte_t *ptep) { +unsigned long psize =huge_page_size (hstate_vma (vma)); +if (alternative_has_cap_unlikely (ARM64_WORKAROUND_2645198 )) {/* * Break-before-make (BBM) is required for all user space mappings
@@ -558,7 +560,7 @@ pte_t huge_ptep_modify_prot_start(structif (pte_user_exec (__ptep_get (ptep)))return huge_ptep_clear_flush (vma, addr, ptep); } -return huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); +return huge_ptep_get_and_clear (vma->vm_mm, addr, ptep, psize); } void huge_ptep_modify_prot_commit(struct vm_area_struct *vma, unsigned long addr, pte_t *ptep,
arch/loongarch/include/asm/hugetlb.h +4 -2
@@ -36,7 +36,8 @@ static inline void huge_pte_clear(struct#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARstatic inline pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +unsigned long addr,pte_t *ptep, +unsigned long sz) {pte_t clear;pte_t pte =ptep_get (ptep);
@@ -51,8 +52,9 @@ static inline pte_t huge_ptep_clear_flus unsigned long addr, pte_t *ptep) { pte_t pte; +unsigned long sz =huge_page_size (hstate_vma (vma)); - pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); + pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep, sz);flush_tlb_page (vma, addr);return pte; }
arch/mips/include/asm/hugetlb.h +4 -2
@@ -27,7 +27,8 @@ static inline int prepare_hugepage_range#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARstatic inline pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +unsigned long addr,pte_t *ptep, +unsigned long sz) {pte_t clear;pte_t pte = *ptep;
@@ -42,13 +43,14 @@ static inline pte_t huge_ptep_clear_flus unsigned long addr, pte_t *ptep) { pte_t pte; +unsigned long sz =huge_page_size (hstate_vma (vma));/* * clear the huge pte entry firstly, so that the other smp threads will * not get old pte entry after finishing flush_tlb_page and before * setting new huge pte entry */ - pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); + pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep, sz);flush_tlb_page (vma, addr);return pte; }
arch/parisc/include/asm/hugetlb.h +1 -1
@@ -10,7 +10,7 @@ void set_huge_pte_at(struct mm_struct *m#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARpte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, -pte_t *ptep); +pte_t *ptep,unsigned long sz);#define __HAVE_ARCH_HUGE_PTEP_CLEAR_FLUSH static inline pte_t huge_ptep_clear_flush(struct vm_area_struct *vma,
arch/parisc/mm/hugetlbpage.c +1 -1
@@ -126,7 +126,7 @@ void set_huge_pte_at(struct mm_struct *mpte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, -pte_t *ptep) +pte_t *ptep,unsigned long sz) {pte_t entry;
arch/powerpc/include/asm/hugetlb.h +4 -2
@@ -45,7 +45,8 @@ void set_huge_pte_at(struct mm_struct *m#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARstatic inline pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +unsigned long addr,pte_t *ptep, +unsigned long sz) {return __pte (pte_update (mm, addr, ptep, ~0UL ,0 ,1 )); }
@@ -55,8 +56,9 @@ static inline pte_t huge_ptep_clear_flus unsigned long addr, pte_t *ptep) { pte_t pte; +unsigned long sz =huge_page_size (hstate_vma (vma)); - pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); + pte =huge_ptep_get_and_clear (vma->vm_mm, addr, ptep, sz);flush_hugetlb_page (vma, addr);return pte; }
arch/riscv/include/asm/hugetlb.h +2 -1
@@ -28,7 +28,8 @@ void set_huge_pte_at(struct mm_struct *m#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARpte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep); +unsigned long addr,pte_t *ptep, +unsigned long sz);#define __HAVE_ARCH_HUGE_PTEP_CLEAR_FLUSH pte_t huge_ptep_clear_flush(struct vm_area_struct *vma,
arch/riscv/mm/hugetlbpage.c +1 -1
@@ -293,7 +293,7 @@ int huge_ptep_set_access_flags(struct vmpte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, -pte_t *ptep) +pte_t *ptep,unsigned long sz) {pte_t orig_pte =ptep_get (ptep);int pte_num;
arch/s390/include/asm/hugetlb.h +13 -5
@@ -23,9 +23,17 @@ void __set_huge_pte_at(struct mm_struct pte_t *ptep, pte_t pte);#define __HAVE_ARCH_HUGE_PTEP_GETextern pte_t huge_ptep_get (struct mm_struct *mm,unsigned long addr,pte_t *ptep); + +pte_t __huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, +pte_t *ptep); +#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEAR -extern pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep); +static inline pte_t huge_ptep_get_and_clear (struct mm_struct *mm, +unsigned long addr,pte_t *ptep, +unsigned long sz) +{ +return __huge_ptep_get_and_clear (mm, addr, ptep); +}static inline void arch_clear_hugetlb_flags (struct folio *folio) {
@@ -47,7 +55,7 @@ static inline void huge_pte_clear(structstatic inline pte_t huge_ptep_clear_flush (struct vm_area_struct *vma,unsigned long address,pte_t *ptep) { -return huge_ptep_get_and_clear (vma->vm_mm, address, ptep); +return __huge_ptep_get_and_clear (vma->vm_mm, address, ptep); }#define __HAVE_ARCH_HUGE_PTEP_SET_ACCESS_FLAGS
@@ -57,7 +65,7 @@ static inline int huge_ptep_set_access_f {int changed = !pte_same (huge_ptep_get (vma->vm_mm, addr, ptep), pte);if (changed) { -huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); +__huge_ptep_get_and_clear (vma->vm_mm, addr, ptep);__set_huge_pte_at (vma->vm_mm, addr, ptep, pte); }return changed;
@@ -67,7 +75,7 @@ static inline int huge_ptep_set_access_fstatic inline void huge_ptep_set_wrprotect (struct mm_struct *mm,unsigned long addr,pte_t *ptep) { -pte_t pte =huge_ptep_get_and_clear (mm, addr, ptep); +pte_t pte =__huge_ptep_get_and_clear (mm, addr, ptep);__set_huge_pte_at (mm, addr, ptep,pte_wrprotect (pte)); }
arch/s390/mm/hugetlbpage.c +2 -2
@@ -188,8 +188,8 @@ pte_t huge_ptep_get(struct mm_struct *mmreturn __rste_to_pte (pte_val (*ptep)); } -pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +pte_t __huge_ptep_get_and_clear (struct mm_struct *mm, +unsigned long addr,pte_t *ptep) {pte_t pte =huge_ptep_get (mm, addr, ptep);pmd_t *pmdp = (pmd_t *) ptep;
arch/sparc/include/asm/hugetlb.h +1 -1
@@ -20,7 +20,7 @@ void __set_huge_pte_at(struct mm_struct#define __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARpte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, -pte_t *ptep); +pte_t *ptep,unsigned long sz);#define __HAVE_ARCH_HUGE_PTEP_CLEAR_FLUSH static inline pte_t huge_ptep_clear_flush(struct vm_area_struct *vma,
arch/sparc/mm/hugetlbpage.c +1 -1
@@ -260,7 +260,7 @@ void set_huge_pte_at(struct mm_struct *m }pte_t huge_ptep_get_and_clear (struct mm_struct *mm,unsigned long addr, -pte_t *ptep) +pte_t *ptep,unsigned long sz) {unsigned int i, nptes, orig_shift, shift;unsigned long size;
include/asm-generic/hugetlb.h +1 -1
@@ -90,7 +90,7 @@ static inline void set_huge_pte_at(struc#ifndef __HAVE_ARCH_HUGE_PTEP_GET_AND_CLEARstatic inline pte_t huge_ptep_get_and_clear (struct mm_struct *mm, -unsigned long addr,pte_t *ptep) +unsigned long addr,pte_t *ptep,unsigned long sz) {return ptep_get_and_clear (mm, addr, ptep); }
include/linux/hugetlb.h +3 -1
@@ -1003,7 +1003,9 @@ static inline void hugetlb_count_sub(lonstatic inline pte_t huge_ptep_modify_prot_start (struct vm_area_struct *vma,unsigned long addr,pte_t *ptep) { -return huge_ptep_get_and_clear (vma->vm_mm, addr, ptep); +unsigned long psize =huge_page_size (hstate_vma (vma)); + +return huge_ptep_get_and_clear (vma->vm_mm, addr, ptep, psize); }#endif
mm/hugetlb.c +2 -2
@@ -5402,7 +5402,7 @@ static void move_huge_pte(struct vm_areaif (src_ptl != dst_ptl)spin_lock_nested (src_ptl,SINGLE_DEPTH_NESTING ); - pte =huge_ptep_get_and_clear (mm, old_addr, src_pte); + pte =huge_ptep_get_and_clear (mm, old_addr, src_pte, sz);if (need_clear_uffd_wp &&pte_marker_uffd_wp (pte))huge_pte_clear (mm, new_addr, dst_pte, sz);
@@ -5577,7 +5577,7 @@ void __unmap_hugepage_range(struct mmu_gset_vma_resv_flags (vma,HPAGE_RESV_UNMAPPED ); } - pte =huge_ptep_get_and_clear (mm, address, ptep); + pte =huge_ptep_get_and_clear (mm, address, ptep, sz);tlb_remove_huge_tlb_entry (h, tlb, ptep, address);if (huge_pte_dirty (pte))set_page_dirty (page);
Greg Kroah-Hartman
maintainerPATCH 198/207 arm64: hugetlb: Fix huge_ptep_get_and_clear() for non-present ptes
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ryan Roberts <[email protected]>
commit 49c87f7677746f3c5bd16c81b23700bb6b88bfd4 upstream.
arm64 supports multiple huge_pte sizes. Some of the sizes are covered by a single pte entry at a particular level (PMD_SIZE, PUD_SIZE), and some are covered by multiple ptes at a particular level (CONT_PTE_SIZE, CONT_PMD_SIZE). So the function has to figure out the size from the huge_pte pointer. This was previously done by walking the pgtable to determine the level and by using the PTE_CONT bit to determine the number of ptes at the level.
But the PTE_CONT bit is only valid when the pte is present. For non-present pte values (e.g. markers, migration entries), the previous implementation was therefore erroneously determining the size. There is at least one known caller in core-mm, move_huge_pte(), which may call huge_ptep_get_and_clear() for a non-present pte. So we must be robust to this case. Additionally the "regular" ptep_get_and_clear() is robust to being called for non-present ptes so it makes sense to follow the behavior.
Fix this by using the new sz parameter which is now provided to the function. Additionally when clearing each pte in a contig range, don't gather the access and dirty bits if the pte is not present.
An alternative approach that would not require API changes would be to store the PTE_CONT bit in a spare bit in the swap entry pte for the non-present case. But it felt cleaner to follow other APIs' lead and just pass in the size.
As an aside, PTE_CONT is bit 52, which corresponds to bit 40 in the swap entry offset field (layout of non-present pte). Since hugetlb is never swapped to disk, this field will only be populated for markers, which always set this bit to 0 and hwpoison swap entries, which set the offset field to a PFN; So it would only ever be 1 for a 52-bit PVA system where memory in that high half was poisoned (I think!). So in practice, this bit would almost always be zero for non-present ptes and we would only clear the first entry if it was actually a contiguous block. That's probably a less severe symptom than if it was always interpreted as 1 and cleared out potentially-present neighboring PTEs.
--- arch/arm64/mm/hugetlbpage.c | 51 ++++++++++++++++---------------------------- 1 file changed, 19 insertions(+), 32 deletions(-)
arch/arm64/mm/hugetlbpage.c +19 -32
@@ -100,20 +100,11 @@ static int find_num_contig(struct mm_strstatic inline int num_contig_ptes (unsigned long size,size_t *pgsize) { -int contig_ptes =0 ; +int contig_ptes =1 ; *pgsize = size;switch (size) { -#ifndef __PAGETABLE_PMD_FOLDED -case PUD_SIZE : -if (pud_sect_supported ()) - contig_ptes =1 ; -break ; -#endif -case PMD_SIZE : - contig_ptes =1 ; -break ;case CONT_PMD_SIZE : *pgsize =PMD_SIZE ; contig_ptes =CONT_PMDS ;
@@ -122,6 +113,8 @@ static inline int num_contig_ptes(unsign *pgsize =PAGE_SIZE ; contig_ptes =CONT_PTES ;break ; +default : +WARN_ON (!__hugetlb_valid_size (size)); }return contig_ptes;
@@ -163,24 +156,23 @@ static pte_t get_clear_contig(struct mm_ unsigned long pgsize, unsigned long ncontig) { -pte_t orig_pte =__ptep_get (ptep); -unsigned long i; +pte_t pte, tmp_pte; +bool present; -for (i =0 ; i < ncontig; i++, addr += pgsize, ptep++) { -pte_t pte =__ptep_get_and_clear (mm, addr, ptep); - -/* -* If HW_AFDBM is enabled, then the HW could turn on -* the dirty or accessed bit for any page in the set, -* so check them all. -*/ -if (pte_dirty (pte)) - orig_pte =pte_mkdirty (orig_pte); - -if (pte_young (pte)) - orig_pte =pte_mkyoung (orig_pte); + pte =__ptep_get_and_clear (mm, addr, ptep); + present =pte_present (pte); +while (--ncontig) { + ptep++; + addr += pgsize; + tmp_pte =__ptep_get_and_clear (mm, addr, ptep); +if (present) { +if (pte_dirty (tmp_pte)) + pte =pte_mkdirty (pte); +if (pte_young (tmp_pte)) + pte =pte_mkyoung (pte); + } } -return orig_pte; +return pte; } static pte_t get_clear_contig_flush(struct mm_struct *mm,
@@ -401,13 +393,8 @@ pte_t huge_ptep_get_and_clear(struct mm_ {int ncontig;size_t pgsize; -pte_t orig_pte =__ptep_get (ptep); - -if (!pte_cont (orig_pte)) -return __ptep_get_and_clear (mm, addr, ptep); - - ncontig =find_num_contig (mm, addr, ptep, &pgsize); + ncontig =num_contig_ptes (sz, &pgsize);return get_clear_contig (mm, addr, ptep, pgsize, ncontig); }
Greg Kroah-Hartman
maintainerPATCH 199/207 iio: hid-sensor-prox: Split difference from multiple channels
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ricardo Ribalda <[email protected]>
[ Upstream commit 4eba4d92906c3814ca3ec65c16af27c46c12342e ]
When the driver was originally created, it was decided that sampling_frequency and hysteresis would be shared_per_type instead of shared_by_all (even though it is internally shared by all). Eg:in_proximity_rawin_proximity_sampling_frequency
When we introduced support for more channels, we continued with shared_by_type which. Eg:in_proximity0_rawin_proximity1_rawin_proximity_sampling_frequencyin_attention_rawin_attention_sampling_frequency
Ideally we should change to shared_by_all, but it is not an option, because the current naming has been a stablished ABI by now. Luckily we can use separate instead. That will be more consistent:in_proximity0_rawin_proximity0_sampling_frequencyin_proximity1_rawin_proximity1_sampling_frequencyin_attention_rawin_attention_sampling_frequency
--- drivers/iio/light/hid-sensor-prox.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/iio/light/hid-sensor-prox.c +4 -3
@@ -49,9 +49,10 @@ static const u32 prox_sensitivity_addresses[] = {#define PROX_CHANNEL (_is_proximity, _channel) \ {\ .type = _is_proximity ? IIO_PROXIMITY : IIO_ATTENTION,\ - .info_mask_separate = _is_proximity ? BIT(IIO_CHAN_INFO_RAW) :\ - BIT(IIO_CHAN_INFO_PROCESSED),\ - .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_OFFSET) |\ + .info_mask_separate = \ + (_is_proximity ? BIT(IIO_CHAN_INFO_RAW) :\ + BIT(IIO_CHAN_INFO_PROCESSED)) |\ + BIT(IIO_CHAN_INFO_OFFSET) |\ BIT(IIO_CHAN_INFO_SCALE) |\ BIT(IIO_CHAN_INFO_SAMP_FREQ) |\ BIT(IIO_CHAN_INFO_HYSTERESIS),\
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 200/207 dt-bindings: iio: dac: adi-axi-adc: fix ad7606 pwm-names
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Angelo Dureghello <[email protected]>
[ Upstream commit 02ccd7e5d81af4ae20852fc1ad67e7d943fa5778 ]
Fix make dt_binding_check warning:
DTC [C] Documentation/devicetree/bindings/iio/adc/adi,axi-adc.example.dtb .../adc/adi,axi-adc.example.dtb: adc@0: pwm-names: ['convst1'] is too short
from schema $id: http://devicetree.org/schemas/iio/adc/adi,ad7606.yaml#
Add "minItems" to pwm-names, it allows to use one single pwm when connected to both adc conversion inputs.
--- Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml +1 -0
@@ -146,6 +146,7 @@ properties: maxItems: 2 pwm-names: + minItems: 1 items: - const: convst1 - const: convst2
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 201/207 iio: adc: ad7606: fix wrong scale available
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Angelo Dureghello <[email protected]>
[ Upstream commit bead181694df16de464ca2392d0cec2cf15fb978 ]
Fix wrong scale available list since only one value is returned:
...
iio:device1: ad7606b (buffer capable)
8 channels found:
voltage0: (input, index: 0, format: le:S16/16>>0)
2 channel-specific attributes found:
attr 0: scale value: 0.305176
attr 1: scale_available value: 0.076293
Fix as:
voltage0: (input, index: 0, format: le:S16/16>>0)
2 channel-specific attributes found:
attr 0: scale value: 0.305176
attr 1: scale_available value: 0.076293 0.152588 0.305176--- drivers/iio/adc/ad7606.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iio/adc/ad7606.c +1 -1
@@ -1039,7 +1039,7 @@ static int ad7606_read_avail(struct iio_dev *indio_dev, cs = &st->chan_scales[ch]; *vals = (int *)cs->scale_avail; - *length = cs->num_scales; + *length = cs->num_scales *2 ; *type =IIO_VAL_INT_PLUS_MICRO ;return IIO_AVAIL_LIST ;
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 202/207 kbuild: hdrcheck: fix cross build with clang
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Arnd Bergmann <[email protected]>
[ Upstream commit 02e9a22ceef0227175e391902d8760425fa072c6 ]
The headercheck tries to call clang with a mix of compiler arguments that don't include the target architecture. When building e.g. x86 headers on arm64, this produces a warning like
clang: warning: unknown platform, assuming -mfloat-abi=soft
Add in the KBUILD_CPPFLAGS, which contain the target, in order to make it build properly.
See also 1b71c2fb04e7 ("kbuild: userprogs: fix bitsize and target detection on clang").
--- usr/include/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
usr/include/Makefile +1 -1
@@ -10,7 +10,7 @@ UAPI_CFLAGS := -std=c90 -Wall -Werror=implicit-function-declaration # In theory, we do not care -m32 or -m64 for header compile tests. # It is here just because CONFIG_CC_CAN_LINK is tested with -m32 or -m64. -UAPI_CFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CFLAGS)) +UAPI_CFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CPPFLAGS) $(KBUILD_CFLAGS)) # USERCFLAGS might contain sysroot location for CC. UAPI_CFLAGS += $(USERCFLAGS)
Signature · 1 line
2.39.5
Greg Kroah-Hartman
maintainerPATCH 203/207 arm64: Kconfig: Remove selecting replaced HAVE_FUNCTION_GRAPH_RETVAL
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lukas Bulwahn <[email protected]>
commit f458b2165d7ac0f2401fff48f19c8f864e7e1e38 upstream.
Commit a3ed4157b7d8 ("fgraph: Replace fgraph_ret_regs with ftrace_regs") replaces the config HAVE_FUNCTION_GRAPH_RETVAL with the config HAVE_FUNCTION_GRAPH_FREGS, and it replaces all the select commands in the various architecture Kconfig files. In the arm64 architecture, the commit adds the 'select HAVE_FUNCTION_GRAPH_FREGS', but misses to remove the 'select HAVE_FUNCTION_GRAPH_RETVAL', i.e., the select on the replaced config.
Remove selecting the replaced config. No functional change, just cleanup.
--- arch/arm64/Kconfig | 1 - 1 file changed, 1 deletion(-)
arch/arm64/Kconfig +0 -1
@@ -221,7 +221,6 @@ config ARM64 select HAVE_FUNCTION_ERROR_INJECTION select HAVE_FUNCTION_GRAPH_FREGS select HAVE_FUNCTION_GRAPH_TRACER - select HAVE_FUNCTION_GRAPH_RETVAL select HAVE_GCC_PLUGINS select HAVE_HARDLOCKUP_DETECTOR_PERF if PERF_EVENTS && \ HW_PERF_EVENTS && HAVE_PERF_EVENTS_NMI
Greg Kroah-Hartman
maintainerPATCH 204/207 fprobe: Always unregister fgraph function from ops
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steven Rostedt <[email protected]>
commit ded9140622358a154efb3a777025fa7f7ae2c2d9 upstream.
When the last fprobe is removed, it calls unregister_ftrace_graph() to remove the graph_ops from function graph. The issue is when it does so, it calls return before removing the function from its graph ops via ftrace_set_filter_ips(). This leaves the last function lingering in the fprobe's fgraph ops and if a probe is added it also enables that last function (even though the callback will just drop it, it does add unneeded overhead to make that call).
# echo "f:myevent1 kernel_clone" >> /sys/kernel/tracing/dynamic_events # cat /sys/kernel/tracing/enabled_functions kernel_clone (1) tramp: 0xffffffffc02f3000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60
# echo "f:myevent2 schedule_timeout" >> /sys/kernel/tracing/dynamic_events # cat /sys/kernel/tracing/enabled_functions kernel_clone (1) tramp: 0xffffffffc02f3000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60 schedule_timeout (1) tramp: 0xffffffffc02f3000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60
# > /sys/kernel/tracing/dynamic_events
# cat /sys/kernel/tracing/enabled_functions
# echo "f:myevent3 kmem_cache_free" >> /sys/kernel/tracing/dynamic_events # cat /sys/kernel/tracing/enabled_functions kmem_cache_free (1) tramp: 0xffffffffc0219000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60 schedule_timeout (1) tramp: 0xffffffffc0219000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60
The above enabled a fprobe on kernel_clone, and then on schedule_timeout. The content of the enabled_functions shows the functions that have a callback attached to them. The fprobe attached to those functions properly. Then the fprobes were cleared, and enabled_functions was empty after that. But after adding a fprobe on kmem_cache_free, the enabled_functions shows that the schedule_timeout was attached again. This is because it was still left in the fprobe ops that is used to tell function graph what functions it wants callbacks from.
--- kernel/trace/fprobe.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
kernel/trace/fprobe.c +2 -4
@@ -374,11 +374,9 @@ static void fprobe_graph_remove_ips(unsilockdep_assert_held (&fprobe_mutex); fprobe_graph_active--; -if (!fprobe_graph_active) { -/* Q: should we unregister it ? */ +/* Q: should we unregister it ? */ +if (!fprobe_graph_active)unregister_ftrace_graph (&fprobe_graph_ops); -return ; - }ftrace_set_filter_ips (&fprobe_graph_ops.ops, addrs, num,1 ,0 ); }
Greg Kroah-Hartman
maintainerPATCH 205/207 fprobe: Fix accounting of when to unregister from function graph
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steven Rostedt <[email protected]>
commit ca26554a1498bc905c4a39fb42d55d93f3ae8df2 upstream.
When adding a new fprobe, it will update the function hash to the functions the fprobe is attached to and register with function graph to have it call the registered functions. The fprobe_graph_active variable keeps track of the number of fprobes that are using function graph.
If two fprobes attach to the same function, it increments the fprobe_graph_active for each of them. But when they are removed, the first fprobe to be removed will see that the function it is attached to is also used by another fprobe and it will not remove that function from function_graph. The logic will skip decrementing the fprobe_graph_active variable.
This causes the fprobe_graph_active variable to not go to zero when all fprobes are removed, and in doing so it does not unregister from function graph. As the fgraph ops hash will now be empty, and an empty filter hash means all functions are enabled, this triggers function graph to add a callback to the fprobe infrastructure for every function!
# echo "f:myevent1 kernel_clone" >> /sys/kernel/tracing/dynamic_events # echo "f:myevent2 kernel_clone%return" >> /sys/kernel/tracing/dynamic_events # cat /sys/kernel/tracing/enabled_functions kernel_clone (1) tramp: 0xffffffffc0024000 (ftrace_graph_func+0x0/0x60) ->ftrace_graph_func+0x0/0x60
# > /sys/kernel/tracing/dynamic_events
# cat /sys/kernel/tracing/enabled_functions trace_initcall_start_cb (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 run_init_process (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 try_to_run_init_process (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 x86_pmu_show_pmu_cap (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 cleanup_rapl_pmus (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 uncore_free_pcibus_map (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 uncore_types_exit (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 uncore_pci_exit.part.0 (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 kvm_shutdown (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 vmx_dump_msrs (1) tramp: 0xffffffffc0026000 (function_trace_call+0x0/0x170) ->function_trace_call+0x0/0x170 [..]
# cat /sys/kernel/tracing/enabled_functions | wc -l 54702
If a fprobe is being removed and all its functions are also traced by other fprobes, still decrement the fprobe_graph_active counter.
--- kernel/trace/fprobe.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/trace/fprobe.c +3 -3
@@ -378,7 +378,8 @@ static void fprobe_graph_remove_ips(unsiif (!fprobe_graph_active)unregister_ftrace_graph (&fprobe_graph_ops); -ftrace_set_filter_ips (&fprobe_graph_ops.ops, addrs, num,1 ,0 ); +if (num) +ftrace_set_filter_ips (&fprobe_graph_ops.ops, addrs, num,1 ,0 ); }static int symbols_cmp (const void *a,const void *b)
@@ -648,8 +649,7 @@ int unregister_fprobe(struct fprobe *fp) }del_fprobe_hash (fp); -if (count) -fprobe_graph_remove_ips (addrs, count); +fprobe_graph_remove_ips (addrs, count);kfree_rcu (hlist_array, rcu); fp->hlist_array =NULL ;
Greg Kroah-Hartman
maintainerPATCH 206/207 ALSA: hda: realtek: fix incorrect IS_REACHABLE() usage
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Arnd Bergmann <[email protected]>
commit d0bbe332669c5db32c8c92bc967f8e7f8d460ddf upstream.
The alternative path leads to a build error after a recent change:
sound/pci/hda/patch_realtek.c: In function 'alc233_fixup_lenovo_low_en_micmute_led':include/linux/stddef.h:9:14: error: called object is not a function or function pointer
9 | #define NULL ((void *)0)
| ^
sound/pci/hda/patch_realtek.c:5041:49: note: in expansion of macro 'NULL'
5041 | #define alc233_fixup_lenovo_line2_mic_hotkey NULL
| ^~~~sound/pci/hda/patch_realtek.c:5063:9: note: in expansion of macro 'alc233_fixup_lenovo_line2_mic_hotkey'
5063 | alc233_fixup_lenovo_line2_mic_hotkey(codec, fix, action);
Using IS_REACHABLE() is somewhat questionable here anyway since it leads to the input code not working when the HDA driver is builtin but input is in a loadable module. Replace this with a hard compile-time dependency on CONFIG_INPUT. In practice this won't chance much other than solve the compiler error because it is rare to require sound output but no input support.
--- sound/pci/hda/Kconfig | 1 + sound/pci/hda/patch_realtek.c | 5 ----- 2 files changed, 1 insertion(+), 5 deletions(-)
sound/pci/hda/Kconfig +1 -0
@@ -208,6 +208,7 @@ comment "Set to Y if you want auto-loadi config SND_HDA_CODEC_REALTEK tristate "Build Realtek HD-audio codec support" + depends on INPUT select SND_HDA_GENERIC select SND_HDA_GENERIC_LEDS select SND_HDA_SCODEC_COMPONENT
sound/pci/hda/patch_realtek.c +0 -5
@@ -5002,7 +5002,6 @@ static void alc298_fixup_samsung_amp_v2_alc298_samsung_v2_init_amps (codec,4 ); } -#if IS_REACHABLE (CONFIG_INPUT )static void gpio2_mic_hotkey_event (struct hda_codec *codec,struct hda_jack_callback *event) {
@@ -5111,10 +5110,6 @@ static void alc233_fixup_lenovo_line2_mi spec->kb_dev =NULL ; } } -#else /* INPUT */ -#define alc280_fixup_hp_gpio2_mic_hotkey NULL -#define alc233_fixup_lenovo_line2_mic_hotkey NULL -#endif /* INPUT */ static void alc269_fixup_hp_line1_mic1_led (struct hda_codec *codec,const struct hda_fixup *fix,int action)
Greg Kroah-Hartman
maintainerPATCH 207/207 nvme-tcp: Fix a C2HTermReq error message
In reply to Greg Kroah-Hartman6.13-stable review patch. If anyone has any objections, please let me know.
------------------
From: Maurizio Lombardi <[email protected]>
commit afb41b08c44e5386f2f52fa859010ac4afd2b66f upstream.
In H2CTermReq, a FES with value 0x05 means "R2T Limit Exceeded"; but in C2HTermReq the same value has a different meaning (Data Transfer Limit Exceeded).
--- drivers/nvme/host/tcp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/nvme/host/tcp.c +1 -1
@@ -788,7 +788,7 @@ static void nvme_tcp_handle_c2h_term(str [NVME_TCP_FES_PDU_SEQ_ERR] = "PDU Sequence Error", [NVME_TCP_FES_HDR_DIGEST_ERR] = "Header Digest Error", [NVME_TCP_FES_DATA_OUT_OF_RANGE] = "Data Transfer Out Of Range", - [NVME_TCP_FES_R2T_LIMIT_EXCEEDED] = "R2T Limit Exceeded", + [NVME_TCP_FES_DATA_LIMIT_EXCEEDED] = "Data Transfer Limit Exceeded", [NVME_TCP_FES_UNSUPPORTED_PARAM] = "Unsupported Parameter", };
Hello,
Quoted 7 lines · On Mon, 10 Mar 2025 18:03:13 +0100 Greg Kroah-Hartman…
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +0000. Anything received after that time might be too late.
This rc kernel passes DAMON functionality test[1] on my test machine. Attaching the test results summary below. Please note that I retrieved the kernel from linux-stable-rc tree[2].
[1] https://github.com/damonitor/damon-tests/tree/next/corr
[2] e41b0f8a619f ("Linux 6.13.7-rc1")
Thanks,
SJ
[...]
---
ok 9 selftests: damon: damos_tried_regions.py
ok 10 selftests: damon: damon_nr_regions.py
ok 11 selftests: damon: reclaim.sh
ok 12 selftests: damon: lru_sort.sh
ok 13 selftests: damon: debugfs_empty_targets.sh
ok 14 selftests: damon: debugfs_huge_count_read_write.sh
ok 15 selftests: damon: debugfs_duplicate_context_creation.sh ok 16 selftests: damon: debugfs_rm_non_contexts.sh
ok 17 selftests: damon: debugfs_target_ids_read_before_terminate_race.sh ok 18 selftests: damon: debugfs_target_ids_pid_leak.sh
ok 19 selftests: damon: sysfs_update_removed_scheme_dir.sh
ok 20 selftests: damon: sysfs_update_schemes_tried_regions_hang.py ok 1 selftests: damon-tests: kunit.sh
ok 2 selftests: damon-tests: huge_count_read_write.sh
ok 3 selftests: damon-tests: buffer_overflow.sh
ok 4 selftests: damon-tests: rm_contexts.sh
ok 5 selftests: damon-tests: record_null_deref.sh
ok 6 selftests: damon-tests: dbgfs_target_ids_read_before_terminate_race.sh ok 7 selftests: damon-tests: dbgfs_target_ids_pid_leak.sh
ok 8 selftests: damon-tests: damo_tests.sh
ok 9 selftests: damon-tests: masim-record.sh
ok 10 selftests: damon-tests: build_i386.sh
ok 11 selftests: damon-tests: build_arm64.sh # SKIP
ok 12 selftests: damon-tests: build_m68k.sh # SKIP
ok 13 selftests: damon-tests: build_i386_idle_flag.sh
ok 14 selftests: damon-tests: build_i386_highpte.sh
ok 15 selftests: damon-tests: build_nomemcg.sh
[33m
[92mPASS [39m
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Works fine on my Dell Latitude 7390 laptop with model name :
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
and Arch Linux with testing repos enabled
Den mån 10 mars 2025 kl 17:18 skrev Greg Kroah-Hartman <[email protected]>:
Quoted 924 lines
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:Greg Kroah-Hartman <[email protected]>
Linux 6.13.7-rc1Maurizio Lombardi <[email protected]>
nvme-tcp: Fix a C2HTermReq error messageArnd Bergmann <[email protected]>
ALSA: hda: realtek: fix incorrectIS_REACHABLE()usageSteven Rostedt <[email protected]>
fprobe: Fix accounting of when to unregister from function graphSteven Rostedt <[email protected]>
fprobe: Always unregister fgraph function from opsLukas Bulwahn <[email protected]>
arm64:Kconfig: Remove selecting replacedHAVE_FUNCTION_GRAPH_RETVALArnd Bergmann <[email protected]>
kbuild: hdrcheck: fix cross build with clangAngelo Dureghello <[email protected]>
iio: adc: ad7606: fix wrong scale availableAngelo Dureghello <[email protected]>
dt-bindings: iio: dac: adi-axi-adc: fix ad7606 pwm-namesRicardo Ribalda <[email protected]>
iio: hid-sensor-prox: Split difference from multiple channelsRyan Roberts <[email protected]>
arm64: hugetlb: Fixhuge_ptep_get_and_clear()for non-present ptesRyan Roberts <[email protected]>
mm: hugetlb: Add huge page size param tohuge_ptep_get_and_clear()Nayab Sayed <[email protected]>
iio: adc: at91-sama5d2_adc: fix sama7g5 realbits valueMarkus Burri <[email protected]>
iio: adc: ad7192: fix channel selectAngelo Dureghello <[email protected]>
iio: dac: ad3552r: clear reset status flagJavier Carrasco <[email protected]>
iio: light: apds9306: fixmax_scale_nanovaluesSam Winchenbach <[email protected]>
iio: filter: admv8818: Force initialization of SDOHaoyu Li <[email protected]>
drivers: virt: acrn: hsm: Use kzalloc to avoid info leak inpmcmd_ioctlAndy Shevchenko <[email protected]>
eeprom:digsy_mtc: Make GPIO lookup table match the deviceManivannan Sadhasivam <[email protected]>
bus: mhi: host:pci_generic: Usepci_try_reset_function()to avoid deadlockVisweswara Tanuku <[email protected]>
slimbus: messaging: Free transaction ID in delayed interrupt scenarioLuca Ceresoli <[email protected]>
drivers: core: fix device leak in__fw_devlink_relax_cycles()Thadeu Lima de Souza Cascardo <[email protected]>
char: misc: deallocate static minor in error pathAlexander Shishkin <[email protected]>
intel_th: pci: Add Panther Lake-P/U supportAlexander Shishkin <[email protected]>
intel_th: pci: Add Panther Lake-H supportPawel Chmielewski <[email protected]>
intel_th: pci: Add Arrow Lake supportHans de Goede <[email protected]>
mei: vsc: Use "wakeuphostint" when getting the host wakeup GPIOAlexander Usyskin <[email protected]>
mei: me: add panther lake P DIDQiu-ji Chen <[email protected]>
cdx: Fix possible UAF error indriver_override_show()Xiaoyao Li <[email protected]>
KVM: x86: Explicitly zero EAX and EBX whenPERFMON_V2isn't supported by KVMSean Christopherson <[email protected]>
KVM: x86: Snapshot the host's DEBUGCTL after disabling IRQsSean Christopherson <[email protected]>
KVM: SVM: Manually context switch DEBUGCTL if LBR virtualization is disabledSean Christopherson <[email protected]>
KVM: x86: Snapshot the host's DEBUGCTL in common x86Sean Christopherson <[email protected]>
KVM: SVM: Suppress DEBUGCTL.BTF on AMDSean Christopherson <[email protected]>
KVM: SVM: Drop DEBUGCTL[5:2] from guest's effective valueSean Christopherson <[email protected]>
KVM: SVM: Save host DR masks on CPUs with DebugSwapSean Christopherson <[email protected]>
KVM: SVM: Set RFLAGS.IF=1 in C code, to get VMRUN out of the STI shadowChristian A. Ehrhardt <[email protected]>
acpi: typec: ucsi: Introduce a ->poll_cci methodThomas Weißschuh <[email protected]>
kbuild: userprogs: use correct lld when linking through clangPrashanth K <[email protected]>
usb: gadget: Check bmAttributes only if configuration is validMarek Szyprowski <[email protected]>
usb: gadget: Fix setting self-powered state on suspendPrashanth K <[email protected]>
usb: gadget: Set self-powered based on MaxPower and bmAttributesAngeloGioacchino Del Regno <[email protected]>
usb: typec:tcpci_rt1711h: Unmask alert interrupts to fix functionalityFedor Pchelkin <[email protected]>
usb: typec: ucsi: increase timeout for PPM reset operationsBadhri Jagan Sridharan <[email protected]>
usb: dwc3: gadget: Prevent irq storm when TH re-executesThinh Nguyen <[email protected]>
usb: dwc3: Set SUSPENDENABLE soon after phy initNikita Zhandarovich <[email protected]>
usb: atm: cxacru: fix a flaw in existing endpoint checksPrashanth K <[email protected]>
usb: gadget:u_ether: Setis_suspendflag if remote wakeup failsMichal Pecio <[email protected]>
usb: xhci: Enable the TRB overfetch quirk on VIA VL805Claudiu Beznea <[email protected]>
usb:renesas_usbhs: Flush thenotify_hotplug_workAndrei Kuchynski <[email protected]>
usb: typec: ucsi: Fix NULL pointer accessMichal Pecio <[email protected]>
usb: xhci: Fix host controllers "dying" after suspend and resumeMiao Li <[email protected]>
usb: quirks: AddDELAY_INITandNO_LPMfor Prolific Mass Storage Card ReaderPawel Laszczak <[email protected]>
usb: hub: lack of clearing xHC resourcesClaudiu Beznea <[email protected]>
usb:renesas_usbhs: Usedevm_usb_get_phy()Marc Zyngier <[email protected]>
xhci: Restrict USB4 tunnel detection for USB3 devices to Intel hostsClaudiu Beznea <[email protected]>
usb:renesas_usbhs: Callclk_put()Christian Heusel <[email protected]>
Revert "drivers/card_reader/rtsx_usb: Restore interrupt based detection"Fabrizio Castro <[email protected]>
gpio: rcar: Fix missingof_node_put()callJustin Iurman <[email protected]>
net: ipv6: fix missing dst ref drop in ila lwtunnelJustin Iurman <[email protected]>
net: ipv6: fix dst ref loop in ila lwtunnelMatt Johnston <[email protected]>
mctp i3c: handle NULL header addressTakashi Iwai <[email protected]>
drm/bochs: Fix DPMS regressionLorenzo Bianconi <[email protected]>
net: dsa: mt7530: Fix traffic flooding for MMIO devicesDan Carpenter <[email protected]>
nvme-tcp: fix signedness bug innvme_tcp_init_connection()Zecheng Li <[email protected]>
sched/fair: Fix potential memory corruption inchild_cfs_rq_on_listUday Shankar <[email protected]>
ublk:set_params: properly check if parameters can be appliedJason Xing <[email protected]>
net-timestamp: support TCP GSO case for a few missing flagsEric Sandeen <[email protected]>
exfat: short-circuit zero-byte writes inexfat_file_write_iterNamjae Jeon <[email protected]>
exfat: fix soft lockup inexfat_clear_bitmapYuezhang Mo <[email protected]>
exfat: fix just enough dentries but allocate a new cluster to dirJarkko Sakkinen <[email protected]>
x86/sgx: Fix size overflows insgx_encl_create()Oscar Maes <[email protected]>
vlan: enforce underlying device typeMaxime Chevallier <[email protected]>
net: ethtool: netlink: Allow NULL nlattrs when getting aphy_deviceJakub Kicinski <[email protected]>
net: ethtool: plumb PHY stats to PHY driversOleksij Rempel <[email protected]>
ethtool: linkstate: migrate linkstate functions to support multi-PHY setupsJiayuan Chen <[email protected]>
ppp: Fix KMSAN uninit-value warning with bpfLuca Weiss <[email protected]>
net: ipa: Enable checksum for IPA_ENDPOINT_AP_MODEM_{RX,TX} for v4.7Luca Weiss <[email protected]>
net: ipa: Fix QSB data for v4.7Luca Weiss <[email protected]>
net: ipa: Fix v4.7 resource group namesVicki Pfau <[email protected]>
HID: hid-steam: Fix use-after-free when detaching deviceMaarten Lankhorst <[email protected]>
drm/xe: Remove double pageflipPeiyang Wang <[email protected]>
net: hns3: make sure ptp clock is unregister and freed ifhclge_ptp_get_cyclereturns an errorNikolay Aleksandrov <[email protected]>
be2net: fix sleeping while atomic bugs inbe_ndo_bridge_getlinkPhilipp Stanner <[email protected]>
drm/sched: Fix preprocessor guardXinghuo Chen <[email protected]>
hwmon: fix a NULL vsIS_ERR_OR_NULL()check inxgene_hwmon_probe()Eric Dumazet <[email protected]>
llc: do not useskb_get()beforedev_queue_xmit()Murad Masimov <[email protected]>
ALSA: usx2y: validate nrpacks module parameter on probeAlessio Belle <[email protected]>
drm/imagination: Fix timestamps in firmware tracesMasami Hiramatsu (Google) <[email protected]>
tracing: probe-events: Remove unusedMAX_ARG_BUF_LENmacroErik Schumacher <[email protected]>
hwmon: (ad7314) Validate leading zero bits and return errorMaud Spierings <[email protected]>
hwmon: (ntc_thermistor) Fix the ncpXXxh103 sensor tableTitus Rwantare <[email protected]>
hwmon: (pmbus) Initialise page count inpmbus_identify()Herbert Xu <[email protected]>
cred: Fix RCU warnings in override/revert_credsChristian Brauner <[email protected]>
cred: return old creds fromrevert_creds_light()Peter Zijlstra <[email protected]>
perf/core: Fixpmus_lockvs.pmus_srcuorderingVitaliy Shevtsov <[email protected]>
caif_virtio: fix wrong pointer check incfv_probe()Antoine Tenart <[email protected]>
net: gso: fix ownership in__udp_gso_segmentAntheas Kapenekakis <[email protected]>
ALSA: hda/realtek: Remove (revert) duplicate Ally X configMeir Elisha <[email protected]>
nvmet-tcp: Fix a possible sporadic response drops in weakly ordered archMaurizio Lombardi <[email protected]>
nvme-tcp: fix potential memory corruption innvme_tcp_recv_pdu()Maurizio Lombardi <[email protected]>
nvme-tcp: add basic support for the C2HTermReq PDUMaurizio Lombardi <[email protected]>
nvmet: remove old function prototypeSalah Triki <[email protected]>
bluetooth: btusb: Initialize .owner field offorce_poll_sync_fopsDave Airlie <[email protected]>
drm/nouveau: select FW cachingMasami Hiramatsu (Google) <[email protected]>
tracing: fprobe-events: Log error for exceeding the number of entry argsMasami Hiramatsu (Google) <[email protected]>
fprobe: Rewrite fprobe on function-graph tracerMasami Hiramatsu (Google) <[email protected]>
tracing: Addftrace_fill_perf_regs()for perf eventMasami Hiramatsu (Google) <[email protected]>
tracing: Addftrace_partial_regs()for convertingftrace_regstopt_regsMasami Hiramatsu (Google) <[email protected]>
fprobe: Useftrace_regsin fprobe exit handlerMasami Hiramatsu (Google) <[email protected]>
fprobe: Useftrace_regsin fprobe entry handlerMasami Hiramatsu (Google) <[email protected]>
fgraph: Replacefgraph_ret_regswithftrace_regsJohannes Berg <[email protected]>
wifi: mac80211: fix vendor-specific inheritanceJohannes Berg <[email protected]>
wifi: mac80211: fix MLE non-inheritance parsingIlan Peer <[email protected]>
wifi: mac80211: Support parsing EPCS ML elementKeith Busch <[email protected]>
nvme-ioctl: fix leaked requests on mapping errorKees Cook <[email protected]>
coredump: Only sort VMAs whencore_sort_vmasysctl is setZhang Lixu <[email protected]>
HID: intel-ish-hid: Fix use-after-free issue inishtp_hid_remove()Zhang Lixu <[email protected]>
HID: intel-ish-hid: Fix use-after-free issue inhid_ishtp_cl_remove()Yu-Chun Lin <[email protected]>
HID: google: fix unused variable warning under !CONFIG_ACPIIlan Peer <[email protected]>
wifi: iwlwifi: Fix A-MSDU TSO preparationIlan Peer <[email protected]>
wifi: iwlwifi: Free pages allocated when failing to build A-MSDUJohannes Berg <[email protected]>
wifi: iwlwifi: limit printed string from FW fileEmmanuel Grumbach <[email protected]>
wifi: iwlwifi: mvm: don't try to talk to a dead firmwareEmmanuel Grumbach <[email protected]>
wifi: iwlwifi: mvm: don't dump the firmware state upon RFKILL while suspendBenjamin Berg <[email protected]>
wifi: iwlwifi: mvm: log error for failures after D3Johannes Berg <[email protected]>
wifi: iwlwifi: mvm: clean up ROC on failureMiri Korenblit <[email protected]>
wifi: iwlwifi: fw: avoid using an uninitialized variableMa Wupeng <[email protected]>
mm: memory-hotplug: check folio ref count first indo_migrate_rangeMa Wupeng <[email protected]>
hwpoison,memory_hotplug: lock folio before unmap hwpoisoned folioBrian Geffon <[email protected]>
mm: fixfinish_fault()handling for large foliosRyan Roberts <[email protected]>
mm: don't skiparch_sync_kernel_mappings()in error pathsMa Wupeng <[email protected]>
mm: memory-failure: update ttu flag insideunmap_poisoned_folioLorenzo Stoakes <[email protected]>
mm: abortvma_modify()on merge out of memory failureHao Zhang <[email protected]>
mm/page_alloc: fix uninitialized variableOlivier Gayot <[email protected]>
block: fix conversion of GPT partition name to 7-bitQi Zheng <[email protected]>
arm: pgtable: fix NULL pointer dereference issueSuren Baghdasaryan <[email protected]>
userfaultfd: do not block on locking a large folio with raised refcountMike Snitzer <[email protected]>
NFS: fixnfs_release_folio()to not deadlock via kcompactd writebackHeiko Carstens <[email protected]>
s390/traps: Fixtest_monitor_call()inline assemblySebastian Andrzej Siewior <[email protected]>
dma: kmsan: exportkmsan_handle_dma()for modulesHaoxiang Li <[email protected]>
rapidio: fix an API misues whenrio_add_net()failsHaoxiang Li <[email protected]>
rapidio: add check forrio_add_net()inrio_scan_alloc_net()SeongJae Park <[email protected]>
selftests/damon/damon_nr_regions: sort collected regiosn before checking with min/max boundariesSeongJae Park <[email protected]>
selftests/damon/damon_nr_regions: set ops update for merge results check to 100msSeongJae Park <[email protected]>
selftests/damon/damos_quota: make real expectation of quota exceedsSeongJae Park <[email protected]>
selftests/damon/damos_quota_goal: handle minimum quota that cannot be further reducedVitaliy Shevtsov <[email protected]>
wifi: nl80211: reject cooked mode if it is set along with other flagsNikita Zhandarovich <[email protected]>
wifi: cfg80211: regulatory: improve invalid hints checkingHaoxiang Li <[email protected]>
Bluetooth: Add check formgmt_alloc_skb()inmgmt_device_connected()Haoxiang Li <[email protected]>
Bluetooth: Add check formgmt_alloc_skb()inmgmt_remote_name()Thomas Hellström <[email protected]>
drm/xe/userptr: Unmap userptrs in the mmu notifierMatthew Auld <[email protected]>
drm/xe/userptr: properly setuppfn_flags_maskThomas Hellström <[email protected]>
drm/xe: Fix fault mode invalidation with unbindTvrtko Ursulin <[email protected]>
drm/xe: Fix GT "for each engine" workaroundsKrister Johansen <[email protected]>
mptcp: fix 'scheduling while atomic' inmptcp_pm_nl_append_new_local_addrThomas Hellström <[email protected]>
drm/xe/vm: Validate userptr during gpu vma prefetchingThomas Hellström <[email protected]>
drm/xe/vm: Fix a misplaced #endifThomas Hellström <[email protected]>
drm/xe/hmm: Don't dereference struct page pointers without notifier lockThomas Hellström <[email protected]>
drm/xe/hmm: Style- and include fixesMatthew Brost <[email protected]>
drm/xe: Add staging tree for VM bindsAhmed S. Darwish <[email protected]>
x86/cpu: Properly parse CPUID leaf 0x2 TLB descriptor 0x63Ahmed S. Darwish <[email protected]>
x86/cpu: Validate CPUID leaf 0x2 EDX outputAhmed S. Darwish <[email protected]>
x86/cacheinfo: Validate CPUID leaf 0x2 EDX outputArd Biesheuvel <[email protected]>
x86/boot: Sanitize boot params before parsing command lineMingcong Bai <[email protected]>
platform/x86:thinkpad_acpi: Add battery quirk for ThinkPad X131eJohn Hubbard <[email protected]>
Revert "selftests/mm: remove local __NR_* definitions"Gabriel Krisman Bertazi <[email protected]>
Revert "mm/page_alloc.c: don't show protection in zone's ->lowmem_reserve[] for empty zone"Richard Thier <[email protected]>
drm/radeon: Fixrs400_gpu_initfor ATI mobility radeon Xpress 200MBrendan King <[email protected]>
drm/imagination: only init job done fences onceBrendan King <[email protected]>
drm/imagination: Holddrm_gem_gpuvalock for unmapBrendan King <[email protected]>
drm/imagination: avoid deadlock on fence releaseKenneth Feng <[email protected]>
drm/amd/pm: always allow ih interrupt from fwAndrew Martin <[email protected]>
drm/amdkfd: Fix NULL Pointer Dereference in KFD queueMa Ke <[email protected]>
drm/amd/display: Fix null check for pipe_ctx->plane_state in resource_build_scaling_paramsPaul Fertser <[email protected]>
hwmon: (peci/dimmtemp) Do not provide fake thresholds dataNikunj A Dadhania <[email protected]>
virt: sev-guest: Allocate request data dynamicallyHaoxiang Li <[email protected]>
btrfs: fix a leaked chunk map issue inread_one_chunk()Naohiro Aota <[email protected]>
btrfs: zoned: fix extent range end unlock incow_file_range()Kailang Yang <[email protected]>
ALSA: hda/realtek: update ALC222 depop optimizeKailang Yang <[email protected]>
ALSA: hda/realtek - add supported Mic Mute LED for Lenovo platformHoku Ishibe <[email protected]>
ALSA: hda: intel: Add Dell ALC3271 topower_savedenylistTakashi Iwai <[email protected]>
ALSA: seq: Avoid module auto-load handling at event deliveryKoichiro Den <[email protected]>
gpio: aggregator: protect driver attr handlers against module unloadNiklas Söderlund <[email protected]>
gpio: rcar: Useraw_spinlockto protect register accessNamjae Jeon <[email protected]>
ksmbd: fix bug on trap insmb2_lockNamjae Jeon <[email protected]>
ksmbd: fix use-after-free insmb2_lockNamjae Jeon <[email protected]>
ksmbd: fix out-of-bounds inparse_sec_desc()Namjae Jeon <[email protected]>
ksmbd: fix type confusion via race condition when usingipc_msg_send_requestStuart Hayhurst <[email protected]>
HID: corsair-void: Update power supply values with a unified work handlerDaniil Dulov <[email protected]>
HID: appleir: Fix potential NULL dereference at raw event handleBibo Mao <[email protected]>
LoongArch: KVM: Fix GPA size issue about VMBibo Mao <[email protected]>
LoongArch: KVM: Reload guest CSR registers after sleepBibo Mao <[email protected]>
LoongArch: KVM: Add interrupt checking for AVECBibo Mao <[email protected]>
LoongArch: Setmax_pfnwith the PFN of the last pageBibo Mao <[email protected]>
LoongArch: Set hugetlb mmap base address aligned with pmd sizeHuacai Chen <[email protected]>
LoongArch: Use pollingplay_dead()when resuming from hibernationTiezhu Yang <[email protected]>
LoongArch: Convertunreachable()toBUG()Philipp Stanner <[email protected]>
stmmac: loongson: Pass correct arg to PCI functionMasami Hiramatsu (Google) <[email protected]>
tracing: tprobe-events: Reject invalid tracepoint nameMasami Hiramatsu (Google) <[email protected]>
tracing: tprobe-events: Fix a memory leak when tprobe with $retvalRob Herring (Arm) <[email protected]>
Revert "of: reserved-memory: Fix using wrong number of cells to get property 'alignment'"Peter Zijlstra <[email protected]>
loongarch: UseASM_REACHABLEBorislav Petkov (AMD) <[email protected]>
x86/microcode/AMD: Add some forgotten models to the SHA checkSteve French <[email protected]>
smb311: failure to open files of length 1040 when mounting with SMB3.1.1 POSIX extensionsPali Rohár <[email protected]>
cifs: Remove symlink member fromcifs_open_info_dataunionYutaro Ohno <[email protected]>
rust: block: fix formatting in GenDisk docAndrew Cooper <[email protected]>
x86/amd_nb: Userdmsr_safe()inamd_get_mmconfig_range()-------------
Diffstat:
Documentation/admin-guide/sysctl/kernel.rst | 11 + .../devicetree/bindings/iio/adc/adi,ad7606.yaml | 1 + Makefile | 9 +- arch/arm/mm/fault-armv.c | 37 +- arch/arm64/Kconfig | 2 +- arch/arm64/include/asm/ftrace.h | 49 +- arch/arm64/include/asm/hugetlb.h | 4 +- arch/arm64/kernel/asm-offsets.c | 12 - arch/arm64/kernel/entry-ftrace.S | 32 +- arch/arm64/mm/hugetlbpage.c | 59 +- arch/loongarch/Kconfig | 3 +- arch/loongarch/include/asm/bug.h | 13 +- arch/loongarch/include/asm/ftrace.h | 32 +- arch/loongarch/include/asm/hugetlb.h | 6 +- arch/loongarch/kernel/asm-offsets.c | 12 - arch/loongarch/kernel/machine_kexec.c | 4 +- arch/loongarch/kernel/mcount.S | 17 +- arch/loongarch/kernel/mcount_dyn.S | 14 +- arch/loongarch/kernel/setup.c | 3 + arch/loongarch/kernel/smp.c | 47 +- arch/loongarch/kvm/exit.c | 6 + arch/loongarch/kvm/main.c | 7 + arch/loongarch/kvm/vcpu.c | 2 +- arch/loongarch/kvm/vm.c | 6 +- arch/loongarch/mm/mmap.c | 6 +- arch/mips/include/asm/hugetlb.h | 6 +- arch/parisc/include/asm/hugetlb.h | 2 +- arch/parisc/mm/hugetlbpage.c | 2 +- arch/powerpc/include/asm/ftrace.h | 13 + arch/powerpc/include/asm/hugetlb.h | 6 +- arch/riscv/Kconfig | 2 +- arch/riscv/include/asm/ftrace.h | 45 +- arch/riscv/include/asm/hugetlb.h | 3 +- arch/riscv/kernel/mcount.S | 24 +- arch/riscv/mm/hugetlbpage.c | 2 +- arch/s390/Kconfig | 3 +- arch/s390/include/asm/ftrace.h | 36 +- arch/s390/include/asm/hugetlb.h | 18 +- arch/s390/kernel/asm-offsets.c | 6 - arch/s390/kernel/mcount.S | 12 +- arch/s390/kernel/traps.c | 6 +- arch/s390/mm/hugetlbpage.c | 4 +- arch/sparc/include/asm/hugetlb.h | 2 +- arch/sparc/mm/hugetlbpage.c | 2 +- arch/x86/Kconfig | 3 +- arch/x86/boot/compressed/pgtable_64.c | 2 + arch/x86/include/asm/ftrace.h | 33 +- arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kernel/amd_nb.c | 9 +- arch/x86/kernel/cpu/cacheinfo.c | 2 +- arch/x86/kernel/cpu/intel.c | 52 +- arch/x86/kernel/cpu/microcode/amd.c | 6 + arch/x86/kernel/cpu/sgx/ioctl.c | 7 + arch/x86/kernel/ftrace_32.S | 13 +- arch/x86/kernel/ftrace_64.S | 17 +- arch/x86/kvm/cpuid.c | 2 +- arch/x86/kvm/svm/sev.c | 13 +- arch/x86/kvm/svm/svm.c | 49 ++ arch/x86/kvm/svm/svm.h | 2 +- arch/x86/kvm/svm/vmenter.S | 10 +- arch/x86/kvm/vmx/vmx.c | 8 +- arch/x86/kvm/vmx/vmx.h | 2 - arch/x86/kvm/x86.c | 2 + block/partitions/efi.c | 2 +- drivers/base/core.c | 1 + drivers/block/ublk_drv.c | 7 +- drivers/bluetooth/btusb.c | 1 + drivers/bus/mhi/host/pci_generic.c | 5 +- drivers/cdx/cdx.c | 6 +- drivers/char/misc.c | 2 +- drivers/gpio/gpio-aggregator.c | 20 +- drivers/gpio/gpio-rcar.c | 31 +- drivers/gpu/drm/amd/amdkfd/kfd_queue.c | 4 +- drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 3 +- drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0.c | 12 +- drivers/gpu/drm/imagination/pvr_fw_meta.c | 6 +- drivers/gpu/drm/imagination/pvr_fw_trace.c | 4 +- drivers/gpu/drm/imagination/pvr_queue.c | 18 +- drivers/gpu/drm/imagination/pvr_queue.h | 4 + drivers/gpu/drm/imagination/pvr_vm.c | 134 ++++- drivers/gpu/drm/imagination/pvr_vm.h | 3 + drivers/gpu/drm/nouveau/Kconfig | 1 + drivers/gpu/drm/radeon/r300.c | 3 +- drivers/gpu/drm/radeon/radeon_asic.h | 1 + drivers/gpu/drm/radeon/rs400.c | 18 +- drivers/gpu/drm/scheduler/gpu_scheduler_trace.h | 4 +- drivers/gpu/drm/tiny/bochs.c | 5 +- drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 - drivers/gpu/drm/xe/xe_gt.c | 4 +- drivers/gpu/drm/xe/xe_hmm.c | 194 ++++-- drivers/gpu/drm/xe/xe_hmm.h | 7 + drivers/gpu/drm/xe/xe_pt.c | 96 +-- drivers/gpu/drm/xe/xe_pt_walk.c | 3 +- drivers/gpu/drm/xe/xe_pt_walk.h | 4 + drivers/gpu/drm/xe/xe_vm.c | 100 +++- drivers/gpu/drm/xe/xe_vm.h | 10 +- drivers/gpu/drm/xe/xe_vm_types.h | 8 +- drivers/hid/hid-appleir.c | 2 +- drivers/hid/hid-corsair-void.c | 83 +-- drivers/hid/hid-google-hammer.c | 2 + drivers/hid/hid-steam.c | 2 +- drivers/hid/intel-ish-hid/ishtp-hid-client.c | 2 +- drivers/hid/intel-ish-hid/ishtp-hid.c | 4 +- drivers/hwmon/ad7314.c | 10 + drivers/hwmon/ntc_thermistor.c | 66 +-- drivers/hwmon/peci/dimmtemp.c | 10 +- drivers/hwmon/pmbus/pmbus.c | 2 + drivers/hwmon/xgene-hwmon.c | 2 +- drivers/hwtracing/intel_th/pci.c | 15 + drivers/iio/adc/ad7192.c | 2 +- drivers/iio/adc/ad7606.c | 2 +- drivers/iio/adc/at91-sama5d2_adc.c | 68 ++- drivers/iio/dac/ad3552r.c | 6 + drivers/iio/filter/admv8818.c | 14 +- drivers/iio/light/apds9306.c | 4 +- drivers/iio/light/hid-sensor-prox.c | 7 +- drivers/misc/cardreader/rtsx_usb.c | 15 - drivers/misc/eeprom/digsy_mtc_eeprom.c | 2 +- drivers/misc/mei/hw-me-regs.h | 2 + drivers/misc/mei/pci-me.c | 2 + drivers/misc/mei/vsc-tp.c | 2 +- drivers/net/caif/caif_virtio.c | 2 +- drivers/net/dsa/mt7530.c | 8 +- drivers/net/ethernet/emulex/benet/be.h | 2 +- drivers/net/ethernet/emulex/benet/be_cmds.c | 197 ++++--- drivers/net/ethernet/emulex/benet/be_main.c | 2 +- .../net/ethernet/hisilicon/hns3/hns3pf/hclge_ptp.c | 2 +- .../net/ethernet/stmicro/stmmac/dwmac-loongson.c | 6 +- drivers/net/ipa/data/ipa_data-v4.7.c | 18 +- drivers/net/mctp/mctp-i3c.c | 3 + drivers/net/phy/phy.c | 43 ++ drivers/net/phy/phy_device.c | 2 + drivers/net/ppp/ppp_generic.c | 28 +- drivers/net/wireless/intel/iwlwifi/fw/dump.c | 3 + drivers/net/wireless/intel/iwlwifi/iwl-drv.c | 2 +- drivers/net/wireless/intel/iwlwifi/mvm/d3.c | 77 ++- drivers/net/wireless/intel/iwlwifi/mvm/debugfs.c | 7 + .../net/wireless/intel/iwlwifi/mvm/time-event.c | 2 + drivers/net/wireless/intel/iwlwifi/pcie/internal.h | 5 +- drivers/net/wireless/intel/iwlwifi/pcie/tx-gen2.c | 6 +- drivers/net/wireless/intel/iwlwifi/pcie/tx.c | 20 +- drivers/nvme/host/ioctl.c | 12 +- drivers/nvme/host/tcp.c | 81 ++- drivers/nvme/target/nvmet.h | 1 - drivers/nvme/target/tcp.c | 15 +- drivers/of/of_reserved_mem.c | 4 +- drivers/platform/x86/thinkpad_acpi.c | 1 + drivers/rapidio/devices/rio_mport_cdev.c | 3 +- drivers/rapidio/rio-scan.c | 5 +- drivers/slimbus/messaging.c | 5 +- drivers/usb/atm/cxacru.c | 13 +- drivers/usb/core/hub.c | 33 ++ drivers/usb/core/quirks.c | 4 + drivers/usb/dwc3/core.c | 85 +-- drivers/usb/dwc3/core.h | 2 +- drivers/usb/dwc3/drd.c | 4 +- drivers/usb/dwc3/gadget.c | 10 +- drivers/usb/gadget/composite.c | 17 +- drivers/usb/gadget/function/u_ether.c | 4 +- drivers/usb/host/xhci-hub.c | 8 + drivers/usb/host/xhci-mem.c | 3 +- drivers/usb/host/xhci-pci.c | 10 +- drivers/usb/host/xhci.c | 6 +- drivers/usb/host/xhci.h | 2 +- drivers/usb/renesas_usbhs/common.c | 6 +- drivers/usb/renesas_usbhs/mod_gadget.c | 2 +- drivers/usb/typec/tcpm/tcpci_rt1711h.c | 11 + drivers/usb/typec/ucsi/ucsi.c | 25 +- drivers/usb/typec/ucsi/ucsi.h | 2 + drivers/usb/typec/ucsi/ucsi_acpi.c | 21 +- drivers/usb/typec/ucsi/ucsi_ccg.c | 1 + drivers/usb/typec/ucsi/ucsi_glink.c | 1 + drivers/usb/typec/ucsi/ucsi_stm32g0.c | 1 + drivers/usb/typec/ucsi/ucsi_yoga_c630.c | 1 + drivers/virt/acrn/hsm.c | 6 +- drivers/virt/coco/sev-guest/sev-guest.c | 24 +- fs/btrfs/inode.c | 9 +- fs/btrfs/volumes.c | 1 + fs/coredump.c | 15 +- fs/exfat/balloc.c | 10 +- fs/exfat/exfat_fs.h | 2 +- fs/exfat/fatent.c | 11 +- fs/exfat/file.c | 2 +- fs/exfat/namei.c | 2 +- fs/nfs/file.c | 3 +- fs/smb/client/cifsglob.h | 6 +- fs/smb/client/inode.c | 2 +- fs/smb/client/reparse.h | 28 +- fs/smb/client/smb1ops.c | 4 +- fs/smb/client/smb2inode.c | 4 + fs/smb/client/smb2ops.c | 3 +- fs/smb/server/smb2pdu.c | 8 +- fs/smb/server/smbacl.c | 16 + fs/smb/server/transport_ipc.c | 1 + include/asm-generic/hugetlb.h | 2 +- include/linux/compaction.h | 5 + include/linux/cred.h | 9 +- include/linux/ethtool.h | 23 + include/linux/fprobe.h | 62 +- include/linux/ftrace.h | 66 ++- include/linux/ftrace_regs.h | 2 + include/linux/hugetlb.h | 4 +- include/linux/nvme-tcp.h | 2 + include/linux/phy.h | 36 ++ include/linux/phylib_stubs.h | 42 ++ include/linux/sched.h | 2 +- kernel/events/core.c | 4 +- kernel/sched/fair.c | 6 +- kernel/trace/Kconfig | 18 +- kernel/trace/bpf_trace.c | 16 +- kernel/trace/fgraph.c | 21 +- kernel/trace/fprobe.c | 653 +++++++++++++++------ kernel/trace/trace_fprobe.c | 37 +- kernel/trace/trace_probe.h | 5 +- lib/test_fprobe.c | 51 +- mm/compaction.c | 3 + mm/hugetlb.c | 4 +- mm/internal.h | 5 +- mm/kmsan/hooks.c | 1 + mm/memory-failure.c | 63 +- mm/memory.c | 21 +- mm/memory_hotplug.c | 28 +- mm/page_alloc.c | 4 +- mm/userfaultfd.c | 17 +- mm/vma.c | 12 +- mm/vmalloc.c | 4 +- net/8021q/vlan.c | 3 +- net/bluetooth/mgmt.c | 5 + net/ethtool/cabletest.c | 8 +- net/ethtool/linkstate.c | 26 +- net/ethtool/netlink.c | 6 +- net/ethtool/netlink.h | 5 +- net/ethtool/phy.c | 2 +- net/ethtool/plca.c | 6 +- net/ethtool/pse-pd.c | 4 +- net/ethtool/stats.c | 18 + net/ethtool/strset.c | 2 +- net/ipv4/tcp_offload.c | 11 +- net/ipv4/udp_offload.c | 8 +- net/ipv6/ila/ila_lwt.c | 4 +- net/llc/llc_s_ac.c | 49 +- net/mac80211/ieee80211_i.h | 2 + net/mac80211/mlme.c | 1 + net/mac80211/parse.c | 164 ++++-- net/mptcp/pm_netlink.c | 18 +- net/wireless/nl80211.c | 5 + net/wireless/reg.c | 3 +- rust/kernel/block/mq/gen_disk.rs | 6 +- samples/fprobe/fprobe_example.c | 4 +- sound/core/seq/seq_clientmgr.c | 46 +- sound/pci/hda/Kconfig | 1 + sound/pci/hda/hda_intel.c | 2 + sound/pci/hda/patch_realtek.c | 107 +++- sound/usb/usx2y/usbusx2y.c | 11 + sound/usb/usx2y/usbusx2y.h | 26 + sound/usb/usx2y/usbusx2yaudio.c | 27 - tools/testing/selftests/damon/damon_nr_regions.py | 2 + tools/testing/selftests/damon/damos_quota.py | 9 +- tools/testing/selftests/damon/damos_quota_goal.py | 3 + tools/testing/selftests/mm/hugepage-mremap.c | 2 +- tools/testing/selftests/mm/ksm_functional_tests.c | 8 +- tools/testing/selftests/mm/memfd_secret.c | 14 +- tools/testing/selftests/mm/mkdirty.c | 8 +- tools/testing/selftests/mm/mlock2.h | 1 - tools/testing/selftests/mm/protection_keys.c | 2 +- tools/testing/selftests/mm/uffd-common.c | 4 + tools/testing/selftests/mm/uffd-stress.c | 15 +- tools/testing/selftests/mm/uffd-unit-tests.c | 14 +- usr/include/Makefile | 2 +- 269 files changed, 3214 insertions(+), 1547 deletions(-)
Hi Greg
no regressions here on x86_64 (RKL, Intel 11th Gen. CPU)
Thanks
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.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 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v6.13:
10 builds: 10 pass, 0 fail
28 boots: 28 pass, 0 fail
116 tests: 116 pass, 0 failLinux version: 6.13.7-rc1-g2fe515e18cba
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra186-p3509-0000+p3636-0001, tegra194-p2972-0000,
tegra194-p3509-0000+p3668-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04Jon
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
Thanks! Tested with Alpine Linux configs and packaging.
Hi Greg
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
6.13.7-rc1 tested.
Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.
Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)
[ 0.000000] Linux version 6.13.7-rc1rv-g2fe515e18cba
(takeshi@ThinkPadX1Gen10J0764) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Tue Mar 11 18:49:13 JST 2025
Thanks
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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.
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
## Build
* kernel: 6.13.7-rc1
* git: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
* git commit: 2fe515e18cbae9a204a7662d4b3b5760633f31fa
* git describe: v6.13.6-208-g2fe515e18cba
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.13.y/build/v6.13.6-208-g2fe515e18cba
## Test Regressions (compared to v6.13.3-552-g3244959bfa6b)
## Metric Regressions (compared to v6.13.3-552-g3244959bfa6b)
## Test Fixes (compared to v6.13.3-552-g3244959bfa6b)
## Metric Fixes (compared to v6.13.3-552-g3244959bfa6b)
## Test result summary
total: 74660, pass: 60565, fail: 2624, skip: 11471, xfail: 0
## Build Summary
* arc: 6 total, 5 passed, 1 failed
* arm: 143 total, 137 passed, 6 failed
* arm64: 58 total, 56 passed, 2 failed
* i386: 22 total, 19 passed, 3 failed
* mips: 38 total, 33 passed, 5 failed
* parisc: 5 total, 3 passed, 2 failed
* powerpc: 44 total, 42 passed, 2 failed
* riscv: 27 total, 24 passed, 3 failed
* s390: 26 total, 25 passed, 1 failed
* sh: 6 total, 5 passed, 1 failed
* sparc: 5 total, 3 passed, 2 failed
* x86_64: 50 total, 49 passed, 1 failed
## Test suites summary
* boot
* commands
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-exec
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-kcmp
* kselftest-kvm
* kselftest-membarrier
* kselftest-memfd
* kselftest-mincore
* kselftest-mqueue
* kselftest-net
* kselftest-net-mptcp
* kselftest-openat2
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-rust
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-tc-testing
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user_events
* kselftest-vDSO
* kselftest-x86
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-build-clang
* log-parser-build-gcc
* log-parser-test
* ltp-capability
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-crypto
* ltp-cve
* ltp-fcntl-locktests
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-hugetlb
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* perf
* rcutorture
--
Linaro LKFT
https://lkft.linaro.org
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
The kernel, bpf tool, perf tool, and kselftest builds fine for v6.13.7-rc1 on x86 and arm64 Azure VM.
Kernel binary size for x86 build:
text data bss dec hex filename 29937422 17837074 6320128 54094624 3396b20 vmlinux
Kernel binary size for arm64 build:
text data bss dec hex filename 36684450 15081117 1054416 52819983 325f80f vmlinux
Thanks,
Hardik
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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, 12 Mar 2025 17:04:00 +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/v6.x/stable-review/patch-6.13.7-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.13.y
and the diffstat can be found below.thanks,
greg k-h
Thanks! Builded and tested with Alpine Linux configs.
Am 10.03.2025 um 18:03 schrieb Greg Kroah-Hartman:
Quoted 4 lines
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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.
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.
Beste Grüße,
Peter Schneider
Signature · 8 lines
Climb the mountain not to plant your flag, but to embrace the challenge, enjoy the air and behold the view. Climb it so you can see the world, not so the world can see you. -- David McCullough Jr. OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244 Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc https://keys.mailvelope.com/pks/lookup?op=get&[email protected] https://keys.mailvelope.com/pks/lookup?op=get&[email protected]
Sorry, please disregard my mail. I accidentally replied to the wrong, older thread. I meant to reply to the 6.13-rc8 review thread. My bad... 🙄
Beste Grüße,
Peter Schneider
Signature · 20 lines
Climb the mountain not to plant your flag, but to embrace the challenge, enjoy the air and behold the view. Climb it so you can see the world, not so the world can see you. -- David McCullough Jr. Peter Schneider Tölzer Str. 1 D-82549 Königsdorf OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244 Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc https://keys.mailvelope.com/pks/lookup?op=get&[email protected] https://keys.mailvelope.com/pks/lookup?op=get&[email protected] M: [email protected] M: [email protected] P: +49 8179 929164 P: +49 171 4568637 F: +49 8179 9976800 Am 21.03.2025 um 01:15 schrieb Peter Schneider:
Quoted 14 lines
Am 10.03.2025 um 18:03 schrieb Greg Kroah-Hartman:
Quoted 4 lines
This is the start of the stable review cycle for the 6.13.7 release. There are 207 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.
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg oddities or regressions found.
Tested-by Peter Schneider <[email protected]>Beste Grüße,
Peter Schneider