[PATCH 4.4 089/163] ASoC: ssm4567: Reset device before regcache_sync()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lars-Peter Clausen commit 712a8038cc24dba668afe82f0413714ca87184e0 upstream. When the ssm4567 is powered up the driver calles regcache_sync() to restore the register map

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Mon, May 02, 2016 at 04:25:51PM -0700, Dan Williams wrote: > On Mon, May 2, 2016 at 4:04 PM, Dave Chinner wrote: > > On Mon, May 02, 2016 at 11:18:36AM -0400, Jeff Moyer wrote: > >> Dave Chinner writes: > >> > >> > On Mon, Apr 25, 2016 at 11:53:13PM

[PATCH 4.4 017/163] dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit 9567366fefddeaea4ed1d713270535d93a3b3c76 upstream. The READ_LOCK macro was incorrectly returning -EINVAL if dm_bm_is_read_only() was true -- it will

[PATCH 4.4 002/163] block: loop: fix filesystem corruption in case of aio/dio

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit a7297a6a3a3322b054592e8e988981d2f5f29cc4 upstream. Starting from commit e36f620428(block: split bios to max possible length), block core starts to split

Re: [PATCH 2/2] zram: user per-cpu compression streams

Hello Minchan, On (05/03/16 10:40), Minchan Kim wrote: > > > > ...hm... inc ->failed_writes? [..] > Okay, let's add the knob to the existing sysfs(There is no different > between sysfs and debugfs with point of userspace once they start to > use it) because no need to add new code to avoid such

[GIT PULL] clk fixes for v4.6-rc6

The following changes since commit 2aac7ddf9a410e3418c9cc69618f304550466793: clk: qcom: ipq4019: add some fixed clocks for ddrppl and fepll (2016-03-29 16:31:16 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git

[PATCH 4.4 020/163] debugfs: Make automount point inodes permanently empty

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Seth Forshee commit 87243deb88671f70def4c52dfa7ca7830707bd31 upstream. Starting with 4.1 the tracing subsystem has its own filesystem which is automounted in the

[PATCH 4.4 018/163] dm cache metadata: fix cmd_read_lock() acquiring write lock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ahmed Samy commit 6545b60baaf880b0cd29a5e89dbe745a06027e89 upstream. Commit 9567366fefdd ("dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros") uses

[PATCH 3.14 12/37] Input: gtco - fix crash on detecting device without endpoints

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 162f98dea487206d9ab79fc12ed64700667a894d upstream. The gtco driver expects at least one valid endpoint. If given malicious descriptors that specify 0

[PATCH 3.14 13/37] pinctrl: single: Fix pcs_parse_bits_in_pinctrl_entry to use __ffs than ffs

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Keerthy commit 56b367c0cd67d4c3006738e7dc9dda9273fd2bfe upstream. pcs_parse_bits_in_pinctrl_entry uses ffs which gives bit indices ranging from 1 to MAX. This leads to a

[PATCH 3.14 14/37] i2c: cpm: Fix build break due to incompatible pointer types

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 609d5a1b2b35bb62b4b3750396e55453160c2a17 upstream. Since commit ea8daa7b9784 ("kbuild: Add option to turn incompatible pointer check into error"),

[PATCH 3.14 10/37] crypto: gcm - Fix rfc4543 decryption crash

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu This bug has already bee fixed upstream since 4.2. However, it was fixed during the AEAD conversion so no fix was backported to the older kernels.

[PATCH 3.14 15/37] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using

Re: [PATCH v7 1/6] Shared library support

Hi Emese, 2016-05-03 2:56 GMT+09:00 Emese Revfy : > On Mon, 2 May 2016 14:03:00 +0900 > Masahiro Yamada wrote: > >> In the first place, >> I am wondering if we need to revive this documentation. >> What this commit is only interested in *.so

Re: [PATCH v2] cgroup: allow management of subtrees by new cgroup namespaces

On Tue, 2016-05-03 at 11:59 +1000, Aleksa Sarai wrote: > > > Change the mode of the cgroup directory for each cgroup > > > association, > > > allowing the process to create subtrees and modify the limits of > > > the > > > subtrees *without* allowing the process to modify its own limits. > > > Due

Re: [PATCH 2/2] zram: user per-cpu compression streams

On (05/03/16 11:20), Minchan Kim wrote: [..] > We are concerning about returing back to no per-cpu options but actually, > I don't want. If duplicate compression is really problem(But It's really > unlikely), we should try to solve the problem itself with different way > rather than roll-back to

