Received: by 10.192.165.148 with SMTP id m20csp444148imm; Fri, 27 Apr 2018 01:28:34 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpmi4tnUGPOw6Z7gREkPodCthhBYkzqjIqt01k9uuDdiJFiQzAkASa+Xv+fqdxjg+oChG6T X-Received: by 10.98.8.12 with SMTP id c12mr1357405pfd.77.1524817714054; Fri, 27 Apr 2018 01:28:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524817714; cv=none; d=google.com; s=arc-20160816; b=ndUL5krI9cFJz3gafbRLNax8fTLjvjx0sJ9fNU7BaJ/sOauKR1eDM1ZtL8TUu3oeeC fjWUDQxOEqC39dKYc7ee2/iHJ89AP6Lf/qxzZmcf2Q8iBMGBzp6ZKh8LLOP8s8IV9xhO dOAQqI7XZnnOTdExcoZnOduOQ8PMfERAzSpqgly1Pc8mtUxut1MEnSx5fTfF3PAjLY0x zGeC2q3HqHULWFR3nqaKq4VZP1jRtMnMRbtQgZvOHbXXrlqKGTB+yzEo267khZPQDicO C4x/PiyJXdGM+0LUSVZ94meYQTxsatLEaAFbJhpr/FievayU/JxRIe18ocKQs4uzqxjN Gufw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=J2vG7Hwijxk1rf3gpfFFVllZyvVRkoraDXseTgTa1K0=; b=C+zt5o/Xu+GXpgUnL9nNOQ2mRGyGokl/DobcAKJFvht5oiEyVrKD+xoTAlxdbOhjn+ +7/ZANwvPIhwxFHC+xGCG0azCjw0VCE9AAgqRRY6IyjDjvP0w/Ami36UCYMOPGs0wbnS XgiYAWAoYyiSljz93SDrMaPfEKfha6gI2OKHsy4QNvdZCACEe4SX68yvwa+vOxZifqWs N9eDwVxEQSku+Eud1AUkvMNY+w3sbdzWCwsznlyHmIYsshnNcHJ3SogWOsSJhMszwRq9 3tLZfLmEvmS+kLDFeKMJw3Z05edyRBkGqHQ2TIan9dRHJG1jAsbEmeiIHG0dM2wuLSGR nUrw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d8-v6si789989pgt.630.2018.04.27.01.28.20; Fri, 27 Apr 2018 01:28:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932295AbeD0I0A (ORCPT + 99 others); Fri, 27 Apr 2018 04:26:00 -0400 Received: from mx2.suse.de ([195.135.220.15]:40946 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757758AbeD0IZ6 (ORCPT ); Fri, 27 Apr 2018 04:25:58 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 360FEAC4F; Fri, 27 Apr 2018 08:25:57 +0000 (UTC) Date: Fri, 27 Apr 2018 10:25:55 +0200 From: Michal Hocko To: Mikulas Patocka Cc: "Michael S. Tsirkin" , John Stoffel , James Bottomley , Michal@stoffel.org, eric.dumazet@gmail.com, netdev@vger.kernel.org, jasowang@redhat.com, Randy Dunlap , linux-kernel@vger.kernel.org, Matthew Wilcox , linux-mm@kvack.org, dm-devel@redhat.com, Vlastimil Babka , Andrew@stoffel.org, David Rientjes , Morton , virtualization@lists.linux-foundation.org, David Miller , edumazet@google.com Subject: Re: [dm-devel] [PATCH v5] fault-injection: introduce kvmalloc fallback options Message-ID: <20180427082555.GC17484@dhcp22.suse.cz> References: <1524694663.4100.21.camel@HansenPartnership.com> <1524697697.4100.23.camel@HansenPartnership.com> <23266.8532.619051.784274@quad.stoffel.home> <20180427005213-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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