Re: [PATCH v3 08/23] mm/memblock: Add memblock memory allocation apis

Andrew, On Monday 09 December 2013 07:25 PM, Andrew Morton wrote: > On Mon, 9 Dec 2013 16:50:41 -0500 Santosh Shilimkar > wrote: > >> Introduce memblock memory allocation APIs which allow to support >> PAE or LPAE extension on 32 bits archs where the physical memory >> start address can be

Re: [PATCH v6 2/8] x86: allow to call text_poke_bp during boot

On Tue, 10 Dec 2013 16:46:12 +0100 Borislav Petkov wrote: > On Tue, Dec 10, 2013 at 04:42:14PM +0100, Petr Mladek wrote: > > We would like to use text_poke_bp in ftrace. It might be called also during > > boot when there is only one CPU and we do not need to sync the others. > > > > The check

[PATCH 01/18] mm: numa: Serialise parallel get_user_page against THP migration

Base pages are unmapped and flushed from cache and TLB during normal page migration and replaced with a migration entry that causes any parallel or gup to block until migration completes. THP does not unmap pages due to a lack of support for migration entries at a PMD level. This allows races with

Re: XFS security fix never sent to -stable?

Hi, On Tue, Dec 10, 2013 at 08:31:23AM -0600, Eric Sandeen wrote: > On 12/10/13, 7:15 AM, Josh Boyer wrote: > > On Tue, Dec 10, 2013 at 2:56 AM, Greg KH wrote: > >> On Tue, Dec 10, 2013 at 10:55:23AM +1100, Dave Chinner wrote: > >>> [cc xfs list, cc sta...@vger.kernel.org] > >>> > >>> On Mon,

[PATCH 06/18] mm: numa: Ensure anon_vma is locked to prevent parallel THP splits

The anon_vma lock prevents parallel THP splits and any associated complexity that arises when handling splits during THP migration. This patch checks if the lock was successfully acquired and bails from THP migration if it failed for any reason. Cc: sta...@vger.kernel.org Signed-off-by: Mel

Re: [PATCH 2/2] sched: update runqueue clock before migrations away

On 10/12/13 15:14, Peter Zijlstra wrote: On Tue, Dec 10, 2013 at 01:24:21PM +, Chris Redpath wrote: What happens is that if you have a task which sleeps for a while and wakes on a different CPU and the previous CPU hasn't had a tick for a while, then that sleep time is lost. /me more

Re: [PATCH 16/17] uprobes: Allocate ->utask before handler_chain() for tracing handlers

On 12/10, Masami Hiramatsu wrote: > > (2013/12/09 15:20), Namhyung Kim wrote: > > From: Oleg Nesterov > > > > uprobe_trace_print() and uprobe_perf_print() need to pass the additional > > info to call_fetch() methods, currently there is no simple way to do this. > > > > current->utask looks like a

[PATCH 05/18] mm: numa: Do not clear PTE for pte_numa update

The TLB must be flushed if the PTE is updated but change_pte_range is clearing the PTE while marking PTEs pte_numa without necessarily flushing the TLB if it reinserts the same entry. Without the flush, it's conceivable that two processors have different TLBs for the same virtual address and at

Re: [PATCH 00/17] NUMA balancing segmentation fault fixes and misc followups v4

On Tue, Dec 10, 2013 at 03:51:18PM +, Mel Gorman wrote: > Changelog since V3 > o Dropped a tracing patch > o Rebased to 3.13-rc3 > o Removed unnecessary ptl acquisition > *sigh* There really are only 17 patches in the series. 18/18 does not exist. -- Mel Gorman SUSE Labs -- To unsubscribe

[PATCH 07/18] mm: numa: Avoid unnecessary work on the failure path

If a PMD changes during a THP migration then migration aborts but the failure path is doing more work than is necessary. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/migrate.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [PATCH 1/2] perf tools: Automate setup of FEATURE_CHECK_(C|LD)FLAGS-all variables

Jiri, On 10 December 2013 14:55, Jiri Olsa wrote: > On Tue, Dec 10, 2013 at 01:24:02PM +0100, Jean Pihet wrote: >> Add CFLAGS and LDFLAGS for each feature to be checked during the >> build. This allows to pass particular flags and parameters to the >> feature checks compilation. >> >> Use the

Re: [PATCH 1/2] x86, microcode: Do Intel microcode revision check signed

On Tue, Dec 10, 2013 at 10:30:00AM -0500, Konrad Rzeszutek Wilk wrote: > On Fri, Dec 06, 2013 at 01:04:02PM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > The Intel SDM Vol 3 9.11.1 Microcode update states that > > the update revision field is signed. However we do the comparison > >

Re: [PATCHv4] clocksource: dw_apb_timer_of: Fix read_sched_clock