Re: [PATCH] tracing: Don't display trigger file for events that don't have register func

On Mon, 2 May 2016 22:14:14 +0800 Chunyu Hu wrote: > Currently register function of the event will be called > through the 'reg' field of event class directly without > any check when seting up triggers. > > Triggers for events that don't support register through > debug fs

Re: [PATCH 1/2] : Make hash_64(), hash_ptr() return 32 bits

On Mon, May 2, 2016 at 6:59 PM, George Spelvin wrote: > > AFAICT, none of the string-hash functions outside of fs/ are > on particularly hot paths. The goal is deleting redundant code. Yes, agreed. >> We'll never get rid of "hash_name()", it not only has that '/' case, >>

RE: [PATCH] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

> From: Yongji Xie > Sent: Wednesday, April 27, 2016 8:22 PM > > Current vfio-pci implementation disallows to mmap > sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio > page may be shared with other BARs. This will cause some > performance issues when we passthrough a PCI device with

Re: [PATCH 1/2] ASoC: rockchip: i2s: separate capture and playback

Hi John, On 4/30/2016 15:00, John Keeping Wrote: Hi Enric, On Fri, Apr 29, 2016 at 04:59:27PM +0200, Enric Balletbo Serra wrote: 2015-12-09 11:32 GMT+01:00 John Keeping : If we only clear the tx/rx state when both are disabled it is not possible to start/stop one multiple

[REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

In testing with HiKey, we found that since commit 3f30b158eba5c60 (asix: On RX avoid creating bad Ethernet frames), we're seeing lots of noise during network transfers: [ 239.027993] asix 1-1.1:1.0 eth0: asix_rx_fixup() Data Header synchronisation was lost, remaining 988 [ 239.037310] asix

[PATCH 1/1] drivers: acpi: add CPU id to cooling device type of processor driver

Currently, in an ACPI based system, the processor driver registers one cooling device per processor. However, the cooling device type is the same for each processor. For example, on a system with four processors, the sysfs reading of each cooling device would look like: ebv@besouro ~ $ cat

Re: [PATCH 2/2] zram: user per-cpu compression streams

On (05/03/16 14:40), Minchan Kim wrote: [..] > > At least, we need sanity check code, still? > > Otherwise, user can echo "garbage" > /sys/xxx/max_comp_stream" and then > > cat /sys/xxx/max_comp_stream returns num_online_cpus. > > One more thing, > > User: > echo 4 > /sys/xxx/max_comp_stream" >

[PATCH 4.4 046/163] iwlwifi: mvm: fix memory leak in paging

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matti Gottlieb commit 7fdf9663261cc77a516396fec82cee8a8ea07e76 upstream. Currently paging download buffer is freed during the the unloading of the opmode which

Re: [PATCH V2 2/7] PM / OPP: Mark cpumask as const in dev_pm_opp_set_sharing_cpus()

On 02-05-16, 17:43, Stephen Boyd wrote: > On 04/27, Viresh Kumar wrote: > > dev_pm_opp_set_sharing_cpus() isn't supposed to update the cpumask > > passed as its parameter, and so it should always have been marked > > 'const'. > > > > Do it now. > > > > Signed-off-by: Viresh Kumar

[PATCH 3.14 21/37] USB: usbip: fix potential out-of-bounds write

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ignat Korchagin commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream. Fix potential out-of-bounds write to urb->transfer_buffer usbip handles network

[PATCH 3.14 01/37] ARM: OMAP2+: hwmod: Fix updating of sysconfig register

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream. Commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle when necessary") talks about

[PATCH 3.14 20/37] workqueue: fix ghost PENDING flag while doing MQ IO

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Roman Pen commit 346c09f80459a3ad97df1816d6d606169a51001a upstream. The bug in a workqueue leads to a stalled IO request in MQ ctx->rq_list with the following

Re: [PATCH v4 11/12] zsmalloc: page migration support

On Tue, May 03, 2016 at 10:42:18AM +0900, Chulmin Kim wrote: > On 2016년 05월 03일 09:43, Minchan Kim wrote: > >Good morning, Chulmin > > > >On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: > >>Hello, Minchan! > >> > >>On 2016년 04월 27일 16:48, Minchan Kim wrote: > >>>This patch introduces

[PATCH 3.14 24/37] misc/bmp085: Enable building as a module

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 50e6315dba721cbc24ccd6d7b299f1782f210a98 upstream. Commit 985087dbcb02 'misc: add support for bmp18x chips to the bmp085 driver' changed the BMP085

Re: Watchdog reset trigger for eMMC

Hi Marek On 2 May 2016 at 11:57, Marek Szyprowski wrote: > Hi Anand > > > On 2016-04-30 08:06, Anand Moon wrote: >> >> Hi All, >> >> Using microSD card when I try to write into /dev/watchdog device >> it triggers reboot of the board after timer expires. >> >>

Re: [PATCH v10 1/3] gpio: dwapb: remove name from dwapb_port_property

在 4/29/2016 5:22 PM, Linus Walleij 写道: > On Thu, Apr 28, 2016 at 11:32 AM, Jiang Qiu wrote: > >> This patch removed the name property from dwapb_port_property. >> The name property is redundant, since we can get this info >> from dwapb_gpio dev node. >> >> Reviewed-by: Andy

Re: [PATCH 1/1] simplified security.nscapability xattr

"Andrew G. Morgan" writes: > On 2 May 2016 6:04 p.m., "Eric W. Biederman" > wrote: >> >> "Serge E. Hallyn" writes: >> >> > On Tue, Apr 26, 2016 at 03:39:54PM -0700, Kees Cook wrote: >> >> On Tue, Apr 26, 2016 at 3:26 PM, Serge E.

Re: [PATCH 2/2] zram: user per-cpu compression streams

On (05/03/16 14:23), Minchan Kim wrote: [..] > > - zram->max_comp_streams = num; > > - ret = len; > > -out: > > - up_write(>init_lock); > > - return ret; > > At least, we need sanity check code, still? > Otherwise, user can echo "garbage" > /sys/xxx/max_comp_stream" and then > cat

[PATCH 4.4 083/163] perf intel-pt: Fix segfault tracing transactions

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 1342e0b7a6c1a060c593037fbac9f4b717f1cb3b upstream. Tracing a workload that uses transactions gave a seg fault as follows: perf record -e

linux-next: manual merge of the vfs tree with the f2fs tree

Hi Al, Today's linux-next merge of the vfs tree got a conflict in: fs/f2fs/data.c between commit: 6bfc49197eba ("f2fs: issue cache flush on direct IO") from the f2fs tree and commit: c8b8e32d700f ("direct-io: eliminate the offset argument to ->direct_IO") from the vfs tree. I fixed

[PATCH 4.4 010/163] assoc_array: dont call compare_object() on a node

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jerome Marchand commit 8d4a2ec1e0b41b0cf9a0c5cd4511da7f8e4f3de2 upstream. Changes since V1: fixed the description and added KASan warning. In

[PATCH 4.4 024/163] sched/cgroup: Fix/cleanup cgroup teardown/init

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit 2f5177f0fd7e531b26d54633be62d1d4cb94621c upstream. The CPU controller hasn't kept up with the various changes in the whole cgroup initialization /

[PATCH 4.4 022/163] dmaengine: hsu: correct use of channel status register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 4f4bc0abff79dc9d7ccbd3143adbf8ad1f4fe6ab upstream. There is a typo in documentation regarding to descriptor empty bit (DESCE) which is

[PATCH 4.4 023/163] dmaengine: pxa_dma: fix the maximum requestor line

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Robert Jarzmik commit 6bab1c6afdca0371cfa957079b36b78d12dd2cf5 upstream. The current number of requestor lines is limited to 31. This was an error of a previous commit,

[PATCH 4.4 011/163] usb: xhci: applying XHCI_PME_STUCK_QUIRK to Intel BXT B0 host

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Rafal Redzimski commit 0d46faca6f887a849efb07c1655b5a9f7c288b45 upstream. Broxton B0 also requires XHCI_PME_STUCK_QUIRK. Adding PCI device ID for Broxton B and

[PATCH 4.4 021/163] dmaengine: dw: fix master selection

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit 3fe6409c23e2bee4b2b1b6d671d2da8daa15271c upstream. The commit 895005202987 ("dmaengine: dw: apply both HS interfaces and remove

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Tue, May 03, 2016 at 01:26:46AM +, Rudoff, Andy wrote: > > >> The takeaway is that msync() is 9-10x slower than userspace cache > >> management. > > > >An alternative viewpoint: that flushing clean cachelines is > >extremely expensive on Intel CPUs. ;) > > > >i.e. Same numbers, different

Re: [RESEND PATCH]nbd: fix might_sleep warning on socket shutdown

On Tue, May 3, 2016 at 5:45 AM, Greg KH wrote: > On Mon, May 02, 2016 at 08:58:34AM +0530, Pranay Srivastava wrote: >> Hi, >> >> Can the following patch be reviewed? I'm working on some more changes >> on top of this change, >> so it'll be really helpful if someone can

[RFC][RFP] LPC2016 Thermal MC

Linux-pm, As a continuation of the work done in 2015, I am proposing this year a micro conference (MC) to gather thermal interested parties to discuss improvements to the thermal subsystem [1]. Last year, I believe it was a success in terms of achieving the goal of creating awareness, however, I

Re: [PATCH v4 11/12] zsmalloc: page migration support

On Tue, May 03, 2016 at 09:43:59AM +0900, Minchan Kim wrote: > Good morning, Chulmin > > On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: > > Hello, Minchan! > > > > On 2016년 04월 27일 16:48, Minchan Kim wrote: > > >This patch introduces run-time migration feature for zspage. > > > > >

[PATCH 4.4 080/163] drm/amdkfd: uninitialized variable in dbgdev_wave_control_set_registers()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 93fce954427effee89e44a976299b15dd75b4bbc upstream. At the end of the function we expect "status" to be zero, but it's either -EINVAL or

[PATCH 4.4 077/163] pwm: brcmstb: Fix check of devm_ioremap_resource() return code

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit c5857e3f94ab2719dfac649a146cb5dd6f21fcf3 upstream. The change fixes potential oops while accessing iomem on invalid address if devm_ioremap_resource()

[PATCH 4.4 071/163] drm/radeon: fix vertical bars appear on monitor (v2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Prosyak commit 5d5b7803c49bbb01bdf4c6e95e8314d0515b9484 upstream. When crtc/timing is disabled on boot the dig block should be stopped in order ignore timing

[PATCH 4.4 073/163] drm/nouveau/gr/gf100: select a stream master to fixup tfb offset queries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs commit 28dca90533750c7e31e8641c3df426bad9c12941 upstream. Signed-off-by: Ben Skeggs Signed-off-by: Greg Kroah-Hartman

[PATCH 4.4 009/163] ARM: OMAP2+: hwmod: Fix updating of sysconfig register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit 3ca4a238106dedc285193ee47f494a6584b6fd2f upstream. Commit 127500ccb766f ("ARM: OMAP2+: Only write the sysconfig on idle when necessary") talks about

Re: [PATCH v4 11/12] zsmalloc: page migration support

On 2016년 05월 03일 09:43, Minchan Kim wrote: Good morning, Chulmin On Tue, May 03, 2016 at 08:33:16AM +0900, Chulmin Kim wrote: Hello, Minchan! On 2016년 04월 27일 16:48, Minchan Kim wrote: This patch introduces run-time migration feature for zspage. For migration, VM uses page.lru field so it

Re: [PATCH v7 1/6] Shared library support

Hi Emese, 2016-05-03 2:56 GMT+09:00 Emese Revfy : > On Mon, 2 May 2016 14:03:00 +0900 > Masahiro Yamada wrote: > >> In the first place, >> I am wondering if we need to revive this documentation. >> What this commit is only interested in *.so

Re: [PATCH 4/9] thermal: rockchip: handle the power sequence for tsadc controller

在 2016年04月28日 23:04, Eduardo Valentin 写道: On Thu, Apr 28, 2016 at 09:50:29AM +0800, Caesar Wang wrote: 在 2016年04月28日 07:48, Eduardo Valentin 写道: On Mon, Apr 18, 2016 at 11:35:56AM +0800, Caesar Wang wrote: + regmap_write(grf, GRF_TSADC_TESTBIT_L, GRF_TSADC_TSEN_PD_ON); +

Re: [PATCH 2/2] zram: user per-cpu compression streams

On (05/03/16 11:30), Sergey Senozhatsky wrote: > > We are concerning about returing back to no per-cpu options but actually, > > I don't want. If duplicate compression is really problem(But It's really > > unlikely), we should try to solve the problem itself with different way > > rather than

[PATCH] sched/debug: fix idle balance factors aren't printed out if w/o CONFIG_SCHEDSTATS

From: Wanpeng Li max_idle_balance_cost and avg_idle which used to capture short idle are not associated with schedstats, however, the information of these two factors are't printed out if w/o CONFIG_SCHEDSTATS. This patch fix it by moving max_idle_balance_cost and

Re: [PATCH 2/2] zram: user per-cpu compression streams

On Tue, May 03, 2016 at 01:29:02PM +0900, Sergey Senozhatsky wrote: > On (05/03/16 11:30), Sergey Senozhatsky wrote: > > > We are concerning about returing back to no per-cpu options but actually, > > > I don't want. If duplicate compression is really problem(But It's really > > > unlikely), we

