Bug#524940: module-init-tools: modprobe starts fork-bombing on executing oss-compat postinst

[Matthew Lockner <mlockner@iastate.edu>]

Marco d'Itri wrote:
> On Apr 21, "Matthew J. Lockner" <mlockner@iastate.edu> wrote:
>
>   
> > I suspect this will be unreproducible since it hasn't been reported yet that
> >     
> I definitely never experienced this on my system.
> Anyway, I have no reason to believe this to be a m-i-t bug.
>   

The strongest evidence is that if I downgrade module-init-tools to the 
prior version and hold the prior version and hold the package, the 
problem goes away.  I'd find the next most likely candidate to be 
oss-compat's postinst script, but downgrading that package does nothing 
if you still have the newest module-init-tools in place.

> Please show the content of /etc/modprobe.d/oss-compat.conf.
> Are you sure that the processes were related to oss-compat? Please find
> out the exact command linux.
>
>   

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 ; : ; }