> Reviewed-by: Zhao Junwang
>
> kfree will check that.
How does this feedback fit to a check before a call
of the vfree() function?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo in
08.07.2015 19:30, Sebastien Rannou пишет:
Hi Stas,
On Fri, 27 Mar 2015, Stas Sergeev wrote:
When MDIO bus is unavailable (common setup for SGMII), the in-band
signaling must be used to correctly track link state.
This patch enables the in-band status delivery and interrupts for
links state cha
On Wed, 8 Jul 2015, Peter Zijlstra wrote:
> On Wed, Jul 08, 2015 at 11:17:38AM -0400, Mikulas Patocka wrote:
> > Hi
> >
> > I found out that the patch a66734297f78707ce39d756b656bfae861d53f62 breaks
> > the kernel on processors without performance counters, such as AMD K6-3.
> > Reverting the
On Fri, Jul 03, 2015 at 05:13:42PM +0800, Zidan Wang wrote:
> Add sysclk auto mode. When it's sysclk auto mode, if the MCLK is
> available for clock configure, using MCLK to provide sysclk directly,
> otherwise, search a available pll out frequcncy and set pll.
>
> TX and RX share the same sysclk
On 07/08/2015 06:25 AM, Paul Osmialowski wrote:
> Signed-off-by: Paul Osmialowski
> ---
> security/smack/Makefile | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/security/smack/Makefile b/security/smack/Makefile
> index ee2ebd5..bd6927c 100644
> --- a/security/smack/Makefile
> +++ b/s
On 07/06/2015 09:22 PM, Nicholas Krause wrote:
This removes no longer used marcos at the top of the driver
due tilepro.c due to having no proper values nor never being
used by this driver code.
Signed-off-by: Nicholas Krause
---
drivers/net/ethernet/tile/tilepro.c | 13 -
1 file c
Quoting Morten Rasmussen (2015-07-07 11:24:27)
> From: Juri Lelli
>
> Since the true utilization of a long running task is not detectable while
> it is running and might be bigger than the current cpu capacity, create the
> maximum cpu capacity head room by requesting the maximum cpu capacity onc
On 7/8/2015 3:25 AM, Paul Osmialowski wrote:
> This patchset partially summarizes effects of collective work by
> Karol Lewandowski and Paul Moore towards introduction of LSM into KDBUS.
>
> These patches originate from following git repositories:
>
> git://git.infradead.org/users/pcmoore/selinux (
Quoting Morten Rasmussen (2015-07-07 11:24:28)
> From: Juri Lelli
>
> Use the cpu argument of cpufreq_sched_set_cap() to handle per_cpu writes,
> as the thing can be called remotely (e.g., from load balacing code).
>
> cc: Ingo Molnar
> cc: Peter Zijlstra
>
> Signed-off-by: Juri Lelli
Looks
Quoting Morten Rasmussen (2015-07-07 11:24:27)
> From: Juri Lelli
>
> Since the true utilization of a long running task is not detectable while
> it is running and might be bigger than the current cpu capacity, create the
> maximum cpu capacity head room by requesting the maximum cpu capacity onc
On 07/08/2015 09:13 AM, Stephen Smalley wrote:
> On Sun, Jun 14, 2015 at 12:48 PM, Hugh Dickins wrote:
>> It appears that, at some point last year, XFS made directory handling
>> changes which bring it into lockdep conflict with shmem_zero_setup():
>> it is surprising that mmap() can clone an inod
On 7/8/2015 6:42 AM, Stephen Smalley wrote:
> On 07/08/2015 06:25 AM, Paul Osmialowski wrote:
>> This adds implementation of three smack callbacks sitting behind kdbus
>> security hooks as proposed by Karol Lewandowski.
>>
>> Originates from:
>>
>> git://git.infradead.org/users/pcmoore/selinux (bra
On 07/08/2015 03:46 PM, Ralf Baechle wrote:
I don't see any signoffs.
arch/mips/Kconfig | 4 -
arch/mips/kernel/Makefile | 1 -
arch/mips/kernel/i8259.c| 384
drivers/irqchip/Kconfig | 4 +
drivers/irqchip/Makefile
On Wed, 08 Jul 2015 08:22:20 -0700
Daniel Grimshaw wrote:
> I am a high school student trying to become familiar with Linux kernel
> development.
That's great!
> The btrfs documentation in Documentation/filesystems had a
> few typos and errors in whitespace. This patch corrects both of these.
Hi Stas,
On Fri, 27 Mar 2015, Stas Sergeev wrote:
> When MDIO bus is unavailable (common setup for SGMII), the in-band
> signaling must be used to correctly track link state.
> This patch enables the in-band status delivery and interrupts for
> links state changes, namely:
> - link up/down
> - li
Le Wednesday 08 July 2015 à 16:18 +0200, Iago López Galeiras a écrit :
> On 07/04/2015 07:07 PM, Jean Delvare wrote:
> > On Fri, 3 Jul 2015 11:10:45 +0200, Iago López Galeiras wrote:
> >> The purpose of this option is enabling /proc//task//children
> >> without
> >> having to enable CHECKPOINT_RES
On 07/08/2015 01:34 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.0.8 release.
> There are 55 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 sho
Le Wednesday 08 July 2015 à 15:50 +0100, Djalal Harouni a écrit :
> On Wed, Jul 08, 2015 at 04:18:28PM +0200, Iago López Galeiras wrote:
> > On 07/04/2015 07:07 PM, Jean Delvare wrote:
> > > That being said, I am curious... Is this interface so expensive that it
> > > really deserves a separate opt
On 07/08/2015 01:34 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.2 release.
> There are 56 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 sho
On 07/08/2015 01:33 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.48 release.
> There are 30 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 s
On 07/08/2015 01:31 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.84 release.
> There are 14 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 s
On Sun, Jul 5, 2015 at 2:22 PM, Linus Torvalds
wrote:
> It's Sunday, two weeks have passed, and the merge window is closed. I
> just pushed out the tag to the git trees, and tar-balls and patches
> should be mirroring out too.
>
> I thought this release would be one of the biggest ones ever, but i
On Wed, 8 Jul 2015 12:02:49 -0400
Steven Rostedt wrote:
>
> Well, any testing will have to wait. The reason I found this is because
> it caused my own tests to fail for a bug fix I'm testing (unrelated to
> this) that I'm getting ready to send to you. My box to run this on is
> back to running th
Hello Greg,
Here's the complete list of linux-next/UFS patches needed
to stop regressions in write mode:
13b987ea2758
fs/ufs: revert "ufs: fix deadlocks introduced by sb mutex merge"
cdd9eefdf905
fs/ufs: restore s_lock mutex
12ecbb4b1d76
ufs: Fix warning from unlock_new_inode()
On 7/8/2015 3:25 AM, Paul Osmialowski wrote:
> Originates from:
>
> https://github.com/lmctl/kdbus.git (branch: kdbus-lsm-v4.for-systemd-v212)
> commit: aa0885489d19be92fa41c6f0a71df28763228a40
>
> Signed-off-by: Karol Lewandowski
> Signed-off-by: Paul Osmialowski
> ---
> ipc/kdbus/bus.c
With the ARMv8.1 VHE, the kernel can run in HYP mode, and thus
use the HYP timer instead of the normal guest timer in a mostly
transparent way, except for the interrupt line.
This patch reworks the arch timer code to allow the selection of
the HYP PPI, possibly falling back to the guest timer if n
ARMv8.1 comes with the "Virtualization Host Extension" (VHE for
short), which enables simpler support of Type-2 hypervisors.
This extension allows the kernel to directly run at EL2, and
significantly reduces the number of system registers shared between
host and guest, reducing the overhead of vir
With the kernel running at EL2, there is no point trying to
configure page tables for HYP, as the kernel is already mapped.
Take this opportunity to refactor the whole init a bit, allowing
the various parts of the hypervisor bringup to be split across
multiple functions.
Signed-off-by: Marc Zyngi
The kern_hyp_va macro is pretty meaninless with VHE, as there is
only one mapping - the kernel one.
In order to keep the code readable and efficient, use runtime
patching to replace the 'and' instruction used to compute the VA
with a 'nop'.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm
With ARMv8.1 VHE extension, it will be possible to run the kernel
at EL2 (aka HYP mode). In order for the kernel to easily find out
where it is running, add a new predicate that returns whether or
not the kernel is in HYP mode.
For completeness, the 32bit code also get such a predicate (always
ret
With VHE, the host never issues an HVC instruction to get into the
KVM code, as we can simply branch there.
Use runtime code patching to simplify things a bit.
Signed-off-by: Marc Zyngier
---
arch/arm64/kvm/hyp.S| 43 ---
arch/arm64/kvm/vhe-macros
In order to switch between host and guest, a VHE-enabled kernel
must use different accessors for certain system registers.
This patch uses runtime patching to use the right instruction
when required...
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/kvm_asm.h | 40 ++--
arch/arm64/k
Add a new ARM64_HAS_VIRT_HOST_EXTN features to indicate that the
CPU has the ARMv8,1 VHE capability.
This will be used to trigger kernel patching in KVM.
Signed-off-by: Marc Zyngier
---
arch/arm64/include/asm/cpufeature.h | 3 ++-
arch/arm64/kernel/cpufeature.c | 11 +++
2 files c
With the ARMv8.1 VHE, the architecture is able to (almost) transparently
run the kernel at EL2, despite being written for EL1.
This patch takes care of the "almost" part, mostly preventing the kernel
from dropping from EL2 to EL1, and setting up the HYP configuration.
Signed-off-by: Marc Zyngier
As we're starting to get different requirements for non-VHE and VHE
code paths, use a slightly more fine-grained approach:
- __save/restore_sysregs: save/restore non-shared sysregs
- __save/restore_shared_sysregs: save/restore only shared sysregs
Of course, non-VHE always requires both.
Signed-o
With VHE enabled, it is possible to let the kernel handle an interrupt
without saving the full guest context, and without restoring the full
host context either. This reduces the latency of handling an interrupt.
When an interrupt fires we can:
- save the guest's general purpose registers, shared
Having both VHE and non-VHE capable CPUs in the same system
is likely to be a recipe for disaster.
If the boot CPU has VHE, but a secondary is not, we won't be
able to downgrade and run the kernel at EL1. Add CPU hotplug
to the mix, and this produces a terrifying mess.
Let's solve the problem onc
Running the kernel in HYP mode requires the HCR_E2H bit to be set
at all times, and the HCR_TGE bit to be set when running as a host
(and cleared when running as a guest).
Also add some cryptic macros to deal with cpp macro expansion inside
asm macros...
Signed-off-by: Marc Zyngier
---
arch/arm
On a VHE-capable system, there is no point in setting VTCR_EL2
at KVM init time. We can perfectly set it up when the kernel
boots, removing the need for a more complicated configuration.
In order to allow this, turn VTCR_EL2 setup into a macro that
we'll be able to reuse at boot time.
Signed-off-
On wo, 2015-07-08 at 17:42 +0200, Espen Carlsen wrote:
> I have tested my suggested changes on:
> CentOS 6.5, 7.0, Ubuntu 14.04 and 12.04. After the patch the kernel
> -devel package will be correct on all systems.
> Without the patch, only CentOS generates correct packages.
Wild guess: do the Ubu
>From 8956df8fa1a669e8e476456e4afe0eccd8174684 Mon Sep 17 00:00:00 2001
From: Chao Yu
Date: Wed, 8 Jul 2015 20:49:05 +0800
Subject: [PATCH] f2fs: maintain extent cache in separated file
This patch moves extent cache related code from data.c into extent_cache.c
since extent cache is independent fe
On Wednesday 08 July 2015 17:18:20 Johannes Thumshirn wrote:
> Destroy battery_id IDR on module exit, reclaiming the allocated
> memory.
>
> This was detected by the following semantic patch (written by Luis
> Rodriguez )
>
> @ defines_module_init @
> declarer name module_init, module_exit;
> dec
This patch adds the DT binding documentation for the FDMA xbar hw
found on STi based chipsets from STMicroelectronics.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/dma/st_fdma.txt | 24 +++
1 file changed, 24 insertions(+)
To increase the number of peripheral requests, the FDMA crossbar
can multiplex up to 96 peripheral requests to one of 3 fdma
controllers.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
---
drivers/dma/Kconfig| 11
drivers/dma/Makefile | 1 +
drivers/dma/st_fdma.
This patch adds the FDMA driver files to the STi
section of the maintainers file.
Signed-off-by: Peter Griffin
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8133cef..8cb1ad9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1503,6 +1503,8 @@ S
This DMA controller is found on all STi chipsets.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 6d83a1b..370dd85 100644
--- a/arch/arm/con
These nodes are required to get the fdma and xbar driver working
on STiH407 based silicon.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-family.dtsi | 59 +++
1 file changed, 59 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch
Hi,
This patchset adds support for the Flexible Direct Memory Access (FDMA) core
found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU
with a dedicated firmware. It is a general purpose DMA controller supporting
16 independent channels and data can be moved from memory to memo
This patch adds support for the Flexible Direct Memory Access (FDMA) core
driver. The FDMA is a slim core CPU with a dedicated firmware.
It is a general purpose DMA controller capable of supporting 16
independent DMA channels. Data moves maybe from memory to memory
or between memory and paced laten
On Wed, Jul 08, 2015 at 02:27:50PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> sk_prot->proto_cgroup is allowed to return NULL but sock_update_memcg
> doesn't check for NULL. The function relies on the mem_cgroup_is_root
> check because we shouldn't get NULL otherwise because
> mem_cgroup
This patch adds the DT binding documentation for the FDMA constroller
found on STi based chipsets from STMicroelectronics.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/dma/st_fdma.txt | 76 +++
1 file changed, 76 insertions(
On Tue, Jul 07, 2015 at 08:56:37AM -0700, Andy Lutomirski wrote:
> On Tue, Jul 7, 2015 at 8:43 AM, Andrew Vagin wrote:
> > On Mon, Jul 06, 2015 at 10:10:32AM -0700, Andy Lutomirski wrote:
> >> On Mon, Jul 6, 2015 at 1:47 AM, Andrey Vagin wrote:
> >> > Currently we use the proc file system, where
On Wed, Jul 08, 2015 at 11:17:38AM -0400, Mikulas Patocka wrote:
> Hi
>
> I found out that the patch a66734297f78707ce39d756b656bfae861d53f62 breaks
> the kernel on processors without performance counters, such as AMD K6-3.
> Reverting the patch fixes the problem.
>
> The static key rdpmc_alway
> > In commit:8a9e62a "sched/numa: Prefer NUMA hotness over cache hotness"
> > sched feature NUMA was always set to true. However this sched feature was
> > suppose to be enabled on NUMA boxes only thro set_numabalancing_state().
> >
> > To get back to the above behaviour, bring back NUMA_FAVOUR_HI
On Wed, Jul 08, 2015 at 02:27:49PM +0200, Michal Hocko wrote:
> From: Tejun Heo
>
> Restructure it to lower nesting level and help the planned threadgroup
> leader iteration changes.
>
> This is pure reorganization.
>
> Signed-off-by: Tejun Heo
> Cc: Johannes Weiner
> Acked-by: Michal Hocko
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: James Smart
commit 27f344eb15dd0da80ebec80c7245e8c85043f841 upstream.
Add a memory barrier to ensure the valid bit is read before
any of the cqe payload is read. This fixes an issue
On Wed, 8 Jul 2015 11:59:39 -0400
Steven Rostedt wrote:
> I'll test it again, even though I already did (see below).
Well, any testing will have to wait. The reason I found this is because
it caused my own tests to fail for a bug fix I'm testing (unrelated to
this) that I'm getting ready to sen
Patch 1 is just a quick update to MAINTAINERS for include/linux/pmem.h.
Patches 2 and 3 in this series contain correctness fixes for the NFIT BLK I/O
path, which in my opinion need to be pulled in for v4.2. These fixes include
making sure that the block control registers are properly flushed befo
On Wed, Jul 08, 2015 at 02:27:48PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> We currently have only one caller of mem_cgroup_select_victim_node which
> is sitting in mm/vmscan.c and which is already wrapped by CONFIG_MEMCG
> ifdef. Now that we have struct mem_cgroup visible outside of
>
发自我的 iPhone
> 在 2015年7月8日，下午10:03，Arnaldo Carvalho de Melo 写道：
>
> Em Wed, Jul 08, 2015 at 01:13:49PM +, Wang Nan escreveu:
>> Hi Arnaldo Carvalho de Melo,
>
> Hi Wang (hope this shorter form is ok on your country, calling me just
> "Arnaldo" is fine in mine :-))
>
>> I rearranged the
The file include/linux/pmem.h was recently created to hold the PMEM API,
and is logically part of the PMEM driver. Add an entry for this file to
MAINTAINERS.
Signed-off-by: Ross Zwisler
Cc: Greg KH
Cc: Dan Williams
Cc: linux-nvd...@lists.01.org
---
MAINTAINERS | 1 +
1 file changed, 1 insert
From: Kan Liang
When multiple events are sampled it may not be needed to collect fine
grained time stamps on all events. The sample sites are usually nearby.
It's enough to have time stamps on the regular reference events.
This patchkit adds the ability to turn off time stamps per event. This
in
From: Kan Liang
This patch extends the OPT_CALLBACK/OPT_CALLBACK_NOOPT to support 'set'
item of struct option. So the perf knows whether an option was set by
user.
The new macros are used by call-graph options.
Signed-off-by: Kan Liang
---
tools/perf/builtin-record.c | 4 ++--
tools/perf/p
From: Kan Liang
Add tests in tests/parse-events.c to check callgrap and time option
Signed-off-by: Kan Liang
---
tools/perf/tests/parse-events.c | 28
1 file changed, 28 insertions(+)
diff --git a/tools/perf/tests/parse-events.c b/tools/perf/tests/parse-events.c
i
On Wed, 8 Jul 2015 08:53:34 -0700
Linus Torvalds wrote:
> Anyway, to make a long rant more on-point, does this alternative
> version work for you?
I'll test it again, even though I already did (see below).
>
> diff --git a/kernel/auditsc.c b/kernel/auditsc.c
> index 09c65640cad6..e85bd
Update the nfit block I/O path to use the new PMEM API and to adhere to
the read/write flows outlined in the "NVDIMM Block Window Driver
Writer's Guide":
http://pmem.io/documents/NVDIMM_Driver_Writers_Guide.pdf
This includes adding support for targeted NVDIMM flushes called "flush
hints" in the A
From: Kan Liang
'period' param is not defined in
/sys/bus/event_sources/devices//format/*
Signed-off-by: Kan Liang
---
tools/perf/Documentation/perf-record.txt | 8
1 file changed, 8 insertions(+)
diff --git a/tools/perf/Documentation/perf-record.txt
b/tools/perf/Documentation/perf-
Add support in the NFIT BLK I/O path for the "latch" flag
defined in the "Get Block NVDIMM Flags" _DSM function:
http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf
This flag requires the driver to read back the command register after it
is written in the block I/O path. This ensures that
From: Kan Liang
This patchkit adds the ability to turn off callgraphs and time stamps
per event. This in term can reduce sampling overhead and the size of
the perf.data.
Changes since V1:
- Break up V1 patches into three patches(parse option changes,
partial time support and partial callgr
From: Kan Liang
When multiple events are sampled it may not be needed to collect
callgraphs for all of them. The sample sites are usually nearby, and
it's enough to collect the callgraphs on a reference event (such as
precise cycles or precise instructions).
This patchkit adds the ability to turn
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Kamal Mostafa
This reverts commit a39d787c6d2df9850559923ffb7516f1011cf54e.
Not suitable for 3.13 (no bpf_jit_binary_free).
Cc: Brad Figg
Signed-off-by: Kamal Mostafa
---
arch/a
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Sasha Levin
commit 161f873b89136eb1e69477c847d5a5033239d9ba upstream.
We used to read file_handle twice. Once to get the amount of extra
bytes, and once to fetch the entire structu
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Kamal Mostafa
This reverts commit a40cec456029f3c743ee93ec7d0c7382c640eb8f.
New feature; not qualified for -stable kernels.
Signed-off-by: Kamal Mostafa
---
drivers/hv/hyperv_vmb
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Kamal Mostafa
This reverts commit bb551e6492d6f9e1fce1b7be8d7d7220e3031266.
New feature; not qualified for -stable kernels.
Signed-off-by: Kamal Mostafa
---
drivers/hv/hyperv_vmb
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Philippe Reynes
commit a29ef819f3f34f89a1b9b6a939b4c1cdfe1e85ce upstream.
According to the imx27 documentation, fec has a 4 Kbyte
memory space map. Moreover, the actual 16 Kbyte map
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Paul Cercueil
commit c2a8b623a089d52c199e305e7905829907db8ec8 upstream.
We unfortunately can't use ~0UL for the scan mask to indicate that the
only valid scan mask is all channels s
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Al Viro
commit 2159184ea01e4ae7d15f2017e296d4bc82d5aeb0 upstream.
when we find that a child has died while we'd been trying to ascend,
we should go into the first live sibling itsel
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Mark Rutland
commit 965278dcb8ab0b1f666cc47937933c4be4aea48d upstream.
At boot time we round the memblock limit down to section size in an
attempt to ensure that we will have mapped
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Chris Lesiak
commit adba657533bdd255f7b78bc8a324091f46b294cd upstream.
When configured via device tree, the associated iio device needs to be
measuring voltage for the conversion to
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Ben Hutchings
pipe_iov_copy_{from,to}_user() may be tried twice with the same iovec,
the first time atomically and the second time not. The second attempt
needs to continue from the
On Wed, Jul 8, 2015 at 8:26 AM, Steven Rostedt wrote:
>
> Yes, strnlen_user() returns 0 on fault, but if you look at what len is
> set to, than you would notice that on fault len would be -1.
Ugh. I hate that. It looks bad, but it's also pointless.
It turns out that "len" is unsigned (it's a "si
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Paul Cercueil
commit 7323d59862802ca109451eeda9777024a7625509 upstream.
Previously, the two voltage channels had the same ID, which didn't cause
conflicts in sysfs only because one
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Rusty Russell
commit 83a35114d0e4583e6b0ca39502e68b6a92e2910c upstream.
This bug has been there since day 1; addresses in the top guest physical
page weren't considered valid. You
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Guenter Roeck
commit 1b63bf617206ff35b93c57c67bbe067ac735a85a upstream.
The following error message is seen when loading the nct6775 driver
with DEBUG_LOCK_ALLOC enabled.
BUG: key
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Sasha Levin
commit dcbff39da3d815f08750552fdd04f96b51751129 upstream.
match_token() expects a NULL terminator at the end of the token list so
that it would know where to stop. Not
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Michael Brunner
commit f230e8ffc03f17bd9d6b90ea890b8252a8cc1821 upstream.
This patch fixes an inverted return value of the gpio get_direction
function.
The wrong value causes the d
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Axel Lin
commit e5d732186270e0881f47d95610316c0614b21c3e upstream.
Remove extra space between platform prefix and DRIVER_NAME in MODULE_ALIAS.
Signed-off-by: Axel Lin
Signed-off-b
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Subbaraya Sundeep Bhatta
commit 459e210c4fd034d20077bcec31fec9472a700fe9 upstream.
Fixed the incorrect macro definitions correctly as per databook.
Signed-off-by: Subbaraya Sundeep
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Sachin Kamat
commit a9fbbbd7d2668232babc60ef77539dd82a33a89c upstream.
'rx' is not used in this function. Remove it.
Signed-off-by: Sachin Kamat
Acked-by: Lars-Peter Clausen
Sign
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Patrick Riphagen
commit 1df5b888f54070a373a73b34488cc78c2365b7b4 upstream.
This adds support for new Xsens device, Motion Tracker Development Board,
using Xsens' own Vendor ID
Sign
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Laura Abbott
commit 72586c6061ab8c23ffd9f301ed19782a44ff5f04 upstream.
Commit 32f13521ca68bc624ff6effc77f308a52b038bf0
("n_tty: Line copy to user buffer in canonical mode")
changed
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Wolfram Sang
commit 1ef9f0583514508bc93427106ceef3215e4eb1a5 upstream.
Fix this from the logs:
usb 7-1: New USB device found, idVendor=046d, idProduct=08ca
...
usb 7-1: Warning! Un
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Philipp Zabel
commit 392bceedb107a3dc1d4287e63d7670d08f702feb upstream.
The driver configures the IDLE condition to interrupt the SDMA engine.
Since the SDMA UART ROM script doesn't
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Paul Cercueil
commit 9df560350c90f3d3909fe653399b3584c9a17b61 upstream.
There are a few issues with the burst mode support. For one we don't setup
the rx buffer, so the buffer will
On 07/08/2015 01:12 AM, Frans Klaver wrote:
On Wed, Jul 8, 2015 at 7:45 AM, Christophe JAILLET
wrote:
Le 07/07/2015 19:04, Khalid Aziz a écrit :
On 07/07/2015 02:45 AM, Frans Klaver wrote:
On Tue, Jul 7, 2015 at 7:39 AM, Christophe JAILLET
wrote:
Stop comparing the strings as soon as we
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Hans de Goede
commit 5f0ee9d17aae628b22be86966471db65be21f262 upstream.
Make the check to skip the rate check more lax, so that it applies
to all hw_version 4 models.
This fixes th
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Jan Kara
commit f18c34e483ff6b1d9866472221e4015b3a4698e4 upstream.
If the specified maximum length of the string is a multiple of unsigned
long, we would load one long behind the sp
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Takashi Iwai
commit b5d724b1add6eabf3aa7276ab3454ea9f45eebd3 upstream.
Acer Aspire 9420 with ALC883 (1025:0107) needs the fixup for EAPD to
make the sound working like other Aspire
3.13.11-ckt23 -stable review patch. If anyone has any objections, please let
me know.
--
From: Jim Bride
commit e058c945e03a629c99606452a6931f632dd28903 upstream.
According to the HSW b-spec we need to try clock divisors of 63
and 72, each 3 or more times, when attempting DP
Hey Al,
On Wed, Jul 08, 2015 at 02:42:38AM +0100, Al Viro wrote:
> Normally opening a file, unlinking it and then closing will have
> the inode freed upon close() (provided that it's not otherwise busy and
> has no remaining links, of course). However, there's one case where that
> does *no
401 - 500 of 1227 matches
Mail list logo
