[PATCH 6/6] Input: remove remaining unneeded MODULE_VERSION() usage

MODULE_VERSION is useless for in-kernel drivers, so just remove all usage of it in the remaining few input drivers that still used it (input-polldev and sparse-keymap). Cc: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman --- drivers/input/input-polldev.c | 1 - drivers/input/sparse-keymap.c |

[PATCH 4/6] Input: touchscreen: remove unneeded MODULE_VERSION() usage

MODULE_VERSION is useless for in-kernel drivers, so just remove all usage of it in the touchscreen drivers. Along with this, some DRV_VERSION macros were removed as they are also pointless. Cc: Dmitry Torokhov Cc: Sangwon Jee Signed-off-by: Greg Kroah-Hartman --- drivers/input/touchscreen/col

[PATCH 5/6] Input: misc: remove unneeded MODULE_VERSION() usage

MODULE_VERSION is useless for in-kernel drivers, so just remove all usage of it in the misc input drivers. Along with this, some DRIVER_VERSION macros were removed as they are also pointless. Cc: Dmitry Torokhov Cc: Ville Syrjala Signed-off-by: Greg Kroah-Hartman --- drivers/input/misc/apanel

[PATCH] i2c: i2c-boardinfo: fix memory leaks on devinfo

From: Colin Ian King Currently when an error occurs devinfo is still allocated but is unused when the error exit paths break out of the for-loop. Fix this by kfree'ing devinfo to avoid the leak. Detected by CoverityScan, CID#1416590 ("Resource Leak") Fixes: 4124c4eba402 ("i2c: allow attaching I

Re: FW: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

Apologies for the slow response. I didn't get switched over from tpmdd-devel to linux-integrity till just now. > On 11/21/2017 01:30 PM, Jarkko Sakkinen wrote: >> On Tue, Nov 21, 2017 at 10:07:34AM +0100, Javier Martinez Canillas >> wrote: >>> As mentioned, I think this should be documented. I gue

Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license

On Wed, Nov 22, 2017 at 06:07:13PM +0100, Pavel Machek wrote: > Lets look at random file in usb: > > // SPDX-License-Identifier: GPL-2.0+ > /* > * Driver for SMSC USB3503 USB 2.0 hub controller driver > * > * Copyright (c) 2012-2013 Dongjin Kim (tobet...@gmail.com) > */ > ... > MODULE_LICENSE(

Re: Does CONFIG_HARDENED_USERCOPY break /dev/mem?

On Wed, Nov 22, 2017 at 9:43 AM, Kees Cook wrote: > On Wed, Nov 22, 2017 at 1:28 AM, Michael Holzheu > wrote: >> So what's your plan now? How will you fix this issue? > > I think the best plan here would be to use the Kconfig "imply > STRICT_DEVMEM" in HARDENED_USERCOPY. That would make STRICT_DE

[PATCH 0/3] trace-cmd: fixing three minor user experience issues

This short patch series fixes three minor user experience issues in trace-cmd: - an error message (when record is used without -e and -p) - the documentation of trace record (plugins vs tracers terminology) - the command 'stat' to report when the stack tracer is enabled The

[PATCH 1/3] trace-cmd: Fix err msg for record w/o the -e option

Currently, running just `trace-cmd record` without telling which events have to be traced (-e) nor which tracer to use (-p), trace-cmd dies with the message: No instances reference?? Which might not be helpful to new users of the tool. This small patch removes an early check in trace_record

[PATCH 3/3] trace-cmd: Making stat to report when the stack tracer is ON

trace-cmd stat is a handy way for users to see what tracing is currently going on, but currently is does not say anything about the stack tracing. This simple patch makes the command to show a message when the stack tracer is ON. Signed-off-by: Vladislav Valtchev (VMware) --- trace-cmd.h | 3

[PATCH 2/3] trace-cmd: s/plugin/tracer/ in record's man page

Currently, the man page of trace-cmd record states that: To see a list of available plugins, see trace-cmd-list(1). While `trace-cmd list` [w/o options] mentions "tracers", which is the proper term there. The inconsistency exists because the terminology in trace-cmd/ftrace changed over time

Re: [PATCH v3 03/16] phy: qcom-qmp: Power-on PHY before initialization

On 11/21/2017 01:23 AM, Manu Gautam wrote: > PHY must be powered on before turning ON clocks and > attempting to initialize it. Driver is exposing > separate init and power_on routines for this. > Apparently USB dwc3 core driver performs power-on after > init. Also, poweron and init for QMP PHY nee

Re: [RFC PATCH for 4.15 v12 00/22] Restartable sequences and CPU op vector

