fanotify: Support for file creation and deletion

Hello, we are a group of students, for a course we would like to create an efficient backup/file synchronization tool that supports file system trees with lots of directories. Currently such tools use the inotify interface but we would rather not use it because (1) inotify requires a watch

[PATCH 3/3] Staging:wilc1000:host_interface: Integrated two 'if' statements to a single 'if' statement

Removed unnecessary 'if' statement and integrated the condition to the previous 'if' statement. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/host_interface.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git

fanotify: Support for file creation and deletion

Hello, we are a group of students, for a course we would like to create an efficient backup/file synchronization tool that supports file system trees with lots of directories. Currently such tools use the inotify interface but we would rather not use it because (1) inotify requires a watch

[PATCH 3/3] Staging:wilc1000:host_interface: Integrated two 'if' statements to a single 'if' statement

Removed unnecessary 'if' statement and integrated the condition to the previous 'if' statement. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/host_interface.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git

[PATCH 14/26] [media] dvb-frontends: reduce stack size in i2c access

A typical code fragment was copied across many dvb-frontend drivers and causes large stack frames when built with -fsanitize-address-use-after-scope, e.g. drivers/media/dvb-frontends/cxd2841er.c:3225:1: error: the frame size of 3992 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]

[PATCH 14/26] [media] dvb-frontends: reduce stack size in i2c access

A typical code fragment was copied across many dvb-frontend drivers and causes large stack frames when built with -fsanitize-address-use-after-scope, e.g. drivers/media/dvb-frontends/cxd2841er.c:3225:1: error: the frame size of 3992 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]

[PATCH 26/26] kasan: rework Kconfig settings

We get a lot of very large stack frames using gcc-7.0.1 with the default -fsanitize-address-use-after-scope --param asan-stack=1 options, which can easily cause an overflow of the kernel stack, e.g. drivers/acpi/nfit/core.c:2686:1: warning: the frame size of 4080 bytes is larger than 2048 bytes

[PATCH 26/26] kasan: rework Kconfig settings

We get a lot of very large stack frames using gcc-7.0.1 with the default -fsanitize-address-use-after-scope --param asan-stack=1 options, which can easily cause an overflow of the kernel stack, e.g. drivers/acpi/nfit/core.c:2686:1: warning: the frame size of 4080 bytes is larger than 2048 bytes

[PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

When CONFIG_KASAN is enabled, the READ_ONCE/WRITE_ONCE macros cause rather large kernel stacks, e.g.: mm/vmscan.c: In function 'shrink_page_list': mm/vmscan.c:1333:1: error: the frame size of 3456 bytes is larger than 3072 bytes [-Werror=frame-larger-than=] block/cfq-iosched.c: In function

[PATCH 13/26] rtl8180: reduce stack size for KASAN

When CONFIG_KASAN is set, we see overly large stack frames from inlining functions with local variables: drivers/net/wireless/realtek/rtl818x/rtl8180/rtl8225se.c: In function 'rtl8225se_rf_init': drivers/net/wireless/realtek/rtl818x/rtl8180/rtl8225se.c:431:1: warning: the frame size of 4384

[PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

When CONFIG_KASAN is enabled, the READ_ONCE/WRITE_ONCE macros cause rather large kernel stacks, e.g.: mm/vmscan.c: In function 'shrink_page_list': mm/vmscan.c:1333:1: error: the frame size of 3456 bytes is larger than 3072 bytes [-Werror=frame-larger-than=] block/cfq-iosched.c: In function

[PATCH 13/26] rtl8180: reduce stack size for KASAN

When CONFIG_KASAN is set, we see overly large stack frames from inlining functions with local variables: drivers/net/wireless/realtek/rtl818x/rtl8180/rtl8225se.c: In function 'rtl8225se_rf_init': drivers/net/wireless/realtek/rtl818x/rtl8180/rtl8225se.c:431:1: warning: the frame size of 4384

[PATCH 19/26] [media] r820t: mark register functions as noinline_for_kasan

With KASAN, we get an overly long stack frame due to inlining the register access function: drivers/media/tuners/r820t.c: In function 'generic_set_freq.isra.7': drivers/media/tuners/r820t.c:1334:1: error: the frame size of 2880 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] An

[PATCH 19/26] [media] r820t: mark register functions as noinline_for_kasan

With KASAN, we get an overly long stack frame due to inlining the register access function: drivers/media/tuners/r820t.c: In function 'generic_set_freq.isra.7': drivers/media/tuners/r820t.c:1334:1: error: the frame size of 2880 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] An

