All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG] wait_for_devfsd_finished deadlock
Date: Sat, 1 Dec 2001 19:11:13 -0800	[thread overview]
Message-ID: <20011201191113.A1034@holomorphy.com> (raw)

While testing 2.4.17-pre1 with some other patches, a situation
reminiscent of a deadlock arose. mutt(1) would block indefinitely
while opening a large mbox, and all further calls to sys_open()
would block indefinitely.

After some further testing to isolate the problem, I reproduced
this behavior in the vanilla 2.4.17-pre1 kernel. The sysrq output showed
a number of processes with the following call trace in the devfs core:


Dec  1 17:29:26 holomorphy kernel: sh            D C02A2A00     0   821    806  
                   (NOTLB)
Dec  1 17:29:26 holomorphy kernel: Call Trace: [wait_for_devfsd_finished+170/208
] [devfs_d_revalidate_wait+135/160] [devfs_lookup+409/448] [d_alloc+27/400] [rea
l_lookup+83/192] 
Dec  1 17:29:26 holomorphy kernel:    [link_path_walk+1310/1888] [path_walk+26/3
2] [open_namei+131/1488] [filp_open+59/96] [sys_open+56/192] [system_call+51/56]


And the following call traces elsewhere:


Dec  1 17:29:26 holomorphy kernel: cron          S E3540000     0   852    633  
 853     855   827 (NOTLB)
Dec  1 17:29:26 holomorphy kernel: Call Trace: [pipe_wait+124/176] [pipe_read+17
9/512] [sys_read+150/208] [system_call+51/56] 


Dec  1 17:29:26 holomorphy kernel: procmail      S E2395ED8     0   881    880  
         882       (NOTLB)
Dec  1 17:29:26 holomorphy kernel: Call Trace: [interruptible_sleep_on_locked+11
6/192] [locks_block_on+28/48] [posix_lock_file+178/1232] [fcntl_setlk+335/512] [
do_fcntl+318/512] 


Dec  1 17:29:26 holomorphy kernel: exim          S 00000000     0   905    899  
 907               (NOTLB)
Dec  1 17:29:26 holomorphy kernel: Call Trace: [sys_wait4+862/912] [system_call+
51/56] 

 

Further diagnostic information is available upon request.

Mr. Gooch, your attention to this matter is much appreciated.



Thanks,
Bill

             reply	other threads:[~2001-12-02  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02  3:11 William Lee Irwin III [this message]
2001-12-02 19:01 ` [BUG] wait_for_devfsd_finished deadlock Richard Gooch
2001-12-03  1:34   ` William Lee Irwin III
2001-12-03  1:44     ` Richard Gooch
2001-12-04  5:04 ` Richard Gooch

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=20011201191113.A1034@holomorphy.com \
    --to=wli@holomorphy.com \
    --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.