On Tue, 2013-12-10 at 16:53 +0100, Ingo Molnar wrote: > * dingu...@altera.com wrote: > > > From: Dinh Nguyen > > > > The read_sched_clock should return the ~value because the clock is a > > countdown implementation. read_sched_clock() should be the same as > > __apbt_read_clocksource(). > > >

Re: [PATCH 13/41] percpu: Add raw_cpu_ops

* Tejun Heo wrote: > On Tue, Dec 10, 2013 at 04:45:06PM +0100, Ingo Molnar wrote: > > > > * Tejun Heo wrote: > > > > > On Tue, Dec 03, 2013 at 05:32:45PM -0600, Christoph Lameter wrote: > > > > The patches following this one will add preemption checks to __this_cpu > > > > ops so we need to

[PATCH 09/18] mm: numa: Clear numa hinting information on mprotect

On a protection change it is no longer clear if the page should be still accessible. This patch clears the NUMA hinting fault bits on a protection change. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/huge_memory.c | 2 ++ mm/mprotect.c| 2 ++ 2

[PATCH 08/18] sched: numa: Skip inaccessible VMAs

Inaccessible VMA should not be trapping NUMA hint faults. Skip them. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- kernel/sched/fair.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index

[PATCH 11/18] mm: fix TLB flush race between migration, and change_protection_range

