Kernel

perf annotate segfaults when source code has goto label that looks like hex number
The script below demonstrate this. The problem is in hist_entry__parse_objdump_line(): if (*tmp) { /* * Parse hexa addresses followed by ':' */ line_ip = strtoull(tmp, &tmp2, 16); if (*tmp2 != ':' || tmp == tmp2) ... 22 Jul 2010 03:47

cfq-iosced: Implement IOPS mode and group_idle tunable V3
Vivek Goyal wrote: Hi, This is V3 of the group_idle and CFQ IOPS mode implementation patchset. Since V2 I have cleaned up the code a bit to clarify the confusion lingering around in what cases do we charge time slice and in what cases do we charge number of requests. What's the problem ----... 27 Jul 2010 05:10

dynamic debug: move ddebug_remove_module() down into free_module()
On Wednesday 21 July 2010 23:34:23 Andrew Morton wrote: On Wed, 14 Jul 2010 16:00:57 -0400 Jason Baron <jbaron(a)redhat.com> wrote: move the call to ddebug_remove_module() down into free_module(). In this way it should be called from all error paths. Currently, we are missing the remove if the mo... 22 Jul 2010 03:47

Possible Oprofile crash/race when stopping
Hi folks ! We've hit a strange crash internally, that we -think- we have tracked down to an oprofile bug. It's hard to hit, so I can't guarantee yet that we have fully smashed it but I'd like to share our findings in case you guys have a better idea. So the initial observation is a spinlock bad magic followed ... 2 Aug 2010 22:26

[2.6.34.1] OOPS in raid10 module.
hi, i'm testing an raid10 with ata-over-ethernet backend. there're 13 slave machines and each one exports 2 partitions via vbladed as /dev/etherd/e[1-13].[0-1]. there's also a master which assembles /dev/etherd/... into raid10. everything seems to work fine until first failure event. mdadm monitor sent to me ... 22 Jul 2010 02:43

kexec: increase max of kexec segments and use dynamic allocation
On 07/22/10 14:28, Eric W. Biederman wrote: Amerigo Wang<amwang(a)redhat.com> writes: Currently KEXEC_SEGMENT_MAX is only 16 which is too small for machine with many memory ranges. Increase this hard limit to 1024 which is reasonably large, and change ->segment from a static array to a dynamically allo... 4 Aug 2010 23:26

[PATCH 4/6] writeback: sync expired inodes first in background writeback
A background flush work may run for ever. So it's reasonable for it to mimic the kupdate behavior of syncing old/expired inodes first. The policy is - enqueue all newly expired inodes at each queue_io() time - retry with halfed expire interval until get some inodes to sync CC: Jan Kara <jack(a)suse.cz> Signed-o... 22 Jul 2010 02:43

[PATCH 2/6] writeback: the kupdate expire timestamp should be a moving target
Dynamicly compute the dirty expire timestamp at queue_io() time. Also remove writeback_control.older_than_this which is no longer used. writeback_control.older_than_this used to be determined at entrance to the kupdate writeback work. This _static_ timestamp may go stale if the kupdate work runs on and on. The fl... 22 Jul 2010 02:43

[PATCH 5/6] writeback: try more writeback as long as something was written
writeback_inodes_wb()/__writeback_inodes_sb() are not agressive in that they only populate b_io when necessary at entrance time. When the queued set of inodes are all synced, they just return, possibly with wbc.nr_to_write > 0. For kupdate and background writeback, there may be more eligible inodes sitting in b_... 22 Jul 2010 02:43

[PATCH 0/6] [RFC] writeback: try to write older pages first
Andrew, The basic way of avoiding pageout() is to make the flusher sync inodes in the right order. Oldest dirty inodes contains oldest pages. The smaller inode it is, the more correlation between inode dirty time and its pages' dirty time. So for small dirty inodes, syncing in the order of inode dirty time is abl... 22 Jul 2010 02:43