Re: [RFC][PATCH 3/3] locking/qspinlock: Optimize for x86

On Tue, Oct 02, 2018 at 02:19:53PM +0100, Will Deacon wrote: > On Mon, Oct 01, 2018 at 10:00:28PM +0200, Peter Zijlstra wrote: > > Let me draw a picture of that.. > > > > > > CPU0 CPU1CPU2CPU3 > > > > 0) lock > >

[PATCH 4.18 003/228] tsl2550: fix lux1_input error in low light

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Matt Ranostay [ Upstream commit ce054546cc2c26891cefa2f284d90d93b52205de ] ADC channel 0 photodiode detects both infrared + visible light, but ADC channel 1 just detects infrared. However, the

[PATCH 4.18 034/228] IB/mlx4: Test port number before querying type.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tarick Bedeir [ Upstream commit f1228867adaf8890826f2b59e4caddb1c5cc2df7 ] rdma_ah_find_type() can reach into ib_device->port_immutable with a potentially out-of-bounds port number, so check t

[PATCH 4.18 032/228] IB/core: type promotion bug in rdma_rw_init_one_mr()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit c2d7c8ff89b22ddefb1ac2986c0d48444a667689 ] "nents" is an unsigned int, so if ib_map_mr_sg() returns a negative error code then it's type promoted to a high unsi

[PATCH 4.18 035/228] powerpc/kdump: Handle crashkernel memory reservation failure

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hari Bathini [ Upstream commit 8950329c4a64c6d3ca0bc34711a1afbd9ce05657 ] Memory reservation for crashkernel could fail if there are holes around kdump kernel offset (128M). Fail gracefully in

[PATCH 4.18 004/228] misc: ibmvmc: Use GFP_ATOMIC under spin lock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun [ Upstream commit 97b715b62e5b4c6edb75d023f556fd09a46cb4e1 ] The function alloc_dma_buffer() is called from ibmvmc_add_buffer(), in which a spin lock be held here, so we should use

[PATCH 4.18 005/228] vmci: type promotion bug in qp_host_get_user_memory()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ] The problem is that if get_user_pages_fast() fails and returns a negative error code, it gets type promoted to a high

[PATCH 4.18 033/228] media: exynos4-is: Prevent NULL pointer dereference in __isp_video_try_fmt()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sylwester Nawrocki [ Upstream commit 7c1b9a5aeed91bef98988ac0fcf38c8c1f4f9a3a ] This patch fixes potential NULL pointer dereference as indicated by the following static checker warning: drive

[PATCH 4.18 008/228] net: hns3: Fix for mac pause not disable in pfc mode

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Yunsheng Lin [ Upstream commit 6d0ec65cb5810f9bf08671be008785bb8c84d39f ] When pfc pause mode is enable, the mac pause mode need to be disabled, otherwise the pfc pause packet will not be sent

[PATCH 4.18 038/228] media: staging/imx: fill vb2_v4l2_buffer field entry

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Seiderer [ Upstream commit a38d4b71cb7a12b65317f4e3d59883a918957719 ] - fixes gstreamer v4l2src warning: 0:00:00.716640334 349 0x164f720 WARN v4l2bufferpool gstv4l2bufferpool.c:11

[PATCH 4.18 047/228] scsi: klist: Make it safe to use klists in atomic context

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 624fa7790f80575a4ec28fbdb2034097dc18d051 ] In the scsi_transport_srp implementation it cannot be avoided to iterate over a klist from atomic context when usin

Re: [PATCH v6] selftests: add headers_install to lib.mk

Shuah Khan writes: > On 09/27/2018 10:52 PM, Michael Ellerman wrote: >> [ + linuxppc-dev ] >> >> Anders Roxell writes: >>> If the kernel headers aren't installed we can't build all the tests. >>> Add a new make target rule 'khdr' in the file lib.mk to generate the >>> kernel headers and that get

