Re: staging: ks7010: Delete unnecessary uses of the variable "retval"

> Do you find such a source code transformation useful? No. I already gave that answer by agreeing to Julia's viewpoint. signature.asc Description: PGP signature

Re: staging: ks7010: Delete unnecessary uses of the variable "retval"

> Do you find such a source code transformation useful? No. I already gave that answer by agreeing to Julia's viewpoint. signature.asc Description: PGP signature

Re: [V2, 2/2] crypto: vmx - Convert to CPU feature based module autoloading

On Tue, 2016-19-07 at 04:03:53 UTC, Alastair D'Silva wrote: > From: Alastair D'Silva > > This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure > to automatically load the vmx_crypto module if the CPU supports > it. > > Signed-off-by: Alastair D'Silva

Re: [V2, 2/2] crypto: vmx - Convert to CPU feature based module autoloading

On Tue, 2016-19-07 at 04:03:53 UTC, Alastair D'Silva wrote: > From: Alastair D'Silva > > This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure > to automatically load the vmx_crypto module if the CPU supports > it. > > Signed-off-by: Alastair D'Silva Applied to powerpc next, thanks.

Re: [V2,1/2] powerpc: Add module autoloading based on CPU features

On Tue, 2016-19-07 at 04:03:52 UTC, Alastair D'Silva wrote: > From: Alastair D'Silva > > This patch provides the necessary infrastructure to allow drivers > to be automatically loaded via UDEV. It implements the minimum > required to be able to use module_cpu_feature_match

Re: [V2,1/2] powerpc: Add module autoloading based on CPU features

On Tue, 2016-19-07 at 04:03:52 UTC, Alastair D'Silva wrote: > From: Alastair D'Silva > > This patch provides the necessary infrastructure to allow drivers > to be automatically loaded via UDEV. It implements the minimum > required to be able to use module_cpu_feature_match to trigger > the

Re: [1/1] powerpc/mm: Add memory barrier in __hugepte_alloc()

On Tue, 2016-05-04 at 19:05:47 UTC, Sukadev Bhattiprolu wrote: > >From f7b73c6b4508fe9b141a43d92be2f9dd7d3c4a58 Mon Sep 17 00:00:00 2001 > From: Sukadev Bhattiprolu > Date: Thu, 24 Mar 2016 02:07:57 -0400 > Subject: [PATCH 1/1] powerpc/mm: Add memory barrier in

Re: [1/1] powerpc/mm: Add memory barrier in __hugepte_alloc()

On Tue, 2016-05-04 at 19:05:47 UTC, Sukadev Bhattiprolu wrote: > >From f7b73c6b4508fe9b141a43d92be2f9dd7d3c4a58 Mon Sep 17 00:00:00 2001 > From: Sukadev Bhattiprolu > Date: Thu, 24 Mar 2016 02:07:57 -0400 > Subject: [PATCH 1/1] powerpc/mm: Add memory barrier in __hugepte_alloc() > >

Re: [Intel-gfx] [Announcement] 2016-Q2 release of XenGT - a Mediated Graphics Passthrough Solution from Intel

Hi all, We are pleased to announce another update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel Graphics processors. A virtual GPU instance is maintained for each VM, with

Re: [Intel-gfx] [Announcement] 2016-Q2 release of XenGT - a Mediated Graphics Passthrough Solution from Intel

Hi all, We are pleased to announce another update of Intel GVT-g for Xen. Intel GVT-g is a full GPU virtualization solution with mediated pass-through, starting from 4th generation Intel Core(TM) processors with Intel Graphics processors. A virtual GPU instance is maintained for each VM, with

4.7.0-rc7+: Oops during boot with USB pen drive inserted

Hi, With Linus' latest and greatest, I get an opps when I boot my laptop with a pen drive inserted in any USB port. The oops message is: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) The oops seems to be 100% repeatable. If a USB pen drive is not inserted, the

4.7.0-rc7+: Oops during boot with USB pen drive inserted

Hi, With Linus' latest and greatest, I get an opps when I boot my laptop with a pen drive inserted in any USB port. The oops message is: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) The oops seems to be 100% repeatable. If a USB pen drive is not inserted, the

