Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp989955ybl; Wed, 4 Dec 2019 14:41:36 -0800 (PST) X-Google-Smtp-Source: APXvYqzdWgcf3QmihLmdL5lCmVJC1tUgoVG150gdPEdOhvnlrWGkS7SST6KtWSDuWDArbQNLO9l8 X-Received: by 2002:a05:6830:1e9a:: with SMTP id n26mr4085627otr.99.1575499296427; Wed, 04 Dec 2019 14:41:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575499296; cv=none; d=google.com; s=arc-20160816; b=zNMrSxPtT9PZbk1Bzz8Tsk4TGPnTc0dDB9flihnvdRuv2bJZggJ9qExEeT0d+J8/1M JbQ2PDIYZ+llJZfkOhEq0bqBVefA0pW9Dm3jzUfP6B8Dm8LpXwZuqD3Tx2GoMn9tTcW4 H6iC5+YID+qa875C53S8qfOZhYpalUwYR9m77aC+vyb1lIEbS0OwVhknUGGMinbIrMdc f6MJT9sVm7rgoKTNsccd0zRMqcenCetV0bpGZji4wbHxleiAKosTb4MUW7cUbvDy6qOx Hv1QqdrRl2n+MNMMB+vicP3Hr4kxB05PSJGoEVVD/3LBmpu2gLDFDuEQGW+3556ym1Gh RASA== 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:date:from:dkim-signature; bh=PXU0l6hsLNwOEAachYcf3O/SAhU82EqIUjlmH0om7uk=; b=PnCi7EfWB9+qk6lTm2B98VehmrzcI4VLx+4O9UzwmO0Md/Q5mMbjm8dbhLdrO4jm67 RazLMDgzhiSPNNre+J8V9ooRPPGbbwg5hL0PuATkJ7T+Gd/+Jp/pUxsr3+A4Nz0rUUjh Qe1zxnCooU7ClRUAS4uKwXuG0IE3yWF0rQkwvXFQjOPn2CgMVQtdmh+qlIsiBaidU6hl at5A/lSlvKR9Jlzoy1L5PmE+xWQlvrZoigaejENWq2+nV5uvG/hMybImxSYNwBCUjVP+ kOsl6jGhDx5Uc72+n3C/ALQPqbj0+F3/DjsG3nlF8SYeeRAtKQTEJD1DnUNlawfZKPNF 6fzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=F96XFSXR; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m1si1527201otf.174.2019.12.04.14.41.22; Wed, 04 Dec 2019 14:41:36 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=F96XFSXR; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728121AbfLDWkt (ORCPT + 99 others); Wed, 4 Dec 2019 17:40:49 -0500 Received: from mail-lf1-f66.google.com ([209.85.167.66]:38635 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728053AbfLDWks (ORCPT ); Wed, 4 Dec 2019 17:40:48 -0500 Received: by mail-lf1-f66.google.com with SMTP id r14so866788lfm.5 for ; Wed, 04 Dec 2019 14:40:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=PXU0l6hsLNwOEAachYcf3O/SAhU82EqIUjlmH0om7uk=; b=F96XFSXRmW86ugKdykHTCw+//Ckr2I37FfACIGnU9BIPH5uQDgSkjEaFAJjn5FOd9N ghzJbE0W0zDlD4xBGKMbcWs9mdQDJlJ4RRJYRRWH2dTttCzUlySAKLwlWjfdlQd8Inpj AqnY9qnCilK/APl5c93l5GJXqWw6TnVlqwrsKPxnYgTZNyiiQu7DegGpw3qSy4GvEviy yvkyIeft4+SJpKxQs2wvH7TkCm/iL2cR87+qLAvXqYcjDTidd5oqLe+teimX0iYs5uob CS8JXtTgcwFeaCuPij5HAP/bR66jxE9lT2dsEgLl1xkrD+tIrcB1JW5znVjUp6InIpZx fIiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=PXU0l6hsLNwOEAachYcf3O/SAhU82EqIUjlmH0om7uk=; b=rBYgerIQMixk2i6NQD/5sa0OQ1UbnUzrl8XMIwKyFWb2+Ne0LV1cnSc3hRhUNGPyI6 77DrM3HFKBiYrYz2rMJt4QZP2rJhF/ZcBvS0jyW7+n+Vna7M1io3IbyNvOINvpJ4LVlO lpZy3GYpd3q7ZzQbpQHrjlXS+Hf2gdJt+NFvBWJyEXYYvb/resirAyMLrcLR7XZ7kScf O4z6txZoXHqy/htO70YpTR87SSlRJbAYroOChYXSE5XaRMr+BDfs0E+OpDCM+HXnDgzK yRfZiHuumql6ZXSWORe1o955lRxNWhC9TKTjpAqFhwxVHKanuqQ3bLRC9fTSjV6HXT4l Fbow== X-Gm-Message-State: APjAAAV04eTxcsxa6h989aA34MKp4yClZs0WrPYmJkVI0rkbyhqp8XkT tsHbGezUNc65YhdCBzT9zhc= X-Received: by 2002:a19:4f46:: with SMTP id a6mr3490704lfk.143.1575499246564; Wed, 04 Dec 2019 14:40:46 -0800 (PST) Received: from pc636 (h5ef52e31.seluork.dyn.perspektivbredband.net. [94.245.46.49]) by smtp.gmail.com with ESMTPSA id m16sm3932304ljb.47.2019.12.04.14.40.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Dec 2019 14:40:45 -0800 (PST) From: Uladzislau Rezki X-Google-Original-From: Uladzislau Rezki Date: Wed, 4 Dec 2019 23:40:37 +0100 To: Andrey Ryabinin Cc: Andrew Morton , Alexander Potapenko , Dmitry Vyukov , kasan-dev@googlegroups.com, Daniel Axtens , Qian Cai , linux-mm@kvack.org, linux-kernel@vger.kernel.org, syzbot+82e323920b78d54aaed5@syzkaller.appspotmail.com Subject: Re: [PATCH 1/2] kasan: fix crashes on access to memory mapped by vm_map_ram() Message-ID: <20191204224037.GA12896@pc636> References: <20191204204534.32202-1-aryabinin@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191204204534.32202-1-aryabinin@virtuozzo.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > diff --git a/mm/vmalloc.c b/mm/vmalloc.c > index 4d3b3d60d893..a5412f14f57f 100644 > --- a/mm/vmalloc.c > +++ b/mm/vmalloc.c > @@ -1073,6 +1073,7 @@ static struct vmap_area *alloc_vmap_area(unsigned long size, > struct vmap_area *va, *pva; > unsigned long addr; > int purged = 0; > + int ret = -EBUSY; > > BUG_ON(!size); > BUG_ON(offset_in_page(size)); > @@ -1139,6 +1140,10 @@ static struct vmap_area *alloc_vmap_area(unsigned long size, > va->va_end = addr + size; > va->vm = NULL; > > + ret = kasan_populate_vmalloc(addr, size); > + if (ret) > + goto out; > + But it introduces another issues when is CONFIG_KASAN_VMALLOC=y. If the kasan_populate_vmalloc() gets failed for some reason it just leaves the function, that will lead to waste of vmap space. > spin_lock(&vmap_area_lock); > insert_vmap_area(va, &vmap_area_root, &vmap_area_list); > spin_unlock(&vmap_area_lock); > ret = kasan_populate_vmalloc(addr, size); if (ret) { free_vmap_area(va); return ERR_PTR(-EBUSY);; } > @@ -1169,8 +1174,9 @@ static struct vmap_area *alloc_vmap_area(unsigned long size, > pr_warn("vmap allocation for size %lu failed: use vmalloc= to increase size\n", > size); > > +out: > kmem_cache_free(vmap_area_cachep, va); > - return ERR_PTR(-EBUSY); > + return ERR_PTR(ret); > } >