[PATCH 4.18 000/228] 4.18.12-stable review

This is the start of the stable review cycle for the 4.18.12 release. There are 228 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 Thu Oct 4 13:24:08 UTC 2018. Anything recei

[PATCH 4.18 050/228] usb: wusbcore: security: cast sizeof to int for comparison

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Julia Lawall [ Upstream commit d3ac5598c5010a878ebbcca3b1c6188ca36b ] Comparing an int to a size, which is unsigned, causes the int to become unsigned, giving the wrong result. usb_get_de

[PATCH 4.18 052/228] ath10k: sdio: set skb len for all rx packets

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alagu Sankar [ Upstream commit 8530b4e7b22bc3bd8240579f3844c73947cd5f71 ] Without this, packets larger than 1500 will silently be dropped. Easily reproduced by sending a ping packet with a siz

[PATCH 4.18 049/228] scsi: target: Avoid that EXTENDED COPY commands trigger lock inversion

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit 36d4cb460bcbe2a1323732a6e4bb9dd783284368 ] The approach for adding a device to the devices_idr data structure and for removing it is as follows: * &dev->dev_

[PATCH 4.18 048/228] scsi: ibmvscsi: Improve strings handling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Breno Leitao [ Upstream commit 1262dc09dc9ae7bf4ad00b6a2c5ed6a6936bcd10 ] Currently an open firmware property is copied into partition_name variable without keeping a room for \0. Later one,

[PATCH 4.18 054/228] platform/x86: asus-wireless: Fix uninitialized symbol usage

4.18-stable review patch. If anyone has any objections, please let me know. -- From: João Paulo Rechi Vita [ Upstream commit eca4c4e47eb0658ad251f0bff465e23c055377da ] 'ret' will not be initialized if acpi_evaluate_integer() returns through an error path, so it should not be u

[PATCH 4.18 051/228] ath10k: sdio: use same endpoint id for all packets in a bundle

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alagu Sankar [ Upstream commit 679e1f07c86221b7183dd69df7068fd42d0041f6 ] All packets in a bundle should use the same endpoint id as the first lookahead. This matches how things are done is a

[PATCH 4.18 055/228] ACPI / button: increment wakeup count only when notified

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ravi Chandra Sadineni [ Upstream commit 7c058c7c74b3dbeb7d157c273959f87faf710350 ] Because acpi_lid_initialize_state() is called on every system resume and it triggers acpi_lid_notify_state()

[PATCH 4.18 057/228] alarmtimer: Prevent overflow for relative nanosleep

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef ] Air Icy reported: UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7 signed integer overflow: 1529

[PATCH 4.18 059/228] s390/scm_blk: correct numa_node in scm_blk_dev_setup

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Gorbik [ Upstream commit d642d6262f4fcfa5d200ec6e218c17f0c15b3390 ] The numa_node field of the tag_set struct has to be explicitly initialized, otherwise it stays as 0, which is a valid

[PATCH 4.18 060/228] s390/extmem: fix gcc 8 stringop-overflow warning

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Gorbik [ Upstream commit 6b2ddf33baec23dace85bd647e3fc4ac070963e8 ] arch/s390/mm/extmem.c: In function '__segment_load': arch/s390/mm/extmem.c:436:2: warning: 'strncat' specified bound

[PATCH 4.18 061/228] mtd: rawnand: atmel: add module param to avoid using dma

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Peter Rosin [ Upstream commit efc6362c6f8c1e74b340e2611f1b35e7d557ce7b ] On a sama5d31 with a Full-HD dual LVDS panel (132MHz pixel clock) NAND flash accesses have a tendency to cause display

Re: [PATCH v3 2/3] perf: add arm64 smmuv3 pmu driver

Hi Shameer, I have a few comments below, mostly naive since I don't know anything about perf drivers. On 21/09/2018 16:08, Shameer Kolothum wrote: > From: Neil Leeder > > Adds a new driver to support the SMMUv3 PMU and add it into the > perf events framework. > > Each SMMU node may have multip

