netdev - Re: [PATCH] Stochastic Fair Blue queue discipline

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: <20080408163252.GS16647@one.firstfloor.org>
Date:	Tue, 8 Apr 2008 18:32:52 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Juliusz Chroboczek <Juliusz.Chroboczek@....jussieu.fr>
Cc:	Andi Kleen <andi@...stfloor.org>, netdev@...r.kernel.org
Subject: Re: [PATCH] Stochastic Fair Blue queue discipline

On Tue, Apr 08, 2008 at 05:38:47PM +0200, Juliusz Chroboczek wrote:
> > I think we have multiple qdiscs now doing very similar such hashes.
> > Any chance this could be factored out into a common library function 
> > first?
> 
> I'll be glad to do so.  Where shall I put it?

See Patrick's suggestion.

> > But in any case it is likely better you only get the
> > get_random_bytes() entropy once and then use that to init some kind
> > of RNG (either a secure one if it's for security or some random fast
> > one if it's not) and then use that output for rehashing.
> 
> Could do, but in that case the RNG should be shared between sfq and
> sfb.  Shall I simply use net_random (which calls random32) ?

no net_random/srandom32 is per CPU and likely does the wrong thing for you.

There was a new RND being scheduled to be merged with perfmon,
either use that or add a simple own (I assume your needs are not great)

-Andi

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html