Re: [RFC v7 22/41] richacl: Propagate everyone@ permissions to other aces

2015-09-18 23:36 GMT+02:00 J. Bruce Fields : > On Sat, Sep 05, 2015 at 12:27:17PM +0200, Andreas Gruenbacher wrote: >> + if (!richace_is_owner(who) && >> + richace_is_everyone(ace) && richace_is_allow(ace) && > > That richace_is_allow(ace) check is redundant at

Re: [PATCH] driver core: Ensure proper suspend/resume ordering

Hi, On Mon, Sep 21, 2015 at 10:51 AM, Thierry Reding wrote: > On Sat, Sep 19, 2015 at 01:07:56AM +0200, Rafael J. Wysocki wrote: >> On Fri, Sep 18, 2015 at 5:55 PM, Thierry Reding >> wrote: > [...] >> > Of course there's still the matter of

[PATCH v2] perf record: Synthesize COMM event for a command line workload

When perf creates a new child to profile, the events are enabled on exec(). And in this case, it doesn't synthesize any event for the child since they'll be generated during exec(). But there's an window between the enabling and the event generation. It used to be overcome since samples are

Re: [PATCH v6 03/22] of/platform: Point to struct device from device node

On Mon, Sep 21, 2015 at 9:02 AM, Tomeu Vizoso wrote: > When adding platform and AMBA devices, set the device node's device > member to point to it. > > This speeds lookups considerably and is safe because we only create one > of these devices for any given device node.

[PATCH] staging: dgap: fix returned errno code in dgap_parsefile()

The driver is using -1 instead of the -ENOMEM defined macro to specify that a buffer allocation failed. Since the error number is propagated, the caller will get a -EPERM which is the wrong error condition. Also, the smatch tool complains with the following warning: dgap_parsefile() warn:

Re: [PATCH 3/3] page-flags: rectify forward declaration

On Sat, 19 Sep 2015 22:42:59 +0530 Sudip Mukherjee wrote: > compound_head is defined as inline in page-flags.h but in the forward > declaration of compound_head in the same file missed "inline". As a result > we got plenty of build warnings while building for some

Linux 3.10.89

I'm announcing the release of the 3.10.89 kernel. All users of the 3.10 kernel series must upgrade. The updated 3.10.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.10.y and can be browsed at the normal kernel.org git web

Re: [PATCH] doc: add information about max_ptes_swap

On Fri, 18 Sep 2015, Ebru Akagunduz wrote: > max_ptes_swap specifies how many pages can be brought in from > swap when collapsing a group of pages into a transparent huge page. > > /sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap > > A higher value can cause excessive swap IO and

Re: [PATCH v10 4/5] QE/CPM: move muram management functions to qe_common

On Fri, Sep 18, 2015 at 03:15:20PM +0800, Zhao Qiang wrote: > QE and CPM have the same muram, they use the same management > functions. Now QE support both ARM and PowerPC, it is necessary > to move QE to "driver/soc", so move the muram management functions > from cpm_common to qe_common for

Re: [PATCH 2/3] mfd: tps65912: Rewrite driver adding DT support and using regmap

On Mon, 21 Sep 2015, Andrew F. Davis wrote: > On 09/19/2015 11:16 PM, Lee Jones wrote: > >On Tue, 15 Sep 2015, Andrew F. Davis wrote: > > > >>The old driver does not support DT. Rewrite the driver adding DT support > >>and use modern kernel features such as regmap and related helpers. > >> >

Re: [PATCH 05/15] RDS: increase size of hash-table to 8K

From: Santosh Shilimkar Date: Sat, 19 Sep 2015 19:04:42 -0400 > Even with per bucket locking scheme, in a massive parallel > system with active rds sockets which could be in excess of multiple > of 10K, rds_bin_lookup() workload is siginificant because of smaller >

Re: [PATCH] lib: fix data race in rhashtable_rehash_one

On Tue, 2015-09-22 at 00:25 +0200, Thomas Graf wrote: > On 09/21/15 at 07:51am, Eric Dumazet wrote: > > The important part here is that we rehash an item, so we need to make > > sure to maintain consistent ->next field, and need to prevent compiler > > from using ->next as a temporary variable. >

Re: [PATCH 2/2] EDAC: Fix sysfs dimm_label store operation

On Mon, 2015-09-21 at 13:19 -0600, Toshi Kani wrote: : > > diff --git a/drivers/edac/edac_mc_sysfs.c b/drivers/edac/edac_mc_sysfs.c > index 8983755..f2ea914 100644 > --- a/drivers/edac/edac_mc_sysfs.c > +++ b/drivers/edac/edac_mc_sysfs.c > @@ -241,13 +241,14 @@ static ssize_t

Re: mm: ksm: WARNING: CPU: 3 PID: 22593 at mm/ksm.c:715 remove_stable_node+0xc7/0xf0()

On Thu, 17 Sep 2015, Sasha Levin wrote: > Hi all, > > I've observed the following warning while fuzzing with trinity inside a KVM > tools > guest running -next: > > [1385507.811807] Out of memory (oom_kill_allocating_task): Kill process 22593 > (ksm04) score 0 or sacrifice child >

Re: [Nbd] NBD: Disconnect connection/kill NBD server cause kernel bug even kernel hang

Thank you Paul! That's exactly the issue I met. I've read the whole thread and got a general idea of the issue. I try to summarize it and please correct me if I'm wrong: 1. The issue is the result of kill_bdev() when connection has been cut when IO is still flying. 2. Other block devices driver

Re: Please suggest proper format for DT properties.

On Mon, Sep 21, 2015 at 2:24 PM, Constantine Shulyupin wrote: > On Mon, Sep 21, 2015 at 4:51 AM, Rob Herring wrote: >> On Fri, Sep 18, 2015 at 5:36 PM, Constantine Shulyupin >> wrote: >>> Hi, >>> >>> I am designing DT support for a

Re: [PATCH v2 5/8] soc: qcom: smd: Remove use of VLAIS

indication of the request being truncated... @Andy, I presume this is only on your -next, can you update the commit? Or do you want a patch for it? With this tiny change what we have on next-20150921 seems to work fine. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 1/3] mmc: debugfs: fix memory leak for mmc_ext_csd_open

