From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C588AC433EF for ; Mon, 16 May 2022 21:28:06 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id DAD3A6B0072; Mon, 16 May 2022 17:28:05 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D5C606B0073; Mon, 16 May 2022 17:28:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C25946B0074; Mon, 16 May 2022 17:28:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id B464E6B0072 for ; Mon, 16 May 2022 17:28:05 -0400 (EDT) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id 7B30F815A7 for ; Mon, 16 May 2022 21:28:05 +0000 (UTC) X-FDA: 79472894130.07.F27301B Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf16.hostedemail.com (Postfix) with ESMTP id F0012180059 for ; Mon, 16 May 2022 21:27:53 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id E4E68B81675; Mon, 16 May 2022 21:28:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7F128C385AA; Mon, 16 May 2022 21:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1652736481; bh=EM6ZQkiQKgpAaDYaA6WjPhnZvN0fVUJjX1XitUtMIs8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ZncUOfR5ydNppphNM7bCyHaeeVtoa/cDcINUcafTV2G5pjni+bwaDQQd96t7ZAIml DJqkX8XWxDIoclFzgJk6S7FBgdujsfRsJW/ADQ8+B+NoCfPLUx4HTrR3p67q0PWa4O sIF+9ZBSf3FfS7U9tYVzcJY4KBnC9vyPhGkO5++Q= Date: Mon, 16 May 2022 14:28:00 -0700 From: Andrew Morton To: "Jason A. Donenfeld" Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Theodore Ts'o Subject: Re: [PATCH] random: move randomize_page() into mm where it belongs Message-Id: <20220516142800.4730a41ec1498d5e3d7863c0@linux-foundation.org> In-Reply-To: <20220514120556.363559-1-Jason@zx2c4.com> References: <20220514120556.363559-1-Jason@zx2c4.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Stat-Signature: 9tiqwcjmm4npn51cc1ed6rzxpizrje5j X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: F0012180059 Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=ZncUOfR5; spf=pass (imf16.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-Rspam-User: X-HE-Tag: 1652736473-911729 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Sat, 14 May 2022 14:05:56 +0200 "Jason A. Donenfeld" wrote: > randomize_page is an mm function. It is documented like one. It contains > the history of one. It has the naming convention of one. It looks > just like another very similar function in mm, randomize_stack_top(). > And it has always been maintained and updated by mm people. There is no > need for it to be in random.c. In the "which shape does not look like > the other ones" test, pointing to randomize_page() is correct. > > So move randomize_page() into mm/util.c, right next to the similar > randomize_stack_top() function. > > This commit contains no actual code changes. hm, does it make sense? Probably randomize_page() (which used to be called randomize_range()) should have been called randomize_address(). Is it an MM function then? Not really - it's simply an application of the random number generator. So I think it's more a random thing than an MM thing. > --- a/mm/util.c > +++ b/mm/util.c > @@ -343,6 +343,38 @@ unsigned long randomize_stack_top(unsigned long stack_top) > #endif > } > > +/** > + * randomize_page - Generate a random, page aligned address The patch assumes that drivers/char/random.o is always built into vmlinux, which appears to be the case. If some space-conscious person goes and makes random.o build-time optional then they'll need to make the appropriate adjustments in util.c. I see no problems with this.