On Fri, Feb 21, 2014 at 12:40 PM, poma wrote:
>
> Affected kernels - 3.14.0-0.rc3*:
>
> - 3.14.0-0.rc3.git0.1
> http://koji.fedoraproject.org/koji/buildinfo?buildID=498711
>
> - 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1
>
> - 3.14.0-0.rc3.git2.1
>
Hello,
On Fri, Feb 21, 2014 at 07:51:48AM -0500, Peter Hurley wrote:
> I think the vast majority of kernel code which uses the workqueue
> assumes there is a memory ordering guarantee.
Not really. Workqueues haven't even guaranteed non-reentrancy until
recently, forcing everybody to lock
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jens Axboe
commit c8123f8c9cb517403b51aa41c3c46ff5e10b2c17 upstream.
When mkfs issues a full device discard and the device only
supports discards of a smallish size, we can loop in
Hello,
The Project is about the exportation of 100,000 barrels of Light Crude
Oil daily out from Iraq to Turkey through my client's company in Iraq
at the rate of $92.00 per barrel. This amount to $9,200,000 daily. I ask
for your support as a foreigner to handle this business project with my
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka
commit 2995fa78e423d7193f3b57835f6c1c75006a0315 upstream.
This reverts commit be35f48610 ("dm: wait until embedded kobject is
released before destroying a device") and
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: NeilBrown
commit 2ec197db1a56c9269d75e965f14c344b58b2a4f6 upstream.
If an NFS client attempts to get a lock (using NLM) and the lock is
not available, the server will remember the
On Fri, 21 Feb 2014, Liu, Chuansheng wrote:
> > -Original Message-
> > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > Sent: Friday, February 21, 2014 7:53 PM
> > To: Liu, Chuansheng
> > Cc: linux-kernel@vger.kernel.org; Wang, Xiaoming
> > Subject: RE: [PATCH 1/2] genirq: Fix the
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Raymond Wanyoike
commit 3635c7e2d59f7861afa6fa5e87e2a58860ff514d upstream.
Interface #5 of 19d2:1270 is a net interface which has been submitted to the
qmi_wwan driver so consequently
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Marciniszyn
commit 2f75e12c4457a9b3d042c0a0d748fa198dc2ffaf upstream.
Research has shown that commit a77fcf895046 ("IB/qib: Use a single
txselect module parameter for serdes
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Oleg Nesterov
commit 789b5e0315284463617e106baad360cb9e8db3ac upstream.
Subsystems that want to register CPU hotplug callbacks, as well as perform
initialization for the CPUs that are
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Martin Schwidefsky
commit 8d7f6690cedb83456edd41c9bd583783f0703bf0 upstream.
The kernel currently crashes with a low-address-protection exception
if a user space process executes an
On 20/02/14 20:39, Luis R. Rodriguez wrote:
On Wed, Feb 19, 2014 at 11:13 AM, Zoltan Kiss wrote:
On 19/02/14 17:20, Luis R. Rodriguez wrote:
On 19/02/14 17:20, Luis R. Rodriguez also wrote:
Zoltan has noted though some use cases of IPv4 or IPv6 addresses on
backends though <...>
As
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: John Stultz
commit 6fdda9a9c5db367130cf32df5d6618d08b89f46a upstream.
As part of normal operaions, the hrtimer subsystem frequently calls
into the timekeeping code, creating a locking
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Borislav Petkov
commit cb6ef42e516cb8948f15e4b70dc03af8020050a2 upstream.
We're using edac_mc_workq_setup() both on the init path, when
we load an edac driver and when we change the
On 20/02/14 20:01, Luis R. Rodriguez wrote:
On Thu, Feb 20, 2014 at 5:19 AM, Zoltan Kiss wrote:
How about this: netback sets the root_block flag and a random MAC by
default. So the default behaviour won't change, DAD will be happy, and
userspace don't have to do anything unless it's using
On 20/02/14 20:24, Luis R. Rodriguez wrote:
On Thu, Feb 20, 2014 at 9:19 AM, Stephen Hemminger
wrote:
On Wed, 19 Feb 2014 09:59:33 -0800 "Luis R. Rodriguez"
wrote:
On Wed, Feb 19, 2014 at 9:08 AM, Stephen Hemminger
wrote:
Please only use the netlink/sysfs flags fields that already exist
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Naoya Horiguchi
commit 8d547ff4ac5927245e0833ac18528f939da0ee0e upstream.
mce-test detected a test failure when injecting error to a thp tail
page. This is because we take page
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Oberparleiter
commit 6583327c4dd55acbbf2a6f25e775b28b3abf9a42 upstream.
Commit d61931d89b, "x86: Add optimized popcnt variants" introduced
compile flag -fcall-saved-rdi for
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit d651aa1d68a2f0a7ee65697b04c6a92f8c0a12f2 upstream.
Each sub-buffer (buffer page) has a full 64 bit timestamp. The events on
that page use a 27 bit
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paul Gortmaker
commit 2c45aada341121438affc4cb8d5b4cfaa2813d3d upstream.
In allmodconfig builds for sparc and any other arch which does
not set CONFIG_SPARSE_IRQ, the following will be
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: KOSAKI Motohiro
commit 227d53b397a32a7614667b3ecaf1d89902fb6c12 upstream.
To use spin_{un}lock_irq is dangerous if caller disabled interrupt.
During aio buffer migration, we have a
3.5.7.31 -stable review patch. If anyone has any objections, please let me
know.
--
From: Harald Freudenberger
commit 0519e9ad89e5cd6e6b08398f57c6a71d9580564c upstream.
The aes-ctr mode uses one preallocated page without any concurrency
protection. When multiple threads run
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Vrabel
commit 564eb714f5f09ac733c26860d5f0831f213fbdf1 upstream.
xen/gntdev.h and xen/gntalloc.h both provide userspace ABIs so they
should be installed.
Signed-off-by: David
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit 87fbb2ac6073a7039303517546a76074feb14c84 upstream.
When the conversion was made to remove stop machine and use the breakpoint
logic instead, the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: "H. Peter Anvin"
commit 03bbd596ac04fef47ce93a730b8f086d797c3021 upstream.
If SMAP support is not compiled into the kernel, don't enable SMAP in
CR4 -- in fact, we should clear it,
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Raymond Wanyoike
commit 3635c7e2d59f7861afa6fa5e87e2a58860ff514d upstream.
Interface #5 of 19d2:1270 is a net interface which has been submitted to the
qmi_wwan driver so consequently
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jens Axboe
commit c8123f8c9cb517403b51aa41c3c46ff5e10b2c17 upstream.
When mkfs issues a full device discard and the device only
supports discards of a smallish size, we can loop in
Hi,
On 02/21/2014 01:47 PM, Luis Henriques wrote:
> 3.11.10.5 -stable review patch. If anyone has any objections, please let me
> know.
>
This was nack'ed by Greg KH a few days ago. Please see [1].
Regards,
Florian
[1] http://www.spinics.net/lists/stable/msg35959.html
> --
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?=
commit 0930b0950a8996aa88b0d2ba4bb2bab27cc36bc7 upstream.
\E[3J console code (secure clear screen) needs to update_screen(vc)
in order to
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicholas Bellinger
commit fc09149df6e20cfbb0bb86f10899607c321a31eb upstream.
This patch addresses a >= v3.11 free-after-use regression
in core_scsi3_emulate_pro_register() that was
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: "H. Peter Anvin"
commit 4640c7ee9b8953237d05a61ea3ea93981d1bc961 upstream.
If CONFIG_X86_SMAP is disabled, smap_violation() tests for conditions
which are incorrect (as the AC flag
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Doug Anderson
commit d3d89c468ceebbcf9423d1a3d66c5bf91f569570 upstream.
The ntc thermistor code was doing math whose temporary result might
have overflowed 32-bits. We need some casts
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steve French
commit 666753c3ef8fc88b0ddd5be4865d0aa66428ac35 upstream.
When mounting with smb2 (or smb2.1 or smb3) we need to check to make
sure that attempts to query or set extended
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Gleixner
commit dd5fd9b91a77b4c9c28b7ef9c181b1a875820d0a upstream.
AMD systems which use the C1E workaround in the amd_e400_idle routine
trigger the WARN_ON_ONCE in the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Oleg Nesterov
commit 789b5e0315284463617e106baad360cb9e8db3ac upstream.
Subsystems that want to register CPU hotplug callbacks, as well as perform
initialization for the CPUs that are
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Marciniszyn
commit 2f75e12c4457a9b3d042c0a0d748fa198dc2ffaf upstream.
Research has shown that commit a77fcf895046 ("IB/qib: Use a single
txselect module parameter for serdes
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: NeilBrown
commit 2ec197db1a56c9269d75e965f14c344b58b2a4f6 upstream.
If an NFS client attempts to get a lock (using NLM) and the lock is
not available, the server will remember the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steve French
commit 83e3bc23ef9ce7c03b7b4e5d3d790246ea59db3e upstream.
The get/set ACL xattr support for CIFS ACLs attempts to send old
cifs dialect protocol requests even when mounted
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steve French
commit d979f3b0a1f0b5499ab85e68cdf02b56852918b6 upstream.
Changeset 666753c3ef8fc88b0ddd5be4865d0aa66428ac35 added protocol
operations for get/setxattr to avoid calling
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Vrabel
commit 0160676bba69523e8b0ac83f306cce7d342ed7c8 upstream.
On hosts with more than 168 GB of memory, a 32-bit guest may attempt
to grant map an MFN that is error cannot
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Frediano Ziglio
commit 7cde9b27e7b3a2e09d647bb4f6d94e842698d2d5 upstream.
Due to the way kernel is initialized under Xen is possible that the
ring1 selector used by the kernel for the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jingoo Han
commit c542b53da9ffa4fe9de61149818a06aacae531f8 upstream.
The usage of strict_strtol() is not preferred, because strict_strtol()
is obsolete. Thus, kstrtol() should be used.
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Martin Schwidefsky
commit 8d7f6690cedb83456edd41c9bd583783f0703bf0 upstream.
The kernel currently crashes with a low-address-protection exception
if a user space process executes an
On 02/21/2014 05:03 AM, Tejun Heo wrote:
On Fri, Feb 21, 2014 at 12:13:16AM -0500, Peter Hurley wrote:
CPU 0| CPU 1
|
INIT_WORK(fw_device_workfn) |
|
workfn = funcA |
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mel Gorman
commit f98b7a772ab51b52ca4d2a14362fc0e0c8a2e0f3 upstream.
There was a large performance regression that was bisected to
commit 611ae8e3 ("x86/tlb: enable tlb flush range
How old?
On February 21, 2014 2:32:50 AM PST, Jan Beulich wrote:
>Just like for other ISA extension instruction uses we should check
>whether the assembler actually supports them. The fallback here simply
>is to encode an instruction with fixed operands (%eax and %ecx).
>
>Signed-off-by: Jan
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Henningsson
commit f47e5dc464251f661da9495fcbf003a0d22c1360 upstream.
This quirk is needed for the headset microphone to work.
Alsa-info at
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Borislav Petkov
commit 9da21b1509d8aa7ab4846722817d16c72d656c91 upstream.
Sanitize code even more to accept unsigned longs only and to not allow
polling intervals below 1 second as
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Borislav Petkov
commit cb6ef42e516cb8948f15e4b70dc03af8020050a2 upstream.
We're using edac_mc_workq_setup() both on the init path, when
we load an edac driver and when we change the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steven Noonan
commit a9f180345f5378ac87d80ed0bea55ba421d83859 upstream.
I started noticing problems with KVM guest destruction on Linux
3.12+, where guest memory wasn't being cleaned
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Vrabel
commit 3661371701e714f0cea4120f6a365340858fb4e4 upstream.
Backend drivers shouldn't transistion to CLOSED unless the frontend is
CLOSED. If a backend does transition to
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Prarit Bhargava
commit 79040cad3f8235937e229f1b9401ba36dd5ad69b upstream.
If you do
echo 0 > /sys/module/edac_core/parameters/edac_mc_poll_msec
the following stack trace is output
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Hellstrom
commit cf5e3413337309050c05e13dcebe85b7194a21e5 upstream.
The call to ttm_eu_backoff_reservation() as part of an error path would cause
a lock imbalance if the
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Airlie
commit ec22b4aa993abbd18f5bbbcb20a1c56be3b1d38b upstream.
mode->mdev otherwise the bw limits never kick in.
Reported in RHEL testing.
Signed-off-by: Dave Airlie
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 276ab336b4c6e483d12fd46cbf24f97f71867710 upstream.
AD1983 has flexible loopback routes and the generic parser would take
wrong path confusingly instead of taking
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Florian Vaussard
commit e7f2a444891cb39f11d5429467d0fd7e011fe7fe upstream.
Commit c420619 "pinctrl: pinconf: remove checks on ops->pin_config_get"
removed the check on (ops != NULL)
3.11.10.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tony Prisk
commit f17248ed868767567298e1cdf06faf8159a81f7c upstream.
Due to an assumption in the VT8500 pinctrl driver, the value passed
from devicetree for 'wm,pull' was not
On Fri, 21 Feb 2014 16:09:25 +0400
Kirill Tkhai wrote:
>
>
> 21.02.2014, 15:39, "Kirill Tkhai" :
> > 21.02.2014, 14:37, "Peter Zijlstra" :
> >
> >> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
> >>> Since deadline tasks share rt bandwidth, we must care about
> >>>
On Tue, Feb 18, 2014 at 10:10:03AM -0800, Kees Cook wrote:
> On Mon, Feb 17, 2014 at 4:34 AM, Dave Martin wrote:
> > On Fri, Feb 14, 2014 at 11:11:07AM -0800, Kees Cook wrote:
> >> On Fri, Feb 14, 2014 at 8:22 AM, Dave Martin wrote:
> >> > On Thu, Feb 13, 2014 at 05:04:10PM -0800, Kees Cook
Hi Hanjun,
(Adding MarcZ for his views on GIC)
On 20/02/14 03:59, Hanjun Guo wrote:
> Hi Sudeep,
>
> Thanks for your comments, please refer to the replies below. :)
>
> On 2014年02月19日 22:33, Sudeep Holla wrote:
>> Hi Hanjun,
>>
>> On 18/02/14 16:23, Hanjun Guo wrote:
>>> Get apic id from MADT
On Tue, Feb 18, 2014 at 05:00:27PM -0500, Luiz Capitulino wrote:
> It should read "reclaimable slab" and not "reclaimable swap".
>
> Signed-off-by: Luiz Capitulino
> ---
> fs/proc/meminfo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/proc/meminfo.c
Two cps in parallel managed to stall the the ext4 fs. It seems that
journal code is either waiting for locks or sleeping waiting for
something to happen. This seems similar to what Mike observed on ext3,
here is his description:
|With an -rt kernel, and a heavy sync IO load, tasks can jam
|up on
Hi all!
Ok, I hope that this is the last update of the patches which add basic
support for dynamic allocation of memory reserved regions defined in
device tree.
This time I've mainly sliced the main patch into several smaller pieces
to make the changes easier to understand and fixes some minor
On 02/21/2014 02:25 PM, Kishon Vijay Abraham I wrote:
> Hi Roger,
>
> On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
>> Hi,
>>
>> On 02/12/2014 11:46 AM, Kishon Vijay Abraham I wrote:
>>> On Wednesday 29 January 2014 08:17 PM, Heikki Krogerus wrote:
Hi,
On Tue, Jan
This patch adds support for dynamically allocated reserved memory regions
declared in device tree. Such regions are defined by 'size', 'alignment'
and 'alloc-ranges' properties.
Based on previous code provided by Josh Cartwright
Signed-off-by: Marek Szyprowski
---
drivers/of/Kconfig
Hello Thomas,
> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Friday, February 21, 2014 7:53 PM
> To: Liu, Chuansheng
> Cc: linux-kernel@vger.kernel.org; Wang, Xiaoming
> Subject: RE: [PATCH 1/2] genirq: Fix the possible synchronize_irq()
> wait-forever
>
This patch adds support for static (defined by 'reg' property) reserved
memory regions declared in device tree.
Memory blocks can be reliably reserved only during early boot. This must
happen before the whole memory management subsystem is initialized,
because we need to ensure that the given
This patch adds code for automated assignment of reserved memory regions
to struct device. reserved_mem->ops->device_init()/device_cleanup()
callbacks are called to perform reserved memory driver specific
initialization and cleanup. The code looks for 'memory-region' property
in the client device
Use recently introduced of_reserved_mem_device_init() function to
automatically assign respective reserved memory region to the newly created
platform and amba device.
Signed-off-by: Marek Szyprowski
---
drivers/of/platform.c |7 +++
1 file changed, 7 insertions(+)
diff --git
Add support for custom reserved memory drivers. Call their init() function
for each reserved region and prepare for using operations provided by them
with by the reserved_mem->ops array.
Based on previous code provided by Josh Cartwright
Signed-off-by: Marek Szyprowski
---
From: Grant Likely
Reserved memory nodes allow for the reservation of static (fixed
address) regions, or dynamically allocated regions for a specific
purpose.
Signed-off-by: Grant Likely
[joshc: Based on binding document proposed (in non-patch form) here:
Enable reserved memory initialization from device tree.
Signed-off-by: Marek Szyprowski
---
arch/arm/Kconfig |1 +
arch/arm/mm/init.c |2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index e25419817791..d0262bea8020 100644
---
Enable reserved memory initialization from device tree.
Signed-off-by: Marek Szyprowski
---
arch/arm64/Kconfig |1 +
arch/arm64/mm/init.c |1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 27bbcfc7202a..6abf15407dca 100644
---
Add support for handling 'shared-dma-pool' reserved-memory device tree
nodes.
Based on previous code provided by Josh Cartwright
Signed-off-by: Marek Szyprowski
---
drivers/base/dma-coherent.c | 41 +
1 file changed, 41 insertions(+)
diff --git
Refactor internal dma_contiguous_init_reserved_mem() function, which
creates CMA area from previously reserved memory region and add support
for handling 'shared-dma-pool' reserved-memory device tree nodes.
Based on previous code provided by Josh Cartwright
Signed-off-by: Marek Szyprowski
---
Enable reserved memory initialization from device tree.
Signed-off-by: Marek Szyprowski
---
arch/powerpc/Kconfig |1 +
arch/powerpc/kernel/prom.c |3 +++
2 files changed, 4 insertions(+)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index 957bf344c0f5..3b6617fed8fc
Hi Roger,
On Wednesday 19 February 2014 06:07 PM, Roger Quadros wrote:
> Hi,
>
> On 02/12/2014 11:46 AM, Kishon Vijay Abraham I wrote:
>> On Wednesday 29 January 2014 08:17 PM, Heikki Krogerus wrote:
>>> Hi,
>>>
>>> On Tue, Jan 28, 2014 at 10:30:36AM -0600, Felipe Balbi wrote:
On Tue, Jan
On Thu, Feb 20, 2014 at 01:17:44PM -0500, Rik van Riel wrote:
> On 02/20/2014 01:14 PM, Dave Jones wrote:
> > On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote:
> > > In use after free situations, it is possible for one thread to write to
> > > memory that has just been reallocated
On Fri, Feb 21, 2014 at 04:24:21AM +, Joel Fernandes wrote:
> Currently, EDMA driver uses of_address_to_resource for getting Channel
> controller and x-bar register resources. Use platform_get_resource_by_name
> instead regardless of whether its DT-boot or not, document the new reg-names
>
Why is this x86 only code?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This fixes bug introduced in 667a6b7a (regulator: max14577: Add missing
of_node_put). The DTS parsing function returned number of matched
regulators as success status which then was compared against 0 in probe.
Result was a probe fail after successful parsing the DTS:
max14577-regulator: probe of
21.02.2014, 15:39, "Kirill Tkhai" :
> 21.02.2014, 14:37, "Peter Zijlstra" :
>
>> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
>>> Since deadline tasks share rt bandwidth, we must care about
>>> bandwidth timer set. Otherwise rt_time may grow up to infinity
>>> in
From: "Lad, Prabhakar"
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/omap3isp/isp.c|2 +-
drivers/media/platform/omap3isp/ispccdc.c|2 +-
drivers/media/platform/omap3isp/ispccp2.c|4 ++--
drivers/media/platform/omap3isp/isphist.c|2 +-
From: "Lad, Prabhakar"
This patch series include fixing some typos and
removal of unwanted comments.
Lad, Prabhakar (3):
media: omap3isp: fix typos
media: omap3isp: ispccdc: remove unwanted comments
media: omap3isp: rename the variable names in description
From: "Lad, Prabhakar"
this patch renames the variable in the description to
match it appropriately to function definition.
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/omap3isp/isp.h| 12 ++--
drivers/media/platform/omap3isp/ispccdc.c|8
From: "Lad, Prabhakar"
this patch removes the description of members which
does not exists for ispccdc_lsc structure.
Signed-off-by: Lad, Prabhakar
---
drivers/media/platform/omap3isp/ispccdc.h |6 --
1 file changed, 6 deletions(-)
diff --git
On Thu, Feb 20, 2014 at 01:14:40PM -0500, Dave Jones wrote:
> On Thu, Feb 20, 2014 at 06:44:59PM +0100, Mateusz Guzik wrote:
> > In use after free situations, it is possible for one thread to write to
> > memory that has just been reallocated to a new user. This could open up
> > potential
On Thu, Feb 20, 2014 at 06:23:13PM +, Felipe Balbi wrote:
> Hi,
>
> On Wed, Feb 19, 2014 at 03:10:45PM +0530, Subbaraya Sundeep Bhatta wrote:
> > This patch adds xilinx axi usb2 device driver support
> >
> > Signed-off-by: Subbaraya Sundeep Bhatta
> > ---
> >
This is preparation patch to add multi stream support to zcomp.
Introduce struct zcomp_strm_single and a set of functions to manage zcomp_strm
stream access. zcomp_strm_single implements single compession stream, same way
as current zcomp implementation. This moves zcomp_strm stream control and
This patchset introduces zcomp compression backend abstraction
adding ability to support compression algorithms other than LZO;
support for multi compression streams, making parallel compressions
possible.
v5->v6 (reviewed by Minchan Kim):
-- handle single compression stream case separately,
ZRAM performs direct LZO compression algorithm calls, making it the one and
only option. Introduce compressing backend abstraction zcomp in order to
support multiple compression algorithms with the following set of operations:
.create
.destroy
.compress
.decompress
1) Add ZRAM_MULTI_STREAM configuration option and make multi stream
zcomp support available.
2) Introduce zram device attribute max_comp_streams to show and store
current zcomp's max number of zcomp streams (num_strm).
3) Extend zcomp zcomp_create() with `num_strm' parameter. `num_strm'
limits
This patch implements multi stream compression support.
Introduce struct zcomp_strm_multi and a set of functions to manage
zcomp_strm stream access. zcomp_strm_multi has a list of idle zcomp_strm
structs, spinlock to protect idle list and wait queue, making it possible
to perform parallel
Add max_comp_streams device attribute documentation.
Signed-off-by: Sergey Senozhatsky
---
Documentation/ABI/testing/sysfs-block-zram | 9 -
Documentation/blockdev/zram.txt| 24 +++-
2 files changed, 27 insertions(+), 6 deletions(-)
diff --git
Do not perform direct LZO compress/decompress calls, initialise
and use zcomp LZO backend (single compression stream) instead.
Signed-off-by: Sergey Senozhatsky
---
drivers/block/zram/Makefile | 2 +-
drivers/block/zram/zram_drv.c | 62 +++
On Fri, 21 Feb 2014, Liu, Chuansheng wrote:
> > > > I think you have a point there, but not on x86 wherre the atomic_dec
> > > > and the spinlock on the queueing side are full barriers. For non-x86
> > > > there is definitely a potential issue.
> > > >
> > > But even on X86, spin_unlock has no
[Adding Tony Prisk to Cc]
On Fri, Feb 21, 2014 at 06:31:30AM +, Alistair Popple wrote:
> Currently the ppc-of driver uses the compatibility string
> "usb-ehci". This means platforms that use device-tree and implement an
> EHCI compatible interface have to either use the ppc-of driver or add
>
Affected kernels - 3.14.0-0.rc3*:
- 3.14.0-0.rc3.git0.1
http://koji.fedoraproject.org/koji/buildinfo?buildID=498711
- 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1
- 3.14.0-0.rc3.git2.1
http://koji.fedoraproject.org/koji/buildinfo?buildID=499061
- 3.14.0-0.rc3.git5.1
21.02.2014, 14:37, "Peter Zijlstra" :
> On Thu, Feb 20, 2014 at 02:16:00AM +0400, Kirill Tkhai wrote:
>
>> Since deadline tasks share rt bandwidth, we must care about
>> bandwidth timer set. Otherwise rt_time may grow up to infinity
>> in update_curr_dl(), if there are no other available RT
Stephen Rothwell wrote:
> Today's linux-next merge of the akpm-current tree got a conflict in
> drivers/sbus/char/jsflash.c between commit 967f038e491b ("Sparc:
> sparc_cpu_model isn't in asm/system.h any more [ver #2]") from the sparc
> tree and commit 695f43eb1721 ("asm/system.h: sparc:
601 - 700 of 1526 matches
Mail list logo