[RFC PATCH v2 14/32] x86: mm: Provide support to use memblock when spliting large pages

If kernel_maps_pages_in_pgd is called early in boot process to change the memory attributes then it fails to allocate memory when spliting large pages. The patch extends the cpa_data to provide the support to use memblock_alloc when slab allocator is not available. The feature will be used in

[RFC PATCH v2 14/32] x86: mm: Provide support to use memblock when spliting large pages

If kernel_maps_pages_in_pgd is called early in boot process to change the memory attributes then it fails to allocate memory when spliting large pages. The patch extends the cpa_data to provide the support to use memblock_alloc when slab allocator is not available. The feature will be used in

Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On 03/02/2017 05:38 PM, Arnd Bergmann wrote: > When CONFIG_KASAN is enabled, the READ_ONCE/WRITE_ONCE macros cause > rather large kernel stacks, e.g.: > > mm/vmscan.c: In function 'shrink_page_list': > mm/vmscan.c:1333:1: error: the frame size of 3456 bytes is larger than 3072 > bytes

Re: [PATCH 02/26] rewrite READ_ONCE/WRITE_ONCE

On 03/02/2017 05:38 PM, Arnd Bergmann wrote: > When CONFIG_KASAN is enabled, the READ_ONCE/WRITE_ONCE macros cause > rather large kernel stacks, e.g.: > > mm/vmscan.c: In function 'shrink_page_list': > mm/vmscan.c:1333:1: error: the frame size of 3456 bytes is larger than 3072 > bytes

