Andrew Morton writes:
> On Tue, 6 May 2014 19:31:36 +0200 Oleg Nesterov wrote:
>
>> On 05/06, Kirill Tkhai wrote:
>> >
>> > User may want to prohibit autoloading of some modules,
>> > which happens when someone in kernel calls request_module().
>> >
>> > For comparison, udev considers blacklist
On Tue, 6 May 2014 19:31:36 +0200 Oleg Nesterov wrote:
> On 05/06, Kirill Tkhai wrote:
> >
> > User may want to prohibit autoloading of some modules,
> > which happens when someone in kernel calls request_module().
> >
> > For comparison, udev considers blacklist even if corresponding
> >
On 05/06, Kirill Tkhai wrote:
>
> User may want to prohibit autoloading of some modules,
> which happens when someone in kernel calls request_module().
>
> For comparison, udev considers blacklist even if corresponding
> hardware presents in the system. In-kernel request_module()
> functionality
On Tue, 6 May 2014 19:31:36 +0200 Oleg Nesterov o...@redhat.com wrote:
On 05/06, Kirill Tkhai wrote:
User may want to prohibit autoloading of some modules,
which happens when someone in kernel calls request_module().
For comparison, udev considers blacklist even if corresponding
Andrew Morton a...@linux-foundation.org writes:
On Tue, 6 May 2014 19:31:36 +0200 Oleg Nesterov o...@redhat.com wrote:
On 05/06, Kirill Tkhai wrote:
User may want to prohibit autoloading of some modules,
which happens when someone in kernel calls request_module().
For comparison, udev
On 05/06, Kirill Tkhai wrote:
User may want to prohibit autoloading of some modules,
which happens when someone in kernel calls request_module().
For comparison, udev considers blacklist even if corresponding
hardware presents in the system. In-kernel request_module()
functionality is
6 matches
Mail list logo