Re: [PATCH 7/9] powerpc/powernv: Add platform support for stop instruction

> diff --git a/arch/powerpc/include/asm/cputable.h > b/arch/powerpc/include/asm/cputable.h > index df4fb5f..a4739a1 100644 > --- a/arch/powerpc/include/asm/cputable.h > +++ b/arch/powerpc/include/asm/cputable.h > @@ -205,6 +205,7 @@ enum { >  #define CPU_FTR_DABRX >

Re: [PATCH kernel v4 08/11] powerpc/powernv/ioda2: Export debug helper pe_level_printk()

There's one call to pr_warn() in pnv_npu_disable_bypass() that could arguably be converted to pe_warn(), but we can clean that up later as the patch looks fine and I'm assuming subsequent patches make use of these. Reviewed-By: Alistair Popple On Fri, 29 Apr 2016

Re: [PATCH kernel v4 08/11] powerpc/powernv/ioda2: Export debug helper pe_level_printk()

On Tue, 3 May 2016 15:46:33 Alistair Popple wrote: > There's one call to pr_warn() in pnv_npu_disable_bypass() that could arguably > be converted to pe_warn(), but we can clean that up later as the patch looks > fine and I'm assuming subsequent patches make use of these. And inevitably the

[PATCH 4.4 044/163] s390/pci: add extra padding to function measurement block

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Ott commit 9d89d9e61d361f3adb75e1aebe4bb367faf16cfa upstream. Newer machines might use a different (larger) format for function measurement blocks. To

[PATCH 4.4 043/163] cpufreq: intel_pstate: Fix processing for turbo activation ratio

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Srinivas Pandruvada commit 1becf03545a0859ceaaf9e8c2d9861882a71cb01 upstream. When the config TDP level is not nominal (level = 0), the MSR values for

[PATCH 4.4 081/163] drm/i915: Fixup the free space logic in ring_prepare

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Akash Goel commit d43f3ebf12f59c57782ec652da65ef61c2662b40 upstream. Currently for the case where there is enough space at the end of Ring buffer for accommodating only

[PATCH 4.4 045/163] iwlwifi: pcie: lower the debug level for RSA semaphore access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 9fc515bc9e735c10cd327f05c20f5ef69474188d upstream. IWL_INFO is not an error but still printed by default. "can't access the RSA semaphore

[PATCH 4.4 086/163] toshiba_acpi: Fix regression caused by hotkey enabling value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Azael Avalos commit a30b8f81d9d6fe24eab8a023794548b048f08e3c upstream. Commit 52cbae0127ad ("toshiba_acpi: Change default Hotkey enabling value") changed the hotkeys

Re: [PATCH 2/2] zram: user per-cpu compression streams

On Mon, May 02, 2016 at 06:21:57PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 17:28), Minchan Kim wrote: > [..] > > > aha... I misunderstood you. I thought you talked about the test results > > > in particular, not about zram stats in general. hm, given that we don't > > > close the door for

