[PATCH] microblaze: use sg_phys()

Use sg_phys() instead of open-coding it. Signed-off-by: Geliang Tang --- arch/microblaze/kernel/dma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/microblaze/kernel/dma.c b/arch/microblaze/kernel/dma.c index 12e093a..e45ada8 100644 ---

Re: [PATCH] drivers/staging/dgnc: Removing manual function tracing using dev_dbg

On Thu, Mar 23, 2017 at 02:20:53PM +0530, Pushkar Jambhlekar wrote: > Current implementation manually traces function using 'dev_dbg'. This way is > not needed because of ftrace, making these calls redundant. Always wrap your changelog lines properly. Also, someone else sent this same patch in

RE: Query on DT overlay support.

Hi,     This mail is regarding the DT overlay support in the Linux kernel     I am able to make the device-tree overlay work out of box by using my own dtc complier (I mean I used the dtc compiler     Available here

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

On Thu, Mar 23, 2017 at 11:10 AM, Uwe Kleine-König wrote: > So you exchanged many obvious and easy to fix problems with a few hard > ones. I don't agree that's a good idea, but you seem to be willing to > try it. Good luck. I think instead of going to sarcastic

[PATCH 2/4] sched: cpudeadline: don't re-initialize struct cpudl

The struct cpudl passed to cpudl_init() is already initialized to zero. Don't do that again. Signed-off-by: Viresh Kumar --- kernel/sched/cpudeadline.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/sched/cpudeadline.c b/kernel/sched/cpudeadline.c index

[PATCH 1/4] sched: topology: drop memset() from init_rootdomain()

There are only two callers of init_rootdomain(). One of them passes a global to it and another one sends dynamically allocated root-domain. There is no need to memset the root-domain in the first case as the structure is already reset. Update alloc_rootdomain() to allocate the memory with

[PATCH] staging: ad7746: Moved contents of the header to the source file.

Moved the contents of the header(ad7746.h) into the source file ad7746.c with the exception of the platform data struct which is supposed to be used from somewhere else other than the driver. Signed-off-by: Arushi Singhal --- drivers/staging/iio/cdc/ad7746.c | 5

Re: [PATCH v5 3/3] mfd: wm831x: Add device tree binding document

On Fri, 17 Mar 2017, Charles Keepax wrote: > Add a device tree binding document for the wm831x series of PMICs. > Currently only support for the registering the device and the GPIOs are > actually implemented in the driver. > > Signed-off-by: Charles Keepax

[PATCH v2] kasan: report only the first error by default

Disable kasan after the first report. There are several reasons for this: * Single bug quite often has multiple invalid memory accesses causing storm in the dmesg. * Write OOB access might corrupt metadata so the next report will print bogus alloc/free stacktraces. * Reports after the

Re: [PATCH] video: fbdev: pmag-aa-fb: remove incorrect __exit markups

On Mon, 20 Mar 2017, Bartlomiej Zolnierkiewicz wrote: > > Even if bus is not hot-pluggable, devices can be unbound from the > > driver via sysfs, so we should not be using __exit annotations on > > remove() methods. The only exception is drivers registered with > > platform_driver_probe() which

[GIT PULL] Immutable branch between MFD and GPIO due for the v4.12 merge window

Enjoy, The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201: Linux 4.11-rc1 (2017-03-05 12:59:56 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-gpio-v4.12 for you to fetch changes up to

Re: [PATCH] ARM: nommu: access ID_PFR1 only if CPUID scheme

Hi Afzal, On 23/03/17 20:43, afzal mohammed wrote: On Fri, Mar 17, 2017 at 10:10:34PM +0530, afzal mohammed wrote: Greg upon trying to boot no-MMU Kernel on ARM926EJ reported boot failure. He root caused it to ID_PFR1 access introduced by the commit mentioned in the fixes tag below. All CP15

[PATCH] drm/i915/kvmgt: avoid dereferencing a potentially null info pointer

From: Colin Ian King info is being checked to see if it is a null pointer, however, vpgu is dereferencing info before this check, leading to a potential null pointer dereference. If info is null, then the error message being printed by macro gvt_vgpu_err and this

[PATCH] arm/arm64: KVM: send SIGBUS error to qemu

when the pfn is KVM_PFN_ERR_HWPOISON, it indicates to send SIGBUS signal from KVM's fault-handling code to qemu, qemu can handle this signal according to the fault address. Signed-off-by: Dongjiu Geng --- arch/arm/kvm/mmu.c | 20

[PATCH 5/5] w83627ehf: Drop support for nct6775/nct6776

Since there exists a dedicated driver for nct6775/nct6776 it makes sense to remove support for these chips from this driver, in order to have only one code base for these types of chips. This also improves maintainability and readability (and size) of this driver. Some not so-obvious changes

[PATCH 1/5] w83627ehf: Use hwmon_device_register_with_info and sensor groups

This patch replaces the old, deprecated call to hwmon_device_register with the new hwmon_device_register_with_info and converts the whole driver to the new hwmon interface using the hwmon_chip_info methods and the attribute_group method. All standard attributes were converted to the corresponding

Re: [PATCH] ARM: gemini: don't select SERIAL_OF_PLATFORM

On Thu, Mar 23, 2017 at 1:13 PM, Arnd Bergmann wrote: > On Thu, Mar 23, 2017 at 11:22 AM, Linus Walleij > wrote: >> On Tue, Mar 21, 2017 at 9:52 PM, Arnd Bergmann wrote: >> >>> We cannot select the option when SERIAL_8250 is not also set:

[PATCH 3/5] w83627ehf: Minor readability fixes

just some cosmetics for better readability, proposed by Lindent/checkpatch Signed-off-by: Peter Huewe --- drivers/hwmon/w83627ehf.c | 39 +++ 1 file changed, 15 insertions(+), 24 deletions(-) diff --git a/drivers/hwmon/w83627ehf.c

Re: [PATCH 3/7] iommu/iova: insert start_pfn boundary of dma32

On 22/03/17 06:27, Zhen Lei wrote: > Reserve the first granule size memory(start at start_pfn) as boundary > iova, to make sure that iovad->cached32_node can not be NULL in future. > Meanwhile, changed the assignment of iovad->cached32_node from rb_next to > rb_prev of >node in function

[PATCH] qla2xxx: use sg_virt()

Use sg_virt() instead of open-coding it. Signed-off-by: Geliang Tang --- drivers/scsi/qla2xxx/qla_isr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c index 3203367..9610d85 100644 ---

[PATCH] iommu: use sg_phys()

Use sg_phys() instead of open-coding it. Signed-off-by: Geliang Tang --- drivers/iommu/intel-iommu.c | 2 +- drivers/iommu/iommu.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c index

[PATCH] crypto: ixp4xx - Use sg_virt()

Use sg_virt() instead of open-coding it. Signed-off-by: Geliang Tang --- drivers/crypto/ixp4xx_crypto.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/ixp4xx_crypto.c b/drivers/crypto/ixp4xx_crypto.c index 7868765..771dd26 100644 ---

Re: [PATCH v2 02/10] x86: assembly, FUNC_START for fn, DATA_START for data

On Thu, Mar 23, 2017 at 08:38:20AM +0100, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > On Wed, Mar 22, 2017 at 08:46:16AM +0100, Ingo Molnar wrote: > > > > > > * Jiri Slaby wrote: > > > > > > > On 03/22/2017, 08:25 AM, Ingo Molnar wrote: > > > > >

Re: [PATCH] staging: media: atomisp: use kvmalloc and kvfree

On Thu, Mar 23, 2017 at 09:12:39PM +0800, Geliang Tang wrote: > Use kvmalloc() and kvfree() instead of open-coding. These functions are not in Linus's tree, so I can't apply this patch without breaking things :( thanks, greg k-h

[PATCH] staging: rtl8192e: Fix embedded function names with __func__

From: Suniel Mahesh Prefer and make it generic by using %s and __func__ to print functions name instead of embedding functions name in print statements Signed-off-by: Suniel Mahesh --- drivers/staging/rtl8192e/rtl8192e/rtl_ps.c | 22

Re: [PATCH] scsi: fcoe: sanity check string size for store_ctrl_mode option

On Wed, Mar 22, 2017 at 07:42:08PM +, Colin Ian King wrote: > On 22/03/17 19:39, Dan Carpenter wrote: > > On Wed, Mar 22, 2017 at 02:01:37PM +, Colin King wrote: > >> From: Colin Ian King > >> > >> Reading and writing to mode[count - 1] implies the count should

Re: [PATCH] staging: tsl2x7x: Moved contents of the header to the source file.

On 03/23/2017 12:53 PM, Arushi Singhal wrote: > Moved the contents of the header(tsl2x7x.h) into the source file > tsl2x7x_core.c with the exception of the platform data struct which is > supposed to be used from somewhere else other than the driver. The platform_data struct uses the other

Re: [PATCH] selinux: Remove unnecessary check of array base in selinux_set_mapping()

On Wed, Mar 22, 2017 at 8:28 PM, Grant Grundler wrote: > Ping? Any feedback on this patch? It's on my list of patches to review, patience please. > On Thu, Mar 16, 2017 at 3:26 PM, Matthias Kaehlcke wrote: >> >> 'perms' will never be NULL since it

Re: [PATCH] blk-mq: don't complete un-started request in timeout handler

On Wed, Mar 22, 2017 at 11:58:17AM -0400, Keith Busch wrote: > On Tue, Mar 21, 2017 at 11:03:59PM -0400, Jens Axboe wrote: > > On 03/21/2017 10:14 PM, Ming Lei wrote: > > > When iterating busy requests in timeout handler, > > > if the STARTED flag of one request isn't set, that means > > > the

Re: [PATCH v3 2/3] mfd: intel_soc_pmic_bxtwc: Move inclusion to c-file

On Fri, 17 Mar 2017, Andy Shevchenko wrote: > There is no need to include intel_soc_pmic.h into header which doesn't > require it. > > Signed-off-by: Andy Shevchenko > --- > drivers/mfd/intel_soc_pmic_bxtwc.c | 1 + > include/linux/mfd/intel_bxtwc.h| 2 --

Re: [PATCH v4 1/7] mfd: rk808: fix up the chip id get failed

On Fri, 17 Mar 2017, Elaine Zhang wrote: > the rk8xx chip id is: > ((MSB << 8) | LSB) & 0xfff0 > > Signed-off-by: Elaine Zhang > --- > drivers/mfd/rk808.c | 21 +++-- > include/linux/mfd/rk808.h | 1 + > 2 files changed, 16 insertions(+), 6

Re: [PATCH] ARM: gemini: don't select SERIAL_OF_PLATFORM

On Thu, Mar 23, 2017 at 11:22 AM, Linus Walleij wrote: > On Tue, Mar 21, 2017 at 9:52 PM, Arnd Bergmann wrote: > >> We cannot select the option when SERIAL_8250 is not also set: >> >> warning: (ARCH_GEMINI) selects SERIAL_OF_PLATFORM which has unmet

Re: [PATCH v3 1/3] mfd: intel_soc_pmic: Fix a mess with compilation units

On Fri, 17 Mar 2017, Andy Shevchenko wrote: > Crystal Cove and Whiskey Cove are two different PMICs which are > installed on Intel Atom SoC based platforms. > > Moreover there are two independent drivers that by some reason were > supposed (*) to get into one kernel module. > > Fix the mess by

Re: [PATCH v18 0/3] USB Type-C Connector class

On Tue, Mar 21, 2017 at 01:56:45PM +0200, Heikki Krogerus wrote: > The USB Type-C class is meant to provide unified interface to the > userspace to present the USB Type-C ports in a system. Now applied, nice job, thanks for sticking with this, it's much appreciated. greg k-h

[PATCH] xen, fbfront: fix connecting to backend

Connecting to the backend isn't working reliably in xen-fbfront: in case XenbusStateInitWait of the backend has been missed the backend transition to XenbusStateConnected will trigger the connected state only without doing the actions required when the backend has connected. Cc:

[PATCH] xen, fbfront: add support for specifying size via xenstore

Today xen-fbfront supports specifying the display size via module parameters only. Add support for specifying the size via Xenstore in order to enable doing this easily via the domain's Xen configuration. Add an error message in case the configured display size conflicts with video memory size.

[PATCH 4/5] w83627ehf: Drop FSFE template and replace with SPDX License information

As indicated by checkpatch it makes sense to not use the FSFE Template about GPLv2+ Signed-off-by: Peter Huewe --- drivers/hwmon/w83627ehf.c | 15 ++- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/drivers/hwmon/w83627ehf.c

[PATCH] x86/boot: Support uncompressed kernel

Compressed kernel has its own drawback: uncompressing takes time. Even though the time is short enough to ignore for most cases but for cases that time is critical this is still a big number. In our on-going optimization for kernel boot time, the measured overall kernel boot time is ~90ms while

[PATCH 2/5] w83627ehf: Use octal values for access rights of sysfs files

As indicated by checkpatch, use the octal representation for the access rights. S_IWUSR | S_IRUGO => 0644 S_IRUGO => 0444 Signed-off-by: Peter Huewe --- drivers/hwmon/w83627ehf.c | 52 --- 1 file changed, 22 insertions(+), 30

[PATCH] isdn: use setup_timer

Use setup_timer() instead of init_timer() to simplify the code. Signed-off-by: Geliang Tang --- drivers/isdn/divert/isdn_divert.c | 9 +++-- drivers/isdn/hardware/eicon/divasi.c| 5 ++--- drivers/isdn/hardware/mISDN/hfcmulti.c | 10 --

Re: Updates, autofocus, 5Mpix mode on N900? Re: [RFC 08/13] smiapp-pll: Take existing divisor into account in minimum divisor check

Hi! > > Plus I have played with v4l-utils, and managed to implement autofocus > > and autoexposure -- it was easier than expected. I believe you > > mentioned you had some patches to automatically initialize the > > pipeline. Do you and can I have them? > > It was an early prototype and it

Re: [PATCH v2] kasan: report only the first error by default

On Thu, Mar 23, 2017 at 04:06:59PM +0300, Andrey Ryabinin wrote: > On 03/23/2017 03:41 PM, Mark Rutland wrote: > > Rather than trying to pick an arbitrarily large number, how about we use > > separate flags to determine whether we're in multi-shot mode, and > > whether a (oneshot) report has been

Re: [PATCH v4] KVM: VMX: Fix enable VPID even if INVVPID is not exposed in vmx capability

On 23.03.2017 03:39, Wanpeng Li wrote: > From: Wanpeng Li > > This can be reproduced by running L2 on L1, and disable VPID on L0 > if w/o commit "KVM: nVMX: Fix nested VPID vmx exec control", the L2 > crash as below: > > KVM: entry failed, hardware error 0x7 >

[PATCH] ASoC: WM8962: Let codec driver enable/disable its MCLK

From: Nicolin Chen WM8962 needs its MCLK when powerup in wm8962_resume(). Thus it's better to control the MCLK in codec driver. Thus remove the clock enable in machine dirver accordingly. While at it, get rid of imx_wm8962_remove function since it is now empty.

kvm: use-after-free function call in kvm_io_bus_destroy

Hello, I've got the following report while running syzkaller fuzzer on 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected kmalloc failure, most likely it's the root cause. FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 0

Re: [PATCH 4/4] tty/serial: sh-sci: remove uneeded IS_ERR_OR_NULL calls

On Thu, Mar 23, 2017 at 01:03:56PM +0100, Geert Uytterhoeven wrote: > Hi Uwe, > > On Thu, Mar 23, 2017 at 12:11 PM, Uwe Kleine-König > wrote: > >> Make sure to enable all drivers and subsystems you need when building > >> your kernel. That's always true. And may

Re: [PATCH] drm/i915/kvmgt: avoid dereferencing a potentially null info pointer

On Thu, Mar 23, 2017 at 12:22:30PM +, Colin King wrote: > From: Colin Ian King > > info is being checked to see if it is a null pointer, however, vpgu is > dereferencing info before this check, leading to a potential null > pointer dereference. If info is null,

Re: [PATCH] ARM: nommu: access ID_PFR1 only if CPUID scheme

Hi, On Thu, Mar 23, 2017 at 09:37:48PM +1000, Greg Ungerer wrote: > Tested-by: Greg Ungerer Thanks Greg Since there was no negative feedback yet, change has been deposited in rmk's patch system as 8665/1 Regards afzal

[RFC PATCH 0/2] Add hstate parameter to huge_pte_offset()

On architectures that support hugepages composed of contiguous pte as well as block entries at the same level in the page table, huge_pte_offset() is not able to determine the right offset to return when it encounters a swap entry (which is used to mark poisoned as well as migrated pages in the

Re: [PATCH 1/5] w83627ehf: Use hwmon_device_register_with_info and sensor groups

On 03/23/2017 06:05 AM, Peter Hüwe wrote: This is of course v2 of the series Forgot to add it to git-send-email, sorry. Shall I resend with v2 in subject? No, it's ok. At least you have a change log :-). Thanks, Guenter

Re: [PATCH v1] mfd: core: Preserve PLATFORM_DEVID_NONE

On Thu, 2017-03-23 at 11:21 +, Lee Jones wrote: > On Thu, 16 Mar 2017, Andy Shevchenko wrote: > > > There is a potential flaw if cell has id > 0 and is going to be > > registered with PLATFORM_DEVID_NONE. > > > > Ignore if PLATFORM_DEVID_NONE is supplied. > > This is a substantial change to

Re: [PATCH 11/11] staging: speakup: Fix alignment with parenthesis.

On Tue, Mar 21, 2017 at 05:12:35PM +0530, Arushi Singhal wrote: > This patch fixes the warnings reported by checkpatch.pl > for please use a blank line after function/struct/union/enum > declarations. That's not what this patch does at all! Please be more careful. greg k-h

[PATCH] nvmem: imx-ocotp: fix usage of "dev" pointers

Assign the correct dev pointer to struct ocotp_priv during probe. This is needed to display dev_* messages correctly. Furthermore harmonize the usage of dev (instead of >dev) in the probe function. Signed-off-by: Richard Leitner --- drivers/nvmem/imx-ocotp.c | 4

ata: WARNING in ata_qc_issue

Hello, The following program triggers WARNING in ata_qc_issue: https://gist.githubusercontent.com/dvyukov/3503afce181b7d48dabb421e10e70b00/raw/d049bd2128a8b1089497beb6104ba48c5550b4a8/gistfile1.txt [ cut here ] WARNING: CPU: 3 PID: 2956 at drivers/ata/libata-core.c:5317

[PATCH] auxdisplay: hd44780: Fix DT properties to include units of measurement

DT properties specifying physical properties should contain appropriate suffices indicating the units of measurement. Hence amend the HD44780 DT bindings to add "chars" suffixes to the "display-height" and "display-width" properties, and update the driver to parse them. Fixes: dd9502a9e9156dd8

[PATCH v2] staging:speakup: Fix alignment with parenthesis.

Fix checkpatch issues: "CHECK: Alignment should match open parenthesis". Signed-off-by: Arushi Singhal --- changes in v2 - change the commit message. drivers/staging/speakup/speakup_apollo.c | 2 +- drivers/staging/speakup/speakup_decext.c | 4 ++-- 2 files

[PATCH 2/8] pinctrl: meson: gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c index 8d5dd4772042..9bae2e3968af

[PATCH 3/8] pinctrl: meson: gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 31 +++ 1 file changed, 31 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index

[PATCH 5/8] ARM64: dts: meson-gxbb: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 63 + 1 file changed, 63 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index

[PATCH 4/8] pinctrl: meson: gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index a022a9e49113..a5a9b4f78636 100644

Re: Dell Inspiron 5558/0VNM2T hangs at resume from suspend when USB 3 is enabled

On 22.03.2017 19:51, Mathias Nyman wrote: On 22.03.2017 00:52, Diego Viola wrote: On Tue, Mar 21, 2017 at 12:29 PM, Diego Viola wrote: On Tue, Mar 21, 2017 at 10:04 AM, Diego Viola wrote: On Mon, Mar 20, 2017 at 8:15 PM, Diego Viola

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/2017 15:22, Marc Zyngier wrote: > On 23/03/17 13:05, Mason wrote: > >> +#define MSI_COUNT 32 > > Is this something that is hardcoded? Unlikely to ever change? The host bridge actually supports 256 MSIs. IIUC, what you suggested on IRC is that I support 256 in the driver, and only

[PATCH v5 1/4] syscalls: Restore address limit after a syscall

This patch ensures a syscall does not return to user-mode with a kernel address limit. If that happened, a process can corrupt kernel-mode memory and elevate privileges. For example, it would mitigation this bug: - https://bugs.chromium.org/p/project-zero/issues/detail?id=990 The

[PATCH v5 3/4] arm/syscalls: Specific usage of verify_pre_usermode_state

Implement specific usage of verify_pre_usermode_state for user-mode returns for arm. --- Based on next-20170322 --- arch/arm/Kconfig | 1 + arch/arm/kernel/entry-common.S | 16 +++- 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig

RE: [PATCH] Add initial SX3000b platform code to MIPS arch

Will be sending a revised version splitting the irqchip related code to a different patch and using a generic platform code... -Original Message- From: Amit Kama IL Sent: Wednesday, March 22, 2017 7:38 AM To: 'r...@linux-mips.org' Cc: 'devicet...@vger.kernel.org'

[PATCH -v3 0/8] PI vs SCHED_DEADLINE fixes

Now that this pesky little problem with futexes is (hopefully) dealt with; https://lkml.kernel.org/r/20170322103547.756091...@infradead.org We can get on with fixing the actual bug this all started out with. These patches, started by Xunlei Pang, rework the PI infrastructure a bit fixing

[PATCH -v3 1/8] rtmutex: Deboost before waking up the top waiter

From: Xunlei Pang We should deboost before waking the high-priority task, such that we don't run two tasks with the same "state" (priority, deadline, sched_class, etc). In order to make sure the boosting task doesn't start running between unlock and deboost (due to 'spurious'

[PATCH -v3 7/8] rtmutex: Fix PI chain order integrity

rt_mutex_waiter::prio is a copy of task_struct::prio which is updated during the PI chain walk, such that the PI chain order isn't messed up by (asynchronous) task state updates. Currently rt_mutex_waiter_less() uses task state for deadline tasks; this is broken, since the task state can, as said

[PATCH -v3 5/8] sched/rtmutex: Refactor rt_mutex_setprio()

With the introduction of SCHED_DEADLINE the whole notion that priority is a single number is gone, therefore the @prio argument to rt_mutex_setprio() doesn't make sense anymore. So rework the code to pass a pi_task instead. Note this also fixes a problem with pi_top_task caching; previously we

[PATCH -v3 4/8] rtmutex: Clean up

Previous patches changed the meaning of the return value of rt_mutex_slowunlock(); update comments and code to reflect this. Signed-off-by: Peter Zijlstra (Intel) --- kernel/futex.c |7 --- kernel/locking/rtmutex.c| 28

[PATCH v3 2/7] arm64: marvell: enable the Armada 37xx pinctrl driver

This commit makes sure the driver for the Armada 37xx pin controller is enabled. Signed-off-by: Gregory CLEMENT --- arch/arm64/Kconfig.platforms | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms

Re: [REGRESSION] 07ec51480b5e ("virtio_pci: use shared interrupts for virtqueues") causes crashes in guest

On Thu, Mar 23, 2017 at 01:13:50PM +0800, Jason Wang wrote: > >From 312859b596e83a2164a8430343d31fce2a5ad808 Mon Sep 17 00:00:00 2001 > From: Jason Wang > Date: Thu, 23 Mar 2017 13:07:16 +0800 > Subject: [PATCH] virtio_pci: fix out of bound access for msix_names > >

[PATCH v3 0/7] Add support for pinctrl/gpio on Armada 37xx

Hi, In this third version I finally managed to use gpio-ranges from the device tree. For the record, this series adds support for the pin and gpio controllers present on the Armada 37xx SoCs. Each Armada 37xx SoC comes with 2 pin controllers: one on the south bridge (managing 28 pins) and one on

[PATCH v3 4/7] pinctrl: armada-37xx: Add gpio support

GPIO management is pretty simple and is part of the same IP than the pin controller for the Armada 37xx SoCs. This patch adds the GPIO support to the pinctrl-armada-37xx.c file, it also allows sharing common functions between the gpiolib and the pinctrl drivers. Signed-off-by: Gregory CLEMENT

[PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs

If a given cpu is not in cpu_present and cpu hotplug is disabled, arch can skip setting up the cpu_dev. Arch cpuidle driver should pass correct cpu mask for registration, but failing to do so by the driver causes error to propagate and crash like this: [ 30.076045] Unable to handle kernel

[PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). On PowerNV platform cpu_present could be less than cpu_possible in cases where firmware detects the cpu, but it is not available to the OS. When CONFIG_HOTPLUG_CPU=n, such cpus are not hotplugable at runtime and hence we skip

Re: [PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan wrote: > drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). > On PowerNV platform cpu_present could be less than cpu_possible in cases > where firmware detects the cpu, but it is not available

Re: [PATCH v2 3/5] mm: use a dedicated workqueue for the free workers

On 03/22/2017 01:41 AM, Aaron Lu wrote: > On Wed, Mar 22, 2017 at 03:33:35PM +0900, Minchan Kim wrote: >> On Wed, Mar 15, 2017 at 05:00:02PM +0800, Aaron Lu wrote: >>> Introduce a workqueue for all the free workers so that user can fine >>> tune how many workers can be active through sysfs

Re: deadlock in synchronize_srcu() in debugfs?

On Thu, Mar 23, 2017 at 03:54:46PM +0100, Johannes Berg wrote: > Hi, > > Before I go hunting - has anyone seen a deadlock in synchronize_srcu() > in debugfs_remove() before? We're observing that with our (backported, > but very recent) driver against 4.9 (and 4.10, I think), but there are > no

Re: [PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

* Rafael J. Wysocki [2017-03-23 16:28:31]: > On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan > wrote: > > drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). > > On PowerNV platform cpu_present could be less than

Re: stmmac: Performance regression after commit aff3d9eff843 "net: stmmac: enable multiple buffers"

RX and TX queues to use */ - plat->tx_queues_to_use = 1; - plat->rx_queues_to_use = 1; - - /* Disable Priority config by default */ - plat->tx_queues_cfg[0].use_prio = false; - plat->rx_queues_cfg[0].use_prio = false; - - /* Disable RX queues routing

netlink: NULL timer crash

Hello, The following program triggers call of NULL timer func: https://gist.githubusercontent.com/dvyukov/c210d01c74b911273469a93862ea7788/raw/2a3182772a6a6e20af3e71c02c2a1c2895d803fb/gistfile1.txt BUG: unable to handle kernel NULL pointer dereference at (null) IP: (null)

Re: [PATCH] hangcheck-timer: Fix typo in comment

On Thu, Mar 23, 2017 at 05:08:00PM +0800, Shile Zhang wrote: > Fix the typo "alloted" -> "allotted" in comment. > > Signed-off-by: Shile Zhang > --- > drivers/char/hangcheck-timer.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) You sent me two different

[RFC PATCH 1/2] mm/hugetlb.c: add hstate parameter to huge_pte_offset()

A poisoned or migrated hugepage is stored as a swap entry in the page tables. On architectures that support hugepages consisting of contiguous page table entries (such as on arm64) this leads to ambiguity in determining the right page table entry to return in huge_pte_offset() when a poisoned

Re: net/kcm: use-after-free in kcm_wq

On Fri, Mar 3, 2017 at 9:03 PM, Cong Wang wrote: > On Fri, Mar 3, 2017 at 2:11 AM, Dmitry Vyukov wrote: >> Also like this one: >> >> == >> BUG: KASAN: use-after-free in atomic_long_read

[RFC PATCH 2/2] arm64: hugetlbpages: Correctly handle swap entries in huge_pte_offset()

huge_pte_offset() does not correctly handle poisoned or migration page table entries. Not knowing the size of the hugepage entry being requested only compounded the problem. The recently added hstate parameter can be used to determine the size of hugepage being accessed. Use the size to find the

[RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

I think this version is ready for review. It has all the required bits and pieces. I still have a few questions, embedded as comments in the code. (Missing are ancillary changes to Kconfig, Makefile) --- drivers/pci/host/pcie-tango.c | 350 ++ 1 file

security, hugetlbfs: write to user memory in hugetlbfs_destroy_inode

Hello, I've got the following report while running syzkaller fuzzer on 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected kmalloc failure in inode_alloc_security, most likely it's the root cause. FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0,

[PATCH] staging: media: atomisp: use kvmalloc and kvfree

Use kvmalloc() and kvfree() instead of open-coding. Signed-off-by: Geliang Tang --- drivers/staging/media/atomisp/pci/atomisp2/atomisp_cmd.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git

[PATCH] staging: media: atomisp: fix build error

Fix the following build error: CC drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.o drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.c:52:2: error: excess elements in array initializer [-Werror] "i", /* ion */ ^~~ drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm.c:52:2: note:

Re: [PATCH 05/11] staging: speakup: Remove multiple assignments

On Tue, Mar 21, 2017 at 05:12:29PM +0530, Arushi Singhal wrote: > This patch fixes the checkpatch.pl warning "multiple assignments > should be avoided." > > Signed-off-by: Arushi Singhal > --- > drivers/staging/speakup/main.c | 3 ++- > 1 file changed, 2

Re: [PATCH 02/11] staging: speakup: Remove multiple assignments

On Tue, Mar 21, 2017 at 05:12:26PM +0530, Arushi Singhal wrote: > This patch fixes the checkpatch.pl warning "multiple assignments > should be avoided." > > Signed-off-by: Arushi Singhal > --- > drivers/staging/speakup/main.c | 18 -- > 1 file

Re: [PATCH] hibernation: on 32-bit x86, disabled in favor of KASLR

On 23.03.2017 03:27, Kees Cook wrote: This is a modified revert of commit 65fe935dd238 ("x86/KASLR, x86/power: Remove x86 hibernation restrictions"), since it appears that 32-bit hibernation still can't support KASLR. 64-bit is fine. Since people have been running with KASLR by default on 32-bit

Re: [PATCH 2/5] mfd: intel_soc_pmic: Select designware i2c-bus driver

On Wed, 22 Mar 2017, Andy Shevchenko wrote: > On Wed, 2017-03-22 at 12:29 +0100, Hans de Goede wrote: > > The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be > > available before other drivers using it are loaded, which is why > > INTEL_SOC_PMIC is a bool. > > > > Just having

[PATCH 1/8] pinctrl: meson: gxbb: add i2s output pins

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 31 ++ 1 file changed, 31 insertions(+) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c index

Re: [PATCH v3 04/11] Documentation: DT: bindings: mfd: add A33 GPADC binding

On Tue, 21 Mar 2017, Quentin Schulz wrote: > This patch adds documentation for the A33 GPADC binding. > > Signed-off-by: Quentin Schulz > --- > > v3: > - fixed missing allwinner in front of compatible, > - updated compatible to allwinner,sun8i-a33-ths to

[PATCH 6/8] ARM64: dts: meson-gxbb: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi index

[PATCH 8/8] ARM64: dts: meson-gxl: add spdif output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 21 + 1 file changed, 21 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index 88ad3490c124..8f57e74b719c

[PATCH 7/8] ARM64: dts: meson-gxl: add i2s output pins

Signed-off-by: Jerome Brunet --- arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 62 ++ 1 file changed, 62 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi index

Re: [tip:sched/urgent] sched/clock: Fix clear_sched_clock_stable() preempt wobbly

On Thu, Mar 23, 2017 at 02:10:47AM -0700, tip-bot for Peter Zijlstra wrote: > Commit-ID: 71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Gitweb: http://git.kernel.org/tip/71fdb70eb48784c1f28cdf2e67c4c587dd7f2594 > Author: Peter Zijlstra > AuthorDate: Mon, 13 Mar 2017

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