Hi,
On Tue, Feb 14, 2012 at 7:03 AM, Marco d'Itri <m...@linux.it> wrote:
> Yes, still broken.
>
> ----- Forwarded message from Alban Browaeys <pra...@yahoo.com> -----
>
> From: Alban Browaeys <pra...@yahoo.com>
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> Subject: Bug#659838: kmod: v5 acts like a fork bomb
>
> Package: kmod
> Version: 5-1
> Severity: important
>
> Dear Maintainer,
> The version 5 of kmod forks tenth of time to attempt to load one module.
> Notwithstanding I miss the point (does anything need a module loaded 40 times
> per milliseconds ?)
> it render a box nearly unusable. This is with a custom kernel (I have been
> workign on a few kernel
> patches but currently am on vanilla). Should happens also on debian ones as
> for example loading snd-hda-intel
> trigger the load of snd which loads snd-seq. Here I have no snd-seq-oss (I
> did not build it) so this fork
> forever happens while modprobe snd-seq. But it also happens because
> snd-ioctl32 is not there and
> I have been unable to find this module in the i686 conf. So it might well
> happens to all i386
> users.
I bet you have these rules in your config:
install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe
--quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd_rawmidi /sbin/modprobe --ignore-install snd-rawmidi && {
/sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd_emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && {
/sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
install snd_pcm modprobe --ignore-install snd-pcm $CMDLINE_OPTS && {
modprobe --quiet snd-pcm-oss ; : ; }
install snd_mixer modprobe --ignore-install snd-mixer $CMDLINE_OPTS &&
{ modprobe --quiet snd-mixer-oss ; : ; }
install snd_seq modprobe --ignore-install snd-seq $CMDLINE_OPTS && {
modprobe --quiet snd-seq-midi ; modprobe --quiet snd-seq-oss ; : ; }
Marco, why are you shipping this with alsa? This creates dependency
loops, relying on modules being inserted to be able to break the
loops. It seems very fragile. What are you trying to accomplish with
that config? Looking at
http://packages.debian.org/sid/all/alsa-base/filelist, it seems like
you still have the file where these configs come from. I'm adding
Jordi and Elimar in CC, since they are the package maintainers in
Debian.
>
> Reverting to libkmod1 and kmod 3-1 fixed the issue. I now get "Fatal: Module
> snd-seq-oss" messages but no
> more fork bombs.
In kmod-5 we changed the way we calculate dependencies to be faster,
more reliable and share code between modprobe and libkmod. Sadly as a
result this regression appeared. We also added a testsuite, so if
anyone write a test for this case we can make sure this regression
doesn't appear anymore.
I'll take a look how to fix this up, but please could you drop that
config or explain what are their goals?
Regards
Lucas De Marchi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
