linux-kernel - Re: [PATCH v2 1/4] mm: Add optional close() to struct vm_special

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: <CAHk-=wiyxQMG7gK5d=_UEcHF2PV3EoCFrENEhRvJH9Qsk7cOeA@mail.gmail.com>
Date: Mon, 19 Aug 2024 18:11:24 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Nathan Chancellor <nathan@...nel.org>, Guo Ren <guoren@...nel.org>, Brian Cain <bcain@...cinc.com>, 
	Dinh Nguyen <dinguyen@...nel.org>, Yoshinori Sato <ysato@...rs.sourceforge.jp>, 
	Rich Felker <dalias@...c.org>, John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>, 
	Richard Weinberger <richard@....at>, Anton Ivanov <anton.ivanov@...bridgegreys.com>, 
	Johannes Berg <johannes@...solutions.net>, Michael Ellerman <mpe@...erman.id.au>, linux-mm@...ck.org, 
	linuxppc-dev@...ts.ozlabs.org, christophe.leroy@...roup.eu, jeffxu@...gle.com, 
	Liam.Howlett@...cle.com, linux-kernel@...r.kernel.org, npiggin@...il.com, 
	oliver.sang@...el.com, pedro.falcato@...il.com, linux-um@...ts.infradead.org, 
	linux-csky@...r.kernel.org, linux-hexagon <linux-hexagon@...r.kernel.org>, 
	Linux-sh list <linux-sh@...r.kernel.org>
Subject: Re: [PATCH v2 1/4] mm: Add optional close() to struct vm_special_mapping

On Mon, 19 Aug 2024 at 18:05, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> >
> > I forgot to actually attach that "this". Here it is. For real, this time.
>
> Thanks.  Do you think your one-liner remains desirable with this fix in
> place?

That patch actually removes the whole 'legacy_special_mapping_vmops'
that my one-liner then removed the '.close' field from, so no - my
one-liner just becomes a non-issue.

NOTE! That patch of mine *will* conflict with Michael's patch series,
since my patch to remove legacy_special_mapping_vmops was done on top
of my current -git tree. But it should be an obvious conflict, in that
it just means that the addition of .close never happens.

               Linus