[PATCH 45/45] arch/sparc: remove duplicate includes

These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Signed-off-by: Pravin Shedge --- arch/sparc/kernel/uprobes.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 45/45] arch/sparc: remove duplicate includes

These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Signed-off-by: Pravin Shedge --- arch/sparc/kernel/uprobes.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/sparc/kernel/uprobes.c

Re: [ANNOUNCE] 4.1.46-rt52

On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: > On 11/29/2017 05:13 PM, Julia Cartwright wrote: > > Hello RT Folks! > > > > I'm pleased to announce the 4.1.46-rt52 stable release. > > > > You can get this release via the git tree at: > > > >

Re: [ANNOUNCE] 4.1.46-rt52

On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: > On 11/29/2017 05:13 PM, Julia Cartwright wrote: > > Hello RT Folks! > > > > I'm pleased to announce the 4.1.46-rt52 stable release. > > > > You can get this release via the git tree at: > > > >

[PATCH] crypto: chacha20poly1305 - validate the digest size

From: Eric Biggers If the rfc7539 template was instantiated with a hash algorithm with digest size larger than 16 bytes (POLY1305_DIGEST_SIZE), then the digest overran the 'tag' buffer in 'struct chachapoly_req_ctx', corrupting the subsequent memory, including 'cryptlen'.

[PATCH] crypto: chacha20poly1305 - validate the digest size

From: Eric Biggers If the rfc7539 template was instantiated with a hash algorithm with digest size larger than 16 bytes (POLY1305_DIGEST_SIZE), then the digest overran the 'tag' buffer in 'struct chachapoly_req_ctx', corrupting the subsequent memory, including 'cryptlen'. This caused a crash

Re: [PATCH net,stable] net: qmi_wwan: add Quectel BG96 2c7c:0296

Hi, Sorry for the re-email of the patch below, clearly a beginners mistake of me not to clear my tmp/ folder. Please disregard this. Regards, Sebastian > On Dec 11, 2017, at 21:12 , ssjoh...@mac.com wrote: > > From: Sebastian Sjoholm > > Quectel BG96 is an Qualcomm

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 11 Dec 2017 19:54:33 + Jonathan Haws wrote: > > Probably a better subject would be: > > > >  ipc: mqueue: Have RT tasks queue in by priority in wq_add() > > Is the best way to change that just to change it in the email thread or > resubmit the patch as v2?

Re: [PATCH net,stable] net: qmi_wwan: add Quectel BG96 2c7c:0296

Hi, Sorry for the re-email of the patch below, clearly a beginners mistake of me not to clear my tmp/ folder. Please disregard this. Regards, Sebastian > On Dec 11, 2017, at 21:12 , ssjoh...@mac.com wrote: > > From: Sebastian Sjoholm > > Quectel BG96 is an Qualcomm MDM9206 based IoT modem,

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 11 Dec 2017 19:54:33 + Jonathan Haws wrote: > > Probably a better subject would be: > > > >  ipc: mqueue: Have RT tasks queue in by priority in wq_add() > > Is the best way to change that just to change it in the email thread or > resubmit the patch as v2? That, or whoever takes

[PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

From: Sebastian Sjoholm From: Sebastian Sjoholm Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. Signed-off-by: Sebastian Sjoholm --- [The

[PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

From: Sebastian Sjoholm From: Sebastian Sjoholm Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. Signed-off-by: Sebastian Sjoholm --- [The corresponding qcserial patch will be submitted by Reinhard

[PATCH net,stable] net: qmi_wwan: add Quectel BG96 2c7c:0296

From: Sebastian Sjoholm Quectel BG96 is an Qualcomm MDM9206 based IoT modem, supporting both CAT-M and NB-IoT. Tested hardware is BG96 mounted on Quectel development board (EVB). The USB id is added to qmi_wwan.c to allow QMI communication with the BG96. Signed-off-by:

[PATCH net,stable] net: qmi_wwan: add Quectel BG96 2c7c:0296

From: Sebastian Sjoholm Quectel BG96 is an Qualcomm MDM9206 based IoT modem, supporting both CAT-M and NB-IoT. Tested hardware is BG96 mounted on Quectel development board (EVB). The USB id is added to qmi_wwan.c to allow QMI communication with the BG96. Signed-off-by: Sebastian Sjoholm

Re: [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree

On Mon, Dec 11, 2017 at 12:31:06PM +0200, Joonas Lahtinen wrote: > + GVT folks. > > On Fri, 2017-12-08 at 09:15 +1100, Stephen Rothwell wrote: > > Hi all, > > > > Commit > > > > 365ad5df9caa ("drm/i915/gvt: Export > > intel_gvt_render_mmio_to_ring_id()") > > > > is missing a Signed-off-by

Re: [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree

On Mon, Dec 11, 2017 at 12:31:06PM +0200, Joonas Lahtinen wrote: > + GVT folks. > > On Fri, 2017-12-08 at 09:15 +1100, Stephen Rothwell wrote: > > Hi all, > > > > Commit > > > > 365ad5df9caa ("drm/i915/gvt: Export > > intel_gvt_render_mmio_to_ring_id()") > > > > is missing a Signed-off-by

Re: [PATCH] perf tools: Fix swap for samples with raw data

Em Wed, Nov 29, 2017 at 07:43:46PM +0100, Jiri Olsa escreveu: > When we detect different endianity we swap event before > processing. It's tricky for samples because we have no > idea what's inside. We treat it as an array of u64s, > swap them and later on we swap back parts which are > different.

Re: [PATCH] perf tools: Fix swap for samples with raw data

Em Wed, Nov 29, 2017 at 07:43:46PM +0100, Jiri Olsa escreveu: > When we detect different endianity we swap event before > processing. It's tricky for samples because we have no > idea what's inside. We treat it as an array of u64s, > swap them and later on we swap back parts which are > different.

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On Mon, Dec 11, 2017 at 11:47 AM, Dave Hansen wrote: > On 12/11/2017 11:39 AM, Andy Lutomirski wrote: >>> I thought there would be a "fast path" where we just use the normal >>> clear_LDT() LDT from the cpu_entry_area and don't have to do any of >>> this, but I'm missing

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On Mon, Dec 11, 2017 at 11:47 AM, Dave Hansen wrote: > On 12/11/2017 11:39 AM, Andy Lutomirski wrote: >>> I thought there would be a "fast path" where we just use the normal >>> clear_LDT() LDT from the cpu_entry_area and don't have to do any of >>> this, but I'm missing where that happens. Do

RE: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

From: Logan Gunthorpe > On 11/12/17 12:17 PM, Allen Hubbe wrote: > >> mw_get_align doesn't communicate the fact that the buffer has to be > >> aligned by its size. > > > > Is that not the purpose of the addr_align out parameter of > > ntb_mw_get_align()? > > addr_align provides the minimum

RE: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

From: Logan Gunthorpe > On 11/12/17 12:17 PM, Allen Hubbe wrote: > >> mw_get_align doesn't communicate the fact that the buffer has to be > >> aligned by its size. > > > > Is that not the purpose of the addr_align out parameter of > > ntb_mw_get_align()? > > addr_align provides the minimum

Re: Oops on 4.15-rc[123] on shutdown/reboot

On 11/12/17 17:17, Bjorn Helgaas wrote: > [+cc linux-pci] > > On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote: >> Hi Chris, >> >>> >>> I'm more than happy to provide additional diagnostics and test proposed >>> fixes. As a starter for ten, I've attached the >>> output from 'lspci -v'.

Re: Oops on 4.15-rc[123] on shutdown/reboot

On 11/12/17 17:17, Bjorn Helgaas wrote: > [+cc linux-pci] > > On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote: >> Hi Chris, >> >>> >>> I'm more than happy to provide additional diagnostics and test proposed >>> fixes. As a starter for ten, I've attached the >>> output from 'lspci -v'.

Re: [PATCH v3 5/5] perf-probe: Support escaped character in parser

Em Sat, Dec 09, 2017 at 01:28:41AM +0900, Masami Hiramatsu escreveu: > Support the special characters escaped by '\' in parser. > This allows user to specify versions directly like below. > > = > # ./perf probe -x /lib64/libc-2.25.so malloc_get_state\\@GLIBC_2.2.5 > Added new event: >

Re: [PATCH v3 5/5] perf-probe: Support escaped character in parser

Em Sat, Dec 09, 2017 at 01:28:41AM +0900, Masami Hiramatsu escreveu: > Support the special characters escaped by '\' in parser. > This allows user to specify versions directly like below. > > = > # ./perf probe -x /lib64/libc-2.25.so malloc_get_state\\@GLIBC_2.2.5 > Added new event: >

Re: [PATCH tip/core/rcu 02/20] torture: Prepare scripting for shift from %p to %pK

On Sun, Dec 10, 2017 at 1:47 PM, Paul E. McKenney wrote: > On Sun, Dec 10, 2017 at 12:39:11PM -0800, Linus Torvalds wrote: >> I'd rather make %pK act more like %p than have gratuitous differences. The feature that paranoid folks currently depend on is getting a value

Re: [PATCH tip/core/rcu 02/20] torture: Prepare scripting for shift from %p to %pK

On Sun, Dec 10, 2017 at 1:47 PM, Paul E. McKenney wrote: > On Sun, Dec 10, 2017 at 12:39:11PM -0800, Linus Torvalds wrote: >> I'd rather make %pK act more like %p than have gratuitous differences. The feature that paranoid folks currently depend on is getting a value entirely zeroed out with %pK

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 2017-12-11 at 14:32 -0500, Steven Rostedt wrote: > On Mon, 11 Dec 2017 17:12:05 + > Jonathan Haws wrote: > > > > > Adding linux-rt-users group to thread. > > > > From: Jonathan Haws > > Sent: Monday,

[PATCH v5] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for the TSCS42xx audio CODEC. Add support for it. v5 attempts to address all issues raised in the previous reviews. Thank you to everyone who has invested their time reviewing these patches. Acked-by: Philippe Ombredanne Signed-off-by:

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 2017-12-11 at 14:32 -0500, Steven Rostedt wrote: > On Mon, 11 Dec 2017 17:12:05 + > Jonathan Haws wrote: > > > > > Adding linux-rt-users group to thread. > > > > From: Jonathan Haws > > Sent: Monday, December 11, 2017 08:37 > > To:

[PATCH v5] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for the TSCS42xx audio CODEC. Add support for it. v5 attempts to address all issues raised in the previous reviews. Thank you to everyone who has invested their time reviewing these patches. Acked-by: Philippe Ombredanne Signed-off-by: Steven Eckhoff ---

[PATCH] writeback: synchronize sync(2) against cgroup writeback membership switches

sync_inodes_sb() can race against cgwb (cgroup writeback) membership switches and fail to writeback some inodes. For example, if an inode switches to another wb while sync_inodes_sb() is in progress, the new wb might not be visible to bdi_split_work_to_wbs() at all or the inode might jump from a

[PATCH] writeback: synchronize sync(2) against cgroup writeback membership switches

sync_inodes_sb() can race against cgwb (cgroup writeback) membership switches and fail to writeback some inodes. For example, if an inode switches to another wb while sync_inodes_sb() is in progress, the new wb might not be visible to bdi_split_work_to_wbs() at all or the inode might jump from a

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On 12/11/2017 11:39 AM, Andy Lutomirski wrote: >> I thought there would be a "fast path" where we just use the normal >> clear_LDT() LDT from the cpu_entry_area and don't have to do any of >> this, but I'm missing where that happens. Do we need a check in >> (un)map_ldt_struct() for

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On 12/11/2017 11:39 AM, Andy Lutomirski wrote: >> I thought there would be a "fast path" where we just use the normal >> clear_LDT() LDT from the cpu_entry_area and don't have to do any of >> this, but I'm missing where that happens. Do we need a check in >> (un)map_ldt_struct() for

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On Mon, Dec 11, 2017 at 11:32 AM, Dave Hansen wrote: > On 12/11/2017 10:40 AM, Andy Lutomirski wrote: >>> Also, from a high level, this does increase the overhead of KPTI in a >>> non-trivial way, right? It costs us three more page table pages per >>> process allocated at

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On Mon, Dec 11, 2017 at 11:32 AM, Dave Hansen wrote: > On 12/11/2017 10:40 AM, Andy Lutomirski wrote: >>> Also, from a high level, this does increase the overhead of KPTI in a >>> non-trivial way, right? It costs us three more page table pages per >>> process allocated at fork() and freed at

[BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

Hello, [First: Apologies if cross-posting from Kernel.org BZ is bad form; my distro BZ advised I post this to your mailing list as well.] Situation: enabling TPM on a Clevo W510LU with an Intel N3160 CPU breaks PS/2 keyboard and mouse. They just don't respond until after a suspend/resume

[BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

Hello, [First: Apologies if cross-posting from Kernel.org BZ is bad form; my distro BZ advised I post this to your mailing list as well.] Situation: enabling TPM on a Clevo W510LU with an Intel N3160 CPU breaks PS/2 keyboard and mouse. They just don't respond until after a suspend/resume

Re: RFC(v2): Audit Kernel Container IDs

On Monday, December 11, 2017 11:30:57 AM EST Eric Paris wrote: > > Because a container doesn't have to use namespaces to be a container > > you still need a mechanism for a process to declare that it is in > > fact > > in a container, and to identify the container. > > I like the idea but I'm

Re: RFC(v2): Audit Kernel Container IDs

On Monday, December 11, 2017 11:30:57 AM EST Eric Paris wrote: > > Because a container doesn't have to use namespaces to be a container > > you still need a mechanism for a process to declare that it is in > > fact > > in a container, and to identify the container. > > I like the idea but I'm

Re: [PATCH 0/4] Sunxi: Add SMP support on A83T

On Mon, Dec 11, 2017 at 08:49:57AM +0100, Mylène Josserand wrote: > Hello everyone, > > This series adds SMP support for Allwinner Sun8i-a83t > with MCPM (Multi-Cluster Power Management). > Series information: > - Based on last linux-next (next-20171211) > - Had

Re: [PATCH 0/4] Sunxi: Add SMP support on A83T

On Mon, Dec 11, 2017 at 08:49:57AM +0100, Mylène Josserand wrote: > Hello everyone, > > This series adds SMP support for Allwinner Sun8i-a83t > with MCPM (Multi-Cluster Power Management). > Series information: > - Based on last linux-next (next-20171211) > - Had

Re: [PATCH] tuners: tda8290: reduce stack usage with kasan

On Mon, 2017-12-11 at 13:06 +0100, Arnd Bergmann wrote: > With CONFIG_KASAN enabled, we get a relatively large stack frame in one > function > > drivers/media/tuners/tda8290.c: In function 'tda8290_set_params': > drivers/media/tuners/tda8290.c:310:1: warning: the frame size of 1520 bytes > is

Re: [PATCH] tuners: tda8290: reduce stack usage with kasan

On Mon, 2017-12-11 at 13:06 +0100, Arnd Bergmann wrote: > With CONFIG_KASAN enabled, we get a relatively large stack frame in one > function > > drivers/media/tuners/tda8290.c: In function 'tda8290_set_params': > drivers/media/tuners/tda8290.c:310:1: warning: the frame size of 1520 bytes > is

Re: [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull

On Mon, 11 Dec 2017 17:47:32 +0100 Ingo Molnar wrote: > > Link: > > http://lkml.kernel.org/r/8c913cc2-b2e3-8c2e-e503-aff1428f8...@monom.org > > Fixes: 4bdced5c9 ("sched/rt: Simplify the IPI based RT balancing logic") > > Cc: sta...@vger.kernel.org > > Reported-by: Daniel

Re: [PATCH] sched/rt: Do not pull from current CPU if only one cpu to pull

On Mon, 11 Dec 2017 17:47:32 +0100 Ingo Molnar wrote: > > Link: > > http://lkml.kernel.org/r/8c913cc2-b2e3-8c2e-e503-aff1428f8...@monom.org > > Fixes: 4bdced5c9 ("sched/rt: Simplify the IPI based RT balancing logic") > > Cc: sta...@vger.kernel.org > > Reported-by: Daniel Wagner > > I've

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On 12/11/2017 10:40 AM, Andy Lutomirski wrote: >> Also, from a high level, this does increase the overhead of KPTI in a >> non-trivial way, right? It costs us three more page table pages per >> process allocated at fork() and freed at exit() and a new TLB flush. > Yeah, but no one will care.

Re: [PATCH PTI v2 6/6] x86/pti: Put the LDT in its own PGD if PTI is on

On 12/11/2017 10:40 AM, Andy Lutomirski wrote: >> Also, from a high level, this does increase the overhead of KPTI in a >> non-trivial way, right? It costs us three more page table pages per >> process allocated at fork() and freed at exit() and a new TLB flush. > Yeah, but no one will care.

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 11 Dec 2017 17:12:05 + Jonathan Haws wrote: > Adding linux-rt-users group to thread. > > From: Jonathan Haws > Sent: Monday, December 11, 2017 08:37 > To: mi...@kernel.org; v...@zeniv.linux.org.uk;

Re: [RFC][PATCH] ipc: mqueue: wq_add priority changed to dynamic priority

On Mon, 11 Dec 2017 17:12:05 + Jonathan Haws wrote: > Adding linux-rt-users group to thread. > > From: Jonathan Haws > Sent: Monday, December 11, 2017 08:37 > To: mi...@kernel.org; v...@zeniv.linux.org.uk; a...@arndb.de; > a...@linux-foundation.org;

Re: Oops on 4.15-rc[123] on shutdown/reboot

On 11/12/17 17:24, Sinan Kaya wrote: > On 12/11/2017 12:06 PM, Chris Clayton wrote: >> Here's the output of dmesg for 4.15.0-rc3. I'll open a bugzilla later and >> add this and the lspci output that I sent with >> my original repoart. > > This was helpful. I don't see any AER/DPC in your log.

Re: Oops on 4.15-rc[123] on shutdown/reboot

On 11/12/17 17:24, Sinan Kaya wrote: > On 12/11/2017 12:06 PM, Chris Clayton wrote: >> Here's the output of dmesg for 4.15.0-rc3. I'll open a bugzilla later and >> add this and the lspci output that I sent with >> my original repoart. > > This was helpful. I don't see any AER/DPC in your log.

Re: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

On 11/12/17 12:17 PM, Allen Hubbe wrote: From: Logan Gunthorpe mw_get_align doesn't communicate the fact that the buffer has to be aligned by its size. Is that not the purpose of the addr_align out parameter of ntb_mw_get_align()? addr_align provides the minimum alignment required by the

Re: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

On 11/12/17 12:17 PM, Allen Hubbe wrote: From: Logan Gunthorpe mw_get_align doesn't communicate the fact that the buffer has to be aligned by its size. Is that not the purpose of the addr_align out parameter of ntb_mw_get_align()? addr_align provides the minimum alignment required by the

Re: [PATCH 16/20] ARM: dts: aspeed: Add Witherspoon BMC machine

On Sun, Dec 10, 2017 at 11:07 PM, Joel Stanley wrote: > The Witherspoon BMC is an ASPEED ast2500 based BMC that is part of an > OpenPower Power9 server. > > This adds the device tree description for most upstream components. It > is a squashed commit from the OpenBMC kernel tree.

Re: [PATCH 16/20] ARM: dts: aspeed: Add Witherspoon BMC machine

On Sun, Dec 10, 2017 at 11:07 PM, Joel Stanley wrote: > The Witherspoon BMC is an ASPEED ast2500 based BMC that is part of an > OpenPower Power9 server. > > This adds the device tree description for most upstream components. It > is a squashed commit from the OpenBMC kernel tree. > >

Re: [kernel-hardening][PATCH] arm: hw_breakpoint: Mark variables as __ro_after_init

On Mon, Dec 11, 2017 at 4:50 AM, Jinbum Park wrote: > core_num_brps, core_num_wrps, debug_arch, has_ossr, > max_watchpoint_len are setup once while init stage, > and never changed after that. > so it is good candidate for __ro_after_init. > > Signed-off-by: Jinbum Park

Re: [kernel-hardening][PATCH] arm: hw_breakpoint: Mark variables as __ro_after_init

On Mon, Dec 11, 2017 at 4:50 AM, Jinbum Park wrote: > core_num_brps, core_num_wrps, debug_arch, has_ossr, > max_watchpoint_len are setup once while init stage, > and never changed after that. > so it is good candidate for __ro_after_init. > > Signed-off-by: Jinbum Park Reviewed-by: Kees Cook

RE: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

From: Logan Gunthorpe > mw_get_align doesn't communicate the fact that the buffer has to be > aligned by its size. Is that not the purpose of the addr_align out parameter of ntb_mw_get_align()? > It may also be that all hardware does not have this > restriction (ie. if the hardware adds to the

RE: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

From: Logan Gunthorpe > mw_get_align doesn't communicate the fact that the buffer has to be > aligned by its size. Is that not the purpose of the addr_align out parameter of ntb_mw_get_align()? > It may also be that all hardware does not have this > restriction (ie. if the hardware adds to the

[PATCH] net: igmp: Use correct source address on IGMPv3 reports

Closing a multicast socket after the final IPv4 address is deleted from an interface can generate a membership report that uses the source IP from a different interface. The following test script, run from an isolated netns, reproduces the issue: #!/bin/bash ip link add dummy0 type

[PATCH] net: igmp: Use correct source address on IGMPv3 reports

Closing a multicast socket after the final IPv4 address is deleted from an interface can generate a membership report that uses the source IP from a different interface. The following test script, run from an isolated netns, reproduces the issue: #!/bin/bash ip link add dummy0 type

Re: [PATCH] Fix resume on x86-32 machines

On Mon, Dec 11, 2017 at 10:41 AM, Andy Lutomirski wrote: > > I'll try to get to this in a day or so -- is that okay? Or should we > do some trivial fix/revert and fix it for real next time around? I don't think we want some trivial fix/revert just to keep it working. This

Re: [PATCH] Fix resume on x86-32 machines

On Mon, Dec 11, 2017 at 10:41 AM, Andy Lutomirski wrote: > > I'll try to get to this in a day or so -- is that okay? Or should we > do some trivial fix/revert and fix it for real next time around? I don't think we want some trivial fix/revert just to keep it working. This code is too fragile

Re: general protection fault in blkcipher_walk_done

On Mon, Nov 27, 2017 at 10:56:47AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > If you want to test a patch for this bug, please reply with: > #syz test:

Re: general protection fault in blkcipher_walk_done

On Mon, Nov 27, 2017 at 10:56:47AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > If you want to test a patch for this bug, please reply with: > #syz test:

Re: [PATCH v10 4/4] [media] platform: Add Synopsys DesignWare HDMI RX Controller Driver

On Mon, Dec 11, 2017 at 6:41 PM, Jose Abreu wrote: > This is an initial submission for the Synopsys DesignWare HDMI RX > Controller Driver. This driver interacts with a phy driver so that > a communication between them is created and a video pipeline is > configured. > >

Re: [PATCH v10 4/4] [media] platform: Add Synopsys DesignWare HDMI RX Controller Driver

On Mon, Dec 11, 2017 at 6:41 PM, Jose Abreu wrote: > This is an initial submission for the Synopsys DesignWare HDMI RX > Controller Driver. This driver interacts with a phy driver so that > a communication between them is created and a video pipeline is > configured. > > The controller + phy

Re: general protection fault in crypto_chacha20_crypt

On Wed, Nov 29, 2017 at 01:24:38AM -0800, Eric Biggers wrote: > > The bug is that the skcipher_walk API doesn't set the IV for zero-length > inputs, > while some algorithms (e.g. ChaCha20) access the IV even if the input is > zero-length. So it was dereferencing a pointer which came from

Re: general protection fault in crypto_chacha20_crypt

On Wed, Nov 29, 2017 at 01:24:38AM -0800, Eric Biggers wrote: > > The bug is that the skcipher_walk API doesn't set the IV for zero-length > inputs, > while some algorithms (e.g. ChaCha20) access the IV even if the input is > zero-length. So it was dereferencing a pointer which came from

Re: [PATCH v10 3/4] [media] platform: Add Synopsys DesignWare HDMI RX PHY e405 Driver

On Mon, Dec 11, 2017 at 6:41 PM, Jose Abreu wrote: > This adds support for the Synopsys DesignWare HDMI RX PHY e405. This > phy receives and decodes HDMI video that is delivered to a controller. > > Main features included in this driver are: > - Equalizer

Re: [PATCH v10 3/4] [media] platform: Add Synopsys DesignWare HDMI RX PHY e405 Driver

On Mon, Dec 11, 2017 at 6:41 PM, Jose Abreu wrote: > This adds support for the Synopsys DesignWare HDMI RX PHY e405. This > phy receives and decodes HDMI video that is delivered to a controller. > > Main features included in this driver are: > - Equalizer algorithm that chooses the phy

Re: [PATCH 27/45] net: remove duplicate includes

On Mon, Dec 11, 2017 at 10:09:46PM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Signed-off-by: Pravin Shedge For the Netfilter

Re: [PATCH 27/45] net: remove duplicate includes

On Mon, Dec 11, 2017 at 10:09:46PM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Signed-off-by: Pravin Shedge For the Netfilter chunk. Acked-by: Pablo Neira Ayuso

Re: [ANNOUNCE] 4.1.46-rt52

On 11/29/2017 05:13 PM, Julia Cartwright wrote: Hello RT Folks! I'm pleased to announce the 4.1.46-rt52 stable release. You can get this release via the git tree at: git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git branch: v4.1-rt Head SHA1:

Re: [ANNOUNCE] 4.1.46-rt52

On 11/29/2017 05:13 PM, Julia Cartwright wrote: Hello RT Folks! I'm pleased to announce the 4.1.46-rt52 stable release. You can get this release via the git tree at: git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git branch: v4.1-rt Head SHA1:

Re: [RFC PATCH 0/9] ethtool netlink interface (WiP)

On 12/11/2017 09:01 AM, David Miller wrote: > From: Jiri Pirko > Date: Mon, 11 Dec 2017 17:32:46 +0100 > >> I think that it does not make sense to convert ethtool->netlink_ethtool >> 1:1 feature wise. Now we have devlink, ritch switch representation >> model, tc offload and

Re: [RFC PATCH 0/9] ethtool netlink interface (WiP)

On 12/11/2017 09:01 AM, David Miller wrote: > From: Jiri Pirko > Date: Mon, 11 Dec 2017 17:32:46 +0100 > >> I think that it does not make sense to convert ethtool->netlink_ethtool >> 1:1 feature wise. Now we have devlink, ritch switch representation >> model, tc offload and many others. Lot of

Re: KASAN: use-after-free Write in aead_recvmsg

On Mon, Dec 04, 2017 at 07:57:01AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > If you want to test a patch for this bug, please reply with: > #syz test:

Re: KASAN: use-after-free Write in aead_recvmsg

On Mon, Dec 04, 2017 at 07:57:01AM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > If you want to test a patch for this bug, please reply with: > #syz test:

[PATCH 2/4] ASoC: codecs: tas5720: add TAS5722 register support

From: Andreas Dannenberg Introduce a custom super-set register map and associated bit definitions to allow driver access to all TAS5722 device functionality. Signed-off-by: Andreas Dannenberg Signed-off-by: Andrew F. Davis ---

[PATCH 2/4] ASoC: codecs: tas5720: add TAS5722 register support

From: Andreas Dannenberg Introduce a custom super-set register map and associated bit definitions to allow driver access to all TAS5722 device functionality. Signed-off-by: Andreas Dannenberg Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tas5720.c | 23 ++-

[PATCH] ASoC: nau8825: fix issue that pop noise when start capture

From: Abhijeet Kumar In skylake platform, we hear a loud pop noise(0 dB) at start of audio capture power up sequence. This patch removes the pop noise from the recording by adding a delay before enabling ADC. Signed-off-by: Abhijeet Kumar ---

[PATCH] ASoC: nau8825: fix issue that pop noise when start capture

From: Abhijeet Kumar In skylake platform, we hear a loud pop noise(0 dB) at start of audio capture power up sequence. This patch removes the pop noise from the recording by adding a delay before enabling ADC. Signed-off-by: Abhijeet Kumar --- sound/soc/codecs/nau8825.c | 1 + 1 file changed,

[PATCH 1/4] ASoC: codecs: tas5720: add basic support for TAS5722 devices

From: Andreas Dannenberg The TI TAS5722 digital amplifier is very similar to the TAS5720 from an overall and register map perspective. Therefore the existing driver can be extended easily to support this additional device. This commit allows TAS5722 devices to be used in a

[PATCH 1/4] ASoC: codecs: tas5720: add basic support for TAS5722 devices

From: Andreas Dannenberg The TI TAS5722 digital amplifier is very similar to the TAS5720 from an overall and register map perspective. Therefore the existing driver can be extended easily to support this additional device. This commit allows TAS5722 devices to be used in a "subset" type of

[PATCH 4/4] ASoC: codecs: tas5720: add TAS5722 TDM slot width setting support

From: Andreas Dannenberg Unlike the TAS5720, the TAS5722 can be configured to utilize 16-bit wide slots in TDM mode. This can help easing audio clocking/frequency requirements. Signed-off-by: Andreas Dannenberg Signed-off-by: Andrew F. Davis

[PATCH 4/4] ASoC: codecs: tas5720: add TAS5722 TDM slot width setting support

From: Andreas Dannenberg Unlike the TAS5720, the TAS5722 can be configured to utilize 16-bit wide slots in TDM mode. This can help easing audio clocking/frequency requirements. Signed-off-by: Andreas Dannenberg Signed-off-by: Andrew F. Davis --- sound/soc/codecs/tas5720.c | 11 +++ 1

[PATCH 3/4] ASoC: codecs: tas5720: add TAS5722 specific volume control

From: Andreas Dannenberg The TAS5722 supports modifying volume in 0.25dB steps (as opposed to 0.5dB steps on the TAS5720). Introduce a custom mixer control that allows taking advantage of this finer output volume granularity. Signed-off-by: Andreas Dannenberg

[PATCH 3/4] ASoC: codecs: tas5720: add TAS5722 specific volume control

From: Andreas Dannenberg The TAS5722 supports modifying volume in 0.25dB steps (as opposed to 0.5dB steps on the TAS5720). Introduce a custom mixer control that allows taking advantage of this finer output volume granularity. Signed-off-by: Andreas Dannenberg Signed-off-by: Andrew F. Davis

Re: [RESEND PATCH] arm64: v8.4: Support for new floating point multiplication variant

Hi gengdongjiu Sorry for the late response. I have a similar patch to add the support for "FHM", which I was about to post it this week. On 11/12/17 13:29, Dave Martin wrote: On Mon, Dec 11, 2017 at 08:47:00PM +0800, gengdongjiu wrote: On 2017/12/11 19:59, Dave P Martin wrote: On Sat, Dec

Re: [RESEND PATCH] arm64: v8.4: Support for new floating point multiplication variant

Hi gengdongjiu Sorry for the late response. I have a similar patch to add the support for "FHM", which I was about to post it this week. On 11/12/17 13:29, Dave Martin wrote: On Mon, Dec 11, 2017 at 08:47:00PM +0800, gengdongjiu wrote: On 2017/12/11 19:59, Dave P Martin wrote: On Sat, Dec

RE: [PATCH v2] Enable SR-IOV instantiation through /sys file

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Monday, December 11, 2017 1:13 PM > To: Wang, Liang-min > Cc: Alexander Duyck ; Kirsher, Jeffrey T > ;

RE: [PATCH v2] Enable SR-IOV instantiation through /sys file

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Monday, December 11, 2017 1:13 PM > To: Wang, Liang-min > Cc: Alexander Duyck ; Kirsher, Jeffrey T > ; k...@vger.kernel.org; linux- > p...@vger.kernel.org; linux-kernel@vger.kernel.org; Bjorn

Re: Linux 4.15-rc3 (uml + bpf_perf_event.h)

On 12/11/2017 10:49 AM, Richard Weinberger wrote: > Am Montag, 11. Dezember 2017, 11:19:54 CET schrieb Daniel Borkmann: >> Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ] >> >> On 12/11/2017 09:32 AM, Richard Weinberger wrote: >>> Randy, >>> >>> Am Montag, 11. Dezember 2017, 03:42:12 CET

Re: Linux 4.15-rc3 (uml + bpf_perf_event.h)

On 12/11/2017 10:49 AM, Richard Weinberger wrote: > Am Montag, 11. Dezember 2017, 11:19:54 CET schrieb Daniel Borkmann: >> Hi Randy, hi Richard, [ +Hendrik for c895f6f703ad7dd2f ] >> >> On 12/11/2017 09:32 AM, Richard Weinberger wrote: >>> Randy, >>> >>> Am Montag, 11. Dezember 2017, 03:42:12 CET

Re: general protection fault in strcmp

On Thu, Nov 30, 2017 at 12:44:01PM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

Re: general protection fault in strcmp

On Thu, Nov 30, 2017 at 12:44:01PM -0800, syzbot wrote: > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to this email with: > #syz fix: exact-commit-title > To mark this as a duplicate of another syzbot report, please reply with: > #syz dup:

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