Re: [PATCH 3/4] media: Add Mediatek MDP Driver

On Mon, 2016-07-18 at 14:18 +0200, Hans Verkuil wrote: > On 07/14/2016 02:18 PM, Minghsiu Tsai wrote: > > Add MDP driver for MT8173 > > > > Signed-off-by: Minghsiu Tsai > > --- > > drivers/media/platform/Kconfig| 16 + > >

Re: [PATCH 3/4] media: Add Mediatek MDP Driver

On Mon, 2016-07-18 at 14:18 +0200, Hans Verkuil wrote: > On 07/14/2016 02:18 PM, Minghsiu Tsai wrote: > > Add MDP driver for MT8173 > > > > Signed-off-by: Minghsiu Tsai > > --- > > drivers/media/platform/Kconfig| 16 + > > drivers/media/platform/Makefile |2 +

Re: [PATCH] powernv: Use __printf in pe_level_printk

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160721] [cannot apply to powerpc/next] [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/Joe-Perches/powernv-Use-__printf

Re: [PATCH] powernv: Use __printf in pe_level_printk

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160721] [cannot apply to powerpc/next] [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/Joe-Perches/powernv-Use-__printf

Re: [kernel-hardening] [PATCH v5 03/32] x86/cpa: In populate_pgd, don't set the pgd entry until it's populated

On 07/21/2016 09:43 PM, valdis.kletni...@vt.edu wrote: On Mon, 11 Jul 2016 13:53:36 -0700, Andy Lutomirski said: This avoids pointless races in which another CPU or task might see a partially populated global pgd entry. These races should normally be harmless, but, if another CPU propagates

Re: [kernel-hardening] [PATCH v5 03/32] x86/cpa: In populate_pgd, don't set the pgd entry until it's populated

On 07/21/2016 09:43 PM, valdis.kletni...@vt.edu wrote: On Mon, 11 Jul 2016 13:53:36 -0700, Andy Lutomirski said: This avoids pointless races in which another CPU or task might see a partially populated global pgd entry. These races should normally be harmless, but, if another CPU propagates

[PATCH v2] iio: humidity: hdc100x: add triggered buffer support for HDC100X

Triggered buffer support uses the HDC100X's dual acquisition mode to read both humidity and temperature in one shot. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- Changes in v2: Thanks for the review Peter - switched endianness from

[PATCH v2] iio: humidity: hdc100x: add triggered buffer support for HDC100X

Triggered buffer support uses the HDC100X's dual acquisition mode to read both humidity and temperature in one shot. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- Changes in v2: Thanks for the review Peter - switched endianness from IIO_CPU to IIO_BE - use only one buffer in the

Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template

On 2016年07月14日 05:07, Yaniv Machani wrote: + + /* if channel width is 20MHz - configure HT capab accordingly*/ + if (sdata->vif.bss_conf.chandef.width == NL80211_CHAN_WIDTH_20) { + cap &= ~IEEE80211_HT_CAP_SUP_WIDTH_20_40; + cap &=

Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template

On 2016年07月14日 05:07, Yaniv Machani wrote: + + /* if channel width is 20MHz - configure HT capab accordingly*/ + if (sdata->vif.bss_conf.chandef.width == NL80211_CHAN_WIDTH_20) { + cap &= ~IEEE80211_HT_CAP_SUP_WIDTH_20_40; + cap &=

Re: [PATCH v6 0/2] [media] atmel-isc: add driver for Atmel ISC

On 7/21/2016 16:41, Hans Verkuil wrote: On 07/21/2016 10:14 AM, Songjun Wu wrote: The Image Sensor Controller driver includes two parts. 1) Driver code to implement the ISC function. 2) Device tree binding documentation, it describes how to add the ISC in device tree. Test result with

Re: [PATCH v6 0/2] [media] atmel-isc: add driver for Atmel ISC

On 7/21/2016 16:41, Hans Verkuil wrote: On 07/21/2016 10:14 AM, Songjun Wu wrote: The Image Sensor Controller driver includes two parts. 1) Driver code to implement the ISC function. 2) Device tree binding documentation, it describes how to add the ISC in device tree. Test result with