On 2015/9/22 9:29, trick wong wrote: In the correct path,this buf will used later.why freed? right. sorry for this noise, withdraw this patch[1/3]. 2015-09-22 9:18 GMT+08:00 Shawn Lin >: buf allocated isn't been freed before

Re: [RFC v7 15/41] richacl: Automatic Inheritance

On Mon, Sep 21, 2015 at 11:19:59PM +0200, Andreas Gruenbacher wrote: > 2015-09-18 20:40 GMT+02:00 J. Bruce Fields : > > On Sat, Sep 05, 2015 at 12:27:10PM +0200, Andreas Gruenbacher wrote: > >> Automatic Inheritance (AI) allows changes to the acl of a directory to > > In the

[lkp] [sched/fair] 50a2a3b246: 6.8% unixbench.score

FYI, we noticed the below changes on https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 50a2a3b246149d041065a67ccb3e98145f780a2f ("sched/fair: Have task_move_group_fair() unconditionally add the entity load to the runqueue")

Re: [PATCH v10 4/5] QE/CPM: move muram management functions to qe_common

On Mon, 2015-09-21 at 22:06 -0500, Zhao Qiang-B45475 wrote: > On Tue, Sep 22, 2015 at 10:26AM +0800, Wood Scott-B07421 wrote: > > > -Original Message- > > From: Wood Scott-B07421 > > Sent: Tuesday, September 22, 2015 10:26 AM > > To: Zhao Qiang-B45475 > > Cc: linux-kernel@vger.kernel.org;

Re: [PATCH 5/5] mtd: orion_nand: Fix module autoload for OF platform driver

On Fri, Sep 18, 2015 at 12:14:02AM +0200, Luis de Bethencourt wrote: > This platform driver has a OF device ID table but the OF module > alias information is not created so module autoloading won't work. > > Signed-off-by: Luis de Bethencourt Acked-by: Andrew Lunn

[4.3-rc1, regression] dax: hang on i_mmap_rwsem in generic/075

Hi folks, I'm seeing hangs like this when using DAX on XFS on 4.3-rc1 running xfstests generic/075 (fsx test): # echo w > /proc/sysrq-trigger [71628.984872] sysrq: SysRq : Show Blocked State [71628.985988] taskPC stack pid father [71628.987635] fsx D

Re: [PATCH] powercap / RAPL : remove dependency on iosf_mbi

