cifs causes high system load avg, oopses when unloaded on2.6.0-test11

[Steve French]

>> Using CIFS causes a very high load average (approx. 12 according to
>> After I umout all filesystems (CIFS ones) and then unload the module,
>> it oopses (below).
>> CC me replies if more information is needed.

I don't know if this will fail with the more current (version 0.99 of 
the 2.6 version of the cifs filesystem) which is at
http://us1.samba.org/samba/ftp/cifs-cvs/cifs-0.9.9-2.6kern.tar.gz
but I am trying some experiments today to see if I can reproduce
something similar artificially.  I was concerned about some other oopses
and problems in the tcp reconnection logic that are now fixed but are in
the much older version 0.94 of the cifs vfs in the
linux.bkbits.net/linux-2.5 tree but as 2.6 has been mostly locked down
for weeks - test11 is missing at least a dozen key cifs fixes (including
stress test fixes and fixes for a few oopses reported by 2.6 users
testing more actively over the past couple months), the more recent
fs/cifs files (version 0.9.9) are likely to be much better than what is
in 2.6-test11

(the gz simply contains the contents of the 0.9.9 version of the fs/cifs
directory, rather than a patch (about 15 changesets ahead of 2.6test9,10
or 11).  There are no corequisite fixes outside the directory and it can
be applied to any of the recent 2.6-test* versions)

> Hmm, this unload needs to hand back failure to module unload when it>>
> can't nuke inodes etc. I'd suggest not using it as a module for the
> time being.

I don't see how I could pass failure back on module unload even if I
could detect problems freeing the memory associated with cifs's inode
cache - there is no place for return code info - see the caller ie the
call to mod->exit() in sys_delete_module (about line 735 of
kernel/module.c)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/