[PATCH 4.4 085/163] i2c: exynos5: Fix possible ABBA deadlock by keeping I2C clock prepared

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Javier Martinez Canillas commit 10ff4c5239a137abfc896ec73ef3d15a0f86a16a upstream. The exynos5 I2C controller driver always prepares and enables a clock before using it

[PATCH 4.4 084/163] i2c: cpm: Fix build break due to incompatible pointer types

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 609d5a1b2b35bb62b4b3750396e55453160c2a17 upstream. Since commit ea8daa7b9784 ("kbuild: Add option to turn incompatible pointer check into error"),

Re: [PATCH 3.16 106/217] sd: disable discard_zeroes_data for UNMAP

> "Ben" == Ben Hutchings writes: Ben> But if sd in 3.16 is wrongly promising that discard zeroes data, it Ben> really does need to be fixed somehow. If there's a regression on a particular device we should address that rather than dropping valid fixes from core SCSI

[PATCH 4.4 029/163] ALSA: hda - Dont trust the reported actual power state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 50fd4987c4f3c3ebf0ce94d932732011bbdc7c71 upstream. We've got a regression report that the recording on Mac with a cirrus codec doesn't work any longer. This

[PATCH 4.4 028/163] x86 EDAC, sb_edac.c: Repair damage introduced when "fixing" channel address

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit ff15e95c82768d589957dbb17d7eb7dba7904659 upstream. In commit: eb1af3b71f9d ("Fix computation of channel address") I switched the "sck_way" variable