On 09/22/2015 05:36 AM, Jacob Pan wrote: On Mon, 21 Sep 2015 11:48:14 +0800 Pengyu Ma wrote: On 09/18/2015 11:43 PM, Jacob Pan wrote: On Fri, 18 Sep 2015 02:09:55 +0200 "Rafael J. Wysocki" wrote: On Thursday, September 17, 2015 03:31:41 PM

Re: [Intel-wired-lan] [PATCH] igb: add more checks for disconnected adapter

On 09/21/2015 10:11 AM, Jarod Wilson wrote: Some pci changes upcoming in 4.3 seem to cause additional disconnects, which can happen at unfortuitous times for igb, leading to issues such as this, where the disconnect happened just before igb_configure_tx_ring(): [ 414.440115] igb :15:00.0:

[GIT PULL] cgroup fixes for v4.3-rc2

Hello, Linus. The threadgroup locking changes which went in during 4.2 devel cycle added write locking of a percpu_rwsem in cgroup task migration path; unfortunately, that involved expedited rcu syncing which turned out to be too slow and heavy for certain workloads. The patchset which is

Re: [RFC PATCH 0/2] kvmclock: fix ABI breakage from PVCLOCK_COUNTS_FROM_ZERO.

2015-09-21 17:53-0300, Marcelo Tosatti: > On Mon, Sep 21, 2015 at 10:00:27PM +0200, Radim Krčmář wrote: >> 2015-09-21 12:52-0300, Marcelo Tosatti: >> > On Mon, Sep 21, 2015 at 05:12:10PM +0200, Radim Krčmář wrote: >> >> 2015-09-20 19:57-0300, Marcelo Tosatti: >> >>> Is it counting from zero that

Re: [PATCH 1/7] phy: fix of_mdio_find_bus() device refcount leak

From: Russell King - ARM Linux Date: Mon, 21 Sep 2015 20:32:07 +0100 > In the case of the mdio mux code, I'm dropping the reference when > either (a) we've encountered an error during initialisation and > we're cleaning up, or (b) when the mdio mux code is being torn down

Re: [PATCH tip/core/rcu 14/19] rcu: Extend expedited funnel locking to rcu_data structure

On 09/21/2015 12:12 AM, Paul E. McKenney wrote: > Hmmm... I created rdp->exp_funnel_mutex, but failed to give RCU-sched > its own lock class. Does the following untested patch fix things for you? Haven't reproduced yet, but it didn't happen that often before - let's give it another day or two

Re: [PATCH v5 3/4] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

On Tue, Sep 08, 2015 at 10:10:52AM +0100, Alex Smith wrote: > Add a driver for NAND devices connected to the NEMC on JZ4780 SoCs, as > well as the hardware BCH controller. DMA is not currently implemented. > > While older 47xx SoCs also have a BCH controller, they are incompatible > with the one

Re: [PATCH v7] pci: quirk to skip msi disable on shutdown

On Mon, Sep 21, 2015 at 10:42:13PM +0300, Michael S. Tsirkin wrote: > On Mon, Sep 21, 2015 at 01:21:47PM -0500, Bjorn Helgaas wrote: > > On Sun, Sep 06, 2015 at 06:32:35PM +0300, Michael S. Tsirkin wrote: > > > On some hypervisors, virtio devices tend to generate spurious interrupts > > > when

[PATCH v3 2/9] ARM: dts: Use label for device nodes in Cygnus dts

Use label instead of full path to reference device nodes in Cygnus dts files Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm911360_entphn.dts | 8 +++ arch/arm/boot/dts/bcm911360k.dts | 6 ++---

[PATCH v3 9/9] ARM: dts: fix Cygnus nand device node

The third compatible string "brcm,brcmnand" in bcm-cygnus.dtsi nand node is incorrect, redundant and should be removed. "brcm,brcmnand" is meant to be used by STB based Broadcom SoCs. All iProc based SoCs should use "brcm,nand-iproc". Signed-off-by: Ray Jui ---

[PATCH v3 1/9] ARM: dts: consolidate aliases for Cygnus dt files

Move aliases into bcm-cygnus.dtsi to avoid duplications in Cygnus dts files Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm-cygnus.dtsi | 4 arch/arm/boot/dts/bcm911360_entphn.dts | 4

Re: [Nbd] NBD: Disconnect connection/kill NBD server cause kernel bug even kernel hang

