[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0c85ca7-d8ac-5f9d-2c57-79543c1f9b5d@gmail.com>
Date: Thu, 16 Jan 2020 23:10:37 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Jon Hunter <jonathanh@...dia.com>,
Laxman Dewangan <ldewangan@...dia.com>,
Vinod Koul <vkoul@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Thierry Reding <thierry.reding@...il.com>,
Michał Mirosław <mirq-linux@...e.qmqm.pl>
Cc: dmaengine@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 01/14] dmaengine: tegra-apb: Fix use-after-free
15.01.2020 12:00, Jon Hunter пишет:
>
> On 14/01/2020 20:33, Dmitry Osipenko wrote:
>> 14.01.2020 18:09, Jon Hunter пишет:
>>>
>>> On 12/01/2020 17:29, Dmitry Osipenko wrote:
>>>> I was doing some experiments with I2C and noticed that Tegra APB DMA
>>>> driver crashes sometime after I2C DMA transfer termination. The crash
>>>> happens because tegra_dma_terminate_all() bails out immediately if pending
>>>> list is empty, thus it doesn't release the half-completed descriptors
>>>> which are getting re-used before ISR tasklet kicks-in.
>>>
>>> Can you elaborate a bit more on how these are getting re-used? What is
>>> the sequence of events which results in the panic? I believe that this
>>> was also reported in the past [0] and so I don't doubt there is an issue
>>> here, but would like to completely understand this.
>>>
>>> Thanks!
>>> Jon
>>>
>>> [0] https://lore.kernel.org/patchwork/patch/675349/
>>>
>>
>> In my case it happens in the touchscreen driver during of the
>> touchscreen's interrupt handling (in a threaded IRQ handler) + CPU is
>> under load and there is other interrupts activity. So what happens here
>> is that the TS driver issues one I2C transfer, which fails with
>> (apparently bogus) timeout (because DMA descriptor is completed and
>> removed from the pending list, but tasklet not executed yet), and then
>> TS immediately issues another I2C transfer that re-uses the
>> yet-incompleted descriptor. That's my understanding.
>
> OK, but what is the exact sequence that it allowing it to re-use the
> incompleted descriptor?
TDMA driver DMA Client
1.
dmaengine_prep()
2.
tegra_dma_desc_get()
dma_desc = kzalloc()
...
tegra_dma_prep_slave_sg()
INIT_LIST_HEAD(&dma_desc->tx_list);
INIT_LIST_HEAD(&dma_desc->cb_node);
list_add_tail(sgreq->node,
dma_desc->tx_list)
3.
dma_async_issue_pending()
4.
tegra_dma_tx_submit()
list_splice_tail_init(dma_desc->tx_list,
tdc->pending_sg_req)
5.
tegra_dma_isr()
...
handle_once_dma_done()
...
sgreq = list_first_entry(tdc->pending_sg_req)
list_del(sgreq->node);
...
list_add_tail(dma_desc->cb_node,
tdc->cb_desc);
list_add_tail(dma_desc->node,
tdc->free_dma_desc);
...
tasklet_schedule(&tdc->tasklet);
...
6.
timeout
dmaengine_terminate_async()
7.
tegra_dma_terminate_all()
if (list_empty(tdc->pending_sg_req))
return 0;
8.
dmaengine_prep()
9.
tegra_dma_desc_get()
list_for_each_entry(dma_desc,
tdc->free_dma_desc) {
list_del(dma_desc->node);
return dma_desc;
}
...
tegra_dma_prep_slave_sg()
INIT_LIST_HEAD(&dma_desc->tx_list);
INIT_LIST_HEAD(&dma_desc->cb_node);
*** tdc->cb_desc list is wrecked now! ***
list_add_tail(sgreq->node,
dma_desc->tx_list)
...
10.
same actions as in #4 #5 ...
11.
tegra_dma_tasklet()
dma_desc = list_first_entry(tdc->cb_desc)
list_del(dma_desc->cb_node);
eventual woopsie
Powered by blists - more mailing lists