[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b0ec01bc-4cbd-431b-bcdd-084cc14553be@gmail.com>
Date: Fri, 6 Feb 2026 18:01:31 +0000
From: Pavel Begunkov <asml.silence@...il.com>
To: Anuj gupta <anuj1072538@...il.com>
Cc: linux-block@...r.kernel.org, io-uring@...r.kernel.org,
Vishal Verma <vishal1.verma@...el.com>, tushar.gohad@...el.com,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Sumit Semwal <sumit.semwal@...aro.org>,
Christian König <christian.koenig@....com>,
linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-fsdevel@...r.kernel.org, linux-media@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linaro-mm-sig@...ts.linaro.org
Subject: Re: [RFC v2 05/11] block: add infra to handle dmabuf tokens
On 2/6/26 15:08, Anuj gupta wrote:
>> +
>> + dma_fence_init(&fence->base, &blk_mq_dma_fence_ops, &fence->lock,
>> + token->fence_ctx, atomic_inc_return(&token->fence_seq));
>> + spin_lock_init(&fence->lock);
>
> nit lock should be initialized before handing its address to
> dma_fence_init()
Good catch, thanks, I'll apply that and other suggestions. And I still
need to address bits Christoph pointed out during review.
--
Pavel Begunkov
Powered by blists - more mailing lists