On Wed, Mar 26, 2014 at 1:27 PM, Ben Skeggs wrote:
> On Tue, Mar 25, 2014 at 9:10 AM, Thierry Reding
> wrote:
>> On Mon, Mar 24, 2014 at 05:42:33PM +0900, Alexandre Courbot wrote:
>>> GK20A does not embed a dedicated COPY engine and thus cannot allocate
>>> the copy channel that
On 16 April 2014 11:18, Srivatsa S. Bhat
wrote:
> From: Srivatsa S. Bhat
> Subject: [PATCH] cpufreq, powernv: Fix build failure on UP
>
> Paul Gortmaker reported the following build failure of the powernv cpufreq
> driver on UP configs:
>
> drivers/cpufreq/powernv-cpufreq.c:241:2: error:
On Wed, 16 Apr 2014 05:46:18 +0100 Al Viro wrote:
> On Wed, Apr 16, 2014 at 02:03:37PM +1000, NeilBrown wrote:
> > namespace_sem can be taken while various i_mutex locks are held, so we
> > need to avoid reclaim from blocking on an FS (particularly loop-back
> > NFS).
>
> I would really prefer
On Wed, Apr 16, 2014 at 02:03:36PM +1000, NeilBrown wrote:
> lockdep reports a locking chain
>
> sk_lock-AF_INET --> rtnl_mutex --> pcpu_alloc_mutex
>
> As sk_lock may be needed to reclaim memory, allowing that
> reclaim while pcu_alloc_mutex is held can lead to deadlock.
> So set PF_FSTRANS
On 04/15/2014 07:41 PM, Paul Gortmaker wrote:
> Hi all,
>
> This new driver is causing build fails on linux-next for non-SMP.
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/10911507/
>
> I didn't bisect since there are only two commits in total. :)
>
> Looks like some header foo where
On Tue, 15 Apr 2014 22:13:46 -0700 Eric Dumazet
wrote:
> On Wed, 2014-04-16 at 14:03 +1000, NeilBrown wrote:
> > sk_lock can be taken while reclaiming memory (in nfsd for loop-back
> > NFS mounts, and presumably in nfs), and memory can be allocated while
> > holding sk_lock, at least via:
> >
>
Freescale's Integrated Flash controller(IFC) module is used to handle
devices such as NOR, NAND, FPGA and ASIC.
Update same in Help section of Kconfig for IFC.
Signed-off-by: Prabhakar Kushwaha
---
drivers/memory/Kconfig |4
1 file changed, 4 insertions(+)
diff --git
On 04/16/2014 01:19 PM, 管雪涛 wrote:
> This problem has been fixed, but I didn't submit.
> Anyway, I can apply your version.
>
> Acked-by: Xuetao Guan
>
OK, thanks.
> - Chen Gang 写道：
>> Missing related ')', the related compiling error:
>>
>> CC [M] drivers/gpu/drm/udl/udl_fb.o
>>
(2014/04/16 0:10), Sasha Levin wrote:
>>> - Memory access size. We're currently decoding the size (in bytes) of an
>>> address size, and operand size. kmemcheck would like to know in addition
>>> how many bytes were read/written from/to an address by a given instruction,
>>> so we also keep the
On 15 April 2014 18:14, Frederic Weisbecker wrote:
> Sure but check out the static_key_false() in the implementation of
> tick_nohz_full_enabled().
> That's where the magic hides.
> No problem, the jump label/static key code is quite tricky. And its use
> can be easily missed, as in here.
>
>
On 04/16/2014 01:15 PM, 管雪涛 wrote:
> Acked-by: Xuetao Guan
>
OK, thanks.
> - Chen Gang 写道：
>> unicore32 supports STRICT_DEVMEM, so it needs devmem_is_allowed(), like
>> some of other architectures have done (e.g. arm, powerpc, x86 ...).
>>
>> The related error with allmodconfig:
>>
>>
On Wed, 2014-04-16 at 07:37 +0200, Fabian Frederick wrote:
> -Convert printk(KERN_WARNING|KERN_ERR|KERN_INFO to pr_foo()
> -Define pr_fmt where it doesn't break existing format.
[]
> (other ones ?)
[]
> diff --git a/drivers/pci/hotplug/cpqphp_core.c
> b/drivers/pci/hotplug/cpqphp_core.c
[]
> @@
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
ERROR: "kmalloc_order" [drivers/net/wireless/brcm80211/brcmfmac/brcmfmac.ko]
undefined!
Caused by commit a3ed1ed24850 ("mm: get rid of __GFP_KMEMCG").
I added the following
From: Mr. RWH Lee
Email: (1952025...@qq.com)
Good Day
I am Mr. Raymond Wing Hung LEE the Executive Director and chief Financial
officer of Fubon Bank (Hong Kong) Limited. I need your assistance in
transferring funds worth $47.1million dollars.
Kindly write back to (1952025...@qq.com), I shall
On Wed, Apr 16, 2014 at 02:03:36PM +1000, NeilBrown wrote:
> Currently both xfs and nfs will handle PF_FSTRANS by disabling
> __GFP_FS.
>
> Make this effect global by repurposing memalloc_noio_flags (which
> does the same thing for PF_MEMALLOC_NOIO and __GFP_IO) to generally
> impost the task
-Convert printk(KERN_WARNING|KERN_ERR|KERN_INFO to pr_foo()
-Define pr_fmt where it doesn't break existing format.
Cc: Bjorn Helgaas
Cc: Andrew Morton
Cc: Joe Perches
Signed-off-by: Fabian Frederick
---
v2: (From suggestions by Joe Perches)
-Coalesce format fragments.
-Remove 'PCI: ' in
Replace blocks of code which checks whether pwq is defalut with
jump to use_dfl_pwq. It is same as before.
Signed-off-by: Daeseok Youn
---
kernel/workqueue.c |5 +
1 files changed, 1 insertions(+), 4 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index
wq_update_unbound_numa() failure path has the following two bugs.
- alloc_unbound_pwq() is called without holding wq->mutex;
however, if the allocation fails, it jumps to out_unlock
which tries to unlock wq->mutex.
- The function should switch to dfl_pwq on failure
but didn't do so after
(2014/04/16 13:03), Sasha Levin wrote:
> On 04/15/2014 11:54 PM, H. Peter Anvin wrote:
>> On 04/15/2014 08:47 PM, Sasha Levin wrote:
Yes, if kmemcheck for some reason needs to figure out if an instruction
is a MOV variant we'll need to list quite a few mnemonics, but that list
On Apr 15, 2014, at 11:07 PM, Theodore Ts'o wrote:
> On Wed, Apr 16, 2014 at 10:30:10AM +0530, Amit Sahrawat wrote:
>> 4) Corrupt the block group ‘1’ by writing all ‘1’, we had one file
>> with all 1’s, so using ‘dd’ –
>> dd if=i_file of=/dev/sdb1 bs=4096 seek=17 count=1
>> After this mount
On Tue, Apr 15, 2014 at 08:54:19PM -0700, Paul E. McKenney wrote:
> But falling back on the old ways of doing this at least looks a bit
> nicer:
>
> static inline bool rcu_should_resched(void)
> {
> int t;
> int *tp = _cpu(rcu_cond_resched_count,
>
wq_update_unbound_numa() failure path has the following two bugs.
- alloc_unbound_pwq() is called without holding wq->mutex;
however, if the allocation fails, it jumps to out_unlock
which tries to unlock wq->mutex.
- The function should switch to dfl_pwq on failure
but didn't do so after
On Tue, 2014-04-15 at 22:04 -0700, Brian Norris wrote:
> Hi Sergei,
>
> On Tue, Dec 17, 2013 at 11:37:40PM +0400, Sergei Ianovich wrote:
> > This provides an MTD device driver for 512kB of battery backed up SRAM
> > on ICPDAS LP-8X4X programmable automation controllers.
> >
> > SRAM chip is
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from mm/vmscan.c:50:0:
include/linux/swapops.h: In function 'is_swap_pte':
include/linux/swapops.h:57:2: error: implicit declaration of function
This problem has been fixed, but I didn't submit.
Anyway, I can apply your version.
Acked-by: Xuetao Guan
- Chen Gang 写道：
> Missing related ')', the related compiling error:
>
> CC [M] drivers/gpu/drm/udl/udl_fb.o
> drivers/gpu/drm/udl/udl_fb.c: In function ‘udl_fb_mmap’:
>
On Tue, Apr 15, 2014 at 03:17:55PM -0700, Paul E. McKenney wrote:
> Hello, Christoph,
>
> I have a patch that currently uses __this_cpu_inc_return() to increment a
> per-CPU variable, but without preemption disabled. Of course, given that
> preemption is enabled, it might well end up picking up
Acked-by: Xuetao Guan
- Chen Gang 写道：
> unicore32 supports STRICT_DEVMEM, so it needs devmem_is_allowed(), like
> some of other architectures have done (e.g. arm, powerpc, x86 ...).
>
> The related error with allmodconfig:
>
> CC drivers/char/mem.o
> drivers/char/mem.c: In
Hi all,
Please ignore this, since it turns out that is doesn't solve the
problem.
Instead, please consider the following patch.
>From ac9ad0b1de42dc311323b9c3b8f431f4b097b43b Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Wed, 16 Apr 2014 10:47:06 +0900
Subject: [PATCH] f2fs: adjust free mem
On Wed, 2014-04-16 at 14:03 +1000, NeilBrown wrote:
> sk_lock can be taken while reclaiming memory (in nfsd for loop-back
> NFS mounts, and presumably in nfs), and memory can be allocated while
> holding sk_lock, at least via:
>
> inet_listen -> inet_csk_listen_start ->reqsk_queue_alloc
>
> So
Change log from v1:
o change the patch, which includes this bug fix
>From 0f3b8427b40b9ace829ba0b16336d5cd67589022 Mon Sep 17 00:00:00 2001
From: Jaegeuk Kim
Date: Tue, 15 Apr 2014 16:04:15 +0900
Subject: [PATCH] f2fs: call redirty_page_for_writepage
This patch replace some general codes with
wq_update_unbound_numa() failure path has the following two bugs.
- alloc_unbound_pwq() is called without holding wq->mutex;
however, if the allocation fails, it jumps to out_unlock
which tries to unlock wq->mutex.
- The function should switch to dfl_pwq on failure
but didn't do so after
Hi Sachin,
On 04/16/2014 02:04 PM, Sachin Kamat wrote:
> Hi Chanwoo,
>
> On 16 April 2014 10:25, Chanwoo Choi wrote:
>> Hi Sachin,
>>
>> On 04/16/2014 01:44 PM, Chanwoo Choi wrote:
>>> Hi Sachin,
>>>
>>> On 04/16/2014 12:48 PM, Sachin Kamat wrote:
Hi Chanwoo,
On 14 April 2014
On Wed, Dec 25, 2013 at 12:40:50PM +, Caizhiyong wrote:
> From: Cai Zhiyong
> Date: Wed, 25 Dec 2013 20:11:15 +0800
> Subject: [PATCH] mtd: nand: remove unused function input parameter
>
> The nand_get_flash_type parameter "busw" input value is not used by any
> branch, and it is updated
On Wed, Apr 16, 2014 at 10:30:10AM +0530, Amit Sahrawat wrote:
> 4)Corrupt the block group ‘1’ by writing all ‘1’, we had one file
> with all 1’s, so using ‘dd’ –
> dd if=i_file of=/dev/sdb1 bs=4096 seek=17 count=1
> After this mount the partition – create few random size files and then
> ran
Hi Sergei,
On Tue, Dec 17, 2013 at 11:37:40PM +0400, Sergei Ianovich wrote:
> This provides an MTD device driver for 512kB of battery backed up SRAM
> on ICPDAS LP-8X4X programmable automation controllers.
>
> SRAM chip is connected via FPGA and is not accessible without a driver,
> unlike flash
Hi Chanwoo,
On 16 April 2014 10:25, Chanwoo Choi wrote:
> Hi Sachin,
>
> On 04/16/2014 01:44 PM, Chanwoo Choi wrote:
>> Hi Sachin,
>>
>> On 04/16/2014 12:48 PM, Sachin Kamat wrote:
>>> Hi Chanwoo,
>>>
>>> On 14 April 2014 14:37, Chanwoo Choi wrote:
This patch control special clock for ADC
Thanks Ted, for the detailed reply.
We could not retain the original HDD – on which we got the issue. In
order to replicate the problem we did steps like this:
1) Make 250MB partition
2) Format the partition with blocksize ‘4K’
3) Using dumpe2fs – get the block group information
Hi Sachin,
On 04/16/2014 01:44 PM, Chanwoo Choi wrote:
> Hi Sachin,
>
> On 04/16/2014 12:48 PM, Sachin Kamat wrote:
>> Hi Chanwoo,
>>
>> On 14 April 2014 14:37, Chanwoo Choi wrote:
>>> This patch control special clock for ADC in Exynos series's FSYS block.
>>> If special clock of ADC is
(2014/04/16 11:33), Vivek Goyal wrote:
> On Wed, Apr 16, 2014 at 10:28:39AM +0900, Masami Hiramatsu wrote:
>> (2014/04/15 23:08), Vivek Goyal wrote:
>>> On Tue, Apr 15, 2014 at 10:37:40AM +0900, Masami Hiramatsu wrote:
>>>
>>> [..]
> Masami,
>
> So what's the alternative to kdump which
On Wed, Apr 16, 2014 at 02:03:37PM +1000, NeilBrown wrote:
> namespace_sem can be taken while various i_mutex locks are held, so we
> need to avoid reclaim from blocking on an FS (particularly loop-back
> NFS).
I would really prefer to deal with that differently - by explicit change of
gfp_t
Hi Sachin,
On 04/16/2014 12:48 PM, Sachin Kamat wrote:
> Hi Chanwoo,
>
> On 14 April 2014 14:37, Chanwoo Choi wrote:
>> This patch control special clock for ADC in Exynos series's FSYS block.
>> If special clock of ADC is registerd on clock list of common clk framework,
>> Exynos ADC drvier
Samsung GH7 has four PCIe controllers which can be used as root
complex for PCIe interface.
Signed-off-by: Jingoo Han
---
drivers/pci/host/Kconfig |2 +-
drivers/pci/host/pci-exynos.c | 135 ++---
2 files changed, 126 insertions(+), 11 deletions(-)
Add ARM64 PCI support for Synopsys designware PCIe, by using
pcie arm64 arch support and creating generic pcie bridge from
device tree.
Signed-off-by: Jingoo Han
---
drivers/pci/host/pcie-designware.c | 32
1 file changed, 32 insertions(+)
diff --git
Hi,
On Tue, Apr 15, 2014 at 01:55:38PM -0400, Alan Stern wrote:
> On Tue, 15 Apr 2014, Felipe Balbi wrote:
>
> > > 2. Does device need to know OUT transactions before hand so that OUT
> > > requests are queued for endpoint before packets are received
> > > from host?
> >
> > well, no. Gadget
This patch adds support for Samsung GH7 PCIe host controller.
Samsung GH7 PCIe controller driver has dependency on the PCI arm64
arch support. So, the Liviu Dudau's patcheset for creating generic
host_bridge from device tree [1] and supporting PCI in AArch64 [2]
are required.
This patch is marked
On Tue, Apr 15, 2014 at 08:08:32PM +0200, Paul Bolle wrote:
> On Tue, 2014-04-15 at 12:23 -0500, Felipe Balbi wrote:
> > so this means that drivers/usb/gadget/mv_u3d_core.c isn't used either ?
>
> Why should it? There's no dependency on CPU_MMP3 for USB_MV_U3D anymore,
> is there?
no, but the
Hi All,
This the 2nd patchset supports 4 levels of tranlsation tables for ARM64.
Firstly, The patchset decouples page size from level of translation tables
as taking account into the comment from Catalin Marinas:
http://www.spinics.net/linux/lists/arm-kernel/msg319552.html
Then, it implements 4
This patch separates page size from level of translation tables in
configuration. It facilitates introduction of different options,
such as 4KB + 4 levels, 16KB + 4 levels and 64KB + 3 levels, easily.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/Kconfig
This patch adds hardware definition and types for 4 levels of
translation tables with 4KB pages.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/include/asm/pgtable-4level-hwdef.h | 50 +
arch/arm64/include/asm/pgtable-4level-types.h | 71
This patch adds memory layout and translation lookup information
about 48-bit address space with 4K pages. The description is based
on 4 levels of translation tables.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
Documentation/arm64/memory.txt | 59
This patch implements 4 levels of translation tables since 3 levels
of page tables with 4KB pages cannot support 40-bit physical address
space described in [1] due to the following issue.
It is a restriction that kernel logical memory map with 4KB + 3 levels
This patch adds a kernel configuration for VA_BITS.
It helps to prevent unnecessary #ifdef statements insertions
for VA_BITS when implementing different page sizes and level of
translation tables.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/Kconfig |
This patch adds 4 levels of translation tables implementation for both
HYP and stage2. A combination of 4KB + 4 levels host and 4KB + 4 levels
guest can run on ARMv8 architecture as introducing this feature.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
This patch fixed the following checkpatch complaint as using pr_*
instead of printk.
WARNING: printk() should include KERN_ facility level
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/kernel/traps.c | 14 +++---
1 file changed, 7 insertions(+), 7
I really wonder if it makes sense...
On April 15, 2014 9:03:48 PM PDT, Sasha Levin wrote:
>On 04/15/2014 11:54 PM, H. Peter Anvin wrote:
>> On 04/15/2014 08:47 PM, Sasha Levin wrote:
>>> >
>>> > Yes, if kmemcheck for some reason needs to figure out if an
>instruction
>>> > is a MOV variant
Currently kswapd sets current->lockdep_reclaim_gfp but the first
memory allocation call will clear it. So the setting does no good.
Thus the lockdep_set_current_reclaim_state call in kswapd() is
ineffective.
With this patch we always save the old value and then restore it,
so lockdep gets to
Currently both xfs and nfs will handle PF_FSTRANS by disabling
__GFP_FS.
Make this effect global by repurposing memalloc_noio_flags (which
does the same thing for PF_MEMALLOC_NOIO and __GFP_IO) to generally
impost the task flags on a gfp_t.
Due to this repurposing we change the name of
If an incoming NFS request is coming from the local host, then
nfsd will need to perform some special handling. So detect that
possibility and make the source visible in rq_local.
Signed-off-by: NeilBrown
---
include/linux/sunrpc/svc.h |1 +
include/linux/sunrpc/svc_xprt.h |1 +
If a localhost mount is present, then it is easy to deadlock NFS by
nfsd entering direct reclaim and calling nfs_release_page() which
requires nfsd to perform an fsync() (which it cannot do because it is
reclaiming memory).
By setting PF_FSTRANS we stop the memory allocator from ever
attempting
Because mmap_sem is sometimes(*) taken while holding a sock lock,
and the sock lock might be needed for reclaim (at least when loop-back
NFS is active), we must not block on FS reclaim while mmap_sem is
held.
exec.c allocates memory while holding mmap_sem, and so needs
PF_FSTRANS protection.
*
On 2014/4/16 11:50, Eric W. Biederman wrote:
> Kay Sievers writes:
>
>> On Tue, Apr 15, 2014 at 7:48 PM, Li Zefan wrote:
>>> On 2014/4/15 5:44, Tejun Heo wrote:
cgroup users often need a way to determine when a cgroup's
subhierarchy becomes empty so that it can be cleaned up. cgroup
nfsd will sometimes call flush_workqueue on the workqueue running
nfsd4_do_callback_rpc, so we must ensure that it doesn't block in
filesystem reclaim.
So set PF_FSTRANS.
Signed-off-by: NeilBrown
---
fs/nfsd/nfs4callback.c |5 +
1 file changed, 5 insertions(+)
diff --git
On 16 April 2014 00:14, Thomas Gleixner wrote:
> On Tue, 15 Apr 2014, Viresh Kumar wrote:
>
>> In tick_do_update_jiffies64() we are processing ticks only if delta is
>> greater
>> than tick_period. This is what we are supposed to do here and it broke a bit
>> with this patch:
>>
>> commit
lockdep reports a locking chain:
sk_lock-AF_INET --> rtnl_mutex --> gdp_mutex
As sk_lock can be needed for memory reclaim (when loop-back NFS is in
use at least), any memory allocation under gdp_mutex needs to
be protected by PF_FSTRANS.
The path frome rtnl_mutex to gdp_mutex is
[]
__d_alloc can be called with i_mutex held, so it is safer to
use GFP_NOFS.
lockdep reports this can deadlock when loop-back NFS is in use,
as nfsd may be required to write out for reclaim, and nfsd certainly
takes i_mutex.
Signed-off-by: NeilBrown
---
fs/dcache.c |4 ++--
1 file changed, 2
memory allocates can happen while the xfs ilock is held in
xfs_free_eofblocks, particularly
[] kmem_zone_alloc+0x67/0xc0
[] xfs_trans_add_item+0x25/0x50
[] xfs_trans_ijoin+0x2c/0x60
[] xfs_itruncate_extents+0xbe/0x400
[] xfs_free_eofblocks+0x1c4/0x240
So set PF_FSTRANS to avoid this
lockdep reports a locking chain
sk_lock-AF_INET --> rtnl_mutex --> pcpu_alloc_mutex
As sk_lock may be needed to reclaim memory, allowing that
reclaim while pcu_alloc_mutex is held can lead to deadlock.
So set PF_FSTRANS while it is help to avoid the FS reclaim.
pcpu_alloc_mutex can be taken
namespace_sem can be taken while various i_mutex locks are held, so we
need to avoid reclaim from blocking on an FS (particularly loop-back
NFS).
A memory allocation happens under namespace_sem at least in:
[] kmem_cache_alloc+0x4f/0x290
[] alloc_vfsmnt+0x1f/0x1d0
[] clone_mnt+0x2a/0x310
[]
When loop-back NFS with NFSv4 is in use, client_mutex might be needed
to reclaim memory, so any memory allocation while client_mutex is held
must avoid __GFP_FS, so best to set PF_FSTRANS.
Signed-off-by: NeilBrown
---
fs/nfsd/nfs4state.c |3 +++
1 file changed, 3 insertions(+)
diff --git
It is normally safe for direct reclaim to enter filesystems
even when a page is locked - as can happen if ->writepage
allocates memory with GFP_KERNEL (which xfs does).
However if a localhost NFS mount is present, then a flush-*
thread might hold a page locked and then in direct reclaim,
ask nfs
sk_lock can be taken while reclaiming memory (in nfsd for loop-back
NFS mounts, and presumably in nfs), and memory can be allocated while
holding sk_lock, at least via:
inet_listen -> inet_csk_listen_start ->reqsk_queue_alloc
So to avoid deadlocks, always set PF_FSTRANS while holding sk_lock.
As rtnl_mutex can be taken while holding sk_lock, and sk_lock can be
taken while performing memory reclaim (at least when loop-back NFS is
active), any memory allocation under rtnl_mutex must avoid __GFP_FS,
which is most easily done by setting PF_MEMALLOC.
CPU0CPU1
xfs_file_*_read holds an inode lock while calling a generic 'read'
function. These functions perform read-ahead and are quite likely to
allocate memory.
So set PF_FSTRANS to ensure they avoid __GFP_FS and so don't recurse
into a filesystem to free memory.
This can be a problem with loop-back NFS
nfsd already uses PF_LESS_THROTTLE (and is the only user) to avoid
throttling while dirtying pages. Use it also to avoid throttling while
doing direct reclaim as this can stall nfsd in the same way.
Also only set PF_LESS_THROTTLE when handling a 'write' request for a
local connection. This is
On 2014/4/16 11:33, Kay Sievers wrote:
> On Tue, Apr 15, 2014 at 7:48 PM, Li Zefan wrote:
>> On 2014/4/15 5:44, Tejun Heo wrote:
>>> cgroup users often need a way to determine when a cgroup's
>>> subhierarchy becomes empty so that it can be cleaned up. cgroup
>>> currently provides release_agent
lockdep can check for locking problems involving reclaim using
the same infrastructure as used for interrupts.
However a number of the messages still refer to interrupts even
if it was actually a reclaim-related problem.
So determine where the problem was caused by reclaim or irq and adjust
Loop-back NFS mounts are when the NFS client and server run on the
same host.
The use-case for this is a high availability cluster with shared
storage. The shared filesystem is mounted on any one machine and
NFS-mounted on the others.
If the nfs server fails, some other node will take over that
These are useful macros from xfs for modifying current->flags.
Other places in the kernel perform the same task in various different
ways.
This patch moves the macros from xfs to include/linux/sched.h and
changes all code which temporarily sets a current->flags flag to
use these macros.
This does
On Tue, Apr 15, 2014 at 8:50 PM, Eric W. Biederman
wrote:
> Kay Sievers writes:
>
>> On Tue, Apr 15, 2014 at 7:48 PM, Li Zefan wrote:
>>> On 2014/4/15 5:44, Tejun Heo wrote:
cgroup users often need a way to determine when a cgroup's
subhierarchy becomes empty so that it can be cleaned
On Tue, 15 Apr 2014, Vince Weaver wrote:
> Possibly it looks like a struct perf_event is being used after freed,
> specifically the event->migrate_entry->prev value? I could
> be completely wrong about that.
and actually I'm mixing up hex and decimal. It looks like the actual
value being
On Wed, Apr 16, 2014 at 09:30:24AM +0530, Viresh Kumar wrote:
> On 16 April 2014 06:54, Simon Horman wrote:
> > I have dropped this patch.
> >
> > Please let me know if there is a stable branch which
> > includes cpufreq_frequency_table which I can use as a base to apply
> > this patch.
> >
> >
On Wed, Apr 16, 2014 at 01:27:04AM +0300, Stratos Karafotis wrote:
> The cpufreq core now supports the cpufreq_for_each_valid_entry macro
> helper for iteration over the cpufreq_frequency_table, so use it.
>
> It should have no functional changes.
>
> Signed-off-by: Stratos Karafotis
Rafael,
On 16 April 2014 00:12, Thomas Gleixner wrote:
> B1;3202;0c
What does this mean ??
> On Tue, 15 Apr 2014, Viresh Kumar wrote:
>
>> tick_check_replacement() returns if a replacement of clock_event_device is
>> possible or not. It does this as the first check:
>>
>> if
On 16 April 2014 00:00, Thomas Gleixner wrote:
> On Tue, 15 Apr 2014, Viresh Kumar wrote:
>
>> If 'curdev' passed to tick_check_preferred() is the current
>> clock_event_device
>> then these two checks look exactly same, because td->mode is set to
>> TICKDEV_MODE_ONESHOT only when the event
On 04/15/2014 11:54 PM, H. Peter Anvin wrote:
> On 04/15/2014 08:47 PM, Sasha Levin wrote:
>> >
>> > Yes, if kmemcheck for some reason needs to figure out if an instruction
>> > is a MOV variant we'll need to list quite a few mnemonics, but that list
>> > will be much shorter and more readable
Hi Eric,
Today's linux-next merge of the audit tree got conflicts in
arch/mips/include/asm/syscall.h, arch/x86/Kconfig and kernel/audit.c
between commits from Linus' tree and commit 596b0569084b ("Merge tag
'v3.14' into mergeing") from the audit tree.
This happened because you merged Linus' tag
On 16 April 2014 03:55, Stratos Karafotis wrote:
> Hi all,
>
> This patch set introduces two freq_table helper macros which
> can be used for iteration over cpufreq_frequency_table and
> makes the necessary changes to cpufreq core and drivers that
> use such an iteration procedure.
>
> The
> -Original Message-
> From: Xiubo Li [mailto:li.xi...@freescale.com]
> Sent: Wednesday, April 16, 2014 10:20 AM
> To: daniel.lezc...@linaro.org; t...@linutronix.de; shawn@linaro.org; Lu
> Jingchang-B35083; Jin Zhengxiong-R64188; Wang Dongsheng-B40534
> Cc:
On 16 April 2014 06:54, Simon Horman wrote:
> I have dropped this patch.
>
> Please let me know if there is a stable branch which
> includes cpufreq_frequency_table which I can use as a base to apply
> this patch.
>
> Alternatively, I would be happy to Ack this patch and let someone
> else pick
On Tue, Apr 15, 2014 at 03:47:26PM -0700, Paul E. McKenney wrote:
> On Tue, Apr 15, 2014 at 06:29:51PM -0400, Dave Jones wrote:
> > On Tue, Apr 15, 2014 at 03:17:55PM -0700, Paul E. McKenney wrote:
> >
> > > My current admittedly crude workaround is as follows:
> > >
> > > static inline bool
On 04/15/2014 08:47 PM, Sasha Levin wrote:
>
> Yes, if kmemcheck for some reason needs to figure out if an instruction
> is a MOV variant we'll need to list quite a few mnemonics, but that list
> will be much shorter and more readable than a corresponding list of opcodes.
>
You're completely
Kay Sievers writes:
> On Tue, Apr 15, 2014 at 7:48 PM, Li Zefan wrote:
>> On 2014/4/15 5:44, Tejun Heo wrote:
>>> cgroup users often need a way to determine when a cgroup's
>>> subhierarchy becomes empty so that it can be cleaned up. cgroup
>>> currently provides release_agent for it;
Hi Chanwoo,
On 14 April 2014 14:37, Chanwoo Choi wrote:
> This patch control special clock for ADC in Exynos series's FSYS block.
> If special clock of ADC is registerd on clock list of common clk framework,
> Exynos ADC drvier have to control this clock.
>
> Exynos3250/Exynos4/Exynos5 has 'adc'
On 04/15/2014 11:26 PM, H. Peter Anvin wrote:
> On 04/15/2014 08:10 AM, Sasha Levin wrote:
>>
>> Mnemonics don't have 1:1 relationship with opcodes. So, for example,
>> if kmemcheck needs to check (and it does) whether a given instruction
>> is an "ADD", it would need to compare it to 9 different
On Apr 15, 2014 5:20 PM, "Vivek Goyal" wrote:
>
> On Tue, Apr 15, 2014 at 02:53:13PM -0700, Andy Lutomirski wrote:
> > On Tue, Apr 15, 2014 at 2:15 PM, Vivek Goyal wrote:
> > > This patch implements socket option SO_PASSCGROUP along the lines of
> > > SO_PASSCRED.
> > >
> > > If SO_PASSCGROUP is
[...]
> > +static void ftm_set_mode(enum clock_event_mode mode,
> > + struct clock_event_device *evt)
> > +{
> > + switch (mode) {
> > + case CLOCK_EVT_MODE_PERIODIC:
> > + ftm_set_next_event(peroidic_cyc, evt);
> > + break;
> > + default:
> > +
On Tue, Apr 15, 2014 at 7:48 PM, Li Zefan wrote:
> On 2014/4/15 5:44, Tejun Heo wrote:
>> cgroup users often need a way to determine when a cgroup's
>> subhierarchy becomes empty so that it can be cleaned up. cgroup
>> currently provides release_agent for it; unfortunately, this mechanism
>> is
On 04/15/2014 08:10 AM, Sasha Levin wrote:
>
> Mnemonics don't have 1:1 relationship with opcodes. So, for example,
> if kmemcheck needs to check (and it does) whether a given instruction
> is an "ADD", it would need to compare it to 9 different opcodes.
>
Excuse me, but on what planet does,
This is a cleanup patch suggested by Peter. Use new
this_cpu_xxx to improve operation speed.
v2 -> v1: Separate cleanup from bug fix.
Signed-off-by: Chen, Gong
Suggested-by: H. Peter Anvin
---
arch/x86/kernel/cpu/mcheck/mce.c | 36 +---
1 file changed, 17
This bug is introduced by me in commit 27f6c573e0. I forget
to execute put_cpu_var operation after get_cpu_var. Fix it
via this_cpu_write instead of get_cpu_var.
v2 -> v1: Separate cleanup from bug fix.
Signed-off-by: Chen, Gong
Suggested-by: H. Peter Anvin
---
1 - 100 of 1932 matches
Mail list logo