[PATCH 4.18 065/228] ALSA: snd-aoa: add of_node_put() in error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Mc Guire [ Upstream commit 222bce5eb88d1af656419db04bcd84b2419fb900 ] Both calls to of_find_node_by_name() and of_get_next_child() return a node pointer with refcount incremented thu

[PATCH 4.18 063/228] posix-timers: Make forward callback return s64

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 6fec64e1c92d5c715c6d0f50786daa7708266bde ] The posix timer ti_overrun handling is broken because the forwarding functions can return a huge number of overruns

[PATCH 4.18 064/228] posix-timers: Sanitize overrun handling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner [ Upstream commit 78c9c4dfbf8c04883941445a195276bb4bb92c76 ] The posix timer overrun handling is broken because the forwarding functions can return a huge number of overruns wh

[PATCH 4.18 068/228] media: s3c-camif: ignore -ENOIOCTLCMD from v4l2_subdev_call for s_power

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 30ed2b83343bd1e07884ca7355dac70d25ffc158 ] When the subdevice doesn't provide s_power core ops callback, the v4l2_subdev_call for s_power returns -ENOIOCTLCMD.

Re: [PATCH 4/5] locking/lockdep: Make class->ops a percpu counter

On 10/02/2018 05:55 AM, Ingo Molnar wrote: > * Peter Zijlstra wrote: > >> On Fri, Sep 28, 2018 at 01:53:20PM -0400, Waiman Long wrote: >>> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c >>> index ca002c0..7a0ed1d 100644 >>> --- a/kernel/locking/lockdep.c >>> +++ b/kernel/locking/

[PATCH 4.18 071/228] media: ov772x: add checks for register read errors

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 30f3b17eaf4913e9e56be15915ce57aae69db701 ] This change adds checks for register read errors and returns correct error code. Cc: Laurent Pinchart Cc: Hans Verku

[PATCH 4.18 070/228] media: omap3isp: zero-initialize the isp cam_xclk{a,b} initial data

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas [ Upstream commit 2ec7debd44b49927a6e2861521994cc075a389ed ] The struct clk_init_data init variable is declared in the isp_xclk_init() function so is an automatic vari

[PATCH 4.18 072/228] staging: android: ashmem: Fix mmap size validation

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alistair Strachan [ Upstream commit 8632c614565d0c5fdde527889601c018e97b6384 ] The ashmem driver did not check that the size/offset of the vma passed to its .mmap() function was not larger tha

[PATCH 4.18 043/228] x86/entry/64: Add two more instruction suffixes

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich [ Upstream commit 6709812f094d96543b443645c68daaa32d3d3e77 ] Sadly, other than claimed in: a368d7fd2a ("x86/entry/64: Add instruction suffix") ... there are two more instances

[PATCH 4.18 044/228] ARM: dts: ls1021a: Add missing cooling device properties for CPUs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit 47768f372eae030db6fab5225f9504a820d2c07f ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for all

[PATCH 4.18 077/228] serial: pxa: Fix an error handling path in serial_pxa_probe()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 95a0e656580fab3128c7bee5f660c50784f53651 ] If port.line is out of range, we still need to release some resources, or we will leak them. Fixes: afc7851fab8

[PATCH 4.18 073/228] media: ov772x: allow i2c controllers without I2C_FUNC_PROTOCOL_MANGLING

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Akinobu Mita [ Upstream commit 0b964d183cbf3f95a062ad9f3eec87ffa2790558 ] The ov772x driver only works when the i2c controller have I2C_FUNC_PROTOCOL_MANGLING. However, many i2c controller dr

[PATCH 4.18 076/228] arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit c5a884838ce34681200b5a45b2330177036affd0 ] With recent dtc and W=1: ...salvator-x.dtb: Warning (graph_port): /soc/i2c@e66d8000/video-receiver@70/port