> > If anyone ever reports that as a problem, I'll gladly fix it in the > > kernel. That's doable without an ABI change. If rseq-like things > > started breaking single-stepping, we can't just fix it in the kernel. AFAIK nobody ever complained about it since we have vsyscalls and vDSOs. > > Ve

Re: Failed IRQ assignment for INT0002 on Braswell

Hi, Hans. With this patch applied the warning is not emitted anymore with threadirqs enabled, and relevant kthread (irq/9-INT0002) is created. Feel free to add Reported-by/Tested-by from me once you do a submission. Thanks. Regards, Oleksandr On středa 22. listopadu 2017 16:50:33 CET Hans d

Re: [dm-devel] new patchset to eliminate DM's use of BIOSET_NEED_RESCUER

On Wed, 22 Nov 2017, NeilBrown wrote: > On Tue, Nov 21 2017, Mikulas Patocka wrote: > > > On Tue, 21 Nov 2017, Mike Snitzer wrote: > > > >> On Tue, Nov 21 2017 at 4:23pm -0500, > >> Mikulas Patocka wrote: > >> > >> > This is not correct: > >> > > >> >2206 static void dm_wq_work(struct w

Re: [bisected] system hang after boot

Hi Sebastian, Thanks for the report. On Wed, Nov 22, 2017 at 06:46:01PM +0100, Sebastian Ott wrote: > One of my test systems (s390) hangs after boot. One of the cpus is idle > the other is in arch_spin_relax. Bisect pointed to this one: > > a8a217c22116eff6c120d753c9934089fb229af0 is the first b

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

+ Johannes On 22-11-17 18:43, Florian Fainelli wrote: Hi, (sorry for the cross post) I am at v4.14-12995-g0c86a6bd85ff and just met the following, attached is my .config file. Is this a known problem? Thanks! [1.798714] cfg80211: Loading compiled-in X.509 certificates for regulatory datab

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

On Wed, 2017-11-22 at 19:29 +0100, Arend van Spriel wrote: > + Johannes > > >>> BUG_ON(!sig->digest); > BUG_ON(!sig->s); I *think* this is the same bug that was reported before, then this should fix it: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=d7be10

Re: new patchset to eliminate DM's use of BIOSET_NEED_RESCUER

On Wed, Nov 22 2017 at 1:24pm -0500, Mikulas Patocka wrote: > Another problem is this: > > struct bio *b = bio_clone_bioset(bio, GFP_NOIO, md->queue->bio_split); > bio_advance(b, (bio_sectors(b) - ci.sector_count) << 9); > bio_chain(b, bio); > > What if it blocks because the bioset is exhaust

Re: [PATCH 4.14 00/31] 4.14.1-stable review

On Wed, Nov 22, 2017 at 06:00:23PM +0100, Greg Kroah-Hartman wrote: > On Wed, Nov 22, 2017 at 04:06:42PM +, Ben Hutchings wrote: > > On Tue, 2017-11-21 at 11:38 -0800, Guenter Roeck wrote: > > > On Tue, Nov 21, 2017 at 07:07:14PM +, Ben Hutchings wrote: > > > > On Tue, 2017-11-21 at 18:09 +

[PATCH v2] mm/cma: fix alloc_contig_range ret code/potential leak

If the call __alloc_contig_migrate_range() in alloc_contig_range returns -EBUSY, processing continues so that test_pages_isolated() is called where there is a tracepoint to identify the busy pages. However, it is possible for busy pages to become available between the calls to these two routines.

Re: [PATCH] NTB: switchtec_ntb: fix spelling mistake: "peforming" -> "performing"

On 21/11/17 08:13 PM, Joe Perches wrote: probably nicer to add the missing newlines too. Oh, my mistake. I was never sure what was correct so I think I've been pretty lax about that. I'll clean that up. Seems like something that should be added to checkpatch. I may attempt a patch for th

Re: [bisected] system hang after boot

Hello Will, On Wed, 22 Nov 2017, Will Deacon wrote: > Now, I can't see what the break_lock is doing here other than causing > problems. Is there a good reason for it, or can you just try removing it > altogether? Patch below. With your patch applied the system is able to boot again. I did some qu

Re: [Fwd: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware]

+ a few folks who might care + lkml. On Mon, Nov 20, 2017 at 06:24:28PM -0500, Mimi Zohar wrote: > Hi Matthew, David, Luis, > > After Linus' comments I'm just not sure if it makes sense to re-post > the patch.  To address Linus' comments, I could update the patch > description as follows: > >

"git reset --hard" on riscv for-linux-next branch

Is it OK to rewrite history on my for-linux-next branch? Since we got upstream I've started getting patches from various people and as a result I now have a bunch of branches with independent commits on them. In an ideal world I'd like to do something like git checkout for-linux-next git

Re: [patches] RE: [PATCH 3/4] RISC-V: Flush I$ when making a dirty page executable

On Wed, Nov 22, 2017 at 9:38 AM, Palmer Dabbelt wrote: > On Tue, 21 Nov 2017 08:57:07 PST (-0800), david.lai...@aculab.com wrote: >> >> From: Palmer Dabbelt >>> >>> Sent: 20 November 2017 18:58 >>> >>> The RISC-V ISA allows for instruction caches that are not coherent WRT >>> stores, even on a sin

Re: [PATCH v2 07/18] x86/asm: Fix assumptions that the HW TSS is at the beginning of cpu_tss

On Tue, Nov 21, 2017 at 08:44:02PM -0800, Andy Lutomirski wrote: > I'm going to move SYSENTER_stack to the beginning of cpu_tss to help > detect overflow. Before this can happen, I need to fix several code > paths that hardcode assumptions about the old layout. Please formulate that commit messag

Re: [bisected] system hang after boot

Hi Sebastian, On Wed, Nov 22, 2017 at 07:54:54PM +0100, Sebastian Ott wrote: > On Wed, 22 Nov 2017, Will Deacon wrote: > > Now, I can't see what the break_lock is doing here other than causing > > problems. Is there a good reason for it, or can you just try removing it > > altogether? Patch below.

Re: hugetlb page migration vs. overcommit

On 11/22/2017 07:28 AM, Michal Hocko wrote: > Hi, > is there any reason why we enforce the overcommit limit during hugetlb > pages migration? It's in alloc_huge_page_node->__alloc_buddy_huge_page > path. I am wondering whether this is really an intentional behavior. I do not think it was intention

[PATCH 1/2] ALSA: pcm: add SNDRV_PCM_FORMAT_{S,U}20_4

This format is similar to existing SNDRV_PCM_FORMAT_{S,U}20_3 that keep 20-bit PCM samples in 3 bytes, however i.MX6 platform SSI FIFO does not allow 3-byte accesses (including DMA) so a 4-byte format is needed for it. Signed-off-by: Maciej S. Szmigiero --- include/sound/pcm.h | 8 +

[PATCH 2/2] ASoC: fsl_ssi: add 20-bit sample format for AC'97 and use it for capture

When testing AC'97 capture on UDOO board (currently the only user of fsl_ssi driver in the AC'97 mode) it become obvious that there is a massive distortion above certain, small input signal. This problem has been traced to silicon errata ERR003778: "In AC97, 16-bit mode, received data is shifted b

