[PATCH 4.14 68/75] staging: ccree: fix leak of import() after init()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gilad Ben-Yossef commit c5f39d07860c35e5e4c63188139465af790f86ce upstream. crypto_ahash_import() may be called either after crypto_ahash_init() or without such call.

[PATCH 4.14 69/75] usb: hub: Cycle HUB power when initialization fails

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mike Looijmans commit 973593a960ddac0f14f0d8877d2d0abe0afda795 upstream. Sometimes the USB device gets confused about the state of the initialization and the

[PATCH 4.14 67/75] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dominik Behr commit ea4d5a270b57fa8d4871f372ca9b97b7697fdfda upstream. To avoid hanging userspace components that might have been waiting on the active fences of the

[PATCH 4.14 51/75] usbip: tools: Install all headers needed for libusbip development

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings [ Upstream commit c15562c0dcb2c7f26e891923b784cf1926b8c833 ] usbip_host_driver.h now depends on several additional headers, which need to be installed

Re: [PATCH 4.9 038/109] dmaengine: stm32-dma: Fix null pointer dereference in stm32_dma_tx_status

Acked-by: Pierre-Yves MORDRET ~PYM~ On 12/07/2017 02:18 PM, Ludovic BARRE wrote: > with Pierre Yves mail it's better ;-) > > On 12/07/2017 02:04 PM, Ludovic BARRE wrote: >> add Pierre-yves Mordret >> >> acked-by: Ludovic BARRE >> >> On

[PATCH 4.14 53/75] staging: fsl-mc/dpio: Fix incorrect comparison

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ioana Radulescu [ Upstream commit 8dabf52ffb6445fa5bcc8b6d2ecb615f60d0dd12 ] For some dpio functions, a cpu id parameter value of -1 is valid and means "any". But

Re: [PATCH V7 02/12] clk: sprd: Add common infrastructure

Dear Chunyan, On Thu, Dec 7, 2017 at 1:57 PM, Chunyan Zhang wrote: > Added Spreadtrum's clock driver framework together with common > structures and interface functions. > > Signed-off-by: Chunyan Zhang > --- /dev/null > +++

Re: rsi: fix memory leak on buf and usb_reg_buf

Colin Ian King wrote: > From: Colin Ian King > > In the cases where len is too long, the error return path fails to > kfree allocated buffers buf and usb_reg_buf. The simplest fix is to > perform the sanity check on len before the

[PATCH 4.14 31/75] perf/core: Fix __perf_read_group_add() locking

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra [ Upstream commit a9cd8194e1e6bd09619954721dfaf0f94fe2003e ] Event timestamps are serialized using ctx->lock, make sure to hold it over reading all

[PATCH 4.14 30/75] hwmon: (pmbus/core) Prevent unintentional setting of page to 0xFF

4.14-stable review patch. If anyone has any objections, please let me know. -- From: "Edward A. James" [ Upstream commit 6dcf2fb5e8db3704f50af1f198256cb4e2453f8b ] The pmbus core may call read/write word data functions with a page value of -1, intending

Re: [PATCH] perf: qcom_l2_pmu: don't allow guest access

On Wed, Dec 06, 2017 at 04:19:24PM -0500, Leeder, Neil wrote: > On 12/6/2017 11:11 AM, Mark Rutland wrote: > > On Wed, Dec 06, 2017 at 10:55:33AM -0500, Neil Leeder wrote: > >> Guests cannot access IMPDEF system registers, which are used > >> by this driver. Disable the driver if it's running in a

[PATCH 4.14 11/75] USB: serial: option: add Quectel BG96 id

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Sjoholm commit c654b21ede93845863597de9ad774fd30db5f2ab upstream. Quectel BG96 is an Qualcomm MDM9206 based IoT modem, supporting both CAT-M and NB-IoT. Tested

[PATCH 4.4 20/49] usbip: tools: Install all headers needed for libusbip development

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings [ Upstream commit c15562c0dcb2c7f26e891923b784cf1926b8c833 ] usbip_host_driver.h now depends on several additional headers, which need to be installed

[PATCH 4.14 01/75] drm/fsl-dcu: avoid disabling pixel clock twice on suspend

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Agner commit 9306e996574f7f57136a62e49cd0075f85713623 upstream. With commit 0a70c998d0c5 ("drm/fsl-dcu: enable pixel clock when enabling CRTC") the pixel clock is

Re: [PATCH] libsas: flush pending destruct work in sas_unregister_domain_devices()