[PATCH 4.18 041/228] x86/tsc: Add missing header to tsc_msr.c

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko [ Upstream commit dbd0fbc76c77daac08ddd245afdcbade0d506e19 ] Add a missing header otherwise compiler warns about missed prototype: CC arch/x86/kernel/tsc_msr.o arch/x86/k

[PATCH 4.18 046/228] thermal: i.MX: Allow thermal probe to fail gracefully in case of bad calibration.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jean-Christophe Dubois [ Upstream commit be926ceeb4efc3bf44cb9b56f5c71aac9b1f8bbe ] Without this fix, the thermal probe on i.MX6 might trigger a division by zero exception later in the probe i

[PATCH 4.18 090/228] brcmsmac: fix wrap around in conversion from constant to s16

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner [ Upstream commit c9a61469fc97672a08b2f798830a55ea6e03dc4a ] The last value in the log_table wraps around to a negative value since s16 has a value range of -32768 to 32767. This

[PATCH 4.18 091/228] bitfield: fix *_encode_bits()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg [ Upstream commit e7d4a95da86e0b048702765bbdcdc968aaf312e7 ] There's a bug in *_encode_bits() in using ~field_multiplier() for the check whether or not the constant value fits in

[PATCH 4.18 094/228] ARM: mvebu: declare asm symbols as character arrays in pmsu.c

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ethan Tuttle [ Upstream commit d0d378ff451a66e486488eec842e507d28145813 ] With CONFIG_FORTIFY_SOURCE, memcpy uses the declared size of operands to detect buffer overflows. If src or dest is d

[PATCH 4.18 037/228] vhost_net: Avoid tx vring kicks during busyloop

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit 027b17603b030f1334ade079b7a3e986569c956b ] Under heavy load vhost busypoll may run without suppressing notification. For example tx zerocopy callback can push

[PATCH 4.18 080/228] ASoC: qdsp6: qdafe: fix some off by one bugs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit c54c1c5ee8e73b7cb752834e52e2129b1dab00bd ] The > should be >= or we could read one element beyond the end of the port_maps[] array. Fixes: 7fa2d70f9766 ("ASoC:

[PATCH v4 3/3] gpiolib: Show correct direction from the beginning

Current code assumes that the direction is input if direction_input function is set. This might not be the case on GPIOs with programmable direction. Signed-off-by: Ricardo Ribalda Delgado --- Changelog v4: ti...@kernel.org: Remove REVISIT comment drivers/gpio/gpiolib.c | 27 +-

[PATCH 4.18 095/228] RDMA/uverbs: Dont overwrite NULL pointer with ZERO_SIZE_PTR

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit a5cc9831af05e658543593abaee45a29d061bac4 ] Number of specs is provided by user and in valid case can be equal to zero. Such argument causes to call to kcalloc

[PATCH 4.18 097/228] perf/hw_breakpoint: Split attribute parse and commit

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Frederic Weisbecker [ Upstream commit 9a4903dde2c8633c5fcf887b98c4e047a6154a54 ] arch_validate_hwbkpt_settings() mixes up attribute check and commit into a single code entity. Therefore the va

[PATCH 4.18 099/228] HID: hid-ntrig: add error handling for sysfs_create_group

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit 44d4d51de9a3534a2b63d69efda02a10e66541e4 ] When sysfs_create_group fails, the lack of error-handling code may cause unexpected results. This patch adds error-ha

[PATCH 4.18 098/228] arm: dts: mediatek: Add missing cooling device properties for CPUs

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar [ Upstream commit 0c7f7a5150023f3c6f0b27c4d4940ce3dfaf62cc ] The cooling device properties, like "#cooling-cells" and "dynamic-power-coefficient", should either be present for all

