linux-kernel - Re: [linuxppc-dev] Unbinding device from a driver

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

Message-ID: <1373326425.8183.184@snotra>
Date:	Mon, 8 Jul 2013 18:33:45 -0500
From:	Scott Wood <scottwood@...escale.com>
To:	Gupta Ruchika-R66431 <R66431@...escale.com>
CC:	"linuxppc-dev@...ux.freescale.net" <linuxppc-dev@...ux.freescale.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [linuxppc-dev] Unbinding device from a driver

On 07/04/2013 05:35:28 AM, Gupta Ruchika-R66431 wrote:
> Hi,
> 
> 
> 
> I am trying to unbind a platform device from a driver. Even when the  
> remove function of the device returns an EBUSY error, the device is  
> unbound from the driver. Is this the right behavior ? Why does kernel  
> forcefully unbind the device even if device remove function returns  
> an error ?

 From looking at the code, it seems it's not allowed for a driver to  
refuse the unbinding.  If you can't unbind yet, you need to block until  
you can (and take measures to ensure that it won't take too long).

I don't know the history of why the remove method can return an error  
even though nothing seems to check it.

> root@...80ds: ls
> 
> bind  ffe301000.jr  ffe302000.jr  ffe303000.jr  ffe304000.jr  uevent   
> unbind
> 
> 
> 
> root@...80ds: echo ffe301000.jr > unbind
> 
> In caam_jr_remove
> 
> caam_jr ffe301000.jr: Device Busy

Is the caam_jr driver printing this, or the device model infrastructure?

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