linux-kernel - Re: spi_topcliff

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]

Date:	Wed, 2 Mar 2011 15:07:56 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Tomoya MORINAGA <morinaga526@....okisemi.com>
Cc:	'David Brownell' <dbrownell@...rs.sourceforge.net>,
	spi-devel-general@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, qi.wang@...el.com,
	yong.y.wang@...el.com, joel.clark@...el.com,
	kok.howg.ewe@...el.com,
	Toshiharu Okada <toshiharu-linux@....okisemi.com>
Subject: Re: spi_topcliff_pch: reload issue

On Tue, Feb 22, 2011 at 10:22:11AM +0900, Tomoya MORINAGA wrote:
> Hi,
> 
> issue: after reload the spi module, it can't do SPI communication.
> 
> We have faced issue when execute the following command.
> insmod xxx.ko(Then, /dev/spidev0.0 is created with success)
> rmmod xxx.ko (Then, /dev/spidev0.0 is deleted with success)
> insmod xxx.ko(Then, /dev/spidev0.0 is created, however, below error message is showed)
> 
>   0000:02:0c.1: registered master spi0
>   0000:02:0c.1: chipselect 0 already in use
>   0000:02:0c.1: can't create new device for spidev
> 
> Do you have any information about the above ?

Nope, I'm not an expert on that driver, but it definitely looks like a
bug!  :-)  It *looks* like the spi_device slaves are not getting unregistered
when the driver unloads.  That's where I would start investigating.
The bug could either be in core code or the device driver itself, but
I don't know without digging deeper.

g.
--
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/