linux-kernel - Re: [PATCH 1/7] ALSA: usb-audio: Add initial driver for TASCAM US-144MKII

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c97b2c44-d03c-40d0-b2a8-e8070320499d@web.de>
Date: Fri, 22 Aug 2025 14:00:22 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Takashi Iwai <tiwai@...e.de>, Šerif Rami
 <ramiserifpersia@...il.com>, linux-sound@...r.kernel.org
Cc: Takashi Iwai <tiwai@...e.com>, LKML <linux-kernel@...r.kernel.org>,
 Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH 1/7] ALSA: usb-audio: Add initial driver for TASCAM
 US-144MKII

…
> > +	char *handshake_buf __free(kfree);
> 
> For the __free(kfree), you'd always need to initialize the variable to
> NULL, i.e.
…

Can another software design option become more attractive?
May the scope be reduced for such a variable (in the implementation of the function “tascam_probe”)?

Regards,
Markus