Re: [PATCH v6 1/2] [media] atmel-isc: add the Image Sensor Controller code

On 7/21/2016 17:13, Hans Verkuil wrote: On 07/21/2016 10:14 AM, Songjun Wu wrote: Add driver for the Image Sensor Controller. It manages incoming data from a parallel based CMOS/CCD sensor. It has an internal image processor, also integrates a triple channel direct memory access controller

Re: [PATCH v6 1/2] [media] atmel-isc: add the Image Sensor Controller code

On 7/21/2016 17:13, Hans Verkuil wrote: On 07/21/2016 10:14 AM, Songjun Wu wrote: Add driver for the Image Sensor Controller. It manages incoming data from a parallel based CMOS/CCD sensor. It has an internal image processor, also integrates a triple channel direct memory access controller

Re: [PATCH 19/19] x86/dumpstack: print any pt_regs found on the stack

On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote: > On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote: >> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote: >> > Now that we can find pt_regs registers in the middle of the stack due

Re: [PATCH 19/19] x86/dumpstack: print any pt_regs found on the stack

On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote: > On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote: >> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote: >> > Now that we can find pt_regs registers in the middle of the stack due to >> > an interrupt or exception, we can

Re: [kernel-hardening] [PATCH v5 03/32] x86/cpa: In populate_pgd, don't set the pgd entry until it's populated

On Mon, 11 Jul 2016 13:53:36 -0700, Andy Lutomirski said: > This avoids pointless races in which another CPU or task might see a > partially populated global pgd entry. These races should normally > be harmless, but, if another CPU propagates the entry via > vmalloc_fault and then populate_pgd

Re: [kernel-hardening] [PATCH v5 03/32] x86/cpa: In populate_pgd, don't set the pgd entry until it's populated

On Mon, 11 Jul 2016 13:53:36 -0700, Andy Lutomirski said: > This avoids pointless races in which another CPU or task might see a > partially populated global pgd entry. These races should normally > be harmless, but, if another CPU propagates the entry via > vmalloc_fault and then populate_pgd

Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control method lid device restrictions

Hi Lv, On Fri, Jul 22, 2016 at 12:24:50AM +, Zheng, Lv wrote: > Hi, Dmitry > > > Thanks for the review. > > > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > > Subject: Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control > > method lid device restrictions > > > > On

Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control method lid device restrictions

Hi Lv, On Fri, Jul 22, 2016 at 12:24:50AM +, Zheng, Lv wrote: > Hi, Dmitry > > > Thanks for the review. > > > From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com] > > Subject: Re: [PATCH v4 2/2] ACPI / button: Add document for ACPI control > > method lid device restrictions > > > > On

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 05:14:33PM +0300, Pantelis Antoniou wrote: > Hi David, > > > On Jul 21, 2016, at 16:42 , David Gibson > > wrote: > > > > On Wed, Jul 20, 2016 at 11:59:44PM +0300, Pantelis Antoniou wrote: > >> Hi David, > >> > >> Spent some time looking at

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 05:14:33PM +0300, Pantelis Antoniou wrote: > Hi David, > > > On Jul 21, 2016, at 16:42 , David Gibson > > wrote: > > > > On Wed, Jul 20, 2016 at 11:59:44PM +0300, Pantelis Antoniou wrote: > >> Hi David, > >> > >> Spent some time looking at this, and it looks like it’s

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 02:09:18PM -0500, Rob Herring wrote: > On Thu, Jul 21, 2016 at 9:14 AM, Pantelis Antoniou > wrote: > > Hi David, > > > >> On Jul 21, 2016, at 16:42 , David Gibson > >> wrote: > >> > >> On Wed, Jul 20, 2016 at

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 02:09:18PM -0500, Rob Herring wrote: > On Thu, Jul 21, 2016 at 9:14 AM, Pantelis Antoniou > wrote: > > Hi David, > > > >> On Jul 21, 2016, at 16:42 , David Gibson > >> wrote: > >> > >> On Wed, Jul 20, 2016 at 11:59:44PM +0300, Pantelis Antoniou wrote: > >>> Hi David, >

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 02:15:57PM -0500, Rob Herring wrote: > On Mon, Jul 18, 2016 at 9:20 AM, David Gibson > wrote: > > Hi, > > > > Here's some of my thoughts on how a connector format for the DT could > > be done. Sorry it's taken longer than I hoped - I've been

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 02:15:57PM -0500, Rob Herring wrote: > On Mon, Jul 18, 2016 at 9:20 AM, David Gibson > wrote: > > Hi, > > > > Here's some of my thoughts on how a connector format for the DT could > > be done. Sorry it's taken longer than I hoped - I've been pretty > > swamped in my day

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 10:15:36PM +0300, Pantelis Antoniou wrote: > Hi Rob, > > > On Jul 21, 2016, at 22:09 , Rob Herring wrote: > > > > On Thu, Jul 21, 2016 at 9:14 AM, Pantelis Antoniou > > wrote: > >> Hi David, > >> > >>> On Jul 21,

