Re: [PATCH v12 7/9] ACPI: Translate the I/O range of non-MMIO devices before scanning

On Tue, Jan 23, 2018 at 5:36 PM, John Garry wrote: > On some platforms(such as Hip06/Hip07), the legacy ISA/LPC devices access > I/O with some special host-local I/O ports known on x86. As their I/O space > are not memory mapped like PCI/PCIE MMIO host bridges, this patch is meant > to support a n

[no subject]

This is in regards to an inheritance on your surname, reply back using your email address, stating your full name for more details. Reply to email for info. Email me here ( ger...@dr.com )

[PATCH] mm/migrate: Rename various page allocation helper functions

Allocation helper functions for migrate_pages() remmain scattered with similar names making them really confusing. Rename these functions based on type of the intended migration. Function alloc_misplaced_dst_page() remains unchanged as its highly specialized. The renamed functions are listed below.

Re: [PATCH 4.14 103/156] scripts/faddr2line: extend usage on generic arch

Hi Greg Kroah-Hartman, Below commit is needed to resolve issue in this patch: Upstream commit 4cc90b4cc3d4955f79eae4f7f9d64e67e17b468e B.R. Changcheng On 17:58 Fri 02 Feb, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > ---

[PATCH] x86/build: Add arch/x86/tools/insn_decoder_test to gitignore

The file was generated by make command and should not be in source tree Signed-off-by: Progyan Bhattacharya --- arch/x86/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/.gitignore b/arch/x86/.gitignore index aff152c87cf4..5a82bac5e0bc 100644 --- a/arch/x86/.gitignore +++

[PATCH 2/2] kernel: compat: fixed a trailing whitespaces code style issue

From: devesh pradhan Fixed a coding style issue. Signed-off-by: devesh pradhan --- kernel/compat.c | 24 1 file changed, 16 insertions(+), 8 deletions(-) diff --git a/kernel/compat.c b/kernel/compat.c index d1cee656a7ed..d40c83792ae9 100644 --- a/kernel/compat.c +++ b

[PATCH] libata: fix length validation of ATAPI-relayed SCSI commands

From: Eric Biggers syzkaller reported a crash in ata_bmdma_fill_sg() when writing to /dev/sg1. The immediate cause was that the ATA command's scatterlist was not DMA-mapped, which causes 'pi - 1' to underflow, resulting in a write to 'qc->ap->bmdma_prd[0x]'. Strangely though, the flag A

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, 3 Feb 2018 10:27:59 -0500 Steven Rostedt wrote: > On Sat, 3 Feb 2018 22:38:17 +0900 > Masami Hiramatsu wrote: > > > This seems very similar feature of what kprobe-based event does. > > It is similar, but not the same as kprobes. It only focuses on > functions and their arguments, and s

Re: [PATCH 13/18] tracing: Add array type to function based events

On Sat, 3 Feb 2018 10:29:03 -0500 Steven Rostedt wrote: > On Sat, 3 Feb 2018 22:56:15 +0900 > Masami Hiramatsu wrote: > > > This idea looks good for kprobe events too. > > I'll try to implement same one :) > > We should have the two re-use the same code. > > In other words, I would like as mu

[PATCH 1/2] trace-cmd: Fix the detection for swig

