From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8EF72C4363A for ; Fri, 23 Oct 2020 13:23:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2CCE2207FF for ; Fri, 23 Oct 2020 13:23:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kernel-dk.20150623.gappssmtp.com header.i=@kernel-dk.20150623.gappssmtp.com header.b="e7HMtDUx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S373739AbgJWNXU (ORCPT ); Fri, 23 Oct 2020 09:23:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47496 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S373576AbgJWNXT (ORCPT ); Fri, 23 Oct 2020 09:23:19 -0400 Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 29C47C0613D2 for ; Fri, 23 Oct 2020 06:23:19 -0700 (PDT) Received: by mail-io1-xd29.google.com with SMTP id p7so1744414ioo.6 for ; Fri, 23 Oct 2020 06:23:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=iIXXMTAFKEUOXUJ6Hngll7ihraOgdUZlAqeHFDgyY7I=; b=e7HMtDUxozZVnJQN4nwx6gLgKj9Jh+YYtcUP0Pwy2VfGhM4YnjwyEnS1PB21YHuawu fxCMdVoVaM/YqMIwFCLig2gaY+Pq2qeANvbTD6ywLw+6FPpma09F5IIx3ZU0o6dKHO5L 5S90l/cQd207SDdENPR1e05TtRYG0CCtx9Pz5aDD8/nVyOcn99UvLbfr/58K7fOPyLOP 9FnVdvagyDojndRSERh4xujbIa4TAvdYt0Z8dXCqyQ2Ylvk+mJ5anzdGES5/b8r10xX6 ZFX5kfiaxGLUpdQRNX+pMmyUWE286ClMagOhHW6l3bvanVRvZRS/7yfQSpjaaZhzdxjf m3Hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iIXXMTAFKEUOXUJ6Hngll7ihraOgdUZlAqeHFDgyY7I=; b=R65dQ5tm4QbQouWO9YcacWe+2ipFdu3mIFQ5jJAvzbJDPgm05S7iis3EHs6bD5dlz5 Ck6zSZwmBf8Dy9QkmwfVGl42PZWFUlGv+Xn0QhucADt9Zu8eZ4oq+4jMWUfoSTy7cEvs MU8K1fHLkbRToOr4xPrNWf5t3pzGYnCLz2PcRDNK5OiMZjyZaGBnXc6+AjEb8yKo56Zw 1WxPNaOd6wNNZJa7BE1OSi81r1YkvgiGKFpeVfqho6a1NdVCJi1gMb4fzjqr0ei/HRWz Bf1ubC457C4nHkzKhaF2F1UQj2H0B2jxSns0HOmqVQqP5JT9A83HYAs9Zc2uPX98sCzX XnBQ== X-Gm-Message-State: AOAM530YS8S1PDSkvHrq6EIh7g3FM2ykTBxuwywY1VK8qnlt/VfZkLV9 DcWdsg54MBM4+QPpLOzNVluvvg== X-Google-Smtp-Source: ABdhPJy9ZE3R9jmYdEpwid3c9GavbQ0/arGXkTiSPg8hHX1/yxqhlduNTA/d6K6ddXpkttLEEGEtTw== X-Received: by 2002:a05:6602:1216:: with SMTP id y22mr1572155iot.53.1603459398359; Fri, 23 Oct 2020 06:23:18 -0700 (PDT) Received: from [192.168.1.30] ([65.144.74.34]) by smtp.gmail.com with ESMTPSA id c1sm940393ile.0.2020.10.23.06.23.17 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 23 Oct 2020 06:23:17 -0700 (PDT) Subject: Re: [PATCH] io-wq: fix 'task->pi_lock' spin lock protect To: qiang.zhang@windriver.com Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org References: <20201023062003.3353-1-qiang.zhang@windriver.com> From: Jens Axboe Message-ID: <80fa2e28-bbb4-dfa7-7215-c8cea052dca0@kernel.dk> Date: Fri, 23 Oct 2020 07:23:17 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20201023062003.3353-1-qiang.zhang@windriver.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On 10/23/20 12:20 AM, qiang.zhang@windriver.com wrote: > From: Zqiang > > The set CPU affinity func 'do_set_cpus_allowed' may be operate > 'task_rq', need add rq lock protect, replace 'pi_lock' spinlock > protect with task_rq_lock func. Thanks, I'm going to fold this one. -- Jens Axboe