From: "Takashi Sakamoto" <o-takashi@sakamocchi.jp>
To: "Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Thomas Fourier" <fourier.thomas@gmail.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: nosy: Fix dma_free_coherent() size
Date: Fri, 19 Dec 2025 23:16:37 +0900 [thread overview]
Message-ID: <f62dc6e5-12e0-414f-8a7b-0675d95938cb@app.fastmail.com> (raw)
In-Reply-To: <7ffdcfff-0f2f-4563-9051-d398f3c5c6a7@wanadoo.fr>
Hi,
I'm sorry to be late for reply, but I'm in travel and could not process the
reviewed patches for my tree. Please wait for the next weekend.
It's our misfortune that Christophe's first proposal has been overlooked.
(The patch was posted before 2023, when I took over the role...)
Let us put it for next merge window to v6.20 kernel.
On Wed, Dec 17, 2025, at 02:47, Christophe JAILLET wrote:
> Le 16/12/2025 à 17:54, Thomas Fourier a écrit :
>> It looks like the buffer allocated and mapped in add_card() is done
>> with size RCV_BUFFER_SIZE which is 16 KB and 4KB.
>>
>> Fixes: 286468210d83 ("firewire: new driver: nosy - IEEE 1394 traffic sniffer")
>> Signed-off-by: Thomas Fourier <fourier.thomas@gmail.com>
>
> Reviewed-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
> And for the records, see [1].
>
> CJ
>
> [1]:
> https://lore.kernel.org/lkml/20200625191554.941614-1-christophe.jaillet@wanadoo.fr/
>
>> ---
>> drivers/firewire/nosy.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/firewire/nosy.c b/drivers/firewire/nosy.c
>> index ea31ac7ac1ca..f562e82e5438 100644
>> --- a/drivers/firewire/nosy.c
>> +++ b/drivers/firewire/nosy.c
>> @@ -494,6 +494,8 @@ irq_handler(int irq, void *device)
>> return IRQ_HANDLED;
>> }
>>
>> +#define RCV_BUFFER_SIZE (16 * 1024)
>
> Maybe this could be moved at the top of the file when #define are
> usually placed.
>
>> +
>> static void
>> remove_card(struct pci_dev *dev)
>> {
>> @@ -517,16 +519,14 @@ remove_card(struct pci_dev *dev)
>> lynx->rcv_start_pcl, lynx->rcv_start_pcl_bus);
>> dma_free_coherent(&lynx->pci_device->dev, sizeof(struct pcl),
>> lynx->rcv_pcl, lynx->rcv_pcl_bus);
>> - dma_free_coherent(&lynx->pci_device->dev, PAGE_SIZE, lynx->rcv_buffer,
>> - lynx->rcv_buffer_bus);
>> + dma_free_coherent(&lynx->pci_device->dev, RCV_BUFFER_SIZE,
>> + lynx->rcv_buffer, lynx->rcv_buffer_bus);
>>
>> iounmap(lynx->registers);
>> pci_disable_device(dev);
>> lynx_put(lynx);
>> }
>>
>> -#define RCV_BUFFER_SIZE (16 * 1024)
>> -
>> static int
>> add_card(struct pci_dev *dev, const struct pci_device_id *unused)
>> {
>> @@ -680,7 +680,7 @@ add_card(struct pci_dev *dev, const struct pci_device_id *unused)
>> dma_free_coherent(&lynx->pci_device->dev, sizeof(struct pcl),
>> lynx->rcv_pcl, lynx->rcv_pcl_bus);
>> if (lynx->rcv_buffer)
>> - dma_free_coherent(&lynx->pci_device->dev, PAGE_SIZE,
>> + dma_free_coherent(&lynx->pci_device->dev, RCV_BUFFER_SIZE,
>> lynx->rcv_buffer, lynx->rcv_buffer_bus);
>> iounmap(lynx->registers);
Cheers
Takashi Sakamoto
next prev parent reply other threads:[~2025-12-19 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 16:54 Thomas Fourier
2025-12-16 17:47 ` Christophe JAILLET
2025-12-19 14:16 ` Takashi Sakamoto [this message]
2025-12-26 13:12 ` Takashi Sakamoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f62dc6e5-12e0-414f-8a7b-0675d95938cb@app.fastmail.com \
--to=o-takashi@sakamocchi.jp \
--cc=christophe.jaillet@wanadoo.fr \
--cc=fourier.thomas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®