On 28/11/2017 17:04, Cong Wang wrote: On Tue, Nov 28, 2017 at 3:18 AM, John Garry wrote: On 28/11/2017 08:20, Johannes Thumshirn wrote: On Mon, Nov 27, 2017 at 04:24:45PM -0800, Cong Wang wrote: We saw dozens of the following kernel waring: WARNING: CPU: 0 PID: 705

[PATCH 4.4 14/49] usb: dwc2: Error out of dwc2_hsotg_ep_disable() if were in host mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: John Stultz [ Upstream commit 9b481092c2a31a6b630aff9c28f0145bf6683787 ] We've found that while in host mode, using Android, if one runs the command: stop adbd The

[PATCH 4.4 40/49] Revert "ocfs2: should wait dio before inode lock in ocfs2_setattr()"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit c4baa4a5870cb02f713def1620052bfca7a82bbb which is commit 28f5a8a7c033cbf3e32277f4cc9c6afd74f05300 upstream. It shouldn't be

[PATCH 4.4 03/49] uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7fee72d5e8f1e7b8d8212e28291b1a0243ecf2f1 upstream. We've been adding this as a quirk on a per device basis hoping that newer disk enclosures would do

Re: [RFC][PATCH] printk: add console_msg_format command line option

On Fri 2017-12-01 19:44:04, Sergey Senozhatsky wrote: > 0day and kernelCI automatically parse kernel log - basically some sort > of grepping using the pre-defined text patterns - in order to detect > and report regressions/errors. There are several sources they get the > kernel logs from: > > a)

[PATCH 4.4 08/49] ima: fix hash algorithm initialization

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Boshi Wang [ Upstream commit ebe7c0a7be92bbd34c6ff5b55810546a0ee05bee ] The hash_setup function always sets the hash_setup_done flag, even when the hash algorithm is

[PATCH 4.4 04/49] usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit e43a12f1793ae1fe006e26fe9327a8840a92233c upstream. KY-688 USB 3.1 Type-C Hub internally uses a Genesys Logic hub to connect to Realtek r8153.

[PATCH 4.4 05/49] serial: 8250_pci: Add Amazon PCI serial device ID

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matt Wilson commit 3bfd1300abfe3adb18e84a89d97a0e82a22124bb upstream. This device will be used in future Amazon EC2 instances as the primary serial port (i.e., data sent to

[PATCH 4.9 093/109] dma-buf/sw-sync: Fix locking around sync_timeline lists

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit d3862e44daa7a0c94d2f6193502a8c49379acfce upstream. The sync_pt were not adding themselves atomically to the timeline lists, corruption imminent.

[PATCH 4.9 095/109] dma-buf/sw_sync: move timeline_fence_ops around

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo Padovan commit 150b6a9d7d6fffb95c0a5349960a10569e8218b5 upstream. We are going to use timeline_fence_signaled() in a internal function in the next

Re: [PATCH V6 4/7] OF: properties: Implement get_match_data() callback

Hi, On Tue, 5 Dec 2017 12:04:49 -0500 Sinan Kaya wrote: > Now that we have a get_match_data() callback as part of the firmware node, > implement the OF specific piece for it. > > Signed-off-by: Sinan Kaya > --- > drivers/of/property.c | 7 +++ > 1 file changed, 7

[PATCH 4.9 086/109] xen-netback: vif counters from int/long to u64

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mart van Santen [ Upstream commit ebf692f85ff78092cd238166d8d7ec51419f9c02 ] This patch fixes an issue where the type of counters in the queue(s) and interface are not in

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

Hi! > >> (It does seem unfortunate that the man page cannot help the programmer > >> actually write correct code here. He or she is forced to read the kernel > >> implementation, in order to figure out the true alignment rules. I was > >> hoping we could avoid that.) > > > > It would be nice if

[PATCH 4.9 050/109] net: qrtr: Mark buf as little endian

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd [ Upstream commit 3512a1ad56174308a9fd3e10f4b1e3e152e9ec01 ] Failure to mark this pointer as __le32 causes checkers like sparse to complain:

[PATCH 4.9 052/109] mac80211: calculate min channel width correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg [ Upstream commit 96aa2e7cf126773b16c6c19b7474a8a38d3c707e ] In the current minimum chandef code there's an issue in that the recalculation can happen

Re: [PATCH 4.9 037/109] dmaengine: stm32-dma: Set correct args number for DMA request from DT

I did check. DT Bindings are aligned with the patch. In fact the patch was an alignment with DT Bindings. For DT : 47c8a5035b68 ARM: dts: stm32: Add DMA support for STM32F746 SoC 01d281b6e4a2 ARM: dts: stm32: Add DMA support for STM32H743 SoC Nonetheless I can ack the patch Acked-by:

Re: [PATCH] perf evsel: Enable ignore_missing_thread for pid option

Hi Jiri, Thanks for your review! I've sent a patch V2 to address these issues. On 2017/12/6 20:59, Jiri Olsa wrote: On Tue, Dec 05, 2017 at 05:03:33PM +0800, Mengting Zhang wrote: While monitoring a multithread process with pid option, perf sometimes may return sys_perf_event_open failure

[PATCH 4.9 036/109] l2tp: take remote address into account in l2tp_ip and l2tp_ip6 socket lookups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit a9b2dff80be979432484afaf7f8d8e73f9e8838a ] For connected sockets, __l2tp_ip{,6}_bind_lookup() needs to check the remote IP when looking

