1 commit 8d9a79dd5bb0ceba3838fedab9664eeaf210a009
2 Author: Oliver Pinter <oliver.pntr@gmail.com>
3 Date: Wed Apr 2 19:30:05 2008 +0200
7 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
9 commit 0227b57719a85762471efc8bd2d5daf0044aac08
10 Author: andrew.patterson@hp.com <andrew.patterson@hp.com>
11 Date: Sat Apr 5 14:41:08 2008 +0200
13 MCA when shutting down tulip quad-NIC
15 Shutting down the network causes an MCA because of an IO TLB error when
16 a DEC quad 10/100 card is in any slot. This problem was originally seen
19 Acked-by: Olaf Kirch <okir@suse.de>
20 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
22 drivers/net/tulip/tulip_core.c | 4 ++++
23 1 file changed, 4 insertions(+)
25 commit 2d45c9f2d6864599795ad7e5a1d963c810a41862
26 Author: Joe Korty <joe.korty@ccur.com>
27 Date: Wed Mar 5 15:04:59 2008 -0800
29 slab: NUMA slab allocator migration bugfix
31 NUMA slab allocator cpu migration bugfix
33 The NUMA slab allocator (specifically, cache_alloc_refill)
34 is not refreshing its local copies of what cpu and what
35 numa node it is on, when it drops and reacquires the irq
36 block that it inherited from its caller. As a result
37 those values become invalid if an attempt to migrate the
38 process to another numa node occured while the irq block
41 The solution is to make cache_alloc_refill reload these
42 variables whenever it drops and reacquires the irq block.
44 The error is very difficult to hit. When it does occur,
45 one gets the following oops + stack traceback bits in
46 check_spinlock_acquired:
48 kernel BUG at mm/slab.c:2417
49 cache_alloc_refill+0xe6
53 This patch was developed against 2.6.23, ported to and
54 compiled-tested only against 2.6.25-rc4.
56 Signed-off-by: Joe Korty <joe.korty@ccur.com>
57 Signed-off-by: Christoph Lameter <clameter@sgi.com>
58 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
60 commit 46340efe3e4d0f5cd48bbba6339f86b14732600c
61 Author: NeilBrown <neilb@suse.de>
62 Date: Wed Feb 6 01:40:00 2008 -0800
64 md: fix an occasional deadlock in raid5
66 raid5's 'make_request' function calls generic_make_request on underlying
67 devices and if we run out of stripe heads, it could end up waiting for one of
68 those requests to complete. This is bad as recursive calls to
69 generic_make_request go on a queue and are not even attempted until
70 make_request completes.
72 So: don't make any generic_make_request calls in raid5 make_request until all
73 waiting has been done. We do this by simply setting STRIPE_HANDLE instead of
74 calling handle_stripe().
76 If we need more stripe_heads, raid5d will get called to process the pending
77 stripe_heads which will call generic_make_request from a
79 This change by itself causes a performance hit. So add a change so that
80 raid5_activate_delayed is only called at unplug time, never in raid5. This
81 seems to bring back the performance numbers. Calling it in raid5d was
86 How about we queue it for 2.6.25-rc1 and then about when -rc2 comes out,
87 we queue it for 2.6.24.y?
89 Acked-by: Dan Williams <dan.j.williams@intel.com>
90 Signed-off-by: Neil Brown <neilb@suse.de>
91 Tested-by: dean gaudet <dean@arctic.org>
92 Cc: <stable@kernel.org>
93 Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
94 Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
95 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
97 commit 88af5e7a00f3bfe70a4dbc0c6b0d076572952ffb
98 Author: Steve French <sfrench@us.ibm.com>
99 Date: Sat Apr 5 14:41:06 2008 +0200
101 Fix sign mount option and sign proc config setting
103 Patch mainline: 2.6.23-rc1
105 Backported the fix (2.6.23-rc1) from Steve French. The original patch removes
106 few commented functions (which are not required) as part of this fix, backport
107 also does the same to retain compatibility.
109 We were checking the wrong (old) global variable to determine
110 whether to override server and force signing on the SMB
113 Backported-to-2.6.22.y-by: Suresh Jayaraman <sjayaraman@suse.de>
114 Acked-by: Dave Kleikamp <shaggy@austin.ibm.com>
115 Signed-off-by: Steve French <sfrench@us.ibm.com>
116 Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de>
117 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
119 commit eca993ae9ba2c5009c480a4dba75d156a12bf6ed
120 Author: Steve French <sfrench@us.ibm.com>
121 Date: Tue Nov 13 22:41:37 2007 +0000
123 Fix buffer overflow if server sends corrupt response to small
125 [CIFS] Fix buffer overflow if server sends corrupt response to small
128 In SendReceive() function in transport.c - it memcpy's
129 message payload into a buffer passed via out_buf param. The function
130 assumes that all buffers are of size (CIFSMaxBufSize +
131 MAX_CIFS_HDR_SIZE) , unfortunately it is also called with smaller
132 (MAX_CIFS_SMALL_BUFFER_SIZE) buffers. There are eight callers
133 (SMB worker functions) which are primarily affected by this change:
135 TreeDisconnect, uLogoff, Close, findClose, SetFileSize, SetFileTimes,
138 CC: Dave Kleikamp <shaggy@austin.ibm.com>
139 CC: Przemyslaw Wegrzyn <czajnik@czajsoft.pl>
140 Acked-by: Jeff Layton <jlayton@redhat.com>
141 Signed-off-by: Steve French <sfrench@us.ibm.com>
142 Acked-by: Jeff Mahoney <jeffm@suse.com>
143 Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>