linux-kernel - Re: [patch] fix 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091017204608.GA5676@suse.de>
Date:	Sat, 17 Oct 2009 13:46:08 -0700
From:	Greg KH <gregkh@...e.de>
To:	Stas Sergeev <stsp@...et.ru>
Cc:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] fix driver_register() return value

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@...et.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
--
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/