[PATCH 4.9 037/109] dmaengine: stm32-dma: Set correct args number for DMA request from DT

4.9-stable review patch. If anyone has any objections, please let me know. -- From: M'boumba Cedric Madianga [ Upstream commit 7e96304d99477de1f70db42035071e56439da817 ] This patch sets the right number of arguments to be used for DMA clients which

[PATCH 4.9 028/109] sysrq : fix Show Regs call trace on ARM

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jibin Xu [ Upstream commit b00bebbc301c8e1f74f230dc82282e56b7e7a6db ] When kernel configuration SMP,PREEMPT and DEBUG_PREEMPT are enabled, echo 1

[PATCH 4.9 006/109] mm, oom_reaper: gather each vma to prevent leaking TLB entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wang Nan commit 687cb0884a714ff484d038e9190edc874edcf146 upstream. tlb_gather_mmu(, mm, 0, -1) means gathering the whole virtual memory space. In this case, tlb->fullmm

[PATCH v5 net-next] net/tcp: trace all TCP/IP state transition with tcp_set_state tracepoint

The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other transitions are not traced with tcp_set_state tracepoint. In order to trace the whole tcp lifespans, two helpers are introduced, void sk_set_state(struct sock *sk, int state); void sk_state_store(struct sock *sk, int newstate);

[PATCH 4.9 014/109] selftests/x86/ldt_get: Add a few additional tests for limits

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski [ Upstream commit fec8f5ae1715a01c72ad52cb2ecd8aacaf142302 ] We weren't testing the .limit and .limit_in_pages fields very well. Add more tests. This

[PATCH] drm/i915: add FTRACE dependency for DRM_I915_TRACE_GEM

The new trace option gratuitously added a 'select TRACING' statement, which now causes build failures in other code that assumed tracepoints were only available with FTRACE: ERROR: "__tracepoint_ucsi_command" [drivers/usb/typec/ucsi/typec_ucsi.ko] undefined! ERROR:

[PATCH AUTOSEL for 3.18 58/59] macvlan: Only deliver one copy of the frame to the macvlan interface

From: Alexander Duyck [ Upstream commit dd6b9c2c332b40f142740d1b11fb77c653ff98ea ] This patch intoduces a slight adjustment for macvlan to address the fact that in source mode I was seeing two copies of any packet addressed to the macvlan interface being delivered

[PATCH AUTOSEL for 3.18 05/59] NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)

From: NeilBrown [ Upstream commit 928c6fb3a9bfd6c5b287aa3465226add551c13c0 ] Current code will return 1 if the version is supported, and -1 if it isn't. This is confusing and inconsistent with the one place where this is used. So change to return 1 if it is supported, and zero

[PATCH AUTOSEL for 4.9 020/156] NFSD: fix nfsd_minorversion(.., NFSD_AVAIL)

From: NeilBrown [ Upstream commit 928c6fb3a9bfd6c5b287aa3465226add551c13c0 ] Current code will return 1 if the version is supported, and -1 if it isn't. This is confusing and inconsistent with the one place where this is used. So change to return 1 if it is supported, and zero

[PATCH v4 03/15] dt-bindings: display: sun4i-drm: Add LVDS properties

Some clocks and resets supposed to drive the LVDS logic in the display engine have been overlooked when the driver was first introduced. Add those additional resources to the binding, and we'll deal with the ABI stability in the code. Reviewed-by: Rob Herring Signed-off-by:

[PATCH v4 09/15] drm/sun4i: Add A83T support

