On Thu, Apr 11, 2013 at 04:18:13PM +0300, Kirill A. Shutemov wrote:
> Minchan Kim wrote:
> > On Fri, Mar 29, 2013 at 09:04:16AM -0400, Sasha Levin wrote:
> > > Hi all,
> > >
> > > While fuzzing with trinity inside a KVM tools guest running latest -next
> > > kernel,
> > > I've stumbled on the fol
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix compile errors for teh at91rm9200_wdt driver.
This will update the following files:
Kconfig |2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
with these Changes:
commit 0
Hi,
Il 14/04/2013 02:18, KOSAKI Motohiro ha scritto:
(4/13/13 5:14 AM), Marco Stornelli wrote:
Hi,
I was seeing the code of __mm_populate (in -next) and I've got a doubt
about the return value. The function __mlock_posix_error_return should
return a proper error for mlock, converting the retur
Hi KOSAKI,
On Thu, Apr 11, 2013 at 11:01:11AM -0400, KOSAKI Motohiro wrote:
> and adding new syscall invokation is unwelcome.
> >>>
> >>> Sure. But one more system call could be cheaper than page-granuarity
> >>> operation on purged range.
> >>
> >> I don't think vrange(VOLATILE) cost is the
On Sat, Apr 13 2013, Rob Landley wrote:
> Cleaning out "look at this" directory, I don't see this applied upstream but
> it may already be in Jens' tree. (That's the tree it should go in
> through...)
It's already included, see:
http://git.kernel.dk/?p=linux-block.git;a=commit;h=fdc6fdc52e4630f50
On Fri, Apr 12 2013, Asai Thambi S P wrote:
>
> Temporarily disabling TRIM support until TRIM related issues
> are addressed in the firmware.
How serious is this? We do have released kernels out there with the
driver, you might want to consider a stable backport too.
Anyway, applied for 3.10.
-
On Fri, Apr 12 2013, Asai Thambi S P wrote:
>
> Reported smatch warning:
> drivers/block/mtip32xx/mtip32xx.c:4163 mtip_block_shutdown() warn: variable
> dereferenced before check 'dd->disk' (see line 4159)
>
> dd->disk->disk_name accessed before the check if dd->disk is NULL. Fixed this
> and ac
Hi Linus
one fix for a hotplug locking regressions, and one fix for an oops if you
unplug the monitor at an inopportune moment on the udl device.
Dave.
The following changes since commit cfb63bafdb87bbcdc5d6dbbca623d3f69475f118:
Merge branch 'fixes' of git://git.infradead.org/users/vkoul/sl
Hello,
On 4/12/13 9:19 PM, Borislav Petkov wrote:
so I'm currently experimenting with my randconfig build scripts and
thought that maybe it would be a cool thing to not only do the random
builds only but also boot-test them in kvm. Which reminded me that we
have that KVMTOOL_TEST_ENABLE config o
Devices have various maintenance operations need to perform internally.
In order to reduce latencies during time critical operations like read
and write, it is better to execute maintenance operations in other
times - when the host is not being serviced. Such operations are called
Background operat
On Sun, Apr 14, 2013 at 12:31:12PM +0300, Pekka Enberg wrote:
> I obviously support having something like this in mainline. I wonder
> though if we could just call this "default standalone KVM guest
> config" instead of emphasizing testing angle.
/me nods agreeingly...
And it should be unter HYPE
On Sun, Apr 14, 2013 at 09:17:03AM +0200, Wim Van Sebroeck wrote:
> Hi Linus,
>
> Please pull from 'master' branch of
> git://www.linux-watchdog.org/linux-watchdog.git
>
> It will fix compile errors for teh at91rm9200_wdt driver.
>
> This will update the following files:
>
> Kconfig |
On Thu, Apr 11, 2013 at 02:04:50AM +0200, Arnd Bergmann wrote:
> No other file in the kernel besides i2c-s3c2410.c uses the current
> plat/regs-iic.h, so we can simply move the header file to live in the
> same directory as the driver, as a preparation to multiplatform builds.
What about putting
On 04/13/13 23:46, Rob Landley wrote:
> On 04/06/2013 03:55:26 PM, Randy Dunlap wrote:
>> On 03/03/13 04:43, Borislav Petkov wrote:
>> > From: Borislav Petkov
>> >
>> > Documentation/SubmittingPullRequests | 148
>> > +++
>> > 1 file changed, 148 insertions(+)
>>
Hi James,
I am a newbie to linux kernel device driver and would like to use this
client driver on my uClinux running on the NIOS2. Can you kindly point me to
the right direction, since I am using a device tree and believe this doesn't
support device tree, right? What do I need to add/modify so I c
On Mon, Apr 08, 2013 at 12:54:01PM -0700, Bryan Freed wrote:
[...]
> And as a more general question, why should we try not to put
> configuration in the device tree? It seems like a great (and
> portable) place to put this stuff.
> It certainly seems better to have it there than hardwired in the
>
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
HEAD: c481420248c6730246d2a1b1773d5d7007ae0835 perf: Fix error return code
Misc fixlets.
Thanks,
Ingo
-->
Chen Ga
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
HEAD: e614b3332a4f3f264a26da28e5a1f4cc3aea3974 sched/cputime: Fix accounting
on multi-threaded processes
Misc fixlets.
Thanks,
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
HEAD: 26564600c9e88c6572a5e6ef5ae9121907edfb7f x86/mm: Flush lazy MMU when
DEBUG_PAGEALLOC is set
Misc fixes.
Thanks,
Ingo
---
On Sun, Apr 14, 2013 at 09:28:50AM +0800, Alex Shi wrote:
> Even some scenario the total energy cost more, at least the avg watts
> dropped in that scenarios.
Ok, what's wrong with x = 32 then? So basically if you're looking at
avg watts, you don't want to have more than 16 threads, otherwise
powe
Commit-ID: c481420248c6730246d2a1b1773d5d7007ae0835
Gitweb: http://git.kernel.org/tip/c481420248c6730246d2a1b1773d5d7007ae0835
Author: Wei Yongjun
AuthorDate: Fri, 12 Apr 2013 11:05:54 +0800
Committer: Ingo Molnar
CommitDate: Fri, 12 Apr 2013 06:33:56 +0200
perf: Fix error return code
Commit-ID: 26564600c9e88c6572a5e6ef5ae9121907edfb7f
Gitweb: http://git.kernel.org/tip/26564600c9e88c6572a5e6ef5ae9121907edfb7f
Author: Boris Ostrovsky
AuthorDate: Thu, 11 Apr 2013 13:59:52 -0400
Committer: Ingo Molnar
CommitDate: Fri, 12 Apr 2013 07:19:19 +0200
x86/mm: Flush lazy MMU w
Commit-ID: 18699739b60cb60230153ff5475b2ba92be185f9
Gitweb: http://git.kernel.org/tip/18699739b60cb60230153ff5475b2ba92be185f9
Author: Andrea Arcangeli
AuthorDate: Thu, 11 Apr 2013 15:36:09 +0200
Committer: Ingo Molnar
CommitDate: Fri, 12 Apr 2013 06:39:20 +0200
x86/mm/cpa/selftest: Fi
This reverts commit 87dc669ba25777b67796d7262c569429e58b1ed4.
The patch was fine but we can no longer race with SIGKILL after
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL", the __TASK_TRACED tracee can't be woken up and
->ptrace_bps[] can't go away.
The patch on
This reverts commit bf0b8f4b55e591ba417c2dbaff42769e1fc773b0.
The patch was fine but we can no longer race with SIGKILL after
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL", the __TASK_TRACED tracee can't be woken up and
->ptrace_bps[] can't go away.
Signed-off-b
This reverts commit e0ac8457d020c0289ea566917267da9e5e6d9865.
The patch was fine but we can no longer race with SIGKILL after
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL", the __TASK_TRACED tracee can't be woken up and
->ptrace_bps[] can't go away.
Signed-off-b
This reverts commit bf26c018490c2fce7fe9b629083b96ce0e6ad019.
The patch was fine but we can no longer race with SIGKILL after
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL", the __TASK_TRACED tracee can't be woken up and
->ptrace_bps[] can't go away.
Now that ptr
Hello.
Kill ptrace_{get,put}_breakpoints and task_struct->ptrace_bp_refcnt,
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL" made this all unneeded.
Benjamin, Paul, arch_dup_task_struct()->flush_ptrace_hw_breakpoint(src)
on powerpc looks "obviously wrong". Don't we
Commit-ID: 9b89f6ba2ab56e4d9c00e7e591d6bc333137895e
Gitweb: http://git.kernel.org/tip/9b89f6ba2ab56e4d9c00e7e591d6bc333137895e
Author: Andrei Epure
AuthorDate: Thu, 11 Apr 2013 20:30:29 +0300
Committer: Ingo Molnar
CommitDate: Fri, 12 Apr 2013 07:20:27 +0200
sched: Document task_struct
This reverts commit 07fa7a0a8a586c01a8b416358c7012dcb9dc688d and
removes ptrace_get/put_breakpoints() added by other commits.
The patch was fine but we can no longer race with SIGKILL after
9899d11f "ptrace: ensure arch_ptrace/ptrace_request can never race
with SIGKILL", the __TASK_TRACED tracee c
Commit-ID: a7e6567585e513cb4e44387831cb75eb5b562cbb
Gitweb: http://git.kernel.org/tip/a7e6567585e513cb4e44387831cb75eb5b562cbb
Author: Paul Bolle
AuthorDate: Thu, 11 Apr 2013 18:49:42 +0200
Committer: Ingo Molnar
CommitDate: Fri, 12 Apr 2013 07:21:18 +0200
x86/mm/fixmap: Remove unused
When user requests encryption (or decryption) of block which
is not aligned to cipher block size through userspace crypto
interface, an OOps like this can happen:
[ 112.738285] BUG: unable to handle kernel paging request at e1c44840
[ 112.738407] IP: [] scatterwalk_done+0x53/0x70
...
[ 112.7405
On 04/14/2013 06:12 PM, Milan Broz wrote:
> When user requests encryption (or decryption) of block which
> is not aligned to cipher block size through userspace crypto
> interface, an OOps like this can happen
And this is a reproducer for the problem above...
Milan
/*
* Check for unaligned buf
2013/4/12 Lee Jones :
> So I need to devise another way, as this function cannot be called
> here either. Using the dmaengine API, allocating a channel and
> configuring it are to be completed using different calls. Using the
> API correctly, there is no way the driver can setup the channel
> with
I found the early-increasing nr_running in wq_worker_waking_up() is useless
in many cases. it tries to avoid waking up idle workers for pending work item.
but delay increasing nr_running does not increase waking up idle workers.
so we delay increasing and remove wq_worker_waking_up() and ...
enjo
WARN_ON_ONCE(cpu != raw_smp_processor_id()) in
wq_worker_sleeping() in useless, the caller ensures
cpu == raw_smp_processor_id().
We should use WARN_ON_ONCE(pool->cpu != raw_smp_processor_id())
to do the expected test.
It results @cpu removed from wq_worker_sleeping()
Signed-off-by: Lai Jiangsha
After we allocated worker, we are free to access the worker without and
protection before it is visiable/published.
In old code, worker is published by start_worker(), and it is visiable only
after start_worker(), but in current code, it is visiable by
for_each_pool_worker() after
"idr_replace(&po
In process_one_work(), we can use "worker->flags & WORKER_CPU_INTENSIVE"
instead "cpu_intensive" and because worker->flags is hot field
(accessed when process each work item). so this change will not cause
any performance down.
It prepare for also clearing WORKER_QUIT_CM in the same place.
Signed
When a work is waken up from sleeping, it makes very small sense if
we still consider this worker is RUNNING(in view of concurrency management)
o if the work goes to sleep again, it is not RUNNING again.
o if the work runs long without sleeping, the worker should be consider
as
When a worker is sleeping, its flags has WORKER_QUIT_CM, which means
worker->flags & WORKER_NOT_RUNNING is always non-zero, and which means
wq_worker_waking_up() is disabled.
so we removed wq_worker_waking_up(). (the access to worker->flags
in wq_worker_waking_up() is not protected by "LI". after
Now, nr_running is accessed only with local IRQ-disabled and only from local
cpu if the pool is assocated.(execpt read-access in insert_work()).
so we convert it to non-atomic to reduce the overhead of atomic.
It is protected by "LI"
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 49 ++
worker->flags is hot field(accessed when process each work item).
Move it up the the first 64 bytes(32 byte in 32bis) which are
hot fields.
And move colder field worker->task down to ensure worker->pool is
still in the first 64 bytes.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue_internal.h
nr_running is not a good name, the reviewers may think they are non-sleeping
busy workers. nr_running is actually a counter for concurrency managed
workers. renaming it to nr_cm_workers would be better.
s/nr_running/nr_cm_workers/
s/NOT_RUNNING/NOT_CM/
manually tune a little(indent and the comment
Am Sonntag, 14. April 2013, 14:20:35 schrieb Wolfram Sang:
> On Thu, Apr 11, 2013 at 02:04:50AM +0200, Arnd Bergmann wrote:
> > No other file in the kernel besides i2c-s3c2410.c uses the current
> > plat/regs-iic.h, so we can simply move the header file to live in the
> > same directory as the driv
Hi Joe,
On Sat, 13 Apr 2013 22:55:45 -0700, Joe Perches wrote:
> commit 3401d54696f ("KVM: ARM: Introduce KVM_ARM_SET_DEVICE_ADDR ioctl")
> added the case, but omitted adding break;
[...]
Already reported here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-April/160127.html
> $ gr
Cc: Linus Walleij
Cc: Jean Delvare
Cc: Samuel Ortiz
Cc: Mark Brown
Cc: Guenter Roeck
Cc: linux-kernel
Cc: Grant Likely
Signed-off-by: Marek Vasut
---
drivers/gpio/gpio-ucb1400.c | 19 ++-
drivers/mfd/ucb1400_core.c |5 +
include/linux/ucb1400.h | 18 ++-
Now that hierarchy_id alloc / free are protected by the cgroup
mutexes, there's no need for this separate lock. Drop it.
Signed-off-by: Tejun Heo
---
kernel/cgroup.c | 23 +--
1 file changed, 17 insertions(+), 6 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
in
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
Implement task_cgroup_path_from_hierarchy().
Signed-off-by: Tejun Heo
Cc: Kay Sievers
Cc: Greg Kroah-Hartman
Cc: Lennart Poettering
We're planning to converting hierarchy_ida to an idr and use it to
look up hierarchy from its id. As we want the mapping to happen
atomically with cgroupfs_root registration, this patch refactors
hierarchy_id init / exit so that ida operations happen inside
cgroup_[root_]mutex.
* s/init_root_id()
We want to be able to lookup a hierarchy from its id and cyclic
allocation is a whole lot simpler with idr. Convert to idr and use
idr_alloc_cyclc().
Signed-off-by: Tejun Heo
---
kernel/cgroup.c | 28
1 file changed, 8 insertions(+), 20 deletions(-)
diff --git a/ke
kdbus folks want a sane way to determine the cgroup path that a given
task belongs to on a given hierarchy, which is a reasonble thing to
expect from cgroup core.
This patchset make hierarchy_id allocation use idr instead of ida and
implement task_cgroup_path_from_hierarchy(). In the process, the
Dear Marek Vasut,
> Cc: Linus Walleij
> Cc: Jean Delvare
> Cc: Samuel Ortiz
> Cc: Mark Brown
> Cc: Guenter Roeck
> Cc: linux-kernel
> Cc: Grant Likely
> Signed-off-by: Marek Vasut
> ---
> drivers/gpio/gpio-ucb1400.c | 19 ++-
> drivers/mfd/ucb1400_core.c |5 +
>
ptrace_write_dr7() looks unnecessarily overcomplicated. We can
factor out ptrace_modify_breakpoint() and do not do "continue"
twice, just we need to pass the proper "disabled" argument to
ptrace_modify_breakpoint().
Signed-off-by: Oleg Nesterov
---
arch/x86/kernel/ptrace.c | 40 +++
On Sun, Apr 14, 2013 at 11:36:59AM -0700, Tejun Heo wrote:
> kdbus folks want a sane way to determine the cgroup path that a given
> task belongs to on a given hierarchy, which is a reasonble thing to
> expect from cgroup core.
>
> Implement task_cgroup_path_from_hierarchy().
>
> Signed-off-by: T
ptrace_write_dr7() skips ptrace_modify_breakpoint(disabled => true)
unless second_pass, this buys nothing but complicates the code and
means that we always do the main loop twice even if "disabled" was
never true.
The comment says:
Don't unregister the breakpoints right-away,
unle
Hello.
On top of "[PATCH 0/5] kill ptrace_{get,put}_breakpoints()".
Cleanup and preparation for the potential fix, see below.
--
Now the question. Initially I was going to make more patches
and fix the regression introduc
swap_pci_ref function is used by the IOMMU API code for swapping pci device
pointers, while determining the iommu group for the device.
Currently this function was being implemented for different IOMMU drivers.
This patch moves the function to pci.h so that the implementation can be
shared across v
Added the following domain attributes for the FSL PAMU driver:
1. Added new iommu stash attribute, which allows setting of the
LIODN specific stash id parameter through IOMMU API.
2. Added an attribute for enabling/disabling DMA to a particular
memory window.
3. Added domain attribute to chec
On Sun, 14 Apr 2013 21:12:05 +0200, Oleg Nesterov wrote:
> Jan, Frederic, et all. What do you think we should do?
>
> 1. Change ptrace_write_dr7() to do register_user_hw_breakpoint()
> if necessary.
>
> This is what I was going to do, but I am no longer sure
> we
Some filesystems try to optimize barrier flushes by maintaining
fs-specific generation counters, but if we introduce generic
flush generation counter for block device filesystems may use
it for fdatasync(2) optimization. Optimization should works if
userspace performs mutli-threaded IO with a lot
Track blkdev's flush generation counter on per-inode basis and update
inside end_io. If inode's flush generation counter is older than current
blkdev's flush counter inode's data was already flushed to stable media,
so we can skip explicit barrier. Optimization is safe only when inode's
end_io was
Callers may use this counter to optimize flushes
Signed-off-by: Dmitry Monakhov
---
block/blk-core.c |1 +
block/blk-flush.c |3 ++-
include/linux/blkdev.h |1 +
3 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c
index 074b75
From: Joe Perches
Date: Sat, 13 Apr 2013 22:03:16 -0700
> Convert various printk logging styles to current styles.
>
> Uncompiled, untested.
>
> Joe Perches (3):
> fec: Convert printks to netdev_
> gianfar: Use netdev_ when possible
> ucc_geth: Convert ugeth_ to pr_
All applied.
--
To un
On 04/14, Jan Kratochvil wrote:
>
> On Sun, 14 Apr 2013 21:12:05 +0200, Oleg Nesterov wrote:
> > Jan, Frederic, et all. What do you think we should do?
> >
> > 1. Change ptrace_write_dr7() to do register_user_hw_breakpoint()
> >if necessary.
> >
> >This is what I was going to do
On 10:22-20130413, Tony Lindgren wrote:
> * Nishanth Menon [130412 16:43]:
> > Thanks for checking up. Fixed all of them below, will post part of
> > series again, only if I need to address further comments in other
> > patches..
>
> Thanks it seems that the other ones are ready to go, just one
>
Use devm_request_and_ioremap function which provides more consistent error
handling.
Signed-off-by: Alexandru Gheorghiu
---
drivers/dma/txx9dmac.c |6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/dma/txx9dmac.c b/drivers/dma/txx9dmac.c
index 913f55c..471f9f1 10
Hi Steven,
I'm pleased to announce the 3.6.11.1-rt32 stable release.
Unfortunately, there is another compile error:
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_wait_for_error’:
drivers/gpu/drm/i915/i915_gem.c:118:3: warning: passing argument 1 of
‘rt_spin_lock’ from incompatible poin
Use ERR_CAST function instead of ERR_PTR and PTR_ERR.
Patch found using coccinelle.
Signed-off-by: Alexandru Gheorghiu
---
lib/digsig.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/digsig.c b/lib/digsig.c
index 2f31e6a..8793aed 100644
--- a/lib/digsig.c
+++ b/lib/di
Hi,
after update to 3.8, every update of the kernel ends up in an unbootable
machine. It is due to the following commit:
commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
Author: Matthew Garrett
Date: Sat Mar 2 19:40:17 2013 -0500
efi: be more paranoid about available space when creating var
Use ERR_CAST function instead of ERR_PTR and PTR_ERR.
Patch found using coccinelle.
Signed-off-by: Alexandru Gheorghiu
---
drivers/usb/gadget/composite.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
index 7
Use kstrdup function instead of kmalloc and strcpy.
Patch found using coccinelle.
Signed-off-by: Alexandru Gheorghiu
---
fs/reiserfs/super.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/fs/reiserfs/super.c b/fs/reiserfs/super.c
index 194113b..f8a23c3 100644
--- a/fs/
From: Dan Magenheimer
Add how-to for ramster.
Singed-off-by: Dan Magenheimer
Signed-off-by: Wanpeng Li
---
drivers/staging/zcache/ramster/HOWTO.txt | 249 ++
1 file changed, 249 insertions(+)
create mode 100644 drivers/staging/zcache/ramster/HOWTO.txt
diff --git
On Mon, Apr 15, 2013 at 07:56:56AM +0800, Wanpeng Li wrote:
> +This is a how-to document for RAMster. It applies to the March 9, 2013
> +version of RAMster, re-merged with the new zcache codebase, built and tested
> +on the 3.9 tree and submitted for the staging tree for 3.9.
This is not needed a
Dear Haojian Ahuang.
> > This patch looks like it should be in the 3.8-stable tree, should we
> apply
> > it?
> >
>
> It could be merged into 3.8-stable tree.
>
Thanks~
Best Regards.
> -Original Message-
> From: Haojian Zhuang [mailto:haojian.zhu...@linaro.org]
> Sent: Sunday, April 14
(2013/04/12 15:54), Yinghai Lu wrote:
> Index: linux-2.6/kernel/kexec.c
> ===
> --- linux-2.6.orig/kernel/kexec.c
> +++ linux-2.6/kernel/kexec.c
> @@ -1368,35 +1368,114 @@ static int __init parse_crashkernel_simp
> return 0;
>
Hi Guenter
> I really don't like that idea. It defeats a significant part of the
> purpose
> for having a watchdog, which is to prevent user-space hangups.
>
> To make this a driver option is even more odd - it forces every user of
> this
> driver to use it in-kernel only, and makes /dev/watchdog
Hi all,
First of all, I am not subscribed to the mailing list and I'd like to get the
answers directly to my email. Thank you!
I am working on a project where I am trying to detect the Out Of Memory machine
state and collect some data from the machine. I've created a LKM that hacks the
do_brk
Quoting Tejun Heo (t...@kernel.org):
> There's no reason to be using bitops, which tends to be more
> cumbersome, to handle root flags. Convert them to masks. Also, as
> they'll be moved to include/linux/cgroup.h and it's generally a good
> idea, add CGRP_ prefix.
>
> Note that flags are assigne
--- On Mon, 8/4/13, Joe Perches wrote:
> Use a more current logging style.
>
> Rename macro and uses.
> Add do {} while (0) to macro.
> Add DBG_ to macro.
> Add and use hfs_dbg_cont variant where appropriate.
>
> Signed-off-by: Joe Perches
> +++ b/fs/hfs/hfs_fs.h
> @@ -34,8 +34,18 @@
> //#
Quoting Tejun Heo (t...@kernel.org):
> While controllers shouldn't be accessing cgroupfs_root directly, it
> being hidden inside kern/cgroup.c makes somethings pretty silly. This
> makes routing hierarchy-wide settings which need to be visible to
> controllers cumbersome.
>
> We're gonna add anot
Quoting Tejun Heo (t...@kernel.org):
> It's a sad fact that at this point various cgroup controllers are
> carrying so many idiosyncrasies and pure insanities that it simply
> isn't possible to reach any sort of sane consistent behavior while
> maintaining staying fully compatible with what already
Quoting Tejun Heo (t...@kernel.org):
> Turn on use_hierarchy by default if sane_behavior is specified and
> don't create .use_hierarchy file.
>
> It is debatable whether to remove .use_hierarchy file or make it ro as
> the former could make transition easier in certain cases; however, the
> behavi
Quoting Tejun Heo (t...@kernel.org):
> Turn on use_hierarchy by default if sane_behavior is specified and
> don't create .use_hierarchy file.
>
> It is debatable whether to remove .use_hierarchy file or make it ro as
> the former could make transition easier in certain cases; however, the
> behavi
Another week, another -rc.
This is mostly random one-liners, with a few slightly larger driver
fixes. The most interesting (to me, probably to nobody else) fix is a
fix for a rather subtle TLB invalidate bug that only hits 32-bit PAE
due to the weird way that works. Even then it only hits you if y
On Fri, 2013-04-05 at 08:32 -0400, Eduardo Valentin wrote:
> This patch adds a helper function to get a reference of
> a thermal zone, based on the zone type name.
>
> It will perform a zone name lookup and return a reference
> to a thermal zone device that matches the name requested.
> In case th
On Fri, 2013-04-05 at 08:32 -0400, Eduardo Valentin wrote:
> This patch exports the thermal_zone_get_temp API so that driver
> writers can fetch temperature of thermal zones managed by other
> drivers.
>
> Acked-by: Durgadoss R
> Signed-off-by: Eduardo Valentin
refreshed the patch to modify dri
On Fri, 2013-04-05 at 08:32 -0400, Eduardo Valentin wrote:
> For boards that provide a PCB sensor close to SoC junction
> temperature, it is possible to remove the cumulative heat
> reported by the SoC temperature sensor.
>
> This patch changes the extrapolation computation to consider
> an extern
On Friday, April 12, 2013 5:25 AM, Andrew Bresticker wrote:
>
> Platform LCD devices may need to do some device-specific
> initialization before they can be used (regulator or GPIO setup,
> for example), but currently the driver does not support any way of
> doing this. This patch adds a probe()
On Mon, 2013-04-15 at 01:53 +0100, Hin-Tak Leung wrote:
> --- On Mon, 8/4/13, Joe Perches wrote:
> > Use a more current logging style.
[]
> I have been sitting on a patch which changes this part of the code to dynamic
> debugging, and it is much simplier. Just:
> #define dprint(flg, fmt, args...)
In the comment describing the sync_writers field of the btrfs_inode
struct, "fsyncing" was misspelled "fsycing."
Signed-off-by: Nathaniel Yazdani
---
diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
index d9b97d4..08b286b 100644
--- a/fs/btrfs/btrfs_inode.h
+++ b/fs/btrfs/btrfs_inode.
On Fri, 2013-04-12 at 11:16 +0200, Peter Zijlstra wrote:
> On Wed, 2013-04-10 at 11:48 -0400, Olivier Langlois wrote:
> > Please explain how expensive it is. All I am seeing is a couple of
> > additions.
>
> Let me start with this, since your earlier argument also refers to
> this.
>
> So yes it
--- On Mon, 15/4/13, Joe Perches wrote:
> On Mon, 2013-04-15 at 01:53 +0100,
> Hin-Tak Leung wrote:
> > --- On Mon, 8/4/13, Joe Perches
> wrote:
> > > Use a more current logging style.
> []
> > I have been sitting on a patch which changes this part
> of the code to dynamic debugging, and it is m
On 04/11/2013 11:54 PM, Yinghai Lu wrote:
> + /*
> + * two parts from lib/swiotlb.c:
> + * swiotlb size: user specified with swiotlb= or default.
> + * swiotlb overflow buffer: now is hardcoded to 32k,
> + * rou
On Fri, Apr 12, 2013 at 11:38:04PM -0700, Paul E. McKenney wrote:
> On Fri, Apr 12, 2013 at 04:54:02PM -0700, Josh Triplett wrote:
> > On Fri, Apr 12, 2013 at 04:19:13PM -0700, Paul E. McKenney wrote:
> > > From: "Paul E. McKenney"
> > >
> > > Systems with HZ=100 can have slow bootup times due to
On Mon, 2013-04-15 at 02:56 +0100, Hin-Tak Leung wrote:
> --- On Mon, 15/4/13, Joe Perches wrote:
> > On Mon, 2013-04-15 at 01:53 +0100,
> > Hin-Tak Leung wrote:
> > > --- On Mon, 8/4/13, Joe Perches wrote:
> > > > Use a more current logging style.
> > []
> > > I have been sitting on a patch whic
On Mon, Apr 15, 2013 at 12:43:31AM +, Kim, Milo wrote:
> Hi Guenter
>
> > I really don't like that idea. It defeats a significant part of the
> > purpose
> > for having a watchdog, which is to prevent user-space hangups.
> >
> > To make this a driver option is even more odd - it forces every
From: Sahara
Somehow tracepoint_entry_add_probe function allows a null probe function.
And, this may lead to unexpected result since the number of probe
functions in an entry can be counted by checking whether probe is null
or not in for-loop.
This patch prevents the null probe from being added.
> -Original Message-
> From: Guenter Roeck [mailto:li...@roeck-us.net]
> Sent: Monday, April 15, 2013 11:07 AM
> To: Kim, Milo
> Cc: w...@iguana.be; linux-watch...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH 1/2] watchdog: introduce new watchdog AUTOSTART
> option
When hot removing memory presented at boot time, following messages are shown:
[ 296.867031] [ cut here ]
[ 296.922273] kernel BUG at mm/slub.c:3409!
[ 296.970229] invalid opcode: [#1] SMP
[ 297.019453] Modules linked in: ebtable_nat ebtables xt_CHECKSUM
iptable_m
This is the start of the stable review cycle for the 3.0.74 release.
There are 11 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 should be made by Wed Apr 17 02:05:34 UTC 2013.
Anything receive
1 - 100 of 228 matches
Mail list logo