Re: [PATCH] NTB: switchtec_ntb: fix spelling mistake: "peforming" -> "performing"

On Wed, 2017-11-22 at 11:53 -0700, Logan Gunthorpe wrote: > > On 21/11/17 08:13 PM, Joe Perches wrote: > > probably nicer to add the missing newlines too. > > Oh, my mistake. > > I was never sure what was correct so I think I've been pretty lax about > that. I'll clean that up. > > Seems like

Re: [PATCH] perf tool powerpc: Add Power9 DD2.1 PVR

Em Wed, Nov 22, 2017 at 09:38:50PM +0530, Ravi Bangoria escreveu: > From: Madhavan Srinivasan > > This will enable parsing JSON files on Power9 DD2.1. Ravi, Can you take a look at this patch posted today by Will Cohen: Subject: [PATCH] Use more flexible pattern matching for CPU ident

Re: FW: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

Hello Philip, On 11/22/2017 06:16 PM, flihp wrote: > Apologies for the slow response. I didn't get switched over from > tpmdd-devel to linux-integrity till just now. > No worries, thanks a lot for your feedback. >> On 11/21/2017 01:30 PM, Jarkko Sakkinen wrote: >>> On Tue, Nov 21, 2017 at 10:07

[PATCH v2 5/6] iommu/vt-d: Add debugfs extension to show Pasid table contents

From: Gayatri Kammela Debugfs extension to dump the internals such as pasid table entries for each IOMMU to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/intel_iommu_ctx IOMMU dmar0: Extended Root Table Addr:4310c4800 Extended Root tbl e

[PATCH v2 2/6] iommu/vt-d: Add Intel IOMMU debugfs to show context internals

From: Gayatri Kammela IOMMU internals states such as root and context can be exported to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/intel_iommu_ctx IOMMU dmar2:Root Table Addr:4558a3000 Root tbl entries: Bus 0 L: 4558aa001 H: 0

[PATCH v2 0/6] Intel IOMMU debugfs support

Hi all, This series aims to add debugfs support for Intel IOMMU. It exposes IOMMU registers, internal context and dumps individual table entries to help debug Intel IOMMUs. The first patch does the ground work for the following patches by creating a new Kconfig option - INTEL_IOMMU_DEBUG. It also