Add support for the A83T display pipeline. Reviewed-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard --- drivers/gpu/drm/sun4i/sun4i_drv.c | 1 + drivers/gpu/drm/sun4i/sun4i_tcon.c | 5 + drivers/gpu/drm/sun4i/sun8i_mixer.c | 11

[PATCH AUTOSEL for 4.9 011/156] net: bcmgenet: reserved phy revisions must be checked first

From: Doug Berger [ Upstream commit eca4bad73409aedc6ff22f823c18b67a4f08c851 ] The reserved gphy_rev value of 0x01ff must be tested before the old or new scheme for GPHY major versioning are tested, otherwise it will be treated as 0xff00 according to the old scheme. Fixes:

Re: [RFC][PATCH] printk: add console_msg_format command line option

On (12/07/17 16:45), Petr Mladek wrote: [.,] > > hmm... `dmesg -S --raw' doesn't show anything on my system. `dmesg --raw' > > matches the console_msg_format=syslog. > > Huh, I am confused now. I thought that I saw the extended, /dev/kmsg - like, > output with "dmesg --raw" but I do not see it

Re: [PATCH v11 0/6] Add support for Qualcomm A53 CPU clock

On 12/06/2017 11:08 PM, Rob Herring wrote: > On Tue, Dec 05, 2017 at 05:46:55PM +0200, Georgi Djakov wrote: >> This patchset adds support for the A53 CPU clock on MSM8916 platforms >> and allows scaling of the CPU frequency on msm8916 based platforms. >> >> Changes since v10

[PATCH v4 12/15] ARM: dts: sun8i: a83t: Add LVDS pins group

The A83T has an LVDS bus that can be connected to a panel or a bridge. Add the pinctrl group for it. Reviewed-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun8i-a83t.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff

[PATCH v4 00/15] drm/sun4i: Add A83t LVDS support

Hi, Here is an attempt at supporting the LVDS output in our DRM driver. This has been tested on the A83T (with DE2), but since everything is basically in the TCON, it should also be usable on the older SoCs with minor modifications. This was the occasion to refactor a bunch of things. The most

[PATCH AUTOSEL for 4.14 131/135] lightnvm: pblk: protect line bitmap while submitting meta io

From: Rakesh Pandit [ Upstream commit e57903fd972a398b7140d0bc055714e13a0e58c5 ] It seems pblk_dealloc_page would race against pblk_alloc_pages for line bitmap for sector allocation.The chances are very low but might as well protect the bitmap properly. Signed-off-by: Rakesh

[PATCH AUTOSEL for 4.9 021/156] NFSD: fix nfsd_reset_versions for NFSv4.

From: NeilBrown [ Upstream commit 800a938f0bf9130c8256116649c0cc5806bfb2fd ] If you write "-2 -3 -4" to the "versions" file, it will notice that no versions are enabled, and nfsd_reset_versions() is called. This enables all major versions, not no minor versions. So we lose the

[PATCH AUTOSEL for 4.9 010/156] net: bcmgenet: correct MIB access of UniMAC RUNT counters

From: Doug Berger [ Upstream commit 1ad3d225e5a40ca6c586989b4baaca710544c15a ] The gap between the Tx status counters and the Rx RUNT counters is now being added to allow correct reporting of the registers. Fixes: 1c1008c793fa ("net: bcmgenet: add main driver file")

Re: [PATCH 1/2] epoll: use the waitqueue lock to protect ep->wq

On 12/06/2017 06:52 PM, Christoph Hellwig wrote: > The eoll code currently always uses the unlocked waitqueue helpers for > ep->wq, but instead of holding the lock inside the waitqueue around these > calls, as expected by the epoll code uses its own lock. Given that the > waitqueue is not exposed

[PATCH AUTOSEL for 3.18 53/59] raid5: Set R5_Expanded on parity devices as well as data.

From: NeilBrown [ Upstream commit 235b6003fb28f0dd8e7ed8fbdb088bb548291766 ] When reshaping a fully degraded raid5/raid6 to a larger nubmer of devices, the new device(s) are not in-sync and so that can make the newly grown stripe appear to be "failed". To avoid this, we set the

[PATCH AUTOSEL for 3.18 08/59] net: wimax/i2400m: fix NULL-deref at probe

From: Johan Hovold [ Upstream commit 6e526fdff7be4f13b24f929a04c0e9ae6761291e ] Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer or accessing memory beyond the endpoint array should a malicious device lack the expected endpoints. The endpoints

Re: [PATCH v9 1/8] drm/tilcdc: ensure nonatomic iowrite64 is not used

