Re: 2.5.70-mm9

Re: 2.5.70-mm9

[Shane Shrybman]

Hi Andrew,

Would you consider adding Joe Thornber's latest fix for the fixes? :)
LVM has been busted since -mm7. :/

The patch went by on lkml on Wednesday and had a subject line of

[PATCH 1/1] dm: Repair persistent minors

Regards,

Shane

Re: 2.5.70-mm9

[James Bottomley]

On Wed, 2003-06-18 at 02:38, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > I re-run the many fsx tests with feral driver on 2.5.70mm9, ext3
> >  fileystems, on deadline scheduler and as scheduler respectively.  Both
> >  tests passed.  They were running for more than 24 hours without any
> >  problems. So it could be a bug in the device driver that I used
> >  before(QLA2xxx V8).  Before the fsx tests failed on ext3 on either
> >  deadline scheduler or as scheduler.
> 
> Well it could be a bug in the driver, or it could be a bug in the generic
> block/iosched area which was just triggered by the particular way in which
> that driver exercises the core code.
> 
> James, do we have the latest-and-greatest version of the qlogic driver
> in-tree?  ISTR that there's an update out there somewhere?

I'm still currently keeping the qlogic and feral drivers out of tree. 
Feral because Matthew Jacob thinks its not ready yet and Qlogic because
I was waiting for the must-fix list (I'll prod hch again for this).

You can get the current qlogic driver at

  http://sourceforge.net/projects/linux-qla2xxx/

And I will update the BK tree at linux-scsi.bkbits.net

James

Re: 2.5.70-mm9

[Andrew Morton]

Mingming Cao <cmm@us.ibm.com> wrote:
>
> I re-run the many fsx tests with feral driver on 2.5.70mm9, ext3
>  fileystems, on deadline scheduler and as scheduler respectively.  Both
>  tests passed.  They were running for more than 24 hours without any
>  problems. So it could be a bug in the device driver that I used
>  before(QLA2xxx V8).  Before the fsx tests failed on ext3 on either
>  deadline scheduler or as scheduler.

Well it could be a bug in the driver, or it could be a bug in the generic
block/iosched area which was just triggered by the particular way in which
that driver exercises the core code.

James, do we have the latest-and-greatest version of the qlogic driver
in-tree?  ISTR that there's an update out there somewhere?

Re: 2.5.70-mm9

[Mingming Cao]

On Sat, 2003-06-14 at 23:20, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:
> > 
> > > Was elevator=deadline observed to fail in earlier kernels?  If not then it
> > > may be an anticipatory scheduler bug.  It certainly had all the appearances
> > > of that.
> > Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
> >  
> > > So once you're really sure that elevator=deadline isn't going to fail,
> > > could you please test elevator=as?
> > > 
> > Ok, the deadline test was run for 10 hours then I stopped it (for the
> > elevator=as test).  
> > 
> > But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
> > problem.  Some fsx tests are sleeping on io_schedule().  
> > 
> > Next I think I will re-run test on elevator=deadline for 24 hours, to
> > make sure the problem is really gone there.  After that maybe try a
> > different Qlogic Driver, currently I am using the driver from Qlogic
> > company(QLA2XXX V8).
> 
> Martin has just observed what appears to be the same failure on
> 2.5.71-mjb1, which is the deadline scheduler, using qlogicisp.
> 
> Again, some IO appears to have been submitted but it never came back.
> 
> It could be a bug in the requests queueing code somewhere, or in the device
> driver.
> 
> So a good thing to do now would be to find the workload+IO
> scheduler+filesystem which triggers it most easily, and run that with a
> different device driver.  The feral driver (drivers/scsi/isp/ in -mm)
> should be suitable for that test.
> 
> 
I re-run the many fsx tests with feral driver on 2.5.70mm9, ext3
fileystems, on deadline scheduler and as scheduler respectively.  Both
tests passed.  They were running for more than 24 hours without any
problems. So it could be a bug in the device driver that I used
before(QLA2xxx V8).  Before the fsx tests failed on ext3 on either
deadline scheduler or as scheduler.

Thanks for your time and help on tracing down this problem. :)

Mingming

Re: 2.5.70-mm9

[Mingming Cao]