Re: [PATCH v4 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

Hi Kishon, On Wed, Feb 22, 2017 at 9:29 AM, Vivek Gautam wrote: > Hi Kishon, > > > On Fri, Jan 27, 2017 at 11:54 AM, Vivek Gautam > wrote: >> >> >> On 01/26/2017 11:45 PM, Bjorn Andersson wrote: >>> >>> On Tue 24 Jan 01:19 PST 2017,

Re: [PATCH v4 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

Hi Kishon, On Wed, Feb 22, 2017 at 9:29 AM, Vivek Gautam wrote: > Hi Kishon, > > > On Fri, Jan 27, 2017 at 11:54 AM, Vivek Gautam > wrote: >> >> >> On 01/26/2017 11:45 PM, Bjorn Andersson wrote: >>> >>> On Tue 24 Jan 01:19 PST 2017, Kishon Vijay Abraham I wrote: On Monday 23 January

Re: [Outreachy kernel] [PATCH] staging: nvec: cleanup USLEEP_RANGE checkpatch checks

On Thu, 2 Mar 2017, SIMRAN SINGHAL wrote: > > > On Thursday, March 2, 2017 at 8:31:23 PM UTC+5:30, Julia Lawall wrote: > > > On Thu, 2 Mar 2017, SIMRAN SINGHAL wrote: > > > > > > > On Thursday, March 2, 2017 at 8:06:40 PM UTC+5:30, Julia > Lawall wrote: > > >

Re: [Outreachy kernel] [PATCH] staging: nvec: cleanup USLEEP_RANGE checkpatch checks

On Thu, 2 Mar 2017, SIMRAN SINGHAL wrote: > > > On Thursday, March 2, 2017 at 8:31:23 PM UTC+5:30, Julia Lawall wrote: > > > On Thu, 2 Mar 2017, SIMRAN SINGHAL wrote: > > > > > > > On Thursday, March 2, 2017 at 8:06:40 PM UTC+5:30, Julia > Lawall wrote: > > >

[RFC PATCH v2 13/32] KVM: SVM: Enable SEV by setting the SEV_ENABLE CPU feature

From: Tom Lendacky Modify the SVM cpuid update function to indicate if Secure Encrypted Virtualization (SEV) is active in the guest by setting the SEV KVM CPU features bit. SEV is active if Secure Memory Encryption is enabled in the host and the SEV_ENABLE bit of the

[RFC PATCH v2 13/32] KVM: SVM: Enable SEV by setting the SEV_ENABLE CPU feature

From: Tom Lendacky Modify the SVM cpuid update function to indicate if Secure Encrypted Virtualization (SEV) is active in the guest by setting the SEV KVM CPU features bit. SEV is active if Secure Memory Encryption is enabled in the host and the SEV_ENABLE bit of the VMCB is set. Signed-off-by:

[RFC PATCH v2 12/32] x86: Add early boot support when running with SEV active

From: Tom Lendacky Early in the boot process, add checks to determine if the kernel is running with Secure Encrypted Virtualization (SEV) active by issuing a CPUID instruction. During early compressed kernel booting, if SEV is active the pagetables are updated so that

[RFC PATCH v2 12/32] x86: Add early boot support when running with SEV active

From: Tom Lendacky Early in the boot process, add checks to determine if the kernel is running with Secure Encrypted Virtualization (SEV) active by issuing a CPUID instruction. During early compressed kernel booting, if SEV is active the pagetables are updated so that data is accessed and

Re: rxrpc: Fix deadlock between call creation and sendmsg/recvmsg

Colin Ian King wrote: > I think the following part of the patch is problematic: > > call = rxrpc_find_call_by_user_ID(rx, user_call_ID); > if (!call) { > + ret = -EBADSLT; > if (cmd != RXRPC_CMD_SEND_DATA) > -

[PATCH 21/26] drm/bridge: ps8622: reduce stack size for KASAN

When CONFIG_KASAN is set, each call to ps8622_set() adds an object to the stack frame, leading to a warning about possible stack overflow: drivers/gpu/drm/bridge/parade-ps8622.c: In function 'ps8622_send_config': drivers/gpu/drm/bridge/parade-ps8622.c:338:1: error: the frame size of 5872 bytes

Re: rxrpc: Fix deadlock between call creation and sendmsg/recvmsg

Colin Ian King wrote: > I think the following part of the patch is problematic: > > call = rxrpc_find_call_by_user_ID(rx, user_call_ID); > if (!call) { > + ret = -EBADSLT; > if (cmd != RXRPC_CMD_SEND_DATA) > - return -EBADSLT;

[PATCH 21/26] drm/bridge: ps8622: reduce stack size for KASAN

When CONFIG_KASAN is set, each call to ps8622_set() adds an object to the stack frame, leading to a warning about possible stack overflow: drivers/gpu/drm/bridge/parade-ps8622.c: In function 'ps8622_send_config': drivers/gpu/drm/bridge/parade-ps8622.c:338:1: error: the frame size of 5872 bytes

[PATCH 17/26] [media] i2c: ks0127: reduce stack frame size for KASAN

When CONFIG_KASAN is set, inlining of functions with local variables causes excessive stack usage: drivers/media/i2c/ks0127.c: In function 'ks0127_s_routing': drivers/media/i2c/ks0127.c:541:1: error: the frame size of 3136 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] Marking one

[PATCH 25/26] isdn: eicon: mark divascapi incompatible with kasan

When CONFIG_KASAN is enabled, we have several functions that use rather large kernel stacks, e.g. drivers/isdn/hardware/eicon/message.c: In function 'group_optimization': drivers/isdn/hardware/eicon/message.c:14841:1: warning: the frame size of 864 bytes is larger than 500 bytes

[PATCH 17/26] [media] i2c: ks0127: reduce stack frame size for KASAN

When CONFIG_KASAN is set, inlining of functions with local variables causes excessive stack usage: drivers/media/i2c/ks0127.c: In function 'ks0127_s_routing': drivers/media/i2c/ks0127.c:541:1: error: the frame size of 3136 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] Marking one

[PATCH 25/26] isdn: eicon: mark divascapi incompatible with kasan

When CONFIG_KASAN is enabled, we have several functions that use rather large kernel stacks, e.g. drivers/isdn/hardware/eicon/message.c: In function 'group_optimization': drivers/isdn/hardware/eicon/message.c:14841:1: warning: the frame size of 864 bytes is larger than 500 bytes

[PATCH] Staging:wilc1000:wilc_sdio: Modified comment style to preferred kernel comment style

Modified comment style to preferred kernel comment style. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/wilc_sdio.c | 13 + 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/drivers/staging/wilc1000/wilc_sdio.c

[PATCH] Staging:wilc1000:wilc_sdio: Modified comment style to preferred kernel comment style

Modified comment style to preferred kernel comment style. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/wilc_sdio.c | 13 + 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/drivers/staging/wilc1000/wilc_sdio.c b/drivers/staging/wilc1000/wilc_sdio.c

[PATCH] clk: tegra: fix disable unused for clocks sharing enable bit

In case 2 clocks share an enable bit and one of them is enabled by a driver and the other one is not, CCF will think it's enabled because it will only look at the hw state. Therefor it will disable the clock and thus also disable the other clock which was enabled. Solve this by reading the initial

[PATCH] clk: tegra: fix disable unused for clocks sharing enable bit

In case 2 clocks share an enable bit and one of them is enabled by a driver and the other one is not, CCF will think it's enabled because it will only look at the hw state. Therefor it will disable the clock and thus also disable the other clock which was enabled. Solve this by reading the initial

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

Le 02/03/2017 à 15:29, Boris Brezillon a écrit : > On Thu, 2 Mar 2017 19:24:43 +0530 > Vignesh R wrote: > >> > Not really, I am debugging another issue with UBIFS on DRA74 EVM (ARM > cortex-a15) wherein pages allocated by vmalloc are in highmem region > that

Re: [RFC PATCH 2/2] mtd: devices: m25p80: Enable spi-nor bounce buffer support

Le 02/03/2017 à 15:29, Boris Brezillon a écrit : > On Thu, 2 Mar 2017 19:24:43 +0530 > Vignesh R wrote: > >> > Not really, I am debugging another issue with UBIFS on DRA74 EVM (ARM > cortex-a15) wherein pages allocated by vmalloc are in highmem region > that are not

[PATCH] clk: tegra: Implement reset control reset

From: Mikko Perttunen For completeness, also implement this reset framework API for Tegra. Signed-off-by: Mikko Perttunen Reviewed-by: Peter De Schrijver Reviewed-by: Arto Merilainen ---

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

On Thu, Mar 02, 2017 at 05:16:06PM +0100, Michal Hocko wrote: > I've just realized that Darrick was not on the CC list. Let's add him. > I believe this patch should go in in the current cycle because > 5d17a73a2ebe was merged in this merge window and it can be abused... > > The other patch [1] is

[PATCH] clk: tegra: Implement reset control reset

From: Mikko Perttunen For completeness, also implement this reset framework API for Tegra. Signed-off-by: Mikko Perttunen Reviewed-by: Peter De Schrijver Reviewed-by: Arto Merilainen --- drivers/clk/tegra/clk.c | 16 1 file changed, 16 insertions(+) diff --git

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

On Thu, Mar 02, 2017 at 05:16:06PM +0100, Michal Hocko wrote: > I've just realized that Darrick was not on the CC list. Let's add him. > I believe this patch should go in in the current cycle because > 5d17a73a2ebe was merged in this merge window and it can be abused... > > The other patch [1] is

Re: [PATCH 00/11] drm/meson: Initial support for HDMI Output

On 03/02/2017 04:58 PM, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 04:39:56PM +0100, Neil Armstrong wrote: >> The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller >> in combination with a very custom PHY. >> >> This patchset depends on Laurent Pinchart v4 patchset at [1] and

Re: [PATCH 00/11] drm/meson: Initial support for HDMI Output

On 03/02/2017 04:58 PM, Daniel Vetter wrote: > On Thu, Mar 02, 2017 at 04:39:56PM +0100, Neil Armstrong wrote: >> The Amlogic GX SoCs implements a Synopsys DesignWare HDMI TX Controller >> in combination with a very custom PHY. >> >> This patchset depends on Laurent Pinchart v4 patchset at [1] and

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

On 2017-03-01 at 20:45:21 +0100, Guenter Roeck wrote: > On Wed, Mar 01, 2017 at 07:58:17PM +0100, Sven Schmidt wrote: > > Hi Guenter, Tobias and Sandra, > > > > thanks for your effort here. > > > > On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote: > > > On Tue,

Re: nios2 crash/hang in mainline due to 'lib: update LZ4 compressor module'

On 2017-03-01 at 20:45:21 +0100, Guenter Roeck wrote: > On Wed, Mar 01, 2017 at 07:58:17PM +0100, Sven Schmidt wrote: > > Hi Guenter, Tobias and Sandra, > > > > thanks for your effort here. > > > > On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote: > > > On Tue, Feb 28, 2017 at

Re: [PATCH 6/7] net: stmmac: dwc-qos: Split out ->probe() and ->remove()

Às 5:24 PM de 2/23/2017, Thierry Reding escreveu: > From: Thierry Reding > > Split out the binding specific parts of ->probe() and ->remove() to > enable the driver to support variants of the binding. This is useful in > order to keep backwards-compatibility while making it

Re: [PATCH 6/7] net: stmmac: dwc-qos: Split out ->probe() and ->remove()

Às 5:24 PM de 2/23/2017, Thierry Reding escreveu: > From: Thierry Reding > > Split out the binding specific parts of ->probe() and ->remove() to > enable the driver to support variants of the binding. This is useful in > order to keep backwards-compatibility while making it easy for a sub- >

Re: [PATCH v5 06/10] seccomp,landlock: Handle Landlock events per process hierarchy

On Wed, Mar 1, 2017 at 3:28 PM, Mickaël Salaün wrote: > > > On 01/03/2017 23:20, Andy Lutomirski wrote: >> On Wed, Mar 1, 2017 at 2:14 PM, Mickaël Salaün wrote: >>> >>> On 28/02/2017 21:01, Andy Lutomirski wrote: On Tue, Feb 21, 2017 at 5:26 PM, Mickaël

Re: [PATCH v5 06/10] seccomp,landlock: Handle Landlock events per process hierarchy

On Wed, Mar 1, 2017 at 3:28 PM, Mickaël Salaün wrote: > > > On 01/03/2017 23:20, Andy Lutomirski wrote: >> On Wed, Mar 1, 2017 at 2:14 PM, Mickaël Salaün wrote: >>> >>> On 28/02/2017 21:01, Andy Lutomirski wrote: On Tue, Feb 21, 2017 at 5:26 PM, Mickaël Salaün wrote: >>> This design makes

[PATCH 2/4] staging: speakup: spaces preferred around operator

Fixed the checkpatch.pl issues like: CHECK: spaces preferred around that '&' (ctx:VxV) CHECK: spaces preferred around that '|' (ctx:VxV) CHECK: spaces preferred around that '-' (ctx:VxV) CHECK: spaces preferred around that '+' (ctx:VxV) etc. Signed-off-by: Arushi Singhal

[PATCH 2/4] staging: speakup: spaces preferred around operator

Fixed the checkpatch.pl issues like: CHECK: spaces preferred around that '&' (ctx:VxV) CHECK: spaces preferred around that '|' (ctx:VxV) CHECK: spaces preferred around that '-' (ctx:VxV) CHECK: spaces preferred around that '+' (ctx:VxV) etc. Signed-off-by: Arushi Singhal ---

[PATCH 03/11] drm/meson: Add support for components

This patch adds support for optional components connected through the Device Tree endpoints scheme. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_drv.c | 113 +- 1 file changed, 99 insertions(+), 14 deletions(-) diff

[PATCH 03/11] drm/meson: Add support for components

This patch adds support for optional components connected through the Device Tree endpoints scheme. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_drv.c | 113 +- 1 file changed, 99 insertions(+), 14 deletions(-) diff --git

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Steve, On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote: > v4l2_pipeline_inherit_controls() will add the v4l2 controls from > all subdev entities in a pipeline to a given video device. > > Signed-off-by: Steve Longerbeam > --- >

Re: [PATCH v4 14/36] [media] v4l2-mc: add a function to inherit controls from a pipeline

Hi Steve, On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote: > v4l2_pipeline_inherit_controls() will add the v4l2 controls from > all subdev entities in a pipeline to a given video device. > > Signed-off-by: Steve Longerbeam > --- > drivers/media/v4l2-core/v4l2-mc.c | 48 >

Re: [PATCH 2/2] dt-bindings: display: imx: entry for LAUSCR

On Mon, Feb 27, 2017 at 11:56:42AM +0100, Martin Kaiser wrote: > Allow setting the LCDC AUS Mode Control Register from the device tree. > This setting is optional, the register is available only on imx21 and > compatible chipsets. > > Signed-off-by: Martin Kaiser > --- >

Re: [PATCH 2/2] dt-bindings: display: imx: entry for LAUSCR

On Mon, Feb 27, 2017 at 11:56:42AM +0100, Martin Kaiser wrote: > Allow setting the LCDC AUS Mode Control Register from the device tree. > This setting is optional, the register is available only on imx21 and > compatible chipsets. > > Signed-off-by: Martin Kaiser > --- >

Re: [PATCH v2 2/3] printk: rename selected_console -> preferred_console

On (03/02/17 10:01), Steven Rostedt wrote: > > The variable selected_console is set in __add_preferred_console() > > to point to the last console parameter that was added to the > > console_cmdline array. > > > > Rename it to preferred_console so that the name reflects the usage. > > As I said

Re: [PATCH v2 2/3] printk: rename selected_console -> preferred_console

On (03/02/17 10:01), Steven Rostedt wrote: > > The variable selected_console is set in __add_preferred_console() > > to point to the last console parameter that was added to the > > console_cmdline array. > > > > Rename it to preferred_console so that the name reflects the usage. > > As I said

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Thu 02-03-17 09:01:01, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 07:57:35PM +0100, Michal Hocko wrote: > > On Wed 01-03-17 13:31:49, Johannes Weiner wrote: [...] > > > The error when reading a specific smaps should be completely ok. > > > > > > In numbers: even if your process is

Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps

On Thu 02-03-17 09:01:01, Johannes Weiner wrote: > On Wed, Mar 01, 2017 at 07:57:35PM +0100, Michal Hocko wrote: > > On Wed 01-03-17 13:31:49, Johannes Weiner wrote: [...] > > > The error when reading a specific smaps should be completely ok. > > > > > > In numbers: even if your process is

Re: [Outreachy kernel] [PATCH v2] staging: speakup: Comparison to NULL could be written

On Thu, Mar 02, 2017 at 02:13:02PM +0530, Arushi Singhal wrote: > Fixed coding style for null comparisons in speakup driver to be more > consistant with the rest of the kernel coding style. > > Signed-off-by: Arushi Singhal > --- > changes in v2 > - fixed

Re: [Outreachy kernel] [PATCH v2] staging: speakup: Comparison to NULL could be written

On Thu, Mar 02, 2017 at 02:13:02PM +0530, Arushi Singhal wrote: > Fixed coding style for null comparisons in speakup driver to be more > consistant with the rest of the kernel coding style. > > Signed-off-by: Arushi Singhal > --- > changes in v2 > - fixed coding style error and upto the coding

Re: [tpmdd-devel] [PATCH v2] tpm: Apply a sane minimum adapterlimit value for retransmission.

On 02/03/17 14:43, Peter Huewe wrote: > > > Am 2. März 2017 13:55:43 MEZ schrieb Jarkko Sakkinen > : >> On Wed, Mar 01, 2017 at 04:36:17PM +0100, Enric Balletbo i Serra wrote: >>> From: Bryan Freed >>> >>> When the I2C Infineon part is

Re: [tpmdd-devel] [PATCH v2] tpm: Apply a sane minimum adapterlimit value for retransmission.

On 02/03/17 14:43, Peter Huewe wrote: > > > Am 2. März 2017 13:55:43 MEZ schrieb Jarkko Sakkinen > : >> On Wed, Mar 01, 2017 at 04:36:17PM +0100, Enric Balletbo i Serra wrote: >>> From: Bryan Freed >>> >>> When the I2C Infineon part is attached to an I2C adapter that imposes >>> a size

Re: [PATCHv2 1/2] mfd: cpcap: implement irq sense helper

* Sebastian Reichel [170301 16:24]: > CPCAP can sense if IRQ is currently set or not. This > functionality is required for a few subdevices, such > as the power button and usb phy modules. > > Signed-off-by: Sebastian Reichel > --- > Changes since PATCHv1: > -

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

I've just realized that Darrick was not on the CC list. Let's add him. I believe this patch should go in in the current cycle because 5d17a73a2ebe was merged in this merge window and it can be abused... The other patch [1] is not that urgent. [1]

Re: [PATCHv2 1/2] mfd: cpcap: implement irq sense helper

* Sebastian Reichel [170301 16:24]: > CPCAP can sense if IRQ is currently set or not. This > functionality is required for a few subdevices, such > as the power button and usb phy modules. > > Signed-off-by: Sebastian Reichel > --- > Changes since PATCHv1: > - Newly introduced patch > --- >

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

I've just realized that Darrick was not on the CC list. Let's add him. I believe this patch should go in in the current cycle because 5d17a73a2ebe was merged in this merge window and it can be abused... The other patch [1] is not that urgent. [1]

Re: Problem with RSA test from testmgr

On 03/01/2017 10:21 PM, Corentin Labbe wrote: > I am finishing a patch that made testmgr test both (padded and unpadded). Even if you patch the test vectors there is no guarantee that a user of the API will always have the plain text padded. It can be anything between 1 and the key size. This

Re: Problem with RSA test from testmgr

On 03/01/2017 10:21 PM, Corentin Labbe wrote: > I am finishing a patch that made testmgr test both (padded and unpadded). Even if you patch the test vectors there is no guarantee that a user of the API will always have the plain text padded. It can be anything between 1 and the key size. This

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH 1/2] xfs: allow kmem_zalloc_greedy to fail

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH v3 2/2] crypto: vmx - Use skcipher for xts fallback

On Wed, Mar 01, 2017 at 11:00:00AM -0300, Paulo Flabiano Smorigo wrote: > Signed-off-by: Paulo Flabiano Smorigo Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key:

Re: [PATCH v3 2/2] crypto: vmx - Use skcipher for xts fallback

On Wed, Mar 01, 2017 at 11:00:00AM -0300, Paulo Flabiano Smorigo wrote: > Signed-off-by: Paulo Flabiano Smorigo Patch applied. Thanks. -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Re: Problem with RSA test from testmgr

Hi Stephan, On 03/01/2017 10:08 PM, Stephan Müller wrote: >> memset(ptextp, 0, 256); >> memcpy(ptextp + 64 - 8, ptext_ex, plen); > I actually have tested that and it did not return the data the kernel > implementation would return It did for me: Result 64 plen=8 63 1c cd 7b e1 7e e4 de

Re: Problem with RSA test from testmgr

Hi Stephan, On 03/01/2017 10:08 PM, Stephan Müller wrote: >> memset(ptextp, 0, 256); >> memcpy(ptextp + 64 - 8, ptext_ex, plen); > I actually have tested that and it did not return the data the kernel > implementation would return It did for me: Result 64 plen=8 63 1c cd 7b e1 7e e4 de

Re: [PATCH 2/2] ASoC: es7134: add dt-bindings for the es7134 dac

