On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote:
> On Tue, Dec 05, 2017 at 11:56:44AM +0530, kaiwan.billimo...@gmail.com wrote:
> > Currently, leaking_addresses.pl only supports scanning 64 bit
> > architectures. This is due to how the regular expressions are formed. We
> > can do better
From: Markus Elfring
Date: Wed, 6 Dec 2017 12:42:20 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/usb/misc/emi62.c | 5 ++---
1 file changed, 2 insertions(+), 3
On the Amlogic Gx SoCs (GXBB, GXL & GXM), the VPU power domain is initialized
by the vendor U-Boot code, but running mainline U-boot has been possible
on these SoCs. But lacking such init made the system lock at kernel boot.
A PM Power Domain driver has been pushed at [1] to solve the main issue.
On reference boards and derivatives, the HDMI Logic is powered by an external
5V regulator.
This regulator was set by the Vendor U-Boot, add optional support for it.
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.txt | 4 +
On reference boards and derivatives, the HDMI Logic is powered by an external
5V regulator.
This regulator was set by the Vendor U-Boot, add optional support for it.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/meson/meson_dw_hdmi.c | 13 +
1 file changed, 13 insertions(+)
diff
The VPU init misses these configurations values.
Signed-off-by: Neil Armstrong
---
drivers/gpu/drm/meson/meson_drv.c | 9 +
drivers/gpu/drm/meson/meson_registers.h | 4
2 files changed, 13 insertions(+)
diff --git a/drivers/gpu/drm/meson/meson_drv.c
b/drivers/gpu/drm/meson/m
The Video Processing Unit power domain was setup by the Vendor U-Boot,
add support for an optional Power Domain phandle to setup it from the kernel.
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/display/amlogic,meson-vpu.txt | 4
1 file changed,
On 12/05/17 11:33, Alan Tull wrote:
> On Thu, Nov 30, 2017 at 6:46 AM, Frank Rowand wrote:
>> On 11/29/17 11:11, Alan Tull wrote:
>>> On Wed, Nov 29, 2017 at 7:31 AM, Rob Herring wrote:
On Wed, Nov 29, 2017 at 3:20 AM, Frank Rowand
wrote:
> On 11/27/17 15:58, Alan Tull wrote:
On 12/05/17 12:07, Alan Tull wrote:
> On Mon, Dec 4, 2017 at 7:14 PM, Frank Rowand wrote:
>> Hi Alan,
>>
>> In the RFC thread "of: Add whitelist", I did not understand the use case and
>> asked you some questions (30 Nov 2017 07:46:36 -0500), that you seem to have
>> overlooked (or my mail server
From: Wanpeng Li
*** Guest State ***
CR0: actual=0x0030, shadow=0x6010,
gh_mask=fff7
CR4: actual=0x2050, shadow=0x,
gh_mask=e871
CR3 = 0xfffbc000
RSP = 0x RIP = 0x
RFLAGS=0
On 06/12/2017 13:02, Chris Wilson wrote:
> Quoting Neil Armstrong (2017-12-06 11:54:28)
>> The VPU init misses these configurations values.
>>
>> Signed-off-by: Neil Armstrong
>> ---
>> drivers/gpu/drm/meson/meson_drv.c | 9 +
>> drivers/gpu/drm/meson/meson_registers.h | 4
>>
From: Markus Elfring
Date: Wed, 6 Dec 2017 13:03:21 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/usb/misc/emi26.c | 5 ++---
1 file changed, 2 insertions(+), 3
Description:
If there is a driver in system which starts creating async schedules
just after resume (Same as our case, in which we faced issue).
Then async_synchronize_full API in PM cores starts waiting for completion
of async schedules created by that driver (Even though those are in a domain).
Hi Bjorn,
On 11/16/2017 12:38 PM, Bjorn Andersson wrote:
Attempt to acquire the APCS IPC through the mailbox framework and fall
back to the old syscon based approach, to allow us to move away from
using the syscon.
Signed-off-by: Bjorn Andersson
---
drivers/rpmsg/qcom_smd.c | 62 +++
On Wed, 06 Dec 2017 03:17:07 +
NAMIT GUPTA wrote:
> Hi Steve,
>
>
>
> Please check the patch.
Sure. BTW, when you send a patch, please add '[PATCH]' in the subject.
I currently have over 17 thousand emails in my INBOX, and I filter
it on "[PATCH" to find patches that I missed. Which mean
On Wed, 6 Dec 2017, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 6 Dec 2017 13:03:21 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
> driver
From: Srinivas Kandagatla
This patch fixes missing mnd_width for codec_digital clk, this is now set to
8 inline with datasheet.
Fixes: 3966fab8b6ab ("clk: qcom: Add MSM8916 Global Clock Controller support")
Signed-off-by: Srinivas Kandagatla
---
drivers/clk/qcom/gcc-msm8916.c | 1 +
1 file cha
From: Srinivas Kandagatla
Hi Stephen,
Found few issues while trying to set 12.288MHz on codec digital clk.
One is to do with missing mnd_width and other is missing clk entry.
thanks,
srini
Srinivas Kandagatla (2):
clk: qcom: msm8916: fix mnd_width for codec_digcodec
clk: qcom: msm8916: ad
From: Srinivas Kandagatla
This patch adds 12.288 MHz suport to codec digital clk, this clock.
Some external PA requires a 12.288 MHz to work.
Signed-off-by: Srinivas Kandagatla
---
drivers/clk/qcom/gcc-msm8916.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/qcom/gcc-msm8916.c
On Tue, Dec 05, 2017 at 12:02:00PM -0200, rodrigosiqueira wrote:
> The first parameter of prepare_lock_switch (kernel/sched/sched.h) is not
> used anymore. Commit c55f5158f removed the code that use the first
> parameter and function prepare_lock_switch is only used in
> prepare_task_switch (kernel
On Mon 04-12-17 14:36:20, Linus Torvalds wrote:
> On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
> >
> > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> > systems I have tested, so it is probably safe to assume it to be
> > broken everywhere.
>
> Oh, it's definite
On 12/05/2017 06:49 PM, David Miller wrote:
From: Arvind Yadav
Date: Mon, 4 Dec 2017 23:18:20 +0530
@@ -120,9 +120,10 @@ static int sni_82596_probe(struct platform_device
*dev)
netdevice->dev_addr[5] = readb(eth_addr + 0x06);
iounmap(eth_addr);
-if (!netdevice->irq) {
On Tue 05-12-17 13:00:54, Kirill Tkhai wrote:
[...]
> This meets the problem in case of many containers
> are used on the hardware node. Since aio_max_nr is
> a global limit, any container may occupy the whole
> available aio requests, and to deprive others the
> possibility to use aio at all. The
On Wed, 6 Dec 2017, Michal Hocko wrote:
> merging tip/x86/urgent on top of your tree fixed this problem for me,
> but I am seeing something else
> [ 131.711412] ACPI: Preparing to enter system sleep state S3
> [ 131.755328] ACPI: EC: event blocked
> [ 131.755328] ACPI: EC: EC stopped
> [ 131.75
On Tue, Dec 05, 2017 at 09:54:11AM -0600, Andrew F. Davis wrote:
> From: Michael Stecklein
>
> Add the bindings for the TAS6424 digital amplifier.
Please use subject lines matching the style for the subsystem. This
makes it easier for people to identify relevant patches.
signature.asc
Descrip
On 12/04/2017 05:21 PM, Christoph Hellwig wrote:
> On Wed, Nov 29, 2017 at 08:18:09PM +0100, Christian Borntraeger wrote:
>> Works fine under KVM with virtio-blk, but still hangs during boot in an LPAR.
>> FWIW, the system not only has scsi disks via fcp but also DASDs as a boot
>> disk.
>> Seems
Op 06-12-17 om 13:15 schreef Michal Hocko:
> On Mon 04-12-17 14:36:20, Linus Torvalds wrote:
>> On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
>>> So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
>>> systems I have tested, so it is probably safe to assume it to be
>>>
Dear Linux folks,
With Linux 4.15-rc2 built by the Ubuntu Kernel Team, the error messages
below are shown by the Linux kernel. These are new.
```
Dez 06 13:22:24 Ixpees kernel: microcode: microcode updated early to
revision 0x62, date = 2017-04-27
Dez 06 13:22:24 Ixpees kernel: Linux version
On Fri, Dec 01, 2017 at 06:19:50AM -0800, Tejun Heo wrote:
> What do you think? Would this be something worth pursuing?
My worry with the whole thing is that it makes PMU scheduling _far_ more
expensive.
Currently HW PMU scheduling is 'bounded' by the fact that we have
bounded hardware resource
We're about to rework the way ASIDs are allocated, switch_mm is
implemented and low-level kernel entry/exit is handled, so keep the
ARM64_SW_TTBR0_PAN code out of the way whilst we do the heavy lifting.
It will be re-enabled in a subsequent patch.
Reviewed-by: Mark Rutland
Signed-off-by: Will De
In preparation for mapping kernelspace and userspace with different
ASIDs, move the ASID to TTBR1 and update switch_mm to context-switch
TTBR0 via an invalid mapping (the zero page).
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/mmu_context.h | 7 +++
arc
With the ASID now installed in TTBR1, we can re-enable ARM64_SW_TTBR0_PAN
by ensuring that we switch to a reserved ASID of zero when disabling
user access and restore the active user ASID on the uaccess enable path.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig
On 6 December 2017 at 12:38, Patrick Bellasi wrote:
> Hi Vincent,
>
> On 06-Dec 10:39, Vincent Guittot wrote:
>> Hi Patrick,
>>
>> On 30 November 2017 at 12:47, Patrick Bellasi
>> wrote:
>
> [...]
>
>> > static void dequeue_task_rt(struct rq *rq, struct task_struct *p, int
>> > flags)
>> > @@
In preparation for unmapping the kernel whilst running in userspace,
make the kernel mappings non-global so we can avoid expensive TLB
invalidation on kernel exit to userspace.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/kernel-pgtable.h | 12 ++--
ar
On 06.12.2017 15:23, Michal Hocko wrote:
> On Tue 05-12-17 13:00:54, Kirill Tkhai wrote:
> [...]
>> This meets the problem in case of many containers
>> are used on the hardware node. Since aio_max_nr is
>> a global limit, any container may occupy the whole
>> available aio requests, and to deprive
The literal pool entry for identifying the vectors base is the only piece
of information in the trampoline page that identifies the true location
of the kernel.
This patch moves it into its own page, which is only mapped by the full
kernel page table, which protects against any accidental leakage
There are now a handful of open-coded masks to extract the ASID from a
TTBR value, so introduce a TTBR_ASID_MASK and use that instead.
Suggested-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/asm-uaccess.h | 3 ++-
arch/arm64/include/asm/mmu.h | 1 +
arch/arm64/i
When running with the kernel unmapped whilst at EL0, the virtually-addressed
SPE buffer is also unmapped, which can lead to buffer faults if userspace
profiling is enabled and potentially also when writing back kernel samples
unless an expensive drain operation is performed on exception return.
Fo
Allow explicit disabling of the entry trampoline on the kernel command
line (kpti=off) by adding a fake CPU feature (ARM64_UNMAP_KERNEL_AT_EL0)
that can be used to toggle the alternative sequences in our entry code and
avoid use of the trampoline altogether if desired. This also allows us to
make u
Add a Kconfig entry to control use of the entry trampoline, which allows
us to unmap the kernel whilst running in userspace and improve the
robustness of KASLR.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig | 13 +
1 file changed, 13 insertions(+)
diff
Since an mm has both a kernel and a user ASID, we need to ensure that
broadcast TLB maintenance targets both address spaces so that things
like CoW continue to work with the uaccess primitives in the kernel.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/tlbflus
To allow unmapping of the kernel whilst running at EL0, we need to
point the exception vectors at an entry trampoline that can map/unmap
the kernel on entry/exit respectively.
This patch adds the trampoline page, although it is not yet plugged
into the vector table and is therefore unused.
Review
Hook up the entry trampoline to our exception vectors so that all
exceptions from and returns to EL0 go via the trampoline, which swizzles
the vector base register accordingly. Transitioning to and from the
kernel clobbers x30, so we use tpidrro_el0 and far_el1 as scratch
registers for native tasks
On Tue, Dec 05, 2017 at 12:14:46PM -0600, Andrew F. Davis wrote:
> Platform ASoC drivers are a lot like ASoC CODEC drivers in that they
> both are independent pieces of a sound device, or "machine". Platform
> drivers should be free of CODEC specifics and visa-versa. Both are then
> used by the the
When unmapping the kernel at EL0, we use tpidrro_el0 as a scratch register
during exception entry from native tasks and subsequently zero it in
the kernel_ventry macro. We can therefore avoid zeroing tpidrro_el0
in the context-switch path for native tasks using the entry trampoline.
Reviewed-by: M
The exception entry trampoline needs to be mapped at the same virtual
address in both the trampoline page table (which maps nothing else)
and also the kernel page table, so that we can swizzle TTBR1_EL1 on
exceptions from and return to EL0.
This patch maps the trampoline at a fixed virtual address
We will need to treat exceptions from EL0 differently in kernel_ventry,
so rework the macro to take the exception level as an argument and
construct the branch target using that.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/kernel/entry.S | 46 +++-
We rely on an atomic swizzling of TTBR1 when transitioning from the entry
trampoline to the kernel proper on an exception. We can't rely on this
atomicity in the face of Falkor erratum #E1003, so on affected cores we
can issue a TLB invalidation to invalidate the walk cache prior to
jumping into th
Hi everybody,
This is version three of the patches formerly known as KAISER (♔).
v1:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
v2:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/544817.html
Changes since v2 include:
* Rename com
The post_ttbr0_update_workaround hook applies to any change to TTBRx_EL1.
Since we're using TTBR1 for the ASID, rename the hook to make it clearer
as to what it's doing.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/assembler.h | 5 ++---
arch/arm64/kernel/entr
In order for code such as TLB invalidation to operate efficiently when
the decision to map the kernel at EL0 is determined at runtime, this
patch introduces a helper function, arm64_kernel_unmapped_at_el0, to
determine whether or not the kernel is mapped whilst running in userspace.
Currently, thi
The pre_ttbr0_update_workaround hook is called prior to context-switching
TTBR0 because Falkor erratum E1003 can cause TLB allocation with the wrong
ASID if both the ASID and the base address of the TTBR are updated at
the same time.
With the ASID sitting safely in TTBR1, we no longer update thing
In preparation for separate kernel/user ASIDs, allocate them in pairs
for each mm_struct. The bottom bit distinguishes the two: if it is set,
then the ASID will map only userspace.
Reviewed-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/include/asm/mmu.h | 1 +
arch/arm64/mm/contex
Gautham R Shenoy writes:
> Hi Michael,
>
> On Wed, Dec 06, 2017 at 09:54:27PM +1100, Michael Ellerman wrote:
>> Shilpasri G Bhat writes:
>>
>> > From: "Gautham R. Shenoy"
>> >
>> > Pstates are 8bit values but on POWER8 they are negative and on POWER9
>> > they are positive. This patch adds hel
On Wed 06-12-17 15:36:56, Kirill Tkhai wrote:
> On 06.12.2017 15:23, Michal Hocko wrote:
> > On Tue 05-12-17 13:00:54, Kirill Tkhai wrote:
> > [...]
> >> This meets the problem in case of many containers
> >> are used on the hardware node. Since aio_max_nr is
> >> a global limit, any container may
On Tue, Dec 05, 2017 at 03:20:19PM -0600, Andrew F. Davis wrote:
> On 12/01/2017 07:26 AM, Mark Brown wrote:
> > The advantage being...? Not all architectures use DT or ACPI so it's
> > not clear that this is a step forwards in itself.
> Simplifies the code in several places, and you don't need
On Wed, Dec 06, 2017 at 02:51:41PM +0530, George Cherian wrote:
> Hi Michael,
>
>
> On 12/06/2017 12:59 AM, Michael S. Tsirkin wrote:
> > Users of ptr_ring expect that it's safe to give the
> > data structure a pointer and have it be available
> > to consumers, but that actually requires an smb_w
On Wed, 6 Dec 2017, Maarten Lankhorst wrote:
> Op 06-12-17 om 13:15 schreef Michal Hocko:
> >
> > "No irq handler" part looks a bit scary (maybe related to lost affinity
> > messages?) but the following messages look quite as well. Is this
> > something known? The system seems to be up and running
On Tue, Dec 05, 2017 at 03:23:49PM -0600, Andrew F. Davis wrote:
> On 12/04/2017 10:47 AM, Andrew F. Davis wrote:
> > Kbuild bot seems mad a this one, looks like I need to include
> > linux/gpio/consumer.h, will fix for v3.
> Looks like you already have this in your -next branch, how do you want
On Wed, Dec 06, 2017 at 11:11:27AM +0200, Marcus Wolf wrote:
>
> Since the rule for kernel development seems to be, not to care about future,
> most probably you patch is fine, anyway.
>
Yeah. Deleting code if there is no user is required to move this code
out of staging...
I've worked in stag
On Fri, Oct 27, 2017 at 11:18 PM, Cong Wang wrote:
> On Thu, Oct 26, 2017 at 11:00 PM, Dmitry Vyukov wrote:
>> On Thu, Oct 26, 2017 at 7:58 PM, Tejun Heo wrote:
>>> Hello,
>>>
>>> On Thu, Oct 26, 2017 at 09:35:44AM -0700, syzbot wrote:
BUG: KASAN: use-after-free in __read_once_size
inc
On Wed, Dec 06, 2017 at 02:43:02PM +0300, Jan Dakinevich wrote:
> This patch introduces globally visible intel_pmu_lbr_fill() routine,
> which gathers information which LBR MSRs are support for specific CPU
> family/model.
>
> It is supposed that the routine would be used in KVM code, using guest
On Wed, Dec 06, 2017 at 02:43:03PM +0300, Jan Dakinevich wrote:
> Windows Server 2016 Essentials (for yet unknown reason) attempts to
> access MSR_LBR_TOS and other LBR-related registers at startup. These
> are not currently hadled by KVM so the guest gets #GP and crashes.
Shiny feature :-)
On Wed, 2017-12-06 at 17:21 +0530, kaiwan.billimo...@gmail.com wrote:
> On Wed, 2017-12-06 at 15:04 +1100, Tobin C. Harding wrote:
> > On Tue, Dec 05, 2017 at 11:56:44AM +0530, kaiwan.billimo...@gmail.com wrote:
> > > Currently, leaking_addresses.pl only supports scanning 64 bit
> > > architectures
A single socket, single core, single thread system has __max_smt_threads
set to 0 since smp_callin() is not called.
__max_smt_threads must be a minimum of 1.
Fixes: b1cbacc8663a ("x86/smpboot: Do not use smp_num_siblings in
__max_logical_packages calculation)
Signed-off-by: Prarit Bhargava
Cc:
On Wed, Dec 06, 2017 at 03:03:18PM +0900, Katsuhiro Suzuki wrote:
> > I'd expect this code to be structured more like a library - have a
> > driver that handles the specific IPs then have it call into a shared
> > block of code that does the generic bits. Though in this case the
> > device specif
sun6i_spi_probe() uses sun6i_spi_runtime_resume() to prepare/enable clocks,
so sun6i_spi_remove() should use sun6i_spi_runtime_suspend() to
disable/unprepare them.
Found by Linux Driver Verification project (linuxtesting.org).
Fixes: 3558fe900e8af spi: sunxi: Add Allwinner A31 SPI controller driv
On 6 December 2017 at 12:35, Will Deacon wrote:
> The literal pool entry for identifying the vectors base is the only piece
> of information in the trampoline page that identifies the true location
> of the kernel.
>
> This patch moves it into its own page, which is only mapped by the full
> kerne
On Tue, Dec 05, 2017 at 05:03:33PM +0800, Mengting Zhang wrote:
> While monitoring a multithread process with pid option, perf sometimes
> may return sys_perf_event_open failure with 3(No such process) if any
> of the process's threads die before we open the event. However, we want
> perf continue
On Mon, 2017-12-04 at 05:27:25 UTC, David Gibson wrote:
> This reverts commit a3b2cb30f252b21a6f962e0dd107c8b897ca65e4.
>
> The earlier patch tried to fix problems with panic on powerpc in
> certain circumstances, where some output from the generic panic code
> was being dropped.
>
> Unfortunatel
On Thu, 2017-11-30 at 08:33:22 UTC, Ravi Bangoria wrote:
> When user tries to group imc (In-Memory Collections) event with
> normal event, (sometime) kernel crashes with following log:
>
> Faulting instruction address: 0x
> [link register ] c010ce88 power_check_constraint
Just two patches fixing minor coding style issues. The first one
contains fixes for problems reported by checkpatch. The second adds
a common prefix to all symbols in at24.c.
v1 -> v2:
- don't breal the user space: use module_param_named() for module
parameters
Bartosz Golaszewski (2):
eeprom
There are a couple symbols defined in the driver source file which are
missing the at24_ prefix. This patch fixes that.
For module params: use module_param_named() in order not to break the
userspace.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 34 ++-
Fix issues reported by checkpatch for at24.c.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index 625b00166117..2426f2c111c7 10
On 12/05/2017 03:55 PM, Benjamin Gaignard wrote:
> Add SPDX identifier in stm32's files in IIO directory
>
> Signed-off-by: Benjamin Gaignard
> ---
> drivers/iio/adc/stm32-adc-core.c| 14 +-
> drivers/iio/adc/stm32-adc-core.h| 14 +-
> drivers/iio/
It was <2017-12-06 śro 12:37>, when Krzysztof Kozlowski wrote:
> On Wed, Dec 6, 2017 at 12:32 PM, Łukasz Stelmach
> wrote:
>> It was <2017-12-05 wto 19:06>, when Krzysztof Kozlowski wrote:
>>> On Tue, Dec 5, 2017 at 6:53 PM, Krzysztof Kozlowski wrote:
On Tue, Dec 05, 2017 at 05:43:10PM +010
Op 06-12-17 om 13:46 schreef Thomas Gleixner:
> On Wed, 6 Dec 2017, Maarten Lankhorst wrote:
>> Op 06-12-17 om 13:15 schreef Michal Hocko:
>>> "No irq handler" part looks a bit scary (maybe related to lost affinity
>>> messages?) but the following messages look quite as well. Is this
>>> something
On 06.12.2017 15:43, Michal Hocko wrote:
> On Wed 06-12-17 15:36:56, Kirill Tkhai wrote:
>> On 06.12.2017 15:23, Michal Hocko wrote:
>>> On Tue 05-12-17 13:00:54, Kirill Tkhai wrote:
>>> [...]
This meets the problem in case of many containers
are used on the hardware node. Since aio_max_n
From: Markus Elfring
Date: Wed, 6 Dec 2017 13:23:35 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/usb/host/imx21-hcd.c | 4 +---
1 file changed, 1 insertion(+),
On Wed, Dec 06, 2017 at 01:12:32PM +0100, Julia Lawall wrote:
>
>
> On Wed, 6 Dec 2017, SF Markus Elfring wrote:
>
> > From: Markus Elfring
> > Date: Wed, 6 Dec 2017 13:03:21 +0100
> >
> > Omit an extra message for a memory allocation failure in this function.
> >
> > This issue was detected by
Hi,
On Wed, 06 Dec 2017, Andreas Platschek wrote:
> Previously enabled clks are only disabled if clk_prepare_enable() fails.
> However, there are other error paths were the previously enabled
> clocks are not disabled.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signe
On 29.11.2017 23:05, Alexandre Belloni wrote:
Hi,
On 15/11/2017 at 14:56:46 +0200, Eugen Hristev wrote:
Added DMA property for ADC device
Signed-off-by: Eugen Hristev
---
arch/arm/boot/dts/sama5d2.dtsi | 2 ++
1 file changed, 2 insertions(+)
This didn't apply cleanly, please check
htt
On 12/5/2017 5:18 PM, Rafael J. Wysocki wrote:
> On Tue, Dec 5, 2017 at 10:01 PM, Sinan Kaya wrote:
>> Some GED interrupts could be pending by the time we are doing a reboot.
>>
>> Even though GED driver uses devm_request_irq() to register the interrupt
>> handler, the handler is not being freed o
>> @@ -42,10 +42,9 @@ static int emi26_writememory (struct usb_device *dev, int
>> address,
>> int result;
>> unsigned char *buffer = kmemdup(data, length, GFP_KERNEL);
>>
>> -if (!buffer) {
>> -dev_err(&dev->dev, "kmalloc(%d) failed.\n", length);
>
> I guess the length
Hi Ard,
On Wed, Dec 06, 2017 at 12:59:40PM +, Ard Biesheuvel wrote:
> On 6 December 2017 at 12:35, Will Deacon wrote:
> > The literal pool entry for identifying the vectors base is the only piece
> > of information in the trampoline page that identifies the true location
> > of the kernel.
>
in error path of jz4740_dma_probe(), call clk_disable_unprepare() to clean
up.
Found by Linux Driver Verification project (linuxtesting.org).
Fixes: 25ce6c35fea0 MIPS: jz4740: Remove custom DMA API
Signed-off-by: Tobias Jordan
---
drivers/dma/dma-jz4740.c | 4 +++-
1 file changed, 3 insertions(
Hi Nipun,
Can you polish a bit this commit message? It doesn't seem to explain why
this is needed.
On 12/06/2017 06:18 PM, Nipun Gupta wrote:
> When DPRC probing is deferred (such as where IOMMU is not probed
> before the fsl-mc bus), all the devices in the DPRC containers gets
> initialized one
On Wed, Dec 06, 2017 at 08:44:53AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Dec 05, 2017 at 07:15:34PM +0100, Heiko Carstens wrote:
> > On Tue, Dec 05, 2017 at 06:08:47PM +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Dec 05, 2017 at 05:02:32PM +, Ben Hutchings wrote:
> > > > On Tue, 2017-11-
From: Sunil Goutham
This adds timestamping support for both receive and transmit
paths. On the receive side no filters are supported i.e either
all pkts will get a timestamp appended infront of the packet or none.
On the transmit side HW doesn't support timestamp insertion but
only generates a se
This series adds support for IEEE 1588 Precision Time Protocol
to Cavium ethernet driver.
The first patch adds support for the Precision Time Protocol Clocks and
Timestamping coprocessor (PTP) found on Cavium processors.
It registers a new PTP clock in the PTP core and provides functions
to use th
From: Radoslaw Biernacki
This patch adds support for the Precision Time Protocol
Clocks and Timestamping hardware found on Cavium ThunderX
processors.
Signed-off-by: Radoslaw Biernacki
Signed-off-by: Aleksey Makarov
---
drivers/net/ethernet/cavium/Kconfig | 13 +
drivers/net/ethe
On Wed, Dec 06, 2017 at 08:44:53AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Dec 05, 2017 at 07:15:34PM +0100, Heiko Carstens wrote:
> > On Tue, Dec 05, 2017 at 06:08:47PM +0100, Greg Kroah-Hartman wrote:
> > > On Tue, Dec 05, 2017 at 05:02:32PM +, Ben Hutchings wrote:
> > > > On Tue, 2017-11-
On 12/5/17 11:58 PM, Vinod Koul wrote:
On Tue, Dec 05, 2017 at 08:48:03AM -0600, Pierre-Louis Bossart wrote:
On 12/5/17 7:43 AM, Pierre-Louis Bossart wrote:
On 12/5/17 12:31 AM, Vinod Koul wrote:
On Sun, Dec 03, 2017 at 09:01:41PM -0600, Pierre-Louis Bossart wrote:
+static inline int do_tra
On Wed, Dec 6, 2017 at 10:33 AM, Chris Chiu wrote:
> On Wed, Dec 6, 2017 at 5:56 AM, Rafael J. Wysocki wrote:
>> On Tuesday, December 5, 2017 5:19:03 PM CET Chris Chiu wrote:
>>> On Tue, Dec 5, 2017 at 11:01 PM, Rafael J. Wysocki
>>> wrote:
>>> > On Tue, Dec 5, 2017 at 11:32 AM, Chris Chiu wro
On Wed, Dec 06, 2017 at 12:35:37PM +, Will Deacon wrote:
> When running with the kernel unmapped whilst at EL0, the virtually-addressed
> SPE buffer is also unmapped, which can lead to buffer faults if userspace
> profiling is enabled and potentially also when writing back kernel samples
> unle
On Wed, Dec 06, 2017 at 09:57:41AM +, George Cherian wrote:
> While running a multiple VM testscase with each VM running iperf
> traffic between others the following kernel NULL pointer exception
> was seen.
>
> Race appears when the tun driver instance of one VM calls skb_array_produce
> (fro
On Wed, Dec 06, 2017 at 12:13:16AM +0800, John Garry wrote:
> For some architectures (like arm64), there are architecture-
> defined recommended events. Vendors may not be obliged to
> follow the recommendation and may implement their own pmu
> event for a specific event code.
>
> This patch adds
On Wed, Dec 6, 2017 at 2:24 PM, Sinan Kaya wrote:
> On 12/5/2017 5:18 PM, Rafael J. Wysocki wrote:
>> On Tue, Dec 5, 2017 at 10:01 PM, Sinan Kaya wrote:
>>> Some GED interrupts could be pending by the time we are doing a reboot.
[cut]
>
>>
>>> .probe = ged_probe,
>>> .driver = {
On Wed, Dec 06, 2017 at 12:13:16AM +0800, John Garry wrote:
SNIP
> ---
> tools/perf/pmu-events/jevents.c | 215
>
> 1 file changed, 198 insertions(+), 17 deletions(-)
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> i
On Wed, Dec 06, 2017 at 12:13:15AM +0800, John Garry wrote:
SNIP
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index b578aa2..a0d489e 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -588,7 +588,7 @@ static char *file
201 - 300 of 1246 matches
Mail list logo