From: Rik van Riel There are a few subtle races, between change_protection_range (used by mprotect and change_prot_numa) on one side, and NUMA page migration and compaction on the other side. The basic race is that there is a time window between when the PTE gets made non-present (PROT_NONE or

[PATCH 14/18] mm: numa: Limit scope of lock for NUMA migrate rate limiting

NUMA migrate rate limiting protects a migration counter and window using a lock but in some cases this can be a contended lock. It is not critical that the number of pages be perfect, lost updates are acceptable. Reduce the importance of this lock. Signed-off-by: Mel Gorman Reviewed-by: Rik van

[PATCH 13/18] mm: numa: Make NUMA-migrate related functions static

numamigrate_update_ratelimit and numamigrate_isolate_page only have callers in mm/migrate.c. This patch makes them static. Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/migrate.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/mm/migrate.c b/mm/migrate.c

[PATCH 03/18] mm: Clear pmd_numa before invalidating

pmdp_invalidate clears the present bit without taking into account that it might be in the _PAGE_NUMA bit leaving the PMD in an unexpected state. Clear pmd_numa before invalidating. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/pgtable-generic.c | 3 +++

Re: [PATCHv4] clocksource: dw_apb_timer_of: Fix read_sched_clock

* dingu...@altera.com wrote: > From: Dinh Nguyen > > The read_sched_clock should return the ~value because the clock is a > countdown implementation. read_sched_clock() should be the same as > __apbt_read_clocksource(). > > Maintain backwards compatibility for "dw-apb-timer-sp" and >

Re: [PATCH] sched: Revert need_resched() to look at TIF_NEED_RESCHED

On Mon, Dec 09, 2013 at 12:11:33PM +0530, Aneesh Kumar K.V wrote: > Peter Zijlstra writes: > > > Subject: sched: Revert need_resched() to look at TIF_NEED_RESCHED > > From: Peter Zijlstra > > Date: Fri Sep 27 17:20:30 CEST 2013 > > > > Yuanhan reported a serious throughput regression in his

[PATCH 04/18] mm: numa: Do not clear PMD during PTE update scan

If the PMD is flushed then a parallel fault in handle_mm_fault() will enter the pmd_none and do_huge_pmd_anonymous_page() path where it'll attempt to insert a huge zero page. This is wasteful so the patch avoids clearing the PMD when setting pmd_numa. Cc: sta...@vger.kernel.org Signed-off-by: Mel

[PATCH 17/18] sched: Add tracepoints related to NUMA task migration

This patch adds three tracepoints o trace_sched_move_numawhen a task is moved to a node o trace_sched_swap_numawhen a task is swapped with another task o trace_sched_stick_numa when a numa-related migration fails The tracepoints allow the NUMA scheduler activity to be

[PATCH 10/18] mm: numa: Avoid unnecessary disruption of NUMA hinting during migration

do_huge_pmd_numa_page() handles the case where there is parallel THP migration. However, by the time it is checked the NUMA hinting information has already been disrupted. This patch adds an earlier check with some helpers. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik

[PATCH 12/18] mm: numa: Defer TLB flush for THP migration as long as possible

THP migration can fail for a variety of reasons. Avoid flushing the TLB to deal with THP migration races until the copy is ready to start. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman --- mm/huge_memory.c | 7 --- mm/migrate.c | 3 +++ 2 files changed, 3 insertions(+), 7

[PATCH 16/18] mm: numa: Do not automatically migrate KSM pages

KSM pages can be shared between tasks that are not necessarily related to each other from a NUMA perspective. This patch causes those pages to be ignored by automatic NUMA balancing so they do not migrate and do not cause unrelated tasks to be grouped together. Signed-off-by: Mel Gorman

[PATCH 15/18] mm: numa: Trace tasks that fail migration due to rate limiting

A low local/remote numa hinting fault ratio is potentially explained by failed migrations. This patch adds a tracepoint that fires when migration fails due to migration rate limitation. Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- include/trace/events/migrate.h | 26

[PATCH 02/18] mm: numa: Call MMU notifiers on THP migration

MMU notifiers must be called on THP page migration or secondary MMUs will get very confused. Cc: sta...@vger.kernel.org Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel --- mm/migrate.c | 22 ++ 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/mm/migrate.c

[PATCH] null_blk: mem garbage on NUMA systems during init

For NUMA systems, initializing the blk-mq layer and using per node hctx. We initialize submit queues to 1, while blk-mq nr_hw_queues is initialized to the number of NUMA nodes. This makes the null_init_hctx function overwrite memory outside of what it allocated. In my case it lead to writing

[PATCH 00/17] NUMA balancing segmentation fault fixes and misc followups v4

Changelog since V3 o Dropped a tracing patch o Rebased to 3.13-rc3 o Removed unnecessary ptl acquisition Alex Thorlton reported segementation faults when NUMA balancing is enabled on large machines. There is no obvious explanation from the console what the problem but similar problems have been

[PATCHv4] clocksource: dw_apb_timer_of: Fix read_sched_clock

From: Dinh Nguyen The read_sched_clock should return the ~value because the clock is a countdown implementation. read_sched_clock() should be the same as __apbt_read_clocksource(). Maintain backwards compatibility for "dw-apb-timer-sp" and "dw-apb-timer-osc". Signed-off-by: Dinh Nguyen ---

Re: [PATCH v2 00/11] Consolidate asm/fixmap.h files

On Tue, 2013-12-10 at 09:48 +0100, Jonas Bonn wrote: > Hi Mark, > > Is there some reason you've excluded OpenRISC here? Did you just miss > it, or does the implementation diverage too much to be usable with > your generic version? It was the runtime BUG() in fix_to_virt() instead of the usual

Re: [PATCH 13/41] percpu: Add raw_cpu_ops

On Tue, Dec 10, 2013 at 04:45:06PM +0100, Ingo Molnar wrote: > > * Tejun Heo wrote: > > > On Tue, Dec 03, 2013 at 05:32:45PM -0600, Christoph Lameter wrote: > > > The patches following this one will add preemption checks to __this_cpu > > > ops so we need to have an alternative way to use

Re: [PATCH v2 15/16] wl1251: Add sysfs file address for setting permanent mac address

Pali Rohár writes: > Driver wl1251 generating mac address randomly at startup and there is no way > to > set permanent mac address via SET_IEEE80211_PERM_ADDR. This patch export sysfs > file which can set permanent mac address by userspace helper program. Patch is > needed for devices which do

Re: [RFC PATCH tip 0/5] tracing filters with BPF

* Alexei Starovoitov wrote: > > I'm fine if it becomes a requirement to have a vmlinux built with > > DEBUG_INFO to use BPF and have a tool like perf to translate the > > filters. But it that must not replace what the current filters do > > now. That is, it can be an add on, but not a

Re: [GIT PULL 00/21] perf/core improvements and fixes

* Jiri Olsa wrote: > On Tue, Dec 10, 2013 at 12:07:59PM +0100, Ingo Molnar wrote: > > > > SNIP > > > > > Pulled, thanks Arnaldo! > > > > There's one detail I noticed about the recent trace-plugin changes: > > > > comet:~/tip/tools/perf> make install > > BUILD: Doing 'make -j12'

Re: [GIT PULL 00/21] perf/core improvements and fixes

On Tue, Dec 10, 2013 at 12:07:59PM +0100, Ingo Molnar wrote: > SNIP > > Pulled, thanks Arnaldo! > > There's one detail I noticed about the recent trace-plugin changes: > > comet:~/tip/tools/perf> make install > BUILD: Doing 'make -j12' parallel build > SUBDIR Documentation >

Re: [PATCH v2 02/16] wl1251: add sysfs interface for bluetooth coexistence mode configuration

Pali Rohár writes: > From: David Gnedt > > Port the bt_coex_mode sysfs interface from wl1251 driver version included > in the Maemo Fremantle kernel to allow bt-coexistence mode configuration. > This enables userspace applications to set one of the modes > WL1251_BT_COEX_OFF,

process 'stuck' at exit.

I woke up to find my fuzzer in a curious state. 1121 pts/5SN+0:00 | \_ ../trinity -q -l off -N 99 -C 42 1130 pts/5SN+0:01 | \_ ../trinity -q -l off -N 99 -C 42 1131 pts/5SN+0:17 | \_ ../trinity -q -l off -N 99 -C 42 10818 ?

Re: [PATCH v3 02/23] mm/memblock: debug: don't free reserved array if !ARCH_DISCARD_MEMBLOCK

Hi Andrew, On 12/10/2013 02:11 AM, Andrew Morton wrote: > On Mon, 9 Dec 2013 16:50:35 -0500 Santosh Shilimkar > wrote: > >> Now the Nobootmem allocator will always try to free memory allocated for >> reserved memory regions (free_low_memory_core_early()) without taking >> into to account

Re: [PATCH v6 2/8] x86: allow to call text_poke_bp during boot

On Tue, Dec 10, 2013 at 04:42:14PM +0100, Petr Mladek wrote: > We would like to use text_poke_bp in ftrace. It might be called also during > boot when there is only one CPU and we do not need to sync the others. > > The check is must to have because there are also disabled interrupts during > the

[PATCH v6 7/8] x86: patch all traced function calls using the int3-based framework

Let's continue with replacing the existing Int3-based framework in ftrace with the new generic function introduced by the commit fd4363fff3d9 (x86: Introduce int3 (breakpoint)-based instruction patching) This time use it in ftrace_replace_code that modifies all the watched function calls. If we

Re: [PATCH 13/41] percpu: Add raw_cpu_ops

* Tejun Heo wrote: > On Tue, Dec 03, 2013 at 05:32:45PM -0600, Christoph Lameter wrote: > > The patches following this one will add preemption checks to __this_cpu > > ops so we need to have an alternative way to use this_cpu operations > > without preemption checks. > > > > raw_cpu_ops will

[PATCH v6 8/8] x86: enable/disable ftrace graph call using new int3-based framework

One more change related to replacing the existing Int3-based framework with the new generic function introduced by the commit fd4363fff3d9 (x86: Introduce int3 (breakpoint)-based instruction patching) ftrace_enable_ftrace_graph_caller and ftrace_disable_ftrace_graph_caller modified the jump

[PATCH v6 6/8] x86: modify ftrace function using the new int3-based framework

The commit fd4363fff3d9 (x86: Introduce int3 (breakpoint)-based instruction patching) uses the same technique that has been used in ftrace since 08d636b ("ftrace/x86: Have arch x86_64 use breakpoints instead of stop machine") It would be great to use the new generic implementation and clean up

[PATCH v6 4/8] x86: speed up int3-based patching using direct write

When trying to use text_poke_bp_iter in ftrace, the result was slower than the original implementation. It turned out that one difference was in text_poke vs. ftrace_write. text_poke did many extra operations to make sure that code was read-write and the change was atomic. In fact, we do not

[PATCH v6 3/8] x86: add generic function to modify more calls using int3 framework

The commit fd4363fff3d9 (x86: Introduce int3 (breakpoint)-based instruction patching) uses the same technique that has been used in ftrace since 08d636b ("ftrace/x86: Have arch x86_64 use breakpoints instead of stop machine") When trying to use text_poke_bp in dynamic ftrace, the process was

[PATCH v6 5/8] x86: do not trace __probe_kernel_read

probe_kernel_read is used when modifying function calls in ftrace_replace_code, see arch/x86/kernel/ftrace.c. On x86, the code is replaced using int3 guard. All functions are patched in parallel to reduce an expensive synchronization of all CPUs. The result is that all affected functions are

Re: [PATCH v2 4/4] futex: Avoid taking hb lock if nothing to wakeup

* Davidlohr Bueso wrote: > On Fri, 2013-12-06 at 19:26 +0100, Thomas Gleixner wrote: > > On Tue, 3 Dec 2013, Davidlohr Bueso wrote: > > > Signed-off-by: Waiman Long > > > Signed-off-by: Jason Low > > > Signed-off-by: Davidlohr Bueso > > > > Who is the author of this? According to the SOB

[PATCH v6 2/8] x86: allow to call text_poke_bp during boot

We would like to use text_poke_bp in ftrace. It might be called also during boot when there is only one CPU and we do not need to sync the others. The check is must to have because there are also disabled interrupts during the boot. Then the call would cause a deadlock, see the warning in

[PATCH v6 1/8] x86: allow to handle errors in text_poke function family

The text_poke functions called BUG() in case of error. This was too strict. There are situations when the system is still usable even when the patching has failed, for example when enabling the dynamic ftrace. This commit modifies text_poke and text_poke_bp functions to return an error code

[PATCH v6 0/8] x86: use new text_poke_bp in ftrace

This resubmit primary adds text_poke*_or_die wrappers as suggested by Masami Hiramatsu. See below for more details. It basically modifies only the first patch in the set. The commit fd4363fff3d9 (x86: Introduce int3 (breakpoint)-based instruction patching) uses the same technique that has been

Re: [PATCH] mm/slab.c: check pointer slabp before using it in alloc_slabmgmt()

On Sun, 8 Dec 2013, ethan.zhao wrote: > Move the NULL check of slabp to the right place before refer its memeber in > function alloc_slabmgmt(). Ok this patch is needed for 2.6.30 to 3.12 Acked-by: Christoph Lameter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

pull request: bluetooth-next 2013-12-10

Hi John, More patches to 3.14. Here we have the support for Low Energy Connection Oriented Channels (LE CoC). Basically, as the name says, this adds supports for connection oriented channels in the same way we already have them for BR/EDR connections so profiles/protocols that work on top of

Re: [PATCH] mm/slab.c: check pointer slabp before using it in alloc_slabmgmt()

On Tue, 10 Dec 2013, Ethan Zhao wrote: > No, stable 3.12.4 and 3.12.3 need this patch. 3.13RC doesn't > need it anymore. Hmmm.. Then this commit may have fixed it: commit 0172f779e4314639a8ed440082cfe9e3450954e8 Author: Joonsoo Kim Date: Wed Oct 30 19:04:00 2013 +0900 slab: fix to

Re: randconfig build error with next-20131210, in drivers/crypto/ccp/ccp-pci.c

On Tuesday, December 10, 2013 07:21:36 AM Jim Davis wrote: > Building with the attached random configuration file, > > drivers/crypto/ccp/ccp-pci.c: In function ‘ccp_get_msix_irqs’: > drivers/crypto/ccp/ccp-pci.c:44:20: error: array type has incomplete > element type >

Re: [PATCH 13/41] percpu: Add raw_cpu_ops

On Tue, Dec 03, 2013 at 05:32:45PM -0600, Christoph Lameter wrote: > The patches following this one will add preemption checks to __this_cpu > ops so we need to have an alternative way to use this_cpu operations > without preemption checks. > > raw_cpu_ops will be the basis for all other ops

Re: rcu: Avoid irq disable in rcu_cpu_kthread

On Mon, 9 Dec 2013, Paul E. McKenney wrote: > On Thu, Dec 05, 2013 at 09:06:55PM +, Christoph Lameter wrote: > > Once we have the per cpu patchset merged we could do the following [it > > even works without that patchset but the __this_cpu ops will not do > > preemption checks]. Would this

Re: randconfig build error with next-20131210, in drivers/crypto/ccp

On Monday, December 09, 2013 10:30:17 PM Jim Davis wrote: > Building with the attached random configuration file, > > drivers/built-in.o: In function `ccp_init': > /home/jim/linux/drivers/crypto/ccp/ccp-dev.c:402: undefined reference > to `hwrng_register' > drivers/built-in.o: In function

Re: [PATCH 28/28] perf tools: Add udis86 disassembler feature check

* Jiri Olsa wrote: > On Thu, Dec 05, 2013 at 11:45:46AM +0100, Ingo Molnar wrote: > > SNIP > > > > > > > > > 1) > > > > > > > > So, the first problem I can see is in the output: > > > > > > > > Auto-detecting system features: > > > > ... backtrace: [ on ] > > > > ...