On Mon, Feb 27, 2017 at 04:47:24PM +0100, Jerome Brunet wrote: > Signed-off-by: Jerome Brunet > --- > Documentation/devicetree/bindings/sound/everest,es7134.txt | 10 ++ > 1 file changed, 10 insertions(+) > create mode 100644

Re: [PATCH 2/2] ASoC: es7134: add dt-bindings for the es7134 dac

On Mon, Feb 27, 2017 at 04:47:24PM +0100, Jerome Brunet wrote: > Signed-off-by: Jerome Brunet > --- > Documentation/devicetree/bindings/sound/everest,es7134.txt | 10 ++ > 1 file changed, 10 insertions(+) > create mode 100644 Documentation/devicetree/bindings/sound/everest,es7134.txt

Re: Kernel bio layer is sending bio size more than our block device is capable of handling

Please post your driver to the linux-block list, and test a recent kernel.

Re: Kernel bio layer is sending bio size more than our block device is capable of handling

Please post your driver to the linux-block list, and test a recent kernel.

[PATCH] Staging:wilc1000:linux_wlan: Modified the 'if-else' statement

Modified the 'if-else' statement to make it more readable. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/linux_wlan.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/staging/wilc1000/linux_wlan.c

[PATCH] Staging:wilc1000:linux_wlan: Modified the 'if-else' statement