On Sat, 2003-06-14 at 21:14, Nick Piggin wrote:
> 
> 
> Mingming Cao wrote:
> 
> >But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
> >problem.  Some fsx tests are sleeping on io_schedule().  
> >
> 
> So by failed, you just mean stuck in io_schedule? Are you sure
> they are permanently stuck there? Is any progress being made?
> I have tried this test, and often some or most of the processes
> wait in io_schedule for a while, but do get woken.
> 

Yes, I mean they are permanetly hang there with Status D.  No progress
were made.

Re: 2.5.70-mm9

[Mingming Cao]

On Sat, 2003-06-14 at 23:20, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:
> > 
> > > Was elevator=deadline observed to fail in earlier kernels?  If not then it
> > > may be an anticipatory scheduler bug.  It certainly had all the appearances
> > > of that.
> > Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
> >  
> > > So once you're really sure that elevator=deadline isn't going to fail,
> > > could you please test elevator=as?
> > > 
> > Ok, the deadline test was run for 10 hours then I stopped it (for the
> > elevator=as test).  
> > 
> > But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
> > problem.  Some fsx tests are sleeping on io_schedule().  
> > 
> > Next I think I will re-run test on elevator=deadline for 24 hours, to
> > make sure the problem is really gone there.  After that maybe try a
> > different Qlogic Driver, currently I am using the driver from Qlogic
> > company(QLA2XXX V8).
> 
> Martin has just observed what appears to be the same failure on
> 2.5.71-mjb1, which is the deadline scheduler, using qlogicisp.
> 
> Again, some IO appears to have been submitted but it never came back.
> 
> It could be a bug in the requests queueing code somewhere, or in the device
> driver.
> 
> So a good thing to do now would be to find the workload+IO
> scheduler+filesystem which triggers it most easily, and run that with a
> different device driver.  The feral driver (drivers/scsi/isp/ in -mm)
> should be suitable for that test.
> 

I re-run the tests on the deadline scheduler on 2.5.70-mm9 kernel for 24
hours,  serveral fsx tests failed as before, same as as scheduler.  So
the problem is not gone on deadline scheduler, it shows up on both
deadline and as scheduler when running fsx tests on exts3 filesystem. 
It's easy to reproduce: fsx tests +ext3 + deadline/as scheduler + with
QLA2xxx v8 driver.

Now I am going to run the same test with feral driver. Will let you
know.

Mingming

Re: 2.5.70-mm9

[Diego Calleja García]

On 15 Jun 2003 09:58:29 +0200
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:

> The "__mark_inode_dirty" message is a deugging leftofer from Andrew that
> is spit out the first time the machine starts swapping out. You can
> safely ignore it.
> 

