Hi!

Since the introduction of USER_HZ the SG_[GS]ET_TIMEOUT ioctls may have
a serious BUG as userspace uses a different HZ from the HZ in kernelspace.

In x86 HZ=1000 and USER_HZ=100, resulting in confusing timouts as the
kernel measures time 10 times as fast as userspace.

This patch is an attempt to fix this by transforming USER_HZ based timing to
HZ based timing before storing it in timeout. To make sure that SG_GET_TIMEOUT
and SG_SET_TIMEOUT behave consistently a field timeout_user is added which
stores the exact value that's passed by SG_SET_TIMEOUT and it's returned on
SG_GET_TIMEOUT.

Rolf Fokkens
fokkensr@fokkensr.vertis.nl

P.S. this is the second post of this patch

But it's called from scsi_add_lun()->scsi_alloc_sdev() before the type
is known.  The type is -1 all the time in scsi_initialise_merge_fn()
and scsi always bounces.

This patch makes it do the right thing - just enable block-highmem for
all scsi devices.

Jens had this to say:

"I guess that block-highmem has been around long enough, that I can
 use the term 'historically' at least in the kernel sense :-)

 This extra check was added for IDE because each device type driver
 (ide-disk, ide-cd, etc) needed to be updated to not assume virtual
 mappings of request data was valid.  I only did that for ide-disk,
 since this is the only one where bounce buffering really hurt
 performance wise.  So while ide-cd and ide-tape etc could have been
 updated, I deemed it uninteresting and not worthwhile.

 Now, this was just carried straight into the scsi counter parts,
 conveniently, because of laziness.  A quick glance at sr shows that it
 too can aviod bouncing easily (no changes needed).  st may need some
 changes, though.  So again, for scsi it was a matter of not impacting
 existing code in 2.4 too much.

 So TYPE_DISK check can be killed in 2.5 if someone does the work of
 checking that it is safe.  I'm not so sure it will make eg your SCSI
 CD-ROM that much faster :-)"

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

This URL evaporated long ago, and Alan claims it's not coming back.

Implement a "mapping change" notification for virtual lookup caches, and
make the futex code use that to keep the futex page pinning consistent
across copy-on-write events in the VM space.

into kroah.com:/home/greg/linux/BK/gregkh-2.5

the same ignore rules for "tar" as well.

x86-64 has an early console implementation which runs before the normal
console is initialized. To avoid duplicated output it needs to be
disabled when the real console starts. This patch adds an function call
for that to the appropiate part of console_init.

Add the PCI IDs of an AMD 8151 AGP bridge.

Add an AGP driver for the AGP aperture in the northbridge of the AMD Hammer.
The AGP driver works for both 32bit and 64bit kernels.

It also adds some hooks to the AGP driver to allow the x86-64 GART based
IOMMU code to share the aperture with AGP. The hooks are intentionally kept
minimalistic. In addition it needs some Config.in hackery, because AGP cannot
be modular in this case, because the IOMMU needs to control its startup and
it runs early when PCI is initialized.

The original AGP driver was done by Dave Jones, I added the IOMMU support.

Align ELF binary name for x86-64 with ABI.

Required for the x86-64 merge in other mail.

Make CONFIG_ACPI_SLEEP dependent on software suspend (because suspend
is not working yet on x86-64)

Add support for the HPET tables.

The m68k architecture define is __mc68000__, not __m68k__.

From Andreas Schwab <schwab@suse.de>.

  Fix undefined symbol references when support for G100 is requested,
but support for G450 is not.

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

into kleikamp.austin.ibm.com:/home/shaggy/bk/jfs-2.5

If the log (journal) superblock is changed between the time we mount
and unmount the volume, don't trap.  Instead complain, and exit
gracefully.

Always free the request, not just on error.

Small problem, we must of course also remember to take into account
where the last service point was (or will be).

deadline_get_last_sector() either returns the last offset serviced, or
the last one that will be (back of dispatch queue).

Otherwise the insert-at-head can be very unfair.

  Jens Thoms Toerring <Jens.Toerring@physik.fu-berlin.de>
    - RDP must be reset only in isolation phase

It appears that during the MODULE_LICENSE merge for pcmcia i82092 was
missed.

Here is a trivial patch to correct this.

This fixes a problem with the deadline io scheduler, if the correct
insertion point is at the front of the list.  This is something that we
never have gotten right in 2.4 either.

The problem is that the elevator merge function has to return a pointer
to a struct request, and for front insert we really have to return the
head of the list which cannot be expressed as a request of course.

The real issue is that the elevator_merge function actually performs two
functions - it scans for a merge, and if it can't find any, it selects
and insertion point.  It's done this way for efficiency reasons, even if
the design isn't all that clean.

So we change the io scheduler merge functions to get passed a pointer to
a list_head pointer instead.  This works for both inserts and merges.
In addition, deadline checks if it really should insert at the very
front.

Also don't pass in request to elv_try_last_merge(), the very name of the
function suggests that it's q->last_merge that we are interested in.

This is a simple, obvious patch for the abort handler.  I don't know how
we missed it before.

Fix abort problem: us->srb was used after it was erased.

on rechecking the current stable kernel code, I found some places where jiffies
were compared in a way that seems to break when they wrap. For these,
I made up patches to use the macros "time_before()" or "time_after()"
that are supposed to handle wraparound correctly.

Attached is a patch against the 2.4.19 linux kernel. It adds an entry
for another version of the JMTek USBDrive (driverless), and also updates
my email address.

- XFS has started to use clear_page_dirty(), so we should export
  test_clear_page_dirty() to modules.

  This function is ued by the inlined clear_page_dirty().  It marks a
  page clean and updates the global dirty memory accounting.  Anyone
  who cleans pagecache pages should use this, so the export makes
  sense.  Can't implement aops->writepages() without it, really.

- __mark_inode_dirty is no longer called under mapping->private_lock.
   Update comment.

This updates the orinoco wireless driver to version 0.13.

into nuts.ninka.net:/home/davem/src/BK/net-2.5