Modified the 'if-else' statement to make it more readable. Signed-off-by: Georgios Emmanouil --- drivers/staging/wilc1000/linux_wlan.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c

Re: [PATCH v2 2/2] drm: bridge: Move HPD handling to PHY operations

Hi Neil, Thank you for the patch. On Thursday 02 Mar 2017 16:29:32 Neil Armstrong wrote: > The HDMI TX controller support HPD and RXSENSE signaling from the PHY > via it's STAT0 PHY interface, but some vendor PHYs can manage these > signals independently from the controller, thus these STAT0

Re: [PATCH v2 2/2] drm: bridge: Move HPD handling to PHY operations

Hi Neil, Thank you for the patch. On Thursday 02 Mar 2017 16:29:32 Neil Armstrong wrote: > The HDMI TX controller support HPD and RXSENSE signaling from the PHY > via it's STAT0 PHY interface, but some vendor PHYs can manage these > signals independently from the controller, thus these STAT0

Re: [PATCH 0/6] cpufreq: schedutil: fixes for flags updates

On 2 March 2017 at 16:45, Patrick Bellasi wrote: > The current version of schedutil has some issues related to the management > of update flags used by systems with frequency domains spawning multiple CPUs. > > Each time a CPU utilisation update is issued by the scheduler

Re: [PATCH 0/6] cpufreq: schedutil: fixes for flags updates