Happy to hear that :)
It happened in the init scripts, so it seems coherent.
Anyway, i rebooted to fsck the root filesystem and it found a error (i
don't remember what though) and it fixed it. 

Re: 2.5.70-mm9

[Felipe Alfaro Solana]

On Sun, 2003-06-15 at 03:14, Diego Calleja García wrote:
> On Fri, 13 Jun 2003 01:33:37 -0700
> Andrew Morton <akpm@digeo.com> wrote:
> 
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/
> 
> 
> I had the following messages: (ide, ext3 without any option, SMP, AS, JBD
> debugging enabled):
> 
> VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
>     ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
>     ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
> hda: Maxtor 6Y060L0, ATA DISK drive
> anticipatory scheduling elevator
> [...]
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> VFS: Mounted root (ext3 filesystem) readonly.
> [...]
> EXT3 FS 2.4-0.9.16, 02 Dec 2001 on hda5, internal journal
> [...]
> 
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> PPP: VJ decompression error
> PPP: VJ decompression error
> PPP: VJ decompression error
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> __mark_inode_dirty: this cannot happen
> invalid via82xx_cur_ptr, using last valid pointer
> invalid via82xx_cur_ptr, using last valid pointer
> invalid via82xx_cur_ptr, using last valid pointer
> PPP: VJ decompression error

The "__mark_inode_dirty" message is a deugging leftofer from Andrew that
is spit out the first time the machine starts swapping out. You can
safely ignore it.

Re: 2.5.70-mm9

[Andrew Morton]

Mingming Cao <cmm@us.ibm.com> wrote:
>
> On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:
> 
> > Was elevator=deadline observed to fail in earlier kernels?  If not then it
> > may be an anticipatory scheduler bug.  It certainly had all the appearances
> > of that.
> Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
>  
> > So once you're really sure that elevator=deadline isn't going to fail,
> > could you please test elevator=as?
> > 
> Ok, the deadline test was run for 10 hours then I stopped it (for the
> elevator=as test).  
> 
> But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
> problem.  Some fsx tests are sleeping on io_schedule().  
> 
> Next I think I will re-run test on elevator=deadline for 24 hours, to
> make sure the problem is really gone there.  After that maybe try a
> different Qlogic Driver, currently I am using the driver from Qlogic
> company(QLA2XXX V8).

Martin has just observed what appears to be the same failure on
2.5.71-mjb1, which is the deadline scheduler, using qlogicisp.

Again, some IO appears to have been submitted but it never came back.

It could be a bug in the requests queueing code somewhere, or in the device
driver.

So a good thing to do now would be to find the workload+IO
scheduler+filesystem which triggers it most easily, and run that with a
different device driver.  The feral driver (drivers/scsi/isp/ in -mm)
should be suitable for that test.

Re: 2.5.70-mm9

[Nick Piggin]

Mingming Cao wrote:

>On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:
>
>
>>Was elevator=deadline observed to fail in earlier kernels?  If not then it
>>may be an anticipatory scheduler bug.  It certainly had all the appearances
>>of that.
>>
>Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
> 
>
>>So once you're really sure that elevator=deadline isn't going to fail,
>>could you please test elevator=as?
>>
>>
>Ok, the deadline test was run for 10 hours then I stopped it (for the
>elevator=as test).  
>
>But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
>problem.  Some fsx tests are sleeping on io_schedule().  
>

So by failed, you just mean stuck in io_schedule? Are you sure
they are permanently stuck there? Is any progress being made?
I have tried this test, and often some or most of the processes
wait in io_schedule for a while, but do get woken.

Re: 2.5.70-mm9

[Diego Calleja García]

On Fri, 13 Jun 2003 01:33:37 -0700
Andrew Morton <akpm@digeo.com> wrote:

> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/


I had the following messages: (ide, ext3 without any option, SMP, AS, JBD
debugging enabled):

VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 6Y060L0, ATA DISK drive
anticipatory scheduling elevator
[...]
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
[...]
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on hda5, internal journal
[...]

__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
PPP: VJ decompression error
PPP: VJ decompression error
PPP: VJ decompression error
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
__mark_inode_dirty: this cannot happen
invalid via82xx_cur_ptr, using last valid pointer
invalid via82xx_cur_ptr, using last valid pointer
invalid via82xx_cur_ptr, using last valid pointer
PPP: VJ decompression error

Re: 2.5.70-mm9

[Mingming Cao]

On Sat, 2003-06-14 at 01:01, Andrew Morton wrote:

> Was elevator=deadline observed to fail in earlier kernels?  If not then it
> may be an anticipatory scheduler bug.  It certainly had all the appearances
> of that.
Yes, with elevator=deadline the many fsx tests failed on 2.5.70-mm5.
 
> So once you're really sure that elevator=deadline isn't going to fail,
> could you please test elevator=as?
> 
Ok, the deadline test was run for 10 hours then I stopped it (for the
elevator=as test).  

But the test on elevator=as (2.5.70-mm9 kernel) still failed, same
problem.  Some fsx tests are sleeping on io_schedule().  

Next I think I will re-run test on elevator=deadline for 24 hours, to
make sure the problem is really gone there.  After that maybe try a
different Qlogic Driver, currently I am using the driver from Qlogic
company(QLA2XXX V8).

Thanks,

Mingming

Re: 2.5.70-mm9

[Andrew Morton]

Mingming Cao <cmm@us.ibm.com> wrote:
>
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/
> > 
> > 
> > Lots of fixes, lots of new things.
> >
> 
> Good news, Andrew. I run 50 fsx tests on ext3 filesystems on 2.5.70-mm9. 
>    The hang problem I used seen on 2.5.70-mm6 kernel is gone. The tests 
> runs fine for more than 9 hours. (Normally the problem will occur after 
> 7 hours run on 2.5.70-mm6 kernel).

OK.  I'm no statistician, but I'd be more comfortable with 24 hours..

> I am running the tests on 8 way PIII 700MHz, 4G memory, with 
> elevator=deadline.
> 

Was elevator=deadline observed to fail in earlier kernels?  If not then it
may be an anticipatory scheduler bug.  It certainly had all the appearances
of that.

So once you're really sure that elevator=deadline isn't going to fail,
could you please test elevator=as?

Re: 2.5.70-mm9

[Mingming Cao]

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/
> 
> 
> Lots of fixes, lots of new things.
>

Good news, Andrew. I run 50 fsx tests on ext3 filesystems on 2.5.70-mm9. 
   The hang problem I used seen on 2.5.70-mm6 kernel is gone. The tests 
runs fine for more than 9 hours. (Normally the problem will occur after 
7 hours run on 2.5.70-mm6 kernel).

I am running the tests on 8 way PIII 700MHz, 4G memory, with 
elevator=deadline.

Re: 2.5.70-mm9

[Brandon Low]

I tried to compile this drivre and got a ton of undefined references to
psmouse_command ... haven't looked at the code yet, but I'd guess it
only works when builtin, not as a module?  Need an export symbol
somewhere?

--Brandon Low
Gentoo Dork/Dev :)