On 12/06/17 01:30, Logan Gunthorpe wrote: > Add a check to ensure iowrite64 is only used if it is atomic. > > It was decided in [1] that the tilcdc driver should not be using an > atomic operation (so it was left out of this patchset). However, it turns > out that through the drm code, a

[PATCH AUTOSEL for 3.18 13/59] sched/deadline: Use deadline instead of period when calculating overflow

From: "Steven Rostedt (VMware)" [ Upstream commit 2317d5f1c34913bac5971d93d69fb6c31bb74670 ] I was testing Daniel's changes with his test case, and tweaked it a little. Instead of having the runtime equal to the deadline, I increased the deadline ten fold. Daniel's test

[PATCH AUTOSEL for 3.18 14/59] drm/radeon: reinstate oland workaround for sclk

From: Alex Deucher [ Upstream commit 66822d815ae61ecb2d9dba9031517e8a8476969d ] Higher sclks seem to be unstable on some boards. bug: https://bugs.freedesktop.org/show_bug.cgi?id=100222 Signed-off-by: Alex Deucher Cc:

[PATCH AUTOSEL for 3.18 38/59] iscsi-target: fix memory leak in lio_target_tiqn_addtpg()

From: tangwenji [ Upstream commit 12d5a43b2dffb6cd28062b4e19024f7982393288 ] tpg must free when call core_tpg_register() return fail Signed-off-by: tangwenji Signed-off-by: Nicholas Bellinger Signed-off-by: Sasha Levin

[PATCH AUTOSEL for 3.18 39/59] target:fix condition return in core_pr_dump_initiator_port()

From: tangwenji [ Upstream commit 24528f089d0a444070aa4f715ace537e8d6bf168 ] When is pr_reg->isid_present_at_reg is false,this function should return. This fixes a regression originally introduced by: commit d2843c173ee53cf4c12e7dfedc069a5bc76f0ac5 Author: Andy

Re: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer()

On Thu, 2017-12-07 at 10:12 -0500, Alan Stern wrote: > The real problem is that the kernel development community doesn't have > a fixed policy on how to handle memory allocation errors. [] > If there was one agreed-upon policy, then we could definitively point > to old code and say "That's wrong,

[PATCH AUTOSEL for 3.18 20/59] afs: Populate and use client modification time

From: Marc Dionne [ Upstream commit ab94f5d0dd6fd82e7eeca5e7c8096eaea0a0261f ] The inode timestamps should be set from the client time in the status received from the server, rather than the server time which is meant for internal server use. Set AFS_SET_MTIME and

Re: [PATCH] mm: terminate shrink_slab loop if signal is pending

On Thu 07-12-17 07:46:07, Suren Baghdasaryan wrote: > I'm, terribly sorry. My original code was checking for additional > condition which I realized is not useful here because it would mean > the signal was already processed. Should have missed the error while > removing it. Will address Michal's

[PATCH AUTOSEL for 3.18 19/59] afs: Fix the maths in afs_fs_store_data()

From: David Howells [ Upstream commit 146a1192783697810b63a1e41c4d59fc93387340 ] afs_fs_store_data() works out of the size of the write it's going to make, but it uses 32-bit unsigned subtraction in one place that gets automatically cast to loff_t. However, if to < offset,

[PATCH AUTOSEL for 4.4 090/101] raid5: Set R5_Expanded on parity devices as well as data.

From: NeilBrown [ Upstream commit 235b6003fb28f0dd8e7ed8fbdb088bb548291766 ] When reshaping a fully degraded raid5/raid6 to a larger nubmer of devices, the new device(s) are not in-sync and so that can make the newly grown stripe appear to be "failed". To avoid this, we set the

Re: Multiple oom_reaper BUGs: unmap_page_range racing with exit_mmap

On Fri 08-12-17 00:44:11, Tetsuo Handa wrote: > Michal Hocko wrote: > > David, could you test with this patch please? > > Even if this patch solved David's case, you need to update > >* tsk_is_oom_victim() cannot be set from under us >* either because current->mm is already set

[PATCH AUTOSEL for 4.4 096/101] scsi: bfa: integer overflow in debugfs

From: Dan Carpenter [ Upstream commit 3e351275655d3c84dc28abf170def9786db5176d ] We could allocate less memory than intended because we do: bfad->regdata = kzalloc(len << 2, GFP_KERNEL); The shift can overflow leading to a crash. This is debugfs code so the

[PATCH AUTOSEL for 4.4 101/101] ath9k: fix tx99 potential info leak

