linux-kernel - Re: BUG: using smp_processor_id() in preemptible [00000000] code: icedove-bin/5449

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]

Message-ID: <4BFB9F0A.9040803@example.com>
Date:	Tue, 25 May 2010 11:57:30 +0200
From:	Piotr Hosowicz <piotr@...owicz.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>,
	Divyesh Shah <dpshah@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code:
 icedove-bin/5449

On 25.05.2010 11:43, Ingo Molnar wrote:

> This doesnt fix the whole issue. cpu_clock() is local, while the measurements
> done in the blk code are global ...
>
> While the warning is fixed this way, the far more serious issue is still
> there: time can go backwards if two points of time measurement are on
> different CPUs and can mess up the statistics with negative values, etc...

How serious is this? Can it damage my data? I ask because the machine is 
my private computer, not any test machine.

Regards,

Piotr Hosowicz

-- 
Babcia rox! :
alek:   przyszli do mnie jechowi dzisiaj, otworzyła babcia
pate_q: i co?
alek:   po 30 minutach rozmowy chcieli przejść na chrześcijaństwo
NP: Alice In Chains - All Secrets Known
NB: 2.6.34-20100524-1752
--
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/