[PATCH 4.4 003/163] x86/mce: Avoid using object after free in genpool

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit a3125494cff084b098c80bb36fbe2061ffed9d52 upstream. When we loop over all queued machine check error records to pass them to the registered notifiers we

[PATCH 4.4 025/163] arm64: Honour !PTE_WRITE in set_pte_at() for kernel mappings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit ac15bd63bbb24238f763ec5b24ee175ec301e8cd upstream. Currently, set_pte_at() only checks the software PTE_WRITE bit for user mappings when it sets

[PATCH 4.4 035/163] asm-generic/futex: Re-enable preemption in futex_atomic_cmpxchg_inatomic()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Romain Perier commit fba7cd681b6155e2d93e7862fcd6f970336b83c3 upstream. The recent decoupling of pagefault disable and preempt disable added an explicit

Re: [PATCH v3 1/2] cgroup: apply common ancestor cgroup.procs restriction in cgroupv1

So, you can't apply a new restriction like this retro-actively to cgroup v1 hierarchies. Okay, understood. I'll see if it's possible to make this change safe without adding restrictions to cgroupv1 hierarchies. -- Aleksa Sarai Software Engineer (Containers) SUSE Linux GmbH

[PATCH 4.4 030/163] ALSA: hda/realtek - Add ALC3234 headset mode for Optiplex 9020m

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bastien Nocera commit afecb146d8d8a60a1dde9cdf570c278649617fde upstream. The Optiplex 9020m with Haswell-DT processor needs a quirk for the headset jack at the front of the

