adds simple support for atomically-mapped PTEs. On highmem systems this enables the allocation of the pagetables in highmem.

- the new vmalloc_to_page() interface should be used to determine the physical page a given vmalloc() area virtual address is mapped to.

into elte.hu:/home/mingo/BK/mine/linux-2.5

into home.transmeta.com:/home/torvalds/v2.5/linux

This patch (+ BK changeset) converts the meye driver to the new DMA API,
this is necessary for the driver to be used in 2.5. 

Stelian.

ChangeSet@1.332, 2002-02-15 16:35:31+01:00, stelian@popies.net
  Convert to the new DMA API and allocate separate DMA pages instead of one big buffer.

into home.transmeta.com:/home/torvalds/v2.5/linux

Just the usual removal of the dead global arrays and associated cruft.
(Thistime not affecting lvm, which BTW. doesn't compile currently anyway
;-).

The end_request() function familiy (not the global one, but the IDE
specific ones), did bear a permuted parameter ordering.  After fixing
this it turned out that at all places the huk parameter wasn't the
hwgroup, but just the drive in question itself.  I have changed this to
be more sane, which allowed to remove many unneccessary code
duplication, or rather obfuscation, in between the __ide_end_request()
and ide_end_request() functions.  This simplification is actually the
"spreading" part of the game. 

into home.transmeta.com:/home/torvalds/v2.5/linux

A forward-port.  This is the code which prevents ENOSPC
errors from exposing stale data within filesystems.

- in generic_file_write(), if prepare_write() fails, truncate
  the file to drop any part-added blocks.

- in __block_write_full_page(), if we hit an error,  push
  whatever buffers we _have_ mapped into the file out to disk.

- in __block_prepare_write(), if we hit an error, zero out
  any blocks which we did manage to map into the file.  This
  is because the caller won't be doing any writing to those
  blocks due to the error.

A forward port.  At present, msync() does not report errors
from EIO or ENOSPC.  fsync() has the same bug for mapped pages
against the affected fd.

The patch correctly propagates these errors back up from
writepage so that fsync and msync correctly report errors.

It's fairly important - msync is the only way we have
of reporting ENOSPC against sparse mappings.

Of course, you can still silently lose your data if it's kswapd who
gets ENOSPC during writepage.  I have 3/4 of a patch for that.  It
records the data loss so that a later msync() will report the bad
news.

This patch also adds an implementation of msync(MS_ASYNC), because
it was easy.

A forward-port.  ext2, minix and sysv aren't handling directories
correctly when IS_SYNC is in place.  They call waitfor_one_page(),
but forgot to start the I/O.

The patch also moves waitfor_one_page and writeout_one_page
into fs/buffer.c, so mm/filemap.c now does not mention buffer_head
at all.

Here's the x86 BUG() implementation we discussed the other day.

I also have the rework of the header files which avoids
instantiation of strings in headers and saves 100-200k.
However that is only needed for gcc 2.X.  I assume that
by the time 2.6 is in use, gcc-3.x will be the preferred
compiler.

into home.transmeta.com:/home/torvalds/v2.5/linux

Tidyup init/exit for nfsd module

move nfsd_init into an initcall with other module
startup.  This means that "initialized" isn't needed for
any of the files that use it, as the bits are always initialised if
in use.

Cleanup the syscall interface to nfsd

1/ add an "owner" field to the nfsd_linkage structure
2/ grab a reference to that module before calling the syscall
3/ Remove the reference counting from inside the module
4/ Always allow nfsd module to be called, even if compile with
	CONFIG_NFSD == N
   ( but not if CONFIG_MODULES also == N)

Use MKDEV for making device number from components

This patch is thanks to GOTO Masanori <gotom@debian.or.jp>

Tidy up some vfs calls in nfsd

1/ changes to sys_fsync had not also been made to nfsd_sync.
   Now nfsd_sync calls filemap_fdatasync and filemap_fdatawait.
2/ change nfsd_readdir to use vfs_readdir instead of i_op->readdir

Get nfsd_setattr to not put too much weight on inode_change_ok

nfsd_currently calls inode_change_ok and does not try setattr if this fails.
However this is wrong.  If a filesystem defines it's own i_op->setattr, then
it might use a completely different mechanisim for determining what is ok.
nfsd shouldn't assume...

We still use inode_change_ok when normalising NFSv2 "touch" requests, but
only in passing.

Stop fat_fh_to_dentry returning NULL

the fh_to_dentry routines should never return NULL.
The caller expects an ERR_PTR or a valid (possibly negative)
dentry.  fat did the wrong thing and so could oops.

Fix bugs recently introduced into kNFSd

When searching a list.h list, we cannot export
to find NULL at the end.  Instead we return a pointer
when found, or NULL if nothing found.  Same bug, 4 times.

The seq_file improvements to /proc/fs/nfs/exports got the counting
wrong so that some clients would get reported twice, always the last.

	A bunch of places dereferences ->d_parent->d_inode with no
protection whatsoever (e.g. on return from read()).  It's an
SMP race on all boxen and pretty wide UP race if we have dnotify
set on parent (race between read() and rename() and similar beasts).

	Patch below is the first one in a series of ->d_parent-related
fixes.  It adds a helper (dnotify_parent(dentry, event)) and converts
places that did inode_dir_notify(dentry->d_parent->d_inode,...) to it.

	Please, apply.  Notice that problem exists in 2.4 and unlike 2.5
there we can't switch to saner API (basically, reporting file events on
file, not on a parent directory).

Some of the further fixes depend on Pat's and Greg's (driverfs and usbdevfs
resp.) patches, so getting them merged would make life easier.  And yes,
some of further chunks (e.g. smbfs ->revalidate() and friends) will also
have to go into 2.4 - they are independent from any threading projects ;-/

Ugh, another one.  Linus, please apply.

	Robert Love

of double_lock_balance().

into hera.kernel.org:/home/mochel/BK/linux-2.5

old_inode is locked by vfs_link().

BKL shifted into ->symlink() (+ fixes for {ramfs,shmem}_symlink())

BKL shifted into ->link(), check for S_ISDIR moved into vfs_link().

BKL shifted into ->rmdir()

BKL shifted into ->mkdir()

This patch fixes a bug in the Linux process ID allocator.  It isn't quite
SMP safe since it references "last_pid" after releasing the lock protecting
it.  This can result in two processes getting assigned the same process ID.

this is the NeoMagic floating foint removal patch
I posted previously for Linux 2.4.18-pre9-ac3.

Best regards,
  Denis Oliver Kropp