From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-hyperv@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
linux-arch@vger.kernel.org, linux-s390@vger.kernel.org,
Wei Liu <wei.liu@kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Laura Abbott <labbott@redhat.com>,
Nitin Gupta <ngupta@vflare.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
linaro-mm-sig@lists.linaro.org, bpf@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Christophe Leroy <christophe.leroy@c-s.fr>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, Minchan Kim <minchan@kernel.org>,
iommu@lists.linux-foundation.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: decruft the vmalloc API
Date: Wed, 8 Apr 2020 17:03:24 +0100 [thread overview]
Message-ID: <20200408160324.GS25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200408115926.1467567-1-hch@lst.de>
On Wed, Apr 08, 2020 at 01:58:58PM +0200, Christoph Hellwig wrote:
> Hi all,
>
> Peter noticed that with some dumb luck you can toast the kernel address
> space with exported vmalloc symbols.
>
> I used this as an opportunity to decruft the vmalloc.c API and make it
> much more systematic. This also removes any chance to create vmalloc
> mappings outside the designated areas or using executable permissions
> from modules. Besides that it removes more than 300 lines of code.
I haven't read all your patches yet.
Have you tested it on 32-bit ARM, where the module area is located
_below_ PAGE_OFFSET and outside of the vmalloc area?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-08 16:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200408115926.1467567-1-hch@lst.de>
[not found] ` <20200408115926.1467567-27-hch@lst.de>
2020-04-08 12:18 ` [PATCH 26/28] arm64: use __vmalloc_node in arch_alloc_vmap_stack Mark Rutland
[not found] ` <20200408115926.1467567-18-hch@lst.de>
2020-04-08 12:21 ` [PATCH 17/28] mm: remove the prot argument from vm_map_ram Peter Zijlstra
2020-04-09 0:39 ` Gao Xiang
2020-04-08 12:25 ` decruft the vmalloc API Peter Zijlstra
[not found] ` <20200408115926.1467567-20-hch@lst.de>
2020-04-08 12:25 ` [PATCH 19/28] gpu/drm: remove the powerpc hack in drm_legacy_sg_alloc Daniel Vetter
2020-04-09 8:54 ` Benjamin Herrenschmidt
2020-04-09 9:41 ` Daniel Vetter
2020-04-09 14:19 ` Alex Deucher
2020-04-09 14:57 ` Daniel Vetter
2020-04-09 22:56 ` Benjamin Herrenschmidt
2020-04-10 8:11 ` Daniel Vetter
2020-04-09 11:46 ` Gerhard Pircher
[not found] ` <20200408115926.1467567-19-hch@lst.de>
2020-04-08 12:38 ` [PATCH 18/28] mm: enforce that vmap can't map pages executable Mark Rutland
2020-04-08 12:48 ` [PATCH 02/28] staging: android: ion: use vmap instead of vm_map_ram Hillf Danton
[not found] ` <20200408115926.1467567-3-hch@lst.de>
2020-04-08 13:27 ` Greg KH
[not found] ` <20200408115926.1467567-28-hch@lst.de>
2020-04-08 13:33 ` [PATCH 27/28] s390: use __vmalloc_node in alloc_vm_stack Christian Borntraeger
[not found] ` <20200408115926.1467567-29-hch@lst.de>
2020-04-08 13:44 ` [PATCH 28/28] s390: use __vmalloc_node in stack_alloc Christian Borntraeger
[not found] ` <20200408115926.1467567-10-hch@lst.de>
2020-04-08 15:00 ` [PATCH 09/28] mm: rename CONFIG_PGTABLE_MAPPING to CONFIG_ZSMALLOC_PGTABLE_MAPPING Randy Dunlap
2020-04-09 15:59 ` Minchan Kim
2020-04-08 16:03 ` Russell King - ARM Linux admin [this message]
[not found] ` <20200408115926.1467567-2-hch@lst.de>
2020-04-09 15:52 ` [PATCH 01/28] x86/hyperv: use vmalloc_exec for the hypercall page Wei Liu
2020-04-10 20:40 ` Michael Kelley
[not found] ` <20200408115926.1467567-11-hch@lst.de>
2020-04-08 15:01 ` [PATCH 10/28] mm: only allow page table mappings for built-in zsmalloc Randy Dunlap
2020-04-08 15:12 ` Peter Zijlstra
2020-04-08 15:15 ` Matthew Wilcox
2020-04-08 15:36 ` Randy Dunlap
[not found] ` <20200408153602.GA28081@lst.de>
2020-04-08 15:37 ` Randy Dunlap
2020-04-09 16:08 ` Minchan Kim
2020-04-09 16:50 ` Peter Zijlstra
2020-04-09 17:08 ` Minchan Kim
2020-04-10 2:38 ` Sergey Senozhatsky
2020-04-10 23:11 ` Minchan Kim
[not found] ` <20200411072052.GA31242@lst.de>
2020-04-16 20:37 ` Minchan Kim
[not found] ` <20200408115926.1467567-26-hch@lst.de>
2020-04-09 22:25 ` [PATCH 25/28] mm: remove vmalloc_user_node_flags Andrii Nakryiko
2020-04-13 20:03 ` Johannes Weiner
[not found] ` <20200408115926.1467567-21-hch@lst.de>
2020-04-10 20:39 ` [PATCH 20/28] mm: remove the pgprot argument to __vmalloc Michael Kelley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200408160324.GS25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=christophe.leroy@c-s.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=haiyangz@microsoft.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kys@microsoft.com \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=peterz@infradead.org \
--cc=robin.murphy@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).