From: Juan Quintela <quintela@mandrakesoft.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org,
devfs-announce-list@vindaloo.ras.ucalgary.ca
Subject: Re: [PATCH] devfs v199.8 available
Date: 01 Feb 2002 18:18:18 +0100 [thread overview]
Message-ID: <m2it9h3yud.fsf@localhost.mandrakesoft.com> (raw)
In-Reply-To: <200201210635.g0L6ZjA22202@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201210635.g0L6ZjA22202@vindaloo.ras.ucalgary.ca>
>>>>> "richard" == Richard Gooch <rgooch@ras.ucalgary.ca> writes:
richard> Hi, all. Version 199.8 of my devfs patch is now available from:
richard> http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html
richard> The devfs FAQ is also available here.
richard> Patch directly available from:
richard> ftp://ftp.??.kernel.org/pub/linux/kernel/people/rgooch/v2.4/devfs-patch-current.gz
richard> AND:
richard> ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.4/devfs-patch-current.gz
richard> This is against 2.4.18-pre4. Highlights of this release:
richard> - Fixed deadlock bug in <devfs_d_revalidate_wait>
I still has that bug with 2.4.18-pre7, and it has this patch applied.
stack traces are:
p1:
schedule()
devfs_de_revalidate_wait()
cached_lookup()
lookup_hash()
sys_unlink()
system_call()
p2:
schedule()
wait_for_devfsd_finished()
devfs_lookup(()
lookup_hash()
unix_bind()
sys_bind()
sys_socketcall()
system_call()
the thing that they are tring to create/remove is /dev/log.
And devfsd is already running in that state:
__schedule()
__down()
__down_failed()
__text_lock_namei()
This has worked normally until now, it has beggining to fail yesterday.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
prev parent reply other threads:[~2002-02-01 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 6:35 [PATCH] devfs v199.8 available Richard Gooch
2002-02-01 17:18 ` Juan Quintela [this message]
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=m2it9h3yud.fsf@localhost.mandrakesoft.com \
--to=quintela@mandrakesoft.com \
--cc=devfs-announce-list@vindaloo.ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox