The utime and utimes should do exactly the smae permission check
according to SUSv3.
	"The effective user ID of the process shall match the owner of the file,
or has write access to the file or appropriate privileges to use this call
in this manner."

utimes when passed a NULL second argument would fail on a read only
file even if the file is owned by the caller.

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

The following comes from James Bottemley, as he updated the SCSI layer
to use the generic tagging.

Basically just put blk_queue_tag_request() into ll_rw_blk.c and name it
something more sane, blk_queue_find_tag(). In addition, remove REQ_CMD
requirement in blk_queue_start_tag() -- this is actually IDE specific
(we can only tag read/write requests there...), SCSI actually requires
everything to be tagged once enabled. It's replaced with a safety check
for an already tagged request.

This is a merge of the two things that are needed for the plugging as it
stands in 2.5.21. The first is fixing the locking to be both clearer and
safe (Andrew repeatedly broke the old version). The second is a few
changes that allow make_request_fn drivers to utilize plugging. This is
needed for umem and raid, for instance, that have their private
plugging.

Silly oversight - read_pages needs to pass the file *
down to ->readpage().

- If we're PF_MEMALLOC and BIO allocation failed, fall back to try
  to allocate a smaller BIO (from a different mempool)

- When writepages() gets confused, call a_ops->writepage()
  instead of going directly to block_write_full_page().  It
  gives the fs more flexibility, and XFS may want this.

It will need swapops.h for swp_entry().

Fix the order of inodes being marked dirty in a couple of corner cases.

The only impact of this bug is that the on-disk copies of i_version
might got out of sync for a directory, or that an error inserting an
inode into a directory might leave its i_nlinks incorrect on disk for a
short interval.  Neither problem will cause trouble for ext3 during
normal operation, but the nlink problem might cause e2fsck to emit
unnecessary warnings if we crash while the incorrect version of the
inode is in the journal.

Removes the put_iode optimisation.  It's racy, as
Chris pointed out.

ext3 will remount the fs readonly if it runs out of inode
space.  It shouldn't do that - it should just return -ENOSPC.

Cset exclude: bcrl@redhat.com|ChangeSet|20020429021546|12619

This allows compilation without ACPI_DEBUG defined.

This adds an export so that processor.o and thermal.o can be compiled as
modules

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

A couple of targets were still in the main part of the Makefile,
even though they did not need .config to exist for execution.

Move them into the noconfig section of the Makefile, allowing them
to be executed before make *config.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

Unreversed allocations on the error path and the like.

 - Inline locks_notify_blocked.
 - Remove a couple of now-bogus comments.
 - Remove the obsolete F_SHLCK and F_EXLCK cases.
 - Remove the last remaining reference to FL_BROKEN.

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make

Contributed by Greg Banks.

amd7930_fn.h defined a static array, which however was only used in
one of the files which include amd7930_fn.h. So move the array to the
file where it is actually referenced.

While we're at it, do some more cleanup like removing the #defines
for BYTE,WORD and use u16,u8 instead - WORD was even wrongly defined
to unsigned int. Also, convert some macros to inlines etc.

The eicon header defined macros for byte, word, dword. Apart from that
not being a good idea in general, it did clash with the use of a parameter
called "word" in asm/signal.h. At some other place in the Eicon headers, 
there are also typedefs for these types, so the macros can simply go away.

The always-appreciated Stanford Checker found a memory leak in
net/socket.c :: sock_fasync.  It was a bit tricky since the memory was
only conditionally allocated, so must only conditionally be freed.

	This patch  fixes the Compaq WL210 problems I've been having.

The symptoms were that no interupts were ever received from the card;
the BIOS reported it had assigned INTA to IRQ 10; but the yenta
driver reported IRQ 17.

The fix is not to rely on the BIOS's initialisation of interrupt
routing in the TI1410, but to do it explicitly.

This may break laptops that actually use the parallel ISA IRQ
mechanism.

on non-x86 architectures)

in structures and unions (and why not other variables too..)

Many old ISA drivers are not 64bit clean. To avoid dealing with them on
x86-64 I guarded them with CONFIG_ISA. This is also helpful for other
archs (including modern x86) that do not have ISA slots anymore.
The patch has been reviewed by Linux-Kernel, with some additional
cleanups by me. It misses some directories like ISDN or sound drivers.

This fixes a potential security issue on i386. FXRSTOR raises an #GP
when the MXCSR field in the FXSAVE frame contains illegal values. By
putting an signal frame just at a border to an unmapped page a malicious
user could potentially cause an exception in the context switch using this.
When the EFAULT occurs in the last bytes of the signal frame the MXCSR
check would be skipped in the old code, but the rogue value would be already
in task_struct, causing problems later.

Here is the minimal fix for this.

Originally discovered by Andrea while doing x86-64 work. It was fixed in
a different way a bit more intrusive way on x86-64 - all FXRSTOR in the
kernel are guarded by exception handlers.

It's nearly impossible to get the correct CPU names for AMD CPUs in
the MP table (would need BIOS calls etc.). The decoding of CPU names form
the mptable doesn't look too useful anyways, because the correct CPU name
from CPUID is printed only a few lines later. This patch just removes
the name table and replaces it with a printout of the hex value.
This mirrors a change in x86-64

Remove myself as networking maintainer. I haven't done much for networking
for a long time and it doesn't look likely it'll change anytime soon.
Also David/Alexey are doing a fine job without me.

Here is the big 2.5.21 x86-64 sync patch. It only touches arch/x86_64
and include/asm-x86_64. It requires a few other changes that I'm sending
in separate mail.

Changes:
- merge wit 2.5.21
- merge from 2.5.21/i386 (new PCI code, new LDT code etc.)
- sync with 2.4-x86_64 tree.
- minor updates to 32bit emulation
- better early console; including serial support.
- now set up dummy PDA for booting to avoid problems
- Fix GS reloading in context switch one instruction race
- Remove hardcoded names from mpparse code
- Fix inline assembly for RAID-5 xor (similar change needed for i386)
- Real per cpu data support based on PDA field
- Cleanup of offset.c generation requested by Kai: it only puts structure
  offsets into offset.h now.
- Fix i387 fxsave signal frame problems.
- Add uname emulation via personality ("linux32")
- New SSE optimized checksum-copy, copy*user, memcpy, clear_page, copy_page
  functions. Other tunings/cleanups in checksum and other user memory
  access function.
- check if exception table is really sorted
- Cleanups in page table handling in preparation of non executable pages
  support.
- Cleanup PDA access to not require offset.h (thanks to kai for kicking me
  to this)
- use long long for u64/s64 to avoid more warnings
- remove CONFIG_ISA
- fix various bugs and other cleanups