Date: Wed, 24 Oct 2018 17:07:06 +0200 From: Jessica Yu <jeyu@...nel.org> To: Ard Biesheuvel <ard.biesheuvel@...aro.org> Cc: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "daniel@...earbox.net" <daniel@...earbox.net>, "keescook@...omium.org" <keescook@...omium.org>, "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>, "arjan@...ux.intel.com" <arjan@...ux.intel.com>, "tglx@...utronix.de" <tglx@...utronix.de>, "linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>, "linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>, "jannh@...gle.com" <jannh@...gle.com>, "x86@...nel.org" <x86@...nel.org>, "kristen@...ux.intel.com" <kristen@...ux.intel.com>, "Dock, Deneen T" <deneen.t.dock@...el.com>, "catalin.marinas@....com" <catalin.marinas@....com>, "mingo@...hat.com" <mingo@...hat.com>, "will.deacon@....com" <will.deacon@....com>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, "bp@...en8.de" <bp@...en8.de>, "Hansen, Dave" <dave.hansen@...el.com>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "davem@...emloft.net" <davem@...emloft.net>, "arnd@...db.de" <arnd@...db.de>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, "sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org> Subject: Re: [PATCH RFC v3 0/3] Rlimit for module space +++ Ard Biesheuvel [23/10/18 08:54 -0300]: >On 22 October 2018 at 20:06, Edgecombe, Rick P ><rick.p.edgecombe@...el.com> wrote: >> On Sat, 2018-10-20 at 19:20 +0200, Ard Biesheuvel wrote: >>> Hi Rick, >>> >>> On 19 October 2018 at 22:47, Rick Edgecombe <rick.p.edgecombe@...el.com> >>> wrote: >>> > If BPF JIT is on, there is no effective limit to prevent filling the entire >>> > module space with JITed e/BPF filters. >>> >>> Why do BPF filters use the module space, and does this reason apply to >>> all architectures? >>> >>> On arm64, we already support loading plain modules far away from the >>> core kernel (i.e. out of range for ordinary relative jump/calll >>> instructions), and so I'd expect BPF to be able to deal with this >>> already as well. So for arm64, I wonder why an ordinary vmalloc_exec() >>> wouldn't be more appropriate. >> AFAIK, it's like you said about relative instruction limits, but also because >> some predictors don't predict past a certain distance. So performance as well. >> Not sure the reasons for each arch, or if they all apply for BPF JIT. There seem >> to be 8 by my count, that have a dedicated module space for some reason. >> >>> So before refactoring the module alloc/free routines to accommodate >>> BPF, I'd like to take one step back and assess whether it wouldn't be >>> more appropriate to have a separate bpf_alloc/free API, which could be >>> totally separate from module alloc/free if the arch permits it. >>> >> I am not a BPF JIT expert unfortunately, hopefully someone more authoritative >> will chime in. I only ran into this because I was trying to increase >> randomization for the module space and wanted to find out how many allocations >> needed to be supported. >> >> I'd guess though, that BPF JIT is just assuming that there will be some arch >> specific constraints about where text can be placed optimally and they would >> already be taken into account in the module space allocator. >> >> If there are no constraints for some arch, I'd wonder why not just update its >> module_alloc to use the whole space available. What exactly are the constraints >> for arm64 for normal modules? >> > >Relative branches and the interactions with KAsan. > >We just fixed something similar in the kprobes code: it was using >RWX-mapped module memory to store kprobed instructions, and we >replaced that with a simple vmalloc_exec() [and code to remap it >read-only], which was possible given that relative branches are always >emulated by arm64 kprobes. > >So it depends on whether BPF code needs to be in relative branching >range from the calling code, and whether the BPF code itself is >emitted using relative branches into other parts of the code. > >> It seems fine to me for architectures to have the option of solving this a >> different way. If potentially the rlimit ends up being the best solution for >> some architectures though, do you think this refactor (pretty close to just a >> name change) is that intrusive? >> >> I guess it could be just a BPF JIT per user limit and not touch module space, >> but I thought the module space limit was a more general solution as that is the >> actual limited resource. >> > >I think it is wrong to conflate the two things. Limiting the number of >BPF allocations and the limiting number of module allocations are two >separate things, and the fact that BPF reuses module_alloc() out of >convenience does not mean a single rlimit for both is appropriate. Hm, I think Ard has a good point. AFAIK, and correct me if I'm wrong, users of module_alloc() i.e. kprobes, ftrace, bpf, seem to use it because it is an easy way to obtain executable kernel memory (and depending on the needs of the architecture, being additionally reachable via relative branches) during runtime. The side effect is that all these users share the "module" memory space, even though this memory region is not exclusively used by modules (well, personally I think it technically should be, because seeing module_alloc() usage outside of the module loader is kind of a misuse of the module API and it's confusing for people who don't know the reason behind its usage outside of the module loader). Right now I'm not sure if it makes sense to impose a blanket limit on all module_alloc() allocations when the real motivation behind the rlimit is related to BPF, i.e., to stop unprivileged users from hogging up all the vmalloc space for modules with JITed BPF filters. So the rlimit has more to do with limiting the memory usage of BPF filters than it has to do with modules themselves. I think Ard's suggestion of having a separate bpf_alloc/free API makes a lot of sense if we want to keep track of bpf-related allocations (and then the rlimit would be enforced for those). Maybe part of the module mapping space could be carved out for bpf filters (e.g. have BPF_VADDR, BPF_VSIZE, etc like how we have it for modules), or continue sharing the region but explicitly define a separate bpf_alloc API, depending on an architecture's needs. What do people think? Thanks, Jessica
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.