[PATCH V16 04/11] efi: parse ARM processor error

Add support for ARM Common Platform Error Record (CPER). UEFI 2.6 specification adds support for ARM specific processor error information to be reported as part of the CPER records. This provides more detail on for processor error logs. Signed-off-by: Tyler Baicar CC: Jonathan (Zhixiong) Zhang R

[PATCH V16 11/11] arm/arm64: KVM: add guest SEA support

Currently external aborts are unsupported by the guest abort handling. Add handling for SEAs so that the host kernel reports SEAs which occur in the guest kernel. When an SEA occurs in the guest kernel, the guest exits and is routed to kvm_handle_guest_abort(). Prior to this patch, a print message

[PATCH V16 09/11] ras: acpi / apei: generate trace event for unrecognized CPER section

The UEFI spec includes non-standard section type support in the Common Platform Error Record. This is defined in section N.2.3 of UEFI version 2.5. Currently if the CPER section's type (UUID) does not match any section type that the kernel knows how to parse, a trace event is not generated. Gener

[GIT PULL] (xen) stable/for-jens-4.12

Hey Jens, Could you kindly pull: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.12 which has one tiny fix: Thanks! Gustavo A. R. Silva (1): block: xen-blkback: add null check to avoid null pointer dereference drivers/block/xen-blkback/xenbus.c | 8

[PATCH V16 10/11] trace, ras: add ARM processor error trace event

Currently there are trace events for the various RAS errors with the exception of ARM processor type errors. Add a new trace event for such errors so that the user will know when they occur. These trace events are consistent with the ARM processor error section type defined in UEFI 2.6 spec section

[PATCH V16 07/11] acpi: apei: panic OS with fatal error status block

From: "Jonathan (Zhixiong) Zhang" Even if an error status block's severity is fatal, the kernel does not honor the severity level and panic. With the firmware first model, the platform could inform the OS about a fatal hardware error through the non-NMI GHES notification type. The OS should pani

[PATCH V16 05/11] arm64: exception: handle Synchronous External Abort

SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code. When SEA occurs, before killing the process, report the error in the kernel logs. Update fault_info[] with spec

[PATCH V16 02/11] ras: acpi/apei: cper: add support for generic data v3 structure

The ACPI 6.1 spec adds a new revision of the generic error data entry structure. Add support to handle the new structure as well as properly verify and iterate through the generic data entries. Signed-off-by: Tyler Baicar CC: Jonathan (Zhixiong) Zhang --- drivers/acpi/apei/ghes.c| 11 +-

Re: linux-next: stats (Was: Linux 4.12-rc1)

Hi Sebastian, On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote: > > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote: > > There are also 288 commits in next-20170502 that didn't make it into > > v4.12-rc1. > > > > [...] > > > > Top ten commiters: > > > > 66 s...@c

[PATCH] libertas: Remove function entry/exit debugging

In at least one place, the enter/exit debugging was not being correctly matched. Based on mailing list feedback, it was desired to drop all of these in favor of using ftrace instead. Suggested-by: Joe Perches Suggested-by: Kalle Valo Signed-off-by: Kees Cook --- drivers/net/wireless/marvell/li

Re: [GIT PULL] (xen) stable/for-jens-4.12

On 05/15/2017 03:28 PM, Konrad Rzeszutek Wilk wrote: > Hey Jens, > > Could you kindly pull: > > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git > stable/for-jens-4.12 > > which has one tiny fix: > > Thanks! > > Gustavo A. R. Silva (1): > block: xen-blkback: add null check

[PATCH] ARM: davinci_all_defconfig: enable LEGO MINDSTORMS EV3 battery module

This enables the power supply module for the LEGO MINDSTORMS EV3 battery. Signed-off-by: David Lechner --- Goes along with https://patchwork.kernel.org/patch/9676087/ (which I don't see in linux-davinci yet). arch/arm/configs/davinci_all_defconfig | 1 + 1 file changed, 1 insertion(+) diff --

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