From: Miaoqing Pan [ Upstream commit ee0a47186e2fa9aa1c56cadcea470ca0ba8c8692 ] When the user sets count to zero the string buffer would remain completely uninitialized which causes the kernel to parse its own stack data, potentially leading to an info leak. In addition

[PATCH AUTOSEL for 4.4 099/101] RDMA/cma: Avoid triggering undefined behavior

From: Bart Van Assche [ Upstream commit c0b64f58e8d49570aa9ee55d880f92c20ff0166b ] According to the C standard the behavior of computations with integer operands is as follows: * A computation involving unsigned operands can never overflow, because a result that cannot

Re: [PATCH] spi: sun6i: disable/unprepare clocks on remove

On Thu, Dec 07, 2017 at 03:04:53PM +0100, Tobias Jordan wrote: > sun6i_spi_probe() uses sun6i_spi_runtime_resume() to prepare/enable > clocks, so sun6i_spi_remove() should use sun6i_spi_runtime_suspend() to > disable/unprepare them if we're not suspended. > Replacing pm_runtime_disable() by

[PATCH AUTOSEL for 4.4 058/101] dmaengine: ti-dma-crossbar: Correct am335x/am43xx mux value type

From: Peter Ujfalusi [ Upstream commit 288e7560e4d3e259aa28f8f58a8dfe63627a1bf6 ] The used 0x1f mask is only valid for am335x family of SoC, different family using this type of crossbar might have different number of electable events. In case of am43xx family 0x3f mask

[PATCH AUTOSEL for 4.4 064/101] platform/x86: sony-laptop: Fix error handling in sony_nc_setup_rfkill()

From: Markus Elfring [ Upstream commit f6c8a317ab208aee223776327c06f23342492d54 ] Source code review for a specific software refactoring showed the need for another correction because the error code "-1" was returned so far if a call of the function

[PATCH AUTOSEL for 4.4 100/101] IB/ipoib: Grab rtnl lock on heavy flush when calling ndo_open/stop

From: Alex Vesker [ Upstream commit b4b678b06f6eef18bff44a338c01870234db0bc9 ] When ndo_open and ndo_stop are called RTNL lock should be held. In this specific case ipoib_ib_dev_open calls the offloaded ndo_open which re-sets the number of TX queue assuming RTNL lock is

[PATCH AUTOSEL for 4.4 066/101] iscsi-target: fix memory leak in lio_target_tiqn_addtpg()

From: tangwenji [ Upstream commit 12d5a43b2dffb6cd28062b4e19024f7982393288 ] tpg must free when call core_tpg_register() return fail Signed-off-by: tangwenji Signed-off-by: Nicholas Bellinger Signed-off-by: Sasha Levin

[PATCH AUTOSEL for 4.4 070/101] crypto: tcrypt - fix buffer lengths in test_aead_speed()

From: Robert Baronescu [ Upstream commit 7aacbfcb331ceff3ac43096d563a1f93ed46e35e ] Fix the way the length of the buffers used for encryption / decryption are computed. For e.g. in case of encryption, input buffer does not contain an authentication tag. Signed-off-by:

[PATCH AUTOSEL for 4.4 062/101] powerpc/opal: Fix EBUSY bug in acquiring tokens

From: "William A. Kennington III" [ Upstream commit 71e24d7731a2903b1ae2bba2b2971c654d9c2aa6 ] The current code checks the completion map to look for the first token that is complete. In some cases, a completion can come in but the token can still be on lease to the caller

[PATCH AUTOSEL for 4.4 044/101] perf symbols: Fix symbols__fixup_end heuristic for corner cases

From: Daniel Borkmann [ Upstream commit e7ede72a6d40cb3a30c087142d79381ca8a31dab ] The current symbols__fixup_end() heuristic for the last entry in the rb tree is suboptimal as it leads to not being able to recognize the symbol in the call graph in a couple of corner

[PATCH AUTOSEL for 4.4 065/101] target/iscsi: Fix a race condition in iscsit_add_reject_from_cmd()

From: Bart Van Assche [ Upstream commit cfe2b621bb18d86e93271febf8c6e37622da2d14 ] Avoid that cmd->se_cmd.se_tfo is read after a command has already been freed. Signed-off-by: Bart Van Assche Cc: Christoph Hellwig Cc: Mike Christie

[PATCH AUTOSEL for 4.4 061/101] netfilter: ipvs: Fix inappropriate output of procfs

From: KUWAZAWA Takuya [ Upstream commit c5504f724c86ee925e7ffb80aa342cfd57959b13 ] Information about ipvs in different network namespace can be seen via procfs. How to reproduce: # ip netns add ns01 # ip netns add ns02 # ip netns exec ns01 ip a add dev lo

