Hi Steve,
Attached is the modified test program. Here is the sample output:
localhost ~ # ./ftrace-test-epoll-kafai
<...>-1857 [000] ...1 720.174295: tracing_mark_write: some data
1857: waitting for more data..
1858: written more data
Thanks,
--Martin
On Tue, Jun 10, 2014
Paul E. McKenney, Eric Biederman, David Miller (and/or anyone else interested):
It was brought to my attention that netns creation/execution might
have suffered scalability/performance regression after v3.8.
I would like you, or anyone interested, to review these charts/data
and check if there
On Wed, 2014-06-11 at 07:24 +0200, Mike Galbraith wrote:
> (CCs network wizard hangout)
>
> On Wed, 2014-06-11 at 00:12 -0400, Rich Felker wrote:
> > While looking to add support for the recvmmsg and sendmmsg syscalls in
> > musl libc, I ran into some disturbing findings on the kernel side. In
>
On Tue, Jun 10, 2014 at 05:38:49PM -0400, Jeff Layton wrote:
> From: Jeff Layton
>
> Lately, when I do a make with C=1, I get *tons* of these warnings:
>
> include/linux/err.h:35:16: warning: dereference of noderef expression
> include/linux/err.h:30:23: warning: dereference of noderef
On Tue, Jun 10, 2014 at 08:26:55AM +0200, Daniel Vetter wrote:
> On Sun, Jun 08, 2014 at 10:30:15PM +0100, Sitsofe Wheeler wrote:
> > With a tree that is close to 3.15 final I'm regularly seeing the
> > following on my EeePC 900 when starting ioquake3:
> >
> > [drm:intel_pipe_config_compare]
On Tue, Jun 10, 2014 at 10:48:35PM +0200, Rickard Strandqvist wrote:
> Hi
>
> True!
> Sorry :-(
>
> But then one would either operate strcpy outright.
>
> Or use strlcpy then the code would be:
>
> /* strlcpy() handles not include \0 */
> len = strlcpy(busid, buf + 4, BUSID_SIZE);
>
On Tue, 2014-06-10 at 23:32 -0400, Peter Hurley wrote:
> While rcu list traversal over the vmap_area_list is safe, this may
> arrive at different results than the spinlocked version. The rcu list
> traversal version will not be a 'snapshot' of a single, valid instant
> of the entire
Currently CLK_FOUT_EPLL was set as one of the parents of AUDSS mux.
As per the user manual, it should be CLK_MAU_EPLL.
The problem surfaced when the bootloader in Peach-pit board set
the EPLL clock as the parent of AUDSS mux. While booting the kernel,
we used to get a system hang during late boot
Peach-pi board has MAX98090 audio codec connected on HSI2C-7 bus.
Signed-off-by: Tushar Behera
---
arch/arm/boot/dts/exynos5800-peach-pi.dts | 31 +
1 file changed, 31 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5800-peach-pi.dts
With next-20140610, Peach-pit/Peach-pi board hangs during boot if we
run 'sound init' during u-boot. The issue is fixed in following patches.
While at it, also enable audio support for Peach-pi board.
How to test audio on Peach-pi:
* On top of exynos_defconfig, enable SND_SOC_SNOW and PL330_DMA
When the output clock of AUDSS mux is disabled, we are getting kernel
oops while doing a clk_get() on other clocks provided by AUDSS. Though
user manual doesn't specify this dependency, we came across this issue
while disabling the parent of AUDSS mux clocks.
Keeping the parents of AUDSS mux
Hi Linus,
Can you please pull the changes from the tree below. Lots of changes
all over the place in XFS, the main addition is a new on-disk btree
for tracking free inodes and the associated optimised allocator
rework to make use of it. Most of the rest of the changes are
cleanups or reworking of
(CCs network wizard hangout)
On Wed, 2014-06-11 at 00:12 -0400, Rich Felker wrote:
> While looking to add support for the recvmmsg and sendmmsg syscalls in
> musl libc, I ran into some disturbing findings on the kernel side. In
> the struct mmsghdr, the field where the result for each message is
Hi all,
The powerpc allyesconfig is again broken more than usual.
Changes since 20140610:
Dropped tree: drm-intel-fixes (build problems)
The drm-intel-fixes still had its build failure so I dropped it at the
maintainers request.
The pci tree gained a build failure so I used the version from
[adding developers of the two syscalls to CC; maybe they have some insights.]
On Wed, Jun 11, 2014 at 6:12 AM, Rich Felker wrote:
> While looking to add support for the recvmmsg and sendmmsg syscalls in
> musl libc, I ran into some disturbing findings on the kernel side. In
> the struct mmsghdr,
Replaced 'printk' with 'netdev_' function
Signed-off-by: A Raghavendra Rao
---
drivers/staging/rtl8192e/dot11d.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8192e/dot11d.c
b/drivers/staging/rtl8192e/dot11d.c
index 53da610..bfcc935 100644
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early microcode updating.
Also make it to take boot_params pointer for different usage.
Signed-off-by: Yinghai Lu
---
devm_request_and_ioremap() was obsoleted by the commit 7509657
("lib: devres: Introduce devm_ioremap_resource()") and has been
deprecated for a long time. So, let's remove this function.
In addition, all usages of devm_request_and_ioremap() are also
removed.
Signed-off-by: Jingoo Han
---
On Wed, Jun 11, 2014 at 10:11:55AM +0530, A Raghavendra Rao wrote:
> Replaced 'printk' with 'netdev_' function
>
> Signed-off-by: A Raghavendra Rao
> ---
> drivers/staging/rtl8192e/dot11d.c |9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git
On Tue, Jun 10, 2014 at 11:35:07PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> > > Let's take USB peripheral as an example, there is a device for
> > > udc, and a device driver for usb gadget driver, at default, we want
> > > the device to be
Hi,
On Tue, Jun 10, 2014, Kamal Mostafa wrote:
> 3.13.11.3 -stable review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Johan Hedberg
>
> commit 09da1f3463eb81d59685df723b1c5950b7570340 upstream.
>
> When we're performing reauthentication (in
Hi Doug,
On Tue, Jun 10, 2014 at 9:19 PM, Nicolas Pitre wrote:
> On Tue, 10 Jun 2014, Doug Anderson wrote:
>
>> My S-state knowledge is not strong, but I believe that Lorenzo's
>> questions matter if we're using S2 for CPUidle (where we actually turn
>> off power and hot unplug CPUs) but not
Replaced 'printk' with 'netdev_' function
Signed-off-by: A Raghavendra Rao
---
drivers/staging/rtl8192e/dot11d.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8192e/dot11d.c
b/drivers/staging/rtl8192e/dot11d.c
index 53da610..ef9da86 100644
On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> On Wed, Jun 11, 2014 at 10:14:40AM +0800, Peter Chen wrote:
> > Hi Greg,
> >
> > Currently, we can't disable auto probe function during booting
> > if both device and device driver register code are built in due
> > to .drivers_autoprobe
On Wed, Jun 11, 2014 at 12:23:57AM -0400, Pranith Kumar wrote:
> Hi Paul,
>
> On Wed, Jun 11, 2014 at 12:12 AM, Paul E. McKenney
> wrote:
> >> if (rnp->gpnum != rnp->completed ||
> >> - ACCESS_ONCE(rnp->gpnum) != ACCESS_ONCE(rnp->completed)) {
> >> +
Hi,
On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> > Let's take USB peripheral as an example, there is a device for
> > udc, and a device driver for usb gadget driver, at default, we want
> > the device to be bound to driver automatically, this is what
> > we have done now. But if
adds the device managed APIs so that no need worry about
freeing the resources.
Signed-off-by: Varka Bhadram
---
drivers/net/ieee802154/mrf24j40.c | 33 +
1 file changed, 13 insertions(+), 20 deletions(-)
diff --git a/drivers/net/ieee802154/mrf24j40.c
> So have you actually instrumented the kernel to demonstrate that in
> fact we have super deep stack call paths where the 128 bytes worth of
> stack actually matters?
I haven't got a specific call chain where 128 bytes pushes it
over a limit. But kernel stack usage is a perennial problem.
Gday,
I'm seeking some guidance on how to best (or if) to implement a feature.
Please CC me on any reply, I am not subscribed to this list.
The feature is, "an application would like to know how many files another
process has open".
>From user space, the cheapest way would be to use the
On Tue, Jun 10, 2014 at 11:32:19PM -0400, Peter Hurley wrote:
> PF: none (google.com: pe...@hurleysoftware.com does not designate permitted
> sender hosts) client-ip=216.70.64.70;
> Received: from h96-61-95-138.cntcnh.dsl.dynamic.tds.net ([96.61.95.138]:55986
> helo=[192.168.1.139])
> by
Hi Paul,
On Wed, Jun 11, 2014 at 12:12 AM, Paul E. McKenney
wrote:
>> if (rnp->gpnum != rnp->completed ||
>> - ACCESS_ONCE(rnp->gpnum) != ACCESS_ONCE(rnp->completed)) {
>> + ACCESS_ONCE(rnp_root->gpnum) != ACCESS_ONCE(rnp_root->completed)) {
>
> At this point in the code,
On Wed, Jun 11, 2014 at 09:25:47AM +0530, A Raghavendra Rao wrote:
> From: Raghavendra
>
> Fixed coding style issues
Which specific coding style issue? Be exact please.
And don't try to fix more than one type of coding style issue at a
time...
>
> Signed-off-by: A Raghavendra Rao
This
While looking to add support for the recvmmsg and sendmmsg syscalls in
musl libc, I ran into some disturbing findings on the kernel side. In
the struct mmsghdr, the field where the result for each message is
stored has type int, which is inconsistent with the return type
ssize_t of
some times i get confused by one patch should do only one thing
policy, for example this patch removes
many other things along _rtw_read_mem().
But you are also right it's much easier to review when they are all
folded together.
I'm glad, i did it right this time. :)
regards,
navin patidar
On
On Tue, Jun 10, 2014 at 11:20:19PM -0400, Pranith Kumar wrote:
> The comment above the code says that we are checking both the current node and
> the parent node to see if a grace period is in progress. Change the code
> accordingly.
Almost... Please see below.
On Tue, 2014-06-10 at 13:50 -0400, Benjamin LaHaise wrote:
> On Tue, Jun 10, 2014 at 05:47:28AM +0200, Mike Galbraith wrote:
> > On Mon, 2014-06-09 at 10:08 +0800, Lai Jiangshan wrote:
> > > Hi, rt-people
> > >
> > > I don't think it is the correct direction.
> > > Softirq (including
On Wed, Jun 11, 2014 at 10:14:40AM +0800, Peter Chen wrote:
> Hi Greg,
>
> Currently, we can't disable auto probe function during booting
> if both device and device driver register code are built in due
> to .drivers_autoprobe is a private value for bus core and this
> value can only be changed
Signed-off-by: Zhouyi Zhou
---
arch/x86/kernel/cpu/perf_event_amd_uncore.c | 32 +++
1 file changed, 18 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kernel/cpu/perf_event_amd_uncore.c
b/arch/x86/kernel/cpu/perf_event_amd_uncore.c
index 3bbdf4c..f60a50e 100644
According to Peter's advice, put the failure handling to a goto chain.
Compiled in x86_64, could you check if there is anything that I missed.
Signed-off-by: Zhouyi Zhou
---
arch/x86/kernel/cpu/perf_event_amd_uncore.c | 111 ---
1 file changed, 84 insertions(+), 27
From: Raghavendra
Fixed coding style issues
Signed-off-by: A Raghavendra Rao
---
drivers/staging/rtl8192e/dot11d.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8192e/dot11d.c
b/drivers/staging/rtl8192e/dot11d.c
index 53da610..ef9da86
> Actually, it's **fine**. That's because RNDADDENTROPY adds the
> entropy to the input pool, which is has the limit flag set. So we
> will never pull more entropy than the pool is credited as having.
> This means that race can't happen. It ***is*** safe.
>
> 1) Assume the entropy count
>From 14485894add32aedacb3e486ebb2cc2b73861abf Mon Sep 17 00:00:00 2001
From: Fu zhonghui
Date: Wed, 11 Jun 2014 11:06:55 +0800
Subject: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and
connecting
Watchdog in brcmfmac driver may make WiFi chip enter sleep mode
before
Hi Greg,
Currently, we can't disable auto probe function during booting
if both device and device driver register code are built in due
to .drivers_autoprobe is a private value for bus core and this
value can only be changed by sys entry.
It causes we can't implement feature that the user can
On 06/11/2014 10:41 AM, Minchan Kim wrote:
> On Mon, Jun 09, 2014 at 11:26:19AM +0200, Vlastimil Babka wrote:
>> From: David Rientjes
>>
>> The page allocator has gfp flags (like __GFP_WAIT) and alloc flags (like
>> ALLOC_CPUSET) that have separate semantics.
>>
>> The function
On 06/10/2014 10:19 PM, Joonsoo Kim wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he didn't answer it.
We previously extracted a portion of the entropy pool in
mix_pool_bytes() and hashed it in to avoid racing CPU's from returning
duplicate random values. Now that we are using a spinlock to prevent
this from happening, this is no longer necessary. So remove it, to
simplify the code a bit.
Instead of using lockless techniques introduced in commit
902c098a3663, use spin_trylock to try to grab entropy pool's lock. If
we can't get the lock, then just try again on the next interrupt.
Based on discussions with George Spelvin.
Signed-off-by: Theodore Ts'o
Cc: George Spelvin
---
In xfer_secondary_pull(), check to make sure we need to pull from the
secondary pool before checking and potentially updating the
last_pulled time.
Signed-off-by: Theodore Ts'o
Cc: George Spelvin
---
drivers/char/random.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff
After going through a very long thread, and trying to work out things in
words, I was frustrated enough that I decided a good way to improve the
conversation was to do it in code instead of words.
I don't think any of this should be controversial...
On 06/09/2014 05:26 PM, Vlastimil Babka wrote:
> Unlike the migration scanner, the free scanner remembers the beginning of the
> last scanned pageblock in cc->free_pfn. It might be therefore rescanning pages
> uselessly when called several times during single compaction. This might have
> been
Extracts the common check/assign logic, and separates the two mode
setting paths to make things more readable with fewer #ifdefs within
function bodies.
Signed-off-by: Kees Cook
---
kernel/seccomp.c | 124 +-
1 file changed, 85 insertions(+),
Wires up the new seccomp syscall.
Signed-off-by: Kees Cook
---
arch/mips/include/uapi/asm/unistd.h | 15 +--
arch/mips/kernel/scall32-o32.S |1 +
arch/mips/kernel/scall64-64.S |1 +
arch/mips/kernel/scall64-n32.S |1 +
arch/mips/kernel/scall64-o32.S
Normally, task_struct.seccomp.filter is only ever read or modified by
the task that owns it (current). This property aids in fast access
during system call filtering as read access is lockless.
Updating the pointer from another task, however, opens up race
conditions. To allow cross-thread filter
Applying restrictive seccomp filter programs to large or diverse
codebases often requires handling threads which may be started early in
the process lifetime (e.g., by code that is linked in). While it is
possible to apply permissive programs prior to process start up, it is
difficult to further
Since seccomp transitions between threads requires updates to the
no_new_privs flag to be atomic, changes must be atomic. This moves the nnp
flag into the seccomp field as a separate unsigned long for atomic access.
Signed-off-by: Kees Cook
Acked-by: Andy Lutomirski
---
fs/exec.c
In preparation for having other callers of the seccomp mode setting
logic, split the prctl entry point away from the core logic that performs
seccomp mode setting.
Signed-off-by: Kees Cook
---
kernel/seccomp.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git
In preparation for adding seccomp locking, move filter creation away
from where it is checked and applied. This will allow for locking where
no memory allocation is happening. The validation, filter attachment,
and seccomp mode setting can all happen under the future locks.
Signed-off-by: Kees
[re-send with smaller CC list]
This adds the ability for threads to request seccomp filter
synchronization across their thread group (at filter attach time).
For example, for Chrome to make sure graphic driver threads are fully
confined after seccomp filters have been attached.
To support this,
This adds the new "seccomp" syscall with both an "operation" and "flags"
parameter for future expansion. The third argument is a pointer value,
used with the SECCOMP_SET_MODE_FILTER operation. Currently, flags must
be 0. This is functionally equivalent to prctl(PR_SET_SECCOMP, ...).
Wires up the new seccomp syscall.
Signed-off-by: Kees Cook
---
arch/arm/include/uapi/asm/unistd.h |1 +
arch/arm/kernel/calls.S|1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/include/uapi/asm/unistd.h
b/arch/arm/include/uapi/asm/unistd.h
index
On Tue, Jun 10, 2014 at 11:08:15PM -0400, Mimi Zohar wrote:
> On Wed, 2014-06-11 at 03:22 +0100, Matthew Garrett wrote:
> > Providing a userspace mechanism for selectively dropping keys from the
> > kernel seems like a good thing?
>
> No, patch "KEYS: verify a certificate is signed by a
On Tue, 2014-06-10 at 16:33 -0700, Andrew Morton wrote:
> > break;
> >
> > if (nr_file > nr_anon) {
> > - unsigned long scan_target =
> targets[LRU_INACTIVE_ANON] +
> >
> -
The comment above the code says that we are checking both the current node and
the parent node to see if a grace period is in progress. Change the code
accordingly.
Signed-off-by: Pranith Kumar
---
kernel/rcu/tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, 2014-06-11 at 03:22 +0100, Matthew Garrett wrote:
> On Tue, Jun 10, 2014 at 09:24:53PM -0400, Mimi Zohar wrote:
> > On Tue, 2014-06-10 at 22:40 +0100, Matthew Garrett wrote:
> > > The hole is that the system trusts keys that you don't trust. The
> > > appropriate thing to do is to
On Wed, 2014-06-11 at 09:46 +0800, Zhouyi Zhou wrote:
> Thanks for reviewing, I will work on a new version
If you do, please remove the "out of memory" messages.
These messages are redundant to a generic OOM and
stack dump from the memory subsystem.
Less code is also makes it less likely to
Quoting Mimi Zohar (zo...@linux.vnet.ibm.com):
> On Tue, 2014-06-10 at 13:23 -0700, Greg KH wrote:
> > On Tue, Jun 10, 2014 at 03:20:15PM +1000, James Morris wrote:
> > > On Thu, 5 Jun 2014, Greg KH wrote:
> > >
> > > > Hi all,
> > > >
> > > > James has had to step back from doing kernel work
On Mon, Jun 09, 2014 at 11:26:20AM +0200, Vlastimil Babka wrote:
> From: David Rientjes
>
> struct compact_control currently converts the gfp mask to a migratetype, but
> we
> need the entire gfp mask in a follow-up patch.
>
> Pass the entire gfp mask as part of struct compact_control.
>
>
On 06/09/2014 05:26 PM, Vlastimil Babka wrote:
> isolate_freepages_block() rechecks if the pageblock is suitable to be a target
> for migration after it has taken the zone->lock. However, the check has been
> optimized to occur only once per pageblock, and compact_checklock_irqsave()
> might be
On Mon, Jun 09, 2014 at 11:26:19AM +0200, Vlastimil Babka wrote:
> From: David Rientjes
>
> The page allocator has gfp flags (like __GFP_WAIT) and alloc flags (like
> ALLOC_CPUSET) that have separate semantics.
>
> The function allocflags_to_migratetype() actually takes gfp flags, not alloc
>
On 06/10/2014 11:12 AM, Jens Axboe wrote:
> On 2014-06-09 20:50, Junxiao Bi wrote:
>> On 06/10/2014 10:41 AM, Jens Axboe wrote:
>>> On 2014-06-09 20:31, Junxiao Bi wrote:
commit 7b5a3522 (loop: Limit the number of requests in the bio list)
limit
the request number in loop queue to
On Tue, Jun 10, 2014 at 12:16:22PM +0200, Peter Zijlstra wrote:
> What other target would you optimize for? The purpose here is to build
> an energy aware scheduler, one that schedules tasks so that the total
> amount of energy, for the given amount of work, is minimal.
>
> So we can't measure in
Consider the scenario:
For a TCP-style socket, while processing the COOKIE_ECHO chunk in
sctp_sf_do_5_1D_ce(), after it has passed a series of sanity check,
a new association would be created in sctp_unpack_cookie(), but afterwards,
some processing maybe failed, and sctp_association_free() will be
On Tue, Jun 10, 2014 at 2:51 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After relatively recent changes in the ACPI-based PCI hotplug
> (ACPIPHP) code, the acpiphp_check_host_bridge() executed for PCI
> host bridges via acpi_pci_root_scan_dependent() doesn't do anything
> useful,
/include/asm/pci.h defines PCI_DISABLE_MWI and there are
> two version of those functions depending on the setting of that symbol.
>
> I have used the pci tree from next-20140610 for today.
Thanks. This is my fault, not Ryan's. I made more similar changes,
but didn't notice the #ifdefs around t
On Tue, Jun 10, 2014 at 09:24:53PM -0400, Mimi Zohar wrote:
> On Tue, 2014-06-10 at 22:40 +0100, Matthew Garrett wrote:
> > The hole is that the system trusts keys that you don't trust. The
> > appropriate thing to do is to remove that trust from the entire system,
> > not just one layer of the
On Tue, Jun 10, 2014 at 08:10:03PM -0400, George Spelvin wrote:
>
> But even I get annoyed when I have a 1-line comment typo fix and wonder
> if it really deserves its own commit or if I can just include it with
> the other changes I'm making to that file.
Unless you're actually modifying that
On Tue, 10 Jun 2014 15:10:01 -0700 (PDT)
David Rientjes wrote:
> On Mon, 9 Jun 2014, Luiz Capitulino wrote:
>
> > > > > > diff --git a/arch/x86/include/asm/numa.h
> > > > > > b/arch/x86/include/asm/numa.h
> > > > > > index 4064aca..01b493e 100644
> > > > > > --- a/arch/x86/include/asm/numa.h
>
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he didn't answer it.
https://lkml.org/lkml/2014/4/10/416
Although I'm not sure that
On Tue, Jun 10, 2014 at 12:52:06PM +0100, Dietmar Eggemann wrote:
Hi Dietmar,
> Not in this sense but there is no functionality in the scheduler right
> now to check constantly if an sd flag has been set/unset via sysctl.
Sorry, I still don't understand. There are many "if (sd->flags & SD_XXX)"
On Mon, Jun 09, 2014 at 11:26:17AM +0200, Vlastimil Babka wrote:
> Unlike the migration scanner, the free scanner remembers the beginning of the
> last scanned pageblock in cc->free_pfn. It might be therefore rescanning pages
> uselessly when called several times during single compaction. This
On Tue, 2014-06-10 at 16:33 -0700, Andrew Morton wrote:
> On Mon, 9 Jun 2014 21:27:16 +0800 Chen Yucong wrote:
>
> > Via https://lkml.org/lkml/2013/4/10/334 , we can find that recording the
> > original scan targets introduces extra 40 bytes on the stack. This patch
> > is able to avoid this
On Tue, Jun 10, 2014 at 08:10:03PM -0400, George Spelvin wrote:
> What I wanted to do was eliminate that huge tmp buffer from
> _xfer_secondary_pool. There's no good reason why it needs to be there.
> and several reasons for getting rid of it.
So have you actually instrumented the kernel to
On Tue, Jun 10, 2014 at 1:05 PM, Wim Van Sebroeck wrote:
> Hi Linus,
>
> Please pull from 'master' branch of
> git://www.linux-watchdog.org/linux-watchdog.git
gmail has decided that you are a spammer, and the only reason I saw
this email was that BenH had the same fate and emailed me
bol.
I have used the pci tree from next-20140610 for today.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
signature.asc
Description: PGP signature
From: "Steven Rostedt (Red Hat)"
The per_cpu buffers are created one per possible CPU. But these do
not mean that those CPUs are online, nor do they even exist.
With the addition of the ring buffer polling, it assumes that the
caller polls on an existing buffer. But this is not the case if
the
From: "Steven Rostedt (Red Hat)"
The freeing of an instance, if max data is configured, there will be
per cpu data structures created. But these are not freed when the instance
is deleted, which causes a memory leak.
A new helper function is added that frees the individual buffers within a
From: Namhyung Kim
The recent addition of saved_cmdlines_size file had some remaining
(minor - mostly coding style) issues. Fix them by passing pointer
name to sizeof() and using scnprintf().
Link:
http://lkml.kernel.org/p/1402384295-23680-1-git-send-email-namhy...@kernel.org
Cc: Namhyung
From: "Steven Rostedt (Red Hat)"
The check that tests if ftrace_trace_arrays is empty in
top_trace_array(), uses the .prev pointer:
if (list_empty(ftrace_trace_arrays.prev))
instead of testing the variable itself:
if (list_empty(_trace_arrays))
Although it is technically correct, it is
Thanks to Namhyung Kim who pointed out some slight things with the code
that went to Linus already, I have some early cleanups.
There's also a bug that needs to be fixed in the ring buffer waiter
logic.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1:
On Mon, Jun 09, 2014 at 11:26:16AM +0200, Vlastimil Babka wrote:
> Compaction scanners try to lock zone locks as late as possible by checking
> many page or pageblock properties opportunistically without lock and skipping
> them if not unsuitable. For pages that pass the initial checks, some
>
Thanks for reviewing, I will work on a new version
On Wed, Jun 11, 2014 at 7:28 AM, Thomas Gleixner wrote:
> On Tue, 10 Jun 2014, H. Peter Anvin wrote:
>
>> On 06/10/2014 12:35 AM, Zhouyi Zhou wrote:
>> > Fixing some memory allocation failure handling in x86 UV
>> >
>> > Signed-off-by: Zhouyi
On Wed, 2014-06-11 at 02:23 +0200, Rafael J. Wysocki wrote:
> On Tuesday, June 10, 2014 02:26:45 PM Joe Perches wrote:
> > c89 is 25 years ago now.
> Apparently, I'm old.
nah, just older than yesterday.
No doubt better too.
> > > Either way, in my opinion it's better to put the parens into the
On Tue, 2014-06-10 at 13:23 -0700, Greg KH wrote:
> On Tue, Jun 10, 2014 at 03:20:15PM +1000, James Morris wrote:
> > On Thu, 5 Jun 2014, Greg KH wrote:
> >
> > > Hi all,
> > >
> > > James has had to step back from doing kernel work for a few weeks, so
> > > I've offered to step up and handle
On Mon, Jun 09, 2014 at 11:26:15AM +0200, Vlastimil Babka wrote:
> Compaction scanners regularly check for lock contention and need_resched()
> through the compact_checklock_irqsave() function. However, if there is no
> contention, the lock can be held and IRQ disabled for potentially long time.
>
(2014/06/10 22:53), Namhyung Kim wrote:
> Hi Masami,
>
> 2014-06-10 (화), 10:50 +, Masami Hiramatsu:
>> Introduce FTRACE_OPS_FL_IPMODIFY to avoid conflict among
>> ftrace users who may modify regs->ip to change the execution
>> path. This also adds the flag to kprobe_ftrace_ops, since
>>
On 06/10/2014 08:59 PM, Guenter Roeck wrote:
> Commit bf5db2f (microblaze: Use generic device.h) removes the
> microblaze specific pdev_archdata and dma_mask.
>
> At the same time, commit 591c1ee (of: configure the platform
> device dma parameters) initializes the just removed field.
> This
On Tue, 2014-06-10 at 22:40 +0100, Matthew Garrett wrote:
> On Wed, Jun 11, 2014 at 12:34:28AM +0300, Dmitry Kasatkin wrote:
>
> > My statement is still valid. It is a hole...
> >
> > To prevent the hole it should be explained that one might follow
> > certain instructions
> > to take ownership
Hm. Sorry, I thought I'd picked that one up. I'll send it in a couple of
days.
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, Jun 09, 2014 at 12:30:34PM +0900, J. R. Okajima wrote:
>
> Linus Torvalds:
> > So I ended up doing an rc8 because I was a bit worried about some
> > last-minute dcache fixes, but it turns out that nobody seemed to even
> > notice those. We did have other issues during the week, though, so
On Mon, Jun 09, 2014 at 11:26:14AM +0200, Vlastimil Babka wrote:
> Async compaction aborts when it detects zone lock contention or need_resched()
> is true. David Rientjes has reported that in practice, most direct async
> compactions for THP allocation abort due to need_resched(). This means that
1 - 100 of 1720 matches
Mail list logo
