From: "Adam J. Richter" <adam@yggdrasil.com>
To: andrew@walrond.org, linux-kernel@vger.kernel.org
Cc: akpm@digeo.com
Subject: Patch: 2.5.62.4 small devfs
Date: Fri, 28 Feb 2003 14:29:37 -0800 [thread overview]
Message-ID: <200302282229.OAA10670@adam.yggdrasil.com> (raw)
On Fri, 28 Feb 2003, Andrew Walrond wrote:
>[...] I want to give this another whirl, but your latest
>patch doesn't apply cleanly against 2.5.63+ (fs/devfs/base.c fails). Any
>chance of an update?
I have made a new version of my small devfs patch against
linux-2.5.62.bk4. This version fixes a bug where directory->i_sem was
held while devfs_helper ran, which caused deadlock on one system. I
am surprised I had not noticed this problem before. This version also
adds Documentation/filesystems/devfs/small-devfs, describing
differences between the old devfs implementation and this one. You can
retrieve the patch from the following URL.
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/smalldevfs-2.5.62.4-v11.patch
As before, the optional devfs_helper user level program can
be retrived from:
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/devfs_helper-0.2.tar.gz
My "to do" list for small devfs is now as follows.
- Submit a patch to the -mm kernels, as Andrew has been
kind enough to distribute this change in his -mm kernels.
- Remove CONFIG_DEVFS_MOUNT?
- Explore eliminating by fs/devfs/fs.c by extending
dnotify and ramfs slightly.
- Probably request integration after linux-2.7.0.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-02-28 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 22:29 Adam J. Richter [this message]
2003-03-03 16:27 ` Andrew Walrond
[not found] <200303031638.h23GcH131618@gaea.projecticarus.com>
2003-03-03 16:45 ` Andrew Walrond
2003-03-03 18:15 Adam J. Richter
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=200302282229.OAA10670@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=akpm@digeo.com \
--cc=andrew@walrond.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®