Hello,
On Thu, Mar 23, 2017 at 11:20:39AM +0100, Geert Uytterhoeven wrote:
> But having the error breaks setups where the GPIO is optional and does
> not exist.
so the right way forward is to check harder in the situation where
-ENOSYS was returned before to determine if there is really no GPIO
POKE?
The linking status may be changed when autosuspend. And, after
autoresume, the driver may try to transmit packets when the device
is carrier off, because the interrupt transfer doesn't update the
linking status, yet. And, if the device is in ALDPS mode, the device
would stop working.
The another
On Thu, Mar 23, 2017 at 11:50 AM, Joerg Roedel wrote:
> On Thu, Mar 23, 2017 at 02:06:44AM +0100, Rafael J. Wysocki wrote:
>> The main problem is that representing anything hot-removable as a
>> platform device is inherently fragile, as the platform bus type has no
>> idea whatever about things
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 a pretty tried and tested piece of
sub-system code. Can you put
Under extremely heavy uses of padata, crashes occur, and with list
debugging turned on, this happens instead:
[87487.298728] WARNING: CPU: 1 PID: 882 at lib/list_debug.c:33
__list_add+0xae/0x130
[87487.301868] list_add corruption. prev->next should be next
(b17abfc043d0), but was
On Thu, 23 Mar 2017, michael.henner...@analog.com wrote:
> From: Michael Hennerich
comments below
> Signed-off-by: Michael Hennerich
> ---
> .../devicetree/bindings/iio/adc/ltc2497.txt| 13 +
> MAINTAINERS| 1 +
> drivers/iio/adc/Kconfig
s/the\ the/the
Signed-off-by: Viresh Kumar
---
init/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/main.c b/init/main.c
index f9c9d9948203..717b2ab803e5 100644
--- a/init/main.c
+++ b/init/main.c
@@ -495,7 +495,7 @@ asmlinkage __visible void __init
Add a tab before it to follow standard practices. Also add the missing
full stop '.'.
Signed-off-by: Viresh Kumar
---
init/main.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/init/main.c b/init/main.c
index 717b2ab803e5..7bb8e845a8a1 100644
--- a/init/main.c
+++
On Thu, Mar 23, 2017 at 01:23:56PM +1000, Peter Hutterer wrote:
> On Wed, Mar 22, 2017 at 11:54:48PM -0300, Marcos Paulo de Souza wrote:
> > Hi Peter,
> >
> > first of all, thanks a lot for reading this patch so quickly and to
> > point a lot of things to make this doc way better.
> >
> > See
On Thu, Mar 23, 2017 at 11:47 AM, Linus Walleij
wrote:
> On Mon, Mar 20, 2017 at 7:44 PM, Krzysztof Kozlowski wrote:
> > On Fri, Feb 17, 2017 at 01:52:14PM +, Charles Keepax wrote:
> >> On Fri, Feb 17, 2017 at 03:35:04PM +0200, Krzysztof Kozlowski wrote:
> >> > On Thu, Feb 16, 2017 at
On Thu, Mar 23, 2017 at 12:38 PM, Linus Walleij
wrote:
> On Mon, Mar 20, 2017 at 5:48 PM, Krzysztof Kozlowski wrote:
>
>> Add a Git tree on @kernel.org for maintaining the Samsung pinctrl
>> drivers. The tree will be maintained in a shared model between current
>> Samsung pinctrl maintainers.
'ptr' is never used after setting 'rt_rq' and there is no need to update
it.
Signed-off-by: Viresh Kumar
---
kernel/sched/core.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 6d6cad9a46af..bd33a05d038b 100644
--- a/kernel/sched/core.c
+++
Hi,
Here are few minor cleanups for the sched core. The first three tries to
avoid reinitializing memory which is already set to zero and the last
one drops an unused statement.
--
viresh
Viresh Kumar (4):
sched: topology: drop memset() from init_rootdomain()
sched: cpudeadline: don't
The struct cpupri passed to cpupri_init() is already initialized to
zero. Don't do that again.
Signed-off-by: Viresh Kumar
---
kernel/sched/cpupri.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/sched/cpupri.c b/kernel/sched/cpupri.c
index 981fcd7dc394..d6165d87ef3e 100644
---
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 fba235c7d026..a51e91bf3907
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
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 +
On 22/03/17 06:27, Zhen Lei wrote:
> Keep these four variables type consistent with the paramters of function
> __alloc_and_insert_iova_range and the members of struct iova:
>
> 1. static int __alloc_and_insert_iova_range(struct iova_domain *iovad,
> unsigned long size, unsigned
On 03/23/2017 12:36 PM, Arushi Singhal wrote:
> 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
> ---
>
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 +++---
1 file changed, 11 insertions(+), 11
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 not
> >> be less than 1 so
On Fri, 17 Mar 2017, Charles Keepax wrote:
> Now the wm831x-core has basic DT support we can update this driver to
> allow use of the GPIOs within a device tree system.
>
> Signed-off-by: Charles Keepax
> Acked-by: Linus Walleij
> ---
>
> No changes since v4, still should go through Lee's
On Fri, 17 Mar 2017, Charles Keepax wrote:
> Add the basic ability to register the device through device tree, more
> work is needed to get each individual sub-driver functioning correctly
> but this is enough to get the device to probe from device tree.
>
> Signed-off-by: Charles Keepax
> ---
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
> ---
>
> Changes since v4:
> -
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
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
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
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
From: Colin Ian King
All error paths to label out_term2 result in sess being null, so the
check for sess being non-null and the call to put_sess is dead code
and can therefore be removed.
Detected with CoverityScan, CID#1420664 ("Logically dead code")
Signed-off-by: Colin Ian King
---
On Fri, 17 Mar 2017, Enric Balletbo i Serra wrote:
> From: Shawn Nematbakhsh
>
> This adds support for the ChromeOS LPC Microchip Embedded Controller
> (mec1322) variant.
>
> mec1322 accesses I/O region [800h, 9ffh] through embedded memory
> interface (EMI) rather than LPC.
>
> Signed-off-by:
On Fri, 17 Mar 2017, Enric Balletbo i Serra wrote:
> From: Shawn Nematbakhsh
>
> Call common functions for read / write to prepare support for future
> LPC protocol variants which use different I/O ops than inb / outb.
>
> Signed-off-by: Shawn Nematbakhsh
> Signed-off-by: Thierry Escande
>
Hi Hemant, Maddy,
On Thu, Mar 16, 2017 at 01:05:00PM +0530, Madhavan Srinivasan wrote:
> From: Hemant Kumar
>
> Adds cpumask attribute to be used by each IMC pmu. Only one cpu (any
> online CPU) from each chip for nest PMUs is designated to read counters.
>
> On CPU hotplug, dying CPU is
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.
Signed-off-by: Arushi Singhal
---
drivers/staging/iio/light/tsl2x7x.h | 57
Enable the Tegra BPMP I2C adapter by default if the Tegra BPMP itself
is enabled. This adapter is used as the I2C interface for the PMIC on
the Tegra186 Jetson-TX2 platform.
Signed-off-by: Jon Hunter
Acked-by: Thierry Reding
---
Changes since V1:
- Dropped redundant 'if' condition from
From: Colin Ian King
The call to v4ls_m2m_get_vq is only used to get the return value
which is not being used, so it appears to be redundant and can
be removed.
Detected with CoverityScan, CID#1420674 ("Useless call")
Signed-off-by: Colin Ian King
---
On Thu, Mar 23, 2017 at 12:51 PM, Lee Jones wrote:
> 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
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
On Wed 2017-03-22 18:59:20, Peter Zijlstra wrote:
> On Mon, Mar 06, 2017 at 09:45:50PM +0900, Sergey Senozhatsky wrote:
> > sysrq is potentially even trickier. can we always wake_up() kernel
> > thread from sysrq? there probably might be cases when we can't rely
> > on the scheduler.
>
> sysrq
On Mon, Mar 20, 2017 at 01:34:19PM -0700, Andrey Smirnov wrote:
> On Mon, Mar 20, 2017 at 12:03 AM, Dong Aisheng wrote:
> > On Thu, Mar 16, 2017 at 06:30:50AM -0700, Andrey Smirnov wrote:
> >> Add code allowing for control of various power domains managed by GPCv2
> >> IP block found in i.MX7
Hi Michel,
On 23 March 2017 at 08:53, Michel Dänzer wrote:
> Otherwise this can also prevent modesets e.g. for switching VTs, when
> multiple monitors with different native resolutions are connected.
>
> The depths must match though, so keep the != test for that.
>
> Also update the DRM_DEBUG
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
> EAX= EBX=
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.
Signed-off-by: Nicolin Chen
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 indeed be hard to debug (e.g. what
>> kernel options do I need to make systemd work?).
>
> It's worse here. If
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 isn't a plain pointer but an array
>> of u32
Hello,
I've got the following report while running syzkaller fuzzer. Note the
preceding kmem_cache_alloc injected failure, it's most likely the root
cause.
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 1 PID: 21839 Comm: syz-executor4 Not
On Thu 2017-03-23 18:00:42, Sergey Senozhatsky wrote:
> On (03/20/17 17:09), Petr Mladek wrote:
> [..]
> >
> > BTW: wake_up_klogd_work does not need to be per-CPU as well.
> > irq_work infrastructure heavily uses per-CPU variables.
> > But a global struct irq_work is safe, see irq_work_claim().
>
On 22/03/17 06:27, Zhen Lei wrote:
> Below judgement can only be satisfied at the last time, which produced 2N
> judgements(suppose N times failed, 0 or 1 time successed) in vain.
>
> if ((pfn >= iova->pfn_lo) && (pfn <= iova->pfn_hi)) {
> return iova;
> }
For me, GCC (6.2.1 AArch64) seems
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
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
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 direct
>> dependencies (TTY && HAS_IOMEM &&
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 --
> 2 files changed, 1
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 deletions(-)
For my own
On Fri, 17 Mar 2017, Andy Shevchenko wrote:
> For better understanding of relationship between headers and modules
> rename:
> intel_bxtwc.h -> intel_soc_pmic_bxtwc.h
>
> While here, remove file name from the file itself.
>
> Signed-off-by: Andy Shevchenko
> ---
>
On Fri, 17 Mar 2017, Elaine Zhang wrote:
> Signed-off-by: Elaine Zhang
> ---
> include/linux/mfd/rk808.h | 119
> ++
> 1 file changed, 119 insertions(+)
>
> diff --git a/include/linux/mfd/rk808.h b/include/linux/mfd/rk808.h
> index
On Thursday 23 March 2017 12:15 AM, Andy Shevchenko wrote:
> On Tue, Mar 21, 2017 at 3:36 PM, Vignesh R wrote:
>> Introduce a field to store name of uart_port that can be used to easily
>> identify uart port instances on a system that has more than one uart
>
> uart -> UART
>
>> instance. The
Hello,
I've got the following report while running syzkaller fuzzer on
093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Not 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 PID:
On 03/22/2017 05:32 PM, Andy Lutomirski wrote:
> Hi all-
>
> This applies to tip:x86/mm. For ease of testing, the series is here, too:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/tag/?h=review_20170322_gdt_and_wp
>
> This fixes a few issues, most of which appear to be
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 requires vpgu to exist. We can
Hello,
I've got the following report while running syzkaller fuzzer on
093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Unfortunately this is not
reproducible so far.
==
BUG: KASAN: use-after-free in __lock_acquire+0x39df/0x3a80
On Fri, 17 Mar 2017, Elaine Zhang wrote:
> The RK805 chip is a Power Management IC (PMIC) for multimedia and handheld
> devices. It contains the following components:
>
> - Regulators
> - RTC
> - Clocking
>
> Both RK808 and RK805 chips are using a similar register map,
> so we can
On Thursday 23 March 2017 12:16 AM, Andy Shevchenko wrote:
> On Tue, Mar 21, 2017 at 3:36 PM, Vignesh R wrote:
>> This series adds name attribute to uart_port struct inorder to store
>> name of the tty port that will help in identify different uart
>> instances.
>> This patch series is based on
On Fri, 17 Mar 2017, Elaine Zhang wrote:
> Add device tree bindings documentation for Rockchip's RK805 PMIC.
>
> Signed-off-by: Elaine Zhang
> ---
> Documentation/devicetree/bindings/mfd/rk808.txt | 20 +++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git
Also agree with Suzuki's excellent summary.
A couple of notes on using EDPRCR
The logic for this assuming a correctly implemented system should be
something like.
if (prsr() == powered_down) { // if we are powered down request power up.
sw_unlock() // ensure that the sw lock
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
EAX= EBX= ECX= EDX=000306c3
ESI= EDI=
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-iio-input-v4.12
for you to fetch changes up to
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
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 indeed be hard to debug (e.g.
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, then the error message being
On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote:
> + kasan_multi_shot
> + [KNL] Enforce KASAN (Kernel Address Sanitizer) to print
> + report on every invalid memory access. Without this
> + parameter KASAN will print
On 2017-03-22 21:32, Scot Doyle wrote:
On Wed, 22 Mar 2017, Tim Gardner wrote:
BugLink: http://bugs.launchpad.net/bugs/869017
Console blanking is not enabling DPMS power saving (thereby negating any
power-saving benefit), and is simply turning the screen content blank. This
means that any
Hi Uwe,
On Thu, Mar 23, 2017 at 1:34 PM, Uwe Kleine-König
wrote:
> On Thu, Mar 23, 2017 at 01:03:56PM +0100, Geert Uytterhoeven wrote:
>> 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.
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
include/linux/kvm_host.h | 5 +
2
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
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:
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.
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)
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
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
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
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 patches, with the same
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
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
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
>> include/linux/compiler.h:254 [inline] at
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
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:
>>>
>>> warning: (ARCH_GEMINI) selects
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 b/drivers/hwmon/w83627ehf.c
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
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
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
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 deletions(-)
diff --git
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 b/drivers/hwmon/w83627ehf.c
index
This is of course v2 of the series
Forgot to add it to git-send-email, sorry.
Shall I resend with v2 in subject?
Peter
On 03/23/2017 03:41 PM, Mark Rutland wrote:
> On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote:
>> +kasan_multi_shot
>> +[KNL] Enforce KASAN (Kernel Address Sanitizer) to print
>> +report on every invalid memory access. Without this
>> +
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
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,
On Thu, Mar 23, 2017 at 2:06 PM, Dmitry Vyukov wrote:
> 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.
>
>
>
Hi Maddy, Hemant, Anju,
On Thu, Mar 16, 2017 at 01:05:02PM +0530, Madhavan Srinivasan wrote:
[..snip..]
> +
> +static void core_imc_change_cpu_context(int old_cpu, int new_cpu)
> +{
> + if (!core_imc_pmu)
> + return;
> + perf_pmu_migrate_context(_imc_pmu->pmu, old_cpu,
On 23 March 2017 at 11:45, Bean Huo (beanhuo) wrote:
> Hi,
>
>>On 19 March 2017 at 01:45, Bean Huo (beanhuo) wrote:
>>> This patch fixes the issue that mmc_blk_issue_rq still flushes cache
>>> when eMMC cache has already been off through user space tool, such as
>>> mmc-utils.
>>> The reason is
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
1201 - 1300 of 1994 matches
Mail list logo