Re: DT connectors, thoughts

On Thu, Jul 21, 2016 at 10:15:36PM +0300, Pantelis Antoniou wrote: > Hi Rob, > > > On Jul 21, 2016, at 22:09 , Rob Herring wrote: > > > > On Thu, Jul 21, 2016 at 9:14 AM, Pantelis Antoniou > > wrote: > >> Hi David, > >> > >>> On Jul 21, 2016, at 16:42 , David Gibson > >>> wrote: > >>> >

Re: [PATCH v5 3/3] arm: dts: mt2701: Add auxadc node.

05969.html --- I will add this information in next version commit message. > Hi, > > [auto build test ERROR on robh/for-next] > [also build test ERROR on v4.7-rc7 next-20160721] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the s

Re: [PATCH v5 3/3] arm: dts: mt2701: Add auxadc node.

05969.html --- I will add this information in next version commit message. > Hi, > > [auto build test ERROR on robh/for-next] > [also build test ERROR on v4.7-rc7 next-20160721] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the s

Re: Question about group scheduler cpu shares

On Thu, 2016-07-21 at 20:24 -0700, Gaurav Poothia wrote: (top posting.. naught naughty;) > 1.What is the function that translates from various nice levels to > weight i.e. nice(0) == 1024 how to translate for other levels If you rummage around in kernel/sched, you'll find this table: const int

Re: Question about group scheduler cpu shares

On Thu, 2016-07-21 at 20:24 -0700, Gaurav Poothia wrote: (top posting.. naught naughty;) > 1.What is the function that translates from various nice levels to > weight i.e. nice(0) == 1024 how to translate for other levels If you rummage around in kernel/sched, you'll find this table: const int

[PATCH v3 1/3] ACPI / debugger: Add kernel flushing support

This patch adds debugger log flushing support in kernel via .ioctl() callback. The in-kernel flushing is more efficient, because it reduces useless log IOs by bypassing log user_read/kern_write during the flush period. Signed-off-by: Lv Zheng Cc: linux-...@vger.kernel.org ---

[PATCH v3 3/3] tools/power/acpi/acpidbg: Add multi-commands support in batch mode

This patch adds multi-commands support for the batch mode. The same mode can be seen in acpiexec. However people may think this is not useful for an in-kernel debugger, because the in-kernel debugger is always running, never exits. So we can run another command by running another acpidbg batch

[PATCH v3 1/3] ACPI / debugger: Add kernel flushing support

This patch adds debugger log flushing support in kernel via .ioctl() callback. The in-kernel flushing is more efficient, because it reduces useless log IOs by bypassing log user_read/kern_write during the flush period. Signed-off-by: Lv Zheng Cc: linux-...@vger.kernel.org ---

[PATCH v3 3/3] tools/power/acpi/acpidbg: Add multi-commands support in batch mode

This patch adds multi-commands support for the batch mode. The same mode can be seen in acpiexec. However people may think this is not useful for an in-kernel debugger, because the in-kernel debugger is always running, never exits. So we can run another command by running another acpidbg batch

[PATCH v3 2/3] tools/power/acpi/acpidbg: Use new flushing mechanism