From: Zamir SUN The current detection for swig will cause output to be /usr/bin/swig y So this will never be equal to y. With this patch, the swig path is removed from output, so the detection can work as expected. Fixes 3bf187a43b7e6302592552ecbc294e5820249687 Signed-off-by: Zamir SUN (Red Hat

[PATCH 2/2] trace-cmd: Change the way of getting python ldflags.

From: Zamir SUN Prior than this patch, Makefile detects python ldflags using a hardcoded python command. It will cause problems if we are building against python3 in the future when ldflags for python2 and python3 are different. With this patch, python ldflags are detected by corresponding python

[PATCH 0/2] trace-cmd: Improves python plugin support

From: Zamir SUN (Red Hat) This is a set of patch to improve trace-cmd python plugin support. Patch 1 fixes the detection for swig. With this patch, python-plugin can be built successfully. Patch 2 improves the detection for python ldflags. With this patch, ldflags can be detected with python3 i

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sun, Feb 4, 2018 at 6:30 AM, Alexei Starovoitov wrote: > On Sat, Feb 03, 2018 at 04:08:24PM -0500, Steven Rostedt wrote: >> OK, so no new development in this was wanted? So the entire talk about >> getting tracepoints into vfs and scheduling wasn't needed? > > I don't know who wants tracepoints

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

Hi Steve and Alexei, On Sun, Feb 4, 2018 at 6:17 AM, Steven Rostedt wrote: > On Sat, 3 Feb 2018 12:52:08 -0800 > Alexei Starovoitov wrote: > >> It's a user space job. > > BTW, I asked around at DevConf.cz, and nobody I talked with (besides > Arnaldo), have used eBPF. The "path to hello world" is

Re: [PATCH AUTOSEL for 4.14 006/110] KVM/x86: Check input paging mode when cs.l is set

On Sat, Feb 03, 2018 at 05:24:29PM -0800, Eric Biggers wrote: >On Sat, Feb 03, 2018 at 06:00:29PM +, Sasha Levin wrote: >> From: Lan Tianyu >> >> [ Upstream commit f29810335965ac1f7bcb501ee2af5f039f792416 ] >> >> Reported by syzkaller: >> WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On 2/3/18 12:17 PM, Stephen Hemminger wrote: > On Sat, 3 Feb 2018 14:29:04 +0100 > Christian Brauner wrote: > >> +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, >> + struct nlattr *tb[], >> + struct netlink_

Re: [PATCH 5/5] USB: serial: f81232: fix bulk_in/out size

On Thu, Feb 01, 2018 at 01:50:55PM +0800, Ji-Ze Hong (Peter Hong) wrote: > Hi Johan, > > Johan Hovold 於 2018/1/30 下午 12:11 寫道: > > On Mon, Jan 22, 2018 at 03:58:47PM +0800, Ji-Ze Hong (Peter Hong) wrote: > >> diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c > >> index a054f69

Re: [PATCH 3/5] USB: serial: f81232: enable remote wakeup via RX/RI pin

On Thu, Feb 01, 2018 at 11:13:01AM +0800, Ji-Ze Hong (Peter Hong) wrote: > Hi Johan, > > Johan Hovold 於 2018/1/30 上午 11:57 寫道: > > On Mon, Jan 22, 2018 at 03:58:45PM +0800, Ji-Ze Hong (Peter Hong) wrote: > >> The F81232 can do remote wakeup via RX/RI pin with pulse. > >> This patch will use device

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Sun, Feb 4, 2018 at 1:25 AM, Dan Williams wrote: > On Sat, Feb 3, 2018 at 4:14 PM, Andy Lutomirski wrote: >> On Sat, Feb 3, 2018 at 11:21 PM, Dan Williams >> wrote: >>> At entry userspace may have populated the extra registers outside the >>> syscall calling convention with values that could

Re: [PATCH] cifs: silence compiler warnings showing up with gcc-8.0.0

merged into cifs-2.6.git for-next On Fri, Feb 2, 2018 at 9:48 AM, Arnd Bergmann wrote: > This bug was fixed before, but came up again with the latest > compiler in another function: > > fs/cifs/cifssmb.c: In function 'CIFSSMBSetEA': > fs/cifs/cifssmb.c:6362:3: error: 'strncpy' offset 8 is out of

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Sat, Feb 3, 2018 at 4:14 PM, Andy Lutomirski wrote: > On Sat, Feb 3, 2018 at 11:21 PM, Dan Williams > wrote: >> At entry userspace may have populated the extra registers outside the >> syscall calling convention with values that could be useful in a >> speculative execution attack. Clear them

Re: [PATCH AUTOSEL for 4.14 006/110] KVM/x86: Check input paging mode when cs.l is set

On Sat, Feb 03, 2018 at 06:00:29PM +, Sasha Levin wrote: > From: Lan Tianyu > > [ Upstream commit f29810335965ac1f7bcb501ee2af5f039f792416 ] > > Reported by syzkaller: > WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.c:5631 > x86_emulate_insn+0x557/0x15f0 [kvm] > Modules linked

[PATCH] PCI: update location of pci.ids file

From: Randy Dunlap Update the URL for the pci.ids file and add locations for its mirrors. Signed-off-by: Randy Dunlap Cc: Martin Mares Cc: Michal Vaner --- Documentation/PCI/pci.txt |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- linux-next-20180202.orig/Documentation/PCI/pc

[GIT PULL] fscrypt updates for 4.16

Note: there will be a merge conflict; please just take the chunk which calls fscrypt_encrypt_symlink() from the fscrypt tree. This will end up dropping the kzalloc() -> f2fs_kzalloc() change, which means the fscrypt-specific allocation won't get tested by f2fs's kmalloc error injection system; whi

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sat, Feb 03, 2018 at 09:35:26PM +0100, Pavel Machek wrote: >On Sat 2018-02-03 18:00:59, Sasha Levin wrote: >> From: Matthieu CASTET >> >> [ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ] >> >> With the current code, the following sequence won't work : >> echo timer > trigger >> >> e

[PATCH v3] Input: matrix_keypad - fix keypad does not response

If matrix_keypad_stop() is calling and the keypad interrupt is triggered, disable_row_irqs() is called by both matrix_keypad_interrupt() and matrix_keypad_stop() at the same time. then disable_row_irqs() is called twice, and the device enter suspend state before keypad->work is executed. At this co

Re: [PATCH 1/3] perf tools: Fix period/freq terms setup

On Sat, Feb 3, 2018 at 7:30 AM, Jiri Olsa wrote: > On Fri, Feb 02, 2018 at 10:45:46AM -0800, Stephane Eranian wrote: >> Jiri, >> >> On Thu, Feb 1, 2018 at 12:38 AM, Jiri Olsa wrote: >> > Stephane reported that we don't set properly PERIOD >> > sample type for events with period term defined. >> >

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Sat, Feb 3, 2018 at 11:21 PM, Dan Williams wrote: > At entry userspace may have populated the extra registers outside the > syscall calling convention with values that could be useful in a > speculative execution attack. Clear them to minimize the kernel's attack > surface. Note, this only clea

Re: [PATCH v2] Input: matrix_keypad - fix keypad does not response

On Sat, 2018-02-03 at 11:35 -0800, Dmitry Torokhov wrote: Hi Dmitry Torokhov > > If matrix_keypad_stop() is calling and the keypad interrupt is > > triggered, > > disable_row_irqs() is called by both matrix_keypad_interrupt() and > > matrix_keypad_stop() at the same time. then disable_row_irqs() is

[PATCH] parport_pc: Add support for WCH CH382L PCI-E single parallel port card.

WCH CH382L is a PCI-E adapter with 1 parallel port. It is similair to CH382 but serial ports are not soldered on board. Detected as Serial controller: Device 1c00:3050 (rev 10) (prog-if 05 [16850]) Signed-off-by: Alexander Gerasiov --- drivers/parport/parport_pc.c | 4 1 file changed, 4 ins

[PATCH] parport_pc: Add support for WCH CH382L PCI-E single parallel port card.

WCH CH382L is a PCI-E adapter with 1 parallel port. It is similair to CH382 but serial ports are not soldered on board. Detected as Serial controller: Device 1c00:3050 (rev 10) (prog-if 05 [16850]) Signed-off-by: Alexander Gerasiov --- drivers/parport/parport_pc.c | 4 1 file changed, 4 ins

[PATCH 3/3] x86/entry: Clear registers for compat syscalls

From: Andi Kleen At entry userspace may have populated registers with values that could be useful in a speculative execution attack. Clear them to minimize the kernel's attack surface. [djbw: rename the macro, only clear the extra registers] Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter An

[PATCH 2/3] x86/entry: Clear registers for 64bit exceptions/interrupts

From: Andi Kleen Clear the 'extra' registers on entering the 64bit kernel for exceptions and interrupts. The common registers are not cleared since they are likely clobbered well before they can be exploited in a speculative execution attack. Signed-off-by: Andi Kleen Signed-off-by: Dan William

[PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

At entry userspace may have populated the extra registers outside the syscall calling convention with values that could be useful in a speculative execution attack. Clear them to minimize the kernel's attack surface. Note, this only clears the extra registers and not the unused registers for syscal

[PATCH 0/3] x86/entry: clear registers to sanitize speculative usages

At entry userspace may have populated callee saved registers with values that could be useful in a speculative execution attack. Clear them to minimize the kernel's attack surface. Note, this is done to make it harder to find / manipulate exploitable sequences in the kernel. The clearing is limit

[tip:x86/pti] KVM/x86: Add IBPB support

Commit-ID: 15d45071523d89b3fb7372e2135fbd72f6af9506 Gitweb: https://git.kernel.org/tip/15d45071523d89b3fb7372e2135fbd72f6af9506 Author: Ashok Raj AuthorDate: Thu, 1 Feb 2018 22:59:43 +0100 Committer: Thomas Gleixner CommitDate: Sat, 3 Feb 2018 23:06:51 +0100 KVM/x86: Add IBPB support

[tip:x86/pti] KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL

Commit-ID: b2ac58f90540e39324e7a29a7ad471407ae0bf48 Gitweb: https://git.kernel.org/tip/b2ac58f90540e39324e7a29a7ad471407ae0bf48 Author: KarimAllah Ahmed AuthorDate: Sat, 3 Feb 2018 15:56:23 +0100 Committer: Thomas Gleixner CommitDate: Sat, 3 Feb 2018 23:06:52 +0100 KVM/SVM: Allow direc

[tip:x86/pti] KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL

Commit-ID: d28b387fb74da95d69d2615732f50cceb38e9a4d Gitweb: https://git.kernel.org/tip/d28b387fb74da95d69d2615732f50cceb38e9a4d Author: KarimAllah Ahmed AuthorDate: Thu, 1 Feb 2018 22:59:45 +0100 Committer: Thomas Gleixner CommitDate: Sat, 3 Feb 2018 23:06:52 +0100 KVM/VMX: Allow direc

[tip:x86/pti] KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES

Commit-ID: 28c1c9fabf48d6ad596273a11c46e0d0da3e14cd Gitweb: https://git.kernel.org/tip/28c1c9fabf48d6ad596273a11c46e0d0da3e14cd Author: KarimAllah Ahmed AuthorDate: Thu, 1 Feb 2018 22:59:44 +0100 Committer: Thomas Gleixner CommitDate: Sat, 3 Feb 2018 23:06:52 +0100 KVM/VMX: Emulate MSR

[tip:x86/pti] KVM/x86: Update the reverse_cpuid list to include CPUID_7_EDX

Commit-ID: b7b27aa011a1df42728d1768fc181d9ce69e6911 Gitweb: https://git.kernel.org/tip/b7b27aa011a1df42728d1768fc181d9ce69e6911 Author: KarimAllah Ahmed AuthorDate: Thu, 1 Feb 2018 22:59:42 +0100 Committer: Thomas Gleixner CommitDate: Sat, 3 Feb 2018 23:06:51 +0100 KVM/x86: Update the

[PATCH 3/3] x86/Kconfig : Explicitly enumerate i686-class cpus in Kconfig

The X86_P6_NOP config class leaves out many i686-class cpus. Instead, explicitly enumerate all these cpus. Using a configuration with M686 currently sets X86_MINIMUM_CPU_FAMILY=5 instead of the correct value 6. Booting on an i586 it will fail to generate the "This kernel requires an i686 CPU, but

[PATCH 2/3] x86/Kconfig : Exclude i586-class cpus lacking PAE support from HIGHMEM64G Kconfig group

i586-class machines also lack support for Physical Address Extension (PAE), so add them to the exclusion list Signed-off-by: Matthew Whitehead --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 423e4b6..c45fe6d 10064

[PATCH 1/3] x86/Kconfig : Add missing i586-class cpus to X86_CMPXCHG64 Kconfig group

Several i586-class cpus supporting this instruction are missing from the X86_CMPXCHG64 config group. Using a configuration with either M586TSC or M586MMX currently sets X86_MINIMUM_CPU_FAMILY=4 instead of the correct value 5. Booting on an i486 it will fail to generate the "This kernel requires a

Re: [PATCH] audit: update bugtracker and source URIs

On Sat, Feb 3, 2018 at 12:33 AM, Richard Guy Briggs wrote: > Since the Linux Audit project has transitioned completely over to > github, update the MAINTAINERS file and the primary audit source file to > reflect that reality. > > Signed-off-by: Richard Guy Briggs > --- > MAINTAINERS| 1 - >

Re: [PATCH AUTOSEL for 4.9 28/52] led: core: Fix brightness setting when setting delay_off=0

On 02/03/2018 10:22 PM, Jacek Anaszewski wrote: > Hi Sasha, > > All 3.18, 4.4 and 4.9 also require the follow-up > patch [0], similarly like autosel did it for 4.14, > since this one alone breaks the other use case. Actually after taking closer look, it turns out that the patch [0] applies cleanl

[PULL REQUEST] i2c for 4.16

Linus, I2C has the following changes for you: * new flag to mark DMA safe buffers in i2c_msg. Also, some infrastructure around it. And docs. * huge refactoring of the at24 driver led by the new maintainer Bartosz * update I2C bus recovery to send STOP after recovery * conversion from gpio to gp

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On Sat, Feb 3, 2018 at 3:32 PM, Igor Stoppa wrote: > > > On 03/02/18 22:12, Boris Lukashev wrote: > >> Regarding the notion of validated protected memory, is there a method >> by which the resulting checksum could be used in a lookup >> table/function to resolve the location of the protected data?

Re: [GIT PULL tools] Linux kernel memory model

On Sat, 3 Feb 2018, Paul E. McKenney wrote: > Please see below for an initial patch to this effect. This activity > proved to be more productive than expected for these tests, which certainly > supports our assertion that locking needs more testing... > > MP+polocks.litmus > MP+porevlocks.litmus

Re: [PATCH v2 1/2] arm64: dts: rockchip: add i2s0-2ch-bus pins on rk3399

Am Samstag, 3. Februar 2018, 16:50:15 CET schrieb Klaus Goger: > Add pin definition for I2S0 if used as a 2-channel only bus. > > Signed-off-by: Klaus Goger applied for 4.17 Thanks Heiko

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, Feb 3, 2018 at 9:04 AM, Mathieu Desnoyers wrote: > > The approach proposed here will introduce an expectation that internal > function signatures never change in the kernel, else it would break user-space > tools hooking on those functions. No, I really don't think so. There's two reason

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, Feb 03, 2018 at 04:17:32PM -0500, Steven Rostedt wrote: > On Sat, 3 Feb 2018 12:52:08 -0800 > Alexei Starovoitov wrote: > > > It's a user space job. > > BTW, I asked around at DevConf.cz, and nobody I talked with (besides > Arnaldo), have used eBPF. The "path to hello world" is quite hig

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, Feb 03, 2018 at 04:08:24PM -0500, Steven Rostedt wrote: > On Sat, 3 Feb 2018 12:52:08 -0800 > Alexei Starovoitov wrote: > > > On Sat, Feb 03, 2018 at 02:02:17PM -0500, Steven Rostedt wrote: > > > > > > From those that were asking about having "trace markers" (ie. > > > Facebook), they to

Re: [PATCH AUTOSEL for 4.9 28/52] led: core: Fix brightness setting when setting delay_off=0

Hi Sasha, All 3.18, 4.4 and 4.9 also require the follow-up patch [0], similarly like autosel did it for 4.14, since this one alone breaks the other use case. [0] https://lkml.org/lkml/2018/2/3/249 On 02/03/2018 07:03 PM, Sasha Levin wrote: > From: Matthieu CASTET > > [ Upstream commit 2b83ff96

[PATCH] HID: magicmouse: Delete an error message for a failed memory allocation in magicmouse_probe()

From: Markus Elfring Date: Sat, 3 Feb 2018 22:15:05 +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/hid/hid-magicmouse.c | 4 +--- 1 file changed, 1 insertion(+),

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, 3 Feb 2018 12:52:08 -0800 Alexei Starovoitov wrote: > It's a user space job. BTW, I asked around at DevConf.cz, and nobody I talked with (besides Arnaldo), have used eBPF. The "path to hello world" is quite high. This interface is extremely simple to use, and one doesn't need to install

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, 3 Feb 2018 12:52:08 -0800 Alexei Starovoitov wrote: > On Sat, Feb 03, 2018 at 02:02:17PM -0500, Steven Rostedt wrote: > > > > From those that were asking about having "trace markers" (ie. > > Facebook), they told us they can cope with kernel changes. > > There is some misunderstanding

[PATCH 2/2] HID: ntrig: Improve a size determination in ntrig_probe()

From: Markus Elfring Date: Sat, 3 Feb 2018 21:48:39 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was dete

[PATCH 1/2] HID: ntrig: Delete an error message for a failed memory allocation in ntrig_probe()

From: Markus Elfring Date: Sat, 3 Feb 2018 21:46: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/hid/hid-ntrig.c | 4 +--- 1 file changed, 1 insertion(+), 3 del

[PATCH 0/2] HID: N-Trig: Adjustments for ntrig_probe()

From: Markus Elfring Date: Sat, 3 Feb 2018 21:54:32 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation Improve a size determination drivers/hid/hid-ntrig.c | 6 ++ 1 file chan

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, Feb 03, 2018 at 02:02:17PM -0500, Steven Rostedt wrote: > > From those that were asking about having "trace markers" (ie. > Facebook), they told us they can cope with kernel changes. There is some misunderstanding here. We never asked for this interface. We're perfectly fine with existing

Re: Can RCU stall lead to hard lockups?

On Fri, Feb 02, 2018 at 05:44:30PM -0600, Serge E. Hallyn wrote: > Quoting Paul E. McKenney (paul...@linux.vnet.ibm.com): > > On Tue, Jan 09, 2018 at 06:11:14AM -0800, Tejun Heo wrote: > > > Hello, Paul. > > > > > > On Mon, Jan 08, 2018 at 08:24:25PM -0800, Paul E. McKenney wrote: > > > > > I don'

Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0

On Sat 2018-02-03 18:00:59, Sasha Levin wrote: > From: Matthieu CASTET > > [ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ] > > With the current code, the following sequence won't work : > echo timer > trigger > > echo 0 > delay_off > * at this point we call > ** led_delay_off_stor

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On 03/02/18 22:12, Boris Lukashev wrote: > Regarding the notion of validated protected memory, is there a method > by which the resulting checksum could be used in a lookup > table/function to resolve the location of the protected data? What I have in mind is a checksum at page/vmap_area level,

Why is 4.14.17 not marked as "longterm" at https://www.kernel.org/ ?

It differs from the statement made at https://www.kernel.org/category/releases.html -- Toralf PGP C4EACDDE 0076E94E

[PATCH 2/2] HID: picoLCD: Improve a size determination in picolcd_probe()

From: Markus Elfring Date: Sat, 3 Feb 2018 21:05:55 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was dete

Re: PROBLEM: NULL pointer dereference in dell_set_arguments() in 4.15

On Sat, Feb 03, 2018 at 07:20:21PM +0300, Alexander Sergeyev wrote: # first bad commit: [549b4930f057658dc50d8010e66219233119a4d8] platform/x86: dell-smbios: Introduce dispatcher for SMM calls From source code (at 549b4930f057) it looks like dell_set_arguments() which writes to `buffer` is cal

[PATCH 1/2] HID: picoLCD: Delete an error message for a failed memory allocation in three functions

From: Markus Elfring Date: Sat, 3 Feb 2018 21:00:37 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/hid/hid-picolcd_core.c | 1 - drivers/hid/hid-picolcd_fb.c

[PATCH 0/2] HID-picoLCD: Adjustments for three function implementations

From: Markus Elfring Date: Sat, 3 Feb 2018 21:12:24 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in three functions Improve a size determination in picolcd_probe() drivers/h

Re: [PATCH 1/2] srcu: Prevent sdp->srcu_gp_seq_needed_exp counter wrap

On Wed, Jan 31, 2018 at 10:39:53PM +0300, Ildar Ismagilov wrote: > Signed-off-by: Ildar Ismagilov I did apply this for testing and review, thank you and good eyes! However, I had to: 1. hand-edit it to make it work against the rcu/dev branch of my -rcu tree: git://git.kerne

Re: [PATCH 2/2] srcu: reduce scans of srcu_data in counter wrap check

On Wed, Jan 31, 2018 at 10:42:21PM +0300, Ildar Ismagilov wrote: > This patch reduce scans of srcu_data in case of a srcu_struct > tree have more than one levels Good catch!!! Applied for testing and review. I had to hand-apply this patch as well, and also fill out the commit log. In addition, i

Re: [GIT PULL tools] Linux kernel memory model

On Wed, Jan 31, 2018 at 10:00:06AM +0100, Ingo Molnar wrote: > * Paul E. McKenney wrote: > > On Mon, Jan 29, 2018 at 07:57:24AM +0100, Ingo Molnar wrote: [ . . . ] > A couple of questions: > > - Would it be possible to include all the nice descriptions of the litmus > tests in > the tests th

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On Sat, Feb 3, 2018 at 2:57 PM, Igor Stoppa wrote: >>> On Thu, 25 Jan 2018, Matthew Wilcox wrote: > It's worth having a discussion about whether we want the pmalloc API or whether we want a slab-based API. > I'd love to have some feedback specifically about the API. > > I have also some

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

>> On Thu, 25 Jan 2018, Matthew Wilcox wrote: >>> It's worth having a discussion about whether we want the pmalloc API >>> or whether we want a slab-based API. I'd love to have some feedback specifically about the API. I have also some idea about userspace and how to extend the pmalloc concept

[PATCH 4/6] Protectable Memory

The MMU available in many systems running Linux can often provide R/O protection to the memory pages it handles. However, the MMU-based protection works efficiently only when said pages contain exclusively data that will not need further modifications. Statically allocated variables can be segreg

[PATCH 3/6] struct page: add field for vm_struct

When a page is used for virtual memory, it is often necessary to obtian a handler to the corresponding vm_struct, which refers to the virtually continuous area generated when invoking vmalloc. The struct page has a "mapping" field, which can be re-used, to store a pointer to the parent area. This

[PATCH 2/6] genalloc: selftest

Introduce a set of macros for writing concise test cases for genalloc. The test cases are meant to provide regression testing, when working on new functionality for genalloc. Primarily they are meant to confirm that the various allocation strategy will continue to work as expected. The execution

[PATCH 1/6] genalloc: track beginning of allocations

The genalloc library is only capable of tracking if a certain unit of allocation is in use or not. It is not capable of discerning where the memory associated to an allocation request begins and where it ends. The reason is that units of allocations are tracked by using a bitmap, where each bit r

[RFC PATCH v13 0/6] mm: security: ro protection for dynamic data

This patch-set introduces the possibility of protecting memory that has been allocated dynamically. The memory is managed in pools: when a memory pool is turned into R/O, all the memory that is part of it, will become R/O. A R/O pool can be destroyed, to recover its memory, but it cannot be turne

Re: [PATCH v2] Input: matrix_keypad - fix keypad does not response

Hi Zhang, On Sat, Feb 03, 2018 at 11:58:16PM +0800, Zhang Bo wrote: > If matrix_keypad_stop() is calling and the keypad interrupt is triggered, > disable_row_irqs() is called by both matrix_keypad_interrupt() and > matrix_keypad_stop() at the same time. then disable_row_irqs() is called > twice, a

Re: [PATCH net 1/1 v1] rtnetlink: require unique netns identifier

On Sat, 3 Feb 2018 14:29:04 +0100 Christian Brauner wrote: > +static int rtnl_ensure_unique_netns_attr(const struct sock *sk, > + struct nlattr *tb[], > + struct netlink_ext_ack *extack) > +{ > + int ret = -EINVAL; > +

Re: RFC(V3): Audit Kernel Container IDs

On 2/2/2018 3:24 PM, Paul Moore wrote: > On Fri, Feb 2, 2018 at 5:19 PM, Simo Sorce wrote: >> On Fri, 2018-02-02 at 16:24 -0500, Paul Moore wrote: >>> On Wed, Jan 10, 2018 at 2:00 AM, Richard Guy Briggs wrote: On 2018-01-09 11:18, Simo Sorce wrote: > On Tue, 2018-01-09 at 07:16 -0500, Ri

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

On Sat, 3 Feb 2018 17:04:14 + (UTC) Mathieu Desnoyers wrote: > The approach proposed here will introduce an expectation that internal > function signatures never change in the kernel, else it would break user-space > tools hooking on those functions. I had this exact discussion with Linus.

Re: [PATCH 08/19] clk: meson: add regmap to the clock controllers

On Wed, Jan 31, 2018 at 7:09 PM, Jerome Brunet wrote: > This change register a regmap in meson8b, gxbb and axg controllers. > The clock are still accessing their registers directly through iomem. > Once all clocks handled by these controllers have been move to regmap, > the regmap register will be

[PATCH AUTOSEL for 4.14 013/110] mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM

From: Sascha Hauer [ Upstream commit fdf2e821052958a114618a95ab18a300d0b080cb ] When erased subpages are read then the BCH decoder returns STATUS_ERASED if they are all empty, or STATUS_UNCORRECTABLE if there are bitflips. When there are bitflips, we have to set these bits again to show the uppe

Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events

I need to add a "Quick guide" and "Tips and tricks" section to the document. To explain the arguments better... Simple args are: "int val", "unsigned int val", "char x", "unsigned long addr", Also the types: "s32 val", "u32 val", "s8 x", "u64 addr" The above are all printed in decimal "%d"

[PATCH AUTOSEL for 4.14 024/110] scsi: core: check for device state in __scsi_remove_target()

From: Hannes Reinecke [ Upstream commit 81b6c999897919d5a16fedc018fe375dbab091c5 ] As it turned out device_get() doesn't use kref_get_unless_zero(), so we will be always getting a device pointer. Consequently, we need to check for the device state in __scsi_remove_target() to avoid tripping ove

[PATCH AUTOSEL for 4.14 016/110] parisc: Reduce thread stack to 16 kb

From: John David Anglin [ Upstream commit da57c5414f49ef9e4bcb9ae0bbafd1d650b31411 ] In testing, I found that the thread stack can be 16 kB when using an irq stack. Without it, the thread stack needs to be 32 kB. Currently, the irq stack is 32 kB. While it probably could be 16 kB, I would prefe

[PATCH AUTOSEL for 4.14 025/110] xfrm: Reinject transport-mode packets through tasklet

From: Herbert Xu [ Upstream commit acf568ee859f098279eadf551612f103afdacb4e ] This is an old bugbear of mine: https://www.mail-archive.com/netdev@vger.kernel.org/msg03894.html By crafting special packets, it is possible to cause recursion in our kernel when processing transport-mode packets at

[PATCH AUTOSEL for 4.14 014/110] mtd: nand: brcmnand: Zero bitflip is not an error

From: Albert Hsieh [ Upstream commit e44b9a9c135727f3410e029910275f40681dc8bc ] A negative return value of brcmstb_nand_verify_erased_page() indicates a real bitflip error of an erased page, and other return values (>= 0) show the corrected bitflip number. Zero return value means no bitflip, but

[PATCH AUTOSEL for 4.14 027/110] mac80211_hwsim: Fix a possible sleep-in-atomic bug in hwsim_get_radio_nl

From: Jia-Ju Bai [ Upstream commit 162bd5e5fd921785077b5862d8f2ffabe2fe11e5 ] The driver may sleep under a spinlock. The function call path is: hwsim_get_radio_nl (acquire the spinlock) nlmsg_new(GFP_KERNEL) --> may sleep To fix it, GFP_KERNEL is replaced with GFP_ATOMIC. This bug is found b

[PATCH AUTOSEL for 4.14 039/110] net: stmmac: Fix TX timestamp calculation

From: Fredrik Hallenberg [ Upstream commit 200922c93f008e03ddc804c6dacdf26ca1ba86d7 ] When using GMAC4 the value written in PTP_SSIR should be shifted however the shifted value is also used in subsequent calculations which results in a bad timestamp value. Signed-off-by: Fredrik Hallenberg Sig

[PATCH AUTOSEL for 4.14 064/110] perf/x86/intel: Plug memory leak in intel_pmu_init()

From: Thomas Gleixner [ Upstream commit 7ad1437d6ace0e450a6c1167720608ad660b191d ] A recent commit introduced an extra merge_attr() call in the skylake branch, which causes a memory leak. Store the pointer to the extra allocated memory and free it at the end of the function. Fixes: a5df70c354c

[PATCH AUTOSEL for 4.14 015/110] ipv6: icmp6: Allow icmp messages to be looped back

From: Brendan McGrath [ Upstream commit 588753f1eb18978512b1c9b85fddb457d46f9033 ] One example of when an ICMPv6 packet is required to be looped back is when a host acts as both a Multicast Listener and a Multicast Router. A Multicast Router will listen on address ff02::16 for MLDv2 messages.

Re: [PATCH 17/19] clk: meson: rework meson8b cpu clock

Hi Jerome, On Wed, Jan 31, 2018 at 7:09 PM, Jerome Brunet wrote: > Instead of migrating meson cpu_clk to clk_regmap, like the other meson > clock drivers, we take advantage of the massive rework to get rid of it > completely, and solve (the first part) of the related FIXME notice. > > As pointed

Re: [PATCH 18/19] clk: meson: remove obsolete cpu_clk

On Wed, Jan 31, 2018 at 7:09 PM, Jerome Brunet wrote: > meson8b cpu_clk has been replaced by a set of divider and mux clocks. > meson_cpu_clk is no longer used and can be removed as I mentioned in the other series: I've seen the system lock up with the "old" clk-cpu implementation. the new code st

[PATCH AUTOSEL for 4.14 026/110] x86/stacktrace: Make zombie stack traces reliable

From: Josh Poimboeuf [ Upstream commit 6454b3bdd138dfc640deb5e7b9a0668fca2d55dd ] Commit: 1959a60182f4 ("x86/dumpstack: Pin the target stack when dumping it") changed the behavior of stack traces for zombies. Before that commit, /proc//stack reported the last execution path of the zombie be

[PATCH AUTOSEL for 4.14 040/110] net: stmmac: Fix bad RX timestamp extraction

From: Fredrik Hallenberg [ Upstream commit a1762456993893795030d911106a7650481db0ef ] As noted in dwmac4_wrback_get_rx_timestamp_status the timestamp is found in the context descriptor following the current descriptor. However the current code looks for the context descriptor in the current desc

[PATCH AUTOSEL for 4.14 017/110] ARM: 8731/1: Fix csum_partial_copy_from_user() stack mismatch

From: Chunyan Zhang [ Upstream commit 36b0cb84ee858f02c256d26f0cb4229c78e3399e ] An additional 'ip' will be pushed to the stack, for restoring the DACR later, if CONFIG_CPU_SW_DOMAIN_PAN defined. However, the fixup still get the err_ptr by add #8*4 to sp, which results in the fact that the code

[PATCH AUTOSEL for 4.14 028/110] spi: atmel: fixed spin_lock usage inside atmel_spi_remove

From: Radu Pirea [ Upstream commit 66e900a3d225575c8b48b59ae1fe74bb6e5a65cc ] The only part of atmel_spi_remove which needs to be atomic is hardware reset. atmel_spi_stop_dma calls dma_terminate_all and this needs interrupts enabled. atmel_spi_release_dma calls dma_release_channel and dma_relea

[PATCH AUTOSEL for 4.14 059/110] tipc: error path leak fixes in tipc_enable_bearer()

From: Tommi Rantala [ Upstream commit 19142551b2be4a9e13838099fde1351386e5e007 ] Fix memory leak in tipc_enable_bearer() if enable_media() fails, and cleanup with bearer_disable() if tipc_mon_create() fails. Acked-by: Ying Xue Acked-by: Jon Maloy Signed-off-by: Tommi Rantala Signed-off-by: D

  1   2   3   4   5   >