[PATCH 4.4 006/163] ARM: dts: AM43x-epos: Fix clk parent for synctimer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lokesh Vutla commit cfe1580a6415bc37fd62d79eb8102a618f7650b2 upstream. commit 55ee7017ee31 ("arm: omap2: board-generic: use omap4_local_timer_init for AM437x") makes

[PATCH 4.4 004/163] kvm: x86: do not leak guest xcr0 into host interrupt handlers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Matlack commit fc5b7f3bf1e1414bd4e91db6918c85ace0c873a5 upstream. An interrupt handler that uses the fpu can kill a KVM VM, if it runs under the following

[PATCH 4.4 037/163] futex: Acknowledge a new waiter in counter before plist

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Davidlohr Bueso commit fe1bce9e2107ba3a8faffe572483b6974201a0e6 upstream. Otherwise an incoming waker on the dest hash bucket can miss the waiter adding itself to the plist

Re: [Xen-devel] efi_enabled(EFI_PARAVIRT) use

On 2016/5/2 18:45, Matt Fleming wrote: > On Sun, 01 May, at 10:36:51PM, Shannon Zhao wrote: >> So is there any other way you suggest? > > Would this work (compile tested but not runtime tested)? > > --- > > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c > index

[PATCH 4.4 031/163] ALSA: hda - Keep powering up ADCs on Cirrus codecs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit de3df8a986b635082a1d94bae2c361d043c57106 upstream. Although one weird behavior about the input path (inconsistent D0/D3 switch) on Cirrus CS420x codecs was

[PATCH 4.4 026/163] arm64: Update PTE_RDONLY in set_pte_at() for PROT_NONE permission

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit fdc69e7df3cb24f18a93192641786e5b7ecd1dfe upstream. The set_pte_at() function must update the hardware PTE_RDONLY bit depending on the state of

[PATCH 4.4 027/163] x86/mm/xen: Suppress hugetlbfs in PV guests

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 103f6112f253017d7062cd74d17f4a514ed4485c upstream. Huge pages are not normally available to PV guests. Not suppressing hugetlbfs use results in an endless

Re: mainline build: 896 warnings 1 failures (mainline/v4.6-rc5-224-gda9373d)

On Mon, May 2, 2016 at 12:24 AM, Arnd Bergmann wrote: > On Sunday 01 May 2016 16:19:53 Olof Johansson wrote: >> On Sun, May 1, 2016 at 2:26 PM, Olof's autobuilder wrote: >> > Here are the build results from automated periodic testing. >> > >> > The tree being

[PATCH] thermal: rockchip: use the usleep_range instead of udelay

