[PATCH v2 4/4] staging: ccree: simplify OOM handling

Simplify handling of memory allocation failures and remove redundant log messages Signed-off-by: Gilad Ben-Yossef --- drivers/staging/ccree/ssi_cipher.c | 11 -- drivers/staging/ccree/ssi_driver.c | 1 - drivers/staging/ccree/ssi_hash.c | 42

refactor dma_cache_sync V2

The dma_cache_sync routines is used to flush caches for memory returned by dma_alloc_attrs with the DMA_ATTR_NON_CONSISTENT flag (or previously from dma_alloc_noncoherent), but the requirements for it seems to be frequently misunderstood. dma_cache_sync is documented to be a no-op for allocations

[PATCH 03/11] frv: make dma_cache_sync a no-op

frv does not implement DMA_ATTR_NON_CONSISTENT allocations, so it doesn't make any sense to do any work in dma_cache_sync given that it must be a no-op when dma_alloc_attrs returns coherent memory. Signed-off-by: Christoph Hellwig --- arch/frv/include/asm/dma-mapping.h | 1 - 1

[PATCH] net: dsa: mt7530: make functions mt7530_phy_write static

From: Colin Ian King The function mt7530_phy_write is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warnings: symbol 'mt7530_phy_write' was not declared. Should it be static? Signed-off-by: Colin Ian King

Re: [PATCH V2] firmware: tegra: add BPMP debugfs support

Jon, thanks for reviewing On 03.10.2017 13:55, Jonathan Hunter wrote: +static int create_debugfs_mirror(struct tegra_bpmp *bpmp, void *buf, +size_t bufsize, struct dentry *root) +{ + struct seqbuf seqbuf; + int err; + + bpmp->debugfs_mirror =

Re: [PATCH] x86/CPU/AMD, mm: Extend with mem_encrypt=sme option

On Tue, Oct 03, 2017 at 12:50:15PM +0200, Paolo Bonzini wrote: > Stupid question ahead: if it's just about guests, why bother with > mem_encrypt=xxx at all? kvm_amd should have a sev parameter anyway, you > can just do kvm_amd.sev=0 to disable it. Yes, it is only about guests so this could be a

Re: [PATCH 07/11] powerpc: make dma_cache_sync a no-op

Le 03/10/2017 à 12:43, Christoph Hellwig a écrit : powerpc does not implement DMA_ATTR_NON_CONSISTENT allocations, so it doesn't make any sense to do any work in dma_cache_sync given that it must be a no-op when dma_alloc_attrs returns coherent memory. What about

Re: [PATCH 07/11] powerpc: make dma_cache_sync a no-op

On 03/10/17 12:24, Christophe LEROY wrote: > > > Le 03/10/2017 à 12:43, Christoph Hellwig a écrit : >> powerpc does not implement DMA_ATTR_NON_CONSISTENT allocations, so it >> doesn't make any sense to do any work in dma_cache_sync given that it >> must be a no-op when dma_alloc_attrs returns

[PATCH 3/4] staging: bcm2835-camera: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/vc04_services/bcm2835-camera/mmal-vchiq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] staging: rtlwifi: pr_err() strings should end with newlines

pr_err() messages should end with a new-line to avoid other messages being concatenated. Signed-off-by: Arvind Yadav --- drivers/staging/rtlwifi/halmac/halmac_88xx/halmac_func_88xx.c | 6 +++--- drivers/staging/rtlwifi/rtl8822be/phy.c | 4 ++-- 2

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Wed 27-09-17 14:09:34, Roman Gushchin wrote: > Traditionally, the OOM killer is operating on a process level. > Under oom conditions, it finds a process with the highest oom score > and kills it. > > This behavior doesn't suit well the system with many running > containers: > > 1) There is no

Re: [v9 4/5] mm, oom: add cgroup v2 mount option for cgroup-aware OOM killer

On Wed 27-09-17 14:09:35, Roman Gushchin wrote: > Add a "groupoom" cgroup v2 mount option to enable the cgroup-aware > OOM killer. If not set, the OOM selection is performed in > a "traditional" per-process way. > > The behavior can be changed dynamically by remounting the cgroupfs. I do not