On 2 March 2017 at 16:45, Patrick Bellasi wrote: > The current version of schedutil has some issues related to the management > of update flags used by systems with frequency domains spawning multiple CPUs. > > Each time a CPU utilisation update is issued by the scheduler a set of flags > are

[PATCH 02/11] drm/meson: Add missing HDMI register

Add missing VPU HDMI register. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_registers.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/meson/meson_registers.h b/drivers/gpu/drm/meson/meson_registers.h index 6adf9c1..2847381 100644

[PATCH 02/11] drm/meson: Add missing HDMI register

Add missing VPU HDMI register. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_registers.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/meson/meson_registers.h b/drivers/gpu/drm/meson/meson_registers.h index 6adf9c1..2847381 100644 ---

[PATCH 01/11] drm/meson: Use crtc_state for hdisplay and fix atomic flush/enable sync for vsync commit

Clean the crtc_enable by using the proper crtc_state instead of the state of the primary plane state data. Also fix the dependency to commit the plane changes even if enable is called after the flush. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_crtc.c

[PATCH 01/11] drm/meson: Use crtc_state for hdisplay and fix atomic flush/enable sync for vsync commit

Clean the crtc_enable by using the proper crtc_state instead of the state of the primary plane state data. Also fix the dependency to commit the plane changes even if enable is called after the flush. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_crtc.c | 15 +++ 1

