linux-toradex.git/include, branch v2.6.20.3

Fix timewait jiffies

2007-03-13T18:26:47+00:00

[INET]: twcal_jiffie should be unsigned long, not int

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

conntrack: fix {nf, ip}_ct_iterate_cleanup endless loops

2007-03-13T18:26:45+00:00

[NETFILTER]: conntrack: fix {nf,ip}_ct_iterate_cleanup endless loops

Fix {nf,ip}_ct_iterate_cleanup unconfirmed list handling:

- unconfirmed entries can not be killed manually, they are removed on
  confirmation or final destruction of the conntrack entry, which means
  we might iterate forever without making forward progress.

  This can happen in combination with the conntrack event cache, which
  holds a reference to the conntrack entry, which is only released when
  the packet makes it all the way through the stack or a different
  packet is handled.

- taking references to an unconfirmed entry and using it outside the
  locked section doesn't work, the list entries are not refcounted and
  another CPU might already be waiting to destroy the entry

What the code really wants to do is make sure the references of the hash
table to the selected conntrack entries are released, so they will be
destroyed once all references from skbs and the event cache are dropped.

Since unconfirmed entries haven't even entered the hash yet, simply mark
them as dying and skip confirmation based on that.

Signed-off-by: Patrick McHardy 
Signed-off-by: Greg Kroah-Hartman

ATA: convert GSI to irq on ia64

2007-03-09T18:50:32+00:00

If an ATA drive uses legacy mode, ata driver will choose 14 and 15 as the
fixed irq number.  On ia64 platform, such numbers are GSI and should be
converted to irq vector.

Signed-off-by: Zhang Yanmin 
Cc: Jeff Garzik 
Cc: Tony Luck 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

throttle_vm_writeout(): don't loop on GFP_NOFS and GFP_NOIO allocations

2007-03-09T18:50:31+00:00

throttle_vm_writeout() is designed to wait for the dirty levels to subside. 
But if the caller holds IO or FS locks, we might be holding up that writeout.

So change it to take a single nap to give other devices a chance to clean some
memory, then return.

Cc: Nick Piggin 
Cc: OGAWA Hirofumi 
Cc: Kumar Gala 
Cc: Pete Zaitcev 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

lockdep: forward declare struct task_struct

2007-03-09T18:50:30+00:00

3117df0453828bd045c16244e6f50e5714667a8a causes this:

In file included from arch/s390/kernel/early.c:13:
include/linux/lockdep.h:300: warning:
		"struct task_struct" declared inside parameter list
include/linux/lockdep.h:300:
		warning: its scope is only this definition or
		declaration, which is probably not what you want

Acked-by: Ingo Molnar 
Cc: Martin Schwidefsky 
Signed-off-by: Heiko Carstens 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

ufs: restore back support of openstep

2007-03-09T18:50:29+00:00

This is a fix of regression, which triggered by ~2.6.16.

Patch with name ufs-directory-and-page-cache-from-blocks-to-pages.patch: in
additional to conversation from block to page cache mechanism added new
checks of directory integrity, one of them that directory entry do not
across directory chunks.

But some kinds of UFS: OpenStep UFS and Apple UFS (looks like these are the
same filesystems) have different directory chunk size, then common
UFSes(BSD and Solaris UFS).

So this patch adds ability to works with variable size of directory chunks,
and set it for ufstype=openstep to right size.

Tested on darwin ufs.

Signed-off-by: Evgeniy Dushistov 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

Revert "[PATCH] LOG2: Alter get_order() so that it can make use of ilog2() on a constant"

2007-03-09T18:50:28+00:00

Revert "[PATCH] LOG2: Alter get_order() so that it can make use of ilog2() on a constant"

This reverts commit 39d61db0edb34d60b83c5e0d62d0e906578cc707.

The commit was buggy in multiple ways:
 - the conversion to ilog2() was incorrect to begin with
 - it tested the wrong #defines, so on all architectures but FRV you'd
   never see the bug except for constant arguments.
 - the new "get_order()" macro used its arguments multiple times, and
   didn't even parenthesize them properly
 - despite the comments, it was not true that you could use it for
   constant initializers, since not all architectures even use the
   generic page.h header file.

All of the problems are individually fixable, but it all boils down to:
better just revert it, and re-do it from scratch.

Cc: David Howells 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mackerras 
Cc: Andrew Morton 
Cc: David Woodhouse 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

mmc: Power quirk for ENE controllers

2007-03-09T18:50:24+00:00

mmc: Power quirk for ENE controllers

Support for these devices was broken for 2.6.18-rc1 and later by commit
146ad66eac836c0b976c98f428d73e1f6a75270d, which added voltage level support.

This restores the previous behaviour for these devices by ensuring that when
the voltage is changed, only one write to set the voltage is performed.

It may be that both writes are needed if the voltage is being changed between
two non-zero values or that it's safe to ensure that only one write is done
if the hardware only supports one voltage; I don't know whether either is the
case nor can I test since I have only the one SD reader (1524:0550), and it
supports just the one voltage.

Signed-off-by: Darren Salt 
Signed-off-by: Pierre Ossman 
Signed-off-by: Greg Kroah-Hartman

x86: Don't require the vDSO for handling a.out signals

2007-03-09T18:50:22+00:00

x86: Don't require the vDSO for handling a.out signals

and in other strange binfmts. vDSO is not necessarily mapped there.

This fixes signals in a.out programs

Signed-off-by: Andi Kleen 
Signed-off-by: Greg Kroah-Hartman

x86_64: Fix wrong gcc check in bitops.h

2007-03-09T18:50:22+00:00

gcc 5.0 will likely not have the constraint problem

Signed-off-by: Andi Kleen 
Signed-off-by: Greg Kroah-Hartman