Re: [PATCH v3 11/26] mm/swapfile: Annotate static information into meminspect
Christoph Hellwig <[email protected]>
| Newsgroups | org.kernel.vger.linux-remoteproc,org.kernel.vger.linux-arch,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel,org.kernel.vger.workflows,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 09, 2026 at 03:53:44PM +0100, Lorenzo Stoakes wrote: > > The whole reason we had to tag most of the MM symbols is that > > the crash tool looks for this information while launching itself. > > You're missing the point. > > EXPORT_SYMBOL_GPL() != EXPORT_SYMBOL(). > > We cannot and will not allow symbols that are GPL-only to be exported by the > back door to non-GPL modules. > > Meminspect seems to ignore all of this and just exports symbols another way > overriding kernel mechanisms which is just not acceptable... > > I also don't really understand what you're saying here either, what has what > crash looks up on startup got to do with anything? Yeah, random backdoor exports for a totally opaque facility without good use cases that comes from a known malicious actor like qualcomm is a no-go. I don't think anyone should even waste time on this.