* [patch] fix driver_register() return value
@ 2009-10-17 20:31 Stas Sergeev
2009-10-17 20:46 ` Greg KH
2009-10-26 23:56 ` patch driver-core-fix-driver_register-return-value.patch added to gregkh-2.6 tree gregkh
0 siblings, 2 replies; 4+ messages in thread
From: Stas Sergeev @ 2009-10-17 20:31 UTC (permalink / raw)
To: Greg KH; +Cc: Linux kernel
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hi Greg.
In this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=16dc42e018c2868211b4928f20a957c0c216126c
the check was added for another
driver to already claim the same
device on the same bus. But the
returned error code was wrong:
to modprobe, the -EEXIST means
that _this_ driver is already
installed. It therefore doesn't
produce the needed error message
when _another_ driver is trying
to register for the same device.
Returning -EBUSY fixes the problem.
Signed-off-by: Stas Sergeev <stsp@aknet.ru>
[-- Attachment #2: drv_busy.diff --]
[-- Type: text/x-patch, Size: 403 bytes --]
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index ed2ebd3..f367885 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -236,7 +236,7 @@ int driver_register(struct device_driver *drv)
put_driver(other);
printk(KERN_ERR "Error: Driver '%s' is already registered, "
"aborting...\n", drv->name);
- return -EEXIST;
+ return -EBUSY;
}
ret = bus_add_driver(drv);
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [patch] fix driver_register() return value
2009-10-17 20:31 [patch] fix driver_register() return value Stas Sergeev
@ 2009-10-17 20:46 ` Greg KH
2009-10-17 21:03 ` Stas Sergeev
2009-10-26 23:56 ` patch driver-core-fix-driver_register-return-value.patch added to gregkh-2.6 tree gregkh
1 sibling, 1 reply; 4+ messages in thread
From: Greg KH @ 2009-10-17 20:46 UTC (permalink / raw)
To: Stas Sergeev; +Cc: Linux kernel
On Sun, Oct 18, 2009 at 12:31:38AM +0400, Stas Sergeev wrote:
> Hi Greg.
>
> In this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=16dc42e018c2868211b4928f20a957c0c216126c
> the check was added for another
> driver to already claim the same
> device on the same bus. But the
> returned error code was wrong:
> to modprobe, the -EEXIST means
> that _this_ driver is already
> installed. It therefore doesn't
> produce the needed error message
> when _another_ driver is trying
> to register for the same device.
> Returning -EBUSY fixes the problem.
>
> Signed-off-by: Stas Sergeev <stsp@aknet.ru>
Does this cause problems with the way things now are? If so, what are
they? Does this change need to be backported to older -stable kernels?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [patch] fix driver_register() return value
2009-10-17 20:46 ` Greg KH
@ 2009-10-17 21:03 ` Stas Sergeev
0 siblings, 0 replies; 4+ messages in thread
From: Stas Sergeev @ 2009-10-17 21:03 UTC (permalink / raw)
To: Greg KH; +Cc: Linux kernel
18.10.2009 00:46, Greg KH wrote:
>> Returning -EBUSY fixes the problem.
>> Signed-off-by: Stas Sergeev<stsp@aknet.ru>
> Does this cause problems with the way things now are? If so, what are
> they?
They are simple.
Suppose the pcspkr driver was loaded
by the udev. Then someone types:
modprobe snd-pcsp
and that doesn't print anything, so
he thinks the snd-pcsp was loaded and
asks me why there is no sound. :)
Only by typing "dmesg" you can see what
actually happened, but it would be better
to have that from modprobe too.
> Does this change need to be backported to older -stable kernels?
I think it can't hurt.
^ permalink raw reply [flat|nested] 4+ messages in thread
* patch driver-core-fix-driver_register-return-value.patch added to gregkh-2.6 tree
2009-10-17 20:31 [patch] fix driver_register() return value Stas Sergeev
2009-10-17 20:46 ` Greg KH
@ 2009-10-26 23:56 ` gregkh
1 sibling, 0 replies; 4+ messages in thread
From: gregkh @ 2009-10-26 23:56 UTC (permalink / raw)
To: stsp, gregkh, linux-kernel, stable
This is a note to let you know that I've just added the patch titled
Subject: Driver core: fix driver_register() return value
to my gregkh-2.6 tree. Its filename is
driver-core-fix-driver_register-return-value.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
>From stsp@aknet.ru Mon Oct 26 16:00:03 2009
From: Stas Sergeev <stsp@aknet.ru>
Date: Sun, 18 Oct 2009 00:31:38 +0400
Subject: Driver core: fix driver_register() return value
To: Greg KH <gregkh@suse.de>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Message-ID: <4ADA29AA.9070907@aknet.ru>
In this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=16dc42e018c2868211b4928f20a957c0c216126c
the check was added for another driver to already claim the same device
on the same bus. But the returned error code was wrong: to modprobe, the
-EEXIST means that _this_ driver is already installed. It therefore
doesn't produce the needed error message when _another_ driver is trying
to register for the same device. Returning -EBUSY fixes the problem.
Signed-off-by: Stas Sergeev <stsp@aknet.ru>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
drivers/base/driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -236,7 +236,7 @@ int driver_register(struct device_driver
put_driver(other);
printk(KERN_ERR "Error: Driver '%s' is already registered, "
"aborting...\n", drv->name);
- return -EEXIST;
+ return -EBUSY;
}
ret = bus_add_driver(drv);
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-10-27 0:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-17 20:31 [patch] fix driver_register() return value Stas Sergeev
2009-10-17 20:46 ` Greg KH
2009-10-17 21:03 ` Stas Sergeev
2009-10-26 23:56 ` patch driver-core-fix-driver_register-return-value.patch added to gregkh-2.6 tree gregkh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox