From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] uml-patch-2.4.24-3
Date: Wed, 12 May 2004 18:08:37 -0400 [thread overview]
Message-ID: <200405122208.i4CM8cCe008920@ccure.user-mode-linux.org> (raw)
This patch contains a ton of hostfs/humfs work.
The kernel infrastructure that was in hostfs_kern.c was made asynchronous,
cleaned up, and many bugs fixed. It was also renamed to externfs. The old
hostfs_user.c is now host_fs.c. Previously, there were a number of bugs
conspiring to make hostfs completely synchronous, so you could read a file
in, change it from the host, read it again, and see the new contents. This
is now very likely not to work. If you depend on it, yell, and I'll see how
to get it back. O_SYNC will make writes synchronous, and O_DIRECT (when this
stuff makes it into my 2.6 tree) should do the same for writes, if it can
be invoked from mount for an entire filesystem.
humfs is now able to accept plug-in metadata modules, thanks to Piotr Neuman.
The existing shadow filesystem metadata is now plugged in to this interface,
and lives in meta_fs.c. This will enable all the other metadata backends
that people suggested earlier to be plugged in. Piotr is currently working
on a tdb backend.
There was also a cleanup patch from Paul Wagland.
Everything in arch/um/fs/hostfs is now kernel code, and the USER_* stuff
in the Makefile is now gone.
As for everything else, there were
a fix from Oleg which causes malloc to call vmalloc, which I changed
to check the allocation size and only use vmalloc for large allocations
a fix for a bug in mconsole_interrupt which would crash if it ever saw
an empty to-do list which cleaned up the code
a ethernet ioctl patch from Gerd Knorr
clean-up of the AIO support, which should now build and run on 2.4,
falling back to the IO thread if 2.6 AIO support isn't available
a filehandle abstraction to support reclaiming file descriptors
when we hit the kernel limit
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-05-12 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 22:08 Jeff Dike [this message]
2004-05-12 23:09 ` [uml-devel] uml-patch-2.4.24-3 roland
2004-05-13 0:14 ` Sven 'Darkman' Michels
2004-05-13 0:33 ` roland
2004-05-13 21:01 ` Joe Marzot
2004-05-14 1:43 ` Jeff Dike
2004-05-14 11:50 ` Joe Marzot
2004-05-17 15:37 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts [ was Re: [uml-devel] uml-patch-2.4.24-3] Joe Marzot
2004-05-17 23:50 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts Henrik Nordstrom
2004-05-18 4:54 ` [uml-devel] how to do programming in UML pronoy debnath
2004-05-18 8:07 ` roland
2004-05-18 15:43 ` [uml-devel] 2.4.24-2 UML problems with hostfs ClearCase mounts Joe Marzot
2004-05-18 16:26 ` Henrik Nordstrom
2004-05-18 17:54 ` Jeff Dike
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=200405122208.i4CM8cCe008920@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.