2.5.59-mm2

2.5.59-mm2

[Andrew Morton]

http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.59/2.5.59-mm2/

- Added Andi's lockless current_kernel_time() patch again.  It'll break
  non-ia32 builds.  But it appears that we should push ahead and get this
  implemented across the other architectures.

- Updated oprofile patches from John.

- Adam's devfs rework is back in.  We only had two testers last time, (out
  of maybe 150 downloads) which is fairly disappointing.

  So if you use devfs, _please_ test this change and send either success or
  failure reports (not to me though).

  Adam said:

   If you want devfsd functionality (well, at least the "REGISTER" and
   "LOOKUP" events), you can get my user level program devfs_helper, which is
   a reduced functionality replacement program for devfsd from the following
   URL.

	ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/devfs_helper-0.2.tar.gz




Changes since 2.5.59-mm1:


+lockless-current_kernel_time.patch

 Reinstated.

-mixer-bounds-check.patch

 This didn't look right.

+kirq-up-fix.patch

 Fix the kirq build for non-SMP

-op4-fix.patch

 Not needed with the updated oprofile patch

+oprofile_cpu-as-string.patch

 oprofile work from John.

+remove-will_become_orphaned_pgrp.patch

 Cleanup

+MAX_IO_APICS-ifdef.patch

 NUMA fix

+dac960-error-retry.patch

 DAC960 robustness enhancements

+put_user-warning-fix.patch

 ARM build fix

+vmlinux-fix.patch

 Should fix the modprobe oopses with RH8.0 toolchains

+smalldevfs.patch

 devfs rework

+sound-firmware-load-fix.patch

 Build fix for OSS sound card firmware loading.

+exit_mmap-fix2.patch

 Fix exec of 32-bit apps from 64-bit apps on PPC64/ia64/sparc64, perhaps.



All 43 patches:

kgdb.patch

devfs-fix.patch

deadline-np-42.patch
  (undescribed patch)

deadline-np-43.patch
  (undescribed patch)

setuid-exec-no-lock_kernel.patch
  remove lock_kernel() from exec of setuid apps

buffer-debug.patch
  buffer.c debugging

warn-null-wakeup.patch

reiserfs-readpages.patch
  reiserfs v3 readpages support

fadvise.patch
  implement posix_fadvise64()

ext3-scheduling-storm.patch
  ext3: fix scheduling storm and lockups

auto-unplug.patch
  self-unplugging request queues

less-unplugging.patch
  Remove most of the blk_run_queues() calls

lockless-current_kernel_time.patch
  Lockless current_kernel_timer()

scheduler-tunables.patch
  scheduler tunables

htlb-2.patch
  hugetlb: fix MAP_FIXED handling

kirq.patch

kirq-up-fix.patch
  Subject: Re: 2.5.59-mm1

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

prune-icache-stats.patch
  add stats for page reclaim via inode freeing

vma-file-merge.patch

mmap-whitespace.patch

read_cache_pages-cleanup.patch
  cleanup in read_cache_pages()

remove-GFP_HIGHIO.patch
  remove __GFP_HIGHIO

quota-lockfix.patch
  quota locking fix

quota-offsem.patch
  quota semaphore fix

oprofile-p4.patch

oprofile_cpu-as-string.patch
  oprofile cpu-as-string

wli-11_pgd_ctor.patch
  (undescribed patch)

wli-11_pgd_ctor-update.patch
  pgd_ctor update

stack-overflow-fix.patch
  stack overflow checking fix

Richard_Henderson_for_President.patch
  Subject: [PATCH] Richard Henderson for President!

parenthesise-pgd_index.patch
  Subject: i386 pgd_index() doesn't parenthesize its arg

macro-double-eval-fix.patch
  Subject: Re: i386 pgd_index() doesn't parenthesize its arg

mmzone-parens.patch
  asm-i386/mmzone.h macro paren/eval fixes

blkdev-fixes.patch
  blkdev.h fixes

remove-will_become_orphaned_pgrp.patch
  remove will_become_orphaned_pgrp()

MAX_IO_APICS-ifdef.patch
  MAX_IO_APICS #ifdef'd wrongly