[PATCH 4.18 100/228] HID: i2c-hid: Use devm to allocate i2c_hid struct

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd [ Upstream commit d6f83894110de247a81392ab7ef89e5498df7e80 ] Use devm here to save some lines and prepare for bulk regulator usage in this driver. Otherwise, when we devm bulk get

[PATCH 4.18 106/228] iomap: complete partial direct I/O writes synchronously

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher [ Upstream commit ebf00be37de35788cad72f4f20b4a39e30c0be4a ] According to xfstest generic/240, applications seem to expect direct I/O writes to either complete as a whole o

[PATCH 4.18 105/228] scsi: bnx2i: add error handling for ioremap_nocache

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Zhouyang Jia [ Upstream commit aa154ea885eb0c2407457ce9c1538d78c95456fa ] When ioremap_nocache fails, the lack of error-handling code may cause unexpected results. This patch adds error-handl

[PATCH 4.18 103/228] drm/v3d: Take a lock across GPU scheduler job creation and queuing.

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Anholt [ Upstream commit 7122b68b8a9692dcc3acf89595f04c492872115f ] Between creation and queueing of a job, you need to prevent any other job from being created and queued. Otherwise the

[PATCH 4.18 104/228] perf/x86/intel/lbr: Fix incomplete LBR call stack

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kan Liang [ Upstream commit 0592e57b24e7e05ec1f4c50b9666c013abff7017 ] LBR has a limited stack size. If a task has a deeper call stack than LBR's stack size, only the overflowed part is report

[PATCH 4.18 112/228] ASoC: rsnd: SSI parent cares SWSP bit

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Kuninori Morimoto [ Upstream commit 203cdf51f28820bee7893b4be392847418e6f4ec ] SSICR has SWSP bit (= Serial WS Polarity) which decides WS pin 1st channel polarity (low or hi). This bit shouldn

[PATCH 4.18 082/228] net: phy: xgmiitorgmii: Check read_status results

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Brandon Maier [ Upstream commit 8d0752d11312be830c33e84dfd1016e6a47c2938 ] We're ignoring the result of the attached phy device's read_status(). Return it so we can detect errors. Signed-off-

[PATCH 4.18 116/228] gpio: Fix wrong rounding in gpio-menz127

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Nadav Amit [ Upstream commit 7279d9917560bbd0d82813d6bf00490a82c06783 ] men_z127_debounce() tries to round up and down, but uses functions which are only suitable when the divider is a power o

[PATCH 4.18 113/228] EDAC, i7core: Fix memleaks and use-after-free on probe and remove

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit 6c974d4dfafe5e9ee754f2a6fba0eb1864f1649e ] Make sure to free and deregister the addrmatch and chancounts devices allocated during probe in all error paths. Also

[PATCH 4.18 109/228] scsi: megaraid_sas: Update controller info during resume

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Shivasharan S [ Upstream commit c3b10a55abc943a526aaecd7e860b15671beb906 ] There is a possibility that firmware on the controller was upgraded before system was suspended. During resume, drive

[PATCH 4.18 111/228] ASoC: rt1305: Use ULL suffixes for 64-bit constants

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit 4f29b663c08d369fe320a148179996c94cf7d01b ] With gcc 4.1.2: sound/soc/codecs/rt1305.c: In function ‘rt1305_calibrate’: sound/soc/codecs/rt1305.c:10

[PATCH 4.18 115/228] module: exclude SHN_UNDEF symbols from kallsyms api

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jessica Yu [ Upstream commit 9f2d1e68cf4d641def734adaccfc3823d3575e6c ] Livepatch modules are special in that we preserve their entire symbol tables in order to be able to apply relocations af

[PATCH 4.18 117/228] nfsd: fix corrupted reply to badly ordered compound

4.18-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" [ Upstream commit 5b7b15aee641904ae269be9846610a3950cbd64c ] We're encoding a single op in the reply but leaving the number of ops zero, so the reply makes no sense. Somewha