Re: refactor dma_cache_sync V2

On 03/10/17 11:43, Christoph Hellwig wrote: > The dma_cache_sync routines is used to flush caches for memory returned > by dma_alloc_attrs with the DMA_ATTR_NON_CONSISTENT flag (or previously > from dma_alloc_noncoherent), but the requirements for it seems to be > frequently misunderstood.

[PATCH v6 2/4] x86/xen/time: set pvclock flags on xen_time_init()

Specifically check for PVCLOCK_TSC_STABLE_BIT and if this bit is set, then set it too on pvclock flags. This allows Xen clocksource to use it and thus speeding up xen_clocksource_read() callers (i.e. sched_clock()) Signed-off-by: Joao Martins Reviewed-by: Boris

[PATCH v6 4/4] MAINTAINERS: xen, kvm: track pvclock-abi.h changes

This file defines an ABI shared between guest and hypervisor(s) (KVM, Xen) and as such there should be an correspondent entry in MAINTAINERS file. Notice that there's already a text notice at the top of the header file, hence this commit simply enforces it more explicitly and have both peers

[PATCH v6 3/4] x86/xen/time: setup vcpu 0 time info page

In order to support pvclock vdso on xen we need to setup the time info page for vcpu 0 and register the page with Xen using the VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall will also forcefully update the pvti which will set some of the necessary flags for vdso. Afterwards we

[PATCH v6 0/4] x86/xen: pvclock vdso support

Hey, This is take 6 for vdso for Xen. PVCLOCK_TSC_STABLE_BIT can be set starting Xen 4.8 which is required for vdso time related calls. In order to have it on, you need to have the hypervisor clocksource be TSC e.g. with the following boot params "clocksource=tsc tsc=stable:socket". Series is

[PATCH v2] ide: pci: free PCI BARs on initialization failure

Recent pci_assign_irq() changes uncovered a problem with missing freeing of PCI BARs on PCI IDE host initialization failure: ide0: disabled, no IRQ ide0: failed to initialize IDE interface ide0: disabling port cmd64x :00:02.0: IDE controller (0x1095:0x0646 rev 0x07) CMD64x_IDE :00:02.0:

[PATCH 4.9 00/64] 4.9.53-stable review

This is the start of the stable review cycle for the 4.9.53 release. There are 64 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 5 11:42:06 UTC 2017. Anything

[PATCH 4.9 11/64] tracing: Erase irqsoff trace with empty write

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bo Yan commit 8dd33bcb7050dd6f8c1432732f930932c9d3a33e upstream. One convenient way to erase trace is "echo > trace". However, this is currently broken if the current tracer

[PATCH 4.9 10/64] tracing: Fix trace_pipe behavior for instance traces

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit 75df6e688ccd517e339a7c422ef7ad73045b18a2 upstream. When reading data from trace_pipe, tracing_wait_pipe() performs a check to see if tracing has been

[PATCH 4.9 21/64] security/keys: rewrite all of big_key crypto

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Jason A. Donenfeld" commit 428490e38b2e352812e0b765d8bceafab0ec441d upstream. This started out as just replacing the use of crypto/rng with get_random_bytes_wait, so that we

[PATCH 4.9 16/64] crypto: drbg - fix freeing of resources

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller commit bd6227a150fdb56e7bb734976ef6e53a2c1cb334 upstream. During the change to use aligned buffers, the deallocation code path was not updated correctly.

[PATCH 4.9 27/64] powerpc/ftrace: Pass the correct stack pointer for DYNAMIC_FTRACE_WITH_REGS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Naveen N. Rao" commit a4979a7e71eb8da976cbe4a0a1fa50636e76b04f upstream. For DYNAMIC_FTRACE_WITH_REGS, we should be passing-in the original set of registers

[PATCH 4.9 17/64] crypto: talitos - Dont provide setkey for non hmac hashing algs.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 56136631573baa537a15e0012055ffe8cfec1a33 upstream. Today, md5sum fails with error -ENOKEY because a setkey function is set for non hmac hashing