dac960-error-retry.patch
  Subject: [PATCH] linux2.5.56 patch to DAC960 driver for error retry

put_user-warning-fix.patch
  Subject: Re: Linux 2.5.59

vmlinux-fix.patch
  vmlinux fix

smalldevfs.patch
  smalldevfs

sound-firmware-load-fix.patch
  soundcore.c referenced non-existent errno variable

exit_mmap-fix2.patch
  exit_mmap fix for 64bit->32bit execs


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59-mm2

[Arjan van de Ven]

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]


> +kirq-up-fix.patch
> 
>  Fix the kirq build for non-SMP

Hi,

Is there any reason to put this complexity in the kernel instead of
doing it from a userspace daemon?

A userspace daemon can do higher level evaluations, read config files
about the system (like numa configuration etc etc) and all 2.4/2.5
kernels already have a userspace api for setting irq affinity..

an example of a simple version of such daemon is:
http://people.redhat.com/arjanv/irqbalance/irqbalance-0.03.tar.gz

any chance of testing this in an intel lab?

Greetings,
     Arjan van de Ven

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

2.5.59mm2 BUG at fs/jbd/transaction.c:1148

[Mike Galbraith]

[-- Attachment #1: Type: text/plain, Size: 167 bytes --]

Greetings,

I got the attached oops upon doing my standard reboot sequence SysRq[sub].

fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.

	-Mike

[-- Attachment #2: oops --]
[-- Type: application/octet-stream, Size: 1675 bytes --]

SysRq : Emergency Sync
Syncing device ide0(3,6) ... OK
Syncing device ide0(3,7) ... 
<0>Assertion failure in journal_dirty_metadata() at fs/jbd/transaction.c:1148: "jh->b_jlist != 1"
------------[ cut here ]------------
kernel BUG at fs/jbd/transaction.c:1148!
invalid operand: 0000
CPU:    0
EIP:    0060:[<c01755e4>]    Not tainted
EFLAGS: 00010286
EIP is at journal_dirty_metadata+0x10c/0x174
eax: 00000062   ebx: c33aeb80   ecx: c31df8e0   edx: c027fbb0
esi: c32b9260   edi: c7a89e00   ebp: c7a839c0   esp: c31e1ccc
ds: 007b   es: 007b   ss: 0068
Process syslogd (pid: 102, threadinfo=c31e0000 task=c31df8e0)
Stack: c0249ca0 c024a1c1 c0249c80 0000047c c024a1d8 c317cd3c c7a839c0 00000000 
       c31e1d64 c0169bd1 c7a839c0 c317cd3c c317cd3c 00001000 c317cd3c 00001000 
       00000050 00000040 c0169994 c7a839c0 c317cd3c 00010000 00000000 c31c5660 
Call Trace:
 [<c0169bd1>] commit_write_fn+0x19/0x60
 [<c0169994>] walk_page_buffers+0x50/0x74
 [<c0169cda>] ext3_commit_write+0xc2/0x1d8
 [<c0169bb8>] commit_write_fn+0x0/0x60
 [<c0129e13>] generic_file_aio_write_nolock+0x797/0x984
 [<c01f2bab>] kfree_skbmem+0xb/0x54
 [<c01f2cb6>] __kfree_skb+0xc2/0xc8
 [<c0230fba>] unix_stream_recvmsg+0x2ea/0x370
 [<c012a06f>] generic_file_write_nolock+0x6f/0x8c
 [<c01efe46>] sock_aio_read+0x8a/0x9c
 [<c013cab1>] do_sync_read+0x81/0xb0
 [<c01163bd>] do_schedule+0x235/0x25c
 [<c012a225>] generic_file_writev+0x31/0x44
 [<c013d08b>] do_readv_writev+0x1a7/0x27c
 [<c013cbe0>] do_sync_write+0x0/0xb0
 [<c017205d>] ext3_force_commit+0x1d/0x24
 [<c01675bb>] ext3_sync_file+0x5b/0x70
 [<c013d1f7>] vfs_writev+0x4b/0x50
 [<c013d262>] sys_writev+0x2a/0x3c
 [<c010a367>] syscall_call+0x7/0xb

Re: 2.5.59mm2 BUG at fs/jbd/transaction.c:1148

[Mike Galbraith]

At 12:05 AM 1/19/2003 -0800, Andrew Morton wrote:
>Mike Galbraith <efault@gmx.de> wrote:
> >
> > Greetings,
> >
> > I got the attached oops upon doing my standard reboot sequence SysRq[sub].
> >
> > fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.
> >
>
>You using data=journal?

Yup, on /var.

         -Mike

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59mm2 BUG at fs/jbd/transaction.c:1148

[Andrew Morton]

Mike Galbraith <efault@gmx.de> wrote:
>
> Greetings,
> 
> I got the attached oops upon doing my standard reboot sequence SysRq[sub].
> 
> fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.
> 

You using data=journal?


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59mm2 BUG at fs/jbd/transaction.c:1148

[Mike Galbraith]

At 12:05 AM 1/19/2003 -0800, Andrew Morton wrote:
>Mike Galbraith <efault@gmx.de> wrote:
> >
> > Greetings,
> >
> > I got the attached oops upon doing my standard reboot sequence SysRq[sub].
> >
> > fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.
> >
>
>You using data=journal?

(p.s. it isn't a repeatable oops.  i've done SysRq-S many times)

         -Mike


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59mm2 BUG at fs/jbd/transaction.c:1148

[Andrew Morton]

Mike Galbraith <efault@gmx.de> wrote:
>
> At 12:05 AM 1/19/2003 -0800, Andrew Morton wrote:
> >Mike Galbraith <efault@gmx.de> wrote:
> > >
> > > Greetings,
> > >
> > > I got the attached oops upon doing my standard reboot sequence SysRq[sub].
> > >
> > > fwiw, I was fiddling with an ext2 ramdisk just prior to poking buttons.
> > >
> >
> >You using data=journal?
> 

data=journal is sick in 2.5, although this is not the crash which I have seen
it exhibit.

On my todo list.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59-mm2

[Andrew Morton]

"Nakajima, Jun" <jun.nakajima@intel.com> wrote:
>
> My point was that doing in user mode cannot justify wasting CPUs cycles
> for not good reasons.

Performing this function in userspace means that we can implement more
effective algorithms, more configurability and perhaps better monitoring - so
on machines which need it, the overhead could well be more than reclaimed.

And we can work on the overhead.  Perhaps add a lightweight alternative to
/proc/interrupts, and change the IRQ affinity setting code so that it merely
places some settings into memory, and those are actually acted upon when the
next interrupt occurs (should be able to do this locklessly).

Given that your new algorithm requires granularity on the order of a second
(this is good!), Arjan's approach is very attractive indeed.

And it should be pretty easy to get the implementation working on other
architectures.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

RE: 2.5.59-mm2

[Nakajima, Jun]

> costly is a relative thing. a dozen cycles perhaps; do it once per
> 10 seconds and it's invisbile. I agree that if you want to do it thousands
> of times per second it might become a problem.But so far I don't see the
> real need for that.

Well, "complex" is a relative thing as well. At that time, we did not have a sophisticated algorithm to adjust the time period depending on the interrupt load. So today we may not see the difference. 

Anyway, I agree that complex things or policies should be moved to user mode as much as possible and the kernel should have the mechanism. And we'll take a look at your code. My point was that doing in user mode cannot justify wasting CPUs cycles for not good reasons.

Thanks,
Jun


> -----Original Message-----
> From: Arjan van de Ven [mailto:arjanv@redhat.com]
> Sent: Sunday, January 19, 2003 12:19 PM
> To: Nakajima, Jun
> Cc: arjanv@redhat.com; Andrew Morton; linux-mm@kvack.org; Kamble, Nitin A;
> Mallick, Asit K; Saxena, Sunil
> Subject: Re: 2.5.59-mm2
> 
> On Sun, Jan 19, 2003 at 11:45:35AM -0800, Nakajima, Jun wrote:
> > We initially implemented it in user level, accessing /proc/interrupts.
> We have two issues/concerns at that point. And we saw better results with
> kernel mode.
> 
> > - the data structures required, such as kstat, are already in the kernel
> >   and converting the text info from /proc/interrupts was costly in
> >   user mode.
> 
> costly is a relative thing. a dozen cycles perhaps; do it once per
> 10 seconds and it's invisbile. I agree that if you want to do it thousands
> of times per second it might become a problem.But so far I don't see the
> real need for that.
> 
> > - we suspect that frequent writes (asynchronous to interrupts)
> >   to /proc/irq/N/smp_affinity might expose a race condition in interrupt
> >   machinery. For example, we saw a hang caused by such a write.
> 
> if there's a bug there it needs fixing anyway; even inside the kernel
> you'll have a similar race I suspect
> 
> > So to implement it in user level efficiently, we need API that
> > - that provide binary data that can be easily processed by such a daemon,
> 
> there is rightfully a veto on such ABI and it's also not needed.
> /proc/interrupts is less than 4Kb normally; it'll be in cache so parsing
> it will be cheap. Sure the code I posted isn't optimal (far from it) but
> that can be optimized a lot.
> 
> Greetings,
>   Arjan van de Ven
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

Re: 2.5.59-mm2

[Arjan van de Ven]

On Sun, Jan 19, 2003 at 11:45:35AM -0800, Nakajima, Jun wrote:
> We initially implemented it in user level, accessing /proc/interrupts. We have two issues/concerns at that point. And we saw better results with kernel mode.

> - the data structures required, such as kstat, are already in the kernel
>   and converting the text info from /proc/interrupts was costly in
>   user mode.

costly is a relative thing. a dozen cycles perhaps; do it once per
10 seconds and it's invisbile. I agree that if you want to do it thousands
of times per second it might become a problem.But so far I don't see the
real need for that.

> - we suspect that frequent writes (asynchronous to interrupts)
>   to /proc/irq/N/smp_affinity might expose a race condition in interrupt
>   machinery. For example, we saw a hang caused by such a write.

if there's a bug there it needs fixing anyway; even inside the kernel
you'll have a similar race I suspect

> So to implement it in user level efficiently, we need API that
> - that provide binary data that can be easily processed by such a daemon,

there is rightfully a veto on such ABI and it's also not needed.
/proc/interrupts is less than 4Kb normally; it'll be in cache so parsing
it will be cheap. Sure the code I posted isn't optimal (far from it) but
that can be optimized a lot.

Greetings,
  Arjan van de Ven
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

RE: 2.5.59-mm2

[Nakajima, Jun]

We initially implemented it in user level, accessing /proc/interrupts. We have two issues/concerns at that point. And we saw better results with kernel mode.
- the data structures required, such as kstat, are already in the kernel and converting the text info from /proc/interrupts was costly in user mode.
- we suspect that frequent writes (asynchronous to interrupts) to /proc/irq/N/smp_affinity might expose a race condition in interrupt machinery. For example, we saw a hang caused by such a write.

So to implement it in user level efficiently, we need API that
- that provide binary data that can be easily processed by such a daemon,
- safer API to change routing. Or we need to take a closer look at /proc/irq/N/smp_affinity.

Thanks,
Jun


> -----Original Message-----
> From: Arjan van de Ven [mailto:arjanv@redhat.com]
> Sent: Saturday, January 18, 2003 12:13 PM
> To: Andrew Morton
> Cc: linux-mm@kvack.org; Kamble, Nitin A; Nakajima, Jun; Mallick, Asit K;
> Saxena, Sunil
> Subject: Re: 2.5.59-mm2
> 
> 
> > +kirq-up-fix.patch
> >
> >  Fix the kirq build for non-SMP
> 
> Hi,
> 
> Is there any reason to put this complexity in the kernel instead of
> doing it from a userspace daemon?
> 
> A userspace daemon can do higher level evaluations, read config files
> about the system (like numa configuration etc etc) and all 2.4/2.5
> kernels already have a userspace api for setting irq affinity..
> 
> an example of a simple version of such daemon is:
> http://people.redhat.com/arjanv/irqbalance/irqbalance-0.03.tar.gz
> 
> any chance of testing this in an intel lab?
> 
> Greetings,
>      Arjan van de Ven
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/