Hi Eric, Thank you for the patch. On Thursday 11 May 2017 16:56:23 Eric Anholt wrote: > The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with > DSI->DPI bridge and touchscreen controller integrated, that connects > to the Raspberry Pi through its 15-pin "DSI" connector (some lines are >

Re: kmemleak splat on copy_process()

l/debug/kmemleak > > echo scan > /sys/kernel/debug/kmemleak > > cat /sys/kernel/debug/kmemleak > > Worked fine for me. Maybe your config is special? I don't think my config is special at all, here it is its just what I use for my qemu kvm guest image: http://drvbp1.linux-fou

[PATCH v2 0/7] staging: sm750fb: cleaning code

Folowing patch set cleans some warnings and checkups from checkpatch.pl and also fix code to better fot linux code style. Changes since v1 [1]: * staging: sm750fb: fix length of lines, function calls and declaration * created better description * squashed: staging: sm750fb: unif

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

Hi Rob, On Monday 15 May 2017 15:44:57 Rob Herring wrote: > On Thu, May 11, 2017 at 04:56:23PM -0700, Eric Anholt wrote: > > The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with > > DSI->DPI bridge and touchscreen controller integrated, that connects > > to the Raspberry Pi through its

[PATCH v2 6/7] staging: sm750fb: Remove typedef from "typedef enum _DPMS_t"

This patch removes typedefs from enum and renames it from "typedef enum _DPMS_t" to "enum DPMS" as per kernel coding standards. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_power.c | 2 +- drivers/staging/sm750fb/ddk750_power.h | 7 +++ 2 files changed, 4 insertions(+), 5 d

[PATCH v2 4/7] staging: sm750fb: Remove typedef from "typedef enum _clock_type_t"

This patch removes typedefs from enum and renames it from "typedef enum _clock_type_t" to "enum clock_type" as per kernel coding standards. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_chip.h | 8 drivers/staging/sm750fb/ddk750_mode.c | 2 +- drivers/staging/sm750fb/dd

[PATCH v2 7/7] staging: sm750fb: Remove typedef from "typedef enum _sii164_hot_plug_mode_t"

This patch removes typedefs from enum and renames it from "typedef enum _sii164_hot_plug_mode_t" to "enum sii164_hot_plug_mode" as per kernel coding standards. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_sii164.c | 2 +- drivers/staging/sm750fb/ddk750_sii164.h | 4 ++-- 2 file

[PATCH v2 3/7] staging: sm750fb: Remove typedef from "typedef enum _logical_chip_type_t"

This patch removes typedefs from enum and renames it from "typedef enum _logical_chip_type_t" to "enum logical_chip_type" as per kernel coding standards. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_chip.c | 2 +- drivers/staging/sm750fb/ddk750_chip.h | 8 2 files chan

[PATCH v2 2/7] staging: sm750fb: unifying macro usage and definitions

This patch adds tabs into macro definitions so all rhs are on same column. Removing MHz macro from ddk_chip.c file and reuse MHZ from sm750.h. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_chip.c| 18 drivers/staging/sm750fb/ddk750_display.h | 78 ---

[PATCH v2 5/7] staging: sm750fb: Remove typedef from "typedef enum _disp_output_t"

This patch removes typedefs from enum and renames it from "typedef enum _disp_output_t" to "enum disp_output" as per kernel coding standards. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_display.c | 2 +- drivers/staging/sm750fb/ddk750_display.h | 8 drivers/staging/sm

[PATCH v2 1/7] staging: sm750fb: fix length of lines, function calls and declaration

This patch breaks lines that are longer than 80 characters and joins together those, that are too short and can be placed at one. Function calls and declarations are updated to fit kernel code style. Signed-off-by: Matej Dujava --- drivers/staging/sm750fb/ddk750_chip.c | 7 +++-- drivers/sta

[PATCH 2/2] gpu: drm: i915: compress logic into one line

Simplify logic to avoid unnecessary variable declaration and assignment. Signed-off-by: Gustavo A. R. Silva --- drivers/gpu/drm/i915/intel_display.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c

next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

For a few kernel releases now I have managed to trigger the warning added via commit e1a58320a38dfa ("x86/mm: Warn on W^X mappings", merged upstream since v4.4) on my KVM qemu x86_64 system. Since I just booted into the shiny new linux-next tag next-20170515 (based on v4.12-rc1) and thi

Re: [PATCHv2] watchdog: core: add option to avoid early handling of watchdog

On Sun, May 14 2017, Guenter Roeck wrote: > On 05/12/2017 05:05 AM, Sebastian Reichel wrote: >> On some systems its desirable to have watchdog reboot the system >> when it does not come up fast enough. This adds a kernel parameter >> to disable the auto-update of watchdog before userspace takes ov

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

On Tue, May 16, 2017 at 12:06:50AM +0200, Luis R. Rodriguez wrote: > Using QEMU emulator version 2.7.94 (v2.8.0-rc4-dirty) > > I will try updating my distro package for qemu and see if perhaps its this > and for the other odd fork issue I reported [0]. > > [0] > https://lkml.kernel.org/r/CAB=NE6

Re: [PATCH 1/3] ipc/sem.c: remove sem_base, embed struct sem

On Mon, May 15, 2017 at 1:08 PM, Andrew Morton wrote: > On Mon, 15 May 2017 19:19:10 +0200 Manfred Spraul > wrote: > >> sma->sem_base is initialized with >> sma->sem_base = (struct sem *) &sma[1]; >> >> The current code has four problems: >> - There is an unnecessary pointer dereference -

[RESEND][PATCH v4] arm64: dts: hi6220: Add k3-dma and i2s/hdmi audio support

Add entry for k3-dma driver and i2s/hdmi audio devices. This enables HDMI audio output. Cc: Zhangfei Gao Cc: Liam Girdwood Cc: Mark Brown Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Wei Xu Cc: Rob Herring Cc: Andy Green Cc: Dave Long Cc: Guodong Xu Cc: Antonio Borneo Signed-off-by: John S

Re: [PATCH v4 1/4] of: remove *phandle properties from expanded device tree

On Mon, May 1, 2017 at 9:46 PM, wrote: > From: Frank Rowand > > Remove "phandle", "linux,phandle", and "ibm,phandle" properties from > the internal device tree. The phandle will still be in the struct > device_node phandle field. > > This is to resolve the issue found by Stephen Boyd [1] when h

Re: [PATCH 3/3] pinctrl: cherryview: Extend the Chromebook DMI quirk to Intel_Strago systems

On Mon, May 15, 2017 at 4:14 AM, Andy Shevchenko wrote: > On Mon, 2017-05-15 at 14:01 +0300, Mika Westerberg wrote: >> It turns out there are quite many Chromebooks out there that have the >> same keyboard issue than Acer Chromebook. All of them are based on >> Intel_Strago reference and report th

Re: [PATCH] ARM: dts: Add devicetree for the Raspberry Pi 3, for arm32 (v6)

Hi, On Tue, Apr 25, 2017 at 9:45 AM, Eric Anholt wrote: > Raspbian and Fedora have decided to support the Pi3 in 32-bit mode for > now, so it's useful to be able to test that mode on an upstream > kernel. It's also been useful for me to use the same board for 32-bit > and 64-bit development. > >

[PATCH] net: ethernet: broadcom: bnxt: remove dead code

Local variable _sh_ is assigned to a constant value and it is never updated again. Remove this variable and the dead code it guards. Addresses-Coverity-ID: 1350916 Signed-off-by: Gustavo A. R. Silva --- drivers/net/ethernet/broadcom/bnxt/bnxt.c | 9 +++-- 1 file changed, 3 insertions(+), 6 d

[RFC][PATCHSET] wait4()/waitid() cleanups

This series switches compat wait4() and waitid() variants away from set_fs() use. A couple of helpers (kernel_wait4() and kernel_waitid()) are introduced, copying siginfo/rusage to userland is taken to sys_wait...(). That allows both to simplify the guts of do_wait() machinery and avoid me

Re: [PATCH v4 1/4] firmware: scm: Add support for shared access of a memory

Hi Avaneesh, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc1 next-20170515] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Avaneesh-Kumar-Dwivedi/firmware-scm-Add