On Fri, 06/13/03 at 01:33:37 -0700, Andrew Morton wrote:
> +synaptics.patch
> +synaptics-cleanup.patch
> 
>  Synaptics driver (one flavour thereof)

Re: 2.5.70-mm9

[Andrew Morton]

Andrew Morton <akpm@digeo.com> wrote:
>
> +mark-inode-dirty-debug.patch

This will print "__mark_inode_dirty: this cannot happen" when the machine
first starts to swap.  Please ignore it.

2.5.70-mm9

[Andrew Morton]

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.70/2.5.70-mm9/


Lots of fixes, lots of new things.



Changes since 2.5.70-mm8:


 linus.patch

 Current Linus -BK.

-remove-DRM-ioctls.patch
-rtc-32-bit-fix.patch
-rtc-busywait-fix.patch
-irq_cpustat-cleanup.patch
-discontig-empty-node-fix.patch
-mem-driver-cleanup-2.patch
-TARGET_CPUS-cleanup-fix.patch
-compaq-drivers-MAINTAINERS.patch
-fixed-size-kmalloc-speedup.patch
-rebalance_tick-fix.patch
-loop-01-use-highmem.patch
-loop-02-privatise-bio_copy.patch
-loop-03-rename-bio-things.patch
-loop-04-copy-bio-not-data.patch
-loop-05-remove-unused-IV.patch
-loop-06-remove-LO_FLAGS_BH_REMAP.patch
-loop-07-remove-blk_queue_bounce.patch
-loop-08-copy_bio-use-highmem.patch
-loop-09-dont-lose-PF_MEMDIE.patch
-fix-numa-meminfo.patch
-tmpfs-01-shmem_file_write-EFAULT.patch
-tmpfs-02-swapoff-truncate-race-refix.patch
-tmpfs-03-little-bits.patch
-pci-init-ordering-fix.patch
-early-printk-x86.patch
-resource-seqfile-cleanup.patch
-ds-02-x25-facilities-parse-fix.patch
-ds-05-eicon-usercopy-fix.patch
-ds-06-intermezzo-usercopy-fix.patch
-ds-07-mdc800-usercopy-fix.patch
-ds-08-mpu401-usercopy-fix.patch
-ds-11-emu10k1-memleak-fix.patch
-ds-12-rio-memleak-fix.patch
-ds-13-i810-leak-fix.patch
-serial-core-oops-fix.patch
-trond-3.patch
-nfs-to-localhost-lockup-fix.patch
-devfs_mk_dir-fix.patch
-tioclinux-symbolic-names.patch
-cpqarray-stack-reduction.patch
-s390-dirty-bit-cleaning.patch
-char-dev-init-call-fix.patch

 Merged

+generic-numa-fixes.patch

 Fix strangely-configured NUMA systems.

+compat_ioctl-fixes.patch

 Fix up some 64/32-bit ioctl things

+synaptics.patch
+synaptics-cleanup.patch

 Synaptics driver (one flavour thereof)

+es7000-01-generic.patch
+es7000-02-subarch.patch

 Unisys ES7000 subarch support.

-ppc64-ioctl-pci-update.patch
+ppc64-pci-update.patch

 ppc64 PCI fixes (split out)

