Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4127049ybg; Fri, 25 Oct 2019 13:45:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqwMw6mNCexqIhIsAq3AHG++iHe5Z+QWG922YQbR6pijSNwkIYFwi4l2FxJ719GUTsMu3X38 X-Received: by 2002:a17:906:2319:: with SMTP id l25mr5332840eja.309.1572036341409; Fri, 25 Oct 2019 13:45:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572036341; cv=none; d=google.com; s=arc-20160816; b=v64AYE/rDZ3QMkw/H2UaRs5bOSLix4Nk+vQY6+SPb42DUXSkz1BkbJ0Y7Am2000M86 qCrc3MfdIJe9ZiQfwSGS8WNNo7yBhaYQwu+K3WZyqHX6WOzdQokkfTmJQi9cFox6SyLn k1Xnjai15ZjOk9HpUte1D5TrUuBwH4Ch0Hs+zH5cf3+rQKG96etXxSGzeYo+BgkCgj03 ZyuwIiOndWVa5/Lj88b4TmwEpPGo/LDVje4ddeGMeFvcTDaxAD4Mhm4ufOsYzGV5OEFO I25CaPRYJzwOPgh+vEOTehMjvYm4/5c01UmYsVGblfRd8WY+zd0t7Wm49ptBXk1IXJxr Bo7Q== 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:to:subject:dkim-signature; bh=zm0Wt9tmeF43jjcGuGvd+uwom6rh1GotNz5s3vFhBPs=; b=UzW8NVaHlLmT32MuOGf+gyb2jvRVP7fWgn8YlYkc44AvnXWrdbccP9tYyqtkU+3xbz Sujdw2Y2Mfcaid0bMC4HcvRf/qTpc5kM2eGdtq+SPuVxbLKc8nMMIsgaUrYDDkxYeV6U ptf8x/qfVXTujynbBKW0iTCLJ0Bs/ykCSjr5croG62tc/OCV+NxWuHTdG0kdJvkkwbeK WqmgD5SxiUCmnfWqlCkrU2PGrNG11ysJ0N0w9yfnoqgfG5ZoIuFGcoXx4lPCIGdgG4rS kYGcIGyc93x8flvHQtWF+OHsORl5kyQW7XGOluq0fEa+mWkwb6qSh+rpflL+H9qMXzHg 1TfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=NBn6ptFx; 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 l22si1783630ejr.149.2019.10.25.13.45.17; Fri, 25 Oct 2019 13:45:41 -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=@kernel-dk.20150623.gappssmtp.com header.s=20150623 header.b=NBn6ptFx; 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 S2633142AbfJYQpW (ORCPT + 99 others); Fri, 25 Oct 2019 12:45:22 -0400 Received: from mail-io1-f67.google.com ([209.85.166.67]:38952 "EHLO mail-io1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2633127AbfJYQoi (ORCPT ); Fri, 25 Oct 2019 12:44:38 -0400 Received: by mail-io1-f67.google.com with SMTP id y12so3154101ioa.6 for ; Fri, 25 Oct 2019 09:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=zm0Wt9tmeF43jjcGuGvd+uwom6rh1GotNz5s3vFhBPs=; b=NBn6ptFxLHGd/sb4nsdiAXWE+YmSvdbCPGTI/PAKBsSKnTwSiymObmzbnyL3A7TJqV NFp3ZVVdimCpyFzTaeecq/rw/vKBduQD2qk98uhitEmCbIlbO3LjuoRDlOM8vTDJ5YvF 72farqcKHi4/kAtg/BzgvUNAVqOSL0VwOusCuH7ESgM0/SV0TiT59l6HQI/DJ5t03nM7 tWi3b7QffFY0dtp4A+CgwSamO5p2hJDLwTe7p4JIa70AZTp9PLNk3lJFGYhuLv11eJMh kE5rpedFqhV0yNnJ0KeHxxHkof7cTzcBPVDj9AWcxvM23T4g7aFEz2yBcQNPTuDWwz0d PsAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zm0Wt9tmeF43jjcGuGvd+uwom6rh1GotNz5s3vFhBPs=; b=Csa4xrFds37+YvWnTA+327umsQdjxt5TXXWd6rNUs3gXtylyGwmS6xnSLDVKY6ie23 ko4s3fxcZqUl5uXkZrBIYB5P9JZF0uIf7Y1lxd7KLIbdG26b1ZXsqUtC0rqGiX6UqRWd b4KrNjpPy70HHtqRhBofinyRzxdMWH4sw/ha/MnOHejFRE7Kk7XZA8yDJmVMj+kCqm3a fFBB18GK1xM6guLMVy7731lebEaIpJeFTxHgDyEwhrhimCN0zldygYkh0DNnNW3tHcA9 V+ELQDfm/cS8h5d4mayEs+MQ6XRerwgNxxhhSWXMVbHiMILalEtl599TPMWBsdnfHWSi rzPg== X-Gm-Message-State: APjAAAWIM2/1MRda2GjYUHHOvUlZO5vfwPGFe2I07eeZ2HGasbfbiFB4 +LlRIwVDdFTl6ec4LuQ8PkssrDZzmTLnBg== X-Received: by 2002:a5d:8b10:: with SMTP id k16mr2452894ion.69.1572021877607; Fri, 25 Oct 2019 09:44:37 -0700 (PDT) Received: from [192.168.1.159] ([65.144.74.34]) by smtp.gmail.com with ESMTPSA id r13sm417313ilo.35.2019.10.25.09.44.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Oct 2019 09:44:36 -0700 (PDT) Subject: Re: [BUG] io_uring: defer logic based on shared data To: Pavel Begunkov , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org References: <5badf1c0-9a7d-0950-2943-ff8db33e0929@gmail.com> <96446fe1-4f32-642b-7100-ebfa291d7127@kernel.dk> <31a7765b-bb6d-985a-454d-d998678100d1@gmail.com> From: Jens Axboe Message-ID: Date: Fri, 25 Oct 2019 10:44:35 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <31a7765b-bb6d-985a-454d-d998678100d1@gmail.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 10/25/19 10:40 AM, Pavel Begunkov wrote: > On 25/10/2019 19:32, Jens Axboe wrote: >> On 10/25/19 10:27 AM, Jens Axboe wrote: >>> On 10/25/19 10:21 AM, Pavel Begunkov wrote: >>>> On 25/10/2019 19:03, Jens Axboe wrote: >>>>> On 10/25/19 3:55 AM, Pavel Begunkov wrote: >>>>>> I found 2 problems with __io_sequence_defer(). >>>>>> >>>>>> 1. it uses @sq_dropped, but doesn't consider @cq_overflow >>>>>> 2. @sq_dropped and @cq_overflow are write-shared with userspace, so >>>>>> it can be maliciously changed. >>>>>> >>>>>> see sent liburing test (test/defer *_hung()), which left an unkillable >>>>>> process for me >>>>> >>>>> OK, how about the below. I'll split this in two, as it's really two >>>>> separate fixes. >>>> cached_sq_dropped is good, but I was concerned about cached_cq_overflow. >>>> io_cqring_fill_event() can be called in async, so shouldn't we do some >>>> synchronisation then? >>> >>> We should probably make it an atomic just to be on the safe side, I'll >>> update the series. >> >> Here we go, patch 1: >> >> http://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=f2a241f596ed9e12b7c8f960e79ccda8053ea294 >> >> patch 2: >> >> http://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=b7d0297d2df5bfa0d1ecf9d6c66d23676751ef6a >> > 1. submit rqs (not yet completed) > 2. poll_list is empty, inflight = 0 > 3. async completed and placed into poll_list > > So, poll_list is not empty, but we won't get to polling again. > At least until someone submitted something. But if they are issued, the will sit in ->poll_list as well. That list holds both "submitted, but pending" and completed entries. -- Jens Axboe