There is no point in calculating the residue if state does not
exist to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/sun6i-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
index 5065ca4..3835fcd 100644
--
Noop watchdog pretimeout governor, only an informational message is
added to the kernel log buffer.
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3:
* temporarily removed tristate option, the governor can be built-in only
Changes from v1 to v2:
* removed #ifdef CONFIG_WATCHDOG_PRETIM
From: Robin Gong
Add set_pretimeout since our watchdog driver has those interfaces and
obviously, the new common watchdog framework didn't implement this
interface.
Signed-off-by: Robin Gong
[vzapolskiy: rebased, added an inline comment to describe new interface]
Signed-off-by: Vladimir Zapolsk
The TWL6030_FIXED_LDO() macro passes the TWL_FIXED_LDO()
macro an 0x0 instead of a NULL. Changing this to a NULL
fixes the following warnings:
drivers/regulator/twl-regulator.c:1068:1: warning: Using plain integer as NULL
pointer
drivers/regulator/twl-regulator.c:1069:1: warning: Using plain inte
The change adds a simple watchdog pretimeout framework infrastructure,
its purpose is to allow users to select a desired handling of watchdog
pretimeout events, which may be generated by some watchdog devices.
A user selects a default watchdog pretimeout governor during
compilation stage.
Watchdo
There is no point calculating the residue if there is
no txstate to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/tegra20-apb-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/tegra20-apb-dma.c b/drivers/dma/tegra20-apb-dma.c
index 01e316f..7f4
Panic watchdog pretimeout governor, on watchdog pretimeout event the
kernel shall panic.
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3:
* temporarily removed tristate option, the governor can be built-in only
Changes from v1 to v2:
* removed #ifdef CONFIG_WATCHDOG_PRETIMEOUT_DEFAUL
The change allows for WDIOF_PRETIMEOUT capable watchdog devices to get
a configured pretimeout value over sysfs, the correspondent device
attribute name is "pretimeout".
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3:
* none, new change
Changes from v1 to v2:
* none, new change
dr
From: Robin Gong
Since the watchdog common framework centrialize the IOCTL interfaces
of device driver now, the SETPRETIMEOUT and GETPRETIMEOUT need to be
added in common code.
Signed-off-by: Robin Gong
[vzapolskiy: rebased, cleanups]
Signed-off-by: Vladimir Zapolskiy
---
Changes from v2 to v3
The change adds a simple watchdog pretimeout framework infrastructure,
its purpose is to allow users to select a desired handling of watchdog
pretimeout events, which may be generated by a watchdog driver.
The idea of adding this kind of a framework appeared after reviewing
several attempts to add
There is no point in calculating the residue if there is no
txstate to store the value.
Signed-off-by: Peter Griffin
---
drivers/dma/coh901318.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/coh901318.c b/drivers/dma/coh901318.c
index c340ca9..c100616 100644
---
Doing so saves a few lines of code in the driver.
Signed-off-by: Peter Griffin
---
drivers/dma/s3c24xx-dma.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/dma/s3c24xx-dma.c b/drivers/dma/s3c24xx-dma.c
index 17ccdfd..f7d2c7a 100644
--- a/drivers/dma/s3c24xx-dma.
Currently fsl-edma doesn't clk_disable_unprepare()
its clocks on error conditions. This patch adds a
fsl_disable_clocks helper for this, and also only
disables clocks which were enabled if encountering
an error whilst enabling clocks.
Signed-off-by: Peter Griffin
---
drivers/dma/fsl-edma.c | 19
It is useful to print the error code as part of the error
message.
Signed-off-by: Peter Griffin
---
drivers/dma/fsl-edma.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/fsl-edma.c b/drivers/dma/fsl-edma.c
index 7208fc9..cc06eea 100644
--- a/drivers/dma/fsl
Hi,
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.7-rc2 next-20160607]
[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/Peter-Griffin/Add-support-for-FDMA-DMA
On Tue, Jun 07, 2016 at 08:23:15AM -0700, Paul E. McKenney wrote:
> and if the hardware is not excessively clever (bad bet, by the
> way, long term),
This ^
> > Is there something else than conditional move instructions that could
> > come to play here? Obviously a much smarter CPU could evaluate
The driver defines a variable called __packet but then never
uses it, and does not export it for others to use either. Fix
the warning about undeclared variable by removing it.
drivers/soc/bcm/raspberrypi-power.c:48:3: warning: symbol '__packet' was not
declared. Should it be static?
Signed-off-
On Tue, Jun 07, 2016 at 01:30:17PM +0100, Mel Gorman wrote:
> Mike Galbraith reported that the LTP test case futex_wake04 was broken
> by commit 65d8fc777f6d ("futex: Remove requirement for lock_page()
> in get_futex_key()").
>
> This test case uses futexes backed by hugetlbfs pages and so there i
From: Paul Burton
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit ab4a92e66741b35ca12f8497896bafbe579c28a1 upstream.
When emulating a jalr instruction with rd == $0, the code in
isBranchInstr was incorrectly writing to G
Hi Guenter,
On Tue, Jun 07, 2016 at 08:54:53AM +0200, Willy Tarreau wrote:
> > Jiri provides a branch for 3.12, exactly as you suggested. In his case it is
> > named stable-3.12-queue. Sasha does the same, with linux-3.18.y-queue and
> > linux-4.1.y-queue. Both force-push as needed. I don't see a
From: James Hogan
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit 5daebc477da4dfeb31ae193d83084def58fd2697 upstream.
Commit 85efde6f4e0d ("make exported headers use strict posix types")
changed the asm-generic siginfo.h
kzalloc will issue its own error message including a dump_stack()
so remote the site specific message.
Signed-off-by: Peter Griffin
---
drivers/phy/phy-qcom-ufs-qmp-20nm.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/phy-qcom-ufs-qmp-20nm.c
b/drivers/phy/ph
kzalloc will issue its own error message including a dump_stack()
so remote the site specific message.
Signed-off-by: Peter Griffin
---
drivers/phy/phy-qcom-ufs-qmp-14nm.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/phy/phy-qcom-ufs-qmp-14nm.c
b/drivers/phy/ph
On Tue, 2016-06-07 at 19:50 +0200, Peter Zijlstra wrote:
> On Tue, Jun 07, 2016 at 01:30:17PM +0100, Mel Gorman wrote:
> > Signed-off-by: Mel Gorman
>
> Acked-by: Peter Zijlstra (Intel)
Wants a stable tag so it gets auto-snarfed by Greg?
Hi,
On Mon, Jun 06, 2016 at 05:22:44PM +0530, Laxman Dewangan wrote:
> Maxim PMIC MAX77620 is Power management IC which have multiple
> sub blocks like regulators (DCDC/LDOs), GPIO, RTC, Clock, Watchdog
> timer etc.
>
> Add the driver for watchdog timer under watchdog framework.
> The driver impl
On Tue, Jun 07, 2016 at 02:47:57PM +0100, Mel Gorman wrote:
> On Fri, Jun 03, 2016 at 05:58:40PM -0500, Josh Poimboeuf wrote:
> > Commit cb2517653fcc ("sched/debug: Make schedstats a runtime tunable
> > that is disabled by default") introduced a bug when CONFIG_SCHEDSTATS is
> > enabled and the run
Use stdout-path to specify the console and remove the console argument from
the kernel command line.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/usb_a9g20_common.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/usb_a9g20_common.dtsi
b/arch/
On Tue, Jun 07, 2016 at 08:23:15AM -0700, Paul E. McKenney wrote:
> On Tue, Jun 07, 2016 at 04:59:02PM +0200, Hannes Frederic Sowa wrote:
> > Sorry, to follow-up again on this. Will Deacon's comments were about
> > conditional-move instructions, which this compiler-option would prevent,
> > as far
r in kasan_slab_free().
- change allocation size for double-free tests to 100.
v4 link: https://lkml.org/lkml/2016/5/29/62
Patchset is based on linux-next 'next-20160607'.
Kuthonuzo Luruo (2):
mm, kasan: improve double-free detection
kasan: add double-free tests
include/linux/kasan.
Currently, KASAN may fail to detect concurrent deallocations of the same
object due to a race in kasan_slab_free(). This patch makes double-free
detection more reliable by serializing access to KASAN object metadata.
New functions kasan_meta_lock() and kasan_meta_unlock() are provided to
lock/unloc
Hi! Another problem which I found now:
On Tuesday 07 June 2016 10:33:47 Mario Limonciello wrote:
> + ret = hex2bin(buf, obj->string.pointer + 9, 6);
> + if (!(ret == 0 && is_valid_ether_addr(buf))) {
> + netif_warn(tp, probe, tp->netdev,
> +"Invalid MAC
Hi Jassi,
Thanks for your reply !
On Tue, Jun 7, 2016 at 10:20 AM, Jassi Brar wrote:
> On Tue, May 24, 2016 at 6:31 AM, Hoan Tran wrote:
>> Hi Rob,
>>
>> Thanks for your review !
>>
>> On Mon, May 23, 2016 at 1:30 PM, Rob Herring wrote:
>>>
>>> On Mon, May 16, 2016 at 09:17:25AM -0700, Hoan Tr
This patch adds new tests for KASAN double-free error detection when the
same slab object is concurrently deallocated.
Signed-off-by: Kuthonuzo Luruo
---
Changes in v5:
- Addressed review comment from Alexander Potapenko: changed allocation
size for double-free tests to an innocuous 100.
Chan
On 03/06/2016 at 11:45:38 +0530, Raashid Muhammed wrote :
> From: Raashid Muhammed
>
> Remove leading zeros in OHCI node for at91sam9260 based boards.
>
> Signed-off-by: Raashid Muhammed
> Reviewed-by: Vijay Kumar B.
> ---
> arch/arm/boot/dts/aks-cdu.dts | 2 +-
> arch/arm/boot/
Em Sat, Jun 04, 2016 at 05:36:29AM +, He Kuang escreveu:
> -int unwind__prepare_access(struct thread *thread)
> +int unwind__prepare_access(struct thread *thread, struct map *map)
> {
> + const char *arch;
> + enum dso_type dso_type;
> +
> + if (thread->addr_space) {
> +
On Tue, Jun 07, 2016 at 08:49:14AM -0700, Kees Cook wrote:
> > Heiko Carstens (2):
> > vmlinux.lds.h: allow arch specific handling of ro_after_init data section
> > s390/mm: add proper __ro_after_init support
> >
> > arch/s390/include/asm/cache.h | 3 ---
> > arch/s390/include/asm/section
In 8c05cd08a7 ("PCI: fix offset check for sysfs mmapped files"), try
to check exposed value with resource start/end in proc mmap path.
|start = vma->vm_pgoff;
|size = ((pci_resource_len(pdev, resno) - 1) >> PAGE_SHIFT) + 1;
|pci_start = (mmap_api == PCI_MMAP_PROCFS) ?
|
From: Megha Dey
Herbert wants the sha1-mb algorithm to have an async implementation:
https://lkml.org/lkml/2016/4/5/286.
Currently, sha1-mb uses an async interface for the outer algorithm
and a sync interface for the inner algorithm. This patch introduces
a async interface for even the inner algo
-Original Message-
From: Herbert Xu [mailto:herb...@gondor.apana.org.au]
Sent: Tuesday, June 7, 2016 3:35 AM
To: Dey, Megha
Cc: tim.c.c...@linux.intel.com; da...@davemloft.net;
linux-cry...@vger.kernel.org; linux-kernel@vger.kernel.org; Yu, Fenghua
; Megha Dey
Subject: Re: [PATCH V2
This one is preparing patch for next one:
PCI: Let pci_mmap_page_range() take resource addr
We need to pass extra resource pointer to avoid searching that again
for powerpc and microblaze prot set operation.
update for fixing bisectibility problem found by build test robot.
Signed-off-by: Ying
On Tue, Jun 07, 2016 at 06:52:22PM +0200, Borislav Petkov wrote:
> +void mce_log(struct mce *m)
> {
> unsigned next, entry;
>
> + if (!in_atomic() && memory_error(m) && mce_usable_address(m))
> + if (!ce_add_elem(m->addr >> PAGE_SHIFT))
> + return;
> +
>
On 06/07/2016 10:31 AM, Christoph Hellwig wrote:
Of course you can, and every user of configfs relies on being able
to create directories from the kernel using either the default_groups
list, or through the use of configfs_register_group().
Apparently configfs_register_group() has been added la
On Tue, Jun 7, 2016 at 11:07 AM, Heiko Carstens
wrote:
> On Tue, Jun 07, 2016 at 08:49:14AM -0700, Kees Cook wrote:
>> > Heiko Carstens (2):
>> > vmlinux.lds.h: allow arch specific handling of ro_after_init data section
>> > s390/mm: add proper __ro_after_init support
>> >
>> > arch/s390/incl
On Tue, Jun 7, 2016 at 11:11 AM, Kani, Toshimitsu wrote:
> On Sat, 2016-06-04 at 13:52 -0700, Dan Williams wrote:
> :
>> diff --git a/drivers/nvdimm/region_devs.c b/drivers/nvdimm/region_devs.c
>> index 420e1a5e2250..5b6f85d00bb5 100644
>> --- a/drivers/nvdimm/region_devs.c
>> +++ b/drivers/nvdim
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workqueue srp_remove_wq with
workitem &target->remove_work, is a work queue for the SRP target removal.
WQ_MEM_RECLAIM has been set to ensure forward progress under memory
pressure.
Since there ar
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since cm.wq has workitem
&cm_id_priv->timewait_info->work.work (maps to cm_work_handler) is
involved in normal device operation. When a cm mad is received, it is
queued to a cm workqueue for processing. The
The helper function usb_of_get_child_node() is defined in the
header but this was not included. Fix the warning
about usb_of_get_child_node() not being declared by adding the
right include. Fixes:
drivers/usb/core/of.c:31:20: warning: symbol 'usb_of_get_child_node' was not
declared. Should it be
On Tue, Jun 7, 2016 at 4:52 AM, Wanpeng Li wrote:
> 2016-06-07 18:39 GMT+08:00 Paolo Bonzini :
> [...]
>>
>> John Stultz also reported a similar issue after guest S3.
>
> Since there is cpu hot-unplug during S3.
While I'm excited to finally see some progress on this, I
unfortunately can't verify
On Tue, Jun 07, 2016 at 07:49:53PM +0200, Willy Tarreau wrote:
>
> Now done. Please find it here :
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/linux-stable.git
> linux-3.10.y-queue
>
> It's a fork of Greg's linux-stable. I cleaned it up from irrelevant
> tags and branches. If y
The RTL8153-AD supports a persistent system specific MAC address.
This means a device plugged into two different systems with host side
support will show different (but persistent) MAC addresses.
This information for the system's persistent MAC address is burned in when
the system HW is built and
There exists potential memory leak in ufshcd_parse_clock_info(),
this patch fixes it.
Signed-off-by: Tiezhu Yang
---
drivers/scsi/ufs/ufshcd-pltfrm.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/ufs/ufshcd-pltfrm.c b/drivers/scsi/ufs/ufshcd-pltfrm.c
Hi Peter,
On Tue, Jun 07, 2016 at 06:50:09PM +0100, Peter Griffin wrote:
> kzalloc will issue its own error message including a dump_stack()
> so remote the site specific message.
>
> Signed-off-by: Peter Griffin
> ---
> drivers/phy/phy-qcom-ufs-qmp-14nm.c | 4 +---
> 1 file changed, 1 insertio
On 07.06.2016 17:23, Paul E. McKenney wrote:
> On Tue, Jun 07, 2016 at 04:59:02PM +0200, Hannes Frederic Sowa wrote:
>> On 07.06.2016 15:06, Paul E. McKenney wrote:
>>> On Tue, Jun 07, 2016 at 02:41:44PM +0200, Hannes Frederic Sowa wrote:
On 07.06.2016 09:15, Peter Zijlstra wrote:
>>
>
> > + int cpu, cnt = num_online_cpus();
> > + cpumask_t mask = { CPU_BITS_NONE };
> > + size_t size = 4097; /* must be <= KMALLOC_MAX_CACHE_SIZE/2 */
> Can you please explicitly calculate |size| from KMALLOC_MAX_CACHE_SIZE?
> > +
> > + if (cnt == 1)
> > + r
On Tue, Jun 07, 2016 at 07:48:53PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 07, 2016 at 08:23:15AM -0700, Paul E. McKenney wrote:
> > and if the hardware is not excessively clever (bad bet, by the
> > way, long term),
>
> This ^
>
> > > Is there something else than conditional move instructions
The previous workaround may still fail as there are actually 4 retries to
be done to ensure the communication succeed. Also, some I2C adapter drivers
may return -EIO instead of -ENXIO.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-rv8803.c | 6 +++---
1 file changed, 3 insertions(+), 3 de
On Tue, Jun 07, 2016 at 07:01:07PM +0100, Will Deacon wrote:
> On Tue, Jun 07, 2016 at 08:23:15AM -0700, Paul E. McKenney wrote:
> > On Tue, Jun 07, 2016 at 04:59:02PM +0200, Hannes Frederic Sowa wrote:
> > > Sorry, to follow-up again on this. Will Deacon's comments were about
> > > conditional-mov
On Sat, 2016-06-04 at 13:52 -0700, Dan Williams wrote:
:
> diff --git a/drivers/nvdimm/region_devs.c b/drivers/nvdimm/region_devs.c
> index 420e1a5e2250..5b6f85d00bb5 100644
> --- a/drivers/nvdimm/region_devs.c
> +++ b/drivers/nvdimm/region_devs.c
> @@ -803,11 +803,29 @@ EXPORT_SYMBOL_GPL(nvdimm_v
On 06/07/2016 11:16 AM, Bhaktipriya Shridhar wrote:
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workqueue srp_remove_wq with
workitem &target->remove_work, is a work queue for the SRP target removal.
WQ_MEM_RECLAIM has been set to ensure
Hello Stephen,
On Wed, Jun 1, 2016 at 7:15 PM, Stephen Boyd wrote:
> Now that we have clk_hw based provider APIs to register clks, we
> can get rid of struct clk pointers while registering clks in
> these drivers, allowing us to move closer to a clear split of
> consumer and provider clk APIs.
>
While testing the deadline scheduler + cgroup setup I hit this
warning.
[ 132.612935] [ cut here ]
[ 132.612951] WARNING: CPU: 5 PID: 0 at kernel/softirq.c:150
__local_bh_enable_ip+0x6b/0x80
[ 132.612952] Modules linked in: (a ton of modules...)
[ 132.612981] CPU: 5 PI
On Tue, Jun 07, 2016 at 07:01:07PM +0100, Will Deacon wrote:
> On Tue, Jun 07, 2016 at 08:23:15AM -0700, Paul E. McKenney wrote:
> > On Tue, Jun 07, 2016 at 04:59:02PM +0200, Hannes Frederic Sowa wrote:
> > > Sorry, to follow-up again on this. Will Deacon's comments were about
> > > conditional-mov
On 06/07/2016 02:50 PM, Javier Martinez Canillas wrote:
> Hello Stephen,
>
> On Wed, Jun 1, 2016 at 7:15 PM, Stephen Boyd wrote:
>> Now that we have clk_hw based provider APIs to register clks, we
>> can get rid of struct clk pointers while registering clks in
>> these drivers, allowing us to mov
Hi,
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v4.7-rc2 next-20160607]
[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/Ben-Dooks/USB-core-fix-missing-include-linux-usb
On Tue, Jun 07, 2016 at 07:29:37PM +0800, Zhao Lei wrote:
> In current system, when we set core_pattern to a pipe, both pipe program
> and program's output are in host's filesystem.
> But when we set core_pattern to a file, the container will write dump
> into container's filesystem.
>
> For examp
This change reorders some operations in brcmf_setup_ifmodes in hope to
make it simpler:
1) It allocates arrays right before filling them. This way it's easier
to follow requested array length as it's immediately followed by
code filling it. It's easier to check e.g. why we need 4 entries for
Hi Mark,
Thanks for reviewing.
On 06/03/2016 11:57 AM, Mark Rutland wrote:
On Fri, Jun 03, 2016 at 11:40:28AM -0700, Andrew Duggan wrote:
Signed-off-by: Andrew Duggan
---
.../devicetree/bindings/input/rmi4/rmi_2d_sensor.txt | 5 +
drivers/input/rmi4/rmi_2d_sensor.c
On Wed, 2016-06-08 at 02:00 +0800, Tiezhu Yang wrote:
> There exists potential memory leak in ufshcd_parse_clock_info(),
> this patch fixes it.
What makes you think there's a leak here? These are all devm_
allocations, so they're all freed when the device is. If an error is
returned, the device
Dma_pool_zalloc combines dma_pool_alloc and memset 0.
The Coccinelle semantic patch used to make this change is as follows:
@@
type T;
T *d;
expression e;
statement S;
@@
d =
-dma_pool_alloc
+dma_pool_zalloc
(...);
if (!d) S
- memset(d, 0
On Tue, Jun 07, 2016 at 11:32:42AM -0700, Bart Van Assche wrote:
> On 06/07/2016 11:16 AM, Bhaktipriya Shridhar wrote:
> > alloc_workqueue replaces deprecated create_workqueue().
> >
> > A dedicated workqueue has been used since the workqueue srp_remove_wq with
> > workitem &target->remove_work, i
When many threads are trying to add or delete inode to or from
a superblock's s_inodes list, spinlock contention on the list can
become a performance bottleneck.
This patch changes the s_inodes field to become a per-cpu list with
per-cpu spinlocks. As a result, the following superblock inode list
Linked list is used everywhere in the Linux kernel. However, if many
threads are trying to add or delete entries into the same linked list,
it can create a performance bottleneck.
This patch introduces a new per-cpu list subystem with associated
per-cpu locks for protecting each of the lists indiv
From: Jan Kara
fsnotify_unmount_inodes() played complex tricks to pin next inode in the
sb->s_inodes list when iterating over all inodes. If we switch to
keeping current inode pinned somewhat longer, we can make the code much
simpler and standard.
Signed-off-by: Jan Kara
Signed-off-by: Waiman L
v6->v7:
- Fix the race condition in __pcpu_list_next_cpu() as reported by
Jan Kara.
- No changes in patches 2-4.
v5->v6:
- Remove patch 5 which can increase the kernel testing matrix.
- Disable preemption in pcpu_list_add() as it was complained by
the 0-day test even though it is not tec
From: Jan Kara
evict_inodes() and invalidate_inodes() use list_for_each_entry_safe()
to iterate sb->s_inodes list. However, since we use i_lru list entry for
our local temporary list of inodes to destroy, the inode is guaranteed
to stay in sb->s_inodes list while we hold sb->s_inode_list_lock. So
On Tue, Jun 07, 2016 at 03:51:15PM -0300, Daniel Bristot de Oliveira wrote:
> While testing the deadline scheduler + cgroup setup I hit this
> warning.
>
> [ 132.612935] [ cut here ]
> [ 132.612951] WARNING: CPU: 5 PID: 0 at kernel/softirq.c:150
> __local_bh_enable_ip+0x
On 06/07/2016 03:24 PM, Waiman Long wrote:
v6->v7:
- Fix the race condition in __pcpu_list_next_cpu() as reported by
Jan Kara.
- No changes in patches 2-4.
v5->v6:
- Remove patch 5 which can increase the kernel testing matrix.
- Disable preemption in pcpu_list_add() as it was complai
alloc_workqueue replaces deprecated create_workqueue().
Since the driver is infiniband which can be used as block device and the
workqueue seems involved in regular operation of the device, so a
dedicated workqueue has been used with WQ_MEM_RECLAIM set to guarantee
forward progress under memory p
On 06/07/2016 03:29 PM, Waiman Long wrote:
Hi, I am resending this patch series as I haven't received any
feedback to see if further change is needed or is good enough to get
merged.
Sorry, that patch series isn't the latest one. Please ignore it. I am
going to resend the latest one out.
From: Jan Kara
evict_inodes() and invalidate_inodes() use list_for_each_entry_safe()
to iterate sb->s_inodes list. However, since we use i_lru list entry for
our local temporary list of inodes to destroy, the inode is guaranteed
to stay in sb->s_inodes list while we hold sb->s_inode_list_lock. So
When many threads are trying to add or delete inode to or from
a superblock's s_inodes list, spinlock contention on the list can
become a performance bottleneck.
This patch changes the s_inodes field to become a dlock list which
is a distributed set of lists with per-list spinlocks. As a result,
This is a follow up of the following patchset:
[PATCH v7 0/4] vfs: Use per-cpu list for SB's s_inodes list
https://lkml.org/lkml/2016/4/12/1009
The main change is the renaming of percpu list to dlock list, as
suggested by Christoph Lameter. It also adds a new patch from Boqun
Feng to add the
Linked list is used everywhere in the Linux kernel. However, if many
threads are trying to add or delete entries into the same linked list,
it can create a performance bottleneck.
This patch introduces a new list APIs that provide a set of distributed
lists (one per CPU), each of which is protecte
From: Jan Kara
fsnotify_unmount_inodes() played complex tricks to pin next inode in the
sb->s_inodes list when iterating over all inodes. If we switch to
keeping current inode pinned somewhat longer, we can make the code much
simpler and standard.
Signed-off-by: Jan Kara
Signed-off-by: Waiman L
From: Boqun Feng
Add __percpu modifier properly to help:
1. Differ pointers to actual structures with those to percpu
structures, which could improve readability.
2. Prevent sparse from complaining about "different address spaces"
Signed-off-by: Boqun Feng
Signed-off-by: Wai
On Mon, Jun 6, 2016 at 6:50 PM, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Jun 06, 2016 at 09:42:03AM -0700, Chris Brand wrote:
>> On Thu, Jun 2, 2016 at 7:38 PM, Sebastian Reichel wrote:
>> > Feel free to queue it via arm-soc with
>> >
>> > Acked-By: Sebastian Reichel
>> >
>> > If I didn't over
Fixes for two more bugs I found in the schedstats code, in addition to
to the other patches I sent out:
https://lkml.kernel.org/r/cover.1464994423.git.jpoim...@redhat.com
Josh Poimboeuf (2):
sched/debug: fix 'schedstats=enable' cmdline option
sched/debug: fix deadlock when enabling sched
When enabling sched trace events via:
echo 1 > /sys/kernel/debug/tracing/events/sched/enable
I see a hang, with the following BUG in the printk buffer:
BUG: spinlock recursion on CPU#1, swapper/1/0
lock: 0x88007d5d8c00, .magic: dead4ead, .owner: swapper/1/0, .owner_cpu:
1
CPU: 1 PI
On Tue, Jun 07, 2016 at 04:03:40PM +0100, Robin Murphy wrote:
> On 07/06/16 15:43, Daniel Vetter wrote:
> > On Tue, Jun 07, 2016 at 01:18:09PM +0100, Robin Murphy wrote:
> > > In the absence of an fb_mmap callback, the fbdev code falls back to a
> > > naive implementation which relies upon the DMA
Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu:
> On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote:
>
> SNIP
>
> > For using remote libunwind libraries, reference this:
> > http://thread.gmane.org/gmane.linux.kernel/2224430
> >
> > and now we can use LIBUNWIND_DIR to spec
The 'schedstats=enable' option doesn't work, and also produces the
following warning during boot:
WARNING: CPU: 0 PID: 0 at /home/jpoimboe/git/linux/kernel/jump_label.c:61
static_key_slow_inc+0x8c/0xa0
static_key_slow_inc used before call to jump_label_init
Modules linked in:
CPU: 0 PID:
On Tue, Jun 07, 2016 at 11:21:10PM +0530, Sumit Semwal wrote:
> On 07-Jun-2016 2:32 PM, "Jani Nikula" wrote:
> >
> > On Tue, 07 Jun 2016, Vinay Simha BN wrote:
> > > Provide a small convenience wrapper that transmits
> > > a set_tear_scanline command.
> > >
> > > Cc: Archit Taneja
> > > Cc: John
;
> url:
> https://github.com/0day-ci/linux/commits/Andrew-Morton/tile-early_printk-o-is-always-required/20160607-043356
> base:
> https://git.kernel.org/pub/scm/linux/kernel/git/cmetcalf/linux-tile.git master
> config: tile-allnoconfig (attached as .config)
> compiler: t
On Tue, Jun 07, 2016 at 02:43:17PM -0500, Josh Poimboeuf wrote:
> 1. Instead of just warning and allowing the tracepoints to be broken,
>I'd argue that it would be better to make them work by forcing
>schedstats enabled and printing a warning about that, which is what's
Forcing them enable
On Tue 07 Jun 09:18 PDT 2016, Peter Griffin wrote:
> Some firmware and rproc drivers such as slim core don't have a
> resource table. To avoid having to fudge an empty table
> in the rproc driver this patch introduces a new has_rsctable
> flag. rproc drivers which don't require a rsc table can set
On 06/07/2016 12:21 PM, Tejun Heo wrote:
On Tue, Jun 07, 2016 at 11:32:42AM -0700, Bart Van Assche wrote:
On 06/07/2016 11:16 AM, Bhaktipriya Shridhar wrote:
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workqueue srp_remove_wq with
worki
On Tue, 2016-06-07 at 12:23 -0400, Johannes Weiner wrote:
> Hi Tim,
>
> On Mon, Jun 06, 2016 at 04:50:23PM -0700, Tim Chen wrote:
> >
> > On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> > >
> > > To tell inactive from active refaults, a page flag is introduced that
> > > marks pages
Le 29/05/2016 à 00:01, Sinan Kaya a écrit :
> The code was allowing platform devices to be used without a supporting
> VFIO reset driver. The hardware can be left in some inconsistent state
> after a guest machine abort.
>
> The reset driver will put the hardware back to safe state and disable
>
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been used since the workqueue
mlxsw_wq is used for FDB notif. processing with workitems that are
involved in normal device operation && because it's a network device
which can be depended upon during memory reclaim.
On 06/07/2016 12:56 PM, Bart Van Assche wrote:
On 06/07/2016 12:21 PM, Tejun Heo wrote:
On Tue, Jun 07, 2016 at 11:32:42AM -0700, Bart Van Assche wrote:
On 06/07/2016 11:16 AM, Bhaktipriya Shridhar wrote:
alloc_workqueue replaces deprecated create_workqueue().
A dedicated workqueue has been u
701 - 800 of 1210 matches
Mail list logo