This patch converts tools/power/acpi/tools/acpidbg/acpidbg to use the new flushing mechanism. Signed-off-by: Lv Zheng --- tools/power/acpi/tools/acpidbg/acpidbg.c | 51 -- 1 file changed, 7 insertions(+), 44 deletions(-) diff --git

[PATCH v3 2/3] tools/power/acpi/acpidbg: Use new flushing mechanism

This patch converts tools/power/acpi/tools/acpidbg/acpidbg to use the new flushing mechanism. Signed-off-by: Lv Zheng --- tools/power/acpi/tools/acpidbg/acpidbg.c | 51 -- 1 file changed, 7 insertions(+), 44 deletions(-) diff --git

[PATCH v3 0/3] ACPI / debugger: Add kernel flushing support

AML debugger is implemented in the kernel as a character device located in the debugfs. Currently, when its batch mode is used, the userspace tool needs to flush the logs/prompts remained in the kernel output buffer, this is implemented in an inefficient way in the userspace by polling the IO and

[PATCH v3 0/3] ACPI / debugger: Add kernel flushing support

AML debugger is implemented in the kernel as a character device located in the debugfs. Currently, when its batch mode is used, the userspace tool needs to flush the logs/prompts remained in the kernel output buffer, this is implemented in an inefficient way in the userspace by polling the IO and

[PATCH 56/58] staging: lustre: move ioctls to lustre_ioctl.h

From: John L. Hammond Move ioctl definitions and related functions from lustre_dlm.h, lustre_lib.h, obd.h, to lustre_ioctl.h. Replace the definitions of retired ioctls with comment. Signed-off-by: John L. Hammond Intel-bug-id:

[PATCH 56/58] staging: lustre: move ioctls to lustre_ioctl.h

From: John L. Hammond Move ioctl definitions and related functions from lustre_dlm.h, lustre_lib.h, obd.h, to lustre_ioctl.h. Replace the definitions of retired ioctls with comment. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4961 Reviewed-on:

[PATCH 54/58] staging: lustre: reorder LOV_MAGIC_* definition

From: Fan Yong Since all the LOV_MAGIC_* definitions have the same postfix values break that value out into its own definition. With this we can check whether the magic's postfix match the LOV_MAGIC_MAGIC or not: if yes, then it is quite possible that the clients has

[PATCH 54/58] staging: lustre: reorder LOV_MAGIC_* definition

From: Fan Yong Since all the LOV_MAGIC_* definitions have the same postfix values break that value out into its own definition. With this we can check whether the magic's postfix match the LOV_MAGIC_MAGIC or not: if yes, then it is quite possible that the clients has encountered an newer LOV

[PATCH 58/58] staging: lustre: ptlrpc: Early replies need to honor at_max

From: Chris Horn When determining whether an early reply can be sent the server will calculate the new deadline based on an offset from the request arrival time. However, when actually setting the new deadline the server offsets the current time. This can result in deadlines

[PATCH 57/58] staging: lustre: llite: add error handler in inode prepare phase

From: wang di Add error handler during inode inialization, so inode will become bad inode if something bad happens during inode prepare phase, otherwise the striped directory will not get its layout and being mis-regarded as normal directory. Signed-off-by: wang di

[PATCH 58/58] staging: lustre: ptlrpc: Early replies need to honor at_max

From: Chris Horn When determining whether an early reply can be sent the server will calculate the new deadline based on an offset from the request arrival time. However, when actually setting the new deadline the server offsets the current time. This can result in deadlines being extended more

[PATCH 57/58] staging: lustre: llite: add error handler in inode prepare phase

From: wang di Add error handler during inode inialization, so inode will become bad inode if something bad happens during inode prepare phase, otherwise the striped directory will not get its layout and being mis-regarded as normal directory. Signed-off-by: wang di Intel-bug-id:

[PATCH 52/58] staging: lustre: lmv: rename request to preq in lmv_getattr_name()

From: John L. Hammond Rename request to preq. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on: http://review.whamcloud.com/9863 Reviewed-by: Nathaniel Clark

[PATCH 52/58] staging: lustre: lmv: rename request to preq in lmv_getattr_name()

From: John L. Hammond Rename request to preq. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on: http://review.whamcloud.com/9863 Reviewed-by: Nathaniel Clark Reviewed-by: Bob Glossman Reviewed-by: Oleg Drokin Signed-off-by: James Simmons

