On Fri, 2012-09-28 at 13:33 -0700, Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Vinicius Costa Gomes
>
> commit 78c04c0bf52360dc2f7185e99c8e9aa05d73ae5a upstream.
>
> For example, when a usb reset is
Hey Thomas,
I just updated my fortglx/3.7/time branch to include and resolve
the collision with Arnd's LATCH fix. Just wanted to give you a heads up
so you weren't surprised by the additional change.
Full pull request below.
thanks
-john
The following changes since commit
Hi Mark,
On Wed, Sep 26, 2012 at 06:00:29PM +0100, Mark Brown wrote:
> Signed-off-by: Mark Brown
> ---
> drivers/mfd/wm5110-tables.c | 96
> ++-
> 1 file changed, 95 insertions(+), 1 deletion(-)
Applied as well, thanks.
Cheers,
Samuel.
--
Intel Open
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
[ Upstream commit 1485348d2424e1131ea42efc033cbd9366462b01 ]
Cache the device gso_max_segs in sock::sk_gso_max_segs and use it to
limit the size of TSO skbs. This avoids the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hiroaki SHIMODA
[ Upstream commit 696ecdc10622d86541f2e35cc16e15b6b3b1b67e ]
gact_rand array is accessed by gact->tcfg_ptype whose value
is assumed to less than MAX_RAND, but any range checks
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Khoroshilov
[ Upstream commit 7364e445f62825758fa61195d237a5b8ecdd06ec ]
Do not leak memory by updating pointer with potentially NULL realloc return
value.
Found by Linux Driver
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
[ Upstream commit 4acd4945cd1e1f92b20d14e349c6c6a52acbd42d ]
Cong Wang reports that lockdep detected suspicious RCU usage while
enabling IPV6 forwarding:
[ 1123.310275]
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit e862f1a9b7df4e8196ebec45ac62295138aa3fc2 ]
The ATM code fails to initialize the two padding bytes of struct
sockaddr_atmpvc inserted for alignment. Add an
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wu Fengguang
[ Upstream commit 77f00f6324cb97cf1df6f9c4aaeea6ada23abdb2 ]
Fix a buffer overflow bug by removing the revision and printk.
[ 22.016214] isdnloop-ISDN-driver Rev 1.11.6.7
[
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 3c0c5cfdcd4d69ffc4b9c0907cec99039f30a50a ]
The ATM code fails to initialize the two padding bytes of struct
sockaddr_atmpvc inserted for alignment. Add an
Hi Mark,
On Wed, Sep 26, 2012 at 06:00:28PM +0100, Mark Brown wrote:
> It can misreport.
>
> Signed-off-by: Mark Brown
> ---
> drivers/mfd/arizona-irq.c |1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 9ad2de43f1aee7e7274a4e0d41465489299e344b ]
The RFCOMM code fails to initialize the key_size member of struct
bt_security before copying it to userland -- that
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 792039c73cf176c8e39a6e8beef2c94ff46522ed ]
The L2CAP code fails to initialize the l2_bdaddr_type member of struct
sockaddr_l2 and the padding byte added for
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 3592aaeb80290bda0f2cf0b5456c97bfc638b192 ]
The LLC code wrongly returns 0, i.e. "success", when the socket is
zapped. Together with the uninitialized uaddrlen
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 9344a972961d1a6d2c04d9008b13617bcb6ec2ef ]
The RFCOMM code fails to initialize the trailing padding byte of struct
sockaddr_rc added for alignment. It that
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 7b07f8eb75aa3097cdfd4f6eac3da49db787381d ]
The CCID3 code fails to initialize the trailing padding bytes of struct
tfrc_tx_info added for alignment on 64 bit
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 3f68ba07b1da811bf383b4b701b129bfcb2e4988 ]
The HCI code fails to initialize the hci_channel member of struct
sockaddr_hci and that for leaks two bytes kernel
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Leblond
[ Upstream commit c0de08d04215031d68fa13af36f347a6cfa252ca ]
If a packet is emitted on one socket in one group of fanout sockets,
it is transmitted again. It is thus read again
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
[ Upstream commit 20e1db19db5d6b9e4e83021595eab0dc8f107bef ]
Non-root user-space processes can send Netlink messages to other
processes that are well-known for being
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit e0e3cea46d31d23dc40df0a49a7a2c04fe8edfea ]
Pablo Neira Ayuso discovered that avahi and
potentially NetworkManager accept spoofed Netlink messages because of a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Claudiu Manoil
[ Upstream commit e2c53be223aca36cf93eb6a0f6bafa079e78f52b ]
Commit -
"b852b72 gianfar: fix bug caused by
87c288c6e9aa31720b72e2bc2d665e24e1653c3e"
disables by default (on mac
On 09/28/2012 02:36 PM, Arnd Bergmann wrote:
Patch a7ea3bbf5d "time/jiffies: Allow CLOCK_TICK_RATE to be undefined"
breaks the compilation of targets that rely on the LATCH definition,
because of recursive header file inclusion not defining CLOCK_TICK_RATE
before it is checked here.
This fixes
On 09/28/2012 03:36 PM, Arnd Bergmann wrote:
> On a normal build, we get output from both make and from dtc
> about each file that is being processed.
>
> DTC arch/arm/boot/vexpress-v2p-ca5s.dtb
> DTC: dts->dtb on file
> "/git/arnd/linux-arm/arch/arm/boot/dts/vexpress-v2p-ca5s.dts"
>
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Krause
[ Upstream commit 43da5f2e0d0c69ded3d51907d9552310a6b545e8 ]
The implementation of dev_ifconf() for the compat ioctl interface uses
an intermediate ifc structure allocated in
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Yuval Mintz
[ Upstream commit 5c879d2094946081af934739850c7260e8b25d3c ]
Commit c3def943c7117d42caaed3478731ea7c3c87190e have added support for
new pci ids of the 57840 board, while failing
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jesse Gross
[ Upstream commit 7fe99e2d434eafeac0c57b279a77e5de39212636 ]
It's possible that packets that are sent on internal devices (from
the OVS perspective) have already traversed the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 6889125b8b4e09c5e53e6ecab3433bed1ce198c9 upstream.
powernowk8_target() runs off a per-cpu work item and if the
cpufreq_policy->cpu is different from the current one, it
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Stephen M. Cameron"
commit 2453f5f992717251cfadab6184fbb3ec2f2e8b40 upstream.
If a command completes with a status of CMD_PROTOCOL_ERR, this
information should be conveyed to the SCSI mid
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit b161dfa6937ae46d50adce8a7c6b12233e96e7bd upstream.
IBM reported a soft lockup after applying the fix for the rename_lock
deadlock. Commit c83ce989cb5f ("VFS: Fix the nfs
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
commit 8335eafc2859e1a26282bef7c3d19f3d68868b8a upstream.
After calling into the lower filesystem to do a rename, the lower target
inode's attributes were not copied up to the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
commit 4c054ba63ad47ef244cfcfa1cea38134620a5bae upstream.
This patch fixes a long-standing bug with SCSI overflow handling
where se_cmd->data_length was incorrectly being
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Brown
commit 70b0476a2394de4f4e32e0b67288d80ff71ca963 upstream.
'make dtbs' in a clean tree will try running the dtc before actually
building it. Make these rules depend upon the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 2b2040af0b64cd93e5d4df2494c4486cf604090d upstream.
get_user may fail to load from the provided __user address due to an
unhandled fault generated by the access.
In the case
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Dae S. Kim"
commit 6bd4a5d96c08dc2380f8053b1bd4f879f55cd3c9 upstream.
Fixed a bug. Data was being written to user space using an IOCTL
command encoded with _IOC_WRITE access mode.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 07dc59f0988cb54fd87bd373b3b27eb2401dd811 upstream.
snd_hda_codec_reset() calls restore_pincfgs() where the codec is
powered up again, which eventually tries to resume and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit e427c2375646789ecd0ccaef1a1e41458559ab2d upstream.
On recent kernels, Realtek codec parser tries to optimize the routing
aggressively and take the headphone output as
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Seth Jennings
commit 6d7d9798ad5c97ee4e911dd070dc12dc5ae55bd0 upstream.
This patch fixes a race condition that results in memory
corruption when using cleancache.
The race exists between the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Igor Grinberg
commit 45caae74d238ef6583e9402cb8c550cc0b0f7dbd upstream.
Currently, omap2_sync32k_clocksource_init() function initializes the 32K
timer as the system clock source regardless of
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit 61ed59ed09e6ad2b8395178ea5ad5f653bba08e3 upstream.
Don't zero out bits 15..12 of the data value in `das08jr_ao_winsn()` as
that knobbles the upper three-quarters of the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Francesco Ruggeri
commit 6bf6104573482570f7103d3e5ddf9574db43a363 upstream.
The unregister_sysctl_table() function hangs if all references to its
ctl_table_header structure are not dropped.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Malcolm Priestley
commit aa209eef3ce8419ff2926c2fa944dfbfb5afbacb upstream.
Hi,
This patch fixes a bug with driver failing to negotiate a connection.
The bug was traced to commit
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lauri Hintsala
commit 1af36b2a993dddfa3d6860ec4879c9e8abc9b976 upstream.
Release the lock before mmc_signal_sdio_irq is called by mxs_mmc_irq_handler.
Backtrace:
[ 79.66]
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Chen
commit 3550ccdb9d8d350e526b809bf3dd92b550a74fe1 upstream.
For several MoviNAND eMMC parts, there are known issues with secure
erase and secure trim. For these specific MoviNAND
On Fri, Sep 28, 2012 at 10:27:43AM -0400, Alan Stern wrote:
> On Fri, 28 Sep 2012, Dan Carpenter wrote:
>
> > I've filed a bug for this.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=48061
> >
> > Probably the other information which would be useful is the output
> > from lsusb. Anyway,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox
commit 17c60c6b763cb5b83b0185e7d38d01d18e55a05a upstream.
This can also appear as 0x9192. Reported in bugzilla and confirmed with the
board documentation for these boards.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Lu
commit f25b70613c048ceb1df052576fda03321ebf41cf upstream.
commit a606dac368eed5696fb38e16b1394f1d049c09e9 adds support to link
devices which have _PRx, if a device does not have _PRx,
On 09/28/2012 04:36 PM, Arnd Bergmann wrote:
> The con_debug_leave/con_debug_enter functions are stubbed out
> by defining them to (0), which causes harmless build warnings.
> Using proper inline functions is the normal way to deal with
> this.
>
> Without this patch, building the ARM
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 667a5313ecd7308d79629c0738b0db588b0b0a4e upstream.
commit 27a7b260f71439c40546b43588448faac01adb93
md: Fix handling for devices from 2TB to 4TB in 0.90 metadata.
changed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 6dafab6b1383e912cd252fa809570b484eb6e0dc upstream.
It isn't always necessary to update the metadata when spares are
removed as the presence-or-not of a spare isn't really
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit e5c86471f933608db5d43679f84cb4346c32033e upstream.
When a replacement device becomes active, we mark the device that it
replaces as 'faulty' so that it can subsequently get
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dylan Reid
commit 57b2d68863f281737d8596cb3d76d89d9cc54fd8 upstream.
The pause and resume operations indicate that the stream can be
un-paused/resumed from the exact location they were
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Hilman
commit 8dcebaa9a0ae8a0487f4342f3d56d2cb1c980860 upstream.
On some platforms, bootloaders are known to do some interesting RTC
programming. Without going into the obscurities as
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Benoît Locher
commit cab32f39dcc5b35db96497dc0a026b5dea76e4e7 upstream.
The MCP2515 has a silicon bug causing repeated frame transmission, see section
5 of MCP2515 Rev. B Silicon Errata
On Fri, 28 Sep 2012, Glauber Costa wrote:
> I am happy as long as we don't BUG and can mask out that feature.
> If Christoph is happy with me masking it in the SLAB only, I'm also fine.
>
Absolutely, I agree that the implementation-defined __kmem_cache_create()
can mask out bits that are not
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jianguo Wu
commit 05cf96398e1b6502f9e191291b715c7463c9d5dd upstream.
I found following definition in include/linux/memory.h, in my IA64
platform, SECTION_SIZE_BITS is equal to 32, and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stefano Stabellini
commit 2fc136eecd0c647a6b13fcd00d0c41a1a28f35a5 upstream.
If the caller passes a valid kmap_op to m2p_add_override, we use
kmap_op->dev_bus_addr to store the original mfn,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Herrmann
commit 5f0ecb907deb1e6f28071ee3bd568903b9da1be4 upstream.
The quirk introduced with commit
00250ec90963b7ef667843f3244985ecde14 (hwmon: fam15h_power: fix
bogus values with
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 73d7c119255615a26070f9d6cdb722a166a29015 upstream.
twl4030_madc_conversion uses do_avg and type structure elements of
twl4030_madc_request. Initialize structure to avoid
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nestor Lopez Casado
commit 596264082f10dd4a567c43d4526b2f54ac5520bc upstream.
This patch fixes an issue introduced after commit 4ea5454203d991ec
("HID: Fix race condition between driver core
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Airlie
commit 5e1782d224c79b26ab7d5c31e3f87657000714fb upstream.
Testing and works with the -modesetting driver,
Reviewed-by: Jakob Bornecrantz
Signed-off-by: Dave Airlie
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eliad Peller
commit 3d2abdfdf14f4d6decc2023708211e19b096f4ca upstream.
ifmgd->bssid wasn't cleared properly in some
auth/assoc failure cases, causing mac80211 and
the low-level driver to go
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit 4e21f4eaa49f78d3e977e316514c941053871c76 upstream.
The 'name' sysfs attribute is mandatory for hwmon devices, but was missing
in this driver.
Cc: Paul Thomas
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "sreekanth.re...@lsi.com"
commit 10cce6d8b5af0b32bc4254ae4a28423a74c0921c upstream.
This patch checks whether HBA is SAS2008 B0 controller.
if it is a SAS2008 B0 controller then it use IO-APIC
Functions for hotplugging must be marked as __devinit so
they do not get discarded, as pointed out by a build time
warning from modpost.
Cc: Mark Langsdorf
Cc: Rob Herring
Cc: Jeff Garzik
---
drivers/ata/sata_highbank.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Something is wrong with the exynos_dp_core logic, and gcc
emits a warning about this. An array is declared in
exynos_dp_process_equalizer_training with length '2',
and exynos_dp_channel_eq_ok tries to access the third
element of it.
This patch is certainly not correct, but hopefully helps
The atmel_nand driver was broken by b654a9a46fc2 "mtd: atmel nand: fix
gpio missing request". This is a rather helpless attempt to fix this,
probably messing up the error handling even further but getting the
build to work again, so please treat it as a bug report rather than
a fix to be applied.
The driver has not been building for some time after the
irq_to_gpio function has been removed from the kernel.
The only board in the upstream kernel that provides
this device is the "Stargate 2", which is also maintained
by Jonathan Cameron. Rather than working around the problem
by adding new
Patch a7ea3bbf5d "time/jiffies: Allow CLOCK_TICK_RATE to be undefined"
breaks the compilation of targets that rely on the LATCH definition,
because of recursive header file inclusion not defining CLOCK_TICK_RATE
before it is checked here.
This fixes the problem by moving LATCH back to where it
The samsung pinctrl driver has a probe function that is
__devinit and that calls a lot of other functions that are
marked __init, which kbuild complains about.
Marking everything __devinit means that the code does not
discarded when CONFIG_HOTPLUG is set, which is a little
more wasteful, but also
On 09/28/2012 04:36 PM, Arnd Bergmann wrote:
> Functions for hotplugging must be marked as __devinit so
> they do not get discarded, as pointed out by a build time
> warning from modpost.
>
> Cc: Mark Langsdorf
> Cc: Rob Herring
> Cc: Jeff Garzik
> ---
> drivers/ata/sata_highbank.c |2 +-
a4c96ae319 "sched: Unthrottle rt runqueues in __disable_runtime()"
turned the unthrottle_offline_cfs_rqs function into a static symbol,
which now triggers a warning about it being potentially unused:
kernel/sched/fair.c:2055:13: warning: 'unthrottle_offline_cfs_rqs' defined but
not used
On a normal build, we get output from both make and from dtc
about each file that is being processed.
DTC arch/arm/boot/vexpress-v2p-ca5s.dtb
DTC: dts->dtb on file
"/git/arnd/linux-arm/arch/arm/boot/dts/vexpress-v2p-ca5s.dts"
DTC arch/arm/boot/vexpress-v2p-ca9.dtb
DTC: dts->dtb on
The ixp4xx queue manager uses "const struct qmgr_regs __iomem *" as the
type for a pointer that is passed to __raw_writel, which is not
allowed because of the const-ness.
Dropping the 'const' keyword fixes the problem. While we're here,
let's also drop the useless type cast.
Without this patch,
Patch 6e20a0a4 "gpio: pcf857x: enable gpio_to_irq() support"
added IRQ domain support to the pcf857x driver, but some configurations
(e.g. davinci_all_defconfig) don't already enable CONFIG_IRQ_DOMAIN.
Always selecting it from the Kconfig in this case is what other
such drivers do as well, and
The MODULE_DEVICE_TABLE() entry in the dw_mmc_exynos driver
points to the wrong symbol which results in a link error
when building as a loadable module.
Further, we get a warning about the driver_data being
marked constant, which requires annotating a few pointers
as const.
Signed-off-by: Arnd
The con_debug_leave/con_debug_enter functions are stubbed out
by defining them to (0), which causes harmless build warnings.
Using proper inline functions is the normal way to deal with
this.
Without this patch, building the ARM bcm2835_defconfig results in:
drivers/tty/serial/kgdboc.c: In
Hi everyone,
I've run my own build tests on the arm-soc tree, and now on linux-next
in order to find regressions on build warnings. These are a bunch of
patches that I came up with to address problems that were newly
introduced since 3.6 and that are not in the domain of the
arm-soc tree.
I'd
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andrzej Kaczmarek
commit 3d1cbdd6aefff711bcf389fdabc4af9bc22e8201 upstream.
When new BT USB adapter is plugged in it's configured while still being powered
off (HCI_AUTO_OFF flag is set), thus
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vinicius Costa Gomes
commit 78c04c0bf52360dc2f7185e99c8e9aa05d73ae5a upstream.
For example, when a usb reset is received (I could reproduce it
running something very similar to this[1] in a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hante Meuleman
commit e020a83d0942a5aceac35986500c9834efc8707d upstream.
Fixes big endian host configuration parameters.
Reviewed-by: Arend Van Spriel
Signed-off-by: Hante Meuleman
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Santiago Leon
commit d90c92fee89ccd75ef2646f3bde0b4c0450666c3 upstream.
This patch fixes a bug found by Nish Aravamudan
(https://lkml.org/lkml/2012/5/15/220) where the driver is not following
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit c73f693989d7a7d99ec66a7065295a0c93d0b127 upstream.
This function returns the wrong value, which causes the callers to get
the length of the resulting pathname wrong when it
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit 8d54db795dfb1049d45dc34f0dddbc5347ec5642 upstream.
The hypervisor is in charge of allocating the proper "NUMA" memory
and dealing with the CPU scheduler to keep
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Kasatkin
commit bc01637a80f5b670bd70a0279d3f93fa8de1c96d upstream.
When pkcs_1_v1_5_decode_emsa() returns without error and hash sizes do
not match, hash comparision is not done and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Clements
commit fded4e090c60100d709318896c79816d68d5b47d upstream.
Fix a serious but uncommon bug in nbd which occurs when there is heavy
I/O going to the nbd device while, at the same
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
commit 67a806d9499353fabd5b5ff07337f3aa88a1c3ba upstream.
The following build error occurred during an alpha build:
net/core/sock.c:274:36: error: initializer element is not
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lin Ming
commit 40bf66ec9791f1452b90b82aadc3b6e6aee201f5 upstream.
Commit 0090def("ACPI: Add interface to register/unregister device
to/from power resources") used resource_lock to protect the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
commit ba9edaa468869a8cea242a411066b0f490751798 upstream.
Fix the ZTE K5006-Z entry so that it actually matches anything
commit f1b5c997 USB: option: add ZTE
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit ab548d2dba63ba947287965e525cc02a15d9853d upstream.
With the commit [2faa3bf: ALSA: hda - Rewrite the mute-LED hook with
vmaster hook in patch_sigmatel.c], the former Master
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit a849088aa1552b1a28eea3daff599ee22a734ae3 upstream.
Murali Nalajala reports a regression that ioremapping address zero
results in an oops dump:
Unable to handle kernel
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 8404663f81d212918ff85f493649a7991209fa04 upstream.
The {get,put}_user macros don't perform range checking on the provided
__user address when !CPU_HAS_DOMAINS.
This patch
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matthew Leach
commit e1e5b7e4251c7538ca08c2c5545b0c2fbd8a6635 upstream.
This patch zeroes the SCTLR.TRE bit prior to setting the mapping as
cacheable for ARMv7 cores in the decompressor,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Anisse Astier
commit 8669cf6793bb38307a30fb6b9565ddc8840ebd3f upstream.
On Toshiba Satellite C850D, the touchpad and the keyboard might randomly
not work at boot. Preventing MUX mode
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Toshi Kani
commit 308b135e4fcc00c80c07e0e04e7afa8edf78583c upstream.
kdump can be interrupted by watchdog timer when the timer is left
activated on the crash kernel. Changed the hpwdt driver
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit 022e1d0680c7b4366017393417b8758be5abcee8 upstream.
There are a number of problems that occur for the latest version
of the Realtek RTL8188CE device with the in-kernel
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Søren Holm
commit ed3770a9cd5764a575b83810ea679bbff2b03082 upstream.
Signed-off-by: Søren Holm
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
drivers/net/usb/asix.c
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Ira W. Snyder"
commit e21093ef6fb4cbecdf926102286dbe280ae965db upstream.
The Revision 1.0 Janz CMOD-IO Carrier Board does not have support for
the reset registers. To support older hardware,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Kamat
commit 2e2c682becb20416c140aa0d6d3137b51a5c76da upstream.
'r->cfg' is being checked for NULL. However, it is dereferenced
in the previous statements. Thus moving those statements
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Ferre
commit c618a9be0e8c0f36baee2560860a0118a428fb26 upstream.
s/dma_memcpy/slave_sg/ and it is sg length that we are
talking about.
Signed-off-by: Nicolas Ferre
Signed-off-by:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gertjan van Wingerde
commit 177ef8360fabdc49ff08d2598c06e7f7a36b53e3 upstream.
This is an RT3572 based device.
Signed-off-by: Maximilian Engelhardt
Signed-off-by: Gertjan van Wingerde
101 - 200 of 2396 matches
Mail list logo