[PATCH AUTOSEL for 4.9 145/156] rtl8188eu: Fix a possible sleep-in-atomic bug in rtw_createbss_cmd

From: Jia-Ju Bai [ Upstream commit 2bf9806d4228f7a6195f8e03eda0479d2a93b411 ] The driver may sleep under a spinlock, and the function call path is: rtw_surveydone_event_callback(acquire the spinlock) rtw_createbss_cmd kzalloc(GFP_KERNEL) --> may sleep To fix it,

[PATCH AUTOSEL for 4.9 156/156] ath9k: fix tx99 potential info leak

From: Miaoqing Pan [ Upstream commit ee0a47186e2fa9aa1c56cadcea470ca0ba8c8692 ] When the user sets count to zero the string buffer would remain completely uninitialized which causes the kernel to parse its own stack data, potentially leading to an info leak. In addition

[PATCH AUTOSEL for 4.9 155/156] icmp: don't fail on fragment reassembly time exceeded

From: Matteo Croce [ Upstream commit 258bbb1b0e594ad5f5652cb526b3c63e6a7fad3d ] The ICMP implementation currently replies to an ICMP time exceeded message (type 11) with an ICMP host unreachable message (type 3, code 1). However, time exceeded messages can either represent

[PATCH AUTOSEL for 4.9 154/156] IB/ipoib: Grab rtnl lock on heavy flush when calling ndo_open/stop

From: Alex Vesker [ Upstream commit b4b678b06f6eef18bff44a338c01870234db0bc9 ] When ndo_open and ndo_stop are called RTNL lock should be held. In this specific case ipoib_ib_dev_open calls the offloaded ndo_open which re-sets the number of TX queue assuming RTNL lock is

[PATCH AUTOSEL for 4.9 122/156] bcache: explicitly destroy mutex while exiting

From: Liang Chen [ Upstream commit 330a4db89d39a6b43f36da16824eaa7a7509d34d ] mutex_destroy does nothing most of time, but it's better to call it to make the code future proof and it also has some meaning for like mutex debug. As Coly pointed out in a previous

[PATCH AUTOSEL for 4.9 126/156] btrfs: tests: Fix a memory leak in error handling path in 'run_test()'

From: Christophe JAILLET [ Upstream commit 9ca2e97fa3c3216200afe35a3b111ec51cc796d2 ] If 'btrfs_alloc_path()' fails, we must free the resources already allocated, as done in the other error handling paths in this function. Signed-off-by: Christophe JAILLET

[PATCH AUTOSEL for 4.9 125/156] arm64: prevent regressions in compressed kernel image size when upgrading to binutils 2.27

From: Nick Desaulniers [ Upstream commit fd9dde6abcb9bfe6c6bee48834e157999f113971 ] Upon upgrading to binutils 2.27, we found that our lz4 and gzip compressed kernel images were significantly larger, resulting is 10ms boot time regressions. As noted by Rahul: "aarch64

[PATCH AUTOSEL for 4.9 138/156] tty fix oops when rmmod 8250

From: nixiaoming [ Upstream commit c79dde629d2027ca80329c62854a7635e623d527 ] After rmmod 8250.ko tty_kref_put starts kwork (release_one_tty) to release proc interface oops when accessing driver->driver_name in proc_tty_unregister_driver Use jprobe, found

[PATCH AUTOSEL for 4.9 128/156] nvme: use kref_get_unless_zero in nvme_find_get_ns

From: Christoph Hellwig [ Upstream commit 2dd4122854f697afc777582d18548dded03ce5dd ] For kref_get_unless_zero to protect against lookup vs free races we need to use it in all places where we aren't guaranteed to already hold a reference. There is no such guarantee in

[PATCH AUTOSEL for 4.9 112/156] mm: Handle 0 flags in _calc_vm_trans() macro

From: Jan Kara [ Upstream commit 592e254502041f953e84d091eae2c68cba04c10b ] _calc_vm_trans() does not handle the situation when some of the passed flags are 0 (which can happen if these VM flags do not make sense for the architecture). Improve the _calc_vm_trans() macro to return

Re: [PATCH v8 2/2] ARM: dts: TS-4600: add basic device tree

