On 22 September 2014 17:57, Stephen Warren wrote:
> From: Stephen Warren
>
> As soon as the CD IRQ is requested, it can trigger, since it's an
> externally controlled event. If it does, delayed_work host->detect will
> be scheduled.
>
> Many host controller probe()s are roughly structured as:
>
>
The "_MODULE" suffix is reserved for tristates compiled as
loadable kernel modules (LKM). The "TEST_MODULE" feature thereby
violates this convention. The feature is used to compile the
lib/test_module.c kernel module.
This patch renames the feature and its reference in a Makefile
to "TEST_LKM", wh
On Mon, 2014-09-22 at 22:59 -0700, Linus Torvalds wrote:
> Yup. It's 9cb0e394234d ("x86/efi: Fixup GOT in all boot code paths")
> according to bisect.
>
> Now building current git with that reverted, just to double-check,
> before pushing the revert out.
Crap. Sorry about that. I did get a report
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, September 23, 2014 12:47 PM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH 07/10] f2
>> -static inline bool task_no_new_privs(struct task_struct *p)
>> -{
>> - return test_bit(PFA_NO_NEW_PRIVS, &p->atomic_flags);
>> -}
>> -
>> -static inline void task_set_no_new_privs(struct task_struct *p)
>> -{
>> - set_bit(PFA_NO_NEW_PRIVS, &p->atomic_flags);
>> -}
>> +#define TASK_P
On 2014年09月23日 03:10, Rob Clark wrote:
Ok, couple more small comments.. this time I actually had time to go
through the entire patch, not just the uapi
On Mon, Sep 22, 2014 at 6:48 AM, Mark yao wrote:
This patch adds the basic structure of a DRM Driver for Rockchip Socs.
Signed-off-by: Mark
On Mon, Sep 22, 2014 at 09:29:19PM +0200, Paolo Bonzini wrote:
> Il 22/09/2014 21:20, Christian Borntraeger ha scritto:
> > "while using trinity to fuzz KVM, we noticed long stalls on invalid ioctls.
> > Lets bail out early on invalid ioctls". or similar?
>
> Okay. David, can you explain how you
On 09/23/2014 06:04 AM, Matt Ranostay wrote:
> diff --git a/drivers/input/keyboard/cap1106.c
> b/drivers/input/keyboard/cap1106.c
> index d70b65a..07f9e88 100644
> --- a/drivers/input/keyboard/cap1106.c
> +++ b/drivers/input/keyboard/cap1106.c
> @@ -55,8 +55,6 @@
> #define CAP1106_REG_MANUFACTURE
On 2014/9/23 14:33, Tejun Heo wrote:
> Hello, Linus.
>
> One late fix for cgroup. I was waiting for another set of fixes for a
> long-standing obscure cpuset bug but am not sure whether they'll be
> ready before v3.17 release. This one is a simple fix for a mutex
> unlock balance bug, which is d
The irq_chip_type instances have separate mask registers, so we need to
enable IRQ_GC_MASK_CACHE_PER_TYPE to actually handle separate mask registers.
Signed-off-by: Jisheng Zhang
---
drivers/irqchip/irq-dw-apb-ictl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/irqchip/irq-dw-apb-
These patches try to improve dw-apb-ictl irqchip driver a bit.
The first patch does a bit clean up work -- unify the register access usage.
The two dw-apb-ictl's irq_chip_type instances have separate mask registers, so
the second patch enables IRQ_GC_MASK_CACHE_PER_TYPE.
The last patch adds sus
This patch adds in support for S2R for dw-apb-ictl irqchip driver.
Signed-off-by: Jisheng Zhang
---
drivers/irqchip/irq-dw-apb-ictl.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/irqchip/irq-dw-apb-ictl.c
b/drivers/irqchip/irq-dw-apb-ictl.c
index c136b67..53b
On Mon, Sep 22, 2014 at 11:04 PM, Zefan Li wrote:
> This will simplify code when we add new flags.
>
> v2:
> - updated scripts/tags.sh, suggested by Peter
>
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
> Cc: Miao Xie
> Cc: Kees Cook
> Cc: Tetsuo Handa
> Signed-off-by: Zefan Li
> ---
> include/lin
relaxed version and non-relaxed version are mixed, this patch always
use the relaxed version to unify the memory access usage.
Signed-off-by: Jisheng Zhang
---
drivers/irqchip/irq-dw-apb-ictl.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/irqchip/irq-d
Hi Kamezawa,
于 14-9-23 下午12:46, Kamezawa Hiroyuki 写道:
> (2014/09/17 16:17), Wanpeng Li wrote:
>> BUG: unable to handle kernel NULL pointer dereference at 0004
>> IP: [..] find_busiest_group
>> PGD 5a9d5067 PUD 13067 PMD 0
>> Oops: [#3] SMP
>> [...]
>> Call Trace:
>> load_balance
>>
Hello, Linus.
One late fix for cgroup. I was waiting for another set of fixes for a
long-standing obscure cpuset bug but am not sure whether they'll be
ready before v3.17 release. This one is a simple fix for a mutex
unlock balance bug, which is detected by coccinelle and probably won't
trigger
The unw_addr_space_t in libunwind represents an address space to be
used for stack unwinding. It doesn't need to be create/destory
everytime to unwind callchain (as in get_entries) and can have a same
lifetime as thread (unless exec called).
So move the address space construction/destruction logi
The libunwind provides two caching policy which are global and
per-thread. As perf unwinds callchains in a single thread, it'd
sufficient to use global caching.
This speeds up my perf report from 14s to 7s on a ~260MB data file.
Although the output contains a slight difference (~0.01% in terms of
+linux-arm-msm
On Tuesday 23 September 2014 11:38 AM, Pramod Gurav wrote:
> This change replaces use of arm_pm_restart with recently introduced
> reset mechanism in Linux kernel called restart_notifier.
>
> Reviewed-by: Guenter Roeck
> Cc: Guenter Roeck
> Cc: Josh Cartwright
> Cc: Sebastian Rei
On 09/17/2014 09:48 PM, Toshi Kani wrote:
This patch refactors the !pat_enabled handling code and integrates
this case into the PAT abstraction code. The PAT table is emulated
by corresponding to the two cache attribute bits, PWT (Write Through)
and PCD (Cache Disable). The emulated PAT table is
On Tue, Sep 23, 2014 at 07:43:28AM +0200, Ingo Molnar wrote:
> * Stephen Rothwell wrote:
> > Today's linux-next merge of the tiny tree got conflicts in
> > arch/x86/kernel/process_32.c and arch/x86/kernel/process_64.c between
> > commits dc56c0f9b870 ("x86, fpu: Shift "fpu_counter = 0" from
> > co
Kukjin Kim wrote:
> >
> Andreas Färber wrote:
[...]
> > > Kukjin: Andreas's patch series was Reviewed long ago I think and by
> > > now I'd imagine it's got some conflicts due to it not having been
> > > applied in a timely fashion. Perhaps you could fix it up for Andreas
> > > (since he's alre
On Fri, Sep 19 2014, Johannes Weiner wrote:
> In a memcg with even just moderate cache pressure, success rates for
> transparent huge page allocations drop to zero, wasting a lot of
> effort that the allocator puts into assembling these pages.
>
> The reason for this is that the memcg reclaim cod
On 9/20/2014 3:29 PM, Beniamino Galvani wrote:
Hi,
the Ethernet controller available in Amlogic Meson6 and Meson8 SoCs is
a Synopsys DesignWare MAC IP core, already supported by the stmmac
driver.
These patches add a glue layer to the driver for the platform-specific
settings required by the Am
Hello, Neil.
On Tue, Sep 23, 2014 at 04:11:44PM +1000, NeilBrown wrote:
> You didn't say if you preferred a flag or a 'max_size'.
Sorry, missed that. No strong preference but a flag should be easier
and enough for now, right?
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "u
This patch fixes the checkpatch.pl warning:
WARNING: Missing a blank line after declarations
Signed-off-by: Sorin Facaoaru
---
drivers/staging/android/ion/ion.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android/ion/ion.c
index 2703
On 2014/9/23 12:58, Guenter Roeck wrote:
> On 09/22/2014 07:27 PM, Zefan Li wrote:
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.104 release.
>> There are 45 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with t
On 2014/9/23 12:54, Satoru Takeuchi wrote:
> Hi Li,
>
> At Tue, 23 Sep 2014 10:27:39 +0800,
> Zefan Li wrote:
>>
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.104 release.
>> There are 45 patches in this series, all will be posted as a response
>> to this one.
Because perf_session__new() could fail
for more reasons than just ENOMEM,
I modified error code(ENOMEM or EINVAL)
into -1.
Signed-off-by: taeung
---
tools/perf/builtin-annotate.c | 2 +-
tools/perf/builtin-diff.c | 2 +-
tools/perf/builtin-evlist.c| 2 +-
On Tue, 23 Sep 2014 01:51:56 -0400 Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 03:40:58PM +1000, NeilBrown wrote:
> > > Oh, I meant the buffer seqfile read op writes to, so it depends on the
> > > fact that the allocation is only on the first read? That seems
> > > extremely brittle to me, especi
On Tue, Sep 23, 2014 at 08:09:06AM +0200, Christoph Hellwig wrote:
> On Tue, Sep 23, 2014 at 02:01:41AM -0400, Tejun Heo wrote:
> > On Tue, Sep 23, 2014 at 07:59:24AM +0200, Christoph Hellwig wrote:
> > > "[PATCHSET percpu/for-3.18] percpu_ref: implement
> > > switch_to_atomic/percpu()"
> > >
> >
Hi Fancy Fang,
I do have a few comments:
1) One reason why the switch to vm_iomap_memory() was made originally was that
that function did a bunch of sanity checks. Since this patch moves back to
remap_pfn_range() those sanity checks are lost and should be reinstated.
2) You need Marek's Ack as w
On 9/23/2014 3:16 AM, Kweh, Hock Leong wrote:
-Original Message-
From: David Miller [mailto:da...@davemloft.net]
Sent: Tuesday, September 23, 2014 2:19 AM
From: Kweh Hock Leong
Date: Thu, 18 Sep 2014 20:34:10 +0800
Giuseppe, Kweh, where are we with this patch?
We are discussing whethe
Hi,
Have you got the update price of oil dated on AUGUEST.28.
If not, kindly send us the concrete type you need. we will send mail to you
ASAP!
Sunflower oil
soybean oil
Linseed oil
Rapeseed oil
Update news from your esteemed company will be appreciated.
Thanks!
Anna
XINJIANG FIRST
On Tue, Sep 23, 2014 at 02:01:41AM -0400, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 07:59:24AM +0200, Christoph Hellwig wrote:
> > "[PATCHSET percpu/for-3.18] percpu_ref: implement switch_to_atomic/percpu()"
> >
> > looks way to big for 3.17, and the regression was introduced in the 3.17
> > merg
>From 83b06f4fc6ca2f7f3d706a168b71c248bdada668 Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Tue, 23 Sep 2014 01:58:34 -0400
blk-mq uses percpu_ref for its usage counter which tracks the number
of in-flight commands and used to synchronously drain the queue on
freeze. percpu_ref shutdown takes
On Mon, Sep 22, 2014 at 10:59 PM, Linus Torvalds
wrote:
>
> Now building current git with that reverted, just to double-check,
> before pushing the revert out.
Double-checked and verified. Revert pushed out,
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kern
When we change cpuset.memory_spread_{page,slab}, cpuset will flip
PF_SPREAD_{PAGE,SLAB} bit of tsk->flags for each task in that cpuset.
This should be done using atomic bitops, but currently we don't,
which is broken.
Tetsuo reported a hard-to-reproduce kernel crash on RHEL6, which happend
when on
This change replaces use of arm_pm_restart with recently introduced
reset mechanism in Linux kernel called restart_notifier.
Reviewed-by: Guenter Roeck
Cc: Guenter Roeck
Cc: Josh Cartwright
Cc: Sebastian Reichel
Cc: Dmitry Eremin-Solenikov
Cc: David Woodhouse
Cc: Stephen Boyd
Cc: linux...@v
From: Tetsuo Handa
Commit 1d4457f99928 ("sched: move no_new_privs into new atomic flags")
defined PFA_NO_NEW_PRIVS as hexadecimal value, but it is confusing
because it is used as bit number. Redefine it as decimal bit number.
Note this changes the bit position of PFA_NOW_NEW_PRIVS from 1 to 0.
This will simplify code when we add new flags.
v2:
- updated scripts/tags.sh, suggested by Peter
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Miao Xie
Cc: Kees Cook
Cc: Tetsuo Handa
Signed-off-by: Zefan Li
---
include/linux/sched.h | 20 +++-
scripts/tags.sh | 6 ++
2
On Tue, Sep 23, 2014 at 02:01:41AM -0400, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 07:59:24AM +0200, Christoph Hellwig wrote:
> > "[PATCHSET percpu/for-3.18] percpu_ref: implement switch_to_atomic/percpu()"
> >
> > looks way to big for 3.17, and the regression was introduced in the 3.17
> > merg
On Tue, Sep 23, 2014 at 07:59:24AM +0200, Christoph Hellwig wrote:
> "[PATCHSET percpu/for-3.18] percpu_ref: implement switch_to_atomic/percpu()"
>
> looks way to big for 3.17, and the regression was introduced in the 3.17
> merge window. I'm not sure what was broken before, but it defintively
>
in this function)...
right, I will remove it.
Best Regards,
Boris
[1]http://thread.gmane.org/gmane.comp.video.dri.devel/114064
[2]https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/exynos/exynos_drm_drv.c?id=refs/tags/next-20140922#n373
--
To unsubscribe fro
SCO connection cannot be setup to devices that do not support retransmission.
Patch based on http://permalink.gmane.org/gmane.linux.bluez.kernel/7779 and
adapted for this kernel version.
Code changed to check SCO/eSCO type before setting retransmission effort
and max. latency. The purpose of the pa
ping?
On Sat, Sep 06, 2014 at 04:08:05PM -0700, Christoph Hellwig wrote:
> Set max_sectors to the value the drivers provides as hardware limit by
> default. Linux had proper I/O throttling for a long time and doesn't
> rely on a artifically small maximum I/O size anymore. By not limiting
> the I
On Tue, Sep 23, 2014 at 01:56:48AM -0400, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 07:55:54AM +0200, Christoph Hellwig wrote:
> > Jens,
> >
> > can we simply get these commits reverted from now if there's no better
> > fix? I'd hate to have this boot stall in the first kernel with blk-mq
> > su
On Tue, Sep 23, 2014 at 02:57:11PM +1000, Stephen Rothwell wrote:
> Hi Josh,
>
> After merging the tiny tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> mm/built-in.o: In function `.isolate_migratepages_range':
> (.text+0x2fbd8): undefined reference to `.balloon_pa
Yup. It's 9cb0e394234d ("x86/efi: Fixup GOT in all boot code paths")
according to bisect.
Now building current git with that reverted, just to double-check,
before pushing the revert out.
Linus
On Mon, Sep 22, 2014 at 10:44 PM, H. Peter Anvin wrote:
> That would be my guess, too.
>
>
* Some comments became stale. Updated.
* percpu_ref_tryget() unnecessarily initializes @ret. Removed.
* A blank line removed from percpu_ref_kill_rcu().
* Explicit function name in a WARN format string replaced with __func__.
* WARN_ON() in percpu_ref_reinit() converted to WARN_ON_ONCE().
Signed
Hello,
Over the past several months, percpu_ref grew use cases where it's
used as a persistent on/off switch which may be cycled multiple times
using percpu_ref_reinit(). One of such use cases is blk-mq's
mq_usage_counter which tracks the number of in-flight commands and is
used to drain them. U
percpu_ref will be restructured so that percpu/atomic mode switching
and reference killing are dedoupled. In preparation, do the following
renames.
* percpu_ref->confirm_kill -> percpu_ref->confirm_switch
* __PERCPU_REF_DEAD -> __PERCPU_REF_ATOMIC
* __percpu_ref_alive()
percpu_ref is gonna go through restructuring. Move
percpu_ref_reinit() after percpu_ref_kill_and_confirm(). This will
make later changes easier to follow and result in cleaner
organization.
Signed-off-by: Tejun Heo
Cc: Kent Overstreet
---
include/linux/percpu-refcount.h | 2 +-
lib/percpu-re
* Ingo Molnar wrote:
> * Ingo Molnar wrote:
>
> >
> > * Linus Torvalds wrote:
> >
> > > On Fri, Sep 19, 2014 at 3:40 AM, Ingo Molnar wrote:
> > > >
> > > > Please pull the latest x86-urgent-for-linus git tree from:
> > >
> > > I only just noticed, but this pull request causes my Sony Vaio
On Tue, Sep 23, 2014 at 01:56:48AM -0400, Tejun Heo wrote:
> On Tue, Sep 23, 2014 at 07:55:54AM +0200, Christoph Hellwig wrote:
> > Jens,
> >
> > can we simply get these commits reverted from now if there's no better
> > fix? I'd hate to have this boot stall in the first kernel with blk-mq
> > su
percpu_ref will be restructured so that percpu/atomic mode switching
and reference killing are dedoupled. In preparation, add
PCPU_REF_DEAD and PCPU_REF_ATOMIC_DEAD which is OR of ATOMIC and DEAD.
For now, ATOMIC and DEAD are changed together and all PCPU_REF_ATOMIC
uses are converted to PCPU_REF_
On Mon, Sep 22, 2014 at 02:40:15PM -0400, Douglas Gilbert wrote:
> With these patches applied (actually a resync an hour
> ago with the for-linus tree which includes them), the
> freeze-during-boot-up problem that I have been seeing
> with an old SATA boot disk (perhaps 1.5 Gbps) for
> the last two
On Tue, Sep 23, 2014 at 07:55:54AM +0200, Christoph Hellwig wrote:
> Jens,
>
> can we simply get these commits reverted from now if there's no better
> fix? I'd hate to have this boot stall in the first kernel with blk-mq
> support for scsi.
Patches going out right now.
Thanks.
--
tejun
--
To
Currently, a percpu_ref which is initialized with
PERPCU_REF_INIT_ATOMIC or switched to atomic mode via
switch_to_atomic() automatically reverts to percpu mode on the first
percpu_ref_reinit(). This makes the atomic mode difficult to use for
cases where a percpu_ref is used as a persistent on/off
percpu_ref has treated the dropping of the base reference and
switching to atomic mode as an integral operation; however, there's
nothing inherent tying the two together.
The use cases for percpu_ref have been expanding continuously. While
the current init/kill/reinit/exit model can cover a lot,
Jens,
can we simply get these commits reverted from now if there's no better
fix? I'd hate to have this boot stall in the first kernel with blk-mq
support for scsi.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mo
With the recent addition of percpu_ref_reinit(), percpu_ref now can be
used as a persistent switch which can be turned on and off repeatedly
where turning off maps to killing the ref and waiting for it to drain;
however, there currently isn't a way to initialize a percpu_ref in its
off (killed and
percpu_ref uses pcpu_ prefix for internal stuff and percpu_ for
externally visible ones. This is the same convention used in the
percpu allocator implementation. It works fine there but percpu_ref
doesn't have too much internal-only stuff and scattered usages of
pcpu_ prefix are confusing than he
percpu_ref has treated the dropping of the base reference and
switching to atomic mode as an integral operation; however, there's
nothing inherent tying the two together.
The use cases for percpu_ref have been expanding continuously. While
the current init/kill/reinit/exit model can cover a lot,
Be similar with commit (ata: Disabling the async PM for JMicron chip 363/361),
Barto found the similar issue for JMicron chip 368, that 363/368 has no
parent-children relationship, but they have the power dependency.
So here we can exclude the JMicron chips out of pm_async method directly,
to avoi
On Tue, Sep 23, 2014 at 03:40:58PM +1000, NeilBrown wrote:
> > Oh, I meant the buffer seqfile read op writes to, so it depends on the
> > fact that the allocation is only on the first read? That seems
> > extremely brittle to me, especially for an issue which tends to be
> > difficult to reproduce
On 9/22/2014 8:40 PM, Joe Perches wrote:
> No caller or macro uses the return value so make it void.
>
> Signed-off-by: Joe Perches
> ---
> This change is associated to a desire to eventually
> change printk to return void.
>
> drivers/net/ethernet/mellanox/mlx4/en_main.c | 17 +++--
On 09/17/2014 09:48 PM, Toshi Kani wrote:
This patch sets WT to the PA7 slot in the PAT MSR when the processor
is not affected by the PAT errata. The PA7 slot is chosen to further
minimize the risk of using the PAT bit as the PA3 slot is UC and is
not currently used.
The following Intel process
That would be my guess, too.
On September 22, 2014 10:37:11 PM PDT, Ingo Molnar wrote:
>
>* Ingo Molnar wrote:
>
>>
>> * Linus Torvalds wrote:
>>
>> > On Fri, Sep 19, 2014 at 3:40 AM, Ingo Molnar
>wrote:
>> > >
>> > > Please pull the latest x86-urgent-for-linus git tree from:
>> >
>> > I on
* Stephen Rothwell wrote:
> Hi Josh,
>
> Today's linux-next merge of the tiny tree got conflicts in
> arch/x86/kernel/process_32.c and arch/x86/kernel/process_64.c between
> commits dc56c0f9b870 ("x86, fpu: Shift "fpu_counter = 0" from
> copy_thread() to arch_dup_task_struct()") and 6f46b3aef00
On Tue, 23 Sep 2014 00:55:49 -0400 Tejun Heo wrote:
> Hello, Neil.
>
> On Tue, Sep 23, 2014 at 02:46:50PM +1000, NeilBrown wrote:
> > seqfile is only safe for reads. sysfs via kernfs uses seq_read(), so there
> > is only a single allocation on the first read.
> >
> > It doesn't really related
> Sorry for later response due to sickness. I can't write this patch in
> time. Sorry again. I will test it soon.
Oh, get well soon! Please say so next time, so I know.
signature.asc
Description: Digital signature
* Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Fri, Sep 19, 2014 at 3:40 AM, Ingo Molnar wrote:
> > >
> > > Please pull the latest x86-urgent-for-linus git tree from:
> >
> > I only just noticed, but this pull request causes my Sony Vaio
> > laptop to immediately reboot at start
* Linus Torvalds wrote:
> On Fri, Sep 19, 2014 at 3:40 AM, Ingo Molnar wrote:
> >
> > Please pull the latest x86-urgent-for-linus git tree from:
>
> I only just noticed, but this pull request causes my Sony Vaio
> laptop to immediately reboot at startup.
>
> I'm assuming it's one of the efi
Hi,
any chance to have this in 3.18?
Juergen
On 09/12/2014 12:35 PM, Juergen Gross wrote:
The x86 architecture offers via the PAT (Page Attribute Table) a way to
specify different caching modes in page table entries. The PAT MSR contains
8 entries each specifying one of 6 possible cache modes.
Hi Chao,
I fixed that. :)
Thanks,
On Mon, Sep 22, 2014 at 05:22:27PM +0800, Chao Yu wrote:
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Monday, September 15, 2014 6:14 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-
On 06/03/2014 09:26 PM, Davidlohr Bueso wrote:
> On Fri, 2014-05-02 at 15:16 +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Manfred,
>>
>> On Mon, Apr 21, 2014 at 4:26 PM, Manfred Spraul
>> wrote:
>>> Hi all,
>>>
>>> the increase of SHMMAX/SHMALL is now a 4 patch series.
>>> I don't have ideas ho
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> The changes in this series include:
>
> 1.Update RCU documentation. These were posted to LKML at
> https://lkml.org/lkml/2014/8/28/378.
>
> 2.Miscellaneous fixes. These were posted to LKML at
> https://lkml.org/lkml/2014/8/28/
On Fri, Sep 19, 2014 at 3:40 AM, Ingo Molnar wrote:
>
> Please pull the latest x86-urgent-for-linus git tree from:
I only just noticed, but this pull request causes my Sony Vaio laptop
to immediately reboot at startup.
I'm assuming it's one of the efi changes, but I'm bisecting now to say
exactl
2014-09-22 22:03 GMT-07:00 Olof Johansson :
> On Fri, Sep 19, 2014 at 11:17:11AM -0700, Florian Fainelli wrote:
>> Hi all,
>>
>> As some of you may have seen in the news, Broadcom has recently stopped
>> its mobile SoC activities. Upstream support for Broadcom's Mobile SoCs
>> was an effort initial
On 09/23/2014 04:44 AM, Chanwoo Choi wrote:
On 09/22/2014 06:51 PM, George Cherian wrote:
On 09/22/2014 01:37 PM, Chanwoo Choi wrote:
Hi George,
This patch removes 'gpio_active_low' field of struct gpio_extcon_data.
But, include/linux/extcon-gpio.h has the description of 'gpio_active_low' fie
Hello:
I am facing an issue wherein kernel 3.17 crashes while loading IPoIB module. I
guess the issue discussed in this thread
(https://www.mail-archive.com/linux-rdma@vger.kernel.org/msg20963.html) is
similar.
We were able to reproduce the issue with RC6 also. Here are the steps I
followed:
Hi Arnd,
On Mon, 22 Sep 2014 21:45:40 +0200
Arnd Bergmann wrote:
> On Monday 22 September 2014 21:37:55 Boris BREZILLON wrote:
> > dma_mask and dma_parms are already inherited from the parent device but
> > dma_coherent_mask was left uninitialized (set to zero thanks to kzalloc).
> > Set sub-dev
On Fri, Sep 19, 2014 at 11:17:11AM -0700, Florian Fainelli wrote:
> Hi all,
>
> As some of you may have seen in the news, Broadcom has recently stopped
> its mobile SoC activities. Upstream support for Broadcom's Mobile SoCs
> was an effort initially started by Christian Daudt and his team, and th
On 09/22/2014 07:27 PM, Zefan Li wrote:
From: Zefan Li
This is the start of the stable review cycle for the 3.4.104 release.
There are 45 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses shou
Hi Josh,
After merging the tiny tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/built-in.o: In function `.isolate_migratepages_range':
(.text+0x2fbd8): undefined reference to `.balloon_page_isolate'
mm/built-in.o: In function `.putback_movable_pages':
(.text+0x713c4)
On Mon, Sep 22, 2014 at 02:17:33PM -0700, Andrew Morton wrote:
> On Mon, 22 Sep 2014 09:03:11 +0900 Minchan Kim wrote:
>
> > Some zram usecase could want lower fullness than default 80 to
> > avoid unnecessary swapout-and-fail-recover overhead.
> >
> > A typical example is that mutliple swap wit
Hello, Neil.
On Tue, Sep 23, 2014 at 02:46:50PM +1000, NeilBrown wrote:
> seqfile is only safe for reads. sysfs via kernfs uses seq_read(), so there
> is only a single allocation on the first read.
>
> It doesn't really related to fixing writes, except to point out that only
> writes need to be
Hi Li,
At Tue, 23 Sep 2014 10:27:39 +0800,
Zefan Li wrote:
>
> From: Zefan Li
>
> This is the start of the stable review cycle for the 3.4.104 release.
> There are 45 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, plea
On Mon, Sep 22, 2014 at 02:11:18PM -0700, Andrew Morton wrote:
> On Mon, 22 Sep 2014 09:03:10 +0900 Minchan Kim wrote:
>
> > This patch implement SWAP_FULL handler in zram so that VM can
> > know whether zram is full or not and use it to stop anonymous
> > page reclaim.
> >
> > How to judge full
Previously, f2fs tries to reorganize the dirty nat entries into multiple sets
according to its nid ranges. This can improve the flushing nat pages, however,
if there are a lot of cached nat entries, it becomes a bottleneck.
This patch introduces a new set management flow by removing dirty nat list
This patch introduces FITRIM in f2fs_ioctl.
In this case, f2fs will issue small discards and prefree discards as many as
possible for the given area.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c| 4 +-
fs/f2fs/f2fs.h | 9 +++-
fs/f2fs/file.c | 29 +++
This patch add a new data structure to control checkpoint parameters.
Currently, it presents the reason of checkpoint such as is_umount and normal
sync.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c| 16
fs/f2fs/f2fs.h | 11 ++-
fs/f2fs/gc.c
On Mon, Sep 22, 2014 at 05:20:19PM +0800, Chao Yu wrote:
> > -Original Message-
> > From: Huang Ying [mailto:ying.hu...@intel.com]
> > Sent: Monday, September 22, 2014 3:39 PM
> > To: Chao Yu
> > Cc: 'Jaegeuk Kim'; linux-kernel@vger.kernel.org;
> > linux-fsde...@vger.kernel.org;
> > linux-
On 09/23/14 12:18, Greg KH wrote:
> On Tue, Sep 23, 2014 at 10:57:09AM +0800, Hui Zhu wrote:
>> The cause of this issue is when free memroy size is low and a lot of task is
>> trying to shrink the memory, the task that is killed by lowmemkiller cannot
>> get
>> CPU to exit itself.
>>
>> Fix this
From: Behan Webster
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This patch allocates the appropriate amount of memory
using a char array using the SHASH_DESC_ON_STACK macro.
The new code can be compiled with both gcc and clang.
Signed-off-by: B
From: Behan Webster
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This patch allocates the appropriate amount of memory
using a char array using the SHASH_DESC_ON_STACK macro.
The new code can be compiled with both gcc and clang.
Signed-off-by: B
(2014/09/17 16:17), Wanpeng Li wrote:
> BUG: unable to handle kernel NULL pointer dereference at 0004
> IP: [..] find_busiest_group
> PGD 5a9d5067 PUD 13067 PMD 0
> Oops: [#3] SMP
> [...]
> Call Trace:
> load_balance
> ? _raw_spin_unlock_irqrestore
> idle_balance
> __schedule
> sch
Hi Chao,
On Mon, Sep 22, 2014 at 10:36:25AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Monday, September 15, 2014 6:14 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> > linux-f2fs-de...
From: Behan Webster
Replaced the use of a Variable Length Array In Struct (VLAIS) with a C99
compliant equivalent. This patch allocates the appropriate amount of memory
using a char array using the SHASH_DESC_ON_STACK macro.
The new code can be compiled with both gcc and clang.
Signed-off-by: B
1 - 100 of 947 matches
Mail list logo
