4.11.10-stable review
Greg Kroah-Hartman
maintainercover 4.11.10-stable review
This is the start of the stable review cycle for the 4.11.10 release. There are 36 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 Jul 12 17:10:29 UTC 2017. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.11.10-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.11.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.11.10-rc1
Yifeng Li <[email protected]>
rt286: add Thinkpad Helix 2 to force_combo_jack_table
Stephan Mueller <[email protected]>
crypto: drbg - Fixes panic in wait_for_completion call
Juergen Gross <[email protected]>
xen: avoid deadlock in xenbus driver
Paolo Abeni <[email protected]>
x86/uaccess: Optimize copy_user_enhanced_fast_string() for short strings
Jarkko Sakkinen <[email protected]>
tpm: fix a kernel memory leak in tpm-sysfs.c
Josh Zimmerman <[email protected]>
tpm: Issue a TPM2_Shutdown for TPM2 devices.
Josh Zimmerman <[email protected]>
Add "shutdown" to "struct class".
Andreas Gruenbacher <[email protected]>
gfs2: Fix glock rhashtable rcu bug
Jiahau Chang <[email protected]>
xhci: Limit USB2 port wake support for AMD Promontory hosts
Bjørn Mork <[email protected]>
USB: serial: qcserial: new Sierra Wireless EM7305 device ID
Johan Hovold <[email protected]>
USB: serial: option: add two Longcheer device ids
Geert Uytterhoeven <[email protected]>
pinctrl: sh-pfc: Update info pointer after SoC-specific init
Sergei Shtylyov <[email protected]>
pinctrl: sh-pfc: r8a7791: Add missing HSCIF1 pinmux data
Uwe Kleine-König <[email protected]>
pinctrl: mxs: atomically switch mux and drive strength config
Tony Lindgren <[email protected]>
pinctrl: core: Fix warning by removing bogus code
Chen-Yu Tsai <[email protected]>
pinctrl: sunxi: Fix SPDIF function name for A83T
Alexandre TORGUE <[email protected]>
pinctrl: stm32: Fix bad function call
Martin Blumenstingl <[email protected]>
pinctrl: meson: meson8b: fix the NAND DQS pins
Geert Uytterhoeven <[email protected]>
pinctrl: sh-pfc: r8a7795: Fix hscif2_clk_b and hscif4_ctrl
Sergei Shtylyov <[email protected]>
pinctrl: sh-pfc: r8a7791: Add missing DVC_MUTE signal
Sergei Shtylyov <[email protected]>
pinctrl: sh-pfc: r8a7791: Fix SCIF2 pinmux data
Sergei Shtylyov <[email protected]>
pinctrl: sh-pfc: r8a7794: Swap ATA signals
Juri Lelli <[email protected]>
arm: remove wrong CONFIG_PROC_SYSCTL ifdef
Johan Hovold <[email protected]>
USB: core: fix device node leak
Benjamin Herrenschmidt <[email protected]>
usb: Fix typo in the definition of Endpoint[out]Request
Michael Grzeschik <[email protected]>
usb: usbip: set buffer pointers to NULL after free
Devin Heitmueller <[email protected]>
Add USB quirk for HVR-950q to avoid intermittent device resets
Jeremie Rapin <[email protected]>
USB: serial: cp210x: add ID for CEL EM3588 USB ZigBee stick
Felipe Balbi <[email protected]>
usb: dwc3: replace %p with %pK
Gerd Hoffmann <[email protected]>
drm/virtio: don't leak bo on drm_gem_object_init failure
Sabrina Dubroca <[email protected]>
tracing/kprobes: Allow to create probe with a module name starting with a digit
Yan, Zheng <[email protected]>
ceph: choose readdir frag based on previous readdir reply
Boris Pismenny <[email protected]>
RDMA/uverbs: Check port number supplied by user verbs cmds
Adrian Salido <[email protected]>
driver core: platform: fix race condition with driver_override
Christoph Hellwig <[email protected]>
fs: completely ignore unknown open flags
Christoph Hellwig <[email protected]>
fs: add a VALID_OPEN_FLAGS
-------------
Diffstat:
Makefile | 4 ++-- arch/arm/kernel/topology.c | 2 -- arch/x86/lib/copy_user_64.S | 7 ++++-- crypto/drbg.c | 1 + drivers/base/core.c | 6 +++++- drivers/base/platform.c | 11 ++++++++-- drivers/char/tpm/tpm-chip.c | 34 ++++++++++++++++++++++++++++++ drivers/char/tpm/tpm-sysfs.c | 6 +++++- drivers/gpu/drm/virtio/virtgpu_object.c | 4 +++- drivers/infiniband/core/uverbs_cmd.c | 8 +++++++ drivers/pinctrl/core.c | 20 +++--------------- drivers/pinctrl/freescale/pinctrl-mxs.c | 16 ++++++++++---- drivers/pinctrl/meson/pinctrl-meson8b.c | 4 ++-- drivers/pinctrl/pinmux.c | 21 ++++-------------- drivers/pinctrl/sh-pfc/core.c | 3 +++ drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 12 +++++++---- drivers/pinctrl/sh-pfc/pfc-r8a7794.c | 16 +++++++------- drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 4 ++-- drivers/pinctrl/stm32/pinctrl-stm32.c | 2 +- drivers/pinctrl/sunxi/pinctrl-sun8i-a83t.c | 2 +- drivers/usb/core/quirks.c | 4 ++++ drivers/usb/core/usb.c | 2 ++ drivers/usb/dwc3/dwc3-st.c | 2 +- drivers/usb/dwc3/gadget.c | 9 +++----- drivers/usb/host/xhci-hub.c | 3 +++ drivers/usb/host/xhci-pci.c | 12 +++++++++++ drivers/usb/host/xhci.h | 1 + drivers/usb/serial/cp210x.c | 1 + drivers/usb/serial/option.c | 4 ++++ drivers/usb/serial/qcserial.c | 1 + drivers/usb/usbip/stub_main.c | 4 ++++ drivers/usb/usbip/stub_tx.c | 4 ++++ drivers/xen/xenbus/xenbus_comms.c | 21 +++++++++--------- fs/ceph/dir.c | 19 +++++++++++------ fs/fcntl.c | 14 ++++-------- fs/gfs2/glock.c | 11 ++++++++-- fs/gfs2/incore.h | 1 + fs/open.c | 6 ++++++ include/linux/device.h | 2 ++ include/linux/fcntl.h | 6 ++++++ include/linux/usb/hcd.h | 4 ++-- kernel/trace/trace_kprobe.c | 21 +++++++----------- sound/soc/codecs/rt286.c | 7 ++++++ 43 files changed, 223 insertions(+), 119 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/36 fs: add a VALID_OPEN_FLAGS
4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Hellwig <[email protected]>
commit 80f18379a7c350c011d30332658aa15fe49a8fa5 upstream.
Add a central define for all valid open flags, and use it in the uniqueness check.
--- fs/fcntl.c | 14 ++++---------- include/linux/fcntl.h | 6 ++++++ 2 files changed, 10 insertions(+), 10 deletions(-)
fs/fcntl.c +4 -10
@@ -742,16 +742,10 @@ static int __init fcntl_init(void)* Exceptions: O_NONBLOCK is a two bit define on parisc; O_NDELAY * is defined as O_NONBLOCK on some platforms and not on others. */ -BUILD_BUG_ON (21 -1 /* for O_RDONLY being 0 */ !=HWEIGHT32 ( -O_RDONLY |O_WRONLY |O_RDWR | -O_CREAT |O_EXCL |O_NOCTTY | -O_TRUNC |O_APPEND |/* O_NONBLOCK | */ - __O_SYNC |O_DSYNC |FASYNC | -O_DIRECT |O_LARGEFILE |O_DIRECTORY | -O_NOFOLLOW |O_NOATIME |O_CLOEXEC | - __FMODE_EXEC |O_PATH | __O_TMPFILE | - __FMODE_NONOTIFY - )); +BUILD_BUG_ON (21 -1 /* for O_RDONLY being 0 */ != +HWEIGHT32 ( + (VALID_OPEN_FLAGS & ~(O_NONBLOCK |O_NDELAY )) | + __FMODE_EXEC | __FMODE_NONOTIFY)); fasync_cache =kmem_cache_create ("fasync_cache" ,sizeof (struct fasync_struct ),0 ,SLAB_PANIC ,NULL );
include/linux/fcntl.h +6 -0
@@ -3,6 +3,12 @@#include <uapi/linux/fcntl.h> +/* list of all valid flags for the open/openat flags argument: */ +#define VALID_OPEN_FLAGS \ + (O_RDONLY | O_WRONLY | O_RDWR | O_CREAT | O_EXCL | O_NOCTTY | O_TRUNC | \ + O_APPEND | O_NDELAY | O_NONBLOCK | O_NDELAY | __O_SYNC | O_DSYNC | \ + FASYNC | O_DIRECT | O_LARGEFILE | O_DIRECTORY | O_NOFOLLOW | \ + O_NOATIME | O_CLOEXEC | O_PATH | __O_TMPFILE)#ifndef force_o_largefile#define force_o_largefile () (BITS_PER_LONG != 32)
Greg Kroah-Hartman
maintainerPATCH 2/36 fs: completely ignore unknown open flags
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Hellwig <[email protected]>
commit 629e014bb8349fcf7c1e4df19a842652ece1c945 upstream.
Currently we just stash anything we got into file->f_flags, and the report it in fcntl(F_GETFD). This patch just clears out all unknown flags so that we don't pass them to the fs or report them.
--- fs/open.c | 6 ++++++ 1 file changed, 6 insertions(+)
fs/open.c +6 -0
@@ -900,6 +900,12 @@ static inline int build_open_flags(int fint lookup_flags =0 ;int acc_mode =ACC_MODE (flags); +/* +* Clear out all open flags we don't know about so that we don't report +* them in fcntl(F_GETFD) or similar interfaces. +*/ + flags &=VALID_OPEN_FLAGS ; +if (flags & (O_CREAT | __O_TMPFILE)) op->mode = (mode &S_IALLUGO ) |S_IFREG ;else
Greg Kroah-Hartman
maintainerPATCH 3/36 driver core: platform: fix race condition with driver_override
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Salido <[email protected]>
commit 6265539776a0810b7ce6398c27866ddb9c6bd154 upstream.
The driver_override implementation is susceptible to race condition when different threads are reading vs storing a different driver override. Add locking to avoid race condition.
--- drivers/base/platform.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
drivers/base/platform.c +9 -2
@@ -866,7 +866,7 @@ static ssize_t driver_override_store(str const char *buf, size_t count) {struct platform_device *pdev =to_platform_device (dev); -char *driver_override, *old = pdev->driver_override, *cp; +char *driver_override, *old, *cp;if (count >PATH_MAX )return -EINVAL ;
@@ -879,12 +879,15 @@ static ssize_t driver_override_store(strif (cp) *cp ='\0' ; +device_lock (dev); + old = pdev->driver_override;if (strlen (driver_override)) { pdev->driver_override = driver_override; }else {kfree (driver_override); pdev->driver_override =NULL ; } +device_unlock (dev);kfree (old);
@@ -895,8 +898,12 @@ static ssize_t driver_override_show(stru struct device_attribute *attr, char *buf) { struct platform_device *pdev = to_platform_device(dev); +ssize_t len; -return sprintf (buf,"%s\n" , pdev->driver_override); +device_lock (dev); + len =sprintf (buf,"%s\n" , pdev->driver_override); +device_unlock (dev); +return len; }static DEVICE_ATTR_RW (driver_override);
Greg Kroah-Hartman
maintainerPATCH 4/36 RDMA/uverbs: Check port number supplied by user verbs cmds
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Boris Pismenny <[email protected]>
commit 5ecce4c9b17bed4dc9cb58bfb10447307569b77b upstream.
The ib_uverbs_create_ah() ind ib_uverbs_modify_qp() calls receive the port number from user input as part of its attributes and assumes it is valid. Down on the stack, that parameter is used to access kernel data structures. If the value is invalid, the kernel accesses memory it should not. To prevent this, verify the port number before using it.
BUG: KASAN: use-after-free in ib_uverbs_create_ah+0x6d5/0x7b0 Read of size 4 at addr ffff880018d67ab8 by task syz-executor/313 BUG: KASAN: slab-out-of-bounds in modify_qp.isra.4+0x19d0/0x1ef0 Read of size 4 at addr ffff88006c40ec58 by task syz-executor/819
--- drivers/infiniband/core/uverbs_cmd.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/infiniband/core/uverbs_cmd.c +8 -0
@@ -2404,6 +2404,11 @@ static int modify_qp(struct ib_uverbs_fi goto out; } +if (!rdma_is_port_valid (qp->device, cmd->base.port_num)) { + ret = -EINVAL ; + goto release_qp; + } + attr->qp_state = cmd->base.qp_state; attr->cur_qp_state = cmd->base.cur_qp_state; attr->path_mtu = cmd->base.path_mtu;
@@ -3000,6 +3005,9 @@ ssize_t ib_uverbs_create_ah(struct ib_uvif (copy_from_user (&cmd, buf,sizeof cmd))return -EFAULT ; +if (!rdma_is_port_valid (ib_dev, cmd.attr.port_num)) +return -EINVAL ; +INIT_UDATA (&udata, buf +sizeof (cmd), (unsigned long )cmd.response +sizeof (resp), in_len -sizeof (cmd), out_len -sizeof (resp));
Greg Kroah-Hartman
maintainerPATCH 5/36 ceph: choose readdir frag based on previous readdir reply
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yan, Zheng <[email protected]>
commit b50c2de51e611da90cf3cf04c058f7e9bbe79e93 upstream.
The dirfragtree is lazily updated, it's not always accurate. Infinite loops happens in following circumstance.
- client send request to read frag A
- frag A has been fragmented into frag B and C. So mds fills the reply with contents of frag B
- client wants to read next frag C. ceph_choose_frag(frag value of C) return frag A.
The fix is using previous readdir reply to calculate next readdir frag when possible.
--- fs/ceph/dir.c | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-)
fs/ceph/dir.c +12 -7
@@ -294,7 +294,7 @@ static int ceph_readdir(struct file *filstruct ceph_mds_client *mdsc = fsc->mdsc;int i;int err; -u32 ftype; +unsigned frag =-1 ;struct ceph_mds_reply_info_parsed *rinfo;dout ("readdir %p file %p pos %llx\n" , inode, file, ctx->pos);
@@ -341,7 +341,6 @@ more:/* do we have the correct frag content buffered? */ if (need_send_readdir (fi, ctx->pos)) {struct ceph_mds_request *req; -unsigned frag;int op =ceph_snap (inode) ==CEPH_SNAPDIR ?CEPH_MDS_OP_LSSNAP :CEPH_MDS_OP_READDIR ;
@@ -352,8 +351,11 @@ more: }if (is_hash_order (ctx->pos)) { - frag =ceph_choose_frag (ci,fpos_hash (ctx->pos), -NULL ,NULL ); +/* fragtree isn't always accurate. choose frag +* based on previous reply when possible. */ +if (frag == (unsigned )-1 ) + frag =ceph_choose_frag (ci,fpos_hash (ctx->pos), +NULL ,NULL ); }else { frag =fpos_frag (ctx->pos); }
@@ -476,6 +478,7 @@ more:struct ceph_mds_reply_dir_entry *rde = rinfo->dir_entries + i;struct ceph_vino vino;ino_t ino; +u32 ftype;BUG_ON (rde->offset < ctx->pos);
@@ -498,15 +501,17 @@ more: ctx->pos++; } +ceph_mdsc_put_request (fi->last_readdir); + fi->last_readdir =NULL ; +if (fi->next_offset >2 ) { -ceph_mdsc_put_request (fi->last_readdir); - fi->last_readdir =NULL ; + frag = fi->frag; goto more; }/* more frags? */ if (!ceph_frag_is_rightmost (fi->frag)) { -unsigned frag =ceph_frag_next (fi->frag); + frag =ceph_frag_next (fi->frag);if (is_hash_order (ctx->pos)) {loff_t new_pos =ceph_make_fpos (ceph_frag_value (frag), fi->next_offset, true);
Greg Kroah-Hartman
maintainerPATCH 6/36 tracing/kprobes: Allow to create probe with a module name starting with a digit
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sabrina Dubroca <[email protected]>
commit 9e52b32567126fe146f198971364f68d3bc5233f upstream.
Always try to parse an address, since kstrtoul() will safely fail when given a symbol as input. If that fails (which will be the case for a symbol), try to parse a symbol instead.
This allows creating a probe such as:
p:probe/vlan_gro_receive 8021q:vlan_gro_receive+0
Which is necessary for this command to work:
perf probe -m 8021q -a vlan_gro_receive
--- kernel/trace/trace_kprobe.c | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-)
kernel/trace/trace_kprobe.c +8 -13
@@ -680,30 +680,25 @@ static int create_trace_kprobe(int argc,pr_info ("Probe point is not specified.\n" );return -EINVAL ; } -if (isdigit (argv[1 ][0 ])) { -if (is_return) { -pr_info ("Return probe point must be a symbol.\n" ); -return -EINVAL ; - } -/* an address specified */ - ret =kstrtoul (&argv[1 ][0 ],0 , (unsigned long *)&addr); -if (ret) { -pr_info ("Failed to parse address.\n" ); -return ret; - } - }else { + +/* try to parse an address. if that fails, try to read the +* input as a symbol. */ +if (kstrtoul (argv[1 ],0 , (unsigned long *)&addr)) {/* a symbol specified */ symbol = argv[1 ];/* TODO: support .init module functions */ ret =traceprobe_split_symbol_offset (symbol, &offset);if (ret) { -pr_info ("Failed to parse symbol.\n" ); +pr_info ("Failed to parse either an address or a symbol.\n" );return ret; }if (offset && is_return) {pr_info ("Return probe must be used without offset.\n" );return -EINVAL ; } + }else if (is_return) { +pr_info ("Return probe point must be a symbol.\n" ); +return -EINVAL ; } argc -=2 ; argv +=2 ;
Greg Kroah-Hartman
maintainerPATCH 8/36 usb: dwc3: replace %p with %pK
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
commit 04fb365c453e14ff9e8a28f1c46050d920a27a4a upstream.
%p will leak kernel pointers, so let's not expose the information on dmesg and instead use %pK. %pK will only show the actual addresses if explicitly enabled under /proc/sys/kernel/kptr_restrict.
--- drivers/usb/dwc3/dwc3-st.c | 2 +- drivers/usb/dwc3/gadget.c | 9 +++------ 2 files changed, 4 insertions(+), 7 deletions(-)
drivers/usb/dwc3/dwc3-st.c +1 -1
@@ -230,7 +230,7 @@ static int st_dwc3_probe(struct platform dwc3_data->syscfg_reg_off = res->start; -dev_vdbg (&pdev->dev,"glue-logic addr 0x%p, syscfg-reg offset 0x%x\n" , +dev_vdbg (&pdev->dev,"glue-logic addr 0x%pK, syscfg-reg offset 0x%x\n" , dwc3_data->glue_base, dwc3_data->syscfg_reg_off); dwc3_data->rstc_pwrdn =
drivers/usb/dwc3/gadget.c +3 -6
@@ -1212,12 +1212,9 @@ static int __dwc3_gadget_ep_queue(structreturn -ESHUTDOWN ; } -if (WARN (req->dep != dep,"request %p belongs to '%s'\n" , - &req->request, req->dep->name)) { -dev_err (dwc->dev,"%s: request %p belongs to '%s'\n" , - dep->name, &req->request, req->dep->name); +if (WARN (req->dep != dep,"request %pK belongs to '%s'\n" , + &req->request, req->dep->name))return -EINVAL ; - }pm_runtime_get (dwc->dev);
@@ -1429,7 +1426,7 @@ static int dwc3_gadget_ep_dequeue(struct } goto out1; } -dev_err (dwc->dev,"request %p was not queued to %s\n" , +dev_err (dwc->dev,"request %pK was not queued to %s\n" , request, ep->name); ret = -EINVAL ; goto out0;
Greg Kroah-Hartman
maintainerPATCH 9/36 USB: serial: cp210x: add ID for CEL EM3588 USB ZigBee stick
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jeremie Rapin <[email protected]>
commit fd90f73a9925f248d696bde1cfc836d9fda5570d upstream.
Added the USB serial device ID for the CEL ZigBee EM3588 radio stick.
--- drivers/usb/serial/cp210x.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/cp210x.c +1 -0
@@ -141,6 +141,7 @@ static const struct usb_device_id id_tab { USB_DEVICE(0x10C4, 0x8977) }, /* CEL MeshWorks DevKit Device */ { USB_DEVICE(0x10C4, 0x8998) }, /* KCF Technologies PRN */ { USB_DEVICE(0x10C4, 0x8A2A) }, /* HubZ dual ZigBee and Z-Wave dongle */ + { USB_DEVICE(0x10C4, 0x8A5E) }, /* CEL EM3588 ZigBee USB Stick Long Range */ { USB_DEVICE(0x10C4, 0xEA60) }, /* Silicon Labs factory default */ { USB_DEVICE(0x10C4, 0xEA61) }, /* Silicon Labs factory default */ { USB_DEVICE(0x10C4, 0xEA70) }, /* Silicon Labs factory default */
Greg Kroah-Hartman
maintainerPATCH 10/36 Add USB quirk for HVR-950q to avoid intermittent device resets
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Devin Heitmueller <[email protected]>
commit 6836796de4019944f4ba4c99a360e8250fd2e735 upstream.
The USB core and sysfs will attempt to enumerate certain parameters which are unsupported by the au0828 - causing inconsistent behavior and sometimes causing the chip to reset. Avoid making these calls.
This problem manifested as intermittent cases where the au8522 would be reset on analog video startup, in particular when starting up ALSA audio streaming in parallel - the sysfs entries created by snd-usb-audio on streaming startup would result in unsupported control messages being sent during tuning which would put the chip into an unknown state.
--- drivers/usb/core/quirks.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/core/quirks.c +4 -0
@@ -223,6 +223,10 @@ static const struct usb_device_id usb_qu/* Blackmagic Design UltraStudio SDI */ { USB_DEVICE(0x1edb, 0xbd4f), .driver_info = USB_QUIRK_NO_LPM }, + /* Hauppauge HVR-950q */ + { USB_DEVICE(0x2040, 0x7200), .driver_info = + USB_QUIRK_CONFIG_INTF_STRINGS }, + /* INTEL VALUE SSD */ { USB_DEVICE(0x8086, 0xf1a5), .driver_info = USB_QUIRK_RESET_RESUME },
Greg Kroah-Hartman
maintainerPATCH 11/36 usb: usbip: set buffer pointers to NULL after free
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michael Grzeschik <[email protected]>
commit b3b51417d0af63fb9a06662dc292200aed9ea53f upstream.
The usbip stack dynamically allocates the transfer_buffer and setup_packet of each urb that got generated by the tcp to usb stub code. As these pointers are always used only once we will set them to NULL after use. This is done likewise to the free_urb code in vudc_dev.c. This patch fixes double kfree situations where the usbip remote side added the URB_FREE_BUFFER.
--- drivers/usb/usbip/stub_main.c | 4 ++++ drivers/usb/usbip/stub_tx.c | 4 ++++ 2 files changed, 8 insertions(+)
drivers/usb/usbip/stub_main.c +4 -0
@@ -262,7 +262,11 @@ void stub_device_cleanup_urbs(struct stukmem_cache_free (stub_priv_cache, priv);kfree (urb->transfer_buffer); + urb->transfer_buffer =NULL ; +kfree (urb->setup_packet); + urb->setup_packet =NULL ; +usb_free_urb (urb); } }
drivers/usb/usbip/stub_tx.c +4 -0
@@ -28,7 +28,11 @@ static void stub_free_priv_and_urb(strucstruct urb *urb = priv->urb;kfree (urb->setup_packet); + urb->setup_packet =NULL ; +kfree (urb->transfer_buffer); + urb->transfer_buffer =NULL ; +list_del (&priv->list);kmem_cache_free (stub_priv_cache, priv);usb_free_urb (urb);
Greg Kroah-Hartman
maintainerPATCH 12/36 usb: Fix typo in the definition of Endpoint[out]Request
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Benjamin Herrenschmidt <[email protected]>
commit 7cf916bd639bd26db7214f2205bccdb4b9306256 upstream.
The current definition is wrong. This breaks my upcoming Aspeed virtual hub driver.
--- include/linux/usb/hcd.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
include/linux/usb/hcd.h +2 -2
@@ -561,9 +561,9 @@ extern void usb_ep0_reinit(struct usb_de ((USB_DIR_IN|USB_TYPE_STANDARD|USB_RECIP_INTERFACE)<<8)#define EndpointRequest \ - ((USB_DIR_IN|USB_TYPE_STANDARD|USB_RECIP_INTERFACE)<<8) + ((USB_DIR_IN|USB_TYPE_STANDARD|USB_RECIP_ENDPOINT)<<8)#define EndpointOutRequest \ - ((USB_DIR_OUT|USB_TYPE_STANDARD|USB_RECIP_INTERFACE)<<8) + ((USB_DIR_OUT|USB_TYPE_STANDARD|USB_RECIP_ENDPOINT)<<8)/* class requests from the USB 2.0 hub spec, table 11-15 */ #define HUB_CLASS_REQ (dir, type, request) ((((dir) | (type)) << 8) | (request))
Greg Kroah-Hartman
maintainerPATCH 13/36 USB: core: fix device node leak
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
commit e271b2c909a22a2c13b2d5f77f2ce0091b74540c upstream.
Make sure to release any OF device-node reference taken when creating the USB device.
Note that we currently do not hold a reference to the root hub device-tree node (i.e. the parent controller node).
--- drivers/usb/core/usb.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/core/usb.c +2 -0
@@ -282,6 +282,8 @@ static void usb_release_dev(struct devicusb_destroy_configuration (udev);usb_release_bos_descriptor (udev); +if (udev->parent) +of_node_put (dev->of_node);usb_put_hcd (hcd);kfree (udev->product);kfree (udev->manufacturer);
Greg Kroah-Hartman
maintainerPATCH 14/36 arm: remove wrong CONFIG_PROC_SYSCTL ifdef
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Juri Lelli <[email protected]>
commit f70b281b59a871545362a494d99a644153fbbaac upstream.
The sysfs cpu_capacity entry for each CPU has nothing to do with PROC_FS, nor it's in /proc/sys path.
Remove such ifdef.
--- arch/arm/kernel/topology.c | 2 -- 1 file changed, 2 deletions(-)
arch/arm/kernel/topology.c +0 -2
@@ -57,7 +57,6 @@ static void set_capacity_scale(unsignedper_cpu (cpu_scale, cpu) = capacity; } -#ifdef CONFIG_PROC_SYSCTL static ssize_t cpu_capacity_show (struct device *dev,struct device_attribute *attr,char *buf)
@@ -114,7 +113,6 @@ static int register_cpu_capacity_sysctl(return 0 ; }subsys_initcall (register_cpu_capacity_sysctl); -#endif #ifdef CONFIG_OF struct cpu_efficiency {
Greg Kroah-Hartman
maintainerPATCH 15/36 pinctrl: sh-pfc: r8a7794: Swap ATA signals
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sergei Shtylyov <[email protected]>
commit 5f4c8cafe1148f8a91287072815df8f0b66f0e5c upstream.
All R8A7794 manuals I have here (0.50 and 1.10) agree that the PFC driver has ATAG0# and ATAWR0# signals in IPSR12 swapped -- fix this.
--- drivers/pinctrl/sh-pfc/pfc-r8a7794.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/pinctrl/sh-pfc/pfc-r8a7794.c +8 -8
@@ -281,8 +281,8 @@ enum {FN_AVB_AVTP_CAPTURE ,FN_ETH_CRS_DV_B ,FN_SSI_WS1 ,FN_SCIF1_TXD_B ,FN_IIC1_SDA_C ,FN_VI1_DATA0 ,FN_CAN0_TX_D ,FN_AVB_AVTP_MATCH ,FN_ETH_RX_ER_B ,FN_SSI_SDATA1 ,FN_HSCIF1_HRX_B ,FN_SDATA ,FN_VI1_DATA1 , -FN_ATAG0_N ,FN_ETH_RXD0_B ,FN_SSI_SCK2 ,FN_HSCIF1_HTX_B ,FN_VI1_DATA2 , -FN_MDATA ,FN_ATAWR0_N ,FN_ETH_RXD1_B , +FN_ATAWR0_N ,FN_ETH_RXD0_B ,FN_SSI_SCK2 ,FN_HSCIF1_HTX_B ,FN_VI1_DATA2 , +FN_MDATA ,FN_ATAG0_N ,FN_ETH_RXD1_B ,/* IPSR13 */ FN_SSI_WS2, FN_HSCIF1_HCTS_N_B, FN_SCIFA0_RXD_D, FN_VI1_DATA3, FN_SCKZ,
@@ -575,8 +575,8 @@ enum {ETH_CRS_DV_B_MARK ,SSI_WS1_MARK ,SCIF1_TXD_B_MARK ,IIC1_SDA_C_MARK ,VI1_DATA0_MARK ,CAN0_TX_D_MARK ,AVB_AVTP_MATCH_MARK ,ETH_RX_ER_B_MARK ,SSI_SDATA1_MARK ,HSCIF1_HRX_B_MARK ,VI1_DATA1_MARK ,SDATA_MARK , -ATAG0_N_MARK ,ETH_RXD0_B_MARK ,SSI_SCK2_MARK ,HSCIF1_HTX_B_MARK , -VI1_DATA2_MARK ,MDATA_MARK ,ATAWR0_N_MARK ,ETH_RXD1_B_MARK , +ATAWR0_N_MARK ,ETH_RXD0_B_MARK ,SSI_SCK2_MARK ,HSCIF1_HTX_B_MARK , +VI1_DATA2_MARK ,MDATA_MARK ,ATAG0_N_MARK ,ETH_RXD1_B_MARK ,/* IPSR13 */ SSI_WS2_MARK, HSCIF1_HCTS_N_B_MARK, SCIFA0_RXD_D_MARK, VI1_DATA3_MARK,
@@ -1413,13 +1413,13 @@ static const u16 pinmux_data[] = {PINMUX_IPSR_MSEL (IP12_26_24 ,HSCIF1_HRX_B ,SEL_HSCIF1_1 ),PINMUX_IPSR_GPSR (IP12_26_24 ,VI1_DATA1 ),PINMUX_IPSR_MSEL (IP12_26_24 ,SDATA ,SEL_FSN_0 ), -PINMUX_IPSR_GPSR (IP12_26_24 ,ATAG0_N ), +PINMUX_IPSR_GPSR (IP12_26_24 ,ATAWR0_N ),PINMUX_IPSR_MSEL (IP12_26_24 ,ETH_RXD0_B ,SEL_ETH_1 ),PINMUX_IPSR_MSEL (IP12_29_27 ,SSI_SCK2 ,SEL_SSI2_0 ),PINMUX_IPSR_MSEL (IP12_29_27 ,HSCIF1_HTX_B ,SEL_HSCIF1_1 ),PINMUX_IPSR_GPSR (IP12_29_27 ,VI1_DATA2 ),PINMUX_IPSR_MSEL (IP12_29_27 ,MDATA ,SEL_FSN_0 ), -PINMUX_IPSR_GPSR (IP12_29_27 ,ATAWR0_N ), +PINMUX_IPSR_GPSR (IP12_29_27 ,ATAG0_N ),PINMUX_IPSR_MSEL (IP12_29_27 ,ETH_RXD1_B ,SEL_ETH_1 ), /* IPSR13 */
@@ -4938,10 +4938,10 @@ static const struct pinmux_cfg_reg pinmu0 ,0 ,0 ,0 ,/* IP12_29_27 [3] */ FN_SSI_SCK2 ,FN_HSCIF1_HTX_B ,FN_VI1_DATA2 ,FN_MDATA , -FN_ATAWR0_N ,FN_ETH_RXD1_B ,0 ,0 , +FN_ATAG0_N ,FN_ETH_RXD1_B ,0 ,0 ,/* IP12_26_24 [3] */ FN_SSI_SDATA1 ,FN_HSCIF1_HRX_B ,FN_VI1_DATA1 ,FN_SDATA , -FN_ATAG0_N ,FN_ETH_RXD0_B ,0 ,0 , +FN_ATAWR0_N ,FN_ETH_RXD0_B ,0 ,0 ,/* IP12_23_21 [3] */ FN_SSI_WS1 ,FN_SCIF1_TXD_B ,FN_IIC1_SDA_C ,FN_VI1_DATA0 , FN_CAN0_TX_D, FN_AVB_AVTP_MATCH, FN_ETH_RX_ER_B, 0,
Greg Kroah-Hartman
maintainerPATCH 16/36 pinctrl: sh-pfc: r8a7791: Fix SCIF2 pinmux data
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sergei Shtylyov <[email protected]>
commit 58439280f84e6b39fd7d61f25ab30489c1aaf0a9 upstream.
PINMUX_IPSR_MSEL() macro invocation for the TX2 signal has apparently wrong 1st argument -- most probably a result of cut&paste programming...
--- drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/sh-pfc/pfc-r8a7791.c +1 -1
@@ -1099,7 +1099,7 @@ static const u16 pinmux_data[] = {PINMUX_IPSR_MSEL (IP6_5_3 ,FMIN_E ,SEL_FM_4 ),PINMUX_IPSR_GPSR (IP6_7_6 ,AUDIO_CLKOUT ),PINMUX_IPSR_MSEL (IP6_7_6 ,MSIOF1_SS1_B ,SEL_SOF1_1 ), -PINMUX_IPSR_MSEL (IP6_5_3 ,TX2 ,SEL_SCIF2_0 ), +PINMUX_IPSR_MSEL (IP6_7_6 ,TX2 ,SEL_SCIF2_0 ),PINMUX_IPSR_MSEL (IP6_7_6 ,SCIFA2_TXD ,SEL_SCIFA2_0 ),PINMUX_IPSR_GPSR (IP6_9_8 ,IRQ0 ), PINMUX_IPSR_MSEL(IP6_9_8, SCIFB1_RXD_D, SEL_SCIFB1_3),
Greg Kroah-Hartman
maintainerPATCH 17/36 pinctrl: sh-pfc: r8a7791: Add missing DVC_MUTE signal
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sergei Shtylyov <[email protected]>
commit 3908632fb829d73317c64c3d04f584b49f62e4ae upstream.
The R8A7791 PFC driver was apparently based on the preliminary revisions of the user's manual, which omitted the DVC_MUTE signal altogether in the PFC section. The modern manual has the signal described, so just add the necassary data to the driver...
--- drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/pinctrl/sh-pfc/pfc-r8a7791.c +4 -3
@@ -203,7 +203,7 @@ enum {/* IPSR6 */ FN_AUDIO_CLKB ,FN_STP_OPWM_0_B ,FN_MSIOF1_SCK_B , -FN_SCIF_CLK ,FN_BPFCLK_E , +FN_SCIF_CLK ,FN_DVC_MUTE ,FN_BPFCLK_E ,FN_AUDIO_CLKC ,FN_SCIFB0_SCK_C ,FN_MSIOF1_SYNC_B ,FN_RX2 ,FN_SCIFA2_RXD ,FN_FMIN_E , FN_AUDIO_CLKOUT, FN_MSIOF1_SS1_B, FN_TX2, FN_SCIFA2_TXD,
@@ -573,7 +573,7 @@ enum {/* IPSR6 */ AUDIO_CLKB_MARK ,STP_OPWM_0_B_MARK ,MSIOF1_SCK_B_MARK , -SCIF_CLK_MARK ,BPFCLK_E_MARK , +SCIF_CLK_MARK ,DVC_MUTE_MARK ,BPFCLK_E_MARK ,AUDIO_CLKC_MARK ,SCIFB0_SCK_C_MARK ,MSIOF1_SYNC_B_MARK ,RX2_MARK ,SCIFA2_RXD_MARK ,FMIN_E_MARK , AUDIO_CLKOUT_MARK, MSIOF1_SS1_B_MARK, TX2_MARK, SCIFA2_TXD_MARK,
@@ -1090,6 +1090,7 @@ static const u16 pinmux_data[] = {PINMUX_IPSR_MSEL (IP6_2_0 ,STP_OPWM_0_B ,SEL_SSP_1 ),PINMUX_IPSR_MSEL (IP6_2_0 ,MSIOF1_SCK_B ,SEL_SOF1_1 ),PINMUX_IPSR_MSEL (IP6_2_0 ,SCIF_CLK ,SEL_SCIF_0 ), +PINMUX_IPSR_GPSR (IP6_2_0 ,DVC_MUTE ),PINMUX_IPSR_MSEL (IP6_2_0 ,BPFCLK_E ,SEL_FM_4 ),PINMUX_IPSR_GPSR (IP6_5_3 ,AUDIO_CLKC ), PINMUX_IPSR_MSEL(IP6_5_3, SCIFB0_SCK_C, SEL_SCIFB_2),
@@ -5896,7 +5897,7 @@ static const struct pinmux_cfg_reg pinmu0 ,0 ,/* IP6_2_0 [3] */ FN_AUDIO_CLKB ,FN_STP_OPWM_0_B ,FN_MSIOF1_SCK_B , -FN_SCIF_CLK ,0 ,FN_BPFCLK_E , +FN_SCIF_CLK ,FN_DVC_MUTE ,FN_BPFCLK_E , 0, 0, } }, { PINMUX_CFG_REG_VAR("IPSR7", 0xE606003C, 32,
Greg Kroah-Hartman
maintainerPATCH 18/36 pinctrl: sh-pfc: r8a7795: Fix hscif2_clk_b and hscif4_ctrl
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Geert Uytterhoeven <[email protected]>
commit 4324b6084f45b9faebda8d6563d8625d22b4b5df upstream.
Fix typos in hscif2_clk_b_mux[] and hscif4_ctrl_mux[].
--- drivers/pinctrl/sh-pfc/pfc-r8a7795.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/pinctrl/sh-pfc/pfc-r8a7795.c +2 -2
@@ -2167,7 +2167,7 @@ static const unsigned int hscif2_clk_b_p RCAR_GP_PIN(6, 21), };static const unsigned int hscif2_clk_b_mux[] = { -HSCK1_B_MARK , +HSCK2_B_MARK , };static const unsigned int hscif2_ctrl_b_pins[] = {/* RTS, CTS */
@@ -2240,7 +2240,7 @@ static const unsigned int hscif4_ctrl_pi RCAR_GP_PIN(1, 15), RCAR_GP_PIN(1, 14), };static const unsigned int hscif4_ctrl_mux[] = { -HRTS4_N_MARK ,HCTS3_N_MARK , +HRTS4_N_MARK ,HCTS4_N_MARK , };static const unsigned int hscif4_data_b_pins[] = {
Greg Kroah-Hartman
maintainerPATCH 19/36 pinctrl: meson: meson8b: fix the NAND DQS pins
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Martin Blumenstingl <[email protected]>
commit 97ba26b8a9343008504d4e3a87d212bc07b05212 upstream.
The nand_groups table uses different names for the NAND DQS pins than the GROUP() definition in meson8b_cbus_groups (nand_dqs_0 vs nand_dqs0). This prevents using the NAND DQS pins in the devicetree.
Fix this by ensuring that the GROUP() definition and the meson8b_cbus_groups use the same name for these pins.
--- drivers/pinctrl/meson/pinctrl-meson8b.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/pinctrl/meson/pinctrl-meson8b.c +2 -2
@@ -739,8 +739,8 @@ static const char * const sdxc_c_groups[static const char *const nand_groups[] = {"nand_io" ,"nand_io_ce0" ,"nand_io_ce1" ,"nand_io_rb0" ,"nand_ale" ,"nand_cle" , -"nand_wen_clk" ,"nand_ren_clk" ,"nand_dqs0" , -"nand_dqs1" +"nand_wen_clk" ,"nand_ren_clk" ,"nand_dqs_0" , +"nand_dqs_1" };static const char *const nor_groups[] = {
Greg Kroah-Hartman
maintainerPATCH 20/36 pinctrl: stm32: Fix bad function call
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexandre TORGUE <[email protected]>
commit b7c747d4627462f25b3daabf49c18895a6722faa upstream.
In stm32_pconf_parse_conf function, stm32_pmx_gpio_set_direction is called with wrong parameter value. Indeed, using NULL value for range will raise an oops.
--- drivers/pinctrl/stm32/pinctrl-stm32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/stm32/pinctrl-stm32.c +1 -1
@@ -786,7 +786,7 @@ static int stm32_pconf_parse_conf(structbreak ;case PIN_CONFIG_OUTPUT :__stm32_gpio_set (bank, offset, arg); - ret =stm32_pmx_gpio_set_direction (pctldev,NULL , pin, false); + ret =stm32_pmx_gpio_set_direction (pctldev, range, pin, false);break ;default : ret = -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 21/36 pinctrl: sunxi: Fix SPDIF function name for A83T
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Chen-Yu Tsai <[email protected]>
commit 7903d4f5e1dec53963cba9b1bc472a76a3532e07 upstream.
We use well known standard names for functions that have name, such as I2C, SPI, SPDIF, etc..
Fix the function name of SPDIF, which was named OWA (One Wire Audio) based on Allwinner datasheets.
support")
--- drivers/pinctrl/sunxi/pinctrl-sun8i-a83t.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/sunxi/pinctrl-sun8i-a83t.c +1 -1
@@ -394,7 +394,7 @@ static const struct sunxi_desc_pin sun8iSUNXI_PIN (SUNXI_PINCTRL_PIN (E ,18 ),SUNXI_FUNCTION (0x0 ,"gpio_in" ),SUNXI_FUNCTION (0x1 ,"gpio_out" ), -SUNXI_FUNCTION (0x3 ,"owa" )),/* DOUT */ +SUNXI_FUNCTION (0x3 ,"spdif" )),/* DOUT */ SUNXI_PIN (SUNXI_PINCTRL_PIN (E ,19 ),SUNXI_FUNCTION (0x0 ,"gpio_in" ), SUNXI_FUNCTION(0x1, "gpio_out")),
Greg Kroah-Hartman
maintainerPATCH 22/36 pinctrl: core: Fix warning by removing bogus code
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tony Lindgren <[email protected]>
commit 664b7c4728821767e0228ee161bab87db2be58f1 upstream.
Andre Przywara <[email protected]> noticed that we can get the following warning with -EPROBE_DEFER:
"WARNING: CPU: 1 PID: 89 at drivers/base/dd.c:349driver_probe_device+0x2ac/0x2e8"
Let's fix the issue by removing the indices as suggested by Tejun Heo <[email protected]>. All we have to do here is kill the radix tree.
I probably ended up with the indices after grepping for removal of all entries using radix_tree_for_each_slot() and the first match found was gmap_radix_tree_free(). Anyways, no need for indices here, and we can just do remove all the entries using radix_tree_for_each_slot() along how the item_kill_tree() test case does.
--- drivers/pinctrl/core.c | 20 +++----------------- drivers/pinctrl/pinmux.c | 21 ++++----------------- 2 files changed, 7 insertions(+), 34 deletions(-)
drivers/pinctrl/core.c +3 -17
@@ -680,30 +680,16 @@ EXPORT_SYMBOL_GPL(pinctrl_generic_remove* pinctrl_generic_free_groups() - removes all pin groups * @pctldev: pin controller device * -* Note that the caller must take care of locking. +* Note that the caller must take care of locking. The pinctrl groups +* are allocated with devm_kzalloc() so no need to free them here. */ static void pinctrl_generic_free_groups (struct pinctrl_dev *pctldev) {struct radix_tree_iter iter; -struct group_desc *group; -unsigned long *indices;void **slot; -int i =0 ; - - indices =devm_kzalloc (pctldev->dev,sizeof (*indices) * - pctldev->num_groups,GFP_KERNEL ); -if (!indices) -return ;radix_tree_for_each_slot (slot, &pctldev->pin_group_tree, &iter,0 ) - indices[i++] = iter.index; - -for (i =0 ; i < pctldev->num_groups; i++) { - group =radix_tree_lookup (&pctldev->pin_group_tree, - indices[i]); -radix_tree_delete (&pctldev->pin_group_tree, indices[i]); -devm_kfree (pctldev->dev, group); - } +radix_tree_delete (&pctldev->pin_group_tree, iter.index); pctldev->num_groups =0 ; }
drivers/pinctrl/pinmux.c +4 -17
@@ -826,30 +826,17 @@ EXPORT_SYMBOL_GPL(pinmux_generic_remove_* pinmux_generic_free_functions() - removes all functions * @pctldev: pin controller device * -* Note that the caller must take care of locking. +* Note that the caller must take care of locking. The pinctrl +* functions are allocated with devm_kzalloc() so no need to free +* them here. */ void pinmux_generic_free_functions (struct pinctrl_dev *pctldev) {struct radix_tree_iter iter; -struct function_desc *function; -unsigned long *indices;void **slot; -int i =0 ; - - indices =devm_kzalloc (pctldev->dev,sizeof (*indices) * - pctldev->num_functions,GFP_KERNEL ); -if (!indices) -return ;radix_tree_for_each_slot (slot, &pctldev->pin_function_tree, &iter,0 ) - indices[i++] = iter.index; - -for (i =0 ; i < pctldev->num_functions; i++) { - function =radix_tree_lookup (&pctldev->pin_function_tree, - indices[i]); -radix_tree_delete (&pctldev->pin_function_tree, indices[i]); -devm_kfree (pctldev->dev, function); - } +radix_tree_delete (&pctldev->pin_function_tree, iter.index); pctldev->num_functions =0 ; }
Greg Kroah-Hartman
maintainerPATCH 24/36 pinctrl: sh-pfc: r8a7791: Add missing HSCIF1 pinmux data
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sergei Shtylyov <[email protected]>
commit da7a692fbbab07f4e9798b5b52798f6e3256dd8f upstream.
The R8A7791 PFC driver was apparently based on the preliminary revisions of the user's manual, which omitted the HSCIF1 group E signals in the IPSR4 register description. This would cause HSCIF1's probe to fail with the messages like below:
sh-pfc e6060000.pfc: cannot locate data/mark enum_id for mark 1989 sh-sci e62c8000.serial: Error applying setting, reverse things back
sh-sci: probe of e62c8000.serial failed with error -22
Add the neceassary PINMUX_IPSR_MSEL() invocations for the HSCK1_E, HCTS1#_E, and HRTS1#_E signals...
--- drivers/pinctrl/sh-pfc/pfc-r8a7791.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/pinctrl/sh-pfc/pfc-r8a7791.c +3 -0
@@ -1010,14 +1010,17 @@ static const u16 pinmux_data[] = {PINMUX_IPSR_MSEL (IP4_12_10 ,SCL2 ,SEL_IIC2_0 ),PINMUX_IPSR_MSEL (IP4_12_10 ,GPS_CLK_B ,SEL_GPS_1 ),PINMUX_IPSR_MSEL (IP4_12_10 ,GLO_Q0_D ,SEL_GPS_3 ), +PINMUX_IPSR_MSEL (IP4_12_10 ,HSCK1_E ,SEL_HSCIF1_4 ),PINMUX_IPSR_GPSR (IP4_15_13 ,SSI_WS2 ),PINMUX_IPSR_MSEL (IP4_15_13 ,SDA2 ,SEL_IIC2_0 ),PINMUX_IPSR_MSEL (IP4_15_13 ,GPS_SIGN_B ,SEL_GPS_1 ),PINMUX_IPSR_MSEL (IP4_15_13 ,RX2_E ,SEL_SCIF2_4 ),PINMUX_IPSR_MSEL (IP4_15_13 ,GLO_Q1_D ,SEL_GPS_3 ), +PINMUX_IPSR_MSEL (IP4_15_13 ,HCTS1_N_E ,SEL_HSCIF1_4 ),PINMUX_IPSR_GPSR (IP4_18_16 ,SSI_SDATA2 ),PINMUX_IPSR_MSEL (IP4_18_16 ,GPS_MAG_B ,SEL_GPS_1 ),PINMUX_IPSR_MSEL (IP4_18_16 ,TX2_E ,SEL_SCIF2_4 ), +PINMUX_IPSR_MSEL (IP4_18_16 ,HRTS1_N_E ,SEL_HSCIF1_4 ),PINMUX_IPSR_GPSR (IP4_19 ,SSI_SCK34 ),PINMUX_IPSR_GPSR (IP4_20 ,SSI_WS34 ), PINMUX_IPSR_GPSR(IP4_21, SSI_SDATA3),
Greg Kroah-Hartman
maintainerPATCH 25/36 pinctrl: sh-pfc: Update info pointer after SoC-specific init
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Geert Uytterhoeven <[email protected]>
commit 3091ae775fae17084013021d01513bc1ad274e6a upstream.
Update the sh_pfc_soc_info pointer after calling the SoC-specific initialization function, as it may have been updated to e.g. handle different SoC revisions. This makes sure the correct subdriver name is printed later.
--- drivers/pinctrl/sh-pfc/core.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/pinctrl/sh-pfc/core.c +3 -0
@@ -586,6 +586,9 @@ static int sh_pfc_probe(struct platform_ ret = info->ops->init (pfc);if (ret <0 )return ret; + +/* .init() may have overridden pfc->info */ + info = pfc->info; }/* Enable dummy states for those platforms without pinctrl support */
Greg Kroah-Hartman
maintainerPATCH 28/36 xhci: Limit USB2 port wake support for AMD Promontory hosts
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jiahau Chang <[email protected]>
commit dec08194ffeccfa1cf085906b53d301930eae18f upstream.
For AMD Promontory xHCI host, although you can disable USB 2.0 ports in BIOS settings, those ports will be enabled anyway after you remove a device on that port and re-plug it in again. It's a known limitation of the chip. As a workaround we can clear the PORT_WAKE_BITS.
This will disable wake on connect, disconnect and overcurrent on AMD Promontory USB2 ports
--- drivers/usb/host/xhci-hub.c | 3 +++ drivers/usb/host/xhci-pci.c | 12 ++++++++++++ drivers/usb/host/xhci.h | 1 + 3 files changed, 16 insertions(+)
drivers/usb/host/xhci-hub.c +3 -0
@@ -1350,6 +1350,9 @@ int xhci_bus_suspend(struct usb_hcd *hcd t2 |=PORT_WKOC_E |PORT_WKCONN_E ; t2 &= ~PORT_WKDISC_E ; } +if ((xhci->quirks &XHCI_U2_DISABLE_WAKE ) && + (hcd->speed <HCD_USB3 )) + t2 &= ~PORT_WAKE_BITS ; }else t2 &= ~PORT_WAKE_BITS ;
drivers/usb/host/xhci-pci.c +12 -0
@@ -54,6 +54,11 @@#define PCI_DEVICE_ID_INTEL_APL_XHCI 0x5aa8#define PCI_DEVICE_ID_INTEL_DNV_XHCI 0x19d0 +#define PCI_DEVICE_ID_AMD_PROMONTORYA_4 0x43b9 +#define PCI_DEVICE_ID_AMD_PROMONTORYA_3 0x43ba +#define PCI_DEVICE_ID_AMD_PROMONTORYA_2 0x43bb +#define PCI_DEVICE_ID_AMD_PROMONTORYA_1 0x43bc +static const char hcd_name[] ="xhci_hcd" ;static struct hc_driver __read_mostly xhci_pci_hc_driver;
@@ -135,6 +140,13 @@ static void xhci_pci_quirks(struct devicif (pdev->vendor ==PCI_VENDOR_ID_AMD ) xhci->quirks |=XHCI_TRUST_TX_LENGTH ; +if ((pdev->vendor ==PCI_VENDOR_ID_AMD ) && + ((pdev->device ==PCI_DEVICE_ID_AMD_PROMONTORYA_4 ) || + (pdev->device ==PCI_DEVICE_ID_AMD_PROMONTORYA_3 ) || + (pdev->device ==PCI_DEVICE_ID_AMD_PROMONTORYA_2 ) || + (pdev->device ==PCI_DEVICE_ID_AMD_PROMONTORYA_1 ))) + xhci->quirks |=XHCI_U2_DISABLE_WAKE ; +if (pdev->vendor ==PCI_VENDOR_ID_INTEL ) { xhci->quirks |=XHCI_LPM_SUPPORT ; xhci->quirks |=XHCI_INTEL_HOST ;
drivers/usb/host/xhci.h +1 -0
@@ -1819,6 +1819,7 @@ struct xhci_hcd {/* For controller with a broken Port Disable implementation */ #define XHCI_BROKEN_PORT_PED (1 << 25)#define XHCI_LIMIT_ENDPOINT_INTERVAL_7 (1 << 26) +#define XHCI_U2_DISABLE_WAKE (1 << 27)unsigned int num_active_eps;unsigned int limit_active_eps;
Greg Kroah-Hartman
maintainerPATCH 29/36 gfs2: Fix glock rhashtable rcu bug
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andreas Gruenbacher <[email protected]>
commit 961ae1d83d055a4b9ebbfb4cc8ca62ec1a7a3b74 upstream.
Before commit 88ffbf3e03 "GFS2: Use resizable hash table for glocks", glocks were freed via call_rcu to allow reading the glock hashtable locklessly using rcu. This was then changed to free glocks immediately, which made reading the glock hashtable unsafe. Bring back the original code for freeing glocks via call_rcu.
--- fs/gfs2/glock.c | 11 +++++++++-- fs/gfs2/incore.h | 1 + 2 files changed, 10 insertions(+), 2 deletions(-)
fs/gfs2/glock.c +9 -2
@@ -80,9 +80,9 @@ static struct rhashtable_params ht_parmsstatic struct rhashtable gl_hash_table; -void gfs2_glock_free (struct gfs2_glock *gl) +static void gfs2_glock_dealloc (struct rcu_head *rcu) { -struct gfs2_sbd *sdp = gl->gl_name.ln_sbd; + struct gfs2_glock *gl = container_of(rcu, struct gfs2_glock, gl_rcu);if (gl->gl_ops->go_flags &GLOF_ASPACE ) {kmem_cache_free (gfs2_glock_aspace_cachep, gl);
@@ -90,6 +90,13 @@ void gfs2_glock_free(struct gfs2_glock *kfree (gl->gl_lksb.sb_lvbptr);kmem_cache_free (gfs2_glock_cachep, gl); } +} + +void gfs2_glock_free (struct gfs2_glock *gl) +{ +struct gfs2_sbd *sdp = gl->gl_name.ln_sbd; + +call_rcu (&gl->gl_rcu, gfs2_glock_dealloc);if (atomic_dec_and_test (&sdp->sd_glock_disposal))wake_up (&sdp->sd_glock_wait); }
fs/gfs2/incore.h +1 -0
@@ -370,6 +370,7 @@ struct gfs2_glock {loff_t end; } gl_vm; }; +struct rcu_head gl_rcu;struct rhash_head gl_node; };
Greg Kroah-Hartman
maintainerPATCH 30/36 Add "shutdown" to "struct class".
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Zimmerman <[email protected]>
commit f77af15165847406b15d8f70c382c4cb15846b2a upstream.
The TPM class has some common shutdown code that must be executed for all drivers. This adds some needed functionality for that.
--- drivers/base/core.c | 6 +++++- include/linux/device.h | 2 ++ 2 files changed, 7 insertions(+), 1 deletion(-)
drivers/base/core.c +5 -1
@@ -2667,7 +2667,11 @@ void device_shutdown(void)pm_runtime_get_noresume (dev);pm_runtime_barrier (dev); -if (dev->bus && dev->bus->shutdown) { +if (dev->class && dev->class->shutdown) { +if (initcall_debug) +dev_info (dev,"shutdown\n" ); + dev->class->shutdown (dev); + }else if (dev->bus && dev->bus->shutdown) {if (initcall_debug)dev_info (dev,"shutdown\n" ); dev->bus->shutdown (dev);
include/linux/device.h +2 -0
@@ -378,6 +378,7 @@ int subsys_virtual_register(struct bus_t* @suspend: Used to put the device to sleep mode, usually to a low power * state. * @resume: Used to bring the device from the sleep mode. +* @shutdown: Called at shut-down time to quiesce the device. * @ns_type: Callbacks so sysfs can detemine namespaces. * @namespace: Namespace of the device belongs to this class. * @pm: The default device power management operations of this class.
@@ -407,6 +408,7 @@ struct class {int (*suspend)(struct device *dev,pm_message_t state);int (*resume)(struct device *dev); +int (*shutdown)(struct device *dev);const struct kobj_ns_type_operations *ns_type;const void *(*namespace)(struct device *dev);
Greg Kroah-Hartman
maintainerPATCH 31/36 tpm: Issue a TPM2_Shutdown for TPM2 devices.
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Zimmerman <[email protected]>
commit d1bd4a792d3961a04e6154118816b00167aad91a upstream.
If a TPM2 loses power without a TPM2_Shutdown command being issued (a "disorderly reboot"), it may lose some state that has yet to be persisted to NVRam, and will increment the DA counter. After the DA counter gets sufficiently large, the TPM will lock the user out.
NOTE: This only changes behavior on TPM2 devices. Since TPM1 uses sysfs, and sysfs relies on implicit locking on chip->ops, it is not safe to allow this code to run in TPM1, or to add sysfs support to TPM2, until that locking is made explicit.
--- drivers/char/tpm/tpm-chip.c | 34 ++++++++++++++++++++++++++++++++++ drivers/char/tpm/tpm-sysfs.c | 3 +++ 2 files changed, 37 insertions(+)
drivers/char/tpm/tpm-chip.c +34 -0
@@ -132,6 +132,39 @@ static void tpm_dev_release(struct devic }/** +* tpm_class_shutdown() - prepare the TPM device for loss of power. +* @dev: device to which the chip is associated. +* +* Issues a TPM2_Shutdown command prior to loss of power, as required by the +* TPM 2.0 spec. +* Then, calls bus- and device- specific shutdown code. +* +* XXX: This codepath relies on the fact that sysfs is not enabled for +* TPM2: sysfs uses an implicit lock on chip->ops, so this could race if TPM2 +* has sysfs support enabled before TPM sysfs's implicit locking is fixed. +*/ +static int tpm_class_shutdown (struct device *dev) +{ + struct tpm_chip *chip = container_of(dev, struct tpm_chip, dev); + +if (chip->flags &TPM_CHIP_FLAG_TPM2 ) { +down_write (&chip->ops_sem); +tpm2_shutdown (chip,TPM2_SU_CLEAR ); + chip->ops =NULL ; +up_write (&chip->ops_sem); + } +/* Allow bus- and device-specific code to run. Note: since chip->ops +* is NULL, more-specific shutdown code will not be able to issue TPM +* commands. +*/ +if (dev->bus && dev->bus->shutdown) + dev->bus->shutdown (dev); +else if (dev->driver && dev->driver->shutdown) + dev->driver->shutdown (dev); +return 0 ; +} + +/** * tpm_chip_alloc() - allocate a new struct tpm_chip instance * @pdev: device to which the chip is associated * At this point pdev mst be initialized, but does not have to
@@ -169,6 +202,7 @@ struct tpm_chip *tpm_chip_alloc(struct ddevice_initialize (&chip->dev); chip->dev.class = tpm_class; + chip->dev.class->shutdown = tpm_class_shutdown; chip->dev.release = tpm_dev_release; chip->dev.parent = pdev; chip->dev.groups = chip->groups;
drivers/char/tpm/tpm-sysfs.c +3 -0
@@ -294,6 +294,9 @@ static const struct attribute_group tpm_void tpm_sysfs_add_device (struct tpm_chip *chip) { +/* XXX: If you wish to remove this restriction, you must first update +* tpm_sysfs to explicitly lock chip->ops. +*/ if (chip->flags &TPM_CHIP_FLAG_TPM2 )return ;
Greg Kroah-Hartman
maintainerPATCH 32/36 tpm: fix a kernel memory leak in tpm-sysfs.c
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jarkko Sakkinen <[email protected]>
commit 13b47cfcfc60495cde216eef4c01040d76174cbe upstream.
While cleaning up sysfs callback that prints EK we discovered a kernel memory leak. This commit fixes the issue by zeroing the buffer used for TPM command/response.
The leak happen when we use either tpm_vtpm_proxy, tpm_ibmvtpm or xen-tpmfront.
--- drivers/char/tpm/tpm-sysfs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/char/tpm/tpm-sysfs.c +2 -1
@@ -36,9 +36,10 @@ static ssize_t pubek_show(struct devicessize_t err;int i, rc;char *str = buf; -struct tpm_chip *chip =to_tpm_chip (dev); +memset (&tpm_cmd,0 ,sizeof (tpm_cmd)); + tpm_cmd.header.in = tpm_readpubek_header; err = tpm_transmit_cmd(chip, &tpm_cmd, READ_PUBEK_RESULT_SIZE, READ_PUBEK_RESULT_MIN_BODY_SIZE, 0,
Greg Kroah-Hartman
maintainerPATCH 33/36 x86/uaccess: Optimize copy_user_enhanced_fast_string() for short strings
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Paolo Abeni <[email protected]>
commit 236222d39347e0e486010f10c1493e83dbbdfba8 upstream.
According to the Intel datasheet, the REP MOVSB instruction exposes a pretty heavy setup cost (50 ticks), which hurts short string copy operations.
This change tries to avoid this cost by calling the explicit loop available in the unrolled code for strings shorter than 64 bytes.
The 64 bytes cutoff value is arbitrary from the code logic point of view - it has been selected based on measurements, as the largest value that still ensures a measurable gain.
Micro benchmarks of the __copy_from_user() function with lengths in the [0-63] range show this performance gain (shorter the string, larger the gain):
- in the [55%-4%] range on Intel Xeon(R) CPU E5-2690 v4
- in the [72%-9%] range on Intel Core i7-4810MQ
Other tested CPUs - namely Intel Atom S1260 and AMD Opteron 8216 - show no difference, because they do not expose the ERMS feature bit.
--- arch/x86/lib/copy_user_64.S | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
arch/x86/lib/copy_user_64.S +5 -2
@@ -37,7 +37,7 @@ ENTRY(copy_user_generic_unrolled) movl %edx,%ecx andl $63,%edx shrl $6,%ecx - jz 17f + jz .L_copy_short_string 1: movq (%rsi),%r8 2: movq 1*8(%rsi),%r9 3: movq 2*8(%rsi),%r10
@@ -58,7 +58,8 @@ ENTRY(copy_user_generic_unrolled) leaq 64(%rdi),%rdi decl %ecx jnz 1b -17: movl %edx,%ecx +.L_copy_short_string: + movl %edx,%ecx andl $7,%edx shrl $3,%ecx jz 20f
@@ -174,6 +175,8 @@ EXPORT_SYMBOL(copy_user_generic_string) */ ENTRY(copy_user_enhanced_fast_string) ASM_STAC + cmpl $64,%edx + jb .L_copy_short_string /* less then 64 bytes, avoid the costly 'rep' */ movl %edx,%ecx 1: rep movsb
Greg Kroah-Hartman
maintainerPATCH 34/36 xen: avoid deadlock in xenbus driver
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Juergen Gross <[email protected]>
commit 1a3fc2c402810bf336882e695abd1678dbc8d279 upstream.
There has been a report about a deadlock in the xenbus driver:
[ 247.979498] ======================================================
[ 247.985688] WARNING: possible circular locking dependency detected
[ 247.991882] 4.12.0-rc4-00022-gc4b25c0 #575 Not tainted
[ 247.997040] ------------------------------------------------------
[ 248.003232] xenbus/91 is trying to acquire lock:
[ 248.007875] (&u->msgbuffer_mutex){+.+.+.}, at: [<ffff00000863e904>]
xenbus_dev_queue_reply+0x3c/0x230
[ 248.017163]
[ 248.017163] but task is already holding lock:
[ 248.023096] (xb_write_mutex){+.+...}, at: [<ffff00000863a940>]
xenbus_thread+0x5f0/0x798
[ 248.031267]
[ 248.031267] which lock already depends on the new lock.
[ 248.031267]
[ 248.039615]
[ 248.039615] the existing dependency chain (in reverse order) is:
[ 248.047176]
[ 248.047176] -> #1 (xb_write_mutex){+.+...}:
[ 248.052943] __lock_acquire+0x1728/0x1778
[ 248.057498] lock_acquire+0xc4/0x288
[ 248.061630] __mutex_lock+0x84/0x868
[ 248.065755] mutex_lock_nested+0x3c/0x50
[ 248.070227] xs_send+0x164/0x1f8
[ 248.074015] xenbus_dev_request_and_reply+0x6c/0x88
[ 248.079427] xenbus_file_write+0x260/0x420
[ 248.084073] __vfs_write+0x48/0x138
[ 248.088113] vfs_write+0xa8/0x1b8
[ 248.091983] SyS_write+0x54/0xb0
[ 248.095768] el0_svc_naked+0x24/0x28
[ 248.099897]
[ 248.099897] -> #0 (&u->msgbuffer_mutex){+.+.+.}:
[ 248.106088] print_circular_bug+0x80/0x2e0
[ 248.110730] __lock_acquire+0x1768/0x1778
[ 248.115288] lock_acquire+0xc4/0x288
[ 248.119417] __mutex_lock+0x84/0x868
[ 248.123545] mutex_lock_nested+0x3c/0x50
[ 248.128016] xenbus_dev_queue_reply+0x3c/0x230
[ 248.133005] xenbus_thread+0x788/0x798
[ 248.137306] kthread+0x110/0x140
[ 248.141087] ret_from_fork+0x10/0x40It is rather easy to avoid by dropping xb_write_mutex before calling xenbus_dev_queue_reply().
driver for multiple concurrent xenstore accesses").
--- drivers/xen/xenbus/xenbus_comms.c | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-)
drivers/xen/xenbus/xenbus_comms.c +10 -11
@@ -299,17 +299,7 @@ static int process_msg(void)mutex_lock (&xb_write_mutex);list_for_each_entry (req, &xs_reply_list, list) {if (req->msg.req_id == state.msg.req_id) { -if (req->state == xb_req_state_wait_reply) { - req->msg.type = state.msg.type; - req->msg.len = state.msg.len; - req->body = state.body; - req->state = xb_req_state_got_reply; -list_del (&req->list); - req->cb (req); - }else { -list_del (&req->list); -kfree (req); - } +list_del (&req->list); err =0 ;break ; }
@@ -317,6 +307,15 @@ static int process_msg(void)mutex_unlock (&xb_write_mutex);if (err) goto out; + +if (req->state == xb_req_state_wait_reply) { + req->msg.type = state.msg.type; + req->msg.len = state.msg.len; + req->body = state.body; + req->state = xb_req_state_got_reply; + req->cb (req); + }else +kfree (req); }mutex_unlock (&xs_response_mutex);
Greg Kroah-Hartman
maintainerPATCH 35/36 crypto: drbg - Fixes panic in wait_for_completion call
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stephan Mueller <[email protected]>
commit b61929c654f2e725644935737c4c1ea9c741e2f8 upstream.
Initialise ctr_completion variable before use.
--- crypto/drbg.c | 1 + 1 file changed, 1 insertion(+)
crypto/drbg.c +1 -0
@@ -1691,6 +1691,7 @@ static int drbg_init_sym_kernel(struct dreturn PTR_ERR (sk_tfm); } drbg->ctr_handle = sk_tfm; +init_completion (&drbg->ctr_completion); req =skcipher_request_alloc (sk_tfm,GFP_KERNEL );if (!req) {
Greg Kroah-Hartman
maintainerPATCH 36/36 rt286: add Thinkpad Helix 2 to force_combo_jack_table
In reply to Greg Kroah-Hartman4.11-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yifeng Li <[email protected]>
commit fe0dfd6358a17c79bd7d6996af7512ba452a7059 upstream.
Thinkpad Helix 2 is a tablet PC, the audio is powered by Core M broadwell-audio and rt286 codec. For all versions of Linux kernel, the stereo output doesn't work properly when earphones are plugged in, the sound was coming out from both channels even if the audio contains only the left or right channel. Furthermore, if a music recorded in stereo is played, the two channels cancle out each other out, as a result, no voice but only distorted background music can be heard, like a sound card with builtin a Karaoke sount effect.
Apparently this tablet uses a combo jack with polarity incorrectly set by rt286 driver. This patch adds DMI information of Thinkpad Helix 2 to force_combo_jack_table[] and the issue is resolved. The microphone input doesn't work regardless to the presence of this patch and still needs help from other developers to investigate.
This is my first patch to LKML directly, sorry for CC-ing too many people here.
--- sound/soc/codecs/rt286.c | 7 +++++++ 1 file changed, 7 insertions(+)
sound/soc/codecs/rt286.c +7 -0
@@ -1108,6 +1108,13 @@ static const struct dmi_system_id force_ DMI_MATCH(DMI_PRODUCT_NAME, "Kabylake Client platform") } }, + { + .ident = "Thinkpad Helix 2nd", + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"LENOVO" ), + DMI_MATCH(DMI_PRODUCT_VERSION, "ThinkPad Helix 2nd") + } + }, { } };
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.11.10 release. There are 36 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 Jul 12 17:10:29 UTC 2017. Anything received after that time might be too late.
Build results:
total: 145 pass: 145 fail: 0 Qemu test results: total: 122 pass: 122 fail: 0
Details are available at http://kerneltests.org/builders.
Guenter