Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp991653ybh; Tue, 21 Jul 2020 12:59:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyI5izB6FhhWUKB6xOm0KnBAzGOpkahHTLPde29lVcPHMeBrt6Qzu23hA1RTHfWMwkglsuJ X-Received: by 2002:a17:906:1a54:: with SMTP id j20mr26402496ejf.455.1595361573232; Tue, 21 Jul 2020 12:59:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595361573; cv=none; d=google.com; s=arc-20160816; b=l9ErbamFcsLzjRI5unlR3kszJCIs3on9H6ksI5nd81PIYn5sZjxOvgOEn5DC7uoP7X 30d/Qmgi+2gcAfbgV8skqaR/3FhsLq+C+IDo+Ht+9sCdqtiK/qXT3NzBq9WeaXkm79TZ TGCRbCcfGSg0CpeTOz4Rc4RPH78u3cx65Jf2EE8dKVk55kyqQNwnMvTX90VM4kZCZ/xY 6t5g/uya4xrptB5CiD7bt7yI84dpJkSfWRxUmN8CYQwu9+RWzZa3ky66y7lWJNDrvXcX BnRWTsskdlV5nKJY4/sTtHqH55dznJIFAvy0DWlcgQTl0DKK5+O5kLAT3uOK1T107cuD U0IA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=AqPj1xBhDhu20FWDwJyJBEuqNaNWXORj4eQ/tBPqOlo=; b=jwxQeeNStViPxgrMkKN3ugEsbcify8rX73AcMf7ULQntwSSFDvSGdU30VNojuyCYqD 6IVdMJD7sHl8TyeGT9zZo+Rt84z5SIgmK8nHF1MN623uUi565XfEbYnWqjV5XBAJyKas NEwICWQm0b98HaWrE0rN3E5OuYpZTQUDfhMgJ6t4jYu92q0188lBC63iAISc8Z3w2lVN ozIKNBmIbKQwqllwGvUFfl9s452fgCEQlieGWEN2+sK40JxieicTpYFO0RhMqK5EbqLw 6gIMcpcE0fwwQCVfFt0AzRaD8ku4W6BEFGwfR4Ddi4OScMFmTLY6RrKUvY+1KLsFy0Qe tfpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@anarazel.de header.s=fm2 header.b=fimQshPg; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="K/5IJJUr"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a19si13132265edt.160.2020.07.21.12.59.10; Tue, 21 Jul 2020 12:59:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@anarazel.de header.s=fm2 header.b=fimQshPg; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="K/5IJJUr"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731025AbgGUT4H (ORCPT + 99 others); Tue, 21 Jul 2020 15:56:07 -0400 Received: from wnew3-smtp.messagingengine.com ([64.147.123.17]:44937 "EHLO wnew3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730664AbgGUT4H (ORCPT ); Tue, 21 Jul 2020 15:56:07 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 1D38EB24; Tue, 21 Jul 2020 15:56:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 21 Jul 2020 15:56:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=AqPj1xBhDhu20FWDwJyJBEuqNaN WXORj4eQ/tBPqOlo=; b=fimQshPgm3sthCqApa+djmcfCkLSFwHY7QblvbjAlcv fPAeBpiKsqs0mi3QLh/mXmVgdoJGl9yF7GQdobNdc899gi75MM7QXJSWdeGAzP7s pSqG/bclBObeMUkxz/dRBESdzacl39lEoopnuJpHNa6X9FXj5KSV36Yywu6LzFHw 3zpOiEbxa7VY7ly3+0eWQJu/UGasSNqBBg0G6xEinO3fsdd0gj2taDBAEmvjobeS K5vsV8vy83764Ae5qR8ReCf/r3JLq6FCORMmJgZ/60QZzT4RIZEmQ0fN3oZb/CbS N9buoYDtMl3zFfWbIKyZrEurHDEhE/bkHpvmbn4Yutg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=AqPj1x BhDhu20FWDwJyJBEuqNaNWXORj4eQ/tBPqOlo=; b=K/5IJJUrbwW7dfc8maPE+b At1jqzRMcstf7E7PyDytihqi9rgeeXyx3p0UJTKG3eIJTnB02AAm+JC3CkttZ1Nd N5rkxvIOVIKX0sXbOw6Xl0dJ6Si2ntASsU/3OSsxiTrWjuz7m829nn7ktLAS9vJj 1vx11jy/npcDV7Jc2zUTA74XOI1Kmtnw2OEoJCMvdXazgipT2WxsWbJ/ij9/DyHu FIVXQ2b1z72wtETwOJ6brF9P0Z/Q6A/Gve6m0KxtOEyKNilXxL0FjJn1JKD6gl/m d08EhKLjB0eiZWiicGMDLi507bD9Gf4F9WbkBlx52akc8iLr8JJURQhViOaQIvjQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgeejgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghs ucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrfgrth htvghrnhepudekhfekleeugeevteehleffffejgeelueduleeffeeutdelffeujeffhfeu ffdunecukfhppeeijedrudeitddrvddujedrvdehtdenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdgu vg X-ME-Proxy: Received: from intern.anarazel.de (c-67-160-217-250.hsd1.ca.comcast.net [67.160.217.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 655F930600B1; Tue, 21 Jul 2020 15:56:03 -0400 (EDT) Date: Tue, 21 Jul 2020 12:56:02 -0700 From: Andres Freund To: Andy Lutomirski Cc: Jens Axboe , Stefano Garzarella , Christoph Hellwig , Kees Cook , Pavel Begunkov , Miklos Szeredi , Matthew Wilcox , Jann Horn , Christian Brauner , strace-devel@lists.strace.io, io-uring@vger.kernel.org, Linux API , Linux FS Devel , LKML , Michael Kerrisk , Stefan Hajnoczi Subject: Re: strace of io_uring events? Message-ID: <20200721195602.qtncgzddl7y55b6l@alap3.anarazel.de> References: <20200716131404.bnzsaarooumrp3kx@steredhat> <202007160751.ED56C55@keescook> <20200717080157.ezxapv7pscbqykhl@steredhat.lan> <39a3378a-f8f3-6706-98c8-be7017e64ddb@kernel.dk> <65ad6c17-37d0-da30-4121-43554ad8f51f@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 2020-07-21 12:44:09 -0700, Andy Lutomirski wrote: > Can you enlighten me? I don't see any iov_iter_get_pages() calls or > equivalents. If an IO is punted, how does the data end up in the > io_uring_enter() caller's mm? For operations needing that io_op_def.needs_mm is true. Which is checked by io_prep_async_work(), adding the current mm to req. On the wq side io_wq_switch_mm() uses that mm when executing the queue entry. Greetings, Andres Freund