[PATCH 51/58] staging: lustre: lmv: cleanup req in lmv_getattr_name()

From: John L. Hammond In lmv_getattr_name() don't return a freed request in the error path. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on: http://review.whamcloud.com/9863 Reviewed-by:

[PATCH 51/58] staging: lustre: lmv: cleanup req in lmv_getattr_name()

From: John L. Hammond In lmv_getattr_name() don't return a freed request in the error path. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on: http://review.whamcloud.com/9863 Reviewed-by: Nathaniel Clark Reviewed-by: Bob Glossman

[PATCH 55/58] staging: lustre: ldlm: flock completion fixes.

From: Vitaly Fertman Move checks for FAILED, DESTROYED flags under ldlm spinlock, destroy flock atomically with the check it is not destroyed yet. Do not put the granted flock into the resource if this is UNLOCK, TEST, or DEADLOCK'ed flock. Later a regression for

[PATCH 55/58] staging: lustre: ldlm: flock completion fixes.

From: Vitaly Fertman Move checks for FAILED, DESTROYED flags under ldlm spinlock, destroy flock atomically with the check it is not destroyed yet. Do not put the granted flock into the resource if this is UNLOCK, TEST, or DEADLOCK'ed flock. Later a regression for this patch was reported under

Re: [PATCH] vfs:Fix memory leak on error path in get_empty_file

On Thu, Jul 21, 2016 at 10:53:37PM -0400, Nicholas Krause wrote: > This fixes a memory leak on the error path if the call to > security_file_alloc fails to run successfully as detected > in this trace by kmemleak: > [ 321.783718] ath9k :03:00.0 eth0: renamed from wlan0 > [ 330.960024] atl1c

Re: [PATCH] vfs:Fix memory leak on error path in get_empty_file

On Thu, Jul 21, 2016 at 10:53:37PM -0400, Nicholas Krause wrote: > This fixes a memory leak on the error path if the call to > security_file_alloc fails to run successfully as detected > in this trace by kmemleak: > [ 321.783718] ath9k :03:00.0 eth0: renamed from wlan0 > [ 330.960024] atl1c

[PATCH 45/58] staging: lustre: simplify inline functions in lustre_fid.h

From: John L. Hammond Several inline functions return a structure that was passed in. Their is no need for this so just make these function void. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on:

[PATCH 45/58] staging: lustre: simplify inline functions in lustre_fid.h

From: John L. Hammond Several inline functions return a structure that was passed in. Their is no need for this so just make these function void. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641 Reviewed-by:

[PATCH 47/58] staging: lustre: lmv: lookup remote migrating object in LMV

From: wang di If remote object is being found in a migrating directory, it should continue to lookup the object in remote MDT, instead of return. Signed-off-by: wang di Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4805 Reviewed-on:

[PATCH 47/58] staging: lustre: lmv: lookup remote migrating object in LMV

From: wang di If remote object is being found in a migrating directory, it should continue to lookup the object in remote MDT, instead of return. Signed-off-by: wang di Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4805 Reviewed-on: http://review.whamcloud.com/9806 Reviewed-by: John L.

[PATCH 53/58] staging: lustre: obdclass: unified flow control interfaces

From: Fan Yong Unify the flow control interfaces for MDC RPC and FLD RPC. We allow to adjust the maximum inflight RPCs count via /sys interface. Signed-off-by: Fan Yong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4687 Reviewed-on:

[PATCH 48/58] staging: lustre: lmv: Ensure lmv_intent_lookup cleans up reqp

From: Nathaniel Clark Ensure there aren't invalid pointers hanging around after ptlrpc_req_finished is called. Signed-off-by: Nathaniel Clark Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on:

[PATCH 48/58] staging: lustre: lmv: Ensure lmv_intent_lookup cleans up reqp

From: Nathaniel Clark Ensure there aren't invalid pointers hanging around after ptlrpc_req_finished is called. Signed-off-by: Nathaniel Clark Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4826 Reviewed-on: http://review.whamcloud.com/9841 Reviewed-by: John L. Hammond Reviewed-by: Bob

