[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d8d4cca1-031f-4ea7-89da-573e0863c3ec@web.de>
Date: Wed, 19 Jun 2024 15:28:43 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Paul Cercueil <paul@...pouillou.net>, Nuno Sá
<nuno.sa@...log.com>, linux-iio@...r.kernel.org, dmaengine@...r.kernel.org,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, Christian König
<christian.koenig@....com>, Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>, Sumit Semwal
<sumit.semwal@...aro.org>, Vinod Koul <vkoul@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
Jonathan Corbet <corbet@....net>, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v11 3/7] iio: core: Add new DMABUF interface
infrastructure
>> …
>>> +++ b/drivers/iio/industrialio-buffer.c
>> …
>>> +static void iio_buffer_dmabuf_release(struct kref *ref)
>>> +{
>> …
>>> + dma_resv_lock(dmabuf->resv, NULL);
>>> + dma_buf_unmap_attachment(attach, priv->sgt, priv->dir);
>>> + dma_resv_unlock(dmabuf->resv);
>> …
>>
>> Under which circumstances will another lock guard become applicable?
>> https://elixir.bootlin.com/linux/v6.10-rc4/source/include/linux/cleanup.h#L179
>
> As soon as "struct dma_resv" gets a DEFINE_GUARD().
Would any contributor like to add a macro call accordingly?
Regards,
Markus
Powered by blists - more mailing lists