linux-kernel - Re: [PATCH 2/2] - SH/Dreamcast

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: <20080206230127.GA9614@kroah.com>
Date:	Wed, 6 Feb 2008 15:01:27 -0800
From:	Greg KH <greg@...ah.com>
To:	Adrian McMenamin <adrian@...golddream.dyndns.info>
Cc:	Paul Mundt <lethal@...rs.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-sh <linux-sh@...r.kernel.org>
Subject: Re: [PATCH 2/2] - SH/Dreamcast - fix maple bus bugs

On Wed, Feb 06, 2008 at 10:53:51PM +0000, Adrian McMenamin wrote:
> -	dev->function = function;
> -	dev->dev.bus = &maple_bus_type;
> -	dev->dev.parent = &maple_bus;
> -	dev->dev.release = &maple_release_device;
> -	retval = device_register(&dev->dev);
> -	if (retval) {
> -		printk(KERN_INFO
> -		       "Maple bus: Attempt to register device (%x, %x) failed.\n",
> -		       dev->port, dev->unit);
> -		maple_free_dev(dev);
> +	mdev->function = function;
> +	mdev->dev.release = &maple_release_device;
> +	if (mdev->registered == 0) {
> +		retval = device_register(&mdev->dev);
> +		if (retval) {
> +			printk(KERN_INFO
> +			"Maple bus: Attempt to register device"
> +			" (%x, %x) failed.\n",
> +			mdev->port, mdev->unit);
> +			maple_free_dev(mdev);
> +			mdev = NULL;
> +			return;
> +		}
> +		mdev->registered = 1;
>  	}
> -	dev->registered = 1;

I think you are still papering over the real problem here of trying to
register a device twice.  That's something you should never be doing,
and your bus walking logic must be incorrect...

thanks,

greg k-h
--
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/