3.8-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.8-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.8-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.8-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.8-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.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Benny Halevy
commit 78f33277f96430ea001c39e952f6b8200b2ab850 upstream.
Pass the directio request on pageio_init to clean up the API.
Percolate pg_dreq from original nfs_pageio_descriptor to
3.8-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
On Tue, Mar 12, 2013 at 12:38 AM, Minchan Kim wrote:
> First of all, let's define the term.
> From now on, I'd like to call it as vrange(a.k.a volatile range)
> for anonymous page. If you have a better name in mind, please suggest.
>
> This version is still *RFC* because it's just quick prototype
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Weston Andros Adamson
commit a47970ff7814718fec31b7d966747c6aa1a3545f upstream.
This fixes an oops where a LAYOUTGET is in still in the rpciod queue,
but the requesting processes has been
Thadeu Lima de Souza Cascardo wrote:
> On Fri, Mar 08, 2013 at 03:29:55AM +, Ben Hutchings wrote:
> > On Fri, 2013-03-08 at 13:51 +1100, Michael Neuling wrote:
> > > This patch is breaking the celleb_defconfig on powerpc with:
> > >
> > > arch/powerpc/kernel/of_platform.c: In function
3.8-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.8-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.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Mattia Dongili
commit 3ec1c3983d73b1e3d4cfd72afab94c34eceafe8a upstream.
The call to handlers 0x124 and 0x135 (rfkill control) seems to take a
bitmask to control various states of the device.
On Tue, Mar 12, 2013 at 07:08:43PM -0400, Jason Cooper wrote:
> Greg,
>
> On Tue, Mar 12, 2013 at 03:43:54PM -0700, Greg Kroah-Hartman wrote:
> > 3.4-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Andrew Lunn
> >
> > commit
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Bing Zhao
commit 466026989f112e0546ca39ab00a759af82dbe83a upstream.
For SD8688, FUNC_INIT command is queued before fw_ready flag is
set. This causes the following crash as lbs_thread blocks
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Christie
commit 87eb5b21d92a92ac2da3163039d62df88c2b8422 upstream.
dm_calculate_queue_limits will first reset the provided limits to
defaults using blk_set_stacking_limits; whereby
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Takahisa Tanaka
commit 41adafbd7b84c66c2cdad857b75d5d45032310a6 upstream.
In case of SP5100 or SB7x0 chipsets, the sp5100_tco module writes zero to
reserved bits. The module, however,
The exynos ADC won't work without a regulator called "vdd" and a clock
called "adc". Document this fact in the device tree bindings.
Signed-off-by: Doug Anderson
---
Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt | 8
1 file changed, 8 insertions(+)
diff --git
This set of patches is based on Naveen Krishna Chatradhi's recent work
(some of which is still in-flight) and does the final touches to get
things working on exynos5250-snow (the ARM Chromebook).
These patches were tested on next-20130312 (which includes support for
the common clock framework
Without this change the exynos adc controller needed to have its phy
enabled in some out-of-driver C code. Add support for specifying the
phy enable register by listing it in the reg list.
Signed-off-by: Doug Anderson
---
.../devicetree/bindings/arm/samsung/exynos-adc.txt | 4 ++--
Add the device tree entry for the device-tree enabled ADC driver that
recently landed in the iio tree.
Signed-off-by: Doug Anderson
---
arch/arm/boot/dts/exynos5250.dtsi | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
3.8-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
Hook up the exynos5250-snow thermistors via the device tree now that
there's a driver available to use them.
Signed-off-by: Doug Anderson
---
arch/arm/boot/dts/cros5250-common.dtsi | 4
arch/arm/boot/dts/exynos5250-snow.dts | 31 +++
2 files changed, 35
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit cc9945bf9cac03860b2f7d59882263c965c6e3af upstream.
Avoids splatter if the interrupt handler is not registered due
to acceleration being disabled.
Signed-off-by: Alex
3.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 8a4e3a9ead7e37ce1505602b564c15da09ac039f upstream.
mm->context.id is updated under asid_lock when a new ASID is allocated
to an mm_struct. However, it is also read without
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Pitre
commit 70264367a243a68b1d5636ffb570183449803cbe upstream.
When udelay() is implemented using an architected timer, it is wrong
to scale loops_per_jiffy when changing the CPU
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit d61947a164760ac520cb416768afdf38c33d60e7 upstream.
The LPAE page table format uses 64-bit descriptors, so we need to take
endianness into account when populating the swapper
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 3412f2f086ea7531378fabe756bd4a1109994ae6 upstream.
On many different chips, important aspects of the MAC state are not
fully cleared by a warm reset. This can show up as
3.8-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
On Tue, Mar 12, 2013 at 02:09:08PM -0700, John Stultz wrote:
> On 03/11/2013 08:56 PM, Feng Tang wrote:
> }
> >-/* re-base the last cycle value */
> >-tk->clock->cycle_last = tk->clock->read(tk->clock);
> >+
> >+if (suspendtime_found)
> >+
On Wed, Mar 13, 2013 at 03:02:22AM +0400, Sergey Yanovich wrote:
> ICP DAS LP-8x4x is an industrial data acquision device. It is based
> on PXA270 CPU. The board containsi a lot of (up to 36) standard UARTi
> 8250i serial ports. System console on the board is provided with
> an on-chip PXA serial
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 221f8dfca89276d8aec54c6d07fbe20c281668f0 upstream.
This patch (as1649) reverts commit
55bcdce8a8228223ec4d17d8ded8134ed265d2c5 (USB: EHCI: remove ASS/PSS
polling timeout).
On 03/12/2013 04:08 PM, Rhyland Klein wrote:
> This change adds the binding documentation for the tps65090-charger.
> diff --git a/Documentation/devicetree/bindings/power_supply/tps65090.txt
> b/Documentation/devicetree/bindings/power_supply/tps65090.txt
> +Example:
> +
> + tps65090@48 {
>
3.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Frederic Weisbecker
commit e5ab012c3271990e8457055c25cafddc1ae8aa6b upstream.
As it stands, irq_exit() may or may not be called with
irqs disabled, depending on __ARCH_IRQ_EXIT_IRQS_DISABLED
3.8-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.8-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.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit 69dde4c52dbac2891b49ff9723d9c84efc5baf6f upstream.
Following commit 26ffd0d4 (ARM: mm: introduce present, faulting entries
for PAGE_NONE), if a page has been mapped as
Greg,
On Tue, Mar 12, 2013 at 03:43:54PM -0700, Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Andrew Lunn
>
> commit 89c58c198b252f2bc20657fdd72a2aea788c435c upstream.
>
> The Marvell RTC on Kirkwood
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit ee0b0244030434cdda26777bfb98962447e080cd upstream.
When raid1/raid10 needs to fix a read error, it first drains
all pending requests by calling freeze_array().
This calls
3.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Noonan
commit 45e27161c62216c163880d7aed751cb55a65c8e9 upstream.
Adding an include of linux/mm.h resolves this:
drivers/xen/xenbus/xenbus_client.c: In function
3.8-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.8-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 7b54c165a0c012edbaeaa73c5c87cb73721eb580 upstream.
It's "normal" - it can happen if the file descriptor you followed was
opened with O_NOFOLLOW.
Reported-by: Dave Jones
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit db04dc679bcc780ad6907943afe24a30de974a1b upstream.
Update proc_ns_follow_link to use nd_jump_link instead of just
manually updating nd.path.dentry.
This fixes the
3.8-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:
-
On Tue, Mar 12, 2013 at 03:52:19PM -0700, Larry Baker wrote:
> Greg,
>
> Will there also be a 2.6-stable patch (Eric's first submission)? My CentOS
> 6.3
> systems still use 2.6 kernels.
I do not maintain any 2.6-stable releases, sorry. I suggest you work
with Centos to get this patch into
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Stéphane Marchesin
commit 0920a48719f1ceefc909387a64f97563848c7854 upstream.
This increases GEN6_RC6p_THRESHOLD from 10 to 15. For some
reason this avoids the
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Kenneth Graunke
commit 86c268ed0f9b3b4d51d81dd8fcec533a164414d1 upstream.
The second digit was off by one, which meant we accidentally treated
GT(n) as GT(n-1). This also meant no support for
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter
commit 52d7ecedac3f96fb562cb482c139015372728638 upstream.
Otherwise the new irq-driven gmbus and dp aux code won't work that
well. Noticed since the dp aux code doesn't have an
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit c79c49826270b8b0061b2fca840fc3f013c8a78a upstream.
The git commit 8eaffa67b43e99ae581622c5133e20b0f48bcef1
(xen/pat: Disable PAT support for now) explains in
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter
commit 15239099d7a7a9ecdc1ccb5b187ae4cda5488ff9 upstream.
We need it to restore the ilk rc6 context, since the gpu wait no
requires interrupts. But in general having interrupts
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Patrik Jakobsson
commit f40ebd6bcbbd0d30591f42dc16be52b5086a366b upstream.
According to PRM we need to disable hsync and vsync even though ADPA is
disabled. The previous code did infact do the
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
commit 12a5c05cb143105d989abf728a8c769830670e54 upstream.
DA9055_WATCHDOG (introduced in v3.8) needs to select WATCHDOG_CORE so that it
will
build cleanly. Fixes these build
Larry Baker writes:
> Greg,
>
> Will there also be a 2.6-stable patch (Eric's first submission)? My CentOS
> 6.3
> systems still use 2.6 kernels.
Larry what is in CentOS is for the CentOS maintainers to determine.
Last I checked they followed RHEL and RHEL seems to have so little
interest in
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Hurley
commit e1082f45f1e2bbf6e25f6b614fc6616ebf709d19 upstream.
If the src msg is > 4k, then dest->next points to the
next allocated segment; resetting it just prior to dereferencing
is
Use resource_size() instead of explicit calculation and change the way
debugging for struct resource is done.
Signed-off-by: Silviu-Mihai Popescu
---
drivers/net/ethernet/nxp/lpc_eth.c |7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Hurley
commit 88b9e456b1649722673ffa147914299799dc9041 upstream.
When MSG_COPY is set, a duplicate message must be allocated for the copy
before locking the queue. However, the copy
On 3/12/2013 3:39 PM, Eric W. Biederman wrote:
> Mike Travis writes:
>
>> Let me see if I can understand the concept better. By denying
>> an external hardware vendor the use of KDB to support a significant
>> piece of proprietary hardware on Linux, I furthering the interests
>> of Linux and
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Connor
commit 69a4cfdd444d1fe5c24d29b3a063964ac165d2cd upstream.
Set card->private_data in snd_ice1712_create for fixing NULL
dereference in snd_ice1712_remove().
Signed-off-by: Sean
3.8-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
ICP DAS LP-8x4x is an industrial data acquision device. It is based
on PXA270 CPU. The board containsi a lot of (up to 36) standard UARTi
8250i serial ports. System console on the board is provided with
an on-chip PXA serial port. Both modules use /dev/ttyS0 by default.
To solve the collision,
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Marcelo Tosatti
commit ed55705dd5008b408c48a8459b8b34b01f3de985 upstream.
To match whats mapped via vsyscalls to userspace.
Reported-by: Peter Hurley
Signed-off-by: Marcelo Tosatti
On Wed, 6 Mar 2013 18:52:01 -0500 Andrew Shewmaker wrote:
> Add user_reserve_pages knob.
>
> Limit the growth of the memory reserved for other user
> processes to min(3% current process, user_reserve_pages).
>
> user_reserve_pages defaults to min(3% free pages, 128MB)
> I arrived at 128MB by
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit dcd9006b1b053c7b1cebe81333261d4fd492ffeb upstream.
hid_output_raw_report() makes a direct call to usb_control_msg(). However,
some USB3 boards have shown that the usb
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit 925396ecf251432d6d0f703a6cfd0cb9e651d936 upstream.
Dave sent me a panic where we were doing the orphan cleanup and panic'ed
trying to release our reservation from the orphan
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Takahisa Tanaka
commit 10ab329b5db7e592a3a60b4594e4e5f40b60c45c upstream.
In case of SB800 or later chipset and re-programming MMIO address(*),
sp5100_tco module may read incorrect value of
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
commit fd3a9025c0349bc9b01d627529f54e6e1e389015 upstream.
This patch addresses a v3.5+ regression in iscsi-target where TX thread
process context -> handle_response_queue()
This is the start of the stable review cycle for the 3.4.36 release.
There are 40 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Mar 14 22:31:37 UTC 2013.
Anything
3.8-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit b980955236922ae6106774511c5c05003d3ad225 upstream.
Commit 6133705494bb introduced a circular lock dependency because
posix_cpu_timers_exit() is called by release_task(),
3.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Asias He
commit 472b72f2db7831d7dbe22ffdff4adee3bd49b05d upstream.
The page++ is wrong. It makes bio_add_pc_page() pointing to a wrong page
address if the 'while (len > 0 && data_len > 0) {
3.4-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,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olaf Hering
commit d9904344fc4052fbe7e4dc137eba0dcdadf326bd upstream.
An earlier commit cd006086fa5d91414d8ff9ff2b78fbb593878e3c ("ata_piix:
defer disks to the Hyper-V drivers by default")
3.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit dcd9006b1b053c7b1cebe81333261d4fd492ffeb upstream.
hid_output_raw_report() makes a direct call to usb_control_msg(). However,
some USB3 boards have shown that the usb
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Konrad Rzeszutek Wilk
commit c79c49826270b8b0061b2fca840fc3f013c8a78a upstream.
The git commit 8eaffa67b43e99ae581622c5133e20b0f48bcef1
(xen/pat: Disable PAT support for now) explains in
3.4-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.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Lunn
commit 89c58c198b252f2bc20657fdd72a2aea788c435c upstream.
The Marvell RTC on Kirkwood makes use of the runit clock. Ensure the
driver clk_prepare_enable() this clock, otherwise
101 - 200 of 1740 matches
Mail list logo