Hi Fabio On 11/26/2017 02:39 PM, Fabio Estevam wrote: > Hi Sebastien, > > On Thu, Nov 23, 2017 at 7:04 PM, Sebastien Bourdelin > wrote: > >> + reg_vddio_sd0: regulator-vddio-sd0 { >> + compatible = "regulator-fixed"; >> +

[PATCH AUTOSEL for 4.9 096/156] PCI: Do not allocate more buses than available in parent

From: Mika Westerberg [ Upstream commit a20c7f36bd3d20d245616ae223bb9d05dfb6f050 ] One can ask more buses to be reserved for hotplug bridges by passing pci=hpbussize=N in the kernel command line. If the parent bus does not have enough bus space available we

[PATCH AUTOSEL for 4.9 117/156] ppp: Destroy the mutex when cleanup

From: Gao Feng [ Upstream commit f02b2320b27c16b644691267ee3b5c110846f49e ] The mutex_destroy only makes sense when enable DEBUG_MUTEX. For the good readbility, it's better to invoke it in exit func when the init func invokes mutex_init. Signed-off-by: Gao Feng

[PATCH AUTOSEL for 4.9 101/156] platform/x86: intel_punit_ipc: Fix resource ioremap warning

From: Kuppuswamy Sathyanarayanan [ Upstream commit 6cc8cbbc8868033f279b63e98b26b75eaa0006ab ] For PUNIT device, ISPDRIVER_IPC and GTDDRIVER_IPC resources are not mandatory. So when PMC IPC driver creates a PUNIT device, if these resources are not

[PATCH AUTOSEL for 4.9 063/156] afs: Better abort and net error handling

From: David Howells [ Upstream commit 70af0e3bd65142f9e674961c975451638a7ce1d5 ] If we receive a network error, a remote abort or a protocol error whilst we're still transmitting data, make sure we return an appropriate error to the caller rather than ESHUTDOWN or

[PATCH AUTOSEL for 4.9 095/156] powerpc/powernv/cpufreq: Fix the frequency read by /proc/cpuinfo

From: Shriya [ Upstream commit cd77b5ce208c153260ed7882d8910f2395bfaabd ] The call to /proc/cpuinfo in turn calls cpufreq_quick_get() which returns the last frequency requested by the kernel, but may not reflect the actual frequency the processor is running at. This

[PATCH AUTOSEL for 4.9 100/156] powerpc/ipic: Fix status get and status clear

From: Christophe Leroy [ Upstream commit 6b148a7ce72a7f87c81cbcde48af014abc0516a9 ] IPIC Status is provided by register IPIC_SERSR and not by IPIC_SERMR which is the mask register. Signed-off-by: Christophe Leroy Signed-off-by: Michael

[PATCH AUTOSEL for 4.9 069/156] nvmet: confirm sq percpu has scheduled and switched to atomic

From: Sagi Grimberg [ Upstream commit d11ea004a458b982e19b188c386e25a9b66ec446 ] percpu_ref_kill is not enough to prevent subsequent percpu_ref_tryget_live from failing. Hence call perfcpu_ref_kill_confirm to make it safe. Reviewed-by: Christoph Hellwig

[PATCH AUTOSEL for 4.9 087/156] video: udlfb: Fix read EDID timeout

From: Ladislav Michl [ Upstream commit c98769475575c8a585f5b3952f4b5f90266f699b ] While usb_control_msg function expects timeout in miliseconds, a value of HZ is used. Replace it with USB_CTRL_GET_TIMEOUT and also fix error message which looks like: udlfb: Read EDID byte

[PATCH AUTOSEL for 4.9 108/156] iommu/amd: Limit the IOVA page range to the specified addresses

From: Gary R Hook [ Upstream commit b92b4fb5c14257c0e7eae291ecc1f7b1962e1699 ] The extent of pages specified when applying a reserved region should include up to the last page of the range, but not the page following the range. Signed-off-by: Gary R Hook

[PATCH AUTOSEL for 4.9 045/156] drm/radeon/si: add dpm quirk for Oland

From: Alex Deucher [ Upstream commit 0f424de1fd9bc4ab24bd1fe5430ab5618e803e31 ] OLAND 0x1002:0x6604 0x1028:0x066F 0x00 seems to have problems with higher sclks. Acked-by: Christian König Signed-off-by: Alex Deucher

[PATCH AUTOSEL for 4.9 058/156] afs: Flush outstanding writes when an fd is closed

From: David Howells [ Upstream commit 58fed94dfb17e89556b5705f20f90e5b2971b6a1 ] Flush outstanding writes in afs when an fd is closed. This is what NFS and CIFS do. Reported-by: Marc Dionne Signed-off-by: David Howells

<    7   8   9   10   11   12   13   14   15   16   >