arch/sparc64/kernel/trampoline.S | 18 ++-
drivers/acpi/button.c | 3
drivers/acpi/dock.c | 5 -
drivers/acpi/video.c | 123 ++++++++++++++-----------
drivers/edac/cell_edac.c | 2
drivers/gpio/gpiolib.c | 2
drivers/i2c/busses/scx200_i2c.c | 1
drivers/media/dvb/frontends/s5h1411.c | 35 +++++--
drivers/media/video/pvrusb2/pvrusb2-encoder.c | 4
drivers/net/wireless/libertas/scan.c | 4
drivers/scsi/qla2xxx/qla_gs.c | 6 +
fs/ext2/dir.c | 60 +++++++-----
fs/ext3/dir.c | 10 +-
fs/ext4/dir.c | 11 +-
include/linux/sched.h | 2
include/math-emu/op-common.h | 17 ++-
include/net/scm.h | 5 -
net/core/dev.c | 27 +----
net/core/rtnetlink.c | 2
net/core/scm.c | 24 ++++
net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c | 2
net/ipv4/netfilter/nf_nat_snmp_basic.c | 1
net/ipv6/tcp_ipv6.c | 2
net/netfilter/xt_iprange.c | 8 -
security/commoncap.c | 6 -
sound/core/control.c | 4
26 files changed, 245 insertions(+), 139 deletions(-)
New commits:
commit 63e0e67b17dc233f93f709610971bbfadc97f75e
Author: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Date: Mon Nov 10 11:18:24 2008 -0800
Linux 2.6.26.8
commit fda28f0c717d958e3a29fcb4bcb5e95ae8bbb4a2
Author: Patrick McHardy <[EMAIL PROTECTED]>
Date: Wed Oct 22 19:41:31 2008 +0200
netfilter: restore lost ifdef guarding defrag exception
netfilter: restore lost #ifdef guarding defrag exception
Upstream commit 38f7ac3eb:
Nir Tzachar <[EMAIL PROTECTED]> reported a warning when sending
fragments over loopback with NAT:
[ 6658.338121] WARNING: at net/ipv4/netfilter/nf_nat_standalone.c:89
nf_nat_fn+0x33/0x155()
The reason is that defragmentation is skipped for already tracked
connections.
This is wrong in combination with NAT and ip_conntrack actually had some
ifdefs
to avoid this behaviour when NAT is compiled in.
The entire "optimization" may seem a bit silly, for now simply restoring the
lost #ifdef is the easiest solution until we can come up with something
better.
Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 27caba5caf0f8ba55abbee157b5b96487bae1883
Author: Ilpo Järvinen <[EMAIL PROTECTED]>
Date: Wed Oct 22 19:41:29 2008 +0200
netfilter: snmp nat leaks memory in case of failure
netfilter: snmp nat leaks memory in case of failure
Upstream commit 311670f3e:
Signed-off-by: Ilpo Jarvinen <[EMAIL PROTECTED]>
Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]>
commit 2eac9443c4b027d841adbbf0e364d97538505f05
Author: Alexey Dobriyan <[EMAIL PROTECTED]>
Date: Wed Oct 22 19:41:28 2008 +0200
netfilter: xt_iprange: fix range inversion match
netfilter: xt_iprange: fix range inversion match
Upstream commit 6def1eb48:
Inverted IPv4 v1 and IPv6 v0 matches don't match anything since 2.6.25-rc1!
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
Acked-by: Jan Engelhardt <[EMAIL PROTECTED]>
Signed-off-by: Patrick McHardy <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 4bdaa73e7d66b73d32a75beaf38ddf96ca6f8325
Author: Shaohua Li <[EMAIL PROTECTED]>
Date: Thu Nov 6 14:18:55 2008 -0500
ACPI: dock: avoid check _STA method
commit 8b59560a3baf2e7c24e0fb92ea5d09eca92805db upstream.
ACPI: dock: avoid check _STA method
In some BIOSes, every _STA method call will send a notification again,
this cause freeze. And in some BIOSes, it appears _STA should be called
after _DCK. This tries to avoid calls _STA, and still keep the device
present check.
http://bugzilla.kernel.org/show_bug.cgi?id=10431
Signed-off-by: Shaohua Li <[EMAIL PROTECTED]>
Signed-off-by: Len Brown <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit a133c85cd28b3fe09fa567bbd1e3a6e23b027c2c
Author: Julia Jomantaite <[EMAIL PROTECTED]>
Date: Mon Oct 27 23:45:56 2008 -0400
ACPI: video: fix brightness allocation
upstream commit 469778c1740fcf3113498b6fdf4559bdec25c58f
Thanks to Arjan for spotting this
http://www.kerneloops.org/search.php?search=acpi_video_switch_brightness
and suggesting it for .stable
Fix use of uninitialized device->brightness.
Signed-off-by: Julia Jomantaite <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Acked-by: Zhang Rui <[EMAIL PROTECTED]>
Signed-off-by: Len Brown <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit f0d6570e2215dcdb93afc65564be6676456ce696
Author: Andrea Shepard <[EMAIL PROTECTED]>
Date: Sun Oct 19 23:33:03 2008 -0700
sparc64: Fix race in arch/sparc64/kernel/trampoline.S
[ Upstream commit e0037df3852b4b60edbe01f70f4968e4a9fdb272 ]
Make arch/sparc64/kernel/trampoline.S in 2.6.27.1 lock prom_entry_lock
when calling the PROM. This prevents a race condition that I observed
causing a hang on startup on a 12-CPU E4500.
I am not subscribed to this list, so please CC me on replies.
Signed-off-by: Andrea Shepard <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 0cba8ac12e0720b32f03005b8c0113e85fadbd50
Author: Kumar Gala <[EMAIL PROTECTED]>
Date: Tue Oct 21 22:19:00 2008 -0700
math-emu: Fix signalling of underflow and inexact while packing result.
[ Upstream commit 930cc144a043ff95e56b6888fa51c618b33f89e7 ]
I'm trying to move the powerpc math-emu code to use the include/math-emu
bits.
In doing so I've been using TestFloat to see how good or bad we are
doing. For the most part the current math-emu code that PPC uses has
a number of issues that the code in include/math-emu seems to solve
(plus bugs we've had for ever that no one every realized).
Anyways, I've come across a case that we are flagging underflow and
inexact because we think we have a denormalized result from a double
precision divide:
000.FFFFFFFFFFFFF / 3FE.FFFFFFFFFFFFE
soft: 001.0000000000000 ..... syst: 001.0000000000000 ...ux
What it looks like is the results out of FP_DIV_D are:
D:
sign: 0
mantissa: 01000000 00000000
exp: -1023 (0)
The problem seems like we aren't normalizing the result and bumping the exp.
Now that I'm digging into this a bit I'm thinking my issue has to do with
the fix DaveM put in place from back in Aug 2007 (commit
405849610fd96b4f34cd1875c4c033228fea6c0f):
[MATH-EMU]: Fix underflow exception reporting.
2) we ended up rounding back up to normal (this is the case where
we set the exponent to 1 and set the fraction to zero), this
should set inexact too
...
Another example, "0x0.0000000000001p-1022 / 16.0", should signal both
inexact and underflow. The cpu implementations and ieee1754
literature is very clear about this. This is case #2 above.
Here is the distilled glibc test case from Jakub Jelinek which prompted that
commit:
--------------------
#include <float.h>
#include <fenv.h>
#include <stdio.h>
volatile double d = DBL_MIN;
volatile double e = 0x0.0000000000001p-1022;
volatile double f = 16.0;
int
main (void)
{
printf ("%x\n", fetestexcept (FE_UNDERFLOW));
d /= f;
printf ("%x\n", fetestexcept (FE_UNDERFLOW));
e /= f;
printf ("%x\n", fetestexcept (FE_UNDERFLOW));
return 0;
}
--------------------
It looks like the case I have we are exact before rounding, but think it
looks like the rounding case since it appears as if "overflow is set".
000.FFFFFFFFFFFFF / 3FE.FFFFFFFFFFFFE = 001.0000000000000
I think the following adds the check for my case and still works for the
issue your commit was trying to resolve.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 657f714bcf9209d6fa4497c871633d29cc4131e0
Author: Ilpo Järvinen <[EMAIL PROTECTED]>
Date: Wed Oct 8 14:36:33 2008 -0700
tcpv6: fix option space offsets with md5
[ Upstream commit 53b125779fb0b29e5b316bf3dc7d199e6dcea567 ]
More breakage :-), part of timestamps just were previously
overwritten.
Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 858fac9c58f8a0bd447653e80e06170b46161c89
Author: Herbert Xu <[EMAIL PROTECTED]>
Date: Tue Oct 7 15:50:03 2008 -0700
net: Fix netdev_run_todo dead-lock
[ Upstream commit 58ec3b4db9eb5a28e3aec5f407a54e28f7039c19 ]
Benjamin Thery tracked down a bug that explains many instances
of the error
unregister_netdevice: waiting for %s to become free. Usage count = %d
It turns out that netdev_run_todo can dead-lock with itself if
a second instance of it is run in a thread that will then free
a reference to the device waited on by the first instance.
The problem is really quite silly. We were trying to create
parallelism where none was required. As netdev_run_todo always
follows a RTNL section, and that todo tasks can only be added
with the RTNL held, by definition you should only need to wait
for the very ones that you've added and be done with it.
There is no need for a second mutex or spinlock.
This is exactly what the following patch does.
Signed-off-by: Herbert Xu <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 69e0453ecbaec161673aff629e22297572033d29
Author: Lennart Sorensen <[EMAIL PROTECTED]>
Date: Fri Oct 31 17:05:59 2008 +0100
scx200_i2c: Add missing class parameter
commit 4a029abee0f1d69cb0445657d6fa5a38597bd17d upstream
The scx200_i2c driver is missing the .class parameter, which means no
i2c drivers are willing to probe for devices on the bus and attach to
them.
Signed-off-by: Len Sorensen <[EMAIL PROTECTED]>
Signed-off-by: Jean Delvare <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit fac229f3dcd33ed79adbda06badc802f81389485
Author: Devin Heitmueller <[EMAIL PROTECTED]>
Date: Sun Nov 2 23:04:38 2008 -0500
DVB: s5h1411: Power down s5h1411 when not in use
commit 11fc9a4a440112b5afc1a99d86ba92d70205a688 upstream.
DVB: s5h1411: Power down s5h1411 when not in use
Power down the s5h1411 demodulator when not in use
(on the Pinnacle 801e, this brings idle power from
123ma down to 84ma).
Signed-off-by: Devin Heitmueller <[EMAIL PROTECTED]>
Acked-by: Steven Toth <[EMAIL PROTECTED]>
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 05cc17f976602786e7645bdad5226d4b4b1d5bfc
Author: Devin Heitmueller <[EMAIL PROTECTED]>
Date: Sun Nov 2 23:04:36 2008 -0500
DVB: s5h1411: Perform s5h1411 soft reset after tuning
commit f0d041e50bc6c8a677922d72b010f80af9b23b18 upstream.
DVB: s5h1411: Perform s5h1411 soft reset after tuning
If you instruct the tuner to change frequencies, it can take up to 2500ms to
get a demod lock. By performing a soft reset after the tuning call (which
is consistent with how the Pinnacle 801e Windows driver behaves), you get
a demod lock inside of 300ms
Signed-off-by: Devin Heitmueller <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
Acked-by: Steven Toth <[EMAIL PROTECTED]>
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 8aa3b2b7b7defa8cce96b2e3051b10608175768d
Author: Steven Toth <[EMAIL PROTECTED]>
Date: Sun Nov 2 23:04:33 2008 -0500
DVB: s5h1411: bugfix: Setting serial or parallel mode could destroy bits
commit 1af46b450fa49c57d73764d66f267335ccd807e2 upstream.
DVB: s5h1411: bugfix: Setting serial or parallel mode could destroy bits
Adding a serialmode function to read/and/or/write the register for safety.
Signed-off-by: Steven Toth <[EMAIL PROTECTED]>
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit bcf3b9fc11b7709f058c4b75a4b19a88620236c5
Author: Boris Dores <[EMAIL PROTECTED]>
Date: Sun Nov 2 23:04:30 2008 -0500
V4L: pvrusb2: Keep MPEG PTSs from drifting away
commit 3f93d1adca658201c64251c43a147cc79d468c3f upstream.
V4L: pvrusb2: Keep MPEG PTSs from drifting away
This change was empirically figured out by Boris Dores after
empirically comparing against behavior in the Windows driver.
Signed-off-by: Mike Isely <[EMAIL PROTECTED]>
Signed-off-by: Mauro Carvalho Chehab <[EMAIL PROTECTED]>
Signed-off-by: Michael Krufky <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit a5069282922b9ce9b1db1b3a196ef6df958d95d5
Author: Guillem Jover <[EMAIL PROTECTED]>
Date: Tue Oct 28 01:34:27 2008 -0400
ACPI: Always report a sync event after a lid state change
upstream commit df316e939100e789b3c5d4d102619ccf5834bd00
Currently not always an EV_SYN event is reported to userland
after the EV_SW SW_LID event has been sent. This is easy to verify
by using âinput-eventsâ from input-utils and just closing and opening
the lid.
Signed-off-by: Guillem Jover <[EMAIL PROTECTED]>
Acked-by: Dmitry Torokhov <[EMAIL PROTECTED]>
Signed-off-by: Len Brown <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 8f9f0e59f77df62a7f7c58adee08831e78e506aa
Author: Takashi Iwai <[EMAIL PROTECTED]>
Date: Sun Sep 7 12:51:13 2008 +0200
ALSA: use correct lock in snd_ctl_dev_disconnect()
commit d8009882e9f5e1a76986c741f071edd2ad760c97 upstream
The lock used in snd_ctl_dev_disconnect() should be card->ctl_files_rwlock
for protection of card->ctl_files entries, instead of card->controls_rwsem.
Reported-by: Vegard Nossum <[EMAIL PROTECTED]>
Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]>
Signed-off-by: Jaroslav Kysela <[EMAIL PROTECTED]>
Cc: Chris Wedgwood <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit d98555a502f4a5d714b99b697942df256b0633ad
Author: Serge Hallyn <[EMAIL PROTECTED]>
Date: Thu Oct 30 11:52:23 2008 -0500
file caps: always start with clear bprm->caps_*
commit 3318a386e4ca68c76e0294363d29bdc46fcad670 upstream
While Linux doesn't honor setuid on scripts. However, it mistakenly
behaves differently for file capabilities.
This patch fixes that behavior by making sure that get_file_caps()
begins with empty bprm->caps_*. That way when a script is loaded,
its bprm->caps_* may be filled when binfmt_misc calls prepare_binprm(),
but they will be cleared again when binfmt_elf calls prepare_binprm()
next to read the interpreter's file capabilities.
Signed-off-by: Serge Hallyn <[EMAIL PROTECTED]>
Acked-by: David Howells <[EMAIL PROTECTED]>
Acked-by: Andrew G. Morgan <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit f53dd684abef20b9c1133548bfb56d91da537e3e
Author: Johannes Berg <[EMAIL PROTECTED]>
Date: Sun Nov 2 19:30:21 2008 +0000
libertas: fix buffer overrun
commit 48735d8d8bd701b1e0cd3d49c21e5e385ddcb077 upstream
If somebody sends an invalid beacon/probe response, that can trash the
whole BSS descriptor. The descriptor is, luckily, large enough so that
it cannot scribble past the end of it; it's well above 400 bytes long.
Signed-off-by: Johannes Berg <[EMAIL PROTECTED]>
Signed-off-by: John W. Linville <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 1e675381c2c443e84ba7bea055017ded1ac8f816
Author: David Miller <[EMAIL PROTECTED]>
Date: Thu Nov 6 00:37:40 2008 -0800
net: Fix recursive descent in __scm_destroy().
commit f8d570a4745835f2238a33b537218a1bb03fc671 and
3b53fbf4314594fa04544b02b2fc6e607912da18 upstream (because once wasn't
good enough...)
__scm_destroy() walks the list of file descriptors in the scm_fp_list
pointed to by the scm_cookie argument.
Those, in turn, can close sockets and invoke __scm_destroy() again.
There is nothing which limits how deeply this can occur.
The idea for how to fix this is from Linus. Basically, we do all of
the fput()s at the top level by collecting all of the scm_fp_list
objects hit by an fput(). Inside of the initial __scm_destroy() we
keep running the list until it is empty.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit 20246fe8e4ea34f2ab556b7c50037b976051cab7
Author: Andrew Vasquez <[EMAIL PROTECTED]>
Date: Tue Oct 21 20:25:04 2008 +0200
SCSI: qla2xxx: Skip FDMI registration on ISP21xx/22xx parts.
commit 031e134e5f95233d80fb1b62fdaf5e1be587597c upstream
Firmware does not have the facilities to issue management server
IOCBs.
Signed-off-by: Andrew Vasquez <[EMAIL PROTECTED]>
Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
Cc: Ferenc Wagner <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit e3cf06d9ba60f5d60e22f41c698346ba34b8212a
Author: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Date: Mon Oct 20 16:50:07 2008 +0000
edac cell: fix incorrect edac_mode
commit 3b274f44d2ca05f719fe39947b6a5293a2dbd8fd upstream
The cell_edac driver is setting the edac_mode field of the csrow's to an
incorrect value, causing the sysfs show routine for that field to go out
of an array bound and Oopsing the kernel when used.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Signed-off-by: Doug Thompson <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit d7b1831d957c4d8fd129ad99d53328be35a3afa5
Author: Eric Sandeen <[EMAIL PROTECTED]>
Date: Wed Oct 22 10:11:52 2008 -0500
ext[234]: Avoid printk floods in the face of directory corruption
(CVE-2008-3528)
This is a trivial backport of the following upstream commits:
- bd39597cbd42a784105a04010100e27267481c67 (ext2)
- cdbf6dba28e8e6268c8420857696309470009fd9 (ext3)
- 9d9f177572d9e4eba0f2e18523b44f90dd51fe74 (ext4)
This addresses CVE-2008-3528
ext[234]: Avoid printk floods in the face of directory corruption
Note: some people thinks this represents a security bug, since it
might make the system go away while it is printing a large number of
console messages, especially if a serial console is involved. Hence,
it has been assigned CVE-2008-3528, but it requires that the attacker
either has physical access to your machine to insert a USB disk with a
corrupted filesystem image (at which point why not just hit the power
button), or is otherwise able to convince the system administrator to
mount an arbitrary filesystem image (at which point why not just
include a setuid shell or world-writable hard disk device file or some
such). Me, I think they're just being silly. --tytso
Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Cc: Eugene Teo <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
commit fa1b284673e834fb814fb0a638d4259e619ac1ec
Author: David Brownell <[EMAIL PROTECTED]>
Date: Mon Oct 20 16:50:10 2008 +0000
gpiolib: fix oops in gpio_get_value_cansleep()
commit 978ccaa8ea5d8c7bf6b676209f2fc126eae6355b upstream
We can get the following oops from gpio_get_value_cansleep() when a GPIO
controller doesn't provide a get() callback:
Unable to handle kernel paging request for instruction fetch
Faulting instruction address: 0x00000000
Oops: Kernel access of bad area, sig: 11 [#1]
[...]
NIP [00000000] 0x0
LR [c0182fb0] gpio_get_value_cansleep+0x40/0x50
Call Trace:
[c7b79e80] [c0183f28] gpio_value_show+0x5c/0x94
[c7b79ea0] [c01a584c] dev_attr_show+0x30/0x7c
[c7b79eb0] [c00d6b48] fill_read_buffer+0x68/0xe0
[c7b79ed0] [c00d6c54] sysfs_read_file+0x94/0xbc
[c7b79ef0] [c008f24c] vfs_read+0xb4/0x16c
[c7b79f10] [c008f580] sys_read+0x4c/0x90
[c7b79f40] [c0013a14] ret_from_syscall+0x0/0x38
It's OK to request the value of *any* GPIO; most GPIOs are bidirectional,
so configuring them as outputs just enables an output driver and doesn't
disable the input logic.
So the problem is that gpio_get_value_cansleep() isn't making the same
sanity check that gpio_get_value() does: making sure this GPIO isn't one
of the atypical "no input logic" cases.
Reported-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=63e0e67b17dc233f93f709610971bbfadc97f75e
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=fda28f0c717d958e3a29fcb4bcb5e95ae8bbb4a2
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=27caba5caf0f8ba55abbee157b5b96487bae1883
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=2eac9443c4b027d841adbbf0e364d97538505f05
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=4bdaa73e7d66b73d32a75beaf38ddf96ca6f8325
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=a133c85cd28b3fe09fa567bbd1e3a6e23b027c2c
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=f0d6570e2215dcdb93afc65564be6676456ce696
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=0cba8ac12e0720b32f03005b8c0113e85fadbd50
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=657f714bcf9209d6fa4497c871633d29cc4131e0
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=858fac9c58f8a0bd447653e80e06170b46161c89
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=69e0453ecbaec161673aff629e22297572033d29
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=fac229f3dcd33ed79adbda06badc802f81389485
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=05cc17f976602786e7645bdad5226d4b4b1d5bfc
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=8aa3b2b7b7defa8cce96b2e3051b10608175768d
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=bcf3b9fc11b7709f058c4b75a4b19a88620236c5
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=a5069282922b9ce9b1db1b3a196ef6df958d95d5
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=8f9f0e59f77df62a7f7c58adee08831e78e506aa
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=d98555a502f4a5d714b99b697942df256b0633ad
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=f53dd684abef20b9c1133548bfb56d91da537e3e
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=1e675381c2c443e84ba7bea055017ded1ac8f816
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=20246fe8e4ea34f2ab556b7c50037b976051cab7
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=e3cf06d9ba60f5d60e22f41c698346ba34b8212a
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=d7b1831d957c4d8fd129ad99d53328be35a3afa5
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=fa1b284673e834fb814fb0a638d4259e619ac1ec
_______________________________________________
svn mailing list
[email protected]
http://mailman.vyatta.com/mailman/listinfo/svn
