>> There's no need for me to take the patch I think; now that 3.9-rc1 is
>> out, the serial and driver core trees all have whatever dependencies
>> this series needed, so any patches can go through their usual trees, I
>> think... (Sorry, the context of this discussion was little while ago).
>
>
The fsync call should be ended after flushing the in-device caches.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 269645e..ff018a4 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -13,6 +13,7 @@
The build_free_nid should not add free nids over nm_i->max_nid.
But, there was a hole that invalid free nid was added by the following scenario.
Let's suppose nm_i->max_nid = 150 and the last NAT page has 100 ~ 200 nids.
build_free_nids
- get_current_nat_page loads the last NAT page
-
If the return value of releasepage is equal to zero, the page cannot be
reclaimed.
Instead, we should return 1 in order to reclaim clean pages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 4 +++-
fs/f2fs/node.c | 13 +++--
2 files changed, 6 insertions(+), 11 deletions(-)
diff
Currently, f2fs doesn't reclaim any node pages.
However, if we found that a node page was truncated by checking its block
address with zero during f2fs_write_node_page, we should not skip that node
page and return zero to reclaim it.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 15
When we build new free nids, let's scan the just next NAT page instead of
skipping a couple of previously scanned pages in order to reuse free nids in
there.
Otherwise, we can use too much wide range of nids even though several nids were
deallocated, and also their node pages can be cached in the
This patch reduces redundant locking and unlocking pages during read operations.
In f2fs_readpage, let's use wait_on_page_locked() instead of lock_page.
And then, when we need to modify any data finally, let's lock the page so that
we can avoid lock contention.
[readpage rule]
- The f2fs_readpage
If the node page was truncated, its block address became zero.
This means that we don't need to write the node page, but have to unlock
NODE_WRITE, decrease the number of dirty node pages, and then unlock_page
before returning the f2fs_write_node_page with zero.
Signed-off-by: Jaegeuk Kim
---
2013-03-18 (월), 14:23 +0900, Namjae Jeon:
> 2013/3/18, Jaegeuk Kim :
> > 2013-03-17 (일), 17:27 +0900, Namjae Jeon:
> >> From: Namjae Jeon
> >>
> >> In function check_nid_range, there is no need to trigger BUG_ON and make
> >> kernel stop.
> >> Instead it could just check and indicate the inode
On Sat, Mar 16, 2013 at 02:10:22AM +, Ben Hutchings wrote:
> On Tue, 2013-03-12 at 15:44 -0700, Greg Kroah-Hartman wrote:
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Asias He
> >
> > commit
2013/3/18, Jaegeuk Kim :
> 2013-03-17 (일), 17:27 +0900, Namjae Jeon:
>> From: Namjae Jeon
>>
>> In function check_nid_range, there is no need to trigger BUG_ON and make
>> kernel stop.
>> Instead it could just check and indicate the inode number to be EINVAL.
>> Update the return path in
Hi all,
Changes since 20130315:
New trees: mfd-fixes, vfio-fixes
The ftrace tree gained a conflict against Linus' tree.
The char-misc tree gained a build failure so I used the version from
next-20130315.
The gpio tree still had its build failure for which I reverted a commit.
The arm-soc
Hi Linus !
Here's a few powerpc fixes for 3.9, mostly regressions (though not all
from 3.9 merge window) that we've been hammering into shape over the
last couple of weeks. They fix booting on Cell and G5 among other
things (yes, we've been a bit sloppy with older machines this time
around).
From: Namhyung Kim
It's a per-cpu data structure but missed the __percpu annotation.
Cc: Tejun Heo
Signed-off-by: Namhyung Kim
---
include/linux/perf_event.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
index
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit a64685399181780998281fe07309a94b25dd24c3 upstream.
You cannot resize a RAID0 array (in terms of making the devices
bigger), but the code doesn't entirely stop you.
So:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
This reverts commit 066f289835f09a3f744d6bac96f25e25d20b3ded which was
6a040ce72598159a74969a2d01ab0ba5ee6536b3 upstream.
This was not needed and is not suitable for 3.2.y.
This is the start of the stable review cycle for the 3.2.41 release.
There are 82 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Mar 20 12:00:00 UTC 2013.
Anything
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 838f427955dcfd16858b0108ce29029da0d56a4e upstream.
The ath9k commit 2ef167557c0a26c88162ecffb017bfcc51eb7b29
(ath9k: fix signal strength reporting issues) fixed an issue
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mathieu Desnoyers
commit 8aec0f5d4137532de14e6554fd5dd201ff3a3c49 upstream.
Looking at mm/process_vm_access.c:process_vm_rw() and comparing it to
compat_process_vm_rw() shows that the
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 0720a06a7518c9d0c0125bd5d1f3b6264c55c3dd upstream.
The utf8s_to_utf16s conversion routine needs to be improved. Unlike
its utf16s_to_utf8s sibling, it doesn't accept
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit d3b9d7a9051d7024a93c76a84b2f84b3b66ad6d5 upstream.
A USB 3.0 device can transition to the Inactive state if a U1 or U2 exit
transition fails. The current code in hub_events
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit 2d4fa940f99663c82ba55b2244638833b388e4e2 upstream.
The next patch will refactor the hub port code to rip out the recursive
call to hub_port_reset on a failed hot reset. In
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Axel Lin
commit df069079c153d22adf6c28dcc0b1cf62bba75167 upstream.
Signed-off-by: Axel Lin
Acked-by: Jean Delvare
Signed-off-by: Guenter Roeck
Signed-off-by: Ben Hutchings
---
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit a24a6078754f28528bc91e7e7b3e6ae86bd936d8 upstream.
When a hot reset fails on a USB 3.0 port, the current port reset code
recursively calls hub_port_reset inside
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Kot
commit c00b6856fc642b234895cfabd15b289e76726430 upstream.
Writing a icmp_packet_rr and then reading icmp_packet can lead to kernel
memory corruption, if __user *buf is just below
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sven Eckelmann
commit b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c upstream.
Don't write more than the requested number of bytes of an batman-adv icmp
packet to the userspace buffer. Otherwise
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Laszlo Ersek
commit 08e34eb14fe4cfd934b5c169a7682a969457c4ea upstream.
After a guest is live migrated, the xen-netfront driver emits a gratuitous
ARP message, so that networking hardware on
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guo Chao
commit d646a02a9d44d1421f273ae3923d97b47b918176 upstream.
blkdev_ioctl(GETBLKSIZE) uses i_size_read() to read size of block device.
If we update block size directly, reader may see
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guo Chao
commit b1a6650406875b9097a032eed89af50682fe1160 upstream.
When loopdev is built as module and we pass an invalid parameter,
loop_init() will return directly without deregister misc
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 884ac2978a295b7df3c4a686d3bff6932460 upstream.
There is no hypercall to setup multiple MSI per PCI device.
As such with these two new commits:
-
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
commit 9a5467bf7b6e9e02ec9c3da4e23747c05faeaac6 upstream.
Three errors resulting in kernel memory disclosure:
1/ The structures used for the netlink based crypto algorithm
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 2ca39528c01a933f6689cd6505ce65bd6d68a530 upstream.
When the new signal handlers are set up, the location of sa_restorer is
not cleared, leaking a parent process's address
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit fd7c092e711ebab55b2688d3859d95dfd0301f73 upstream.
Avoid returning a truncated table or status string instead of setting
the DM_BUFFER_FULL_FLAG when the last target of
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 8c958c703ef8804093437959221951eaf0e1e664 upstream.
On LTC2978, only READ_TEMPERATURE is supported. It reports
the internal junction temperature. This register is unpaged.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jiang Liu
commit 08dff7b7d629807dbb1f398c68dd9cd58dd657a1 upstream.
When online_pages() is called to add new memory to an empty zone, it
rebuilds all zone lists by calling
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Conklin
commit a57e82a18779ab8a5e5a1f5841cef937cf578913 upstream.
The Rigblaster Advantage is an amateur radio interface sold by West Mountain
Radio. It contains a cp210x serial
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit b255188f90e2bade1bd11a986dd1ca4861869f4d upstream.
Paolo Pisati reports that IPv6 triggers this warning:
BUG: scheduling while atomic: swapper/0/0/0x4100
Modules
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 0da9dfdd2cd9889201bc6f6f43580c99165cd087 upstream.
This fixes CVE-2013-1792.
There is a race in install_user_keyrings() that can cause a NULL pointer
dereference when
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Wang YanQing
commit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366 upstream.
01:08.0 Communication controller: NetMos Technology PCI 9835 Multi-I/O
Controller (rev 01)
Subsystem: Device
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 66efdc71d95887b652a742a5dae51fa834d71465 upstream.
snd_seq_timer_open() didn't catch the whole error path but let through
if the timer id is a slave. This may lead to Oops
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Amit Shah
commit e84e7a56a3aa2963db506299e29a5f3f09377f9b upstream.
The code currently only supports one virtio-rng device at a time.
Invoking guests with multiple devices causes the guest to
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ley Foon Tan
commit e06c93cacb82dd147266fd1bdb2d0a0bd45ff2c1 upstream.
Add support for Altera 8250/16550 compatible serial port.
Signed-off-by: Ley Foon Tan
Signed-off-by: Greg Kroah-Hartman
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit bdc5c1812cea6efe1aaefb3131fcba28cd0b2b68 upstream.
While shuting down a HVM guest with pci devices passed through we
get this:
pciback :04:00.0: restoring
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Schmiedl
commit 1941138e1c024ecb5bd797d414928d3eb94d8662 upstream.
add support for Cinterion's products AH6 and PLS8 by adding Product IDs
and USB_DEVICE tuples.
Signed-off-by:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 9d2696e658ef4f209955ddaa987d43f1a1bd81a1 upstream.
Properly initialize scatterlist before using it.
Signed-off-by: K. Y. Srinivasan
Signed-off-by: James Bottomley
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit ab4b71644a26d1ab92b987b2fd30e17c25e89f85 upstream.
This reverts commit 200e0d99 ("USB: storage: optimize to match the
Huawei USB storage devices and support new switch
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit 4e0855dff094b0d56d6b5b271e0ce7851cc1e063 upstream.
This patch removes redundant and unbalanced pci_disable_device() from
__e1000_shutdown(). pci_clear_master() is
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Matwey V. Kornilov"
commit be3101c23394af59694c8a2aae6d07f5da62fea5 upstream.
This patch adds support for the Lake Shore Cryotronics devices to
the CP210x driver.
These lines are ported from
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Avinash Patil
commit 3e7a4ff7c5b6423ddb644df9c41b8b6d2fb79d30 upstream.
Maximum delay for waking up card is 50 ms. Because of typo in
counter, this delay goes to 500ms. This patch fixes the
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 5e4ba617c1b584b2e376f31a63bd4e734109318a upstream.
Martin Storsjö reports that the sequence:
ee312ac1vsub.f32s4, s3, s2
ee702ac0
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Tu, Xiaobing"
commit e37736777254ce1abc85493a5cacbefe5983b896 upstream.
When system enters sleep, non-boot CPUs will be disabled.
Cpufreq stats sysfs is created when the CPU is up, but it is
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit a930d8790552658140d7d0d2e316af4f0d76a512 upstream.
If you open a pipe for neither read nor write, the pipe code will not
add any usage counters to the pipe, causing the 'struct
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 208afec4f3be8c51ad6eebe6611dd6d2ad2fa298 upstream.
This bug was introduced back in bitkeeper days in 2003. We use
"dcb->dev_mode" before it has been initialized.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Riemer
commit bbfa57c0f2243a7c31fd248d22e9861a2802cad5 upstream.
If an fsync occurs on a read-only array, we need to send a
completion for the IO and may not increment the active IO
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Boyer
commit 68d929862e29a8b52a7f2f2f86a0600423b093cd upstream.
UEFI variables are typically stored in flash. For various reasons, avaiable
space is typically not reclaimed immediately
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit f528d980c17b8714aedc918ba86e058af914d66b upstream.
When dma_ops are initialized the unity mappings are created. The
init_device_table_dma() function makes sure DMA from all
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 58ebb34c49fcfcaa029e4b1c1453d92583900f9a upstream.
Create_stripe_zones returns an error slightly differently to
raid0_run and to raid0_takeover_*.
The error returned used by
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: James Ralston
commit 77b12bc9cf7b10c7c1a04ca45272fbb4287902d0 upstream.
This patch adds the AHCI-mode SATA Device IDs for the Intel Lynx Point-LP PCH
Signed-off-by: James Ralston
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: James Ralston
commit 151743fd8dfb02956c5184b5f4f0f42677eb75bc upstream.
This patch adds the AHCI-mode SATA Device IDs for the Intel Wellsburg PCH
Signed-off-by: James Ralston
Signed-off-by:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Seiji Aguchi
commit d80a361d779a9f19498943d1ca84243209cd5647 upstream.
[Issue]
As discussed in a thread below, Running out of space in EFI isn't a well-tested
scenario.
And we wouldn't
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Seth Heasley
commit 29e674dd5c8e781589f09c3ee139c80f6da274e4 upstream.
This patch adds the AHCI and RAID-mode SATA DeviceIDs for the Intel Avoton SOC.
Signed-off-by: Seth Heasley
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit e8fc41377f5037ff7a661ea06adc05f1daec1548 upstream.
vbios values are wrong leading to colors that are
too bright. Use the default values instead.
Signed-off-by: Alex
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Fernando Luis Vázquez Cao
commit 99d249021abd4341771523ed8dd7946276103432 upstream.
Document what the fix-up is does and make it more robust by ensuring
that it is only applied to the USB
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit e70ab977991964a5a7ad1182799451d067e62669 upstream.
While PROC_CN_MCAST_LISTEN/IGNORE is entirely advisory, it was possible
for an unprivileged user to turn off notifications
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit ce2ac52105aa663056dfc17966ebed1bf93e6e64 upstream.
Kjell Braden reported this oops:
[ 833.211970] BUG: unable to handle kernel NULL pointer dereference at
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Seth Heasley
commit ea4ace66782fc35245133d2766f38d62827761cc upstream.
This patch adds the AHCI-mode SATA DeviceIDs for the Intel Lynx Point PCH.
Signed-off-by: Seth Heasley
Signed-off-by:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Boyer
commit 81fa4e581d9283f7992a0d8c534bb141eb840a14 upstream.
[Problem]
There is a scenario which efi_pstore fails to log messages in a panic case.
- CPUA holds an efi_var->lock in
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit a40e7cf8f06b4e322ba902e4e9f6a6b0c2daa907 upstream.
Commit 9f9c9cbb6057 ("drivers/firmware/dmi_scan.c: fetch dmi version
from SMBIOS if it exists") hoisted the check for
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Rusty Russell
commit f7f154f1246ccc5a0a7e9ce50932627d60a0c878 upstream.
virtio_rng feeds the randomness buffer handed by the core directly
into the scatterlist, since commit
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.
The FH hardware will always write back to the scratch field
in commands, even host commands not just TX commands, which
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 2069d483b39a603a5f3428a19d3b4ac89aa97f48 upstream.
When a value of a vmaster slave control is changed, the ctl change
notification is sometimes ignored. This happens when
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Fernando Luis Vázquez Cao
commit a464918419f94a0043d2f549d6defb4c3f69f68a upstream.
Some Vaio desktop computers, among them the VGC-LN51JGB multimedia PC, have
a RF receiver, multi-interface
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit dbd712c2272764a536e29ad6841dba74989a39d9 upstream.
Peak attributes were not initialized and cleared correctly.
Also, temp2_max is only supported on page 0 and thus does
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit f366fccd0809f13ba20d64cae3c83f7338c88af7 upstream.
We read the chip ID from the chip, use it to determine if the chip ID provided
to the driver is correct, and report it
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Sandeen
commit bc178622d40d87e75abc131007342429c9b03351 upstream.
Doing this would reliably fail with -EBUSY for me:
# mount /dev/sdb2 /mnt/scratch; umount /mnt/scratch; mkfs.btrfs -f
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Brown
commit 3e78080f81481aa8340374d5a37ae033c1cf4272 upstream.
Not having power is a pretty serious error so check that we are able to
enable the supply and error out if we can't.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 23cb21092eb9dcec9d3604b68d95192b79915890 upstream.
Add module aliases so that autoloading works correctly if the user
tries to activate "snapshot-origin" or
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ville Syrjälä
commit 4a35f83b2b7c6aae3fc0d1c4554fdc99dc33ad07 upstream.
Restore crtc->fb to the old framebuffer if queue_flip fails.
While at it, kill the pointless intel_fb temp variable.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit f2fe09b055e2549de41fb107b34c60bac4a1b0cf upstream.
Masked out PMXEVTYPER.NSH means that we can't enable profiling at PL2,
regardless of the settings in the HDCR.
This patch
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guo Chao
commit 5370019dc2d2c2ff90e95d181468071362934f3a upstream.
bd_mutex and lo_ctl_mutex can be held in different order.
Path #1:
blkdev_open
blkdev_get
__blkdev_get (hold bd_mutex)
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Marcin Jurkowski
commit 9d1817cab2f030f6af360e961cc69bb1da8ad765 upstream.
On Sat, Mar 02, 2013 at 10:45:10AM +0100, Sven Geggus wrote:
> This is the bad commit I found doing git bisect:
>
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit 0fe51aa5eee51db7c7ecd201d42a977ad79c58b6 upstream.
The EHCI host controller needs to prevent EHCI initialization when the
UHCI or OHCI companion controller is in the middle
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit daec90e7382cbd0e73eb6861109b3da91e5ab1f3 upstream.
Another device using CDC ACM with vendor specific protocol to mark
serial functions.
Signed-off-by: Bjørn Mork
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit db05021d49a994ee40a9735d9c3cb0060c9babb8 upstream.
The prompt to enable DYNAMIC_FTRACE (the ability to nop and
enable function tracing at run time) had a confusing
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 2d90e63603ac235aecd7d20e234616e0682c8b1f upstream.
4 ports; AT/PPP is standard CDC-ACM. The other three (added by this
patch) are QCDM/DIAG, possibly GPS, and unknown.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Scott Ashcroft
commit d13402a4a944e72612a9ec5c9190e35717c02a9d upstream.
I've managed to find an 8 port version of the card 4 port card which was
discussed here:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit feca7746d5d9e84b105a613b7f3b6ad00d327372 upstream.
This patch (as1661) fixes a rather obscure bug in ehci-hcd. In a
couple of places, the driver compares the DMA address
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Malcolm Priestley
commit 6987a6dabfc40222ef767f67b57212fe3a0225fb upstream.
Remove usb_put_dev from vt6656_suspend and usb_get_dev
from vt6566_resume.
These are not normally in suspend/resume
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Bolle
commit 827aa0d36d486f359808c8fb931cf7a71011a09d upstream.
This could have been either ARCH_S5P64X0 or CPU_S5P6450. Looking at
commit 2555e663b367b8d555e76023f4de3f6338c28d6c ("ARM:
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit c0f5ecee4e741667b2493c742b60b6218d40b3aa upstream.
The buffer for responses must not overflow.
If this would happen, set a flag, drop the data and return
an error after
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
When decnet is built as a module a simple:
echo 0.0 >/proc/sys/net/decnet/node_address
results in most of the sysctl entries under /proc/sys/net/decnet and
Hi all,
Today's linux-next merge of the tegra tree got a conflict in
drivers/clocksource/tegra20_timer.c between commit 1d16cfb3aeba
("clocksource: tegra20: use the device_node pointer passed to init") from
the arm-soc tree and commit 6f88fb8af6c6 ("clocksource: tegra: move to
of_clk_get") from
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 8d0c2d10dd72c5292eda7a06231056a4c972e4cc upstream.
ext3_msg() takes the printk prefix as the second parameter and the
format string as the third parameter. Two
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Zykov
commit 64325a3be08d364a62ee8f84b2cf86934bc2544a upstream.
The root of problem is carelessly zeroing pointer(in function
__tty_buffer_flush()),
when another thread can use it. It
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 5a7a613a47a715711b3f2d3322a0eac21d459166 upstream.
Commit 73ca100 broke the code that prevents the client from deleting
a silly renamed dentry. This affected "delete on
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit a9a6b52ee1baa865283a91eb8d443ee91adfca56 upstream.
If the socket is full, we're better off just waiting until it empties,
or until the connection is broken. The reason
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit a3d63cadbad97671d740a9698acc2c95d1ca6e79 upstream.
RSSI is being stored internally as s8 in several places. The indication
of an unset RSSI value, ATH_RSSI_DUMMY_MARKER,
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 1cba0cdf5e4dbcd9e5fa5b54d7a028e55e2ca057 upstream.
__btrfs_close_devices() clones btrfs device structs with
memcpy(). Some of the fields in the clone are reinitialized,
On 18/03/2013, at 10:48 AM, Will Deacon wrote:
Due to all of the goodness being packed into today's kernels, the
resulting image isn't as slim as it once was.
In light of this, don't pass -msmall-data to the tools, which
results in
link failures due to impossible relocations when compiling
Hi Stephen,
Today's linux-next merge of the bcm2835 tree got a conflict in
arch/arm/Kconfig.debug between commit 29c9b7be7574 ("ARM: cns3xxx: move
debug_ll code to include/debug/") from the arm-soc tree and commit
f1ac922dec7e ("ARM: bcm2835: convert to multi-platform") from the bcm2835
tree.
I
1 - 100 of 658 matches
Mail list logo
