lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 27 Apr 2018 10:25:55 +0200 From: Michal Hocko <mhocko@...nel.org> To: Mikulas Patocka <mpatocka@...hat.com> Cc: "Michael S. Tsirkin" <mst@...hat.com>, John Stoffel <john@...ffel.org>, James Bottomley <James.Bottomley@...senPartnership.com>, Michal@...ffel.org, eric.dumazet@...il.com, netdev@...r.kernel.org, jasowang@...hat.com, Randy Dunlap <rdunlap@...radead.org>, linux-kernel@...r.kernel.org, Matthew Wilcox <willy@...radead.org>, linux-mm@...ck.org, dm-devel@...hat.com, Vlastimil Babka <vbabka@...e.cz>, Andrew@...ffel.org, David Rientjes <rientjes@...gle.com>, Morton <akpm@...ux-foundation.org>, virtualization@...ts.linux-foundation.org, David Miller <davem@...emloft.net>, edumazet@...gle.com Subject: Re: [dm-devel] [PATCH v5] fault-injection: introduce kvmalloc fallback options On Thu 26-04-18 18:52:05, Mikulas Patocka wrote: > > > On Fri, 27 Apr 2018, Michael S. Tsirkin wrote: [...] > > But assuming it's important to control this kind of > > fault injection to be controlled from > > a dedicated menuconfig option, why not the rest of > > faults? > > The injected faults cause damage to the user, so there's no point to > enable them by default. vmalloc fallback should not cause any damage > (assuming that the code is correctly written). But you want to find those bugs which would BUG_ON easier, so there is a risk of harm IIUC and this is not much different than other fault injecting paths. -- Michal Hocko SUSE Labs
Powered by blists - more mailing lists