Re: [PATCH 1/2] x86, microcode: Do Intel microcode revision check signed

On Fri, Dec 06, 2013 at 01:04:02PM -0800, Andi Kleen wrote: > From: Andi Kleen > > The Intel SDM Vol 3 9.11.1 Microcode update states that > the update revision field is signed. However we do the comparison > unsigned, as the comparison gets promoted. > > Use a cast to really do a signed

Re: [PATCH net V2 1/2] tun: unbreak truncated packet signalling

On Tue, Dec 10, 2013 at 01:49:45PM +0800, Jason Wang wrote: > Commit 6680ec68eff47d36f67b4351bc9836fd6cba9532 > (tuntap: hardware vlan tx support) breaks the truncated packet signal by nev > return a length greater than iov length in tun_put_user(). This patch fixes > by always return the length

Re: [PATCH v2] gpiolib: return -ENOENT if no GPIO mapping exists

On Tue, 2013-12-10 at 23:37 +0900, Alexandre Courbot wrote: > Some devices drivers make use of optional GPIO parameters. For such > drivers, it is important to discriminate between the case where no > GPIO mapping has been defined for the function they are requesting, and > the case where a

Re: [PATCH -tip v4 0/6] kprobes: introduce NOKPROBE_SYMBOL() and fixes crash bugs

