Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4332439ybg; Mon, 21 Oct 2019 07:25:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqwYQmjOGO7cjyuKEPc3iDscVxBZGIj+Qh6bckfvrL6xIB7jSdzrZPSvucRKQuv7sguYRECz X-Received: by 2002:a17:906:6451:: with SMTP id l17mr22268544ejn.114.1571667945993; Mon, 21 Oct 2019 07:25:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571667945; cv=none; d=google.com; s=arc-20160816; b=PWQ+mmlxYQHmKRdodS0cDA7j0Z8pVP+4/H8NY5JKSSYovsWRu/W7g2Wz0TgKYPgXXT Q/eCYN+13jNX3zdzCetZlsmSLQusvEUxvSiYTC+rv/j4JtfwJu0RLm/Xjkn7taTCM8Ff WFDe2lkYC5Uf51nuxjwZA7m2gkXPnLoXg0KfDgkPtdOlan9crlQoalaFLEeAytv4CT+u FxnDre08iJdgsvtTfvOQQatilccLnwPjauXF/5uHLWLiTmUX/tFqK0LsaAxJ7V5pdYxh bfdzLz7zcV1FVnjMCCKiQsp/dktETBQwW1/wmiSykl4OrTQdDyPTCvXd1VuSESkjRbSh k99A== 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:message-id:date :content-id:mime-version:subject:cc:to:references:in-reply-to:from :organization:dkim-signature; bh=juvjyDj/bXESr8Pj+8TGvYoxpIfnIpsm8+f+H/8UCWM=; b=W4iou2pt4TrJ51EX6LGOlHRStJ3FzcnGtDQjn+1X2zkgqElq09lVprElF9q6FX1Ct7 /SoHl27zX0K6IpGYmco0Pb61Nm68b5q2WE2oYgNYQ3OMQX9jjjZ+hbWjMC102EOko4Ht P9R4mEhmzPp4s4zd15RhHQYwMIsrtnlE5TZjEExZ75zk4t0IssteQV4mWtsNMzWn3sZX EwxnjEM7PbHExvl9TKF0EuEUWjph1GWiH8ue0+YvicOhnvVlAjAqPJG2j56gnBoS0iGQ pk4Vm1KWsZWu9rsrvyle8prdPAgJlM1LKMM5+SkY37ziDpX9L7ESZQ1rarKB9mefOKFX fK9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AHcdZDYl; 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 v13si9645832eds.375.2019.10.21.07.25.22; Mon, 21 Oct 2019 07:25:45 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AHcdZDYl; 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 S1728826AbfJUOWJ (ORCPT + 99 others); Mon, 21 Oct 2019 10:22:09 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:42300 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727555AbfJUOWJ (ORCPT ); Mon, 21 Oct 2019 10:22:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571667728; 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=juvjyDj/bXESr8Pj+8TGvYoxpIfnIpsm8+f+H/8UCWM=; b=AHcdZDYlTAh1iWhTBQfQix00XLQu6ecluEQNbfPUrlTsVswhQbSKH5iLrIQhL/9QNiE6wz GhZCoOtjDVvbg7MsjcdWWnfiMR1wu/GrKBfPOc3zi4HceHGXWG3k2Fly+wQxVaayKj6iuz q11INVBLyZvgYgUXLpt97J1NIIHA6is= 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-337-C06jtCk6MO2DbhBQzqUQyw-1; Mon, 21 Oct 2019 10:22:07 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BFB4947B; Mon, 21 Oct 2019 14:22:05 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-121-40.rdu2.redhat.com [10.10.121.40]) by smtp.corp.redhat.com (Postfix) with ESMTP id 39B1E5D717; Mon, 21 Oct 2019 14:22:00 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20191018184030.8407-1-crecklin@redhat.com> References: <20191018184030.8407-1-crecklin@redhat.com> To: Chris von Recklinghausen Cc: dhowells@redhat.com, Jarkko Sakkinen , James Morris , "Serge E . Hallyn" , keyrings@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Waiman Long Subject: Re: [PATCH] security/keyring: avoid pagefaults in keyring_read_iterator MIME-Version: 1.0 Content-ID: <30308.1571667719.1@warthog.procyon.org.uk> Date: Mon, 21 Oct 2019 15:21:59 +0100 Message-ID: <30309.1571667719@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: C06jtCk6MO2DbhBQzqUQyw-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 Chris von Recklinghausen wrote: > The put_user call from keyring_read_iterator caused a page fault which > attempts to lock mm->mmap_sem and type->lock_class (key->sem) in the reve= rse > order that keyring_read_iterator did, thus causing the circular locking > dependency. >=20 > Remedy this by using access_ok and __put_user instead of put_user so we'l= l > return an error instead of faulting in the page. I wonder if it's better to create a kernel buffer outside of the lock in keyctl_read_key(). Hmmm... The reason I didn't want to do that is that keyrings have don't have limits on the size. Maybe that's not actually a problem, since 1MiB would be able to hold a list of a quarter of a million keys. David