linux-kernel - Re[2]: [PATCH v2 1/3] mfd: syscon: Removed support for unloading

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1360650935.475602112@f368.mail.ru>
Date:	Tue, 12 Feb 2013 10:35:35 +0400
From:	Alexander Shiyan <shc_work@...l.ru>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org,
	Dong Aisheng <dong.aisheng@...aro.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re[2]: [PATCH v2 1/3] mfd: syscon: Removed support for unloading

Hello.

> On Monday 11 February 2013, Alexander Shiyan wrote:
> > The driver can be used in various subsystems and therefore should not
> > be unloaded when it is defined in the kernel configuration, so remove
> > support for unloading it.
> > 
> > Signed-off-by: Alexander Shiyan <shc_work@...l.ru>
> 
> Can you describe a scenario where that would happen? Normally the
> module should stay pinned as long as any other module refers
> to its exported symbols.

Probably I wrote a bad description.
The driver registered by "postcore_initcall". Therefore, if we unregister the
driver, we have no way to register it back. Fixme please.

---