Received: by 10.192.165.148 with SMTP id m20csp4929210imm; Tue, 24 Apr 2018 10:41:29 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpmgSGAsopDsnRPB9AH7blF/tK/wmDmdxDOq8SCW8Or0Dv3xOn4fHQmQjFBFp9AH5ljR+eK X-Received: by 2002:a17:902:7702:: with SMTP id n2-v6mr4159952pll.385.1524591689449; Tue, 24 Apr 2018 10:41:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524591689; cv=none; d=google.com; s=arc-20160816; b=fOZX/WiiIuJtxAwGX0PaMoVjAF+Gp37UPMO21kyugBy1W4QpHY1UD9g2fLbZV1TrPI ZI+W+KORVePdYvExOKwIjpn3VTyquRzTNm3tiusGkvL1am7zPL+vyLL9b+d6jQ6azALz okAxc6haYYCxzSAFEk3sxTpt+6S42TCWZF6JpQhtLlZAvCjAjfsprvknJ+IztWtubnVN 7GHwhBntffDXuuba1a0gkL44D6W9YZ09IJAnDn0F6W1wI11GolDEj5eE8wdhWLftqfg1 olRx5Umfayf3Gl+yft7XrR6lZxevoeoTyy2wJvHvxt0AANt8I9svOnohOtTODaMA1gPj L17g== 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=C9ErHT+lNeaU4ydSKTulIZSOE0h+xTGWN4v8dqvVtVw=; b=afl9GS83TwexbE40r/Vo4zoUlTA4+4hxN90F/BeADuf+p/WHzdJhwJazLA6LhODkAG 9jpxac8kCUy0jobp9J1tJZXvhZygbwvJV41Jo39nuUBI30TWVROgWfgLsevtm+1HJFDI 5BzOamWzhfPzRzn+7XjrZNZoULQVFBcpLqxo1lQzeVTaqthG5epafWlsuAgo+Te/ZRRU 9ptTRCY/+N/LOJQok3gtfpIKFGkimFptGVR/+I9So3Q0eA3Tz5+qDiD4Yi1czyDFpW4z w+etXLu9Eg/smURRZxT4IVHawwi5nu4DNPXWYGLYp1fTtj/fWUGzepWZXJvlHeylMBOe W4BA== 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 u7si11085578pgv.251.2018.04.24.10.41.14; Tue, 24 Apr 2018 10:41:29 -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 S1752862AbeDXRio (ORCPT + 99 others); Tue, 24 Apr 2018 13:38:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:46809 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460AbeDXRil (ORCPT ); Tue, 24 Apr 2018 13:38:41 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 6C25AAC64; Tue, 24 Apr 2018 17:38:39 +0000 (UTC) Date: Tue, 24 Apr 2018 11:38:36 -0600 From: Michal Hocko To: Mikulas Patocka Cc: Matthew Wilcox , David Miller , Andrew Morton , linux-mm@kvack.org, eric.dumazet@gmail.com, edumazet@google.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, mst@redhat.com, jasowang@redhat.com, virtualization@lists.linux-foundation.org, dm-devel@redhat.com, Vlastimil Babka Subject: Re: [PATCH v3] kvmalloc: always use vmalloc if CONFIG_DEBUG_SG Message-ID: <20180424173836.GR17484@dhcp22.suse.cz> References: <20180421144757.GC14610@bombadil.infradead.org> <20180423151545.GU17484@dhcp22.suse.cz> <20180424125121.GA17484@dhcp22.suse.cz> <20180424162906.GM17484@dhcp22.suse.cz> <20180424170349.GQ17484@dhcp22.suse.cz> 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 Tue 24-04-18 13:28:49, Mikulas Patocka wrote: > > > On Tue, 24 Apr 2018, Michal Hocko wrote: > > > On Tue 24-04-18 13:00:11, Mikulas Patocka wrote: > > > > > > > > > On Tue, 24 Apr 2018, Michal Hocko wrote: > > > > > > > On Tue 24-04-18 11:50:30, Mikulas Patocka wrote: > > > > > > > > > > > > > > > On Tue, 24 Apr 2018, Michal Hocko wrote: > > > > > > > > > > > On Mon 23-04-18 20:06:16, Mikulas Patocka wrote: > > > > > > [...] > > > > > > > @@ -404,6 +405,12 @@ void *kvmalloc_node(size_t size, gfp_t f > > > > > > > */ > > > > > > > WARN_ON_ONCE((flags & GFP_KERNEL) != GFP_KERNEL); > > > > > > > > > > > > > > +#ifdef CONFIG_DEBUG_SG > > > > > > > + /* Catch bugs when the caller uses DMA API on the result of kvmalloc. */ > > > > > > > + if (!(prandom_u32_max(2) & 1)) > > > > > > > + goto do_vmalloc; > > > > > > > +#endif > > > > > > > > > > > > I really do not think there is anything DEBUG_SG specific here. Why you > > > > > > simply do not follow should_failslab path or even reuse the function? > > > > > > > > > > CONFIG_DEBUG_SG is enabled by default in RHEL and Fedora debug kernel (if > > > > > you don't like CONFIG_DEBUG_SG, pick any other option that is enabled > > > > > there). > > > > > > > > Are you telling me that you are shaping a debugging functionality basing > > > > on what RHEL has enabled? And you call me evil. This is just rediculous. > > > > > > > > > Fail-injection framework is if off by default and it must be explicitly > > > > > enabled and configured by the user - and most users won't enable it. > > > > > > > > It can be enabled easily. And if you care enough for your debugging > > > > kernel then just make it enabled unconditionally. > > > > > > So, should we add a new option CONFIG_KVMALLOC_FALLBACK_DEFAULT? I'm not > > > quite sure if 3 lines of debugging code need an extra option, but if you > > > don't want to reuse any existing debug option, it may be possible. Adding > > > it to the RHEL debug kernel would be trivial. > > > > Wouldn't it be equally trivial to simply enable the fault injection? You > > would get additional failure paths testing as a bonus. > > The RHEL and Fedora debugging kernels are compiled with fault injection. > But the fault-injection framework will do nothing unless it is enabled by > a kernel parameter or debugfs write. > > Most users don't know about the fault injection kernel parameters or > debugfs files and won't enabled it. We need a CONFIG_ option to enable it > by default in the debugging kernels (and we could add a kernel parameter > to override the default, fine-tune the fallback probability etc.) If it is a real issue to install the debugging kernel with the required kernel parameter then I a config option for the default on makes sense to me. -- Michal Hocko SUSE Labs