On 01/24/2017 05:29 PM, Jarkko Sakkinen wrote:
On Mon, Jan 23, 2017 at 10:11:48PM +0530, Nayna wrote:
On 01/23/2017 08:49 PM, Jarkko Sakkinen wrote:
On Fri, Jan 20, 2017 at 12:05:13PM -0500, Nayna Jain wrote:
The current TPM 2.0 device driver extends only the SHA1 PCR bank
but the TCG Spec
On 01/23/2017 04:39 PM, Mel Gorman wrote:
> Many workloads that allocate pages are not handling an interrupt at a
> time. As allocation requests may be from IRQ context, it's necessary to
> disable/enable IRQs for every page allocation. This cost is the bulk
> of the free path but also a significan
On Mon, Jan 23, 2017 at 06:04:42PM +0100, Peter Zijlstra wrote:
> On Mon, Jan 23, 2017 at 02:30:12PM +0100, Dmitry Vyukov wrote:
> > Hello,
> >
> > The following program triggers use-after-free in perf_event_for_each:
> > https://gist.githubusercontent.com/dvyukov/f1c354a8356e42f4d0b3d912e1bec956/
VIRTIO_GPU_F_VIRGL is added in features list only
for LE kernel, so we must check for it only on LE kernel,
otherwise virtio_has_feature() calls BUG() and
crashes the kernel.
Suggested-by: Gerd Hoffmann
Signed-off-by: Laurent Vivier
---
Note: this patch has been actually written by Gerd,
but to
On Mon, Jan 23, 2017 at 04:14:59PM +0100, linux-kernel-...@beckhoff.com wrote:
> From: Patrick Bruenn
>
> The pinmux configuration in device tree is different from manual
> muxing in /board/freescale/mx53loco/mx53loco.c
> It seems the device tree configuration is never used by any kernel
> driver
Back before commit 1dccb598df54 ("arm64: simplify dma_get_ops"), for arm64,
devices that do not manually set a dma_ops are automatically configured to
use swiotlb_dma_ops, since this was hard-coded as the global "dma_ops" in
arm64_dma_init().
Now, the global "dma_ops" has been removed, and all dev
On Tue, Jan 24, 2017 at 2:17 PM, Peter Zijlstra wrote:
> On Mon, Jan 23, 2017 at 06:04:42PM +0100, Peter Zijlstra wrote:
>> On Mon, Jan 23, 2017 at 02:30:12PM +0100, Dmitry Vyukov wrote:
>> > Hello,
>> >
>> > The following program triggers use-after-free in perf_event_for_each:
>> > https://gist.g
On Tue, Jan 24, 2017 at 11:01:42AM +0100, Matias Bjørling wrote:
> Yup. That fixes it. Should I put together the patch, or will you take
> care of it?
I'll send it out. Of course with proper reporting credits for you.
On 01/24/2017 02:34 PM, Christoph Hellwig wrote:
> On Tue, Jan 24, 2017 at 11:01:42AM +0100, Matias Bjørling wrote:
>> Yup. That fixes it. Should I put together the patch, or will you take
>> care of it?
>
> I'll send it out. Of course with proper reporting credits for you.
>
Awesome. Thanks
Le 11/01/2017 à 14:50, David Engraf a écrit :
> On newer boards the TC can be read as single 32 bit value without locking.
> Thus the clock can be used as reference for sched_clock which is much more
> accurate than the jiffies implementation.
>
> Tested on a Atmel SAMA5D2 board.
>
> Signed-off-b
Le 23/01/2017 à 14:59, Daniel Lezcano a écrit :
> On Wed, Jan 11, 2017 at 02:50:59PM +0100, David Engraf wrote:
>> On newer boards the TC can be read as single 32 bit value without locking.
>> Thus the clock can be used as reference for sched_clock which is much more
>> accurate than the jiffies im
On certain HiSilicon platforms (Hip05/Hip07) the GIC ITS and
PCIe RC deviates from the standard implementation and this breaks
PCIe MSI functionality when SMMU is enabled.
The HiSilicon erratum 161010801 describes this limitation of certain
HiSilicon platforms to support the SMMU mappings for MSI
When hardware flow-control is disabled, manual toggling of the UART's
reset line (RTS) using userland applications (e.g. stty) is not
possible, since the ASC IP does not provide this functionality in the
same was as some other IPs do. Thus, we have to do this manually.
This set ensures the correc
When hardware flow-control is disabled, manual toggling of the UART's
reset line (RTS) using userland applications (e.g. stty) is not
possible, since the ASC IP does not provide this functionality in the
same was as some other IPs do. Thus, we have to do this manually.
This patch configures the UA
When hardware flow-control is disabled, manual toggling of the UART's
reset line (RTS) using userland applications (e.g. stty) is not
possible, since the ASC IP does not provide this functionality in the
same was as some other IPs do. Thus, we have to do this manually.
This patch ensures that whe
Each serial port which supports HW flow-control should have 2 Pinctrl
groups. Once for when HW flow-control is in progress, where the IP
will take over controlling the lines and another group which enables
the lines to be toggled using GPIO mechanisms.
Signed-off-by: Lee Jones
---
arch/arm/boot
Hardware flow-control capability must be specified at a platform
level in order to inform the ASC driver that the platform is capable
(i.e. are the lines wired up, etc). STiH4{07,10} devices are indeed
capable, so let's provide the property.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih40
Having just defined some new Pinctrl groups for when when HW flow-
control is {en,dis}abled, let's reference them for use within the
driver.
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih407-family.dtsi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/d
From: Gwendal Grignou
Handle the barometer sensor presented by the ChromeOS EC Sensor hub.
Signed-off-by: Gwendal Grignou
Signed-off-by: Enric Balletbo Serra
---
drivers/iio/pressure/Kconfig | 10 ++
drivers/iio/pressure/Makefile | 1 +
drivers/iio/pressure/cros_ec_baro.c
Until this point, it has not been possible for userland serial
applications (e.g. stty) to toggle the UART RTS line. This can
be useful with certain configurations. For example, when using
a Mezzanine on a Linaro 96board, RTS line is used to take the
on-board microcontroller in and out of reset.
The datasheet states:
"If the MODE field selects an 8-bit frame then this [parity error] bit
is undefined. Software should ignore this bit when reading 8-bit frames."
Signed-off-by: Lee Jones
---
drivers/tty/serial/st-asc.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-
There are now 2 possible separate/different Pinctrl states which can
be provided from platform data. One which encompasses the lines
required for HW flow-control (CTS/RTS) and another which does not
specify these lines, such that they can be used via GPIO mechanisms
for manually toggling (i.e. fro
On 24.01.2017 13:01, Jarkko Sakkinen wrote:
> On Mon, Jan 23, 2017 at 06:23:55PM +0100, Maciej S. Szmigiero wrote:
>> On 16.01.2017 17:39, Jarkko Sakkinen wrote:
>>> On Mon, Jan 16, 2017 at 03:58:26PM +0100, Maciej S. Szmigiero wrote:
On 16.01.2017 14:55, Jarkko Sakkinen wrote:
> On Mon, J
Hello.
I'm see this crash on 4.9.[3|5] stable series kernel.
[ 1297.357388] nvidiafb: Device ID: 10de104a
[ 1297.379856] nvidiafb: CRTC0 analog not found
[ 1297.403834] nvidiafb: CRTC1 analog not found
[ 1298.147858] nvidiafb: Unable to detect display type...
[ 1298.147873] ...Using default of CR
On Mon 23-01-17 09:26:44, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -11.1% regression of fsmark.files_per_sec due to commit:
>
>
> commit: 5e56dfbd837421b7fa3c6c06018c6701e2704917 ("mm, vmscan: consider
> eligible zones in get_scan_count")
> https://git.kernel.org/pub/scm/li
This erratum describes the limitation of certain HiSilicon platforms
to support the SMMU mappings for MSI transactions and on those platforms
the MSI transactions has to be bypassed by SMMU. The IIDR register of the
GICv3 ITS on these platforms are not properly populated to differentiate
the hardwa
On Tue, Jan 24, 2017 at 02:57:56PM +0200, Mika Westerberg wrote:
> On Tue, Jan 24, 2017 at 01:53:53PM +0100, Linus Walleij wrote:
> > On Tue, Jan 24, 2017 at 12:11 PM, Mika Westerberg
> > wrote:
> > > On Mon, Jan 23, 2017 at 06:11:07PM +0100, Johan Hovold wrote:
> > >> On Mon, Jan 23, 2017 at 03:3
On 01/23/2017 01:59 PM, Boris Ostrovsky wrote:
> On 01/23/2017 05:09 AM, Juergen Gross wrote:
>> Handling of multiple concurrent Xenstore accesses through xenbus driver
>> either from the kernel or user land is rather lame today: xenbus is
>> capable to have one access active only at one point of t
Since commit 2164a476205ccc ("usb: dwc3: set SUSPHY bit for all cores"),
the USB ports on odroid-XU4 don't work anymore.
Inserting an usb key (USB2.0) on the USB3.0 port result in:
[ 64.488264] xhci-hcd xhci-hcd.2.auto: Port resume took longer than 2
msec, port status = 0xc400fe3
[ 74.568
On Tue, Jan 24, 2017 at 02:29:19PM +0100, Dmitry Vyukov wrote:
>
> Try to run more parallel processes at the same time.
> This program will run 32 processes in a tight loop:
> https://gist.githubusercontent.com/dvyukov/b36aa4398bb016923278fccdd1cc5b45/raw/9607078fd5ac2daf769c13d82561a83e17b06032/g
On Tue, Jan 24, 2017 at 03:34:06AM +0530, afzal mohammed wrote:
> Enable EXT4_FS to have rootfs in EXT[2-4].
>
> Other changes are result of savedefconfig keeping minimal config (even
> without enabling EXT4_FS, these would be present).
>
> Signed-off-by: afzal mohammed
Applied, thanks.
Hi,
These patches try to address issues I've encountered during integration of
userfaultfd with CRIU.
Previously added userfaultfd events for fork(), madvise() and mremap()
unfortunately do not cover all possible changes to a process virtual memory
layout required for uffd monitor.
When one or mor
The current quirk mechanism is based on the IIDR register.
This introduces a ACPI MADT OEM information based erratum
support for platforms on which the IIDR registers are not
properly populated.
Signed-off-by: shameer
---
drivers/irqchip/irq-gic-v3-its.c | 62
Allow userfaultfd monitor track termination of the processes that have
memory backed by the uffd.
Signed-off-by: Mike Rapoport
---
fs/userfaultfd.c | 24
include/linux/userfaultfd_k.h| 7 +++
include/uapi/linux/userfaultfd.h | 5 -
kernel/ex
Hi,
I see this wasn't Cc'd to LAKML, unlike the cover letter, and patch 3
(which isn't threaded against the cover letter).
Please use a consistent Cc list, with patches in-reply to the cover
letter.
On Tue, Jan 24, 2017 at 01:42:56PM +, Shameerali Kolothum Thodi wrote:
> This erratum describ
The HiSilicon erratum 161010801 describes the limitation of certain
HiSilicon platforms to support the SMMU mappings for MSI transactions.
On these platforms GICv3 ITS translator is presented with the deviceID
by extending the MSI payload data to 64 bits to include the deviceID.
Hence, the PCIe co
In the non-cooperative userfaultfd case, the process exit may race with
outstanding mcopy_atomic called by the uffd monitor. Returning -ENOSPC
instead of -EINVAL when mm is already gone will allow uffd monitor to
distinguish this case from other error conditions.
Signed-off-by: Mike Rapoport
---
The commit dc0ef0df7b6a (mm: make mmap_sem for write waits killable for mm
syscalls) replaced call to vm_munmap in munmap syscall with open coded
version to allow different waits on mmap_sem in munmap syscall and
vm_munmap. Now both functions use down_write_killable, so we can restore
the call to v
The memory mapping of a process may change between #PF event and the call
to mcopy_atomic that comes to resolve the page fault. In such case, there
will be no VMA covering the range passed to mcopy_atomic or the VMA will
not have userfaultfd context.
To allow uffd monitor to distinguish those case
On Tue, Jan 24, 2017 at 01:14:16PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 24, 2017 at 11:41 AM, Johannes Stezenbach wrote:
> > Meanwhile I found out the TI PMIC and power button drivers
> > has been published as part of the Asus ZenFone Zoom (ZX551ML)
> > Android kernel code drop (based on li
When a non-cooperative userfaultfd monitor copies pages in the background,
it may encounter regions that were already unmapped. Addition of
UFFD_EVENT_UNMAP allows the uffd monitor to track precisely changes in the
virtual memory layout.
Since there might be different uffd contexts for the affecte
This enables the acpi based workaround for HiSilicon erratum 161010801.
Signed-off-by: shameer
---
drivers/irqchip/irq-gic-v3-its.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 9fa12b7..d0f5099 1
> On 24/01/17 10:15, Bharat Kumar Gogada wrote:
> >> On 21/01/17 11:11, Bharat Kumar Gogada wrote:
> >>> - The legacy status register value for particular INTx becomes low
> >>> only after DEASSERT_INTx is received.
> >>> - Few End Points take time for sending DEASSERT_INTx, checking
> >>> legacy s
Hi Mark,
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Tuesday, January 24, 2017 1:52 PM
> To: Shameerali Kolothum Thodi
> Cc: marc.zyng...@arm.com; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Linuxarm; devicet...@vger.kernel.org; John
> Garry; G
On Tue, Jan 24, 2017 at 01:53:09PM +, Shameerali Kolothum Thodi wrote:
> This enables the acpi based workaround for HiSilicon erratum 161010801.
>
> Signed-off-by: shameer
> ---
> drivers/irqchip/irq-gic-v3-its.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/d
On Tue, Jan 24, 2017 at 3:03 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 20 January 2017 03:12 AM, Stephen Boyd wrote:
>> On 01/19, Vivek Gautam wrote:
>>>
>>> On 01/19/2017 06:10 AM, Stephen Boyd wrote:
>
Didn't we already move away from subnodes for lanes in an earlier
re
On 01/24, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > Suppose we have a process P in the root namespace and another namespace X.
> >
> > P does setns() and enters the X namespace.
> > P forks a child C.
> >
> > C forks a grandchild G.
> > C exits.
> >
> > The question is, where should
+ Robin,
On 24/01/17 13:47, Shameerali Kolothum Thodi wrote:
> The HiSilicon erratum 161010801 describes the limitation of certain
> HiSilicon platforms to support the SMMU mappings for MSI transactions.
>
> On these platforms GICv3 ITS translator is presented with the deviceID
> by extending the
On 01/23/2017 11:06 PM, Zhang Rui wrote:
On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote:
On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote:
Hi!
I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes
the issue.
Any idea what went wrong and how to fix
On 01/23/2017 11:34 PM, Pavel Machek wrote:
Hi!
I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes
the issue.
Any idea what went wrong and how to fix that?
Anyway as we are at -rc5 and this is warning fix that caused a
regression on different hardware... it should be rever
Hi!
> /sys files related to battery no longer appear. I beieve this has
> something to do with it:
>
> [2.374877] of_get_named_gpiod_flags: parsed 'reset-gpios' property
> of node '/ocp@6800/spi@48098000/tsc2005@0[0]' - status (0)
> [2.375946] input: TSC2005 to
Hi,
On Tuesday 24 January 2017 07:35 PM, Vivek Gautam wrote:
> On Tue, Jan 24, 2017 at 3:03 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Friday 20 January 2017 03:12 AM, Stephen Boyd wrote:
>>> On 01/19, Vivek Gautam wrote:
On 01/19/2017 06:10 AM, Stephen Boyd wrote:
>>
> D
On Tue, Jan 24, 2017 at 01:47:57PM +, Shameerali Kolothum Thodi wrote:
> The HiSilicon erratum 161010801 describes the limitation of certain
> HiSilicon platforms to support the SMMU mappings for MSI transactions.
>
> On these platforms GICv3 ITS translator is presented with the deviceID
> by
From: Colin Ian King
There are some error exit paths to the label 'out' that end up
kfree'ing an uninitialized im_node. Fix this by inititializing
im_node to NULL to avoid kfree'ing a garbage address.
Issue found by CoverityScan, CID#1398022 ("Uninitialized pointer read")
Signed-off-by: Colin
Hello,
Cc Steven
On (01/24/17 19:20), kernel test robot wrote:
> of/unittest: fix infinite loop in of_unittest_destroy_tracked_overlays()
>
> of_overlay_destroy() can return `-ENODEV' error code once it
> failed to find the requested overlay in `ov_idr'. However,
> of_unittest_des
pply
> Patch failed at 0001 pinctrl / gpio: Introduce .set_config() callback for
> GPIO chips
I tried today's linux-next 766074e7818 ("Add linux-next specific files
for 20170124") but only saw that GPIO conflict.
In any case I'm going to rebase my series on top of linux-gpio.git/devel
and submit it as v3.
On 01/23/2017 11:37 PM, Pavel Machek wrote:
On Tue 2017-01-24 15:06:39, Zhang Rui wrote:
On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote:
On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote:
Hi!
I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes
the
On 01/12/2017 11:12 AM, Mark Rutland wrote:
> On Thu, Jan 12, 2017 at 03:45:48PM +, Catalin Marinas wrote:
>> On Wed, Jan 11, 2017 at 06:40:52PM +, Mark Rutland wrote:
>
>>> Likewise, I beleive we may need to modify cpu_set_reserved_ttbr0().
>>
>> This may be fine if my assumptions about t
On Tue, Jan 24, 2017 at 3:52 PM, Johannes Stezenbach wrote:
> On Tue, Jan 24, 2017 at 01:14:16PM +0200, Andy Shevchenko wrote:
>> On Tue, Jan 24, 2017 at 11:41 AM, Johannes Stezenbach wrote:
>> > Meanwhile I found out the TI PMIC and power button drivers
>> > has been published as part of the Asu
On Mon, Jan 23, 2017 at 09:47:54AM -0700, Jason Gunthorpe wrote:
> On Mon, Jan 23, 2017 at 01:44:32AM +0200, Jarkko Sakkinen wrote:
> > From: James Bottomley
> >
> > Signed-off-by: James Bottomley
> >
>
> I really think we should not use the ugly read/write interface for any
> new things.
>
>
On Mon, 2017-01-23 at 11:23 +0100, Dmitry Vyukov wrote:
> On Mon, Jan 23, 2017 at 11:19 AM, Dmitry Vyukov wrote:
> > Hello,
> >
> > While running syzkaller fuzzer I started seeing use-after-frees in
> > tw_timer_handler. It happens with very low frequency, so far I've seen
> > 22 of them. But all
On Tue, Jan 24, 2017 at 02:00:30PM +, Shameerali Kolothum Thodi wrote:
> > -Original Message-
> > From: Mark Rutland [mailto:mark.rutl...@arm.com]
> > On Tue, Jan 24, 2017 at 01:42:56PM +, Shameerali Kolothum Thodi
> > wrote:
> > > +Optional
> > > +- hisilicon,erratum-161010801 :
On 01/23/2017 01:52 PM, Fabian Frederick wrote:
>
>
>> On 23 January 2017 at 19:43 Dave Kleikamp wrote:
>>
>>
>> On 01/23/2017 11:50 AM, Fabian Frederick wrote:
>>> See i_size_read() comments in include/linux/fs.h
>>
>> Is this fixing a real problem? Can the bd_inode size change while we're
>> m
On 01/24/2017 06:15 AM, Pavel Machek wrote:
Hi!
/sys files related to battery no longer appear. I beieve this has
something to do with it:
[2.374877] of_get_named_gpiod_flags: parsed 'reset-gpios' property
of node '/ocp@6800/spi@48098000/tsc2005@0[0]' - status (0)
[2.375946] input:
On Mon, Jan 23, 2017 at 02:28:23PM -0800, James Bottomley wrote:
> On Mon, 2017-01-23 at 09:47 -0700, Jason Gunthorpe wrote:
> > On Mon, Jan 23, 2017 at 01:44:32AM +0200, Jarkko Sakkinen wrote:
> > > From: James Bottomley
> > >
> > > Signed-off-by: James Bottomley
> > >
> >
> > I really think w
On Mon, Jan 23, 2017 at 05:06:08PM -0700, Jason Gunthorpe wrote:
> For a long time the cdev read/write interface had this strange
> idea that userspace had to read the result within 60 seconds otherwise
> it is discarded. Perhaps this made sense under some older locking regime,
> but in the modern
On 01/22/2017 01:58 PM, Jonathan Cameron wrote:
On 19/01/17 13:34, Fabrice Gasnier wrote:
Define extended attribute so that user may choose rising, falling or both
edges for external trigger sources.
Default to rising edge in case it isn't set.
Signed-off-by: Fabrice Gasnier
Creates a custom
On 24/01/17 14:11, Marc Zyngier wrote:
> + Robin,
>
> On 24/01/17 13:47, Shameerali Kolothum Thodi wrote:
>> The HiSilicon erratum 161010801 describes the limitation of certain
>> HiSilicon platforms to support the SMMU mappings for MSI transactions.
>>
>> On these platforms GICv3 ITS translator i
On Mon, Jan 23, 2017 at 05:19:18PM -0700, Jason Gunthorpe wrote:
> On Tue, Jan 24, 2017 at 02:02:52AM +0200, Jarkko Sakkinen wrote:
> > This commit adds a command filter for whitelisting a set of commands in
> > a TPM space. When a TPM space is created through /dev/tpms0, no
> > commands are allowe
On 01/22/2017 02:14 PM, Jonathan Cameron wrote:
On 19/01/17 13:34, Fabrice Gasnier wrote:
Add optional DMA support to STM32 ADC.
Use dma cyclic mode with at least two periods.
Signed-off-by: Fabrice Gasnier
What is the point going forward in supporting non dma buffered reads at all?
Is there
On 2017-01-24 15:40:06 [+0100], To Peter Zijlstra wrote:
> Since the change in commit fd7a4bed1835 ("sched, rt: Convert
> switched_{from, to}_rt() / prio_changed_rt() to balance callbacks") we
> don't reschedule a task under certain circumstances:
|switched_to_dl()
|{
|…
| if (rq->curr !=
On 01/24/2017 12:58 AM, Baoyou Xie wrote:
This patch adds watchdog controller driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/watchdog/Kconfig | 10 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/zx2967_wdt.c | 274 +++
* Pali Rohár [170124 02:02]:
> On Tuesday 24 January 2017 10:18:17 Pavel Machek wrote:
> > Hi!
> > On Mon 2017-01-23 14:44:54, Tony Lindgren wrote:
> > > * Pavel Machek [170123 14:26]:
> > > > [25392.239837] Unhandled fault: external abort on non-linefetch
> > > > (0x1028) at 0xfa0ab060
> > > >
From: Colin Ian King
The error return path When csraddr_str fails to free buf, causing a
memory leak. Fix this by returning via the free_buf label that
performs the necessary cleanup.
Signed-off-by: Colin Ian King
---
drivers/misc/eeprom/idt_89hpesx.c | 6 --
1 file changed, 4 insertions(+
On 01/24/2017 09:15 AM, David Binderman wrote:
> Hello there,
>
> fs/jffs2/readinode.c:189]: (style) Condition 'tn.fn.ofs>=offset' is always
> true
>
> Source code is
>
> if (tn->fn->ofs < offset)
> next = tn->rb.rb_right;
> else if (tn->fn->ofs >= offset)
>
On 24/01/17 14:41, Robin Murphy wrote:
> On 24/01/17 14:11, Marc Zyngier wrote:
>> + Robin,
>>
>> On 24/01/17 13:47, Shameerali Kolothum Thodi wrote:
>>> The HiSilicon erratum 161010801 describes the limitation of certain
>>> HiSilicon platforms to support the SMMU mappings for MSI transactions.
>>
User is not interested in USB cable events appearing on the
console. Use dev_dbg() instead of dev_info() for these events.
Signed-off-by: Roger Quadros
---
drivers/extcon/extcon-palmas.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/extcon/extcon-pa
On 01/22/2017 01:55 PM, Jonathan Cameron wrote:
On 19/01/17 13:34, Fabrice Gasnier wrote:
STM32 ADC has external timer trigger sources. Use stm32 timer triggers
API (e.g. is_stm32_timer_trigger()) with local ADC lookup table to
validate a trigger can be used.
This also provides correct trigger s
Felipe,
On 03/01/17 14:53, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>> Mathias & Felipe,
>>
>> On 17/11/16 17:01, Roger Quadros wrote:
>>> Hi,
>>>
>>> Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
>>>
>>> If the attached high-speed device is misbehaving, the
On Fri 20-01-17 14:41:37, Vlastimil Babka wrote:
> On 01/12/2017 06:37 PM, Michal Hocko wrote:
> > On Thu 12-01-17 09:26:09, Kees Cook wrote:
> >> On Thu, Jan 12, 2017 at 7:37 AM, Michal Hocko wrote:
> > [...]
> >>> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
> >>> index 4f745
On Wed, 2017-01-18 at 07:14 -0500, Jeff Layton wrote:
> On Thu, 2017-01-12 at 12:37 +0100, Ilya Dryomov wrote:
> > On Thu, Jan 12, 2017 at 12:27 PM, Jeff Layton wrote:
> > > On Thu, 2017-01-12 at 07:59 +, Al Viro wrote:
> > > > On Tue, Jan 10, 2017 at 07:57:31AM -0500, Jeff Layton wrote:
> > >
On Wed, Jan 18, 2017 at 07:19:48PM -0500, Doug Ledford wrote:
> On Wed, 2017-01-18 at 23:39 +0200, Michael S. Tsirkin wrote:
> > No hardware seems to actually call link_reset, and
> > no driver implements it as more than a nop stub.
> >
> > This drops the mentions of the callback from everywhere.
Am Dienstag, 24. Januar 2017, 15:16:40 CET schrieb Alexander Kochetkov:
> The patch move ce field out of struct bc_timer into struct
> rk_clock_event_device and rename struct bc_timer to struct rk_timer.
>
> The main idea for the commit is to exctact low level timer
> routines from current impleme
Hi Catalin,
On 01/11/2017 01:06 PM, Catalin Marinas wrote:
> Some minor comments below, nothing fundamental (as long as you say the
> new sequence doesn't have the speculative TLB load problem I mentioned
> on a previous version).
This workaround is documented as providing functional correctness
On 01/18/2017 07:07 AM, Jun Gao wrote:
From: Jun Gao
This add i2c DT binding to i2c-mt6577.txt for MT2701.
Signed-off-by: Jun Gao
---
.../devicetree/bindings/i2c/i2c-mt6577.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetre
On Tue, Jan 24, 2017 at 09:00:07PM +0800, Cao jin wrote:
> It take me for a long while to find what I missed. I missed much
> details in pci-error-recovery.txt, and I was not conscious of a
> multi-function device which could have different functions(driver) on it.
>
> Thank you both.
Pls note t
On Fri, Jan 20, 2017 at 11:04:42PM +, Colin Ian King wrote:
> On 20/01/17 20:47, Darrick J. Wong wrote:
> > On Fri, Jan 20, 2017 at 01:26:12PM -0600, Eric Sandeen wrote:
> >> On 1/20/17 8:26 AM, Colin King wrote:
> >>> From: Colin Ian King
> >>>
> >>> If pag cannot be allocated, the current er
The allocation fast path contains two similar checks for zoneref->zone being
NULL, where zoneref points either to the first zone in the zonelist, or to the
preferred zone. These can be NULL either due to empty zonelist, or no zone
being compatible with given nodemask or task's cpuset.
These checks
Since commit 682a3385e773 ("mm, page_alloc: inline the fast path of the
zonelist iterator") we replace a NULL nodemask with cpuset_current_mems_allowed
in the fast path, so that get_page_from_freelist() filters nodes allowed by the
cpuset via for_next_zone_zonelist_nodemask(). In that case it's poi
Since the change in commit fd7a4bed1835 ("sched, rt: Convert
switched_{from, to}_rt() / prio_changed_rt() to balance callbacks") we
don't reschedule a task under certain circumstances:
Lets say taskA, SCHED_OTHER, is running on CPU0 (and it may run only on
CPU0) and holds a PI lock. This task is r
Will include it in patch-set with documentation fix. Thanks Oleg!
Reviewed-by: Pavel Tikhomirov
On 01/23/2017 02:57 PM, Oleg Nesterov wrote:
Add the new helper to walk the process tree, the next patch adds a user.
Note that it visits the group leaders only, proc_visitor can do
for_each_thread
On Tue, 2017-01-24 at 15:52 +0100, Marek Vasut wrote:
> On 01/24/2017 09:15 AM, David Binderman wrote:
> > Hello there,
> >
> > fs/jffs2/readinode.c:189]: (style) Condition 'tn.fn.ofs>=offset' is always
> > true
> >
> > Source code is
> >
> > if (tn->fn->ofs < offset)
> > ne
On 01/23/2017 06:08 PM, Dan O'Donovan wrote:
(Re-submitting this patch set originally created by Leonard Crestez,
possibly abandoned by Leonard due to a change in employment)
When using devicetree, stuff like i2c_client.name or spi_device.modalias
is initialized to the first DT compatible id wit
On Tue, Jan 24, 2017 at 3:28 PM, Eric Dumazet wrote:
> On Mon, 2017-01-23 at 11:23 +0100, Dmitry Vyukov wrote:
>> On Mon, Jan 23, 2017 at 11:19 AM, Dmitry Vyukov wrote:
>> > Hello,
>> >
>> > While running syzkaller fuzzer I started seeing use-after-frees in
>> > tw_timer_handler. It happens with
> -Original Message-
> From: Mark Rutland [mailto:mark.rutl...@arm.com]
> Sent: Tuesday, January 24, 2017 2:29 PM
> To: Shameerali Kolothum Thodi
> Cc: marc.zyng...@arm.com; will.dea...@arm.com; linux-
> ker...@vger.kernel.org; Linuxarm; devicet...@vger.kernel.org; John
> Garry; Guohanjun
Hi Dan,
On 24/01/17 13:25, Daniel Kurtz wrote:
> Back before commit 1dccb598df54 ("arm64: simplify dma_get_ops"), for arm64,
> devices that do not manually set a dma_ops are automatically configured to
> use swiotlb_dma_ops, since this was hard-coded as the global "dma_ops" in
> arm64_dma_init().
On 01/24/2017 04:11 PM, Joakim Tjernlund wrote:
> On Tue, 2017-01-24 at 15:52 +0100, Marek Vasut wrote:
>> On 01/24/2017 09:15 AM, David Binderman wrote:
>>> Hello there,
>>>
>>> fs/jffs2/readinode.c:189]: (style) Condition 'tn.fn.ofs>=offset' is always
>>> true
>>>
>>> Source code is
>>>
>>>
> 24 янв. 2017 г., в 18:02, Heiko Stübner написал(а):
>
> Please don't add Reviewed-by tags without explicit mention of them by
> reviewers. (Also it's spelled wrong).
>
> I haven't looked that deeply into the driver itself and the changes made to
> feel comfortable with a "Reviewed-by".
Tha
On 01/23/2017 09:45 PM, Stephen Rothwell wrote:
> Hi Shuah,
>
> Today's linux-next merge of the kselftest tree got a conflict in:
>
> tools/testing/selftests/bpf/Makefile
>
> between commit:
>
> 4d3381f5a322 ("bpf: Add tests for the lpm trie map")
>
> from the net-next tree and commit:
>
On Tue, Jan 24, 2017 at 5:11 PM, Jarkko Nikula wrote:
> After addressing comments from Andy
>
> Reviewed-by: Jarkko Nikula
> Tested-by: Jarkko Nikula
> -
> Intel Finland Oy
> Registered Address: PL 281, 00181 Helsinki Business I
301 - 400 of 836 matches
Mail list logo