+ppc64-do_settimeofday-update.patch
+sparc64-do_settimeofday-update.patch
+x86_64-do_settimeofday-update.patch
+ia64-do_settimeofday-update.patch
+parisc-do_settimeofday-update.patch
+s390-do_settimeofday-update.patch
+alpha-do_settimeofday-update.patch
+arm-do_settimeofday-update.patch
+cris-do_settimeofday-update.patch
+m68k-do_settimeofday-update.patch
+ppc-do_settimeofday-update.patch
+arm26-do_settimeofday-update.patch
+sh-do_settimeofday-update.patch
+sparc-do_settimeofday-update.patch
+um-do_settimeofday-update.patch
+v850-do_settimeofday-update.patch

 Save george from angry arch maintainers

+centrino-cpufreq-driver.patch

 cpufreq driver for Intel Centrino CPUs

+remove_anon_hash_chain.patch

 anon_hash_chain is unneeded.

+e100-use-after-free-fix.patch

 Manfred's debug patch kills this driver.  (Scott has a patch for this
 queued).

+statfs64-3.patch

 sys_statfs64(), again.

+hugetlbfs-size-inodes-mount-option.patch

 Allow the admin to specify the sizing of a hugetlbfs mount

+sched-cleanup-2.patch

 Tidy a few things in the CPU scheduler.

+shmem-license-revert.patch

 use the same licensing words as in 2.4

+lsm-1-early-init.patch
+lsm-2-remove-hook.patch
+lsm-3-remove-inode_permission_lite.patch
+lsm-4-setfsuid-fix.patch

 Security stuff

-synaptics-mouse-support.patch

 Dropped

+as-div-by-zero-fix.patch
+as-more-HZ.patch
+as-even-more-write-batch-tuning.patch

 Anticipatory scheduler changes

+jbd-680-log_wait_for_space-fix.patch

 Tiny tweak.

+aio-12-readahead.patch

 Open-code the readahead needed for restartable AIO.

+truncate-pagefault-race-fix.patch

 Fix race between truncate and pagein which leaves dangling anon pages.

+writeback-memory-backed-fix.patch

 Don't let dirty memory-backed inodes prevent writeout of non-memory-backed
 inodes.

+mark-inode-dirty-debug.patch

 Check that inode->i_sb really cannot be zero in __mark_inode_dirty()

+sync-write-more-pages.patch

 sys_sync() and the kupdate function can forget to write out atime updates.

+make-pid_max-readable.patch

 Make /proc/sys/kernel/pid_max readable by mortals.




All 192 patches


linus.patch

mm.patch
  add -mmN to EXTRAVERSION