Thank you Wouter! (Add back lkml since I got another kernel issue...) In fact I just hit another issue with nbd-server/client on the same machine. The following commands hang after a while: dd if=/dev/zero of=./test When process hanging, dd/nbd-server are no long showing in high cpu

[PATCH v3 3/9] ARM: dts: Put Cygnus core components under core bus

Put all Cygnus core components into "core" node of type "simple-bus" in bcm-cygnus.dtsi Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm-cygnus.dtsi | 54 ++- 1 file changed, 30

Re: [PATCH v5 3/4] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

On Mon, Sep 14, 2015 at 03:38:48PM -0300, Ezequiel Garcia wrote: > On 9 September 2015 at 11:24, Ezequiel Garcia > wrote: > Whatever the outcome of the discussion on patch 1/4 > "mtd: nand: increase ready wait timeout and report timeouts" > is, the jz4780-specific

[PATCH v3 7/9] ARM: dts: Enable NAND support on bcm911360_entphn

This patch enables NAND support on Broadcom Cygnus form factor board (bcm911360_entphn) Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm911360_entphn.dts | 16 1 file changed, 16 insertions(+) diff --git

[PATCH v3 8/9] ARM: dts: enable touchscreen support on Cygnus

This patch enables touchscreen support on bcm958300k and bcm958305k. Touchscreen is connected to these boards through the bcm9hmidc daughter card, and therefore also adding bcm9hmidc.dtsi that describes the daughter card Signed-off-by: Ray Jui Reviewed-by: Vikram Prakash

[PATCH v3 4/9] ARM: dts: Move all Cygnus peripherals into axi bus

Move all Cygnus peripherals to be under the "axi" bus node of type "simple-bus" Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm-cygnus.dtsi | 279 +++--- 1 file changed, 140 insertions(+), 139

[PATCH v3 5/9] ARM: dts: Reorder Cygnus peripherals

Reorder all Cygnus peripherals based on base register addresses in bcm-cygnus.dtsi Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm-cygnus.dtsi | 56 +++ 1 file changed, 28 insertions(+),

[PATCH v3 6/9] ARM: dts: Enable various peripherals on bcm958305k

This patch enables various peripherals on Broadcom Cygnus wireless audio board (bcm958305k). These peripherals include I2C, PCIe, and NAND Signed-off-by: Ray Jui Reviewed-by: Scott Branden --- arch/arm/boot/dts/bcm958305k.dts | 32

[PATCH v3 0/9] Broadcom Cygnus device tree changes

This patch series cleans up the Broadcom Cygnus device tree files and makes it more consistent with the rest of Broadcom iProc device tree files. This patch series also enables various peripherals on Cygnus boards. They include: bcm11360_entphn: NAND bcm958300k: touchscreen bcm958305k: I2C,

[PATCH] x86, perf: Handle multiple umask bits for BDW CYCLE_ACTIVITY.*

From: Andi Kleen The earlier constraint fix for Broadwell CYCLE_ACTIVITY.* forced umask 8 to counter 2. For this it used UEVENT, to match the complete umask. The event list for Broadwell has an additional CYC_ACT.STALLS_L1D_PENDIND event that uses umask 8, but also sets

Re: [PATCH] barriers: introduce smp_mb__release_acquire and update documentation

On Mon, Sep 21, 2015 at 03:10:38PM +0100, Boqun Feng wrote: > On Mon, Sep 21, 2015 at 09:45:15PM +0800, Boqun Feng wrote: > > On Thu, Sep 17, 2015 at 07:00:01PM +0100, Will Deacon wrote: > > > On Thu, Sep 17, 2015 at 03:50:12AM +0100, Boqun Feng wrote: > > > > If an ACQUIRE loads the value of

Re: [RFC v2 3/7] powerpc: atomic: Implement atomic{,64}_{add,sub}_return_* variants

Hi Boqun, On Sun, Sep 20, 2015 at 09:23:03AM +0100, Boqun Feng wrote: > On Sat, Sep 19, 2015 at 11:33:10PM +0800, Boqun Feng wrote: > > On Fri, Sep 18, 2015 at 05:59:02PM +0100, Will Deacon wrote: > > > On Wed, Sep 16, 2015 at 04:49:31PM +0100, Boqun Feng wrote: > > > > On powerpc, we don't need

Re: [PATCH] lib: fix data race in rhashtable_rehash_one