[PATCH 4.18 118/228] EDAC: Fix memleak in module init error path

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit 4708aa85d50cc6e962dfa8acf5ad4e0d290a21db ] Make sure to use put_device() to free the initialised struct device so that resources managed by driver core also gets

[PATCH 4.18 083/228] ath10k: protect ath10k_htt_rx_ring_free with rx_ring.lock

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Greear [ Upstream commit 168f75f11fe68455e0d058a818ebccfc329d8685 ] While debugging driver crashes related to a buggy firmware crashing under load, I noticed that ath10k_htt_rx_ring_free c

[PATCH 4.18 087/228] ath10k: transmit queued frames after processing rx packets

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ] When running iperf on ath10k SDIO, TX can stop working: iperf -c 192.168.1.1 -i 1 -t 20 -w 10K [ 3] 0.0- 1.0 sec

[PATCH 4.18 086/228] drm/sun4i: Fix releasing node when enumerating enpoints

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Jernej Skrabec [ Upstream commit 367c359aa8637b15ee8df6335c5a29b7623966ec ] sun4i_drv_add_endpoints() has a memory leak since it uses of_node_put() when remote is equal to NULL and does nothin

[PATCH 4.18 130/228] perf tests: Fix indexing when invoking subtests

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das [ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ] Recently, the subtest numbering was changed to start from 1. While it is fine for displaying results, this should not

[PATCH 4.18 088/228] mt76x2: fix mrr idx/count estimation in mt76x2_mac_fill_tx_status()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Lorenzo Bianconi [ Upstream commit 2d1e9be0016230f3707812243561fbd16f1aea4b ] Fix mcs and attempt count estimation in mt76x2_mac_fill_tx_status routine if the number of tx retries reported by

[PATCH 4.18 132/228] floppy: Do not copy a kernel pointer to user memory in FDGETPRM ioctl

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Andy Whitcroft commit 65eea8edc315589d6c993cf12dbb5d0e9ef1fe4e upstream. The final field of a floppy_struct is the field "name", which is a pointer to a string in kernel memory. The kernel po

[PATCH 4.18 131/228] gpio: tegra: Fix tegra_gpio_irq_set_type()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Osipenko [ Upstream commit f78709a5d4114edc21a5d86586ed5e56e284f2bd ] Commit 36b312792b97 ("gpiolib: Respect error code of ->get_direction()") broke tegra_gpio_irq_set_type() because re

Re: [PATCH v7 03/14] PM: Introduce an Energy Model management framework

On Tuesday 02 Oct 2018 at 15:48:57 (+0200), Peter Zijlstra wrote: > +/** > + * em_cpu_get() - Return the performance domain for a CPU > + * @cpu : CPU to find the performance domain for > + * > + * Return: the performance domain to which 'cpu' belongs, or NULL if it > doesn't > + * exist. > + */ >

[PATCH 4.18 135/228] tty: serial: lpuart: avoid leaking struct tty_struct

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner commit 3216c622a24b0ebb9c159a8d1daf7f17a106b3f5 upstream. The function tty_port_tty_get() gets a reference to the tty. Since the code is not using tty_port_tty_set(), the referenc

[PATCH 4.18 136/228] serial: imx: restore handshaking irq for imx1

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Uwe Kleine-König commit 7e620984b62532783912312e334f3c48cdacbd5d upstream. Back in 2015 when irda was dropped from the driver imx1 was broken. This change reintroduces the support for the thir

Re: [PATCH v4 1/6] mpt3sas: Introduce mpt3sas_base_pci_device_is_available

On Mon, Oct 01, 2018 at 03:40:51PM -0500, Bjorn Helgaas wrote: > I think the names "pci_device_is_present()" and > "mpt3sas_base_pci_device_is_available()" contribute to the problem > because they make promises that can't be kept -- all we can say is > that the device *was* present, but we know whe