[PATCH 53/58] staging: lustre: obdclass: unified flow control interfaces

From: Fan Yong Unify the flow control interfaces for MDC RPC and FLD RPC. We allow to adjust the maximum inflight RPCs count via /sys interface. Signed-off-by: Fan Yong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4687 Reviewed-on: http://review.whamcloud.com/9562 Reviewed-by: Niu Yawei

[PATCH 50/58] staging: lustre: lov: handle the case of stripe size is not power 2

From: Jinshan Xiong Calculate the end of current stripe correctly when the stripe size is not power 2. Signed-off-by: Jinshan Xiong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4860 Reviewed-on: http://review.whamcloud.com/9882

[PATCH 50/58] staging: lustre: lov: handle the case of stripe size is not power 2

From: Jinshan Xiong Calculate the end of current stripe correctly when the stripe size is not power 2. Signed-off-by: Jinshan Xiong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4860 Reviewed-on: http://review.whamcloud.com/9882 Reviewed-by: Bobi Jam Reviewed-by: Oleg Drokin

[PATCH 49/58] staging: lustre: llite: avoid a deadlock in page write

From: Jinshan Xiong For a partial page write, it will have to issue a READ RPC firstly to get a full uptodate page. If another page is already locked by this thread it can easily cause deadlock. Signed-off-by: Jinshan Xiong Intel-bug-id:

[PATCH 49/58] staging: lustre: llite: avoid a deadlock in page write

From: Jinshan Xiong For a partial page write, it will have to issue a READ RPC firstly to get a full uptodate page. If another page is already locked by this thread it can easily cause deadlock. Signed-off-by: Jinshan Xiong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4873 Reviewed-on:

[PATCH 42/58] staging: lustre: don't need to const __u64 parameters for lustre_idl.h

From: John L. Hammond Remove the const for the __u64 parameters for inline functions in lustre_idl.h. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641

[PATCH 42/58] staging: lustre: don't need to const __u64 parameters for lustre_idl.h

From: John L. Hammond Remove the const for the __u64 parameters for inline functions in lustre_idl.h. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641 Reviewed-by: wangdi Reviewed-by: Fan Yong Reviewed-by:

[PATCH 39/58] staging: lustre: osc: allow to call brw_commit() multiple times

From: Jinshan Xiong Sometimes the rq_commit_cb of BRW RPC can be called twice if that RPC has already committed at reply time. This will cause inaccuracy of unstable pages accounting and then assertion. Signed-off-by: Jinshan Xiong

[PATCH 39/58] staging: lustre: osc: allow to call brw_commit() multiple times

From: Jinshan Xiong Sometimes the rq_commit_cb of BRW RPC can be called twice if that RPC has already committed at reply time. This will cause inaccuracy of unstable pages accounting and then assertion. Signed-off-by: Jinshan Xiong Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3274

[PATCH 46/58] staging: lustre: lmv: access lum_stripe_offset as little endian

From: John L. Hammond By the time that a struct lmv_user_md reaches lmv_placement_policy() it has already been converted to little endian. Therefore use the appropriate macros around accesses to this this field. This issue was found by rewriting the definition of struct

[PATCH 44/58] staging: lustre: use bool for several function in lustre_idl.h/lustre_fid.h

From: John L. Hammond Change the return type of several predicate functions from int to bool. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641 Reviewed-by:

[PATCH 37/58] staging: lustre: libcfs: Only dump log once per sec. to avoid EEXIST

From: Ryan Haasken Since the log file name contains the current time in seconds, dumping the logs more than once per second causes EEXIST errors to be emitted. Add a static variable to libcfs_debug_dumplog_internal that records the time of the last Lustre log dump. If the

[PATCH 46/58] staging: lustre: lmv: access lum_stripe_offset as little endian

From: John L. Hammond By the time that a struct lmv_user_md reaches lmv_placement_policy() it has already been converted to little endian. Therefore use the appropriate macros around accesses to this this field. This issue was found by rewriting the definition of struct lmv_user_md to use the

[PATCH 44/58] staging: lustre: use bool for several function in lustre_idl.h/lustre_fid.h

