Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1238764
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC][PATCH] x86/mm: warn on W+x mappings |
| Date | 2015-10-03 10:00 +0200 |
| Message-ID | <qfpTA-40C-13@gated-at.bofh.it> (permalink) |
| References | <qeP3I-1CP-17@gated-at.bofh.it> <qeRIe-5ti-23@gated-at.bofh.it> <qeS1z-5PY-1@gated-at.bofh.it> <qf2X0-50d-11@gated-at.bofh.it> <qf3Jn-69x-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Borislav Petkov <bp@alien8.de> wrote: > On Fri, Oct 02, 2015 at 09:26:44AM +0200, Ingo Molnar wrote: > > It's better to generate a WARN()ing programmatically if the W+X condition occurs, > > that gets noticed by tools and people alike. I'd like to start treating that > > condition as a hard kernel bug. > > > > A dump in dmesg is subject to random noise by printk crusaders and is also subject > > to general bitrot, nor does it provide any ready warning to act upon. > > You're not going to enable this option in production anyway. [...] Why not? I'd suggest distros do it too, it's not too much code to run during bootup. That way if we one some weird configuration forget about a W+X mapping, the distro is warned that there's a security problem. > > I'd even add this debug check as default-enabled in the x86 defconfigs, so > > that my own continuous kernel testing kit picks up any new warnings from it. > > There's the problem with exposing sensitive info in debugfs if you do that. And > nowadays we're trying hard not to leak any of that. Ah, I think you missed the following detail: the patch I suggested would separate the debugfs bits from the checking bits and would thus allow a 'security check only' .config setting. Distros would normally not want to enable the debugfs file, agreed about that. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC][PATCH] x86/mm: warn on W+x mappings Stephen Smalley <sds@tycho.nsa.gov> - 2015-10-01 18:40 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Kees Cook <keescook@chromium.org> - 2015-10-01 21:30 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Borislav Petkov <bp@alien8.de> - 2015-10-01 21:50 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Ingo Molnar <mingo@kernel.org> - 2015-10-02 09:30 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Borislav Petkov <bp@alien8.de> - 2015-10-02 10:20 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Ingo Molnar <mingo@kernel.org> - 2015-10-03 10:00 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Borislav Petkov <bp@alien8.de> - 2015-10-03 11:10 +0200
Re: [RFC][PATCH] x86/mm: warn on W+x mappings Ingo Molnar <mingo@kernel.org> - 2015-10-02 09:40 +0200
csiph-web