[PATCH 4.18 139/228] intel_th: Fix device removal logic

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 8801922cd94c918e4dc3a108ecaa500c4d40583f upstream. Commit a753bfcfdb1f ("intel_th: Make the switch allocate its subdevices") brings in new subdevice addition/removal

[PATCH 4.18 142/228] spi: sh-msiof: Fix invalid SPI use during system suspend

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Gaku Inami commit ffa69d6a16f686efe45269342474e421f2aa58b2 upstream. If the SPI queue is running during system suspend, the system may lock up. Fix this by stopping/restarting the queue durin

[PATCH 4.18 148/228] USB: fix error handling in usb_driver_claim_interface()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit bd729f9d67aa9a303d8925bb8c4f06af25f407d1 upstream. The syzbot fuzzing project found a use-after-free bug in the USB core. The bug was caused by usbfs not unbinding from an i

[PATCH 4.18 147/228] regulator: Fix do-nothing value for regulators without suspend state

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 3edd79cf5a44b12dbb13bc320f5788aed6562b36 upstream. Some regulators don't have all states defined and in such cases regulator core should not assume anything. However in

[PATCH 4.18 123/228] fs/lock: skip lock owner pid translation in case we are in init_pid_ns

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Konstantin Khorenko [ Upstream commit 826d7bc9f013d01e92997883d2fd0c25f4af1f1c ] If the flock owner process is dead and its pid has been already freed, pid translation won't work, but we still

[PATCH 4.18 149/228] USB: handle NULL config in usb_find_alt_setting()

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Alan Stern commit c9a4cb204e9eb7fa7dfbe3f7d3a674fa530aa193 upstream. usb_find_alt_setting() takes a pointer to a struct usb_host_config as an argument; it searches for an interface with specif

[PATCH 4.18 143/228] spi: sh-msiof: Fix handling of write value for SISTR register

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Hiromitsu Yamasaki commit 31a5fae4c5a009898da6d177901d5328051641ff upstream. This patch changes writing to the SISTR register according to the H/W user's manual. The TDREQ bit and RDREQ bits

[PATCH 4.18 152/228] usb: musb: dsps: do not disable CPPI41 irq in driver teardown

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Bin Liu commit 783f3b4e9ec50491c21746e7e05ec6c39c21f563 upstream. TI AM335x CPPI 4.1 module uses a single register bit for CPPI interrupts in both musb controllers. So disabling the CPPI irq i

[PATCH 4.18 124/228] ath10k: fix memory leak of tpc_stats

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit 260e629bbf441585860e21d5e10d2e88437f47c8 ] Currently tpc_stats is allocated and is leaked on the return path if num_tx_chain is greater than WMI_TPC_TX_N_CHAIN

[PATCH 4.18 158/228] ext2, dax: set ext2_dax_aops for dax files

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Toshi Kani commit 9e796c9db93b4840d1b00e550eea26db7cb741e2 upstream. Sync syscall to DAX file needs to flush processor cache, but it currently does not flush to existing DAX files. This is be

[PATCH 4.18 153/228] USB: usbdevfs: sanitize flags more

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 7a68d9fb851012829c29e770621905529bd9490b upstream. Requesting a ZERO_PACKET or not is sensible only for output. In the input direction the device decides. Likewise accepti

Re: [PATCH] ARM: makefile: use ARMv3M mode for RiscPC

On Tue, Oct 2, 2018 at 3:54 PM Arnd Bergmann wrote: > Please add this to Russell's patch tracker for inclusion at > http://www.arm.linux.org.uk/developer/patches/ Wild! And done: http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8801/1

[PATCH 4.18 125/228] Input: xen-kbdfront - fix multi-touch XenStore nodes locations

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Oleksandr Andrushchenko [ Upstream commit ce6f7d087e2b037f47349c1c36ac97678d02e394 ] kbdif protocol describes multi-touch device parameters as a part of frontend's XenBus configuration nodes w