kgdb-ga.patch
  kgdb stub for ia32 (George Anzinger's one)

kgdb-use-ggdb.patch

HZ-100.patch

generic-numa-fixes.patch
  NUMA fixes

compat_ioctl-fixes.patch
  compat_ioctl fixes

synaptics.patch
  From: "Joseph Fannin" <jhf@rivenstone.net>
  Subject: [PATCH] Synaptics TouchPad driver for 2.5.70

synaptics-cleanup.patch

es7000-01-generic.patch
  Unisys ES7000 platform subarch 1/2: generic bits

es7000-02-subarch.patch
  Unisys ES7000 2/2: platform subarch

config_spinline.patch
  uninline spinlocks for profiling accuracy.

ppc64-bat-initialisation-fix.patch
  ppc64: BAT initialisation fix

ppc64-fixup.patch
  ppc64 fixup

ppc64-pci-update.patch

ppc64-reloc_hide.patch

ppc64-semaphore-reimplementation.patch
  ppc64: use the ia32 semaphore implementation

ppc64-knr-to-ansi.patch
  K&R style to ANSI style conversions in arch/ppc64/boot/zlib.c

sym-do-160.patch
  make the SYM driver do 160 MB/sec

x86_64-fixes.patch
  x86_64 fixes

irqreturn-snd-via-fix.patch
  via sound irqreturn fix

config-PAGE_OFFSET.patch
  Configurable kenrel/user memory split

lru_cache_add-check.patch
  lru_cache_add debug check

delay-ksoftirqd-fallback.patch
  Try harded in IRQ context before falling back to ksoftirqd

time-fixes-cleanup-1.patch
  Some clean up of the time code.

time-fixes-cleanup-2.patch
  More time clean up stuff

ppc64-do_settimeofday-update.patch
  ppc64: fix do_settimeofday() for new API

sparc64-do_settimeofday-update.patch
  sparc64: fix do_settimeofday() for new API

x86_64-do_settimeofday-update.patch
  x86_64: fix do_settimeofday() for new API

ia64-do_settimeofday-update.patch
  ia64: fix do_settimeofday() for new API

parisc-do_settimeofday-update.patch
  parisc: fix do_settimeofday() for new API

s390-do_settimeofday-update.patch
  ppc64: fix do_settimeofday() for new API

alpha-do_settimeofday-update.patch
  ppc64: fix do_settimeofday() for new API

arm-do_settimeofday-update.patch
  arm: fix do_settimeofday() for new API

cris-do_settimeofday-update.patch
  cris: fix do_settimeofday() for new API

m68k-do_settimeofday-update.patch
  m68k: fix do_settimeofday() for new API

ppc-do_settimeofday-update.patch
  ppc: fix do_settimeofday() for new API

arm26-do_settimeofday-update.patch
  arm26: fix do_settimeofday() for new API

sh-do_settimeofday-update.patch
  sh: fix do_settimeofday() for new API

sparc-do_settimeofday-update.patch
  sparc: fix do_settimeofday() for new API

um-do_settimeofday-update.patch
  um: fix do_settimeofday() for new API

v850-do_settimeofday-update.patch
  ppc64: fix do_settimeofday() for new API

centrino-cpufreq-driver.patch
  Pentium M (Centrino) cpufreq device driver (please test me)

fb-image-depth-fix.patch
  fbdev image depth fix

ds-01-arcnet-oops-fix.patch
  arcnet oops fix

ds-09-vicam-usercopy-fix.patch
  vicam usercopy fix

buffer-debug.patch
  buffer.c debugging

show_stack-cleanup.patch
  show_stack() portability and cleanup patch

ppc64-show_stack.patch

remove_anon_hash_chain.patch
  remove anon_hash_chain

e100-use-after-free-fix.patch

statfs64-3.patch
  Add system calls statfs64 and fstatfs64

VM_RESERVED-check.patch
  VM_RESERVED check

rcu-stats.patch
  RCU statistics reporting

ide_setting_sem-fix.patch

hugetlbfs-size-inodes-mount-option.patch
  hugetlbfs: specify size & inodes at mount

sched-cleanup-2.patch
  sched.c cleanups, hotplug CPU preparation

shmem-license-revert.patch
  tmpfs: revert license to 2.4 version

reslabify-pgds-and-pmds.patch
  re-slabify i386 pgd's and pmd's

lsm-1-early-init.patch
  LSM 1/4: Early init for security modules

lsm-2-remove-hook.patch
  LSM 2/4: Remove task_kmod_set_label hook

lsm-3-remove-inode_permission_lite.patch
  LSM 3/4: Remove inode_permission_lite hook

lsm-4-setfsuid-fix.patch
  LSM 4/4: setfsuid/setgsuid bug fix

linux-isp.patch

isp-update-1.patch

isp-remove-pci_detect.patch

list_del-debug.patch
  list_del debug check

airo-schedule-fix.patch
  airo.c: don't sleep in atomic regions

resurrect-batch_requests.patch
  bring back the batch_requests function

kblockd.patch
  Create `kblockd' workqueue

cfq-infrastructure.patch

elevator-completion-api.patch
  elevator completion API

as-iosched.patch
  anticipatory I/O scheduler

as-proc-read-write.patch
  AS: pgbench improvement

as-discrete-read-fifo-batches.patch
  AS: discrete read fifo batches

as-sync-async.patch
  AS sync/async batches

as-hash-removal-fix.patch
  AS: hash removal fix

as-jumbo-patch-for-scsi.patch
  AS jumbo patch (for SCSI and TCQ)

as-stupid.patch
  AS: fix stupid thinko

as-no-batch-antic-limit.patch
  AS: no batch-antic-limit

as-autotune-write-batches.patch
  AS: autotune write batches

as-div-by-zero-fix.patch
  AS: divide by zero fix

as-more-HZ.patch
  AS: more HZ != 1000 fixes

as-even-more-write-batch-tuning.patch
  AS: update_write_batch tuning

as-locking.patch
  AS locking

as-HZ.patch
  AS HZ fixes

as-double-free-and-debug.patch
  AS: fix a leak + more debugging

as-fix-seek-estimation.patch
  AS: maybe repair performance drop of random read O_DIRECT

as-fix-seeky-loads.patch
  AS: fix IBM's seek load

unplug-use-kblockd.patch
  Use kblockd for running request queues

cfq-2.patch
  CFQ scheduler, #2
  CFQ: update to rq-dyn API

cfq-hash-removal-fix.patch
  CFQ: hash removal fix

cfq-list_del-fix.patch
  CFQ: empty the queuelist

per-queue-nr_requests.patch
  per queue nr_requests

blk-invert-watermarks.patch
  blk_congestion_wait threshold cleanup

blk-fair-batches.patch
  blk-fair-batches

blk-as-hint.patch
  blk-as-hint

get_request_wait-oom-fix.patch
  handle OOM in get_request_wait().

blk-fair-batches-2.patch
  blk fair batches #2

unmap-page-debugging-2.patch
  debug patch: unmap unused kernel pages

slab-poisoning-fix.patch
  slab poisoning fix

print-build-options-on-oops.patch
  print a few config options on oops

mmap-prefault.patch
  prefault of executable mmaps

bio-debug-trap.patch
  BIO debugging patch

sound-irq-hack.patch

show_task-free-stack-fix.patch
  show_task() fix and cleanup

put_task_struct-debug.patch

ia32-mknod64.patch
  mknod64 for ia32

ext2-64-bit-special-inodes.patch
  ext2: support for 64-bit device nodes

ext3-64-bit-special-inodes.patch
  ext3: support for 64-bit device nodes

64-bit-dev_t-kdev_t.patch
  64-bit dev_t and kdev_t

oops-dump-preceding-code.patch
  i386 oops output: dump preceding code

lockmeter.patch

ext3-no-bkl.patch
  ext3: move lock_kernel() down into the JBD layer.

journal_get_write_access-speedup.patch
  JBD: journal_get_write_access() speedup

ext3-concurrent-block-inode-allocation.patch
  ext3: concurrent block/inode allocation
  Fix orlov allocator boundary case

ext3-concurrent-block-allocation-hashed.patch
  ext3: scalable counters and locks
  fix ext3 inode allocator race

jbd-010-b_committed_data-race-fix.patch
  JBD: fix race over access to b_committed_data

jbd-020-locking-schema.patch
  JBD: plan JBD locking schema

jbd-030-remove-splice_lock.patch
  JBD: remove jh_splice_lock

jbd-040-journal_add_journal_head-locking.patch
  JBD: fine-grain journal_add_journal_head locking

jbd-045-rename-journal_unlock_journal_head.patch
  JBD: rename journal_unlock_journal_head to journal_put_journal_head

jbd-050-b_frozen_data-locking.patch
  JBD: Finish protection of journal_head.b_frozen_data

jbd-060-b_committed_data-locking.patch
  JBD: implement b_committed_data locking

jbd-070-b_transaction-locking.patch
  JBD: implement b_transaction locking rules

jbd-080-b_next_transaction-locking.patch
  JBD: Implement b_next_transaction locking rules

jbd-090-b_tnext-locking.patch
  JBD: b_tnext locking

jbd-100-remove-journal_datalist_lock.patch
  JBD: remove journal_datalist_lock

jbd-110-t_nr_buffers-locking.patch
  JBD: t_nr_buffers locking

jbd-120-t_updates-locking.patch
  JBD: t_updates locking

jbd-130-t_outstanding_credits-locking.patch
  JBD: implement t_outstanding_credits locking

jbd-140-t_jcb-locking.patch
  JBD: implement t_jcb locking

jbd-150-j_barrier_count-locking.patch
  JBD: implement j_barrier_count locking

jbd-160-j_running_transaction-locking.patch
  JBD: implement j_running_transaction locking

jbd-170-j_committing_transaction-locking.patch
  JBD: implement j_committing_transaction locking

jbd-180-j_checkpoint_transactions.patch
  JBD: implement j_checkpoint_transactions locking

jbd-190-j_head-locking.patch
  JBD: implement journal->j_head locking

jbd-200-j_tail-locking.patch
  JBD: implement journal->j_tail locking

jbd-210-j_free-locking.patch
  JBD: implement journal->j_free locking

jbd-220-j_commit_sequence-locking.patch
  JBD: implement journal->j_commit_sequence locking

jbd-230-j_commit_request-locking.patch
  JBD: implement j_commit_request locking

jbd-240-dual-revoke-tables.patch
  JBD: implement dual revoke tables.

jbd-250-remove-sleep_on.patch
  JBD: remove remaining sleep_on()s

jbd-300-remove-lock_kernel.patch
  JBD: remove lock_kernel()

jbd-400-remove-lock_journal.patch
  JBD: remove lock_journal()

jbd-510-h_credits-fix.patch
  JBD: journal_release_buffer: handle credits fix

jbd-520-journal_unmap_buffer-race.patch
  JBD: journal_unmap_buffer race fix

jbd-530-walk_page_buffers-race-fix.patch
  ext3: ext3_writepage race fix

jbd-540-journal_try_to_free_buffers-race-fix.patch
  JBD: buffer freeing non-race comment

jbd-550-locking-checks.patch
  JBD: add some locking assertions

jbd-570-transaction-state-locking.patch
  JBD: additional transaction shutdown locking

jbd-580-log_start_commit-race-fix.patch
  JBD: fix log_start_commit race

jbd-590-do_get_write_access-speedup.patch
  JBD: do_get_write_access() speedup

ext3-010-fix-journalled-data.patch
  ext3: fix data=journal mode

ext3-035-journal_try_to_free_buffers-race-fix.patch

ext3-040-recursive-ext3_write_inode-check.patch
  ext3: add a dump_stack()

ext3-050-ioctl-transaction-leak.patch
  ext3: fix error-path handle leak

ext3-070-xattr-clone-leak-fix.patch
  Fix leak in ext3_acl_chmod()

ext3-080-remove-block-inode-count-message.patch
  ext3: remove mount-time diagnostic messages

jbd-600-journal_dirty_metadata-speedup.patch
  JBD: journal_dirty_metadata() speedup

jbd-610-journal_dirty_metadata-diags.patch
  JBD: journal_dirty_metadata diagnostics

jbd-620-commit-vs-start-race-fix.patch
  JBD: fix race between journal_commit_transaction and start_this_handle

ext3-090-journalled-writepage-vs-truncate-fix.patch
  ext3: fix data=journal for small blocksize

jbd-630-remove-j_commit_timer_active.patch
  JBD: remove j_commit_timer_active

jbd-650-truncate-ordered-pages.patch
  ext3: explicitly free truncated pages

jbd-660-log_do_checkpoint-fix.patch
  JBD: log_do_checkpoint() locking fixes

jbd-670-log_start_commit-locking-fix.patch
  JBD: fix locking around log_start_commit()

jbd-680-log_wait_for_space-fix.patch
  JBD: hold onto j_state_lock after log_wait_for_space().

invalidate_mmap_range.patch
  Interface to invalidate regions of mmaps

aio-01-retry.patch
  AIO: Core retry infrastructure

aio-02-lockpage_wq.patch
  AIO: Async page wait

aio-03-fs_read.patch
  AIO: Filesystem aio read

aio-04-buffer_wq.patch
  AIO: Async buffer wait

aio-05-fs_write.patch
  AIO: Filesystem aio write

aio-05-fs_write-fix.patch

aio-06-bread_wq.patch
  AIO: Async block read

aio-06-bread_wq-fix.patch

aio-07-ext2getblk_wq.patch
  AIO: Async get block for ext2

aio-poll.patch
  aio_poll
  aio-poll: don't put extern decls in .c!

O_SYNC-speedup-2.patch
  speed up O_SYNC writes

aio-09-o_sync.patch
  aio O_SYNC

aio-10-BUG-fix.patch
  AIO: fix a BUG

aio-11-workqueue-flush.patch
  AIO: flush workqueues before destroying ioctx'es

aio-12-readahead.patch
  AIO: readahead fixes

vfsmount_lock.patch
  From: Maneesh Soni <maneesh@in.ibm.com>
  Subject: [patch 1/2] vfsmount_lock

syncppp-locking-fix.patch
  syncppp locking fix

sched-hot-balancing-fix.patch
  fix for CPU scheduler load distribution

truncate-pagefault-race-fix.patch
  Fix vmtruncate race and distributed filesystem race

writeback-memory-backed-fix.patch
  fix writeback for dirty ramdisk blockdev inodes

mark-inode-dirty-debug.patch

sync-write-more-pages.patch
  dirty inode writeback fix

make-pid_max-readable.patch
  make pid_max readable