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: <574262b0-6dd1-4e0e-a2c0-0e22aa885c6e@sk.com>
Date: Thu, 22 May 2025 14:55:49 +0900
From: Honggyu Kim <honggyu.kim@...com>
To: SeongJae Park <sj@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>
Cc: kernel_team@...ynix.com, damon@...ts.linux.dev, kernel-team@...a.com,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 2/2] mm/damon/Kconfig: enable CONFIG_DAMON by default



On 5/21/2025 1:27 PM, SeongJae Park wrote:
> As of this writing, multiple major distros including Alma, Amazon,
> Android, CentOS, Debian, Fedora, and Oracle are build-enabling DAMON
> (set CONFIG_DAMON[1]).  Enabling it by default will save configuration
> setup time for the current and future DAMON users.
> 
> Build-enabling DAMON does not introduce a real risk since it makes no
> behavioral change by default.  It requires explicit user requests to do
> anything.  Only one potential risk is making the size of the kernel a
> little bit larger.  On a production-purpose configuration, it increases
> the resulting kernel package size by about 0.1 % of the final package
> file.  I believe that's too small to be a real problem in common setups.
> 
> Hence, the benefit of enabling CONFIG_DAMON outweighs the potential
> risk.  Set CONFIG_DAMON by default.

Agreed.

> [1] https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DAMON
> 
> Signed-off-by: SeongJae Park <sj@...nel.org>
> ---
>   mm/damon/Kconfig | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/mm/damon/Kconfig b/mm/damon/Kconfig
> index c93d0c56b963..551745df011b 100644
> --- a/mm/damon/Kconfig
> +++ b/mm/damon/Kconfig
> @@ -4,6 +4,7 @@ menu "Data Access Monitoring"
>   
>   config DAMON
>   	bool "DAMON: Data Access Monitoring Framework"
> +	default y
>   	help
>   	  This builds a framework that allows kernel subsystems to monitor
>   	  access frequency of each memory region. The information can be useful

     Acked-by: Honggyu Kim <honggyu.kim@...com>

Thanks,
Honggyu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