[PATCH 4.18 127/228] drm/vc4: Add missing formats to vc4_format_mod_supported().

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Anholt [ Upstream commit 1e871d65e375280757833d9fce91dda71980bdf5 ] Daniel's format_mod_supported() patch predated Dave's for NV21/61, and I didn't catch that when rebasing. This is a pr

[PATCH 4.18 126/228] iio: 104-quad-8: Fix off-by-one error in register selection

4.18-stable review patch. If anyone has any objections, please let me know. -- From: William Breathitt Gray [ Upstream commit 2873c3f0e2bd12a7612e905c920c058855f4072a ] The reset flags operation is selected by bit 2 in the "Reset and Load Signals Decoders" register, not bit 1.

[PATCH 4.18 129/228] drm/vc4: plane: Expand the lower bits by repeating the higher bits

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Ripard [ Upstream commit 3257ec797d3a8c5232389eb1952d4451e80f3931 ] The vc4 HVS uses an internal RGB888 representation of the frames, and will by default expand formats using a lower de

[PATCH 4.18 174/228] qed: Prevent a possible deadlock during driver load and unload

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit eaa50fc59e5841910987e90b0438b2643041f508 ] The MFW manages an internal lock to prevent concurrent hardware (de)initialization of different PFs. This, together wit

[PATCH 4.18 163/228] IB/hfi1: Invalid user input can result in crash

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael J. Ruhl commit 94694d18cf27a6faad91487a38ce516c2b16e7d9 upstream. If the number of packets in a user sdma request does not match the actual iovectors being sent, sdma_cleanup can be ca

[PATCH 4.18 175/228] qed: Avoid sending mailbox commands when MFW is not responsive

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit b310974e041913231b6e3d5d475d4df55c312301 ] Keep sending mailbox commands to the MFW when it is not responsive ends up with a redundant amount of timeout expiries.

[PATCH 4.18 172/228] qed: Wait for ready indication before rereading the shmem

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tomer Tayar [ Upstream commit f00d25f3154b676fcea4502a25b94bd7f142ca74 ] The MFW might be reset and re-update its shared memory. Upon the detection of such a reset the driver rereads this memo

[PATCH 4.18 179/228] mmc: android-goldfish: fix bad logic of sg_copy_{from,to}_buffer conversion

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches [ Upstream commit 17e96d8516e31c3cb52cb8e2ee79d1d2e6948c11 ] The conversion to sg_copy_{from,to}_buffer has been done in the wrong way. sg_copy_to_buffer is a copy from an SG

[PATCH 4.18 180/228] bus: ti-sysc: Fix no_console_suspend handling

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 4f3530f4a41d49c41015020cd9a5ed5c95b5d2db ] If no_console_suspend is set, we should keep console enabled during suspend. Lets fix this by only producing a warnin

[PATCH 4.18 178/228] mmc: atmel-mci: fix bad logic of sg_copy_{from,to}_buffer conversion

4.18-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches [ Upstream commit 19f5e9e015675fcdbf2c20e804b2e84e80201454 ] The conversion to sg_copy_{from,to}_buffer has been done in the wrong way. sg_copy_to_buffer is a copy from an SG

Re: [PATCH v2] dma-debug: Check for drivers mapping invalid addresses in dma_map_single()

On 01/10/18 22:53, Stephen Boyd wrote: I recently debugged a DMA mapping oops where a driver was trying to map a buffer returned from request_firmware() with dma_map_single(). Memory returned from request_firmware() is mapped into the vmalloc region and this isn't a valid region to map with dma_m

[PATCH 4.18 185/228] bpf: sockmap: write_space events need to be passed to TCP handler

4.18-stable review patch. If anyone has any objections, please let me know. -- From: John Fastabend [ Upstream commit 9b2e0388bec8ec5427403e23faff3b58dd1c3200 ] When sockmap code is using the stream parser it also handles the write space events in order to handle the case wher

<    1   2   3   4   5   6   7   8   9   10   >