linux-kernel - RE: [PATCH v5] ppc44x:PHY fixup for USB on canyonlands board

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: <a00291ed1ff0ac93aa2c24636c068760@mail.gmail.com>
Date:	Mon, 13 Dec 2010 12:47:43 +0530
From:	Rupjyoti Sarmah <rsarmah@....com>
To:	Josh Boyer <jwboyer@...ux.vnet.ibm.com>
Cc:	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org
Subject: RE: [PATCH v5] ppc44x:PHY fixup for USB on canyonlands board

>This can fail if you boot a new kernel on a board with an old FDT that
lacks the gpio node.  Calling of_iomap with a NULL np seems like it would
work without crashing anything, so maybe that's not a huge issue.

>>+	vaddr = of_iomap(np, 0);
>>+	if (!vaddr) {
>>+		printk(KERN_CRIT "Could not get gpio node address\n");
>>+		ret = -ENODEV;
>>+		goto err_bcsr;
>>+	}

>A reference count is leaked for the node in this error case because
of_node_put isn't called for the gpio node.  Also, iounmap is never called
on vaddr.

>>+	/* Disable USB, through the BCSR7 bits */


Thanks for your inputs. I will fix and resubmit.

Regards,
Rup
--
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/