linux-kernel - Re: Long delays and keystrokes required

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20081031114025.GB10383@corsac.net>
Date:	Fri, 31 Oct 2008 12:40:25 +0100
From:	Yves-Alexis Perez <corsac@...ian.org>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org
Subject: Re: Long delays and keystrokes required - related to disk
	encryption?

On Fri, Oct 31, 2008 at 08:57:05AM +0100, Pavel Machek wrote:
> On Fri 2008-10-31 01:04:25, Frans Pop wrote:
> > On Thursday 30 October 2008, Pavel Machek wrote:
> > > Try "nohz=off highres=off"...
> > 
> > Oh, I have no doubt that that could help. The point is though that I don't 
> > think I should have to use such parameters.
> > 
> > I think we've already established that disabling hires timers helps, so, 
> > unless this will provide some additional tracing info to the developers, 
> > I think I'll skip this suggestion.
> > 
> > 2.6 28-rc2 is a regression against 2.6.27 because hires is broken. I don't 
> > think I'll want to permanently add random boot parameters to work around 
> > that regression.
> 
> Well, you could probably narrow it down to "nohz=off", because I
> believe it is probably nohz and not highres that makes problems.
> 
> Anyway, if this does not get fixed soon, you should cc rjw so this
> gets on the regression list.

It already is on the regression list, see:

http://bugzilla.kernel.org/show_bug.cgi?id=11826
http://bugzilla.kernel.org/show_bug.cgi?id=11893
> 
> You can probably debug this with git bisect if no other ideas
> surface...

Bisect has already been done, the offending commit is:

commit dc4304f7deee29fcdf6a2b62f7146ea7f505fd42
Author: Arjan van de Ven <arjan@...ux.intel.com>
Date:   Mon Oct 13 10:32:15 2008 -0400
    rangetimers: fix the bug reported by Ingo for real


And workarounding it with a return; early in the function worked.
But that's not really a solution.

Cheers,
-- 
Yves-Alexis
--
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/