On 09/21/15 at 07:51am, Eric Dumazet wrote: > The important part here is that we rehash an item, so we need to make > sure to maintain consistent ->next field, and need to prevent compiler > from using ->next as a temporary variable. > > ptr->next = 1UL | ((base + offset) << 1); > > Is dangerous

[PATCH v2] netlink: Replace rhash_portid with bound

On Mon, Sep 21, 2015 at 02:20:22PM -0400, Tejun Heo wrote: > > store_release and load_acquire are different from the usual memory > barriers and can't be paired this way. You have to pair store_release > and load_acquire. Besides, it isn't a particularly good idea to OK I've decided to drop the

RE: [PATCH v10 4/5] QE/CPM: move muram management functions to qe_common

> -Original Message- > From: Wood Scott-B07421 > Sent: Tuesday, September 22, 2015 11:25 AM > To: Zhao Qiang-B45475 > Cc: linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org; > lau...@codeaurora.org; Xie Xiaobo-R63061; b...@kernel.crashing.org; Li > Yang-Leo-R58472;

Re: [Intel-wired-lan] [PATCH] igb: add more checks for disconnected adapter

On 09/21/2015 09:14 PM, Jarod Wilson wrote: Alexander Duyck wrote: On 09/21/2015 10:11 AM, Jarod Wilson wrote: Some pci changes upcoming in 4.3 seem to cause additional disconnects, which can happen at unfortuitous times for igb, leading to issues such as this, where the disconnect happened

Re: [PATCH] xen/x86: Don't try to write syscall-related MSRs for PV guests

On Mon, Sep 21, 2015 at 09:09:28AM -0400, Boris Ostrovsky wrote: > For PV guests these registers are set up by hypervisor and thus > should not be written by the guest. The comment in xen_write_msr_safe() > says so but we still write the MSRs, causing the hypervisor to > print a warning. > >

Re: [RFC v7 13/41] richacl: Check if an acl is equivalent to a file mode

On Mon, Sep 21, 2015 at 09:59:07AM -0400, Austin S Hemmelgarn wrote: > Mode equivalence get's even trickier when you throw in permissions > just beyond rwx Note by the way that the major technical achievement here is the reconciliation of two completely different evaluation algorithms.

Re: can't oom-kill zap the victim's memory?

On 09/21, Michal Hocko wrote: > > On Mon 21-09-15 15:44:14, Oleg Nesterov wrote: > [...] > > So yes, in general oom_kill_process() can't call oom_unmap_func() directly. > > That is why the patch uses queue_work(oom_unmap_func). The workqueue thread > > takes mmap_sem and frees the memory allocated

Re: [RFC PATCH 0/2] kvmclock: fix ABI breakage from PVCLOCK_COUNTS_FROM_ZERO.

2015-09-21 17:12+0200, Radim Krčmář: > 2015-09-20 19:57-0300, Marcelo Tosatti: > > On Fri, Sep 18, 2015 at 05:54:28PM +0200, Radim Krčmář wrote: >>> This patch series will be disabling PVCLOCK_COUNTS_FROM_ZERO flag and is >>> RFC because I haven't explored many potential problems or tested it. >>

[PATCH 15/17] ir-hix5hd2: drop the use of IRQF_NO_SUSPEND

This driver doesn't claim the IR transmitter to be wakeup source. It even disables the clock and the IR during suspend-resume cycle. This patch removes yet another misuse of IRQF_NO_SUSPEND. Cc: Mauro Carvalho Chehab Cc: Zhangfei Gao Cc:

[PATCH 17/17] mfd : ab8500/db8500: fix the abuse of IRQF_NO_SUSPEND

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 12/17] ARM: OMAP2+: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 13/17] net: gianfar: remove misuse of IRQF_NO_SUSPEND flag

The device is set as wakeup capable using proper wakeup API but the driver misuses IRQF_NO_SUSPEND to set the interrupt as wakeup source which is incorrect. This patch removes the use of IRQF_NO_SUSPEND flags replacing it with enable_irq_wake instead. Cc: "David S. Miller"

[PATCH 09/17] MIPS: ttyFDC: replace IRQF_NO_SUSPEND with IRQF_COND_SUSPEND