[RFC PATCH v2 11/32] x86: Unroll string I/O when SEV is active

From: Tom Lendacky Secure Encrypted Virtualization (SEV) does not support string I/O, so unroll the string I/O operation into a loop operating on one element at a time. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/io.h | 26

[RFC PATCH v2 11/32] x86: Unroll string I/O when SEV is active

From: Tom Lendacky Secure Encrypted Virtualization (SEV) does not support string I/O, so unroll the string I/O operation into a loop operating on one element at a time. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/io.h | 26 ++ 1 file changed, 22

RE: [PATCH V2] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT

> >Hi Bjorn, > >On 2/28/2017 1:57 PM, Patel, Mayurkumar wrote: >>> I was trying to figure out when to use saved values vs. the values in >>> registers by looking at the enable_cnt. >>> enable_cnt is 0 during boot on my system. >> enable_cnt for the root port on my system is set to 1 for "root

[PATCH 05/11] drm/meson: add support for HDMI clock support

This patchs adds support for the supported HDMI modes clocks frequencies. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_vclk.c | 624 +++- drivers/gpu/drm/meson/meson_vclk.h | 6 +-

RE: [PATCH V2] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT

> >Hi Bjorn, > >On 2/28/2017 1:57 PM, Patel, Mayurkumar wrote: >>> I was trying to figure out when to use saved values vs. the values in >>> registers by looking at the enable_cnt. >>> enable_cnt is 0 during boot on my system. >> enable_cnt for the root port on my system is set to 1 for "root

[PATCH 05/11] drm/meson: add support for HDMI clock support

This patchs adds support for the supported HDMI modes clocks frequencies. Signed-off-by: Neil Armstrong --- drivers/gpu/drm/meson/meson_vclk.c | 624 +++- drivers/gpu/drm/meson/meson_vclk.h | 6 +- drivers/gpu/drm/meson/meson_venc_cvbs.c | 9 +- 3 files

<    5   6   7   8   9   10   11   12   13   14   >