[PATCH 4.9 20/64] security/keys: properly zero out sensitive key material in big_key

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason A. Donenfeld commit 910801809b2e40a4baedd080ef5d80b4a180e70e upstream. Error paths forgot to zero out sensitive material, so this patch changes some kfrees into a

[PATCH 4.4 11/41] KEYS: fix writing past end of user-supplied buffer in keyring_read()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit e645016abc803dafc75e4b8f6e4118f088900ffb upstream. Userspace can call keyctl_read() on a keyring to get the list of IDs of keys in the keyring. But if

[PATCH 4.9 63/64] video: fbdev: aty: do not leak uninitialized padding in clk to userspace

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vladis Dronov commit 8e75f7a7a00461ef6d91797a60b606367f6e344d upstream. 'clk' is copied to a userland with padding byte(s) after 'vclk_post_div' field unitialized, leaking

Re: [PATCH v9 02/12] sparc64/mm: setting fields in deferred pages

On Wed 20-09-17 16:17:04, Pavel Tatashin wrote: > Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), > flags and other fields in "struct page"es are never changed prior to first > initializing struct pages by going through __init_single_page(). > > With deferred struct page

[PATCH 4.9 39/64] selftests/seccomp: Support glibc 2.26 siginfo_t.h

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 10859f3855db4c6f10dc7974ff4b3a292f3de8e0 upstream. The 2.26 release of glibc changed how siginfo_t is defined, and the earlier work-around to using the

[PATCH v4 2/6] perf record: Get the first sample time and last sample time

In perf record, it's walked on all samples yet. So it's very easy to get the first/last samples and save the time to perf file header via the function write_sample_time(). In later, perf report/script will fetch the time from perf file header. Change log: --- v3: Remove the definitions

Re: 4.14-rc2 on thinkpad x220: out of memory when inserting mmc card

On 02/10/17 17:09, Linus Walleij wrote: > On Sun, Oct 1, 2017 at 12:57 PM, Tetsuo Handa > wrote: > I inserted u-SD card, only to realize that it is not detected as it should be. And dmesg indeed reveals: >>> >>> Tetsuo asked me to report this to

Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage

On Tue, 3 Oct 2017, Michael Ellerman wrote: > Hi Thomas, > Unfortunately this is hitting the WARN_ON in start_wd_cpu() on powerpc > because we're calling it multiple times for the boot CPU. > > The first call is via: > > start_wd_on_cpu+0x80/0x2f0 > watchdog_nmi_reconfigure+0x124/0x170 >

Re: [PATCH v3] dma-debug: fix incorrect pfn calculation