Since the FD interrupt handler can discern spurious IRQs and it is shared with timer interrupt, use IRQF_COND_SUSPEND instead of IRQF_NO_SUSPEND. Cc: Greg Kroah-Hartman Cc: Jiri Slaby Signed-off-by: Sudeep Holla ---

[PATCH 14/17] media: st-rc: remove misuse of IRQF_NO_SUSPEND flag

The device is set as wakeup capable using proper wakeup API but the driver misuses IRQF_NO_SUSPEND to set the interrupt as wakeup source which is incorrect. This patch removes the use of IRQF_NO_SUSPEND flags replacing it with enable_irq_wake instead. Cc: Srinivas Kandagatla

[PATCH 16/17] pinctrl: single: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

Re: [PATCH 05/15] RDS: increase size of hash-table to 8K

On 9/21/2015 1:31 AM, David Laight wrote: From: Santosh Shilimkar Sent: 20 September 2015 00:05 Even with per bucket locking scheme, in a massive parallel system with active rds sockets which could be in excess of multiple of 10K, rds_bin_lookup() workload is significant because of smaller

[PATCH v8 1/5] lightnvm: Support for Open-Channel SSDs

Open-channel SSDs are devices that share responsibilities with the host in order to implement and maintain features that typical SSDs keep strictly in firmware. These include (i) the Flash Translation Layer (FTL), (ii) bad block management, and (iii) hardware units such as the flash controller,

[PATCH v8 0/5] Support for Open-Channel SSDs

These patches implement support for Open-Channel SSDs. Applies against v4.2 and available through the lkml_v8 branch at: https://github.com/OpenChannelSSD/linux Major changes from last revision is: - The NVMe driver is no longer forced to use a non-standard way to detect LightNVM

[PATCH v8 5/5] nvme: LightNVM support

The first generation of Open-Channel SSDs will be based on NVMe. The integration requires that a NVMe device register itself as a LightNVM device. The detection is through PCI IDs. The current supported are the qemu nvme simulator and CNEX Labs Westlake SSD. The qemu nvme enables support through

[PATCH v8 2/5] lightnvm: Hybrid Open-Channel SSD block manager

The host implementation for Open-Channel SSDs is divided into block management and targets. This patch implements a basic block manager hybrid open-channel SSDs. On top of the block manager, a target can be initialized. Signed-off-by: Matias Bjørling ---

Re: [PATCH] drivers/crypto/nx: Add CRC and validation support for nx842

On Mon, Sep 21, 2015 at 10:26 AM, Herbert Xu wrote: > On Sat, Sep 19, 2015 at 05:02:42PM -0700, Haren Myneni wrote: >> Hi, >> >> This patch allows nx842 coprocessor to add CRC for compression and >> check the computed CRC value for uncompression. Please let me know >>

Re: [PATCH 1/2] zbud: allow PAGE_SIZE allocations

On Fri, Sep 18, 2015 at 4:03 AM, Vitaly Wool wrote: >> I don't know how zsmalloc handles uncompressible PAGE_SIZE allocations, but >> I wouldn't expect it to be any more clever than this? So why duplicate the >> functionality in zswap and zbud? This could be handled e.g. at

Re: EXT4: new warnings from 4.3.0-rc2

On Mon, 21 Sep 2015 16:08:59 +0100, Chris Clayton wrote: > Applying the 4.2.1-rc1 patch results in a kernel that emits the messages, > so I guess my fix-not-yet-in-4.2 theory is right. I have been getting these forever since I switched to ext4-for-ext3, at least since early last year - if not

[PATCH] fs/super.c: use && instead of & for warn_on condition

This fixes the following sparse warning: fs/super.c:1202:9: warning: dubious: x & !y Bitwise and logical and are equivalent here, but logical was intended. The generated code is identical, with and without CONFIG_LOCKDEP. Signed-off-by: Vincent Stehlé Cc: Oleg

Re: [PATCH v2] KVM: x86: put vcpu_create under kvm->srcu critical section

On Mon, Sep 21, 2015 at 08:02:56AM +0200, Paolo Bonzini wrote: > This is needed in case vcpu_create wants to access the memslots array. > Fixes this lockdep splat: > > [26421.303750] === > [26421.307952] [ INFO: suspicious RCU usage. ] > [26421.312161] 4.3.0-rc1+ #1

Re: possible reason: unannotated irqs-off

