Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 16, 2016 at 03:22:41PM -0700, Jaegeuk Kim wrote: > > Sorry, I just ran out of time to try to verify that the patch wouldn't > > break anything, and given that we're going to need to wait for > > "fscrypto/f2fs: allow fs-specific key prefix for fs encryption" to go > > upstream. > >

Re: [PATCH v2 0/3] input: rmi4: Regulator supply support

On 05/13/2016 03:29 PM, Bjorn Andersson wrote: On Thu 12 May 17:52 PDT 2016, Andrew Duggan wrote: On 05/11/2016 08:05 PM, Bjorn Andersson wrote: On Wed 11 May 16:30 PDT 2016, Andrew Duggan wrote: Hi Bjorn, On 05/10/2016 08:49 AM, Bjorn Andersson wrote: [..] So either we duplicate the

Re: [PATCH v2 0/3] input: rmi4: Regulator supply support

On 05/13/2016 03:29 PM, Bjorn Andersson wrote: On Thu 12 May 17:52 PDT 2016, Andrew Duggan wrote: On 05/11/2016 08:05 PM, Bjorn Andersson wrote: On Wed 11 May 16:30 PDT 2016, Andrew Duggan wrote: Hi Bjorn, On 05/10/2016 08:49 AM, Bjorn Andersson wrote: [..] So either we duplicate the

Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 16, 2016 at 03:22:41PM -0700, Jaegeuk Kim wrote: > > Sorry, I just ran out of time to try to verify that the patch wouldn't > > break anything, and given that we're going to need to wait for > > "fscrypto/f2fs: allow fs-specific key prefix for fs encryption" to go > > upstream. > >

