Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3331978ybc; Thu, 21 Nov 2019 06:52:29 -0800 (PST) X-Google-Smtp-Source: APXvYqzuvRSTqc/GUOsapWjl728mL7j+tttxJ1q+bSIhnSQ31BVZa4/9dZUDH4kIPdDptcxGc2Co X-Received: by 2002:a7b:c84b:: with SMTP id c11mr9767988wml.158.1574347949058; Thu, 21 Nov 2019 06:52:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574347949; cv=none; d=google.com; s=arc-20160816; b=GZ2K5YVNTVpHrDbYM/Y54p8wGeZZhUEFcoHTFLXvS4CJsi4Svjo/YaHNTgrr5Qb2eS XeuR+GrvHkjgVWfTyVax4fJz5wnQ+IEqCI+HsZzeJHz6yAfCv92F3FlEd+83vzEPcEeb t7kKz0U0m3y8PFXc0KhiW2Ig7yErvzmZ5vJ3av/fzcxhcbvGUtl1NAzdXFGWSzwhfFsW eXK8fcLWF+o7RdQJ0l3OnsvYlP35fbv6pEn/vss25ShTuBA1J3eMNTM3pnsRyliKzvOW hs7lcussFEPiTL3nCAD5DTMx1oSx68Om+GqG/HCxM4JMxwttrAm7X3zOYi+xFNBDXbsv HmRw== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=vBwingZgYTW82TS3d0tJl0goOomstXZnkfoRxFBHZCI=; b=rAdmwOFrDtm/8ficXOiWGr+twv5I+E1PTe/R/iBTZIM20To0028hTBFISe8eCVDRgJ PJnJbDd6Gx8WC/N2gz6Y7/CUSEs8b1s037SidoLZIBa16SSRu5LSCESLhlfMHcq+O3OD 5nKM8yMogebOGfpkB2CaTHJILaTA+DjA32rSmmiybYE5miuMEV+w5rwTdX3f+IZGhRFm +hxT4lgZsNSqpnUIXjarXko8t4gyoxWFiQagvFvWlBrvaw439bNHgDOACvP4I8cSw/dd 7hAcsITs+qVCp5Hfe7WDqBTNAay777gbXG1/mWlZz+K9kfbkXWNFWdeRhiEv/j3CX6KP sgXg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=WdAFI0OR; 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=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 49si2432385edz.9.2019.11.21.06.52.03; Thu, 21 Nov 2019 06:52:29 -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=@redhat.com header.s=mimecast20190719 header.b=WdAFI0OR; 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=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726905AbfKUOst (ORCPT + 99 others); Thu, 21 Nov 2019 09:48:49 -0500 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:46601 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726379AbfKUOss (ORCPT ); Thu, 21 Nov 2019 09:48:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574347727; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vBwingZgYTW82TS3d0tJl0goOomstXZnkfoRxFBHZCI=; b=WdAFI0ORqDnlMqkMvA2jZd58zx/zDb7fhnRddLjQ2naQajGXv8UCSo+YE2bkHZkxMFDucD +/MsvDsJJXuC93b0K/+/6QQTXZDaN9ciaKV0DPvBC3783/9U4OBzFHpyWb2Bpio2Jez9Yi E4arRkUSST8wDJYV6sZH9lBvvMb49dU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-183-eeECgZNrMhGjSDmNcxSs8g-1; Thu, 21 Nov 2019 09:48:46 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C6B111883524; Thu, 21 Nov 2019 14:48:43 +0000 (UTC) Received: from suzdal.zaitcev.lan (ovpn-117-3.phx2.redhat.com [10.3.117.3]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8B32B60BDA; Thu, 21 Nov 2019 14:48:42 +0000 (UTC) Date: Thu, 21 Nov 2019 08:48:42 -0600 From: Pete Zaitcev To: Alan Stern Cc: syzbot , , , , , , Kernel development list , USB list , , , , zaitcev@redhat.com Subject: Re: possible deadlock in mon_bin_vma_fault Message-ID: <20191121084842.095edf87@suzdal.zaitcev.lan> In-Reply-To: References: <20191120111235.7d306f23@suzdal.zaitcev.lan> Organization: Red Hat, Inc. MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-MC-Unique: eeECgZNrMhGjSDmNcxSs8g-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 20 Nov 2019 13:47:00 -0500 (EST) Alan Stern wrote: > > + if (rp->mmap_active) > > + return -EBUSY; > Like that, yes, but the test has to be made while fetch_lock is held. =20 Certainly, thanks. I was rushing just to add a postscriptum. > Incidentally, the comment for fetch_lock says that it protects b_read=20 > and b_out, but mon_bin_vma_fault doesn't use either of those fields. I probably should change that comment to "protect the integrity of the circular buffer, such as b_out". Anyway... If you are looking at it too, what do you think about not using any locks in mon_bin_vma_fault() at all? Isn't it valid? I think I tried to be "safe", but it only uses things that are constants unless we're opening and closing; a process cannot make page faults unless it has some thing mapped; and that is only possible if device is open and stays open. Can you find a hole in this reasoning? -- Pete