928.383496] [] (kernfs_fop_write) from []
(__vfs_write+0x2c/0xd4)
[ 5928.391308] [] (__vfs_write) from []
(vfs_write+0xa0/0x144)
[ 5928.398598] [] (vfs_write) from [] (SyS_write+0x44/0x84)
[ 5928.405631] [] (SyS_write) from []
(ret_fast_syscall+0x0/0x3c)
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.o
-by: Marek Szyprowski
Cc: Stable [v3.6+]
---
Hello,
This is a backported version of mainline 9d1400cf79afb49584b commit.
It should apply fine to v3.8.y, v3.7.y and v3.6.y stable kernel trees.
Best regards
Marek Szyprowski
Samsung Poland R&D Center
---
arch/arm/mm/dma-mapping.c |
Hello,
On 3/19/2013 3:24 PM, Luis Henriques wrote:
Hi Marek,
On Tue, Mar 19, 2013 at 08:24:21AM +0100, Marek Szyprowski wrote:
> commit 9d1400cf79afb49584b4873eb22cd5130cb341db upstream.
>
> Atomic pool should always be allocated from DMA zone if such zone is
> available in the sys
Correct value for minimal voltage for ldo10 output is 95 uV. This
patch fixes the typo introduced by patch adf6178ad5552a7f2f742a8c85343c50
("regulator: max8998: Use uV in voltage_map_desc"), what solves broken
probe of max8998 in v3.8-rc4.
Signed-off-by: Marek Szyprowski
the issues introduced by patch
1056e4388b0454917a512618c8416a98628fc9ce ("v4l2-dev: Fix race condition
on __video_register_device"), which has been merged in v3.12-rc1.
Signed-off-by: Marek Szyprowski
Cc: stable@vger.kernel.org
---
This patch should be applied also to stable v3
GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
flags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an
atomic allocation, the code must test __GFP_WAIT flag presence. This patch
fixes the issue introduced in v3.6-rc5
Signed-off-by: Marek Szyprowski
Signed-off-by: Marek Szyprowski
---
arch/x86/kernel/pci-dma.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
index 872079a..32a81c9 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -100,7 +100,7
Hello,
On 2014-01-17 11:49, Andy Whitcroft wrote:
On Fri, Jan 17, 2014 at 8:46 AM, Marek Szyprowski
wrote:
> GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
> flags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an
> atomic allocation,
: stable@vger.kernel.org
Signed-off-by: Marek Szyprowski
---
arch/x86/kernel/pci-dma.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
index 872079a..3519a78 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel
: stable@vger.kernel.org
Signed-off-by: Marek Szyprowski
---
Changelog:
v3:
- fixed spelling issues
v2:
- added more comments in the code to explain for _GFP_WAIT test
v1:
- initial version
---
arch/x86/kernel/pci-dma.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a
condition. This issue has been introduced by
commit 4d852ef8c2544ce21ae41414099a7504c61164a0 ("arm: dma-mapping: Add
support to extend DMA IOMMU mappings").
Reported-by: Hyungwon Hwang
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.org # v3.15+
---
arch/arm/mm/dma-mapping.c
condition. This issue has been introduced by
commit 4d852ef8c2544ce21ae41414099a7504c61164a0 ("arm: dma-mapping: Add
support to extend DMA IOMMU mappings").
Reported-by: Hyungwon Hwang
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.org # v3.15+
---
V2 fixed build problem c
enabled and exynos-drm driver tries to allocate
buffer via DMA mapping API on Odroid-XU3 board.
Fixes: b70045167815 ("ARM: dts: add sysmmu nodes for exynos5420")
Signed-off-by: Joonyoung Shim
Cc: # v4.2
Reviewed-by: Javier Martinez Canillas
Acked-by: Marek Szyprowski
---
Changes for v2
merged in parallel to that commit. This patch adds a missing call to
samsung_clk_of_add_provider(), so the driver is operational again.
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.org # v3.17+
---
drivers/clk/samsung/clk-s5pv210.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/d
dma_mmap() function in IOMMU-based dma-mapping implementation lacked
a check for valid range of mmap parameters (offset and buffer size), what
might have caused access beyond the allocated buffer. This patch fixes
this issue.
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.org # v3.6
IOMMU-based dma_mmap() implementation lacked proper support for offset
parameter used in mmap call (it always assumed that mapping starts from
offset zero). This patch adds support for offset parameter to IOMMU-based
implementation.
Signed-off-by: Marek Szyprowski
CC: stable@vger.kernel.org
be removed
from final buffer size calculation formula. This patch fixes this issue,
solving possible IOMMU page fault caused by FIMD module accessing memory
outside of the given display buffer.
Signed-off by: Marek Szyprowski
CC: stable@vger.kernel.org # v4.0+
---
drivers/gpu/drm/exynos/exy
disable_irq(mct_irq);
Maybe it will be better to simply request this irq in disabled state?
Just call
irq_set_status_flags(mct_irq, IRQ_NOAUTOEN) before request_irq().
+ }
}
err = register_cpu_notifier(&exynos4_mct_cpu_nb);
Best regards
--
Marek Szy
18 matches
Mail list logo
