| 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
| ||
|
Message-Id: <20260206073942.e37ce92b81f0a0c51a1f5b82@linux-foundation.org>
Date: Fri, 6 Feb 2026 07:39:42 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: <xu.xin16@....com.cn>
Cc: <david@...nel.org>, <chengming.zhou@...ux.dev>, <hughd@...gle.com>,
<wang.yaxin@....com.cn>, <yang.yang29@....com.cn>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: ksm: initialize rmap values directly and make them const
On Fri, 6 Feb 2026 16:38:50 +0800 (CST) <xu.xin16@....com.cn> wrote:
> > >
> > > Fixes: 06fbd555dea8 ("ksm: optimize rmap_walk_ksm by passing a suitable addressrange")
> > > Signed-off-by: xu xin <xu.xin16@....com.cn>
> >
> > The patch does not seem to be upstream / in mm-stable yet.
> >
> > Can you resend the original patch with these changes included and the
> > reproducer referenced in the updated patch description?
>
> Sure, I thought the original patch was merged in linux-next.
I've recently moved the original series into mm.git's mm-new branch, which
isn't included in linux-next. Because it appeared that the v2 series
wouldn't be available in time for the next merge window.
It is a wonderful performance improvement, but I think it's best that
we revisit the series for the next -rc cycle. So can you please
integrate this new change into "ksm: optimize rmap_walk_ksm by passing
a suitable addressrange", rework the changelogs to reflect the
discussion thus far and resend the "KSM: Optimizations for
rmap_walk_ksm" series?
Powered by blists - more mailing lists