linux-kernel - Re: [PATCH] drivers/base: error handling fixes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061004164413.3352df7d@gondolin.boeblingen.de.ibm.com>
Date:	Wed, 4 Oct 2006 16:44:13 +0200
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Greg KH <greg@...ah.com>, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drivers/base: error handling fixes

On Wed, 4 Oct 2006 09:05:54 -0400,
Jeff Garzik <jeff@...zik.org> wrote:

> drivers/base/class:
> - class_device_rename(): function basically shat itself if anything
>   failed, leaving things in an indeterminant state.  If kmalloc() ever
>   failed, it would dereference ERR_PTR(-ENOMEM).  Fix a bunch of bugs,
>   over and above sysfs_create_link() error handling.
> 
> - class_device_add(): add missing sysfs_remove_link() [fix leak] to error path
> - class_device_add(): handle sysfs_create_link() failure
> 
> drivers/base/dmapool:
> - kmalloc() takes a GFP_xxx argument
> - handle device_create_file() failure
> 
> drivers/base/platform:
> - properly handle errors (fix leak-on-err) in platform_bus_init()
> 
> drivers/base/topology:
> - return sysfs error via NOTIFY_BAD

Hm, I already did fixes for some of these which are in -mm / in Greg's
tree. It would perhaps make sense if you rediffed against one of those
trees.

Cornelia
-
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/