[PATCH 2/8] wait4(2)/waitid(2): separate copying rusage to userland

From: Al Viro New helpers: kernel_waitid() and kernel_wait4(). sys_waitid(), sys_wait4() and their compat variants switched to those. Copying struct rusage to userland is left to syscall itself. For compat_sys_wait4() that eliminates the use of set_fs() completely. For compat_sys_waitid() it's

[PATCH 1/8] move compat wait4 and waitid next to native variants

From: Al Viro Signed-off-by: Al Viro --- kernel/compat.c | 66 -- kernel/exit.c | 69 + 2 files changed, 69 insertions(+), 66 deletions(-) diff --git a/kernel/compat.c b/kernel/compat.

[PATCH 5/8] lift getrusage() from wait_noreap_copyout()

From: Al Viro Signed-off-by: Al Viro --- kernel/exit.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/kernel/exit.c b/kernel/exit.c index 9ea7c0d4cb37..3cfb74f7a64e 100644 --- a/kernel/exit.c +++ b/kernel/exit.c @@ -1062,9 +1062,6 @@ static int wait_noreap_cop

[PATCH 3/8] kernel_wait4()/kernel_waitid(): delay copying status to userland

From: Al Viro Signed-off-by: Al Viro --- kernel/exit.c | 20 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/kernel/exit.c b/kernel/exit.c index b3c141a4432f..574e6b04f838 100644 --- a/kernel/exit.c +++ b/kernel/exit.c @@ -1002,7 +1002,7 @@ struct wait_opts {

[PATCH 4/8] waitid(2): leave copyout of siginfo to syscall itself

From: Al Viro have kernel_waitid() collect the information needed for siginfo into a small structure (waitid_info) passed to it; deal with copyout in sys_waitid()/compat_sys_waitid(). Signed-off-by: Al Viro --- kernel/exit.c | 168 ++ 1 f

[PATCH 6/8] kill wait_noreap_copyout()

From: Al Viro folds into callers Signed-off-by: Al Viro --- kernel/exit.c | 65 +++ 1 file changed, 25 insertions(+), 40 deletions(-) diff --git a/kernel/exit.c b/kernel/exit.c index 3cfb74f7a64e..3fcca7e51711 100644 --- a/kernel/exit.c

[PATCH 7/8] wait_task_zombie: consolidate info logics

From: Al Viro Signed-off-by: Al Viro --- kernel/exit.c | 45 - 1 file changed, 16 insertions(+), 29 deletions(-) diff --git a/kernel/exit.c b/kernel/exit.c index 3fcca7e51711..e93876b06b28 100644 --- a/kernel/exit.c +++ b/kernel/exit.c @@ -1074,28 +1

[PATCH 8/8] waitid(): switch copyout of siginfo to unsafe_put_user()

From: Al Viro Signed-off-by: Al Viro --- kernel/exit.c | 40 +--- 1 file changed, 25 insertions(+), 15 deletions(-) diff --git a/kernel/exit.c b/kernel/exit.c index e93876b06b28..a13dd4d0dc34 100644 --- a/kernel/exit.c +++ b/kernel/exit.c @@ -1625,15 +1625,1

[PATCH 1/2] gpu: drm: i915: remove dead code

Local variable has_reduced_clock is assigned to a constant value and it is never updated again. Remove this variable and the dead code it guards. Addresses-Coverity-ID: 1362230 Signed-off-by: Gustavo A. R. Silva --- drivers/gpu/drm/i915/intel_display.c | 9 + 1 file changed, 1 insertion(

RE: [PATCH] scsi: zero per-cmd driver data for each MQ I/O

> -Original Message- > From: Long Li [mailto:lon...@exchange.microsoft.com] > Sent: Wednesday, May 10, 2017 2:07 PM > To: James E.J. Bottomley ; Martin K. Petersen > ; linux-s...@vger.kernel.org; linux- > ker...@vger.kernel.org > Cc: Long Li > Subject: [PATCH] scsi: zero per-cmd driver dat

Re: [PATCH v2 2/2] regulator: Allow for asymmetric settling times

El Sun, May 14, 2017 at 07:16:52PM +0900 Mark Brown ha dit: > On Mon, May 01, 2017 at 11:37:15AM -0700, Matthias Kaehlcke wrote: > > > else if (rdev->constraints->settling_time) > > return rdev->constraints->settling_time; > > + else if (rdev->constraints->settling_time_up && >

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

On Mon, May 15, 2017 at 3:15 PM, Luis R. Rodriguez wrote: > On Tue, May 16, 2017 at 12:06:50AM +0200, Luis R. Rodriguez wrote: >> Using QEMU emulator version 2.7.94 (v2.8.0-rc4-dirty) >> >> I will try updating my distro package for qemu and see if perhaps its this >> and for the other odd fork iss

Re: [Possible Phish Fraud][PATCH] scsi: zero per-cmd driver data for each MQ I/O

On Wed, 2017-05-10 at 14:07 -0700, Long Li wrote: > From: Long Li > > Lower layer driver may not initialize private data before use. Zero them > out to prevent use of stale data. > > Signed-off-by: Long Li > --- > drivers/scsi/scsi_lib.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH v2 0/2] i2c: xgene-slimpro: Add ACPI support

Hi All, Do you have any comments on this patch set? Thanks Hoan On Mon, Apr 24, 2017 at 11:00 AM, Hoan Tran wrote: > This patch set adds ACPI support by using PCC mailbox communication interface. > > v2: > * Alphabeltical order > * Use reinit_completion > * Remove mutex > * Use ENOENT inste

Re: [PATCH 4/8] waitid(2): leave copyout of siginfo to syscall itself

On Mon, May 15, 2017 at 3:37 PM, Al Viro wrote: > > +struct waitid_info { > + pid_t pid; > + uid_t uid; > + int status; > + int why; > +}; Ugh. Could we please just name those with what they are actually used for? Even if you hate the "si_" previx for some reason, I reall

Re: [PATCH v6 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN

On Tue, May 16, 2017 at 6:57 AM, Alan Cox wrote: > O> I'm not implying that my patch is supposed to provide safety for >> "hundreds of other" issues. I'm looking to provide a way to lock down a >> single TTY ioctl that has caused real security issues to arise. For > > In other words you are not ac

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

On Fri, May 12, 2017 at 11:02:26PM +0200, Arend Van Spriel wrote: > try again.. replacing email address from Michał > On 12-5-2017 22:55, Arend Van Spriel wrote: > > Let me explain the idea to refresh your memory (and mine). It started > > when we were working on adding driver support for OpenWrt i

Re: [v3 9/9] s390: teach platforms not to zero struct pages memory

Hello Pasha, > Thank you for looking at this patch. I am worried to make the proposed > change, because, as I understand in this case we allocate memory not for > "struct page"s but for table that hold them. So, we will change the behavior > from the current one, where this table is allocated zero

[PATCH 2/2] arm64: marvell: dts: add second 1G port on the Armada 8040 DB

Armada 8040 DB is equipped with 4 (2x 10G SFI + 2x 1G RGMII) ethernet ports of which only one was hitherto enabled. Because currently mvpp2 driver is capable of supporting only 1G RGMII/SGMII, enable second port from CP slave HW block. Signed-off-by: Marcin Wojtas --- arch/arm64/boot/dts/marvell

[PATCH 1/2] arm64: marvell: dts: fill MachiatoBin board description

This patch adds following improvements to Armada 8040 MachiatoBin: * Add 'chosen' node with stdout-path assignment * Enable 1G sgmii port * Enable SDHCI controllers on AP and CP HW blocks Signed-off-by: Marcin Wojtas --- arch/arm64/boot/dts/marvell/armada-8040-mcbin.dts | 34 +

[PATCH 0/2] Armada 8040 MachiatoBin and DB improvements

Hi, This very short series apply improvements to two Armada 8040 boards, adding missing 'chosen' node for MachiatoBin and some of the interfaces hitherto not present in device trees, but yet supported in the kernel. I'm looking forward to any comments or remarks. Best regards, Marcin Marcin Woj

RE: [PATCH] scsi: zero per-cmd driver data for each MQ I/O

> -Original Message- > From: Long Li > Sent: Monday, May 15, 2017 3:48 PM > To: Long Li ; James E.J. Bottomley > ; Martin K. Petersen > ; linux-s...@vger.kernel.org; linux- > ker...@vger.kernel.org > Cc: KY Srinivasan ; Stephen Hemminger > > Subject: RE: [PATCH] scsi: zero per-cmd driver

Re: Question on fscrypt_d_revalidate() and fstest generic/429

On Mon, May 15, 2017 at 09:51:03PM +0200, Richard Weinberger wrote: > > > > The test is repeatedly creating and removing a directory "dir" while > > lookups are > > being done in it. It seems the problem is that many dentries are being > > created > > for "dir", and they pin many different inod

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Thu, May 11, 2017 at 03:40:28PM +0200, Michał Kępień wrote: > > Perhaps so (overly zealous). Regarding the globals, let's be clear on the > > motivation. We want to follow good sw engineering practice, use data > > encapsulation, etc. However, using an explicit path to an ACPI device to > > avo

Re: [PATCH 1/2] arm64: marvell: dts: fill MachiatoBin board description

On Tue, May 16, 2017 at 01:28:32AM +0200, Marcin Wojtas wrote: > This patch adds following improvements to Armada 8040 > MachiatoBin: > * Add 'chosen' node with stdout-path assignment > * Enable 1G sgmii port > * Enable SDHCI controllers on AP and CP HW blocks > > Signed-off-by: Marcin Wojtas

[PATCH] sparc64: Fix mapping of 64k pages with MAP_FIXED

An incorrect huge page alignment check caused mmap failure for 64K pages when MAP_FIXED is used with address not aligned to HPAGE_SIZE. Orabug: 25885991 Signed-off-by: Nitin Gupta --- arch/sparc/include/asm/hugetlb.h | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/arch

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

On Mon, May 15, 2017 at 3:15 PM, Luis R. Rodriguez wrote: > On Tue, May 16, 2017 at 12:06:50AM +0200, Luis R. Rodriguez wrote: >> Using QEMU emulator version 2.7.94 (v2.8.0-rc4-dirty) >> >> I will try updating my distro package for qemu and see if perhaps its this >> and for the other odd fork iss

Re: [PATCH] ASoC: simple-card: fix mic jack initialization

Hi > Initialize asoc_simple_card_init_mic with the correct struct > asoc_simple_jack. > > Signed-off-by: Stefan Agner > Fixes: 9eac361877b3 ("ASoC: simple-card: add new asoc_simple_jack and use it") > --- Acked-by: Kuninori Morimoto > sound/soc/generic/simple-card.c | 2 +- > 1 file changed

RE: [PATCH] scsi: zero per-cmd driver data for each MQ I/O

> -Original Message- > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com] > Sent: Monday, May 15, 2017 4:03 PM > To: j...@linux.vnet.ibm.com; linux-s...@vger.kernel.org; linux- > ker...@vger.kernel.org; Long Li ; > martin.peter...@oracle.com > Cc: Long Li > Subject: Re: [Possible Ph

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

note_page+0x630/0x7e0 [0.893674] Modules linked in: [0.893972] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc1-next-20170515+ #145 [0.894687] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.10.2-0-g5f4c7b1-prebuilt.qemu-project.org 04/01/2014 [0.895828] task: 8

Re: [PATCH 4/8] waitid(2): leave copyout of siginfo to syscall itself

On Mon, May 15, 2017 at 04:06:49PM -0700, Linus Torvalds wrote: > On Mon, May 15, 2017 at 3:37 PM, Al Viro wrote: > > > > +struct waitid_info { > > + pid_t pid; > > + uid_t uid; > > + int status; > > + int why; > > +}; > > Ugh. Could we please just name those with what the

Re: Question on fscrypt_d_revalidate() and fstest generic/429

On Mon, May 15, 2017 at 09:51:03PM +0200, Richard Weinberger wrote: > > I doubt it's the right solution to make fscrypt_d_revalidate() look at > > ->i_nlink, since ->d_revalidate() is meant to validate the filename, not the > > inode. I think there is probably a VFS bug that is causing the dentri

Re: [PATCH v3 6/6] drm: arc: Use crtc->mode_valid() callback

Hi Daniel, On 15-05-2017 16:52, Daniel Vetter wrote: > On Mon, May 15, 2017 at 10:53:25AM +0200, Daniel Vetter wrote: >> On Thu, May 11, 2017 at 10:06:02AM +0100, Jose Abreu wrote: >>> Now that we have a callback to check if crtc supports a given mode >>> we can use it in arcpgu so that we restri

Re: [PATCH] scsi: zero per-cmd driver data for each MQ I/O

On Mon, 2017-05-15 at 23:32 +, Long Li wrote: > Thanks for looking! Yes this is for chasing a bug. > > With the patch, we also zero the private data used by lower layer driver, in > addition to the private data in scsi_cmnd. Hello Long, What bug did you encounter, with which combination of

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

Hi Michael Apologies for the delayed response - things have been a bit crazy lately. Darren's mail just now has reminded me that you were awaiting feedback. On Thu, May 11, 2017 at 03:40:28PM +0200, Micha?? K??pie?? wrote: > > You could accomplish this by making call_fext_func() not static and c

Re: [PATCH 2/3] ipc: merge ipc_rcu and kern_ipc_perm

On Mon, May 15, 2017 at 10:19 AM, Manfred Spraul wrote: > ipc has two management structures that exist for every id: > - struct kern_ipc_perm, it contains e.g. the permissions. > - struct ipc_rcu, it contains the rcu head for rcu handling and > the refcount. > > The patch merges both structures.

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

Laurent Pinchart writes: > Hi Eric, > > Thank you for the patch. > > On Thursday 11 May 2017 16:56:23 Eric Anholt wrote: >> The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with >> DSI->DPI bridge and touchscreen controller integrated, that connects >> to the Raspberry Pi through its 15

Hang/soft lockup in d_invalidate with simultaneous calls

Hi, I'm seeing behavior in d_invalidate, if multiple threads call d_invalidate on the same tree at the same, behavior time blows up and all the calls hang with large enough trees/enough simultaneous callers. (e.g. a directory w/ 100k entries in d_subdir, and 5 or so threads calling d_invalidate wa

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Mon, May 15, 2017 at 04:27:25PM -0700, Darren Hart wrote: > > In light of the above, I still feel the split is worth going through > > with. The question is whether Jonathan feels the same :) > > In the interest of keeping this moving... As I'm not sure there is a "right > answer" to split or

Re: next-20170515: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0

s > c00e4000/0xc00e4000 > [0.892394] [ cut here ]---- > [0.892834] WARNING: CPU: 0 PID: 1 at > arch/x86/mm/dump_pagetables.c:236 note_page+0x630/0x7e0 > [0.893674] Modules linked in: > [0.893972] CPU: 0 PID: 1 Comm: swapper/0 Not t

Re: [PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

On Mon, May 15, 2017 at 7:03 PM, Eric Anholt wrote: > Laurent Pinchart writes: > >> Hi Eric, >> >> Thank you for the patch. >> >> On Thursday 11 May 2017 16:56:23 Eric Anholt wrote: >>> The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with >>> DSI->DPI bridge and touchscreen controller

Re: [v6 2/3] iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74

DT changes should go to DT list. On Fri, May 12, 2017 at 7:41 AM, Geetha sowjanya wrote: > From: Linu Cherian > > Cavium ThunderX2 SMMU implementation doesn't support page 1 register space > and PAGE0_REGS_ONLY option is enabled as an errata workaround. > This option when turned on, replaces all

[PATCH 0/2] PCI: Workaround for bus reset on Cavium cn8xxx root ports

With the recent improvements in arm64 and vfio-pci, we are seeing failures like this (on cn8890 based systems): [ 235.622361] Unhandled fault: synchronous external abort (0x96000210) at 0xfc00c1000100 [ 235.630625] Internal error: : 96000210 [#1] PREEMPT SMP . . . [ 236.208820] [] pci_gene

[PATCH 2/2] PCI: Avoid bus reset for Cavium cn8xxx root ports.

Root ports of cn8xxx do not function after bus reset when used with some e1000e and LSI HBA devices. Add a quirk to prevent bus reset on these root ports. Signed-off-by: David Daney --- drivers/pci/quirks.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/pci/quirks.c b/drive

[PATCH 1/2] PCI: Allow PCI_DEV_FLAGS_NO_BUS_RESET to be used on bus device.

When checking to see if a PCI bus can safely be reset, we check to see if any of the children have their PCI_DEV_FLAGS_NO_BUS_RESET flag set. As these devices are know not to behave well after a bus reset. Some PCIe root port bridges also do not behave well after a bus reset, sometimes causing the

Re: [PATCH v5 1/2] drm: Add writeback connector type

On Mon, May 15, 2017 at 1:20 PM, Liviu Dudau wrote: > From: Brian Starkey > > Writeback connectors represent writeback engines which can write the > CRTC output to a memory framebuffer. Add a writeback connector type and > related support functions. > > Drivers should initialize a writeback conne

Re: [v3 9/9] s390: teach platforms not to zero struct pages memory

Ah OK, I will include the change. Thank you, Pasha On 05/15/2017 07:17 PM, Heiko Carstens wrote: Hello Pasha, Thank you for looking at this patch. I am worried to make the proposed change, because, as I understand in this case we allocate memory not for "struct page"s but for table that hold

Re: [PATCH] net: ethernet: broadcom: bnxt: remove dead code

On Mon, May 15, 2017 at 3:28 PM, Gustavo A. R. Silva wrote: > Local variable _sh_ is assigned to a constant value and it is never updated > again. Remove this variable and the dead code it guards. > > Addresses-Coverity-ID: 1350916 > Signed-off-by: Gustavo A. R. Silva > --- > drivers/net/etherne

[PATCH] efi/bgrt: skip efi_bgrt_init in case non-efi boot

Sabrina Dubroca reported an early panic below, it was introduced by commit 7b0a911478c7 ("efi/x86: Move the EFI BGRT init code to early init code") The cause is on this machine even for legacy boot firmware still provide the ACPI BGRT table which should be EFI only. Thus the garbage bgrt data caus

Re: [RFC] perf: Add "-f" and "-F" flags to watch a "/sys" style file

Em Mon, May 15, 2017 at 12:27:03PM -0700, Luck, Tony escreveu: > From: Tony Luck > > Thomas Gleixner is encouraging us to extend the /sys/fs/resctrl file system > to include monitoring data (LLC occupancy, memory bandwidth) from the > (weird) counters that come as part of "Resource Director Techn

Re: [PATCH v2] perf report: distinguish between inliners in the same function

On Mon, May 15, 2017 at 12:01:54PM +0200, Milian Wolff wrote: > On Monday, May 15, 2017 3:21:58 AM CEST Namhyung Kim wrote: > > Hi Milian, > > > > On Sun, May 14, 2017 at 08:10:50PM +0200, Milian Wolff wrote: > > > On Freitag, 12. Mai 2017 15:01:29 CEST Namhyung Kim wrote: > > > > On Fri, May 12,

Re: [PATCH v5 2/3] KASLR: Handle memory limit specified by memmap and mem option

Hi Baoquan, At 05/13/2017 01:46 PM, Baoquan He wrote: Option mem= will limit the max address a system can use and any memory region above the limit will be removed. Furthermore, memmap=nn[KMG] which has no offset specified has the same behaviour as mem=. KASLR needs to consider this when choos

Re: [PATCH] x86/efi: Fix kexec kernel panic when efi=old_map is enabled

On 05/15/17 at 02:23pm, Matt Fleming wrote: > (Pulling in Dave, Mr. Kexec on EFI) > > On Mon, 08 May, at 12:25:23PM, Sai Praneeth Prakhya wrote: > > From: Sai Praneeth > > > > Booting kexec kernel with "efi=old_map" in kernel command line hits > > kernel panic as shown below. > > > > [0.001

linux-next: manual merge of the akpm tree with the imx-mxs tree

Hi Andrew, Today's linux-next merge of the akpm tree got a conflict in: drivers/soc/imx/Kconfig between commit: e23c7f7d5783 ("soc: imx: add PM dependency for IMX7_PM_DOMAINS") from the imx-mxs tree and patch: "imx7: fix Kconfig warning and build errors" from the akpm tree. I fixed it

Re: [PATCH v11 11/12] uapi: export all arch specifics directories

On Mon, Mar 27, 2017 at 5:20 AM, Nicolas Dichtel wrote: > This patch removes the need of subdir-y. Now all files/directories under > arch//include/uapi/ are exported. > > The only change for userland is the layout of the command 'make > headers_install_all': directories asm- are replaced by arch-/

CVE-2016-10229 in 4.4.x series

Hi, This is my first post - not currently subscribed so please CC me. :) I searched a bit for this question, but couldn't find an answer (Googled '2016-10229 site:lkml.org'). Does CVE-2016-10229 affect the newest version of the 4.4.x kernel series (currently 4.4.68) and are there any plans to fix

Re: [PATCH 1/2] zram: count same page write as page_stored

On (05/15/17 16:41), Minchan Kim wrote: > Regardless of whether it is same page or not, it's surely write > and stored to zram so we should increase pages_stored stat. > Otherwise, user can see zero value via mm_stats although he > writes a lot of pages to zram. > > Signed-off-by: Minchan Kim Re

Re: [PATCH v5 2/3] KASLR: Handle memory limit specified by memmap and mem option

On 05/16/17 at 08:56am, Dou Liyang wrote: > Hi Baoquan, > > At 05/13/2017 01:46 PM, Baoquan He wrote: > > Option mem= will limit the max address a system can use and any memory > > region above the limit will be removed. > > > > Furthermore, memmap=nn[KMG] which has no offset specified has the sa

Re: [PATCH v11 11/12] uapi: export all arch specifics directories

On Mon, May 15, 2017 at 6:02 PM, Dan Williams wrote: > On Mon, Mar 27, 2017 at 5:20 AM, Nicolas Dichtel > wrote: >> This patch removes the need of subdir-y. Now all files/directories under >> arch//include/uapi/ are exported. >> >> The only change for userland is the layout of the command 'make >

[PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

From: Joonsoo Kim Hello, all. This is an attempt to recude memory consumption of KASAN. Please see following description to get the more information. 1. What is per-page shadow memory This patch introduces infrastructure to support per-page shadow memory. Per-page shadow memory is the same wit

[PATCH v1 02/11] mm/kasan: don't fetch the next shadow value speculartively

From: Joonsoo Kim Fetching the next shadow value speculartively has pros and cons. If shadow bytes are zero, we can exit the check with a single branch. However, it could cause unaligned access. And, if the next shadow value isn't zero, we need to do additional check. Next shadow value can be non

[PATCH v1 03/11] mm/kasan: handle unaligned end address in zero_pte_populate

From: Joonsoo Kim It doesn't handle unaligned end address so last pte could not be initialized. Fix it. Note that this shadow memory can be used by others so map the actual page in this case. Signed-off-by: Joonsoo Kim --- mm/kasan/kasan_init.c | 8 1 file changed, 8 insertions(+) d

[PATCH v1 04/11] mm/kasan: extend kasan_populate_zero_shadow()

From: Joonsoo Kim In the following patch, per-page shadow memory will be introduced and some ranges are checked by per-page shadow and the others are checked by original shadow. To notify the range type, per-page shadow will be mapped by the page that is filled by a special shadow value, KASAN_PE

[PATCH v1 05/11] mm/kasan: introduce per-page shadow memory infrastructure

From: Joonsoo Kim 1. What is per-page shadow memory This patch introduces infrastructure to support per-page shadow memory. Per-page shadow memory is the same with original shadow memory except the granualarity. It's one byte shows the shadow value for the page. The purpose of introducing this n

[PATCH v1 10/11] mm/kasan: support dynamic shadow memory free

From: Joonsoo Kim On-demand alloc/map the shadow memory isn't sufficient to save memory consumption since shadow memory would be populated for all the memory range in the long running system. This patch implements dynamic shadow memory unmap/free to solve this problem. Since shadow memory is pop

<    4   5   6   7   8   9   10   11   >