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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 27 Apr 2018 10:25:55 +0200
From:   Michal Hocko <>
To:     Mikulas Patocka <>
Cc:     "Michael S. Tsirkin" <>,
        John Stoffel <>,
        James Bottomley <>,,,,, Randy Dunlap <>,, Matthew Wilcox <>,,,
        Vlastimil Babka <>,,
        David Rientjes <>,
        Morton <>,,
        David Miller <>,
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

Powered by blists - more mailing lists