Documentation/timers/timers-howto.txt recommends to use usleep_range on delays > 10usec. The usleep_range indeed reduces CPU load, since the udelay will busy wait for enough loop cycles to achieve the desired delay. Fixes commit b06c52db39fd ("thermal: rockchip: handle the power sequence for

linux-next: manual merge of the drm-misc tree with the drm-intel tree

Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/i915/intel_display.c between commits: f7e5838bb37d ("drm/i915: Simplify reset_counter handling during atomic modesetting") from the drm-intel tree and commit: 81072bfd13f2 ("drm/i915: Rename async

Re: [PATCH 1/1] ARM: dts: sunxi: Add a olinuxino-lime2-emmc

Hi, On Thu, Apr 28, 2016 at 3:19 PM, Olliver Schinagl wrote: > There are 3 kinds of OLinuXino Lime2 boards. > One without any on board storage, one with NAND storage and one with > eMMC storage. This patch adds the eMMC variant of boards. > > eMMC storage is different from a

Re: [PATCH] Make clocksource insert entry more efficiently

On 05/02/16 at 10:39P, John Stultz wrote: > On Mon, Apr 25, 2016 at 2:20 AM, Minfei Huang wrote: > > It is unnecessary to continue looping the list, if we find there is an > > entry that the value of rating is smaller than the new one. It is safe > > to be out the loop, because

[PATCH 4/6] mm/page_owner: introduce split_page_owner and replace manual handling

From: Joonsoo Kim split_page() calls set_page_owner() to set up page_owner to each pages. But, it has a drawback that head page and the others have different stacktrace because callsite of set_page_owner() is slightly differnt. To avoid this problem, this patch copies

[PATCH 6/6] mm/page_owner: use stackdepot to store stacktrace

From: Joonsoo Kim Currently, we store each page's allocation stacktrace on corresponding page_ext structure and it requires a lot of memory. This causes the problem that memory tight system doesn't work well if page_owner is enabled. Moreover, even with this large memory

Re: [PATCH 2/2] zram: user per-cpu compression streams

On Mon, May 02, 2016 at 05:06:00PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 16:25), Sergey Senozhatsky wrote: > [..] > > > Trivial: > > > We could remove max_strm now and change description. > > > > oh, yes. > > how about something like this? remove max_comp_streams entirely, but > leave

[PATCH 5/6] tools/vm/page_owner: increase temporary buffer size

From: Joonsoo Kim Page owner will be changed to store more deep stacktrace so current temporary buffer size isn't enough. Increase it. Signed-off-by: Joonsoo Kim --- tools/vm/page_owner_sort.c | 9 +++-- 1 file changed, 7 insertions(+), 2

[PATCH 1/6] mm/compaction: split freepages without holding the zone lock

From: Joonsoo Kim We don't need to split freepages with holding the zone lock. It will cause more contention on zone lock so not desirable. Signed-off-by: Joonsoo Kim --- include/linux/mm.h | 1 - mm/compaction.c| 42

[PATCH 0/6] mm/page_owner: use tackdepot to store stacktrace

From: Joonsoo Kim This patchset changes a way to store stacktrace in page_owner in order to reduce memory usage. Below is motivation of this patchset coped from the patch 6. Currently, we store each page's allocation stacktrace on corresponding page_ext structure and it

[PATCH 2/6] mm/page_owner: initialize page owner without holding the zone lock

From: Joonsoo Kim It's not necessary to initialized page_owner with holding the zone lock. It would cause more contention on the zone lock although it's not a big problem since it is just debug feature. But, it is better than before so do it. This is also preparation step

[PATCH 3/6] mm/page_owner: copy last_migrate_reason in copy_page_owner()

From: Joonsoo Kim Currently, copy_page_owner() doesn't copy all the owner information. It skips last_migrate_reason because copy_page_owner() is used for migration and it will be properly set soon. But, following patch will use copy_page_owner() and this skip will cause

RE: [PATCH v2 4/6] ACPI / osi: Fix default _OSI(Darwin) support

Hi, Lukas First, thanks for the test. :) > From: Lukas Wunner [mailto:lu...@wunner.de] > Subject: Re: [PATCH v2 4/6] ACPI / osi: Fix default _OSI(Darwin) support > > Hi Lv Zheng, > > On Fri, Apr 29, 2016 at 02:07:53AM +, Zheng, Lv wrote: > > I just sent UPDATE of PATCH 4/6 and PATCH 6/6 to

[PATCH 3.14 05/37] lib: lz4: fixed zram with lz4 on big endian machines

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Rui Salvaterra commit 3e26a691fe3fe1e02a76e5bab0c143ace4b137b4 upstream. Based on Sergey's test patch [1], this fixes zram with lz4 compression on big endian cpus.

[PATCH 3.14 22/37] paride: make verbose parameter an int again

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit dec63a4dec2d6d01346fd5d96062e67c0636852b upstream. gcc-6.0 found an ancient bug in the paride driver, which had a "module_param(verbose, bool, 0);" since

[PATCH 3.14 04/37] usb: hcd: out of bounds access in for_each_companion

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Robert Dobrowolski commit e86103a75705c7c530768f4ffaba74cf382910f2 upstream. On BXT platform Host Controller and Device Controller figure as same PCI

  1   2   3   4   5   6   7   8   9   10   >