Received: by 10.192.165.148 with SMTP id m20csp4893589imm; Tue, 24 Apr 2018 10:05:26 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+JbRZ6v1SZQv36Qky8dCLmgp+ImSghFZxKFgVuUYnhVUHmAYoWwdeFi9wmpJTNqhJQKF+u X-Received: by 2002:a17:902:3225:: with SMTP id y34-v6mr26179319plb.180.1524589526865; Tue, 24 Apr 2018 10:05:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524589526; cv=none; d=google.com; s=arc-20160816; b=atks4MbofZkXLKKJgzIjObO2k4Jazbmu6G5vhkUXQXVxw8vBGxSf5UGtl31lUlcuMP Fcb4Eod2G3DRY1eqmqz/i1Ovahjp11a+TIGnSmRrFAz/LQlXTOhxObAUITkwsiiozbec q03ze2zaQpdEU+mse9REFj0Z5YuGdwGGNdnQFlERb6UPaYe4FKuWuvw/joT9zKaYS62O IEARqTAqcREQsINtKDrPOMkzhlDz4M8pH8CoGSGqAdOq/IOYc6HqQI9uDTuG3XwFJgke kebYJhR3rXg/LTPxoowBJDzsmksy1OMDas381V5SutWyUtvGdyHrX8hgQmDBugPdXy7T S8ZA== 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=cJpL2jjQIAIrFYzuarHw+tiNjG+AHbIYwayHz9BsoVM=; b=ogIHoWkcQ0qwV+HCV4QrmDO4PZzzJAP5D8VwpRSNqDMz+5bQ2cq6Or5LlBzEoAwBcz 6bD6rFogI+6rWt/OSIY3Y+wbCgaZ0PnGgzeBvwg83H9TLDHLN923eC9I1w3o9ZMmfi8W dkjGo5BXmodboL8lsFn7JwavCvJIKrlJfl2nrvj3xQ/d1tJuDBsZZN9NTklzbEkS+N3z LYas0camQ0F9BTudg64m2NngcOzx3sgnGUj5BPfZ5SEDkYaCc3d4DmT8meIz6fWZI593 kCMEgLDQywpPvGBoY/zoW1COjKjmXjsz1MNToxiApJrlnSnTU4I4VvhFgXEOBDWmas6E gywA== 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 v40-v6si14433704plg.84.2018.04.24.10.05.11; Tue, 24 Apr 2018 10:05:26 -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 S1751612AbeDXRD4 (ORCPT + 99 others); Tue, 24 Apr 2018 13:03:56 -0400 Received: from mx2.suse.de ([195.135.220.15]:43681 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750757AbeDXRDy (ORCPT ); Tue, 24 Apr 2018 13:03:54 -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 ADE04AC61; Tue, 24 Apr 2018 17:03:52 +0000 (UTC) Date: Tue, 24 Apr 2018 11:03:49 -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: <20180424170349.GQ17484@dhcp22.suse.cz> References: <20180420210200.GH10788@bombadil.infradead.org> <20180421144757.GC14610@bombadil.infradead.org> <20180423151545.GU17484@dhcp22.suse.cz> <20180424125121.GA17484@dhcp22.suse.cz> <20180424162906.GM17484@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: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. -- Michal Hocko SUSE Labs