Russell, On 09/18/2015 01:02 PM, Russell King - ARM Linux wrote: On Fri, Sep 18, 2015 at 12:02:15PM -0400, Murali Karicheri wrote: While chasing a fix for a deadlock in netcp driver with debug options enabled, i bumped on another warning shown below.. Looks like I need to enable

Re: include/linux/kvm_host.h:488 suspicious rcu_dereference_check() usage!

On Mon, Sep 21, 2015 at 05:19:57PM +0200, Paolo Bonzini wrote: > First, the leaf test would have to be == 0, because I prepared the > patch on the first 4.3 pull request instead of the latest Linus > tree. However even this would not be a good change, because > > is_shadow_present_pte(spte) ==

[PATCH 10/17] tty/serial: st-asc: drop the use of IRQF_NO_SUSPEND

These drivers doesn't claim the serial device to be wakeup source. Even if it is, it needs to use enable_irq_wake or other related PM wakeup APIs to enable it. This patch removes yet another misuse of IRQF_NO_SUSPEND. Cc: Srinivas Kandagatla Cc: Maxime Coquelin

[PATCH 11/17] pm: bf609: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 06/17] rtc: ds1343: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 04/17] powerpc: mpic: use IRQCHIP_SKIP_SET_WAKE instead of redundant mpic_irq_set_wake

mpic_irq_set_wake return -ENXIO for non FSL MPIC and sets IRQF_NO_SUSPEND flag for FSL ones. enable_irq_wake already returns -ENXIO if irq_set_wak is not implemented. Also there's no need to set the IRQF_NO_SUSPEND flag as it doesn't guarantee wakeup for that interrupt. This patch removes the

[PATCH 01/17] rtc: pl031: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 02/17] rtc: ab8500: remove misuse of IRQF_NO_SUSPEND flag

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should be left enabled so as to allow them to work as expected during the suspend-resume cycle, but doesn't guarantee that it will wake the system from a suspended state, enable_irq_wake is recommended to be used for the wakeup.

[PATCH 00/17] PM / wakeup : remove misuse of IRQF_NO_SUSPEND flag

Hi, As discussed in under the topic "Wakeup sources configuration and management" in LPC PM microconference @ Seattle[1], this is the first set of changes to remove the mis/ab-use of IRQF_NO_SUSPEND for wakeup IRQ configuration. This list is not complete, there are few more usages that can be

[PATCH 07/17] input: tegra-kbc: drop use of IRQF_NO_SUSPEND flag

The driver handles wakeup irq correctly using irq_set_irq_wake. There's no need to use IRQF_NO_SUSPEND while registering the interrupt. This patch removes the use of IRQF_NO_SUSPEND flag. Cc: Samuel Ortiz Cc: Lee Jones Signed-off-by: Sudeep Holla

[PATCH 08/17] hwmon: abx500: drop the use of IRQF_NO_SUSPEND

The description in the driver states: "ABX500 does not provide auto ADC, so to monitor the required temperatures, a periodic work is used. It is more important to not wake up the CPU... If the chip gets too hot during a sleep state it's most likely due to external factors, such as the surrounding

[PATCH] [media] cx25821, cx88, tm6000: use SNDRV_DEFAULT_ENABLE_PNP

Instead of manually initializing the bool array enable, use the SNDRV_DEFAULT_ENABLE_PNP macro. As most drivers do. Signed-off-by: Luis de Bethencourt --- Hi, I don't see any good reason to use = 1 instead of = SNDRV_DEFAULT_ENABLE_PNP. Semantically it is the same, and

Re: [PATCH 00/15] RDS: connection scalability and performance improvements

On 9/20/2015 1:37 AM, Sagi Grimberg wrote: On 9/20/2015 2:04 AM, Santosh Shilimkar wrote: This series addresses RDS connection bottlenecks on massive workloads and improve the RDMA performance almost by 3X. RDS TCP also gets a small gain of about 12%. RDS is being used in massive systems with

Re: [RFC v7 13/41] richacl: Check if an acl is equivalent to a file mode

On 2015-09-17 20:56, J. Bruce Fields wrote: On Thu, Sep 17, 2015 at 02:22:19PM -0400, bfields wrote: On Sat, Sep 05, 2015 at 12:27:08PM +0200, Andreas Gruenbacher wrote: ACLs are considered equivalent to file modes if they only consist of owner@, group@, and everyone@ entries, the owner@