Re: [PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

On 5/16/2016 4:45 PM, Z Lim wrote: Hi Yang, On Mon, May 16, 2016 at 4:09 PM, Yang Shi wrote: In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and

Re: [PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

On 5/16/2016 4:45 PM, Z Lim wrote: Hi Yang, On Mon, May 16, 2016 at 4:09 PM, Yang Shi wrote: In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and epilogue. The latest blinding

Re: [PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

Hi Yang, On Mon, May 16, 2016 at 4:09 PM, Yang Shi wrote: > In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for > tmp registers, which are callee-saved registers. This leads to variable size > of JIT prologue and epilogue. The latest blinding constant

Re: [PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

Hi Yang, On Mon, May 16, 2016 at 4:09 PM, Yang Shi wrote: > In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for > tmp registers, which are callee-saved registers. This leads to variable size > of JIT prologue and epilogue. The latest blinding constant change prefers to >

Re: [PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

On Mon, May 2, 2016 at 09:19 PM, Al Stone wrote: > On 04/25/2016 03:21 PM, Al Stone wrote: > > The ACPI 6.1 specification was recently released at the end of January > > 2016, but the arm64 kernel documentation for the use of ACPI was written > > for the 5.1 version of the spec. There were

Re: [PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

On Mon, May 2, 2016 at 09:19 PM, Al Stone wrote: > On 04/25/2016 03:21 PM, Al Stone wrote: > > The ACPI 6.1 specification was recently released at the end of January > > 2016, but the arm64 kernel documentation for the use of ACPI was written > > for the 5.1 version of the spec. There were

Re: [v4,1/1] powerpc/86xx: Add support for Emerson/Artesyn MVME7100

On Wed, Apr 27, 2016 at 10:35:25AM +0200, Alessio Igor Bogani wrote: > + bcsr@4,0 { > + compatible = "artesyn,mvme7100-bcsr"; > + reg = <4 0 0x1>; > + }; > + > +serial@5,1000 { > + cell-index = <2>;

Re: [v4,1/1] powerpc/86xx: Add support for Emerson/Artesyn MVME7100

On Wed, Apr 27, 2016 at 10:35:25AM +0200, Alessio Igor Bogani wrote: > + bcsr@4,0 { > + compatible = "artesyn,mvme7100-bcsr"; > + reg = <4 0 0x1>; > + }; > + > +serial@5,1000 { > + cell-index = <2>;

Re: [PATCH] ideapad-laptop: add a new WMI string for ESC key

On Thu, May 12, 2016 at 12:34:05AM +0300, Denis Gordienko wrote: > Hi, Darren. This patch already tested on my laptop and I can confirm - it's > work fine. Awesome, thanks! Added your tested-by. > Denis > 11 Май 2016 г. 23:09 пользователь "Darren Hart" > написал: > > On

Re: [PATCH] ideapad-laptop: add a new WMI string for ESC key

On Thu, May 12, 2016 at 12:34:05AM +0300, Denis Gordienko wrote: > Hi, Darren. This patch already tested on my laptop and I can confirm - it's > work fine. Awesome, thanks! Added your tested-by. > Denis > 11 Май 2016 г. 23:09 пользователь "Darren Hart" > написал: > > On Mon, May 09, 2016 at

Re: tty crash in Linux 4.6

Hi Mikulas, On 05/16/2016 01:12 PM, Mikulas Patocka wrote: > Hi > > In the kernel 4.6 I get crashes in the tty layer. I can reproduce the > crash by logging into the machine with ssh and typing before the prompt > appears. Thanks for the report. I tried to reproduce this a number of times on

[PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and epilogue. The latest blinding constant change prefers to constant size of prologue and epilogue. AAPCS reserves R9 ~ R15 for

[PATCH net-next] bpf: arm64: remove callee-save registers use for tmp registers

In the current implementation of ARM64 eBPF JIT, R23 and R24 are used for tmp registers, which are callee-saved registers. This leads to variable size of JIT prologue and epilogue. The latest blinding constant change prefers to constant size of prologue and epilogue. AAPCS reserves R9 ~ R15 for

Re: tty crash in Linux 4.6

Hi Mikulas, On 05/16/2016 01:12 PM, Mikulas Patocka wrote: > Hi > > In the kernel 4.6 I get crashes in the tty layer. I can reproduce the > crash by logging into the machine with ssh and typing before the prompt > appears. Thanks for the report. I tried to reproduce this a number of times on

Re: 4.6 compilation error when making signing key

CONFIG_MODULE_SIG_KEY="signing_key.pem" This should be 'certs/signing_key.pem', right? I'm not sure how it ended up like that -- perhaps something happened in my next branch (which shares the same .config generally). -- James Morris

Re: 4.6 compilation error when making signing key

CONFIG_MODULE_SIG_KEY="signing_key.pem" This should be 'certs/signing_key.pem', right? I'm not sure how it ended up like that -- perhaps something happened in my next branch (which shares the same .config generally). -- James Morris

Re: 4.6 compilation error when making signing key

On Mon, 16 May 2016, David Howells wrote: > James Morris wrote: > > > I'm seeing this with the 4.6 kernel build: > > > > CHK include/generated/compile.h > > make[1]: *** No rule to make target `signing_key.pem', needed by > > `certs/signing_key.x509'. Stop. > > make:

Re: 4.6 compilation error when making signing key

On Mon, 16 May 2016, David Howells wrote: > James Morris wrote: > > > I'm seeing this with the 4.6 kernel build: > > > > CHK include/generated/compile.h > > make[1]: *** No rule to make target `signing_key.pem', needed by > > `certs/signing_key.x509'. Stop. > > make: *** [certs] Error 2

Re: [v5,1/7] QE: Add IC, SI and SIRAM document to device tree bindings.

On Wed, Mar 09, 2016 at 09:21:28AM +0800, Zhao Qiang wrote: > Add IC, SI and SIRAM document of QE to > Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe.txt > > Signed-off-by: Zhao Qiang > Acked-by: Rob Herring > --- > changes for v2 > - Add

Re: [v5,1/7] QE: Add IC, SI and SIRAM document to device tree bindings.

On Wed, Mar 09, 2016 at 09:21:28AM +0800, Zhao Qiang wrote: > Add IC, SI and SIRAM document of QE to > Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe.txt > > Signed-off-by: Zhao Qiang > Acked-by: Rob Herring > --- > changes for v2 > - Add interrupt-controller in Required

Re: [PATCH v2 1/7] powerpc/8xx: Fix vaddr for IMMR early remap

On Fri, 2016-05-13 at 11:25 +0200, Christophe Leroy wrote: > Le 11/05/2016 à 22:38, Scott Wood a écrit : > > On Wed, 2016-05-11 at 17:03 +0200, Christophe Leroy wrote: > > > Memory: 124428K/131072K available (3748K kernel code, 188K rwdata, > > > 648K rodata, 508K init, 290K bss, 6644K reserved) >

Re: [PATCH v2 1/7] powerpc/8xx: Fix vaddr for IMMR early remap

On Fri, 2016-05-13 at 11:25 +0200, Christophe Leroy wrote: > Le 11/05/2016 à 22:38, Scott Wood a écrit : > > On Wed, 2016-05-11 at 17:03 +0200, Christophe Leroy wrote: > > > Memory: 124428K/131072K available (3748K kernel code, 188K rwdata, > > > 648K rodata, 508K init, 290K bss, 6644K reserved) >

Re: [PATCH v7 3/3] SMAF: add fake secure module

Hi Benjamin, On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > This module is allow testing secure calls of SMAF. > "Add fake secure module" does sound like something not (m)any people want to hear ;-) Have you considered calling it 'dummy', 'test' or similar ? >

Re: [PATCH v7 3/3] SMAF: add fake secure module

Hi Benjamin, On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > This module is allow testing secure calls of SMAF. > "Add fake secure module" does sound like something not (m)any people want to hear ;-) Have you considered calling it 'dummy', 'test' or similar ? > --- /dev/null > +++

Re: [PATCH v7 2/3] SMAF: add CMA allocator

Hi Benjamin, On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > SMAF CMA allocator implement helpers functions to allow SMAF > to allocate contiguous memory. > > match() each if at least one of the attached devices have coherent_dma_mask > set to DMA_BIT_MASK(32). >

Re: [PATCH v7 2/3] SMAF: add CMA allocator

Hi Benjamin, On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > SMAF CMA allocator implement helpers functions to allow SMAF > to allocate contiguous memory. > > match() each if at least one of the attached devices have coherent_dma_mask > set to DMA_BIT_MASK(32). > What is the idea behind the

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, 2016-05-16 at 16:46 -0500, Josh Poimboeuf wrote: > On Mon, May 16, 2016 at 02:39:06PM -0700, Megha Dey wrote: > > On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > > > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > > > On Mon, 2016-05-16 at 09:44 -0500, Josh

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, 2016-05-16 at 16:46 -0500, Josh Poimboeuf wrote: > On Mon, May 16, 2016 at 02:39:06PM -0700, Megha Dey wrote: > > On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > > > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > > > On Mon, 2016-05-16 at 09:44 -0500, Josh

Re: [PATCH 1/2] Create UV efi_call macros

On Thu, May 12, 2016 at 10:17:39AM +0200, Ingo Molnar wrote: > > Fine by me, although having a newline after arch_efi_call_virt_setup() > > but not before arch_efi_call_virt_teardown() seems rather arbitrary > > It's an oversight! :-) > > #define efi_call_virt(f, args...)

Re: [PATCH 1/2] Create UV efi_call macros

On Thu, May 12, 2016 at 10:17:39AM +0200, Ingo Molnar wrote: > > Fine by me, although having a newline after arch_efi_call_virt_setup() > > but not before arch_efi_call_virt_teardown() seems rather arbitrary > > It's an oversight! :-) > > #define efi_call_virt(f, args...)

[PATCH 0/2] DEC frame buffer modular driver cleanups

Hi, This is a pair of small cleanups for `__init' annotation issues in PMAG-B and PMAGB-B frame buffer drivers discovered in a modular build, which is a seldom used, but supported configuration. Please apply; I think these are obvious enough to be fast-tracked to 4.7 right away. Maciej

[PATCH 0/2] DEC frame buffer modular driver cleanups

Hi, This is a pair of small cleanups for `__init' annotation issues in PMAG-B and PMAGB-B frame buffer drivers discovered in a modular build, which is a seldom used, but supported configuration. Please apply; I think these are obvious enough to be fast-tracked to 4.7 right away. Maciej

[PATCH 2/2] video: fbdev: pmagb-b-fb: Remove bad `__init' annotation

Fix: WARNING: drivers/video/fbdev/pmagb-b-fb.o(.text+0x6dc): Section mismatch in reference from the function pmagbbfb_probe() to the function .init.text:pmagbbfb_erase_cursor() The function pmagbbfb_probe() references the function __init pmagbbfb_erase_cursor(). This is often because

[PATCH 2/2] video: fbdev: pmagb-b-fb: Remove bad `__init' annotation

Fix: WARNING: drivers/video/fbdev/pmagb-b-fb.o(.text+0x6dc): Section mismatch in reference from the function pmagbbfb_probe() to the function .init.text:pmagbbfb_erase_cursor() The function pmagbbfb_probe() references the function __init pmagbbfb_erase_cursor(). This is often because

[PATCH 1/2] video: fbdev: pmag-ba-fb: Remove bad `__init' annotation

Fix: WARNING: drivers/video/fbdev/pmag-ba-fb.o(.text+0x308): Section mismatch in reference from the function pmagbafb_probe() to the function .init.text:pmagbafb_erase_cursor() The function pmagbafb_probe() references the function __init pmagbafb_erase_cursor(). This is often because

[PATCH 1/2] video: fbdev: pmag-ba-fb: Remove bad `__init' annotation

Fix: WARNING: drivers/video/fbdev/pmag-ba-fb.o(.text+0x308): Section mismatch in reference from the function pmagbafb_probe() to the function .init.text:pmagbafb_erase_cursor() The function pmagbafb_probe() references the function __init pmagbafb_erase_cursor(). This is often because

Re: [PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

On Mon, May 16, 2016 at 03:45:50PM +0530, Rajneesh Bhardwaj wrote: > On Thu, May 12, 2016 at 06:02:45PM +0300, Andy Shevchenko wrote: > > On Thu, May 12, 2016 at 4:50 PM, Rajneesh Bhardwaj > > wrote: > > > > Sorry for a bit late review, but I think there are still

Re: [PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

On Mon, May 16, 2016 at 03:45:50PM +0530, Rajneesh Bhardwaj wrote: > On Thu, May 12, 2016 at 06:02:45PM +0300, Andy Shevchenko wrote: > > On Thu, May 12, 2016 at 4:50 PM, Rajneesh Bhardwaj > > wrote: > > > > Sorry for a bit late review, but I think there are still issues need > > to be

Re: [PATCH v7 1/3] create SMAF module

Hi Benjamin, I'd suspect you're interested in some feedback on these, so here is a few :-) Sadly (ideally?) nothing serious, but a bunch minor suggestions, plus the odd bug. On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > --- /dev/null > +++

Re: [PATCH v7 1/3] create SMAF module

Hi Benjamin, I'd suspect you're interested in some feedback on these, so here is a few :-) Sadly (ideally?) nothing serious, but a bunch minor suggestions, plus the odd bug. On 9 May 2016 at 16:07, Benjamin Gaignard wrote: > --- /dev/null > +++ b/drivers/smaf/smaf-core.c > @@ -0,0 +1,794 @@ >

Re: [PATCH 1/2] Create UV efi_call macros

On Thu, May 12, 2016 at 01:06:00PM +0100, Matt Fleming wrote: > (Adding author of arch_efi_call code) > > On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote: > > We need a slightly different macro than the standard efi_call_virt, > > since those macros all assume that the function pointer, f,

Re: [PATCH 1/2] Create UV efi_call macros

On Thu, May 12, 2016 at 01:06:00PM +0100, Matt Fleming wrote: > (Adding author of arch_efi_call code) > > On Wed, 11 May, at 02:55:44PM, Alex Thorlton wrote: > > We need a slightly different macro than the standard efi_call_virt, > > since those macros all assume that the function pointer, f,

Re: [GIT PULL] EFI fix

On Mon, May 16, 2016 at 03:23:51PM -0500, Alex Thorlton wrote: > Everything discussed above makes sense to me, and the patch looks sane. > I will apply and test it today and let you know how it works. I applied this to the latest -tip kernel and tested on both real hardware and in our simulator.

Re: [GIT PULL] EFI fix

On Mon, May 16, 2016 at 03:23:51PM -0500, Alex Thorlton wrote: > Everything discussed above makes sense to me, and the patch looks sane. > I will apply and test it today and let you know how it works. I applied this to the latest -tip kernel and tested on both real hardware and in our simulator.

Re: [PATCH] mm: unhide vmstat_text definition for CONFIG_SMP

On Mon, 16 May 2016 16:23:33 +0200 Michal Hocko wrote: > Andrew, I think that the following is more straightforward fix and > should be folded in to the patch which has introduced vmstat_refresh. > --- > >From b8dd18fb7df040e1bfe61aadde1d903589de15e4 Mon Sep 17 00:00:00 2001 >

Re: [PATCH] mm: unhide vmstat_text definition for CONFIG_SMP

On Mon, 16 May 2016 16:23:33 +0200 Michal Hocko wrote: > Andrew, I think that the following is more straightforward fix and > should be folded in to the patch which has introduced vmstat_refresh. > --- > >From b8dd18fb7df040e1bfe61aadde1d903589de15e4 Mon Sep 17 00:00:00 2001 > From: Michal Hocko

[PATCH 2/2] net: ethernet: fec-mpc52xx: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/freescale/fec_mpc52xx.c | 26 ++ 1 files changed, 2

[PATCH 2/2] net: ethernet: fec-mpc52xx: use phy_ethtool_{get|set}_link_ksettings

There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/freescale/fec_mpc52xx.c | 26 ++ 1 files changed, 2 insertions(+), 24

RE: [Intel-wired-lan] [PATCH] e1000e: prevent division by zero if TIMINCA is zero

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On > Behalf Of Denys Vlasenko > Sent: Friday, May 6, 2016 12:42 PM > To: Kirsher, Jeffrey T > Cc: intel-wired-...@lists.osuosl.org; Denys Vlasenko > ; LKML

[PATCH 1/2] net: ethernet: fec-mpc52xx: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phydev in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 2/5] f2fs: use percpu_counter for page counters

This patch substitutes percpu_counter for atomic_counter when counting various types of pages. Signed-off-by: Jaegeuk Kim --- fs/f2fs/debug.c | 1 + fs/f2fs/f2fs.h | 12 +++- fs/f2fs/super.c | 31 +++ 3 files changed, 35 insertions(+), 9

[PATCH 2/5] f2fs: use percpu_counter for page counters

This patch substitutes percpu_counter for atomic_counter when counting various types of pages. Signed-off-by: Jaegeuk Kim --- fs/f2fs/debug.c | 1 + fs/f2fs/f2fs.h | 12 +++- fs/f2fs/super.c | 31 +++ 3 files changed, 35 insertions(+), 9 deletions(-) diff

RE: [Intel-wired-lan] [PATCH] e1000e: prevent division by zero if TIMINCA is zero

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On > Behalf Of Denys Vlasenko > Sent: Friday, May 6, 2016 12:42 PM > To: Kirsher, Jeffrey T > Cc: intel-wired-...@lists.osuosl.org; Denys Vlasenko > ; LKML ; > net...@vger.kernel.org > Subject: [Intel-wired-lan] [PATCH]

[PATCH 1/2] net: ethernet: fec-mpc52xx: use phydev from struct net_device

The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phydev in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 1/5] f2fs: manipulate dirty file inodes when DATA_FLUSH is set

It needs to maintain dirty file inodes only if DATA_FLUSH is set. Otherwise, let's avoid its overhead. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/checkpoint.c

[PATCH 1/5] f2fs: manipulate dirty file inodes when DATA_FLUSH is set

It needs to maintain dirty file inodes only if DATA_FLUSH is set. Otherwise, let's avoid its overhead. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c index

[PATCH 4/5] f2fs: use percpu_counter for alloc_valid_block_count

This patch uses percpu_count for sbi->alloc_valid_block_count. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 2 +- fs/f2fs/f2fs.h | 8 +--- fs/f2fs/recovery.c | 5 +++-- fs/f2fs/super.c | 7 +-- 4 files changed, 14 insertions(+), 8 deletions(-)

[PATCH 5/5] f2fs: use percpu_counter for total_valid_inode_count

This patch uses percpu_counter to avoid stat_lock. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 18 +++--- fs/f2fs/super.c | 11 --- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index

[PATCH 3/5] f2fs: use percpu_counter for # of dirty pages in inode

This patch adds percpu_counter for # of dirty pages in inode. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 10 +- fs/f2fs/file.c | 2 +- fs/f2fs/super.c | 8 +++- 3 files changed, 13 insertions(+), 7 deletions(-) diff --git a/fs/f2fs/f2fs.h

[PATCH 4/5] f2fs: use percpu_counter for alloc_valid_block_count

This patch uses percpu_count for sbi->alloc_valid_block_count. Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 2 +- fs/f2fs/f2fs.h | 8 +--- fs/f2fs/recovery.c | 5 +++-- fs/f2fs/super.c | 7 +-- 4 files changed, 14 insertions(+), 8 deletions(-) diff --git

[PATCH 5/5] f2fs: use percpu_counter for total_valid_inode_count

This patch uses percpu_counter to avoid stat_lock. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 18 +++--- fs/f2fs/super.c | 11 --- 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 43aa692..c965897 100644 ---

[PATCH 3/5] f2fs: use percpu_counter for # of dirty pages in inode

This patch adds percpu_counter for # of dirty pages in inode. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 10 +- fs/f2fs/file.c | 2 +- fs/f2fs/super.c | 8 +++- 3 files changed, 13 insertions(+), 7 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index

Re: [PATCH] Use MICRO UINT_MAX instead of actual value

On 04/30/2016 07:13 AM, Minfei Huang wrote: Ping. Any comment is appreciate. Hi Minfei, I guess a good idea would be to resend the patch with the typo fixed, as a v2 patch. What do you think? Cheers, Guilherme Thanks Minfei On 04/25/16 at 11:13P, Minfei Huang wrote: It's more

Re: [GIT PULL] extcon next for 4.7

Dear Greg, On 2016년 05월 16일 21:35, Greg KH wrote: > On Tue, May 10, 2016 at 10:47:23AM +0900, Chanwoo Choi wrote: >> Dear Greg, >> >> I'm sorry for late pull request. This is extcon-next pull request for v4.7. >> I add detailed description of this pull request on below. >> Please pull extcon with

Re: [PATCH] Use MICRO UINT_MAX instead of actual value

On 04/30/2016 07:13 AM, Minfei Huang wrote: Ping. Any comment is appreciate. Hi Minfei, I guess a good idea would be to resend the patch with the typo fixed, as a v2 patch. What do you think? Cheers, Guilherme Thanks Minfei On 04/25/16 at 11:13P, Minfei Huang wrote: It's more

Re: [GIT PULL] extcon next for 4.7

Dear Greg, On 2016년 05월 16일 21:35, Greg KH wrote: > On Tue, May 10, 2016 at 10:47:23AM +0900, Chanwoo Choi wrote: >> Dear Greg, >> >> I'm sorry for late pull request. This is extcon-next pull request for v4.7. >> I add detailed description of this pull request on below. >> Please pull extcon with

Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 16, 2016 at 05:30:28PM -0400, Theodore Ts'o wrote: > On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote: > > Hi Stephen, > > > > Thank you for the notice. > > I've been waiting for a comment about the below patch targeted to v4.7 from > > Ted. > > Meanwhile, I intended to

Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 16, 2016 at 05:30:28PM -0400, Theodore Ts'o wrote: > On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote: > > Hi Stephen, > > > > Thank you for the notice. > > I've been waiting for a comment about the below patch targeted to v4.7 from > > Ted. > > Meanwhile, I intended to

Re: [PATCH] ftrace/x86: Fix function graph tracer reset path

On Mon, 16 May 2016 09:58:33 -0400 Steven Rostedt wrote: > > Nice work Masami! > > On Mon, 16 May 2016 21:32:50 +0900 > Namhyung Kim wrote: > > > > > -/* This is global to keep gas from relaxing the jumps */ > > >

Re: [PATCH] ftrace/x86: Fix function graph tracer reset path

On Mon, 16 May 2016 09:58:33 -0400 Steven Rostedt wrote: > > Nice work Masami! > > On Mon, 16 May 2016 21:32:50 +0900 > Namhyung Kim wrote: > > > > > -/* This is global to keep gas from relaxing the jumps */ > > > -ENTRY(early_idt_handler) > > > +/* This is weak to keep gas

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Sunday 05/15 at 15:36 +0900, Sergey Senozhatsky wrote: > Hello, > > On (05/13/16 13:58), Calvin Owens wrote: > [..] > > +#if defined(CONFIG_PRINTK_APPEND_UNAME) > > +static ssize_t msg_print_ext_uname(char *buf, size_t size) > > +{ > > + return scnprintf(buf, size, " UNAME=%s\n",

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Sunday 05/15 at 15:36 +0900, Sergey Senozhatsky wrote: > Hello, > > On (05/13/16 13:58), Calvin Owens wrote: > [..] > > +#if defined(CONFIG_PRINTK_APPEND_UNAME) > > +static ssize_t msg_print_ext_uname(char *buf, size_t size) > > +{ > > + return scnprintf(buf, size, " UNAME=%s\n",

Re: [PATCH v9] mm: kasan: Initial memory quarantine implementation

Hi Alexander, On Wed, May 11, 2016 at 6:18 PM, Alexander Potapenko wrote: > Quarantine isolates freed objects in a separate queue. The objects are > returned to the allocator later, which helps to detect use-after-free > errors. > > Freed objects are first added to per-cpu

Re: [PATCH v9] mm: kasan: Initial memory quarantine implementation

Hi Alexander, On Wed, May 11, 2016 at 6:18 PM, Alexander Potapenko wrote: > Quarantine isolates freed objects in a separate queue. The objects are > returned to the allocator later, which helps to detect use-after-free > errors. > > Freed objects are first added to per-cpu quarantine queues. >

RE: [PATCH] mpt3sas: Do scsi_remove_host() before deleting SAS PHY objects

Our understanding is the relationship between the SCSI host and SAS end devices is a parent-child and before ripping of SCSI host we need to rip of all the children. Why the enclosure ends up trying to re-parent the SCSI device from the enclosure to the SAS PHY even after we remove the SAS Phy?.

RE: [PATCH] mpt3sas: Do scsi_remove_host() before deleting SAS PHY objects

Our understanding is the relationship between the SCSI host and SAS end devices is a parent-child and before ripping of SCSI host we need to rip of all the children. Why the enclosure ends up trying to re-parent the SCSI device from the enclosure to the SAS PHY even after we remove the SAS Phy?.

Re: [PATCH 1/1] simplified security.nscapability xattr

On Mon, May 16, 2016 at 04:15:23PM -0500, Serge E. Hallyn wrote: > Quoting Serge E. Hallyn (se...@hallyn.com): > ... > > There's a problem though. The above suffices to prevent an unprivileged > > user > > in a user_ns from unsharing a user_ns to write a file capability and exploit > > that

Re: [PATCH 1/1] simplified security.nscapability xattr

On Mon, May 16, 2016 at 04:15:23PM -0500, Serge E. Hallyn wrote: > Quoting Serge E. Hallyn (se...@hallyn.com): > ... > > There's a problem though. The above suffices to prevent an unprivileged > > user > > in a user_ns from unsharing a user_ns to write a file capability and exploit > > that

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, May 16, 2016 at 02:39:06PM -0700, Megha Dey wrote: > On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > > On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > > > > On Fri, May 13, 2016 at 10:32:26AM -0700,

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, May 16, 2016 at 02:39:06PM -0700, Megha Dey wrote: > On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > > On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > > > > On Fri, May 13, 2016 at 10:32:26AM -0700,

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Sunday 05/15 at 00:19 +0200, Richard Weinberger wrote: > On Fri, May 13, 2016 at 10:58 PM, Calvin Owens wrote: > > We use netconsole to collect kernel logs from all the servers at > > Facebook. We use this patch internally so each logline has a record of > > which kernel

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Sunday 05/15 at 00:19 +0200, Richard Weinberger wrote: > On Fri, May 13, 2016 at 10:58 PM, Calvin Owens wrote: > > We use netconsole to collect kernel logs from all the servers at > > Facebook. We use this patch internally so each logline has a record of > > which kernel version emitted it. >

Re: [PATCH] objtool: cope with pre-4.5 gcc (and non-gcc)

On Fri, May 13, 2016 at 12:27:06AM -0600, Jan Beulich wrote: > The kernel's unreachable() translates to __builtin_unreachable() only > for gcc 4.5 and newer, and else expands to an infinite loop. Avoid > "function has unreachable instruction" warnings for this case by > inspecting the instructions

Re: [PATCH] objtool: cope with pre-4.5 gcc (and non-gcc)

On Fri, May 13, 2016 at 12:27:06AM -0600, Jan Beulich wrote: > The kernel's unreachable() translates to __builtin_unreachable() only > for gcc 4.5 and newer, and else expands to an infinite loop. Avoid > "function has unreachable instruction" warnings for this case by > inspecting the instructions

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > > > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > > > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar

Re: [PATCH] crypto/sha1-mb: make sha1_x8_avx2() conform to C function ABI

On Mon, 2016-05-16 at 15:16 -0500, Josh Poimboeuf wrote: > On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote: > > On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > > > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > > > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar

Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote: > Hi Stephen, > > Thank you for the notice. > I've been waiting for a comment about the below patch targeted to v4.7 from > Ted. > Meanwhile, I intended to prepare -next for that patch in advance. > Surely, once I get a sense that I

Re: linux-next: manual merge of the f2fs tree with the ext4 tree

On Mon, May 09, 2016 at 10:15:03AM -0700, Jaegeuk Kim wrote: > Hi Stephen, > > Thank you for the notice. > I've been waiting for a comment about the below patch targeted to v4.7 from > Ted. > Meanwhile, I intended to prepare -next for that patch in advance. > Surely, once I get a sense that I

[GIT PULL] Generic device properties framework update for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ device-properties-4.7-rc1 to receive an update of the generic device properties framework for v4.7-rc1 with top-most commit dab2e29402f40431d2199e6faff48174204d2d06 Merge back new device

[GIT PULL] Generic device properties framework update for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ device-properties-4.7-rc1 to receive an update of the generic device properties framework for v4.7-rc1 with top-most commit dab2e29402f40431d2199e6faff48174204d2d06 Merge back new device

[GIT PULL] ACPI updates for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.7-rc1 to receive core ACPI code updates for v4.7-rc1 with top-most commit fc723957801465c4a911d0a509709f0f8b91aa8a Merge branches 'acpi-pci', 'acpi-misc' and 'acpi-tools' on top of commit

[GIT PULL] ACPI updates for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.7-rc1 to receive core ACPI code updates for v4.7-rc1 with top-most commit fc723957801465c4a911d0a509709f0f8b91aa8a Merge branches 'acpi-pci', 'acpi-misc' and 'acpi-tools' on top of commit

[GIT PULL] Power management updates for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.7-rc1 to receive the main part of power management material for v4.7-rc1 with top-most commit 27c4a1c5ef61b6d4a9aeae68b24419b4319b97ed Merge branches 'pm-avs', 'pm-clk', 'powercap' and

[GIT PULL] Power management updates for v4.7-rc1

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.7-rc1 to receive the main part of power management material for v4.7-rc1 with top-most commit 27c4a1c5ef61b6d4a9aeae68b24419b4319b97ed Merge branches 'pm-avs', 'pm-clk', 'powercap' and

Re: [PATCH 1/1] simplified security.nscapability xattr

Quoting Serge E. Hallyn (se...@hallyn.com): ... > There's a problem though. The above suffices to prevent an unprivileged user > in a user_ns from unsharing a user_ns to write a file capability and exploit > that capability in the ns where he is unprivileged. With one exception, which > is the

Re: [PATCH 1/1] simplified security.nscapability xattr

Quoting Serge E. Hallyn (se...@hallyn.com): ... > There's a problem though. The above suffices to prevent an unprivileged user > in a user_ns from unsharing a user_ns to write a file capability and exploit > that capability in the ns where he is unprivileged. With one exception, which > is the

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