linux-kernel - Re: [git pull] scheduler changes for v2.6.26

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 19 Apr 2008 20:47:21 +0200
From:	"Guillaume Chazarain" <guichaz@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [git pull] scheduler changes for v2.6.26

On 4/19/08, Ingo Molnar <mingo@...e.hu> wrote:
>  Guillaume Chazarain (1):
>       sched: fix rq->clock overflows detection with CONFIG_NO_HZ

This one should have been dropped (per http://lkml.org/lkml/2008/1/25/413)
I don't like rq->clock relying on jiffies, and you already fixed the
original manifestation of the problem in:

commit 2997c8c4a0b179e8b834a7f30ba4323f2c60ccf4
Author: Ingo Molnar <mingo@...e.hu>
Date:   Fri Jan 11 13:35:54 2008 +0100

    block: fix blktrace timestamps

    David Dillow reported broken blktrace timestamps. The reason
    is cpu_clock() which is not a global time source.

    Fix bkltrace timestamps by using ktime_get() like the networking
    code does for packet timestamps. This also removes a whole lot
    of complexity from bkltrace.c and shrinks the code by 500 bytes:

       text    data     bss     dec     hex filename
       2888     124      44    3056     bf0 blktrace.o.before
       2390     116      44    2550     9f6 blktrace.o.after

    Signed-off-by: Ingo Molnar <mingo@...e.hu>
    Signed-off-by: Jens Axboe <jens.axboe@...cle.com>


-- 
Guillaume
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/