Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp618467imu; Fri, 25 Jan 2019 08:02:38 -0800 (PST) X-Google-Smtp-Source: ALg8bN607o94/PISyIJ6HxZOd+NSxu34Y4wyYo6LVcO8Ba6m/VhF8p8DuY7pb9vqtj9PEvB6WZ1F X-Received: by 2002:a63:e711:: with SMTP id b17mr10163549pgi.363.1548432158174; Fri, 25 Jan 2019 08:02:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548432158; cv=none; d=google.com; s=arc-20160816; b=Gm508ISdJF5c0/lA/agun5Ef3ejPhF0jieL2Sf89WnpUOsjbk4Pe4EgMaIhrhJVc20 W14oZRadqR9Rn0+8FRC4zUqHwSu5I7HJtNRuyn4nrlnxC4a5VxNx/FL0ZoXbAhaZbUiQ XIX6MEncCVG95FWXvlQsc88pe+eOHd/boLCMkNj1y2YEFcsPdz3W+NwENBTkSmCsKbj2 290u3r4QzHjQOttRllb7xxiJkXn7zO7g6HRp3lCC0p1JCEqXpV1cWFnazVt6lIQBB8u6 9ATOzyQ3lnNeH78xAwKsiBzyfQ+iYHr3RldDPSLeNByl8mvjLIypZ6v7Pf3KVL+kT4HL pL8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=CqCtzfmNIlsjjr37EaboZ+t7nVgdj0ZPM+y425F5GJQ=; b=ljWzze+AuNmimN0RCfhyhvzFi7FmDG6gQ1pIvXbubn9B1QIyEJX94O5k2WDO3/WqGh x+ii/pwyUAKPP3/Vn5WF7S+EkPfgV/yvLBRH9x7e8RwZuucHmTm8tDGUy039XFYvKxdV FbFsAJNxYqUzw+Wrclx/5IthEOs4G6fAZDCpkE8ysRsG1LfMjvsedLhBoGIaKSC7KicS qnVR8pC2gAwDz2hQYUnLB9ylFitaPyx/8syWZHCMredzBpNcdmDiA92OgOhMYdLcinLS p787kB0bSAyWpz4n2FXeNu19ZIyosV97bd40fJ/GK2fjBx8iijqE0QeKuuLxSZqOQXCJ ohPw== 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 a124si3317899pfb.263.2019.01.25.08.02.22; Fri, 25 Jan 2019 08:02:38 -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; 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 S1726800AbfAYQCI (ORCPT + 99 others); Fri, 25 Jan 2019 11:02:08 -0500 Received: from www262.sakura.ne.jp ([202.181.97.72]:45068 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726122AbfAYQCI (ORCPT ); Fri, 25 Jan 2019 11:02:08 -0500 Received: from fsav107.sakura.ne.jp (fsav107.sakura.ne.jp [27.133.134.234]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id x0PG26fg055728; Sat, 26 Jan 2019 01:02:06 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav107.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav107.sakura.ne.jp); Sat, 26 Jan 2019 01:02:06 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav107.sakura.ne.jp) Received: from [192.168.1.8] (softbank126126163036.bbtec.net [126.126.163.36]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id x0PG26Rv055723 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Sat, 26 Jan 2019 01:02:06 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: possible deadlock in __do_page_fault To: Joel Fernandes Cc: Andrew Morton , Todd Kjos , syzbot+a76129f18c89f3e2ddd4@syzkaller.appspotmail.com, ak@linux.intel.com, Johannes Weiner , jack@suse.cz, jrdr.linux@gmail.com, LKML , linux-mm@kvack.org, mawilcox@microsoft.com, mgorman@techsingularity.net, syzkaller-bugs@googlegroups.com, =?UTF-8?Q?Arve_Hj=c3=b8nnev=c3=a5g?= , Todd Kjos , Martijn Coenen , Greg Kroah-Hartman References: <201901230201.x0N214eq043832@www262.sakura.ne.jp> <20190123155751.GA168927@google.com> <201901240152.x0O1qUUU069046@www262.sakura.ne.jp> <20190124134646.GA53008@google.com> From: Tetsuo Handa Message-ID: Date: Sat, 26 Jan 2019 01:02:06 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190124134646.GA53008@google.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/01/24 22:46, Joel Fernandes wrote: > On Thu, Jan 24, 2019 at 10:52:30AM +0900, Tetsuo Handa wrote: >> Joel Fernandes wrote: >>>> Anyway, I need your checks regarding whether this approach is waiting for >>>> completion at all locations which need to wait for completion. >>> >>> I think you are waiting in unwanted locations. The only location you need to >>> wait in is ashmem_pin_unpin. >>> >>> So, to my eyes all that is needed to fix this bug is: >>> >>> 1. Delete the range from the ashmem_lru_list >>> 2. Release the ashmem_mutex >>> 3. fallocate the range. >>> 4. Do the completion so that any waiting pin/unpin can proceed. >>> >>> Could you clarify why you feel you need to wait for completion at those other >>> locations? OK. Here is an updated patch. Passed syzbot's best-effort testing using reproducers on all three reports. From f192176dbee54075d41249e9f22918c32cb4d4fc Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Fri, 25 Jan 2019 23:43:01 +0900 Subject: [PATCH] staging: android: ashmem: Don't call fallocate() with ashmem_mutex held. syzbot is hitting lockdep warnings [1][2][3]. This patch tries to fix the warning by eliminating ashmem_shrink_scan() => {shmem|vfs}_fallocate() sequence. [1] https://syzkaller.appspot.com/bug?id=87c399f6fa6955006080b24142e2ce7680295ad4 [2] https://syzkaller.appspot.com/bug?id=7ebea492de7521048355fc84210220e1038a7908 [3] https://syzkaller.appspot.com/bug?id=e02419c12131c24e2a957ea050c2ab6dcbbc3270 Reported-by: syzbot Reported-by: syzbot Reported-by: syzbot Signed-off-by: Tetsuo Handa --- drivers/staging/android/ashmem.c | 23 ++++++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c index 90a8a9f..d40c1d2 100644 --- a/drivers/staging/android/ashmem.c +++ b/drivers/staging/android/ashmem.c @@ -75,6 +75,9 @@ struct ashmem_range { /* LRU list of unpinned pages, protected by ashmem_mutex */ static LIST_HEAD(ashmem_lru_list); +static atomic_t ashmem_shrink_inflight = ATOMIC_INIT(0); +static DECLARE_WAIT_QUEUE_HEAD(ashmem_shrink_wait); + /* * long lru_count - The count of pages on our LRU list. * @@ -438,7 +441,6 @@ static int ashmem_mmap(struct file *file, struct vm_area_struct *vma) static unsigned long ashmem_shrink_scan(struct shrinker *shrink, struct shrink_control *sc) { - struct ashmem_range *range, *next; unsigned long freed = 0; /* We might recurse into filesystem code, so bail out if necessary */ @@ -448,17 +450,27 @@ static int ashmem_mmap(struct file *file, struct vm_area_struct *vma) if (!mutex_trylock(&ashmem_mutex)) return -1; - list_for_each_entry_safe(range, next, &ashmem_lru_list, lru) { + while (!list_empty(&ashmem_lru_list)) { + struct ashmem_range *range = + list_first_entry(&ashmem_lru_list, typeof(*range), lru); loff_t start = range->pgstart * PAGE_SIZE; loff_t end = (range->pgend + 1) * PAGE_SIZE; + struct file *f = range->asma->file; - range->asma->file->f_op->fallocate(range->asma->file, - FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, - start, end - start); + get_file(f); + atomic_inc(&ashmem_shrink_inflight); range->purged = ASHMEM_WAS_PURGED; lru_del(range); freed += range_size(range); + mutex_unlock(&ashmem_mutex); + f->f_op->fallocate(f, + FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, + start, end - start); + fput(f); + if (atomic_dec_and_test(&ashmem_shrink_inflight)) + wake_up_all(&ashmem_shrink_wait); + mutex_lock(&ashmem_mutex); if (--sc->nr_to_scan <= 0) break; } @@ -713,6 +725,7 @@ static int ashmem_pin_unpin(struct ashmem_area *asma, unsigned long cmd, return -EFAULT; mutex_lock(&ashmem_mutex); + wait_event(ashmem_shrink_wait, !atomic_read(&ashmem_shrink_inflight)); if (!asma->file) goto out_unlock; -- 1.8.3.1