linux-kernel - Q: What will happen if I insmod a new version driver when it has already been statically in kernel?

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: <CAO_0yfNxa9m0BR-MxMezC-CZ8M=JkOmnLrpWyUcti-cT8f3zzA@mail.gmail.com>
Date:	Mon, 27 Aug 2012 18:06:27 +0800
From:	Yang Bai <hamo.by@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Q: What will happen if I insmod a new version driver when it has
 already been statically in kernel?

Hi all,

We have one driver which has been statically compiled into kernel, and
now we want to upgrade it. But we only have a new version module for
this driver. Could I just insmod this module and make the new driver
work?

If so, what happens to the static old one?

If not, Can we upgrade this driver without re-compile the kernel to
make the in-kernel driver out or module?

Thanks,
Yang
--
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/