From: John L. Hammond Change the return type of several predicate functions from int to bool. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641 Reviewed-by: wangdi Reviewed-by: Fan Yong Reviewed-by: Oleg

[PATCH 37/58] staging: lustre: libcfs: Only dump log once per sec. to avoid EEXIST

From: Ryan Haasken Since the log file name contains the current time in seconds, dumping the logs more than once per second causes EEXIST errors to be emitted. Add a static variable to libcfs_debug_dumplog_internal that records the time of the last Lustre log dump. If the current time in

[PATCH] update sc->nr_reclaimed after each shrink_slab

In !global_reclaim(sc) case, we should update sc->nr_reclaimed after each shrink_slab in the loop. Because we need the correct sc->nr_reclaimed value to see if we can break out. Signed-off-by: Zhou Chengming --- mm/vmscan.c |5 + 1 files changed, 5

[PATCH] update sc->nr_reclaimed after each shrink_slab

In !global_reclaim(sc) case, we should update sc->nr_reclaimed after each shrink_slab in the loop. Because we need the correct sc->nr_reclaimed value to see if we can break out. Signed-off-by: Zhou Chengming --- mm/vmscan.c |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff

[PATCH 40/58] staging: lustre: llite: a few fixes for migration.

From: wang di 1. Clear the client dentry cache before migrating file/directory to the remote MDT. 2. Do not return stripe information to client, if it did not get the layout lock. Signed-off-by: wang di Intel-bug-id:

[PATCH 40/58] staging: lustre: llite: a few fixes for migration.

From: wang di 1. Clear the client dentry cache before migrating file/directory to the remote MDT. 2. Do not return stripe information to client, if it did not get the layout lock. Signed-off-by: wang di Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4682 Reviewed-on:

[PATCH 41/58] staging: lustre: mdc: fixup MDS_SWAP_LAYOUTS ELC handling

From: John L. Hammond In mdc_ioc_swap_layouts() cancel *any* unused locks with LAYOUT or XATTR IBITS set on the two files. (This matches the locks acquired in mdt_swap_layouts(). Previously only locks that conflicted with a CR LAYOUT lock were cancelled.) Signed-off-by:

[PATCH 43/58] staging: lustre: const correct FID/OSTID/... helpers

From: John L. Hammond Add a const qualifier wherever possible to the pointer parameters of the inline helper functions in lustre_idl.h and lustre_fid.h. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675

[PATCH 41/58] staging: lustre: mdc: fixup MDS_SWAP_LAYOUTS ELC handling

From: John L. Hammond In mdc_ioc_swap_layouts() cancel *any* unused locks with LAYOUT or XATTR IBITS set on the two files. (This matches the locks acquired in mdt_swap_layouts(). Previously only locks that conflicted with a CR LAYOUT lock were cancelled.) Signed-off-by: John L. Hammond

[PATCH 43/58] staging: lustre: const correct FID/OSTID/... helpers

From: John L. Hammond Add a const qualifier wherever possible to the pointer parameters of the inline helper functions in lustre_idl.h and lustre_fid.h. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2675 Reviewed-on: http://review.whamcloud.com/8641

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

On Fri, Jul 22, 2016 at 09:23:02AM +1000, Stephen Rothwell wrote: > Hi Arnaldo, > > On Thu, 21 Jul 2016 10:12:48 -0300 Arnaldo Carvalho de Melo > wrote: > > > > Em Thu, Jul 21, 2016 at 09:29:50AM +1000, Stephen Rothwell escreveu: > > > Hi Arnaldo, > > > > > > On Tue, 19 Jul

Re: [PATCH/RFC] Re: linux-next: build failure after merge of the luto-misc tree

On Fri, Jul 22, 2016 at 09:23:02AM +1000, Stephen Rothwell wrote: > Hi Arnaldo, > > On Thu, 21 Jul 2016 10:12:48 -0300 Arnaldo Carvalho de Melo > wrote: > > > > Em Thu, Jul 21, 2016 at 09:29:50AM +1000, Stephen Rothwell escreveu: > > > Hi Arnaldo, > > > > > > On Tue, 19 Jul 2016 23:52:02 -0300

  1   2   3   4   5   6   7   8   9   10   >