linux-kernel - Re: [PATCH] KEYS: Have the garbage collector set its timer for live expired keys

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: <20090916150556.GA23523@elte.hu>
Date:	Wed, 16 Sep 2009 17:05:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Howells <dhowells@...hat.com>
Cc:	torvalds@...l.org, jmorris@...ei.org, eparis@...hat.com,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KEYS: Have the garbage collector set its timer for
	live expired keys


* David Howells <dhowells@...hat.com> wrote:

> The key garbage collector sets a timer to start a new collection cycle at the
> point the earliest key to expire should be considered garbage.  However, it
> currently only does this if the key it is considering hasn't yet expired.
> 
> If the key being considering has expired, but hasn't yet reached the collection
> time then it is ignored, and won't be collected until some other key provokes a
> round of collection.
> 
> Make the garbage collector set the timer for the earliest key that hasn't yet
> passed its collection time, rather than the earliest key that hasn't yet
> expired.
> 
> Signed-off-by: David Howells <dhowells@...hat.com>

Is this in response to my bugreport? (If yes then the changelog is quite 
vague about the circumstances of the bug, its effects, which tools were 
used to find it, etc. etc.)

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