linux-kernel - Re: [PATCH update] firewire: deadline for PHY config transmission

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: <4863D75F.3000804@s5r6.in-berlin.de>
Date:	Thu, 26 Jun 2008 19:52:31 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	linux1394-devel@...ts.sourceforge.net
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH update] firewire: deadline for PHY config transmission

Stefan Richter wrote:
> +	long timeout = DIV_ROUND_UP(HZ, 10);
...
> +	card->driver->send_request(card, &p->packet);
> +	timeout = wait_for_completion_timeout(&p->done, timeout);
> +	kref_put(&p->kref, phy_packet_release);
>  
> -	card->driver->send_request(card, &p.packet);
> -	wait_for_completion(&p.done);
> +	/* will leak p if the callback is never executed */
> +	WARN_ON(timeout == 0);
>  }

I can easily trigger the WARN_ON with something like "printf 'br 
short\nbr short\nbr short\n' | firecontrol" (repeatedly done) on an 
otherwise well behaving FW323.  I will eventually look into changing the 
phy packet submission once more into something which cannot leak memory.
-- 
Stefan Richter
-=====-==--- -==- ==-=-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/