From: Olaf Hering <olh@suse.de>
To: autofs@linux.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: race in autofs / nfs
Date: Sun, 11 Feb 2001 21:17:01 +0100 [thread overview]
Message-ID: <20010211211701.A7592@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
Hi,
there is a race in 2.4.1 and 2.4.2-pre3 in autofs/nfs.
When the cwd is on the nfs mounted server (== busy) and you try to
reboot the shutdown hangs in "rcautofs stop". I can reproduce it everytime.
I attach a screen log and a decoded sysrq output. It is not related to
that killproc, it hangs right now in automount <-> kupdate (with kernel
2.4.1):
kupdate 6 0 0 -1 ?00000000 c307a000 0 current
automoun 1525 31480 503680 54 u0176a368 df3e6000 1 current
there is a spinlock message:
_spin_lock(c021f6e4) CPU#1 NIP c01b8220 holder: cpu 1 pc E126BF28
c021f6e4 is not in the System.map, but c01b8220 is
c01b817c T memparse
c01b8200 T atomic_dec_and_lock
c01b9a5c t cleanup_proc_rtas
The attached log is kernel 2.4.2-pre3.
killproc 1701 1030738 16491808 106 u0178d5c8 c7de6000 0 current
automoun 1705 1036120 16577920 54 u0176a368 c7b46000 1 current
_spin_lock(c022279c) CPU#1 NIP c01b7c5c holder: cpu 1 pc E126BF28
SysRq: Emergency Sync
_spin_lock(c022279c) CPU#0 NIP c005d920 holder: cpu 1 pc E126BF28
_spin_lock(c022279c) CPU#1 NIP c01b7c5c holder: cpu 1 pc E126BF28
c01b7c5c is again atomic_dec_and_lock and c005d920 is d_lookup.
The system is a 2way RS/6000, 2gig ram.
Linux cantaloupe 2.4.1-SMP #1 SMP Sun Feb 11 13:02:05 GMT 2001 ppc
unknown
Kernel modules 2.4.1
Gnu C 2.95.2
Gnu Make 3.79.1
Binutils 2.10.0.33
Linux C Library x 1 root root 1499361 Feb 9 02:50
/lib/libc.so.6
Dynamic linker ldd (GNU libc) 2.2
Procps 2.0.7
Mount 2.10q
Net-tools 1.57
Kbd 1.02
Sh-utils 2.0
Modules Loaded nfsd autofs4 ipv6
Any ideas what could be wrong?
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
[-- Attachment #2: screenlog.0.crash.gz --]
[-- Type: application/x-gunzip, Size: 8680 bytes --]
[-- Attachment #3: blah.txt.gz --]
[-- Type: application/x-gunzip, Size: 1358 bytes --]
next reply other threads:[~2001-02-11 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 20:17 Olaf Hering [this message]
2001-02-11 20:31 ` race in autofs / nfs H. Peter Anvin
2001-02-12 8:57 ` Trond Myklebust
2001-02-12 9:35 ` Olaf Hering
2001-02-12 10:14 ` Olaf Hering
2001-02-12 11:51 ` Olaf Hering
2001-02-12 17:38 ` H. Peter Anvin
2001-02-12 17:48 ` Olaf Hering
2001-02-13 15:58 ` Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010211211701.A7592@suse.de \
--to=olh@suse.de \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.