linux-kernel - [Patch 0/2] Driver core: device_register() and put

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080903182637.50bec6fd@gondolin.boeblingen.de.ibm.com>
Date:	Wed, 3 Sep 2008 18:26:37 +0200
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Greg K-H <greg@...ah.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [Patch 0/2] Driver core: device_register() and put_device()

Hi Greg,

recently I stumbled over a bug in my code where I called kfree() on a
device after device_register() had been called (instead of using
put_device()). This seems to be a trap that is easily hit, so I added
some clarifications to the docbook comments for the device registration
functions. Looking further at the driver core code, I found that
device_create_vargs() contains the same bug.

The patches are on top of the driver core quilt.

[Patch 1/2] Driver core: Clarify device cleanup.
[Patch 2/2] Driver core: Fix cleanup in device_create_vargs().
--
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/