On 18/07/2017 at 15:22, Ludovic Desroches wrote:
> A new compatible string is introduced for SMC on sama5d2 to manage a
> different layout of the registers.
>
> Signed-off-by: Ludovic Desroches
> Acked-by: Rob Herring
Acked-by: Nicolas Ferre
> ---
> Documentation/devicetree/bindings/mfd/atme
From: Laurentiu Tudor
The mc-bus specific field, fsl_mc in struct msi_desc is missing its
comment so add it.
Signed-off-by: Laurentiu Tudor
---
Notes:
-v2
-no changes
include/linux/msi.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/msi.h b/include/linux/msi.h
in
From: Laurentiu Tudor
Nothing from linux/irqchip/arm-gic-v3.h is used, so the #include can be
safely dropped.
Signed-off-by: Laurentiu Tudor
---
Notes:
-v2
-no changes
drivers/staging/fsl-mc/bus/fsl-mc-msi.c| 1 -
drivers/staging/fsl-mc/bus/irq-gic-v3-its-fsl-mc-msi.
From: Laurentiu Tudor
No need to use arch-specific memory barriers; switch to using generic
ones. The rmb()s were useless so drop them.
Signed-off-by: Laurentiu Tudor
---
Notes:
-v2
-no changes
drivers/staging/fsl-mc/bus/mc-sys.c | 6 ++
1 file changed, 2 insertions(+), 4 deleti
On Tue, Jul 18, 2017 at 6:12 AM, Eric W. Biederman
wrote:
> Kees Cook writes:
>
>> On Mon, Jul 10, 2017 at 10:07 AM, Eric W. Biederman
>> wrote:
>>> Kees Cook writes:
>>>
On Mon, Jul 10, 2017 at 1:46 AM, Eric W. Biederman
wrote:
>
> But you miss it.
>
> The "point of
Michael Cree writes:
> On Fri, Jul 14, 2017 at 05:59:06AM -0500, Eric W. Biederman wrote:
>> in which cases the oddities will happen let alone test them. Plus at
>> least for ia64 and alpha those architectures don't appear to be
>> receiving updates for new syscalls, and no new hardware is being
The patch
spi: loopback-test: make several module parameters static
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
> The patch is untested but I can work on this if that fits in with the
> plans for tty.
I think this is the right direction.
Alan
ebied...@xmission.com (Eric W. Biederman) writes:
> David Miller writes:
>
>> From: "Eric W. Biederman"
>> Date: Fri, 30 Jun 2017 07:39:01 -0500
>>
>>> diff --git a/arch/sparc/include/uapi/asm/siginfo.h
>>> b/arch/sparc/include/uapi/asm/siginfo.h
>>> index 2d9b79ccaa50..6bc5c677e92f 100644
>>>
On Tue, Jun 06, 2017 at 02:04:22PM +0200, Richard Leitner wrote:
> For the configuration of the automatic volume control block (AVC), which
> reduces loud signals and amplifies low level signals for easier
> listening, following controls are added:
This doesn't apply against current code, please c
On 7/18/2017 4:36 AM, Ingo Molnar wrote:
* Tom Lendacky wrote:
Create a new function attribute, __nostackp, that can used to turn off
stack protection on a per function basis.
Signed-off-by: Tom Lendacky
---
include/linux/compiler-gcc.h | 2 ++
include/linux/compiler.h | 4
2 f
Alexey Budankov writes:
>> Apparently the patches are not threaded, so one needs to fish them out
>> one by one in order to review.
>
> Thanks for feedback. The BKM in this case is just to keep subject unchanged,
> right?
No, just use git-send-email, it will set all the email headers correctly
On 7/18/2017 7:03 AM, Thomas Gleixner wrote:
On Mon, 17 Jul 2017, Tom Lendacky wrote:
This patch series provides support for AMD's new Secure Memory Encryption (SME)
feature.
SME can be used to mark individual pages of memory as encrypted through the
page tables. A page of memory that is marked
Hi,
On 18/07/17 11:15, Viresh Kumar wrote:
> On 17-07-17, 10:35, Joel Fernandes wrote:
> > On Mon, Jul 17, 2017 at 1:04 AM, Viresh Kumar
> > wrote:
> > > On 16-07-17, 01:04, Joel Fernandes wrote:
>
> > >> + if (sg_cpu->iowait_boost_pending) {
> > >> + sg_cpu->iowait_boost_pendin
Commit e2fe14564d3316d1 ("oom_reaper: close race with exiting task")
guarded whole OOM reaping operations using oom_lock. But there was no
need to guard whole operations. We needed to guard only setting of
MMF_OOM_REAPED flag because get_page_from_freelist() in
__alloc_pages_may_oom() is called wit
Unconditional reset dwmac before HW init if reset controller is present.
In existing implementation we reset dwmac only after second module
probing:
(module load -> unload -> load again [reset happens])
Now we reset dwmac at every module load:
(module load [reset happens] -> unload -> load again
Today sending a signal with rt_sigqueueinfo and receving it on
a signalfd does not work reliably. The issue is that reading
a signalfd instead of returning a siginfo returns a signalfd_siginfo and
the kernel must convert from one to the other.
The kernel does not currently have the code to deduc
On Tue, Jul 18, 2017 at 01:26:50PM +0200, Johannes Poehlmann wrote:
> o Replace incorrect register offsett calculation by
> direct configuration of bus_shift in mfd-cell.
> Indirect definition of address-shift by resource size
> was unobvious and should have used a binary log.
> o Make endian clean
This patch converts the of CONFIG_X86_5LEVEL check to runtime checks for
p4d folding.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/mm/fault.c| 2 +-
arch/x86/mm/ident_map.c| 2 +-
arch/x86/mm/init_64.c | 30 ++
arch/x86/mm/kasan_init_6
For boot-time switching between 4- and 5-level paging we need to be able
to fold p4d page table level at runtime. It requires variable
PGDIR_SHIFT and PTRS_PER_P4D.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/kaslr.c| 5 +
arch/x86/include/asm/pgtable_32.h |
On Tue 18-07-17 23:06:50, Tetsuo Handa wrote:
> Commit e2fe14564d3316d1 ("oom_reaper: close race with exiting task")
> guarded whole OOM reaping operations using oom_lock. But there was no
> need to guard whole operations. We needed to guard only setting of
> MMF_OOM_REAPED flag because get_page_fr
Setting si_code to __SI_FAULT results in a userspace seeing
an si_code of 0. This is the same si_code as SI_USER. Posix
and common sense requires that SI_USER not be a signal specific
si_code. As such this use of 0 for the si_code is a pretty
horribly broken ABI.
Given that alpha is on it's las
Looks like we only need pre-built page tables for XEN_PV and XEN_PVH
cases. Let's not provide them for other configuration.
This patch if preparation for boot-time switching between 4- and 5-level
paging. pgd_index() is going to depend on a variable and cannot be
easily used in head_64.S.
Signed-
This patch changes page table helpers to fold p4d at runtime.
The logic is the same as in .
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/paravirt.h | 3 ++-
arch/x86/include/asm/pgalloc.h | 5 -
arch/x86/include/asm/pgtable.h | 10 +-
3 files changed, 15 insertions(
Fix the debug print statements in these tests where they reference
si_codes and in particular __SI_FAULT. __SI_FAULT is a kernel
internal value and should never be seen by userspace.
While I am in there also fix si_code_str. si_codes are an enumeration
there are not a bitmap so == and not & is t
Setting si_code to __SI_FAULT results in a userspace seeing
an si_code of 0. This is the same si_code as SI_USER. Posix
and common sense requires that SI_USER not be a signal specific
si_code. As such this use of 0 for the si_code is a pretty
horribly broken ABI.
This use of of __SI_FAULT is on
On Tue, Jul 18, 2017 at 01:26:53PM +0200, Johannes Poehlmann wrote:
> Signed-off-by: Johannes Poehlmann
> Acked-by: Evgeniy Polyakov
> ---
> drivers/w1/masters/ds1wm.c | 15 ++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
And here as well.
>
> diff --git a/drivers/w1/maste
struct siginfo is a union and the kernel since 2.4 has been hiding a union
tag in the high 16bits of si_code using the values:
__SI_KILL
__SI_TIMER
__SI_POLL
__SI_FAULT
__SI_CHLD
__SI_RT
__SI_MESGQ
__SI_SYS
While this looks plausible on the surface, in practice this situation has
not worked well.
On Tue, Jul 18, 2017 at 11:06:50PM +0900, Tetsuo Handa wrote:
> Commit e2fe14564d3316d1 ("oom_reaper: close race with exiting task")
> guarded whole OOM reaping operations using oom_lock. But there was no
> need to guard whole operations. We needed to guard only setting of
> MMF_OOM_REAPED flag bec
On Tue, Jul 18, 2017 at 3:37 PM, wrote:
> From: Laurentiu Tudor
>
> As raw device io functions are not portable and don't handle byte-order
> (triggering suspicion that endianness isn't handled well) switch to
> using the standard api.
> Since MC expects LE byte-order and the upper layers alread
We have a weird and problematic intersection of features that when
they all come together result in ambiguous siginfo values, that
we can not support properly.
- Supporting fcntl(F_SETSIG,...) with arbitrary valid signals.
- Using positive values for POLL_IN, POLL_OUT, POLL_MSG, ..., etc
that i
This patch prepare decompression code to boot-time switching between 4-
and 5-level paging.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/head_64.S | 24
1 file changed, 24 insertions(+)
diff --git a/arch/x86/boot/compressed/head_64.S
b/arch/x86/boot/c
Setting si_code to __SI_FAULT results in a userspace seeing
an si_code of 0. This is the same si_code as SI_USER. Posix
and common sense requires that SI_USER not be a signal specific
si_code. As such this use of 0 for the si_code is a pretty
horribly broken ABI.
This was introduced in 2.3.41 s
This patch adds detection of 5-level paging at boot-time and adjusts
virtual memory layout and folds p4d page table layer if needed.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/boot/compressed/kaslr.c| 13 +--
arch/x86/entry/entry_64.S | 12 +++
arch/x86/include/
[ This patchset is on top my previous 5-level paging patchset[1] ]
The basic idea is to implement the same logic as pgtable-nop4d.h provides,
but at runtime.
Runtime folding is only implemented for CONFIG_X86_5LEVEL=y case. With the
option disabled, we do compile-time folding as before..
Initial
Setting si_code to __SI_FAULT results in a userspace seeing
an si_code of 0. This is the same si_code as SI_USER. Posix
and common sense requires that SI_USER not be a signal specific
si_code. As such this use of 0 for the si_code is a pretty
horribly broken ABI.
Given that ia64 is on it's last
On Tue, Jul 18, 2017 at 01:26:52PM +0200, Johannes Poehlmann wrote:
> Signed-off-by: Johannes Poehlmann
> Acked-by: Evgeniy Polyakov
> ---
> drivers/w1/masters/ds1wm.c | 6 ++
> 1 file changed, 6 insertions(+)
Same here, I need a changelog text.
thanks,
greg k-h
Please pull:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.13-1
One fix for a problem introduced in the most recent merge window and
found by Dave Jones and KASAN.
--b.
Trond Myklebust (1):
nfsd: Fix a memory scribble in the callback channel
fs/nfsd/nfs4callback.c | 6 +++---
1 f
We need to be able to adjust virtual memory layout at runtime to be able
to switch between 4- and 5-level paging at boot-time.
KASLR already has movable __VMALLOC_BASE, __VMEMMAP_BASE and __PAGE_OFFSET.
Let's re-use it.
Signed-off-by: Kirill A. Shutemov
---
arch/x86/include/asm/kaslr.h
This controller maps 128 input lines to 24 output lines.
The output lines are routed to GIC SPI 0 to 23.
This driver muxes LEVEL_HIGH IRQs onto output line 0,
and gives every EDGE_RISING IRQ a dedicated output line.
---
Changes from v3 to v4:
o Register tango_alloc() instead of tango_map() in order
On Tue, Jul 18, 2017 at 01:26:51PM +0200, Johannes Poehlmann wrote:
> Signed-off-by: Johannes Poehlmann
> Acked-by: Evgeniy Polyakov
> ---
> drivers/w1/masters/ds1wm.c | 4
> 1 file changed, 4 insertions(+)
>
I can not take a patch without any changelog text at all, sorry. Please
write s
We are going to support boot-time switching between 4- and 5-level
paging. For KASAN it means we cannot have different KASAN_SHADOW_OFFSET
for different paging modes: the constant is passed to gcc to generate
code and cannot be changed at runtime.
This patch changes KASAN code to use 0xdc0
All pieces of the puzzle are in place and we can now allow to boot with
CONFIG_X86_5LEVEL=y on a machine without la57 support.
Kernel will detect that la57 is missing and fold p4d at runtime.
Update documentation and Kconfig option description to reflect the
change.
Signed-off-by: Kirill A. Shut
By this point we have functioning boot-time switching between 4- and
5-level paging mode. But naive approach comes with cost.
Numbers below are for kernel build, allmodconfig, 5 times.
CONFIG_X86_5LEVEL=n:
Performance counter stats for 'sh -c make -j100 -B -k >/dev/null' (5 runs):
17308719.
On 18/07/17 16:15, Kirill A. Shutemov wrote:
> This patch converts the of CONFIG_X86_5LEVEL check to runtime checks for
> p4d folding.
>
> Signed-off-by: Kirill A. Shutemov
> ---
> arch/x86/mm/fault.c| 2 +-
> arch/x86/mm/ident_map.c| 2 +-
> arch/x86/mm/init_64.c
Attention:Beneficiary
I am Meliana Trump, and I am writing to inform you about your Bank
Check Draft brought back 16/07/2017 by the United Embassy Mr John
Moore from the government of Benin Republic in the white house
Washington DC been mandated to be deliver to your home address once
you reconfi
On Tue, Jul 18, 2017 at 3:37 PM, wrote:
> --- a/drivers/staging/fsl-dpaa2/Kconfig
> +++ b/drivers/staging/fsl-dpaa2/Kconfig
> @@ -4,7 +4,7 @@
>
> config FSL_DPAA2
> bool "Freescale DPAA2 devices"
> - depends on FSL_MC_BUS
> + depends on FSL_MC_BUS && ARCH_LAYERSCAPE
>
This adds the connector name when printing a debug message about the DP
link training result. It is useful to figure out what connector is
failing when multiple DP connectors are used.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/i915/intel_dp_link_training.c | 8 ++--
1 file changed
Hi Arnd,
On 07/18/2017 05:18 PM, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 3:37 PM, wrote:
>> From: Laurentiu Tudor
>>
>> As raw device io functions are not portable and don't handle byte-order
>> (triggering suspicion that endianness isn't handled well) switch to
>> using the standard api
On Tue, Jul 18, 2017 at 3:37 PM, wrote:
> From: Laurentiu Tudor
>
> Apart from a small change (first patch) which adds a missing comment,
> this series make the bus driver compile on other architectures, as per
> GregKH comment [1].
> Compiled tested on:
> - booke powerpc (corenet{32,64}_smp_de
On Tue, Jul 18, 2017 at 4:26 PM, Laurentiu Tudor
wrote:
>
> Maybe i made an error in my previous emails, but the hi-lo variant is
> the correct one. The command execution is triggered when the _first_
> 32-bit half of the header (header&0x) is written, so that's why
> it must be written la
From: "Gautham R. Shenoy"
Hi,
The stop4 idle state on POWER9 is a deep idle state which loses
hypervisor resources, but whose latency is low enough that it can be
exposed via cpuidle.
Until now, the deep idle states which lose hypervisor resources (eg:
winkle) were only exposed via CPU-Hotplug.
From: "Gautham R. Shenoy"
The stop4 idle state on POWER9 is a deep idle state which loses
hypervisor resources, but whose latency is low enough that it can be
exposed via cpuidle.
Until now, the deep idle states which lose hypervisor resources (eg:
winkle) were only exposed via CPU-Hotplug. Hen
From: "Gautham R. Shenoy"
Currently we use the stop-api provided by the firmware to program the
SLW engine to restore the values of hypervisor resources that get lost
on deeper idle states (such as winkle). Since the deep states were
only used for CPU-Hotplug on POWER8 systems, we would program
Hi,
On 18.07.2017 17:01, Alexander Shishkin wrote:
> Alexey Budankov writes:
>
>>> Apparently the patches are not threaded, so one needs to fish them out
>>> one by one in order to review.
>>
>> Thanks for feedback. The BKM in this case is just to keep subject unchanged,
>> right?
>
> No, just
On Mon, Jul 17, 2017 at 07:07:00PM -0400, ok...@codeaurora.org wrote:
> Maybe, I need to understand the design better. I was curious why completion
> and submission queues were protected by a single lock causing lock
> contention.
Ideally the queues are tied to CPUs, so you couldn't have one threa
Commit 16ecba59bc333d6282ee057fb02339f77a880beb has apparently broken
at least the 82574L under heavy load (as in load heavy enough to cause
packet drops). In this case, when running in MSI-X mode, the Other
Causes interrupt fires about 3000 times per second, but not due to link
state changes. Un
Current implementation relies on L1 line length which might easily
be smaller than L2 line (which is usually the case BTW).
Imagine this typical case: L2 line is 128 bytes while L1 line is
64-bytes. Now we want to allocate small buffer and later use it for DMA
(consider IOC is not available).
kma
On Tue, Jul 18, 2017 at 12:22 AM, Greg KH wrote:
> On Mon, Jul 17, 2017 at 03:14:29PM -0500, Alan Tull wrote:
>> > Also, we're thinking that some operations require that you first "acquire
>> > ownership" of the respective device, which I believe maps more easily to
>> > open() and ioctls than sys
On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote:
> This patch allows the user to disable write combined mapping
> of the efifb framebuffer console using an nowc option.
>
> A customer noticed major slowdowns while logging to the console
> with write combining enabled, on other tasks ru
On Mon, Jul 17, 2017 at 8:17 PM, Wu, Hao wrote:
>> On Sun, Jun 25, 2017 at 8:52 PM, Wu Hao wrote:
>>
>> Hi Hao,
>>
>> I'm making my way through this (very large) patchset. Some minor
>> comments below.
>>
>
> Hi Alan
>
> Thanks for your review. : )
Hi Hao,
Thanks, this looks good and will be h
Hi Arnd,
On 07/18/2017 05:25 PM, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 3:37 PM, wrote:
>
>> --- a/drivers/staging/fsl-dpaa2/Kconfig
>> +++ b/drivers/staging/fsl-dpaa2/Kconfig
>> @@ -4,7 +4,7 @@
>>
>> config FSL_DPAA2
>> bool "Freescale DPAA2 devices"
>> - depends on FSL
On Wed, 2017-06-14 at 18:12 -0700, Thomas Garnier wrote:
> Ensure the address limit is a user-mode segment before returning to
> user-mode. Otherwise a process can corrupt kernel-mode memory and
> elevate privileges [1].
>
> The set_fs function sets the TIF_SETFS flag to force a slow path on
> ret
On Mon, Jul 17, 2017 at 1:20 PM, Jan Kiszka wrote:
> On 2017-07-17 19:48, Rob Herring wrote:
>> On Thu, Jul 13, 2017 at 08:44:26AM +0200, Jan Kiszka wrote:
>>> The device-specific property should be prefixed with the vendor name
>>> Change this and document the bindings of this platform device.
>>
Am Dienstag, 18. Juli 2017, 10:52:12 CEST schrieb Greg Kroah-Hartman:
Hi Greg,
>
> > I have stated the core concerns I have with random.c in [1]. To remedy
> > these core concerns, major changes to random.c are needed. With the past
> > experience, I would doubt that I get the changes into rando
On 07/17/2017 04:56 PM, Waiman Long wrote:
> On 07/17/2017 10:14 AM, Peter Zijlstra wrote:
>> On Sun, Jul 16, 2017 at 10:07:20PM -0400, Tejun Heo wrote:
>>> v4: - Updated to marking each cgroup threaded as suggested by PeterZ.
>>>
>>> +On creation, a cgroup is always a domain cgroup and can be made
On Tue, Jul 18, 2017 at 4:36 PM, Laurentiu Tudor
wrote:
> Good point, I'll take care of it. But don't you mean COMPILE_TEST be
> added on the actual MC_BUS config, like so:
>
> config FSL_MC_BUS
> bool "QorIQ DPAA2 fsl-mc bus driver"
> - depends on OF && ARCH_LAYERSCAPE
> +
On 7/17/2017 3:59 PM, Toshi Kani wrote:
The ghes_edac driver was introduced in 2013 [1], but it has not
been enabled by any distro yet.
Ubuntu is expected to enable this soon.
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technolo
Hi Arnd,
On 07/18/2017 05:26 PM, Arnd Bergmann wrote:
> On Tue, Jul 18, 2017 at 3:37 PM, wrote:
>> From: Laurentiu Tudor
>>
>> Apart from a small change (first patch) which adds a missing comment,
>> this series make the bus driver compile on other architectures, as per
>> GregKH comment [1].
>
Replace hard-coded function names in strings with "%s", __func__
in the goldfish_nand.c file. Issue found by checkpatch.pl.
Signed-off-by: Chris Coffey
---
drivers/staging/goldfish/goldfish_nand.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/
Update links to the PDFs of PCI and interrupt mapping bindings, as
the previous links are broken.
Signed-off-by: Harvey Hunt
Cc: Bjorn Helgaas
Cc: linux-...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Documentation/devicetree/bindings/pci/pci.txt | 4 ++--
On Wed 2017-06-28 11:37:27, Joe Lawrence wrote:
> diff --git a/samples/livepatch/livepatch-shadow-mod.c
> b/samples/livepatch/livepatch-shadow-mod.c
> new file mode 100644
> index ..423f4b7b0adb
> --- /dev/null
> +++ b/samples/livepatch/livepatch-shadow-mod.c
> + * Usage
> + * -
>
On Mon, Jul 17, 2017 at 06:12:35PM +0800, Chen-Yu Tsai wrote:
> On Mon, Jul 17, 2017 at 5:14 PM, Maxime Ripard
> wrote:
> > Hi,
> >
> > On Fri, Jul 14, 2017 at 02:42:54PM +0800, Chen-Yu Tsai wrote:
> >> The MMC2 clock supports a new timing mode. When the new mode is active,
> >> the output clock r
After commit 3d375d78593c ("mm: update callers to use HASH_ZERO flag"),
drop unused pidhash_size in pidhash_init().
Signed-off-by: Kefeng Wang
---
kernel/pid.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/pid.c b/kernel/pid.c
index 731c4e5..c69c30d 100644
--- a/kernel/pid.c
+++ b
Christophe Leroy writes:
> gup_hugepte() checks if pages are present and readable, and
> when 'write' is set, also checks if the pages are writable.
>
> Initially this was done by checking if _PAGE_PRESENT and
> _PAGE_READ were set. In addition, _PAGE_WRITE was verified for write
> accesses.
>
>
Reviewed-by: Pavel Tatashin
On 07/18/2017 10:47 AM, Kefeng Wang wrote:
After commit 3d375d78593c ("mm: update callers to use HASH_ZERO flag"),
drop unused pidhash_size in pidhash_init().
Signed-off-by: Kefeng Wang
---
kernel/pid.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kerne
On Fri, Jul 14, 2017 at 01:51:12PM +0800, Jeremy Kerr wrote:
> Hi Thierry,
>
> > I /think/ Jeremy Kerr (To'ed) would be a good person to contact about
> > this.
> >
> > Jeremy, anything you can do about this?
>
> OK, all sorted. I've updated Jerome's entry in the database to suit.
Headers do in
On Tue, Jul 18, 2017 at 12:02:01PM +0800, Chen-Yu Tsai wrote:
> The explanation for the endpoint ID numbering scheme is convoluted
> and hard to understand.
>
> This patch aims to improve the readability of it by combining the
> existing two paragraphs, while also providing a diagram example,
> an
On Fri, Jul 14, 2017 at 04:51:31PM -0700, Kees Cook wrote:
> On Fri, Jul 14, 2017 at 2:28 PM, Daniel Micay wrote:
> > Using strscpy was wrong because FORTIFY_SOURCE is passing the maximum
> > possible size of the outermost object, but strscpy defines the count
> > parameter as the exact buffer siz
On Tue, Jul 18, 2017 at 09:21:22AM -0400, Stefan Berger wrote:
> On 07/18/2017 08:30 AM, Vivek Goyal wrote:
> > On Tue, Jul 18, 2017 at 08:05:18AM -0400, Stefan Berger wrote:
> > > On 07/18/2017 07:48 AM, Vivek Goyal wrote:
> > > > On Mon, Jul 17, 2017 at 04:50:22PM -0400, Stefan Berger wrote:
> >
KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and
sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below).
Make sure all fields of an IPv6 address are initialized, which
guarantees that the IPv4 fields are also initialized.
On Mon, 17 Jul 2017, Alexander Popov wrote:
> Christopher, if I change BUG_ON() to VM_BUG_ON(), it will be disabled by
> default
> again, right?
It will be enabled if the distro ships with VM debugging on by default.
On Tue, Jul 18, 2017 at 08:58:22AM +0200, Greg KH wrote:
> On Sat, Jul 15, 2017 at 11:43:05AM +, Joseph Wright wrote:
> > Declare private function static to fix sparse warning:
> >
> > ion_cma_heap.c:109:5: warning: symbol '__ion_add_cma_heaps' \
> > was not declared. Should it be static?
On 07/17/2017 10:28 PM, Suman Anna wrote:
> From: Nishanth Menon
>
> Texas Instrument's System Control Interface (TI-SCI) Message Protocol
> is implemented in Keystone 2 generation 66AK2G SoC with the PMMC entity.
>
> Add the ti-sci node representing this 66AK2G PMMC module.
>
> Signed-off-by:
On Tue, Jul 18, 2017 at 4:55 PM, Alexander Potapenko wrote:
> KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and
> sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below).
> Make sure all fields of an IPv6 address are initialized, which
> guarantees that the IPv4 fields ar
On 07/05/2017 10:05 AM, Juergen Gross wrote:
> Commit dc6416f1d711eb4c1726e845d653235dcaae12e1 ("xen/x86: Call
> cpu_startup_entry(CPUHP_AP_ONLINE_IDLE) from xen_play_dead()")
> introduced an error leading to a stack overflow of the idle task when
> a cpu was brought offline/online many times: by c
This series does few amendments to architectural ACPI code related to
boot, in particularly to arch/x86/kernel/acpi/boot.c.
First two patches are amendments to satisfy compiler and static analyzer
(the order is changed from first version which had been applied; in case
of partial update first pa
As per note in 5.2.9 Fixed ACPI Description Table (FADT) chapter of ACPI
specification OSPM will ignore fields related to the ACPI HW register
interface, one of which is SCI_INT.
Follow the spec and ignore any configuration done for interrupt line
defined by SCI_INT if FADT specifies HW reduced pl
Sparse complains about wrong address space used in __acpi_map_table()
and in __acpi_unmap_table().
arch/x86/kernel/acpi/boot.c:127:29: warning: incorrect type in return
expression (different address spaces)
arch/x86/kernel/acpi/boot.c:127:29:expected char *
arch/x86/kernel/acpi/boot.c:127:29:
Some code in acpi_parse_x2apic() conditionally compiled, though parts of
it are being used in any case. This annoys gcc.
arch/x86/kernel/acpi/boot.c: In function ‘acpi_parse_x2apic’:
arch/x86/kernel/acpi/boot.c:203:5: warning: variable ‘enabled’ set but not used
[-Wunused-but-set-variable]
u8 e
Sometimes it's useful to have when mp_config_acpi_legacy_irqs() is called.
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/acpi/boot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 6d5b1346268a..0186d3bae610
Some platform might take care of legacy devices on theirs own.
Let's allow them to do that by exporting a weak function.
Signed-off-by: Andy Shevchenko
---
arch/x86/kernel/acpi/boot.c | 2 +-
include/linux/acpi.h| 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/
On Tue, Jul 18, 2017 at 2:32 PM, Alexey Khoroshilov
wrote:
> clk_disable_unprepare(info->clk) is missed in of_platform_serial_probe(),
> while irq_dispose_mapping(port->irq) is missed in of_platform_serial_setup().
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
Reviewed-by:
Alexey Budankov writes:
> Ok. I see. So what are the next steps needs to be taken towards the upstream
> of this work?
> What do I need to do more to have this stuff included into the kernel?
> Could you please clarify this?
Well, normally you'd be sending new versions of your patchset until th
On Tue, 18 Jul 2017, Reshetova, Elena wrote:
> > On Tue, 18 Jul 2017, Reshetova, Elena wrote:
> >
> > > > On Tue, 18 Jul 2017, Elena Reshetova wrote:
> > > >
> > > > > The below script can be used to detect potential misusage
> > > > > of atomic_t type and API for reference counting purposes.
>
Fix a comment misspell
Signed-off-by: Xaralampos Mainas
---
drivers/staging/rtl8723bs/core/rtw_efuse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_efuse.c
b/drivers/staging/rtl8723bs/core/rtw_efuse.c
index 8e29802..44b92ef 100644
--- a/
On Tue, Jul 18, 2017 at 04:24:06PM +0200, Juergen Gross wrote:
> On 18/07/17 16:15, Kirill A. Shutemov wrote:
> > diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
> > index cab28cf2cffb..b0530184c637 100644
> > --- a/arch/x86/xen/mmu_pv.c
> > +++ b/arch/x86/xen/mmu_pv.c
> > @@ -1209,7 +12
Hi,
On Tue, Jul 18, 2017 at 4:20 AM, Chris Zhong wrote:
> The DP is using the same audio infoframe payload as hdmi, per DP 1.3
> spec, but it has a different header. Provide a new interface here,
> it just packs the payload.
>
> Signed-off-by: Chris Zhong
> ---
>
> Changes in v2: None
>
> drive
On Tue, Jul 18, 2017 at 02:56:47PM +0800, Li, Aubrey wrote:
> On 2017/7/18 14:43, Thomas Gleixner wrote:
> > On Mon, 17 Jul 2017, Andi Kleen wrote:
> >
> >>> We need a tradeoff here IMHO. I'll check Daniel's work to understand
> >>> how/if
> >>> it's better than menu governor.
> >>
> >> I still w
Hi,
parisc64 builds, specifically generic-64bit_defconfig, fail to build
in mainline as follows.
hppa64-linux-ld:
hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divdi3.o)(.text+0xec):
cannot reach $$divU
hppa64-linux/bin/../lib/gcc/hppa64-linux/4.9.0/libgcc.a(_divdi3.o):
In function `__
501 - 600 of 1285 matches
Mail list logo