[PATCH v2 6/6] iommu/vt-d: Add debugfs support for Intel IOMMU Interrupt remapping

Debugfs extension for Intel IOMMU to dump Interrupt remapping table entries for Interrupt remapping and Interrupt posting. The file /sys/kernel/debug/intel_iommu/intel_iommu_interrupt_remap provides detailed information, such as Index, Source Id, Destination Id, Vector and the raw values for entri

[PATCH v2 4/6] iommu/vt-d: Add debugfs extension to show register contents

From: Gayatri Kammela Debugfs extension to dump all the register contents for each IOMMU device to the user space via debugfs. example: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/intel_iommu_regset DMAR: dmar1: reg_base_addr fed9 Name Offset Contents VER 0x00

[PATCH v2 1/6] iommu/vt-d: Add debugfs support for Intel IOMMU internals

From: Gayatri Kammela Enable Intel IOMMU debug to export Intel IOMMU internals in debugfs Cc: Sohil Mehta Cc: Fenghua Yu Cc: Ashok Raj Signed-off-by: Jacob Pan Signed-off-by: Gayatri Kammela --- v2: No change drivers/iommu/Kconfig | 10 ++ drivers/iommu/intel-iommu.c | 31 +

[PATCH v2 3/6] iommu/vt-d: Add Intel IOMMU debugfs to show extended context internals

From: Gayatri Kammela Debugfs extension to dump internals such as extended context table entries for each IOMMU to the userspace. root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/intel_iommu_ctx IOMMU dmar1: Extended Root Table Addr:4558a1800 Extended Root tbl entries: Bus 0 L: 4558a6001 H

Re: [PATCH] Use more flexible pattern matching for CPU identification for mapfile.csv

Em Wed, Nov 22, 2017 at 11:08:49AM -0500, William Cohen escreveu: > The powerpc cpuid information includes chip revision information. > Changes between chip revisions are usually minor bug fixes and usually > do not affect the operation of the performance monitoring hardware. > The original mapfile

Re: [PATCH] arch, mm: introduce arch_tlb_gather_mmu_lazy

Hi Michal, On Mon, Nov 20, 2017 at 05:04:22PM +0100, Michal Hocko wrote: > On Mon 20-11-17 14:24:44, Will Deacon wrote: > > On Thu, Nov 16, 2017 at 10:20:42AM +0100, Michal Hocko wrote: > > > On Wed 15-11-17 17:33:32, Will Deacon wrote: > [...] > > > > > diff --git a/arch/arm64/include/asm/tlb.h

Re: [RFC PATCH for 4.15 v12 00/22] Restartable sequences and CPU op vector

On Tue, Nov 21, 2017 at 10:05:08PM +, Mathieu Desnoyers wrote: > Other than that, I have not received any concrete alternative proposal to > properly handle single-stepping. That's not entirely true; amluto did have an alternative in Prague: do full machine level instruction emulation till the

[PATCH v3 0/4] vm: add a syscall to map a process memory into a pipe

