netdev - Re: CONFIG_KMOD breakage in next 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Aug 2008 03:49:17 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Takashi Iwai <tiwai@...e.de>, linux-next@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Rusty Russell <rusty@...tcorp.com.au>,
	LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
	video4linux-list@...hat.com
Subject: Re: CONFIG_KMOD breakage in next kernel

Hi Johannes,

> > > I found that CONFIG_KMOD was already removed in linux-next tree.
> > > This seems to result in many breakages.  For example, I cannot mount a
> > > FAT device automatically because of failure of automatic loading of
> > > nls modules.
> > > 
> > > My particular problem would be fixed by the patch below, but I found
> > > CONFIG_KMOD is still referred in many places.
> > 
> > I am happy to fix the net/bluetooth/ part, you someone has to put out a
> > guideline how this should be fixed.
> 
> Bluetooth was already part of http://lkml.org/lkml/2008/7/9/144
> 
> Basically, I got rid of CONFIG_KMOD, always enabling it when
> CONFIG_MODULES is defined and making it a dummy no-op inline when not.

I missed the patches, but that happens from time to time. Just looked at
them and they look pretty nice. I like it this way.

Acked-by: Marcel Holtmann <marcel@...tmann.org>

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html