linux-kernel - Re: [PATCH] RFC: change do_timer() to take xtime lock, and provide do_timer

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] [day] [month] [year] [list]

Date:	Fri, 21 Jan 2011 14:59:59 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Torben Hohn <torbenh@....de>
cc:	linux-kernel@...r.kernel.org, johnstul@...ibm.com,
	hch@...radead.org, tglx@...x.de
Subject: Re: [PATCH] RFC: change do_timer() to take xtime lock, and provide
 do_timer_locked()

On Fri, 21 Jan 2011, Torben Hohn wrote:

> in an effort to reduce occurrences of xtime_lock in the codebase,
> this commit makes do_timer take the xtime lock.
> 
> there are quite some occurences where arch code seems to protect
> other datastructures with this lock too.
> we provide do_timer_locked() for these occurences.
> 
> however, for this change to make sense, we should try to get rid
> of most calls to do_timer_locked()
> gonna try to address that in other arch specific commits.

Please see my other mail. We really don't want all that churn in one
large commit.

Thanks,

	tglx
--
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/