From: Yossi Kuperman Hi, This patches introduces new process_vmsplice system call that combines functionality of process_vm_read and vmsplice. It allows to map the memory of another process into a pipe, similarly to what vmsplice does for its own address space. The patch 2/4 ("vm: add a syscal

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Mon, Nov 20, 2017 at 02:50:58PM -0800, Laura Abbott wrote: > On 11/17/2017 10:21 AM, Will Deacon wrote: > >This patch series implements something along the lines of KAISER for arm64: > > Passed some basic tests on Hikey Android and my Mustang box. I'll > leave the Mustang building kernels for a

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Wed, Nov 22, 2017 at 05:19:14PM +0100, Pavel Machek wrote: > > This patch series implements something along the lines of KAISER for arm64: > > > > https://gruss.cc/files/kaiser.pdf > > > > although I wrote this from scratch because the paper has some funny > > assumptions about how the archi

Re: [PATCH 18/18] arm64: Kconfig: Add CONFIG_UNMAP_KERNEL_AT_EL0

Hi Marc, On Wed, Nov 22, 2017 at 04:52:36PM +, Marc Zyngier wrote: > On 17/11/17 18:22, Will Deacon wrote: > > Add a Kconfig entry to control use of the entry trampoline, which allows > > us to unmap the kernel whilst running in userspace and improve the > > robustness of KASLR. > > > > Signe

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Mon, Nov 20, 2017 at 06:20:39PM +, Ard Biesheuvel wrote: > On 20 November 2017 at 18:06, Will Deacon wrote: > > I'll see if I can measure the cost of the current vbar switching to get > > an idea of the potential performance available. > > > > Yeah, makes sense. If the bulk of the performa

Re: [RFC PATCH for 4.15 v12 00/22] Restartable sequences and CPU op vector

On Wed, Nov 22, 2017 at 08:32:19PM +0100, Peter Zijlstra wrote: > On Tue, Nov 21, 2017 at 10:05:08PM +, Mathieu Desnoyers wrote: > > Other than that, I have not received any concrete alternative proposal to > > properly handle single-stepping. > > That's not entirely true; amluto did have an a

[PATCH v3 1/4] fs/splice: introduce pages_to_pipe helper

Signed-off-by: Mike Rapoport --- fs/splice.c | 57 - 1 file changed, 36 insertions(+), 21 deletions(-) diff --git a/fs/splice.c b/fs/splice.c index 39e2dc0..7f1ffc5 100644 --- a/fs/splice.c +++ b/fs/splice.c @@ -1185,6 +1185,36 @@ static lo

[PATCH v3 3/4] x86: wire up the process_vmsplice syscall

From: Andrei Vagin Signed-off-by: Andrei Vagin --- arch/x86/entry/syscalls/syscall_32.tbl | 1 + arch/x86/entry/syscalls/syscall_64.tbl | 2 ++ 2 files changed, 3 insertions(+) diff --git a/arch/x86/entry/syscalls/syscall_32.tbl b/arch/x86/entry/syscalls/syscall_32.tbl index 448ac21..dc64bf5

[PATCH 0/4] staging: lustre: fixed some signedness warns from sparse

Fixed some signedness warnings from sparse on lustre. Stefano Manni (4): staging: lustre: fixed signedness of some socklnd params staging: lustre: fixed signedness of llite staging: lustre: fixed signedness of lov staging: lustre: fixed signedness of obdclass drivers/staging/lustre/lnet/

[PATCH v3 4/4] test: add a test for the process_vmsplice syscall

From: Andrei Vagin This test checks that process_vmsplice() can splice pages from a remote process and returns EFAULT, if process_vmsplice() tries to splice pages by an unaccessiable address. Signed-off-by: Andrei Vagin --- tools/testing/selftests/process_vmsplice/Makefile | 5 + .../proces

[PATCH v3 2/4] vm: add a syscall to map a process memory into a pipe

From: Andrei Vagin It is a hybrid of process_vm_readv() and vmsplice(). vmsplice can map memory from a current address space into a pipe. process_vm_readv can read memory of another process. A new system call can map memory of another process into a pipe. ssize_t process_vmsplice(pid_t pid, in

[PATCH 1/4] staging: lustre: fixed signedness of some socklnd params

sparse warnings: warning: incorrect type in assignment (different signedness) expected int *[addressable] [toplevel] [assigned] ksnd_nscheds got unsigned int static [toplevel] * warning: incorrect type in assignment (different signedness) expected int *[addressable] [toplevel] [assigned] ksnd_zc_re

[PATCH 2/4] staging: lustre: fixed signedness of llite

sparse warnings on dir.c: warning: incorrect type in argument 5 (different signedness) expected unsigned int [usertype] *vallen got int * sparse warnings on llite_lib.c: warning: incorrect type in argument 5 (different signedness) expected unsigned int [usertype] *vallen got int * sparse warnings

[PATCH 4/4] staging: lustre: fixed signedness of obdclass

sparse warning on obd_mount.c: warning: incorrect type in argument 5 (different signedness) expected unsigned int [usertype] *vallen got int * Signed-off-by: Stefano Manni --- drivers/staging/lustre/lustre/obdclass/obd_mount.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/d

[PATCH 3/4] staging: lustre: fixed signedness of lov

sparse warning on lov_obd.c: warning: incorrect type in argument 3 (different signedness) expected int *res got unsigned int [usertype] *i sparse warning on lov_offset.c: warning: incorrect type in argument 4 (different signedness) expected long long [usertype] * got unsigned long long * Signed-o

[PATCH] USB: usbip: fix spelling mistake: "synchronuously" -> "synchronously"

From: Colin Ian King Trivial fix to spelling mistake in error message text Signed-off-by: Colin Ian King --- drivers/usb/usbip/vhci_rx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/usbip/vhci_rx.c b/drivers/usb/usbip/vhci_rx.c index 90577e8b2282..a9813f1d507

Re: [RFC PATCH for 4.15 v3 15/22] rseq: selftests: Provide self-tests

On Tue, Nov 21, 2017 at 09:18:53AM -0500, Mathieu Desnoyers wrote: > Implements two basic tests of RSEQ functionality, and one more > exhaustive parameterizable test. > > The first, "basic_test" only asserts that RSEQ works moderately > correctly. E.g. that the CPUID pointer works. > > "basic_per

Re: [PATCH v2 0/6] Intel IOMMU debugfs support

Hi Alex you can add for the whole series Reviewed By: Ashok Raj On Wed, Nov 22, 2017 at 11:25:40AM -0800, Mehta, Sohil wrote: > Hi all, > > This series aims to add debugfs support for Intel IOMMU. It exposes IOMMU > registers, internal context and dumps individual table entries to help debug >

Re: [PATCH 3/3] trace-cmd: Making stat to report when the stack tracer is ON

On Wed, 22 Nov 2017 20:02:02 +0200 "Vladislav Valtchev (VMware)" wrote: > trace-cmd stat is a handy way for users to see what tracing is currently going > on, but currently is does not say anything about the stack tracing. This > simple > patch makes the command to show a message when the stack

[PATCH 4/5] crypto: x86/chacha20 - Remove cra_alignmask

From: Eric Biggers Now that the generic ChaCha20 implementation no longer needs a cra_alignmask, the x86 one doesn't either -- given that the x86 implementation doesn't need the alignment itself. Signed-off-by: Eric Biggers --- arch/x86/crypto/chacha20_glue.c | 1 - 1 file changed, 1 deletion(

[PATCH 1/5] crypto: chacha20 - Fix unaligned access when loading constants

From: Eric Biggers The four 32-bit constants for the initial state of ChaCha20 were loaded from a char array which is not guaranteed to have the needed alignment. Fix it by just assigning the constants directly instead. Signed-off-by: Eric Biggers --- crypto/chacha20_generic.c | 10 --

[PATCH 5/5] crypto: chacha20 - Fix keystream alignment for chacha20_block()

From: Eric Biggers When chacha20_block() outputs the keystream block, it uses 'u32' stores directly. However, the callers (crypto/chacha20_generic.c and drivers/char/random.c) declare the keystream buffer as a 'u8' array, which is not guaranteed to have the needed alignment. Fix it by having bo

[PATCH 0/5] crypto: chacha20 - Alignment fixes

From: Eric Biggers This series fixes potentially unaligned memory accesses when loading the initial state, key, and IV for ChaCha20, and when outputting each keystream block. It also removes the cra_alignmask from the generic and x86 ChaCha20 implementations, once it is no longer needed. Eric B

[PATCH 3/5] crypto: chacha20 - Remove cra_alignmask

From: Eric Biggers Now that crypto_chacha20_setkey() and crypto_chacha20_init() use the unaligned access macros and crypto_xor() also accepts unaligned buffers, there is no need to have a cra_alignmask set for chacha20-generic. Signed-off-by: Eric Biggers --- crypto/chacha20_generic.c | 1 - 1

[PATCH 2/5] crypto: chacha20 - Use unaligned access macros when loading key and IV

From: Eric Biggers The generic ChaCha20 implementation has a cra_alignmask of 3, which ensures that the key passed into crypto_chacha20_setkey() and the IV passed into crypto_chacha20_init() are 4-byte aligned. However, these functions are also called from the ARM and ARM64 implementations of Ch

[PATCH 0/2] ASoC: cs35l32: Adjustments for cs35l32_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 20:49:45 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete two error messages for a failed memory allocation Improve two size determinations sound/soc/codecs/cs35l32.c | 18 ++---

RE: [PATCH v4 1/2] tpm: Keep CLKRUN enabled throughout the duration of transmit_cmd()

I found an issue with this patch. In tpm_transmit() function after clk_enable is called with false, the assumption was whenever the next TPM transaction happens, the clock will be stopped in tpm_platform_end_xfer(). But in cases where after tpm_transmit is completed and there is no TPM transac

[PATCH 1/2] ASoC: cs35l32: Delete two error messages for a failed memory allocation in cs35l32_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 20:35:06 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- sound/soc/codecs/cs35l32.c | 9 +++-- 1 file changed, 3 insertions(+

[PATCH 2/2] ASoC: cs35l32: Improve two size determinations in cs35l32_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 20:40:47 +0100 Replace the specification of two data structures by pointer dereferences 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 d

[PATCH] pinctrl: gemini: Fix usage of 3512 groups

The pin config lookup function was still hardcoding the 3516 pin set, which is obviously wrong. Use the pointer in the state container. Signed-off-by: Linus Walleij --- drivers/pinctrl/pinctrl-gemini.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-ge

Re: FW: [RFC PATCH] tpm: don't return -EINVAL if TPM command validation fails

On Wed, Nov 22, 2017 at 09:16:25AM -0800, flihp wrote: > We can work around quirks in the kernel RM in user space if we must > (short term?) but I'm hesitant to do so in this case. Would feel better > about a short term work-around knowing it's only going to be short term. Pedantically, the kerne

[GIT PULL] ARC updates for 4.15-rc1

Hi Linus, Please pull ARC updates for 4.15-rc1: nothing too fancy here ! And in the spirit of Thanks giving, thank you for creating this amazing project (and giving a whole new connotation to the term "hacker"). God knows what we all would have been doing if Linux was not around to play with.

Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)

On Wed, 22 Nov 2017, Jesper Nilsson wrote: > On Mon, Nov 20, 2017 at 10:50:46PM -0500, Nicolas Pitre wrote: > > On Mon, 20 Nov 2017, Guenter Roeck wrote: > > > On Mon, Nov 20, 2017 at 07:28:21PM -0500, Nicolas Pitre wrote: > > > > On Mon, 20 Nov 2017, Guenter Roeck wrote: > > > > > > > > > bdata-

Re: kernel CI: printk loglevels in kernel boot logs?

On Wed, Nov 22, 2017 at 4:38 AM, Sergey Senozhatsky wrote: > On (11/22/17 12:34), Petr Mladek wrote: > [..] >> > > > This is espeically useful when ingesting kernel logs into advanced >> > > > search/analytics frameworks (I'm playing with and ELK stack: Elastic >> > > > Search, Logstash, Kibana).

Re: [bisected] system hang after boot

On Wed, Nov 22, 2017 at 06:26:59PM +, Will Deacon wrote: > Now, I can't see what the break_lock is doing here other than causing > problems. Is there a good reason for it, or can you just try removing it > altogether? Patch below. The main use is spin_is_contended(), which in turn ends up use

Re: [PATCH 1/5] crypto: chacha20 - Fix unaligned access when loading constants

On 22 November 2017 at 19:51, Eric Biggers wrote: > From: Eric Biggers > > The four 32-bit constants for the initial state of ChaCha20 were loaded > from a char array which is not guaranteed to have the needed alignment. > > Fix it by just assigning the constants directly instead. > > Signed-off-

Re: [PATCH 2/5] crypto: chacha20 - Use unaligned access macros when loading key and IV

On 22 November 2017 at 19:51, Eric Biggers wrote: > From: Eric Biggers > > The generic ChaCha20 implementation has a cra_alignmask of 3, which > ensures that the key passed into crypto_chacha20_setkey() and the IV > passed into crypto_chacha20_init() are 4-byte aligned. However, these > function

[PATCH 1/2] power: supply: ab8500_charger: Fix an error handling path

'ret' is know to be 0 at this point, because it has not been updated by the the previous call to 'abx500_mask_and_set_register_interruptible()'. Fix it by updating 'ret' before checking if an error occurred. Fixes: 84edbeeab67c ("ab8500-charger: AB8500 charger driver") Signed-off-by: Christophe J

[PATCH 0/2] ASoC: cs35l34: Adjustments for cs35l34_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 21:23:45 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete two error messages for a failed memory allocation Improve two size determinations sound/soc/codecs/cs35l34.c | 19 ++---

[PATCH 1/2] ASoC: cs35l34: Delete two error messages for a failed memory allocation in cs35l34_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 21:13:29 +0100 Omit extra messages for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- sound/soc/codecs/cs35l34.c | 10 +++--- 1 file changed, 3 insertions

Re: [PATCH 3/5] crypto: chacha20 - Remove cra_alignmask

On 22 November 2017 at 19:51, Eric Biggers wrote: > From: Eric Biggers > > Now that crypto_chacha20_setkey() and crypto_chacha20_init() use the > unaligned access macros and crypto_xor() also accepts unaligned buffers, > there is no need to have a cra_alignmask set for chacha20-generic. > > Signe

Re: [PATCH 4/5] crypto: x86/chacha20 - Remove cra_alignmask

On 22 November 2017 at 19:51, Eric Biggers wrote: > From: Eric Biggers > > Now that the generic ChaCha20 implementation no longer needs a > cra_alignmask, the x86 one doesn't either -- given that the x86 > implementation doesn't need the alignment itself. > > Signed-off-by: Eric Biggers Acked-b

[PATCH 2/2] ASoC: cs35l34: Improve two size determinations in cs35l34_i2c_probe()

From: Markus Elfring Date: Wed, 22 Nov 2017 21:17:42 +0100 Replace the specification of two data structures by pointer dereferences 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 d

[PATCH 2/2] power: supply: ab8500_charger: Bail out in case of error in 'ab8500_charger_init_hw_registers()'

If an error occurs when we enable the backup battery charging, we should go through the error handling path directly. Before commit db43e6c473b5 ("ab8500-bm: Add usb power path support") this was the case, but this commit has added some code between the last test and the 'out' label. So, in case o

[PATCH v2 2/2] ARM: dts: TS-7970: add basic device tree

These device trees add support for TS-7970 by Technologic Systems. More details here: https://wiki.embeddedarm.com/wiki/TS-7970 Signed-off-by: Sebastien Bourdelin --- Changes v1 -> v2: - rebase on master - remove spidev devices (suggested by Fabio Estevam) - remove inexistant sata node

[PATCH v2 1/2] of: documentation: add bindings documentation for TS-7970

This adds the documentation for the TS-7970 by Technologic Systems. Signed-off-by: Sebastien Bourdelin --- Changes v1 -> v2: - rebase on master --- Documentation/devicetree/bindings/arm/technologic.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/devicetree/bindings/

Re: [RFC PATCH] kvm: arm64: handle single-step of hyp emulated mmio instructions

On Wed, Nov 22, 2017 at 05:07:46PM +, Alex Bennée wrote: > There is a fast-path of MMIO emulation inside hyp mode. The handling > of single-step is broadly the same as kvm_arm_handle_step_debug() > except we just setup ESR/HSR so handle_exit() does the correct thing > as we exit. > > For the c

Re: [PATCH v3 0/4] vm: add a syscall to map a process memory into a pipe

Hi Mike, On 22 November 2017 at 20:36, Mike Rapoport wrote: > From: Yossi Kuperman > > Hi, > > This patches introduces new process_vmsplice system call that combines > functionality of process_vm_read and vmsplice. > > It allows to map the memory of another process into a pipe, similarly to > wh

Re: [PATCH v3 3/3] DT: leds: Add Qualcomm Light Pulse Generator binding

On 11/20/2017 10:45 PM, Bjorn Andersson wrote: > On Mon 20 Nov 12:35 PST 2017, Jacek Anaszewski wrote: > >> On 11/20/2017 08:58 PM, Bjorn Andersson wrote: >>> On Sun 19 Nov 13:35 PST 2017, Jacek Anaszewski wrote: >>> Hi Bjorn, Thanks for the update. On 11/15/2017 08:13 AM,

x86/insn-eval: negative return value?

Hi, While doing some Clang test builds, this was reported: arch/x86/lib/insn-eval.c:780:10: warning: implicit conversion from 'int' to 'char' changes value from 132 to -124 [-Wconstant-conversion] return INSN_CODE_SEG_PARAMS(4, 8); ~~ ^~

Re: [PATCH] VMCI: Use memdup_user() as a cleanup

I am agree, I will change it. On Wed, Nov 22, 2017 at 4:55 PM, Joe Perches wrote: > On Wed, 2017-11-22 at 16:29 +0100, Vasyl Gomonovych wrote: >> Fix coccicheck warning which recommends to use memdup_user(): >> drivers/misc/vmw_vmci/vmci_host.c:757:11-18: WARNING opportunity for >> memdup_user >

Re: [PATCH 08/13] x86/paravirt: Clean up paravirt_types.h

On Wed, Oct 04, 2017 at 10:58:29AM -0500, Josh Poimboeuf wrote: > Make paravirt_types.h more understandable: > > - Use more consistent and logical naming > - Simplify interfaces > - Put related macros together > - Improve whitespace > > Signed-off-by: Josh Poimboeuf > --- > arch/x86/include/asm

Re: [PATCH v2 2/2] ARM: dts: TS-7970: add basic device tree

On Wed, Nov 22, 2017 at 6:32 PM, Sebastien Bourdelin wrote: > +/dts-v1/; > +#include "imx6q.dtsi" > +#include "imx6qdl-ts7970.dtsi" > + > +/ { > + model = "Technologic Systems i.MX6 Quad TS-7970 (Default Devuice > Tree)"; Typo: Devuice--> Device > + reg_can1_3v3: reg_can1_3v3 { > +

Re: [PATCH 3.16 000/133] 3.16.51-rc1 review

On Wed, 2017-11-22 at 07:00 -0800, Guenter Roeck wrote: > On 11/21/2017 05:58 PM, Ben Hutchings wrote: > > This is the start of the stable review cycle for the 3.16.51 > > release. > > There are 133 patches in this series, which will be posted as > > responses > > to this one. If anyone has any is

Re: [PATCH 5/5] crypto: chacha20 - Fix keystream alignment for chacha20_block()

On 22 November 2017 at 19:51, Eric Biggers wrote: > From: Eric Biggers > > When chacha20_block() outputs the keystream block, it uses 'u32' stores > directly. However, the callers (crypto/chacha20_generic.c and > drivers/char/random.c) declare the keystream buffer as a 'u8' array, > which is not

RE: Beneficiary

Good Day my name is Mrs Alice Walton I have a Present Package for you contact me Via:alicewaltso...@gmail.com

<    1   2   3   4   5   6   7   8   9   10   >