This is the first ARMv8 SoC from Socionext Inc.
Signed-off-by: Masahiro Yamada
---
Changes in v2:
- Split into a single patch
MAINTAINERS| 1 +
arch/arm64/boot/dts/Makefile | 1 +
arch/arm64/boot/dts/socionext/Makefile
On 2015/11/26 1:32, Paolo Bonzini wrote:
On 20/11/2015 09:57, Xiao Guangrong wrote:
You can move this patch to the front of
[PATCH 08/10] KVM: x86: MMU: Use for_each_rmap_spte macro instead of
pte_list_walk()
By moving kvm_mmu_mark_parents_unsync() to the behind of mmu_spte_set()
(then the
2015-11-24 18:39 GMT+09:00 Masahiro Yamada :
> Hi Arnd, Olof,
>
> Here is another series for UniPhier SoC family:
>
> - 1/4: add a new driver. The UniPhier System Bus is an external bus
> where on-board devices are connected to the SoC.
> (please check if the binding
On 11/26/2015 06:12 AM, Konrad Rzeszutek Wilk wrote:
> On Wed, Nov 25, 2015 at 03:56:03PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Wed, Nov 25, 2015 at 02:25:07PM -0500, Konrad Rzeszutek Wilk wrote:
xen/blkback: separate ring information out of struct xen_blkif
xen/blkback: pseudo
Hi Mark,
2015-11-25 2:38 GMT+09:00 Mark Rutland :
> Hi,
>
>> >> +UniPhier System Bus Controller
>> >> +--
>> >> +
>> >> +The UniPhier System Bus Controller is a hardware block with registers
>> >> that
>> >> +controls the System Bus accessing; how each bank is mapped
From: "Steven Rostedt (Red Hat)"
When crossing over to a new page, commit the current work. This will allow
readers to get data with less latency, and also simplifies the work to get
timestamps working for interrupted events.
Signed-off-by: Steven Rostedt
---
kernel/trace/ring_buffer.c | 7
From: "Steven Rostedt (Red Hat)"
The ftrace function hook utility has several internal checks to make sure
that whatever it modifies is exactly what it expects to be modifying. This
is essential as modifying running code can be extremely dangerous to the
system.
When an anomaly is detected,
From: "Steven Rostedt (Red Hat)"
When an anomaly is detected in the function call modification code,
ftrace_bug() is called to disable function tracing as well as give any
information that may help debug the problem. Currently, only the first found
trampoline that is attached to the failed
From: "Steven Rostedt (Red Hat)"
When an anomaly is found while modifying function code, ftrace_bug() is
called which disables the function tracing infrastructure and reports
information about what failed. If the code that is to be replaced does not
match what is expected, then actual code is
From: Tom Zanussi
When a trigger is enabled, the cond flag should be set beforehand,
otherwise a trigger that's expecting to process a trace record
(e.g. one with post_trigger set) could be invoked without one.
Likewise a trigger's cond flag should be reset after it's disabled,
not before.
Better output in ftrace_bug() for debugging when ftrace fails to modify
a location. Also, removed module modifications that were left over from
debugging before (rebased).
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1:
Russell King - ARM Linux writes:
> On Thu, Nov 26, 2015 at 12:50:08AM +, Måns Rullgård wrote:
>> If not calling the function saves an I-cache miss, the benefit can be
>> substantial. No, I have no proof of this being a problem, but it's
>> something that could happen.
>
> That's a
Hi
> > It is possible to remove this patch from topic/rcar,
> > and, apply it to topic/pcm-list ?
>
> > ccae40fa973f5b0eec5d5ad27e81c5a2b95f7b7c
> > (" ASoC: rcar: remove unused variable")
>
> I did that already.
Thanks !
--
To unsubscribe from this list: send the line "unsubscribe
Hello,
The checkpatch.pl GIT_COMMIT_ID rule appears to be designed to enforce
a minimum description when citing patches: 'commit <12+ chars of sha1>
(\"\")'. One (unintended?) consequence of this rule is
that unmodified 'cherry picked from commit ' (git cherry-pick
-x) lines are flagged.
- Is
These have only been included in linux-firmware.git.
Signed-off-by: Ben Hutchings
---
WHENCE | 3 ---
1 file changed, 3 deletions(-)
diff --git a/WHENCE b/WHENCE
index 1b880c9..9ecc984 100644
--- a/WHENCE
+++ b/WHENCE
@@ -1917,7 +1917,6 @@ Licence:
in hexadecimal or equivalent format,
On Wed, Nov 25, 2015 at 02:45:15AM -0800, David Rientjes wrote:
> On Wed, 25 Nov 2015, Joonsoo Kim wrote:
>
> > This patch uses is_via_compact_memory() to distinguish direct compaction.
>
> When I think of "direct compaction", I think of compaction triggered for
> high-order allocations from
Signed-off-by: Ben Hutchings
---
WHENCE | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/WHENCE b/WHENCE
index 412e5fb..1b880c9 100644
--- a/WHENCE
+++ b/WHENCE
@@ -1906,7 +1906,7 @@ Found in hex form in kernel source.
Driver: qed - QLogic 4 Ethernet Driver Core Module.
On Wed, Nov 25, 2015 at 01:00:22PM +0100, Michal Hocko wrote:
> On Tue 24-11-15 15:22:03, Joonsoo Kim wrote:
> > When I tested compaction in low memory condition, I found that
> > my benchmark is stuck in congestion_wait() at shrink_inactive_list().
> > This stuck last for 1 sec and after then it
Hi Marc,
On 11/25/2015 9:36 AM, Marc Zyngier wrote:
On Tue, 24 Nov 2015 15:04:53 -0800
Ray Jui wrote:
This patch adds PCIe MSI support for both PAXB and PAXC interfaces on
all iProc based platforms. The patch follows the latest trend in the
kernel to use MSI domain based implementation
On Wed, Nov 25, 2015 at 10:04:44AM -0600, Christoph Lameter wrote:
> > Although vmstat values aren't designed for accuracy, these are already
> > used by some sensitive places so it is better to be more accurate.
>
> The design is to sacrifice accuracy and the time the updates occur for
>
Hi Andrew,
[auto build test WARNING on input/next]
[cannot apply to v4.4-rc2 next-20151124]
url:
https://github.com/0day-ci/linux/commits/Andrew-Duggan/Input-synaptics-rmi4-Synaptics-RMI4-Driver-rebased-on-4-3/20151126-081351
base:
Signed-off-by: Fengguang Wu
---
hid-rmi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/hid-rmi.c b/drivers/hid/hid-rmi.c
index 81472c9..832c77d 100644
--- a/drivers/hid/hid-rmi.c
+++ b/drivers/hid/hid-rmi.c
@@ -497,7 +497,7 @@ static int
On 2015/11/26 9:10, 平松雅巳 / HIRAMATU，MASAMI wrote:
From: Wang Nan [mailto:wangn...@huawei.com]
If libelf unable to open debuginfo for an offline module but the ko has
symtab, something unexpected may happen.
# rm -rf ~/.debug/
# mv /usr/lib64/elfutils/libebl_x86_64.so{,.bak}
Please do give
On Thu, Nov 26, 2015 at 12:50:08AM +, Måns Rullgård wrote:
> If not calling the function saves an I-cache miss, the benefit can be
> substantial. No, I have no proof of this being a problem, but it's
> something that could happen.
That's a simplistic view of modern CPUs.
As I've already
Hi Andrew,
[auto build test ERROR on input/next]
[cannot apply to v4.4-rc2 next-20151124]
url:
https://github.com/0day-ci/linux/commits/Andrew-Duggan/Input-synaptics-rmi4-Synaptics-RMI4-Driver-rebased-on-4-3/20151126-081351
base:
Hi Bayi, Matthias,
Sorry for the late review, one comment below...
On Wed, Nov 18, 2015 at 11:30 AM, Bayi Cheng wrote:
> Add Mediatek nor flash node
>
> Signed-off-by: Bayi Cheng
> Acked-by: Brian Norris
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 18 +-
> 1 file
From: Wang Nan [mailto:wangn...@huawei.com]
>
>If libelf unable to open debuginfo for an offline module but the ko has
>symtab, something unexpected may happen.
>
> # rm -rf ~/.debug/
> # mv /usr/lib64/elfutils/libebl_x86_64.so{,.bak}
Please do give more possible usecase. removing libebl is
The mm-of-the-moment snapshot 2015-11-25-17-08 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Wed, Nov 25, 2015 at 11:54:06PM +, Kuninori Morimoto wrote:
> It is possible to remove this patch from topic/rcar,
> and, apply it to topic/pcm-list ?
> ccae40fa973f5b0eec5d5ad27e81c5a2b95f7b7c
> (" ASoC: rcar: remove unused variable")
I did that already.
signature.asc
Description: PGP
On Wed, Nov 25, 2015 at 03:31:23PM -0800, Kees Cook wrote:
> It may be useful to debug writes to the readonly sections of memory,
> so provide a cmdline "rodata=off" to allow for this.
>
> Suggested-by: H. Peter Anvin
> Signed-off-by: Kees Cook
> ---
> Documentation/kernel-parameters.txt | 4
On Wed, Nov 25, 2015 at 05:45:24PM -0600, Rob Herring wrote:
> On Mon, Nov 23, 2015 at 05:19:58PM +0800, Songjun Wu wrote:
> > Set GCK's parent as audio clock.
> > Signed-off-by: Songjun Wu
> Applied, thanks.
I already applied this to the ASoC tree.
signature.asc
Description: PGP signature
rhel-d0164adc89f6bb374d304ffcc375c6d2652fe67d-20151125-7326-77ivz1-0.yaml"
max_uptime: 674.07
initrd: "/osimage/debian/debian-x86_64-2015-02-07.cgz"
bootloader_append:
- root=/dev/ram0
- user=lkp
-
job=/lkp/scheduled/vm-vp-1G-8/bisect_fsmark-1x-32t-1HDD-xfs-16MB-60G-fsyncBef
Nicolas Pitre writes:
> On Thu, 26 Nov 2015, Måns Rullgård wrote:
>
>> Nicolas Pitre writes:
>>
>> > 3) In fact I was wondering if the overhead of the branch and back is
>> >really significant compared to the non trivial cost of a idiv
>> >instruction and all the complex
On Thu, 26 Nov 2015, Måns Rullgård wrote:
> Nicolas Pitre writes:
>
> > On Wed, 25 Nov 2015, Stephen Boyd wrote:
> >
> >> The ARM compiler inserts calls to __aeabi_uidiv() and
> >> __aeabi_idiv() when it needs to perform division on signed and
> >> unsigned integers. If a processor has support
Hi,
On Mon, Nov 23, 2015 at 4:28 PM, Doug Anderson wrote:
> John,
>
> On Thu, Nov 19, 2015 at 8:33 PM, John Youn wrote:
>> Patches 1-3:
>> Acked-by: John Youn
>>
>> Patch 2:
>> Tested-by: John Youn
>>
>> Tested on core version 3.20 using internal TE for un-aligned
>> buffers.
>>
>> I haven't
On Wed, 2015-11-25 at 23:11 +, Luis Henriques wrote:
> On Tue, Nov 24, 2015 at 10:33:59PM +, Ben Hutchings wrote:
> > 3.2.74-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Filipe Manana
> >
> > commit
On 25 Nov 2015 at 15:31, Kees Cook wrote:
> + rodata= [KNL]
> + on Mark read-only kernel memory as read-only (default).
> + off Leave read-only kernel memory writable for debugging.
> +
> +#ifdef CONFIG_DEBUG_RODATA
> +bool disable_mark_readonly;
WARN() takes a condition and a format string. The condition was
omitted. So I added it.
Signed-off-by: Geliang Tang
---
Changes in v3:
- fix kbuild test robot error.
Changes in v2:
- remove __func__ in WARN()
---
arch/arm/mach-davinci/board-dm355-evm.c | 4 +---
On Wed, 2015-11-25 at 23:05 +, Luis Henriques wrote:
> On Tue, Nov 24, 2015 at 10:33:59PM +, Ben Hutchings wrote:
> > 3.2.74-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Takashi Iwai
> >
> > commit
On 25.11.2015 21:11, Javier Martinez Canillas wrote:
> The header is already included in the
> exynos4412-odroid-common DTSI so there's no need to do it again
> in the DTS file.
>
> Signed-off-by: Javier Martinez Canillas
>
> ---
>
> arch/arm/boot/dts/exynos4412-odroidu3.dts | 1 -
> 1 file
On 11/25/2015 4:26 PM, kbuild test robot wrote:
Hi Yang,
[auto build test ERROR on v4.4-rc2]
[also build test ERROR on next-20151124]
url:
https://github.com/0day-ci/linux/commits/Yang-Shi/sparc64-gup-check-address-scope-legitimacy/20151126-065342
config: sparc64-allnoconfig (attached as
Hi Yang,
[auto build test ERROR on v4.4-rc2]
[also build test ERROR on next-20151124]
url:
https://github.com/0day-ci/linux/commits/Yang-Shi/sparc64-gup-check-address-scope-legitimacy/20151126-065342
config: sparc64-allnoconfig (attached as .config)
reproduce:
wget
On 11/26/2015 01:01 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
kernel/bpf/syscall.c
between commit:
c9da161c6517 ("bpf: fix clearing on persistent program array maps")
from the net tree and commit:
f99bf205dab0 ("bpf: add
On 25 Nov 2015 at 15:31, Kees Cook wrote:
> diff --git a/include/asm-generic/vmlinux.lds.h
> b/include/asm-generic/vmlinux.lds.h
> index c4bd0e2c173c..772c784ba763 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -256,6 +256,7 @@
> .rodata
On 11/10/2015 01:23 AM, Benjamin Tissoires wrote:
On Tue, Nov 10, 2015 at 12:13 AM, Dmitry Torokhov
wrote:
diff --git a/drivers/input/rmi4/rmi_f01.c b/drivers/input/rmi4/rmi_f01.c
index ee5f4a1..2d72dc8 100644
--- a/drivers/input/rmi4/rmi_f01.c
+++ b/drivers/input/rmi4/rmi_f01.c
@@ -176,6
Add devicetree binding for SPI devices.
Signed-off-by: Andrew Duggan
---
.../devicetree/bindings/input/rmi4/rmi_spi.txt | 57 ++
drivers/input/rmi4/rmi_spi.c | 44 -
2 files changed, 100 insertions(+), 1 deletion(-)
create mode
Add the transport driver for devices using RMI4 over SPI.
Signed-off-by: Andrew Duggan
---
drivers/input/rmi4/Kconfig | 9 +
drivers/input/rmi4/Makefile | 1 +
drivers/input/rmi4/rmi_spi.c | 422 +++
include/linux/rmi.h | 53 ++
4
The Synaptics RMI4 driver provides support for RMI4 devices. Instead of
duplicating the RMI4 processing code, make hid-rmi a transport driver
and register it with the Synaptics RMI4 core.
Signed-off-by: Andrew Duggan
---
drivers/hid/hid-rmi.c | 922
RMI4 F30 supports input from clickpad buttons and controls LEDs located
on the touchpad PCB. This patch adds support of the clickpad buttons and
defers supporting LEDs for the future.
Signed-off-by: Andrew Duggan
Signed-off-by: Benjamin Tissoires
---
drivers/input/rmi4/Kconfig | 9 +
2D sensors have several parameter which can be set in the platform data.
This patch adds support for getting those values from devicetree.
Signed-off-by: Andrew Duggan
---
.../bindings/input/rmi4/rmi_2d_sensor.txt | 54 +++
drivers/input/rmi4/rmi_2d_sensor.c |
Function 12 implements 2D touch position sensor for newer Synaptics touch
devices. It replaces F11 and no device will contain both functions.
Signed-off-by: Andrew Duggan
Signed-off-by: Christopher Heiny
---
drivers/input/rmi4/Kconfig | 10 +
drivers/input/rmi4/Makefile | 1 +
On Wed, Nov 25, 2015 at 01:51:04PM -0800, Stephen Boyd wrote:
> diff --git a/arch/arm/include/asm/cputype.h b/arch/arm/include/asm/cputype.h
> index 85e374f873ac..48c77d422a0d 100644
> --- a/arch/arm/include/asm/cputype.h
> +++ b/arch/arm/include/asm/cputype.h
> @@ -250,8 +250,14 @@ static inline
RMI4 currently defines two functions for reporting data for 2D sensors
(F11 and F12). This patch adds the common functionality which is shared
by devices with 2D reporting along with implementing functionality for
F11.
Signed-off-by: Andrew Duggan
Signed-off-by: Christopher Heiny
---
Add devicetree binding for I2C devices and add bindings for optional
parameters in the function drivers. Parameters for function drivers are
defined in child nodes for each of the functions.
Signed-off-by: Andrew Duggan
---
.../devicetree/bindings/input/rmi4/rmi_f01.txt | 39
Nicolas Pitre writes:
> On Wed, 25 Nov 2015, Stephen Boyd wrote:
>
>> The ARM compiler inserts calls to __aeabi_uidiv() and
>> __aeabi_idiv() when it needs to perform division on signed and
>> unsigned integers. If a processor has support for the udiv and
>> sdiv division instructions the calls
Synaptics uses the Register Mapped Interface (RMI) protocol as a
communications interface for their devices. This driver adds the core
functionality needed to interface with RMI4 devices.
RMI devices can be connected to the host via several transport protocols
and can supports a wide variety of
Add the transport driver for devices using RMI4 over I2C.
Signed-off-by: Andrew Duggan
Signed-off-by: Christopher Heiny
---
drivers/input/rmi4/Kconfig | 11 ++
drivers/input/rmi4/Makefile | 3 +
drivers/input/rmi4/rmi_i2c.c | 260 +++
3 files
This is a new patch series which squashes all of the development
history of the RMI4 driver into patches based on functionality. The
first patch adds the core RMI4 functionality needed by all RMI4 devices
and then the additional patches add transport and function drivers for
supporting various
On Wed, Nov 25, 2015 at 06:09:13PM -0500, Nicolas Pitre wrote:
> 3) In fact I was wondering if the overhead of the branch and back is
>really significant compared to the non trivial cost of a idiv
>instruction and all the complex infrastructure required to patch
>those branches
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
kernel/bpf/syscall.c
between commit:
c9da161c6517 ("bpf: fix clearing on persistent program array maps")
from the net tree and commit:
f99bf205dab0 ("bpf: add show_fdinfo handler for maps")
from the net-next
On Wed, Nov 25, 2015 at 11:50:30AM +0200, Adriana Reus wrote:
>
>
> On 25.11.2015 02:01, Rob Herring wrote:
> >On Tue, Nov 24, 2015 at 12:59:49PM +0200, Adriana Reus wrote:
> >>Add a property to allow changing the default power-saving mode.
> >>By default, at read raw the chip will activate and
On 11/25/2015 4:52 AM, Quentin Casasnovas wrote:
On Wed, Nov 25, 2015 at 12:21:45PM +, David Laight wrote:
From: Santosh Shilimkar
Sent: 24 November 2015 22:13
...
Sasha's found a NULL pointer dereference in the RDS connection code when
sending a message to an apparently unbound socket.
Hi Mark, Arnd
> > /opt/home/morimoto/WORK/linux/sound/soc/sh/rcar/core.c: In function
> > '__rsnd_kctrl_new':
> > /opt/home/morimoto/WORK/linux/sound/soc/sh/rcar/core.c:807:18: error:
> > 'soc_card' undeclared (first use in this function)
> >.index = rtd - soc_card->rtd,
> >
On Wed, Nov 18, 2015 at 05:18:11PM +0800, Yuan Yao wrote:
> new compatible string: "fsl,ls1021-qspi".
>
> Signed-off-by: Yuan Yao
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/mtd/fsl-quadspi.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
On Wed, Nov 18, 2015 at 12:20:58PM +, Stefan Wahren wrote:
> This company already provided some products, so add them to the
> vendor prefix list.
>
> Signed-off-by: Stefan Wahren
Applied, thanks.
Rob
> ---
> .../devicetree/bindings/vendor-prefixes.txt|1 +
> 1 file changed,
Hi Geert
> wrote:
> >> Besides, your property is already covered by of-thermal. Please convert
> >> your driver to use of-thermal, this way it will give you the flexibility
> >> to configure thermal data in DT.
> >
> > I see, but we need to keep compatibility for non-DT SoC.
> > (This driver is
On Thu, Nov 19, 2015 at 09:42:49AM +0900, Krzysztof Kozlowski wrote:
> SRAM bindings for various SoCs, using the mmio-sram genalloc
> API, are spread over different places - per SoC vendor. Since all of
> these are quite similar (they depend on mmio-sram) move them to a common
> place.
>
>
On Wed, Nov 25, 2015 at 01:51:03PM -0800, Stephen Boyd wrote:
> The ARM compiler inserts calls to __aeabi_uidiv() and
> __aeabi_idiv() when it needs to perform division on signed and
> unsigned integers. If a processor has support for the udiv and
> sdiv division instructions the calls to these
Hi LABBE
Thank you for your patch
> of_match_device could return NULL, and so cause a NULL pointer
> dereference later.
> Even if the probability of this case is very low, fixing it made
> static analyzers happy.
> Solving this with of_device_get_match_data made also code simplier.
>
>
On Mon, Nov 23, 2015 at 05:19:58PM +0800, Songjun Wu wrote:
> Set GCK's parent as audio clock.
>
> Signed-off-by: Songjun Wu
Applied, thanks.
Rob
> ---
>
> .../devicetree/bindings/sound/atmel-classd.txt |6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git
On Tue, Nov 24, 2015 at 08:31:51PM +0900, Masahiro Yamada wrote:
> Signed-off-by: Masahiro Yamada
Applied, thanks.
Rob
> ---
>
> Documentation/devicetree/bindings/arm/cpus.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt
>
On Tue, Nov 24, 2015 at 04:06:41PM +, Peter Maydell wrote:
> The existing device tree bindings assume that we are only trying to
> describe a single address space with a device tree (for ARM, either
> the Normal or the Secure world). Some uses for device tree need to
> describe both Normal and
Please pull this fix for the keys subsystem, for 4.4, from David Howells.
Note: this oops is triggerable by non-privileged users.
The following changes since commit 6ffeba9607343f15303a399bc402a538800d89d9:
Merge tag 'dm-4.4-fixes' of
The vDSO does not need to be writable after __init, so mark it as
__ro_after_init. The result kills the exploit method of writing to the
vDSO from kernel space resulting in userspace executing the modified code,
as shown here to bypass SMEP restrictions: http://itszn.com/blog/?p=21
The memory map
On Wed, Nov 25, 2015 at 3:05 PM, Michael Ellerman wrote:
> On Wed, 2015-11-25 at 07:03 -0800, Kees Cook wrote:
>> On Tue, Nov 24, 2015 at 4:54 PM, Michael Ellerman
>> wrote:
>> > On Tue, 2015-11-24 at 16:44 -0800, Kees Cook wrote:
>> > > On Tue, Nov 24, 2015 at 4:34 PM, Andy Lutomirski
>> > >
One of the easiest ways to protect the kernel from attack is to reduce
the internal attack surface exposed when a "write" flaw is available. By
making as much of the kernel read-only as possible, we reduce the
attack surface.
Many things are written to only during __init, and never changed
again.
One of the easiest ways to protect the kernel from attack is to reduce
the internal attack surface exposed when a "write" flaw is available. By
making as much of the kernel read-only as possible, we reduce the
attack surface.
Many things are written to only during __init, and never changed
again.
The new __ro_after_init section should be writable before init, but
not after. Validate that it gets updated at init and can't be written
to afterwards.
Signed-off-by: Kees Cook
---
drivers/misc/lkdtm.c | 29 ++---
1 file changed, 26 insertions(+), 3 deletions(-)
diff
It may be useful to debug writes to the readonly sections of memory,
so provide a cmdline "rodata=off" to allow for this.
Suggested-by: H. Peter Anvin
Signed-off-by: Kees Cook
---
Documentation/kernel-parameters.txt | 4
init/main.c | 31
On Wed, 25 Nov 2015, Stephen Boyd wrote:
> The ARM compiler inserts calls to __aeabi_uidiv() and
> __aeabi_idiv() when it needs to perform division on signed and
> unsigned integers. If a processor has support for the udiv and
> sdiv division instructions the calls to these support routines
> can
On Wed, Nov 25, 2015 at 08:16:00PM +0100, Andrew Lunn wrote:
> So looking at this list, could you maybe post the following, if they
> don't have dependencies. Going from only the subject, most look simple
> and should not be too much effort to get mainlined.
It's really not that simple. Remember
On Tue, Nov 24, 2015 at 02:09:18AM +0200, Constantine Shulyupin wrote:
> From: Constantine Shulyupin
>
> Introduced subnodes sensor, fan and peci with properties.
>
> Signed-off-by: Constantine Shulyupin
Acked-by: Rob Herring
> ---
> Changed in v9:
> - Fixed nuvoton,nct7802-sensor
> -
On Tue, Nov 24, 2015 at 10:33:59PM +, Ben Hutchings wrote:
> 3.2.74-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Filipe Manana
>
> commit f1cd1f0b7d1b5d4aaa5711e8f4e4898b0045cb6d upstream.
>
> When listing a inode's xattrs we have a
Add of_match_table for "brcm,bcm6345-wdt".
Use a NULL clock name when not on mach-bcm63xx so that the device tree
clock name does not have to be "periph".
Allow the watchdog to be selected on BMIPS_GENERIC and select the BCM6345
timer interrupt handler.
Signed-off-by: Simon Arlott
---
Patch 7
A couple of fixes for sendfile lockups caught by Dmitry + a fix
for ancient sysvfs symlink breakage. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (1):
fix sysvfs symlinks
Jan Kara (2):
vfs: Make sendfile(2)
On Wed, 2015-11-25 at 07:03 -0800, Kees Cook wrote:
> On Tue, Nov 24, 2015 at 4:54 PM, Michael Ellerman wrote:
> > On Tue, 2015-11-24 at 16:44 -0800, Kees Cook wrote:
> > > On Tue, Nov 24, 2015 at 4:34 PM, Andy Lutomirski
> > > wrote:
> > > > On Nov 24, 2015 1:38 PM, "Kees Cook" wrote:
> > > >
On Tue, Nov 24, 2015 at 10:33:59PM +, Ben Hutchings wrote:
> 3.2.74-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Takashi Iwai
>
> commit cadd16ea33a938d49aee99edd4758cc76048b399 upstream.
>
> We've had many reports that some
Check if user address is accessible in atomic version __get_user_pages_fast()
before walking the page table.
And, check if end > start in get_user_pages_fast(), otherwise fallback to slow
path.
Signed-off-by: Yang Shi
---
Just found slow_irqon label is not defined, added it to avoid compile
There is only one user of bcm63xx_timer and that is the watchdog.
To allow the watchdog driver to be used on machine types other than
mach-bcm63xx, it needs to use an interrupt instead of a custom register
function.
Modify bcm63xx_timer to only disable the timers (so that they don't
interfere
On Wednesday 25 November 2015 10:04:10 Ondrej Zary wrote:
> I think that PDMA should work with 53C400A too but seems that the driver was
> never able to do it.
>
> Although there is code for port-mapped transfer in NCR5380_pread(),
> NCR53C400_register_offset is defined to 0 in the port-mapped
Warn when the device is registered if the hardware watchdog is currently
running and report the remaining time left.
Signed-off-by: Simon Arlott
---
On 25/11/15 02:51, Guenter Roeck wrote:
> This is really two logical changes, isn't it ?
Patch 7 split into two patches.
Return the remaining time from the hardware control register.
Signed-off-by: Simon Arlott
---
On 25/11/15 02:51, Guenter Roeck wrote:
> This is really two logical changes, isn't it ?
Patch 7 correctly split into two patches this time.
drivers/watchdog/bcm63xx_wdt.c | 15 +++
1
On Wed, Nov 25, 2015, at 23:43, Eric Dumazet wrote:
> On Wed, 2015-11-25 at 23:32 +0100, Hannes Frederic Sowa wrote:
> > On Wed, Nov 25, 2015, at 23:09, Eric Dumazet wrote:
> > > On Wed, 2015-11-25 at 20:57 +, Rainer Weikusat wrote:
> > >
> > > > I do agree that keeping the ->sk_data_ready
Return the remaining time from the hardware control register.
Signed-off-by: Simon Arlott
---
On 25/11/15 02:51, Guenter Roeck wrote:
> This is really two logical changes, isn't it ?
Patch 7 split into two patches.
drivers/watchdog/bcm63xx_wdt.c | 17 -
1 file changed, 16
Check if user address is accessible in atomic version __get_user_pages_fast()
before walking the page table.
And, check if end > start in get_user_pages_fast(), otherwise fallback to slow
path.
Signed-off-by: Yang Shi
---
arch/sparc/mm/gup.c | 5 +
1 file changed, 5 insertions(+)
diff
Instead of using a fixed clock HZ in the driver, obtain it from the
"periph" clk that the watchdog timer uses.
Signed-off-by: Simon Arlott
---
Patch 7 split into two patches.
On 24/11/15 22:42, Florian Fainelli wrote:
> On 24/11/15 14:12, Simon Arlott wrote:
>> Instead of using a fixed clock HZ
Jarod Wilson :
[...]
> They do at least have a signed-off-by in the patches attached to the bug,
> so I'm working on touching up the descriptions and formatting, regression
> testing them on my laptop that has an alx-driven E2200 in it (which isn't
> affected by this bug), and then I can ship
On Wed, Nov 25, 2015 at 09:05:02PM +0100, Arnd Bergmann wrote:
> On Wednesday 25 November 2015 18:37:28 Russell King - ARM Linux wrote:
> > On Wed, Nov 25, 2015 at 05:09:37PM +0100, Andrew Lunn wrote:
> > > Russell, you are the last known user of mach-dove. What are your
> > > plans? You keep
On Tue, Nov 24, 2015 at 02:47:41PM +0100, Ludovic Desroches wrote:
> From: Wenyou Yang
>
> Add a DT property "atmel,twd-hold-cycles" to specify the HOLD
> filed of TWIHS_CWGR register to increase the TWD hold time.
>
> Signed-off-by: Wenyou Yang
> Signed-off-by: Ludovic Desroches
Acked-by:
On Wed, 2015-11-25 at 23:32 +0100, Hannes Frederic Sowa wrote:
> On Wed, Nov 25, 2015, at 23:09, Eric Dumazet wrote:
> > On Wed, 2015-11-25 at 20:57 +, Rainer Weikusat wrote:
> >
> > > I do agree that keeping the ->sk_data_ready outside of the lock will
> > > very likely have performance
101 - 200 of 1982 matches
Mail list logo
