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;
Subject: Re: linux-next: Fixes tag needs some work in the block tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Pavel Begunkov <asml.silence@gmail.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20210220155124.4bffc798@canb.auug.org.au>
From:   Jens Axboe <axboe@kernel.dk>
Message-ID: <cd8430b8-6f82-056a-d9a9-ff04dcf7c749@kernel.dk>
Date:   Fri, 19 Feb 2021 21:57:54 -0700
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: <20210220155124.4bffc798@canb.auug.org.au>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2/19/21 9:51 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   76676c992506 ("io_uring: fix io_rsrc_ref_quiesce races")
> 
> Fixes tag
> 
>   Fixes: 0ce4a72632317 ("io_uring: don't hold uring_lock when calling io_run_task_work*")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: a4f2225d1cb2 ("io_uring: don't hold uring_lock when calling io_run_task_work*")

Fixed it up, thanks Stephen.

-- 
Jens Axboe