Hi,
After a bit of further investigation, I can now repeatedly oops 2.0.29 by
doing the following:
smbmount //<some-host>/<something> <mount-point> -s <something> -n
where <some-host> is a valid hostname which is not responding to internet
traffic - I tested it with a switched off pc in my lab.
If you press ctrl-c to get out of it within a short time, then nothing too
bad happens - you just get the message:
smb_dont_catch_keep_alive: server->data_ready==NULL
If however you let it wait for a bit longer trying to connect, and then
press ctrl-c, the oops always happens. After this I have to power cycle to
get the machine running again - init is in the 'D' state, probably waiting
on a hung sync() after ctrl-alt-del is pressed.
Maybe there should be a time-out in the smbfs code. During the stalled
smbmount call, I also noticed that bdflush was in the 'D' state - could
the oops time-dependence be related to bdflush interval?
Chris.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2i
Comment: PGP Signed with PineSign 2.0
iQCVAwUBMwJRCGZVEN0KDxVBAQHTbgQAgxQ9gSiaVBSVwUr63fIUbwrs88DIonJN
iy42anwOZ38AB4HWNZ+TRgMoFvEFL0nBUtLz0MkWyGmFgBYnhQPXjEIimk5waAW0
me4oUmJ4gpRnMZgOV+NqR/4+q8N5ZGKMXTHj6e+3BRWBXmCQiXQdw54sr9u+3FNl
ELbQNiG1bVY=
=Pe73
-----END PGP SIGNATURE-----