From: Sasha Levin Date: Fri, 7 Aug 2020 20:10:52 +0000 (-0400) Subject: Fixes for 4.14 X-Git-Tag: v4.19.139~25 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a9c347473bcc779fe96ace6256aec129ba8b1c5c;p=thirdparty%2Fkernel%2Fstable-queue.git Fixes for 4.14 Signed-off-by: Sasha Levin --- diff --git a/queue-4.14/atm-fix-atm_dev-refcnt-leaks-in-atmtcp_remove_persis.patch b/queue-4.14/atm-fix-atm_dev-refcnt-leaks-in-atmtcp_remove_persis.patch new file mode 100644 index 00000000000..9e0bee24eaa --- /dev/null +++ b/queue-4.14/atm-fix-atm_dev-refcnt-leaks-in-atmtcp_remove_persis.patch @@ -0,0 +1,54 @@ +From c49b638c74f7dc8b36127be1b99850ca03d2bcff Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 29 Jul 2020 21:06:59 +0800 +Subject: atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent + +From: Xin Xiong + +[ Upstream commit 51875dad43b44241b46a569493f1e4bfa0386d86 ] + +atmtcp_remove_persistent() invokes atm_dev_lookup(), which returns a +reference of atm_dev with increased refcount or NULL if fails. + +The refcount leaks issues occur in two error handling paths. If +dev_data->persist is zero or PRIV(dev)->vcc isn't NULL, the function +returns 0 without decreasing the refcount kept by a local variable, +resulting in refcount leaks. + +Fix the issue by adding atm_dev_put() before returning 0 both when +dev_data->persist is zero or PRIV(dev)->vcc isn't NULL. + +Signed-off-by: Xin Xiong +Signed-off-by: Xiyu Yang +Signed-off-by: Xin Tan +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/atm/atmtcp.c | 10 ++++++++-- + 1 file changed, 8 insertions(+), 2 deletions(-) + +diff --git a/drivers/atm/atmtcp.c b/drivers/atm/atmtcp.c +index afebeb1c3e1e9..723bad1201cc5 100644 +--- a/drivers/atm/atmtcp.c ++++ b/drivers/atm/atmtcp.c +@@ -432,9 +432,15 @@ static int atmtcp_remove_persistent(int itf) + return -EMEDIUMTYPE; + } + dev_data = PRIV(dev); +- if (!dev_data->persist) return 0; ++ if (!dev_data->persist) { ++ atm_dev_put(dev); ++ return 0; ++ } + dev_data->persist = 0; +- if (PRIV(dev)->vcc) return 0; ++ if (PRIV(dev)->vcc) { ++ atm_dev_put(dev); ++ return 0; ++ } + kfree(dev_data); + atm_dev_put(dev); + atm_dev_deregister(dev); +-- +2.25.1 + diff --git a/queue-4.14/cfg80211-check-vendor-command-doit-pointer-before-us.patch b/queue-4.14/cfg80211-check-vendor-command-doit-pointer-before-us.patch new file mode 100644 index 00000000000..a76c96f25a5 --- /dev/null +++ b/queue-4.14/cfg80211-check-vendor-command-doit-pointer-before-us.patch @@ -0,0 +1,50 @@ +From 615514d8ccafc099b0437e7730c6bf6770fab580 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 6 Jul 2020 17:13:53 -0400 +Subject: cfg80211: check vendor command doit pointer before use + +From: Julian Squires + +[ Upstream commit 4052d3d2e8f47a15053320bbcbe365d15610437d ] + +In the case where a vendor command does not implement doit, and has no +flags set, doit would not be validated and a NULL pointer dereference +would occur, for example when invoking the vendor command via iw. + +I encountered this while developing new vendor commands. Perhaps in +practice it is advisable to always implement doit along with dumpit, +but it seems reasonable to me to always check doit anyway, not just +when NEED_WDEV. + +Signed-off-by: Julian Squires +Link: https://lore.kernel.org/r/20200706211353.2366470-1-julian@cipht.net +Signed-off-by: Johannes Berg +Signed-off-by: Sasha Levin +--- + net/wireless/nl80211.c | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c +index d0b75781e6f7a..9be7ee322093b 100644 +--- a/net/wireless/nl80211.c ++++ b/net/wireless/nl80211.c +@@ -11859,13 +11859,13 @@ static int nl80211_vendor_cmd(struct sk_buff *skb, struct genl_info *info) + if (!wdev_running(wdev)) + return -ENETDOWN; + } +- +- if (!vcmd->doit) +- return -EOPNOTSUPP; + } else { + wdev = NULL; + } + ++ if (!vcmd->doit) ++ return -EOPNOTSUPP; ++ + if (info->attrs[NL80211_ATTR_VENDOR_DATA]) { + data = nla_data(info->attrs[NL80211_ATTR_VENDOR_DATA]); + len = nla_len(info->attrs[NL80211_ATTR_VENDOR_DATA]); +-- +2.25.1 + diff --git a/queue-4.14/drivers-hv-vmbus-ignore-channelmsg_tl_connect_result.patch b/queue-4.14/drivers-hv-vmbus-ignore-channelmsg_tl_connect_result.patch new file mode 100644 index 00000000000..2edbc8060c2 --- /dev/null +++ b/queue-4.14/drivers-hv-vmbus-ignore-channelmsg_tl_connect_result.patch @@ -0,0 +1,107 @@ +From 3340dc2f677ada482be46a2908ee137d723d4bad Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 19 Jan 2020 15:29:22 -0800 +Subject: Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23) + +From: Dexuan Cui + +[ Upstream commit ddc9d357b991838c2d975e8d7e4e9db26f37a7ff ] + +When a Linux hv_sock app tries to connect to a Service GUID on which no +host app is listening, a recent host (RS3+) sends a +CHANNELMSG_TL_CONNECT_RESULT (23) message to Linux and this triggers such +a warning: + +unknown msgtype=23 +WARNING: CPU: 2 PID: 0 at drivers/hv/vmbus_drv.c:1031 vmbus_on_msg_dpc + +Actually Linux can safely ignore the message because the Linux app's +connect() will time out in 2 seconds: see VSOCK_DEFAULT_CONNECT_TIMEOUT +and vsock_stream_connect(). We don't bother to make use of the message +because: 1) it's only supported on recent hosts; 2) a non-trivial effort +is required to use the message in Linux, but the benefit is small. + +So, let's not see the warning by silently ignoring the message. + +Signed-off-by: Dexuan Cui +Reviewed-by: Michael Kelley +Signed-off-by: Sasha Levin +--- + drivers/hv/channel_mgmt.c | 21 +++++++-------------- + drivers/hv/vmbus_drv.c | 4 ++++ + include/linux/hyperv.h | 2 ++ + 3 files changed, 13 insertions(+), 14 deletions(-) + +diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c +index 43eaf54736f4e..462f7f363faab 100644 +--- a/drivers/hv/channel_mgmt.c ++++ b/drivers/hv/channel_mgmt.c +@@ -1228,6 +1228,8 @@ channel_message_table[CHANNELMSG_COUNT] = { + { CHANNELMSG_19, 0, NULL }, + { CHANNELMSG_20, 0, NULL }, + { CHANNELMSG_TL_CONNECT_REQUEST, 0, NULL }, ++ { CHANNELMSG_22, 0, NULL }, ++ { CHANNELMSG_TL_CONNECT_RESULT, 0, NULL }, + }; + + /* +@@ -1239,23 +1241,14 @@ void vmbus_onmessage(void *context) + { + struct hv_message *msg = context; + struct vmbus_channel_message_header *hdr; +- int size; + + hdr = (struct vmbus_channel_message_header *)msg->u.payload; +- size = msg->header.payload_size; + +- if (hdr->msgtype >= CHANNELMSG_COUNT) { +- pr_err("Received invalid channel message type %d size %d\n", +- hdr->msgtype, size); +- print_hex_dump_bytes("", DUMP_PREFIX_NONE, +- (unsigned char *)msg->u.payload, size); +- return; +- } +- +- if (channel_message_table[hdr->msgtype].message_handler) +- channel_message_table[hdr->msgtype].message_handler(hdr); +- else +- pr_err("Unhandled channel message type %d\n", hdr->msgtype); ++ /* ++ * vmbus_on_msg_dpc() makes sure the hdr->msgtype here can not go ++ * out of bound and the message_handler pointer can not be NULL. ++ */ ++ channel_message_table[hdr->msgtype].message_handler(hdr); + } + + /* +diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c +index 1fd812ed679b4..45b8ccdfb0852 100644 +--- a/drivers/hv/vmbus_drv.c ++++ b/drivers/hv/vmbus_drv.c +@@ -890,6 +890,10 @@ void vmbus_on_msg_dpc(unsigned long data) + } + + entry = &channel_message_table[hdr->msgtype]; ++ ++ if (!entry->message_handler) ++ goto msg_handled; ++ + if (entry->handler_type == VMHT_BLOCKING) { + ctx = kmalloc(sizeof(*ctx), GFP_ATOMIC); + if (ctx == NULL) +diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h +index 8d3ca6da33421..63cd81e5610d1 100644 +--- a/include/linux/hyperv.h ++++ b/include/linux/hyperv.h +@@ -422,6 +422,8 @@ enum vmbus_channel_message_type { + CHANNELMSG_19 = 19, + CHANNELMSG_20 = 20, + CHANNELMSG_TL_CONNECT_REQUEST = 21, ++ CHANNELMSG_22 = 22, ++ CHANNELMSG_TL_CONNECT_RESULT = 23, + CHANNELMSG_COUNT + }; + +-- +2.25.1 + diff --git a/queue-4.14/drm-nouveau-fbcon-fix-module-unload-when-fbcon-init-.patch b/queue-4.14/drm-nouveau-fbcon-fix-module-unload-when-fbcon-init-.patch new file mode 100644 index 00000000000..57e13312441 --- /dev/null +++ b/queue-4.14/drm-nouveau-fbcon-fix-module-unload-when-fbcon-init-.patch @@ -0,0 +1,33 @@ +From 1c8e967016163ccf69517caaa7eec0bc88694f93 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 24 Jul 2020 17:01:39 +1000 +Subject: drm/nouveau/fbcon: fix module unload when fbcon init has failed for + some reason + +From: Ben Skeggs + +[ Upstream commit 498595abf5bd51f0ae074cec565d888778ea558f ] + +Stale pointer was tripping up the unload path. + +Signed-off-by: Ben Skeggs +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/nouveau/nouveau_fbcon.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/gpu/drm/nouveau/nouveau_fbcon.c b/drivers/gpu/drm/nouveau/nouveau_fbcon.c +index 2b12d82aac150..ee8f744dc4881 100644 +--- a/drivers/gpu/drm/nouveau/nouveau_fbcon.c ++++ b/drivers/gpu/drm/nouveau/nouveau_fbcon.c +@@ -543,6 +543,7 @@ fini: + drm_fb_helper_fini(&fbcon->helper); + free: + kfree(fbcon); ++ drm->fbcon = NULL; + return ret; + } + +-- +2.25.1 + diff --git a/queue-4.14/drm-nouveau-fbcon-zero-initialise-the-mode_cmd2-stru.patch b/queue-4.14/drm-nouveau-fbcon-zero-initialise-the-mode_cmd2-stru.patch new file mode 100644 index 00000000000..3069087e1c7 --- /dev/null +++ b/queue-4.14/drm-nouveau-fbcon-zero-initialise-the-mode_cmd2-stru.patch @@ -0,0 +1,33 @@ +From 4315ea3c35be6024f055cd8a8bbe8bbec135a649 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 24 Jul 2020 17:02:48 +1000 +Subject: drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure + +From: Ben Skeggs + +[ Upstream commit 15fbc3b938534cc8eaac584a7b0c1183fc968b86 ] + +This is tripping up the format modifier patches. + +Signed-off-by: Ben Skeggs +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/nouveau/nouveau_fbcon.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/gpu/drm/nouveau/nouveau_fbcon.c b/drivers/gpu/drm/nouveau/nouveau_fbcon.c +index ee8f744dc4881..9ffb09679cc4a 100644 +--- a/drivers/gpu/drm/nouveau/nouveau_fbcon.c ++++ b/drivers/gpu/drm/nouveau/nouveau_fbcon.c +@@ -310,7 +310,7 @@ nouveau_fbcon_create(struct drm_fb_helper *helper, + struct nouveau_framebuffer *fb; + struct nouveau_channel *chan; + struct nouveau_bo *nvbo; +- struct drm_mode_fb_cmd2 mode_cmd; ++ struct drm_mode_fb_cmd2 mode_cmd = {}; + int ret; + + mode_cmd.width = sizes->surface_width; +-- +2.25.1 + diff --git a/queue-4.14/i2c-slave-add-sanity-check-when-unregistering.patch b/queue-4.14/i2c-slave-add-sanity-check-when-unregistering.patch new file mode 100644 index 00000000000..321fb3231b4 --- /dev/null +++ b/queue-4.14/i2c-slave-add-sanity-check-when-unregistering.patch @@ -0,0 +1,34 @@ +From f5ca0886dc467dbd25834ea127afb8ad362e1f44 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 25 Jul 2020 21:50:53 +0200 +Subject: i2c: slave: add sanity check when unregistering + +From: Wolfram Sang + +[ Upstream commit 8808981baf96e1b3dea1f08461e4d958aa0dbde1 ] + +Signed-off-by: Wolfram Sang +Reviewed-by: Alain Volmat +Signed-off-by: Wolfram Sang +Signed-off-by: Sasha Levin +--- + drivers/i2c/i2c-core-slave.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/drivers/i2c/i2c-core-slave.c b/drivers/i2c/i2c-core-slave.c +index 21051aba39e3a..d89bc31e06227 100644 +--- a/drivers/i2c/i2c-core-slave.c ++++ b/drivers/i2c/i2c-core-slave.c +@@ -62,6 +62,9 @@ int i2c_slave_unregister(struct i2c_client *client) + { + int ret; + ++ if (IS_ERR_OR_NULL(client)) ++ return -EINVAL; ++ + if (!client->adapter->algo->unreg_slave) { + dev_err(&client->dev, "%s: not supported by adapter\n", __func__); + return -EOPNOTSUPP; +-- +2.25.1 + diff --git a/queue-4.14/i2c-slave-improve-sanity-check-when-registering.patch b/queue-4.14/i2c-slave-improve-sanity-check-when-registering.patch new file mode 100644 index 00000000000..cf435b051b4 --- /dev/null +++ b/queue-4.14/i2c-slave-improve-sanity-check-when-registering.patch @@ -0,0 +1,38 @@ +From 38523724a8915a893662da95e3616b04d1a4841d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 25 Jul 2020 21:50:52 +0200 +Subject: i2c: slave: improve sanity check when registering + +From: Wolfram Sang + +[ Upstream commit 1b1be3bf27b62f5abcf85c6f3214bdb9c7526685 ] + +Add check for ERR_PTR and simplify code while here. + +Signed-off-by: Wolfram Sang +Reviewed-by: Alain Volmat +Signed-off-by: Wolfram Sang +Signed-off-by: Sasha Levin +--- + drivers/i2c/i2c-core-slave.c | 4 +--- + 1 file changed, 1 insertion(+), 3 deletions(-) + +diff --git a/drivers/i2c/i2c-core-slave.c b/drivers/i2c/i2c-core-slave.c +index 4a78c65e99713..21051aba39e3a 100644 +--- a/drivers/i2c/i2c-core-slave.c ++++ b/drivers/i2c/i2c-core-slave.c +@@ -22,10 +22,8 @@ int i2c_slave_register(struct i2c_client *client, i2c_slave_cb_t slave_cb) + { + int ret; + +- if (!client || !slave_cb) { +- WARN(1, "insufficient data\n"); ++ if (WARN(IS_ERR_OR_NULL(client) || !slave_cb, "insufficient data\n")) + return -EINVAL; +- } + + if (!(client->flags & I2C_CLIENT_SLAVE)) + dev_warn(&client->dev, "%s: client slave flag not set. You might see address collisions\n", +-- +2.25.1 + diff --git a/queue-4.14/igb-reinit_locked-should-be-called-with-rtnl_lock.patch b/queue-4.14/igb-reinit_locked-should-be-called-with-rtnl_lock.patch new file mode 100644 index 00000000000..092ce139890 --- /dev/null +++ b/queue-4.14/igb-reinit_locked-should-be-called-with-rtnl_lock.patch @@ -0,0 +1,92 @@ +From 70d12fa978a71be7bbd1a258a6153e0f5cd9b376 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 2 Jul 2020 15:39:06 -0700 +Subject: igb: reinit_locked() should be called with rtnl_lock + +From: Francesco Ruggeri + +[ Upstream commit 024a8168b749db7a4aa40a5fbdfa04bf7e77c1c0 ] + +We observed two panics involving races with igb_reset_task. +The first panic is caused by this race condition: + + kworker reboot -f + + igb_reset_task + igb_reinit_locked + igb_down + napi_synchronize + __igb_shutdown + igb_clear_interrupt_scheme + igb_free_q_vectors + igb_free_q_vector + adapter->q_vector[v_idx] = NULL; + napi_disable + Panics trying to access + adapter->q_vector[v_idx].napi_state + +The second panic (a divide error) is caused by this race: + +kworker reboot -f tx packet + +igb_reset_task + __igb_shutdown + rtnl_lock() + ... + igb_clear_interrupt_scheme + igb_free_q_vectors + adapter->num_tx_queues = 0 + ... + rtnl_unlock() +rtnl_lock() +igb_reinit_locked +igb_down +igb_up +netif_tx_start_all_queues + dev_hard_start_xmit + igb_xmit_frame + igb_tx_queue_mapping + Panics on + r_idx % adapter->num_tx_queues + +This commit applies to igb_reset_task the same changes that +were applied to ixgbe in commit 2f90b8657ec9 ("ixgbe: this patch +adds support for DCB to the kernel and ixgbe driver"), +commit 8f4c5c9fb87a ("ixgbe: reinit_locked() should be called with +rtnl_lock") and commit 88adce4ea8f9 ("ixgbe: fix possible race in +reset subtask"). + +Signed-off-by: Francesco Ruggeri +Tested-by: Aaron Brown +Signed-off-by: Tony Nguyen +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/intel/igb/igb_main.c | 9 +++++++++ + 1 file changed, 9 insertions(+) + +diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c +index 9c7e75b3b6c7a..50fa0401c7014 100644 +--- a/drivers/net/ethernet/intel/igb/igb_main.c ++++ b/drivers/net/ethernet/intel/igb/igb_main.c +@@ -5487,9 +5487,18 @@ static void igb_reset_task(struct work_struct *work) + struct igb_adapter *adapter; + adapter = container_of(work, struct igb_adapter, reset_task); + ++ rtnl_lock(); ++ /* If we're already down or resetting, just bail */ ++ if (test_bit(__IGB_DOWN, &adapter->state) || ++ test_bit(__IGB_RESETTING, &adapter->state)) { ++ rtnl_unlock(); ++ return; ++ } ++ + igb_dump(adapter); + netdev_err(adapter->netdev, "Reset adapter\n"); + igb_reinit_locked(adapter); ++ rtnl_unlock(); + } + + /** +-- +2.25.1 + diff --git a/queue-4.14/net-9p-validate-fds-in-p9_fd_open.patch b/queue-4.14/net-9p-validate-fds-in-p9_fd_open.patch new file mode 100644 index 00000000000..3ce468edab9 --- /dev/null +++ b/queue-4.14/net-9p-validate-fds-in-p9_fd_open.patch @@ -0,0 +1,70 @@ +From 9502bda8c236037021cae59d7c6ed557671a4bbc Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 10 Jul 2020 10:57:22 +0200 +Subject: net/9p: validate fds in p9_fd_open + +From: Christoph Hellwig + +[ Upstream commit a39c46067c845a8a2d7144836e9468b7f072343e ] + +p9_fd_open just fgets file descriptors passed in from userspace, but +doesn't verify that they are valid for read or writing. This gets +cought down in the VFS when actually attempting a read or write, but +a new warning added in linux-next upsets syzcaller. + +Fix this by just verifying the fds early on. + +Link: http://lkml.kernel.org/r/20200710085722.435850-1-hch@lst.de +Reported-by: syzbot+e6f77e16ff68b2434a2c@syzkaller.appspotmail.com +Signed-off-by: Christoph Hellwig +[Dominique: amend goto as per Doug Nazar's review] +Signed-off-by: Dominique Martinet +Signed-off-by: Sasha Levin +--- + net/9p/trans_fd.c | 24 ++++++++++++++++-------- + 1 file changed, 16 insertions(+), 8 deletions(-) + +diff --git a/net/9p/trans_fd.c b/net/9p/trans_fd.c +index 32de8afbfbf8e..9f020559c1928 100644 +--- a/net/9p/trans_fd.c ++++ b/net/9p/trans_fd.c +@@ -829,20 +829,28 @@ static int p9_fd_open(struct p9_client *client, int rfd, int wfd) + return -ENOMEM; + + ts->rd = fget(rfd); ++ if (!ts->rd) ++ goto out_free_ts; ++ if (!(ts->rd->f_mode & FMODE_READ)) ++ goto out_put_rd; + ts->wr = fget(wfd); +- if (!ts->rd || !ts->wr) { +- if (ts->rd) +- fput(ts->rd); +- if (ts->wr) +- fput(ts->wr); +- kfree(ts); +- return -EIO; +- } ++ if (!ts->wr) ++ goto out_put_rd; ++ if (!(ts->wr->f_mode & FMODE_WRITE)) ++ goto out_put_wr; + + client->trans = ts; + client->status = Connected; + + return 0; ++ ++out_put_wr: ++ fput(ts->wr); ++out_put_rd: ++ fput(ts->rd); ++out_free_ts: ++ kfree(ts); ++ return -EIO; + } + + static int p9_socket_open(struct p9_client *client, struct socket *csocket) +-- +2.25.1 + diff --git a/queue-4.14/series b/queue-4.14/series index 913d042baa7..50396f75f14 100644 --- a/queue-4.14/series +++ b/queue-4.14/series @@ -16,3 +16,13 @@ leds-wm831x-status-fix-use-after-free-on-unbind.patch leds-da903x-fix-use-after-free-on-unbind.patch leds-lm3533-fix-use-after-free-on-unbind.patch leds-88pm860x-fix-use-after-free-on-unbind.patch +net-9p-validate-fds-in-p9_fd_open.patch +drm-nouveau-fbcon-fix-module-unload-when-fbcon-init-.patch +drm-nouveau-fbcon-zero-initialise-the-mode_cmd2-stru.patch +i2c-slave-improve-sanity-check-when-registering.patch +i2c-slave-add-sanity-check-when-unregistering.patch +cfg80211-check-vendor-command-doit-pointer-before-us.patch +igb-reinit_locked-should-be-called-with-rtnl_lock.patch +atm-fix-atm_dev-refcnt-leaks-in-atmtcp_remove_persis.patch +tools-lib-traceevent-fix-memory-leak-in-process_dyna.patch +drivers-hv-vmbus-ignore-channelmsg_tl_connect_result.patch diff --git a/queue-4.14/tools-lib-traceevent-fix-memory-leak-in-process_dyna.patch b/queue-4.14/tools-lib-traceevent-fix-memory-leak-in-process_dyna.patch new file mode 100644 index 00000000000..d0bf1566ea2 --- /dev/null +++ b/queue-4.14/tools-lib-traceevent-fix-memory-leak-in-process_dyna.patch @@ -0,0 +1,72 @@ +From 9f934130a2bd2f67806aaecb7ab4467078a3575d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 30 Jul 2020 11:02:36 -0400 +Subject: tools lib traceevent: Fix memory leak in process_dynamic_array_len + +From: Philippe Duplessis-Guindon + +[ Upstream commit e24c6447ccb7b1a01f9bf0aec94939e6450c0b4d ] + +I compiled with AddressSanitizer and I had these memory leaks while I +was using the tep_parse_format function: + + Direct leak of 28 byte(s) in 4 object(s) allocated from: + #0 0x7fb07db49ffe in __interceptor_realloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dffe) + #1 0x7fb07a724228 in extend_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:985 + #2 0x7fb07a724c21 in __read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1140 + #3 0x7fb07a724f78 in read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1206 + #4 0x7fb07a725191 in __read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1291 + #5 0x7fb07a7251df in read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1299 + #6 0x7fb07a72e6c8 in process_dynamic_array_len /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:2849 + #7 0x7fb07a7304b8 in process_function /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3161 + #8 0x7fb07a730900 in process_arg_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3207 + #9 0x7fb07a727c0b in process_arg /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1786 + #10 0x7fb07a731080 in event_read_print_args /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3285 + #11 0x7fb07a731722 in event_read_print /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3369 + #12 0x7fb07a740054 in __tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6335 + #13 0x7fb07a74047a in __parse_event /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6389 + #14 0x7fb07a740536 in tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6431 + #15 0x7fb07a785acf in parse_event ../../../src/fs-src/fs.c:251 + #16 0x7fb07a785ccd in parse_systems ../../../src/fs-src/fs.c:284 + #17 0x7fb07a786fb3 in read_metadata ../../../src/fs-src/fs.c:593 + #18 0x7fb07a78760e in ftrace_fs_source_init ../../../src/fs-src/fs.c:727 + #19 0x7fb07d90c19c in add_component_with_init_method_data ../../../../src/lib/graph/graph.c:1048 + #20 0x7fb07d90c87b in add_source_component_with_initialize_method_data ../../../../src/lib/graph/graph.c:1127 + #21 0x7fb07d90c92a in bt_graph_add_source_component ../../../../src/lib/graph/graph.c:1152 + #22 0x55db11aa632e in cmd_run_ctx_create_components_from_config_components ../../../src/cli/babeltrace2.c:2252 + #23 0x55db11aa6fda in cmd_run_ctx_create_components ../../../src/cli/babeltrace2.c:2347 + #24 0x55db11aa780c in cmd_run ../../../src/cli/babeltrace2.c:2461 + #25 0x55db11aa8a7d in main ../../../src/cli/babeltrace2.c:2673 + #26 0x7fb07d5460b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2) + +The token variable in the process_dynamic_array_len function is +allocated in the read_expect_type function, but is not freed before +calling the read_token function. + +Free the token variable before calling read_token in order to plug the +leak. + +Signed-off-by: Philippe Duplessis-Guindon +Reviewed-by: Steven Rostedt (VMware) +Link: https://lore.kernel.org/linux-trace-devel/20200730150236.5392-1-pduplessis@efficios.com +Signed-off-by: Arnaldo Carvalho de Melo +Signed-off-by: Sasha Levin +--- + tools/lib/traceevent/event-parse.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c +index 8211e8010e09b..d260ca680f074 100644 +--- a/tools/lib/traceevent/event-parse.c ++++ b/tools/lib/traceevent/event-parse.c +@@ -2780,6 +2780,7 @@ process_dynamic_array_len(struct event_format *event, struct print_arg *arg, + if (read_expected(EVENT_DELIM, ")") < 0) + goto out_err; + ++ free_token(token); + type = read_token(&token); + *tok = token; + +-- +2.25.1 +