Bug 101413 - autofs can't shut down
Summary: autofs can't shut down
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: kernel
Version: beta1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
Reported: 2003-07-31 20:02 UTC by Bill Nottingham
Modified: 2015-01-04 22:02 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2004-11-25 08:02:11 UTC

Attachments (Terms of Use)

Description Bill Nottingham 2003-07-31 20:02:28 UTC
Description of problem:

shutdown of autofs hangs; the current pid is 'pidof', stuck in 'R'

Show Regs sez:

Pid/TGid: 1181911819, comm: pidof
EIP: 0060:[<c016b4f6>] CPU:0
EIP is at .text.lock.inode [kernel] 0x167 (
Call trace is:

Seems to happen pretty much every shutdown.

Comment 1 Michael K. Johnson 2003-08-08 20:19:19 UTC
Our only changes to autofs from the base kernel are in the O(1)/nptl patch,
and they involve signal handling.  Have you seen this in the upstream 2.4.21
kernel by any chance?

Comment 2 Bill Nottingham 2003-08-08 21:06:31 UTC
It seems to work in taroon, which is also NPTL.

Comment 3 Brian Brock 2003-10-10 15:28:49 UTC
I'm still seeing this in 2.4.22-1.2087.nptlsmp  on an thlon system.

Comment 4 Michael K. Johnson 2003-10-21 20:19:15 UTC
Ingo, any thoughts?

Comment 5 Chris Ricker 2003-10-22 19:21:37 UTC
I use autofs very extensively for NFS mounts, and I've not been seeing this. All
my severn workstations are single CPU Athlon or mobile Athlon, though

Comment 6 Ingo Molnar 2003-10-27 18:16:59 UTC
hm, it seems to have spinlock deadlocked in some inode.c function called by
proc_pid_make_inode() - possibly new_inode()? This is not something NPTL has
changed or should affect directly.

Comment 7 Ingo Molnar 2003-10-27 18:24:59 UTC
what could bring us forward would be to know what happens on the other CPU which
seems to cause the deadlock of this CPU.

Comment 8 Michael K. Johnson 2003-10-29 17:38:22 UTC
Hmm, I just noticed that I've got an SMP machine running autofs and I can't
reproduce this with recent kernels.  Maybe fixed...

Note You need to log in before you can comment on or make changes to this bug.