On Mon, Oct 02, 2017 at 06:30:41PM +0800, Miles Chen wrote: > ARCHs like metag and xtensa define their mappings (non-vmalloc and > non-linear) for dma allocation. metag basically is a reimplementation of the vmalloc map mechanism that should be easy to consolidate into the common one :( xtensa

Re: [PATCH] clk: tegra30: make tegra_clk_pll_params __ro_after_init

Acked-By: Peter De Schrijver I would assume this also applies to many PLL structs for other Tegra SoCs? Peter. On Tue, Oct 03, 2017 at 01:42:08AM +0530, Bhumika Goyal wrote: > These structures are only passed to the functions tegra_clk_register_pll, >

Re: sysbench throughput degradation in 4.13+

On Mon, Oct 02, 2017 at 11:53:12PM +0100, Matt Fleming wrote: > On Wed, 27 Sep, at 01:58:20PM, Rik van Riel wrote: > > > > I like the simplicity of your approach! I hope it does not break > > stuff like netperf... > > > > I have been working on the patch below, which is much less optimistic > >

Re: [PATCH v3 01/12] pinctrl: move gpio-axp209 to pinctrl

On Tue, Oct 3, 2017 at 4:18 AM, Maxime Ripard wrote: > On Mon, Oct 02, 2017 at 12:08:43PM +, Quentin Schulz wrote: >> To prepare the driver for the upcoming pinctrl features, move the GPIO >> driver AXP209 from GPIO to pinctrl subsystem. >> >> Signed-off-by:

Re: [PATCH V5 4/7] blk-mq: introduce blk_mq_dequeue_from_ctx()

On Sat, Sep 30, 2017 at 06:27:17PM +0800, Ming Lei wrote: > This function is introduced for dequeuing request > from sw queue so that we can dispatch it in > scheduler's way. > > More importantly, some SCSI devices may set > q->queue_depth, which is a per-request_queue limit, > and applied on

[PATCH 0/1] virt: Add vboxguest driver for Virtual Box Guest integration

Hi All, Here is my first non RFC submission of my cleaned up version of the VirtualBox vboxguest driver. VirtualBox upstream has declared the ioctl API for the /dev/vboxguest device as being stable now, so once this passes review this is ready for merging. I'm only submitting the vboxguest

Re: [PATCH V5 8/8] blk-mq: improve bio merge from blk-mq sw queue

This looks generally good to me, but I really worry about the impact on very high iops devices. Did you try this e.g. for random reads from unallocated blocks on an enterprise NVMe SSD?

[PATCH v10 1/4] rockchip/rga: v4l2 m2m support

Rockchip RGA is a separate 2D raster graphic acceleration unit. It accelerates 2D graphics operations, such as point/line drawing, image scaling, rotation, BitBLT, alpha blending and image blur/sharpness The driver supports various operations from the rendering pipeline. - copy - fast solid

Re: [kernel-hardening] [PATCH 0/3] Makefile: Introduce CONFIG_CC_STACKPROTECTOR_AUTO

Hi Kees, On Mon, Oct 02, 2017 at 12:20:04PM -0700, Kees Cook wrote: > As described in the final patch: > > Nearly all modern compilers support a stack-protector option, and nearly > all modern distributions enable the kernel stack-protector, so enabling > this by default in kernel builds would

Re: [PATCH] virt: Add vboxguest driver for Virtual Box Guest integration

Looks like you forgot to CC previous revierers. > +#define CHECK_IOCTL_IN(req) \ > +do { \ > + if ((req)->Hdr.cbIn != (sizeof((req)->Hdr) + sizeof((req)->u.In)) || \ > +

[PATCH 4.13 094/110] futex: Fix pi_state->owner serialization

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit c74aef2d06a9f59cece89093eecc552933cba72a upstream. There was a reported suspicion about a race between exit_pi_state_list() and put_pi_state(). The

[PATCH 4.13 093/110] etnaviv: fix gem object list corruption

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Lucas Stach commit 518417525f3652c12fb5fad6da4ade66c0072fa3 upstream. All manipulations of the gem_object list need to be protected by the list mutex, as GEM objects

[PATCH 4.13 087/110] fix infoleak in waitid(2)

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 6c85501f2fabcfc4fc6ed976543d252c4eaf4be9 upstream. kernel_waitid() can return a PID, an error or 0. rusage is filled in the first case and waitid(2)

[PATCH 4.13 082/110] KVM: nVMX: fix HOST_CR3/HOST_CR4 cache

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Ladi Prosek commit 44889942b6eb356eab27ce25fe10701adfec7776 upstream. For nested virt we maintain multiple VMCS that can run on a vCPU. So it is incorrect to keep

[PATCH 4.13 089/110] irq/generic-chip: Dont replace domains name

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Jeffy Chen commit 72364d320644c12948786962673772f271039a4a upstream. When generic irq chips are allocated for an irq domain the domain name is set to the irq chip

[PATCH 4.13 072/110] extable: Consolidate *kernel_text_address() functions

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 9aadde91b3c035413c806619beb3e3ef6e697953 upstream. The functionality between kernel_text_address() and _kernel_text_address() is the same

[PATCH 4.13 097/110] PCI: Fix race condition with driver_override

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Nicolai Stange commit 9561475db680f7144d2223a409dd3d7e322aca03 upstream. The driver_override implementation is susceptible to a race condition when different threads are

[PATCH 4.13 077/110] arm64: mm: Use READ_ONCE when dereferencing pointer to pte table

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit f069faba688701c4d56b6c3452a130f97bf02e95 upstream. On kernels built with support for transparent huge pages, different CPUs can access the PMD

[PATCH v4 4/6] perf util: Create function to perform multiple time range checking

Previous patch supports the multiple time range. For example, select the first and second 10% time slices. perf report --time 10%/1,10%/2 We need a function to check if a timestamp is in the ranges of [0, 10%) and [10%, 20%]. Note that it includes the last element in [10%, 20%] but it doesn't

[PATCH v4 1/6] perf header: Record first sample time and last sample time in perf file header

perf report/script/... have a --time option to limit the time range of output. That's very useful to slice large traces, e.g. when processing the output of perf script for some analysis. But right now --time only supports absolute time. Also there is no fast way to get the start/end times of a

[PATCH v4 5/6] perf report: support time percent and multiple time ranges

perf report has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf report --time 10%/1,10%/2 2. Select

[PATCH v4 3/6] perf util: Create function to parse time percent

Current perf report/script/... have a --time option to limit the time range of output. But right now it only supports absolute time. For easy using, now it can support a percent of time usage. For example: 1. Select the second 10% time slice perf report --time 10%/2 2. Select from 0% to 10%

[PATCH v4 0/6] perf report/script: Support percent and multiple range in --time option

v4: --- 1. Use perf script time style for timestamp printing. Also add with the printing of sample duration. For example: perf report --header time of first sample : 5276531.323099 time of last sample : 5276555.345625 sample duration : 24022.526 ms 2. Fix an invalid time string

[PATCH v4 6/6] perf script: support time percent and multiple time ranges

perf script has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf script --time 10%/1,10%/2 2.

Re: [PATCH 5/6] lightnvm: pblk: free up mempool allocation for erases correctly

> On 2 Oct 2017, at 19.18, Rakesh Pandit wrote: > > On Mon, Oct 02, 2017 at 03:25:10PM +0300, Rakesh Pandit wrote: >> On Mon, Oct 02, 2017 at 02:09:35PM +0200, Javier González wrote: On 1 Oct 2017, at 15.25, Rakesh Pandit wrote: While

Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage

On Tue, 3 Oct 2017, Thomas Gleixner wrote: > On Tue, 3 Oct 2017, Michael Ellerman wrote: > > Hi Thomas, > > Unfortunately this is hitting the WARN_ON in start_wd_cpu() on powerpc > > because we're calling it multiple times for the boot CPU. > > > > The first call is via: > > > >

Re: regression in 4.14-rc2 caused by apparmor: add base infastructure for socket mediation

On 10/02/2017 11:48 PM, Vlastimil Babka wrote: > On 10/03/2017 07:15 AM, James Bottomley wrote: >> On Mon, 2017-10-02 at 21:11 -0700, John Johansen wrote: >>> On 10/02/2017 09:02 PM, James Bottomley wrote: The specific problem is that dnsmasq refuses to start on openSUSE Leap 42.2.

Re: [RFC] yamldt v0.5, now a DTS compiler too

Hi Pantelis, On Mon, Oct 2, 2017 at 9:46 PM, Pantelis Antoniou wrote: > # Note that the YAML example must be validated against this binding > # to be an accepted entry Indeed ;-) > yaml: | > sk11@0: > compatible: "skel,sk11" >

[BUGFIX PATCH] kprobes/x86: Remove IRQ disabling from jprobe handlers

Jprobe actually doesn't need to disable IRQs while calling handlers, because Documentation/kprobes.txt says: - Probe handlers are run with preemption disabled. Depending on the architecture and optimization state, handlers may also run with interrupts disabled (e.g., kretprobe handlers

[RFC PATCH] mm, hugetlb: drop hugepages_treat_as_movable sysctl

From: Michal Hocko hugepages_treat_as_movable has been introduced by 396faf0303d2 ("Allow huge page allocations to use GFP_HIGH_MOVABLE") to allow hugetlb allocations from ZONE_MOVABLE even when hugetlb pages were not migrateable. The purpose of the movable zone was different at

Re: [PATCH v2 0/5] Simplify panel bridge cleanup

On Mon, Oct 02, 2017 at 11:32:30AM +0200, Benjamin Gaignard wrote: > The goal of this series is to simplify driver code when they need to clean up > a previously allocated panel bridge. > Few drivers have "is_panel_bridge" flag to be able to distinguish a > drm_panel_bridge from "simple"

Re: [PATCH V7 6/6] SCSI: set block queue at preempt only when SCSI device is put into quiesce

On Mon, Oct 02, 2017 at 06:52:25AM -0700, Christoph Hellwig wrote: > > + /* > > +* Simply quiesing SCSI device isn't safe, it is easy > > +* to use up requests because all these allocated requests > > +* can't be dispatched when device is put in QIUESCE. > > +* Then no request

Re: [PATCH 0/6] Boot-time switching between 4- and 5-level paging for 4.15, Part 1

On Fri, Sep 29, 2017 at 05:08:15PM +0300, Kirill A. Shutemov wrote: > The first bunch of patches that prepare kernel to boot-time switching > between paging modes. > > Please review and consider applying. Ping? -- Kirill A. Shutemov

[PATCH v2 2/2] dmaengine: omap-dma: Implement protection for invalid max_burst

Set the device's max_burst to 16777215 (EN is 24bit unsigned value) so clients can take this into consideration when setting up the transfer. During slave transfer preparation check if the requested maxburst is valid. Signed-off-by: Peter Ujfalusi Cc: Russell King

[PATCH v2 1/2] dmaengine: edma: Implement protection for invalid max_burst

Set the device's max_burst to 32767 (CIDX is 16bit signed value) so clients can take this into consideration when setting up the transfer. During slave transfer preparation check if the requested maxburst is valid. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c |

Re: [PATCH REBASED 0/6] rwsem: Implement down_read_killable()

On Fri, Sep 29, 2017 at 07:05:45PM +0300, Kirill Tkhai wrote: > The series introduces new down_read_killable() primitive, which > is similar to down_read(), but it may be interrupted by a signal. > The most touched is architectures code. Also, it marks a new user > of the primitive, which is

Re: [PATCH v3 04/12] pinctrl: axp209: add programmable gpio_status_offset

On Tue, Oct 3, 2017 at 4:38 AM, Maxime Ripard wrote: > On Mon, Oct 02, 2017 at 12:08:46PM +, Quentin Schulz wrote: >> To prepare for patches that will add support for a new PMIC that has a >> different GPIO input status register, add a gpio_status_offset

Re: [PATCH v2] arm64: dts: foundation-v8: Enable PSCI mode

On 02/10/17 18:26, Sudeep Holla wrote: Sorry for late response, I thought I had sent this mail out long back but was sitting in my draft :( No worries. I've been at Linaro connect this last week anyway. On 20/09/17 12:17, Daniel Thompson wrote: On 20/09/17 10:42, Sudeep Holla wrote: On

Re: [PATCH V5 7/7] blk-mq-sched: don't dequeue request until all in ->dispatch are flushed

This looks good in general: Reviewed-by: Christoph Hellwig Minor nitpicks below: > const bool has_sched_dispatch = e && e->type->ops.mq.dispatch_request; This is now only tested once, so you can remove the local variable for it. > + /* > + * We may

Re: [PATCH V5 5/8] block: add check on elevator for supporting bio merge via hashtable from blk-mq sw queue

On Sat, Sep 30, 2017 at 07:26:52PM +0800, Ming Lei wrote: > blk_mq_sched_try_merge() will be reused in following patches > to support bio merge to blk-mq sw queue, so add checkes to > related functions which are called from blk_mq_sched_try_merge(). The changes themselves look ok, but don't make

Re: [PATCH v3 5/8] platform/x86: dell-wmi-smbios: introduce character device for userspace

On Wed, Sep 27, 2017 at 11:02:17PM -0500, Mario Limonciello wrote: > +static int dell_wmi_smbios_open(struct inode *inode, struct file *file) > +{ > + return nonseekable_open(inode, file); > +} > + > +static int dell_wmi_smbios_release(struct inode *inode, struct file *file) > +{ > +

[PATCH v10 2/4] ARM: dts: rockchip: add RGA device node for RK3288

This patch add the RGA dt config of rk3288 SoC. Signed-off-by: Jacob Chen Signed-off-by: Yakir Yang --- arch/arm/boot/dts/rk3288.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi

Re: [PATCH] KVM: VMX: check match table

On 01/10/2017 01:22, Nick Desaulniers wrote: > On Wed, Sep 27, 2017 at 02:36:03PM +0200, Paolo Bonzini wrote: >> On 26/09/2017 19:12, Josh Triplett wrote: >>> Does this make any other checks redundant and removable? >> >> It would make sense to place it in cpu_has_kvm_support instead > >

[PATCH] md-cluster: make function cluster_check_sync_size static

From: Colin Ian King The function cluster_check_sync_size is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'cluster_check_sync_size' was not declared. Should it be static? Signed-off-by: Colin Ian King

Re: [PATCH v2 2/7] drm/rockchip: dw_hdmi: add device type

On 30/09/2017 03:43, Algea Cao wrote: > To determine type of SOC, we add a parameter dev_type. > > Signed-off-by: Algea Cao > --- > drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 5 + > include/drm/bridge/dw_hdmi.h| 10 ++ > 2 files changed,

[PATCH 9/9] lightnvm: pblk: correct valid lba count calculation

From: Hans Holmberg During garbage collect, lbas being written can end up being invalidated. Make sure that this is reflected in the valid lba count. Signed-off-by: Hans Holmberg --- drivers/lightnvm/pblk-map.c | 7 --- 1 file

[PATCH] mmc: sdhci-of-at91: make function sdhci_at91_set_uhs_signaling static

From: Colin Ian King The function sdhci_at91_set_uhs_signaling is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'sdhci_at91_set_uhs_signaling' was not declared. Should it be static? Signed-off-by:

[PATCH 0/9] recovery robustness improvements

From: Hans Holmberg This patchset improves the robustness of recovery - fixing a bunch of issues that occurs when removing and re-creating a pblk instance. It also adds a couple of debug-only prints to facilitate detection of L2P table corruptions. The patches apply

Re: regression in 4.14-rc2 caused by apparmor: add base infastructure for socket mediation

On 10/02/2017 10:15 PM, James Bottomley wrote: > On Mon, 2017-10-02 at 21:11 -0700, John Johansen wrote: >> On 10/02/2017 09:02 PM, James Bottomley wrote: >>> >>> The specific problem is that dnsmasq refuses to start on openSUSE >>> Leap 42.2. The specific cause is that and attempt to open a >>>

Re: [RFC PATCH 0/2] Missing READ_ONCE in core and arch-specific pgtable code leading to crashes

On 09/29/2017 04:56 AM, Will Deacon wrote: > The full fix isn't just cosmetic; it's also addressing the wider problem > of unannotated racing page table accesses outside of the specific failure > case we've run into. Let us know if there are additional tests we should be running on the Red Hat

Re: [PATCH] of: do not leak console options

On Tue 2017-09-26 15:25:10, Sergey Senozhatsky wrote: > Do not strdup() console options. It seems that the only reason for > it to be strdup()-ed was a compilation warning: printk, UART and > console drivers, for some reason, expect char pointer instead of > const char pointer. So we can just pass

Fix a typo in Documentation/sysctl/vm.txt

--- linux/Documentation/sysctl/vm.txt.orig 2017-09-07 00:19:43.260477784 +0900 +++ linux/Documentation/sysctl/vm.txt 2017-09-07 00:19:56.498431846 +0900 @@ -793,7 +793,7 @@ with no ill effects: errors and warnings swappiness This control is used to define how aggressive the kernel will swap

Re: [PATCH v3 00/20] Speculative page faults

On 03/10/2017 03:27, Michael Ellerman wrote: > Laurent Dufour writes: > >> Hi Andrew, >> >> On 28/09/2017 22:38, Andrew Morton wrote: >>> On Thu, 28 Sep 2017 14:29:02 +0200 Laurent Dufour >>> wrote: >>> > Laurent's [0/n] provides some

Re: Patch "KVM: VMX: avoid double list add with VT-d posted interrupts" has been added to the 4.13-stable tree

On 03/10/2017 09:46, Stefan Lippers-Hollmann wrote: > Hi > > On 2017-10-02, gre...@linuxfoundation.org wrote: >> This is a note to let you know that I've just added the patch titled >> >> KVM: VMX: avoid double list add with VT-d posted interrupts >> >> to the 4.13-stable tree which can be

Re: [PATCH V2] PCI: AER: fix deadlock in do_recovery

On Mon, Oct 02, 2017 at 05:14:09PM -0700, Govindarajulu Varadarajan wrote: > > I would avoid increasing the size of pci_dev. The list_head would be empty > after > we call aer_pci_walk_bus(). We already have pci_bus *subordinate to link all > the > 'device's. Making list_head available to others

Re: [PATCH 05/18] net: use ARRAY_SIZE

On Tue, Oct 3, 2017 at 4:22 AM, Jérémy Lefaure wrote: > On Mon, 2 Oct 2017 16:07:36 +0300 > Andy Shevchenko wrote: > >> > + {_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev0), >> > 26, 192, >> > +32}, >> >> For all such

Re: [PATCH] PM: ARM: locomo: Drop suspend and resume bus type callbacks

On 26 September 2017 at 22:45, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > None of the locomo drivers in the tree implements the suspend and > resume callbacks from struct locomo_driver, so drop them and drop > the corresponding

RE: [PATCH] fsl/fman: remove of_node

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Tuesday, October 03, 2017 2:05 AM > To: Madalin-cristian Bucur > Subject: Re: [PATCH] fsl/fman: remove of_node > > From: Madalin Bucur > Date: Mon, 2 Oct 2017

Re: [PATCH V5 1/7] blk-mq: issue rq directly in blk_mq_request_bypass_insert()

This patch does two many things at once and needs a split. I also don't really understand why it's in this series and not your dm-mpath performance one. > +static void blk_mq_request_direct_insert(struct blk_mq_hw_ctx *hctx, > + struct request *rq) > +{ > +

Re: [PATCH V5 6/7] blk-mq-sched: improve dispatching from sw queue

On Sat, Sep 30, 2017 at 06:27:19PM +0800, Ming Lei wrote: > SCSI devices use host-wide tagset, and the shared > driver tag space is often quite big. Meantime > there is also queue depth for each lun(.cmd_per_lun), > which is often small. > > So lots of requests may stay in sw queue, and we >

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote: > For WMI operations that are only Set or Query read or write sysfs > attributes created by WMI vendor drivers make sense. > > For other WMI operations that are run on Method, there needs to be a > way to guarantee to userspace

Re: [PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote: > For WMI operations that are only Set or Query read or write sysfs > attributes created by WMI vendor drivers make sense. > > For other WMI operations that are run on Method, there needs to be a > way to guarantee to userspace

Re: [PATCH v3] mm, sysctl: make NUMA stats configurable

On Thu 28-09-17 14:11:41, Kemi Wang wrote: > This is the second step which introduces a tunable interface that allow > numa stats configurable for optimizing zone_statistics(), as suggested by > Dave Hansen and Ying Huang. > >

Re: [BUGFIX PATCH] kprobes/x86: Remove IRQ disabling from jprobe handlers

* Masami Hiramatsu wrote: > Jprobe actually doesn't need to disable IRQs while calling > handlers, because Documentation/kprobes.txt says: > > - > Probe handlers are run with preemption disabled. Depending on the > architecture and optimization state, handlers may

Re: i2c-omap.c vs. qemu: too much work in one irq (and broken boot)

Hi! > > > I'm trying to get qemu emulation of Nokia N900 to work, but > > > unfortunately i2c-omap.c breaks boot in the emulator (real hardware > > > works ok). > > > > I started bisection. v4.6 works, v4.7 is broken. (It still may be > > config difference or something). > > > > This looked

[PATCH] mmc: dw_mmc-k3: make array hs_timing_cfg static

From: Colin Ian King The array hs_timing_cfg is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: symbol 'hs_timing_cfg' was not declared. Should it be static? Signed-off-by: Colin Ian King

Re: [PATCH v2] arm64: dts: foundation-v8: Enable PSCI mode

On 3 October 2017 at 10:12, Daniel Thompson wrote: > On 02/10/17 18:26, Sudeep Holla wrote: >> >> Sorry for late response, I thought I had sent this mail out long back >> but was sitting in my draft :( > > > No worries. I've been at Linaro connect this last week

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