linux-kernel - Re: 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <201302121138.48288.arnd@arndb.de>
Date:	Tue, 12 Feb 2013 11:38:48 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Alexander Shiyan <shc_work@...l.ru>
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: Re[2]: [PATCH v2 1/3] mfd: syscon: Removed support for unloading

On Tuesday 12 February 2013, Alexander Shiyan wrote:
> > 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.

Ah, the driver is actually "bool" in Kconfig rather than "tristate", so
it is not possible to build it as a module. Makes sense then, and if 
we ever want to turn this into a module, we can still revert your patch.

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