3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 6d769f1e1420179d1f83cf1a9cdc585b46c28545 upstream.
Currently, when we try to mount and get back NFS4ERR_CLID_IN_USE or
NFS4ERR_WRONGSEC, we create a new rpc_clnt and then
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Christoffer Dall
commit 40c2729bab48e2832b17c1fa8af9db60e776131b upstream.
Using virt_to_phys on percpu mappings is horribly wrong as it may be
backed by vmalloc. Introduce kvm_kaddr_to_phys
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Hao
commit ab4ead02ec235d706d0611d8741964628291237e upstream.
In commit 8a4d0a687a59 "ftrace: Use breakpoint method to update ftrace
caller", we choose to use breakpoint method to
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 487a588d09db0d6508261867df208d8bdc718251 upstream.
BIOS on ASUS W5A laptop with ALC880 codec doesn't provide any pin
configurations, so we have to set up all pins
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Bonzini
commit daf727225b8abfdfe424716abac3d15a3ac5626a upstream.
When I was looking at RHEL5.9's failure to start with
unrestricted_guest=0/emulate_invalid_guest_state=1, I got it
On Tuesday, November 26, 2013 06:11:57 PM Toshi Kani wrote:
> On Wed, 2013-11-27 at 02:02 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, November 26, 2013 05:33:28 PM Toshi Kani wrote:
> > > On Wed, 2013-11-27 at 01:27 +0100, Rafael J. Wysocki wrote:
> > > > On Tuesday, November 26, 2013 05:00:42
On 11/26/2013 10:58 AM, Dmitry Torokhov wrote:
Hi Guenter,
On Mon, Nov 25, 2013 at 08:39:04PM -0800, Guenter Roeck wrote:
Simplify the code and create mandatory 'name' attribute by using
new hwmon API.
So this moves hwmon attributes from the parent i2c device to the hwmon
device, right?
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Edwards
commit 27ef63c7e97d1e585051c03f8d44cc887f34 upstream.
When determining the page size we could use to map with the IOMMU, the
page size should also be aligned with the hva,
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Moyer
commit 4912aa6c11e6a5d910264deedbec2075c6f1bb73 upstream.
crocode i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support shpchp ioatdma dca
be2net sg ses enclosure ext4 mbcache jbd2
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Guenter Roeck
commit e41fae2b1ed8c78283d73651cd65be0228c0dd1c upstream.
Bit 2 of status register 2 on MAX6696 (external diode 2 open)
sets ALERT; the bit thus has to be listed in
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Anatolij Gustschin
commit 2bf75084f6d9f9a91ba6e30a501ff070d8a1acf6 upstream.
The MPC5200 LPBFIFO driver requires the bestcomm module to be
enabled, otherwise building will fail. Fix it.
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Gerhard Sittig
commit 45d20e8348969a165c53cfb91f445e7cc599a9f0 upstream.
a disabled Kconfig option results in a reference to a not implemented
routine when the IS_ENABLED() macro is used for
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Jesper Nilsson
commit 3a72660b07d86d60457ca32080b1ce8c2b628ee2 upstream.
Commit 2caacaa82a51 ("ipc,shm: shorten critical region for shmctl")
restructured the ipc shm to shorten critical
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit a207f5937630dd35bd2550620bef416937a1365e upstream.
The probe function is supposed to return NULL on failure (as we can see in
kobj_lookup: kobj = probe(dev, index,
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 468ac413045af1e0e4d1272291bed6878f248a69 upstream.
We don't change the EAPD bit in set_pin_eapd() if keep_eapd_on flag is
set by the codec driver and enable is false.
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit d82ae52e68892338068e7559a0c0657193341ce4 upstream.
Without this patch all DM devices will default to BLK_MAX_SEGMENT_SIZE
(65536) even if the underlying device(s) have a
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit 5959a6bc1124211a359525d209005abc07b0197b upstream.
In case there is both a multifunction headset jack and a Line Out
jack, automuting was not working properly from
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit f3f5a0f8cc40b942f4c0ae117df82eeb65f07d4d upstream.
In the spec, the security label attribute id is '80', which means that
it should be bit number 80-64 == 16 in the 3rd
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 0fc28fc030a85aa3d6d14e9e9fca0c8237c9ffb5 upstream.
When a codec is resumed, it keeps the power on while the resuming
phase via hda_keep_power_on(), then turns down via
On Wed, 2013-11-27 at 02:02 +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 26, 2013 05:33:28 PM Toshi Kani wrote:
> > On Wed, 2013-11-27 at 01:27 +0100, Rafael J. Wysocki wrote:
> > > On Tuesday, November 26, 2013 05:00:42 PM Toshi Kani wrote:
> > > > On Mon, 2013-11-25 at 01:09 +0100,
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit d183b4fc463489b6bbe05c99afa0257a6fe578eb upstream.
snd_hda_codec_reset() is called either in resetting the whole setup at
error paths or hwdep clear/reconfig sysfs
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 0f5a5b8515472a0219768423226b58228001e3d5 upstream.
BIOS sets MISC_NO_PRESENCE bit wrongly to the pin config on NID 0x0f.
Signed-off-by: Takashi Iwai
Signed-off-by: Greg
On Tue, Nov 26, 2013 at 5:00 AM, Wolfram Sang wrote:
> Have you also tried repeated module loading/unloading?
I ran a loop of insmod + rmmod 1000 times and didn't see any issues.
Thanks,
Tim Kryger
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tuesday, November 26, 2013 03:50:05 PM Paul Walmsley wrote:
> On 11/25/2013 09:03 PM, viresh kumar wrote:
> > On Tuesday 26 November 2013 07:31 AM, Paul Walmsley wrote:
> >> diff --git a/drivers/cpufreq/cpufreq-cpu0.c
> >> b/drivers/cpufreq/cpufreq-cpu0.c
> >> index d4585ce2346c..0faf756f6197
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Tomas Winkler
commit 4bff7208f332b2b1d7cf1338e50527441283a198 upstream.
The flow may reach the err label without freeing cl and cl_info
cl and cl_info weren't assigned to ndev->cl and
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit a6f951ddbdfb7bd87d31a44f61abe202ed6ce57f upstream.
In nfs4_proc_getlk(), when some error causes a retry of the call to
_nfs4_proc_getlk(), we can end up with Oopses of
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit d5b6b65e75ce607c2734227524e11574317a1c1a upstream.
Some HP machines with Realtek codecs have mute LEDs connected to VREF pins.
However when these go into runtime
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit d49f042aeec99c5f87160bb52dd52088b1051311 upstream.
Currently, if the call to nfs_refresh_inode fails, then we end up leaking
a reference count, due to the call to
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit 58e21f73975ec927119370635bf68b9023831c56 upstream.
To enable USB 2.0 Link Power Management (LPM), the xHCI host controller
needs the device slot ID to generate the device
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit de68bab4fa96014cfaa6fcbcdb9750e32969fb86 upstream.
How it's supposed to work:
--
USB 2.0 Link PM is a lower power state that some newer USB 2.0
On 11/11/2013 06:13 PM, Peter Hurley wrote:
On 11/11/2013 03:05 PM, Jiri Slaby wrote:
When we leak something, warn about that. For that we need to account
the memory used also in the free_all method. It is handled elsewhere
correctly.
Hi Jiri,
Good idea.
Signed-off-by: Jiri Slaby
---
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Gavin Shan
commit 631ad691b5818291d89af9be607d2fe40be0886e upstream.
We need add PE to its own PELTV. Otherwise, the errors originated
from the PE might contribute to other PEs. In the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Pugliese
commit 7b6bc07ab554e929c85d51b3d5b26cf7f12c6a3b upstream.
For isochronous endpoints, set the RPIPE wMaxPacketSize value using
wOverTheAirPacketSize from the endpoint companion
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit c5340bd14336b902604ab95212a8877de109d9ae upstream.
So I captured this:
|WARNING: CPU: 0 PID: 2078 at
/home/bigeasy/work/new/TI/linux/lib/debugobjects.c:260
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit 427d6c6646d868fbd3094e7e2e1644d480cd9204 upstream.
Someone noticed exportfs happily accepted exports that would later be
rejected when mountd tried to give them to
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit 36165fd5b00bf8163f89c21bb16a3e9834555b10 upstream.
Polling TX statuses too frequently has two negative effects. First is
randomly peek CPU usage, causing overall
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit 8b9fcce2d88586b9a120ff3e039d8f42413f0bb0 upstream.
The timer is initialized right after musb is probed. There is actually
no need to have this timer running
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 818e5a22e907fbae75e9c1fd78233baec9fa64b6 upstream.
Split out two helpers to make the code more readable and easier to verify
for correctness.
Signed-off-by:
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit 0d2dd7eaed1dac07b266ca2c662ff4a184a3060f upstream.
The patch fixes two issues in the error path cleanup:
- in MUSB_PORT_MODE_DUAL_ROLE mode, if
On Tuesday, November 26, 2013 12:13:50 PM Yinghai Lu wrote:
> On Tue, Nov 26, 2013 at 11:34 AM, Yinghai Lu wrote:
> > On Mon, Nov 25, 2013 at 7:38 PM, Bjorn Helgaas wrote:
> >> On Mon, Nov 25, 2013 at 6:28 PM, Yinghai Lu wrote:
> >>> Mutliple removing via /sys will call pci_destroy_dev two
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit 5ca1db41ecdeb0358b968265fadb755213558a85 upstream.
We need to dput() the result of d_splice_alias(), unless it is passed to
finish_no_open().
Edited by Steven
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit 7ab64a85e1a009046f97413a573e83fd85f7804d upstream.
The get_tod_clock_ext inline assembly does not specify its output
operands correctly. This can cause incorrect
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 72a0c5571351f5184195754d23db3e14495b2080 upstream.
On cris arch, the functions below aren't defined:
drivers/media/platform/sh_veu.c: In function
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 5a049f14902982c26538250bdc8d54156d357252 upstream.
Commit fba2369e6ceb (mm: use vm_unmapped_area() on powerpc architecture)
has a bug in slice_scan_available() where we
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit 0d0d110720d7960b77c03c9f2597faaff4b484ae upstream.
unless it was given an IS_ERR(inode), which isn't the case here. So clean
up the unnecessary error handling in
On Tue, Nov 26, 2013 at 06:00:10PM -0500, Johannes Weiner wrote:
> On Wed, Nov 27, 2013 at 09:29:37AM +1100, Dave Chinner wrote:
> > On Tue, Nov 26, 2013 at 04:27:25PM -0500, Johannes Weiner wrote:
> > > On Tue, Nov 26, 2013 at 10:49:21AM +1100, Dave Chinner wrote:
> > > > On Sun, Nov 24, 2013 at
On Tue, Nov 26 2013, Kent Overstreet wrote:
> On Mon, Nov 25, 2013 at 10:05:58PM -0800, Christoph Hellwig wrote:
> > On Mon, Nov 25, 2013 at 01:52:16PM -0800, Kent Overstreet wrote:
> > > Jens - here's immutable biovecs, rebased and ready for 3.14. Changes
> > > since the
> > > last version of
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Neuling
commit c13f20ac48328b05cd3b8c19e31ed6c132b44b42 upstream.
The VSX MSR bit in the user context indicates if the context contains VSX
state. Currently we set this when the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit 95f715b08fa4a953771398d20cbe35a6803ea41d upstream.
__get_user_pages_fast() may be called with interrupts disabled (see e.g.
get_futex_key() in kernel/futex.c) and
clk_round_rate() should return 0 now upon an error, rather than returning
a negative error code. This is because clk_round_rate() is being changed
to return an unsigned return type rather than a signed type, since some
clock sources can generate rates higher than (2^31)-1 Hz.
The bindings for the TTC changed in commit 'arm: zynq: Use standard
timer binding' (e932900a3279b5dbb6d8f43c7b369003620e137c). That change
removed possible subnodes from this driver rendering the 'clock-ranges'
property invalid for this node.
Signed-off-by: Soren Brinkmann
Acked-by: Peter
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Gavin Shan
commit bf898ec5cbd33be11147743bee27b66b10cb2f85 upstream.
On PHB3, we will fail to fetch IODA tables without PCI_COMMAND_MASTER
on PCI bridges. According to one experiment I had,
Add a 'cpus' node to describe the CPU cores of Zynq.
Signed-off-by: Soren Brinkmann
Acked-by: Peter Crosthwaite
---
v2:
- remove cache size related properties
---
arch/arm/boot/dts/zynq-7000.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git
To ensure that the timer interrupt is properly enabled/disabled across
the whole CPU cluster use enable/disable_irq() instead of
local_irq_disable().
Signed-off-by: Soren Brinkmann
---
drivers/clocksource/cadence_ttc_timer.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff
On Tuesday, November 26, 2013 11:34:24 AM Yinghai Lu wrote:
> On Mon, Nov 25, 2013 at 7:38 PM, Bjorn Helgaas wrote:
> > On Mon, Nov 25, 2013 at 6:28 PM, Yinghai Lu wrote:
> >> Mutliple removing via /sys will call pci_destroy_dev two times.
> >>
> >> | When concurent removing pci devices which
The currently used method adjusting the clocksource to a changing input
frequency does not work on kernels from 3.11 on.
The new approach is to keep the timer frequency as constant as possible.
I.e.
- due to the TTC's prescaler limitations, allow frequency changes
only if the frequency scales
The timer frequency of the arm_global_timer depends on the CPU
frequency. With cpufreq altering that frequency the arm_global_timer
does not maintain a stable time base. Therefore don't enable that timer
in case cpufreq is enabled.
Signed-off-by: Soren Brinkmann
---
arch/arm/mach-zynq/Kconfig |
Currently the driver uses two of the three counters the TTC provides to
implement a clocksource and a clockevent device. By using the TTC's
match feature we can implement both use cases using a single counter
only.
The old approach is to use timer over-/underflow to generate an
interrupt. Using
The generic cpufreq-cpu0 driver can scale the CPU frequency on Zynq
SOCs. Add the required platform device to the BSP and appropriate
OPPs to the dts.
Signed-off-by: Soren Brinkmann
---
arch/arm/boot/dts/zynq-7000.dtsi | 6 ++
arch/arm/mach-zynq/Kconfig | 2 ++
The clockevent has to be reprogrammed if the timer's input
clock frequency changes and the timer is in periodic mode, in order to
maintain the correct timer interval.
Signed-off-by: Soren Brinkmann
---
v2:
- adjust the timer interval while the timer interrupt is disabled
---
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 5fccc5b52ee07d07a74ce53c6f174bff81e26a16 upstream.
Add the missing 'break' to ensure that we don't corrupt a legacy 'v0' type
message by appending the 'v1'.
Cc: Bruce
On 11/26/2013 04:57 PM, Doug Anderson wrote:
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998
I revised this series and rebased on top of Linus' tree. Patch specific
changes are tracked in the respective email with their patch. On the
level of the whole series, this changed:
v2:
- added 'clocksource/cadence_ttc: Use enable/disable_irq'. I hope that
is more appropriate to avoid races
The existing watchdog timeout worked OK but didn't deal with
rounding in an ideal way when dividing out all of its clocks.
Specifically if you had a timeout of 32 seconds and an input clock of
, you'd end up setting a timeout of 31.9998 seconds and
reporting a timeout of 31 seconds.
It is not allowed to call clk_get_rate() from interrupt context. To
avoid such calls the timer input frequency is stored in the driver's
data struct which makes it accessible to the driver in any context.
Signed-off-by: Soren Brinkmann
Acked-by: Daniel Lezcano
---
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 84b073868b9d9e754ae48b828337633d1b386482 upstream.
When reading from the dispatch trace log (dtl) userspace interface, I
sometimes see duplicate entries. One example:
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 7a3e6107f94344e65c35bfe62de6c096a7b48965 upstream.
The only EAPD on AD1986A is on NID 0x1b where usually the speaker.
But this doesn't control only the speaker amp but may
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit 411cabf79e684171669ad29a0628c400b4431e95 upstream.
Commit e82b89a6f19bae73fb064d1b3dd91fcefbb478f4 used strcat instead of
strcpy which can result in an overflow of
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit d07ba8422f1e58be94cc98a1f475946dc1b89f1b upstream.
In cases where an rpc client has a parent hierarchy, then
rpc_free_client may end up calling rpc_release_client() on
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Lameter
commit c6f58d9b362b45c52afebe4342c9137d0dabe47f upstream.
Andreas Herrmann writes:
When I've used slub_debug kernel option (e.g.
"slub_debug=,skbuff_fclone_cache" or
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit b8362e70cbbb397db50939bc4c7c78dc3246c3eb upstream.
BugLink: https://bugs.launchpad.net/bugs/1253636
Signed-off-by: David Henningsson
Signed-off-by: Takashi Iwai
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit a6b31d18b02ff9d7915c5898c9b5ca41a798cd73 upstream.
The following scenario can cause silent data corruption when doing
NFS writes. It has mainly been observed when doing
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Julius Werner
commit e92aee330837e4911553761490a8fb843f2053a6 upstream.
This patch adds the Port Reset Change flag to the set of bits that are
preemptively cleared on init/resume of a hub. In
On Fri, 22 Nov 2013, Johannes Weiner wrote:
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 13b9d0f..cc4f9cb 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2677,6 +2677,9 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
> if
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 890dae88672175f1d39f6105444d9bdc71c89258 upstream.
Some usb3 devices falsely claim they support usb2 hardware Link PM
when connected to a usb2 port. We only trust
On Monday, November 25, 2013 05:28:03 PM Yinghai Lu wrote:
> We should not release resource in pci_destroy that is too early
> as there could be still other use hold reference.
>
> release them or remove it from bus devices list at last
> in pci_release_dev instead.
>
> Signed-off-by: Yinghai Lu
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sarah Sharp
commit dcc01c0864823f91c3bf3ffca6613e2351702b87 upstream.
Before the USB core resets a device, we need to disable the L1 timeout
for the roothub, if USB 2.0 Link PM is enabled.
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Junxiao Bi
commit 76ae281f6307331aa063288edb6422ae99f435f0 upstream.
A race window in configfs, it starts from one dentry is UNHASHED and end
before configfs_d_iput is called. In this
clk_round_rate() should return 0 upon an error, rather than returning
a negative error code. This is because clk_round_rate() is being
changed to return an unsigned return type rather than a signed type,
since some clock sources can generate rates higher than (2^31)-1 Hz.
Signed-off-by: Paul
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Roger Tseng
commit a0e5a12fd18d47aa87a7a8c60ca5bc422b136564 upstream.
In h_msb_read_page() in ms_block.c, flow never reaches case
MSB_RP_RECIVE_STATUS_REG. This causes error when
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit 0f901c980110cd69b63670096465b35377e73b1c upstream.
According to the comments, we rely on the OTG timer because the core
does not expose some important OTG
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit 4560e7c3317c7a2b370e36dadd3a3bac2ed70818 upstream.
Use the ACCESS_ONCE macro for both accesses to idle->sequence in the
loops to calculate the idle time. If only one
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit 365da4adebb1c012febf81019ad3dc5bb52e2a13 upstream.
This fixes a regression from 247500820ebd02ad87525db5d9b199e5b66f6636
"nfsd4: fix decoding of compounds across page
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 987da4791052fa298b7cfcde4dea9f6f2bbc786b upstream.
Use a straight goto error label style in nfsd_setattr to make sure
we always do the put_write_access call after we
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
commit ae44df2e21b50f9fff28ac75c57e399c04df812c upstream.
In commit 001dd84 ("usb: musb: start musb on the udc side, too") it was
ensured that the state engine is
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Vinod Koul
commit 917f4b5cba78980a527098a910d94139d3e82c8d upstream.
The drain and drain_notify callback were blocked by low level driver untill the
draining was complete. Due to this being
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 885845d78551be7bf8570f6283df8b7a7797c4d1 upstream.
The commit [8fe7b65ab465: ALSA: hda - Apply GPIO setup for MacBooks
with CS4208] added a fixup entry matching with the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit 67aa4acbc97f6a55b328e4e2305ef19cbe949d85 upstream.
`comedi_alloc_spriv()` allocates private storage for a comedi subdevice
and sets the `SRF_FREE_SPRIV` flag in the
3.12-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Lu
commit 2c62333a408f5badd2d2ffd7177f95deeccc5ca4 upstream.
Some firmware doesn't initialize initial backlight level to a proper
value and _BQC will return 0 on first time evaluation.
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit 411cabf79e684171669ad29a0628c400b4431e95 upstream.
Commit e82b89a6f19bae73fb064d1b3dd91fcefbb478f4 used strcat instead of
strcpy which can result in an overflow of
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Horman
commit 714b33d15130cbb5ab426456d4e3de842d6c5b8a upstream.
Stephan Mueller reported to me recently a error in random number generation in
the ansi cprng. If several small requests
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit d82ae52e68892338068e7559a0c0657193341ce4 upstream.
Without this patch all DM devices will default to BLK_MAX_SEGMENT_SIZE
(65536) even if the underlying device(s) have a
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bob Moore
commit 4be4be8fee2ee99a52f94f90d03d2f287ee1db86 upstream.
This change fixes a problem where a Store operation to an ArgX object
that contained a reference to a field object did not
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 51f0885e5415b4cc6535e9cdcc5145bfbc134353 upstream.
Dave Jones found another /proc issue with his Trinity tool: thanks to
the namespace model, we can have multiple /proc
This is the start of the stable review cycle for the 3.4.71 release.
There are 39 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 Fri Nov 29 00:56:06 UTC 2013.
Anything
On Tue, Nov 26, 2013 at 12:46:03AM +, Mark Brown wrote:
> lot changing the callers is probably the cleanest. I'll probably do
> that tomorrow if a patch doesn't turn up before then.
Sorry, that'll now be Wednesday - an unusually busy day started by
someone deciding to fell trees outside my
On Fri, 22 Nov 2013, Johannes Weiner wrote:
> But userspace in all likeliness DOES need to take action.
>
> Reclaim is a really long process. If 5 times doing 12 priority cycles
> and scanning thousands of pages is not enough to reclaim a single
> page, what does that say about the health of
With immutable biovecs we don't want code accessing bi_io_vec directly -
the uses this patch changes weren't incorrect since they all own the
bio, but it makes the code harder to audit for no good reason - also,
this will help with multipage bvecs later.
Signed-off-by: Kent Overstreet
Cc: Jens
When we start sharing biovecs, keeping bi_vcnt accurate for splits is
going to be error prone - and unnecessary, if we refactor some code.
So bio_segments() has to go - but most of the existing users just needed
to know if the bio had multiple segments, which is easier - add a
Now that we've got a mechanism for immutable biovecs -
bi_iter.bi_bvec_done - we need to convert drivers to use primitives that
respect it instead of using the bvec array directly.
The aoe code no longer has to manually iterate over partial bvecs, so
some struct members go away - other struct
301 - 400 of 1902 matches
Mail list logo
