linux-kernel - Re: [PATCH 11/13] Core Resource Allocation

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]

Message-ID: <ada4psxn72o.fsf@cisco.com>
Date:	Fri, 17 Nov 2006 12:37:03 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Steve Wise <swise@...ngridcomputing.com>
Cc:	openib-general@...nib.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH  11/13] Core Resource Allocation

 > I think we can use random32() or get_random_bytes().  I need to
 > re-review how this algorithm works.  Its randomizing the stag IDs so
 > they are not predictable.

I assume based on the algorithm you have now that they don't need to
be cryptographically unpredictable.  So random32() would probably be
the best thing to do (get_random_bytes() should be used sparingly,
since it depletes the kernel entropy pool).

 - R.
-
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/