Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1691706
| From | Christopher Lameter <cl@linux.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/1] mm/slub.c: add a naive detection of double free or corruption |
| Date | 2017-07-19 16:10 +0200 |
| Message-ID | <u4XPQ-1bD-29@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <u4iMH-8w3-43@gated-at.bofh.it> <u4jz4-zE-15@gated-at.bofh.it> <u4jIJ-Dg-9@gated-at.bofh.it> <u4GP0-6Cx-21@gated-at.bofh.it> <u4GYF-6V8-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 18 Jul 2017, Kees Cook wrote: > I think there are two issues: first, this should likely be under > CONFIG_FREELIST_HARDENED since Christoph hasn't wanted to make these > changes enabled by default (if I'm understanding his earlier review > comments to me). The second issue is what to DO when a double-free is > discovered. Is there any way to make it safe/survivable? If not, I The simple thing is to not free the object when you discover this. That is what the existing debugging code does. But you do not have an easy way to fail at the point in the code that is patched here.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 1/1] mm/slub.c: add a naive detection of double free or corruption Alexander Popov <alex.popov@linux.com> - 2017-07-18 22:00 +0200
Re: [PATCH 1/1] mm/slub.c: add a naive detection of double free or corruption Kees Cook <keescook@chromium.org> - 2017-07-18 22:10 +0200
Re: [PATCH 1/1] mm/slub.c: add a naive detection of double free or corruption Alexander Popov <alex.popov@linux.com> - 2017-07-19 10:40 +0200
Re: [PATCH 1/1] mm/slub.c: add a naive detection of double free or corruption Christopher Lameter <cl@linux.com> - 2017-07-19 16:10 +0200
csiph-web