Re: [PATCH 03/38] drm/i915: fix handling gen8_emit_flush_coherentl3_wa result

On Mon, 21 Sep 2015, Andrzej Hajda wrote: > The function can return negative value. > > The problem has been detected using proposed semantic patch > scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1]. > > [1]: http://permalink.gmane.org/gmane.linux.kernel/2038576 >

Re: can't oom-kill zap the victim's memory?

On 09/20, Raymond Jennings wrote: > > On 09/20/15 11:05, Linus Torvalds wrote: >> >> which can be called from just about any context (but atomic >> allocations will never get here, so it can schedule etc). > > I think in this case the oom killer should just slap a SIGKILL on the > task and then

[PATCH 1/2] mm/vmscan: make inactive_anon/file_is_low return bool

This patch makes inactive_anon/file_is_low return bool due to these particular functions only using either one or zero as their return value. No functional change. Signed-off-by: Yaowei Bai --- mm/vmscan.c | 18 +- 1 file changed, 9 insertions(+), 9

[PATCH 4/4] sound/core/seq: make prioq_match return bool

This patch makes prioq_match return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- sound/core/seq/seq_prioq.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-)

[PATCH v6 19/22] power-supply: Probe power supplies on demand

When looking up a power supply through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by:

[PATCH v6 13/22] backlight: Probe backlight devices on demand

When looking up a backlight device through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed.

[PATCH v6 03/22] of/platform: Point to struct device from device node

When adding platform and AMBA devices, set the device node's device member to point to it. This speeds lookups considerably and is safe because we only create one of these devices for any given device node. Signed-off-by: Tomeu Vizoso --- Changes in v5: - Set the

Re: [PATCH] lib: fix data race in rhashtable_rehash_one

On Mon, 2015-09-21 at 17:10 +0200, Dmitry Vyukov wrote: > On Mon, Sep 21, 2015 at 4:51 PM, Eric Dumazet wrote: > > On Mon, 2015-09-21 at 06:31 -0700, Eric Dumazet wrote: > >> On Mon, 2015-09-21 at 10:08 +0200, Dmitry Vyukov wrote: > >> > rhashtable_rehash_one() uses plain

Re: [PATCH] barriers: introduce smp_mb__release_acquire and update documentation

On Mon, Sep 21, 2015 at 09:45:15PM +0800, Boqun Feng wrote: > On Thu, Sep 17, 2015 at 07:00:01PM +0100, Will Deacon wrote: > > On Thu, Sep 17, 2015 at 03:50:12AM +0100, Boqun Feng wrote: > > > On Wed, Sep 16, 2015 at 12:07:06PM +0100, Will Deacon wrote: > > > > On Wed, Sep 16, 2015 at 11:43:14AM

[PATCH v6 01/22] driver core: handle -EPROBE_DEFER from bus_type.match()

Lets implementations of the match() callback in struct bus_type to return errors and if it's -EPROBE_DEFER then queue the device for deferred probing. This is useful to buses such as AMBA in which devices are registered before their matching information can be retrieved from the HW (typically

[PATCH v6 08/22] regulator: core: Probe regulators on demand

When looking up a regulator through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v4] tools lib traceevent: str addresses in heterogeneous arch environments

When a trace recorded on a 32-bit device is processed with a 64-bit binary, the higher 32-bits of the address need to ignored The lack of this results in the output of the 64-bit pointer value to the trace as the 32-bit address lookup fails in find_printk. Before: burn-1778 [003] 548.600305:

[PATCH 1/5] leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting

This patch removes SET_BRIGHTNESS_ASYNC and SET_BRIGHTNESS flags. led_set_brightness now calls led_set_brightness_nosleep instead of choosing between sync and async op basing on the flags defined by the driver. >From now on, if a user wants to make sure that brightness will be set synchronously,

[PATCH 3/5] leds: max77693: Remove work queue

Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by: Jacek Anaszewski --- drivers/leds/leds-max77693.c | 57 +++--- 1 file changed, 9 insertions(+), 48

Re: why is text address constant with full randomization?

2015-09-15 17:05 GMT+08:00 yalin wang : > >> On Sep 15, 2015, at 16:36, 慕冬亮 wrote: >> >> First, my linux kernel is Linux 114-212-83-136 4.1.0-2-amd64. >> Second, I copy /bin/cat in system to mycat , and see the address space >> layout below. >>

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