* Masami Hiramatsu wrote: > (2013/12/05 19:21), Ingo Molnar wrote: > > > > * Masami Hiramatsu wrote: > > > >>> So we need both a maintainable and a sane/safe solution, and I'd > >>> like to apply the whole thing at once and be at ease that the > >>> solution is round. We should have done

Re: questions of cpuidle

On 12/10/2013 10:53 PM, Arjan van de Ven wrote: > On 12/9/2013 10:08 PM, Alex Shi wrote: >> And for monitor/mwait idle method, seems deep c-state cpu need to keep a >> eye on memory bus. So seems the memory controller in cpu package is >> impossible to get into sleep, right? > not the memory bus >

Re: 3.11.4: kernel BUG at fs/buffer.c:1268

On Tue 10-12-13 04:35:28, George Spelvin wrote: > One of those additional WARN_ON tests tripped, hooray! > And it turned out to be in the ext4 metadata checksumming. To be > precise, ext4_block_bitmap_csum_set() returned with irqs disabled, > and kaboom. Ha, great. Thanks for the persistence in

Re: [PATCH net V2 2/2] macvtap: signal truncated packets

On Tue, Dec 10, 2013 at 01:49:46PM +0800, Jason Wang wrote: > macvtap_put_user() never return a value grater than iov length, this in fact > bypasses the truncated checking in macvtap_recvmsg(). Fix this by always > returning the size of packet plus the possible vlan header to let the trunca >

