Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1314276
| From | Christoph Lameter <cl@linux.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC][PATCH 0/7] Sanitization of slabs based on grsecurity/PaX |
| Date | 2016-01-21 16:40 +0100 |
| Message-ID | <qTpv4-7aA-5@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <qOlBN-29Y-27@gated-at.bofh.it> <qOu2n-7SE-15@gated-at.bofh.it> <qOFTR-7OQ-15@gated-at.bofh.it> <qQHeO-1eM-3@gated-at.bofh.it> <qTegi-7QO-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
n Wed, 20 Jan 2016, Laura Abbott wrote: > The SLAB_DEBUG flags force everything to skip the CPU caches which is > causing the slow down. I experimented with allowing the debugging to > happen with CPU caches but I'm not convinced it's possible to do the > checking on the fast path in a consistent manner without adding > locking. Is it worth refactoring the debugging to be able to be used > on cpu caches or should I take the approach here of having the clear > be separate from free_debug_processing? At least posioning would benefit from such work. I think both sanitization and posoning should be done by the same logic. Remove poisoning if necessary. Note though that this security stuff should not have a significant impact on the general case.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [RFC][PATCH 0/7] Sanitization of slabs based on grsecurity/PaX Laura Abbott <laura@labbott.name> - 2016-01-21 04:40 +0100 Re: [RFC][PATCH 0/7] Sanitization of slabs based on grsecurity/PaX Christoph Lameter <cl@linux.com> - 2016-01-21 16:40 +0100
csiph-web