Re: [PATCH 2/3] perf tools: allow user to specify hardware breakpoint bp_len

On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com wrote: > From: Jacob Shin > > Currently bp_len is given a default value of 4. Allow user to override it: > > $ perf stat -e mem:0x1000/8 > ^ > bp_len > > If no

Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation updates

* David Miller wrote: > From: Steven Rostedt > Date: Thu, 5 Dec 2013 08:51:46 -0500 > > > I wish vger wouldn't do that. I wonder how much spam is really flagged > > by this one characteristic alone. That is, spam that would have made it > > otherwise, but because of the Cc list, it was

Re: [PATCH 1/3] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8

On Wed, Oct 02, 2013 at 11:11:06AM -0500, suravee.suthikulpa...@amd.com wrote: > From: Jacob Shin > > Implement hardware breakpoint address mask for AMD Family 16h and > above processors. CPUID feature bit indicates hardware support for > DRn_ADDR_MASK MSRs. These masks further qualify DRn/DR7

Re: [PATCH 35/41] tile: Replace __get_cpu_var uses

On Mon, 9 Dec 2013, Chris Metcalf wrote: > Except for a comment typo: > > > /* > > * Read the set of maskable interrupts. > > - * We avoid the preemption warning here via __this_cpu_ptr since even > > + * We avoid the preemption warning here via raw_cpu_ptr since even > > * if irqs are

[PATCH driver-core-next] sysfs: fix use-after-free in sysfs_kill_sb()

>From e09aae4796ac5b90c6514fc9789fc259bf783129 Mon Sep 17 00:00:00 2001 From: Tejun Heo Date: Tue, 10 Dec 2013 10:16:30 -0500 While restructuring the [u]mount path, 4b93dc9b1c68 ("sysfs, kernfs: prepare mount path for kernfs") incorrectly updated sysfs_kill_sb() so that it first kills

Re: [PATCH v2 1/3] nohz_full: fix code sytle issue of tick_nohz_full_stop_tick

On 12/03/2013 11:00 PM, Morten Rasmussen wrote: > In subject: s/sytle/style/ > > On Tue, Dec 03, 2013 at 12:35:10PM +, Alex Shi wrote: >> > Code usually starts with 'tab' instead of 7 'space'es in kernel >> > Found another function has the code style issue too. >From

Re: [PATCH tip/core/locking 4/4] Documentation/memory-barriers.txt: Document ACCESS_ONCE()

* Paul E. McKenney wrote: > > [...] > > > > > + (*) The compiler is within its rights to reorder memory accesses unless > > > + you tell it not to. For example, consider the following interaction > > > + between process-level code and an interrupt handler: > > > + > > > + void

Re: [question] sched: idle_avg and migration latency

CC to MikeG, he written this part. :) I try to explain sth I know. I am sorry if my understanding incorrect. On 12/10/2013 07:30 PM, Daniel Lezcano wrote: > > Hi All, > > I am trying to understand how is computed the idle_avg and how it is > used regarding the migration latency. > > 1. What is

Re: [PATCH 2/2] sched: update runqueue clock before migrations away

On Tue, Dec 10, 2013 at 01:24:21PM +, Chris Redpath wrote: > What happens is that if you have a task which sleeps for a while and wakes > on a different CPU and the previous CPU hasn't had a tick for a while, then > that sleep time is lost. /me more confused now. Where does

Re: [question] sched: idle_avg and migration latency

On Tue, 2013-12-10 at 12:30 +0100, Daniel Lezcano wrote: > Hi All, > > I am trying to understand how is computed the idle_avg and how it is > used regarding the migration latency. > > 1. What is the sysctl_sched_migration_cost value ? It is initialized to > 50UL. Is it an arbitrarily

Re: [PATCH tip/core/locking 4/4] Documentation/memory-barriers.txt: Document ACCESS_ONCE()

* Paul E. McKenney wrote: > On Thu, Dec 05, 2013 at 10:05:47AM -0800, Paul E. McKenney wrote: > > On Thu, Dec 05, 2013 at 10:50:42AM +0100, Ingo Molnar wrote: > > > > > > * Paul E. McKenney wrote: > > > > > > > + (*) The compiler is within its rights to reload a variable, for > > > >

Re: Will CPU 0 be forever prohibited from NO_HZ_FULL status?

On Tue, Dec 10, 2013 at 03:37:03PM +0100, Frederic Weisbecker wrote: > On Wed, Dec 04, 2013 at 06:50:37PM -0800, Paul E. McKenney wrote: > > On Thu, Dec 05, 2013 at 02:20:55AM +0100, Frederic Weisbecker wrote: > > > On Wed, Dec 04, 2013 at 11:39:57AM -0800, Paul E. McKenney wrote: > > > > Hello,

Re: [RFC part2 PATCH 2/9] ARM64 / ACPI: Prefill cpu possible/present maps and map logical cpu id to APIC id

On 2013年12月10日 20:53, Grant Likely wrote: On Mon, 2 Dec 2013 23:44:47 +0800, Hanjun Guo wrote: When boot the kernel with MADT, the cpu possible and present maps should be prefilled for cpu topology and acpi based cpu hot-plug. The logic cpu id maps to APIC id (GIC id) is also implemented, it

Re: [PATCH 04/10] net: stmmac: sunxi platfrom extensions for GMAC in Allwinner A20 SoC's

On 09/12/13 17:34, Chen-Yu Tsai wrote: > Hi, > > On Mon, Dec 9, 2013 at 7:10 PM, srinivas kandagatla > wrote: >> Hi Chen, >> Good to know that Allwinner uses gmac. > > To my knowledge, Allwinner has never confirmed this. > >> On ST SoC, we have very similar requirements, before we merge any

Re: 50 Watt idle power regression bisected to Linux-3.10

* Thomas Gleixner wrote: > On Tue, 10 Dec 2013, Mike Galbraith wrote: > > vogelweide:~/:[130]# turbostat -P -i 60 > > pk cor CPU%c0 GHz TSC SMI%c1%c3%c6 CTMP %pc3 %pc6 > > 0.02 2.12 2.26 0 43.40 56.57 0.00 53 33.81 0.00 > > 0 0 0 0.23 2.10

Re: [GIT PULL 00/21] perf/core improvements and fixes

* Arnaldo Carvalho de Melo wrote: > Em Tue, Dec 10, 2013 at 01:18:01PM +0100, Ingo Molnar escreveu: > > > > * Adrian Hunter wrote: > > > > > -void dso__set_short_name(struct dso *dso, const char *name) > > > +void dso__set_short_name(struct dso *dso, const char *name, bool > > >

Re: [PATCH] net-tg3: Initialize REG_BASE_ADDR at PCI config offset 120 to 0

Michael, The only time I see crashes is after the tg3 driver has been loaded into the system. I our use case we are poking around /sys/devices/pci//config. I guess you will incorporate the original patch into the driver and we can abandon this patch. Regards Nat On Mon,

Re: [PATCH v7 2/5] usb: gadget: add quirk_ep_out_aligned_size field to struct usb_gadget

On Tue, Dec 10 2013, David Cohen wrote: > I've got no idea how returns became reguens :) The keys are like right next to each other . ;) > But maybe Felipe can fix it when applying? -- Best regards, _ _ .o. | Liege of Serenely

Re: [PATCH 2/2] arm: keystone: enable watchdog support

+ CC devicet...@vger.kernel.org linux-arm-ker...@lists.infradead.org linux-kernel@vger.kernel.org On 12/10/2013 04:47 PM, Ivan Khoronzhuk wrote: After Keystone watchdog driver updates are already merged we can enable WDT in config. Signed-off-by: Ivan Khoronzhuk --- Based on

Re: questions of cpuidle

On 12/9/2013 10:08 PM, Alex Shi wrote: And for monitor/mwait idle method, seems deep c-state cpu need to keep a eye on memory bus. So seems the memory controller in cpu package is impossible to get into sleep, right? not the memory bus the cache coherency logic ;-) -- To unsubscribe from this

Re: [PATCH 1/2] arm: dts: keystone: add watchdog entry

+ CC devicet...@vger.kernel.org linux-arm-ker...@lists.infradead.org linux-kernel@vger.kernel.org On 12/10/2013 04:47 PM, Ivan Khoronzhuk wrote: Add watchdog entry to keystone device tree. Acked-by: Guenter Roeck Signed-off-by: Ivan Khoronzhuk --- Based on

Re: [PATCH 1/3] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8

On Wed, Dec 04, 2013 at 02:57:43PM +0100, Oleg Nesterov wrote: > > Ideally it would be nice if we drop bp_mask and use extended ranges > > only when len > 8. How does that sound? > > Again, iirc, this is what the code does. except (in essence) it checks > mask != 0 instead of len > 8. > > And

[PATCH driver-core-next] sysfs: bail early from kernfs_file_mmap() to avoid spurious lockdep warning

Hello, Yeap, I was planning to send this out earlier but was completely passed out yesterday after the first snowboarding in over a decade. :) The offending commit a8b14744429f isn't applicable to driver-core-next. This was done this way because no matter what we do, conflict is inevitable and

Re: [PATCH v10] x86, apic, kexec, Documentation: Add disable_cpu_apic kernel parameter

On Wed, Dec 04, 2013 at 05:10:58PM +0900, HATAYAMA Daisuke wrote: > This patch set is to allow kdump 2nd kernel to wake up multiple CPUs, > a continueing work from: > > [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP > https://lkml.org/lkml/2013/10/16/300. > > At v4, basic

Re: [RFC][PATCH 0/7] sched: Optimize sched_clock bits

On Tue, Dec 03, 2013 at 04:10:53PM +0100, Peter Zijlstra wrote: > Also, static_key and related APIs suck donkey ballz -- I did indeed > promise myself I'd not step into that bike shed contest but having had > to use them again *painfull*. > POST: > > [5.061000] sched_clock_stable: 1 > [

RE: [PATCH 3.4 01/25] crypto: scatterwalk - Set the chain pointer indication bit

Hi Greg, This patch is probably not needed in any of the stable branches, but if you do add it you'll need to also include a patch that changes the use of an sg_page to an sg_chain_ptr to prevent a BUG_ON when CONFIG_DEBUG_SG is enabled (http://marc.info/?l=linux-crypto-vger=138627061905651=2).

Re: [PATCH 1/3] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8

On Wed, Dec 04, 2013 at 02:57:43PM +0100, Oleg Nesterov wrote: > On 12/03, Frederic Weisbecker wrote: > > > > 2013/11/11 Oleg Nesterov : > > > On 11/11, Frederic Weisbecker wrote: > > >> > > >> On Sat, Nov 09, 2013 at 04:54:28PM +0100, Oleg Nesterov wrote: > > >> > > > >> > Up to you and Suravee,

Re: [PATCH v3 07/10] drivers: phy: usb3/pipe3: Adapt pipe3 driver to Generic PHY Framework

Hi, On Friday 06 December 2013 08:05 PM, Roger Quadros wrote: > Hi Kishon, > > On 11/25/2013 12:01 PM, Kishon Vijay Abraham I wrote: >> Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3 >> driver in drivers/usb/phy to drivers/phy and also renamed the file to >>

[PATCH v2] gpiolib: return -ENOENT if no GPIO mapping exists

Some devices drivers make use of optional GPIO parameters. For such drivers, it is important to discriminate between the case where no GPIO mapping has been defined for the function they are requesting, and the case where a mapping exists but an error occured while resolving it or when acquiring

Re: [PATCH v2] kexec: add sysctl to disable kexec

On Tue, Dec 10, 2013 at 09:35:40AM -0500, Vivek Goyal wrote: > On Mon, Dec 09, 2013 at 05:06:10PM -0800, Kees Cook wrote: > > On Mon, Dec 9, 2013 at 4:34 PM, H. Peter Anvin wrote: > > > On 12/09/2013 04:16 PM, Kees Cook wrote: > > >> For general-purpose (i.e. distro) kernel builds it makes sense

Re: [PATCH] sound: memalloc.h - fix wrong truncation of dma_addr_t

At Tue, 10 Dec 2013 14:20:28 +, Stefano Panella wrote: > > When running a 32bit kernel the hda_intel driver is still reporting > a 64bit dma_mask if the HW supports it. > > >From sound/pci/hda/hda_intel.c: > > /* allow 64bit DMA address if supported by H/W */ > if ((gcap &

Re: Will CPU 0 be forever prohibited from NO_HZ_FULL status?

On Wed, Dec 04, 2013 at 06:50:37PM -0800, Paul E. McKenney wrote: > On Thu, Dec 05, 2013 at 02:20:55AM +0100, Frederic Weisbecker wrote: > > On Wed, Dec 04, 2013 at 11:39:57AM -0800, Paul E. McKenney wrote: > > > Hello, Frederic, > > > > > > Just realized that I could further decrease RT latency

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